Creating an E-Line ATM or TDM Pseudowire Service Definition

This procedure provides the steps to create a definition for an E-Line 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 E-Line ATM or TDM services on the network.

The windows 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 an E-Line service definition, complete these tasks, in the order shown:

Specifying General Information for the ATM or TDM Service

In the Build mode of the Network Services > Connectivity task pane, select Service Design > Manage Service Definitions > New > E-Line Service Definition.
The first Create E-Line Service Definition window appears.
In the Name box, type a name for the service definition.
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.
(Optional) In the Description box, type a brief description or other comment that you want to appear in the Service Definition table.
(Optional) For an ATM or TDM service, only l2vpn instance type is available if the signaling type is BGP.
The instance type field is not available for LDP signaling type.
The Enable Multihoming check box is optional and is not available if the signaling type is LDP.
(Optional) To include a service template for the service, click the Add icon or plus sign (+) to select a service template from the Service Template list. The list of available service templates is displayed. Select the check box beside the template you want and click OK. You are returned to the General Settings page.
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 window, 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.
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.
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 E-Line 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 E-Line pseudowire stitching, see Stitching Two E-Line Pseudowires.
Select the Static pseudowire check box to indicate whether the E-Line service definition is a static pseudowire.
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.
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, and not the interface-related traps (such as jnxVpnIfUp or jnxVpnIfDown).
Click Next to continue to the Connectivity Settings window.

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:

Fill in the fields as indicated in the table.

Field	Action
Physical Interface 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.
Autopick VPI	Select the virtual path identifier (VPI). The combination of the VPI and VCID defines the next destination for a cell in the ATM network.
Autopick VCI	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.

Click Next to go to the Connectivity Settings window.

Specifying UNI Settings for TDM Interfaces

To specify the UNI settings for TDM interfaces:

Select the type of Physical Interface 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 Interface Encapulsation is not editable in service order.

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

Table 1:
SAToP Field	Value Range	Default Value
Jitter buffer	M Series: 1 through 340	5
Jitter buffer	M Series: 1 through 340	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 Interface 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.

Click Next to go to the Connectivity Settings window.

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 window follows.

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.
Enable Multihoming	This check box is available only if the signaling type is BGP.
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. Range: 1.1.1.1:1 through 255.255.255.254:65535, or 1:1 through 65535:4294967295
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. Range: 1.1.1.1:1 through 255.255.255.254:65535, or 1:1 through 65535:4294967295
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.

Click Review to examine the settings configured for the E-Line ATM/TDM service definition.

Reviewing the Configured Settings

The Review page of the service definition or service order creation and modification wizards enable you to view and evaluate the service parameters and components you configured in preceding steps or pages of the wizard. This page provides a comprehensive, single-page view of all the service elements configured in the different pages of the wizard. You can either click the buttons corresponding to the various settings at the top of the wizard page to directly traverse to the page you want to modify or click the navigation buttons at the bottom of the wizard page to go to the different pages of the wizard.

Note:

On the Review page, in the Service Templates section, the names of the service templates with which the service definition is associated are displayed. The Default Service Template column indicates whether the attached template is the default template.

To examine and modify the configured service definition settings:

Click Review to view the defined parameters. You can examine and modify the created service order parameters. Alternatively, click the corresponding buttons at the top of the wizard page to navigate to the specific pages pertain to the settings you want to modify.
Click Edit next to the section that contains the parameter you want to modify. You are navigated to the corresponding page of the wizard in which the parameter settings are defined.
Click Finish to save the service definition or service order.
Click Back to return to the previous page of the wizard; else click Cancel to discard the changes.
When the service definition is successfully created, you are returned to the Manage Service Definitions window.

ON THIS PAGE