Upload
others
View
26
Download
0
Embed Size (px)
Citation preview
Release Notes for Cisco RAN ManagementSystem for Release 5.1 MR
First Published: November 20, 2015
Last Modified: February 15, 2016
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 providesend-to-end operations to transmit high quality voice and data from the Service Provider mobility users throughthe Service Providers mobility core.
These release notes are for Release 5.1.0 MR including Hotfix01. Following are some of the key highlightsof the RMS components:.
Abbreviations and DefinitionsAll abbreviations and definitions used in the document are provided here:
Table 1: Abbreviations and Definitions
DescriptionAbbreviation
Broadband Access Center: A Cisco TR-069 management product that includesRDU and DPE.
BAC
Chained Intra ChassisCIC
Customer Premises EquipmentCPE
Device Command and Control User InterfaceDCC UI
Distributed Provisioning Engine. A distributed server of the BAC product.DPE
Equipment IdentifierEID
Femto RAN ManagerFRM
Home Node BHNB
Home eNodeBHeNB
Release Notes for Cisco RAN Management System for Release 5.1 MR 1
DescriptionAbbreviation
Home eNode B GatewayHeNBGW
Home Node B GatewayHNBGW
Long Term EvolutionLTE
Log Upload ServerLUS
Network ListenNWL
Cisco Prime Access RegistrarPAR
Cisco Prime Network RegistrarPNR
Provisioning and Management GatewayPMG
Cisco Quantum SON SuiteQSS
Regional Distribution Unit, a part of the BAC that interfaces with the OSS northbound and DPE south bound and is the master data store.
RDU
Radio Environment MeasurementREM
RAN Management SystemRMS
Small Mode BusinessSMB
Self Optimizing NetworkSON
Secure Socket Layer, an authentication and encryption protocol.SSL
Transport Layer SecurityTLS
Technical Report 069 is a Broadband Forum (standard organization formerlyknown as the DSL forum) technical specification entitled CPE WANManagement Protocol (CWMP).
TR-069
Universal Mobile Telecommunication SystemUMTS
Universal Small Cell Access PointUSC AP
Access control list which specifies which cell phones can register with the AP.Whitelist
Release Notes for Cisco RAN Management System for Release 5.1 MR2
IntroductionAbbreviations and Definitions
System Requirements
Component VersionsRMS Releases 5.1 MR and 5.1 MR Hotfix require the following component versions:
VersionComponent
3.10.1 (Build : 201509210944_95)Broadband Access Center (BAC)
7.0.1 ( Build : 1446660468)Cisco Prime Access Registrar (CPAR)
8.3 (Build : 2)Cisco Prime Network Registrar (CPNR)
3.10.0.0BAC Tools
5.1.1
(Hotfix only) 5.1.2
Baseline Configuration for BAC
5.1.1 (Build : 253)
(Hotfix only) 5.1.2 (Build: 45)
Device Command and Control (DCC) UI
5.1.1 (Build : 253)
(Hotfix only) 5.1.2 (Build: 45)
Operations Tools
5.1.1 (Build : 253)OVA Installation Utilities
5.1.1 (Build : 253)
(Hotfix only) 5.1.2 (Build: 45)
Provisioning Management Gateway (PMG)
9.3.0 (Build : 253)Upload Server
5.1.1 (Build : 253)Fault Management Server
Installation ImageThe checksum values of the OVA files are provided in a text file together with the image download files, andas follows:
Table 2: Checksum of OVA Files
md5Sum ValueFilename
4ed916f49d74eec5b85183b5d393a3e8RMS-All-In-One-Solution-5.1.1-253.tar.gz
Release Notes for Cisco RAN Management System for Release 5.1 MR 3
IntroductionSystem Requirements
8968b41f38c14b736ad8ea5cd0994bc7RMS-Distributed-Solution-5.1.1-253.tar.gz
0d379c9b419d3742c13775be6a47a437RMS-Redundant-Solution-5.1.1-253.tar.gz
92c55b962acc1662d793964b0569388e
(Hotfix only) fd48d53689b08cb9d283f17f5b8d638b
RMS-UPGRADE-5.1.1-253.tar.gz
(Hotfix only)RMS-UPGRADE-5.1.2-45-HOTFIX01.tar.gz
Software CompatibilityRMS Releases 5.1 MR and 5.1 MR Hotfix are compatible with:
• USC AP versions:
BV 3.4.4.8, BV3.5.11.9 (and above), 3.5.12.XResidential
BV 3.5.9.X, BV 3.5.10.X, BV3.5.11.9 (and above), 3.5.12.XEnterprise
DSV4.0.0T.X
(Hotfix only) DSV4.0.6T.10190
4G Enterprise USC 6732
DSV3.8.0T.X
(Hotfix only) DSV3.8.6T.142
3G Enterprise USC 6732
• VMware vSphere, version 5.5.0
• PPM version 1.7 SP1
• PC version 1.5.0.0
• RHEL 6.7
• ovftool version 3.0.1
• USC 6732 3G Data Model, version 1.5.1
• USC 6732 LTE Data Model, version 2.2.86
• USC 6732 LTE Data Model, version 2.2.93
• Mozilla Firefox, version 42
Key Notes• The USC 6732 UMTS and LTE FAP is supported.
• Fresh installation (both all-in-one and distributed) and upgrade are supported.
Release Notes for Cisco RAN Management System for Release 5.1 MR4
IntroductionSoftware Compatibility
• By default, no location verification (LV) methods are enabled on a fresh RMS, Release 5.1 MRinstallation.
• NTP synchronization is recommended from ESXi and all the RMS nodes should be time-synchronized.
• Configuring external Syslogs post-OVA installation is not supported.
• The AP reachability alarm is not supported from RMS, Release 5.1 MR onwards.
• UpgradeMonitoring Tool (UMT) in DCCUI is not supported fromRMS 5.1MR onwards and is removedfrom the DCC UI.
• By default, it is recommended to set powerOn==False in all the descriptor files during a fresh RMSinstallation. After the installation is complete, start the Serving and Upload nodes after the Central nodeis completely up.
• The INSEE SAC configuration script name is changed from configure_func2.sh toconfigure_Insee_RF_AlarmsProfile.sh.
• RMS integration has been qualified with Cisco Prime components.
• After the RMS 4.1 to RMS 5.1 MR upgrade, all the LV related properties must be removed from thevarious groups and should be configured from the region group level only.
• PAR 7.0.1 demo license (bundled as part of RMS 5.1 MR package) is valid only till 14-Jan-2016. Anyinstallations or upgrades performed beyond this date have to procure a new license validity.
• (Hotfix only) The following updates are part of this Hotfix release:
◦Demo CAR license with a validity till 4-apr-2016 is added and can be found in this directory:/rms/upgrade/confFiles/license/CSCOar.lic.70. For demo deployment, thislicense can be applied till 4-apr-2016 and any installations or upgrades performed beyond this datehave to procure a new license validity.
◦The FC-LTE-CARRIER-I-OPENPCILISTSTART andFC-LTE-CARRIER-I-OPENPCILISTRANGE parameters are merged withFC-LTE-CARRIER-I-OPENPCILIST. The FC-LTE-INTRA-FREQ-OPEN-PCILIST-START andFC-LTE-INTRA-FREQ-OPEN-PCILIST-RANGE parameters are merged withFC-LTE-INTRA-FREQ-OPEN-PCILIST.
◦The format for the FC-LTE-IDLEMODE-INTERFREQ-CARRIER-I parameter values is changedfrom ',' separated to ';' .
◦The existing values of the FC-LTE-CARRIER-I-OPENPCILISTSTART andFC-LTE-CARRIER-I-OPENPCILISTRANGE parameters are retained and converted to the newformat post hotfix upgrade and populated to the FC-LTE-CARRIER-I-OPENPCILIST parameter.Similarly, the existing values of the FC-LTE-CARRIER-I-OPENPCILISTSTART andFC-LTE-CARRIER-I-OPENPCILISTRANGE parameters are retained and converted to the newformat post hotfix upgrade and populated to the FC-LTE-INTRA-FREQ-OPEN-PCILIST parameter.
◦QCI 6 and 7 are supported in this release. The default value of X_CISCO_COM_DSCP is changedfrom 46 to 26 for QCI 6 and from 46 to 18 for QCI 7.
◦For QCI, the existing values are retained except for the sixth and seventh instance where the valuesare changed to default for all regions.
◦In DCC UI, the FC-LTE-QOS-LIST is renamed to QCI Configuration in the Region tab.
Release Notes for Cisco RAN Management System for Release 5.1 MR 5
IntroductionKey Notes
◦The upgrade package now supports Java version 1.7.0_91 (64 bit) based on a security requirement.This version is updated on the Central node and Upload node.
◦To address PSIRT vulnerability, NTP version is updated to ntpdate-4.2.6p5-5.el6_7.2.x86_64 andntp-4.2.6p5-5.el6_7.2.x86_64.
◦As a part of security requirement , the upgrade package now supports Java version 1.7.0_91 (64bit).
New and Changed InformationNew features and enhancements to the earlier RMS system releases are added in RMS 5.1 MR and 5.1 MRHoftix releases. Following are the new features of RMS:
Table 3: RMS 5.1 MR New and Changed Information
DescriptionFeature
USC 6732 3G and 4G FAP in active mode is supported.USC 6732 FAP
RMS supports configuration of the Tracking Area Identity (TAI) list tothe AP. It allows the HeNB to decide whether to trigger X2-based HOor not.
Support of X2 Handover
RMS, Release 5.1 MR supports 300,000 FAPs.Support of 300,000 FAPs
RMS supports the capability for the AP to randomly assign PhysicalRandom Access Channel (PRACH) configuration parameters.
Support of PRACH
Table 4: RMS 5.1 MR Hotfix New and Changed Information
DescriptionFeature
RMS supports administration of QCI 6/7USC 6732 FAP - QCI
RMS supports changes in PCI related parameters.USC 6732 FAP - PCI
RMS supports updated LTE FAP parameters and descriptions of LTEFAP parameters.
USC 6732 FAP - Data ModelChanges
RMS supports RF profile change to modify the FACHtoIDLEtimer.USC 6732 FAP - RF Profile 3.3
RMS supports configuration of CommonCollectionPeriod parameter forthe LTE FAP.
USC 6732 FAP - CollectionPeriod
Release Notes for Cisco RAN Management System for Release 5.1 MR6
IntroductionNew and Changed Information
DeploymentThe supported deployments for RMS, Releases 5.1 MR and 5.1 MR Hotfix are:
• All-in-one
• Distributed Redundant
• All-in-one Redundant
InstallationThe RMS provides an integrated installation process, which installs a pre-packaged set of software, such thatyou do not have to install each separate component.
UpgradeUpgrade is supported only for the following releases:
• RMS, Release 4.1.0-1N with Hotfix06 to RMS, Release 5.1 MR
• RMS, Release 5.1 to RMS, Release 5.1 MR
• RMS, Release 5.1 MR to RMS, Release 5.1 MR Hotfix
Supported Hardware• UCS 240
Workarounds for Known Problems – Post InstallationThis section contains workarounds for known issues that might occur post installation.
CSCux21583 DCCUI homepage not loading
Workaround:Reload the page.
CSCux21601 GlobalUMTSsecGW property "IPSEC server host "value getting set default
Workaround: Post upgrade, set the values of IPSEC-SERVER-HOST.
CSCux21605 First time view of dashboard throwing error if we do a DPE restart
Workaround:Retry the operation again to view the dashboard.
CSCux21609 Medium Vulnerability Detected on 3 Nodes through Nessus Tool
Workaround:Refer to the "RMS Ugrade" chapter in the Cisco RANManagement System Installation Guide,Release 5.1 MR.
Release Notes for Cisco RAN Management System for Release 5.1 MR 7
IntroductionDeployment
CSCux21610 CAR core files getting generated during upgrade
Workaround: None. There is no functional impact.
CSCux21614 Audit Log Manipulation - Central Node on DCC UI logs
Workaround: None. There is no functional impact.
CSCux21617 Display of NeighborListInUse takes lot of time in case no staticneighbor
Workaround: Refresh DCC UI.
CSCux21640 Postgres errors seen in the upgrade logs w.r.t password_lifetime
Workaround: None. There is no functional impact.
CSCux21646 rhsmcertd process fails to get stopped on all the nodes
Workaround: None. There is no functional impact.
CSCuy23241 Serving node console window throwing errors.
Workaround: None. There is no functional impact.
CSCuy23249 While running hot fix script throwing some exception.
Workaround: None. There is no functional impact.
CaveatsThis section only includes the bug ID and a short description of the bug. For details on the symptoms, conditions,and workaround for a particular bug you must use the Bug Search Tool.
Use the following link to access the tool: https://tools.cisco.com/bugsearch/search. You are prompted to loginto www.cisco.com. After successful login, the Bug Search Tool page opens. Use the Help link in the BugSearch Tool to obtain detailed help.
Table 5: Open Caveats
DescriptionBug ID
DCCUI homepage not loadingCSCux21583
GlobalUMTSsecGW property "IPSEC server host "value getting set defaultCSCux21601
First time view of dashboard throwing error if we do a DPE restartCSCux21605
Medium Vulnerability Detected on 3 Nodes through Nessus ToolCSCux21609
CAR core files getting generated during upgradeCSCux21610
Audit Log Manipulation - Central Node on DCC UI logsCSCux21614
Release Notes for Cisco RAN Management System for Release 5.1 MR8
IntroductionCaveats
DescriptionBug ID
Display of NeighborListInUse takes lot of time in case no staticneighborCSCux21617
Postgres errors seen in the upgrade logs w.r.t password_lifetimeCSCux21640
rhsmcertd process fails to get stopped on all the nodesCSCux21646
RF profile deployment version is does not change to v3.3 for Residential RF.CSCuy23226
Table 6: Closed Caveats
DescriptionBug ID
[Security] Verifying security issues with Qualys scannerCSCuy06871
[Security] Application of Java security fixCSCuy06881
RMS shall resolve the PSIRT vulnerability CSCuw84997CSCuw84997
GDDT is giving Null Pointer ExceptionCSCuy07617
BGL_ST_PeriodicUploadInterval value should be changed for LTE Enterprise FAPCSCuy07707
RMS4.1 : Script for regenerating certificate for DPE.CSCup08895
FM Component reboot alarms' occurence time incorrect in PC GUICSCur63769
RMS redundancy procedure to be simplifiedCSCur71567
hard coded default bacadmin password causes some scripts failureCSCus05455
RMS50:BACCTools APIScripter.arguments file has password in clear textCSCus10619
Upgrade Monitor Tool - Error when querying FAPs outstanding for UpgradeCSCut18541
OVAdeployer_redundancy.sh script doesn't allow only hotstandbyDeploymentCSCut59749
APRIL 2015 NTPd VulnerabilitiesCSCut77579
SSL Version 2 and 3 Protocol Detection on Upload nodeCSCut90396
RMS4.1 - use of the specific-trap value on enterpriseSpecific (6) trapsCSCuu17721
RMS4.1 - use of the specific-trap value on enterpriseSpecific (6) trapsCSCuu17721
configure_fm_server script should support PC-DR integrationCSCuu28638
RMS5.1: ntp postinstall script doesnt update changesCSCuu38427
Release Notes for Cisco RAN Management System for Release 5.1 MR 9
IntroductionCaveats
DescriptionBug ID
Group-UsageReport and Max Num of Devices shows incorrect dataCSCuu48368
Audit Log Manipulation - Central NodeCSCuu54870
RMS51 Reprting Mechanism of 41st Alarm needs to supported by RMSCSCuu59009
configursnmpserving node script over write Active PC configurationCSCuu71858
After upgrade of RHEL 6.6 the Console for all nodes are stuckCSCuu78502
RMS 4.1 AR stores core dump files under Serving Node root directoryCSCuu80935
RHEL-6.6 Redhat Linux Patch level-Vulnerabilities detected on 3 nodesCSCuu82218
First time login to dcc_ui after upgrade giving errorCSCuu83243
RMS 5.1 API doc needs to be updated with 200Ok IP Notification statusCSCuu90514
configure_fm_server script needs to enable Snmptrap_Enable == TrueCSCuu91794
[Upgrade]AP reboots post upgrade due to configtemplate value changeCSCuu94167
RMS51:AlarmHandler is not up after EFT to FCS upgradeCSCuu96850
RMS5.1Upgrade Logs printing in console for EE ConfigurationsCSCuu98189
PMG allows provisioning even after out of sync with RDUCSCuv06728
BAC Custom Properties Release 4.1 should include discovered dataCSCuv14018
FC-SERVICE-STATUS not explained in RMS admin guideCSCuv15611
LAC/RAC lists for HotSpotAPs need to be removed from FemtoGatewaygroupsCSCuv25821
duplicate cell ID - EE gridCSCuv43859
Service Provisioning Status in DCCUI should have different statesCSCuv54322
Region group needs to be removed from the RMS4.1 admin docCSCuv92724
DCCUI login issues in Mozilla Firefox because of CIPHER_SUITE issuesCSCuw46385
Related Documentation• Cisco RAN Management System Installation Guide
Release Notes for Cisco RAN Management System for Release 5.1 MR10
IntroductionRelated Documentation
• Cisco RAN Management System Administration Guide
• Cisco RAN Management System SNMP/MIB Guide
• High Availability for Cisco RAN Management Systems
• Cisco RAN Management System API Guide
• RMS Configurable Parameters
• BAC Custom Properties
Services and Support
For information on obtaining documentation, obtaining support, providing documentation feedback, securityguidelines, and also recommended aliases and general Cisco documents, see themonthlyWhat's New in CiscoProduct Documentation, which also lists all new and revised Cisco technical documentation, at: http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html.
Release Notes for Cisco RAN Management System for Release 5.1 MR 11
IntroductionServices and Support
Release Notes for Cisco RAN Management System for Release 5.1 MR12
IntroductionServices and Support
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 Ciscotrademarks, go to this URL: http://www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respectiveowners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)
© 2015-2016 Cisco Systems, Inc. All rights reserved.