Dell PowerConnect B-FCXs, Configuration Manual

Page: 551 / 1494

PowerConnect B-Series FCX Configuration Guide 509
53-1002266-01
Configuration notes
14
•
Single STP must be enabled on the device. Dell implementation of GVRP requires Single STP.
If you do not have any statically configured VLANs on the device, you can enable Single STP as
follows.
PowerConnect(config)#vlan 1
PowerConnect(config-vlan-1)#exit
PowerConnect(config)#span
PowerConnect(config)#span single
These commands enable configuration of the default VLAN (VLAN 1), which contains all the
device ports, and enable STP and Single STP.
•
All VLANs that are learned dynamically through GVRP are added to the single spanning tree.
•
All ports that are enabled for GVRP become tagged members of the GVRP base VLAN (4093). If
you need to use this VLAN ID for another VLAN, you can change the GVRP VLAN ID. Refer to
“Changing the GVRP base VLAN ID” on page 510. The software adds the GVRP base VLAN to
the single spanning tree.
•
All VLAN ports added by GVRP are tagged.
•
GVRP is supported only for tagged ports or for untagged ports that are members of the default
VLAN. GVRP is not supported for ports that are untagged and are members of a VLAN other
than the default VLAN.
•
To configure GVRP on a trunk group, enable the protocol on the primary port in the trunk group.
The GVRP configuration of the primary port is automatically applied to the other ports in the
trunk group.
•
You can use GVRP on a device even if the device has statically configured VLANs. GVRP does
not remove any ports from the statically configured VLANs, although GVRP can add ports to the
VLANS. GVRP advertises the statically configured VLANs. Ports added by GVRP do not appear
in the running-config and will not appear in the startup-config file when save the configuration.
You can manually add a port to make the port a permanent member of the VLAN. After you
manually add the port, the port will appear in the running-config and be saved to the
startup-config file when you save the configuration.
•
VLANs created by GVRP do not support virtual routing interfaces or protocol-based VLANs.
virtual routing interfaces and protocol-based VLANs are still supported on statically configured
VLANs even if GVRP adds ports to those VLANs.
•
You cannot manually configure any parameters on a VLAN that is created by GVRP. For
example, you cannot change STP parameters for the VLAN.
•
The GVRP timers (Join, Leave, and Leaveall) must be set to the same values on all the devices
that are exchanging information using GVRP.
•
If the network has a large number of VLANs, the GVRP traffic can use a lot of CPU resources. If
you notice high CPU utilization after enabling GVRP, set the GVRP timers to longer values. In
particular, set the Leaveall timer to a longer value. Refer to
“Changing the GVRP timers” on
page 512.
•
The feature is supported only on Ethernet ports.
NOTE
If you plan to change the GVRP base VLAN ID (4093) or the maximum configurable value for the
Leaveall timer (300000 ms by default), you must do so before you enable GVRP.