close

keyboard_arrow_left

Table of Contents Expand all

play_arrow Common Configuration for All VPNs
- play_arrow VPNs Overview
- play_arrow Assigning Routing Instances to VPNs
- play_arrow Distributing Routes in VPNs
- play_arrow Distributing VPN Routes with Target Filtering
- play_arrow Configuring Forwarding Options for VPNs
  - Chained Composite Next Hops for VPNs and Layer 2 Circuits
  - Example: Configuring Chained Composite Next Hops for Direct PE-PE Connections in VPNs
- play_arrow Configuring Graceful Restart for VPNs
- play_arrow Configuring Class of Service for VPNs
  - VPNs and Class of Service
  - Rewriting Class of Service Markers and VPNs
- play_arrow Pinging VPNs
play_arrow Common Configuration for Layer 2 VPNs and VPLS
- play_arrow Overview
- play_arrow Layer 2 VPNs Configuration Overview
- play_arrow Configuring Layer 2 Interfaces
- play_arrow Configuring Path Selection for Layer 2 VPNs and VPLS
  - Understanding BGP Path Selection
  - Enabling BGP Path Selection for Layer 2 VPNs and VPLS
- play_arrow Creating Backup Connections with Redundant Pseudowires
  - Redundant Pseudowires for Layer 2 Circuits and VPLS
  - Configuring Redundant Pseudowires for Layer 2 Circuits and VPLS
- play_arrow Configuring Class of Service for Layer 2 VPNs
  - Configuring Traffic Policing in Layer 2 VPNs
- play_arrow Monitoring Layer 2 VPNs
play_arrow Configuring Group VPNs
- play_arrow Configuring Group VPNv2
play_arrow Configuring Public Key Infrastructure
- play_arrow Configuring Digital Certificate Validation
  - Understanding Digital Certificate Validation
  - Example: Improving Digital Certificate Validation by Configuring Policy OIDs on an MX Series Device
- play_arrow Configuring a Device for Certificate Chains
  - IKE Authentication (Certificate-Based Authentication)
  - Example: Configuring a Device for Peer Certificate Chain Validation
- play_arrow Managing Certificate Revocation
  - Online Certificate Status Protocol and Certificate Revocation Lists
  - Example: Improving Security by Configuring OCSP for Certificate Revocation Status
play_arrow Configuring Layer 2 Circuits
- play_arrow Overview
  - Layer 2 Circuit Overview
- play_arrow Layer 2 Circuits Configuration Overview
- play_arrow Configuring Class of Service with Layer 2 Circuits
- play_arrow Configuring Pseudowire Redundancy for Layer 2 Circuits
- play_arrow Configuring Load Balancing for Layer 2 Circuits
  - Reducing APS Switchover Time in Layer 2 Circuits
- play_arrow Configuring Protection Features for Layer 2 Circuits
- play_arrow Monitoring Layer 2 Circuits with BFD
  - Configuring BFD for VCCV for Layer 2 Circuits
  - Example: Configuring BFD for VCCV for Layer 2 Circuits
- play_arrow Troubleshooting Layer 2 Circuits
  - Tracing Layer 2 Circuit Operations
play_arrow Configuring VPWS VPNs
- play_arrow Overview
- play_arrow Configuring VPWS VPNs
play_arrow Configuring VPLS
play_arrow Connecting Layer 2 VPNs and Circuits to Other VPNs
- play_arrow Connecting Layer 2 VPNs to Other VPNs
- play_arrow Connecting Layer 2 Circuits to Other VPNs
play_arrow Configuration Statements and Operational Commands
- Junos CLI Reference Overview

list Table of Contents

English

Configuring Local Interface Switching in Layer 2 Circuits

date_range 23-Nov-23

arrow_backward

arrow_forward

You can configure a virtual circuit entirely on the local router, terminating the circuit on a local interface. Possible uses for this feature include being able to enable switching between Frame Relay DLCIs.

To configure a virtual circuit to terminate locally, include the local-switching statement:

local-switching {
    interface interface-name {
        description text;
        end-interface {
            interface interface-name;
            no-revert;
            protect-interface interface-name;
        }
        ignore-mtu-mismatch;
        no-revert;
        protect-interface interface-name;
    }
}

You can include this statement at the following hierarchy levels:

[edit protocols l2circuit]
[edit logical-systems logical-system-name protocols l2circuit]

Note:
ACX Series routers do not support the [edit logical-systems] hierarchy level.

The following sections describe how to configure local interface switching:

Configuring the Interfaces for the Local Interface Switch

Local interface switching requires you to configure at least two interfaces:

Starting interface—Include the interface statement at the [edit protocols l2circuit local-switching] hierarchy level.
Ending interface—Include the end-interface statement at the [edit protocols l2circuit local-switching interface interface-name] hierarchy level.

You can also configure virtual circuit interface protection for each local interface:

Protect interface for the starting interface—Include the protect-interface statement at the [edit protocols l2circuit local-switching interface interface-name] hierarchy level.
Protect interface for the ending interface—Include the protect-interface statement at the [edit protocols l2circuit local-switching interface interface-name end-interface] hierarchy level.

For more information about how to configure protect interfaces, see Configuring the Protect Interface.

Typically, when the primary interface goes down, the pseudowire starts using the protect interface. By default, when the primary interface comes back online, the interface is switched-over back from the protect interface to the primary interface. To prevent the switchover back to the primary interface, unless the primary interface goes down, include the no-revert statement. This prevents loss of traffic during the switchover.

Note:

If the protect interface fails, the interface is switched-over back to the primary interface, irrespective of whether or not the no-revert statement is included in the configuration.

You can configure the no-revert statement both for the starting interface and the ending interface.

content_copy zoom_out_map
[edit protocols l2circuit local-switching interface interface-name]
no-revert;
end-interface {
    interface interface-name;
    no-revert;
}

Note:

The protect interface must be configured prior to configuring the no-revert statement.

Enabling Local Interface Switching When the MTU Does Not Match

You can configure a local switching interface to ignore the MTU configuration set for the associated physical interface. This enables you to bring up a circuit between two logical interfaces that are defined on physical interfaces with different MTU values.

To configure the local switching interface to ignore the MTU configured for the physical interface, include the ignore-mtu-mismatch statement:

ignore-mtu-mismatch;

You can include this statement at the following hierarchy levels:

[edit protocols l2circuit local-switching interface interface-name]
[edit logical-systems logical-system-name protocols l2circuit local-switching interface interface-name]

Note:
ACX Series routers do not support the [edit logical-systems] hierarchy level.

arrow_backward PREVIOUS Configuring Static Layer 2 Circuits

NEXT arrow_forward Configuring Interfaces for Layer 2 Circuits

Layer 2 VPNs and VPLS User Guide for Routing Devices

ON THIS PAGE

Configuring Local Interface Switching in Layer 2 Circuits

Configuring the Interfaces for the Local Interface Switch

Enabling Local Interface Switching When the MTU Does Not Match

Stay in touch

Helped me install or use the product
Accelerated my deployment

Discuss the product with a co-worker
Make a purchase inquiry