Managing Faults on Virtual Services Platform 7200 Series and 8000 Series Version 5
Table Of Contents
- Contents
- Chapter 1: Introduction
- Chapter 2: New in this document
- Chapter 3: Fault management fundamentals
- Chapter 4: Key Health Indicators using ACLI
- Chapter 5: Key Health Indicators using EDM
- Chapter 6: Link state change control using ACLI
- Chapter 7: Link state change control using EDM
- Chapter 8: RMON configuration using ACLI
- Chapter 9: RMON configuration using EDM
- Enabling RMON globally
- Enabling RMON on a port or VLAN
- Viewing the protocol directory
- Viewing the data source for protocol distribution statistics
- Viewing protocol distribution statistics
- Viewing the host interfaces enabled for monitoring
- Viewing address mappings
- Viewing the data source for host statistics
- Viewing network host statistics
- Viewing application host statistics
- Chapter 10: Log and trap fundamentals
- Chapter 11: Log configuration using ACLI
- Chapter 12: Log configuration using EDM
- Chapter 13: SNMP trap configuration using ACLI
- Chapter 14: SNMP trap configuration using EDM
- Glossary
Important:
The switch does not reply to SNMP requests sent to the Virtual Router Redundancy Protocol
(VRRP) virtual interface address; it does, however, reply to SNMP requests sent to the physical
IP address.
An SNMP manager and agent communicate through the SNMP protocol. A manager sends queries
and an agent responds; however, an agent initiates traps. Several types of packets transmit
between SNMP managers and agents:
• Get request—This message requests the values of one or more objects.
• Get next request—This message requests the value of the next object.
• Set request—This message requests to modify the value of one or more objects.
• Get response—An SNMP agent sends this message in response to a get request, get next
request, or set request message.
• Trap—SNMP trap is a notification triggered by events at the agent.
Log message format
The log messages for the switch have a standardized format. All system messages are tagged with
the following information, except that alarm type and alarm status apply to alarm messages only:
• Avaya proprietary (AP) format—Provides encrypted information for debugging purposes
• CPU slot number—Indicates the CP slot where the command is logged.
• timestamp—Records the date and time at which the event occurred. The format is MM/DD/YY
hh:mm:ss.uuu, where uuu is milliseconds. Example: [11/01/10 11:41:21.376].
• event code—Precisely identifies the event reported.
• alarm code—Specifies the alarm code.
• alarm type—identifies the alarm type (Dynamic or Persistent) for alarm messages
• alarm status—identifies the alarm status (set or clear) for alarm messages
• VRF name—Identifies the Virtual Routing and Forwarding (VRF) instance, if applicable.
• module name—Identifies the software module or hardware from which the log is generated.
• severity level—Identifies the severity of the message.
• sequence number—Identifies a specific CLI command.
• context—Specifies the type of the session used to connect to the switch. If the session is a
remote session, the remote IP address is identified.
• user name—Specifies the user name used to login to the switch.
• ACLI command—Specifies the commands typed during the ACLI session. The system logs
anything type during the ACLI session as soon as the user enters the Enter key.
Log message format
December 2015 Managing Faults on Avaya VSP 7200 Series and 8000 Series 53
Comments on this document? infodev@avaya.com










