Extreme Networks ExtremeWare XOS 11.1, Руководство пользователя

Страница: 437 / 496

Using the Command Line Interface
ExtremeWare XOS 11.1 Concepts Guide
437
No link light on Gigabit fiber port:
Check that:
●
The transmit fiber goes to the receive fiber side of the other device and vice-versa. All Gigabit fiber
cables are of the crossover type.
●
The Gigabit ports are set to Auto Off (using the command
configure port <port #> auto off
) if
you are connecting the Extreme Networks switch to devices that do not support autonegotiation.
By default, the Extreme Networks switch has autonegotiation set to On for Gigabit ports.
●
You are using multimode fiber (MMF) when using a 1000BASE-SX Gigabit Ethernet Interface
Connector (GBIC), and single-mode fiber (SMF) when using a 1000BASE-LX GBIC. 1000BASE-SX
technology does not work with SMF. The 1000BASE-LX technology works with MMF but requires
the use of a mode conditioning patchcord (MCP).
VLANs
You cannot add a port to a VLAN:
If you attempt to add a port to a VLAN and get an error message similar to
localhost:7 # configure vlan marketing add ports 1:1,1:2
Error: Protocol conflict when adding untagged port 1:1. Either add this port as tagged
or assign another protocol to this VLAN.
you already have a VLAN using untagged traffic on a port. Only one VLAN using untagged traffic can be
configured on a single physical port.
You verify the VLAN configuration using the following command:
show vlan {detail |<vlan_name> {stpd}}
The solution for this error using this example is to remove ports 1 and 2 from the VLAN currently using
untagged traffic on those ports. If this were the “default” VLAN, the command would be:
localhost:23 # configure vlan default delete ports 1:1,1:2
You can now re-enter the previous command without error:
localhost:26 # configure vlan marketing add ports 1:1,1:2
VLAN names:
There are restrictions on VLAN names. They cannot contain whitespaces and cannot start with a
numeric value.
VLANs, IP addresses, and default routes:
The system can have an IP address for each configured VLAN. You must configure an IP address
associated with a VLAN if you intend to manage (Telnet, SNMP, ping) through that VLAN or route IP
traffic.
You can also configure multiple default routes for the system. The system first tries the default route
with the lowest cost metric.