RMS Release 4.1 Release Notes · The RMS provides end-to-end operations to transmit high quality voice ... PMG DB Database which can store geographical location ... Table 4 Checksum

Release Notes for Cisco RAN Management System for Release 4.1.0

June 30, 2015 HF6

Contents • Introduction, page 1

• Abbreviations and Definitions, page 3

• System Requirements, page 4

• Key Notes, page 6

• New and Changed Information, page 9

• Deployment, page 13

• Troubleshooting, page 14

• Caveats, page 19

• Related Documentation, page 22

IntroductionThe Cisco RAN Management System (RMS) provides end-to-end capabilities to support the management, monitoring, and configuration of Universal Small Cell Access Point (USC AP) devices. The RMS provides end-to-end operations to transmit high quality voice and data from the Service Provider mobility users through the Service Providers mobility core.

These release notes are for the 4.1.0-1N release including Hotfix01, Hotfix02, Hotfix04, Hotfix05 and Hotfix06. Following are some of the key highlights of the RMS components:

Cisco Systems, Inc.www.cisco.com

Introduction

Table 1 RMS Release 4.1 Highlights

Key Component Description

Broadband Access Center (BAC) • Distributed TR-069 ACS

• AP inventory in RDU

• Femto activation logic on DPE

• Admin UI for Operational Tools

• TR-069 and Download services

Cisco Prime Access Registrar (PAR) Provides RADIUS service used by ASR5K to authenticate and authorize AP access during luH HNB Register. PAR is integrated with the DPE. The DPE performs AP authentication by verifying source IP address to AP identity mapping via DHCP. The DPE also delivers the access mode indication and whitelist via RADIUS to the ASR5K based on data in provisioned in BAC.

Cisco Prime Network Registrar (PNR) Provides DHCP service for allocating IPSec addresses to APs via SeGW on ASR5K. PNR is also integrated with BAC DPE which performs queries of IP address lease data.

Device Command and Control User Interface (DCC UI)

• Web UI and CLI tools

• Register the device, activate, and check the status

• Operational Tools

• Group Management, Upgrade Monitor, and Device Data Export

Provisioning and Management Gateway (PMG)

• Integration API with OSS/BSS

• Subscriber portal (registration and whitelist updates)

• Care interfaces (live status)

• XML/HTTP requests and notification

• Key Performance Indicators in CSV Performance Management files

PMG DB Database which can store geographical location data.

Log Upload Server (LUS) • High scale HTTP upload

• AP system logs and PM file uploads

• Bundling of files for distribution to SP OSS

• Purging of old files

• Detailed KPIs in CSV PM files

Universal Small Cell Access Point (USC AP)

USC AP are low-power wireless access points that operate in licensed spectrum to connectstandard mobile devices to a mobile operator’s network using residential DSL or cable broadband connections.

Note USC AP software is not an RMS 4.X.0 component. Hence, the operator needs to download the AP FCS builds separately.

2Release Notes for Cisco RAN Management System for Release 4.1.0

June 30, 2015 HF6

Abbreviations and Definitions

As part of Cisco RMS, the new features are added in several release cycles. See “New and Changed Information” section on page 9 for more information.

Abbreviations and DefinitionsAll abbreviations and definitions used in the document are provided here:

Table 2 Abbreviations and Definitions

Abbreviation Description

BAC Broadband Access Center: A Cisco TR-069 management product that includes RDU and DPE.

EID Equipment Identifier

PAR Cisco Prime Access Registrar

PNR Cisco Prime Network Registrar

CPE Customer Premises Equipment

DCC UI Device Command and Control User Interface

DPE Distributed Provisioning Engine. A distributed server of the BAC product.

FRM Femto RAN Manager

HNB Home Node B

LUS Log Upload Server

PMG Provisioning and Management Gateway

RDU Regional Distribution Unit, a part of the BAC that interfaces with the OSS north bound and DPE south bound and is the master data store.

RMS RAN Management System

SMB Small Mode Business

SSL Secure Socket Layer, an authentication and encryption protocol.

TLS Transport Layer Security

TR-069 Technical Report 069 is a Broadband Forum (standard organization formerly known as the DSL forum) technical specification entitled CPE WAN Management Protocol (CWMP).

USC AP Universal Small Cell Access Point

Whitelist Access control list which specifies which cell phones can register with the AP.

QSS Cisco Quantum SON Suite

SON Self Optimizing Network


June 30, 2015 HF6

System Requirements

System Requirements

Component VersionsRMS Release 4.1 requires the following component versions:

Note The PMG DB is an optional component. Contact Cisco services to deploy the PMG DB.

Installation ImageThe checksum value of the OVA files are as follows:

Table 3 RMS 4.1 Component Versions

Component Version

PMG DB RMS-PMGDB-4.1.0-1N.tar.gz

BAC BAC_3.8.1.1-6_i386.rpm

CPAR CPAR_6.0.1-5_i386.rpm

CPNR CPNR_8.1.3-2_i386.rpm

BACTools CSCOrms-bacctools-3.8.1.0-32.el6_1.noarch.rpm

BAC Config CSCOrms-baseline-config-ga-4.1.0-113.noarch.rpm

DCC UI CSCOrms-dcc-ui-ga-4.1.0-174.noarch.rpm

OPS Tools CSCOrms-ops-tools-ga-4.1.0-168.noarch.rpm

OVA Install CSCOrms-ova-install-ga-4.1.0-124.noarch.rpm

Platform Base CSCOrms-platform-base-2.0.0-10.el6_1.noarch.rpm

PMG CSCOrms-pmg-ga-4.1.0-159.noarch.rpm

Upload Server CSCOrms-upload-server-9.2.0-40.noarch.rpm

Watchdog Package rubygem-god-0.11.0-45.x86_64.rpm

Overall RMS Version 4.1.0-1N

Table 4 Checksum of OVA Files

Filename Checksum Value

RMS-4.1.0-1N-HOTFIX06.tar.gz c8f620a1d0ebd2ce92575f8c38d00823

RMS-4.1.0-1N-Leap_Second.tar.gz 741164cb168226f7ab63ca18867007f2

PAR-UPGRADE-6.1.2.3.tar.gz a583fc20a51e7aa8cd2a198059607172

RMS-4.1.0-1N-HOTFIX05.tar.gz e3084aa39520997d4e779c1259fbae2f

RMS-4.1.0-1N-HOTFIX04.tar.gz 0ca56e3ec6a0323e430434e8ea9e7030

RMS-4.1.0-1N-HOTFIX02.tar.gz 290f207c880f151a5ffdd2403e86047e


June 30, 2015 HF6

System Requirements

Post execution of the Release 4.1 hotfixes, the modified RMS components are as follows:

Software CompatibilityRMS 4.1.0 is compatible with:

• AP software versions:

• VMware Vsphere versions 5.1.0 and 5.5

• ASR 5000 (FemtoGW and SecurityGW versions) 16.0 and 17.0

RMS-4.1.0-1N-HOTFIX01.tar.gz 137d3f54bbda8116fa23bc4de212f77b

All-in-One:RMS-All-In-One-Solution-4.1.0-1N.tar.gz ec6269db783474f818eee44fbfc56f16

Distributed:RMS-Distributed-Solution-4.1.0-1N.tar.gz 65139ea5b99c2759419449f199b232de

Upgrade:RMS-UPGRADE-4.1.0-1N.tar.gz 79c0d04c28d21ef095a11caa75a19e61

PMG DB:RMS-PMGDB-4.1.0-1N.tar.gz c4c56fa39e1c44dc510a521f2b50d3a9

Table 4 Checksum of OVA Files (continued)

Filename Checksum Value

Table 5 Modified RMS Components

RMS Release Modified RMS Components

Release 4.1 Hotfix06 • BAC_3.8.1.2_LinuxK9_HOTFIX_CSCUU71789.gtar.gz

Release 4.1 Hotfix05 • CSCOrms-baseline-config-ga-4.1.0-170.noarch.rpm

• CSCOrms-pmg-ga-4.1.0-174.noarch.rpm

• CPAR_6.1.2.3-1_i386.rpm

Release 4.1 Hotfix04 • CSCOrms-baseline-config-ga-4.1.0-159.noarch.rpm

Release 4.1 Hotfix01 • CSCOrms-ops-tools-ga-4.1.0-174.noarch.rpm

• CSCOrms-baseline-config-ga-4.1.0-124.noarch.rpm

• CSCOrms-ova-install-ga-4.1.0-131.noarch.rpm

• CSCOrms-dcc-ui-ga-4.1.0-183.noarch.rpm

• CSCOrms-pmg-ga-4.1.0-166.noarch.rpm

AP Type AP Software Version

Residential BV 3.4.4.X, BV3.5.11.9 (and above), 3.5.12.X

Enterprise BV 3.5.9.X, BV 3.5.10.X, BV3.5.11.9 (and above), 3.5.12.X


June 30, 2015 HF6

Key Notes

Key Notes• Before installing of any of the available Hotfixes, refer to the README file provided in the

corresponding hotfix tar file. The README file provides important information on how to install the hotfix.

• RMS-4.1.0-1N-HOTFIX06.tar.gz can be applied only after installing Hotfix02 or Hotfix05. If you apply Hotfix06 after Hotfix02, leap second patch and PAR 6.1.2.3 can be applied after the upgrade to Hotfix06.

• The PAR 6.1.2.3 upgrade and Leap Second fix need to be applied after RMS-4.1.0-1N-HOTFIX05.tar.gz is installed.

• Hotfix05 has 2 README files: one for Backup and Upgrade and another for Rollback. The backup procedure is optional, and is meant to be executed if there is not sufficient disk space on the hosts to clone the RMS nodes. Rollback can be executed only if a backup is taken before the upgrade is performed.

• Hotfix05 can be installed only after installing either Hotfix02 or Hotfix04. Installation of Hotfix05 can be performed after Hotfix01 on the serving node and upload nodes only.

• Hotfix04 can be installed only after installing Hotfix02. Installation of Hotfix04 can be performed after Hotfix01 on the serving node and upload nodes only.

• If “INSEE SAC Management” is required together with “Alarm Profile,” make sure that the script config2.sh is run before installing Hotfix04 or Hotfix05. (Refer to the RMS Installation Guide for the procedure to run this script.)

• If reserved mode needs to be enabled by default, make sure that the script config1.sh is run before installing Hotfix04 or Hotfix05. (Refer to the RMS Installation guide for the procedure to run this script.)

Note After installing Hotfix04 or Hotfix05, the scripts config1.sh or config2.sh should not be run.

• Please check the PAR license before installing the RMS4.1 Hotfix. Refer to the “Deployment Troubleshooting” section in the RMS Installation Guide for information on how to check and replace the PAR license.

• Customized RF profiles are not updated with a value for newly introduced parameters of the RFProfile in Hotfix 05 and Hotfix04. The value for these parameters should be added manually after upgrading to Hotfix04 or Hotfix05. Refer to the “Iuh_Parameter_Guide3_5MR” for information on updating these parameters: http://www.cisco.com/c/dam/en/us/td/docs/wireless/asr_5000/smallcell/USC_Software_Docs/R35_MR/References/USC-44-54-006_Iuh_Parameter_Guide3_5MR.pdf

• During the RMS Release 4.1 installation, the default PAR license may have expired. Request a new license from the customer support team and include the property “prop:Car_License_Base=<License>” in the descriptor file. The value for “License” must be obtained from the customer support team.

• To enable GDDT to run periodically, a cron job should be created.

• The periodicity of the GDDT cron should not be less than six hours.

• All the Location Verification related properties and modification of the DN prefix should be configured from the BAC. Refer to Adding Various LV Related Properties from BAC UI in the Cisco RAN Management System Administration Guide.

• RMS alarms are not integrated into Prime Central.


June 30, 2015 HF6

http://www.cisco.com/c/dam/en/us/td/docs/wireless/asr_5000/smallcell/USC_Software_Docs/R35_MR/References/USC-44-54-006_Iuh_Parameter_Guide3_5MR.pdf

Key Notes

• The script getDeviceData.cron.daily can be used for device data exports for the entire population, and can be configured for daily iterations. Download this script from Cisco.com at the RMS 4.1 release URL. Follow these steps to place the getDeviceData.cron.daily script on the Central node:

1. ssh to the Central node as root user

2. Secure copy the file getDeviceData.cron.daily to /rms/app/ops-tools/public/shell-scripts

3. Use chmod command to provide permissions to the file:chmod 755 /rms/app/ops-tools/public/shell-scripts/getDeviceData.cron.daily

The getDeviceData.cron.daily can be configured as a cron. Refer to the “Configuring Crons” section in the RMS Administration Guide for more information.

Note It is recommended to configure getDeviceData.cron.daily for the daily device data reports and not to use getDeviceData.cron for daily reports.

Use ssh to connect to the Central node as root user and execute the following sed commands. This is required for the crons to execute.

$ sed -i 's/bulkStatusReport.sh -outdir/bulkStatusReport.sh -force -outdir/g' /rms/app/ops-tools/public/shell-scripts/bulkStatusReport.cron

$ sed -i 's/getDeviceData.sh -outdir/getDeviceData.sh -force -outdir/g' /rms/app/ops-tools/public/shell-scripts/getDeviceData.cron

$ sed -i 's/getDeviceData.sh -outdir/getDeviceData.sh -force -outdir/g' /rms/app/ops-tools/public/shell-scripts/getDeviceData.cron.daily

$ sed -i 's/getDeviceData.sh -outdir/getDeviceData.sh -force -outdir/g' /rms/app/ops-tools/public/shell-scripts/gpsExportData.sh

• With firewall disabled on the serving node, the CAR service goes down when the application MAP scan is done on TCP port 8443; and an NTP vulnerability is identified as ntp monlist command enabled.

• RMS Release 4.1 is aligned with the PMG NB API published with RMS Release 4.1 Hotfix05.

• The RMS supports RF Profile Version 2.6 for AP software version 3.5 MR only. To support RF Profile Version 2.6, remove two properties from all RF Profile groups and then update the specified properties for each RF Profile group. The procedure to do this is provided here:

Step 1 Go to “/rms/app/rms/conf”.

Step 2 Open the file “bgmt-add-group-screen-setup-RFProfile.xml”.

Step 3 Remove the block containing the following properties. The block begins with <ScreenElement> and ends with </ScreenElement>.

– FC-TTT-EVENT-6B

– FC-POWER-DECREASE-TTT

Step 4 Go to the BAC UI and follow these instructions to delete these two custom properties in each RF profile:

a. Log in to the BACAdmin UI.

b. Click on the Groups tab.

c. In the Search Type drop-down list box, select Group, select the Group Type as RFProfile and click Search.

d. Click each of the RF Profiles and delete these two custom properties:

– FC-TTT-EVENT-6B


June 30, 2015 HF6

Key Notes

– FC-POWER-DECREASE-TTT

Step 5 From the Groups and IDs tab in the DCC UI, select Groups from the left navigation pane.

Step 6 Select the RFProfile tab.

Step 7 For each RFProfile group listed, select the group and click Update.

Step 8 Update each of the following parameters as indicated in the table:

Table 6 RF Profile Required Custom Property Values for V2.6

Parameter NameCustom Property Displayed in DCCUI Re

side

ntia

l Clo

sed

Mod

e 10

dB

m

Resi

dent

ial C

lose

dM

ode

13 d

Bm

Hot

Spot

/Sta

ndal

one

Ope

n M

ode

20 d

Bm

Hot

Spot

/Sta

ndal

one

Ope

n M

ode

24 d

Bm

Mul

ticel

l/Gri

d O

pen

Mod

e 10

dB

m

Mul

ticel

l/Gri

d O

pen

Mod

e 20

dB

m

Mul

ticel

l/Gri

d O

pen

Mod

e 24

dB

m

MaxULTxPower MAX-UL-TX-POWER 5..5 5..5 10..10 10..10 10..10 10..10 10..10

X_UBIQUISYS_COM_SRBOnEDCHEnabled

FC-SRB-ON-EDCH- ENABLED 1 1 0 0 0 0 0

ThresholdUsedFrequencyEvent2d CELL-CONFIG-INTER-FREQ- THRESHOLD-EVENT-2D

-11 -11 -11 -11 -11 -11 -11

ThresholdUsedFrequencyEvent2f CELL-CONFIG-INTER-FREQ- THRESHOLD-EVENT-2F

-11 -11 -11 -11 -11 -11 -11

Version DEPLOYMENT-PROFILE- VERSION

V2.6 V2.6 V2.6 V2.6 V2.6 V2.6 V2.6

DefaultMaxTargetRTWP FC-DEFAULT-MAX-TARGET-RTWP

580 580 580 580 350 350 350

RTWPAveragingWindow ALPHA-IN-RTWP-AVERAGE-WINDOW

3 3 0 0 0 0 0

SSearchRAT CELL-SELECTION-SSEARCHRAT

4 4 4 4 4 4 4

InterFreqMeas1.ThresholdUsedFrequencyEvent2d

CELL-CONFIG-INTER-FREQ-1-THRESHOLD-EVENT-2D

-95 -95 -95 -95 -90 -90 -90

InterFreqMeas1.ThresholdUsedFrequencyEvent2f

CELL-CONFIG-INTER-FREQ-1-THRESHOLD-EVENT-2F

-90 -90 -90 -90 -85 -85 -85

LACRACURASelfConfigEnable ENABLE-LAC-RAC-URA-SELF-CONFIG

1 1 1 1 0 0 0


June 30, 2015 HF6

New and Changed Information

New and Changed Information RMS 4.1.0 adds new features and enhancements to the earlier system releases. Following is a list of the new features of the RMS:

Table 7 RMS 4.1.0 New and Changed Information

Feature Description

Enterprise, Site and Grid Support

The Enterprise Grid allows multiple HNBs to work in a coordinated fashion.The members of a 3G AP Enterprise Grid are predefined and configured in the RMS. RMS enables enterprise AP functionality with the following:

• Configures Enterprise, Site and Grid ID

• Passes the Grid ID to the HNB-GW for Authentication

• Defines AP role: Active Entry AP, Inner AP, or Idle Entry AP.

• Defines the AP purpose (coverage or capacity).

HA Feature Support High end availability provides a redundant setup when the active Central Node or PMGDB fail at one RMS site. It also provides the flexibility of recovering from a disaster when all nodes at one RMS site go down and the connected APs need to be gracefully handed over to another RMS site.

High end availability also protects the data of the connected devices in an external storage location which can be accessed by redundant hosts during a disaster recovery procedure. HA also ensures minimal downtime during any unforeseen circumstances with regard to connectivity of APs to the RMS.

Location Verification Support

Location verification is a part of the provisioning flow in which before unlocking the HNB for Radio On, its location is verified to ensure that the HNB is still in the same location where it was registered. In RMS 4.1, there are seven types of LV (Location Verification) supported:

• GPS - Global Positioning System

• EDN – Expected Detected Neighbors

• DNL – Detected Neighbor Location

• DNM – Detected Neighbor MCC/MNC

• ISM – IP address Subnet Match

• CIG – Chained Intra Grid

• DNB – Detected Neighbor Benchmark

All the above mentioned LV methods are configurable from the RMS. By default, with RMS installation DNM and DNB LV methods are enabled. To enable other LV methods, the properties need to be set manually from the BAC UI on either the group or device level as required.


June 30, 2015 HF6


Alarm Handler The Alarm Handler handles two alarms raised by the RMS:

• AP reachability alarm – When AP is not reachable, RMS raises this alarm.

• AP Location Verification alarm – When APs Location Verification fails, RMS raises the alarm.

The Configuration needs to be enabled. The RMS issues a Connection Request (CR) every 10 minutes (by default) as configured in the PMG server Properties file. The Alarm log in the path /rms/log/AlarmHandler/AlarmHandler.console.log gives details on the traps being sent for Unreachable APs and Location Failed APs in case of both raising and clearing alarms. All the Traps are sent to the Prime Central/SNMP Manager as configured in the PMGServer Properties file.

Note The Alarm Handler is applicable for AP populations up to 5000.

INSEE Management INSEE code is used to search an AP based on INSEE code. It is also used in SAC management in the absence of macro neighbors.

Enhanced SAC management

For regulatory purposes, the implementation of Emergency Call routing to the closest Emergency Center is supported. The call routing is based on the assigned SAC to the cell (macro or small cells) that is used to determine the emergency dispatch center. Hence, a specific SAC allocation mechanism is required.

If there is macro coverage, then the best macro cell indications sniffed by the FAP are used and the same SAC as the one used by the macro is assigned to the small cells. Otherwise, INSEE code of the FAP as provided by the IT system during provisioning is used. If there is no macro coverage and no INSEE code is declared, a unique SAC is computed by the PMG.

Note Implementation of this feature requires a special installation.

SAN Configuration Support

RMS supports external SAN storage.

Ops Tool Enhancements

The GPS Data Export Tool enables the operator to export the FAP’s GPS data in bulk. The export can include data for all FAPs or can be restricted to:

• a specific set of FAPs

• all FAPs in a given area/s or

• all FAPs served by a given Gateway/s.

The tool reports the distances between expected and authorized GPS coordinates for devices which successfully passed GPS location verification. You may use this data in order to ascertain the impact of reducing tolerance radius and thus narrowing precision of the GPS location match.

The Bulk FAP Status report Tool enables retrieval of data from the RDU DB and from live FAPs into a CSV file and produces the bulk status reports.

Secondary Id Support Secondary ID is an optional Parameter along with Subscriber ID which is a part of AP registration on the DCC UI. These two are optional parameters in which Secondary ID is unique and Subscriber ID is common for a group of APs. Using either Subscriber ID or Secondary ID, you can perform all the AP operations.

Table 7 RMS 4.1.0 New and Changed Information (continued)

Feature Description


June 30, 2015 HF6


Polygon database for geo-positioning (PMG DB)

PMG DB provides a geospatial lookup service for PMG. It takes a location, defined by latitude and longitude, and returns the name of an area. PMG uses this group for automatic assignments.

PMG DB operates on Oracle and is shipped as installation scripts, schema files, and stored procedures. The Oracle installation, Oracle license, and Map info file are not included in the RMS image.

PMG event subscription model

RMS provides the capability to send notifications to registered subscribers. The operator has an option to configure a set of target address for any notification. RMS can send different types of notification to different targets. The operator can configure the list of parameters which will be part of notification.

Static neighbor configuration at DCC UI

In the RMS DCC UI, the operator can configure the static neighbor list of the AP. DCC UI supports configuration of both Inter-RAT and Inter-Frequency lists on the FAP.

Device replacement message support

It might be possible that an already commissioned device on field needs replacement because of one of the following reasons:

• Misbehaving device which cannot be solved using software/firmware upgrade

• Hardware malfunctioning

The RMS exposes an OSS NBI API which you can use to replace a device with minimal information and even option DCC UI. RMS maintains the static configuration of the device.

Reserved AP Mode Support

RMS supports AP configuration in reserved mode.

Generic CoS/RF profile selection

Configuration template is selected based on the software version.

The RMS can discover the capabilities of each AP including max TX power, and make it available in the configuration template.

Generic SP OSS /QSS Interface and Operational Capabilities

RMS supports integration with service providers OSS/QSS systems.

Refer to the RMS API guide for details of available interfaces.

DN Prefix RMS supports configuration of DN Prefix allowing APs to populate the DN Prefix in the alarms and in the 3GPP xml files generated by the USC AP.

RMS Integration with Cisco Prime Suite

RMS 4.1 supports integration with Cisco Prime Performance Manager (PPM) for performance management and with Cisco Prime Central for Access Point fault management. Refer to the RAN Management System SNMP/MIB Guide for more details.

Closed mode support for residential USC APs

For 3G APs in closed access mode, the list of approved subscribers (white list) is obtained from the PAR and used by the HNB GW to determine if a given UE should be allowed on a 3G AP or not. For 3G APs in open access mode, the 3G HNB can accept any authenticated UE, in addition to the subscribers on a whitelist.

Note Closed mode is supported only for residential APs.


Feature Description


June 30, 2015 HF6


15 min log upload support on LUS

RMS supports configuration for periodicity of uploading PM files with a minimum interval of 15 minutes for enterprise APs. The minimum interval for residential APs is 30 minutes.

Performance/Capacity and Scaling

RMS supports up to 150K devices in a distributed deployment.

RMS supports up to 50K devices in an all-in-one deployment.

Anti Tamper Anti-tamper allows the operator to clear the tampering status from the device. This feature is supported on the RMS, but not for the end-to-end system.

The device can only report its tampered status as true and cannot clear it on its own. This functionality allows the RMS to clear the tampering status from the device and set the status back to false.

To use this feature:

• Property FC-TAMPERED-ENABLED must be set to true. • AP must have reported EnclosureTamperingDetected = true.

• AP service status is set as “Pre-requisites not met: AP tampered”.

Release 4.1 Hotfix01 In addition to resolution of defects, the RMS Release 4.1 Hotfix1 contains the following functionality:

• DNL fix (230K entries) from BAC 3.8.1.2

• RF profile version 2.2 compatibility

• Support for global override parameter for controlling common pegging interval for all the PM counters on a device. As part of this feature there are two new parameters added in the Area group on the DCC UI - one parameter each for residential and enterprise APs.

• Support for DN prefix on APs running software release 3.4.x, so that they include DN prefix in alarms and PM files similar to APs running release 3.5.x.

Release 4.1 Hotfix02 RMS Release 4.1 Hotfix2 contains a fix to handle the scenario where the macro detected is not present in the Detected Neighbor Location (DNL) file. In this case the DNL returns “Unknown.”

Release 4.1 Hotfix03 RMS Release 4.1 Hotfix3 contains the following functionality:

• Location Verification Enhancement to support no macro

• Support for SecGW Redundancy and Edge node router list

• Support for AP software Version 3.5 MR for both residential and enterprise

Release 4.1 Hotfix04 RMS Release 4.1 Hotfix4 contains the following functionality:

• All features from Release 4.1 Hotfix3

• Support for Blacklisting IMSI

• Resolves NTP and GLIBC vulnerability

• RF Profile Version 2.4 compatibility with AP software 3.5 MR


Feature Description


June 30, 2015 HF6

Deployment

Deployment

InstallationThe RMS provides an integrated installation process, which installs a pre-packaged set of software, such that you do not have to install each separate component.

Upgrade Paths

Upgrade support is provided for:

• RMS 3.0 FCS to RMS 4.1 FCS

• RMS 3.0.1 MR to RMS 4.1 FCS

• RMS 4.0 FCS to RMS 4.1 FCS

• RMS 4.1.0-1N (FCS) to RMS-4.1.0-1N-HOTFIX01.tar.gz

• RMS-4.1.0-1N-HOTFIX01.tar.gz to RMS-4.1.0-1N-HOTFIX02.tar.gz




• RMS-4.1.0-1N-HOTFIX05.tar.gz to PAR-UPGRADE-6.1.2.3.tar.gz

• RMS-4.1.0-1N-HOTFIX05.tar.gz to RMS-4.1.0-1N-Leap_Second.tar.gz

Release 4.1 Hotfix05 RMS Release 4.1 Hotfix05 contains following functionality:

• Support of RF profile Version 2.6 with BV3.5.11.9 and above, and BV3.5.12.X

• Support for Cell ID overwriting via PMG API

• Modification of PC integration script to support PC disaster recovery configuration

• Restrict the PMG log generation for 5 days instead of 30 days

• Optional RMS backup and rollback

• CPAR 6.1.2.3 upgrade

• Leap Second fix

Release 4.1 Hotfix06 RMS Release 4.1 Hotfix06 contains fixes for the following issues:

• CSCuu64883: RMS Sending Grid ID = O for APs registered as residential in RMS

• CSCur75799: PNR is crashing continuously 1minute after each restart with 10K leases


Feature Description


June 30, 2015 HF6

Troubleshooting


• RMS-4.1.0-1N-HOTFIX06.tar.gz to PAR-UPGRADE-6.1.2.3.tar.gz

• RMS-4.1.0-1N-HOTFIX06.tar.gz to RMS-4.1.0-1N-Leap_Second.tar.gz


Supported Hardware• UCS 5108 (B200-M3 blades), UCS 240-M3

Troubleshooting

Workarounds for Known Problems – Post Installation• CSCus46506: GA Scripts & Generic Files Sync Failures Terminate Provisioning Flow, page 14

• CSCuu09695: UpdateMsg can cause Duplicate CID when same ID is Assigned During Update, page 15

• Unable to Log In to Central VM after Reboot, page 15

• CSCuq54139: DCC UI Tool Tip Update for Log Upload Triggers, page 15

• CSCuq36616: Unable to Upgrade the USC 7330 Image using RMS, page 15

• CSCuq47805: DN Prefix Does Not Reflect on Connection Request, page 16

• CSCur39673: SetLiveData of Parameters with an Empty Value Via PMG NBI API Fails, page 16

• CSCur41236: Group Updates for RF Profile not Happening during Release 4.1 Hotfix1, page 16

• CSCut09292: RMS41HF DCCUI is not validating the maximum number of values given for a parameter, page 17

• CSCut20511 RMS4.1_MR: FGW Import Failing with Cause 'ZAP-ROUTE-IP-ADDRESS-ENABLE’, page 18

• CSCut59222: RMS41HF04 Periodic Interval Parameters Should not be Added in Activated CoS3.5.11, page 18

• CSCut26992: AIO Redundancy Login as Root User Takes Time, page 19

CSCus46506: GA Scripts & Generic Files Sync Failures Terminate Provisioning Flow

Cause/Scenario

There is no retry mechanism for file synchronization failures between the RDU and DPE, which can result in provisioning flow failures.

Workaround

Restart the DPE on the serving node using this command:

/etc/init.d/bprAgent restart dpe.

Make sure that no exceptions are displayed in the DPE logs (/rms/data/CSCObac/dpe/logs/dpe.log).


June 30, 2015 HF6

Troubleshooting

CSCuu09695: UpdateMsg can cause Duplicate CID when same ID is Assigned During Update

Workaround

Do not send the same Area (which is already assigned to the device) in an Update message.

Unable to Log In to Central VM after Reboot

Cause/Scenario

Reboot the Central VM and try to log in.

Workaround

Post RMS installation, edit the eth0 routing configuration on the Central node as root user to comment out the default gateway as shown below:

[blrrms-central-22] ~ # cat /etc/sysconfig/network-scripts/ifcfg-eth0DEVICE=eth0BOOTPROTO=noneONBOOT=yesTYPE=EthernetNM_CONTROLLED="no"IPV6INIT=noIPADDR=10.5.1.220NETMASK=255.255.255.0#GATEWAY=10.105.233.11BROADCAST=10.5.1.255

Check that the default gateway entry is present in the eth1 routing configuration:

[blrrms-central-22] ~ # cat /etc/sysconfig/network-scripts/ifcfg-eth1DEVICE=eth1BOOTPROTO=noneONBOOT=yesTYPE=EthernetNM_CONTROLLED="no"IPV6INIT=noIPADDR=10.105.233.92NETMASK=255.255.255.128GATEWAY=10.105.233.11BROADCAST=10.105.233.127

After completing these changes, reboot the Central VM.

CSCuq54139: DCC UI Tool Tip Update for Log Upload Triggers

The tool tip for Log Upload says “LogUploadinterval ranges between 900 to 4294967295.” For Enterprise AP the minimum value is 900, however, for Residential AP, the minimum value for LogUploadinterval is 1800.

CSCuq36616: Unable to Upgrade the USC 7330 Image using RMS

Workaround

1. Modify the /etc/hosts file in the Serving node


June 30, 2015 HF6

Troubleshooting

2. Add the Southbound ID of the DPE and FQDN mapping. For example, if the southbound IP of the serving node is 10.5.2.56 and Acs_Virtual_Fqdn is femtosetup11.testlab.com, add this line into the /etc/hosts file: 10.5.2.56 femtosetup11.testlab.com femtosetup11.testlab.com

Note This workaround is applicable only when the value in the descriptor property Acs_Virtual_Fqdn is an FQDN and not an IP address.

CSCuq47805: DN Prefix Does Not Reflect on Connection Request

Workaround

1. Customize the DN prefix format.

2. Perform an update operation on the AP (Provision --> Update/Log Upload Triggers).

3. Verify using Live Data that the configured DN prefix is reflected.

For more information regarding DN prefix, refer to the “Configuring DN Prefix Format” section in the RAN Management System Administration Guide.

CSCur39673: SetLiveData of Parameters with an Empty Value Via PMG NBI API Fails

Impact

You cannot provision empty values for device parameters from the OSS using the SetLiveData API of the PMG NBI.

WorkAround

You need to provision the same parameters with empty values from the DCC UI using the “Set Live Data” operation.

CSCur41236: Group Updates for RF Profile not Happening during Release 4.1 Hotfix1

Scenario

While applying the Release 4.1 Hotfix1, group updates are not happening for particular RF profile groups if any devices are associated with them.

Impact

Any device which is already associated or which initially gets associated with the RF profile group that is not updated during the Hotfix gets provisioned with an old set of parameters.

WorkAround

You must disassociate all devices from the RF profile groups before applying Hotfix1 and then associate them back to the same groups after applying the Hotfix as described here:

1. Login to the DCC UI.

2. Navigate to the RF profiles groups (Click Groups and IDs > Groups > RFProfile).

3. Export the device and RF profile association information using the export functionality as described here:

a. Click the Export button. The Export Group: RFProfile dialog box is displayed.


June 30, 2015 HF6

Troubleshooting

b. Check the All Groups check box.

c. In the Export Type drop down list box select Related EIDs.

d. Click the Export button.

e. Save the exported CSV file for reference.

4. For each device in the exported CSV file, disassociate the RF Profile group as described here:

a. Search for the device using the Device ID field in the Device Manager screen.

b. In the Provision tab, click on Update.

c. In the Update Device Registration pop-up screen, delete the RF Profile group name in the RF Profile text box and click on Update.

d. Navigate to the Device Dashboard and verify that there are no RF Profile groups shown in the Registration Data block.

e. Repeat these steps for each of the devices in the exported CSV to disassociate all RF Profile groups for each device.

5. Apply the Release 4.1 Hotfix1 on the setup following the instructions in the README file provided in the Hotfix tar file.

6. Login to the DCC UI and associate back the correct RF Profile groups for all the devices in the exported CSV file by following this procedure:

a. Search for the device using the Device ID field in the Device Manager screen.

b. In the Provision tab, click on Update.

c. In the Update Device Registration pop-up screen, in the RF Profile drop-down list box, select the same RF Profile group that was associated with this device (as per the CSV file) and click on Update.

d. Navigate to the Device Dashboard and verify that the correct RF Profile groups are shown in the Registration Data block.

e. Repeat these steps for each of the devices in the exported CSV to associate back all RF Profile groups for each device as it was before the Hotfix was applied.

CSCut09292: RMS41HF DCCUI is not validating the maximum number of values given for a parameter

Scenario

If a parameter in the DCC UI is provisioned with more than the allowable number of values (for example, if eleven values are provisioned and only ten are allowed), the instruction generation (IGS) fails in the RDU. Due to this, the RDU IGS state is “Waiting for Generation”. In this state, no updates are pushed to the device.

Workaround

Reprovision the parameters with the proper number of values and restart the RDU using the command /etc/init.d/bprAgent Restart.


June 30, 2015 HF6

Troubleshooting

CSCut20511 RMS4.1_MR: FGW Import Failing with Cause 'ZAP-ROUTE-IP-ADDRESS-ENABLE’

Scenario

A FemtoGateway group CSV import fails with the error “Failed to add group 'FGWXX’. Unknown parameter names- ZAP-ROUTE-IP-ADDRESS-ENABLE”. Where FGWXX represents the FGW Name specified in the CSV file.

Workaround

1. Log into the Central Server as root user.

2. Navigate to the directory /rms/app/rms/conf/ for the pmg-profile.xml.

3. Save a backup of the file pmg-profile.xml. If the pmg-profile.xml is not found in /rms/app/rms/conf/, then execute steps 4, 5, and 6.

4. Copy pmg-profile.xml from /rms/app/rms/doc/pmg/.

cp /rms/app/rms/doc/pmg/pmg-profile.xml /rms/app/rms/conf/

5. Change the permission of pmg-profile.xml.

chmod 664 pmg-profile.xml

6. Take a backup.

7. Edit and copy the below snippet into the file pmg-profile.xml.

<ParameterDefinition> <Name>ZAP-ROUTE-IP-ADDRESS-ENABLE</Name> <Type>boolean</Type> <SourceType>DeviceProperty</SourceType> <Writable>true</Writable> <Readable>true</Readable> <Deletable>true</Deletable></ParameterDefinition>

8. Restart the PMG Server with the command god restart PMGServer.

9. Retry importing the FemtoGateway group.

CSCut59222: RMS41HF04 Periodic Interval Parameters Should not be Added in Activated CoS3.5.11

Issue

These parameters make devices send more frequent Periodic Informs and perform more frequent RemScan. This issue is applicable to RMS 4.1 Hotfix04 only.

• FC-REM-2G-PERIODIC-INTERVAL

• FC-PERIODIC-INFORM-INTERVAL

• GPS-PERIODIC-INTERVAL

• FC-REM-3G-PERIODIC-INTERVAL

Workaround

1. Log in to the BAC UI with bacadmin credentials.

2. Select Configuration.

3. Navigate to Class of Service.

4. Click on activated-BV3.5.11.0.

5. Browse and delete these parameters:


June 30, 2015 HF6

Caveats

– FC-REM-2G-PERIODIC-INTERVAL

– FC-PERIODIC-INFORM-INTERVAL

– GPS-PERIODIC-INTERVAL

– FC-REM-3G-PERIODIC-INTERVAL

6. Scroll down the page and select “FC-ACTIVATED-INFORM-ENABLE”

7. Enter the value true and click Add.

8. Click Submit.

CSCut26992: AIO Redundancy Login as Root User Takes Time

Issue

Virtual machine (VM) migration via Vmotion or Cloning to a different DataStore may flush the contents of ovfenv.xml. This is a known problem of VMware.

WorkAround

Make sure to make a backup of /opt/vmware/etc/vami/ovfEnv.xml before performing a migration or cloning and restore this after the migration or cloning if required.

Alternatively if the ovfenv.xml file is blank, you can just add the following three lines in /opt/vmware/etc/vami/ovfEnv.xml

<Environment

>

</Environment>

And then, enter these lines in /etc/rc.local:

echo "<Environment

>

</Environment>" >>/opt/vmware/etc/vami/ovfEnv.xml

Caveats Refer to the bug toolkit online to view information for defects related to the RMS: https://tools.cisco.com/bugsearch.

Following is a list of important open defects for RMS release 4.1.0 with no known workarounds:

Table 8 Open Defects

Bug ID Description

CSCul76447 Ubi FAP always displays the UTC time

CSCun27329 [SN]SetLivedata pushes two values for FemtoNeighbourFilteringEnable flag

CSCun69770 UpdatePolygonsInPmg.sh failed to create few groups in RMS

CSCun96680 UI Operations taking longer time to complete

CSCuo69847 java.lang.NullPointerException when parameter not defined

CSCup28412 Increased downtime when both hosts in cluster are rebooted


June 30, 2015 HF6

https://tools.cisco.com/bugsearch

Caveats

Following is a list of defects closed for RMS release 4.0.0 and 4.1.0:

CSCup42348 AP Factory recovery support in ResetCPEToFactoryDefaults Msg

CSCuq27979 DCCUI should do Validation of Parameters for SLD and Groups

CSCuq30160 AP sending multiple 4 value change for GPS scan within a very short time

CSCuq37047 PMG not supporting EUTRA Parameters

CSCuq37350 Device with open mode RF profile and Closed Mode enabled get registered

CSCuq37852 PMG not setting Custom Properties in BAC for Successful Noti

CSCuq52211 Issues seen during PMG startup with Load running

CSCuq72110 reassigndevices.sh does not remove alarm profile from area

CSCuq73766 DCCUI doesn't display success msg when SAI/CELL import completes

CSCuq75630 Few LUS counter values are not logged correctly in PerfLog file

CSCuq95896 DNB returns unknown status if the GPS fails or is unknown and if DNB is failing

CSCur34680 DN-prefix value is not updated in pm stat file even though AP is updated

CSCus89695 Feb 4 2015 - NTPd.org Vulnerabilities for CVE-2014-9297 and CVE-2014-9298Public advisory link for NTPD issue is: http://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20141222-ntpd

CSCut14435 UMT job stops monitoring firmware upgrades after 18 hours

CSCut15953 RMS should generate alarm for PAR License Expiry.

CSCut38084 Upgrade takes time if disk space on the server is not sufficient

CSCut69267 PMG is not deleting the log (.gz) files that are older than 64 days.

CSCut74531 CID is not updating through update API when moving to different FGW.

CSCut90322 Abrupt interruption makes RMS going to irrecoverable state

CSCut90841 Issues with incomplete backup procedure

CSCut91777 HotFix5 upgrade script not considering PMGServer.console.log

CSCut92472 RMS-PC integration script optimization

CSCut97826 PMG Log rotation policy is not deleting older extracted files

CSCut94666 Default value does not match config template value for the parameters

CSCuu14321 RADIUS authorization needs to be disabled to support ASR 5000 geo-redundancy

CSCuu30109 RMS installation issues-4.1.0-1N: the OS gets stuck

Table 8 Open Defects (continued)

Bug ID Description

Table 9 Closed Defects

Bug ID Description

CSCul24149 PAR dropping Radius Access request

CSCul40880 ConnectionRequest Event code does not reach RMS - BV3.4.2.13

CSCum79863 DCC UI allows to create two pool groups with same range of values


June 30, 2015 HF6

http://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20141222-ntpd

Caveats

CSCun65696 LAT/LONG is not sent in Assigned Data Notification for Enterprise AP

CSCun82640 uls.csr has the IP address in SubjectAltName in uls.csr

CSCun85460 Due to incorrect certificate chain length, AP throws \"Unknown CA\"

CSCuo33397 PS session failing if IU-PLMNID & IU-RAC not configured

CSCuo51209 Admin1 user is not able to run the GDDT OPs tool script for bulk device

CSCuo69727 Serving node startup hangs in distributed RMS installation

CSCuo96987 SON overwrite parameters in RMS

CSCup05800 ULS archives all the AP stat files after certain interval

CSCup08947 central-multi-nodes-config.sh used for serving redundancy fails

CSCup48352 LiveData/ConnectionRequest not working when 2 DPEs are configured

CSCup73347 [Upgrade] PeriodicLogUpload is seen disabled post upgrade on DCC UI

CSCup81144 Not Receiving AP Alarms on Prime central

CSCuq49521 Signal Strength should be measured based on RSCP\RSSI parameters

CSCuq87681 DNL LV should not check for all neighbors after a single match is found

CSCuq93736 SN-2/ULS-2 on Site-2 in a redundant setup are missing routes to Site-1

CSCuq93477 RMS41: Unable to import back the exported RF profiles with no changes

CSCuq99588 SAC/CELL ID Provided in the Register XML is not as expected

CSCur16978 NWL scan randomization

CSCur17063 RMS to be compliant with v2.2 RF Profile version

CSCur17067 Add Reporting Mechanism in the template by default

CSCur17069 Add parameter Add parameter "EquivPLMNID" in RMS configurations

CSCur22639 Product evaluation for CVE-2014-6271 and CVE-2014-7169

CSCur24608 RMS4.1 : ASR5K Configuration to support Inter-Site DPE Redundancy

CSCur24633 RMS4.1 : DHCP Configuration for hardcoded subnet value

CSCur24656 RMS4.1 : Geo-Redundant DPE/ULS Deployment Failure Documentation

CSCur26689 FEAT 1159 and FEAT 1219 changes

CSCur28541 RMS4.1: Hotfix script execution fails on HA Central Server

CSCur87349 DNL-based location validation not working as required

CSCur85623 Initial location verification fails if there are no neighbors

CSCus27596 December 2014 - NTPd.org Vulnerabilities - CVE-2014-9293, CVE-2014-9294, CVE-2014-9295, CVE-2014-9296

Public advisory link for NTPD issue is: http://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20141222-ntpd

Table 9 Closed Defects (continued)

Bug ID Description


June 30, 2015 HF6

http://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20141222-ntpd

Related Documentation

Related Documentation • Cisco RAN Management System Installation Guide, Release 4.1

• Cisco RAN Management System Administration Guide, Release 4.1

• High Availability for Cisco RAN Management Systems, Release 4.1

• Cisco RAN Management System API Guide, Release 4.1

• Cisco RAN Management System SNMP/MIB Guide, Release 4.1

Obtaining Documentation and Submitting a Service RequestFor information on obtaining documentation, using the Cisco Bug Search Tool (BST), submitting a service request, and gathering additional information, see What’s New in Cisco Product Documentation at: http://www.cisco.com/c/en/us/td/docs/general/whatsnew/whatsnew.html.

Subscribe to What’s New in Cisco Product Documentation, which lists all new and revised Cisco technical documentation as an RSS feed and delivers content directly to your desktop using a reader application. The RSS feeds are a free service.

This document is to be used in conjunction with the documents listed in the “Related Documentation” section.

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: 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 partnership relationship between Cisco and any other company. (1110R)

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, network topology 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 unintentional and coincidental.

© 2015 Cisco Systems, Inc. All rights reserved.

CSCus69653 Evaluation of glibc GHOST vulnerability - CVE-2015-0235

GHOST issue public advisory link is: http://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20150128-ghost

CSCus87277 SNMP trap documentation enhancement

CSCuu37626 CPAR 6.0.1 version for RMS is EOS, needs upgrade to CPAR 6.1.2.3

CSCuu64883 RMS Sending Grid ID = O for APs registered as residential in RMS

CSCur75799 PNR crashes continuously 1minute after each restart with 10K leases

CSCuu72836 Leap second issues in RHEL 6.1

Table 9 Closed Defects (continued)

Bug ID Description


June 30, 2015 HF6

http://www.cisco.com/go/trademarks

http://www.cisco.com/c/en/us/td/docs/general/whatsnew/whatsnew.html

http://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20150128-ghost

Documents

RMS Release 4.1 Release Notes · The RMS provides end-to-end operations to transmit high quality voice ... PMG DB Database which can store geographical location ... Table 4 Checksum