Overview of RAN Backhaul Services
Radio access network (RAN) transport manages the backhaul traffic (both voice and data) from the cell site base transceiver stations (BTSs) to aggregation nodes and to base station controllers (BSCs), between BSCs, and between the BSC and an associated mobile switching center (MSC). Figure 5-1 shows an example RAN backhaul topology.
Figure 5-1 Example RAN Backhaul Topology
Figure 5-2 is an abstracted topology view that is used in this chapter when discussing how to configure RAN backhaul services in the Prime Provisioning GUI.
Figure 5-2 Abstracted RAN Backhual Topology
Prime Provisioning is able to provision Internet Protocol based Radio Access Networking (IP RAN) services. This is performed through the Ethernet Virtual Circuit (EVC) policies and service requests within Prime Provisioning to configure the following services to enable RAN backhaul services:
-
Circuit Emulation Time Delay Multiple Access (TDM-CEM)
-
Pseudowire provisioning of Asynchronous Transfer Mode (ATM)
In addition, the EVC service requests use CEM and pseudowire class objects to bundle common attributes for resuse on every node where the service is provisioned.
The basic workflow for configuring and managing RAN backhaul services in Prime Provisioning, involves the following tasks:
1. Verify prerequisites and preform necessary setup tasks.
2. Create CEM and/or pseudowire classes to be used in RAN backhaul policies and service requests.
3. Create the TDM-CEM or ATM policy.
4. Create template(s) for use in the TDM-CEM or ATM service request.
5. Create the TDM-CEM or ATM service request.
6. Deploy the service request to the device(s) on the network.
In this chapter, the above workflow tasks are documented for the ATM service.
Creating an ATM Policy
This section describes how to create an ATM policy.
You must define an ATM policy before you can provision a service. A policy can be shared by one or more service requests that have similar service requirements. A policy is a template of most of the parameters needed to define a the service request. After you define the policy, it can be used by all the service requests that share a common set of characteristics. You create a new ATM policy whenever you create a new type of service or a service with different parameters.
You can also associate Prime Provisioning templates and data files with a policy. See Using Templates with Policies. for more about using templates and data files in policies.
It is also possible to create user-defined attributes within a policy (and service requests based on the policy). For background information on how to use the additional information feature, see
Appendix D, “Adding Additional Information to Services.”
To start defining an ATM policy, perform the following steps.
Step 1 Choose
Service Design
>
Policies > Policy Manager
.
The Policy Manager window appears.
Step 2 Click
Create
.
The Policy Editor window appears.
Step 3 Choose
EVC
from the Policy Type drop-down list.
The Policy Editor window appears.
Step 4 Enter a
Policy Name
for the EVC policy.
Step 5 Choose the
Policy Owner
for the EVC policy.
There are three types of EVC policy ownership:
-
Customer ownership
-
Provider ownership
-
Global ownership—Any service operator can make use of this policy.
This ownership has relevance when the Prime Provisioning Role-Based Access Control (RBAC) comes into play. For example, an EVC policy that is customer-owned can only be seen by operators who are allowed to work on this customer-owned policy. Similarly, operators who are allowed to work on a provider’s network can view, use, and deploy a particular provider-owned policy.
Step 6 Click
Select
to choose the owner of the EVC policy.
The policy owner was established when you created customers or providers during Prime Provisioning setup. If the ownership is global, the Select function does not appear.
Step 7 Choose the
ATM
as the
Policy Type
.
Step 8 Click
Next
.
The Create New EVC Policy window appears.
Step 9 Continue with the steps contained in the next section, Setting the ATM Interface Attributes.
Setting the ATM Interface Attributes
This section describes how to set the ATM Interface attributes for the ATM policy.
To set the ATM interface attributes, perform the following steps.
Step 1 Choose the
Transport Mode
from the drop-down list. The choices are:
-
VP
—Virtual path mode. This is the default.
-
VC
—Virtual circuit mode. If this option is chosen, an ATM Encapsulation attribute appears in the GUI with a default value of AAL0. The ATM Encapsulation cannot be changed.
Step 2 Click
Next
.
The Policy Editor window appears, displaying the Service Attributes section.
Step 3 Continue with the steps contained in the next section, Setting the Service Attributes.
Setting the Service Attributes
To set the service attributes, perform the following steps.
Step 1 Check the
Enable PseudoWire Redundancy
check box to enable pseudowire redundancy (alternative termination device) under certain conditions.
Step 2 Check the
AutoPick VC ID
check box to have Prime Provisioning autopick the VC ID during service request creation.
If this check box is unchecked, the operator will be prompted to specify a VC ID during service request creation.
Usage notes:
-
When AutoPick VC ID is checked, Prime Provisioning allocates a VC ID for pseudowires from the Prime Provisioning-managed VC ID resource pool.
Step 3 Click
Next
.
The Policy Editor window appears, displaying the Pseudowire section.
Step 4 Continue with the steps contained in the next section, Using Pseudowire Classes.
Using Pseudowire Classes
To specify a pseudowire class to be used by the ATM policy, perform the following steps.
Step 1 Check the
Use PseudoWireClass
check box to enable the selection of a pseudowire class.
This attribute is unchecked by default.
Usage notes:
-
The pseudowire class name is used for provisioning
pw-class
commands on IOS devices. See Creating and Modifying Pseudowire Classes for additional information on pseudowire class support for IOS XR devices.
-
If
Use PseudoWireClass
is checked, an additional attribute,
PseudoWireClass
, appears in the GUI. Click the
Edit
button to choose a pseudowire class previously created in Prime Provisioning.
-
Use PseudoWireClass is only applicable for IOS devices.
Step 2 Click
Next
.
The Policy Editor window appears.
Step 3 Continue with the steps contained in the next section, Adding User-Defined Fields into the ATM Policy Workflow.
Enabling Template Association
The Prime Provisioning template feature gives you a means to download free-format CLIs to a device. If you enable templates, you can create templates and data files to download commands that are not currently supported by Prime Provisioning.
Note Template variable support is available for ATM policies and services. An example template and data file is available containing the ATM-related variables. See the section Using Template Variables in ATM Services, for how to access and use this template.
Step 1 To enable template association for the policy, click the
Next
button in the Policy Editor window (before clicking
Finish
).
The Policy Editor window appears, displaying the Template Information section. In this window, you can enable template support and, optionally, associate templates and data files with the policy. For instructions about associating templates with policies and how to use the features in this window, see Using Templates with Policies.
Step 2 When you have completed setting up templates and data files for the policy, click
Finish
in the Template Information window to close it and return to the Policy Editor window.
Step 3 To save the ATM policy, click
Finish
.
To create a service request based on an ATM policy, see Managing an ATM Service Request.
Using Template Variables in ATM Services
This section describes how to access and use the example ATM template in Prime Provisioning.
To create a data file for the example ATM template, perform the following steps.
Step 1 In the Prime Provisioning GUI, choose
Service Design
>
Templates > Template Manager
.
The Template Manager window appears.
Step 2 In the
Templates
window, click on the root folder to expand it.
A list of subfolders appears, with the Examples folder on top.
Step 3 Click the Examples folder to expand it.
Several sample templates are visible, including the ATM template.
Step 4 Click on the ATM folder to choose it.
The ATM template shows in the Template window, along with a pre-loaded ATMData data file in the Data File Name column of the table.
Step 5 Either click the
Edit
button to edit the ATMData data file or else uncheck it and click
Create
Data File to create and new one.
In either case, the Data File Editor window appears. You can use this file to map the template variables required for provisioning ATM services.
Step 6 When you have made the desired changes to the templates variables, click
Save
to save the changes.
Step 7 Click
Close
to close the Data File Editor window.
Creating an ATM/IMA Interface Using Templates
ATM/IMA interfaces are created in the device that needs to be provisioned. If they have not been previously created on the device manually, they can be created through the Device Console by using templates. Once the ATM/IMA interfaces are created in the device through Device Console, you must perform a Config collection task for the device. After the Config collection, the Prime Provisioning inventory (repository) is populated with the newly created ATM/IMA interfaces. These interfaces can then be used for ATM service provisioning.
Creating Template and Data File and Downloading it to a Device.
Note The steps below are presented at a high-level and assume a basic working-knowledge of using templates and data files in Prime Provisioning. If you require more detailed information on the steps necessary to create templates and data files, see Chapter11, “Managing Templates and Data Files”
Perform the following steps.
Step 1 Choose
Service Design
>
Templates
>
Template Manager
.
Step 2 In the
Template Manager
tree, click on the Example folder to expand it.
Step 3 Create an IMA template as shown below and Save
Step 4 Click on the
Create Template
button to create the IMA template.
The Template Editor window appears.
Step 5 Enter the following:
-
Template Name
(required)—For example, “IMA MWR 2941,” or whatever name you choose.
-
Description
(optional).
-
Body
(required)—Enter the configuration text, Velocity Template Language (VTL) directives, and variables that you want included. An example is:
controller $container $slot/$sub-slot
Where:
–
container
is of string type with value either as
E1
or
T1
.
–
slot
and
sub-slot
refer to the respective slot and sub-slot.
–
option
value is of string type with value either
internal
or
line
.
–
ima
value is of interger type with minimum value of 0 and maximum value of 23.
Step 6 Click
Save
to save the template.
Step 7 Create an appropriate data file with values mentioned as defined in the previous step.
Now use the Device Console to select the device and specify the data file as follows.
Step 8 Choose
Inventory
>
Device Tools > Device Console
.
The Choose Operation window appears.
Step 9 Select
Download Template
and click
Next
.
The Download Template window appears.
Step 10 To add devices, click
Add
.
Step 11 From the resulting Device Selection window, check the check box(es) for each device you want to select.
Step 12 Click
Select
.
You return to the Download Template window with the added devices.
Step 13 Click
Next
.
The window refreshes, allowing you to add device groups.
Step 14 Click Next.
The window refreshes, allowing you to choose a template to download.
Step 15 Click the
Select
button.
The Add/Remove Template window appears.
Step 16 Click
Add
to add templates or
Remove
to remove templates.
When you click
Add
you get a Template Datafile Chooser window with the template choices in the tree. Navigate the folders and subfolders in the tree to find the ATM/IMA template you created previously.
Step 17 .When you have the template you want, click
OK
.
Step 18 Select the data file you created previously and click
Accept
.
You return to the Download Template window, which shows the updated information.
Step 19 Click
Next.
The Template Summary section appears in the window.
Step 20 Check the check boxes for
Upload Config After Download
and
Retrieve device attributes
.
Checking these check boxes will perform a Collect Config on the device when the template download is submitted. This causes the device configuration with the template additions to be updated in the Prime Provisioning inventory/repository.
Note You can also run the Collect as a separate task, as covered in the next section Adding ATM/IMA Interfaces to the Inventory.
Step 21 Click
Finish
to submit the download.
You receive a message showing the status.
Step 22 Click
Done
.
Adding ATM/IMA Interfaces to the Inventory
You can separately run a Config collection task for a device in order to populate the inventory with the ATM/IMA interfaces previously downloaded via template. This section describes how to connect to the physical device in the network, collect the device information, and populate the repository.
Perform the following steps.
Step 1 Choose
Operate
>
Tasks > Task Manager
.
The Choose Operation window appears.
Step 2 Click
Create
.
Step 3 Choose
Collect Config
.
The Create Task window appears.
Tip You might want to change the default Name and Description for this task, so you can more easily identify it in the task log.
Step 4 Click
Next
.
The Collect Config Task window appears.
Step 5 To choose devices associated to the task, in the Devices panel, click
Select
.
The Select Device window appears.
Step 6 Check to choose the desired device(s), then click
Select
.
The Collect Config Task window reappears.
Step 7 To choose device groups associated to the task, in the Groups panel, click
Select
.
A list of available device groups appears.
Step 8 Check to choose the desired device group(s), then click
Select
.
The Collect Config Task window reappears.
Step 9 Set schedule and task owner, if applicable.
Step 10 Click
Submit
.
The Tasks window appears.
Step 11 Choose your task in the Task Name column, then click
Details
to view more information.
The result of the Collect Config task is that the ATM/IMA interfaces created via the template previously download to the device will be updated in the device configuration in the Prime Provisioning inventory/repository.
Managing an ATM Service Request
This section describes the various tasks of the workflow involved in managing ATM service requests to support RAN backhaul services. It contains the following sections:
Creating an ATM Service Request
To begin creating the ATM service request, perform the following steps.
Step 1 Choose
Operate > Service Requests > Service Request Manager
.
The Service Request Manager window appears.
Step 2 Click
Create
.
The Service Request Editor window appears.
Step 3 From the Policy drop-down list, choose an ATM policy from the policies previously created (see Creating an ATM Policy). This will be a policy of type EVC, as noted by (EVC) following the policy name.
The EVC Service Request Editor window appears. This is the first window of the workflow, in which you can add and modify attributes for the service request. The new service request inherits all the properties of the chosen policy, such as all the editable and non-editable features and pre-set parameters.
The attributes in this window describe the pseudowire connectivity between the attachment circuits. The pseudowire connectivity allows you to create a point-to-point connection between two customer sites using X-connect (that is, cross connection).
Step 4 Continue with the steps contained in the next section, Setting the Service Request Details.
Setting the Service Request Details
To set the attributes in the Service Request Details section, perform the following steps.
Note The Job ID and SR ID fields are read-only. When the service request is being created for the first time, the fields display a value of NEW. When an existing service request is being modified, the values of the fields indicate the respective IDs that the Prime Provisioning database holds within the editing flow of the service request.
Note The Policy Name field is read-only. It displays the name of the policy on which the service request is based. Clicking on the read-only policy name displays a list of all the attribute values set within the policy.
Step 1 Check the
AutoPick VC ID
check box if you want Prime Provisioning to choose a VC ID.
If you do not check this check box, you will be prompted to provide the ID in the VC ID field, as covered in the next step.
When AutoPick VC ID is checked, Prime Provisioning allocates a VC ID for pseudowires from the Prime Provisioning-managed VC ID resource pool. In this case, the text field for the VC ID option is non-editable.
Step 2 If AutoPick VC ID was unchecked, enter a VC ID in the
VC ID
field.
Usage notes:
-
The VC ID value must be an integer value corresponding to a VC ID.
-
When a VC ID is manually allocated, Prime Provisioning verifies the VC ID to see if it lies within Prime Provisioning’s VC ID pool. If the VC ID is in the pool but not allocated, the VC ID is allocated to the service request. If the VC ID is in the pool and is already in use, Prime Provisioning prompts you to allocate a different VC ID. If the VC ID lies outside of the Prime Provisioning VC ID pool, Prime Provisioning does not perform any verification about whether or not the VC ID allocated. The operator must ensure the VC ID is available.
-
The VC ID can be entered only while creating a service request. If you are editing the service request, the VC ID field is not editable.
Step 3 Check the
PseudoWire Redundancy
check box to enable pseudowire redundancy (alternative termination device) under certain conditions.
Usage notes:
-
When PseudoWire Redundancy is unchecked, pseudowire redundancy is not provisioned in the service request. Therefore, there will be only two devices actively contributing to the service. See Figure 5-4 for an example configuration. One device is the “A” side of the pseudowire and one side is the “Z” side of the pseudowire. In this case, you would not be able to enter a Backup PW VC ID
.
Figure 5-4 Pseudowire Termination Example
Step 4 If appropriate for the configuration, enter a VC ID for the backup pseudowire in the
Backup PW VC ID
field.
The backup VC ID behaves the same as the VC ID of the primary pseudowire.
Step 5 Continue with the steps contained in the next section, Selecting Devices.
Selecting Devices
The Select Devices section of the EVC Service Request Editor window allows you to set up links to the N-PE. In Prime Provisioning, devices added for circuit emulation provisioning are considered as N-PE role-based devices. After the device is selected, the respective ATM or ATM/IMA interfaces are populated in the Interface drop-down list(s).
The configuration example shown in Figure 5-4 is also used in this section.
Perform the following steps.
Step 1 Click the
Select Device
link to choose the “A” side pseudowire termination point.
The Select PE Device window appears.
Step 2 Choose the appropriate device and click
Save
.
Step 3 In the Interfaces column, choose the desired interface from the drop-down list for the device.
Usage notes:
-
The interfaces that display in the drop-down list for the “A” side termination point will be ATM or ATM/IMA interfaces.
Step 4 After selecting the interface for the “A” side termination device, click the
Edit
link in the Link Attributes column to set the interface attributes.
The ATM UNI Details window appears. This displays a list of interface attributes,
Step 5 Set interface attributes for the “A” side terminal device.
Note The attributes in the window dynamically change depending whether the value of the Transport Mode attribute is set as VP (PVP service) or VC (PVC service). Refer to the appropriate substep below, depending on your configuration.
a. If the “A” side termination is a PVP service, set the following attributes displayed in the window:
–
Transport Mode
—The PVP transport type. In this case, VP appears in the drop-down list.
–
ATM VPI
—Virtual path identifier. Anumber between 0 and 255.
–
Maximum no. of cells to be packed
—The maximum number of cells to be packed into a packet (cell-packing). A number from 2 to 28.
–
Use PseudoWireClass
—Check the check box to associate an existing pseudowire class with the service request. A Select button appears in the GUI, which you can use to choose a pseudowire class. Uncheck the check box to dissociate the pseudowire class from the service request.
–
Use Backup PseudoWireClass
—(This attribute is only available when the Pseudowire Redundancy attribute is checked.) Check the check box to associate an existing pseudowire class as a backup pseudowire class with the service request. A Select button appears in the GUI, which you can use to choose a backup pseudowire class. Uncheck the check box to dissociate the pseudowire class from the service request. The functionality is similar to Pseudowire Class selection in the service request window. The Use Backup PseudowireClass attribute is only applicable for “A” terminals and not for “Z” and “Z - Backup” terminals.
b. If the “A” side termination is a PVC service, set the following attributes displayed in the window:
–
Transport Mode
—The PVC transport type. In this case, VC appears in the drop-down list.
–
Sub-Interface #
—Creates the specified point-to-point sub-interface on the given port on the specified ATM SPA. Range for sub-interface is between 1 and 2147483647.
–
ATM VPI
—Virtual path identifier. A number between 0 and 255.
–
ATM VCI
—Virtual circuit identifier. A number between 1 and 65535.
–
Maximum no. of cells to be packed
—The maximum number of cells to be packed into a packet (cell-packing). A number from 2 to 28.
–
Use PseudoWireClass
—Check the check box to associate an existing pseudowire class with the service request. A Select button appears in the GUI, which you can use to choose a pseudowire class. Uncheck the check box to dissociate the pseudowire class from the service request.
Step 6 After setting the attributes for the interfaces for the “A” terminal device, click
OK
.
The EVC Service Request Editor window reappears.
Step 7 Select the “Z” and, if applicable, the “Z - Backup” terminal devices and configure their interfaces following the same steps you performed for the “A” terminal device.
Usage notes:
-
ATM interfaces are populated in the Interface drop-down list for “Z” and “Z - Backup” terminal devices.
-
When the Pseudowire Redundancy check box is checked in the EVC Service Request Editor window (previously in the workflow), you can select and configure a “Z - Backup” node once the link attributes have been set on for the “A” and “Z” terminal devices.
-
As in case of the “A” terminal device, the interface attributes for the “Z” and “Z - Backup” terminal devices will depend on the type of ATM service (PVP or PVC).
Step 8 After selecting the interface for these termination devices, click the
Edit
link in the Link Attributes column to set the interface attributes.
Step 9 If desired, use the
Swap Terminals
drop-down list to reorder the devices in relation to the terminals.
The choices are based on the configuration:
-
Swap A - Z
-
Swap A - Z
Backup
-
Swap Z- Z
Backup
Choose one of the options to perform the swap operation. The devices reorder in the Select Devices column based on the selection.
Usage notes:
-
The Swap Terminals button only appears when you first create the service request. If you later edit the service request, the button does not appear and you cannot perform the swap operation at that time.
-
The Swap A - Z Backup and Swap Z - Z Backup options are available only when the Pseudowire Redundancy attribute is checked.
-
When devices and terminals are swapped, the interfaces must be reset in the Interfaces column.
Step 10 After the interface attributes are set, click
OK
.
The EVC Service Request Editor window appears.
Step 11 When you have completed setting the attributes in the EVC Service Request Editor window, click the
Save
button at the bottom of the window to save the settings and create the ATM service request.
If any attributes are missing or incorrectly set, Prime Provisioning displays a warning. Make any corrections or updates needed (based on the information provided by Prime Provisioning), and click the
Save
button.
For information on modifying an EVC service request see the section Modifying the ATM Service Request. For additional information about saving an ATM service request, see Saving the ATM Service Request.
Modifying the ATM Service Request
You can modify an ATM service request if you must change or modify the links or other settings of the service request.
To modify a service request, perform the following steps.
Step 1 Choose
Operate > Service Requests > Service Request Manager
.
The Service Request Manager window appears, showing service requests available in Prime Provisioning.
Step 2 Check a check box for a service request.
Step 3 Click
Edit
.
The EVC Service Request Editor window appears.
Step 4 Modify any of the attributes, as desired.
Step 5 To add a template/data file to an attachment circuit, see the section Using Templates and Data Files with an ATM Service Request.
Step 6 When you are finished editing the ATM service request, click
Save
.
For additional information about saving an ATM service request, see Saving the ATM Service Request.
Using Templates and Data Files with an ATM Service Request
Prime Provisioning does not support configuration of all the available CLI commands on a device being managed by the application. In order to configure such commands on the devices, you can use Prime Provisioning Template Manager functionality. Templates can be associated at the policy level on a per-device role basis. Templates can be overridden at service request level, if the policy-level setting permits the operator to do so.
To associate templates and data files in a service request select any link in the Service Request Editor window and click the
Template
button at the bottom of the window.
Note If the template feature has not been enabled in the associated policy then the Template button will not be available for selection.
The SR Template Association window appears. In this window, you can associate templates at a per-device level. The SR Template Association window lists the devices comprising the link, the device roles, and the template(s)/data file(s) associated with the devices. In this case, the template(s)/data file(s) have not yet been set up.
For further instructions on how to associate templates and data files with a service request, see Using Templates with Service Requests.
Saving the ATM Service Request
To save an ATM service request, perform the following steps.
Step 1 When you have finished setting the attributes for the service request, click
Save
to create the service request.
If the service request is successfully created, the Service Request Manager window appears. The newly created ATM service request is added with the state of Requested.
If, however, the service request creation fails for some reason (for example, a value chosen is out of bounds), you are warned with an error message. In such a case, you should correct the error and save the service request again.
Step 2 If you are ready to deploy the ATM service request, see Deploying Service Requests.
For sample configlets for ATM services, see the section Sample Configlets for ATM Services.
Sample Configlets for ATM Services
This section provides sample configlets for RAN backhaul service provisioning in Prime Provisioning. It contains the following subsections:
Overview
The configlets provided in this section show the CLIs generated by Prime Provisioning for particular services and features. Each configlet example provides the following information:
-
Service
-
Feature
-
Devices configuration (network role, hardware platform, relationship of the devices and other relevant information)
-
Sample configlets for each device in the configuration
-
Comments
Note The configlets generated by Prime Provisioning are only the delta between what needs to be provisioned and what currently exists on the device. This means that if a relevant CLI is already on the device, it does not show up in the associated configlet.
Note The CLIs shown in bold are the most relevant commands.
Configuration
-
Service: RAN Backhaul.
-
Feature: This sections contains sample configlets that would be generated for ATM PVP service on a cell site router and two distribution nodes.
-
Device configuration:
– The cell site router is an MWR 2941-DC router with an IOS image.
Contoller(s): E1 0/12, E1 0/13
Interface(s): ATM0/IMA2
– Distribution node A is a 760X series device with IOS image.
Interface(s): ATM 3/1/1
– Distribution node B is a 760X series device with IOS image.
Interface(s): ATM 3/1/1
Configlets
|
pseudowire-class c76a3-1
encapsulation mpls
!
pseudowire-class c76a3-2
encapsulation mpls
!
controller E1 0/12
framing NO-CRC4
clock source internal
ima-group 2 scrambling-payload
!
controller E1 0/13
framing NO-CRC4
clock source internal
ima-group 2 scrambling-payload
!
interface ATM0/IMA2
no ip address
ima version 1.0
ima group-id 2
atm mcpt-timers 1000 5000 10000
atm pvp 9 l2transport
cell-packing 28 mcpt-timer 3
xconnect 10.0.0.1 4090102003 pw-class c76a3-1
backup peer 10.0.0.4 4090403003 pw-class c76a3-2
no atm ilmi-keepalive
|
|
Distribution Node Z Backup
|
pseudowire-class c76a3-1
encapsulation mpls
preferred-path interface Tunnel211
!
interface ATM3/1/1
no ip address
atm mcpt-timers 1000 5000 10000
atm pvp 9 l2transport
cell-packing 28 mcpt-timer 3
xconnect 10.0.0.1 4090102003 pw-class c76a3-1
no atm enable-ilmi-trap
|
pseudowire-class c76a3-2
encapsulation mpls
preferred-path interface Tunnel340
!
interface ATM3/1/1
no ip address
atm mcpt-timers 1000 5000 10000
atm pvp 9 l2transport
cell-packing 28 mcpt-timer 3
xconnect 10.0.0.4 4090403003 pw-class c76a3-2
no atm enable-ilmi-trap
|
Configuration
-
Service: RAN Backhaul.
-
Feature: This sections contains sample configlets that would be generated for ATM VCC service on a cell site router and two distribution nodes.
-
Device configuration:
– The cell site router is an MWR 2941-DC router with an IOS image.
Contoller(s): E1 0/8, E1 0/9
Interface(s): ATM0/IMA0, ATM0/ IMA0
– Distribution node A is a 760X series device with IOS image.
Interface(s): ATM 3/1/0
– Distribution node B is a 760X series device with IOS image.
Interface(s): ATM 3/1/0
Configlets
|
pseudowire-class c76a3-1
encapsulation mpls
!
pseudowire-class c76a3-2
encapsulation mpls
!
controller E1 0/8
framing NO-CRC4
clock source internal
ima-group 0 scrambling-payload
!
controller E1 0/9
framing NO-CRC4
clock source internal
ima-group 0 scrambling-payload
!
interface ATM0/IMA0
ima version 1.0
ima group-id 0
atm mcpt-timers 1000 5000 10000
!
interface ATM0/IMA0.1 point-to-point
snmp trap link-status
pvc 9/34 l2transport
cbr 255
encapsulation aal0
cell-packing 28 mcpt-timer 3
xconnect 10.0.0.1 4090102001 pw-class c76a3-1
backup peer 10.0.0.4 4090403001 pw-class c76a3-2
|
|
Distribution Node Z Backup
|
pseudowire-class c76a3-1
encapsulation mpls
preferred-path interface Tunnel211
!
interface ATM3/1/0
atm mcpt-timers 1000 5000 10000
!
interface ATM3/1/0.9001 point-to-point
description m29a2-3 - ATM0/IMA0
no atm enable-ilmi-trap
pvc 9/34 l2transport
cell-packing 28 mcpt-timer 3
encapsulation aal0
xconnect 10.0.0.1 4090102001 pw-class c76a3-1
|
pseudowire-class c76a3-2
encapsulation mpls
preferred-path interface Tunnel340
!
interface ATM3/1/0
atm mcpt-timers 1000 5000 10000
!
interface ATM3/1/0.9001 point-to-point
description m29a2-3 - ATM0/IMA0
no atm enable-ilmi-trap
pvc 9/34 l2transport
cell-packing 28 mcpt-timer 3
encapsulation aal0
xconnect 10.0.0.4 4090403001 pw-class c76a3-2
|
ATM PVC Service (IOS-XR device)
Configuration
-
Service: RAN Backhaul.
-
Feature: This sections contains sample configlets that would be generated for ATM PVC service on a cell site router with an IOS-XR image.
-
Device configuration:
– The cell site router could be a device belonging to either MWR 2941-DC, ASR901, ASR903, 7600X, or ME36XX platforms with with an IOS-XR image.
Interface(s): ATM0
Configlets
|
interface ATM0/2/1/0
description Link to ONS 12/2
atm mctp-timers 1000 2000 4000
!
interface ATM0/2/1/0.21 l2transport
pvc 2/121
encapsulation aa10
cell-packing 17 1
!
!
xconnect group atm21
p2p atm21
interface ATM0/2/1/0.21
neighbor 192.168.0.7 pw-id 21
pw-class atm
|
ATM PVP Service (IOS-XR device)
Configuration
-
Service: RAN Backhaul.
-
Feature: This sections contains sample configlets that would be generated for ATM PVP service on a cell site router with an IOS-XR image.
-
Device configuration:
– The cell site router could be a device belonging to either MWR 2941-DC, ASR901, ASR903, 7600X, or ME36XX platforms with with an IOS-XR image.
Interface(s): ATM0
Configlets
|
interface ATM0/2/1/0
description ATM MS-PW BU
atm mctp-timers 1000 2000 4000
!
interface ATM0/2/1/0.88 l2transport
pvp 200
cell-packing 200 2
!
!
xconnect group atm88
p2p atm55
interface ATM0/2/1/0.88
neighbor 192.168.0.8 pw-id 55
pw-class atm
!
!
|
ATM/PVP Service (ASR platform, IOS device)
Configuration
-
Service: RAN Backhaul.
-
Feature: This sections contains sample configlets that would be generated for ATM PVP service on a cell site router and one distribution node.
-
Device configuration:
– The cell site router is an ASR 901 device with an IOS image.
Interface(s): ATM0/4/IMA0
– Distribution node A is an ASR 903 device with IOS image.
Interface(s): ATM 6/0/2
Configlets
|
interface ATM0/4/ima0
atm pvp 23 l2transport
cell-packing 12 mcpt-timer 2
xconnect 20.10.10.100 1503 encapsulation mpls
|
|
interface ATM6/0/2
atm pvp 76 l2transport
no epd
cell-packing 27 mcpt-timer 3
xconnect 192.168.0.7 1503 encapsulation mpls
|
ATM/PVP Service (ASR platform, IOS-XR device)
Configuration
-
Service: RAN Backhaul.
-
Feature: This sections contains sample configlets that would be generated for ATM PVP service on a cell site router and one distribution node.
-
Device configuration:
– The cell site router is an ASR 901 device with an IOS image.
Interface(s): ATM0/4/IMA0
– Distribution node A is an ASR 9K device with IOS-XR image.
Interface(s): ATM 0/2/1/0.88
Configlets
|
interface ATM0/4/ima0
atm pvp 23 l2transport
cell-packing 12 mcpt-timer 2
xconnect 20.10.10.100 1503 encapsulation mpls
|
|
interface ATM0/2/1/0.88 l2transport
pvp 123
cell-packing 14 1
l2vpn
xconnect group ISC
p2p test_atm_pvp
interface ATM0/2/1/0.88
neighbor 70.70.70.1 pw-id 2321
|
ATM/PVC Service (ASR platform, IOS device)
Configuration
-
Service: RAN Backhaul.
-
Feature: This sections contains sample configlets that would be generated for ATM PVP service on a cell site router and one distribution node.
-
Device configuration:
– The cell site router is an ASR 901 device with an IOS image.
Interface(s): ATM0/2.45
– Distribution node A is an ASR 903 device with IOS image.
Interface(s): ATM 6/0/3.45
Configlets
|
interface ATM6/0/2.45 point-to-point
pvc 5/66 l2transport
encapsulation aal0
cell-packing 4 mcpt-timer 1
xconnect 20.10.10.100 encapsulation mpls
|
|
interface ATM6/0/3.45 point-to-point
pvc 5/66 l2transport
encapsulation aal0
cell-packing 4 mcpt-timer 1
xconnect 45.2.2.2 756 encapsulation mpls
|
ATM/PVC Service (ASR platform, IOS-XR device)
Configuration
-
Service: RAN Backhaul.
-
Feature: This sections contains sample configlets that would be generated for ATM PVP service on a cell site router and one distribution node.
-
Device configuration:
– The cell site router is an ASR 901 device with an IOS image.
Interface(s): ATM6/0/2.45
– Distribution node A is an ASR 903 device with IOS-XR image.
Interface(s): ATM 0/2/1/0.7644
Configlets
|
interface ATM6/0/2.45 point-to-point
pvc 5/66 l2transport
encapsulation aal0
cell-packing 4 mcpt-timer 1
xconnect 20.10.10.100 encapsulation mpls
|
|
interface ATM0/2/1/0.7644 l2transport
pvc 150/3111
encapsulation aal0
cell-packing 27 1
l2vpn
pw-class PW2026
encapsulation mpls
protocol ldp
xconnect group ISC
p2p ems2941q_442344
interface ATM0/2/1/0.7644
neighbor 70.70.70.1 pw-id 442344
pw-class PW2026
|