Each CA, router, and switch contains the following management agents:
Implementation of the SMA, PMA, and BMA is required.
Implementation of the DMA, SNMP tunneling agent, Vendor-specific agent, and Application-specific agents is optional.
When an asynchronous, exceptional condition associated with one of the implemented management agents occurs, that agent may wish to send an event notice to its respective GSM.
It does this by issuing a Trap(Notice) MAD wherein the Notice attribute indicates the event of interest. Table 9-3 on page 178 describes the contents of the Notice attribute that is returned in the Data field of the Trap MAD.
Field Name | Description |
---|---|
IsGeneric |
|
Type | 7 bits. Indicates the type of event:
|
NodeType or VendorID | 24 bits.
|
TrapNumber/DeviceID |
|
IssuerLID | 16 bits. LID of the port that transmitted the trap. |
NoticeToggle | 1 bit.
|
NoticeCount | When a MA isn't capable of, or is not enabled to deliver notices via the trap mechanism, it may maintain a Notice Queue to log events that may be of interest to its respective manager. In this case, this value indicates the number of notices currently queued up by this MA in this device. For more information, see “Event Subscription and Event Forwarding” on page 801. |
DataDetails |
|
Software within or behind a CA may wish to be informed when a GSM receives a Trap from a specific CA, switch, or router. This is done via the event forwarding subscription mechanism. To subscribe, the subscriber sends a Set(InformInfo) request to the class manager.
The GSM knows who the subscriber is (and therefore who to send an event notice to) by the SLID field in the request packet.
The subscriber tells the GSM that it wishes to be notified when a Trap MAD is received from a specific port or a range of ports. The information provided to the GSM in the InformInfo attribute identifies which CA or router ports, or switch management port the subscriber is interested in. The port of interest is specified by its GID or LID. Alternatively, the subscriber can define a collection of CA, router, or switch management ports by specifying a LID address range.
The class manager responds to the Set(InformInfo) request GMP with a GetResp(InformInfo) message to confirm or deny the requested forwarding. Subscribers wishing to subscribe to event forwarding may determine which managers exist and their locations on the fabric by querying the SA.
Upon receipt of a Trap(Notice) GMP from a port, the GSM determines if anyone has subscribed to receive notices of that type from that port. If so, the GSM sends a Report(Notice) GMP to the subscriber. The subscriber, in turn, responds with a ReportResp(Notice) GMP with the same transaction ID as that issued by the class manager—in its Report(Notice) GMP—and an empty Notice attribute.
Software within or behind a CA may wish to be informed when the SA receives a Trap from a specific CA, switch, or router.
The SA implements four methods to support subscription capability: