H3C Technologies H3C S3600 Series Switches - Manual (Page 150)

1-1
1
GVRP Configuration
When configuring GVRP, go to these sections for information you are interested in:
z Introduction to GVRP
z GVRP Configuration
z Displaying and Maintaining GVRP
z GVRP Configuration Example
Introduction to GVRP
GARP VLAN registration protocol (GVRP) is an implementation of generic attribute registration protocol
(GARP). GARP is introduced as follows.
GARP
The 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 attribute.
GARP itself does not exist on a device as an entity. GARP-compliant application entities are called
GARP applications. One example is GVRP. When a GARP application entity is present on a port on
your device, this port is regarded a GARP application entity.
GARP messages and timers
1) GARP messages
GARP members communicate with each other through the messages exchanged between them. The
messages performing important functions for GARP fall into three types: Join, Leave and LeaveAll.
z When a GARP entity wants its attribute information to be registered on other devices, it sends Join
messages to these devices. A GARP entity also sends Join messages when it receives Join
messages from other entities or it wants some of its statically configured attributes to be registered
on other GARP entities.
z When a GARP entity wants some of its attributes to be deregistered on other devices, it sends
Leave messages to these devices. A GARP entity also sends Leave messages when it receives
Leave messages from other entities for deregistering some attributes or it has some attributes
statically deregistered.
z Once a GARP entity is launched, the LeaveAll timer is triggered at the same time. The GARP entity
sends out LeaveAll messages after the timer times out. LeaveAll messages deregister all the
attributes, through which the attribute information of the entity can be registered again on the other
GARP entities.
Leave messages, LeaveAll messages, together with Join messages ensure attribute information can be
deregistered and re-registered.
Through message exchange, all the attribute information to be registered can be propagated to all the
GARP-enabled switches in the same LAN.