Configure GVRP Settings on a Switch

Available Languages

Download Options

  • PDF     (747.8 KB)
    View with Adobe Reader on a variety of devices
  • ePub     (858.1 KB)
    View in various apps on iPhone, iPad, Android, Sony Reader, or Windows Phone
  • Mobi (Kindle)     (463.6 KB)
    View on Kindle device or Kindle app on multiple devices
Updated:December 13, 2018
Document ID:SMB2754

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

Configure GVRP Settings on a Switch

Objective

Adjacent Virtual Local Area Network (VLAN)-aware devices can exchange VLAN information with each other with the use of the Generic VLAN Registration Protocol (GVRP). GVRP is based on the Generic Attribute Registration Protocol (GARP) and propagates VLAN information throughout a bridged network. When GVRP is activated, it transmits and receives GARP Packet Data Units (GPDUs). This allows you to configure a VLAN on one switch and then propagate its information across the network, instead of the previously required creation of the VLAN on each switch in the network.

This article provides instructions on how to configure GVRP settings on the switch.

Note: Since GVRP requires support for tagging, the port must be configured in Trunk or General mode. To learn how to configure a port on an Sx300 or Sx500 switch to be a Trunk or General Mode, click here. If you have an Sx350, SG350X, or Sx550X switch, click here.

Applicable Devices

  • Sx250 Series
  • Sx300 Series
  • Sx350 Series
  • SG350X Series
  • Sx500 Series
  • Sx550X Series

Software Version

  • 1.4.7.06 — Sx300, Sx500
  • 2.2.8.04 — Sx250, Sx350, SG350X, Sx550X

Configure GVRP Settings

Step 1. Log in to the web-based utility of your switch then choose Advanced in the Display Mode drop-down list.

Note: The available menu options may vary depending on the device model. In this example, SG350X-48MP is used.

Note: If you have an Sx300 or Sx500 Series switch, skip to Step 2.

Step 2. Choose VLAN Management > GVRP Settings.

Step 3. Check the Enable check box in the GVRP Global Status area to enable GVRP.

Step 4. Click Apply.

Step 5. Choose an interface or Link Aggregation (LAG) from the Interface Type equals to drop-down list then click Go.

Note: In this example, Port of Unit 1 is chosen.

Step 6. Click the radio button next to the desired interface on which to configure GVRP settings. In this example, GE3 is chosen.

Step 7. Scroll down then click Edit.

Step 8. (Optional) In the Interface area, click the desired interface type and choose the desired interface from the adjacent drop-down list. The options are:

  • Unit and Port — A single interface.
  • LAG — Link aggregation (LAG) is used to describe various methods for using multiple parallel network connections to increase throughput beyond the limit that one link can achieve.

Note: In this example, the unit and port are retained.

Step 9. Check the GVRP State Enable check box to enable GVRP on the interface.

Step 10. (Optional) Check the Dynamic VLAN Creation Enable check box to allow users to create new VLANs on the interface.

Step 11. Check the GVRP Registration Enable check box to allow GVRP to register VLANs on the desired interface.

Step 12. Click Apply then click Close.

Step 13. (Optional) Click Save to save the configured settings to the startup configuration file.

You should now have successfully configured the GVRP settings on your switch.

Revision History

Revision Publish Date Comments
1.0
13-Dec-2018
Initial Release

Was this Document Helpful?

FeedbackFeedback

Contact Cisco