NN 20500 225

Use pursuant to applicable agreements
Title page
Alcatel-Lucent 9370
Radio Network Controller | UA08.1
PNNI Hairpin Removal
NN-20500-225
Issue 7.05 | November 2012
Alcatel-Lucent Proprietary
Legal notice
Legal notice
Alcatel, Lucent, Alcatel-Lucent and the Alcatel-Lucent logo are trademarks of Alcatel-Lucent. All other trademarks are the property of their respective
owners.
The information presented is subject to change without notice. Alcatel-Lucent assumes no responsibility for inaccuracies contained herein.
Copyright 2012 Alcatel-Lucent. All rights reserved.
Contains proprietary/trade secret information which is the property of Alcatel-Lucent and must not be made available to, or copied or used by anyone outside
Alcatel-Lucent without its written authorization.
Not to be used or disclosed except in accordance with applicable agreements.
Trademarks
"Nortel Multiservice Switch", "Nortel Multiservice Data Manager", "Nortel Point of Concentration" are Nortel products.
Alcatel-Lucent Proprietary
Contents
About this document

Purpose ............................................................................................................................................................................................. xi
xi
Reason for reissue ........................................................................................................................................................................ xi

xi
New in this release ....................................................................................................................................................................... xi

xi
Intended audience ......................................................................................................................................................................... xi

xi
Supported systems ........................................................................................................................................................................ xi

xi
How to use this document ........................................................................................................................................................ xii

xii
Safety information ...................................................................................................................................................................... xii

xii
Prerequisites .................................................................................................................................................................................. xii

xii
Conventions used ........................................................................................................................................................................ xii

xii
Related information ................................................................................................................................................................... xiii

xiii
Document support ...................................................................................................................................................................... xiv

xiv
Technical support ....................................................................................................................................................................... xiv

xiv
How to order ................................................................................................................................................................................ xiv

xiv
How to comment ........................................................................................................................................................................ xiv

xiv
1 Roadmap to Radio Network Controller documentation
Overview ...................................................................................................................................................................................... 1-1

1-1
Roadmap to Radio Network Controller documentation ............................................................................................. 1-2

1-2
2 Safety statements
Overview ...................................................................................................................................................................................... 2-1

2-1
Structure of safety statements ............................................................................................................................................... 2-2

2-2
3 Hairpin overview
Overview ...................................................................................................................................................................................... 3-1

3-1
....................................................................................................................................................................................................................................
Alcatel-Lucent 9370 RNC Alcatel-Lucent Proprietary iii
NN-20500-225 UA08.1 Use pursuant to applicable agreements
Issue 7.05 November 2012
Contents
....................................................................................................................................................................................................................................
About hairpins
Overview ...................................................................................................................................................................................... 3-2

3-2
Permanent Virtual Connection (PVC) ............................................................................................................................... 3-3

3-3
Soft Permanent Virtual Connections (SPVC) ................................................................................................................. 3-4

3-4
Physical position of hairpins
Situating hairpins ...................................................................................................................................................................... 3-5

3-5
Hairpin connections
Hairpin connections ................................................................................................................................................................. 3-7

3-7
Impacts
Overview ................................................................................................................................................................................... 3-10

3-10
4 Hairpin removal process
Overview ...................................................................................................................................................................................... 4-1

4-1
Steps for hairpin removal ....................................................................................................................................................... 4-2

4-2
5 UA06.0 migration
Overview ...................................................................................................................................................................................... 5-1

5-1
Moving the SPVC endpoints ................................................................................................................................................ 5-2

5-2
NodeB to OAM connectivity ................................................................................................................................................ 5-5

5-5
6 Procedures for moving endpoints
Overview ...................................................................................................................................................................................... 6-1

6-1
Aal2If and the Iub, IuCs and Iur interfaces
Introduction ................................................................................................................................................................................. 6-2

6-2
Iub and open Iub interface ..................................................................................................................................................... 6-3

6-3
IuCs Interface ............................................................................................................................................................................. 6-4

6-4
Iur interface ................................................................................................................................................................................. 6-6

6-6
Iub interface ................................................................................................................................................................................ 6-9

6-9
....................................................................................................................................................................................................................................
iv Alcatel-Lucent Proprietary Alcatel-Lucent 9370 RNC
Use pursuant to applicable agreements NN-20500-225 UA08.1
Contents
....................................................................................................................................................................................................................................
SS7 SaalNNI and the IuCs and Iur interfaces
Introduction .............................................................................................................................................................................. 6-11

6-11
IuCS and IuPS interfaces ..................................................................................................................................................... 6-12

6-12
Iur Interface .............................................................................................................................................................................. 6-13

6-13
7 CAS commands and PNNI hairpin removal
Overview ...................................................................................................................................................................................... 7-1

7-1
ATMPE CAS provisioning and operational commands ............................................................................................. 7-2

7-2
Aal2If and IubIf provisioning commands ........................................................................................................................ 7-5

7-5
Aal2If and IubIf operational commands ........................................................................................................................ 7-13

7-13
SS7 SaalNni CAS provisioning commands .................................................................................................................. 7-16

7-16
SS7 SaalNni CAS operational commands .................................................................................................................... 7-20

7-20
8 Removing the hairpins
Overview ...................................................................................................................................................................................... 8-1

8-1
Tools for hairpin removal ....................................................................................................................................................... 8-2

8-2
Removing the hairpin .............................................................................................................................................................. 8-3

8-3
A Product conformance statements
Overview ..................................................................................................................................................................................... A-1

A-1
Regulatory requirement compliance ................................................................................................................................. A-2

A-2
Compliance for Canada ......................................................................................................................................................... A-3

A-3
Compliance for China ........................................................................................................................................................... A-5

A-5
Compliance for European Union ....................................................................................................................................... A-6

A-6
Compliance for United States ............................................................................................................................................. A-9

A-9
Index
....................................................................................................................................................................................................................................
Alcatel-Lucent 9370 RNC Alcatel-Lucent Proprietary v
Contents
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
vi Alcatel-Lucent Proprietary Alcatel-Lucent 9370 RNC
List of tables
5-1 Interface and concerned RNC application ........................................................................................................ 5-4
6-1 Aal2If usage for different interfaces and their connections ....................................................................... 6-2
6-2 SaalNni usage for interfaces and their connections .................................................................................... 6-11
....................................................................................................................................................................................................................................
Alcatel-Lucent 9370 RNC Alcatel-Lucent Proprietary vii
List of tables
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
viii Alcatel-Lucent Proprietary Alcatel-Lucent 9370 RNC
List of figures
1-1 Roadmap to Radio Network Controller documentation .............................................................................. 1-3
3-1 Typical RNC layout .................................................................................................................................................. 3-6

3-6
3-2 16pOC3 with hairpins .............................................................................................................................................. 3-7
3-3 16pOC3 without hairpins ........................................................................................................................................ 3-9
5-1 SPVC source/destination point example ........................................................................................................... 5-3
8-1 16pOC3 module ......................................................................................................................................................... 8-4

8-4
....................................................................................................................................................................................................................................
Alcatel-Lucent 9370 RNC Alcatel-Lucent Proprietary ix
List of figures
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
x Alcatel-Lucent Proprietary Alcatel-Lucent 9370 RNC
About this document
About this document
Purpose
This publication describes the procedure for removing the hairpins used as endpoints.
Reason for reissue

The reissue reasons are:
Issue number Issue date Reasons for reissue

7.05 November 2012 Standard issue
7.04 October 2012 Standard issue
7.03 March 2012 Preliminary issue
7.02 September 2011 Preliminary issue
7.01 June 2011 Draft issue
New in this release

New features:
None
Other Changes:
Reformat to comply with the current document standards.
Intended audience
This publication is for operations and maintenance personnel, who are required to modify
RNC hardware and reconfigure the RNC platform.
Supported systems
This document applies to Alcatel-Lucent W-CDMA UA08.1 system release.
This document applies to 9370 RNC.
...................................................................................................................................................................................................................................
Alcatel-Lucent 9370 RNC Alcatel-Lucent Proprietary xi
About this document
....................................................................................................................................................................................................................................
How to use this document
Start with the first chapter and work through the manual to the end.
Safety information
For your safety, this document contains safety statements. Safety statements are given at
points where risks of damage to personnel, equipment, and operation may exist. Failure to
follow the directions in a safety statement may result in serious consequences.
Prerequisites
Readers should be familiar with the 3rd Generation Partnership Project (3GPP) Technical
Specification release 99 (R99) and the UMTS specification.
The reconfiguration requirements are based on the network already in place. It is
extremely important that the personnel have the knowledge of their current configuration
in order to anticipate the changes that will occur.
The network should be stable. Any major errors or warnings must be corrected.
Before starting the reconfiguration a snapshot of the current network must be acquired
and each modification should be noted as you progress.
Conventions used
Vocabulary conventions
None
Typographical conventions
The following typographical conventions are used in this document:
Appearance Description
italicized text File and directory names
Emphasized information
graphical user interface text None
variable None
key name None
command-syntax None
input text None
output text None
IP reference, IP number Related document that is referenced in the document
....................................................................................................................................................................................................................................
xii Alcatel-Lucent Proprietary Alcatel-Lucent 9370 RNC
About this document
....................................................................................................................................................................................................................................
Related information
Refer to this document At this location For more information on

Alcatel-Lucent 9370 Radio http://support.alcatel- Radio Network Controller (RNC)
Network Controller - lucent.com 9370 used in a Universal Mobile
Technical Description, Telecommunications System
NN-20500-021 (UMTS).
Alcatel-Lucent 9370 Radio http://support.alcatel- The replacement procedures
Network Controller - lucent.com applicable to the preventive and
Maintenance Guide, corrective maintenance of the
NN-20500-023 Alcatel-Lucent UMTS 9370
Radio Network Controller 1500
(9370 RNC) for X SONET,
SDH-x and PCM-x
configurations.
Nortel Networks Multiservice http://support.alcatel- Hardware description of Nortel
Switch 15000/20000 - lucent.com Networks multiservice switch.
Hardware Description,
NN-10600-120
Nortel Networks Multiservice http://support.alcatel- Hardware, Maintenance and
Switch 15000/20000 - lucent.com Upgrade procedures for Nortel
Hardware Installation, Networks Multiservice Switch.
Maintenance, and Upgrades,
NN-10600-130
Alcatel-Lucent 9952 Wireless http://support.alcatel- Using Alcatel-Lucent 9952
Provisioning System - User lucent.com Wireless provisioning system.
Guide, NN-20500-036
Alcatel-Lucent 9353 http://support.alcatel- RAN Model information and a
W-CDMA Product Family - lucent.com list of the user accessible UMTS
Parameters Reference Guide: Access Network configuration
RAN Model, parameters.
NN-20500-027P1
Alcatel-Lucent W-CDMA http://support.alcatel- List of terms used in
System - Terminology, lucent.com Alcatel-Lucent 9300 W-CDMA
NN-20500-002 documents.
Alcatel-Lucent W-CDMA http://support.alcatel- Safety guidelines and the catalog
System - Safety Guide, lucent.com of hazard statements that appear
401-382-880 in the Alcatel-Lucent UMTS
customer documents.
....................................................................................................................................................................................................................................
Alcatel-Lucent 9370 RNC Alcatel-Lucent Proprietary xiii
About this document
....................................................................................................................................................................................................................................
Document support
For support in using this or any other Alcatel-Lucent document, contact Alcatel-Lucent at
one of the following telephone numbers:
1-888-582-3688 (for the United States)
1-630-224-2485 (for all other countries)
Technical support
For technical support, contact your local Alcatel-Lucent customer support team. See the
Alcatel-Lucent Support web site (http://www.alcatel-lucent.com/support/) for contact
information.
How to order
To order Alcatel-Lucent documents, contact your local sales representative or use Online
Customer Support (OLCS) (http://support.alcatel-lucent.com)
How to comment
To comment on this document, go to the Online Comment Form (http://infodoc.alcatel-
lucent.com/comments/) or e-mail your comments to the Comments Hotline
(comments@alcatel-lucent.com).
....................................................................................................................................................................................................................................
xiv Alcatel-Lucent Proprietary Alcatel-Lucent 9370 RNC
1 1oadmap to Radio
R
Network Controller
documentation
Overview
Purpose
This chapter provides the roadmap for Radio Network Controller documentation.
Contents
Roadmap to Radio Network Controller documentation 1-2
...................................................................................................................................................................................................................................
Alcatel-Lucent 9370 RNC Alcatel-Lucent Proprietary 1-1
Roadmap to Radio Network Controller documentation Roadmap to Radio Network Controller documentation
....................................................................................................................................................................................................................................
Roadmap to Radio Network Controller documentation

Overall roadmap
For the roadmap relating to the full documentation collection, see:
Alcatel-Lucent W-CDMA System - Document Collection Overview, NN-20500-050
For the Access Network Elements Overview, see:
Alcatel-Lucent W-CDMA System - Access Network Elements Overview,
NN-20500-233
....................................................................................................................................................................................................................................
1-2 Alcatel-Lucent Proprietary Alcatel-Lucent 9370 RNC
....................................................................................................................................................................................................................................
Figure 1-1 Roadmap to Radio Network Controller documentation
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
2 Safety statements
2
Overview
Purpose
This chapter provides information on the structure of safety statements which may arise
in the course of your work.
Contents
Structure of safety statements 2-2
...................................................................................................................................................................................................................................
Safety statements Structure of safety statements
....................................................................................................................................................................................................................................
Structure of safety statements

Overview
This topic describes the components of safety statements that appear in this document.
General structure
Safety statements include the following structural elements:
B C D
CAUTION
MP L E
Lifting hazard E F
SA
Lifting this equipment by yourself can result in injury
due to the size and weight of the equipment.
G
Always use three people or a lifting device to transport
and position this equipment. [ABC123]
H
Item Structure element Purpose
1 Safety alert symbol Indicates the potential for personal injury
(optional)
2 Safety symbol Indicates hazard type (optional)
3 Signal word Indicates the severity of the hazard
4 Hazard type Describes the source of the risk of damage or
injury
5 Safety message Consequences if protective measures fail
6 Avoidance message Protective measures to take to avoid the hazard
7 Identifier The reference ID of the safety statement
(optional)
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Signal words
The signal words identify the hazard severity levels as follows:
Signal word Meaning

DANGER Indicates an extremely hazardous situation which, if not avoided, will
result in death or serious injury.
WARNING Indicates a hazardous situation which, if not avoided, could result in
death or serious injury.
CAUTION Indicates a hazardous situation which, if not avoided, could result in
minor or moderate injury.
NOTICE Indicates a hazardous situation not related to personal injury.
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
3 Hairpin overview
3
Overview
Purpose
Hairpins were introduced to act as physical endpoints for some routing applications. With
the Release UA06.0:
The need for more communication ports is created to handle increased traffic capacity.
The software to remove the need for the physical endpoints is improved.
Removing the hairpin to liberate the ports becomes mandatory when:
More than 800 NodeBs are connected to the RNC.
Note: For the NodeBs identified by aal2If =[801 - 1200], the associated
atmConnections are configured on port 808. This can only be done when the PNNI
hairpin resources are re-assigned.
The IuFlex feature is used. This feature is used when several MGW and several
SGSNs that require more atmConnections are present.
The neighboring RNC requires more atmConnections for the Iur interface.
Contents
About hairpins 3-2

Permanent Virtual Connection (PVC) 3-3
Soft Permanent Virtual Connections (SPVC) 3-4
Physical position of hairpins 3-5
Situating hairpins 3-5
Hairpin connections 3-7
Hairpin connections 3-7
Impacts 3-10
Overview 3-10
...................................................................................................................................................................................................................................
Hairpin overview Overview
About hairpins
....................................................................................................................................................................................................................................
About hairpins
Overview
Purpose
This section explains the historical origins of the hairpin usage in the RNC.
Contents
Permanent Virtual Connection (PVC) 3-3

Soft Permanent Virtual Connections (SPVC) 3-4
....................................................................................................................................................................................................................................
Hairpin overview Permanent Virtual Connection (PVC)
About hairpins
....................................................................................................................................................................................................................................
Permanent Virtual Connection (PVC)

Overview
Until Release UA05.0, the traffic for the Iub, Iu-CS, Iu-PS and Iur terminate at the
AtmMpe, Aal2If, IubIf and SS7 SaalNni applications. These applications are engineered
to use ATM PVCs to terminate the traffic. A PVC is an ATM Permanent Virtual
Connection for which the qualifier "permanent" signifies that it is established
administratively (through network management) hop by hop rather than on demand.
....................................................................................................................................................................................................................................
Hairpin overview Soft Permanent Virtual Connections (SPVC)
About hairpins
....................................................................................................................................................................................................................................
Soft Permanent Virtual Connections (SPVC)

Overview
The "SPVCs on Iu/Iur/Iub interface" feature was introduced in Release UA4.2 to use
SPVCs and ATM PNNI routing protocol to simplify provisioning, increase the reliability
and availability of the UTRAN network.
An SPVC between two network interfaces or applications is one where signaling does the
establishment within the network. Assigning unique ATM addresses to the corresponding
network interfaces or applications identifies the endpoints of an SPVC. Route selection is
provided by ATM routing. The routing protocol maintains a topology database and selects
the best path for a given connection and routes the connection setup.
Because the RNC applications cannot terminate or initiate an SPVC connection, the
provisioning of physical hairpins on the 16pOC3 card (PQC based cards with PEC codes
NTHW21 and NTHW31) was required. The SPVC was provisioned to terminate at one
end of the physical hairpin and the applications use a PVC at the other end. The SPVCs
were routed over the links that provide connectivity to the RNC interfaces. The use of
these hairpins reduced the number of ports that are available for the interfaces.
....................................................................................................................................................................................................................................
Hairpin overview Situating hairpins
....................................................................................................................................................................................................................................
Situating hairpins
Overview
This section describes the physical positioning of the hairpins in the RNC. The hairpins
are constructed from optical fibers. Making the connection between two adjacent
connectors forms a "U" shape that can resemble a hairpin or bobby pin. The connectors
are part of the 16pOC3 module that is accessible from the rear of the RNC.
This is related only to the cards with the following codes:
NTHW21
NTHW31
NTHW48
Figure 3-1, Typical RNC layout (p. 3-6) shows the physical position of 16pOC3/STM1
in the RNC.
....................................................................................................................................................................................................................................
Hairpin overview Situating hairpins
....................................................................................................................................................................................................................................
Figure 3-1 Typical RNC layout
....................................................................................................................................................................................................................................
Hairpin overview Hairpin connections
Hairpin connections
....................................................................................................................................................................................................................................
Hairpin connections
Hairpin connections
Overview
This section describes the position of hairpins in the 16pOC3 cards, their purpose, and the
physical result after their removal.
Hairpins are used to connect the ports for the Iub, Iu, and Iur interfaces as shown in
Figure 3-2, 16pOC3 with hairpins (p. 3-7).
Figure 3-2 16pOC3 with hairpins
....................................................................................................................................................................................................................................
Hairpin connections
....................................................................................................................................................................................................................................
In Figure 3-2, 16pOC3 with hairpins (p. 3-7), there are:
Three Iub connections going to the POC (ports 0 to 2) in which only two links are
active at any one time. The third connection provides redundancy in case a failure
occurs on the POC.
Two physical hairpins are required to provide the SPVCs for the three IuB interfaces
(port 3-4 and 5-6).
Two Iu/Iur connections go to the Core Network or other RNCs (ports 14 and 15).
Two physical hairpins are required to provide the SPVCs for the two Iu/Iur interfaces
(port 9-10 and 11-12).
In Release UA05.0, AtmMpe, Aal2If, IubIf and SS7 SaalNni use a PVC from one end of
the physical hairpins. At the other end of the hairpin, a source or destination endpoint of
the SPVC is provisioned.
In Release UA06.0, after Aal2If, IubIf and SS7 SaalNni are modified to use SPVC to
connect to their peer counterpart, eight ports become available to add interfaces as shown
in Figure 3-3, 16pOC3 without hairpins (p. 3-9).
The free ports can be used to add links to or connections to:
Other NodeBs
The Core Network
Other RNCs
....................................................................................................................................................................................................................................
Hairpin connections
....................................................................................................................................................................................................................................
Figure 3-3 16pOC3 without hairpins
....................................................................................................................................................................................................................................
Hairpin overview Overview
Impacts
....................................................................................................................................................................................................................................
Impacts
Overview
Impacts of hairpin removal
This section describes some of the impacts that will occur during and after the process of
removing the hairpins to liberate the ports.
The network administrator must ensure that only PNNI 1.0 or UNI 4.0 interfaces are used
for establishing the SPVCs.
Note: IuBC and CBS are not supported with SPVC.
During the removal process
The re-configuration process should be programmed for a period when traffic is limited.
Traffic can be interrupted throughout the re-configuration period.
Note: To avoid traffic disruption, ensure that the hairpin is no longer used before
removing it physically.
Dependability
This feature is not expected to impact the RNC internal dependability, but may improve
the dependability for connectivity over the Iur, IuCS, IuPS and Iub interfaces by
providing alternate routing when an SPVC failure is detected (if an alternate route is
available).
....................................................................................................................................................................................................................................
4 Hairpin removal process
4
Overview
Purpose
This section describes the procedure to remove the physical hairpins.
Contents
Steps for hairpin removal 4-2
...................................................................................................................................................................................................................................
Hairpin removal process Steps for hairpin removal
....................................................................................................................................................................................................................................
Steps for hairpin removal

Hairpin removal
This section describes the steps to release the 16pOC3 connectors and remove the
hairpins.
Procedure
...................................................................................................................................................................................................
1 Upgrade to the UA06.0 load. For more information on the upgrade procedure, see
Chapter 5, UA06.0 migration.
...................................................................................................................................................................................................
2 Move the endpoints of the SPVCs to AtmMpe, Aal2If, IubIf, and SaalNni. For more
information on moving the endpoints, see Moving the SPVC endpoints (p. 5-2) section.
For re-configuration procedures, see Chapter 6, Procedures for moving endpoints.
...................................................................................................................................................................................................
3 Physically remove the hairpins from the 16pOC3. For more information on the hairpin
removal procedure, see Chapter 8, Removing the hairpins.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
5 UA06.0 migration
5
Overview
Purpose
This section describes hairpin removal process with the UA06.0 upgrade scenario.
The system will default all AtmMpe, Aal2If, IubIf, and SS7 SaalNni to use PVC
connections after upgrading to the UA06.0 RNC load, unless the provisioning for these
components is modified to use SPVCs.
The RNC should be upgraded to Release UA06.0 and then the provisioning must be
changed to replace SPVCs with hairpins to SPVCs without hairpins.
This can be done using WPS or performed manually. Although WPS is recommended,
other configuration managers can perform this task.
For more details about the WPS procedures, see Alcatel-Lucent 9952 Wireless
Provisioning System - User Guide, NN-20500-036.
Contents
Moving the SPVC endpoints 5-2

NodeB to OAM connectivity 5-5
...................................................................................................................................................................................................................................
UA06.0 migration Moving the SPVC endpoints
....................................................................................................................................................................................................................................
Moving the SPVC endpoints

Overview
The next task is to move the endpoint of the current SPVC that is provisioned at one end
of the hairpin to AtmMpe, Aal2If, IubIf, or SaalNni. Depending on which end of the
SPVC (source or destination end) is provisioned on the RNC, the endpoints are moved by
using the provisioning commands.
The WPS Access sets up the SPVC with the RNC as the source endpoint for the Iub and
IuCS SPVC and has a mix of source and destination endpoints for the Iur interface.
Note: For the specific procedures to provision the destination endpoint of the SPVC
on the RNC, see SPVC destination endpoint (p. 6-13) section.
When working with physical hairpins, a combination of ATM PVCs and SPVCs is
required to provide the connectivity.
The PVC portion is provided by the RNC application through a Network Access Point
(NAP) that links to an AtmIf Vcc Network End Point (NEP) residing at one end of the
physical hairpin. At the other end of the hairpin is the endpoint of the SPVC under the
AtmIf Vcc.
This endpoint could be a source or destination endpoint as identified by the presence of a
SourcePvc (src) component under the AtmIf Vcc or a DestinationPvc (dest) component
respectively.
If it is a SourcePvc, the traffic management attributes for the Atm Qos under the AtmIf
Vcc Vcd Tm component exist.
This is shown in Figure 5-1, SPVC source/destination point example (p. 5-3).
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Figure 5-1 SPVC source/destination point example
The AtmIf Vcc that has an src component will have the following two attributes:
calledAddress: Contains the NSAP address of the destination endpoint.
calledVpiVci: Contains the VPI.VCI of the Vcc at the destination.
Moving the destination endpoint of the SPVC to the RNC application impacts the
provisioning on the switches that provide the source endpoint of the SPVC. This is
because the source endpoint will have to change the NSAP address and called VPI.VCI of
the new destination endpoint.
When moving the endpoint of the SPVC, the first step is to look at the current
provisioning of all the SPVCs to:
Determine which endpoint of the SPVC is found on the hairpin.
Find the switch and the provisioning that provides the other end of the SPVC. If the
source endpoint is available, some provisioning changes are required.
Determine which PVC/SPVC combination is for which RNC application.
The next steps depend on which interface and for which RNC application the SPVC is
required. Table 5-1, Interface and concerned RNC application (p. 5-4) contains a list of
interfaces, applications, and the steps required to move the endpoint.
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Additional tasks
Add a new dlep component dlep/0, which contains two hardware links to both ATM cards
before adding any aal2if stp components. The mainLp of dlep is always set to lp/8 and
spareLp is lp/9. All Aal2if STP components contain a link to dlep/0. The dlep/0
component can be added anytime after the rnc upgrade to V6 and can be configured even
if no aal2/x stp is configured. The dlep component is needed to deliver provisioning data
to the proper software entities. One instance of dlep, dlep/0 is required before any RNC
application SPVC is provisioned.
Note: When adding atmmpe spvc or switching from SPVC with Hairpin to SPVC
without Hairpin you must have feature name "atmmpespvc" implemented into the
Logical processor type associated with OC3 cards ('Sw Lpt featureList).
Table 5-1 Interface and concerned RNC application
Interface RNC Application See section

NodeB to OAM AtmMpe NodeB to OAM connectivity (p. 5-5)
connectivity
Iub Aal2If Aal2If and the Iub, IuCs and Iur
interfaces (p. 6-2)
IubIf Iub interface (p. 6-9)
IuCs Aal2If Aal2If and the Iub, IuCs and Iur
interfaces (p. 6-2)
IuPs SPVC is not recommended
IuPc SPVC is not recommended
Iur Aal2If Aal2If and the Iub, IuCs and Iur
interfaces (p. 6-2)
SaalNni SS7 SaalNni CAS provisioning
commands (p. 7-16)
Note: Any change to the provisioning of an existing SPVC will impact the service
provided by that connection. The current SPVC will be released and the new SPVC
that now terminates on the RNC application will be established. It is recommended to
perform this task during a maintenance window.
When working on the Iur interface that is used to link two or more RNCs together,
changes to the provisioning on one RNC will affect the service of the Iur interface
after it is activated. The connectivity can only be re-established when the provisioning
is completed on the other RNCs. No special code is implemented to minimize the
outage. The changing of the Iur interface configured using WPS procedures and
scripts.
....................................................................................................................................................................................................................................
UA06.0 migration NodeB to OAM connectivity
....................................................................................................................................................................................................................................
NodeB to OAM connectivity

Overview
This procedure is used to move the SPVC endpoint to AtmMpe.
Currently, AtmMpe uses a combination of PVC and SPVC for the OAM to NodeB
connectivity but not for the IuPS user plane traffic or the IuPC traffic.
To change from using the combination of PVC and SPVC for AtmMpe to use only an
SPVC with the source endpoint under the AtmMpe Ac component on the RNC, follow
these steps:
To move SPVC endpoint to AtmMpe

Note: This procedure must be duplicated for all of the PVC/SPVC combinations for
all AtmMpe Ac components, but not all need to be done at the same time.
...................................................................................................................................................................................................
1 Add the Stp component under the AtmMpe/n instance.

...................................................................................................................................................................................................
2 Delete the AtmIf Vcc that is providing the NEP that is linked to this AtmMpe/n Ac/m
through the atmConnection attribute.
...................................................................................................................................................................................................
3 Blank out the atmConnection attribute under the AtmMpe/n Ac/m component.
...................................................................................................................................................................................................
4 Add the SourcePvc component under the AtmMpe/n Ac/m component.

...................................................................................................................................................................................................
5 Set the AtmMpe/n Ac/m SourcePvc remoteAddress to the value of the old provisioned
hairpin SPVCs AtmIf Vcc Src calledAddress.
...................................................................................................................................................................................................
6 Set the AtmMpe/n Ac/m SourcePvc calledVpiVci to the value of the old provisioned
hairpin SPVCs AtmIf Vcc Src calledVpiVci.
...................................................................................................................................................................................................
7 Set the AtmMpe/n Ac/m SourcePvc TrafficManagement atmServiceCategory and

peakCellRate attributes based on the value of the old provisioned hairpin SPVCs AtmIf
Vcc Vcd Tm attributes.
...................................................................................................................................................................................................
8 Delete the AtmIf Vcc of the SPVC at the end of the hairpin.
....................................................................................................................................................................................................................................
UA06.0 migration NodeB to OAM connectivity
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
9 Activate the provisioning on the RNC.

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
6 6rocedures for moving
P
endpoints
Overview
Purpose
This section introduces the procedures for moving endpoints.
Contents
Aal2If and the Iub, IuCs and Iur interfaces 6-2

Introduction 6-2
Iub and open Iub interface 6-3
IuCs Interface 6-4
Iur interface 6-6
Iub interface 6-9
SS7 SaalNNI and the IuCs and Iur interfaces 6-11
Introduction 6-11
IuCS and IuPS interfaces 6-12
Iur Interface 6-13
...................................................................................................................................................................................................................................
Procedures for moving endpoints Introduction
....................................................................................................................................................................................................................................
Introduction
This section describes the procedure to change from using PVC and SPVC for Aal2If to
use only an SPVC under the Aal2If Path component or Aal2if Alcap SaalUni.
The Aal2If Path SPVC can be used by multiple interfaces to connect to different pieces of
equipment as illustrated in the following table.
Table 6-1 Aal2If usage for different interfaces and their connections
Interface Connecting to
Iub Poc AtmIf Vcc
Open hub Third party ATM switch Vcc
IuCs ALU Core Network AtmIf Vcc
Third party Core Vcc
Iur Another RNC Aal2If Path
Another RNC Aal2If Path via AtmIf Vcc using the hairpin
A third party ATM switch Vcc
For the Iub and IuCs interface, the source endpoint of the SPVC will be provisioned
under the RNC Aal2If Path component. For the Iur interface, the RNC Aal2If Path
component could be the source endpoint or the destination endpoint.
....................................................................................................................................................................................................................................
Procedures for moving endpoints Iub and open Iub interface
....................................................................................................................................................................................................................................
Iub and open Iub interface

Overview
The following procedure is used to move the SPVC source endpoint for the Iub interface
to the Aal2If Path component that is used to connect to an AtmIf Vcc on the PoC.
Procedure
...................................................................................................................................................................................................
1 Add the Stp component under the Aal2If/n instance.

...................................................................................................................................................................................................
2 Set aal2if/n stp linkToDlep to dlep/0.

...................................................................................................................................................................................................
3 Delete the AtmIf Vcc that is providing the NEP that is linked to this Aal2If/n Path/m Nap
atmConnection attribute.
...................................................................................................................................................................................................
4 Delete the Aal2If/n Path/m NAP subcomponent.

...................................................................................................................................................................................................
5 Add the SourcePvc subcomponent under the Aal2If/n Path/m component.

...................................................................................................................................................................................................
6 Set the Aal2If/n Path/m SourcePvc calledAddress to the value of the old provisioned
...................................................................................................................................................................................................
7 Set the Aal2If/n Path/m SourcePvc calledVpiVci to the value of the old provisioned
...................................................................................................................................................................................................
8 Set the Aal2If/n Path/m SourcePvc TrafficManagement atmServiceCategory,

rx/txTrafficDescType, and rx/txTrafficDescParm attributes based on the value of the old
provisioned hairpin SPVCs AtmIf Vcc Vcd Tm attributes.
...................................................................................................................................................................................................
...................................................................................................................................................................................................
10 Activate the provisioning on this RNC.

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
Procedures for moving endpoints IuCs Interface
....................................................................................................................................................................................................................................
IuCs Interface
Overview
The following procedure is used to move the SPVC source endpoint for the IuCS
interface to the Aal2If Path component that is used to connect to an AtmIf Vcc on the
RNC Core, or to a third party Core Vcc
Procedure
...................................................................................................................................................................................................
1 Add the Stp component under the Aal2If/n instance.

...................................................................................................................................................................................................

...................................................................................................................................................................................................
...................................................................................................................................................................................................
4 Delete the Aal2If/n Path/m NAP subcomponent.

...................................................................................................................................................................................................
5 Add the SourcePvc subcomponent under the Aal2If/n Path/m component.

...................................................................................................................................................................................................
6 Set the Aal2If/n Path/m SourcePvc calledAddress to the value of the old provisioned
...................................................................................................................................................................................................
7 Set the Aal2If/n Path/m SourcePvc calledVpiVci to the value of the old provisioned
...................................................................................................................................................................................................
8 Set the Aal2If/n Path/m SourcePvc TrafficManagement atmServiceCategory,

...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Procedures for moving endpoints IuCs Interface
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
Procedures for moving endpoints Iur interface
....................................................................................................................................................................................................................................
Iur interface
Overview
When connecting to an Aal2If Path instance on another RNC, the provisioning will
depend on if the Aal2If Path on the other RNC supports the use of SPVC or not. It would
be possible that the other RNC software was not yet upgraded to UA06.0.
If the Iur interface connects two RNCs, you must modify the provisioning on the two
RNCs:
the RNC that will contain the destination endpoint of the SPVC
the RNC that will contain the source endpoint of the SPVC
SPVC destination endpoint

Procedure
...................................................................................................................................................................................................
1 For the RNC that will contain the destination endpoint of the SPVC and is also running
with the UA06.0 load with SPVC support, add the Stp component under the Aal2If/x
instance.
...................................................................................................................................................................................................
2 Set aal2if/x stp linkToDlep to dlep/0.

...................................................................................................................................................................................................
3 Delete the AtmIf Vcc that is providing the NEP that is linked to this Aal2If/x Path/y Nap
...................................................................................................................................................................................................
4 Delete the Aal2If/x Path/y Nap subcomponent.

...................................................................................................................................................................................................
5 Add the destination subcomponent under the Aal2If/x Path/y component.

...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
SPVC source endpoint
Procedure
...................................................................................................................................................................................................
1 For the RNC that contains the SPVC source endpoint, add the Stp component under the
Aal2If/n instance.
...................................................................................................................................................................................................

...................................................................................................................................................................................................
...................................................................................................................................................................................................
4 Delete the Aal2If/n Path/m Nap subcomponent.

...................................................................................................................................................................................................
5 Add the SourcePvc component under the Aal2If/n Path/m component.

...................................................................................................................................................................................................
6 For an Iur SPVC connecting to an Aal2If/x Path/y on another RNC with SPVC support:
1. On the other RNC, repeat steps 1 through to 5 to setup the destination endpoint of the
SPVC (as described above).
2. After activation of the provisioning on the other RNC, the new NSAP address will be
found in the Aal2If/x Stp.
3. opLocalAddress operational attribute that is displayed by issuing the CAS command:
d-o aal2If/x stp
4. On this RNC, set the Aal2If/n Path/m SourcePvc calledAddress to the new NSAP
address of the remote Aal2If/x instance by using:

either the value of the opLocalAddress that was printed as part of the output seen
when you issued the "d -o aal2if/x stp" from step b) above
Or the default or provisioned NSAP address
5. On this RNC, set the Aal2If/n Path/m SourcePvc remotePathIdentifier to y, where y is
the remote Aal2If/x Path/y instance.
6. On this RNC, set the Aal2If/n Path/m SourcePvc TrafficManagement
atmServiceCategory, rx/txTrafficDescType, and rx/txTrafficDescParm attributes based
on the value of the old provisioned hairpin SPVCs AtmIf Vcc Vcd Tm attributes.
7. Delete the AtmIf Vcc of the SPVC at the end of the hairpin.
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
8. Activate the provisioning on this RNC.
9. When you have time, cleanup the other RNC provisioning by deleting the Aal2If/x
Path/y Nap subcomponent and the linked Atmif Vcc, and the AtmIf Vcc used to
provide the SPVC through the hairpin.
...................................................................................................................................................................................................
7 For an Iur SPVC connecting to an Aal2If/x Path/y on another RNC without SPVC
support, this means that the SPVC will terminate on an AtmIf Vcc at the end of an hairpin
on the other RNC; or for an Iur SPVC that connects to a third party ATM Vcc:
1. On this RNC, set the Aal2If/n Path/m SourcePvc calledAddress to the value of the old
provisioned hairpin SPVCs AtmIf Vcc Src calledAddress.
2. On this RNC, set the Aal2If/n Path/m SourcePvc calledVpiVci to the value of the old
provisioned hairpin SPVCs AtmIf Vcc Src calledVpiVci.
3. On this RNC, set the Aal2If/n Path/m SourcePvc TrafficManagement
atmServiceCategory, rx/txTrafficDescType and rx/txTrafficDescParm attributes based
E...................................................................................................................................................................................................
N D O F S T E P S
These steps will need to be duplicated for all of the PVC/SPVC combination for Aal2If.
Note:
Not all Aal2If SPVCs need to cut over at the same time.
When using SourcePvc RPI (remotePathIdentifier), you must set VPI and VCI to
0 (vcc/0.0).
When using SourcePvc calledVpiVci, you must set RPI (remotePathIdentifier) to
notUsed.
....................................................................................................................................................................................................................................
Procedures for moving endpoints Iub interface
....................................................................................................................................................................................................................................
Iub interface
Overview
This procedure is used to change the situation which uses a combination of PVC and
SPVC for IubIf to use only an SPVC.
Procedure
...................................................................................................................................................................................................
1 Add the Stp component under the IubIf/n instance.

...................................................................................................................................................................................................
2 Delete the AtmIf Vcc that is providing the NEP that is linked to this IubIf/n
SignallingBearer/m Nap atmConnection attribute.
...................................................................................................................................................................................................
3 Delete the IubIf/n SignallingBearer/m Nap subcomponent.

...................................................................................................................................................................................................
4 Add the SourcePvc component under the IubIf/n SignallingBearer/m component.

...................................................................................................................................................................................................
5 Set the IubIf/n SignallingBearer/m SourcePvc calledAddress to the value of the old
provisioned hairpin SPVCs AtmIf Vcc Src calledAddress.
...................................................................................................................................................................................................
6 Set the IubIf/n SignallingBearer/m SourcePvc calledVpiVci to the value of the old
provisioned hairpin SPVCs AtmIf Vcc Src calledVpiVci.
...................................................................................................................................................................................................
7 Set the IubIf/n SignallingBearer/m SourcePvc TrafficManagement, atmServiceCategory

...................................................................................................................................................................................................
...................................................................................................................................................................................................
9 Activate the provisioning on the RNC.

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
Procedures for moving endpoints Iub interface
....................................................................................................................................................................................................................................
These steps will need to be duplicated for all of the PVC/SPVC combination for IubIf.
Note: Not all IubIf need to cut over to use SPVCs simultaneously.
....................................................................................................................................................................................................................................
Procedures for moving endpoints Overview
....................................................................................................................................................................................................................................
Introduction
SS7 SaalNni usage for interfaces
Here are the provisioning steps to change from using a combination of PVC and SPVC
for SS7 SaalNni to use only an SPVC under the SS7 SaalNni component.
The SS7 SaalNni can be used by different interfaces to connect to different pieces of
equipment as shown in Table 6-2, SaalNni usage for interfaces and their connections
(p. 6-11).
Table 6-2 SaalNni usage for interfaces and their connections
Interface Connecting to
IuPs Alcatel-Lucent Core AtmlfVcc
A third party Core Vcc
IuCs Alcatel-Lucent Core AtmlfVcc
A third party Core Vcc
Iur Another RNC SS7 SaalNni
Another RNC SS7 SaalNni via AtmIf Vcc using the hairpin
A third party ATM switch Vcc
....................................................................................................................................................................................................................................
Procedures for moving endpoints IuCS and IuPS interfaces
....................................................................................................................................................................................................................................
IuCS and IuPS interfaces

Overview
This procedure is used to move the SPVC source endpoint for the IuCS and IuPS
interfaces to the SS7 SaalNni component that is used to connect to an AtmIf Vcc on the
ALU Core, or to a third party Core Vcc:
Procedure
...................................................................................................................................................................................................
1 Add the Stp component under the SS7 SaalNni/n instance.

...................................................................................................................................................................................................
2 Delete the AtmIf Vcc that is providing the NEP that is linked to this SS7 SaalNni/n
through the NAP atmConnection attribute.
...................................................................................................................................................................................................
3 Delete the SS7 SaalNni/n NAP subcomponent.

...................................................................................................................................................................................................
4 Add the SourcePvc component under the SS7 SaalNni/n component.

...................................................................................................................................................................................................
5 Set the SS7 SaalNni/n SourcePvc calledAddress to the value of the old provisioned
...................................................................................................................................................................................................
6 Set the SS7 SaalNni/n SourcePvc calledVpiVci to the value of the old provisioned hairpin
SPVCs AtmIf Vcc Src calledVpiVci.
...................................................................................................................................................................................................
7 Set the SS7 SaalNni/n SourcePvc TrafficManagement atmServiceCategory

...................................................................................................................................................................................................
8 Delete the AtmIf Vcc at the SPVC end of the hairpin.

...................................................................................................................................................................................................
9 Activate the provisioning.

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
Procedures for moving endpoints Iur Interface
....................................................................................................................................................................................................................................
Iur Interface
Overview
When connecting to a SS7 SaalNni instance on another RNC, the provisioning will
depend on if the SS7 SaalNni on the other RNC supports the use of SPVC or not. It could
be possible that the other RNC software was not yet upgraded to UA06.0.
If the Iur interface is connecting two RNCs together, you will need to modify the
provisioning on two RNCs:
The RNC that will contain the destination endpoint of the SPVC.
The RNC that will contain the source endpoint of the SPVC.
SPVC destination endpoint

Procedure
...................................................................................................................................................................................................
1 For the RNC that will contain the destination endpoint of the SPVC and is also running
with the UA06.0 load with SPVC support, add the Stp component under the SS7
SaalNni/x instance.
...................................................................................................................................................................................................
2 Delete the AtmIf Vcc that is providing the NEP that is linked to this SS7 SaalNni/x Nap
...................................................................................................................................................................................................
3 Delete the SS7 SaalNni/x Nap subcomponent.

...................................................................................................................................................................................................
4 Add the destination subcomponent under the SS7 SaalNni/x component.

...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
SPVC source endpoint

Procedure
...................................................................................................................................................................................................
1 For the RNC(a) that contains the SPVC source endpoint used to connect to another SS7
SaalNni on another RNC(b) or to a Vcc on a third party ATM switch, add the Stp
component under the SS7 SaalNni/n instance.
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
2 Delete the AtmIf Vcc that is providing the NEP that is linked to this SS7 SaalNni/n via
the Nap atmConnection attribute.
...................................................................................................................................................................................................
3 Delete the SS7 SaalNni/n Nap subcomponent.

...................................................................................................................................................................................................
4 Add the SourcePvc component under the SS7 SaalNni/n component.

...................................................................................................................................................................................................
5 For an SPVC connecting to SS7 SaalNni/x on another RNC with SPVC support:
1. On the other RNC(b), repeat steps 1 through to 5 to setup the destination endpoint of
the SPV (as described above).
2. After activation of the provisioning on the other RNC(b), the new NSAP address will
be found in the SS7 SaalNni/x Stp.
3. opLocalAddress operational attribute that is displayed by issuing the CAS command:
"d -o aal2If/x stp".
4. On this RNC(b), set the SS7 SaalNni/n SourcePvc calledAddress to the new NSAP
address of the remote SS7 SaalNni/x instance by using:
either the value of the opLocalAddress that was printed as part of the output seen
when you issued the "d -o ss7 saalnni/x stp" from step 2) above.
Or the default or provisioned NSAP address.
5. On this RNC(b), set the SS7 SaalNni/x SourcePvc remoteSaalNniIdentifier to x where
"x" is the remote SS7 SaalNni instance on the other RNC(a).
6. On this RNC(b), set the SS7 SaalNni/x SourcePvc TrafficManagement
atmServiceCategory, rx/txTrafficDescType and rx/txTrafficDescParm attributes based
8. Activate the provisioning on this RNC(b).
9. Cleanup the other RNC(a) provisioning by deleting the SS7 SaalNni/x Nap
subcomponent and the AtmIf Vcc used to provide the SPVC via the hairpin.
...................................................................................................................................................................................................
6 For an SPVC connecting to SS7 SaalNni/x on another RNC without SPVC support, this
means that the SPVC will terminate on an AtmIf Vcc on the other RNC; or if connecting
to a third party ATM switch Vcc:
1. Set the SS7 SaalNni/n SourcePvc calledAddress to the value of the old provisioned
2. Set the SS7 SaalNni/n SourcePvc calledVpiVci to the value of the old provisioned
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
3. Set the SS7 SaalNni/n SourcePvc TrafficManagement atmServiceCategory
rx/txTrafficDescType and rx/txTrafficDescParm attributes based on the value of the
old provisioned hairpin SPVCs AtmIf Vcc Vcd Tm attributes.
4. Delete the AtmIf Vcc at the SPVC end of the hairpin.
E...................................................................................................................................................................................................
N D O F S T E P S
These steps must be duplicated for all of the PVC/SPVC combinations for all SS7
SaalNni.
Note: When using SourcePvc RSI (remoteSaalNniIdentifier), you must set SourcePvc
VPI and VCI to 0 (vcc/0.0).
When using SourcePvc calledVpiVci, you must set SourcePvc RSI
(remoteSaalNniIdentifier) to notUsed.
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
7 7 AS commands and PNNI
C
hairpin removal
Overview
Purpose
This section and the following sections describe Channel Associated Signaling (CAS)
commands that are used to re-configure the network when necessary. The commands are
used to configure the AtmMpe, Aal2If, IubIf and SS7 SaalNni applications to comply
with the network requirements.
In the following sections, examples are used to demonstrate different use cases where the
resulting configuration will:
Use ATM PVCs only
Use of a mix of ATM PVCs and SPVC with the help of a physical hairpin
Use ATM SPVCs only
Note: Some CAS commands can be used to verify if, and what traffic is directed to
what endpoint. Before removing a hairpin, it is extremely important to ensure that no
traffic uses the hairpin as an endpoint.
Contents
ATMPE CAS provisioning and operational commands 7-2

Aal2If and IubIf provisioning commands 7-5
Aal2If and IubIf operational commands 7-13
SS7 SaalNni CAS provisioning commands 7-16
SS7 SaalNni CAS operational commands 7-20
...................................................................................................................................................................................................................................
CAS commands and PNNI hairpin removal ATMPE CAS provisioning and operational commands
....................................................................................................................................................................................................................................
ATMPE CAS provisioning and operational commands

Overview
Removing PNNI hairpins will affect the AtmMpe, Aal2If, IubIf and SS7 SaalNni
applications. These applications need to interface with the Atm Networking to be able to
continue support ATM PVCs but also to be able to setup and manage Atm SPVCs. The
pertinent Channel Associated Signaling (CAS) commands that are used for this feature
are described in the following sections. Some commands are already used on the RNC to
be able to setup SPVCs when using the physical hairpins. These include:
Add artg
Add artg pnni
Add artg pnni cfgnode/n
Set artg pnni cfgnode/n peerGroupId
Add AtmIf/n pnni
There are CAS provisioning and operational commands that are supported for this
feature. The following sections contain a list of current commands used to support ATM
PVCs and a list of new commands to support ATM SPVCsFor each of the AtmMpe,
Aal2If and IubIf, and SS7 SaalNni components.
The following list of commands can be used during hairpin removal:
add atmmpe/n Stp or delete atmmpe/n Stp
add atmmpe/n ac/m SourcePvc or delete atmmpe/n ac/m SourcePvc
add atmmpe/n ac/m DestPvc or delete atmmpe/n ac/m DestPvc
set atmmpe/n ac/m SourcePvc
set atmmpe/n ac/m SourcePvc Tm
set atmmpe/n ac/m SourcePvc calledVpiVci
set atmmpe/n ac/m commentText
To provision for RNC AtmMpe SPVC support, it is necessary to replace existing
provisioning.
Customers may provision AtmMpe to use ATM PVCs. This PVC could be on an AtmIf
Vcc that is at the end of a physical hairpin, or it could be an AtmIf Vcc on the link that
connects to the Poc going to the NodeB. If a physical hairpin is used, AtmMpe uses PVC
at one end of the hairpin, and an AtmIf SPVC is setup at the other end of the hairpin to
connect to PoC.
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
After this feature is implemented the customer will have three different provisioning
options available when provisioning AtmMpe:
Use ATM PVCs only
Use ATM SPVCs only
Customers are able to setup AtmMpe to use an ATM SPVC directly but are limited to use
a VPI value of zero (0). Once this feature is implemented this restriction is removed.
When working with SPVCs, you have the option of provisioning a source SPVC or
destination SPVC on the RNC. The following provisioning command examples illustrate
the three options.
start prov add

atmmpe/1000 ac/49
# other atmmpe/1000 ac/49# provisioning command here
# start of the commands needed if using option 1, use of PVCs
only
add AtmIf/800 Vcc/0.32 Nep
set atmMpe/1000 ac/49 atmConnection AtmIf/800 Vcc/0.32 Nep
# end of the commands needed when using option 1
Start of the commands needed for using option 2, for the use of a mix of PVCs and
SPVCs.
In this example, there is a physical hairpin between ports 3 and 4. AtmIf/803 and
AtmIf/804 are using ports 3 and 4 respectively.

set atmMpe/1000 ac/49 atmConnection AtmIf/803 Vcc/0.1185 Nep
add Atmif/804 Vcc/0.1185 Src
set Atmif/804 Vcc/0.1185 Src
calledAddress45613889902200010F000000000020480D025E00
set AtmIf/804 Vcc/0.1185 Src calledVpiVci 0.32
set AtmIf/804 Vcc/0.1185 Vcd Tm atmServiceCategory constantBitRate
set AtmIf/804 Vcc/0.1185 Vcd Tm rxTrafficDescType sameAsTx
set AtmIf/804 Vcc/0.1185 Vcd Tm rxTrafficDescParm 1 60 2 0 3 0 4 0 5
0
set AtmIf/804 Vcc/0.1185 Vcd Tm txTrafficDescType 3
set AtmIf/804 Vcc/0.1185 Vcd Tm txTrafficDescParm 1 60 2 0 3 0 4 0
5 0
Start of the commands needed for using option 3, for the use of SPVCs only, these actions
add the SPVC termination point under the atmmpe component.
add atmmpe/1000 stp
# If using source SPVC under atmmpe/1000 ac/49
add atmmpe/1000 ac/49 src
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
set atmmpe/1000 ac/49 src calledAddress
45613889902200010F000000000020480D025E00
set atmmpe/1000 ac/49 src calledVpiVci 0.32
set atmmpe/1000 ac/49 src Tm atmServiceCategory constantBitRate
set atmmpe/1000 ac/49 src Tm peakCellRate 60
# If using source SPVC under atmmpe/1000 ac/49
add atmmpe/1000 ac/49 dst

#
check prov
act prov
conf prov
....................................................................................................................................................................................................................................
CAS commands and PNNI hairpin removal Aal2If and IubIf provisioning commands
....................................................................................................................................................................................................................................
Aal2If and IubIf provisioning commands

Overview
To provide the RNC Aal2If and IubIf SPVC support, it is necessary to replace the existing
Aal2If and IubIf provisioning. The following list of commands are required to setup
Aal2If and IubIf to use ATM PVC or an ATM SPVC.
Aal2If commands
The following CAS provisioning commands are supported for Aal2If and its
subcomponents:
add Aal2If/n Stp or delete Aal2If/n Stp
add Aal2If/n Path/n SourcePvc or delete Aal2If/n Path/n SourcePvc
delete Aal2If/n Path/n DestPvc or add Aal2If/n Path/n DestPvc
add Aal2If/n Path/n Nap or delete Aal2If/n Path/n Nap
add Aal2If/n AlcapBearer SaalUni/1 or delete Aal2If/n AlcapBearer SaalUni/1
add Aal2If/n AlcapBearer SaalUni/1 SourcePvc or delete Aal2If/n AlcapBearer
SaalUni/1 SourcePvc
add Aal2If/n AlcapBearer SaalUni/1 DestPvc or delete Aal2If/n AlcapBearer
SaalUni/1 DestPvc
add/delete Aal2If/n AlcapBearer SaalUni/1 Nap or add/delete Aal2If/n AlcapBearer
SaalUni/1 Nap
set Aal2If/n Stp softPvcRetryPeriod
set Aal2if/n Stp linkToDlep
set Aal2If/n Path/n SourcePvc calledAddress
set Aal2If/n Path/n SourcePvc calledVpiVci
set Aal2If/n Path/n SourcePvc remotePathIdentifier
set Aal2If/n Path/n SourcePvc TrafficManagement atmServiceCategory
set Aal2If/n Path/n SourcePvc TrafficManagement rxTrafficDescType
set Aal2If/n Path/n SourcePvc TrafficManagement rxTrafficDescParm
set Aal2If/n Path/n SourcePvc TrafficManagement txTrafficDescType
set Aal2If/n Path/n SourcePvc TrafficManagement txTrafficDescParm
set Aal2If/n AlcapBearer SaalUni/1 SourcePvc calledAddress
set Aal2If/n AlcapBearer SaalUni/1SourcePvc calledVpiVci
set Aal2If/n AlcapBearer SaalUni/1SourcePvc remotePathIdentifier
set Aal2If/n AlcapBearer SaalUni/1 SourcePvc TrafficManagement
atmServiceCategory
set Aal2If/n AlcapBearer SaalUni/1 SourcePvc TrafficManagement rxTrafficDescType
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
rxTrafficDescParm
set Aal2If/n AlcapBearer SaalUni/1 SourcePvc TrafficManagement txTrafficDescType
txTrafficDescParm
After this feature is implemented, the customer will have three different provisioning
options available when provisioning AtmMpe:
Use ATM PVCs only
Use ATM SPVCs only
Customers are able to setup Aal2If and IubIf to use an ATM PVC. This PVC could be an
AtmIf Vcc on a port that connects to the remote end, or it could be an AtmIf Vcc that is at
the end of a physical hairpin. If a physical hairpin is used, an ATM SPVC is setup at the
other end of the hairpin to connect to the remote end. With this feature customers will be
able to setup Aal2If and IubIf using an ATM SPVC directly.
When working with SPVCs, you have the option of provisioning a source SPVC or
destination SPVC. The following provisioning command examples illustrate the three
options.
Aal2If example
start prov
# Add dlep/0 here
#
add Dlep/0
set Dlep/0 MainLp Lp/8
set Dlep/0 SpareLp Lp/9
# Add Aal2If here
Here are the commands needed for using option 1, for the use of PVCs only
add Aal2If/1 Path/1 Nap
set Aal2If/1 Path/1 Nap atm AtmIf/800 Vcc/0.34 Nep
add Aal2If/1 Path/2 Nap
add Aal2If/1 AlcapBearer SaalUni/1 Nap
set Aal2If/1 AlcapBearer SaalUni/1 Nap atm AtmIf/800 Vcc/0.36 Nep
# end of the commands needed if using option 1
Here are the commands needed if using option 2, to enable the use of a mix of PVCs and
SPVCs. In this example, there is a physical hairpin between ports 3 and 4. AtmIf/803 and
AtmIf/804 are using ports 3 and 4 respectively.
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
# Using one source SPVC and one destination SPVC
set Atmif/804 Vcc/0.34 Src calledAddress
47000012345601234560A110100020480D00C900
set AtmIf/804 Vcc/0.34 Vcd Tm atmServiceCategory rtVariableBitRate
0
set AtmIf/804 Vcc/0.34 Vcd Tm txTrafficDescParm 1 4490 2 898 3 13 4 0 5
0
add Atmif/804 Vcc/0.35 Dst
47000012345601234560A110100020480D00C900
0
set AtmIf/804 Vcc/0.36 Vcd Tm txTrafficDescParm 1 4490 2 898 3 13 4 0 5
0
add Aal2If/1 Path/1 Nap add Aal2If/1 Path/2 Nap
add Aal2If/1 AlcapBearer SaalUni/1 Nap
set Aal2If/1 AlcapBearer SaalUni/1 atm AtmIf/803 Vcc/0.36 Nep
Here are the commands needed if using option 3, use of SPVCs only. Add the SPVC
termination point under the aal2If component.
add Aal2If/1 stp
set Aal2If/1 stp linkToDlep Dlep/0
# Using one source SPVC and one destination SPVC
# The source SPVC is trying to reach an AtmIf Vcc component
add Aal2If/1 Path/1 src
set Aal2If/1 Path/1 src calledAddress
47000012345601234560A110100020480D00C900
set Aal2If/1 Path/1 src calledVpiVci 0.34
set Aal2If/1 Path/1 src Tm atmServiceCategory rtVariableBitRate
set Aal2If/1 Path/1 src Tm rxTrafficDescType sameAsTx
set Aal2If/1 Path/1 src Tm rxTrafficDescParm 1 4490 2 898 3 13 4 0 5 0
set Aal2If/1 Path/1 src Tm txTrafficDescType 6
set Aal2If/1 Path/1 src Tm txTrafficDescParm 1 60 2 30 3 4 4 250 5 0
add Aal2If/1 Path/2 dst
add Aal2If/1 AlcapBearer SaalUni/1 src
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
set Aal2If/1 AlcapBearer SaalUni/1 src calledAddress
47000012345601234560A110100020480D00C900
set Aal2If/1 AlcapBearer SaalUni/1 src calledVpiVci 0.35
set Aal2If/1 AlcapBearer SaalUni/1 src Tm atmServiceCategory
rtVariableBitRate
set Aal2If/1 AlcapBearer SaalUni/1 src Tm rxTrafficDescType sameAsTx
set Aal2If/1 AlcapBearer SaalUni/1 src Tm rxTrafficDescParm 1 4490 2
898 3 13 4 0 5 0
set Aal2If/1 AlcapBearer SaalUni/1 src Tm txTrafficDescType 6
set Aal2If/1 AlcapBearer SaalUni/1 src Tm txTrafficDescParm 1 60 2 30 3
4 4 250 5 0
check prov
act prov
start prov
IubIf commands
The following CAS provisioning commands are supported for IubIf and its
subcomponents:
add IubIf/n Stp or delete IubIf/n Stp
add IubIf/n SignallingBearer/n SaalUni SourcePvc or delete IubIf/n
SignallingBearer/n SaalUni SourcePvc
add IubIf/n SignallingBearer/n SaalUni DestPvc or delete IubIf/n SignallingBearer/n
SaalUni DestPvc
add IubIf/n SignallingBearer/n SaalUni Nap or delete IubIf/n SignallingBearer/n
SaalUni Nap
set IubIf/n Stp softPvcRetryPeriod
set IubIf/n SignallingBearer/n SaalUni SourcePvc calledAddress
set IubIf/n SignallingBearer/n SaalUni SourcePvc calledVpiVci
set IubIf/n SignallingBearer/n SaalUni SourcePvc TrafficManagement
atmServiceCategory
rxTrafficDescType
rxTrafficDescParm
txTrafficDescType
txTrafficDescParm
IubIf example
# Add IubIf, SignallingBearer, and SaalUni here
# Here are the commands needed if using option 1, use of PVCs only
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
add IubIf/1 SignallingBearer/1 SaalUni Nap
set IubIf/1 SignallingBearer/1 SaalUni Nap atm AtmIf/800 Vcc/0.50 Nep
Here are the commands needed for using option 2, use of a mix of PVCs and SPVCs. In
this example, there is a physical hairpin between ports 3 and 4. AtmIf/803 and AtmIf/804
are using ports 3 and 4 respectively.
# Using one source SPVC and one destination SPVC add Atmif/804 Vcc/
0.50 Src
47000012345601234560A110100020480D00C900
set AtmIf/804 Vcc/0.50 Vcd Tm rxTrafficDescParm 1 60 2 30 3 4 4 250 5 0
set AtmIf/804 Vcc/0.50 Vcd Tm txTrafficDescParm 1 60 2 30 3 4 4 250 5 0
Add Atmif/804 Vcc/0.51 Dst
Here are the commands needed for using option 3, use of SPVCs only. To add the SPVC
termination point under the IubIf component.
add IubIf/1 stp
# Using one source SPVC and one destination SPVC. The source SPVC
is trying to reach an AtmIf Vcc component.
add IubIf/1 SignallingBearer/1 SaalUni src
set IubIf/1 SignallingBearer/1 SaalUni src calledAddress
47000012345601234560A110100020480D00C900
set IubIf/1 SignallingBearer/1 SaalUni src calledVpiVci 0.50
set IubIf/1 SignallingBearer/1 SaalUni src Tm atmServiceCategory
rtVariableBitRate
set IubIf/1 SignallingBearer/1 SaalUni src Tm rxTrafficDescType sameAsTx
set IubIf/1 SignallingBearer/1 SaalUni src Tm rxTrafficDescParm 1 60 2
30 3 4 4 250 5 0
set IubIf/1 SignallingBearer/1 SaalUni src Tm txTrafficDescType 6
set IubIf/1 SignallingBearer/1 SaalUni src Tm txTrafficDescParm 1 60 2
30 3 4 4 250 5 0
add IubIf/1 SignallingBearer/2 SaalUni dst
check prov
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
act prov
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
To verify the state after re-configuration
The following command can be useful to verify the states after switching SPVC with
hairpin to SPVC without Hairpin:
Command: d atmif/* vcc/* ep
Example
d atmif/* vcc/* ep
AtmIf/* Vcc/* Ep
+=====+==========+------------------+------
|AtmIf| Vcc | applicationName |Response
+=====+==========+------------------+------
| 800|0.5 |AtmIf/800 Pnni Sig |
| 800|0.18 |AtmIf/800 Pnni Rcc |
| 800|0.14436 |Aal2If/350 Path/4426|
| | | AtmCon |
| 800|0.14485 |Ss7 SaalNni/34 |
| | | AtmCon |
| 800|0.14517 |Aal2If/80 Path/1265 |
| | | AtmCon |
| 800|0.14518 |AtmMpe/1000 Ac/80 |
| | | AtmCon |
| 803|0.5 |AtmIf/803 Pnni Sig |
| 803|0.18 |AtmIf/803 Pnni Rcc |
| 803|0.13998 |Ss7 SaalNni/33 |
| | | AtmCon |
| 803|0.14024 |Aal2If/80 Path/1279 |
| | | AtmCon |
| 803|0.14025 |Aal2If/80 Path/1271 |
| | | AtmCon |
| 803|0.14026 |Aal2If/80 Path/1272 |
| | | AtmCon |
| 803|0.14027 |Aal2If/80 Path/1269 |
| | | AtmCon |
| 803|0.14028 |Aal2If/80 Path/1270
| | | AtmCon |
| 803|0.14029 |Aal2If/80 Path/1278 |
| | | AtmCon |
| 803|0.14030 |Aal2If/80 Alcap |
| | | AtmCon |
| 803|0.14031 |Aal2If/80 Path/1277 |
| | | AtmCon |
| 803|0.14032 |Aal2If/80 Path/1280 |
| | | AtmCon |
| 803|0.14033 |Iub/80 Sig/0 SaalUni
| | | AtmCon |
| 803|0.14034 |Iub/80 Sig/2 SaalUni|
| | | AtmCon |
| 803|0.14035 |Iub/80 Sig/1 SaalUni|
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
| | | AtmCon |
| 803|0.16367 |Aal2If/350 Path/4473|
| | | AtmCon |
| 803|0.16368 |Aal2If/350 Path/4433|
| | | AtmCon |
ok 2008-10-27 19:08:20.88
....................................................................................................................................................................................................................................
CAS commands and PNNI hairpin removal Aal2If and IubIf operational commands
....................................................................................................................................................................................................................................
Aal2If and IubIf operational commands

Overview
This section describes some CAS commands and provides information on how to use
them for specific tasks concerned with Aal2If and IubIf.
Clear - for tearing down connections

The CAS clear command can be used on either the SrcPvc or the DstPvc component
under Aal2If Path or Aal2if AlcapBearer SaalUni or under IubIf SignallingBearer
SaalUni. This command tears down any active SPVC connection underneath the
component to which it is applied. In addition, the clear command resets the retryCount
attribute (calling endpoints only).
Here are some examples:
clear Aal2If/<n>Path/<n><n>SrcPvc
clear Aal2If/AlcapBearer SaalUni/1 SrcPvc
clear IubIf/<n>SignallingBearer/<n>SaalUni SrcPvc
or
clear Aal2If/<n>Path/<n>DstPvc
clear Aal2If/<n>AlcapBearer SaalUni/1 DstPvc
clear IubIf/<n>SignallingBearer/<n>SaalUni DstPvc
Display - for connection monitoring

SPVC connection establishment can be verified by observing the state attribute
underneath the SrcPvc and DstPvc components on either side of an SPVC. If an SPVC
connection has been established, both sides of the SPVC should be in the active state.
Here are some examples:
display Aal2If/<n>Path/<n><n>SrcPvc state
display Aal2If/AlcapBearer SaalUni/1 SrcPvc state
display IubIf/<n>SignallingBearer/<n>SaalUni SrcPvc state
or
display Aal2If/<n>Path/<n>DstPvc state
display Aal2If/<n>AlcapBearer SaalUni/1 DstPvc state
display IubIf/<n>SignallingBearer/<n>SaalUni DstPvc state
Display - for AtmIf Vcc flow

This procedure describes the flow of data through an SPVC. The traffic flow can be
observed by monitoring the Aal2If Path, the IubIf SignallingBearer SaalUni, and the
AtmIf statistics.
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
To verify the flow across the UTRAN network:
...................................................................................................................................................................................................
1 Find out the SPVC on which the Atm Vcc is established:

display Aal2If/<n> Path/<n> atmCon nextHop
display Aal2If/<n> AlcapBearer SaalUni/1 atmCon nextHop
display IubIf/<n> SignallingBearer/<n> SaalUni atmCon nextHop
Observe the AtmIf/n vcc/vpi.vci
...................................................................................................................................................................................................
2 Verify that ATM cells are sent out to the calling endpoint of the SPVC:
display AtmIf/<n> vcc/ <vpi.vci> from 1. above
Observe the txCell count attributes.
...................................................................................................................................................................................................
3 Verify that data is received by the SPVC:

display AtmIf/<n> Vcc/<vpi.vci> from 1. above
Observe the rxCell count.
E...................................................................................................................................................................................................
N D O F S T E P S
Display - spvc failure (troubleshooting)

The SPVC establishment has failed if either endpoint (SrcPvc or DstPvc) is in the inactive
state.
You can use the display command for troubleshooting in case of SPVC failure:
display Aal2If/<n> Path/<n> SrcPvc state
display Aal2If/<n> AlcapBearer SaalUni/1 SrcPvc state
display IubIf/<n> SignallingBearer/<n> SaalUni SrcPvc state
or
display Aal2If/<n> Path/<n> DstPvc state
display Aal2If/<n> AlcapBearer SaalUni/1 DstPvc state
display IubIf/<n> SignallingBearer/<n> SaalUni DstPvc state
You can view the number of retries made by the calling endpoint by using the following
commands:
display Aal2If/<n> Path/<n> SrcPvc retry
display Aal2If/<n> AlcapBearer SaalUni/1 SrcPvc retry
display IubIf/<n> SignallingBearer/<n> SaalUni SrcPvc retry
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
If the SPVC was previously established, identify the reason for the last connection tear
down by using the following operator command:
display Aal2If/<n> Path/<n> SrcPvc lastClearCause
display Aal2If/<n> AlcapBearer SaalUni/1 SrcPvc lastClearCause
display IubIf/<n> SignallingBearer/<n> SaalUni SrcPvc lastClearCause
or
display Aal2If/<n> Path/<n> DstPvc lastClearCause
display Aal2If/<n> AlcapBearer SaalUni/1 DstPvc lastClearCause
display IubIf/<n> SignallingBearer/<n> SaalUni DstPvc lastClearCause
If the SPVC was not previously established, there is likely a misconfiguration at one or
both endpoints of the SPVC.
Clear - for path optimization

Aal2If and IubIf SPVCs provide break-before-make path recovery. Therefore, a link or
node in the path of the active SPVC must fail before an SPVC calling endpoint will try to
re-establish the connection using an alternate path.
In other words, if a "better" path (that is a path with less cost) to the remote end becomes
available, the SPVC will not migrate to the better path without provocation. This feature
does not support the ATM SPVC reroute. If the network on which the SPVC is traversing
finds a better route, a reroute message could be sent to both ends of the SPVC to use a
new route.
To "force" the SPVC to migrate to an alternate path, the following operational procedure
can be used:
clear Aal2If/<n> Path/<n> SrcPvc
clear Aal2If/<n> AlcapBearer SaalUni/1 SrcPvc
clear IubIf/<n> SignallingBearer/<n> SaalUni SrcPvc
or
clear Aal2If/<n> Path/ <n> DstPvc
clear Aal2If/<n> AlcapBearer SaalUni/1 DstPvc
clear IubIf/<n> SignallingBearer/<n> SaalUni DstPvc
This will cause a loss of the connection and the SPVCs will enter the inactive state, and
begin a new attempt to re-establish the connection after the softPvcRetryTimer has
expired.
The new path depends on the current topology and GCAC information stored for the
PNNI 1.0 network. This command can be used when there are two fibers that provide
connectivity to the destination and you need to replace the fiber on which the SPVCs are
established. In this situation, you can use the clear command and lock the port on which
you need to replace the fiber. This will force the SPVCs to establish on the other link.
Note: The CAS clear command can be executed on either the calling or called
endpoint of an SPVC.
....................................................................................................................................................................................................................................
CAS commands and PNNI hairpin removal SS7 SaalNni CAS provisioning commands
....................................................................................................................................................................................................................................
SS7 SaalNni CAS provisioning commands

Overview
The following CAS commands can be used for hairpin removal. They include:
add ss7 saalnni/n Stp or delete ss7 saalnni/n Stp
add ss7 saalnni/n SourcePvc or delete ss7 saalnni/n SourcePvc
add ss7 saalnni/n DestPvc or delete ss7 saalnni/n DestPvc
add ss7 saalnni/n Nap or delete ss7 saalnni/n Nap
set ss7 saalnni/n Stp softPvcRetryPeriod
set ss7 saalnni/n SourcePvc calledAddress
set ss7 saalnni/n SourcePvc calledVpiVci
set ss7 saalnni/n SourcePvc remoteSaalNniIdentifier
set ss7 saalnni/n SourcePvc TrafficManagement atmServiceCategory
set ss7 saalnni/n SourcePvc TrafficManagement rxTrafficDescType
set ss7 saalnni/n SourcePvc TrafficManagement rxTrafficDescParm
set ss7 saalnni/n SourcePvc TrafficManagement txTrafficDescType
set ss7 saalnni/n SourcePvc TrafficManagement txTrafficDescParm
To provision the RNC SS7 SaalNni SPVC support, it is necessary to replace the existing
SS7 SaalNni provisioning. To illustrate this, here is a list of commands required to setup
SaalNni to use ATM PVC or to use ATM SPVC. The list in question will concentrate on
the SS7 SaalNni provisioning only and will not contain all the commands needed to
provision all of SS7 on an RNC.
When this feature is implemented the customer will have three different provisioning
options available when provisioning SS7 SaalNni:
1. Use ATM PVCs only
2. Use of a mix of ATM PVCs and SPVC with the help of a physical hairpin
3. Use ATM SPVCs only
Currently, the SS7 SaalNni setup is required to use ATM PVCs. However, this PVC could
be on an AtmIf Vcc that is at the end of a physical hairpin, or it could be an AtmIf Vcc on
link that connects to the Core Network or another RNC.
If a physical hairpin is used, SaalNni uses a PVC at one end of the hairpin, and an AtmIf
SPVC is set up at the other end of the hairpin to connect to the Core Network or another
RNC. With this feature, the users will be able to set up SS7 SaalNni to use an ATM SPVC
directly. When working with SPVCs, you have the option of provisioning a source SPVC
or destination SPVC. The following provisioning command examples illustrate the three
provisioning options:
start prov
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
# other SS7 provisioning command here
add ss7 saalnni/1
add ss7 saalnni/2
add ss7 saalnni/17
add ss7 saalnni/18
add ss7 saalnni/33
add ss7 saalnni/34
When using option 1, use PVCs only:
add ss7 saalnni/1 nap
set ss7 saalnni/1 nap atm AtmIf/815 Vcc/1.32 Nep
The commands needed when using option 2, to use of a mix of PVCs and SPVCs are as
follows. In this example, there is a physical hairpin between ports 11 and 12. AtmIf/811
and AtmIf/812 are using ports 11 and 12 respectively.
# Using three source SPVCs and three desination SPVCs
47000012345601234560A110100020480D00C900
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
47000012345601234560A220200020480D123400
47000012345601234560A110100020480D022200
The following commands are used when using option 3, to use SPVCs only. To add the
SPVC termination point under the SaalNni component:
add ss7 saalnni/1 stp
# Using three source SPVCs and three desination SPVCs
# All three source SPVCs are trying to reach an AtmIf Vcc component
add ss7 saalnni/1 src
set ss7 saalnni/1 src calledAddress
47000012345601234560A110100020480D00C900
set ss7 saalnni/1 src calledVpiVci 1.32
set ss7 saalnni/1 src Tm atmServiceCategory rtVariableBitRate
set ss7 saalnni/1 src Tm rxTrafficDescType sameAsTx
set ss7 saalnni/1 src Tm rxTrafficDescParm 1 60 2 30 3 4 4 250 5 0
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
set ss7 saalnni/1 src Tm txTrafficDescType 6
set ss7 saalnni/1 src Tm txTrafficDescParm 1 60 2 30 3 4 4 250 5 0
add ss7 saalnni/2 dst
47000012345601234560A220200020480D123400
47000012345601234560A110100020480D022200
# end of the commands for using option 3
The following is an example of commands for a SaalNni SPVC terminating on a
destination SPVC under SS7 SaalNni/34 that resides on another RNC.
47000012345601234560A110100020480DC0C902
set ss7 saalnni/34 src remoteSaalNniIdentifier 34
check prov
act prov
conf prov
....................................................................................................................................................................................................................................
CAS commands and PNNI hairpin removal SS7 SaalNni CAS operational commands
....................................................................................................................................................................................................................................
SS7 SaalNni CAS operational commands

Overview
This section contains sub-sections that describe how to use CAS commands for specific
SS7 SaalNni tasks.
Clear - for tearing down endpoint connections

The CAS clear command can be used on either the SaalNni SrcPvc component or the
SaalNni DstPvc component. This command tears down any active SPVC connection
underneath the component to which it is applied. In addition, the clear command resets
the retryCount attribute (calling endpoints only).
clear SS7 SaalNni/<n> SrcPvc
or
clear SS7 SaalNni/<n> DstPvc
Display - for connection monitoring and verification

SPVC connection establishment can be verified by observing the state attribute
underneath the SrcPvc and DstPvc components on either side of an SPVC. If an SPVC
connection has been established, both sides of the SPVC should be in the active state.
display SS7 SaalNni/<n> SrcPvc
or
display SS7 SaalNni/<n> DstPvc
Display - for AtmIf Vcc data flow

The display command can be used to observe the flow of data through an SaalNni SPVC.
The traffic flow can be observed by monitoring the SaalNni and the AtmIf statistics. To
verify the flow across a UTRAN network:
...................................................................................................................................................................................................
1 To find out on which AtmIf VCC the SPVC has been established:
display SS7 SaalNni/<n> atmCon nextHop
Observe the AtmIf/n vcc/vpi.vci.
...................................................................................................................................................................................................
2 Verify that ATM cells are sent out the calling endpoint of the SaalNni SPVC:
display AtmIf/<n> vcc/<vpi.vci> from 1. above
Observe the txCell count attributes.
...................................................................................................................................................................................................
3 Verify that data is received by the SaalNni SPVC:

....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
display AtmIf/<n> Vcc/ <vpi.vci> from 1. above
Observe the rxCell count.
E...................................................................................................................................................................................................
N D O F S T E P S
Display - for spvc failure (troubleshooting)

The SPVC establishment has failed if either endpoint (SrcPvc or DstPvc) is in the inactive
state:
display SS7 SaalNni/<n> SrcPvc state
or
display SS7 SaalNni/<n> DstPvc state
The number of retries that have been made by the calling endpoint can be viewed:
display SaalNni/<n> SrcPvc retry
If the SPVC was previously established, you can identify the reason for the last
connection tear down using the command:
display SaalNni/<n> SrcPvc lastClearCause
or
display SaalNni/<n> DstPvc lastClearCause
If the SPVC was not established, there is probably a misconfiguration at one or both
endpoints of the SaalNni SPVC.
Clear - for path optimization

SaalNni SPVCs provide break-before-make path recovery. Therefore, a link or node in
the path of the active SPVC must fail before an SPVC calling endpoint will try to re-
establish the connection using an alternate path.
This means that if a "better" path (i.e. a path with less cost) to the end should become
available, the SPVC will not migrate to the better path without provocation.
In order to "force" the SPVC to migrate to an alternate path, the following operational
procedure can be used:
clear SS7 SaalNni/<n> SrcPvc
or
clear SS7 SaalNni/<n> DstPvc
This will cause a loss of the connection and the SaalNni SPVC will enter the inactive
state, a new attempt to re-establish the connection starts when the softPvcRetryTimer has
expired.
The new path depends on the current topology and GCAC information stored for the
PNNI 1.0 network.
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
This command could be used in a situation where you have two fibers that provides
connectivity to the destination and you need to replace the fiber on which the SPVCs
have been established. In this situation you can use the clear command and lock the port
on which you need to replace the fiber. This will force the SPVCs to establish on the other
link.
Note: The CAS clear command can be executed on either the calling or called
endpoint of an SaalNni SPVC.
....................................................................................................................................................................................................................................
8 Removing the hairpins
8
Overview
Purpose
The final step to liberate the ports is the physical removal of the fiber between the two
ports used by the physical hairpin.
This can be done at any time that is convenient to the customer or the technician (after the
migration of services over hairpin is completed) and does not need to be done
immediately.
The ports that are liberated can then be used to add extra links for the Iub, Iu and Iur
interfaces.
Contents
Tools for hairpin removal 8-2

Removing the hairpin 8-3
...................................................................................................................................................................................................................................
Removing the hairpins Tools for hairpin removal
....................................................................................................................................................................................................................................
Tools for hairpin removal

Overview
The list of tools should include:
Anti static bracelet and connection
A sufficient number of optical connection protectors for the 16pOC3 module.
Note: The following precautions must be taken while using these tools for hairpin
removal:
Interventions on electrical apparatus
Anti-static protection
....................................................................................................................................................................................................................................
Removing the hairpins Removing the hairpin
....................................................................................................................................................................................................................................
Removing the hairpin

Notice
NOTICE
ESD hazard
Contact with equipment without the anti-static protection can cause injury.
All usual precautions concerning electrical telephony equipment and anti-static
protection must be taken into account for this procedure.
The following procedure is used to liberate the ports by removing the physical hairpins.
Note: The physical removal of the hairpin must only be attempted after all the
reconfiguration is completed.
Figure 8-1, 16pOC3 module (p. 8-4) shows the module with the cover open to access
the optical connections. In this figure no optical cables, hairpins or protectors are installed
on or connected to the Tx/Rx fiber ports.
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Figure 8-1 16pOC3 module
Procedure
Use the following procedure to remove the hairpins.
...................................................................................................................................................................................................
1 Locate the RNC geographically.

...................................................................................................................................................................................................
2 Locate the 16pOC3 module in the RNC.

...................................................................................................................................................................................................
3 Lift the cable connection cover to expose the connections to the 16pOC3 module.
...................................................................................................................................................................................................
4 Locate the hairpins that you want to remove.
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
5 Unplug the connections of the hairpin.

...................................................................................................................................................................................................
6 Insert the optical connection protectors.

...................................................................................................................................................................................................
7 Repeat the operation on the second 16pOC3 module.

...................................................................................................................................................................................................
8 Check that the action has not created any additional port alarms and that the RNC is
functioning correctly.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Appendix A: Product
conformance statements
Overview
Purpose
This appendix presents the product conformance statements that apply to the
Alcatel-Lucent 9370 Radio Network Controller.
In regions such as North America and the European Union, the statements that are
required are determined primarily by national or multi-national regulations. However, in
some regions, contract terms determine the required statements.
The presence of the statement indicates that the product does comply with that statement
wherever it is required to do so.
Contents
Regulatory requirement compliance A-2

Compliance for Canada A-3
Compliance for China A-5
Compliance for European Union A-6
Compliance for United States A-9
...................................................................................................................................................................................................................................
Alcatel-Lucent 9370 RNC Alcatel-Lucent Proprietary A-1
Product conformance statements Regulatory requirement compliance
....................................................................................................................................................................................................................................
Regulatory requirement compliance

Overview
The equipment described in this document generates, uses, and can radiate radio
frequency energy. If the equipment is not installed and used in accordance with the
instruction manual, the equipment can cause harmful interference to radio
communications.
There is no guarantee that interference will not occur in a particular installation. To
determine whether this equipment is causing interference, the operator can turn the
equipment off and on. The operator is encouraged to correct any interference problems.
The Electromagnetic Compatibility (EMC) requirements have been selected to ensure an
adequate level of compatibility for apparatus in residential, commercial, and light
industrial environments.
Compatibility levels, however, do not cover extreme cases that can occur anywhere, but
that have a low probability of occurrence. In particular, they may not cover cases where a
source of interference that is producing repeated transient or continuous phenomena is
permanently present. This could include a radar or broadcast site in the vicinity. In such
cases, the operator can limit the source of interference and/or apply special protection to
the impacted equipment.
For the integrity of the product, the operator must wear the antistatic wrist strap at all
times while working with Alcatel-Lucent systems.
....................................................................................................................................................................................................................................
A-2 Alcatel-Lucent Proprietary Alcatel-Lucent 9370 RNC
Product conformance statements Compliance for Canada
....................................................................................................................................................................................................................................
Compliance for Canada

Overview
The following statements are the product conformance statements that apply to the
Alcatel-Lucent 9370 Radio Network Controller when deployed in Canada.
Industry Canada statements

ICES-003: Interference-Causing Equipment Standard Digital Apparatus
This Class A digital apparatus complies with Canadian ICES-003. Cet appareil numrique
de la classe A est conforme la norme NMB-003 du Canada.
9370 RNC is tested for emissions. The test results revealed that it does not exceed the
limits for Class B emissions IC CS-03, Specification for Terminal Equipment, Terminal
Systems, Network Protection Devices, Connection Arrangements, and Hearing Aids
Compatibility.
This product meets the applicable Industry Canada technical specifications.
Product safety conformance statements

The Alcatel-Lucent 9370 Radio Network Controller is Safety Certified CSA c22.2 No.
60950-1 by Information Technology Equipment, Safety - Part 1: General Requirements
Canadian Regulatory Safety Standard (Bi-National standard, with UL 60950-1).
9370 RNC CSA certificate and report:
Master Contract : 154792
Project : 2031833
Certificate : 1888020
This certification is marked on the equipment main nameplate label. If the local Authority
Having Jurisdiction (AHJ) require prior or additional verification of this certification, a
Product Certificate of Compliance can be obtained from the specific Certification Body
by the Business/Product Unit Applicant for the product or by contacting the Technical
Support Services, within the Canada at +1 630 224 4762, prompt 2.
Any modifications to this equipment are not permitted without review and official written
authorization from the specific Certification Body. Unauthorized changes may violate the
Product Safety certification. Modifications or changes authorized by official CN/CNN are
assumed to have received prior approval from this Lab.
Indoor applications
This equipment is intended for installation in restricted access locations where access is
controlled or where access can only be gained by service personnel with a key or tool.
....................................................................................................................................................................................................................................
Product conformance statements Compliance for Canada
....................................................................................................................................................................................................................................
Eco-Environmental Statements
Packaging collection and recovery requirements
Countries, states, localities, or other jurisdictions may require that systems be established
for the return and/or collection of packaging waste from the consumer, or other end user,
or from the waste stream. Additionally, reuse, recovery, and/or recycling targets for the
return and/or collection of the packaging waste may be established. For more information
regarding collection and recovery of packaging and packaging waste within specific
jurisdictions, contact the Alcatel-Lucent Environment, Health and Safety organization.
....................................................................................................................................................................................................................................
Product conformance statements Compliance for China
....................................................................................................................................................................................................................................
Compliance for China

Overview
The statements that follow are the product conformance statements that apply to the
Alcatel-Lucent 9370 Radio Network Controller when deployed in China.
Eco-Environmental Statements
Material content compliance
The People's Republic of China Ministry of Information Industry has published a
regulation (Order #39) and associated standards regarding restrictions on hazardous
substances (China RoHS). Currently, the legislation requires all Electronic and
Information Products (EIP) to comply with certain labeling and documentation
requirements. Alcatel-Lucent products manufactured on or after 1 March 2007, that are
intended for sale to customers in the China market, must comply with these requirements.
In accordance with the People's Republic of China Electronic Industry Standard Marking
for the Control of Pollution Caused by Electronic Information Products
(SJ/T11364-2006), customers may access the Alcatel-Lucent Hazardous Substances Table
at (http://www.alcatel-sbell.com.cn/wwwroot/images/upload/private/1/media/ChinaRoHS.
pdf).
....................................................................................................................................................................................................................................
Product conformance statements Compliance for European Union
....................................................................................................................................................................................................................................
Compliance for European Union

Overview
Alcatel-Lucent 9370 Radio Network Controller when deployed in the European Union.
Declaration of conformity for radio and telecommunication terminal equipment
under the scope of Directive 1999/5/EC
Hereby, Alcatel-Lucent declares that the equipment documented in this publication is in
compliance with the essential requirements and other relevant provisions of Directive
1999/5/EC.
The technical documentation as required by the Conformity Assessment procedure is kept
at the Alcatel-Lucent location which is responsible for this product. For more information,
contact your local Alcatel-Lucent Customer Service Organization.
CE Marking Statement
This product has been CE-marked in accordance with the following European Directives:
Directive 1999/5/EC Radio and Telecommunication Terminal Equipment (R&TTE) of
the European Parliament and of the council.
Directive 2004/108/EC Electromagnetic Compatibility (EMC)
Directive 73/23/EEC Low Voltage Directive (LVD)
Directive 2002/96/EC Waste Electrical and Electronic Equipment (WEEE)
Directive 2002/95/EC Restriction of the use of certain Hazardous Substances in
Electrical and Electronic Equipment (RoHS)
EMC compliance
The equipment complies with the following EMC specifications:
EN 300 386 (Europe)
EN 55022 (Europe) Class B
EN 55024 (Europe)

The equipment complies with the following product safety specifications:
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
CB Report is issued by CSA and provides regulatory safety compliance to International
and European markets and covers the following standards:
IEC 60950-1 Information technology equipment - Safety - Part 1: General
requirements International Regulatory Safety Standard.
EN 60950-1 Information technology equipment - Safety Part 1: General requirements
European Standard Regulatory Safety Standard.
9370 RNC CB Report
Reference number: CB 154792-1889473
Certificate Reference: CA/8762M2/CSA
Eco-environmental Statements
Recycling / take-back / disposal of products and batteries
Electronic products and batteries bearing or referencing the symbols shown below shall
be collected and treated at the end of their useful life, in compliance with applicable
European Union and other local legislation. They shall not be disposed of as part of
unsorted municipal waste. Due to materials that may be contained in the product and
batteries, such as heavy metals, the environment and human health may be negatively
impacted as a result of inappropriate disposal.
Note: For electronic products put on the market in the European Union, a solid bar
under the crossed-out wheeled bin indicates that the product was put on the market
after 13 August 2005.
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Note: For batteries put on the market in the European Union, a chemical symbol Hg
(mercury), Cd (cadmium), or Pb (lead), or a combination of those symbols, beneath
the cross-out wheeled bin indicates that the battery contains the corresponding heavy
metals.
Moreover, in compliance with legal requirements and contractual agreements, where

applicable, Alcatel-Lucent will offer to provide for the collection and treatment of
Alcatel-Lucent products bearing the logo at the end of their useful life, or products
displaced by Alcatel-Lucent equipment offers.
For information regarding take-back of equipment by Alcatel-Lucent, or for more
information regarding the requirements for recycling/disposal of a product, please contact
your Alcatel-Lucent account manager. Visit the Alcatel-Lucent Take-Back
(http://www.alcatel-lucent.com/product_takeback) web page, or contact Alcatel-Lucent
Takeback Support (mailto:takeback@alcatel-lucent.com) . For technical information on
product treatment, see the Alcatel-Lucent Recycling Information at http://www.
alcatel-lucent.com/product_recycling.
European Union (EU) Directive 2002/95/EC, Restriction of the use of certain Hazardous
Substances (RoHS), restricts the use of lead, mercury, cadmium, hexavalent chromium,
and certain flame retardants in electrical and electronic equipment. This Directive applies
to electrical and electronic products placed on the EU market after 1 July 2006, with
various exemptions, including an exemption for lead solder in network infrastructure
equipment. Alcatel-Lucent products shipped to the EU after 1 July 2006 comply with the
EU RoHS Directive.
....................................................................................................................................................................................................................................
Product conformance statements Compliance for United States
....................................................................................................................................................................................................................................
Compliance for United States

Overview
Alcatel-Lucent 9370 Radio Network Controller when deployed in the United States.
Federal communications commission

Note: Changes or modifications not expressly approved by Alcatel-Lucent could void
the user's authority to operate the equipment.
This device complies with Part 15 of the FCC Rules. Operation is subject to the following
two conditions:
This device may not cause harmful interference
This device must accept any interference received, including interference that may
cause undesired operation.
FCC Part 15 Class A
This equipment has been tested and found to comply with the limits for a Class A digital
device, pursuant to Part 15 of the FCC Rules. These limits are designed to provide
reasonable protections against harmful interference when the equipment is operated in a
commercial environment. This equipment generates, uses, and can radiate radio frequency
energy and, if not installed and used in accordance with the instruction manual, may
cause harmful interference to radio communications. Operation of this equipment in a
residential area is likely to cause harmful interference, in which case the user will be
required to correct the interference at the user's expense.

The Alcatel-Lucent 9370 Radio Network Controller is Safety Certified.
UL 60950-1 (USA), by Information Technology Equipment - Safety - Part 1: General
Requirements US Regulatory Safety Standard .
9370 RNC CSA Certificate and Report:
Master Contract : 154792
Project : 2031833
Certificate : 1888020
This certification is marked on the equipment main nameplate label. If the local Authority
Having Jurisdiction (AHJ) require prior or additional verification of this certification, a
Product Certificate of Compliance can be obtained from the specific Certification Body
by the Business/Product Unit Applicant for the product or by contacting Technical
Support Services, within the United States at +1 630 224 4762, prompt 2:
....................................................................................................................................................................................................................................
Product conformance statements Compliance for United States
....................................................................................................................................................................................................................................
Any modifications to this equipment are not permitted without review and official written
authorization from the specific Certification Body. Unauthorized changes may violate the
Product Safety Certification. Modifications or changes authorized by official CN/CNN
are assumed to have received prior approval from this lab.
Indoor applications
This equipment is intended for installation in restricted access locations where access is
controlled or where access can only be gained by service personnel with a key or tool.
Access to this equipment is restricted to qualified service personnel only.
Eco-Environmental statements
for the return and/or collection of packaging waste from either the consumer or the end
user, or from the waste stream. Additionally, reuse, recovery, and/or recycling targets for
the return and/or collection of the packaging waste may be established. For more
information regarding collection and recovery of packaging and packaging waste within
specific jurisdictions, contact the Alcatel-Lucent Environment, Health and Safety
organization or Alcatel-Lucent Hazardous Waste Center technical support at (888)
539-2783.
The following notification applies to Alcatel-Lucent products distributed for sale, resale,
or use.
This product, part, or both may include a lithium-manganese dioxide battery, which
contains very small amounts of a perchlorate substance. Special handling may apply.
For California
Perchlorate Material - special handling may apply. See www.dtsc.ca.gov/hazardouswaste/
perchlorate.
....................................................................................................................................................................................................................................
Index
C CAS commands, 7-2
CAS operational commands, 7-20

CAS provisioning
SS7 SaalNni, 7-16
.............................................................
D documentation roadmap, 1-2
.............................................................
H hairpin connections, 3-7
hairpin removal, 4-2

.............................................................
I Iub interface, 6-3

IuCs interface, 6-4
.............................................................
O operational commands, 7-13
.............................................................
R roadmap
documentation, 1-2
.............................................................
S Safety statements, 2-1, 2-2
SS7 SaalNni, 7-20
....................................................................................................................................................................................................................................
Alcatel-Lucent 9370 RNC Alcatel-Lucent Proprietary IN-1
Index
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
IN-2 Alcatel-Lucent Proprietary Alcatel-Lucent 9370 RNC

NN 20500 225

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

NN 20500 225

Hochgeladen von

Copyright:

Verfügbare Formate

Use pursuant to applicable agreements

About this document

Reason for reissue ........................................................................................................................................................................ xi

New in this release ....................................................................................................................................................................... xi

Intended audience ......................................................................................................................................................................... xi

Supported systems ........................................................................................................................................................................ xi

How to use this document ........................................................................................................................................................ xii

Safety information ...................................................................................................................................................................... xii

Prerequisites .................................................................................................................................................................................. xii

Conventions used ........................................................................................................................................................................ xii

Related information ................................................................................................................................................................... xiii

Document support ...................................................................................................................................................................... xiv

Technical support ....................................................................................................................................................................... xiv

How to order ................................................................................................................................................................................ xiv

How to comment ........................................................................................................................................................................ xiv

1 Roadmap to Radio Network Controller documentation

Overview ...................................................................................................................................................................................... 1-1

Roadmap to Radio Network Controller documentation ............................................................................................. 1-2

Overview ...................................................................................................................................................................................... 2-1

Structure of safety statements ............................................................................................................................................... 2-2

Overview ...................................................................................................................................................................................... 3-1

Overview ...................................................................................................................................................................................... 3-2

Permanent Virtual Connection (PVC) ............................................................................................................................... 3-3

Soft Permanent Virtual Connections (SPVC) ................................................................................................................. 3-4

Physical position of hairpins

Situating hairpins ...................................................................................................................................................................... 3-5

Hairpin connections ................................................................................................................................................................. 3-7

Overview ................................................................................................................................................................................... 3-10

4 Hairpin removal process

Overview ...................................................................................................................................................................................... 4-1

Steps for hairpin removal ....................................................................................................................................................... 4-2

Overview ...................................................................................................................................................................................... 5-1

Moving the SPVC endpoints ................................................................................................................................................ 5-2

NodeB to OAM connectivity ................................................................................................................................................ 5-5

6 Procedures for moving endpoints

Overview ...................................................................................................................................................................................... 6-1

Aal2If and the Iub, IuCs and Iur interfaces

Introduction ................................................................................................................................................................................. 6-2

Iub and open Iub interface ..................................................................................................................................................... 6-3

IuCs Interface ............................................................................................................................................................................. 6-4

Iur interface ................................................................................................................................................................................. 6-6

Iub interface ................................................................................................................................................................................ 6-9

Introduction .............................................................................................................................................................................. 6-11

IuCS and IuPS interfaces ..................................................................................................................................................... 6-12

Iur Interface .............................................................................................................................................................................. 6-13

7 CAS commands and PNNI hairpin removal

Overview ...................................................................................................................................................................................... 7-1

ATMPE CAS provisioning and operational commands ............................................................................................. 7-2

Aal2If and IubIf provisioning commands ........................................................................................................................ 7-5

Aal2If and IubIf operational commands ........................................................................................................................ 7-13

SS7 SaalNni CAS provisioning commands .................................................................................................................. 7-16

SS7 SaalNni CAS operational commands .................................................................................................................... 7-20

8 Removing the hairpins

Overview ...................................................................................................................................................................................... 8-1

Tools for hairpin removal ....................................................................................................................................................... 8-2

Removing the hairpin .............................................................................................................................................................. 8-3

A Product conformance statements

Overview ..................................................................................................................................................................................... A-1

Regulatory requirement compliance ................................................................................................................................. A-2

Compliance for Canada ......................................................................................................................................................... A-3

Compliance for China ........................................................................................................................................................... A-5

Compliance for European Union ....................................................................................................................................... A-6

Compliance for United States ............................................................................................................................................. A-9