Disabling syslog messages and traps for cli access, Examples of syslog messages for cli access – Brocade BigIron RX Series Configuration Guide User Manual
Page 201

BigIron RX Series Configuration Guide
123
53-1002484-04
Configuring Simple Network Management Protocol traps
5
NOTE
By default, all SNMP traps are enabled at system startup.
You can selectively disable one or more of the following traps:
•
SNMP authentication key
•
Power supply failure
•
Fan failure
•
Cold start
•
Link up
•
Link down
•
Bridge new root
•
Bridge topology change
•
Locked address violation
•
Module insert
•
Module remove
•
BGP4
•
OSPF
•
FSRP
•
VRRP
•
VRRPE
To stop link down occurrences from being reported, enter the following.
BigIron RX(config)# no snmp-server enable traps link-down
Syntax: [no] snmp-server enable traps <trap-type>
A list of Brocade traps is available in the MIB Reference Guide.
Disabling Syslog messages and traps for CLI access
The device sends Syslog messages and SNMP traps when a user logs into or out of the User EXEC
or Privileged EXEC level of the CLI. The feature, enabled by default, applies to users whose access
is authenticated by an authentication-method list based on a local user account, RADIUS server, or
TACACS and TACACS+ server.
NOTE
The Privileged EXEC level is sometimes called the “Enable” level, because the command for
accessing this level is enable.
Examples of Syslog messages for CLI access
When a user whose access is authenticated by a local user account, a RADIUS server, or a TACACS
and TACACS+ server logs into or out of the CLI’s User EXEC or Privileged EXEC mode, the software
generates a Syslog message and trap containing the following information:
•
The time stamp
•
The user name