[an error occurred while processing this directive][an error occurred while processing this directive]

Option: Configuring VPLS Interinstance Bridging and Routing

To deliver interinstance traffic between two or more VPLS instances, or between a VPLS instance and a Layer 3 VPN routing instance, you must use a logical tunnel interface. Originally designed to interconnect logical systems, the logical tunnel interface acts as a point-to-point connection between instances. A logical tunnel interface can be generated by a Tunnel Services PIC installed on an Enhanced FPC in your routing platform, an integrated Adaptive Services Module installed in an M7i router, or a tunnel services interface configured on MX Series routers. To configure a logical tunnel interface, include the lt-fpc/pic/0 statement at the [edit interfaces] hierarchy level. Keep in mind these rules when you connect instances:

  • You need to configure both endpoints of the logical tunnel. Configure the first logical tunnel interface in the VPLS instance and the second within the instance you want to interconnect to the VPLS domain.
  • Choose one of several interface encapsulation types for your logical tunnel interface peers. Your choices are Ethernet, Ethernet circuit cross-connect (CCC), Ethernet VPLS, Frame Relay, Frame Relay CCC, VLAN, VLAN CCC, and VLAN VPLS. Include one of these choices with the encapsulation statement at the [edit interfaces lt-fpc/pic/0 unit unit-number] hierarchy level.
  • Depending on the encapsulation type you select, specify a corresponding data-link connection identifier (DLCI) number for Frame Relay or a VLAN identifier for VLAN encapsulations on your logical tunnel interface peers. To configure the DLCI or VLAN identifier, include the dlci or vlan-id statement at the [edit interfaces lt-fpc/pic/0 unit unit-number] hierarchy level.
  • Your choice of protocol family for the logical tunnel interface also is determined by your selection of an encapsulation type. For Ethernet VPLS and VLAN VPLS, family vpls is assigned by default. For all other Ethernet and VLAN encapsulation types, include the mpls or inet statement at the [edit interfaces lt-fpc/pic/0 unit unit-number family] hierarchy level. For Frame Relay encapsulation types, you can configure any of the available protocol families: ccc, inet, inet6, iso, mpls, or tcc.
  • Be sure to match the logical interface unit numbers of the peering logical tunnel interfaces. To configure, include the peer-unit statement at the [edit interfaces lt-fpc/pic/0 unit unit-number] hierarchy level.
    [edit]interfaces {lt-fpc/pic/0 {unit unit-number {encapsulation (ethernet | ethernet-ccc | ethernet-vpls | frame-relay |
    frame-relay-ccc | vlan | vlan-ccc | vlan-vpls);
    peer-unit number; # The logical unit number of the peering lt interface.dlci dlci-number; vlan-id vlan-number;family (ccc | inet | inet6 | iso | mpls | tcc);}
    }
    }routing-instances {vpls-instance-name {interface ge-fpc/pic/port.unit-number;interface lt-0/0/0.1;... second-instance-name {interface at-fpc pic/port.unit-number;interface lt-0/0/0.2;...}}}

Published: 2010-04-15

[an error occurred while processing this directive]