Ir a la página of
manuales de instrucciones parecidos
-
Switch
Cisco Systems 2950-24
15 páginas 0.27 mb -
Switch
Cisco Systems MGX 8220
312 páginas 2.88 mb -
Switch
Cisco Systems 3130
1226 páginas 14.43 mb -
Switch
Cisco Systems WSC2960X48TSL
112 páginas 3.1 mb -
Switch
Cisco Systems MCS 7800 Series
156 páginas 2.15 mb -
Switch
Cisco Systems SR224
2 páginas 3 mb -
Switch
Cisco Systems 2975
16 páginas 1.92 mb -
Switch
Cisco Systems WSC4500XF32SFP
194 páginas 7.47 mb
Buen manual de instrucciones
Las leyes obligan al vendedor a entregarle al comprador, junto con el producto, el manual de instrucciones Cisco Systems 17053. La falta del manual o facilitar información incorrecta al consumidor constituyen una base de reclamación por no estar de acuerdo el producto con el contrato. Según la ley, está permitido adjuntar un manual de otra forma que no sea en papel, lo cual últimamente es bastante común y los fabricantes nos facilitan un manual gráfico, su versión electrónica Cisco Systems 17053 o vídeos de instrucciones para usuarios. La condición es que tenga una forma legible y entendible.
¿Qué es un manual de instrucciones?
El nombre proviene de la palabra latina “instructio”, es decir, ordenar. Por lo tanto, en un manual Cisco Systems 17053 se puede encontrar la descripción de las etapas de actuación. El propósito de un manual es enseñar, facilitar el encendido o el uso de un dispositivo o la realización de acciones concretas. Un manual de instrucciones también es una fuente de información acerca de un objeto o un servicio, es una pista.
Desafortunadamente pocos usuarios destinan su tiempo a leer manuales Cisco Systems 17053, sin embargo, un buen manual nos permite, no solo conocer una cantidad de funcionalidades adicionales del dispositivo comprado, sino también evitar la mayoría de fallos.
Entonces, ¿qué debe contener el manual de instrucciones perfecto?
Sobre todo, un manual de instrucciones Cisco Systems 17053 debe contener:
- información acerca de las especificaciones técnicas del dispositivo Cisco Systems 17053
- nombre de fabricante y año de fabricación del dispositivo Cisco Systems 17053
- condiciones de uso, configuración y mantenimiento del dispositivo Cisco Systems 17053
- marcas de seguridad y certificados que confirmen su concordancia con determinadas normativas
¿Por qué no leemos los manuales de instrucciones?
Normalmente es por la falta de tiempo y seguridad acerca de las funcionalidades determinadas de los dispositivos comprados. Desafortunadamente la conexión y el encendido de Cisco Systems 17053 no es suficiente. El manual de instrucciones siempre contiene una serie de indicaciones acerca de determinadas funcionalidades, normas de seguridad, consejos de mantenimiento (incluso qué productos usar), fallos eventuales de Cisco Systems 17053 y maneras de solucionar los problemas que puedan ocurrir durante su uso. Al final, en un manual se pueden encontrar los detalles de servicio técnico Cisco Systems en caso de que las soluciones propuestas no hayan funcionado. Actualmente gozan de éxito manuales de instrucciones en forma de animaciones interesantes o vídeo manuales que llegan al usuario mucho mejor que en forma de un folleto. Este tipo de manual ayuda a que el usuario vea el vídeo entero sin saltarse las especificaciones y las descripciones técnicas complicadas de Cisco Systems 17053, como se suele hacer teniendo una versión en papel.
¿Por qué vale la pena leer los manuales de instrucciones?
Sobre todo es en ellos donde encontraremos las respuestas acerca de la construcción, las posibilidades del dispositivo Cisco Systems 17053, el uso de determinados accesorios y una serie de informaciones que permiten aprovechar completamente sus funciones y comodidades.
Tras una compra exitosa de un equipo o un dispositivo, vale la pena dedicar un momento para familiarizarse con cada parte del manual Cisco Systems 17053. Actualmente se preparan y traducen con dedicación, para que no solo sean comprensibles para los usuarios, sino que también cumplan su función básica de información y ayuda.
Índice de manuales de instrucciones
-
Página 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 [...]
-
Página 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 [...]
-
Página 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 1Autonegotiation Val[...]
-
Página 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,[...]
-
Página 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[...]
-
Página 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[...]
-
Página 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[...]
-
Página 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[...]
-
Página 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[...]
-
Página 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[...]
-
Página 11
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. MTU−Exced Verify ISL and dot1q configurations. Verify another switch or router does not inject [...]
-
Página 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[...]
-
Página 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[...]
-
Página 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[...]
-
Página 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, [...]
-
Página 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[...]
-
Página 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[...]
-
Página 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[...]
-
Página 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[...]
-
Página 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[...]
-
Página 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[...]
-
Página 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[...]
-
Página 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[...]
-
Página 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[...]
-
Página 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[...]
-
Página 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[...]
-
Página 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[...]