Examples

The following example shows how to export Cisco CMX data from Cassandra to a CSV file:

[cmxadmin]$ /opt/cmx/bin/cassandraexport --date 2017/06/14

Data exported into the file /tmp/CassandraExport_201706150220-02.csv

Examples

The following example shows how to the schemen integrity for cassandra and postgres database:

[root@server]# cmxctl checkdb cassandra

Schema passed analytics
Schema passed loc
Schema passed mse
Cassandra passed schema validation

[root@server]# cmxctl checkdb postgres
Schema passed analytics
Schema passed loc
Schema passed mse
Postgres passed schema validation

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
***********************************************************************

Examples

The following example shows how to display security parameters for CMX:

[root@server]# cmxctl config auth show

Enable strong password : yes
Minimum password length : 10
Unsuccessful login attempts before account lock : 3
Session timeout in minutes : 20

Examples

The following example shows how to get the authorization information:

[cmxadmin@cmx-nortech ~]$ cmxctl config authinfo get
+-------------------+------------------------------------------+------------------------------------------------------------------+
| macAddress        | keyHashString                            | sha2KeyHashString                                                |
+-------------------+------------------------------------------+------------------------------------------------------------------+
| 00:0c:29:07:36:84 | e743ac54029ce36282c582f04bfb45ec187c824d | 560d69882adb90dda10227651da0c6a2850999620b50f83ed0d157fb87d1a920 |
+-------------------+------------------------------------------+------------------------------------------------------------------+

Examples

The following example shows how to create the login banner “CentOS release 7.0.”

hostname# cmxctl config banner edit

Current Login Banner = []
Enter text to be displayed as login banner. Enter a single period on a line to terminate.
CentOS release 7.0
.
Stopping sshd:                                             [  OK  ]
Starting sshd:                                             [  OK  ]
 

login as: cmxadmin
CentOS release 7.0
cmxadmin@168.172.1.20’s password:
Last login: 6/5/2018 1:10 PM

When you log into CMX from a browser, the banner message appears in a pop-up window on the login page.

Examples

The following example shows how to clear out old certificates from the /opt/cmx/srv/certs directory.

[root@server]# cmxctl config certs clear

Clear Certificates
 

The following example shows how to select key type ECDSA:

[root@server]# cmxctl config certs keytype

Please enter key type [RSA / ECDSA] [RSA]:ECDSA
Keytype is set to ECDSA.
 

The following example shows how to generate new self-signed certification files in the /opt/cmx/srv/certs directory using an RSA key:

[root@server]# cmxctl config certs installnewcerts

Keytype is RSA, generating RSA key with length  4096
Generating RSA private key, 4096 bit long modulus
.......................
...............................
e is 65537 (0x10001)
Generating RSA private key, 4096 bit long modulus
..............................................
..........................
e is 65537 (0x10001)
Signature ok
subject=/C=US/ST=CA/L=San Jose/O=MSE/CN=ServerCrt
Getting CA Private Key
Certificates are valid.
 

The following example shows how to create a new certificate signing request (CSR):

[root@server]# cmxctl config certs createcsr

Keytype is RSA, so generating RSA key with length  4096
Generating RSA private key, 4096 bit long modulus
...........
........
e is 65537 (0x10001)
You are about to be asked to enter information that will be incorporated
into your certificate request.
What you are about to enter is what is called a Distinguished Name or a DN.
There are quite a few fields but you can leave some blank
For some fields there will be a default value,
If you enter '.', the field will be left blank.
-----
Country Name (2 letter code) [AU]: US
State or Province Name (full name) [Some-State]: CA
Locality Name (eg, city) []: San Jose
Organization Name (eg, company) [Internet Widgits Pty Ltd]: Yourco, Inc.
Organizational Unit Name (eg, section) []: Gulag 10
Common Name (e.g. server FQDN or YOUR name) []: Wireless
Email Address []:email@yourco.com

Please enter the following 'extra' attributes
to be sent with your certificate request
A challenge password []:
An optional company name []:
The CSR is in: /opt/cmx/srv/certs
The Private key is in: /opt/cmx/srv/certs

CSR created successfully.
 

Sometimes two or more files need to be combined (or concatenated) before you can import the resulting file. For example, you may have intermediate CA certificates as well as root certs. This example shows how to concatenate the files root-ca-cert.pem and intermediate-ca-cert.pem, and import the resulting file to CMX.

1. Concatenate the files:

   [root@server]# cat root-ca-cert.pem intermediate-ca-cert.pem > ca-chain.pem

2. Import the new file ca-chain.pem :

   [root@server]# cmxctl config certs importcacerts ca-chain.pem

   Importing CA certificate.....
   Enter Export Password: caexportpw
   Verifying - Enter Export Password: caexportpw
   Enter Import Password: caimportpw
   Import CA Certificate successful
   0
    

The importservercert command requires you to combine the server key and the server certificate into one pem file. The following example shows how to combine the files and import the resulting file.

Note	Import CA chain certificates before importing the server certificate.

1. Concatenate the files:

   [root@server]# cat cmxserverkey.pem signed-cert.pem > server-key-cert.pem

2. Import the new file server-key-cert.pem :

   [root@server]# cmxctl config certs importservercerts server-key-cert.pem

   Importing Server certificate.....
   
   Successfully transferred the file
    

   At the prompts, provide an export and import password specific to this command.

   
   Enter Export Password: svrexportpw
   Verifying - Enter Export Password: svrexportpw
   Enter Import Password: svrimportpw
   Private key present in the file: /home/cmxadmin/server-key-cert.pem
   Enter Import Password: svrimportpw
   verifying SAN
   Validation is Successful
   Import Server Certificate successful
   No CRL found
   Restart CMX services for the changes to take effect.
   0
    

The following example shows how to display the details of the server certificate and all CA chain certificates:

[root@server]# cmxctl config certs show

Certificate details

*************************  Certificate Listing  ********************
====================================================================
***********************  CA Certificate(s)  ************************
====================================================================
Certificate:
    Data:
        Version: 3 (0x2)
        Serial Number:
            b6:c0:fc:05:f6:27:45:1a
    Signature Algorithm: sha256WithRSAEncryption
        Issuer: C=US, ST=CA, L=San Jose, O=MSE, CN=RootCA
        Validity
            Not Before: Jan 19 05:17:33 2018 GMT
            Not After : Jan 18 05:17:33 2021 GMT
        Subject: C=US, ST=CA, L=San Jose, O=MSE, CN=RootCA
        Subject Public Key Info:
            Public Key Algorithm: rsaEncryption
                Public-Key: (4096 bit)
                Modulus:
                    00:ba:f2:2b:cd:87:90:23:f0:64:f5:83:d5:f2:90:
                    43:1a:16:36:c9:67:1a:82:f1:8f:6b:eb:1c:47:f1:
                    c4:fd:bf:55:98:ab:06:c0:90:dc:d7:13:1f:d3:2f:
                    12:e8:f2:74:66:65:7c:49:12:72:0c:27:9c:2e:84:
                    7e:29:a8:b6:18:62:5f:c2:97:a4:1c:e7:45:a2:cb:
                    f3:35:f3:64:15:e5:f0:27:6f:f1:07:61:41:9b:4c:
                    96:b3:56:d4:28:a4:85:90:86:52:4c:04:bc:da:38:
                    cc:f8:05:5b:3e:5c:03:b4:59:ec:8b:c9:5d:eb:61:
                    76:ba:20:3f:64:6c:25:5d:50:1e:85:37:ad:09:b2:
                    4a:fa:58:15:89:91:d9:5f:b8:9d:dd:64:31:8b:a4:
                    df:99:ff:ae:72:19:f8:a3:93:81:b9:4e:07:74:74:
                    95:b6:42:7b:5a:7d:38:92:4a:f4:86:5a:54:66:f0:
                    c1:fe:38:31:df:24:1c:40:94:36:67:8b:b3:56:93:
                    62:26:29:c2:cd:7f:7d:66:9d:f1:78:54:88:4f:6c:
                    b3:b7:80:54:05:03:09:c9:f9:14:65:8a:21:00:b5:
 

Examples

The following example shows how to delete all CMX connect clients:

[root@server]# cmxctl config connect deleteClientsAll 
Successfully Deleted Connect Data, deleted 1 clients

Examples

Starting from Cisco CMX Release 10.3.1, you can specify SNMP settings when you use the cmxctl config controllers add command. For example:

[root@server]# cmxctl config controllers add
Please enter controller type [WLC / NGWC] [WLC]: WLC
Please enter controller ip: 0.0.0.0
Please enter the controller version [Optional]:
Please enter controller SNMP version [v1 / v2c / v3] [v2c]: v2c
Please enter controller SNMP write community [private]:
....................................................................
Controller Added 0.0.0.0

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

[root@server]# cmxctl config controllers show

+--------------+------+------------+----------------+------+--------+
| IP Address | Type | Version | Device Version | SHA2 | Status |
+--------------+------+------------+----------------+------+--------+
| 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 |
+--------------+------+------------+----------------+------+--------+

Examples

This example shows how to delete client history and raw analytics data.

[root@server]# cmxctl config data deleteAll
Do you wish to continue? All client history data, analytics data will be deleted and CMX services will be restarted. [y/N]: y
Stopping all the services
All the Application services are stopped
Data Deletion Began
Deleting All Analytics Raw Visits Data
Deleting All Clients History Data
Starting all the services
All the Application services are restarted

Examples

The following example shows how to list the feature flags:

[root@server]# cmxctl config featureflags
+---------------------------------+-------+
| location.compactlocationhistory | true  |
+---------------------------------+-------+
| configuration.apimport          | true  |
+---------------------------------+-------+
| location.rogueapclienthistory   | true  |
+---------------------------------+-------+
| monit                           | true  |
+---------------------------------+-------+
| container.influxdbreporter      | true  |
+---------------------------------+-------+
| configuration.highendbypass     | false |
+---------------------------------+-------+
| apiserver.enabled               | true  |
+---------------------------------+-------+
| analytics.queuetime             | false |
+---------------------------------+-------+

Examples

[root@server]#  cmxctl config gateway show

CMX_CLOUD_SERVER: demo.com

Examples

The following example shows how to display configuration information for the CMX analytics service.

[root@server]# cmxctl config get analytics

{
    "services": {
        "analytics": {
            "maxdirectmemory": "1536M",
            "maxnewsize": "400M",
            "mem": "1536M"
        }
    }
}

Optionally, you can filter the results by using one of the listed configuration keywords. For example:

[root@server]$ cmxctl config get cassandra
{
    "services": {
        "cassandra": {
            "keycachesize": "100",
            "maxnewsize": "800M",
            "mem": "4096M"
        }
    }
}
[root@server]$ cmxctl config get cassandra maxnewsize
{"maxnewsize": "800M"}

Examples

The following example shows how to import a map and Cisco WLC from Cisco 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.

Examples

The following example shows how to set the path to a map address file, which you can then associate with a map.

[root@server]# cmxctl config maps address --path /home/cmxadmin/campusPath.csv

cmxctl config maps address --path /home/cmxadmin/campusPath.csv
Now importing address for: North Campus>Building 9

Done importing addresses

Examples

The following example shows how to list all the APs on the Registration Floor of Bld-4.

First, use the cmxctl config maps floors command to get the Location Floor ID for the floor you want to view:

[root@server]# cmxctl config maps floors

+------------------------------------+--------------------+--------------------+
| Floor Name                         | Location Floor ID  | Analytics Floor ID |
+------------------------------------+--------------------+--------------------+
| North Campus>Bld-4>Registration    | 727035700041482593 | 35                 |
+------------------------------------+--------------------+--------------------+

[root@server]# cmxctl config maps aplist 72703570082593

+---------------+-------------------+-------------------+----------------+----------+
| Name          | EthMacAddress     | RadioMacAddress   | FloorId        | Status   |
+---------------+-------------------+-------------------+----------------+----------+
| CMX-AP05-7069 | None              | 70:69:5a:51:48:40 | 72703570082593 | INACTIVE |
+---------------+-------------------+-------------------+----------------+----------+
| CMX-AP01-7070 | 40:01:7a:b2:c7:a2 | 70:70:8b:06:19:60 | 72703570082593 | ACTIVE   |
+---------------+-------------------+-------------------+----------------+----------+
| CMX-AP02-7071 | 40:01:7a:b2:c8:86 | 70:70:8b:06:1d:e0 | 72703570082593 | ACTIVE   |
+---------------+-------------------+-------------------+----------------+----------+
| CMX-AP06-7072 | 4c:77:6d:9e:61:9e | 70:69:5a:51:52:80 | 72703570082593 | ACTIVE   |
+---------------+-------------------+-------------------+----------------+----------+
| CMX-AP03-7073 | 40:01:7a:b2:c7:92 | 70:70:8b:06:19:20 | 72703570082593 | ACTIVE   |
+---------------+-------------------+-------------------+----------------+----------+
| CMX-AP04-7074 | 4c:77:6d:9e:61:04 | 70:69:5a:51:48:e0 | 72703570082593 | ACTIVE   |
+---------------+-------------------+-------------------+----------------+----------+

Examples

The following example shows how to display a list of all buildings, in CSV format. The output format is Campus Name > Building Name , Location Building ID , Analytics Building ID .

[root@server]# cmxctl config maps buildings --csv

System Campus>TMT,749980497668473090,18
System Campus>LCN,727001546461545854,16
System Campus>PCH,769481534004431937,15
North Campus>Newtech Building,732849996352089441,13
 

The following example shows how to display a list of building maps for North Campus:

[root@server]# cmxctl config maps buildings --campus North Campus

+------------------------------+----------------------+-----------------------+
| Building Name                | Location Building ID | Analytics Building ID |
+------------------------------+----------------------+-----------------------+
| North Campus>Newtech 1       | 727001546461544629   | 48                    |
+------------------------------+----------------------+-----------------------+
| North Campus>Newtech 2       | 725930212039482938   | 49                    |
+------------------------------+----------------------+-----------------------+
 

Examples

The following example shows how to display a list of campus maps:

[root@server]# cmxctl config maps campuses

+----------------+--------------------+---------------------+
| Campus Name    | Location Campus ID | Analytics Campus ID |
+----------------+--------------------+---------------------+
| North Campus   | 727001546461544473 | 14                  |
+----------------+--------------------+---------------------+
| South Campus   | 384920494820170003 | 15                  |
+----------------+--------------------+---------------------+
 

If you want the campus map to be displayed in CSV format, add the --csv flag:

[root@server]# cmxctl config maps campuses –-csv

North Campus,727001546461545275,14
South Campus,384920494820170003,15
 

Examples

This example shows how to delete the Newtech 1 Security floor in North Campus:

[root@server]# cmxctl config maps delete

Please enter the hierarchy to be deleted (campus-name>building-name>floor-name):
North Campus>Newtech 1>Security
map deleted.

This example shows how to delete the map named NorthCampus.

[root@server]# cmxctl config maps delete --name NorthCampus
Confirm delete hierarchy: NorthCampus ? [y/N]: y
Map deleted.

Examples

The following example shows how to display a list of floor maps for North Campus, building A9:

[root@server]# cmxctl config maps floors --campus North Campus ‑‑building A9

+----------------------------------+--------------------+--------------------+
| Floor Name                       | Location Floor ID  | Analytics Floor ID |
+----------------------------------+--------------------+--------------------+
| North Campus>A9>Main Floor       | 615446507270015464 | 16                 |
+----------------------------------+--------------------+--------------------+
| North Campus>A9>Lab Floor        | 727001546461544650 | 17                 |
+----------------------------------+--------------------+--------------------+
| North Campus>A9>Offices Floor    | 615447265700154640 | 18                 |
+----------------------------------+--------------------+--------------------+
 

Examples

The following example shows how to import a map, overwriting any existing maps or zones with the same name:

[root@server]# cmxctl config maps import ‑‑type PI ‑‑path 
/opt/Import_fdff5788ad650.tar.gz ‑‑override yes ‑‑importzones yes

Please enter PI ip address: 168.172.206.3
Please enter PI username [root]: root
Please enter PI password [Public123]: ********
Import successfully started from PI 168.172.206.3. 
 

Examples

The following example shows how to reprocess floor tile images when they become misaligned:

[root@server]$ cmxctl config maps reprocessimage --imagename domain_2_147753.png

File domain_2_147753.png exists in /opt/cmx/srv/floormaps. Proceeding...
Image processing job submitted for domain_2_147753.png.

Examples

The following example shows how to display a list of zones for North Campus Bld-4:

[root@server]# cmxctl config maps floors --campus North Campus building Bld-4

[cmxadmin@cmx-nortech-server ~]$ cmxctl config maps zones
+------------------------------------+-----------+-------------------+
| Floor Name                         | Zone Name | Analytics Zone ID |
+------------------------------------+-----------+-------------------+
| North Campus>Bld-4>1st Floor       | NOC       | 376               |
+------------------------------------+-----------+-------------------+
| North Campus>Bld-4>1st Floor       | School    | 375               |
+------------------------------------+-----------+-------------------+

 

Examples

[root@server]#  cmxctl config qlesspyworker cleanRedis
QlessHistoryCleanupTask started
Deleted 0 qless-job-history records that were idle for 1209600 seconds.
Found 0 SMA-job records, deleted all.
QlessHistoryCleanupTask completed

Examples

The following example shows how to forcefully generate a configuration file:

[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

Examples

The following example shows how to set the timeout for RFID tags, and then verify the setting:

[root@server]# cmxctl config rfid timeout set

need to include a timeout within 600 to 10800 seconds
[root@server]# cmxctl config rfid timeout set 600
[root@server]# cmxctl config rfid timeout get
600 seconds

Examples

This example shows how to generate a key for the service location .

[root@server]$ cmxctl config set location key 2512
{"key": "2512"}
Change will take effect on service restart.

Restart the service.

[root@server]$ cmxctl restart location
Done
The nodeagent service is currently running with PID: 3299
Attempting to restart Location
............
Service Location has successfully restarted

To verify the key, use the cmxctl config get location command:

[root@server]$ cmxctl config get location
{
    "services": {
        "location": {
            "key": "2512",
            "maxdirectmemory": "1536M",
            "maxnewsize": "800M",
            "mem": "6144M"
        }
    }
}

Examples

The following example shows how to manage SMA:

[root@server]# cmxctl config sma proxy
Please enter value for http proxy: http://proxy.cisco.com:80
Please enter value for https proxy: http://proxy.cisco.com:80
SMA Proxies have been set. Please restart qlesspyworker for the changes to take effect.

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
+-----------------+--------------------------------+------------+-------------------------+
| module | check | passed | msg
|
+=================+================================+============+========================+
| netman_stopped | NetworkManager service is not | Success |
|
| | running | |
|
+-----------------+--------------------------------+------------+-------------------------
--+
| matlabengine | http://matlabengine.service.co | Failed | check the log files
under |
| | nsul:5577/api/services/matlabe | | /opt/cmx/var/log
|
| | ngine/status | |
|
+-----------------+--------------------------------+------------+-------------------------+
| database | connect to database port:5432 | Success |
|
+-----------------+--------------------------------+------------+-------------------------+
| consul_dns | 127.0.0.1 (consul) is present | Success |
|
| | as dns server in | |
|
| | /etc/resolv.conf | |
|
+-----------------+--------------------------------+------------+-------------------------
--+
| etchost_hacks | consul service hostnames not | Success |
|
| | static in /etc/hosts | |
|
+-----------------+--------------------------------+------------+-------------------------+
| analytics | http://analytics.service.consu | Failed | check the log files
under |
| | l:5556/api/services/analytics/ | | /opt/cmx/var/log
|
| | status | |
|
+-----------------+--------------------------------+------------+-------------------------+
| hostname_ping | ping to hostname:cmx-master-1 | Success |
|
+-----------------+--------------------------------+------------+-------------------------
--+
| location | http://location.service.consul | Failed | check the log files
under |
| | :5555/api/services/location/st | | /opt/cmx/var/log
|
| | atus | |
|
+-----------------+--------------------------------+------------+-------------------------
--+
| confd_installed | Confd is installed | Success |
|
+-----------------+--------------------------------+------------+-------------------------+
| consul_installe | Consul is installed | Success |
|
| d | | |
|
+-----------------+--------------------------------+------------+-------------------------
--+
| nmsplb | http://nmsplb.service.consul:6 | Failed | check the log files
under |
| | 001/api/services/nmsplb/status | | /opt/cmx/var/log
|
+-----------------+--------------------------------+------------+-------------------------+
| configuration | http://configuration.service.c | Failed | check the log files
under |
| | onsul:6000/api/services/config | | /opt/cmx/var/log
|
| | uration/status | |
|
+-----------------+--------------------------------+------------+-------------------------+
| cassandra | connect to cassandra port:9042 | Success |
|
+-----------------+--------------------------------+------------+-------------------------+

Examples

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

[cmxadmin@10.10.10.10:~]$ 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.

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.

Examples

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

[root@server]# cmxctl dump
running locally
Dumping configuration information...
[localhost] Executing task 'dump_config'
Done.

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

Examples

The following example shows how to verify the heterarchy:

[root@server]# cmxctl heterarchy verify
Verifying heterarchy...
Checking user levels
Heterarchy is healthy.

Examples

The following example shows how to wipe the influx database:

[root@server]# cmxctl influxdb wipe
This command will wipe the Influx database. All system metric data will be erased.
Do you want to continue?: y
Stopping influxdb Process...
executing shutdown
Retrying..
Retrying...
Retrying....
Done
Successfully shutdown influxdb Process.
Cleaning Influx database directories
Configuring InfluxDB

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.

Examples

The following example shows how to generate metrics for a Cisco CMX file:

[root@server]# cmxctl metrics notification
+--------------------------------+------------+------------+-----------------+------------+
| EndPoint | Success | Failure | SuccessRate |
FailureRate |
+================================+============+============+=================+===========+
+--------------------------------+------------+------------+-----------------+------------+

Examples

The following example shows how to manage node installation:

[root@server]# 	cmxctl node sslmode enable --pem <pem-file-location> --key <key-file-location>
enabling ssl
ssl enabled

Examples

The following example shows how to restart a Cisco CMX service:

[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

Examples

The following example shows how to generate jstack for location services:

Examples

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

[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

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: 6190
+----------------+---------------+---------+----------------+
| Host           | Service       | Status  | Uptime (HH:mm) |
+----------------+---------------+---------+----------------+
| CMX-LowEnd-200 | Analytics     | Running | 5 days, 05:49  |
+----------------+---------------+---------+----------------+
| CMX-LowEnd-200 | Cache_6378    | Running | 5 days, 05:52  |
+----------------+---------------+---------+----------------+
| CMX-LowEnd-200 | Cache_6379    | Running | 5 days, 05:49  |
+----------------+---------------+---------+----------------+
| CMX-LowEnd-200 | Cache_6380    | Running | 5 days, 05:49  |
+----------------+---------------+---------+----------------+
| CMX-LowEnd-200 | Cache_6381    | Running | 5 days, 05:49  |
+----------------+---------------+---------+----------------+
| CMX-LowEnd-200 | Cache_6382    | Running | 5 days, 05:49  |
+----------------+---------------+---------+----------------+
| CMX-LowEnd-200 | Cache_6383    | Running | 5 days, 05:49  |
+----------------+---------------+---------+----------------+
| CMX-LowEnd-200 | Cache_6385    | Running | 5 days, 05:49  |
+----------------+---------------+---------+----------------+
| CMX-LowEnd-200 | Cassandra     | Running | 5 days, 05:51  |
+----------------+---------------+---------+----------------+
| CMX-LowEnd-200 | Confd         | Running | 5 days, 05:49  |
+----------------+---------------+---------+----------------+
| CMX-LowEnd-200 | Configuration | Running | 5 days, 05:49  |
+----------------+---------------+---------+----------------+
| CMX-LowEnd-200 | Connect       | Running | 5 days, 05:49  |
+----------------+---------------+---------+----------------+
| CMX-LowEnd-200 | Consul        | Running | 5 days, 05:52  |
+----------------+---------------+---------+----------------+
| CMX-LowEnd-200 | Database      | Running | 5 days, 05:52  |
+----------------+---------------+---------+----------------+
| CMX-LowEnd-200 | Haproxy       | Running | 5 days, 05:49  |
+----------------+---------------+---------+----------------+
| CMX-LowEnd-200 | Hyperlocation | Running | 5 days, 05:47  |
+----------------+---------------+---------+----------------+
| CMX-LowEnd-200 | Influxdb      | Running | 5 days, 05:49  |
+----------------+---------------+---------+----------------+
| CMX-LowEnd-200 | Iodocs        | Running | 5 days, 05:50  |
+----------------+---------------+---------+----------------+
| CMX-LowEnd-200 | Location      | Running | 5 days, 05:49  |
+----------------+---------------+---------+----------------+
| CMX-LowEnd-200 | Matlabengine  | Running | 5 days, 05:48  |
+----------------+---------------+---------+----------------+
| CMX-LowEnd-200 | Metrics       | Running | 5 days, 05:49  |
+----------------+---------------+---------+----------------+
| CMX-LowEnd-200 | Nmsplb        | Running | 5 days, 05:47  |
+----------------+---------------+---------+----------------+
| CMX-LowEnd-200 | Qlesspyworker | Running | 5 days, 05:50  |
+----------------+---------------+---------+----------------+
| CMX-LowEnd-200 | gateway       | Running | 5 days, 05:50  |
+----------------+---------------+---------+----------------+

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.

Examples

[cmxadmin@CMX-LowEnd-200 ~]$ cmxctl trace mac status
+-------------------+
| MAC Address       |
+-------------------+
| 3c:a9:f4:6c:ee:44 |
+-------------------+
| ac:37:43:4b:cc:2f |
+-------------------+
| 3c:a9:f4:6c:5a:ac |

Examples

The following example shows how to display current tarce levels:

[root@server]# cmxctl trace mac status
+-------------------+
| MAC Address       |
+-------------------+
| 00:01:02:03:04:05 |
+-------------------+

Examples

Examples

The following example shows how to list Cisco CMX users using the CLI:

[root@server]# cmxctl users list
+----------+--------------+-----------+
| Username | Full Name | Roles |
+==========+==============+===========+
| monitor | Monitor User | Read Only |
+----------+--------------+-----------+
| admin | Admin User | Admin |
+----------+--------------+-----------+

Examples

The following example shows how to unlock the CMX GUI user someguy:

[root@server]# cmxctl users unlock gui someguy

Account unlocked successfully

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
----------------------------------------------------------------------

Examples

The following example shows how to list all Cisco CMX accuracy tests:

[cmxadmin@cmx-nortech ~]$ cmxloc list
+-------+----------+-------------------+---------------+---------------+---------+---------+-------------+
| Name  | Status   | MAC Address       | Comp Freq (s) | Avg Error (m) | 90% (m) | 50% (m) | Test Points |
+-------+----------+-------------------+---------------+---------------+---------+---------+-------------+
| FB1   | PAUSED   | 98:07:2d:2a:11:fa | 0.0           | 0.0           | 0.0     | 0.0     | 0           |
+-------+----------+-------------------+---------------+---------------+---------+---------+-------------+
| Test1 | FINISHED | 98:07:2d:2a:11:fa | 61.0          | 2.45          | 3.23    | 1.93    | 1           |
+-------+----------+-------------------+---------------+---------------+---------+---------+-------------+
| Test2 | FINISHED | 98:07:2d:2a:11:fa | 33.25         | 4.36          | 6.27    | 3.44    | 4           |
+-------+----------+-------------------+---------------+---------------+---------+---------+-------------+

Examples

The following example shows how to increase disk space in the operating system:

[root@server]# cmxos addswap
10485760+0 records in
10485760+0 records out
10737418240 bytes (11 GB) copied, 29.6845 s, 362 MB/s
Setting up swapspace version 1, size = 10485756 KiB
no label, UUID=2734f069-e687-4635-b2d6-9381241bc7ee
swap added, run system info to verify
[root@cmx-vmdev146 ~]#

Examples

The following example shows how to stop the administrator UI:

[root@server]# cmxos adminui stop
Stopping adminui...

Examples

The following example shows how to disable the Cisco CMX API server:

[root@server]# cmxos apiserver disable
Starting CMX API Server...

Examples

The following example shows how to enable the Cisco CMX API server:

[root@server]# cmxos apiserver enable
Enabling CMX API Server...
Starting CMX API Server...

Examples

The following example shows how to reset the Cisco CMX API server:

[root@server]# cmxos apiserver reset
Resetting CMX API Server...

Examples

The following example shows how to start the Cisco CMX API server:

[root@server]# cmxos apiserver restart
Restarting CMX API Server...

Examples

The following example shows how to start the Cisco CMX API server:

[root@server]# cmxos apiserver start
Starting CMX API Server...

Examples

The following example shows how to view the status of Cisco CMX API server:

[root@server]# cmxos apiserver status
+--------------------------+
|  CMX API Server Status   |
+---------------+----------+
| Configuration | Enabled  |
+---------------+----------+
| Status        | Running  |
+---------------+----------+

Examples

The following example shows how to start the Cisco CMX API server:

[root@server]# cmxos apiserver stop
Stopping CMX API Server...

Examples

The following example shows how to add a new user for the Cisco CMX API server:

[root@server]# cmxos apiserver user add
Please enter the userid for the CMX API Server: user1
Please enter the password for the CMX API Server: password
Please re-enter the password for the CMX API Server: password
Restarting CMX API Server...
Stopping CMX API Server...
Starting CMX API Server...
Successfully updated userid/password and restarted the CMX API Server

The following example shows how to list Cisco CMX API server users:

[root@server]# cmxos apiserver user list
+---------+
| User ID |
+=========+
| admin   |
+---------+
| user1   |
+---------+

Examples

The following example shows how to back up a node:

[cmxadmin@10.10.10.10:~]$ cmxos 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

Examples

The following example shows how to verify the disk performance:

[root@server]# cmxos benchmark disk
This process will check disk performance on /opt/cmx/srv/
You must stop all CMX services manually before running this command
Do you want to continue?: yes
Running disk performance...this may take a while...please wait...
READ IOPS: 6085, WRITE IOPS: 2024

Examples

[root@server]# cmxos checkpostgresdatasize
651488	/opt/cmx/srv/postgres

Examples

The following example shows how to search for large files:

[root@server]# cmxos clean find
Starting search for large files
Size: 1.96G File: /tmp/cmx_backup_CMX-LowEnd-200_2017_01_18_17_56.tar.gz
Size: 2.36G File: /tmp/cmx_backup_CMX-LowEnd-200_2017_03_14_11_16.tar.gz
Size: 2.43G File: /tmp/cmx_backup_CMX-LowEnd-200_2017_03_20_14_36.tar.gz
Size: 2.32G File: /tmp/cmx_backup_CMX-LowEnd-200_2017_01_18_18_00.tar.gz
Size: 1.45G File: /var/log/maillog-20170212.gz
Size: 2.63G File: /var/log/maillog-20170205.gz
Size: 6.84G File: /home/cmxadmin/cmx_backup_CMX-LAC-210_2017_03_23_22_09.tar.gz
Size: 1.17G File: /home/cmxadmin/CISCO_CMX-10.3.0-58.cmx
Completed search for large files

[root@server]# cmxos clean normal
Files which can be removed in: /opt/cmx/var/log
/opt/cmx/var/log/adminui/adminui.pid
/opt/cmx/var/log/adminui/webui.ans
/opt/cmx/var/log/agent/server.log.3
/opt/cmx/var/log/agent/server.log.1
/opt/cmx/var/log/agent/server.log.5
/opt/cmx/var/log/agent/server.log.2
/opt/cmx/var/log/agent/server.log.4
/opt/cmx/var/log/backup.log.2
/opt/cmx/var/log/backup.log.3
/opt/cmx/var/log/setup.log.8
/opt/cmx/var/log/setup.log.7
/opt/cmx/var/log/cmxjobs.log.1
/opt/cmx/var/log/cmxjobs.log.5

[root@server]# cmxos clean normal --delete
Are you sure you wish to remove files? [y/N]: y
Removing files in: /opt/cmx/var/log
Remove: /opt/cmx/var/log/agent/server.log.2
Remove: /opt/cmx/var/log/agent/server.log.1
Remove: /opt/cmx/var/log/cmxjobs.log.5
Remove: /opt/cmx/var/log/cmxjobs.log.2
Remove: /opt/cmx/var/log/cmxjobs.log.4
Remove: /opt/cmx/var/log/cmxjobs.log.1
Remove: /opt/cmx/var/log/cmxjobs.log.3

Examples

The following example shows how to configure the network and operating system parameters:

[root@server]# cmxos configure --force
*** The system is already configured
********************************************************************************
Checking if the machine meets required specification...
********************************************************************************
+----------+------------------------+--------------+--------+
| Check | expected | actual | Result |
+==========+========================+==============+========+
| memory | 8GB | 25GB | ? |
+----------+------------------------+--------------+--------+
| cpu | 4 | 8 | ? |
+----------+------------------------+--------------+--------+
| disk | 50GB | 51GB | ? |
+----------+------------------------+--------------+--------+
| hostname | rfc compliant hostname | cmx-vmdev146 | ? |
+----------+------------------------+--------------+--------+

Examples

The following example show how to enable encryption after CMX installation.

[root@server]# cmxos encryptdisk

Have you closed all SSH sessions to this CMX? [y/N]:y
Are you sure you want to encrypt the /opt partition of the disk ? [y/N]:y

Checking disk space requirements for backing up /opt folder...
Looks Good.

Proceed with stopping all CMX services? [y/N]:y

Backing up /opt folder into /var ...
tar backup done.
Press Enter key to enter rescue mode and begin the encryption.

Press Enter.

Shredding /opt ...
Shread: List of deleted folders
Shread: List of deleted folders
Shread: List of deleted folders
...
Formatting /opt ...

You will be prompted to set a passphrase for encrypted disk /opt.
Choose a passphrase, Enter and Verify it.

Note:
On every boot / power up, you will be prompted for this passphrase.
System will continue only if this passphrase is correct.

WARNING!
========
This will overwrite data on /opt irrevocably.
Are you sure? (Type uppercase yes): YES

Enter a passphrase.

Enter passphrase:
Verify passphrase:
Command successful.

Opening /opt ...
Enter passphrase for /opt:

Encryption of /opt is complete.

System will reboot now.
Upon (every) restart, when prompted to enter passphrase for /opt partition, 
enter the passphrase you just set.

Press Enter to continue with reboot

Press Enter.

Please enter passphrase for disk opt on /opt!:

Examples

[root@server]# cmxos etchosts
[root@cmx-vmdev185 cmxadmin]# cmxos etchosts --help
Usage: __main__.py etchosts [OPTIONS]
  Configure /etc/hosts properly
Options:
  --help  Show this message and exit.

Examples

The following example shows how to set up Cisco CMX again:

[root@server]# cmxos firstboot
Not first boot....Exiting...

Examples

The following example shows how to verify HA proxy permissions:

[root@server]# cmxos fixhaproxy
Raising haproxy setcap...

Examples

The following example shows how to check the health of a Cisco CMX system:

[root@server]# cmxos health filedescriptors
2195 total file descriptors open

[root@server]# cmxos health ntp
NTP Synchronization error:
unsynchronised
  time server re-starting
   polling server every 8 s

Examples

The following example shows how to view the inventory details:

[root@server]# cmxos inventory
UDI: AIR-MSE-3365-K9 Serial Number -  FCH1904V055

State of the RAID array: Healthy and working normally
Capacity of the RAID array: 1.088 TB
Type of disks in RAID array: Spinning Disk Drive
All chassis fans operating normally
One of the power supplies in the chassis has failed or it has not been installed/connected
Disk Capacity: 1.0T
Disk space used: 33.2G
Memory installed: 63.00G 
CPUs  installed: 20
CPU Type:  Intel(R) Xeon(R) CPU E5-2650 v3 @ 2.30GHz
Server uptime: 6 Hours, 59 Minutes, 44 Seconds
Server boot time: Mon, 27 Mar 2017 16-44-36 
Number of server reboots: 1

Examples

[root@cmx-vmdev185 cmxadmin]# cmxos kill
This command will force kill all CMX processes, for dev use only
Do you want to continue?:

Examples

The following example shows how to display the monitoring settings:

[cmxadmin]$ cmxos monit configure
Deleting all monit configurations....
Configuring monit mail settings...
Configuring monit OS settings...
Configuring monit CMX services settings...

The following example shows how to enable monitoring of Cisco CMX services:

[cmxadmin]$ cmxos monit start
Starting monit:

Examples

The following example shows how to open ports based on a node:

[root@server]# cmxos openports analytics
Opened port 6541
Opened port 6542
Successfully opened all ports. Saving iptables info...

Examples

The following example shows how to reconfigure the network after Cisco CMX installation:

[root@server]# cmxos reconfigure
This command will wipe all system metrics data when the configuration is changed
Do you want to continue?: yes
Please enter hostname [cisco-cmx-centos7-test0]:
Please enter IP address [192.0.2.1]:
Please enter netmask [255.255.255.0]:
Please enter gateway [192.0.2.2]:
Please enter DNS server [192.0.2.3]:
Please enter search domain name [example.com]:
Are the network settings correct?: yes
Stopping keepalived service
Verify keepalived service has been stopped
Successfully stopped the keepalived service.
Starting keepalived service
ERROR: Failed to start keepalived service.
********************************************************************************
Configuring NTP Server...
********************************************************************************
Please enter the NTP server name (blank for no NTP server) [ntp.esl.cisco.com]:
Setting ntp server ntp.esl.cisco.com
********************************************************************************
Configuring Timezone and date...
********************************************************************************
Please identify a location so that time zone rules can be set correctly.
Please select a continent or ocean.
 1) Africa
 2) Americas
 3) Antarctica
 4) Arctic Ocean
 5) Asia
 6) Atlantic Ocean
 7) Australia
 8) Europe
 9) Indian Ocean
10) Pacific Ocean
11) none - I want to specify the time zone using the Posix TZ format.
#? 10
Please select a country.
 1) Chile                      15) Northern Mariana Islands
 2) Cook Islands               16) Palau
 3) Ecuador                    17) Papua New Guinea
 4) Fiji                       18) Pitcairn
 5) French Polynesia           19) Samoa (American)
 6) Guam                       20) Samoa (western)
 7) Kiribati                   21) Solomon Islands
 8) Marshall Islands           22) Tokelau
 9) Micronesia                 23) Tonga
10) Nauru                      24) Tuvalu
11) New Caledonia              25) United States
12) New Zealand                26) US minor outlying islands
13) Niue                       27) Vanuatu
14) Norfolk Island             28) Wallis & Futuna
#? 25
Please select one of the following time zone regions.
 1) Eastern (most areas)              16) Central - ND (Morton rural)
 2) Eastern - MI (most areas)         17) Central - ND (Mercer)
 3) Eastern - KY (Louisville area)    18) Mountain (most areas)
 4) Eastern - KY (Wayne)              19) Mountain - ID (south); OR (east)
 5) Eastern - IN (most areas)         20) MST - Arizona (except Navajo)
 6) Eastern - IN (Da, Du, K, Mn)      21) Pacific
 7) Eastern - IN (Pulaski)            22) Alaska (most areas)
 8) Eastern - IN (Crawford)           23) Alaska - Juneau area
 9) Eastern - IN (Pike)               24) Alaska - Sitka area
10) Eastern - IN (Switzerland)        25) Alaska - Annette Island
11) Central (most areas)              26) Alaska - Yakutat
12) Central - IN (Perry)              27) Alaska (west)
13) Central - IN (Starke)             28) Aleutian Islands
14) Central - MI (Wisconsin border)   29) Hawaii
15) Central - ND (Oliver)
#? 21

The following information has been given:

        United States
        Pacific

Therefore TZ='America/Los_Angeles' will be used.
Local time is now:      Mon May 21 08:25:39 PDT 2018.
Universal Time is now:  Mon May 21 15:25:39 UTC 2018.
Is the above information OK?
1) Yes
2) No
#? 1
The Timezone selected is America/Los_Angeles

The current time is Mon May 21 08:25:40 PDT 2018

Enter Date (YYYY-mm-dd hh:mm:ss) (blank to sync with ntp):  []:
*** No changes were detected

Note	This command opens the Device Configuration window, where you can take the appropriate action, that is reconfigure the device or the DNS.

Examples

The following example shows how to restore a node:

[root@server]# cmxos 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

Examples

Examples

The following example shows how to set a proxy on the Cisco CMX server, and then verify the change and restart Cisco CMX:

[root@server]# cmxos sysproxy proxy https://proxy-wsa.esl.cisco.com:80

[root@server]# cmxos sysproxy show
USE_PROXY=1
PROXY_URL=http://proxy-wsa.esl.cisco.com:80
NO_PROXY_LIST=""
[root@server]# cmxctl restart

The following example shows how to enable a proxy on the Cisco CMX server, and then verify the change and restart Cisco CMX:

[root@server]# cmxos sysproxy enable

[root@server]# cmxos sysproxy show
USE_PROXY=1
PROXY_URL=http://proxy-wsa.esl.cisco.com:80
NO_PROXY_LIST=""
[root@server]# cmxctl restart

The following example shows how to disable a proxy on the Cisco CMX server, and then verify the change and restart Cisco CMX:

[root@server]# cmxos sysproxy disable

[root@server]# cmxos sysproxy show
USE_PROXY=0
PROXY_URL=http://proxy-wsa.esl.cisco.com:80
NO_PROXY_LIST=""
[root@server]# cmxctl restart

The following example shows how to clear proxy settings, and then verify the change and restart Cisco CMX:

[root@server]# cmxos sysproxy clear

[root@server]# cmxos sysproxy show
USE_PROXY=0
PROXY_URL=""
NO_PROXY_LIST=""
[root@server]# cmxctl restart

Examples

The following example shows how to upgrade the Cisco CMX using RPM or package:

[root@server]# cmxos upgrade
The nodeagent service is not running.
Agent is not running, starting it now.
Starting nodeagent Process...
Stopping nodeagent Process...
Done
Successfully shutdown nodeagent Process.
Stopping consul Process...
Successfully shutdown consul Process.
Stopping qlesspyworker Process...
Successfully shutdown qlesspyworker Process.
Stopping cassandra Process...
Successfully shutdown cassandra Process.
Stopping iodocs Process...
The iodocs service is not running.
Stopping redis6383 Process...
Successfully shutdown redis6383 Process.
Stopping redis6380 Process...
Successfully shutdown redis6380 Process.
Stopping redis6381 Process...
Successfully shutdown redis6381 Process.
Stopping influxdb Process...
The influxdb service is not running.
Stopping collectd Process...
The collectd service is not running.
Stopping confd Process...
The confd service is not running.
Stopping redis6379 Process...
Successfully shutdown redis6379 Process.
Stopping redis6378 Process...
Successfully shutdown redis6378 Process.
Stopping haproxy Process...
Stopping postgres Process...
Successfully shutdown postgres Process.
Stopping analytics Process...
The analytics service is not running.
Stopping location Process...
The location service is not running.
Stopping configuration Process...
The configuration service is not running.
Stopping halo Process...
The halo service is not running.
Stopping matlabengine Process...
The matlabengine service is not running.
Stopping nmsplb Process...
The nmsplb service is not running.
Shutting down

Examples

The following example shows how to verify the virtual machine configuration:

[root@server]# cmxos verify
+----------+------------------------+--------------+--------+
| Check | expected | actual | Result |
+==========+========================+==============+========+
| memory | 8GB | 25GB | ? |
+----------+------------------------+--------------+--------+
| cpu | 4 | 8 | ? |
+----------+------------------------+--------------+--------+
| disk | 50GB | 51GB | ? |
+----------+------------------------+--------------+--------+
| hostname | rfc compliant hostname | cmx-vmdev146 | ? |
+----------+------------------------+--------------+--------+