Brocade Fabric OS Message Reference (Supporting Fabric OS v7.3.0) - Manual (Page 33)

Fabric OS Message Reference 11
53-1003140-01
Changing the severity level of swEventTrap
1
Priv Protocol: noPriv
Engine ID: 80:00:05:23:01:0a:23:34:21
User 2 (rw): snmpadmin2
Auth Protocol: MD5
Priv Protocol: DES
Engine ID: 80:00:05:23:01:0a:23:34:1b
User 3 (rw): snmpadmin3
Auth Protocol: noAuth
Priv Protocol: noPriv
Engine ID: 00:00:00:00:00:00:00:00:00
User 4 (ro): snmpuser1
Auth Protocol: noAuth
Priv Protocol: noPriv
Engine ID: 00:00:00:00:00:00:00:00:00
User 5 (ro): snmpuser2
Auth Protocol: noAuth
Priv Protocol: noPriv
Engine ID: 00:00:00:00:00:00:00:00:00
User 6 (ro): snmpuser3
Auth Protocol: noAuth
Priv Protocol: noPriv
Engine ID: 00:00:00:00:00:00:00:00:00
SNMPv3 Trap configuration:
Trap Entry 1: 192.0.2.2
Trap Port: 162
Trap User: snmpadmin1
Trap recipient Severity level: 4
Trap Entry 2: 192.0.10.10
Trap Port: 162
Trap User: snmpadmin2
Trap recipient Severity level: 4
Trap Entry 3: No trap recipient configured yet
Trap Entry 4: No trap recipient configured yet
Trap Entry 5: No trap recipient configured yet
Port logs
The Fabric OS maintains an internal log of all port activity. Each switch or logical switch maintains a
log file for each port. Port logs are circular buffers that can save up to 8000 entries per logical
switch. When the log is full, the newest log entries overwrite the oldest log entries. Port logs capture
switch-to-device, device-to-switch, switch-to-switch, some device A-to-device B, and control
information. Port logs are not persistent and are lost over power cycles and reboots.
Execute the portLogShow command to display the port logs for a particular port.
Execute the portLogEventShow command to display the specific events reported for each port.
Port log functionality is completely separate from the system message log. Port logs are typically
used to troubleshoot device connections.
Changing the severity level of swEventTrap
When an event occurs and if the event severity level is at or below the set severity level, the SNMP
trap, swEventTrap, is sent to the configured trap recipients. By default, the severity level is set at 0
(None), implying that all the event traps are sent. Use the snmpConfig
--
set mibCapability
command to modify the severity level of swEventTrap.