HP 3100 Series Configuration Manual page 203

•
When a port receives the withdrawal of a VLAN attribute, the port deregisters the VLAN and
leaves the VLAN.
Figure 68 shows a simple MVRP implementation on an MSTI. In a network with multiple MSTIs,
VLAN registration and deregistration are performed on a per-MSTI basis.
MRP messages
MRP exchanges information among MRP participants by advertising MRP messages, including Join,
New, Leave, and LeaveAll. Join and New messages are declarations, and Leave and LeaveAll
messages are withdrawals.
•
Join message
An MRP participant sends Join messages when it wishes to declare the attribute values
configured on it and receives Join messages from other MRP participants.
When receiving a Join message, an MRP participant sends a Join message to all
participants except the sender.
Join messages fall into the following types:
JoinEmpty—An MRP participant sends JoinEmpty messages to declare attribute values
that it has not registered. For example, when a static VLAN exists on a device, the attribute
of the VLAN on the device is not changed even if the device learns the VLAN again through
MRP. In this case, the Join message for the VLAN attribute is a JoinEmpty message,
because the VLAN attribute is not registered.
JoinIn—An MRP participant sends JoinIn messages to declare attribute values that it has
registered. For example, when the device learns a VLAN through MRP messages, and
dynamically creates the VLAN, the Join message for the VLAN attribute is a JoinIn
message.
•
New message
Similar to a Join message, a New message enables MRP participants to register attributes.
When the Multiple Spanning Tree Protocol (MSTP) topology changes, an MRP participant
sends New messages to declare the topology change.
On receiving a New message, an MRP participant sends a New message out of each port
except the receiving port.
•
Leave message
An MRP participant sends Leave messages when it wishes other participants to deregister
the attributes that is has deregistered.
When receiving a Leave message, an MRP participant sends a Leave message to all
participants except the sender.
•
LeaveAll message
Each MRP participant is configured with an individual LeaveAll timer. When the timer
expires, the MRP participant sends LeaveAll messages to the remote participants, so that
the local participant and the remote participants deregister all attributes and re-register all
attributes. This process periodically clears the useless attributes in the network.
On receiving a LeaveAll message, MRP determines whether to send a Join message to
request the sender to re-register these attributes according to attribute status.
MRP timers
The implementation of MRP uses the following timers to control MRP message transmission.
•
Periodic timer
On startup, an MRP participant starts its own Periodic timer to control MRP message
transmission. The MRP participant collects the MRP messages to be sent before the Periodic
timer expires, and sends the MRP messages in as few packets as possible when the Periodic
timer expires and meanwhile restarts the Periodic timer. This mechanism reduces the number
of MRP protocol packets periodically sent.
194