Filter
Top Products
Setting Ethernet Port Parameters Configuring Ethernet Ports
page 1-22 OmniSwitch 6600 Family Network Configuration Guide April 2006
Configuring Auto Negotiation, Crossover, and Flow Control
Settings
The following subsections describe how to enable and disable auto negotiation (see “Enabling and
Disabling Auto Negotiation” on page 1-22), configuring crossover settings (see “Configuring Crossover
Settings” on page 1-23), and configuring flow control (see “Enabling and Disabling Flow” on page 1-23).
Enabling and Disabling Auto Negotiation
By default, auto negotiation is enabled. To enable or disable auto negotiation on a single port, a range of
ports, or an entire slot use the interfaces autoneg command. (See “Configuring Crossover Settings” on
page 1-23 and “Enabling and Disabling Flow” on page 1-23 for more information).
To enable or disable auto negotiation on an entire switch enter interfaces followed by the slot number,
autoneg, and either enable or disable. For example, to enable auto negotiation on slot 2 enter:
-> interfaces 2 autoneg enable
To enable or disable auto negotiation on a single port enter interfaces followed by the slot number, a slash
(/), the port number, autoneg, and either enable or disable. For example, to enable auto negotiation on
port 3 on slot 2 enter:
-> interfaces 2/3 autoneg enable
To enable or disable auto negotiation on a range of ports enter interfaces followed by the slot number, a
slash (/), the first port number, a hyphen (-), the last port number, autoneg, and either enable or disable.
For example, to enable auto negotiation on ports 1 through 3 on slot 2 enter:
-> interfaces 2/1-3 autoneg enable
As an option, you can document the interface type by entering ethernet, fastethernet, or gigaethernet
before the slot number. For example, to enable auto negotiation on port 3 on slot 2 and document the port
as Ethernet enter:
-> interfaces ethernet 2/3 autoneg enable
Please note a link will not be established on any copper Ethernet port if any one of the following is true:
• The local port advertises 100 Mbps full duplex and the remote link partner is forced to 100 Mbps full
duplex.
• The local port advertises 100 Mbps full duplex and the remote link partner is forced to 100 Mbps half
duplex.
• The local port advertises 10 Mbps full duplex and the remote link partner is forced to 10 Mbps full
duplex.
• The local port advertises 10 Mbps full duplex and the remote link partner is forced to 10 half duplex.
This is due to the fact that when the local device is set to auto negotiating 10/100 full duplex it senses the
remote device is not auto negotiating. Therefore it resolves to Parallel Detect with Highest Common
Denominator (HCD), which is “10/100 Half” according to IEEE 802.3 Clause 28.2.3.1.
However, since the local device is set to auto negotiating at 10/100 full duplex it cannot form a 10/100
Mbps half duplex link in any of the above mentioned cases. One solution is to configure the local device to
auto negotiation, 10/100 Mbps, with auto or half duplex.