Avaya Cajun P580, User Manual, Page: 607 / 770

Document No. 650-100-700, Issue 1 21-7
Monitoring the Avaya Multiservice Switch
CLI Command
Use the following CLI commands to configure event notification:
■
To log events in the event log and in the shutdown log,
(configure)#
logging history {start | system | config | temp |
resource | fan | power | service_port | user_port | auth_failure |
bridge_stat | switch_fabric | ospf | dvmrp | rip | ldap | cli | snmp |
appletalk | redundant_cpu | vrrp | unknown_mac | login_stat us
| acl_log | ssl_ssh}
■
To generate SNMP traps,
(configure)#
logging traps {start |
system | config | temp | resource | fan | power | service_port |
user_port | auth_failure | bridge_stat | switch_fabric |
redundant_cpu | unknown_mac | snmp | login_status}
■
To generate event notification to the console,
(configure)#
logging console {start | system | config | temp | resource | fan |
power | service_port | user_port | auth_failure | bridge_stat |
switch_fabric | ospf | dvmrp | rip | ldap | cli | snmp | appletalk |
redundant_cpu | vrrp | unknown_mac | login_status | acl_log |
ssl_ssh}
■
To forward events to syslog servers,
(configure)#
set syslog
facility {start | system | config | temp | resource | fan |
service_port | user_port | power | bridge_stat | switch_fabric |
ospf | rip | ldap | appletalk | auth_failure | redundant_cpu |
dvmrp | cli | snmp | unknown_mac | vrrp | login_status | acl_log |
ssl_ssh | all}
Configuring Notification of Protocol Events
Overview
* Important: If enabled, protocol event logging displays system
messages that help Avaya Technical Support
troubleshoot network problems. Avaya
recommends that logging of protocol events be
enabled only during troubleshooting sessions. If
protocol event logging is enabled during normal
network operation, the switch may display
messages that users may incorrectly interpret as
indications of protocol failures.
If you enable event notification for CLI, SNMP, RIP, OSPF, DVMRP,
LDAP, Apple Talk, or VRRP, you must set which categories of the protocol
events generate notifications.
* Note: Enabling logging of protocol events may cause the event log to
rapidly fill with protocol events.
You can use either the Web Agent or the CLI to configure event notification
for protocol events.