Explore Cisco
How to Buy

Have an account?

  •   Personalized content
  •   Your products and support

Need an account?

Create an account

Cisco RAN Management System Administration Guide, Release 5.1

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

Book Contents
Find Matches in This Book
Available Languages
Download Options

Book Title

Cisco RAN Management System Administration Guide, Release 5.1

Chapter Title

Additional RMS Functionality

Results

Updated:
July 6, 2017

Chapter: Additional RMS Functionality

Additional RMS Functionality

INSEE Management

Enhanced SAC Management

Enhanced SAC Management helps you geo-locate the FemtoCell for emergency call routing in case no macro coverage is seen by the FemtoCell. INSEE code is not used for the following purpose:

  • Search a femtocell based on INSEE code

The INSEE code is a numerical indexing code used by the French National Institute for Statistics and Economic Studies (INSEE) to identify various entities, including communes, departments.

Configuring INSEE

Configuring INSEE allows you to enable or disable the INSEE feature in RMS.

Add the following file at the location on the central node:rms/app/CSCObac/rdu/mappingfiles:
  1. INSEE-SAC mapping file: insee_sac_femto.csv

To enable INSEE in RMS:

Procedure
    Step 1   Log in to the Central node.
    Step 2   Switch to root user: su-
    Step 3   Change the directory using command cd/rms/ova/scripts/post_install.
    Step 4   Execute the following command: configure_Insee_RF_AlarmsProfile.sh script

    System is enabled for INSEE code - SAC mapping feature.

    This tool enables the following optional configurations in RMS:

    • INSEE SAC configuration

    • Additional RF-Profile parameters configuration

    • Alarm profile group type support



    Example:Following is the output: 
    BPR client version: BPR2.7 
Parsing Args...
Parsing File: /rms/app/baseconfig/ga_kiwi_scripts/insee_configuration. kiwi
Warning: On line 138 could not find class [ubi-config-v3] when searching 
for constant value.  
Using [ubi-config-v3.5-ee] as String value instead.
...
Warning: On line 543 could not find class [@ubiquisys] when searching for 
constant value.  
Using [@ubiquisys.com] as String value instead.
Executing 117 batches...
PASSED|batchID=Batch:rms-aio-central/10.5.4.32:57c9999f:1474447a937:
80000002 
Batch 	  Activation mode = NoActivation|Confirmation mode = NoConfirmation|
Publishing mode = NoPublishing		
		EXPECT	
		ACTUAL|batch status code=BATCH_COMPLETED[0]|batch error msg=null 
Cmd 0 	  Line 29|Proprietary.changeSystemDefaultsInternally
({/pace/crs/start=false}, null)	
		EXPECT|expected command status code=CMD_OK[0]	
		ACTUAL|command status code=CMD_OK[0]|command error msg=null|data 
type=DATA_VOID[-1]|results=null
...
...
FAILED|batchID=Batch:rms-aio-central/10.5.4.32:57c9999f:1474447a937:8000004a 
Batch 	  Activation mode = NoActivation|Confirmation mode = 
NoConfirmation|Publishing mode = NoPublishing	
		EXPECT	
		ACTUAL|batch status code=BATCH_FAILED_WRITE[-121]|batch error msg=Batch 
failed. See status of the 
failed command for details. 
Cmd 0 	  Line 73|Configuration.addCustomPropertyDefinition(FC-PCH-POWER, 
java.lang.Integer)	
		EXPECT|expected command status code=CMD_OK[0]	
		ACTUAL|command status code=CMD_ERROR_CUSTOM_PROPERTY_REDEFINITION[-603]|
command error msg=A custom 
  property with the name [FC-PCH-POWER] already exists in the system.|data 
type=DATA_VOID[-1]|results=null	 
  -ERROR|command status code !=0
...
...
PASSED|batchID=Batch:rms-aio-central/10.5.4.32:57c9999f:1474447a937:800000d1 
Batch 	  Activation mode = NoActivation|Confirmation mode = NoConfirmation|
Publishing mode = NoPublishing	
		EXPECT	
		ACTUAL|batch status code=BATCH_COMPLETED[0]|batch error msg=null 
Cmd 0 	  Line 2039|Proprietary.changeSystemDefaultsInternally
({/pace/crs/start=true}, null)	
		EXPECT|expected command status code=CMD_OK[0]	
		ACTUAL|command status code=CMD_OK[0]|command error msg=null|data 
type=DATA_VOID[-1]|results=null

File: /rms/app/baseconfig/ga_kiwi_scripts/insee_configuration.kiwi
Finished tests in 7824ms
Total Tests Run    - 117
Total Tests Passed - 104
Total Tests Failed - 13
    Step 5   Check PMGServer status if it is up then skip this step.

    Example: 
    god status PMGServer
[rms-aio-central] /home/admin1 # god status PMGServer
PMGServer: unmonitored
    Step 6   If the PMGServer status is unmonitored then run the following command.

    Example: 
    god start PMGServer
Sending 'start' command

The following watches were affected:
PMGServer

check the status PMGServer should be up and running after sometime

[rms-aio-central] /home/admin1 # god status PMGServer
PMGServer: up

    Creating an INSEE SAC CSV File

    INSEE SAC csv files can be created in two ways. Both the options are provided in the following procedure.

    Procedure
      Step 1   Option 1:
      1. Locally, create a csv file with the name “insee_sac_femto.csv”.

        • The csv file should not contain any header fields or any comments (#, // etc are not permitted).

        • In this file enter comma separated list of INSEE code, SAC value For example, insee1,100.

          Note that there should not be any spaces before and after the comma.

        • INSEE code can be an alphanumeric string. Spaces at the start and end of the INSEE code are not permitted. Spaces in between INSEE code is allowed.

        • Data type of SAC is an unsigned integer with maximum value of 65535.

      2. Using WinScp or similar, copy this file on the Central node in the /tmp dir or user login dir.
      3. Log in to the Central node as root user.
      4. Copy insee_sac_femto.csv to /rms/app/CSCObac/rdu/mappingfiles.
      5. Validate this mapping file (see Verifying the Mapping Files).

        Whenever the INSEE SAC csv file is modified, it has to be validated to ensure that the changes are reflected.

      Step 2   Option 2:
      1. Log in to the Central node with a non-root user.
      2. Change to root user.
      3. Change dir using command ‘cd /rms/app/CSCObac/rdu/mappingfiles’.
      4. Create insee_sac_femto.csv file in the above dir using the vi insee_sac_femto.csv command.

        • The csv file should not contain any header fields or any comments (#, // etc are not permitted).

        • In this file enter comma separated list of INSEE code, SAC value For example, insee1,100.

          Note that there should not be any spaces before and after the comma.

        • INSEE code can be an alphanumeric string. Spaces at the start and end of the INSEE code are not permitted. Spaces in between INSEE code is allowed.

        • Data type of SAC is an unsigned integer with maximum value of 65535.

      5. Save the file.
      6. Validate this mapping file (see Verifying the Mapping Files).

        Whenever the INSEE SAC csv file is modified, it has to be validated to ensure that the changes are reflected.

      Verifying the Mapping Files

      Perform the procedure to validate the mapping file. If the INSEE code or the SAC value is not in the correct format, validation of the mapping file will fail. The changes made in mapping files take effect only after successful validation.

      Before You Begin

      Log in to the RMS and locate the mappingFiles.

      Procedure
        Step 1   Log in to the Central node.
        Step 2   Switch to root user: su-
        Step 3   Execute the following command to change the directory to mapping files: cd /rms/app/CSCObac/rdu/mappingfiles/
        Step 4   Make sure that there are two sub-directories present in the mappingfiles directory.
        1. latest
        2. backup
        Step 5   Copy the staged mapping files into the directory: cd /rms/app/CSCObac/rdu/mappingfiles
        Step 6   Validate the mapping files:
        1. Confirm that BAC Config is deployed and the Shell script is located at: /rms/app/baseconfig/bin/runkiwi.sh
        2. Confirm that the Kiwi script is available at: /rms/app/CSCObac/rdu/mappingfiles/addinsee_sac_femto.kiwi
          Note    Before running the command to validate the mapping files, ensure that entries in insee_sac_femto.csv are in valid format. INSEE code with leading and trailing spaces is not valid. However, INSEE code can contain spaces in between.

          For example:

          Valid entries in the mapping file: 
           AB123,567
         AB123,567
          Invalid entries in the mapping file: 
             AB123  ,567
  AB 123  ,567
       AB123,567
        3. Run the following commands to validate the mapping files added in the mappingfiles folder.
        4. Change directory using command cd /rms/app/baseconfig/bin.
        5. Run the kiwi script using the INSEE code - SAC mapping: ./runkiwi.sh /rms/app/CSCObac/rdu/mappingfiles/addinsee_sac_femto.kiwi.

        Edge-Node Discovery Provisioning

        Edge discovery is an extension to SON discovery, and allows you to provision one element with the address of another element on a different LAN subnet. Edge-node discovery provisioning propagates the list of members of each grid to the grid of the provisioned element and vice versa, thereby achieving a full mesh of both grids in each subnet.

        You can configure a single IP address or a set of IP addresses. There is one parameter required for edge-node discovery provisioning:

        • EdgeDiscoveryProvisioning—user-editable, read/write parameter found in the Site Group in the DCC-UI. To enable edge node discovery provisioning, you need to update the Site Group CSV file with the required IP address or IP addresses in the "EdgeDiscoveryProvisioning" field.

        The HNB is initialized with this property during its next connection to the RMS.

        Security Gateway Geographical Redundancy

        Security gateway (SecGW) geographical redundancy allows you to configure a second redundant security gateway (Cisco ASR 5000 server) IP address for the connected HNBs using the RMS DCC-UI. These parameters are used:

        • SecGWServer2 —user-editable read/write parameter found in the FemtoGateway and UMTSSecGW Group in the DCC-UI. Properties are "IPSEC Server Host 1" and "IPSEC Server Host 2". If these properties are defined in both groups, FemtoGateway and UMTSSecGW, then FemtoGateway group will take precedence.

        • RedundancyFailoverTimeout—read/write parameter which holds the value of the timer interval to determine when the HNB should trigger a failover to the redundant security gateway. This parameter is not configurable via the DCC-UI, but can be configured using SetLiveData.

        • LastUsedSecGWServer—read-only parameter which indicates to which SecGW the HNB was last connected. To enable this parameter, you need to update the Femto Gateway Group with the required redundant security gateway server IP address or FQDN in the field titled "SecGWServer2."

        The HNB is initialized with these properties during its next connection to the RMS.

        To add additional DHCP and RADIUS clients in the PNR and PAR, see the procedure in the "HNB Gateway and DHCP Configuration" section of the Cisco RAN Management System Installation Guide.

        To support the Security Gateway (SecGW) Geographical Redundancy feature, the FAP authorization needs to be disabled at RMS as described in the following steps:

        1. Log in to the Serving node.

        2. Switch to root user.

        3. Navigate to the directory /rms/app/CSCObac/dpe/conf/.

        4. Locate the "dpe.properties" file.

        5. Set "/authEP/AuthorizationEnable=false" in the dpe.properties file and save the file.

        6. Restart the DPE using the command: /etc/init.d/bprAgent restart dpe.

        IMSI Blacklisting

        International mobile subscriber identity (IMSI) blacklisting is available to use in field trial situations where a particular problematic IMSI is identified as causing call drops due to either poor RF performance or to the fact that the user is operating outside of the operating physical region. IMSI blacklisting is meant for enterprise APs only.

        To implement IMSI blacklisting, find the parameter under Site Group called Black list: (FC-BLACK-LIST). Specify a list of IMSIs which are to be blacklisted. Up to ten IMSIs can be provided.

        Integrating RMS with Prime Central Server

        To integrate RMS with Prime Central Server, see Cisco RAN Management System Installation Guide, Release 5.1.

        De-Registering RMS from Prime Central Server

        The following sections describes how to de-register RMS from the Prime Central Server on the Central node and de-register Prime Central Active and Disaster Recovery Server from RMS.

        De-Registering RMS With Prime Central Post Deployment

        To rerun the Cisco RMS integration with Prime Central on the Central node, complete the procedures listed in this section before the integration. It is mandatory to de-register Cisco RMS with Prime Central NMS before the rerun:

        Disabling SNMP Traps Notification to Prime Central NMS Interface

        Follow these steps to disable SNMP traps notifications to the Prime Central NMS interface on the Cisco RMS Central node.

        Procedure
          Step 1   Log in to the Central node and run the following commands.

          Example: 
          [rms-aio-central]cd /rms/ova/scripts/post-install
./configure_fm_server.sh
          Step 2   Enter the number of SNMP managers to be configured as ‘0’ to deregister the PC NMS interface. This will disable the SNMP traps notification. The script execution output log is displayed as follows:

          Example: 
          [rms-aio-central] /rms/ova/scripts/post_install # ./configure_fm_server.sh
*******************Script to configure NMS interface details for FM-Server*******************************
RMS FM Framework requires the NMS manager interface details...
Enter number of SNMP managers to be configured (0 to disable SNMP traps/1/2/3)
0
Disabling SNMP traps from RMS
Deleting the iptable rules, added for the earlier configured NMS...
iptables: Saving firewall rules to /etc/sysconfig/iptables:[  OK  ]
*********Done************
[rms-aio-central] /rms/ova/scripts/post_install #
          What to Do Next

          Complete Cleaning Up Files On Central Node procedure.

          Cleaning Up Files On Central Node

          To clean up the files on the Central node, which was generated from the earlier Prime Central integration procedure, complete these steps.

          Procedure
            Step 1   Go to the directory /rms/app/fm_server/prime_integrator.
            Step 2   Enter rm –rf DMIntegrator.log DMIntegrator.prop datasource.properties dbpasswd.pwd dmid.xml jms.log pc.xml.
            Step 3   Enter /rms/app/CSCObac/snmp/bin/snmpAgentCfgUtil.sh delete host rms-aio-central.
            Note   

            ' rms-aio-central' is the host name of the RMS Central node.

            What to Do Next

            Complete the De-Registering RMS Data Manager from Prime Central procedure.

            De-Registering RMS Data Manager from Prime Central

            De-register RMS Data Manager from Prime Central, which was used to integrate RMS with Prime Central earlier.

            Procedure
              Step 1   Log in to the Prime Central server using ssh with 'root' user ID and its password.
              Step 2   Enter su – primeusr.
              Step 3   Execute the list command to find the ID value assigned to the RMS host (Central node host name).
              Step 4   Enter cd ~/install/scripts.
              Step 5   Enter ./dmRemoveUtil.
              Note   

              When prompted, enter the Central administrator user ID and password and the RMS ID value, which is found in Step 3.

              Step 6   Log out from the Prime Central server.

              De-Registering Prime Central Active and Disaster Recovery Server from RMS

              Procedure
                Step 1   Log in to the Serving node as admin user. 
                 ssh admin@<serving-node IP>
                Step 2   Switch to root user using the following command 
                su root
                Step 3   Remove Prime Central Active and Disaster Recovery servers details that exist in the /etc/hosts file. 
                 vi /etc/hosts
                Step 4   Delete Prime Central DM integration files.
                Step 5   Go to the directory cd /rms/app/CSCObac/prime_integrator.
                Step 6   Delete the below DM integration files manually.

                • DMIntegrator.lo

                • DMIntegrator.prop

                • datasource.properties

                • dbpasswd.pwd

                • dmid.xml

                • jms.log

                • pc.xml 

                rm –rf DMIntegrator.log DMIntegrator.prop datasource.properties dbpasswd.pwd dmid.xml jms.log pc.xml
                Step 7   Delete SNMP Agent configurations as shown below: 
                /rms/app/CSCObac/snmp/bin/snmpAgentCfgUtil.sh delete host <Prime Central active ip address>
/rms/app/CSCObac/snmp/bin/snmpAgentCfgUtil.sh delete host <Prime Central  DR  ip address>
                Step 8   Delete Prime Central Active and Disaster Recovery Server details from the DPE CLI configurations. Login to the DPE CLI. 
                rms-Serving-blr01# no snmp-server host 10.105.242.19 notification
rms-Serving-blr01# no snmp-server host 10.105.242.36 notification
rms-Serving-blr01#snmp-server reload
                Note   

                To de-register RMS from both Prime Central and Disaster Recovery server, see the Cisco Prime Central 1.3 Quick Start Guide at http:/​/​www.cisco.com/​c/​en/​us/​td/​docs/​net_mgmt/​prime/​central/​1-3/​quick_start/​guide/​b_​prime_​central_​13_​qsg.html.

                Was this Document Helpful?

                FeedbackFeedback

                Contact Cisco