11
GVRP Configuration
Wh n configuring GVRP, g
e
o to these sections for information you are interested in:
z
Introduction to GVRP
z
GVRP Configuration
Displaying and Maintaining GVRP
z
mple
z
GVRP Configuration Exa
Intro
GARP VLAN registration protocol (GVRP) is an implementation of generic attribute registration protocol
ARP). GARP is introduced as follows.
GARP
participants in a
-compliant application entities are called
RP. When a GARP application entity is present on a port on
application entity.
GARP mess
mes
z
es. A GARP entity also sends Join messages when it receives Join
z
e devices. A GARP entity also sends Leave messages when it receives
z
All messages after the timer times out. LeaveAll messages deregister all the
change, all the attribute information to be registered can be propagated to all the
GARP-enabled switches in the same LAN.
duction to GVRP
(G
The generic attribute registration protocol (GARP), provides a mechanism that allows
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
GARP applications. One example is GV
your device, this port is regarded a GARP
ages and timers
1) GARP
messages
GARP members communicate with each other through the messages exchanged between them. The
sages performing important functions for GARP fall into three types: Join, Leave and LeaveAll.
When a GARP entity wants its attribute information to be registered on other devices, it sends Join
messages to these devic
messages from other entities or it wants some of its statically configured attributes to be registered
on other GARP entities.
When a GARP entity wants some of its attributes to be deregistered on other devices, it sends
Leave messages to thes
Leave messages from other entities for deregistering some attributes or it has some attributes
statically deregistered.
Once a GARP entity is launched, the LeaveAll timer is triggered at the same time. The GARP entity
sends out Leave
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 ex
11-1