Header Only - DO NOT REMOVE - Extreme Networks

XOS 15.7.1.4 mvrp between BD8806 and SUMMIT X460-G2-48t-10GE4


Userlevel 1
Hi,

just testing mvrp between

3 SUMMIT X460-G2-48t-10GE4 configured as a stack
and
1 BD8806 MSM-48c 10G8Xc

The Summit X stack is connected to BD8806 via a 10GE port.

On the BD8806:
create vlan test
configure test tag 500
configure vlan test add ports 6:2 tagged
configure mvrp tag 500 ports 6:2 registration normal
configure mvrp tag 500 ports 6:2 transmit on
configure mvrp vlan auto-creation on
configure mvrp vlan registration normal
enable mvrp ports 6:2
enable mvrp[/code]On the SUMMIT X stack:
create vlan test
configure test tag 500
configure vlan test add ports 2:49 tagged
configure mvrp tag 500 ports 2:49 registration normal
configure mvrp tag 500 ports 2:49 transmit on
configure mvrp vlan auto-creation on
configure mvrp vlan registration normal
enable mvrp ports 2:49
enable mvrp
create vlan mvrptest
configure mvrptest tag 200
configure vlan mvrptest add ports 2:49 tagged[/code]
However, a show vlan on BD8806 doesn't show mvrptest.

Any hints would be appreciated.
Thank you
--
antonio

28 replies

Userlevel 6
Antonio,

There were actually multiple problems with that article. I have corrected the article (and renamed it something more practical):

Can a VLAN created dynamically by MVRP be renamed?

To preserve your work above, I also created another article pertaining to your issue:

VLAN not propagating across the network after enabling MVRP

Please let me know if you would like me to add or change anything.

Also, I wanted to point out that the following commands are default, you do not have to enter them:
configure mvrp tag 500 ports 2:49 registration normal
configure mvrp tag 500 ports 2:49 transmit on
configure mvrp vlan auto-creation on
configure mvrp vlan registration normal[/code]By default all MVRP enabled ports can join any VLAN and will advertise all VLANs (with a port in them :)).
Userlevel 1
CORRECT PROCEDURE

Given two switches (XOS 15.7.1.4) inter-connected from port (say) 6:2 of switch A to port 2:49 of switch B:

on switch A
create vlan test configure test tag 500
configure vlan test add ports 6:2 tagged
configure mvrp tag 500 ports 6:2 registration normal
configure mvrp tag 500 ports 6:2 transmit on
configure mvrp vlan auto-creation on
configure mvrp vlan registration normal
enable mvrp ports 6:2
enable mvrp [/code]
on switch B:
create vlan test
configure test tag 500
configure vlan test add ports 2:49 tagged
configure mvrp tag 500 ports 2:49 registration normal
configure mvrp tag 500 ports 2:49 transmit on
configure mvrp vlan auto-creation on
configure mvrp vlan registration normal
enable mvrp ports 2:49
enable mvrp
create vlan mvrptest
configure mvrptest tag 200
configure vlan mvrptest add ports 2:1 tagged[/code][look at the last line: a different port must be added to vlan mvrptest in order to activate the propagation process]

At this point vlan 200 will propagate from switch B to switch A: issuing a show vlan command on switch A it shows as SYS_VLAN_0200 with a 'd' flag (dynamically created VLAN).
Userlevel 6
if the correct ports are enable for mvrp (the ones interconnecting the 2 switches), it should work as soon as a new vlan is created on one side with a port in it (even inactive).
Hey Antonio,

Looks like Chad updated the GTAC Knowledge Article you just referenced and improved our KB by adding even more. Good stuff.

Did want to call out, that you can give us suggestions to improve articles directly on GTAC Knowledge. Here's a quick pic to show you how.

Just helps us keep straight your comments with which article. We'd love to hear from our customers on this stuff!

Userlevel 6
if the correct ports are enable for mvrp (the ones interconnecting the 2 switches), it should work as soon as a new vlan is created on one side with a port in it (even inactive).
Maybe you did Antonio....perfect.

Well, for those that read this thread later, use the feedback on GTAC Knowledge. I offer this as proof it works!
Userlevel 6
Antonio,

There were actually multiple problems with that article. I have corrected the article (and renamed it something more practical):

Can a VLAN created dynamically by MVRP be renamed?

To preserve your work above, I also created another article pertaining to your issue:

VLAN not propagating across the network after enabling MVRP

Please let me know if you would like me to add or change anything.

Also, I wanted to point out that the following commands are default, you do not have to enter them:
configure mvrp tag 500 ports 2:49 registration normal
configure mvrp tag 500 ports 2:49 transmit on
configure mvrp vlan auto-creation on
configure mvrp vlan registration normal[/code]By default all MVRP enabled ports can join any VLAN and will advertise all VLANs (with a port in them :)).

Antonio,

Port 3 was not added to VLAN default in my example, so this command would work. However, I added "tagged" to the command in the article anyways.

Thanks for all your input.

As for the article feedback, yes this is currently a limitation of GTACKnowledge. You cannot comment on positive feedback.
Userlevel 7
Hi,

do you see a SYS_VLAN_0200?
Userlevel 1
hi,

no I don't.
there are just "default" and "mgmt" vlans

--
antonio
Userlevel 7
just fired up two VMs running EXOS 15.7.1p1-1, as soon as I do on each side on the correct port:

en mvrp port x
en mvrp

vlans are created.
Userlevel 1
just fired up two VMs running EXOS 15.7.1p1-1, as soon as I do on each side on the correct port:

en mvrp port x
en mvrp

vlans are created.
ok, I'll be back to you tomorrow, thank you
Userlevel 6
Antonio,

Is 8806 port 6:2 connected to Stack port 2:49 (i'm assuming so)? Are there any other active ports in mvrptest?

In order for MVRP to function, there should be multiple devices advertising the VLAN in the network. It is intended to dynamically extend/provision a VLAN, advertised by two edge devices, across the core of a network. Try adding another active port on the 8806 to mvrptest (not 6:2). I suspect you will see 6:2 added dynamically to the VLAN at that point.

If not, please post the following outputs (from both switches) and we can investigate further:

show vlan
show vlan mvrptest
show mvrp tag 200[/code]
Userlevel 6
Antonio,

Are the two switches connected through the correct ports?
show edp port all should show you through which ports the switches see each other.
Userlevel 7
if the correct ports are enable for mvrp (the ones interconnecting the 2 switches), it should work as soon as a new vlan is created on one side with a port in it (even inactive).
Userlevel 1
Antonio,

Is 8806 port 6:2 connected to Stack port 2:49 (i'm assuming so)? Are there any other active ports in mvrptest?

In order for MVRP to function, there should be multiple devices advertising the VLAN in the network. It is intended to dynamically extend/provision a VLAN, advertised by two edge devices, across the core of a network. Try adding another active port on the 8806 to mvrptest (not 6:2). I suspect you will see 6:2 added dynamically to the VLAN at that point.

If not, please post the following outputs (from both switches) and we can investigate further:

show vlan
show vlan mvrptest
show mvrp tag 200[/code]
Try adding another active port on the 8806 to mvrptest (not 6:2)

Hi Chad,

my point is that there is not a mvrptest vlan on BD8806 yet, so I cannot add another active port.

thank you
--
antonio
Userlevel 1
Antonio,

Are the two switches connected through the correct ports?
show edp port all should show you through which ports the switches see each other.

Hi Daniel,

yes, both switches are connected on right ports:

BD8806:

sh edp port all

Port Neighbor Neighbor-ID Remote Age Num
Port Vlans
=============================================================================
6:2 access01 00:00:02:04:96:XX:XX:XX 2:49 33 3
=============================================================================[/code]

SUMMIT X:

sh edp port all
Port Neighbor Neighbor-ID Remote Age Num
Port Vlans
=============================================================================
2:49 core01 00:00:00:04:96:XX:XX:XX 6:2 21 2
=============================================================================[/code] thank you

--

antonio
Userlevel 1
just fired up two VMs running EXOS 15.7.1p1-1, as soon as I do on each side on the correct port:

en mvrp port x
en mvrp

vlans are created.
here are my EXOS versions

on BD8806: 15.7.1.4 v1571b4
on SUMMIT X: 15.7.1.4 v1571b4-patch1-2

thank you

--
antonio
Userlevel 1
just fired up two VMs running EXOS 15.7.1p1-1, as soon as I do on each side on the correct port:

en mvrp port x
en mvrp

vlans are created.
upgraded also BD8806 to 15.7.1.4 v1571b4-patch1-2

vlans still don't propagate
Userlevel 7
Antonio,

Are the two switches connected through the correct ports?
show edp port all should show you through which ports the switches see each other.

is that port a LAG ?
Userlevel 1
Antonio,

Is 8806 port 6:2 connected to Stack port 2:49 (i'm assuming so)? Are there any other active ports in mvrptest?

In order for MVRP to function, there should be multiple devices advertising the VLAN in the network. It is intended to dynamically extend/provision a VLAN, advertised by two edge devices, across the core of a network. Try adding another active port on the 8806 to mvrptest (not 6:2). I suspect you will see 6:2 added dynamically to the VLAN at that point.

If not, please post the following outputs (from both switches) and we can investigate further:

show vlan
show vlan mvrptest
show mvrp tag 200[/code]
anyway, on SUMIT X stack:

sh vlan
-----------------------------------------------------------------------------------------------
Name VID Protocol Addr Flags Proto Ports Virtual
Active router
/Total
-----------------------------------------------------------------------------------------------
Default 1 --------------------------------T---------------- ANY 1 /142 VR-Default
Mgmt 4095 172.31.150.102 /24 ----------------------------- ANY 1 /1 VR-Mgmt
mvrptest 200 ------------------------------------------------- ANY 1 /1 VR-Default
test 500 ------------------------------------------------- ANY 1 /1 VR-Default
-----------------------------------------------------------------------------------------------
Flags : (B) BFD Enabled, (c) 802.1ad customer VLAN, (C) EAPS Control VLAN,
(d) Dynamically created VLAN, (D) VLAN Admin Disabled,
(e) CES Configured, (E) ESRP Enabled, (f) IP Forwarding Enabled,
(F) Learning Disabled, (h) TRILL Enabled, (i) ISIS Enabled,
(I) Inter-Switch Connection VLAN for MLAG, (k) PTP Configured,
(l) MPLS Enabled, (L) Loopback Enabled, (m) IPmc Forwarding Enabled,
(M) Translation Member VLAN or Subscriber VLAN, (n) IP Multinetting Enabled,
(N) Network Login VLAN, (o) OSPF Enabled, (O) Flooding Disabled,
(p) PIM Enabled, (P) EAPS protected VLAN, (r) RIP Enabled,
(R) Sub-VLAN IP Range Configured, (s) Sub-VLAN, (S) Super-VLAN,
(t) Translation VLAN or Network VLAN, (T) Member of STP Domain,
(v) VRRP Enabled, (V) VPLS Enabled, (W) VPWS Enabled, (Z) OpenFlow Enabled
Total number of VLAN(s) : 4 [/code]

show vlan mvrptest
VLAN Interface with name mvrptest created by user
Admin State: Enabled Tagging: 802.1Q Tag 200
Description: None
Virtual router: VR-Default
IPv4 Forwarding: Disabled
IPv4 MC Forwarding: Disabled
IPv6 Forwarding: Disabled
IPv6 MC Forwarding: Disabled
IPv6: None
STPD: None
Protocol: Match all unfiltered protocols
Loopback: Disabled
NetLogin: Disabled
OpenFlow: Disabled
TRILL: Disabled
QosProfile: None configured
Egress Rate Limit Designated Port: None configured
Flood Rate Limit QosProfile: None configured
Ports: 1. (Number of active ports=1)
Tag: *2:49
Flags: (*) Active, (!) Disabled, (g) Load Sharing port
(b) Port blocked on the vlan, (m) Mac-Based port
(a) Egress traffic allowed for NetLogin
(u) Egress traffic unallowed for NetLogin
(t) Translate VLAN tag for Private-VLAN
(s) Private-VLAN System Port, (L) Loopback port
(x) VMAN Tag Translated port
(G) Multi-switch LAG Group port
(H) Dynamically added by MVRP
(D) TRILL Designated, (A) TRILL Appointed Forwarder
(I) Dynamically added by IDM
(U) Dynamically added uplink port
(V) Dynamically added by VM Tracking[/code]

show mvrp tag 200
Port Applicant Applicant Registrar Registrar
State Control State Control
----- --------- --------- --------- ---------
2:49 VO On IN Fixed
-----------------------------------------------------------------
Applicant States:
AA : Anxious active, AN : Anxious new,
AO : Anxious observer, AP : Anxious passive,
LA : Leaving active, LO : Leaving observer,
QA : Quiet active, QO : Quiet observer,
QP : Quiet passive, VN : Very anxious new,
VO : Very anxious observer, VP : Very anxious passive
Registrar States:
IN : In - Registered, INR : In Refresh,
LV : Leaving - Timing out, MT : Empty - Not Registered
Applicant Control:
On : Transmit On, Off : Transmit off
Registrar Control:
Fixed : Statically added, Forbidden : Forbidden VLAN,
Normal : Dynamically added[/code]

thank you

--

antonio
Userlevel 1
Antonio,

Are the two switches connected through the correct ports?
show edp port all should show you through which ports the switches see each other.

no, it's not
Userlevel 1
just fired up two VMs running EXOS 15.7.1p1-1, as soon as I do on each side on the correct port:

en mvrp port x
en mvrp

vlans are created.
just tested mvrp between two SUMMIT X stacks as well (both with 15.7.1.4 v1571b4-patch1-2)

vlans don't propagate either
Userlevel 1
Antonio,

Is 8806 port 6:2 connected to Stack port 2:49 (i'm assuming so)? Are there any other active ports in mvrptest?

In order for MVRP to function, there should be multiple devices advertising the VLAN in the network. It is intended to dynamically extend/provision a VLAN, advertised by two edge devices, across the core of a network. Try adding another active port on the 8806 to mvrptest (not 6:2). I suspect you will see 6:2 added dynamically to the VLAN at that point.

If not, please post the following outputs (from both switches) and we can investigate further:

show vlan
show vlan mvrptest
show mvrp tag 200[/code]
Chad,

I tried to add another (disabled) port of SUMMIT X stack to vlan mvrptest.

as you said mvrptest propagated correctly and has been dynamically added to mvrp enabled ports.

so, it seems that a vlan doesn't propagate until a port (other than mvrp transmitting port) is added to that vlan.

am I correct?

thank you
--
antonio
Userlevel 1
if the correct ports are enable for mvrp (the ones interconnecting the 2 switches), it should work as soon as a new vlan is created on one side with a port in it (even inactive).
with a port in it (even disabled) other than mvrp transmitting ports.
is it correct?

thank you
--
antonio
Userlevel 6
Antonio,

Is 8806 port 6:2 connected to Stack port 2:49 (i'm assuming so)? Are there any other active ports in mvrptest?

In order for MVRP to function, there should be multiple devices advertising the VLAN in the network. It is intended to dynamically extend/provision a VLAN, advertised by two edge devices, across the core of a network. Try adding another active port on the 8806 to mvrptest (not 6:2). I suspect you will see 6:2 added dynamically to the VLAN at that point.

If not, please post the following outputs (from both switches) and we can investigate further:

show vlan
show vlan mvrptest
show mvrp tag 200[/code]
Yes that is correct
Userlevel 1
Antonio,

Is 8806 port 6:2 connected to Stack port 2:49 (i'm assuming so)? Are there any other active ports in mvrptest?

In order for MVRP to function, there should be multiple devices advertising the VLAN in the network. It is intended to dynamically extend/provision a VLAN, advertised by two edge devices, across the core of a network. Try adding another active port on the 8806 to mvrptest (not 6:2). I suspect you will see 6:2 added dynamically to the VLAN at that point.

If not, please post the following outputs (from both switches) and we can investigate further:

show vlan
show vlan mvrptest
show mvrp tag 200[/code]
well, if that's correct then I guess it's not correct what explained in this recent article by extreme networks

thank you
--
antonio
Userlevel 7
if the correct ports are enable for mvrp (the ones interconnecting the 2 switches), it should work as soon as a new vlan is created on one side with a port in it (even inactive).
correct.
I have double-checked that internally.

Reply