Allied Telesis AT-S60 - Manual (Page 286)

AT-S60 Management Software User’s Guide
Section II: Local and Telnet Management 285
Figure 98 provides an example of how GVRP works.
Figure 98 GVRP Example
Switches #1 and #3 contain the Sales VLAN, but Switch #2 does not.
Consequently, the end nodes of the two parts of the Sales VLANs are
unable to communicate with each other.
Without GVRP, you would need to configure Switch #2 by creating the
Sales VLAN on the switch and adding ports 2 and 3 as members of the
VLAN. If you happen to have a large network with a large number of
VLANs, such manual configurations can be cumbersome and time
consuming.
GVRP can make the configurations for you. Here is how GVRP would
resolve the problem in the example.
1. Port 1 on Switch #1 sends a PDU to Port 2 on Switch #2, containing the
VIDs of all the VLANs on the switch. One of the VIDs in the PDU would
be that of the Sales VLAN, VID 11.
2. Switch #2 examines the PDU it receives on Port 2 and notes that it
does not have a VLAN with a VID 11. So it creates the VLAN as a
dynamic GVRP VLAN and assigns it a VID 11 and the name
GVRP_VLAN_11. (The name of a dynamic GVRP VLAN has the prefix
“GVRP_VLAN_”, followed by the VID number.) The switch then adds
Port 2, the port that received the PDU, as a tagged member of the
VLAN.
3. Switch #2 sends a PDU out port 3 containing all of the VIDs of the
VLANs on the switch, including the new gvrp11 VLAN with its VID of
11. (It should be noted that port 3 is not yet a member of the VLAN.
Ports are added to VLANs when they receive, not send a PDU.)
4. Switch #3 receives the PDU on port 4 and, after examining it, notes
that one of the VLANs on Switch #2 has the VID 11, which matches the
VID of an already existing VLAN on the switch. So it does not create
the VLAN since it already exists. It then determines whether the port
that received the PDU, in this case port 4, is a member of the VLAN. If
Switch #1
Static VLAN
Sales VID=11
Port 1 Port 2 Port 3 Port 4
Switch #2 Switch #3
Static VLAN
Sales VID=11