Troubleshooting Ist Failure Using The Cli - Avaya 8800 Troubleshooting Manual
Ethernet routing switch
Hide thumbs
Also See for 8800:
- Planning and engineering, network design (327 pages) ,
- Planning and engineering (306 pages) ,
- Configuration manual (226 pages)
Table of Contents
Advertisement
8. After the SMLT links recover, to inspect ARP table software records for their
Troubleshooting IST failure using the CLI
When interswitch trunk (IST) links are used, all critical network traffic runs this link. Therefore,
in the event of IST failure, network protocols like RIP, VRRP, OSPF, VLACP and so on go up
and down and eventually causes a network outage.
There are the possible reasons for IST failure:
• The IST had been disabled.
• An incorrect peer IP address is configured.
• The MLT does not have the proper ports configured.
• MLT ports are down.
Note:
When the VLACP protocol goes up and down (flaps) rapidly, this behavior can cause
system-wide instability, including high CPU utilization. For more information on how to
resolve VLACP flapping, see Avaya Ethernet Routing Switch 8800/8600 Configuration —
Link Aggregation, MLT, and SMLT (NN46205-518).
For a flowchart recovery tree, see
Procedure steps
1. Check IST settings:
2. Check MLT settings:
Troubleshooting
show vlan mac-address-entry [vlan <vid>]
integrity, enter the following CLI command:
show ip arp info [<ip address>]
OR
enter the following ACLI command:
show ip arp [<ip address>]
show mlt ist info
If any settings are incorrect, make the correction.
show mlt info
Troubleshooting IST failure using the CLI
IST failure
on page 335.
July 2013
351
Advertisement
Table of Contents
Troubleshooting
