72
required to set the port connected to the backbone
networks to be up-link port.
4 Create VLAN Mapping
entries.
Required. On the
VLAN
→
VLAN VPN
→
VLAN Mapping
page, configure the VLAN Mapping entries basing on the
actual application.
5 Create SP (Service
Provider) VLAN
Optional. On the
VLAN
→
802.1Q VLAN
page, create the
SP VLAN. For the steps of creating VLAN, please refer to
802.1Q VLAN
.
Configuration Procedure of VLAN Mapping Function:
Step Operation
Description
1 Create VLAN Mapping
entries.
Required. On the
VLAN
→
VLAN VPN
→
VLAN Mapping
page, configure the VLAN Mapping entries basing on the
actual application.
2 Enable VLAN Mapping
function for port.
Required. On the
VLAN
→
VLAN VPN
→
Port Enable
page,
enable VLAN Mapping function for the ports.
3 Create SP (Service
Provider) VLAN
Optional. On the
VLAN
→
802.1Q VLAN
page, create the
SP VLAN. For the steps of creating VLAN, please refer to
802.1Q VLAN
.
8.5 GVRP
GVRP (GARP VLAN Registration Protocol) is an implementation of GARP (generic attribute
registration protocol). GVRP allows the switch to automatically add or remove the VLANs via the
dynamic VLAN registration information and propagate the local VLAN registration information to
other switches, without having to individually configure each VLAN.
¾
GARP
GARP provides the mechanism to assist the switch members in LAN to deliver, propagate and
register the information among the members. GARP itself does not work as the entity among the
devices. The application complied with GARP is called GARP implementation, and GVRP is the
implementation of GARP. When GARP is implemented on a port of device, the port is called
GARP entity.
The information exchange between GARP entities is completed by messages. GARP defines the
messages into three types: Join, Leave and LeaveAll.
•
Join Message:
When a GARP entity expects other switches to register certain attribute
information of its own, it sends out a Join message. And when receiving the Join message
from the other entity or configuring some attributes statically, the device also sends out a Join
message in order to be registered by the other GARP entities.
•
Leave Message:
When a GARP entity expects other switches to deregister certain attribute
information of its own, it sends out a Leave message. And when receiving the Leave message
from the other entity or deregistering some attributes statically, the device also sends out a
Leave message.
•
LeaveAll Message:
Once a GARP entity starts up, it starts the LeaveAll timer. After the timer
times out, the GARP entity sends out a LeaveAll message. LeaveAll message is to deregister