Interfaces and Hardware Component Configuration Guide for Cisco 8000 Series Routers, Cisco IOS XR Releases

PDF

Interfaces and Hardware Component Configuration Guide for Cisco 8000 Series Routers, Cisco IOS XR Releases

Configure a bridge group and assign interfaces to a bridge domain

Updated: September 8, 2026

Want to summarize with AI?

Log in

This topic describes how to configure an L2VPN bridge group and bridge domain and associate a HundredGigE interface with the bridge domain so that the interfaces can be routed by a Bridge-Group Virtual Interface (BVI).

To configure a bridge group and assign interfaces to a bridge domain, complete the following steps.

Procedure

  1. In the global configuration mode, run the l2vpn command to enter the L2VPN configuration mode.

    Example:

    
Router(config)#l2vpn

  2. Run the bridge group bridge-group-name command to create a bridge group and enter the L2VPN bridge group configuration mode.

    Example:

    
Router(config-l2vpn)#bridge group 10

  3. Run the bridge-domain bridge-domain-name command to create a bridge domain and enter L2VPN bridge group bridge domain configuration mode.

    Example:

    Router(config-l2vpn-bg)#bridge-domain BD_1

  4. Associate a HundredGigE interface with the specified bridge domain and enter the L2VPN bridge group bridge domain attachment circuit configuration mode.

    Example:

    
Router(config-l2vpn-bg-bd)#interface HundredGigE 0/1/0/0.1

    The interface-path-id is specified as the rack/slot/module/port location of the interface and .subinterface is the optional subinterface number.

    Repeat this step for as many interfaces as you want to associate with the bridge domain.

  5. Run the end or commit commands to save the configuration changes.

    Example:

    
Router(config-l2vpn-bg-bd-ac)#end

    or

    Router(config-l2vpn-bg-bd-ac)#commit

    • When you issue the end command, the system prompts you to commit changes:

      
Uncommitted changes found, commit them before exiting(yes/no/cancel)?
[cancel]:

    • Entering yes saves configuration changes to the running configuration file, exits the configuration session, and returns the router to EXEC mode.

    • Entering no exits the configuration session and returns the router to EXEC mode without committing the configuration changes.

    • Entering cancel leaves the router in the current configuration session without exiting or committing the configuration changes.

    • Use the commit command to save the configuration changes to the running configuration file and remain within the configuration session.