close

keyboard_arrow_left

Table of Contents Expand all

play_arrow Introduction
- play_arrow Overview
- play_arrow Access and Manage Paragon Automation Account
play_arrow Administration
- play_arrow Introduction
  - Administration Overview
  - Administration Workflow
- play_arrow Organization Management
- play_arrow Site Management
- play_arrow User Management
- play_arrow Inventory Management
- play_arrow Audit Logs
  - Audit Logs Overview
  - About the Audit Logs Page
- play_arrow Tags
  - About the Tags Page
  - Manage Tags
play_arrow Device Life Cycle Management
- play_arrow Introduction
- play_arrow Day-Wise Activities for Device Life Cycle Management
- play_arrow Field Technician User Interface
  - Field Technician UI Overview
  - Working with Field Technician UI Pages
- play_arrow Onboarding Profiles
- play_arrow Plan Device Onboarding
- play_arrow View Device Onboarding
- play_arrow Device Management
play_arrow Observability
- play_arrow Introduction
  - Observability Overview
- play_arrow Health Dashboard
- play_arrow Troubleshoot Devices
- play_arrow View Network Topology
play_arrow Trust and Compliance
- play_arrow Introduction
  - Trust and Compliance Overview
  - Perform Compliance Scan and Manage Checklists
- play_arrow Manage Trust Settings and Trust Scores
- play_arrow Manage Compliance Scans
- play_arrow Manage Vulnerabilities
- play_arrow Monitor Integrity
play_arrow Service Orchestration
- play_arrow Introduction
  - Service Orchestration Overview
  - Service Provisioning Workflow
- play_arrow View Service Design Catalog
- play_arrow Manage Customers
- play_arrow Add Resources for Network Services
- play_arrow Manage Service Instances
- play_arrow Provision VPN Services
- play_arrow Monitor Service Order Execution Workflows
play_arrow Active Assurance
- play_arrow Introduction
- play_arrow Test Agents
- play_arrow Tests and Monitors
- play_arrow Test Templates
  - About the Test Templates Page
  - Create a Test Template
play_arrow Paragon Shell CLI Reference

list Table of Contents

English

keyboard_arrow_right

Add L2 Circuit VPN Nodes

date_range 14-Nov-24

arrow_backward

arrow_forward

Use the VPN Nodes section of the Add L2 Circuit page to enter details about the VPN nodes. VPN nodes refer to the PE devices through which the L2 circuit spans in the service provider MPLS network, and which transfer data between the CE devices.

You can configure the following in the VPN Nodes section:

Details about PE nodes such as the VPN node ID and underlay transport details.
Site network access details such as the CE device that the PE device connects to, PE interface used to connect to the CE device, connection, and service parameters.
Signaling type used between PE devices in the service provider network.

Prerequisite

Before adding the L2 circuit node details, you must create an L2 circuit service instance and enter general details about the service. Follow steps 1 to 4 of the Add an L2 Circuit Service Instance procedure to create a new instance and add L2 circuit service general details.

To add L2 circuit node details in the VPN Nodes section:

Click the add (+) icon above the VPN Nodes table.
The VPN Node page appears.

Enter the following details in the General section:

Enter the PE device details by referring to the following table:

Note:

You can add only two PE devices for an L2 circuit.

Table 1: PE Device Details (L2 Circuit)
Field	Description
VPN Node ID	Click the drop-down to select the PE device name for the L2 circuit.
Description	Enter a description about the device, if applicable.

Expand Underlay Transport and enter the underlay transport details by referring to the following table:

Table 2: Underlay Transport Details (L2 Circuit)
Field	Description
Transport Instance ID	(Optional) Enter a unique name for the tunnel or LSP used to transport the L2 circuit. To get the LSP name, log in to the PE router and execute the `run show mpls lsp` command. The LSP name is displayed in the Ingress LSP > LSPname output field. Enter the LSP name in the Transport Instance ID field. Note: The transport instance ID is an optional field. If you do not provide the LSP name, any available LSP on the PE device is used to send network traffic.
Instance Type	Specify the instance type or type of tunnel used between the PE devices in the service provider network to transport the L2 circuit or connection. LSP is the only instance type that is supported in this release.

Click Next to proceed to the Network Access section.
Click the add (+) icon above the Network Accesses table.
The Configure Network Access page appears.

Configure the network access parameters:

Enter the name of the CE device and PE interface ID by referring to the following table:

Table 3: Network Access Parameters (L2 Circuit)
Field	Description
ID	Enter a unique ID for the CE device that connects to the PE device interface.
Port ID	Enter the ID of the PE device interface that connects to the CE device. For example, et-0/0/0/1
Description	Enter a description about the CE device, if applicable.

Expand Connection > Encapsulation and enter the connection parameters by referring to the following table:

Table 4: Connection Parameters (L2 Circuit)
Field	Description
L2 Access Type	Click the L2 Access Type drop-down and click dot1q to specify the type of L2 access used for the L2 circuit in the service provider network. Dot1q is the only L2 access type that is supported in this release. The IEEE 802.1Q standard or Dot1q is a method of tagging or encapsulating Ethernet frames with VLAN tags. The service provider tags packets between CE and PE devices with one or more customer VLAN (C-VLAN) IDs to identify which VLAN the frame belongs to.
C-VLAN ID	(Optional) Expand Dot1q and in the C-VLAN ID field, enter a unique ID for the C-VLAN. Enter a value from 512 to 65,535.

(Optional) Expand Service > Service Input Bandwidth and click the add (+) icon above the Input Bandwidth table.
The Input Bandwidth page appears.

Enter the input bandwidth parameters by referring to the following table:

Table 5: Service Input Bandwidth Parameters (L2 Circuit)
Field	Description
Type	Specify the type of download bandwidth from the service provider network to the site. Bandwidth per port (bw-per-port) is the only input bandwidth type that is supported in this release. This bandwidth type refers to the input bandwidth per network access (connection) on the CE device.
CBS	Enter the Committed Burst Size (CBS) in bytes per second (Bps). When network traffic does not utilize the configured Committed Information Rate (CIR), the unused bandwidth is accumulated up to a maximum limit defined by the CBS.
CIR	Enter the CIR or the maximum number of bits per second (bps) that an interface can receive. The service provider provides the CIR as the guaranteed bandwidth for network traffic that an interface can receive in one second, under normal line conditions.

Click OK.
The input bandwidth entries are listed in the Input bandwidth table.
(Optional) Click the edit or delete icons above the Input Bandwidth table to edit or delete the entries.
(Optional) Expand Service > Service Output Bandwidth and click the add (+) icon above the Output Bandwidth table.
The Output Bandwidth page appears.

Enter the output bandwidth parameters by referring to the following table: .

Table 6: Service Output Bandwidth Parameters (L2 Circuit)
Field	Description
Type	Specify the type of upload bandwidth from the site to the provider network. Bandwidth per port (bw-per-port) is the only output bandwidth type that is supported in this release. This bandwidth type refers to the output bandwidth per network access (connection) on the CE device.
CBS	Enter the Committed Burst Size (CBS) in bytes per second (Bps). When network traffic does not utilize the configured Committed Information Rate (CIR), the unused bandwidth is accumulated up to a maximum limit defined by the CBS.
CIR	Enter the CIR or the maximum number of bits per second (bps) that an interface can send. The service provider provides the CIR as the guaranteed bandwidth for network traffic that an interface can send in one second, under normal line conditions.

Click OK.
The output bandwidth entries are listed in the Output bandwidth table.
(Optional) Click the edit or delete icons above the Output Bandwidth table to edit or delete the entries.

Click OK on the Configure Network Access page.
Click Next on the VPN Node page to proceed to the Signaling Options section.

Enter the signaling parameters:

Click the Type drop-down and click ldp-signaling.
Use this field to define the signaling type that is used between the PE devices in the service provider MPLS network, to create an L2 circuit.

MPLS Label Distribution Protocol (LDP) is the only signaling protocol supported in this release.
Expand LDP and click the add (+) icon above the AC and PW Bindings table.
The AC and PW Bindings page appears.

Enter the values by referring to the following table:

Table 7: AC and PW Bindings Parameters (L2 Circuit)
Field	Description
Peer Addr	Enter the IP address of the peer PE device with which the PE device communicates using LDP, to create an L2 circuit through the MPLS network.
VC ID	Enter a unique ID for the virtual circuit (VC). Toggle one of the following options: Auto—The VC ID is automatically allocated from the options that you configured in the network resource pool. The Auto option is toggled on by default. Explicit—Enter the VC ID manually. To enter the VC ID manually, switch the Auto toggle off and enter the ID in the VC ID field.

Click OK.
The entries are listed in the AC and PW Bindings table.
(Optional) Click the edit or delete icons above the AC and PW Bindings table to edit or delete the entries.

Click Done.
The L2 circuit nodes and site network access parameters you entered are listed in the VPN Nodes table.
Proceed to step 6 of the Add an L2 Circuit Service Instance procedure to complete the remaining steps for creating the L2 circuit service instance.

arrow_backward PREVIOUS Add an L2 Circuit Service Instance

NEXT arrow_forward Modify a Service Instance

Juniper Paragon Automation User Guide

Add L2 Circuit VPN Nodes

Stay in touch

Helped me install or use the product
Accelerated my deployment

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

Juniper Paragon Automation User Guide

Add L2 Circuit VPN Nodes

Related Documentation

Stay in touch