Technical data

6 Network OS Message Reference

53-1002489-01

Configuring the syslog message destinations

You can reset the console severity level to the default (INFO) using the no logging rbridge-id

rbridge-id raslog console command.

SNMP management station

When an unusual event, error, or a status change occurs on the device, an event notification is sent

to the SNMP management station. Network OS v2.1.1 supports two types of event notifications:

traps (in SNMPv1, SNMPv2c, and SNMPv3) and informs (in SNMPv3).

SNMP traps

An unsolicited message that comes to the management station from the SNMP agent on the

device is called a trap. 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. The VarBind in

the Trap Data Unit contains the corresponding instance of the event index, time information, event

severity level, the repeat count, and description. The possible severity levels are as follows:

• Critical

• Debug

• Error

• Info

• None

• Warning

By default, the severity level is set to None, implying all traps are filtered and therefore no event

traps are received. When the severity level is set to Info, all traps with the severity level of Info,

Warning, Error, and Critical are received.

NOTE

The Audit log messages are not converted into swEventTrap.

The SNMP traps are unreliable because the trap recipient does not send any acknowledgment

when it receives a trap. Therefore, the SNMP agent cannot determine if the trap was received.

Brocade switches send traps out on UDP port 162. To receive traps, the management station IP

address must be configured on the switch. You can configure the SNMPv1, SNMPv2c, and SNMPv3

hosts to receive the traps. For more information, refer to “Configuring the SNMP (version 1 or

version 2c) server host” on page 7.

SNMP informs

An SNMP inform is similar to the trap except that the management station that receives an SNMP

inform acknowledges the system message with an SNMP response PDU. If the sender does not

receive the SNMP response, the inform request can be sent again. An SNMP inform request is

saved in the switch memory until a response is received or the request times out. The informs are

more reliable and they consume more resources in the device and in the network. Use SNMP

informs only if it is important that the management station receives all event notifications.

Otherwise, use the SNMP traps.

Brocade devices support SNMPv3 informs. For more information, refer to “Configuring the SNMPv3

server” on page 8.