GARP VLAN Registration Protocol
(GVRP)
The generic attribute registration protocol (GARP) VLAN registration protocol (GVRP), defined by the IEEE
802.1q specification, is a Layer 2 network protocol that provides for automatic VLAN configuration of
switches. GVRP-compliant switches use GARP to register and de-register attribute values, such as VLAN IDs,
with each other.
Typical virtual local area network (VLAN) implementation involves manually configuring each Layer 2 switch
that participates in a given VLAN. GVRP, defined by the IEEE 802.1q specification, is a Layer 2 network
protocol that provides for automatic VLAN configuration of switches. GVRP-compliant switches use GARP to
register and de-register attribute values, such as VLAN IDs, with each other.
GVRP exchanges network VLAN information to allow switches to dynamically forward frames for one or more
VLANs. Therefore, GVRP spreads this information and configures the needed VLANs on any additional
switches in the network. Data propagates via the exchange of GVRP protocol data units (PDUs).
The purpose of GVRP is to simplify (but not eliminate) static configuration. The idea is to configure switches at
the edge and have the information dynamically propagate into the core. As such, the edge ports must still be
statically configured with VLAN membership information, and they do not run GVRP. It is this information that
is propagated to create dynamic VLAN membership in the core of the network.
Important Points to Remember
• GVRP propagates VLAN membership throughout a network. GVRP allows end stations and switches to
issue and revoke declarations relating to VLAN membership.
• VLAN registration is made in the context of the port that receives the GARP PDU and is propagated to
the other active ports.
• GVRP is disabled by default; enable GVRP for the switch and then for individual ports.
• Dynamic VLANs are aged out after the LeaveAll timer expires three times without receipt of a Join
message. To display status, use the
show gvrp statistics {interface
interface
| summary}
command.
• If spanning tree and GVRP are both required, implement the rapid spanning tree protocol (RSTP). The
device does not support enabling GVRP and MSTP at the same time.
Dell(conf)#protocol spanning-tree pvst
Dell(conf-pvst)#no disable
% Error: GVRP running. Cannot enable PVST.
.........
Dell(conf)#protocol spanning-tree mstp
Dell(conf-mstp)#no disable
% Error: GVRP running. Cannot enable MSTP.
.........
19
GARP VLAN Registration Protocol (GVRP)
412
Содержание S4048T
Страница 1: ...Dell Configuration Guide for the S4048T ON System 9 10 0 1 ...
Страница 98: ... saveenv 7 Reload the system uBoot mode reset Management 98 ...
Страница 113: ...Total CFM Pkts 10303 CCM Pkts 0 LBM Pkts 0 LTM Pkts 3 LBR Pkts 0 LTR Pkts 0 802 1ag 113 ...
Страница 411: ...mode transit no disable Force10 Resilient Ring Protocol FRRP 411 ...
Страница 590: ...Figure 67 Inspecting the LAG Configuration Link Aggregation Control Protocol LACP 590 ...
Страница 591: ...Figure 68 Inspecting Configuration of LAG 10 on ALPHA Link Aggregation Control Protocol LACP 591 ...
Страница 594: ...Figure 70 Inspecting a LAG Port on BRAVO Using the show interface Command Link Aggregation Control Protocol LACP 594 ...
Страница 595: ...Figure 71 Inspecting LAG 10 Using the show interfaces port channel Command Link Aggregation Control Protocol LACP 595 ...
Страница 646: ...Figure 87 Configuring Interfaces for MSDP Multicast Source Discovery Protocol MSDP 646 ...
Страница 647: ...Figure 88 Configuring OSPF and BGP for MSDP Multicast Source Discovery Protocol MSDP 647 ...
Страница 648: ...Figure 89 Configuring PIM in Multiple Routing Domains Multicast Source Discovery Protocol MSDP 648 ...
Страница 653: ...Figure 91 MSDP Default Peer Scenario 2 Multicast Source Discovery Protocol MSDP 653 ...
Страница 654: ...Figure 92 MSDP Default Peer Scenario 3 Multicast Source Discovery Protocol MSDP 654 ...
Страница 955: ...Figure 119 Single and Double Tag First byte TPID Match Service Provider Bridging 955 ...
Страница 1179: ...Figure 147 Create Hypervisor Figure 148 Edit Hypervisor Figure 149 Create Transport Connector Virtual Extensible LAN VXLAN 1179 ...