Cisco Cisco ASR 5500 Guide De Dépannage
Contents
Overview
Explanation
Example output
ASR 5000
ASR 5500
Related Cisco Support Community Discussions
Overview
The implementation of Link Aggregation (LAG) changes the behavior of "show port npu counters"
and "show port utilization table" commands. The port commands are important for troubleshooting
port and throughput related issues and so it is important to be able to properly interpret their
output, especially since it is unintuitive when compared to non-LAG ports. The bottom line is that
port npu counters for LAG on an individual port basis are not available and are reported for the
entire LAG group only up to at least StarOS v18 which is the time of this writing. This could
change in future releases.
and "show port utilization table" commands. The port commands are important for troubleshooting
port and throughput related issues and so it is important to be able to properly interpret their
output, especially since it is unintuitive when compared to non-LAG ports. The bottom line is that
port npu counters for LAG on an individual port basis are not available and are reported for the
entire LAG group only up to at least StarOS v18 which is the time of this writing. This could
change in future releases.
Explanation
Due to design/ar
Because the implementation of LAG requires all the ports in the LAG to be active, "show port
utilization table" reports utilization for all the LAG ports whether they are distributing (active) or
agreed (standby) for both ASR 5000/5500. Sidenote: Normally agreed ports show no traffic, but
there have been instances where the Rx and/or Tx direction of agreed ports are also carrying
traffic (not the subject of this article but just pointing it out).
utilization table" reports utilization for all the LAG ports whether they are distributing (active) or
agreed (standby) for both ASR 5000/5500. Sidenote: Normally agreed ports show no traffic, but
there have been instances where the Rx and/or Tx direction of agreed ports are also carrying
traffic (not the subject of this article but just pointing it out).
Meanwhile for non-LAG ports, there is a difference between what is reported for ASR 5000 vs.
ASR 5500. ASR 5000 does not report utilization for standby ports, while ASR 5500 does report
utilization for standby ports (even though those ports are operationally down)
ASR 5500. ASR 5000 does not report utilization for standby ports, while ASR 5500 does report
utilization for standby ports (even though those ports are operationally down)
Consistent with what has just been mentioned, "show port table" for LAG reports all the ports as
operationally up, compared to non-LAG where only the active port of a port pair is operationally
up.
operationally up, compared to non-LAG where only the active port of a port pair is operationally
up.
For "show port npu counters", ALL LAG ports are listed, but the following is true:
- ASR 5000:
- the counters under the Master (configured) port are a TOTAL count across all the currently
ACTIVE ports
- the counters for ALL other ports (including the master port's pair) are not relevant and should
not be used
- ASR 5500:
- the counters under the Master port and its standby are a TOTAL count across all the currently
ACTIVE ports (they will both report a similar but slightly different value - use either one)
- the counters for ALL other ports are 0s
- the counters under the Master (configured) port are a TOTAL count across all the currently
ACTIVE ports
- the counters for ALL other ports (including the master port's pair) are not relevant and should
not be used
- ASR 5500:
- the counters under the Master port and its standby are a TOTAL count across all the currently
ACTIVE ports (they will both report a similar but slightly different value - use either one)
- the counters for ALL other ports are 0s