H3C Technologies H3C WX6000 Series Access Controllers - Manual (Page 78)

9-1
9
GVRP Configuration
GARP VLAN Registration Protocol (GVRP) is a GARP application. It functions based on the operating
mechanism of GARP to maintain and propagate dynamic VLAN registration information for the GVRP
devices on the network.
When configuring GVRP, go to these sections for information you are interested in:
z
Introduction to GVRP
z
GVRP Configuration Task List
z
Configuring GVRP
z
Displaying and Maintaining GVRP
z
GVRP Configuration Examples
Introduction to GVRP
GARP
Generic Attribute Registration Protocol (GARP) provides a mechanism that allows participants in a
GARP application to distribute, propagate, and register with other participants in a bridged LAN the
attributes specific to the GARP application, such as the VLAN or multicast address attribute.
GARP itself does not exist on a device as an entity. GARP-compliant participants are known as GARP
applications. One example is GVRP. When a GARP participant is present on a port on your device, the
port is regarded as a GARP participant.
GARP messages and timers
1) GARP messages
GARP participants exchange information through the following three types of messages: Join message,
Leave message, and LeaveAll message.
z
A GARP participant uses Join messages to have its attributes registered on other devices. A GARP
participant also sends Join messages to register attributes on other GARP participants when it
receives Join messages from other GARP participants or static attributes are configured on it.
z
A GARP participant uses Leave messages to have its attributes deregistered on other devices. A
GARP participant also sends Leave messages when it receives Leave messages from other
GARP participants or static attributes are deregistered on it.
z
LeaveAll messages are used to deregister all the attributes, through which all the other GARP
participants begin to have all their attributes registered. A GARP participant sends LeaveAll
messages upon the expiration of the LeaveAll timer, which is triggered when the GARP participant
is created.
Join messages, Leave messages, and LeaveAll message make sure the reregistration and
deregistration of GARP attributes are performed in an orderly way.
Through message exchange, all attribute information that needs registration propagates to all GARP
participants throughout a LAN.