02-Layer 2-LAN Switching Configuration Guide

HomeSupportWirelessH3C WX5500E Series Access ControllersConfigure & DeployConfiguration GuidesH3C WX5540E Access Controller Switching Engine Configuration Guides(R2607P26)-6W10102-Layer 2-LAN Switching Configuration Guide
13-MVRP configuration
Title Size Download
13-MVRP configuration 196.29 KB

This section describes how to configure MVRP.

Overview

Multiple Registration Protocol (MRP) is an attribute registration protocol and transmits attribute messages. Multiple VLAN Registration Protocol (MVRP) is a typical MRP application. MVRP propagates and learns VLAN configuration among devices. MVRP enables a device to propagate the local VLAN configuration to the other devices, receive VLAN configuration from other devices, and dynamically update the local VLAN configuration (including the active VLANs and the ports through which a VLAN can be reached). MVRP makes sure that all MVRP-enabled devices in a LAN maintain the same VLAN configuration, and reduces the VLAN configuration workload. When the network topology changes, MVRP can propagate and learn VLAN configuration information again according to the new topology, and real-time synchronize the network topology.

MRP is an enhanced version of Generic Attribute Registration Protocol (GARP) and improves the declaration efficiency. MVRP is an enhanced version of GARP VLAN Registration Protocol (GVRP). MVRP delivers the following benefits over GVRP:

·          GVRP does not support the multiple spanning tree instance (MSTI). MVRP runs on a per-MSTI basis, and implements per-VLAN redundant link calculation and load sharing.

·          MVRP decreases the number of packets transmitted for the same amount of VLAN configuration, and improves the declaration efficiency.

For more information about GVRP, see "Configuring GVRP." For more information about MSTI, see "Configuring spanning tree protocols."

MRP

MRP allows participants in the same LAN to declare, propagate, and register information (for example, VLAN information) on a per Multiple Spanning Tree Instance (MSTI) basis.

MRP implementation

Each port that participates in an MRP application (for example, MVRP) is called an "MRP participant." Similarly, a port that participates in an MVRP application is called an "MVRP participant."

As shown in Figure 1, an MRP participant registers and deregisters its attribute values on other MRP participants by sending declarations and withdrawals, and registers and deregisters the attribute values of other participants according to the received declarations and withdrawals. MRP rapidly propagates the configuration information of an MRP participant throughout the LAN.

Figure 1 MRP implementation

 

MVRP registers and deregisters VLAN attributes as follows:

·          When a port receives the declaration of a VLAN attribute, the port registers the VLAN and joins the VLAN.

·          When a port receives the withdrawal of a VLAN attribute, the port deregisters the VLAN and leaves the VLAN.

Figure 1 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.

You can enable or disable the Periodic timer at the CLI. When you disable the Periodic timer, MRP will not periodically send MRP messages, and MRP messages are sent only when the LeaveAll timer expires or the local participant receives LeaveAll messages from a remote participant.

·          Join timer

The Join timer controls the transmission of Join messages. To make sure that Join messages can be reliably transmitted to other participants, an MRP participant waits for a period of the Join timer after sending a Join message. If the participant receives JoinIn messages from other participants and the attributes in the JoinIn messages are the same as the sent Join messages before the Join timer expires, the participant does not re-send the Join message. When both the Join timer and the Periodic timer expire, the participant re-sends the Join message.

·          Leave timer

The Leave timer controls the deregistration of attributes. When an MRP participant wishes other participants to deregister its attributes, it sends a Leave message. On receiving a Leave message, MRP starts the Leave timer, and deregisters the attributes if it does not receive any Join message for the attributes before the Leave timer expires. When an MRP participant sends or receives LeaveAll messages, it starts the Leave timer. MRP deregisters the attributes in the LeaveAll messages if it does not receive any Join message for the attributes before the Leave timer expires.

·          LeaveAll timer

On startup, an MRP participant starts its own LeaveAll timer. When the LeaveAll timer expires, MRP sends out a LeaveAll message and restarts the LeaveAll timer. On receiving the LeaveAll message, other participants re-register all the attributes and re-start their LeaveAll timer.

When you configure the MRP timers, follow these guidelines:

·          When the LeaveAll timer of an MRP participant expires, the MRP participant sends LeaveAll messages to the remote participants. On receiving a LeaveAll message, a remote participant restarts its LeaveAll timer, and stops sending out LeaveAll messages. This mechanism effectively reduces the number of LeaveAll messages in the network.

·          To avoid the case that the LeaveAll timer of a fixed participant always first expires, the switch randomly changes the LeaveAll timer within a certain range when the MRP participant restarts its LeaveAll timer.

MVRP registration modes

The VLAN information propagated by MVRP includes not only locally, manually configured static VLAN information but also dynamic VLAN information from other devices.

VLANs created manually, locally are called "static VLANs," and VLANs learned through MVRP are called "dynamic VLANs." The following MVRP registration modes are available.

·          Normal

An MVRP participant in normal registration mode performs dynamic VLAN registrations and deregistrations, and sends declarations and withdrawals for dynamic and static VLANs.

·          Fixed

An MVRP participant in fixed registration mode disables deregistering dynamic VLANs, sends declarations for dynamic VLANs and static VLANs, and drops received MVRP protocol packets. As a result, an MVRP participant port in fixed registration mode does not deregister or register dynamic VLANs.

·          Forbidden

An MVRP participant in forbidden registration mode disables registering dynamic VLANs, sends declarations for dynamic VLANs and static VLANs, and drops received MVRP protocol packets. As a result, an MVRP participant in forbidden registration mode does not register dynamic VLANs, and does not re-register a dynamic VLAN when the VLAN is deregistered.

Protocols and standards

IEEE 802.1ak IEEE Standard for Local and Metropolitan Area Networks: Virtual Bridged Local Area Networks – Amendment 07: Multiple Registration Protocol

MVRP configuration task list

Task

Remarks

Enabling MVRP

Required.

Configuring the MVRP registration mode

Optional.

Configuring MRP timers

Optional.

Enabling GVRP compatibility

Optional.

 

Configuration prerequisites

Before configuring MVRP, perform the following tasks:

·          Make sure that all MSTIs in the network are effective and each MSTI is mapped to an existing VLAN on each device in the network, because MVRP runs on a per-MSTI basis.

·          Configure the involved ports as trunk ports, because MVRP is available only on trunk ports.

Enabling MVRP

This section describes how to enable MVRP.

Configuration restrictions and guidelines

·          MVRP can work with STP, RSTP, or MSTP, but not other link layer topology protocols, for example, service loopback. Ports blocked by STP, RSTP, or MSTP can receive and send MVRP protocol packets. For more information about service loopback, see "Configuring service loopback groups." For more information about STP, RSTP, and MSTP, see "Configuring spanning tree protocols."

·          Do not enable both MVRP and remote port mirroring on a port. Otherwise, MVRP may register the remote probe VLAN to incorrect ports, which would cause the monitor port to receive undesired duplicates. For more information about port mirroring, see Network Management and Monitoring Configuration Guide.

·          Enabling MVRP on a Layer 2 aggregate interface enables both the aggregate interface and all Selected member ports in the link aggregation group to participate in dynamic VLAN registration and deregistration.

Configuration procedure

To enable MVRP:

 

Step

Command

Remarks

1.       Enter system view.

system-view

N/A

1.       Enable MVRP globally.

mvrp global enable

By default, MVRP is globally disabled.

To enable MVRP on a port, first enable MVRP globally.

2.       Enter interface view.

·      Enter Layer 2 Ethernet interface view or Layer 2 aggregate interface view:
interface
interface-type interface-number

·      Enter port group view:
port-group manual port-group-name

Use one of the commands.

3.       Configure the port to permit the specified VLANs.

port trunk permit vlan { vlan-list | all }

By default, a trunk port permits only VLAN 1.

Make sure that the trunk port permits all registered VLANs.

For more information about the port trunk permit vlan command, see Layer 2LAN Switching Command Reference.

4.       Enable MVRP on the port.

mvrp enable

By default, MVRP is disabled on a port.

 

Configuring the MVRP registration mode

Step

Command

Remarks

1.       Enter system view.

system-view

N/A

2.       Enter interface view.

·      Enter Layer 2 Ethernet interface view or Layer 2 aggregate interface view:
interface
interface-type interface-number

·      Enter port group view:
port-group manual port-group-name

Use one of the commands.

3.       Configure the MVRP registration mode.

mvrp registration { fixed | forbidden | normal }

Optional.

The default setting is normal registration mode.

 

Configuring MRP timers

CAUTION

CAUTION:

The MRP timers apply to all MRP applications, for example, MVRP, on a port. To avoid frequent VLAN registrations and deregistrations, use the same MRP timers throughout the network.

 

Each port maintains its own Periodic, Join, and LeaveAll timers, and each attribute of a port maintains a Leave timer.

To configure MRP timers:

 

Step

Command

Remarks

1.       Enter system view.

system-view

N/A

2.       Enter interface view.

·      Enter Layer 2 Ethernet interface view or Layer 2 aggregate interface view:
interface
interface-type interface-number

·      Enter port group view:
port-group manual port-group-name

Use one of the commands.

3.       Configure the LeaveAll timer.

mrp timer leaveall timer-value

Optional.

The default setting is 1000 centiseconds.

4.       Configure the Join timer.

mrp timer join timer-value

Optional.

The default setting is 20 centiseconds.

5.       Configure the Leave timer.

mrp timer leave timer-value

Optional.

The default setting is 60 centiseconds.

6.       Configure the Periodic timer.

mrp timer periodic timer-value

Optional.

The default setting is 100 centiseconds.

 

Table 1 shows the value ranges for Join, Leave, and LeaveAll timers and their dependencies.

·          If you set a timer to a value beyond the allowed value range, your configuration will fail. To do that, you can change the allowed value range by tuning the value of another related timer.

·          To restore the default settings of the timers, restore the Join timer first, followed by the Leave and LeaveAll timers.

Table 1 Dependencies of the Join, Leave, and LeaveAll timers

Timer

Lower limit

Upper limit

Join

20 centiseconds

Half the Leave timer

Leave

Twice the Join timer

LeaveAll timer

LeaveAll

Leave timer on each port

32760 centiseconds

 

You can restore the Periodic timer to the default at any time.

Enabling GVRP compatibility

CAUTION

CAUTION:

·      MVRP with GVRP compatibility enabled can work together with STP or RSTP, but cannot work together with MSTP. When MVRP with GVRP compatibility enabled works with MSTP, the network might operate improperly.

·      When GVRP compatibility is enabled for MVRP, H3C recommends disabling the Period timer. Otherwise, the VLAN status might frequently change when the system is busy.

 

MVRP can be compatible with GVRP. When the peer device supports GVRP, you can enable GVRP compatibility on the local end, so that the local end can receive and send MVRP and GVRP protocol packets at the same time.

To enable GVRP compatibility:

 

Step

Command

Remarks

1.       Enter system view

system-view

N/A

2.       Enable GVRP compatibility

mvrp gvrp-compliance enable

By default, GVRP compatibility is disabled.

 

Displaying and maintaining MVRP

Task

Command

Remarks

Display the MVRP status of the specified port and each MVRP interface in the specified VLAN.

display mvrp state interface interface-type interface-number vlan vlan-id [ | { begin | exclude | include } regular-expression ]

Available in any view.

Display the MVRP running status.

display mvrp running-status [ interface interface-list ] [ | { begin | exclude | include } regular-expression ]

Available in any view.

Display the MVRP statistics.

display mvrp statistics [ interface interface-list ] [ | { begin | exclude | include } regular-expression ]

Available in any view.

Display the dynamic VLAN operation information of the specified port.

display mvrp vlan-operation interface interface-type interface-number  [ | { begin | exclude | include } regular-expression ]

Available in any view.

Clear the MVRP statistics of the specified ports.

reset mvrp statistics [ interface interface-list ]

Available in user view.

 

Configuration example for MVRP in normal registration mode

Network requirements

As shown in Figure 2, configure MSTP, map VLAN 10 to MSTI 1, map VLAN 20 MST 2, and map the other VLANs to MSTI 0.

Configure MVRP and set the MVRP registration mode to normal, so that Device A, Device B, Device C, and Device D can register and deregister dynamic and static VLANs and keep identical VLAN configuration for each MSTI.

When the network is stable, set the MVRP registration mode to fixed on the port that connecting Device B to Device A, so that the dynamic VLANs on Device B are not de-registered.

Figure 2 Network diagram

 

Configuration procedure

Configuring Device A

# Enter MST region view.

<DeviceA> system-view

[DeviceA] stp region-configuration

# Configure the MST region name, VLAN-to-instance mappings, and revision level.

[DeviceA-mst-region] region-name example

[DeviceA-mst-region] instance 1 vlan 10

[DeviceA-mst-region] instance 2 vlan 20

[DeviceA-mst-region] revision-level 0

# Manually activate the MST region configuration.

[DeviceA-mst-region] active region-configuration

[DeviceA-mst-region] quit

# Configure Device A as the primary root bridge of MSTI 1.

[DeviceA] stp instance 1 root primary

# Globally enable the spanning tree feature.

[DeviceA] stp enable

# Globally enable MVRP.

[DeviceA] mvrp global enable

# Configure port GigabitEthernet 1/0/1 as a trunk port, and configure it to permit all VLANs.

[DeviceA] interface gigabitethernet 1/0/1

[DeviceA-GigabitEthernet1/0/1] port link-type trunk

[DeviceA-GigabitEthernet1/0/1] port trunk permit vlan all

# Enable MVRP on port GigabitEthernet 1/0/1.

[DeviceA-GigabitEthernet1/0/1] mvrp enable

[DeviceA-GigabitEthernet1/0/1] quit

# Configure port GigabitEthernet1/0/2 as a trunk port, and configure it to permit VLAN 40.

[DeviceA] interface gigabitethernet 1/0/2

[DeviceA-GigabitEthernet1/0/2] port link-type trunk

[DeviceA-GigabitEthernet1/0/2] port trunk permit vlan 40

# Enable MVRP on port GigabitEthernet1/0/2.

[DeviceA-GigabitEthernet1/0/2] mvrp enable

[DeviceA-GigabitEthernet1/0/2] quit

# Configure port GigabitEthernet 1/0/3 as a trunk port, and configure it to permit all VLANs.

[DeviceA] interface gigabitethernet 1/0/3

[DeviceA-GigabitEthernet1/0/3] port link-type trunk

[DeviceA-GigabitEthernet1/0/3] port trunk permit vlan all

# Enable MVRP on port GigabitEthernet 1/0/3.

[DeviceA-GigabitEthernet1/0/3] mvrp enable

[DeviceA-GigabitEthernet1/0/3] quit

# Create VLAN 10.

[DeviceA] vlan 10

[DeviceA-vlan10] quit

Configuring Device B

# Enter MST region view.

<DeviceB> system-view

[DeviceB] stp region-configuration

# Configure the MST region name, VLAN-to-instance mappings, and revision level.

[DeviceB-mst-region] region-name example

[DeviceB-mst-region] instance 1 vlan 10

[DeviceB-mst-region] instance 2 vlan 20

[DeviceB-mst-region] revision-level 0

# Manually activate the MST region configuration.

[DeviceB-mst-region] active region-configuration

[DeviceB-mst-region] quit

# Configure Device B as the primary root bridge of MSTI 2.

[DeviceB] stp instance 2 root primary

# Globally enable the spanning tree feature.

[DeviceB] stp enable

# Globally enable MVRP.

[DeviceB] mvrp global enable

# Configure port GigabitEthernet 1/0/1 as a trunk port, and configure it to permit VLANs 20 and 40.

[DeviceB] interface gigabitethernet 1/0/1

[DeviceB-GigabitEthernet1/0/1] port link-type trunk

[DeviceB-GigabitEthernet1/0/1] port trunk permit vlan 20 40

# Enable MVRP on port GigabitEthernet 1/0/1.

[DeviceB-GigabitEthernet1/0/1] mvrp enable

[DeviceB-GigabitEthernet1/0/1] quit

# Configure port GigabitEthernet1/0/2 as a trunk port, and configure it to permit all VLANs.

[DeviceB] interface gigabitethernet 1/0/2

[DeviceB-GigabitEthernet1/0/2] port link-type trunk

[DeviceB-GigabitEthernet1/0/2] port trunk permit vlan all

# Enable MVRP on port GigabitEthernet1/0/2.

[DeviceB-GigabitEthernet1/0/2] mvrp enable

[DeviceB-GigabitEthernet1/0/2] quit

# Configure port GigabitEthernet 1/0/3 as a trunk port, and configure it to permit all VLANs.

[DeviceB] interface gigabitethernet 1/0/3

[DeviceB-GigabitEthernet1/0/3] port link-type trunk

[DeviceB-GigabitEthernet1/0/3] port trunk permit vlan all

# Enable MVRP on port GigabitEthernet 1/0/3.

[DeviceB-GigabitEthernet1/0/3] mvrp enable

[DeviceB-GigabitEthernet1/0/3] quit

# Create VLAN 20.

[DeviceB] vlan 20

[DeviceB-vlan20] quit

Configuring Device C

# Enter MST region view.

<DeviceC> system-view

[DeviceC] stp region-configuration

# Configure the MST region name, VLAN-to-instance mappings, and revision level.

[DeviceC-mst-region] region-name example

[DeviceC-mst-region] instance 1 vlan 10

[DeviceC-mst-region] instance 2 vlan 20

[DeviceC-mst-region] revision-level 0

# Manually activate the MST region configuration.

[DeviceC-mst-region] active region-configuration

[DeviceC-mst-region] quit

# Configure Device C as the root bridge of MSTI 0.

[DeviceC] stp instance 0 root primary

# Globally enable the spanning tree feature.

[DeviceC] stp enable

# Globally enable MVRP.

[DeviceC] mvrp global enable

# Configure port GigabitEthernet 1/0/1 as a trunk port, and configure it to permit all VLANs.

[DeviceC] interface gigabitethernet 1/0/1

[DeviceC-GigabitEthernet1/0/1] port link-type trunk

[DeviceC-GigabitEthernet1/0/1] port trunk permit vlan all

# Enable MVRP on port GigabitEthernet 1/0/1.

[DeviceC-GigabitEthernet1/0/1] mvrp enable

[DeviceC-GigabitEthernet1/0/1] quit

# Configure port GigabitEthernet1/0/2 as a trunk port, and configure it to permit all VLANs.

[DeviceC] interface gigabitethernet 1/0/2

[DeviceC-GigabitEthernet1/0/2] port link-type trunk

[DeviceC-GigabitEthernet1/0/2] port trunk permit vlan all

# Enable MVRP on port GigabitEthernet1/0/2.

[DeviceC-GigabitEthernet1/0/2] mvrp enable

[DeviceC-GigabitEthernet1/0/2] quit

Configuring Device D

# Enter MST region view.

<DeviceD> system-view

[DeviceD] stp region-configuration

# Configure the MST region name, VLAN-to-instance mappings, and revision level.

[DeviceD-mst-region] region-name example

[DeviceD-mst-region] instance 1 vlan 10

[DeviceD-mst-region] instance 2 vlan 20

[DeviceD-mst-region] revision-level 0

# Manually activate the MST region configuration.

[DeviceD-mst-region] active region-configuration

[DeviceD-mst-region] quit

# Globally enable the spanning tree feature.

[DeviceD] stp enable

# Globally enable MVRP.

[DeviceD] mvrp global enable

# Configure port GigabitEthernet 1/0/1 as a trunk port, and configure it to permit VLANs 20 and 40.

[DeviceD] interface gigabitethernet 1/0/1

[DeviceD-GigabitEthernet1/0/1] port link-type trunk

[DeviceD-GigabitEthernet1/0/1] port trunk permit vlan 20 40

# Enable MVRP on port GigabitEthernet 1/0/1.

[DeviceD-GigabitEthernet1/0/1] mvrp enable

[DeviceD-GigabitEthernet1/0/1] quit

# Configure port GigabitEthernet1/0/2 as a trunk port, and configure it to permit VLAN 40.

[DeviceD] interface gigabitethernet 1/0/2

[DeviceD-GigabitEthernet1/0/2] port link-type trunk

[DeviceD-GigabitEthernet1/0/2] port trunk permit vlan 40

# Enable MVRP on port GigabitEthernet1/0/2.

[DeviceD-GigabitEthernet1/0/2] mvrp enable[DeviceD-GigabitEthernet1/0/2] quit

Verifying the configuration

1.        Verify the normal registration mode configuration.

Use the display mvrp running-status command to display the local MVRP VLAN information to verify whether the configuration takes effect.

# Check the local VLAN information on Device A.

[DeviceA] display mvrp running-status

 -------[MVRP Global Info]-------

 Global Status     : Enabled

 Compliance-GVRP   : False

 

 ----[GigabitEthernet1/0/1]----

 Config  Status                      : Enabled

 Running Status                      : Enabled

 Join Timer                          : 20 (centiseconds)

 Leave Timer                         : 60 (centiseconds)

 Periodic Timer                      : 100 (centiseconds)

 LeaveAll Timer                      : 1000 (centiseconds)

 Registration Type                   : Normal

 Local VLANs :

  1(default),

 

 ----[GigabitEthernet1/0/2]----

 Config  Status                      : Enabled

 Running Status                      : Enabled

 Join Timer                          : 20 (centiseconds)

 Leave Timer                         : 60 (centiseconds)

 Periodic Timer                      : 100 (centiseconds)

 LeaveAll Timer                      : 1000 (centiseconds)

 Registration Type                   : Normal

 Local VLANs :

  1(default),

 

 ----[GigabitEthernet1/0/3]----

 Config  Status                      : Enabled

 Running Status                      : Enabled

 Join Timer                          : 20 (centiseconds)

 Leave Timer                         : 60 (centiseconds)

 Periodic Timer                      : 100 (centiseconds)

 LeaveAll Timer                      : 1000 (centiseconds)

 Registration Type                   : Normal

 Local VLANs :

  1(default), 20,

The output shows that: ports GigabitEthernet 1/0/1 and GigabitEthernet1/0/2 have learned only VLAN 1 through MVRP; port GigabitEthernet 1/0/3 has learned VLAN 1 and dynamic VLAN 20 created on Device B through MVRP.

# Check the local VLAN information on Device B.

[DeviceB] display mvrp running-status

 -------[MVRP Global Info]-------

 Global Status     : Enabled

 Compliance-GVRP   : False

 

 ----[GigabitEthernet1/0/1]----

 Config  Status                      : Enabled

 Running Status                      : Enabled

 Join Timer                          : 20 (centiseconds)

 Leave Timer                         : 60 (centiseconds)

 Periodic Timer                      : 100 (centiseconds)

 LeaveAll Timer                      : 1000 (centiseconds)

 Registration Type                   : Normal

 Local VLANs :

  1(default),

 

 ----[GigabitEthernet1/0/2]----

 Config  Status                      : Enabled

 Running Status                      : Enabled

 Join Timer                          : 20 (centiseconds)

 Leave Timer                         : 60 (centiseconds)

 Periodic Timer                      : 100 (centiseconds)

 LeaveAll Timer                      : 1000 (centiseconds)

 Registration Type                   : Normal

 Local VLANs :

  1(default), 10,

 

 ----[GigabitEthernet1/0/3]----

 Config  Status                      : Enabled

 Running Status                      : Enabled

 Join Timer                          : 20 (centiseconds)

 Leave Timer                         : 60 (centiseconds)

 Periodic Timer                      : 100 (centiseconds)

 LeaveAll Timer                      : 1000 (centiseconds)

 Registration Type                   : Normal

 Local VLANs :

  1(default), 10,

The output shows that: port GigabitEthernet 1/0/1 has learned only VLAN 1 through MVRP; ports GigabitEthernet 1/0/2 and GigabitEthernet 1/0/3 have learned VLAN 1 and dynamic VLAN 10 created on Device A through MVRP.

# Check the local VLAN information on Device C.

[DeviceC] display mvrp running-status

 -------[MVRP Global Info]-------

 Global Status     : Enabled

 Compliance-GVRP   : False

 

 ----[GigabitEthernet1/0/1]----

 Config  Status                      : Enabled

 Running Status                      : Enabled

 Join Timer                          : 20 (centiseconds)

 Leave Timer                         : 60 (centiseconds)

 Periodic Timer                      : 100 (centiseconds)

 LeaveAll Timer                      : 1000 (centiseconds)

 Registration Type                   : Normal

 Local VLANs :

  1(default), 10, 20,

 

 ----[GigabitEthernet1/0/2]----

 Config  Status                      : Enabled

 Running Status                      : Enabled

 Join Timer                          : 20 (centiseconds)

 Leave Timer                         : 60 (centiseconds)

 Periodic Timer                      : 100 (centiseconds)

 LeaveAll Timer                      : 1000 (centiseconds)

 Registration Type                   : Normal

 Local VLANs :

  1(default), 20,

The output shows that: port GigabitEthernet 1/0/1 has learned VLAN 1, dynamic VLAN 10 created on Device A, and dynamic VLAN 20 created on Device B through MVRP; port GigabitEthernet1/0/2 has learned VLAN 1 and dynamic VLAN 20 created on Device B through MVRP.

# Check the local VLAN information on Device D.

[DeviceD] display mvrp running-status

 -------[MVRP Global Info]-------

 Global Status     : Enabled

 Compliance-GVRP   : False

 

 ----[GigabitEthernet1/0/1]----

 Config  Status                      : Enabled

 Running Status                      : Enabled

 Join Timer                          : 20 (centiseconds)

 Leave Timer                         : 60 (centiseconds)

 Periodic Timer                      : 100 (centiseconds)

 LeaveAll Timer                      : 1000 (centiseconds)

 Registration Type                   : Normal

 Local VLANs :

  1(default), 20,

 

 ----[GigabitEthernet1/0/2]----

 Config  Status                      : Enabled

 Running Status                      : Enabled

 Join Timer                          : 20 (centiseconds)

 Leave Timer                         : 60 (centiseconds)

 Periodic Timer                      : 100 (centiseconds)

 LeaveAll Timer                      : 1000 (centiseconds)

 Registration Type                   : Normal

 Local VLANs :

  1(default),

The output shows that: port GigabitEthernet 1/0/1 has learned VLAN 1 and dynamic VLAN 20 created on Device B through MVRP; port GigabitEthernet1/0/2 has learned only VLAN 1 through MVRP.

2.        Change the registration mode and verify the configuration.

Set the MVRP registration mode to fixed on GigabitEthernet 1/0/3 of Device B, so that the dynamic VLANs that Device B learns in VLAN 1 are not de-registered.

# Set the MVRP registration mode to fixed on GigabitEthernet 1/0/3.

[DeviceB] interface gigabitethernet 1/0/3

[DeviceB-GigabitEthernet1/0/3] mvrp registration fixed

[DeviceB-GigabitEthernet1/0/3] quit

# Display the local MVRP VLAN information on GigabitEthernet 1/0/3.

[DeviceB] display mvrp running-status interface gigabitethernet 1/0/3

 -------[MVRP Global Info]-------

 Global Status     : Enabled

 Compliance-GVRP   : False

 

 ----[GigabitEthernet1/0/3]----

 Config  Status                      : Enabled

 Running Status                      : Enabled

 Join Timer                          : 20 (centiseconds)

 Leave Timer                         : 60 (centiseconds)

 Periodic Timer                      : 100 (centiseconds)

 LeaveAll Timer                      : 1000 (centiseconds)

 Registration Type                   : Fixed

 Local VLANs :

  1(default), 10,

The output shows that the VLAN information on GigabitEthernet 1/0/3 is not changed after you set the MVRP registration mode to fixed on GigabitEthernet 1/0/3.

# Delete VLAN 10 on Device A.

[DeviceA] undo vlan 10

# Display the local MVRP VLAN information on GigabitEthernet 1/0/3.

[DeviceB] display mvrp running-status interface gigabitethernet 1/0/3

 -------[MVRP Global Info]-------

 Global Status     : Enabled

 Compliance-GVRP   : False

 

 ----[GigabitEthernet1/0/3]----

 Config  Status                      : Enabled

 Running Status                      : Enabled

 Join Timer                          : 20 (centiseconds)

 Leave Timer                         : 60 (centiseconds)

 Periodic Timer                      : 100 (centiseconds)

 LeaveAll Timer                      : 1000 (centiseconds)

 Registration Type                   : Fixed

 Local VLANs :

  1(default), 10,

The output shows that the dynamic VLAN information on GigabitEthernet 1/0/3 is not changed after you set the MVRP registration mode to fixed on GigabitEthernet 1/0/3.

 

  • Cloud & AI
  • InterConnect
  • Intelligent Computing
  • Intelligent Storage
  • Security
  • SMB Products
  • Intelligent Terminal Products
  • Product Support Services
  • Technical Service Solutions
All Services
  • Resource Center
  • Policy
  • Online Help
  • Technical Blogs
All Support
  • Become A Partner
  • Partner Policy & Program
  • Global Learning
  • Partner Sales Resources
  • Partner Business Management
  • Service Business
All Partners
  • Profile
  • News & Events
  • Online Exhibition Center
  • Contact Us
All About Us
新华三官网