Configuring Logical Tunnel Interfaces

[ Contents] [ Prev] [ Next] [ Index] [ Report an Error]

Logical tunnel (lt-) interfaces provide quite different services depending on the host routing platform:

On M-series and T-series routing platforms, logical tunnel interfaces allow you to connect logical systems, virtual routers, or VPN instances. The router must be equipped with a Tunnel Services PIC or an Adaptive Services Module (only available on M7i routers). For more information on the latter applications, see the JUNOS VPNs Configuration Guide.
On J-series Services Routers, lt- interfaces have a completely different function; they enable you to change class-of-service (CoS) classifications and header bits.

For more information, see the following sections:

Connecting Logical Systems

To connect two logical systems, you configure a logical tunnel interface on both logical systems. Then you configure a peer relationship between the logical tunnel interfaces, thus creating a point-to-point connection.

To configure a point-to-point connection between two logical systems, configure the logical tunnel interface by including the lt-fpc/pic/port statement:


            
               lt-fpc/pic/port {
               
               
                  
                     unit logical-unit-number {
                     
                     encapsulation encapsulation;
                     
                     peer-unit unit-number;   # peering logical system unit number
                     
                     dlci dlci-number;
                     
                     family (inet | inet6 | iso |
                        mpls);
                     
                     }
                  
               
               }

You can include this statement at the following hierarchy levels:

[edit interfaces]
[edit logical-systems logical-system-name interfaces]

When configuring logical tunnel interfaces, note the following:

You can configure each logical tunnel interface with one of the following encapsulation types: Ethernet, Ethernet circuit cross-connect (CCC), Ethernet VPLS, Frame Relay, Frame Relay CCC, VLAN, VLAN CCC, or VLAN VPLS.
You can configure the IP, IPv6, International Organization for Standardization (ISO), or MPLS protocol family.
The peering logical interfaces must belong to the same logical tunnel interface derived from the Tunnel Services PIC or Adaptive Services Module.
You can configure only one peer unit for each logical interface. For example, unit 0 cannot peer with both unit 1 and unit 2.
To enable the logical tunnel interface, you must configure at least one physical interface statement.
Logical tunnels are not supported with Adaptive Services, MultiServices, or Link Services PICs (but they are supported on the Adaptive Services Module on M7i routers, as noted above).
On M-series routers other than the M40e router, logical tunnel interfaces require an Enhanced Flexible PIC Concentrator (FPC).

For more information about configuring logical systems, see the JUNOS Routing Protocols Configuration Guide.

Configuring Logical Tunnels on J-series Platforms

On J-series Services Routers, you can configure the lt interface to provide class-of-service (CoS) support for data link switching (DLSw) traffic and real-time performance monitoring (RPM) probe packets.

Within a J-series Services Router, packets are routed to this internal interface for services. The lt interface is an internal interface only and is not associated with a physical medium or PIM. You must configure the interface for it to perform CoS for DLSW and RPM services. For more information, see the J-series Services Router Advanced WAN Access Configuration Guide.

Note: The lt interface on the J-series Services Router does not support logical systems.

[ Contents] [ Prev] [ Next] [ Index] [ Report an Error]