Vlans - Extreme Networks ExtremeWare 7.2e Installation And User Manual

Using the Command-Line Interface
Always verify that the Extreme switch and the network device match in configuration for speed and
duplex.
No link light on Gigabit fiber port:
Check to ensure that the transmit fiber goes to the receive fiber side of the other device, and vice-versa.
All gigabit fiber cables are of the cross-over type.
The Extreme switch has auto-negotiation set to on by default for gigabit ports. These ports need to be
set to auto off (using the command ) if you are connecting it to
configure port <port #> auto off
devices that do not support auto-negotiation.
Ensure that you are using multi-mode fiber (MMF) when using a 1000BASE-SX GBIC, and single mode
fiber (SMF) when using a 1000BASE-LX GBIC. 1000BASE-SX does not work with SMF. 1000BASE-LX
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 port 1:1,1:2
ERROR: Protocol conflict on port 1:5
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.
VLAN configuration can be verified by using the following command:
show vlan {<vlan name> | detail | stats {vlan} <vlan name>}
The solution for this error 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 # configure vlan default del port 1,2
which should now allow you to re-enter the previous command without error as follows:
localhost # configure vlan add port 1,2
VLAN names:
There are restrictions on VLAN names. They cannot contain whitespaces and cannot start with a
numeric value unless you use quotation marks around the name. If a name contains whitespaces, starts
with a number, or contains non-alphabetical characters, you must use quotation marks whenever
referring to the VLAN name.
802.1Q links do not work correctly:
Remember that VLAN names are only locally significant through the command-line interface. For two
switches to communicate across a 802.1Q link, the VLAN ID for the VLAN on one switch should have a
corresponding VLAN ID for the VLAN on the other switch.
ExtremeWare 7.2e Installation and User Guide 329