Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Add L2 Circuit VPN Nodes

Use the VPN Nodes section of the Add E-Line L2Circuit NSM 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:

  1. Click the add (+) icon above the VPN Nodes table.
    The VPN Node page appears.
  2. Enter the following details in the General section:
    1. Enter the PE device details by referring to the following table:
      Note:

      • You can add only two PE devices for a single-homed L2 circuit. You must add three devices for a multihomed L2 circuit.

      • Fields marked with an asterisk (*) are mandatory.
      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.
    2. 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

      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.

      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.

      Do not enter a transport instance ID, if you do not want to reserve a community resource during placements and you do not want to apply the community related configuration on the device.

      Note: If you are configuring multihoming on the L2 circuit, do not enter the Transport Instance ID.

      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.
  3. Click Next to proceed to the Network Access section.
  4. Click the add (+) icon above the Network Accesses table.
    The Configure Network Access page appears.
  5. Configure the network access parameters:
    1. Enter the name of the CE device and its description 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. For example, ce1.

      Port ID

      Select a PE device interface that connects to the CE device from the drop-down. For example, et-0/0/1

      Note:

      This drop-down list is empty when you configure network access parameters for the first time. This list is populated when you use the Update Placements option after you exit the VPN Node page. Continue configuring the remaining parameters and you can select the interfaces towards the end of the procedure.

      Description

      Enter a description about the CE device, if applicable.
      Access Type Specifies the access type:

      • regular—Select regular for standard Layer 2 VPN connection type between the site and service provider network.

        By default, the regular connection type is selected.

      • stitching-endpoint—Represents the initiating side of a service stitch (the creator side or the left-side of the stitch).

      • service—Represents the terminating side of a service stitch (the connector or the right-side of the stitch).
    2. 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 select dot1q or qinq to specify the type of L2 access used for the L2 circuit in the service provider network.

      When you select dot1q or qinq as the L2 access type, the Update Placements option will display only tagged interfaces for selection in the Port ID drop-down list.

      If you do not select dot1q or qinq as the L2 access type, the Update Placements option will display only untagged interfaces for selection in the Port ID drop-down list.

      Dot1q

      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.

      Expand Dot1q and configure C-VLAN ID. Enter a unique identifier for the C-VLAN.

      Enter a value in the range 1 through 4094.

      Qinq

      A Q-in-Q interface transmits and receives frames with double VLAN tags that is an inner C-VLAN and an outer service VLAN (S-VLAN). In the Q-in-Q method, the service provider adds an additional S-VLAN tag outside the C-VLAN tag, creating a double-tagged frame between the CE and PE device.

      Expand Qinq and configure C-VLAN ID and S-VLAN ID. Enter unique identifiers for the inner C-VLAN and the outer S-VLAN.

      Enter a value in the range 1 through 4094.

      Note: For migrating the Q-in-Q interface configuration in a brownfield service to Routing Director, you must configure a range of Ethernet interface units that would be associated with the service. For information, see Units.
    3. (Optional) Expand Service > Service Input Bandwidth and click the add (+) icon above the Input Bandwidth table.
      The Input Bandwidth page appears.
    4. Enter the input bandwidth parameters by referring to the following table:
      Table 5: Service Input Bandwidth Parameters (L2 Circuit)

      Field

      Description

      Type

      Select 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.
    5. Click OK.
      The input bandwidth entries are listed in the Input bandwidth table.
    6. (Optional) Click the edit or delete icons above the Input Bandwidth table to edit or delete the entries.
    7. (Optional) Expand Service > Service Output Bandwidth and click the add (+) icon above the Output Bandwidth table.
      The Output Bandwidth page appears.
    8. Enter the output bandwidth parameters by referring to the following table: .
      Table 6: Service Output Bandwidth Parameters (L2 Circuit)

      Field

      Description

      Type

      Select 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.
    9. Click OK.
      The output bandwidth entries are listed in the Output bandwidth table.
    10. (Optional) Click the edit or delete icons above the Output Bandwidth table to edit or delete the entries.
  6. Click OK on the Configure Network Access page.
  7. Click Next on the VPN Node page to proceed to the Signaling Options section.
  8. Enter the signaling parameters:
    1. 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.

    2. Expand LDP and click the add (+) icon above the AC and PW Bindings table.
      The AC and PW Bindings page appears.
    3. Enter the values by referring to the following table:
      Table 7: AC and PW Bindings Parameters (L2 Circuit)

      Field

      Description

      Peer Addr

      Configure 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. For example, 10.2.3.4.

      To configure the IP address of the peer PE device:

      1. Click the search icon next to the Peer Addr text box.

        The Choose Peer Address page appears.

      2. Select a node from the Node drop-down list.

      3. Select a corresponding loopback address from the Loopback Address drop-down list.

      4. Click OK.

        The selected loopback address is displayed in the Peer Addr text box.

      In a multihomed L2 circuit, enter the IP address of the primary peer.

      VC ID

      Enter a unique ID for the virtual circuit (VC).

      The default value of 0 allows placements to auto allocate a label. If you want to explicitly specify a label, enter a number between 1 and 4294967295.
    4. Click OK.
      The entries are listed in the AC and PW Bindings table.
    5. (Optional) Click the edit or delete icons above the AC and PW Bindings table to edit or delete the entries.
    6. Enable the Multihoming toggle on, to enable multihoming on the L2 circuit. In a multihomed L2 circuit there are three devices. For example, consider a multihomed L2 circuit between PE1, PE2, and PE3 devices. PE1 which is connected to CE1 is the local PE access node, and PE2 and PE3, both connected to CE2, are the remote PE peer nodes. The pseudowire between the access node PE1 and the primary peer PE2 is the primary active pseudowire. The pseudowire between access node PE1 and backup peer PE3 is the backup pseudowire. The following two modes are available in a multihomed L2 circuit:

      • Backup mode—In the default backup mode, there is a single active pseudowire between the access node and the remote PE node. The backup pseudowire is not pre-signalled. If the active pseudowire fails, then the backup pseudowire becomes active after a connection is established.

      • Hot-standby mode—In this mode, the backup pseudowire is pre-signalled. If the active pseudowire fails, then the backup pseudowire becomes active immediately. Since the backup pseudowire is pre-signalled, the switchover time to the backup pseudowire is reduced minimizing traffic disruption.

      Note: Enter multihoming only on the access node.
      Enter multihoming details by referring to the following table:
      Table 8: Multihoming
      Field Description

      Hot-standby

      When disabled, the default backup multihoming mode is activated. When enabled, the hot-standby mode is activated.

      Backup

      Peer Addr*

      Enter the IP address of the backup peer. For example, 10.10.10.20.

      VC Id

      Enter a VC label to identify the pseudowire. Enter 0 to allow placements to auto allocate a label. If you want to explicitly specify a label, enter a number between 1 and 4294967295.

      Revert timer

      Maximum

      Enter time in seconds for maximum period for all traffic to switch over from backup pseudowire to the primary pseudowire after the active pseudowire becomes usable. If traffic has not successfully switched over to the primary pseudowire within the entered time, the switchover is canceled and the backup pseudowire continues to transmit traffic.

      Start

      Enter time in seconds for the traffic in the backup pseudowire to switch over back to the primary pseudowire, once the primary pseudowire is restored and becomes usable after a failure.

      For example, if the start time is 10 seconds. The system will wait for 10 seconds after the primary pseudowire becomes usable again, and then start to switch over traffic.
  9. Toggle MTU Allow Mismatch to True to allow MTU mismatch for a pseudowire. This allows a pseudowire to be brought up between two logical interfaces that are defined on physical interfaces with different MTU values. It is disabled by default.
  10. Toggle Encapsulation Allow Mismatch to True to allow a Layer 2 circuit to be established even though the encapsulation configured on the CE device interface does not match the encapsulation configured on the Layer 2 circuit interface. It is disabled by default.
  11. Click Done and then click Close.
    The L2 circuit nodes and site network access parameters you entered are listed in the VPN Nodes table.
  12. Configure placement parameters for the service instance.

    1. Click the Update Placements button on top of the page and click Yes when prompted to save the service instance in its current state.

      The service instance is saved to the Routing Director database. The saved instance is listed in the Service Instances table on the Service Instances page.

      Service orchestration automatically assigns possible PE device interface placement options for the service instance. You see a message confirming that the placement is updated successfully.

    2. To configure the placement parameters, select the node for which you want to configure placement parameters, and click the edit (pencil) icon.

      The VPN Node page appears.

    3. Click Next to go to Network Accesses page, select the network access ID, and click the edit (pencil) icon.

      The Configure Network Access page appears.

    4. Configure the placement parameter by referring to the following table:

      Table 9: Placement Parameter

      Field

      Description

      Port ID

      Click the drop-down to view the updated interface placement options. Select the PE device interface that connects to the CE device. For example, et-0/0/1.

      The list displays tagged interfaces when you select dot1q as the L2 access type and untagged interfaces when you do not select the L2 access type.

    5. Edit the placement parameters for service stitching:

      • if you selected stitching-endpoint as the Access Type on the Configure Network Access page, see table for editing placement resources.

        Table 10: Stitching Interface Parameters
        Field Description

        PE

        Select the PE device where the logical tunnel interface is created.

        Logical Tunnel

        Select the logical tunnel interface (for example, lt-0/0/0) created for service stitching.

        Left Range

        Select the range of logical tunnel subinterfaces (for example, range-2) from which the subinterface for initiating the service stitch is allocated.

        Left Unit

        Enter the subinterface on the left-side of the logical tunnel interface.

        Right Range

        Select the range of logical tunnel subinterfaces (for example, range-1) from which the subinterface for terminating the service stitch is allocated.

        Right Unit

        Enter the subinterface on the right-side of the logical tunnel interface.

      • If you selected service as the Access Type on the Configure Network Access page, see Table 11 to edit placement resources.

        Table 11: Interface for Peering Service Parameters
        Field Description

        Service Instance

        Select the service instance that initiates the service stitch or the service instance on the left-side of the service stitch.

        PE

        Select the provider edge device on the terminating side or the right-side of the stitch.

        Network Access

        Select the network access reference on the initiating side or the left-side of the service stitch.

        Logical Tunnel Interface Left

        View the LT interface on the right side of the stitch.

    6. Click OK to exit the Configure Network Access page.

      The Network Accesses table displays the interface that you configured. You can also view connection type and C-VLAN ID, if configured.

    7. Click Next to view the Signaling Options page and then click Done and Close to exit the VPN Node page.

      The selected interface is displayed in the Ports column of the VPN Nodes table.

  13. 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.

Related Documentation