Here are the steps:   If the Prime Infrastructure servers are paired for High Availability (HA), remove HA before performing these steps. Once the IP address is changed, the servers can be paired again.   1. Login to the console of the Prime Infrastructure server as an 'admin' user.   2. Stop the Service by using 'ncs stop' command.   3. Identify the interface name for which the IP address should be changed using the 'show interface' command   For example: prime-eagle/admin# show interface GigabitEthernet 1 Link encap:Ethernet HWaddr 00:50:56:A1:16:3C inet addr:10.10.20.30 Bcast:10.10.20.1 Mask:255.255.255.0 inet6 addr: 2003:a04::8d3c:2304:51e0:5b1b/64 Scope:Global inet6 addr: 2003:a04::250:56ff:fea1:163c/64 Scope:Global inet6 addr: fe80::250:56ff:fea1:163c/64 Scope:Link inet6 addr: 2003:a04::1089:f316:a0c1:d710/64 Scope:Global inet6 addr: 2003:a04::2447:eb8c:c538:2d3/64 Scope:Global inet6 addr: 2003:a04::d95f:d46f:e149:3545/64 Scope:Global inet6 addr: 2003:a04::c00d:dd7f:84e6:31ce/64 Scope:Global inet6 addr: 2003:a04::d17e:c3bd:100f:78ed/64 Scope:Global inet6 addr: 2003:a04::8852:f9c0:e4f8:6acf/64 Scope:Global UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:59059145 errors:0 dropped:0 overruns:0 frame:0 TX packets:32775030 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:27751205364 (25.8 GiB) TX bytes:15591640503 (14.5 GiB)   In this example, 'GigabitEthernet 1' is the name of the interface.     4. Enter the interface configuration mode to configure the new IP address.   conf t interface <interface name> ip address <new-IP> <subnet-mask> exit  After the change, the config is saved to the start-up configuration.   5. Change the Gateway (if needed) conf t ip default-gateway <new-gateway-IP-address> exit write memory 6. Finally re-start the services using the commands below. It could take anywhere between 15 - 30 minutes for the services to start completely depending on the version of code & allocated resources.   ncs start   Note: Changing the IP address directly from the Linux level  as a 'root' user can cause issues & also won't update the IP address in the Oracle config/listener files. ... View more

1. Connected Mobile Experience (CMX) 10.x is a bundle of Network Services & the current services offered on CMX 10.1 (latest as of this writing) are:       a. Location       b. Analytics       c. CMX Connect Services  2. CMX uses three databases within it.        a. Redis - For Current data       b. Cassandra - For Historical Information       c. PostGres - For Configuration data 3. It has a GUI of it's own. The underlying Operating System is based on Linux. It runs CentOS release 6.6. The Cisco Mobility Service Engine (MSE) also runs on Linux but Red Hat Enterprise Linux 5.5. 4. Commands to Stop and Start the services. cmxctl start  cmxctl stop 5. MSE 8.x licenses can be used for CMX 10.x servers 6. Licenses are not tied to UDI/VUDI of the server or to any other entity. Meaning you can copy a license file from MSE 8.x server & upload it to CMX 10.x without having to go through Cisco Licensing to re-host the files. 7. Cisco CMX 10.x is only loosely coupled with Cisco Prime Infrastructure (PI). Cisco Prime Infrastructure discovers access points and offers tools to place them on site maps/floor plans. These populated maps can be reused by Cisco CMX using an export and import process supported by Cisco Prime Infrastructure and Cisco CMX respectively. Once the maps are imported, there are no dependencies on PI by CMX. CMX is independent of PI & can’t be added to PI like the MSE. 8. Maps can be imported from Prime Infrastructure. It can be done using one of the following ways.           a. Export the maps from PI & manually import the tar bundle into CMX using the command below.               cmxctl config maps import                        cmxctl config maps import --help (will show all the available command options)                b. CMX can be configured to login directly into PI & load the maps on it's own using the command below               cmxctl config import prime     Status of the import can be monitored using ' cmxctl config import status '   9. WLC's can be added to the CMX server using one of the following ways.        a. cmxctl config controllers add                b. cmxctl config controllers import Once added, the status of the WLC can be verified using:         cmxctl config controllers show Wireless LAN Controllers report client RSSI data via NMSP. With CMX 10.x, it adds a NMSP Load Balancer in the front end for improved scalability.        10 . From the CLI, type " cmxctl debug " to collect all the logs and system parameters on the server. Logs bundle would be saved under the /root directory with a file name format of debug-cmx-<hostname>-<time-stamp>.tar.gz.  For example: debug-cmx-testserver-2015-06-02.tar.gz. Once extracted, all the logs would be under the "log" directory. The service name would be prepended with all the relevant log files. For example, all the analytics related log files would start with 'analytics' in their name & so forth. This command can be used for collecting logs & providing to Cisco TAC for troubleshooting. ... View more