3Com CoreBuilder 3500, Command Reference Manual

Page: 366 / 784

366 C
HAPTER
14: V
IRTUAL
LAN
S
(VLAN
S
)
bridge vlan
✓
3500
✓
9000
9400
3900
9300
vlanAwareMode
For CoreBuilder 9000: Applies to Layer 3 switching modules only.
For compatibility purposes, allows the system to observe previous VLAN
resource usage and tagged-frame ingress rules for CoreBuilder 3500
serial-port upgrades from Release 1.2.0 to 2.1.0 or 3.0.0 (or
CoreBuilder 9000 upgrades from Release 2.0.0 to 3.0.0).
Valid Minimum Abbreviation
b v v
Important Considerations
■
Use this command
only
if you upgrade your system and the system
reports an error after reaching the VLAN resource limit during a power
up with a serial-port console connection. During the upgrade, the
difference in resource usage and modes of tagging could cause the
later release to use more VLAN resources than did the earlier release,
thereby causing a decrease in the total number of allowable VLANs.
■
If the system reaches the VLAN resource limit during the upgrade, it
displays an error message to identify the index of the VLAN that it was
unable to create. The system removes all bridge ports from the VLAN
that it could not restore from NV data but does maintain the
previously stored NV data.
■
The difference in VLAN resource usage is based on the following:
■
In CoreBuilder 3500 Release 1.2.0 (and CoreBuilder 9000
Release 2.0.0), all bridge ports were
not VLAN aware (tagging
aware) unless they were assigned to a VLAN that has one or more
tagged ports. This behavior is associated with the VLAN aware
mode of
taggedVlanPorts
. If you see the VLAN resource error
message, you can restore your VLANs by issuing this command and
setting the VLAN aware mode to
taggedVLANPorts
. If VLANs are
already defined, the system prompts you to reboot the system to
put the new mode into effect.
■
As of CoreBuilder 3500 Release 2.0.0, (and CoreBuilder 9000
Release 3.0.0), all bridge ports become VLAN aware after a
software update or after an NV data reset and do not have to be
explicitly tagged in order to forward tagged frames. This behavior
is associated with the default VLAN aware mode of
allPorts
. If
you do not see the VLAN internal resource error message, maintain
the VLAN aware mode of
allPorts
.