Résumé du contenu de la page N° 1
Troubleshooting Cisco Catalyst Switches to NIC
Compatibility Issues
Document ID: 17053
Introduction
Prerequisites
Requirements
Components Used
Conventions
Background Information
Purpose
Why Do Autonegotiation and Compatibility Issues Exist?
General Troubleshooting for 10/100/1000 Mbps NICs
Autonegotiation Valid Configuration Table
EtherChannel and Trunking Between Catalyst Switches and NICs
Verifying Physical Connection and Link
Verifying Swi
Résumé du contenu de la page N° 2
Components Used This document is not restricted to specific software and hardware versions. Conventions Refer to Cisco Technical Tips Conventions for more information on document conventions. Background Information Purpose This document discusses how to troubleshoot these issues: • Autonegotiation • Physical Connectivity • Port Errors (Data Link Errors) • Continuous Link Up/Down Situations • Gigabit Port Configuration • Common Catalyst Switch Software Issues • Common NIC Issues and Resolutions W
Résumé du contenu de la page N° 3
performance−related issues. The most common problems with NIC issues deal with speed and duplex configuration. Table 1 summarizes all possible settings of speed and duplex for FastEthernet NICs and switch ports. Note: This section is only applicable for 10/100/1000 Mbps (1000BASE−T) NICs, and not 1000BASE−X NICs. Table 1 Autonegotiation Valid Configuration Configuration NIC Configuration Resulting (Speed/Duplex) Resulting NIC Switch Catalyst Comments Speed/Duplex (Speed/Duplex) Speed/Duplex Assu
Résumé du contenu de la page N° 4
100 Mbps, 100 Mbps, 100 Mbps, Duplex 1 Full−duplex Full−duplex Half−duplex Mismatch AUTO 100 Mbps, 100 Mbps, 100 Mbps, Duplex 1 Full−duplex Half−duplex Full−duplex Mismatch 100 Mbps, Correct Full−duplex 100 Mbps, 100 Mbps, 100 Mbps, Manual Full−duplex Full−duplex Full−duplex 2 Configuration Link is established, but switch does not see any 100 Mbps, autonegotiation Half−duplex 100 Mbps, 100 Mbps, AUTO information Half−duplex Half−duplex from NIC and defaults to half−duplex when operating at 10/
Résumé du contenu de la page N° 5
2 Some third−party NIC cards can fall back to half−duplex operation mode, even though both the switchport and NIC configuration are manually configured for 100 Mbps, full−duplex. This is because NIC autonegotiation link detection still operates when the NIC is manually configured. This causes duplex inconsistency between the switchport and the NIC. Symptoms include poor port performance and frame check sequence (FCS) errors that increment on the switchport. In order to troubleshoot this issue,
Résumé du contenu de la page N° 6
Example for Cisco IOS Software on the Switch − Catalyst 2900XL, 3500XL, 2948G−L3, and 6000 that Run Cisco IOS Software • show interfaces type Switch# show interfaces fastethernet 0/1 FastEthernet0/1 is down, line protocol is down States other than connected and line protocol is up indicate a physical connectivity issue. Complete these steps in order to troubleshoot physical connectivity: 1. Set speed and duplex of both the NIC and switch at 10 Mbps, full−duplex. Is there physical connectivity? I
Résumé du contenu de la page N° 7
This is an example: %PAGP−5−PORTFROMSTP:Port 3/3 left bridge port 3/3 %PAGP−5−PORTTOSTP:Port 3/3 joined bridge port 3/3 • For Cisco IOS Software−based switches, these messages appear for link up/down situations: %LINK−3−UPDOWN: Interface interface, changed state to up %LINK−3−UPDOWN: Interface interface, changed state to down This is an example: %LINK−3−UPDOWN: Interface FastEthernet0/1, changed state to up %LINK−3−UPDOWN: Interface FastEthernet0/1, changed state to down In order to resolve th
Résumé du contenu de la page N° 8
collisions are normal. Generally, a one percent ratio of errors to total traffic is acceptable for half−duplex connections. If the ratio of errors to input packets is greater than two or three percent, performance degradation can be noticed. In half−duplex environments, it is possible for both the switch and the connected device to sense the wire and transmit at exactly the same time and result in a collision. Collisions can cause runts, FCS, and alignment errors, caused when the frame is not co
Résumé du contenu de la page N° 9
64−byte transmit time occurs. They are only detected during transmissions of packets longer than 64 bytes. Its detection is exactly the same as it is for a normal collision; it just happens later than it does for a normal collision. Excessive Excessive collisions are the number of frames that Collisions are dropped after 16 attempts to send the packet resulted in 16 collisions. Carrier Carrier sense occurs every time an Ethernet Sense controller wants to send data and the counter is incremented
Résumé du contenu de la page N° 10
Multiple This is an indication of a half−duplex Collisions configuration. Late Collisions This is an indication of faulty hardware (NIC, cable, or switch port) or a duplex mismatch. Excessive Collisions This is an indication of overutilization of the switch port at half−duplex or duplex mismatch. Carrier Sense This is an indication of faulty hardware (NIC, cable, or switch port). This is an indication of the result of collisions, Runts duplex mismatch, IEEE 802.1Q (dot1q), or an Inter−Switch Lin
Résumé du contenu de la page N° 11
2 In−Discard and Lrn−Discard do not exist on all Catalyst platforms. Table 5 Possible Causes for Incrementing CatOS Counters Counter Possible Cause Delay Exced Severe problem with the switch. Create a service request with Cisco Technical Support. Verify ISL and dot1q configurations. Verify MTU−Exced another switch or router does not inject frame over maximum transmission unit (MTU) into the switch network. Increments when the switch receives traffic on a Lrn−Discard trunk for a specific VLAN wh
Résumé du contenu de la page N° 12
Teaming of Network Interface Cards Teaming of Network Interface Cards, or NIC Teaming, can cause instability in the networks. Such setups can introduce disruptions to the Spanning tree and can make it undergo frequent recomputations. If intermittent loss of connectivity to NIC teamed servers occurs for devices or hosts in the same VLAN, try to disable NIC teaming. If the connectivity stabilizes, refer to the NIC vendor documentation in order to tune the NIC teaming configuration. Additional Trou
Résumé du contenu de la page N° 13
Cisco Catalyst Switch Compatibility and Operation−Specific Issues These sections deal with specific Cisco Catalyst switch issues that can affect performance, compatibility, and interoperation of certain NICs. Catalyst 8510 and 8540 CSR In the campus switch router (CSR) Cisco IOS Software Release 12.0(5)W5(13), autonegotiation for speed and duplex are enabled by default. In earlier releases, autonegotiation is not supported by default. As a result, each connected interface must be set to run in f
Résumé du contenu de la page N° 14
after an autonegotiation failure. registered customers only For detailed information on Cisco bug IDs, refer to the Bug Toolkit ( ) . Refer to Cisco Catalyst 6500 Series Switches Release Notes for more Catalyst 6000 and 6500 documented bug fixes. Catalyst 5000 and 5500 Switches This table lists several known issues found on the Catalyst 5000 and 5500 switches. Table 8 Cisco Bug ID Resolved In Description Directly connected hosts (PCs, routers, and servers) can indicate a connected state in the
Résumé du contenu de la page N° 15
WS−X5225R) can result in speed or duplex mismatches under certain conditions. The problem typically occurs after the module is reset or the switch port is disabled and reenabled. The workaround is to disconnect and reconnect the cable that connects the workstation to the switch port. The 48−port, 10BASE−T Ethernet module (WS−X5012) CSCdk32984 ( incorrectly drops valid registered customers only ) 4.2(2) frames with dribble bits (extra bits added to frames by some end stations and transceivers).
Résumé du contenu de la page N° 16
day to once a month. This issue can reoccur even after the switch is power cycled. The purpose of this Cisco bug ID is to combine several software reworks, fixes that resolve and reduce the loss of connectivity issues, and additional troubleshooting checks in software. An invalid packet with a length of less than 64 bytes received on a CSCdr37645 10/100 port causes both the Runts registered ( and FCS−Error counters to 4.5(8), customers only ) increment on the port. To determine 5.5(2), the act
Résumé du contenu de la page N° 17
Xmit−Err counter increments on CSCds89148 unconnected ports for unexplained registered ( reasons. The bug also resolves an customers only ) 5.5.6, issue of high−CPU utilization 6.2.1 conditions that can be caused by unconnected ports that are configured as host ports. registered customers only For detailed information on Cisco bug IDs, refer to the Bug Toolkit ( ) . Refer to Catalyst 4500 Series Release Notes for more Catalyst 2948G, 2980G, and 4000 documented bug fixes. Catalyst 2950 and 35
Résumé du contenu de la page N° 18
registered customers only For detailed information on Cisco bug IDs, refer to the Bug Toolkit ( ) . NIC Compatibility and Operation Issues Disclaimer: Use this table as a guide in order to troubleshoot NIC issues. Consult the NIC vendor for verification and proper resolution of the issue. Table 11 NIC Model/Manufacture Symptom Description Resolution Intermittently loses Driver versions Apple Macintosh network services earlier than 2.04 can G3 when the built−in experience this issue. Upgrade to
Résumé du contenu de la page N° 19
AsantéFast 10/100 See technical document PCI Adapter Slow login or fails TID1084 at Asanté to log in to server. support website. Numerous CRC and AsantéFast 10/100 FCS errors reported PCI Adapter See technical document on switch when TID1109 at Asanté connected to Power support website. Macintosh 9500. AsantéFast 10/100 Slow network See technical document PCI Adapter throughput after TID1976 at Asanté Macintosh OS 8.5 support website. or 8.6 upgrade. When the energy Turn off the energy sav
Résumé du contenu de la page N° 20
traffic. Despite the proper configuration of 3Com Catalyst switch ports, 3C905/3C905B Intermittent DHCP workstations still issues. Upgrade to driver version experience some 4.01b or later, which intermittent DHCP resolves DHCP issues. issues. Despite the proper configuration of 3Com Unable to log in to Upgrade to driver 4.01b Catalyst switch ports, 3C905/3C905B Novell Internetwork or later, which resolves workstations still Packet Exchange IPX autoframe−type experience (IPX) network. issues. Alt
