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
Application layer host MIB
The application layer host MIB monitors traffic statistics by application protocol for each host.
The system populates an entry for the management IP of the switch to represent the network
segment where the system collects the statistics. You have to enable each host interface that you
want to monitor on the switch.
The system only collects statistics for this group from packets that go to the CP.
Link state change control
Rapid fluctuation in a port link state is called link flapping.
Link flapping is detrimental to network stability because it can trigger recalculation in spanning tree
and the routing table.
If the number of port down events exceeds a configured limit during a specified interval, the system
forces the port out of service.
You can configure link flap detection to control link state changes on a physical port. You can set
thresholds for the number and frequency of changes allowed.
You can configure the system to take one of the following actions if changes exceed the thresholds:
• send a trap
• bring down the port
If changes exceed the link state change thresholds, the system generates a log entry.
Connectivity Fault Management
The Shortest Path Bridging MAC (SPBM) network needs a mechanism to debug connectivity issues
and isolate faults. This function is performed at Layer 2, not Layer 3. Connectivity Fault
Management (CFM) operates at Layer 2 and provides an equivalent of the ping and traceroute
commands. The switch supports a subset of CFM functionality to support troubleshooting of the
SPBM cloud. For more information about CFM see Configuring Avaya Fabric Connect on VSP
Operating System Software, NN47227-510.
Fault management fundamentals
December 2015 Managing Faults on Avaya VSP 7200 Series and 8000 Series 16
Comments on this document? infodev@avaya.com










