100 Configuring standard security features
Sample modification of the options for configuring SNMP MIB traps
The following
snmpMibCapSet
parameters for FA-TRAP appear in the preceding example:
•
connUnitStatusChange
indicates that the overall status of the connectivity unit has changed. Its
variables are:
•
connUnitStatus
: the status of the connection unit
•
connUnitState
: the state of the connection unit
•
connUnitEventTrap indicates that the connectivity unit has generated an event. Its variables are:
•
connUnitEventId
: the internal event ID
•
connUnitEventType
: the type of this event
•
connUnitEventObject
is used with the connUnitEventType to identify the object to which the
event refers.
•
connUnitEventDescr
is the description of the event.
•
connUnitSensorStatusChange
indicates that the status of the sensor associated with the
connectivity unit has changed.
•
connUnitSensorStatus
is the status indicated by the sensor.
•
connUnitPortStatusChange
indicates that the status of the sensor associated with the connectivity
unit has changed.
•
connUnitPortStatus
shows overall protocol status for the port.
•
connUnitPortState
shows the user-specified state of the port hardware.
switch:admin>
snmpmibcapset
The SNMP Mib/Trap Capability has been set to support
FE-MIB
SW-MIB
FA-MIB
FA-TRAP
FA-MIB (yes, y, no, n): [yes]
FICON-MIB (yes, y, no, n): [no]
y
HA-MIB (yes, y, no, n): [no]
y
SW-TRAP (yes, y, no, n): [no]
y
swFCPortScn (yes, y, no, n): [no]
swEventTrap (yes, y, no, n): [no]
swFabricWatchTrap (yes, y, no, n): [no]
swTrackChangesTrap (yes, y, no, n): [no]
FA-TRAP (yes, y, no, n): [yes]
connUnitStatusChange (yes, y, no, n): [no]
connUnitEventTrap (yes, y, no, n): [no]
connUnitSensorStatusChange (yes, y, no, n): [no]
connUnitPortStatusChange (yes, y, no, n): [no]
SW-EXTTRAP (yes, y, no, n): [no]
y
FICON-TRAP (yes, y, no, n): [no]
y
linkRNIDDeviceRegistration (yes, y, no, n): [no]
linkRNIDDeviceDeRegistration (yes, y, no, n): [no]
linkLIRRListenerAdded (yes, y, no, n): [no]
linkLIRRListenerRemoved (yes, y, no, n): [no]
linkRLIRFailureIncident (yes, y, no, n): [no]
HA-TRAP (yes, y, no, n): [no]
y
fruStatusChanged (yes, y, no, n): [no]
cpStatusChanged (yes, y, no, n): [no]
fruHistoryTrap (yes, y, no, n): [no]
Avoid-Duplicate-TRAP (yes, y, no, n): [no]
y
switch:admin>
Summary of Contents for AE370A - Brocade 4Gb SAN Switch 4/12
Page 18: ...18 ...
Page 82: ...82 Managing user accounts ...
Page 102: ...102 Configuring standard security features ...
Page 126: ...126 Maintaining configurations ...
Page 198: ...198 Routing traffic ...
Page 238: ...238 Using the FC FC routing service ...
Page 260: ...260 Administering FICON fabrics ...
Page 280: ...280 Working with diagnostic features ...
Page 332: ...332 Administering Extended Fabrics ...
Page 414: ...398 Configuring the PID format ...
Page 420: ...404 Configuring interoperability mode ...
Page 426: ...410 Understanding legacy password behaviour ...
Page 442: ...426 ...
Page 444: ......
Page 447: ......