Cisco RAN Management System Administration Guide, Release 4 · ConnectionRequest:Messages 75...
Transcript of Cisco RAN Management System Administration Guide, Release 4 · ConnectionRequest:Messages 75...
-
Cisco RAN Management System Administration Guide, Release 4.xFirst Published: June 15, 2014
Americas HeadquartersCisco Systems, Inc.170 West Tasman DriveSan Jose, CA 95134-1706USAhttp://www.cisco.comTel: 408 526-4000 800 553-NETS (6387)Fax: 408 527-0883
Text Part Number: OL-32398-01
-
THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS,INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND,EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.
THE SOFTWARE LICENSE AND LIMITEDWARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITHTHE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY,CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.
The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB's public domain versionof the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California.
NOTWITHSTANDINGANYOTHERWARRANTYHEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS"WITH ALL FAULTS.CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OFMERCHANTABILITY, FITNESS FORA PARTICULAR PURPOSEANDNONINFRINGEMENTORARISING FROMACOURSEOFDEALING, USAGE, OR TRADE PRACTICE.
IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUTLIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERSHAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, networktopology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentionaland coincidental.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: http://www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnershiprelationship between Cisco and any other company. (1110R)
© 2014 Cisco Systems, Inc. All rights reserved.
http://www.cisco.com/go/trademarkshttp://www.cisco.com/go/trademarks
-
C O N T E N T S
C H A P T E R 1 Preface 1
Preface 1
Document Revision History 1
Objectives 1
Audience 2
Conventions 2
Related Documentation 2
Obtaining Documentation and Submitting a Service Request 3
C H A P T E R 2 Cisco RAN Management System Overview 5
Cisco RMS Solution Overview 5
Cisco RMS Solution Components 6
Provisioning Management Gateway 6
Broadband Access Center 7
Device Provisioning Engine 8
Regional Data Unit 8
Device Command and Control 8
DCC UI 8
Ops Tools 9
Prime Access Registrar 9
Prime Network Registrar 9
Upload Server 9
Femtocell Access Point Process Flow 10
Cisco RMS High-Level Provisioning Flow 10
Cisco RMS Interfaces 11
Service Provider OSS 12
Provisioning Management Gateway 12
Provisioning and Management Gateway DB 13
Cisco RAN Management System Administration Guide, Release 4.x OL-32398-01 iii
-
Broadband Access Center 13
Access Point 13
Cisco Radio Access Network 14
Cisco RMS Software Architecture 14
Central RMS Node 14
Serving RMS Node 15
Upload RMS Node 16
Cisco RMS Physical and Virtual Architecture 17
All-in-One RMS Node 17
Distributed RMS Node 18
C H A P T E R 3 Device Command and Control 19
DCC Overview 19
DCC UI Requirements 19
Device Manager User Roles and Permissions 20
Information About the DCC UI 21
Logging In to the DCC-UI 22
Configuring DCC Dialog Boxes 23
Dynamic Screen Configuration Files 26
Adding or Updating Fields in the Group Dialog Box 27
Configuring the DCC Dashboard 28
C H A P T E R 4 Baseline Configuration 33
Configuring BAC 33
Device Activation Custom Properties 33
Location Aware Custom Properties 36
Firmware Upgrade Custom Properties 37
RF Profiles Custom Properties 37
ubi-config-X.Y.Z Custom Properties 39
C H A P T E R 5 Device Manager 45
Device Provisioning 45
Preparing to Register a Device 45
Registering a Device in Enterprise Mode 47
Registering a Device in Residential Mode 48
Cisco RAN Management System Administration Guide, Release 4.xiv OL-32398-01
Contents
-
Re-registering the Device with a New Group 49
AP Site Reassignment 49
Area Site Reassignment 49
Updating a Device 50
Enabling Location Verification 50
Expected Detected Neighbor (EDN) 51
Detected Neighbor Location (DNL) 52
Detected Neighbor MCC/MNC (DNM) 55
IP Address Subnet Match (ISM) 56
Detected Neighbor Benchmark (DNB) 57
View Information about a Device 59
Displaying the Device Dashboard 60
Log Uploads and Triggers 61
Uploading a Log 62
Setting Triggers to Upload the Logs 62
Device Operations 63
Configuring Static Neighbors 63
Adding or Updating Static Neighbors 63
Updating Static Neighbor Filtering 63
Deleting Static Neighbors 64
Replacing a Device 65
Requesting a Connection to a Device 66
Rebooting a Device 66
Resetting a Device 67
Shutting Down a Device 67
View and Update Live Data 67
Displaying Live Data 67
Updating Live Data for a Device 68
Updating Modified Live Data 70
Device Manager Status Messages 70
Registering a Device: Status Messages 70
Activating a Device: Messages 71
Displaying the Device Dashboard: Messages 72
Uploading a Log: Messages 73
Updating Log Upload Triggers: Messages 74
Cisco RAN Management System Administration Guide, Release 4.x OL-32398-01 v
Contents
-
Connection Request: Messages 75
Rebooting a Device: Messages 75
Resetting a Device: Messages 75
Shutting Down a Device: Messages 76
Display Live Data: Messages 76
Updating Live Data: Messages 76
Updating Modified Live Data: Messages 77
C H A P T E R 6 Upgrade Monitoring Tool 79
Upgrading a Firmware 80
Monitoring a Firmware Upgrade 81
Upgrade Monitor History 86
Displaying Upgrade Monitor Errors 86
Upgrade Monitor Success 86
Reconciling a Monitor Upgrade Job 87
Adding a Firmware Type to the UMT 87
Adding a Firmware Version to the UMT 88
C H A P T E R 7 Managing Groups and ID Pools 91
Overview of Managing Groups and ID Pools 91
Recommended Order for Working with Pools and Groups 92
Managing Group Types 93
Site Groups 94
Area Groups 95
RF Profile Groups 105
FemtoGateway 112
Enterprise Groups 114
Managing Groups 115
Managing ID Pool Types 116
SAI Pools 117
CELL Pools 119
Managing ID Pools 120
Making Changes to a Group Type, Group Instance, ID Pool Type or IP Pool Instance 122
Adding a Group Type 122
Adding a Group Instance 122
Cisco RAN Management System Administration Guide, Release 4.xvi OL-32398-01
Contents
-
Adding a Device to New Group 123
Adding ID Pool Types 123
Adding an ID Pool Instance 124
Updating a Group Type, Group Instance, ID Pool Type or ID Pool Instance 124
Deleting a Group Type, Group Instance, ID Pool Type or ID Pool Instance 125
Importing a Group Type, Group Instance, ID Pool Type or ID Pool Instance 125
Importing the Exported Pools and Groups from the Previous Build to the New Build 126
Exporting ID Pool or Group Types 128
Exporting Information about a Group or ID Pool Instance 128
Groups and IP Pools: Messages 129
Adding a Group Type: Messages 129
Updating a Group Type: Messages 130
Import Group Type, Group Instance, ID Pool Type and ID Pool Instance: Messages 130
Export Group Type: Messages 130
Adding or Updating a Group Instance: Messages 131
Deleting a Group Instance: Messages 131
Exporting Information about a Group Instance: Messages 132
Adding an ID Pool: Messages 132
Deleting an ID Pool Type: Messages 132
Exporting ID Pool Type: Messages 133
Export an ID Pool: Messages 133
Updating an ID Pool Instance: Messages 134
Updating an ID Pool Type: Messages 134
C H A P T E R 8 Global Configuration of Devices in BAC RDU 137
Configuring DN Prefix Format 137
Adding CWMP Defaults 139
Updating CWMP Defaults 140
Deleting CWMP Defaults 140
C H A P T E R 9 Administering Users and Roles 143
PAM Authentication 144
User Roles and Access Permissions 144
Managing Roles 145
Adding a Role 145
Cisco RAN Management System Administration Guide, Release 4.x OL-32398-01 vii
Contents
-
Editing a Role 145
Deleting a Role 146
Managing Users 146
Adding a User 146
Editing a User 147
Deleting a User 147
User Administration: Messages 148
C H A P T E R 1 0 Operational Tools 149
massCr.sh 150
massReboot.sh 153
getDeviceData.sh 156
encryptPassword.sh 160
searchAndExport.sh 160
reassignDevices 162
resync.sh 164
massFactoryRestore.sh 165
Operational Tools for PMGDB 168
comparePolygons.sh 168
updatePolygons.sh 170
getAreaChangeDtls.sh 171
getAreas.sh 172
loadRevision.bat 173
updatePolygonsInPmg.sh 174
C H A P T E R 1 1 Performance Counters 177
C H A P T E R 1 2 Cisco Provisioning Management Gateway (PMG) 181
PMG Overview 181
PMG Message Flow 183
LUS Organized Directory Structure for AP PM Files 183
PMG Event Subscription 183
Managing the PMG 185
PMG Logging 185
PMG Performance Logs 186
Cisco RAN Management System Administration Guide, Release 4.xviii OL-32398-01
Contents
-
Individual Performance Log File 186
Hourly Performance Log File 188
PMG Alarm Logs 189
PMG Syslogs 190
PMG Message Logs 190
Alarm Messages 190
PMG Profiles 191
Parameter Definitions 192
C H A P T E R 1 3 Troubleshooting 195
Troubleshooting the Device Command and Control UI 195
Operational Tools Troubleshooting 196
A P P E N D I X A Appendix 199
Creating Neighbor ID for EDN and DNL 199
Creating Frequency Signature for DNB 200
Adding Files for DNL and ISM from BAC 201
Adding Various LV Related Properties from BAC UI 201
Glossary 203
API 203
BAC 203
BSS 203
CMHS 203
Cisco RAN Management System Administration Guide, Release 4.x OL-32398-01 ix
Contents
-
Cisco RAN Management System Administration Guide, Release 4.xx OL-32398-01
Contents
-
C H A P T E R 1Preface
• Preface, page 1
• Document Revision History, page 1
• Objectives, page 1
• Audience, page 2
• Conventions , page 2
• Related Documentation, page 2
• Obtaining Documentation and Submitting a Service Request, page 3
PrefaceThis section describes the objectives, audience, organization, conventions, and related documentation of theCisco RAN Management System (RMS) Administration Guide, Release 4.x.
Document Revision HistoryThe Document Revision History table below records technical changes to this guide. The table shows thedocument revision number for the change, the date of the change, and a brief summary of the change.
Change SummaryDateDocument Number
Initial version of the document.June 23, 2014OL-32398-01
ObjectivesThis guide provides a brief overview of the Cisco RAN Management System (RMS) system and covers allthe administration information and tasks needed to manage and operate Cisco RMS.
Cisco RAN Management System Administration Guide, Release 4.x OL-32398-01 1
-
AudienceThe primary audience for this guide includes network operations personnel and system administrators. Thisguide assumes that you are familiar with the following products and topics:
• Basic internetworking terminology and concepts
• Network topology and protocols
• Microsoft Windows 2000, Windows XP, Windows Vista, and Windows 7
• Linux administration
• RedHat Enterprise Linux 6.1
• VMWare vSphere 5.1.0
ConventionsThis document uses the following conventions:
DescriptionConvention
Commands and keywords and user-entered text appear in bold font.bold font
Document titles, new or emphasized terms, and arguments for which yousupply values are in italic font.
Italic font
Terminal sessions and information the system displays appear in courierfont.
Courier font
Bold Courier font indicates text that the user must enter.Bold Courier font
Elements in square brackets are optional.[x]
A nonquoted set of characters. Do not use quotation marks around thestring or the string will include the quotation marks.
string
Nonprinting characters such as passwords are in angle brackets.< >
Default responses to system prompts are in square brackets.[ ]
An exclamation point (!) or a pound sign (#) at the beginning of a lineof code indicates a comment line.
!, #
Related DocumentationFor additional information about the Cisco RAN Management Systems, refer to the following documents:
Cisco RAN Management System Administration Guide, Release 4.x2 OL-32398-01
PrefaceAudience
-
• Cisco RAN Management System Installation Guide, Release 4.x
• Cisco RAN Management System API Guide, Release 4.x
• Cisco RAN Management System SNMP/MIB Guide, Release 4.x
• Cisco RAN Management System Release Notes, Release 4.0
Obtaining Documentation and Submitting a Service RequestFor information on obtaining documentation, using the Cisco Bug Search Tool (BST), submitting a servicerequest, and gathering additional information, seeWhat's New in Cisco Product Documentation, at: http://www.cisco.com/c/en/us/td/docs/general/whatsnew/whatsnew.html.
Subscribe toWhat's New in Cisco Product Documentation, which lists all new and revised Cisco technicaldocumentation, as an RSS feed and deliver content directly to your desktop using a reader application. TheRSS feeds are a free service.
Cisco RAN Management System Administration Guide, Release 4.x OL-32398-01 3
PrefaceObtaining Documentation and Submitting a Service Request
http://www.cisco.com/c/en/us/td/docs/general/whatsnew/whatsnew.htmlhttp://www.cisco.com/c/en/us/td/docs/general/whatsnew/whatsnew.html
-
Cisco RAN Management System Administration Guide, Release 4.x4 OL-32398-01
PrefaceObtaining Documentation and Submitting a Service Request
-
C H A P T E R 2Cisco RAN Management System Overview
This chapter provides a functional overview of the Small Cell Solution (SCS), Cisco RAN ManagementSystem (RMS), and explains how to use it to manage your network.
• Cisco RMS Solution Overview, page 5
• Femtocell Access Point Process Flow , page 10
• Cisco RMS High-Level Provisioning Flow , page 10
• Cisco RMS Interfaces, page 11
• Cisco RMS Software Architecture, page 14
• Cisco RMS Physical and Virtual Architecture, page 17
Cisco RMS Solution OverviewThe Cisco RAN Management System provides different workflows and services to support enhancedprovisioning andmanaging capabilities for both, 3G and LTE Femtocells. These services include provisioningand management functions such as, device configuration, status monitoring, firmware upgrade, data retrieval,and troubleshooting.
The following are a few key functionalists of the Cisco RMS solution:
• Device activation and configuration
• Software upgrade and status monitoring of devices
• Performance monitoring through Key Performance Indicator (KPI) data uploaded by devices
• Enhanced access to the device alarm data
• Troubleshooting of devices
• Remote Authentication Dial In User Service (RADIUS) for device authorization on Home NodeBGateway (HNB-GW) including per device whitelist support
• Dynamic Host Configuration Protocol (DHCP) service for allocating IPSec addresses
Cisco RAN Management System Administration Guide, Release 4.x OL-32398-01 5
-
The Small Cell RMS solution integrates with the Cisco Broadband Access Center (BAC) for Telecom andWireless, as well as the Cisco ASR 5000 Gateway that plays the HNB-GW and Security Gateway (SeGW)roles.
Cisco RMS Solution ComponentsThe Cisco RMS solution comprises of the following components that provide end-to-support in provisioning,managing, and maintaining the Femtocell access points (FAPs or APs, used interchangeably in this guide):
Provisioning Management GatewayThe Provisioning Management Gateway (PMG) provides a programmatic integration interface, Northboundinterface (NBI) API, to the service provider Operating Support Systems (OSS) or Business Support Systems(BSS) for provisioning and managing access points (APs).
The PMG supports the following functions:
• Integration of API with OSS / BSS to enable:
◦Subscriber portal to communicate with the PMG to perform a device registration, update thewhitelist, and so on.
◦Mobile systems to compute and configure SAI, e911 location data on the FAP.
◦Care interface to access live data. For example, admin status, operator status, and so on.
• Provision of XML/HTTP API for requests and notifications
• Generation of KPIs (which PMG generates) in CSV (format) for PM files
• Installation on Cisco UCS x86 hardware with RedHat Linux OS
• Implementation of critical algorithm that automatically assigns...
◦AP
◦Regional SeGW, HNB-GW
◦Unique SAI
◦Unique Cell ID (so that Femtocell can be optimized or work efficiently)
◦RF & Management Groups
• Facilitation ofWhitelist management: it interfaces with the HNBGW like RADIUS interface apart frominteracting with the BAC so that it can directly update the IMSI to the HNB GW.
• Facilitation of Plan-Activate Flow; this enables the operator to register the AP separately, activateseparately, or group the registration and activation.
PMG provides the following interfaces for provisioning and CSR requests, and notifications:
• Provisioning Requests
◦Register
◦Activate / Deactivate
Cisco RAN Management System Administration Guide, Release 4.x6 OL-32398-01
Cisco RAN Management System OverviewCisco RMS Solution Components
-
◦Update
◦Update IMSI
◦Block / Unblock
◦Shutdown
◦Delete
• CSR Requests
◦Get Stored Data
◦Get Live Data
◦Reboot
◦Reset to Defaults
• Notifications (from PMG to the SP OSS or subscriber)
◦Assigned Data
◦Location Status
◦Service Operational
◦Service Error
The PMG workflow facilitates zero-touch activation flows by integrating with the Femtocell RAN Manager(FRM) and Broadband Access Center (BAC). On Femtocell registration, PMG communicates with FRM inorder to assign unique RF parameters. For example, FRM can assign a unique SAI for the Femtocell and PMGcan set this data on the Femtocell via BAC as well as notify the SP OSS about the assignment.
PMG utilizes FRM to select the appropriate provisioning, SeGW, and HNB-GW nodes for the Femtocell anddetermine location-specific RF scan configuration for the Femtocell. This location-groups data is providedto the BAC, which instructs the Femtocell to perform a radio scan on specific bands and frequencies that arerelevant in the area. After completing the radio scan and location check, BAC can notify PMG, which can,in turn, notify SP OSS.
The PMG is usually co-located with BAC on the same HW node.
Broadband Access CenterThe Broadband Access Center (BAC) is a versatile TR-069 (support TR-169, v1 and v2) management systemthat provides all essential Femtocell management functions whether it is AP configuration, firmware, dataretrieval (like get parameter value), troubleshooting (logs), and so on.
BAC supports the following functions:
• Maintenance of AP inventory in the RDU
• Implementation of policy-based configuration and firmware (FW) for APs—When the AP is contactingthe BAC for the first time, BAC pushes a specific configuration. When the AP contacts the BACsubsequently, it pushes specific parameters, when the device is sending NWL scan.
• Implementation of TR-069 standards. BAC also implements download service.
Cisco RAN Management System Administration Guide, Release 4.x OL-32398-01 7
Cisco RAN Management System OverviewCisco RMS Solution Components
-
• Implementation of Femtocell activation logic, which is on the DPE. PMG does not play any role on theFemtocell activation logic, although PMG provides the configuration values as part of the registrationto the BAC. Therefore it is BAC that pushes all the information to the FAP as part of the provisioningflow.
• Implementation of Oracle Berkeley database to store all the AP database information.
• Installation on Cisco UCS x86 hardware with Red Hat Linux OS.
Cisco RMS uses BAC as the TR-069 Auto Configuration Server (ACS), which contains the Regional DataUnit (RDU) and Device Provisioning Engine (DPE). The RDU is a central database of registration and RFdata. The DPE provides TLS secured TR-069 services and HTTPS download service for firmware and otherfiles (e.g. AGPS). The TR-069 extensions in DPE perform small cell activation flows including locationverification.
In a small deployment, RDU and DPE servers can be deployed on same hardware node.
For more information about the DPE, see Device Provisioning Engine, on page 8.
For more information about the RDU, see Regional Data Unit, on page 8.
Device Provisioning EngineThe DPE is part of Cisco Broadband Access Center. It acts as a Auto Configuration Server. It provides essentialfunctionality for remote management of 3G APs, such as discovery, registration, activation, configuration,live operations (get live data, factory reset, etc), service shutdown, and HTTPs Download support.
There are two kinds of DPEs: start-up DPE and home DPE. The ACS URL of the start-up DPEs is stored inthe 3G AP by the CloudBase. When it comes up for the first time, the 3G AP contacts the start-up DPE. ThisDPE then redirects the 3G AP to the home DPE based on geographical location of the 3G AP. On subsequentreboot, the 3G AP directly contacts the home DPE. The home DPE pushes new software/firmware,configuration, and performs location check.
Regional Data UnitThe RDU is also part of Cisco Broadband Access Center. It is the central part of the RMS and has a persistentdatabase. It stores the information related to 3G AP parameters such as: expected software/firmware image,expected location, network listen status, PLMN, LAC, SAC, Cell, CSG, RNC ID, SeGW, and HNB GW IPaddress, and network listen information.
The RDU receives all this data from the DCC UI, Ops Tools, and IT portal via the PMG (Provisioning andManagement Gateway). The RDU provides this data to the startup and home DPEs, on request. The DPE andRDU are distributed in the network.
Device Command and ControlThe Device Command and Control (DCC) provides the following UI and CLI tool that can be used to manageCisco RMS and devices for device activation, administration, and troubleshooting.
DCC UI
The DCC UI provides the framework within which all the user interface applications reside. The followingapplication solutions are provided within the DCC UI:
Cisco RAN Management System Administration Guide, Release 4.x8 OL-32398-01
Cisco RAN Management System OverviewCisco RMS Solution Components
-
• Enhanced Groups & IDs Management—Provides the ability to manage, edit, import, and export grouptypes and instances and ID pool types and instances.
• Device Manager—Provides device management capabilities based on user permissions (Read only /Read & Write / Read & Write Advanced).
Ops Tools
The Ops Tools are a set of CLIs that enables the following functions:
• Bulk device management (e.g. connection requests, reboots)
• Device searches (based on group, etc)
• Device data retrieval
• Device property setting
• Re-balance of group and ID assignments
• BFST
• GPS Data Export
• Factory restore
In addition, the Ops Tools can be used in a workflow to perform group operations such as upgrades or movingdevices from default provisioning groups.
Prime Access RegistrarThe Prime Access Registrar (PAR) is used for AAA authentication. It provides AP authentication on theHNB-GW and delivers AP whitelists to HNB-GW via RADIUS.
Prime Network RegistrarThe Prime Network Registrar (PNR), also called the DHCP server, is used to allocate IPSec addresses forSeGW via DHCP. The lease database can then be queried to discover the current IP address of an AP.
Upload ServerThe Upload Server provides a high scale service for receiving and processing file uploads from the Femtocells.All the logs from the FAP are uploaded to the Upload Server.
The Upload Server supports the following functionality:
• Supports only HTTPS
• Uploads AP system logs, PM file uploads, and performance data
• Bundles files for distribution to the SP OSS
• Exposes the HTTP and SFTP interface towards the SP OSS
• Purges old files.
Cisco RAN Management System Administration Guide, Release 4.x OL-32398-01 9
Cisco RAN Management System OverviewCisco RMS Solution Components
-
• Provides detailed KPIs in the CSV PM files
• Runs on UCS x86 on the Red Hat Linux
Femtocell Access Point Process FlowThe following describes the life cycle of an AP life cycle from procurement to service commissioning:
Procedure
Step 1 When an AP is manufactured, there are two processes that occur:
• The AP manufacturing information gets fed in to the production system (server). Like the serial numberof AP, basic certificate, and so on.
• The AP is dispatched to the Central Warehouse (factory) along with the AP manufacturing informationthat was fed into the production server.
Step 2 The information from the production system is fed into the Cloudbase Activation Server (CAS), which isspecific to the Ubiquisys AP. The information would include the serial number of the AP, basic certificate,service provider information, and so on.
Step 3 Now a subscriber requests for the AP service through a retailer, customer care, or via a web interface. Thesubscriber provides all the information like, location, authorized user list, and other subscription details.
Step 4 The subscription details are fed into the OSS system. OSS internally calls the Cisco RMS component tobasically register the device.
Step 5 On completion of the subscription details, a small cell (AP) is delivered to the subscriber from the CentralWarehouse.
Step 6 After the AP gets delivered, the subscriber connects the device and powers it up.Step 7 When the AP powers up for the first time, it goes to the CAS and downloads the appropriate image (when
the information is fed into the CAS, the service provider mapping, which is the serial number meant for aspecific service provider to identify the appropriate firmware to be downloaded).The AP activation occurs after the particular FW gets pushed to the AP.
Step 8 RMS provisioning follows next. This is final automated, zero-touch plug and play activation that occurs.(from step 7 to 10)
Step 9 All auto-configurations, like different parameters for RAN, RF parameter, and so on, get configured.Step 10 After the auto-configuration is complete, that is administration, radio access network, and operations services
are up, the service is provided to the subscriber.
Cisco RMS High-Level Provisioning FlowA high-level workflow of the Cisco RMS and the various components is described as follows:
Cisco RAN Management System Administration Guide, Release 4.x10 OL-32398-01
Cisco RAN Management System OverviewFemtocell Access Point Process Flow
-
Procedure
Step 1 To register an AP, the SP OSS calls the register message from the PMG for the parameters like, EID (entityID or serial number of the device). The operator can provide the whitelist (if it is a closed mode support) andlocation information (for example, some service providers provide latitude and longitude, while others serviceproviders may not provide the location) or associate the device with the area group based on which area itbelongs to.
Step 2 When the register message comes to the PMG, the PMG goes to the BAC and adds that device entry andupdates the whitelist.
Step 3 Next, when the FAP comes up for the first time, it sends a BootStrap to the BAC. Then a HTTP establishmentoccurs between the BAC and FAP, certificate based authentication occurs, and at the end, the Inform Response.
Step 4 After the Inform Response is done, BAC pushes the baseline configuration to the FAP. Part of the baselineconfiguration is the baseline parameters like NWL scan, HNB GW IP add, and scan on boot=true.
Step 5 The FAP performs the NWL scan, and it sends that information by indicating whether the scan is completedor not.
Step 6 When the NWL scan is completed, BAC gets the NWL data from the FAP. The NWL data is the TR-069 datamodel attribute that the BAC fetches from the FAP.
Step 7 After receiving the NWL data, the BAC performs a location verification; after location verification is passed,the BAC sends the location verification status to the PMG and the SP OSS. If the OSS operator wants toactivate the FAP, the operator will activate the device.Cisco RMS provides the following activation support:
• At the registration stage, the operator can set the AP to activate at the end of the registration
• Activation can be performed explicitly. That is, whenever the activation happens, the operator canperform an Admin Up to the FAP, then the FAP starts IPSec tunnel establishment with the HNB GW,authentication takes place, FAP gets the IPSec address from the CNR, then it goes basically for the HNBGW registration request; in the HNB GW Registration request, the RADIUS Access Request comes tothe CAR, the CAR verifies whether i is a valid FAP or not. The CAR checks if it has the EID of theFAP, whether the proper IP address is configured, and validates it. After all checks are complete andauthenticated, the FAP comes to the operational state.
Cisco RMS InterfacesThe following figure illustrates the various Cisco RMS interfaces and interactions.
Cisco RAN Management System Administration Guide, Release 4.x OL-32398-01 11
Cisco RAN Management System OverviewCisco RMS Interfaces
-
Cisco RMS interacts with the various interfaces as follows:
Service Provider OSSCisco RMS exposes programmatic APIs, which use XML over HTTP, to interact with the SP OSS. CiscoRMS exposes a kind of XSD schema that the OSS uses to communicate to RMS.
There are several APIs that are used for signatures, AP registration and activation that the SP OSS uses tocommunicate with the Cisco RMS.
Provisioning Management GatewayPMG is a generic provisioning and management application that provides the necessary workflow componentbetween the Service Provider (SP) IT/OSS applications (for example, service management and customer care)and the Cisco provisioning system, Broadband Access Center (BAC). It exposes the NBI API, which is XMLover HTTP, to enable the SP OSS to communicate with the PMG. The PMG in turn sends a set of notifications
Cisco RAN Management System Administration Guide, Release 4.x12 OL-32398-01
Cisco RAN Management System OverviewService Provider OSS
-
to the SP OSS. For example, PMG assigns the LAC and Cell ID for a particular registered device. Thisinformation is passed back to the SP OSS.
Provisioning and Management Gateway DBProvisioning andManagement Gateway (PMG)DB provides a geo-spatial lookup service for PMG (read-only).It takes a location, defined by latitude and longitude, and returns the name of a group (for example, polygon).PMG then uses this group for automatic assignments. PMGDB operates on Oracle and is shipped as installationscripts, schema files, and stored procedures. It is expected that the operator provides the Oracle license andmaintenance.
Broadband Access CenterCisco RMS and FAP-related alarm are logged on the BAC. All component-related alarms, for example, alarmsthat PMG raises and so on, are sent directly to the Prime Suite, which is the Network Management System(NMS) interface.
Cisco RMS has three categories of alarms:
• Device or AP Alarms—A set of alarms that is received from the AP. For example, unable to connect tothe HNB GW, or some sector has gone down, or radio status is not up. All these alarms come to theBAC and from BAC, it goes to the Prime Suite (Network Management System [NMS]). Therefore thealarm is converted to TR-069 to the SNMP and the alarm is sent to the Prime Suite. This is called thedevice alarm or AP alarm.
• Component-specific Alarm—All component specific alarms are sent to the BAC. For example, PMGis not able to get some resource, does not have enough memory. Those specific alarms raised by thecomponent are sent directly to the NMS or Element Management System (EMS).
• System-specific Resource Alarm—Cisco RMS does not participate in resource-specific alarms like CPU,I/O, disk, memory, and so on. The Prime Suite and VMware vCenter that are running on the Cisco UCShardware, monitor and track the utilization and convert the alarms and sends them back to the PrimeSuite.
Access PointThe Remote management module (RMM) is the TR69 client interface between the Cisco RMS and the APthat uses the TR-69 data model or TR-196 data model to manage object and perform actions like get parametervalue, set parameter value, and so on.
The Ubiquisys FAP supports a concept called Cloudbase Server (not supported on IPA FAP).
Whenever an AP comes up, it contacts the CAS. The CAS has information about what firmware to push tothe AP, Cisco RMS IP address, and SeGW IP address. This information comes from the CAS and the AP getsbooted with that particular image which it has got fm the CAS. Now the AP knows the Cisco RMS IP addressor the fully qualified domain names (FQDNs) and the SeGW FQDN so the AP starts communicating withthe RAN server.
Therefore, when the AP comes up, it contacts the Cisco RMS, which in turn configures a set of parametersback to the AP. Then the AP contacts the SeGW and HNB GW via the luCS and luPS on the RAN server and
Cisco RAN Management System Administration Guide, Release 4.x OL-32398-01 13
Cisco RAN Management System OverviewProvisioning and Management Gateway DB
-
the proceeds to contact the Cisco RMS to get the AAA. When the authentication is complete, the AP goes tothe SP MSC or SP GGSN, etc.
Cisco Radio Access NetworkThe Cisco Radio Access Network (RAN) interacts and interfaces with the Cisco RMS. Though RAN is nota Cisco RMS component, the Prime Access Registrar component of the Cisco RMS interacts with the RANfor authentication whenever an AP contacts the Cisco RMS.
The Cisco RMS interacts with the RAN to configure the AAA/RADIUS whitelist on the HNB GW to get thesystem up and running.
The Prime Network Registrar, which is the DHCP server interacts with the RAN because it is responsible forassigning the IP address to a given AP.
Cisco RMS Software ArchitectureThe following figure illustrates the Cisco RMS software architecture.
Cisco RMS architecture is divided into three logical components:
Central RMS NodeIn the Central RMS node, the DCC UI, PMG, and BAC RDU components of the Cisco RMS are installed ona separate node.
Cisco RAN Management System Administration Guide, Release 4.x14 OL-32398-01
Cisco RAN Management System OverviewCisco Radio Access Network
-
The Central node can be paired with any number of serving nodes.
Figure 1: Central RMS Node
In any of the Cisco RMS deployments, it is mandatory to have at least one Central node.
To deploy the Central node, it is mandatory to procure and install VMware with one VMware vCenter perdeployment. For more information, see the Cisco RAN Management Systems Installation Guide, Release 4.0.
Serving RMS NodeIn the Serving RMS node, the BAC DPE, PNR, and PAR components of the Cisco RMS are provided on aseparate node.
Cisco RAN Management System Administration Guide, Release 4.x OL-32398-01 15
Cisco RAN Management System OverviewServing RMS Node
-
The Serving node must be combined with the Central node. To add additional Serving nodes, the propertiesof the additional Serving nodes must be configured on the Central node.
Figure 2: Serving RMS Node
The Serving node can be scaled horizontally, which means that there can be multiple Serving nodes with oneCentral node depending on how many APs need to be supported.
The AP (HNB) always interacts with the Serving node. APs use the Serving node IP address to reach theCisco RMS. The IP address or FQDN of the Cisco RMS that is configured on the AP is part of the Servingnode and not the Central node, which is hidden from the AP.
For example, if a customer has around 1 million devices up and running, and they have 16 different Servingnodes, each of the devices will be configured to interact with specific Serving nodes. That is how a Servingnode can be scaled horizontally.
Upload RMS NodeIn the Upload RMS node, the Upload Sever is provided on a separate node.
Cisco RAN Management System Administration Guide, Release 4.x16 OL-32398-01
Cisco RAN Management System OverviewUpload RMS Node
-
The Upload RMS node must be combined with the Serving node.
Figure 3: Upload RMS Node
For more information about the Upload Server, see Upload Server , on page 9.
Cisco RMS Physical and Virtual ArchitectureThis section lists the physical and virtual architecture of the Cisco RMS.
The Cisco RMS can be deployed in one of these modes:
All-in-One RMS NodeIn the All-in-One RMS node, all the components of the Cisco RMS solution is provided on a single host.
Cisco RAN Management System Administration Guide, Release 4.x OL-32398-01 17
Cisco RAN Management System OverviewCisco RMS Physical and Virtual Architecture
-
The physical hardware has one virtual machine running a central node and one serving node.
Figure 4: All-in-One RMS Node
In an All-In-One RMS node, the Serving Node comprises of the Upload Sever VM and the VM combiningthe BAC DPE, PNR, and PAR components; the Central Node comprises of the VM combining the DCC UI,PMG, and BAC RDU VM components.
To deploy the All-in-One node, it is mandatory to procure and install VMware with one VMware vCenterper deployment. For more information, see the Cisco RAN Management Systems Installation Guide, Release4.0.
Distributed RMS NodeIn a Distributed RMS deployment mode, the following nodes are deployed:
• Central RMS Node, on page 14
• Serving RMS Node, on page 15
• Upload RMS Node, on page 16
In a Distributed deployment mode, up to 10,000 APs are supported.
Cisco RAN Management System Administration Guide, Release 4.x18 OL-32398-01
Cisco RAN Management System OverviewDistributed RMS Node
-
C H A P T E R 3Device Command and Control
• DCC Overview, page 19
• DCC UI Requirements, page 19
• Device Manager User Roles and Permissions, page 20
• Information About the DCC UI, page 21
• Logging In to the DCC-UI, page 22
• Configuring DCC Dialog Boxes, page 23
• Configuring the DCC Dashboard, page 28
DCC OverviewTheDevice Command andControl (DCC) application is the user interfacewithin the CiscoRemoteManagementSystem (RMS) that provides operation, administration and management of 3G access points. It is a collectionof tools and contains both a graphic user interface (GUI) and a command line interface (CLI). It enables thefollowing functions:
• Device data export
• Upgrade monitoring
• Device group management
• Single device management for troubleshooting
• Mass connection request and reboot
• SAI pool management
DCC UI RequirementsThe DCC UI is supported on the following browser:
• Mozilla Firefox Version 16.0.1 and above.
Cisco RAN Management System Administration Guide, Release 4.x OL-32398-01 19
-
Device Manager User Roles and PermissionsTo access the various device manager operations you must have the correct permission. Your permissionsdetermine which functionality you have within the system.
Table 1: Device Manager Functionality According to User Permissions
User Permission Allows FunctionalityOperationFunctionality
Read-write AdvancedRead-write BasicRead-only
YesYesYesDashboardView
Yes——Live Data
YesYes—UpdateProvision
YesYes—Shutdown
Yes——Log Upload Triggers
YesYes—Static Neighbors
YesYes—Device Replacement
YesYes—Connection RequestPerform
YesYes—On-Demand Log Upload
YesYes—Reboot
YesYes—Factory Reset
Yes——Set Live Data
Yes——Set Modified Live Data
YesYes—Register a DeviceRegister
The three access levels restrict basic users to access advanced operations that require knowledge of deviceparameters. The levels of access are:
• Read Only: Allows access to operations listed under ‘View’ button (currently only Dashboard) only.This is meant for a user with very basic knowledge.
• Read Write Basic: Allows access to operations that require basic knowledge such as Registration,Updation, Reboot, Shutdown, Reset, Static neighbours, CR, On demand log upload and so on in additionto the Read Only operations.
• Read Write Advanced: Allows access to advanced operations such as View/Set Live Data, ModifiedLive Data, Log upload triggers and so on in addition to the Read Write Basic operations. This is meantfor a user with advanced knowledge.
Cisco RAN Management System Administration Guide, Release 4.x20 OL-32398-01
Device Command and ControlDevice Manager User Roles and Permissions
-
Information About the DCC UIThe DCC UI presentation framework has a generic design and layout. All the applications hosted on thisframework use this layer for display. The common elements like the header, application navigation, andprimary navigation are available to all the applications installed on this framework. The application navigationis displayed below the header. All the installed and enabled applications that are approved are displayed inthis screen.
Figure 5: DCC UI Main Screen - Application Presentation Page
The DCC UI includes the following components:
Device Manager
The Device Manager consolidates the individual CPE management functions and provides the ability toeasily navigate through the device data model and view values.
Cisco RAN Management System Administration Guide, Release 4.x OL-32398-01 21
Device Command and ControlInformation About the DCC UI
-
Some of the components of the device manager are located on the same machine, and the communicationwith the CPE occurs through Provisioning Management Gateway (PMG), and Broadband Access CenterRegional Distribution Unit (BAC RDU).
Upgrade Monitor
The Upgrade Monitoring Tool (UMT) is a web based tool that supports multiple users concurrently viewinga single monitoring job or executing multiple monitoring jobs. The tool is able to efficiently scale by receivingreal time events from BAC instead of polling the devices.
Groups and IDs
Groups and IDs allows you to manage the group types, groups, pool types and pools on the BAC.
Admin
Admin allows you to manage Users and Roles without having to access the DCC UI Admin User Interfacedirectly.
Configuration
Configuration allows you to manage global level configuration of devices in BAC RDU for properties suchas DN Prefix Format. This tab is disabled by default and can be enabled by updating 'superuser' role fromAdmin tab->Roles.
Logging In to the DCC-UIThe DCC UI login and authentication system verifies the login credentials and authentication details.
DCC UI Password Policy:
As part of security measures, the password policy is implemented for DCC UI. Ensure that you adhere to thepassword policy. The new password must be minimum 8-16 characters long and alphanumeric, should bemixed case, should contain one of the special characters(*,@,#) and no spaces.
Procedure
Step 1 Navigate to the DCC-UI application URL. Below is a sample url:https://central node eth1 IP address/dcc_ui/admin/Login.do
Step 2 Enter a valid Username and Password in the appropriate text boxes and click Log In.The credentials are verified by the Login and Authentication system. A new user is logged in with the defaultpassword and is prompted to enter a new password.
For the new user changing the password is a must to log in to the DCC UI application. With thedefault password user cannot log in to the application.
Note
Step 3 Enter the existing and new password as requested and click Save. After entering the new password theapplication redirects you to the log in page to log in to the DCC UI application with the new password.Password changed successfully pop up box appears on Save if the new password provided adheres to thepassword policy.
Cisco RAN Management System Administration Guide, Release 4.x22 OL-32398-01
Device Command and ControlLogging In to the DCC-UI
-
A popup is displayed that requests the user for which you are changing the password. This is a browser featureand not triggered through the DCC UI.
Figure 6: Confirm Password Change Dialog
In order to disable this popup, the password history needs to be disabled for the browser through the browseroptions.
If you are an application administrator for a specific application, the specific application page displayson successful login.
If the login credentials fail to authenticate, you are returned to the login page with a failure message.
Note
DCC UI Session expiry: The session times out if the period of inactivity exceeds the time limit set for theDCC UI. If you try to access the page after the session has expired, then you are navigated back to the loginpage. The session timeout period is 45 minutes.
DCC UI Input Validation: As part of security feature XSS implementation, invalid data such as script tagsor html tags are not allowed.
Step 4 When you are finished, click Log Out at the top right corner to exit from the current session.
Configuring DCC Dialog BoxesThe dialog boxes of the Device Command and Control user interface can be customized according to yourneeds. Each of the dialog boxes is controlled via an xml file contained in the/rms/app/rms/conf directory.For example, the xml file for the dialog box for registering a device in Residential mode is named assdm-register-residential-screen-setup.xml and for Enterprise mode is named assdm-register-enterprise-screen-setup.xml. You can open this file in an xml or text editor and changeit as necessary to customize the dialog box for your needs. The xml file for the update screen for registeringa device in Residential mode is named as sdm-update-residential-screen-setup.xml, and for Enterprisemode is named assdm-update-enterprise-screen-setup.xml.
This is an example of the sdm-register-residential-screen-setup.xml file:
-
reproduce, or allow others to use this program without specific writtenauthorization of Cisco Systems, Inc.
Copyright 2012 Cisco Systems, Inc. All rights reserved.-->
areatrueArea99px
198px/sdm/handleService.do?action=Get
Groups&additionalInfo=Area
Select the area of the device.Areagroupsstring
rfProfilefalseRF Profile99px
198px/sdm/handleService.do?action=Get
Groups&additionalInfo=RFProfile
Select an optional RF Profile to be used.RFProfilegroupsstring
-
dnmListfalseDNM List95px
mcc_or_mccmncAdd MCC or MCC/MNC200pxDNM List50pxfalse
Updates the DNM list. MCC may be 3 digits long, MCC/MNC must be 5 to 6
digits long.DNMIDListexpected_locationmcc_or_mccmnc_list
ednListfalseEDN List95px
radio_neighbor_idAdd MCC or MCC/MNC200pxEDN List50pxfalse
Updates the EDN list.EDNIDListexpected_locationradio_neighbor_id_list
saitrueSAI100px
200px
Sets the SAI.SAIelementsai
accessModefalseClosed Mode100px
closedopen
acl
Controls the access mode is closed (checked) or open (unchecked).
AccessModeaccess_controlaccess_mode
Cisco RAN Management System Administration Guide, Release 4.x OL-32398-01 25
Device Command and ControlConfiguring DCC Dialog Boxes
-
aclfalseWhite List95px
textAdd IMSI150px\d{14}$|\d{15}$ACL50pxfalse
Updates the ACL list.AccessControlListaccess_controlstring_list
-->
The DCC UI exposes xml files which the customer can modify to build their user interface.Note
Dynamic Screen Configuration FilesThis table lists the xml files that are used to customize the associated DCC UI screens with additionalparameters. The complete list of configurable parameters that can be used is provided in the RMSConfigurableParameters for Release 4.0 document.
Folder PathXML FilenameDCC UI AreaDCC UI Dialog Box
rms/app/rms/confsdm-register-enterprise-screen-setup.xmlDeviceManagerDeviceRegistration—Enterprise
rms/app/rms/confsdm-register-residential-screen-setup.xmlDeviceManagerDeviceRegistration—Residential
rms/app/rms/confsdm-update-enterprise-screen-setup.xmlDeviceManagerUpdate DeviceRegistration—Enterprise
rms/app/rms/confsdm-update-residential-screen-setup.xmlDeviceManagerUpdate DeviceRegistration—Residential
rms/app/rms/confsdm-inter-freq-static-neighbors.xmlDeviceManagerInter-FrequencyNeighbors
rms/app/rms/confsdm-inter-rat-static-neighbors.xmlDeviceManagerInter-RAT Neighbors
rms/app/rms/confsdm-static-neighbors-filter-screen-setup.xmlDeviceManagerUpdate Static NeighborsFilter
rms/app/rms/confumt-setup.xmlUpgradeMonitor
Add Firmware Type
rms/app/rms/confumt-config.xmlUpgradeMonitor
Add Firmware Version
Cisco RAN Management System Administration Guide, Release 4.x26 OL-32398-01
Device Command and ControlDynamic Screen Configuration Files
-
Folder PathXML FilenameDCC UI AreaDCC UI Dialog Box
rms/app/rms/confuploadServers.xmlDeviceManagerLog Uploads andTriggers
Copy the xml file to/rms/app/rms/confdirectory from/rms/app/rms/doc/config/sampledirectory and makeappropriatechanges.
deviceParamsDisplayConfig.xmlDeviceManagerDashboard Display
rms/app/rms/confbgmt-add-group-screen-setup-Area.xmlGroups and IDsAdd Area Instance
rms/app/rms/confbgmt-add-group-screen-setup-Enterprise.xmlGroups and IDsAdd Enterprise Instance
rms/app/rms/confbgmt-add-group-screen-setup-FemtoGateway.xmlGroups and IDsAdd FemtoGatewayInstance
rms/app/rms/confbgmt-add-group-screen-setup-RFProfile.xmlGroups and IDsAdd RF Profile Instance
rms/app/rms/confbgmt-add-group-screen-setup-Site.xmlGroups and IDsAdd Site Instance
rms/app/rms/confbgmt-add-group-screen-setup-SAI-POOL.xmlGroups and IDsAddSAI-POOL Instance
rms/app/rms/confbgmt-add-group-screen-setup-CELL-POOL.xmlGroups and IDsAdd CELL-POOLInstance
Adding or Updating Fields in the Group Dialog BoxUse this task to make fields available in the Add/Update group dialog box.
Procedure
Step 1 Create a file named 'bgmt-add-group-screen-setup-.xml' in the /rms/app/rms/conf directory.Step 2 Enter an appropriate screen element configuration for each BAC property that is applicable to groups of this
group type, in the xml. This xml should validate against screen-setup.xsd, which is available in/rms/app/rms/doc/config/xsd for reference.
Step 3 Sample files should be referred to while preparing the configuration file. Thebgmt-add-group-screen-setup-Area.xml and bgmt-add-group-screen-setup-FemtoGateway.xml are availablein /rms/app/rms/doc/config/sample for reference.
Step 4 Use appropriate screen elements for each of the properties and save the file. Make screen elements 'Required'as needed. Follow the convention used in sample xml files. Set readable label names and appropriate tooltipmessages. Values for each field can be validated by setting a regular expression on textbox value.
Step 5 Restart the DCC UI application, so that it can pick up the new configuration file. Further changes made tothis file will be automatically reloaded by DCC UI after one minute.
Step 6 Open the add/update group screen. The screen should contain dynamically added input elements for all theconfigured properties as per the xml. If it does not, check for file loading/validation errors in DCC UI debug
Cisco RAN Management System Administration Guide, Release 4.x OL-32398-01 27
Device Command and ControlAdding or Updating Fields in the Group Dialog Box
-
log. Also the headers in the grid inside Groups main page should show labels configured inside XML insteadof property names.
Step 7 If you get an 'Unknown Parameter' error while adding/updating group with property values, make sure it isconfigured in pmg-profile.xml so that PMG can recognize them. The sample PMG files (configs, xmls, andxsds) are available in /rms/app/rms/doc/pmg for reference.Usually all the properties needed to be set on a group should be configured in XML file, otherwise the PMGmaintains only properties submitted in the add or update group request in FRM.
Group dialog boxes can be configured with Reserved mode or LAC ID.
Configuring the DCC DashboardThe Dashboard (combined view) can be configured dynamically with the help of a sample XML file presentin RMS. The sample file deviceParamsDisplayConfig.xml contains the default contents of the Dashboardscreen and is located at/rms/app/rms/doc/config/sample/deviceParamsDisplayConfig.xml.
Dashboard can be customized by copying this sample file to /rms/app/rms/conf directory of centralnode and adding/removing tags to any of its sections, for example, or, in accordance with xsd located at/rms/app/rms/doc/config/xsd/deviceParamsDisplayConfig.xsd.
You can open the xml file using VI editor and change it as necessary to customize the dashboard for yourneeds.
This is an example of the deviceParamsDisplayConfig.xml file:
groups
FemtoGatewayHNB-GW
group_parameterFemtoGateway:FC-MCCMCC
group_parameterFemtoGateway:FC-MNCMNC
parametersFC-LAC-IDLAC ID
Cisco RAN Management System Administration Guide, Release 4.x28 OL-32398-01
Device Command and ControlConfiguring the DCC Dashboard
-
group_parameterFemtoGateway:FC-RNC-IDRNC ID
parametersFC-SAC-IDSAC ID
parametersCELL-CONFIG-RAN-CELL-IDCell ID
access_controlAccessModeAccessMode
group_parameterFemtoGateway:FC-PROV-GRP-NAMEProvisioning Group
parameters/provisioning/classOfService/selectedClass of Service
elementServiceStatusService Provisioning StatusPre-requisites not met: AP not yet
bootstrapped
elementServiceStatusTSService Provisioning Status Timestamp
parametersFC-FIRST-RADIO-ONFirst Radio On
elementLocationValidLocation Validfalse
elementLocationValidTSLocation Valid Timestamp
location_status
Cisco RAN Management System Administration Guide, Release 4.x OL-32398-01 29
Device Command and ControlConfiguring the DCC Dashboard
-
DNMStatusDNM Location Status
location_statusDNMStatusTSDNM Location Status Timestamp
parametersFC-EDN-STATUSDetected Neighbors Status
parametersREPORTED-BANDS-SUPPORTEDBands Supported
parametersREPORTED-MAX-TX-POWERMax Transmission Power
parametersREPORTED-GPS-CAPABILITYGPS Capabilityint_to_boolean
elementBLOCKEDBlocked
parametersFC-CSON-STATUS-HANRQSS optimization status for HANR
parametersFC-CSON-STATUS-HSCO-M2FQSS optimization status for HSCO M2F
parametersFC-CSON-STATUS-HSCO-INNERQSS optimization status for HSCO Inner
parameters/cwmp/discovered/Inform.DeviceId.ManufacturerManufacturer
parameters/cwmp/discovered/Inform.DeviceId.ManufacturerOUIManufacturer OUI
parameters/cwmp/discovered/InternetGatewayDevice.DeviceInfo.ModelName
Model Name
parameters
Cisco RAN Management System Administration Guide, Release 4.x30 OL-32398-01
Device Command and ControlConfiguring the DCC Dashboard
-
/cwmp/discovered/InternetGatewayDevice.DeviceInfo.HardwareVersionHardware Version
parameters
/cwmp/discovered/InternetGatewayDevice.DeviceInfo.SoftwareVersionSoftware Version
parameters
/cwmp/discovered/InternetGatewayDevice.DeviceInfo.X_00000C_3GModuleVersion3G Module Version
parameters
/cwmp/discovered/InternetGatewayDevice.DeviceInfo.X_00000C_RouterModuleVersionRouter Module Version
parameters
/cwmp/discovered/InternetGatewayDevice.WANDevice.{i}.WANConnectionDevice.{i}.WANIPConnection.{i}.MACAddress
MAC Address
groupsEnterpriseEnterprise
groupsSiteSite
groupsAreaArea
groupsRFProfileRF Profile
elementActivatedActivated
parametersFC-LOG-PERIODIC-UPLOAD-ENABLEPeriodic Log Upload Enabled
parametersFC-LOG-PERIODIC-UPLOAD-INTERVALPeriodic Log Upload Interval
parametersFC-AP-ROLERole
Cisco RAN Management System Administration Guide, Release 4.x OL-32398-01 31
Device Command and ControlConfiguring the DCC Dashboard
-
parametersFC-AP-PURPOSEPurpose
parametersFC-RESERVED-MODEReserved Mode
elementREGISTEREDONRegistered On
Alias.FAPService.FAPControl.AdminStateint_to_boolean
Alias.FAPService.FAPControl.OpStateint_to_boolean
Alias.FAPService.FAPControl.RFTxStatusint_to_boolean
Alias.DeviceInfo.HardwareVersion
Alias.DeviceInfo.SoftwareVersion
Following is an example explaining how to add a new parameter, "JOB ID" to the "Assigned Data" sectionin the Dashboard:
1 Log in to central node as a root user.2 Copy the deviceParamsDisplayConfig.xml file to /rms/app/rms/conf folder.3 Open the file using VI editor and edit the parameters as shown in the example below:
parameters
FC-JOB-IDJOB ID
4 Save the changes using the command: :wq!5 Log in to DCCUI, and verify whether the newly added parameter JOB ID has been updated in the Assigned
Data section of the device dashboard.
If a configured parameter is not set for a particular device, it will not be visible in the Dashboard.Note
Cisco RAN Management System Administration Guide, Release 4.x32 OL-32398-01
Device Command and ControlConfiguring the DCC Dashboard
-
C H A P T E R 4Baseline Configuration
The Small Cell RMS solution supports provisioning of devices by configuring RMS components based onthe baseline configuration. The baseline configuration defines the BAC custom properties using a definedtemplate, depending on the software version and the device model. The baseline configuration defines anumber of scripts, templates, extensions, and images that are executed from the command line or using theUIs to configure various components.
• Configuring BAC, page 33
Configuring BACThe devices in the Small Cell RMS solution are managed through a larger set of TR-196 extension parametersto provide additional enhanced functionalities. These standard TR-196 extension parameters are used forretrieving device status information and for managing configuration through XML profiles (BAC templates).
The BAC configuration of the Small Cell RMS solution includes the following BAC custom properties thatare defined in the configuration template:
• Device Activation Custom Properties
• Location Aware Custom Properties
• RF Profiles Custom Properties
• Firmware Upgrade Custom properties
• ubi-config-vX.Y.Z Custom Properties
Device Activation Custom PropertiesThe below table lists the Device Activation Custom properties that are defined in the BAC configurationtemplate.
Cisco RAN Management System Administration Guide, Release 4.x OL-32398-01 33
-
DescriptionAccess TypeProperty TypeProperty Name
This custom property is used to determine ifthe device is previously detected as tampered.The property is set to "true" if the device istampered. Else, the value of the property isset to "false" or is non-existent. This customproperty is set by the activation flow logicand is used to determine if the device ispreviously detected as tampered.
Read OnlyBooleanFC-TAMPERED
This custom property is used to determine ifthe service is to be disabled before endingthe TR-069 session. If the property is set to"true", the device is in the shutdown mode.Else, the value of the property is set to "false"or is non-existent. This custom property isset by the RMS as a result of the Shutdownmessage on the device record in the RDU.
Read WriteBooleanFC-SHUTDOWN
This custom property is set by the activationflow logic on the device record in the RDUand indicates the service activation status.This custom property is set automatically bythe activation flow logic on the device recordin the RDU. The valid values are:Pre-requisites not met: AP tamperedPre-requisites not met: AP blockedPre-requisites not met: AP location is invalidEnablement pending Enablement error: Enabled Operation error: Operational
Read WriteStringFC-SERVICE-STATUS
This custom property is automatically set onthe device record in the RDU and indicatesthe last time when theFC-SERVICE-STATUS property is set. Theformat is as per TR-069 protocol and mustbe in Co-ordinated Universal Time (UTC)standard with a trailing 'Z'. This customproperty is set by the activation flow logicon the device record in the RDU.
Read OnlyDateTimeFC-SERVICE-STATUS-TS
This custom property is automatically set onthe device record in the RDU and indicatesthe first time the service is reported as"Operational". The format is as per TR-069protocol and must be in Co-ordinatedUniversal Time (UTC) standard with atrailing 'Z'. This custom property is set by theactivation flow logic on the device record inthe RDU.
Read OnlyDateTimeFC-FIRST-RADIO-ON
Cisco RAN Management System Administration Guide, Release 4.x34 OL-32398-01
Baseline ConfigurationDevice Activation Custom Properties
-
DescriptionAccess TypeProperty TypeProperty Name
This custom property is used to determine ifthe service is to be activated, and indicatesif the device is allowed for service. If theproperty is set to "true", the service isactivated, else the property is set to "false".The custom property is set by the RMS orthroughAdmin using UI on the device recordin the RDU.
Read WriteBooleanFC-ACTIVATED
This custom property includes the followingaccess mode type definitions, where: 0x00defines the Closed Access. 0x01 defines theHybrid Access. 0x02 defines the OpenAccess.
Read WriteByteFC-ACL-ACCESS-MODE
This custom property indicates the RANService Area Code.
Read WriteIntegerFC-SAC-ID
This custom property indicates the "LocationArea Code Identifier".
Read WriteIntegerFC-LAC-ID
This custom property indicates the device RFcandidate list.
Read WriteStringFC-RF-CL
This custom property indicates the RNC ID.Read WriteIntegerFC-RNC-ID
This custom property indicates the TR-069Periodic Inform Interval and is set to '300'(five minutes).
Read WriteIntegerFC-PERIODIC-INFORM-INTERVAL
This custom property indicates the MobileCountry Code.
Read WriteIntegerFC-MCC
This custom property indicates the MobileNational Code.
Read WriteIntegerFC-MNC
This custom property indicates the AP IPsectraffic selector string.
Read WriteStringFC-IPSEC-TRAFFIC-SEL
This custom property indicates the FemtoHNBGateway FullyQualifiedDomainNameand is set to ASR5K HNB Gateway IPaddress.
Read WriteStringFC-FGW-FQDN
This custom property indicates the LAC/RACcandidate list.
Read WriteStringFC-LAC-RAC-CL
This custom property indicates the list ofUMTS RF frequencies for band-II andband-V for Network Listen scanning.
Read WriteStringFC-NWL-SCAN-RANGE
This custom property indicates the IPsecserver host IP address and is the OAMinterface of the Security Gateway (SeGW).
Read WriteStringFC-IPSEC-SERVER-HOST
Cisco RAN Management System Administration Guide, Release 4.x OL-32398-01 35
Baseline ConfigurationDevice Activation Custom Properties
-
DescriptionAccess TypeProperty TypeProperty Name
This custom property is used to reduce thenumber of UEs allowed in the CELL_DCHstate to fewer than the number the hardwareis capable of supporting. If the value of thisattribute is greater than or equal to the valueof the attribute maxNumCellDchUes, thereare no changes. The minimum value is set to"0", and the maximum value is "64". Thedefault value is "64".
Read WriteIntegerFC-MAX-NUM-CELL-OVERRIDE
Location Aware Custom PropertiesThe below table lists the Location Aware Custom properties that are defined in the BAC configuration template.
DescriptionProperty TypeProperty Name
This custom property is set by the activation flow logic on thedevice record in the RDU once the location verificationmethodis completed. If the property is set to "true", the location is valid.Else, if the property is set to "false" or is non-existent, thelocation is not valid.
BooleanFC-LOCATION-VALID
This custom property indicates the last time theFC-LOCATION-VALID property was set. The property isset by the activation flow logic on the device record in the RDUas per TR-069 protocol and must be in the Co-ordinatedUniversal Time (UTC) standard with a trailing 'Z'.
DateTimeFC-LOCATION-VALID-TS
This custom property is set by RMS as a result of "Register" or"Update" messages on the device record in the RDU. Theproperty is set by the activation flow logic to determine if thelocation verification methods must be executed. If the locationverification is set to "true", all location methods are skippedand the flow removes all location verification statuses and setsFC-LOCATION-VALID to "true".
BooleanFC-NO-LV
This custom property indicates the DNM location verificationmethod status and is set by the activation flow logic on thedevice record in the RDU. The valid values are: Missing validMCC/MNCs Error: Wrong location Valid location Ifthe property is not present, then DNM location verification hasnot yet occurred or is disabled.
StringFC-DNM-STATUS
This custom property is set by the activation flow logic on thedevice record in the RDU and indicates the last time theFC-DNM-STATUS property is set. The format is as per TR-069protocol andmust be in the Co-ordinated Universal Time (UTC)standard with a trailing 'Z'.
DateTimeFC-DNM-STATUS-TS
Cisco RAN Management System Administration Guide, Release 4.x36 OL-32398-01
Baseline ConfigurationLocation Aware Custom Properties
-
DescriptionProperty TypeProperty Name
This custom property is a comma separated list of valid MCCor MCC/MNCs and is configured upon initial setup of BAC.The property is set by the RMS as a result of the "Register" or"Update" messages on the device record in the RDU. Theproperty is used by the activation flow logic and comparesagainst the detected neighbors (from NWL) to determine if thedevice location is valid or not.
StringFC-DNM-LIST
This custom property value indicates the minimum number ofexpected neighbors that must be matched against the detectedneighbors (from REM). If the value is not present, the BACactivation flow logic uses a default value of "1" (indicating asingle neighbor must be matched).
IntegerFC-EDN-TOLERANCE
Firmware Upgrade Custom PropertiesThe below table lists the Firmware Upgrade Custom properties that are defined in the BAC configurationtemplate.
DescriptionProperty TypeProperty Name
Conditional that defines if Router chipsetfirmware upgrades or downgrades are enabledor disabled for the UBI Access Points.
BOOLEANFIRMWARE-DPH-SO16-ENABLE
ASCII textual string to define the explicit Routerfirmware and software version for the UBIAccess Points.
STRINGFIRMWARE-DPH-SO16-VERSION
ASCII textual string to define the explicit nameof the Router firmware/software image for theUBI Access Points.
STRINGFIRMWARE-DPH-SO16-IMAGE
RF Profiles Custom PropertiesThe below table lists the RF Profiles Custom properties that are defined in the BAC configuration template.
DescriptionProperty ValueProperty Name
This custom property contains the percentage of theMaximum Total Wideband Transmit Power that isallocated to the primary CPICH. The Primary CPICHPower is calculated from the Primary CPICH PowerPercent in dBm and the Maximum Total WidebandTransmit Power in dBm. The minimum value of theproperty is 1 and the maximum value is 250.
200FC-POWER-PERCENT
Cisco RAN Management System Administration Guide, Release 4.x OL-32398-01 37
Baseline ConfigurationFirmware Upgrade Custom Properties
-
DescriptionProperty ValueProperty Name
This custom property defines the transmission poweroffset measured in {{units}} of the PCH relative tothe Primary CPICH power. The minimum value ofthe property is -350 and the maximum value is 150.
-80FC-PCH-POWER
This custom property defines per downlink RABtype configuration used in downlink power control.Each entry in the list consists of Downlink RABType, Maximum Downlink Transmitter Power, andDownlink BLER Target. The property can includea maximum of eight entries. The allowed value forMaximumDownlink Transmitter Power is an integerin the range of -350 to 150 and the allowed valuefor Downlink BLER Target is an integer in the rangeof -63 to 0 with a scale factor of 10. The maximumvalue is 512.
-70, -60, -30,-27, -20, 0, 10,20
FC-DLINK-POWER-CTRL-PER-RAB
This custom property defines the transmission poweroffset measured in {{units}} of the FACH relativeto the Primary CPICH power. The minimum valueof the property is -350 and the maximum value is150.
-10FC-FACH-POWER
This custom property indicates the level of HighSpeed Downlink Shared Channel (HS-DSCH)measurement power offset. The minimum value ofthe property is -12 and the maximum value is 26.
13FC-HSDSCH-POWER
This property indicates the power level of the HighSpeed Shared Control Channel (HS-SCCH) relativeto CPICH. The minimum value of the property is-28 and the maximum value is 0.
-16C-HSSCCH-POWER
This custom property defines the transmission poweroffset measured in {{units}} of one AICH relativeto the Primary CPICH power. The minimum valueof the property is -22 and the maximum value is 5.
-8FC-AICH-POWER
This custom property defines the transmission poweroffset measured in {{units}} of the Secondary SCHrelative to the Primary CPICH power. Theminimumvalue of the property is -350 and the maximum valueof the property is 150.
-80FC-SSCH-POWER
This custom property indicates the value of thetransmission power of the Primary Common PilotChannel (P-CPICH). The P-CPICH physical channelcarries the common pilots of the cell. The maximumvalue of the property is 64.
1FC-PCPICH-POWER
Cisco RAN Management System Administration Guide, Release 4.x38 OL-32398-01
Baseline ConfigurationRF Profiles Custom Properties
-
DescriptionProperty ValueProperty Name
This custom property defines the transmission poweroffset measured in {{units}} of the BCH relative tothe Primary CPICH power. The minimum value ofthe property is -350 and the maximum value is 150.
-50FC-BCH-POWER
This custom property defines the transmission poweroffset measured in {{units}} of the Primary SCHrelative to the Primary CPICH power. Theminimumvalue of the property is -350 and the maximum valueis 150.
-10FC-PSCH-POWER
This custom property defines the headroom used bythe dynamic HSDPA power allocation algorithm atthe Baseband Processor in terms of the percentageof the maximum available 3GAP power. Theminimum value of the property is 0 and themaximum value of the property is 100.
8FC-POWER-HEADROOM
This custom property defines the maximumtransmission power offset measured in {{units}} ofthe PICH channel relative to the Primary CPICHtransmission power. The minimum value of theproperty is -10 and the maximum value is 5.
-8FC-PICHPOWER
This custom property defines the power used totransmit the E-DCH HARQ AcknowledgementIndicator Channel or E-DCHRelativeGrant Channeland is relative to the CPICHTransmitter Power. Theminimum value of the property is -127 and themaximum value is 127.
-64FC-EHICH-POWER
This custom property defines the power used totransmit the E-DCH Absolute Grant Channel and isrelative to the CPICH TX Power. The minimumvalue of the property is -128 and the maximum valueis 127.
-20FC-EAGCH-POWER
The custom property has a maximum value 8 and aminimum value 0.
4FC-EDPCCH-POWER
ubi-config-X.Y.Z Custom PropertiesThe below table lists an example of the ubi-config-v3.4.2 Custom properties that are defined in the BACconfiguration template.
DescriptionPropertyType
Property Name
Enables or disables the ability to send FAPinformation periodically to a designated File Server.
BooleanFC-LOG-PERIODIC-UPLOAD-ENABLE
Cisco RAN Management System Administration Guide, Release 4.x OL-32398-01 39
Baseline Configurationubi-config-X.Y.Z Custom Properties
-
DescriptionPropertyType
Property Name
URL specifies the destination file location. HTTPand HTTPS transports MUST be supported.
StringFC-LOG-PERIODIC-UPLOAD-URL
Absolute time references in UTC to determinewhenthe FAP will initiate the periodic file upload.
DateTimeLOG-UPLOAD-PERIODIC-TIME
Username to be used by the FAP to authenticatewith the file server.
StringLOG-PERIODIC-UPLOAD-USERNAME
Password to be used by the FAP to authenticatewith the file server.
StringLOG-PERIODIC-UPLOAD-PASSWORD
The duration in seconds of the interval for whichthe FAP MUST create an Performance File andattempt to upload the file to URL ifPeriodicUploadEnable is true.
IntegerFC-LOG-PERIODIC-UPLOAD-INTERVAL
The duration in seconds of the interval for whichthe CPE MUST attempt to connect with the ACSand call the Informmethod if PeriodicInformEnableis true.
IntegerFC-PERIODIC-INFORM-INTERVAL
Name of the local time zone (human readablestring).
StringLOCAL-TIME-ZONE-NAME
First public NTP timeserver. Either a host name orIP address
StringNTP-SERVER-1
First operator NTP timeserver. Either a host nameor IP address. Manual reboot of AP required inorder for a change to this parameter to take effect.
StringOPERATOR-NTP-SERVER-1
Second operator NTP timeserver. Either a hostname or IP address. Manual reboot of AP requiredin order for a change to this parameter to take effect.
StringOPERATOR-NTP-SERVER-2
Comma-separated list (maximum length 32) ofstrings.
StringREM-3G-PLMN-LIST
Comma-separated list of strings. Each item is aUMTS Band to measure.
StringREM-3G-BAND-LIST
Enables or disables Radio EnvironmentMeasurement during the FAP start up.
BooleanFC-REM-3G-SCAN-ON-BOOT
Enable Periodic Radio Environment Measurementon all enabled RAT.
BooleanFC-REM-3G-SCAN-PERIODICALLY
An absolute time reference in UTC to determinewhen the CPE will initiate the periodic REM.
DateTimeFC-REM-3G-PERIODIC-TIME
When ScanPeriodically is true, this value indicatesthe interval in seconds which REM is performedwhile the FAP service is enabled.
IntegerFC-REM-3G-PERIODIC-INTERVAL
Cisco RAN Management System Administration Guide, Release 4.x40 OL-32398-01
Baseline Configurationubi-config-X.Y.Z Custom Properties
-
DescriptionPropertyType
Property Name
Comma-separated list (maximum length 64) ofstrings. Each entry is a UARFCN in the DLdirection to measure.
StringREM-3G-ARFCN-LIST
Comma-separated list (maximum length 32) ofstrings.
StringREM-2G-PLMN-LIST
Enables or disables Radio EnvironmentMeasurement during the FAP start up.
BooleanFC-REM-2G-SCAN-ON-BOOT
Enable Periodic Radio Environment Measurementon all enabled RAT.
BooleanFC-REM-2G-SCAN-PERIODICALLY
An absolute time reference in UTC to determinewhen the CPE will initiate the periodic REM.
DateTimeFC-REM-2G-PERIODIC-TIME
When ScanPeriodically is true, this value indicatesthe interval in seconds which REM is performedwhile the FAP service is enabled.
IntegerFC-REM-2G-PERIODIC-INTERVAL
Comma-separated list of strings. Each item is aUMTS Band to measure.
StringREM-2G-BAND-LIST
Comma-separated list (maximum length 64) ofstrings. Each entry is a UARFCN in the DLdirection to measure.
StringREM-2G-ARFCN-LIST
This custom property indicates the IPsec server hostIP address and is the OAM interface of the SecurityGateway (SeGW).
StringFC-IPSEC-SERVER-HOST
First FAP-GW the FAP attempts to establishconnection with. Either hostname or IPaddress.
StringHNB-GW-SERVER
Port number of FAP-GW used for initial Iuh SCTPcontact.
IntegerHNB-GW-PORT
PLMN ID consists ofMobile Country Code (MCC)and Mobile Network Code (MNC)3GPP-TS.23.003, 3GPP-TS.24.008.
StringCELL-CONFIG-PLMNID
Service Area Code (SAC) 3GPP-TS.23.003. Theconcatenation of PLMN ID (MCC+MNC), LAC,and SAC uniquely identifies the Service Area ID(SAI).
IntegerFC-SAC-ID
Comma-separated list (maximum length 256) ofstrings.
StringCELL-CONFIG-LAC-RAC-CL
T3212 timeout value specified in seconds.3GPP-TS.24.008
IntegerCELL-CONFIG-T3212
Periodic Routing Area Update time interval (inminutes).
IntegerCELL-CONFIG-RAU-TIMER
Cisco RAN Management System Administration Guide, Release 4.x OL-32398-01 41
Baseline Configurationubi-config-X.Y.Z Custom Properties
-
DescriptionPropertyType
Property Name
Cell Identity. 3GPP-TS.25.331 Section 10.3.2.2IntegerCELL-CONFIG-RAN-CELL-ID
Comma-separated list (maximum length 64)(minimum 1 items) of strings.
StringCELL-CONFIG-RF-UARFCNDL
Comma-separated list (maximum length 32)(minimum 1 items) of strings.
StringCELL-CONFIG-RF-PSC
Enables or disables this entry.BooleanFC-SC-INTER-RAT-i-ENABLE
Indicates whether this instance of the neighbor shallbe included or excluded in the FAP's NLconfiguration.
BooleanFC-SC-INTER-RAT-i-MUST-INCLUDE
PLMN ID consists ofMobile Country Code (MCC)and Mobile Network Code (MNC)3GPP-TS.23.003, 3GPP-TS.24.008.
StringFC-SC-INTER-RAT-i-PLMNID
Location Area Code (LAC). The concatenation ofPLMN ID (MCC+MNC) and LAC uniquelyidentifies the Location Area ID (LAI).
IntegerFC-SC-INTER-RAT-i-LAC
Routing Area Code (RAC). The concatenation ofPLMN ID (MCC+MNC), LAC, and RAC uniquelyidentifies the Routing Area ID (RAI).
IntegerFC-SC-INTER-RAT-i-RAC
BSIC of the cell per 3GPP-TS.23.003 [8],consisting of: Bit 7:6 - not used ("00") Bit 5:3 -NCC (PLMNColor Code) Bit 2:0 - BCC (BS colorcode)
IntegerFC-SC-INTER-RAT-i-BSIC
Cell ID of the cell per 3GPP-TS.23.003IntegerFC-SC-INTER-RAT-i-CI
Indicates how to interpret the BCCH ARFCN.Enumeration of: - "GSM850" - "GSM900" - "DCS1800" - "PCS 1900"
EnumerationFC-SC-INTER-RAT-i-BAND
ARFCN of this cell.IntegerFC-SC-INTER-RAT-i-BCCH-ARFCN
Max permitted UE Tx power: -50-33 (dBm) asbroadcast in SIB 3 3GPP-TS.25.331 10.3.6.39
IntegerSC-INTER-RAT-i-MAX-TX-POWER
Enables or disables this entry.BooleanFC-SC-INTER-FREQ-i-ENABLE
Indicates whether this instance of the neighbor shallbe included or excluded in the FAP's NLconfiguration.
BooleanFC-SC-INTER-FREQ-i-MUST-INCLUDE
PLMN ID consists ofMobile Country Code (MCC)and Mobile Network Code (MNC)3GPP-TS.23.003, 3GPP-TS.24.008.
StringFC-SC-INTER-FREQ-i-PLMNID
RNC-ID of an intra-freq neighbor cell. It uniquelyidentifies an RNC within a PLMN.
IntegerFC-SC-INTER-FREQ-i-RNCID
Cisco RAN Management System Administration Guide, Release 4.x42 OL-32398-01
Baseline Configurationubi-config-X.Y.Z Custom Properties
-
DescriptionPropertyType
Property Name
C-ID of the intra-freq neighbour cell3GPP-TS.25.401
IntegerFC-SC-INTER-FREQ-i-CID
Location Area Code (LAC). The concatenation ofPLMN ID (MCC+MNC) and LAC uniquelyidentifies the Location Area ID (LAI).
IntegerFC-SC-INTER-FREQ-i-LAC
Routing Area Code (RAC). The concatenation ofPLMN ID (MCC+MNC), LAC, and RAC uniquelyidentifies the Routing Area ID (RAI)
IntegerFC-SC-INTER-FREQ-i-RAC
UTRAN Registration Area (URA)3GPP-TS.23.401. Indicates to the UE which URAit shall use in case of overlapping URAs.
IntegerSC-INTER-FREQ-i-URA
TheULUTRAAbsolute Radio Frequency ChannelNumber (UARFCN) in an FDD mode cell.3GPPTS.25.433
IntegerSC-INTER-FREQ-i-UARFCNUL
Comma-separated list (maximum length 64)(minimum 1 items) of strings.
IntegerFC-SC-INTER-FREQ-i-UARFCDL
Primary CPICH scrambling code.IntegerFC-SC-INTER-FREQ-i-SCRAMBLING-CODE
Primary CPICH Tx power in dBm. Actual valuesof the power are -10.0 dBm to 50.0 dBm in stepsof 0.1 dB. The value of PCPICHTxPower dividedby 10 yields the actual value of the power.
IntegerFC-SC-INTER-FREQ-i-PCPICH-TX-POWER
Indicates whether the cell is using transmit diversityBooleanSC-INTER-FREQ-i-TX-DIVERSITY-INDICATOR
Max permitted UE Tx power: -50-33 (dBm) asbroadcast in SIB 3 3GPP-TS.25.331 10.3.6.39
IntegerSC-INTER-FREQ-i-MAX-UL-TX-POWER
Enables or disables this entry.BooleanFEMTO-NEIGHBORING-FILTERING-ENABLE
Enables or disables this entry.BooleanSTATIC-NEIGHBORING-FILTERING-ENABLE
The FQDN or IP address of the server where thePost Event Diagnostics tarballs should be uploadedto. An empty string will indicate that uploading (asopposed to collection and packaging) is disabled.
StringPOST-EVENT-UPLOAD-URL
Route definition 0StringZAP-ROUTE-IP-ADDRESS
IP address or FQDN of timing serverStringIP-TIMING-SERVER-IP
Cisco RAN Management System Administration Guide, Release 4.x OL-32398-01 43
Baseline Configurationubi-config-X.Y.Z Custom Properties
-
Cisco RAN Management System Administration Guide, Release 4.x44 OL-32398-01
Baseline Configurationubi-config-X.Y.Z Custom Properties
-
C H A P T E R 5Device Manager
You access the device manager by clicking the Device Manager tab in the DCC UI. The device managerprovides a consolidated interface to perform various tasks on an individual Customer Premises Equipment(CPE). Specifically it allows you to perform the functions:
• Device Provisioning, page 45
• View Information about a Device, page 59
• Log Uploads and Triggers , page 61
• Device Operations, page 63
• View and Update Live Data, page 67
• Device Manager Status Messages, page 70
Device ProvisioningYou can register and activate a new device at a time using the Register screen in the DCC UI. Alternatively,you can activate an already registered device using update button in the DCC UI.
Preparing to Register a DeviceUse this task to choose a 3G device to register.
Before You Begin
Before registering a device you should verify the following:
• Latest version of RMS is installed.
• Appropriate network connectivity is established between the RDU and the DPE, and between the DPEand the FAPs.
• The PMGDB is up and running.
• You can create groups from the DCC-UI Groups and IDs tab.
• The register button is activated when you enter in an identifier for a device in the Device Manager.
Cisco RAN Management System Administration Guide, Release 4.x OL-32398-01 45
-
After the post-installation steps are complete, do not use default Groups and Pools. Add the new Groupsand Pools.
Note
Before registering an Enterprise device, you must create all of the following:
• Enterprise group—the Enterprise group must be created before the Site group.
• Site group
• Area group
• Femto gateway group
• Cell pool
• SAI pool
Before registering a Residential device, you must create all of the following:
• Area group
• Femto gateway group
• Cell pool
• SAI pool
Procedure
Step 1 Log in to the DCC UI with valid credentials.The Device Command and Control screen is displayed.
Step 2 Select the Device Manager tab.Step 3 Enter a new device ID in the Select Device text box.
The device ID is a combination of themanufacturer OrganizationallyUnique Identifier (OUI) number (001B67),and the 15 digit serial number which is the International Mobile Equipment Identity (IMEI) number of theFAP (for example, 357539019690151).As you type the first few characters of the device ID, the Device Manager does an automatic lookup to findall device IDs beginning with that string instead of having to scroll down the entire list to find the device IDthat you are looking for.
Also, as you start typing a new device ID, a tooltip is displayed indicating that the device is not registeredand the Register button is enabled to allow for registering the device.
Step 4 Click Register.The Device Registration screen is displayed with the Device ID populated in the Device ID text box. ByDefault, the registration screen for Enterprise deployment is displayed. For Residential FAP registration,check the Residential Deployment check box.
The content of this dialog box is based on the dynamic screen configuration files:sdm-register-enterprise-screen-setup.xml andsdm-register-residential-screen-setup.xml. Refer to Configuring DCC DialogBoxes, on page 23 for information on customizing these.
Note
Cisco RAN Management System Administration Guide, Release 4.x46 OL-32398-01
Device ManagerPreparing to Register a Device
-
Registering a Device in Enterprise ModeUse this task to register a 3G device in Enterprise mode after the Device Registration screen is displayed.
Before You Begin
You should have completed