Additional RMS Functionality

Transcription

1 INSEE Management, page 1 Edge-Node Discovery Provisioning, page 5 Security Gateway Geographical Redundancy, page 5 IMSI Blacklisting, page 6 Integrating RMS and Prime Central Active with Disaster Recovery Server, page 6 De-Registering Prime Central Active and Disaster Recovery Server from RMS, page 12 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: April 28, 2015 HF5 1

2 Configuring INSEE Step 1 Step 2 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_func2.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 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!= PASSED batchid=batch:rms-aio-central/ :57c9999f: a937:800000d1 2 April 28, 2015 HF5

3 Creating an INSEE SAC CSV File 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 INSEE SAC CSV File INSEE SAC csv files can be created in two ways. Both the options are provided in the following procedure. Step 1 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 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 b) Using WinScp or similar, copy this file on the Central node in the /tmp dir or user login dir. April 28, 2015 HF5 3

4 Verifying the Mapping Files 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 INSEE SAC csv file is modified, it has to be validated to ensure that the changes are reflected. Step 2 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 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 e) Save the file. f) Validate this mapping file (see Verifying the Mapping Files, on page 4). 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. Step 1 Step 2 Step 3 Step 4 Step 5 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: 4 April 28, 2015 HF5

5 Edge-Node Discovery Provisioning Step 6 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. 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 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 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 Group in the DCC-UI. April 28, 2015 HF5 5

6 IMSI Blacklisting 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. 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 and Prime Central Active with Disaster Recovery Server Integrating the Prime Central fault management active and Disaster Recovery enables AP alarms to be forwarded to the Prime Central NMS through the SNMPv2c interface. Before You Begin Ensure the /etc/hosts of Prime Central active and Disaster Recovery server has the serving node details. Step 1 Update host information on RMS. a) Log in to the Serving node as admin user. ssh admin@<serving-node IP> b) Switch to root user using the following command. su root c) Update /etc/hosts file with Prime Central Active and Disaster Recovery server details in below format. vi /etc/hosts <IP> < FQDN > <host name> prime-central-active.cisco.com prime-central-active prime-central-secondary.cisco.com prime-central-secondary d) Save the host information. Step 2 Disable IPtable services. 6 April 28, 2015 HF5

7 Integrating Prime Central Active Server with RMS Note IPtable services should be stopped while executing the script and restarted after the script is executed and appropriate firewall rules are added. service iptables save admin1]# service iptables save iptables: Saving firewall rules to /etc/sysconfig/iptables:[ OK ]save iptables service Disable IPtables service on the Serving nodes. service iptables stop admin1]# service iptables stop iptables: Flushing firewall rules: [ OK ] iptables: Setting chains to policy ACCEPT: filter [ OK ] iptables: Unloading modules: [ OK ] [root@rms-serving-blr01 admin1]# What to Do Next Continue with the Integrating Prime Central Active Server with RMS, on page 7 procedure without logging out. Integrating Prime Central Active Server with RMS Step 1 Step 2 Step 3 Execute primeintegration.sh script. Navigate to the below directory: cd /rms/app/cscobac/prime_integrator Run the primeintegration.sh script. [root@rms-serving-blr01 prime_integrator]#./primeintegration.sh Integrating BAC with Prime Central. Are you sure? (y/n) [n]: y Select mode - Active(a) or DR(d) [a]: <select option a for BAC integration with Prime Central Active server> Enter the Prime Central Database Server IP Address [rms-serving-blr01]: <Prime Central Active DB IP> Enter the Prime Central database name (sid) [primedb]: <SID of Prime Central Active DB> Enter the Prime Central database port [1521]: <Prime CentralActive DB port> Enter the Prime Central database user [primedba]: <Prime Central Active DB Administrator user> Enter the Prime Central database password : <Prime Central Active DB Administrator user password> Enter the Prime Central SNMP Trap Host [ ]: <Prime Central Active IP> Enter the Prime Central SNMP Trap port [1162]: <Prime Central Active port> [root@rms-serving-blr01 prime_integrator]#./primeintegration.sh Integrating BAC with Prime Central. Are you sure? (y/n) [n]: y Select mode - Active(a) or DR(d) [a]: a April 28, 2015 HF5 7

8 Integrating Prime Central Active Server with RMS Enter the Prime Central Database Server IP Address [rms-serving-blr01]: Enter the Prime Central database name (sid) [primedb]: primedb Enter the Prime Central database port [1521]: 1521 Enter the Prime Central database user [primedba]: primedba Enter the Prime Central database password : ******* Enter the Prime Central SNMP Trap Host [ ]: Enter the Prime Central SNMP Trap port [1162]: 1162 ********* Running DMIntegrator on rms-serving-blr01 at Fri Apr 17 13:52:35 IST 2015 *********** Invoking./DMIntegrator.sh with [PROPFILE: DMIntegrator.prop] [SERVER: ] [SID: primedb] [USER: primedba] [PORT: 1521] [ID: ] - Initializing - Checking property file - Validating Java - Setting ENVIRONMENT - DM install location: /rms/app/cscobac - User Home Direcory: /root - Extracting DMIntegrator.tar - Setting Java Path - JAVA BIN : /rms/app/cscobac/jre/bin/java -classpath /rms/app/cscobac/prime_integrator/dmintegrator/lib/*:/rms/app/cscobac/prime_integrator/dmintegrator/lib - Creating Data Source - Encrypting DB Passwd - Created /rms/app/cscobac/prime_integrator/datasource.properties - PRIME_DBSOURCE : /rms/app/cscobac/prime_integrator/datasource.properties - Checking DB connection parameters - Insert/Update DM Data in Suite DB - dmid.xml not found. Inserting - Regular case - Inserted with ID : bac://bac:9 - Setting up SSH on the DM - Setting SSH Keys - Copying /usr/bin/scp - Modifying /rms/app/cscobac/prime_local/prime_secured/ssh_config - file transfer test successful - Adding Prime Central server into pc.xml - Running DMSwitchToSuite.sh - /DMSwitchToSuite.sh doesn't exist. Skipping The Integration process completed. Check the DMIntegrator.log for any additional details Updating trap host and port Process [snmpagent] has been restarted. Prime Central integration is successful. [root@rms-serving-blr01 prime_integrator]# Note From the above script output make a note of the DM ID value (Inserted with ID : bac://bac:9 ) and ensure that the same DM ID value is used for the Prime Central Disaster Recovery Server integration. What to Do Next Continue with the Integrating Prime Central Disaster Recovery Server, on page 9 procedure without logging out. 8 April 28, 2015 HF5

9 Integrating Prime Central Disaster Recovery Server Integrating Prime Central Disaster Recovery Server Step 1 Remove the dmid.xml file from /rms/app/cscobac/prime_integrator after integrating Prime Central Active server. Step 2 [root@rms-serving-blr01 prime_integrator]# rm dmid.xml rm: remove regular file `dmid.xml'? y [root@rms-serving-blr01 prime_integrator] Run the primeintegration.sh script again for integrating the Prime Central Disaster Recovery server with RMS. [root@rms-serving-blr01 prime_integrator]#./primeintegration.sh Integrating BAC with Prime Central. Are you sure? (y/n) [n]: y Select mode - Active(a) or DR(d) [a]: <select option d for BAC integration with Prime Central Disaster Recovery server> Enter the Prime Central Database Server IP Address [rms-serving-blr01]: <Prime Central Disaster Recovery DB IP > Enter the Prime Central database name (sid) [primedb]: <SID of Prime Central Disaster Recovery DB> Enter the Prime Central database port [1521]: <Prime Central Disaster Recovery DB port> Enter the Prime Central database user [primedba]: <Prime Central Disaster Recovery DB Administrator user> Enter the Prime Central database password : <Prime Central Disaster Recovery DB Administrator user password> Enter the Prime Central SNMP Trap Host [ ]: <Prime Central Disaster Recovery IP> Enter the Prime Central SNMP Trap port [1162]: <Prime Central Disaster Recovery snmp port> [root@rms-serving-blr01 prime_integrator]#./primeintegration.sh Integrating BAC with Prime Central. Are you sure? (y/n) [n]: y Select mode - Active(a) or DR(d) [a]: d Enter the Prime Central Database Server IP Address [rms-serving-blr01]: Enter the Prime Central database name (sid) [primedb]: primedb Enter the Prime Central database port [1521]: 1521 Enter the Prime Central database user [primedba]: primedba Enter the Prime Central database password : ********** Enter the Prime Central SNMP Trap Host [ ]: Enter the Prime Central SNMP Trap port [1162]: 1162 Enter the Prime Central Domain Manager (DM) Id [1]: 9 ********* Running DMIntegrator on rms-serving-blr01 at Fri Apr 17 13:54:50 IST 2015 *********** Invoking./DMIntegrator.sh with [PROPFILE: DMIntegrator.prop] [SERVER: ] [SID: primedb] [USER: primedba] [PORT: 1521] [ID: 9] - Initializing - Checking property file - Validating Java - Setting ENVIRONMENT - DM install location: /rms/app/cscobac April 28, 2015 HF5 9

10 Integrating Prime Central Disaster Recovery Server - User Home Direcory: /root - Extracting DMIntegrator.tar - Setting Java Path - JAVA BIN : /rms/app/cscobac/jre/bin/java -classpath /rms/app/cscobac/prime_integrator/dmintegrator/lib/*:/rms/app/cscobac/prime_integrator/dmintegrator/lib - Creating Data Source - Encrypting DB Passwd - Created /rms/app/cscobac/prime_integrator/datasource.properties - PRIME_DBSOURCE : /rms/app/cscobac/prime_integrator/datasource.properties - Checking DB connection parameters - Checking if ID is valid - Insert/Update DM Data in Suite DB - dmid.xml not found. Inserting - Disaster Recovery case - Inserted with ID : bac://bac:9 - Setting up SSH on the DM - Setting SSH Keys - Copying /usr/bin/scp - Modifying /rms/app/cscobac/prime_local/prime_secured/ssh_config - file transfer test successful - Adding Prime Central server into pc.xml - Running DMSwitchToSuite.sh - /DMSwitchToSuite.sh doesn't exist. Skipping The Integration process completed. Check the DMIntegrator.log for any additional details Updating trap host and port Process [snmpagent] has been restarted. Step 3 Prime Central integration is successful. [root@rms-serving-blr01 prime_integrator]# Update DPE configurations on the Serving node with Prime Central Active and Disaster Recovery server details. a) Log in to the DPE CLI prompt using the following command and use the RMS_App password. telnet localhost 2323 [root@rms-serving-blr01 prime_integrator]# telnet localhost 2323 Trying Connected to localhost. Escape character is '^]'. rms-serving-blr01 BAC Device Provisioning Engine User Access Verification Password: rms-serving-blr01> en Password: b) Update the Prime Central details as shown in the below example : rms-serving-blr01# snmp-server host <PRIMECENTRAL_ACTIVE_SERVER_IP> notification community public udp-port 1162 rms-serving-blr01# snmp-server host <PRIMECENTRAL_DISASTOR_RECOVERY_IP> notification community public udp-port 1162 rms-serving-blr01# snmp-server host notification community public udp-port 1162 rms-serving-blr01# snmp-server host notification community public udp-port 1162 % OK () Requires SNMP agent restart "> snmp-server reload" rms-serving-blr01#snmp-server reload No such process [nativesnmpagent]. Process [snmpagent] has been restarted. % OK rms-serving-blr01# exit 10 April 28, 2015 HF5

11 Integrating Prime Central Disaster Recovery Server Step 4 % Connection closed. Connection closed by foreign host. Verify if SNMP agent details are updated in the Serving node with the Prime Central Active and Disaster Recovery server details using the following command. /rms/app/cscobac/snmp/bin/snmpagentcfgutil.sh show Sample Output Step 5 Location : Contact : Port Number : 8001 Notification Type : inform Notification Retries : 3 Notification Timeout : 10 Notification Recipient Table : [ Host IP address, Community, UDP Port ] [ , public, 1162 ] [ , public, 1162 ] Access Control Table : Read Only Communities Read Write Communities Add the new IPtable rules for the newly configured Prime Central and Disaster Recovery server and enable the IPtable service. # iptables -A OUTPUT -p udp -o eth0 -s <$Serving_Node_Eth0_Address> -d <$Snmptrap1_Address> --dport <$Snmptrap_PortNumber> -m state --state NEW -j ACCEPT Step 6 iptables -A OUTPUT -p udp -o eth0 -s d dport m state --state NEW -j ACCEPT iptables -A OUTPUT -p udp -o eth0 -s d dport m state --state NEW -j ACCEPT Save and start the IPtable service. service iptables save [root@rms-serving-blr01 admin1]# service iptables save iptables: Saving firewall rules to /etc/sysconfig/iptables:[ OK ]save iptables service service iptables start [root@rms-serving-blr01 admin1]# service iptables start iptables: Applying firewall rules: [ OK ] April 28, 2015 HF5 11

12 De-Registering Prime Central Active and Disaster Recovery Server from RMS De-Registering Prime Central Active and Disaster Recovery Server from RMS Step 1 Step 2 Log in to the Serving node as admin user. ssh admin@<serving-node 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/fm_server/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. 12 April 28, 2015 HF5