Class 1 laser product.
Connecting GBICs to the Gigabit Ethernet and Gigabit EtherChannel Ports
To connect GBICs to the Gigabit Ethernet or Gigabit EtherChannel ports, perform these steps:
Step 1 Remove the plugs from the GBIC optical bores; store them for future use.
Step 2 Remove the plugs from the SC connector (see Figure 10) on the fiber-optic cable. Insert the connector into the GBIC.
Note When you plug the SC connector into the GBIC, make sure that both the tx
(transmit) and rx (receive) fiber-optic cables are fully inserted into the SC connector.
Note If you are using the LX/LH GBIC with MMF, you need to install a patch cord
between the GBIC and the MMF cable. See the
"Mode-Conditioning Patch
Cord" section for details.
Do not remove the plugs from the GBIC optical bores or the fiber-optic cable until you are ready to connect the cable. The plugs protect the GBIC optical bores and cable from contamination.
Figure 10 SC Connector
Removing GBICs
To remove a GBIC, perform these steps:
Step 1 Disconnect the fiber-optic cable from the GBIC SC-type connector.
Step 2 Release the GBIC from the slot by simultaneously squeezing the plastic tabs (see Figure 11).
Figure 11 Removing a GBIC in a Gigabit Ethernet Switching Module
Step 3 Slide the GBIC out of the slot.
Step 4 Install the plugs in the GBIC optical bores, and place the GBIC in protective packaging.
Mode-Conditioning Patch Cord
When using the 1000BaseLX/LH GBIC with 62.5-micron diameter MMF, you must install a mode-conditioning patch cord (Cisco product number CAB-GELX-625 or equivalent) between the GBIC and the MMF cable on both the transmit and receive ends of the link. The patch cord is required for link distances greater than 984 feet (300 meters).
Note For link spans of less than 300 meters, the patch cord can be omitted; however, using the
LX/LH GBIC with MMF and no patch cord for very short link distances (tens of meters) is not
recommended. The result could be an elevated bit error rate (BER).
Note The patch cord is required to comply with IEEE standards. The IEEE found that link
distances could not be met with certain types of fiber-optic cable due to a problem in the center of
some fiber-optic cable cores. The solution is to launch light from the laser at a precise offset from
the center by using the patch cord. At the output of the patch cord, the LX/LH GBIC is compliant
with the IEEE 802.3z standard for 1000BaseLX. For a detailed description of this problem, refer to
Appendix C, "Differential Mode Delay," in the Catalyst 5000 Series Supervisor Engine Installation
Guide.
Note Cisco Gigabit Ethernet products have been tested and evaluated to comply with the standards
listed in the "Standards Compliance"
section. Equivalent cables should also meet these standards.
Patch Cord Configuration Example
Figure 12 shows a typical configuration using the patch cord.
Figure 12 Patch Cord Configuration
Installing the Patch Cord
Plug the end of the patch cord labeled "To Equipment" into the GBIC (see Figure 13). Plug the end labeled "To Cable Plant" into the patch panel. The patch cord is 9.84 feet (3 meters) long and has duplex SC-male connectors at each end.
Figure 13 Patch Cord Installation
Checking the Interface Status
Check the status of the interfaces as follows:
- Ensure that the Status LED cycles from orange to green when you apply power to the module.
- If you perform a hot swap, the console displays the message "Module n has been inserted." This message also appears if you are connected to the Catalyst 5000 series switch through a Telnet session.
- If this installation is for a replacement switching module, enter the show module or show port [mod_num/port_num] command to verify that the system has acknowledged the new interfaces and brought them up.
Configuring Gigabit Ethernet and Gigabit EtherChannel Switching Modules
This section lists the default configurations of the Gigabit Ethernet and Gigabit EtherChannel switching modules and the commands you can use to customize your configuration.
Default Configuration
The features you can customize have default values that are likely to suit your environment and need not be changed. Table 8 lists the default values of these features.
Table 8 Default Values
| Feature
|
Default Setting
|
Port enable state
|
All ports are enabled1
|
Port name
|
None
|
Port priority
|
Normal
|
Port duplex setting
|
Full duplex2
|
Native VLAN
|
VLAN 1
|
Spanning-Tree Protocol
|
Enabled for VLAN 1
|
Spanning-tree port-VLAN cost
|
4
|
Spanning-tree port-VLAN priority
|
32
|
Gigabit EtherChannel3
|
Disabled
|
| Port availability for the Gigabit Ethernet module depends on which Catalyst 5000 series switch the module is installed in and in which slot the module is installed.
Gigabit Ethernet module ports can operate only in full duplex.
Gigabit EtherChannel is not supported on the WS-X5403.
|
Configuring the Ports
Table 9 lists the tasks and commands to configure the Gigabit Ethernet and Gigabit EtherChannel module ports.
Table 9 Quick Configuration
| Task
|
Command
|
| Setting Up the System
|
|
|
set port name mod_num/port_num [name_string]
|
- Setting the port priority level
|
set port level mod_num/port_num {normal | high}
|
- Verify the port configuration
|
show port mod_num/port_num
|
| Checking Connectivity
|
- Send an echo request from the Catalyst 5000 series switch to the host.
|
ping host
|
- If the host is unresponsive, check the configuration for the IP address of the Catalyst 5000 series switch and default IP route, if appropriate.
|
show interface
show ip route
|
Configuring Flow Control on the Gigabit Ethernet Switching Module (WS-X5403)
The Gigabit Ethernet switching modules use flow control, which inhibits packet transmission to the Gigabit Ethernet module for a period of time. If the Gigabit Ethernet switching module's receive buffer becomes full, the module transmits a "pause" packet that tells remote devices to delay sending more packets for a specified period of time. The Gigabit Ethernet switching module can also receive "pause" packets from other devices.
To configure flow control, enter the set port flowcontrol {receive | send} mod_num/port_num {off | on | desired} command. Table 10 lists the flow-control tasks and commands.
Table 10 Gigabit Ethernet set port flowcontrol Commands
| Task
|
Command
|
Causes the local port to send flow-control packets to a remote device.
|
set port flowcontrol send mod_num/port_num on
|
Causes the local port to send flow-control packets if a remote device wants them (default).
|
set port flowcontrol send mod_num/port_num desired
|
Turns off a local port's ability to send flow- control packets to a remote device.
|
set port flowcontrol send mod_num/port_num off
|
Requires a local port to be flow controlled by a remote device.
|
set port flowcontrol receive mod_num/port_num on
|
Causes the local port to operate with an attached device that is required to send flow-control packets or with an attached device that is not required to but may send flow-control packets.
|
set port flowcontrol receive mod_num/port_num desired
|
Turns off an attached device's ability to send flow-control packets to a local port (default).
|
set port flowcontrol receive mod_num/port_num off
|
This example shows how to turn on transmit flow control:
Console> (enable)
set port flowcontrol send 3/1 on
Port 3/1 will send flowcontrol to far end.
This example shows how to set transmit flow control to advertise that it will send flow-control frames if the attached device elects to receive them:
Console> (enable)
set port flowcontrol send 3/1 desired
Port 3/1 will send flowcontrol to far end if far end supports it
This example shows how to turn off transmit flow control:
Console> (enable)
set port flowcontrol send 3/1 off
Port 3/1 will not send flowcontrol to far end
This example shows how to turn on receive flow control:
Console> (enable)
set port flowcontrol receive 3/1 on
Port 3/1 will require far end to send flowcontrol
This example shows how to set receive flow control to advertise that it will accept flow-control frames if the attached device elects to transmit them:
Console> (enable)
set port flowcontrol receive 3/1 desired
Port 3/1 will allow far end to send flowcontrol
This example shows how to turn off receive flow control:
Console> (enable)
set port flowcontrol receive 3/1 off
Port 3/1 will not allow far end to send flowcontrol
To display the current flow-control status and statistics, perform this task:
| Task
|
Command
|
Display the current flow-control status and statistics.
|
show port flowcontrol
|
This example shows how to verify the flow-control configuration:
Console>
show port flowcontrol
Port Send Flowcontrol Receive Flowcntl RxPause TxPause
----- ----------------- ----------------- ------- -------
3/1 on disagree on disagree 0 0
3/3 desired off desired off 10 10
Table 11 shows output field descriptions for the show port flowcontrol command:
Table 11 Output Field Descriptions
| Field
|
Description
|
Port
|
Module and port number.
|
Send-Flowcontrol- Admin
|
Flow-control administrative state. Possible settings: on indicates the local port sends flow control to the far end; off indicates the local port does not send flow control to the far end; desired indicates the local end sends flow control to the far end if the far end supports it.
|
Send-Flowcontrol- Oper
|
Flow-control operation. Possible indications: disagree indicates the two ports could not agree on a link protocol.
|
Receive-Flowcntl- Admin
|
Flow-control administrative state. Possible settings: on indicates the local port requires the far end to send flow control; off indicates the local port does not allow the far end to send flow control; desired indicates the local end allows the far end to send flow control.
|
Receive-Flowcntl- Oper
|
Flow-control operation. Possible indications: disagree indicates the two ports could not agree on a link protocol.
|
RxPause
|
Count of pause frames received.
|
TxPause
|
Count of pause frames transmitted.
|
Configuring Flow Control on the Gigabit EtherChannel Switching Module (WS-X5410)
Ports can be characterized by their ability to generate and respond to flow control frames (pause frames) as well as the pause behavior they require of their link partner.
The Gigabit EtherChannel module's Gigabit Ethernet ports respond to received pause frames. Upon configuration, these ports advertise a pause capability. The ports at the two ends of the link negotiate a mutually acceptable flow-control configuration.
A pause frame is never generated by the Gigabit EtherChannel module's Gigabit Ethernet ports.
In all cases, pause frames received on the module are processed internally and are not switched through the system.
To configure flow-control, enter the set port flowcontrol {receive | send} [mod_num/port_num] {off | on | desired} command. Table 12 lists the flow-control tasks and commands.
Table 12 Gigabit EtherChannel set port flowcontrol Commands
| Task
|
Command
|
Causes the local port to advertise that it will send flow-control frames1.
|
set port flowcontrol send mod_num/port_num on
|
Causes the local port to advertise that it will send flow-control frames if the attached device elects to receive them1 (default).
|
set port flowcontrol send mod_num/port_num desired
|
Turns off a local port's ability to send flow-control packets to a remote device.
|
set port flowcontrol send mod_num/port_num off
|
Requires a local port to be flow controlled by a remote device.
|
set port flowcontrol receive mod_num/port_num on
|
Causes the local port to operate with an attached device that is required to send flow-control packets or with an attached device that is not required to but may send flow-control packets.
|
set port flowcontrol receive mod_num/port_num desired
|
Turns off an attached device's ability to send flow-control packets to a local port (default).
|
set port flowcontrol receive mod_num/port_num off
|
| Even though the GEM never sends flow-control frames, this configuration option is useful if the attached device refuses to complete negotiation unless the local device advertises that it will send flow-control frames. For cases where the attached device is willing to accept flow-control frames, there is no adverse effect in advertising to that attached device that the local device intends to send them.
|
This example shows how to turn transmit flow control on:
Console> (enable)
set port flowcontrol send 5/1 on
Port 5/1 flow control send administration status set to on
(port will send flowcontrol to far end)
This example shows how to set transmit flow control to advertise that it will send flow-control frames if the attached device elects to receive them:
Console> (enable)
set port flowcontrol send 5/1 desired
Port 5/1 flow control send administration status set to desired
(port will send flowcontrol to far end if far end supports it)
This example shows how to turn transmit flow control off:
Console> (enable)
set port flowcontrol send 5/1 off
Port 5/1 flow control send administration status set to off
(port will not send flowcontrol to far end)
This example shows how to turn receive flow control on:
Console> (enable)
set port flowcontrol receive 5/1 on
Port 5/1 flow control receive administration status set to on
(port will require far end to send flowcontrol)
This example shows how to set receive flow control to advertise that it will accept flow-control frames if the attached device elects to transmit them:
Console> (enable)
set port flowcontrol receive 5/1 desired
Port 5/1 flow control receive administration status set to desired
(port will allow far end to send flowcontrol if far end supports it)
This example shows how to turn off receive flow control:
Console> (enable)
set port flowcontrol receive 5/1 off
Port 5/1 flow control receive administration status set to off
(port will not allow far end to send flowcontrol)
To display the current flow-control status and statistics, perform this task:
| Task
|
Command
|
Display the current flow-control status and statistics.
|
show port flowcontrol
|
This example shows how to verify the flow-control configuration:
Console> (enable)
show port flowcontrol
Port Send FlowControl Receive FlowControl RxPause TxPause Unsupported
admin oper admin oper opcodes
----- -------- -------- -------- -------- ------- ------- -----------
5/1 desired off off off 0 0 0
5/2 desired off off off 0 0 0
5/3 desired off off off 0 0 0
Table 13 shows the Output field descriptions for the show port flowcontrol command.
Table 13 Output Field Descriptions
| Field
|
Description
|
Port
|
Module and port number.
|
Send-Flowcontrol- Admin
|
Flow-control administrative state. Possible settings: on indicates the local port sends flow control to the far end; off indicates the local port does not send flow control to the far end; desired indicates the local end sends flow control to the far end if the far end supports it.
|
Send-Flowcontrol- Oper
|
Flow-control operation. Possible indications: disagree indicates the two ports could not agree on a link protocol.
|
Receive-Flowcntl- Admin
|
Flow-control administrative state. Possible settings: on indicates the local port requires the far end to send flow control; off indicates the local port does not allow the far end to send flow control; desired indicates the local end allows the far end to send flow control.
|
Receive-Flowcntl- Oper
|
Flow-control operation. Possible indications: disagree indicates the two ports could not agree on a link protocol.
|
RxPause
|
Count of pause frames received.
|
TxPause
|
Count of pause frames transmitted.
|
Unsupported opcodes
|
Count of pause frames with unsupported opcodes. These are frames with a valid destination address (01:80:c2:00:00:01) and a valid Ethernet type (0x8808) but an invalid opcode. Currently we recognize pause frames with an opcode of 1 (Xoff). All others are unsupported. Note that all frames received at this multicast address are discarded by the bridge.
|
Configuring Port Negotiation on the Gigabit EtherChannel Switching Module (WS-X5410)
Autonegotiation with Gigabit Ethernet behaves differently than autonegotiation with Ethernet or Fast Ethernet. To avoid link configuration problems, we recommend that you read and understand the information in this section and the information in the "Configuring Flow Control on the Gigabit Ethernet Switching Module (WS-X5403)" section.
Unlike 10/100 Fast Ethernet ports, autonegotiation with Gigabit Ethernet does not involve negotiating port speed. You cannot disable autonegotiation on Gigabit Ethernet ports by setting the port speed and duplex state. With Gigabit Ethernet, the link negotiation protocol is used to exchange flow-control behavior, remote fault information, and duplex information (even though the Catalyst 5000 series gigabit ports only support full-duplex operation). In Gigabit Ethernet, you can control whether the link negotiation protocol runs with the set port negotiation command.
Table 14 shows the four possible autonegotiation configurations for a link and the resulting link status for each configuration.
Table 14 Configuring Autonegotiation on Gigabit Ethernet Links
| Autonegotiation State
|
Link Status
|
| Near End1
|
Far End2
|
Near End
|
Far End
|
Off
|
Off
|
Up
|
Up
|
Off
|
On
|
Up
|
Down
|
On
|
Off
|
Down
|
Up
|
On
|
On
|
Up
|
Up
|
| Refers to the GEM's front panel port.
Refers to the remote port at the other end of the gigabit link.
|
Both ends of the link must have the same setting. The link will not come up if the two ends of the link are set inconsistently (link negotiation enabled on one end and disabled on the other).
The link negotiation protocol is enabled by default. To enable or disable the link negotiation protocol on a port, perform this task:
| Task
|
Command
|
Enable or disable link negotiation protocol.
|
set port negotiation mod_num/port_num {enable | disable}
|
This example shows how to turn link negotiation off:
Console> (enable)
set port negotiation 5/1 disable
Port 5/1 negotiation disabled.
To display the link negotiation protocol setting for the specified port, perform this task:
| Task
|
Command
|
Display the link negotiation protocol setting.
|
show port negotiation [mod_num/port_num]
|
This example shows how to verify the link negotiation configuration:
Console> (enable)
show port negotiation 5/1
------- --------------------
FCC Class A Compliance
This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to part 15 of the FCC rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment. This equipment generates, uses, and can radiate radio-frequency energy and, if not installed and used in accordance with the instruction manual, may cause harmful interference to radio communications. Operation of this equipment in a residential area is likely to cause harmful interference, in which case users will be required to correct the interference at their own expense.
You can determine whether your equipment is causing interference by turning it off. If the interference stops, it was probably caused by the Cisco equipment or one of its peripheral devices. If the equipment causes interference to radio or television reception, try to correct the interference by using one or more of the following measures:
- Turn the television or radio antenna until the interference stops.
- Move the equipment to one side or the other of the television or radio.
- Move the equipment farther away from the television or radio.
- Plug the equipment into an outlet that is on a different circuit from the television or radio. (That is, make certain the equipment and the television or radio are on circuits controlled by different circuit breakers or fuses.)
Modifications to this product not authorized by Cisco Systems could void the FCC approval and negate your authority to operate the product.
Cisco Connection Online
Cisco Connection Online (CCO) is Cisco Systems' primary, real-time support channel. Maintenance customers and partners can self-register on CCO to obtain additional information and services.
Available 24 hours a day, 7 days a week, CCO provides a wealth of standard and value-added services to Cisco's customers and business partners. CCO services include product information, product documentation, software updates, release notes, technical tips, the Bug Navigator, configuration notes, brochures, descriptions of service offerings, and download access to public and authorized files.
CCO serves a wide variety of users through two interfaces that are updated and enhanced simultaneously: a character-based version and a multimedia version that resides on the World Wide Web (WWW). The character-based CCO supports Zmodem, Kermit, Xmodem, FTP, and Internet e-mail, and it is excellent for quick access to information over lower bandwidths. The WWW version of CCO provides richly formatted documents with photographs, figures, graphics, and video, as well as hyperlinks to related information.
You can access CCO in the following ways:
For a copy of CCO's Frequently Asked Questions (FAQ), contact cco-help@cisco.com. For additional information, contact cco-team@cisco.com.
Note If you are a network administrator and need personal technical assistance with a Cisco
product that is under warranty or covered by a maintenance contract, contact Cisco's Technical
Assistance Center (TAC) at 800 553-2447, 408 526-7209, or tac@cisco.com. To obtain general
information about Cisco Systems, Cisco products, or upgrades, contact 800 553-6387,
408 526-7208, or cs-rep@cisco.com.
Documentation CD-ROM
Cisco documentation and additional literature are available in a CD-ROM package, which ships with your product. The Documentation CD-ROM, a member of the Cisco Connection Family, is updated monthly. Therefore, it might be more current than printed documentation. To order additional copies of the Documentation CD-ROM, contact your local sales representative or call customer service. The CD-ROM package is available as a single package or as an annual subscription. You can also access Cisco documentation on the World Wide Web at http://www.cisco.com, http://www-china.cisco.com, or http://www-europe.cisco.com.
If you are reading Cisco product documentation on the World Wide Web, you can submit comments electronically. Click Feedback in the toolbar and select Documentation. After you complete the form, click Submit to send it to Cisco. We appreciate your comments.
|