Cisco Systems 17053 manual

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27

Go to page of

A good user manual

The rules should oblige the seller to give the purchaser an operating instrucion of Cisco Systems 17053, along with an item. The lack of an instruction or false information given to customer shall constitute grounds to apply for a complaint because of nonconformity of goods with the contract. In accordance with the law, a customer can receive an instruction in non-paper form; lately graphic and electronic forms of the manuals, as well as instructional videos have been majorly used. A necessary precondition for this is the unmistakable, legible character of an instruction.

What is an instruction?

The term originates from the Latin word „instructio”, which means organizing. Therefore, in an instruction of Cisco Systems 17053 one could find a process description. An instruction's purpose is to teach, to ease the start-up and an item's use or performance of certain activities. An instruction is a compilation of information about an item/a service, it is a clue.

Unfortunately, only a few customers devote their time to read an instruction of Cisco Systems 17053. A good user manual introduces us to a number of additional functionalities of the purchased item, and also helps us to avoid the formation of most of the defects.

What should a perfect user manual contain?

First and foremost, an user manual of Cisco Systems 17053 should contain:
- informations concerning technical data of Cisco Systems 17053
- name of the manufacturer and a year of construction of the Cisco Systems 17053 item
- rules of operation, control and maintenance of the Cisco Systems 17053 item
- safety signs and mark certificates which confirm compatibility with appropriate standards

Why don't we read the manuals?

Usually it results from the lack of time and certainty about functionalities of purchased items. Unfortunately, networking and start-up of Cisco Systems 17053 alone are not enough. An instruction contains a number of clues concerning respective functionalities, safety rules, maintenance methods (what means should be used), eventual defects of Cisco Systems 17053, and methods of problem resolution. Eventually, when one still can't find the answer to his problems, he will be directed to the Cisco Systems service. Lately animated manuals and instructional videos are quite popular among customers. These kinds of user manuals are effective; they assure that a customer will familiarize himself with the whole material, and won't skip complicated, technical information of Cisco Systems 17053.

Why one should read the manuals?

It is mostly in the manuals where we will find the details concerning construction and possibility of the Cisco Systems 17053 item, and its use of respective accessory, as well as information concerning all the functions and facilities.

After a successful purchase of an item one should find a moment and get to know with every part of an instruction. Currently the manuals are carefully prearranged and translated, so they could be fully understood by its users. The manuals will serve as an informational aid.

Table of contents for the manual

  • Page 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 [...]

  • Page 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 [...]

  • Page 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 Val[...]

  • Page 4

    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−duplex 100 Mbps, Full−duplex 100 Mbps, Full−duplex 100 Mbps, Full−duplex Correct Manual Configuration 2 100 Mbps, Half−duplex AUTO 100 Mbps,[...]

  • Page 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 th[...]

  • Page 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 i[...]

  • Page 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[...]

  • Page 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 wi[...]

  • Page 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 Collisions Excessive collisions are the number of frames that are dropped after 16 attempts to send the p[...]

  • Page 10

    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. Carrier Sense This is an indication of faulty ha[...]

  • Page 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. MTU−Exced Verify ISL and dot1q configurations. Verify another switch or router does not inject [...]

  • Page 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 disa[...]

  • Page 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[...]

  • Page 14

    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. Catalyst 5000 and 5500 Switches This table lists several known issues found on the Catalyst 5000 and 55[...]

  • Page 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. CSCdk32984 ( registered customers only ) 4.2(2) The 48−port, [...]

  • Page 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. CSCdr37645 ( registered customers only ) 4.5(8), 5.5(2), 6.1(1) An invalid packe[...]

  • Page 17

    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 ( registe[...]

  • Page 18

    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. Table 11 NIC Model/Manufacture Symptom Description Resoluti[...]

  • Page 19

    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.  See technical document TID1109 at Asanté support website. AsantéFast 10/100 PCI Adapter Slo[...]

  • Page 20

    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. Despite the proper[...]

  • Page 21

    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.0.4428387.2305072. 3Com 3C985/3C985B Packets larger than Ethernet MTU (1518 bytes) are ge[...]

  • Page 22

    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. Certain 10/100 switches implement automatic correction for polarity−reversed cables that are not completely compatible with the same c[...]

  • Page 23

    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.2.3.5 in the IEEE 802.3 specification. Carrier Extensi[...]

  • Page 24

    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. Certain 10/100 switches implement automatic correction for polarity−r[...]

  • Page 25

    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. Appendix A: Information to Gather Before Creating a Service Request If the troubleshooting procedu[...]

  • Page 26

    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.11 Power Down 1 = power down 0 = normal down 0.10 Isolated 1 = PHY electrica[...]

  • Page 27

    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. It informs each link partner of the message type, IEEE 802.3 or IEEE 802.9a, and a tec[...]