Traps and objects to enable traps, In this chapter, Objects for brocade 6910 switch traps – Brocade 6910 Ethernet Access Switch MIB Reference User Manual
Page 91: Trap information, Trap receiver table, Chapter 14, Chapter
Brocade 6910 Ethernet Access Switch MIB Reference
79
53-1002652-02
Chapter
14
Traps and Objects to Enable Traps
In this chapter
•
Objects for Brocade 6910 switch traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
•
•
•
Objects for Brocade 6910 switch traps
This section present the objects available to enable or disable traps.
Trap information
The following objects provide general information on traps.
Trap receiver table
This table allows you to configure trap receivers on the Brocade 6910 switch:
Name, OID, and Syntax
Access
Description
snAgTrpRcvrCurEntry
brcdIp.1.1.2.1.16
Syntax: Integer
Read only
Shows the total number of entries that are currently in the Trap
Receiver Table. There can be up to 5 entries.
Name, OID, and Syntax
Access
Description
fdryTrapReceiverTable
brcdIp.1.1.10.1.1.1
None
The Trap Receiver Table.
fdryTrapReceiverEntry
brcdIp.1.1.10.1.1.1.1
None
An entry in the Trap Receiver Table. This table uses a running
index as the index to the table.
Reasons to use the running index scheme rather than IP
addresses:
1
The table will be Virtual Routing and Forwarding (VRF)
independent so that multiple VRFs can share the same
address type and address.
2
An index with address type and address could be
potentially 17 unsigned integers, causing parsing and
finding the next index to take much CPU time. The PDU
gets to be huge too.
3
An IP address is just another attribute, and they are
supposed to be a list of servers.