6. Research and consider the following additional causes:
•
Traffic congestion
Examine the MIB statistics and the event log to check for traffic congestion. If you
determine that traffic congestion is the problem, consider redistributing traffic to relieve
congestion.
• A software anomaly
Check Release Notes for any potential issues.
7. Look at the LEDs on the router’s front and rear panels, and refer to the event log and MIB
statistics to answer the following questions:
Are the symptoms limited to:
• A single protocol on a single port?
If so, the problem is most likely in the network layer or above.
• Multiple protocols on a single port?
If so, the problem is most likely in the physical or data link layer.
• A single protocol on multiple ports in one slot?
If so, the problem is most likely in the configuration of the network layer protocol.
• Multiple protocols on multiple ports in one slot?
If so, and if the same protocols are running successfully in other slots, the problem is most
likely physical.
• A single protocol on multiple ports in all slots running that protocol?
If so, the problem is most likely in the configuration of the network layer protocol. Make
sure you enabled the protocol.
• Multiple protocols on multiple ports in all slots in the router?
If so, the problem is most likely operational.
• Multiple routers?
If so, the problem is most likely due to an external device. Try to determine the cause of
the problem.
Determining the scope of a problem
18 Troubleshooting August 2013
Comments? infodev@avaya.com
To Next Page
Loading...
