0% found this document useful (0 votes)

207 views974 pages

1xRNC OAM PDF

Lucent EVDO RNC

Uploaded by

avishek2005

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

207 views974 pages

1xRNC OAM PDF

Lucent EVDO RNC

Uploaded by

avishek2005

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

You are on page 1/ 974

See notice on first page

PRELIMINARY

Alcatel-Lucent 9270 1x Radio Network

Controller (RNC)
Release 31 and later
Operations, Administration, and Maintenance (OA&M)

401-710-082
Issue 14
September 2009

Copyright 2009 Alcatel-Lucent

Unpublished and Not for Publication
All Rights Reserved

PRELIMINARY

Alcatel-Lucent - Proprietary
This document contains proprietary information of Alcatel-Lucent and
is not to be disclosed or used except in accordance with applicable agreements.

PRELIMINARY

See notice on first page

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 2009 Alcatel-Lucent. All Rights Reserved.

Alcatel-Lucent - Proprietary
See notice on first page

PRELIMINARY

Contents

About this information product

Purpose

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

xxix

Reason for reissue

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

xxix

Intended audience

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

xxxi

How to use this information product

Conventions used

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

Systems supported

xxxi

xxxiii

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

Related information products

Related training

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

xxxv

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

xxxv

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

xxxv

To obtain technical support, documentation, and training or submit feedback

Safety information
How to comment

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

xxxv

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

xxxvi

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

xxxvi

Part I: System description

Safety and general information

Overview

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

1-1

Hazard statements
Overview

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

General hazard statements

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

1-3

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

1-5

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
iii
Issue 14, September 2009
See notice on first page

PRELIMINARY

Structure of hazard statements

1-2

PRELIMINARY

Contents

System Architecture
Overview

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

CDMA 1X RNC evolution

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

2-2
2-8

Network functional architecture

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

Support for 2G and circuit data

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

2-12

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

2-13

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

2-14

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

2-16

Support for multiple RNCs

RNC alternate routing
IP backhaul

IP-based soft handoff

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

CDMA 1X RNC software architecture

2-20

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

2-24

OA&M software components and interfaces

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

Call processing software components and interfaces

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

User bearer processing software components and interfaces

2-26
2-29

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

2-32

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

2-35

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

2-37

Physical Network Connectivity

B-PCF Architecture

2-17

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

CDMA 1X RNC hardware architecture overview

CDMA 1X RNC high-level call control signaling

2-1

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

2-42

Hardware architecture
Overview

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

3-1

RNC cabinet
Overview

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

Cabinet indicators

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

PRELIMINARY

3-9

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

3-12

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

3-14

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

3-17

Frame Interface Panel (FIP)

Power distribution shelf
Terminal server

3-3

cPSB chassis and components

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

3-20

Power trays

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

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

3-24

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

3-26

Chassis fan trays

Alarm card

3-22

Ethernet switch card

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

TPU shelf components

3-27

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

3-30

GICC cards

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

3-33

CICC cards

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

3-37

Solaris B-PCF

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

PRELIMINARY

Contents

3-39

MM-AP Cabinet
Overview

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

3-41

RNC-AP (400S server)

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

3-43

RNC-AP (410S server)

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

3-47

OAM proxy AP (400S server)

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

3-50

OAM proxy AP (410S server)

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

3-53

OA&M Architecture
Overview

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

Executive Cellular Processor (ECP)

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

Operations and Management Platform (OMP)

Element Management System (EMS)
Command Line Interface (CLI)
Input/Output Messages

4-2

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

4-4

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

4-8

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

4-27

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

4-28

UNIX command interface

RNC logs

4-1

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

4-37

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

4-38

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

4-39

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

4-40

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

4-41

Status Display Pages (SDPs)

RNC alarms

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
v
Issue 14, September 2009
See notice on first page

PRELIMINARY

Recent Change and Verify (RC/V)

PRELIMINARY

Contents

Service measurements

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

Read-Only Printer (ROP)

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

Operations and Maintenance Center Radio Access Network (OMC-RAN)

To enable/disable OMC-RAN

4-44

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

4-45

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

4-49

Local Maintenance Terminal (LMT)

4-43

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

4-56

Maintenance states
Overview

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

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

5-2

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

5-5

RNC-AP and OAM proxy AP

TPU managed object states

5-1

SC-GICC service maintenance state

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

5-9

Part II: System administration

System management, methods, and procedures

Overview

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

6-1

RNC-related interfaces
Overview

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

Methods for RNC-AP and OAM Proxy AP login

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

6-5

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

6-6

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

6-11

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

6-14

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

6-17

Accessing TICLI

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

6-18

Access via OMP

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

6-19

Hypertext Transfer Protocol modification

Accessing the TPU GUI directly
Accessing TPU CLI

PRELIMINARY

6-4

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

Logging on to Element Management System (EMS)

Accessing TPU GUI

6-3

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

6-23

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

6-24

Access via direct login

Access via LMT

Accessing Recent Change/Verify (RC/V)

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

6-25

Accessing Status Display Pages (SDPs)

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

6-27

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

6-28

Backing up and restoring

Overview

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

6-29

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

6-32

Backing up/restoring AP configuration data

Backing up AP configuration data

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

6-34

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

6-36

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

6-39

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

6-42

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

6-45

Restoring AP configuration files and packages

Backing up/restoring RNC Database
Maintaining directory/file space
Backing up RNC database
Restoring RNC database

Rebooting CICCs and non-APS GICCs

Rebooting APS GICCs

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

6-55

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

6-60

PRELIMINARY

Contents

Part III: Fault management

Monitoring the system

Overview

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

Monitoring status via SDP

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

Monitoring RNC-AP/OAM proxy AP activities

Monitoring RNC/TPU activites

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

Monitoring RNC-related activities via logs

Accessing Admin logs

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

7-2
7-4

7-13

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

7-28

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

7-33

Monitoring activities via Read-Only Printer (ROP)

Crossover LAN connectivity monitoring

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

7-36

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

7-38

Cross-over LAN cable connection and verification

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

7-39

Troubleshooting
Overview

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

8-1

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
vii
Issue 14, September 2009
See notice on first page

PRELIMINARY

7-1

PRELIMINARY

Contents

Enabling troubleshooting
Overview

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

RNC failure types

Customer tools

8-3

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

8-4

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

8-5

Component indicators
RNC health check

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

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

B-PCF monitoring and flow control

8-11

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

8-18

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

8-24

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

8-26

1xRNC packet filtering

Far end CA audit

8-8

To enable/disable far end CA audits

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

8-27

Application Processor (AP) problem solving

Overview

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

RNC AP OOS (components or alarms)

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

OAM Proxy AP OOS (components or alarms)

RNC-AP rebooting

8-31

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

8-34

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

8-37

LANS 1 and/or 2 OOS

EIN LAN OOS

8-30

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

8-39

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

8-41

LANS 3 and/or 4 OOS

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

8-42

Traffic Processing Unit (TPU) problem solving

Overview

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

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

8-44

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

8-46

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

8-48

TPU OOS Components or Alarms

Alarm card fault

PRELIMINARY

ESC fault

8-43

GICC fault

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

8-50

CICC fault

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

8-53

B-PCF fault

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

8-55

E-PCF fault

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

8-57

viii

PCF reachability alarm

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

8-59

Assert Brevity Control

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

8-62

TPU GUI access problem solving

Overview

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

Unable to access TPU GUI

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

Verify correct IP address for direct access

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

Verify TPU GUI application is running (CLI command)

8-65
8-67

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

8-69

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

8-74

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

8-76

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

8-81

Eliminate file conflicts and verify proxies

Update Java runtime parameters

8-64

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

Verify TPU GUI application is running (EMS GUI)

Verify Java version for Internet Explorer

8-63

PRELIMINARY

Contents

Automatic Protection Switching (APS) problem solving

Overview

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

APS mated GICC not available - major alarm

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

8-88

APS Data Out Of Sync failure - major alarm

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

8-89

APS far end protection failure - major alarm

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

8-90

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

8-91

APS mode mismatch - major alarm

Unable to protection switch due to AISL - major alarm

8-87

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

8-93

APS protection byte failure - warning

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

8-94

APS channel mismatch - minor alarm

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

8-96

Replace components
Overview

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

9-2

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

9-3

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

9-4

Hot-swappability versus cold swappability

Replace 400S/410S server components

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

9-5

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
ix
Issue 14, September 2009
See notice on first page

PRELIMINARY

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

Customer-replaceability versus field-replaceability

RNC replaceable components

9-1

PRELIMINARY

Contents

Replace TPU shelf components

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

Replace an SC-GICC or non-SC-GICC card

Replace a CICC card
Replace a B-PCF

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

9-6
9-7

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

9-18

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

9-23

Replace a cPSB chassis fan tray

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

9-37

Replace cPSB chassis DC power supply

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

9-40

Replace an air filter in the cPSB chassis

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

9-47

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

9-52

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

9-53

Replace RNC cabinet components

Replace a cabinet alarm board

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

9-56

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

9-59

Replace a circuit breaker in the ECBU

Loopback Testing

Initiating PSU loopback test

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

9-60

Part IV: Performance management

Service measurement
Overview

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

10-1

Service measurement basics

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

10-2

CDN service measurements

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

10-3

RNC Performance Management

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

10-6

RNC-related XML count groups

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

10-9

Change B-PCF Service Measurement (SM) interval

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

10-13

Part V: Configuration management

Software configuration management

PRELIMINARY

Overview

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

RC/V provisioning

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

FAF/QFAF control

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

RNC fault management parameters

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

11-1
11-2

11-12
11-15

Verify or modify RNC fault management parameters

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

11-16

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

11-20

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

11-21

Software Update Automation (SUA)

Generic retrofit

Golden image restoration (B-PCF)

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

To download cpio file from Online Customer Support Site (OLCS)

To load and install B-PCF golden image package
12

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

11-26

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

11-35

Configuring ATM connectivity in RNCs SHO universe

Overview

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

ATM SHO universe connection type considerations

Adding a new remote subnet to RNC
Removing a subnet from the RNC

12-2

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

12-6

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

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

Moving an RNC from one local subnet to another

Changing a subnets VCC VPI

12-12
12-18

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

12-23

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

12-28

Automatic Protection Switching (APS)

Overview

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

13-1

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

13-2

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

13-4

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

13-5

Changing APS mode

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

13-9

Changing APS mode

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

5EGW Redundancy/Automatic Protection Switching (APS)

APS standard for RNC OC3 facilities
Preparing to enable APS

12-1

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

Changing intra-subnet PVC connection types

11-25

PRELIMINARY

Contents

13-10

Configuring IPSHO connectivity

Overview

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

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

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

14-5

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

14-6

Simultaneous support of IP and ATM SHO

IPSHO GICC IP addressing

14-2

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
xi
Issue 14, September 2009
See notice on first page

PRELIMINARY

IPSHO connectivity

14-1

PRELIMINARY

Contents

IPSHO traffic handling

IPSHO configuration

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

14-8

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

14-9

Change cluster ID of a single MSC

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

Integrate IPSHO enabled RNC and its neighbors

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

14-12
14-16

Growing/Degrowing TPU cards

Overview

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

15-1

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

15-3

Growth
Overview

Growing 5E Gateway (5EGW) GICCs

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

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

15-14

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

15-16

Physically install GICC pair and connect cables

Add and configure GICC pair via TPU GUI

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

15-30

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

15-33

Growing 5E Gateway (5EGW) on unused OC3 ports

Physically connect OC3 cable

Configure OC3 (ATM) port(s) as 5EGW

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

15-34

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

15-44

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

15-46

Growing an IPSHO GICC pair

Growing CICCs

15-7

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

15-48

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

15-52

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

15-76

Install plug and play CICC card in shelf

Growing B-PCF(s)
Configure B-PCF

Configure PDSN(s)

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

15-83

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

15-92

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

15-99

Physically install B-PCF in TPU shelf

De-Growth

PRELIMINARY

Overview

Degrowing GICCs

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

Shutdown the GICC card

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

Degrow GICC via TPU GUI

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

15-102
15-103
15-106

xii

Remove GICC card

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

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

15-116

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

15-117

Degrowing 5E gateway on used OC3 port

Shutdown the 5EGW

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

15-120

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

15-127

Deprovision 5E gateway(s) on GICC

Degrowing CICCs

Shutdown the CICC card

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

Remove plug and play CICC from shelf

15-128

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

15-131

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

15-135

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

15-136

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

15-140

Degrowing a B-PCF
Shutdown B-PCF
Halt B-PCF

15-112

Delete B-PCF presence from RNC Database

Physically remove B-PCF

PRELIMINARY

Contents

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

15-142

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

15-147

Part VI: Security management

Managing security
Overview

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

16-1

Wireless network interfaces

Overview

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

OMP security guidelines

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

OMC-RAN security levels

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

16-3
16-4

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

16-5

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

16-6

MM-APC security management

Eliminate open consoles

16-2

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

16-10

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

16-11

Centralized security management phase three

TPU GUI login security administration

TPU GUI login synchronization

Adminstrator tasks

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

16-13

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

16-15

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
xiii
Issue 14, September 2009
See notice on first page

PRELIMINARY

Overview

PRELIMINARY

Contents

Add local TPU GUI user

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

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

16-22

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

16-26

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

16-30

Edit local TPU GUI user access profile

Delete local TPU GUI system user
Clear configuration lock

Reactivate local TPU GUI user

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

16-38

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

16-40

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

16-41

Updating local TPU GUI password

Controls and indicators

Overview

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

Cabinet indicators
Power indicators

ESC indicators

A-2

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

A-3

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

A-4

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

A-7

CICC indicators

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

A-10

GICC indicators

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

A-13

B-PCF indicators

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

A-17

Command Reference
Overview

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

B-1

apactivate

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

B-3

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

B-5

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

B-6

apappconfig
apapply

PRELIMINARY

A-1

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

Alarm card indicators

16-34

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

Verify EMS user accounts synchronization status

Change local password

16-17

apbackout

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

B-7

apbackup

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

B-9

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

B-12

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

B-16

apcc_ip_migr
apinstall

xiv

apoffline ..................................................................................................................................................................................... B-18

aponline

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

B-19

aponlygr

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

B-20

appkgchk

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

B-21

appkginfo

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

B-23

appkgload

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

B-25

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

B-26

appkgrm

appkgtrans

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

B-28

appkgunload

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

B-31

applatconfig

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

B-33

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

B-35

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

B-36

aprecover
aprenew

PRELIMINARY

Contents

apsettimers

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

B-40

flxactivate

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

B-41

flxbackout

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

B-43

flxbackup ................................................................................................................................................................................... B-45

flxbuninfo

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

B-46

flxchkfwacv

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

B-47

flxcoremgmt

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

B-49

flxcronmgmt

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

B-50

flxdeactivate

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

B-52

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

B-53

flxfwac

flxfwacv

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

flxname

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

B-58

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

B-60

flxpkginfo

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

SMxmldump(1)

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

B-62
B-63

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
xv
Issue 14, September 2009
See notice on first page

PRELIMINARY

flxlogmgmt

B-55

PRELIMINARY

Contents

Service measurement supplement

Overview

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

SMxmldump tool

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

C-2

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

C-4

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

C-5

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

C-8

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

D-1

Issue 7

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

D-2

Issue 6

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

D-3

Issue 5

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

D-5

Issue 4

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

D-8

Issue 3

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

D-15

Issue 8

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

D-21

Issue 9

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

D-22

Time zone synchronization (OMP and RNC-AP)

Time zone verification and update
Managing XML RNC PM data
D

C-1

History of revision
Overview

Issue 10

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

D-23

Glossary

PRELIMINARY

Index

xvi

PRELIMINARY

List of tables

Part I: System description

System Architecture
2-1

E-PCF/B-PCF comparison

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

2-2

Cabinet hardware specifics

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

2-20

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

3-10

2-5

Hardware architecture
3-1

LEDs and outputs

3-2

ECBU breaker assignments

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

3-15

3-3

ESC ports and connections

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

3-28

3-4

GICC Services

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

3-35

OA&M Architecture
TI Commands

4-2

RNC-AP and OAM Proxy AP-Related Screens

4-3

1X RNC TPU page

4-4

Link from Configuration Data icon

4-5

Link from Installation & Software Updates icon

4-6

Link from Network Elements icon

4-7

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

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

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

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

4-3
4-8

4-11
4-12

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

4-17

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

4-17

Link from Alarms icon

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

4-18

4-8

Link from BPCFs icon

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

4-18

4-9

Link from Admin button

4-10

Link from Change Password button

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

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

4-19
4-20

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
xvii
Issue 14, September 2009
See notice on first page

PRELIMINARY

4-1

PRELIMINARY

List of tables

4-11

1X RNCs button link

4-12

Global ConfigData button link

4-13

APS Status button link

4-14

BHS Status link

4-15

Neighbor List (IPSHO GICC View) link

4-16

CA-IP Map (IPSHO GICC View) link

4-17

CA-IP Con Status link

4-18

Neighbor List (RNC DB View) link

4-19

CA-IP Map (RNC DB View) link

4-20

Failed PVCs button link

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

4-21

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

4-21

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

4-23

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

4-23

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

4-23

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

4-24

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

4-24

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

4-25

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

4-25

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

4-26

Maintenance states
5-1

AP managed objects and states

5-2

TPU managed objects and associated states

5-3

SC-GICC service and all associated states

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

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

5-2
5-8

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

5-10

Part III: Fault management

PRELIMINARY

Monitoring the system

7-1

Monitoring Activity via CLI

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

7-11

7-2

Monitoring Activity via CLI

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

7-23

7-3

Outputs for ROP Stream

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

7-36

Troubleshooting
8-1

Customer tools

8-2

Card controls and indicators

8-3

Using SDP, EMS-GUI, and TPU-GUI

8-4

Using TICLI and TPU-CLI for RNC-APs

8-5

Using TICLI and TPU-CLI for OAM Proxy APs

8-6

Using TICLI and TPU-CLI for each TPU shelf

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

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

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

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

8-5
8-8

8-15
8-16

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

8-17

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

8-17

xviii

8-7

RNC-AP OOS

8-8

OAM Proxy AP OOS

8-9

RNC-AP rebooting

8-10

LANS 1 and/or 2 OOS

8-11

EIN LAN OOS

8-12

LANS 3 and/or 4 OOS

8-13

TPU OOS Components or Alarms

8-14

Alarm card fault

8-15

ESC fault

8-16

GICC fault

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

8-50

8-17

CICC fault

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

8-53

8-18

B-PCF fault

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

8-55

8-19

E-PCF fault

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

8-57

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

8-31

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

8-34

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

8-37

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

8-39

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

8-41

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

PRELIMINARY

List of tables

8-42

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

8-44

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

8-46

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

8-48

Replace components
9-1

B-PCF states

9-2

B-PCF port numbers

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

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

9-27
9-30

Part V: Configuration management

Software configuration management

11-1

Timeline of Retrofit Activities

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

11-21

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

15-11

Growing/Degrowing TPU cards

Fiber cables

15-2

B-PCF Dynamic Parameters

15-3

B-PCF Static Parameters

15-4

PDSN parameter form

15-5

PDSN Parameters

15-6

Failed PSDN action

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

15-55

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

15-58

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

15-67

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

15-68

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

15-74

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
xix
Issue 14, September 2009
See notice on first page

PRELIMINARY

15-1

PRELIMINARY

List of tables

15-7
A

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

15-93

Controls and indicators

A-1

Cabinet LEDs

A-2

ECBU LEDs

A-3

Alarm card LEDs

A-4

ESC LEDs

A-5

CICC LEDs

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

A-12

A-6

GICC LEDs

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

A-15

A-7

Alarm card LEDs

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

A-2

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

A-3

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

A-5

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

A-9

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

A-19

Service measurement supplement

C-1

PRELIMINARY

B-PCF port numbers

Tunable details

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

C-9

PRELIMINARY

List of figures

Part I: System description

System Architecture
Existing 3G 1X network architecture

2-2

CDMA 1X RNC architecture for data off-load

2-3

E-PCF and B-PCF options

2-4

High-level CDMA 1X RNC network functional architecture

2-5

Logical RNC functions

2-6

Ethernet/IP topology

2-7

IPSHO network with ATM SHO network

2-8

IPSHO network configuration

2-9

RNC related cabinet types (high-level view)

2-10

CDMA 1X RNC Software Architecture

2-11

CDMA 1X RNC OA&M Interfaces

2-12

CDMA 1X RNC Call Processing Interface

2-13

CDMA 1X RNC User Bearer Interfaces

2-14

Physical network connectivity

2-15

B-PCF functional decomposition

2-16

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

2-2

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

2-4

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

2-5

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

2-8

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

2-10

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

2-11

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

2-17

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

2-18

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

2-20

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

2-24

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

2-27

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

2-30

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

2-33

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

2-35

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

2-38

B-PCF control and data paths

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

2-39

2-17

B-PCF management software

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

2-40

2-18

1X Packet data call session initialization

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

2-42

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
xxi
Issue 14, September 2009
See notice on first page

PRELIMINARY

2-1

PRELIMINARY
PRELIMINARY

List of figures

2-19

Mobile reactivation call signaling flow

2-20

Network reactivation call signaling flow

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

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

2-44
2-46

Hardware architecture
3-1

RNC cabinet (2310)

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

3-4

3-2

Cabinet aesthetics

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

3-5

3-3

RNC cabinet with 5ESS stanchions and end guard

3-4

Cabinet LEDs

3-5

Cabinet LED alarms and triggers

3-6

Frame Interface Panel (FIP)

3-7

Power input views

3-8

Power distribution shelf

3-9

Power Distribution Block diagram

3-10

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

3-6

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

3-9

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

3-10

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

3-12

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

3-13

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

3-14

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

3-14

Front view of terminal server

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

3-17

3-11

Rear view of terminal server

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

3-17

3-12

Terminal server port assignments

3-13

cPSB chassis (Front View)

3-14

cPSB Power Block diagram

3-15

Chassis air filter

3-16

Fan trays with frame maintenance unit (FMU) in operating position.

3-17

Fan tray with FMU in position for fan maintenance.

3-18

Alarm card

3-19

Ethernet Switch Card

3-20

Frame level wiring architecture

3-21

Minimum TPU shelf configuration

3-22

Maximum TPU Shelf Configuration

3-23

Non-optical ethernet GICC (1.0) card

3-24

Optical ethernet GICC (1.1) card

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

3-18

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

3-20

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

3-22

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

3-23

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

3-24

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

3-25

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

3-26

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

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

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

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

3-27
3-29
3-31
3-32

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

3-33

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

3-34

xxii

3-25

CICC card

3-26

Solaris B-PCF

3-27

Typical MM-AP growth frame/cabinet

3-28

RNC-AP 400S Server

3-29

Hardware Configuration for RNC-AP 400S pairs

3-30

RNC-AP 410S Server

3-31

Hardware Configuration for RNC-AP 410S pairs

3-32

OAM Proxy AP 400S Server

3-33

Provisioning and configuration architecture

3-34

OAM Proxy AP 410S Server

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

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

3-37
3-39

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

3-41

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

3-43

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

3-45

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

3-47

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

3-48

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

3-50

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

3-51

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

3-53

PRELIMINARY

List of figures

OA&M Architecture
4-1

OMP System Architecture

4-2

ECP Maintenance and Administrative Access

4-3

5ESS Switch Maintenance and Administration Access

4-4

Alcatel-Lucent CDMA Network with OMC-RAN Solution

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

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

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

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

4-4
4-5
4-6

4-46

Maintenance states
5-1

Operational state

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

5-5

5-2

Usage state

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

5-6

5-3

Administrative state

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

5-7

Part II: System administration

System management, methods, and procedures

Account locked out

6-2

TPU GUI login screen

6-3

1X RNC TPU Web launch page

6-4

OMP Technician menu

6-5

ECP Access menu

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

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

6-8

6-15

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

6-16

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

6-19

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

6-20

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
xxiii
Issue 14, September 2009
See notice on first page

PRELIMINARY

6-1

PRELIMINARY

List of figures

6-6

Miscellaneous applications menu

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

6-22

6-7

Accessing RC/V via OMP menus

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

6-25

6-8

Standby GICC and bundle verification

6-9

Cmds pull down menu

6-10

Confirm install

6-11

Update installation

6-12

Issuing lock

6-13

Issuing shutdown

6-14

Issuing unlock

6-15

Installation complete (standby GICC)

6-16

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

6-49

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

6-49

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

6-50

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

6-51

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

6-52

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

6-52

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

6-52

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

6-52

Install command invoked

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

6-53

6-17

Issuing second shutdown

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

6-53

6-18

SC-GICC reboots

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

6-53

6-19

Second SC-GICC installation complete

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

6-53

Part III: Fault management

PRELIMINARY

Monitoring the system

7-1

Typical example of RNC SDP status indicator

7-2

RNC-AP activity status monitoring

7-3

RNCM status page

7-4

TCS status page

7-5

OAM Proxy AP activity status monitoring

7-6

RNC-DBMS status

7-7

TPU GUI status

7-8

1X RNC TPU web page

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

7-13

7-9

1X RNC Summary page

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

7-15

7-10

Installation and software options page

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

7-2

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

7-5

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

7-6

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

7-7

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

7-8

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

7-9

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

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

7-10

7-16

xxiv

7-11

TPU network elements (filter all) page

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

7-17

7-12

TPU alarms page

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

7-18

7-13

Failed PVCs page

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

7-19

7-14

APS status

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

7-20

7-15

B-PCF performance statistics

7-16

1X-RNC information page

7-17

RNC call processing status page

7-18

BHS statistics

7-19

RNC DB global admin log examples

7-20

RNC DB admin log examples

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

7-21

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

7-21

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

7-22

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

7-22

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

7-29

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

7-30

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

9-14

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

9-15

PRELIMINARY

List of figures

Replace components
Loosen GICC retention screws

9-2

Partially eject GICC

9-3

Loosen CICC retention screws

9-4

Partially eject CICC

9-5

1X RNC TPU Web page

9-6

TPU page (filter all)

9-7

Initiate shutdown

9-8

Shutdown complete

9-9

FMU in lowered position

9-10

Remove fan drawer

9-11

Front view of air filter and grill

9-12

cPSB chassis DC power supplies (cutout view)

9-13

Injector/ejector handles

9-14

Air filter location

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

9-20

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

9-21

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

9-25

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

9-26

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

9-28

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

9-28

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

9-38

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

9-38

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

9-40

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

9-41

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

9-42

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

9-48

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
xxv
Issue 14, September 2009
See notice on first page

PRELIMINARY

9-1

PRELIMINARY

List of figures

Part IV: Performance management

Service measurement
10-1

RNC-specific CDMA-PAF-CARR-L counts

10-2

RNC-specific CP CDMA counts

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

10-4

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

10-4

Part V: Configuration management

PRELIMINARY

Software configuration management

11-1

Typical ecppkt form (screen 1)

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

11-3

11-2

Typical ecppkt form (screen 2)

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

11-3

Typical ecppkt form (screen 3)

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

11-4

Typical cell2 form (screen 1)

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

11-5

Typical cell2 form (screen 12)

11-6

Typical apeqp form

11-7

Sample ecp3g form (screen 1)

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

11-7

11-8

Sample ecp3g form (screen 6)

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

11-7

11-9

Sample ecp3g form (screen 7)

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

11-8

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

11-5

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

11-6

Configuring ATM connectivity in RNCs SHO universe

12-1

Example of connectivity with VPCs

12-2

Example of connectivity with VCCs and VPCs

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

12-3

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

12-4

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

13-2

Automatic Protection Switching (APS)

13-1

APS architecture

13-2

Mated pairs when APS is enabled

13-3

Cable configuration necessary prior to APS enable

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

13-6

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

13-7

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

14-2

Configuring IPSHO connectivity

14-1

IP SHO network architecture

14-2

Simultaneous support of IP and ATM SHO

14-3

IP SHO IP Addressing

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

14-5

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

14-6

xxvi

Growing/Degrowing TPU cards

15-1

Minimum TPU Shelf Card Configuration

15-2

GICC and CICC growth (maximum)

15-3

Example Screen 1: Without APS Enabled

15-4

Example Screen 2: With APS Enabled

15-5

Example Screen 1: Without APS Enabled

15-6

Example Screen 2: With APS Enabled

15-7

B-PCF installation sequence

15-8

GICC and CICC Degrowth

15-9

Loosen GICC retention screws

15-10 Partially eject GICC

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

15-5

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

15-21

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

15-22

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

15-38

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

15-39

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

15-54

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

15-100
15-113

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

15-114

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

15-123

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

15-124

15-13 Loosen CICC retention screws

15-14 Partially eject CICC
A

15-3

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

15-11 Without APS enabled

15-12 With APS enabled

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

PRELIMINARY

List of figures

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

15-132

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

15-133

Controls and indicators

A-1

Cabinet LEDs

A-2

Alarm card faceplate

A-3

ESC faceplate

A-4

CICC face plate

A-5

Non-optical ethernet GICC (1.0) faceplate

A-6

Optical ethernet GICC (1.1) faceplate

A-7

B-PCF faceplate

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

A-2

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

A-4

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

A-8

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

A-11

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

A-14

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

A-15

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

A-18

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
xxvii
Issue 14, September 2009
See notice on first page

PRELIMINARY

About this information product

PRELIMINARY

About this information product

Purpose

This Operations, Administration, and Maintenance (OA&M) document provides an

overview of CDMA 1X RNC and procedures for performing OA&M activities on the
CDMA 1X RNC wireless network.
Alcatel-Lucent has changed the name of products within the CDMA portfolio.
The product previously known as the CDMA2000 has been renamed and is now
referred to as the Alcatel-Lucent 9270 1x Radio Network Controller (RNC).
The product previously known as 5ESS DCS is now referred to as 9281 Packet Switch
(PS).
The use of any of these names in this document refer to the same product and
functionality.
Reason for reissue

The following procedures were updated in R33, Issue 14 for MR196387:

Replace an SC-GICC or non-SC-GICC card (p. 9-7)

Replace a B-PCF (p. 9-23)
Degrowing GICCs (p. 15-102)

Degrowing 5E gateway on used OC3 port (p. 15-116).

The following changes were made for R32, Issue 13:

....................................................................................................................................................................................................................................
401-710-082
Alcatel-Lucent - Proprietary
xxix
Issue 14, September 2009
See notice on first page
,

PRELIMINARY

Replace an SC-GICC or non-SC-GICC card (p. 9-7): Add clarification of what

services need to be switched over before shutting down the GICC. The current
wording only mentions ATM switchtomate command, which is not appropriate if
replacing an IPBH or IPSHO GICC.
Replace a B-PCF (p. 9-23): Add several missing steps - timezone modification
and setting system date.

PRELIMINARY

About this information product

Degrowing GICCs (p. 15-102): Add a warning that degrowing a GICC may
cause an outage on an in-service system.
Degrowing 5E gateway on used OC3 port (p. 15-116): Add a warning that only
the ATM services on the SC-GICC should be locked and degrown. Locking the
SC-GICC itself will cause a service interruption.

The following changes were made for R32, Issue 12:

Step added at the end of Replace a B-PCF (p. 9-23) to run the MM security
audit.

The following changes were made for R32, Issue 11:

Updates to the SMxmldump command for the CDMA Short Interval SM Reporting
feature. See Appendix C, Service measurement supplement for information on
SMxmldump, and on the management of XML RNC PM data.

This issue adds the Release 32.0 Restrict Root Login Phase 1: RBAC Roles and
Centralized User Account Management for MM-APs feature. This feature changes
the way in which MM-AP users change their account password and the way in
which MM-AP users obtain permission to execute OAM&P tools. When this
feature is disabled, the feature functionalities are not in affect and pre-R32
procedures are to be used.
When this feature is enabled, procedures are impacted by these feature
functionalities:

A new tool to change your own CAM-managed MM-AP account password.

The mmpasswd tool is used by non-privileged users to change their

CAM-managed account password.

PRELIMINARY

A new way to obtain permissions to execute MM-AP OAM&P tools.

If the Security Administrator has assigned the MM-AP System Administration or
MM-AP Application Administration profile to your account, then no additional
login steps are necessary to use certain tools (however, note that only one profile
may be assigned to a login account, not both).
If the Security Administrator has assigned one or more RBAC roles to your
account (rsecadm, rsysadm, or rappadm), then to use certain tools the user should
use su to rsecadm, rsysadm, or rappadm (as required by the tool to be used),
followed by entering the password for the RBAC role. Refer to RRL and RBAC
Feature Description, 401-662-119, for a list of impacted tools and their assigned
RBAC roles.
Using the root login is still allowed when this feature is enabled, however the
audit trail is lost because root is a shared login; it is not used by one single user.
Contact your Security Administrator to determine if this feature is enabled, if your
MM-AP login is CAM-managed, and whether you should use the rsecadm, rsysadm,
and rappadm RBAC roles to execute your tools.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009
,

xxx

Intended audience

This information product is designed for system administrators and other technical
personnel who perform operations, administration, and maintenance (OA&M) on the
elements of a CDMA 1X RNC wireless network.
How to use this information product

PRELIMINARY

About this information product

This information product contains the following parts, chapters, and appendices:
Part 1: System description

Part I: System description presents descriptive information, concepts, and principles

that are prerequisite to procedural information in later chapters.
Chapter 1, Safety and general information,

Chapter 1, Safety and general information provides a generic overview of the

standard hazard symbols and statements that are currently used in Alcatel-Lucent
documentation, and which may appear in this document.
Chapter 2, System architecture

Chapter 2, System Architecture describes the system architecture of the CDMA 1X

Radio Network Controller (RNC).
Chapter 3, Hardware architecture

Chapter 3, Hardware architecture describes the hardware components that comprise

the CDMA 1X RNC deployment.
Chapter 4, OA&M Architecture

Chapter 4, OA&M Architecture describes the OA&M architecture associated with the
CDMA 1X RNC.
Chapter 5, Maintenance states

Chapter 5, Maintenance states provides information concerning maintenance states

associated with the:

RNC-AP and OAM proxy AP

RNC related elements

Part 2: System administration

Part II: System administration covers tasks that are necessary to access RNC-related
system interfaces and maintain the integrity of the RNC.
Chapter 6, System management, methods, and procedures provides information
concerning:

Methods for accessing the various RNC-related interfaces.

The backup and restoration of RNC related configuration data and databases.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
xxxi
See notice on first page
Issue 14, September 2009
,

PRELIMINARY

Chapter 6, System management, methods, and procedures

PRELIMINARY

About this information product

Part 3: Fault management

Part III: Fault management provides the tasks in the International Telecommunications Union (ITU) standard that are associated with detecting, diagnosing, isolating and
recovering from fault conditions in the network.
Chapter 7, Monitoring the system

Chapter 7, Monitoring the system provides information that pertains to monitoring

the system elements such as the RNC-APs, OAM proxy AP, and TPUs.
Chapter 8, Troubleshooting

Chapter 8, Troubleshooting provides information on how to identify and resolve

RNC problems after initial installation.
Chapter 9, Replace components

Chapter 9, Replace components provides information that explains how to remove

and replace faulty RNC-related components when other attempts to restore the faulty
components have failed.
Part 4: Performance management

Part IV: Performance management provides the basic performance management

service measurement categories and processes associated with the 1X CDMA RNC.
Chapter 10, Service measurement

Chapter 10, Service measurement provides information pertinent to Service

Measurement of the CDMA 1X RNC.
Part 5: Configuration management

Part V: Configuration management provides the processes and procedures associated

with configuration management.
Chapter 11, Software configuration management

Chapter 11, Software configuration management provides information concerning

RC/V provisioning, FAF/QFAF control, software updates and generic retrofits
associated with the:

RNC-AP and OAM proxy AP

TPU

PRELIMINARY

Chapter 12, Configuring ATM connectivity in RNCs SHO universe

Chapter 12, Configuring ATM connectivity in RNCs SHO universe provides

descriptive and configuration information regarding the ATM connectivity for the
RNCs in a SHO universe.
Chapter 13, Automatic Protection Switching (APS)

Chapter 13, Automatic Protection Switching (APS) provides descriptive and

migration configuration information regarding the use of APS.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009
,

xxxii

Chapter 14, Configuring IPSHO connectivity

Chapter 14, Configuring IPSHO connectivity provides descriptive information

regarding IP connectivity for the RNCs in a SHO universe
Chapter 15, Growing/Degrowing TPU cards

Chapter 15, Growing/Degrowing TPU cards provides information concerning the

growth/degrowth of GICCs, CICCs, and B-PCFs in an existing TPU shelf.

PRELIMINARY

About this information product

Part 6: Security management

Part VI: Security management deals with intentional and unintentional threats to
network information coming from within the service providers organization, and also
from external sources.
Chapter 16, Managing security

Chapter 16, Managing security provides the security management guidelines

applicable for the CDMA 1X RNC.
Appendix A, Controls and indicators

Appendix A, Controls and indicators describes the controls and indicators on the
RNC cabinet and on each sub-system component.
Appendix B, Command Reference

Appendix B, Command Referencedescribes commands that are executed from the

UNIX shell prompt of a Mobility Manager Application Processor (MM-AP) to
administer MM-AP software.
Appendix C, Service measurement supplement

Appendix C, Service measurement supplement provides information relevant to the

SMxmldump tool, and to management of XML RNC PM data.
Appendix D, History of revision

Appendix D, History of revision provides information regarding the revision history

of 401-710-082.
Glossary

The Glossary defines technical terms and abbreviations that are used in this
information product.
Index

Conventions used

The following conventions are used throughout this information product:

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
xxxiii
See notice on first page
Issue 14, September 2009
,

PRELIMINARY

The Index identifies the location of information on specific topics in this information
product.

PRELIMINARY

About this information product

Typographic conventions

This information product presents different types of information in different typefaces

to emphasize the nature of the information:

Literal user input. Keystrokes that you are to enter character by character exactly
as shown in the text appear in monospace bold type. For example:
Enter the following command:
apappsconfig

Variable user input. Input values that vary from one execution or instance to
another appear in monospace bold italic type. For example:
cd directory

where
directory = the directory to which to change.

Literal system output. The names of files, directories, forms, messages, and other
information that a system outputs exactly as shown in the text appear in monospace
regular type. For example:
RST SPA=cnam REQUEST ACKNOWLEDGED

Variable system output. Values that vary from one instance to another in system
output appear in monospace italic type. For example:
RST SPA=SPA_NAME REQUEST COMPLETED

where
SPA_NAME = the name of the Service Package Application (SPA) that is successfully

restored.

The names of keys on a terminal keyboard are indicated by bold letters. For
example:
Press the F4 (Enter Query) function key.

The Ctrl (Control) key is signified by the carat ( ^ ) symbol. When the ^ symbol
precedes the name of another key (as in ^e), press the Crtl key and the other key
simultaneously.

Actions for user input

In this information product, the following words specify what action you should
perform to input data or execute commands:

The word enter means to key in the specified keystrokes (such as a command) and
then press the Enter or Return key. For example:
Enter the following command:

PRELIMINARY

apappconfig

The word press means to push down the specified key or keys on the keyboard.
For example:
Press the F4 (Enter Query) function key.

The word type means to key in the specified keystrokes (such as a value in the
field of a form) without pressing the Enter or Return key. For example:
In the IP address field, type the IP address of the host server.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009
,

xxxiv

Systems supported

This information product supports ECP Release 30.0 and later.

Related information products

The following information products are either referenced in this information product or
provide additional information that relates to the RNC:

PRELIMINARY

About this information product

Alcatel-Lucent CDMA Network information products:

These are categorized as follows:

401-610-036, Alcatel-Lucent CDMA Network Database Update Manual

401-610-055, Alcatel-Lucent CDMA Network Input Messages

401-610-057, Alcatel-Lucent CDMA Network Output Messages

401-610-135, Alcatel-Lucent CDMA Network Service Measurements

401-610-160, CDMA Network ECP Operations, Administration, and

Maintenance Guide

401-662-108, Alcatel-Lucent CDMA Network Operations and Management

Platform (OMP) Operations, Administration, and Maintenance Guide

401-380-835, Alcatel-Lucent CDMA Network Operations and Maintenance

Center - Radio Access Network - Operations, Administration, Maintenance, and
Provisioning
401-710-087, Alcatel-Lucent CDMA Networks Ethernet Packet Control Function
(E-PCF) Operation, Administration, and Maintenance Guide
401-710-201, Alcatel-Lucent 9290 Mobility Manager Application Processor
Cluster (MM-APC) Operations, Administration, and Maintenance (OA&M)
401-710-212, Alcatel-Lucent 9290 Mobility Manager OAM Proxy Operations,
Administration, and Maintenance

401-710-221, FMS/FWR Local Maintenance Terminal (LMT) Users Guide

Related training

Alcatel-Lucent offers the following training products that relate to OA&M of the ECP:

CL8000, Introduction to Executive Cellular Processor (ECP) Complex

Maintenance
CL8002, Executive Cellular Processor (ECP) Complex Maintenance

CL8005, 5ESS Digital Cellular Switch (DCS) Maintenance

The Online Customer Support (OLCS) web site, (http://support.lucent.com), provides

access to technical support, related documentation, related training, and feedback tools.
The site also provides account registration for new users.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
xxxv
See notice on first page
Issue 14, September 2009
,

PRELIMINARY

To obtain technical support, documentation, and training or submit feedback

PRELIMINARY

About this information product

Safety information

This information product contains hazard statements for your safety. Hazard statements
are given at points where safety consequences to personnel, equipment, and operation
may exist. Failure to follow these statements may result in serious consequences.
How to comment

PRELIMINARY

To comment on this information product, go to the Online Comment Form

(http://www.lucent-info.com/comments/enus/) or e-mail your comments to the
Comments Hotline ([email protected]).

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009
,

xxxvi

PRELIMINARY

Part I: System description

Overview
...................................................................................................................................................................................................................................
Purpose

This Part presents descriptive information, concepts, and principles that are prerequisite
to procedural information in later chapters.
Objectives

After reading the chapters in this Part, users should become familiar with:

the concept of the RNC and its role in providing the off-load of data traffic from
the 5ESS DCS.

the hardware and software architecture of the RNC.

the primary user interfaces used for OA&M activities on the RNC and the function
of each.

the maintenance states of the TPU and how they relate to the operation of the
RNC.

Contents
Chapter 1, Safety and general information

1-1

Chapter 2, System Architecture

2-1

Chapter 3, Hardware architecture

3-1

Chapter 4, OA&M Architecture

4-1

Chapter 5, Maintenance states

5-1

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
I-1
Issue 14, September 2009
See notice on first page

PRELIMINARY

1S afety and general information

PRELIMINARY

This chapter provides information on hazards, which may arise in the course of your
work.
Contents
Hazard statements

1-2

Structure of hazard statements

1-3

General hazard statements

1-5

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
1-1
Issue 14, September 2009
See notice on first page

PRELIMINARY

Safety and general information

Hazard statements
Overview
...................................................................................................................................................................................................................................
Purpose

This section provides information on the structure of hazard statements as well as

general and specific hazards, which may arise in the course of your work.

PRELIMINARY

Contents
Structure of hazard statements

1-3

General hazard statements

1-5

1-2

Structure
of hazard statements
...................................................................................................................................................................................................................................
Overview

Hazard statements describe the safety risks relevant while performing tasks on
Alcatel-Lucent products during deployment and/or use. Failure to avoid the hazards
may have serious consequences.

PRELIMINARY

Safety and general information

General structure

Hazard statements include the following structural elements:

Item

Structure element

Purpose

Personal-injury symbol

Indicates the potential for personal injury

(optional)

Hazard-type symbol

Indicates hazard type (optional)

Signal word

Indicates the severity of the hazard

Hazard type

Describes the source of the risk of damage or

injury

Damage statement

Consequences if protective measures fail

Avoidance message

Protective measures to take to avoid the hazard

Identifier

The reference ID of the hazard statement

(optional)

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
1-3
Issue 14, September 2009
See notice on first page

PRELIMINARY

Safety and general information

Structure of hazard statements

Signal words

The signal words identify the hazard severity levels as follows:

Signal word

Meaning

DANGER

Indicates an imminently hazardous situation (high risk) which, if

not avoided, will result in death or serious injury.

WARNING

Indicates a potentially hazardous situation (medium risk) which,

if not avoided, could result in death or serious injury.

CAUTION

When used with the personal injury symbol:

Indicates a potentially hazardous situation (low risk) which, if
not avoided, may result in personal injury.
When used without the personal injury symbol:

PRELIMINARY

Indicates a potentially hazardous situation (low risk) which, if

not avoided, may result in property damage, such as service
interruption or damage to equipment or other materials.

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

1-4

General
hazard statements
...................................................................................................................................................................................................................................
Purpose

Provides information on general hazard statements that may arise in the course of your
work, but are not necessarily related to a specific procedure.

PRELIMINARY

Safety and general information

DANGER
Electric-shock hazard
This equipment generates high leakage current. This can lead to high voltages with
respect to ground for accessible parts of the installation. Contact with these parts can
cause serious health effects, possibly including death, even hours after the event.
This equipment is only suited for permanent connection. Before connecting the power
supply, establish a grounding connection.

WARNING
Electric-shock hazard
Contact with energized parts can cause serious injury.
At least one other trained person must be in attendance, who can immediately and
safely disconnect the system if necessary.
This second person must be trained in first aid for emergency purposes.

WARNING
Electric-shock hazard
There is a danger of electric shock if the grounding system is inadequate.
You must comply with the grounding requirements for the grounding system.

WARNING
Electric-shock hazard
Contact with energized parts can cause serious injury.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
1-5
Issue 14, September 2009
See notice on first page

PRELIMINARY

Work on energized equipment is only permitted if you are using insulated connection
terminals, are adequately trained and follow safe work practices.

PRELIMINARY

Safety and general information

General hazard statements

WARNING
Electric-shock hazard
Contact with energized parts can cause serious personal injury.
Seal off the installation area (warning tape, signs) to prevent untrained or
unauthorized persons from entering.
Follow safe work practices and lockout/tagout procedures.

WARNING
Electric-shock hazard
Some parts of all electrical installations are energized. Failure to follow safe work
practices and the safety warnings may lead to bodily injury and property damage.
For this reason, only trained and qualified personnel (electrical workers as defined in
IEC 60215 or EN 60215 + A1 or in the National Electrical Code or in ANSI/NFPA
No. 10) may install or service the installation.

WARNING
Laser hazard
The light from laser and high-radiance LEDs may cause eye damage if absorbed by
the retina.
In the US consult ANSI Z136.2, in Europe consult IEC-60825 Safety of laser products,
for guidance on the safe use of optical fiber communication systems in the workplace.

WARNING
Falling-object hazard
Cabinet may tip when it is moved if an obstacle or a downward step is encountered.
Do not use dolly wheels if the installation location has an uneven surface, steps etc.

PRELIMINARY

WARNING
Overhead-load hazard
Cabinet eyebolts can break, severely damaging the cabinet, if a crane is used to lift the
cabinet into an upright position.
Ensure that the cabinet is in an upright position before transportation by crane.
....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

1-6

General hazard statements

WARNING
Inhalation hazard
Inhalation of asbestos fibers can result in serious illness or death.
Buildings constructed before 1980 MAY contain asbestos. Buildings constructed before
1970 OFTEN contain asbestos. Potential exposure could occur during routing of cable
or wires, removing cables, removing transite or asbestos cement boards, drilling
wallboard, transite panels, or floor tiles, removing sprayed-on fireproofing, moving or
removing ceiling tiles, installing cable hangers.

PRELIMINARY

Safety and general information

Do not disturb asbestos. If asbestos is present, ensure potential expose is controlled by

adhering to local asbestos management regulations and follow safe work practices.

CAUTION
Service-disruption hazard
Condensation can occur in the network element during transport, especially on moving
from outside to closed rooms. Condensation can cause malfunctioning of the circuit
packs.
Ensure that circuit packs and shelves have reached room temperature and are dry
before taking them into operation.

CAUTION
Service-disruption hazard
Tools left in the work area can cause short circuits during operation which can lead to
the destruction of units.
Make sure after finishing your work that no tools, testing equipment, flashlights, etc.,
have been left in or on the equipment.

CAUTION
Lifting hazard
Lifting this equipment by yourself can result in injury due to the size and weight of the
equipment.

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
1-7
Issue 14, September 2009
See notice on first page

PRELIMINARY

Always use three people or a lifting device to transport and position this equipment.

PRELIMINARY

Safety and general information

General hazard statements

CAUTION
Flammable-material hazard
The heat vent (grill) at the top of the cabinet can become obstructed, preventing
ventilation of the cabinet.
Make sure that the airvent is not obstructed and remains clear at all times.

CAUTION
ESD hazard
Semiconductor components can be damaged by static discharges.
The following rules must be followed when handling any module containing
semiconductor components:

PRELIMINARY

Wear conductive or antistatic working clothes (for example, a coat made of 100%
cotton).
Wear the grounded wrist strap.

Wear shoes with conductive soles on a conductive floor surface or conductive work
mat.

Leave the modules in their original packaging until ready for use.

Make sure there is no difference in potential between yourself, the workplace, and
the packaging before removing, unpacking, or packing a module.

Hold the module only by the grip without touching the connection pins, tracks, or
components.

Place modules removed from the equipment on a conductive surface.

Test or handle the module only with grounded tools on grounded equipment.

Handle defective modules exactly like new ones to avoid causing further damage.

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

1-8

PRELIMINARY

2S ystem Architecture

This chapter describes the CDMA 1X Radio Network Controller (CDMA 1X RNC) by
explaining evolution of the system, the architecture of the CDMA 1X RNC and the
architecture of the E-PCF and B-PCF.
Contents
2-2

Network functional architecture

2-8

Support for 2G and circuit data

2-12

Support for multiple RNCs

2-13

RNC alternate routing

2-14

IP backhaul

2-16

IP-based soft handoff

2-17

CDMA 1X RNC hardware architecture overview

2-20

CDMA 1X RNC software architecture

2-24

OA&M software components and interfaces

2-26

Call processing software components and interfaces

2-29

User bearer processing software components and interfaces

2-32

Physical Network Connectivity

2-35

B-PCF Architecture

2-37

CDMA 1X RNC high-level call control signaling

2-42

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
2-1
Issue 14, September 2009
See notice on first page

PRELIMINARY

CDMA 1X RNC evolution

PRELIMINARY

System Architecture

CDMA
1X RNC evolution
...................................................................................................................................................................................................................................
Introduction

The CDMA 1X RNC product is designed to provide the smooth evolution path(s) for
wireless legacy systems to a future all Internet Protocol (IP) network architecture.
Basic infrastructure

The CDMA 1X RNC product provides the basic infrastructure necessary to process
mobile-to-network data calls over a CDMA IP-based network.
CDMA packet-mode data services are bidirectional, and apply to both cellular and
PCS.
Existing 3G1X network architecture

Figure 2-1, Existing 3G 1X network architecture (p. 2-2) provides a view of the
existing 3G1X network architecture. Without the CDMA 1X RNC, the 5ESS DCS
serves for both voice and data bearer processing.

PRELIMINARY

Figure 2-1 Existing 3G 1X network architecture

2-2

CDMA 1X RNC evolution

Voice and data bearer traffic

In this current technological environment:

Voice bearer traffic from mobile devices is processed (that is, frame selection and
vocoding are performed), and are sent to the PSTN.

Data bearer traffic from mobile devices is processed (that is, data frame selection
and RLP control are performed), and are sent to the Packet Data Network (PDN).

PRELIMINARY

System Architecture

With this mature technology, however, some major limitations still exist for 3G1X
Packet data applications:

Data transaction delay limitation

Data throughput limitation

Resource contention limitation

Data transaction delay limitation

Packet data call setup and reactivation delay in current systems is generally in the
range of 3 to 5 seconds, because the majority of call processing procedures are
performed serially.
Data throughput limitation

The data throughput at the L interface is limited (that is, up to 6 Mbps in each
direction).
Resource contention limitation

There are always potential resource contention issues between voice services and data
services within the current network.
CDMA 1X RNC network architecture

To address the aforementioned limitations in existing systems, and provide a smooth

path for system evolution towards a 3GPP2 All-IP architecture, the CDMA 1X RNC
Network architecture is being introduced. The first phase in its evolution addresses
3G1X packet data applications.
Figure 2-2, CDMA 1X RNC architecture for data off-load (p. 2-4) shows the CDMA
1X RNC architecture for 3G1X packet data offload applications.

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
2-3
Issue 14, September 2009
See notice on first page

PRELIMINARY

System Architecture

CDMA 1X RNC evolution

Figure 2-2 CDMA 1X RNC architecture for data off-load

Packet data off-load

The CDMA2000 1X RNC supports 3G1X packet data offload applications. The
inclusion of the RNC into an existing network provides an all-IP based bearer
processing platform, and also provides the initial step towards the 3GPP2 All-IP
network.

PRELIMINARY

Specifically, the RNC:

Allows the 5ESS DCS to more efficiently utilize its resources for circuit voice
services by supporting 3G1X packet data off-load from the 5ESS DCS.

Provides service providers with two PCF options (Figure 2-3, E-PCF and B-PCF
options (p. 2-5) and Table 2-1, E-PCF/B-PCF comparison (p. 2-5)) for use in
their networks:

New Blade PCFs (B-PCFs) can be implemented inside the RNC TPU shelf.

2-4

CDMA 1X RNC evolution

Figure 2-3 E-PCF and B-PCF options

PRELIMINARY

System Architecture

Relieves the CDN load and the DLN load for 3G1X packet data call
processing, thereby improving overall MSC messaging capacity.
Provides future investment protection for IMS features since CDMA 1X RNC
will be the future IP bearer processing platform in the All-IP Radio Access
Network (RAN).

Table 2-1
Category
Security

E-PCF/B-PCF comparison
B-PCF

Separate network element. Direct

OA&M interface.

Integrated into the RNC.

Interfaces are hidden behind the
GICC and OA&M Proxy AP. No
direct connectivity to external
monitoring systems.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
2-5
Issue 14, September 2009
See notice on first page

PRELIMINARY

E-PCF

PRELIMINARY

System Architecture

CDMA 1X RNC evolution

Table 2-1

E-PCF/B-PCF comparison (continued)

Category
Tunables

E-PCF

B-PCF

prov_tunas is used to provision

static and dynamic tunables.

Stored in RNC DB; Configured

via TPU-GUI (Dynamic and
some Static and PDSN pool).

PDSN Pool File is provisioned

from EMS.

Lucent will preset static tunables

that are not on the TPU-GUI.

Dynamic Tunables File.

Common data is shared across

B-PCFs.
Alarm/Event
Output
Messages

SNMP Traps on OA&M LAN

ROP

(sent to EMS or third party

monitoring system).

(Output messages are

documented in Lucent
401-610-057

Status Displays

EMS

SDP RNC summary indicator

provides cumulative indication
for all RNC related alarms
including B-PCF.
TPU-GUI provides B-PCF alarm
and status details

Log Files

E-PCF admin log

Stored on the RNC-AP in the

rncadmin.log (messages are in
ROP format).

Service
Measurements

Can be polled via the E-PCF

MIB. OMP/OMC RAN retrieves
XML files hourly.

Hourly measurements stored in

the RNC SM XML file retrieved
by the OMP/OMC RAN every
hour. TPU-GUI performance
statistics page provides
user-friendly access.

States

IS/OOS

Operational: Enabled/Disabled
Administrative: Locked/
Unlocked/Shutting Down
Usage: Idle/Active/Busy

PRELIMINARY

Maintenance
Commands

Remove

Lock

Restore

Unlock

Inhibit Call Processing

Shutdown

Allow Call Processing

ResetHalt (halt the B-PCF disk

Init

2-6

CDMA 1X RNC evolution

Handoff types

The supported handoff type is:

Soft/Semi-soft handoff between the RNC and DCS, which is achieved via the
existing Soft handoff (SHO) ATM network.

Operations, Administration & Maintenance (OA&M)

PRELIMINARY

System Architecture

In addition to the existing OA&M interfaces, new mechanisms supporting fault and
configuration management capabilities related to call processing and traffic processing
elements of an CDMA 1X RNC are provided.
Performance Measurement (PM)

Performance (service) measurement for RNC is provided by the use of XML-based

RNC PM counts and CDN Service Measurement (SM) counts.
For specific information regarding these counts, and their collection refer to Chapter
10, Service measurement.
RC/V RNC data translation

Some configuration information that is needed by the CDMA 1X RNC is provisioned

at the ECPC.
Because the provisioning mechanism in the ECPC is reused for the CDMA 1X RNC,
the data stored in the ECPC is translated into an acceptable format required by the
software in the CDMA 1X RNC. Additionally, a trigger mechanism ensures that
updates initiated in RC/V are propagated to the CDMA 1X RNC.
Dynamic CDMA 1X RNC configuration

To prevent end user outages that result from changes to the configuration, an
appropriate set of CDMA 1X RNC configuration parameters have been given the
ability to be changed without affecting active calls. As a result, the CDMA 1X RNC
supports a data configuration download and activation procedure similar to that
currently used for the RCS-AP.
Applicable mobile types

Mobiles designed to support cdma2000 are also supported. The data features that are
provided by the system require 3G-1X data capable mobiles.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
2-7
Issue 14, September 2009
See notice on first page

PRELIMINARY

The current CDMA 1X RNC system supports both IS-95A/B conformance mobiles and
CDMA 2000 Release A/B conformance mobiles in the cellular bands (800MHz) and
the PCS bands (1900 MHz).

PRELIMINARY

System Architecture

Network
functional architecture
...................................................................................................................................................................................................................................
Introduction

For CDMA 1X RNC, the existing MSC adds the Radio Network Controller (RNC).
Overall structure

Figure 2-4, High-level CDMA 1X RNC network functional architecture (p. 2-8)
shows the overall structure of the CDMA 1X RNC network functional architecture.
Figure 2-4 High-level CDMA 1X RNC network functional architecture

PRELIMINARY

The system architecture provides four separate IP networks as follows:

One for A8/A9

One for A10/A11

One for backhaul

One for IPSHO

2-8

Network functional architecture

For deployment, the A8/A9, A10/A11, and the IP SHO networks are a single IP
network. The backhaul network is a separate IP network. Both circuit voice and circuit
data are processed through the DCS.
Figure 2-4, High-level CDMA 1X RNC network functional architecture (p. 2-8)
shows that there are BTSs connected to both the RNC, and to the PSU through the
backhaul network.

PRELIMINARY

System Architecture

The RNCs have a TPU for the bearer connection, a Traffic Control Server (TCS) on
the RNC-AP for control of the frame selectors, and a RNC-M on the RNC-AP to
provide the OAM control of the TPU.
The Packet Control Function on a Netra (E-PCF) or FMS Blade (B-PCF) manages the
packets between the RNC and the PDSN.
RNC components

An RNC requires an MM-AP cabinet (to house the RNC-AP), and an RNC cabinet.
MM-AP cabinet

In the MM-AP cabinet, the RNC-AP hosts two major application processes, the Traffic
Control Server (TCS) Process that manages user bearer resources on the TPU shelves
(for example, FS and RLP) and the RNC-Manager Process that provides the OA&M
functions for the TPU.
RNC cabinet

In the RNC cabinet, TPU shelves provide user bearer processing functions, and
terminate all External I/O interfaces.
Logical RNC functions

Figure 2-5, Logical RNC functions (p. 2-10) shows an RNC in the existing MSC.
architecture.

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
2-9
Issue 14, September 2009
See notice on first page

PRELIMINARY

System Architecture

Network functional architecture

Figure 2-5 Logical RNC functions

The Traffic Control Server (TCS) process provides the interface into the RNC for the
RCS/RCC and selects a Frame Selector Resource Manager (FSRM) on a particular
traffic processor (CICC) to allocate the FS/RLP. The TP connects to the BTS, other
RNCs, and PSUs for the bearer path. The RNC-M is the OAM manager of the TP. The
RNC also contains gateway functions for the BTS, to other RNCs, and to the PSU.
Voice and data calls

Voice calls get frame selection and vocoding on the DCS. For data calls, FS/RLP is
provided on either the DCS, or the RNC.
Packet control function

The DCS and RNC both have their own Packet Control Function (PCF) resources. The
RNC can access a stand-alone PCF (Netra) via the packet A8/A9 interface.The DCS
can access a stand-alone PCF via the T1 based L-interface or via a packet A8/A9
interface from the PHE2.
Note that the DCS also supports a PCF on a PHE2, with access to the PDN via the
packet A10/A11 to the PDSN.

PRELIMINARY

The interfaces to the packet network are not affected by the RNC.
Ethernet/IP topology

Figure 2-6, Ethernet/IP topology (p. 2-11) show a very general view of the network
topology of the RNC.

2-10

Network functional architecture

Figure 2-6 Ethernet/IP topology

PRELIMINARY

System Architecture

Figure 2-6, Ethernet/IP topology (p. 2-11) shows that there are several different
networks to which the RNC interconnects:

Each Application Processor (AP) has access to the dual rail LAN, which
interconnects the APs.

There is a link from each AP to the ring in the ECPC to provide a reliable control
path from the AP to the legacy MSC elements.
The RNC TPU has an internal IP network to interconnect the TPU shelves.

The RNC-AP and the RNC-TPU have an internal IP network for control signaling.

The gateway cards interconnect the transport network used to interconnect the
bearer from the legacy elements.

The gateway card (BTS gateway) interconnects the backhaul network used to
connect the BTS to the RNC.

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
2-11
Issue 14, September 2009
See notice on first page

PRELIMINARY

System Architecture

Support
for 2G and circuit data
...................................................................................................................................................................................................................................
Introduction

During the migration phase of packet data functions from the DCS to the RNC, packet
data service can be provided from both the DCS and the RNC. This allows for
seamless integration of the RNC into the existing network without interrupting service
to the end user.
CDMA packet mode data

The CDMA packet mode data services feature provides a subscriber with the ability to
transmit bursts of data over a packet data network via the CDMA air interface. It
provides the infrastructure for mobile users with laptop computers or other data devices
conforming to the TIA/EIA/IS-707 standard to access various data applications, such as
E-mail, file transfer, field service automation, and fleet dispatch.

PRELIMINARY

These applications may reside on existing or custom designed data networks.

2-12

Support
for multiple RNCs
...................................................................................................................................................................................................................................
Introduction

Support of multiple RNCs on an ECPC/DCS system allows a service provider to grow

and manage RNCs to meet the demands of data and voice services. The number of
RNCs in an MSC can grow up to fifteen.

PRELIMINARY

System Architecture

RNC interconnection

The RNCs are seamlessly integrated into the wireless network to provide functions
such as resource pooling between RNCs, and soft handoff. RNCs in the same MSC
talk to each other via an IP network.
Interconnecting RNCs via this network allow for ease in provisioning and configuring
the interconnection between networks. This is also a step towards migration to an IP
based soft handoff universe.
RNC/DCS interface

Communication between the DCS and the RNC is based on the existing ATM AAL5
interface to DCS. RNCs in different MSCs will communicate with each other via this
ATM AAL5 interface as well.
The RNC is connected seamlessly to this existing ATM network, which is used to
provide soft handoff support.

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
2-13
Issue 14, September 2009
See notice on first page

PRELIMINARY

System Architecture

RNC
alternate routing
...................................................................................................................................................................................................................................
Introduction

RNC alternate routing provides a method for increasing RNC redundancy, beyond the
redundancy built into each RNC itself.
Pooling RNCs

RNC alternate routing works by placing all existing RNCs into a pool. Any RNC
within the pool can automatically and seamlessly take over the total work of any other
RNC, if the other RNC should become unavailable.
Default RNC

Packet data call setup messages are sent directly from each cell to the RNC that is
preprovisioned to serve that cell. The RNC preprovisioned to serve a cell is identified
as the default RNC.
If failure occurs

If a default RNC fails, the Administrative Call Processing and Database Node (ACDN)
automatically selects an alternate RNC as the new (temporary) destination for routing
the messages.
The ACDN chooses the alternate RNC based on which RNC has the highest value of
FS QFAF quota allocated to that RNC. The selected RNC will add the FS QFAF and
CICC QFAF quotas of the failed RNC to its own, in order to properly handle the
combined traffic from the failed RNC as well as its own.
Transparent rerouting

The re-routing is transparent to the cell and other network elements, and requires no
human intervention. The software does the re-routing automatically.
Assignment of alternate RNCs

PRELIMINARY

Alternate RNC is triggered automatically and immediately by the ACDN when a

sufficient failure is experienced by a GICC, CICC or PCF.
For a TCS duplex failure, the ACDN will wait 30 seconds before selecting an alternate
RNC. When a TCS duplex failure occurs the ACDN is not able to receive the RNC
status, therefore, the ACDN will wait to make sure the TCSs are actually out of service
before assigning an alternate RNC.

2-14

RNC alternate routing

Call dispostion during transistion

Calls that exist at an RNC that goes OOS will be successfully completed immediately.
That is because PCFs associated with RNCs are notified of the alternate RNC that is
picked by the ACDN.
Network reactivation

PRELIMINARY

System Architecture

If an RNC failure is due to a A8/A9 and A10/11 GICC failure, the PDSN will no
longer be able to reach the B-PCFs on the failed RNC since the bearer traffic
(A10/A11) has to go through the GICC to reach the B-PCFs. As such, network
reactivation calls involving the B-PCFs will not be successful until a mobile
reactivation occurs first which forces a new PCF to be selected.
Duration of outage

The interval during which an RNC is in alternate routing mode is the duration of the
RNC outage, which can be planned or unplanned. Once the OOS RNC recovers, the
RNC pool will revert to the normal state of operation, which is accomplished via an
inherent software mechanism, requiring no human intervention.
Feature activation

Refer to the Planning and Implementation guide (401-710-081) for detailed feature
activation information pertaining to RNC alternate routing.

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
2-15
Issue 14, September 2009
See notice on first page

PRELIMINARY
PRELIMINARY

System Architecture

IP
backhaul
...................................................................................................................................................................................................................................
Reference

For information pertaining to IP backhaul refer to 401-710-090, CDMA Backhaul

Networks.

2-16

IP-based
soft handoff
...................................................................................................................................................................................................................................
Introduction

IP-based soft handoff provides IP-based connectivity between the RNC, and PSU/DCS
in place of ATM.

PRELIMINARY

System Architecture

Advantages of IP

Using IP as the transport mechanism provides:

Simpler maintainability of the IP network as opposed to the ATM network.

Simpler engineering due to the reduction of the number of physical interfaces (one
GIGE interface gives the same throughput as two or more OC3 interfaces).

The possibility of sharing networking equipment with IP backhaul.

IPSHO overlay network

Figure 2-7, IPSHO network with ATM SHO network (p. 2-17) gives a view of the
IP-based SHO network as a network overlaying the existing ATM SHO network. This
Figure depicts one RNC with gateways towards both the ATM and IP SHO networks
(PSU GW and IPSHO GW respectively), and one PSU with only an ATM interface,
and another PSU with only an IP interface.
Figure 2-7 IPSHO network with ATM SHO network

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
2-17
Issue 14, September 2009
See notice on first page

PRELIMINARY

System Architecture

IP-based soft handoff

Generic configuration

This is a generic configuration, with both IPSHO-enabled and non-IPSHO-enabled

PSUs co-existing. Once all the RNC/PSUs complete the transition to IP, the ATMSHO
network will not be required.
Call processing

For a given call, two cells pick up two call legs of the same call, for which the Frame
Selector (FS) resource is within a CICC card in the RNC, and the call leg packets are
routed to the same FS over a different SHO network.
In the forward direction, the Frame Distributor function sends the packet for different
call legs through different SHO gateways, and different SHO networks.
Note that the RNC may have directly homed IPBTS cells, but for this cell, the call leg
need not traverse through the SHO network to reach the FS.
IPSHO simplified architecture

Figure 2-8, IPSHO network configuration (p. 2-18) provides a simplified view of the
IP soft handoff network architecture. Note that this is a typical view, annd actual
deployment will be based on the Service Providers network plan.

PRELIMINARY

Figure 2-8 IPSHO network configuration

On each IPSHO-enabled RNC or PSU, an IPSHO gateway is implemented on a pair of

interface cards with Gigabit Ethernet interface.

2-18

IP-based soft handoff

The ethernet interfaces are terminated on a router or a Multi-Layer Switch (MLS)

through which the PSU/RNC is connected to the Wide-Area Network (WAN) of the
IP-based soft handoff universe.
Typically, all the RNCs and PSUs within one MSC are connected using a Local Area
Network (LAN). Inter-MSC SHO traffic is exchanged over the WAN.

PRELIMINARY

System Architecture

Limitations and considerations

In the current architecture, each RNC can provide only one IPSHO GW. This also
means that not more than two pair of BHS GICCs can be equipped in the RNC.
Additionally, even after all the Community Addresses(CAs) are transitioned to IP, the
SC-GICC will still be responsible for running the A8/A9 and A10/A11 services.

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
2-19
Issue 14, September 2009
See notice on first page

PRELIMINARY

System Architecture

CDMA
1X RNC hardware architecture overview
...................................................................................................................................................................................................................................
Introduction

The information in this section provides a high-level overview of the CDMA 1X RNC
hardware architecture. More detailed information concerning the CDMA 1X RNC
hardware can be found in Chapter 3, Hardware architecture.
Cabinet hardware

To implement CDMA 1X RNC, two cabinet types (Figure 2-9, RNC related cabinet
types (high-level view) (p. 2-20) and Table 2-2, Cabinet hardware specifics
(p. 2-20)) are required, an MM-AP cabinet and an RNC cabinet. .
Figure 2-9 RNC related cabinet types (high-level view)

Table 2-2

Cabinet hardware specifics

MM-AP Cabinet

PRELIMINARY

ANSI cabinet: 762MM(W) X 4584MM

(D)X 1830mm (H)

RNC Cabinet
Universal cabinet (2310): 600mm (W)X
600mm (D)X 1830mm (H)

2-20

CDMA 1X RNC hardware architecture overview

Table 2-2

Cabinet hardware specifics (continued)

MM-AP Cabinet

RNC-APs
(400s or
410s
servers)

OAM Proxy
AP (400s or
410s
servers)

can co-exist within the

existing MM-AP cabinet

RNC Cabinet
2 TPU
shelves

4 Alarm Cards

uses existing MM
platform

4 ESCs

2 per RNC
(active/standby)

Up to 8 GICCs (deployed in
non-redundant pairs in
Release 24.0) for:

- RNC I/O functions

- application gateway and

services

RNC-M Process: OA&M

functions

Up to 20 or 28 (assumes no
Blade PCFS) CICCs
(deployed in N+K
redundancy) for FS/RLP
functions

TCS Process: TPU

Resource Management
and Admission control

Up to 8 Blade PCFs
(deployed in N+K
redundancy)

supports the TPU-GUI

web server and the
RNC-DB

PRELIMINARY

System Architecture

One Terminal Server for remote console

access

2 per MSC
(active/standby)

MM-AP cabinet

The MM-AP cabinet that is used can be either:

An existing R1 (model 2205) growth frame/cabinet. The R1 growth frame/cabinet

can be used to house 400S type servers or 410S type servers that function as an
OAM Proxy AP, and as RNC-AP(s).

An existing or additional R1SR (model 2215) growth frame/cabinet. The R1SR

growth frame/cabinet can be used to house 410S type servers that function as an
OAM Proxy AP, and as RNC-AP(s).

For the first CDMA 1X RNC deployed in an MSC, one pair of 400s or 410s servers
are required to function as an OAM Proxy AP.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
2-21
Issue 14, September 2009
See notice on first page

PRELIMINARY

OAM Proxy AP

PRELIMINARY

System Architecture

CDMA 1X RNC hardware architecture overview

There are currently two CDMA 1X RNC applications running on the OAM Proxy APs:

TPU-GUI
RNC Database (DB)

RNC-AP pairs

One pair of 400s or 410s servers are required to function as an RNC-AP for each
CDMA 1X RNC.
There are currently two CDMA 1X RNC applications running on the RNC-APs:

Traffic Control Server Service

RNC-Manager Service

Both TCS and RNC-M are RCC VCVMs and both use the virtual IP services.
RNC cabinet

The RNC integrated cabinet (model 2310) provides:

Two PICMG 2.16 cPSB shelves, which provide the CDMA 1X RNC Traffic
Processing Unit (TPU) functions.

A terminal server.

The cPSB shelves are commonly identified by their application name as the TPU
shelves.
TPU shelf

There are two TPU shelves in an RNC cabinet, and each TPU shelf has 21 slots
arranged as follows:

One slot for alarm cards

Two slots for Ethernet switch cards (ESC)

Eighteen slots for application cards or blades which are identified as follows:

Gateway Intelligent Carrier Cards (GICCs)

Common Intelligent Carrier Cards (CICCs)

Blade Packet Control Function (B-PCF) blades

Alarm cards

The alarm cards provide low-level management functions for the cPSB shelf.

PRELIMINARY

Ethernet switch cards

The ESCs provide a dual-star redundant Gigabit Ethernet Fabric at the cPSB
backplane, and also provide four uplink GIGE ports at the front panel.

2-22

CDMA 1X RNC hardware architecture overview

GICCs

The GICC cards provide CDMA 1X RNC broadband I/O functions to/from the:

ATM soft handoff (SHO) universe

A8/A9 network

A10/A11 network

IP SHO universe (future).

IP BTS

PRELIMINARY

System Architecture

The GICCs also provide bearer packet security filtering according to CDMA 1X RNC
application-defined rules. GICCs are based on C-5 network processor (NP) technology.
CICCs

The CICCs (not shown in Figure 2-9, RNC related cabinet types (high-level view)
(p. 2-20)) provide data frame selection functions, packet data radio link protocol (RLP)
functions, and A8/A9 functions for 3G1X packet data service. The CICCs have three
embedded Power PC (PPC) processors.
B-PCF blades

The B-PCFs housed inside the CDMA 1X RNC integrated cabinet provide the same
functions performed by the E-PCFs. The B-PCF is based on a Solaris blade. For
further information on B-PCFs, see B-PCF Architecture (p. 2-37).
Terminal server

The terminal server provides an alternative method for access to the serial interfaces of
each TPU board via an ethernet interface. This alternative method is highly intrusive
and can result in system faults, if used improperly.

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
2-23
Issue 14, September 2009
See notice on first page

PRELIMINARY

System Architecture

CDMA
1X RNC software architecture
...................................................................................................................................................................................................................................
Introduction

The 1X RNC software architecture is supported by the hardware structure that

encompasses the OA&M components, the call signaling components, and the user
bearer processing components.
Hardware structure

The various components that comprise the hardware structure of the 1X RNC software
architecture (Figure 2-10, CDMA 1X RNC Software Architecture (p. 2-24)) are listed
as follows:

PRELIMINARY

Figure 2-10 CDMA 1X RNC Software Architecture

Proxy-AP: The OAM Proxy AP hosts the TPU-GUI VCVM and the FDBMS
process.
RNC-AP: The RNC-AP hosts the RNC-M VCVM and the TCS VCVM.

2-24

CDMA 1X RNC software architecture

SC-GICC: The SC-GICC is the pair of GICC cards in both TPU shelves that host
the Shelf Controller Functions. In addition, it can also host 5EGW services and the
A8/A9GW and A10/A11GW services.

5EGW-GICC: The 5EGW-GICC cards used in both TPU shelves that host the ATM
services connected to the ATM SHO Universe. On each 5EGW-GICC card, there
exists up to two 5EGW services.

IPSHO-GICC- The IPSHO-GICC cards are the pair of GICC cards that host only
the IP SHO related features. The pair of IPSHO-GICC cards provide IPSHO
GW/IPAM virtual service.

IPBTS-GICC: The pair(s) of GICC cards that host only the IP services related to
the IPBH architecture. On each pair of IPBTS-GICC cards, there exists IPBTS GW
virtual service and Backhaul Controller virtual Service. See also, IP Backhaul for
CDMA Voice and Packet Data guide (401-710-090) for additional information.

B-PCF: The B-PCF includes the PCF call processing functions and the PCF traffic
processing functions.

CICC: The CICC is the Common ICC card in both TPU shelves that hosts the
FSRM entity for local call control functions and application bearer processing
functions, such as FS/RLP processing and GRE processing.

PRELIMINARY

System Architecture

Important! Note that a pair of GICC cards (that is, non-SC GICC cards) can act as
ATM-GICC cards, IPBTS-GICC cards or IPSHO-GICC, but not at the same time.

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
2-25
Issue 14, September 2009
See notice on first page

PRELIMINARY

System Architecture

OA&M
software components and interfaces
...................................................................................................................................................................................................................................
Introduction

The OA&M software components and interfaces of the 1X RNC provide the various
functions that enable the system, and system users to maintain the integrity of 1X RNC
operation.
Components

The CDMA 1X RNC OA&M software components are listed as follows:

RNC-M: The RNC-Manager provides major OA&M functionality for 1X RNC,

including RNC fault management, Configuration Management, Performance
Management and interfacing with the MSC legacy OA&M subsystems (that is,
RCV, ROP and SDP) through MM midware. RNC-M is a VCVM residing on the
pair of RNC-APs, which coexists with the TCS VCVM.

TPU-GUI: The TPU-GUI VCVM on the OAM Proxy APs provides Web Server
functions to the TPU-GUI client applications residing on the OMP/OMC-RAN
terminals. TPU-GUI is used to provision TPU shelves and application node cards
on the shelves in the 1X RNC Integrated Frame, as well as monitoring faults and
events from the TPU shelves and application node cards on the shelves. By
residing on the OAM Proxy AP pair, the TPU-GUI VCVM also provides Security
Management for accessing the RNC-APs for provisioning and monitoring of the 1X
RNC.

FDBMS: The Flexent Data Base Management System provides RNC DB access
management and RNC DB persistent services. FDBMS is active on both Proxy-APs
so that it can keep RNC DB in synch on Both Proxy-APs.

Shelf Controller: The Shelf Controller a Virtual IP Service on the SC-GICC pair. It
uses the Virtual Service Redundancy Protocol (VSRP) to provide an
active/hot-standby operation mode. It provides cPSB shelf configuration
management, including application software provisioning in each Blade and Blade
initialization support. Active/Standby Shelf Controllers only reside on the first pair
of GICC cards in a 1X RNC cabinet.

Interfaces

PRELIMINARY

Figure 2-11, CDMA 1X RNC OA&M Interfaces (p. 2-27) summarizes the major
OA&M Interface architecture of a 1X RNC.

2-26

OA&M software components and interfaces

Figure 2-11 CDMA 1X RNC OA&M Interfaces

PRELIMINARY

System Architecture

The RNC-Manager is the main OAM functional entity in the entire 1X RNC. The
RNC-M has the following interfaces:

RNC-M <=>TPU shelves: This interface provides CDMA 1X RNC hardware and
software provisioning and management functions in the CDMA 1X RNC integrated
frame.

RNC-M <=> TCS: This interface provides provisioning and management functions
needed in the TCS for RNC call processing.

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
2-27
Issue 14, September 2009
See notice on first page

PRELIMINARY

System Architecture

OA&M software components and interfaces

RNC-M <=> OAM-AP: This interface provides 1X RNC system level provisioning
and fault management capabilities integrated into the legacy MSC OA&M
subsystems. OAM APs are B-servers located in an MM-AP base frame.

RNC-M <=> Proxy-AP: This interface provides TPU related provisioning and fault
management functions through the TPU-GUI. TPU-GUI and RNC-DB are located
on the OAM Proxy AP Pair. TPU-GUI VCVM provides the web sever functions for
the TPU-GUI client on the OMP/OMC-RAN terminals. The detailed TPU
provisioning is from the TPU-GUI

RNC-AP provisioning

Note that the RNC-AP provisioning is the same as all other MM-AP applications.
RNC-DB

The RNC-DB stores all RNC configuration and operational data for all the RNCs in
the MSC. The RNC-DB also stores CDMA 1X RNC hardware and software alarms
and TMN states for all the RNCs in the MSC.
OAM AP/OAM Proxy AP interface

The OAM AP pair and the OAM Proxy AP pair interface with the OMP/OMC RAN
through the customers maintenance IP network.
AP HW and VCVM provisioning and fault management

PRELIMINARY

APOAM provides AP HW and VCVM provisioning and fault management functions

for the RNC-APs and various application VCVMs on the RNC-APs, that is, TCS
VCVM, RNC-M VCVM, TPU-GUI VCVM.

2-28

Call
processing software components and interfaces
...................................................................................................................................................................................................................................
Introduction

The CDMA 1X RNCcall processing depends on several software call processing

components.

PRELIMINARY

System Architecture

Components

The CDMA 1X RNC software call processing components are listed as follows:

TCS: Traffic Control Server handles real time RNC bearer resource management,
supports RNC bearer resource availability monitoring and provides call processing
functions for 1X RNC. TCS VCVM resides on the pair of RNC-APs.
FSRM: Frame Selector Resource Manager is the local bearer resource manager on a
traffic processor. It establishes, maintains and releases traffic channel instances on a
local traffic processor. Each traffic processor has one FSRM instance. Each CICC
card has three traffic processors.
PCF-CP: PCF Call Processing provides 1X PCF signaling and control functions to
interface with FS/RLP functions in the RAN and PDSN functions in the Packet
Data Network. It establishes, maintains and releases user bearer paths over the A8
Interface (between PCF and RAN) and over the A10 interface (between PCF and
PDSN).

Interfaces

Figure 2-12, CDMA 1X RNC Call Processing Interface (p. 2-30) summarizes the
major 1X RNC call processing interface architecture.

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
2-29
Issue 14, September 2009
See notice on first page

PRELIMINARY

System Architecture

Call processing software components and interfaces

Figure 2-12 CDMA 1X RNC Call Processing Interface

TCS

The TCS is the center entity for all the 1X RNC call processing. It interfaces with the:

Cell Call Processing Entities (RCSs) to establish, maintain and release a data call
through the 1X RNC.

ECPC/CDN to get the subscriber information and update the link layer data call
records.

ECPC to report BHS status.

FSRMs on the TPU shelves to allocate, maintain and release the data Frame
Selection and RLP instances.

PCF-CP to coordinate data call network reactivations and to deliver SDB payloads
to the PCF/PDSN.

PRELIMINARY

FSRM

FSRM interfaces with PCF-CP to establish, maintain and release the A8 connectivity to
PCFs. This is the A9+ interface. Note that the A9+ interface is the standard A9
interface with Lucent enhancements. For example, RNC-to-PCF/PDSN reachability
monitoring.

2-30

Call processing software components and interfaces

The A8/A9GW service on the path provides the NAT functions and IP transport
address filtering functions to isolate the 1X RNC internal communication network from
the external customer IP bearer network.
The A8/A9 GW function is used for communication between FSRMs in one frame and
PCF functions external to that RNC frame. This includes configurations that include
multiple RNCs in an MSC, or configurations which use either a 3rd party PCF or the
E-PCF.

PRELIMINARY

System Architecture

If the configuration contains a single RNC with B-PCFs only, then A8/A9
communications between FSRMs and B-PCFs is performed internal to the RNC frame,
and does not use the A8/A9 GW Service.
PCF-CP

PCF-CP interfaces with PDSN to establish, maintain and release the A10 connectivity
to PDSNs. This is the A11 interface.
The A10/A11GW service on the path provides the NAT functions and IP transport
address filtering functions to isolate the 1X RNC internal communication network from
the external customer IP bearer network. However, it will not alternate any application
layer information.

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
2-31
Issue 14, September 2009
See notice on first page

PRELIMINARY

System Architecture

User
bearer processing software components and interfaces
...................................................................................................................................................................................................................................
Introduction

The CDMA 1X RNC user bearer processing functions all reside in the CDMA 1X
RNC Integrated Frame,that is on the TPU shelves. The current traffic processing
entities support 3G1X Packet Data Bearer only.
Components

The CDMA 1X RNC software bearer processing components are listed as folows:

FS/RLP: FS/RLP provides Frame Selection and RLP functions for 1X user bearer
streams. It resides on each Traffic Processor. Each Traffic Processor has multiple
instances of FS/RLP. Each instance of FS/RLP is dedicated to one active data call.
Each CICC has three traffic processors.

GRE: GRE provides layer processing in each Traffic Processor. The GRE entity in
the TP initiates or terminates traffic packets to/from the packet data core network
(that is, the A8 interface can be regarded as the beginning of the packet data core
network packet flows). It also receives and delivers the proper octet stream to/from
the Radio Access Network (that is, the FS/RLP instance can be regarded as the
beginning of the RAN packet flows).
5E GW: 5EGW interfaces into the existing soft handoff universe and terminates the
existing inter-PSU soft handoff protocol layers. 5E GW may reside on one or more
pairs of GICC cards, including the SC-GICC.

IPBTS GW. IPBTS GW supports IPBH terminations, routes the IPBH packets in
and out the 1X RNC, and provides NAT functions and packet filtering functions
to/from the IPBH bearer network for communications between FS/RLP in the 1X
RNC and Channel Element in the Cell Site. The IPBTS GW resides on
IPBTS-GICC cards.

IPSHO GW. IPSHO GW interfaces with other RNCs or PSUs for inter- and
intra-MSC soft handoff over IP connections. IPSHO GW resides on a pair of
IPSHO-GICC cards.

A8/A9 GW: A8/A9 GW provides NAT functions and packet filtering functions
to/from the external customer IP bearer network for communications between
FS/RLP and PCFs (that is E-PCF or B-PCF in another RNC). A8/A9 GW resides
on the SC-GICC pair.
A10/A11 GW: A10/A11 GW provides NAT functions and packet filtering functions
to/from the external customer IP bearer network for communications between
B-PCF and PDSN. A10/A11 GW resides on the SC-GICC pair.

PRELIMINARY

PCF-TP: PCF-TP provides PCF bearer processing functions, including GRE

Switching between the A8 interface and the A10 interface and TCP flow control
functions. It resides in each PCF.

2-32

User bearer processing software components and

interfaces

Interfaces

Figure 2-13, CDMA 1X RNC User Bearer Interfaces (p. 2-33) summarizes the major
1X RNC bearer interface architecture.
Figure 2-13 CDMA 1X RNC User Bearer Interfaces

PRELIMINARY

System Architecture

FS/RLP<=>FRBTS

This is the application interface between the Channel Element in a FRBH Cell and an
FS/RLP instance in the 1X RNC. The application packets are carried through the
FRBH, the PSU, the ATM SHO universe and the 5EGW services. The FRBH is
terminated in 5E-PSU. The AAL5/ATM protocol stack and the 5E Packet Bus Protocol
are terminated in the 5EGW, as shown in the path of the application interface between
CE in a FRBH Cell and FS/RLP in the 1X RNC.
FS/RLP<=>IPBTS

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
2-33
Issue 14, September 2009
See notice on first page

PRELIMINARY

This is the application interface between the Channel Element in an IPBH Cell and an
FS/RLP instance in the 1X RNC. The application packets are carried through the IPBH
and the IPGW services to the FS/RLP instance. The IPBH protocol stack is terminated
in the IPBTS GW. Then IPBTS GW routes the application packets to the FS/RLP
through the 1X RNC Internal Communication Protocol.

PRELIMINARY

System Architecture

User bearer processing software components and

interfaces

FS/RLP<=>GRE

This is an internal software interface for traffic processing software on each TP, which
delivers octet streams between an FS/RLP instance and a GRE instance for each active
data call. Each octet stream is encapsulated as the RLP payload towards the mobile by
the FS/RLP instance and is encapsulated as the GRE payload towards the PDSN by the
GRE instance.
GRE<=>PCF-TP

This is the A8 bearer interface between FS/RLP/GRE and PCF Traffic Processing
Function. The A8/A9GW service on the path provides the NAT functions and IP
transport address filtering functions to isolate the 1X RNC internal communication
network from the external customer IP bearer network. However, it will not alternate
any application layer information. Note that for communications between GRE and
PCF within the same RNC, the A8/A9 GW is not involved.
PCF-TP<=>PDSN

PRELIMINARY

This is the A10 bearer Interface between B-PCF and PDSN. The A10/A11GW service
on the path provides the NAT functions and IP transport address filtering functions to
isolate the 1X RNC internal communication network from the external customer IP
bearer network. However, it will not alternate any application layer information.

2-34

Physical
Network Connectivity
...................................................................................................................................................................................................................................
Introduction

Figure 2-14, Physical network connectivity (p. 2-35) depicts the physical
connectivity in the CDMA 1X RNC deployment for packet data offload applications.

PRELIMINARY

System Architecture

Figure 2-14 Physical network connectivity

RNC-APs

RNC-APs connect to the RNC Cabinet and the AP dual-rail LAN, as well as the ECPC
IMS ring.
OAM Proxy APs

CICC cards

Application node cards (CICCs) provide all the traffic processing functions for
supporting 1X Packet Data Services.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
2-35
Issue 14, September 2009
See notice on first page

PRELIMINARY

OAM Proxy-APs connect to the AP dual-rail LAN and the Customer Maintenance IP
network, as well as ECP IMS ring.

PRELIMINARY

System Architecture

Physical Network Connectivity

GICC cards

All the I/O functions for user bearer traffic are provided by the various GICC cards.
SC-GICC pairs

The SC-GICC pair has the 5EGW services, the A8/A9GW service and the
A10/A11GW Service.
B-PCF cards

The B-PCFs integrated within the RNC cabinet, provide the packet control functions.
Cable connections

The cable connections can be categorized as the internal control interfaces and the
external bearer interface.
Internal control interfaces

The MM-AP servers use the following connection criteria:

The RNC-AP pairs connect to the RNC Cabinet through the ESC cards. These
connections are 100Base-TX (full-duplex).

The OAM Proxy-AP pairs connect to the OMP/OMC RAN through 100Base-TX
links (full-duplex).

The RNC-AP pairs and the OAM Proxy-AP pairs are all connected to the ECP/IMS
ring through the EINE nodes. These connections are 100Base-TX (full-duplex).
All of these ethernet connector types are shielded RJ-45.
External bearer interface

The RNC interface coming out from the GICC card and into the existing ATM SHO
universe is AAL5/ATM/OC-3c. The physical media can be the multi-mode fiber or the
single mode fiber. The fiber connector on the GICC cards is the SC type.

PRELIMINARY

The two IPSHO GICCs per RNC are connected to the multi-layer switch using Gigbit
short-reach multi-mode Fiber in 1+1 sparing scheme for reliability and path
diversification.
The RNC interface into the the external IP bearer networks is provided via the
SC-GICC. There are four cable connections coming out of the RNC Cabinet for the
A8/A9 (two) and A10/A11 (two) service. The Ethernet connections are
100/1000Base-TX (fully duplex). All the connector types are shielded RJ-45.

2-36

B-PCF
Architecture
...................................................................................................................................................................................................................................
Introduction

The Blade Packet Control Function (B-PCF) provides a packet control function that is
implemented on a Solaris Blade with an attached PMC disk drive. The executable
software as well as required data resides on the local disk.

PRELIMINARY

System Architecture

Integration

The B-PCF is fully integrated within the CDMA 1X RNC architecture, and is installed
directly in the TPU shelf.
Function

The B-PCF provides the interface between the radio network side of a data call and the
internet part of a data call. The B-PCF also manages the number of active, and
dormant packet data sessions.
Communication

The B-PCF communicates via the CICC/TCS on the RNC-side and the Packet Data
Serving Node (PDSN) on the internet-side. The CICC/TCS interacts with the B-PCF
through the A8/A9 interface and the PDSN interacts with the B-PCF through the
A10/A11 interface.
Each B-PCF can be configured to communicate with a maximum of 256 PDSNs.
Logical configuration

Each B-PCF is considered a separate PCF from the traffic processing perspective.
Currently, a CDMA 1X RNC will support up to eight distinct B-PCF servers using
eight cards, and requiring eight IP addresses.
Software

The PCF server has a layered software architecture consisting of the PCF Application
(PCFA) and Solaris operating system software. The B-PCF also uses third party
middleware.
Figure 2-15, B-PCF functional decomposition (p. 2-38) illustrates the layered
architecture of the B-PCF in the TPU shelf.
The PCFA manages itself via its PCF manager, and has interfaces to the TPU-M to
send event messages.
The Lucent Platform is an infrastructure used by the PCF control path programs, that
provide various communication and process control functionality.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
2-37
Issue 14, September 2009
See notice on first page

PRELIMINARY

PCFA components

PRELIMINARY

System Architecture

B-PCF Architecture

Figure 2-15 B-PCF functional decomposition

Data and control paths

The data path (A8 & A10) and the control path (A9 & A11) are illustrated in Figure
2-16, B-PCF control and data paths (p. 2-39).
Ethernet interfaces

PRELIMINARY

The Ethernet interfaces (Figure 2-16, B-PCF control and data paths (p. 2-39)) are
operated active/standby. All packets arrive on the active ethernet interface, and the
802.3 driver delivers the packets to the IP module.
A9 and A11 UDP/IP signaling packets are sent up to PCFCC for processing. A8 and
A10 GRE bearer packets are sent to GRE for GRE and flow analysis processing.
After processing, both signaling and bearer packets are sent back out over the active
ethernet interface.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

2-38

B-PCF Architecture

Figure 2-16 B-PCF control and data paths

PRELIMINARY

System Architecture

B-PCF management

The B-PCF is managed by the RNCM over the TPU cPSB ethernet backplane, see also
Figure 2-17, B-PCF management software (p. 2-40).
As shown in Figure 2-17, B-PCF management software (p. 2-40), the primary
processes involved in B-PCF management are the PCFA OA&M processes. These are
listed as follows:
PCF Manager

PCF Agent

PCF Maint
PCF Logger.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
2-39
Issue 14, September 2009
See notice on first page

PRELIMINARY

System Architecture

B-PCF Architecture

Figure 2-17 B-PCF management software

Solaris init scripts start the PCF Manager, and the PCF Manager creates all PCFA
control path processes, and monitors their status.
Security

Security for the B-PCF is provided by means of the manner in which its bearer data is
received, and through the secure attributes of the GICC card.
Bearer data

PRELIMINARY

With bearer data, the B-PCF receives unstructured byte stream fragments of PPP
frames. As a result, no security danger is posed because this data is treated strictly as
payload data.
Note, that this bearer data becomes unsecure after the PDSN converts the PPP frames
into routable IP datagrams, but within the B-PCF itself it is not in IP datagram format,
and therefore harmless because it is not routable.
GICC card

The B-PCF communicates to the GICC over the TPU shelf backplane.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

2-40

B-PCF Architecture

All arriving and departing A10/A11 packets enter through the GICC. The GICC
A10/A11 gateway only allows those packets that meet the criteria for mapping the
external IP address to the internal IP address.
This arrangement essentially serves to function as an effective firewall.

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
2-41
Issue 14, September 2009
See notice on first page

PRELIMINARY

System Architecture

PRELIMINARY

System Architecture

CDMA
1X RNC high-level call control signaling
...................................................................................................................................................................................................................................
Introduction

In the following subsections, the high-level ladder diagrams for 1X packet data call
signaling flows in a CDMA 1X RNC system will be provided. These call signaling
flows are the data session initiation, the mobile reactivation and the network
reactivation. Note that only best-case scenarios are addressed here.
Data session initiations in a CDMA 1X RNC system

This scenario begins when a subscriber powers on the mobile and the mobile initiates a
PPP session to the PDSN. Figure 2-18, 1X Packet data call session initialization
(p. 2-42) shows the ladder diagram of call signaling steps.

PRELIMINARY

Figure 2-18 1X Packet data call session initialization

The following is a summary of call signaling sequences.

2-42

CDMA 1X RNC high-level call control signaling

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

Upon receiving Mobile Origination (with SO=33), the RCS decides that the mobile
attached cell supports the CDMA 1X RNC features and sends a call setup request to a
CDMA 1X RNC. Meanwhile, it also informs the mobile request to the CDN for MSC
level call processing.

PRELIMINARY

System Architecture

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

Since this is a new data session initiation, CDMA 1X RNC needs to wait the
subscriber information from the CDN in order to build the link layer record for the
mobile. After the CDN has authorized the mobile and its call request, it will send a
message to the CDMA 1X RNC containing the subscriber information.
...................................................................................................................................................................................................

Meanwhile, CDN instructs the cell to set up the traffic channel over the air link.
...................................................................................................................................................................................................

CDMA 1X RNC begins to build the Link Layer Record with the CDN provided
information and the information in the setup request from the RCS. Then CDMA 1X
RNC selects the serving PCF/PDSN and sends session setup request to the chosen
PCF/PDSN.
...................................................................................................................................................................................................

The serving PCF/PDSN connects to the Radio Access Network and acknowledges the
successful allocation of the A8 and/or A10 bearer paths.
...................................................................................................................................................................................................

The CDMA 1X RNC adds the serving PCF and the serving PDSN information into the
Link Layer Call Record for the mobile. Then it sends the Data Call Setup complete
indication to the RCS with the address of the allocated FS/RLP instance for the data
call.
...................................................................................................................................................................................................

During the air link setup, additional mobile capability is negotiated between the mobile
and its attached cell. These information may be needed to update the billing record.
Thus, the RCS, once it finishes the air link setup, will send a mobile information
update message to the CDMA 1X RNC. Further, the RCS sends the traffic channel
confirmation message to the CDN. With the information in the origination message and
the information in the traffic channel confirmation message, the CDN creates the new
Link Layer Record for the mobile in the ECPC.

The CDMA 1X RNC not only puts the additional mobile information into the Link
Layer Record but also informs the serving PCF/PDSN.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
2-43
Issue 14, September 2009
See notice on first page

PRELIMINARY

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

PRELIMINARY

System Architecture

CDMA 1X RNC high-level call control signaling

At this moment, the bearer path between the mobile and the serving PDSN is
completed and the mobile now can complete the PPP session setup.
Mobile reactivations in a CDMA 1X RNC system

This scenario begins when a mobile, which already has a PPP session, has user data to
send and the mobile initiates a data call request to the CDMA 1X RNC system. Figure
2-19, Mobile reactivation call signaling flow (p. 2-44) shows the ladder diagram of
call signaling steps.
Figure 2-19 Mobile reactivation call signaling flow

The following is a summary of call signaling sequences.

PRELIMINARY

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

2-44

CDMA 1X RNC high-level call control signaling

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

Since this is a data call request for an existing session, the CDN immediately instructs
the cell to set up the traffic channel over the air link.
...................................................................................................................................................................................................

PRELIMINARY

System Architecture

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

During the air link setup, additional mobile capability used for this particular
reactivation may be negotiated between the mobile and its attached cell. This
information may be needed to update the billing record. Thus, the RCS, once it
finishes the air link setup, sends a mobile information update message to the CDMA
1X RNC. Further, the RCS sends the traffic channel confirmation message to the CDN.
...................................................................................................................................................................................................

The CDMA 1X RNC informs additional billing information to the serving PCF/PDSN.
At this moment, the bearer path between the mobile and the serving PDSN is
completed and the mobile now can send the user data to the PDSN.

Network reactivations in a CDMA 1X RNC system

This scenario begins when a network node or a host in the Packet Data Network has
user data to send to a mobile, which already has a PPP session with the PDSN. Figure
2-20, Network reactivation call signaling flow (p. 2-46) shows the ladder diagram of
call signaling steps.

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
2-45
Issue 14, September 2009
See notice on first page

PRELIMINARY

System Architecture

CDMA 1X RNC high-level call control signaling

Figure 2-20 Network reactivation call signaling flow

The following is a summary of call signaling sequences.

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

PCF/PDSN buffers user data from the network and sends an incoming call request to
the proper CDMA 1X RNC.
...................................................................................................................................................................................................

PRELIMINARY

CDMA 1X RNC verifies that the incoming call is for an existing data session and
sends an incoming call request to the CDN.
...................................................................................................................................................................................................

CDN verifies that the incoming call is for an existing data session and sends a Page
request to the cells.

2-46

CDMA 1X RNC high-level call control signaling

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

Upon receiving mobile page response (with SO=33), the RCS decides that the mobile
attached cell supports the CDMA 1X RNC features and sends a call setup request to a
CDMA 1X RNC. Meanwhile, it also informs the page response to the CDN for MSC
level call processing.

PRELIMINARY

System Architecture

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

The CDN instructs the cell to set up the traffic channel over the air link.
...................................................................................................................................................................................................

CDMA 1X RNC gets the existing link layer record for the mobile, allocates the
FS/RLP instance for the data call request and acknowledges the call setup request to
the RCS. Meanwhile, CDMA 1X RNC sends the A8 and/or A10 setup request to the
serving PCF/PDSN, based on the existing link layer record.
...................................................................................................................................................................................................

During the air link setup, additional mobile capability used for this particular
reactivation may be negotiated between the mobile and its attached cell. These
information may be needed to update the billing record. Thus, the RCS, once it
finishes the air link setup, sends a mobile information update message to the CDMA
1X RNC. Further, the RCS sends the traffic channel confirmation message to the CDN.
...................................................................................................................................................................................................

The 1X RNC informs additional billing information to the serving PCF/PDSN.

At this moment, the bearer path between the mobile and the serving PDSN is
completed and the PCF/PDSN now can send the user data to the mobile.

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
2-47
Issue 14, September 2009
See notice on first page

PRELIMINARY

3H ardware architecture

This chapter describes the components that comprise the CDMA 1X RNC deployment.
Deployment

The RNC deployment consists of an RNC cabinet that contains the TPU hardware, and
a new or existing MM-AP growth cabinet that contains the MM hardware of the RNC.
Dual cabinet solution

The use of two cabinets for the RNC provides a flexible hardware configuration
between controller processors in the MM-AP growth cabinet, and processors in the
RNC cabinet. This allows for different controller capacity and traffic processing needs.
Current design

In the current design:

Both cabinets are deployable in a 5ESS lineup (6-foot height limit).

The call processing function is provided by RNC-AP servers in the MM-AP growth
cabinet and the CICC cards in the RNC cabinet
The traffic processing function is accomplished within the Traffic Processing Unit
(TPU) in the RNC cabinet via specific gateway and common cards.

Contents
3-3

Cabinet indicators

3-9

Frame Interface Panel (FIP)

3-12

Power distribution shelf

3-14

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
3-1
Issue 14, September 2009
See notice on first page

PRELIMINARY

RNC cabinet

PRELIMINARY
PRELIMINARY

Hardware architecture

Overview

Terminal server

3-17

cPSB chassis and components

3-20

Power trays

3-22

Chassis fan trays

3-24

Alarm card

3-26

Ethernet switch card

3-27

TPU shelf components

3-30

GICC cards

3-33

CICC cards

3-37

Solaris B-PCF

3-39

MM-AP Cabinet

3-41

RNC-AP (400S server)

3-43

RNC-AP (410S server)

3-47

OAM proxy AP (400S server)

3-50

OAM proxy AP (410S server)

3-53

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

3-2

RNC cabinet
Overview
...................................................................................................................................................................................................................................

PRELIMINARY

Hardware architecture

Purpose

This section describes the hardware that comprises the RNC cabinet.
Cabinet design

The RNC cabinet design is based on the NEBS2000 cabinet guidelines for height,
width, and depth (1825mm x 600mm x 600mm). The base cabinet design supports site
installations in standard equipment aisles, with both front and rear maintenance access,
and in locations where rear cabinet access is totally restricted.
Universal compatibility

The NEBS2000 cabinet physical size ensures a product that can be installed directly in
an existing 5ESS line up as well as provide full compatibility with the European Union
Telecommunications ETSI site installation requirements.
Physical configuration

Figure 3-1, RNC cabinet (2310) (p. 3-4) illustrates the physical organization of the
major elements of the RNC cabinet.

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
3-3
Issue 14, September 2009
See notice on first page

PRELIMINARY

Hardware architecture

Overview

Figure 3-1 RNC cabinet (2310)

Cabinet exterior

The look and feel of the RNC cabinet has been chosen to blend with 5ESS cabinet
line-ups in existing installations, or to stand alone as needed.
Stand-alone cabinet

PRELIMINARY

Figure 3-2, Cabinet aesthetics (p. 3-5) shows a stand-alone cabinet either with or
without the optional cable shroud to cover top cable access. When more than one
cabinet is used in a line-up, the cabinets are attached to each other.

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

3-4

Overview

Figure 3-2 Cabinet aesthetics

PRELIMINARY

Hardware architecture

5ESS lineup installation

Figure 3-3, RNC cabinet with 5ESS stanchions and end guard (p. 3-6) shows the
RNC cabinet with filler stanchions and an end guard in place for aesthetic display
within an existing a 5ESS cabinet lineup. This is an optional feature for some
installations.

PRELIMINARY

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
3-5
Issue 14, September 2009
See notice on first page

PRELIMINARY
PRELIMINARY

Hardware architecture

Overview

Figure 3-3 RNC cabinet with 5ESS stanchions and end guard

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

3-6

Overview

Cabinet characteristics

The following table provides a high-level summary of the RNC cabinet characteristics.
Function

Characteristic

Cabinet Height with Earthquake Mounting

Hardware (No Cable Shroud)

1825 mm (71.9 inches)

Cabinet Height with Cable Shroud (Including

earthquake mounting)

2200 mm (86.6 inches)

External Cabinet Width

598 mm (23.5 inches)

External Cabinet Depth

600 mm (23.6 inches)

Cabinet Weight (maximum equipage)

408 kg (900 lbs)

Maximum 48 V Load Current per power bus at 40

88 Amps

Maximum Cabinet Heat Dissipated

3500 watts (11,943 BTUs per hr.)

Operating Temperature Range - Long-term

5C to 40C

Operating Temperature Range - Short-term

-5C to 50C

Operating Humidity Range - Long-term

5% to 85%

Operating Humidity Range - Short-term

5% to 90%

Telecommunication Industry Compliance

ETSI and NEBS including

Earthquake zone 4

International Regulatory Compliance

UL, FCC, CE mark

PRELIMINARY

Hardware architecture

Cabinet-level -48 V power

The RNC cabinet provides a high availability power infrastructure implemented via
redundancy combined with hardware separation. Fault isolation accounts for both
electrical and mechanical interactions, as both component failures and maintenance
activities can potentially create dual fault conditions.
Fault groups

All duplicated functions within the cabinet are assigned to one of two primary fault
groups, either A or B.

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
3-7
Issue 14, September 2009
See notice on first page

PRELIMINARY

Both power fault groups are required to provide power fault tolerance for duplex
hardware (cPSB chassis). Simplex hardware, such as the terminal servers, that do not
support redundant power, must be cabled such that each chassis is in a separate power
fault group.

PRELIMINARY

Hardware architecture

Overview

Components

Basic cabinet components consists of the following:

Cabinet indicators (status LEDs)

Frame Interface Panel (FIP) Power distribution shelf with two Enhanced Circuit
Breaker Units (ECBUs)
Two Traffic Processing Unit (TPU) shelves that contain Ethernet switch, alarm, and
blade (GICCs, CICCs, B-PCFs) cards with:
Chassis power supply units (PSU)

Chassis air filter covered by a grill

Chassis Fan drawers

One terminal server

Contents

PRELIMINARY

Cabinet indicators

3-9

Frame Interface Panel (FIP)

3-12

Power distribution shelf

3-14

Terminal server

3-17

cPSB chassis and components

3-20

Power trays

3-22

Chassis fan trays

3-24

Alarm card

3-26

Ethernet switch card

3-27

TPU shelf components

3-30

GICC cards

3-33

CICC cards

3-37

Solaris B-PCF

3-39

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

3-8

Cabinet
indicators
...................................................................................................................................................................................................................................
Introduction

The cabinet -level equipment indicators and how they work are described in this
section.

PRELIMINARY

Hardware architecture

Cabinet LEDs

Cabinet-level equipment status LED indicators are incorporated above each cabinet
door to help guide maintenance personal directly to any cabinet requiring attention.
SeeFigure 3-4, Cabinet LEDs (p. 3-9).
Figure 3-4 Cabinet LEDs

Figure 3-5, Cabinet LED alarms and triggers (p. 3-10) illustrates the logical
information flow that drives the various LEDs. See Table 3-1, LEDs and outputs
(p. 3-10) for LED meanings and events.

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
3-9
Issue 14, September 2009
See notice on first page

PRELIMINARY

Hardware architecture

Cabinet indicators

Figure 3-5 Cabinet LED alarms and triggers

Table 3-1

LEDs and outputs

PRELIMINARY

Individual Scenarios

Input
Breaker/Fuse Equipment
Power
LED
Fault LED
LED

All OK (both ECBUs installed and -48V

present at both ECBU inputs)

OFF

Input Power Bus A or B failure

OFF

Undefined
(Note)

Any breaker tripped

OFF

Single breaker manually set to off

OFF

ECBU Power LED off (internal ECBU fault

that prevents power from being connected to
circuit breakers)

OFF

Total input power failure

OFF

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

3-10

Cabinet indicators

Notes:

To avoid complications involved in duplex powering the alarm board, loss of either the A
or B 48V input (Input Power LED off) may result in the alarm boards inability to
enunciate any other alarm condition. This is acceptable since the loss of power is the
highest order fault and must be addressed before trouble shooting any faults that may
have occurred as a result loosing A or B.

PRELIMINARY

Hardware architecture

Reference

See Appendix A, Controls and indicators for additional information on the cabinet
level LEDs.
Providing visibility

Without additional contact closure alarm information, items such as 48 V power, and
cabinet cooling would not have specific visibility from a remote maintenance center.
Unmonitored high-level problems commonly appear as a number of other equipment
failures.

PRELIMINARY

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
3-11
Issue 14, September 2009
See notice on first page

PRELIMINARY

Hardware architecture

Frame
Interface Panel (FIP)
...................................................................................................................................................................................................................................
Introduction

The Frame Interface Panel (FIP), provides the cabinets cable demarcation function. In
other words, with the exception of the fiber optic cables, all internal cabinet conductive
cables entering or leaving the cabinet must terminate and be appropriately labeled at
the FIP.
The FIP (Figure 3-6, Frame Interface Panel (FIP) (p. 3-12)) provides a number of
functions including, replaceable internal cable restraining hardware, EMC cable
terminations (both for internal and external cable shielding) and a simplified external
cabinet cabling maintenance interface. Cable finger guides (15 in all) at the top of the
FIP help with cable management.
Also see Figure 3-6, Frame Interface Panel (FIP) (p. 3-12) for FIP power entry
assembly
Figure 3-6 Frame Interface Panel (FIP)

Front cover

PRELIMINARY

The FIP includes a multi-function removable front cover that provides isolation for the
cable connections and a location for maintenance, regulatory and safety labeling. The
inside of the FIP covers includes a small documentation holder for required safety
documentation.

3-12

Frame Interface Panel (FIP)

Fiber optic cables

Fiber optic cables are not terminated at the FIP since the additional connections add
complexity and signal losses. The fiber optic cables pass through the top or bottom of
the cabinet with appropriate cable restraints and terminate directly at the destination
GICC blade.

PRELIMINARY

Hardware architecture

Grounding

The FIP employs low impedance, safety connections to chassis earth ground to cover
potential -48 V power fault conditions. The grounding path to the safety earth ground
also minimizes the effects of external shield ground noise.
With the FIP also providing a termination location for internal shielded cables, it also
has a high frequency low impedance path back to all internal cabinet noise sources.
Figure 3-7 Power input views

-48 V input power

For extra safety both the FIPs front and rear power connections have removable safety
shields.

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
3-13
Issue 14, September 2009
See notice on first page

PRELIMINARY

All of the cabinets -48 V input power enters via four isolated power lugs in the FIPs
power entry assembly. External power cable termination hardware supports both AWG
#1/0 wiring via lugs with a hole diameter of 5/16.

PRELIMINARY

Hardware architecture

Power
distribution shelf
...................................................................................................................................................................................................................................
Introduction

The Power Distribution Shelf (PDS) includes two individually serviceable Enhanced
Circuit Breaker Units (ECBUs) and an alarm board. See Figure 3-8, Power
distribution shelf (p. 3-14).
Figure 3-8 Power distribution shelf

Power distribution

The block diagram shown in Figure 3-9, Power Distribution Block diagram (p. 3-14)
shows two ECBUs, as part of the PDS, being used to distribute power to a number of
units within an RNC cabinet.

PRELIMINARY

Figure 3-9 Power Distribution Block diagram

3-14

Power distribution shelf

Each ECBU distributes only the 48V A bus or 48V B bus power, never both. An
individual functional unit may be simplex powered (Terminal Server), or duplex
powered (cPSB shelf). Each ECBU provides power distribution and protection of
48VDC to each of the other units within the cabinet.
Enhanced Circuit Breaker Unit (ECBU)

PRELIMINARY

Hardware architecture

Each ECBU utilizes field replaceable circuit breakers to protect the branch circuits in
case of an over-current condition.
Each ECBU:

Works with the other ECBU to distribute and share power evenly to each of the
other components in the cabinet.

Low Voltage disconnect of the branch circuits when the input 48VDC drops below
39V. This is done to protect the battery plant from further discharge that could
damage it. Automatic reconnection of the branch circuits will occur when the
battery plant recovers to approximately 44VDC.

Over Voltage disconnect of the branch circuits when the 48VDC input exceeds
60V. This is done to protect the other shelves in the cabinet from damage.
Automatic reconnection of the branch circuits occur when the battery plant drops to
approximately 58VDC.

Reverse Polarity protection of the branch circuits to prevent the other shelves from
seeing +48VDC at their inputs.

Voltage Dropout protection to isolate the branch circuits from short duration drops
to 0V up to 10 ms on the 48VDC input of the ECBU.

The circuit breakers in each ECBU are identified by number (CB1 through CB9), from
left to right. Each circuit breaker corresponds to a different component in the cabinet.
See Table 3-2, ECBU breaker assignments (p. 3-15).
ECBU breaker assignments

Breaker

ECBU A function

ECBU B function

CB 1

Not used

CB 2

Terminal server lower (optional)

Terminal server upper (optional)

CB 3

Not used

CB 4

cPSB lower

CB 5

cPSB lower

CB 6

cPSB upper

CB 7

cPSB upper

CB 8

Not used

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
3-15
Issue 14, September 2009
See notice on first page

PRELIMINARY

Table 3-2

PRELIMINARY

Hardware architecture

Table 3-2

Power distribution shelf

ECBU breaker assignments (continued)

Breaker

ECBU A function

ECBU B function

CB 9

Cabinet fan (optional)

PDS alarm board

PRELIMINARY

The alarm board acts as an alarm collection and dissemination point for cabinet level
alarm information. The alarms are generated by different equipment inside the cabinet.
The alarm board collects the alarm input and generates output to the cabinet LEDs, and
also sends alarm triggers to the chassis alarm cards.

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

3-16

Terminal
server
...................................................................................................................................................................................................................................
Introduction

The terminal server provides an alternative method for authorized installation and field
maintenance personnel to access the serial interfaces of each TPU board via an ethernet
interface.

PRELIMINARY

Hardware architecture

When to use

When boards are unconfigured or in unreachable states, access from the terminal server
is the only way to perform low-level debugging and access without having to
physically connect a serial cable to a card with a special terminal.
Front view

Figure 3-10, Front view of terminal server (p. 3-17) shows the front of the terminal
server used in the RNC cabinet (2310). The terminal server provides 40
software-configurable ports, DC power input, and an Ethernet port. A PMC-type flash
card that is inserted into a front slot, contains the pre-configured software load that is
required at when the unit is powered on or initialized.
Figure 3-10 Front view of terminal server

Rear view

See Figure 3-11, Rear view of terminal server (p. 3-17) for an example of key
elements at the rear of the terminal server.
Figure 3-11 Rear view of terminal server

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
3-17
Issue 14, September 2009
See notice on first page

PRELIMINARY

Hardware architecture

Terminal server

Ports

Figure 3-12, Terminal server port assignments (p. 3-18) identifies the port locations
on the rear of the terminal server.
Figure 3-12 Terminal server port assignments

The 40 ports can each be configured as:

Console Port (Remote) to connect directly to other devices. Note that all ports are
configurable, with a default of 8 bits, no parity, 1 stop bit, 9600 baud. An
auto-bauding feature permits a speed setting between 50 and 38400. Fixed settings
are also permitted between 50 and 115200. The valid settings above 38400 are
56000, 57600, 64000, 76800, and 115200 with a limited number of ports (six)
using speeds greater than 57600.All slot positions are populated and couplers are
fitted from the front.
Important! All applications should only set a maximum of four ports to the higher
speeds. Specifically, limit the use of 115200 to connecting up to four alarm card
ports.

PRELIMINARY

Local (Management) Port (port 40, see Figure 3-11, Rear view of terminal server
(p. 3-17)): It is recommended that the default settings not be changed. This port
should be configured as 8-bit characters with parity set to NONE, XON flow
Control, VT100 Terminal Emulation and one stop bit in order to receive load
messages and to enter into the ROM Configuration Menu. The port will autobaud
between 50 and 38400 Kbps.

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

3-18

Terminal server

Software load

The terminal servers are pre-set at the factory to load configuration software from a
flash card, if one has been inserted in the card slot on the face of the terminal. If a
card is not present, the unit will request a software image from a network load server.
The software load will be required whenever the unit is powered on or re-initialized.

PRELIMINARY

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
3-19
Issue 14, September 2009
See notice on first page

PRELIMINARY

Hardware architecture

PRELIMINARY

Hardware architecture

cPSB
chassis and components
...................................................................................................................................................................................................................................
Introduction

The compactPCI Packet Switched Backplane (cPSB) chassis is referred to for the
1X-RNC as the Traffic Processing Unit (TPU) shelf, and it contains the central
processor units for CDMA 1X RNC. Up to 2 cPSB chassis (TPU shelves) can be
contained in the RNC cabinet (2310).
RNC cabinet (2310)

The cPSB chassis shown in Figure 3-13, cPSB chassis (Front View) (p. 3-20) is a
typical layout for a cPSB chassis. See TPU shelf components (p. 3-30) for the TPU
shelf maximum and minimum configurations in the 1X RNC. The cPSB chassis resides
in the RNC cabinet (2310) as shown in Figure 3-1, RNC cabinet (2310) (p. 3-4).

PRELIMINARY

Figure 3-13 cPSB chassis (Front View)

3-20

cPSB chassis and components

cPSB chassis

The cPSB chassis includes the backplane, power, and cooling. It is a full-height (12U
high) chassis that provides slots for the remaining subcomponents.
Chassis components

The chassis components include:

Alarm cards: 2 per chassis

Ethernet switch cards (ESC: 2 per chassis

Up to 18 processing blades per chassis including Common Intelligent Carrier Cards

(CICCs), Gateway Common Carrier Cards (GICCs) and Blade PCFs (B-PCFs)

Power supply units

Fan trays

Blanking panels for unused slots

PRELIMINARY

Hardware architecture

cPSB chassis configuration

The maximum and minimum 1X RNC chassis configuration is described in the

following section: TPU shelf components (p. 3-30).

PRELIMINARY

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
3-21
Issue 14, September 2009
See notice on first page

PRELIMINARY

Hardware architecture

Power
trays
...................................................................................................................................................................................................................................
Introduction

Two power trays occupy the bottom of the cPSB chassis. Each tray has its own
backplane that provides slots for up to four power supplies. The power supplies are
field replaceable units.
Power supply unit

The cPSB shelf has eight Power Supply Units (PSUs), see Figure 3-13, cPSB chassis
(Front View) (p. 3-20), that provide multiple logic power domain. Each of these
power domains has multiple power supplies that convert 48VDC to logic power (-3.3,
-5, -12, and +12VDC).

PRELIMINARY

Figure 3-14 cPSB Power Block diagram

Within each domain the multiple power supplies are split such that half of them are
powered from the 48 A bus and the other half are powered from the 48 B bus
(Figure 3-14, cPSB Power Block diagram (p. 3-22)). In turn, each of those -48
busses supplies power to the chassis components (alarm cards, ESCs and various cards,
sometimes referred to as blades.

3-22

Power trays

Power

The fan drawers are powered from all eight power supplies at system at +12V.
Chassis air filter

The chassis air filter is located at the bottom of the cPSB chassis (Figure 3-15,
Chassis air filter (p. 3-23)) covered by an air intake grill

PRELIMINARY

Hardware architecture

Figure 3-15 Chassis air filter

PRELIMINARY

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
3-23
Issue 14, September 2009
See notice on first page

PRELIMINARY

Hardware architecture

Chassis
fan trays
...................................................................................................................................................................................................................................
Introduction

Each of the three fan trays is a field replaceable unit. Each tray contains three fans, a
control board, and a status LED. This combination of 3 trays with three fans each
provides cooling for the entire shelf.
Hot-Swappable

The fan trays are accessible from the front of the shelf and are hot-swappable.See
Figure 3-16, Fan trays with frame maintenance unit (FMU) in operating position.
(p. 3-24)and Hot-Swappable (p. 3-24).

PRELIMINARY

Figure 3-16 Fan trays with frame maintenance unit (FMU) in operating position.

3-24

Chassis fan trays

Figure 3-17 Fan tray with FMU in position for fan maintenance.

PRELIMINARY

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
3-25
Issue 14, September 2009
See notice on first page

PRELIMINARY

Hardware architecture

PRELIMINARY

Hardware architecture

Alarm
card
...................................................................................................................................................................................................................................
Introduction

The Alarm card (Figure 3-18, Alarm card (p. 3-26)) in the cPSB chassis supports
and monitors the presence and health of all plug-in cards, the fan trays and all power
supplies.
Figure 3-18 Alarm card

Function

Two half-height alarm cards are required for the CDMA 1X RNC. They populate a
single slot, and provide redundant operations for high-availability in each chassis. The
data collection and reporting from the alarm card also includes the collection of FRU
data, and the measurement of power supply voltages and temperatures at the different
blades within the chassis, and at different points in the chassis.
When any alarm condition monitored by the Alarm Card is cleared on the TPU shelf,
the Alarm Card will clear the alarm.
OA&M monitoring

The faceplate includes three amber alarm status LEDs, for Minor, Major and Critical
alarms, a status LED that reports on card activity and a hot swap LED.
References

PRELIMINARY

See Appendix A, Controls and indicators. for details on Alarm card LEDs.

3-26

Ethernet
switch card
...................................................................................................................................................................................................................................
Introduction

The Ethernet Switch Card (ESC) provides Ethernet switching connectivity within the
cPSB chassis, and connectivity to external links.Two ESCs are required per chassis.

PRELIMINARY

Hardware architecture

GIGE Ethernet links

Each ESC (Figure 3-19, Ethernet Switch Card (p. 3-27)) has 24-port GIGE Ethernet
Links. Nineteen of which are used for communication to the backplane. Out of the 5
remaining ports, 4 are brought to the front panel for a front access only configuration.
Figure 3-19 Ethernet Switch Card

Ports

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
3-27
Issue 14, September 2009
See notice on first page

PRELIMINARY

Four of the switched ports are available on the faceplate (Figure 3-19, Ethernet
Switch Card (p. 3-27)) for cascading with other switches within the cabinet, or for
interfacing with a network outside of the cabinet.

PRELIMINARY

Hardware architecture

Ethernet switch card

The 18 cPSB node slots are served with 18 of the switched ports. One port of the
switch is used for one of the Alarm Cards in slot 1. The upper Alarm Card Ethernet is
connected via the midplane to the first ESC and the lower Alarm Card is connected to
the second ESC. This arrangement actually leaves one of the 24 ports unused.
The following ports (see also Table 3-3, ESC ports and connections (p. 3-28))are
available on the ESC:

The four External Ports are used for inter-switch links and AP-to-TPU links. There
is a LAG with 2 Gbps aggregate bandwidth between ESC-U1 and ESC-L2. This
LAG guarantees that any node in a 1X RNC can communicate with any other
nodes in the 1X RNC, unless the node itself is totally out of service.

The Console Port provides connection via a 6 position RJ-11 connector to the
console port, and is used for direct local management. This port must be properly
configured.
The twenty-four switched ports are internally connected through the backplane.

The out-of-band Ethernet management ports.

See Figure 3-20, Frame level wiring architecture (p. 3-29) for internal wiring details.
Table 3-3

ESC ports and connections

Ports

Connection/Function

Console Ports

The Console port uses RS232 single levels providing a DTE

connection and the terminal (or terminal emulator)
connected to this port must be configured as follows:

Baud Rate: 9600

Data bits: 8

Stop bit: 1

Parity: None

Flow control: None

VT100 Terminal compatible

Four Gigabit Ports

Connection via RJ-45 connectors.

Out-of-Band Ethernet
Management Port

Connection via RJ-45 connector.

PRELIMINARY

OA&M monitoring

The faceplate includes Port Status LEDs, ESC system status LED for Minor, Major
and Critical alarms, a fault LED that reports on card activity, and a hot swap LED.
References

See Appendix A, Controls and indicators. for details on ESC LEDs.

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

3-28

Ethernet switch card

Frame architecture wiring

Figure 3-20, Frame level wiring architecture (p. 3-29) illustrates the frame level
wiring architecture.
Figure 3-20 Frame level wiring architecture

PRELIMINARY

Hardware architecture

In addition, the switch card supports layer-3 functionality, which may be enabled and
disabled via configuration commands on a per-port basis. The switch card will be able
to function as a L2 switch on some ports and as a L3 switch (router) on other ports at
the same time.

PRELIMINARY

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
3-29
Issue 14, September 2009
See notice on first page

PRELIMINARY

Hardware architecture

TPU
shelf components
...................................................................................................................................................................................................................................
Introduction

The major components of the Traffic Processing Unit (TPU) shelf consists of standard
chassis equipment and RNC-specific components.
Standard chassis components

Standard chassis components includes:

Alarm cards (see Alarm card (p. 3-26))

Ethernet switch cards (see Ethernet switch card (p. 3-27))
fan trays (see Chassis fan trays (p. 3-24)),

power trays (see Power trays (p. 3-22))

RNC-specific components

The RNC-specific components of the TPU shelf are:

GICC cards (see GICC cards (p. 3-33))

CICC cards (see CICC cards (p. 3-37))
Blade-PCF cards (see Solaris B-PCF (p. 3-39))

Minimum configuration

PRELIMINARY

The minimum TPU shelf card configuration for the two shelves is shown in Figure
3-21, Minimum TPU shelf configuration (p. 3-31).

3-30

TPU shelf components

Figure 3-21 Minimum TPU shelf configuration

PRELIMINARY

Hardware architecture

The GICC cards (slot 3) provide the TPU Shelf Controller (SC) function.
Maximum configuration

The maximum TPU shelf card configuration for the two shelves is shown in Figure
3-22, Maximum TPU Shelf Configuration (p. 3-32).

PRELIMINARY

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
3-31
Issue 14, September 2009
See notice on first page

PRELIMINARY

Hardware architecture

TPU shelf components

Figure 3-22 Maximum TPU Shelf Configuration

GICC and CICC population rules

PRELIMINARY

The GICC cards are grown in pairs starting with slot 20, then slot 4, and finally slot
19. For CICC cards (also grown in pairs) the growth pattern alternates outwardly from
the center of the shelf starting at slot 11, then slot 13, slot 10, slot 14, and so on.

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

3-32

GICC
cards
...................................................................................................................................................................................................................................
Introduction

The Gateway Intelligent Carrier Card ( GICC) blade is a network processor-based,

high-speed protocol processing card.

PRELIMINARY

Hardware architecture

Figure

Figure 3-23, Non-optical ethernet GICC (1.0) card (p. 3-33) shows a view of the
non-optical ethernet GICC (1.0) card used in the TPU shelf. Figure 3-24, Optical
ethernet GICC (1.1) card (p. 3-34) shows a view of the optical ethernet GICC (1.1)
card also used in the TPU shelf.
Figure 3-23 Non-optical ethernet GICC (1.0) card

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
3-33
Issue 14, September 2009
See notice on first page

PRELIMINARY

Hardware architecture

GICC cards

Figure 3-24 Optical ethernet GICC (1.1) card

Functions

The primary function of the GICC is to manage IP and ATM processing. It supports
AAL5/ATM and IP/GigE. Its current overall throughput for RNC application is around
600 Mbps bi-directional.
The main components for:

PRELIMINARY

Non-optical ethernet GICC (1.0) card:

One console serial port

Two copper-based Gigabit Ethernet (GigE) ports

Four OC-3/STM ports (only the bottom two ports can be used)

Optical ethernet GICC (1.1) card:

One console serial port

One copper-based Gigabit Ethernet (GigE) port (not operational)

Two optical Gigabit Ethernet (GigE) ports

Two OC-3/STM ports

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

3-34

GICC cards

See also Table 3-4, GICC Services (p. 3-35) for a comparison of the two GICC
types.
Table 3-4

GICC Services

Services

Non-Optical Ethernet GICC

Optical Ethernet GICC

IP Back Haul

Yes

IP Soft Handoff (future)

Yes

A8/A9

Yes

A10/A11

Yes

External Electrical
Ethernet Capability

Yes

External Optical
Ethernet Capability

Yes (GigE)

PRELIMINARY

Hardware architecture

OC3 ports

OC3 ports are directly connected into the network processor. OC3 ports are used for
RNC backhaul connections and RNC sidehaul (that is, SHO universe) connections.
AAL5/ATM/OC-3c is the low-level transport protocol stack in the backhaul and in the
sidehaul.
GigE ports

GigE ports are inter-connected by a Broadcom Switching Chip. C5 network processor

is both IP engine and ATM engine. It supports AAL5/ATM and IP/GIGE. Its current
overall throughput for RNC application is around 600 Mbps bi-directional.
The optical GigE switch/router ports should be configured as follows:

auto-negotiation should be disabled

flow control should be disabled

full duplex should be configured

data rate should be set to 1G.

Single and multi-mode

Both OC3 and GigE ports can be Single-Mode Fiber (SMF) or Multi-Mode Fiber
(MMF), duplex or simplex, and crimp (ST) or push-pull coupling (SC).
Host processor

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
3-35
Issue 14, September 2009
See notice on first page

PRELIMINARY

The Host Processor is a management entity for the GICC. Any OA&M event in the
network processor or on the I/O links will cause network processor send an exceptional
event to the host processor.

PRELIMINARY
PRELIMINARY

Hardware architecture

GICC cards

OA&M Monitoring

The GICC faceplatef includes the standard cPSB blue hot swap LED, two
software-programmable status LEDs. There is one programmable LED and one signal
detect LED per OC-3/STM1 port.
References

See Appendix A, Controls and indicators. for details on GICC LEDs and controls.

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

3-36

CICC
cards
...................................................................................................................................................................................................................................
Introduction

The Common Intelligent Carrier Card ( CICC) blade (Figure 3-25, CICC card
(p. 3-37))provides general purpose processing power for application software modules
that are compute-intensive and required Ethernet I/O.

PRELIMINARY

Hardware architecture

Figure 3-25 CICC card

Functions

Each CICC card has two GIGE backplane links and one 100base-T Ethernet port at the
faceplate.
Processors

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
3-37
Issue 14, September 2009
See notice on first page

PRELIMINARY

Two of the three internal processors have one GIGE port on each of them. The
remaining one processor is the board master, which has two GIGE ports. It is used to
send Heartbeats over the active/standby backplane links to monitor the connectivity
over the backplane. It is also used to configure the switch chip on the card.

PRELIMINARY

Hardware architecture

CICC cards

Ports

The CICC includes three micro-DB9 serial console ports, one for each of the three
processors
OA&M Monitoring

A blue hot swap LED is provided, and a power/fault LED indicates when the onboard
power controller detects a problem with the local power.
References

PRELIMINARY

See Appendix A, Controls and indicators. for details on GICC LEDs.

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

3-38

Solaris
B-PCF
...................................................................................................................................................................................................................................
Introduction

The Solaris Blade-Packet Control Function (B-PCF) blade (Figure 3-26, Solaris
B-PCF (p. 3-39)) is a Sun Solaris Blade that has a single 650 MHz CP. Each blade
includes one SPARC IIe/IIi CPU and 512 MB RAM.

PRELIMINARY

Hardware architecture

Figure 3-26 Solaris B-PCF

Functions

Up to four B-PCFs are used per TPU shelf. Each B-PCF communicates with the
Ethernet Switch Card (ESC) in the same shelf. A separate VLAN is created on each
ESC to handle the signaling, bearer and OA&M traffic coming from and to the BPCF.
The SUN OS package on the B-PCF is Solaris 9. The B-PCF has a single Ethernet
interface - dmfe to handle A8/9, A10/A11 and OA&M traffic.
The blade backplane ports are 100 Base-T ports. Each B-PCF blade also has a serial
port at the front panel. However, this serial cable connector type is different from the
type of serial interfaces used on the GICC cards and CICC cards.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
3-39
Issue 14, September 2009
See notice on first page

PRELIMINARY

Backplane ports

PRELIMINARY

Hardware architecture

Solaris B-PCF

OA&M Functions

The following interfaces are used when performing OA&M procedures for the PCF:

TPU GUI and CLI

Secure Shell (SSH) access to the PCF.

The following LEDs are available on the B-PCF: an ALARM/USER LED and a
READY LED.
References

PRELIMINARY

See Appendix A, Controls and indicators. for details on B-PCF LEDs.

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

3-40

MM-AP Cabinet
Overview
...................................................................................................................................................................................................................................

PRELIMINARY

Hardware architecture

Purpose

This section describes the equipment that comprises the MM-AP cabinet.
Growth cabinets

Existing MM-AP growth cabinets ( see Figure 3-27, Typical MM-AP growth
frame/cabinet (p. 3-41)) can be used to house the servers that make up the RNC-AP
pairs and OAM Proxy AP pairs of the RNC. This assumes that there are at least two
free drawers (for either pair) in any under-utilized frame, and the frame is running all
MM-based applications.
Figure 3-27 Typical MM-AP growth frame/cabinet

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
3-41
Issue 14, September 2009
See notice on first page

PRELIMINARY

Otherwise, a new MM-AP growth cabinet is needed to house the RNC-related APs.

PRELIMINARY

Hardware architecture

Overview

Important! Starting in Release 30.0 and beyond, new MM-AP growth will be
provided by means of the Universal Cabinet (UNC). The UNC design supports site
installations in standard equipment aisles, with both front and rear maintenance
access, and in locations where rear cabinet access is totally restricted.
MM -AP cabinet configuration

For specific details regarding the configuration details of an MM-AP cabinet, refer to
401-710-201 (Mobility Manager Application Processor Cluster Operations,
Administration, and Maintenance).
Server types

Two types of server types, as follows, are available for use in RNC-APs and OAM
Proxy AP applications:

400S server

410S server

PRELIMINARY

Contents
RNC-AP (400S server)

3-43

RNC-AP (410S server)

3-47

OAM proxy AP (400S server)

3-50

OAM proxy AP (410S server)

3-53

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

3-42

RNC-AP
(400S server)
...................................................................................................................................................................................................................................
Introduction

Each RNC (up to 15 per system) requires one RNC-AP pair.

400s servers

PRELIMINARY

Hardware architecture

The RNC-AP (Figure 3-28, RNC-AP 400S Server (p. 3-43)) is a 400S server that
operates as an active/standby pair.
Figure 3-28 RNC-AP 400S Server

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
3-43
Issue 14, September 2009
See notice on first page

PRELIMINARY

Hardware architecture

RNC-AP (400S server)

Two main application processes

The RNC-AP hosts two main application processes, the Traffic Control Server (TCS)
process and the RNC-Manager (RNC-M) process. Both are Virtual Clusters and Virtual
Machines (VCVM).
Main functions

The main functions of the TCS process include FS/RLP resource management, traffic
load balancing and RNC system-level status monitoring.
The main functions of the RNC-M process include RNC provisioning interfaces, TPU
Manager, RNC Integrity Monitor, fault reporting processes, and functions to interface
with MSC existing OA&M infrastructure.
Configuration

PRELIMINARY

Figure 3-29, Hardware Configuration for RNC-AP 400S pairs (p. 3-45) provides
details of the RNC-AP pair connections. In this example, the gray boxes represent
other potential APs (which could also be an OAM Proxy pair). Therefore, RNC-AP
pairs can coexist with other MM-APs in the same growth cabinet.

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

3-44

RNC-AP (400S server)

Figure 3-29 Hardware Configuration for RNC-AP 400S pairs

PRELIMINARY

Hardware architecture

As with all MM-APs, the RNC-AP pairs require an EIN connection to interconnect
with the legacy ring and ECP.
RNC-AP 400S server hardware

Each RNC-AP 400S server provides the following hardware:

one alarm card

one hard disk (boot drive)

one Host CPU card

two combo cards

one system controller board

two fan trays

one system status panel

one power supply

For specifics regarding 400S server hardware and replacement, refer to 401-710-201.
....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
3-45
Issue 14, September 2009
See notice on first page

PRELIMINARY

PRELIMINARY
PRELIMINARY

Hardware architecture

RNC-AP (400S server)

Population guidelines for RNC-AP

The following are specific guidelines for populating an RNC-AP in an MM-AP growth
frame:

There should be at least two server drawers available in a MM-AP cabinet. The
two server drawers should be on different power fault groups. For example, server
in the upper shelf is on power fault group A, and server in the lower shelf is on
power fault group B.

An RNC-AP pair should be deployed based on the AP frame/drawer-pairing rule.

Server Drawer 1 and Server Drawer 2 are paired. Server Drawer 3 and Server
Drawer 4, and so on.

Following multiple application population rules, an RNC-AP should be in the same

RCC cluster as the MM applications.

The two Ethernet Ports on an RNC-AP, used for 1X RNC internal call processing
and 1X RNC internal LAN communications, should be physically isolated from
other Ethernet ports that are used for MSC Server-to-Server communications and
for connections on the IMS/CNI ring.

If a new MM-AP growth frame is required and if RNC-APs are the first pair of
APs in the new frame, this pair of RNC-APs should be in server drawers 1 and 2.
This is because frame level Alarm contacts are provided by the first pair of APs in
an FMS growth frame.

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

3-46

RNC-AP
(410S server)
...................................................................................................................................................................................................................................
Introduction

Each RNC (up to 15 per system) requires one RNC-AP pair.

410S servers

PRELIMINARY

Hardware architecture

The RNC-AP (Figure 3-30, RNC-AP 410S Server (p. 3-47)) is a 410S server that
operates as an active/standby pair.
Figure 3-30 RNC-AP 410S Server

Notes:
1. This slot can be occupied by a combo card, or a carrier card.
2. For a combo card this port is qfe1. For a carrier card this port is pro5.
3. For a combo card this port is qfe0. For a carrier card this port is pro4.
Two main application processes

The RNC-AP hosts two main application processes, the Traffic Control Server (TCS)
process and the RNC-Manager (RNC-M) process. Both are Virtual Clusters and Virtual
Machines (VCVM).
Main functions

The main functions of the RNC-M process include RNC provisioning interfaces, TPU
Manager, RNC Integrity Monitor, fault reporting processes, and functions to interface
with MSC existing OA&M infrastructure.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
3-47
Issue 14, September 2009
See notice on first page

PRELIMINARY

The main functions of the TCS process include FS/RLP resource management, traffic
load balancing and RNC system-level status monitoring.

PRELIMINARY

Hardware architecture

RNC-AP (410S server)

Configuration

Figure 3-31, Hardware Configuration for RNC-AP 410S pairs (p. 3-48) provides
details of the RNC-AP pair connections. In this example, the gray boxes represent
other potential APs (which could also be an OAM Proxy pair). Therefore, RNC-AP
pairs can coexist with other MM-APs in the same growth cabinet.
Figure 3-31 Hardware Configuration for RNC-AP 410S pairs

As with all MM-APs, the RNC-AP pairs require an EIN connection to interconnect
with the legacy ring and ECP.

PRELIMINARY

RNC-AP 410S server hardware

Each RNC-AP 410S server provides the following hardware:

one alarm card

one hard disk (boot drive)

1 host CPU card configured with 4-port Ethernet PMC

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

3-48

RNC-AP (410S server)

one Ethernet combo, or carrier card that provides the EIN interface for RNC-AP
applications on the CPU card.

one system controller board

two fan trays

one system status panel

one power supply.

PRELIMINARY

Hardware architecture

For specifics regarding 410S server hardware and replacement, refer to 401-710-201.
Population guidelines for RNC-AP

The following are specific guidelines for populating an RNC-AP in an MM-AP growth
frame:

An RNC-AP pair should be deployed based on the AP frame/drawer-pairing rule.

Server Drawer 1 and Server Drawer 2 are paired. Server Drawer 3 and Server
Drawer 4, and so on.

Following multiple application population rules, an RNC-AP should be in the same

RCC cluster as the MM applications.

PRELIMINARY

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
3-49
Issue 14, September 2009
See notice on first page

PRELIMINARY

Hardware architecture

OAM
proxy AP (400S server)
...................................................................................................................................................................................................................................
Introduction

One OAM Proxy AP pair is required to serve from 1 to 15 RNCs.

400S server

The OAM proxy AP (Figure 3-32, OAM Proxy AP 400S Server (p. 3-50)) is a 400S
server that operates as an active/standby pair.

PRELIMINARY

Figure 3-32 OAM Proxy AP 400S Server

3-50

OAM proxy AP (400S server)

Primary purpose

The primary purpose of the OAM Proxy AP pairs is to serve for the TPU-GUI and
RNC Database (DB). Each of these functionalities is a VCVM that operates across the
OAM Proxy AP pair.
TPU -GUI and RNC Database

PRELIMINARY

Hardware architecture

As seen in Figure 3-33, Provisioning and configuration architecture (p. 3-51), the
TPU-GUI and the RNC DB reside on the OAM proxy AP.
Figure 3-33 Provisioning and configuration architecture

Because the addition of more RNCs does not require the addition of more OAM proxy
APs, the same TPU-GUI and RNCDB serve all the RNCs in the system, and thus
provide for secure access.

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
3-51
Issue 14, September 2009
See notice on first page

PRELIMINARY

Note that the OAM Proxy AP contains a firewall to protect the AP from the customers
user LAN.

PRELIMINARY

Hardware architecture

OAM proxy AP (400S server)

Configuration

OAM Proxy AP pairs can coexist with other MM-APs in the same growth cabinet. As
with all MM-APs, the OAM Proxy AP pairs require an EIN connection to interconnect
with the legacy ring and ECP.
OAM proxy AP 400S server hardware

Each OAM proxy AP 400S server provides the following hardware:

one alarm card

one hard disk (boot drive)

one host CPU card

one unused T1 card

one combo card

one system controller board

two fan trays

one system status panel

one power supply

PRELIMINARY

For specifics regarding 410S server hardware and replacement, refer to 401-710-201.

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

3-52

OAM
proxy AP (410S server)
...................................................................................................................................................................................................................................
Introduction

One OAM Proxy AP pair is required to serve from 1 to 15 RNCs.Each RNC (up to 15
per system) requires one RNC-AP pair.

PRELIMINARY

Hardware architecture

410S servers

The OAM proxy AP (Figure 3-34, OAM Proxy AP 410S Server (p. 3-53)) is a 410S
server that operates as an active/standby pair.
Figure 3-34 OAM Proxy AP 410S Server

Notes:
1. This slot can be occupied by a combo card, or a carrier card.
2. For a combo card this port is qfe1. For a carrier card this port is pro5.
Primary purpose

The primary purpose of the OAM Proxy AP pairs is to server for the TPU-GUI and
RNC Database (DB). Each of these functionalities is a VCVM that operates across the
OAM Proxy AP pair.
TPU-GUI and RNC Database

The main functions of the TCS process include FS/RLP resource management, traffic
load balancing and RNC system-level status monitoring.

Because the addition of more RNCs does not require the addition of more OAM proxy
APs, the same TPU-GUI and RNCDB serve all the RNCs in the system, and thus
provide for secure access.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
3-53
Issue 14, September 2009
See notice on first page

PRELIMINARY

As seen in Figure 3-33, Provisioning and configuration architecture (p. 3-51), the
TPU-GUI and the RNC DB reside on the OAM proxy AP.

PRELIMINARY

Hardware architecture

OAM proxy AP (410S server)

Note that the OAM Proxy AP contains a firewall to protect the AP from the customers
user LAN.
Configuration

Only one pair of OAM Proxy-AP servers is required per MSC. OAM Proxy AP pairs
can coexist with other MM-APs in the same growth cabinet.
As with all MM-APs, the OAM Proxy AP pairs require an EIN connection to
interconnect with the legacy ring and ECP.
OAM proxy AP 410S server hardware

Each OAM proxy AP 410S server provides the following hardware:

one alarm card

one hard disk (boot drive)

one host CPU card with Ethernet PMC and two Ethernet interfaces
one combo, or carrier card

one system controller board

two fan trays

one system status panel

one power supply

PRELIMINARY

For specifics regarding 410S server hardware and replacement, refer to 401-710-201.

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

3-54

PRELIMINARY

4O A&M Architecture

This chapter describes the OA&M architecture associated with the CDMA 1X RNC.
Contents
Executive Cellular Processor (ECP)

4-2

Operations and Management Platform (OMP)

4-4

Element Management System (EMS)

4-8

Command Line Interface (CLI)

4-27

Input/Output Messages

4-28

UNIX command interface

4-37

RNC logs

4-38

Recent Change and Verify (RC/V)

4-39

Status Display Pages (SDPs)

4-40

RNC alarms

4-41

Service measurements

4-43

Read-Only Printer (ROP)

4-44

Operations and Maintenance Center Radio Access Network (OMC-RAN)

4-45

To enable/disable OMC-RAN

4-49

Local Maintenance Terminal (LMT)

4-56

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
4-1
Issue 14, September 2009
See notice on first page

PRELIMINARY

OA&M Architecture

Executive
Cellular Processor (ECP)
...................................................................................................................................................................................................................................
Introduction

The Executive Cellular Processor (ECP) provided the original OA&M interface for the
AUTOPLEX System 1000. With the evolution of that system, the everyday OA&M
interface functions have evolved over to the:

Operations and Management Platform (OMP), also see Operations and

Management Platform (OMP) (p. 4-4)

Operations and Maintenance Center Radio Access Network (OMC-RAN), also see
Operations and Maintenance Center Radio Access Network (OMC-RAN)
(p. 4-45).

Software Updates (SUs) and generic retrofits

After the implementation of RNC hardware and software into an existing System,
future SUs and generic retrofits will require that the ECP be updated for as long as it
remains a functioning system element.
Migrated OA&M functions

Migrated ECP Recent Change/Verify (RC/V) and SDP OA&M functions will be
performed at the OMP via connection to the appropriate designated MM-AP.
Resident OA&M functions

If still resident on the ECP, Status Display Page (SDP) functions will be performed
directly on the ECP, or at the OMP via connection to the ECP. See also 401-610-160
for specifics on performing OA&M functions at the ECP.
Technician Interface (TI)

Technician Interface (TI) is the legacy Command Line Interface (CLI) on the ECP.
Mobility Manager Technician Interface

PRELIMINARY

The Mobility Manager Technician Interface (MM-TI) feature moves input

command-request handling (TI commands) from the legacy CLI on the ECP to the
MM-AP.
TI command execution is accomplished from a new CLI (accessible from the OMP)
called Technician Interface CLI (TICLI). See also TI commands (p. 4-3).
When theMM-TI feature is enabled, migrated legacy commands can only be executed
from the TICLI. Attempting to execute a migrated command from the ECP craft shell
will generate an error directing the user to use the TICLI.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

4-2

Executive Cellular Processor (ECP)

TI commands

The TI commands listed in Table 4-1, TI Commands (p. 4-3) have been provided or
modified to include RNC. Note these commands are executable via the TICLI.
Table 4-1

TI Commands

RNC Status Command

OP:RNC [a]

Request the status of an RNC.

OP:RNCDB

Requests a list of all RNC application database

backup files for a specified RNC.

OP:RNC-BHSSTAT

Requests the status of all Backhaul Servers

(BHSs) at the Radio Network Controller
(RNC).

PRELIMINARY

OA&M Architecture

RNC Alarm Command

OP:ALARM

Request all system alarms including RNC and

TPU alarms.

Hardware Call Trace Commands

OP:DN
OP:IMSI
OP:MIN

Initiate a hardware call trace of a data mobile

call via use of a mobiles Directory Number
(DN), International Mobile Station Identity
(IMSI), or Mobile Identification Number
(MIN).

RC/V Database Commands

BKUP:DATABASE

Requests the master copy of the specified

database be backed up to disk in the dbbackup
directory.

COPY:DB

Overwrites the master copy of a database with

the backup copy.

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
4-3
Issue 14, September 2009
See notice on first page

PRELIMINARY

OA&M Architecture

Operations
and Management Platform (OMP)
...................................................................................................................................................................................................................................
Introduction

The Operations and Management Platform (OMP) provides OA&M capabilities for all
the Alcatel-Lucent CDMA Network related products.
Administration and maintenance

The OMP (Figure 4-1, OMP System Architecture (p. 4-4)) is essentially an adjunct
system that provides terminal support and off-line processing to facilitate administrative
and maintenance tasks on all RNC-related system elements as well as the RNC.

PRELIMINARY

Figure 4-1 OMP System Architecture

4-4

Operations and Management Platform (OMP)

For more detailed information regarding OMP OA&M equipment, interfaces, and tasks,
refer to 401-662-102.
ECP and 5ESS legacy interface

The OMP provides technician access to the ECP and 5ESS through various types of
terminals, and a multi-windowing interface.

PRELIMINARY

OA&M Architecture

ECP connection

Connection between the OMP and ECP (Figure 4-2, ECP Maintenance and
Administrative Access (p. 4-5)) is accomplished through the Network Terminal Server
(NTS) and over the Dual Serial Channel Computer Interconnect (DCI) link.
Figure 4-2 ECP Maintenance and Administrative Access

Terminal sessions and connections provided through the Network Terminal Server
(NTS) are listed as follows:
Up to seven Control and Display Terminal (CDT) sessions.

One ECP Maintenance CRT (MCRT), including Emergency Action Interface (EAI).
One ECP physical ROP connection.

Terminal sessions and connections provided over the DCI link are listed as follows:

Up to eight CDT sessions.

Up to 23 Virtual TTY sessions

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
4-5
Issue 14, September 2009
See notice on first page

PRELIMINARY

OA&M Architecture

Operations and Management Platform (OMP)

Up to 12 OMP Recent Change and Verify (RC/V) sessions.

Up to three ECP ROP monitors

5ESS connection

Connection between the OMP and 5ESS (Figure 4-3, 5ESS Switch Maintenance and
Administration Access (p. 4-6)) is accomplished through the NTS.
Figure 4-3 5ESS Switch Maintenance and Administration Access

The following terminal sessions are supported:

One 5ESS switch EAI MCRT terminal

One 5ESS switch ROP session

One 5ESS switch traffic channel (TRFC) session

Up to eight 5ESS switch RC/V terminal sessions

Up to eight 5ESS switch Supplementary Trunk Line Workstations (STLWSs)

sessions

PRELIMINARY

Terminal choices

The following four types of terminals are used to provide user access at the OMP:

The OMP system console for UNIX administration

Personal computers (PCs) running VT-100 terminal emulation software for

accessing network elements

4-6

Operations and Management Platform (OMP)

X Window System terminals (referred to as X-Terminals)

Text terminals (ANSI X3.64 compatible)

OMP system console

All OMP functions can be accessed from the OMP system console, using multiple
windows to run simultaneous sessions. The OMP system console is a SUN Workstation
running X (from the associated OMP),

PRELIMINARY

OA&M Architecture

Personal computers

All OMP functions can be accessed from a PC running an X-software package (for
example, Hummingbird Exceed), using multiple windows to run simultaneous sessions.
X-terminals

All OMP functions can be accessed from X-terminals, using multiple windows to run
simultaneous sessions. An X-terminal may also be more convenient for some OMP
administration and maintenance tasks.
Text terminals

Text (ASCII) terminals provide access only to character-based System 1000 functions.
Therefore, text terminals are unable to execute X-related functions such as:

Solaris applications for technicians such as mailtool, file manager, and printtool.
Solaris applications for administrators such as admintool, perfmeter, and tapetool.

OMP manual pages (xman)

CDMA Networks CD-ROM documentation

ROP Log Archives

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
4-7
Issue 14, September 2009
See notice on first page

PRELIMINARY

OA&M Architecture

Element
Management System (EMS)
...................................................................................................................................................................................................................................
Introduction

The EMS was designed to serve as the primary interface for performing OA&M on
RNC network components.
Network elements

Essentially, the EMS presents technicians with a view of the network elements that it
oversees and of the applications that run within those elements.
It also provides technicians with the ability to perform maintenance operations on those
elements and applications. In summary, it helps technicians manage the network under
their control.
EMS GUI

The EMS provides a web-based GUI for element management and is based on industry
standard network management systems.

PRELIMINARY

The EMS GUI allows system users to monitor and control the maintenance and alarm
states of an RNC-AP and OAM Proxy AP and their managed resources. The following
table provides a list and description of all the related screens available through the
EMS GUI.
Table 4-2

RNC-AP and OAM Proxy AP-Related Screens

EMS GUI
Page

Provides. . .

With Navigation to. . .

1X RNCs
Summary
Page

The location,
maintenance
states, and any
associated alarms
for the network
elements
(RNC-APs, and
TPUs).

The following:

AP Status Page via Network Elements and

Maintenance States table (click on AP)

Alarms Page

OMP Web Main

TPU-GUI via Network Elements and Maintenance

States table (click on RNC TPU)

4-8

Element Management System (EMS)

Table 4-2

RNC-AP and OAM Proxy AP-Related Screens (continued)

EMS GUI
Page

Provides. . .

With Navigation to. . .

AP Status
Page with
1X RNC
(RNCAP)

EIN/LAN status,
and the GUI
equivalent for the
following input
commands:

The following:

1X
RNCRNCM
Status
Page

Commit/Select
AP platform
version

Restore/
Remove AP

Report:
AP status
AP active
alarms
AP
commands
AP
software
version

Switchover/
Initialize AP

TCS Status Page

RNCM Status Page

OMP Web Main

Alarms Page

1X RNCs Summary Page

Status for the

RNCM, and the
GUI equivalent
for the following
input commands:

The following:

Restore/
Remove
RNCM

Switchback
RNCM

AP Status Page

OMP Web Main

Alarms Page

1X RNCs Summary Page

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
4-9
Issue 14, September 2009
See notice on first page

PRELIMINARY

OA&M Architecture

PRELIMINARY

OA&M Architecture

Table 4-2

RNC-AP and OAM Proxy AP-Related Screens (continued)

EMS GUI
Page

Provides. . .

With Navigation to. . .

TCS
Status
Page

Status for the

TCS, and the GUI
equivalent for the
following input
commands:

The following:

Restore/
Remove TCS

Switchback
TCS

Run TCS
Audit

Allow/Inhibit
TCS Audits

AP Status
Page with
RNCDBMS
and TPU
GUI
(OAM
Proxy)

PRELIMINARY

Element Management System (EMS)

AP Status Page

OMP Web Main

Alarms Page

1X RNCs Summary Page

EIN/LAN status,
and the GUI
equivalent for the
following input
commands:

The following:

Commit/Select
AP platform
version

Restore/
Remove AP

Report:
AP status
AP active
alarms
AP
commands
AP
software
version

Switchover/
Initialize AP

TPU GUI Status Page

RNCDBMS Status Page

OMP Web Main

Alarms Page

APs

4-10

Element Management System (EMS)

Table 4-2

RNC-AP and OAM Proxy AP-Related Screens (continued)

EMS GUI
Page

Provides. . .

With Navigation to. . .

1X
RNCRNCDBMS
Status
Page

Status for the

RNCM, and the
GUI equivalent
for the following
input commands:

The following:

Restore/
Remove
RNCDBMS

Switchback
RNCDBMS

1X RNC
TPUGUI

AP Status Page

OMP Web Main

Alarms Page

APs

Status for the

TPU GUI, and the
GUI equivalent
for the following
input commands:

The following:

Restore/
Remove TPU
GUI

Switchback
TPU GUI

AP Status Page

OMP Web Main

Alarms Page

APs

PRELIMINARY

OA&M Architecture

TPU GUI

The TPU GUI provides the primary interface for the TPU shelf of the RNC. Main
functionality includes TPU Configuration Management, TPU Alarm Viewing, and
TMN-based TPU fault management.
The following tables provide a list and description of all the applicable TPU-related
screens available through the TPU GUI.
Table 4-3

1X RNC TPU page

With Navigation to. . .

Configuration
Data icon

RNC Configuration Data page

Installation &
Software Updates
icon

Installation Options page

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
4-11
Issue 14, September 2009
See notice on first page

PRELIMINARY

Displayed Icon

PRELIMINARY

OA&M Architecture

Table 4-3

Element Management System (EMS)

1X RNC TPU page

(continued)

Displayed Icon

With Navigation to. . .

Network Elements
icon

Traffic Processing Unit (TPU) page

Alarms icon

Alarms page

BPCFs icon

Blade Packet Control Functions (BPCFs) page

Admin button

Admin page

Change Password
buton

Change Password page

Logout

Table 4-4

Link from Configuration Data icon

TPU GUI
Page

Displayed With the

Icon
associated . .
.

Which has screen buttons for accessing.

RNC
Configuration
Data

RNC
Dynamic
Data

The following:

RNC
Configuration
Data

PRELIMINARY

RNC
Configuration
Data

RNC
Dynamic
Data

1X RNC
information

OMP Web Main

TPU Web Main

1X RNCs Summary Page

information
page.

Global Configuration Data

Logout

Static Route

The following:

link for
connecting to
the Static
Route page.

OMP Web Main

TPU Web Main

1X RNCs Summary Page

Global Configuration Data

Logout

link for
connecting to
the 1X RNC

PSU VCC
Override link

The following:

OMP Web Main

TPU Web Main

VCC Override

1X RNCs Summary Page

page.

Global Configuration Data

Logout

for connecting
to the PSU

4-12

Element Management System (EMS)

Table 4-4

Link from Configuration Data icon (continued)

TPU GUI
Page

Displayed With the

Icon
associated . .
.

Which has screen buttons for accessing.

RNC
Configuration
Data

RNC
Dynamic
Data

The following:

BHS Level
IPBH
Parameters

link for
connecting to
the BHS Level

OMP Web Main

TPU Web Main

1X RNCs Summary Page

Logout

PRELIMINARY

OA&M Architecture

IPBH
Parameters

page.
RNC
Configuration
Data

RNC
Dynamic
Data

RNC Level
IPBH
Parameters

link for
connecting to
the RNC Level

The following:

OMP Web Main

TPU Web Main

1X RNCs Summary Page

Logout

IPBH
Parameters

page.
RNC
Configuration
Data

RNC
Dynamic
Data

Update
External IP
Address link

for connecting
to the External
IP Addresses

The following:

OMP Web Main

TPU Web Main

1X RNCs Summary Page

Logout

page.
RNC
Configuration
Data

RNC
Dynamic
Data

SD and SF
BER

Thresholds link
for connecting
to the SD and
SF BER
Thresholds

The following:

OMP Web Main

TPU Web Main

1X RNCs Summary Page

Logout

page.

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
4-13
Issue 14, September 2009
See notice on first page

PRELIMINARY

OA&M Architecture

Element Management System (EMS)

Table 4-4

Link from Configuration Data icon (continued)

TPU GUI
Page

Displayed With the

Icon
associated . .
.

Which has screen buttons for accessing.

RNC
Configuration
Data

RNC
Dynamic
Data

The following:

RNC Fault
Management
Parameters

link for
connecting to
the RNC Fault
Management
Parameters

OMP Web Main

TPU Web Main

1X RNCs Summary Page

Global Configuration Data

Logout

page.
RNC
Configuration
Data

RNC
Dynamic
Data

RNC Level
IPSHO
Parameters

link for
connecting to
the RNC Level
IPSHO
Parameters

The following:

OMP Web Main

TPU Web Main

1X RNCs Summary Page

Global Configuration Data

Logout

page.
RNC
Configuration
Data

RNC
Dynamic
Data

IPSHO Fault
Management
Parameters
and IP
Addresses link

The following:

for connecting
to the IPSHO

OMP Web Main

TPU Web Main

1X RNCs Summary Page

Global Configuration Data

Logout

Fault
Management
Parameters
and IP
Addresses

PRELIMINARY

page.

4-14

Element Management System (EMS)

Table 4-4

Link from Configuration Data icon (continued)

TPU GUI
Page

Displayed With the

Icon
associated . .
.

Which has screen buttons for accessing.

RNC
Configuration
Data

RNC
Dynamic
Data

The following:

IPSHO Local
CA Parameters

and IP
Addresses link
for connecting
to the IPSHO
Local CA
Parameters

OMP Web Main

TPU Web Main

1X RNCs Summary Page

Global Configuration Data

Logout

PRELIMINARY

OA&M Architecture

page.
RNC
Configuration
Data

RNC
Dynamic
Data

Neighbor List
(RNC DB View)

and IP
Addresses link
for connecting
to the
Neighbor List
(RNC DB View)

The following:

OMP Web Main

TPU Web Main

1X RNCs Summary Page

Global Configuration Data

Logout

page.
RNC
Configuration
Data

RNC
Configuration
Data

RNC
Dynamic
Data

Wizards

CA-IP Map
(RNC DB View)

and IP
Addresses link
for connecting
to the CA-IP

The following:

OMP Web Main

TPU Web Main

1X RNCs Summary Page

Global Configuration Data

Map (RNC DB
View) page.

Logout

5E GW
Growth/Degrowth link for

The following pages:

connecting to
the 5E GW
growth/
degrowth steps.

OMP Web Main

TPU Web Main

1X RNCs Summary Page

Logout

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
4-15
Issue 14, September 2009
See notice on first page

PRELIMINARY

OA&M Architecture

Table 4-4

Link from Configuration Data icon (continued)

TPU GUI
Page

Displayed With the

Icon
associated . .
.

Which has screen buttons for accessing.

RNC
Configuration
Data

Wizards

The following pages:

RNC
Configuration
Data

PRELIMINARY

Element Management System (EMS)

GICC
Growth/Degrowth link for

connecting to
the GICC
growth/
degrowth steps.
Wizards

Wizards

OMP Web Main

TPU Web Main

1X RNCs Summary Page

Logout

RNC De-growth

The following pages:

link for
connecting to
the RNC
degrowth steps.

OMP Web Main

TPU Web Main

1X RNCs Summary Page

Logout

APS Migration
Wizard link for

connecting to
the APS
Migration
steps.

The following pages:

OMP Web Main

TPU Web Main

1X RNCs Summary Page

Logout

4-16

Table 4-5

Element Management System (EMS)

Link from Installation & Software Updates icon

TPU GUI
Page

Which Provides. . .

With Screen buttons for accessing. . .

Installation
Options

The capability for

choosing software
bundle versions.

The following:

Displays for managed

resources, i.e.
SC-GICCS, and their
associated:

Application version

States

Alarms

Command status

OMP Web Main

TPU Web Main

1X RNCs Summary Page

Alarms Page

System Status (Network Elements) Page

Logout

PRELIMINARY

OA&M Architecture

Also, provides the

capability for inputting
TI commands.

Table 4-6

Link from Network Elements icon

TPU GUI
Page

Which Provides. . .

With Screen buttons and links for

accessing. . .

Traffic
Processing
Unit (TPU)

The capability for

filtering managed
resources, e.g., GICCs,
CICCs, B-PCFs, and
displays for their
associated:

The following:

OMP Web Main

TPU Web Main

1X RNCs Summary Page

Alarms

Application version

APS Status

States

BHS Info

Alarms

Neighbor List (IPSHO GICC View)

Command status

CA-IP Map (IPSHO GICC View)

Also, provides the

capability for inputting
TI commands.

CA-IP Con Status

Logout

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
4-17
Issue 14, September 2009
See notice on first page

PRELIMINARY

OA&M Architecture

Element Management System (EMS)

Table 4-7

Link from Alarms icon

TPU GUI
Page

Which Provides. . .

With Screen buttons for accessing. . .

Alarms

Displays for network

element alarm
information, as follows:

The following:

PRELIMINARY

Table 4-8

Managed resources,
e.g., GICCs, CICCs,
B-PCFs.

OMP Web Main

TPU Web Main

1X RNCs Summary Page

Network Element

Severity

Failed PVCs

Event time

Logout

Alarm details

Link from BPCFs icon

TPU GUI
Page

Displayed
Icon

With
Navigation
to. . .

Which has screen buttons for

accessing. . .

Blade
Packet
Control
Functions
(BPCFs)

BPCF
Configuration Data

The

The following:

Configure
BPCFs

OMP Web Main

TPU Web Main

1X RNCs Summary Page

Logout

page.

Blade
Packet
Control
Functions
(BPCFs)

Network
Elements

The Traffic Processing Unit (TPU) page.

Blade
Packet
Control
Functions
(BPCFs)

Alarms

The Alarms page.

4-18

Table 4-8

Element Management System (EMS)

Link from BPCFs icon (continued)

TPU GUI
Page

Displayed
Icon

With
Navigation
to. . .

Which has screen buttons for

accessing. . .

Blade
Packet
Control
Functions
(BPCFs)

Performance Data

The BPCF
Performance
Statistics

The following:

Blade
Packet
Control
Functions
(BPCFs)

page.

View All
BPCFs

OMP Web Main

TPU Web Main

1X RNCs Summary Page

System Status (Network Elements) Page

Logout

The View

The following:

BPCFs

OMP Web Main

TPU Web Main

1X RNCs Summary Page

Logout

page.

Table 4-9

Link from Admin button

TPU GUI
Page

With navigation to. . .

With Screen buttons for accessing. . .

Admin

The User Mangement

page

The following:

Admin

TPU GUI Locks page

Activate Accounts page

OMP Web Main

TPU Web Main

1X RNCs Summary Page

Logout

PRELIMINARY

OA&M Architecture

The following:

OMP Web Main

TPU Web Main

1X RNCs Summary Page

Logout

The following:
OMP Web Main

TPU Web Main

1X RNCs Summary Page

Logout

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
4-19
Issue 14, September 2009
See notice on first page

PRELIMINARY

OA&M Architecture

Table 4-9

Link from Admin button

TPU GUI
Page

With navigation to. . .

With Screen buttons for accessing. . .

Admin

View EMS user accounts

synchronization status

The following:

page

Admin

PRELIMINARY

Element Management System (EMS)

Configure Far CA
Reachability page

(continued)

OMP Web Main

TPU Web Main

1X RNCs Summary Page

Logout

The following:

OMP Web Main

TPU Web Main

1X RNCs Summary Page

Logout

IPBH Audit Configuration

The following:

page

OMP Web Main

TPU Web Main

1X RNCs Summary Page

Logout

Table 4-10

Link from Change Password button

TPU GUI
Page

With navigation to. . .

With Screen buttons for accessing. . .

Change
Password

The Change Password

page

The following:

OMP Web Main

TPU Web Main

1X RNCs Summary Page

Logout

4-20

Element Management System (EMS)

Table 4-11

1X RNCs button link

TPU GUI
Page

Which Provides. . .

With Screen buttons for accessing. . .

1X RNC
Summary

An overview of the 1X
RNC-AP locations in the
MSC as well as the
maintenance state and
alarm state of each
RNC-AP and TPU.

The following:

OMP Web Main

Alarms Page

Logout

Table 4-12

Global ConfigData button link

TPU GUI
Page

Displayed
Icon

With the
associated .
..

Which has screen buttons for

accessing. . .

Global
Configuration Data

MSC Data

External PCF
Servers link

The following:

Global
Configuration Data

OMP Web Main

TPU Web Main

1X RNCs Summary Page

PCF Servers

Global Configuration Data

page.

Logout

PDSN
Configuration

The following:

for
connecting to
the External

MSC Data

link for
connecting to
the Configure
PDSNs page.
MSC Data

RNC Call
Processing
Parameters

link for
connecting to
the RNC Call
Processing
Parameters

OMP Web Main

TPU Web Main

1X RNCs Summary Page

Global Configuration Data

Logout

PRELIMINARY

OA&M Architecture

The following:

OMP Web Main

TPU Web Main

1X RNCs Summary Page

Global Configuration Data

Logout

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
4-21
Issue 14, September 2009
See notice on first page

PRELIMINARY

page.

PRELIMINARY

OA&M Architecture

Element Management System (EMS)

Table 4-12

Global ConfigData button link (continued)

TPU GUI
Page

Displayed
Icon

With the
associated .
..

Which has screen buttons for

accessing. . .

Global
Configuration Data

MSC Data

General RNC
Call
Processing
Status link

The following:

Global
Configuration Data

PSU SHO
Universe

OMP Web Main

TPU Web Main

for
connecting to
the Call

1X RNCs Summary Page

Global Configuration Data

Alarms Page

Processing
Status page.

Logout

PSU Subnet
& VPI
Configuration

The following:

link for
connecting to
the PSU
Subnet & VPI
Configuration

OMP Web Main

TPU Web Main

1X RNCs Summary Page

Global Configuration Data

Logout

page.
Global
Configuration Data

PSU SHO
Universe

Global IPSHO
Parameters

link for
connecting to
the Global
IPSHO
Parameters

The following:

OMP Web Main

TPU Web Main

1X RNCs Summary Page

Global Configuration Data

Logout

PRELIMINARY

page.

4-22

Element Management System (EMS)

Table 4-13

APS Status button link

TPU GUI
Page

Which Provides. . .

With Screen buttons for accessing. . .

APS Status

Specifics on the GICC

ATM status as regards to
port status, selector
status, role, etc.

The following:

Table 4-14

OMP Web Main

TPU Web Main

1X RNCs Summary Page

Network Element Page

Alarms Page

Logout

BHS Status link

TPU GUI
Page

Which Provides. . .

With Screen buttons for accessing. . .

BHS Statistics
Information

Specifics on the GICC Back

Haul Server (BHS) status as
regards to usage state,
loading status, UDP port
usage status, and BHA count.

The following:

Table 4-15

PRELIMINARY

OA&M Architecture

OMP Web Main

TPU Web Main

1X RNCs Summary Page

Network Element

Alarms Page

Logout

Neighbor List (IPSHO GICC View) link

TPU GUI
Page

Which Provides. . .

With Screen buttons and links for accessing. .

Neighbor List
(IPSHO GICC
View

Provides a view of all

neighbor list parameters
configured.

The following:
OMP Web Main

TPU Web Main

1X RNCs Summary Page

Neighbor List (RNC DB View

CA-IP Map (IPSHO GICC View)

CA-IP Map (RNC DB View)

CA-IP Con Status

Network Element

Logout

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
4-23
Issue 14, September 2009
See notice on first page

PRELIMINARY

OA&M Architecture

Element Management System (EMS)

Table 4-16
TPU GUI
Page

Which Provides. . .

With Screen buttons and links for accessing. .

CA-IP Map
(IPSHO GICC
View)

Provides a view of all CA-IP

map parameters configured.

The following:

Table 4-17

PRELIMINARY

CA-IP Map (IPSHO GICC View) link

OMP Web Main

TPU Web Main

1X RNCs Summary Page

CA-IP Map (RNC DB View)

Neighbor List (IPSHO GICC View)

Neighbor List (RNC DB View)

CA-IP Con Status

Network Element

Logout

CA-IP Con Status link

TPU GUI
Page

Which Provides. . .

With Screen buttons and links for accessing. .

CA-IP
Connectivity
Status

Provides a view of all

CA-IPs configured.

The following:

OMP Web Main

TPU Web Main

1X RNCs Summary Page

CA-IP Map (IPSHO GICC View)

Neighbor List (IPSHO GICC View)

Network Element

Logout

4-24

Element Management System (EMS)

Table 4-18

Neighbor List (RNC DB View) link

TPU GUI
Page

Which Provides. . .

With Screen buttons and links for accessing. .

Neighbor List
(RNC DB
View

Provides a view of all

neighbor list parameters
configured.

The following:

Table 4-19

OMP Web Main

TPU Web Main

1X RNCs Summary Page

Neighbor List (IPSHO GICC View)

CA-IP Map (IPSHO GICC View)

CA-IP Map (RNC DB View)

CA-IP Con Status

Logout

PRELIMINARY

OA&M Architecture

CA-IP Map (RNC DB View) link

TPU GUI
Page

Which Provides. . .

With Screen buttons and links for accessing. .

CA-IP Map
(RNC DB
View)

Provides a view of all CA-IP

map parameters configured.

The following:

OMP Web Main

TPU Web Main

1X RNCs Summary Page

CA-IP Map (IPSHO GICC View)

Neighbor List (IPSHO GICC View)

Neighbor List (RNC DB View)

CA-IP Con Status

Logout

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
4-25
Issue 14, September 2009
See notice on first page

PRELIMINARY
PRELIMINARY

OA&M Architecture

Element Management System (EMS)

Table 4-20

Failed PVCs button link

TPU
GUI
Page

Which
Provides. .
.

With Screen buttons for accessing. . .

Failed
PVCs
Status

A list of any
currently
existing
failed
Permanent
Virtual
Circuits
(PVCs).

The following:

OMP Web Main

TPU Web Main

1X RNCs Summary Page

Network Element

Alarms Page

Logout

4-26

Command
Line Interface (CLI)
...................................................................................................................................................................................................................................
Introduction

The RNC-APs and OAM Proxy APs have a Command Handler that allows commands
to be initiated from the MM-TICLI, or the OMC-RAN TICLI. Commands that are
specific to the RNC/TPU can be initiated either from the MM-TICLI, TPU CLI, and
(for the most part) OMC-RAN TICLI.

PRELIMINARY

OA&M Architecture

MM-TICLI

When the MM-TI feature is enabled, the MM-TICLI (a text-based command interface)
is accessible from the OMP, or any AP.
The MM-AP CLI previously used to execute AP commands is now eliminated with the
added benefit that once a system user logs into any AP and initiates MM-TICLI, the
user may now execute a command for any specific AP or RNC/TPU in the MSC that
they choose.
Important! RNC-TPU commands can only be executed on the MM-TICLI when
the MM-TICLI indicates that it supports TPU commands.
For accessing MM-TICLI see the following:

TICLI from the OMP, see Access via OMP (p. 6-19).
TICLI from any AP, see Access via direct login (p. 6-23).
Important! It is not a good practice to enter a large number of commands in quick
succession. You should wait for a response from the previous command before
entering the next command.

TPU CLI

The TPU CLI command mechanism can also be used for RNC-TPU specific
commands; however, all the commands that can be executed via TPU CLI can also be
executed via MM-TICLI.
OMC-RAN TICLI

The OMC-RAN TICLI is a set of TICLI interfaces that exist only on the OMC-RAN.
OMC-RAN TICLI and MM TICLI share the same functionality, and most of the same
TI message set.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
4-27
Issue 14, September 2009
See notice on first page

PRELIMINARY

For accessing OMC-RAN TICLI refer to 401-380-835, Alcatel-Lucent CDMA Network

Operations and Maintenance Center - Radio Access Network - Operations,
Administration, Maintenance, and Provisioning.

PRELIMINARY

OA&M Architecture

Input/Output
Messages
...................................................................................................................................................................................................................................
Introduction

All RNC/TPU, RNC-AP, and OAM Proxy AP related input messages, and output
messages are listed in alphabetical order in this section.
RNC-TPU input messages

PRELIMINARY

The RNC-TPU related input messages are listed in the following table. Note that
messages not executable via OMC-RAN CLI are flagged as no.
Command

MM-TICLI/TPU
CLI

OMC-RAN
TICLI

ALW:RNC-ABREVC

yes

ALW:RNC-CA

yes

ALW:RNC-TPU-DGN

yes

BKUP:RNCDB

yes

CLEAR:RNC-GICC

yes

COPY:RNCDB

yes

DELBKUP:RNCDB

yes

EXPORT:RNC-CONFIG

yes

GET:RNC-ABREVC

yes

GET:RNC-ALARM

yes

GET:RNC-BHS-INFO

yes

GET:RNC-BHS-STATE

yes

GET:RNC-CA2IPMAP

yes

GET:RNC-CAIPPM

yes

GET:RNC-GICC

yes

GET:RNC-GICC-INFO

yes

GET:RNC-GICC-STATE

yes

GET:RNC-INSTALL

yes

GET:RNC-INVENTORY

yes

GET:RNC-IPCON

yes

GET:RNC-NBRLST

yes

GET:RNC-PDSNLIST

yes

4-28

Input/Output Messages

MM-TICLI/TPU
CLI

OMC-RAN
TICLI

GET:RNC-PSPCF

yes

GET:RNC-SERVICE-INFO

yes

GET:RNC-STATUS

yes

GET:RNC-TPU-DGNRES

yes

GET:RNC-TPU-ETHERNET

yes

GET:RNC-TPU-FAILEDPVC

yes

GET:RNC-TPU-INFO

yes

GET:RNC-TPU INVENT

yes

GET:RNC-TPU-STATE

yes

GET:RNC-TPU-VER-CON

yes

GET:RNC-TPU-VERSION

yes

GET:RNC-VERSION

yes

HALT:RNC-TPU

yes

IMPORT:RNC-CONFIG

yes

INH:RNC-ABREVC

yes

INH:RNC-CA

yes

INH:RNC-TPU-DGN

yes

LOCKOUT:RNC-GICC

yes

LOCK:RNC-TPU

yes

QUERY:RNC-CA2IPMAP

yes

QUERY:RNC-NBRLST

yes

PING:RNC-TPU-GICC

yes

RESET:RNC-TPU

yes

SET:IPSHO

yes

SET:RNC-IPSHO

yes

SHUTDOWN:RNC-TPU

yes

SWITCH:RNC

yes

SWITCH:TOMATE-RNC-TPU

yes

TST:FARCAS-RNC-TPU

yes

TST:PSU-RNC

yes

TST:RNC-CA

yes

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
4-29
Issue 14, September 2009
See notice on first page

PRELIMINARY

Command

PRELIMINARY

OA&M Architecture

PRELIMINARY

OA&M Architecture

Input/Output Messages

Command

MM-TICLI/TPU
CLI

OMC-RAN
TICLI

TST:RNC-CA-SHOLNK

yes

UNLOCK:RNC-TPU

yes

UPD:RNC-CA2IPMAP

yes

UPD:RNC-NBRLST

yes

RNC-AP and OAM Proxy AP related input messages

All RNC-AP and OAM Proxy AP input messages are executable via MM-TICLI or
OMC-RAN CLI.

PRELIMINARY

The RNC-AP, and OAM Proxy AP related input messages are listed as follows:

ALW:TCS-AUD

AUD:TCS-NAME

COMMIT:AP

INH:TCS-AUD
INIT:AP

INSTALL:RNC-TPU

LOCK:RNC-TPU
OP:AP-ALARM

OP:AP-CMDS

OP:AP-INFO
OP:AP-STATUS

OP:AP-VERSION

OP:RNC
OP:RNCDB

RMV:AP

RMV:AP-RNCDBMS
RMV:AP-RNCM

RMV:AP-TCS

RMV:AP-TPUGUI
RST:AP

RST:AP-RNCDBMS

RST:AP-RNCM
RST:AP-TCS

4-30

Input/Output Messages

RST:AP-TPUGUI
SELECT:AP

SWITCHOVER:RNCDBMS

SWITCHOVER:RNCM
SWITCHOVER:TCS

SWITCHOVER:TPUGUI

PRELIMINARY

OA&M Architecture

RNC-TPU output messages

The RNC-TPU related output messages are listed in the following table. Note that
messages not reportable via OMC-RAN CLI are flagged as no.
MM-TICLI/TPU
CLI

OMC-RAN
TICLI

ALW-RNC-ABREVC

yes

ALW-RNC-CA

yes

ALW-RNC-TPU-DGN

yes

BKUP-RNCDB

yes

CLEAR-RNC-GICC

yes

COPY-RNCDB

yes

DELBKUP-RNCDB

yes

EXPORT-RNC-CONFIG

yes

GET-RNC-ABREVC

yes

GET-RNC-ALARM-SUM

yes

GET-RNC-BHS-INFO

yes

GET-RNC-BHS-STATE

yes

GET-RNC-CA2IPMAP

yes

GET-RNC-CAIPPM

yes

GET-RNC-GICC

yes

GET-RNC-GICC-INFO

yes

GET-RNC-GICC-STATE

yes

GET-RNC-INSTALL

yes

GET-RNC-INVENTORY

yes

GET-RNC-IPCON

yes

GET-RNC-NBRLST

yes

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
4-31
Issue 14, September 2009
See notice on first page

PRELIMINARY

Command

PRELIMINARY
PRELIMINARY

OA&M Architecture

Input/Output Messages

Command

MM-TICLI/TPU
CLI

OMC-RAN
TICLI

GET-RNC-PDSNLIST

yes

GET-RNC-PSPCF

yes

GET-RNC-SERVICE-INFO

yes

GET-RNC-STATUS

yes

GET-RNC-TPU-ALARM

yes

GET-RNC-TPU-DGNRES

yes

GET-RNC-TPU-ETHERNET

yes

GET-RNC-TPU-FAILEDPVC

yes

GET-RNC-TPU-INFO

yes

GET-RNC-TPU INVENT

yes

GET-RNC-TPU-STATE

yes

GET-RNC-TPU-VER-CON

yes

GET-RNC-TPU-VERSION

yes

GET-RNC-VERSION

yes

HALT-RNC-TPU

yes

IMPORT-RNC-CONFIG

yes

INH-RNC-ABREVC

yes

INH-RNC-CA

yes

INH-RNC-TPU-DGN

yes

LOCKOUT-RNC-GICC

yes

LOCK-RNC-TPU

yes

QUERY-RNC-CA2IPMAP

yes

QUERY-RNC-NBRLST

yes

PING-RNC-TPU-GICC

yes

RESET-RNC-TPU

yes

SET-IPSHO

yes

SET-RNC-IPSHO

yes

SHUTDOWN-RNC-TPU

yes

SWITCH-RNC

yes

SWITCH-TOMATE-RNC-TPU

yes

TST-FARCAS-RNC-TPU

yes

4-32

Input/Output Messages

Command

MM-TICLI/TPU
CLI

OMC-RAN
TICLI

TST-PSU-RNC

yes

TST-RNC-CA

yes

TST-RNC-CA-SHOLNK

yes

UNLOCK-RNC-TPU

yes

UPD-RNC-CA2IPMAP

yes

UPD-RNC-NBRLST

yes

PRELIMINARY

OA&M Architecture

RNC-AP and OAM Proxy AP related output messages

All RNC-AP and OAM Proxy AP output messages are reportable via MM-TICLI or
OMC-RAN CLI.
The RNC-AP, and OAM Proxy AP related output messages are listed as follows:
ALW-TCS-AUD
AUD-TCS-NAME

AUD-TCS-NAME-ERR

COMMIT-AP
INH-TCS-AUD

INIT-AP

LOCKOUT-RNC-GICC
LOCK-RNC-TPU

OP-ALARM

OP-AP-CMDS
OP-AP-INFO

OP-AP-STATUS

OP-AP-VERSION
OP-RNC

OP-RNCDB

OP-TCS AUD
RMV-AP

RMV-AP-RNCDBMS

RMV-AP-RNCM
RMV-AP-TCS

RST-AP-TPUGUI

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
4-33
Issue 14, September 2009
See notice on first page

PRELIMINARY

OA&M Architecture

Input/Output Messages

SELECT-AP
SWITCHOVER-AP

SWITCHOVER-RNCDBMS

SWITCHOVER-RNCM
SWITCHOVER-TCS

SWITCHOVER-TPUGUI

Note that with Release 30.0, the following commands and ROP reports are obsolete:

OP:RNC-TRKGRP

RMV:RNC-TRKGRP
RST:RNC-TRKGRP

TST:BTS-RNC

Report (REPT) output messages

All RNC related REPT output messages are reportable via MM-TICLI or OMC-RAN
CLI.

PRELIMINARY

The REPT output messages are listed as follows:

REPT-AP-RNCDBPP

REPT-AP-RNCDBSYNC

REPT-AP-RNCTPUALM
REPT-AP-RNCTPUATMALM

REPT-AP-RNCTPUETHALM

REPT-AP-RNCTPUFANALM
REPT-AP-RNCTPUFSBUSYALM

REPT-AP-RNCTPUFSOOSALM

REPT-AP-RNCTPUPOWERALM
REPT-AP-RNCTPUPPOOSALM

REPT-AP-RNCTPUSLOTALM

REPT-AP-RNCTPUSONETALM
REPT-AP-RNCTPUTHERMALALM

REPT-AP-RNCTPUVOLTAGEALM

REPT-CP-DN
REPT-IMSI

REPT-MIN

REPT-RNC
REPT-RNC-ABN-MET

4-34

Input/Output Messages

REPT-RNCALMCFGERR
REPT-RNCALMEQPMALF

REPT-RNCALMLANERR

REPT-RNCALMLOSSSIG
REPT-RNCALMPRSRPROB

REPT-RNCALMPWRPROB

REPT-RNCALMSOFTERR
REPT-RNCALMTEMPUNAC

REPT-RNC-AVAILABLE

REPT-RNC-BPCF-20000 through REPT-RNC-BPCF-21106 (Not consecutively

numbered, 87 messages in total.)

REPT-RNC-DCF
REPT-RNC-DYNAMIC

REPT-RNC-IPSHOGW-ALM

REPT-RNC-SECURITY-ALERT
REPT-RNC-SUMMARY

REPT-RNC-TPU-ALM

REPT-RNC-TPU-BPCF
REPT-RNC-TPU-BPCF-ALM

REPT-RNC-TPU-CICC-PROC-ALM

REPT-RNCTPUCONFIG
REPT-RNCTPUDGNALM

REPT-RNCTPUETHALM

REPT-RNC-TPU-GICC-1002 through REPT-RNC-TPU-GICC-9009 (Not

consecutively numbered, 89 messages in total.)

REPT-RNC-TPU-GICC-ATM-ALM
REPT-RNCTPUHTBTALM

REPT-RNCTPUICMPTHRES

REPT-RNCTPUIPFWCFGALM
REPT-RNCTPUIPSHODGNALM

REPT-RNCTPUIPSHOOVLDALM

REPT-RNCTPUNTWKALM
REPT-RNCTPUOC3ALM

REPT-RNCTPUPCFALM

REPT-RNCTPUPPOOSALM
REPT-RNCTPUPROCALM

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
4-35
Issue 14, September 2009
See notice on first page

PRELIMINARY

OA&M Architecture

PRELIMINARY
PRELIMINARY

OA&M Architecture

Input/Output Messages

REPT-RNC-TPU-RIM
REPT-RNC-TPU-STATE

REPT-RNCTPUVERALM

Additional details

For more specifics regarding the use of the related input and associated output
messages, refer to the following:

Input Messages Manual, 401-610-055

Output Messages Manual, 401-610-057

4-36

UNIX
command interface
...................................................................................................................................................................................................................................
Introduction

UNIX commands associated with the RNC-AP and OAM Proxy AP are executed via
an AP UNIX shell and are listed in Appendix B, Command Reference.

PRELIMINARY

OA&M Architecture

Multiple uses

Many of these UNIX commands are executed primarily during generic retrofits and
SUs, but other commands are applicable for maintenance tasks.
ECP and OMP

UNIX commands associated with the ECP and OMP can be found in the UNIX Users
Guide, 401-610-048.

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
4-37
Issue 14, September 2009
See notice on first page

PRELIMINARY

OA&M Architecture

RNC
logs
...................................................................................................................................................................................................................................
Introduction

RNC-related activities generate viewable log files and associated ROP messages that
can aid system users in monitoring the system and determining system errors.
Message variety

These log files include a variety of messages that for the most part also appear on the
ROP, but in a slightly different format.
Additional information

PRELIMINARY

See Monitoring RNC-related activities via logs (p. 7-28) for additional information.

4-38

Recent
Change and Verify (RC/V)
...................................................................................................................................................................................................................................
Introduction

The RC/V interface for RNC provides access to the RC/V database to perform selected
operations such as Insert, Review, Update and Delete on the applicable RNC-related
screens.

PRELIMINARY

OA&M Architecture

Storage format

The RC/V data is first stored in ALX format.

RC/V data tables

The DBE software, which resides on the OAM B-server APs, copies the RC/V data
tables for CDMA 1X RNC to the OAM Proxy AP. The RNC DBMS VCVM then
copies the RC/V data tables for CDMA 1X RNC into the RNC-DB.
Applicable screens

The RC/V screens that have applicability for RNC are described in RC/V
provisioning (p. 11-2).

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
4-39
Issue 14, September 2009
See notice on first page

PRELIMINARY

OA&M Architecture

Status
Display Pages (SDPs)
...................................................................................................................................................................................................................................
Introduction

SDPs provide another graphical human interface to system status information. Status
display pages provide a summary status indicator for all RNCs.
Types of information

Typical information included on SDPs:

alarm levels

real time status

equipage

overload conditions

menus of possible input commands

Access to SDPs

The RNC-related SDPs are either stored on the MM-SP, and mirrored on the ECP, or
stored directly on the ECP.
Applicable SDPs

The SDPs that have applicability for RNC are listed as follows:

SDP 2100

SDP 2121
SDP 2122

SDP 2138

Note that SDP 2100, SDP 2121, SDP 2122 and SDP 2138, provide RNC and MM-AP
summary status.

PRELIMINARY

For details concerning these SDPs, refer to volume 1 of 401-610-160.

4-40

RNC
alarms
...................................................................................................................................................................................................................................
Introduction

RNC alarms are raised against managed objects.

Managed objects

PRELIMINARY

OA&M Architecture

RNC alarms are raised against the following managed objects:

RNC-AP

LAN

RNC-M
TCS

TPU

Alarm levels

The alarm levels defined for RNC are listed as follows:

WARNING: Indicates the detection of a potential or impending service affecting

fault, before any significant effects have been felt. Action should be taken to further
diagnose (if necessary) and correct the problem in order to prevent it from
becoming a more serious service affecting fault. This level will not be supported on
the RNC-AP.

MINOR: Indicates the existence of a non-service affecting fault condition and that
corrective action should be taken in order to prevent a more serious, for example,
service affecting, fault. Such a severity can be reported, for example, when the
detected alarm condition is not currently degrading the capacity of the managed
object.
MAJOR: Indicates that a service affecting condition has developed and an urgent
corrective action is required. Such a severity can be reported, for example, when
there is a severe degradation in the capability of the managed object, and its full
capability must be restored.

CRITICAL: Indicates that a service affecting condition has occurred and an

immediate corrective action is required. Such a severity can be reported, for
example, when a managed object goes totally out of service and its capability must
be restored.

INDETERMINATE: Indicates that the severity level cannot be determined, or

unable to assign any of the following values:
WARNING

MINOR
MAJOR

CRITICAL

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
4-41
Issue 14, September 2009
See notice on first page

PRELIMINARY

PRELIMINARY
PRELIMINARY

OA&M Architecture

RNC alarms

GUI alarm list

The EMS GUI provides a dynamic list of all the current alarms on the RNC-AP
platform, RNC-AP applications, OAM proxy AP platform, OAM proxy AP
applications.
The TPU GUI provides a dynamic list of all the current alarms on the TPU
applications.

4-42

Service
measurements
...................................................................................................................................................................................................................................
Specific information

For information pertaining to Service Measurements, refer to Chapter 10, Service

measurement.

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
4-43
Issue 14, September 2009
See notice on first page

PRELIMINARY

OA&M Architecture

PRELIMINARY
PRELIMINARY

OA&M Architecture

Read-Only
Printer (ROP)
...................................................................................................................................................................................................................................
Specific information

For information pertaining to ROP, refer to Monitoring activities via Read-Only

Printer (ROP) (p. 7-36).

4-44

Operations and Maintenance Center Radio Access Network

(OMC-RAN)
...................................................................................................................................................................................................................................
Introduction

In conjunction with the OMP, the Operations and Maintenance Center Radio Access
Network (OMC-RAN) provides enhancements to the OA&M capabilities of the
System.

PRELIMINARY

OA&M Architecture

Features

The OMC-RAN includes the following features:

OAM Proxy server pair

OMC-RAN interfaces
ORCA (an application bundled with MM-SP application on the 800S/810S servers)

Spf (an application on the OAM Proxy servers)

Support

One OMC-RAN can support a single System or multiple Systems. At present, one
OMC-RAN can support up to:

10 systems (and up to 2300 BTSs)

320 Applications Processors (APs)

40 Digital Cellular Switches (DCSs) (of which up to 11 can be physical DCSs)

Client sessions

The OMC-RAN (Figure 4-4, Alcatel-Lucent CDMA Network with OMC-RAN

Solution (p. 4-46)) can support up to 94 simultaneous client sessions of which at least
three fourths are GUI client sessions.
User capacity

One OMC-RAN Solution can support up to 1000 users.

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
4-45
Issue 14, September 2009
See notice on first page

PRELIMINARY

OA&M Architecture

Operations and Maintenance Center Radio Access

Network (OMC-RAN)

Figure 4-4 Alcatel-Lucent CDMA Network with OMC-RAN Solution

For more detailed information regarding OMC-RAN OA&M equipment, interfaces, and
tasks, refer to 401-380-835, Alcatel-Lucent CDMA Network Operations and
Maintenance Center - Radio Access Network - Operations, Administration,
Maintenance, and Provisioning.
OMC-RAN GUI

PRELIMINARY

The OMC-RAN provides a web-based GUI for element management and is based on
industry standard network management systems.
The OMC-RAN GUI allows system users to monitor and control the maintenance and
alarm states of system elements and their managed resources.

4-46

Operations and Maintenance Center Radio Access

Network (OMC-RAN)

On-lne help

The OMC-RAN provides context-sensitive on-line help for each RNC alarm. The
on-line help provides details on the field definitions, specific reasons for every alarm
and the corrective action to resolve the same.
For additional information pertaining to on-line help refer to 401-380-835,
Alcatel-Lucent CDMA Network Operations and Maintenance Center - Radio Access
Network - Operations, Administration, Maintenance, and Provisioning.

PRELIMINARY

OA&M Architecture

Choose to use the OMC-RAN GUI

Only one GUI (EMS or OMC-RAN) can be used to monitor the RNC-APs and OAM
Proxy APs. A parameter on the apeqp form for each of the APs (OAM Proxy APs and
RNC APs) is used to indicate whether or not the OMC-RAN GUI is to be used.
Currently, the OMC-RAN and the EMS co-exist. Users may select some of the
MM-APs (including OAM Proxy APs and RNC APs) to be managed by OMC-RAN
and others to be managed by EMS.
For information on how to enable or disable OMC-RAN access refer to To
enable/disable OMC-RAN (p. 4-49).
OMC-RAN TICLI

The majority of RNC-related input messages are executable, and the majority of
RNC-related output messages are viewable via the OMC-RAN TICLI.
See also Input/Output Messages (p. 4-28).
TPU GUI

The OMC-RAN will co-exist with the TPU GUI.

Configuration management

TPU GUI capabilities for configuration management, card/port level status, and
on-demand statistics will not migrate to OMC-RAN.
Access control and cut through

The OMC-RAN will provide access control and cut through to the TPU GUI using
existing login synchronization between the the OMP and the TPU GUI. Cut though
from the OMC-RAN to TPU GUI is provided for access to TPU GUI Alarms Page and
the TPU GUI Status Page.

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
4-47
Issue 14, September 2009
See notice on first page

PRELIMINARY
PRELIMINARY

OA&M Architecture

Operations and Maintenance Center Radio Access

Network (OMC-RAN)

Access to OMC-RAN

For information on logging onto the OMC-RAN, and also for launching cut through to
the TPU GUI, refer to 401-380-835, Alcatel-Lucent CDMA Network Operations and
Maintenance Center - Radio Access Network - Operations, Administration,
Maintenance, and Provisioning.

4-48

To
enable/disable OMC-RAN
...................................................................................................................................................................................................................................
Purpose

To enable/disable OMC-RAN.
Reason to perform

PRELIMINARY

OA&M Architecture

To provide or eliminate the RNC user capability of performing some of the 1X RNC
related operations from the OMC-RAN.
Before you begin

To enable or disable OMC-RAN ensure the following before proceeding:

If enabling, set the OMC-RAN Managed field on the apeqp RC/V form to y (yes).

If disabling, set the OMC-RAN Managed field on the apeqp RC/V form to n (no).

Enabling OMC-RAN

Proceed as follows:
...................................................................................................................................................................................................

Log on to the OMP, and bring up the Command Line Interface (CLI) and ECP RTR
Shell by performing the procedure provided under Access via OMP (p. 6-19).
Important! Note that when you execute the apappenable -l command, the state
of ORCARNC, and ORCATPU will show up as disabled.
...................................................................................................................................................................................................

Via the TICLI, remove the Status Display Process (SP) application from service, on the
standby RNC-AP, by executing the following command:
RMV:AP #,sp;ucl

where: # is the ID number of the standby RNC-AP.

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

From the ECP RTR shell, execute the following command:

apappenable -a ORCARNC

Result: The output shows that the ORCARNC process is enabled.

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

From the ECP RTR shell, execute the following command:

apappenable -a ORCATPU

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
4-49
Issue 14, September 2009
See notice on first page

PRELIMINARY

OA&M Architecture

To enable/disable OMC-RAN

Result: An output similar to the following example will result showing that

ORCATPU is also enabled, which means that OMC-RAN is now managing its
associated 1X RNC elements:

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

Via the TICLI, restore the Status Display Process (SP) application to service, on the
standby RNC-AP, by executing the following command:
RST:AP #,sp;ucl

where: # is the ID number of the standby RNC-AP.

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

PRELIMINARY

Via the TICLI, switchover the Status Display Process (SP) application from the active
RNC-AP to the standby, by executing the following command:
SWITCHOVER:SP

4-50

To enable/disable OMC-RAN

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

Via the OMC-RAN Network Manager verify:

1. That the 1X RNC Managed Objects are populated.
2. That cut-through for TPU GUI Alarms and Status is functioning via the Tools
menu item.
See the following example screens.

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
4-51
Issue 14, September 2009
See notice on first page

PRELIMINARY

OA&M Architecture

PRELIMINARY

OA&M Architecture

To enable/disable OMC-RAN

PRELIMINARY

E...................................................................................................................................................................................................
ND OF STEPS

4-52

To enable/disable OMC-RAN

Disabling OMC-RAN

Log on to the OMP, and bring up the Command Line Interface (CLI) and ECP RTR
Shell by performing the procedure provided under Access via OMP (p. 6-19).

PRELIMINARY

OA&M Architecture

Important! Note that when you execute the apappenable -l command, the state
of ORCARNC, and ORCATPU will show up as enabled.
...................................................................................................................................................................................................

Via the TICLI, remove the Status Display Process (SP) application from service, on the
standby RNC-AP, by executing the following command:
RMV:AP #,sp;ucl

where: # is the ID number of the standby RNC-AP.

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

From the ECP RTR shell, execute the following command:

apappenable -a ORCARNC (passwd ORCATPU)

Result: The output shows that the ORCARNC process is disabled.

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

From the ECP RTR shell, execute the following command:

apappenable -a ORCATPU

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
4-53
Issue 14, September 2009
See notice on first page

PRELIMINARY

OA&M Architecture

To enable/disable OMC-RAN

Result: An output similar to the following example will result showing that

ORCATPU is also disabled, which means that OMC-RAN is now managing its
associated 1X RNC elements:

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

Via the TICLI, restore the Status Display Process (SP) application to service, on the
standby RNC-AP, by executing the following command:
RST:AP #,sp;ucl

where: # is the ID number of the standby RNC-AP.

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

PRELIMINARY

Via the TICLI, switchover the Status Display Process (SP) application from the active
RNC-AP to the standby, by executing the following command:
SWITCHOVER:SP

4-54

To enable/disable OMC-RAN

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

Via the OMC-RAN Network Manager verify:

1. That the 1X RNC Managed Objects are no longer populated.
2. That cut-through for TPU GUI Alarms and Status is no longer functioning via the
Tools menu item.
END OF STEPS

PRELIMINARY

OA&M Architecture

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

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
4-55
Issue 14, September 2009
See notice on first page

PRELIMINARY

OA&M Architecture

Local
Maintenance Terminal (LMT)
...................................................................................................................................................................................................................................
Introduction

The LMT is primarily intended for use in service and support situations.
LMT software

LMT software is distributed with the MM-AP delivery. Therefore to use this software,
a user logs into the MM-AP and downloads (via SFTP of the IP address of the active
AP) and installs the LMT software (according to wizard program instructions) on a
laptop or equivalent computer.
MM-AP frame connection

Once the LMT software is installed on a PC, it may be used for physical connection
through the Front Maintenance Interface Panel (FMIP) to the MM-AP frame and
access via the Ethernet LAN.
Installing software, connecting, and using LMT

For complete details on installing LMT software, connecting the LMT and using the
LMT, refer to the FMS/FWR Local Maintenance Terminal (LMT) Users Guide,
401-710-221.
Terminal server

To reduce the need to have field personnel physically travel to a site and use an LMT
to resolve problems, a 40-port Terminal Server is included in the RNC cabinet. Each of
the forty RS-232 ports connects to a console port of a cPSB card, so that every card is
accessible from the terminal server.

PRELIMINARY

The terminal server also has an Ethernet connection that is connected to the OMP so
that authorized maintenance personnel can gain remote access via the OMP to the
terminal server and then to each cPSB card without having to be physically at the
RNC cabinet.
However, if the LMT is connected to the MM-AP frames Ethernet LAN, authorized
maintenance personnel can access a GICC without physically connecting by looking up
the IP address of the GICC with the active SC and then telneting to the GICC in the
TPU shelf. Once they have gained access to the GICC, they can access all of the other
cards in the system.

4-56

Local Maintenance Terminal (LMT)

ESC and alarm card

Only direct LMT connection to the Ethernet Management Port on each Ethernet Switch
Card port is available. For LMT access, the Alarm Cards Ethernet connection is also
via the front-panel.
However, both the ESCs and Alarm Cards have front RS-232 Console Ports available
on the MIP via an RJ45 connector type so easy physical access is available via
RS-232.

PRELIMINARY

OA&M Architecture

Important! A major effort has been made to minimize the need to access the cPSB
cards directly, so such measures should only be necessary during initial shelf
installation where the starting IP address of the cPSBs internal IP addresses must
be provisioned, or in catastrophic emergency maintenance situations (and only then)
by authorized maintenance personnel or under direct Lucent Technologies
supervision.

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
4-57
Issue 14, September 2009
See notice on first page

PRELIMINARY

5M aintenance states

The purpose of this chapter is to provide information concerning the maintenance

states associated with the:

RNC-AP and OAM proxy AP

TPU managed objects and services of the RNC

Contents
RNC-AP and OAM proxy AP

5-2

TPU managed object states

5-5

SC-GICC service maintenance state

5-9

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
5-1
Issue 14, September 2009
See notice on first page

PRELIMINARY

Maintenance states

RNC-AP
and OAM proxy AP
...................................................................................................................................................................................................................................
Introduction

The RNC-AP and OAM Proxy AP support the legacy state model that was derived for
the MM platform.
EMS managed objects

The following EMS managed objects exist for the RNC-AP:

LAN
EINE

RNC-M

TCS

The following EMS managed objects exist for the OAM Proxy AP:

LAN
EINE

RNC DB

TPU GUI

EMS-GUI

The EMS-GUI displays the managed objects and associated states listed in Table 5-1,
AP managed objects and states (p. 5-2).
Table 5-1

AP managed objects and states

Managed Object
AP

PRELIMINARY

LAN

Valid States

Alarm States

ACTIVE

Critical

OOS-MANUAL

Major

ISOLATED

Minor

Warning

Informational

ACTIVE

Critical

STANDBY

Major

OOS-FAULT

Minor

Warning

Informational

5-2

RNC-AP and OAM proxy AP

Table 5-1

AP managed objects and states (continued)

Managed Object
EINE

RNC-M

TCS

RNC DB

TPU GUI

Valid States

Alarm States

ACTIVE

Critical

OOS-FAULT

Major

Minor

Warning

Informational

ACTIVE

Critical

STANDBY

Major

OOS-FAULT

Minor

OOS-MANUAL

Warning

Informational

ACTIVE

Critical

STANDBY

Major

OOS-FAULT

Minor

OOS-MANUAL

Warning

Informational

ACTIVE

Critical

STANDBY

Major

OOS-FAULT

Minor

OOS-MANUAL

Warning

Informational

ACTIVE

Critical

STANDBY

Major

OOS-FAULT

Minor

OOS-MANUAL

Warning

Informational

PRELIMINARY

Maintenance states

Platform
Application

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
5-3
Issue 14, September 2009
See notice on first page

PRELIMINARY

The AP managed objects are grouped into two categories, in the area pertaining to
maintenance states:

PRELIMINARY
PRELIMINARY

Maintenance states

RNC-AP and OAM proxy AP

Platform

The RNC AP, OAM Proxy AP, and EINE follow the platform maintenance states of the
Mobility Manager (MM).
Application

The RNC-M, TCS, RNC DB and TPU GUI follow the application maintenance states
of the MM.

5-4

TPU
managed object states
...................................................................................................................................................................................................................................
Introduction

The TPU state model is based on the TMN (Telecommunications Management

Network) model (x.731). The state of a managed object represents the instantaneous
condition of availability and operability of the associated resource from a management
point of view. TPU managed objects map to the following states:

operational

usage

administrative

PRELIMINARY

Maintenance states

Operational state

The operability of a managed object is defined by the operational state attribute, which
has three possible values (see also Figure 5-1, Operational state (p. 5-5)):

disabled

enabled
unknown

Figure 5-1 Operational state

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
5-5
Issue 14, September 2009
See notice on first page

PRELIMINARY

Maintenance states

TPU managed object states

Disabled

The managed object is totally inoperable (powered off), and unable to provide service.
Enabled

The managed object is operable, and available for service.

Unknown

When the slot power is on and the managed object is disabled, or during initialization
of the managed object.
Usage state

The usage of a managed object is defined by the usage state attribute, which has four
possible values (see also Figure 5-2, Usage state (p. 5-6)):

idle

active

busy
unknown

PRELIMINARY

Figure 5-2 Usage state

Idle

The managed object is not currently in use.

5-6

TPU managed object states

Active

The managed object is in use, and has sufficient operating capacity to provide for
additional service.
Busy

The managed object is in use, but it has no spare operating capacity to provide for
additional service at this point in time.

PRELIMINARY

Maintenance states

Unknown

When the slot power is on and the managed object is disabled, or during initialization
of the managed object.
Administrative state

The administration of managed objects operates independently of the operability and

usage of managed objects, and is described by the administrative state attribute, which
has four possible values (see also Figure 5-3, Administrative state (p. 5-7)):

locked

unlocked

shutting down (to a locked state)

unknown

Figure 5-3 Administrative state

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
5-7
Issue 14, September 2009
See notice on first page

PRELIMINARY

Maintenance states

TPU managed object states

Locked

The managed object is administratively prohibited from performing services for its
users.
Unlocked

The managed object is administratively permitted to perform services for its users. This
is independent of its inherent operability.
Shutting down

Use of the managed object is administratively permitted for existing instances of use
only. New calls for service will NOT be permitted, and existing activity will cease in
due course, eventually culminating in the locked state.
Important! In the case of a shutdown, the GICC card and/or its individual gateway
ports are actually governed by a two-minute timer; therefore, lockdown will occur
after two minutes.
Unknown

When the slot power is on and the managed object is disabled, or during initialization
of the managed object.
State and status attributes

State and status attribute information for TPU managed objects are displayed in a
summary format at the SDP, ROP, RNC Admin log, and TPU-GUI.
The TPU managed objects and associated states are shown in Table 5-2, TPU
managed objects and associated states (p. 5-8).

PRELIMINARY

Table 5-2

TPU managed objects and associated states

Managed Object

Operational
State

Administrative State

Usage state

CICC processor 0 through 2

(Note)

GICC processor 0

GICC: ATM 1 and 2

B-PCF

Alarm card

Always
unlocked

Always active

Ethernet switch card

Always
unlocked

Always active

Note: Three processors per CICC.

5-8

SC-GICC
service maintenance state
...................................................................................................................................................................................................................................
Introduction

The varying combinations of operational, administrative and usage states define the
maintenance state of the SC-GICC service. The maintenance state indicates the current
availability of the SC-GICC service:

active
standby

stale

offline
unknown

PRELIMINARY

Maintenance states

Active

The service is running and in service.

Standby

The service is running and ready to become active in the case of failure of the
currently active service.
Stale

The service has application and/or configuration files that are older than those on its
active mate. This state may occur during a software update.
Offline

The service is not active. This may occur when the service has been locked for
maintenance reasons.
Unknown

The state of the service cannot be identified because of a communications problem or

other issue.

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
5-9
Issue 14, September 2009
See notice on first page

PRELIMINARY

Maintenance states

SC-GICC service maintenance state

Example

The following scenario describes the various maintenance states for an SC-GICC pair.

Active state: When an SC-GICC is running the shelf controller service.

Standby state: At the same time, its mate SC-GICC is available for service if a
failure occurs on the active SC-GICC. The mate SC-GICC is in the standby state.
This means the application and configuration files are equivalent to those on the
Active SC-GICC.

Stale state: During a software update, the application and configuration files on the
SC-GICC do not match those on its mate, the Active SC-GICC.

The SC-GICC service and associated states are shown in Table 5-3, SC-GICC service
and all associated states (p. 5-10).

PRELIMINARY

Table 5-3

SC-GICC service and all associated states

Operational State

Administrative
State

Usage state

Maintenance State

N/A

active/standby

5-10

PRELIMINARY

Part II: System administration

This Part covers tasks that are necessary to access RNC-related system interfaces and
maintain the integrity of the RNC.
General-purpose tasks

The general-purpose tasks provided in this Part are those tasks that enable the user to
understand how to access the RNC-related interfaces. These RNC-related interfaces are
necessary for performing other tasks and procedures referenced in other parts of this
document.
System administration tasks

The system administration tasks provided in this Part are those tasks specific to:

backing up AP configuration information

restoring AP configuration files and packages

managing AP file systems

backing up the RNC database

restoring the RNC database

Contents
Chapter 6, System management, methods, and procedures

6-1

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
II-1
Issue 14, September 2009
See notice on first page

PRELIMINARY

6 ystem management, methods,

S
and procedures

PRELIMINARY

To provide information concerning:

Methods for accessing the various RNC-related interfaces.

The backup and restoration of RNC related configuration data and databases.

Contents
RNC-related interfaces

6-3

Methods for RNC-AP and OAM Proxy AP login

6-4

Logging on to Element Management System (EMS)

6-5

Accessing TPU GUI

6-6
6-11

Accessing the TPU GUI directly

6-14

Accessing TPU CLI

6-17

Accessing TICLI

6-18

Access via OMP

6-19

Access via direct login

6-23

Access via LMT

6-24

Accessing Recent Change/Verify (RC/V)

6-25

Accessing Status Display Pages (SDPs)

6-27

Backing up and restoring

6-28

Backing up/restoring AP configuration data

6-29

Backing up AP configuration data

6-32

Restoring AP configuration files and packages

6-34

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
6-1
Issue 14, September 2009
See notice on first page

PRELIMINARY

Hypertext Transfer Protocol modification

PRELIMINARY
PRELIMINARY

System management, methods, and procedures

Overview

Backing up/restoring RNC Database

6-36

Maintaining directory/file space

6-39

Backing up RNC database

6-42

Restoring RNC database

6-45

Rebooting CICCs and non-APS GICCs

6-55

Rebooting APS GICCs

6-60

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

6-2

RNC-related interfaces
Overview
...................................................................................................................................................................................................................................

PRELIMINARY

System management, methods, and procedures

Purpose

This section describes the various legacy and new interfaces that are required to
communicate with the RNC-related elements.
Methods for access

The information in this section provides information on how to obtain access to these
interfaces.
Contents
Methods for RNC-AP and OAM Proxy AP login

6-4

Logging on to Element Management System (EMS)

6-5

Accessing TPU GUI

6-6

Hypertext Transfer Protocol modification

6-11

Accessing the TPU GUI directly

6-14

Accessing TPU CLI

6-17

Accessing TICLI

6-18

Access via OMP

6-19

Access via direct login

6-23

Access via LMT

6-24

Accessing Recent Change/Verify (RC/V)

6-25

Accessing Status Display Pages (SDPs)

6-27

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
6-3
Issue 14, September 2009
See notice on first page

PRELIMINARY

System management, methods, and procedures

Methods
for RNC-AP and OAM Proxy AP login
...................................................................................................................................................................................................................................
Introduction

There are seven ways to log directly into an RNC-AP or OAM proxy AP as follows:

Accessing an AP from OMP menus

Accessing an AP via Secure Shell (SSH) from the OMP shell

Accessing an AP via SSH from another AP

Accessing an AP via SSH from the LMT

Telneting to an AP console via the alarm card

Accessing an AP via the alarm card serial port

Accessing an AP via the CPU serial port

Procedures

PRELIMINARY

The procedure for logging into an RNC-AP or OAM proxy AP are the same as used
for logging into an MM-AP. See Chapter 5 (System Administration) of 401-710-201.

6-4

Logging
on to Element Management System (EMS)
...................................................................................................................................................................................................................................
Introduction

The EMS is a web server that resides on the OMP. To execute the EMS process and
bring up the Graphical user Interface (GUI), a system user uses a web browser (either
remotely or at the OMP) to access the EMS home page.

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
6-5
Issue 14, September 2009
See notice on first page

PRELIMINARY

System management, methods, and procedures

PRELIMINARY

System management, methods, and procedures

Accessing
TPU GUI
...................................................................................................................................................................................................................................
Introduction

The TPU GUI was designed to be integrated, as regards to look and feel, with the
EMS GUI.
Secure Socket Layer supported for HTTP

The TPU GUI has the option either to support Hyper-Text Transfer Protocol (HTTP)
over Secure Socket Layer (HTTPS), or to support HTTP. System users are provided
with the capability to switch from HTTPS (provided by default) to HTTP, or vice
versa. See also Hypertext Transfer Protocol modification (p. 6-11).
Access methods

Access to the TPU GUI can be obtained:

Via login from EMS GUI.

Via direct access.

Important! If an OAM Proxy AP switchover occurs after you login to the TPU
GUI, you will be required to log back-in to the TPU GUI.

TPU GUI performance issues

The following TPU GUI performance issues are currently relevant:

The maximum number of simultaneous TPU GUI/TPU CLI sessions per RNC is
limited to five.

During periods of heavy call load on the RNC:

PRELIMINARY

The TPU GUI Alarms page and Traffic Processing Unit (TPU) network
elements page may take up to one minute (cold response time) to display.
The TPU GUI Failed PVCs Status page may take up to six minutes (cold
response time) to display.

When a Traffic Processing Unit (TPU) network elements page session expires, no
expiration message will appear unless the user refreshes the browser or tries to
navigate to another screen.
Important! Any command entered via the Commands column after the network
elements page session expires will still execute. Until this issue is resolved in a
future release, always refresh the screen before entering any commands to prevent
the loss of session continuity.

TPU GUI switchover

Make sure the TPU GUI VCVM on the other AP is in STANDBY before the ACTIVE
TPU GUI VCVM is switched over.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

6-6

Accessing TPU GUI

After executing a Switchover, wait for the display, Switchover of TPUGUI VCVM
successful message before performing another operation on the TPU GUI, , or TICLI.
If the TPU GUI VCVM on the other OAM Proxy AP is not in STANDBY mode, bring
it up by using the RST:AP#, TPUGUI command on the TICLI.
OAM Proxy AP reboot

PRELIMINARY

System management, methods, and procedures

Ensure that the TPU GUI VCVM on the other OAM Proxy AP is in STANDBY before
rebooting the OAM Proxy AP on which the TPU GUI is ACTIVE.
When the OAM Proxy AP reboots, it will display TPUGUI OOS:FAULT, then
STANDBY, and then ACTIVE.
If the TPUGUI VCVM is made OOS:MANUAL before an OAM Proxy AP is
rebooted, then RCC will not restore. In that case, run the RST:AP#, TPUGUI
command.
Important! Wait for the indication that the TPUGUI VCVM is ACTIVE before
executing any specific TPU commands on the TICLI, or TPU GUI.
Remove/Restore OAM Proxy AP/TPU GUI

When you remove a TPU GUI VCVM or OAM Proxy AP, ensure that the response
TPUGUI successfully removed occurs before proceeding to execute TPU GUI, or
TICLI commands for the TPU.
When you restore a TPU GUI VCVM or OAM Proxy AP, ensure that the response
TPUGUI successfully restoredoccurs before proceeding to execute TPU GUI, or
TICLI commands for the TPU.
Initialization

After an initialization occurs, do not execute multiple TPU-related commands in quick

succession over the TICLI. The system has just initialized and may not be prepared to
handle commands in quick succession.
Login required from EMS GUI

Access to the TPU GUI is provided via the EMS GUI through a URL-based
navigational relationship, and a login screen.
Logging in

Important! If you enter five invalid login attempts, in succession you will be
locked out, and the mesage shown in Figure 6-1, Account locked out (p. 6-8)
will be displayed.
....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
6-7
Issue 14, September 2009
See notice on first page

PRELIMINARY

At the OMP Web page of the EMS GUI, you select the 1X RNC TPU Web icon which
brings up the 1X RNC TPU GUI LOGIN screen.You are then required to re-enter your
EMS GUI user ID and password, and click on the Login button. (See also TPU GUI
login synchronization (p. 16-13)).

PRELIMINARY

System management, methods, and procedures

Accessing TPU GUI

Figure 6-1 Account locked out

A correct login action will direct you to the 1X RNC TPU Web launch page, from
which you can then navigate (as required) via TPU GUI.
Note that if you navigate to TPU GUI via EMS GUI, you can also navigate back to
EMS GUI.
Unable to access TPU GUI

PRELIMINARY

If you are unable to access TPU GUI, refer to Unable to access TPU GUI (p. 8-64)
for additional measures that you can initiate to ensure TPU GUI access.
Direct access

Service providers may also access TPU GUI directly, via a url that contains the IP
address of the TPU GUI. See also Accessing the TPU GUI directly (p. 6-14).

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

6-8

Accessing TPU GUI

Pop-up message disabling

The following pop-up message will be shown on the TPU GUI everytime a user
navigates to the Alarms page, Traffic Processing Unit (TPU) network elements page,
Installation Options page, Growth and Degrowth pages:
This page contains both secure and nonsecure items. Do you want to
display the nonsecure items? Yes/No/MoreInfo

PRELIMINARY

System management, methods, and procedures

To disable this message:

1. Go to Internet Options from the Tools menu of Internet Explorer.
2. Select Security tab.
3. Select Internet icon and click on Custom Level button.
4. Select Enable for the option Display mixed content.
Navigating between GUIs

To see the RNC-related navigational relationship between the EMS GUI and the TPU
GUI, refer to Element Management System (EMS) (p. 4-8) for specifics.
Multiple logins and login classifications

The TPU GUI supports multiple user level logins. Currently, there are two user roles:

System administrator level (ADMIN)

Non-system adminstrator level (USER/technician)

Refer to Local TPU GUI admin/user screens (p. 16-11) and TPU GUI login
synchronization (p. 16-13) for specifics.
Single-user configuration management

The TPU-GUI provides single-user configuration management capability per each

RNC. If a subsequent user tries to access the configuration data that another user is
currently modifying, the subsequent user is provided with a warning message stating
that the configuration data is already being modified by another system user.
This warning message contains the users name and IP address.
The subsequent user will be allowed to review the configuration data pages, but will
not be allowed to modify the configuration data, until the current user logs out.
Configuration data screens

Individual RNC screens tha can be locked are as folows:

First Time Install Wizard

PSU GW Growth Wizard

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
6-9
Issue 14, September 2009
See notice on first page

PRELIMINARY

A user that initiates access to any of the following configuration data screens will be in
control until proper log out:

PRELIMINARY

System management, methods, and procedures

GICC Growth Wizard

PSU GW Degrowth Wizard

GICC Degrowth Wizard

BPCF Parameters Configuration

Common BPCF Parameters Configuration

1X-RNC Information

Static Routes configuration

PSU VCC Overrides

Update External IP Address

Accessing TPU GUI

Global screens that can be locked are as follows:

External PCF Servers

PDSN Pool Configuration

PDSN Configuration
RNC Call Processing Parameters

PSU Subnet & VPI Configuration

Locked configuration screens

When a user fails to log out of a configuration data screen, the screen will become
locked. If the user session has a lock timeout, the screen will become available when
the timeout occurs. For example, after 30 minutes. It is also possible for a user with
ADMIN privileges to unlock the screen prior to the timeout.
If, however, the user session has a no timeout privilege set, then a user with ADMIN
privileges will be needed to unlock the screen.
Procedures

Use the following procedures to:

Modify Hyper-Text Transfer Protocol (HTTP) settings

Obtain direct access to the TPU GUI:

Hypertext Transfer Protocol modification (p. 6-11)

PRELIMINARY

Accessing the TPU GUI directly (p. 6-14)

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

6-10

Hypertext
Transfer Protocol modification
...................................................................................................................................................................................................................................
Purpose

To switch from using HTTPS to HTTP for TPU GUI access, or vice versa.
Reason to perform

PRELIMINARY

System management, methods, and procedures

To maintain the same security balance between EMS GUI and TPU GUI, or security
concerns may necessitate a change.
HTTPS default

By default, CDMA 1X RNC is installed with HTTPS support.

Before you begin

If you are unsure what HTTP convention is currently invoked for TPU GUI access,
verify by performing Accessing the TPU GUI directly (p. 6-14).
Procedure

To switch from using HTTPS to HTTP for TPU GUI access, or vice versa, perform the
following procedure:
...................................................................................................................................................................................................

As root, switchover all active applications from the odd-numbered OAM Proxy AP to
the even-numbered OAM Proxy AP, by executing the following TICLI command:
SWITCHOVER:AP a<CR>

where:
a = the number of the odd-numbered OAM Proxy AP
Result The following completion message will be outputted when the switch is

completed:
SWITCHOVER:AP a COMPLETE
...................................................................................................................................................................................................

As root, remove the OAM Proxy AP that was just switched by executing the following
command:
RMV:AP a<CR>

a = the number of the specified OAM Proxy AP

Result The following message occurs when the remove is completed:
RMV:AP A ! COMPLETE

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
6-11
Issue 14, September 2009
See notice on first page

PRELIMINARY

where:

PRELIMINARY

System management, methods, and procedures

Hypertext Transfer Protocol modification

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

Log in to the removed OAM Proxy AP as root, or in Release 32.0 when the RBAC
feature is enabled, as the Security Administrator.
...................................................................................................................................................................................................

Take the removed OAM Proxy AP offline by executing the following command from
the UNIX shell:
apoffline<CR>

Result The OAM Proxy AP is taken offline.

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

Then run one of the following commands from the UNIX shell:
httpactivate<CR>
-orhttpsactivate<CR>

Result Either HTTP or HTTPS is activated.

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

Run the following command from the UNIX shell:

/flx/bin/clntpuweb<CR>

Result The activate function is completed.

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

Bring the OAM Proxy AP online by executing the following command from the UNIX
shell:
aponline <CR>

Result While the OAM Proxy AP is initializing (booting), the OAM Proxy AP is

isolated for about five minutes. When the initialization is completed, the OAM
Proxy AP is promoted to OOS-Manual.
...................................................................................................................................................................................................

Do not proceed until the OAM Proxy AP is in the OOS-Manual state following the
OAM Proxy AP boot. As root, check the status of the OAM Proxy AP by using the
following TICLI command:
OP:AP a, STATUS<CR>

where:

PRELIMINARY

a = the number of the specified OAM Proxy AP

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

As root, restore the OAM Proxy AP to service by entering the following TICLI
command:
RST:AP a <CR>

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

6-12

Hypertext Transfer Protocol modification

where:
a = the number of the specified OAM Proxy AP
Result The OAM Proxy AP is restored to service.
...................................................................................................................................................................................................

As root, check to see if the OAM Proxy AP is restored to service by using the
following TICLI command:

PRELIMINARY

System management, methods, and procedures

OP:AP a, STATUS<CR>

where:
a = the number of the specified OAM Proxy AP
...................................................................................................................................................................................................

As root, switchover all active applications from the even-numbered OAM Proxy AP to
the odd-numbered OAM Proxy AP, by executing the following TICLI command:
SWITCHOVER:AP a<CR>

where:
a = the number of the even-numbered OAM Proxy AP
Result The following completion message will be outputted when the switch is

Repeat Step 2 through Step 11 for the even-numbered OAM Proxy AP.
...................................................................................................................................................................................................

To verify that change has been implemented correctly, perform Accessing the TPU
GUI directly (p. 6-14).
END OF STEPS
...................................................................................................................................................................................................

PRELIMINARY

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
6-13
Issue 14, September 2009
See notice on first page

PRELIMINARY

System management, methods, and procedures

Accessing
the TPU GUI directly
...................................................................................................................................................................................................................................
Purpose

Use this procedure to access TPU GUI directly, via an Internet browser.
Important! The supported Internet browsers are Internet Explorer 6.0 or later for
Windows, and Netscape 4.76 for Solaris. No other combinations are supported. For
example, Netscape on PC.
Reason to perform

Access via EMS GUI is impaired, or direct access is the preferred method.
IP address required

Before you can access TPU GUI directly, you will need to obtain the IP address
assigned for the TPU GUI during initial installation.
Troubleshooting

If you are unable to gain access to the TPU GUI, refer to Unable to access TPU GUI
(p. 8-64).
Procedure

Perform the following procedure, to access the TPU GUI directly:

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

Bring-up the appropriate Internet browser.

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

Enter the following url and depress enter:

https://ip_address/tpuweb/login.jsp

where

PRELIMINARY

ip_address

is the IP address assigned during initial installation for direct access

to the TPU GUI

6-14

Accessing the TPU GUI directly

Result After entering the url, the screen shown in Figure 6-2, TPU GUI login

screen (p. 6-15) is displayed:

Figure 6-2 TPU GUI login screen

PRELIMINARY

System management, methods, and procedures

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

Enter either of the following:

Your shared OMP/TPU GUI user ID and password (see also TPU GUI login
synchronization (p. 16-13)).

Your specific TPU GUI user ID and password (see also Adminstrator tasks
(p. 16-15)) and Updating local TPU GUI password (p. 16-40)).
Important! If you enter five invalid login attempts, in succesion you will be locked
out, and the mesage shown in Figure 6-1, Account locked out (p. 6-8) will be
displayed.

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
6-15
Issue 14, September 2009
See notice on first page

PRELIMINARY

System management, methods, and procedures

Accessing the TPU GUI directly

Result The 1X RNC TPU Web launch page is displayed, as shown in the example

of Figure 6-3, 1X RNC TPU Web launch page (p. 6-16).

Figure 6-3 1X RNC TPU Web launch page

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

Navigate via the appropriate icon or button as desired.

Important! If you access TPU GUI via direct access, you cannot then navigate to
EMS GUI. Navigation between GUIs is only possible if you access TPU GUI by
means of EMS GUI.
END OF STEPS

PRELIMINARY

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

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

6-16

Accessing
TPU CLI
...................................................................................................................................................................................................................................
Introduction

The TPU CLI is a text-based command interface that runs locally on the RNC-AP or
OAM Proxy AP of each RNC, and is accessed by means of the OMP via the RNC-AP
or OAM Proxy AP.

PRELIMINARY

System management, methods, and procedures

CLI equivalent of GUI

All Fault management commands that can be executed by the TPU GUI can also be
executed via the TPU CLI.
Simultaneous TPU CLI and TPU GUI sessions

The maximum number of simultaneous TPU CLI and TPU GUI sessions per RNC is
limited to five.
Login to AP

To access TPU CLI, a user must first login to an RNC-AP or OAM Proxy AP, see also
Methods for RNC-AP and OAM Proxy AP login (p. 6-4). The user then types
TPUCLI at the AP login prompt, and then hits enter. See the following example:
ap21:root > TPUCLI <CR>
cPSB Traffic Processing Units Command Line Interface (TPUCLI)
Copyright (C) 2001-2002, Lucent Technologies.
Starting TPUCLI... Thu Apr 01 11:28:08 CST 2004
Session Number: TPUCLI488429
Equipped RNCs are: 1 14
TPUCLI: For help with command, enter ? or help. To exit, enter exit or quit. TPUCLI>
Important! Note that TPUCLI is case sensitive.
Once an TPU CLI session is sucessfully invoked, a user can start executing
RNC-related CLI commands via the TPU CLI.

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
6-17
Issue 14, September 2009
See notice on first page

PRELIMINARY

System management, methods, and procedures

Accessing
TICLI
...................................................................................................................................................................................................................................
Introduction

The TICLI can be used to execute legacy TI commands formerly executed via the ECP
Technician Interface CLI and RNC-AP/OAM Proxy AP commands that are executable
via the EMS CLI and MM-AP CLI.
Access via OMP

Command execution by means of the TICLI both for legacy ECP TI commands and
RNC-AP/OAM Proxy AP related TI commands is possible via the OMP.
Access via direct login

It is also possible to execute RNC-AP/OAM Proxy AP related TI commands over

TICLI via the direct login method.
Access via LMT

It is also possible to execute RNC-AP/OAM Proxy AP related TI commands over

TICLI via the LMT.
Procedures

Depending on the situation, perform the following procedures to access the TICLI:
Access via OMP (p. 6-19)
Access via direct login (p. 6-23)

PRELIMINARY

Access via LMT (p. 6-24)

6-18

Access
via OMP
...................................................................................................................................................................................................................................
Purpose

Perform this procedure to access TICLI via the OMP Technician Interface menu.
Procedure

PRELIMINARY

System management, methods, and procedures

Perform the following procedure to access TICLI via the OMP Technician Interface
menu:
...................................................................................................................................................................................................

From an OMP X-terminal, launch the AUTOPLEX(R) OMP Technician menu.

Result The following menu is displayed:
Figure 6-4 OMP Technician menu

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

Select the AUTOPLEX(R) System 1000 ECP Access menu item.

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
6-19
Issue 14, September 2009
See notice on first page

PRELIMINARY

System management, methods, and procedures

Access via OMP

Result The following menu is displayed:

Figure 6-5 ECP Access menu

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

Select the ECP RTR Shell menu item.

Result The ECP RTR shell prompt (#) displays.
...................................................................................................................................................................................................

At the ECP RTR shell prompt, ensure that TI is enabled by entering the following
command:

PRELIMINARY

apappenable -l

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

6-20

Access via OMP

Result An output similar to the following occurs:

PRELIMINARY

System management, methods, and procedures

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

Return to the AUTOPLEX(R) OMP Technician menu and select the Miscellaneous
Applications menu item.

PRELIMINARY

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
6-21
Issue 14, September 2009
See notice on first page

PRELIMINARY

System management, methods, and procedures

Access via OMP

Result The following menu is displayed:

Figure 6-6 Miscellaneous applications menu

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

Select the TICLI menu item.

Result The following TICLI prompt displays:
TICLI n >

PRELIMINARY

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

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

6-22

Access
via direct login
...................................................................................................................................................................................................................................
Purpose

Perform this procedure to access TICLI via the direct login method.
Procedure

PRELIMINARY

System management, methods, and procedures

Perform the following procedure to access TICLI via the direct login method:
...................................................................................................................................................................................................

First verify that MM-TI is enabled by performing Step 1 through Step 4 of Access via
OMP (p. 6-19).
...................................................................................................................................................................................................

Log into the MM-AP as root.

Reference See Chapter 5 (System Administration) of 401-710-201 for the different

methods for logging in.

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

Access the TICLI by executing the following command:

TICLI

Result The following TICLI prompt displays:

TICLI n >
where
n identifies one of 54 supported simultaneous TICLI sessions
END OF STEPS
...................................................................................................................................................................................................

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
6-23
Issue 14, September 2009
See notice on first page

PRELIMINARY

System management, methods, and procedures

Access
via LMT
...................................................................................................................................................................................................................................
Purpose

Perform this procedure to access TICLI via the LMT.

Procedure

Perform the following procedure to access TICLI via the LMT:

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

Connect the LMT to the RNC-AP or OAM Proxy AP.

Reference For details on connecting the LMT refer to the FMS/FWR Local

Maintenance Terminal (LMT) Users Guide, 401-710-221.

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

At the LMT terminal, login as root to the AP by entering:

ssh <apname> -l root
Where <apname> is the name of the AP.

Result The following TICLI prompt displays:

TICLI n >
where
n identifies one of 54 supported simultaneous TICLI sessions
END OF STEPS

PRELIMINARY

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

6-24

Accessing
Recent Change/Verify (RC/V)
...................................................................................................................................................................................................................................
Introduction

Access to RNC-related RC/V forms is provided by means of the OMP.

X-terminal users

PRELIMINARY

System management, methods, and procedures

For X-terminal users, the OMP provides a menu item on the OMP Technician Menu
(AUTOPLEXSystem 1000 ECP Access) that also provides access to the following
menu items that permit access to the RC/V database:

ECP Recent Change/Verify via OMP RCV

ECP Recent Change/Verify via ECP RCV

See also Figure 6-7, Accessing RC/V via OMP menus (p. 6-25).
Figure 6-7 Accessing RC/V via OMP menus

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
6-25
Issue 14, September 2009
See notice on first page

PRELIMINARY
PRELIMINARY

System management, methods, and procedures

Accessing Recent Change/Verify (RC/V)

Using RC/V

For specifics regarding the use of RC/V, refer to Volume I of the Database Update
Manual (401-610-036).

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

6-26

Accessing
Status Display Pages (SDPs)
...................................................................................................................................................................................................................................
Introduction

Access to RNC related SDPs is provided by means of the OMP.

X-terminal users

PRELIMINARY

System management, methods, and procedures

For X-terminalusers, the OMP provides a menu item on the OMP Technician Menu
(AUTOPLEX System 1000 ECP Access) that also provides access to the ECP
Control and Display interface on the ECP which in turn allows the user to bring up the
appropriate SDPs.
Using SDPs

For specifics regarding the use of SDPs, refer to Volume I of 401-610-160.

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
6-27
Issue 14, September 2009
See notice on first page

PRELIMINARY

System management, methods, and procedures

Backing up and restoring

This section provides the various procedures for backing up and restoring AP
configuration data, and the RNC database.
Configuration data

AP packages and configuration files are stored on the OMP and their respective APs.
This section explains how to use the apbackup and aprenew commands, and when to
remove old versions of packages and backed-up AP files.
RNC database

The RNC database needs to be backed up periodically and at times may need to be
restored. This section provides information on performing these tasks.

PRELIMINARY

Contents
Backing up/restoring AP configuration data

6-29

Backing up AP configuration data

6-32

Restoring AP configuration files and packages

6-34

Backing up/restoring RNC Database

6-36

Maintaining directory/file space

6-39

Backing up RNC database

6-42

Restoring RNC database

6-45

Rebooting CICCs and non-APS GICCs

6-55

Rebooting APS GICCs

6-60

6-28

Backing
up/restoring AP configuration data
...................................................................................................................................................................................................................................
Introduction

The RNC-AP and OAM Proxy AP use the Operations and Management Platform
(OMP) as a file server. Configuration files at some point need to be backed up or
restored if they become lost or corrupted.

PRELIMINARY

System management, methods, and procedures

File systems

The RNC-AP and OAM Proxy AP use the Operations and Management Platform
(OMP) as a file server for savesets and software packages. The following file systems
reside on both the OMP and APs (RNC and OAM proxy) for the savesets and
packages:
File system name

Description

/var/spool/ap/apserver_id/apbkup

The directory that contains the

version subdirectories that
contain files specific to each
version of apbackup saveset.

where
server_id = the AP (RNC or OAM proxy) number
/var/flx/bun

The directory that contains the

bundle subdirectory, with
different versions of the AP
bundle, as well as the version
subdirectories, each of which
contains files specific to a
particular version of AP platform.

apbackup command

The apbackup command is a UNIX-level (platform) script that backs up the

information and files necessary to restore the system to its current configuration. The
apbackup command is not a generalpurpose backup utility. It does not back up the
entire disk.
Files that are backed up by apbackup

The apbackup script backs up the following collection of information:

a text string that you create to describe the contents of a specific backup
a list of the AP (RNC or OAM proxy) packages and their versions that are
currently installed on the AP
a list of configuration files for installed applications (RNC or OAM proxy)

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
6-29
Issue 14, September 2009
See notice on first page

PRELIMINARY

System management, methods, and procedures

Backing up/restoring AP configuration data

high-availability framework (RCC) configuration files

user login ID information and system configuration files, such as/etc/passwd and
/etc/group
the Admin log file

The apbackup command collects this information into a backup saveset.

Files that apbackup does not back up

The apbackup command does not back up the following information:

the name or version of the MM-AP bundle.

AP (RNC or OAM proxy) packages. (The apbackup command backs up pointers to
the packages. Backup copies of the actual packages are stored on the OMP).
Customized user files and home directories.

Solaris log files.

Where the saveset is stored

The apbackup command stores the saveset on the AP (RNC or OAM proxy) and then
copies it onto the OMP. The saveset is stored on both the AP and OMP:
/var/spool/ap/apserver_id/apbkup/N
where
server_id is the AP number
N is the version number that you have assigned to a specific saveset
Sample version naming for savesets

Consider using a consistent convention to name saveset versions. For example, you
may want to use the following naming convention:
YYYYMMDD

where
YYYY is the year (four digits)
MM is the month (two digits)

PRELIMINARY

DD is the day (two digits)

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

6-30

Backing up/restoring AP configuration data

When to use apbackup

To keep AP configuration files current, execute the apbackup command to back up files
at the following times:

after you add general AP login IDs or change login ID passwords

in any procedure that causes configuration changes, for example:

as part of an AP platform Software Update (SU)

when a new application instance is configured

when you replace or add a new AP

PRELIMINARY

System management, methods, and procedures

The apbackup command can be run while the CPU is active and operational. For files
that are being updated at the time the backup is performed, the saveset includes a
snapshot of those files at the time of the backup.
Automated vs. manual execution of apbackup

Use of apbackup can be automated via cron (for example, by registering a cron job
with flxcronmgmt) or manual (see the procedurte that follows).
aprenew command

The aprenew command restores AP (RNC or OAM Proxy) packages and configuration
files on the servers. It transfers, installs, and activates packages and restores
configuration files and directories, returning an AP to a configuration state that you
specify.
Important! aprenew does not restore the AP bundle.
Managing MM-AP file systems

The MM-AP file systems (RNC-AP and OAM Proxy AP) need to be checked
periodically to see if any file systems are becoming full. See Managing MM-AP file
systems in 401-710-201 for details.
Procedures

The following procedures can be used to backup and restore AP (RNC-AP or OAM
proxy AP) files:
Backing up AP configuration data (p. 6-32)

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
6-31
Issue 14, September 2009
See notice on first page

PRELIMINARY

Restoring AP configuration files and packages (p. 6-34)

PRELIMINARY

System management, methods, and procedures

Backing
up AP configuration data
...................................................................................................................................................................................................................................
Purpose

To backup configuration data on the AP (RNC or OAM proxy) and then copy it onto
the OMP.
Reason to perform

Periodically, to keep thebackup configuration data as current as possible.

Procedure

To execute a backup of the configuration data, perform the following:

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

or
su <system administrator login>

where <system administrator login> is the System Administrator login.

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

Execute the following command:

apbackup -t text_string

where
text_string equals text that you enter to distinguish one saveset from another such as

Installed RNC-AP SU AP22.0.0003

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

PRELIMINARY

Specify the following when prompted:

The version of the desired backup saveset. (The default is YYYYMMDD. Press
Return to accept the default or specify a specific version.)

The login ID on the OMP. (Press Return to accept the default (root) or specify a
login ID that has root permission.)

The password of the OMP login ID. (No default option is provided.)

6-32

Backing up AP configuration data

Result The result of the backup (success or failure) is displayed.

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

Repeat Step 1 through Step 3 for each AP that you want to back up.
E...................................................................................................................................................................................................
ND OF STEPS

PRELIMINARY

System management, methods, and procedures

Execute apbackup with specific parameters

To specify parameters on the apbackup command instead of being prompted for them,
execute the complete apbackup command line as follows:
apbackup [-v backup_version] [-t text string] [-s server] [-l login]
[-z password]

where
-v is the version of this backup saveset
-t a text string that you can associate with this backup saveset
-s the node name of the remote server (the default is apomp)
-l (minus sign and lowercase letter L) is the login ID on the remote server

Note: If you do not specify root as the login ID on the OMP, the login ID that you
specify must have superuser (su) permission to the /var/spool/ap directory and
subdirectories.

PRELIMINARY

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
6-33
Issue 14, September 2009
See notice on first page

PRELIMINARY

System management, methods, and procedures

Restoring
AP configuration files and packages
...................................................................................................................................................................................................................................
Purpose

To restore configuration files and directories, to return an AP to a configuration state

that you specify.
Reason to perform

When you are troubleshooting an AP or when you replace a server boot drive.
Procedure

To execute a restore of the configuration data, perform the following:

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

Log in to an AP as root or System Administrator or Security Administrator.

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

Execute the following command to take the AP server offline:

apoffline
...................................................................................................................................................................................................

Execute the following command:

Specify the following when prompted:

The version of the desired backup saveset. (The version number that you enter
must correspond to the version that you want restored. If you do not know what the
version number is, log in to the OMP and find the saveset that you want to restore
under /var/spool/ap/apXX/apbkup, where XX is the AP number.)

The login ID on the OMP (known as apomp by the AP).(Press Return to accept the
default (root) or specify a login ID that has root superuser permission.)

The password of the OMP login ID. (No default option is provided.)
Continue aprenew or exit the program. (Press Return to continue.)
Result Continue aprenew or exit the program. (Press Return to continue.)

PRELIMINARY

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

Execute the following command to activate AP platform processes:

aponline

6-34

Restoring AP configuration files and packages

Result The AP server reboots.

To execute aprenew with specific parameters

To specify parameters on the aprenew command line instead of being prompted for
them, execute the complete command line as follows:

PRELIMINARY

System management, methods, and procedures

aprenew [-v backup_version] [-s server] [-l login] [-z password]

where
-v is the version of this backup saveset
-s the node name of the remote server (the default is apomp)
-l (minus sign and lowercase letter L) is the login ID on the remote server

Important! If you do not specify root as the login ID on the OMP, the login ID
that you specify must have superuser (su) permission to the /var/spool/ap directory
and subdirectories.
-z the password of the login ID on the remote server

PRELIMINARY

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
6-35
Issue 14, September 2009
See notice on first page

PRELIMINARY

System management, methods, and procedures

Backing
up/restoring RNC Database
...................................................................................................................................................................................................................................
Introduction

CLI commands are used to backup and restore the RNC Database (RNC DB), and to
also delete obsolete RNC database archive files.
Backup command

The BKUP (backup) command will result in a backup copy of the RNC DB on both
OAM Proxy APs. Each backup copy will be archived in the
$CDMA_OAM_ROOT/rncdbbackups directory.
Backups can be performed for all the RNCs at one time, or on individual RNCs.
Major backup

A backup for all RNCs is considered a Major backup. A Major backup includes a
backup for the data comon to all RNCs. A Major backup archive file is designated with
a trailing zero. For example:
rnc24_1.0, rnc24_2.0
Minor backup

A backup for an individual RNC is considered a Minor backup. A Minor backup

archive file is designated with a trailing whole number, other than zero. For example:
rnc24_1.1, rnc24_2.3, rnc24_10.11
Common data warning

If a Minor backup is performed on an individual RNC, and the common data across all
RNCs has changed, the backup will fail and a message informing the user that,
common data has changed since the last complete RNC backup will be output on the
CLI and ROP. It will then be necessary to perform a Major backup across all RNCs.
Restore command

The COPY (restore) command will restore the RNC DB for all RNCs, or an individual
RNC, using the most recent backup file (as specified by the system user) from the
$CDMA_OAM_ROOT/rncdbbackups directory.

PRELIMINARY

Major restore

A restore for all RNCs is considered a Major restore. A Major restore includes a
restore for the data comon to all RNCs.
Minor restore

A restore for an individual RNCs is considered a Minor restore and will not restore
data common to all RNCs.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

6-36

Backing up/restoring RNC Database

Common data warning

If a restore is performed across all RNCs and the archive file used for the restore was
generated for a Minor backup, or does not have the most current common data, then
the restore will fail, and a message informing the user to specify a backup file
generated from the most current Major backup will be output.
Note that the archive that is suggested will be the most recent archive. The system user
could, in fact, roll back to an older major archive, if preferred.

PRELIMINARY

System management, methods, and procedures

It will then be necessary to perform a restore using that specific archived file.
Configuration data restore

A restore of configuration data for all RNCs, or an individual RNC may require the
config.ini file to be FTPd to both TPU shelves, and the equipment onthe TPUs to be
rebooted. This involves a redownload of the config.ini files and a reset of all of the
SC-GICCs, GICCs, and CICCs associated with an RNC, or all RNCs.
Note that this will only be necessary when static (non-dynamic data) has changed. A
message will appear in the CLI and ROP output informing you when this will be
required.
ECP database synchronization

When a major backup is performed, the RC/V database data that has been provisioned
via the ECP RC/V screens is synchronized with the values in the RNCB. However, if
at some point in time after a major backup is performed an RC/V field or fields are
updated, and the Service Provider subsequently performs a restore of all RNC data, the
RC/V data that was updated will not restore to the value settings in place at the time of
the last major backup.
This is due to the fact that an internal RNCDB audit fires and restores all new value
settings performed in the RC/V database since the last major backup; in effect
overriding the previous value settings in place at the time of the last major backup.
This thus ensures that the new value settings are preserved.
However, in a case where a Service Provider makes an RC/V update official, and then
discovers that the update has created a problem and wishes to restore the database back
to the original value setting(s), the new data will override the previous data.
In that event you would need to either:
Manually restore the previous data value(s) in the RC/V field(s).
Perform a major restore of the ECP database.

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
6-37
Issue 14, September 2009
See notice on first page

PRELIMINARY

System management, methods, and procedures

Backing up/restoring RNC Database

Maintaining rncdbbackups directories

Up to 25 archive files can be contained in the rncdbbackups directories. If you attempt

a backup, and the directories are at full archive capacity, the backup will fail, and a
message indicating, maxed out rncdbbackup directories will be output on the CLI
and ROP. It will then be necessary to delete at least one of the old archive files before
you can proceed.
Note also that the archive numbering scheme is cummulative, so that when the major
rncdbbackup directory name reaches 99 (for example, rnc25_99.0) the RNCDB backup
tool will reset the number to 1, or the next available number, so that existing archives
are not overwritten.
Delete backup command

The DELBKUP command is provided to enable system users to delete obsolete archive
files. The DELBKUP command will simultaneously remove archived files from both
rncdbbackup directories on both the OAM Proxy APs.
To prevent the failure of a backup as a result of maxed out rncdbbackup directories,
periodically delete the older archived files.
Procedures

The procedures for backing up, restoring, and maintaining backup directories for the
RNC DB, are as follows:
Maintaining directory/file space (p. 6-39)
Backing up RNC database (p. 6-42)

PRELIMINARY

Restoring RNC database (p. 6-45)

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

6-38

Maintaining
directory/file space
...................................................................................................................................................................................................................................
Purpose

To ensure that the rncdbbackups directories provided on the OAM Proxy APs do not
exceed 25 archive files.

PRELIMINARY

System management, methods, and procedures

Reason to perform

To prevent a backup failure due to a lack of available archive file space in the
rncdbbackups directories on the OAM Proxy APs.
Procedure

Perform the following procedure to remove older version archive files on the OAM
Proxy APs:
...................................................................................................................................................................................................

Obtain access to the TICLI (see Accessing TICLI (p. 6-18)).

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

Check the number of files in the rncdbbackups directory by executing the following
command:
OP:RNCDB,RNC ALL<CR>

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
6-39
Issue 14, September 2009
See notice on first page

PRELIMINARY

System management, methods, and procedures

Maintaining directory/file space

Result An output similar to the following example will occur:

1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
M 05 OP:RNCDB,RNC 14! IN COMPLETED
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
Archive AP(s) RNC(s) Timestamp Single RNC Rst Alw
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
rnc24_8.0 21,22 14 Oct 06 15:03:43 Yes
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
rnc24_7.2 21,22 14 Oct 06 12:03:01 No, run rnc24_8.0
1234567890123456789012345678901212345678901234567890123456789
rnc24_7.0 21,22 14 Oct 06 11:18:28 No, run rnc24_8.0
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
rnc24_6.0 21,22 14 Oct 06 10:05:15 No, run rnc24_8.0
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
rnc24_5.0 21,22 14 Oct 06 09:37:47 No, run rnc24_8.0
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
rnc24_12.0 67,68 14 Sep 30 15:56:56 No, run rnc24_8.0
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
rnc24_12.1 67,68 14 Sep 30 15:56:56 No, run rnc24_8.0
1234567890123456789012345678901212345678901234567890123456789
rnc24_12.2 67,68 14 Sep 30 15:56:56 No, run rnc24_8.0
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
rnc24_12.3 67,68 14 Sep 30 15:56:56 No, run rnc24_8.0
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
rnc24_12.4 68 14 Sep 30 15:56:56 No, run rnc24_8.0
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
rnc24_12.5 67,68 14 Sep 30 15:56:56 No, run rnc24_8.0
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
rnc24_12.6 67,68 14 Sep 30 15:56:56 No, run rnc24_8.0
1234567890123456789012345678901212345678901234567890123456789
rnc24_12.7 67,68 14 Sep 30 15:56:56 No, run rnc24_8.0
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
rnc24_12.10 67,68 14 Sep 30 15:56:56 No, run rnc24_8.0
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
rnc24_12.11 67,68 14 Oct 15 15:56:56 No, run rnc24_8.0
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
rnc24_12.12 67,68 14 Sep 30 15:56:56 No, run rnc24_8.0
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
rnc24_12.14 67,68 14 Sep 30 15:56:56 No, run rnc24_8.0
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
ORIGINATING COMMAND #329058802.12
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
2004-10-06 15:05:27 REPORT #000001
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
EXECUTED ON PROCESSOR: AP 2110/06/04 15:05:32 #002774
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
...................................................................................................................................................................................................

If the archive file space is approaching the maximum of 25 files, proceed to Step 4.
...................................................................................................................................................................................................

To delete an old archive file from both rncdbbackups directories on the OAM Proxy
APs, enter the following command:
DELBKUP:RNCDB,DIRNAME rncXX_YY.YY<CR>

where
XX = the Release number of the archive file, e.g., 24.0, 25.0

PRELIMINARY

YY.YY = the incremental archive file number

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

6-40

Maintaining directory/file space

Result An output similar to the following example occurs:

PRELIMINARY

System management, methods, and procedures

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

Repeat Step 4 for as many archive files as required.

END OF STEPS
...................................................................................................................................................................................................

PRELIMINARY

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
6-41
Issue 14, September 2009
See notice on first page

PRELIMINARY

System management, methods, and procedures

Backing
up RNC database
...................................................................................................................................................................................................................................
Purpose

To ensure that a backup database version copy is available in the event of a single AP
failure.
Reason to perform

To keep the backup database version data as current as possible.

Frequency for performing

A backup of the RNC database should be performed daily.

Before you begin

Ensure that older (obsolete) versions of the RNC DB backup files in the
$CDMA_OAM_ROOT/rncdbbackups directories on the OAM Proxy APs have been
deleted to allow room for the most current version, see Maintaining directory/file
space (p. 6-39).
Duration

Running a backup for an individual RNC, or all RNCs should not take more than a
minute.
Procedure

To execute a backup of the RNC database, perform the following procedure:

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

Obtain access to the TICLI (see Accessing TICLI (p. 6-18)).

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

Archive the RNC database on both OAM Proxy APs, as follows:

1. For all RNCs, execute the following command:
BKUP:RNCDB,RNC ALL<CR>

2. For an individual RNC, execute the following command:

PRELIMINARY

BKUP:RNCDB,RNC XX<CR>

where:
XX = the number of the individual RNC

6-42

Backing up RNC database

Result Depending on the command that was entered, output examples are given as

follows:
1. For all RNCs:

PRELIMINARY

System management, methods, and procedures

2. For an individual RNC:

PRELIMINARY

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
6-43
Issue 14, September 2009
See notice on first page

PRELIMINARY

System management, methods, and procedures

Backing up RNC database

In a situation where common data has changed, you will have to re-execute the backup
across all RNCs.
END OF STEPS

PRELIMINARY

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

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

6-44

Restoring
RNC database
...................................................................................................................................................................................................................................
Purpose

To restore the RNC database on an individual RNC, or across all RNCs.

Reason to perform

PRELIMINARY

System management, methods, and procedures

The existing data has become corrupted in some fashion and you now need to restore
data from the most recent backup archive file.
Service-affecting download

After the RNC database is restored, it will sometimes be necessary to redownload the
config.ini files, and reset all the SC-GICCs, GICCs and CICCs for specific TPUs or all
TPUs. This task will be accomplished via the Installation Options page and the TPU
Network Elements page of the TPU-GUI.
Output message

The output message will specify when it is necessary to reboot any or all TPU shelves.
Minimizing reset impact

The reset impact to non-APS gateway services (GICCs) and traffic processors (CICCs)
will be minimized by use of the Shutdown command, which allows for traffic to
drain before entering into the locked state prior to initiating a reset.
Duration

Including the dynamic data portion, it could take up to 10 minutes for the dynamic
portion and two minutes for the RNCDB restore,. A total of 10 to 12 minutes.
A redownload of the config.ini files, and a reset of one RNCs TPU shelves will add
about 30 additional minutes.
Screen refresh

When using the Installation Options or TPU Network Elements pages of the TPU
GUI it will be necessary to periodically refresh your Web browser to track the
real-time progress of user-initiated commands. You should never proceed, until you are
sure that a previous action has completed.

To execute a restore of the RNC database, perform the following procedure:

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

Obtain access to the TICLI (see Accessing TICLI (p. 6-18)).

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
6-45
Issue 14, September 2009
See notice on first page

PRELIMINARY

Procedure

PRELIMINARY

System management, methods, and procedures

Restoring RNC database

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

Depending on your preference, restore the RNC database as follows:

1. For all RNCs, execute the following command:
COPY:RNCDB,RNC ALL,DIRNAME rncXX_YY.YY<CR>

2. For an individual RNC, execute the following command:

COPY:RNCDB,RNC ZZ,DIRNAME rncXX_YY.YY<CR>

where:
XX = the Release number of the archive file, e.g., 24.0, 25.0
YY.YY = the incremental archive file number
ZZ = the RNC number
Result Depending on the command that was entered, output examples are given as

follows:
1. For all RNCs (no TPU reboot required):

PRELIMINARY

2. For an individual RNC (no TPU reboot required):

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

6-46

Restoring RNC database

PRELIMINARY

System management, methods, and procedures

3. For all RNCs (TPU reboot required):

PRELIMINARY

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
6-47
Issue 14, September 2009
See notice on first page

PRELIMINARY

System management, methods, and procedures

Restoring RNC database

PRELIMINARY

Depending on the output, any of the following is true:

The restore was successful, no further action is required.

The restore was unsuccessful due to a common data issue. Proceed as directed by
the output message.
A download of the config.ini files will be necessary. Perform the following steps
for each TPU specified in the output message.

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

6-48

Restoring RNC database

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

Bring up the TPU-GUI and navigate to the Installation Options page. Determine
which TPU or TPUs need to be updated and proceed as follows.
...................................................................................................................................................................................................

At the Installation Options page (see Figure 6-8, Standby GICC and bundle
verification (p. 6-49)):

PRELIMINARY

System management, methods, and procedures

1. Verify which SC-GICC is standby (indicated by a half-green, half-gray capsule).

2. Verify that the bundle version in the Bundle Version: box matches the Appl
Version for the SC-GICCs.
Figure 6-8 Standby GICC and bundle verification

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

Via the Cmds pull down menu, choose Install for the standby GICC and then choose
Submit (see Figure 6-9, Cmds pull down menu (p. 6-49)).
Figure 6-9 Cmds pull down menu

PRELIMINARY

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
6-49
Issue 14, September 2009
See notice on first page

PRELIMINARY

System management, methods, and procedures

Restoring RNC database

Result The Confirm command execution box appears (see Figure 6-10, Confirm

install (p. 6-50)).

Figure 6-10 Confirm install

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

PRELIMINARY

Click on OK.

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

6-50

Restoring RNC database

Result The Update Installation box appears (see Figure 6-11, Update installation

(p. 6-51)).
Figure 6-11 Update installation

PRELIMINARY

System management, methods, and procedures

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

Ensure that only the boxes shown in Figure 6-11, Update installation (p. 6-51) are
checked and then click OK.

PRELIMINARY

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
6-51
Issue 14, September 2009
See notice on first page

PRELIMINARY

System management, methods, and procedures

Restoring RNC database

Result The following sequence of screens (Figure 6-12, Issuing lock (p. 6-52)

through Figure 6-19, Second SC-GICC installation complete (p. 6-53)) show
various stages of the download. See also Screen refresh (p. 6-45).
Figure 6-12 Issuing lock

Figure 6-13 Issuing shutdown

Figure 6-14 Issuing unlock

PRELIMINARY

Figure 6-15 Installation complete (standby GICC)

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

6-52

Restoring RNC database

Figure 6-16 Install command invoked

PRELIMINARY

System management, methods, and procedures

Figure 6-17 Issuing second shutdown

Figure 6-18 SC-GICC reboots

Figure 6-19 Second SC-GICC installation complete

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
6-53
Issue 14, September 2009
See notice on first page

PRELIMINARY

Note that in this Result example, the SC-GICC that was previously standby is now
active, and the SC-GICC that was previously active is now standby.

PRELIMINARY

System management, methods, and procedures

Restoring RNC database

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

The non-shelf controller GICCs and the CICCs now need to be reset. You can either
first reset all the CICCs and then the GICCs, or vice-versa. See Rebooting CICCs and
non-APS GICCs (p. 6-55) and Rebooting APS GICCs (p. 6-60) as applicable.
...................................................................................................................................................................................................

Perform Step 1 through Step 9 for all applicable RNCs.

END OF STEPS

PRELIMINARY

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

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

6-54

Rebooting
CICCs and non-APS GICCs
...................................................................................................................................................................................................................................
Purpose

To reboot all CICCs and non-APS GICCs for specific TPUs, or all TPUs in an MSC.
Reason to perform

PRELIMINARY

System management, methods, and procedures

The config.ini files have been downloaded, and blades for specific TPUs, or all TPUs
in an MSC must be reset.
Service-affecting download

The reset impact to traffic processors (CICCs) will be minimized by use of the
Shutdown command, which allows for traffic to drain before entering into the locked
state prior to a technician initiated reset.
The reset impact to gateways (GICCs) will be minimized by use of the Shutdown
command, which will allow no new calls, and automatically lock after approximately
two minutes, prior to a technician initiated reset.
Duration

A redownload of the config.ini files, and a reset of one RNCs TPU shelves (that is, all
CICCs and non-APS GICCs) will take about 30 minutes.
Screen refresh

When using the TPU Network Elements pages of the TPU GUI it will be necessary to
periodically refresh your Web browser to track the real-time progress of user-initiated
commands. You should never proceed, until you are sure that a previous action has
completed.
Procedure
...................................................................................................................................................................................................

At the TPU GUI, navigate to the TPU Network Elements page and use the Filter: box
to filter on only the CICCs or GICCs. (See example screen that follows.)

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
6-55
Issue 14, September 2009
See notice on first page

PRELIMINARY

System management, methods, and procedures

Rebooting CICCs and non-APS GICCs

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

Initiate a shutdown on the top-shelf CICC or GICC, by using the pull-down menu and
clicking on Submit. (See example screen that follows.)

Result Once a shutdown is initiated and accepted, no new call traffic will be

processed by the:

CICC and all current traffic will drain by attrition until the shutdown (lock)
completes.
GICC and the GICC will automatically lock after approximately two minutes.

PRELIMINARY

Status is indicated by the locked Admin state capsule and idle Usage State
capsule associated with the three CICC processor rows, or single GICC processor
row. (See example screen that follows.)

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

6-56

Rebooting CICCs and non-APS GICCs

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

Initiate a reset on the top-shelf CICC or GICC, by using the pull-down menu and
clicking on Submit. (See example screen that follows.)

PRELIMINARY

System management, methods, and procedures

Result The Confirm command execution box appears. (See example screen that

follows.)

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

Click on OK.
Result The reset is accepted as shown in the Command Status column. (See

example screen that follows.)

Either wait until the screen automatically refreshes, or do a manual refresh of the
browser to determine if the reset has completed (indicated by blank cells in the
Command Status column).

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
6-57
Issue 14, September 2009
See notice on first page

PRELIMINARY

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

PRELIMINARY

System management, methods, and procedures

Rebooting CICCs and non-APS GICCs

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

Initiate an unlock on the top-shelf CICC or GICC, by using the pull-down menu and
clicking on Submit. (See example screen that follows.)

Result The Confirm command execution box appears. (See example that

follows.)

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

Click on OK.
Result The Admin state of the CICC or GICC becomes unlocked. (See example

PRELIMINARY

screen that follows.)

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

6-58

Rebooting CICCs and non-APS GICCs

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

In the same manner perform Step 2 through Step 7 for all applicable CICCs and
GICCs.
END OF STEPS
...................................................................................................................................................................................................

PRELIMINARY

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
6-59
Issue 14, September 2009
See notice on first page

PRELIMINARY

System management, methods, and procedures

PRELIMINARY

System management, methods, and procedures

Rebooting
APS GICCs
...................................................................................................................................................................................................................................
Purpose

To reboot APS GICCs for specific TPUs or all TPUs.

Reason to perform

The config.ini files have been downloaded, and APS GICCs for specific TPUs, or all
TPUs must be reset.
Service-affecting download

The reset impact to gateways (GICCs) will be minimized by virtue of the fact that the
reset is always performed on the standby, locked GICC of the pair.
Duration

A redownload of the config.ini files, and a reset of one RNCs TPU shelves (that is,
both APS GICCs and CICCs) will take about 30 minutes.
Screen refresh

Perform the following procedure to reboot APS GICCs for specific TPUs or all TPUs:
...................................................................................................................................................................................................

PRELIMINARY

At the TPU GUI, navigate to the TPU Network Elements page (see example screen
that follows) and use the Filter: box to filter on only the GICCs.

6-60

Rebooting APS GICCs

PRELIMINARY

System management, methods, and procedures

Important! The GICC in the upper TPU shelf is normally always active, and the
GICC in the lower TPU shelf is normally always standby.
Result The RNC related GICCs are displayed. Note that, the abscence of a yellow

star next to a GICC in a mated pair indicates that the GICC without a yellow star
is in standby mode.
...................................................................................................................................................................................................

On the TPU Network Elements page identify the standby GICC that you wish to
reboot, and choose Lock via the Commands column, and then select Submit.
Result The GICC immediately transitions to the states indicated in the following

table.
Oper State

Usage State

Locked

Disabled

Idle

See Figure 5-1.Figure 5-1,

Operational state (p. 5-5)
for capsule correlation.

See Figure 5-2Figure 5-2,

Usage state (p. 5-6) for
capsule correlation.

See Figure 5-3Figure 5-3,

Administrative state
(p. 5-7) for capsule
correlation.

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
6-61
Issue 14, September 2009
See notice on first page

PRELIMINARY

Admin State

PRELIMINARY

System management, methods, and procedures

Rebooting APS GICCs

Either wait until the screen automatically refreshes, or do a manual refresh of the
TPU Network Elements page to confirm that the GICC that you intend to reboot
has transitioned to the required states.
...................................................................................................................................................................................................

Initiate a reset on the locked GICC, by using the pull-down menu of the Commands
column, and clicking on Submit.
Result The Confirm command execution box appears. (See example screen that
follows.)

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

Click on OK.
Result The reset is accepted and can be confirmed in the Command Status

column.
Either wait until the screen automatically refreshes, or do a manual refresh of the
browser to determine that the reset has completed (indicated by blank cells in the
Command Status column).
...................................................................................................................................................................................................

PRELIMINARY

Initiate an unlock on the locked GICC, by using the pull-down menu in the Command
Status column, and clicking on Submit.

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

6-62

Rebooting APS GICCs

Result The Confirm command execution box appears. (See example that

follows.)

PRELIMINARY

System management, methods, and procedures

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

Click on OK.
Result The GICC immediately transitions to the states indicated in the following

table.
Admin State

Oper State

Usage State

Unlocked

Enabled

Idle

See Figure 5-3Figure 5-3,

Administrative state
(p. 5-7) for capsule
correlation.

See Figure 5-1Figure 5-1,

Operational state (p. 5-5)
for capsule correlation.

See Figure 5-2Figure 5-2,

Usage state (p. 5-6) for
capsule correlation.

Either wait until the screen automatically refreshes, or do a manual refresh of the
TPU Network Elements page to confirm that the GICC has transitioned to the
required states.
...................................................................................................................................................................................................

Run the SWITCHTOMATE command (via theCommands column) on the active GICC
that is mated to the GICC that you just unlocked by using the pull-down menu in the
Command Status column, and then clicking on Submit.
standby GICC transitions to active.
Either wait until the screen automatically refreshes, or do a manual refresh of the
TPU Network Elements page to confirm that the active GICC has transitioned to

standby (abscence of a yellow star), and the previously standby GICC has
transitioned to active (prescence of a yellow star).
....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
6-63
Issue 14, September 2009
See notice on first page

PRELIMINARY

Result The previously active GICC transitions to standby, and the previously

PRELIMINARY

System management, methods, and procedures

Rebooting APS GICCs

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

Perform Step 2 through Step 7 for the other GICC in the pair.
...................................................................................................................................................................................................

Perform Step 2 through Step 8 for all remaining GICCs in the RNC.
END OF STEPS

PRELIMINARY

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

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

6-64

PRELIMINARY

Part III: Fault management

Fault management is the set of tasks in the International Telecommunications Union

(ITU) standard that are associated with detecting, diagnosing, isolating and recovering
from fault conditions in the network.
Objectives

The chapters provided within this Part should enable users to:

Identify the various tools available for detecting, diagnosing, isolating, and
recovering from faults that occur in the RNC including:

EMS-GUI
TPU-GUI and TPU CLI

SDPs

ROP
log files

Use those tools to perform fault management on the RNC, for example:

Monitoring and determining the maintenance and alarm states of the

RNC-related elements.

Diagnosing the RNC-related element.

Restore the RNC-related element to service, unless the problem lies outside of the
scope of the procedures provided in Chapter 8, Troubleshooting.

Monitoring

EMS-GUI (RNC-AP detailed alarms and summary alarms for the RNC TPUs)

SDP (summary alarms for each RNC)

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
III-1
Issue 14, September 2009
See notice on first page

PRELIMINARY

All alarms and fault events are sent to the following, to provide system users with
real-time monitoring capability:

PRELIMINARY

Fault management

Overview

TPU-GUI (detailed alarms for TPU)

ROP (all detailed alarms)

external log files (all detailed alarms)

Depending upon which OA&M user interface is preferred (GUI, SDP, ROP or logs) a
system user is able to monitor the integrity of the RNC-related elements.
Command Line Interface (CLI)

Additional monitoring capability is also provided by the use of input commands

executed via the TPU-CLI and TI CLI
GUI types

The RNC-related elements are managed either via the EMS-GUI or the TPU-GUI.
RNC-APs

RNC-APs are managed by EMS, which is the same interface used to manage existing
MM-APs.
TPU shelf

The TPU shelf is managed by the TPU-GUI which uses an Apache web server that
runs on the OAM AP proxy.
Fault management overview

PRELIMINARY

The Figure that follows provides an overview of fault mangement essentially from the
GUI perspective. Note that both the TPU-GUI and TPU-CLI return the same fault
management information about the TPU shelf.

III-2

Overview

PRELIMINARY

Fault management

Contents
Chapter 7, Monitoring the system

7-1

Chapter 8, Troubleshooting

8-1

Chapter 9, Replace components

9-1

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
III-3
Issue 14, September 2009
See notice on first page

PRELIMINARY

7M onitoring the system

To provide information that pertains to monitoring the system elements such as the
RNC-APs, OAM proxy AP, and TPUs.
Contents
Monitoring status via SDP

7-2

Monitoring RNC-AP/OAM proxy AP activities

7-4

Monitoring RNC/TPU activites

7-13

Monitoring RNC-related activities via logs

7-28

Accessing Admin logs

7-33

Monitoring activities via Read-Only Printer (ROP)

7-36

Crossover LAN connectivity monitoring

7-38

Cross-over LAN cable connection and verification

7-39

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
7-1
Issue 14, September 2009
See notice on first page

PRELIMINARY

Monitoring the system

Monitoring
status via SDP
...................................................................................................................................................................................................................................
Introduction

Because the RNC is managed by software residing on the RNC-APs and all APs use
EMS as their primary means for fault status and isolation, SDP pages are not
considered the primary means for drilling down to the other major and minor
components that comprise the RNC. However, as an existing legacy interface, SDP can
still be used to determine RNC-AP, OAM Proxy AP, and TPU status.
RNC summary status indicator

All SDP pages now provide an RNC Summary Status indicator (RNC) in the Status
Summary Area at the top of the page for any configuration that contains one or more
RNCs, as shown in the example of Figure 7-1, Typical example of RNC SDP status
indicator (p. 7-2).
Figure 7-1 Typical example of RNC SDP status indicator

PRELIMINARY

The RNC summary indicator on the SDP will indicate the condition of either of the
RNC-APs, and the equipment in the cPSB frame, as follows:

the status of the RNC-APs

the status of RNC-AP applications (RNC-M and RNC VCVM)

alarms associated with the TPU

7-2

Monitoring status via SDP

This indicator is the flag that triggers the technician to traverse the RNC cloud at the
EMS to begin tracking the problem.
Existing MM-AP indicator

The existing MM-AP indicator on the SDP will NOT light if any of the RNC-AP pairs
has trouble. This is because the RNC-APs are logically a part of the RNC, and are
therefore included in the RNC indicator, and not the MM-APindicator.

PRELIMINARY

Monitoring the system

In the case of the OAM Proxy AP, however, the MM-AP indicator will be used to
indicate problems with the OAM Proxy AP.
Supporting Documentation

For details concerning all RNC-related SDP modifications, refer to 401-610-160

Volume I.

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
7-3
Issue 14, September 2009
See notice on first page

PRELIMINARY

Monitoring the system

Monitoring
RNC-AP/OAM proxy AP activities
...................................................................................................................................................................................................................................
Introduction

The EMS-GUI, and TICLI provide the means for the monitoring of the activities
associated with maintaining the RNC-related application processors.
Types of tasks

The types of real-time tasks that can be determined are listed as follows:

Maintenance states

Alarm status
Software versions

Command status in queue

EMS-GUI

PRELIMINARY

Monitoring these real-time activities via the EMS-GUI is a simple task. By accessing
the EMS-GUI and navigating to the specific processor page, the system user can pick
the task and then navigate to the appropriate page to obtain the desired information
(see the examples of Figure 7-2, RNC-AP activity status monitoring (p. 7-5) through
Figure 7-7, TPU GUI status (p. 7-10)).

7-4

Monitoring RNC-AP/OAM proxy AP activities

Figure 7-2 RNC-AP activity status monitoring

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
7-5
Issue 14, September 2009
See notice on first page

PRELIMINARY

Monitoring the system

PRELIMINARY
PRELIMINARY

Monitoring the system

Monitoring RNC-AP/OAM proxy AP activities

Figure 7-3 RNCM status page

7-6

Monitoring RNC-AP/OAM proxy AP activities

Figure 7-4 TCS status page

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
7-7
Issue 14, September 2009
See notice on first page

PRELIMINARY

Monitoring the system

PRELIMINARY
PRELIMINARY

Monitoring the system

Monitoring RNC-AP/OAM proxy AP activities

Figure 7-5 OAM Proxy AP activity status monitoring

7-8

Monitoring RNC-AP/OAM proxy AP activities

Figure 7-6 RNC-DBMS status

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
7-9
Issue 14, September 2009
See notice on first page

PRELIMINARY

Monitoring the system

PRELIMINARY
PRELIMINARY

Monitoring the system

Monitoring RNC-AP/OAM proxy AP activities

Figure 7-7 TPU GUI status

7-10

Monitoring RNC-AP/OAM proxy AP activities

MM-AP CLI

When the EMS-GUI is unavailable, it is still possible to perform monitoring activities

by the use of commands executed by means of the Command Line Interface (CLI).
The commands and outputs used for these monitoring activities are provided in Table
7-1, Monitoring Activity via CLI (p. 7-11).
Table 7-1

Monitoring Activity via CLI

Input
Command

Function

Output
Message

Function

OP:APALARM

Reports the alarms that

have been generated
autonomously for the
specified RNC-AP or
OAM proxy AP.

OP-APALARM

Alarm information,
alarm severity and
alarm description, are
provided by this
message for alarms that
have been autonomously
generated for an
RNC-AP or OAM Proxy
AP.

OP:AP-CMDS

This command outputs a

list of running
commands and queued
commands.

OP-AP-CMDS

Indicates any running

command and how
many seconds there are
until it exceeds its
command timer.

OP:APSTATUS

Reports the maintenance

status of an RNC-AP or
OAM Proxy AP.

OP-APSTATUS

Indicates the
maintenance status of
all the elements
associated with the
RNC-AP or OAM Proxy
AP.

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
7-11
Issue 14, September 2009
See notice on first page

PRELIMINARY

Monitoring the system

PRELIMINARY

Monitoring the system

Table 7-1

Monitoring RNC-AP/OAM proxy AP activities

Monitoring Activity via CLI (continued)

Input
Command

Function

Output
Message

Function

OP:APVERSION

This command reports

the following:

OP-APVERSION

The version information

is provided. This output
may be spread across
several messages.

- The running version of

platform software.
- The new version of
platform software on the
RNC-AP or OAM Proxy
AP (if it exists), or the
backout version of
platform software on the
RNC-AP or OAM Proxy
AP (if it exists).

PRELIMINARY

- The version of
platform software
selected on the RNC-AP
or OAM Proxy AP.
OP:TCS AUD

Reports a list of
currently inhibited
audits.

OP-TCS AUD

Indicates a list of
currently inhibited
audits.

OP:TCS
AUD;PRINT

Reports a list of
currently inhibited
audits that are being
reported on the ROP

OP-TCS
AUD;PRINT

Indicates a list of
currently inhibited
audits that are being
reported on the ROP

7-12

Monitoring
RNC/TPU activites
...................................................................................................................................................................................................................................
Introduction

The TPU-GUI and TPU CLI provide the means for the monitoring of the elements
associated with maintaining the RNC and TPU.

PRELIMINARY

Monitoring the system

Monitoring real-time activities via TPU GUI

Monitoring of real-time activities is made possible by accessing the 1X RNC TPU web
page (Figure 7-8, 1X RNC TPU web page (p. 7-13)) and using the Configuration
Data, Installation & Software Updates, Network Elements, and Alarms icons. By
these means, a system user can navigate to the appropriate page to obtain the desired
information.
Figure 7-8 1X RNC TPU web page

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
7-13
Issue 14, September 2009
See notice on first page

PRELIMINARY

Monitoring the system

Monitoring RNC/TPU activites

Types of monitoring via TPU GUI

The types of monitoring activities that can be initiated via TPU GUI are listed as
follows:

High-level RNC alarm and maintenance states (Figure 7-9, 1X RNC Summary
page (p. 7-15)).
Installation status and software versions (Figure 7-10, Installation and software
options page (p. 7-16)).
Network elements as follows:

Equipped cards and their associated maintenance states and alarm states (see
Figure 7-11, TPU network elements (filter all) page (p. 7-17)).

PRELIMINARY

Assert brevity status and call processing summary (see Figure 7-11, TPU
network elements (filter all) page (p. 7-17)).
A8A9/A10/A11 status for SC-GICCs. Most easily viewable by using filtering
option available via the screen.
Alarm information, regarding RNC- related managed resources, such as severity,
event occurance, and brief details (Figure 7-12, TPU alarms page (p. 7-18)).
Failed PVC (Permanent Virtual Circuit) status Figure 7-13, Failed PVCs page
(p. 7-19)).
APS-related 5EGW data (Figure 7-14, APS status (p. 7-20)).
BPCF performance data (Figure 7-15, B-PCF performance statistics (p. 7-21)).
RNC IP Address related information (Figure 7-16, 1X-RNC information page
(p. 7-21))
General RNC call processing status for all MSC associated RNCs (see Figure 7-17,
RNC call processing status page (p. 7-22))
GICC BHS status (Figure 7-18, BHS statistics (p. 7-22).)

7-14

Monitoring RNC/TPU activites

Figure 7-9 1X RNC Summary page

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
7-15
Issue 14, September 2009
See notice on first page

PRELIMINARY

Monitoring the system

PRELIMINARY
PRELIMINARY

Monitoring the system

Monitoring RNC/TPU activites

Figure 7-10 Installation and software options page

7-16

Monitoring RNC/TPU activites

Figure 7-11 TPU network elements (filter all) page

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
7-17
Issue 14, September 2009
See notice on first page

PRELIMINARY

Monitoring the system

PRELIMINARY
PRELIMINARY

Monitoring the system

Monitoring RNC/TPU activites

Figure 7-12 TPU alarms page

7-18

Monitoring RNC/TPU activites

Figure 7-13 Failed PVCs page

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
7-19
Issue 14, September 2009
See notice on first page

PRELIMINARY

Monitoring the system

PRELIMINARY
PRELIMINARY

Monitoring the system

Monitoring RNC/TPU activites

Figure 7-14 APS status

7-20

Monitoring RNC/TPU activites

Figure 7-15 B-PCF performance statistics

PRELIMINARY

Monitoring the system

Figure 7-16 1X-RNC information page

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
7-21
Issue 14, September 2009
See notice on first page

PRELIMINARY

Monitoring the system

Monitoring RNC/TPU activites

Figure 7-17 RNC call processing status page

PRELIMINARY

Figure 7-18 BHS statistics

7-22

Monitoring RNC/TPU activites

Monitoring via Command Line Interface (CLI)

When the TPU-GUI is unavailable, it is still possible to perform monitoring activities

by the use of commands executed via the CLI. The commands and outputs used for
these monitoring activities are provided in Table 7-2, Monitoring Activity via CLI
(p. 7-23) and described in detail in the Input Messages Manual, 401-610-055 and the
Output Messages Manual, 401-610-057.
Table 7-2

PRELIMINARY

Monitoring the system

Monitoring Activity via CLI

Input
Command

Function

Output
Message

Function

GET:RNCABREVC

Report the current

assert brevity control
state on the specified
RNC.

GET-RNCABREVC

Indicates the current

assert brevity control
state on the specified
RNC.

GET:RNCALARM

Report the alarms that

have been generated
autonomously for the
specified TPU on the
specified RNC, or a
summary of all alarms
(total number of
alarms, and number of
alarms in each severity
category) that have
been generated
autonomously on a
specified RNC.

GET-RNCALARM-SUM

Indicates the alarms

that have been
generated
autonomously for the
specified TPU on the
specified RNC.

GET:RNCINSTALL

Report the installation

status of the specified
RNC or installation
software versions and
hardware versions for
the specified GICC or
B-PCF of the specified
RNC.

GET-RNCINSTALL

Indicates the
installation status of
the specified RNC or
installation software
versions and hardware
versions for the
specified GICC or
B-PCF of the specified
RNC.

GET:RNCINVENTORY

Report the equipped

TPUs on the specified
RNC.

GET-RNCINVENTORY

Indicates the equipped

TPUs on the specified
RNC.

GET-RNC-TPUALARM

Indicates the alarms

that have been
generated
autonomously for the
specified Traffic
Processing Unit (TPU)
on the specified RNC.

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
7-23
Issue 14, September 2009
See notice on first page

PRELIMINARY
PRELIMINARY

Monitoring the system

Table 7-2

Monitoring RNC/TPU activites

Monitoring Activity via CLI (continued)

Input
Command

Function

Output
Message

Function

GET:RNCPDSNLIST

Report the Packet Data

Serving Node (PDSN)
list for the specific
RNC, the Traffic
Processing Unit (TPU)
shelf, or a specific
Blade Packet Control
Function (BPCF) in an
RNC.

GET-RNCPDSNLIST

Provides the Packet

Data Serving Node
(PDSN) list for the
specified Traffic
Processing Unit (TPU)
cards.

GET:RNCPSPCF

Report the Process

Status on the Blade
Packet Control
Function (BPCF) for
the specified element.

GET-RNCPSPCF

Provides the Process

Status on the Blade
Packet Control
Function (BPCF) for
the specified Traffic
Processing Unit (TPU)
cards.

GET:RNCSTATUS

Report the call

processing status for
the specified RNC.

GET-RNCSTATUS

Provides the call

processing status for
the specified RNC

GET:RNC-TPU5EGW-INFO

Report the available

Automatic Protection
Switching (APS)
related information for
the 5EGWs resident on
the specified GICC
card pair(s). This
command is only
available for execution
when the APS
Capability is enbaled
on the RNC.

GET-RNC-TPU5EGW-INFO

Indicates the available

Automatic Protection
Switching (APS)
related information for
the 5EGWs resident on
the specified GICC
card pair(s).

7-24

Table 7-2

Monitoring RNC/TPU activites

Monitoring Activity via CLI (continued)

Function

Output
Message

Function

GET:RNC-TPUDGNRES

Report the available

results of POST
diagnostics test(s) for
the equipped TPU
cards (CICC and
GICC) on the specified
TPU and RNC. Or for
an individual GICC or
CICC.

GET-RNC-TPUDGNRES

Indicates the available

results of POST
diagnostics test(s) for
the equipped/specified
TPU cards (CICC and
GICC) on the specified
TPU and RNC.

GET:RNC-TPUETHERNET

Report the current

Address Resolution
Protocol (ARP) status,
auto-negotiation mode,
flow control mode,
duplex status, and data
rate at the Ethernet
Port (IDs) for the
specified Gateway
Intelligent Carrier Card
(GICC), Traffic
Processing Unit (TPU)
and RNC.

GET-RNC-TPUETHERNET

Indicates the current

Address Resolution
Protocol (ARP) status,
auto negotiation mode,
flow control mode,
duplex status and data
rate at the Ethernet
Port (IDs) for the
specified Gateway
Intelligent carrier card
(GICC),

GET:RNC-TPUFAILEDPVC

Report the available

failed Permanent
Virtual Circuit (PVC)
for the specified TPU
managed resource of
the specified RNC.

GET-RNC-TPUFAILEDPVC

Indicates the failed

Permanent Virtual
Circuit (PVC) list on
the specified TPU and
RNC.

GET:RNC-TPUINFO

Report the
administrative
information, operational
information and usage
information for the
specified Blade Packet
Control Function
(BPCF) card and
Traffic Processing Unit
(TPU).

GET-RNC-TPUINFO

Indicates the
administrative
information,
operational information
and usage information
for the specified Blade
Packet Control
Function (BPCF) card
and Traffic Processing
Unit (TPU).

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
7-25
Issue 14, September 2009
See notice on first page

PRELIMINARY

Input
Command

PRELIMINARY

Monitoring the system

PRELIMINARY

Monitoring the system

Table 7-2

Monitoring RNC/TPU activites

Monitoring Activity via CLI (continued)

Input
Command

Function

Output
Message

Function

GET:RNC-TPUINVENT

Report the equipped

TPU cards on the
specified TPU and
RNC.

GET-RNC-TPUINVENT

Indicates the equipped

TPU cards on the
specified TPU and
RNC.

GET:RNC-TPUSTATE

Report the
Administrative State,
Operational State and
Usage State for the
specified:

GET-RNC-TPUSTATE

Indicates the
Administrative State,
Operational State and
Usage State for the
specified:

- Ethernet Switch Card

(ESC)

- Ethernet Switch Card

- GICC

- CICC

-B-PCF

- B-PCF

- Alarm Card

- Alarm Card (AC)

- ATM port on a GICC

- Shelf Controller
GICC

- GICC

PRELIMINARY

- Shelf Controller
GICC
GET:RNC-TPUVER-CON

Report the configured

application software
version for the
equipped TPU cards
(GICC, CICC, and
B-PCF) on the
specified TPU and
RNC.

GET-RNC-TPUVER-CON

Indicates the
configured application
software version for
the equipped TPU
cards (GICC, CICC,
and B-PCF) on the
specified TPU and
RNC.

GET:RNC-TPUVERSION

Report the application

software version and
Flash File System
(FFS) application
binary version for the
equipped TPU cards
(ESC, GICC, CICC,
AC, and B-PCF) on the
specified TPU and
RNC.

GET-RNC-TPUVERSION

Indicates the
application software
version and Flash File
System (FFS)
application binary
version for the
equipped TPU cards
(ESC, GICC, CICC,
AC, and B-PCF) on the
specified TPU and
RNC

7-26

Table 7-2

Monitoring RNC/TPU activites

Monitoring Activity via CLI (continued)

Input
Command

Function

Output
Message

Function

GET:RNCVERSION

Report the application

software version for the
specified RNC.

GET-RNCVERSION

Indicates the
application software
version for the
specified RNC.

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
7-27
Issue 14, September 2009
See notice on first page

PRELIMINARY

Monitoring the system

PRELIMINARY

Monitoring the system

Monitoring
RNC-related activities via logs
...................................................................................................................................................................................................................................
Purpose

The RNC-related elements generate viewable log files that can help you monitor the
system and determine system errors.
All RNC-related user visible alarms and events (including state changes) are also sent
to the ROP. ROP messages are abbreviated to reduce ROP traffic.
Introduction

RNC logs provide event history for alarms, events (including state changes), and
asserts. The RNC manages the log files based on the log file size.
Types of logs

The following types of log files are supported for RNC:

AP admin log

RNC global admin log

RNC DB admin log

RNC admin log

AP admin log

A separate AP admin log exists on each RNC-AP and OAM Proxy AP which is used to
log platform events and alarms. This AP admin log is updated independently from the
RNC admin log.
Details concerning formats and the types of messages that appear in AP admin log files
can be found in 401-710-201, Appendix B.
RNC DB Global Admin log

The RNC DB Global Admin log is a user viewable log file that is used to log:

Communication link failures between the OAM Proxy AP and an RNC-AP.

RNCDB backup attempts.

PRELIMINARY

The link failures and backup attempts are stored in the following directory on the
associated OAM Proxy AP pairs:
/flx/cip_rnc/apoam/rncglobaladmin.log
Log example

Figure 7-19, RNC DB global admin log examples (p. 7-29) provides a view of the
types of messages that are logged.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

7-28

Monitoring RNC-related activities via logs

Figure 7-19 RNC DB global admin log examples

PRELIMINARY

Monitoring the system

The TPU GUI (via the use of a FAF and an ecppkt form field) can log all database
transactions into a customer viewable log file.
For every successful login, the logger will write to the customer viewable log file
designated, which is located in the following directory on the OAM Proxy AP, where
the TPU GUI is active:
/flx/cip_rnc/apoam/rncdbadmin.log
Only the write transactions (not the read) will be logged.
Logged parameters

The following parameters will be logged:

Timestamp
Session ID

User ID

Machine IP
Type of Transaction

RNC Number

Old and modified data

Log file size and backup

The default size for the logfiles is 5 MB and one backup file is maintained at any
point in time for each logfile.
Log examples

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
7-29
Issue 14, September 2009
See notice on first page

PRELIMINARY

Figure 7-20, RNC DB admin log examples (p. 7-30) provides a view of the types of
messages that are logged.

rnc2

PRELIMINARY

Monitoring the system

Monitoring RNC-related activities via logs

Figure 7-20 RNC DB admin log examples

RNC admin log

PRELIMINARY

The admin log is a user viewable log file that records the
alarm/state/version/configuration information for the RNC, in the following directory,
located on the associated RNC-AP pairs:
flx/cip_rnc/apoam/rncadmin.log
Note, that the active RNC-AP will always record the most current log information, and
if a switch from the active to the standby occurs, the newly active RNC-AP will then
become the primary logging mechanism.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

7-30

Monitoring RNC-related activities via logs

Log message format

The RNC admin log message format follows the same conventions used for the
MM-AP log file format. Each RNC Administrative log message provides the following
format/information:

A Header identifying the RNC element to which the log entry belongs.

Equipment Identification, for example, TPU slot and TPU shelf ID.
Time stamp.

Details of fault/alarm conditions/events encountered by the RNC element.

User actions and corresponding responses like configuration change events, various
administrative tasks performed on RNC elements such as LOCK or UNLOCK.

Update activity (configuration and software update).

Initialization progress.

PRELIMINARY

Monitoring the system

Rollover scheme

When a log file reaches its maximum size parameter, it will be backed up and the
previous back up file will be deleted.
Types of messages

The following types of messages are logged to the rncadmin.log file:

RNCM and TPU shelf alarms, as shown in the following example:
REPT: RNC 14, TPU 1, GICC 3, Proc 0, ALARM CLEARED
SONET Driver cleared Loss of Frame failure [RNCTPUSONETALM]
2004-02-09 19:12:44 REPORT #000001 FINAL

State/change events for TPU components, as shown in the following example:

REPT: RNC 14, TPU 1, GICC 3, ATM 1, STATE CHANGE
RNC 14, TPU 1, GICC 3, ATM 1 changed state
from UNLOCKED, DISABLED, ACTIVE
to UNLOCKED, ENABLED, ACTIVE
ORIGINATING COMMAND #consoleUnLock1.1
2004-02-09 19:12:45 REPORT #000001 FINAL

CICC configuration change reports, as shown in the following example:

REPT: RNC 15, TPU 1, GICC 3, ATM 3, CONFIG CHANGE
RNC 15, TPU 1, GICC 3, ATM 3 ADDED
2004-04-08 13:15:46 REPORT #000001 FINAL

Dynamic data update, as shown in the following example:

REPT: RNC 14
TPU 1, Dynamic Update success: config file installed on TPU
FRAME 14
2004-02-09 19:15:25 REPORT #000001 FINAL

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
7-31
Issue 14, September 2009
See notice on first page

PRELIMINARY

Monitoring the system

Monitoring RNC-related activities via logs

TPU CLI issued commands and outputs, as shown in the following examples:
GET:RNC 14,TPU 1,ALARM! IN PROGRESS
ORIGINATING COMMAND #TPUCLI974463.1
2004-02-17 11:29:53 REPORT #000001 FINAL
GET:RNC 14,TPU 1,ALARM! COMPLETE
Resource Time Severity Description
----------------------------------------------------------------------TPU 1 Tue Feb 17 11:15:24 warning At least one processor may not have the
provisioned version
GICC 3,ATM 2 Tue Feb 17 11:26:31 major SONET Driver generated Loss of
Signal failure
TMN commands (lock/unlock/shutdown/reset) status, as shown in the following
examples:
UNLOCK:RNC 14,TPU 1,GICC 3,Proc 0! IN PROGRESS
ORIGINATING COMMAND #TPUGUI936725.9
2004-02-17 11:26:49 REPORT #000001 FINAL
UNLOCK:RNC 14,TPU 1,GICC 3,Proc 0! ISSUED
ORIGINATING COMMAND #TPUGUI936725.9
2004-02-17 11:26:50 REPORT #000001 FINAL
TPU installation status, as shown in the following examples:
FILE TRANSFER:RNC 14,TPU 2,GICC 3,Proc 0! IN PROGRESS
ORIGINATING COMMAND #0.0
2004-02-09 19:16:10 REPORT #000001 FINAL
FILE TRANSFER:RNC 14,TPU 2,GICC 3,Proc 0! COMPLETE
ORIGINATING COMMAND #0.0
2004-02-09 19:16:20 REPORT #000001 FINAL

Accessing log files

RNC logs and AP admin log files can be accessed via the RNC-AP, by means of the
following procedure:

PRELIMINARY

Accessing Admin logs (p. 7-33)

7-32

Accessing
Admin logs
...................................................................................................................................................................................................................................
Where the Admin log files are located

AP admin logs are located in the following directory on each RNC-AP:

/var/ap/platform/logs/admin

PRELIMINARY

Monitoring the system

RNC admin logs are located in the following diectory on each RNC-AP:
/flx/cip_rnc/apoam/log
RNC DB global admin logs and RNC DB admin logs are located in the following
diectory on each OAM Proxy AP:
/flx/cip_rnc/apoam/log
How admin logs are named

AP log files are named with the following convention:

YYYYMMDD.ADM
where
YYYYMMDD is the date in which the log was produced:
YYYY is the year
MM is the month
DD is the day
The RNC admin log file is named:
rncadmin.log
The RNC DB global admin log file is named:
rncglobaladmin.log
The RNC DB Admin log file is named:
rncdbadmin.log
Old files

Old AP log file names that begin with old

There is only one old RNC admin log file and it is named:
rncadmin.log.backup
There is only one old RNC DB Admin log file and it is named:
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
7-33
Issue 14, September 2009
See notice on first page

PRELIMINARY

(old.YYYYMMDD.ADM) are overflow files. When the log file exceeds its maximum
size, it is copied to an overflow file and a new file for that date is created.

PRELIMINARY

Monitoring the system

Accessing Admin logs

rncdbadmin.log.backup
How long files are stored

The system maintains the most recent 30 days of AP admin log files.
For the RNC admin log rollover scheme see Rollover scheme (p. 7-31).
To view an Admin log

To view any Admin log, perform the following steps:

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

Log in to the RNC-AP or OAM Proxy AP whose logs you wish to see. You must be
root or System Administrator to view the ADM log in /var/ap/platform/logs/admin.
Any login can view the log files in /flx/cip_rnc/apoam/log.
...................................................................................................................................................................................................

Change directory (cd) to the Admin log directory and list the files that are present; for
example:

ending with the most recent file.

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

PRELIMINARY

If your login is root, you can use an editor (such as vi), open the file that you would
like to see:

7-34

Accessing Admin logs

PRELIMINARY

Monitoring the system

If you are System Administrator, you should use /flx/bin/viewadmlog to view the ADM
log in /var/ap/platform/logs/admin. For example:
/flx/bin/viewadmlog 20081202.ADM

The System Administrator can use an editor to view the log in /flx/cip_rnc/apoam/log
If you are neither root nor System Administrator, you do not have permission to view
the ADM log in /var/ap/platform/logs/admin, but you may view the log in
/flx/cip_rnc/apoam/log.
END OF STEPS
...................................................................................................................................................................................................

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
7-35
Issue 14, September 2009
See notice on first page

PRELIMINARY

Monitoring the system

Monitoring
activities via Read-Only Printer (ROP)
...................................................................................................................................................................................................................................
Introduction

The ROP application is an output message filtering, formatting and routing mechanism
that resides on the ECP and MM-AP. The MM-ROP feature takes over formatting,
routing and filtering of the majority of the messages in the ROP output stream.
Alarms

RNC- AP and OAM Proxy AP hardware and application software produce conventional
alarm conditions on the ROP using the MM-AP infrastructure. The RNC-M application
passes detailed TPU alarms from the cards on the TPU shelf and from the TCS
application to the ROP stream.
RNC ID

The RNC ID will be shown on the ROP output in order to guide the user to RNC
summary page on the EMS GUI to allow access into the TPU GUI pages.
Output

Table 7-3, Outputs for ROP Stream (p. 7-36) shows a high-level view of the types of
output that are in the ROP stream for RNC.
Table 7-3

Outputs for ROP Stream

Output
AP Summary alarm will be printed
RNC summary alarms TPU summary alarm and AP summary alarm
RNC AP command-requests
RNC AP command-acknowledgements
RNC AP command-responses
TCS events (abbreviated)
RNC-M events (abbreviated)
TPU-M events (abbreviated)

PRELIMINARY

TPU input command that has valid syntax

Output of commands executed through the TPU-CLI/GUI
Formatted output reports for completed on-demand TCS audits.
Formatted output reports for failed on-demand and routine TCS audits
Detailed TPU alarms and autonomous events

7-36

Table 7-3

Monitoring activities via Read-Only Printer (ROP)

Outputs for ROP Stream

(continued)

Output
All OC-3 fault and alarm conditions
Dynamic Data failure and status messages.
Warning message when deleting/changing a PSU parameter

PRELIMINARY

Monitoring the system

Failure of the FS audit

TCS-PCF communication loss alarm
TCS-PCF alarm situation is cleared
Legacy TI commands and reports that also support RNC

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
7-37
Issue 14, September 2009
See notice on first page

PRELIMINARY

Monitoring the system

Crossover
LAN connectivity monitoring
...................................................................................................................................................................................................................................
Introduction

Crossover LAN connectivity provides a second path for data synchronization of the
alarm cards (CMMs).
Default behavior

The default behavior of the CMMs is to attempt data synchronization through the
backplane Ethernet ports.
The default path for data synchronization through the backplane ports requires the data
to traverse three elements to go from one CMM to the other. If any one of these
elements fail, the CMMs will not be able to synchronize critical data, and the CMMs
will be prevented from failing over.
Redundant data synchronization

The addition of the Crossover LAN connection provides a second, redundant data
synchronization path between the CMMs. Therefore, the CMMs will still be able to
synchronize chassis system state data through the front panel Ethernet connections in
the event that any of the three elements fail.
Important! Note that the physical connection is actually two crossover cables
connected at the FIP of the UNC in which the RNC is housed. These FIP
connections conceptually equate to physically connecting the eth0 ports on the
CMM cards.
Cable connection and verification

PRELIMINARY

Refer to the Cross-over LAN cable connection and verification (p. 7-39) procedure
for information on how to connect and verify the integrity of the cross-over cable
connections.

7-38

Cross-over
LAN cable connection and verification
...................................................................................................................................................................................................................................
Purpose

To install and verify the integrity of the cross-over LAN cables provided for the alarm
(CMM) cards used in the CDMA 1X RNC.

PRELIMINARY

Monitoring the system

Reason to perform

To help ensure that the CMMs will fail over in the event that the default path becomes
disabled.
Non-service affecting

The installation of the cross-over LAN cables will have no impact on system operation.
Ping test

After the cross-over cables are connected you will need to verify that the cross-over
connection paths are valid.
Accessing RNC-AP

Verification first involves accessing the RNC-AP. Procedures for accessing any type of
MM-AP are found in 401-710-201.
Completing verification

From the RNC-AP you must then SSH to the CMM card in the top position of the
upper TPU shelf:

Log into the CMM card.

Ping the CMM card in the bottom position of the upper TPU shelf.
Then repeat the ping verification from the CMM card in the bottom position to the
CMM card in the top position.

After the CMM cards in the upper TPU shelf have been verified the same verification
is performed on the CMM cards in the lower TPU shelf.
IP addresses

To perform the ping test you will need to know the IP addresses associated with eth1
and eth0.

172.Y.128.121 for CMM1-1.

172.Y.128.122 for CMM1-2.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
7-39
Issue 14, September 2009
See notice on first page

PRELIMINARY

The IP addresses associated with eth1 (required for telneting into the CMM cards) are
partially site dependent. The addresses are listed as fiollows:

PRELIMINARY

Monitoring the system

Cross-over LAN cable connection and verification

172.Y.132.121 for CMM2-1.

172.Y.132.122 for CMM1-2.

where Y is site dependent. See your System Administrator for details.

The eth0 IP addresses (required for pinging of the CMM cards) are listed as follows

10.1.0.91 for CMM1-1

10.1.0.92 for CMM1-2

10.1.0.94 for CMM2-2

10.1.0.93 for CMM2-1

Before you begin

The cross-over LAN cables can be obtained as follows:

Some sites may have the cables readily available. The cables are six to eight inches
long and are labelled as, W2058 and W2059. The cables are also labelled at either
end to denote the FIP port to which that connector is to be connected. That is,
W2058 connects to FIP ports 7 and 23, and W2059 connects to FIP ports 22 and
38.

If the cross-over LAN cables are not available on-site they can be ordered from
Alcatel-Lucent using the Orderable Item (OI) code 300950730.

You will also need a flat-head screwdriver to remove the FIP panel.
Important! Note that sites with more than one RNC will require mutiple pairs of
cables.
Procedure

To install and verify the cross-over LAN cables, proceed as follows:

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

At the FIP, remove the panel covering the FIP.

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

At the FIP, orient the W2058 cable so that you can insert the end labelled 7 into FIP
port 7, and the end labelled 23 into FIP port 23. Then insert the cable ends into the
FIP ports.
...................................................................................................................................................................................................

PRELIMINARY

At the FIP, orient the W2059 cable so that you can insert the end labelled 22 into FIP
port 22, and the end labelled 38 into FIP port 38. Then insert the cable ends into the
FIP ports.
...................................................................................................................................................................................................

Access the RNC-AP via any method described in section 401-710-201

7-40

Cross-over LAN cable connection and verification

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

From the RNC-AP SSH into the CMM1-1 card as follows:

ssh 172.Y.128.121<CR>

where Y is site dependent. See your System Administrator for details.

Result
Trying 172.Y.128.121...
Connected to 172.Y.128.121.
Escape character is ^].
Intel(R) NetStructure(TM) ZT7102 Chassis Management Module
login:

PRELIMINARY

Monitoring the system

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

Enter the following:

root<CR>

Result
Password:
...................................................................................................................................................................................................

Enter the password and hit return.

Result The command prompt is displayed.
...................................................................................................................................................................................................

Enter the following:

ping 10.1.0.92<CR>

Result An output such as shown in the following abbreviated example indicates

that the path is true.

PING 10.1.0.92 (10.1.0.92) from 10.1.0.91 : 56(84) bytes of data.
Warning: time of day goes back, taking countermeasures.
64 bytes from 10.1.0.92: icmp_seq=0 ttl=255 time=0 usec
64 bytes from 10.1.0.92: icmp_seq=1 ttl=255 time=0 usec
64 bytes from 10.1.0.92: icmp_seq=2 ttl=255 time=0 use
...................................................................................................................................................................................................

In a like manner perform steps 3 through 6 to ping CMM1-1 from CMM1-2,

substituting the correct IP address information as described in IP addresses (p. 7-39).
...................................................................................................................................................................................................

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
7-41
Issue 14, September 2009
See notice on first page

PRELIMINARY

Repeat steps 3 through 7 for the CMM cards in the lower TPU shelf substituting the
correct IP address information as described in IP addresses (p. 7-39).

PRELIMINARY
PRELIMINARY

Monitoring the system

Cross-over LAN cable connection and verification

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

At the conclusion of testing replace the FIP panel.

7-42

PRELIMINARY

8Troubleshooting

This chapter addresses how to identify and resolve RNC problems after initial install.
It is assumed that Technical Support has successfully installed and made the RNC
operational prior to this point.
Contents
Enabling troubleshooting

8-3

RNC failure types

8-4

Customer tools

8-5

Component indicators

8-8
8-11

B-PCF monitoring and flow control

8-18

1xRNC packet filtering

8-24

Far end CA audit

8-26

To enable/disable far end CA audits

8-27

Application Processor (AP) problem solving

8-30

RNC AP OOS (components or alarms)

8-31

OAM Proxy AP OOS (components or alarms)

8-34

RNC-AP rebooting

8-37

LANS 1 and/or 2 OOS

8-39

EIN LAN OOS

8-41

LANS 3 and/or 4 OOS

8-42

Traffic Processing Unit (TPU) problem solving

8-43

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
8-1
Issue 14, September 2009
See notice on first page

PRELIMINARY

RNC health check

PRELIMINARY
PRELIMINARY

Troubleshooting

Overview

TPU OOS Components or Alarms

8-44

Alarm card fault

8-46

ESC fault

8-48

GICC fault

8-50

CICC fault

8-53

B-PCF fault

8-55

E-PCF fault

8-57

PCF reachability alarm

8-59

Assert Brevity Control

8-62

TPU GUI access problem solving

8-63

Unable to access TPU GUI

8-64

Verify correct IP address for direct access

8-65

Verify TPU GUI application is running (CLI command)

8-67

Verify TPU GUI application is running (EMS GUI)

8-69

Verify Java version for Internet Explorer

8-74

Eliminate file conflicts and verify proxies

8-76

Update Java runtime parameters

8-81

Automatic Protection Switching (APS) problem solving

8-87

APS mated GICC not available - major alarm

8-88

APS Data Out Of Sync failure - major alarm

8-89

APS far end protection failure - major alarm

8-90

APS mode mismatch - major alarm

8-91

Unable to protection switch due to AISL - major alarm

8-93

APS protection byte failure - warning

8-94

APS channel mismatch - minor alarm

8-96

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

8-2

Enabling troubleshooting
Overview
...................................................................................................................................................................................................................................

PRELIMINARY

Troubleshooting

Purpose

In order to enable troubleshooting, the Service Provider needs to be aware of the types
of failures that are possible, and the means that are available to detect and resolve any
possible failures.
Contents
RNC failure types

8-4

Customer tools

8-5

Component indicators

8-8

RNC health check

8-11

B-PCF monitoring and flow control

8-18

1xRNC packet filtering

8-24

Far end CA audit

8-26

To enable/disable far end CA audits

8-27

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
8-3
Issue 14, September 2009
See notice on first page

PRELIMINARY

Troubleshooting

RNC
failure types
...................................................................................................................................................................................................................................
Introduction

RNC failures can be expected to fall into various types or categories, as described in
the following paragraphs.
Configuration issues

RNC configuration issues (usually at initial installation or after some office

configuration changes).
Lost connectivity

Lost connectivity due to wiring issues or transport configuration issues (usually at

initial install or after wiring or maintenance changes). This applies to the Ethernet
LANs or the ATM network.
Application process failures

Application processes on a component not running due to installation issues (pertains

to initial installation or software upgrade).
Application processes on a component not running due to a fault (usually a
configuration issue).
Application software bugs

With the introduction of new application software, code interaction problems that were
not apparent during testing, can sometimes arise after software is released into the
field.
Operating System (OS) problems

OS problems that affect performance, such as booting up or lock-ups.

Hardware failures

Component hardware failures are failures at the card/board level.

PRELIMINARY

CPU occupancy overload

When the RNC becomes BUSY due to a TCS crossing the CPU occupancy threshold
(that is, an AP_OVERLOAD condition) processing of new/reactivation calls, and the
forwarding of calls to next the RNC (if present) will be stopped until the condition is
cleared.

8-4

Customer
tools
...................................................................................................................................................................................................................................
Introduction

Customer level troubleshooting is accomplished via OA&M functionality, and some

generally available embedded tools. Table 8-1, Customer tools (p. 8-5) identifies the
OA&M functionality and embedded tools available for the RNC.
Table 8-1

Customer tools

OA&M
tool

How accessed

What tells

ECP SDP

ECP SDP terminal

summary status of RNC

previous functionality to support: CDNs,

APs, EINs, cells, etc.

RNC: device state changes, warnings,

alarms, maintenance results. RNC ROP
output is a subset of the RNC admin log and
is filtered by the RNC Integrity Monitor
(RIM)

previous functionality

ECP ROP

PRELIMINARY

Troubleshooting

ECP ROP display

OMP, start EMS GUI

application

Graphical interface for: RNC summary

alarms, status, configuration commands,
maintenance commands and software
download commands for: RNC-APs, and
EPCFs or BPCFs

TICLI

OMP, from Technician

can access multiple APs

commands for status, test and maintenance

of RNC-APs and RNC applications

AP unix
commands

SSH to target AP and

execute commands
from unix prompt

Examples: RCCcstat, apoffline, aponline,

commit, bundle, enable, flxpkginfo
commands

TPU GUI

When in EMS GUI,

navigate to TPU and
this accesses TPU GUI
server in OA&M proxy

Status, alarms, maintenance, version,

configuration, test, data provision and install
commands for TPU and specific cards:
GICC, CICC, ESC and CMM.

TPU-CLI

SSH to RNC-AP or
OAM-Proxy AP and
run TPU-CLI

Status, alarms, maintenance, configuration,

test, version and install commands for TPU
and specific cards: GICC, CICC, ESC and
CMM

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
8-5
Issue 14, September 2009
See notice on first page

PRELIMINARY

EMS GUI

PRELIMINARY

Troubleshooting

Customer tools

Table 8-1

Customer tools

(continued)

OA&M
tool

How accessed

What tells

APadmin.log

Located on AP under
the following directory:

AP and VCVM state changes, alarms and

asserts

rncadmin.log

Located on RNCM-AP
under the following
directory:

RNC component state changes, alarms and

asserts

On ACTIVE RNCM; if an ACTIVESTANDBY switch has occurred, look at

rncadmin.log on both RNC-APs

rrncglobaladmin.log

Located on OAM
Proxy AP under the
following directory:

Communication link failures between the

OAM Proxy AP and an RNC-AP.

RNCDB backup attempts.

Database transactions

/var/ap/platform/logs/
adm in file name is:
yyyymmdd.ADM
rncadmin.log

$CDMA_OAM_ROOT/
log or
/flx/cip_rnc/apoam/log
RNC DB
global
admin log

$CDMA_OAM_ROOT/
log or
/flx/cip_rnc/apoam/log
rncdbadmin.log

rncdbadmin.log
Located on OAM
Proxy AP under the
following directory:
$CDMA_OAM_ROOT/
log or

PRELIMINARY

/flx/cip_rnc/apoam/log
Controlling ROP
assert
output

CLI command

Capability to confine ROP assert output (assert

brevity control) to significant information so as
to keep the output volume manageable. Vast
amounts of ROP output may discourage craft
attention.

Monitoring
assert
brevity
control

CLI command or TPU

GUI

Capability to determine the state of assert

brevity control status.

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

8-6

Customer tools

Table 8-1

Customer tools

(continued)

OA&M
tool

How accessed

What tells

Monitoring
RNC call
processing
status

CLI command or TPU

GUI

Capability to determine the general call

processing status for an individual RNC, or for
all MSC associated RNCs.

Monitoring
gateway
(A8A9/
A10/A11)
status

TPU GUI

Capability to determine the states of the

A8A9/A10/A11 gateways on the SC-GICC.

Monitoring
GICC
BHS status

TPU GUI

Capability to display specifics on the GICC

BHS status as regards to usage state, loading
status, UDP port usage status, and so forth.

Obtaining
ping
status of
external IP
network

CLI command

Capability to ping external interfaces such as

PDSNs, and B-PCFs.

Triggering
FARCA
reachability test

CLI command or TPU

GUI

Capability that enables the user to isolate

connectivity issues between Far CAs.

netstat

SSH to AP

IP routing

ifconfig

SSH to AP

IP configuration

traceroute SSH to AP

IP routing

SSH to AP

Connectivity test tool

ping

PRELIMINARY

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
8-7
Issue 14, September 2009
See notice on first page

PRELIMINARY

Troubleshooting

PRELIMINARY

Troubleshooting

Component
indicators
...................................................................................................................................................................................................................................
Cabinet indicators

See Appendix A, Controls and indicators of this document for a view and a
description of the RNC cabinet indicators.
AP indicators

For a complete description of AP indicators, see See Chapter 7, Troubleshooting in

(401-710-201.
TPU indicators

See Appendix A, Controls and indicators of this document for a view of the RNC
indicators (cabinet and TPU cards) and a description of the RNC cabinet and TPU
controls and indicators. Table 8-2, Card controls and indicators (p. 8-8) included
here, provides a quick-reference view of the TPU card controls and indicators.
Table 8-2

Card controls and indicators

Component Indicator/Control

Color and State

Alarm
Card

Steady GREEN: Alarm card is ACTIVE

Blinking GREEN: Alarm card is

STANDBY

Steady RED: Alarm Card is faulted

Blinking BLUE: indicates card is booting

Steady BLUE: indicates card latches are

open, the card has not been selected with
BSEL or the card power supplies are out of
band

CMM Status LED

Hot Swap LED

Minor Alarm LED

OFF... no alarm

Major Alarm LED

Steady AMBER... alarm

Critical Alarm LED

Blinking AMBER....alarm cutoff engaged

YELLOW: OFF 10MBS, ON 100mbs

GREEN: OFF (no link), ON (link

in-service), Blinking (ACTIVE)

PRELIMINARY

Ethernet Status LED

Alarm Cutoff/Reset
Switch

Hold for 7 seconds to reset card

8-8

Component indicators

Table 8-2

Card controls and indicators (continued)

Component Indicator/Control

Color and State

ESC

GREEN (board OK)

YELLOW (board is booting)

OFF (fault or no power)

RED (fault)

OFF (no fault or no power)

Blinking BLUE: indicates card is booting

Steady BLUE: indicates card latches are

open, the card has not been selected with
BSEL or the card power supplies are out of
band.

System LED

Fault LED

Hot Swap LED

GICC

CICC

Card Reset Switch

Performs card reset when depressed

PRGM LED 1 (Fault

LED)

During initialization this LED blinks

GREE

For POST fails this LED stays ON GREEN

If initialization is successful, this LED is

turned OFF

PRGM LED 2
(In-service LED)

Turns ON steady GREEN for a successful

initialization

Hot Swap LED

Blinking BLUE: indicates card is booting

Steady BLUE: indicates card latches are

open, the card has not been selected with
BSEL or the card power supplies are out of
band

RED: blinks during power up/reset sequence.

Lights steady if a fault is detected.

CPSB Status LEDS

Active and link LEDS for cpsb0 (link1) and

cpsb1 (link2)

Hot Swap LED

Blinking BLUE: indicates card is booting

Steady BLUE: indicates card latches are

open, the card has not been selected with
BSEL or the card power supplies are out of
band

Card Reset Switch

Performs card reset when depressed

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
8-9
Issue 14, September 2009
See notice on first page

PRELIMINARY

Power/Fault LED

PRELIMINARY

Troubleshooting

PRELIMINARY
PRELIMINARY

Troubleshooting

Component indicators

Table 8-2

Card controls and indicators (continued)

Component Indicator/Control

Color and State

B-PCF

Alarm/User

YELLOW: a card alarm is present

Ready

GREEN: card is operational with no alarms

Hot Swap LED

Blinking BLUE: indicates card is booting

Steady BLUE: indicates card latches are

open, the card has not been selected with
BSEL or the card power supplies are out of
band

Abort Switch

Will bring Solaris OS to OK prompt (open

boot)

Reset Switch

This is a software reset of the card

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

8-10

RNC
health check
...................................................................................................................................................................................................................................
Introduction

This section provides procedures for determining RNC health. Supplemental

information that can be useful in determining RNC health is also provided.

PRELIMINARY

Troubleshooting

System monitoring

A description of the methods provided for monitoring the systems health is provided
in Chapter 7, Monitoring the system. The information presented here attempts to give
a quick overview of some of these methods as well as give examples of CLI input and
output that can be used to determine the states and general health of the RNC-related
components.
Status Display Pages

For a system with multiple RNCs, the RNC SSA indicator is a composite of the states
of all RNCs. If any RNC component in any of the RNCs is OFF NORMAL, then the
RNC SSA will be OFF NORMAL.
RNC/TPU and RNC-AP combined status

RNC components for a given RNC include the RNC AP and its associated TPUs.
MM-AP indicator

Status of the OAM Proxy AP is included as part of the MM-AP status indicator.
Using EMS or TICLI

Executing the following commands from the EMS or TICLI will provide status and
show any alarms for the RNC-AP or OAM Proxy AP:

OP:AP a, STATUS

OP:AP a, ALARM

Sample output (RNC-AP status)

By executing the OP:AP a, STATUS command, status for an RNC-AP would be

defined as follows:
Normal case: AP, EIN, LANs and RNC application are all ACTIVE or STANDBY

Abnormal states: OOS-MANUAL, OOS-FAULT, INDETERMINATE, UNKNOWN

LAN 1&2: identifies the ethernet links to the MM dual rail LAN

LAN 3&4: identifies the ethernet links to the RNC frame, i.e., the ethernet switch
cards, ESCs.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
8-11
Issue 14, September 2009
See notice on first page

PRELIMINARY

Troubleshooting

RNC health check

The example that follows, shows both RNC-AP applications active on the same AP.
Normally, TCS would be active and RNCM standby on one AP and TCS standby and
RNCM active on the other RNC-AP.

The normal case would be no alarms, when the OP:AP a, ALARM command is
executed. The example that follows shows TPU alarms present.

PRELIMINARY

Executing the following commands from the TPU-CLI will provide status and show
any alarms for the TPU shelf:

GET: RNC a, TPU b, STATE

GET:RNC a, ALARM;SUMMARY

GET: RNC a, TPU b, ALARM

Sample output for TPU state

By executing the GET: RNC a, TPU b, STATE command, normal status for a TPU
would be: resources UNLOCKED, ENABLED and either ACTIVE or IDLE. The
example that follows shows a resource DISABLED; this would be a MAJOR alarm.
....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

8-12

RNC health check

Sample output (TPU summary alarms)

The normal case would be no alarms when the GET:RNC a, ALARM;SUMMARY

command is executed. The example that follows shows a number of MAJOR, MINOR
and WARNING alarms.
....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
8-13
Issue 14, September 2009
See notice on first page

PRELIMINARY

1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
M 30 GET:RNC 14,TPU 1,STATE! IN
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
PROGRESS
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
ORIGINATING COMMAND
1234567890123456789012345678901212345678901234567890123456789
#TPUCLI105113.2
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
2004-03-04 14:30:20 REPORT #000001 FINAL
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
TPUCLI>
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
M 30 GET:RNC 14,TPU 1,STATE!
1234567890123456789012345678901212345678901234567890123456789
COMPLETE
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
Resource
Admin
Oper
1234567890123456789012345678901212345678901234567890123456789
Usage
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
-----------------------------------------------1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
ACS 1,AC 1
UNLOCKED
ENABLED
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
ACTIVE
1234567890123456789012345678901212345678901234567890123456789
ACS 1,AC 2
UNLOCKED
ENABLED
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
ACTIVE
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
ESC 2
UNLOCKED
ENABLED
1234567890123456789012345678901212345678901234567890123456789
ACTIVE
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
GICC 3,Proc 0
UNLOCKED
ENABLED
1234567890123456789012345678901212345678901234567890123456789
ACTIVE
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
GICC 3,ATM 1
UNLOCKED
ENABLED
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
IDLE
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
GICC 3,ATM 2
UNLOCKED
ENABLED
1234567890123456789012345678901212345678901234567890123456789
IDLE
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
GICC 3,ATM 3
UNLOCKED
ENABLED
1234567890123456789012345678901212345678901234567890123456789
IDLE
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
GICC 3,ATM 4
UNLOCKED
ENABLED
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
IDLE
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
CICC 12,Proc 0
UNLOCKED
ENABLED
1234567890123456789012345678901212345678901234567890123456789
IDLE
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
CICC 12,Proc 1
UNLOCKED
ENABLED
1234567890123456789012345678901212345678901234567890123456789
IDLE
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
CICC 12,Proc 2
UNLOCKED
ENABLED
IDLE
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
GICC 20,Proc 0
UNKNOWN
DISABLED
IDLE
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
ESC
21
UNLOCKED
ENABLED
ACTIVE
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
ORIGINATING COMMAND #TPUCLI105113.2
1234567890123456789012345678901212345678901234567890123456789
2004-03-04 14:30:21 REPORT #000001 FINAL
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789

PRELIMINARY

Troubleshooting

PRELIMINARY

Troubleshooting

RNC health check

The normal case would be no alarms when the GET: RNC a, TPU b, ALARM
command is executed. The example that follows shows MAJOR ATM alarms,
INDETERMINATE PCF states and a WARNING.

PRELIMINARY

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

8-14

RNC health check

PRELIMINARY

Troubleshooting

The procedures that follow (described in Table 8-3, Using SDP, EMS-GUI, and
TPU-GUI (p. 8-15) through Table 8-6, Using TICLI and TPU-CLI for each TPU
shelf (p. 8-17)) determine RNC health at a high level. At the end of these procedures
all OOS components and alarms will be identified.
Table 8-3

Using SDP, EMS-GUI, and TPU-GUI

Answer

Is the RNC status in

the Summary Status
Area (SSA) of any
ECP SDP page
green?

IF NO, go to
Question 3.

Is the MM-AP status

indicator of any ECP
SDP page green?

IF NO, go to
Question 4.

Check Steps

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
8-15
Issue 14, September 2009
See notice on first page

PRELIMINARY

No. Question

PRELIMINARY

Troubleshooting

RNC health check

Table 8-3

Using SDP, EMS-GUI, and TPU-GUI

(continued)

No. Question

Answer

Check Steps

IF NO ---------->

Do the following:

Do both the EMS GUI

and the TPU GUI
show the RNC in
service with no
alarms?

Note all OOS components and

alarms

Identify the most critical OOS

component, i.e., TCS VCVM,
RNCM VCVM, TPU)

For AP Issues: Go to RNC AP

OOS (components or alarms)
(p. 8-31)
For TPU issues: Go to TPU OOS
Components or Alarms (p. 8-44)
4

Does the EMS GUI

show the OAM-Proxy
APs in service with no
alarms?

IF NO ---------->

Do the following:

Note all OOS components and

alarms

Identify the most critical OOS

component

Go to OAM Proxy AP OOS

(components or alarms) (p. 8-34)
5

On the EMSGUI, are

there any EPCF
alarms present

Table 8-4

Do the following:

For E-PCF: Go to E-PCF

fault (p. 8-57)

For B-PCF: Go to B-PCF

fault (p. 8-55)

Using TICLI and TPU-CLI for RNC-APs

No. Question

Answer

Check Steps

IF NO to any
question -------->

Do the following:

Does CLI show AP

status ok?

Does CLI show an

ACTIVE TCS and a
STANDBY TCS?

Note all OOS components

and alarms

Identify the most critical

OOS and alarms

Does CLI show an

ACTIVE RNCM and a
STANDBY RNCM?

Go to RNC AP OOS
(components or alarms)
(p. 8-31)

Does CLI show no

alarms on the
RNC-APs?

PRELIMINARY

IF YES --------->

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

8-16

RNC health check

Table 8-5

Using TICLI and TPU-CLI for OAM Proxy APs

No. Question

Answer

Check Steps

IF NO to any
question -------->

Do the following:

Does CLI show AP

status ok?

Does CLI show an

ACTIVE RNCDBMS
NDBY RNCDBMS?

Note all OOS components

and alarms

Identify the most critical

OOS and alarms

Does CLI show an

ACTIVE TPUGUI and
a STANDBY TPUGUI?

Go to OAM Proxy AP OOS

(components or alarms)
(p. 8-34)

Does CLI show no

alarms on the
OAM-Proxy APs?

Table 8-6

Using TICLI and TPU-CLI for each TPU shelf

No.Question

Answer

Check Steps

IF NO to
any
question
-------->

Do the following:

PRELIMINARY

Troubleshooting

Does the
TPU-CLI
show all
TPU shelf
cards as:
UNLOCKED,
ENABLED
and either
ACTIVE or
IDLE?

Note all OOS components and alarms

Identify the most critical OOS and alarms

Go to TPU OOS Components or Alarms (p. 8-44)

Does
TPU-CLI
show no
CRITICAL
or MAJOR
alarms for
the shelf?

PRELIMINARY

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
8-17
Issue 14, September 2009
See notice on first page

PRELIMINARY

Troubleshooting

B-PCF
monitoring and flow control
...................................................................................................................................................................................................................................
Introduction

The B-PCF implements a MINOR, and then a MAJOR alarm as CPU usage exceeds
acceptable levels. When the MAJOR alarm level is reached, the B-PCF will not accept
any new calls.
Existing active calls

A problem that has been identified within existing active calls is that the bursting of
the extremely high flow packet stream from the network side can also contribute to the
overload of the CPU. Under heavier traffic conditions, that can result in a premature,
and even unnecessary B-PCF lockout of any new calls.
Important! This also applies to the E-PCF as well. See 401-710-087 for additional
information.
Full-time monitoring and flow control

For Release 29.0 and beyond, the following updates have been implemented:

Support for full-time monitoring of the total throughput of incoming IP packets

from PDSNs.
A flow control scheme on the B-PCF and GICC to discard incoming packets
accordingly, once packet throughput reaches a critical threshold.

Thus, a potential for the lockout of any new calls under the Existing active calls
scenario previously described, is avoided.
Solution

Essentially, the solution is to:

Limit the number of packets per second for each A10 link.
Limit the number of bits per second for each A10 link.

Limit the total number of packets per second on Packet Control Function (PCF)
based on GICC for B-PCF.
Provide additional PM counts for Service Measurement monitoring purposes. See
also, 401-610-135 for additional information.
Provide B-PCF configuration parameters to set the aforementioned limits.

PRELIMINARY

8-18

B-PCF monitoring and flow control

Configuration

In Release 29.0 and beyond it will be possible to implement monitoring and flow
control on an existing, or newly installed B-PCF, by using the following TPU GUI
screens:

1X RNC Information

Configure BPCF Parameters

PRELIMINARY

Troubleshooting

Configure Common BPCF Parameters

1X RNC Information

The 1X RNC Information page/screen is provided with the following monitoring and
flow control related parameter field:
Threshold of total throughput per PCF

This field is used to limit the outgoing total number of packets towards a B-PCF
within a 200 ms time-window. The default value is 2000, and the range is 1500
through 5000.
A10 incoming GRE packet flow control

This field enables the per session based filtering on the B-PCF, and limits the number
of packets outgoing from B-PCF within each 200 ms time-window. The default value
is an unchecked box which indicates disabled.
Configure BPCF Parameters

The Configure BPCF Parameters page/screen is provided with the following

monitoring and flow control related parameter fields:

Threshold for number of packets within 200 ms per A10 link

This field is set to permit a B-PCF to accept only a certain number of packets on
each A10 link within each 200 ms time-window. The default value is 20, and the
range is 10 through 200.

Threshold of kilo bits within 200 ms per A10 link

This field is set to permit a B-PCF to accept only certain data bits on each A10
link within each 200 ms time-window. The default value is 70, and the range is 45
through 92.

PRELIMINARY

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
8-19
Issue 14, September 2009
See notice on first page

PRELIMINARY

Troubleshooting

B-PCF monitoring and flow control

Configure Common BPCF Parameters

The Configure Common BPCF Parameters page/screen is provided with the

following monitoring and flow control related parameter field:

Threshold for number of packets within 200 ms per A10 link

This field is set to permit a B-PCF to accept only a certain number of packets on
each A10 link within each 200 ms time-window. The default value is 20, and the
range is 10 through 200.

Threshold of kilo bits within 200 ms per A10 link

This field is set to permit a B-PCF to accept only certain data bits on each A10
link within each 200 ms time-window. The default value is 70, and the range is 45
through 92.
DoS attack alarm

When a DoS attack from the network occurs, the BPCF raises a major alarm on the
ROP See the following example alarm:
**19 REPT: RNC 2, TPU 1, BPCF 5, ALARM [RNC 2]
21107: PCF under DoS attack from the Network.
PERCEIVED SEVERITY: MAJOR, CAUSE: CPU Cycles Limit Exceeded
FRAME 2
2007-04-10 01:19:02 REPORT #000001 FINAL

In the aforementioned example, the BPCF in slot 5 of TPU 1 of RNC 2 is under

attack.
For a sinusoidal type of DoS attack, there will be a one minute gap between two
consecutive DoS attack major alarms.
Note that Assert 21590 and Assert 41313 may be observed on the ROP for the mobile
under a DoS attack.
Dropped packets

When a PCF is under forward A10 attacks and the PCF starts dropping excessive
packets beyond the provisioned per-PCF threshold, there is a chance that some forward
packets from good users will also be dropped in the process. Affected mobiles may
experience slightly reduced end-to-end throughputs as TCP/IP retransmits dropped
packets.

PRELIMINARY

BPCF logs information for post-attack analysis

All B-PCF logs are by default available in the /app1 directory on the RNC-AP (where
RNCM VCVM is active). However, to be consistent with EPCF, the logs for
post-attack analysis are made available only on the local disk whenever the DoS attack
has occurred even for a few milliseconds.
The BPCF logs the complete attack related information to the diag file in the
$LTI_DIR/logs directory.
....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

8-20

B-PCF monitoring and flow control

Note that the procedure to log on to a B-PCF is provided in Replace a B-PCF

(p. 9-23).
Important! The diag files get overwritten reused within a certain number of
hours and hence the user is advised to contact Alcatel-Lucent within 8 hours of
attack alarms so that post-attack analysis can be performed with the log information
still available. An example of post-attack analysis is provided below.

PRELIMINARY

Troubleshooting

While there is a possibility that the logged packets come from good users the
probability of packets from attackers is much higher.
Note also, that if an attack lasts less than two seconds, there will be no alarm, but the
diag logs will contain attack related information.
SM count for packets discarded during DoS attack

When B-PCF monitoring and flow control is enabled (see also Configuration
(p. 8-19)) and a DoS attack is in progress, the SC-GICC drops the packets above a per
PCF threshold - Threshold of total throughput per PCF, and increments the SM count,
FwdPktDiscardCountBPCF#. (Details can be found in cgrncGICC15 Counts section of
401-610-135).
Analyzing DoS attack log

An example of a post-DoS attack log is given as follows:

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
8-21
Issue 14, September 2009
See notice on first page

PRELIMINARY

Fri Jun 14 10:35:23 CDT 2007, 715450 usec

Application: gre (ModId: 10003)
Location: ../com/gredriver.c on line 1929
Sequence Number: 4669
Message: Post Attack Info:
WindowID
Source IP
Port
GRE Key
623
0x87fefc4a
2043
1778417665
623
0x87fefc4a
2043
1778417665
623
0x87fefc4a
2043
1778417665
623
0x87fefc4a
2043
1778417665
623
0x87fefc4a
2043
1778417665
623
0x87fefc4a
2043
1778417665
623
0x87fefc4a
2043
1778417665
623
0x87fefc4a
2043
1778417665
623
0x87fefc4a
2043
1778417665
623
0x87fefc4a
2043
1778417665
624
0x87fefc4a
2043
1778417665
624
0x87fefc4a
2043
1778417665
624
0x87fefc4a
2043
1778417665
624
0x87fefc4a
2043
1778417665
624
0x87fefc4a
2043
1778417665
624
0x87fefc4a
2043
1778417665
624
0x87fefc4a
2043
1778417665

PRELIMINARY

Troubleshooting

B-PCF monitoring and flow control

624
624
624
625
625
625
625
625

0x87fefc4a
0x87fefc4a
0x87fefc4a
0x87fefc4a
0x87fefc4a
0x87fefc4a
0x87fefc4a
0x87fefc4a

2043
2043
2043
2043
2043
2043
2043
2043

1778417665
1778417665
1778417665
1778417665
1778417665
1778417665
1778417665
1778417665

Timestamp

The timestamp (14 10:35:23) can be used to judge the approximate time when the
attack occurred.
Window ID

The Window ID is the 200 ms duration during which the dropped packets were logged
Source IP

The Source IP is the attackers IP address. There is a possibility that the IP address
may have been spoofed. For example, 0x87fefc4a, when converted to decimal 135.254.252.74.
Port

The Port is the attackers source port.

GRE Key

The GRE key is modified, and hence need to be reconstructed as per the process that
follows.
Format

PRELIMINARY

The format of the GRE key is described in the following Figure.

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

8-22

B-PCF monitoring and flow control

Process

The GRE Key shown in the example log is 1778417665 (in decimal). In binary this
converts as follows:
0110 1010 0000 0000 1000 0000 0000 0001
By replacing the RNC-id bits with the actual RNC ID, which in this is example is 2
(0010) in binary, the following is seen:

PRELIMINARY

Troubleshooting

0110 1010 0001 0000 1000 0000 0000 0001

The decimal equivalent of the reconstructed GRE key changes to: 1779466241
Note that the example log is a specific example of a single session being attacked from
a single IP address. If different IP addresses and ports are used to originate the attack
on one or multiple sessiosn, the aforementioned information will vary accordingly.
Information from up to 400 dropped packets will get logged for post-analysis.
Suggested solutions

From the TPU GUI, increase the following thresholds:

Threshold of total throughput per PCF

Threshold for number of packets within 200 ms per A10 link

Threshold of kilo bits within 200 ms per A10 link

Major alarm due to empty PDSN

list (SFC 1xRNC A10/A11 Packet
Filteringis set to Y)

Perform in the folowing order:

1. Make sure that SFC is supposed to be
enabled.
2. Make sure that at least one PDSN has been
provisioned for the 1xRNC.

Minor alarm due to

filter-exemption being active

Contact ALU technical support.

Dynamic PDSNs are getting

blocked, but not provisioned
PDSNs

Perform in the following order:

1. Execute
GET:RNC a, TPU b, GICC c, PDSNLIST to

make sure that the GICC and B-PCFs have

the same list of PDSNs.
2. Check the Maximum Number of Dynamic
PDSNs tunable to make sure it is appropriate
(ensure that the limit is not 0). To modify the
tunable:
a. Login to OAM Proxy A
b. Enter: isql
c. Enter:
update TPU set MaxNumPDSNLimit=N
where RNCNumber=X

where: N = 32-128 (default=128)

X = RNC number

PRELIMINARY

3. Contact Alcatel-Lucent technical support.

8-24

1xRNC packet filtering

Problem

Actions to be taken

Informational message,

Perform in the following order:

A10A11_Dropped_Packet_
Rate_Exceeded_Thresholdappears

1. Check the A10/A11 Dropped Packet Rate

Threshold value and make sure it is
appropriate (not too high, but not too low).
To modify the tunable, perform the
following:
a. Login to OAM Proxy A
b. Enter: isql
c. Enter:

on the ROP

PRELIMINARY

Troubleshooting

update TPU set

A10A11DropPktThreshold=P
where RNCNumber=X

where: P = 1-100 (percent) (default=5)

X = RNC number
2. Execute
GET:RNC a, TPU b, GICC c, PDSNLIST to

make sure that GICC and B-PCF are in sync..

3. Make sure that the correct IP address for
each PDSN is listed (especially if its IP
address has changed recently).
4. Contact Alcatel-Lucent technical support.
Bogus packets are getting through,
that is, filtering is not stopping the
bogus packets.

Contact Alcatel-Lucent technical support.

PRELIMINARY

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
8-25
Issue 14, September 2009
See notice on first page

PRELIMINARY

Troubleshooting

Far
end CA audit
...................................................................................................................................................................................................................................
Introduction

Daily far end Community Address (CA) audits can be launched by means of the TPU
GUI.
Configuring far end CA audit

A hyper link has been added to the Admin screen of the TPU GUI that brings up the
Configure Far CA Reachability screen.
This screen enables the technician to enable and configure the time that a daily far end
CA audit will occur.
Important! The GUI screens only control whether or not a periodic audit will take
place. The user can always demand an audit through the CLI.
Audit sequence

Once enabled, all the CICCs in the TPU are audited, and all the FAR CAs previously
learned by the CICCs are tallied.
SC-GICCs

The FAR CA audit will run on both SC-GICCs. This is required to start the enhanced
loopbacks when the ATM ports are active on both the SC-GICCs.
Audit complete

Once the audit is complete, the FarCA audit manager consolidates the far end CA list
and starts the enhanced loopbacks to each CA (32 in a group at one time). It uses the
service command interface to issue commands to the ATM subsystems and then
waits for the response.
When loopbacks have been conducted on all the far end CAs, a result is sent to the
ROP.
Procedure

PRELIMINARY

The procedure for configuring far end CA audits is provided in To enable/disable far
end CA audits (p. 8-27).

8-26

To
enable/disable far end CA audits
...................................................................................................................................................................................................................................
Purpose

To enable/disable, and configure far end CA audits.

Reason to perform

PRELIMINARY

Troubleshooting

To aid in isolating connectivity issues.

Procedure

To enable/disable, and configure daily far end CA audits, proceed as follows:

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

Obtain access to TPU-GUI either by:

Direct access method. Refer to Accessing TPU GUI (p. 6-6).

EMS. Refer to Logging on to Element Management System (EMS) (p. 6-5).

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

If using EMS, at the OMP Web page you need to select 1X RNC TPU Web to navigate
to the 1X RNC TPU Web page. If using the direct access method, the same will result.
...................................................................................................................................................................................................

Click on the Admin button.

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
8-27
Issue 14, September 2009
See notice on first page

PRELIMINARY

Troubleshooting

To enable/disable far end CA audits

Result: The GUI navigates to the Admin screen. See the following example.

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

PRELIMINARY

Click on the Configure Far CA Reachability link.

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

8-28

To enable/disable far end CA audits

Result: The GUI navigates to the ConfigureFAR CA Reachability screen. See the

following example.

PRELIMINARY

Troubleshooting

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

Use the drop-down box to enable/disable the periodic audits as required, and enter the
start time in hours as required.
END OF STEPS
...................................................................................................................................................................................................

PRELIMINARY

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
8-29
Issue 14, September 2009
See notice on first page

PRELIMINARY

Troubleshooting

Application Processor (AP) problem solving

The information provided in this section is to be used to troubleshoot RNC-AP and

OAM Proxy AP related fault conditions. Tables are provided to guide the system user
through troubleshooting procedures for each known fault condition that yields a
warning or alarm.

PRELIMINARY

Contents
RNC AP OOS (components or alarms)

8-31

OAM Proxy AP OOS (components or alarms)

8-34

RNC-AP rebooting

8-37

LANS 1 and/or 2 OOS

8-39

EIN LAN OOS

8-41

LANS 3 and/or 4 OOS

8-42

8-30

RNC
AP OOS (components or alarms)
...................................................................................................................................................................................................................................
Introduction

The procedures provided in this section walk through various RNC AP OOS and alarm
conditions. In some cases, they will point to other procedures.

PRELIMINARY

Troubleshooting

Expected outcome

When all the provided procedures (Table 8-7, RNC-AP OOS (p. 8-31)) have been
fully executed, all RNC APs should be in service with no alarms. Note that more
detailed troubleshooting may frequently require WTSC support.
Table 8-7

RNC-AP OOS
Answer

Check Steps

1 Is the AP
stable, that
is, not in a
rolling
reboot?

IF NO
Go to RNC-AP rebooting (p. 8-37)
----------->

2 Is Reliable
Cluster
Computing
operational
(RCC)
operational?

IF NO,
go to
Question 3.

3 Is AP
ONLINE?

IF NO
Execute: aponline command
----------->

4 Can
RCCcstat
now be
executed?

IF NO
Contact WTSC for support.
----------->

5 Can CLI
commands
be executed
on the AP?

IF NO,
go to
Question 6.

6 Is AP
ONLINE?

IF NO
Execute: aponline command
----------->

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
8-31
Issue 14, September 2009
See notice on first page

PRELIMINARY

No.Question

PRELIMINARY
PRELIMINARY

Troubleshooting

RNC AP OOS (components or alarms)

Table 8-7

RNC-AP OOS (continued)

No.Question

Answer

Check Steps

7 Did AP
come
ONLINE?

IF NO
Check apadminlog for stopped platform processes related
-----------> to CLI.

8 Is problem
resolved?

IF NO
Contact WTSC for support.
----------->

9 Does CLI
status show
connectivity
failures?

IF YES
--------->

10 Does CLI
status show
the AP as
ACTIVE?

IF NO,
go to
Question 11.

11 Is EIN
active from
ECP side?

IF NO
Restore ECP side of EIN
----------->

12 Did AP
become
ACTIVE?

IF NO
Try remove, restore of AP
----------->

13 Did AP
become
ACTIVE?

IF NO
Try full init of AP
----------->

14 Did AP
become
ACTIVE?

IF NO
Check apadminlog for clues to problem, and if
-----------> unresolvable, contact WTSC for support.

15 Does CLI
status show
the RNC AP
applications
as ACTIVE
and
STANDBY?

IF NO
Do a remove, restore of the RNC application.
----------->

Go to:

EIN LAN OOS (p. 8-41)

LANS 3 and/or 4 OOS (p. 8-42)

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

8-32

RNC AP OOS (components or alarms)

Table 8-7

RNC-AP OOS (continued)

No.Question

Answer

Check Steps

16 Did the OOS

application
move to the
ACTIVE or
STANDBY
state?

IF NO
Init the AP
----------->

17 Did the OOS

application
move to the
ACTIVE or
STANDBY
state?

IF NO
Check apadminlog for clues to problem, and if
-----------> unresolvable, contact WTSC for support.

PRELIMINARY

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
8-33
Issue 14, September 2009
See notice on first page

PRELIMINARY

Troubleshooting

PRELIMINARY

Troubleshooting

OAM
Proxy AP OOS (components or alarms)
...................................................................................................................................................................................................................................
Introduction

The procedures provided in this section walk through various OAM Proxy AP OOS
and alarm conditions. In some cases, they will point to other procedures.
Expected outcome

When all the provided procedures (Table 8-8, OAM Proxy AP OOS (p. 8-34)) have
been fully executed, all OAM Proxy APs should be in service with no alarms. Note
that more detailed troubleshooting may frequently require WTSC support.

PRELIMINARY

Table 8-8

OAM Proxy AP OOS

No.Question

Answer

Check Steps

Is the AP
stable, that is,
not in a
rolling reboot?

IF NO
----------->

Go to RNC-AP rebooting (p. 8-37)

Is Reliable
Cluster
Computing
operational
(RCC)
operational?

IF NO, go
to
Question
3.

Is AP
ONLINE?

IF NO
----------->

Execute: aponline command

Can RCCcstat
now be
executed?

IF NO
----------->

Contact WTSC for support.

Can CLI
commands be
executed on
the AP?

IF NO, go
to
Question
6.

Is AP
ONLINE?

IF NO
----------->

Execute: aponline command

Did AP come
ONLINE?

IF NO
----------->

Check apadminlog for stopped platform processes

related to CLI.

8-34

OAM Proxy AP OOS (components or alarms)

Table 8-8

OAM Proxy AP OOS (continued)

No.Question

Answer

Check Steps

Is problem
resolved?

IF NO
----------->

Contact WTSC for support.

Does CLI
status show
connectivity
failures?

IF YES
--------->

Go to:

EIN LAN OOS (p. 8-41)

LANS 3 and/or 4 OOS (p. 8-42)

IF NO, go
to
Question
11.

11 Is EIN active
from ECP
side?

IF NO
----------->

Restore ECP side of EIN

12 Did AP
become
ACTIVE?

IF NO
----------->

Try remove, restore of AP

13 Did AP
become
ACTIVE?

IF NO
----------->

Try full init of AP

14 Did AP
become
ACTIVE?

IF NO
----------->

Check apadminlog for clues to problem, and if

unresolvable, contact WTSC for support.

15 Does CLI
status show
the OAM
Proxy AP
applications as
ACTIVE and
STANDBY?

IF NO
----------->

Do a remove, restore of the RNC application.

16 Did the OOS

application
move to the
ACTIVE or
STANDBY
state?

IF NO
----------->

Init the AP.

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
8-35
Issue 14, September 2009
See notice on first page

PRELIMINARY

10 Does CLI
status show
the AP as
ACTIVE?

PRELIMINARY

Troubleshooting

PRELIMINARY
PRELIMINARY

Troubleshooting

OAM Proxy AP OOS (components or alarms)

Table 8-8

OAM Proxy AP OOS (continued)

No.Question

Answer

Check Steps

17 Did the OOS

application
move to the
ACTIVE or
STANDBY
state?

IF NO
----------->

Check apadminlog for clues to problem, and if

unresolvable, contact WTSC for support.

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

8-36

RNC-AP
rebooting
...................................................................................................................................................................................................................................
Introduction

The procedures provided in this section troubleshoot the condition where an RNC-AP
is rebooting. In some cases, they will point to other procedures.

PRELIMINARY

Troubleshooting

Expected outcome

When all the provided procedures (Table 8-9, RNC-AP rebooting (p. 8-37)) have
been fully executed, the RNC-AP should be stable. Note that more detailed
troubleshooting may frequently require WTSC support.
Table 8-9

RNC-AP rebooting
Answer

Check Steps

Are LANs 1&2 both

OOS?

IF YES --------->

Go to LANS 1 and/or 2 OOS

(p. 8-39)

Did the watchdog miss

a heartbeat?

IF YES --------->

Check apadminlog and

/var/adm/messages for indications of
watchdog initiated reboot.

IF YES --------->

Search logs further for cause. If

unresolvable contact WTSC for
support.

Has the RCC sanity

monitor missed a
heartbeat from an
essential process?

IF YES --------->

Check apadminlog for indication if

RCC sanity monitor is missing a
heartbeat from a process.

IF YES --------->

Determine what process is not

responding and attempt to restart the
process. If unresolvable contact
WTSC for support.

Is the file system

failed or full?

IF YES --------->

Check /var/adm/messages for file

system initiated reboot complaints.

IF YES --------->

Attempt to resolve. If unresolvable

contact WTSC for support.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
8-37
Issue 14, September 2009
See notice on first page

PRELIMINARY

No. Question

PRELIMINARY
PRELIMINARY

Troubleshooting

RNC-AP rebooting

Table 8-9

RNC-AP rebooting

(continued)

No. Question

Answer

Check Steps

IF YES --------->

Check /var/adm/messages for

indications that the OS may be
initiating the reboot

IF YES --------->

Save crash dump and contact WTSC

for support.

Is the Operating
System (OS) causing
the reboot?

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

8-38

LANS
1 and/or 2 OOS
...................................................................................................................................................................................................................................
Introduction

The procedures provided in this section troubleshoot the conditions where LANs 1 or 2
are OOS. LANs 1 and 2 connect the AP to the dual rail LAN which connects to other
APs.

PRELIMINARY

Troubleshooting

Expected outcome

When all the provided procedures (Table 8-10, LANS 1 and/or 2 OOS (p. 8-39))
have been fully executed, the LAN(s) should be in-service. Note that more detailed
troubleshooting may frequently require WTSC support.
Table 8-10

LANS 1 and/or 2 OOS

No. Question

Answer

Check Steps

------------------->

Perform ifconfig -a command.

IF NO ----------->

Contact WTSC for support.

----------------->

For host name check:/etc/hosts

IF NO ----------->

Contact WTSC for support.

------------------->

Perform the following

Is the IP and netmask

configured correctly?

Is the host name

configured correctly?
NOTE: Important if
using host name instead
of IP.

Do ping tests pass?

Do ping test originating from

OOS LAN to some other AP
on MM dual rail LAN or
OMP

Test both LANs 1&2

Example:
ping -s -i hme0 ap14
ping -2 -i hme1 ap14
where:

- i: says use this port

- ap14: is an AP in the cluster
that is the target of the ping

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
8-39
Issue 14, September 2009
See notice on first page

PRELIMINARY

- s: pings 1x per second and

collects statistics

PRELIMINARY
PRELIMINARY

Troubleshooting

LANS 1 and/or 2 OOS

Table 8-10

LANS 1 and/or 2 OOS (continued)

No. Question

Answer

Check Steps

Are LAN 1 and LAN 2

cables properly
connected?

------------------->

Visually check cable connections.

Are cables ok?

------------------->

If all other tests to this point are

ok, check cables with a cable
tester.

Are LANS 1&2 STILL

OOS?

IF YES -------->

Contact WTSC for support.

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

8-40

EIN
LAN OOS
...................................................................................................................................................................................................................................
Introduction

The procedures provided in this section troubleshoot the conditions where the EIN
LAN is OOS.

PRELIMINARY

Troubleshooting

Expected outcome

When all the provided procedures (Table 8-11, EIN LAN OOS (p. 8-41)) have been
fully executed, the LAN(s) should be in-service. Note that more detailed
troubleshooting may frequently require WTSC support.
Table 8-11

EIN LAN OOS

No. Question

Answer

Check Steps

------------------->

Perform ifconfig -a command.

IF NO ----------->

Contact WTSC for support.

----------------->

For host name check:/etc/hosts

IF NO ----------->

Contact WTSC for support.

------------------->

Perform the following:

Is the IP and netmask

configured correctly?

Is the host name

configured correctly?

Can the EIN be pinged

from the OOS LAN?

Check that the EIN is in

service. If not restore from
the ECP.

Ping the EIN from the OOS

LAN # ping ein.

Is the EIN cable properly

connected?

------------------->

Visually check cable connections.

Are cables ok?

------------------->

If all other tests to this point are

ok, check cables with a cable
tester.

Is the EIN LAN still

OOS?

IF YES --------->

Contact WTSC for support.

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
8-41
Issue 14, September 2009
See notice on first page

PRELIMINARY

Troubleshooting

LANS
3 and/or 4 OOS
...................................................................................................................................................................................................................................
Introduction

The procedures provided in this section troubleshoot the conditions where LANs 3 or 4
from the RNC AP to the TPU is OOS.
Expected outcome

When all the provided procedures (Table 8-12, LANS 3 and/or 4 OOS (p. 8-42))
have been fully executed, the LAN(s) should be in-service. Note that more detailed
troubleshooting may frequently require WTSC support.
Table 8-12
No.

Question

Answer

Check Steps

Is the IP and netmask

configured correctly?

------------------->

Perform ifconfig -a command.

IF NO ----------->

Contact WTSC for support.

----------------->

For host name check:/etc/hosts

IF NO ----------->

Contact WTSC for support.

Can the EIN be pinged

from the OOS LAN?

------------------->

For ESC ping:

Are the LAN3 and

LAN4 cables properly
connected?

------------------->

Visually check cable connections.

Are cables ok?

------------------->

If all other tests to this point are

ok, check cables with a cable
tester.

Is either LAN3 or
LAN4 still OOS?

IF YES --------->

Contact WTSC for support.

PRELIMINARY

LANS 3 and/or 4 OOS

Is the host name

configured correctly?

# ping -s -i qfe2 172.x.y.z

8-42

Traffic Processing Unit (TPU) problem solving

PRELIMINARY

Troubleshooting

Purpose

The information provided in this section is to be used to troubleshoot TPU related

element fault conditions. Tables are provided to guide the system user through
troubleshooting procedures for each known fault condition that yields a warning or
alarm.
Contents
TPU OOS Components or Alarms

8-44

Alarm card fault

8-46

ESC fault

8-48

GICC fault

8-50

CICC fault

8-53

B-PCF fault

8-55

E-PCF fault

8-57

PCF reachability alarm

8-59

Assert Brevity Control

8-62

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
8-43
Issue 14, September 2009
See notice on first page

PRELIMINARY

Troubleshooting

TPU
OOS Components or Alarms
...................................................................................................................................................................................................................................
Introduction

The procedures provided in this section troubleshoot the conditions where TPU
components are OOS or alarmed.
Expected outcome

When all the provided procedures (Table 8-13, TPU OOS Components or Alarms
(p. 8-44)) have been fully executed, the TPU components should be in-service. Note
that more detailed troubleshooting may frequently require WTSC support.
Table 8-13

TPU OOS Components or Alarms

No. Question

Answer

Check Steps

Does TPU-GUI or
TPU-CLI status show
multiple cards in the
UNKNOWN state?

IF YES
--------->

Ensure the card power is on.

Are they ALL GREEN....

no faults?

IF NO, go to
Question 3.

Are some power modules

GREEN... no faults?

IF NO --------->

Check the power modules status

LEDs for the shelf with card(s) in
the UNKNOWN state.

Check power distribution system if

power is reaching some power
modules
Test power module and replace if
necessary.

PRELIMINARY

Contact WTSC for support as

needed.
4

Is the SC-GICC for the

shelf with the
UNKNOWN cards in the
ENABLED state?

IF YES, go to
Question 5.

Is the CMM for the shelf

with the UNKNOWN
cards in the enabled
state?

IF YES
--------->

Attempt to power cycle the card

slot using TPUCLI. Use:
reset: rnc a, tpu b, slot d
If the slot does not recover from
power cycling the slot, or if the
SCGICC for the shelf is
UNKNOWN, contact WTSC for
support.

8-44

TPU OOS Components or Alarms

Table 8-13

TPU OOS Components or Alarms

(continued)

No. Question

Answer

Check Steps

IF YES
--------->

Go to Alarm card fault (p. 8-46)

Does an Alarm card

show a fault?
NOTE: Determined by
any of the following:
TPUGUI, TPUCLI,
Alarm Card indicators

Does an ESC card show

FAULT?

IF YES
--------->

Go to ESC fault (p. 8-48)

Does an GICC card show

FAULT?

IF YES
--------->

Go to GICC fault (p. 8-50)

Does an CICC card show

FAULT?

IF YES
--------->

Go to CICC fault (p. 8-53)

10 Does a B-PCF card show

FAULT?

IF YES
--------->

Go to B-PCF fault (p. 8-55)

IF YES
--------->

Go to E-PCF fault (p. 8-57)

PRELIMINARY

Troubleshooting

(Use EMS-GUI)
11 Does an E-PCF show
FAULT?
(Use EMS-GUI)

PRELIMINARY

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
8-45
Issue 14, September 2009
See notice on first page

PRELIMINARY

Troubleshooting

Alarm
card fault
...................................................................................................................................................................................................................................
Introduction

The procedures provided in this section troubleshoot the conditions where an Alarm
card is faulted.
Expected outcome

When all the provided procedures (Table 8-14, Alarm card fault (p. 8-46)) have been
fully executed, the alarm card should be in-service. Note that more detailed
troubleshooting may frequently require WTSC support.
Table 8-14

Alarm card fault

No. Question

Answer

Does TPUGUI or
TPUCLI status show
the Alarm card as
UNKNOWN?

IF YES, go to
Question 2.

Is the Alarm card

present?

IF NO
--------->

Check Steps

Populate card slot.

IF YES, go to
Question 3.
3

Is the card powered?

Is the HOT SWAP

LED ON?

IF YES, go to
Question 4.
IF NO
--------->

Check that power modules are ok and

power distribution.

IF YES
--------->

Ensure that the card is fully seated and

the latches locked.

PRELIMINARY

If the HOT SWAP LED fails to

extinguish, contact WTSC for support
5

Does the TPUGUI or

TPUCLI status show
the Alarm card as
DISABLED.... or...is
the STATUS LED
RED...indicating
FAULT?

IF YES to
Attempt to recover via a reset;depress the
either------------------->
front panel for at least 7 seconds

Does the status LED

go steady or
blinking GREEN?

IF NO
--------->

Contact WTSC for support

8-46

Alarm card fault

Table 8-14

Alarm card fault

(continued)

No. Question

Answer

Check Steps

Does the
rncadminlog show
alarms from the
Alarm card?

IF YES
--------->

For alarms related to power module or fan

failures, check the power module and fan
STATUS LEDS, if they show FAULT
replace the power module.

If the alarm is a
CMM sync alarm,
are both CMMs
either ACTIVE or
STANDBY?

IF NO
----------->

Refer to the TPU OOS Components or

Alarms (p. 8-44) procedure.

IF YES
--------->

Contact WTSC for support

PRELIMINARY

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
8-47
Issue 14, September 2009
See notice on first page

PRELIMINARY

Troubleshooting

PRELIMINARY

Troubleshooting

ESC
fault
...................................................................................................................................................................................................................................
Introduction

The procedures provided in this section troubleshoot the conditions where an ESC is
faulted.
Expected outcome

When all the provided procedures (Table 8-15, ESC fault (p. 8-48)) have been fully
executed, the ESC should be in-service. Note that more detailed troubleshooting may
frequently require WTSC support.
Table 8-15

ESC fault

No. Question

Answer

Does TPUGUI or TPUCLI

status show the ESC as
UNKNOWN?

IF YES, go to
Question 2.

Is the ESC present?

IF NO --------->

Check Steps

Populate card slot.

IF YES, go to
Question 3.
3

Is the card powered?

Is the HOT SWAP LED

ON?

IF YES, go to
Question 4.
IF NO --------->

Check that power modules are

ok and power distribution.

IF YES --------->

Ensure that the card is fully

seated and the latches locked.
If the HOT SWAP LED fails
to extinguish, contact WTSC
for support

PRELIMINARY

Does the TPUGUI or

TUPCLI status show the
ESC as DISABLED, or is
the SYSTEM LED OFF and
the FAULT LED RED?

IF YES to either
------------------->

Does the SYSTEM LED go

YELLOW...card booting
GREEN...card OK FAULT
LED go off

IF NO --------->

Attempt to power cycle the

card slot using TPUCLI. Use:
reset: rnc a, tpu b, slot d

Contact WTSC for support

8-48

ESC fault

Table 8-15

ESC fault

(continued)

No. Question

Answer

Check Steps

IF YES --------->

For ESC external ports

FAULTS, check external
wiring.

Does TPUGUI or TPUCLI

show ESC connectivity
alarms?

If visual or cable tester checks

pass contact WTSC for
support.

PRELIMINARY

Troubleshooting

For ESC backpanel port

FAULTS, check:

ESC to ESC external

cables are in place.

That the root ESCs (upper

shelf slot 2, lower shelf
slott 21) are ACTIVE.

If still not resolved,

contact WTSC for support.

PRELIMINARY

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
8-49
Issue 14, September 2009
See notice on first page

PRELIMINARY

Troubleshooting

GICC
fault
...................................................................................................................................................................................................................................
Introduction

The procedures provided in this section troubleshoot the conditions where a GICC card
is faulted.
Expected outcome

When all the provided procedures (Table 8-16, GICC fault (p. 8-50)) have been fully
executed, the GICC should be in-service. Note that more detailed troubleshooting may
frequently require WTSC support.
Table 8-16

GICC fault

No.

Question

Answer

Does TPUGUI or
TPUCLI status show
GICC PROC 0 as
UNKNOWN?

IF YES, go to
Question 2.

Is the GICC
present?

IF NO --------->

Check Steps

Populate card slot.

IF YES, go to
Question 3.
3

Is the card powered?

Any GICC LEDs
ON?

Is the HOT SWAP

LED ON?

IF YES, go to
Question 4.
IF NO --------->

Check that power modules are ok

and power distribution.

IF YES --------->

Ensure that the card is fully seated

and the latches locked.

PRELIMINARY

If the HOT SWAP LED fails to

extinguish, contact WTSC for
support.

8-50

GICC fault

Table 8-16

GICC fault

(continued)

No.

Question

Answer

Check Steps

Is the PROGRAM
LED 1 steady
GREEN...indicating
an initialization
FAULT?

IF YES --------->

Attempt to recover via an

escalating reset:

1st attempt a software reset

from TPUCLI:
# reset: rnc a, tpu b, gicc c

2nd attempt a power cycle of

the slot from TPUCLI:
# reset: rnc a, tpu b. slot d

PRELIMINARY

Troubleshooting

If neither works, contact WTSC

for support.
6

Does TPUGUI or
TPUCLI alarm
status show any
OC3 alarms?

IF YES to
Identify the card, OC3 port and
either------------------->
alarm type:
1. For Receive Side LOS alarm,
check the OC3 wiring from the
switch to the ATM port and
switch configuration
2. Check if the switch is
receiving a signal from this
OC3/ATM port. If yes, it
should contain a remote alarm
signal from the GICC
OC3/ATM port
3. For side sync alarm, if there is
an active OC3 connection
connected to either ports 0 or
1 of the GICC, contact WTSC
for support.
4. For received remote alarms,
use loopback commands to
determine the point at which
the OC3 path is broken.
5. It may be necessary to also run
a loopback command from the
far end ATM.

IF YES --------->

Check the configuration tables at

the ATM and the ATM address at
the GICC port .(for a 5EGW this
is an algorithm using the 5E
community address)

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
8-51
Issue 14, September 2009
See notice on first page

PRELIMINARY

Does TPUGUI or
TPUCLI alarm
status show any
ATM alarms?

PRELIMINARY

Troubleshooting

GICC fault

Table 8-16

GICC fault

(continued)

No.

Question

Answer

Check Steps

Does TPUGUI or
TPUCLI alarm
status show any
external ethernet
alarms... or...
A8-A9, A10/A11,
and PCF reachability
alarms?

IF YES --------->

Is an external ethernet cable

present on the front of both
SC-GICCS?
Is the connection from the
customer network connected to the
correct FIP port?
Are the target IP addresses
configured correctly?
Are the target IP network devices
IS?

PRELIMINARY

If this does not restore the external

ethernet port to service, contact
WTSC for support.

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

8-52

CICC
fault
...................................................................................................................................................................................................................................
Introduction

The procedures provided in this section troubleshoot the conditions where a CICC card
is faulted.

PRELIMINARY

Troubleshooting

Expected outcome

When all the provided procedures (Table 8-17, CICC fault (p. 8-53)) have been fully
executed, the GICC should be in-service. Note that more detailed troubleshooting may
frequently require WTSC support.
Table 8-17

CICC fault

No. Question

Answer

Does TPUGUI or TPUCLI

status show CICC PROC 0
as UNKNOWN?

IF YES, go
to Question
2.

Is the CICC present?

IF NO
--------->

Check Steps

Populate card slot.

IF YES, go
to Question
3.
3

Is the card powered? Any

CICC LEDs ON?

Is the HOT SWAP LED

ON?

IF YES, go
to Question
4.
IF NO
--------->

Check that power modules are ok

and power distribution.

IF YES
--------->

Ensure that the card is fully seated

and the latches locked.
If the HOT SWAP LED fails to
extinguish, contact WTSC for
support.

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
8-53
Issue 14, September 2009
See notice on first page

PRELIMINARY

Troubleshooting

CICC fault

Table 8-17

CICC fault

(continued)

No. Question

Answer

Check Steps

IF YES
--------->

Attempt to recover via an escalating

reset:

Is the POWER/FAULT LED

steady RED...indicating an
initialization FAULT? (The
LED blinks during init).

1st attempt a software reset

from TPUCLI:
# reset: rnc a, tpu b, cicc c

2nd attempt a power cycle of

the slot from TPUCLI:
# reset: rnc a, tpu b. slot d

If neither works, contact WTSC for

support.

PRELIMINARY

Does TPUGUI or TPUCLI

show processor 0 as
ACTIVE and processors 1
or 2 as DISABLED or with
alarm faults?

IF YES
--------->

T he card is handling some amount

of call processing traffic. DO NOT
ATTEMPT CARD RESETS TO
RECOVER PROCESSORS 1 OR 2.
Contact WTSC for support.

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

8-54

B-PCF
fault
...................................................................................................................................................................................................................................
Introduction

The procedures provided in this section troubleshoot the conditions where a fault
conditions B-PCF card is faulted.

PRELIMINARY

Troubleshooting

Expected outcome

When all the provided procedures (Table 8-18, B-PCF fault (p. 8-55)) have been
fully executed, the B-PCF should be in-service. Note that more detailed
troubleshooting may frequently require WTSC support.
Table 8-18

B-PCF fault

No.

Question

Answer

Does the TPU-GUI show a

B-PCF as Disabled or
Uknown?

IF YES, go to
Question 2.

Is the B-PCF present?

IF NO --------->

Check Steps

Populate card slot.

IF YES, go to
Question 3.
3

Is the card powered? Any

B-PCF LEDs ON?

Is the HOT SWAP LED

ON?

IF YES, go to
Question 4.
IF NO --------->

Check that power

modules are ok and
power distribution.

IF YES --------->

Ensure that the card is

fully seated and the
latches locked.
If the HOT SWAP LED
fails to extinguish,
contact WTSC for
support.

Does TPU-GUI show

alarms on the B-PCF?

IF YES, go to
Question 2.

Does the GICC have any

A8-A9 connectivity alarms?

IF YES --------->

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
8-55
Issue 14, September 2009
See notice on first page

PRELIMINARY

Follow the external

ethernet FAULT
procedure under GICC,
see Table 8-16, GICC
fault (p. 8-50).

PRELIMINARY

Troubleshooting

B-PCF fault

Table 8-18

B-PCF fault

(continued)

No.

Question

Answer

Check Steps

Is the alarm is for PDSN

connectivity?

IF YES --------->

Is the PDSN POOL

configured?
Are any PDSNs in
service?
Do any alarms show
BPCF processes not
running?

PRELIMINARY

Contact WTSC for

support.

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

8-56

E-PCF
fault
...................................................................................................................................................................................................................................
Introduction

The procedures provided in this section troubleshoot the conditions where a E-PCF is
faulted.

PRELIMINARY

Troubleshooting

Expected outcome

When all the provided procedures (Table 8-19, E-PCF fault (p. 8-57)) have been
fully executed, the E-PCF should be in-service. Note that more detailed troubleshooting
may frequently require WTSC support.
Table 8-19

E-PCF fault

No.Question

Answer

Check Steps

Does the EMS GUI

show a E -PCF as OOS
or UNKNOWN?

IF YES, go
to Question
2.

Is the E-PCF present

and powered on?

IF YES, go
to Question
3.

Can you SSH to the

EPCF?

IF NO
----------->

Access the E-PCF console port via a

local terminal server.

Are the EPCF processes

running?

IF NO
----------->

Contact WTSC for support.

Does EMS GUI show

alarms on the E-PCF?

IF YES, go
to Question
6.

Is the alarm for A8-A9

connectivity?

IF YES, go
to Question
7.

Does the GICC have

any A8-A9 connectivity
alarms?

IF YES
--------->

Is the alarm is for

PDSN connectivity?

IF YES, go
to Question
9.

Follow the external ethernet FAULT

procedure under GICC, see Table 8-16,
GICC fault (p. 8-50).

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
8-57
Issue 14, September 2009
See notice on first page

PRELIMINARY
PRELIMINARY

Troubleshooting

E-PCF fault

Table 8-19

E-PCF fault

(continued)

No.Question

Answer

Check Steps

IF YES
--------->

Contact WTSC for support.

Is the PDSN POOL

configured? Are any
PDSNs in service? Do
any alarms show BPCF
processes not running?

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

8-58

PCF
reachability alarm
...................................................................................................................................................................................................................................
Introduction

The RNC FSRMs periodically heartbeat with PCFs. If no PCFs are reachable, the
FSRM (a CICC processor) will raise an alarm (1) (see related Related ROP messages
(p. 8-61)).

PRELIMINARY

Troubleshooting

Reasons

Reasons why a PCF may not be reachable include:

Overload
PCF interface falure

PCF is unable to contact any PDSNs.

Failure of an interface with an external PCF can be caused by problems with the
RNCs A8/A9 interface or with the A8/A9 network. Failure of the interface between a
PCF and a PDSN can be caused by problems in the A10/A11 network. B-PCFs
interface with PDSNs via the RNCs A10/A11 interface.
FSRM monitoring

The RNC monitors the number of FSRMs that indicate a PCF interface failure and
raises the appropriate alarm based on the percentage of PCFs reporting the problem, as
follows:

If more than 25% of the FSRMs have raised this alarm, the RNC raises a major
alarm (2).

If more than 50% of the FSRMs have raised this alarm, the RNC raises a critical
alarm (3).

If more than 90% of the FSRMs have raised this alarm, the RNC raises a critical
alarm and declares itself N/A (4).

Note that these thresholds are tunable via the TPU GUI.
When the RNC declares itself Not Available (N/A), the ECP no longer assigns new
calls to this RNC. At this point, the PCF Reachability condition is considered to be
active. The RNC will suppress the individual FSRM alarms on the TPU GUI while this
critical N/A alarm is active.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
8-59
Issue 14, September 2009
See notice on first page

PRELIMINARY

When an FSRM is able to establish new calls with a PCF, the RNC clears the critical
alarm and indicates to the ECP that it is OK and the ECP begins assigning new calls
to this RNC again.

PRELIMINARY

Troubleshooting

PCF reachability alarm

Cause and recovery

The reachbility condition may be caused by a silent falure in the network or GICC. To
recover from this condition, when a PCF reachbility condition persists for more than 1
minute, the RNC will attempt a recovery action.
If both A10/A11 interfaces are unlocked/enabled, the RNC will attempt to switchover
the A10/A11 gateway on the SC-GICC (if successful, a message (8) is reported on the
ROP). If this switchover is successful, but the condition does not clear, the RNC will
attempt to switch over the A8/A9 interface (7).
Important! The technician must monitor the ROP for these conditions (alarms)
because an alarm may clear automatically if the RNCs automatic recovery
(gateway switchover) is successful in restoring service.
Cause

Generally reachability conditions will be caused by problems with the A10/A11

interface or A10/A11 network. FSRMs interface with B-PCFs in the same RNC via an
internal interface, not the external A8/A9 interface, so it is unlikely that an A8/A9
interface problem will cause the PCF reachability condition.
Switchover

If a switchover occurs, and the reachability condition clears, the technician should
diagnose the interface that was switched. However, the technician cannot rely solely on
monitoring via SDP because the alarm may clear even though the problem still exists
on the standby interface.
The reason for this is that the RNC cannot monitor the entire connection to the
PCFs/PDSNs on the standby side due to the nature of the IP network.
If the problem cannot be traced to the network, Lucent field support may be required
to determine if the problem is in the GICC.
An IP gateway switch over comment (SWITCH-RNC) is supported that allows the
technician to force an A8/A9 or A10/A11 gateway switchover for trouble shooting and
verification purposes. A switchover will only occur if both gateways are
unlocked/enabled.
Obtaining status

PRELIMINARY

A8/A9 and A10/A11 gateway status is available via the GET-RNC-TPU-GICC-STATE

command. The administrative, operational and usage states appear under the SC-GICC.
The usage state for the serving gateway is active, while the non-serving is idle.

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

8-60

PCF reachability alarm

Related ROP messages

The following PCF ROP messages are applicable:

1. REPT: RNC a, TPU b, CICC c, Proc d, ALARM
2. REPT: RNC a, TPU b, ALARM
RNC has exceeded PCF Reachability Major Threshold
3. REPT: RNC a, TPU b, ALARM
RNC has exceeded PCF Reachability Critical Threshold
4. REPT: RNC a, TPU b, ALARM
RNC has exceeded PCF Reachability N/A Threshold.
5. REPT: RNC a, TPU b, ALARM
Disabled BPCFs exceeds Threshold
6. REPT: RNC a, TPU b, ALARM
Percentage of unlocked/enabled internal B-PCFs reporting all RP connections failed
alarm exceeds the threshold.

PRELIMINARY

Troubleshooting

7. REPT: RNC a, TPU b

RIM has Switched the A8/A9 Gateway to RNC a:TPU c:GICC d:Proc 0
8. REPT: RNC a, TPU b
RIM has Switched the A10/A11 Gateway to RNC a:TPU c:GICC d:Proc 0

PRELIMINARY

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
8-61
Issue 14, September 2009
See notice on first page

PRELIMINARY

Troubleshooting

Assert
Brevity Control
...................................................................................................................................................................................................................................
Introduction

The RNC may generate asserts (defensive code checks) if it detects an internal
problem such as a software error.
Assert reporting

Asserts are reported in the REPT-RNC-DCF output report. These types of anamolies
normally require Lucent field support for diagnosis of the problem.
If a large number of asserts of a specific type are being generated, asserts are throttled
and a summary message (REPT-RNC-DCF-SUMMARY) is reported on the ROP.
Assert throttling

Assert throttling can be disabled/enabled via the RNC assert brevity control commands
INH:RNC-ABREVC disables the assert throttling to the ROP and ALW:RNCABREVC command re-enables the assert throttling. GET:RNC-ABREVC displays the
current brevity control status.

PRELIMINARY

Note that all asserts are always reported to the RNC admin log regardless of the
brevity control setting.

8-62

TPU GUI access problem solving

PRELIMINARY

Troubleshooting

Purpose

The information provided in this section is to be used to troubleshoot TPU GUI access
issues. Tables are provided to guide the system user for each known TPU GUI access
problem.
Expected outcome

When all the provided procedures have been fully executed, access to TPU GUI should
be realized. Note that more detailed troubleshooting may require WTSC support.
Contents
Unable to access TPU GUI

8-64

Verify correct IP address for direct access

8-65

Verify TPU GUI application is running (CLI command)

8-67

Verify TPU GUI application is running (EMS GUI)

8-69

Verify Java version for Internet Explorer

8-74

Eliminate file conflicts and verify proxies

8-76

Update Java runtime parameters

8-81

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
8-63
Issue 14, September 2009
See notice on first page

PRELIMINARY

Troubleshooting

Unable
to access TPU GUI
...................................................................................................................................................................................................................................
Introduction

Measures that system users can take when accsess to TPU GUI is inhibited are
provided in the information that follows.
Problem checklist

The following list provides questions that isolate potential problem issues that can be
resolved when access to TPU GUI is inhibited:
Important! If you are attempting to access TPU GUI for the first time, then you
need to review subparagraphs (3) through (5) to ensure that your browser and PC
are set up correctly.
1. For direct access, are you using the correct IP address assigned for the TPU GUI?
See Verify correct IP address for direct access (p. 8-65).
2. Is the TPU GUI application up and running? See Verify TPU GUI application is
running (CLI command) (p. 8-67) or Verify TPU GUI application is running
(EMS GUI) (p. 8-69).
3. Is Java version jre1.6.0_10 or later (necessary for TPU GUI access) currently
running on your PC? See Verify Java version for Internet Explorer (p. 8-74).
4. Have you eliminated all known potential temporary file conflicts, and are your
browsers proxies disabled? See Eliminate file conflicts and verify proxies
(p. 8-76).
5. Does your PC have the correct Java runtime parameters? See Update Java runtime
parameters (p. 8-81).
6. Is TPU GUI access still denied, after verifying and updating as described in
subparagraphs through? If so, you should either contact Alcatel-Lucent, or you can
go to the Internet Explorer browsers menu bar and click on:
a. Tools -> Internet Options -> Advanced
b. Verify which options are available for Java.

PRELIMINARY

c. Try different options, and verify if you can then access TPU GUI.
d. If access is still denied, contact Alcatel-Lucent..

8-64

Verify
correct IP address for direct access
...................................................................................................................................................................................................................................
Purpose

To verify if you are using the correct IP address for direct access of TPU GUI.
Reason to perform

PRELIMINARY

Troubleshooting

You have attempted to access TPU GUI directly, and access currently appears to be
inihibited.
Background information

The IP address that needs to be specified in the url for the TPU GUI is the fourth IP
address of four consecutive IP addresses that are used for the OAM Proxy APs. This
address can be located by connecting to either OAM Proxy AP, and executing a
specific UNIX command.
Procedure

To verify that you are using the correct IP address for TPU GUI access, proceed as
follows:
...................................................................................................................................................................................................

Login to either OAM Proxy AP.

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

Execute the following command from the UNIX shell:

ifconfig -a <CR>

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
8-65
Issue 14, September 2009
See notice on first page

PRELIMINARY

Troubleshooting

Verify correct IP address for direct access

Result An output similar to the following occurs:

The IP address for TPU GUI is the IP address of qfe1 plus 3. In this example it would
be 135.2.12.197, which is also reflected in qfe1:1 which indicates that the TPU GUI is
active on this OAM Proxy AP.
Important! If OMC-RAN exists, qfe1:1 could point to the IP address of the active
OMC-RAN, if OMC-RAN was introduced before RNC. In that case qfe1:2 would
display the IP address of the TPU GUI to indicate that the TPU GUI is active on
the OAM Proxy AP.
END OF STEPS

PRELIMINARY

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

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

8-66

Verify
TPU GUI application is running (CLI command)
...................................................................................................................................................................................................................................
Purpose

To verify if the TPU GUI application is up and running via CLI command.
Reason to perform

PRELIMINARY

Troubleshooting

You have attempted to access TPU GUI and access currently appears to be inihibited.
Background information

The TPU GUI application runs on the OAM Proxy AP pairs. The TPU GUI application
should be active on one of the pair, and standby on the other. If it is active on neither
OAM Proxy AP, no communication via TPU GUI will be possible until the outage is
resolved.
Procedure

To determine the TPU GUI application status via CLI command, proceed as follows:
...................................................................................................................................................................................................

Obtain access to a CLI interface as discussed in RNC-related interfaces (p. 6-3).

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

Enter the following command:

OP:AP XX, STATUS <CR>

where: XX = the number of either OAM Proxy AP of the pair.

Result An output similar to the following example occurs:

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
8-67
Issue 14, September 2009
See notice on first page

PRELIMINARY

PRELIMINARY
PRELIMINARY

Troubleshooting

Verify TPU GUI application is running (CLI command)

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

If the TPU GUI is not active on either OAM Proxy AP, no communication via TPU
GUI will be possible until the outage is resolved.
END OF STEPS
...................................................................................................................................................................................................

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

8-68

Verify
TPU GUI application is running (EMS GUI)
...................................................................................................................................................................................................................................
Purpose

To verify if the TPU GUI application is up and running via EMS GUI.
Reason to perform

PRELIMINARY

Troubleshooting

You have attempted to access TPU GUI and access currently appears to be inhibited.
Background information

The TPU GUI application runs on the OAM Proxy AP pairs. Normally, the TPU GUI
application should be active on one of the pair, and standby on the other.
Procedure

To determine the TPU GUI application status via EMS GUI, proceed as follows:
...................................................................................................................................................................................................

Log on to the EMS GUI.

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
8-69
Issue 14, September 2009
See notice on first page

PRELIMINARY

Troubleshooting

Verify TPU GUI application is running (EMS GUI)

Result The OMP Web Page (see the following example) appears.

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

PRELIMINARY

Click on the Mobility Manager - AP Cluster (MM-APCs) icon.

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

8-70

Verify TPU GUI application is running (EMS GUI)

Result The AP Summary Page (see the following example) appears.

PRELIMINARY

Troubleshooting

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

Scroll until you find the AP ID numbers that correspond to the OAM Proxy AP pair.
Note that if the related capsule under Maint State is not green for one AP of the pair,
that does not necessarily indicate that the TPU GUI is faulted.
...................................................................................................................................................................................................

Click on the identifier number for either OAM Proxy AP of the pair.

PRELIMINARY

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
8-71
Issue 14, September 2009
See notice on first page

PRELIMINARY
PRELIMINARY

Troubleshooting

Verify TPU GUI application is running (EMS GUI)

Result A screen such as shown in the following examples appears.

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

8-72

Verify TPU GUI application is running (EMS GUI)

PRELIMINARY

Troubleshooting

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

PRELIMINARY

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
8-73
Issue 14, September 2009
See notice on first page

PRELIMINARY

Troubleshooting

Verify
Java version for Internet Explorer
...................................................................................................................................................................................................................................
Purpose

To verify which version of Java is currently running for your Internet Explorer
browser.
Reason to perform

You are currently unable to access TPU GUI via your Internet Explorer browser, and
you have multiple Java release versions located in your Java folder stored in your
Program Files folder.
Procedure

Perform the following procedure to verify the version of Java that is currently running
for your PCs Internet Explorer browser:
...................................................................................................................................................................................................

Bring up the Internet Explorer Browser on your PC.

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

PRELIMINARY

In the browsers top tool bar click on Tools and then Sun Java Console.

8-74

Verify Java version for Internet Explorer

Result A window similar to the following example appears.

PRELIMINARY

Troubleshooting

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

If you are unable to view the top two lines that indicate the version of Java that is
currently running for Internet Explorer, scroll the window up.
...................................................................................................................................................................................................

If you dont have the correct version of Java (that is, Version 1.6.0_10), contact
Alcatel-Lucent for assistance.
END OF STEPS
...................................................................................................................................................................................................

PRELIMINARY

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
8-75
Issue 14, September 2009
See notice on first page

PRELIMINARY

Troubleshooting

Eliminate
file conflicts and verify proxies
...................................................................................................................................................................................................................................
Purpose

Use this procedure to eliminate potential temporary file browser conflicts, and verify
whether the browsers proxies have been disabled.
Reason to perform

You are unable to access TPU GUI and you need to ensure that the browser proxies
are disabled and that no potential temporary file browser conflicts exist.
Procedure

Perform the following procedure to eliminate temporary file browser conflicts, and to
verify if the browsers proxies have been disabled:
...................................................................................................................................................................................................

Start up your Internet Explorer browser.

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

PRELIMINARY

Click on Tools and then Internet Options...

8-76

Eliminate file conflicts and verify proxies

Result The Internet Options window (as seen in the following example) appears.

PRELIMINARY

Troubleshooting

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

If the General tab is not already selected, select it and then click on Delete Files...
and then OK.
Result Any temporay files that might create conflicts are deleted.
...................................................................................................................................................................................................

Click on the Connections tab.

PRELIMINARY

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
8-77
Issue 14, September 2009
See notice on first page

PRELIMINARY

Troubleshooting

Eliminate file conflicts and verify proxies

Result The Connections tab window (as seen in the following example) appears.

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

PRELIMINARY

Click on LAN Settings...

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

8-78

Eliminate file conflicts and verify proxies

Result The Local Area Lan (LAN) Settings window (as seen in the following

example) appears.

PRELIMINARY

Troubleshooting

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

If the Use a proxy server for your LAN... box does not contain a check mark,
proceed to Step 8. If the Use a proxy server for your LAN... box contains a check
mark, click in the box to remove it.
Result The associated proxy elements become inert (grayed out).
...................................................................................................................................................................................................

Cick on OK.
Result The following occurs:

The proxies for the Internet Explorer browser are disabled.

The Local Area Lan (LAN) Settings window closes.

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
8-79
Issue 14, September 2009
See notice on first page

PRELIMINARY

Troubleshooting

Eliminate file conflicts and verify proxies

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

Close the Internet Options window by clicking on OK.

Result The Internet Options window closes.
...................................................................................................................................................................................................

Restart your Internet Explorer browser.

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

Proceed to Update Java runtime parameters (p. 8-81) (if necessary).

END OF STEPS

PRELIMINARY

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

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

8-80

Update
Java runtime parameters
...................................................................................................................................................................................................................................
Purpose

Use this procedure to update the PCs related Java runtime parameters of the Java
Plug-in Control Panel.

PRELIMINARY

Troubleshooting

Reason to perform

You are unable to access TPU GUI and you need to ensure that the runtime parameters
of the Java Plug-in Control Panel are correct.
Procedure

Perform the following procedure to update the PCs related Java runtime parameters of
the Java Plug-in Control Panel:
...................................................................................................................................................................................................

Via the PCs Start menu select, Settings, then Control Panel, and then Java Plug-in.

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
8-81
Issue 14, September 2009
See notice on first page

PRELIMINARY

Troubleshooting

Update Java runtime parameters

Result The Java Plug-in Control Panel, as shown in the following example

appears.

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

PRELIMINARY

Select the Advanced tab and enter the following string in the Java Runtime
Parameters field, as shown in the following example: Dsun.java2d.noddraw.

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

8-82

Update Java runtime parameters

PRELIMINARY

Troubleshooting

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

Click the Apply button.

Result The Java runtime parameters are updated.
...................................................................................................................................................................................................

Select the Cache tab.

PRELIMINARY

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
8-83
Issue 14, September 2009
See notice on first page

PRELIMINARY

Troubleshooting

Update Java runtime parameters

Result The Cache tab window (as seen in the following example) appears:

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

PRELIMINARY

Select Clear.

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

8-84

Update Java runtime parameters

Result The Confirmation Needed - Cache box (as seen in the following example)

appears:

PRELIMINARY

Troubleshooting

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

Selecy Yes.
Result The following occurs:

The Cache is cleared.

The Confirmation Needed - Cache box closes.

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

Click on the X box of the Java Plug-in Control Panel.

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
8-85
Issue 14, September 2009
See notice on first page

PRELIMINARY

PRELIMINARY
PRELIMINARY

Troubleshooting

Update Java runtime parameters

Result The Java Plug-in Control Panel closes.

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

Restart your Internet Explorer browser.

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

8-86

Automatic Protection Switching (APS) problem

solving
Overview
...................................................................................................................................................................................................................................

PRELIMINARY

Troubleshooting

Purpose

The information provided in this section is to be used to troubleshoot APS fault

conditions. Tables are provided to guide the system user through troubleshooting
procedures for each known APS fault condition that yields a warning or alarm. All
procedures assume that APS is enabled.
Expected outcome

When all the provided procedures have been fully executed, the APS condition(s)
should be cleared. Note that more detailed troubleshooting may require WTSC support.
Contents
APS mated GICC not available - major alarm

8-88

APS Data Out Of Sync failure - major alarm

8-89

APS far end protection failure - major alarm

8-90

APS mode mismatch - major alarm

8-91

Unable to protection switch due to AISL - major alarm

8-93

APS protection byte failure - warning

8-94

APS channel mismatch - minor alarm

8-96

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
8-87
Issue 14, September 2009
See notice on first page

PRELIMINARY

Troubleshooting

APS
mated GICC not available - major alarm
...................................................................................................................................................................................................................................
Description

This alarm is raised when the heart beating between mated PSU GWs fails for a
defined period of time. The alarm should clear automatically when the heart beating is
restored. In most cases, this alarm will be raised when a mated GICC is not installed
or not operational.
Resolve issue

Use the following table to resolve this issue:

No.
1

PRELIMINARY

Question
Is mated GICC Installed
and operational?

Are any Etherlink alarms

present on the RNC?

Answer

Check Steps

Install mated GICC, software

and initialize card. The alarm
should clear. If the alarm does
not clear, proceed to question
2.

Yes

Go to question 2.

Contact WTSE.

Yes

Clear the Etherlink alarm(s). If

the APS mated GICC Not
Available alarm is not cleared
after the Etherlink alarms
clear, contact WTSC for
support.

8-88

APS
Data Out Of Sync failure - major alarm
...................................................................................................................................................................................................................................
Description

This alarm is raised when data that is kept synchronized between two mated GICCs for
a particular 5EGW pair is out of sync. For example, both GICCs believe their 5EGW
in the mated pair is active. The alarm should clear automatically when the condition is
cleared. Rebooting the impacted GICC may be required to clear this alarm.

PRELIMINARY

Troubleshooting

Resolve issue

Use the following table to resolve this issue:

No.
1

Question

Answer

Check Steps

Is the working line in the

impacted 5EGW pair
capable of processing
traffic?

Contact WTSC for support.

Yes

Shutdown the GICC

experiencing the problem then
proceed to question 2.

Did the shutdown complete

successfully (GICC and
associated 5EGWs transition
to the LOCKED state)?

Yes

Reset the GICC then proceed

to question 3.

Contact WTSC for support.

Did the card initialize

successfully?

Yes

Unlock the card and proceed

to question 4.

Contact WTSC for support.

Yes

Ensure that the APS Data Out

of Sync Failure alarm cleared.
If it did not, contact WTSC for
support.

Contact WTSC for support.

Did the GICC and ATM

5EGWs unlock
successfully?

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
8-89
Issue 14, September 2009
See notice on first page

PRELIMINARY

Troubleshooting

APS
far end protection failure - major alarm
...................................................................................................................................................................................................................................
Description

This alarm is raised when the RNC receives a Signal Failure APS request in the K1
byte transmitted from the ATM switch for the protection line in a 5EGW mated pair.
The alarm will clear automatically when the Signal Failure is no longer received in the
K1 byte for the particular protection line.
Resolve issue

Use the following table to resolve this issue:

No.
1

PRELIMINARY

Question
Is there a signal failure
alarm raised on the ATM
switch for the protection
line?

Is the protection line

equipped on the ATM
switch for this 5EGW
physically connected to the
protection line (TPU shelf
2) in the RNC pair?

Answer

Check Steps

Yes

Resolve the problem at the

ATM switch. After the signal
failure at the ATM switch
clears, the RNC APS Far End
Protection Failure alarm should
clear. If it does not, proceed to
question 3.

Proceed to question 2.

Yes

Contact WTSC for support.

Connect the protection line on

the ATM switch to the
protection line on the RNC
(TPU shelf 2) and the working
line on the ATM switch to the
working line on the RNC
(TPU shelf 1). Ensure the
alarm clears. If it does not,
contact WTSC.

8-90

APS
mode mismatch - major alarm
...................................................................................................................................................................................................................................
Description

This alarm is raised when one of the following conditions is present:

1. The RNC is provisioned for the APS bidirectional mode and the respective OC3
mated pair on the ATM switch is provisioned for uni-directional.
2. The APS architecture mode for the associated OC3 mated pair on the ATM switch
is provisioned for an APS architecture other than 1+1.

PRELIMINARY

Troubleshooting

Resolve issue

Use the following table to resolve this issue:

No.
1

Question
Is there an AIS-L alarm
present on the protection
line of the impacted APS
pair?

Is the associated OC3 pair

on the ATM switch
provisioned for the APS
unidirectional mode?

Is the associated OC3 pair

on the ATM switch
provisioned for an APS
architecture other than 1+1?

Answer

Check Steps

Yes

Clear up the AISL alarm. If

the APS Mode Mismatch
alarm does not clear 10
seconds after the AISL clears,
proceed to question 2.

Proceed to question 2.

Yes

Provision the OC3 pair on the

ATM switch to operate in the
APS bidirectional mode. The
APS Mode Mismatch alarm on
the RNC should clear. If it
does not, proceed to question
3.

Proceed to question 3.

Yes

Provision the OC3 pair on the

ATM switch to operate in the
1+1 APS architecture. The
APS Mode Mismatch alarm on
the RNC should clear. If it
does not proceed to question
4.

Proceed to question 4.

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
8-91
Issue 14, September 2009
See notice on first page

PRELIMINARY
PRELIMINARY

Troubleshooting

APS mode mismatch - major alarm

No.
4

Question
Is the protection line
equipped on the ATM
switch for this 5EGW
physically connected to the
protection line (TPU shelf
2) in the RNC pair?

Answer

Check Steps

Yes

Contact WTSC for support.

Connect the protection line on

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

8-92

Unable
to protection switch due to AISL - major alarm
...................................................................................................................................................................................................................................
Description

This alarm is raised when the RNC is unable to protection switch after receiving an
AISL on the 5EGW in an APS mated pair due to the presence of a higher priority APS
request. This alarm will clear automatically when the AISL is cleared or when the line
with the AISL defect becomes the active APS line in its mated pair.

PRELIMINARY

Troubleshooting

Resolve issue

Use the following table to resolve this issue:

No.
1

Question
Is there an APS request
present with priority higher
than SF Low Priority?

Answer

Check Steps

Yes

This can be checked by

browsing to the TPU GUI APS
Status Page or executing the
GET:RNC a,GICC
b,5EGW,INFO CLI command.
No action is required. The
alarm will clear automatically
when the AISL clears or the
line receiving the AISL
becomes the active line in the
APS mated OC3 pair.

Contact WTSC for support.

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
8-93
Issue 14, September 2009
See notice on first page

PRELIMINARY

Troubleshooting

APS
protection byte failure - warning
...................................................................................................................................................................................................................................
Description

This warning is raised when an invalid APS request is received in the K1 byte at the
RNC for a particular 5EGW pair. The alarm will clear automatically when the invalid
APS request is replaced with a valid request in the received K1 byte for that 5EGW.
Note that the RNC does not support 1:N and revertive related APS requests. These
requests are considered invalid.
Resolve issue

Use the following table to resolve this issue:

No.
1

PRELIMINARY

Question

Answer

Check Steps

Is the protection line

equipped on the ATM
switch for this 5EGW
physically connected to
the protection line (TPU
shelf 2) in the RNC pair?

Yes

Proceed to Question 2.

Connect the protection line on

the ATM switch to the protection
line on the RNC (TPU shelf 2)
and the working line on the ATM
switch to the working line on the
RNC (TPU shelf 1). Ensure the
warning clears. If it does not,
proceed to question 2.

Is there an AIS-L alarm

present on the protection
line of the impacted APS
pair?

Yes

Clear up the AISL alarm. If the

APS Protection Byte Failure
warning does not clear 10
seconds after the AISL clears,
proceed to question 3.

Proceed to question 3.

Yes

Proceed to question 4.

Provision the respective OC3 pair

on the ATM switch for 1+1
Architecure. Ensure the warning
has cleared on the RNC. If it
does not clear, proceed to
question 4.

Is the far end OC3

equipped on the APS
switch provisioned for an
architecture other than
1+1 APS?

8-94

APS protection byte failure - warning

No.
4

Question
Is the far end OC3
equipped on the APS
switch provisioned for
non-revertive APS
processing.

Answer

Check Steps

Provision the respective OC3 pair

on the ATM switch for
non-revertive APS processing.
Ensure the warning has cleared
on the RNC. If it does not,
contact WTSC for assistance.

Yes

Contact WTSC for support.

PRELIMINARY

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
8-95
Issue 14, September 2009
See notice on first page

PRELIMINARY

Troubleshooting

PRELIMINARY

Troubleshooting

APS
channel mismatch - minor alarm
...................................................................................................................................................................................................................................
Description

This alarm occurs when the channel number in the K2 byte received by the RNC is
not equal to the channel number transmitted by the RNC in the K1 byte for a
particular 5EGW pair. This alarm should clear automatically when the channel number
in the K2 byte received by the RNC is equal to the channel number sent by the RNC
in the K1 byte.
Resolve issue

Use the following table to resolve this issue:

No.
1

PRELIMINARY

Question

Answer

Check Steps

Is the protection line

equipped on the ATM
switch for this 5EGW
physically connected to
the protection line (TPU
shelf 2) in the RNC
pair?

Yes

Proceed to question 2.

Connect the protection line on

the ATM switch to the protection
line on the RNC (TPU shelf 2)
and the working line on the ATM
switch to the working line on the
RNC (TPU shelf 1). Ensure the
alarm clears. If it does not,
proceed to question 2.

Is there an AIS-L alarm

present on the protection
line of the impacted APS
pair?

Yes

Clear up the AISL alarm. If the

APS Channel Mismatch alarm
does not clear 10 seconds after
the AISL clears, proceed to
question 3.

Proceed to question 3.

Yes

Clear the APS Mode Mismatch

alarm. If the APS Channel
Mismatch alarm does not clear,
contact WTSC for assistance.

Contact WTSC for support.

Does an APS Mode

Mismatch alarm exist for
this 5EGW?

8-96

PRELIMINARY

9R eplace components

To provide information that explains how to remove and replace faulty RNC-related
components when other attempts to restore the faulty components have failed.
Contents
Customer-replaceability versus field-replaceability

9-2

Hot-swappability versus cold swappability

9-3

RNC replaceable components

9-4

Replace 400S/410S server components

9-5

Replace TPU shelf components

9-6

Replace an SC-GICC or non-SC-GICC card

9-7
9-18

Replace a B-PCF

9-23

Replace a cPSB chassis fan tray

9-37

Replace cPSB chassis DC power supply

9-40

Replace an air filter in the cPSB chassis

9-47

Replace RNC cabinet components

9-52

Replace a cabinet alarm board

9-53

Replace a circuit breaker in the ECBU

9-56

Loopback Testing

9-59

Initiating PSU loopback test

9-60

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
9-1
Issue 14, September 2009
See notice on first page

PRELIMINARY

Replace a CICC card

PRELIMINARY

Replace components

Customer-replaceability
versus field-replaceability
...................................................................................................................................................................................................................................
Introduction

Each RNC-related component is either a Customer-Replaceable Unit (CRU) or a

Field-Replaceable Unit (FRU).
Customer-replaceable units

Customer-Replaceable Units (CRUs) are units that may be removed and replaced by
service-provider personnel without technical assistance or special training on the
removal and replacement procedures from Alcatel-Lucent.
Field-replaceable units

PRELIMINARY

Field-Replaceable Units (FRUs) are units that should be removed and replaced only
by:

Alcatel-Lucent personnel

service-provider personnel with technical assistance from Alcatel-Lucent

service-provider personnel whom Alcatel-Lucent has trained to remove and replace

the unit

9-2

Hot-swappability
versus cold swappability
...................................................................................................................................................................................................................................
Introduction

The components in an RNC cabinet are either hot-swappable or cold-swappable.

Hot-swappable

PRELIMINARY

Replace components

Components that are hot swappable can be installed or replaced while a TPU shelf or
RNC cabinet is powered up, without interrupting the operation of the RNC.
Cold-swappable

Components that are cold-swappable require that you halt (and, in some cases, also
power off) the equipment before installing or replacing the component. Note that you
must halt power only to the equipment where you would be installing or replacing the
component; any other equipment installed in the same chassis can remain running.

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
9-3
Issue 14, September 2009
See notice on first page

PRELIMINARY

Replace components

RNC
replaceable components
...................................................................................................................................................................................................................................
Introduction

The CRUs and FRUs for RNC are categorized in the following paragraphs.
CRU components

In the RNC cabinet, the following CRU components are hot-swappable:

TPU shelf components:

Shelf controller GICC card

Non-shelf controller GICC card

CICC card

Blade-PCF (B-PCF)

Fan drawer
cPSB Power Supply Units (PSUs)

cPSB air filter

RNC cabinet components:

ECBU circuit breakers

ECBU alarm board

FRU components

Field replaceable RNC components are listed as follows:

TPU shelf components are hot-swappable:

Ethernet Switch Card (ESC)

PRELIMINARY

TPU shelf Alarm card

RNC cabinet:
cPSB chassis

Enhanced Circuit Breaker Unit (ECBU)

Terminal Server

9-4

Replace
400S/410S server components
...................................................................................................................................................................................................................................
Introduction

The RNC-AP and OAM proxy AP functions are provided by means of 400S/410S
servers that are housed in an FMM-AP growth frame. Replacement procedures for
these components are provided in Chapter 8 (Replace Components) of 401-710-201.

PRELIMINARY

Replace components

Major topics

The major topics discussed are as follows:

Characteristics of components and the cfgadm utility

Replace server components

Replace frame components

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
9-5
Issue 14, September 2009
See notice on first page

PRELIMINARY

Replace components

Replace
TPU shelf components
...................................................................................................................................................................................................................................
Introduction

This section provides the following procedures for replacing TPU shelf components:
Replace an SC-GICC or non-SC-GICC card (p. 9-7)
Replace a CICC card (p. 9-18)
Replace a B-PCF (p. 9-23)
Replace a cPSB chassis fan tray (p. 9-37)
Replace cPSB chassis DC power supply (p. 9-40)

PRELIMINARY

Replace an air filter in the cPSB chassis (p. 9-47)

9-6

Replace
an SC-GICC or non-SC-GICC card
...................................................................................................................................................................................................................................
Purpose

Perform this procedure to replace a faulty SC-GICC or non-SC-GICC card or to

upgrade from a non-optical ethernet GICC to an optical ethernet GICC.

PRELIMINARY

Replace components

Important! This procedure is service impacting and should be done only in a

maintenance window.
Reason to perform

Troubleshoooting indicates that only card replacement will correct a known problem.
Note that with APS invoked an automatic switch to the protection line may have
already occurred.
Hot-swappability

A GICC card can be replaced without the need for powering down the TPU shelf.
Important! GICC pairs should be equipped with the same hardware version. A
mismatch in hardware versions. For example, non-optical ethernet GICC (1.0) card
paired with an optical ethernet GICC (1.1) card is supported while GICC hardware
is being upgraded for a particular GICC pair. However, non-optical ethernet GICC
(1.0) card pairs can be equipped in the same RNC with optical ethernet GICC (1.1)
card pairs.
SC-GICC replacement

The SC-GICC is provided in pairs for reliability. It is assumed that if you are replacing
a faulty SC-GICC, the other SC-GICC is still functioning normally and controlling
both shelves.
Important! Never under any circumstance shutdown both SC-GICCs in an active
RNC!
Duration

This procedure typically takes 30 minutes to perform.

Required conditions

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
9-7
Issue 14, September 2009
See notice on first page

PRELIMINARY

One or more OC3 ports have stopped functioning normally and it is determined that
they cannot be fixed without card replacement or an upgrade from a non-optical
ethernet GICC to an optical ethernet GICC is required.

PRELIMINARY

Replace components

Replace an SC-GICC or non-SC-GICC card

Required tools

This procedure requires the following tools:

A No. 2 Phillips screwdriver

an antistatic wrist strap

an electrostatic discharge mat

TPU GUI

Required materials

This procedure requires a replacement GICC card of the same type.

Important! You should never replace a non-optical ethernet GICC card with an
optical ethernet GICC card, or vice versa.
Updating external IP address

If the address of the router hosting the optical GigE port(s) connected to the newly
inserted GICC has changed, you will need to access the TPU GUI to change the
heartbeat target IP address for the GigE port(s) on the GICC. See Step 28 and Step 29.
Procedure

To replace a GICC card, perform the following:

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

Obtain access to the TPU CLI. See Accessing TPU CLI (p. 6-17).
...................................................................................................................................................................................................

Verify the type of GICC to be replaced by entering the following:

GET:RNC a, TPU b, STATE

Where:
a = RNC number (1-15)
b = TPU shelf number (1-2) that has the GICC to replace.

Result: An output similar to the following will occur:

PRELIMINARY

M 44 GET:RNC 10,TPU 1,STATE! COMPLETE

Resource Admin Oper Usage
-----------------------------------------------ACS 1,AC 1 UNLOCKED ENABLED IDLE

9-8

Replace an SC-GICC or non-SC-GICC card

ACS 1,AC 2 UNLOCKED ENABLED ACTIVE

ESC 2 UNLOCKED ENABLED ACTIVE
GICC 3,A10A11GW UNLOCKED ENABLED IDLE
GICC 3,A8A9GW UNLOCKED ENABLED IDLE
GICC 3,Proc 0 UNLOCKED ENABLED ACTIVE

PRELIMINARY

Replace components

GICC 3,ATM 1 UNLOCKED ENABLED IDLE

GICC 3,ATM 2 UNLOCKED ENABLED IDLE
GICC 4,IPBTSGW UNLOCKED ENABLED IDLE
GICC 4,Proc 0 UNLOCKED ENABLED ACTIVE
BPCF 5 UNLOCKED DISABLED IDLE
CICC 11,Proc 0 UNLOCKED ENABLED ACTIVE
CICC 11,Proc 1 UNLOCKED ENABLED ACTIVE
CICC 11,Proc 2 UNLOCKED ENABLED ACTIVE
CICC 12,Proc 0 UNLOCKED ENABLED ACTIVE
CICC 12,Proc 1 UNLOCKED ENABLED ACTIVE
CICC 12,Proc 2 UNLOCKED ENABLED ACTIVE
CICC 13,Proc 0 UNLOCKED ENABLED ACTIVE
CICC 13,Proc 1 UNLOCKED ENABLED ACTIVE
CICC 13,Proc 2 UNLOCKED ENABLED ACTIVE
GICC 19,IPSHOGW UNLOCKED ENABLED IDLE
GICC 19,Proc 0 UNLOCKED ENABLED ACTIVE
GICC 20,IPBTSGW UNLOCKED ENABLED ACTIVE
GICC 20,Proc 0 UNLOCKED ENABLED ACTIVE

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

Do one of the following:

If this is an SC-GICC (slot 3), go to Step 4.

If this is an IPSHO GICC, go to Step 10.
If this is an IPBH GICC, go to Step 13.

Do one of the following:

If APS is in effect, go to Step 5.

If APS is not in effect, or in the case of an SC-GICC, go to Step 15.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
9-9
Issue 14, September 2009
See notice on first page

PRELIMINARY

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

PRELIMINARY

Replace components

Replace an SC-GICC or non-SC-GICC card

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

Verify the status of the GICC that you intend to replace by entering the following:
GET:RNC a, TPU b, GICC c, state

Where:
a = RNC number (1-15)
b = TPU shelf number (1-2)
c = GICC slot number (3, 4, 19, 20)

Result: An output similar to the following will occur:

M 57 GET:RNC 1,TPU 1,GICC 3,STATE! COMPLETE
Resource Admin Oper Usage
-----------------------------------------------GICC 3,Proc 0 UNLOCKED ENABLED ACTIVE
GICC 3,ATM 2 UNLOCKED ENABLED ACTIVE
GICC 3,ATM 1 UNLOCKED ENABLED ACTIVE
GICC 3,A8A9GW UNLOCKED ENABLED ACTIVE
GICC 3,A10A11GW UNLOCKED ENABLED ACTIVE

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

Do one of the following:

If the GICC is STANDBY, go to Step 15.

If the A8A9GW is ACTIVE, go to Step 7.

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

Enter the following to make the A8A9GW STANDBY:

SWITCH:RNC #,A8A9

Where: a = RNC number (1-15).

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

PRELIMINARY

If the A10A11GW is ACTIVE, type the following to make it STANDBY:

SWITCH:RNC #,A10A11

Where: a = RNC number (1-15).

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

Find out which ATM is ACTIVE for APS by entering the following:
GET:RNC a,GICC 3,5EGW,INFO

9-10

Replace an SC-GICC or non-SC-GICC card

Where: a = RNC number (1-15).

If the ATM for the GICC to be replaced is ACTIVE, enter the following to make it
STANDBY:
SWITCH:TOMATE, RNC a, TPU b, GICC c, ATM d

Where:

PRELIMINARY

Replace components

a = RNC number (1-15)

b = TPU shelf number (1-2)
c = GICC slot number (3)
d - ACTIVE ATM to be switched (1-2)

Go to Step 15.
...................................................................................................................................................................................................

Verify the status of the IPSHO GICC that you intend to replace by entering the
following:
GET:RNC a, TPU b, GICC c, state

Where:
a = RNC number (1-15)
b = TPU shelf number (1-2)
c = GICC slot number (4,19,20)

Result: An output similar to the following will occur:

M 54 GET:RNC 10,TPU 2,GICC 19,STATE! COMPLETE
Resource Admin Oper Usage
-----------------------------------------------GICC 19,Proc 0 UNLOCKED ENABLED ACTIVE
GICC 19,IPSHOGW UNLOCKED ENABLED ACTIVE

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

Do one of the following:

If the IPSHOGW service is STANDBY, go to Step 15.

If the IPSHOWGW is ACTIVE, go to Step 12.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
9-11
Issue 14, September 2009
See notice on first page

PRELIMINARY

Replace components

Replace an SC-GICC or non-SC-GICC card

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

Enter the following to make the IPSHOWGW STANDBY:

SWITCH:RNC a, IPSHO

Where: a = RNC number (1-15).

Verify the status of the IPBH GICC that you intend to replace by entering the
following:
GET:RNC a, TPU b, GICC c, state

Where:
a = RNC number (1-15)
b = TPU shelf number (1-2)
c = GICC slot number (4,19,20)

Result: An output similar to the following will occur:

M 43 GET:RNC 10,TPU 1,GICC 20,STATE! COMPLETE
Resource Admin Oper Usage
-----------------------------------------------GICC 20,Proc 0 UNLOCKED ENABLED ACTIVE
GICC 20,IPBTSGW UNLOCKED ENABLED ACTIVE

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

Do one of the following:

If the IPBTSGW service is STANDBY, go to Step 15.

If the IPBTSGW is ACTIVE, enter the following to make it STANDBY:

SWITCH:RNC a, BHS b

Where: a = RNC number (1-15) and b = BHS number served by the IPBH GICC that
is being replaced.

PRELIMINARY

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

Obtain access to the TPU GUI either by:

Direct access method. Refer to Accessing TPU GUI (p. 6-6).

EMS. Refer to Logging on to Element Management System (EMS) (p. 6-5).

9-12

Replace an SC-GICC or non-SC-GICC card

Choose the GICC in the TPU shelf that you wish to shutdown,, and choose Shutdown
via the Commands column.
Result The following will occur:

Shutdown Accepted will initially appear in the Command Status column.

After two minutes, the GICC will transition to:

Admin State

Oper State

Usage State

Locked

Disabled

Idle

See Figure 5-3,

Administrative state
(p. 5-7) for capsule
correlation.

See Figure 5-1,

Operational state (p. 5-5)
for capsule correlation.

PRELIMINARY

Replace components

See Figure 5-2, Usage

state (p. 5-6) for capsule
correlation.

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

Refresh the browser (if necessary) to verify the transition.

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

Attach an antistatic wrist strap.

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

CAUTION
Laser hazard
Possible eye injury.
Never look directly into the open end of a functioning optic cable, even if you are
certain that it is not currently functioning, or even connected at the other end.
Although the laser beams strength is insufficient to harm exposed skin, or damage
combustible maerials, eye damage can occur if you stare directly into the beam for a
prolonged period.
Remove the serial port console connector.
...................................................................................................................................................................................................

Important! If the new GICC to be inserted is a different hardware version than the
GICC being replaced, please ensure the proper switch/router ports are configured
and the correct type of cabling is run to the GICC area.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
9-13
Issue 14, September 2009
See notice on first page

PRELIMINARY

Before disconnecting the GIGE, OC3 and (if applicable) serial port terminal server
connector connections, label them, if you are are replacing a GICC with a GICC of the
same hardware versio. That way they can be properly reinserted in the replacement
card.

PRELIMINARY

Replace components

Replace an SC-GICC or non-SC-GICC card

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

Disconnect the cable connections. (You can also wait to do this until after the GICC is
removed.)
...................................................................................................................................................................................................

Loosen the GICCs upper and lower retention retention screws (see Figure 9-1,
Loosen GICC retention screws (p. 9-14)).
Figure 9-1 Loosen GICC retention screws

PRELIMINARY

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

Important! Do not fully open the ejector at this point because that action levers the
board out of the enclosure, and the midplane connection will be broken before it
has shut down properly.

9-14

Replace an SC-GICC or non-SC-GICC card

Signal the GICC that it is about to be removed by (with equal pressure) partially
unlatching the top and bottom ejector levers (Figure 9-2, Partially eject GICC
(p. 9-15)).
Figure 9-2 Partially eject GICC

PRELIMINARY

Replace components

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

Wait for the blue hot swap LED to light. (This may take several seconds depending on
the amount of data that must be synchronized.)
Result The blue hot swap LED lights.

With equal pressure, press upward and downward on the two ejector levers on the card
to fully unseat the card from the chassis.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
9-15
Issue 14, September 2009
See notice on first page

PRELIMINARY

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

PRELIMINARY

Replace components

Replace an SC-GICC or non-SC-GICC card

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

Slide the card out and place it on the electrostatic discharge mat.
...................................................................................................................................................................................................

Keeping the replacement GICC card vertical, slide the card firmly into the slot between
the two guides and lock the upper and lower levers.
Result The following occurs:

The Power/Fault LED lights green.

The new card begins to initialize.

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

Connect the OC3 and GigE cables. Note that Optical GigE switch/router ports should
be configured as follows:

auto-negotiation should be disabled

flow control should be disabled

full duplex should be configured

data rate should be set to 1G.

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

If the address of the router hosting the optical GigE port(s) connected to the newly
inserted GICC has changed, access the Update External IP Address link on the RNC
Configuration Data page on the TPU GUI.
...................................................................................................................................................................................................

Change the heartbeat target IP address for the one or two equipped GigE ports on the
GICC to the routers IP address, and submit the changes.
...................................................................................................................................................................................................

Replace the GICC retentions crews.

Important! The following Step 31 is a special step necessary for an SC-GICC
only, because non-SC-GICCs are downloaded by the SC-GICCs automatically.
...................................................................................................................................................................................................

At the TPU GUI, access the Installation & Software Options Page and perform a
software update for the SC-GICC.

PRELIMINARY

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

For a non-SC-GICC, perform a reset via the Commands column of the TPU-GUI
TPU Network Elements page.

9-16

Replace an SC-GICC or non-SC-GICC card

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

Determine the state of the newly-replaced GICC via the TPU-GUI TPU Network
Elements page.
Result The newly-installed GICC should be in the following state:
Admin State

Oper State

Usage State

Locked

Enabled

Idle

See Figure 5-3,

Administrative state
(p. 5-7) for capsule
correlation.

See Figure 5-1,

Operational state (p. 5-5)
for capsule correlation.

PRELIMINARY

Replace components

See Figure 5-2, Usage

state (p. 5-6) for capsule
correlation.

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

Perform an unlock via the Commands column of TPU Network Elements page.
Result The GICC card is now in-service.
...................................................................................................................................................................................................

Verify GICC OC3 ATM integrity by initiating an ATM-to-PSU loopback test. See
Initiating PSU loopback test (p. 9-60).
END OF STEPS
...................................................................................................................................................................................................

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
9-17
Issue 14, September 2009
See notice on first page

PRELIMINARY

Replace components

Replace
a CICC card
...................................................................................................................................................................................................................................
Purpose

Perform this procedure to replace a faulty CICC card.

Reason to perform

Troubleshoooting indicates that only card replacement will correct a known problem.
Hot-swappability

A CICC card can be replaced without the need for powering down the TPU shelf.
Duration

This procedure typically takes 15 minutes to perform.

Required conditions

One or more components on the card have stopped functioning normally and it is
determined that they cannot be fixed without card replacement.
Required tools

This procedure requires the following tools:

a No.2 Phillips screwdriver

an antistatic wrist strap

an electrostatic discharge mat

TPU CLI or TPU-GUI. The TPU-GUI can also be used to enter the CLI
commands.

Required materials

This procedure requires a replacement CICC card.

Procedure

To replace a CICC card, perform the following:

PRELIMINARY

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

Verify which CICC card you are going to pull.

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

Obtain access to the TPU CLI, see also Accessing TPU CLI (p. 6-17).

9-18

Replace a CICC card

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

Type the following command:

SHUTDOWN:RNC a, TPU b, CICC c <ENTER>

Important! If a CICC is removed without first being shutdown/locked, call setup

failures may occur.
where:

PRELIMINARY

Replace components

a = RNC number 1-15

b = TPU shelf number 1-2
c = CICC slot number (7 through 16)
Result The following response is returned:
SHUTDOWN:RNC a, TPU b, CICC c ISSUED
...................................................................................................................................................................................................

Wait two minutes and then periodically use the GET:RNC-TPU-STATE command to
determine if the CICC card has transitioned to the locked state.When it does, proceed
to Step 17. See also the following example:

1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
REPT: RNC 14, TPU 1, CICC 3, Proc 1, STATE CHANGE
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
RNC 14, TPU 1, CICC 3, Proc 1 changed state
1234567890123456789012345678901212345678901234567890123456789
from UNLOCKED, DISABLED, IDLE
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
to LOCKED, DISABLED, IDLE
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
...................................................................................................................................................................................................

Attach an antistatic wrist strap.

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

If applicable, disconnect any of the 3 console ports or the Ethernet connection,

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

Loosen the CICCs upper and lower retention retention screws (see Figure 9-3,
Loosen CICC retention screws (p. 9-20)).

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
9-19
Issue 14, September 2009
See notice on first page

PRELIMINARY

Replace components

Replace a CICC card

Figure 9-3 Loosen CICC retention screws

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

PRELIMINARY

Signal the CICC that it is about to be removed by (with equal pressure) partially
unlatching the top and bottom ejector levers (Figure 9-4, Partially eject CICC
(p. 9-21)).

9-20

Replace a CICC card

Figure 9-4 Partially eject CICC

PRELIMINARY

Replace components

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

Wait for the blue hot swap LED to light. (This may take several seconds depending on
the amount of data that must be synchronized.)
Result The blue hot swap LED lights.
...................................................................................................................................................................................................

With equal pressure, press upward and downward on the two ejection levers on the
card to fully unseat the card from the chassis.

Slide the card out and place it on the electrostatic discharge mat.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
9-21
Issue 14, September 2009
See notice on first page

PRELIMINARY

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

PRELIMINARY

Replace components

Replace a CICC card

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

Keeping the replacement CICC card vertical, slide the card firmly into the slot between
the two guides and lock the upper and lower levers.
Result As soon as the new card is inserted, it will try to reboot.
...................................................................................................................................................................................................

If applicable, reconnect any of the 3 console ports or the Ethernet connection,

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

Use the GET:RNC-TPU-STATE command to determine if the CICCs CICC

processors have transitioned to, Enabled.
...................................................................................................................................................................................................

Type the following command:

UNLOCK:RNC a, TPU b, CICC c <ENTER>

where:
a = RNC number 1-15
b = TPU shelf number 1-2
c = CICC slot number (7 through 16)
Result The following response is returned:
UNLOCK:RNC a, TPU b, CICC c ISSUED

The CICC card is now in-service.

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

Verify that the replacement card is operating properly. If it is not contact

Alcatel-Lucent.
END OF STEPS

PRELIMINARY

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

9-22

Replace
a B-PCF
...................................................................................................................................................................................................................................
Purpose

Use this procedure to replace a B-PCF in a TPU shelf.

Reason to perform

PRELIMINARY

Replace components

You may need to replace a B-PCF if you cannot access the blade through the
TPU-GUI or TPU-CLI, or if the LED on the B-PCF is yellow, indicating the presence
of a card alarm.
A repetitive stem message, for example, In determinate PCF in recovery, for the
same B-PCF may also indicate a problem with the blade.
See Chapter 8, Troubleshooting for further information about diagnosing problems
on the B-PCF.
Hot-swappability

A B-PCF card can be replaced without the need for powering down the TPU shelf.
Duration

It will take from 1.5 hours to 3.5 hours to complete the replacement process.
Frequency

Replacement of a Solaris blade occurs rarely.

Required tools

This procedure requires the following tools:

a No.2 Phillips screwdriver
an antistatic wrist strap

an electrostatic discharge mat

TPU-GUI
TPU-CLI

NTS console connection.

AP UNIX access on either one of the RNC APs. There are two methods for access:
Access the OMP Technicians menu on an OMP workstation. Select
FLEXENT(TM) AP Access at the OMP Technicians menu. Select the Frame #
and then the AP # at the Frame Access menu.

You can connect to the RNC AP using the LMT.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
9-23
Issue 14, September 2009
See notice on first page

PRELIMINARY

Replace components

Replace a B-PCF

Required materials

This procedure requires a Solaris blade for replacement that has the most recent
firmware and FMS software installed.
Required information

You must know:

What release of the software is currently running on your system.

What current AP bundle is running for B-PCFs

The BPCF root login with the factory-configured root password. Note that this
password is not currently customer-configurable, and may be amended in a future
Release.

Suspend B-PCF disk activity

CAUTION
ESD hazard
Destruction of components by electrostaic discharge
Electronic components can be destroyed by electrostatic discharge. Use an anti-static
wrist strap when working with electrolyze components. Alaways observe the general
ESD instructions.
To prevent damage to the B-PCF disk, it is necessary to suspend B-PCF disk activity
before a B-PCF blade is removed. Suspending disk activity is included as part of the
following procedure. See Step 7.
Procedure

To replace a B-PCF card, perform the following:

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

Obtain access to TPU-GUI either by:

Direct access method. See also Accessing TPU GUI (p. 6-6).
EMS. See also Logging on to Element Management System (EMS) (p. 6-5).

PRELIMINARY

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

If using EMS, at the OMP Web page you need to select 1X RNC TPU Web to
navigate to the 1X RNC TPU Web page. If using the direct access method, the same
will result. See the following example screen.

9-24

Replace a B-PCF

Figure 9-5 1X RNC TPU Web page

PRELIMINARY

Replace components

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

On the 1X RNC TPU Web page select Network Elements.

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
9-25
Issue 14, September 2009
See notice on first page

PRELIMINARY

Replace components

Replace a B-PCF

Result The GUI navigates to the Network Elements web page (see example of

Figure 9-6, TPU page (filter all) (p. 9-26)).

Figure 9-6 TPU page (filter all)

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

PRELIMINARY

Use the Filter: box to filter on only the BPCFs.

9-26

Replace a B-PCF

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

Note the state (Admin, Oper, and Usage) of the B-PCF in question. See Table 9-1,
B-PCF states (p. 9-27) for reference.
Table 9-1
Admin State

B-PCF states
TPU GUI
Capsule
Indicator

Operation
State

TPU GUI
Capsule
Indicator

Usage State

unlocked

enabled

active

unlocked

enabled

idle

unlocked

enabled

busy

shutting
down

enabled

active

locked

disabled

unknown

TPU GUI
Capsule
Indicator

PRELIMINARY

Replace components

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

If the Admin State does not already indicate locked, initiate a shutdown on the B-PCF
in question, by using the pull-down menu, and clicking on Submit (see example of
Figure 9-7, Initiate shutdown (p. 9-28)).

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
9-27
Issue 14, September 2009
See notice on first page

PRELIMINARY

Replace components

Replace a B-PCF

Figure 9-7 Initiate shutdown

Result Once a shutdown is initiated and accepted, all current activity will drain by
attrition until the shutdown completes. Indicated by the locked Admin state capsule
and idle Usage State capsule of the B-PCF. See also Table 9-1, B-PCF states

(p. 9-27).
Note that you may do periodic refreshes of the web browser to see if the state
change has already occurred.
Figure 9-8 Shutdown complete

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

At the TPU CLI, suspend B-PCF disk activity by executing the following command:
HALT:RNC a, TPU b, BPCF c <CR>

PRELIMINARY

where:
a = RNC number (1-15)
b = TPU shelf number (1 or 2)
c = BPCF card slot number (5,6,17, or 18)

9-28

Replace a B-PCF

Result The following occurs:

B-PCF disk activity ceases.

The blue Hot Swap LED lights

The system returns a status message (ISSUED) to indicate that the B-PCF hard
disk has successfully been halted.

PRELIMINARY

Replace components

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

Attach an antistatic wrist strap.

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

Using the No2. Phillips screw driver, unscrew the retention screws that fasten the blade
to the TPU shelf.
...................................................................................................................................................................................................

With both hands, open the card ejectors, then rotate the handles outward until the blade
disengages from the midplane.
...................................................................................................................................................................................................

Slide the blade evenly out of the slot enclosure, and set it on the ESD mat.
...................................................................................................................................................................................................

Retrieve the replacement blade.

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

Slide the replacement board into the appropriate slot, and align the top and bottom
mounting rails. Then move the blade toward the backplane while gently pushing the
board handles inward (this may require both hands).
Result The following occurs:

The blue Hot Swap LED and green Ready LED light.

The new B-PCF begins to initialize.

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

As the B-PCF initializes, install two screws through the top and bottom of the front
connector plate to secure the board.
...................................................................................................................................................................................................

After the B-PCF has initialized, obtain access to the B-PCF through the NTS console
connection. See also Required tools (p. 9-23) for connection information.

From the OMP Shell start a SSH session through the NTS to the B-PCF console by
entering the following command:
SSH NTS_IP_address port_number

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
9-29
Issue 14, September 2009
See notice on first page

PRELIMINARY

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

PRELIMINARY

Replace components

Replace a B-PCF

where:
NTS_IP_address is the customer provided or the factory default NTS IP address.
port_number is the port number for the B-PCF shown in Table 9-2, B-PCF port

numbers (p. 9-30).

Table 9-2

B-PCF port numbers

For...

Enter Port Number...

B-PCF in Upper shelf slot 05

3600

B-PCF in Lower shelf slot 05

5500

B-PCF in Upper shelf slot 18

2300

B-PCF in Lower shelf slot 18

4300

B-PCF in Upper shelf slot 06

2400

B-PCF in Lower shelf slot 06

4400

B-PCF in Upper shelf slot 17

2300

B-PCF in Lower shelf slot 17

4300

Notes:

Both slot 17 and slot 18 (upper and lower shelves) are provided with one movable cable
that is used to make the serial connection. When you need to make a serial connection to
B-PCFs installed in these slots, move the cable to the appropriate B-PCF card position,
and plug in the connector.

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

Press the Enter key to get the login prompt.

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

Login to the B-PCF console as root. See the following example:

pcfb1 console login: root
Password: (not displayed when entered)
...................................................................................................................................................................................................

PRELIMINARY

Configure DHCP and the host name on the B-PCF by entering the following
commands from the B-PCF:
cd /flx/FMSadmin/current/bin/
./flxdhcpcfg

9-30

Replace a B-PCF

Result A script is outputted, such as shown in the following example:

PRELIMINARY

Replace components

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

Modify the .rhosts file on the B-PCF by enteing the following commands on the
B-PCF:
cd /
vi .rhosts
...................................................................................................................................................................................................

Enter the following:

cat /etc/TIMEZONE

Verify that the TZ is set correct for this location. If not, then open the /etc/TIMEZONE
file and change the TZ to the correct time zone. Save and close the file.
...................................................................................................................................................................................................

Enter the following:

Verify that the time and date is correct. If not, use the date command to correct the
time and date. Use the following syntax:
date mmddHHMM[[cc]yy][.SS]

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
9-31
Issue 14, September 2009
See notice on first page

PRELIMINARY

date

PRELIMINARY

Replace components

Replace a B-PCF

Where:
mm = 2-digit month
dd = 2-digit day
HH = 2-digit hour using 24-hour clock
MM = 2-digit minutes
cc = first 2 digits of the year
yy = last 2 digits of the year
SS = 2-digit seconds

NOTE: Use leading zero where necessary (for example, mm for February = 02).
...................................................................................................................................................................................................

In vi insert the IP addresses of the primary and secondary RNC AP on the AP Dual
Rail LAN, as follows:
172.Y.128.sp
172.Y.128.ss

where:
Y is the second octet of the RNC APs IP address on AP Dual Rail LAN network. The

value ranges from 16 to 31.

sp is the slot the Primary RNC AP is installed in the MM-AP growth frame.
ss is the slot the Secondary RNC AP is installed in the MM-AP growth frame.
...................................................................................................................................................................................................

Save and exit vi after making the updates by entering the following command:
wq!
...................................................................................................................................................................................................

Reboot the B-PCF by entering the following command on the B-PCF:

sync;/etc/reboot

Result The B-PCF reboots.

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

PRELIMINARY

After the Operating System (OS) boot sequence is complete on the B-PCF, log back
into the B-PCF.
...................................................................................................................................................................................................

Verify that the B-PCF has been assigned an IP address by the GICC. Enter the
following command:
ifconfig a

9-32

Replace a B-PCF

Result The SC-GICC assigns the B-PCFs dmfe0 interface an IP address in the

subnet (for upper TPU shelf B-PCFs) or subnet (for lower TPU shelf B-PCFs). See
the following output example:

PRELIMINARY

Replace components

index 2

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

Verify that the FMS golden image package for the B-PCF is greater then 9.1.5, by
executing the following command:
# flxpkginfo -a |grep FMSgolden-1

Result If the output indicates 9.1.5 as indicated in the example output that follows,

or greater, then proceed to Step 29. If the output indicates earlier then 9.1.5,
proceed to Step 30.
FMSgolden-1 9.1.5 FMS Golden Image Identification (current,committed)
...................................................................................................................................................................................................

Execute the following three UNIX copy (cp) commands:

1. cp -p /etc/lvm/mddb.cf /secroot/etc/lvm
2. cp -p /etc/lvm/md.cf /secroot/etc/lvm
3. cp -p /kernel/drv/md.conf /secroot/kernel/drv
...................................................................................................................................................................................................

Log out of the B-PCF by entering the following command:

exit
...................................................................................................................................................................................................

Terminate the Console connection to the B-PCF by entering the following commands:
ctrl-]
quit
...................................................................................................................................................................................................

Access AP UNIX on either one of the RNC APs. See also Required tools (p. 9-23)
for connection information.

Login to the RNC AP as root,

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

Access TPU CLI from the RNC AP by entering the following command:
TPUCLI<CR>

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
9-33
Issue 14, September 2009
See notice on first page

PRELIMINARY

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

PRELIMINARY

Replace components

Replace a B-PCF

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

Obtain the name of the latest software version for the B-PCF by entering the following
TPU CLI command:
get, rnc f, install, version<CR>

where: f = RNC Frame number (1-15).

Result The B-PCFs software version is displayed.
...................................................................................................................................................................................................

Transfer the B-PCF bundle file from the RNC AP to the B-PCFs /var/flx/bun directory
by entering the following TPU CLI command:
install:rnc f,tpu s, bpcf b,version Version_String<CR>

where:
f = RNC Frame number (1-15)
s = TPU Shelf number (1-2)
b = BPCF Slot number (5, 6, 17, 18)
Version_String = B-PCF software version. For example:BPCF23L20.0

Important! The system will issue a reminder to shutdown the B-PCF. Ignore this
message, the B-PCF slot was previously shutdown in Step 6.
Result The B-PCF bundle is transferred from the RNC-AP to the B-PCF.

The bundle activation (Step 37) takes about 2 hours to complete. The system will
reboot several times (up to 3 times) if it needs to perform firmware updates.
...................................................................................................................................................................................................

Execute and activate the bundle by entering the following command:

bpcf_update -rnc f -tpu s -bpcf b -activate

where:
f = RNC Frame number (1-15)
s = TPU Shelf number (1-2)
b = BPCF Slot number (5, 6, 17, 18)

PRELIMINARY

Result The script will output progress messages and generate error messages for

any failure cases. The script also saves the output to a log file for future/further
debugging. The log file is named rncadmin.log, and it is stored on the active
RNC-AP under the /$CDMA_OAM_ROOT/log directory.
...................................................................................................................................................................................................

Wait for the Script to complete and display a success message (after the B-PCF
reboots).

9-34

Replace a B-PCF

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

Logout of the RNC-AP by entering the following command:

Login to the OAM Proxy AP as root.

PRELIMINARY

Replace components

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

Access TPU CLI from the OAM Proxy AP by entering the following command:
TPUCLI<CR>
...................................................................................................................................................................................................

Verify that the B-PCF is unlocked by entering the following TPU-CLI command:
get: rnc f, tpu s, bpcf b, state

where:
f = RNC Frame number (1-15)
s = TPU Shelf number (1-2)
b = BPCF Slot number (5, 6, 17, 18)

Result An output similar to the following will occur:

1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
command_echo! COMPLETED
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
Resource Admin Oper Usage
1234567890123456789012345678901212345678901234567890123456789
---------------------------------- -------------1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
BPCF 5 UNLOCKED ENABLED ACTIVE
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
...................................................................................................................................................................................................

If the B-PCF is reported to be in a locked state, then enter the following TPU-CLI
command
unlock: rnc f, tpu s, bpcf b

where:
f = RNC Frame number (1-15)
s = TPU Shelf number (1-2)
b = BPCF Slot number (5, 6, 17, 18)

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
9-35
Issue 14, September 2009
See notice on first page

PRELIMINARY

Replace components

Replace a B-PCF

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

Run the MM security audit:

1. First, verify if csm-3 (that is, security feature) is on or off . This can be done from
the secctrl form in apxrcv on the OMP.
2. On the active RNCM-AP (use TICLI OP:AP command to determine this), run the
$CDMA_OAM_ROOT/bin/1XRNC_BootStrap script.
3. If csm-3 is on, it is not mandatory but recommended that the user run the following
commands for the B-PCF being replaced:
mmkeyrefresh s 1xrnc.<rnc num> -e bpcf.<tpu num><bpcf slot> H
mmsecaudit s 1xrnc.<rnc num> -e bpcf.<tpu num>/<bpcf slot> t c

where <rnc num> is the RNC number, <tpu num> is the TPU number, and <bpcf
slot> is the B-PCF slot number.
...................................................................................................................................................................................................

The timezone must be reset. Refer to Time zone verification and update (p. C-5).
...................................................................................................................................................................................................

The system date must be reset.

END OF STEPS

PRELIMINARY

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

9-36

Replace
a cPSB chassis fan tray
...................................................................................................................................................................................................................................
Purpose

Perform this procedure to replace a faulty cPSB chassis fan tray.

Reason to perform

PRELIMINARY

Replace components

A fan drawer failure alarm has been outputted, and the fan drawer LED has switched
from green to amber indicating that the fan drawer has ceased to function on its own.
Important! A non functioning fan drawer can remain in the chassis for a prolonged
period because the remaining fan drawers will step up their operation, and
essentially provide enough air flow to keep the three fan units in the defective fan
drawer spinning.
Hot-swappability

A fan tray can be replaced without the need for powering down the TPU shelf.
Duration

This procedure typically takes 5 minutes to perform.

Required tools

This procedure requires the following tools:

an antistatic wrist strap

an electrostatic discharge mat

a flat head screwdriver

Required materials

This procedure requires a replacement fan drawer. The replacement fan drawer should
plugged into service as soon as possible after a defective drawer is removed.
Procedure

To replace a fan drawer, perform the following:

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

Attach an antistatic wrist strap.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
9-37
Issue 14, September 2009
See notice on first page

PRELIMINARY

Replace components

Replace a cPSB chassis fan tray

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

Pull (by hand) the securing pins on each side of the FMU to loosen it from its secure
position on the position brackets, then move the FMS to the down position.
Figure 9-9 FMU in lowered position

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

Use a flat head screwdriver to remove the recessed screw on the front of the fan
drawer panel that holds the fan drawer securely in the chassis. Remove fan drawer
retention screw.
...................................................................................................................................................................................................

Tug on the handle of the fan drawer, to release it from its backplane connector, and
using both hands slide it out of the chassis. (See Figure 9-10, Remove fan drawer
(p. 9-38).)

PRELIMINARY

Figure 9-10 Remove fan drawer

9-38

Replace a cPSB chassis fan tray

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

Position the replacement fan drawer in the vacated fan drawer area, and slide it back
into the chassis until it engages the backplane connector.
Result The following occurs:

Fan drawer LED blinks, and then lights green.

The three fan units in the fan drawer begin to operate.

PRELIMINARY

Replace components

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

Replace the recessed screw on the front of the fan drawer panel that holds the fan
drawer securely in the chassis.
...................................................................................................................................................................................................

Using both hands move the FMU back to the up position and insert the securing pins
into the bracket.
END OF STEPS
...................................................................................................................................................................................................

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
9-39
Issue 14, September 2009
See notice on first page

PRELIMINARY

Replace components

Replace
cPSB chassis DC power supply
...................................................................................................................................................................................................................................
Purpose

Perform this procedure to replace a faulty cPSB chassis DC power supply.

Reason to perform

Troubleshoooting indicates that only power supply replacement will correct a known
problem.
Power supplies

The cPSB chassis accommodates up to eight modular power supplies. The power
supplies are load sharing, and plug directly into the power trays.
Important! Air management boards must populate any empty power supply slots in
order to maintain optimum chassis cooling.
Location in chassis

The power supplies are located at the bottom of the chassis (Figure 9-12, cPSB
chassis DC power supplies (cutout view) (p. 9-41)) in two power supply trays,
covered by an air intake grill and air filter. The air intake grill and air filter must be
temporarily removed when a power supply needs to be replaced.

PRELIMINARY

Figure 9-11 Front view of air filter and grill

9-40

Replace cPSB chassis DC power supply

Figure 9-12 cPSB chassis DC power supplies (cutout view)

PRELIMINARY

Replace components

Power supply injector/ejector operation

The spring-loaded ejector is shown in the open and closed positions in Figure 9-13,
Injector/ejector handles (p. 9-42).

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
9-41
Issue 14, September 2009
See notice on first page

PRELIMINARY

Replace components

Replace cPSB chassis DC power supply

Figure 9-13 Injector/ejector handles

The following actions are used with the spring-loaded latch:

To remove a power supply: push down the spring-loaded latch on the ejector and
rotate the ejector away from the power supplys faceplate. This levers the power
supply away from the backplane.

To insert a power supply: open the injector/ejector mechanism. Once the power
supply is fully seated in the slot, close the ejector. This signals the system that the
power supply is fully seated and ready to go.

PRELIMINARY

Hot-swappability

A cPSB chassis DC power supply can be replaced without the need for powering down
the TPU shelf.
Duration

This procedure typically takes 10 minutes to perform.

9-42

Replace cPSB chassis DC power supply

Required tools

This procedure requires the following tools:

No.2 Phillips screwdriver

Flat head screw driver

an antistatic wrist strap

an electrostatic discharge mat

PRELIMINARY

Replace components

Required materials

One DC power supply.

Procedure

To replace a cPSB chassis DC power supply, perform the following:

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

Using the No. 2 phillips screwdriver, unscrew the two retention screws at the top of
the air intake grill.

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

Grasp the top front of the grill and pull it gently forward to loosen the top and release
it from the screw locations. (Youll need to reach under and up beneath the cable
management unit (CMU).

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
9-43
Issue 14, September 2009
See notice on first page

PRELIMINARY

Replace components

Replace cPSB chassis DC power supply

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

Place your hands underneath the bottom of the grill and lift it up to remove the bottom
tab connectors from the chassis.

PRELIMINARY

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

Tilt the loosened grill toward you and remove it from the chassis.

9-44

Replace cPSB chassis DC power supply

PRELIMINARY

Replace components

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

Set the grill on the ESD mat.

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

Using the flat head screwdriver, loosen the retention screws that fasten the power
supply board to the chassis.
...................................................................................................................................................................................................

To release the power supply from the backplane, follow the directions provided under
Power supply injector/ejector operation (p. 9-41).
...................................................................................................................................................................................................

Pull the power supply away from its backplane connection, turn it and slide it out of
the enclosure. Youll need to turn it sideways as you remove it to clear the CMU.
...................................................................................................................................................................................................

Prepare the replacement power supply by setting the injector/ejector mechanism to the
open (ejected) position. (See also Power supply injector/ejector operation (p. 9-41).)
...................................................................................................................................................................................................

Result The following occurs:

The power supply LEDs blink, and then light steadily.

The power supply is now operating.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
9-45
Issue 14, September 2009
See notice on first page

PRELIMINARY

Turn the replacement power supply in the power case and align the rails on the power
supply with the guides in the slot, then slide the power supply on the guides and press
firmly to seat the connector in the slot.

PRELIMINARY

Replace components

Replace cPSB chassis DC power supply

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

Using the flat head screwdriver, tighten the retention screws that are used to fasten the
power supply board to the chassis.
...................................................................................................................................................................................................

Replace the air intake grill by reversing steps 2 through 4 above.

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

Align the screws at the top of the grill with the corresponding holes on the enclosure,
and then replace and tighten the screws with the No. 2 Phillips screwdriver.

END OF STEPS

PRELIMINARY

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

9-46

Replace
an air filter in the cPSB chassis
...................................................................................................................................................................................................................................
Purpose

Perform this procedure to replace an air filter in the air intake grill of the cPSB
chassis.

PRELIMINARY

Replace components

Reason to perform

The cPSB air filter should be replaced about every three months under normal
operating conditions.
If the environment has more dust and other particulate matter than normal, replacement
will need to occur at more frequent intervals. Check your local conditions to see when
replacement is necessary.
Duration

This procedure typically takes 5 minutes to perform.

Location

The air filter is located at the bottom of the cPSB chassis (Figure 9-14, Air filter
location (p. 9-48)) covered by an air intake grill.

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
9-47
Issue 14, September 2009
See notice on first page

PRELIMINARY

Replace components

Replace an air filter in the cPSB chassis

Figure 9-14 Air filter location

Required tools

This procedure requires a No.2 Phillips screwdriver.

Required materials

One replacement air filter.

Procedure

PRELIMINARY

To replace a cPSB chassis air filter, perform the following:

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

Using the No. 2 phillips screwdriver, unscrew the two retention screws at the top of
the air intake grill..

9-48

Replace an air filter in the cPSB chassis

PRELIMINARY

Replace components

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

Grasp the top front of the grill and pull it gently forward to loosen the top and release
it from the screw locations. (Youll need to reach under and up beneath the cable
management unit (CMU.

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

Place your hands underneath the bottom of the grill and lift it up to remove the bottom
tab connectors from the chassis.

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
9-49
Issue 14, September 2009
See notice on first page

PRELIMINARY

Replace components

Replace an air filter in the cPSB chassis

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

PRELIMINARY

Tilt the loosened grill toward you and remove it from the chassis.

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

Set the grill on the ESD mat.

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

Note that the air filter is visible clipped into the back of the intake grill.

9-50

Replace an air filter in the cPSB chassis

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

Unfasten the filter retainer clips to release and remove the air filter element.
...................................................................................................................................................................................................

Fit a new air filter element into the back of the intake grill, then clip the filter retainer
into place.

PRELIMINARY

Replace components

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

Replace the air intake grill by reversing steps 2 through 4 above.

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

Align the screws at the top of the grill with the corresponding holes on the enclosure,
and then replace and tighten the screws with the No. 2 Phillips screwdriver.

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
9-51
Issue 14, September 2009
See notice on first page

PRELIMINARY

Replace components

Replace
RNC cabinet components
...................................................................................................................................................................................................................................
Introduction

This section provides the following procedures for replacing RNC cabinet components:
Replace a cabinet alarm board (p. 9-53)

PRELIMINARY

Replace a circuit breaker in the ECBU (p. 9-56)

9-52

Replace
a cabinet alarm board
...................................................................................................................................................................................................................................
Purpose

Perform this procedure to replace a faulty cabinet alarm board in the power distribution
shelf.

PRELIMINARY

Replace components

Important! This procedures interrupts alarm condition reporting to the frame LEDs
and to the server alarm cards.
Reason to perform

Perform this procedure when troubleshooting indicates that the cabinet alarm board has
failed.
Duration

This procedure typically takes less than 5 - 15 minutes to perform.

Required tools

This procedure requires the following tools:

a flathead screwdriver

an antistatic wrist strap

an electrostatic discharge mat

Required materials

This procedure requires a replacement cabinet alarm board.

Procedure

To replace a faulty cabinet alarm board, perform the following steps:

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

Note the location of each cable connected to the front of the cabinet alarm board and
then disconnect the two cables from the alarm board (see the following figure).

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
9-53
Issue 14, September 2009
See notice on first page

PRELIMINARY

Replace components

Replace a cabinet alarm board

You will need this information to reconnect the cables to the replacement cabinet alarm
board later in this procedure.
...................................................................................................................................................................................................

Use a flathead screwdriver to loosen the captive screws at the top and bottom of the
alarm board.
...................................................................................................................................................................................................

Pull the board out of the slot and place it on the ESD mat.
Use a gentle side-to-side motion to loosen the alarm board from its connectors while
removing it.
...................................................................................................................................................................................................

Get the replacement alarm board from the ship kit.

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

Keeping the board vertical, gently slide the board into the slot until it will not advance
easily (usually about 1/4 inch of the board remains extended past the front of the
power distribution unit).
...................................................................................................................................................................................................

Use a gentle side-to-side motion to move the board securely into the slot until it is all
the way in and flush with the other shelf components.
...................................................................................................................................................................................................

PRELIMINARY

Use a flat-head screwdriver to tighten the captive screws on the top and bottom of the
board.

9-54

Replace a cabinet alarm board

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

Connect any cables to the replacement alarm board that you unplugged from the failed
alarm board.
END OF STEPS
...................................................................................................................................................................................................

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
9-55
Issue 14, September 2009
See notice on first page

PRELIMINARY

Replace components

PRELIMINARY

Replace components

Replace
a circuit breaker in the ECBU
...................................................................................................................................................................................................................................
Purpose

Perform this procedure to replace a faulty circuit breaker in the ECBU.

Reason to perform

To correct partial loss of power to some frame components.

Duration

This procedure typically takes less than 10 minutes.

Before you begin

Ensure the following:

The ECBU is operating normally and that troubleshooting has identified the need
for breaker replacement.
You have replacement breakers of the same amperage rating as the one that you
want to replace.

Required tools

This procedure requires the following tools:

Flat head screwdriver.

Either of the following:

The breaker extraction/insertion tool located in the documentation holder behind

the Frame Interface Panel (FIP) covering panel.

The handle of the ECBU alarm board. This handle can also serve as the breaker
extraction and insertion tool.

Required materials

A replacement breaker of the correct amperage.

Maintenance state

PRELIMINARY

This procedure interrupts the cabinet alarm condition.

Procedure

To replace a faulty circuit breaker in the ECBU, perform the following:

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

Manually set the circuit breaker that is being replaced to the off position.

9-56

Replace a circuit breaker in the ECBU

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

Retrieve the breaker extraction/insertion tool from the documentation holder located on
the back of the panel that covers the FIP.
-ORIf necessary, remove the handle of the ECBU alarm board (breaker extraction and
insertion tool) from the ECBU alarm board by exerting finger and thumb pressure to
unscrew (counter-clockwise) the alarm board handle posts.

PRELIMINARY

Replace components

Important! It may be difficult to loosen (unscrew) the posts with your fingers. DO
NOT use an allen wrench to remove the screws that secure the alarm board handle
posts to the alarm handle. If necessary, try and break the grip of the alarm board
handle posts with a pair of needle-nose pliers.
...................................................................................................................................................................................................

Use the flat-head screwdriver to loosen the two screws at the top and bottom at each
end of the ECBU front panel.
...................................................................................................................................................................................................

Use the flat-head screwdriver to loosen the earthquake locking arm that secures the
ECBU front panel.The locking arm is located to the right or left of the ECBU front
panel
...................................................................................................................................................................................................

Remove the front panel.

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

Attach the breaker extraction/insertion tool to the breaker that is to be replaced as

follows:

Line up the threaded rods of the breaker extraction/insertion tool with the screw
holes of the breaker that you are going to remove.

Insert the threaded rods of the breaker extraction/insertion tool into the screw holes
of the breaker.

Use finger and thumb pressure on thebreaker extraction/insertion tool posts to

screw (clockwise) the threaded rods of the posts into the breaker screw holes.

Use a side-to-side motion (if necesary) to slowly remove the breaker.

When the breaker is completely out of the ECBU, unscrew the breaker
extraction/insertion tool from the breaker, and discard the faulty breaker.

Attach the breaker extraction/insertion tool to the replacement breaker.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
9-57
Issue 14, September 2009
See notice on first page

PRELIMINARY

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

PRELIMINARY

Replace components

Replace a circuit breaker in the ECBU

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

Use a side-to-side motion (if necessary) to slowly insert the replacement breaker into
position. Note that the new circuit breaker front should be flush with the others in
order to accommodate the front panel.
...................................................................................................................................................................................................

Remove the breaker extraction/insertion tool from the newly inserted breaker.
...................................................................................................................................................................................................

Replace the ECBU front panel, then use a flat-head screwdriver, to tighten the screws
on the top and bottom of front panel.
...................................................................................................................................................................................................

Resecure the earthquake locking arm of the ECBU front panel with the flat-head
screwdriver.
...................................................................................................................................................................................................

Set the circuit breaker to the on position.

Result The equipment fed by the new circuit breaker is powered on.
...................................................................................................................................................................................................

Return the breaker extraction/insertion tool to the document holder behind the covering
panel of the FIP, and reattach the covering panel.
-ORReattach the ECBU alarm board handle to the ECBU alarm board.
END OF STEPS

PRELIMINARY

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

9-58

Loopback
Testing
...................................................................................................................................................................................................................................
Introduction

Loopback testing, is intended to allow system users to test the provisioning of the links
between two PSUs.

PRELIMINARY

Replace components

Loopback testing can be run on a single PVC or on all PVCs on a given OC3 or 5E
GW port.
5E gateway

For a 5E Gateway, the system will query the RNCDB to get the local community
address (NEARCA) associated with the OC3 port. For the loopback to ALL PVCs, the
RNC constructs a list (1 through 254) of remote community addresses (FARCA),
excluding the NEARCA.
Procedure

The procedure for performing loopback testing is as follows:

Initiating PSU loopback test (p. 9-60)

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
9-59
Issue 14, September 2009
See notice on first page

PRELIMINARY

Replace components

Initiating
PSU loopback test
...................................................................................................................................................................................................................................
Purpose

To initiate a PSU loopback and verify the integrity of the links between two PSUs.
Reason to perform

To determine if there is ATM connectivity between an RNC 5E GW port and other

5ESS PSU(s).
APS consideration

If APS capability is enabled on the RNC, the 5EGW must be the active 5EGW in the
APS mated pair for the test to pass.
If the operational mode for that port is unidirectional, the ATM switch OC3 port that is
physically connected to the port under test must also be active for the test to pass.
Determine status and switching mode

To determine if the port to be tested is the active port in the pair, do either of the
following:
1. Browse to the TPU GUI APS Status page.
2. Execute the GET:RNC a,GICC b,5EGW, INFO CLI command.
Activate port

If it is then necessary to activate the port on the RNC, do either of the following:
1. Browse to the TPU GUI TPU Network Element page.
2. Execute the SWITCH TO MATE command from the TPU GUI command pull down
box on the ATM port in the 5EGW pair that you would like to switch away from.
Refer to your ATM switch manual to determine which OC3 port on the ATM switch is
active, and how to activate a port if necessary.
Procedure

To initiate a PSU loopback test, proceed as follows:

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

PRELIMINARY

Determine the GICC providing the OC3 port (5EGW/PSU gateway) that is to be
tested. See also APS consideration (p. 9-60).
...................................................................................................................................................................................................

Obtain access to the TICLI (see also Accessing TICLI (p. 6-18).

9-60

Initiating PSU loopback test

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

Execute the following command:

TST:PSU, RNC a, TPU b, GICC c, ATM d, FARCA {e|ALL} [,SUBNET f] [,
VCC|VPC] [;ENH]

where
a = RNC number (1-15)

PRELIMINARY

Replace components

b = TPU shelf number (1-2).

c = GICC slot number (3, 4,19,20).
d = ATM port number (1-4) - 1 is the bottom and 4 is at the top.)
e = Far End Community Address (FARCA) (1-254)
f = Far End Subnet (0-3) - Optional
VCC|VPC = indicates that the loopback test be run over VPC or VCC for Intra-Subnet
connections. This parameter is ignored for Inter-Subnet connections, since Inter-Subnet
is only VCC. If this parameter is not specified, then the provisioned connection type is
used.
ALL = The command will be issued on all applicable Community Addresses (CAs) at
the Far-End (up to 253), while excluding the CA (Near-End) of the port under test.
f = Far End Subnet (0-15) - Optional
ENH = Proprietary enhanced option. An enhanced loop back test is the same as a
standard loop back test except that the far end inserts their actual Virtual Path Identifier
(VPI) and Virtual Channel Identifier (VCI) into the looped back message thereby
allowing the user to verify exactly who it is they are communicating with.
Result The following reports are generated (depending upon which command was

used):

1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
TST:PSU,RNC a,TPU b,GICC c,ATM d,FARCA f, SUBNET g ENH! COMPLETE
1234567890123456789012345678901212345678901234567890123456789
PSU link loopback test results k
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
Managed resource: GICC c,ATM d
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
where
k = Test results: pass or fail

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
9-61
Issue 14, September 2009
See notice on first page

PRELIMINARY

Replace components

Initiating PSU loopback test

PRELIMINARY

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

9-62

PRELIMINARY

Part IV: Performance management

This Part provides the basic performance management service measurement categories
and processes associated with the 1X CDMA RNC.
Performance management

Performance management is the process of measuring system activity and using the
measurements to efficiently engineer system capacity and (when applicable) identify
and then correct system faults.
Service Measurements

The Service Measurements provided for 1X CDMA RNC will enable the Service
Provider to:

determine traffic usage

determine quality of service (QoS) metrics

determine critical system triggers

conduct special engineering studies

handoff matrix (HOM)

RF call trace

Real Time Performance Alarm feature

Contents
10-1

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
IV-1
Issue 14, September 2009
See notice on first page

PRELIMINARY

Chapter 10, Service measurement

PRELIMINARY

Service measurement
10

This chapter provides information pertinent to Service Measurement of the CDMA 1X

RNC.
Contents
Service measurement basics

10-2

CDN service measurements

10-3

RNC Performance Management

10-6

RNC-related XML count groups

10-9

Change B-PCF Service Measurement (SM) interval

10-13

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
10-1
Issue 14, September 2009
See notice on first page

PRELIMINARY

Service measurement

Service
measurement basics
...................................................................................................................................................................................................................................
Introduction

Service Measurement (SM) counts enable system users to understand traffic patterns on
their CDMA 1X RNC network, so that they can efficiently monitor, configure, and
grow their systems.
Detailed information

PRELIMINARY

For detailed information concerning methods and procedures used to obtain service
measurement data for the RNC and (in general) the CDMA Network, refer to
401-610-135 (Volumes 1 and 2).

10-2

CDN
service measurements
...................................................................................................................................................................................................................................
Introduction

CDN service measurement counts are RNC-specific counts reported by the CDN via
the legacy ECP/OMP service measurement interface.

PRELIMINARY

Service measurement

24-hour cycle

On an hourly basis, specific RNC-related service measurements are stored in files on

the OMP.
When a new hour begins, the corresponding hourly disk file from the previous day is
overwritten with new hourly data. Therefore, at any point in time, the 24 hourly files
contain data for the previous 24 hours.
Obtaining raw data

Service measurement data can be raw dumped, on the OMP, using a UNIX tool
called SMsmdump. Numerous command-line options are available that allow the user
to selectively dump (from all 24 files):

All the data

Portions of the data

Just one selected hourly file

SMsmdump tool location

The SMsmdump tool resides in the /omp/bin directory.

Base station measurement counts

The following Base Station Measurement count groups were updated to include
RNC-specific counts:

CDMA-PAF-CARR-L (see Figure 10-1, RNC-specific CDMA-PAF-CARR-L

counts (p. 10-4))
CP CDMA (see Figure 10-2, RNC-specific CP CDMA counts (p. 10-4))

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
10-3
Issue 14, September 2009
See notice on first page

PRELIMINARY

Service measurement

CDN service measurements

Figure 10-1 RNC-specific CDMA-PAF-CARR-L counts

Figure 10-2 RNC-specific CP CDMA counts

PRELIMINARY

Detailed count descriptions

For detailed information concerning RNC-specific CDN service measurement counts,

refer to 401-610-135 (Volume 1).

10-4

CDN service measurements

Storage on OMP

RNC-related CDN service measurements are stored on the OMP, in files smd.00
through smd.23, in the following directory:
/omp-data/smdata

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
10-5
Issue 14, September 2009
See notice on first page

PRELIMINARY

Service measurement

PRELIMINARY

Service measurement

RNC
Performance Management
...................................................................................................................................................................................................................................
Introduction

RNC performance measurements are collected and stored on the MM-AP in Extensible
Markup Language (XML) file format. These files are then collected hourly, or at
15-minute intervals by the OMP.
XML-Based RNC PM Counts

All counts are stored in 3GPP-compliant XML format.

When the collection interval timeout occurs, the TPU Manager, requests the PM count
data from the SNMP Agents residing in the CICC, GICC, and B-PCF cards.
After the count data is collected, the PM count data is translated into XML file format
and is written to a shared memory location. The data from the shared memory location
is then written into the following directory on the associated RNC-AP:
/var/flx/data/FMSsm/xml
Viewing raw PM data

To view the raw PM count files, the user only has to cd into the
/var/flx/data/FMSsm/xml directory and vi the appropriate file. However, the
SMxmldump tool can be used to format the XML files into a more user-friendly
format. See SMxmldump tool (p. C-2) in Appendix C, Service measurement
supplement for specifics.
Polling

The SM data is polled at one hour and at 15-minute intervals.

ATM counts

ATM counts are retrieved at 15-minute intervals.

RIM, TCS and CICC counts

The RIM, TCS and CICC counts are retrieved hourly.

PRELIMINARY

B-PCF counts

In Release 29.0, and beyond, B-PCF counts can be retrieved either hourly (default), or
at 15-minute intervals. This flexibility is provided by a TPU GUI configuration
parameter on the Configure Common BPCF Parameters page/screen.
See Change B-PCF Service Measurement (SM) interval (p. 10-13), for details on
how to modify the reporting interval.

10-6

RNC Performance Management

Hourly-interval directory storage

The hourly RIM, TCS, B-PCF, and CICC performance file data is stored in the
following directory on the RNC-AP supporting the RNC-M:
/var/flx/data/FMSsm/xml
The file is named as follows:

PRELIMINARY

Service measurement

g3SubNetwork=ECP12,g3ManagedElement=RNC14,rncFunction=z
where:
z = RNC-AP, TPU Traffic, or PCF
Note this is not the full name. An example of the full name is shown as follows:
A20040316.14151430_g3SubNW=ECP13,ME=RNC15,rncFnt=TPU

The timestamp portion within each file uniquely distinguishes it from the other files
(hourly and 15-minute interval files).
15-minute interval directory storage

The 15-minute interval ATM and B-PCF performance monitoring file data is stored in
the following directory on the RNC-AP supporting the RNC-M:
/var/flx/data/FMSsm/xml
The file is named as follows:
g3SubNetwork=ECP12,g3ManagedElement=RNC14,rncFunction=z
where:
z = TPU or PCF.
The timestamp portion within each file uniquely distinguishes it from the other files
(hourly and 15-minute interval files).
Four performance monitoring files are created each hour, containing all 15-minute
performance monitoring counts from various RNC components.
Retrieval

The OMP XML file retrieval tool automatically retrieves XML files from the
/var/flx/data/FMSsm/xml directory.
Data collection intervals

The upstream processor will then SFTP the files from the OMP.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
10-7
Issue 14, September 2009
See notice on first page

PRELIMINARY

The SM and performance monitoring data collected during an hourly or 15-minute

interval are available for retrieval by an upstream processor such as Vallent Prospect
within one minute from the end of the interval.

PRELIMINARY
PRELIMINARY

Service measurement

RNC Performance Management

Deletion of old files

The SM and performance monitoring XML files that exceed 48-hours are automatically
deleted.
Managing XML RNC PM data

Management of XML RNC PM data is accomplished through the use of tunable

variables. Refer to Managing XML RNC PM data (p. C-8) in Appendix C, Service
measurement supplement for specifics.

10-8

RNC-related
XML count groups
...................................................................................................................................................................................................................................
Introduction

The RNC-related XML count groups are categorized into the following four types:

AP XML counts (hourly)

TPU traffic XML counts (hourly)

TPU based XML counts (15-minute)

B-PCF XML counts (hourly or 15-minute)

PRELIMINARY

Service measurement

AP XML counts (hourly)

Hourly AP XML counts are categorized as follows:

Counts pegged per RNC

Counts pegged per TCS

Counts pegged per RNC

These counts provide:

A10/A11 gateway performance statistics

A8/A9 gateway performance statistics

GICC shelf controller performance statistics

RNC-related RIM statistics

Counts pegged per TCS

These counts provide:

RNC call attempt and blocked call statistics

Processor occupancy and overload statistics

PCF disconnect statistics

RNC call setup failure statistics

RNC dropped call statistics

RNC busy and unavailable call statistics

RNC calls redirected to 5ESS statistics

RNC Frame Selector (FS) statistics

TPU traffic XML counts (hourly)

Traffic counts

Counts pegged per ESC

Counts pegged per GICC

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
10-9
Issue 14, September 2009
See notice on first page

PRELIMINARY

Hourly TPU traffic XML counts are categorized as follows:

PRELIMINARY

Service measurement

RNC-related XML count groups

Counts pegged per OC3

Counts pegged per TCU

Data rate RLP counts

Traffic counts

These counts provide:

Frame Selector (FS) unavailable statistics

CICC processor occupancy statistics

Bearer IP packet statistics

FSRM packet statistics

FS/RLP packet statistics

FSRM duration statistics

Counts pegged per ESC

These counts provide Ethernet Switch Card (ESC) duration statistics.

Counts pegged per GICC

These counts provide:

GICC card duration statistics

OC3 failover statistics

Counts pegged per OC3

These counts provide OC3 duration statistics.

Counts pegged per TCU

These counts provide TPU duration statistics.

Data rate RLP counts

These counts provide RLP byte transmission statistics.

TPU based XML counts (15-minute)

PRELIMINARY

Fifteen minute TPU based XML counts are categorized as follows:

Counts pegged per ESC

Counts pegged per GICC

Counts pegged per OC3

ATM traffic counts

IPBH counts per GIGE

IPSHO counts

Counts pegged per ESC

These counts provide ESC ethernet packet statistics.

10-10

RNC-related XML count groups

Counts pegged per GICC

These counts provide:

A10/A11 packet statistics

GICC ethernet kilo-octet statistics

GICC ethernet and ICMP packet statistics

PRELIMINARY

Service measurement

Counts pegged per OC3

These counts provide:

Dropped ATM cell statistics

ATM cell related OC3 port statistics

ATM PDU-related OC3 port statistics

Dropped packet statistics

ATM traffic counts

These counts provide:

ATM cell related discards, anomalies and error statistics

SONET alarm statistics

APS related performance statistics

SONET related performance statistics

GICC performance statistics

IPBH counts per GIGE

These counts provide IPBH related performance staistics.

IPSHO counts

These counts provide IPSHO related performance staistics.

B-PCF XML counts (hourly or 15 minute)

Hourly or fifteen minute B-PCF based XML counts are categorized as follows:
Packet discards and inactivity counts

Link opens and closures

RP connect failures/attempts

3G R-P connection attempts

A8/A10 packet discards

A8 connect denials, segmented packets, and directional counts

A10 tunnel failures and release counts

A11 registered failures

Packet Data Link Layer Connection reactivations

CPU overloads

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
10-11
Issue 14, September 2009
See notice on first page

PRELIMINARY

PRELIMINARY
PRELIMINARY

Service measurement

RNC-related XML count groups

Mobile short data bursts

Early packet counts

PCF related counts

10-12

Change
B-PCF Service Measurement (SM) interval
...................................................................................................................................................................................................................................
Purpose

To modify the SM interval (15-minutes or 60-minutes) for a B-PCF.

Reason to perform

PRELIMINARY

Service measurement

More frequent reported SM data, or less frequent reported SM data is required.

When to perform

Change of B-PCF SM Reporting Period should be done during a maintenance window

since this results in loss of BPCF SM files for the new interval. The optimum time
interval for modifying this parameter is within first 5 minutes at the top of hour. For
example, between 6:00 am and 6:05 am.
Before you begin

Ensure the following:

That the OMP and RNC has been upgraded to Release 29.0, or beyond.
All BPCFs in the RNC are up and running (they should not be locked or disabled).

That the SC-GICCs are in the Active/Standby mode. This will ensure that the
dynamic update is successful.

That the SMxmlcollector on the OMP is configured to collect SM files from the
RNC-APs every 15 minutes. (This is the default configuration on the OMP.) Verify
using the SMxmlconfig a command on the OMP. See the sample output that
follows

ap03 15 0 oamproxy /var/flx/data/FMSsm/xml

ap04 15 0 oamproxy /var/flx/data/FMSsm/xml

Required hardware

At least one installed B-PCF blade.

Duration

This procedure should take less than 5 minutes to perform

Procedure

Perform the following procedure:

Obtain access to TPU-GUI either by:

Direct access method. Refer to Accessing TPU GUI (p. 6-6).

EMS. Refer to Logging on to Element Management System (EMS) (p. 6-5).

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
10-13
Issue 14, September 2009
See notice on first page

PRELIMINARY

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

PRELIMINARY

Service measurement

Change B-PCF Service Measurement (SM) interval

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

Click on the BPCFs icon.

Result: The GUI navigates to the Blade Packet Control Function (BPCFs) page.
...................................................................................................................................................................................................

Click on the BPCF Configuration Data icon.

Result: The GUI navigates to the Configure BPCFs-Add/Delete page.
...................................................................................................................................................................................................

Click on the Configure Common BPCF Parameter icon (located above the Add BPCF:
box) to configure the common B-PCF parameters (used across all B-PCFs).
...................................................................................................................................................................................................

Important! The first time that the reporting interval is changed, the default of 60
will be displayed.
Use the pull-down box associated with the B-PCF SM Reporting Period and change
the interval to either 15 or 60.
...................................................................................................................................................................................................

Click on the Submit button.

Result: The following occurs:

All the parameters are inserted into the database.

DUA will create and SFTP the new config.ini file to the TPU shelf.

PRELIMINARY

Note that the change in a reporting period will result in the loss of B-PCF SM files
for the new interval. For example:
If the B-PCF SM Reporting Period is changed from 60 minutes to 15 minutes
at say 6:05, then there will be no 15 minute SM file generated at 6:15. The first
SM file will be generated at 6:30.

If the B-PCF SM Reporting Period is changed from 15 minutes to 60 minutes

at say 6:05, then there will be no hourly SM file generated at 7:00. The first
SM file will be generated at 8:00.

If the reporting interval is 60 minutes, peaks and averages are calculated for 1
hour. If reporting interval is 15 minutes, peaks and averages are calculated for
15 minutes.

10-14

PRELIMINARY

Part V: Configuration management

This Part provides the processes and procedures associated with configuration
management. The processes and procedures associated with configuration management
of the CDMA 1X RNC are categorized in the following paragraphs.
OAM Proxy AP

In the event (rare) that the Customer Maintenance Network IP addresses and network
mask previously assigned for the OAM Proxy AP pairs during system integration
should ever need to be reconfigured, see the OAM Proxy Operations, Administration,
and Maintenance guide (401-710-212) for information regarding the use of the
nbifconfig command in configuring the OAM Proxy AP pairs.
Important! Consult with Alcatel-Lucent before attempting such a reconfiguration.
Software configuration

Software configuration for the RNC equates to TPU-GUI provisioning, RC/V

provisioning, FAF/QFAF control, and software installation (generic retrofits and
software updates). Essentially, the elements that are associated with the ongoing
evolution of the RNC product.
Software Update Automation (SUA)

Be aware that during the process of SUA, no activities targeted at updating the RNC or
RC/V databases (such as described in this Part) should be attempted. In general, all
system maintenance activity should be minimized.

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
V-1
Issue 14, September 2009
See notice on first page

PRELIMINARY

Configuration management

Overview

ATM connectivity

Virtual Path Connections (VPCs) or Virtual Channel Connections (VCCs) must be set
up in the ATM network to allow RNCs to communicate with each other, and Packet
switching Units (PSUs) in the Soft Handoff (SHO) universe. Periodic modifications
will be required to ensure optimimum connectivity.
Automatic Protection Switching (APS)

APS is a method at the physical layer to provide redundancy services to the ATM layer
and for ATM services above the ATM layer. Each 5EGW is protected independently,
and individually.
For RNCs that were previously operating without APS, migration to APS can be
achieved via TPU GUI.
IPSHO Connectivity

The IPSHO feature allows for connectiung the RNC and 5ESS to an IP transport based
soft handoff universe.
Growth/degrowth of TPU cards

Due to the complexity involved in expanding RNC capacity Alcatel-Lucent limits

customer expansion tasks to the growth and degrowth of GICC, CICC, and B-PCF
cards.
New growth or degrowth of GICCs in an RNC in which APS is enabled, is
accomplished in the same manner previously applied for non-APS growth/degrowth via
TPU GUI.

PRELIMINARY

Contents
Chapter 11, Software configuration management

11-1

Chapter 12, Configuring ATM connectivity in RNCs SHO universe

12-1

Chapter 13, Automatic Protection Switching (APS)

13-1

Chapter 14, Configuring IPSHO connectivity

14-1

Chapter 15, Growing/Degrowing TPU cards

15-1

V-2

PRELIMINARY

11
Software
configuration
management

The purpose of this chapter is to provide information concerning RC/V provisioning,

FAF/QFAF control, RNC fault management parameters, software updates, generic
retrofits, and golden image updates associated with the:

RNC-AP and OAM proxy AP

TPU

Contents
RC/V provisioning

11-2

FAF/QFAF control

11-12

RNC fault management parameters

11-15

Verify or modify RNC fault management parameters

11-16

Software Update Automation (SUA)

11-20

Generic retrofit

11-21

Golden image restoration (B-PCF)

11-25

To download cpio file from Online Customer Support Site (OLCS)

11-26

To load and install B-PCF golden image package

11-35

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
11-1
Issue 14, September 2009
See notice on first page

PRELIMINARY

Software configuration management

RC/V
provisioning
...................................................................................................................................................................................................................................
Introduction

Because RC/V is still the primary means for the provisioning of ECP Complexes
(ECPCs), cell sites, Packet Pipes, and associated trunks, it was necessary to create new,
and modify existing RC/V forms in order to allow the RNC to conform with existing
CDMA network elements.
ECP database synchronization

The RC/V database data that is provisioned via the ECP RC/V screens is synchronized
with the values in the RNCDB by a process that is designated as DBrncproxy.
Loss of synchronization

In a worst case scenario, if both copies of the RNCDBMS were suddenly OOS, the
DBrncproxy process would not be active. In that case, the RC/V database data would
then lose synchronization with the RNCDB.
This non-synchronzation issue would remain until the RNCDBMS again became
active. At that point the DBrncproxy process would then be brought up, and the
RC/V database would be synchronized with the RNCDB by a timer event or an update
operation.
Initial implementation

When an RNC is introduced into an existing network, the following forms must be
modified:

Executive Cellular Processor Packet Core (ecppkt)

Cell2 (cell2)

Cell3g (cell3g)

AP Equipment (apeqp)
Executive Cellular Processor 3G (ecp3g)

PRELIMINARY

ecppkt form

The ecppkt form (Figure 11-1, Typical ecppkt form (screen 1) (p. 11-3) and Figure
11-2, Typical ecppkt form (screen 2) (p. 11-3)) was modeled after the existing ecp
form. Its purpose is to provide parameters or information that is expected to be the
same across the whole ECP complex. Therefore, this is system-level global information
needed for allowing RNCs to exist within the system.

11-2

RC/V provisioning

Figure 11-1 Typical ecppkt form (screen 1)

PRELIMINARY

Software configuration management

Figure 11-2 Typical ecppkt form (screen 2)

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
11-3
Issue 14, September 2009
See notice on first page

PRELIMINARY

Software configuration management

RC/V provisioning

Figure 11-3 Typical ecppkt form (screen 3)

Note that as each Max Number field is entered with a value, that value is checked
against the QFAF limit (see also FAF/QFAF control (p. 11-12)).
Information explaining the various fields and the most current version of this form can
be found in the 401-610-036.
cell2 form (existing)

Screen 1 of the cell2 form (Figure 11-4, Typical cell2 form (screen 1) (p. 11-5)) has
anRNC ID field which when populated, indicates the default RNC that will handle
the packet data call for the cell, assuming that the Screen 12 PKT CORE DATA field
(Figure 11-5, Typical cell2 form (screen 12) (p. 11-5)) is also enabled.

PRELIMINARY

The RNC Homed field on Screen 1 is always entered with an n because it is

unused.

11-4

RC/V provisioning

Figure 11-4 Typical cell2 form (screen 1)

PRELIMINARY

Software configuration management

Figure 11-5 Typical cell2 form (screen 12)

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
11-5
Issue 14, September 2009
See notice on first page

PRELIMINARY

Information explaining the various fields and the most current version of this form can
be found in 401-610-036.

PRELIMINARY

Software configuration management

RC/V provisioning

apeqp form (existing)

The apeqp form (Figure 11-6, Typical apeqp form (p. 11-6)) has been enhanced to
include an RNC AP field that is populated with y (yes) or n (no) for provisioning an
AP as an RNC-AP.
Figure 11-6 Typical apeqp form

The OAM Proxy AP and RNC-AP also need to be informed as to whether this ECPC
is managed by the OMC-RAN or the OMP from a new OMC-RAN Managed field
that is populated with y (yes) or n (no). Feature activation from the OMP is also
required.
Information explaining the various fields and the most current version of this form can
be found in 401-610-036.
ecp3g form (existing)

The ecp3g form is used to provision Packet Core parameters that apply to the MSC.
This form is also used to enable the 3G1X IP service, which is needed for the RNC.

PRELIMINARY

A sample ecp3g form is shown below:

11-6

RC/V provisioning

Figure 11-7 Sample ecp3g form (screen 1)

PRELIMINARY

Software configuration management

Figure 11-8 Sample ecp3g form (screen 6)

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
11-7
Issue 14, September 2009
See notice on first page

PRELIMINARY

Software configuration management

RC/V provisioning

Figure 11-9 Sample ecp3g form (screen 7)

Post implementation

In the post-implementation phase, as new growth demands become apparent, updates

of the following forms (under FAF/QFAF control as required) will be necessary:

Executive Cellular Processor Packet Core (ecppkt)

Cell2 (cell2)

AP Equipment (apeqp)

Note also that values for 3G packet data on the following forms may affect data calls
that have been offloaded to the 1X RNC:

Subscriber and Feature Information (sub) form

Executive Cellular Processor (ecp) form

Executive Cellular Processor for 3G (ecp3g) form

Cell Site for 3g (cellg)

PRELIMINARY

1X RNC packet filtering

The 1X RNC packet filtering capability is provided to reduce the likelihood of blind
attacks that inject bad packets into the B-PCFs from an unknown PDSN.

11-8

RC/V provisioning

Prior to the introduction of packet filtering, a theoretical possibility existed that an

unknown source could inject corrupt packets by just guessing the destination IP
address, the protocol number and other information, that is used to communicate with
the GICC.
Packet filtering will perform verification of the source IP address to stop attacks from
an unknown source. The GICC will then discard packets received from any unknown
source.

PRELIMINARY

Software configuration management

Known sources would be the static PDSNs configured in the MSC, and the PDSNs
learned by the BPCFs. (Also known as dynamic or unconfigured PDSNs.)
Security administration

Control of this feature is provided via a secure RC/V form under the control of the
systems security administrator. For specifics regarding this feature refer to
401-662-112, Centralized Security Management Security Administration Guide.
Troubleshooting

Various actions that can be taken when problems associated with this feature arise, are
provided in 1xRNC packet filtering (p. 8-24).
Inter-MSC ANSI-41 Hard Handoff for Packet Data Calls

This feature provides the capability for 3G packet data hard handoffs. This feature is
implemented via RC/V and FAF control. See also FAF/QFAF control (p. 11-12).
The cell3g and net forms provide specific fields (see the bolded fields in the Figures
that follow) that need to be enabled (y) to activate this feature.

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
11-9
Issue 14, September 2009
See notice on first page

PRELIMINARY
PRELIMINARY

Software configuration management

RC/V provisioning

11-10

RC/V provisioning

PRELIMINARY

Software configuration management

The following RC/V forms are also used in support of this feature:

ivc

ivt

fci

itg
link

For specific information conerning how these forms and their respective fields are
populated, refer to 401-610-036, Alcatel-Lucent CDMA Network Database Update
Manual.
Note that the associated FAFs need to be enabled, prior to updating the RC/V forms.

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
11-11
Issue 14, September 2009
See notice on first page

PRELIMINARY

Software configuration management

FAF/QFAF
control
...................................................................................................................................................................................................................................
introduction

At the initial introduction of any RNC into an MSC, FAF/QFAF control will be
implemented by Alcatel-Lucent.
CDMA 1X RNC FAF/QFAFs

PRELIMINARY

A number of FAF/QFAFs need to be set for the 1X RNC features. The CDMA 1X
RNC FAF/QFAF settings are as follows.
QFAF

Description

CELL 116

Packet-Based Core Network Solution - Qualifier

is set to the maximum number of Packet Data
Cells (384 in R22.0).

CELL 150

1xRNC IP Soft Handoff Gateway

(1xRNCIPSHOGW) - Qualifier is set to 30
(default value).

CELL 159

Number of RNC Data CICCs - Qualifier is set to

the total number of Data CICCs for all RNCs on
a specific MSC. These are authorized on the
ECPPKT form.The total of all the per RNC
numbers on the ECPPKT form must be less than
or equal to the QFAF.

CELL 167

Number of CDMA 1X RNC Data Frame selectors

- Qualifier is set to the total number of data
Frame Selectors for all RNCs on a specific MSC.
These are authorized on the ECPPKT form. The
total of all the per RNC numbers on the ECPPKT
form must be less than or equal to the QFAF.

CELL 168

CDMA 1X RNC Count on ECPPKT form Qualifier is set to the number of CDMA 1X
RNCs the customer has purchased. These can be
authorized on the ECPPKT form.

CELL 154

Number of B-PCFs at RNC - Qualifier is set to

maximum number of B-PCFs equipped at RNC.

CELL 155

Number of B-PCFs with TCP Jitter at RNC Qualifier is set to maximum number of B-PCFs
with TCP Jitter equipped at RNC.

11-12

FAF/QFAF control

FAF

Description

838

FAF 1513 depends on this FAF (3G-1X

Packet Data).

1449

FAF 1513 depends on this FAF

(InterSystemPage2 To Soft Handoff
Neighbor)

1488

Enables logging of RNC database changes

on the OAM Proxy AP. When this feature
is enabled, the operator can view all
database transactions made through the
TPU GUI in an administrative log file
stored on the OAM Proxy AP.

1513

Enables LA/LAC paging for packet data

with the ability to provision the number of
paging attempts (1 to 4, default 2) and the
paging type (LA, LAC, MSC, or default
MSC) for each attempt.

1610

RNC Dormant Handoff Optimization

1618

Alternate FS_QFAF Control

1636

RNC3G1XPDHHO. Hard Handoff for

Packet Data Calls

PRELIMINARY

Software configuration management

non-CDMA 1X RNC FAF/QFAFs

There are also non-CDMA 1X RNC FAF/QFAFs that need to be set for the CDMA 1X
RNC feature as follows:

IP Data Service with CDMA Packet Mode 3G IP Service - No qualifier is used,

qualifier is set to zero.

3G1X Basic Software Package - No qualifier is used, qualifier is set to zero.

Post implementation

In the post-implementation phase, when additional CICC cards are to be grown, or

Data Frame Selectors are to be added, the Service Provider will have to contact
Alcatel-Lucent to implement the appropriate FAF updates.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
11-13
Issue 14, September 2009
See notice on first page

PRELIMINARY

By the same token, as additional B-PCFs are grown in the MSC, it will be necessary
for the Service Provider to contact Alcatel-Lucent to implement the appropriate FAF
updates.

PRELIMINARY

Software configuration management

FAF/QFAF control

Reducing number of B-PCFs with jitter feaure

After the Number of B-PCF with TCP Jitter QFAF is intially set, a Service Provider
may later wish to reduce the number of B-PCFs that use the TCP Jitter feature. At
that time, they can contact Alcatel-Lucent to implement the change.
When the QFAF limit is decreased, the DB RNC proxy process will check the
RNC-DB to ensure that the number of B-PCFs that have the TCP Jitter feature
enabled does not exceed the QFAF limit.

PRELIMINARY

The TCP Jitterfeature will automatically be disabled on the B-PCF(s), in the reverse
order in whch they were grown in.

11-14

RNC
fault management parameters
...................................................................................................................................................................................................................................
Introduction

The RNC internally correlates alarms, events, asserts, and state information to perform
alarming and fault recovery.

PRELIMINARY

Software configuration management

Thresholds

Fault management for key conditions such as BPCF OOS, PSU GW OOS, PCF
Reachability, and so forth, is provided via the RNC Fault Parameters screen of the
TPU GUI.
Procedure

The procedure for monitoring and changing the threshold levels associated with these
key conditions is provided as follows:
Verify or modify RNC fault management parameters (p. 11-16)

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
11-15
Issue 14, September 2009
See notice on first page

PRELIMINARY

Software configuration management

Verify
or modify RNC fault management parameters
...................................................................................................................................................................................................................................
Purpose

To certify that the site is ready for cabinet installation.

Reason to perform

Conditions have arisen that makes it necessary to verify and possibly modify the
threshold for one or more RNC fault management parameters previously configured.
Procedure

To verify or modify the thresholds of one or more RNC fault management parameters,
perform the following:
...................................................................................................................................................................................................

Obtain access to TPU-GUI either by:

Direct access method. See also Accessing TPU GUI (p. 6-6).
EMS. See also Logging on to Element Management System (EMS) (p. 6-5).

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

PRELIMINARY

If using EMS, at the OMP Web page you need to select 1X RNC TPU Web to
navigate to the 1X RNC TPU Web page. If using the direct access method, the same
will result. See the following example screen.

11-16

Verify or modify RNC fault management parameters

PRELIMINARY

Software configuration management

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

On the 1X RNC TPU Web page select Configuration Data.

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
11-17
Issue 14, September 2009
See notice on first page

PRELIMINARY

Software configuration management

Verify or modify RNC fault management parameters

Result The GUI navigates to the RNC Configuration Data page (see example

screen).

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

PRELIMINARY

On the RNC Configuration Data page under RNC Dynamic Data select RNC Fault
Management Parameters.

11-18

Verify or modify RNC fault management parameters

Result The GUI navigates to the RNC Fault Management Parameters screen.

PRELIMINARY

Software configuration management

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

Verify or modify the appropriate parameter(s) as required.

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

Click on Submit.
Result The appropriate parameter(s) are submitted.
...................................................................................................................................................................................................

Click on Done.
Result The system navigates back to the RNC Configuration Data page.
...................................................................................................................................................................................................

If you wish to exit click on Logout.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
11-19
Issue 14, September 2009
See notice on first page

PRELIMINARY

Software configuration management

Software
Update Automation (SUA)
...................................................................................................................................................................................................................................
Introduction

The Software Update Automation (SUA) tool, automates the Software Update (SU)
process. The SUA tool reduces the planned downtime period and human errors in the
SU installation procedures.
Software upgrades

SUA supports the software upgrade of MM-APs (RNC-APs and OAM Proxy APs) and
TPU shelf software and firmware in two phases.
In the first phase a software update is done on MM-APs and in the second phase the
TPU Shelf is upgraded.
All the states of RNC SUA are integrated with the states of MM-APs. The user will be
able to monitor the progress of each state of the MM-AP while monitoring the progress
of the RNC upgrade as it is going through the same state at the same time, due to the
fact that they are closely integrated together.
SU procedures

PRELIMINARY

For the actual detailed procedures for performing an SU on the RNC-related entities,
refer to the individual SU document provided with each SU.

11-20

Generic
retrofit
...................................................................................................................................................................................................................................
Introduction

Generic retrofits for the RNC elements are done in conjunction with the ECP generic
retrofit that occurs when there is a new release of ECP software.

PRELIMINARY

Software configuration management

Generic retrofit process

Table 11-1, Timeline of Retrofit Activities (p. 11-21) provides a high-level overview
of the overall generic retrofit process as it also applies to RNC for a retrofit from
Release 23.0 to Release 24.0. For the actual detailed procedures for performing a
generic retrofit on the RNC-related elements, refer to hte CDMA Network Release
Software Retrofit Procedures (401-610-190).
Important! Because there is no retrofit to Release 23.0, the generic retrofit process
will begin for Release 24.0.
Table 11-1

Timeline of Retrofit Activities

Time before,
on, or after
the night of
retrofit
3 weeks before

Stage

Activity

Install BWM23-0003 with Critical Fix Tool (CFT) 23-i003

or later.

Log in to the AMPS/PCS Release 24.0 Retrofit Information

web site at:
https://wireless.support.alcatel-lucent.com/amps/rls_info/rls_
doc/wirelessRetrofit/24.0/
Then select ODD Retrofit Questionnaire. Download, print,
and complete the questionnaire and retain the completed
questionnaire for future reference. You need not return the
completed questionnaire to Alcatel-Lucent.
Ensure that the MM-AP hub firmware is upgraded to
Avaya Hub Firmware Version 4.0 or later.

If the fourth pair of Moving Head Disks (MHDs 6 and 7) is

installed in the ECP, verify that MHDs 6 and 7 are 9-GB
disks.

Ensure that Feature 9137.2, Mandatory Features Before

Retrofit to Release 24.0, is enabled and activated.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
11-21
Issue 14, September 2009
See notice on first page

PRELIMINARY

Software configuration management

Table 11-1

Generic retrofit

Timeline of Retrofit Activities

Time before,
on, or after
the night of
retrofit
2 weeks before

11 days before

10 days before

Stage

(continued)

Activity

Receive the OSR tool, and the RNC OSR tool from
Alcatel-Lucent via either CD-ROM or download from the
On-Line Customer server.

If you do not plan to download the Release 24.0

Pre-Retrofit System Check tool from the On-Line Customer
server, receive the Pre-Retrofit System Check tool on
CD-ROM from Alcatel-Lucent.

Receive a Alcatel-Lucent Required ECP Retrofit

Information e-mail message from Alcatel-Lucent. That
e-mail requires you to send your contact information, such
as the name and telephone number of the retrofit engineer,
to Alcatel-Lucent.

Receive the CDMA Networks Software Retrofit Procedures

document for the release to which the system is to be
retrofitted.

10.

Load the Release 24.0 OSR tool on the OMP.

11.

Load the Release 24.0 RNC OSR tool on the OMP.

12.

Either ship the tapes of the ECD database dump to

Alcatel-Lucent via air express or e-mail the files to:
[email protected].

13.

Either ship the completed Alcatel-Lucent Required ECP

Retrofit Information (customer contact information) to
Alcatel-Lucent with the ECD database dump tapes or e-mail
the contact information to: [email protected].

14.

Load and execute the Release 24.0 Pre-Retrofit System

Check tool.

15.

Execute the Release 24.0 OSR tool.

Note that you will repeatedly execute the OSR tool before
the day of the retrofit.

PRELIMINARY

16.

Execute the Release 24.0 RNC OSR tool.

Note that you will repeatedly execute the RNC OSR tool
before the day of the retrofit

3 days before

17.

Apply and make official the ECP retrofit tools.

18.

Re-execute the Release 24.0 Pre-Retrofit System Check tool.

11-22

Table 11-1

Generic retrofit

Timeline of Retrofit Activities

Time before,
on, or after
the night of
retrofit
2 days before

1 day before

(continued)

Stage

Activity

19.

Perform a full ECP system backup.

20.

Audit the ECP file system.

21.

Verify receipt of the required retrofit materials from

Alcatel-Lucent.

22.

Preload the Release 24.0 OMP software.

23.

Upgrade the SUA package on the OMP.

24.

Load the AP/MM-AP software.

25.

Install the AP/MM-AP software via the SUA.

26.

Verify that the OMP is booted off Disk 0.

27.

Preload the OMP Supplemental Software.

28.

Collect the AMA data.

PRELIMINARY

Software configuration management

The OSR process and RNC OSR process should now be

complete.

Morning of
night of retrofit

29.

Verify that the MHDs are ready for retrofit.

30.

Inhibit the crontab process.

31.

Compare the MHDs to each other.

32.

Perform a full OMP system backup.

33.

Inhibit the Routine Exerciser (REX).

34.

Read the generic tapes (text and ECD).

35.

Read the ODD that was created by the OSR tool.

36.

Evolve the online subscriber databases.

37.

Perform the System Update Procedure (SUPR).

38.

Copy the 1X RNC database that was generated by the RNC

OSR tool from the OMP to the OAM Proxy APs.

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
11-23
Issue 14, September 2009
See notice on first page

PRELIMINARY

Software configuration management

Table 11-1

Timeline of Retrofit Activities

Time before,
on, or after
the night of
retrofit
Night of
retrofit

Generic retrofit

(continued)

Stage

Activity

39.

Collect the AMA data.

40.

Prepare the CDN-IIIs for prepump.

41.

Evolve the online subscriber databases.

42.

Prepump the CDN-IIIs.

43.

Prepare the MM-AP DBMS application.

44.

Activate the Release 24.0 AP software on the APs and the

Release 24.0 MM-AP software on Group 1 of the MM-APs
via SUA.

45.

Set the ECP application parameters for MM-APs.

46.

Run the DCI communication script.

47.

Boot (54) the ECP to Release 24.0.

The Group 1 of the MM-APs, and RNC-APs boot to Release
24.0 automatically.

PRELIMINARY

1 day after

48.

Activate the Release 24.0 MM-AP software on Group 2 of

the MM-APs.

49.

Restore the crontab process in Release 24.0.

50.

Restore CU 0 to Standby.

51.

Install the Release 24.0 OMP software and OMP

Supplemental Software.

52.

Back up the databases.

53.

Allow the REX program.

54.

Perform the GIU activities for MM-APs.

11-24

Golden
image restoration (B-PCF)
...................................................................................................................................................................................................................................
Introduction

In Release 30.0 and beyond, the service provider is allowed to integrate the golden
image restore capability onto the B-PCF disks.

PRELIMINARY

Software configuration management

Disk recovery

This golden image restore capability will allow a disk to be recovered using software,
and eliminate the need to return the disk to the factory.
Important! Restoring a failed B-PCF using the Golden Image packages is outside
the scope of this document. The restoration of a failed B-PCF needs to be done
with the support of the Alcatel-Lucent Technical support team.
Scope

This document will cover the installation of the FBPregldn package onto the B-PCF
cards.
The installation procedures will be performed using the SUAGUI, and can be
performed during any maintenance window.
Important! Note that these packages should only be installed on the B-PCF when
the B-PCF is in a healthy state.
Hardware and software requirements

This feature doesnt require any special hardware outside of the typical 1X RNC
configuration, and requires Release 30.0 or beyond software.
Disk space

The Golden Image packages occupy around 630 MB disk space on the B-PCF /var file
system. So it is necessary that the B-PCFs have this required extra space available
before installing the Golden Image packages.
Procedures

The following procedures will be necessary to obtain and install the Golden Image
packages:
To download cpio file from Online Customer Support Site (OLCS) (p. 11-26).
To load and install B-PCF golden image package (p. 11-35).

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
11-25
Issue 14, September 2009
See notice on first page

PRELIMINARY

Software configuration management

To download cpio file from Online Customer Support Site

(OLCS)
...................................................................................................................................................................................................................................
Purpose

To download the 2_0_RNCGLD_2.cpio file from the OLCS web site.

Reason to perform

The B-PCF golden packages are contained in the 2_0_RNCGLD_2.cpio file.

Alcatel-Lucent OLCS account

To access the OLCS web site, you will need an Alcatel-Lucent Account, which
includes a user login ID and password to the Alcatel-Lucent Customer Center web site.
To obtain an Alcatel-Lucent Account, browse to the following web site and complete
the online registration form:
(http://www.alcatel-lucent.com)
Alcatel-Lucent will provide an Alcatel-Lucent Account to you within 48 hours.
Procedure

Access your Alcatel-Lucent as follows:

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

Launch an Internet browser and browse to the following URL:

(https://download.support.lucent.com)
Result: You are directed to Alcatel-Lucent OLCS login page.
...................................................................................................................................................................................................

PRELIMINARY

Enter your user name and password, and select Submit.

11-26

To download cpio file from Online Customer Support Site

(OLCS)

Result: The browser navigates to the following page:

PRELIMINARY

Software configuration management

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

In the left hand column click on Downloads.

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
11-27
Issue 14, September 2009
See notice on first page

PRELIMINARY

Software configuration management

To download cpio file from Online Customer Support Site

(OLCS)

Result: The browser navigates to the following page:

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

PRELIMINARY

In the left hand column click on D-G.

11-28

To download cpio file from Online Customer Support Site

(OLCS)

Result: The browser navigates to the following page:

PRELIMINARY

Software configuration management

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

Click on CDMA 3G-1X.

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
11-29
Issue 14, September 2009
See notice on first page

PRELIMINARY

Software configuration management

To download cpio file from Online Customer Support Site

(OLCS)

Result: The browser navigates to the following page:

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

PRELIMINARY

Under Documentation and downloads click on Downloads: Electronic Delivery.

11-30

To download cpio file from Online Customer Support Site

(OLCS)

Result: The browser navigates to the following page:

PRELIMINARY

Software configuration management

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

In the Please select the item that you wish to download drop-down box select
Miscellaneous Files (as shown) and click on Next.

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
11-31
Issue 14, September 2009
See notice on first page

PRELIMINARY

Software configuration management

To download cpio file from Online Customer Support Site

(OLCS)

Result: The browser navigates to the following page:

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

PRELIMINARY

In the Please select the item that you wish to download drop-down box select
1xRNC_BPCFregldn_2 (as shown) and click on Next.

11-32

To download cpio file from Online Customer Support Site

(OLCS)

Result: The browser navigates to the following page:

PRELIMINARY

Software configuration management

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

In the Download Directory box enter the destination directory as the EESD directory
on the OMP (as shown) and click on Download.

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
11-33
Issue 14, September 2009
See notice on first page

PRELIMINARY

Software configuration management

To download cpio file from Online Customer Support Site

(OLCS)

Result: The browser navigates to the following page where the download continues

until successful completion:

END OF STEPS

PRELIMINARY

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

11-34

To
load and install B-PCF golden image package
...................................................................................................................................................................................................................................
Purpose

To load and install the B-PCF golden image package.

Reason to perform

PRELIMINARY

Software configuration management

To integrate the golden image restore capability onto B-PCF disks.

Procedure

Start the OAM GUI as follows:

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

Login to the OMP and start the oamgui as follows:

/opt/sua/bin/oamgui

Result: The following window eventually appears:

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

Click on the SUA button and select MM-AP (as shown).

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
11-35
Issue 14, September 2009
See notice on first page

PRELIMINARY

PRELIMINARY
PRELIMINARY

Software configuration management

To load and install B-PCF golden image package

11-36

To load and install B-PCF golden image package

Result: The oamgui navigates to the following window:

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
11-37
Issue 14, September 2009
See notice on first page

PRELIMINARY

Important! The above example shows only RNCs and associated RNCM/TCS APs.
Your system will likely include APs unrelated to the 1xRNC and thus would not
benefit from this package. Be sure to only select RNCs and the associated APs that
will benefit from the distribution of this package.

PRELIMINARY

Software configuration management

PRELIMINARY

Software configuration management

To load and install B-PCF golden image package

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

Click on the LED button.

Result: A window with the available products is displayed, as shown in the

following example:

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

Select the RNCGOLD product (as shown), and click on the Load button.
Result: The BPCF regolden package is extracted to the OMP and the following

window is displayed.

PRELIMINARY

Note that if an error is displayed, contact Alcatel-Lucent Technical Support.

11-38

To load and install B-PCF golden image package

Installing the regolden image package

Before the user initiates the installation of the Golden image, it is assumed that the
software was previously committed on the active BPCF, during the previous generic
retrofit. Do not proceed if the software has not previously been committed.
Proceed as follows:

PRELIMINARY

Software configuration management

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

Click on the Install tab of the oamgui.

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
11-39
Issue 14, September 2009
See notice on first page

PRELIMINARY
PRELIMINARY

Software configuration management

To load and install B-PCF golden image package

Result: The Install tab of the oamgui is displayed as shown in the following

example:

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

Click on the Precheck button to verify the health of the BPCFs. Proceed to the next
step only if there are no major errors.

11-40

To load and install B-PCF golden image package

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

Select the RNCGLD software in the Software Version scroll window and click on the
Install button.
Result: After the installation completes, the status of the install step is displayed as

shown in the following example:

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
11-41
Issue 14, September 2009
See notice on first page

PRELIMINARY

Software configuration management

PRELIMINARY
PRELIMINARY

Software configuration management

To load and install B-PCF golden image package

Note that if an error is displayed, contact Alcatel-Lucent Technical Support.

11-42

12
Configuring
ATM connectivity
in RNCs SHO universe

PRELIMINARY

To provide descriptive and configuration information regarding the ATM connectivity

for the RNCs in a SHO universe.
Contents
ATM SHO universe connection type considerations

12-2

Adding a new remote subnet to RNC

12-6

Removing a subnet from the RNC

12-12

Changing intra-subnet PVC connection types

12-18

Moving an RNC from one local subnet to another

12-23

Changing a subnets VCC VPI

12-28

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
12-1
Issue 14, September 2009
See notice on first page

PRELIMINARY

Configuring ATM connectivity in RNCs SHO universe

ATM
SHO universe connection type considerations
...................................................................................................................................................................................................................................
Introduction

The ATM SHO universe is a collection of switching elements interconnected by an

ATM network. These switching elements can be either 5ESS Packet Switching Units
(PSUs), or an RNC.
Propietary addressing scheme

The ATM SHO universe uses a Alcatel-Lucent propietary addressing scheme that
involves the use of Community Addresses (CAs) and subnetworks (subnets). Each
5ESS PSU in the SHO universe requires a unique CA. Each RNC in the SHO universe
provides 5E Gateways (5EGWs). Each 5EGW also requires a a unique CA.
Note that an RNC 5EGW is also sometimes referred to as a PSU GW.
Subnets

A subnet allows for the use of up to 254 CAs. Therefore, with one local subnet, an
RNC 5EGW in the SHO universe is limited to communicating with 253 other CAs.
Each RNC can have up to four subnets configured (one local, three remote) in the
SHO universe, which allows each RNC 5EGW to communicate with up to 1,015
CAs.That is because each individual subnet can be configured with up to 254 CAs (4 x
254=1016).
Initial installation

During an initial RNC installation, a local subnet will need to be selected via the
TPU-GUI. The system default is 0, but any other ID (1 through 3) can also be
assigned.
Remote subnets can be defined during or after RNC installation. A local subnet can
also be changed after RNC installation.
Communication

PRELIMINARY

Communication within a subnet (intra-subnet) or between subnets (inter-subnet) is

provided by means of Permanent Virtual Circuit (PVC) connection types known as
Virtual Path Connections (VPCs) and Virtual Channel Connections (VCCs).
Communication within a subnet (intra-subnet) can be VPC-based, VCC-based, or
mixed. However, communication between subnets (inter-subnet) can only be
VPC-based.

12-2

ATM SHO universe connection type considerations

VPC-only network

Connectivity in a VPC-only network is all VPC-based (Figure 12-1, Example of

connectivity with VPCs (p. 12-3)) and is therefore limited by the 254 CA maximum
constraint.
Virtual Path Identifier

A Virtual Path Identifier ( VPI) is used to provide VCC-connectivity between CAs in a

local subnet, and CAs in remote subnets. Therefore, a VPI is not necessary in a
VPC-only network.

PRELIMINARY

Configuring ATM connectivity in RNCs SHO universe

Figure 12-1 Example of connectivity with VPCs

VCC network

A VCC network is not limited by a 254 CA maximum constraint, and has the
capability to support both VPC-and VCC-based connections simultaneously.
Connectivity

5ESS PSUs or RNC 5EGWs can be connected directly by using VCCs between
subnets (inter-subnet), and VCCs and/or VPCs within a subnet (intra-subnet). See also
Figure 12-2, Example of connectivity with VCCs and VPCs (p. 12-4).
Virtual Path Identifier

To support VCC-connectivity in a local and remote subnet arrangement, each subnet

must be provisioned with a VPI. The VPIs are assigned in the range 510 through 528.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
12-3
Issue 14, September 2009
See notice on first page

PRELIMINARY

Note that if both VCC and VPC are provisioned within a local subnet, then the local
subnet will have to be provisioned with a VPI.

PRELIMINARY

Configuring ATM connectivity in RNCs SHO universe

ATM SHO universe connection type considerations

Figure 12-2 Example of connectivity with VCCs and VPCs

VPC-default

When a 5EGW is grown-in, the default value for its connections to all intra-subnet
CAs is VPC. These connections can be changed to VCC when the 5EGW is:

Grown-in during first-time installation of an RNC using the First Time wizard of
the TPU GUI.

Subsequently grown-in, using the GICC Growth Wizard of the TPU-GUI.

Subsequently grown-in, using the PSU GW (5EGW) Growth wizard of the

TPU-GUI.

Subsequently changed after growth, via the CA Override screen of the TPU-GUI.

Note, that if a customer is retrofitting from one release to the next, the connection
types will remain as they were defined in the previous release.

PRELIMINARY

VPC-to-VCC transition

To support customer network conversion from VPC-to-VCC, RNC software allows a

mismatch (intra-subnet only) of connection types on the forward and reverse channels
between two CAs.

12-4

ATM SHO universe connection type considerations

Outgoing (intra-subnet) connections

To support VPC-based users, and also to support customer network conversions from
VPC to VCC, customers are allowed to provision outgoing (forward direction)
intra-subnet ATM PVC connection types (VPC or VCC) from the RNC to every
possible CA in the local subnet.

PRELIMINARY

Configuring ATM connectivity in RNCs SHO universe

Outgoing (inter-subnet) connections

For inter-subnet connections, it is assumed that communication with all CAs in remote
subnets types is VCC-based, so no provisioning is required. Connections are set up
automatically by the RNC.
Incoming connections

Regarding incoming connections, the RNC will create VCC and VPC based incoming
connections from all CAs in the local subnet. It will also create VCC based incoming
connections for all CAs in remote subnets to the RNC. No provisioning is required.
Procedures

The procedures that are associated with configuring ATM connectivity in SHO universe
are listed as follows:
Adding a new remote subnet to RNC (p. 12-6)
Removing a subnet from the RNC (p. 12-12)
Changing intra-subnet PVC connection types (p. 12-18)
Moving an RNC from one local subnet to another (p. 12-23)
Changing a subnets VCC VPI (p. 12-28)

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
12-5
Issue 14, September 2009
See notice on first page

PRELIMINARY

Configuring ATM connectivity in RNCs SHO universe

Adding
a new remote subnet to RNC
...................................................................................................................................................................................................................................
Purpose

To add a new remote subnet to the RNC.

Reason to perform

To provide new connectivity between the RNC and another PSU that is on a different
subnet.
Non-service affecting

Because a new remote subnet is being added, there are no active calls in the RNC that
are using the new subnet.
Before you begin

Set up the ATM network to support the routing of ATM packets to CAs in the subnet.
Based on the changes made to the ATM switch translations to support the new subnet,
choose a new VPI (in the range 510 through 528) to represent the new remote subnet
that is to be configured.
Note that the VPI should match the VPI provisioned for this subnet in the customer
ATM network.
Procedure

To add and configure the new subnet, proceed as follows:

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

Obtain access to the TPU-GUI either by:

Direct access method. See also Accessing TPU GUI (p. 6-6).
EMS. See also Logging on to Element Management System (EMS) (p. 6-5).

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

PRELIMINARY

If using EMS, at the OMP Web page you need to select 1X RNC TPU Web to
navigate to the 1X RNC TPU Web page. If using the direct access method, the same
will result. See the following example screen.

12-6

Adding a new remote subnet to RNC

PRELIMINARY

Configuring ATM connectivity in RNCs SHO universe

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

Select Configuration Data.

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
12-7
Issue 14, September 2009
See notice on first page

PRELIMINARY

Configuring ATM connectivity in RNCs SHO universe

Adding a new remote subnet to RNC

Result The GUI navigates to the RNC Configuration Data page (see the following

example screen).

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

PRELIMINARY

Select the Global Config Data button.

12-8

Adding a new remote subnet to RNC

Result The GUI navigates to the Global Configuration Data page (see the

following example screen).

PRELIMINARY

Configuring ATM connectivity in RNCs SHO universe

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

Select the PSU Subnet & VPI Configuration link.

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
12-9
Issue 14, September 2009
See notice on first page

PRELIMINARY

Configuring ATM connectivity in RNCs SHO universe

Adding a new remote subnet to RNC

Result The GUI navigates to the PSU Subnet and VPI Congfiguration page (see

the following example screen).

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

Change the VPI for the new subnet (identified by the new subnet ID) from Not
Provisioned to the VCC VPI that has been previously chosen for the new subnet.
...................................................................................................................................................................................................

PRELIMINARY

Select the Submit button.

12-10

Adding a new remote subnet to RNC

Result A Confirmation pop-up similar to the following example appears:

PRELIMINARY

Configuring ATM connectivity in RNCs SHO universe

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

Select OK.
Result The following occurs:

The RNC database is updated to include the new subnet and VPI.

A dynamic data update will occur providing the new data to the TPU shelf on
each RNC.

ATM connections will be created to support incoming and outgoing VCC-based

traffic from all possible CAs in the new subnet, to all PSU gateways (CAs)
provisioned on each RNC. Note that the new VPI should match the VPI
provisioned for this subnet in the customers ATM network.

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
12-11
Issue 14, September 2009
See notice on first page

PRELIMINARY

Configuring ATM connectivity in RNCs SHO universe

Removing
a subnet from the RNC
...................................................................................................................................................................................................................................
Purpose

To remove a remote subnet from the RNC.

Reason to perform

A subnet was erroneously added or CDMA 1X RNC related resources are actually
being degrown.
Service affecting

When a subnet is submitted for removal, all active VCC calls using this subnet will be
dropped. If a valid subnet VPI is removed, then this procedure must be timed in
conjunction with the customers ATM network changes to remove the subnet on the
ATM switch(es) and the 5ESS switch(es).
Procedure

To remove a subnet from the network, proceed as follows:

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

Obtain access to the TPU-GUI either by:

Direct access method. See also Accessing TPU GUI (p. 6-6).

EMS. See also Logging on to Element Management System (EMS) (p. 6-5).

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

PRELIMINARY

If using EMS, at the OMP Web page you need to select 1X RNC TPU Web to
navigate to the 1X RNC TPU Web page. If using the direct access method, the same
will result. See the following example screen.

12-12

Removing a subnet from the RNC

PRELIMINARY

Configuring ATM connectivity in RNCs SHO universe

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

Select Configuration Data.

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
12-13
Issue 14, September 2009
See notice on first page

PRELIMINARY

Configuring ATM connectivity in RNCs SHO universe

Removing a subnet from the RNC

Result The GUI navigates to the RNC Configuration Data page (see the following

example screen).

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

PRELIMINARY

Select the Global Config Data button.

12-14

Removing a subnet from the RNC

Result The GUI navigates to the Global Configuration Data page (see the

following example screen).

PRELIMINARY

Configuring ATM connectivity in RNCs SHO universe

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

Select the PSU Subnet & VPI Configuration link.

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
12-15
Issue 14, September 2009
See notice on first page

PRELIMINARY

Configuring ATM connectivity in RNCs SHO universe

Removing a subnet from the RNC

Result The GUI navigates to the PSU Subnet and VPI Congfiguration page (see

the following example screen).

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

Change the VPI for the subnet being removed to Not Provisioned.
...................................................................................................................................................................................................

Select the Submit button.

PRELIMINARY

Result A Confirmation pop-up similar to the following example appears:

12-16

Removing a subnet from the RNC

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

Select OK.

The RNC database is updated to remove the subnet and VPI.

A dynamic data update will occur providing the new data to the TPU shelf on each
RNC.
ATM connections will be deleted to eliminate support for incoming and outgoing
VCC-based traffic from all possible CAs in the subnet, to all PSU gateways (CAs)
provisioned on each RNC.

PRELIMINARY

Configuring ATM connectivity in RNCs SHO universe

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
12-17
Issue 14, September 2009
See notice on first page

PRELIMINARY

Configuring ATM connectivity in RNCs SHO universe

Changing
intra-subnet PVC connection types
...................................................................................................................................................................................................................................
Purpose

To change the PVC connection type transmitted from a CA provisioned on the RNC to
one or more CAs in the local subnet. By default, all CAs provisioned on this RNC can
receive either VPC or VCC-based traffic.
Reason to perform

It is anticipated that the majority of connection type changes will be VPC-to-VCC to

support customer network conversions that will enable the use of subnets (CA
expansion). The flexibility for converting from from VCC-to-VPC is also provided.
Procedure

To change the PVC connection type transmitted by CAs, proceed as follows:

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

Obtain access to the TPU-GUI either by:

Direct access method. See also Accessing TPU GUI (p. 6-6).

EMS. See also Logging on to Element Management System (EMS) (p. 6-5).

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

PRELIMINARY

If using EMS, at the OMP Web page you need to select 1X RNC TPU Web to
navigate to the 1X RNC TPU Web page. If using the direct access method, the same
will result. See the following example screen.

12-18

Changing intra-subnet PVC connection types

PRELIMINARY

Configuring ATM connectivity in RNCs SHO universe

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

Select Configuration Data.

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
12-19
Issue 14, September 2009
See notice on first page

PRELIMINARY

Configuring ATM connectivity in RNCs SHO universe

Changing intra-subnet PVC connection types

Result The GUI navigates to the RNC Configuration Data page (see the following

example screen).

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

PRELIMINARY

Select the PSU VCC Override link.

12-20

Changing intra-subnet PVC connection types

Result The GUI navigates to the PSU VCC Override page (see the following

example screen).

PRELIMINARY

Configuring ATM connectivity in RNCs SHO universe

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

In the PSU GW: box, select the PSU gateway (local CA) for which you will be
changing connection types.
...................................................................................................................................................................................................

Change a PVC connection type, as follows:

To change the connection type from the PSU GW selected to a single CA in the
local subnet, highlight the CA to be changed in the VCC Connection Type: or
VPC Connection Type: box, and click on the > or < button as appropriate to move
the CA to the VCC or VPC list (as appropriate).

To change the connection type from the PSU GW selected to all CAs in the local
subnet, click on the >> or << button as appropriate to move the CAs to the VCC
or VPC list (as appropriate).

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

Click on the Save button.

Important! Note that after clicking on the Save button, a VCC inoperable
warning will be displayed, if a VPI was not previously assigned for the RNCs
local subnet, and one or more VCCs are provisioned. If that is the case, then VCC
call processing will not be possible, and VPC will remain operational.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
12-21
Issue 14, September 2009
See notice on first page

PRELIMINARY

Configuring ATM connectivity in RNCs SHO universe

Changing intra-subnet PVC connection types

Result The following occurs:

The RNC database is updated for the impacted PSU Gateways and CAs.
A dynamic data update will occur providing the new data to the TPU shelf.

Outgoing ATM connections are updated to reflect the changes made.

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

Make the same VCC overrides on the remaining PSU GWs by repeating Step 5 and
Step 6 and noting the following:

If you are only selecting particular CAs (instead of ALL CAs), you can use the
Copy button. The Copy button is used to copy the overrides of a particular PSU
GW to the current PSU GW. When you click on the Copy button, a pop up comes
up showing the list of PSU GWs which have been overridden. (If no PSU GWs are
overridden, then this popup doesnt show any PSU GWs). Select one of the PSU
GWs and click OK. Now you will see the Override values of the selected PSU GW
for the current selected PSU GW.
The Reset button (button adjacent to the Copy button) is used to undo any changes
done after the last save for the current selected PSU GW.
After all changes have been selected, save all the changes. Refer to Step 7.
The Done button returns to the RNC Configuration Data screen. It does not save
any changes on the PSU VCC Override screen.

END OF STEPS

PRELIMINARY

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

12-22

Moving
an RNC from one local subnet to another
...................................................................................................................................................................................................................................
Purpose

To relocate an RNC from one subnet to another.

Reason to perform

PRELIMINARY

Configuring ATM connectivity in RNCs SHO universe

When evolving an MSC from VPC-to-VCC and moving the MSC to a different VCC
subnet.
Service affecting

Calls to and from the RNC will be dropped.

Procedure

To change the local subnet for the RNC, proceed as follows:

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

Obtain access to the TPU-GUI either by:

Direct access method. See also Accessing TPU GUI (p. 6-6).

EMS. See also Logging on to Element Management System (EMS) (p. 6-5).

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

If using EMS, at the OMP Web page you need to select 1X RNC TPU Web to
navigate to the 1X RNC TPU Web page. If using the direct access method, the same
will result. See the following example screen.

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
12-23
Issue 14, September 2009
See notice on first page

PRELIMINARY

Configuring ATM connectivity in RNCs SHO universe

Moving an RNC from one local subnet to another

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

PRELIMINARY

Select Configuration Data.

12-24

Moving an RNC from one local subnet to another

Result The GUI navigates to the RNC Configuration Data page (see the following

example screen).

PRELIMINARY

Configuring ATM connectivity in RNCs SHO universe

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

Select the 1X RNC Information link.

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
12-25
Issue 14, September 2009
See notice on first page

PRELIMINARY

Configuring ATM connectivity in RNCs SHO universe

Moving an RNC from one local subnet to another

Result The GUI navigates to the1X RNC Information page (see the following

example screen).

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

Select the new local Subnet ID (any number 0 through 3) for the RNC from the PSU
Subnet ID for RNC # pull down box.
where # is the number (1-15) of the RNC whose local subnet is being modified.
...................................................................................................................................................................................................

Select the Submit button.

Note that upon submittal of this page, a VCC inoperable warning will be displayed,
if a VPI was not previously assigned for the RNCs local subnet.

PRELIMINARY

Result The following occurs:

The RNC database is updated with the new local subnet ID.
A dynamic data update will occur providing the new data to the TPU shelf.

All VCC-based connections (incoming and outgoing) are updated to use the
new VPI for the local subnet ID.

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

Repeat for all RNCs.

12-26

Moving an RNC from one local subnet to another

Note that all RNCs in the MSC must use the same local subnet ID.
END OF STEPS
...................................................................................................................................................................................................

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
12-27
Issue 14, September 2009
See notice on first page

PRELIMINARY

Configuring ATM connectivity in RNCs SHO universe

PRELIMINARY

Configuring ATM connectivity in RNCs SHO universe

Changing
a subnets VCC VPI
...................................................................................................................................................................................................................................
Purpose

To change a subnets VCC VPI.

Reason to perform

Reasons for changing a subnets VCC VPI may include:

To evolve the local subnet from being all VPC-based to support VCC-based
connections as well, by changing the VPI from Not Provisioned to an actual VPI
value.

Simply to change the VPI for a subnet.

An erroneous VPI may have been previously provisioned for a remote or local
subnet.
Important! The new VPI must match the VPI that is provisioned for this subnet in
the customers ATM network.

Service affecting

When a subnets VCC VPI is submitted for change, all active VCC calls using the
subnet VPI that is being modified will be dropped. If a valid subnet VPI is changed,
then this procedure must be timed in conjunction with the customers ATM network
changes for the changed subnet on the ATM switch(es) and the 5ESS switch (es). This
procedure would most likely be performed in a maintenance window when the least
amount of traffic would be affected.
Procedure

To change a subnets VCC VPI, proceed as follows:

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

Obtain access to the TPU-GUI either by:

Direct access method. See also Accessing TPU GUI (p. 6-6).
EMS. See also Logging on to Element Management System (EMS) (p. 6-5).

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

PRELIMINARY

If using EMS, at the OMP Web page you need to select 1X RNC TPU Web to
navigate to the 1X RNC TPU Web page. If using the direct access method, the same
will result. See the following example screen..

12-28

Changing a subnets VCC VPI

PRELIMINARY

Configuring ATM connectivity in RNCs SHO universe

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

Select Configuration Data.

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
12-29
Issue 14, September 2009
See notice on first page

PRELIMINARY

Configuring ATM connectivity in RNCs SHO universe

Changing a subnets VCC VPI

Result The GUI navigates to the RNC Configuration Data page (see the following

example screen).

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

PRELIMINARY

Select the Global Config Data button.

12-30

Changing a subnets VCC VPI

Result The GUI navigates to the Global Configuration Data page (see the

following example screen).

PRELIMINARY

Configuring ATM connectivity in RNCs SHO universe

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

Select the PSU Subnet & VPI Configuration link.

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
12-31
Issue 14, September 2009
See notice on first page

PRELIMINARY

Configuring ATM connectivity in RNCs SHO universe

Changing a subnets VCC VPI

Result The GUI navigates to the PSU Subnet and VPI Congfiguration page (see

the following example screen).

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

Change the VPI for the subnet by changing the VPI in the VPI (510-528) column pull
down menu.
...................................................................................................................................................................................................

PRELIMINARY

Select the Submit button.

12-32

Changing a subnets VCC VPI

Result A Confirmation pop-up similar to the following example appears:

PRELIMINARY

Configuring ATM connectivity in RNCs SHO universe

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

SelectOK
Result The following occurs:

The RNC database is updated with the new VPI.

A dynamic data update will occur providing the new data to the TPU shelf.

All incoming and outgoing ATM connections are updated to use the new VPI.
Note that the new VPI should match the VPI provisioned for this subnet in the
customers ATM network.

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

To ensure that there is no mismatch in the VPI/VCI configuration, it is recommended

that an enhanced loopback test be performed. See also Loopback Testing (p. 9-59).
END OF STEPS
...................................................................................................................................................................................................

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
12-33
Issue 14, September 2009
See notice on first page

PRELIMINARY

13
Automatic
Protection Switching
(APS)

PRELIMINARY

To provide descriptive and configuration information regarding the use of APS.

Contents
5EGW Redundancy/Automatic Protection Switching (APS)

13-2

APS standard for RNC OC3 facilities

13-4

Preparing to enable APS

13-5

Changing APS mode

13-9

Changing APS mode

13-10

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
13-1
Issue 14, September 2009
See notice on first page

PRELIMINARY

Automatic Protection Switching (APS)

5EGW
Redundancy/Automatic Protection Switching (APS)
...................................................................................................................................................................................................................................
Introduction

Automatic Protection Switching (APS) is a SONET facility sparing scheme.

Line failure

When a line failure occurs, the 5E (PSU) gateway becomes completely unavailable. As
each 5E gateway becomes disabled, capacity decreases.
Solution

The solution is to protect each Community Address (CA) via the APS scheme. In this
scheme, the same CA is assigned to two 5EGWs that form an APS pair.
When a fault occurs or an APS command is issued via the GUI or CLI, a 5EGW will
protection switch to its mate without impacting service.
The forward traffic is bridged to both 5E gateways from a CICC. Similarly, the ATM
switch sends the reverse traffic to both 5EGWs; however, only the active gateway will
forward the traffic to the CICC in the reverse direction. See also Figure 13-1, APS
architecture (p. 13-2).

PRELIMINARY

Figure 13-1 APS architecture

13-2

5EGW Redundancy/Automatic Protection Switching (APS)

Working line

The working line/5EGW is resident in TPU shelf 1 (top shelf). It has been designated
as the working 5EGW in this mated 5EGW pair.
Protection line

The protection line/5EGW is resident in TPU shelf 2 (bottom shelf). It has been
designated as the protection 5EGW in its mated 5EGW pair. The protection line/5EGW
is responsible for communicating with the connected ATM switch via the K1 and K2
bytes.

PRELIMINARY

Automatic Protection Switching (APS)

APS channel protocol

The signaling between the RNC and ATM switch is done through the utilization of the
K1 and K2 Sonet overhead bytes. The protection line is responsible for communicating
with the ATM switch via these overhead bytes. The K1 and K2 bytes are used to
exchange APS requests and acknowledgements for protection switching actions.
Working channel

The working channel is the 5EGW in an APS mated pair that is processing traffic at a
given time. It serves as the active 5EGW in the mated pair while its 5EGW mate
serves as the standby 5EGW in the pair.
Working and protection roles

Note that the working and protection roles are static. They do not indicate which
5EGW in the mated pair is processing traffic at any given time. It is the active/standby
assignment that is dynamic and indicates which 5EGW is processing traffic.

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
13-3
Issue 14, September 2009
See notice on first page

PRELIMINARY

Automatic Protection Switching (APS)

APS
standard for RNC OC3 facilities
...................................................................................................................................................................................................................................
Introduction

The APS characteristics chosen for 5EGW facilities are the APS 1+1 architecture and
non-revertive recovery. The RNC supports both unidirectional and bidirectional
switching modes..
Non-revertive recovery mode

With the non-revertive mode of recovery, a switch to the protection line is maintained
even after:

The working line has recovered from the failure that caused the switch.

A user requested switch or lockout command is cleared.

Note that some higher priority local or global requests can still force the system
switching back to the working line.
Unidirectional mode

The unidirectional switching mode permits both ends (RNC and ATM switch) to switch
independently of one another. For example, one end can be receiving the working
channel from the working line while the other end is receiving the working channel
from the protection line.
Switching either occurs automatically (in response to a failure detected on an incoming
line) or in response to (local) technician commands.
Disadvantage

The disadvantage of this approach is that each end may select different lines at a given
time. In that case, the forward and reverse traffic will follow different paths and may
have different delays. In addition, it is more complex from the technician perspective
requiring that each end be monitored seperately.
Default

The unidirectional switching mode on the RNC is the default for APS.
Bidirectional mode

PRELIMINARY

In the bidirectional switching mode both ends will attempt to switch together. Ideally,
at any given time, both ends will be selecting from the same line.
Optional

The bidirectional switching mode is optional for APS.

13-4

Preparing
to enable APS
...................................................................................................................................................................................................................................
Introduction

Enabling APS requires cabling changes from the ATM switch to the RNC GICCs, and
the use of the TPU GUI APS Migration wizard.

PRELIMINARY

Automatic Protection Switching (APS)

Capacity implications

When APS is enabled, the 5EGW ports (1 and 2) on a GICC card in the upper TPU
shelf, are protected by the mated 5EGW ports (1 and 2) on the GICC card in the lower
TPU shelf. Therefore, the maximum Community Address (CA) capacity (one per each
5EGW) is reduced from 16 to 8 per RNC (two 5EGWs per a maximum of four GICC
cards).
Unused OC3 ports

Any unused OC3 ports on a GICC that were not previously provisioned as a 5EGW
should already be in the locked state. You can verify the state of GICC ports via the
TPU network elements page on TPU GUI.
CA conflicts

When APS is enabled, the same CA is shared between both 5EGWs in the mated pair
(see Figure 13-2, Mated pairs when APS is enabled (p. 13-6)). Therefore, a CA
conflict will occur when APS is enabled, if a CA was previously assigned to each
5EGW in a to be mated pair.
You will not be able to enable APS with a CA conflict present.

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
13-5
Issue 14, September 2009
See notice on first page

PRELIMINARY

Automatic Protection Switching (APS)

Preparing to enable APS

Figure 13-2 Mated pairs when APS is enabled

Eliminate CA conflict

To eliminate a CA conflict you must de-provision one of the ports in the to be

5EGW mated pair. Note that it does not matter if you shutdown (lock) and degrow a
5EGW on the GICC in the upper, or lower shelf to eliminate a CA conflict.

PRELIMINARY

Refer to Degrowing 5E gateway on used OC3 port (p. 15-116) for details on shutting
down (locking), and degrowing a 5EGW.

13-6

Preparing to enable APS

RNC-to-ATM switch cabling

Prior to the start of the actual APS enable procedure, cabling between:

The working 5EGW ports on the GICCs, and the working OC3 ports of the ATM
switch needs to be completed.

The protection 5EGW ports on the GICCs and the protection OC3 ports of the
ATM switch needs to be completed.

PRELIMINARY

Automatic Protection Switching (APS)

See Figure 13-3, Cable configuration necessary prior to APS enable (p. 13-7) for a
typical high-level connection diagram using the SC-GICC as an example.
Important! After cabling is completed, SONET level alarms will be raised at the
ATM switch for any OC3 ports connected to any 5EGW ports that are not yet
provisioned (UNUSED) at this point.This is to be expected.
Figure 13-3 Cable configuration necessary prior to APS enable

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
13-7
Issue 14, September 2009
See notice on first page

PRELIMINARY

Automatic Protection Switching (APS)

Preparing to enable APS

APS provisioning on ATM switch

Ensure that all OC3 ports physically connected to the RNC GICC 5EGWs are
provisioned to match the RNC APS provisioning. That is:

1+1 architecture

Unidirectional or bidirectional

Non-revertive operation
Important! APS-related alarms will occur on the ATM switch for unprovisioned
(UNUSED) OC3 ports prior to enabling APS on the RNC.

Enabling or disabling APS

PRELIMINARY

Enabling or disabling APS are services that will be performed by Alcatel-Lucent.

Contact your Alcatel-Lucent representative for details.

13-8

Changing
APS mode
...................................................................................................................................................................................................................................
Introduction

At some point in time the Service Provider may find it necessary to change the APS
mode.

PRELIMINARY

Automatic Protection Switching (APS)

APS migration wizard

Changes to the APS mode (unidirectional to bidirectional or vice versa) are

accomplished via the Basic APS Parameters screen of the APS Migration Wizard.
Procedures

The procedure for changing the APS mode is listed as follows:

Changing APS mode (p. 13-10)

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
13-9
Issue 14, September 2009
See notice on first page

PRELIMINARY

Automatic Protection Switching (APS)

Perform this procedure to change the APS swithing mode on the RNC.
Reason to perform

The Service Provider has determined that the APS switching mode should change.
Required interface

The TPU GUI will be required.

Procedure

Perform the following procedure to change the APS mode on the RNC .
...................................................................................................................................................................................................

Obtain access to TPU GUI either by:

Direct access method. See also Accessing TPU GUI (p. 6-6).

EMS. See also Logging on to Element Management System (EMS) (p. 6-5).

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

PRELIMINARY

If using EMS, at the OMP Web page you need to select 1X RNC TPU Web to
navigate to the 1X RNC TPU Web page. If using the direct access method, the same
will result. See the following example screen.

13-10

Changing APS mode

PRELIMINARY

Automatic Protection Switching (APS)

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

On the 1X RNC TPU Web page select Configuration Data.

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
13-11
Issue 14, September 2009
See notice on first page

PRELIMINARY

Automatic Protection Switching (APS)

Changing APS mode

Result The GUI navigates to the RNC Configuration Data page (see example

screen).

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

PRELIMINARY

On the RNC Configuration Data page under Wizards select APS Migration Wizard.

13-12

Changing APS mode

Result The GUI navigates to the APS Migration Wizard - Basic APS Parameters

page (see example screen that follows).

PRELIMINARY

Automatic Protection Switching (APS)

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

Select either Bidirectional or Unidirectional for the RNC APS Capability: field. In
this example Unidirectional would be selected.
...................................................................................................................................................................................................

Click on the Next button.

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
13-13
Issue 14, September 2009
See notice on first page

PRELIMINARY

Automatic Protection Switching (APS)

Changing APS mode

Result The GUI navigates to the APS Migration Wizard - Summary Page (see the

following example).

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

Click on the Submit button.

PRELIMINARY

Result The following occurs:

An RNC dynamic data update is performed.

APS switching mode is changed.

The screen returns to RNC Configuration Data page.

13-14

Changing APS mode

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

After the dynamic data update is completed (approximately two minutes) you can
verify the changes via the TPU GUI APS Status page, or via the TPU CLI command,
GET:RNC, GICC command.
END OF STEPS
...................................................................................................................................................................................................

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
13-15
Issue 14, September 2009
See notice on first page

PRELIMINARY

Automatic Protection Switching (APS)

PRELIMINARY

Configuring IPSHO connectivity

PRELIMINARY

To provide descriptive information regarding IP connectivity for the RNCs in a SHO

universe.
Contents
IPSHO connectivity

14-2

Simultaneous support of IP and ATM SHO

14-5

IPSHO GICC IP addressing

14-6

IPSHO traffic handling

14-8

IPSHO configuration

14-9

Change cluster ID of a single MSC

14-12

Integrate IPSHO enabled RNC and its neighbors

14-16

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
14-1
Issue 14, September 2009
See notice on first page

PRELIMINARY

Configuring IPSHO connectivity

IPSHO
connectivity
...................................................................................................................................................................................................................................
Introduction

The IPSHO feature allows the support of simultaneous ATM and IP connectivity for
every ATM capable CA.
Description

Figure 14-1, IP SHO network architecture (p. 14-2) shows a network overview of the
IPSHO network underlying a generalized IP network.

PRELIMINARY

Figure 14-1 IP SHO network architecture

The major components are:

IPSHO GW

Multilayer Switches
IP Wide Area Network (WAN)

14-2

IPSHO connectivity

New services

The IPSHO feature introduces two new services on the RNC:

IPSHO GW
IP Address Manager (IPAM)

IPSHO GW

PRELIMINARY

Configuring IPSHO connectivity

The traffic processing of the IPSHO GICC is performed by the IPSHO GW software
components. The key function of the IPSHO GW is the Soft Handoff Routing Function
(SHORF), which provides the selection of routes (ATM or IP) and the new iPS Packet
Bus Header (PBH) processing.
The IPSHO GW is also responsible for management of the pair wise connectivity
between the local CAs and the remote far CAs. In addition, the IPSHO GICC also
provides other necessary OAM functions including the Integrity and performance
monitoring, overload control, VSRP IP service management, and service measurements
required by the feature.
IPSHO GW on RNC supports the following two types of traffic:

Channel Element (CE) to Frame Selector traffic (CE-FS Traffic). This type of
traffic is marked as high priority traffic by the RNC.
The CE-FS traffic includes the following scenarios:

Soft Handoff traffic from/to another RNC/PSU, including traffic from IPBH in
the case of overflow.

IPBH traffic from/to another RNC

Traffic to /from non-IPBH capable Cells (such as SII cells) through PSUs.
OAM Traffic, including both IPAM Messages and CA connectiviry management
Messages between RNC and RNC/PSU for IPSHO.

IPAM

IPAM is a control plane function that provides the capability of discovery and
management of neighbor PSU/RNC and the IPSHO GW (IP Capable CA) IP addresses
of the local RNC, and the remote PSUs/RNCs. It is also responsible for maintaining
the synchronization of the CA-IP map between the two IPSHO GICCs and the
RNCDB permanent storage.
IPAM support two different modes of operation:

Learning Mode Disabled (LMD)

Learning Mode Enabled (LME)

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
14-3
Issue 14, September 2009
See notice on first page

PRELIMINARY

An LME mode IPAM can dynamically discover any new neighboring RNCs/PSUs that
are in the SHO area defined by the cluster list. A LMD mode IPAM will rely solely on
the manually entered configuration for its neighbor lists.

PRELIMINARY
PRELIMINARY

Configuring IPSHO connectivity

IPSHO connectivity

In both modes, the IPAM will be able to learn the remote CA-IP addresses and their IP
processing capability flags.

14-4

Simultaneous
support of IP and ATM SHO
...................................................................................................................................................................................................................................
Introduction

In the case that both ATM and IP SHO are supported, the IPSHO GW will support a
subset or all of the ATM capable CAs. However, there should not be any additional
IP-only CAs existing on the IPSHO GW in this mode of operation

PRELIMINARY

Configuring IPSHO connectivity

Transitioning to IPSHO

The IPSHO feature also provides the capability to completely transition SHO to IP on
the RNC, after which the 5EGW can de degrown completely.
Simultaneous IP and ATM SHO

Figure 14-2, Simultaneous support of IP and ATM SHO (p. 14-5) shows the network
architecture for supporting simultaneous IP and ATM SHO. Note that the IPSHO
feature will enable the RNC to handle all the different call leg scenarios illustrated in
the diagram.
Figure 14-2 Simultaneous support of IP and ATM SHO

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
14-5
Issue 14, September 2009
See notice on first page

PRELIMINARY

Configuring IPSHO connectivity

IPSHO
GICC IP addressing
...................................................................................................................................................................................................................................
Introduction

IP addresses are required on the IPSHO GICC, and their associated services and
processors.
Addressing scheme

Figure 14-3, IP SHO IP Addressing (p. 14-6) illustrates the IP addresses required on
the IPSHO GICC, and their associated services and processors.

PRELIMINARY

Figure 14-3 IP SHO IP Addressing

This addressing scheme allows for the simplification of provisioning for operators by
requiring a single IP address for IPAM and IPSHO GW on the external network.
The traffic handled by IPAM and IPSHO GW are differentiated by different UDP ports
and message types in the case of OAM/IPAM messages.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

14-6

IPSHO GICC IP addressing

IP addresses

A total of ten IP addresses are needed. Three of the addresses are on the external
network space and seven are on the internal LAN address space.
Address 1

The External IPSHO GW Service IP Address is the address used by the far RNC/PSU
to communicate with any of the local CAs of the IPSHO GW, and the IPAM in the
local RNC.

PRELIMINARY

Configuring IPSHO connectivity

This IP address only exists on the IPSHO GICC that has the active IPSHO GW, which
will float to the mate GICC upon switch of activity. IPAM traffic will have a UDP
port of 55002, while the IPSHO traffic will have a UDP port of 55000.
For traffic that is destined to IPAM on the GICC host, the NP will use the hosts Mac
address to forward it to the GICC Host.
Address 2 and 7

The External port IP address on IPSHO GICC is the address that the IPSHO GICC
uses to ARP to the 1st hop router for connectivity. This is the physical address of the
IPSHO GICC external port that is provided one per each IPSHO GICC.
Address 3

The Internal IPSHO GW Service IP Address is the address used to transport IPSHO
traffic between the IPSHO GW and other functional entities such as FS, IPBTS GW,
and PSU GW.
This IP address located only on the IPSHO GICC with the active IPSHO GW. It may
also be used for CA-IP Audits between the IPAM and permanent storage.
Address 4 and 8

The IPSHO GICC Host IP addresses are the IP addresses the IPSHO GICC uses for
status reports and audits to TCS and RNC-M.
This is also used for intercommunication between the two IPSHO GICC and includes
VSRP messages, CA_IP map audits and updates. This is the host address and is
provided one per each IPSHO GICC.
Address 5, 6, 9 and 10

The IPSHO GICC internal port physical addresses are the physical addresses for the
internal port that are used for connectivity monitoring via ARP. There are two such
addresses per IPSHO GICC (one per each internal cPSB port).

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
14-7
Issue 14, September 2009
See notice on first page

PRELIMINARY

Configuring IPSHO connectivity

IPSHO
traffic handling
...................................................................................................................................................................................................................................
Introduction

IPSHO traffic handling is supported by the IPSHO GW on the NP of the active IPSHO
GICC.
Provisioning and activation

SHO traffic handling is enabled when at least one of the local CA is configured on the
IPSHO GW.
Provisioning and activation of IPSHO GW on the RNC enables the IPAM function to
create a table that contains all local CA IP and far CA IP capabilities, and
corresponding IP addresses in a soft handoff universe defined by a cluster list.
The IPAM also updates the NP with a subset of the information in its CA-IP routing
Table.
IPSHO GW

The IPSHO GW handles traffic that comes to/from the SHO network from both
internal and external interfaces. For any traffic that comes in from the internal
interfaces, which includes the reverse traffic from BHS and the forward traffic from
FSRM, the IPSH GW will look up the CA_IP information in the Routing Table.
Based on the information in the Routing Table, the traffic will either be relayed to the
PSU GW on the SC GICC, or routed to the IP SHO network.
CA connectivity management message handling

CA connectivity management messages including Loopback Test, Network Test, and

Heartbeat messages are used for testing connectivity and performance between a local
and a far CA pair.
CA_IP address management message handling

PRELIMINARY

CA-IP address management messages are handled on the host by the IPAM function.
The handling of these messages is enabled once the IPSHO GICC is properly
configured, and IPAM has been provisioned with necessary Cluster (and Neighbor list
information).

14-8

IPSHO
configuration
...................................................................................................................................................................................................................................
Introduction

The configuration of CAs, neighbor lists, and cluster IDs is required after the
integration of IPSHO service has been accomplished .

PRELIMINARY

Configuring IPSHO connectivity

Integration

The integration of the IPSHO feature (a service provided by Alcatel-Lucent) starts with
the growth of the IPSHO GICCs, and provisioning of all the required IP
addresses.Then software for RNC AP, SC GICC, and CICC, and BHS is upgraded to
support the IPSHO related OAM, service measurement, and SHO traffic routing in the
case of BHS.
During integration, the RNC will be integrated with the other RNC(s) and the FPS in
the same MSC.
Status at the end of integration

At the end of the Alcatel-Lucent provided integration:

The RNC will have Learning Mode Enabled (LME). LME will allow the technician
to change or add configurations at the FPS, and take advantage of the learning
mode to get the information propagated to the RNC.

The Global RTT will be set, which means that the RNC will be allowed to move
traffic to IP for new neighbors as soon as it learns about the far CAs, and finds that
the far CAs are traffic enabled.

Data configuration

For IPSHO there are primarily two types of data that can be configured:

Data that are configured by the technician.

Data that are typically learned (but can also be configured by the technician).

Major data groups

The major groups of these data are listed as follows:

Common Data
Local CA-IP map list

Cluster-List

Neighbor list
CA-IP map list

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
14-9
Issue 14, September 2009
See notice on first page

PRELIMINARY

Configuring IPSHO connectivity

IPSHO configuration

Common data

Common data equates to such elements as:

Office ID and Cluster ID of the RNC

Learning mode flag (enabled/disabled)

Global RTT flag for all IPAM neighbors (On means enabled for IP, Off means
enabled for ATM)

Local CA-IP map list

Local CA-IP map list. Which is a list of IP-enabled Community addresses (CAs) on
this RNC, as well as their IP addresses, and their Traffic states:

Growth (no bearer, no OAM traffic)

Maintenance (heartbeat enabled, no bearer)

Operational (both heartbeat and bearer).

Cluster-List

A Cluster-List is a list of Cluster IDs. IPAM-RNC only interacts (responds, learns)

from IPAMs belonging to one of the clusters in this list.
Neighbor list

A neighbor list a list of neighbors in the IPSHO universe of which RNC is aware.
These neighbors can be configured or learned.
Each neighbor is part of a cluster (the cluster ID should be in the Cluster list).
The RTT flag decides the routing of outgoing traffic towards the neighbor as follows:

On means enabled for IP

Off means enabled for ATM

Note that setting the Global RTT flag as On overrides this flag. That is, traffic would
be over IP for all neighbors, irrespective of how the neighbor-related RTT flags are set.
CA-IP map list

The CA-IP map list is a list of far CAs, and their IP addresses. Each CA is part of a
neighbor (should be in the neighbor list). The RTR flag is the traffic state of the CA.
Moving from ATM to IPSHO

PRELIMINARY

Once traffic is moved from ATM to IP the potential impact on the SHO traffic can be
negative, if not implemented properly.
If the Global-RTT flag is enabled and the learning modes is also enabled, the RNC can
learn about its far neighbors and far CAs, and move all the ATM SHO traffic to and
from the other MSC (FPS or RNC) to IPSHO immediately.

14-10

IPSHO configuration

If, however, the network is not set up properly or there are other unforeseen issues, this
may have repercussions that can impact service. A couple of mitigation options are
suggested in the following.
Check the network

Before the IPAMs learn about each other, it is recommended that connectivity between
all the end points be tested. The RNC supports commands and utilities to check
end-to-end connectivity.

PRELIMINARY

Configuring IPSHO connectivity

Disable learning

The RNC has two learning modes:

Neighbor learning (enabled/disabled)

CA-IP map learning (enabled/disabled

Both learning modes can be disabled, and the new IPAM neighbors and their data
(CA-IP maps) can be manually configured in Safe Mode.
Safe mode

The use of Safe Mode reduces the risk of a potential impact on traffic, but makes the
integration procedure more lengthy, and involves its own risks. This is generally not
recommended, unless circumstances require it, and the technician has the required
expertise.
However, the Safe Mode option can also be used for the initial deployment, and then
the technician can switch to the regular mode.
Overall strategy

Overall, the recommended strategy is to try to minimize the technician interaction with
the RNC TPU-GUI.
The majority of the configuration changes will be on the FPS from which the RNC can
then learn the information, which is then validated through the TICLI/TPUCLI
interfaces. Thus, TPU-GUI involvement is minimized.
Integration scenarios

Integration scenarios provided in this document are as follows:

Change cluster ID of a single MSC.

Integrate IPSHO enabled RNC and its neighbors.

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
14-11
Issue 14, September 2009
See notice on first page

PRELIMINARY

Configuring IPSHO connectivity

Change
cluster ID of a single MSC
...................................................................................................................................................................................................................................
Purpose

To change the cluster ID of a single MSC that is currently isolated from the network.
Reason to perform

For either of the following scenarios;

The service provider previously integrated an RNC and FPS in two separate,
isolated MSCs, and assigned a temporary unique cluster ID to each MSC. Now
they wish to interconnect the two MSCs, but they want both MSCs to share the
same cluster ID. Before proceeding with the interconnection, the cluster ID will
need to be changed for one of the MSCs.

The service provider previously integrated an RNC and FPS in two separate,
isolated MSCs, and assigned the same temporary cluster ID to each MSC. Now,
before interconnecting the MSCs, they realize that the two MSCs should not be in
same cluster. Before proceeding with the interconnection, the cluster ID will need
to be changed for one of the MSCs.

Scenario (current status)

For this provisioning scenario, the current status is:

Cluster X = MSC alpha.

FPS in MSC alpha = IPAM-1 and CA-a through CA-z

RNC in MSC alpha= IPAM-2 and CA-aa through CA-zz

Traffic and IPAM heartbeats are successful between CAs in Cluster X.

Scenario (goals)

Change MSC alpha FPS and RNC from Cluster X to ClusterY.

Before you begin

PRELIMINARY

Ensure the following:

That you have access to 235-200-100, Alcatel-Lucent 9281 Packet Switch

Operations, Administration, and Maintenance.

That traffic and IPAM heartbeats are functioning successfully between the
Community Addresses (CAs).

That Learning Mode is enabled.

Important! With Learning Mode enabled, if the network is not set up properly, this
could result in an impact to service. See Moving from ATM to IPSHO for
information pertaining to the implications of disabling learning mode, and
provisioning in Safe mode.

14-12

Change cluster ID of a single MSC

Change cluster ID for RNC

Bring up the TPU GUI of the RNC for which you are updating the cluster ID.
...................................................................................................................................................................................................

PRELIMINARY

Configuring IPSHO connectivity

On the 1X RNC TPU Web page, click on the Configuration Data link.
Result: The RNC Configuration Data page is displayed.
...................................................................................................................................................................................................

Select the Global Config Data button on the left side of the TPU GUI.
Result: The GUI navigates to the Global Configuration Data page
...................................................................................................................................................................................................

Click on the Global IPSHO Parameters link.

Result: The GUI navigates to the Global IPSHO Parameters page, as shown in

the following example:

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
14-13
Issue 14, September 2009
See notice on first page

PRELIMINARY

Configuring IPSHO connectivity

Change cluster ID of a single MSC

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

5
If the Cluster name/ID already exists...

If the Cluster name/ID does not

exist...

Proceed to Step 9.

Proceed to Step 6.

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

Enter the new Cluster name/ID in the Add Cluster/Cluster ID: box.
...................................................................................................................................................................................................

Click on the Submit button.

Result: The new cluster name is added to the Cluster List: box on the right hand
side of the Global IPSHO Parameters page.
...................................................................................................................................................................................................

Verify that the new cluster name, now exists:

On the 22.37r form of each FPS neighbor, via the FPS STLWS.
In the Cluster List of the Global IPSHO Parameters view of each neighbor RNC,
via the TPU GUI.

If it does not exist:

Add the cluster name per, 22.37i in 235-200-100 for FPS.

Add the cluster name as previously described for RNC.

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

On the Global IPSHO Parameters page in the RNC Cluster ID: box under Cluster
configuration, change the value to the new cluster/ID name.
...................................................................................................................................................................................................

Click on the Submit button.

Result: A neighbor list update will be sent to all of the FPS and RNC neighbors

with the new cluster information.

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

PRELIMINARY

Via the FPS STLWS:

Verify that the remote neighbor FPSs have received the update with the
op:nbrlist command.

Verify that the new Cluster name shows up in the output

14-14

Change cluster ID of a single MSC

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

Via the TPU GUI, on the left side of the Configuration Data page:

Click on the Neighbor List (GICC View) link.

Click on the Neighbor List (RNC DB View) link.

PRELIMINARY

Configuring IPSHO connectivity

Change cluster ID for FPS

Information pertaining to how a new cluster ID is added (when required) and updated
for FPS is provided in 235-200-100.
Refer to the following sections:

6.18.5 Define New Cluster Name

6.18.6 Update Local Cluster Name

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
14-15
Issue 14, September 2009
See notice on first page

PRELIMINARY

Configuring IPSHO connectivity

Integrate
IPSHO enabled RNC and its neighbors
...................................................................................................................................................................................................................................
Purpose

To introduce an IPSHO-enabled, but as yet isolated MSC into an IPSHO universe

comprising one or more IPSHO-enabled MSCs. The MSC being added to the universe
has one or more IPSHO-enabled RNCs.
Reason to perform

Enable the RNCs to use the IPSHO network instead of the ATM network for hand-off
traffic
Prerequisites

The IPSHO enabled RNC has previously been integrated with the FPS, and any other
RNCs in the MSC in which it is resident.
Assumptions

The following is assumed:

All operations will be done with Learning Mode Enabled (LME)..

The RTT flags will be used to control IPSHO traffic activation.

New neighbors will be provisioned at the FPS, and RNCs will learn about new
neighbors from the FPS.

Terminology

Terminology pertinent to this procedure is identified in the following paragraphs.

Ready To Receive (RTR)

RTR is an attribute associated with an IPSHO Community Address (CA).

PRELIMINARY

The values for RTR are listed as follows:

A value of 0 means that the CA is not ready to receive or process any traffic.

A value of 1 means that the CA can receive and process OAM traffic (like
heartbeats) but not bearer traffic.

A value of 2 means that the CA will receive and process both OAM and bearer
traffic.

Global Ready to Transmit (G-RTT)

G-RTT is a flag that determines whether RNC will use IPSHO or ATMSHO to send
handoff traffic to neighbors towards all neighbor CAs that are ready to receive over
IPSHO (that is, CAs with RTR value of 2).

14-16

Integrate IPSHO enabled RNC and its neighbors

This is a global flag and overrides the Neighbor-wise Ready to Transmit

(Neighbor-RTT) flags. Typically, this flag is meant to be used when the technician
wants to open IPSHO communication for all neighbors.
Neighbor-wise Ready to Transmit (Neighbor-RTT)

Neighbor-RTT is a per-neighbor flag. If the G-RTT flag is not set, this flag decides
whether RNC will use IPSHO or ATMSHO to send handoff traffic to all CAs in that
particular neighbor that are ready to receive over IPSHO (that is, CAs with RTR value
of 2).

PRELIMINARY

Configuring IPSHO connectivity

This flag is meant to be used when the customer wants to control activation of traffic
on a per-neighbor basis.
System configuration at the start

For the example that follows, the assumption for the system configuration at the start
of the procedure is that the cluster ID of the MSC being added to the existing IPSHO
universe is same as that of the universe.
Cluster X = MSC alpha and MSC beta:

MSC alpha = FPS and RNC:

FPS = IPAM-a1 and CA-a through CA-z

RNC = IPAM-a2 and CA-aa through CA-zz

MSC beta = FPS and RNC:

FPS = IPAM-b1 and CA-ab through CA-zb

RNC = IPAM-b2 and CA-ac through CA-zc

Additional conditions

Additional conditions would be:

No Traffic and IPAM heartbeats between CAs in MSC alpha and MSC beta.
MSC alpha and MSC beta are not aware of each others IPSHO capabilities, and
use ATM to exchange traffic.

Variants

One variant to consider is when the cluster ID of the MSC that is being added to the
existing IPSHO universe is different from that of the universe.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
14-17
Issue 14, September 2009
See notice on first page

PRELIMINARY

Since most of the steps are the same, the two variants are described together in the
procedure sections that follow. Specific notes are provided wherever the two variants
require different treatments.

PRELIMINARY

Configuring IPSHO connectivity

Integrate IPSHO enabled RNC and its neighbors

System configuration at the end

The system configuration at the end of the procedure would be as follows:

IPAM-a1 and IPAM-a2 now aware of IPAM-b1 and IPAM-b2 and their respective
CAs

IPAM-b1 and IPAM-b2 now aware of IPAM-a1 and IPAM-a2 and their respective
CAs

Traffic and IPAM heartbeats are successful between CAs in MSC alpha and MSC
beta.

Before you begin

Ensure the following:

That all static routes between subnets have previously been configured. During the
initial IPSHO integration by Alcatel-Lucent, all routes needed for intra-MSC traffic
are configured. If new routes are needed for connection of traffic between the
MSC, and the new neighbors, these need to be added through the TPU-GUI Static
Route addition page.

That you have obtained a list of all the FPS and RNC neighbors in the cluster,
along with their associated IP address and Community Address (CA) information.
That you have access to 235-200-100, Alcatel-Lucent 9281 Packet Switch
Operations, Administration, and Maintenance.

Administration of the RTT flags

Learning mode needs to be enabled, neighbor-wise RTT flags need to be enabled and
then the global-RTT flag need to be disabled for RNC. Similar steps also need to be
executed at the FPS. Refer to 235-200-100 for information pertaining to how learning
modes are enabled on the FPS.
For RNC, proceed as follows:
...................................................................................................................................................................................................

Bring up the TPU GUI on the RNC in MSC alpha.

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

On the 1X RNC TPU Web page, click on the Configuration Data link.
Result: The RNC Configuration Data page is displayed.

PRELIMINARY

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

Click on the RNC Level IPSHO Parameters link.

14-18

Integrate IPSHO enabled RNC and its neighbors

Result: The GUI navigates to the RNC Level IPSHO Parameters page, as shown

in the following example:

PRELIMINARY

Configuring IPSHO connectivity

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

In the Neighbor Learning Mode: and CA-IP Map Learning Mode: drop-down boxes,
ensure that Enabled is selected.
...................................................................................................................................................................................................

Return to the RNC Configuration Data page, and click on the Neighbor List (RNC
DB View) link.

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
14-19
Issue 14, September 2009
See notice on first page

PRELIMINARY

Configuring IPSHO connectivity

Integrate IPSHO enabled RNC and its neighbors

Result: The Neighbor List (RNC DB View) page appears with a list of existing

IPSHO neighbors. See the following example:

...................................................................................................................................................................................................

Select the first neighbor, and click on the Modify button.

Result: Configuration attributes for that neighbor are displayed, as shown in the

PRELIMINARY

following example:

14-20

Integrate IPSHO enabled RNC and its neighbors

...................................................................................................................................................................................................

Proceed as follows:
1. Select (check) the box marked as, Global RTT.
2. Click on Submit and return to the Neighbor List (RNC DB View) page.
3. Execute the same steps for all the neighbors in the list.

PRELIMINARY

Configuring IPSHO connectivity

...................................................................................................................................................................................................

Return to the RNC Configuration Data page, and click on the RNC Level IPSHO
Parameters link.
...................................................................................................................................................................................................

In the Global RNC RTT: drop-down box, ensure that No is selected, and click on the
Submit button.
Result: A dynamic update begins.
...................................................................................................................................................................................................

Return to the Neighbor List (RNCDB View) page, and wait for about ten minutes for
the database changes to reach the GICC through the dynamic update.
...................................................................................................................................................................................................

On the Neighbor List (RNCDB View) page click on the CA-IP Connectivity link.

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
14-21
Issue 14, September 2009
See notice on first page

PRELIMINARY

Configuring IPSHO connectivity

Integrate IPSHO enabled RNC and its neighbors

Result: CA-IP connectivity status appears on the screen, as shown in the following

example:

...................................................................................................................................................................................................

Verify that the Routing Type: box is set to IPGlobal.

...................................................................................................................................................................................................

On the FPS side, verify that all the CAs in the FPS are receiving traffic from the RNC
over IPSHO.
...................................................................................................................................................................................................

If there is more than one RNC in the MSC, repeat the same steps on the other RNC.
On the RNC Configuration Data page, click on the CA-IP Connectivity Status link,
and check that the traffic received indicators are set to IP.
...................................................................................................................................................................................................

PRELIMINARY

If the cluster ID of the MSC is same as the cluster ID of the IPSHO universe to which
it is being added, proceed to Step 16. Otherwise, proceed to Step 19.
...................................................................................................................................................................................................

Return to the RNC Configuration Data page, click on the Global Configuration Data
button, and on that screen select the IPSHO Cluster List link.

14-22

Integrate IPSHO enabled RNC and its neighbors

Result: The GUI navigates to the Global IPSHO Parameters page as shown in the

following example:

PRELIMINARY

Configuring IPSHO connectivity

...................................................................................................................................................................................................

Inside the Cluster Configuration section enter the cluster ID of the IPSHO universe
into the Cluster ID: box under Add Clusterr, and click on the Add Cluster button.
Result: A dynamic update is generated.
...................................................................................................................................................................................................

Execute Step 16 and Step 17 on each of the RNCs in the existing universe, unless the
cluster ID of the MSC being added to the universe is already present on the list.
...................................................................................................................................................................................................

You have reached a SAFE STOPPING POINT.

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
14-23
Issue 14, September 2009
See notice on first page

PRELIMINARY

Configuring IPSHO connectivity

Integrate IPSHO enabled RNC and its neighbors

Trigger learning of new neighbors

On the FPS, add at least one new neighbor. For example, in the FPS of the MSC, add
one FPS of the IPSHO universe. Follow 235-200-100 for details on the operation.
Result: This will trigger a sequence of neighbor and CA-IP map learning events.
...................................................................................................................................................................................................

Via the RNCs TPU GUI verify that learning has occurred as follows:
1. On the Neighbor List (IPSHO GICC View) page, verify that new neighbors have
been learned
2. On the CA-IP Map (IPSHO GICC View) page, verify that new CA-IP maps have
been learned
3. On the CA-IP Connectivity Status page, check that heartbeats have been
established between all the CA pairs, but that no traffic has been setup over
IPSHO.
...................................................................................................................................................................................................

Verify that the new learned information has been added to the database, by viewing the
Neighbor List (RNC DB View) and CA-IP Map (RNC DB View) pages. Note that this
may take from 20 to 30 minutes.
Important! If the RNC is not learning any information, use RNC or FPS
commands to either issue a query, or a neighbor list update request. Refer to
IPSHO service status reports (p. 14-28) for RNC-specific commands.
E...................................................................................................................................................................................................
ND OF STEPS

Activating IPSHO traffic towards new neighbors

Once the RNC has learned about new neighbors and their CA-IP maps, and the IPAM
heartbeat are found to be stable, the next step is to enable traffic towards the newly
learned CAs to move over to IPSHO operation.
On the RNC, proceed as follows:
...................................................................................................................................................................................................

PRELIMINARY

Bring up the TPU GUI on the RNC in MSC alpha, and on the 1X RNC TPU Web
page, click on the Configuration Data icon.
Result: The GUI navigates to the RNC Configuration Data page.
...................................................................................................................................................................................................

Click on the Neighbor List (RNC DB View) link.

14-24

Integrate IPSHO enabled RNC and its neighbors

Result: The Neighbor List (RNC DB View) page appears with a list of existing

IPSHO neighbors. See the following example:

PRELIMINARY

Configuring IPSHO connectivity

...................................................................................................................................................................................................

Select (check) the box identified as Global RTT and click on the Submit button.
Result: Configuration information about that neighbor appears on the screen, as

shown in the example that follows:

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
14-25
Issue 14, September 2009
See notice on first page

PRELIMINARY

Configuring IPSHO connectivity

Integrate IPSHO enabled RNC and its neighbors

...................................................................................................................................................................................................

Select (check) the Global RTT box and click on Submit.

...................................................................................................................................................................................................

Return to the RNC Configuration Data page, and WAIT for about ten minutes for the
database changes to reach the GICC through dynamic update.
...................................................................................................................................................................................................

On the RNC Configuration Data page, click on the Neighbor List (RNC DB View)
link.
Result: The Neighbor List (RNC DB View) page appears. See the following

example:

...................................................................................................................................................................................................

Click on the CA-IP Con Status link.

Result: The CA-IP Connectivity Status page appears.

PRELIMINARY

...................................................................................................................................................................................................

Verify that:

The Routing Type is set to IPGlobal.

The TR Indicator (traffic received indicator) is set to Yes to indicate that traffic
from the newly learned CAs is now coming over IP.

14-26

Integrate IPSHO enabled RNC and its neighbors

...................................................................................................................................................................................................

Optionally, check on the other end (FPS or RNC the newly learned neighbor) and
verify that all the CAs in the FPS are receiving traffic from the RNC over IPSHO.
...................................................................................................................................................................................................

Execute step 1 through 7 for each of the neighbors. Optionally, the routing type for all
the new neighbors can be enabled together, by iterating through steps 3 and 4.

PRELIMINARY

Configuring IPSHO connectivity

...................................................................................................................................................................................................

If there are two RNCs in the MSC repeat steps 1 through 9 for the other RNC.
Important! Equivalent steps also need to be executed at the FPS.
E...................................................................................................................................................................................................
ND OF STEPS

Enable global RTT and disable neighbor-wise RTT (Optional)

At the end of the previous procedure, traffic is activated over IPSHO for all neighbors
by setting the neighbor-wise RTT flag to true (actually setting routing type to IP for
each of the neighbors).
If the technician wants to use the global-RTT flag to control the traffic for all
neighbors, perform the following procedure:
...................................................................................................................................................................................................

For the FPS in MSC alpha, and the FPS in MSC beta, enable the global RTT flag, and
disable the neighbor-wise RTT flag. Refer to 235-200-100 for information on how to
enable the global RTT flag, and disable the neighbor-wise RTT flag.
...................................................................................................................................................................................................

Click on the RNC Level IPSHO Parameters link.

Result: The GUI navigates to the RNC Level IPSHO Parameters page.:
...................................................................................................................................................................................................

In the Global RNC RTT: drop-down box, ensure that Yes is selected, and click on the
Submit button.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
14-27
Issue 14, September 2009
See notice on first page

PRELIMINARY

Configuring IPSHO connectivity

Integrate IPSHO enabled RNC and its neighbors

Result A dynamic update occurs to place the Global RTT flag into the enabled

configuration.
...................................................................................................................................................................................................

Perform steps 2 through 4 for the RNC in MSC beta.

...................................................................................................................................................................................................

From the Neighbor List (RNC-DB view), select each neighbor and click on the Modify
button, to obtain the Neighbor Configuration screen. See the following example:

...................................................................................................................................................................................................

Uncheck the Global RTT flag to disable the neighbor-wise RTT selection, and let the
RNC-wide G-RTT flag determine the IP transmission.

PRELIMINARY

IPSHO service status reports

The following reports can be used to determine IPSHO service status:

CA-IP map report

Neighbor list report

14-28

Integrate IPSHO enabled RNC and its neighbors

CA-IP map report

The CA-IP map report for an RNC can be obtained by executing the following
command:
get:rnc X,ca2ipmap

where: X is the 1xRNC number.

An output similar to the following example occurs:

PRELIMINARY

Configuring IPSHO connectivity

1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
LocalCA Table Entries:
1234567890123456789012345678901212345678901234567890123456789
TrSt = Traffic State
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
------------------------------------------------------------------1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
RNC Name SUBNETID CA TrSt IP Address Degrow Mode
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
------------------------------------------------------------------1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
RNC4 1 1 2 172.98.0.104 OFF
1234567890123456789012345678901212345678901234567890123456789
RNC4 1 2 2 172.98.0.104 OFF
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
RNC4 1 5 2 172.98.0.104 OFF
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
RNC4 1 6 2 172.98.0.104 OFF
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
FarCA Table Entries:
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
-----------------------------------------------------------------------------1234567890123456789012345678901212345678901234567890123456789
SUBNETID FARCA CLUSTERID OFFICEID IPADDR Learn Mode TrSt
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
-----------------------------------------------------------------------------1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
0 11 CLUSTER1 RNC5 172.98.0.105 Learned 2
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
0 12 CLUSTER1 RNC5 172.98.0.105 Learned 2
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
0 102 CLUSTER0 5EG10 172.98.0.23 Learned 2
1234567890123456789012345678901212345678901234567890123456789
0 105 CLUSTER0 5EG10 172.98.0.53 Learned 2
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
0 106 CLUSTER0 5EG10 172.98.0.63 Learned 2
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
Neighbor list report

The neighbor list report for an RNC can be obtained by executing the following
command:
get:rnc X,nbrlst

where: X is the 1xRNC number.

An output similar to the following example should occur:

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
14-29
Issue 14, September 2009
See notice on first page

PRELIMINARY
PRELIMINARY

Configuring IPSHO connectivity

Integrate IPSHO enabled RNC and its neighbors

14-30

Growing/Degrowing TPU cards

PRELIMINARY

To provide information concerning the growth/degrowth of GICCs, CICCs, and

B-PCFs in an existing TPU shelf.
Be advised

This chapter covers GICC growth/degrowth considerations specifically in regard to the

5E Gateway (5EGW) function. For information regarding GICC growth/degrowth as
regards to the IP Backhaul function, refer to IP Backhaul for CDMA Voice and Packet
Data guide (401-710-090).
Contents
Growth

15-3

Growing 5E Gateway (5EGW) GICCs

15-7
15-14

Add and configure GICC pair via TPU GUI

15-16

Growing 5E Gateway (5EGW) on unused OC3 ports

15-30

Physically connect OC3 cable

15-33

Configure OC3 (ATM) port(s) as 5EGW

15-34

Growing an IPSHO GICC pair

15-44

Growing CICCs

15-46

Install plug and play CICC card in shelf

15-48

Growing B-PCF(s)

15-52

Configure B-PCF

15-76

Configure PDSN(s)

15-83

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
15-1
Issue 14, September 2009
See notice on first page

PRELIMINARY

Physically install GICC pair and connect cables

PRELIMINARY
PRELIMINARY

Growing/Degrowing TPU cards

Overview

Physically install B-PCF in TPU shelf

15-92

De-Growth

15-99

Degrowing GICCs

15-102

Shutdown the GICC card

15-103

Degrow GICC via TPU GUI

15-106

Remove GICC card

15-112

Degrowing 5E gateway on used OC3 port

15-116

Shutdown the 5EGW

15-117

Deprovision 5E gateway(s) on GICC

15-120

Degrowing CICCs

15-127

Shutdown the CICC card

15-128

Remove plug and play CICC from shelf

15-131

Degrowing a B-PCF

15-135

Shutdown B-PCF

15-136

Halt B-PCF

15-140

Delete B-PCF presence from RNC Database

15-142

Physically remove B-PCF

15-147

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

15-2

Growth
Overview
...................................................................................................................................................................................................................................

PRELIMINARY

Growing/Degrowing TPU cards

Purpose

This section provides information pertaining to the growth of GICCs, CICCs, and
B-PCFs in an existing TPU shelf.
Introduction

When a TPU shelf is not fully populated, for example, the minimum configuration
exists, the service provider can provide additional GICCs CICCs, or B-PCFs as needed.
Minimum configuration

Each RNC cabinet includes two TPU shelves for redundancy. The minimum TPU shelf
card configuration for the two shelves is shown in Figure 15-1, Minimum TPU Shelf
Card Configuration (p. 15-3).
The GICC cards (slot 3) provide the TPU Shelf Controller (SC) function.
Figure 15-1 Minimum TPU Shelf Card Configuration

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
15-3
Issue 14, September 2009
See notice on first page

PRELIMINARY
PRELIMINARY

Growing/Degrowing TPU cards

Overview

GICC, CICC, and B-PCF population rules

Growth in the TPU shelves (Figure 15-2, GICC and CICC growth (maximum)
(p. 15-5)) is allowed as follows:

The GICCs are grown in pairs. For standardization purposes, starting with slot 20,
then slot 4, and finally slot 19 is recommended.

For CICCs the growth pattern alternates outwardly from the center of the shelf
starting at slot 11, then slot 13, slot 10, slot 14, and so on. Note that the growth of
CICCs should be balanced, alternating each additional CICC between the upper and
lower shelf.

The B-PCFs are grown independently, alternating in slots 5, 6, 17, and 18 of the
upper and lower TPU shelves.

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

15-4

Overview

Figure 15-2 GICC and CICC growth (maximum)

PRELIMINARY

Growing/Degrowing TPU cards

Contents
Growing 5E Gateway (5EGW) GICCs

15-7
15-14

Add and configure GICC pair via TPU GUI

15-16

Growing 5E Gateway (5EGW) on unused OC3 ports

15-30

Physically connect OC3 cable

15-33

Configure OC3 (ATM) port(s) as 5EGW

15-34

Growing an IPSHO GICC pair

15-44

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
15-5
Issue 14, September 2009
See notice on first page

PRELIMINARY

Physically install GICC pair and connect cables

PRELIMINARY
PRELIMINARY

Growing/Degrowing TPU cards

Overview

Growing CICCs

15-46

Install plug and play CICC card in shelf

15-48

Growing B-PCF(s)

15-52

Configure B-PCF

15-76

Configure PDSN(s)

15-83

Physically install B-PCF in TPU shelf

15-92

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

15-6

Growing
5E Gateway (5EGW) GICCs
...................................................................................................................................................................................................................................
Introduction

When planning the initial implementation of CDMA 1X RNC into an existing system
environment, future growth considerations may require the inclusion of an
under-utilized RNC cabinet. When that is the case, additional GICC cards may be
grown in as required.

PRELIMINARY

Growing/Degrowing TPU cards

GICC type

Two types of GICCs are available for use in 5EGW growth:

Non-optical ethernet GICC (1.0) card

Optical ethernet GICC (1.1) card

Note that two ports (1 and 2) on either GICC card type are available for 5EGW
growth.
Planning considerations

Because the optical ethernet GICC (1.1) card is capable of supporting 5EGWs,
planning considerations may make it more desirable to use the optical ethernet GICC
(1.1) card for any future growth scenarios. Contact your Alcatel-Lucent account
representative for additional information.
Non-optical ethernet GICC (1.0) card

The non-optical ethernet GICC (1.0) card can serve as an RNC Shelf Controller GICC
(SC-GICC), and:

Provides the 5EGW function between the DCS and TPU over ATM (OC3).
May provide the RNC Gateway (A8/A9) function between the RNC and PCF over
IP. (SC-GICC only.)
May provide the RNC Gateway (A10/A11) function between the B-PCF and the
PDSN. (SC-GICC only.)

Optical ethernet GICC (1.1) card

The optical ethernet GICC (1.1) card can serve as an RNC SC-GICC, and:
Provides the 5EGW function between the DCS and TPU over ATM (OC3).

Provides theP Backhaul function. Refer to the IP Backhaul for CDMA Voice and
Packet Data guide (401-710-090) for specifics regarding growth and degrowth.
May provide the RNC Gateway (A8/A9) function between the RNC and PCF over
IP. (SC-GICC only.)
May provide the RNC Gateway (A10/A11) function between the B-PCF and the
PDSN. (SC-GICC only.)

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
15-7
Issue 14, September 2009
See notice on first page

PRELIMINARY

Growing/Degrowing TPU cards

Growing 5E Gateway (5EGW) GICCs

GICC 1.0 data rate

The GICC 1.0 is equipped with two copper GigE interfaces that can be used only for
the A8/A9 and A10/A11 interfaces (SC-GICC function only). This data rate is set on a
per RNC basis.
The data rate (set during the implementation phase) for the GICC 1.0 can be any of the
following:

10 Mbps

100 Mbps

1000 Mbps
autonegotiate
Important! It is highly recommended that the data rate for the GICC 1.0 be set at
100 Mbps. Note that peformance of 1000 Mbps over copper cannot be guaranteed.

GICC 1.1 data rate

The GICC 1.1 has two optical GigE interfaces that always operate at 1000 Mps. This
rate is fixed and therefore is not configurable.
The copper GigE data rate setting on the TPU-GUI 1X RNC Information screen does
not impact the GICC 1.1 GigE port data rates.
The GICC 1.1 has one copper GigE interface that is not used on the 3G1xRNC. Note
also that IP Backhaul capability is only possible via the GICC 1.1. The IP backhaul
gateway service is always assigned to the first optical port.
GICC card redundancy

Because the ATM network can be vulnerable to line failures, the GICCs are always
grown in pairs. The option for running in Automatic Protection Switching (APS) mode,
or in non-APS mode is provided.

PRELIMINARY

Important! GICC pairs should be equipped with the same hardware version. A
mismatch in hardware versions, for example, non-optical ethernet GICC (1.0) card
paired with an optical ethernet GICC (1.1) card is supported while GICC hardware
is being upgraded for a particular GICC pair. However, non-optical ethernet GICC
(1.0) card pairs can be equipped in the same RNC with optical ethernet GICC (1.1)
card pairs.
APS mode

With the APS mode, 5EGWs on the GICCs in the upper and lower TPU shelf are
paired to provide each Community Address (CA) with a redundant counterpart. See
also Chapter 13, Automatic Protection Switching (APS) for specifics.

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

15-8

Growing 5E Gateway (5EGW) GICCs

Non-APS mode

With the non-APS mode, each ATM service has its own internal Unique Service IP
address and all ATM services run in active/active mode.
IP services operation mode

The IP services operation mode is independent of the operation mode of ATM services.
Essentially, the IP services, i.e., Shelf Controller, A8/A9 GW service and
RNC_SHO_GW service, still operate in active/standby mode with the support of the
VSRP.

PRELIMINARY

Growing/Degrowing TPU cards

If a fault in the active IP service instance software, or in the Gbps Ethernet (GIGE)
link that supports the active IP service instance prevents correct operation of the active
IP service instance, the standby IP service instance becomes active and provides the
prime services.
Engineering Considerations

In general, since all ATM services essentially run in the simplex mode when the
non-APS mode is invoked, faults in ATM GW service software and/or loss of an OC-3
facility that supports an ATM GW service will cause the total loss of active traffic on
the impacted OC-3 facility. Therefore, in order to minimize the impact of such a loss
on the system, network availability and capacity, the following high-level engineering
rules is recommended for the ATM services.
RNC call processing should evenly distribute the bearer traffic loads among all
available 5EGW instances in the RNC. In other words, all active call legs from all
calls should be evenly distributed across multiple 5EGW instances.
As regards to this rule, because the common address scheme in the SHO universe ATM
network is proprietary and endpointsVirtual Path/Virtual Circuit Identifiers are
predictable and well-known, all 5EGW service instances should be pre-configured with
all Virtual Paths to all possible destination Community Addresses (except the CA of
itself) in the same SHO subnet.
For example, a 5EGW instance with CA=5 should be pre-configured with all the
virtual paths to all other 253 Community Addresses in the same SHO subnet.
Therefore, the loss of one 5EGW instance will not impact the RNC connectivity to all
the PSUs and other RNCs in the soft handoff universe. However, some capacity into
the SHO universe from the RNC will be lost.
5EGW prerequisite considerations

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
15-9
Issue 14, September 2009
See notice on first page

PRELIMINARY

Consideration must be given as to how 5EGWs will be grown on the GICC card.

PRELIMINARY

Growing/Degrowing TPU cards

Growing 5E Gateway (5EGW) GICCs

Community Address (CA) considerations

Each 5EGW (a.k.a. PSU GW) associated with a GICC card (maximum of two allowed
per GICC) has a unique Community Address (CA), unless APS is enabled. With APS
enabled, two 5EGWs in a mated pair share the same CA.
Therefore, each 5EGW (APS disabled) or 5EGW pair (APS enabled) equates to a
5ESS Packet Switching Unit (PSU) in the Soft Handoff (SHO) universe.
Refer to Chapter 12, Configuring ATM connectivity in RNCs SHO universe for
more specifics regarding CAs.
ATM switch-to-5ESS path

The OC3 port is cabled to the PSAX (or equivalent ATM switch) which provides
permanent Virtual Connections (VPC or VCC) to the unique CAs of the associated
5ESS switches in the SHO universe.
IP addressing

Each GICC card (upper and lower shelf) requires a unique IP address for ATM
switch-to-PCF communication.
Order of GICC growth

As shown in Figure 15-2, GICC and CICC growth (maximum) (p. 15-5), the
non-shelf controller GICCs in a TPU shelf are grown in the following order:

slot 20

slot 4

slot 19

Order of OC3 growth

The OC3s on a GICC are provisioned from bottom (1) to top (2).
Important! This is only a recommended standard and may be overridden when the
situation dictates.
Dynamic data update

In order for the GICC configuration changes ( dynamic data updates) to complete,
ensure that the SC-GICCs are in the active/standby mode.

PRELIMINARY

ATM switch provisioning

ATM switch provisioning is a function specific to the Service Providers own methods
and procedures.
To grow an OC3 port as a 5EGW, you must provision the PSAX (or equivalent ATM
switch) to map the CA of each 5EGW (APS disabled) or 5EGW pair (APS enabled) to
all applicable CAs in the local and remote subnets.

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

15-10

Growing 5E Gateway (5EGW) GICCs

Provisioning before or after GICC card installation

If ATM switch-to-GICC card gateway paths are provisioned prior to GICC card
installation and the provisioning of GICC card gateways, alarms will occur on the
switch-side.That is because, from the switch point-of-view the gateway paths are
healthy and have no place to terminate.
If a GICC card is installed and gateways are provisioned, prior to the provsioning of
the ATM switch-to-GICC card gateway paths, alarms will occur on the RNC-side. That
is because, from the RNC point-of-view the gateway paths are healthy and have no
place to terminate.

PRELIMINARY

Growing/Degrowing TPU cards

In either case, the alarm duration time can be minimized, if the associated elements are
provisioned in parallel.
Criticality

The following procedures are non-service affecting.

Duration

The following procedures take approximately 30 minutes to perform.

Required Materials

The following materials will be required:

GICC card(s)

Optical (OC-3c) fiber cables

OC-3c may be Single-Mode Fiber (SMF) or Multi-Mode Fiber (MMF), duplex or

simplex, and crimp (ST) or push-pull coupling (SC). See Table 15-1, Fiber cables
(p. 15-11) for types and lengths.
Table 15-1

Fiber cables

Description
OC-3c MMF SC-SC Duplex

Length

Comcode

25 ft

300447521

50 ft

300447539

75 ft

300447547

100 ft

300447554

150 ft

300447562

PRELIMINARY

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
15-11
Issue 14, September 2009
See notice on first page

PRELIMINARY

Growing/Degrowing TPU cards

Table 15-1

Growing 5E Gateway (5EGW) GICCs

Fiber cables

Description
OC-3c MMF SC-ST Duplex

OC-3c SMF SC-SC Duplex

OC-3c SMF SC-ST Duplex

OC-3c SMF SC-SC Simplex

OC-3c SMF SC-ST Simplex

PRELIMINARY

(continued)
Length

Comcode

25 ft

300447596

50 ft

300447604

75 ft

300447612

100 ft

300447620

150 ft

300447638

25 ft

300447646

50 ft

300447653

75 ft

300447661

100 ft

300447679

150 ft

300447687

25 ft

300447794

50 ft

300447802

75 ft

300447810

100 ft

300447836

150 ft

300447844

32.8 ft

300447711

49.2 ft

300447729

82.0 ft

300447737

114.8 ft

300447745

147.8 ft

300447752

32.8 ft

300447851

49.2 ft

300447869

82.0 ft

300447877

114.8 ft

300447885

147.8 ft

300447893

Required tools

The following tools are required:

An antistatic wrist strap

An electrostatic discharge mat

A No. 2 Phillips screwdriver

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

15-12

Growing 5E Gateway (5EGW) GICCs

Required interfaces

The following interface is required: TPU-GUI.

Procedures

The procedures associated with growing an additional GICC card are listed as follows:

PRELIMINARY

Growing/Degrowing TPU cards

Physically install GICC pair and connect cables (p. 15-14)

Add and configure GICC pair via TPU GUI (p. 15-16)

PRELIMINARY

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
15-13
Issue 14, September 2009
See notice on first page

PRELIMINARY

Growing/Degrowing TPU cards

Physically
install GICC pair and connect cables
...................................................................................................................................................................................................................................
Purpose

Perform this procedure to install a GICC card pair in anticipation of performing the
subsequent configuration procedure.
ATM switch

For the GICC card installation to succeed, the ATM switch has to be provisioned to
accommodate the intended gateways that will be connected through the GICC pairs
that are to be installed in the TPU shelf. See also ATM switch provisioning
(p. 15-10).
Determine slots to be grown

GICCs can be grown in slots 4, 16, or 20 (see also Order of OC3 growth (p. 15-10)
).
APS enabled

If APS is enabled, cabling from the ATM switch to the GICC cards in the upper and
lower TPU shelf will be need to be routed to their respective working top shelf and
protection bottom shelf terminations at either end. See also Chapter 13, Automatic
Protection Switching (APS).
Procedure

CAUTION
ESD hazard
Static Damage Hazard
Always wear a wriststrap to ground your body before touching the GICC card. Keep
your body grounded while handling the card. Hold the card by its edges, do not touch
any components or circuits. When the card is not in an enclosure, store it in a
static-shielding bag.

PRELIMINARY

To install a GICC card in its proper slot of the TPU shelf, proceed as follows:
...................................................................................................................................................................................................

Run OC-3c fiber cables from the RNC cabinet to the Customer ATM SHO router
(5ESS Gateway) for each GICC in the upper and lower shelf. (The cable should be
routed through the Frame Interface Panel (FIP) compartment.)

15-14

Physically install GICC pair and connect cables

...................................................................................................................................................................................................

Verify that you have taken the proper anti-static precautions.

...................................................................................................................................................................................................

Verify the slots of the upper and lower TPU shelves in which you will be installing
each GICC card, and begin the installation in the upper shelf.

PRELIMINARY

Growing/Degrowing TPU cards

...................................................................................................................................................................................................

Keeping the replacement GICC card vertical, slide the card firmly into the slot between
the two guides and lock the upper and lower levers.
Result The Power/Fault LED lights green.
...................................................................................................................................................................................................

Tighten the card retention screw to anchor the card in the chassis.
...................................................................................................................................................................................................

Connect the OC3C cable for 5E Gateway service.

...................................................................................................................................................................................................

Perform Step 4 through Step 6 for the GICC in the lower shelf.
...................................................................................................................................................................................................

Proceed to Add and configure GICC pair via TPU GUI (p. 15-16).
END OF STEPS
...................................................................................................................................................................................................

PRELIMINARY

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
15-15
Issue 14, September 2009
See notice on first page

PRELIMINARY

Growing/Degrowing TPU cards

Add
and configure GICC pair via TPU GUI
...................................................................................................................................................................................................................................
Purpose

Perform this procedure to add and configure the GICC card pairs via the TPU-GUI
Configuration Wizard.
Before you begin

Review the following:

Chapter 12, Configuring ATM connectivity in RNCs SHO universe for specifics
regarding VPC and VCC provisioning.
Chapter 13, Automatic Protection Switching (APS) for specifics regarding APS.

Procedure

To add and configure GICC card(s) via the TPU-GUI Configuration Wizard, proceed
as follows:
...................................................................................................................................................................................................

If you are already at the the RNC Configuration Data page, proceed to Step 4.
If not obtain access to TPU-GUI either by:

Direct access method. See also Accessing TPU GUI (p. 6-6).

EMS. See also Logging on to Element Management System (EMS) (p. 6-5).

...................................................................................................................................................................................................

PRELIMINARY

If using EMS, at the OMP Web page you need to select 1X RNC TPU Web to
navigate to the 1X RNC TPU Web page. If using the direct access method, the same
will result. See the following example screen.

15-16

Add and configure GICC pair via TPU GUI

PRELIMINARY

Growing/Degrowing TPU cards

...................................................................................................................................................................................................

On the 1X RNC TPU Web page select Configuration Data.

PRELIMINARY

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
15-17
Issue 14, September 2009
See notice on first page

PRELIMINARY

Growing/Degrowing TPU cards

Add and configure GICC pair via TPU GUI

Result The GUI navigates to the RNC Configuration Data page (see example

screen).

...................................................................................................................................................................................................

PRELIMINARY

On the RNC Configuration Data page under Wizards select GICC Growth.

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

15-18

Add and configure GICC pair via TPU GUI

Result The GUI navigates to the Grow GICC -Warning Message pane (see

example screen).

PRELIMINARY

Growing/Degrowing TPU cards

...................................................................................................................................................................................................

Note the warning. If the prerequisites have not been met and you configure the GICCs,
alarms will be generated.
...................................................................................................................................................................................................

Select the Next button.

PRELIMINARY

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
15-19
Issue 14, September 2009
See notice on first page

PRELIMINARY

Growing/Degrowing TPU cards

Add and configure GICC pair via TPU GUI

Result The GUI navigates to the Grow GICC-GICC Selection page (see example

screen).

...................................................................................................................................................................................................

Select the number of GICC slots that you intend to grow (2, 4, or 6).
...................................................................................................................................................................................................

PRELIMINARY

Select the Next button.

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

15-20

Add and configure GICC pair via TPU GUI

Result The GUI navigates to the Grow GICC-GICC Configuration page (see

example screens 1 and 2 that follow).

Figure 15-3 Example Screen 1: Without APS Enabled

PRELIMINARY

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
15-21
Issue 14, September 2009
See notice on first page

PRELIMINARY

Growing/Degrowing TPU cards

PRELIMINARY

Growing/Degrowing TPU cards

Add and configure GICC pair via TPU GUI

Figure 15-4 Example Screen 2: With APS Enabled

...................................................................................................................................................................................................

PRELIMINARY

With APS enabled the CA is shared between 5EGWs. That is, ports 1 share a CA
and ports 2 share a CA.

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

15-22

Add and configure GICC pair via TPU GUI

In this example, following the GICC population rules, the GICC in slot 20 could be
grown by:

Selecting 5EGW (via the down arrowhead) in the GICC ATM boxes:
For Shelf 1 and/or Shelf 2 as required with APS disabled.
For Shelf 1 as required with APS enabled.
Entering the CA boxes with a Community Address (see also Chapter 12,
Configuring ATM connectivity in RNCs SHO universe) in the range1-254:
For Shelf 1 and/or Shelf 2 as required with APS disabled.

PRELIMINARY

Growing/Degrowing TPU cards

For Shelf 1 as required with APS enabled.

Important! With APS enabled the CA is shared between 5EGWs. That is, ports 1
share a CA and ports 2 share a CA.
...................................................................................................................................................................................................

When you are finished, select the Next button.

PRELIMINARY

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
15-23
Issue 14, September 2009
See notice on first page

PRELIMINARY

Growing/Degrowing TPU cards

Add and configure GICC pair via TPU GUI

Result The GUI navigates to the Grow GICC, 5E-GW CA Connection Overrides

page (see example screen).

...................................................................................................................................................................................................

For the local subnet in which the 5EGWs of the GICC reside, provision all the CAs
that the 5EGWs of the GICC being provisioned will need to communicate with as
either VCC or VPC, as follows:

PRELIMINARY

To move a single CA in the local subnet, highlight the CA to be changed in the

VCC Connection Type: or VPC Connection Type: box, and click on the > or <
button as appropriate to move the CA to the VCC or VPC list (as appropriate).
To move all CAs in the local subnet, click on the >> or << button as appropriate to
move the CAs to the VCC or VPC list (as appropriate).

...................................................................................................................................................................................................

Select the Next button.

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

15-24

Add and configure GICC pair via TPU GUI

Result The GUI navigates to the Grow GICC-Summary page (see the following

example screen). Note that at this point, a user can review the newly entered
summary information to see if it is correct. If it is not, highlighting and clicking on
the line in the section with the erroneous information will take the user back to the
point in the Wizard where the correction can be made.

PRELIMINARY

Growing/Degrowing TPU cards

...................................................................................................................................................................................................

Select the Submit button.

PRELIMINARY

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
15-25
Issue 14, September 2009
See notice on first page

PRELIMINARY

Growing/Degrowing TPU cards

Add and configure GICC pair via TPU GUI

Result The Confirm GICC box is displayed (see example screen that follows).

...................................................................................................................................................................................................

PRELIMINARY

Select Yes.

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

15-26

Add and configure GICC pair via TPU GUI

Result The Message GICC growth success box is displayed (see example screen

that follows).

PRELIMINARY

Growing/Degrowing TPU cards

...................................................................................................................................................................................................

Select OK.
Result GUI returns to RNC Configuration Data page. Note that depending on

system activity, a successful grow of a GICC may require between one to two
minutes for the GICC status to be updated on the TPU GUI. Wait approximately
two minutes before proceeding.

Navigate to the TPU-GUI TPU Network Elements page (see the following example
screen).

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
15-27
Issue 14, September 2009
See notice on first page

PRELIMINARY

...................................................................................................................................................................................................

PRELIMINARY

Growing/Degrowing TPU cards

Add and configure GICC pair via TPU GUI

...................................................................................................................................................................................................

Use the Filter: box at the top of the screen to filter on GICCs.
...................................................................................................................................................................................................

Determine the state of the newly-installed GICC.

Result The newly-installed GICC could be in any of the following states

PRELIMINARY

(depending on if the card is factory-new or being reused):

Admin State

Oper State

Usage State

Unlocked

Enabled

Idle or Active

Locked

Enabled

Idle or Active

Unlocked

Disabled

Idle or Active

Locked

Disabled

Idle or Active

See Figure 5-3,

Administrative state
(p. 5-7) for capsule
correlation.

See Figure 5-1,

Operational state
(p. 5-5) for capsule
correlation.

See Figure 5-2, Usage

state (p. 5-6) for capsule
correlation.

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

15-28

Add and configure GICC pair via TPU GUI

...................................................................................................................................................................................................

Depending on the state of the GICC, proceed as follows:

If the GICC is Locked-Enabled perform an unlock via the Commands column.

If the GICC is Locked-Disabled or Unlocked-Disabled perform a reset via the

Commands column.
Result The GICC should then come up as:

Admin State

Oper State

Usage State

Unlocked

Enabled

Idle or Active

See Figure 5-3,

Administrative state
(p. 5-7) for capsule
correlation.

See Figure 5-1,

Operational state (p. 5-5)
for capsule correlation.

See Figure 5-2, Usage

state (p. 5-6) for capsule
correlation.

PRELIMINARY

Growing/Degrowing TPU cards

Note: If after the reset the GICC is Locked-Enabled perform an unlock via the
Commands column.

...................................................................................................................................................................................................

Log out by using the Logout button.

...................................................................................................................................................................................................

To verify ATM connectivity, proceed to Initiating PSU loopback test (p. 9-60).
END OF STEPS
...................................................................................................................................................................................................

PRELIMINARY

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
15-29
Issue 14, September 2009
See notice on first page

PRELIMINARY

Growing/Degrowing TPU cards

Growing
5E Gateway (5EGW) on unused OC3 ports
...................................................................................................................................................................................................................................
Introduction

When planning the initial implementation of CDMA 1X RNC into an existing system
environment, future growth considerations may require the inclusionof an
under-utilized OC3 ports on GICC cards. When that is the case, additional OC3 ports
may be activated as 5E (PSU) gateways when required.
Important! This procedure specifically pertains to growing 5EGWs on non-SC
GICCs. For information concerning the growth of 5EGWs on SC-GICCs, contact
Alcatel-Lucent.
5EGW redundancy

Because the ATM network can be vulnerable to line failures, the 5EGWs are always
grown in pairs. See also Chapter 13, Automatic Protection Switching (APS).
Prerequisite considerations

Consideration must be given to how 5EGWs will be grown on the GICC card.
Community Address (CA) considerations

The OC3 port is cabled to the PSAX (or equivalent ATM switch) which provides
Permanent Virtual Conncections (VPC or VCC) to the unique CAs of the associated
5ESS switches in the SHO universe.
Order of 5EGW growth

The 5EGWs on a GICC are provisioned from bottom (1) to top (2).

PRELIMINARY

Dynamic data update

In order for the GICC configuration changes (dynamic data updates) to complete,
ensure that there are no outstanding TPU shelf alarms before you begin, and that the
SC-GICCs are in the active/standby mode.

15-30

Growing 5E Gateway (5EGW) on unused OC3 ports

Provision ATM switch

To grow an OC3 port as a 5EGW, you must provision the PSAX (or equivalent ATM
switch) to map the CA of each 5EGW (APS disabled) or 5EGW pair (APS enabled) to
all applicable CAs in the local and remote subnets.
Criticality

PRELIMINARY

Growing/Degrowing TPU cards

The following procedures are non-service affecting.

Duration

The following procedures take approximately 30 minutes to perform.

Required Materials

Optical (OC-3c) fiber cable(s) will be rquired.

OC-3c may be Single-Mode Fiber (SMF) or Multi-Mode Fiber (MMF), duplex or
simplex, and crimp (ST) or push-pull coupling (SC). See the following table for types
and lengths.
Description
OC-3c MMFSC-SC Duplex

OC-3c MMF SC-ST Duplex

OC-3c SMF SC-SC Duplex

Length

Comcode
300447521

50 ft

300447539

75 ft

300447547

100 ft

300447554

150 ft

300447562

25 ft

300447596

50 ft

300447604

75 ft

300447612

100 ft

300447620

150 ft

300447638

25 ft

300447646

50 ft

300447653

75 ft

300447661

100 ft

300447679

150 ft

300447687

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
15-31
Issue 14, September 2009
See notice on first page

PRELIMINARY

25 ft

PRELIMINARY

Growing/Degrowing TPU cards

Growing 5E Gateway (5EGW) on unused OC3 ports

Description
OC-3c SMF SC-ST Duplex

OC-3c SMF SC-SC Simplex

OC-3c SMF SC-ST Simplex

Length

Comcode

25 ft

300447794

50 ft

300447802

75 ft

300447810

100 ft

300447836

150 ft

300447844

32.8 ft

300447711

49.2 ft

300447729

82.0 ft

300447737

114.8 ft

300447745

147.8 ft

300447752

32.8 ft

300447851

49.2 ft

300447869

82.0 ft

300447877

114.8 ft

300447885

147.8 ft

300447893

Required interfaces

The TPU-GUI and TPU CLI is required.

Procedures

The procedures for activating additional OC3 ports as 5E gateways are listed as
follows:
Physically connect OC3 cable (p. 15-33)

PRELIMINARY

Configure OC3 (ATM) port(s) as 5EGW (p. 15-34)

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

15-32

Physically
connect OC3 cable
...................................................................................................................................................................................................................................
Purpose

Perform this procedure to configure OC3 ATM ports for 5EGW service (in APS or
non-APS mode) via the TPU-GUI Configuration Wizard.

PRELIMINARY

Growing/Degrowing TPU cards

Procedure
...................................................................................................................................................................................................

Run OC-3c fiber cable from the RNC cabinet to the Customer ATM SHO router (5ESS
Gateway), as applicable. (The cable should be routed through the Frame Interface
Panel (FIP) compartment.)
...................................................................................................................................................................................................

Verify the connector of the GICC in which you will be inserting the OC3 cable.
...................................................................................................................................................................................................

Connect the OC3c cables for PSU Gateway service as applicable.

...................................................................................................................................................................................................

Proceed to Configure OC3 (ATM) port(s) as 5EGW (p. 15-34).

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
15-33
Issue 14, September 2009
See notice on first page

PRELIMINARY

Growing/Degrowing TPU cards

Configure
OC3 (ATM) port(s) as 5EGW
...................................................................................................................................................................................................................................
Purpose

Perform this procedure to configure OC3 ATM ports for 5EGW service (in APS or
non-APS mode) via the TPU-GUI Configuration Wizard.
Before you begin

Review the following:

Chapter 12, Configuring ATM connectivity in RNCs SHO universe for specifics
regarding VPC and VCC provisioning.
Chapter 13, Automatic Protection Switching (APS) for specifics regarding APS.

Procedure

To add and configure ATM port(s) as a 5E GW via the TPU-GUI Configuration

Wizard, proceed as follows:
...................................................................................................................................................................................................

Obtain access to TPU-GUI either by:

Direct access method. See also Accessing TPU GUI (p. 6-6).

EMS. See also Logging on to Element Management System (EMS) (p. 6-5).

...................................................................................................................................................................................................

PRELIMINARY

If using EMS, at the OMP Web page you need to select 1X RNC TPU Web to
navigate to the 1X RNC TPU Web page. If using the direct access method, the same
will result. See the following example screen.

15-34

Configure OC3 (ATM) port(s) as 5EGW

PRELIMINARY

Growing/Degrowing TPU cards

...................................................................................................................................................................................................

On the 1X RNC TPU Web page select Configuration Data.

PRELIMINARY

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
15-35
Issue 14, September 2009
See notice on first page

PRELIMINARY

Growing/Degrowing TPU cards

Configure OC3 (ATM) port(s) as 5EGW

Result The GUI navigates to the RNC Configuration Data page (see example

screen).

...................................................................................................................................................................................................

PRELIMINARY

On the RNC Configuration Data page under Wizards select 5E GW Growth.

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

15-36

Configure OC3 (ATM) port(s) as 5EGW

Result The GUI navigates to the Grow-5E-GWs - Warning Message pane (see

example screen).

PRELIMINARY

Growing/Degrowing TPU cards

...................................................................................................................................................................................................

Note the warning. If the prerequisites have not been met and you configure a 5E
Gateway, alarms will be generated.
...................................................................................................................................................................................................

Select the Next button to move to the next page.

PRELIMINARY

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
15-37
Issue 14, September 2009
See notice on first page

PRELIMINARY
PRELIMINARY

Growing/Degrowing TPU cards

Configure OC3 (ATM) port(s) as 5EGW

Result The GUI navigates to the Grow 5E-GWs - GICC ATM Configuration page

(see example screens 1 and 2 that follow).

Figure 15-5 Example Screen 1: Without APS Enabled

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

15-38

Configure OC3 (ATM) port(s) as 5EGW

Figure 15-6 Example Screen 2: With APS Enabled

PRELIMINARY

Growing/Degrowing TPU cards

...................................................................................................................................................................................................

Important! With APS disabled, gateways on the GICCs in the upper and lower
TPU shelf are independent of each other. With APS enabled, gateways on the
GICCs in the upper and lower TPU shelf are paired.
With APS enabled the CA is shared between 5EGWs. That is, ports 1 share a CA
and ports 2 share a CA.

PRELIMINARY

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
15-39
Issue 14, September 2009
See notice on first page

PRELIMINARY

Growing/Degrowing TPU cards

Configure OC3 (ATM) port(s) as 5EGW

In this example, following the 5EGW population rules, the unused ports in slot 20
could be grown by:

Selecting 5EGW (via the down arrowhead) in the GICC ATM boxes:

For Shelf 1 and/or Shelf 2 as required with APS disabled.

For Shelf 1 as required with APS enabled. Note that changes are also
automatically mirrored for Shelf 2 as well.

Entering the CA boxes with a Community Address (see also Chapter 12,
Configuring ATM connectivity in RNCs SHO universe) in the range1-254:

For Shelf 1 and/or Shelf 2 as required with APS disabled.

For Shelf 1 as required with APS enabled.

...................................................................................................................................................................................................

When you are finished, select the Next button.

PRELIMINARY

Result The GUI navigates to the next page (see example screen).

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

15-40

Configure OC3 (ATM) port(s) as 5EGW

...................................................................................................................................................................................................

For the local subnet in which the OC3 5EGW resides, provision all the CAs that the
5EGW being provisioned will need to communicate with as either VCC or VPC, as
follows:

To move a single CA in the local subnet, highlight the CA to be changed in the

VCC Connection Type: or VPC Connection Type: box, and click on the > or <
button as appropriate to move the CA to the VCC or VPC list (as appropriate).

To move all CAs in the local subnet, click on the >> or << button as appropriate to
move the CAs to the VCC or VPC list (as appropriate).

PRELIMINARY

Growing/Degrowing TPU cards

...................................................................................................................................................................................................

When finished select Next. Note at this point, a user can review the newly entered
summary information to see if it is correct. If it is not, highlighting and clicking on the
line in the section with the erroneous information will take the user back to the point
in the Wizard where the correction can be made.

PRELIMINARY

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
15-41
Issue 14, September 2009
See notice on first page

PRELIMINARY

Growing/Degrowing TPU cards

Configure OC3 (ATM) port(s) as 5EGW

Result GUI navigates to the Grow 5E-GWs - Sumary page.

...................................................................................................................................................................................................

Select the Submit button.

PRELIMINARY

Result The Confirm box is displayed as follows.

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

15-42

Configure OC3 (ATM) port(s) as 5EGW

...................................................................................................................................................................................................

Select Yes.
Result The Message success box is displayed as follows.

PRELIMINARY

Growing/Degrowing TPU cards

...................................................................................................................................................................................................

Select OK.
Result TPU GUI returns to RNC Configuration Data page.
...................................................................................................................................................................................................

Log out by using the Logout button.

...................................................................................................................................................................................................

To verify ATM connectivity of the newly grown gateway(s), proceed to Initiating PSU
loopback test (p. 9-60).
END OF STEPS
...................................................................................................................................................................................................

PRELIMINARY

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
15-43
Issue 14, September 2009
See notice on first page

PRELIMINARY

Growing/Degrowing TPU cards

Growing
an IPSHO GICC pair
...................................................................................................................................................................................................................................
Introduction

The long-term vision with the advent of IPSHO is to supplement, and eventually
replace ATM SHO.
GICC type

The optical ethernet GICC (1.1) card is used for IPSHO deployment.
Growth limit

One IPSHO GICC pair is the growth limit per one RNC.
Initial deployment options

The following options of IPSHO initial deployment, are ordered in an increasing

degree of security risk, and cluster design complexity:

Option 1a - Intra-MSC only, Learning Mode Disable (LMD)

Option 1b - Intra-MSC, Learning Mode Enabled (LME)

Option 2 - Co-located MSCs, LMD or LME

Option 3 - LME, a small number of neighboring MSCs

Option 4. LME, many MSCs in a large, complex network (with CA subnet reuse)

Options 1a and 1b

The majority of bearer traffic (~90%) is intra-MSC. This means IPSHO deployed
intra-MSC is able to provide the most benefits in terms of alleviating the known PHA
performance bottleneck (PSU-PSU for voice and PSU-RNC for data).
Within an MSC static provisioning of CA-IP information can be easily performed since
the number of CAs in the MSC is very limited (Option 1a). By the same token,
intra-MSC LME can be used (Option 1b), as IPAM-to-IPAM messages do not leave the
router (they do not go out of the MSC).
Option 2

PRELIMINARY

Some MSCs are co-located in the same building (to save real estate costs) and they
may share the same pair of routers. In this case, IPAM-to-IPAM messages may not
leave the router..
Options 3 and 4

IM IPAM-to-IPAM messages traverse from router to router (from IP LAN of one MSC
to IP LAN of another MSC).These messages are subject to various security threats or
risks that can occur in any of the IP LANs of the remote MSCs that participate in
LME.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

15-44

Growing an IPSHO GICC pair

The more MSCs that are involved in LME-based IPAM message exchange, the higher
the risk. In a large network with subnet reuse, the number of MSCs involved in LME
can be numerous (refer to Office Engineering section), resulting in the highest degree
of security risks among the options listed.
Additional information

For additional information concerning these options., refer to 401-710-081, CDMA 1X

RNC Planning and Implementation.

PRELIMINARY

Growing/Degrowing TPU cards

IPSHO growth procedures

Implementation of IPSHO is currently only provided through Alcatel-Lucent. Please

contact your Alcatel-Lucent representative for more information.

PRELIMINARY

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
15-45
Issue 14, September 2009
See notice on first page

PRELIMINARY

Growing/Degrowing TPU cards

Growing
CICCs
...................................................................................................................................................................................................................................
Introduction

For the benefits of a CICC addition to take effect some prerequisite conditions need to
be met.
CICC activation

A CICC card can be physically installed into the TPU shelf, but it will remain
functionally dormant until the following is accomplished:

Alcatel-Lucent is notified to update the appropriate FAF file. See also FAF/QFAF
control (p. 11-12).
The quantity of CICC cards on the ecppkt form is updated. See also ecppkt form
(p. 11-2).

Data frame selector activation

Each CICC card can provide up to 501 data frame selectors.

Some Service Providers may choose to implement the entire cache of frame selectors
immediately, or choose to implement only a portion. If done incrementally, data frame
selectors are added in increments of 10.
In any case, the addition of data frame selectors requires an update to the ecppkt form,
and an update by Alcatel-Lucent, under FAF/QFAF control. See also ecppkt form
(p. 11-2) and FAF/QFAF control (p. 11-12).
Alternate QFAF control

Calls can be rejected when a temporary spike of packet data traffic (due to a sporting
event, convention, or disaster/emergency) exceeds the cutoff point associated with the
MSC-level FS RTU (Right To Use) that is represented as FS QFAF.

PRELIMINARY

When activated with a FAF, this optional feature allows data calls to go beyond the
cutoff point associated with the FS RTU limit as to avoid call rejection in the RNC.
With the introduction of the Alternate QFAF Control feature a new call will be allowed
even when the FS QFAF for a MSC are used up. See also FAF/QFAF control
(p. 11-12).

15-46

Growing CICCs

CICC card redundancy

The redundancy strategy for CICC cards is to use the N+K model. If the number of
CICC cards needed for engineered capacity in an RNC is N<=10, then K=1. If the
number of CICC cards needed for engineered capacity in an RNC is N>10, then K=0.
In all cases, N+K CICC cards run in the active/active mode, i.e., the K CICC cards
are not cold spares.

PRELIMINARY

Growing/Degrowing TPU cards

Populating CICC slots

When a TPU shelf has empty positions in slots 7 through 16, CICCs can be inserted
into these slots to increase the capacity for handling bearer data traffic.
Note that CICCs may also be inserted in slots 5, 6, 17 and 18, if they are not
populated with B-PCFs.
CICCs should be inserted into the TPU shelf in the order shown in Figure 15-2,
GICC and CICC growth (maximum) (p. 15-5).
Procedures

The procedure for growing additional plug and play CICC cards is listed as follows:
Install plug and play CICC card in shelf (p. 15-48)

PRELIMINARY

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
15-47
Issue 14, September 2009
See notice on first page

PRELIMINARY

Growing/Degrowing TPU cards

Install
plug and play CICC card in shelf
...................................................................................................................................................................................................................................
Purpose

Perform this procedure to physically install a plug and play CICC card.
Procedure

CAUTION
ESD hazard
Static Damage Hazard!
Always wear a wriststrap to ground your body before touching the CICC card. Keep
your body grounded while handling the card. Hold the card by its edges, do not touch
any components or circuits. When the card is not in an enclosure, store it in a
staticshielding bag.
To install a CICC card in its proper slot of the TPU shelf, proceed as follows:
...................................................................................................................................................................................................

Verify that you have taken the proper anti-static precautions.

...................................................................................................................................................................................................

Verify the slot of the TPU shelf in which you will be installing the CICC card.
...................................................................................................................................................................................................

Keeping the replacement CICC card vertical, slide the card firmly into the slot between
the two guides and lock the upper and lower levers.
...................................................................................................................................................................................................

Lock the ejection levers.

PRELIMINARY

Result The following occurs:

LEDs light and some spurious alarms may be generated.

As soon as the CICC is inserted, it will issue a bootp request to the Shelf
Controller GICC.

TPU-M will dynamically detect the new CICC and inform all its northbound
clients including TCS and TPU-GUI.

It may take anywhere from 5 to 10 minutes for the three processors on the
CICC to become operational.

15-48

Install plug and play CICC card in shelf

...................................................................................................................................................................................................

Verify the Administartive, Operational, and Usage state of the CICC, via TPU GUI by:

Direct access method. See also Accessing TPU GUI (p. 6-6).
EMS. See also Logging on to Element Management System (EMS) (p. 6-5).

...................................................................................................................................................................................................

PRELIMINARY

Growing/Degrowing TPU cards

If using EMS, at the OMP Web page you need to select 1X RNC TPU Web to
navigate to the 1X RNC TPU Web page. If using the direct access method, the same
will result. See the following example screen.

...................................................................................................................................................................................................

On the 1X RNC TPU Web page select Network Elements.

PRELIMINARY

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
15-49
Issue 14, September 2009
See notice on first page

PRELIMINARY

Growing/Degrowing TPU cards

Install plug and play CICC card in shelf

Result The GUI navigates to the Network Elements page (see example screen).

...................................................................................................................................................................................................

Use the Filter: box at the top of the screen to filter on CICC and then locate the newly
installed CICC.
Result The newly-installed CICC should be in either of the following two states

PRELIMINARY

(depending on if the card is factory-new or being reused):

Admin State

Oper State

Usage State

Unlocked

Enabled

Idle or Active

Locked

Enabled

Idle or Active

See Figure 5-3,

Administrative state
(p. 5-7) for capsule
correlation.

See Figure 5-1, Operational

state (p. 5-5) for capsule
correlation.

See Figure 5-2, Usage

state (p. 5-6) for capsule
correlation.

...................................................................................................................................................................................................

If the CICC is locked perform an unlock via the Commands column.

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

15-50

Install plug and play CICC card in shelf

...................................................................................................................................................................................................

Log out by using the Logout button.

PRELIMINARY

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
15-51
Issue 14, September 2009
See notice on first page

PRELIMINARY

Growing/Degrowing TPU cards

PRELIMINARY

Growing/Degrowing TPU cards

Growing
B-PCF(s)
...................................................................................................................................................................................................................................
Introduction

The B-PCFs operate independently of one another, and are therefore grown in as
indivdual entities.
B-PCF redundancy

B-PCF redundancy uses the same strategy applied for CICCs.

Prerequisite considerations

For the benefits of a B-PCF addition to take effect, some prerequisite conditions need
to be met.
B-PCF activation

Before a B-PCF can be physically installed into a TPU shelf, the following must first
be accomplished:

Alcatel-Lucent must be notified so that the appropriate FAF file is updated. See
also FAF/QFAF control (p. 11-12).
The Max Number of B-PCFs at RNC field and (if applicable) Max Number of
B-PCFs with TCP Jitter at RNC field on the ecppkt form must be updated. See also
ecppkt form (p. 11-2).

B-PCF and PDSN considerations

Refer to B-PCFs (p. 15-54) for information concerning B-PCF and PDSN
considerations.
Criticality

PRELIMINARY

The following procedures are non-service affecting.

Duration

The following procedures take from 1.5 hours to 3.5 hours to perform.

15-52

Growing B-PCF(s)

Required Materials

This procedure requires a Solaris blade that has the most recent firmware and FMS
software installed.
Required tools

The following tools are required:

a No.2 Phillips screwdriver

an antistatic wrist strap

an electrostatic discharge mat

TPU-GUI

TPU-CLI

NTS console connection.

AP UNIX access on either one of the RNC APs. There are two methods for access:

PRELIMINARY

Growing/Degrowing TPU cards

Access the OMP Technicians menu on an OMP workstation. Select

FLEXENT(TM) AP Access at the OMP Technicians menu. Select the Frame #
and then the AP # at the Frame Access menu.
You can connect to the RNC AP using the LMT.

Populating BPCF slots

The B-PCFs can be inserted into upper and lower TPU (cPSB) shelf slots 5, 6, 17 and
18, as shown in the numbered growth sequence depicted in Figure 15-7, B-PCF
installation sequence (p. 15-54).

PRELIMINARY

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
15-53
Issue 14, September 2009
See notice on first page

PRELIMINARY

Growing/Degrowing TPU cards

Growing B-PCF(s)

Figure 15-7 B-PCF installation sequence

Required information

You must know:

What release of the software is currently running on your system.

What current AP bundle is running for B-PCFs

The BPCF root login with the factory-configured root password. Note that this
password is not currently customer-configurable, and may be amended in a future
Release.

B-PCFs

PRELIMINARY

Up to eight B-PCFs can be installed per RNC cabinet. The maximum number of
B-PCFs per shelf is four.
Dynamic and static parameters

A designated set of parameter values determines how the PCF application of the
B-PCF will function. Table 15-2, B-PCF Dynamic Parameters (p. 15-55) and Table
15-3, B-PCF Static Parameters (p. 15-58) list the applicable B-PCF parameters.
....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

15-54

Growing B-PCF(s)

These tables can be copied, and used accordingly. Some system users may choose to
use all the system defaults.
Table 15-2

B-PCF Dynamic Parameters

Tunable

Description

Range

Maximum number of
open (active and
dormant) mobiles.

Integer ranging from 0 to

10000, Default is 8000

Max. Active A8
Connections

Maximum number of
active mobiles.

Integer ranging from 0 to

1100, Default is 800

Active Session
Shutdown Threshold

Threshold for number of

active session for CP
state change to
SHUTDOWN.

Integer ranging from 0 to

1100, Default is 20

R-P Lifetime

R-P connection lifetime

(in seconds) proposed by
PCF server. This lifetime
may or may not be
accepted by the PDSN.

Integer ranging from 600

to 65534, Default is 3600

PDSN Timer

The Timeout (in

milli-seconds) when
waiting for a reply to a
registration request. The
default is 2000.

Integer ranging from 100

to 6000, Default is 2000

PDSN Retry

Number of additional
A11 registration request
retry attempts before
marking a PDSN out of
service.

Integer ranging from 0 to

10, Default is 2

Jitter Feature Enable

Used when Jitter Feature

is enabled for the B-PCF.
This feature is under
FAF/QFAF control.

Check mark indicates

enabled. Null equals
disabled. Default is null.

Delay Ack. Count

Uplink TCP/IP ACK

jitter count. For every
Delay Ack. Count,
delay the ACK by the
Delay Ack. Time.

Integer ranging from 1 to

20, Default is 8

Delay Ack. Time

Uplink TCP/IP ACK

jitter time in
milliseconds.

Integer ranging from 1 to

300, Default is 180

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
15-55
Issue 14, September 2009
See notice on first page

PRELIMINARY

Max. Open Sessions

Value

PRELIMINARY

Growing/Degrowing TPU cards

PRELIMINARY
PRELIMINARY

Growing/Degrowing TPU cards

Table 15-2

Growing B-PCF(s)

B-PCF Dynamic Parameters (continued)

Tunable

Description

Range

Delay Ack. Size

Heuristically detected
packet size. The Jitter
algorithm will apply to
all packets smaller than
this size.

Integer ranging from 4 to

100,Default is 16

APIT Initial Timer

Initial timer value for

APIT (Adaptive Packet
Inactivity Timer) in
milliseconds.

Integer ranging from

5000 to 60000, Default is
15000

APIT Inactivity Time

Inactivity time value for

APIT (Adaptive Packet
Inactivity Timer) in
milliseconds.

Integer ranging from 0 to

60000, Default is 10000

APIT Reactivation
Cost

Reactivation cost for

APIT (Adaptive Packet
Inactivity Timer) in
milliseconds.

Integer ranging from

1000 to 30000, Default is
7500

APIT Locality Margin

Locality margin for APIT

(Adaptive Packet
Inactivity Timer) in
milliseconds.

Integer ranging from 0 to

10000, Default is 5000

APIT Inter-packet
Arrival Time

Average inter packet

arrival time for APIT
(Adaptive Packet
Inactivity Timer) in
milliseconds.

Integer ranging from 0 to

25000, Default is 5000

APIT Step Down Size

Step down size for APIT

(Adaptive Packet
Inactivity Timer) in
percent.

Integer ranging from 1 to

50, Default is 10

Max. PCF Incall

When the Max PCF

Incall per second
threshold is reached, the
B-PCF will retry calls
that exceed the threshold.

Integer ranging from 1 to

100, Default is 16

Value

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

15-56

Table 15-2

Growing B-PCF(s)

B-PCF Dynamic Parameters (continued)

Tunable

Description

Range

Threshold for number

of packets within 200
ms per A10 link

This field is set to permit

a B-PCF to accept only a
certain number of
packets on each A10 link
within each 200 ms
time-window.

The default value is 20,

and the range is 10
through 200

Threshold of kilo bits

within 200 ms per
A10 link

This field is set to permit

a B-PCF to accept only
certain data bits on each
A10 link within each 200
ms time-window.

The default value is 70,

and the range is 45
through 92.

A10 incoming GRE

packet flow control

This field limits the

outgoing total number of
packets towards a B-PCF
within each 200 ms
time-window.

The default value is a

unchecked box which
indicates disabled.

B-PCF SM Reporting
Period

This field provides the

SM reporting period,
either 60 minutes or 15
minutes. See also
Change B-PCF Service
Measurement (SM)
interval (p. 10-13).

The default is 60
minutes.

Value

PRELIMINARY

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
15-57
Issue 14, September 2009
See notice on first page

PRELIMINARY

Growing/Degrowing TPU cards

PRELIMINARY
PRELIMINARY

Growing/Degrowing TPU cards

Table 15-3

Growing B-PCF(s)

B-PCF Static Parameters

Tunable

Description

Range

A8 Max MTU Size

Maximum size of packets

sent out on the A8
interface. If an A8 packet
would be larger than this
(including headers), it is
segmented into packets
of this size or smaller.
The value should be
between 576 and 1500
inclusive, or zero, which
turns off A8
segmentation. Note that,
although this tool will
allow you enter values of
one through 575, they
are not supported. If a
value in this range is
entered, it will be
overridden with the
default value of 576.

Integer ranging from 0 to

1500, Default is 576

A9 Status Inquiry
Timer

Time in seconds to check

the status of a dormant
call with the TCS

Integer ranging from

10800 to 43200, Default
is 21600

A9 PCF Count

Number of serving PCFs

in the RNC. This value
will be used for pacing
PCF_INCALLs to the
TCS.

Integer ranging from 1 to

255, Default is 4

A9 Total Incalls

Total number of
INCALLs sent to the
TCS.

Integer ranging from 1 to

255, Default is 25

Total Dormancy
Buffer Pool Size

Total size of dormancy

buffer pool (in MB).

Integer ranging from 0 to

128, Default is 16

Max. Dormancy
Buffer Per Mobile

Maximum dormancy
buffer size per mobile (in
KB).

Integer ranging from 0 to

128, Default is 8

Value

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

15-58

Table 15-3

Growing B-PCF(s)

B-PCF Static Parameters (continued)

Tunable

Description

Range

Reactivation Attempt
Timer

The number of seconds

to wait between
reactivation attempts (in
seconds).

Integer ranging from 0 to

255, Default is 30

Max. Reactivation
Attempts

Maximum number of
times to attempt
reactivation.

Integer ranging from 1 to

10, Default is 5

PPP LCP Terminate

when Dormant Enable

When a dormant call is

being closed, should the
call be reactivated in
order to deliver a PPP
LCP terminate request to
the mobile from the
PDSN?

Flag, 0 = disabled, 1 =
enabled, Default is 1

Max. PCF Restarts Per

Hour

Maximum number of
PCF Application restarts
allowed per hour. If an
application process
restarts more than this
many times in an hour,
the PCF escalates to the
next level of recovery
(PCF system
initialization). If the
entire PCF Application
(or the PCF system)
restarts more than this
many times in an hour,
the PCF Application goes
into minimum
configuration mode,
requiring operator
intervention to correct.

Integer ranging from 1 to

16, Default is 5

Value

PRELIMINARY

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
15-59
Issue 14, September 2009
See notice on first page

PRELIMINARY

Growing/Degrowing TPU cards

PRELIMINARY
PRELIMINARY

Growing/Degrowing TPU cards

Table 15-3

Growing B-PCF(s)

B-PCF Static Parameters (continued)

Tunable

Description

Range

Minor CPU Load

Threshold

Minor CPU overload

threshold (in percent). If
the PCF CPU usage
exceeds this threshold, a
minor alarm will be
generated, and a
calculated percentage of
call originations and
activations will be
denied, based on CPU
load, until the CPU
usage drops below the
minor threshold.

Integer ranging from 75

to 89, Default is 85

Major CPU Load

Threshold

Major CPU overload

threshold (in percent). If
the CPU usage exceeds
this threshold, a major
alarm will be generated,
and new calls and
reactivations will be
blocked.

Integer ranging from 90

to 100, Default is 95

Minor LAN Load

Threshold

Integer ranging from 10

to 89, Default is 80

Value

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

15-60

Table 15-3

Growing B-PCF(s)

B-PCF Static Parameters (continued)

Tunable

Description

Range

Major network overload

threshold (in percent). If
the network usage
exceeds this threshold, a
major alarm will be
generated, and new calls
and reactivations will be
blocked.

Integer ranging from 90

to 100, Default is 95

RP Interface UDP Port

R-P interface port

number. UDP port
number on which the
PCF server sends and
receives R-P interface
messages.

Integer ranging from 1 to

65535, Default is 699

Checkpoint Call State

(LLCR) Control

Checkpoint call state

(LLCR) enable/disable. If
enabled, state
information for dormant
calls will be
checkpointed, thus
allowing fast recovery
after a PCF Application
restart.

Flag, 0 = disabled, 1 =
enabled, Default is 1

PDSN Selection
Algorithm

PDSN selection
algorithm to be used. If
set to 0, then the
IOSv4.1 algorithm is
used. If set to 1, then an
improved algorithm is
used which corrects a
load balancing flaw in
the IOSv4.1 algorithm.

Integer ranging from 0 to

1, Default is 1

SDB Snoop PPP

Control

Flag to Enable/Disable
the examination of inner
IP header (contained
within a PPP frame) for
Short Data Burst (SDB)
packets.

Flag, 0 = disabled, 1 =
enabled, Default is 1

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
15-61
Issue 14, September 2009
See notice on first page

PRELIMINARY

Major LAN Load

Threshold

Value

PRELIMINARY

Growing/Degrowing TPU cards

PRELIMINARY
PRELIMINARY

Growing/Degrowing TPU cards

Table 15-3

Growing B-PCF(s)

B-PCF Static Parameters (continued)

Tunable

Description

Range

SDB Retransmit Timer

Time duration
(milli-seconds) for
re-transmission of Short
Data Burst (SDB)
packets.

Integer ranging from

1000 to 9000, Default is
5000

SDB Max. Size

Maximum size (bytes) of

a Short Data Burst
(SDB) packet.

Integer ranging from 1 to

128, Default is 128

No Page Response Number of retries

The number of
reactivation attempts
after receiving a No
Page Response denial.

Integer ranging from 0 to

10, Default is 1

No Page Response Retry Delay

After receiving a No
Page Response denial,
the number of seconds to
wait before the next
reactivation attempt.

Integer ranging from 10

to 255, Default is 20

No Page Response Initial Hysteresis

After the number of

retries have been
exhausted for the No
Page Response scenario,
the initial delay (in
seconds) before
attempting another
network reactivation.

Integer ranging from 10

to 60, Default is 20

No Page Response Maximum Hysteresis

After the number of

retries have been
exhausted for the No
Page Response scenario,
the maximum delay (in
seconds) before
attempting another
network reactivation.

Integer ranging from 10

to 600, Default is 80

Early Packet Detection

Enable

Flag to enable/disable the

examination of early A10
packets to see if they
should be buffered until
an A10 session is
established.

Integer ranging from 0 to

1, Default is 1

Value

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

15-62

Table 15-3

Growing B-PCF(s)

B-PCF Static Parameters (continued)

Tunable

Description

Range

Total size in (KB) of

early packet buffer pool
shared for all early
packets.

Integer ranging from 1 to

2000, Default is 10

Early Max Buffer Per

Mobile

Maximum size (in bytes)

of early packet buffer per
mobile.

Integer ranging from 100

to 10,000, Default is 500

System Early Max

Packet Size

Maximum size (in bytes)

to be considered an early
packet.

Integer ranging from 50

to 1,600, Default is 100

Early Max Session

Differential

Maximum number of
sessions from the most
recently established new
A10 session to be
considered an early
packet.

Integer ranging from 10

to 1,000, Default is 100

Early Hold Duration

Time (in milliseconds) to

hold an early packet
waiting for an A10
session to be established.

Integer ranging from 50

to 1,000, Default is 50

Dormant Closure Hold

Time

For an RNC/mobile
initiated dormant closure,
time (in milliseconds) to
wait for an A11
registration update.

Integer ranging from 0 to

300,000, Default is 5,000

GRE Sequencing
Timeout

GRE repetitive timer

timeout (in milliseconds)
to check for packets to
resequence.

Integer ranging from 10

to 50,000, Default is 50

GRE Out of Order A8

Timer

Time (in milliseconds) to

wait for out-of-order A8
packets to arrive.

Integer ranging from 0 to

50,000, Default is 50

GRE Out of Order

A10 Timer

Time (in milliseconds) to

wait for out-of-order A10
packets to arrive.

Integer ranging from 0 to

50,000, Default is 50

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
15-63
Issue 14, September 2009
See notice on first page

PRELIMINARY

Early Total Buffer

Pool Size

Value

PRELIMINARY

Growing/Degrowing TPU cards

PRELIMINARY
PRELIMINARY

Growing/Degrowing TPU cards

Table 15-3

Growing B-PCF(s)

B-PCF Static Parameters (continued)

Tunable
GRE Destination
Unreachable Limit

Description
Maximum number of
A10 destination
unreachable ICMP
failures before tearing
down R-P session.

Range

Value

Integer ranging from 0 to

20, Default is 3

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

15-64

Table 15-3

Growing B-PCF(s)

B-PCF Static Parameters (continued)

Tunable
BSID NID Override

Description

Range

Allows the service

provider to override the
BSID NID with an
operator configured value
without Alcatel-Lucent
intervention.

Option 1 is the default.

The following options

are provided:

If option 3 is chosen, the

operator can specify the
ID through the TPU-GUI.

1. Override the BSID

NID with the value
that is configured by
Alcatel-Lucent in the
B-PCF/E-PCF
internal procs
table.. If no value,
then pass the NID
received from the
base station.

Value

If option 2 is chosen, the

system will read the
value that is set in the
Network ID field on the
ceqface form.

PRELIMINARY

Growing/Degrowing TPU cards

Any integer from 0 to

65,535 can be
configured, but typically
the ECP ID is used.

2. Pass the NID

received from the
base station only
(ignore any internal
procs table
settings).
3. Override the BSID
NID with a
configurable ID.

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
15-65
Issue 14, September 2009
See notice on first page

PRELIMINARY

NOTE: If the NID

changes when the call is
Dormant, the PDSN will
not be notified regarding
this change during
subsequent reactivation,
unless the compliance
level is greater than or
equal to IOS 5.0. Hence,
it is recommended to set
the IOS Compliance
level to 5.0 at the TPU
GUI if the BSID NID
Override is set to
Option-2.

PRELIMINARY

Growing/Degrowing TPU cards

Table 15-3

Growing B-PCF(s)

B-PCF Static Parameters (continued)

Tunable
Provisioned ID for
BSID NID Override

Description

Range

Required when option 3

of BSID NID Override is
selected.

Integer ranging from 0 to

65,535.

Value

The BSID NID has

default value of 0 when
selecting option 3, on a
per RNC basis, and no
value is entered.
Note that when selecting
option 3, on a per B-PCF
basis, the BSID NID
value configured is not
the one configured for
the RNC.

PRELIMINARY

Fast Handoff
Pre-Registration
Timer:

This timer represents the

longest time span that
the B-PCF is willing to
accept before a fast
handoff pre-registration
for an A10 connection
expires.

Between 2 to 255
seconds.
The default is 10
seconds.

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

15-66

Table 15-3

Growing B-PCF(s)

B-PCF Static Parameters (continued)

Tunable

Description

Network Reactivation
Delay Timer:

This timer represents the

minimum time (in
milliseconds) that the
B-PCF will perform a
network reactivation after
the HHO call ends. That
is, the session goes
dormant after a fast
handoff. It is used to
address a racing
condition in which both
the mobile station and
the target PDSN detect
the need to negotiate PPP
after the fast handoff
ends. Delaying the
network reactivation will
allow for the mobile
reactivation to proceed,
which is preferred
because it saves the
paging channel resource.

Range

Value

Between 0 to 5 seconds.
The default is 3 seconds.

PRELIMINARY

Growing/Degrowing TPU cards

PDSN parameters

PDSN information for a B-PCF can be entered on a blank form such as shown in
Table 15-4, PDSN parameter form (p. 15-67). Each PDSN entry requires an IP
address, a Shared Secret Key, and a Security Parameter Index (SPI). Note that the
PDSN Management url is optional.
The Shared Secret Key and SPI can be the same for all PDSNs or different per PDSN.
.
Table 15-4

PDSN parameter form

PDSN IP Address

Shared Secret Key

SPI

URL (Optional)

____.____._____._____

____.____._____._____
____.____._____._____

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
15-67
Issue 14, September 2009
See notice on first page

PRELIMINARY

____.____._____._____

PRELIMINARY

Growing/Degrowing TPU cards

Table 15-4

Growing B-PCF(s)

PDSN parameter form (continued)

PDSN IP Address

Shared Secret Key

SPI

URL (Optional)

____.____._____._____
____.____._____._____
____.____._____._____
____.____._____._____
____.____._____._____
____.____._____._____
____.____._____._____
____.____._____._____
____.____._____._____
____.____._____._____
____.____._____._____
____.____._____._____
____.____._____._____
____.____._____._____
____.____._____._____
____.____._____._____

Common PDSN parameters

The common PDSN parameters for the B-PCF is provided in Table 15-5, PDSN
Parameters (p. 15-68). Also see Table 15-6, Failed PSDN action (p. 15-74).
The values specified in the blank column of Table 15-5, PDSN Parameters (p. 15-68)
will be applied to all or individual PDSNs specified for the B-PCF. See also example
blank form of Table 15-4, PDSN parameter form (p. 15-67).
Table 15-5
Type

PRELIMINARY

Dynamic

PDSN Parameters
Tunable

Description

Range

PDSN
Management
URL

The URL, if it exists, is

the management URL for
the PDSN.

A closing pipe
(|) must be
present, even if a
URL is not
specified.

Value

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

15-68

Table 15-5
Type

Growing B-PCF(s)

PDSN Parameters (continued)

Tunable

Description

Range

Dynamic

PDSN
Shared
Secret

The value of Shared

Secret is known by the
B-PCF and PDSN.

Shared Secret
values starting
with 0x are
converted to
hexadecimal.

Dynamic

PDSN SPI

The same SPI must be

provisioned on both the
B-PCF and PDSN.

Numerics, such
as 0 through
232, are valid
data types.

Dynamic

R-P Lifetime
Minimum

Minimum allowable R-P

interface lifetime. If the
PDSN repeatedly
proposes a lifetime less
than this value, the PCF
will mark the PDSN
out-of-service. This
tunable is used to avoid
unnecessary load on the
PCF by reducing the
frequency with which R-P
lifetimes are refreshed. In
general, as the maximum
number of open sessions
is increased, the minimum
R-P lifetime should also
be increased.

Integer ranging
from 300 to
3600, Default is
600

Value

PRELIMINARY

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
15-69
Issue 14, September 2009
See notice on first page

PRELIMINARY

Growing/Degrowing TPU cards

PRELIMINARY

Growing/Degrowing TPU cards

Table 15-5
Type
Dynamic

Growing B-PCF(s)

PDSN Parameters (continued)

Tunable
R-P
Standards
Compliance

Description
Version of IOS 4.x
standard that should be
followed when sending
R-P signaling (A11)
messages.

Range

Value

0 indicates that
IOS 4.0
compatible
messages are
sent.
1 indicates that
IOS 4.1
messages are
sent.
2 indicates that
IOS 4.2
messages are
sent.
3 indicates that
IOS 4.3
messages are
sent.

PRELIMINARY

Default is 1
Dynamic

R-P ID Time
Tolerance

R-P interface
identification field time
tolerance (in seconds). If
a registration update is
received with an
identification field outside
this tolerance limit, it will
be rejected by the PCF
server.

Integer ranging
from 0 to 86400,
Default is 7

Dynamic

Failed
PDSN Timer

How long to wait before

sending new connection
requests to a PDSN which
the PCF server has been
marked out-of-service (in
seconds). A value of 0
indicates that new
connection requests
should never again be
sent to the PDSN.

Integer ranging
from 0 to 86400,
Default is 600

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

15-70

Table 15-5
Type

Growing B-PCF(s)

PDSN Parameters (continued)

Tunable

Description

Range

Dynamic

PDSN
Heartbeat
Type

Type of heartbeat to use

with PDSNs. If set to 0,
then heartbeating will be
disabled. If set to 1, then
an A11 RRQ message will
be used. If set to 2, then
an ICMP ping message
will be used.

Integer ranging
from 0 to 2,
Default is 1

Dynamic

ESN
Accounting
Extension
Enable

Flag to indicate if the

ESN extension should be
included in accounting
records for IOS 4.0 and
4.1 compliance levels.

0 indicates that
the ESN will not
be included.

When the IOS compliance

level is 4.2 or greater, the
tunable will be ignored
and the ESN will be
included.

Value

PRELIMINARY

Growing/Degrowing TPU cards

1 indicates that
the ESN will be
included.
Default is 0

For an IOS level of 4.0,

4.1, or 4.3, it is sent as
26/52.
For an IOS level of 4.2, it
is sent as 26/48.

PRELIMINARY

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
15-71
Issue 14, September 2009
See notice on first page

PRELIMINARY

Growing/Degrowing TPU cards

Table 15-5
Type
Dynamic

Growing B-PCF(s)

PDSN Parameters (continued)

Tunable
Pass Cell
Info to
PDSN

Description
Should the cell info be
sent to the PDSN in the
BSC ID field of the R-P
connection setup?

If 0, then the BSC ID

field is set to all 0s.

If 1, then only the

CSN is passed.

If 2, then both the

CSN and PAF are
passed (pre-standard);
PAF (4 bits) followed
by CSN (12 bits).

If 3, then both the

CSN and PAF are
passed (IS-835B);
CSN (12 bits)
followed by PAF (4
bits).

Range

Value

Integer ranging
from 0 to 3,
Required,
Default is 0

For 3 and 4, CSNs must

be less than 4096.
Dynamic

PDSN A11
state after
failure/
denial

Controls OOS/Degraded
state treatment when a
PDSN failure occurs. This
tunable does not control
no response treatment.

0=
OOS/Degraded
1 = Degraded
2 = No Change
(See also Table
15-6, Failed
PSDN action
(p. 15-74).)

PRELIMINARY

Default is 0

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

15-72

Table 15-5
Type
Dynamic

Growing B-PCF(s)

PDSN Parameters (continued)

Tunable
Reject A11
Session
Update
Parameter
Enable

Description

Range

Allows PDSN to send

R-P session parameters to
the B-PCF. For example,
Always On indicator.

0 = A11-Session
Update Ack is
sent with status
0x00 which
represents
Update
Accepted.

Value

PRELIMINARY

Growing/Degrowing TPU cards

1 = A11-Session
Update Ack is
sent with status
0xC9 which
represents
Update Denied
- Session
Parameters Not
Updated.
Default is 1
Dynamic

Dynamic

R-P Use
Common
VSA Header

R-P Active
Time
Parameter
Type

Specifies how multiple

3GPP2 (vendor specific)
airlink parameters in a
single A11 RRQ message
are to be encoded.
Specifically, multiple
vendor-specific
parameters encoded using:

A single,
Vendor-Specific
Attribute (VSA)
header.

Separate VSA
headers.

1 = Single VSA
hearder
Default is 0

0=
RADIUS/3GPP2
type 26/49
1 = RADIUS
type 46
Default is 0

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
15-73
Issue 14, September 2009
See notice on first page

PRELIMINARY

Specifies the
RADIUS/3GPP2 type to
use when sending the
Active Time airlink
parameter in A11 RRQ
Active Stop.

0 = Separate
VSA headrers

PRELIMINARY

Growing/Degrowing TPU cards

Table 15-5
Type

PDSN Parameters (continued)

Tunable

Description

Dynamic

MEID added
to airlink
accounting
record:

Provides support of
Mobile Equipment ID
(MEID) in the RNC, and
also insures that the
MEID, if available, is
provided on the billing
interfaces (CDR and
airlink records). This field
is always enabled when
the value of RP
Standards Compliance is
greater than 3.

Checkmark to
enable. The
default is no
checkmark.

Dynamic

Fast
Handoff
Enable

Specifies whether a
particular PDSN in a
PDSN pool supports fast
handoff.

Checkmark to
enable. The
default is no
checkmark.

Static

Degraded
PDSN
Threshold

High water mark for error

count before marking
PDSN Degraded.

1 through 100

Degraded
PDSN Drip
Period
(Milliseconds)

Drip period (in

milliseconds) for
Degraded leaky bucket
counter.

100 through
3600000

OOS PDSN
Threshold

High water mark for error

count before marking
PDSN Out-of-Service.

1 through 100

OOS PDSN
Drip Period
(Milliseconds)

Drip period (in

milliseconds) for
Out-of-Service. leaky
bucket counter.

100 through
3600000

Static

Table 15-6

PRELIMINARY

Growing B-PCF(s)

Range

Value

Default is 1

Default is 60000

Default is 1

Default is 60000

Failed PSDN action

Failure Description

RRP denial code #129 received

OOS

Degraded

No Change

RRP denial code #130 received

Degraded

No Change

All other RRP denial codes

OOS

Degraded

No Change

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

15-74

Table 15-6

Growing B-PCF(s)

Failed PSDN action

(continued)

Failure Description

A10 lifetime in RRP is out-of-range

OOS

Degraded

No Change

A10 ICMP Destination Unreachable

failure

OOS

Degraded

No Change

No response to RRQ

OOS

Zero lifetime in response to RRQ

w/Connection Setup

Degraded

No Change

#136 (redirect) denial for existing session

Degraded

No Change

#136 (redirect) denial to unavailable

PDSN

Degraded

No Change

PRELIMINARY

Growing/Degrowing TPU cards

Procedures

The procedures associated with growing an additional B-PCF card are listed as
follows:
Configure B-PCF (p. 15-76)
Configure PDSN(s) (p. 15-83)
Physically install B-PCF in TPU shelf (p. 15-92)

PRELIMINARY

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
15-75
Issue 14, September 2009
See notice on first page

PRELIMINARY

Growing/Degrowing TPU cards

Configure
B-PCF
...................................................................................................................................................................................................................................
Purpose

Perform this procedure to configure a B-PCF card via the TPU-GUI Blade Packet
Control Functions (BPCFs) page.
B-PCF parameter options

Two TPU GUI screens are used to configure the B-PCF parameter options:

Configure Common BPCF Parameters screen

Configure BPCF Parameters screen

The Configure BPCF Parameters screen also contains one additional field under
Dynamic Parameters designated as Jitter Feature Enable.
Common B-PCF parameters screen

The Common BPCF Parameters screen is used when the Service Provider wishes to
apply the same B-PCF parameters across all B-PCFs in the RNC.
When the first B-PCF is added in an RNC, Service Providers have the following
options of:

Using the Common BPCF Parameters screen, and its default parameters. In this
case no further action is required once the B-PCF is added via the Configure
BPCFs-Add/Delete page

Using the Common BPCF Parameters screen, and modifying some or all of the
B-PCF parameters for use by any and all subsequent B-PCFs that are grown-in
later. In this case the Common BPCF Parameters screen is normally modified
when the first B-PCF is added. All subsequent B-PCFs that are added will then by
default, be setup with the same parameters.

Note that at any time, these common B-PCF parameters may later be changed by
accessing the Configure BPCFs-Add/Delete page, and using the same method
outlined in the procedure that follows.
Configure BPCF Parameters screen

PRELIMINARY

The Configure BPCF Parameters screen is used when the Service Provider wishes to
apply customized B-PCF parameters to any or all B-PCFs used in the RNC.
Note that at any time, the B-PCF parameters for an individual B-PCF may later be
changed by accessing the Configure BPCFs-Add/Delete page, and using the same
method outlined in the procedure that follows.
Before you begin

Before beginning, ensure that the criteria specified under B-PCF activation (p. 15-52)
has been satisfied.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

15-76

Configure B-PCF

Procedure

To configure a B-PCF card via the TPU-GUI Blade Packet Control Functions (BPCFs)
page, proceed as follows:
...................................................................................................................................................................................................

Obtain access to TPU-GUI either by:

Direct access method. See also Accessing TPU GUI (p. 6-6).

EMS. See also Logging on to Element Management System (EMS) (p. 6-5).

PRELIMINARY

Growing/Degrowing TPU cards

...................................................................................................................................................................................................

If using EMS, at the OMP Web page you need to select 1X RNC TPU Web to
navigate to the 1X RNC TPU Web page. If using the direct access method, the same
will result. See the following example screen.

...................................................................................................................................................................................................

Click on the BPCFs icon.

PRELIMINARY

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
15-77
Issue 14, September 2009
See notice on first page

PRELIMINARY

Growing/Degrowing TPU cards

Configure B-PCF

Result The GUI navigates to the Blade Packet Control Function (BPCFs) page

(see example screen).

...................................................................................................................................................................................................

PRELIMINARY

Click on the BPCF Configuration Data icon.

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

15-78

Configure B-PCF

Result The GUI navigates to the Configure BPCFs-Add/Delete page (see the

following example).

PRELIMINARY

Growing/Degrowing TPU cards

...................................................................................................................................................................................................

Enter the Shelf ID and Slot No. information in the Add BPCF: boxes .OPTIONAL:
If the TCP Jitter feature needs to be enabled, click to put a check mark in the Jitter
box.
...................................................................................................................................................................................................

Click the

icon to add the new B-PCF.

Result The OK confirmation box (similar to the following example) appears.

PRELIMINARY

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
15-79
Issue 14, September 2009
See notice on first page

PRELIMINARY

Growing/Degrowing TPU cards

Configure B-PCF

...................................................................................................................................................................................................

Click on OK.
Result The following occurs:

The newly added B-PCFs row is displayed on the Configure BPCFs page.

The following prompt box appears, and you have the following options:

You can click on OK and then configure PDSN data as described in the
Configure PDSN(s) procedure.

You can defer on configuring PDSN data at this time by clicking on Cancel
and proceeding with Step 8.

...................................................................................................................................................................................................

Depending on your preference:

1. Click on the Configure Common BPCF Parameter icon (located above the Add
BPCF: box) to configure the common B-PCF parameters (used across all B-PCFs).

PRELIMINARY

2. Click on the Configure icon (located in the row of the B-PCF that you just added)
to configure B-PCF parameters, on a per B-PCF basis.

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

15-80

Configure B-PCF

Result Either the Configure Common BPCF Parameters screen, or the

Configure BPCF Parameters screen appears, as shown in Example 1 and Example

2 that follow.

PRELIMINARY

Growing/Degrowing TPU cards

...................................................................................................................................................................................................

Enter the appropriate configuration parameter values (see also Table 15-2, B-PCF
Dynamic Parameters (p. 15-55) and Table 15-4, PDSN parameter form (p. 15-67)).
...................................................................................................................................................................................................

Click on the Submit button.

Result The following occurs:

All the parameters are inserted into the database.

DUA will create and SFTP the new config.ini file to the TPU shelf.

The TPU GUI navigates back to the Configure BPCFs screen.

...................................................................................................................................................................................................

Repeat Step 5 through Step 10 for any additional B-PCFs that are being added.

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
15-81
Issue 14, September 2009
See notice on first page

PRELIMINARY

Growing/Degrowing TPU cards

Configure B-PCF

...................................................................................................................................................................................................

When you are finished configuring B-PCFs, click on the Done button on the
Configure BPCFs screen.
Result The TPU GUI navigates back to the Blade Packet Control Functions
(BPCFs) screen.
...................................................................................................................................................................................................

Proceed to Configure PDSN(s) (p. 15-83) (if required) or log off by clicking on the
Logout button, and proceed to Physically install B-PCF in TPU shelf (p. 15-92).
END OF STEPS

PRELIMINARY

...................................................................................................................................................................................................

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

15-82

Configure
PDSN(s)
...................................................................................................................................................................................................................................
Purpose

Perform this procedure to configure PDSN(s) via the TPU-GUI Configure PDSNs
page.

PRELIMINARY

Growing/Degrowing TPU cards

PDSN parameter options

Two TPU GUI screens are used to configure the PDSN parameter options:

Configure PDSN Pool Parameters screen

Configure PDSN Parameters screen

The Configure PDSN Parameters screen also contains one additional field designated
as PDSN Management URL:.
Configure PDSN pool parameters screen

The Configure PDSN Pool Parameters screen is used when the Service Provider
wishes to apply the same PDSN parameters across all PDSNs used with the RNC.
Important! Only the first two fields (PDSN Shared Secret and PDSN SPI) need
to be individualized per the customers requirements. The rest of the fields are
filled in with default values, and should not be modified, unless specifically
directed. Note also, that the PDSN Shared Secret and PDSN SPI fields fields
could differ between PDSNs, and therefore the differing information would then
require modification via the Configure PDSN Parameters screen.
Also note that, when required, the common PDSN parameters may at any time be
changed by accessing the Configure PDSNs page, and using the same method outlined
in the procedure that follows.
Configure PDSN parameters screen

The Configure PDSN Parameters screen is used when the Service Provider wishes to
apply customized PDSN parameters to any or all PDSNs used with the RNC.
Note that at any time, the PDSN parameters for an individual PDSN may later be
changed by accessing the Configure PDSNs page, and using the same method outlined
in the procedure that follows.
Before you begin

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
15-83
Issue 14, September 2009
See notice on first page

PRELIMINARY

Before beginning, obtain the IP address or IP addresses of the PDSN(s) that are to be
configured.

PRELIMINARY

Growing/Degrowing TPU cards

Configure PDSN(s)

Procedure

To configure a PDSN via the TPU-GUI Blade Packet Control Functions (BPCFs)
page, proceed as follows:
...................................................................................................................................................................................................

Obtain access to TPU-GUI either by:

Direct access method. See also Accessing TPU GUI (p. 6-6).

EMS. See also Logging on to Element Management System (EMS) (p. 6-5).

...................................................................................................................................................................................................

If using EMS, at the OMP Web page you need to select 1X RNC TPU Web to
navigate to the 1X RNC TPU Web page. If using the direct access method, the same
will result. See the following example screen.

...................................................................................................................................................................................................

PRELIMINARY

Click on the Configuration Data icon.

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

15-84

Configure PDSN(s)

Result The GUI navigates to the RNC Configuration Data page (see the

following example screen).

PRELIMINARY

Growing/Degrowing TPU cards

...................................................................................................................................................................................................

Click on the Global Configuration Data button.

PRELIMINARY

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
15-85
Issue 14, September 2009
See notice on first page

PRELIMINARY

Growing/Degrowing TPU cards

Configure PDSN(s)

Result The GUI navigates to the Global Configuration Data page (see the

following example screen).

...................................................................................................................................................................................................

PRELIMINARY

Click on the PDSN Configuration link.

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

15-86

Configure PDSN(s)

Result The GUI navigates to the PDSN Configuration link (see example screen

that follows).

PRELIMINARY

Growing/Degrowing TPU cards

...................................................................................................................................................................................................

Enter the IP address information in the IP Address: box under Add PDSN:.
...................................................................................................................................................................................................

Click the

icon to add the new PDSN.

PRELIMINARY

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
15-87
Issue 14, September 2009
See notice on first page

PRELIMINARY

Growing/Degrowing TPU cards

Configure PDSN(s)

Result The OK confirmation box (similar to the following example) appears.

...................................................................................................................................................................................................

Click on OK.
Result The newly added PDSNs row is displayed on the Configure PDSNs page.
...................................................................................................................................................................................................

At this point you have the following options (see also PDSN parameter options
(p. 15-83)):

If the PDSN that you are adding is going to use the common PDSN pool
parameters currently provisioned, proceed to Step 14.

If the PDSN that you are adding is going to use the common PDSN pool
parameters, but you now wish to modify the common PDSN pool parameters used
across all PDSNs, proceed to Step 10.

If the PDSN that you are adding requires customized PDSN parameters, proceed to
Step 12.

...................................................................................................................................................................................................

PRELIMINARY

Click on the Configure Common PDSN Pool Parameter icon (located above the IP
Address: box ) to configure the common PDSN pool parameters (used across all
PDSNs).

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

15-88

Configure PDSN(s)

Result The Configure PDSN Pool Parameters screen appears, as shown in the

following example.

PRELIMINARY

Growing/Degrowing TPU cards

...................................................................................................................................................................................................

Proceed to Step 13.

...................................................................................................................................................................................................

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
15-89
Issue 14, September 2009
See notice on first page

PRELIMINARY

Click on the Configure icon (located in the row of the PDSN that you just added) to
configure PDSN parameters, on a per PDSN basis.

PRELIMINARY

Growing/Degrowing TPU cards

Configure PDSN(s)

Result The Configure PDSN Parameters screen appears, as shown in the

following example.

...................................................................................................................................................................................................

Enter the appropriate configuration parameter values (see also Table 15-5, PDSN
Parameters (p. 15-68)).

PRELIMINARY

...................................................................................................................................................................................................

Important! For each process, DUA will report the first message to the ROP.
Thereafter, the messages will be throttled such that only every seventh message
will be reported to the ROP.
Click on the Submit button.

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

15-90

Configure PDSN(s)

Result The following occurs:

All the parameters are inserted into the database.

DUA will create and SFTP the new config.ini file to the TPU shelf.

The TPU GUI navigates back to the Configure PDSNs screen.

...................................................................................................................................................................................................

PRELIMINARY

Growing/Degrowing TPU cards

Repeat Step 6 through Step 14 for any additional PDSNs that are being added.
...................................................................................................................................................................................................

When you are finished configuring PDSNs, click on the Done button on the Configure
PDSNs page.
Result The TPU GUI navigates back to the Global Configuration Data screen.
...................................................................................................................................................................................................

Click on the Logout button to log off.

...................................................................................................................................................................................................

If required, proceed to Physically install B-PCF in TPU shelf (p. 15-92).

PRELIMINARY

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
15-91
Issue 14, September 2009
See notice on first page

PRELIMINARY

Growing/Degrowing TPU cards

Physically
install B-PCF in TPU shelf
...................................................................................................................................................................................................................................
Purpose

Perform this procedure to physically install a B-PCF card.

Before you begin

Ensure that the slot is configured before you insert the B-PCF. If it is not configured,
and the B-PCF is inserted, the system will assume that the newly inserted card is a
CICC.
Procedure

To install a B-PCF card in its proper slot of the TPU shelf, proceed as follows:
...................................................................................................................................................................................................

Attach an antistatic wrist strap.

...................................................................................................................................................................................................

Slide the B-PCF board into the appropriate slot, and align the top and bottom mounting
rails. Then move the blade toward the backplane while gently pushing the board
handles inward (this may require both hands).
Result The following occurs:

The blue Hot Swap LED and green Ready LED light.
The new B-PCF begins to initialize.

...................................................................................................................................................................................................

After the B-PCF has initialized, obtain access to the B-PCF through the NTS console
connection. See also Required tools (p. 15-53) for connection information.
...................................................................................................................................................................................................

From the OMP Shell start an SSH session through the NTS to the B-PCF console by
entering the following command:

PRELIMINARY

SSH NTS_IP_address port_number

where:
NTS_IP_address is the customer provided or the factory default NTS IP address.

15-92

Physically install B-PCF in TPU shelf

port_number is the port number for the B-PCF shown in Table 15-7, B-PCF port

numbers (p. 15-93).

Table 15-7

B-PCF port numbers

For...

Enter Port Number...

B-PCF in Upper shelf slot 05

3600

B-PCF in Lower shelf slot 05

5500

B-PCF in Upper shelf slot 18

2300

B-PCF in Lower shelf slot 18

4300

B-PCF in Upper shelf slot 06

2400

B-PCF in Lower shelf slot 06

4400

B-PCF in Upper shelf slot 17

2300

B-PCF in Lower shelf slot 17

4300

PRELIMINARY

Growing/Degrowing TPU cards

Notes:

...................................................................................................................................................................................................

Press the Enter key to get the login prompt.

...................................................................................................................................................................................................

Login to the B-PCF console as root. See the following example:

Important! When the script initiated by the following command is run, you will
need to answer the prompts in the order that they are outputted.
Configure DHCP and the host name on the B-PCF by entering the following
commands from the B-PCF:

./flxdhcpcfg

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
15-93
Issue 14, September 2009
See notice on first page

PRELIMINARY

cd /flx/FMSadmin/current/bin/

PRELIMINARY

Growing/Degrowing TPU cards

Physically install B-PCF in TPU shelf

Result A script is outputted, such as shown in the following example:

Modify the .rhosts file on the B-PCF by entering the following commands on the
B-PCF:
cd /
vi .rhosts
...................................................................................................................................................................................................

In vi insert the IP addresses of the primary and secondary RNC AP on the AP Dual
Rail LAN, as follows:
172.Y.128.sp
172.Y.128.ss

PRELIMINARY

where:
Y is the second octet of the RNC APs IP address on AP Dual Rail LAN network. The

value ranges from 16 to 31.

15-94

Physically install B-PCF in TPU shelf

...................................................................................................................................................................................................

Reboot the B-PCF by entering the following command on the B-PCF:

PRELIMINARY

Growing/Degrowing TPU cards

sync;/etc/reboot

Result The B-PCF reboots.

...................................................................................................................................................................................................

Verify that the B-PCF has been assigned an IP address by the GICC. Enter the
following command:
ifconfig a

Result The SC-GICC assigns the B-PCFs dmfe0 interface an IP address in the

subnet (for upper TPU shelf B-PCFs) or subnet (for lower TPU shelf B-PCFs). See
the following output example, and note that it displays a B-PCF in TPU 1, Slot
Number 5:

1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
lo0: flags=1000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4> mtu 8232
1234567890123456789012345678901212345678901234567890123456789
index 1 inet 127.0.0.1 netmask ff000000
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
dmfe0:flags=1004843<UP,BROADCAST,RUNNING,MULTICAST,DHCP,IPv4>
mtu 1500
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789

index 2

...................................................................................................................................................................................................

Log out of the B-PCF by entering the following command:

Terminate the Console connection to the B-PCF by entering the following commands:
ctrl-]

...................................................................................................................................................................................................

Access AP UNIX on either one of the RNC APs. See also Required tools (p. 15-53)
for connection information.

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
15-95
Issue 14, September 2009
See notice on first page

PRELIMINARY

quit

PRELIMINARY

Growing/Degrowing TPU cards

Physically install B-PCF in TPU shelf

...................................................................................................................................................................................................

Login to the RNC AP as root,

...................................................................................................................................................................................................

Access TPU CLI from the RNC-AP by entering the following command:
TPUCLI<CR>
...................................................................................................................................................................................................

Obtain the name of the latest software version for the B-PCF by entering the following
TPU CLI command:
get, rnc f, install, version<CR>

where: f = RNC Frame number (1-15).

Transfer the B-PCF bundle file from the RNC-AP to the B-PCFs /var/flx/bun directory
by entering the following TPU CLI command:
install:rnc f,tpu s, bpcf b,version Version_String<CR>

where:
f = RNC Frame number (1-15)
s = TPU Shelf number (1-2)
b = BPCF Slot number (5, 6, 17, 18)
Version_String = B-PCF software version. For example:BPCF23L20.0

Important! The system will issue a reminder to lock the B-PCF. Ignore this
message.
Result The B-PCF bundle is transferred from the RNC-AP to the B-PCF.
...................................................................................................................................................................................................

Execute and activate the bundle by entering the following command:

bpcf_update -rnc f -tpu s -bpcf b -activate<CR>

where:

PRELIMINARY

f = RNC Frame number (1-15)

s = TPU Shelf number (1-2)
b = BPCF Slot number (5, 6, 17, 18)

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

15-96

Physically install B-PCF in TPU shelf

Result The script will output progress messages and generate error messages for

Wait for the Script to complete and display a success message (after the B-PCF
reboots).

PRELIMINARY

Growing/Degrowing TPU cards

...................................................................................................................................................................................................

Logout of the RNC-AP by entering the following command:

exit<CR>
...................................................................................................................................................................................................

Login to the OAM Proxy AP as root.

...................................................................................................................................................................................................

Verify that the B-PCF is unlocked by entering the following TPU-CLI command:
get: rnc f, tpu s, bpcf b, state<CR>

where:
f = RNC Frame number (1-15)
s = TPU Shelf number (1-2)
b = BPCF Slot number (5, 6, 17, 18)

Result An output similar to the following will occur:

If the B-PCF is reported to be in a locked state, then enter the following TPU-CLI
command
unlock: rnc f, tpu s, bpcf b<CR>

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
15-97
Issue 14, September 2009
See notice on first page

PRELIMINARY

...................................................................................................................................................................................................

PRELIMINARY

Growing/Degrowing TPU cards

Physically install B-PCF in TPU shelf

where:
f = RNC Frame number (1-15)
s = TPU Shelf number (1-2)
b = BPCF Slot number (5, 6, 17, 18)
END OF STEPS

PRELIMINARY

...................................................................................................................................................................................................

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

15-98

De-Growth
Overview
...................................................................................................................................................................................................................................

PRELIMINARY

Growing/Degrowing TPU cards

Purpose

When future conditions dictate that the TPU shelves in an RNC cabinet either need to
be redeployed or removed from service, the service provider can begin the
redeployment/removal process by deactivitating and removing the GICC, CICC, and
B-PCF cards. By the same token, individual OC3 ports on installed GICC cards can
also be deactivated when required.
GICC and CICC depopulation rules

The GICC cards are degrown in pairs starting with slot 19, then slot 4, and finally slot
20. For CICC cards (also degrown in pairs) the degrowth pattern alternates inwardly
toward the center of the shelf starting at slot 7, then slot 16, slot 8, slot 15, and so on.
See Figure 15-8, GICC and CICC Degrowth (p. 15-100) for further clarification.
Note that if CICCs are populated in slots 5, 6, 17 or18, the order of degrowth is
extended outwardly.

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
15-99
Issue 14, September 2009
See notice on first page

PRELIMINARY

Growing/Degrowing TPU cards

Overview

Figure 15-8 GICC and CICC Degrowth

OC3 facilities

OC3 ports are arranged in order (1 through 4) on the GICC card. They are degrown
from top (fourth port) to bottom (first port).

PRELIMINARY

Contents
Degrowing GICCs

15-102

Shutdown the GICC card

15-103

Degrow GICC via TPU GUI

15-106

Remove GICC card

15-112

Degrowing 5E gateway on used OC3 port

15-116

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

15-100

Overview

Shutdown the 5EGW

15-117

Deprovision 5E gateway(s) on GICC

15-120

Degrowing CICCs

15-127

Shutdown the CICC card

15-128

Remove plug and play CICC from shelf

15-131

Degrowing a B-PCF

15-135

Shutdown B-PCF

15-136

Halt B-PCF

15-140

Delete B-PCF presence from RNC Database

15-142

Physically remove B-PCF

15-147

PRELIMINARY

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
15-101
Issue 14, September 2009
See notice on first page

PRELIMINARY

Growing/Degrowing TPU cards

PRELIMINARY

Growing/Degrowing TPU cards

Degrowing
GICCs
...................................................................................................................................................................................................................................
Introduction

When conditions neccessitate that a GICC card needs to be degrown, use the
procedures provided herein to accomplish the task.
Important! Degrowing a GICC may cause an outage on an in-service system! Only
degrow a GICC if you are sure that the service on that GICC is no longer needed.
Degrowth factors

Factors that may dictate the necessity for degrowing a GICC are listed as follows:

System operation may have been compromised, in some way, after growth of a
GICC and it is first necessary to determine if the GICC growth is a contributing
factor.

Service Measurement data indicates that a previously grown GICC would be better
utilized in another location.

Required tools

The following tools are required:

An antistatic wrist strap

An electrostatic discharge mat

A No. 2 Phillips scewdriver

Required interfaces

The following interface is required: TPU-GUI.

Procedures

The procedures for degrowing GICC cards are listed as follows:

Shutdown the GICC card (p. 15-103)
Degrow GICC via TPU GUI (p. 15-106)

PRELIMINARY

Remove GICC card (p. 15-112)

15-102

Shutdown
the GICC card
...................................................................................................................................................................................................................................
Purpose

To gracefully shutdown a GICC card prior to degrowth.

Procedure

PRELIMINARY

Growing/Degrowing TPU cards

To gracefully shutdown a GICC card prior to degrowth, proceed as follows:

...................................................................................................................................................................................................

Obtain access to TPU-GUI either by:

Direct access method. See also Accessing TPU GUI (p. 6-6).

EMS. See also Logging on to Element Management System (EMS) (p. 6-5).

...................................................................................................................................................................................................

If using EMS, at the OMP Web page you need to select 1X RNC TPU Web to
navigate to the 1X RNC TPU Web page. If using the direct access method, the same
will result. See the following example screen.

On the 1X RNC TPU Web page select Network Elements.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
15-103
Issue 14, September 2009
See notice on first page

PRELIMINARY

...................................................................................................................................................................................................

PRELIMINARY

Growing/Degrowing TPU cards

Shutdown the GICC card

Result The GUI navigates to the Network Elements page (see example screen).

...................................................................................................................................................................................................

Choose the GICC that you wish to shutdown, and choose Shutdown via the
Commands column.
Result The following will occur:

PRELIMINARY

Shutdown Accepted will initially appear in the Command Status column.

After two minutes, the GICC will transition to:

Admin State

Oper State

Usage State

Locked

Disabled

Idle

See Figure 5-3,

Administrative state
(p. 5-7) for capsule
correlation.

See Figure 5-1,

Operational state (p. 5-5)
for capsule correlation.

See Figure 5-2, Usage

state (p. 5-6) for capsule
correlation.

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

15-104

Shutdown the GICC card

...................................................................................................................................................................................................

Refresh the browser (if necessary) to verify the transition.

...................................................................................................................................................................................................

Proceed to Degrow GICC via TPU GUI (p. 15-106).

END OF STEPS

PRELIMINARY

Growing/Degrowing TPU cards

...................................................................................................................................................................................................

PRELIMINARY

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
15-105
Issue 14, September 2009
See notice on first page

PRELIMINARY

Growing/Degrowing TPU cards

Degrow
GICC via TPU GUI
...................................................................................................................................................................................................................................
Purpose

Perform this procedure to remove a GICC card presence from the TPU-GUI.
Before you begin

Before proceeding, ensure that the GICC has been shutdown, see Shutdown the GICC
card (p. 15-103).
Procedure

To remove a GICC card presence from the TPU-GUI, proceed as folows:

...................................................................................................................................................................................................

Obtain access to TPU-GUI either by:

Direct access method. See also Accessing TPU GUI (p. 6-6).
EMS. See also Logging on to Element Management System (EMS) (p. 6-5).

PRELIMINARY

If using EMS, at the OMP Web page you need to select 1X RNC TPU Web to
navigate to the 1X RNC TPU Web page. If using the direct access method, the same
will result. See the following example screen.

15-106

Degrow GICC via TPU GUI

...................................................................................................................................................................................................

On the 1X RNC TPU Web page select Configuration Data.

Result The GUI navigates to the RNC Configuration Data page (see example

screen).

PRELIMINARY

Growing/Degrowing TPU cards

...................................................................................................................................................................................................

On the RNC Configuration Data page under Wizards select De-growth next to GICC
Growth.

PRELIMINARY

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
15-107
Issue 14, September 2009
See notice on first page

PRELIMINARY

Growing/Degrowing TPU cards

Degrow GICC via TPU GUI

Result The GUI navigates to the De-grow GICC-Warning Message pane (see

example screen).

...................................................................................................................................................................................................

PRELIMINARY

Select the Next button to move to the next page.

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

15-108

Degrow GICC via TPU GUI

Result The GUI navigates to the De-Grow GICC-GICC Degrow- Selection page

(see example screen).

PRELIMINARY

Growing/Degrowing TPU cards

...................................................................................................................................................................................................

Select the number of GICC pairs that you intend to de-grow (2, 4, or 6).
...................................................................................................................................................................................................

Select the Submit button.

PRELIMINARY

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
15-109
Issue 14, September 2009
See notice on first page

PRELIMINARY

Growing/Degrowing TPU cards

Degrow GICC via TPU GUI

Result The GUI navigates to the De-Grow GICC - Summary Page (see the

following example).

...................................................................................................................................................................................................

If you are not satsified that the GICC summary coincides with the GICC degrowth that
you are initiating, return to the previous screen. Otherwise, click on Next.
Result The Confirm degrow GICC box is displayed (see example screen that

PRELIMINARY

follows).

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

15-110

Degrow GICC via TPU GUI

...................................................................................................................................................................................................

Select Yes.
Result The Message GICC degrowth success box is displayed (see example screen

that follows).

PRELIMINARY

Growing/Degrowing TPU cards

...................................................................................................................................................................................................

Select OK.
Important! Depending on system activity, a successful degrow of a GICC may
require between one to two minutes for the GICC status to be updated on the TPU
GUI.
Result GUI returns to RNC Configuration Data page.
...................................................................................................................................................................................................

Log out by using the Logout button.

...................................................................................................................................................................................................

Proceed to Remove GICC card (p. 15-112).

PRELIMINARY

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
15-111
Issue 14, September 2009
See notice on first page

PRELIMINARY

Growing/Degrowing TPU cards

Remove
GICC card
...................................................................................................................................................................................................................................
Purpose

Perform this procedure to remove a GICC card after performing the appropriate
deprovisioning procedures.
Procedure

CAUTION
ESD hazard
Static Damage Hazard!
Always wear a wriststrap to ground your body before touching the GICC card. Keep
your body grounded while handling the card. Hold the card by its edges, do not touch
any components or circuits. When the card is not in an enclosure, store it in a
staticshielding bag.
To remove a GICC card from the TPU shelf, proceed as follows:
...................................................................................................................................................................................................

Obtain an anti-static bag in which to place the GICC card.

...................................................................................................................................................................................................

Verify that you have taken the proper anti-static precautions.

...................................................................................................................................................................................................

CAUTION
Laser hazard
Laser Beam Hazard!
Never look directly into the open end of a functioning optic cable, even if you are
certain that it is not currently functioning, or even connected at the other end.
Although the laser beams strength is insufficient to harm exposed skin, or damage
combustible maerials, eye damage can occur if you stare directly into the beam for a
prolonged period.

PRELIMINARY

Verify the slot of the TPU shelf from which you will be removing the GICC card.
...................................................................................................................................................................................................

Disconnect the GIGE and OC3 connections. (You can also wait to do this until after
the GICC is removed.)

15-112

Remove GICC card

...................................................................................................................................................................................................

Loosen the GICCs upper and lower retention retention screws (see Figure 15-9,
Loosen GICC retention screws (p. 15-113)).
Figure 15-9 Loosen GICC retention screws

PRELIMINARY

Growing/Degrowing TPU cards

...................................................................................................................................................................................................

Signal the GICC that it is about to be removed by (with equal pressure) partially
unlatching the top and bottom ejector levers (Figure 15-10, Partially eject GICC
(p. 15-114)).

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
15-113
Issue 14, September 2009
See notice on first page

PRELIMINARY

Important! Do not fully open the ejector at this point because that action levers the
board out of the enclosure, and the midplane connection will be broken before it
has shut down properly .

PRELIMINARY

Growing/Degrowing TPU cards

Remove GICC card

Figure 15-10 Partially eject GICC

...................................................................................................................................................................................................

PRELIMINARY

With equal pressure, press upward and downward on the two ejector levers on the card
to fully unseat the card from the chassis.
...................................................................................................................................................................................................

Slide the card out and place it on the electrostatic discharge mat.

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

15-114

Remove GICC card

...................................................................................................................................................................................................

Place the GICC in the anti-static bag and place it in the appropriate storage area.
END OF STEPS
...................................................................................................................................................................................................

PRELIMINARY

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
15-115
Issue 14, September 2009
See notice on first page

PRELIMINARY

Growing/Degrowing TPU cards

PRELIMINARY

Growing/Degrowing TPU cards

Degrowing
5E gateway on used OC3 port
...................................................................................................................................................................................................................................
Introduction

When conditions neccessitate that an individual OC3 port needs to have its associated
5E gateway degrown, use the procedures provided herein to accomplish the task.
5EGW redundancy

If APS is enabled 5EGWs will be degrown in pairs. See also Chapter 13, Automatic
Protection Switching (APS).
Procedures

The procedures for deactivating an OC3 port as a 5E gateway are listed as follows:
Shutdown the 5EGW (p. 15-117)

PRELIMINARY

Deprovision 5E gateway(s) on GICC (p. 15-120)

15-116

Shutdown
the 5EGW
...................................................................................................................................................................................................................................
Purpose

To gracefully shutdown a 5EGW (APS disabled) or both 5EGWs in a pair (APS

enabled) prior to degrowth.

PRELIMINARY

Growing/Degrowing TPU cards

Procedure

To gracefully shutdown a 5EGW (APS disabled) or 5EGW pair (APS enabled)pair

prior to degrowth, proceed as follows:
...................................................................................................................................................................................................

Obtain access to TPU-GUI either by:

Direct access method. See also Accessing TPU GUI (p. 6-6).
EMS. See also Logging on to Element Management System (EMS) (p. 6-5).

...................................................................................................................................................................................................

If using EMS, at the OMP Web page you need to select 1X RNC TPU Web to
navigate to the 1X RNC TPU Web page. If using the direct access method, the same
will result. See the following example screen.

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
15-117
Issue 14, September 2009
See notice on first page

PRELIMINARY

Growing/Degrowing TPU cards

Shutdown the 5EGW

...................................................................................................................................................................................................

On the 1X RNC TPU Web page select Network Elements.

Result The GUI navigates to the Network Elements page (see example screen).

...................................................................................................................................................................................................

Use the Filter: box at the top of the screen to filter on ATM.
...................................................................................................................................................................................................

Important! Only the ATM services on the SC-GICC should be locked and
degrown. Locking the SC-GICC itself will cause a service interruption! Make sure
that you select the ATM 5EGW that needs to be shutdown and NOT the entire
GICC.

PRELIMINARY

Choose the ATM 5EGW(s) that you wish to shutdown, and choose Shutdown via the
Commands column.

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

15-118

Shutdown the 5EGW

Result The following will occur:

Shutdown Accepted will initially appear in the Command Status column.

After two minutes, the 5EGW will transition to:

Admin State

Oper State

Usage State

Locked

Disabled

Idle

See Figure 5-3,

Administrative state
(p. 5-7) for capsule
correlation.

See Figure 5-1,

Operational state (p. 5-5)
for capsule correlation.

PRELIMINARY

Growing/Degrowing TPU cards

See Figure 5-2, Usage

state (p. 5-6) for capsule
correlation.

...................................................................................................................................................................................................

Refresh the browser (if necessary) to verify the transition.

...................................................................................................................................................................................................

If APS is enabled repeat Step 5 for the other 5EGW of the pair.
...................................................................................................................................................................................................

Proceed to Deprovision 5E gateway(s) on GICC (p. 15-120).

PRELIMINARY

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
15-119
Issue 14, September 2009
See notice on first page

PRELIMINARY

Growing/Degrowing TPU cards

Deprovision
5E gateway(s) on GICC
...................................................................................................................................................................................................................................
Purpose

Perform this procedure to deprovision 5E gateway(s) on a GICC card.

Procedure

To deprovision 5E gateway(s) on a GICC card, proceed as folows:

...................................................................................................................................................................................................

Obtain access to TPU-GUI either by:

Direct access method. See also Accessing TPU GUI (p. 6-6).

EMS. See also Logging on to Element Management System (EMS) (p. 6-5).
Result If using EMS, at the OMP Web page you need to select 1X RNC TPU Web

PRELIMINARY

to navigate to the 1X RNC TPU Web page. If using the direct access method, the
same will result. See the following example screen.

...................................................................................................................................................................................................

On the 1X RNC TPU Web page select Configuration Data.

15-120

Deprovision 5E gateway(s) on GICC

Result The GUI navigates to the RNC Configuration Data page (see example

screen).

PRELIMINARY

Growing/Degrowing TPU cards

...................................................................................................................................................................................................

On the RNC Configuration Data page under Wizards select De-Growth next to 5E
GW Growth.

PRELIMINARY

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
15-121
Issue 14, September 2009
See notice on first page

PRELIMINARY

Growing/Degrowing TPU cards

Deprovision 5E gateway(s) on GICC

Result The GUI navigates to the De-Grow 5EGWs - Warning Message page (see

example screen that follows).

...................................................................................................................................................................................................

PRELIMINARY

Select the Next button to move to the next page.

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

15-122

Deprovision 5E gateway(s) on GICC

Result The GUI navigates to the De-Grow 5E-GWs - DEGROW PSU Selection

page. See the following example screens of Figure 15-11, Without APS enabled
(p. 15-123) and Figure 15-12, With APS enabled (p. 15-124).
Figure 15-11 Without APS enabled

PRELIMINARY

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
15-123
Issue 14, September 2009
See notice on first page

PRELIMINARY

Growing/Degrowing TPU cards

PRELIMINARY

Growing/Degrowing TPU cards

Deprovision 5E gateway(s) on GICC

Figure 15-12 With APS enabled

...................................................................................................................................................................................................

Select the 5EGW port (APS disabled) or ports (APS enabled) that you intend to
de-grow via the down arrowhead, and change to UNUSED.
Note that with APS enabled, you only need to input changes to Shelf 1:Working
GICCs. The changes will be mirrored on Shelf 2:Protection GICCs.
...................................................................................................................................................................................................

PRELIMINARY

Select the Next button.

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

15-124

Deprovision 5E gateway(s) on GICC

Result The GUI navigates to the De-Grow 5E-GWs - Summary page.

PRELIMINARY

Growing/Degrowing TPU cards

...................................................................................................................................................................................................

Click on Submit.
Result The Confirm 5EGW degrow box is displayed (see example screen that

follows)

Select Yes.

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
15-125
Issue 14, September 2009
See notice on first page

PRELIMINARY

...................................................................................................................................................................................................

PRELIMINARY

Growing/Degrowing TPU cards

Deprovision 5E gateway(s) on GICC

Result The Message 5EGW degrowth success box is displayed (see example

screen that follows).

...................................................................................................................................................................................................

Select OK.
Result GUI returns to RNC Configuration Data page.
...................................................................................................................................................................................................

Log out by using the Logout button.

END OF STEPS

PRELIMINARY

...................................................................................................................................................................................................

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

15-126

Degrowing
CICCs
...................................................................................................................................................................................................................................
Introduction

When conditions neccessitate that an individual CICC card or all CICC cards need to
be degrown, use the procedures provided herein to accomplish the task.

PRELIMINARY

Growing/Degrowing TPU cards

Procedures

The procedures for degrowing CICC cards are listed as follows:

Shutdown the CICC card (p. 15-128)
Remove plug and play CICC from shelf (p. 15-131)

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
15-127
Issue 14, September 2009
See notice on first page

PRELIMINARY

Growing/Degrowing TPU cards

Shutdown
the CICC card
...................................................................................................................................................................................................................................
Purpose

To gracefully shutdown a CICC card prior to removing it from the TPU shelf.
Procedure

To gracefully shutdown a CICC card prior to removing it from the TPU shelf, proceed
as follows:
...................................................................................................................................................................................................

Obtain access to TPU-GUI either by:

Direct access method. See also Accessing TPU GUI (p. 6-6).

EMS. See also Logging on to Element Management System (EMS) (p. 6-5).

...................................................................................................................................................................................................

PRELIMINARY

If using EMS, at the OMP Web page you need to select 1X RNC TPU Web to
navigate to the 1X RNC TPU Web page. If using the direct access method, the same
will result. See the following example screen.

...................................................................................................................................................................................................

On the 1X RNC TPU Web page select Network Elements.

15-128

Shutdown the CICC card

Result The GUI navigates to the Network Elements page (see example screen).

PRELIMINARY

Growing/Degrowing TPU cards

...................................................................................................................................................................................................

Use the Filter: box at the top of the screen to filter on CICC.
...................................................................................................................................................................................................

Choose the CICC that you wish to shutdown, and choose Shutdown via the
Commands column.
Result The following will occur:

Shutdown Accepted will initially appear in the Command Status column.

After a pre-determined time, the CICC will transition to:

Oper State

Usage State

Locked

Disabled

Idle

See Figure 5-3,

Administrative state
(p. 5-7) for capsule
correlation.

See Figure 5-1,

Operational state (p. 5-5)
for capsule correlation.

See Figure 5-2, Usage

state (p. 5-6) for capsule
correlation.

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
15-129
Issue 14, September 2009
See notice on first page

PRELIMINARY

Admin State

PRELIMINARY

Growing/Degrowing TPU cards

Shutdown the CICC card

...................................................................................................................................................................................................

Refresh the browser (if necessary) to verify the transition.

...................................................................................................................................................................................................

Proceed to Remove plug and play CICC from shelf (p. 15-131).
END OF STEPS

PRELIMINARY

...................................................................................................................................................................................................

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

15-130

Remove
plug and play CICC from shelf
...................................................................................................................................................................................................................................
Purpose

Perform this procedure to physically remove a plug and play CICC card.
Procedure

PRELIMINARY

Growing/Degrowing TPU cards

CAUTION
ESD hazard
Static Damamge Hazard!
Always wear a wriststrap to ground your body before touching the CICC card. Keep
your body grounded while handling the card. Hold the card by its edges, do not touch
any components or circuits. When the card is not in an enclosure, store it in a
staticshielding bag.
To remove a CICC card from the TPU shelf, proceed as follows:
...................................................................................................................................................................................................

Obtain an anti-static bag in which to place the CICC card.

...................................................................................................................................................................................................

Verify that you have taken the proper anti-static precautions.

...................................................................................................................................................................................................

Verify the slot of the TPU shelf from which you will be removing the CICC card.
...................................................................................................................................................................................................

If applicable, disconnect any of the 3 console ports or the Ethernet connection,

...................................................................................................................................................................................................

Loosen the CICCs upper and lower retention screws (see Figure 15-13, Loosen CICC
retention screws (p. 15-132)).

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
15-131
Issue 14, September 2009
See notice on first page

PRELIMINARY

Growing/Degrowing TPU cards

Remove plug and play CICC from shelf

Figure 15-13 Loosen CICC retention screws

...................................................................................................................................................................................................

PRELIMINARY

Signal the CICC that it is about to be removed by (with equal pressure) partially
unlatching the top and bottom ejector levers (Figure 15-14, Partially eject CICC
(p. 15-133)).

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

15-132

Remove plug and play CICC from shelf

Figure 15-14 Partially eject CICC

PRELIMINARY

Growing/Degrowing TPU cards

...................................................................................................................................................................................................

With equal pressure, press upward and downward on the two ejection levers on the
card to fully unseat the card from the chassis.

Slide the card out and place it on the electrostatic discharge mat.

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
15-133
Issue 14, September 2009
See notice on first page

PRELIMINARY

...................................................................................................................................................................................................

PRELIMINARY
PRELIMINARY

Growing/Degrowing TPU cards

Remove plug and play CICC from shelf

...................................................................................................................................................................................................

Place the CICC in the anti-static bag and place it in the appropriate storage area.
END OF STEPS
...................................................................................................................................................................................................

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

15-134

Degrowing
a B-PCF
...................................................................................................................................................................................................................................
Introduction

After a B-PCF is grown, factors may later arise that dictate the necessity for degrowing
the B-PCF.

PRELIMINARY

Growing/Degrowing TPU cards

Degrowth factors

Factors that may dictate the necessity for degrowing a B-PCF are listed as follows:

System operation may have been compromised, in some way, after growth of a
B-PCF and it is first necessary to determine if the B-PCF growth is a contributing
factor.
Service Measurement data indicates that a previously grown B-PCF would be better
utilized in another location.

Procedures

The procedures associated with degrowing a B-PCF card are listed as follows:
Shutdown B-PCF (p. 15-136)
Halt B-PCF (p. 15-140)
Delete B-PCF presence from RNC Database (p. 15-142)
Physically remove B-PCF (p. 15-147)

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
15-135
Issue 14, September 2009
See notice on first page

PRELIMINARY

Growing/Degrowing TPU cards

Shutdown
B-PCF
...................................................................................................................................................................................................................................
Purpose

Perform this procedure to gracefullyshutdown the PCF application of the B-PCF card
allowing currently active sessions to drain, but blocking all future calls.
Reason to perform

See Degrowth factors (p. 15-135).

Required interfaces

The following interface is required: TPU-CLI

Procedure

To gracefully shutdown a B-PCF card, proceed as follows:

...................................................................................................................................................................................................

Obtain access to TPU-GUI either by:

Direct access method. See also Accessing TPU GUI (p. 6-6).

EMS. See also Logging on to Element Management System (EMS) (p. 6-5).

...................................................................................................................................................................................................

PRELIMINARY

If using EMS, at the OMP Web page you need to select 1X RNC TPU Web to
navigate to the 1X RNC TPU Web page. If using the direct access method, the same
will result. See the following example screen.

15-136

Shutdown B-PCF

PRELIMINARY

Growing/Degrowing TPU cards

...................................................................................................................................................................................................

On the 1X RNC TPU Web page select Network Elements.

PRELIMINARY

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
15-137
Issue 14, September 2009
See notice on first page

PRELIMINARY

Growing/Degrowing TPU cards

Shutdown B-PCF

Result The GUI navigates to the Network Elements page (see example screen).

...................................................................................................................................................................................................

Use the Filter: box at the top of the screen to filter on BPCF.
...................................................................................................................................................................................................

Choose the B-PCF that you wish to shutdown, and choose Shutdown via the
Commands column.
Result The following will occur:

PRELIMINARY

Shutdown Accepted will initially appear in the Command Status column.

After two minutes, the B-PCF will transition to:

Admin State

Oper State

Usage State

Locked

Disabled

Idle

See Figure 5-3,

Administrative state
(p. 5-7) for capsule
correlation.

See Figure 5-1,

Operational state
(p. 5-5) for capsule
correlation.

See Figure 5-2, Usage

state (p. 5-6) for capsule
correlation.

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

15-138

Shutdown B-PCF

...................................................................................................................................................................................................

Refresh the browser (if necessary) to verify the transition.

...................................................................................................................................................................................................

Proceed to Halt B-PCF (p. 15-140).

END OF STEPS

PRELIMINARY

Growing/Degrowing TPU cards

...................................................................................................................................................................................................

PRELIMINARY

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
15-139
Issue 14, September 2009
See notice on first page

PRELIMINARY

Growing/Degrowing TPU cards

Halt
B-PCF
...................................................................................................................................................................................................................................
Purpose

Perform this procedure to halt the hard disk of the B-PCF card (similar to park heads
command on a PC) prior to physically removing the B-PCF card.
Reason to perform

Action is necessary to safeguard the B-PCF hard disk prior to physically removing a
B-PCF card from the TPU shelf after the card has been previously shutdown.
Required interfaces

The following interface is required: TPU-CLI

Before you begin

Ensure that the following procedure has previously been performed:

Shutdown B-PCF (p. 15-136)

Procedure

To halt a B-PCF hard disk, proceed as follows:

...................................................................................................................................................................................................

PRELIMINARY

On the Network Elements page (see the following example) use the Filter: box at the
top of the screen to filter on BPCF if BPCF is not currently selected. .

15-140

Halt B-PCF

PRELIMINARY

Growing/Degrowing TPU cards

...................................................................................................................................................................................................

Choose the B-PCF that you previously shutdown, and select Halt via the Commands
column. Note that Halt will not appear unless the B-PCF has been previously
shutdown.
Result The following will occur:

Halt Accepted will initially appear in the Command Status column.

The B-PCF halts.

...................................................................................................................................................................................................

Proceed to Delete B-PCF presence from RNC Database (p. 15-142).

PRELIMINARY

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
15-141
Issue 14, September 2009
See notice on first page

PRELIMINARY

Growing/Degrowing TPU cards

Delete
B-PCF presence from RNC Database
...................................................................................................................................................................................................................................
Purpose

Perform this procedure to delete the B-PCF presence from the RNC database prior to
physically removing the B-PCF card.
Reason to perform

This action is necessary to delete the B-PCF presence from the RNC database prior to
physically removing a B-PCF card from the TPU shelf.
Required interfaces

The following interface is required: TPU-GUI.

Before you begin

Ensure that the following procedures have previously been performed:

Shutdown B-PCF (p. 15-136)

Halt B-PCF (p. 15-140)

Procedure

To delete the B-PCF presence from the RNC Database, proceed as follows:
...................................................................................................................................................................................................

PRELIMINARY

Navigate back to the 1X RNC TPU Web page. See the following example screen.

15-142

Delete B-PCF presence from RNC Database

PRELIMINARY

Growing/Degrowing TPU cards

...................................................................................................................................................................................................

Click on the BPCFs icon.

PRELIMINARY

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
15-143
Issue 14, September 2009
See notice on first page

PRELIMINARY

Growing/Degrowing TPU cards

Delete B-PCF presence from RNC Database

Result The GUI navigates to the Blade Packet Control Function (BPCFs) page

(see example screen).

...................................................................................................................................................................................................

PRELIMINARY

Click on the BPCF Configuration Data icon.

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

15-144

Delete B-PCF presence from RNC Database

Result The GUI navigates to the Configure BPCFs-Add/Delete page (see example

screen):

PRELIMINARY

Growing/Degrowing TPU cards

...................................................................................................................................................................................................

To delete a B-PCF, click inside the Existing BPCFs: box in the row of the B-PCF that
you wish to delete.
Result A check mark will appear.
...................................................................................................................................................................................................

Click the

icon to delete the B-PCF.

PRELIMINARY

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
15-145
Issue 14, September 2009
See notice on first page

PRELIMINARY

Growing/Degrowing TPU cards

Delete B-PCF presence from RNC Database

Result A delete confirmation box such as shown in the following example

appears.

...................................................................................................................................................................................................

Click on OK.
Result The row containing the B-PCF that you just degrew is deleted.
...................................................................................................................................................................................................

Click on Done.
Result The TPU-GUI navigates back to the Blade Packet Control Function
(BPCFs) page.
...................................................................................................................................................................................................

Logout from the TPU-GUI by hitting the Logout button.

Important! Depending on system activity, a successful degrow of a B-PCF may
require between one to two minutes for the B-PCF status to be updated on the
TPU-GUI.
...................................................................................................................................................................................................

Proceed to Physically remove B-PCF (p. 15-147).

END OF STEPS

PRELIMINARY

...................................................................................................................................................................................................

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

15-146

Physically
remove B-PCF
...................................................................................................................................................................................................................................
Purpose

Perform this procedure to physically remove the B-PCF card from the TPU shelf.
Reason to perform

PRELIMINARY

Growing/Degrowing TPU cards

See Degrowth factors (p. 15-135).

Required tools

The following tools are required:

An antistatic wrist strap

An electrostatic discharge mat

A No. 2 Phillips screwdriver

Before you begin

Ensure that the following procedures have previously been performed:

Shutdown B-PCF (p. 15-136)

Halt B-PCF (p. 15-140)

Delete B-PCF presence from RNC Database (p. 15-142)

Procedure

To physically remove the B-PCF from the TPU shelf, proceed as follows:
...................................................................................................................................................................................................

Obtain an anti-static bag in which to place the B-PCF card.

...................................................................................................................................................................................................

Attach an antistatic wrist strap.

...................................................................................................................................................................................................

Verify the slot of the TPU shelf from which you will be removing the B-PCF card.
...................................................................................................................................................................................................

Using the No2. Phillips screw driver, unscrew the B-PCFs upper and lower retention
screws that fasten the blade to the TPU shelf.

Signal the B-PCF that it is about to be removed by (with equal pressure) partially
unlatching the top and bottom ejector levers.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
15-147
Issue 14, September 2009
See notice on first page

PRELIMINARY

...................................................................................................................................................................................................

PRELIMINARY

Growing/Degrowing TPU cards

Physically remove B-PCF

Important! Do not fully open the ejector at this point because that action levers the
board out of the enclosure, and the midplane connection will be broken before it
has shut down properly.
...................................................................................................................................................................................................

Place the B-PCF in the anti-static bag and place it in the appropriate storage area.
END OF STEPS

PRELIMINARY

...................................................................................................................................................................................................

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

15-148

PRELIMINARY

Part VI: Security management

Security management for CDMA 1X RNC deals with intentional and unintentional
threats to network information coming from within the service providers organization,
and also from external sources.
Secure networking

Secure networking within and between the RNC, other system components, and outside
systems can be segmented into networking zones. The following zones (see the
following Figure) exist:

Northbound Maintenance WAN

AP LAN
RNC Internal LAN

Service-bearing IP networks

Northbound Maintenance WAN

An intranet within the service providers organization that connects MSCs and other
network elements to element management systems, OSS, and maintenance user
workstations. The OMP and the OAM Proxy APs connect to this zone.

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
VI-1
Issue 14, September 2009
See notice on first page

PRELIMINARY

Security management

Overview

PRELIMINARY

AP LAN

The isolated LAN segment within the MM-AP cluster. This zone carries call
processing/signaling and maintenance traffic for voice and data services.

VI-2

Overview

RNC Internal LAN

The isolated LAN segment within each RNC. This zone carries call
processing/signaling, bearer, and maintenance traffic between RNC components.
Service-bearing IP networks

In schematic terms, this consists of the R-P interface network, the Packet Data
Network (PDN), and the public Internet. Security for service-bearing IP networks is
governed by the standards adopted by the individual sevice provider.

PRELIMINARY

Security management

RNC security administration

The System Administrator has control of user IDs and passwords for access to all
RNC-client related applications.
User interfaces

The OMP is the major maintenance platform for the RNC, providing secure access (see
also OMP security guidelines (p. 16-3)) to the following user interfaces:

SDP

EMS-GUI

TPU-GUI
TICLI

TPU-CLI

Recent Change/Verify (RC/V)

User name/password synchronization across any of the RNC user interfaces that
require user name/password authentication is governed by the procedures and methods
applicable to that interface.
Contents
Chapter 16, Managing security

16-1

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
VI-3
Issue 14, September 2009
See notice on first page

PRELIMINARY

Managing security
16

To provide the security management guidelines applicable for the CDMA 1X RNC.
Contents
Wireless network interfaces

16-2

OMP security guidelines

16-3

OMC-RAN security levels

16-4

MM-APC security management

16-5

Eliminate open consoles

16-6
16-10

TPU GUI login security administration

16-11

TPU GUI login synchronization

16-13

Adminstrator tasks

16-15

Add local TPU GUI user

16-17

Edit local TPU GUI user access profile

16-22

Delete local TPU GUI system user

16-26

Clear configuration lock

16-30

Reactivate local TPU GUI user

16-34

Verify EMS user accounts synchronization status

16-38

Updating local TPU GUI password

16-40

Change local password

16-41

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
16-1
Issue 14, September 2009
See notice on first page

PRELIMINARY

Centralized security management phase three

PRELIMINARY

Managing security

Wireless network interfaces

Security for CDMA 1X RNC wireless network interfaces is managed via the OMP,
OMC-RAN, and MM-AP platforms.
Contents
OMP security guidelines

16-3

OMC-RAN security levels

16-4

MM-APC security management

16-5

Eliminate open consoles

16-6

PRELIMINARY

Centralized security management phase three

16-10

16-2

OMP
security guidelines
...................................................................................................................................................................................................................................
Introduction

The OMP provides the major platform for the OA&M capabilities specific to all
Wireless Network related products. As such, it is the service providers responsibility
to create and maintain a secure OMP environment.

PRELIMINARY

Managing security

Documentation

Information pertinent to maintaing the security of the OMP can be found in

Alcatel-Lucent Technologies Practice 401-662-108. The major topics discussed in this
document are listed as follows:

General Security Guidelines

OMP Basic Security

Securing the OMP Network

Local OMP Ethernet Network Security

OMP Ethernet Network Connections

Firewalls or Routers with Filters

Virtual Private Networks (VPNs)

Securing the Solaris Operating System

Unnecessary inet.conf Services

Automated Security Enhancement TOOL (ASET)

Solaris Security Enhancements

Recent Change/Verify (RC/V) Security Logging

OMP Login Administration

Creating OMP Logins

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
16-3
Issue 14, September 2009
See notice on first page

PRELIMINARY
PRELIMINARY

Managing security

OMC-RAN
security levels
...................................................................................................................................................................................................................................
Introduction

Refer to 401-380-835, Alcatel-Lucent CDMA Network Operations and Maintenance

Center - Radio Access Network - Operations, Administration, Maintenance, and
Provisioning for information pertaining to OMC-RAN security levels.

16-4

MM-APC
security management
...................................................................................................................................................................................................................................
Introduction

The two Ethernet switches of the MM-APC (LAN switches A and B) provide
redundant LAN connections for each Application Processor (for example, MM-AP,
RNC-AP, OAM Proxy) in the MM-AP Frame (MM-APF) and between the OMP.

PRELIMINARY

Managing security

Documentation

Information pertinent to maintaing the security of the MM-APC can be found in

Alcatel-Lucent Practice 401-710-201. The major topics discussed in this document are
listed as follows:

Network Security Guidelines

Login Security Guidelines

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
16-5
Issue 14, September 2009
See notice on first page

PRELIMINARY

Managing security

Eliminate
open consoles
...................................................................................................................................................................................................................................
Introduction

At times, Alcatel-Lucent is required to physically access console ports on network

elements (GICCs and CICCs) to resolve problems.
Inherent vulnerability

Prior to Release 29.0, an inherent vulnerability existed in this process because user
authentication was not provided in the network elements resident operating system.
User IDs and passwords

In Release 29.0 and beyond, user IDs and passwords for VxWorks processors will be
required by Alacatel-Lucent personnel when connecting to the processor blades
console port as well as when accessing the blade over the network.
The login/password values will depend on flags set via the RCV forms and the
corresponding user IDs that are provisioned.
Security administration

These logins will be administered by the service providers resident security/system

administrator by means of the centralized RC/V interface.
The user logins provisioned at the RC/V are intended mainly for login access to the
VxWorks boards for troubleshooting purposes only. The logins can be created when
technicians need to access the VxWorks boards. When there is no such need, all the
user name and passwords can be removed to maximize security access.
Default login and password

A default login is provided to enable Alacatel-Lucent personnel access to the

GICC/CICC cards in the initial stages just after the retrofit. The default login value for
GICC/CICC cards is lucent and the password is password.

PRELIMINARY

The default user name and password may or may not exist on GICC/CICC cards
depending on different scenarios, or in some cases different conditions after
initialization. Detailed scenarios when the default user name is valid/invalid are given
in the following paragraphs.
mscsec form

The mscsec form has been modified to include the following new field to control
security management:

1X RNC Security Zone

16-6

Eliminate open consoles

PRELIMINARY

Managing security

Value is 0 (off) and has never been 1 (on)

If the 1X RNC Security Zone value is 0 (off) and has never been 1 (on), the default
user name and password will be in effect on all the TPU cards. Users will be able to
login remotely, or through the console using the defaults.
Value is 0 (off) but was previously 1 (on)

If the 1X RNC Security Zone value is 0 (off), but was previously 1 (on) either of the
following scenarios may be true:

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
16-7
Issue 14, September 2009
See notice on first page

PRELIMINARY

The 1X RNC Security Zone value currently is 0 (off), but the TPU card was not
rebooted after the value was set to 0 (off). In this case, the default user name
password is removed from the card, and the card can only be accessed by using the
user name(s) and password(s) configured via the pwdadm form at the time that the
1X RNC Security Zone value was set to on. However, if no user names exist on
the pwdadm form, then the card cannot be accessed for security reasons.
The current 1X RNC Security Zone value is 0 (off), but the TPU card was
rebooted after the value was set to 0 (off). In this case the card can be accessed by
using the default user name/password.

PRELIMINARY

Managing security

Eliminate open consoles

Value is 1 (on)

If the 1X RNC Security Zone value is 1 (on), the latest user name/password values on
the pwdadm form will be downloaded to the TPU cards and the default values of the
user name/password will be removed. The default user name would not be applicable
even if the pwdadm form user entries are empty.
Users will be able to login remotely to the TP or through the TP console port using the
user names/passwords listed in the RC/V form.
If the pwdadm form is not populated, users will not be able to login remotely to the TP
or through the console port. If a user wants to log on to the TP, the pwdadm form
should be updated with user name(s) and password(s).
Summary

To summarize, the 1X RNC GICCs and CICCs may not all authenticate the same set
of user IDs and logins. Consistent authentication can be restored by setting the 1X
RNC Security Zone value to 1 (on) via the mscsec RC/V form. In which case all the
GICCs and CICCs will authenticate the provisioned user IDs and passwords, and reject
the default user ID and password.
pwdadm form

PRELIMINARY

The pwdadm form has been modified to include a new screen to support provisioning
of up to 10 user IDs along with its associated password.

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

16-8

Eliminate open consoles

PRELIMINARY

Managing security

Recommendations

It is recommended that the security administrator add at least one new user
name/password to the pwdadm form as soon as retrofit is completed. This will erase
the default user name and password on the TPU cards. The security administrator can
then delete the new user, if not needed.

PRELIMINARY

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
16-9
Issue 14, September 2009
See notice on first page

PRELIMINARY

Managing security

Centralized
security management phase three
...................................................................................................................................................................................................................................
Introduction

Centralized security management for RNC has been expanded and enhanced to provide
additional security capabilities.
Overview

Centralized security management provides the measures to increase the network

security for CDMA RNCs. With this feature 1xRNC will make use of Secure Shell
(SSH) in both Solaris and VxWorks environment within the 1xRNC security zone.
The 1xRNC security zone is comprised of:

RNC-AP

SC-GICC
GICCs

CICCs

BPCFs

Previously, the 1xRNC supported insecure protocols such as rlogin, rsh, telnet, rcp, and
ftp on both the OS environments. With this feature, the insecure protocols are replaced
by ssh, scp, and sftp.
Feature enabled

When this feature is enabled, 1xRNC will no longer permit the use of insecure
protocols. Also this feature will use SSH for OAM communication within the 1xRNC
security zone.
Login to the TPU cards as follows:

Login to the GICC/CICC cards from the RNC-AP using:

ssh IPAddress t vxShell

Login to the BPCF cards from the RNC-AP using:

ssh IPAddress

Note also, that Dynamic Updates and Software Installation will be done using secure
protocols like SFTP/SCP.

PRELIMINARY

Additional information

For a complete description of this feature, refer to 401-662-112, Alcatel-Lucent CDMA

Network Centralized Security Management Security Administration Guide.

16-10

TPU GUI login security administration

PRELIMINARY

Managing security

Purpose

User and password security for the TPU GUI is provided by means of:

The OMP through TPU GUI login syncronization.

Local TPU GUI admin/user screens.

TPU GUI login synchronization

TPU GUI login synchronization allows for the use of shared logins and passwords on
both the OMP and TPU GUI. This synchronization is most essential in allowing system
users to navigate from EMS GUI to TPU GUI by means of using one shared login and
password for accessing both GUIs.
For Release 24.0 and beyond, synchronization between the logins and passwords used
for accessing the OMP and TPU GUI is automated.
Local TPU GUI admin/user screens

At the local TPU GUI level, login and password administration may also be performed
via TPU GUI screens. Two types of security access profiles are defined for login and
password access at this local level:

ADMIN

USER

These local TPU GUI security profiles give Service Providers who may choose not to
use the OMP method the means for administering TPU GUI login and password
security. Additionally, Service Providers that use the OMP method are also provided
with an alternative means for assigning local TPU GUI adminstrators, and for
assigning local TPU GUI user logins that may not require access beyond TPU GUI.
ADMIN profile

Add local TPU GUI user

16-17

Edit local TPU GUI user access profile

16-22

Delete local TPU GUI system user

16-26

Clear configuration lock

16-30

Reactivate local TPU GUI user

16-34

Verify EMS user accounts synchronization status

16-38

Updating local TPU GUI password

16-40

Change local password

16-41

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

16-12

TPU
GUI login synchronization
...................................................................................................................................................................................................................................
Introduction

The use of multiple logins and passwords can create confusion for system users;
therefore, login and password administration for the TPU GUI is simplified by
allowing logins and passwords previously created on the OMP to serve for the TPU
GUI as well.

PRELIMINARY

Managing security

OMP logins

Logins created on the OMP are either given the privilege level of an administrator, or
of a technician. These logins are then assigned to serve in one or more security groups.
(Depending upon the Service Providers preference.)
Security groups

Security groups are setup to organize, and also limit, the various system tasks and
functions that OMP assigned administrators and technicians are allowed to perform.
For example, RC/V, TICLI, EMS, call trace.
The following security groups are currently valid on the OMP:

dcs

ecp

ompadmin

ompshell

arladmin

mcrt

ems

emscm

tools

ecpshell

hcama

vs01-vs16

Important! Only the ompadmin, ems, and emscm security groups are valid for use
with the TPU GUI.

For information regarding the following, refer either to 401-662-102.

Enabling password synchronization functionality.

Disabling password synchronization functionality.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
16-13
Issue 14, September 2009
See notice on first page

PRELIMINARY

EMS-TPU GUI login synchronization

PRELIMINARY

Managing security

TPU GUI login synchronization

Synchronizing logins manually.

Checking the status of EMS-TPU GUI login syncronization.

Synchronization of a login update between the OMP and TPU GUI will result
anywhere from 15 to 30 minutes after the update is completed at the OMP. (Depending
on system activity.)
TPU GUI ADMIN logins

In the current implementation, any user login assigned in the ems security group of the
OMP is by default assigned administrator (ADMIN) privleges on the TPU GUI. OMP
assigned administrator or technician status is irrelevant at the TPU GUI.
Note, that there is no limit on the number of user logins that may serve in the ADMIN
capacity.
TPU GUI USER logins

PRELIMINARY

In the current implementation, any user login assigned in either security group ems or
emscm of the OMP are by default assigned technician (USER) privleges on the TPU
GUI. OMP assigned administrator or technician status is irrelevant at the TPU GUI.

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

16-14

Adminstrator
tasks
...................................................................................................................................................................................................................................
Introduction

An administrator (locally assigned or OMP assigned) is provided with the capability

for administering the TPU GUI via TPU GUI screens.

PRELIMINARY

Managing security

Tasks

The tasks associated with administering the TPU GUI via TPU GUI screens include:

Adding new local users, or deleting former local users as required.

Editing local user attributes:

User name

Password

Session timeout
Role (ADMIN/USER)

Clearing configuration screen locks when a user (local or OMP assigned) fails to
logout properly after starting up TPU GUI configuration screens. For example,
when growing a new GICC.
Reactivating an account if a local user enters five invalid login attempts and is
locked out.
Verifying EMS user accounts synchronization status.

Total administrative users

There is no limit on the number of user logins that may serve in the ADMIN capacity.
Preventing user login conflicts

To prevent user login conflicts, an error message will appear if you attempt to create a
user login name that was previously created at the OMP, or at the TPU GUI.
Procedures

The following procedures are required for maintaining the login access of system
users:
Add local TPU GUI user (p. 16-17)

Delete local TPU GUI system user (p. 16-26)

Clear configuration lock (p. 16-30)

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
16-15
Issue 14, September 2009
See notice on first page

PRELIMINARY

Edit local TPU GUI user access profile (p. 16-22)

PRELIMINARY
PRELIMINARY

Managing security

Adminstrator tasks

Reactivate local TPU GUI user (p. 16-34)

Verify EMS user accounts synchronization status (p. 16-38)

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

16-16

Add
local TPU GUI user
...................................................................................................................................................................................................................................
Purpose

To provide a qualified local system user (ADMIN or USER) access to the TPU GUI.
User ID

PRELIMINARY

Managing security

You must either:

Obtain the new user ID from the new TPU GUI user.

Choose a user ID for the new TPU GUI user.

This is dependent on the local practices, customs, and procedures of the Service
Provider.
User password

A user password must be at least six characters (alpha, numeric, or combined) in

length.
Temporary password

Temporary password The system administrator has the option of assigning a new
password for a new local user (Step 9 through Step 11) or letting the TPU GUI assign
the default password (lucent123).
If the default password method is used, the user will be required to delete the default
password and enter a new password when logging in for the first time. If the system
administrator provides the password, then the new user should be reminded to change
to a personal password, the first time that they access TPU GUI.
User name

You will need the name of the user, to associate with the User ID and user password.
Procedure

To provide a local system user (ADMIN or USER) access to TPU GUI, perform the
following:
...................................................................................................................................................................................................

Obtain access to TPU GUI either by:

Direct access method. See also Accessing TPU GUI (p. 6-6).

Via login from EMS GUI. See also Logging on to Element Management System
(EMS) (p. 6-5).

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
16-17
Issue 14, September 2009
See notice on first page

PRELIMINARY

Managing security

Add local TPU GUI user

...................................................................................................................................................................................................

On the 1X RNC TPU Web launch page, click on the Admin button.
Result The Admin screen, as shown in the following example, appears.

...................................................................................................................................................................................................

PRELIMINARY

Click on the User Management link.

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

16-18

Add local TPU GUI user

Result The User Management screen, as shown in the following example,

appears.

PRELIMINARY

Managing security

...................................................................................................................................................................................................

Enter the User ID, and User Name boxes with the appropriate information.
...................................................................................................................................................................................................

Choose the Session Timeout Value. The range is from 30 minutes to 120 minutes, or
no limit may also be specified.

Choose the profile ADMIN or USER for the new user.

...................................................................................................................................................................................................

Click on Done.

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
16-19
Issue 14, September 2009
See notice on first page

PRELIMINARY

...................................................................................................................................................................................................

PRELIMINARY

Managing security

Add local TPU GUI user

Result The User Management screen resets, and the new user is added to the
Existing Users: table.
...................................................................................................................................................................................................

Perform Step 9 through Step 11 only if you do not wish the new user to be assigned
with the TPU GUI default password.
...................................................................................................................................................................................................

In the Edit column of the Existing Users: table, click on the page icon.

PRELIMINARY

Result The Edit User screen, as shown in the following example, appears.

...................................................................................................................................................................................................

Enter the temporary password for the new user in the New Password and Confirm
Password boxes.

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

16-20

Add local TPU GUI user

...................................................................................................................................................................................................

Click on Submit.
Result The Edit User screen resets, and the new user is assigned with a temporary

password.
...................................................................................................................................................................................................

PRELIMINARY

Managing security

To logout, click on the Logout button.

PRELIMINARY

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
16-21
Issue 14, September 2009
See notice on first page

PRELIMINARY

Managing security

Edit
local TPU GUI user access profile
...................................................................................................................................................................................................................................
Purpose

To update a local TPU GUI users access profile.

Reason to perform

The user may have forgotten their password, or they may wish to have their session
timeout value amended, or their role classification may need to be updated.
Procedure

To amend a local TPU GUI users access profile, perform the following:
...................................................................................................................................................................................................

Obtain access to TPU GUI either by:

Direct access method. See also Accessing TPU GUI (p. 6-6).
Via login from EMS GUI. See also Logging on to Element Management System
(EMS) (p. 6-5).

...................................................................................................................................................................................................

PRELIMINARY

On the 1X RNC TPU Web launch page, click on the Admin button.

16-22

Edit local TPU GUI user access profile

Result The Admin screen, as shown in the following example, appears.

PRELIMINARY

Managing security

...................................................................................................................................................................................................

Click on the User Management link.

PRELIMINARY

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
16-23
Issue 14, September 2009
See notice on first page

PRELIMINARY

Managing security

Edit local TPU GUI user access profile

Result The User Management screen, as shown in the following example, appears.

...................................................................................................................................................................................................

PRELIMINARY

In the Edit column of the Existing Users: table, click on the page icon of the user
profile that needs to be amended.

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

16-24

Edit local TPU GUI user access profile

Result The Edit User screen, as shown in the following example, appears.

PRELIMINARY

Managing security

...................................................................................................................................................................................................

Edit the user profile as required.

...................................................................................................................................................................................................

Click on Submit.
Result The Edit User screen resets, and the user profile is amended.
...................................................................................................................................................................................................

To logout, click on the Logout button.

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
16-25
Issue 14, September 2009
See notice on first page

PRELIMINARY

Managing security

Delete
local TPU GUI system user
...................................................................................................................................................................................................................................
Purpose

To delete a local TPU GUI system user.

Reason to perform

The TPU GUI user no longer requires access to the TPU GUI.
Procedure

To delete a local TPU GUI system user, perform the following:

...................................................................................................................................................................................................

Obtain access to TPU GUI either by:

Direct access method. See also Accessing TPU GUI (p. 6-6).
Via login from EMS GUI. See also Logging on to Element Management System
(EMS) (p. 6-5).

...................................................................................................................................................................................................

PRELIMINARY

On the 1X RNC TPU Web launch page, click on the Admin button.

16-26

Delete local TPU GUI system user

Result The Admin screen, as shown in the following example, appears.

PRELIMINARY

Managing security

...................................................................................................................................................................................................

Click on the User Management link.

PRELIMINARY

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
16-27
Issue 14, September 2009
See notice on first page

PRELIMINARY

Managing security

Delete local TPU GUI system user

Result The User Management screen, as shown in the following example,

appears.

...................................................................................................................................................................................................

In the User ID column of the Existing Users: table, click on the box associated with
the user ID of the user that is to be deleted.
Result A check mark appears in the box.

PRELIMINARY

...................................................................................................................................................................................................

Click on the X adjacent to the User ID.

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

16-28

Delete local TPU GUI system user

Result The following confirmation box appears.

PRELIMINARY

Managing security

...................................................................................................................................................................................................

Click on OK.
Result The row in the Existing Users: table containing the user ID marked by the

check mark is removed.

...................................................................................................................................................................................................

To logout, click on the Logout button.

PRELIMINARY

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
16-29
Issue 14, September 2009
See notice on first page

PRELIMINARY

Managing security

Clear
configuration lock
...................................................................................................................................................................................................................................
Purpose

To clear a TPU GUI configuration screen previously left locked by a system user (local
or OMP assigned).
Reason to perform

A user working on a TPU GUI configuration screen, did not complete the
configuration task, e.g., growing a gateway, and exited without properly logging out.
The screens are now locked for use by other system users.
Procedure

To clear a configuration lock scenario, perform the following:

...................................................................................................................................................................................................

Obtain access to TPU GUI either by:

Direct access method. See also Accessing TPU GUI (p. 6-6).

Via login from EMS GUI. See also Logging on to Element Management System
(EMS) (p. 6-5).

...................................................................................................................................................................................................

PRELIMINARY

On the 1X RNC TPU Web launch page, click on the Admin button.

16-30

Clear configuration lock

Result The Admin screen, as shown in the following example, appears.

PRELIMINARY

Managing security

...................................................................................................................................................................................................

Click on the TPU GUI Locks link.

PRELIMINARY

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
16-31
Issue 14, September 2009
See notice on first page

PRELIMINARY

Managing security

Clear configuration lock

The Clear Lock screen, as shown in the following example, appears.

...................................................................................................................................................................................................

Click in the Select box, to select the locked user session that you want to unlock.
Important! There could be a number of user sessions in progress, so make sure
that you select the correct session to unlock.
...................................................................................................................................................................................................

PRELIMINARY

Click on the Clear button.

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

16-32

Clear configuration lock

A confirmation box,as shown in the following example appears.

PRELIMINARY

Managing security

...................................................................................................................................................................................................

Click on OK.
Result The following success message results.

...................................................................................................................................................................................................

Click on OK.
The Locks cleared successfully box disappears along with the previously locked
session indicator row on the Clear Lock screen.
...................................................................................................................................................................................................

To logout, click on the Logout button.

PRELIMINARY

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
16-33
Issue 14, September 2009
See notice on first page

PRELIMINARY

Managing security

Reactivate
local TPU GUI user
...................................................................................................................................................................................................................................
Purpose

To reactivate the account of a local TPU GUI user.

Reason to perform

A TPU GUI user tried unsuccessfully to enter the correct password for accessing TPU
GUI, during five consecutive login attempts. The user is now locked out.
Procedure

To reactivate the account of a local TPU GUI user, perform the following:
...................................................................................................................................................................................................

Obtain access to TPU GUI either by:

Direct access method. See also Accessing TPU GUI (p. 6-6).
Via login from EMS GUI. See also Logging on to Element Management System
(EMS) (p. 6-5).

...................................................................................................................................................................................................

On the 1X RNC TPU Web launch page, click on the Admin button.

PRELIMINARY

Result The Admin screen, as shown in the following example, appears.

16-34

Reactivate local TPU GUI user

...................................................................................................................................................................................................

Click on the Activate Accounts link.

Result The Activate User Accounts screen, as shown in the following example,

appears.

PRELIMINARY

Managing security

...................................................................................................................................................................................................

Highlight the checked box in the Select row and click on the Activate button.
Result The following confirmation box is returned.

...................................................................................................................................................................................................

Click on OK.

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
16-35
Issue 14, September 2009
See notice on first page

PRELIMINARY

Managing security

Reactivate local TPU GUI user

Result The following success box is returned.

...................................................................................................................................................................................................

Click on OK.
...................................................................................................................................................................................................

PRELIMINARY

A screen similar to the following is displayed.

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

16-36

Reactivate local TPU GUI user

PRELIMINARY

Managing security

...................................................................................................................................................................................................

To logout, click on the Logout button.

PRELIMINARY

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
16-37
Issue 14, September 2009
See notice on first page

PRELIMINARY

Managing security

Verify
EMS user accounts synchronization status
...................................................................................................................................................................................................................................
Purpose

To verify EMS user accounts synchronization status.

Reason to perform

To verify whether or not EMS user accounts synchronization status (see TPU GUI
login synchronization (p. 16-13)) is in effect.
Procedure

To verify EMS user accounts synchronization status., perform the following:

...................................................................................................................................................................................................

Obtain access to TPU GUI either by:

Direct access method. See also Accessing TPU GUI (p. 6-6).
Via login from EMS GUI. See also Logging on to Element Management System
(EMS) (p. 6-5).

...................................................................................................................................................................................................

On the 1X RNC TPU Web launch page, click on the Admin button.

PRELIMINARY

Result The Admin screen, as shown in the following example, appears.

16-38

Verify EMS user accounts synchronization status

...................................................................................................................................................................................................

Click on the View EMS user accounts synchronization status link.

Result Depending upon the state of synchronization status, the EMS user
accounts synchronization status screen, as shown in the following example,

appears.

PRELIMINARY

Managing security

...................................................................................................................................................................................................

To logout, click on the Logout button.

PRELIMINARY

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
16-39
Issue 14, September 2009
See notice on first page

PRELIMINARY

Managing security

Updating
local TPU GUI password
...................................................................................................................................................................................................................................
Introduction

Both locally assigned non-ADMIN TPU GUI system users (profiled simply as USER)
and locally assigned ADMIN users are given the capability for updating their local
TPU GUI access password.
New users

When a new user is given local TPU GUI access, the System Administrator provides
the new user with a temporary password that should be changed the first time that the
new local user logs-in to TPU GUI.
After any password change

Any time that you update to a new password, you will automatically be logged out,
and will then be required to re-establish a new user session using your new password.
User password

A local user password must be at least six characters (alpha, numeric, or combined) in
length.
Periodic password updates

It is recommended that the local TPU GUI access passwords be updated periodically.
Follow the standards and practices set up by your local management team for password
duration recommendations.
Procedure

The following procedure is used for updating your local password:

PRELIMINARY

Change local password (p. 16-41)

16-40

Change
local password
...................................................................................................................................................................................................................................
Purpose

To change your local TPU GUI user access password

Reason to perform

PRELIMINARY

Managing security

You are either a new local TPU GUI user or you have used the same password for an
extended duration.
Procedure

To change your local password, perform the following:

...................................................................................................................................................................................................

Obtain access to TPU GUI either by:

Direct access method. See also Accessing TPU GUI (p. 6-6).
Via login from EMS GUI. See also Logging on to Element Management System
(EMS) (p. 6-5).

...................................................................................................................................................................................................

On the 1X RNC TPU Web launch page, click on the Change Password button.

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
16-41
Issue 14, September 2009
See notice on first page

PRELIMINARY

Managing security

Change local password

Result The Change Password screen, as shown in the following example,

appears.

...................................................................................................................................................................................................

In the boxes provided, enter your old password and your new password, as shown.
...................................................................................................................................................................................................

PRELIMINARY

Click on Submit.

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

16-42

Change local password

Result One of the following messages is returned. .

PRELIMINARY

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
16-43
Issue 14, September 2009
See notice on first page

PRELIMINARY

Managing security

PRELIMINARY

Managing security

Change local password

...................................................................................................................................................................................................

In either case click on OK.

Result If you entered your new password successfully, you will be logged out and

will need to log back in to renew your user session. If you entered an invalid
password, the Change Password screen will return so that you can correct your
erroneous password.
END OF STEPS

PRELIMINARY

...................................................................................................................................................................................................

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

16-44

PRELIMINARY

Appendix A: Controls and indicators

This chapter describes the controls and indicators on the cabinet and on each
sub-system component.
Contents
Cabinet indicators

A-2

Power indicators

A-3

Alarm card indicators

A-4

ESC indicators

A-7

CICC indicators

A-10

GICC indicators

A-13

B-PCF indicators

A-17

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
A-1
Issue 14, September 2009
See notice on first page

PRELIMINARY

Controls and indicators

The alarm board in the power distribution shelf (PDS) controls the cabinet LEDs.
The following picture illustrates the cabinet LEDs that are driven by cabinet level
information from the PDS alarm board.
Figure A-1 Cabinet LEDs

LED states

The LEDs appear on the top-left front and top-left rear of the cabinet (from left to
right):
Table A-1

Cabinet LEDs

Name

Description

Status

LED

Power

When on, indicates power to the

cabinet is on, both, ECBUs are
installed and -48V is present at both
ECBU inputs.

Green

Off

Unlit

When lit, indicates one or more

breakers has been automatically
tripped

Red

Off

Unlit

When lit, indicates that a fault exists

in a cabinet exhaust fan, shelf, or an
internal ECBU fault. prevents power
from being connected to the circuit
breakers.

Red

Off

Unlit

PRELIMINARY

Breaker Fault

Equipment
Fault

A-2

Power
indicators
...................................................................................................................................................................................................................................
Introduction

The Power Distribution Shelf (PDS) controls power distribution from 2 Enhanced
Circuit Breaker Units (ECBU) to other components in the cabinet. The power
distribution shelf consists of:

PRELIMINARY

Controls and indicators

2 ECBUs
an alarm board.

ECBU LEDs

The following LEDs appear on each ECBU:

Table A-2

ECBU LEDs

Name

Function

Power (green)

Indicates that power is available for distribution via the

circuit breakers.

Reverse polarity (red)

Indicates that the incoming power is connected backwards.

Power status is reported via the alarm board to the cabinet LEDs.

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
A-3
Issue 14, September 2009
See notice on first page

PRELIMINARY

Controls and indicators

Alarm
card indicators
...................................................................................................................................................................................................................................
Introduction

The alarm card provides reliability management for the components in the TPU shelf.
Alarm card faceplate

The following diagram shows the layout of the alarm card faceplate

PRELIMINARY

Figure A-2 Alarm card faceplate

A-4

Alarm card indicators

Alarm card LEDs

The LEDs for the chassis alarm card, which is located in the cPSB chassis, indicate the
following states:
Table A-3

Alarm card LEDs

Name

Description

Status

LED

Minor,
Major and
critical
alarm

Indicates the presence of various

event-triggered alarms.

Off: No alarm
triggered

Unlit

On: Alarm triggered

Amber

On: Alarm cutoff is

activated

Blinking
amber

Off: No link

Unlit

On: Link

Green,
yellow

On: Link is on and

activity is occurring

Blinking
green

On: Power is on and

board is acting as
master (active).

Green

On: Power is on and

board is acting as
backup (standby)

Blinking
green

Off: power is off

Unlit

On: Alarm card needs

attention (critical
problem exists)

Red

Installation: On:
booting

Blue

Ethernet
port LEDs

Alarm card
status

Hot Swap

Indicates condition of Ethernet

connection.

Indicates alarm card status.

Indicates:

whether it is safe to remove the

board from a live (powered-on)
chassis
board conditions during
installation or removal.

PRELIMINARY

Controls and indicators

Removal: On: ready

for removal
Installation: Off:
operational

Unlit

Removal: Off: ready

for removal

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
A-5
Issue 14, September 2009
See notice on first page

PRELIMINARY

Controls and indicators

Alarm card indicators

Alarm card controls

There is one pushbutton on the alarm card faceplate. This is the Alarm cutoff
push-button. It toggles the ACO state. When ACO is activated, the active alarm LEDs
blink, and all of the alarm relays are deactivated. This button does not clear alarms.
Pressing and holding the ACO button for seven seconds forces a board reset.
Ejector with hot swap switch

PRELIMINARY

This ejector functions as a handle and a lever for installing or removing the chassis
alarm card. A switch is incorporated to tell the second chassis alarm card when the
board is about to be removed or inserted.

A-6

ESC
indicators
...................................................................................................................................................................................................................................
Introduction

The Ethernet Switch Card (ESC) provides 24 Gigabit Ethernet ports. Two ESCs are
required in each TPU shelf.

PRELIMINARY

Controls and indicators

ESC faceplate

The following diagram shows the layout of the ESC faceplate.

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
A-7
Issue 14, September 2009
See notice on first page

PRELIMINARY
PRELIMINARY

Controls and indicators

ESC indicators

Figure A-3 ESC faceplate

A-8

ESC indicators

ESC LEDs

The table provides the indications and conditions for each LED.
Table A-4

ESC LEDs

Name

Description

Status

LED

System (board)

Indicates the status of the board or system

ON: booting

Yellow

ON:
Operational

Green

Off: fault/no
power

Unlit

On: fault

Red

Off: fault/no
power

Unlit

On: link

Green

On: transmit
or receive
activity

Green
blinking

Off: no link

Unlit

On: 100Mbit

Yellow

Off: 10 Mbit

Unlit

Fault (board)

Port

Indicates a system fault condition

Two LEDs are provided for each port.

Management
ports

Indicates port speed

Ethernet ports

Indicates port speed

Hot Swap

Indicates:
whether it is safe to remove the board
from a live (powered-on) chassis
board conditions during installation or
removal.

PRELIMINARY

Controls and indicators

On: 100Mbit
Off: 10 Mbit
or 100 Mbit

Unlit

Installation:
On: booting

Blue

Removal: On:
ready for
removal
Installation:
Off:
operational

Unlit

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
A-9
Issue 14, September 2009
See notice on first page

PRELIMINARY

Removal: Off:
ready for
removal

PRELIMINARY

Controls and indicators

CICC
indicators
...................................................................................................................................................................................................................................
Introduction

The Common Intelligent Carrier Card (CICC) sends heart beats over the active/standby
backplane links to monitor the connectivity over the backplane.
CICC face plate

PRELIMINARY

The following graphic shows the face plate of the Common Intelligent Carrier Card
(CICC):

A-10

CICC indicators

Figure A-4 CICC face plate

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
A-11
Issue 14, September 2009
See notice on first page

PRELIMINARY

Controls and indicators

PRELIMINARY

Controls and indicators

CICC indicators

CICC LEDs

LEDs on the CICC are described in the following table.

Table A-5

CICC LEDs

Name

Description

State

LED...

CPU#1
Ethernet
port status

Indicates the status of the Ethernet port

Active: On

Green

Active: Off

Unlit

Line: On

Green

Line: Off

Unlit

Power/
Fault status

Indicates the operational status of the

board

Green

cPSB status
LEDs

Indicates the operational status of each

cPSB

Act 1/Act 2: On

Green

Act 1/Act2: Off

Unlit

Line 1/Line 2: On

Green

Line 1/Line 2: Off

Unlit

Installation: On:
booting

Blue

Hot Swap

Indicates:
whether it is save to remove the board
from a live (powered-on) chassis
board conditions during installation or
removal.

Removal: On:
ready for removal
Installation: Off:
operational

Unlit

PRELIMINARY

Removal: Off:
ready for removal

A-12

GICC
indicators
...................................................................................................................................................................................................................................
Introduction

The Gateway Intelligent Carrier Card (GICC) provides high-performance hardware data
path protocol processing.

PRELIMINARY

Controls and indicators

GICC face plate

The following graphics show the face plates of the Gateway Common Intelligent
Carrier Card (GICC):

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
A-13
Issue 14, September 2009
See notice on first page

PRELIMINARY
PRELIMINARY

Controls and indicators

GICC indicators

Figure A-5 Non-optical ethernet GICC (1.0) faceplate

A-14

GICC indicators

Figure A-6 Optical ethernet GICC (1.1) faceplate

PRELIMINARY

Controls and indicators

GICC LEDs

LEDs on the GICCs are described in the following table.

Table A-6

GICC LEDs

Name

Description

State

LED...

Ethernet
port status

Indicates transmit receive activity

Active: On

Green

Active: Off

Unlit

Line: On

Green

Line: Off

Unlit

Indicates if the connection is complete

Indicates the operational status of the

board

Green

Off

Unlit

cPSB
status

Indicates the status of each of the 2 cPSB

shelves

Active: On

Green

Active: Off

Unlit

Line: On

Green

Line Off

Unlit

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
A-15
Issue 14, September 2009
See notice on first page

PRELIMINARY

Power/
Fault
status

PRELIMINARY

Controls and indicators

GICC indicators

Table A-6

GICC LEDs

(continued)

Name

Description

State

LED...

Hot Swap

Indicates:

Installation: On:
booting

Blue

whether it is save to remove the board

from a live (powered-on) chassis
board conditions during installation or
removal.

Removal: On: ready

for removal
Installation: Off:
operational

Unlit

PRELIMINARY

Removal: Off: ready

for removal

A-16

B-PCF
indicators
...................................................................................................................................................................................................................................
Introduction

The Blade Packet Control Function (B-PCF) provides a packet control function that is
implemented on a Solaris Blade with an attached PMC disk drive.

PRELIMINARY

Controls and indicators

B-PCF card faceplate

The following diagram shows the layout of the B-PCF card faceplate

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
A-17
Issue 14, September 2009
See notice on first page

PRELIMINARY

Controls and indicators

B-PCF indicators

Figure A-7 B-PCF faceplate

PMC slot B

PMC slot A

Serial port

ABORT pushbutton
RESET pushbutton
ALARM/USER LED yellow
READY LED green

PRELIMINARY

HOT SWAP LED blue

A-18

B-PCF indicators

Controls and indicators

TheLEDs and controls for the B-PCF are listed as follows:

Table A-7

Alarm card LEDs

Name

Description

LED

Alarm/User

a card alarm is present

yellow

Ready

card is operational with no alarms

green

Hot Swap

Blinking BLUE: indicates card is booting

blue

PRELIMINARY

Controls and indicators

Steady BLUE: indicates card latches are

open, the card has not been selected with
BSEL or the card power supplies are out
of band
Abort Switch

Will bring Solaris OS to OK prompt (open

boot)

Reset Switch

This is a software reset of the card

Ejector with hot swap switch

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
A-19
Issue 14, September 2009
See notice on first page

PRELIMINARY

Appendix B: Command Reference

This appendix describes commands that are executed from the UNIX shell prompt of a
Mobility Manager Application Processor (MM-AP) to administer MM-AP software.
The description of each MM-AP command provides the following information:

Syntax. The Syntax information specifies the format of the command and the
arguments and options that may or must be entered on the command line to specify
how the command is to execute.

Typical usage. The Typical usage information presents the command line for a
typical execution of the command.

Description. The Description information describes the purpose and result of

executing the command and its various arguments and options. The Description
information may also describe the output of the command and how the command
executes.

Example output. The Example output information shows the output of a sample
execution of the command.

Contents
apactivate

B-3

apappconfig

B-5

apapply

B-6

apbackout

B-7

apbackup

B-9
B-12

apinstall

B-16

apoffline

B-18

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
B-1
Issue 14, September 2009
See notice on first page

PRELIMINARY

apcc_ip_migr

PRELIMINARY
PRELIMINARY

Command Reference

Overview

aponline

B-19

aponlygr

B-20

appkgchk

B-21

appkginfo

B-23

appkgload

B-25

appkgrm

B-26

appkgtrans

B-28

appkgunload

B-31

applatconfig

B-33

aprecover

B-35

aprenew

B-36

apsettimers

B-40

flxactivate

B-41

flxbackout

B-43

flxbackup

B-45

flxbuninfo

B-46

flxchkfwacv

B-47

flxcoremgmt

B-49

flxcronmgmt

B-50

flxdeactivate

B-52

flxfwac

B-53

flxfwacv

B-55

flxlogmgmt

B-58

flxname

B-60

flxpkginfo

B-62

SMxmldump(1)

B-63

B-2

apactivate
...................................................................................................................................................................................................................................
Syntax
apactivate -p package [-v version] [-s server] [-q]

-p package

activate the software package named package on the MM-AP

-v version

activate version number version of the package that is to be

activated

-s server

activate the package on the remote server named server

-q

run in quiet mode (do not prompt for additional information)

PRELIMINARY

Command Reference

Typical usage
apactivate -p package -v version

Description

The apactivate command is used to make final modifications to an MM-AP after

software packages have been installed on the MM-AP.
Activating the ngn_platform or fms_rcc package saves the currently running package
and then administers the MM-AP to make the newly installed package the currently
running package.
The -p argument specifies the package that is to be activated. The -v argument
specifies the version number of the package that is to be activated. To activate both the
fms_rcc and ngn_platform packages, repeat the -p and -v arguments or specify
-p all.
The -s argument is currently provided as a sanity check. If you use the remsh program
to run the apactivate command remotely, use the -s option to ensure that
apactivate is running on the correct MM-AP.
apactivates default mode of operation is to tell you what it is going to do and then

prompt you for whether you want to continue. To have apactivate execute without
this prompt, use the -q (quiet) option.
Since the apactivate command affects the running MM-AP, it requires the MM-AP to
be offline (see apoffline (p. B-18)).

# apactivate -p ngn_platform -v AP18.0.0001

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
B-3
Issue 14, September 2009
See notice on first page

PRELIMINARY

Example output

PRELIMINARY
PRELIMINARY

Command Reference

apactivate

B-4

from

apappconfig
...................................................................................................................................................................................................................................
Syntax
apappconfig -a app_name -c -p primary_MM-AP -s secondary_MM-AP
apappconfig -a app_name -d
apappconfig -h

PRELIMINARY

Command Reference

create or delete the application named app_name

-a app_name

Currently the supported applications are: dbms, rop.

-c

create the named application

-d

delete the named application

-p primary_MM-AP

configure the primary instance of the application on the

MM-AP named primary_ MM-AP

-s secondary_MM-AP

configure the secondary instance of the application on the

MM-AP named secondary_ MM-AP

-h

show the command syntax

Typical usage
apappconfig -a app_name -c -p primary_MM-AP -s secondary_MM-APMM-AP
apappconfig -a app_name -d

Description

The apappconfig command configures (creates or deletes) a new MM-AP application.

It is run on the OMP. The apappconfig command is typically used once in the
lifetime of a system to configure a new application. Whether creating or deleting an
application, the apappconfig command queries the states of the appropriate MM-APs
to determine if a create or a delete is possible. When deleting an application,
apappconfig automatically determines from which MM-APs to delete the application.
Example output
# apappconfig -a
Creation of dbms
# apappconfig -a
Deletion of dbms

dbms -c -p ap01 -s ap02

was successful.
dbms -d
was successful.

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
B-5
Issue 14, September 2009
See notice on first page

PRELIMINARY

Command Reference

apapply
...................................................................................................................................................................................................................................
Syntax
apapply

Description

The apapply command is used to perform the MM-AP generic retrofit procedure and
should be used only in the performance of that procedure.
The apapply command informs the Reliable Cluster Computing (rcc) software that a
new version of the fms_rcc software is available on all MM-APs. It also changes the
Software Update (SU) status of all of the MM-APs to allow a generic retrofit of
MM-AP platform software.

PRELIMINARY

The apapply command is used only during generic retrofit. It is not used during SUs.
It should be used only if the MM-AP fms_rcc and ngn_platform packages have been
installed on all MM-APs. The apapply command needs to issued from only one
MM-AP, not from each MM-AP.

B-6

apbackout
...................................................................................................................................................................................................................................
Syntax
apbackout -p package [-v version] [-s server] [-q]
-p package

back out the software package named package from the MM-AP

-v version

back out version number version of the package that is to be backed

out

-s server

back out the package from the remote server named server

-q

run in quiet mode (do not prompt for additional information)

PRELIMINARY

Command Reference

Typical usage
apbackout -p package -v version

Description

The apbackout command is used to make final modifications to an MM-AP after

software packages have been installed and activated on that MM-AP. The apbackout
command reverses a previous execution of the apactivate command.
Backout of the ngn_platform or fms_rcc package saves the currently running package
and then administers the MM-AP to make the previously installed package the
currently running package.
The -p argument specifies the package that is to be backed out. The -v argument
specifies the version number of the package that is to be backed out. To back out both
the fms_rcc and the ngn_platform packages, repeat the -p and -v arguments or
specify -p all.
The -s argument is currently provided as a sanity check. If you use the remsh program
to run the apbackout command remotely, use the -s argument to ensure that
apbackout is running on the correct MM-AP.
apactivates default mode of operation is to tell you what it is going to do and then

prompt you for whether you want to continue. To have apactivate execute without
this prompt, use the -q (quiet) option.
Since the apbackout command affects the running MM-AP, it requires the MM-AP to
be offline (see apoffline (p. B-18)).

# apbackout -p ngn_platform -v AP18.0.0001

Activation of the ngn_platform package will result in version
AP18.0.0001 being moved to /ap/platform/new, and version AP17.0.0009
being moved to /ap/platform/default.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
B-7
Issue 14, September 2009
See notice on first page

PRELIMINARY

Example output

PRELIMINARY
PRELIMINARY

Command Reference

apbackout

Do you want to continue [no]: yes Activating ngn_platform package

(AP17.0.0009) from /ap/platform/backout ... The ngn_platform
package (AP17.0.0009) was successfully activated.

B-8

apbackup
...................................................................................................................................................................................................................................
Syntax
apbackup [-v backup_version] [-t text_string] [-s server] [-] login]
[-z password] [-q]
-v backup_
version

back up version number backup_version of this backup saveset

-t
text_string

back up a comment, text_string, in quotation marks that describes

the contents of this backup saveset

-s server

send the backup saveset to the remote server named server

-l login

use login ID login on the remote server when sending a saveset to a

remote server

-z password

use the password password of the login ID on the remote server

when sending a saveset to a remote server

-q

bypass system messages while the command executes

PRELIMINARY

Command Reference

Typical usage
apbackup -t text_string

Description

The apbackup command is used in day-to-day MM-AP administration to save

information about the configuration of an MM-AP. The version numbers of all installed
MM-AP packages are saved; the packages themselves reside on the Operations and
Management Platform (OMP) and the MM-AP distribution tape. Configured MM-AP
applications are saved as a select group of files in the /etc/passwd directory. The
apbackup command does not save the entire MM-AP but only those pieces that are
necessary to reestablish the current configuration. For example, apbackup saves login
IDs and passwords but does not save user-defined $HOME directories.
The -t argument is used to enter a user-defined comment about what the backup
saveset contains. If the saveset is later used, the text string is printed, and the user is
asked to quit or continue.
The -v argument specifies the version of the created backup saveset. Backup savesets
are normally kept on the OMP server, which is named apomp.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
B-9
Issue 14, September 2009
See notice on first page

PRELIMINARY

To send the backup saveset to a different server, use the -s argument to specify that
server.

PRELIMINARY

Command Reference

apbackup

The user who executes the apbackup command must be able to write to the local
backup directory. The remote login ID that is specified in the -l argument in the
apbackup command line must be able to write to the remote backup directory. To
specify the remote login ID, use the -l argument. The password for the remote login
ID can be specified in the -z argument, but for security purposes, users are cautioned
against using the -z argument.
The -q (quiet) option is used to prevent the apbackup command from asking the user
questions while the command executes. If the -q option is used, the user must supply
all required information on the command line.
Example output
# apbackup -t Before configuring cell 222

1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
Enter the version of the backup saveset to be saved [19990324]:
1234567890123456789012345678901212345678901234567890123456789
19990324
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
106 blocks
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
69 blocks
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
61 blocks
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
AP package transfer makes heavy use of the TCP/IP network and may
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
therefore affect performance. AP package transfer should be
1234567890123456789012345678901212345678901234567890123456789
performed during an off-peak period.
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789

PRELIMINARY

B-10

apbackup

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
B-11
Issue 14, September 2009
See notice on first page

PRELIMINARY

Command Reference

PRELIMINARY

Command Reference

apcc_ip_migr
...................................................................................................................................................................................................................................
Syntax
apcc_ip_migr [-c [node] [IP]] [-v [node]] [-n [node]] [-o [node]]

where
-c

create a new MM-APCC LAN

-v

verify MM-APs, alarm cards, or Ethernet switches

-n

change the IP address on alarm cards and Ethernet switches to the new
IP addressing scheme

-o

change the IP address on alarm cards and Ethernet switches to the old
IP addressing scheme

-h

provide help

-p passwd

use passwd as the HUBs password

-q

use non-interactive mode

first two octets of new MM-APCC LAN address

node

name of an MM-AP, alarm card, or Ethernet switch

Important! The -c, -v, -n and -o options cannot be combined.

Typical usage
apcc_ip_migr
apcc_ip_migr
apcc_ip_migr
apcc_ip_migr
apcc_ip_migr

-v
-n
-o
-n ap35 ac35 es2a es2b
-o ap35 ac35 es2a es2b

PRELIMINARY

Description

The apcc_ip_migr command is used only to migrate IP addresses of MM-APs,

MM-AP alarm cards, and Ethernet switches on the MM-APCC LAN to the new IP
addressing scheme introduced in Release 25.0 to accommodate 28 application
processor frames and other Lucent wireless products. It is run on MM-APs two days

B-12

apcc_ip_migr

before retrofitting to Release 25.0 in preparation for the retrofit. It saves the first two
octets of both the old and new MM-APCC LAN IP addresses, and changes the IP
addresses of MM-AP alarm cards and Ethernet switches.
Reference For more information on when and how to run apcc_ip_migr, see Software
Retrofit Procedures (R20.0) (401-610-177).
The -v option verifies that all or selected MM-APs, MM-AP alarm cards, and Ethernet
switches have the same old and new MM-APCC LAN IP network address, whether
they are ready for retrofit to Release 25.0, or backout to Release 19.0, and which IP
network scheme each MM-AP is active on.

PRELIMINARY

Command Reference

If the Ready for GR to R20 column in the output from the -v option is Yes for all
MM-APs, MM-AP alarm cards, and Ethernet switches, the system is ready for retrofit
to Release 25.0. Any element for which the Ready for GR to R20 column shows No i
s not ready for retrofit to Release 25.0.
If the Ready for Backout column in the output from the -v option is Yes for all
MM-APs, MM-AP alarm cards, and Ethernet switches, the system is ready for backout
to Release 19.0. Any element for which the Ready for Backout column shows No i s
not ready for backout to Release 19.0.
An asterisk (*) following the IP address of an MM-AP in the output from the -v option
indicates that the MM-AP is active on that IP network scheme.
The -c option selects (creates) a new MM-APCC LAN IP network address and saves
both the new and old IP network addresses.
The -n option changes the IP address of all or selected MM-AP alarm cards and
Ethernet switches to the new IP network address scheme.
The -o option changes the IP address of all or selected MM-AP alarm cards and
Ethernet switches back to old IP address scheme.
The -p option specifies an Ethernet switch password to be used when running the
command on a switch, if desired.
The -q option runs the command without prompting.
To execute the command on selected MM-APs, MM-AP alarm cards, or Ethernet
switches, list the names of those elements after the -c, -v, -n and -o options. If listing
more than one name, separate each names with a blank space.
Example output

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
B-13
Issue 14, September 2009
See notice on first page

PRELIMINARY

# apcc_ip_migr -v

PRELIMINARY

Command Reference

apcc_ip_migr

Please wait...
--------------------------------------------------------------------------------R19 R20 Custom.name Ready for Ready for
conversion GR to R20 Backout
--------------------------------------------------------------------------------GNP-AP : ap02 10.0* 172.16 N/A Yes Yes
GNP-AP : ap05 10.0* 172.16 N/A Yes Yes
GNP-AP : ap06 10.0* 172.16 N/A Yes Yes
GNP-AP : ap11 10.0* 172.16 N/A Yes Yes
GNP-AP : ap12 10.0* 172.16 N/A Yes Yes
NGN-AP
NGN-AP
NGN-AP
NGN-AP
NGN-AP
AC
AC
AC
AC
AC

:
:
:
:
:

ap61
ap63
ap64
ap65
ap68

ac61
ac63
ac64
ac65
ac68

10.0* 172.16 Converted Yes Yes

10.0* 172.16 Converted Yes Yes
10.0* 172.16* Converted Yes Yes
no* no un-converted No No
no* no un-converted No No

10.0.2.191
10.0.2.193
10.0.2.194
10.0.2.195
10.0.2.198

------

No
No
No
No
No

Yes
Yes
Yes
Yes
Yes

HUB : es6a 10.0.2.69 -- No Yes

HUB : es6b 10.0.2.70 -- No Yes

--------------------------------------------------------------------------------* denotes the AP is active on that IP scheme network.

2 APs have not been saved with new and/or old APCC-LAN network IP
address.

Please check those failure AP, HUB or Alarm card and run apcc_ip_
migr again.
---------------------------------------------------------------------------------

PRELIMINARY

# apcc_ip_migr -c

1)
5)
9)
13)

172.16
172.20
172.24
172.28

2) 172.17 3) 172.18 4) 172.19

6) 172.21 7) 172.22 8) 172.23
10) 172.25 11) 172.26 12) 172.27
14) 172.29 15) 172.30 16) 172.31

You can select one of the above new IP addresses [q]: 1

Are you sure the new APCC-LAN network IP address is 172.16 [y|n|q]:
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

B-14

apcc_ip_migr

PRELIMINARY

Command Reference

y
Please wait... it may take more than 20 minutes [Tue Jun 18 11:02:52 2002]

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
B-15
Issue 14, September 2009
See notice on first page

PRELIMINARY

Command Reference

apinstall
...................................................................................................................................................................................................................................
Syntax
apinstall -p package [-v version] [-s server] [-d directory] [-q]

-p

install the software package named package on the MM-AP

package

-v

install version number version of the package that is to be installed

version

-s server

if executing apinstall remotely, execute it on the remote MM-AP

named server

-d
directory

install the package from the directory named directory, rather than from
the default directory /var/spool/ap/pkg

-q

run in quiet mode (bypass system messages while the command executes)

Typical usage
apinstall -p package -v version

Description

The apinstall command is used to install software packages on an MM-AP. The -p

and -v arguments are entered to specify a select version of a specific package. To
install multiple versions of multiple packages, repeat the -p and -v arguments on the
command line.
When the apinstall command is executed with its default options, the specified
package or packages are installed from the /var/spool/ap/pkg/package/version directory
on the local MM-AP. If the package resides in a local directory other than
/var/spool/ap/pkg, specify that directory in the -d directory argument.
The -s argument is currently provided as a sanity check. If the remsh program is used
to run the apinstall command remotely, use the -s argument to ensure that
apinstall is running on the correct MM-AP.

PRELIMINARY

When the apinstall command is executed, it provides an Are you sure? message.
The -q (quiet) option may be specified to bypass that message.
The position of command line options determines how the options work. The -p
argument is the key. Options that are specified before the -p argument are global and
therefore affect all packages. Options that are specified after the -p argument are local
to that specific package. For example, if the -d argument is used before the -p
argument, all packages are installed from the specified directory.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

B-16

apinstall

Example output
# apinstall -p ngn_platform -v AP18.0.0001

1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
AP installation makes heavy use of the TCP/IP network and may
1234567890123456789012345678901212345678901234567890123456789
therefore affect performance. AP installation should be performed
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
during an off-peak period.
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
Do you want to continue [no]: yes installed into the /ap/platform/
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
new directory.
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
Do you want to continue [no]: yes
1234567890123456789012345678901212345678901234567890123456789
Installing platform package (AP18.0.0001) from
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
/var/spool/ap/pkg/ngn_platform/AP18.0.0001/ngn_platform.pkg ...
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
script.input
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
pkgmap
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
pkginfo
1234567890123456789012345678901212345678901234567890123456789
ngn_platform.cpio.Z
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
install_platform
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
66590 blocks
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
...
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
ap/platform/new/varinits/S40platform.init
1234567890123456789012345678901212345678901234567890123456789
ap/platform/new/varinits/S50rcc.init
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
129454 blocks
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
The ngn_platform package (AP18.0.0001) was successfully installed!
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
B-17
Issue 14, September 2009
See notice on first page

PRELIMINARY

Command Reference

PRELIMINARY

Command Reference

bypass system messages while the command executes

Description

The apoffline command is used to change the Reliable Clustered Computing (RCC)
state to OFFLINE. The execution of apoffline terminates the RCC processes and
MM-AP application processes. Because MM-AP application processes include call
processing, use of apoffline should be limited.
When the appoffline command is executed, apoffline gives the user 5 seconds to
cancel the command. To bypass the 5-second period for canceling the command, enter
the -q (quiet) option.
Execution of the apoffline command causes the state of the MM-AP to be shown as
ISOLATED at the Element Management System (EMS). If the MM-AP is not already
in the Out-of-Service Manual (OOS-M) or ISOLATED state, the MM-AP should first
be removed from service either by using the EMS icons or by executing the RMV:AP
command at the Command Line Interface (CLI). If apoffline is executed while the
MM-AP application processes are still in service, an Are you sure? message is
generated. The user may cancel execution of apoffline at that time and issue the
appropriate RMV:AP command. This allows the MM-AP application processes to switch
to an alternate MM-AP, which minimizes down time. Similarly, if apoffline is
executed while RCC WatchDog ports are offline, the user receives an additional
Are you sure? message. To bypass these messages, enter the -q option.
Example output

PRELIMINARY

# apoffline

1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
Taking server ap01 offline...
1234567890123456789012345678901212345678901234567890123456789
To cancel, interrupt this process within 5 seconds!
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
Waiting up to 360 seconds for ap01 to be taken offline...
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
Server ap01 was successfully taken offline.
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

B-18

aponline
...................................................................................................................................................................................................................................
Syntax
aponline [-q]
-q

bypass system messages while the command executes

PRELIMINARY

Command Reference

Description

The aponline command is used to change the Reliable Clustered Computing (RCC)
state to ONLINE. Execution of aponline reboots the MM-AP and restarts the RCC
processes and MM-AP application processes. If you are connected to the MM-AP via
the TCP/IP network when the MM-AP reboots, your terminal session is lost and you
must log back in to the MM-AP after the boot sequence completes.
When the aponline command is executed, aponline gives the user 5 seconds to
cancel the execution of the command. To bypass the 5-second cancellation period,
enter the -q (quiet) option on the command line.
After the MM-AP is brought online, the Element Management System (EMS) no
longer shows the MM-AP to be in the ISOLATED state but in the Out-of-Service
Manual (OOS-M) or ACTIVE state. If the state of the MM-AP is shown as OOS-M,
the MM-AP can be brought to the ACTIVE state either by using the EMS icons or by
executing the RST:AP command at the Command Line Interface (CLI).
Important! The MM-AP cannot become ACTIVE unless the Ethernet Interface
Node Enhanced (EINE) also becomes ACTIVE. The EINE usually becomes
ACTIVE automatically. In some cases, however, the user may need to restore the
EINE manually to make it ACTIVE.
Example output
# aponline

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
B-19
Issue 14, September 2009
See notice on first page

PRELIMINARY

Command Reference

aponlygr
...................................................................................................................................................................................................................................
Syntax
aponlygr

Description

The aponlygr command executes an MM-AP-only generic retrofit. An MM-AP-only

generic retrofit is similar to an ECP generic retrofit but involves only MM-APs; the
ECP Complex is not affected. An MM-AP-only generic retrofit causes all MM-APs to
boot simultaneously to the selected version of MM-AP platform software. The behavior
of the MM-APs in response to the aponlygr command is the same as the behavior of
the MM-APs in response to the 42 r, 50, 54 command sequence.
MM-AP-only generic retrofit is performed only if the software release notes indicate
that it should be performed. More details about the MM-AP-only generic retrofit are
included in the software release notes.
When the aponlygr command is executed, the following admonishment is displayed:

PRELIMINARY

The MM-AP-only generic retrofit is executed only if the user enters y in response to
that prompt.

B-20

appkgchk
...................................................................................................................................................................................................................................
Syntax
appkgchk -p package [-v version] [-s server] [-D directory] [-q]

-p package

check the software package named package on the MM-AP

-v version

check version number version of the package that is to be checked

-s server

if executing appkgchk remotely, check the package on the remote

MM-AP named server

-D directory

if checking the ngn_platform package, check a new or previously

installed version of the package located in the directory named
directory (the default is to check the version of the package that is
currently in use)

-q

run in quiet mode (bypass system messages while the command

executes)

PRELIMINARY

Command Reference

Typical usage
appkgchk -p package

or
appkgchk -p all

Description

The appkgchk command is used to verify that the files that were installed on an
MM-AP have not changed. If a user suspects that an installed package has become
corrupt, the appkgchk command should be executed.
The -p argument specifies the package that is to be checked. The -v argument
specifies a select version of the package that is to be checked. To check multiple
versions of multiple packages, repeat the -p and -v arguments or enter the -p all
argument in the command line.

appkgchk -p ngn_platform -D /ap/platform/new

Similarly, the following command checks the previously installed ngn_platform

package:
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
B-21
Issue 14, September 2009
See notice on first page

PRELIMINARY

When the appkgchk command is executed, packages that are currently in use are
checked. If the ngn_platform package is specified, you can also instruct appkgchk to
output information about a package that is not currently in use. For example, executing
the following command checks the newly installed ngn_platform package:

PRELIMINARY

Command Reference

appkgchk

appkgchk -p ngn_platform -D /ap/platform/backout

The -s argument is currently provided as a sanity check. If the user is using remsh to
run the appkgchk command remotely, the -s argument should be entered to ensure that
the command is running on the correct MM-AP.
The -q (quiet) option is used to bypass system messages while the command executes.
Since the appkgchk command does not currently interact with the user, the -q option
may be avoided.
Example output
# appkgchk -p ngn_platform -v AP18.0.0001

PRELIMINARY

B-22

appkginfo
...................................................................................................................................................................................................................................
Syntax
appkginfo -p package [-v version] [-s server] [-D directory] [-q]

-p package

retrieve information about the software package named package on

the MM-AP

-v version

retrieve information about version number version of the package

for which information is to be retrieved

-s server

if executing appkginfo remotely, execute it on the remote MM-AP

named server

-D directory

if retrieving information about the ngn_platform package, retrieve

information about a new or previously installed version of the
package located in the directory named directory (the default is
to retrieve information about the version of the package that is
currently in use)

-q

run in quiet mode (bypass system messages while the command

executes)

PRELIMINARY

Command Reference

Typical usage
appkginfo -p package

or
appkginfo -p all

Description

The appkginfo command is used to retrieve important information about a software

package that is installed on an MM-AP.
The -p argument specifies the package about which information is to be retrieved. The
-v argument specifies a select version of the package. To retrieve information about
multiple versions of multiple packages, repeat the -p and -v arguments or enter the
-p all argument.

appkginfo -p ngn_platform -D /ap/platform/new

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
B-23
Issue 14, September 2009
See notice on first page

PRELIMINARY

When the appkginfo command is executed, information is output about the packages
that are currently in use. If the ngn_platform package is specified, the user can also
instruct appkginfo to retrieve information about a package that is not currently in use.
For example, the following command outputs information about the newly installed
ngn_platform package:

PRELIMINARY

Command Reference

appkginfo

Similarly, the following command retrieves information about the previously installed
ngn_platform package:
appkginfo -p ngn_platform -D /ap/platform/backout

The -s argument is currently provided as a sanity check. If the user is using remsh to
run the appkgchk command remotely, the -s argument should be entered to ensure that
the command is running on the correct MM-AP.
The -q (quiet) option is used to bypass system messages while the appkginfo
command executes. Since appkginfo does not currently interact with the user, the -q
option may be avoided.
Example output
# appkginfo -p ngn_platform

PRELIMINARY

B-24

appkgload
...................................................................................................................................................................................................................................
Syntax
appkgload [source_device] [destination_directory...]

Typical usage

PRELIMINARY

Command Reference

appkgload

Description

The appkgload command is used to load MM-AP packages onto the OMP.
When appkgload is executed using the default options, packages that have been
written to the source_device will be loaded into the destination_directory. If so
instructed, multiple destination directories can be specified. Groups of packages will be
loaded, the first group of packages will be loaded into the first destination_directory,
the second
Questions:
1. From first sentence, what do source_device and destination_directory default to?
2. If you specifiy multiple destination directories, what determines how packages that
get loaded into each directory are grouped? An example would be good here. (Last
sentence in paragraph is incomplete.)
The user executing the appkgload command must be able to write to the local source
package directory.
Example output
# appkgload

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
B-25
Issue 14, September 2009
See notice on first page

PRELIMINARY

Command Reference

appkgrm
...................................................................................................................................................................................................................................
Syntax
appkgrm -p package [-v version] [-s server] [-q] [-D directory]

-p package

remove the software package named package from the MM-AP

-v version

remove version number version of the package that is to be

removed

-s server

if executing apremove remotely, execute it on the remote MM-AP

named server

-D directory

remove the package from the directory named directory, rather than
from the default directory /var/spool/ap/pkg

-q

run in quiet mode (bypass system messages while the command

executes)

Typical usage
appkgrm -p package -v version

Description

The appkgrm command is used to remove the installed fms_rcc and ngn_platform
packages from an MM-AP.
Important! To remove the rcs and microcell packages, use the apdelcellsw
program.

PRELIMINARY

The -p argument specifies the package that is to be removed. The -v argument specifies
the version of the package that is to be removed. To remove multiple versions of
multiple packages, repeat the -p and -v arguments.
When the appkgrm command is executed, installed packages are removed from their
directories. The default directory from which the package is removed is the directory
into which a newly installed package would be placed. For the fms_rcc package, the
default directory that is removed is /opt/rcc/su. The default directory that is removed
for the ngn_platform package is /ap/platform/new. If a directory other than the default
directory needs to be removed, use the -D argument. For example, to remove the
backout directory of the ngn_platform package, specify -D /ap/platform/backout.
Question: Are packages removed from directories, or directories of packages removed?
Preceding paragraph is confusing.

B-26

appkgrm

If the execution of the appkgrm command affects the running MM-AP, appkgrm
requires the MM-AP to be offline (see apoffline (p. B-18)). For example, removal of
the platforms default directory affects the running MM-AP, but removal of the new or
backout directory of the platform does not affect the running MM-AP.
When the appkgrm command is executed, it provides an Are you sure? message. The
-q (quiet) option is provided to bypass this message.

PRELIMINARY

Command Reference

Example output
# appkgrm -p ngn_platform -v AP17.0.0108

1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
The ngn_platform package (AP17.0.0108) will be removed from the /ap/platform/n
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
B-27
Issue 14, September 2009
See notice on first page

PRELIMINARY

Command Reference

appkgtrans
...................................................................................................................................................................................................................................
Syntax
appkgtrans -p package [-v version] [-s server] [-S server] [-q] [-d
directory] [-D directory] [-l login] [-z password]
-p package

transfer the package named package to the MM-AP

-v version

transfer the version named version of the package that is to be

transferred to the MM-AP

-s server

get the package that is to be transferred from the remote server with
the node name server (appkgtrans defaults to apomp)

-S server

put the package that is to be transferred on the remote MM-AP with

the node name server

-q

bypass system messages while the command executes

-d directory

get the package that is to be transferred from the source directory

named directory rather than from the default directory
/var/spool/ap/pkg

-D directory

put the package that is to be transferred in the directory named

directory on the remote MM-AP rather than in the default
directory /var/spool/ap/pkg/package/version

-l login

use the login login on the remote server when reading the source
file or writing the destination file remotely

-z password

use the password password for the remote login specified with the
-l option
For security purposes, use of the -z option is discouraged.

Typical usage
appkgtrans -p package -v version

Description

PRELIMINARY

The appkgtrans command is used to transfer MM-AP packages between servers,

typically from the OMP to an MM-AP.
The -p argument specifies the package that is to be transferred. The -v argument
specifies the version of the package that is to be transferred. To transfer multiple
versions of multiple packages, repeat the -p and -v arguments.
The user is prompted for any required information not supplied on the command line.

B-28

appkgtrans

When the appkgtrans command is executed with the default options, the package files
are transferred (pulled) from the /var/spool/ap/pkg/package/version directory on the
OMP server (apomp) to the /var/spool/ap/pkg/package/version directory on the local
MM-AP. If the package resides on a server other than apomp, specify that server with
the -s option. By using the -s option, packages will be retrieved from the remote
system. If the package resides in a source directory other than /var/spool/ap/pkg, use
the -d argument. If the package is to be placed into a destination directory other than
/var/spool/ap/pkg, specify that directory with the -D option.

PRELIMINARY

Command Reference

If the package source directory is on the local system, and the package needs to be
sent to a destination directory on a remote system (pushed), use the -S server option.
If the -S option is used and the -v version option is not specified, all the versions of
the package will be listed and the user will be prompted to select the version of the
package to be transferred. By using the -S option, packages will be sent to the remote
system.
The user who executes the appkgtrans command must be able to read the source
package directory and write to the destination package directory. If appkgtrans is
executed with either the -s or -S option, can be used to specify a login on the remote
server. The remote login that is specifiedthe -l must be able to read the source package
directory (-s option) or write the destination package directory (-S option). The
password for the remote login can be specified with the -z option, but for security
purposes, use of the -z argument is discouraged. If the -l option is not used, appkgtrans
assumes that the remote login is root and prompts for roots password. Use of the
remote login oamproxy when transferring files to a remote MM-AP (-S -l oamproxy)
eliminates the password prompt.
The -q (quiet) option is used to prevent appkgtrans from asking questions while it
executes. If the -q option is used, the user must supply all required information on the
command line.
The position of command line options determine how they work. The -p option is the
key. Options that are specified before the -p argument are global and therefore affect
all packages. Options that are specified after the -p argument are local to that specific
package. For example, if the -D argument is entered before the -p argument, then all
packages are transferred to the specified directory.
Example output
# appkgtrans -p ngn_platform -v AP18.0.0001

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
B-29
Issue 14, September 2009
See notice on first page

PRELIMINARY

Command Reference

appkgtrans

PRELIMINARY

B-30

appkgunload
...................................................................................................................................................................................................................................
Syntax
appkgunload -p package [-v version] [-s server] [-q] [-d directory]
-p package

remove the package named package from the MM-AP

-v version

remove the version named version of the package that is to be

removed from the MM-AP

-s server

remove the package from the remote server with the node name
server ( appkgunload defaults to the local server)

-q

bypass system messages while the command executes

-d directory

remove the package from the source directory named directory rather
than from the default directory /var/spool/ap/pkg/package/version

PRELIMINARY

Command Reference

Typical usage
appkgunload -p package

Description

The appkgunload command is used to unload MM-AP packages that have previously
been loaded onto the OMP with appkgload or that have previously been transferred to
the MM-AP with appkgtrans. The -p and -v options are provided so that a select
version of a particular package can be specified. Multiple versions of multiple
packages can be specified by repeated use of the -p and -v options. The user will be
prompted for any required information that is not supplied on the command line.
When appkgunload is executed using the default options, the user will be prompted to
select the version of the package to be unloaded (removed) from the
/var/spool/ap/pkg/package/version directory on the local server. If the package resides
in a local source directory other than /var/spool/ap/pkg, use the -d directory option.
The -s option is currently provided as a sanity check. If the user is using remsh to run
this command remotely and wants to assure that the command is running on the
correct MM-AP, then use the -s option. If the -q option is used, required information
must be supplied on the command line.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
B-31
Issue 14, September 2009
See notice on first page

PRELIMINARY

The user executing the appkgunload command must be able to write to the local source
package directory.

PRELIMINARY

Command Reference

appkgunload

The position of command line options determine how they work. The -p option is the
key. Options that are specified before the -p are global and therefore affect all
packages. Options that are specified after the -p are local to that specific package. For
example, if the -d option is used before the -p option, then all packages will be
unloaded from the specified source directory.
Example output
# appkgunload -p ngn_platform

PRELIMINARY

1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
The following platform versions are currently loaded:
1234567890123456789012345678901212345678901234567890123456789
1) AP18.0.0001
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
2) ALL
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
Enter the menu number of the ngn_platform package to unload: 1
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
The ngn_platform package (version AP18.0.0001) will be
1234567890123456789012345678901212345678901234567890123456789
unloaded from the /var/spool/ap/pkg directory.
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
Do you want to continue [no]: yes
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789

B-32

applatconfig
...................................................................................................................................................................................................................................
Syntax
applatconfig -s remote_MM-AP -v asset
applatconfig -s remote_MM-AP -a asset

PRELIMINARY

Command Reference

applatconfig -s remote_MM-AP -r asset

applatconfig -s remote_MM-AP -c asset
applatconfig -s remote_MM-AP -l
-a asset

add an asset to the MM-APs configuration

-c asset

list all assets that are part of the MM-APs configuration

-l server

list a particular asset that is part of the MM-APs configuration

-r asset

remove an asset from the MM-APs configuration

-s remote_MMAP

specify the name of the remote MM-AP that is to be configured

-v asset

verify that an asset can be added to an MM-APs configuration

(before the -a is attempted)

Typical usage
applatconfig -s apxy -a asset

Description

The applatconfig command is used to tell the specified MM-AP to configure an

asset, to remove an asset from its configuration, or to list those assets that have been
configured. It controls which assets, from the MM-AP bundle, are installed on a
particular MM-AP. An asset can be thought of as a feature, or as part of a feature.
The MM-AP bundle contains many different packages. Some packages can be installed
on all MM-APs; other packages must only be installed on those MM-APs that are
configured for a particular feature. The applatconfig command is therefore used to
help the bundle install only those packages that are needed.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
B-33
Issue 14, September 2009
See notice on first page

PRELIMINARY

The -s option is ued to specify the name of the remote MM-AP that is being
configured. The -v option is used to verify that an asset can be added to an MM-APs
configuration (before the -a is attempted). The -a option is used to add an asset to the
MM-APs configuration. The -r option is used to remove an asset from the MM-APs

PRELIMINARY

Command Reference

applatconfig

configuration. The -c option is used to list all assets that are part of the MM-APs
configuration. The -l option is used to list a particular asset that is part of the
MM-APs configuration.
The applatconfig command is run from the OMP. It affects the configuration of the
remote MM-AP specified by the -s option. It must be executed separately for each
MM-AP that requires the particular configuration.
Example output
OMP-> applatconfig -s ap01 -a NGNrcs
Resource configured: NGNrcs
OMP->
OMP-> applatconfig -s ap01 -r NGNrcs
Removed resource: NGNrcs

PRELIMINARY

OMP->

B-34

aprecover
...................................................................................................................................................................................................................................
Syntax

aprecover
Description

PRELIMINARY

Command Reference

The aprecover command is used to recover the MM-AP from various Software Update
(SU) or generic retrofit failures. The aprecover command is interactive; it prompts the
user for the name of the ECP version and reports the status of the recovery. In some
cases, the aprecover command detects that the user must perform specific actions
before recovery can proceed, tells the user what to do next, and then exits.
Execute the aprecover command if the MM-AP fails to reboot during an SU or
generic retrofit attempt, especially if the Admin log indicates that the MM-AP was
taken offline because of a version mismatch between the MM-AP and the ECP.
The aprecover command attempts to do the following:
1. Find a version of MM-AP platform software that is compatible with the ECP
version and make that version of the MM-AP platform software the default version.
2. Find a Reliable Clustered Computing (RCC) software version that is compatible
with the MM-AP platform software version that was identified in Step 1 and make
that version of the RCC software the default version.
If the aprecover command cannot perform Step 1 or Step 2, it tells the user what
actions the user should probably perform to enable the recovery to succeed and then
exits. After the user performs the indicated actions, the user can re-execute aprecover
to complete the recovery.

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
B-35
Issue 14, September 2009
See notice on first page

PRELIMINARY

Command Reference

aprenew
...................................................................................................................................................................................................................................
Syntax
aprenew [ -v backup_version ] [ -o options ] [ -s server ] [ -l login ]
[ -z password ] [ -u | -q ]
-v backup_
version

restore the version named version of the backup saveset

-o options

pass the options specified by options to the load-specific copy of

aprenew that is used for the restore

-s server

get the backup saveset that is to be restored from the remote

server with the node name server (aprenew defaults to apomp)

-l login

use the login login on the remote server when reading the
backup saveset remotely

-z password

use the password password for the remote login specified with
the -l option.
For security purposes, use of the -z option is discouraged.

-q

run in quiet mode (do not prompt for additional information

(cannot be used with the -u option)

-u

update the list of packages to be transferred and installed

interactively (cannot be used with the -q option).

Typical usage

aprenew

PRELIMINARY

Description

The aprenew command is used during MM-AP replacement procedures to

automatically configure an MM-AP as the MM-AP was configured at the time of the
specified apback up operation. MM-AP packages that were installed during the
specified apbackup operation are automatically transferred to the MM-AP, installed,
and activated. MM-AP applications that were configured during the specified apbackup
operation are reconfigured automatically. A select group of files (/etc/passwd) are
restored. The aprenew command does not restore the entire MM-AP but only those
components of the MM-AP that are necessary to reestablish a previous configuration.
For example, aprenew restores login IDs and passwords but does not restore
user-defined $HOME directories.
apbackup saves a load-specific copy of aprenew. aprenew executes this saved copy.
Use the -o option to pass options to this saved copy of aprenew.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

B-36

aprenew

Use the -v option to restore a specific version of the backup. Backup savesets are
normally kept on the OMP server, which is named apomp. If the backup saveset is kept
on a different server, specify that server with the -s argument.
To execute the aprenew command, you must be able to write to the local backup
directory. To specify a remote login, use the -l argument. The remote login that you
specify with the -l option to the aprenew command must be able to read the remote
backup directory. You can use the -z option to specify the password for the remote
login, but for security purposes, we recommend against use of this option.

PRELIMINARY

Command Reference

Use the -u option to interactively update the list of packages being transferred and
installed. Use the -q (quiet) option if you do not want to be prompted for additional
information while the aprenew command executes. If you do use the -q option, you
must supply all required information on the command line. The -u and -o options are
mutually exclusive.
Because it affects the running MM-AP, aprenew requires the MM-AP to be offline.
Example output

The following is an example of aprenew output:

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
B-37
Issue 14, September 2009
See notice on first page

PRELIMINARY

PRELIMINARY
PRELIMINARY

Command Reference

aprenew

1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
The text associated with this backup follows:Before configuring cell 222
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
Should the aprenew operation continue [yes]? yes
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
Inspection of ap01 shows that the following packages need to be
1234567890123456789012345678901212345678901234567890123456789
installed but are not yet available on ap01:
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
fms_rcc version 060102
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
ngn_platform version AP18.0.0001
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
These packages will be transferred from apomp.
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
AP package transfer makes heavy use of the TCP/IP networkand may therefore affect
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
Do you want to continue [no]: yes
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
Enter the login on apomp [root]: root
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
Enter the password for root on apomp:
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
Transfer of fms_rcc package (060102) from apomp beginning at Mon Apr 1 09:06:44 C
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
Transfer of ngn_platform package (AP18.0.0001) from apomp beginning at Wed Mar 24
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
Inspection of ap01 shows that the following packages need to be
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
installed on ap01:
1234567890123456789012345678901212345678901234567890123456789
fms_rcc version 060102
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
ngn_platform version AP18.0.0001
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
These packages will be installed.
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

B-38

aprenew

PRELIMINARY

Command Reference

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
B-39
Issue 14, September 2009
See notice on first page

PRELIMINARY

Command Reference

apsettimers
...................................................................................................................................................................................................................................
Syntax
apsettimers [set | reset]

Description

A generic retrofit, or retrofit backout, must be completed in a finite period of time. The
apsettimers command is used to temporarily extend this period of time by first
increasing the values of MM-AP transition timers and then restoring them to their
original values. The apsettimers command toggles between setting (extending)
timer values and resetting timer values. The first time apsettimers is called without a
command line parameter, it extends the timers. The second time apsettimers is called
without a command line parameter, it extends the timers. When apsettimers is called
a second time, it restores the timers to their original values. Alternatively, apsettimers
can be called with a command line parameter, either set to extend the timers or reset to
restores the timers.
The apsettimers command must be run while the MM-AP is online. It must be
executed on each MM-AP that will participate in the retrofit, or retrofit backout. A data
file, /var/ap/platform/apsettimers.data, is used to track when the timers were last set.
Important! Be sure to restore the timers to their original values once the retrofit,
or retrofit backout, is complete.

PRELIMINARY

Example output

B-40

flxactivate
...................................................................................................................................................................................................................................
Syntax
flxactivate [-n] [-q] [-r] [-v] [ pkgnames | pkginstances |
pkgdirectories ] flxactivate -A [-nqv]
-A

When the MM-AP is online, select only those packages for activation
that are safe for online activation. If packages are not specified, check
all packages for whether they can safely be activated onlinen. If the
MM-AP is not online, select all packages for activation that have a
next link. Mutually exclusive with -r.

-n

Perform a dry run, that is, displays actions that would be taken by
flxactivate without actually activating anything.

-q

Prevent flxactivate from prompting for input while it executes (quiet

mode).

-r

Reboot automatically when flxactivate finishes executing if any

package requests it (by default, flxactivate displays instructions to
the user if a reboot is necessary).

-v

Display the list of packages being activated and deactivated (verbose

mode).

pkgnames

Activate only the named packages ( pkgnames).

PRELIMINARY

Command Reference

Question: Any delimiter between package names in a list?

By default, flxactivate activates all new packages.
pkginstances Activate only the named package instances ( pkginstances).
pkgdirectoriesActivate only packages in the the named package directories
(pkgdirectories).

Description
flxactivate activates all new software packages on an FMS MM-AP, independent of

bundling. It shifts current versions to previous, and next versions to current. It also
links in appropriate files into run time locations in /flx.
In the current release, the following FMS platform packages are enabled for online
activation:

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
B-41
Issue 14, September 2009
See notice on first page

PRELIMINARY

Command Reference

flxactivate

PRELIMINARY

codes:
0

Successful completion.

Fatal error.

Non-fatal warning occurred.

Successful completion. System must be rebooted for activation to fully take

effect. If the -r option was used, flxactivate will reboot the system
automatically at completion.

A package has requested that flxactivate reboot the system immediately.

Activation will resume automatically after the system reboots.

Any other exit code means an error occurred.

B-42

flxbackout
...................................................................................................................................................................................................................................
Syntax
flxbackout [-n] [-q] [-r] [-v] [ pkgnames | pkginstances |
pkgdirectories ]
-n

perform a dry run, that is, displays actions that would be taken by
flxbackout without actually backing anything out

-q

prevent flxbackout from prompting for input while it executes (quiet

mode)

-r

reboot automatically when flxbackout finishes executing if any

package requests it (by default, flxbackout displays instructions to the
user if a reboot is necessary)

-v

display the list of packages being activated and deactivated (verbose

mode)

pkgnames

back out only the named packages ( pkgnames)

PRELIMINARY

Command Reference

Question: Any delimiter between package names in a list?

By default, flxbackout undoes the last flxactivate.
pkginstances

back out only the named package instances ( pkginstances)

pkgdirectories

back out only packages in the the named package directories

(pkgdirectories)

Description

The flxbackout command reverts an FMS MM-AP system to previous versions of

software packages by undoing the last flxactivate. It shifts current versions to next
and previous versions to current. With invalid options or arguments, flxbackout just
displays command usage and version number.
flxbackout indicates the results of its execution with one of the following numeric

codes:
Successful completion.

Fatal error.

Non-fatal warning occurred.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
B-43
Issue 14, September 2009
See notice on first page

PRELIMINARY

Command Reference

flxbackout

Successful completion. System must be rebooted for backout to fully take

effect. If the -r option was used, flxbackout will reboot the system
automatically at completion.

A package has requested that flxbackout reboot the system immediately.

Backout will resume automatically after the system reboots.

PRELIMINARY

Any other exit code means an error occurred.

B-44

flxbackup
...................................................................................................................................................................................................................................
Syntax
flxbackup [-s destination_server] [-d destination_directory] [-m
transfer_mode] [-l login] [-z password] [-v backup_version] [-q] [-n
satellite_hostname | -G ]

PRELIMINARY

Command Reference

Description

This command
Options

The flxbackup command has the following options:

-n

no logging

-q

quiet mode, no additional information message

-t timeout_value

timeout value in seconds

-h hostname

change security state for the specified host

-a insecure |
secure

change host security state

Output

Command execution acknowledgement.

Examples

To enable security cluster wide, execute the following command:

flxsshadmin -a 1

To enable security for host flx01, execute the following command:

flxsshadmin -h flx01 -a 1

Files

/flx/data/FMSssh/inetd_config/00default

See also
flxsshkeygen, flxsshkeysync, flxsshstatus
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
B-45
Issue 14, September 2009
See notice on first page

PRELIMINARY

/etc/inetd.conf.conf

PRELIMINARY

Command Reference

flxbuninfo
...................................................................................................................................................................................................................................
Syntax
flxbuninfo [ -v ] [bundle_file_name]
-v

list all packages in each bundle (verbose mode)

bundle_file_name

list of bundle file name(s) ( the default is all installed bundles

plus uninstalled bundle files in the /var/flx/bun directory)

Description

PRELIMINARY

The flxbuninfo command lists information about installed or uninstalled bundles or

both. flxbuninfo returns 0 if it completes successfully, 1 if an error occurred during
execution.

B-46

flxchkfwacv
...................................................................................................................................................................................................................................
Syntax
flxchkfwacv

Description

PRELIMINARY

Command Reference

The flxchkfwacv command verifies the default values shown for the following alarm
card firmware parameters:

RCC_poweroff=true

RCC_poweron=true
RCC_reset=true

panic_dump=false

serial2_baud=9600
serial2_data=7

serial2_hw_flowcontrol=false

serial2_inactivity=false
serial2_mode=rcc

serial2_parity=odd

serial2_stop=1
solaris_watchdog_reboot=false

The flxchkfwacv command reads files in the /flx/FMSfwacv/current/data and

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
B-47
Issue 14, September 2009
See notice on first page

PRELIMINARY

Example output

PRELIMINARY

Command Reference

flxchkfwacv

PRELIMINARY

1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
[flx02]-> flxchkfwacv
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
WARNING: Alarm Card parameter RCC_poweroff = false, expected true
1234567890123456789012345678901212345678901234567890123456789
WARNING: Alarm Card parameter RCC_poweron = false, expected true
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
WARNING: Alarm Card parameter RCC_reset = false, expected true
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
GOOD: Verified Alarm Card parameter panic_dump = false
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
GOOD: Verified Alarm Card parameter serial2_baud = 9600
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
GOOD: Verified Alarm Card parameter serial2_data = 7
1234567890123456789012345678901212345678901234567890123456789
GOOD: Verified Alarm Card parameter serial2_hw_flowcontrol = false
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
GOOD: Verified Alarm Card parameter serial2_inactivity = false
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
GOOD: Verified Alarm Card parameter serial2_mode = rcc
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
GOOD: Verified Alarm Card parameter serial2_parity = odd
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
GOOD: Verified Alarm Card parameter serial2_stop = 1
1234567890123456789012345678901212345678901234567890123456789
GOOD: Verified Alarm Card parameter solaris_watchdog_reboot = false
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
[flx02]->
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789

B-48

flxcoremgmt
...................................................................................................................................................................................................................................
Syntax
flxcoremgmt days
days

delete core files in days number of days

PRELIMINARY

Command Reference

Description

The flxcoremgmt command saves application core files before they are overwritten
and deletes them when they are seven days or older than a specified number of days
(default is seven days)
Core files generated when applications fail contain information critical to determining
the cause of the failure. To prevent a subsequent core file from overwriting an existing
core file in the same directory before someone has an opportunity to analyze the
existing file, FMS MM-AP software appends the name of the failing process to the
name of the core file (for example, core.nslookup or core.DBinit) and saves the
resulting file in /var/corefiles.
flxcoremgmt also periodically checks the age of all core files in /var/corefiles and

removes any that are seven days or older than a specified number of days (default is
seven days) .This is controlled by an associated entry in roots crontab file, which is
automatically controlled by the MM-AP .
IP developers, check the following with your SMEs:

Does your product use the FMS default for core-file deletion (7 days)?
Do they want you to explain to customers how to change this default, e.g., to
expire files more quickly, or not? If they do, use the following paragraph, example,
and reference.

To shorten or lengthen the expiration interval for application core files, create a file
/flx/data/FMSadmin/ unique_name .cronmgmt, with a standard cron entry in which you
specify the desired number of days as an argument to /flx/bin/flxcoremgmt.
Example:
0 2 * * * /flx/bin/flxcoremgmt 3

Reference: For more information on the format of cron entries, execute

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
B-49
Issue 14, September 2009
See notice on first page

PRELIMINARY

man crontab

PRELIMINARY

Command Reference

flxcronmgmt
...................................................................................................................................................................................................................................
Syntax
flxcronmgmt

Description

The flxcronmgmt command updates roots crontab file

(/var/spool/cron/crontabs/root). By default, flxcronmgmt adds the following entries to
roots crontab when FMS MM-AP software is first installed on the FMS MM-AP.

and standard cron entries for flxlogmgmt and flxcoremgmt with the desired
scheduling parameters.
Example:
0 1 * * 6 /flx/bin/flxlogmgmt

PRELIMINARY

0 2 * * 6 /flx/bin/flxcoremgmt

Reference: For more information on the format of cron entries, execute

man crontab

Important! Do not modify the rscadm date -s or APauto_backup entryies.

B-50

flxcronmgmt

To have flxcronmgmt add additional entries to roots crontab file, create a file
/flx/data/FMSadmin/ unique_name .cronmgmt with standard cron entries for each of
the commands that you want flxronmgmt to add to roots crontab file.
Important! flxcronmgmt uses all cronmgmt files, both default and custom, in
updating roots crontab file.

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
B-51
Issue 14, September 2009
See notice on first page

PRELIMINARY

Command Reference

PRELIMINARY

Command Reference

flxdeactivate
...................................................................................................................................................................................................................................
Syntax
flxdeactivate [-n] [-q] [-r] [-v] pkgnames
-n

perform a dry run, that is, display actions that would be taken by
flxdeactivate without actually deactivating anything.

-q

prevent flxdeactivate from prompting for input while it executes

(quiet mode)

-r

reboot automatically when flxdeactivate finishes executing if any

package requests it (by default, flxdeactivate displays instructions to
the user if a reboot is necessary)

-v

display the list of packages being activated and deactivated (verbose

mode)

pkgnames

deactivate only the named packages ( pkgnames)

Question: Any delimiter between package names in a list?
Notes: At least one package name must be specified on the flxdeactivate
command line.

Description

The flxdeactivate command deactivates the current version of specified software

packages so that no version is current. It does this by shifting the current version to
previous and removing applicable files from public directories.
flxdeactivate indicates the results of its execution with one of the following numeric

PRELIMINARY

codes:
0

Successful completion.

Fatal error.

Non-fatal warning occurred.

Successful completion. System must be rebooted for deactivation to fully

take effect. If the -r option was used, flxdeactivate will reboot the
system automatically at completion.

A package has requested that flxdeactivate reboot the system

immediately. Deactivation will resume automatically after the system
reboots.

Any other exit code means an error occurred.

B-52

flxfwac
...................................................................................................................................................................................................................................
Syntax
flxfwac [-c | -d]
-c

check the alarm card firmware version and issue a warning if it is older than
that supported by the current MM-AP release

-d

update the Remote System Control commands and download the latest
firmware if either action is necessary

PRELIMINARY

Command Reference

Description

This command is used on the MM-AP to update the alarm card firmware and Remote
System Control (RSC) commands to the levels supported by the current MM-AP
release. For example, in the current MM-AP release, the supported alarm card firmware
version is 2.0.26.
The flxfwac command is also used to download alarm card firmware when the alarm
card is not responding.
If the alarm card currently has a version of firmware newer than or equal to the level
supported by the current MM-AP release, then flxfwac exits silently and successfully
without generating any output.
If the alarm card currently has a version of firmware older than the level supported by
the current MM-AP release and flxfwac is called with the -c option, then flxfwac
issues a warning about this condition, but does not download the firmware.
If either the version of firmware on the alarm card or the version of the RSC
commands on the MM-AP is older than the level supported by the current MM-AP
release, and flxfwac is called with the -d option, then flxfwac downloads the
firmware and updates the RSC commands.
The flxfwac command also attempts to synchronize the time of day of the alarm card
with that of the MM-AP after a successful firmware download. Note that the command
attempts to download the firmware up to a maximum of 5 times at 30-second intervals
before failing. It also attempts to synchronize the time of day up to a maximum of 5
times, again at 30-second intervals before failing. As a result, it is possible to see
intermediate error messages on failed download or date- synchronization attempts.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
B-53
Issue 14, September 2009
See notice on first page

PRELIMINARY

If flxfwac fails for any reason, it displays an error message.

PRELIMINARY

Command Reference

flxfwac

Example output

Following is an example of running flxfwac -c:

flxap 01-> flxfwac -c
flxfwac: WARNING: Alarm Card Firmware needs an UPREV, run flxfwac -d
manually
flxap 01->

Following is an example of running flxfwac -d. In this example, flxfwac generates

intermediate error messages as it attempts to download firmware and synchronize the
time of day of the alarm card with that of the server, but exits successfully, as
indicated by the response to the echo $? command (0).

Following is an example of running flxfwac -d, in which flxfwac was unable to

successfully update the RSC commands, as indicated by the non-zero response to the
echo $? command:
[ flxap 05]-> flxfwac -d
ERROR: could not create directory /var/flx/patch
[ flx ap 05]-> echo $?

PRELIMINARY

1
[ flxap 05]->

B-54

flxfwacv
...................................................................................................................................................................................................................................
Syntax
flxfwacv

Description

PRELIMINARY

Command Reference

The flxfwacv command sets the following alarm card firmware parameters with the
default values shown:

RCC_poweron=true

RCC_poweroff=true

RCC_reset=true
panic_dump=false

serial2_baud=9600

serial2_data=7
serial2_hw_flowcontrol=false

serial2_inactivity=false

serial2_mode=rcc
serial2_parity=odd

serial2_stop=1

solaris_watchdog_reboot=false

The flxfwacv command reads files in the /flx/FMSfwacv/current/data and

/flx/data/FMSfwacv directories to determine these default values. Values in the
/flx/data/FMSfwacv directory take precedence over those in the
/flx/FMSfwacv/current/data directory
Note to IP developers: the values listed above are the FMS defaults. Your product team
may have chosen different default values. Check with them for any custom values.
The command is typically used when replacing or updating software on a boot disk
drive, or when replacing an alarm card, to ensure that the values of the firmware
parameters on the alarm card match the values for those parameters stored on disk.
The command performs a soft reset on the alarm card, making the alarm card
inaccessible for about 40 seconds after running this command (the alarm card will not
respond during the soft reset). The command does not wait for the soft reset to
complete.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
B-55
Issue 14, September 2009
See notice on first page

PRELIMINARY

The flxfwacv command has no options other than the -? option, which displays the
following usage message:

PRELIMINARY

Command Reference

flxfwacv

The flxfwacv command generates no output if it executes successfully. Otherwise,

flxfwacv outputs an error message.
flxfwacv outputs the following error message, for example, when it is unable to call

PRELIMINARY

the rscadm command because another instance of the rscadm command is already
running, and the alarm card fails to respond after the lock is freed.

B-56

is co

flxfwacv

1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
[flx05]-> flxfwacv
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
rscadm: The RSC lock file was found. Only one
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
instance of rscadm can run at a given time
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
ERROR: Failed setting Alarm Card parameters RCC_poweron = true
1234567890123456789012345678901212345678901234567890123456789
through rscadm
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
rscadm: The RSC lock file was found. Only one
1234567890123456789012345678901212345678901234567890123456789
instance of rscadm can run at a given time
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
ERROR: Failed setting Alarm Card parameters RCC_poweroff = true
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
through rscadm
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
rscadm: The RSC lock file was found. Only one
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
instance of rscadm can run at a given time
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
ERROR: Failed setting Alarm Card parameters RCC_reset = true through
1234567890123456789012345678901212345678901234567890123456789
rscadm
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
rscadm: RSC firmware not responding
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
ERROR: Failed setting Alarm Card parameters solaris_watchdog_
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
reboot = false through rscadm
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
rscadm: RSC firmware not responding
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
ERROR: Failed setting Alarm Card parameters panic_dump = false
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
through rscadm
1234567890123456789012345678901212345678901234567890123456789
[flx05]->
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
B-57
Issue 14, September 2009
See notice on first page

PRELIMINARY

Command Reference

PRELIMINARY

Command Reference

flxlogmgmt
...................................................................................................................................................................................................................................
Syntax
flxlogmgmt

Description

The flxlogmgmt commands trims the following Solaris log files to the sizes indicated
each day:

/var/adm/utmp (36 KB)

/var/adm/wtmp (36 KB)

/var/adm/utmpx (372 KB)

/var/adm/wtmpx (362 lines)

/var/adm/sulog (600 lines)

/var/log/syslog (1000 lines)

Reference: For more information about these Solaris files, use the man on-line help
facility.
To change the sizes to which flxlogmgmt trims these files, for example, to free up
additional space on FMS servers MM-APs, or to have flxlogmgmt trim other files as
well, create a file /flx/data/FMSadmin/unique_name.logmgmt with the following
entries:

PRELIMINARY

where
x

is the number of bytes to which you want the binary file trimmed
(can also be expressed as integer*1024, for example, 18*1024

is the number of lines to which you want the text file trimmed

filename

is the full path name of a file that you want flxlogmgmt to trim

file_format

is B for binary files, T for text files

B-58

trim_size

flxlogmgmt

is the number of bytes (for binary files) or the number of lines

(for text files) to which you want flxlogmgmt to trim the file

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
B-59
Issue 14, September 2009
See notice on first page

PRELIMINARY

Command Reference

PRELIMINARY

Command Reference

flxname
...................................................................................................................................................................................................................................
Syntax
flxname server_id [network] FMS Aruba 1.0.0[-noboot] [-noacreset] FMS

Aruba 1.0.0
flxname
flxname
flxname
flxname

spare
alarmcard
sync
-v

server_id

is the frame number minus (-) 1 (x), and the slot number where the
server currently resides (y). For example, if you are initializing the
server that resides in frame 1, slot 3, x is 0 (frame 1 - 1 = 0), y is 3,
and server_id is 03, or 3
You can omit the x component of server_id if that number is 0, that
is, for servers in frame 1, server_id is simply the server slot number
1-8

network

is the first two octets of the IP address of the dual-rail LAN to which
the server will be connected. The default address is 10.0. Also
available are addresses in the range 172.16 to 172.31.

-noboot

personalize the server (change its host name and, if desired, its IP
address), but do not reboot the server

-noacreset

personalize the server (change its host name and, if desired, its IP
address), but do not reset the alarm card

-v

display server name, operating system and release, and model (400S
or 800S), and complete network interface information

Typical usage
Description

PRELIMINARY

The flxname command personalizes an FMS serverMM-AP, changing its name and,
where desired, its IP address from the factory defaults to those of the FMS-based
productan MM-AP. Servers in new frames ship from the factor with a name in the
range flxspare1 through flxspare8 and network address 10.0. Replacement boot drives
ship from the factory with the name flxspare.
flxname is also used to rename a server to flxap spare when a boot drive is being

removed for maintenance (flxname spare), to personalize a servers alarm card

(flxname alarmcard), and to update server names and IP addresses when changes to
those configurations are made (flxname sync).
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

B-60

flxname

Question: Would someone use flxname spare when doing maintenance on a boot drive?
If not, when?
Running flxname updates the following system files:

PRELIMINARY

Command Reference

/etc/opt/SUNWconn/trunking/bin/nettr.sh (if the FMSMM-AP has IP trunking

configured for fault-tolerant LAN or FT-LAN)
Question: Which FMS products configure IP trunking for FT-LAN? When will
MM-AP?
/flx/data/FMSadmin/ftlan-config (if flxname creates FT-LAN network interfaces)
flxname indicates the results of its execution with one of the following numeric codes:

Successful completion.

-1

An error occurred.

All flxname output is logged in /var/flx/logs/FMSadmin/flxname.log.

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
B-61
Issue 14, September 2009
See notice on first page

PRELIMINARY

Command Reference

flxpkginfo
...................................................................................................................................................................................................................................
Syntax
flxpkginfo [ -a ] [ -c ] [ -k] [ -n] [ -o ] [ -p ] [ -x ] [pkgnames |
pkginstances]
-a

Select all installed package instances. This option is the same as

-c -n -o -p.

-c

Select currently active package instances. This is the default option.

-k

Show package keyword values.

-n

Select the next package instances to be activated. This option selects

the packages that will be activated if flxactivate is executed with
no arguments.

-o

Select package instances that would not be selected by -c -n -p.

-p

Select the most recently previously activated package instances.

-x

Show extra information about each package.

pkgnames

Report information about only the named packages ( pkgnames). The

default is all current FMSMM-AP package instances.
Question: Any delimiter between package names in a list?

pkginstances

Report information about only the named package instances

(pkginstances). The default is all current FMSMM-AP package
instances.
Question: Any delimiter between package names in a list?

Description

The flxpkginfo command reports information about installed FMSMM-AP packages.

flxpkginfo indicates the results of its execution with one of the following numeric

PRELIMINARY

codes:
0

Successful completion.

<>0

An error occurred.

B-62

SMxmldump(1)
...................................................................................................................................................................................................................................
Name
SMxmldump - generates easy-to-read text files from XML-based Service Measurement

files.

PRELIMINARY

Command Reference

Synopsis
SMxmldump [-a ] | [[-d <dir> ] [-f <filename> ] [-h ] [-H <hour> ] [-M
<quarter>] [-s <dir> ] [-t ] [-e <x|s>] [-z ]]

Description
SMxmldump prints a raw data report for the XML-based Service Measurement files

specified on the command line. It is used to generate 1xRNC and 3G1x Short Interval
ASCII files from XML source files.
SMxmldump can be used in 2 ways:

Automated Mode: this mode is intended for use with cron, but can be used at the
command line. Automated usage is specified by the -a option. In automated
mode, the behavior of the tool can be controlled by a configuration file.
Manual Mode: this mode is intended for command line usage and is the default
mode. Behavior of the tool in manual mode is controlled by a series of command
line options.

Options

The following options may appear in any order:

-a

Automatic mode

-d

(Manual mode only) Destination directory for generated files. The

default destination directory is current directory. Example:
SMxmldump -d /alt/dir (generated files are found in /alt/dir).

-f

(Manual mode only) Specify the xml file to dump (-H option will be
overridden). The filename should be compliant to 3GPP standard:

-h

Prints the help section of the SMxmldump command to the terminal.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
B-63
Issue 14, September 2009
See notice on first page

PRELIMINARY

A <timestamp>_g3SubNetwork=ECP<ECP number>,
g3ManagedElement=RNC<RNC number>>,rncFunction=<Function
name>z

PRELIMINARY

Command Reference

SMxmldump(1)

-H

(Manual mode only) Specifies ending hour of the data to dump.

-M

(Manual mode only) Specifies the ending quarter(local time) of 3G1X

Short Interval SM data to dump, option value should be within 1-4(1
means the first quarter while 4 means the last quarter). This option is
only for 3G1X Short Interval SM.

-s

(Manual mode only) Source directory for XML files. The default source
directory is current directory and the XML files in source directory are
supposed to be compressed files.

-t

Outputs the requested data to standard out (the terminal or pipe). Pipes
can be used to redirect or alter data flow).

-e

(Manual mode only) Specify the type of dump file, only the following
two options are allowed: x for 1xRNC data; s for 3G1X Short
Interval SM data.

-z

(Manual mode only) Whether the dump output is compressed. Will not
take effect when -t is specified.

Examples

Generates a report for a single hours worth of data for hour 16 and redirects the
output to a different file:
SMxmldump -H 16 -t > /var/tmp/hour16

Generates a report for a single quarters worth of data for hour 16, the second quarter
and redirects the output to a different file:
SMxmldump -H 16 -e s -M 2 -t > /var/tmp/hour16.2

Files
SMxmldump is located in /omp/bin. The default output directory is

PRELIMINARY

/omp/omp-data/SMxml/dump for 1xRNC and /omp/omp-data/SMxml/dump2 for 3G1X

Short Interval SM. Output can be redirected using the-t option. The output location
can be changed in configuration file for automated mode or using -d option for manual
mode.
The configuration file is located in /omp/omp-data/SMxml/config. The current content
of the configuration file includes:
1. destination- Define the directory that contains the generated text files.
2. source - Define the directory that contains the source XML files.

B-64

SMxmldump(1)

3. files - Define the maximum number (1xRNC) or hour (3G1X Short Interval SM)
of most recently generated files (based on OMP timestamp) to be preserved on the
OMP.
4. time - Define if the XML filenames include time information in Universal Time
(GMT) or Local Time. This field can either have a value of Universal or Local.
If the value in the time field does not match either Universal or Local,
SMxmldump shall default to Universal Time. This is only for 1xRNC.
Important! The timezone settings between the OMP and the RNC-AP MUST be set
consistently. Specifically, the SMxmldump.cfg file on the OMP and the FMSsm.tune
file on the RNC-AP must both have timezone settings of either Universal (GMT)
or Local. If the timezone settings on OMP and RNC-AP are out-of-sync, this will
result in unexpected results. For example, the data generated by SMxmldump could
be timestamped incorrectly.
5. dtdname - Define the DTD file name. This is 1xRNC validation file.

PRELIMINARY

Command Reference

6. dtdlocation - Define the location where the DTD file can be found.
7. xsdname - Define the XSD file name. This is 3G1X Short Interval SM validation
file.
8. xsdlocation - Define the location where the XSD file can be found.
9. stylesheet - Define the location and file name of the stylesheet.
Important! the destination and source keyword only take effect for automated
mode.
See also

crontab(1), FLEXENT(TM)/AUTOPLEX(R) Wireless Networks Executive Cellular

Processor (401-610-135).

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
B-65
Issue 14, September 2009
See notice on first page

PRELIMINARY

Appendix C: Service measurement

supplement

This appendix provides information relevant to the SMxmldump tool, and to

management of XML RNC PM data.
Contents
SMxmldump tool

C-2

Time zone synchronization (OMP and RNC-AP)

C-4

Time zone verification and update

C-5

Managing XML RNC PM data

C-8

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
C-1
Issue 14, September 2009
See notice on first page

PRELIMINARY

Service measurement supplement

SMxmldump
tool
...................................................................................................................................................................................................................................
Introduction

The SMxmldump tool, similar to the legacy SMsmdump tool, provides a means for
converting XML Service Measurement (SM) files.
Enabling quick analysis

Data in compressed XML format is not necessarily convenient for quick analysis by
the Service Provider on the OMP. Furthermore, when problems occur, Service
Providers may not be in a position to wait for a post-processing system to make the
data available.
As a result, the SMxmldump tool has been developed to convert Service Measurements
from the XML format into a text file that provides a user-friendly format.
Usage

The SMxmldump tool executes automatically as a cron job that converts XML data
into text files on an hourly basis. The process for decompressing, converting, and
consolidating the data into a single compressed text file, takes less than a minute to
complete.
Storage and file names

Compressed text files are stored in a separate directory with file names such
as:smdata.16.Z (for hour 16). File names are reused, and files are overwritten every 24
hours.
Up to 24 compressed text files (24 hours worth) are maintained on the OMP.
Manual page

The tool can also be executed manually at the command line. For additional
information concerning the use of this tool, refer to SMxmldump(1) (p. B-63) in
Appendix B, Command Reference.
Help for SMxmldump

The following help output is returned when the SMxmldump tool is invoked as

PRELIMINARY

SMxmldump h:

C-2

SMxmldump tool

PRELIMINARY

Service measurement supplement

Time zone synchronization (OMP and RNC-AP)

For information relevant to keeping time zone conventions consistent between the
OMP and the RNC-AP, refer to Time zone synchronization (OMP and RNC-AP)
(p. C-4).

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
C-3
Issue 14, September 2009
See notice on first page

PRELIMINARY

Service measurement supplement

Time
zone synchronization (OMP and RNC-AP)
...................................................................................................................................................................................................................................
Introduction

Time zone settings for the OMP and RNC-AP(s) must be consistent (the same) to
ensure that the XML SM data processed by the SMxmldump tool is accurate.
Time zone settings

Time zone settings on the OMP and RNC-AP can be either of the following:

Universal/Greenwich Mean Time (GMT)

Local time.

OMP configuration file

Time zone setting for the SMxmldump tool on the OMP is controlled in the
SMxmldump.cfg file, located by the following path:
/omp/omp-data/SMxml/config/SMxmldump.cfg
RNC-AP tunable files

To control time zone setting, the Service Provider has the option of using the default
tunable file (FMSsm.tune) located in the /FMSsm/current/data directory, or creating an
override tunable file (FMSsm.tune), and placing it in the /flx/data/FMSsm directory.
See Managing XML RNC PM data (p. C-8) for specifics.
If the default tunable file (FMSsm.tune) provided in the /FMSsm/current/data directory
is used, then the default of universal time will be in effect. If an override tunable file
(FMSsm.tune) is provided in the /flx/data/FMSsm directory, then the Service Provider
can specify either local time, or universal time as desired.
Procedure

The procedure for verifying and synchronizing time zone settings between the OMP
and RNC-AP is listed as follows:

PRELIMINARY

Time zone verification and update (p. C-5)

C-4

Time
zone verification and update
...................................................................................................................................................................................................................................
Purpose

Either to verify or change the time zone settings for the OMP and RNC-AP(s).
Reason to perform

PRELIMINARY

Service measurement supplement

Either of the following:

You are unsure as to whether the time zone settings between the OMP and
RNC-AP(s) are consistent, and you will need to make them consistent if they are
not.

You need to change the time zone settings for both the OMP and RNC-AP(s) from
universal time to local, or vice versa.
Important! You must only change the time zone setting for the RNC-AP(s) in the
override FMSsm.tune file. See Managing XML RNC PM data (p. C-8) for
specifics on how to create the override file.

Update becomes effective

Depending on what interval during the hour you implement a change, the first hour
after the change might not pick up all the 15 minute TPU files. Some of these files
will have been generated with universal time file names (not local), or vice versa,
depending on what was previously configured.
Procedure

Perform the following procedure to verify, or change the time zone settings for the
OMP and RNC-AP(s):
...................................................................................................................................................................................................

Login as root to the OMP.

...................................................................................................................................................................................................

Enter the config directory in which the SMxmldump.cfg file resides as follows:
cd /omp/omp-data/SMxml/config<CR>
...................................................................................................................................................................................................

Open (vi) the SMxmldump.cfg file as follows: vi SMxmldump.cfg<CR>

...................................................................................................................................................................................................

Check the time parameter by doing a search on, time=

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
C-5
Issue 14, September 2009
See notice on first page

PRELIMINARY

Result The SMxmldump.cfg file opens.

PRELIMINARY

Service measurement supplement

Time zone verification and update

Result The expected value for the time parameter is either:Universal or Local.

Note that the default is Universal. Note that if the value for the time parameter
does not match either Universal or Local, then SMxmldump defaults to universal
time.
...................................................................................................................................................................................................

If you wish to change the setting, edit the time parameter appropriately.
...................................................................................................................................................................................................

To quit the SMxmldump.cfg file, do either of the following:

q:<CR> or wq:<CR>
...................................................................................................................................................................................................

Login as root to the RNC-AP.

...................................................................................................................................................................................................

Run the following command:

stopVM FLXSMPE<CR>

Result The Virtual Machine (VM) process is halted on the RNC-AP.

...................................................................................................................................................................................................

Enter the FMSsm directory in which the override FMSsm.tune file resides as follows:
cd /flx/data/FMSsm<CR>
...................................................................................................................................................................................................

Open (vi) the override FMSsm.tune file as follows:

vi FMSsm.tune<CR>
Result The FMSsm.tune file opens.
...................................................................................................................................................................................................

Check the FLXsmFileNameTimeType parameter by doing a search on,

FLXsmFileNameTimeType.
Result The expected value for the FLXsmFileNameTimeType parameter is either: 1

for universal or 0 for local. Note that the default is 1.

PRELIMINARY

...................................................................................................................................................................................................

If you wish to change the setting, edit the FLXsmFileNameTimeType parameter

appropriately.
...................................................................................................................................................................................................

To quit the override FMSsm.tune file, do either of the following:

q:<CR> or wq:<CR>

C-6

Time zone verification and update

...................................................................................................................................................................................................

Run the following command:

startVM FLXSMPE<CR>

Result The Virtual Machine (VM) process restarts on the RNC-AP.

END OF STEPS

PRELIMINARY

Service measurement supplement

...................................................................................................................................................................................................

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
C-7
Issue 14, September 2009
See notice on first page

PRELIMINARY

Service measurement supplement

Managing
XML RNC PM data
...................................................................................................................................................................................................................................
Introduction

Management of XML RNC PM data is accomplished through the use of tunable

variables that modify the default functionality of the tunable file associated with the
collection of the XML RNC PM data.
Tunable variable

A tunable variable has the following syntax:

keyword:value

where:
keyword is the name of the tunable
value is a string or number that modifies the FMS softwares default behavior

Tunable file

The tunable file may contain one or more tunable keyword:value pairs. Only one
keyword:value pair can be specified on a line. A line beginning with the # character
indicates the line is a comment and is to be ignored.
There are two tunable files associated with service measurement FMS software. Each
tunable file is identified by the same name, FMSsm.tune.
FMSsm.tune file locations

The FMSsm.tune file is located in two directories, as follows:

${FLXDIR}/FMSsm/current/data

${FLXDIR}/data/FMSsm

where:
${FLXDIR} is a shell environment variable that identifies the location of FMS software

on a node.
Default tunable directory

PRELIMINARY

The tunable file (FMSsm.tune) located in the following default directory, should never
be modified:
${FLXDIR}/FMSsm/current/data
Any change made to the FMSsm.tune file in this directory will disappear when a
software update of the FMSsm package occurs, thereby returning all tunables to their
original (default) values.
...................................................................................................................................................................................................................................
401-710-082
Alcatel-Lucent - Proprietary
See notice on first page
Issue 14, September 2009

C-8

Managing XML RNC PM data

Override tunable directory

The tunable file (FMSsm.tune) located in the following override directory, can be
modified:
${FLXDIR}/data/FMSsm
Tunables in the override tunable directory are not modified when the FMSsm package
is updated; therefore, any specified tunables will carry forward to be used by the new
version of software. Service Providers can deliver these as part of their bundle.

PRELIMINARY

Service measurement supplement

Same names required

The override tunable file must have the same name as the tunable file provided with
the FMSsm package and the tunable keyword name must also match. When FMS
software looks for a tunable value, the customer override location is checked first and
if the tunable is found, it is used. If it is not found, then the packages default tunable
files are checked.
Modifying tunables

Tunables in the override FMSsm.tune file are modified in a manner similar to that
described in Step 7 through Step 14 of Time zone verification and update (p. C-5).
Not all tunables may require modification

A Service Provider does not have to modify all the tunables that exist for the
FMSsm.tune file in the override tunable directory; only those tunables whose default
values are to be overridden need to be specified.
Note that if the override FMSsm.tune file exists, and a tunable name is not specified,
then the FMSsm.tune file in the default directory is checked.
Tunable details

Table C-1, Tunable details (p. C-9) provides a list of the tunable names, descriptions
and values.
Table C-1

Tunable details

Name

Description

Value Range

Default

FLXsmRunClientScript

Instruct SM process to
run clients script to
further process XML
files.

0 - do not run
clients script

Instruct SM process to
collect data for the
partial interval or full
interval only.

0 - partial
interval OR 1 full interval

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
C-9
Issue 14, September 2009
See notice on first page

PRELIMINARY

FLXsmFullInterval

1 - run clients
script

PRELIMINARY
PRELIMINARY

Service measurement supplement

Table C-1

Tunable details

Managing XML RNC PM data

(continued)

Name

Description

Value Range

Default

FLXsmFileNameTimeType

Set the type of time_t

conversion to either
local time (0) or
universal GMT time
(1). This time_t
conversion is used in
the process of
generating the XML
file name. The starting
time and end time are
converted to either
local or GMT time and
formatted into the XML
file name.

0 - local time OR
1 - gmt time

FLXsmNumOfWorkerThread

Set the number of

worker threads needed
in the SM process.

1 to 64

FLXsmSizeOf_Worker
Thread_SharedMem

Set the size of the

shared memory used by
the worker threads. The
size of the shared
memory should be able
to be evenly divided by
the number of worker
threads provided by
FLXsmNumOfWorkerThread tunable.

2048 to 131072

10240

C-10

Table C-1

Tunable details

Managing XML RNC PM data

(continued)

Name

Description

Value Range

Default

FLXsmXMLFileAge

SM audit is scheduled
to run every 24-hour to
remove old XML files
under the
/var/flx/data/FMSsm/
xml directory. This
tunable is used to set
the maximum age (in
minutes) of the XML
files. The default age is
48 hours, so the audit
runs every 24-hours and
the XML files older
than 48 hours are
removed.

1440 to 10080

2880

FLXsmXMLFileCompressed

The generated XML file

is compressed if this
tunable is set to 1,
otherwise set it to 0
then the file will not be
compressed. Note that
this option will
compress each XML
file that gets generated.
It will NOT combine
XML files together and
compress the big file.

0 - no compress
OR 1-compress

PRELIMINARY

Service measurement supplement

The FLXsmFLXsmNumOfWorkerThreads and FLXsmSizeOf_WorkerThread_SharedMem

tunables are two versatile tunables that can be adjusted to improve the parallel
processing based on the applications need. These two tunables should be changed with
coordination so that the size of the shared memory is able to be evenly divided by the
number of worker threads provided by the FLXsmNumOfWorkerThread tunable. To
activate the change of these tunables, the FLXSM NCVM needs to be restarted.

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
C-11
Issue 14, September 2009
See notice on first page

PRELIMINARY

Appendix D: History of revision

This appendix describes the history of revisions to the 1X Radio Network Controller
(RNC) Operations, Administration, & Maintenance (OA&M) information product.
Contents
Issue 7

D-2

Issue 6

D-3

Issue 5

D-5

Issue 4

D-8

Issue 3

D-15

Issue 8

D-21

Issue 9

D-22

Issue 10

D-23

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
D-1
Issue 14, September 2009
See notice on first page

PRELIMINARY
PRELIMINARY

History of revision

Issue
7
...................................................................................................................................................................................................................................
Reason for reissue

This is the seventh issue of this information product.

Specific Issue 7 updates are provided as follows:

Step 26, Result (Replace a B-PCF) has been modified.

TPU GUI performance issues under Accessing TPU GUI has been expanded.

New step 9 under Changing a subnets VCC VPI has been added

Chapter 7: Monitoring the system has been updated with, Crossover LAN
connectivity monitoring and Cross-over LAN cable connection and verification.

D-2

Issue
6
...................................................................................................................................................................................................................................
Reason for reissue

This is the sixth issue of this information product. This Issue provides updates
pertinent to the following FIDs:

7098.18 - Packet Core Support of 3G-1X Inter-Vendor, Inter-MSC ANSI-41 Hard

Handoff for Packet Data Calls.

12306.0 - IP Based Soft Handoff for the RNC.

12306.2 - IPSHO Completion for RNC.

12555.0 - BSID NID Override in B-PCF and E-PCF.

12665.0 - Alternate FS_QFAF control.

12868.0 - PCF INCALL pacing enhancement.

PRELIMINARY

History of revision

Specific Issue 6 updates are provded as shown in the following table.

Pages

Update

1-1 through 1-8

New chapter on hazard statements.

2-9 through 2-10

Updates pertaining to IPSHO related information.

2-17

New topic, IP backhaul.

2-18 through
2-20

New topic, IP-based soft handoff.

2-25 through
2-26

Updated CDMA 1X RNC software architecture

pertaining to IPSHO related information.

2-33

Updated User bearer processing software

components and interfaces pertaining to IPSHO
related information.

2-36 through
2.37

Updated Physical Network Connectivity

pertaining to IPSHO related information.

4-12 through
4-23

Updated tables 4-3 through 4-15.

4-24 through
4-29

Updated table 4-16 and 4-17.

6-44 through 663

Revised Restoring RNC database information.

10-8 through
10-10

Revised RNC-related XML count groups

information.

11-3 through
11-10

Revised RC/V and FAF/QFAF information.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
D-3
Issue 14, September 2009
See notice on first page

PRELIMINARY

Chapter

PRELIMINARY
PRELIMINARY

History of revision

Issue 6

Chapter

Pages

Update

14-1 through
14-9

Added Configuring IPSHO connectivity

information.

15-1 through
15-144

In general, provided update of graphics

throughout this chapter.

15-43 through
15-44

Added Growing an IPSHO GICC

pairinformation.

15-45

Added Alternate QFAF control information.

D-4

Issue
5
...................................................................................................................................................................................................................................
Reason for reissue

This is the fifth issue of this information product. This Issue provides updates pertinent
to the following FIDs:

10444.13 - RNC Integrity Monitor (RIM) Phase 3

10933.0 - CDMA 1X RNC Migration to Modular Shelf-M, Part 2

10936.2 - CICC Performance Optimization to Support More Than 501 Channels

12088.3 - Capability to run TPU-CLI Commands on MM-TI-CLI

12335.0 - 1X RNC Combo card replacement

PRELIMINARY

History of revision

Specific updates in Issue 5 that have been incorporated since the prior GA issue are
listed in the following table.

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
D-5
Issue 14, September 2009
See notice on first page

PRELIMINARY
PRELIMINARY

History of revision

Issue 5

D-6

Issue 5

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
D-7
Issue 14, September 2009
See notice on first page

PRELIMINARY

History of revision

PRELIMINARY

History of revision

Issue
4
...................................................................................................................................................................................................................................
Reason for reissue

This is the fourth issue of this information product. This Issue provides updates
pertinent to the following FIDs:

10444.7 - RNC Integrity Monitor (RIM) Phase 2

10444.10 - Packet Core RNC Extended Reliability and Performance Measurements

12254.1 and 12254.2 - R25.0 B-PCF Current Engineering/Maintenance
Updates/Features
10674.2 - IP Backhaul on the CDMA RNC

10615.0 - Automatic Protection Switching on the RNC

PRELIMINARY

Specific updates in Issue 4 that have been incorporated since the prior GA issue are
listed in the following table.

D-8

Issue 4

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
D-9
Issue 14, September 2009
See notice on first page

PRELIMINARY

History of revision

PRELIMINARY
PRELIMINARY

History of revision

Issue 4

D-10

Issue 4

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
D-11
Issue 14, September 2009
See notice on first page

PRELIMINARY

History of revision

PRELIMINARY
PRELIMINARY

History of revision

Issue 4

D-12

Issue 4

PRELIMINARY

History of revision

Revision 1

Revision 1 provides updates regarding the chapters specified in the following table.

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
D-13
Issue 14, September 2009
See notice on first page

PRELIMINARY

History of revision

Issue 4

Revision 2

PRELIMINARY

Revision 2 corrects mddb.cfv in step 26 (1) of the B-PCF replacement procedure in

Chapter 8 to mddb.cf.

D-14

Issue
3
...................................................................................................................................................................................................................................
Reason for reissue

This is the third issue of this information product. This Issue provides updates pertinent
to the following FIDs:

8002.7 - RNC Release 24 OAM Software

9093.2 - SUA SUGR for RNC

10444.6- Packet Core RNC Reliability Measurements

12026.2 - R24 B-PCF Current Engineering Maintenance/Updates

12048.2 - Optical GIGE Interface on the GICC

8107.11 - OMC-RAN 1X RNC Maintenance

8107.41 - OMC-RAN TPUGUI AP Maintenance

8107.42 - OMC-RAN RNCDBMS AP Maintenance

PRELIMINARY

History of revision

Specific updates in Issue 3 that have been incorporated since the prior issue are listed
in the following table.

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
D-15
Issue 14, September 2009
See notice on first page

PRELIMINARY
PRELIMINARY

History of revision

Issue 3

D-16

Issue 3

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
D-17
Issue 14, September 2009
See notice on first page

PRELIMINARY

History of revision

PRELIMINARY
PRELIMINARY

History of revision

Issue 3

D-18

Issue 3

PRELIMINARY

History of revision

Revision 1

TPU GUI performance issues.

Amended information regarding TPU GUI access via EMS GUI and direct access.

References to Chapter 7 for troubleshooting TPU GUI access problems.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
D-19
Issue 14, September 2009
See notice on first page

PRELIMINARY

Revision 1 provides updates regarding Chapter 5 as follows:

PRELIMINARY

History of revision

Issue 3

TPU GUI login synchronization and user sessions.

The repositioning of the Update java runtime parameters procedure to Chapter 7.

Revision 1 provides updates to Chapter 7 regarding troubleshooting of TPU GUI

access problems.
Revision 1 provides updates to Chapter 8 regarding the updating of the external IP
address for optical GigE ports.
Revision 1 provides updates to Chapter 9 regarding the SMxmldump tool.
Revision 1 provides updates to Chapter 12 regarding B-PCF growth (Configure B-PCF,
step 7) and B-PCF degrowth (B-PCF Shutdown and B-PCF Halt).
Revision 1 includes updates to Chapter 13 regarding new information pertaining to
TPU GUI login synchronization, and revised information pertaining to local TPU GUI
Administrator tasks.
Revision 1 provides an update to Appendix B regarding the SMxmldump tool.
Revision 1 includes the addition of Appendix C, Service measurement supplement.
Revision 2

Revision 2 provides an update to the B-PCF replacement procedure in Chapter 8

regarding the FMS golden image package steps 25 and 26.
Revision 3

PRELIMINARY

Revision 3 corrects mddb.cfv in step 26 (1) of the B-PCF replacement procedure in

Chapter 8 to mddb.cf.

D-20

Issue
8
...................................................................................................................................................................................................................................
Reason for reissue

Specific Issue 8 updates are provided as shown in the following table.

Chapter

Pages

Update

4-25

Revised Command Line

Interface (CLI)

4-26 through 4-33

Revised Input/Output
Messages

4-44

Revised Operations and

Maintenance Center Radio
Access Network
(OMC-RAN)

7-21

Revised Figure 7-17: IX

RNC information page

7-25

New Input Command,

GET:RNCTPUETHERNET

8-18 through 8-23

New B-PCF monitoring

and flow control

10-6 and 10-7

Revised Polling

10-11 and 10-12

New B-PCF XML counts

(hourly or 15 minute)

10-13 and 10-14

New Change B-PCF

Service Measurement (SM)
interval

15-4

Revised GICC, CICC, and

B-PCF population rules
second bullet, and Figure
15-2

16-6 through 16-9

New Eliminate open

consoles

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
D-21
Issue 14, September 2009
See notice on first page

PRELIMINARY

History of revision

PRELIMINARY

History of revision

Issue
9
...................................................................................................................................................................................................................................
Reason for reissue

Specific Issue 9 updates are provided as follows:

An Important! note was added on page 3-42.

Added a new row, Configure Far CA Reachability to Table 4-9.

Revised row name, BHS Statistics Information Table 4-14.
Provided new tables (Table 4-15 through Table 4-19).

Updated Input/Output Messages pages 4-29 through 4-37.

Added three new rows (Monitoring GICC BHS status, Obtaining ping status
of external IP network, and Triggering FARCA reachability test) to Table 8-1.
Added new topics (1xRNC packet filtering, Far end CA audit, and To
enable/disable far end CA audits) pages 8-24 through 8-29.

PRELIMINARY

Added 1X RNC packet filtering, pages 11-8 and 11-9.

Added Inter-MSC ANSI-41 Hard Handoff for Packet Data Calls, pages 11-9
through 11-11.
Added new row, 1636 to FAF table on page 11-13.
Added new topics (Golden image restoration (B-PCF), To download cpio file
from Online Customer Support Site (OLCS), and To load and install B-PCF
golden image packagE) pages 11-25 through 11-41.
Provided revised topic (IPSHO configuration) pages 14-9 through 14-11.
Added Provisioned ID for BSID NID Override:, Fast Handoff Pre-Registration
Timer: and Network Reactivation Delay Timer: rows to Table 15-3.
Added MEID added to airlink: accounting record: and Fast Handoff Enable: to
Table 15-5.

D-22

Issue
10
...................................................................................................................................................................................................................................
Reason for reissue

The following changes were made for R31, Issue 10:

All former references to telnet, rlogin, and FTP have been changed to SSH and
SFTP.
Added IPBH Audit Configuration, page 4-21.
Added REPT-RNC-SECURITY-ALERT, page 4-36.

Added topic, On-line help, page 4-48.

Updated Problem checklist, item 3, page 8-64.
Revised topic Integration scenarios, page 14-11.

Added procedure, Change cluster ID of a single MSC, page 14-12

Added procedure, Integrate IPSHO enabled RNC and its neighbors, page 14-16.

Added topic, Centralized security management phase three, page 16-10.

PRELIMINARY

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
D-23
Issue 14, September 2009
See notice on first page

PRELIMINARY

History of revision

PRELIMINARY

Glossary

Numerics
2G

Second Generation
3G

Third Generation
3G-1X

CDMA 3rd Generation-1.25 MHz Carrier

3GPP

3rd Generation Partnership Project

3GPP2

3rd Generation Partnership Project 2

A10/A11

The control (A11) and bearer (A10) interfaces between the PCF and PDSN.
A8/A9

The control (A9) and bearer (A8) interfaces between the RLP and PCF.
AAL

ATM Adaptation Layer

AAL1

ATM Adaptation Layer 1

ATM Adaptation Layer 2

AAL5

ATM Adaptation Layer 5

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
GL-1
Issue 14, September 2009
See notice on first page

PRELIMINARY

AAL2

PRELIMINARY

Glossary

Alarm Card On the CPSB Shelf

Access Network

Network that connects access technologies (such as Radio Access Network) to the core
network.
ACDN

Administrative Call Processing and Database Node

All-IP network

An IP-based network that uses IP for transport of all user data and signaling between the
access network and the service network.
ANSI

American National Statndards Institute

Application Processor
API

Application Processor Interface

APPCC

Application Processor Cluster Complex

APS

Automatic Protection Switching

ATM

Asynchronous Transfer Mode

Authentication

The act of verifying the identity of an entity (for example, user device).
....................................................................................................................................................................................................................................

B-PCF

Blade Packet Control Function

PRELIMINARY

Base Station

A Base Station is the element in the radio telecommunications system, which interfaces
with the Mobile Station (MS). The BS is composed of a Call Control component, BSC,
and one or more Channel Element components, BTS.
BHCA

Busy Hour Call Attempt

GL-2

Base Station
BSC

Base Station Controller

BTS

PRELIMINARY

Glossary

Base Transceiver Station

Community Address
Call

A session between two or more network entities.

Call Control

The set of functions that allows establishment, management, and release of one or more
sessions between two or more callable entities.
CBU

Circuit Break Unit

CCC

CDMA Cluster Controller

CCU

CDMA Channel Unit

CDMA

Code Division Multiple Access

CDN

Call processing and Database Node

Channel Element-in the BTS

CESHL2

Cell Entity to Speech Handler Layer 2 protocol

CESHL3

CIC

Circuit Identification Code

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
GL-3
Issue 14, September 2009
See notice on first page

PRELIMINARY

Cell Entity to Speech Handler Layer 3 protocol

PRELIMINARY

Glossary

CICC

Common ICC in TPU

CLI

Command Line Interface

CLSI

Cell Site Integrity/Initialization

Communication Module in the 5ESS Switch DCS

CNI

Common Network Interface

CPS

AAL2 Common Part Sublayer

cPSB

Compact PCI Packet Switched Backplane

CRU

Customer Replaceable Unit

CSN

Cell Site Node

DACS

Digital Access and Cross-connect System

DCS

Digital Cellular Switch

DFI

Digital Facilities Interface

DHCP

Dynamic Host Configuration Protocol

DLCI

PRELIMINARY

Data Link Connection Identifier

DLMS

Data Link Management System

DLN

Data Link Node

GL-4

DNS

Domain Name Server

DSC

Direct Switch Connect

PRELIMINARY

Glossary

E-PCF

Ethernet Packet Control Function

ECMR

Executive Cellular Processor Message Router

ECP

Executive Cellular Processor

ECPC

Executive Cellular Processor Complex

EIN

Ethernent Interface Node

EMS

Element Management System

Ethernet Switch card inside the TPU

ESC

Ethernet Switch Card

ETSI

European Telecommunication Standards Institute

FAF

Feature Activation File

FDBMS

Flexent Database Management System

FDD

FIP

Frame Interface Panel

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
GL-5
Issue 14, September 2009
See notice on first page

PRELIMINARY

Feature Description Document

PRELIMINARY

Glossary

FLXSM

Flexent Service Measurement platform software

FMSR1SR

A release 1 FMS frame for housing the FMS410 Server APs that is Satellite Ready. It
can support RCC in either the old mode (like an FMSR1 frame) or in the new mode
(like an FMSR2 frame).
FMSR2

A release 2 FMS frame for housing the APs that supports the R2 drawer. There is no
RCC watchdog hardware in this frame. RCC is provided by a SUN card.
Frame Selector Resource Manager (FSRM)

A function of the RNC within a traffic processor unit that provides the allocation of the
frame selector, selection of the PCF resource, signaling to and from the TCS and to and
from the PCF.
FRPH

Frame Relay Protocol Handler

FRU

Field Replaceable Unit

Frame Selection
FSRM

Frame Selector Resource Manager

GICC

Gateway ICC inside TPU

GNPAP

GNP Application Processor

GRE

Generic Routing Encapulation

GUI

PRELIMINARY

Graphical User Interface

Home Agent

GL-6

Handoff

The transfer of a users connection from one radio channel to another while maintaining
the same service. There are instances where the service may be downgraded as a result
of the handoff (for example, due to QoS limitations).
HLR

Home Location Register

PRELIMINARY

Glossary

Handover/handoff
Home Network

The network where the subscriber has a subscription. The concept normally refers to the
network owned by a specific carrier, rather than any geographical concept. Thus, home
network may be global.
HW

Hardware
....................................................................................................................................................................................................................................

ICC

Intelligent Carrier Cards inside cPSB/TPU shelf

ICMP

Internet Control Message Protocol

IETF

Internet Engineering Task Force

IMSHO

Inter-MSC Soft Handoff

IMSI

International Mobile Station Identifier

IMSMR

IMS Message Router

Intelligent Network
INAP

Internet Protocol

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
GL-7
Issue 14, September 2009
See notice on first page

PRELIMINARY

IN Application Part

PRELIMINARY

Glossary

IP Multimedia Domain

The IP Multimedia Domain provides service control and mobility management via
current and evolved versions of Mobile IP, Diameter, and SID protocols. IP Multimedia
Domain services include voice, data, and multimedia services. These services and
functions will be provided using the evolved IS-2000 family of standards over the air
interface and evolved IOS in the RAN. Service control, mobility management, and
session management will be provided using Mobile IP, Diameter, and SIP protocols.
IPv4

Internet Protocol 4
IPv6

Internet Protocol 6
ISDN

Integrated Services Digital Network

ISP

Internet Service Provider

ISUP

ISDN User Part (call signaling portion of SS7)

ITU

International Telecommunications Union

JDBC

Java Database Connectivity -- Java-based protocol using SQL

L2TP

Layer 2 Tunneling Protocol

LAG

Link Aggregation Group

LAN

Local Area Network

PRELIMINARY

LDAP

Lightweight Directory Access Protocol

LEC

Local Exchange Carrier

GL-8

Legacy MS Domain

The Legacy MS Domain provides service and mobility management via the current and
evolved versions of the TIA/EIA-41 protocol. Evolved legacy services include voice
services, data services, and new and evolved interactions between voice and data
services (e.g., call waiting interactions). These services and functions will be provided
using the evolved IS-2000 family of standards over the air interface, evolved IOS in the
RAN, evolved TIA/EIA-41 standards (Telecommunications Industry
Association/Electronics Industry Association) signaling, and IP-based bearer streams and
other IP-based signaling in the Core Network.

PRELIMINARY

Glossary

LIMA

Location Independent Message Addressing

LMT

Local Maintenance Terminal

LOS

Loss of Signal
LPDC HC

Local Power Distribution Cabinet High Current

MAC

Media Access Control

MAP

Mobile Application Part

MCR

Mobile Call Register

MGC

Media Gateway Controller

MGW

Media Gateway
MIB

Management Information Base

MM Cabinet

Cabinet for housing MM-APs: RNC-AP, OAM Proxy AP, etc.

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
GL-9
Issue 14, September 2009
See notice on first page

PRELIMINARY

Mobility Manager (also known as NGN-AP)

PRELIMINARY

Glossary

MM-AP

Mobility Manager - Application Processor

MMRS

Multi-Media Resource Server

Mobility

The ability to access services from any point in the network. The degree of service
availability may depend on the access network capabilities, as well as any service level
agreements between the users home network and the visited network. Types of mobility
include personal mobility, service mobility, and terminal mobility.
Mobility Management

The set of functions used to manage a mobile user accessing a network other than that
users home network. These functions include communication with the home network for
purposes of authentication, authorization, location, and download of user inforamtion.
MRF

Media Resource Function

MRS

Media Resource Server

Mobile Station
MSC

The Mobile Switching Center provides switching, call control, and mobility management
for radio telecommunications system.
MSP

Mobility Server Platform

MTP

Message Transfer Part (SS7)

NAT

Network Address Translator

NEBS

PRELIMINARY

Network Establishment Building System

NGN-AP

Next Generation Network Application Processor (also known as MM-AP)

NMS

Network Management System/Server

GL-10

NNI

Network Node to Node Interface

OAM

Operations, Administration, and Maintenance

PRELIMINARY

Glossary

OAM Proxy AP

An MM-AP with the RNC application software, i.e., TPUGUI VCVM and RNC-DB
VCVM
OAM&P

Operations, Administration, Maintenance, and Provisioning

OC3

Optical Carrier 3
OMC

Operations and Management Center

OMP

Operations and Management Platform

Packet Control Function (PCF)

An entity in the radio access network that manages the relay of packets between the BS
and the PDSN. The PCF is usually located in the BS.
PBP

Packet Bus Protocol

PCF

Packet Control Function

PCF-CP

Packet Control Function Call Processing

PCF-TP

Packet Control Function Traffic Processing

PCM

Pulse Code Modulation

Personal Communication Service

PDSN

Packet Data Serving Node

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
GL-11
Issue 14, September 2009
See notice on first page

PRELIMINARY

PCS

PRELIMINARY

Glossary

Protocol Handler
PHV

Protocol Handler for Voice

PMC

Processor Mezzanine Card

Point of Attachment Mobility

The ability of a subscriber to use a mobile terminal to gain access to any home or
visited network (for example, roaming).
POTS

Plain Old Telephone Service

Packet Pipe
PPC

Power PC
PPGM

Packet Pipe, Group, and Member

PQII

PowerQuicc II
PS

Packet Switched
PSTN

Public Switched Telephone Network

PSU

Packet Switching Unit

PSUCA

PSU Community Address

PVC

PRELIMINARY

Permanent Virtual Circuit

QFAF

Feature Activation File with Qualification

GL-12

QoS

Quality of Service
Quality of Service (QoS)

A specification of the service performance characteristics of one or more sessions

between two of more network entities. QoS specifies parameters including but not
limited to data rate, latency, jitter, and delivery assurance.

PRELIMINARY

Glossary

Radio Access Mobility

The ability of a subscriber to move within or between radio access networkds in real
time while maintaining a connection.
Radio Cluster Server (RCS)

A UNIX process running on Application Processor that controls a modular cell

(analogous to the RCC in a Series II BTS).
Radio Network Controller (RNC)

A set of functional elements consisting of frame selectors, a single traffic control

function, packet control functions, and OA&M manager.
Radio Network Controller Manager (RNC-M)

A function within the RNC that provides the OAM&P for traffic processors of the RNC.
RAN

Radio Access Network

RANAP

Radio Access Network Application Part

RAS

Registration, Admission, and Status

RC/V

Recent Change/Verify
RCC

Reliable Cluster Computing

RCC

Radio Cluster Controller

Radio Cluster Server

RDBMS

Relational Database Management System

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
GL-13
Issue 14, September 2009
See notice on first page

PRELIMINARY

RCS

PRELIMINARY

Glossary

RDBU

Ring Data Base Update

RLC

Radio Link Control

RLP

Radio Link Protocol

RMI

Remote Method Invocation

RNC

Radio Network Controller

RNC-DB

Radio Network Controller Database

RNC-M

Radio Network Controller Manager

Roaming

Action whereby users access services while outside of their subscriber home network.
ROP

Read Only Printer

RPCN

Ring Peripheral Controller Node

Radio Resource
RTP

Real Time Protocol

Shelf Controller
SCCP

PRELIMINARY

Switching Connection Control Part (SS7)

SCF

Service Control Function

SCN

Switched Control Network

GL-14

SCP

Service Control Point

SDP

Status Display Page

SDU

PRELIMINARY

Glossary

Selection Distribution Unit

Service Creation

An environment or a set of techniques that allows a service provider to autonomously

generate and deploy new network features to be offered to subscribers.
Service Mobility

The ability of a subscriber to access subscribed and otherwise authorized services from
any home or visited network.
Session

A logically associated set of communication streams.

SFTP

Secure File Transfer Protocol

SGCP

Simple Gateway Control Protocol

Speech
SHO

Soft Hand Off

SII

Series II cell
SIP

Session Initiated Protocol

Service Measurement
SNMP

Simple Network Management Protocol

Signaling System 7
SSH

Secure Shell
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
GL-15
Issue 14, September 2009
See notice on first page

PRELIMINARY

SS7

PRELIMINARY

Glossary

SUGR

Software Updates and Generic Retrofit

A standard digital transmission facility with 24 DS0 channels

TAG

Trunk Access Gateway

TCAP

Transaction Capabilities Application Part

TCP

Transmission Control Protocol

TCP/IP

Transmission Control Protocol/Internet Protocol

TCS

Traffic Control Server

TDM

Time Division Multiplexing

TDMA

Time Division Multiple Access

Technician Interface
TIA/EIA

Telecommunications Industry Association/Electronics Industry Association

TICC

Traffic ICC (also known as Traffic Processor [TP])

TMN

Telecommunications Management Network

PRELIMINARY

Traffic Processor (also known as TICC)

TPU

Traffic Processing Unit

TPU-M

TPU-Manager -- element manager

GL-16

Traffic Control Server (TCS)

A function within the RNC that is global resource manager the requests for bearer
resources for the RNC.
....................................................................................................................................................................................................................................

UDP

User Datagram Protocol

PRELIMINARY

Glossary

UMTS

Universal Mobile Telecommunications System

UNI

User Network interface

Virtual Channel
VCC

Virtual Channel Connection

VCI

Virtual Channel Identifier

VCVM

Virtual Cluster Virtual Machine

Visited Network

The visited network is a carriers network where a subscriber currently is roaming. The
term visited network is more business significant, than geographically significant.
VLR

Visitor Location Register

VoIP

Voice over IP
VP

Virtual Path
VPC

Virtual Path Connection

Virtual Path Identifier

VPPVC

Virtual Path Permanent Virtual Connections

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
GL-17
Issue 14, September 2009
See notice on first page

PRELIMINARY

VPI

PRELIMINARY

Glossary

VRRP

Virtual Router Redundancy Protocol

VSRP

Virtual Service Redundancy Protocol

WAG

Wireless Access Gateway

WAP

Wireless Application Protocol

Wireless All-IP System

PRELIMINARY

This term is used as an equivalent term to the 3G Wireless End-to-End IP Multimedia

System.

GL-18

PRELIMINARY

Index

Numerics

1X RNC
evolution, 2-2
3G packet data:sub
3G packet data,ecp, 11-8
3GPP2

Accessing
EMS GUI, 6-5
OAM proxy AP, 6-4

RNC-AP, 6-4

existing, 11-6

SDPs, 6-27

field,OMC-RAN Managed,
11-6

All-IP network, 2-4

TPU CLI, 6-17

TPU GUI, 6-6
Alarm card
controls, A-5

data,transaction delay, 2-3,

2-3

faceplate, 3-26, A-4

network architecture, 2-2

function, 3-26

packet data,applications, 2-3

hot swap switch, A-6, A-19

packet data,call processing,

2-5

status LEDs, 3-26, A-4

packet data,offload, 2-3,

2-4, 2-4
resource,contention
limitation, 2-3, 2-3
5EGW
order of growth, 15-30

alarm levels
RNC, 4-41

provisioning, 11-6
associated states
EMS GUI, 5-2
ATM SHO universe
subnet,change connection
type, 12-18
subnet,change VCC VPI,
12-28
subnet,move RNC, 12-23
subnet:add new, 12-6
subnet:communication, 12-2

RNC, 4-42

subnet:Community Address,
12-2

Alarms
input messages, 4-28

Read Only Printer, 7-36

alternate routing
RNC, 2-14

subnet:initial installation,
12-2
subnet:remove, 12-12
VCC network:connectivity,
12-3
VCC network:VPI, 12-3

....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
IN-1
Issue 14, September 2009
See notice on first page

PRELIMINARY

output messages, 4-28

Status Display Pages, 4-40

field,RNC AP, 11-6

alarm list (GUI)

.............................................................
A access to

apeqp form
applicable screens, 4-39

TICLI, 6-18

data,throughput limitation,
2-3, 2-3

RNC,call dispostion, 2-14

RC/V, 6-25

All-IP architecture, 2-3

3G1X

Alternate Routing

PRELIMINARY

Index

VPC network:connectivity,
12-2

RNC,dimensions, 3-3, 3-3,

3-3

field,PKT CORE DATA,

11-4

VPC network:VPI, 12-3

RNC,ECBU, 3-14, 3-14

field,RNC Homed, 11-4

VPC-default, 12-4

RNC,Ethernet Switch Card,

3-27

field,RNC ID, 11-4

VPC-to-VCC transition,
12-4

RNC,fan trays, 3-24

.............................................................

RNC,fault groups, 3-7

B Backing up

RNC,Frame Interface Panel,

3-12

OAM Proxy AP, 6-28, 6-32

RNC Database, 6-36
RNC-AP, 6-28, 6-32
Blade PCF
replace, 9-23
Blade-Packet Control Function
backplane ports, 3-39
functions, 3-39
LEDs, 3-40
.............................................................
C Cabinet

5ESS lineup, 3-5

RNC,front access, 3-3

RNC,FRUs, 9-4
RNC,GICC, 3-33
RNC,grounding, 3-13
RNC,LED states, 3-11, A-2
RNC,LEDs, 3-9, 3-9, 3-11,
A-2
RNC,physical organization,
3-3
RNC,power, 3-7, 3-13
RNC,power connections,
3-13

provisioning, 11-4
cold swappable
components, 9-3
Command Execution
TICLI, 6-18
TPU CLI, 6-17
UNIX, 4-37
Command Line Interface
ECP legacy, 4-2
MM TICLI, 4-27
OMC-RAN TICLI, 4-27
Commands (applicable)
ECP legacy TI, 4-2
TICLI, 4-28
TPU-CLI, 4-28
UNI chkfwacv, B-47

cable shroud, 3-4

RNC,Power Distribution
Shelf, 3-14

end guard, 3-5

RNC,rear access, 3-3

UNIX,appkgchk, B-21

filler stanchions, 3-5

RNC,terminal server, 2-23,

3-17

UNIX,appkginfo, B-23

RNC,universal
compatibility, 3-3

UNIX,appkgunload, B-31

RNC,2310, 3-20, 3-20

RNC,alarm card, 3-26
RNC,B-PCF, 3-39, 3-39

UNIX,apactivate, B-3

UNIX,appkgrm, B-26

UNIX,applatconfig, B-33
CDMA

RNC,characteristics, 3-6

UNIX,aprecover, B-35

PRELIMINARY

air interface, 2-12

RNC,chassis components,
3-21

IP-based network, 2-2

RNC,CICC, 3-37

laptop computers, 2-12

RNC,components, 3-7

mobile types, 2-7

RNC,cPSB chassis, 3-20

mobile users, 2-12

RNC,CRUs, 9-4

packet mode data, 2-2, 2-12

RNC,design, 3-3

cell2 form
existing, 11-4

UNIX,aprenew, B-36
UNIX,apsettimers, B-40
UNIX,flxactivate, B-41
UNIX,flxbackout, B-43
UNIX,flxbackup, B-45
UNIX,flxbuninfo, B-46
UNIX,flxcoremgmt, B-49

IN-2

Index

UNIX,flxcronmgmt, B-50

cabinet indicators, A-2

UNIX,flxdeactivate, B-52

cabinet indicators,LED
states, A-2

UNIX:apappconfig, B-5
UNIX:apapply, B-6
UNIX:apbackout, B-7
UNIX:apbackup, B-9
UNIX:apcc_ip_migr, B-12
UNIX:apinstall, B-16
UNIX:apoffline, B-18
UNIX:aponline, B-19
UNIX:aponlygr, B-20
UNIX:appkgload, B-25
UNIX:appkgtrans, B-28
UNIX:flxfwacv, B-55
UNIX:SMxmldump(1), B-63
Commands(applicable)
UNIX:flxfwac, B-53
Common Intelligent Carrier
Card

cabinet indicators,LEDs,
A-2

customer tools
troubleshooting, 8-5
Customer-Replaceable Units,
9-2

CICC,faceplate, 3-37, A-10

.............................................................

CICC,LEDs, 3-38, A-11

ESC,faceplate, 3-28, A-7
ESC,LEDs, 3-28, A-9

D DC power supplies, 3-22

DCS
circuit voice services, 2-4

GICC,faceplate, 3-35, A-13

processing,data bearer, 2-2
GICC,LEDs, 3-35, A-15
processing,voice, 2-2
power indicators,ECBU
LEDs, A-3, A-3
power indicators,power
status, A-3

support,2G packet data

calls, 2-12
support,circuit data calls,
2-12

cPSB chassis
Degrowing
air filter, 3-23
alarm card, 3-26

B-PCF,interfaces required,
15-136

B-PCF, 3-39

B-PCF,procedures, 15-135

backplane, 3-20

B-PCF,shutdown gracefully,
15-136

faceplate, 3-37, A-10

CICC card, 3-37

functions, 3-37

components, 3-21

LEDs, 3-38, A-11

configuration, 3-21

ports, 3-38

cooling, 3-20

processors, 3-37

Ethernet Switch Card, 3-27

replace, 9-18

fan trays, 3-24

Community Address, 12-2

power, 3-20

Controls and Indicators

Power Supply Units, 3-22

alarm card, A-4

power trays, 3-22

alarm card,controls, A-5

standard components, 3-30

alarm card,faceplate, A-4

redundant data, 7-38

Crossover LAN

B-PCF:deprovision RNC
database, 15-142
B-PCF:halt hard disk,
15-140
B-PCF:interfaces required,
15-140, 15-142
B-PCF:physically remove,
15-147
CICC,depopulation rules,
15-99
CICC,procedures, 15-127
CICC,remove, 15-131

alarm card,hot swap switch,

A-6, A-19

connectivity monitoring,
7-38

CICC,shutdown, 15-128

alarm card,LEDs, 3-26, A-4

default behavior, 7-38

GICC,depopulation rules,
15-99

alarm card:faceplate, 3-26

FIP connections, 7-38

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
IN-3
Issue 14, September 2009
See notice on first page

PRELIMINARY

Index

GICC,interfaces required,
15-102
GICC,procedures, 15-102
GICC,remove card, 15-112
GICC,remove via TPU-GUI,
15-106

Element Management System

EMS GUI, 4-8, 4-8, 4-46,
6-5
EMS-GUI
accessing, 6-5

OA&M interface, 4-2

provisioning mechanism,
2-7
resident OA&M functions,
4-2

GICC,shutdown, 15-103

alarm states,OAM Proxy AP,

4-8

GICC,tools required, 15-102

alarm states,RNC-AP, 4-8

OC3 facilities,order of
degrowth, 15-100

alarm states:OAM Proxy AP,

4-46

.............................................................

PSU gateway,deprovision
via TPU-GUI, 15-120

alarm states:RNC-AP, 4-46

F FAF/QFAF

PSU gateway,procedures,
15-116
PSU gateway,shutdown
5EGW, 15-117
Derowing
B-PCF,factors, 15-135
B-PCF:tools required,
15-147
GICC,factors, 15-102
Dynamic Data

maintenance states,OAM
Proxy AP, 4-8
maintenance states,RNC-AP,
4-8
maintenance states:OAM
Proxy AP, 4-46
maintenance states:RNC-AP,
4-46
Enhanced Circuit Breaker Unit
alarm board, 3-16
power distribution, 3-14

configuration, 2-7

protection, 3-14

update, 15-10, 15-30

replaceable circuit breakers,

3-15

.............................................................
E ECP legacy CLI

commands, 4-2
Technician Interface, 4-2
ecppkt form
applicable screens, 4-39
field,max number, 11-2
field,QFAF limit, 11-2

PRELIMINARY

Mobility Manager,Technician Interface, 4-2

new, 11-2
provisioning, 11-2

Ethernet Switch Card

faceplate, 3-28, A-7

software updates, 4-2

Technician Interface, 4-2

control, 11-12
implementation,initial, 11-12
implementation,post, 11-13
non-packet core, 11-13
failure types
CPU occupancy overload,
8-4
RNC,application processes,
8-4, 8-4
RNC,application software,
8-4
RNC,configuration, 8-4
RNC,hardware, 8-4
RNC:lost connectivity, 8-4
Fan trays

frame level wiring, 3-29

hot-swappable, 3-24, 9-37

GIGE Ethernet Links, 3-27

replace, 9-37

ports, 3-27
Status LEDs, 3-28, A-9
Executive Cellular Processor

fault conditions
alarm card, 8-46
B-PCF, 8-55

commands (TI), 4-2

CICC, 8-53

generic retrofits, 4-2

E-PCF, 8-57

migrated,RC/V, 4-2

EIN LAN, 8-41

migrated,SDP, 4-2

ESC, 8-48

IN-4

Index

GICC, 8-50
LANs 1 and 2, 8-39
LANs 3 or 4, 8-42
OAM Proxy AP, 8-34
RNC-AP, 8-31, 8-37
TPU, 8-44
Field-Replaceable Units, 9-2
Frame Interface Panel
Fiber optic cables, 3-12
front cover, 3-12
power lugs, 3-13
.............................................................
G Gateway Intelligent Carrier

Card
faceplate, 3-35, A-13
functions, 3-34
GIGE ports, 3-35
Host Processor, 3-35
LEDs, 3-36, A-15
replace, 9-7
general hazard statements, 1-5
Generic Retrofit
ECP, 4-2
RNC,process, 11-21
golden image
restoration B-PCF, 11-25
Growing
5EGW,order of growth,
15-30
B-PCF,activation, 15-52
B-PCF,considerations, 15-52
B-PCF,criticality, 15-52
B-PCF,duration, 15-52

B-PCF,dynamic parameters,
15-54

GICC,interfaces required,
15-13

B-PCF,materials required,
15-52

GICC,IP address, 15-10

B-PCF,maximum number,
15-54
B-PCF,PDSN parameters,
15-68
B-PCF,populating slots,
15-53
B-PCF,procedures, 15-75
B-PCF,required information,
15-54
B-PCF,simplex growth,
15-52
B-PCF,slot installation,
15-92

GICC,IP services mode,

15-9, 15-9
GICC,materials required,
15-11
GICC,non-APS mode, 15-9
GICC,order of growth,
15-10
GICC,physically install,
15-14
GICC,procedures, 15-13
GICC,provisioning ATM,
15-10
GICC,switch path:ATM,
15-10

B-PCF,static parameters,
15-54

GICC,tools required, 15-12

B-PCF,tools required, 15-53

GICC:configure via TPU

GUI, 15-16

B-PCF:configure card,
15-76
B-PCF:configure PDSN,
15-83
CICC,activation, 15-46

OC3 facilities,order of
growth, 15-10
OC3 facilities,unused ports,
15-30
population rules,CICC, 15-4

CICC,frame selector
activation, 15-46

population rules,GICC, 15-4

CICC,install in shelf, 15-48

PSU gateway,aterials
required, 15-31

CICC,N+K model, 15-47

CICC,populating slots,
15-47
CICC,procedures, 15-47
GICC,criticality, 15-11
GICC,duration, 15-11
GICC,dynamic data, 15-10
GICC,engineering
considerations, 15-9

PSU gateway,Community
Address, 15-30
PSU gateway,configure ATM
port, 15-34
PSU gateway,criticality,
15-31
PSU gateway,duration,
15-31
PSU gateway,dynamic data,
15-30

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
IN-5
Issue 14, September 2009
See notice on first page

PRELIMINARY

Index

PSU gateway,interfaces
required, 15-32
PSU gateway,procedures,
15-32
PSU gateway,switch
path:ATM, 15-30

installing software, 4-56

MM-AP connection, 4-56
Terminal Server, 4-56
Logs

MM-AP indicator
Status Display Pages, 7-3
Monitoring
Logs,OAM Proxy AP, 7-28

accessing, 7-32, 7-33

Logs,RNC, 7-28

AP admin, 7-28

Logs,RNC- AP, 7-28

.............................................................

message format, 7-31

H Handoff

monitoring, 7-28

OAM Proxy AP,EMS-GUI,

7-4

PSU gateway,unused, 15-30

soft and semi-soft, 2-6

health check

naming conventions, 7-33

old files, 7-33

RNC,determining, 8-15

RNC admin, 7-28, 7-31

RNC,EMS, 8-11

RNC admin log, 7-30

RNC,Status Display Pages,

8-11

RNC DB admin, 7-28, 7-29

RNC,system monitoring,
8-11

rollover scheme, 7-31, 7-34

RNC,TICLI, 8-11
RNC,TPU-CLI, 8-12

RNC global admin, 7-28

storing files, 7-34

types of messages, 7-31
viewing, 7-34

DC power supply, 9-42

fan tray, 9-37
GICC, 9-7

Read Only Printer,RNC-AP,

7-36
Read Only Printer,RNC/
TPU, 7-36
RNC-AP,EMS-GUI, 7-4
RNC-AP,TICLI, 7-10
RNC-AP,TICLII, 7-4
RNC/TPU,TPU CLI, 7-13,
7-22

M maintenance states

RNC/TPU,TPU-GUI, 7-13

B-PCF, 9-23

components, 9-3

Read Only Printer,OAM

Proxy AP, 7-36

.............................................................

Hot-swappable

CICC, 9-18

OAM Proxy AP,TICLI, 7-4,

7-10

AP application, 5-3
AP platform, 5-3
managed objects
EMS GUI, 5-2
OAM Proxy AP, 5-2

Status Display Pages,OAM

Proxy AP, 7-3
Status Display
Pages,RNC-APs, 7-2
Status Display Pages,RNCs,
7-2

.............................................................
I

Input/Output Messages
input messages, 4-28
output messages, 4-28

PRELIMINARY

IP architecture, 2-2, 2-3

.............................................................
L Local Maintenance Terminal

Alarm Card, 4-56

Ethernet Switch Card, 4-56

RNC alarms, 4-41

.............................................................

RNC-AP, 5-2

N Network

TPU, 5-5
MM TICLI
command interface
(text-based), 4-27
Command Line Interface,
4-27

\1X RNC, 2-3

.............................................................
O OAM Proxy AP

400S server, 3-50

410S server, 3-53
acccessing, 6-4

IN-6

Index

AP Admin log, 7-28

applications,RNC Database,
2-22, 3-50
applications,TPU-GUI, 2-22,
3-50
backing up, 6-29, 6-32
configuration, 3-51, 3-54
hardware, 3-52, 3-54
logging in, 6-4
managed objects, 5-2
monitoring,EMS-GUI, 7-4
monitoring,Logs, 7-28
monitoring,MM-AP CLI,
7-10
monitoring,Read Only
Printer, 7-36

Element Management
System, 4-8
EMS GUI, 4-8
Input/Output Messages, 4-28
MM-TICLI, 4-27
Personal Computers, 4-7
RC/V, 4-39, 4-39

Packet data, 2-42, 2-42

call signaling flows, 2-42
mobile reactivations, 2-44
network reactivations, 2-45
Packet Data Network, 2-3
Performance Measurement

Read-Only Printer, 4-44

CDN Service SM)counts,

2-7

RNC alarms, 4-41

RNC PM counts, 2-7

RNC logs, 4-38

Permanent Virtual Circuit, 12-2

SDPs, 4-40, 4-40

Power Distribution Shelf, 3-14

service measurements, 4-43

Power Indicators

system console, 4-7

ECBU LEDs, A-3

terminal choices, 4-6

power status, A-3

text terminals, 4-7

Provisioning

monitoring,SDP, 7-3

TPU GUI, 4-11

3G packet data,cellg, 11-8

primary purpose, 3-50

UNIX command interface,

4-37

3G packet data,ecp3g, 11-8

replace components, 9-5

restoring, 6-29, 6-34
Status Display Pages,AP
indicator, 7-3
OMC-RAN TICLI
Command Line Interface,
4-27
Operations and Management
Platform
5ESS connection,terminal
sessions, 4-6
5ESS legacy interface, 4-5
administrative and
maintenance, 4-4
Command Line Interface,
4-27, 4-27
ECP connection,terminal
sessions, 4-5
ECP legacy interface, 4-5

X-terminals, 4-7

3G packet data,sub, 11-8,

11-8

.............................................................

ATM switch, 15-10, 15-30

P Packet Control Function

forms, 11-2

B-PCF,communication, 2-37
B-PCF,control path, 2-38

initial implementation,apeqp, 11-6

B-PCF,data path, 2-38

initial implementation,cell2,
11-4

B-PCF,ethernet interface,
2-38, 2-39

initial implementation,ecppkt, 11-2

B-PCF,integration, 2-37
B-PCF,interface, 2-37

post implementation,apeqp,
11-8

B-PCF,packet data offload,

2-4

post implementation,cell2,
11-8

B-PCF,software, 2-37

post implementation,ecppkt,
11-8

B-PCF,TPU shelf, 2-37,

A-17
B-PCFsecurity, 2-40

post implementation,FAF/
QFAF control, 11-8
Recent Change and Verify,
11-2

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
IN-7
Issue 14, September 2009
See notice on first page

PRELIMINARY

Index

duration,circuit breaker,
9-56

RNC cabinet components,

9-52

duration,DC power supply,

9-42

SC-GICC, 9-7

alarms, 7-36
ECP, 7-36

duration,fan tray, 9-37

filtering, 7-36

duration,non-SC-GICC, 9-7

.............................................................
R Read Only Printer

formatting, 7-36

duration,SC-GICC, 9-7

MM-AP, 7-36

fan tray, 9-37

OAM Proxy AP,monitoring,

7-36

frequency,B-PCF, 9-23
non-SC-GICC, 9-7

output, 7-36
RNC ID, 7-36
RNC-AP,monitoring, 7-36
RNC/TPU,monitoring, 7-36
routing, 7-36
Recent Change and Verify
accessing, 6-25
database, 4-39

required information,B-PCF,
9-24
required materials,air filter,
9-48
required materials,CICC,
9-18

restoration B-PCF
golden image, 11-25
Restoring
OAM Proxy AP, 6-29, 6-34
RNC-AP, 6-29, 6-34
RNC
admin log, 7-30
alarm cards, 2-22
alarm levels, 4-41
alarm list (GUI), 4-42
alternate routing, 2-14
B-PCF, 2-23
CICC, 2-23

operations, 4-39

required materials,circuit
breaker, 9-56

provisioning,apeqp form,
11-6

required materials,DC power

supply, 9-43

Ethernet Switch Cards, 2-22

provisioning,cell2 form,
11-4

required materials,fan tray,

9-37

GICC, 2-23

provisioning,ecppkt form,
11-2

required materials,non-SCGICC, 9-8

screens, 4-39

required materials,SC-GICC,
9-8

interconnection, 2-13

required tools,air filter, 9-48

monitoring,logs, 7-28

required tools,CICC, 9-18

monitoring,Read Only
Printer, 7-36

storage format, 4-39

Replace
air filter, 9-47
B-PCF, 9-23
CICC, 9-18

PRELIMINARY

performing loopback
verification, 9-59

TPU shelf components, 9-6

required tools,circuit
breaker, 9-56

DCS interface, 2-13

Generic Retrofit, 11-21

hardware, 2-20
input/output messages, 4-28

log files, 4-38, 7-30

monitoring,TPU CLI, 7-13

circuit breaker, 9-56

required tools,DC power

supply, 9-42

DC power supply, 9-40

required tools,fan tray, 9-37

duration,air filter, 9-47

required tools,non-SCGICC, 9-7

Read Only Printer, 7-36

required tools,SC-GICC, 9-7

Status Display Pages, 4-40

duration,B-PCF, 9-23
duration,CICC, 9-18

monitoring,TPU GUI, 7-13

multiple, 2-13
RC/V screens, 4-39

IN-8

Index

Summary Status Indicator,

RNC, 7-2

RNC-M main functions,

3-44, 3-47

TPU shelf, 2-22

TCS main functions, 3-47,

3-53

UNIX commands, 4-37

RNC alarms
managed objects, 4-41
RNC database
backing up, 6-36
restoring, 6-36
RNC-AP
400S server, 3-43

VCVM, 3-43, 3-47

SMxmldump tool, C-4

configure files, C-4
converting XML SM files,
C-2
file names, C-2

.............................................................

help, C-2

S Safety and general information,

manual page, C-2

1-3, 1-5
Security
MM-APC management, 16-5
OMP guidelines, 16-3
Service Measurement

410S server, 3-47

RNC-AP,FMSsm.tune, C-4
storage, C-2
time zone settings,OMP, C-4
SMxmldump Tool
time zone,conventions, C-3

basics, 10-2
accessing, 6-4

SMxmldump tool
counts,base station, 10-3

AP Admin log, 7-28

applications,RNC-Manager,
2-22, 3-47

time zone,OMP, C-4

counts,CDN, 10-3
cycle,24-hour, 10-3

time zone,RNC-AP, C-4

applications,Traffic Control
Server, 2-22, 3-43, 3-47

files,deletion, 10-7

time zone,synchronization,
C-4

files,retrieval, 10-7

usage, C-2

backing up, 6-28, 6-32

files,viewing, 10-6

configuration, 3-44, 3-47

hardware, 3-45, 3-48

managing,RNC PM data,
10-8, C-8

logging in, 6-4

polling, 10-6

managed objects, 5-2

raw data,obtaining, 10-3

monitoring,EMS-GUI, 7-4

raw data,viewing, 10-6

monitoring,Logs, 7-28

storage, 10-4

monitoring,MM-AP CLI,
7-10

tool,SMsmdump, 10-3

monitoring,Read Only
Printer, 7-36

tunable,directory,default,
C-8

monitoring,SDP,RNC-AP,
7-2

tunable,directory,override,
C-8

population guidelines, 3-45,

3-49

tunable,file, C-8

replace components, 9-5

restoring, 6-28, 6-34

Software
call processing, 2-29
Software update

tool,XML file retrieval, 10-7

tunable,variable, C-8
XML format, 10-6

ECP, 4-2
Software Update Automation
SU procedures, 11-20
tool, 11-20
States
administrative state,locked,
5-8
administrative state,shutting
down, 5-8
administrative
state,unknown, 5-8
administrative
state,unlocked, 5-8
EMS-GUI, 5-2
maintenance state,active, 5-9

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
IN-9
Issue 14, September 2009
See notice on first page

PRELIMINARY

Index

maintenance state,offline,
5-9
maintenance state,stale, 5-9
maintenance state,standby,
5-9
maintenance state,unknown,
5-9
operational state,disabled,
5-6
operational state,enabled,
5-6
operational state,unknown,
5-6
SC-GICC,active state, 5-10
SC-GICC,stale state, 5-10
SC-GICC,standby state,
5-10
state attributes, 5-8
status attribute, 5-8
TPU managed object, 5-5,
5-8

OAM Proxy AP, 7-3

overload conditions, 4-40

alarm viewing, 4-11

RNC status indicator, 4-40,

7-2

configuration management,
4-11

RNC-APs, 7-2

direct access, 6-14

types of information, 4-40

fault management, 4-11

structure of hazard statements,

1-3
Subnets, 12-2
Summary Status Indicator, 7-2
RNC-AP, 7-2

GICC, 3-30

Mobility Manager, 4-2

maximum configuration,
3-31

Terminal Server

usage state,unknown, 5-7

Local Maintenance
Terminal, 4-56

MM-AP indicator, 7-3, 7-3

components, 3-30

ECP legacy CLI, 4-2

flash card, 3-17

menus, 4-40

CICC, 3-30

fan trays, 3-30

usage state,idle, 5-6

graphical interface, 4-40

Blade-PCF, 3-30

T Technician Interface

Ethernet port, 3-17

equipage, 4-40

alarm cards, 3-30

Ethernet Switch Cards, 3-30

usage state,busy, 5-7

ECP, 4-40

TPU shelf

.............................................................

DC power input, 3-17

alarm levels, 4-40

TPU GUI

RNC applicable, 4-40

usage state,active, 5-7

accessing, 6-27

accessing, 6-17

accessing, 6-7

Console Port, 3-18

access to, 4-40

TPU CLI

real time status, 4-40

TPU state model, 5-5

Status Display Pages

PRELIMINARY

monitoring, 7-2

Local Management Port,

3-18
ports, 3-17, 3-18
software load, 3-19
TICLI

minimum configuration,
3-30
population rules, 3-32
power trays, 3-30
Shelf Controller function,
3-30
Traffic
data bearer, 2-3
voice bearer, 2-3
trouble indicators
AP, 8-8

accessing, 6-18

cabinet, 8-8

direct login, 6-23

TPU, 8-8

TPU
managed objects, 5-5

troubleshooting
customer tools, 8-5

MM-SP, 4-40
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
See notice on first page
Issue 14, September 2009

IN-10

Index

types of information
Status Display Pages, 4-40
.............................................................
U UNIX

command interface, 4-37

.............................................................
V Virtual Channel Connection,

12-2
Virtual Path Connection, 12-2
Virtual Path Identifier, 12-2,
12-3
.............................................................
X X-terminal

users, 6-25, 6-27

...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
401-710-082
IN-11
Issue 14, September 2009
See notice on first page

PRELIMINARY

Casa System C3200 CMTS Manual
50% (4)
Casa System C3200 CMTS Manual
678 pages
Document Composition - Onbase 18 Module Reference Guide PDF
No ratings yet
Document Composition - Onbase 18 Module Reference Guide PDF
350 pages
Turn-Up and Commissioning Guide - 8DG25697KAAA - V1 - Alcatel-Lucent 1850 Transport Service Switch (TSS-100) Release 3.0 PDF
No ratings yet
Turn-Up and Commissioning Guide - 8DG25697KAAA - V1 - Alcatel-Lucent 1850 Transport Service Switch (TSS-100) Release 3.0 PDF
120 pages
450222
No ratings yet
450222
826 pages
CMD and Port Number
No ratings yet
CMD and Port Number
15 pages
Alcatel-Lucent Long Term Evolution (LTE) Radio Access Network (RAN)
No ratings yet
Alcatel-Lucent Long Term Evolution (LTE) Radio Access Network (RAN)
56 pages
FTHistorian SE Installation and Configuration Guide
No ratings yet
FTHistorian SE Installation and Configuration Guide
68 pages
Alu Os R6 - R7 Part2
No ratings yet
Alu Os R6 - R7 Part2
570 pages
OXO R9.1 Installation Manual
0% (1)
OXO R9.1 Installation Manual
238 pages
Proxy Bypass
No ratings yet
Proxy Bypass
17 pages
Basic Call FD
No ratings yet
Basic Call FD
447 pages
Alcatel 1000 MM E10 Next Generation Switch
100% (1)
Alcatel 1000 MM E10 Next Generation Switch
14 pages
Omnipcx Office Rce Small
No ratings yet
Omnipcx Office Rce Small
238 pages
OpenQuake Manual (Latest) PDF
No ratings yet
OpenQuake Manual (Latest) PDF
193 pages
Es-16 r2.6 CT Operator HB
No ratings yet
Es-16 r2.6 CT Operator HB
594 pages
Nokia RNC Functionality
No ratings yet
Nokia RNC Functionality
100 pages
Desmond Manual
No ratings yet
Desmond Manual
172 pages
Alcatel-Lucent 1850 TSS 5C R6 1 Datasheet Rev.2014
No ratings yet
Alcatel-Lucent 1850 TSS 5C R6 1 Datasheet Rev.2014
3 pages
MPR Configuration File Management PDF
No ratings yet
MPR Configuration File Management PDF
190 pages
NN20500276 - V1 - Alcatel-Lucent 9100 Multi-Standard Base Station Indoor - Technical Description
No ratings yet
NN20500276 - V1 - Alcatel-Lucent 9100 Multi-Standard Base Station Indoor - Technical Description
104 pages
Manual R 8
No ratings yet
Manual R 8
208 pages
Ezcad2Uni User'S Manual
No ratings yet
Ezcad2Uni User'S Manual
139 pages
01 - Nokia RNC Architecture
No ratings yet
01 - Nokia RNC Architecture
34 pages
Alfoplus: Access Link Full Outdoor With Adaptative Code Modulation Full Ip Radio - Point To Point Radio Link
No ratings yet
Alfoplus: Access Link Full Outdoor With Adaptative Code Modulation Full Ip Radio - Point To Point Radio Link
76 pages
Practice Test: Symantec 250-311
No ratings yet
Practice Test: Symantec 250-311
42 pages
ReleaseNote1662SMC27B9 Ed1
No ratings yet
ReleaseNote1662SMC27B9 Ed1
67 pages
1427762685OXO 9.0 Installation Manual
No ratings yet
1427762685OXO 9.0 Installation Manual
230 pages
ReleaseNote1662SMC27B7 Ed1
No ratings yet
ReleaseNote1662SMC27B7 Ed1
66 pages
ReleaseNote1662SMC27B6 Ed1
No ratings yet
ReleaseNote1662SMC27B6 Ed1
64 pages
ReleaseNote1662SMC27B8 Ed1
No ratings yet
ReleaseNote1662SMC27B8 Ed1
67 pages
1662SMC RN 23B6
No ratings yet
1662SMC RN 23B6
59 pages
ulsSysSpecRel2 1 2Ed01It01
No ratings yet
ulsSysSpecRel2 1 2Ed01It01
202 pages
01 Nokia RNC Architecture
50% (2)
01 Nokia RNC Architecture
34 pages
PYTHON PROGRAMMING FOR BEGINNERS A CRASH COURSE WITH HANDS-ON PROJECTS TO LEARN PYTHON CODING, GAME PROGRAMMING WITH NO CODING... (Mike Kernell)
100% (1)
PYTHON PROGRAMMING FOR BEGINNERS A CRASH COURSE WITH HANDS-ON PROJECTS TO LEARN PYTHON CODING, GAME PROGRAMMING WITH NO CODING... (Mike Kernell)
242 pages
Vendor Presentation-3 (Hardware Product Portfolio) - 0801
100% (1)
Vendor Presentation-3 (Hardware Product Portfolio) - 0801
61 pages
D2s 1.LAG PDF
No ratings yet
D2s 1.LAG PDF
30 pages
Guide To Free Forensic Audit Tools
No ratings yet
Guide To Free Forensic Audit Tools
23 pages
Isa-Es16 2.5 Oper - HDBK - Ed05
100% (1)
Isa-Es16 2.5 Oper - HDBK - Ed05
560 pages
Iu Teg Ua6 External Ed07.02 090611 STD
100% (1)
Iu Teg Ua6 External Ed07.02 090611 STD
162 pages
3MN005070001DEZZA - V1 - 9370 Radio Network Controller - Technical Description
No ratings yet
3MN005070001DEZZA - V1 - 9370 Radio Network Controller - Technical Description
174 pages
Alcatel RRH60 PDF
No ratings yet
Alcatel RRH60 PDF
47 pages
App Management
No ratings yet
App Management
204 pages
OmniPCXOffice - R6 - Installation Manual
No ratings yet
OmniPCXOffice - R6 - Installation Manual
188 pages
BBTRX 22 2515515
No ratings yet
BBTRX 22 2515515
141 pages
5 - Predict Housing Prices With Tensorflow and AI Platform
No ratings yet
5 - Predict Housing Prices With Tensorflow and AI Platform
11 pages
Recipe Manager Console Using Python
No ratings yet
Recipe Manager Console Using Python
3 pages
NN-20500-021 Alcatel-Lucent 9370 Radio Network Controller - Technical Description 9.04 Standard September 2011
No ratings yet
NN-20500-021 Alcatel-Lucent 9370 Radio Network Controller - Technical Description 9.04 Standard September 2011
152 pages
Getting Started With SAP HANA 2.0, Express Edition (Virtual Machine Method)
No ratings yet
Getting Started With SAP HANA 2.0, Express Edition (Virtual Machine Method)
24 pages
02 02 RN23822EN40GLA1 mcBSCcommissioning
No ratings yet
02 02 RN23822EN40GLA1 mcBSCcommissioning
69 pages
Linux Tsmcli User Guide 201803
No ratings yet
Linux Tsmcli User Guide 201803
40 pages
WMS Engineering Guide OAM06
No ratings yet
WMS Engineering Guide OAM06
157 pages
1660SM Release Notes PDF
100% (2)
1660SM Release Notes PDF
56 pages
AcronisCyberProtect 15 Best Practices en-US
No ratings yet
AcronisCyberProtect 15 Best Practices en-US
100 pages
MS3600plus r9
No ratings yet
MS3600plus r9
2 pages
9370 Maint Manual
No ratings yet
9370 Maint Manual
72 pages
RTN 900 Brochure (910&950) V2.0
No ratings yet
RTN 900 Brochure (910&950) V2.0
4 pages
RRH 2 X 40W - 900 MHZ NN-20500-281 - 02.05 PDF
No ratings yet
RRH 2 X 40W - 900 MHZ NN-20500-281 - 02.05 PDF
52 pages
01 Nokia RNC Architecture
No ratings yet
01 Nokia RNC Architecture
34 pages
Nokia Flexi Node B Commissioning Quick Reference V3
100% (3)
Nokia Flexi Node B Commissioning Quick Reference V3
8 pages
Autosys Job
No ratings yet
Autosys Job
26 pages
Huawei rtn910
No ratings yet
Huawei rtn910
3 pages
Microsoft Windows 3.0 Manual
No ratings yet
Microsoft Windows 3.0 Manual
676 pages
30-3006 (Alcatel-Lucent 9370 RNC UA08.1 Integration) 01.01 Draft July 2011
No ratings yet
30-3006 (Alcatel-Lucent 9370 RNC UA08.1 Integration) 01.01 Draft July 2011
96 pages
Software Release Notes: PN 3DB23102AEAA, Rev.05 - September 2008
No ratings yet
Software Release Notes: PN 3DB23102AEAA, Rev.05 - September 2008
20 pages
Java Code
No ratings yet
Java Code
29 pages
Dedicated Server Setup Guide
No ratings yet
Dedicated Server Setup Guide
23 pages
IM 24 3005 301 Alcatel Lucent 9370 RNC UA08 X Commissioning Method 3 01 Standard October 2012 PDF
No ratings yet
IM 24 3005 301 Alcatel Lucent 9370 RNC UA08 X Commissioning Method 3 01 Standard October 2012 PDF
108 pages
UMTS RNC Product Description v1 07 July 2010
No ratings yet
UMTS RNC Product Description v1 07 July 2010
84 pages
UA06 9370 Product Specification INTERNAL May08
No ratings yet
UA06 9370 Product Specification INTERNAL May08
160 pages
Payload
No ratings yet
Payload
27 pages
Nanokeyer Building Instructions PCB Rev d1 PDF
No ratings yet
Nanokeyer Building Instructions PCB Rev d1 PDF
35 pages
Android Applications Using Python and SL4A, Part 1:: Set Up Your Development Environment
No ratings yet
Android Applications Using Python and SL4A, Part 1:: Set Up Your Development Environment
12 pages
Micromite Manual
No ratings yet
Micromite Manual
95 pages
Exercise 10 Using IO
No ratings yet
Exercise 10 Using IO
8 pages
Mega AI Agent Architecture and Workflow
No ratings yet
Mega AI Agent Architecture and Workflow
8 pages
Real Dumps For Huawei H19-102 - V2.0-EnU Exam
No ratings yet
Real Dumps For Huawei H19-102 - V2.0-EnU Exam
5 pages
Unit 2
No ratings yet
Unit 2
37 pages
3 - Axway AMPLIFY - Amplify API Management - Demo
No ratings yet
3 - Axway AMPLIFY - Amplify API Management - Demo
50 pages