Cisco Cisco ASR 5000 Guide De Dépannage
Contents
Introduction
Troubleshooting commands
Remediation actions
Example troubleshooting scenarios
Standby PGW Inter Chassis Session Recovery (ICSR) node is receiving high volume of trafficfrom Juniper MX-960
Missing packets between datalink and npu counters
Datalink TX Pause and RX OVF on ASR 5000
Increasing TX ERR due to mismatched port settings on ASR 5500 management port
Increasing Bad Frames and Tx Collisions on management port due to half duplex
Unexpected LAG Switchover - LAG Port 23/1 Issue
Unexplained port errors on Juniper router peered with XGLC Port 27/1 (subscriber impacting)
LAG switchover failed to stick due to failed XGLC
Related Cisco Support Community Discussions
Introduction
This article presents ideas on how to troubleshoot various port related issues ASR 5000 and 5500
platforms including issues related to the Network Processing Unit (NPU), and touches a bit on Link
Aggregation (LAG) issues as well. These techniques are not rocket science and in fact are mostly
known by engineers, but often one or more may be skipped over in the troubleshooting process
simply due to oversight in the rush through the steps towards potential resolution. The article first
starts off with the port related health checks. Then it lays out all the approaches in some kind of
methodical order. Finally it offers a series of real examples that go beyond basic port
troubleshooting for those who want to dig deep.
platforms including issues related to the Network Processing Unit (NPU), and touches a bit on Link
Aggregation (LAG) issues as well. These techniques are not rocket science and in fact are mostly
known by engineers, but often one or more may be skipped over in the troubleshooting process
simply due to oversight in the rush through the steps towards potential resolution. The article first
starts off with the port related health checks. Then it lays out all the approaches in some kind of
methodical order. Finally it offers a series of real examples that go beyond basic port
troubleshooting for those who want to dig deep.
Troubleshooting commands
show snmp trap history
Look for patterns of PortLinkUp and PortLinkDown. Consider:
- how often it is happening and over what time period
- multiple ports or just one port or some other pattern
- maintenance work that technicians may or may not be aware of
- how often it is happening and over what time period
- multiple ports or just one port or some other pattern
- maintenance work that technicians may or may not be aware of
show port table all
- indicates whether the links are up or down
- Link Aggregation (LAG) - confirm ports are in the correct state, either + (distributing/active) or ~
(agreed/standby). Other states * or - need further investigation.
- Link Aggregation (LAG) - confirm ports are in the correct state, either + (distributing/active) or ~
(agreed/standby). Other states * or - need further investigation.
show port info
- various information such as link state, port mode, port settings, Link Aggregation (LAG) settings,