CDMA Access Configuration and Provisioning (CACP) Overview

Code Division Multiple Access (CDMA)
CDMA Access Configuration and

Provisioning (CACP) Overview
ATTENTION
Clicking on a PDF hyperlink takes you to the appropriate page. If necessary,
scroll up or down the page to see the beginning of the referenced section.
NN20000-126
.
Document status: Standard
Document version: 04.30
Document date: 1 December 2006
Copyright © 2003-2006, Nortel Networks

All Rights Reserved.
Sourced in Canada and the United States of America.
The information contained herein is the property of Nortel Networks and is strictly confidential. Except as expressly
authorized in writing by Nortel Networks, the holder shall keep all information contained herein confidential, shall
disclose it only to its employees with a need to know, and shall protect it, in whole or in part, from disclosure and
dissemination to third parties with the same degree of care it uses to protect its own confidential information, but
with no less than reasonable care. Except as expressly authorized in writing by Nortel Networks, the holder is
granted no rights to use the information contained herein.
Information is subject to change without notice. Nortel Networks reserves the right to make changes in design or
components as progress in engineering and manufacturing may warrant.
* Nortel, the Nortel logo and the globemark are trademarks of Nortel Networks. Adobe and Acrobat Reader are
trademarks for Adobe Systems.
Trademarks are acknowledged with an asterisk (*) at their first appearance in the document.
All other trademarks are the property of their respective owners.

3
Contents
New in this release 9
Features 9
Other changes 11
CACP overview 13
CACP purpose 13
Navigation 13
Indication of hypertext links 14
CACP components 15
CACP Client 17
CACP Server 18
Functionality 21
Functionality navigation 21
Base functionality 21
Compact Metro Cell 22
eDCG support 22
Multi-version support 23
PDB on C-EMS 23
Navigating the application 25
Navigating the application navigation 25
Main window 25
Menu bar and tool bar 26
Navigator panel 27
Editing panel 32
Port Map View 32
Row View 40
Data Compare View 41
Column views 43
Message panel 46
Preferences 47
File path settings 49
Debug log settings 49
General settings 50

CDMA Access Configuration and Provisioning (CACP) Overview
NN20000-126 04.30 Standard
NBSS 14.0 1 December 2006
Copyright © 2003-2006, Nortel Networks Nortel Networks Confidential
.
4 Contents
Menus 51
Menus navigation 51
File 51
Edit 53
View 53
Tools 54
Reports 56
Help 57
Configuration wizards 59
Configuration wizards navigation 59
Basic usage 59
MetroCell BTS / Compact MetroCell Outdoor BTS wizard 60
Sites 61
T1/E1 trunks 62
RFMs 63
Carrier sectors 66
CEM cards 68
Add second DCG 69
Compact MetroCell Indoor BTS wizard 70
Sites 70
T1/E1 trunks 71
RMs 72
Carrier sectors 75
CEM cards 76
Metro Cell MultiBTS CEM wizard 77
Compact Metro Cell MultiBTS CEM wizard 77
SBS wizard 78
Validation wizards 79
Check Business Rules 79
Show Unassigned Elements 81
Show Port Conflicts 82
ISSHO BTSs BCNv2 Compliance 83
Intra-BSC BCNv2 Compliance 85
Multi BSC wizards 86
Rehome a BTS 86
Reconcile PDB across BSCs 91
Fill ARP Lists wizard 94
BCNv2 wizards 95
Assign TRG 95
Reconcile TRG on PDB for Physical Sectors 96
Rollback TRG on PDB for Physical/Logical Sectors 96

NN20000-126 04.30 Standard
.
Contents 5
PDB utilities 97
PDB utilities navigation 97
Neighbor list reciprocity 97
PDB/BTS Neighborlist reconciliation 100
Propagate NLIST/CDMANLIST to all carriers 106
Repair unknown beacon targets 108
Repair unknown border targets 109
Repair unknown EHHO target references 110
Repair unknown EC target references 111
Generate beacon targets 111
Search-Replace EBID/Pilot PN 113
Reports 115
Prerequisites 115
Reports navigation 115
EBSC Configuration Statistics report / BSC Configuration Statistics report 115
BSC Configuration Changes report 117
BSC Comparison Delta report 118
BCN Port report 119
BTS Provisioning report 120
Redundant DCG Discrepancies report 121
CFDS License report 122
User help 125

Help navigation 125
About 125
About Sessions 125
CACP Online Help 125
Memory Statistics 125
User Guides 126
Recommended values 127
Restrictions, dependencies, and limitations 131
Restrictions, dependencies, and limitations navigation 131
Communication 131
Version 132
Multiple BSC 132
Commit 132
Configuration 133
CBRS 135
SCH Throughput Enhancements 137
auditfreqorder tool 139

auditfreqorder tool navigation 139

NN20000-126 04.30 Standard
.
6 Contents
Overview 139
Configuration 139
Usage 140
CDMA paging zone editing during upgrade 141

Enabling the script viewer/generator 142
Editing CDMA paging zone data during upgrade 143
Figures
Figure 1 CACP application components 16
Figure 2 CACP Main window 26
Figure 3 Network element tree 28
Figure 4 Network element tree - CBRS / CNFP components 29
Figure 5 Network element tree - CPDS components 30
Figure 6 Network element tree - CSVS components 31
Figure 7 Main Window - Port Map View 33
Figure 8 CBRS Frame Panel - E1 configuration 34
Figure 9 CPDS Chassis Panel 35
Figure 10 24pBCNW Port Map 36
Figure 11 11pMSW Port Map 37
Figure 12 11pMSW Port Configuration dialog box 38
Figure 13 11pMSW Edit Property dialog box 39
Figure 14 24pBCNW Edit Property dialog box 40
Figure 15 Main Window - Row View 41
Figure 16 Main Window - Data Compare View 42
Figure 17 Column view selection 43
Figure 18 Manage Column View - Select Columns dialog box 44
Figure 19 Manage Column view - Sort Order dialog box 45
Figure 20 Manage View dialog box 46
Figure 21 Preferences dialog box - File Path Settings 48
Figure 22 Preferences dialog box - Debug Log Settings 48
Figure 23 Preferences dialog box - General Settings 49
Figure 24 Configure Site dialog box 62
Figure 25 Configure T1/E1 Trunks dialog box 63
Figure 26 Configure RFMs dialog box 64
Figure 27 Configure RFMs Tips 65
Figure 28 Enter Frequency dialog box 65
Figure 29 Enter Values for Carrier-Sector dialog box 66
Figure 30 Configure Carrier Sectors dialog box 67
Figure 31 Configure CEM Cards dialog box 69
Figure 32 Configure Site dialog box 71
Figure 33 Configure T1/E1 Trunks dialog box 72
Figure 34 Configure RMs dialog box 73
Figure 35 Configure RMs Tips 73
Figure 36 Enter Channel dialog box 74
Figure 37 Enter Values for Carrier-Sector dialog box 74
Figure 38 Configure Carrier Sectors dialog box 75
Figure 39 Configure CEM Cards dialog box 76
Figure 40 MultiBTS CEM Add dialog box 77
Figure 41 Multi-cBTS CEM Configure dialog box 78

NN20000-126 04.30 Standard
.
Contents 7
Figure 42 Add SBS Shelves dialog box 79

Figure 43 Check Business Rules dialog box 80
Figure 44 Business Rules tab 81
Figure 45 Unassigned Objects tab 82
Figure 46 Port Conflicts tab 83
Figure 47 ISSHO BTSs BCNv2 Compliance dialog box 84
Figure 48 Intra-BSC BCNv2 Compliance results 86
Figure 49 Multi BSC Rehome - Main Panel 89
Figure 50 Multi BSC Rehome - Set values 90
Figure 51 Multi BSC Rehome confirmation dialog box 91
Figure 52 MultiBSC Connection dialog box 92
Figure 53 Reconciling Logical BSC with Physical BSC dialog box 93
Figure 54 Select Fill Type for ARP Lists dialog box 95
Figure 55 Assign TRG dialog box 95
Figure 56 Check Neighbor Reciprocity with Peers dialog box 98
Figure 57 Add CDMANLIST dialog box 99
Figure 58 Delete CDMANLIST dialog box 99
Figure 59 Delete Reciprocal Neighbors dialog box 100
Figure 60 Reconciliation tab 101
Figure 61 Reconcile PDB and BTS CDMA Neighbor Lists dialog box 102
Figure 62 Select PDB Neighbor dialog box 103
Figure 63 Select BTS Neighbor dialog box 105
Figure 64 Sort Order dialog box 106
Figure 65 Propagate NLIST/CDMANLIST to all Carriers dialog box 107
Figure 66 Repair Unknown BEACON References dialog box 109
Figure 67 Repair Unknown BORDER References dialog box 110
Figure 68 Repair Unknown EHHO References dialog box 110
Figure 69 Repair Unknown EC References dialog box 111
Figure 70 Generate BEACON Targets dialog box 112
Figure 71 Generate BEACON Targets grid dialog box 113
Figure 72 Search-Replace EBID dialog box 114
Figure 73 Search-Replace EBID Results dialog box 114
Figure 74 EBSC Configuration Statistics report 117
Figure 75 BSC Configuration Changes report 118
Figure 76 BSC Comparison Delta report 119
Figure 77 BCN Port report 120
Figure 78 BTS Provisioning report 121
Figure 79 Redundant DCG Discrepancies report 122
Figure 80 CFDS License report 123
Figure 81 Edit Customer Recommended Values dialog box 128
Figure 82 Select New Recommended Values Columns dialog box 129
Figure 83 CDMA paging zone editing during upgrade task flow 142

NN20000-126 04.30 Standard
.
8 Contents

NN20000-126 04.30 Standard
.
9
New in this release

The following sections list new features and changes in CDMA Access
Configuration and Provisioning (CACP) Overview (NN20000-126) for NBSS
14.0:
• "Features" (page 9)
• "Other changes" (page 11)
The Nortel Technical Publication (NTP) development is a three-stage

process. At each level of product maturity, publications have a specific status
based on quality assurance requirements: draft, preliminary, and standard.
In this version of CDMA Access Configuration and Provisioning (CACP)

Overview, the following statuses apply:
Product Status
MFRM-3 Draft
AABS Preliminary
CACP14 MNCL Preliminary
The New in this release section identifies specific content that is draft or
preliminary until the fully customer-ready standard stage is achieved.
Features
The following features impact this NTP:
• "CACP 14.0" (page 9)
• "TurboIF" (page 11)
CACP 14.0
The CACP 14.0 feature impacts the following sections:
• "CACP components" (page 15)
— Modified "CACP Client" (page 17)
— Modified "CACP Server" (page 18)

NN20000-126 04.30 Standard
.
10 New in this release
• "Functionality" (page 21)

— Modified "Multi-version support" (page 23)
• "Navigating the application" (page 25)

— Modified Figure 2 "CACP Main window" (page 26)
— Modified Figure 3 "Network element tree" (page 28)
— Modified Figure 7 "Main Window - Port Map View" (page 33)
— Modified Figure 8 "CBRS Frame Panel—E1 configuration" (page 34)
— Modified Figure 9 "CPDS Chassis Panel" (page 35)
— Modified Figure 10 "24pBCNW Port Map" (page 36)
— Modified Figure 11 "11pMSW Port Map" (page 37)
— Modified Figure 15 "Main Window - Row View" (page 41)
— Modified Figure 16 "Main Window - Data Compare View" (page 42)
— Modified Figure 17 "Column view selection" (page 43)
— Modified Preferences dialog box - General Settings
— Modified Figure 23 "Preferences dialog box - General Settings"
(page 49)
• "Menus" (page 51)

— Added Attention to section purpose statement
— Modified "File" (page 51)
• "Configuration wizards" (page 59)

— Modified "Basic usage" (page 59)
— Modified Figure 24 "Configure Site dialog box" (page 62)
— Modified Figure 26 "Configure RFMs dialog box" (page 64)
— Modified Figure 30 "Configure Carrier Sectors dialog box" (page 67)
— Modified Figure 44 "Business Rules tab" (page 81)
— Modified Figure 45 "Unassigned Objects tab" (page 82)
— Modified Figure 46 "Port Conflicts tab" (page 83)
— Modified Figure 48 "Intra-BSC BCNv2 Compliance results" (page 86)
— Modified Figure 54 "Select Fill Type for ARP Lists dialog box" (page
95)

NN20000-126 04.30 Standard
.
Other changes 11
• "PDB utilities" (page 97)

— Modified Figure 57 "Add CDMANLIST dialog box" (page 99)
— Modified Figure 58 "Delete CDMANLIST dialog box" (page 99)
— Modified Figure 61 "Reconcile PDB and BTS CDMA Neighbor Lists
dialog box" (page 102)
— Modified Figure 65 "Propagate NLIST/CDMANLIST to all Carriers
dialog box" (page 107)
• "Reports" (page 115)

— Modified "EBSC Configuration Statistics report / BSC Configuration
Statistics report" (page 115)
— Modified "BSC Comparison Delta report" (page 118)
— Modified "BTS Provisioning report" (page 120)
• "User help" (page 125)

— Modified "User Guides" (page 126)
• "Restrictions, dependencies, and limitations" (page 131)

— Modified "Version" (page 132)
— Modified "Configuration" (page 133)
TurboIF
The TurboIF feature impacts the following section:
• "CACP overview" (page 13)
— Modified "CACP purpose" (page 13)
Other changes
The following global changes are made in this Nortel Technical Publication
(NTP):
• change eBSC to EBSC
• change BSSM to BSS Manager
• change Passport to Multiservice Switch (MSS)
• change extended neighbor to CDMA neighbor
• change eneighbor to CDMANeighbor

NN20000-126 04.30 Standard
.
12 New in this release
• change ENLIST to CDMANLIST

• added chapter "CDMA paging zone editing during upgrade" (page 141)

NN20000-126 04.30 Standard
.
13
CACP overview
This document describes the CDMA Access Configuration and Provisioning
(CACP) application, including its architecture, functionality, and use of the
Graphical User Interface (GUI).
Use CACP for all configuration activities previously performed with

CheckNeighbor, Commgr, Network Configuration File (NCF) Editor, and
CDF.
CACP purpose
The purpose of the CACP tool is to provide a single application which can
configure Radio Frequency (RF) engineering parameters, and provision and
configure the network elements belonging to the Code Division Multiple
Access (CDMA) network.
Another purpose of the CACP application is to provide transparency from

existing Base Station Subsystem Manager (BSS Manager) configuration
management interfaces such as Base Station Manager Command Interface
(BSMCI), Command Line Interface (CLI), and TurboIF, while at the same
time enhancing the usability of the CDMA Operations, Administration, and
Maintenance (OAM) product. CACP support secure execution of TurboIF.
CACP provides a number of wizards and configuration tools to help

configure the RF data and network expansion functions.
The CACP application overlaps with existing BSS Manager applications

such as Commissioning Manager, NCF/CheckNeighbor, and Enhanced
Base Station Controller (EBSC) Configuration Tool.
Navigation
• "CACP components" (page 15)
• "Functionality" (page 21)
• "Navigating the application" (page 25)
• "Menus" (page 51)

NN20000-126 04.30 Standard
.
14 CACP overview

• "PDB utilities" (page 97)
• "User help" (page 125)
• "Recommended values" (page 127)
• "auditfreqorder tool" (page 139)
Indication of hypertext links

Hypertext links in this document are indicated in blue. If viewing a PDF
version of this document, click on the blue text to jump to the associated
section or page.

NN20000-126 04.30 Standard
.
15
CACP components
This document describes the CDMA Access Configuration and Provisioning
(CACP) tool’s two main components, the CACP Client and the CACP
Server. The CACP tool is implemented as a Client-Server model, where
the CACP Server resides on the existing Base Station Subsystem Manager
(BSS Manager) platform and the CACP Client resides on a Windows PC.
The Client provides tools to import data, view and edit configuration data,
make configuration changes, validate configuration data, and commit the
changes.
The Server collects configuration data from the BSS Manager, CDMA
backhaul and routing subsystem (CBRS) frame, and CDMA packet data
subsystem (CPDS) and submits configuration changes to existing BSS
Manager tools (BSMCI, CLI, and TurboIF) in the form of scripts on behalf
of the CACP Client. The Server is the interface through which the Client
configures the access network.
Figure 1 "CACP application components" (page 16) shows the CACP

application and its relationship with the Base Station Manager Command
Interface (BSMCI), Command Line Interface (CLI), and TurboIF interfaces
on the BSS Manager.

NN20000-126 04.30 Standard
.
16 CACP components
Figure 1
CACP application components
The CACP Client connects to a particular CACP Server and requests a

query of an access network and its related CBRS and CPDS frames. The
Client adds and removes network elements and adjusts configuration
parameters. The configuration changes are validated and then submitted to
the CACP Server. The Server passes configuration scripts to the appropriate
BSS Manager processes and invokes the processes. The processes run
the scripts and provide a log report which is passed back to the Client.
BSMCI and CLI are standard existing interfaces on the BSS Manager used
to access BSC and BTS data. The CACP Server interfaces with these tools
to request queries and to submit configuration scripts for execution.
The TurboIF interface retrieves CBRS/CPDS configuration data and submits

CBRS/CPDS scripts to configure its hardware and software. All the CBRS
and CPDS frames configuration scripts generated by the CACP application
are executed by this tool. TurboIF is also used to retrieve the current
CBRS/CPDS configuration data for a particular frame.
CACP Clients connect to and communicate with the CACP Server using
Transmission Control Protocol/Internet Protocol (TCP/IP) through a well
known TCP port (port 7301). A proprietary protocol exchanges data
between the Client and Server components. Clients can be networked to the

NN20000-126 04.30 Standard
.
CACP Client 17
BSS Manager through any TCP/IP networking facilities that the customer
network provides: standard Local Area Networks (LAN), Point-to-Point
Protocol (PPP) dialup connections, and Virtual Private Network (VPN)
connections over the Internet. The only restriction is that the Client/Server
communication traffic must not be blocked by any intermediary firewall.
The CACP Server manages up to ten concurrent Clients. The CACP

Client can connect to multiple CACP Servers and perform multiple BSC
configuration tasks.
CACP Client
The CACP Client is a Graphical User Interface (GUI) application that
performs system-level configuration of the CDMA access network. The
Client:
• works in online mode (connected to the BSS Manager, using a session
file or online data) or offline mode (not connected to the BSS Manager,
using a session file)
• can connect to multiple CACP Servers to perform multiple BSC
configuration tasks—up to two simultaneous online sessions per Client
and up to five simultaneous offline sessions per Client
• provides the automated ability to retrieve and submit configuration data
to and from the BSS Manager
• provides a variety of wizards and utilities for adding and removing
network elements, making configuration changes to physical and logical
network elements, and performing data validation
• validates data against business rules and recommended values
In the Client process:

1. CACP Client connects to the CACP Server located on the BSS Manager
for the system you want to work on. With multi-version support you
launch a separate Client for each version. For instance, if you connect
to a 13.0 BSS Manager, the 13.0 Client launches. If you connect to a
14.0 BSS Manager, the 14.0 Client launches.
2. Configuration data is requested and the CACP Server relays BSMCI,
CLI, and TurboIF queries to the Client.
3. The Client stores the configuration data in its local store. When
configuration data at the BSS Manager changes while in online mode,
you are notified every five minutes to make sure the data in the Client is
up to date.
4. Once data is imported, the Client application can then work offline.
However when the data is ready to be committed to the system the
Client must reconnect to the CACP Server and come back online. Then

NN20000-126 04.30 Standard
.
18 CACP components
data will need to be refreshed based on the latest datafill on the system
and verified against business rules. The longer you stay offline in a
system where the datafill changes, the more problematic this is. Local
data and BSS Manager data will become further out of sync.
Configuration activities can be performed by the CACP Client application

once the CDMA system data set is imported. This data set is initially
retrieved from an active BSS Manager. Modifications are made to this
imported data set locally and are not submitted to the BSS Manager
database until you choose to commit the data. System data from multiple
BSCs can be imported to a single CACP Client application.
CACP Client provides the data editing tools for configuring and tuning
the CDMA configuration. Some of these tools are wizards for network
expansions such as Base Station Transceiver Subsystem (BTS) and
Selector Bank Subsystem (SBS) expansions, Pilot Database (PDB) utilities,
spreadsheet style editing of data, checking for configuration errors, and
so on.
The CACP Client keeps track of changes made to the original data set of
a session. Changes are tracked relative to the original data set that was
initially retrieved from the BSS Manager.
The current configuration data in the CACP Client can be saved to a session
file and later retrieved. Only data for a single BSC is saved in a single
session file. The session file can be shared among different users.
Partial data sets (for example, data from Row View) can be exported to
a tab-delimited text file and then imported to an Excel spreadsheet for
viewing and editing. Text files can be imported back into the CACP Client
for additional editing.
CACP Server
The CACP Server is a daemon process that runs on the BSS Manager. The
primary function of the CACP Server is to provide an external interface
through which up to ten CACP Clients on remote hosts can communicate
with the BSS Manager to retrieve configuration queries and apply
configuration changes. Clients communicate with the CACP Server using a
simple proprietary messaging protocol over TCP.
The CACP Server validates logins for CACP Clients from the MFT
framework where the logins and passwords are stored. The existing BSS
Manager security rules are enforced for configuration changes submitted
by CACP Clients.

NN20000-126 04.30 Standard
.
CACP Server 19
ATTENTION
If you attempt to connect to an online BSSM where the CACP daemon is running
and you provide an incorrect login ID and password, an error message appears
and the login dialog box closes. You must reopen the login dialog box.
CACP Clients submit configuration changes to the Server. The CACP

Server delivers scripts to the appropriate process (BSMCI, CLI, TurboIF).
Each process executes the scripts and provides a log message. The Server
sends the results back to the Client.
The CACP Server sends query responses to the Clients upon request.
These queries can encompass the entire configuration data set, or can
consist of the changes relative to a previous query.
The CACP Server obtains the configuration data by reading directly from the
BSS Manager database. To reduce database access and speed up queries,
the CACP Server caches the configuration data in memory.

NN20000-126 04.30 Standard
.
20 CACP components

NN20000-126 04.30 Standard
.
21
Functionality
The CDMA Access Configuration and Provisioning (CACP) application
simplifies the current configuration process and significantly improves its
efficiency, making it less error prone and less manually intensive.
Functionality navigation
• "Base functionality" (page 21)
• "Compact Metro Cell" (page 22)
• "eDCG support" (page 22)
• "Multi-version support" (page 23)
• "PDB on C-EMS" (page 23)
Base functionality
CACP provides the following functionality:
• online and offline modes of operation
• save and open work-in-progress Base Station Controller (BSC) data
• manual refresh of Client data
• user security validation for online connectivity with existing Base Station
Subsystem Manager (BSS Manager) user security
• data retrieval and submission of BSS Manager configuration data with
BSC identification validation
• data retrieval and submission of CDMA backhaul and routing subsystem
(CBRS) and CDMA packet data subsystem (CPDS) frame provisioning
data
• configuration change notification for the CACP Client application in the
online mode
• Radio Frequency (RF) configuration and network engineering
functionality
• customizable column views for the CACP application’s grid editing layout

NN20000-126 04.30 Standard
.
22 Functionality
• wizards and utilities that guide you through complex operations such as
network expansion, port management, multi-BSC operations, and Pilot
Database (PDB) configuration
• multi-version configuration for one BSC at a time
• multi-version support for multi-BSC PDB reconciliation
• multi-version support for Rehome BTS
• multi-version support for ISSHO BTSs BCNv2
• business rules validation across network components within a BSC
before committing configuration changes
• report generation
Compact Metro Cell

CACP supports the configuration and provisioning of Compact Metro Cell
components, following the same functionality as provided for Metro Cells.
Note that not all Metro Cell functionality is available for Compact Metro
Cells. Refer to "Restrictions, dependencies, and limitations navigation"
(page 131) for more information.
Refer to the following sections for detailed Compact Metro Cell information:
• "Tools" (page 54)
• "Compact MetroCell Indoor BTS wizard" (page 70)
• "Compact Metro Cell MultiBTS CEM wizard" (page 77)
For Compact Metro Cell related procedures, refer to Metro Cell and
Compact Metro Cell (CACP) Configuration Management (NN20000-167).
For Compact Metro Cell validation rules, refer to CDMA Access

Configuration and Provisioning (CACP) Operational Administration
(NN20000-125).
eDCG support
CACP Client supports enhanced Digital Control Group (eDCG) configuration
and provisioning for Metro Cells containing one or two eDCG modules. The
eDCG consists of a new Control Module (CM-2) and a new CORE Module
(CORE-2) as an upgrade to the DCG’s CM and CORE modules. The eDCG
provides increased call processing capability to the Metro Cell base station.
Metro Cells with eDCG support up to six carriers on a single eDCG, and
allow up to eight T1/E1 links per eDCG.

NN20000-126 04.30 Standard
.
PDB on C-EMS 23
Refer to the following sections for detailed eDCG information:

For eDCG validation rules, refer to CDMA Access Configuration and

Provisioning (CACP) Operational Administration (NN20000-125).
Multi-version support
Multi-version support allows use of multiple NBSS releases, such as 14.0,
13.0, or a combination thereof. This means that you can connect to a
different BSS Manager (different version) as long as the version of the BSS
Manager is supported. The number of BSS Manager versions that are
backward compatible with the CACP Client is set to one. For example, a
14.0 Client does not support a BSS Manager Server running version 12.1,
but does support 14.0 and 13.0.
A single CACP Client window contains only BSCs on the same release.
When you load a new BSC (either from a session file or online), that BSC
appears in the appropriate CACP Client window for that release. A new
CACP window is created if no other BSCs on that release are loaded. With
multi-version support you launch a separate Client for each version. For
instance, if you connect to a 14.0 BSS Manager, the 14.0 Client launches. If
you connect to a 13.0 BSS Manager, the 13.0 Client launches.
Multi-BSC PDB reconciliation is the only cross-BSC operation provided
between BSCs of different versions. BTS re-homes are not included.
Refer to the following sections for detailed multi-version support information:
• "Recommended values" (page 127)
Refer to CDMA Access Configuration and Provisioning (CACP) Operational

Administration (NN20000-125) for multi-version support validation rules and
for multi-version support impact on validating and committing data.
PDB on C-EMS
The PDB on CDMA - Element Management System (C-EMS) supports
PDB for CPDS subsystems. It extends the functionality of the existing
SystemPilotDatabase and SystemSelectorSubsystem Managed Objects
(MO) to act as masters of the PDB attributes for CPDS subsystems. It
eliminates the need to support one copy of the PDB data set for each Data
and Selection Function Processor (DSFP) card and makes the centralized
SystemPilotDatabase and SystemSelectorSubsystem MOs furnish the PDB
attributes to all the DSFP cards that need them.

NN20000-126 04.30 Standard
.
24 Functionality
CACP provides only the capability to edit the PDB attributes in the
SystemPilotDatabase MO and the SystemSelectorSubsystem MO and to
perform the DistributeToAll action on these MOs. CACP does not allow
editing on the new DSFPScratchPad MOs. It also does not support any
actions other than the DistributeToAll action on the SystemPilotDatabase,
SystemSelectorSubsystem, or DSFPScratchPad MOs.
For MO information, refer to BSM Configuration Reference Manual

(411-2133-104).

NN20000-126 04.30 Standard
.
25
Navigating the application

Navigation the application describes the CDMA Access Configuration and
Provisioning (CACP) graphical user interface (GUI) and how to use it.
Navigating the application navigation

• "Main window" (page 25)
• "Menu bar and tool bar" (page 26)
• "Navigator panel" (page 27)
• "Editing panel" (page 32)
• "Message panel" (page 46)
• "Preferences" (page 47)
Main window
The CACP main window (see Figure 2 "CACP Main window" (page 26))
consists of five areas:
• menu bar
• tool bar
• Navigator panel
• Editing panel
• Message panel
The Navigator panel, Editing panel, and Message panel are linked, each
displaying a different type of information from the active data set.

NN20000-126 04.30 Standard
.
26 Navigating the application
Figure 2
CACP Main window
Menu bar and tool bar

Refer to "Menus" (page 51) for detailed information on CACP menus.
The tool bar displays the icons shown in "Menus" (page 51). Tool tips
display when you position the cursor over the icon.
You can hide the tool bar using the Tool Bar toggle option in the View menu.
A check mark next to Tool Bar displays the tool bar in the window.

NN20000-126 04.30 Standard
.
Navigator panel 27
Tool bar buttons and menu items are dimmed if the proper prerequisite
steps are not performed, or if the feature is already open. Tool bar buttons
and menu items also can be unavailable if the necessary information is not
found in the active data set or buffers.
Navigator panel
The Navigator panel displays the configuration data hierarchy in a tree
format, similar to the Windows Explorer interface. The elements in the tree
represent network element types, individual network elements, components
within a network element, and so on. Tree levels can be expanded or
collapsed to control the visibility of different parts in the hierarchy. Figure
3 "Network element tree" (page 28), Figure 4 "Network element tree -
CBRS / CNFP components" (page 29), Figure 5 "Network element tree -
CPDS components" (page 30), and Figure 6 "Network element tree - CSVS
components" (page 31) show the hierarchical format of the network element
tree that displays in the Navigator panel.
The Navigator panel groups and displays network elements by type:

BTS, LOGICAL BTS, SBS, MTX, OVERHEAD, FLEXPOWER, SYSTEM
PARAMETERS, PAGING ZONE, CELLID, and PASSPORT. All nodes in
uppercase are string nodes added for grouping elements.

NN20000-126 04.30 Standard
.
Figure 3
Network element tree

NN20000-126 04.30 Standard
.
Navigator panel 29
Figure 4
Network element tree - CBRS / CNFP components

NN20000-126 04.30 Standard
.
Figure 5
Network element tree - CPDS components

NN20000-126 04.30 Standard
.
Navigator panel 31
Figure 6
Network element tree - CSVS components
ATTENTION
12pDS3/12pE3/4pOC12/4pSTM4 cards are not supported in CACP, but could
display in the Navigator tree. You can view the properties only for these cards.

NN20000-126 04.30 Standard
.
The CACP Client tracks changes made to the original data set of a session.
These changes are tracked relative to the original data set that was initially
retrieved from the Base Station Subsystem Manager (BSS Manager) (by
online connection to that BSS Manager).
The Navigator panel drives the editing panel (see "Editing panel" (page 32)).
Depending on the object you select in the Navigator panel tree, the other
panels update to display applicable information.
Specific views and tools can be selected through the Navigator panel
instead of the menu bar. The object you select determines which tools or
views are available. Some objects in the Navigator panel can be added,
copied-pasted, cloned, or configured. Depending on the object you select, a
dialog box or a wizard appears to perform these operations.
Most objects in the Navigator panel can be deleted in the Navigator panel.
For any object to delete, all child tree objects are also deleted. Note that
there is no undo delete functionality.
Editing panel
The editing panel displays information in different layouts for the three view
types: Port Map View, Row View, and Data Compare View. Refer to CDMA
Access Configuration and Provisioning (CACP) Operational Administration
(NN20000-125) for editing procedures.
Port Map View

The Port Map View is the default view when you load BSC session data
(see Figure 7 "Main Window - Port Map View" (page 33)). The editing panel
displays a separate tab for each BSC labeled by the BSC ID and contains
sub-tabs that provide Distribution and Consolidation (DISCO) and CDMA
backhaul and routing subsystem (CBRS) port management capabilities and
CBRS provisioning.
• Each BSC tab displays the Port Map sub-tab. DISCO and CBRS port
maps graphically display in separate windows within this sub-tab. You
can find ports and assign ports to network elements as well as clear
port assignments from this sub-tab.
• If you have a CBRS system, each BSC tab displays the CBRS Frame
(Figure 8 "CBRS Frame Panel—E1 configuration" (page 34)) sub-tab.
This tab graphically displays CBRS frames and allows you to provision
CBRS frame Functional Processors (FP).
• If there is any CPDS in the network, each BSC tab displays the CPDS
Chassis (Figure 9 "CPDS Chassis Panel" (page 35)) sub-tab. This tab
graphically displays all CPDS frames and allows you to provision 4pOC3
and 4pSTM1 cards.

NN20000-126 04.30 Standard
.
Editing panel 33
• If a CSVS shelf exists, each BSC tab displays the CSVS sub-tab.
Figure 7
Main Window - Port Map View
ATTENTION
12pE3/4pSTM4 (E1) and 12pDS3/4pOC12 (T1) cards are not supported in CACP,
but could display in the Navigator tree You can view the properties only for these
cards.
The CPDS cards (DSFP/PCUFP) are view-only. No datafill provisioning capability
is provided.
The CNFP cards are view-only. No datafill provisioning capability is provided.
The CSVS cards (DSFP-V/2pVS) are view-only. No datafill provisioning capability
is provided.

NN20000-126 04.30 Standard
.
Position the cursor on a Base Station Communication Network (BCN)

port to display the subsystem name assigned to that port. Port conflicts
are marked in red. Subsystems not assigned to a port are marked as
unassigned hardware in the Navigator panel in blue.
Use the Tips button (question mark icon) to display Port Map help including
a legend and recommendations.
Figure 8
CBRS Frame Panel - E1 configuration
As shown in Figure 8 "CBRS Frame Panel—E1 configuration" (page 34),

all the CBRS frames belonging to the same BSC are grouped under the
CBRS Frame tab in the Port Map View.

NN20000-126 04.30 Standard
.
Editing panel 35
Figure 9
CPDS Chassis Panel
As shown in Figure 9 "CPDS Chassis Panel" (page 35), all the CPDS
frames belonging to the same BSC are grouped under the CPDS Chassis
tab in the Port Map view. In this tab you can see all CPDS frames as well
as the CPDS configuration. It is also possible to create and delete 4pOC3
and 4pSTM1 cards using the drag and drop operation but services like
ISTL, BISC, and Router are read-only.
In addition to the DISCO Port Map panel (as seen in Figure 7 "Main Window
- Port Map View" (page 33)), CACP also has individual panels for the
24pBCNW card (see Figure 10 "24pBCNW Port Map" (page 36)) and the
11pMSW card (see Figure 11 "11pMSW Port Map" (page 37)). These
panels show the ports and the subsystems assigned to those ports, if any.
All the three types of Port Map panels are grouped under the Port Map
tab. The CBRS frames and the Port Map panels are visible only in the
Port Map View.

NN20000-126 04.30 Standard
.
Figure 10
24pBCNW Port Map

NN20000-126 04.30 Standard
.
Editing panel 37
Figure 11
11pMSW Port Map
Clear the appropriate traffic range check boxes above the grids in the Port
Level View to turn off visibility to those ports. Selecting the traffic range
check boxes again makes the port data reappear.
Through the 11pMSW Port Map, you can provision a BTS port. Select an
available (that is, free) port in the 11pMSW Port Map panel, right-click on
it, and select the Configure Port option. The 11pMSW Port Configuration
dialog box appears (see Figure 12 "11pMSW Port Configuration dialog
box" (page 38)).

NN20000-126 04.30 Standard
.
Figure 12
11pMSW Port Configuration dialog box
Edit 11pMSW and 24pBCNW properties by right-clicking on the element

in the Navigator panel and selecting Edit. The Edit Property dialog box
displays the hardware properties of the selected port (see Figure 13
"11pMSW Edit Property dialog box" (page 39) and Figure 14 "24pBCNW
Edit Property dialog box" (page 40)).

NN20000-126 04.30 Standard
.
Editing panel 39
Figure 13
11pMSW Edit Property dialog box

NN20000-126 04.30 Standard
.
Figure 14
24pBCNW Edit Property dialog box
Row View
The Row View (Figure 15 "Main Window - Row View" (page 41)) shows
the data related to network elements (selected in the Navigator panel,
see "Navigator panel" (page 27)) in a spreadsheet-like grid format in the
editing panel. You can scroll through the data, edit individual field values,
copy and paste cell values, fill ranges of cells and perform other typical
spreadsheet-type functions. The information displayed in the grid panel is
determined by both the current element selected in the Navigator panel, and
by the currently active column view (see "Column views" (page 43)). An X in
a grid cell indicates that the field is not applicable.
Non-settable properties that cannot be configured from the BSS Manager

(that is, gettable-only BSS Manager attributes) are dimmed. Loader Image
Protocol (LIP) version fields are dimmed and cannot be configured.

NN20000-126 04.30 Standard
.
Editing panel 41
Some properties cannot be directly edited in their cell and are dimmed. This
is because the CDMA datafill is a complex structure of related tables. The
integrity of such complex relationships cannot be maintained by allowing
direct edit of the cell. For such cells, double-click on the cell to display a
separate editing panel or use the appropriate wizard or utility.
ATTENTION
There is no Row View associated with editing attributes on FPs or CBRS ports.
Figure 15
Main Window - Row View
Data Compare View

The Data Compare View (Figure 16 "Main Window - Data Compare View"
(page 42)) compares the configuration of multiple network elements of the
same type (those selected in the Navigator panel, see "Navigator panel"
(page 27)) against each other. The comparison displays in a grid format
with one column per selected network element and one row per property.
The first column representing a network element is the baseline column.

NN20000-126 04.30 Standard
.
Property values that are changed in the active data set are visually displayed
in the editing panel by color-coding.
• Original—Property values unchanged from the original data set display
in black.
• Changed—Changed property values display in blue.
• Additions—Property values for added network elements display in green.
These modifications also display in the Navigator panel.

• Changed—Changed property values display in blue.
• Additions—Property values for added network elements display in green.
Figure 16
Main Window - Data Compare View

NN20000-126 04.30 Standard
.
Editing panel 43
Column views
The column view controls the display of data in the Row View’s editing panel.
It determines which columns are displayed in the grid, as well as the sorting
criteria used to order the rows. You can edit the active column view (that is,
add and remove columns, move columns, and so on) from the grid layout.
CACP provides a number of different default column views, which you can
customize or clone to create your own column views. Each column view is
specific to a particular network element type (see Figure 17 "Column view
selection" (page 43)). For example, the SectorView column view can have
fields related to PDB and sector-level BSMCI tables; the BtsView column
view can have fields related to the BTS-level BSMCI tables.
Figure 17
Column view selection
CACP stores views in preferences files. You can edit and save customized
views in a file called custom.cvf. When you start CACP the file default.cvf is
automatically imported. If the custom.cvf file exists, then CACP renames it
to custom.old.cvf. You can still import custom.old.cvf, thereby retaining your
customized settings, by selecting <node> > Manage views > Import.

NN20000-126 04.30 Standard
.
To import views corresponding to BSMCI tables, use the BSMCITables.cvf

file located where CACP is installed on your hard drive.
When exiting CACP, a confirmation dialog box prompts you to selectively
save modified column views in the custom.cvf file.
Customize the set of columns displayed in the current view using the Select
Columns dialog box (Figure 18 "Manage Column View - Select Columns
dialog box" (page 44)).
Figure 18
Manage Column View - Select Columns dialog box
The list on the right shows the set of columns (that is, fields) displayed in the
current view. It also indicates the order in which those columns appear. The
list on the left shows all available columns that are not currently selected.
Customize the sorting criteria for the current view using the Sort Order dialog
box (Figure 19 "Manage Column view - Sort Order dialog box" (page 45)).

NN20000-126 04.30 Standard
.
Editing panel 45
Figure 19
Manage Column view - Sort Order dialog box
The list on the right shows all of the columns used to sort the rows in the
grid panel. The first column is used as the primary key, the second column
as the secondary key, and so on. The list on the left shows all available
columns that are not currently part of the sort criteria.
You can create a new view by using the Manage Views dialog box (Figure
20 "Manage View dialog box" (page 46)).

NN20000-126 04.30 Standard
.
Figure 20
Manage View dialog box
CACP offers the ability to import and export column views. This is useful for:
• sharing commonly used column views
• duplicating commonly used column views to several PCs
• recovering default column views after making modifications

Administration (NN20000-125) for importing and exporting procedures.
Message panel
The message panel displays messages generated by various operations
you invoke. Message types include informational messages, error
messages, and operation status.
The message panel is tabbed. The Info tab is the main message tab and
is displayed by default and cannot be closed. Messages in this tab can be
saved to a text file. Refer to CDMA Access Configuration and Provisioning
(CACP) Operational Administration (NN20000-125) for saving procedures.

NN20000-126 04.30 Standard
.
Preferences 47
Other tabs open automatically when you invoke the corresponding operation
from CACP. You can close these tabs.
• Check Rules tab—Displays results of the Check Business Rules
operation.
• Check Reciprocity tab—Displays results of the Check Neighbor
Reciprocity operation.
• Check Reconciliation tab—Displays results of the Check PDB/BTS
NeighborList Reconciliation operation.
• Unassigned Objects tab—Displays results of the Show Unassigned
Elements operation.
• Port Conflicts tab—Displays results of the Show Port Conflicts operation.
• BCNv2 Compliance tab—Displays results of the Intra-BSC BCNv2
Compliance operation.
• Check Neighbor Consistency Across Carriers—Displays results of the
Propagate NLIST/CDMANLIST to All Carriers operation.
These tabs include features to help you resolve issues. These features
are available from a panel-specific menu (right-click anywhere in the tab
to see this pop-up menu).
• You can sort, restore to original sequence, remove, and save to text file
messages within the tabs.
• You can invoke the Go To Data feature (by double-clicking) and update
the editing panel to display the data related to the message.
• You can filter displayed results to show only Info messages, Warnings,
or Errors.
If there are more messages in a tab than fits in the text area, a scroll bar
appears on the right. Also, you can resize the message panel.
Preferences
Preferences are saved on the local PC. After starting CACP Client, you can
edit preferences for the tool’s operation to override the default preferences
(see Figure 21 "Preferences dialog box - File Path Settings" (page 48),
Figure 22 "Preferences dialog box - Debug Log Settings" (page 48), and
Figure 23 "Preferences dialog box - General Settings" (page 49)). For
procedures on setting preferences, refer to CDMA Access Configuration
and Provisioning (CACP) Operational Administration (NN20000-125).

NN20000-126 04.30 Standard
.
Figure 21
Preferences dialog box - File Path Settings
Figure 22
Preferences dialog box - Debug Log Settings

NN20000-126 04.30 Standard
.
Preferences 49
Figure 23
Preferences dialog box - General Settings
File path settings

The File Path Settings tab of the Preferences dialog box lets you choose
directories on your local drive or a mapped network drive for:
• Importing and exporting
— Session file path
— Subset file path
— Market Info file path
— Customer Recommended Values file path
• Saving scripts
The default data path for these file types is the original installation path for
the Client; that is, C:\\Program Files\\Nortel Networks\\CACP Client.
CAUTION
If you change the Customer Recommended Values (CRV) file
path to a location other than where the file was initially installed,
you must move the default Nortel Recommendations file to the
changed path. If you do not, you will not be able to use the
Recommended Values portion of the Business Rules Check.
Debug log settings

The Debug Log Settings tab of the Preferences dialog box lets you specify
debug parameters including:
• Number of log files per session
• Maximum number of session log groups

NN20000-126 04.30 Standard
.
• Maximum log file size

• Enable trace log
• Debug log file path
The default log file path is the original installation path for the Client; that is,
C:\\Program Files\\Nortel Networks\\CACP Client.
General settings
The General Settings tab of the Preferences dialog box lets you specify
general parameters for CACP, including:
• Enforcing or relaxing business rules. With business rules relaxed, you
can view scripts and save scripts to a file if business rules errors exist.
CACP does not allow online committing of data with business rules
relaxed, but you can execute the scripts in an offline mode.
• Enabling or disabling automatic garbage collection. Garbage collection
frees memory on the client PC.

NN20000-126 04.30 Standard
.
51
Menus
Menu items are dimmed if the proper prerequisite steps have not yet been
performed, or if the feature is already open. For example, unless a session
file is open (offline mode), most all functions are not available. Menu items
also can be unavailable if the necessary information is not found in the
active data set or buffers.
Invoke menu bar elements from a mouse or pressing the Alt key and the
character key that corresponds to the underlined letter in a menu title and
menu item (for example, Alt+F for the File menu).
Menus navigation
• "File" (page 51)
• "Edit" (page 53)
• "View" (page 53)
• "Tools" (page 54)
• "Help" (page 57)
File
The File menu has twelve main options. You can also access the File menu
using Alt+F on the keyboard.
• Load BSC data
— From Session File—Loads Base Station Controller (BSC)
configuration data from a session file. A file chooser window
appears. The tool bar icon is:
— From Online BSSM—Loads BSC configuration data from a Base

Station Subsystem Manager (BSS Manager). A log on window for
connecting to a BSS Manager appears. After successful log on, an
indicator bar displays the progress and completion of the operation.

NN20000-126 04.30 Standard
.
52 Menus
The BSS Manager remains online after retrieving BSC data. The
tool bar icon is:
• Save—Saves an active session file. A list shows all the active BSCs
(identified by BSC_ID parameter on the BSS Manager). Select any one
active BSC from the list. The tool bar icon is:
• Save As—Saves an active session file with a new name. A list shows all
the active BSCs (identified by BSC_ID parameter on the BSS Manager).
Select any one active BSC from the list.
• Close—Closes an active session file. A list shows all the active BSCs
(identified by BSC_ID parameter on the BSS Manager). Select any one
active BSC from the list. A confirmation window displays and prompts
you to save the data. The tool bar icon is:
• Connect to BSS Manager—Connects to the BSS Manager associated

with an active session file. A list shows all the active BSCs (identified by
BSC_ID parameter on the BSS Manager). However, only offline BSCs
(BSS Managers) are available for selection. Select any one active BSC
from the list. A log on window displays to go online with the associated
BSS Manager. With multi-version support you launch a separate Client
for each version. For instance, if you connect to a 13.0 BSS Manager,
the 13.0 Client launches. If you connect to a 14.0 BSS Manager, the
14.0 Client launches.
• Disconnect from BSS Manager—Disconnects from the BSS Manager
associated with an active session file. A list shows all the active BSCs
(identified by BSC_ID parameter on the BSS Manager). However, only
online BSCs (BSS Managers) are available for selection. Select any one
active BSC from the list. A confirmation window displays.
• Refresh Data—Downloads the latest configuration data from the online
BSS Manager to refresh the active session file. A list shows all the
active, online BSCs (identified by BSC_ID parameter on the BSS
Manager). The Data Refresh Wizard displays to complete the operation.
• Commit/Generate Script—Commits the local changes in the active
session file to the associated online BSS Manager. A list shows all the
active, online BSCs (identified by BSC_ID parameter on the BSSM). The
Data Commit Wizard displays to complete the operation.

NN20000-126 04.30 Standard
.
View 53
• Commit Data—Commits the local changes in the active session file to

the associated online BSS Manager. A list shows all the active, online
BSCs (identified by BSC_ID parameter on the BSS Manager). The Data
Commit Wizard displays to complete the operation.
• Export Subset File—Exports the active rows to a tab-delimited text file.
This menu option is available only in the Row View. You must preselect
the active rows from the grid layout in the editing panel.
• Import Subset File—Imports rows from a tab-delimited text file. This
menu option is available only in the Row View.
• Import Market Info File—Imports a selected Market Info file for use in
the current CACP session.
• Exit—Exits the CACP application. A confirmation window displays and
prompts you to save active data to session files (online and offline
sessions). Online sessions are automatically disconnected. You can
also exit using Alt+X on the keyboard.
Edit
The Edit menu has two options. You can also access the Edit menu using
Alt+E on the keyboard.
• Preferences—Edits the data path, debug log, and general settings.
Refer to "Preferences" (page 47) for dialog box information. Refer to
CDMA Access Configuration and Provisioning (CACP) Operational
Administration (NN20000-125) for procedural information.
• Recommended Values—Edits and saves the customer recommended
values file.
View
The View menu has three window views and the tool bar toggle option. You
can also access the View menu using Alt+V on the keyboard.
• Port Map View—Displays the Main window - Port Map View in the
editing panel. The tool bar icon is:
• Row View—Shows the data related to network elements (selected in the

Navigator panel) in a spreadsheet-like grid format in the editing panel.
The tool bar icon is:
• Data Compare View—Compares the configuration of multiple network

elements of the same type (those selected in the Navigator panel)
against each other in the editing panel. The comparison is displayed in

NN20000-126 04.30 Standard
.
54 Menus
a grid format with one column per selected network element and one
row per property. The tool bar icon is:
• Tool Bar—Toggles to show or hide the tool bar.
Tools
The Tools menu contains wizards, utilities, and validation tools. You can
also access the Tools menu using Alt+T on the keyboard.
• BTS Wizards
— MetroCell BTS / Compact MetroCell Outdoor BTS
– Add—Adds a new Metro Cell or Compact Metro Cell Outdoor.
– Clone—Clones a Metro Cell or Compact Metro Cell Outdoor.
– Configure—Configures site information; add a T1/E1; configure
a carrier and add a sector for Radio Frequency Module (RFM);
configure carrier-sector details; add, remove, or change Channel
Element Modules (CEM) or XCEMs; and add a second Digital
Control Group (DCG).
– MultiBTS CEM Add—Adds CEMs to multiple BTSs at a time.
— Compact MetroCell Indoor BTS

– Add—Adds a new Compact Metro Cell Indoor.
– Clone—Clones a Compact Metro Cell Indoor.
– Configure—Configures site information; add a T1/E1; configure
a carrier and add a sector for Radio Module (RM); configure
carrier-sector details; and add, remove, or change XCEMs.
– Multi-cBTS CEM Configure—Adds XCEM cards and reconfigures
common existing XCEM192 cards on multiple Compact Metro
Cell Indoor BTSs at the same time.
• SBS Wizards
— Add SBS Shelves—Adds Selector Bank Subsystem (SBS) shelves.
• PDB Utilities
— Check Neighbor Reciprocity—Globally checks the reciprocity of
neighbors.
— Check PDB/BTS Neighborlist Reconciliation—Checks the Pilot
Database (PDB) neighbor list against the BTS neighbor list for all
sectors.

NN20000-126 04.30 Standard
.
Tools 55
— Repair UNKNOWN Beacon References—Examines and repairs

instances where a component of a Beacon Target list is datafilled as
an unknown band.
— Repair UNKNOWN Border References—Examines and repairs
instances where a component of a Border Target list is datafilled as
an unknown band.
— Repair UNKNOWN EHHO References—Examines and repairs
instances where a cell with cell type EHHO has an entry in the hard
handoff target list that is datafilled as an unknown band.
— Repair UNKNOWN EC References—Examines and repairs
instances where a cell with cell type EC has an entry in the hard
handoff target list that is datafilled as an unknown band.
— Generate Beacon Targets—Autofills the Beacon Target List for
beacon sectors.
— Search-Replace EBID/PilotPN—Globally searches for and replaces
Extended Base Identifications (EBID) (for logical sectors only) or
Pilot Pseudorandom Numbers (PN).
— Check Neighbor Consistency Across Carriers—Checks the
consistency of the NLIST/CDMANLIST across carriers for a
multi-carrier sector. The check can be global on the selected BSC.
• Validation
— Check Business Rules—Validates business rules. Can check
against recommended values also. The tool bar icon is:
— Show Unassigned Elements—Checks which objects in the Navigator

panel are yet to be assigned to the Port Map.
— Show Port Conflicts—Checks neighbor conflicts and port conflicts
between assigned ports on the BCN Port Map.
— BCNv2
– ISSHO BTSs BCNv2 Compliance—Executes the first of two
utilities that verifies whether all preconditions for using BCNv2
have been met.
– Intra-BSC BCNv2 Compliance—Executes the second of two
utilities that verifies whether all preconditions for using BCNv2
have been met.
• Multi-BSC Wizards
— Rehome BTSs—Moves BTSs from one BSC to another.

NN20000-126 04.30 Standard
.
56 Menus
— Reconcile Physical/Logical Sectors—Reconciles the physical sectors

in one BSC with the corresponding logical sectors in another BSC.
• Miscellaneous Utilities
— Fill ARP Lists—Fills the ARP lists for a single sector or all of the
physical, non-1xEVDO sectors in an entire BSC.
• BCNv2
— Assign TRG—Assigns a traffic range group (TRG) to a BSC
— Reconcile TRG on PDB for Physical Sectors—Synchronizes the
value of TrafficRangeGroup in the PDB table with the value in the
DCG MO.
— Rollback TRG on PDB for Physical/Logical Sectors—Sets the value
of TrafficRangeGroup to zero in all sectors present in the PDB table.
Reports
The Reports menu lets you create a variety of reports. You can also access
the Reports menu using Alt+R on the keyboard.
• BSC Configuration Statistics—Creates full configuration report for the
selected BSC. The tool bar icon is:
• BSC Configuration Changes Report—Creates a report showing

configuration changes in a BSC session. The tool bar icon is:
• BSC Comparison Delta Report—Creates delta report for the selected

BSC sessions.
• BCN Port Report—Creates Base Station Communication Network
(BCN) port map report for the selected BSC.
• BTS Provisioning Report—Creates provisioning report for the selected
BTS.
• Redundant DCG Discrepancies Report—Creates report listing Metro
BTSs with redundant DCGs whose configuration data is not the same.
• CFDS Licensing—Creates CDMA Feature Delivery System (CFDS)
license usage report for the BSC. You can select: BSC, All BTSs,
Selected BTSs, All SBS Shelves, and Selected SBS Shelves.

NN20000-126 04.30 Standard
.
Help 57
Help
The Help menu offers information about CACP. You can also access the
Help menu using Alt+H on the keyboard.
• About—Displays information about CACP Client build version and
copyrights.
• About Sessions—Displays information about active BSC session data,
that is, session file name, and first and last date of refresh including the
user and time. You can also use Alt+A on the keyboard.
• CACP Online Help—Displays context-sensitive help information for the
CACP main window and most of the wizards and utilities. You can also
press the F1 key after selecting a CACP window, wizard, or utility.
• Memory Statistics—Displays information regarding the amount of
memory used by the CACP client. It also provides a way for you to run
the Clean-up Memory procedure, which releases unused memory and
improves the performance of the CACP client.
• User Guides—Launches the PDF document. Lists three CACP guides.
— CACP Overview; also can be launched using the F2 key. F2 works
in Row View only if you select the entire row by clicking on the first
column of the row prior to selecting F2.
— CACP Installation & Patching; also can be launched using the F3 key.
— CACP Operational Administration; also can be launched using the
F4 key.
For more information, refer to "User help" (page 125).

NN20000-126 04.30 Standard
.
58 Menus

NN20000-126 04.30 Standard
.
59
Configuration wizards
Configuration wizards describes the CDMA Access Configuration and
Provisioning (CACP) application wizards, including how to access the
wizards, the purpose of each wizard, and the dialog boxes that make up
the wizards.
Configuration wizards navigation

• "Basic usage" (page 59)
• "MetroCell BTS / Compact MetroCell Outdoor BTS wizard" (page 60)
• "Compact MetroCell Indoor BTS wizard" (page 70)
• "Metro Cell MultiBTS CEM wizard" (page 77)
• "Compact Metro Cell MultiBTS CEM wizard" (page 77)
• "SBS wizard" (page 78)
• "Validation wizards" (page 79)
• "Multi BSC wizards" (page 86)
• "Fill ARP Lists wizard" (page 94)
• "BCNv2 wizards" (page 95)
Basic usage
A wizard is an application that guides you through a complex task by
breaking the operation into sequential steps presented as a series of data
entry dialogs. These entry dialogs display default data and request input.
The selections made in one data entry dialog box determine the context of
the next data entry dialog box at each step.
Changes within the dialogs are validated as you move forward through the
wizard. The changes are not applied until you have gone through the entire
wizard. You have the capability to move back and forth between dialogs.

NN20000-126 04.30 Standard
.
60 Configuration wizards
Wizards are invoked from the menu bar. Many wizards can also be invoked
by right-clicking in the Navigator panel and making a selection from the
pop-up menu.
ATTENTION
For Metro Cell and Compact Metro Cell Outdoor, the Configure RFMs wizard
automatically sets the values of PPRE, TPTLE, and CHANPLE to True when
adding a new MFRM-3 radio module, and when changing an existing radio
module to MFRM-3. Setting PPRE, TPTLE, and CHANPLE to False for MFRM-3
results in a business rule error message.
The values of PPRE, TPTLE, and CHANPLE remain True when changing from
MFRM-3 to another module type. Edit the values as required from Row View.
MetroCell BTS / Compact MetroCell Outdoor BTS wizard

The MetroCell BTS / Compact MetroCell Outdoor BTS wizard can configure:
• "Sites" (page 61)
• "T1/E1 trunks" (page 62)
• "RFMs" (page 63)
• "Carrier sectors" (page 66)
• "CEM cards" (page 68)
• "Add second DCG" (page 69)
When adding or cloning a Metro Cell BTS or adding a second DCG to a

Metro Cell BTS, the LIP version fields are set to "<default>". This indicates
that when the new Metro Cell BTS or DCG is committed to the BSS
Manager, the appropriate BSMCI registered LIP files are used to datafill
these LIP version fields.
When cloning an existing Metro Cell BTS, the wizard detects missing PDB
data for sectors. If this erroneous condition is found, the Metro Cell BTS
cannot be cloned. Use the Add BTS Configuration wizard to correct this
error.
ATTENTION
CACP does not maintain any relationship between carrier frequencies and
AdvancedFA MO names for Metro Cell BTSs. When a new BTS is created, CACP
creates and names the carriers in random order. For example, the first carrier that
is created is assigned the MO name AdvancedFA1, the second is AdvancedFA2,
and so on, which may not match the ordering you want. The same ordering of MO
names can occur when you add new carriers to an existing BTS, move carriers
from one DCG to another, or make any field changes that cause the BTS or
individual carriers to be deleted and re-added. You can use the auditfreqorder
tool to produce a report on existing MO names and to modify their values. See
"auditfreqorder tool" (page 139) for more information.

NN20000-126 04.30 Standard
.
Sites
The Configure Site dialog box is the first dialog box displayed when adding
or cloning.
• Option 1: Select the BTS tree root from the Navigator panel, then from
the menu bar select Tools > BTS Wizards > MetroCell BTS / Compact
MetroCell Outdoor BTS > Add.
• Option 2: In the Navigator panel, right-click on the BTS tree root, select
Add, and then Metro Cell BTS.
You can also access this dialog box for editing by selecting Tools > BTS
Wizards > MetroCell BTS / Compact MetroCell Outdoor BTS > Configure >
Site.
The Configure Site dialog box asks for basic information about the BTS
(see example Configure Site dialog box). The second half of the dialog box
enables for split-mate information if the type is set to split.

NN20000-126 04.30 Standard
.
Figure 24
Configure Site dialog box
When you click the Next button, the Configure T1/E1 Trunks dialog box
(Figure 25 "Configure T1/E1 Trunks dialog box" (page 63)) appears.
T1/E1 trunks
You can access the Configure T1/E1 Trunks dialog box through:
• Option 1: Click the Next button on the Configure Site dialog box.
• Option 2: Select the Metro Cell from the Navigator panel, then from
MetroCell Outdoor BTS > Configure > T1/E1s.
• Option 3: In the Navigator panel, right-click on the Metro Cell BTS,
select Configure > T1/E1s.

NN20000-126 04.30 Standard
.
Figure 25
Configure T1/E1 Trunks dialog box
Figure 25 "Configure T1/E1 Trunks dialog box" (page 63) shows a split-mate
configuration. The dimmed fields are read-only and cannot be modified.
When you click the Next button, the Configure RFMs dialog box appears.
RFMs
You can access the Configure RFMs dialog box through:
• Option 1: Click the Next button on the T1/E1 Trunks dialog box.

NN20000-126 04.30 Standard
.
MetroCell Outdoor BTS > Configure > RFMs.
select Configure, and then RFMs.
Figure 26
Configure RFMs dialog box
Figure 26 "Configure RFMs dialog box" (page 64) shows a simplex

configuration. The dimmed fields are read-only and cannot be modified.
Use the Tips button to display information on configuring RFMs. Refer to

Figure 27 "Configure RFMs Tips" (page 65).
To move a carrier-sector, click on an occupied SECTOR or Channel cell and

drag it to the desired unoccupied SECTOR or Channel cell.

NN20000-126 04.30 Standard
.
To clone a carrier-sector, hold down the Ctrl key, click on an occupied

SECTOR or Channel cell, and drag it to the desired unoccupied SECTOR
or Channel cell.
Figure 27
Configure RFMs Tips
To add or modify a frequency, click on the Freq/Unused column. This

enables the Adjust button. Click the Adjust button and the Enter Frequency
dialog box appears (see Figure 28 "Enter Frequency dialog box" (page
65)). If you select 1xEVDO, the frequency column heading includes DO
(data only), for example, DO Freq 283.
Figure 28
Enter Frequency dialog box
To add a carrier, click on a used Freq field in the Configure RFMs dialog
box to enable the Carrier Sector Add, Edit, and Delete buttons. Click the
Carrier Sector Add or Edit buttons, and the Enter Values for Carrier-Sector
dialog box appears (see Figure 29 "Enter Values for Carrier-Sector dialog
box" (page 66)).

NN20000-126 04.30 Standard
.
Figure 29
Enter Values for Carrier-Sector dialog box
ATTENTION
A Single-carrier Flexible Radio Module (SFRM) can have only one frequency. An
MFRM can have at most three frequencies.
When configuring an existing Metro Cell BTS, the Configure RFMs section
of the wizard detects missing PDB data for non-1xEVDO sectors and
detects PDB data present for 1xEVDO sectors. When you click the Next
button, the wizard notifies you of this error and requests to automatically
correct the condition.
The dialog box to appear is the Configure Carrier Sectors dialog box (see
Configure Carrier Sectors dialog box).
Carrier sectors
You can access the Configure Carrier Sectors dialog box through:
• Option 1: Click the Next button on the Configure RFMs dialog box.
MetroCell Outdoor BTS > Configure > Sectors.
select Configure, and then Sectors.

NN20000-126 04.30 Standard
.
Figure 30
Configure Carrier Sectors dialog box
Configure Carrier Sectors dialog box shows a split-mate configuration. The

dimmed cells in the grid are read-only. You can modify the remaining values
as appropriate. The View button toggles between Full View and Brief View.
The Full View button displays all the fields for the frequency-sector pair.
The Brief View button displays the fields BTS Name, Frequency, Sector,
RFM Number, PERPOW, CARPLB, HIGHPOWCAR, Pilot PN, EXTFREQ,
PAGEFREQ, and CL. The field EXTFREQ must be filled in by the user.
When you click the Next button, the Configure CEM Cards dialog box
appears (see Configure CEM Cards dialog box).

NN20000-126 04.30 Standard
.
ATTENTION
The wizard sets the initial value for a new (that is, added) sector’s MARKET field.
That initial value is the same as that of other existing sectors on that BTS. If the
other existing sectors have differing MARKET values or if there are no existing
sectors, then that BTS’s SID value is used as the new sector’s initial MARKET
value. (1xEVDO sectors do not have the MARKET field.)
CEM cards
You can access the Configure CEM Cards dialog box through:
• Option 1: Click the Next button on the Configure Carrier Sectors dialog
box.
MetroCell Outdoor BTS > Configure > CEM Cards.
select Configure, and then CEM Cards.

NN20000-126 04.30 Standard
.
Figure 31
Configure CEM Cards dialog box
Configure CEM Cards dialog box shows a split-mate configuration. The

Channel Element Balance section is read-only. It is useful for multi-carrier,
multi-T1 in helping you determine the slot in which the channel element
card must be placed. The # of C.E. fields change as you choose slots for a
channel element card.
Click on the Finish button when done. Changes are validated. Once
validated, all the changes made throughout the wizard are applied.
Add second DCG

You can access the Add Second DCG wizard by selecting the Metro Cell
from the Navigator panel, then from the menu bar selecting Tools > BTS
Wizards > MetroCell BTS / Compact MetroCell Outdoor BTS > Configure
> Add Second DCG.

NN20000-126 04.30 Standard
.
The Configure Site dialog box of the MetroCell BTS / Compact MetroCell
Outdoor BTS wizard appears with the Type field set to Split and second
half of the dialog box enabled. The Add Second DCG wizard follows the
same flow of dialogs as the Add and Clone Metro Cell wizards, that is,
when you click OK, you go through the Configure T1/E1 Trunks, RFMs,
Configure Carrier-Sectors, and Configure CEM Cards dialogs to complete
the configuration. When finished, the second DCG appears in the Navigator
panel.
Compact MetroCell Indoor BTS wizard

The Compact MetroCell Indoor BTS wizard can configure:
• "Sites" (page 70)
• "T1/E1 trunks" (page 71)
• "RMs" (page 72)
• "Carrier sectors" (page 75)
• "CEM cards" (page 76)
ATTENTION
AdvancedFA MO names for Compact Metro Cell BTSs. When a new BTS is
created, CACP creates and names the carriers in random order. For example, the
first carrier that is created is assigned the MO name AdvancedFA1, the second
is AdvancedFA2, and so on, which may not match the ordering you want. The
same ordering of MO names can occur when you add new carriers to an existing
BTS, move carriers from one DCG to another, or make any field changes that
cause the BTS or individual carriers to be deleted and re-added. You can use the
auditfreqorder tool to produce a report on existing MO names and to modify their
values. See "auditfreqorder tool" (page 139) for more information.
Sites
The Configure Site dialog box is the first dialog box displayed when adding
or cloning.
the menu bar select Tools > BTS Wizards > Compact MetroCell Indoor
BTS > Add.
• Option 2: In the Navigator panel, right-click on the BTS tree root, select
Add, and then Compact Metro Cell BTS.
You can also access this dialog box for editing by selecting a Compact
Metro Cell from the Navigator panel, then selecting Tools > BTS Wizards >
Compact MetroCell Indoor BTS > Configure > Site.

NN20000-126 04.30 Standard
.
The Configure Site dialog box asks for basic information about the BTS (see
example Figure 32 "Configure Site dialog box" (page 71)).
Figure 32
Configure Site dialog box
T1/E1 trunks
You can access the Configure T1/E1 Trunks dialog box through:
• Option 1: Click the Next button on the Configure Site dialog box.
• Option 2: Select the Compact Metro Cell from the Navigator panel, then
from the menu bar select Tools > BTS Wizards > Compact MetroCell
Indoor BTS > Configure > T1/E1s.
• Option 3: In the Navigator panel, right-click on the Compact Metro Cell
BTS, select Configure, and then T1/E1s.

NN20000-126 04.30 Standard
.
Figure 33
Configure T1/E1 Trunks dialog box
The dimmed fields are read-only and cannot be modified.
When you click the Next button, the Configure RMs dialog box (Figure 34
"Configure RMs dialog box" (page 73)) appears.
RMs
You can access the Configure RMs dialog box through:
• Option 1: Click the Next button on the T1/E1 Trunks dialog box.
Indoor BTS > Configure > RMs.
• Option 3: In the Navigator panel, right-click on the Compact Metro Cell,
select Configure, and then RMs.

NN20000-126 04.30 Standard
.
Figure 34
Configure RMs dialog box
The dimmed fields are read-only and cannot be modified.
Use the Tips button to display information on configuring RMs. Refer to

Figure 35 "Configure RMs Tips" (page 73).
Figure 35
Configure RMs Tips

NN20000-126 04.30 Standard
.
To add or modify a frequency, click on the Freq/Unused column. This

enables the Adjust button. Click the Adjust button and the Enter Channel
dialog box appears (see Figure 36 "Enter Channel dialog box" (page 74)). If
you select 1xEVDO, the frequency column heading includes DO (data only),
for example, DO Freq 283.
Figure 36
Enter Channel dialog box
To add a carrier, click on a used Freq field in the Configure RMs dialog
box to enable the Carrier Sector Add, Edit, and Delete buttons. Click the
Carrier Sector Add or Edit buttons, and the Enter Values for Carrier-Sector
dialog box appears (see Figure 37 "Enter Values for Carrier-Sector dialog
box" (page 74)).
Figure 37
Enter Values for Carrier-Sector dialog box
When you click the Next button, the Configure Carrier Sectors dialog box
appears (see Figure 38 "Configure Carrier Sectors dialog box" (page 75)).

NN20000-126 04.30 Standard
.
Carrier sectors
You can access the Configure Carrier Sectors dialog box through:
• Option 1: Click the Next button on the Configure RMs dialog box.
Indoor BTS > Configure > Sectors.
• Option 3: In the Navigator panel, right-click on the Compact Metro Cell,
select Configure, and then Sectors.
Figure 38
Configure Carrier Sectors dialog box
The dimmed cells in the grid are read-only. You can modify the remaining
values as appropriate. The View button toggles between Full View and Brief
View. The Full View button displays all the fields for the frequency-sector
pair. The Brief View button displays the fields BTS Name, Frequency, Sector,
RM Number, PERPOW, CARPLB, HIGHPOWCAR, Pilot PN, EXTFREQ,
PAGEFREQ, and CL. The field EXTFREQ must be filled in by the user.

NN20000-126 04.30 Standard
.
When you click the Next button, the Configure CEM Cards dialog box
appears (see Figure 39 "Configure CEM Cards dialog box" (page 76)).
ATTENTION
The wizard sets the initial value for a new (that is, added) sector’s MARKET field.
That initial value is the same as that of other existing sectors on that BTS. If the
other existing sectors have differing MARKET values or if there are no existing
sectors, then that BTS’s SID value is used as the new sector’s initial MARKET
value. (1xEVDO sectors do not have the MARKET field.)
CEM cards
You can access the Configure CEM Cards dialog box through:
• Option 1: Click the Next button on the Configure Carrier Sectors dialog
box.
the menu bar select Tools > BTS Wizards > Compact MetroCell Indoor
BTS > Configure > CEM Cards.
• Option 3: In the Navigator panel, right-click on the Compact Metro Cell
BTS, select Configure, and then CEM Cards.
Figure 39
Configure CEM Cards dialog box
Click on the Finish button when done. Changes are validated. Once
validated, all the changes made throughout the wizard are applied.

NN20000-126 04.30 Standard
.
Compact Metro Cell MultiBTS CEM wizard 77
Metro Cell MultiBTS CEM wizard

The Metro Cell MultiBTS CEM wizard automates the addition of many
XCEM cards. All the XCEMs must be put in the same shelf slot and same
carrier for all the BTSs selected.
Select the Metro Cell BTSs to which the CEM cards are to be added, then
select Tools > BTS Wizards > MetroCell BTS / Compact MetroCell Outdoor
BTS > MultiBTS CEM Add. The MultiBTS CEM Add dialog box appears
(Figure 40 "MultiBTS CEM Add dialog box" (page 77)). The common
carriers among the selected BTSs list on the left, and the available slots
list on the right.
ATTENTION
This wizard does not apply to Data Only carriers (that is, DOM cards).
Figure 40
MultiBTS CEM Add dialog box
Compact Metro Cell MultiBTS CEM wizard

The Compact Metro Cell MultiBTS CEM wizard automates the
reconfiguration of the existing XCEM192 cards and addition of the new
XCEM64PnP or/and XCEM192 cards into the empty CEM slots. All the
CEMs must be put in the same shelf slot and same carrier for all the BTSs
selected.
Selects the Compact Metro Cell BTSs to which the CEM cards are to be
added, then select Tools > BTS Wizards > Compact MetroCell Indoor BTS
> MultiBTS CEM Configure. The Multi-cBTS CEM Configure dialog box
appears (Figure 41 "Multi-cBTS CEM Configure dialog box" (page 78))
if the following conditions are met:
• All the selected BTSs are Compact. This wizard does not handle mixed
BTS types.

NN20000-126 04.30 Standard
.
• All the selected BTSs have at least either:

— one common empty slot and at least one common frequency
— one common slot having the same XCEM192 card type and the
same channel element subpool assignment.
ATTENTION
This wizard does not apply to Data Only carriers (that is, DOM cards).
Figure 41
Multi-cBTS CEM Configure dialog box
For XCEM192, the channel elements can be assigned in a factor of 32. For
XCEM64PnP, the number of channel elements assigned is 64. A warning
displays if less than 96 channel elements are assigned to an XCEM192.
When you click OK, the new configuration of the CEM cards applies to
each selected Compact Metro Cell.
SBS wizard
The SBS wizard allows you to add SBS shelves. You can access the wizard
in two ways.
• Option 1: Select the SBS tree root from the Navigator panel, then from
the menu bar select Tools > SBS Wizards > Add SBS Shelves.

NN20000-126 04.30 Standard
.
• Option 2: In the Navigator panel, select the SBS tree root, right-click,
and select Add SBS Shelves.
The wizard displays the Add SBS Shelves dialog box (Figure 42 "Add
SBS Shelves dialog box" (page 79)). You can add shelves with different
configurations. Enter the number of cards to add and specify the shelf
parameters. SBS shelf types include: ESBS-SCI, ESBS-SCIS, and
SBS-SCI. The default type is SBS-SCI.
Figure 42
Add SBS Shelves dialog box
When adding an SBS, the LIP version fields are set to "<default>". This
indicates that when the new SBS is committed to the BSS Manager, the
appropriate BSMCI registered LIP files are used to datafill these LIP version
fields.
Validation wizards
The validation wizards can be used for the following:
• "Check Business Rules" (page 79)
• "Show Unassigned Elements" (page 81)
• "Show Port Conflicts" (page 82)
• "ISSHO BTSs BCNv2 Compliance" (page 83)
• "Intra-BSC BCNv2 Compliance" (page 85)
Check Business Rules

The Check Business Rules tool checks object against defined business
rules. Business rules provide error and range checking of the data based on
Nortel recommendations and system requirements.

NN20000-126 04.30 Standard
.
You can choose to check just business rules, or check both business
rules and recommended values. Business rules check the data against
the rules described in CDMA Access Configuration and Provisioning
(CACP) Operational Administration (NN20000-125). You can use the Nortel
recommended values or specify your own recommended values.
ATTENTION
Business Rules Checking does not allow use of a Customer Recommended Value
(CRV) file that is not of the same version as the BSC version.
To begin rule checking, select a BSC from the Navigator panel. Then select
Tools > Validation > Check Business Rules. The Check Business Rules
dialog box appears (Figure 43 "Check Business Rules dialog box" (page
80)).
Figure 43
Check Business Rules dialog box
Once you click OK, a check performs against the established business
rules. When complete, messages display on the Business Rules tab in the
message panel (Figure 44 "Business Rules tab" (page 81)). The business
rule check aborts if reported rule violations exceed the maximum limit of
20000.

NN20000-126 04.30 Standard
.
Figure 44
Business Rules tab
Unassigned elements and port conflicts are included in rule checking. Refer
to "Show Unassigned Elements" (page 81) and "Show Port Conflicts" (page
82).
Show Unassigned Elements

The Show Unassigned Elements tool checks the port map against all
objects in the Navigator panel. The message panel displays those elements
which could be assigned to a port but are not. Selects a BSC and then
select Tools > Validation > Show Unassigned Elements. The Navigator
panel and message panel display the unassigned objects information
(Figure 45 "Unassigned Objects tab" (page 82)).

NN20000-126 04.30 Standard
.
Figure 45
Unassigned Objects tab
The Navigator panel expands to show all unassigned objects and highlights
them in blue. The Unassigned Objects tab in the message panel displays
all the unassigned objects information. Double-click on the Unassigned
Objects row on the message panel to highlight the object on the Navigator
tree and display the Port Map View if it is not displayed already.
Show Port Conflicts

The Show Port Conflicts tool checks the BCN Port Map for neighbor conflicts
(BTS and T1/E1) and port conflicts (more than one type of hardware
assigned to a port). From the Navigator panel, select a BSC and then select
Tools > Validation > Show Port Conflicts. The Port Conflicts tab (Figure 46
"Port Conflicts tab" (page 83)) in the message panel displays each port
conflict in a separate row. Double-click on the row to highlight it and display
the Port Map View if it is not displayed already.

NN20000-126 04.30 Standard
.
Figure 46
Port Conflicts tab
ISSHO BTSs BCNv2 Compliance

The ISSHO BTSs BCNv2 Compliance tool is the first of two utilities
that verifies whether all preconditions for using BCNv2 have been met.
Specifically, it provides the ability to analyze and find, in physical sectors
and their corresponding logical sectors on neighboring BSCs, BTSs that
are involved in ISSHO and also assigned to DISCO. To use this tool, at
least two BSCs must be loaded in the CACP Client. Only two BSCs can be
checked for BCNv2 compliance at a time.
Start this tool by selecting a BSC node from the Navigator panel and then
selecting Tools > Validation > BCNv2 > ISSHO BTSs BCNv2 Compliance.
Figure 47 "ISSHO BTSs BCNv2 Compliance dialog box" (page 84) shows
an example of the dialog box that appears.
Run this tool and ensure that all checks pass before assigning a nonzero
traffic range group (TRG) using "Assign TRG" (page 95).

NN20000-126 04.30 Standard
.
Figure 47
ISSHO BTSs BCNv2 Compliance dialog box
The dialog box identifies the BTSs, with a CONNTYPE of DISCO on the
physical side, that have a corresponding CONNTYPE of ISSHOTR on the
adjacent BSC. When such a BTS is identified, the tool displays a message
stating that this BSC is not compliant and that the BTS involved in ISSHO is
assigned to DISCO.
The MultiBSC Connection dialog box shown in Figure 47 "ISSHO BTSs
BCNv2 Compliance dialog box" (page 84) consists of a grid that shows
all of the BSCs in a particular market as well as the connections (that
is, ISSHO borders) between them. Each box in the grid represents one

NN20000-126 04.30 Standard
.
physical sector of the reference BSC that corresponds to the logical sector
of the neighbor BSC. The neighbor relationship of BSCs is specified by the
currently imported Market Info file.
Cell contents have different meanings:
• If a box does not contain an X, a neighbor relationship does not exist
between the two BSCs.
• If a box contains a dimmed X, one or both of the BSCs are not loaded.
• If a box contains a red X, the two BSCs do have a connection (as
specified by the Market Info file), and that either:
— the corresponding logical/physical cells have not been checked
— a BTS ISSHO border is assigned to DISCO
• If a box contains a green X, the two BSCs do have a connection, the

corresponding logical/physical cells have been checked, and no BTS
ISSHO border assigned to DISCO is found.
• If a box contains a blue X, one or both of the BSCs are not loaded but
the corresponding logical/physical cells have been checked, and no BTS
ISSHO border assigned to DISCO is found.
The color is reset when the CACP Client application is closed and when the
market info file is imported.
To execute the check in the BSCs, select one BSC in the grid, right-click
and select ISSHO BCNv2 Check. The results of the check are displayed
in the message area at the bottom of the dialog box. The result output
can be cleared, selected, or saved.
Intra-BSC BCNv2 Compliance

The Intra-BSC BCNv2 Compliance tool is the second of two utilities
that verifies whether all preconditions for using BCNv2 have been met.
Specifically, it analyzes the current BSC configuration against the validation
rules provided in CDMA Access Configuration and Provisioning (CACP)
Operational Administration (NN20000-125).
You can start this tool in two ways:
• Select a BSC node from the Navigator panel and then select Tools >
Validation > BCNv2 > Intra-BSC BCNv2 Compliance.
• After setting a TRG to a nonzero value using "Assign TRG" (page 95),
select a BSC node from the Navigator panel and then select Tools
> Validation > Check Business Rules. This last method causes all
validation rules to be checked.

NN20000-126 04.30 Standard
.
When the Intra-BSC BCNv2 Compliance tool executes, the full data set is
validated to ensure the data is consistent across the BSC. When the tool
is complete, it creates a BCNv2 Compliance tab in the Message panel as
shown in Figure 48 "Intra-BSC BCNv2 Compliance results" (page 86). Click
the BCNv2 Compliance tab to display the results.
Figure 48
Intra-BSC BCNv2 Compliance results
Multi BSC wizards

The Multi BSC wizards can be used for the following:
• "Rehome a BTS" (page 86)
• "Reconcile PDB across BSCs" (page 91)
Rehome a BTS
Rehoming moves or copies a BTS from one BSC to a neighboring BSC.
There are four types of BTS rehomes:
• Move Physical to Physical—moves BTSs to adjacent BSC

NN20000-126 04.30 Standard
.
• Move Physical to Physical with Logical—moves BTSs to adjacent BSC,

adding logical BTSs to the source BSC
• Copy Physical to Physical—copies BTS from one BSC to a neighboring
BSC
• Copy Physical to Logical—creates Inter-System Soft Handoff (ISSHO)
border between two BSCs using the physical information with valid port
assignment to datafill the logical BTS on a neighboring BSC
— A logical sector is non-physical sector on a BSC. Non-physical
means that there is no BTS hardware for this sector on that BSC.
A logical sector exists only in datafill, that is, in the PilotDataBase
tables. In the context of rehome, the physical to logical copy means
copying the logical sector (that is, PDB datafill) information from
BSC 1 to BSC 2.
The checkbox Edit SID/NID/MARKET/SWITCH shown in Figure 49 "Multi

BSC Rehome - Main Panel" (page 89) lets you set the values of SID, NID,
MARKET, and SWITCH for all BTSs to be rehomed. This option is only
available to the rehome types Move Physical to Physical and Copy Physical
to Physical.
Rehoming has many requirements and restrictions:
• The Rehome menu option enables only if there is more than one BSC
loaded. Both the source and destination BSCs must be loaded in the
CACP Client application.
• Port assignments for rehomed BTSs are not performed as part of the
rehome activity. This is a post rehome activity which can be done
through CACP.
• CACP will not copy a physical to logical if the physical does not have a
port assigned. Unassigned physical BTSs will not be moved or copied
to a logical.
• Rehomes are supported only between neighboring BSCs. This
information must be present in the market info file. Refer to
CDMA Access Configuration and Provisioning (CACP) Operational
Administration (NN20000-125) for more information.
• If multiple BTSs are selected, all those BTSs must belong to the same
BSC. If not, an error occurs.
• Logical BTSs cannot be rehomed.
• The navigator tree is updated for all rehome types.
• When performing a Move Physical to Physical the following activities
take place:

NN20000-126 04.30 Standard
.
— If that BTS has any logical sector on the target BSC, those logical
sectors delete as part of the rehome activity.
— The NeighborList and CDMANeighbor Lists of all the BTSs on the
source BSC update.
— The source BTS deletes and updates on the Navigator panel.
— The NeighborList and CDMANeighborList of the moved BTS copy
as-is.
• When performing a Move Physical to Physical with Logical the following

activities take place:
— If that BTS has any logical sector on the target BSC, those logical
— The NeighborList and CDMANeighbor Lists of all the BTSs on the
source BSC update.
— The source BTS deletes and updates on the Navigator panel.
— The source BTS is added as a logical BTS on the source BSC and
updates on the Navigator panel.
as-is.
• When performing a Copy Physical to Physical the following activities

take place:
— If that BTS has any logical sectors on the target BSC, those logical
as-is.
• When performing a Copy Physical to Logical the following activities

take place:
— If that BTS has any logical sectors on the target BSC, those logical
sectors update as part of the rehome activity.
— The NeighborList of the moved BTS copy as-is.
• After completing the rehome activity, it is recommended that

you run a business rules validation on the target BSC to correct
any NLIST/CDMANLIST errors. If rehome option Move Physical
to Physical with Logical is used, it is recommended you run
a business rules validation on the source BSC to correct the
TrafficRangeGroup/TrafficRange for the newly created logical sectors.
See "Check Business Rules" (page 79).

NN20000-126 04.30 Standard
.
Start the rehome tool by selecting one or more BTSs to be rehomed from
the Navigator panel, then selecting Tools > Multi-BSC Wizards > Rehome
BTSs. Figure 49 "Multi BSC Rehome - Main Panel" (page 89) shows an
example of the Multi BSC Rehome - Main Panel dialog box.
Figure 49
Multi BSC Rehome - Main Panel
When rehoming a Metro Cell BTS, the wizard detects missing PDB data for
non-1xEVDO sectors and detects PDB data present for 1xEVDO sectors. If
these erroneous conditions are found, rehoming cannot be performed for
that Metro Cell BTS. Use the BTS Configuration wizard to correct these
erroneous conditions.
If you attempt to rehome a BTS populated with only 1xEVDO sectors,
and with the Copy Physical to Logical option button selected, the BTS will
not be rehomed. Also if you select multiple BTSs for rehoming—with the
Copy Physical to Logical option button selected—rehoming skips all BTSs
populated with only 1xEVDO sectors. Use the BTS Configuration Wizard
to configure at least one non-1xEVDO sector in both situations so that
rehoming of the BTS/BTSs is possible.
If the Edit SID/NID/MARKET/SWITCH check box is selected in Figure 49
"Multi BSC Rehome - Main Panel" (page 89), clicking Next causes the
following to take place:
• Multi BSC Rehome - Set values dialog box (Figure 50 "Multi BSC
Rehome - Set values" (page 90)) appears. This dialog box lets you
edit the SID, NID, MARKET, and SWITCH values for all BTSs to be

NN20000-126 04.30 Standard
.
rehomed. The fields in Figure 50 "Multi BSC Rehome - Set values"

(page 90) accept integer values only and all four fields must be filled in.
After rehoming, all selected BTSs contain these values.
When you commit data on the target BSC after rehoming the BTSs,
the MARKET value sent to the PDB table is the value you set before
rehoming the BTS.
• When you click OK in Figure 50 "Multi BSC Rehome - Set values"
(page 90), a confirmation dialog box (Figure 51 "Multi BSC Rehome
confirmation dialog box" (page 91)) appears, which displays all the
BTSs, the BSC information, and the type of rehome.
If the Edit SID/NID/MARKET/SWITCH check box is not selected in Figure

49 "Multi BSC Rehome - Main Panel" (page 89), clicking Next opens a
confirmation dialog box (Figure 51 "Multi BSC Rehome confirmation dialog
box" (page 91)) that displays all the BTSs, the BSC information, and the
type of rehome.
Figure 50
Multi BSC Rehome - Set values

NN20000-126 04.30 Standard
.
Figure 51
Multi BSC Rehome confirmation dialog box
If one or more BTSs have errors, a message box displays the error
messages explaining why the rehome was not successful.
Reconcile PDB across BSCs

The Multi-BSC PDB Reconciliation tool provides the ability to analyze,
find, and reconcile inconsistencies between physical sectors and their
corresponding logical sectors on neighboring BSCs. At least two BSCs
must be loaded and only two BSCs can be reconciled at a time.
Start the reconciliation tool by selecting Tools > Multi-BSC Wizards >
Reconcile Physical/Logical Sectors. Figure 52 "MultiBSC Connection dialog
box" (page 92) shows an example of the MultiBSC Connection dialog box.

NN20000-126 04.30 Standard
.
Figure 52
MultiBSC Connection dialog box
The MultiBSC Connection dialog box consists of a grid that shows all of the
BSCs in a particular market as well as the connections (that is, ISSHO
borders) between them. Each box in the grid represents one physical
sector of the reference BSC that corresponds to the logical sector of
the neighbor BSC. The neighbor relationship of BSCs is specified by the
currently imported market info file.
Cell contents have different meanings:
• If a box does not contain an X, a neighbor relationship does not exist
between the two BSCs in the Market Info file.
• If a box contains a dimmed X, one or both of the BSCs are not loaded.
• If a box contains a red X, the two BSCs do have a connection (as
specified by the Market Info file), and that either:
— the corresponding logical/physical cells are not reconciled
— the neighboring BSCs are not set up for ISSHO (that is, no matching
logical/physical cells are found), in which case there is nothing to
reconcile
• If a box contains a green X, the two BSCs do have a connection, and

the corresponding logical/physical cells are reconciled.
When reconciliation is run on a connection and you click OK, the connection
is marked green, even if you did not choose to update all of the sectors. The
tool assumes that if you did not update certain sectors, then the sectors
do not need to be updated.

NN20000-126 04.30 Standard
.
To reconcile the BSCs, select one BSC in the grid, right-click and select
either Reconcile with Reciprocity or Reconcile without Reciprocity. The
Reconciling Logical BSC with Physical BSC dialog box appears (Figure 53
"Reconciling Logical BSC with Physical BSC dialog box" (page 93)).
Figure 53
Reconciling Logical BSC with Physical BSC dialog box
The left side of the dialog box contains a list of all of the sectors that need to
be reconciled. The total number of sectors display along with the number
that needs to be updated. Note that for reconciliation purposes, the physical
sector is considered the master, that is, a logical sector updates with the
values from its associated physical sector.
Specify which sectors to update by clicking the Update check box in

the corresponding sector row. Update the core fields along with the
neighbor-list, by clicking the Update Nlist check box. Note that you
can select the Update Nlist check box only if there are neighbor-list
inconsistencies between the physical and logical sectors.
If you reconcile with reciprocity and choose to update any NList, reciprocity
is automatically maintained. If you reconcile with reciprocity, the NList
reciprocity information is also included in the GUI. If the NList already has
20 neighbors, appropriate messages display in the message panel Info tab.

NN20000-126 04.30 Standard
.
When you select a sector from the list on the left side, the right side updates
with the reconciliation information for that sector. At the top, the Extended
Base ID and sector types for the physical and logical sectors display.
Below that, the inconsistencies in the core fields for the sector display in a
grid format. Each column represents a particular PDB field, and the two
rows represent the value of that field corresponding to the physical and
logical datafill for that sector.
Below the core fields are the neighbor lists for the physical and logical
sectors. Entries in the logical neighbor list are color coded according
to whether they are being added or deleted based on the values in the
physical neighbor-list.
Use the Tips button to display information about reconciling BSCs.
Fill ARP Lists wizard

The Fill ARP Lists wizard allows you to fill the Access Robustness
Performance (ARP) lists for all of the physical, non-1xEVDO sectors in an
entire BSC or fill the ARP lists for a single, physical, non-1xEVDO sector.
You can access the wizard in two ways.
• Option 1: For all of the physical, non-1xEVDO sectors in an entire BSC:
Select the BSC from the Navigator panel, then from the menu bar select
Tools > Miscellaneous Utilities > Fill ARP Lists.
The Fill ARP Lists menu item is disabled if multiple BSCs are selected
or no BSC is selected.
• Option 2: For a single, physical, non-1xEVDO sector: While in Row
View (View > Row View) or Port Map View (View > Port Map View),
select a sector from the Navigator panel, right-click, and select Fill ARP
Lists from the pop-up menu.
The Fill ARP Lists menu item is disabled if multiple sectors are selected.
The wizard displays the Select Fill Type for ARP Lists dialog box (Figure 54
"Select Fill Type for ARP Lists dialog box" (page 95)). You can set all flags
to false, "F", or set flags based on sector type. If you set flags based on
sector type, the flags are set to "T" if the neighbor is a physical sector and
"F" if the neighbor is a logical sector.

NN20000-126 04.30 Standard
.
BCNv2 wizards 95
Figure 54
Select Fill Type for ARP Lists dialog box
BCNv2 wizards
The BCNv2 wizards can be used for the following:
• "Assign TRG" (page 95)
• "Reconcile TRG on PDB for Physical Sectors" (page 96)
• "Rollback TRG on PDB for Physical/Logical Sectors" (page 96)
Assign TRG
The Assign TRG tool allocates a traffic range group (TRG) to a BSC.
Start this tool by selecting a BSC node from the Navigator panel and then
selecting Tools > BCNv2 > Assign TRG. Figure 55 "Assign TRG dialog box"
(page 95) shows an example of the dialog box that appears.
Figure 55
Assign TRG dialog box
You can perform these allocation/de-allocation actions with the Assign TRG
dialog box:
• Set a TRG value from zero to a nonzero value: allocation
• Set a TRG value from a nonzero value to zero: de-allocation

NN20000-126 04.30 Standard
.
You cannot change a TRG value from a nonzero value directly to another
nonzero value. To do this, reset the TRG to zero, uncouple/couple the ports,
set the TRG to its required value, and uncouple/couple the ports again.
This procedure is necessary to avoid MOs in the same BSC from working
with a different TRG.
Use the Check Compliance button to perform a check to ensure that all
preconditions for using BCNv2 have been met. If any compliance issues
are detected during Check Compliance execution, you are prompted to
run "ISSHO BTSs BCNv2 Compliance" (page 83) before changing the
TRG from zero to a nonzero value. Similarly, clicking the OK button after
setting the TRG to a nonzero value displays a prompt if it detects the ISSHO
BTSs BCNv2 Compliance utility has not run or that there are outstanding
compliance issues.
After assigning a TRG, submit your changes to BSS Manager to distribute

the TRG value to the various subsystems. During the submit process, the
full data set is validated against the business rules provided in CDMA
Access Configuration and Provisioning (CACP) Operational Administration
(NN20000-125) to ensure the data is consistent across the BSC.
Reconcile TRG on PDB for Physical Sectors

This tool synchronizes the value of TrafficRangeGroup in the PDB table with
the value in the DCG MO.
Whenever a field value, such as the TRG, is changed in a physical BTS,

the corresponding entry in the PDB table of the neighbor BSCs must be
updated. To resolve any difference, run the Reconcile Physical/Logical
Sectors tool as described in "Reconcile PDB across BSCs" (page 91).
Rollback TRG on PDB for Physical/Logical Sectors

This tool sets the value of TrafficRangeGroup to zero in all sectors present
in the PDB table. This is the first step to rolling back a BSC to BCNv1.
Whenever a field value, such as the TRG, is changed in a physical BTS,

the corresponding entry in the PDB table of the neighbor BSCs must be
updated. To resolve any difference, run the tool described in "Reconcile
PDB across BSCs" (page 91) after you run the rollback tool.

NN20000-126 04.30 Standard
.
97
PDB utilities
CDMA Access Configuration and Provisioning (CACP) offers various Pilot
Database (PDB) utilities. These utilities apply to the SystemPilotDatabase
MO.
PDB utilities navigation

• "Neighbor list reciprocity" (page 97)
• "PDB/BTS Neighborlist reconciliation" (page 100)
• "Propagate NLIST/CDMANLIST to all carriers" (page 106)
• "Repair unknown beacon targets" (page 108)
• "Repair unknown border targets" (page 109)
• "Repair unknown EHHO target references" (page 110)
• "Repair unknown EC target references" (page 111)
• "Generate beacon targets" (page 111)
• "Search-Replace EBID/Pilot PN" (page 113)
Neighbor list reciprocity

The Check Neighbor List Reciprocity utility checks that PDB neighbor lists
have reciprocal entries with their peers. That is, if sector1 has sector2 in its
neighbor list, sector2 requires sector1 in its neighbor list as well. This utility
lets you see if there are any problems with reciprocity and then correct them.
During reciprocity checking, any sector defined as Cell_Pilot_Beacon is
not checked. Also, any neighbor sector defined as Cell_Pilot_Beacon is
not checked.
Figure 56 "Check Neighbor Reciprocity with Peers dialog box" (page 98)
shows an example reciprocity. You can view neighbor list reciprocity in two
ways:
• Select a BSC node from the Navigator panel and then select Tools >
PDB Utilities > Check Neighbor Reciprocity. Double-click on a message
in the Reciprocity tab of the message panel.

NN20000-126 04.30 Standard
.
98 PDB utilities
• Right-click on an NLIST cell in the Row View and select Check Neighbor
Reciprocity.
Figure 56
Check Neighbor Reciprocity with Peers dialog box
The left side of this dialog box displays the Reference Sector and its
neighbor list. Destination Sites whose neighbor list contains a non-reciprocal
neighbor are identified by Non-reciprocal in the Status field.
The sectors defined as Cell_Pilot_Beacon are identified by Beacon in the

Status field. A beacon sector must not have any NLIST entries and is
therefore always a non-reciprocal neighbor. During reciprocity checking,
any sector defined as Cell_Pilot_Beacon is not checked. Also, any neighbor
sector defined as Cell_Pilot_Beacon is not checked.
The right side of this dialog box displays the Destination Site and neighbor
list. Selections made in the Reference Sector neighbor list control the
display of the Destination Site and neighbor list. The Destination Site is the
site that is selected in the Reference Sector neighbor list. The Destination
Site’s neighbor list is the selected site’s neighbor list.

NN20000-126 04.30 Standard
.
Neighbor list reciprocity 99
You can correct a non-reciprocal situation by adding the missing neighbor

to the appropriate neighbor list, or by deleting the non-reciprocal neighbor
from the Reference Site’s neighbor list.
You can change the order of the neighbors in the lists using the Move Top,
Move Up, Move Down, and Move Bottom buttons.
Clicking the Add Reference Sector button in the Destination Site’s Neighbor
List of this dialog box opens the dialog box shown in Figure 57 "Add
CDMANLIST dialog box" (page 99)giving you the ability to add both the
NLIST and CDMANLIST, or the NLIST only.
Figure 57
Add CDMANLIST dialog box
Similarly, clicking any of the three Delete buttons (in the Reference Sector,
in the Destination Site’s Neighbor List, and labelled Delete NLIST from both
Reference and Target Sectors) opens the dialog box shown in Figure 58
"Delete CDMANLIST dialog box" (page 99), giving you the ability to delete
both the NLIST and CDMANLIST, or the NLIST only.
Figure 58
Delete CDMANLIST dialog box
When you click the Delete button in the Destination Site’s Neighbor List, a
check is performed to see if the NLIST entry has a reciprocal entry. If it
does, then after the dialog box in Figure 58 "Delete CDMANLIST dialog box"
(page 99) is complete, the dialog box shown in Figure 59 "Delete Reciprocal
Neighbors dialog box" (page 100) appears, giving you the ability to delete
the reciprocal entry.

NN20000-126 04.30 Standard
.
100 PDB utilities
Figure 59
Delete Reciprocal Neighbors dialog box
PDB/BTS Neighborlist reconciliation

The Check PDB/BTS Neighborlist Reconciliation utility provides the ability to
reconcile the PDB-level neighbor list of a sector with its BTS-level neighbor
(CDMANeighbor) list. For each physical sector in the BSC session data,
CACP compares the sector’s PDB Neighbor List (NLIST) to its BTS CDMA
Neighbor List (CDMANLIST). Differences are listed in the Reconciliation
tab of the message panel.
The utility allows you to:
• align PDB with BTS neighbor list
• copy selected PDB items to the BTS neighbor list
• add an item to the PDB/BTS neighbor list
• delete an item from the PDB/BTS neighbor list
• set priorities in the PDB/BTS neighbor list
• open the Propagate NLIST/CDMANLIST to All Carriers dialog box
You can view neighbor list reconciliation two ways:

• Select Tools > PDB Utilities > Check PDB/BTS Neighborlist
Reconciliation. Double-click on an error row in the Reconciliation tab
(Figure 60 "Reconciliation tab" (page 101)) of the message panel.
• Double-click on a cell in the Nlist or CDMANlist columns within Row View.
Both methods display the Reconcile PDB and BTS CDMA Neighbor Lists
dialog box (Figure 61 "Reconcile PDB and BTS CDMA Neighbor Lists
dialog box" (page 102)).

NN20000-126 04.30 Standard
.
Figure 60
Reconciliation tab
An error is identified when the PDB neighbor list contains neighbors that do
not exist in the BTS CDMA Neighbor list. An information message appears
for instances when the BTS CDMA Neighbor list contains neighbors that are
not included in the PDB neighbor list.

NN20000-126 04.30 Standard
.
102 PDB utilities
Figure 61
Reconcile PDB and BTS CDMA Neighbor Lists dialog box
The arrows in the middle of the dialog box indicate the alignment of the
different neighbor lists. As you add or delete neighbors from the respective
lists, or change the order of the lists, the arrows redraw to indicate the
alignment.
A gray background for any NLIST neighbor row indicates normal, that is, no
error. For a logical neighbor sector, the BTS Name column shows a value
Logical with gray background. A red background for any NLIST neighbor
row indicates error, meaning for that physical neighbor sector there is no
matching CDMANLIST entry. If the BTS Name column shows the value
Missing, then the neighbor sector is not found in the BSC.
The Status column indicates whether each neighbor sector is reconciled or
not. OK (with gray background) indicates that there are no errors.
Missing (with red background) indicates that no sectors are found in the
BSC matching that CDMANeighbor key (that is, PilotPN, frequency, band).

NN20000-126 04.30 Standard
.
ATTENTION
For CDMANeighbors with PCHCfg (for example, NGHBRCFG property) value
of 2 or 3, missing sectors are allowed. Such CDMANeighbors are marked as
OK regardless of whether or not sectors are found in the BSC matching that
CDMANeighbor key (unless this is a duplicate CDMANeighbor, in which case, it is
marked as Duplicate).
To add an entry to a PDB Neighbor List, click the Add button on the
NList panel of Figure 61 "Reconcile PDB and BTS CDMA Neighbor Lists
dialog box" (page 102). The Select PDB Neighbor dialog box (Figure
62 "Select PDB Neighbor dialog box" (page 103)) appears. This dialog
box lists available sectors from the BSC session data. You can filter the
entries in Figure 62 "Select PDB Neighbor dialog box" (page 103) by Pilot
Pseudorandom Number (Pilot PN) and frequency. On this dialog box, the
frequency should be the same.
To filter on Pilot PN, click the dropdown box beside PILOTPN to display all
entries and then select the required entry. The Select PDB Neighbor dialog
box then displays only those neighbors with the selected Pilot PN. To add a
neighbor to the PDB Neighbor List, select the neighbor entry and click OK.
Figure 62
Select PDB Neighbor dialog box

NN20000-126 04.30 Standard
.
104 PDB utilities
To add an entry to a BTS CDMANeighbor List (CDMANLIST), click the

Add button on the CDMANeighbor List panel of Figure 61 "Reconcile
PDB and BTS CDMA Neighbor Lists dialog box" (page 102). The Select
BTS Neighbor dialog box (Figure 63 "Select BTS Neighbor dialog box"
(page 105)) appears. This dialog box lists available CDMANeighbors for
the reference sector from the BSC session data. You can filter the entries
in Figure 63 "Select BTS Neighbor dialog box" (page 105) by Pilot PN,
frequency, or a valid combination of both.
The filter options work as follows:
• Filtering on Pilot PN: Click the dropdown box beside PILOTPN to display
all available Pilot PNs for the CDMANeighbors. Select one of the values
and ensure FREQ is set to All.
• Filtering on frequency: Click the dropdown box beside FREQ to display
all available frequencies for the CDMANeighbors. Select one of the
values and ensure PILOTPN is set to All.
• Filtering on Pilot PN and frequency: From the dropdown boxes, select
a valid combination of PILOTPN and FREQ. Selecting an invalid
combination causes no CDMANeighbor entries to be listed in the dialog
box.
To add a neighbor to the BTS CDMANeighbor List, select the neighbor

entry on Figure 63 "Select BTS Neighbor dialog box" (page 105) and click
OK. If you select an entry where the Pilot PN, frequency, and band are
equal to the reference sector values, an error message appears indicating
you cannot add this CDMANeighbor.

NN20000-126 04.30 Standard
.
Figure 63
Select BTS Neighbor dialog box
A maximum of twenty sectors is allowed in either neighbor list. Duplicate

neighbors cannot be added to either neighbor list.
By default, the sectors are sorted in Figure 62 "Select PDB Neighbor dialog
box" (page 103) and Figure 63 "Select BTS Neighbor dialog box" (page 105)
by Pilot PN. If you select the Sort button, the Sort Order dialog box appears
(Figure 64 "Sort Order dialog box" (page 106)). Select columns and click
the >> or << button to add or remove them from the list of Sort Columns.
Select Ascending or Descending from the Sort Style list. Use the various
Move buttons to arrange the columns in the desired sort order.

NN20000-126 04.30 Standard
.
106 PDB utilities
Figure 64
Sort Order dialog box
Propagate NLIST/CDMANLIST to all carriers

The Propagate NLIST/CDMANLIST to All Carriers utility provides the ability
to propagate NLIST/CDMANLIST entries across carriers for a given sector.
This utility simplifies the process of populating NLISTs and CDMANLISTs
when adding new multi-carrier sites.
You can view NLIST/CDMANLIST propagation in two ways:
• Select Tools > PDB Utilities > Check Neighbor Consistency Across
Carriers. Right-click on a warning row in the resulting Check Neighbor
Consistency Across Carriers tab and select Go to Data from the pop-up
menu.
• Click the Propagate to all Carriers button on the Reconcile PDB and BTS
Neighbor Lists dialog box (Figure 61 "Reconcile PDB and BTS CDMA
Neighbor Lists dialog box" (page 102)). This button is enabled only if
the sector is a multi-carrier. Using this method saves all the changes
you made in the Reconcile PDB and BTS Neighbor Lists dialog box and
displays any relevant changes in the NLIST/CDMANLIST propagation
dialog box.
Both methods display the Propagate NLIST/CDMANLIST to All Carriers

dialog box (Figure 65 "Propagate NLIST/CDMANLIST to all Carriers dialog
box" (page 107)).

NN20000-126 04.30 Standard
.
Propagate NLIST/CDMANLIST to all carriers 107
Figure 65
Propagate NLIST/CDMANLIST to all Carriers dialog box
The top of the dialog box displays the subsystem name/cell ID/band/sector
of the multi-carrier sector. The multi-carrier frequencies are displayed
(with checkboxes) above their respective NLISTs. The reference carrier is
automatically checked off and a different reference carrier can be selected
only by clicking the Apply button.
The NLISTs are comprised of cell/sector entries. If there are less than nine
carriers on the sector, the empty NLISTs are disabled.
The arrows in the dialog box represent NLIST entries that can be
propagated. An arrow is visible if the sector (cell/name) in the reference
channel exists in the destination channel, but the sector is not included in
the destination NLIST. The arrows point away from the reference carrier
towards the destination carriers.
NLIST propagation works as follows:
• Clicking on an arrow beside a destination carrier entry causes the NLIST
entry of the reference carrier on the same row to be propagated to
that destination carrier. For example, clicking on the fifth arrow in the

NN20000-126 04.30 Standard
.
108 PDB utilities
NLIST of a destination carrier causes the fifth entry in the NLIST of the
reference carrier to be propagated to that destination carrier.
• When the propagation occurs, the new entry appears in yellow at the
bottom of the destination carrier’s NLIST and the arrow is disabled.
• You can select and delete NLIST entries. When you delete a propagated
NLIST entry, the arrow becomes enabled again.
• If you want to propagate an entry to an NLIST that already has twenty
entries, you need to first delete an existing entry.
• Logical NLIST entries are also propagated.
• As well as propagating individual entries, you can also propagate the
entire NLIST by clicking the arrow beside the check box of the frequency
of the destination carrier.
• Any entries that are for 1XEV-DO cannot be propagated.
CDMANLIST propagation occurs automatically as follows:

• When the NLIST entry has an associated CDMANLIST entry, the
CDMANLIST entry is also propagated. However if the destination
CDMANLIST is already full, the CDMANLIST entry is not propagated
and an information message is displayed in the message area.
• Deleting an NLIST entry also deletes the associated CDMANLIST entry.
The buttons at the bottom of the dialog box work as follows:

• OK applies all the information currently in the dialog box and then closes
it.
• Delete deletes any selected NLIST entries.
• Align List to Reference Carrier aligns all NLISTs of the destination
carriers to the NLIST of the reference carrier. The closest sector
appears at the top of the list and the farthest appears at the end.
• Cancel closes the dialog box without applying any changes.
• Apply saves all current information and enables the checkboxes beside
the multi-carrier frequencies, which allows you to select a new reference
carrier.
Repair unknown beacon targets

The beacon repair utility globally searches all beacon targets with a band
value set to UNKNOWN and updates the value if a sector is found that
matches the beacon target information (except with a Band of 800 or 1900).
You can choose if the UNKNOWN value must be updated.

NN20000-126 04.30 Standard
.
Repair unknown border targets 109
Start the beacon utility by selecting Tools > PDB Utilities > Repair Unknown
Beacon References. Figure 66 "Repair Unknown BEACON References
dialog box" (page 109) illustrates the Repair Unknown BEACON References
dialog box.
Figure 66
Repair Unknown BEACON References dialog box
Repair unknown border targets

The border repair utility globally searches all border targets with a band
value set to UNKNOWN and updates the value if a sector is found that
matches the border target information (except with a Band of 800 or 1900).
You can choose if the UNKNOWN value must be updated.
Start the border utility by selecting Tools > PDB Utilities > Repair Unknown
Border References.Figure 67 "Repair Unknown BORDER References
dialog box" (page 110) illustrates the Repair Unknown BORDER References
dialog box.

NN20000-126 04.30 Standard
.
110 PDB utilities
Figure 67
Repair Unknown BORDER References dialog box
Repair unknown EHHO target references

The EHHO target repair utility globally searches for and repairs instances
where a cell with the cell type of EHHO has an entry in the hard handoff
target list that is datafilled as an unknown band. You can choose if the
UNKNOWN value must be updated.
EHHO Target References. Figure 68 "Repair Unknown EHHO References
dialog box" (page 110) illustrates the Repair Unknown EHHO References
dialog box.
Figure 68
Repair Unknown EHHO References dialog box

NN20000-126 04.30 Standard
.
Generate beacon targets 111
Repair unknown EC target references

The EC target repair utility globally searches for and repairs instances
where a cell with the cell type of EC has an entry in the hard handoff target
list that is datafilled as an unknown band. You can choose if the UNKNOWN
value must be updated.
EC Target References. Figure 69 "Repair Unknown EC References dialog
box" (page 111) illustrates the Repair Unknown EC References dialog box.
Figure 69
Repair Unknown EC References dialog box
Generate beacon targets

The Generate Beacon Targets utility auto-generates a minimal beacon target
list for every beacon sector with an empty target list. For beacon sectors
already with a target list, you can potentially add more reference PNs to the
beacon target list. The utility examines the BSC data and tries to determine
potential beacon target list RPILOT entries for these beacon sectors.
For a newly created Pilot Beacon, CACP automatically datafills the target
list with itself even when there is no secondary frequency on that sector.
This datafill has no impact upon CallP (that is, hard handoffs will still be
successful). You can manually remove the entry.
Beacon target lists generate from the following logic:
1. For each beacon sector (that is, sector with CELLTYPE ’beacon’),
a. Find all other non-beacon sectors whose NLIST contain the beacon.
(Such sectors are called reference sectors.)

NN20000-126 04.30 Standard
.
112 PDB utilities
ATTENTION
There must not be any duplicate PNs among the non-beacon sectors. If
more than one sector has the same PN, those sectors are excluded from
further consideration, and a message appears in the Info message tab.
b. For each reference sector identified, determine whether that sector’s

PILOTPN (that is, Reference PILOTPN) already exists among the
beacon sector’s RPILOT values in the BEACON_TARGETS property.
i. If yes, then no action is needed (that is, the existing RPILOT
entry is left unchanged)
ii. If no, then an RPILOT entry for the Reference PILOTPN is added
to the BEACON_TARGETS property of the beacon sector. That
new RPILOT entry consists of two targets: one for the reference
and one for the beacon. You can specify the preferred order
of the targets.
2. Repeat for every beacon sector.
ATTENTION
The Generate Beacon Targets tool is intended to generate beacon targets for
systems that are using ISSHO, where the beacons are existing sites on another
BSC. It is not designed for generating targets in situations where beacon-only
units are used for HHO. If you plan to use the tool where ISSHO and beacon-only
units both are used, be aware that the targets generated for the beacon-only
units are likely to be incorrect and must be reviewed and edited after using the
Generate Beacon Targets tool.
Start the utility by selecting Tools > PDB Utilities > Generate Beacon
Targets. The Generate BEACON Targets dialog box appears. See Figure
70 "Generate BEACON Targets dialog box" (page 112).
Figure 70
Generate BEACON Targets dialog box
If the total number of potential beacon target RPILOTs (for any beacon
sector) exceeds the maximum allowed limit of 20, then each potential
RPILOT instance of beacon target list for a beacon sector are listed in

NN20000-126 04.30 Standard
.
Search-Replace EBID/Pilot PN 113
the Generate Beacon Targets dialog box in grid format (see Figure 71
"Generate BEACON Targets grid dialog box" (page 113)). More than 20
beacon target lists for any beacon sector are not allowed.
Figure 71
Generate BEACON Targets grid dialog box
Note that if the total number of potential beacon targets (for any beacon
sector) does not exceed the maximum allowed limit of 20, then the Generate
Beacon Targets dialog box does not display. In that case, the potential
beacon targets are added without any further user interaction.
Errors or inconsistencies in BSC data that are encountered during the

search display in the Info message tab.
Search-Replace EBID/Pilot PN
The search/replace utility globally searches and replaces the EBID or Pilot
PN.
ATTENTION
EBID for logical sectors only can be changed by this utility. For physical sector
EBID changes, use the BTS configuration wizard. The BTS configuration wizard
automatically propagates any EBID changes to corresponding PDB Neighbor lists
and BTS CDMANeighbor lists in the entire BSC.
If the EBID changes, the entire corresponding neighbor lists and PDB entry
are searched and results provided. The data set is updated with the new
EBID. If the PN changes, the PDB and CDMANeighbor list are searched
and results provided. The changes propagate to the BTS CDMANeighbor
list only.

NN20000-126 04.30 Standard
.
114 PDB utilities
Start the utility by selecting Tools > PDB Utilities > Search-Replace
EBID/PilotPN. Figure 72 "Search-Replace EBID dialog box" (page 114)
shows an example of the Search and Replace GUI.
Figure 72
Search-Replace EBID dialog box
When you fill in the search and replace values and click OK, the
Search-Replace EBID Results dialog box (see Figure 72 "Search-Replace
EBID dialog box" (page 114)) appears with entries matching the search
criteria.
Figure 73
Search-Replace EBID Results dialog box

NN20000-126 04.30 Standard
.
115
Reports
The CDMA Access Configuration and Provisioning (CACP) application
provides a variety of reports that display system configuration information.
Prerequisites
• For procedures to generate reports, see CDMA Access Configuration
and Provisioning (CACP) Operational Administration (NN20000-125).
Reports navigation
• "EBSC Configuration Statistics report / BSC Configuration Statistics
report" (page 115)
• "BSC Configuration Changes report" (page 117)
• "BSC Comparison Delta report" (page 118)
• "BCN Port report" (page 119)
• "BTS Provisioning report" (page 120)
• "Redundant DCG Discrepancies report" (page 121)
• "CFDS License report" (page 122)
EBSC Configuration Statistics report / BSC Configuration Statistics

report
The BSC type determines which configuration statistics report is available;
either the EBSC Configuration Statistics report or the BSC Configuration
Statistics report. If you select a CBRS-based BSC, the EBSC Configuration
Statistics report is available. If you select a legacy BSC, the BSC
Configuration Statistics report is available.
The EBSC Configuration Statistics report and the BSC Configuration
Statistics report display identical information:
• sectors by carrier
• sites by type
• 800 MHz Metro Cells

NN20000-126 04.30 Standard
.
116 Reports
• 1900 MHz Metro Cells

• Compact Metro Cells
• Metro Cell and Compact Metro Cell channel elements
ATTENTION
XCEM/CEM cards appear in the Unknown CEM column if the BTS is not
initialized. Once you initialize the BTS, the cards appear in the appropriate
XCEM or CEM columns.
• Radio Frequency Modules (RFM) by type
ATTENTION
The Mixed column indicates the number of SFRMs and MFRMs present on
the same channel frequency.
• Metro Cell network elements

• Digital Control Groups (DCG)
ATTENTION
The Digital Control Groups (DCG) section shows the number of DCG(s)
depending upon the number of sectors and carriers present for the BTS(s)
on the present BSC.
• Enhanced Digital Control Groups (eDCG)
ATTENTION
The Enhanced Digital Control Groups (eDCG) section shows the number of
eDCG(s) depending upon the number of sectors and carriers present for the
BTS(s) on the present BSC.
• CDMA backhaul and routing subsystem (CBRS) frames

• Distribution and Consolidation (DISCO) shelves
• Selector Bank Subsystem (SBS) shelves
Figure 74 "EBSC Configuration Statistics report" (page 117) illustrates the

EBSC Configuration Statistics report.

NN20000-126 04.30 Standard
.
BSC Configuration Changes report 117
Figure 74
EBSC Configuration Statistics report
BSC Configuration Changes report

BSC Configuration Changes report displays the configuration changes in a
BSC session. The report lists every object that had been created, deleted,
or modified, along with the object type, object path and change type. Key
property values display in bold. Read-only property values display with a
gray background.
Figure 75 "BSC Configuration Changes report" (page 118) illustrates the

BSC Configuration Changes report.

NN20000-126 04.30 Standard
.
118 Reports
Figure 75
BSC Configuration Changes report
BSC Comparison Delta report

BSC Comparison Delta report compares BSC sessions and reports the
configuration differences between them. The report can compare multiple
sessions with different BSC_IDs and multiple sessions of the same
BSC_IDs. Use the CTRL key to select multiple BSCs. The base BSC is the
first BSC node selected in the Navigator panel.
If a BSC is already loaded, you can load the session file under a temporary
BSC name. You cannot use a temporary BSC name that is listed in the
currently imported Market Info file. The temporary BSC name is referred to
as a reference copy.

NN20000-126 04.30 Standard
.
BCN Port report 119
ATTENTION
A reference copy cannot be saved or connected to the Server. Do not edit a
reference copy.
Figure 76 "BSC Comparison Delta report" (page 119) illustrates the BSC
Comparison Delta report.
Figure 76
BSC Comparison Delta report
BCN Port report

The Base Station Communication Network (BCN) port report displays all
the ports and their associated types. It also indicates which subsystem
is currently connected to the port.

NN20000-126 04.30 Standard
.
120 Reports
Only ports on the DISCO show in this report.
Figure 77 "BCN Port report" (page 120) illustrates the BCN Port report.
Figure 77
BCN Port report
BTS Provisioning report

The BTS Provisioning report displays detailed information about the
selected Base Station Transceiver Subsystem (BTS). It contains site,
carrier, sector, Channel Element Module (CEM), module type, and T1/E1
information for that BTS.

NN20000-126 04.30 Standard
.
Redundant DCG Discrepancies report 121
Figure 78 "BTS Provisioning report" (page 121) illustrates the BTS

Provisioning report.
Figure 78
BTS Provisioning report
Redundant DCG Discrepancies report

The Redundant DCG Discrepancies report displays Metro BTSs with
redundant DCGs whose configuration data is not the same. Tables for each
BTS show the attribute values provisioned for DCG, SECTORs, CARRIERs,
and T1E1PORTs for both NUM=1 and NUM=2. Information on DCGs with
NUM=2 and their related configuration data (SECTORs, CARRIERs, and
T1E1PORTs) is available only from this report.
Figure 79 "Redundant DCG Discrepancies report" (page 122) illustrates the

Redundant DCG Discrepancies report.

NN20000-126 04.30 Standard
.
122 Reports
Figure 79
Redundant DCG Discrepancies report
CFDS License report

The CFDS License report displays CFDS licenses required for the selected
subsystems: BSC, all BTSs, selected BTSs, all SBS shelves, or selected
SBS shelves.
Figure 80 "CFDS License report" (page 123) illustrates the CFDS License
report.

NN20000-126 04.30 Standard
.
CFDS License report 123
Figure 80
CFDS License report

NN20000-126 04.30 Standard
.
124 Reports

NN20000-126 04.30 Standard
.
125
User help
The CDMA Access Configuration and Provisioning (CACP) Client provides
a variety of assistance from the Help menu.
Help navigation
• "About" (page 125)
• "About Sessions" (page 125)
• "CACP Online Help" (page 125)
• "Memory Statistics" (page 125)
• "User Guides" (page 126)
About
The About Help option displays information regarding the CACP Client
application, including the release number and copyright information.
About Sessions
The About Sessions Help option displays information regarding an active
session. Information includes the session file name, first and last refresh
times, and the first and last refresh users. You can also access About
Sessions using Alt+A on the keyboard
CACP Online Help

CACP Online Help presents context-sensitive help information for the CACP
main window and most of the wizards and utilities. You can also press the
F1 key after selecting a CACP window, wizard, or utility.
Memory Statistics
The Memory Statistics option displays information regarding the amount of
memory used by the CACP client. It also provides a way for you to run the
Clean-up Memory procedure, which releases unused memory and improves
the performance of the CACP client.

NN20000-126 04.30 Standard
.
126 User help
User Guides
Guides are available in PDF through the Help menu within the application
and through the CACP Help menu on your desktop. You must have Adobe®
Acrobat® Reader™ to read the user guides. You can choose from these
guides:
• CDMA Access Configuration and Provisioning (CACP)
Overview—provides an overview of the CACP application and functions.
You can also use the F2 key within the application to launch this guide.
F2 works in Row View only if you select the entire row by clicking on the
first column of the row prior to selecting F2.
• CACP Installation & Patching —provides step-by-step procedures for
installing and uninstalling Client software. This NTP also included
procedures for enabling CBRS and the Server. You can also use the F3
key within the application to launch this guide.
• CACP Operational Administration—provides step-by-step procedures for
performing administrative tasks associated with the CACP application.
You can also use the F4 key within the application to launch this guide.
ATTENTION
Later releases of the NTPs may be available through Helmsman Express.
ATTENTION
Documentation is available for only the latest installed release. Though you can
open the CACP Client for a prior release (for example, 13.0), only documentation
for the latest release is available (for example, 14.0).

NN20000-126 04.30 Standard
.
127
Recommended values
CDMA Access Configuration and Provisioning (CACP) gives the ability to
check an active BSC data set (session) against user-defined or Nortel
Recommended Values.
The recommended values installed with CACP are Nortel-defined
recommended values. They are typically defined for the sector data, and
apply to Radio Frequency (RF) related parameters.
• Default values represent values for BSMCI table fields that are
recommended by Nortel.
• You may override Nortel-recommended values with your own default
values.
• If present, default values always appear as the first entry in each table;
multiple default entries may be present per BSMCI table.
You can set custom recommended values for use in data validation. CACP
provides the ability to clone and edit the Nortel-recommended values.
Edit the default values by using the normal BSMCI table commands (pos,
top, cha) on the default rows. You can save these recommendations to
a separate file that is portable and can be shared for the Code Division
Multiple Access (CDMA) system.
Both Nortel-defined recommended values and custom defined
recommended values differ by category. For example, the BTS categories
include CompactBTS and MetroBTS.
ATTENTION
Business Rules Checking does not allow use of a Customer Recommended Value
(CRV) file that is not of the same version as the BSC version.
Select Edit from the menu bar and then Recommended Values to display
the Edit Customer Recommended Values dialog box (see Figure 81 "Edit
Customer Recommended Values dialog box" (page 128)).

NN20000-126 04.30 Standard
.
128 Recommended values
Importing an invalid version or newer version CRV file will result in an error
message. Older version CRV files can be imported, and will be migrated to
the current version. During the migration:
• Any network objects and/or properties that do not exist in the new
version are ignored but reported in a pop-up message.
• Properties that would cause invalid values in the new version are
ignored but reported in a pop-up message.
Ignored objects or properties are not included in the saved CRV file.
The recommended procedure for migrating CRV files is by using the Open
and Save or Save As options on the Edit Customer Recommended Values
dialog box. See CDMA Access Configuration and Provisioning (CACP)
Operational Administration (NN20000-125) for information on editing and
saving CRV files.
ATTENTION
When opening a CRV file in a text editor, use a text editor that supports line breaks.
Figure 81
Edit Customer Recommended Values dialog box

NN20000-126 04.30 Standard
.
Recommended values 129
To add a new property to a network object, click the Add button. The Select
New Recommended Values Columns dialog box appears (see Figure 82
"Select New Recommended Values Columns dialog box" (page 129)). You
can choose properties to add to the current network object. The Available
Columns pane lists all the properties in the datafill that relate to the current
network object. Use the selection buttons in the middle of the dialog box to
move properties to the Selected Columns pane.
Figure 82
Select New Recommended Values Columns dialog box

Administration (NN20000-125) for the procedure on editing recommended
values. You can create and maintain multiple Recommended Values files for
use in data validation.

NN20000-126 04.30 Standard
.
130 Recommended values

NN20000-126 04.30 Standard
.
131
Restrictions, dependencies, and

limitations
This section lists the restrictions, dependencies, and limitations of the
CDMA Access Configuration and Provisioning (CACP) application.
Restrictions, dependencies, and limitations navigation

• "Communication" (page 131)
• "Version" (page 132)
• "Multiple BSC" (page 132)
• "Commit" (page 132)
• "Configuration" (page 133)
• "CBRS" (page 135)
• "SCH Throughput Enhancements" (page 137)
Communication
• For firewall access, one port (port number 7301) on the Base Station
Subsystem Manager (BSS Manager) must be accessible to the
CDMA Access Configuration and Provisioning (CACP) Client PC for
bi-directional TCP traffic.
• Communication speed between the Client and the BSS Manager Server
depends on the connection bandwidth and network traffic at any time.
Depending on whether the CACP Client-Server communication is over
Ethernet or modem, the application’s performance is impacted if working
online.
• CACP Client and Server applications typically communicate over the
customer’s private Local Area Network (LAN). However, to provide
access to Nortel support groups, TCP port 7301 must be made available
by the customer on the private LAN.
• If communication to the CACP Server is lost during commit, the CACP
Server will continue to execute the scripts. Check the script results by

NN20000-126 04.30 Standard
.
132 Restrictions, dependencies, and limitations
viewing the logs on the BSS Manager in the "/opt/bsm/log/cacpserver"

directory.
Version
• CACP Client application can run only on a PC platform running
Windows2000 SP2, SP3 or SP4, Windows NT SP6, or Windows XP
Professional SP 1.
• CACP supports only Base Station Controllers (BSC) at NBSS 13.0 or
greater. Pre-13.0 versions cannot use CACP.
• Multiple BSC configuration operations are provided only for BSCs at
NBSS 13.0 or greater.
• The 14.0 CACP Client supports 13.0 as the only backward-compatible
BSS Manager version. For instance, if you connect to a 14.0 BSS
Manager, the 14.0 Client launches. If you connect to a 13.0 BSS
Manager, the 13.0 Client launches.
• Do not use CACP during upgrades as the tool is not forward-compatible.
Use CACP after completing the End-to-End upgrade, and when all
subsystems and EMSs are on the same release.
Multiple BSC
• Only the following multiple BSC configuration operations are supported
by CACP:
— Pilot Database (PDB) reconciliation and reciprocation for physical
and logical sectors
— BTS rehome
• Do not work across more than one BSC version.

• If using multi-version functionality to connect to different version BSC, do
not close any version of the client when using multiple BSC functionality.
• For CACP 1500 cell carriers operations, a maximum of two session files
is supported (1500 cell carriers each). It is not recommended to launch
C-EMS or 12.0 MVS during CACP 1500 cell carriers operations.
Commit
• At any particular time, only one user can commit local configuration
changes from the CACP Client. This ensures data consistency and
proper validation.
• If there is an active prov session on the Multiservice Switch at anytime
during a commit action, the commit can fail.

NN20000-126 04.30 Standard
.
Configuration 133
• Using legacy BSS Manager interfaces such as Base Station Manager

Command Interface (BSMCI) and/or Command Line Interface (CLI) at
the same time as commit operations from the CACP can cause data
inconsistencies.
• CACP generates the "DistributeToAll" action on all PDB changes and
system configuration changes. You are presented with an option
whether or not to execute this command at the time of the commit action.
• Perform data commit one at a time for each open CACP Client
application version.
• Perform a commit action after a Business Rules check.
Configuration
• The System Authentication fields AUTHE, MAXRANDC, MINRANDC,
RANDU, and RANDE fields exist at the system-level (in BSMCI table
SYSAUTH) and also exist at the single BTS level (in BSMCI table
METROINV). The system-level values are generally the master values
such that the BTS-level values are expected to be in sync with them.
When committing a new BTS created using the Add or Clone BTS
wizard, BSMCI automatically overwrites the AUTHE, MAXRANDC,
MINRANDC, RANDU, and RANDE field values for that BTS with
corresponding values from table SYSAUTH. If you commit any custom
values (different than the SYSAUTH values), then a second commit
is required.
• Use CACP for all CheckNeighbor, Commgr, NCF Editor, and CDF
configuration needs.
• Inconsistencies found during the initial data import activity from the BSS
Manager are not resolved automatically by this application. They are
reported only and you are responsible for fixing them. (You can use
tools provided as part of CACP to resolve most errors.)
• CACP provides only configuration management functionality. It does not
support maintenance actions, alarm management, or state notifications
for network elements.
• The configurable data set (at the BSS Manager) is limited to that which
is available through the BSMCI.
• CACP does not restrict you from simultaneously using existing BSS
Manager interfaces such as BSMCI, CLI, and TurboIF, and so on,
for configuration management. Note that the CDMA backhaul and
routing subsystem (CBRS) frame restricts to no more than one open
provisioning session at any given time.
• As with the BSMCI application, if non-settable configuration attributes
are being changed (for example, frequency changes), the associated
network element must be brought to the appropriate state before the

NN20000-126 04.30 Standard
.
changes can be successfully committed. This also applies to CBRS

systems. On CBRS system, check BcnPort state during subsystem
management.
• PDB data on individual Selector Bank Subsystem (SBS) shelves cannot
be edited using CACP.
• You must datafill a unique BSC Instance Display Name value in the
SystemConfiguration Managed Object (MO) of the BSS Manager.
This MO is used by the CACP Client to identify and communicate with
different BSS Managers.
• CACP does not validate CFDS licenses as part of the provisioning.
Existing BSS Manager validation is responsible for performing these
checks. However, CACP provides a report of required CFDS licenses.
Also, the BSS Manager provides a report of available CFDS licenses.
You can refer to these reports while performing configuration activities.
• Configuration changes made to the BSS Manager through other
interfaces may not be indicated to the CACP user for up to five minutes.
This is because the auto-query monitor mechanism runs periodically
every five minutes.
• BSMCI default values cannot be edited through CACP. Note that
according to existing BSS Manager restriction, Nortel-defined
BSMCI default values cannot be edited. However, you can edit the
customer-defined BSMCI default values file directly at the BSS Manager.
Invoke the data refresh operation in order for modified/new BSMCI
default values to take effect as they are not populated into CACP
automatically.
• There is not a CLI for the CACP Client and Server.
• 4pOC12 and 4pSTM4 cards are not supported and must not be used.
• The CPDS cards (DSFP/PCUFP) are view-only in the Port Map View of
CACP Client. No datafill provisioning capability is provided.
• To delete an existing carrier sector from a BTS object, use the
Configuration Wizard instead of deleting the BTS object and then
re-adding the same with the same key values.
— For Metro Cell BTS, use Configure RFM wizard to do the same.
— For Compact Metro Cell BTS, use Configure RM wizard to do the
same.
• CACP does not maintain any relationship between carrier frequencies

and AdvancedFA MO names for Metro Cell and Compact Metro Cell
BTSs. When a new BTS is created, CACP creates and names the
carriers in random order. For example, the first carrier that is created is
assigned the MO name AdvancedFA1, the second is AdvancedFA2, and

NN20000-126 04.30 Standard
.
CBRS 135
so on, which may not match the ordering you want. The same ordering
of MO names can occur when you add new carriers to an existing BTS,
move carriers from one DCG to another, or make any field changes
that cause the BTS or individual carriers to be deleted and re-added.
You can use the auditfreqorder tool to produce a report on existing MO
names and to modify their values. See "auditfreqorder tool" (page 139)
for more information.
• CACP does not permit you to remove RMs from an online BTS.
• The following configuration capabilities are not supported by CACP:
— Inter-System Soft Handoff (ISSHO) provisioning
— CDMA Interface Unit (CIU) provisioning
— Asynchronous Transfer Mode (ATM) Phase 1 and Phase 2
configuration
— new BSC additions (this constitutes green field deployment
scenarios which are typically performed by Nortel I&C teams)
— Channel Data Service Unit (CDSU) provisioning
— fixed wireless feature (V5.2) configuration
CBRS
The following list is the requirements for provisioning CBRS frame and the
associated Functional Processors (FP).
• The following card types can be provisioned using CACP:
— T1: 11pMSW, 24pBCNW, 4pOC3, 16pOC3
— E1: 11pMSW, 24pBCNW, 4pSTM1, 16pSTM1
• The following kinds of T1 ports/services can be provisioned using CACP:

— 11pMSW: BSS Manager, DISCO, BTS, IMH
— 24pBCNW: SBS
— 4pOC3: BSS Manager, DISCO
— 16pOC3: BSS Manager
• The following kinds of E1 ports/services can be provisioned using CACP:

— 11pMSW: BSS Manager, BTS, IMH
— 24pBCNW: SBS
— 4pSTM1: BSS Manager, DISCO
— 16pSTM1: BSS Manager

NN20000-126 04.30 Standard
.
• Provision 11pMSW and 24pBCNW functional processors in pairs. When

dragging and dropping these cards in the slots, place them in the even
slot—CACP automatically provisions the mated card in the odd slot. To
maintain consistency, it is recommended that all functional processors
(except DS3 and E3) be provisioned in the even slot.
• CBRS frame configuration scripts generated by CACP contain and
perform only the following native Component Administration System
(CAS) commands: start prov, copy prov, check prov, activate prov,
confirm prov, and end prov. These native commands are used for CBRS
frame provisioning.
• CACP Client periodically monitors BSS Manager data changes (by an
auto-query mechanism) but not CBRS frame changes. This automatic
monitoring is intended only to indicate a need for refreshing local data.
You must separately invoke the data refresh operation for BSS Manager
and/or CBRS frame data changes. Note that during commit local
data operation, BSS Manager data and CBRS frame data are always
refreshed.
• The ebscDataAudit utility at BSS Manager ("/opt/bsm/bin/") checks for
inconsistency between BSS Manager datafill and CBRS frame datafill.
You must run ebscDataAudit frequently (for example, daily) to ensure
that the BSS Manager datafill and CBRS frame datafill do not go out
of sync. If there is an inconsistency, CACP BSMCI and CBRS frame
commit scripts may fail.
ATTENTION
In the eBSCDataAudit script output log, the ProjectedNumOfDS0sPerLink
attribute under Inverse Multiplexing HLDC (IMH) will show mismatches
between the BSS Manager and the Multiservice Switch 15000. This behavior
is expected.
• CACP expects basic CBRS frame provisioning to be in place before you

can add cards or services to that frame. Some initial datafill is also
required in BSMCI’s PassportInv table.
• CBRS frames are visible only in the Port Map View.
• CACP differentiates between a T1-based CBRS frame and an E1-based
CBRS frame.
• A T1 frame and E1 frame cannot be mixed and matched. CACP supports
CBRS provisioned on either a complete T1 BSC or a complete E1 BSC.
• 24pBCNW cards can be assigned to slots 6, 7, 14, 15 only and must be
assigned to slots 6, 7 first. 24pBCNW cards must be deleted from slots
14, 15 first if there are 24pBCNW cards configured on the slots.
• The legends for the DISCO ports only show on the even card. The Add
Port menu items on the slot on the redundant card are disabled. Note

NN20000-126 04.30 Standard
.
SCH Throughput Enhancements 137
that even if the DISCO port is created on the redundant card, the legend
still shows on the main card only.
• When a BSS Manager port is created, no other services can be added
on the peer port on the peer card.
• DISCO ports are always provisioned as MIMIC Automatic Protection
Switching (APS).
• All T1/E1s belonging to the same DCG must be assigned ports on the
same 11p card.
• CACP supports up to three CBRS and four CPDS frames.
SCH Throughput Enhancements

• This feature is not supported in the SEL (legacy product). It is supported
on the ESEL and CPDS platforms.
• This feature is not supported in fixed wireless platform.
• If the burst type is chosen as finite on the BSS Manager/C-EMS for any
SBS shelf/DSFP card, the Rate Upgrade Time is not applicable.
• If the QOSPI value of all the users are the same, the ESEL/ACP SCH
resource allocation is performed in a FCFS basis.
• If pre-12.1 release infinite burst functionality is desired, the
MinActiveEnable and RateUpgradeEnable must both be disabled. The
BTS and BSC will not preempt or upgrade a burst when these are
disabled.
• Priority Fair Share algorithm is consider the Fwd and Rev SCH requests
equally. This means high priority RSCH requests can get more BSC
resources than low priority FSCH requests, and vice-versa. The
resource allocation scheme is based on priority only, not on the type
of burst.
• BTS Burst Scheduler has a maximum queue size of 8 elements for each
frequency-sector.
• If the values of INFINITE_BURST_SUPPORT_FWD, IN-
FINITE_BURST_SUPPORT_REV, FairShareAlgorithm and
MinActiveEnable, which are part of the SCHParameters attribute on the
SelectorSubsystem MO/DSFP card, change when BSC is processing
data calls, the new values chosen will affect existing data calls. The new
values chosen may not take affect immediately.
— Disabling MinActiveEnable preempts active bursts (if the timer was
running) at the timer expiry.
— Modifying burst type between finite and infinite affects current active
bursts, such as going from finite to infinite can start preempting

NN20000-126 04.30 Standard
.
active bursts (if preemption is also enabled). Going from infinite to

finite maintains all active infinite bursts, but new bursts will be finite.
• If either of INFINITE_BURST_SUPPORT_FWD or INFI-

NITE_BURST_SUPPORT_REV is set to TRUE (configured for infinite),
then MinActiveTime preemption (if MinActiveEnable is set to TRUE)
applies to both forward and reverse bursts. This means that finite
bursts can be preempted with this configuration. This is also true when
changing the configuration from finite bursts to infinite bursts with
preemption.
• Disabling the BTS scheduler by setting RRMBurstSchedulerAlgorithm
on the BTS CallProcessing MO to RBSA_OFF or RBSA_PREEMPTION
causes any currently queued requests at the BTS to reject back to the
BSC by the BTS, where the BSC random backoff timer applies to these
bursts for resource allocation.
• If the BTS is in a contention situation for channel elements and a new
F-SCH burst request is queued at the BTS awaiting channel elements, it
only looks at preempting active F-SCH bursts on the sector that the new
burst is queued against to free up channel elements. The BTS does not
preempt F-SCH bursts on other sectors to free up channel elements.
This is in-line with F-SCH bursts queued up waiting for Walsh code and
RF power resources, which are sector based.

NN20000-126 04.30 Standard
.
139
auditfreqorder tool
This section describes the auditfreqorder tool, which you can use to modify
MO names.
auditfreqorder tool navigation

• "Overview" (page 139)
• "Configuration" (page 139)
• "Usage" (page 140)
Overview
AdvancedFA MO names for Metro Cell and Compact Metro Cell BTSs.
When a new BTS is created, CACP creates and names the carriers in
random order. For example, the first carrier that is created is assigned the
MO name AdvancedFA1, the second is AdvancedFA2, and so on, which
may not match the ordering you want. The same ordering of MO names
can occur when you add new carriers to an existing BTS, move carriers
from one DCG to another, or make any field changes that cause the BTS
or individual carriers to be deleted and re-added.
You can use the auditfreqorder tool to modify the assigned MO names. This
tool runs on the BSS Manager and audits all (or a subset) of the AdvancedFA
MOs in the system. It checks to see if the MO names are consistent with the
ordering that you specify in a configuration file and optionally modifies the
MO names to be consistent with the values in the configuration file.
Configuration
Before running the auditfreqorder tool for the first time, you must create the
configuration file /opt/bsm/cfg/freqorder.cfg. This file specifies the preferred
ordering of the frequencies present in the BSC.
The freqorder.cfg file is an ordinary text file and you can create it
using vi or any other text editor. The template configuration file,
/opt/bsm/cfg/freqorder.cfg.template, is available for reference.

NN20000-126 04.30 Standard
.
140 auditfreqorder tool
There should be exactly one line present in the file for each band present in
the file. The format of each line has the following format:
<band>: <freq1> <freq2> <freq3>...
800: 283 242 201 160 119

1900: 100 125 150 175 200 225
Usage
This section shows auditfreqorder tool usage. Start the auditfreqorder tool
from the BSS Manager by typing the following command:
auditfreqorder -h
$ auditfreqorder –h
Checks the display names of AdvancedFA MOs to determine if
they match the frequency order specified in the config file
/opt/bsm/cfg/freqorder.cfg.
Can optionally fix discrepancies.
Usage: auditfreqorder [ -noconfirm | -report ]
[bts-name> ... ]
-noconfirm Automatically update MO names without
confirmation.
-report Generate report only. Do not update MO names.
If neither of the above options are specified, the tool
operates in interactive mode, where the user is asked to
confirm the changes for each BTS.
Examples
auditfreqorder –report
auditfreqorder -noconfirm MC1900BTS1001
auditfreqorder MC1900BTS1001 MC1900BTS2001 MC1900BTS1002

NN20000-126 04.30 Standard
.
141
CDMA paging zone editing during

upgrade
This section describes the procedure for editing paging zone data during
the upgrade timeframe when one sister BSC is on the Nth release (such
as release 13.0) and the other sister BSC is on the N+1th release (such
as release 14.0).
CAUTION
This procedure is required only if you need to edit the paging zone
data in the middle of the upgrade operation. Once you complete
the upgrade, do not use this procedure. Instead, load the sessions
of both sister BSCs on the same CACP client and edit the paging
zone data. CACP synchronizes data between the sister BSCs
after you load both sessions.

NN20000-126 04.30 Standard
.
142 CDMA paging zone editing during upgrade
Figure 83
CDMA paging zone editing during upgrade task flow
CDMA paging zone editing during upgrade procedure navigation

• "Enabling the script viewer/generator" (page 142)
• "Editing CDMA paging zone data during upgrade" (page 143)
Enabling the script viewer/generator

Use this procedure to enable the script viewer/generation functionality on
the CACP client.
ATTENTION
You only need to perform this procedure once on any CACP client.
Prerequisites
• Ensure that the correct version of the CACP client is running on your PC.

NN20000-126 04.30 Standard
.
Editing CDMA paging zone data during upgrade 143
Procedure steps
Procedure 1
Enabling the script viewer/generator
Step Action
1 Display the Preferences dialog box.

Edit > Preferences
2 Click the General Settings tab.

3 From the Business Rules Relaxation and Script Viewer/Generator
list, select enable.
4 Click OK.
—End—
Editing CDMA paging zone data during upgrade

In order to edit the paging zone data, remove the sister BSC relationship.
After editing the paging zone data, restore the sister BSC relationship to
prevent any business rule errors resulting from cross-BSC validations.
Prerequisites
• Familiarize yourself with BSS Manager operation.
• Ensure that the correct version of the CACP client is running on your PC.
• Establish a connection to the BSS Manager of the appropriate BSC.
• Ensure CACP script viewer/generation functionality is enabled. See
"Enabling the script viewer/generator" (page 142).
Procedure steps
Procedure 2
Editing CDMA paging zone data during upgrade
Step Action
1 Open the marketinfo_ext.txt file.
2 Comment-out the line defining the sister BSC relationship.

Once commented-out, the line appears as:
// MTXZ BSCX BSCY
3 Save marketinfo_ext.txt.

NN20000-126 04.30 Standard
.
144 CDMA paging zone editing during upgrade
4 Import the updated market info file:

File > Import Market Info File
5 Edit the CDMA paging zone information as required.

6 Open the marketinfo_ext.txt file.
7 Uncomment the line you modified in step 2 to restore the sister BSC
relationship.
The uncommented line appears as:
MTXZ BSCX BSCY
8 Save marketinfo_ext.txt.
9 Re-import the updated market info file:
File > Import Market Info File
10 Commit changes to the online BSSM:

File > Commit / Generate Script
11 Accept the following warning:

Paging zone validation failed. Paging zones have been modified,
and sister BSC is not loaded.
12 Repeat steps step 1 to step 11 for the sister BSC.
ATTENTION
After both BSCs are upgraded to the same release, ensure that the
following line is uncommented as it defines the sister BSC relationship
between both BSCs:
MTXZ BSCX BSCY
ATTENTION
On each of the CACP clients with BSC data loaded, modify CDMA paging
zone data separately. For example, modify paging zone data in CACP
13.0 for the 13.0 BSC, and modify paging data in CACP 14.0 for the 14.0
BSC.
—End—

NN20000-126 04.30 Standard
.

Copyright © 2003-2006, Nortel Networks
All Rights Reserved.
Publication: NN20000-126
Document status: Standard
Document version: 04.30
Document date: 1 December 2006
To order documentation from Nortel Global Wireless Knowledge Services, call

(1) (877) 662-5669
To provide feedback or report a problem in this document, go to www.nortel.com/documentfeedback.
Sourced in Canada and the United States of America.
The information contained herein is the property of Nortel Networks and is strictly confidential. Except as expressly authorized in
writing by Nortel Networks, the holder shall keep all information contained herein confidential, shall disclose it only to its employees
with a need to know, and shall protect it, in whole or in part, from disclosure and dissemination to third parties with the same degree
of care it uses to protect its own confidential information, but with no less than reasonable care. Except as expressly authorized in
writing by Nortel Networks, the holder is granted no rights to use the information contained herein.
Information is subject to change without notice. Nortel Networks reserves the right to make changes in design or components
as progress in engineering and manufacturing may warrant.
* Nortel, the Nortel logo and the globemark are trademarks of Nortel Networks. Adobe and Acrobat Reader are trademarks
for Adobe Systems.
Trademarks are acknowledged with an asterisk (*) at their first appearance in the document.
All other trademarks are the property of their respective owners.

CDMA Access Configuration and Provisioning (CACP) Overview

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

CDMA Access Configuration and Provisioning (CACP) Overview

Uploaded by

Copyright:

Available Formats

Code Division Multiple Access (CDMA)