Cisco Cisco IOS Software Release 12.2(33)SRE
Compact GARP VLAN Registration Protocol
Information About cGVRP
2
Cisco IOS Release 12.2(33)SRB
•
VLAN mapping is not supported with GVRP.
•
cGVRP and Connectivity Fault Management (CFM) can coexist but if the line card (LC) or
supervisor does not have enough mac-match registers to support both protocols, the cGVRP ports
on those LCs are put in error disabled state. To use Layer 2 functionality, disable cGVRP on those
ports and configure shut/no shut.
supervisor does not have enough mac-match registers to support both protocols, the cGVRP ports
on those LCs are put in error disabled state. To use Layer 2 functionality, disable cGVRP on those
ports and configure shut/no shut.
•
cGVRP functionality applies only to interfaces configured for Layer 2 (switchport) functionality.
•
Native VLAN tagging causes frames sent to the native VLAN of the .1Q trunk ports to be
encapsulated with .1Q tags. Problems may arise with other GVRP participants on the LAN if they
cannot admit tagged GVRP Protocol Data Unit (PDU)s. Caution must be exercised if both features
are enabled at the same time.
encapsulated with .1Q tags. Problems may arise with other GVRP participants on the LAN if they
cannot admit tagged GVRP Protocol Data Unit (PDU)s. Caution must be exercised if both features
are enabled at the same time.
•
802.1X authentication and authorization takes place after the port becomes link-up and before the
Dynamic Trunking Protocol (DTP) negotiations start prior to GVRP running on the port.
Dynamic Trunking Protocol (DTP) negotiations start prior to GVRP running on the port.
•
Port security works independently from GVRP and it may be limited to the number of other GVRP
participants on a LAN with which a GVRP enabled port on a device can communicate.
participants on a LAN with which a GVRP enabled port on a device can communicate.
•
GVRPs cannot be configured and run on a subinterface.
•
GVRP and UniDirectional Link Routing (UDLR) should not be enabled on the same interface
because UDLR limits frames in one direction on the port and GVRP is a two way communication
protocol.
because UDLR limits frames in one direction on the port and GVRP is a two way communication
protocol.
•
Additional memory is required to store GARP/GVRP configurations and states per GVRP enabled
port, but it can be dynamically allocated on demand.
port, but it can be dynamically allocated on demand.
•
GARP Multicast Registration Protocol (GMRP) is not supported.
Information About cGVRP
To configure cGVRP, you should understand the following concepts:
•
•
•
•
GARP/GVRP Definition
GVRP enables automatic configuration of switches in a VLAN network allowing network devices to
dynamically exchange VLAN configuration information with other devices. GVRP is based on GARP
which defines procedures for registering and deregistering attributes with each other, eliminating
unnecessary network traffic by preventing attempts to transmit information to unregistered users.
dynamically exchange VLAN configuration information with other devices. GVRP is based on GARP
which defines procedures for registering and deregistering attributes with each other, eliminating
unnecessary network traffic by preventing attempts to transmit information to unregistered users.
GVRP is defined in IEEE 802.1Q.
cGVRP Overview
GVRP is a protocol that requires extensive CPU time in order to transmit all 4094 VLAN states on a
port. In Compact mode only one PDU is sent and it includes the states of all the 4094 VLANs on a port.
port. In Compact mode only one PDU is sent and it includes the states of all the 4094 VLANs on a port.