Omcr100&110a PDF

1X Cellular Database
Administration
Student Guide
OMCR100A
General Release G16.4
English
Revision History
Course Number OMCR100A
Document Title 1X Cellular Database Administration
Version Information The following table lists the document revision number, date and
remarks concerning the version.
Revision Date of
Remarks
Number Issue
1.0 07/01 Initial Release

1.1 10/01 Revised Release
1.2 11/01 Updated Release
2.2 11/03 Update Release 16.4
OMCR100A 1X Cellular Database Administration Revision 2.2 - 11/03

ii Student Guide
Copyright/Trademarks and Motorola are trademarks of Motorola, Inc.
Product and service names profiled herein are trademarks of Motorola,

Inc. Other manufactures’ products or services profiled herein may be
referred to by trademarks of their respective companies.
The following copyright/trademarks are acknowledged in this course:
• SPARC is a trademark of Sun Microsystems
• SUN is a trademark of Sun Microsystems
Disclaimer Motorola, Inc. Global Telecom Solutions Sector makes no warranties

either expressed or implied with regard to the information presented in
the course or in this training manual. The information presented in the
course and in this training manual is for educational purposes only, and
the appropriate field manual or appropriate Motorola representative
should be consulted for issues relating to the actual operation and
maintenance of the products described in the course or this training
manual.
Revision 2.2 - 11/03 1X Cellular Database Administration OMCR100A

Student Guide iii
Acknowledgements The Technical Information Products and Services would like to thank
the following individuals for their support in the development of this
course:
• David Heitz
• Paulo Kacelnik
• Jim Teehan
• Tony Wathen
• Mike Jones
• Brian Lehman
• Richa Tiwari
• Stephen Ehrlich
• Frank Edgeton
• William Liebman
• Lauren St. Andre
• David Lin

iv Student Guide
General Introductions
Introductions The following introductions will serve to introduce the instructor,

students, and the course.
• Instructor introduction
- Instructor name
- Instructor background and credentials
• Student introductions
- Student name
- Student background and credentials
• Course terminal objective
• Intended audience
• Course hours
Important Information This information is provided to familiarize you with the facility and to
identify some useful additional information.
• Identification badges are required at all times
- Badges must be turned in every day after class
• Message numbers
- Contact: _______________________
- Telephone Number: __________________

Student Guide v
Facility
- Cafeteria
- Locations of phones, vending area, and rest rooms
- Information monitor (if provided)
- Smoking area (if provided)
- Local area maps (if provided)

vi Student Guide
Course Introduction
Audience This course is created for the following individuals:
• Technical support personnel responsible for performing basic

administration at the CBSC, OMC-R and OMC-IP. Personnel
include CDMA System Operators, Cellular Network
Administrators and System Administrators.
Course Description This course has been designed to help technical personnel create a 1X
Cellular Network in the database.
Course Objective Upon completion of the course you will be able to:
• Perform cellular database administration procedures for 1X

devices.
Course Length Three days
Prerequisites The following training courses or knowledge is recommended:
• GNL130 1X Overview/Migration
or
GNL131 1X Overview/Migration (E-Learning)
• GNL060 Basic CDMA Concepts
• GNL070 SC™ Product Family Overview (CDMA)
• NETG13630 Unix User Fundamentals
• NETG13631 Unix Advanced Topics for Users
• NETG13634 Sun Solaris Basic Administration
• NETG16635 Sun Solaris Network Administration
• Working knowledge of/or experience with Code Division

Multiple Access (CDMA) or cellular system technologies

Student Guide vii
Course Equipment The following equipment is needed to complete this course:
• CDMA2000 1X Operations and Maintenance Center-Radio

(OMC-R)
• CDMA2000 1X Central Base Station Controller (CBSC)
• CDMA2000 1X Access Network (AN)
• CDMA2000 1X Packet Data Service Node (PDSN)
• CDMA2000 1X Mobile Wireless Center (MWC)
• CDMA2000 1X SC™ 4812T and/or SC™ 4812ET Base

Transceiver Station(s)
• Terminals accessing CDMA2000 1X Network
Course Material The following material is needed to complete this course:
• 1X Cellular Database Administration Student Guide
• CDMA Online Documentation CD-ROM Release 2.16.3.X -

System Command Reference

Cellular System Administration

viii Student Guide
Course Agenda Subject Day
Management Information Base (MIB) ...............................1
Access Network (AN).........................................................1
Centralized Base Station Controller (CBSC)......................2
Transcoder (XC) .................................................................2
Base Transceiver Station (BTS)..........................................3
MSC Span and Terrestrial Circuit (TERCKT)....................3

Student Guide ix
Safety
Safety issues must be addressed before going into the lab. Issues to be
covered include, but are not limited to:
• Identification of potential safety hazards
• Identification of the location of any lab power disconnect push-

buttons (if installed)
• Explanation of the Electro-Static Discharge (ESD) precautions
• Demonstrate placing the lab equipment in the proper standby

mode following lab completion
Live Circuits Only factory authorized service personnel or other qualified

maintenance personnel will:
• Remove equipment covers for internal subassembly or any

internal adjustments.
• Disconnect power and discharge circuits because dangerous

voltages exist even with power cable(s) removed.

x Student Guide
Service and Anytime any work is to be accomplished inside the frame, two people
Adjustment should be present.
• Another person required for:
- Internal service
- Adjustment
• Person should be capable of:
- First Aid
- Resuscitation
Substitute Parts/ In order to minimize the danger of introducing any additional hazards:
Modify Equipment
• Do not install substitute parts
• Do not perform any unauthorized modification of equipment

Student Guide xi
Dangerous Procedure Read the text conventions in the manuals. They will represent four
Warnings levels of information as follows:
• NOTE (Written as text)

“Presents additional helpful, non-critical information that you
can use.”
• IMPORTANT (Black box with an asterisk inside a triangle)

“Presents information to help you avoid an undesirable
situation or provide additional information to help you
understand a topic or concept.”
• CAUTION (Black box with a exclamation point inside a

triangle)
“Presents information to identify a situation where equipment
damage could occur and help you avoid damaging your
equipment.”
• WARNING (Black box with a lighting bolt inside a triangle)

“Presents information to warn of a potentially hazardous
situation where there is possibility of personal injury.”

xii Student Guide
Table Of Contents
General Introductions ...................................................................................................... vi

Course Introduction ......................................................................................................... viii
Safety ............................................................................................................................... xi
Management Information Base (MIB)
MIB .................................................................................................................................. 1-3

Review Exercise .............................................................................................................. 1-14
Lab Overview - MIB Management.................................................................................. 1-15
Lab Exercise 1 - Back up the MIB to a Directory ........................................................... 1-16
Lab Exercise 2 - Back up the MIB to a DAT Tape .......................................................... 1-17
Lab Exercise 3 - Drop the MIB........................................................................................ 1-18
Lab Exercise 4 - Import the MIB..................................................................................... 1-20
Lab Exercise 5 - Generate the Data Files......................................................................... 1-21
Lab Exercise 6 - Install and Validate the CDF Files........................................................ 1-23
Lab Exercise 7 - Initialize the MM and Activate the XC ................................................ 1-24
Access Network (AN)
Access Network ............................................................................................................... 2 - 4

Lab Exercise - Provision the AN ..................................................................................... 2 - 11
Centralized Base Station Controller (CBSC)
CBSC Setup ..................................................................................................................... 3 - 3

CBSC Setup Procedure .................................................................................................... 3 - 4
Add the Target CBSC ...................................................................................................... 3 - 6
Add the Inter-CBSC Packet Link .................................................................................... 3 - 7
Add the 1X Packet Data Services .................................................................................... 3 - 8
Edit the CBSC Backhaul Parameter ................................................................................ 3 - 10
Review Exercise .............................................................................................................. 3 - 11
Lab Exercise - Provision the CBSC................................................................................. 3 - 12
Transcoder (XC)
Lab Exercise - Provision the XC ..................................................................................... 4 - 6
Base Transceiver Station (BTS)
1X Cards .......................................................................................................................... 5 - 3
Lab Exercise - Provision the BTS.................................................................................... 5 - 6
xiii 1X Cellular Database Administration Revision 2.2 - 11/03

OMCR100A Student Guide
Table Of Contents
MSC Span and Terrestrial Circuits (TERCKT)
MSC Span and Terrestrial Circuit.................................................................................... 6- 4

Circuit Identity Code ....................................................................................................... 6- 6
Review Exercise .............................................................................................................. 6- 8
Lab Exercise 1 - Provision the MSC Span and Terrestrial Circuits................................. 6- 9
Lab Exercise 2 - Cleanup the Database ........................................................................... 6- 11
Revision 2.2 - 11/03 1X Cellular Database Administration xiv

Student Guide OMCR100A
Module 1

This module will describe the SC MIB and backup procedures to back up.
Objectives What you must do:
• Perform procedures to export a MIB to a directory.
• Perform procedures to back up a MIB to a DAT tape.
• Perform procedures to drop a MIB.
• Perform procedures to import a MIB.
• Perform procedures to generate data files for the network

elements.
• Perform procedures to install and validate the CDF/CFG files.
• Perform procedures to initialize the MM and activate the XC.
How well you must do it:
• In compliance with the 1X Cellular Database Administration

Student Guide and instructor directions.
Materials required • OMCR100A 1X Cellular Database Administration Student

Guide


Student Guide 1-1
Acronyms The following acronyms are used in this lesson:
Acronym Definition
AGNODE Aggregation Node
AN Access Network or Node
API Application Program Interface
BTS Base Transceiver Station
CDF Configuration Data File
CFG Configuration File
CLI Command Line Interface

CM Configuration Management
EDGERTR Edge Router
LWRTR Local WAN Router

IWU Inter-Working Unit
MIB Managed Information Base
MM Mobility Manager
MLS Multi-Layer Switch
NE Network Element
OMC-IP Operations and Maintenance Center - Internet

Protocol
OMC-R Operations and Maintenance Center - Radio
SDU Selection Distribution Unit
VPU Vocoder Processing Unit
XC Transcoder

Student Guide 1-2
MIB
MIB
OMCR MIB The OMC-R functions primarily as a database server containing all of
the system configuration data. This configuration data is stored in what
is referred to as the Managed Information Base (MIB). This MIB is run
using INFORMIX database software on the OMC-R platform.
With the introduction of the packet CBSC in R16, additional changes

have been made to the database. The access network (AN), which is
managed by the OMC-IP, requires datafiles from the OMC-R. The
configuration files for the OMC, CBSC, AN, SDU, VPU, BTSs and
XC, as well as the bootp file required by the XC are generated from the
MIB. The MIB may operate in dynamic or MIB-only mode.
Dynamic Mode In dynamic mode, recent change commands will modify the
configuration database in the Mobility Manager (MM) and MIB. If
command changes are not successfully made to the MM configuration
database, they are not made to the MIB. In this way, both the MM
configuration database and the OMC MIB are in sync at all times. Only
the MM configuration database and the CDF files on the MM are
modified as a result of the recent change commands. The CDF files on
the OMC are not modified using these commands. To obtain CDFs on
the OMC containing the most current information, new CDFs must be
generated from the MIB.
MIB-Only Mode It is possible to get the MM and OMC-R databases out of sync. In these
instances, it is sometimes possible to correct the discrepancies by
placing the OMC-R in MIB-only mode. This requires modifying the /
screl/active/data/scsiim_cdf.omc file and restarting the OMC API
processes.

Student Guide 1-3
MIB
Creation of MIB The following items provide input into the creation of the MIB:
• All provisioning and recent change requests go through the

MIB. If the MIB is unavailable, provisioning will not occur and
recent change commands will be disallowed. An unsuccessful
update indication will be returned to specify that the
transactions have not been accomplished.
• It is possible to provision a system or subsystem without the

physical equipment being present on a live system. This is
accomplished by providing updates offline and loading CM
commands offline.
• It is possible to determine the “mib-only” mode of the system,

which specifies that updates will only be applied within the
MIB.
• The maximum number of concurrent users supported by the

MIB is scalable per site and per release to allow for future
growth. As the customer's network grows, the number of
concurrent users supported by the MIB will also be able to
grow.
• A fatal error in the software will not prevent access to the MIB.
• The MIB will support two phase commit (e.g. specifying a

change and then committing the change later in the load
update).
• In the future, the MIB will be able to support access to data

residing somewhere other than in the Informix database (e.g.
IWU, CBSC or XC). This will be transparent to the end-user.
• A lock-out feature prevents the MIB from processing new

messages coming into the API. This will be useful in release
upgrades, database backup, and configuration management by
various users. This feature prevents partial updates of database,
by locking out new updates until the current update is
completed. Information can still be obtained for display
purposes during the lock-out procedure.
CDF Generation The CDFGEN command is no longer valid in R16. In its place, the
generate CLI commands are used. GENERATE DATAFILES
commands have been introduced to produce CDF/CFG files for the
OMC-R, MM, XC, AN, SDU, VPU and BTS.

Student Guide 1-4
MIB
Generating Datafiles All GENERATE DATAFILES commands with the exception of the
AN, SDU and VPU have two optional parameters:
• LOAD - Specifies the release for which the cdf file will be
updated. Five possible settings are available. The OMCLOAD
setting is only used by the MM.
- ACTIVE - Updates the cdf files for Network Element (NE).
- NEXT - Updates the CDF files for the software release

specified by the target CBSC’s NextLoad. If the NextLoad
has to have been set for the target NE to use the Next
setting.
- NEW - When specified with a VERSION is used to specify

any installed software release that contains software for the
target NE.
- ALL - Builds the data download files for the valid releases
pointed by ACTIVE, NEXT and NEW. This is the default
setting for the Generate OMC-R, XC and BTS Datafiles
commands.
- OMCLOAD - Builds the data download files for the

OMCR’s active load. This is the default setting for the
Generate MM Datafiles command.
• VERSION - Is only valid if the LOAD specified is NEW.
- The version specified must be a software release installed

on the OMCR where the command is being executed, and
must contain software for the target NE.
The GENERATE AN-an# DATAFILES command (for MLS datafiles

only) has one optional parameter.
• ALLFILES - Specifies whether the configuration files should

be produced for all the devices or only for those that were
modified since the last generate.
- Yes - Indicates all the configuration files will be generated.
- No - Indicates configuration files will only be generated for

the devices that changed since the last generate.

Student Guide 1-5
MIB
Generate OMCR The GENERATE OMCR-omcr# DATAFILES command generates

Datafiles the CDF files. This command generates the omc.cdf which features the
cbsc.cdf files for all CBSCs under the OMC-R. Also, the command
generates bts.cdf files for all BTSs under all the CBSCs subtending the
OMC-R. This command is executed recursively for every CBSC under
the OMC-R.
Generate MM The GENERATE MM-mm# DATAFILES command generates the

Datafiles CDF files in either the recursive or non-recursive mode. In the
recursive mode the CDF files are generated for the CBSC’s parent
OMC-R, target CBSC and all BTSs under the target CBSC. When used
in the non-recursive mode, a CDF file is generated for the target CBSC.
The RECURSIVE parameter can be used to generate the CDF files for
the parent OMC-R of the target CBSC, the target CBSC and underlying
BTSs.
• YES - generates the CDF files for the parent OMC-R of the
target CBSC, target CBSC and the underlying BTSs.
• NO - generates only the CDF files for the target CBSC.
Generate AN Datafiles The GENERATE AN-an# DATAFILES command generates the CDF
files for the MLS devices under the target AN. These files are copied,
via TFTP, to the devices at a later time by the operator using a manual
procedure. This command should only be run on a field OMC-R and
should not be run while producing an off-line MIB. This command can
be run by the operator when the EMSync value of the target AN is
GenReq. Display the EMSync value by using the DISPLAY AN-an#
ANCONF command.
Generate XC Datafiles The GENERATE XC-xc# DATAFILES command generates the CDF
files for the XC cages, functions, general, MSCSPANs, BTSSPANs and
spans.
Generate BTS The GENERATE BTS-bts# DATAFILES command generates the

Datafiles CDF file for the target BTS.
Generate SDU The GENERATE SDU-sdu# DATAFILES command generates the

Datafiles CDF file for the target SDU.

Student Guide 1-6
MIB
Generate VPU The GENERATE VPU-vpu# DATAFILES command generates the

Datafiles CDF file for the target VPU.
sc_install_cfg mm-x Once the OMC, CBSC and BTS CDF files have been generated, they
must be transferred to the MM. This is accomplished using the
sc_install_cfg utility. This utility is located in the /screl/active/bin
directory. It installs configuration files from the OMC to the specified
MM.
sc_validate_cdf After the CDF files have been transferred to the appropriate MM, the
files must be made available to the MM for mmap file construction.
This file is generated from the CDF files and is machine readable. The
file is updated by the MM during normal operation, and corresponding
deltas are added to the CDF files. If the mmap file becomes corrupted,
it can be regenerated by using the FORCE=y option in the INIT
command. This forces the system to re-read the CDF files and generate
a new mmap file for system use.
The new CDF files are made available by using the sc_validate_cdf
utility. The files installed from the OMC-R will be named
<filename>.[cdf|cal|bootp|omcmm.net].omc on the MM and will be
located in the /screl/active/loadable/.tmpcdf directory. This directory is
removed after the CDF files are successfully validated.
preactivate XC To speed up the XC activate process the PREACTIVATE XC-xc#

command will download the XC code and/or data files to the standby
OMP. This will also validate the data file generation. So when the XC
is activated it will require less downtime.
• The Force_data option will load the data files only.
• The Force option will load both code and data files.
preactivate BTS To speed up the BTS activate process the PREACTIVATE BTS-bts#
command will download the BTS code files to the standby GLI. So
when the BTS is activated it will require less downtime.
• The Force option will load the code files only.

Student Guide 1-7
MIB
preactivate SDU To speed up the SDU activate process the PREACTIVATE SDU-sdu#
command will download the SDU code files to the standby SPROC. So
when the SDU is activated it will require less downtime.
preactivate VPU To speed up the VPU activate process the PREACTIVATE VPU-vpu#
command will download the VPU code files to the standby SPROC. So
when the VPU is activated it will require less downtime.

Student Guide 1-8
MIB
activate XC To load the XC with code and/or data files use the ACTIVATE XC-
xc# command. The major option for this command is the foreground
load or force load. This will cause a call processing outage.
• The Foreground option will check that the correct code is

loaded in the XC, then load the datafiles.
• The Force option will load both code and datafiles.
The ACTIVATE XC-xc# command will perform the following

sequence of actions:
1. The XC is rebooted.
2. The MM - XC LAN communication is established and tested.
3. Code and/or data files are downloaded from the OMC-R via the
MM or if PREACTIVATE XC-xc# command was done prior
the standby OMP will broadcast the code/data files to the other
XC devices.
4. The XC is initialized.
5. When the initialization is complete, the operator must enable

the CBSC.
activate BTS To load the BTS with code files use the ACTIVATE BTS-bts#
command. The major option for this command is the Version and
Impact.
• The Version option will specify the new software load.
• The Impact option will specify the impact of software load.
activate SDU To load the SDU with code files use the ACTIVATE SDU-sdu#
Impact.

Student Guide 1-9
MIB
activate VPU To load the VPU with code files use the ACTIVATE VPU-vpu#
Impact.

Student Guide 1 - 10
MIB
R16.4 SC Database Operations, MIB Import/Export

MIB
Notes

MIB
R16.4 SC Database Operations, MIB Import/Export

Review Exercise
Review Exercise
Directions Answer the following questions.
1. The OMC-R functions primarily as a database server containing all of the
2. Which two modes can a MIB operate?
3. Explain the purpose of the GENERATE AN-an# DATAFILES command.
4. Once the OMC, CBSC and BTS CDF files have been generated, they should be transferred to the
5. Define mmap file.

Lab Overview - MIB Management
Lab Overview - MIB Management
Directions Your instructor will direct you to the OMC-R for this exercise.
1. Backup the MIB to a directory.
2. Backup the MIB to a DAT tape.
3. Drop the MIB.
4. Import the MIB.
5. Generate the data files.
6. Install and validate the CDF files.
7. Initialize the MM, activate the XC, and enable the CBSC.
NOTE
Most of the steps being performed are in the Cellular
System Administration, OMC-R Procedures, Integrate a New
MIB Procedure.

Lab Exercise 1 - Back up the MIB to a Directory
Lab Exercise 1 - Back up the MIB to a Directory
Introduction This lab is to familiar you with the procedures to back up the MIB to a
directory.
Directions 1. Log into the OMC-R. Substitute user to scadm.

$ su - scadm
$ password: (Instructor will provide the password.)
2. Find the name of the running database.

$ env | grep DBNAME or
$ echo $DBNAME
3. Back up the database using the exportmib utility.

$ /screl/install/exportmib [database name] /screl/mibs/
backup
4. Observe the MIB backup output, then verify the date and time
of the new MIB backup directory.
$ cd /screl/mibs/backup
$ ls -la

Lab Exercise 2 - Back up the MIB to a DAT Tape
Lab Exercise 2 - Back up the MIB to a DAT Tape
Introduction This lab is to familiar you with the procedures to back up the MIB to a
DAT tape.
Directions 1. Insert a DAT tape in the DAT drive on the Sun OMC-R.
2. Create a backup fileset using tar.

$ cd /screl/mibs/backup
$ tar -cvf /dev/rmt/0 [database name]
NOTE
As the tar command runs, you should see a list of files in the
X-term window. These are the files being copied to the tape.
3. List the contents of the backup fileset.

$ tar -tv

Lab Exercise 3 - Drop the MIB
Introduction Before importing a new MIB, the existing MIB must be dropped. The
utility to modify the MIB, which includes dropping it, is dbaccess.
In order to drop the MIB, the dbaccess utility must be used. It can be
executed as scadm.
The system will not permit the MIB to be dropped as long as it is in

use. It is necessary to shut down the processes which may be accessing
the MIB. This is usually accomplished by shutting down the SC
processes. Log on the Sun OMC-R, as scadm, and execute the
following UNIX commands to shut down the application.
Directions 1. Verify the current run level. For a Sun OMC-R, the run level
should be 3.
$ who -r
2. Bring the system to run level 2.

$ su - root
# init 2
# exit
3. Verify no SC processes are running.

$ ps -ef | grep api or
$ /home/scadm/bin/omcprocs
4. Launch the dbaccess. (Make sure you are logged in as scadm.)

$ dbaccess
5. From the DBACCESS menu, select Database by entering d.

Then hit Enter.
DBACCESS: Query-Language Connection Database Table
Session Exit
NOTE
It is not necessary to enter capital D.

6. From the DATABASE menu, select Drop by entering d. Then

hit Enter.
DATABASE: Select Create Info Drop cLose Exit
7. At the DROP DATABASE prompt, select the database you

wish to drop from the list of displayed database. Then hit Enter.
DROP DATABASE>>
8. From the CONFIRM menu, select YES

CONFIRM: NO YES
9. From the DATABASE menu, select Select by entering s. Then

hit Enter. (you should not see the database you have dropped in
the display.)
10. From the DATABASE menu, select Exit by entering e. Then hit
Enter.
11. From the DBACCESS menu, select Exit by entering e, then hit
Enter.

Lab Exercise 4 - Import the MIB
Lab Exercise 4 - Import the MIB
Introduction This lab is to familiar you with the procedures to import the MIB.
Directions 1. Log into the Sun OMC-R as scadm.
2. Verify the current run level, the run level should be 2. If at run
level 3, perform step 3. Otherwise skip to step 4.
$ who -r
3. Take the Sun OMC-R to init level 2 if necessary.

$ su - root
# init 2
# exit
4. Import the MIB.

$ /screl/install/importmib [database name] /scadm/mibs/
backup
5. Bring the Sun OMC-R back to run level 3.

$ su - root
$ password: (Instructor will provide the pasword.)
# init 3
# exit
6. Verify the SC processes are running.

$ ps -ef | grep api or
$ /home/scadm/bin/omcprocs

Lab Exercise 5 - Generate the Data Files
Introduction This lab is to familiar you with the procedures to generate NE data files
from the MIB.
• Remove the old CDF files of BTS, CBSC and OMC.
• Generate the new CDF files for OMC-R, XC, AN, and SDU.
Directions 1. Login to the Sun OMC-R as scadm.
2. Change the present working directory.

$ cd /screl/active/loadable
3. Remove the old BTS CDF files.

$ rm -rf bts-*/*.cdf
4. Remove the old CBSC CDF files and bootp files.

$ rm -rf cbsc-*/*.cdf cbsc-*/*.bootp
5. Remove the old OMC CDF file.

$ rm -rf omc/omc.cdf
6. Start an OMC-R CLI session.

$ CLI
7. Generate the OMC-R data files.

> GENERATE OMCR-omcr# DATAFILES
8. Verify OMC-R data files are up to date.

> DISPLAY OMCR-omcr# DATAFILES
> DISPLAY MM-mm# DATAFILES
NOTE
The DISPLAY OMCR-omcr# DATAFILES command shows
only XC data files status. The DISPLAY MM-mm# DATAFILES
shows OMC, MM and BTS data files status.

9. Generate the XC data files.

> GENERATE XC-xc# DATAFILES
10. Verify the XC data files are up to date.

> DISPLAY XC-xc# DATAFILES
11. Generate the AN data files.

> GENERATE AN-an# DATAFILES
12. Verify the AN data files are up to date.

> DISPLAY AN-an# DATAFILES
13. Generate the SDU data files.

> GENERATE SDU-sdu# DATAFILES
14. Verify the SDU data files are up to date.

> DISPLAY SDU-sdu# DATAFILES
15. Generate the VPU data files.

> GENERATE VPU-vpu# DATAFILES
16. Verify the VPU data files are up to date.

> DISPLAY VPU-vpu# DATAFILES
17. Exit CLI

> EXIT

Lab Exercise 6 - Install and Validate the CDF Files
Lab Exercise 6 - Install and Validate the CDF Files
Introduction This lab is to familiar you with the procedures to install and validate
new CDF files on MM.
2. rlogin into MM as scadm.
3. Change the present working directory.

$ cd /screl/active/loadable
4. Remove the old CDF files from MM.

$ rm -rf */*.cdf
5. Return to OMC-R.
$ exit
6. Install the new CDF files from OMC-R to MM.

$ sc_install_cfg mm-cbsc# cdf
NOTE
This command will generate a temporary directory in the
MM to hold the transferred CDF files. After validation they
are moved to their respective directories.
7. Log into MM as scadm.

$ rlogin mm#
8. Validate the installation of CDF files on MM.

$ /screl/active/bin/sc_validate_cdf
NOTE
A validation logfile is generated. Use the UNIX command
more, cat or page the file to see how the validation
performed.

Lab Exercise 7 - Initialize the MM and Activate the XC
Introduction This lab is to familiar you with the procedures to initialize MM and
verify SC processes are running, activate the XC, then enable the
CBSC.
2. rlogin into MM as scadm.
3. Start an MM CLI session.

$ CLI
4. Initialize the SC processes on the MM.

> INIT MM-1 LEVEL=2 FORCE=y ACTION=full
5. Exit the MM CLI session.

> EXIT
6. Verify the SC processes are running.

$ ps -ef |grep api
7. Return to OMC-R.
$ exit
8. Start an OMC-R CLI session.

$ CLI
9. Find out the active version number.

> DISPLAY XC-xc# ACTVER
10. Activate the XC.

> ACTIVATE XC-xc# version=\"x.x.x.x.x\"
11. Enable the CBSC.

> ENABLE CBSC-cbsc# UNC
12. Exit the OMC-R CLI session, MM, and OMC-R.

1 - 24 Student Guide
Module 2
Access Network (AN)

This module will describe the Access Network (AN), and procedures to configuration the network.
• Describe procedures to accomplish Access Network

Configuration.
• Perform procedures to provision the AN.
• In compliance with instructor presentation and the 1X Cellular

Database Administration Student Guide.
Materials required • 1X Cellular Database Administration Student Guide

System Command Reference


Student Guide 2-1
Access Network (AN)
Acronym Definition
AN Access Network or Access Node
AGNODE Aggregation Node
BERT Bit Error Rate Test
CAT Catalyst
FRSM Frame Relay Service Module
IOS Internet Operating System
LM Line Module
MSFC Multi Layer Switch Feature Card
MLS Multi-Layer Switch
PXM Processor Switch Module

RPM Route Processor Module
SRM Service Resource Module

2-2 Student Guide
Notes

Student Guide 2-3
Access Network (AN)
Access Network
The Access Network (AN) is represented by the AN object. Also called

the Access Node. Note that the AN is not an individual device. It is a
logical entity representing multiple supplementary devices:
• Cisco Catalyst 6509 Multi-Layer Switch (MLS)
• Cisco MGX 8850 Aggregate Node (AGNODE)

2-4 Student Guide
Access Network
AN
AN1 OMCIP1 OMCIP2
MLS1 MLS2
MLS_LINKS MLS_LINKS
General EdgeRtr General EdgeRtr
PDSN PSI PDSN PSI
AGNODEs
AGNODE1
PDSN_CONs
MLS_PDSN_CON1

Student Guide 2-5
Access Network (AN)
Aggregate Node MGX8850 Aggregate Nodes are deployed in pairs within the Access
Network. Primary functions performed by the AGNODES are:
• Packet backhaul
• Packet BTS span aggregation
The AGNODE features the following cards:
• Processor Switch Module (PXM) - Provides internal ATM

switching fabric
• Service Resource Module (SRM) - Manages 1-N service

module redundancy and can perform bit error rate tests (BERT)
on service module lines
• T1/E1/T3 Frame Relay Service Module (FRSM) - Provides

frame forwarding for T1/T3 interface
• T1/E1/T3 Line Module (LM) - Provides media interface for

FRSM
• Route Processor Module (RPM) - Standard Cisco Internet

Operating System (IOS) routers providing IP routing services
• FE back card - Provides Fast Ethernet media interface for RPM
• ATM Cell Bus - internal switching between front cards
• Mid-plane - Provides connectivity between front and back cards
• 16 slots for full size cards or 32 slots for half size cards
• Reserved slots 7 and 8 for PXM cards
• Reserved slots 15, 16, and 31 and 32 for SRM cards
• Remaining slots are for RPM and FRSM cards

2-6 Student Guide
Access Network
Aggregation Node

Student Guide 2-7
Access Network (AN)
Multi-Layer Switch The Cisco Catalyst (CAT) 6509 Multi-Layer Switches (MLS) are used
for the data network transport layer. The Multi-Layer Switches are
deployed in pairs. They serve as the central traffic switching and
interconnection point. Each Cisco Catalyst 6509 has both Layer 2
(Datalink) switching and Layer 3 (Network) routing capabilities.
The MLS cabinet has the following features:
• Dual and load sharing power supplies, redundant fan and clocks
• Nine total chassis slots with slots 1 and 2 reserved for the
supervisor processors
• Supervisor processors include Multi Layer Switch Feature Card

(MSFC) for layer 3 processing
• The seven remaining slots are available for a combination of

switching modules including:
- 48 ports RJ-45 10/100BaseT (Fast) Ethernet switching

modules
- 16 port RJ-45 1000BaseT (Gigabit) Ethernet switching

modules

2-8 Student Guide
Access Network
Multi-Layer Switch
Fan Assembly
Supervisor Engine Redun.

Gigabit Ethernet 16 Port
10/100 Ethernet 48 Port
Supervisor Engine
Open
Open
Open
Open
Open
9 8 7 6 5 4 3 2 1
Power Supply 1 Power Supply 2

Student Guide 2-9
Access Network (AN)
AN Device First the AN devices must be added to the OMC-R (MIB) database.
Management Then the generated AN datafiles are FTP’ed to the OMC-IPs for
network element management. The Sun OMC-IP is an integrated
logical solution made up of a suite of Sun Microsystems server
platforms, Cisco element managers, Motorola software and other third
party applications. The primary function of the Sun OMC-IP is to
provide Cisco element management capabilities.
Three OMC-IPs must be provisioned.
• The first OMC-IP is used for maintaining and troubleshooting

of the Catalyst 6509 (MLS), Cisco PDSN and BTS routers.
RPMs are also called Edge Routers (EDGERTR). It runs on the
Cisco Works for Mobile Wireless (CW4MW) software.
• The second OMC-IP is used for maintaining and

troubleshooting of the MGX 8850 (AGNODE). It runs on the
Cisco WAN Manager (CWM) software.
• The third OMC-IP is used for configuration and management of

the AGNODE, Route Processor Modules (RPM) in the
AGNODE and BTS routers, and is to provide flow-through
provisioning. It runs on the Cisco Mobile Wireless Center
(CMWC) software.
NOTE
Motorola has chosen the Sun Netra 20 model platforms to
replace the current OMC-IP platforms. Refer to Motorola
Bulletin cdma_g_omc_015.

Lab Exercise - Provision the AN
Introduction This lab is to familiar you with the procedure to add AN to the
database.
Directions
NOTE
Refer to CDMA Online Documentation: Cellular System
Administration and System Commands Reference for each
command.
NOTE
The instructor will provide the user names and
passwords.
1. Log into UNO from an x-terminal by entering a valid user name

and password.
________________________________________________
2. Open a terminal window by using the mouse and pull down

menu. For example, click the right mouse button and select
Programs >> Terminal.
________________________________________________
3. Telnet (or rlogin) to the OMC-R and login by entering a valid

user name and password.
________________________________________________
4. Open the CLI window. Type CLI at the OMC-R prompt.
________________________________________________

Access Network (AN)
IMPORTANT
Development has not completed integration of the OMC-IPs

into the R16 network. As a result, all Cisco devices must be
configured manually.
OMC-IPs still must be provisioned for CLI purposes.
5. Add three OMC-IPs. The OMC-IP can be local to the AN or

remote. If true is selected, the IP address will be allocated by
the OMC-R when you provision the connection between the
MLS and the OMC-IP. If false is selected, the OMC-IP will be
outside the IP pool for this AN, and you must specify an IP
address.
Add the first OMC-IP (CW4MW). Command: ADD OMCIP-

omcip# ISLOCAL=t TYPE=cw4mw IPADDRESS=<cr>
________________________________________________
6. Add the second OMC-IP (CWM). Command: ADD OMCIP-

omcip# ISLOCAL=t TYPE=cwm IPADDRESS=<cr>
________________________________________________
7. Add the third OMC-IP (CMWC or DMM). Command: ADD

OMCIP-omcip# ISLOCAL=t TYPE=dmm
IPADDRESS=<cr>
________________________________________________

8. Add the AN device. Command: ADD AN-an# DEVICE

ANIP=10.xxx.0.0 ANSUBNETMASK=255.255.252.0
CBSCIP=10.xxx.64.0 CBSCSUBNETMASK=255.255.192.0
BTSIP=10.xxx.128.0 BTSSUBNETMASK=255.255.240.0
PCFIP=10.xxx.192.0 PCFSUBNETMASK=255.255.240.0
COMMONIP=10.xxx.224.0 COMMONSUBNETMASK=
255.255.255.0 SITENAME=AN-an# LATITUDE=42-4-11
LONGITUDE=-88-2-54 CW4MW=omcip1#
CWM=omcip2# MASTEROMCR=omcr#
STARTVLANNUM=5 ENDVLANNUM=255
STARTMULTICAST=239.193.0.1
ENDMULTICAST=239.193.255.255 CMWC=omcip3#
________________________________________________
9. Add two MLSs. Command: ADD MLS-an#-mls#

HWTYPE=cat6509 IPADDRESS=<cr>
SUBNETMASK=<cr> RELNUM=IOS_12_1_13_E4 (R16.3
only)
________________________________________________
10. Add three MLS to OMC-IP connections. Command: ADD

MLS_OMCIP_CON-omcip#-1 MLS1=an#-1 MLS2=an#-2
MLS1MODULE=4 MLS1PORT=mls1port#
________________________________________________
11. Add the MLS trunk. Command: ADD MLS_TRUNK-an#-1

TYPE=l2 (R16.1 only) MLS1=an#-1 MLS2=an#-2
________________________________________________
12. Add four MLS links. Command: ADD MLS_LINK-an#-1-

mlslink# MLS1MODULE=3 MLS1PORT=mls1port#
________________________________________________
13. Add the Agnode. Command: ADD AGNODE-an#-agnode#

HWTYPE=mgx8850 RELNUM=PXM_1_2_11 (R16.3 only)
________________________________________________

Access Network (AN)
14. Add the redundant EDGERTR. Command: ADD EDGERTR-

an#-edgertr# AGNODE=an#-agnode#
AGNODESLOT=agnodeslot# MAXPKTPIPES=<cr>
ISREDUNDANT=isredundant? HWTYPE=rpm7200
HEADERCOM=y RELNUM=IOS_12_2_8_MC2d (R16.3
only)
________________________________________________
15. Add the EDGERTR. Command: ADD EDGERTR-an#-

edgertr# AGNODE=an#-agnode#
AGNODESLOT=agnodeslot# MAXPKTPIPES=<cr>
ISREDUNDANT=isredundant? HWTYPE=rpm7200
HEADERCOM=y RELNUM=IOS_12_2_8_MC2d (R16.3
only)
________________________________________________
16. Add two MLS to EDGERTR connections. Command: ADD

MLS_EDGERTR_CON-an#-edgertr#-1 MLS1=an#-1
MLS2=an#-2 MLS1MODULE=4 MLS1PORT=mls1port#
________________________________________________
17. Initialize the Agnode. Command: INIT AGNODE-an#-

agnode#
________________________________________________
18. Add the redundant FRSM card. Command: ADD FRCARD-

an#-agnode#-slot# TYPE=t1r_8 RELNUM= (R16.3 only)
________________________________________________
19. Add the FRSM card. Command: ADD FRCARD-an#-

agnode#-frsmslot# TYPE=t1_8
________________________________________________

20. Add the PDSN cluster. Command: ADD PDSN_CLUSTER-

pdsncluster# NUMPDSNS=1 SPI=0x00000100
SECURITYKEY=0123456789abcdef0123456789abcdef
SUMMARIZED=y IPADDRESS=10.xxx.12.0
SUBNETMASK=255.255.255.0
________________________________________________
21. Add the MLS to PDSN connection. Command: ADD

MLS_PDSN_CON-an#-1 MLS1=an#-1 MLS2=an#-2
MLS1MODULE1=4 MLS1PORT1=mls1port#
MLS2MODULE1=4 MLS2PORT1=mls2port#
PDSNCLUSTER=pdsncluster# ANOFFSET=1
________________________________________________
22. Add the DACS. Command: ADD DACS-dacs#

PRODUCTINFO=xyz DESCRIPTION=<cr>
________________________________________________
23. Add the Agonde span. Command: ADD AGNODE_SPAN-

an#-agnode#-1 SINKTERMDEV=dacs-dacs#
SINKTERMPORT=1 SINKTERMMODULE=1
FRSMSLOT=1 FRSMLINE=1 SPANTYPE=t1_2
SRCSPANEQ=<cr> SINKSPANEQ=<cr>
STARTINH=<cr>
________________________________________________
24. Verify the AGNODE configuration. Command: DISPLAY

AGNODE-an#-agnode# BOARDCONF

Access Network (AN)
Notes

Module 3

This module describes procedures for the Centralized Base Station Controller (CBSC) associated with
1X.
• Describe CBSC commands associated with 1X CBSC

provisioning.
• Perform procedures to provision the CBSC.
• In compliance with instructor presentation, CDMA Online

Documentation - Cellular System Administration, System
Commands Reference Release 2.16 and the 1X Cellular


System Commands Reference

Student Guide 3-1
Acronym Definition
CBSC Centralized Base Station Controller
ICLINK Inter-CBSC Link
IMSI International Mobile Station Identifier
OMC-R Operations & Maintenance Center -Radio
MCC Mobile Country Code
MM Mobility Manager
MMI Man Machine Interface

MNC Mobile Network Code
MSC Mobile Switching Center
PDSN Packet Data Service Node

PKTPCF Packet Control Function
PKTIF Packet Interface Function
SERVOPT Service Option
TCBSC Target Centralized Base Station Controller

3-2 Student Guide
CBSC Setup
CBSC Setup
Introduction This module covers information about adding a Centralized Base

Station Controller (CBSC) and how to enable 1X packet data services.
NOTE
The steps required during installation are significant and
must be performed after CBSC provisioning, but before the
CBSC can be enabled.
Procedures covered in this module are:
• Add a CBSC platform
• Add a target CBSC
• Add inter-CBSC packet link
• Add 1X packet data services
• Edit CBSC backhaul

Student Guide 3-3
CBSC Setup Procedure
Planning Several planning steps are required before provisioning can begin.
1. Determine the CBSC ID and MSC connectivity.
2. Determine CDMA service parameters.
3. Determine if any ICTRKGRPs need to be configured by

entering the DISPLAY ICTRKGRP-cbsc#-ictrkgrp#
ICTRKGRPCONF command.
4. Determine if any overload tables need to be modified.
5. Determine equipage of the XC.
System Setup This lists sub-procedures and/or commands need to add the CBSC to
the OMC-R database (MIB).
1. Add CBSC and set MSC parameters.
2. Set up the CBSC CDMA service parameters.
3. Set up LFR support, if required.
4. Set up test mobile support, if required.
5. Set up handoff constraint tables.
6. Set up congestion and overload tables.
7. Add the XC platform to the database and set XC service

parameters.
8. Add the XC frames, cages, and boards. Add the frames in

ascending order using the System Setup steps from the
Transcoder Frame Expansion procedure.
9. Equip the MSC interface.
10. Equip the inter-CBSC interfaces.
11. Equip the data services.

3-4 Student Guide
CBSC Setup Procedure
12. Configure the BTSSPANs, BTSLINKs, and the BTSs. Use the
System Setup steps from the BTS Setup procedure.
Refer To: Manual: 68P09258A91 OMC-R and CBSC Hardware Installation

Manual: 68P09258A92 OMC-R and CBSC Hardware Packet Data
Upgrade manuals for the physical installation information
Manual: CDMA Online Documentation Software Release 2.16.3.X
CDMA2000 1X - System Commands Reference

Student Guide 3-5
Add the Target CBSC
Purpose This ADD TCBSC-tcbsc# CDMASYS command adds a Target

Centralized Base Station Controller (TCBSC) to the Configuration
Management Database. The TCBSC represents another CDMA system
outside of the management scope of an OMC-R that the OMC-R must
interface with for handoffs.
The TCBSC could be either:
• External - Not on this OMC-R
• Foreign - Not a Motorola CBSC (Future IOS capability)
Refer To: Manual: CDMA Online Documentation Software Release 2.16.3.X


3-6 Student Guide
Add the Inter-CBSC Packet Link
Add the Inter-CBSC Packet Link
Purpose This ADD ICLINK-cbsc#-ictrkgrp#-iclink# command adds an inter-

CBSC link (ICLINK) to the Configuration Management Database.
Refer To: CDMA Online Documentation Software Release 2.16.3.X CDMA2000

1X - System Commands Reference

Student Guide 3-7
Add the 1X Packet Data Services
Purpose Allows CBSC to provides 1X packet data service to 1X mobile

stations.
Planning Several planning steps are required before provisioning can begin.
1. Verify that a PDSN is provisioned and in service. For more

information, see the Connecting a PDSN to a BSSAN
procedure.
2. Ensure that the service option is configured.
3. Identify the CBSC’s parent MSC and verify that the 1X packet
data service option is configured on the MSC.
Cut into Service To enable a CBSC to perform 1X packet data services.
1. Add a servopt object for the 1X packet data service option. Run
the ADD SERVOPT-cbsc#-servopt# command.
2. View the default settings of the 1X packet data service option,

where the defaults are defined in the Default Values of 1X
Packet Data Service Option Table.
3. If required, edit the service option to alter the parameters to

non-default settings.
4. Set the packet data 1X upgrade service option to 1X packet data

for each packet data service option listed in the Packet Data
Service Options Other than 1X Table. Run the EDIT
SERVOPT-cbsc#-servopt# SOORDPREF command.

3-8 Student Guide
DISPLAY CBSC-1 SOSERV
Student Guide
| | TCH | XCDR | | |
SO ID | | CKT | CKT | |STEP|
Revision 2.2 - 11/03

CBSC#-SO# | NAME | SERV | SERV |BYPASS | UP |CALLSRVMODE
------------|--------------------------------|------|------|-------|----|-----------
1-0x0000 SoDEFAULT 0x0001 0x0001 PROCESS 20 VOICE
1-0x0001 So8KVoice 0x0001 0x0001 PROCESS 20 VOICE
1-0x0002 So8KLoop 0x0002 0x0002 PROCESS 20 TEST
1-0x0003 SoEvrc 0x0003 0x0003 PROCESS 20 VOICE
1-0x0004 So8kData 0x0004 0x0004 PROCESS 20 ASYNCDATA
1-0x0005 S08kFax 0x0004 0x0004 PROCESS 20 FAX
1-0x0007 LSPD RS1 0x0004 0x0006 PROCESS 20 LOSPPKTDATA
1-0x0009 So13KLoop 0x0009 0x0009 PROCESS 20 TEST
1-0x000c So13kData 0x000c 0x000c PROCESS 20 ASYNCDATA
1-0x000d So13kFax 0x000c 0x000c PROCESS 20 FAX
1-0x000f LSPD RS2 0x0004 0x0006 PROCESS 20 LOSPPKTDATA
1-0x0016 HSPD RS1_Fw_RS1_Rev 0x0004 0x0007 PROCESS 20 HISPPKTDATA
1-0x0019 HSPD RS2_Fw_RS2_Rev 0x0004 0x0007 PROCESS 20 HISPPKTDATA
1-0x0021 1X Packet Data 0x0004 0x0008 PROCESS 20 PKT1XDATA
1-0x1007 LSPD_RS1 0x0004 0x0006 PROCESS 20 LOSPPKTDATA
1-0x8000 So13KVoice 0x8000 0x8000 PROCESS 20 VOICE
1-0x8002 So8KMarkov 0x8002 0x8002 PROCESS 20 TEST
1X Cellular Database Administration

1-0x8003 SoMtoMDATA 0x8003 0x8003 BYPASS 20 TEST
1-0x801e So8KMarkov2 0x801e 0x801e PROCESS 20 TEST
1-0x801f So13KMarkov 0x801f 0x801f PROCESS 20 TEST
Add the 1X Packet Data Services
3-9
OMCR100A
Edit the CBSC Backhaul Parameter
Purpose The EDIT CBSC-cbsc# BACKHAULPARMS command modifies

the CBSC backhaul parameters.
Circuit backhaul is the default. Editing the CBSC backhaul will allow
both circuit and packet backhaul to be used.
Refer To: Manual: CDMA Online Documentation Software Release 2.16.3.X


Review Exercise
Review Exercise
Directions Respond to the following questions.
1. The ADD CBSC-cbsc# PLATFORM command will fail if the following precondition checks are not
met:
2. What is the purpose of the DISPLAY CBSC-cbsc# SOPARMS command?
3. What is the purpose of setting up a TCBSC?
4. Which new service option parameter needs to be enabled for data calls?

Lab Exercise - Provision the CBSC
Introduction This lab is to familiar you with the procedures to add CBSC to the
database.
Directions 1. Open the CLI window. Type the CLI at the OMC-R prompt.
_________________________________________________
2. Add the CBSC platform. Command: ADD CBSC-cbsc#

PLATFORM SSTYPE=cdma1900 MCC=300 MNC=30
INTERNALID=cbsc# ACCESSNETWORK=an#
________________________________________________
3. Edit the CBSC carrier. Command: EDIT CBSC-cbsc#

CARRIER CARRIER1=carrier1# CARRIER2=!
________________________________________________
4. Add the neighbor CBSC. Command: ADD TCBSC-tcbsc#

CDMASYS SYSTEMMGR=external MCC=300 MNC=30
SYSTEMAB=a SWITCHID=0 MARKETID=<cr>
SWITCHNUMBER=0 LATITUDE=42-4-11
LONGITUDE=-88-3-12 SYSNAME=another omcr
GROUP=4 INTERNALID=cbsc# FARMMIP=<cr>
TCBSCPREV=6
________________________________________________
5. Add the inter CBSC trunk group. Command: ADD

ICTRKGRP-cbsc#-1 TCBSC#=tcbsc#
SELECTMODE=<cr> ANCHORHOMETH=<cr>
CONNECTIONTOGGLE=<cr>
________________________________________________

Lab Exercise - Provision the CBSC
6. Add the MLS to MM connection. Command: ADD

MLS_MM_CON-cbsc#-1 MLS1=an#-1 MLS2=an#-2
MLS1MODULE=4 MLS1PORT=1 MLS2MODULE=4
MLS2PORT=1
________________________________________________
7. Add two C7 links. Command: ADD C7LINK-cbsc#-1-c7link#

PARENTMSCSPAN=<cr> TSLOT=<cr> C7SPAN=<cr>
C7SLOT=<cr> SLP=slp# LINKSPEED=64
LINKNAME=<cr> (R16.3 only)
SIGNALLINGLINKCHANNEL=<cr> (R16.3 only)
________________________________________________
8. Add the service option. Command: ADD SERVOPT-cbsc#-33

NAME=xyz AUTOCREATE=y
________________________________________________
9. Edit the CBSC CBSCGEN. Command: EDIT CBSC-cbsc#

CBSCGEN RATE=<cr> PILOTINC=<cr> MINPREV=1
INACTALARMDET=!
________________________________________________
10. Edit the neighbor CBSC CBSCGEN. Command: EDIT

TCBSC-tcbsc# CBSCGEN PREV=6
________________________________________________
11. Edit the CBSC backhaul type. Command: EDIT CBSC-cbsc#

BACKHAULPARMS BACKHAULTYPE=packet
________________________________________________

Notes

Module 4
Transcoder (XC)
R16.0 adds new hardware, and R16.0 and R16.3 add new software functionality to the Transcoder (XC)
subsystem. This module will take you through the procedures to equip a Transcoder in the database.
• Describe hardware and software additions associated with 1X

Transcoder creation in the database.
• Perform procedures to provision the XC.
• In compliance with the instructor presentation and 1X Cellular




Student Guide 4-1
Transcoder (XC)
Acronym Definition
BIB Balanced-line Interconnect Board
EGP Enhanced Generic Processor
OMP Operation and Maintenance Processor
PBIB Packet Balanced-line Interconnect Board
PKTIF Packet Interface
PSI Packet Subrate Interface
RAN Radio Access Node

SDU Selection Distribution Unit
XC Transcoder

4-2 Student Guide
Introduction The R16.0 release notes describe the changes and features for this
release. Some of the hardware and software features that are included
as part of this release are as follows.
Packet Subrate Packet Subrate Interface (PSI) is a new card in the XC as of R16. It is a
Interface bridge and router between the circuit network of the XC and packet
data network via the Access Node (AN) for bearer and call control
traffic. Bridge functionality converts data from Gigabit Ethernet on the
packet side to internal XC protocols on the circuit side. PSI router
functionality interworks and routes to and from the following devices:
MSI, XCDR and FEP. Three functions may run on the PSI in R16:
• PSI-CE (Channel Element) (but list as PKTIF)
• PSI-SEL (Selection)
• PSI-PCF (Packet Control Function)
PSIs can be placed in any valid MSI slot but they will require a Packet
Balanced-line Interconnect Board (PBIB).
In R16.3 the PSI-CE card can be assigned to perform the PSI-TER

(terrestrial) function which is used in VPU interfacing.
PSI Code Object #176 This is a new code object that was added in R16 to support the PSI
functionality. This code object is 1.8 MB in size. The size of this object
requires the Operation and Maintenance Processor (OMP) and OMPR
slots to have Enhanced GPROCs (EGPs).
Packet Balanced-line The Packet Balanced-line Interconnect Board (PBIB) is a field-

Interconnect Board upgradeable, drop-in replacement for the current Balanced-line
Interconnect Board (BIB).
The PBIB provides the physical termination of external span and

Ethernet cabling to the Transcoder (XC) cabinet. Each PBIB supports
three XC slots via four wire pairs per slot.
While the current BIB supports only spans, the PBIB provides external
Ethernet connectivity to three PSI/MSI slots. There are two types of
PBIBs:
• PBIB-ES: Dual span connectivity to two slots (MSI) and

1000BaseT (Gigabit) Ethernet to one slot (PSI)

Student Guide 4-3
Transcoder (XC)
• PBIB-E: Dual 100BaseT Ethernet to three slots (PSI)
• When going from R16.0 to R16.1 and adding SDU the PSI-SEL
and PSI-PCF cards and associated PBIBs will be removed.
NOTE
The three slots supported by the BIB must be taken out of
service if they contain configured MSI boards.
XC PBIB Position and Slot Assignments
XC PBIB
XC Slot Assignment
Position
Port 1 Port 2 Port 3

PBIB-ES Dual T-Span Dual T-Span 1000BaseT
PBIB-E Dual 10/ Dual 10/ Dual 10/
100BaseT 100BaseT 100BaseT
PBIB # Slot Slot Slot
0 17 15 13
1 16 14 12
2 11 9 7
3 10 8 6
CAUTION
It is assumed here that there will be a system outage when
the upgrade is done. The spans under the MSIs which will
be taken out of service unless re-parented under a different
MSI.

4-4 Student Guide
Enhanced GPROC The EGP was designed to be a drop-in replacement for the GPROC
(EGP) in OMP and board in the Transcoder subsystem. The EGP can act as an OMP, CPP,
OMPR Slots CDP, FEP or Cage Controller. All interfaces to the EGP are identical to
the GPROC. The EGP is designed to inter-operate in a mixed GPROC/
EGP environment. The EGP offers increased processor performance
and redundancy over the current GPROC. While in R15, EGPs were
optional, in R16, it became mandatory to have EGPs in OMP and
OMPR slots in order to operate the PSIs.

Student Guide 4-5
Transcoder (XC)
Lab Exercise - Provision the XC
Introduction This lab is to familiar you with the procedures to add the 1X XC to the
database.
_________________________________________________
2. Add the XC. Command: ADD XC-xc# PLATFORM

CLKREDUNDANT=y TDMREDUNDANT=y
LANREDUNDANT=y ECHOCANCELLER=enable
TDMCAPACITY=double_capacity
FEPCPPLINKSPEED=64 FEPPSILINKSPEED=384
MLSTRUNK=an#-1 (R16.1 only)
XCDRTDMPORTMODE=<cr>
___________________________________________________
3. Add the XC frame. Command: ADD XCFRAME-xc#-1

AMRCONF=upper
___________________________________________________
4. Add two XC cages. Command: ADD XCCAGE-xc#-xccage#

CLKXAPORT=xc#-1-107-clkxport#
INPUTLANA=inputlana# TDMCONF=tdmconftype
RMTKSWXA=rmtkswxa# TDMPAIR=tdmpair#
PLANNEDTDMPORTS=<cr> MS0PBIB=ms0pbibtype
MS1PBIB=ms1pbibtype MLS2PBIB=ms2pbibtype
MS3PBIB=ms3pbibtype
___________________________________________________
5. Add two OMP cards. Command: ADD OMP-xc#-omp#

SUBTYPE=xcegp
___________________________________________________

4-6 Student Guide
6. Add the redundant FEP card. Command: ADD FEPR-xc#-fep#

GPROC=xc#-1-25 SUBTYPE=fepegp AUTOCREATE=y
___________________________________________________
7. Add two FEP cards. Command: ADD FEP-xc#-fep#

GPROC=xc#-2-gprocslot# SUBTYPE=fepegp
AUTOCREATE=y
___________________________________________________
8. Add two CPP cards. Command: ADD CPP-xc#-cpp#

GPROC=xc#-xccage#-gprocslot# SUBTYPE=xcgproc
AUTOCREATE=y FEP=xc#-fep#
___________________________________________________
9. Add the CDP card. Command: ADD CDP-xc#-1

GPROC=xc#-2-gprocslot# SUBTYPE=xcgproc
AUTOCREATE=y
___________________________________________________
10. Add three XCDR cards. Command: ADD XCDR-xc#-xccage#-

xcdrslot# SUBTYPE=hxcdr VOCODERRG=xc#-
vocoderrg#
___________________________________________________
11. Add three MSIP cards. Command: ADD MSIP-xc#-xccage#-

msipslot#
___________________________________________________
12. Add two PSI-CE cards. Command: ADD PKTIF-xc#-pktif#

PSI=xc#-1-psislot# AUTOCREATE=y
NUMTDMPORTPAIR=100
NUMTDMPSITERPAIR=numtdmpsiterpair (R16.3 only)
FEP=xc#-fep#
___________________________________________________

Student Guide 4-7
Transcoder (XC)
NOTE
If you have an SDU then you would only add PSI-CE cards
(PKTIF) and would not do steps 13 and 14. For step 15, you
only need to add one MLS to PSI connection.
13. Add the PSI-SEL card. Command: ADD PKTSEL-xc#-1

PSI=xc#-1-15 AUTOCREATE=y
___________________________________________________
14. Add the PSI-PCF card. Command: ADD PKTPCF-xc#-1

PSI=xc#-1-13 AUTOCREATE=y
___________________________________________________
15. Add three MLS to PSI connections. Command: ADD

MLS_PSI_CON-xc#-mls_psi_con# PSI1=xc#-1-psi1slot#
MLS1=an#-1 MLS1MODULE=mls1slot#
MLS1PORT=mls1port# PSI2=xc#-1-psi2slot# MLS2=an#-2
MLS2MODULE=mls2slot# MLS2PORT=mls2port#
___________________________________________________
16. Edit the PKTPCF PDSN cluster. Command: EDIT PKTPCF-

xc#-1 PDSN_CLUSTER ACTION=add
PDSN_CLUSTER=pdsncluster#
___________________________________________________
17. Add the inter-CBSC link. Command: ADD ICLINK-cbsc#-1-0

PARENTICDS0=<cr> FEP=cbsc#-2 LINKSPEED=64
ICLINKCONNTYPE=packet
___________________________________________________
NOTE
When adding an XC cage, the MS0PBIB, MS1PBIB,
MS2PBIB and MS3PBIB assignments should be
compatible with the slots chosen for the PSIs.

4-8 Student Guide
XC Architecture

Student Guide 4-9
Transcoder (XC)
Notes

Module 5

This module describes commands associated with the BTS. Commands are used to add component
components, edit parameters and display outputs.
• Describe MCC-1X and BBX-1X cards associated with SC™

4812T, SC™ 4812ET and SC™ 4812ET Lite 1X upgrade.
• Describe SC™ 4812T, SC™ 4812ET and SC™ 4812ET Lite

cage configuration for 1X upgrade.
• Perform procedures to provision 1X BTSs.
• In compliance with instructor presentation and 1X Cellular




Student Guide 5-1
Acronym Definition
AN Access Node or Access Network
BBX Broadband Transceiver
BBX-R Redundant BBX
CHI Concentration Highway Interface
CNEOMI Command Network Element Operations and

Maintenance Interface
GLI Group Line Interface
LAN Local Area Network
LMF Local Maintenance Facility
MCC Multi-Channel CDMA
MIB Management Information Base
MWR Mobile Wireless Router
RJ Registered Jack
SC SuperCell

5-2 Student Guide
1X Cards
1X Cards
BBX–1X Card The BBX-1X card is a third generation upgrade card supporting all IS-
95 A and B specification requirements for 2G operation and IS-95C
(IS-2000 CDMA) 3G operation. There are two versions of the card:
• 800 MHz (model number SGLF4133CA)
• 1.9 GHz (model number SGLG4044CA)
Both versions of the card may be installed in SC™ 4812T, SC™

4812ET and SC™ 4812ET Lite BTS frames.
The BBX-1X card is capable of operating as either a primary or

redundant BBX with a mix of 2G and 3G GLI, MCC, and BBX cards in
the same cage. It will operate with MCC-8E, MCC-24E, MCC–1X,
GLI2, and BBX cards, and will support circuit or 1X packet operation
for the carrier to which it is dedicated. Providing 1X capability,
however, requires an MCC-1X card to support the channel elements for
the 1X carrier.
MCC–1X Card The MCC-1X card is an upgrade card which supports up to 64 CDMA
channels of any type and complies with IS–95C specification
requirements for 1X packet operation. For R16.1 and beyond, there are
three versions of the card:
• MCC16–1X supporting 16 channel elements (upgradeable to

48)
• MCC48–1X supporting 48 channel elements
• MCC64-1X supporting 64 channel elements
Both versions of the card may be installed in SC™ 4812T, SC™

4812ET, and SC™ 4812ET Lite BTS frames. MCC-1X cards do
support IS-95A/B voice/data calls.
The MCC-1X cards are capable of operating with a mix of 2G and 3G

cards in the same cage. BBX cards may be in the same cage, but may
only be mated with MCC-8E or MCC-24E cards.

Student Guide 5-3
GLI3 Card The Group Line Interface 3 (GLI3) has similar controlling functions
within the BTS as the GLI2. In addition to these functions, the GLI3
can be configured in either circuit or packet mode.
• Message router between SC network and BTS (via AN)
- Circuit mode - GLI has similar functions as GLI2
- Packet mode
» All bearer and control is in IP format
» GLI3 will translate from IP format (external to frame) to

CHI bus format (internal to frame)
• Ethernet LAN provides for external frame communications and

LMF control interface
• GLI3 expanded functions
- Provides 4 Ethernet ports on the front panel
» Two 100BaseT (RJ-45) connections for MWR

interconnection, one to each MWR for redundancy
» One 100BaseT (RJ-45) connection for GLI-to-GLI

communication (Dual port using 8 pins)
» One 100BaseT (RJ-45) connection for Auxiliary/

Monitor port
- GLI3 in packet mode, will utilize CNEOMI agent making

available: Object Management, Configuration Management,
Software Load Management, Performance Management,
and Event Management

5-4 Student Guide
Filler Panel
HSO/LFR
POWER SUPPLY
LFR /LFR2
Student Guide
CSM (slot) 1

CSM (slot) 2
HSO/HSO2/HSOX
Modules
POWER SUPPLY
CCD 2 CCD 1
Two Half Height

IFM/Filler POWER SUPPLY
AMR 2 AMR 1
GLI (slot) 2 GLI (slot)1
IFM (Optional)
MCC-/MCC-1X 7 MCC/MCC-1X 1
or MCC-1Xs
BBX-1X 7 BBX-1X 1

BBX-1X 8 BBX-1X 2
BBX-1X 9 BBX-1X 3
BBX-1X 10 BBX-1X 4
SC™ 4812ET C-CCP Cage
NOTE: MCCs may be MCC8Es, MCC24s

BBX-1X 11 BBX-1X 5
BBX-1X 12 BBX-1X 6
Switch BBX-1X 13
Mounting Bracket)
CIO/MCIO (Behind MPC /EMPC2 MPC /EMPC1
OMCR100A
5-5
1X Cards
Lab Exercise - Provision the BTS
Introduction This lab is to familiar you with the procedures to add BTS to the
database. You will add two BTSs, one SC4812ET and one SC300.
Directions 1. Open the CLI window. Type the CLI in front of OMC-R
prompt.
_________________________________________________
2. Add the SC4812ET BTS. Command: ADD BTS-bts#

PARENTCBSC=cbsc# SITECONF=ontwenty
SSTYPE=cdma1900_1700 CARRIER=carrier#
LOCATIONAREA=<cr> TCHWCCNT=<cr>
SITENAME=<cr> FRAMENAME=sc4812et
BANDCLASS=cdma1900 FREQBAND=uspcs
MODE=packet (or circuit) SATBACKHAUL=<cr> (R16.3
only) FRAMERED=<cr> (R16.3 only)
_________________________________________________
NOTE
Adding the BTS to the database provisions all sectors,
MDM, logical channels (ACH, SCH and PCH) for all sectors,
one carrier, remote GLI and the BTS frame by default.
3. Edit the BTS system ID and network ID. Command: EDIT

BTS-bts# SIDNID SID=4 NID=13
_________________________________________________
4. Edit three carriers. Command: EDIT TCARRIER-tcbsc#-

tbts#-tsector#-tcarrier# TCARRIERCONF
PILOTPN=pilotpn# TYPE=normal BROADCASTNBR=20
ONEXVOICE=on ONEXDATA=on
_________________________________________________

5-6 Student Guide
5. Add the LPA device. Command: ADD LPA-bts#-1 DEVICE

FRAME=bts#-1 PATYPE=trunked NUMMODULE=4
RATEDPWR=48
_________________________________________________
6. Edit three carrier LPA links. Command: EDIT CARRIER-

bts#-sector#-carrier# LPALINK LPA=bts#-1
_________________________________________________
NOTE
If used packet mode in step 2, skip steps 7 and 8.
7. Add the BTS span. Command: ADD BTSSPAN-bts#-1

SRCTERMDEV=msip-xc#-1-8 SRCTERMPORT=1
SPANTYPE=t1_2 SRCSPANEQ=t1_1 SINKSPANEQ=t1_1
STARTINH=<cr> NUMTDMPORT=18 STARTPIPE=19
DACS=dacs# DACSMODULEBTS=2 DACSPORTBTS=1
DACSMODULEXC=3 DACSPORTXC=1
FRSMSLOT=<cr> SUPPINFO=<cr>
_________________________________________________
8. Add the BTS link. Command: ADD BTSLINK-bts#-1

BTSDS0=bts#-1-1 FEP=xc#-2 LINKSPEED=64
_________________________________________________
9. Edit the MDM type. Command: EDIT MDM-bts#-1

MDMTYPE SSTYPE=<cr> BANDCLASS=<cr>
FREQBAND=<cr> CAGECONF=ccp12
BIOTYPE=onetwenty BTSRTRCLUSTER=<cr>
_________________________________________________
10. Add the second MGLI card. Command: ADD MGLI-bts#-2

TYPE=gli3 (or cgli if used circuit mode in step 2)
_________________________________________________
11. Add the second CSM card. Command: ADD CSM-bts#-2
_________________________________________________

Student Guide 5-7
12. Add three BBX cards. Command: ADD BBX-bts#-bbx#

BBXTYPE=bbx1x
_________________________________________________
13. Add the redundant BBX card. Command: ADD BBXR-bts#-1

BBXTYPE=bbx1x
_________________________________________________
14. Add two MCC cards. Command: ADD MCC-bts#-mcc#

MODE=mode? MODE2=traffic MCCTYPE=mcc1x
CSM1CSET=1 CSM2CSET=1 TCHCOUNT=24
TCHCOUNT2=24 PIPESIZE=<cr> PBTSDS0=<cr>
_________________________________________________
15. Edit the MDM link. Command: EDIT MDM-bts#-1 LINK

CARRIERA=carrier# CSETA=1 CARRIERB=!
_________________________________________________
NOTE
The following step adds a neighbor carrier for 3 sectors in a cell
site. This CLI command still for the original SC4812ET, not for real
target cell site.
16. Add three neighbor carriers. Command: ADD TCARRIER-

tcbsc#-tbts#-tsector#-tcarrier# NEIGHBOR
INSERTION_POINT=insertionpoint# DETECT1=tcbsc#-
tbts#-tsector#-tcarrier# HOMETHOD1=soft
DEST1=tcarrier-tcbsc#-tbts#-tsector#-tcarrier#
CONFIG1=same DETECT2=tcbsc#-tbts#-tsector#-
tcarrier# HOMETHOD2=soft DEST2=tcarrier-tcbsc#-
tbts#-tsector#-tcarrier# CONFIG2=same DETECT3=!
_________________________________________________

5-8 Student Guide
17. Add the SC300 BTS. Command: ADD BTS-bts#

PARENTCBSC=cbsc# SITECONF=omni
SSTYPE=cdma1900_1700 CARRIER=carrier#
LOCATIONAREA=<cr> TCHWCCNT=<cr>
SITENAME=<cr> FRAMENAME=sc300h
BANDCLASS=<cr> FREQBAND=uspcs MODE=circuit
SATBACKHAUL=<cr> (R16.3 only) FRAMERED=<cr>
(R16.3 only)
_________________________________________________
18. Edit the BTS system ID and network ID. Command: EDIT
BTS-bts# SIDNID SID=4 NID=13
_________________________________________________
19. Add the BTS span. Command: ADD BTSSPAN-bts#-1

SRCTERMDEV=msip-xc#-1-9 SRCTERMPORT=1
SPANTYPE=t1_2 SRCSPANEQ=t1_1 SINKSPANEQ=t1_1
STARTINH=<cr> NUMTDMPORT=24 STARTPIPE=19
DACS=dacs# DACSMODULEBTS=2 DACSPORTBTS=2
DACSMODULEXC=3 DACSPORTXC=2
FRSMSLOT=<cr> SUPPINFO=<cr>
_________________________________________________
20. Add the BTS link. Command: ADD BTSLINK-bts#-1

BTSDS0=bts#-1-1 FEP=bts#-3 LINKSPEED=64
_________________________________________________
21. Add the MAWI. Command: ADD MAWI-bts#-1

MAWITYPE=mawi1x CARRIER=carrier#
PILOTBEACON=<cr> TCHCOUNT=24 PIPESIZE=<cr>
PBTSDS0=<cr>
_________________________________________________

Student Guide 5-9
CDMA SC™ 9600/4800/2400 BTS

Provisioning Hierarchy
Association Option From...
BTSLINK: Required if MDM has a spanline.
MDM: BDC provisioned only for CCP cage.
From CBSC From BTSLINK
BTS
Frame
RFDS CSM
MDM
RGLI
Sector
LPA
LCI Carrier BBX BBXR GLI
TCHWC MCC BDC MGLI
MCCCE
SCH
PCH
ACH

Module 6

This module will provide a description of MSC span and terrestrial circuits.
• Describe the purpose of MSC span and terrestrial circuit.
• Perform procedures to provision the MSC span and terrestrial

circuits.
• In compliance with instructor presentation and 1X Cellular




Student Guide 6-1
Acronym Definition
CBSC Centralized Base Station Controller
CIC Circuit Identity Code
MM Mobility Manager
MSC Mobile Switching Center
TERCKT Terrestrial Circuit
XC Transcoder Cabinet

6-2 Student Guide
Notes

Student Guide 6-3
MSC Span and Terrestrial Circuit
MSC Span • Span type
- T1
- E1
Terrestrial Circuit Traffic channels on the span that carry voice or data traffic between an
MSC and CBSC are termed terrestrial circuits (TERCKT).
When the amount of traffic required of the CBSC results in higher

desired blocking rates for terrestrial circuits during CBSC operation,
the number of terrestrial circuits must be increased.
System Setup • Install hardware as required:

Procedure
- XC frame and cage
- MSIP card
- DSW card
• Add device(s) to OMC-R database:
- MSIP port available
- MSIP slot available (If no open MSIP port)
• Add MSCSPAN
• Add TERCKTs:
- TDM ports available (One TDM port per TERCKT)
» T1 = 24
» E1 = 32
- PCM Number (0 - 2047)

6-4 Student Guide
Student Guide
MSC CBSC
XC
MSCSPAN-xc#-pcm# MSIP
MSCSPAN-xc#-pcm#
MSIP
MSCSPAN-xc#-pcm#
MSIP
MSCSPAN-xc#-pcm#
MSIP

Naming Convention
MSC-cbsc#-msc#
MSCSPAN-xc#-pcm# CBSC-cbsc#
MSCSPAN-xc#-pcm#
TERCKT-xc#-pcm#-timeslot#
TERCKT-xc#-pcm#-timeslot#
Ranges
cbsc# 1-8
6-5
OMCR100A
Circuit Identity Code
The Circuit Identity Code (CIC) parameter is passed between the MSC
and CBSC. The CIC identifies a particular span and timeslot pertaining
to a terrestrial circuit on the interconnecting MSC to CBSC spans.
The following information describes how the MSC and CBSC interpret
the CIC parameter as used by the A-link messages,
Assigment_Request/Block/Unblock/Reset/Reset_Ack etc.
IS-634 Revision A, Section 6.2.2.22 defines the CIC as a 16 bit number

which decodes as, CIC=<11 bit Span identifier> + <5 bit Timeslot
identifier>. The valid 5 bit timeslot identifier ranges from 0 - 31 for E1
and 0 - 23 for T1.
Domestic: - For T1 the timeslot TS=0 is a valid audio channel.
International: - An E1 span uses TS=0 for frame sync (i.e., timeslot 0)

is not a valid audio channel for E1. As a result, the MSC can align
directly with the CLI and XC databases.
A CIC needs to be set up on both the MM which is 1-based (timeslot

range 1 - 24) and the MSC which is 0-based (most T1 MSC vendors
cases use the timeslot range 0 - 23). To compensate for the offset, the
MM adds 1 to the CIC before it is sent to the XC.
CIC = (MSC_CKT/24 * 8) + MSC_CKT
XC Circuit (CCT_ID) = CIC+1
The following table illustrates how both sides should be set up for the
first six spans. Apply the same calculation for any MSC span.

6-6 Student Guide
Circuit Identity Code Setup on the MSC and MM
Student Guide
MSC IS-634A CBSC

BINARY DECODE MM XC
<SPAN#>+<TIMESLOT>
SPAN TIMESLOT MSC_CKT CIC (DECIMAL) START FINISH TERCKT(X=CBSC#) CCT_ID
0 0 - 23 0 - 23 0 - 23 Invalid MM cannot assign MSCSPAN0
1 0 - 23 24 - 47 32 - 55 100001 1 10111 terckt-x-1-[1 - 24] 33 - 56
2 0 - 23 48 - 71 64 - 87 10 00001 10 10111 terckt-x-2-[-1 - 24] 65 - 88
3 0 - 23 72 - 95 96 - 119 11 00001 11 10111 terckt-x-3-[-1 - 24] 97 - 120
4 0 - 23 96 - 119 128 - 151 100 00001 100 10111 terckt-x-4-[-1-24] 129 - 152
5 0 - 23 120 - 143 160 - 183 101 00001 101 10111 terckt-x-5-[-1 - 24] 161 - 184
6 0 - 23 144 - 167 192 - 215 110 00001 110 10111 terckt-x-6-[-1 - 24] 193 - 216
etc...

Circuit Identity Code
6-7
OMCR100A
Review Exercise
1. What is the purpose of a traffic channel?
2. What is the purpose of the CIC?
3. If the EMX sends CIC 34 in the A+ message for an assignment, what would be the XC CIC?

6-8 Student Guide
Lab Exercise 1 - Provision the MSC Span and Terrestrial Circuits
Lab Exercise 1 - Provision the MSC Span and

Terrestrial Circuits
Introduction This lab is to familiar you with the procedure to add the MSC span and
terrestrial circuits.
_________________________________________________
2. Determine the PCM number and span type of the new MSC
span. Command: DISPLAY CBSC-cbsc# SPANCONF
_________________________________________________
3. Determine the number of available TDM ports. Command:

DISPLAY XC-xc# TDMPORTS
_________________________________________________
4. Locate an open MSIP port in the XC. Command: DISPLAY

XC-xc# LINKCONF DEVICE=msip
_________________________________________________
NOTE
If insufficient number of TDM ports, refer to XC Port Growth
Procedure.
5. If no open MSIP ports are available, check for open slot suitable
for an MSIP (slots 6 through 17). If no slots available, XC cage
or frame growth is required. Add MSIP if required. Command:
ADD MSIP-xc#-xccage#-msipslot#
_________________________________________________

Student Guide 6-9
6. Add the MSC span. Command: ADD MSCSPAN-cbsc#-pcm#

SRCTERMDEV=xc#-2-msipslot# SRCTERMPORT=1
SPANTYPE=t1_1 SRCSPANEQ=t1_1 NUMTDMPORT=24
SUPPINFO=<cr>
_________________________________________________
7. Add two terrestrial circuits. Command: ADD TERCKT-xc#-

pcm#-timeslot#
_________________________________________________

Lab Exercise 2 - Cleanup the Database
Introduction This procedure covers the steps required to delete the database you
created for this course. For entire procedure to delete the database, refer
to Cellular System Administration document.
Directions 1. Delete two terrestrial circuits. Command: DELETE TERCKT-

xc#-pcm#-timeslot#
2. Delete the MSC span. Command: DELETE MSCSPAN-

cbsc#-pcm#
3. Delete the MAWI for SC300. Command: DELETE MAWI-

bts#-1
4. Delete the BTS link for SC300. Command: DELETE

BTSLINK-bts#-1
5. Delete the BTS span for SC300. Command: DELETE

BTSSPAN-bts#-1
6. Delete the SC300 BTS. Command: DELETE BTS-bts#
7. Delete the neighbor carriers for SC4812ET. Command:

DELETE TCARRIER-tcbsc#-tbts#-tsector#-tcarrier#
NEIGHBOR
8. Delete the SC4812T BTS. Command: DELETE BTS-bts#
9. Delete the inter CBSC link. Command: DELETE ICLINK-

cbsc#-ictrkgrp#-iclink#
10. Delete three MLS to PSI connections. Command: DELETE

MLS_PSI_CON-xc#-mls_psi_con#
11. Delete the PSI-SEL card (if added). Command: DELETE

PKTSEL-xc#-pktsel#
12. Delete the PSI-PCF card (if added). Command: DELETE

PKTPCF-xc#-pktpcf#
13. Delete two PSI-CE cards. Command: DELETE PKTIF-xc#-

pktif#

14. Delete three MSIP cards. Command: DELETE XC-xc#-

xccage#-msipslot#
15. Delete the service option. Command: DELETE SERVOPT-

cbsc#-33
16. Delete two C7 links. Command: DELETE C7LINK-cbsc#-1-1
17. Delete the inter CBSC trunk group. Command: DELETE

ICTRKGRP-cbsc#-ictrkgrp#
18. Delete the MLS to MM connection. Command: DELETE

MLS_MM_CON-cbsc#-mls_mm_con#
19. Delete the neighbor CBSC. Command: DELETE TCBSC-

tcbsc#
20. Delete the XC. Command: DELETE XC-xc# PLATFORM
21. Delete the CBSC. Command: DELETE CBSC-cbsc#

PLATFORM
22. Delete the Agnode span. Command: DELETE

AGNODE_SPAN-an#-agnode#-agnode_1
23. Delete the DACS. Command: DELETE DACS-dacs#
24. Delete the MLS to PDSN connection. Command: DELETE

MLS_PDSN_CON-an#-mls_pdsn_con#
25. Delete the PDSN cluster. Command: DELETE

PDSN_CLUSTER-pdsn_cluster#
26. Delete two FRSM cards. Command: DELETE FRCARD-an#-

agnode#-slot#
27. Delete two MLS to EDGERTR connections. Command:

DELETE MLS_EDGERTR_CON-an#-edgertr#-
mls_edgertr_con#
28. Delete two EDGERTR cards. Command: DELETE

EDGERTR-an#-edgertr#
29. Delete the Agnode. Command: DELETE AGNODE-an#-

agnode#

30. Delete four MLS links. Command: DELETE MLS_LINK-

an#-mlstrunk#-link#
31. Delete the MLS trunk. Command: DELETE MLS_TRUNK-

an#-mlstrunk#
32. Delete three MLS to OMC-IP connections. Command:

DELETE MLS_OMCIP_CON-omcip#-1
33. Delete two MLSs. Command: DELETE MLS-an#-mls#
34. Delete the AN. Command: DELETE AN-an#
35. Delete three OMC-IPs. Command: DELETE OMCIP-omcip#

Notes

SDU Database Administration
Student Guide
OMCR110A
General Release G 16.4
Software Release(s) 16.4
Hardware Release(s) 16.4
English
Revision History
Course Number OMCR110A
Document Title SDU Database Administration
Version The following table lists the document revision number, date and
Information remarks concerning the version.
Revision Date of
Remarks
Number Issue
1.0 08/02 Initial Release

1.1 09/02 Post-Alpha Test
1.2 10/02 Post-Beta Test Revisions
OMCR110A SDU Database Administration Revision 1.2 - 10/02

ii Student Guide
Copyright/Trademarks and Motorola are trademarks of Motorola, Inc.
Product and service names profiled herein are trademarks of Motorola,

Inc. Other manufactures’ products or services profiled herein may be
referred to by trademarks of their respective companies.
Disclaimer Motorola, Inc. Network Solutions Sector makes no warranties either

expressed or implied with regard to the information presented in the
course or in this training manual. The information presented in the
course and in this training manual is for educational purposes only, and
the appropriate field manual or appropriate Motorola representative
should be consulted for issues relating to the actual operation and
maintenance of the products described in the course or this training
manual.
Revision 1.2 - 10/02 SDU Database Administration OMCR110A

Student Guide iii
Acknowledgements The Technical Education and Documentation Department would like to
thank the following individuals for their support in the development of
this course:
• Brian Lehman
• Dave Hafferty
• Mike Jones
• Richa Tiwari
• Stephen Ehrlich

iv Student Guide
General Introductions
Important Information This information is provided to familiarize you with the facility and to
identify some useful additional information.
• Identification badges are required at all times
- Badges must be turned in every day after class
• Message numbers
- Contact: _____________________________
- Telephone Number: __________________

Student Guide v
Course Introduction
Audience This course is created for the following individuals:
• Technical support personnel responsible for performing basic

administration at the CBSC, OMC-R and OMC-IP. Personnel
include CDMA System Operators, Cellular Network
Administrators and System Administrators.
Course Description This course has been designed to help technical personnel create an
SDU in the OMC-R database.
Course Objective Upon completion of the course you will be able to:
• Create an SDU in the OMC-R database.
Course Length One day
Prerequisites The following training courses or knowledge is recommended:
• GNL132 - R16.1 Overview
• SDU100NE - SDU Network Elements
• OMCR100A - 1X Cellular Database Administration
Course Material The following material is needed to complete this course:
• SDU Database Administration Student Guide

vi Student Guide
Course Agenda Introduction to SDU............................................................1
Provision the SDU ..............................................................1

Student Guide vii
Safety
Safety issues must be addressed before going into the lab. Issues to be
covered include, but are not limited to:
• Identification of potential safety hazards
• Identification of the location of any lab power disconnect push-

buttons (if installed)
• Explanation of the Electro-Static Discharge (ESD) precautions
• Demonstrate placing the lab equipment in the proper standby

mode following lab completion
Live Circuits Only factory authorized service personnel or other qualified

maintenance personnel will:
• Remove equipment covers for internal subassembly or any

internal adjustments.
• Disconnect power and discharge circuits because dangerous

voltages exist even with power cable(s) removed.

viii Student Guide
Service and Anytime any work is to be accomplished inside the frame, two people
Adjustment should be present.
• Another person required for:
- Internal service
- Adjustment
• Person should be capable of:
- First Aid
- Resuscitation
Substitute Parts/ In order to minimize the danger of introducing any additional hazards:
Modify Equipment
• Do not install substitute parts
• Do not perform any unauthorized modification of equipment
Dangerous Procedure Read the text conventions in the manuals. They will represent four
Warnings levels of information as follows:
• NOTE (Written as text)

Presents additional helpful, non-critical information that you
can use.”
• IMPORTANT (Black box with an asterisk inside a triangle)

“Presents information to help you avoid an undesirable
situation or provide additional information to help you
understand a topic or concept.”
• CAUTION (Black box with a exclamation point inside a

triangle)
“Presents information to identify a situation where equipment
damage could occur and help you avoid damaging your
equipment.”
• WARNING (Black box with a lighting bolt inside a triangle)

“Presents information to warn of a potentially hazardous
situation where there is possibility of personal injury.”

Student Guide ix
General Introductions ...................................................................................................... v
Course Introduction ......................................................................................................... vi
Safety ............................................................................................................................... viii
Introduction to SDU
Introduction...................................................................................................................... 1 - 4
SDU Platform Hardware.................................................................................................. 1 - 6
OMC-R IP POOLS .......................................................................................................... 1 - 12
Review Questions: Introduction to SDU ......................................................................... 1 - 22
Lab 1: SDU Inventory Lab Exercise................................................................................ 1 - 24
Provision the SDU
Provision the SDU in the OMC-R Database Procedures................................................. 2 - 4

Add the SDU.................................................................................................................... 2 - 6
SDU to MLS Connections ............................................................................................... 2 - 10
SDU BPP Provisioning .................................................................................................... 2 - 12
SDU - MM Configuration................................................................................................ 2 - 14
Allocate SCTP Connection .............................................................................................. 2 - 17
Configure the PDSN cluster to SDU ............................................................................... 2 - 19
CUTOVER THE SDU..................................................................................................... 2 - 21
Generate SDU Datafiles................................................................................................... 2 - 22
SDU- MAC/IP Addressing

x Student Guide
Module 1
Introduction to SDU
This module will describe the Selection and Distribution Unit’s (SDU) core platform capabilities and its
hardware layout.
• Describe the functions of the Selection and Distribution Unit.
• Describe the hardware layout of the Selection and Distribution

Unit.
• Locate and describe the functions of SDU components.
• Identify SDU boards required for a full SDU configuration.
• In compliance with instructor presentation and the SDU

Materials required • SDU Database Administration Student Guide

Student Guide 1-1
Introduction to SDU
Acronym Definition
BPP Bearer Payload Processor
CCA Cabinet and Customer Alarm
GPS Global Positioning System
ISB Interface and Switch Board
IV-SHO Inter-Vendor Soft Handoff
MM Mobility Manager
PCF Packet Control Function

PSM Power Supply Module
RAN Radio Access Network
RNCS Radio Network Controller Server
SDU Selection and Distribution Unit
SPROC System Processor
UMTS Universal Mobile Telecommunications System
XC Transcoder

1-2 Student Guide
Notes

Student Guide 1-3
Introduction to SDU
Introduction
Core Platform The Selection and Distribution Unit (SDU) represents a new Motorola
Description RAN Network Element. The SDU performs reverse link selection and
forward link distribution operations for soft handoff, Layers 2 and 3
call processing functionality and packet data functions. Previously,
these functions were performed by different legacy subsystems within
the different product architectures.
The SDU platform provides a common base for implementation of the

SDU function in next generation infrastructures (CDMA 2000, UMTS
etc.) The SDU is the key element in the migration to an IP-based Radio
Access Network (RAN) enabling such benefits as greater system
capacity, interoperability and harmonization between different air
interfaces.
Rather than associating an SDU with a specific Mobility Manager

(MM)/Radio Network Controller Server (RNCS), SDUs can support
multiple call processing platforms in a many- to-many configuration.
This capability supports more efficient use of redundant capacity and
achieves higher service availability.
SDU Functions Specific functions performed by the SDU depend on the air interface
application. General SDU functions include supporting:
• The selection function for uplink packets and choosing the

appropriate legs of the “soft” connection with the mobile station
• Downlink distribution of the packet stream to each of the soft

handoff legs
• Asymmetric forward and reverse link allocation
• Termination of lower layer signalling with the mobile unit
• Termination of Packet Control Function (PCF) and data call

protocols
• Power control functions

1-4 Student Guide
Introduction
General SDU Functions Supported
• Selection function for uplink packets and

appropriate legs of the “soft” connection with
mobile station
• Downlink distribution of the packet stream to each

of the soft handoff legs
• Asymmetric forward and reverse link allocation
• Termination of lower layer signalling with the

mobile unit
• Termination of Packet control function (PCF) and

data call protocols
• Power control functions

Student Guide 1-5
Introduction to SDU
SDU Platform Hardware
Introduction The SDU is a single shelf platform, with no expansion shelves. It

contains 2N redundant System Processors (SPROCs), Interface Switch
Boards (ISBs), Cabinet and Customer Alarms (CCAs), Span I/Os,
Power Supply Modules (PSMs) and Bearer Payload Processors (BPPs).
Multiple pools of N+1 redundant payload cards performing different
functions (e.g. Selection/Distribution, Packet Control Function (PCF),
and/or A3/A7 interface) on a single shelf.
NOTE
The Site I/O board, which supports alarms and Global
Positioning System (GPS) is not redundant.
NOTE
SDU hardware is depicted on the following page.
Description The SDU Shelf is based on a Hub-star switch transport system. It

provides connectivity between system processors, network interfaces
and the payload cards.
Hardware components comprising the SDU platform include:
• System Processor (SPROC): Supports O&M and centralized

call processing activities in the SDU.
• Interface Switch Board (ISB): Implements the HUB connecting

the SPROC, network Interface and all payload cards.
• Bearer Payload Card (BPP): Is a multipurpose processor card

supporting SDF or PCF applications.

1-6 Student Guide
SDU Hardware

Student Guide 1-7
Introduction to SDU
• Cabinet and Customer Alarms (CCA): A payload card that

provides the capability of interfacing with external I/O such as
customer defined alarms, along with monitoring internal alarms
such as fan and power supply alarms
• SITE I/O: Provides the interface to/from the customer and cage
alarm
• SPAN I/O: Supports network interfaces connected to the Access

Network
• Backplane: Supports the card inter-connectivity for a single

SDU card cage
• Main Card Cage: Provides front side access to the 15 BPPs, two
Interface and Switch Boards (ISB)/SPROCs, and two CCAs
• I/O Card Cage: Houses the two Span I/O cards and the Site I/O
card
• Power Supply Module (PSM): Provides cage level input power

conversion for distribution throughput an individual SDU cage
• Power Distribution Equipment: Consists of a: PSM cage

housing the PSMs, a Main Circuit Breaker Panel and circuit
Breaker Module between the PSMs and the Backplane power
regions
• Frame: Provides housing for up to two SDU shelves
Main Card Cage The main card cage features 19 card slots.
• Fifteen standard width slots house BPP cards.
• Two standard width slots are dedicated to CCA cards.
• Two wider slots hold the ISB/SPROC cards.
The card organization is shown in the graphic on the following page.

1-8 Student Guide
Cabinet with Power Supply & Card Cage
Power Supply
ISB/SPROC
ISB/SPROC
BPP
BPP
BPP
BPP
BPP
BPP
BPP
BPP
BPP
BPP
BPP
BPP
BPP
BPP
BPP
CC
CC
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
20 mm 45 mm
Cards in Main Card Cage

Student Guide 1-9
Introduction to SDU
SDU Interfaces • CP1
- Interface from ISB to AN
- 1000bT (gigabit) Switched Ethernet Interface.
• CP2
- Interface to CCAs and BPPs
- Circuit switched interface for legacy equipment (not

implemented in SDU)
- 100 Mb Switched Ethernet Packet Interface.
• CP5:
- ISB-to-ISB Timing reference
- 100Mb Switched Ethernet Packet Interface
• CP8
- Interface from ISB to SPROCs
- 100 Mb Switched Ethernet Packet interface
• CP9
- Interface from ISB to ISB
- 100 Mb Switched Ethernet packet interface

SDU Shelf Architecture
Introduction to SDU
OMC-R IP POOLS
Introduction The OMC-R manages most of the IP allocation within the RAN. The
OMC-R IPPOOLs are set up during system configuration (16 and 16.1
installs) and should be set correctly from the IP planning done before
the configuration of the system.
OMC-R IPPOOLs The OMC-R manages four IPPOOLs (one IPPOOL optional). The
CBSC POOL holds the IP addresses of the OMC-R, any local
OMCIPs, the CBSCs (MMs and XCs), PSI cards of the XC, SDU
SPROCs and the BPPS. The AN POOL holds the IP address of the
MLSs, AGNODEs and EDGERTRs. The BTS POOL hold the IP
address of the BTSs. The PCF POOL is optional and hold the PCF IP
address of the XC PCF PSI cards. The COMMON POOL hold the IP
addresses for the MLS to SDU (ISB) links.
SDU and CBSC POOL When an SDU is added in the OMC-R database it will extract 512 IP
addresses from the CBSC POOL. Consider this when adding the SDU
or multiple SDUs in the OMC-R database.
SDU and the PCF If the PCF POOL is used, each SDU will extract 64 IP addresses from
POOL the PCF POOL and four IP addresses for the SPROCs.
SDU and the Each SDU will pull 16 IP addresses from the COMMON POOL.
COMMON POOL

Student Guide
OMCR IPPOOLs
omcr3-000040 > display omcr-3 ippool
000040-00002 COMMAND ACCEPTED
CLICMD-29191 02-09-23 13:45:53 omcr3 OMCR-3 M000040.00002 002390/002919

INFO:1 “Command Received and Accepted”
COMMAND=”DISPLAY OMCR-3 IPPOOL “
[29192:New Connection (omcr3,IT_daemon,*,root,pid=657,optimised) ]
[29192:New IIOP Connection (omcr3:2623) ]
DISPLAY OMCR IPPOOL:
AN DEVICE |POOL TYPE| IPPOOL | START IP | NETMASK |POOLCONFIG

(AN-an#) | |(IPPOOL-an#-pooltype#-pool#)| | |
----------------|---------|----------------------------|----------------|----------------|----------
AN-1 CBSC IPPOOL-1-1-1 10.200.64.0 255.255.192.0 CURRENT
AN IPPOOL-1-2-1 10.200.0.0 255.255.252.0 CURRENT
BTS IPPOOL-1-3-1 10.200.128.0 255.255.240.0 CURRENT
PCF IPPOOL-1-4-1 10.200.192.0 255.255.240.0 CURRENT
COMMON IPPOOL-1-5-1 10.200.224.0 255.255.255.0 CURRENT

INFO:4 “Command Successfully Completed”
REASON_CODE="No Reason"
OMC-R IP POOLS
OMCR110A
1 - 13
Introduction to SDU
IP Pool Hosts • The CBSC pool has 16384 hosts (possible)
• The AN pool has 1024 hosts (possible)
• The BTS pool has 4096 hosts (possible)
• The PCF pool has 4096 hosts (possible)
• The COMMON pool has 255 hosts (possible)

IP Pool Hosts
Student Guide
• The CBSC pool has 16384 hosts (possible)
• The AN pool has 1024 hosts (possible)
• The BTS pool has 4096 hosts (possible)

• The PCF pool has 4096 hosts (possible)
• The COMMON pool has 255 hosts (possible)
OMC-R IP POOLS
OMCR110A
1 - 15
Introduction to SDU
Checking Available IP To check the available IP space to add the SDU run the CLI command
Space DISPLAY OMC-3 FREESUBNETS this will show the available IP
address in the IP POOLs
Look for the following for each SDU to provision
• 512 from the CBSC POOL
- 255.255.252.0
- /23
• 64 from the PCF POOL
- 255.255.255.192
- /26
- 255.255.255.252
- /30
• 16 from the COMMON POOL
- 255.255.255.240
- /28

OMC-R IP POOLS
OMCR-3 FREESUBNET
omcr3-000040 > display omcr-3 freesubnets

| POOL | IPPOOL | POOL |

AN | TYPE |(an#-pooltype#-pool#)| CONFIG | FREE SUBNET
--------|------|---------------------|--------|----------------
AN-1 CBSC IPPOOL-1-1-1 CURRENT 10.200.64.48/
255.255.255.240
10.200.64.64/
255.255.255.192
10.200.74.0/
255.255.254.0
10.200.76.0/
255.255.254.0
10.200.86.0/
255.255.254.0
10.200.91.128/
255.255.255.128
AN IPPOOL-1-2-1 CURRENT 10.200.0.58/

255.255.255.254
10.200.0.60/
255.255.255.252
10.200.0.64/
255.255.255.192
10.200.0.128/
255.255.255.128
255.255.254.0
BTS IPPOOL-1-3-1 CURRENT 10.200.129.7/
255.255.255.255
PCF IPPOOL-1-4-1 CURRENT 10.200.192.0/

255.255.255.192
COMMON IPPOOL-1-5-1 CURRENT 10.200.224.23/

255.255.255.255
10.200.224.24/
255.255.255.248
10.200.224.32/
255.255.255.248
10.200.224.56/
255.255.255.248

Introduction to SDU
SDU IP Addresses To check the existing SDUs or newly added SDU IP address assigned.
Rn the DISPLAY SDU-x IPADDRESS

SDU IP ADRESSES
Student Guide
omcr3-000040 > display sdu-2 ipaddress

[266:New Connection (omcr3,IT_daemon,*,root,pid=657,optimised) ]
[266:New IIOP Connection (omcr3:2623) ]

INFO:1 "Command Received and Accepted"

COMMAND="DISPLAY SDU-2 IPADDRESS "
DISPLAY SDU-2 IPADDRESS:
DEVICE | IPADDRESS | NETMASK | FUNCTION

-------------------------|----------------|----------------|---------------
SDU-2 EXTERNAL SUBNET 10.200.72.0 255.255.254.0 -
SDU-2 PCF SUBNET - - -
SDU-2 MANAGEMENT_LINK 10.200.72.1 255.255.255.252 -
SDU-2 ROUTER1 10.200.72.5 255.255.255.252 -
SDU-2 ROUTER2 10.200.72.9 255.255.255.252 -
SDUBPP-2-1-3 BCP 10.200.73.1 255.255.255.252 SDF-2-1-1
SDUBPP-2-1-3 CPE 10.200.72.17 255.255.255.240 -
SDUBPP-2-1-4 BCP 10.200.73.5 255.255.255.252 PCF-2-1-1
SDUBPP-2-1-4 CPE 10.200.72.33 255.255.255.240 -
SDULANPORT-2-1 10.200.224.1 255.255.255.252 -
SDULANPORT-2-2 10.200.224.5 255.255.255.252 -
SDULANPORT-2-3 10.200.224.9 255.255.255.252 -
OMC-R IP POOLS
SDULANPORT-2-4 10.200.224.13 255.255.255.252 -
OMCR110A

INFO:4 "Command Successfully Completed"
1 - 19
REASON_CODE="No Reason”
Introduction to SDU
SDUSDFPOOL and Since the SDU to MM is a many to many relationship, you can put as
SDUPCFPOOL many SDUs under the omcr as you want (within reason).
. Each SDU will have its own parameters which need to be added. The
tricky part is to assign the MM (CBSCs) or MMs the resources to that
SDU or SDUs. This is done via SDUPCFPOOLs and
SDUSDFPOOLs these are separate from the SDU its self.
Many SDUs can be assigned to one or more Pools. For example, SDU-
1 may be assigned to SDFPCFPOOL-1 or SDFPCFPOOL-2; or SDU-1
and SDU-2 maybe assigned to SDUPCFPOOL-1 or both
SDFPCFPOOL-1 and SDFPCFPOOL-2.
MMs (CBSC) can only be assigned to one pool. (e.g., CBSC-1 can be
assigned the SDFPCFPOOL-1 but not SDFPCFPOOL-2 or
SDFPCFPOOL-2 and not SDFPCFPOOL-1). Use the following
commands to add, modify and verify the pools.
Command: ADD SDUPCFPOOL-sdupcfpool#.

Command: EDIT CBSC-cbsc# PCFPOOL PCFPOOL= pcfpool#.
Command: EDIT SDU-sdu# PCFPOOLCONF PCFPOOL=pcfpool#.
Command: DISPLAY SDU-sdu# PCFPOOLCONF
Command: DISPLAY CBSC-cbsc# PCFPOOL
Command: DISPLAY OMC-R- OMC-R# PCFPOOLINFO.
Command: ADD SDUSDFPOOL-sdusdfpool#
Command: EDIT CBSC-cbsc# SDFPOOL SDFPOOL= sdfpool#
Command: EDIT SDU-sdu# SDFPOOLCONF SDFPOOL=sdfpool#
Command: DISPLAY SDUSDFPOOL-sdusdfpool# SDFPOOLINFO
Command: DISPLAY SDU-sdu# SDFPOOLCONF Command:
Command DISPLAY SDUPCFPOOL-pcfpool# PCFPOOLINFO
Depending on plans for new SDUs, MM RA links may have to be

moved or added. Use the following command.
Command: ADD SDULINK-sdu#-cbsc# PCFRALINK=YES

SDFRALINK=YES
Command: ADD MMPCFRALINK-sdu#-cbsc#-1
Command: DISPLAY SDU-sdu# STATUS.
Command: ADD MMSDFRALINK-sdu#-cbsc#-1
Command: DISPLAY SDULINK-sdu#-cbsc-# STATUS.
Command: DISPLAY MMSDFRALINK-sdu#-cbsc#-1
MMSDFRALINKCONF
Command: DISPLAY MMSDFRALINK-sdu#-cbsc#-1 STATUS 7.
Command: DISPLAY MMPCFRALINK-sdu#-cbsc#-1
MMPCFRALINKCONF
Command: DISPLAY MMPCFRALINK-sdu#-cbsc#-1 STATUS

OMC-R IP POOLS
The SDUSDFPOOL and SDUPCFPOOL
SDUSDFPOOL1
SDU1
MM1
SDUPCFPOOL1
SDU2
SDUSDFPOOL2
MM2
SDUPCFPOOL2
SDU3
SDUSDFPOOL3
MM3 SDU4
SDUPCFPOOL3
SDUSDFPOOL4
SDU5
MM4
SDUPCFPOOL4

Introduction to SDU
Review Questions: Introduction to SDU
1. List the main functions of SDU.
2. List the main functions of following cards in SDU:
CCA:
ISB:
SPROC:
BPP:
3. List the types of redundancy for the following cards of SDU
CCA:
ISB:

Review Questions: Introduction to SDU
SPROC:
BPP:

Introduction to SDU
Lab 1: SDU Inventory Lab Exercise
Directions Accomplish the follow Inventory Lab.
1. In the following graphic, fill the names of the different cards that need to be installed.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
20 mm 45 mm
2. In the table on the following page, enter the type of board currently in the system (TIPS Lab) for SDU
and the type of board required to match a fully equipped SDU configuration.

Lab 1: SDU Inventory Lab Exercise
Slot No. Board in Fully Equipped SDU Current Board (TIPS Lab)
Configuration
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19

Introduction to SDU
Notes

Module 2
Provision the SDU

This module will describe the process to provision an SDU in the OMC-R database.
• Perform procedures to provision the SDU in the OMC-R

database.
• In compliance with instructor presentation and the SDU

Materials required • SDU Database Administration Student Guide

Student Guide 2-1
Provision the SDU
Acronym Definition
OMC-R Operation and Maintenance Center - Radio
SDU Selection and Distribution Unit

2-2 Student Guide
Notes

Student Guide 2-3
Provision the SDU
Provision the SDU in the OMC-R Database

Procedures
Introduction This procedure describes the steps required to setup an SDU platform
for the first time. The outcome of this procedure is O & M
communication with the OMC-R.
NOTE
This procedure assumes that the OMC-R has already been
upgraded to R16.1 or above.
Directions Perform the following actions. Use the space provided to record device
parameters.
Login and Open UNO Use the following procedure to login, open UNO and access the alarm
manager window and CLI platform.
NOTE
The Instructor will provide the user name and password.
1. Log into UNO from an xterminal by entering a valid user name

and password.
2. Open a terminal window by using the mouse and pull down

menu. For example, click the right mouse button and select
Programs >> Terminal.
3. Telnet (or login) to the OMC-R and login.

2-4 Student Guide
Provision the SDU in the OMC-R Database Procedures
Procedure Flow

Student Guide 2-5
Provision the SDU
Add the SDU
parameters.
1. Open the CLI window, record the process used to open the window. Command: Type CLI at the
OMC-R prompt.
2. Determine the Access Network that the SDU will be connected to, and make sure that SDU subnet
can still be allocated from the AN. Command: DISPLAY AN FREESUBNET.
NOTE
Given the AN #, the display output shows a set of free
subnets under the AN. A subnet will be allocated from the
CBSC IP POOL under the AN to the SDU. The SDU platform
requires 1 subnet of netmask /23 and 4 subnets of netmask
/30. Make sure that the display output indicates that such
subnets are available under the implied AN.
3. Provision the SDU data into the OMC-R. Command: ADD SDU- sdu# PLATFORM
ACCESSNETWORK= an#
NOTE
As part of the ADD SDU, a set of devices will be
automatically created in the MIB, such as SDUSPROC,
SDUISB, SDUCCA, SDUPSMDCDC, SDUFANTRY etc.

2-6 Student Guide
Add the SDU
4. Verify the devices which were created as part of the ADD SDU command. Command: DISPLAY
SDU-sdu# BOARDCONF.
NOTE
The display output shows all the SDU boards in the OMC-
R/MIB database.
5. Verify the SDU’s IP address. Command: DISPLAY SDU- sdu# IPADDRESS.
NOTE
The ADD SDU command will allocate a subnet for the SDU.
The display output shows all the IP addresses that have
been allocated to the SDU devices.
6. Display SDU status. Command: DISPLAY SDU- sdu# STATUS.

Student Guide 2-7
Provision the SDU
Notes

2-8 Student Guide
Add the SDU
SDU TO MLS Connections

Student Guide 2-9
Provision the SDU
SDU to MLS Connections
Introduction The following commands will provision the physical links between an
SDU and MLS. It will assign all the LAN connection information. The
link speed is 1G. Ensure the modules on the MLS are the 16 port Gbit
modules.
parameters.
1. Provision the connection between the SDU and the Access Network.Command: ADD
MLS_SDU_CON-sdu#-2 MLS1=an#-mls1 sMLS1MODULE =module1# MLS1PORT=port#1
MLS2=an#-mls2# MLS2MODULE= module2# MLS2PORT=port#2
2. Provision the connection between the SDU and the Access Network.Command: ADD
MLS_SDU_CON-sdu#-18 MLS1=an#-mls1 sMLS1MODULE =module1#
MLS1PORT=port#1 MLS2=an#-mls2# MLS2MODULE= module2# MLS2PORT=port#2
3. Record the OMC-R Pseudo IP address. Command: DISPLAY MLS_SDU_CON-SDU#-2

CONCONF.
4. Record the OMC-R Pseudo IP address. Command: DISPLAY MLS_SDU_CON-SDU#-18

CONCONF.

SDU to MLS Connections
5. Record the SDU Pseudo IP address. Command: DISPLAY SDU-sdu# IPADDRESS.
NOTE
The SDU Pseudo IP address is indicated by the row
marked with SDU MANAGEMENTLINK.
6. Display SDU LAN Port configuration. Command: DISPLAY SDU-sdu# LANPORTCONF.

Provision the SDU
SDU BPP Provisioning
Introduction The following commands will provision the BPP cards and assign their
function to them and allocate IP address for them.
parameters.
1. Add SDU BPP card and assign the functionality as “SDF”. Command: ADD SDUBPP -sdu#-1-
sdubpp1# FUNCTION=SDF-sdu#-1-sdf# USERNAME=sdf
NOTE
If the BPP is configured as ‘SDF”, it can be used for voice
calls.
2. Add SDU BPP card and assign the functionality as “PCF”. Command: ADD SDUBPP -sdu#-1-
sdubpp2# FUNCTION=PCF-sdu#-1-sdf# USERNAME=pcf
NOTE
If the BPP is configured as ‘PCF” it can be used for packet
calls only. It is either “sdf” or “pcf” depending on which
functionality the BPP is configured for.
3. Display SDU PCF management Parameters. Command: DISPLAY SDU-sdu#

PCFMGMTPARMS1
4. Command: DISPLAY SDU-sdu# PCFMGMTPARMS2.

SDU BPP Provisioning
5. Command: DISPLAY SDU-sdu# SDFMGMT.
6. Command: DISPLAY SDUPCF-sdu#-1 PCFCPPARMS1
7. Command: DISPLAY SDUPCF-sdu#-1 PCFCPPARMS2
8. Command: DISPLAY SDUPCF-sdu#-1 PCFBEARER

Provision the SDU
SDU - MM Configuration
The following commands will provision the resource management

between the MM and SDU. These commands will assign the multicast
IP address for the resource management and will create the resource
pools with the multicast transmit and receive address.
parameters.
1. Command: ADD SDUPCFPOOL-sdupcfpool#.
2. Command: EDIT CBSC-cbsc# PCFPOOL PCFPOOL= pcfpool#.
NOTE
This command will associate the MMs with the pool.
3. Command: EDIT SDU-sdu# PCFPOOLCONF PCFPOOL=pcfpool#.
NOTE
This command will associate the SDU with the pool.
4. Command: DISPLAY SDUPCFPOOL-pcfpool# PCFPOOLINFO

SDU - MM Configuration
5. Command: DISPLAY SDU-sdu# PCFPOOLCONF
6. Command: DISPLAY CBSC-cbsc# PCFPOOL
7. Command: DISPLAY OMC-R- OMC-R# PCFPOOLINFO.
8. Command: ADD SDUSDFPOOL-sdusdfpool#
9. Command: EDIT CBSC-cbsc# SDFPOOL SDFPOOL= sdfpool#
10. Command: EDIT SDU-sdu# SDFPOOLCONF SDFPOOL=sdfpool#
11. Command: DISPLAY SDUSDFPOOL-sdusdfpool# SDFPOOLINFO
12. Command: DISPLAY SDU-sdu# SDFPOOLCONF

Provision the SDU
13. Command: DISPLAY CBSC-cbsc# SDFPOOL.
14. Command: DISPLAY OMC-R-OMC-R# SDFPOOLINFO

Allocate SCTP Connection
Allocate SCTP Connection
Introduction After the BPPs are added, the link between the SDU and the MM has to
be provisioned. The link is required for resource allocation between the
MM and the SDU for both voice and data calls. The logical link
between the SDU and the CBSC is represented by “SDULINK”. Each
SDULINK may contain one MMPCFRALINK (MM resource
allocation link for packet calls) and one MMSDFRALINK (MM
resource allocation link for voice calls.) The SDULINK can be
provisioned for either one of them or both. This is the MM to PCF and
SDF resource allocate SCTP connection. The SDU will have the MM
IP address.
parameters.
1. Command: ADD SDULINK-sdu#-cbsc# PCFRALINK=YES SDFRALINK=YES
2. Command: ADD MMPCFRALINK-sdu#-cbsc#-1
3. Command: ADD MMSDFRALINK-sdu#-cbsc#-1
4. Command: DISPLAY SDU-sdu# STATUS.
5. Command: DISPLAY SDULINK-sdu#-cbsc-# STATUS.

Provision the SDU
6. Command: DISPLAY MMSDFRALINK-sdu#-cbsc#-1 MMSDFRALINKCONF
7. Command: DISPLAY MMSDFRALINK-sdu#-cbsc#-1 STATUS
8. Command: DISPLAY MMPCFRALINK-sdu#-cbsc#-1 MMPCFRALINKCONF
9. Command: DISPLAY MMPCFRALINK-sdu#-cbsc#-1 STATUS

Configure the PDSN cluster to SDU
Configure the PDSN cluster to SDU
Introduction The following commands will provision the SDUPDSNCLUSTER.

The SDUPDSNCLUSTER object is a duplicate of the existing
PDSN_CLUSTER. The CLUSTERID specified indicate ID of the
PDSN_CLUSTER, SDUPDSNLINK may be provisioned as part of the
SDUPDSNCLUSTER provisioning if the PDSN_CLUSTER IP
address list is populated link between the SDU and a PDSN.
The PDSNCLUSTER has to be added only if any PCFRALINK is

added as SDULINK in the previous step, or if the PDSNCLUSTER
doesn’t already exist.
parameters.
1. Command: ADD SDUPDSNCLUSTER-sdu# -sdupdsncluster# CLUSTERID= pdsncluster#
NOTE
ClusterID is the ID of existing PDSN_cluster.
2. Command: DISPLAY SDUPDSNCLUSTER-sdu# -sdupdsncluster# PDSNCLUSTERCONF
3. Command: DISPLAY SDUPDSNCLUSTER-sdu# -sdupdsncluster# PDSNLINKCONF.
4. Command: DISPLAY SDUPDSNCLUSTER-sdu# -sdupdsncluster# STATUS

Provision the SDU
5. Command: DISPLAY OMC-R-OMC-R# SDFQRPT
6. Command: DISPALY OMC-R-OMC-R# SDFCPPPARMS1
7. Command: ADD CBSC-cbsc# PLATFORM.
NOTE
This command is used to assign the SDUSDF to the MM.
8. Command: DISPLAY CBSC-cbsc# SDFPARMS
9. Command: EDIT CBSC -cbsc# SDFPARMS SELLOCATION OVERIDE=sdusdf#.

CUTOVER THE SDU
CUTOVER THE SDU
parameters.
1. Command: CUTOVER SDU-sdu#
2. Command: DISPLAY SDU-sdu# STATUS.
NOTE
This command displays the status of all the devices and
their current states. Verify that all devices that have been
added in the previous steps are listed in the status table.
Please ensure that the status of all the cards and links will
be in UNLOCKED/DISABLED state, except the SDU itself,
which will be in LOCKED/DISABLE state.

Provision the SDU
Generate SDU Datafiles
Introduction Use the following commands to update the SDU software load in the
OMC-R database.
parameters.
1. Command: EDIT SDU-sdu# COMMITEDVERSION VERSION= \”Active Version\”.
NOTE
The SDU software version to be loaded is Active Version
2. Command: DISPLAY SDU-sdu# VERSION
3. Command: GENERATE SDU-sdu# DATAFILES LOAD=ALL VERSION= \”Active version\”.
4. Command: GENERATE AN-an# DATAFILES.

Appendix A
MAC Address The following lists the MAC address format for the SDU entities.I/G
and U/L bits for individual/group and global/local indications. I/G bit
indicates either individual host or broadcast address, and U/L bit is set
as “global” to indicate that it is a globally administered address.
The hardware ID (HID) field is filled in during the production cycle,

and thus it is a static field. The actual assignment of values in this field
is outside the scope of this document. However, it should be noted that,
on all devices that uses Porsche switch (i.e. ISB and BPP), the least
significant 5 bits of the MAC address is automatically determined and
assigned by the Porsche switch due to its specification. Therefore, these
devices can have up to 32 (2^^5) MAC addresses per board maximum.
The EID in each board contains the tuple that defines the base MAC
address and the address mask, which defines the range of MAC address
a given board is allocated with.
Bit
# Bit Field Note
Position
47 1 I/G Individual/Group. Set as individual >
(“0”) for individual host, and group
(“1“) for broadcast address.
46 1 U/L Global/Local (whether MAC address is

globally or locally administered). It is
set as “global” (“0“)
45 - 0 46 HID45 - HID0 Hardware ID (factory assigned)
IP Addressing There are two categories of IP address based on their usage, scope of
Overview traffic, and communication purpose.
• Internal/External IP address
• Physical/Logical IP address

Student Guide A-1
With this combination, there can be 4 different types of IP addresses as

shown below. The following sections describes them in detail. Not all
nodes are equipped with all of these address types. Due to the
functionalities of each entities, only the necessary address type is
assigned to each SDU entity.
Address
SDU Internal Address SDU External Address
Type
Physical Address Internal-Physical Address External-Physical Address
(e.g. CP2 or CP8 links) (e.g. Gbit Ethernet Port on ISB)
Logical Address Internal-Logical Address External -Logical Address

(e.g. SPROC Site Master) (e.g. OMC Agent)
SDU Internal Address SDU internal addresses are used for SDU internal communication only.
The primary purpose of the internal communication is for messaging
that is closed within the SDU, such as initialization, FM and CM
functionalities (e.g. sanity checking, checkpointing between redundant
peer entities, and among hierarchical entities). Due to the nature of
these messages, this type of traffic does not go outside of the SDU.
SDU External SDU external IP address is an externally visible address from outside
Address of the SDU. They are used for communications between SDU and other
network entities in the RAN, such as OMCR, MM, PDSN, BTS, etc.
This type of traffic includes bearer traffic, call processing messages,
O&M between OMCR and SDU (e.g. code download from OMCR),
etc.
Physical Address A physical IP address is assigned to each physical port. These

addresses are always associated with the same card/port. The ability of
an application to communicate using a physical address is dependent
on the state of the port. If a port is up, an application can use the
assigned physical IP address for communication. If a port is down, an
application can not use the assigned IP address for communication.
Hence, an application use of a physical address does not support
redundancy.
Logical Address There are two types of logical address.
• Location dependent logical address

A-2 Student Guide
• Location independent logical address
Location Dependent A location dependent logical IP address identifies each device

Logical Address separately from any of its physical ports. A location dependent logical
IP address is permanently assigned to each specific card. These
addresses are always associated with an internal “Pseudo Port” that is
“never down” or a Porsche chip routing domain that is strictly internal
to the card (e.g. ISB or BPP). They are not associated with any physical
port between the card and the rest of the network. Applications bound
to location dependent logical IP addresses communicate over one of the
physical ports via a path determined by a routing protocol. The ability
of an application to communicate using a logical IP address is
independent of the state of any physical ports (as long as at least one
physical port is usable). However, each location dependent logical IP
address is assigned to a specific card and can not be moved to another
card.
Location Independent A logical IP address identifies an active device from a redundant device
Logical Address pair (or device group). A location independent logical IP address is
assigned to an application that performs a specific function
independently of the card where it resides. These addresses are
assigned only temporarily to a specific card where the function resides
at the moment. Similar to a location dependent logical address, these
addresses are always associated with an internal “Pseudo Port” that is
“never down” or a Porsche chip routing domain that is strictly internal
to the card (e.g. ISB or BPP). They are not associated with any physical
port between the card and the rest of the network. The ability of an
application to communicate using a location independent logical IP
address is independent of the state of both the physical card and all
ports on that card (as long as at least one appropriate physical card and
one port on that card are available).
IP Address Allocation All IP addresses assigned to the SDU entities use the private IP address
space as specified in RFC1918, which consists of the following.
• 10.0.0.0/8 (i.e. 10.0.0.0 - 10.255.255.255, equivalent to class A

block)
• 172.16.0.0/12 (i.e. 172.16.0.0 - 172.31.255.255, equivalent to

16 contiguous class B blocks)
• 192.168.0.0/16 (i.e. 192.168.0.0 - 192.168.255.255, equivalent

to 256 contiguous class C blocks)

Student Guide A-3
The first type is planned to be used for the SDU external IP address
(RAN). The second type is used by the HAP platform for the SDU
internal IP address. For the HAP platform, the use of the second
address range is fixed and the address space 172.31.x.x must be
avoided in assigning external addresses. For external addresses, this is only
a recommended assignment. The actual address assignment is not limited to this
particular arrangement.
Internal IP Address The following diagram shows the internal IP address format. Notice
that four different formats exist with different length of subnet masks.
This definition is based on the HAP internal network layout. According
to their definition, the first format is defined as the physical address,
and the rest as logical address. Their formats are simply referred with
format numbers.
The four formats are generally classified as follows:
• Format 1: IP address for physical ethernet interfaces within the

SDU internal network, such as CP2, CP8, and CP9 links.
• Format 2: Location independent logical IP address related to the

ISB CPE Enhancer board (ICE) and BPP entities.
• Format 3: Location dependent/independent logical IP address

(except ICE, BPP related entities).
• Format 4: Location dependent logical IP address for BCP front

panel subnet.
The subnet masks for the first, second, third, and fourth format are the
uppermost 26 bits (i.e. FFFFFFC0h), 27 bits (i.e. FFFFFFE0h), 29 bits
(i.e. FFFFFFF8h), and 30 bits (i.e. FFFFFFFCh), respectively. Notice
that the ICE is ATM IWF related function, and is a product specific
functionality. Therefore, it is not a part of the core network. However, it
is still a part of the HAP definition, and thus it is included here for the
sake of completeness.

A-4 Student Guide
Internal IP Address Format
Student Guide
Host Addr
Network Addr (26 Bits)
Internal 31 24 16 8 6 5 (6 Bits) 0
Address
Format-1
(Physical Addr) Network Network RL Subnet-1 R R Host
Subnet-2
Host Addr
Internal Network Addr (27 Bits)
Address (5 Bits)
31 24 16 8 5 4 0
Format-2
Logical Addr, ICE/
BPP-CPE Related Network Network RL Subnet-1 R Host
Subnet-2
Host Addr
(3 Bits)
Address 31 24 16 8 3 2 0
Format-3
Logical Addr, Non-
ICE/BPP-CPE Re- Network Network RL Subnet-1 R Subnet-2 Host
lated
Host Addr
(2Bits)
Address 31 24 16 8 21 0
Format-4
Logical Addr,
BPP Front Panel Network Network RL Subnet-1 R Subnet-2 Host
OMCR110A
A-5
Internal IP Address Bit Mapping
Octet Bit Position # Bit Value Description

1 31-24 8 172 Network Addr
3 15 1 0 Reserved
3 14 1 0/1 Physical/Logical Indicator
3 13-9 5 0-31 Subnet Addr-1
3 8 1 0 Reserved
4 7-6 (format 1) 2 0-3 Subnet Addr -2

7-5 (format 2) 3 0-7
7-3 (format 3) 5 0-31
7-2 (format 4) 6 0-63
Internal IP Address Bit Mapping
Octet Bit Position # Bit Value Description

4 5 1 0 Reserved
4 4 - 0 (format 1) 5 1-30 Host Field

4- - 0 (format 2) 5 1030
2 - 0 (format 3) 3 1-6
1 - 0 (format 4) 2 1-2
Internal Physical IP The following table shows the bit mapping of the subnet and host fields
Address Format for the internal location dependent logical IP address. The “m” value in
the subnet is based on either left/right hand ISB.

A-6 Student Guide
Subnet Host Field Definition (Internal Physics)
Physical/
Address
Logical Subnet Field 1 Subnet Field 2 Host Field
Format
Indicator
1 0 m0000: SPROC Subnet 00: CP8 link 00001: ISB
(CP8 links and LMT ports) 00010, 00011: SPROC
LMT port 00001: LMT
00010 - 11110: external
devices
1 0 00001: CP9;link within the 00: CP9 link 0001, 00010: isb
cage
1 0 m0010: ISB Payload 00: in- shelf payload 00001 - 11110: payload,
Subnet ISB
The following table shows the bit mapping of the subnet and host fields
for the internal location dependent logical IP address.
For SPROCs, BPPs, and CCAs, the internal location dependent logical
address will also be used as the OSPF router ID. For the detail
discussion of the OSPF router ID, refer to the OSPF section later in this
chapter. Also, the “slot ID” in the subnet2 field represented by “zzzzz”
indicates the slot number in which the payload card is physically
located in the cage.
The “m” value in the subnet1 is based on either left/right hand ISB.
Also the “yyyyy” field that is concatenated in the bits in Subnet fields 1
and 2 indicates the slot number in which the payload card is physically
located in the cage.
The address defined by the first row is used only for the BPP CPE
Subnet addresses. The third row definition is used for the generic
payload BCP address for both BPP and CCA. The fourth row definition
is for the BPP front panel Subnet for LMT access.

Student Guide A-7
Subnet/Host Field Definition (Internal Location Dependent Logical)
Physical/
Address
Logical Subnet Field 1 Subnet Field 2 Host Field
Format
Indicator
2 1 1yy10: Slot ID - 1 yyy: Slot ID - 2 00001-11110:
E host
3 1 m0000:SPROC/ISB address 00000: SPROC 001: SPROC

00001: ISB BCP BCP
processor 001: ISB BCP
3 1 00010: Payload Cards zzzzz Payload card slot 001: payload

BCP
010: Porsche
port
4 1 00011: ISB BCP/IWU 00000: ISB BCP/IWU 001: host

(1 Addr per cage)
Internal Address The following table summarizes the number of IP address required for
Summary each entity of the SDU internal IP network. Note that BPP has both
internal IP address and the host port interface between BCP and CPEs
for board-level communication. Communication within the individual
BPP is done via either one of the two interfaces depending on the type
of traffic and the nature of the communication. The actual classification
of the usage is outside the scope of this section.

A-8 Student Guide
Internal Physical IP Address Allocation Summary
SPROC SPROC
Subnet ISB1 ISB2 BPPS CCA1 CCA2 TOTAL
1 2
ISB-SPROC 1 1 1 0 0 0 0 3
Subnet1
ISB-SPROC 1 1 0 1 0 0 0 3
Subnet2
ISB-ISB Subnet 0 0 1 1 0 0 0 2
ISB - payload 0 0 1 0 15(*1) 1 1 18
Subnet1
ISB-Payload 0 0 0 1 15(*1) 1 1 18
Subnet2
Total 2 2 3 3 30 2 2 44
NOTE
*1 note: L# switch port per BPP per Subnet, 15 BPPs per
SDU.

Student Guide A-9
Internal Location Dependent Logical IP Address Allocation Summary
SPROC Processor 1 0 0 0 0 0 0 1
Subnet1
SPROC Processor 0 1 0 0 0 0 0 1
Subnet2
ISB Processor 0 0 1 0 0 0 0 1
Subnet1
ISB Processor 0 0 0 1 0 0 0 1
Subnet2
BPP Subnets 0 0 0 0 2*15(*1) 0 0 30
BPP_CPE Subnets 0 0 0 0 13*15(*2) 0 0 195

BPP Front Panel 0 0 0 0 1*15 (*3) 0 0 15
Subnet
CCA Subnets 0 0 0 0 0 1(*4) 1*(4) 2
Total 1 1 1 1 240 1 1 246
NOTE
*1 NOTE - (1 BCP +L3 switch port) IP address per BPP
Subnet, 15 BPPs per SDU.In BPP, BCP-Porsche
connection is both PC1 and ethernet.
*2NOTE (12 CPES + 1 pORSCHE PORT) per BPPs per SDU.
*3 NOTE: 1Porsche port per BPP, 15 BPPs per SDU. The
other address in this Subnet is assigned to the LMT that is
connected to the BPP front panel. * 4 Note: 1 BCP
processor per CCA Subnet, 2 CCas per SDU.

A - 10 Student Guide
Internal Location Dependent Logical IP Address Allocation Summary
SPROC
Addr Type SPROC ISB1 ISB2 BPPs CCA1 CCA2 Total
2
Site Master SPROC 1 (*1) 0(*1) 0 0 0 0 0 1
ISB BCP/IWU 0 0 1(82) 0(*20 0 0 0 1
ISB ICE/IWU 0 0 17(*3) 0 (*3) 0 0 0 17
Total 1 0 18 0 0 0 0 19
NOTE
*1 note - this shows the case where site master IP
address is assigned to SPROC1.
*2 note - this shows the case where the active ISB is
assigned to ISB1.
*3 note - this shows the case where the IWF i/f (for
IVSHO) is assigned to ISB1.
Address Assignment All internal IP addresses are assigned via DHCP. This is based on the
Method HAP internal network architecture. The HAP defines the unique “client
ID” for each entity to use. Based on the “client ID” in the DHCP
DISCOVER message, the DHCP server assigns the internal IP address
using the pre-configured DHCP server table.
Address Assignment The actual address values for the internal IP address is shown below. It
Values is based on the definitions in the preceding sections of the internal IP
address. The actual host field values in some of the subnets are
dependent on the exact setting in the DHCP server table in the ISB.
However, this table shows the valid IP address configuration.

Student Guide A - 11
Internal IP Address Values
Addr
Subnet Entity IP Address/Mask Note
Type
SPROC - ISB ISB1 port 172.31.0.1/26 Internal Subnet
Subnet 1 SPROC1 port 172.31.0.2/26 Physical Around ISB1
SPROC2 port 172.31.0.3/26
SPROC - LMT LMT port LMT Port Internal

Subnet 1 Physical
SPROC - ISB ISB2 port 172.31.32.1/26 Internal Subnet

Subnet 2 SPROC1 port 172.31.32.2/26 Physical Around ISB2
SPROC2 port 172.31.32.3/26
SPROC - LMT LMT port 172.31.2.1/26 Internal CP9 Link

Subnet 2 172.31.2.2/26 Physical
ISB -payload Subnet1 ISB1 port 172.31.4.1/26 Internal CP2 Links

CCA1 port 172.31.4.2/26 Physical Around
ISB1
BPP1 port 172.31.4.3/26
BPP2 port 172.31.4.4/26
BPP3 port 172.31.4.5/26
BPP4 port 172.31.4.6/26
BPP5 port 172.31.4.7/26
BPP6 port 172.31.4.8/26
BPP7 port 172.31.4.9/26
BPP8 port 172.31.4.10/26
BPP9 port 172.31.4.11/26
BPP10 port 172.31.4.12/26
BPP11 port 172.31.4.13/26
BPP12 port 172.31.4.14/26
BPP13 port 172.31.4.15/26
BPP14 port 172.31.4.16/26
BPP15 port 172.31.4.17/26
CCA2 port 172.31.4.18/26

Addr
Type
ISB -Payload Subnet2 ISB2 port 172.31.36.1/26 Internal CP2 Links
CCA1 port 172.31.36.2/26 Physical Around
ISB2
BPP1 port 172.31.36.3/26
BPP2 port 172.31.36.4/26
BPP3 port 172.31.36.5/26
BPP4 port 172.31.36.6/26
BPP5 port 172.31.36.7/26
BPP6 port 172.31.36.8/26
BPP7 port 172.31.36.9/26
BPP8 port 172.31.3610/26
BPP9 port 172.31.36.11/26
BPP10 port 172.31.36.12/26
BPP11 port 172.31.36.13/26
BPP12 port 172.31.36.14/26
BPP13 port 172.31.36.15/26
BPP14 port 172.31.36.16/26
BPP15 port 172.31.36.17/26
CCA2 port 172.31.36.18/26
SPROC_BCP SPROC1 BCP 172.31.64.1/29 internal lo- BCP in

Subnet1 cation SPROC1
de-pendent
logical
SPROC_BCP SPROC2 BCP 172.31.96.1/29 internal lo- BCP in

Subnet2 cation SPROC2
de-pendent
logical
ISB_BCP Subnet1 ISB1 BCP 172.31.64.9/29 internal lo- BCP in

ditto cation ISB1
de-pendent
logical
ISB_BCP Subnet2 ISB2 BCP 172.31.96.9/29 ditto BCP in

ISB2

Addr
Type
CCA1_BCP Subnet CCA1 BCP 172.31.68.9/29 ditto (slot 1)
CCA2_BCP Subnet CCA2 BCP 172.31.68.99/29 ditto (slot 19)
BPP1_BCP Subnet BPP1 BCP 172.31.68.19/29 ditto (slot 3)
BP10_BCP Subnet BPP10 BCP 172.31.68.61/29 ditto (slot 12)

Addr
Type
site master SPROC SPROC1/2 BCP 172.31.102.1/29 Internal 1 Addr per
Location Cage
Indepen-
dent Logical
ISB BCP ISB1/2 BCP 172.31.70.1/29 Ditto 1 Addr per
Cage
ISB ICE ISB1/2 port 172.31.70.81/27 Ditto 17 Addr

ISB1/2 ICE DSP1 172.31.70.82/27 - per Cage
172.31.70.85/27
ISB1/2 ICE DSP2 172.31.70.86/27 -
172.31.70.89/27
ISB1/2 ICE DSP3 172.31.70.90/27 -
172.31.70.93/27
ISB1/2 ICE DSP4
172.31.70.94/27 -
172.31.70.97/27
External IP Address The SDU external IP addressing is outside of the HAP provided
framework. Thus, it is supported by the SDU product specific
implementation.
External IP Address The bit assignment of the external IP address is shown below.
Format

External IP Address Format

Internal Subnet/
Network Addr (23 Bits) Host Addr
31 24 16 9 8 7 X 0
Network Network Network Subnet Host
External IP Address The external IP address is determined and assigned by the OMCR. The
Format address is assigned from the class A private IP address space with 23
bit Subnet mask (i.e. 10.xx.xx.xx/23). Each Subnet represents a unique
SDU unit and its internal Subnet. This address space is based on the
Wireless Transport Network FRDD, and the actual network value
assignment is outside the scope of this document. This illustrates the
recommended bit assignment, and the actual assignment is not limited
to this arrangement. The address range defined by the 23 bit Subnet
mask defines the SDU level Subnet. This gives the maximum of 510 IP
addresses per SDU (2**9 - 2). The externally visible Subnet within the
SDU is further divided by the “internal subnet mask,” (>23 bits) and
assigned to each of these subnets. Note that the length of the
Subnet mask is variable depending on the location of the subnet. The

combination of the subnet and host fields consist the lowermost 9 bit of
the address space. These subnets are defined by the SPROC at the time
of system initialization.
It should be noted that both physical and logical IP addresses are

allocated from this address space. Each SDU entity needs to retain the
association between the assigned IP address and the address type (i.e.
physical or logical) when the address is determined initially.

External IP Address Bit Mapping (Physical/Logical)
Bit
Octet # Bit Value Description
Position
2 23-16 8 0-255 Network Addr
3 15-9 7 0-127 Network Addr
3/4 8-0 9 0-31 Subnet ID/host ID (varies depending on the

subnet)
NOTE
The following table shows the subnet mask/host field
assignment for the SDU subnets.
Subnet/Host Assignment for External IP Address
# of # of Host Subnet Field

Host
Subnet Require Length Total
Subnet Field Note
per d per Subnet Mask
Length
SDU Subnet Length)
AN router -ISB 4 1 7(30) 2 The other address is on the
Subnet port of the association
ISB Processor 3 1 7(30) 2 1 Subnet per ISB (physical

Subnet addr), and 1 subnet per pair
(logical addr)
SPROC 3 1 7(30) 2 1 Subnet per ISB (physical

Processor Subnet addr), and 1 subnet per pair
(logical addr)
BPP BCP 13/15 (*1) 2(*2) 7(30) 2

Processor Subnet
BPP CPE Subnet 13/15 (*1) 13 (*3) 5(28) 4
NOTE
*1 Note - the first number is for the N+1 redundancy
configuration, and the second number is for non-
redundancy configuration. 15 BPPs per SDU, N+1
redundancy for SDF and CPF; 13 active and 2 standby

BPPs
*2 Note - (1 BCP + 1 L3 switch port) IP addresses per BPP.
*3 Note - (12 CPEs +1 L3 switch port) IP addresses per
BPP.
External Physical IP External physical IP address is an externally visible address from

Address outside of the SDU. They are statically associated with a particular
ethernet interface.
ISB For each ISB, there are two router interfaces that are connected to the
AN routers. One external physical IP address is assigned to each of
these interface.
SPROC/BPP/CCA There is no external physical IP address for these device types.
External Location External location dependent logical IP address is an externally visible

Dependent Logical IP address from outside of the SDU. They are statically associated with a
address particular board.
ISB One external location dependent logical IP address is assigned for the
ISB BCP. The purpose of this externally visible IP address is two fold:
1) provide a capability to directly telnet to a particular ISB from outside
of the SDU (e.g. OMCR for maintenance activity), and 2) use as the
OSPF “router ID” for the particular ISB. For further details of the
OSPF Router ID, refer to the OSPF section below.
SPROC The physical ports in the SPROC are within the internal IP subnet.
Therefore, there is no external physical IP address associated with
specific ports for SPROC. However, the SPROC contains a logical
subnet within the board separated by a logical router. One external
location dependent logical IP address is assigned to the SPROC board
level. The purpose of this externally visible IP address is to provide a
capability to directly telnet to a particular SPROC from outside of the
SDU (e.g. OMCR for maintenance activity).
BPP There is no external location dependent logical IP address in BPP. See

the next location independent logical IP address section for more
information.

CCA There is no external location dependent IP address in CCA.
External Location External location independent logical IP address is an externally visible

Independent IP address from outside of SDU. They are either dynamically associated
address in CCA. with a particular interface of a board, or with a particular board level.
The primary purpose of an external location independent logical IP
address is to indicate the active side of a device pair (or device group)
from outside of the SDU. For the SPROC pair, the primary use is the
SNMP agent address to communicate with the OMCR. As the device
status change takes place, the external location independent logical
address is re-assigned to the active device. This way, the active-standby
status and device failover will be transparent from other network
elements in the RAN.
ISB One of the ISB pair is assigned with an external location independent
logical address. It is assigned to the active side at any given time.
SPROC One of the SPROC pair is assigned with an external location

independent logical IP address. It is assigned to the active side at any
given time. The primary use of this logical address is the SNMP Agent
address in order to communicate with the OMCR.
BPP In the CPE subnet and BCP subnet of all the active BPPs, external
location independent logical address is assigned. The BCP, each CPE,
and the associated two router ports are assigned with this address type.
The stand-by BPPs are assigned with this type of address only when
they are brought into active state by being re-assigned from the
previously-active BPP. In other words, they are not configured with this
type of address when they are in the stand-by state, and are dynamically
re-assigned from one BPP to another at the time of failover.
In the case where all BPPs are configured as active state (no
redundancy configuration), all BPPs are assigned with this external
location independent logical IP address.
CCA There is no external location independent IP address for CCA.
External IP address The following tables summarize the number of IP addresses required
summary for each entity of the SDU external IP address.

External Physical IP Address Allocation Summary
SPROC
Subnet SPROC2 ISB1 ISB2 BPPs CCA1 CCA2 Total
1
CSR-ISB 0 0 2(*1) 0 0 0 0 2
Subnet 1,2
CSR-ISB 0 0 0 2(*1) 0 0 0 2
Subnet 3,4
Total 0 0 2 2 0 0 0 4
NOTE
*1 note - ISB port connected to AN routers (2 per ISB)
External Location Dependent Logical IP Address Allocation Summary
SPROC SPROC
Subnet ISB1 ISB2 BPPs CCA1 CCA2 Total
1 2
ISB Processor 0 0 1(*1) 1(*1) 0 0 0 2
Subnet 1,2
SPROC 1 1 0 0 0 0 0 2
Processor
Subnet1, 2
BPP-BCP 0 0 0 0 0 0 0 0
Subnet 1-15
BPP-CPE 0 0 0 0 0 0 0 0
Subnet 1-15
Total 1 1 1 1 0 0 0 4
NOTE
*1 note - 1 BCP per ISB (PCI bus connection to L3 switch).
Also used as the OSPF router ID (1 per ISB)

External Location Independent Logical IP Address Allocation Summary
SPROC ISB BPP BPP cca TOTAL

Addr Type
Pair Pair BCPs CPEs Pair
Logical 1 1 2*13/ 13*13/ 0 197/227
Address 2*15(*1) 13*15(*2)
Total 1 1 26/30 169/195 0 197/227
NOTE
*1 note - (1 BCP + 1 L3-switch port) IP addresses per BPP.
15 BPPs in SDU. BCP-L3 switch connection is an ethernet
(in addition to the PCI bus), thus requires 1 L3 switch port.
The first row is for the case of 13 active BPPs (two N+1
redundant BPP configuration). The second row is for all-
active case (no N+1 redundancy).
*2 note - (12 CPEs + 1 L3-switch port) IP addresses per
BPP. 15 BPPs in SDU. The first row is for the case of 13
active BPPs (two N+1 redundant BPP configuration). The
second row is for all-active case (no N+1 redundancy).
Address Assignment The assignment of external IP address is divided into two stages -
Method provisioning at commissioning time, and address assignment during the
initialization. The minimum subset of the external IP addresses will be
provisioned from an Local Maintenance Terminal (LMT) during the
commissioning in order to initialize the SDU with the minimum
capability. The type of external IP address that is provisioned are as
follows:
1. Gbit interfaces for AN routers (ISB): 2 per ISB, 4 per SDU
2. OSPF Router ID (ISB): 1 per ISB, 2 per SDU
3. SNMP Agent address (SPROC): 1 per SPROC pair (i.e. SDU)
4. OMCR address (SPROC): 1 per SPROC pair (i.e. SDU)

All other external IP addresses will be assigned from the SPROC

during the initialization. The external IP address is a part of the
configuration database which is downloaded from OMCR in the earlier
stage of the initialization. Based on the database, the site master
SPROC allocates and delivers the external IP address to each entity that
requires external address.
The assignment of these external IP addresses are done by the SDU

product specific portion in the SPROC, and it is outside of the HAP
domain.
Sample Address A sample assignment of the external IP address is shown below. The
Assignment base network address of 10.0.40.0/23 is used as an example. This is for
the illustration purpose only, and the actual address, especially the
network portion, will vary depending on the overall address planning at
the system level.
It is worth noting that the proportion of the actual assigned address is

much less than the total address space. This is mainly due to the smaller
host size, and only 1 host address is needed per subnet in many cases.
In the first 4 groups in the table below, only 40 addresses out of the 110
address space is used (36% usage). In the last group, 195 out of 237
address space is used (82%). Overall, approximately 64% of the
address space is used, and the remaining 36% is wasted. With the total
510 address space from the 9 bits for subnet/host combination,
approximately 140 IP address are left unused as future expansion.

Sample Addressing of External IP Address

AN router - ISB Subnet ISB1 port1 10.0.40.2/30 The other
ISB1 port2 10.0.40.6/30 host is
ISB2 port1 10.0.40.10/30 assigned to
ISB2 port2 10.0.40.14/30 the AN router
ISB BCP Processor ISB1 10.0.40.17/30

Subnet ISB2 10.0.40.21/30
logical 10.0.40.25/30
SPROC BCP SPROC1 10.0.40.29/30

Processor Subnet SPROC2 10.0.40.33/30
logical 10.0.40.37/30
BPP BCP Processor BPP1 10.0.40.53/30, 10.0.40.54/30

Subnet BPP2 10.0.40.57/30, 10.0.40.58/30
BPP3 10.0.40.61/30, 10.0.40.62/30
BPP4 10.0.40.65/30, 10.0.40.66/30
BPP5 10.0.40.69/30, 10.0.40.70/30
BPP6 10.0.40.73/30, 10.0.40.74/30
BPP7 10.0.40.77/30, 10.0.40.78/30
BPP8 10.0.40.81/30, 10.0.40.82/30
BPP9 10.0.40.85/30, 10.0.40.86/30
BPP10 10.0.40.89/30, 10.0.40.90/30
BPP11 10.0.40.93/30, 10.0.40.94/30
BPP12 10.0.40.97/30, 10.0.40.98/30
BPP13 10.0.40.101/30, 10.0.40.102/30
BPP14 10.0.40.105/30, 10.0.40.106/30
BPP15 10.0.40.109/30, 10.0.40.110/30

BPP CPE Subnet BPP1, CPE1-12 10.0.40.129/28 ~ 10.0.40.141/28

BPP2, CPE1-12 10.0.40.145/28 ~ 10.0.40.157/28
BPP3, CPE1-12 10.0.40.161/28 ~ 10.0.40.173/28
BPP4, CPE1-12 10.0.40.177/28 ~ 10.0.40.189/28
BPP5, CPE1-12 10.0.40.193/28 ~ 10.0.40.205/28
BPP6, CPE1-12 10.0.40.209/28 ~ 10.0.40.221/28
BPP7, CPE1-12 10.0.40.225/28 ~ 10.0.40.237/28
BPP8, CPE1-12 10.0.40.241/28 ~ 10.0.40.253/28
BPP9, CPE1-12 10.0.41.1/28 ~ 10.0.41.13/28
BPP10, CPE1-12 10.0.41.17/28 ~ 10.0.41.29/28
BPP11, CPE1-12 10.0.41.33/28 ~ 10.0.41.45/28
BPP12, CPE1-12 10.0.41.49/28 ~ 10.0.41.61/28
BPP13, CPE1-12 10.0.41.65/28 ~ 10.0.41.77/28
BPP14, CPE1-12 10.0.41.81/28 ~ 10.0.41.93/28
BPP15, CPE1-12 10.0.41.97/28 ~ 10.0.41.109/28
IP Address Allocation The following table summarizes all types of IP address assignments for
Summary the entire SDU
IP Address Allocation Per Type
Board Type #> of Internal Internal External External

Total
Board per SDU) Physical Logical Physical Logical
SPROC (2) 4 3 0 3 10
ISB(2) 6 20 4 3 33
BPP(15) 30 240 0 195/225 (*1) 465/495 (*1)
CCA(2) 4 2 0 0 6
Total (21) 44 265 4 201/231 514/544
NOTE
*1 note: the first number is for the case of 13 active BPPs
(i.e. two N+1 redundant BPPs), the second number is for
the case of all-active BPPs (i.e. no N+1 redundancy).
IP Address Usage As described above, different types of IP addresses exist for different
purposes. The following table summarizes the relationship of the traffic
type and the address type.

IP Address Usage by Traffic Type
SRC IP Dest IP Traffic

Example
Addr Addr Type
Internal Internal FM, • to address peer SPROC for sanity checking, checkpointing, and link
Logical Logical CM, fault detection between primary/standby SPROCs
O&M • to rlogin from primary SPROC to BPP BCPs
• checkpointing between BPP BCPs
• checkpointing between ISBs.
• to rlogin from a given SPROC to BPP BCPs
• to address ISBs from primary SPROC for sanity checking, link fault
detection, and code download
• to address SPROCs from ISBs for sanity checking, link fault detection
• to address DHCP clients from the DHCP server
• to address BPP BCPs from primary SPROC for sanity checking, link
failure detection, and code download.
• any communication between primary SPROC and primary ISB
• to address CPEs from BCP within a single BPP for sanity checking,
link failure detection, code download.
• to address BCP from CPEs within a single BPP for sanity
checking response, link failure detection, code download request.
• to address primary SPROC from BPP BCP for code download request
• alarm reporting to primary SPROC from BPP BCP
• to address primary SPROC for code download request from ISBs
• alarm reporting to primary SPROC from ISBs
Internal Multicast OSPF • OSPF LSA messages among SDU router entities (except
Logical Addr ISBs).
External Multicast OSPF • OSPF LSA messages to/from ISBs with other SDU router entities.
Logical (*1) Addr
External External FM • to address SPROCs from OMCR (via AN routers) for sanity
Logical Logical O&M checking (if such messaging is necessary)
CM • to address ISBs from OMCR (via AN routers) for sanity checking
CP and link fault detection
bearer • to address OMCR (via AN routers) in response to the above
messages
• to telnet from OMCR (via AN routers) to SDU entities
(SPROCs, ISBs)
• to address primary SPROC from OMCR (via primary CSR) for
code download, O&M MMI commands
• to address BPP CPEs from MM/XC/PDSN/BTS (via primary
CSR) for inbound call processing control messages and bearer
traffic
• to address external AN entities (i.e. MM/XC/PDSN/BTS) from
BPP CPEs for outbound call processing control messages and
bearer traffic

Notes


Omcr100&110a PDF

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Omcr100&110a PDF

Încărcat de

Drepturi de autor:

Formate disponibile

1X Cellular Database

Course Number OMCR100A

Document Title 1X Cellular Database Administration

1.0 07/01 Initial Release

OMCR100A 1X Cellular Database Administration Revision 2.2 - 11/03

Product and service names profiled herein are trademarks of Motorola,

The following copyright/trademarks are acknowledged in this course:

• SPARC is a trademark of Sun Microsystems

• SUN is a trademark of Sun Microsystems

Disclaimer Motorola, Inc. Global Telecom Solutions Sector makes no warranties

Revision 2.2 - 11/03 1X Cellular Database Administration OMCR100A

• Lauren St. Andre

OMCR100A 1X Cellular Database Administration Revision 2.2 - 11/03

Introductions The following introductions will serve to introduce the instructor,

- Instructor background and credentials

- Student background and credentials

• Course terminal objective

• Identification badges are required at all times

- Badges must be turned in every day after class

- Telephone Number: __________________

Revision 2.2 - 11/03 1X Cellular Database Administration OMCR100A

- Locations of phones, vending area, and rest rooms

- Information monitor (if provided)

- Smoking area (if provided)

- Local area maps (if provided)

OMCR100A 1X Cellular Database Administration Revision 2.2 - 11/03

Audience This course is created for the following individuals:

• Technical support personnel responsible for performing basic

• Perform cellular database administration procedures for 1X

Course Length Three days

Prerequisites The following training courses or knowledge is recommended:

• GNL060 Basic CDMA Concepts

• GNL070 SC™ Product Family Overview (CDMA)

• NETG13630 Unix User Fundamentals

• NETG13631 Unix Advanced Topics for Users

• NETG13634 Sun Solaris Basic Administration

• NETG16635 Sun Solaris Network Administration

• Working knowledge of/or experience with Code Division

Revision 2.2 - 11/03 1X Cellular Database Administration OMCR100A

• CDMA2000 1X Operations and Maintenance Center-Radio

• CDMA2000 1X Central Base Station Controller (CBSC)

• CDMA2000 1X Access Network (AN)

• CDMA2000 1X Packet Data Service Node (PDSN)

• CDMA2000 1X Mobile Wireless Center (MWC)

• CDMA2000 1X SC™ 4812T and/or SC™ 4812ET Base

• Terminals accessing CDMA2000 1X Network

Course Material The following material is needed to complete this course:

• 1X Cellular Database Administration Student Guide

• CDMA Online Documentation CD-ROM Release 2.16.3.X -

• CDMA Online Documentation CD-ROM Release 2.16.3.X -

OMCR100A 1X Cellular Database Administration Revision 2.2 - 11/03

Management Information Base (MIB) ...............................1

Access Network (AN).........................................................1

Centralized Base Station Controller (CBSC)......................2

Transcoder (XC) .................................................................2

Base Transceiver Station (BTS)..........................................3

MSC Span and Terrestrial Circuit (TERCKT)....................3

Revision 2.2 - 11/03 1X Cellular Database Administration OMCR100A

• Identification of potential safety hazards

• Identification of the location of any lab power disconnect push-

• Explanation of the Electro-Static Discharge (ESD) precautions

• Demonstrate placing the lab equipment in the proper standby

Live Circuits Only factory authorized service personnel or other qualified