he following is a sample output when the stack port flaps:
Device# show switch stack-ports detail 1/1 is OK Loopback No Cable Length 50cm Neighbor 2 Link Ok Yes Sync Ok Yes Link Active Yes Changes to LinkOK 4 Five minute input rate 0 bytes/sec Five minute output rate 0 bytes/sec 320 bytes input 80 bytes output CRC Errors Data CRC 0 Ringword CRC 0 InvRingWord 0 PcsCodeWord 770 1/2 is OK Loopback No Cable Length 50cm Neighbor 3 Link Ok Yes Sync Ok Yes Link Active Yes Changes to LinkOK 1 Five minute input rate 5 bytes/sec Five minute output rate 1 bytes/sec 2949 bytes input 320 bytes output CRC Errors Data CRC 0 Ringword CRC 0 InvRingWord 0 PcsCodeWord 0 2/1 is OK Loopback No Cable Length 50cm Neighbor 3 Link Ok Yes Sync Ok Yes Link Active Yes Changes to LinkOK 1 Five minute input rate 0 bytes/sec Five minute output rate 0 bytes/sec 49375 bytes input Managing Switch Stacks show switch stack-ports detail Command Output:
Example Field Description Five minute input rate The average rate (calculated over a five minute period) at which packets are received, measured in packets/sec. Five minute output rate The average rate (calculated over a five minute period) at which packets are transmitted, measured in packets/sec. CRC Errors Different types of Cyclic Redundancy Check (CRC) errors that are seen on a stack interface: • Data CRC: Stack interface data CRC error • Ringword CRC: Stack interface ring word CRC error • InvRingWord: Stack interface invalid ring word error • PcsCodeWord:
Stack interface Physical Coding Sublayer (PCS) error These errors normally occur when a stack interface state changes due to a switchover or a switch reload. You can ignore such errors. But when these error counters increase significantly or when they increase continuously over a period of time, check the stack cable for issues. Managing Switch Stacks 16