Troubleshooting / Useful Commands

Scenarios below are listed in alphabetical order.

Alert Mapping for APIC to SevOne NMS Severity

  • The following table provides SevOne NMS severity code and its corresponding severity.

    • SevOne NMS Severity Codes

    CODE SEVERITY
    0 Emergency
    1 Alert
    2 Critical
    3 Error
    4 Warning
    5 Notice
    6 Info
    7 Debug
  • The following table provides the severity code and its corresponding default alert mapping between the APIC vs. SevOne NMS severities.

    • APIC to SevOne NMS Severity Mapping for Alerts

    CODE APIC NMS
    1 Critical Alert
    2 Major Critical
    3 Minor Error
    4 Warning Warning
    5 Info Notice
    6 Cleared Notice
    If you choose to change the alert mapping, please refer to SevOne SDN Collector Filter Alerts Using 'launch generate-fault-config' Option guide for details.

Obtain List of Running Docker Containers

$ docker ps
CONTAINER ID   IMAGE                                              COMMAND                  CREATED       STATUS       PORTS    NAMES
ecf5881e406d   docker.sevone.com/sc/collectors/cisco-aci:v6.6.0   "python source/main.…"   5 days ago    Up 5 days             cisco-aci-agent-2022-06-22-10-15-25

Remove Unused Objects

To remove unused SDN objects, execute the following command.

$ launch delete-objects [--conf-path <configuration directory>]
Additional options and/or flags can be obtained from CLI help
 
$ launch delete-objects --help

Reset settings.env and multi_site_config.json

In order to reset settings.env and multi_site_config.json files to their original factory settings, the launch script has been provided with a reset-settings option. The reset-settings option, when executed, will reset the settings.env and multi_site_config.json files.

Please use reset-settings option with caution as the settings.env and multi_site_config.json files will be overwritten. Please make sure that files are backed-up before running this option.

Example

$ cd /opt/cisco-aci-agent
 
$ ./launch configure --mode reset-settings --conf-path \
<directory path for settings.env/multi_site_config.json file (optional)>

Restart Collector

To restart the collector, execute the following commands. Also, the changes made in the settings.env and multi_site_config.json files are reflected in the collector after the restart.

$ cd /opt/cisco-aci-agent/
 
$ ./launch restart-collector

Start Collector

To start the collector, execute the following commands.

$ cd /opt/cisco-aci-agent/
$ ./launch run

Stop Collector

To stop the collector, perform the steps below.

  1. Execute the following command.

    $ docker ps

  2. Identify the collector container; the name starts with cisco-aci-agent-. For example, cisco-aci-agent-2022-06-22-10-15-25.

  3. To stop the collector,

    $ docker stop <full container-name-or-id>

    Example

    $ docker stop cisco-aci-agent-2022-06-22-10-15-25

View Log

To confirm that the collector is running and checking for errors, tail the log file you have setup. The log file will be available in the location specified in the multi_site_config.json file as cisco_log_filepath setting.

$ tail -f <data-log-file-name>.log