The following display is an abbreviated output from the command, show interface Ethernet 1/1. Two packet drop counters appear under the counters reading the logical interface information. Conditions that may cause these counters to increment are explained below:
Dec 12, 2015 I wane try to get an overview of interfaces with errors. Command: Show interface counters errors. Switch# port align-err FCS-err Xmit-err RCV-err undersize. Eth101/1/1 0 0 0 0 0. Because the interface also contains a 0 it wont show any lines. Jun 10, 2010 - 'show interfaces counters errors' is a great Cisco switch command which gives you a detailed look at the different types of errors on a switch.
show interface ethernet1/1
-------------------------------------------------------------------------------
Name: ethernet1/1, ID: 17
Link status:
Link status:
Runtime link speed/duplex/state: 1000/full/up
Configured link speed/duplex/state: 1000/full/auto
MAC address:
Port MAC address 00:1b:17:0b:80:11
Operation mode: virtual-wire
-------------------------------------------------------------------------------
Logical interface counters read from CPU:
-------------------------------------------------------------------------------
bytes received 675651250
bytes transmitted 523417297
packets received 916417
packets transmitted 816119
receive errors 0
packets dropped 0
packets dropped by flow state check 55
packets dropped by flow state check: This counter is incremented for packets matching flows which are either in expired/inactive/discard states and have not been removed by age-out process.
packets dropped: This counter is indicative of several conditions such as receiving the multicast packets on the same interface, dropping non-ip packets (other than ARP), no topology is configured, a session setup failure, or a discarded route is found.
owner: panagent
Applicable Products
- NetScaler
Information
This article contains information about cyclic redundancy check (CRC) error on a NetScaler interface.
Cyclic Redundancy Check Error on a NetScaler Interface
CRC value is created by the sending device and is recalculated by the receiving device to check for damage that might have occurred to the frame in transit. The nic_err_rx_crc counter tracks the number of received packets with CRC errors received on the specified interface.
An increment in the nic_err_rx_crc counter generally indicates noise or transmission problems on the LAN interface or the LAN bus. A high number of CRC errors are usually the result of collisions or a station transmitting bad data or malfunctioning Ethernet device.
The issue might be with the NetScaler interface or the interface on the Switch or the Router connected to the NetScaler appliance.
Run the following command to check the interface errors on Cisco Switch or Router:
show interfaces ethernet [slot | port]
If there is no error count on upstream Switch or Router, run the following command to verify if the nic_err_rx_crc counter is increasing on the appliance:
BSD_6.3 [nslog] $ nsconmsg92 -K newnslog -g nic_err_rx_crc -s disptime=2 -d current | more
Additional Resources
Complete the following steps to troubleshoot NetScaler 0/1 interface flapping issue:
- Look for any interface getting muted or L2 MAC moves errors in newnslog on NetScaler.
- Look for any CRC errors in newnslog files as mentioned in this article http://support.citrix.com/article/CTX135215.
- If the errors are RECEIVE errors then this means they are (usually) caused by something outside of the NetScaler (cables, switch port, SFPs). Being these are receive errors, very rarely are they caused by NetScaler hardware being bad, especially considering these are on different NICs (built-in on motherboard for 0/1, and a card for 1/3).
- Troubleshoot the CRC errors by swapping cables, SFPs (if used), and switch ports, in that order, to see if the problem moves/goes away, in order to identify the cause.