Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Creating a Point-to-Point ATM or TDM Pseudowire Service Definition

 

This procedure provides the steps to create a definition for a point-to-point ATM or TDM service. The standard service definitions that came with your initial software installation are designed to be appropriate for most requirements. You can also create a customized service definition—for example, to set different bandwidth limits on the service than those offered in the standard service definitions.

After the new service definition is complete and published, network operators or service provisioners can use the completed service definition as a base for creating and then activating point-to-point ATM or TDM services on the network.

The pages appear in the order shown. You can, however, perform these steps in any order by accessing them through the task list in the right panel. If the panel is not visible, click the snap tool on the right side of the main display area.

To create a point-to-point service definition, complete these tasks, in the order shown:

Specifying General Information for the ATM or TDM Service

  1. In the Network Activate task pane, select Service Design > Manage Service Definitions > Create P2P Service Definition.

    The first Create Service Definition page appears.

  2. In the Name box, type a name for the service definition.
  3. Select the signaling type:
    • LDP

    • BGP

    Note

    If the signaling type is BGP, the Static pseudowire, Enable PW Resiliency, Enable Multi Segment Pseudowire and the Enable PW access to L3 VPN network check boxes are not available.

  4. (Optional) In the Comments box, type a brief description or other comment that you want to appear in the Service Definition table.
  5. (Optional) To include a service template for the service, select a service template from the Service Template list.

    The selected service template appears in the Default Service Template field.

    You can select one or more service templates as the default service template. By default, the default service templates are attached to the endpoints.

    Note

    You cannot add or delete a service template while creating a service order.

    The remaining service templates on the Service Template list are termed as optional service templates. You can attach the optional service templates to the endpoints on a need basis.

    In the View Service Definition Details page, the value for the default service template in the Default Service Template column is True.

    For instructions on creating a service template, see Creating a Service Template.

  6. Select the interface type. If you select TDM or ATM as the interface type, the Enable PW access to L3 VPN network check box is unavailable.
  7. Select the Enable Multi Segment Pseudowire check box to enable multi-segment pseudowire. This check box is available for LDP signaling only

    A multi-segment pseudowire is a static or dynamically configured set of two or more contiguous pseudowire segments that behave and function as a single point-to-point pseudowire. Each end of a multi-segment pseudowire, by definition, terminates on a T-PE.

    Note

    The number of pseudowire segments that you can stitch is limited to two.

    For more information on point-to-point pseudowire stitching, see Stitching Two Point-to-Point Pseudowires.

  8. Select the Static pseudowire check box to indicate whether the point-to-point service definition is a static pseudowire.
  9. To enable the pseudowire resilency, select the Enable PW Resiliency check box. For more information on pseudowire redundancy, see Redundant Pseudowires for Layer 2 Circuits and VPLS.
  10. By default, all the events are saved in the OpenNMS database. To isolate the events related to an interface in the OpenNMS, select the Decouple Service Status From Port Status check box.Note

    When you select this check box, only the pseudowire traps are monitored, not the jnxVpnIfVpn traps.

  11. Click Next to continue to the Connectivity Settings page.

Specifying UNI Settings for ATM and TDM Service Definitions

In this step, you provide the UNI service attributes for this service definition. The attributes you set depend on whether you are setting attributes for an ATM or for a TDM interface.

Specifying UNI Settings for ATM Interfaces

To specify the UNI settings for ATM interfaces:

  1. Fill in the fields as indicated in the table.

    Field

    Action

    Physical IF encapsulation

    Select the type of encapsulation to apply to the interface. Use atm-ccc-cell-relay for ATM cell relay encapsulation. Use atm-ccc-cell-mux for ATM VC for CCC.

    VPI selection

    Select the virtual path identifier (VPI).

    The combination of the VPI and VCID defines the next destination for a cell in the ATM network.

    VCI selection

    Select the virtual channel identifier (VCID)—This integer uniquely identifies the virtual circuit that the service uses.

    The VCID can be either set automatically by the Junos Space software, or the service provisioner can set it manually in the service order. The service definition can force the system to pick the VCID, force the service provisioner to pick the VCID, or allow the service provisioner to override the settings in the service definition.

    We recommend allocating the VCID automatically; however, service providers with their own systems for allocating VCIDs may choose the manual setting.

    In the previous example, by default, the system picks a VCID from its pool automatically, but allows the service provisioner to override this value in the service order. Clear the check box to override the service definition setting. The form expands to include an additional field for entering the VCID manually.

    Cell bundle size

    The range for the cell bundle size can be 1 through 34.

  2. Click Next to go to the Connectivity Settings page.

Specifying UNI Settings for TDM Interfaces

To specify the UNI settings for TDM interfaces:

  1. Select the type of Physical IF encapsulation.

    • SAToP—Structure-Agnostic time-division multiplexing (TDM) over Packet (SAToP), as defined in RFC 4553, Structure-Agnostic TDM over Packet (SAToP) is used for pseudowire encapsulation for TDM bits (T1, E1). The encapsulation disregards any structure imposed on the T1 and E1 streams, in particular the structure imposed by standard TDM framing. SAToP is used over packet-switched networks, where the provider edge (PE) routers do not need to interpret TDM data or participate in the TDM signaling.

    • CESoPSN—Circuit Emulation Service over Packet-Switched Network (CESoPSN) bundle represents an IP circuit emulation flow. With CESoPSN bundles, you can group multiple DS0s on one IP circuit, and you can have more than one circuit emulation IP flow created from a single physical interface. For example, some DS0 channels from a T1 interface can go in an IP flow to destination A, and other DS0 channels from that same T1 interface can go to destination B.

    Note

    The Physical IF encapulsation is not editable in service order.

  2. Fill in the SAToP and CESoPSN fields as indicated in the table.

    SAToP Field

    Value Range

    Default Value

    Jitter buffer

    M Series: 1 through 340

    5

    BX7000 Gateway: 2K through 32K

    There is no default value for the jitter buffer on BX7000 Gateway devices. You must specify a value.

    Idle pattern

    0 through 255

    255

    Excessive packet loss rate

    1 through 100%

    20%

    Payload size

    Note: If the Physical IF encapulsation type is CESoPSN, the Payload size is unavailable.

    M Series: 64 through 1024

    192

    Note: For M Series, the value you specify must be a multiple of 32.

    BX7000 Gateway: 24 through 1440

  3. Click Next to go to the Connectivity Settings page.

Specifying Connectivity Information for an ATM or a TDM Service

In this step, you specify the attributes that define the connectivity between remote sites across the service provider network. A sample page follows.

  1. Provide the following information to create connectivity between sites across the network:

    Field

    Action

    VC ID selection

    This box is available only if the Signaling is LDP.

    Specify how you want the VC ID chosen during service order creation:

    • To allow the service provisioner to type the VC ID, choose Select manually.

    • To cause the Junos Space software to assign a VC ID automatically from the VC ID pool, select Auto pick.

    To allow the service provisioner to override the setting in the VC ID box, select Editable in Service Order.

    Default MTU (Bytes)

    Specify the MTU across the service provider network.

    To allow the service provisioner to override the MTU setting, select Editable in Service Order.

    MTU range (Bytes)

    Specify the highest and lowest MTU that the service provisioner can type.

    Range: 1522 bytes through 9192 bytes

    Revert time (sec)

    This box is available only if the Signaling is LDP.

    Revert time for redundant Layer 2 circuits and VPLS pseudowires.

    Default: 5 seconds

    Range: 0 through 65,535 seconds

    Switch Over Delay (sec)

    This box is available only if the Signaling type is LDP.

    Specify the delay to wait before the backup pseudowire takes over.

    Default: 0 second

    Range: 0 through 180 seconds

    Route Distinguisher

    This box is available only if the Signaling type is BGP.

    Specify an identifier attached to a route, enabling you to distinguish to which VPN the route belongs. Each routing instance must have a unique route distinguisher associated with it.

    Note: The IPv4 and IPv6 addresses that you use must be valid addresses. Refer to http://www.iana.org/assignments/ipv4-address-space for the list of restricted IPv4 addresses and http://www.iana.org/assignments/ipv6-address-space for the list of restricted IPv6 addresses.

    Route Target

    This box is available only if the Signaling is BGP.

    Allows you to distribute VPN routes to only the routers that need them.

    Note: The IPv4 and IPv6 addresses that you use must be valid addresses. Refer to http://www.iana.org/assignments/ipv4-address-space for the list of restricted IPv4 addresses and http://www.iana.org/assignments/ipv6-address-space for the list of restricted IPv6 addresses.

    Outgoing label selection

    This field is available only if you have selected the Static pseudowire check box in the General settings. By default, the outgoing label selection is limited to manual.

  2. Click Finish to create a point-to-point ATM/TDM service definition.