1. Manuals
  2. Brands
  3. Computer Equipment
  4. Switch
  5. IBM
  6. Computer Equipment
  7. Switch

IBM 12.1(22)EA6 Preventing Autonegotiation Mismatches, SFP Module Security and Identification, Diagnosing Connectivity Problems

1 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494 550
Download on canonical page 550 pages, 5.74 Mb
25-7
Cisco Systems IntelligentGigabit Ethernet Switch Modules for the IBM BladeCenter, Software Configuration Guide
24R9746
Chapter25 Troubleshooting
Preventing Autonegotiation Mismatches
Preventing Autonegotiation Mismatches
The IEEE 802.3ab autonegotiation protocol manages the switch settings for speed (10 Mbps, 10 0 Mbps,
and 1000 Mbps) and duplex (half or full). There are situations when this protocol can incorrectly align
these settings, reducing performance. A mismatch occurs under these circumstances:
A manually set speed or duplex parameter is different from the manually set speed or duplex
parameter on the connected port.
A port is set to autonegotiate, and the connected port is set to full duplex with no autonegotiation.
To maximize switch performance and ensure a link, follow one of these guidelines when changing the
settings for duplex and speed:
Let both ports autonegotiate both speed and duplex.
Manually set the speed and duplex parameters for the ports on both ends of the connection.
Note If a remote device does not autonegotiate, configure the duplex settings on the two ports to match. The
speed parameter can adjust itself even if the connected port does not autonegotiate.
SFP Module Security and Identification
Small form-factor pluggable (SFP) modules have a serial EEPROM that contains the module serial
number, the vendor name and ID, a unique security code, and cyclic redundancy check (CRC). When an
SFP module is inserted in the switch, the switch software reads the EEPROM to check the serial number,
vendor name and vendor ID, and recompute the security code and CRC. If the serial number, the vendor
name or vendor ID, the security code, or CRC is invalid, the switch places the interface in an
error-disabled state.
Note If you are using a non-Cisco SFP module, remove the SFP module from the switch, and replace it with
a Cisco module.
After inserting a Cisco SFP module, use the errdisable recovery cause gbic-invalid global
configuration command to verify the port status, and enter a time interval for recovering from the
error-disabled state. After the elapsed interval, the switch brings the interface out of the error-disabled
state and retries the operation. For more information about the errdisable recovery command, see the
command reference for this release.
Diagnosing Connectivity Problems
This section describes how to troubleshoot connectivity problems:
Using Ping, page 25-8
Using Layer 2 Traceroute, page 25-9
MENU

Models

Contents