Luxul XMS-1024P - Manual (Page 87)

87
User Guide
© 2014 Luxul. All Rights Reserved.
Other trademarks and registered trademarks are the property of their respective owners
„
Leave Message: When a GARP entity expects other Switches to un-register certain
attributes, it sends out a Leave Message. When receiving a Leave Message from
another entity or un-configuring attributes statically, the device also sends out a
Leave Message.
„
LeaveAll Message: Once a GARP entity starts, it also starts the LeaveAll Timer. If the
Timer expires, the GARP entity sends a LeaveAll Message. LeaveAll Messages will
un-register all attribute information to enable the other GARP entities to re-register
attribute information.
Through message exchange, all attribute information to be registered can be propa-
gated to all member Switches in the same Switched Network.
The interval of GARP Messaging is controlled by Timers. GARP uses the
following Timers:
„
Hold Timer: When a GARP entity receives a piece of registration information, it does
not send out a Join message immediately. Instead it starts the Hold Timer, then puts
all registration information it receives before the timer expires into one Join message
and sends out the message after the timer has expired.
„
Join Timer: To transmit the Join Messages reliably to other entities, a GARP entity
sends each Join Message two times. The Join Timer is used to define the interval
between the two sending operations of each Join Message.
„
Leave Timer: When a GARP entity expects to un-register attribute information, it
sends out a Leave Message. Any GARP entity receiving this message starts its Leave
Timer, and un-registers the attribute information if it does not receive a Join Message
before the timer expires.
„
LeaveAll Timer: Once a GARP entity starts it also starts the LeaveAll Timer, and
sends out a LeaveAll Message after the Timer expires, so the other GARP entities can
re-register all the attribute information on this entity. After re-registration the entity
restarts the LeaveAll Timer to begin a new cycle.
GVRP
GVRP, as an Implementation of GARP and is used to maintain dynamic VLAN registra-
tion information and to propagate the information to other Switches.
Once the GVRP feature is enabled on a Switch, the Switch receives the VLAN registra-
tion information from other Switches to dynamically update the local VLAN registra-
tion information, including VLAN members, Ports through which the VLAN members
can be reached, and so on. The Switch also propagates the local VLAN registration
information to other member Switches so that all the Switching devices in the same
Switched Network can have the same VLAN information. The VLAN registration infor-
mation includes not only the static registration information configured locally, but also