Specifications
Note:
The
VlanZero
counter can increase even if the
TxCrcErrors
counter does not increase. This situation can indicate a different issue. Contact Cisco Technical Support for further assistance.
If you run Cisco IOS Software Release 12.1(11b)EW or later, issue the
show platform cpu packet statistics
command multiple times and look for increments in the
VlanZeroBadCrc
counter. Here is an example:
cat4k#
show platform cpu packet statistics | include VlanZeroBadCrc
VlanZeroBadCrc
94471 9 9 8 7
cat4k#
cat4k#
show platform cpu packet statistics | include VlanZeroBadCrc
VlanZeroBadCrc
94545 9 9 8 7
cat4k#
3. If both Step 1 and Step 2 show symptoms of packet loss, issue the
reload
command to soft reset the switch, and observe the power-on self test (POST) results at system reset.
Make sure to capture all the output to a text file.
cat4k#
reload
Proceed with reload? [confirm]
1d21h: %SYS-5-RELOAD: Reload requested
<output truncated>
Decompressing the image : ###################################################
#################################[OK]
k2diags version 1.6
prod: WS-X4014 part: 73-6854-09 serial: JAB0620090U
Power-on-self-test for Module 1: WS-X4014
Status: (. = Pass, F = Fail)
Traffic using serdes loopback (L2; one port at a time)...
switch port 0: . switch port 1: . switch port 2: .
switch port 3: . switch port 4: . switch port 5: .
switch port 6: . switch port 7: . switch port 8: .
switch port 9: . switch port 10: . switch port 11: .
switch port 12: . switch port 13: . switch port 14: .
switch port 15: . switch port 16: . switch port 17: .
switch port 18: . switch port 19: . switch port 20: .
switch port 21: . switch port 22: . switch port 23: .
switch port 24: . switch port 25: . switch port 26: .
switch port 27: . switch port 28: . switch port 29: .
switch port 30: . switch port 31: .
Traffic using asic loopback (L2; all ports at once)...
switch port 0: F switch port 1: F switch port 2: F
switch port 3: F switch port 4: F switch port 5: F
switch port 6: F switch port 7: F switch port 8: F
switch port 9: F switch port 10: F switch port 11: F
switch port 12: F switch port 13: F switch port 14: F
switch port 15: F switch port 16: F switch port 17: F
switch port 18: F switch port 19: F switch port 20: F
switch port 21: F switch port 22: F switch port 23: F
switch port 24: F switch port 25: F switch port 26: F
switch port 27: F switch port 28: F switch port 29: F
switch port 30: F switch port 31: F
Traffic using asic loopback (L3; all ports at once)...
switch port 0: F switch port 1: F switch port 2: F
switch port 3: F switch port 4: F switch port 5: F
switch port 6: F switch port 7: F switch port 8: F
switch port 9: F switch port 10: F switch port 11: F
switch port 12: F switch port 13: F switch port 14: F
switch port 15: F switch port 16: F switch port 17: F
switch port 18: F switch port 19: F switch port 20: F
switch port 21: F switch port 22: F switch port 23: F
switch port 24: F switch port 25: F switch port 26: F
switch port 27: F switch port 28: F switch port 29: F
switch port 30: F switch port 31: F
Module 1 Failed
Exiting to ios...
This example shows a Supervisor Engine module diagnostic failure.
4. If Step 3 results in a Supervisor Engine module diagnostic failure, power cycle the switch and observe the POST results at bootup.
5. Issue the
show diagnostics power-on
command to verify the POST results from bootup and determine if diagnostics fail again.
If diagnostics fail again, the problem is most likely bad hardware. Contact Cisco
Technical Support for further assistance.
If the Supervisor Engine passes the diagnostics tests without any failure after the power cycle in Step 4, perform these steps:
a. Collect the output from the
show tech-support
command.
b. Remove all power supplies from the box, and collect the serial numbers, Cisco part number, and manufacturer of the power supplies.
c. Contact Cisco Technical Support with the information that you collected.
Note:
If Cisco Technical Support did not assist with the troubleshoot procedure, you must provide the information in the order of these steps.
Troubleshoot Error Messages in the Syslog or Console
If you get error messages in the syslog or console, see this Common Reasons and Solutions section in order to help identify the problem:
Common Reasons and Solutions
The system messages appear on the console if you have enabled console logging or appear in the syslog if you have enabled syslog. Some of the messages are for informational purposes only and do not indicate an error condition. Issue the
show logging
command in order to
display the log messages. In order to better understand a specific system message, refer to Message and Recovery Procedures.
If you still cannot narrow down the problem, or if the error message is not present in the document, contact the Cisco Technical Support Escalation Center.
Troubleshoot Module Failure to Come Online
Part of the module can fail to come online. You may have a module failure if you see an amber or red status LED or if you see one of these statuses in the output of the
show module
command:
z
other
z
faulty
z
err-disable
z
power-deny
z
power-bad
Common Reasons and Solutions
z
Check the
Supported Hardware
section of the Release Notes for the relevant release. If the module does not have support in the software that you currently run, download the necessary software from Downloads - Cisco IOS Software (
registered customers only
) .
Note:
The WS-X4232-L3 module is not supported on a Supervisor Engine II+, III, IV, or V.
z
Ensure that the switch loads an image that supports the corresponding line card or module.
z
If the status is
power-deny
, the switch does not have enough power available to power this module. Issue the
show power
command in order to confirm whether enough power is available. For more information, refer to Environmental Monitoring and Power Management.
z
If the status is
power-bad
, the switch is able to see a card but unable to allocate power. This situation is possible if the Supervisor Engine is not able to access the serial PROM (SPROM) contents on the module in order
to determine the identification of the line card. Issue the
show idprom module
slot
command in order to verify if the SPROM is readable. If SPROM is not accessible, you can reset the module.
z
Make sure that the module is properly seated and that you have completely screwed down the module. If the module still does not come online, issue the
hw-module slot
slot number
reset
command. If the module still does not come online, try the module in a spare slot,
swap the module with the slot of a module that works, or try the module in a different chassis.
z
Issue the
show diagnostics online module
slot number
command in order to identify any hardware failures on the module. You may follow the previous solution before you conclude that the module had hardware that failed.
If the module still does not come online, create a service request with Cisco
Technical Support in order to troubleshoot further. Use the log of the switch output that you collected in the above output and the troubleshooting steps that you performed.
Interface Problems
Workstation Is Unable to Log In to the Network During Startup or Unable to Obtain the DHCP Address
If you observe one of these symptoms when you have powered up a client machine or rebooted, the problem can be due to an initial connectivity delay that the switch introduced:
z
Microsoft network client displays "No Domain Controllers Available".
z
DHCP reports "No DHCP Servers Available".
z
A Novell Internetwork Packet Exchange (IPX) network workstation does not have the Novell login screen upon bootup.
z
An AppleTalk network client displays, "Access to your AppleTalk network has been interrupted. In order to reestablish your connection, open and close the AppleTalk control panel." The AppleTalk client chooser application can either fail to display a zone list or display an
incomplete zone list.
z
IBM Network stations can have one of these messages: