Alcatel-Lucent 6850-48 Network Guide

Configuring VPLS

Interoperability With Alcatel-Lucent SR Series

OmniSwitch AOS Release 6 Network Configuration Guide

page 11-13

This section contains interoperability differences and similarities between the Alcatel-Lucent OmniSwitch 
implementation of MPLS and the Alcatel-Lucent Service Router (SR) Series implementation of MPLS.

Most of the configure, show, and clear CLI commands for VPLS on the OmniSwitch are compatible with 
the Service Router product family running R6.0. However, the following differences exist between the 
CLI commands offered on the OmniSwitch and those offered on the SR products:

• Flat-based CLI on the OmniSwitch; context-based CLI on the SR.

• Limited options for VPLS service CLI commands.

• Some show command output sections or fields do not apply to the OmniSwitch. Where possible, these 

sections or fields were removed or display “N/A” in the field contents.

• The OmniSwitch uses a slot/port designation for port numbering; the SR uses a slot/mod/port designa-

tion for port numbering.

The system IP address identifies a router as an MPLS router. On the OmniSwitch, however, the user-
configured Loopback0 interface address is used as the system IP address. 

The OmniSwitch provides a static FRR mechanism and the SR Series provides a dynamic FRR mecha-
nism. As a result, the following differences exist between the two implementations:

• Dynamic FRR automatically computes a backup tunnel path. Static FRR requires user-configuration of 

the backup tunnel path.

• Dynamic FRR does not require any configuration on transit routers. Static FRR requires configuration 

on every hop in the backup tunnel path.

• Dynamic FRR requires an underlying IGP to function. Static FRR does not require any underlying 

protocol to work.

Note. Interoperability between the SR Series dynamic FRR and the AOS OmniSwitch static FRR is not 
supported. See 

 for information about configuring static FRR.

When configuring services between OmniSwitch and SR Series routers, set the VC type of the mesh-SDP 
binding to Ethernet if the access ports use the null encapsulation type or VLAN if the ports use dot1q 
encapsulation type. See 

 for more information.