Juniper Multiple VLAN Registration Protocol User Manual

Junos® OS

VLAN

s r

Protocol User

Guide

Published

2021-04-18

ii

Juniper Networks, Inc. 1133 nn v n Way Sunnyvale, California 94089 USA

408-745-2000 www.juniper.net

Juniper Networks, the Juniper Networks logo, Juniper, and Junos are registered trademarks of Juniper Networks, Inc. in the United States and other countries. All other trademarks, service marks, registered marks, or registered service marks are the property of their r s c v owners.

Juniper Networks assumes no responsibility for any inaccuracies in this document. Juniper Networks reserves the right

to change, modify, transfer, or otherwise revise this b c		n without n c
Junos® OS	VLAN R s r n Protocol User Guide
Copyright © 2021 Juniper Networks, Inc. All rights reserved.
The n rm	n in this document is current as of the date on the		page.

YEAR 2000 NOTICE

Juniper Networks hardware and s w r products are Year 2000 compliant. Junos OS has no known m r

m ns through the year 2038. However, the NTP c n is known to have some c y in the year 2036.

END USER LICENSE AGREEMENT

The Juniper Networks product that is the subject of this technical						c m n	n consists of (or is intended for use
with) Juniper Networks s w r	Use of such s		w r	is subject to the terms and c n				ns of the End User License
Agreement ("EULA") posted at	s s	r	n r n	s	r	. By downloading, installing or using such
s w r you agree to the terms and c n		ns of that EULA.

iii

Table of Contents

About This Guide | vi

1

n

r n

VLAN

s r

n Protocol

Understanding

VLAN

s r

n Protocol (MVRP) for Dynamic VLAN

s r

n

| 2

n

r n

VLAN

s r

n Protocol (MVRP) to Manage Dynamic VLAN

s r

n

| 6

Enabling MVRP |

6

Disabling MVRP |

7

Changing the R s r n Mode to Disable Dynamic VLANs | 7

n

r n

Timer Values | 7

n

r n

the

c s MAC Address for MVRP | 8

n

r n

an MVRP Interface as a Point-to-Point Interface |

9

n

r n

MVRP Tracing

ns | 9

Controlling the Management State of a VLAN in MVRP n

r ns | 10

n

r

All VLANs to Operate in Normal State | 12

n

r

VLANs to Operate with Mixed States (Fixed and Normal) | 12

nr VLANs to Operate with Mixed States (Fixed, Normal, and Forbidden) | 13

Example: n r n	m c VLAN m n s r n Using MVRP on MX Series
Routers | 14

Requirements | 14

Overview and Topology | 15

nr n | 19

r c n | 27

Verifying That MVRP Is Working Correctly | 34

2

3

iv

nr n Statements

b s n n m c r ss | 40

bridge-domains | 42 bridge-priority | 44 family | 47

interface (MVRP) | 53 interface (Spanning Tree) | 56 interface-mode | 59

nm r (MVRP) | 62

m r (MVRP) | 64 m r (MVRP) | 68

mvrp | 71 no-dynamic-vlan | 75

point-to-point (MVRP) | 77

r s r		n | 79
rstp	| 82
r c		ns (MVRP) | 86

unit | 89

vlan-id (Logical Port in Bridge Domain) | 100 vlan-id-list | 102

rn Mode Commands

show mvrp | 106

show mvrp applicant-state | 110

show mvrp dynamic-vlan-memberships | 114 show mvrp interface | 117

v

show mvrp r	s r	n s	| 120
show mvrp s	s	cs | 123

4Knowledge Base

vi

About This Guide

VLAN R s r	n Protocol (MVRP) is a Layer 2		c n protocol of the
R s r n Protocol (MRP) and is		n in the IEEE 802.1ak standard. MVRP manages the		n
n and renaming of	c v virtual LANs, thereby reducing network administrators’ m			spent on

these tasks. Use MVRP on Juniper Networks MX Series routers, EX Series switches and SRX devices to dynamically register and unregister c v VLANs on trunk interfaces. Using MVRP means that you do

not have to manually register VLANs on all c	nn c	ns	is, you do not need to explicitly bind a
VLAN to each trunk interface. With MVRP, you c n		r	a VLAN on one interface and the VLAN
c n r n is distributed through all c v	interfaces in the domain.

Use this guide to c n r monitor, and troubleshoot MVRP features on your Juniper Network devices.

Junos OS Layer 2 Switching and Bridging Library for R n Devices

1

CHAPTER

r VLAN s r Protocol

Understanding				VLAN R		s r	n Protocol (MVRP) for Dynamic VLAN
R	s r	n	| 2
n	r n			VLAN R	s r	n Protocol (MVRP) to Manage Dynamic
VLAN R		s r	n	| 6
Controlling the Management State of a VLAN in MVRP n r ns | 10
Example:		n	r n	m	c VLAN		m n s r n Using MVRP on MX Series
Routers | 14

Verifying That MVRP Is Working Correctly | 34

2

Understanding	VLAN	s r	n Protocol
(MVRP) for Dynamic VLAN		s r	n

IN THIS SECTION

How MVRP Works | 3

Using MVRP | 3

MVRP R s r n Modes | 4

MRP Timers Control MVRP Updates | 4

MVRP Uses MRP Messages to Transmit Device and VLAN States | 5

MVRP m ns | 5

VLAN R s r	n Protocol (MVRP) is a Layer 2 messaging protocol that manages the	n
n and renaming of	c v virtual LANs, thereby reducing network administrators’ m spent on

these tasks. Use MVRP on Juniper Networks MX Series routers, EX Series switches and SRX devices to

dynamically register and unregister

c

v VLANs on trunk interfaces. Using MVRP means that you do

not have to manually register VLANs on all c

nn c

ns

is, you do not need to explicitly bind a

VLAN to each trunk interface. With MVRP, you c n

r a VLAN on one interface and the VLAN

c n r

n is distributed through all

c v

interfaces in the domain.

The primary purpose of MVRP is to manage dynamic VLAN r

s r

n in Layer 2 networks. In

managing dynamic VLAN r

s r

n MVRP also prunes VLAN n

rm

n

MVRP is an Layer 2

c

n protocol of the

R

s r

n Protocol (MRP) and is

n in

the IEEE 802.1ak standard. MRP and MVRP were designed by IEEE to perform the same nc

ns as

Generic

r b

R

s r

n Protocol (GARP) and GARP VLAN R

s r

n Protocol (GVRP) while

overcoming some GARP and GVRP

m

ns in

r c

r

m

ns involving bandwidth usage and

convergence

m in large networks with large numbers of VLANs.

MVRP was created by IEEE as a replacement

c

n for GVRP. MVRP and GVRP cannot be run

concurrently to share VLAN n rm

n in a Layer 2 network.

This topic describes:

3

How MVRP Works

When any MVRP-member VLAN is changed, that VLAN sends a protocol data unit (PDU) to all other MVRP-member c v VLANs. The PDU informs the other VLANs which devices and interfaces currently belong to the sending VLAN. This way, all MVRP-member VLANs are always updated with the current VLAN state of all other MVRP-member VLANs. Timers dictate when PDUs can be sent and when devices receiving MVRP PDUs can update their MVRP VLAN n rm n

The VLAN r s r n n rm n sent by MVRP protocol data units (PDUs) includes the current VLANs membership—that is, which routers are members of which VLANs—and which router interfaces

are in which VLAN. MVRP shares all n rm n in the PDU with all routers	r c	n in MVRP in
the Layer 2 network.
MVRP stays synchronized using these PDUs. The routers in the network r	c	n in MVRP receive

these PDUs during state changes and update their MVRP states accordingly. MVRP m rs dictate when PDUs can be sent and when routers receiving MVRP PDUs can update their MVRP n rm n

In	n to sending PDU updates, MVRP dynamically creates VLANs on member interfaces when a
new VLAN is added to any one interface. This way, VLANs created on one member device are
propagated to other member devices as part of the MVRP message exchange process.
VLAN n	rm n is distributed as part of the MVRP message exchange process and can be used to

dynamically create VLANs, which are VLANs created on one switch and propagated to other routers as

part of the MVRP message exchange process. Dynamic VLAN cr					n using MVRP is enabled by
default, but can be disabled.
As part of ensuring that VLAN membership n		rm	n is current, MVRP removes routers and
interfaces from the VLAN n rm	n when they become unavailable. Pruning VLAN n rm n has
these b n s
• Limits the network VLAN c n	r n to	c v	r c	n s only, reducing network overhead.
• Targets the scope of broadcast, unknown unicast, and m				c s	(BUM) r c to interested devices
only.

Using MVRP

MVRP is disabled by default on the devices and, when enabled, c s only trunk interfaces. Once you enable MVRP, all VLAN interfaces on the device belong to MVRP (the default normal r s r n mode) and those interfaces accept PDU messages and send their own PDU messages. To prevent one or more interfaces from r c n in MVRP, you can s c c y c n r an interface to forbidden

r s r n mode instead of the default normal mode.

4

VLAN n dynamic VLAN c n r n through MVRP, and VLAN pruning are all c v on trunk interfaces when MVRP is enabled.

MVRP			s r	n Modes
The MVRP r			s r n mode		n s whether an interface does or does not		r c	in MVRP.
The following MVRP r				s r	n modes are c n r b
•	forbidden—The interface does not register or declare VLANS (except s c						y c n	r VLANs).
•	normal—The interface accepts MVRP messages and r c					s in MVRP. This is the default
	r	s r	n mode s	n
•	restricted—The interface ignores all MVRP JOIN messages received for VLANs that are not s c y
	c n	r	on the interface.

MRP Timers Control MVRP Updates

MVRP r		s r	n and updates are controlled by				m rs that are part of the MRP protocol. These		m rs
are set on a per-interface basis and					n when MVRP PDUs can be sent and when MVRP n			rm	n
can be updated on a switch.
The following			m rs are used to control the			r	n of MVRP:
•	Join	m r	n r	s the interval for the next MVRP PDU transmit opportunity.
•	Leave	m r	n r s the period of		m that an interface on the switch waits in the Leave state
	before changing to the unregistered state.
•	LeaveAll m		r	n r s the frequency with which the interface generates LeaveAll messages.
	BEST PRACTICE: Maintain default				m r s	n	s unless there is a compelling reason to change
	the s	n s Modifying m rs to inappropriate values might cause an imbalance in the						r	n
	of MVRP.

5

MVRP Uses MRP Messages to Transmit Device and VLAN States

MVRP uses MRP messages to register and declare MVRP states for a switch and to inform the Layer 2 network that a switch is leaving MVRP. These messages are communicated as part of the PDU to communicate the state of a r c r switch interface on the Layer 2 network to the other switches in the network.

The following messages are communicated for MVRP:

•	Empty—VLAN n	rm	n is not being declared and is not registered.
•	In—VLAN n rm	n is not being declared but is registered.
•	JoinEmpty—VLAN n		rm n is being declared but not registered.
•	JoinIn—VLAN n	rm	n is being declared and is registered.
•	Leave—VLAN n	rm	n that was previously registered is being withdrawn.
•	LeaveAll—All r	s r	ns will be de-registered. r c n s that want to r c	in MVRP will
	need to re-register.
•	New—VLAN n	rm	n is new and possibly not previously registered.

MVRP m	ns
The following m	ns apply when c n r n MVRP:
• MVRP works with Rapid Spanning Tree Protocol (RSTP) and		Spanning Tree Protocol (MSTP),
but not with VLAN Spanning Tree Protocol (VSTP).

•MVRP is allowed only on single tagged trunk ports.

•MVRP is not allowed if a physical interface has more than one logical interface.

•MVRP is only allowed if a logical has one trunk interface (unit 0).

6

n r n	VLAN	s r	n Protocol
(MVRP) to Manage Dynamic VLAN			s r n

IN THIS SECTION
	Enabling MVRP | 6
	Disabling MVRP | 7			n Mode to Disable Dynamic VLANs | 7
	Changing the R s r
	n	r n	Timer Values | 7
	n	r n	the	c s MAC Address for MVRP | 8
	n	r n	an MVRP Interface as a Point-to-Point Interface | 9
	n	r n	MVRP Tracing		ns | 9

VLAN R s r n Protocol (MVRP) is used to manage dynamic VLAN r s r n in a Layer 2 network. You can use MVRP on MX Series routers or on EX Series switches.

MVRP is disabled by default on MX Series routers and EX Series switches.

To enable MVRP or set MVRP ns follow these ns r c ns

Enabling MVRP

MVRP can only be enabled on trunk interfaces.

To enable MVRP on a s c c trunk interface (here, interface ge-3/0/5):

[edit protocols mvrp] user@host# set interface ge-3/0/5

7

Disabling MVRP

MVRP is disabled by default. You only need to perform this procedure if you have previously enabled MVRP.

To disable MVRP on all trunk interfaces, use one of the following:

[edit]	c	protocols mvrp
user@host#

user@host# delete protocols mvrp

Changing the		s r	n Mode to Disable Dynamic VLANs
When the r	s r	n mode for an interface is set to normal (the default), dynamic VLANs are created
on interfaces	r c	n in MVRP. The dynamic VLANs created on one router or switch are then
propagated by means of MVRP to other routers or switches in a topology.
However, dynamic VLAN cr			n through MVRP can be disabled for all trunk interfaces or for
individual trunk interfaces.
For n rm	n about disabling dynamic VLAN cr			n on an interface so that the interface does not
register and does not r c			in MVRP, see "Controlling the Management State of a VLAN in MVRP

nr ns " on page 10.

nr n Timer Values

The m rs in MVRP					n	the amount of	m an interface waits to join or leave MVRP or to send or
process the MVRP n					rm	n for the router or switch		r receiving an MVRP PDU:
•	The join	m r controls the amount of					m the router or switch waits to accept a r		s r n request.
•	The leave	m	r controls the period of				m that the router or switch waits in the Leave state before
	changing to the unregistered state.
•	The leaveall		m r controls the frequency with which the LeaveAll messages are communicated.
The default MVRP				m r values are 200 ms for the join				m r 1000 ms for the leave	m r and 10000
ms for the leaveall				m	r

8

	BEST PRACTICE: Maintain default					m r s n s unless there is a compelling reason to change
	the s n s Modifying			m	rs to inappropriate values might cause an imbalance in the		r	n
	of MVRP.
	To set the join	m	r for a s	c	c interface:
	[edit protocols mvrp]
	user@host# set interface ge-3/0/5					n m r 300
	To set the leave	m r for a s			c c interface:
	[edit protocols mvrp]
	user@host# set interface ge-3/0/5					m r 1200
	To set the leaveall		m r for a s		c c interface:
	[edit protocols mvrp]
	user@host# set interface ge-3/0/5					m r 12000

SEE ALSO

nm r (MVRP) v m r (MVRP)

v m r (MVRP)

n r n the

c s MAC Address for MVRP

MVRP uses the customer MVRP m c s MAC address when MVRP is enabled. However, you can c n r MVRP to instead use the provider MVRP m c s MAC address.

9

To c n r MVRP to use the provider MVRP m c s MAC address:

[edit protocols mvrp]
user@host# set b	s n n m c	r ss provider-bridge-group;

SEE ALSO

b	s n n m c r ss

nr n an MVRP Interface as a Point-to-Point Interface

Specify that a c n r interface is connected point-to-point. If s c a point-to-point subset of the MRP state machine provides a simpler and more c n method to accelerate convergence on the network.

To specify that an MVRP interface is point-to-point (here, interface ge-3/0/5):

[edit protocols mvrp]

user@host# set interface ge-3/0/5 point-to-point;

SEE ALSO

point-to-point (MVRP)

n	r n MVRP Tracing			ns
Set MVRP protocol-level tracing			ns
To specify MVRP protocol tracing (here, the				is /var/log/mvrp-log, size is 2m, number of s is 28,
the	n world-readable indicates the log can be read by user, and MVRP is				n events):
[edit protocols mvrp]
user@host# edit r c		ns	/var/log/mvrp-log size 2m s 28 world-readable		events

10

SEE ALSO

r c ns (MVRP)

RELATED DOCUMENTATION

Example: n r n m c VLAN m n s r n Using MVRP on MX Series Routers | 14

Controlling the Management State of a VLAN in MVRP n r ns

IN THIS SECTION

n	r	All VLANs to Operate in Normal State | 12
n	r	VLANs to Operate with Mixed States (Fixed and Normal) | 12
n	r	VLANs to Operate with Mixed States (Fixed, Normal, and Forbidden) | 13

MX Series routers use VLAN R s r n Protocol (MVRP) to manage dynamic virtual LAN (VLAN) r s r n in Layer 2 networks. Enabling MVRP on trunk interfaces in Layer 2 networks reduces network overhead by m n the scope of broadcast, unknown unicast, and m c s (BUM)

rc to interested devices only.

Dynamic VLAN r		s r n through MVRP is enabled by default when you enable MVRP on a trunk
interface. The trunk interface			m c y uses the normal r	s r	n mode, accepts MVRP messages,
and r c	s in MVRP. The management state in this case is also known as normal. However, it can
be useful to c	n	r VLAN IDs to bypass the dynamic VLAN r		s r	n process for security reasons

or when MVRP is not supported on a peer switch. You can change the management state of a VLAN independently to either exclude it n r y from the MVRP r s r n process and remain in an unregistered state (forbidden state), or to force a VLAN to always stay in a registered state and to be declared on all other forwarding ports ( x state).

Three parameters are used to control the management state of a VLAN in an MVRP c n r n

• The VLAN is a member in the interface VLAN ID list (c n r at the [edit interfaces interfacename family bridge vlan-id-list] hierarchy level).

11

• The VLAN is a member in the bridge domain VLAN ID list (c n r at the [edit bridge-domain bridge-domain-name vlan-id-list] hierarchy level).

• The MVRP r s r n mode is c n interface interface-name r s r

r for MVRP (c n r at the [edit protocols mvrp n (normal | restricted | forbidden)] hierarchy level).

When these three parameters are combined, a VLAN operates with the following MVRP management states:

• If a VLAN ID is present in both the interface and bridge domain VLAN ID list, the VLAN is in a x management state, rr s c v of the MVRP r s r n mode.

• If a VLAN ID is present in the interface VLAN ID list but not in the bridge domain VLAN ID list and the MVRP r s r n mode is forbidden, the VLAN ID is in a forbidden management state. If the

MVRP r s r n mode is not forbidden, the VLAN ID is in a normal r	s r	n state.
• If a VLAN ID is not present in the interface VLAN ID list and the MVRP r	s r	n mode is

forbidden or restricted, the VLAN ID is in a forbidden management state. Otherwise, it is in a normal management state.

Table 1 on page 11	n s in more detail the MVRP management state for a VLAN when the interface
and bridge domain VLAN ID lists and the MVRP r				s r	n mode are c n			r
Table 1 on page 11 contains the service c		n	r	for BEB2, as well as the c				rr	n S-VLAN, I-SID,
and B-VLAN.
Table 1: MVRP Management States
VLAN ID Present	VLAN ID Present	Interface Uses				Interface Uses			Interface Uses
in Interface VLAN	in Bridge Domain	MVRP Normal				MVRP Restricted			Forbidden
ID List?	VLAN ID List?	R	s r	n		R	s r n		R	s r n Mode
		Mode				Mode
yes	yes	x	state			x	state		x	state
yes	no	normal state				normal state			forbidden state
yes	yes/no	normal state				forbidden state			forbidden state

This topic describes how to c n r the management state for VLANs in an MVRP c n r n

12

nr All VLANs to Operate in Normal State

To c n	r an interface to operate in the normal state, c n		r the r s r	n state as normal:
[edit protocols]
user@host# set mvrp interface interface-name r s r n normal
For example, to c n		r all VLANs on trunk interface ge-1/0/0 to operate in normal state:

[edit]

user@host# set interface ge-1/0/0 family bridge trunk

user@host# set protocols mvrp interface ge-1/0/0 r s r n normal

nr VLANs to Operate with Mixed States (Fixed and Normal)

To c n

r an interface to operate in a x state, add the VLANs that should operate in a x state

to the interface VLAN ID list:

[edit]

user@host# set interface interface-name family bridge vlan-id-list vlan-ids user@host# set bridge-domains bridge-domain-name vlan-id-list vlan-ids

For example, to c n r the rs 1024 VLANs on trunk interface ge-1/0/0.0 to operate in x state, and the other VLANs to operate in normal state:

[edit]

user@host# set interface ge-1/0/0.0 family bridge trunk user@host# set interface ge-1/0/0.0 family bridge vlan-id-list 1-1024 user@host# set bridge-domains bd vlan-id-list 1-1024

user@host# set protocols mvrp interface ge-1/0/0 r s r n normal

13

n	r VLANs to Operate with Mixed States (Fixed, Normal, and
Forbidden)
To c n	r an interface to operate in the forbidden state, c n	r the r s r n state as restricted:
[edit protocols]
user@host# set protocols mvrp interface interface-name r s r		n restricted

For example, to c n r the rs 1024 VLANs on trunk interface ge-1/0/0.0 to operate in x state, VLAN IDs 1024 to 2048 to operate in normal state, and the remaining VLANs to operate in forbidden state:

[edit]

user@host# set interface ge-1/0/0.0 family bridge trunk user@host# set interface ge-1/0/0.0 family bridge vlan-id-list 1-2048 user@host# set bridge-domains bd vlan-id-list 1-1024

user@host# set protocols mvrp interface ge-1/0/0 r s r n restricted

RELATED DOCUMENTATION
	Example: n r n	m	c VLAN		m n s r n Using MVRP on MX Series Routers | 14
	n r n	VLAN R	s r	n Protocol (MVRP) to Manage Dynamic VLAN R		s r n |
6
	Verifying That MVRP Is Working Correctly
	Understanding	VLAN R		s r	n Protocol (MVRP) for Dynamic VLAN R s r	n

14

Example: n r n

m c VLAN

m n s r n Using MVRP on MX Series Routers

IN THIS SECTION

Requirements | 14

Overview and Topology | 15

n r n | 19

r c n | 27

	VLAN R			s r n Protocol (MVRP) is used in Layer 2 networks to dynamically share virtual
LAN (VLAN) n			rm	n and to	m c y c n r necessary VLAN n		rm	n	m c y
c n	r n	VLANs on ports based on the current network c n r				n ensures that a router does not
send	r	c to an interface on the network with an n c v VLAN. In this way, MVRP reduces network
overhead by m			n	the scope of broadcast, unknown unicast, and m		c s	(BUM) r		c to interested
devices only. MVRP also provides for rapid healing of network failures without n								rr	n services to
n	c	VLANs and improves convergence m s

MVRP is a Layer 2 network protocol based on the IEEE standard 802.1ak amendment to 802.1Q-2005,

Standard for Local and Metropolitan Area Networks Virtual Bridged Local Area Networks - Amendment 07: R s r n Protocol.

This example describes how to use MVRP to automate	m n s r n of VLAN membership changes
within your network and to dynamically create VLANs:

Requirements

This example uses the following hardware and s						w r components:
•	Two MX Series routers	c	n	as edge switches
•	One MX Series router	c	n	as an	r	n switch

• Junos OS Release 10.1 or later for MX Series routers

15

Overview and Topology

IN THIS SECTION

Topology | 17

VLANs are s c y c	n	r on access interfaces on MX Series routers	c n as edge switches. The
VLAN membership n	rm	n is propagated to the MX Series router c n	as an	r	n switch at
the core by enabling MVRP on two trunk interfaces:one c nn c n edge switch 1				(ES1) to	r	n

switch 1 (AS1), and the other c nn c n ES2 to AS1. Enabling MVRP on the trunk interface of each MX

Series router in your network ensures that the	c v	VLAN n rm	n for the routers in the network is
propagated to each router through the trunk interfaces (the default r			s r n mode for MVRP).
MVRP ensures that the VLAN membership n	rm	n on the trunk interface is updated as the edge
switch’s access interfaces become c v or n c v

You do not need to explicitly bind a VLAN to the trunk interface. When MVRP is enabled, the trunk

interface v r s s all the VLANs that are	c v (bound to access interfaces) on that switch. An MVRP-
enabled trunk interface does not v r s	VLANs that have been c n r on the switch but are not

currently bound to an access interface. For example, ES1 in the topology does not forward r c to n c v VLAN 300 on ES2.

Rapid Spanning Tree Protocol (RSTP) is also c n r on the trunk interfaces to promote a loop-free topology.

This example shows a network with two customer sites, site–1 and site–2, using VLANs 100, 200, and 300.

ES1 supports all three VLANS, and all three VLANS are c v and bound to interfaces that are connected to three customers at site–1:

• ge-11/2/6—Access port c nn c n customer3–site1, VLAN ID 100.

• ge-11/2/7—Access port c nn c n customer2–site1, VLAN ID 200.

• ge-11/2/8—Access port c nn c n customer1–site1, VLAN ID 300.

• ge-11/3/0—Trunk port c nn c n ES1 to AS1.

ES2 has been c n r to support two VLANS, and both VLANS are c v and bound to interfaces that are connected to two customers at site–2:

• ge-0/1/1—Access port c nn c n customer1–site2, VLAN ID 100.

16

• ge-0/2/0—Access port c nn c n customer2–site2, VLAN ID 200.

• ge-0/0/5—Trunk port c nn c n ES2 to AS1.

AS1 learns the VLANs dynamically using MVRP through the c nn c n to the edge switches. AS1 has two trunk interfaces:

•ge-3/3/0—Connects the router to edge switch ES1 on interface ge-11/3/0.

•ge-3/0/5—Connects the router to edge switch ES2 on interface ge-0/0/5.

The default MVRP interface r			s r	n mode is normal and is used in this example. An interface in
normal r	s r	n mode r	c	s in MVRP when MVRP is enabled on the router. For n rm n
about changing the MVRP r			s r	n mode, see "Controlling the Management State of a VLAN in
MVRP n	r	ns " on page 10.

17

Topology

Figure 1 shows MVRP c		n	r	on three MX Series routers: two routers r			n as edge switches
and one router	r n	as an		r	n switch.
Figure 1: MVRP	n	r	on Three MX Series Routers for			m c VLAN	m n s r n

Table 2 on page 18 explains the components of the example topology.

18

Table 2: Components of the Network Topology
Property	S	n s
MX Series routers	•	ES1
	•	ES2
	•	AS1
VLAN tag IDs associated with bridge domain bd	100, 200, and 300
ES1 interfaces	ES1 interfaces:
	•	ge-11/2/6—Access port c nn c	n
		customer3–site1, VLAN ID 100.
	•	ge-11/2/7—Access port c nn c	n
		customer2–site1, VLAN ID 200.
	•	ge-11/2/8—Access port c nn c	n
		customer1–site1, VLAN ID 300.
	•	ge-11/3/0—Trunk port c nn c	n ES1 to
		AS1.
ES2 interfaces	ES2 interfaces:
	•	ge-0/1/1—Access port c nn c	n
		customer3–site2, VLAN ID 100.
	•	ge-0/2/0—Access port c nn c	n
		customer3–site2, VLAN ID 200.
	•	ge-0/0/5—Trunk port c nn c n	ES2 to AS1.
AS1 interfaces	AS1 interfaces:
	• ge-3/3/0—Trunk port connected to ES1.
	• ge-3/0/5—Trunk port connected to ES2.

19

n r n

IN THIS SECTION

n	r n	MVRP on ES1 | 19
n	r n	MVRP on ES2 | 22
n	r n	MVRP on AS1 | 25

To enable MVRP and RSTP on the trunk interface, as well as c n r ES1 access interfaces and the bridge domain, perform these tasks:

nr n MVRP on ES1

CLI Quick	n	r	n
To quickly c	n	r ES1 for MVRP, copy the following commands and paste them into the switch
terminal window of ES1:
[edit]
set interfaces ge-11/2/6			scr	n "connected to customer3-site-1"
set interfaces ge-11/2/6 unit 0 family bridge interface-mode access
set interfaces ge-11/2/6 unit 0 family bridge vlan-id 300
set interfaces ge-11/2/7			scr	n "connected to customer2-site-1"

set interfaces ge-11/2/7 unit 0 family bridge interface-mode access set interfaces ge-11/2/7 unit 0 family bridge vlan-id 200

set interfaces ge-11/2/8	scr	n "connected to customer1-site-1"
set interfaces ge-11/2/8 unit 0 family bridge interface-mode access
set interfaces ge-11/2/8 unit 0 family bridge vlan-id 100
set interfaces ge-11/3/0	scr	n "connected to AS1 interface ge-3/3/0"

set interfaces ge-11/3/0 unit 0 family bridge interface-mode trunk set bridge-domains bd vlan-id-list [100 200 300]

set protocols mvrp interface ge-11/3/0 set protocols rstp interface ge-11/3/0

20

NOTE: As we recommend as a best r c c		default MVRP	m	rs are used in this example. The
default values associated with each MVRP		m r are 200 ms for the join m r 1000 ms for the
leave m r and 10000 ms for the leaveall		m r Modifying	m	rs to inappropriate values might
cause an imbalance in the	r n of MVRP.

Step-by-Step Procedure

To c n		r	MVRP on ES1:
1.	n	r	the access interfaces for customers at customer-site 1 and the trunk interface c nn c n
	ES1 to AS1:
	[edit interfaces]
	user@es1# set ge-11/2/6			scr	n "connected to customer3-site-1"
	user@es1# set ge-11/2/6 unit 0 family bridge interface-mode access
	user@es1# set ge-11/2/6 unit 0 family bridge vlan-id 300
	user@es1# set ge-11/2/7			scr	n "connected to customer2-site-1"
	user@es1# set ge-11/2/7 unit 0 family bridge interface-mode access
	user@es1# set ge-11/2/7 unit 0 family bridge vlan-id 200
	user@es1# set ge-11/2/8			scr	n "connected to customer1-site-1"
	user@es1# set ge-11/2/8 unit 0 family bridge interface-mode access
	user@es1# set ge-11/2/8 unit 0 family bridge vlan-id 100
	user@es1# set ge-11/3/0			scr	n "connected to AS1 interface ge-3/3/0"
	user@es1# set ge-11/3/0 unit 0 family bridge interface-mode trunk
2.	n	r the bridge domain bd and the VLAN IDs associated with the bridge domain:

[edit bridge-domains]

user@es1# set bd vlan-id-list [100 200 300]

3. Enable MVRP on the trunk interface:

[edit protocols]

user@es1# set mvrpinterface ge-11/3/0

21

4. Enable RSTP on the trunk interface:

[edit protocols]

user@es1# set rstp interface ge-11/3/0

Results

Check the results of the c	n	r	n
user@es1> show c n	r	n
interfaces {
ge-11/2/6 {

description "connected to customer3-site-1"; unit 0 {

family bridge { interface-mode access; vlan-id 300;

}

}

}

ge-11/2/7 {

description "connected to customer2-site-1"; unit 0 {

family bridge { interface-mode access; vlan-id 200;

}

}

}

ge-11/2/8 {

description "connected to customer1-site-1"; unit 0 {

family bridge { interface-mode access; vlan-id 100;

}

}

}

ge-11/3/0 {

description "connected to AS1 interface ge-3/3/0";

22

unit 0 {

family bridge { interface-mode trunk;

}

}

}

}

bridge-domains { bd {

vlan-id-list [ 100 200 300 ];

}

}

protocols { mvrp {

interface ge-11/3/0;

}

rstp {

interface ge-11/3/0;

}

}

nr n MVRP on ES2

CLI Quick	n	r	n
To quickly c	n	r ES2 for MVRP, copy the following commands and paste them into the switch
terminal window of ES2:
[edit]
set interfaces ge-0/0/5			scr	n "connected to AS1 interface ge-3/0/5"
set interfaces ge-0/0/5 unit 0 family bridge interface-mode trunk
set interfaces ge-0/1/1			scr	n "connected to customer1-site-2"
set interfaces ge-0/1/1 unit 0 family bridge interface-mode access
set interfaces ge-0/1/1 unit 0 family bridge vlan-id 100
set interfaces ge-0/2/0			scr	n "connected to customer2-site-2"

set interfaces ge-0/2/0 unit 0 family bridge interface-mode access set interfaces ge-0/2/0 unit 0 family bridge vlan-id 200

set bridge-domains bd vlan-id-list [100 200] set protocols mvrp interface ge-0/0/5

set protocols rstp interface ge-0/0/5

23

NOTE: As we recommend as a best r c c		default MVRP	m	rs are used in this example. The
default values associated with each MVRP		m r are 200 ms for the join m r 1000 ms for the
leave m r and 10000 ms for the leaveall		m r Modifying	m	rs to inappropriate values might
cause an imbalance in the	r n of MVRP.

Step-by-Step Procedure

To enable MVRP and RSTP on the trunk interface, as well as c n					r ES2 access interfaces and the
bridge domain:
1.	n	r the access interfaces for customers at customer site site-2 and the trunk interface
	c nn c	n ES2 to AS1:
	[edit interfaces]
	user@es2# set ge-0/0/5		scr	n "connected to AS1 interface ge-3/0/5"
	user@es2# set ge-0/0/5 unit 0 family bridge interface-mode trunk
	user@es2# set ge-0/1/1		scr	n "connected to customer1-site-2"
	user@es2# set ge-0/1/1 unit 0 family bridge interface-mode access
	user@es2# set ge-0/1/1 unit 0 family bridge vlan-id 100
	user@es2# set ge-0/2/0		scr	n "connected to customer2-site-2"
	user@es2# set ge-0/2/0 unit 0 family bridge interface-mode access
	user@es2# set ge-0/2/0 unit 0 family bridge vlan-id 200
2.	n	r the bridge domain bd and the VLAN IDs associated with the bridge domain:

[edit bridge-domains] user@es2# set bd vlan-id-list [100 200]

3. Enable MVRP on the trunk interface:

[edit protocols]

user@es2# set mvrpinterface ge-0/0/5

24

4. Enable RSTP on the trunk interface:

[edit protocols]

user@es2# set rstp interface ge-0/0/5

Results

Check the results of the c	n	r	n
user@es2> show c n	r	n
interfaces {
ge-0/0/5 {

description "connected to AS1 interface ge-3/0/5"; unit 0 {

family bridge { interface-mode trunk;

}

}

}

ge-0/1/1 {

description "connected to customer1-site-2"; unit 0 {

family bridge { interface-mode access; vlan-id 100;

}

}

}

ge-0/2/0 {

description "connected to customer2-site-2"; unit 0 {

family bridge { interface-mode access; vlan-id 200;

}

}

}

}

bridge-domains { bd {