L2VPN ​Commands

l2vpn sdwan instance

To configure an L2VPN instance on an Cisco IOS XE Catalyst SD-WAN device, use the l2vpn sdwan instance command in global configuration mode. To remove the configured L2VPN instance, use the no form of this command.

l2vpn sdwan instance instance-id { multipoint | point-to-point }

Syntax Description

instance-id

A unique number that identifies the VPN or VRF instance. It must be same on the edge devices participating in the Layer 2 domain.

Range: 1 to 65531

multipoint

(Optional) Specifies multipoint as the instance type for connecting multiple sites within the same instance.

point-to-point

(Optional) Specifies point-to-point as the instance type for a direct connection between two edge devices.

Command Default

None

Command Modes

Global configuration (config)

Command History

Release

Modification

Cisco IOS XE Catalyst SD-WAN Release 17.14.1a This command was introduced.

Usage Guidelines

The instance ID must be a unique number. The ID must be the same on the Cisco IOS XE Catalyst SD-WAN devices participating in the Layer 2 domain. It must not overlap with your existing VRFs in the Cisco Catalyst SD-WAN fabric.

The following configures an L2VPN instance for point-to-point service:


Device(config)# l2vpn sdwan instance 10 point-to-point

The following configures an L2VPN instance for multipoint service:


Device(config)# l2vpn sdwan instance 20 multipoint

bridge-domain

To define a broadcast domain internal to a platform, use the bridge-domain command in global configuration mode. To remove the configured components from the bridge domain and to return the components to the bridge-domain default state, use the no form of this command.

bridge-domain bridge-id member { interface service-instance instance-id | sdwan-instance instance-id [ remote-site-id site-id ] vc-id vc-id single-homing }

Syntax Description

bridge-domain bridge-id

Integer that identifies the bridge domain.

Range: 1 to 16000

The upper limit may vary based on the platform.

member

The member interface specifies the LAN side interface or WAN side instance that participates in the bridge domain.

member interface

The LAN side interface that participates in the bridge domain.

member interface service-instance

Specifies the Ethernet service instance.

member interface service-instance instance-id

Specifies the ethernet service instance ID configured for the LAN interface.

Range: 1 to 65531

member

sdwan-instance

The sdwan-instance command is used to link the WAN side sdwan instance with the bridge-domain.

member

sdwan-instance instance-id

Specifies the configured L2VPN SD-WAN instance ID.

Range: 1 to 65531

instance-id

Specifies the ethernet service instance id configured under the LAN interface. It must be the same on the edge devices participating in the Layer 2 domain.

Range: 1 to 65531

remote-site-id

The remote site id that participates in the P2P L2VPN sdwan instance.

site-id

Specifies the remote site ID.

Range: 0 to 4294967295

vc-id

The Virtual Circuit (VC) ID that is used to identify a particular bridge domain.

vc-id

Specifies the Virtual Circuit (VC) ID.

Range: 0 to 4294967295

single-homing

Specifies the homing type. Only single-homing is supported in Cisco IOS XE Catalyst SD-WAN Release 17.14.1a.

dual-homing

Specifies the homing type. Dual-homing is supported from Cisco IOS XE Catalyst SD-WAN Release 17.15.1a.

Command Default

Bridging is disabled.

Command Modes

Global configuration (config) and bridge-domain config

Command History

Release

Modification

Cisco IOS XE Catalyst SD-WAN Release 17.14.1a

The command was introduced.

Cisco IOS XE Catalyst SD-WAN Release 17.15.1a

Added dual-homing keyword.

Usage Guidelines

Use the command to link LAN side interface with bridge-domain. Enter the bridge-domain configuration mode, then enter the member commands.

The following example shows a bridge-domain 30 and service instance ID 20 configured for P2P connection and bridge-domain 31 with service instance ID 21 for P2MP connection for an edge device in a site using single-homing: 


Device(config)# bridge-domain 30
Device(config-bdomain)# member GigabitEthernet7 service-instance 20
Device(config-bdomain-efp)# member sdwan-instance 10  remote-site 2 vc-id 1 single-homing
Device(config-bdomain)# exit
Device(config)# bridge-domain 31
Device(config-bdomain)# member GigabitEthernet7 service-instance 21
Device(config-bdomain-efp)# member sdwan-instance 11 vc-id 1 single-homing

The following example shows a bridge-domain 10 and service instance ID 20 configured for P2P connection and bridge-domain 20 with service instance ID 21 for P2MP connection for an edge device in a site using dual-homing: 


Device(config)# bridge-domain 10
Device(config-bdomain)# member GigabitEthernet7 service-instance 20
Device(config-bdomain-efp)# member sdwan-instance 10  remote-site 2 vc-id 1 dual-homing
Device(config-bdomain)# exit
Device(config)# bridge-domain 20
Device(config-bdomain)# member GigabitEthernet7 service-instance 21
Device(config-bdomain-efp)# member sdwan-instance 11 vc-id 1 dual-homing