Interface Problems; Workstation Is Unable To Log In To The Network - Cisco Catalyst 4500e Series Installation Manual

Chapter 5 Troubleshooting
If the status is "power-bad," the switch detects a switching module but is unable to allocate power. This
situation is possible if the supervisor engine cannot able to access the serial PROM (SPROM) contents
on the module in order to determine the identification of the line card. Enter the show idprom module
slot command to verify that the SPROM is readable. If the SPROM is not accessible, reset the module.
Enter the show diagnostics online module slot number command to identify hardware failures on the
module. 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

If you see an error mentioned in the output of the show interface command, the reason could be:
•
•
•
In order to understand and troubleshoot these problems, refer to Troubleshooting Switch Port and
Interface Problems at:
http://www.cisco.com/en/US/products/hw/switches/ps700/products_tech_note09186a008015bfd6.shtm
l

Workstation Is Unable to Log In to the Network

If you observe that a workstation is unable to log into the network during startup or unable to obtain the
DHCP address when you have powered up a client machine or rebooted, an initial connectivity delay that
the switch introduced could be the problem. To verify this, check the following:
•
•
•
•
•
The reason for these symptoms can be an interface delay that either Spanning Tree Protocol (STP),
EtherChannel, trunking, or an autonegotiation delay causes. For more information about these delays
and possible solutions, refer to
:
http://www.cisco.com/en/US/products/hw/switches/ps700/products_tech_note09186a00800b1500.sht
ml
If you review and follow the procedure in the document and you still have issues, contact Cisco Technical
Support.
OL-13972-01
A physical layer problem, such as a faulty cable or NIC
A configuration problem, such as a speed and duplex mismatch
A performance problem, such as an oversubscription
Microsoft network client displays "No Domain Controllers Available".
DHCP reports "No DHCP Servers Available."
A Novell Internetwork Packet Exchange (IPX) network workstation does not have the Novell login
screen upon bootup.
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.
IBM Network stations can have one of these messages:
NSB83619—Address resolution failed
–
NSB83589—Failed to boot after 1 attempt
–
NSB70519—Failed to connect to a server
–
Troubleshooting Supervisor Engines
Catalyst 4500 E-Series Switches Installation Guide
5-15