Benutzeranleitung / Produktwartung 17053 des Produzenten Cisco Systems
Zur Seite of 27
Troubleshooting Cisco Catalyst Switches to NIC Compatibility Issues Document ID: 17053 Introduction Prerequisites Requirements Components Used Conventions Background Information Purpose Why Do Autoneg.
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.
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.
100 Mbps, Full−duplex 100 Mbps, Full−duplex 100 Mbps, Half−duplex Duplex Mismatch 1 AUTO 100 Mbps, Full−duplex 100 Mbps, Half−duplex 100 Mbps, Full−duplex Duplex Mismatch 1 100 Mbps, Full.
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.
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.
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 .
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.
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.
Multiple Collisions This is an indication of a half−duplex 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.
2 In−Discard and Lrn−Discard do not exist on all Catalyst platforms. Table 5Possible Causes for Incrementing CatOS Counters Counter Possible Cause Delay Exced Severe problem with the switch. Create a service request with Cisco Technical Support.
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.
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.
after an autonegotiation failure. For detailed information on Cisco bug IDs, refer to the Bug Toolkit ( registered customers only ) . Refer to Cisco Catalyst 6500 Series Switches Release Notes for more Catalyst 6000 and 6500 documented bug fixes.
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.
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.
CSCds89148 ( registered customers only ) 5.5.6, 6.2.1 Xmit−Err counter increments on unconnected ports for unexplained reasons. The bug also resolves an issue of high−CPU utilization conditions that can be caused by unconnected ports that are configured as host ports.
For detailed information on Cisco bug IDs, refer to the Bug Toolkit ( registered customers only ) . 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.
AsantéFast 10/100 PCI Adapter Slow login or fails to log in to server. See technical document TID1084 at Asanté support website. AsantéFast 10/100 PCI Adapter Numerous CRC and FCS errors reported on switch when connected to Power Macintosh 9500.
traffic. 3Com 3C905/3C905B Intermittent DHCP issues. Despite the proper configuration of Catalyst switch ports, workstations still experience some intermittent DHCP issues. Upgrade to driver version 4.01b or later, which resolves DHCP issues. 3Com 3C905/3C905B Unable to log in to Novell Internetwork Packet Exchange (IPX) network.
1.0.33921641.2241835. 3Com 3C985/3C985B Novell 5.0 issues Refer to 3Com technical support reference 1.0.16744826.2027011. 3Com 3C985/3C985B Clients are unable to log in or browse server, but pings work correctly. Refer to 3Com technical support reference 2.
fails. The motherboards were manufactured with an Intel Chipset that are incompatible with Cisco switches and Netgear hubs. IBM 10/100 EtherJet CardBus Adapter Extremely slow performance when operating at 10 Mbps.
can see poor network connections or excessive numbers of dropped packets. The interoperability issue arises when a module with a ten bit interface (TBI) transmits an odd byte packet to a receiver with a Gigabit media−independent interface (GMII). Carrier Extension is detailed in subsection 35.
type keyword can be set to Auto Detect or 10BASE−T/100BaseTX. The related port on the attached hub or switch must also be set to 10Mbps, full−duplex. Xircom RealPort2 CardBus Ethernet 10/100 Adapter (R2BE/RBE/CBE) Models Extremely slow performance when operating at 10 Mbps.
manufacturer patches and utility software are installed. Xircom XE2000 PCMCIA NIC Does not autonegotiate to 100 Mbps, full−duplex. NIC only autonegotiates to 100 Mbps, half−duplex. Known limitation of XE2000 NIC. Refer to the XE2000 release notes.
0.14 Loopback 1 = loopback mode switched on 0 = loopback mode switched off 0.13 Rate Selection (least−significant bit [LSB]) 0.6 0.13 1 1 reserved 1 0 1000 Mbps 0 1 100 Mbps 0 0 10 Mbps 0.12 Autonegotiation Enable 1 = autonegotiaton enabled 0 = autonegotiation disabled 0.
partner and defaults to half−duplex. As described in Appendix B: Understanding How Autonegotiation Works, pulses within the FLP are used to derive code words that exchange link partner capabilities. The first code word exchanged is referred to as the base page.
Ein wichtiger Punkt beim Kauf des Geräts Cisco Systems 17053 (oder sogar vor seinem Kauf) ist das durchlesen seiner Bedienungsanleitung. Dies sollten wir wegen ein paar einfacher Gründe machen:
Wenn Sie Cisco Systems 17053 noch nicht gekauft haben, ist jetzt ein guter Moment, um sich mit den grundliegenden Daten des Produkts bekannt zu machen. Schauen Sie zuerst die ersten Seiten der Anleitung durch, die Sie oben finden. Dort finden Sie die wichtigsten technischen Daten für Cisco Systems 17053 - auf diese Weise prüfen Sie, ob das Gerät Ihren Wünschen entspricht. Wenn Sie tiefer in die Benutzeranleitung von Cisco Systems 17053 reinschauen, lernen Sie alle zugänglichen Produktfunktionen kennen, sowie erhalten Informationen über die Nutzung. Die Informationen, die Sie über Cisco Systems 17053 erhalten, werden Ihnen bestimmt bei der Kaufentscheidung helfen.
Wenn Sie aber schon Cisco Systems 17053 besitzen, und noch keine Gelegenheit dazu hatten, die Bedienungsanleitung zu lesen, sollten Sie es aufgrund der oben beschriebenen Gründe machen. Sie erfahren dann, ob Sie die zugänglichen Funktionen richtig genutzt haben, aber auch, ob Sie keine Fehler begangen haben, die den Nutzungszeitraum von Cisco Systems 17053 verkürzen könnten.
Jedoch ist die eine der wichtigsten Rollen, die eine Bedienungsanleitung für den Nutzer spielt, die Hilfe bei der Lösung von Problemen mit Cisco Systems 17053. Sie finden dort fast immer Troubleshooting, also die am häufigsten auftauchenden Störungen und Mängel bei Cisco Systems 17053 gemeinsam mit Hinweisen bezüglich der Arten ihrer Lösung. Sogar wenn es Ihnen nicht gelingen sollte das Problem alleine zu bewältigen, die Anleitung zeigt Ihnen die weitere Vorgehensweise – den Kontakt zur Kundenberatung oder dem naheliegenden Service.
