Cisco Connected Mobile Experiences (CMX) Command Reference Guide, Release 10.1

CLI Commands

This chapter describes the Cisco Connected Mobile Experiences (Cisco CMX) CLI commands:

Note In the context of Cisco Connected Mobile Experiences (Cisco CMX), to access the CLI you use either console to the VM or appliance or SSH to the server when it has IP connectivity.

cmxctl Commands

This section lists the cmxctl commands that you can use to perform debug, backup, and restore functionalities:

cmxctl checklogs

To check logs and generate a report, use the cmxctl checklogs command.

cmxctl checklogs

Syntax Description

This command has no arguments or keywords.

Command Default

None

Usage Guidelines

After a report is generated, the specific log that shows the error can be viewed for additional details.

For example, /opt/cmx.var.log.cmxjobs.log.3 has 108 errors. You can use the command more /opt/cmx.var.log.cmxjobs.log.3 to view that file.

Examples

The following example shows how to check logs and generate a report:

[root@server]# cmxctl checklogs

************************************************************************

Checking /opt/cmx/var/log/cmxjobs.log.3 for errors..

/opt/cmx/var/log/cmxjobs.log.3 has 108 errors

**********************************************************************

Checking /opt/cmx/var/log/system-cron.log for errors..

/opt/cmx/var/log/system-cron.log has 0 errors

************************************************************************

Checking /opt/cmx/var/log/cmxjobs.log for errors..

/opt/cmx/var/log/cmxjobs.log has 81 errors

************************************************************************

Checking /opt/cmx/var/log/collectd.log for errors..

/opt/cmx/var/log/collectd.log has 0 errors

***********************************************************************

Checking /opt/cmx/var/log/consul.log for errors..

/opt/cmx/var/log/consul.log has 0 errors

************************************************************************

Checking /opt/cmx/var/log/qless-py-worker.log for errors..

/opt/cmx/var/log/qless-py-worker.log has 0 errors

************************************************************************

Checking /opt/cmx/var/log/influxdb.log for errors..

/opt/cmx/var/log/influxdb.log has 0 errors

************************************************************************

Checking /opt/cmx/var/log/cmxjobs.log.4 for errors..

/opt/cmx/var/log/cmxjobs.log.4 has 108 errors

***********************************************************************

cmxctl debug

To create a debug tarball in the current directory, use the cmxctl debug command.

cmxctl debug

Syntax Description

This command has no arguments or keywords.

Command Default

None

Usage Guidelines

The debug tarball that is created will be approximately 300 MB and takes at 90 seconds to complete.

Examples

The following example shows how to create a debug tarball in the current directory:

[root@server]# cmxctl debug

running locally

Dumping debug information...

[localhost] Executing task 'dump_config'

cp: cannot stat `/opt/cmx/share/upgrade.answers': No such file or directory

[localhost] Executing task 'dump_state'

running 'ps aux'

running 'ifconfig -a'

running 'cmxctl status'

running 'ulimit -a'

running 'ps -u root,postgres -o %cpu,%mem,cmd'

running 'netstat -o -n -a'

running 'df -h'

running 'ntpdate -d 172.19.28.250'

running 'consul members'

[localhost] Executing task 'dump_apis'

getting /api/config/v1/clusters

getting /api/config/v1/nodes

[localhost] Executing task 'dump_hosts'

pinging configuration.service.consul

pinging location.service.consul

pinging 6379.cache.service.consul

pinging 6380.cache.service.consul

pinging 6381.cache.service.consul

pinging database.service.consul

pinging analytics.service.consul

pinging halo.service.consul

Done.

cmxctl disable

To disable a service, use the cmxctl disable command.

cmxctl disable { analytics | agent | cache_6379 | cache_6380 | cache_6381 | cassandra | configuration | confd | consul | database | haproxy | location | matlabengine | metrics | nmsplb | influxdb | iodocs | qlesspyworker }

Syntax Description

analytics	Performs analytics on calculated location data.
agent	Manages CMX system lifecycle. starts, stops, and monitors all the services running in CMX.
cache_6379	Caches the service used by location service.
cache_6380	Caches the service used by analytics service.
cache_6381	Caches the service used by analytics service.
cassandra	Enables cassandra database service used by the location service for historical data.
configuration	Configures nodes and clusters.
confd	Internal service.
consul	Internal service.
database	Enables the database service used by analytics and configuration services.
haproxy	Enables the TCP or HTTP load balancer gateway to all service APIs.
location	Provides location service to compute location.
matlabengine	Provides access point heatmap for location service.
metrics	Collects system metrics.
nmsplb	Enables load balancer service used for distributing Network Mobility Services Protocol (NMSP) messages to location services.
influxdb	Enables database services used for storing statistics from various services.
iodocs	Enables online document service for REST API offered by various services.
qlesspyworker	Internal service.

Command Default

None

Examples

The following example shows how to disable the cassandra database service:

[root@server]# cmxctl disable cassandra

Done

The nodeagent service is currently running with PID: 31776

Stopping cassandra process...

Done

Successfully shutdown cassandra Process.

cmxctl enable

To enable a service, use the cmxctl enable command.

cmxctl enable { analytics | agent | cache_6379 | cache_6380 | cache_6381 | cassandra | configuration | confd | consul | database | haproxy | location | matlabengine | metrics | nmsplb | influxdb | iodocs | qlesspyworker }

Syntax Description

analytics	Performs analytics on calculated location data.
agent	Manages CMX system lifecycle. starts, stops, and monitors all the services running in CMX.
cache_6379	Caches the service used by location service.
cache_6380	Caches the service used by analytics service.
cache_6381	Caches the service used by analytics service.
cassandra	Enables cassandra database service used by the location service for historical data.
configuration	Configures nodes and clusters.
confd	Internal service.
consul	Internal service.
database	Enables the database service used by analytics and configuration services.
haproxy	Enables the TCP or HTTP load balancer gateway to all service APIs.
location	Provides location service to compute location.
matlabengine	Provides access point heatmap for location service.
metrics	Collects system metrics.
nmsplb	Enables load balancer service used for distributing Network Mobility Services Protocol (NMSP) messages to location services.
influxdb	Enables database services used for storing statistics from various services.
iodocs	Enables online document service for REST API offered by various services.
qlesspyworker	Internal service.

Command Default

None

Examples

The following example shows how to enable analytics service:

[root@server]# cmxctl enable analytics

The nodeagent service is not running.

Agent is not running, starting it now.

Starting nodeagent Process...

Retrying..

Done

Started nodeagent service with PID: 31027

cmxctl jobs

To configure recurring background jobs, use the cmxctl jobs command.

cmxctl jobs { cancel jobname | list | run jobname | runnow jobname}

Syntax Description

cancel	Cancels a scheduled job.
jobname	Name of the job.
list	Lists all the scheduled jobs.
run	Runs a job at a specified time.
runnow	Triggers a one-time run of the job.

Command Default

None

Examples

The following example shows how to run a background job:

[root@server]# cmxctl jobs run LocationIndexCleanup

submitted the job, verify using cmxctl jobs list.

cmxctl node

To manage node installation, use the cmxctl node command.

cmxctl node {addswap | configure | install | reinstall | sslmode { disable | enable } | uninstall | upgrade | verify }

Syntax Description

addswap	Adds a 10GB swap space to the node.
configure	Confirms node specifications.
install	Installs the Cisco Connected Mobile Experiences (Cisco CMX) for the first time.
reinstall	Reinstalls the existing installation.
sslmode disable	Disables Secure Sockets Layer (SSL).
sslmode enable	Enables SSL.
uninstall	Uninstalls the software.
upgrade	Upgrades the Cisco CMX from a URL or a file.
verify	Verifies node configuration.

Command Default

None

Examples

The following example shows how to manage node installation:

[root@server]# cmxctl node sslmode enable

enabling ssl

ssl enabled

cmxctl restart

To restart a service, use the cmxctl restart command.

cmxctl restart { analytics | agent | cache_6379 | cache_6380 | cache_6381 | cassandra | configuration | confd | consul | database | haproxy | location | matlabengine | metrics | nmsplb | influxdb | iodocs | qlesspyworker }

Syntax Description

analytics	Performs analytics on calculated location data.
agent	Manages CMX system lifecycle. starts, stops, and monitors all the services running in CMX.
cache_6379	Caches the service used by location service.
cache_6380	Caches the service used by analytics service.
cache_6381	Caches the service used by analytics service.
cassandra	Enables cassandra database service used by the location service for historical data.
configuration	Configures nodes and clusters.
confd	Internal service.
consul	Internal service.
database	Enables the database service used by analytics and configuration services.
haproxy	Enables the TCP or HTTP load balancer gateway to all service APIs.
location	Provides location service to compute location.
matlabengine	Provides access point heatmap for location service.
metrics	Collects system metrics.
nmsplb	Enables load balancer service used for distributing Network Mobility Services Protocol (NMSP) messages to location services.
influxdb	Enables database services used for storing statistics from various services.
iodocs	Enables online document service for REST API offered by various services.
qlesspyworker	Internal service.

Command Default

None

Examples

The following example shows how to restart services:

[root@server bin]# cmxctl restart database

Done

The nodeagent service is currently running with PID: 16718

Stopping postgres Process...

Successfully shutdown postgres Process.

Starting postgres Process...

Done

Started postgres service with PID: 25702

Exception while notifying CE

cmxctl start

To start a Cisco Connected Mobile Experiences (Cisco CMX) services, use the cmxctl start command.

cmxctl start { analytics | agent | cache_6379 | cache_6380 | cache_6381 | cassandra | configuration | confd | consul | database | haproxy | location | matlabengine | metrics | nmsplb | influxdb | iodocs | qlesspyworker }

Syntax Description

analytics	Performs analytics on calculated location data.
agent	Manages CMX system lifecycle. starts, stops, and monitors all the services running in CMX.
cache_6379	Caches the service used by location service.
cache_6380	Caches the service used by analytics service.
cache_6381	Caches the service used by analytics service.
cassandra	Enables cassandra database service used by the location service for historical data.
configuration	Configures nodes and clusters.
confd	Internal service.
consul	Internal service.
database	Enables the database service used by analytics and configuration services.
haproxy	Enables the TCP or HTTP load balancer gateway to all service APIs.
location	Provides location service to compute location.
matlabengine	Provides access point heatmap for location service.
metrics	Collects system metrics.
nmsplb	Enables load balancer service used for distributing Network Mobility Services Protocol (NMSP) messages to location services.
influxdb	Enables database services used for storing statistics from various services.
iodocs	Enables online document service for REST API offered by various services.
qlesspyworker	Internal service.

Command Default

None

Examples

The following example shows how to start CMX services:

[root@server]# cmxctl start consul

Done

The nodeagent service is currently running with PID: 16718

Done

The analytics service is already running with pid: 1099

Done

Exception while notifying CE

Done

The location service is already running with pid: 16005

Done

Exception while notifying CE

Done

The configuration service is already running with pid: 16165

Done

Exception while notifying CE

Done

The matlabengine service is already running with pid: 1251

Done

Exception while notifying CE

Done

The nmsplb service is already running with pid: 1377

Done

Exception while notifying CE

cmxctl status

To view the status of one or all services, use the cmxctl status command.

Syntax Description

analytics	Performs analytics on calculated location data.
agent	Manages CMX system lifecycle. starts, stops, and monitors all the services running in CMX.
cache_6379	Caches the service used by location service.
cache_6380	Caches the service used by analytics service.
cache_6381	Caches the service used by analytics service.
cassandra	Enables cassandra database service used by the location service for historical data.
configuration	Configures nodes and clusters.
confd	Internal service.
consul	Internal service.
database	Enables the database service used by analytics and configuration services.
haproxy	Enables the TCP or HTTP load balancer gateway to all service APIs.
location	Provides location service to compute location.
matlabengine	Provides access point heatmap for location service.
metrics	Collects system metrics.
nmsplb	Enables load balancer service used for distributing Network Mobility Services Protocol (NMSP) messages to location services.
influxdb	Enables database services used for storing statistics from various services.
iodocs	Enables online document service for REST API offered by various services.
qlesspyworker	Internal service.

Command Default

None

Examples

The following example shows how to display the status for the consul service:

[root@server]# cmxctl status consul

Done

The nodeagent service is currently running with PID: 16718

+--------------+---------------+---------+----------------+

+--------------+---------------+---------+----------------+

+--------------+---------------+---------+----------------+

+--------------+---------------+---------+----------------+

+--------------+---------------+---------+----------------+

+--------------+---------------+---------+----------------+

+--------------+---------------+---------+----------------+

+--------------+---------------+---------+----------------+

+--------------+---------------+---------+----------------+

+--------------+---------------+---------+----------------+

+--------------+---------------+---------+----------------+

+--------------+---------------+---------+----------------+

+--------------+---------------+---------+----------------+

+--------------+---------------+---------+----------------+

+--------------+---------------+---------+----------------+

+--------------+---------------+---------+----------------+

+--------------+---------------+---------+----------------+

+--------------+---------------+---------+----------------+

+--------------+---------------+---------+----------------+

cmxctl stop

To shutdown a service, use the cmxctl stop command.

cmxctl stop { analytics | agent | cache_6379 | cache_6380 | cache_6381 | cassandra | configuration | confd | consul | database | haproxy | location | matlabengine | metrics | nmsplb | influxdb | iodocs | qlesspyworker }

Syntax Description

analytics	Performs analytics on calculated location data.
agent	Manages CMX system lifecycle. starts, stops, and monitors all the services running in CMX.
cache_6379	Caches the service used by location service.
cache_6380	Caches the service used by analytics service.
cache_6381	Caches the service used by analytics service.
cassandra	Enables cassandra database service used by the location service for historical data.
configuration	Configures nodes and clusters.
confd	Internal service.
consul	Internal service.
database	Enables the database service used by analytics and configuration services.
haproxy	Enables the TCP or HTTP load balancer gateway to all service APIs.
location	Provides location service to compute location.
matlabengine	Provides access point heatmap for location service.
metrics	Collects system metrics.
nmsplb	Enables load balancer service used for distributing Network Mobility Services Protocol (NMSP) messages to location services.
influxdb	Enables database services used for storing statistics from various services.
iodocs	Enables online document service for REST API offered by various services.
qlesspyworker	Internal service.

Command Default

The services are running.

Examples

The following example shows how to stop the analytics service:

[root@server]# cmxctl stop analytics

Done

The nodeagent service is currently running with PID: 16987

Stopping analytics Process...

Service analytics with pid: 19095

Retrying..

Done

Successfully shutdown analytics Process.

cmxctl version

To know the Cisco Connected Mobile Experiences (Cisco CMX) RC version, use the cmxctl version command.

cmxctl version

Syntax Description

This command has no arguments or keywords.

Command Default

None

Examples

The following example shows how to display version information for Cisco CMX:

[root@server]# cmxctl version

Build Version : 10.1.0-27

Build Time : 2015-05-05 03:06:45.437430

----------------------------------------------------------------------

Name : cmx-ng-container

Commit Count : 17

Short Hash : bf20ec1

----------------------------------------------------------------------

Name : cmx-ng-location

Commit Count : 5

Short Hash : efc84fa

----------------------------------------------------------------------

Name : cmx-ng-ui

Commit Count : 5

Short Hash : d793df7

----------------------------------------------------------------------

Name : cmx-ova

Build Time : Fri Feb 20 06:34:38 UTC 2015

----------------------------------------------------------------------

cmxctl config Commands

This section lists the cmxctl config commands:

cmxctl config backup

To back up a node, use the cmxctl config backup command.

cmxctl config backup

Syntax Description

This command has no arguments or keywords.

Command Default

None

Examples

The following example shows how to back up a node:

[root@server]# cmxctl config backup

Please enter the path for backup file [/tmp]:

[17:43:50] Preparing for backup...

[17:43:50] Backup Database...

[17:43:51] Backup Cache...

[17:43:51] Backup Cassandra...

[17:43:53] Backup InfluxDb...

[17:43:53] Backup Consul...

[17:43:53] Backup Floormaps...

[17:43:53] Backup node configuration...

[17:43:59] Creating tar file..

[17:43:59] Done Backup. Created backup file /tmp/cmx_backup_cmx-vmdev117_2015_03_10_17_43.tar.gz

?]0;root@cmx-vmdev117:~[root@cmx-vmdev117 ~]# cmxctl config restore

?[?1034hPlease enter the backup file path: /tmp/cmx_backup_cmx-vmdev117_2015_03_10_17_43.tar.gz

[17:44:12] Preparing for restore...

[17:44:12] Untarring backup file...

[17:44:13] Stopping all services...

[17:44:16] Restoring Database...

Restarting database...

[17:44:26] Restoring Cache...

Stopping cache_6379...

Restarting cache_6379...

Stopping cache_6381...

Restarting cache_6381...

Stopping cache_6380...

Restarting cache_6380...

[17:44:55] Restoring Cassandra...

Stopping Cassandra...

Restarting Cassandra...

...............

[17:45:19] Restoring Influxdb...

[17:45:19] Restoring consul...

[17:45:19] Restoring floormaps...

[17:45:19] Running Post Restore Tasks...

[17:45:19] Migrating Schemas...

[17:45:19] Migrating Cassandra schemas...

[17:45:20] Restarting all services...

[17:45:23] Done

cmxctl config controllers

To manage the Cisco Wireless Controllers (Cisco WLC), use the cmxctl config controllers command.

cmxctl config controllers { add | delete | import | show}

Syntax Description

add	Adds a Cisco WLC.
delete	Deletes a Cisco WLC.
import	Imports a Cisco WLC from PI by providing PI credentials or by placing an exported PI MAP file in the /opt directory of the CMX server and providing the path to exported map file.
show	Shows information pertaining to a Cisco WLC.

Command Default

None

Usage Guidelines

After a controller is added, the message “controller added successfully” may be shown. Note that this refers only to the correct parsing of the command. You should issue a cmxctl controllers show command to ensure that the controller is not active.

Examples

The following example shows how to display the Cisco WLC information:

[root@server]# cmxctl config controllers show

+--------------+------+------------+----------------+------+--------+

+--------------+------+------------+----------------+------+--------+

| 30.30.30.65 | WLC | 8.0.72.141 | - | No | ACTIVE |

+--------------+------+------------+----------------+------+--------+

| 30.30.30.44 | WLC | 8.0.72.141 | - | No | ACTIVE |

+--------------+------+------------+----------------+------+--------+

| 30.30.30.46 | WLC | 8.0.72.141 | - | No | ACTIVE |

+--------------+------+------------+----------------+------+--------+

| 30.30.30.70 | WLC | 8.0.72.141 | - | No | ACTIVE |

+--------------+------+------------+----------------+------+--------+

| 30.30.30.93 | WLC | 8.0.72.141 | - | No | ACTIVE |

+--------------+------+------------+----------------+------+--------+

| 30.30.30.97 | WLC | 8.0.72.141 | - | No | ACTIVE |

+--------------+------+------------+----------------+------+--------+

| 30.30.30.35 | WLC | 8.0.72.141 | - | No | ACTIVE |

+--------------+------+------------+----------------+------+--------+

| 30.30.30.58 | WLC | 8.0.72.141 | - | No | ACTIVE |

+--------------+------+------------+----------------+------+--------+

| 30.30.30.82 | WLC | 8.0.72.141 | - | No | ACTIVE |

+--------------+------+------------+----------------+------+--------+

| 30.30.30.84 | WLC | 8.0.72.141 | - | No | ACTIVE |

+--------------+------+------------+----------------+------+--------+

| 30.30.30.53 | WLC | 8.0.72.141 | - | No | ACTIVE |

+--------------+------+------------+----------------+------+--------+

cmxctl config import

To imports maps and Cisco Wireless Controllers (Cisco WLC) from Cisco Prime Infrastructure, use the cmxctl config import command.

cmxctl config import {prime | status}

Syntax Description

prime	Imports maps from the Cisco Prime Infrastructure
status	Shows import status.

Command Default

None

Examples

The following example shows how to import maps and Cisco WLC from Prime Infrastructure:

[root@server]# cmxctl config import prime

Please enter PI ip address: x.x.x.x

Please enter PI username [root]: root

Please enter PI password [Public123]:

Import successfully started from PI x.x.x.x. Check import status using cmxctl config import status.

cmxctl config maps

To import and manage maps, use the cmxctl config maps command.

cmxctl config maps {address | delete | import}

Syntax Description

address	Imports addresses for the maps.
delete	Deletes the campus map.
import	Imports map from the Cisco Prime Infrastructure.

Command Default

None.

Examples

The following example shows how to import and manage maps:

[root@server]# cmxctl config maps import

Please specify import type [PI / FILE] [FILE]: PI

Please enter PI ip address: x.x.x.x

Please enter PI username [root]: root

Please enter PI password [Public123]:

Import successfully started from PI 173.37.206.3. Check import status using cmxctl config import status.

cmxctl config reload

To force the generation of config files, use the cmxctl config reload command.

cmxctl config reload

Syntax Description

This command has no arguments or keywords.

Command Default

None

Examples

The following example shows how to forcefully generate configuration files:

[root@server]# cmxctl config reload

2015-03-10T17:45:50Z cmx-vmdev117 -verbose[17174]: WARNING Skipping confd config file.

2015-03-10T17:45:50Z cmx-vmdev117 -verbose[17174]: INFO Target config /opt/cmx/etc/analytics.conf in sync

2015-03-10T17:45:50Z cmx-vmdev117 -verbose[17174]: INFO Target config /opt/cmx/etc/cassandra/cassandra-env.sh in sync

2015-03-10T17:45:50Z cmx-vmdev117 -verbose[17174]: INFO Target config /opt/cmx/etc/cassandra/cassandra.yaml in sync

2015-03-10T17:45:50Z cmx-vmdev117 -verbose[17174]: INFO Target config /opt/cmx/etc/collectd.conf in sync

2015-03-10T17:45:50Z cmx-vmdev117 -verbose[17174]: INFO Target config /opt/cmx/etc/configuration.conf in sync

2015-03-10T17:45:50Z cmx-vmdev117 -verbose[17174]: INFO Target config /opt/cmx/etc/connect.conf in sync

2015-03-10T17:45:50Z cmx-vmdev117 -verbose[17174]: INFO Target config /opt/cmx/etc/halo.conf in sync

2015-03-10T17:45:50Z cmx-vmdev117 -verbose[17174]: INFO Target config /opt/cmx/etc/haproxy.cfg in sync

2015-03-10T17:45:50Z cmx-vmdev117 -verbose[17174]: INFO Target config /opt/cmx/etc/influxdb.conf in sync

2015-03-10T17:45:50Z cmx-vmdev117 -verbose[17174]: INFO Target config /opt/cmx/etc/location.conf in sync

2015-03-10T17:45:50Z cmx-vmdev117 -verbose[17174]: INFO Target config /opt/cmx/etc/matlabengine.conf in sync

2015-03-10T17:45:50Z cmx-vmdev117 -verbose[17174]: INFO Target config /opt/cmx/etc/nmsplb.conf in sync

2015-03-10T17:45:50Z cmx-vmdev117 -verbose[17174]: INFO Target config /opt/cmx/etc/nmspproxy.conf in sync

2015-03-10T17:45:50Z cmx-vmdev117 -verbose[17174]: INFO Target config /opt/cmx/etc/postgresql.conf in sync

2015-03-10T17:45:50Z cmx-vmdev117 -verbose[17174]: INFO Target config /opt/cmx/etc/redis_6379.conf in sync

2015-03-10T17:45:50Z cmx-vmdev117 -verbose[17174]: INFO Target config /opt/cmx/etc/redis_6380.conf in sync

2015-03-10T17:45:50Z cmx-vmdev117 -verbose[17174]: INFO Target config /opt/cmx/etc/redis_6381.conf in sync

2015-03-10T17:45:50Z cmx-vmdev117 -verbose[17174]: ERROR template: redis.template.conf:15:20: executing "redis.template.conf" at <getv ($tag | printf...>: error calling getv: key does not exist

cmxctl config restore

To restore a node, use the cmxctl config restore command.

cmxctl config restore

Syntax Description

This command has no arguments or keywords.

Command Default

None.

Examples

The following example shows how to restore a node:

[root@server]# cmxctl config restore

Please enter the backup file path: /tmp/cmx_backup_cmx-vmdev117_2015_03_10_17_43.tar.gz

[17:44:12] Preparing for restore...

[17:44:12] Untarring backup file...

[17:44:13] Stopping all services...

[17:44:16] Restoring Database...

Restarting database...

[17:44:26] Restoring Cache...

Stopping cache_6379...

Restarting cache_6379...

Stopping cache_6381...

Restarting cache_6381...

Stopping cache_6380...

Restarting cache_6380...

[17:44:55] Restoring Cassandra...

Stopping Cassandra...

Restarting Cassandra...

...............

[17:45:19] Restoring Influxdb...

[17:45:19] Restoring consul...

[17:45:19] Restoring floormaps...

[17:45:19] Running Post Restore Tasks...

[17:45:19] Migrating Schemas...

[17:45:19] Migrating Cassandra schemas...

[17:45:20] Restarting all services...

[17:45:23] Done

cmxctl config verify

To verify the Cisco CMX installation and configuration, use the cmxctl config verify command.

cmxctl config verify

Syntax Description

This command has no arguments or keywords.

Command Default

None

Examples

The following example shows how to verify the Cisco CMX installation and configuration:

[root@server]# cmxctl config verify

Verifying node configuration...

NetworkManager: unrecognized service

Consul v0.4.1

Consul Protocol: 2 (Understands back to: 1)

confd 0.6.0

+-----------------+--------------------------------+------------+---------------------------+

+=================+================================+============+===========================+