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

Associate BVI as a routed Interface on a bridge domain

Want to summarize with AI?

Log in

This topic describes how to associate a Bridge-Group Virtual Interface (BVI) as the routed interface on a bridge domain by creating the bridge group and bridge domain and applying the routed interface BVI configuration.


To associate the BVI as the routed interface on 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.

Create a bridge group and enter the L2VPN bridge group configuration mode.

Example:

Router(config-l2vpn)#bridge group BG_test
3.

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

Example:

Router(config-l2vpn-bg)#bridge-domain 1
4.

Associate the specified BVI as the routed interface for the interfaces that are assigned to the bridge domain.

Example:

Router(config-l2vpn-bg-bd)# routed interface bvi 1
5.

Run the end or commit commands to save the configuration.

Example:


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

or

Router(config-l2vpn-bg-bd)#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.