Welcome to Scribd. Sign in or start your free trial to enjoy unlimited e-books, audiobooks & documents.Find out more
Standard view
Full view
of .
Look up keyword
Like this
0 of .
Results for:
No results containing your search query
P. 1
IEEE 802.1ak - MVRP and MRP

IEEE 802.1ak - MVRP and MRP

Ratings: (0)|Views: 505|Likes:
Published by joshuayoon

More info:

Published by: joshuayoon on Jan 28, 2011
Copyright:Attribution Non-commercial


Read on Scribd mobile: iPhone, iPad and Android.
download as PDF, TXT or read online from Scribd
See more
See less





Americas Headquarters:Cisco Systems, Inc., 170 West Tasman Drive, San Jose, CA 95134-1706USA
IEEE 802.1ak - MVRP and MRP
First Published: November 14, 2008Last Updated: March 6, 2009
Implementation of the IEEE 802.1ak standard allows for dynamic registration and deregistration of VLANs on ports in a VLAN bridged network. This document describes Multiple Registration Protocol(MRP) and Multiple VLAN Registration Protocol (MVRP) as implemented in accordance with the IEEE802.1ak standard.
Finding Feature Information
Your software release may not support all the features documented in this module. For the latest featureinformation and caveats, see the release notes for your platform and software release. To find informationabout the features documented in this module, and to see a list of the releases in which each feature issupported, see the“Feature Information for IEEE 802.1ak - MVRP and MRP” section on page19.Use CiscoFeature Navigator to find information about platform support and CiscoIOS and CatalystOSsoftware image support. To access CiscoFeature Navigator, go tohttp://www.cisco.com/go/cfn. An account on Cisco.com is not required.
IEEE 802.1ak - MVRP and MRPRestrictions for EEE 802.1ak - MVRP and MRP
Restrictions for EEE 802.1ak - MVRP and MRP
A non-Cisco device can interoperate with a Cisco device only through .1Q trunks.
When both MVRP and VTP pruning are enabled on the device, VTP pruning will be disabled on thedot1q trunks. All dot1q trunks are only allowed to run MVRP and talk to other MVRP participantsin the network, while ISL trunks are running VTP pruning and interoperate with other Cisco deviceswith ISL trunks in another network.
MVRP can be configured on both physical interfaces and Etherchannel interfaces. However, itsconfiguration is not allowed on Etherchannel member ports.
For simple implementation, MVRP dynamic VLAN creation feature is disallowed if the device isrunning in VTP server or client mode.
MVRP and Connectivity Fault Management (CFM) can coexist but if the line card (LC) orsupervisor does not have enough mac-match registers to support both protocols, the MVRP ports onthose LCs are put in error disabled state. To use Layer 2 functionality, disable MVRP on those portsand configure shut/no shut.
MVRP functionality applies only to interfaces configured for Layer 2 (switchport) functionality.
802.1X authentication and authorization takes place after the port becomes link-up and before theDynamic Trunking Protocol (DTP) negotiations start prior to GVRP running on the port.
MVRP cannot be configured and run on a sub-interface.
Information About EEE 802.1ak - MVRP and MRP
IEEE 802.1ak, also known as Multiple Registration Protocol (MRP), allows dynamic registration andderegistration of VLANs on ports in a VLAN bridged network. IEEE 802.1ak provides performanceimprovement over the GVRP and GMRP protocols with more efficient Protocol Data Units (PDUs) andprotocol design. This feature implements MRP and MVRP as specified in the IEEE 802.1ak standard.In a VLAN bridged network, it is desirable to restrict unknown unicast, multicast, and broadcast trafficto those links which the traffic must use to access the appropriate network devices. In a large network,localized topology changes can affect the service over a much larger portion of the network. IEEE802.1ak replaces GARP with MRP offering much improvement over resource utilization andconservation of bandwidth.With the 802.1ak MRP attribute encoding scheme, MVRP only needs to send one PDU that includes thestate of all 4094 VLANs on a port. MVRP also includes the transmission of a Topology ChangeNotification (TCN) for individual VLANs. This is an important feature for service providers because itallows them to localize topology changes.Figure1illustrates MVRP deployed in a provider network onprovider and customer bridges.
IEEE 802.1ak - MVRP and MRPInformation About EEE 802.1ak - MVRP and MRP
Figure1MVRP Deployed on Provider and Customer Bridge
In the Metro Ethernet provider network, the use of thousands of VLANs is likely. Most providers do notwish to filter traffic by destination Mac Addresses. Hence, a pruning protocol like MVRP becomesimportant.InFigure2, redundant links are configured between the access switch and two distribution switches onthe cloud. When the link with VLAN 104 fails over, MVRP need to send only one TCN for VLAN 104.Without MVRP, an STP TCN would have to be sent out for the whole MST region (VLANs1-1000),causing unnecessary network interruption.STP sets the new variable tcDetected for MVRP to decide whether to send a New message (hence,references to MVRP TCN). When an attribute declaration marked as
is received on a given port, anyentries in the filtering database for that port and for that VLAN are removed. This allows MVRP to flushthe filtering database entries rapidly on a per-VLAN basis following a topology change.
        2       7        4        4        8        1

Activity (2)

You've already reviewed this. Edit your review.
1 thousand reads
1 hundred reads

You're Reading a Free Preview

/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->