View Only
last person joined: 2 days ago 

Ask questions and share experiences about EX and QFX portfolios and all switching solutions across your data center, campus, and branch locations.
  • 1.  MVRP - Not working

    Posted 09-13-2021 13:22
    Hi All,
    I've recently started with Juniper.
    I've read through the document for MVRP:
    It seems to be what I'm looking for but I can't get the access switches to give the vlan's to the distribution switch.
    I have a cable from the dist switch directly to the access switch. Both ends are trunks.
    xe-0/0/20 {
    unit 0 {
    family ethernet-switching {
    interface-mode trunk;
    vlan {
    members all;
    mvrp {
    interface xe-0/0/22;
    But I get no vlan's and the stats are below:
    MVRP statistics for routing instance 'default-switch'

    Interface name : xe-0/0/22
    VLAN IDs registered : 0
    Sent MVRP PDUs : 238
    Received MVRP PDUs without error: 217
    Received MVRP PDUs with error : 0
    Transmitted Join Empty : 0
    Transmitted Leave All : 86
    Recieved Join In : 0
    Transmitted Join In : 0
    Transmitted Empty : 1685
    Transmitted Leave : 0
    Transmitted In : 0
    Transmitted New : 0
    Received Leave All : 74
    Received Leave : 0
    Received In : 0
    Received Empty : 899
    Received Join Empty : 0
    Received New : 0

    Any help appreciated.

    Multiple VLAN Registration Protocol
    Juniper remove preview
    Multiple VLAN Registration Protocol
    Multiple VLAN Registration Protocol (MVRP) is a Layer 2 messaging protocol that automates the creation and management of virtual LANs, thereby reducing the time you have to spend on these tasks. Use MVRP on Juniper Networks switches to dynamically register and unregister active VLANs on trunk interfaces.
    View this on Juniper >


  • 2.  RE: MVRP - Not working

    Posted 09-13-2021 15:58
    I see you have trunk interface as xe-0/0/20, is this the interface connected to your MVRP neighbor or is it xe-0/0/22?


  • 3.  RE: MVRP - Not working

    Posted 09-15-2021 14:35
    Thanks for the reply.
    It turns out that Juniper mvrp works totally differently to Cisco vtp.
    In my opinion it's nowhere near as good.

    Vlan's created on the access switch would not appear in the core switch via the trunk link until I physically plugged in a port that was in that vlan.
    Once this was done the Core switch saw the vlan as a dynamic MVRP vlan.
    Cisco's VTP allows the creation of a vlan on the Server and it will be propagated out to all clients.
    I feel this should also be how the Juniper works as we have some wifi access points that are trunks but the ssid is on vlan 98 for example but this will never be created using MVRP.
    Thanks all


  • 4.  RE: MVRP - Not working

    Posted 09-15-2021 21:36
    VTP is a different thing, indeed.

    VTP will distribute the VLANs regardless of their association/membership in the access port of the switch, in the case of MVRP the VLAN association determines the signalling of the MVRP messages indicating it needs the upstream switch to create the VLAN and allow it over the trunk.

    Glad it is all solved.


  • 5.  RE: MVRP - Not working

    Posted 09-16-2021 05:51
    MVRP is an IEEE standard and hopefully Cisco does implement it per the standard as well in there products.

    Naturally VTP being a Cisco proprietary creation they are free to have the behavior work any way they desire and the customers want.

    Steve Puluka BSEET - Juniper Ambassador
    IP Architect - DQE Communications Pittsburgh, PA (Metro Ethernet & ISP)

  • 6.  RE: MVRP - Not working

    Posted 09-16-2021 06:06
    I didn't know about this.

    Is there a way to get vlan's distributed using mvrp where you just create a vlan and it isn't on an access port?

    For instance a trunk port connected to a juniper access point that hosts 3 vlan's inside the trunk?


  • 7.  RE: MVRP - Not working

    Posted 09-16-2021 08:41

    If this exists, I am unaware of such capability. MVRP membership needs to exist in a port for the adjacent switches to become Anxious Observers and allow the VLAN accordingly.