Cisco CMX Cloud Proxy Configuration Guide

Transcription

1 Cisco CMX Cloud Proxy Configuration Guide Overview Welcome to Cisco Connected Mobility Experiences (CMX) in the cloud. CMX Cloud is essentially running the CMX software in a Cisco supported and maintained datacenter that is accessible and delivered as a software subscription to the customer. Both the software and support are included in the service offering. To address the needs of businesses with smaller sites and wireless deployments not designed for location accuracy, we ve developed Presence Analytics, which provides customer insights for customer facing enterprises for example in Retail, Hospitality, Education, Sports and Entertainment, Healthcare, Airports etc. CMX presence analytics is a comprehensive analytics and engagement platform that detects Presence of visitors via their mobile devices using Cisco access points. It eliminates the need for maps and thus enabling faster deployment, easy to use and quicker insights. Various verticals such as Retail, Mall, Hospitality, Education, Healthcare and Airports can offer free Wi- Fi access. CMX Connect enables seamless, customizable, location aware guest captive portal that easily on- boards guests and provides them Internet connectivity. CMX Cloud in the initial phase is available as following packages: Connect Only Connect with Presence Analytics

2 On Prem CMX Detect Connect Engage WLC or NGWC NMSP Proxy Presence and location detection Visibility (Wi-Fi, BLE, video) Easy Wi-Fi login, custom or social Zone-based, custom splash pages Analytics App-based mobile engagement Context-aware invenue experiences CMX Cloud Presence and/or Connect Tenants Access Point 2010 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 4 Cisco CMX Cloud Solution Compatibility Matrix CMX Cloud Proxy Controller Access Points Prime Version: 1.0 WLC: 7.6 or later NGWC: or later All Lightweight, Outdoor and Industrial APs 1.4, or later CMX Cloud Deployment Matrix Service Type Account Signup Setup CMX Cloud Proxy Connect Only Yes Optional. With CMX Cloud Proxy, bandwidth usage statistics information would be displayed on the Connect dashboard. Setup CMX Configure Connect

3 Connect & Presence Analytics Yes Mandatory for Presence Analytics. With CMX Cloud Proxy, bandwidth usage statistics information would be displayed on the Connect dashboard. Configure Connect & Presence Analytics Minimum requirements to get your CMX Cloud deployment Below are the minimum requirements to get your CMX Cloud deployment going: 1. Refer to CMX Cloud Deployment topology. 2. Verify your device versions using Cisco CMX Cloud Solution Compatibility Matrix. 3. Recommended browser is Chrome 45 or later. 4. Signup to for 60 day trial. Or go to Cisco Commerce Workspace (CCW) and purchase license for your choice of CMX Cloud service. Refer to CMX Cloud Ordering information. 5. Install CMX Cloud Proxy on VM using VMware ESXi 5.1 or later. Refer to CMX Cloud Deployment Matrix. 6. Start using Connect or Connect & Presence Analytics as per your configuration. 7. Enjoy the Cool CMX Cloud experience! CMX Cloud Proxy Configuration The proxy is meant to bridge on- premises controllers with cloud hosted CMX. User gets a token in e- mail when signed up on cmxcisco.com

4 Download the CMX Cloud Proxy from the cisco.com Download Software page.

5 In the help page the VM requirements are mentioned and make sure it has the required hardware support.it may be noted that although it is recommended that the CMX Cloud Proxy runs with 4vCPUs, assigning 2 vcpus does not entail any degradation of performance (upto 80 Million messages/day). Use vsphere 5.1 or later for installing ova. Go to File > Deploy OVF Template.

6 Click on Next twice. Click Accept to continue on End User License Agreement Screen. Give a name for your instance in this case it is cmxproxy and click Next.

7 Select Thick or Thin provisioned disk and click Next. (Default is Thick provisioned) Select Finish to deploy the ova. Once the deployment is finished Power On the instance you created. Click console Tab in vsphere client.

8 Login as shown in the output with user as cmxadmin and password as cisco. Press any key to continue as show in the output, you will be prompted to set for passwords for root and cmxadmin. Choose a password with 8 to 20 alphanumeric characters for both root and cmxadmin. You will be prompted for Network Setup screen.

9 Press Enter to do the Device Configuration. Enter the network details in the following screens according to the network.

10 Press DNS Configuration and enter the hostname. Hostname is the RFC compliant name of the CMX Cloud Proxy VM. Press Save&Quit button.

11 Wait for a prompt to enter NTP server details. Once configuration is complete, the setup will install CMX Cloud Proxy. Issue cmxctl status to know the status of process running and you should see something like below.

12 Once CMX Cloud Proxy has been installed, you can add a member using proxyctl members add. Follow the prompts to add your member. Enter the token from the e- mail you have received from CMX Cloud. Enter the member services as CONNECT or PRESENCE_CONNECT. ALL option would configure both LOCATION & PRESENCE.

13 Check the status of the member you added. Now add a controller in the CMX Cloud Proxy. Issue cmxctl config controllers add and follow the instructions. Create a new SNMP Read- Write string or use default Privare Read- Write string on WLC. The default Public SNMP string won t work.

14 Issue proxyctl status command to know whether the site is reachable. CMX Cloud Proxy CLI Following are the CLI supported on CMX Cloud Proxy to see the current status and debug any proxy related issue. cmxctl - - help Usage: cmxctl [OPTIONS] COMMAND [ARGS]... Options: - v, - - verbose Verbose output. - q, - - quiet Suppress all output. - - help Show this message and exit. Commands: checklogs check the logs and generate a report config Configure CMX. debug Create a debug tarball in the current dir. disable Disable an enabled service.

15 dump Create a config tarball in the current dir. enable Enable a disabled service. heterarchy Verify/repair heterarchy. jobs Configure recurring background jobs. leave Leave the cmx cluster. metrics metrics for cmx node Manage SSL. reset Reset CMX Password. restart Restart services. stack generate the jstack for a java service start Start services. status Displays the status for one or all services. stop Shut down services. users Configure cmx users through the cli. version Print CMX version info and exit. [cmxadmin@localhost ~]$ proxyctl - - help Usage: proxyctl [OPTIONS] COMMAND [ARGS]... Options: - - help Show this message and exit. Commands: install Install CMX nmspproxy for the first time members Add/Delete/Show members start Starts all CMX nmspproxy services status Get controller statistics stop Stops all CMX nmspproxy services uninstall Uninstall the CMX nmspproxy software upgrade Upgrade CMX nmspproxy after new RPM install verify Verify node configuration [cmxadmin@localhost ~]$ CMX Cloud Proxy Troubleshooting FAQ Incorrect proxy installation would give following error. In this case, reboot, login as cmxadmin, password as cisco and re- install proxy.

16 proxyctl status displays CLIENT INVALID Unable to determine whether the service is dead or alive. Do cmxctl status to check if the service is running. proxy- 125 nmspproxy]$ cmxctl status Done The agent service is currently running with PID: Host Service Status Uptime (HH:mm) cmx- proxy- 125 Metrics Running 0 days, 17: cmx- proxy- 125 Nmspproxy Running 0 days, 16: [cmxadmin@cmx- proxy- 125 nmspproxy]$

17 proxyctl status show INACTIVE/INVALID controllers verify that: 1. the controller is reachable 2. the controller's time is same or ahead of MSE time 3. the SNMP port(161) is open on the controller 4. the NMSP port(16113) is open on the controller 5. the controller version is correct 6. Check for any exceptions in /opt/cmx/var/log/nmspproxy/error.log 7. the correct key hash is pushed across to the controller by referring the following: MAC Address 00:0c:29:a1:4d: SHA1 Key f34b a5fd d SHA2 Key f1ae c96aae87701d61dc4e35ad2dcb22d1111ca802e [cmxadmin@localhost ~]$ cmxctl config controllers show IP Address Type Version SHA2 Status WLC Yes INACTIVE

18 WLC Yes ACTIVE WLC Yes INACTIVE WLC Yes ACTIVE WLC Yes ACTIVE WLC Yes INACTIVE [cmxadmin@localhost ~]$ proxyctl members show Member Services Access Token Status 1m 5m 15m Last Activity wnbu- tme.cmxcisco.com PRESENCE,LOCATION 718eb331b4cb146d5f8cecc3f0324e93 REACHABLE /27/ :25: [cmxadmin@localhost ~]$ netstat grep 161 tcp 0 0 localhost.localdomain:55657 ::ffff: :16113 ESTABLISHED tcp 0 0 localhost.localdomain:49119 ::ffff: :16113 ESTABLISHED tcp 0 0 localhost.localdomain:59392 ::ffff: :16113 ESTABLISHED [cmxadmin@localhost ~]$ ====Controller CLI================================== (SJC_14_LWAPP1) >config paging disable (SJC_14_LWAPP1) >show auth- list Authorize MIC APs against Auth- list or AAA... disabled Authorize LSC APs against Auth- List... disabled APs Allowed to Join AP with Manufacturing Installed Certificate... yes AP with Self- Signed Certificate... no AP with Locally Significant Certificate... no Mac Addr Cert Type Key Hash :0c:29:04:67:74 LBS- SSC c0ca4babefe74292aeef019a9c0262d8b

19 00:0c:29:1a:df:8c LBS- SSC 6ad78d3fa6547b6db438f38dc776ca1332c5d124 00:0c:29:21:b2:ad LBS- SSC- SHA256 a84843ad2d5eb f0e48d7e24b90eef1ddf8e0e a2710ac5 97a71 00:0c:29:5b:a9:5e LBS- SSC- SHA a924e21c4a84e50f56f17e8b32a6710e21bab8ff26994cc05b2a2d d95d5 00:0c:29:65:41:be LBS- SSC- SHA256 7f4d5d a8867fb2ce336703dba2e51d9c326382fd88e2a7c785a5 21c53 00:0c:29:84:89:22 LBS- SSC- SHA256 16b5a3fca7104f206cb2c0e9dfb1d959e9b9a88087d79d2f1fb :0c:29:a1:4d:90 LBS- SSC- SHA f1ae c96aae87701d61dc4e35ad2dcb22d1111 ca802e 00:0c:29:b2:cb:76 LBS- SSC- SHA ee3a29ffe719f1e9b532c301823e4e92b642cd3dae7b777cbf4ebc103 7cc9 00:0c:29:c5:2a:86 LBS- SSC- SHA aad65ec08442db9e15a706d4c134948a6522c de2bc6e2 e0c80b 00:16:36:29:08:c4 LBS- SSC 87be053fed0d6d0ee94ebcfce b 00:50:56:a1:0a:af LBS- SSC- SHA256 a84e93d6c74db0cf4e05ac2c2e91245ce1f666aa d9df04ee9398e 26a3 00:50:56:a3:24:c2 LBS- SSC- SHA f7d98240bff8f92fc72b3fe4e56be9c08122a9fa8c0bb0e7a9770b1c1 5e8 00:50:56:a3:f7:03 LBS- SSC- SHA256 8da85f df5732b6b9bfedd491ce5a33f1c9e cdf5b c7 (SJC_14_LWAPP1) >config auth- list add sha256- lbs- ssc 00:0c:29:a1:4d: f1ae c96aae87701d61dc4e35ad2dcb22d1111ca802e (SJC_14_LWAPP1) >save config proxyctl controller status displays CLIENT INVALID

20 verify that: 1. the controller is reachable 2. the controller's time is same or ahead of MSE time 3. check NTP server configured on proxy by doing cat /etc/ntp.conf proxyctl member status displays unexpected error proxy- 125 ~]$ proxyctl members add Please enter the member host address: 32txrs.cmxdemo.com Please enter the member access token: eyjhbgcioijiuzi1niisinr5cci6ikpxvcj 9.eyJ0ZW5hbnRJZCI6IjMydHhycyJ9.yPS1pmPa0KhkN9LWd4iO6HRhO41NVcVg5KX mbrez1w8 Please enter the member services [LOCATION, PRESENCE, CONNECT, PRESENCE_CONNECT,ALL] [LOCATION]: PRESENCE_CONNECT 32txrs.cmxdemo.com could not be added proxy- 125 ~]$ proxyctl status System Status Done The agent service is currently running with PID: Host Service Status Uptime (HH:mm)

21 cmx- proxy- 125 Metrics Running 0 days, 03: cmx- proxy- 125 Nmspproxy Running 0 days, 01: Member Status Unexpected error. Check the logs at /opt/cmx/var/log/agent/cmxd.log Controllers Status Controller Status Type SHA2 Version 1m 5m 15m Last Activity CLIENT ACTIVE WLC True /09/ :24: verify that o /opt/cmx/var/log/agent/cmxd.log does not have any exception proxyctl member status displays UNREACHABLE [cmxadmin@cmx- proxy- 125 ~]$ proxyctl members add Please enter the member host address: eaaesc.cmxdemo.com Please enter the member access token: eyjhbgcioijiuzi1niisinr5cci6ikpxvcj9.eyj0zw5hbnrjzci6imvhywvzyyj9.ekul1l amp7oq1gqxhqwiy_arx9fxc_bhdfyp1xk6lfc Please enter the member services [LOCATION, PRESENCE, CONNECT, PRESENCE_CONNECT,ALL] [LOCATION]: PRESENCE_CONNECT eaaesc.cmxdemo.com added [cmxadmin@cmx- proxy- 125 ~]$ proxyctl members show Member Services Access Token Status 1m 5m 15m Last Activity eaaesc.cmxdemo.com CONNECT,PRESENCE eyjhbgcioijiuzi1niisinr5cci6ikpxvcj9.eyj0zw5hbnrjzci6imvhywvzyyj9.ekul1l amp7oq1gqxhqwiy_arx9fxc_bhdfyp1xk6lfc NOT REACHABLE /31/ :00:00

22 [cmxadmin@cmx- proxy- 125 ~]$ proxyctl status System Status Done The agent service is currently running with PID: Host Service Status Uptime (HH:mm) cmx- proxy- 125 Metrics Running 0 days, 03: cmx- proxy- 125 Nmspproxy Running 0 days, 01: Member Status Member Services Access Token Status 1m 5m 15m Last Activity eaaesc.cmxdemo.com CONNECT,PRESENCE eyjhbgcioijiuzi1niisinr5cci6ikpxvcj9.eyj0zw5hbnrjzci6imvhywvzyyj9.ekul1l amp7oq1gqxhqwiy_arx9fxc_bhdfyp1xk6lfc NOT REACHABLE /31/ :00: Controllers Status Controller Status Type SHA2 Version 1m 5m 15m Last Activity CLIENT ACTIVE WLC True /09/ :17: verify that There is a connectivity between proxy and member (cloud instance) o /opt/cmx/var/log/nmspproxy/error.log does not have any exception

23 Proxy is unable to send the data verify that If /opt/cmx/var/log/nmspproxy/error.log shows following error message. meaning token entered is bad T13:23:13,274 [Thread- 40] container ERROR com.cisco.mse.nmspproxy.websockets.configurationmessagesender - Unable to send stats to XXX.cmxcisco.com with response code 401