Additional RMS Functionality

Transcription

1 Geographical Identifier Management, page 1 Edge-Node Discovery Provisioning, page 5 Security Gateway Geographical Redundancy, page 6 IMSI Blacklisting, page 6 Integrating RMS with Prime Central Server, page 7 De-Registering RMS from Prime Central Server, page 7 Integrating RMS with Cisco Prime Performance Manager, page 9 Geographical Identifier Management The Geographical Identifier code is generic term used for INSEE, Postal, or any other identifier code, which can be numeric. 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. The Geographical Identifier code is not used for the following purpose: Search a femtocell based on Geographical Identifier code The Geographical Identifier 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 Geographical Identifier Configuring the Geographical Identifier allows you to enable or disable the Geographical Identifier feature in RMS. Add the following file at the location on the central node:rms/app/cscobac/rdu/mappingfiles: 1 Geographical Identifier -SAC mapping file: insee_sac_femto.csv 1

2 Configuring Geographical Identifier To enable the Geographical Identifier in RMS: Step 3 Step 4 Log in to the Central node. Switch to root user: su- Change the directory using command cd/rms/ova/scripts/post_install. Execute the following command: configure_insee_rf_alarmsprofile.sh script System is enabled for Geographical Identifier code - SAC mapping feature. This tool enables the following optional configurations in RMS: Geographical Identifier SAC configuration Additional RF-Profile parameters configuration Alarm profile group type support 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/ :57c9999f: a937: 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/ :57c9999f: a937: a 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... 2

3 Creating an Geographical Identifier SAC CSV File... PASSED batchid=batch:rms-aio-central/ :57c9999f: a937: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 Step 5 File: /rms/app/baseconfig/ga_kiwi_scripts/insee_configuration.kiwi Finished tests in 7824ms Total Tests Run Total Tests Passed Total Tests Failed - 13 Check PMGServer status if it is up then skip this step. Step 6 god status PMGServer [rms-aio-central] /home/admin1 # god status PMGServer PMGServer: unmonitored If the PMGServer status is unmonitored then run the following command. 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 Geographical Identifier SAC CSV File The Geographical Identifier SAC csv files can be created in two ways. Both the options are provided in the following procedure. Option 1: a) 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 Geographical Identifier code, SAC value For example, insee1,100. Note that there should not be any spaces before and after the comma. 3

4 Verifying the Mapping Files The Geographical Identifier code can be an alphanumeric string. Spaces at the start and end of the Geographical Identifier code are not permitted. Spaces in between the Geographical Identifier code is allowed. Data type of SAC is an unsigned integer with maximum value of b) Using WinScp or similar, copy this file on the Central node in the /tmp dir or user login dir. c) Log in to the Central node as root user. d) Copy insee_sac_femto.csv to /rms/app/cscobac/rdu/mappingfiles. e) Validate this mapping file (see Verifying the Mapping Files, on page 4). Whenever the Geographical Identifier SAC csv file is modified, it has to be validated to ensure that the changes are reflected. Option 2: a) Log in to the Central node with a non-root user. b) Change to root user. c) Change dir using command cd /rms/app/cscobac/rdu/mappingfiles. d) 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 Geographical Identifier code, SAC value For example, geographical identifier 1,100. Note that there should not be any spaces before and after the comma. The Geographical Identifier code can be an alphanumeric string. Spaces at the start and end of the Geographical Identifier code are not permitted. Spaces in between Geographical Identifier code is allowed. Data type of SAC is an unsigned integer with maximum value of e) Save the file. f) Validate this mapping file (see Verifying the Mapping Files, on page 4). Whenever the Geographical Identifier 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 Geographical Identifier 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. 4

5 Edge-Node Discovery Provisioning Step 3 Step 4 Step 5 Step 6 Log in to the Central node. Switch to root user: su- Execute the following command to change the directory to mapping files: cd /rms/app/cscobac/rdu/mappingfiles/ Make sure that there are two sub-directories present in the mappingfiles directory. a) latest b) backup Copy the staged mapping files into the directory: cd /rms/app/cscobac/rdu/mappingfiles Validate the mapping files: a) Confirm that BAC Config is deployed and the Shell script is located at: /rms/app/baseconfig/bin/runkiwi.sh b) 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. Geographical Identifier code with leading and trailing spaces is not valid. However, the Geographical Identifier 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 c) Run the following commands to validate the mapping files added in the mappingfiles folder. d) Change directory using command cd /rms/app/baseconfig/bin. e) Run the kiwi script using the Geographical Identifier 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: 5

6 Security Gateway Geographical Redundancy 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. 6

7 Integrating RMS with Prime Central Server 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, on page 7 De-Registering Prime Central Active and Disaster Recovery Server from RMS, on page 9 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, on page 7 Cleaning Up Files On Central Node, on page 8 De-Registering RMS Data Manager from Prime Central, on page 8 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. Log in to the Central node and run the following commands. [rms-aio-central]cd /rms/ova/scripts/post-install./configure_fm_server.sh 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: [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 7

8 De-Registering RMS With Prime Central Post Deployment 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, on page 8 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. Step 3 Go to the directory /rms/app/fm_server/prime_integrator. Enter rm rf DMIntegrator.log DMIntegrator.prop datasource.properties dbpasswd.pwd dmid.xml jms.log pc.xml. 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, on page 8 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. Step 3 Step 4 Step 5 Step 6 Log in to the Prime Central server using ssh with 'root' user ID and its password. Enter su primeusr. Execute the list command to find the ID value assigned to the RMS host (Central node host name). Enter cd ~/install/scripts. Enter./dmRemoveUtil. Note When prompted, enter the Central administrator user ID and password and the RMS ID value, which is found in Step 3. Log out from the Prime Central server. 8

9 De-Registering Prime Central Active and Disaster Recovery Server from RMS De-Registering Prime Central Active and Disaster Recovery Server from RMS Log in to the Serving node as admin user. ssh IP> 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 Step 5 Step 6 Delete Prime Central DM integration files. Go to the directory cd /rms/app/cscobac/prime_integrator. Delete the below DM integration files manually. DMIntegrator.lo DMIntegrator.prop datasource.properties dbpasswd.pwd dmid.xml jms.log pc.xml Step 7 Step 8 rm rf DMIntegrator.log DMIntegrator.prop datasource.properties dbpasswd.pwd dmid.xml jms.log pc.xml 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> 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 notification rms-serving-blr01# no snmp-server host 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 quick_start/guide/b_prime_central_13_qsg.html. Integrating RMS with Cisco Prime Performance Manager Cisco Prime Performance Manager provides performance statistics and reports for service provider and large enterprise networks including access, edge, distribution, core, mobile backhaul, carrier Ethernet, and core MPLS networks. Cisco Prime Performance Manager acquires devices by importing Cisco Prime Network 9

10 Integrating RMS with Cisco Prime Performance Manager Devices or by running device discovery. After acquiring devices, Prime Performance Manager uses SNMP polling to collect device performance statistics. To install Cisco Prime Performance Manager and integrate it with RMS, follow these steps: For Cisco Prime Performance Manager installation, see Cisco Prime Performance Manager Quick Start Guide at products-installation-guides-list.html. For RMS integration with Cisco Prime Performance Manager, see the "Small Cell Support" section provided in the Cisco Prime Performance Manager User Guide at cloud-systems-management/prime-performance-manager/products-user-guide-list.html. Ensure proper IPTables are added in all the nodes Central Node: iptables -A INPUT -s <ppm server IP> -d <Central node eth1> -i eth1 -p tcp -m tcp --dport 22 -m state --state NEW -j ACCEPT iptables -A INPUT -s <ppm server IP> -d <Central node eth1> -i eth1 -p udp -m udp --dport 161 -m state --state NEW -j ACCEPT Serving Node: iptables -A INPUT -s <ppm server IP> -d <Serving node eth-0> -i eth-0 -p tcp -m tcp --dport 22 -m state --state NEW -j ACCEPT iptables -A INPUT -s <ppm server IP> -d <Serving node eth-0> -i eth-0 -p udp -m udp --dport 161 -m state --state NEW -j ACCEPT Upload Node: iptables -A INPUT -s <ppm server IP> -d <Upload node eth-0> -i eth-0 -p tcp -m tcp --dport 22 -m state --state NEW -j ACCEPT iptables -A INPUT -s <ppm server IP> -d <Upload node eth-0> -i eth-0 -p udp -m udp --dport 161 -m state --state NEW -j ACCEPT iptables -A INPUT -s /32 -d /32 -i eth1 -p tcp -m tcp --dport 22 -m state --state NEW -j ACCEPT iptables -A INPUT -s /32 -d /32 -i eth1 -p udp -m udp --dport 161 -m state --state NEW -j ACCEPT In the above example, is the PPM server and is the Central node IP. 10