Skip to content

Latest commit

 

History

History
151 lines (104 loc) · 10.8 KB

tools.md

File metadata and controls

151 lines (104 loc) · 10.8 KB
Raw
description
Tools to view NSO status and perform specialized tasks.

Tools

The Tools view includes utilities that you can use to run specific tasks on your deployment, such as running compliance reports, etc.

Tools View

The following tools are available:

  • Insights: Gathers and displays useful statistics of your deployment.
  • Package upgrade: Used to perform upgrades to the packages running in NSO.
  • High availability: Used to manage a High Availability (HA) setup in your deployment.
  • Alarms: Shows current alarms/events in your deployment and provides options to manage them.
  • Commit manager: Shortcut to the Commit Manager.
  • Compliance reports: Used to run compliance checks on your NSO network.

Insights

The Insights view collects and displays the following types of operational information using the /ncs:metrics data model to present useful statistics:

  • Real-time data about transactions, commit queues, and northbound sessions.
  • Sessions created and closed towards northbound interfaces since the last restart (CLI, JSON-RPC, NETCONF, RESTCONF, SNMP).
  • Transactions since last restart (committed, aborted, and conflicting). You can select between the running and operational data stores.
  • Devices and their sync statuses.
  • CDB info about its size, compaction, etc.

Package Upgrade

In the Package upgrade view, you can load custom packages in NSO.

The Reload button on the Packages pane is the equivalent of the packages reload command in CLI. Read more about the reload action in NSO Packages.

Install a Package

  1. In the Package upgrade view, click Browse files to select a new package (.tar) from your local disk.
  2. Click Upload. The package becomes visible under the Available pane.
    (The Progress Trace shows the real-time progress of the upload).
  3. Click Install.
  4. On the Loaded pane, click Reload and confirm the intent.

Uninstall a Package

  • To uninstall a package, simply click Deinstall next to the package in the Loaded packages list.

High Availability

The High Availability view is used to visualize your HA setup (rule-based or Raft).

Actions can be performed on the cluster using the Configuration editor -> Actions tab. Possible actions are further described in the High Availability documentation under Actions).

Alarms

The Alarm manager view displays current alarms in the system. The alarms are categorized as criticals, majors, and minors and can be filtered by the device.

You can run actions on an alarm by selecting it and using the run action button.

Commit Manager

The Commit manager displays notifications about commits pending to be approved. Any time a change (a transaction) is made in NSO, the Commit Manager displays a notification to review the change. You can then choose to confirm or revert the commit.

{% hint style="warning" %} Transactions and Commits

Take special note of the Commit Manager. Whenever a transaction has started, the active configuration data changes can be inspected and evaluated before they are committed and pushed to the network. The data is saved to the NSO datastore and pushed to the network when a user presses Commit.

Any network-wide configuration change can be picked up as a rollback file. The rollback can then be applied to undo whatever happened to the network. {% endhint %}

Review a Configuration Change

  1. Access the Commit Manager by clicking its icon in the banner.
  2. Review the available changes appearing as Current transaction. If there are errors in the change, the Commit Manager alerts you and suggests possible corrections. You can then fix them and press Re-validate to clear the errors.
  3. Click Revert to undo or Commit to confirm the changes in the transaction.
    • Commit Options: When committing a transaction, you have the possibility to choose Commit options and perform a commit with the specified commit option(s). Examples of commit options are: No revision drop, No deploy, No networking, etc. Commit options are described in detail in the JSON-RPC API documentation under Methods - transaction - commit changes.

{% hint style="info" %} In the Commit manager view, you can fetch additional information about the leaf by enabling more node options and clicking the info button. {% endhint %}

Load/Save Configuration Data

Start a transaction to load or save configuration data using the Load/Save option which you can then review for commit. The following tabs are available:

  • Rollback, to load data that reverts an earlier change.
  • Files, to load data from a local file on your disk.
  • Paste, to load data by pasting it in.
  • Save, to save loaded data to a file on your local disk.

Commit Manager Tabs

In the Commit manager view, the following tabs are shown.

  • changes tab, to list the changes and actions done in the system, e.g., deleting a device or changing its properties.
  • errors tab, to list the errors encountered while doing changes. You can review the errors, make changes, and revalidate the error using the Re-validate option.
  • warnings tab, to list the warnings encountered while doing changes.
  • config tab, to list the configuration changes associated with the change.
  • native config tab, to list the device configuration data in the native config.
  • commit queue tab, to manage commit queues. See Commit Queue for more information.

Compliance Reporting

The Compliance reporting view is used to create and run compliance reports to check the current situation, check historical events, or both.

{% hint style="success" %} The recommended and preferred way of running the compliance reports is through the Web UI. {% endhint %}

The following main tabs are available in this view:

  • Compliance reports, to create, run, manage, and view existing compliance reports.
  • Report results, to view compliance report results and status.

Create a Compliance Report

  1. In the Compliance reporting view -> Compliance reports tab, click New report.
  2. In the Create new report pop-up, enter the report name and click Create.
  3. Next, set up the compliance report using the following tabs. For a more detailed description of Compliance Reporting concepts and related configuration options, see Lifecycle Operations documentation.
    • General tab: to configure the report name. Configuration options include:
      • Report name: Displays the report name and allows editing of the report name.
    • Devices tab: to configure device compliance checks. Configuration options include:
      • Device choice: Include All devices or only Some devices to include in compliance checks. If Some devices is selected, specify the devices using a device group, an XPath expression, or individual devices.
      • Current out of sync: Check the device's current status and report if the device is in sync or out of sync. Possible values are true (yes, request a check-sync) and false (no, do not request a check-sync).
      • Historic changes: Include or exclude previous changes to devices using the commit log. Possible values are true (yes, include), and false (no, exclude).
      • Compliance templates: If a compliance template should be used to check for compliance (see Device Configuration Checks). You have the option to add a compliance template using the Add template option, or convert an existing device template into a compliance template by using the Create from device template option (which can then be added using the Add template option). To enforce devices to comply exactly to the template's configuration, use Strict mode, see Additional Configuration Checks for more information.
    • Services tab: to configure service compliance checks. Configuration options include:
      • Service choice: Include All services or only Some services. If Some services is selected, specify the services using service type, an XPath expression, or individual service instances.
      • Current out of sync: Check the service's current status and report if the service is in sync or out of sync. Possible values are true (yes, request a check-sync) and false (no, do not request a check-sync).
      • Historic changes: Include or exclude previous changes to services using the commit log. Possible values are true (yes, include), and false (no, exclude).
  4. Click Create report when the report setup is complete. The changes are saved and applied immediately.

{% hint style="info" %} In the Compliance reports tab, you can apply the following actions directly on the report by selecting it using the checkbox and using the more options button.

  • Copy as new report: Copy an existing report as a new report.
  • Run: Run the report.
  • Delete: Delete the report.
  • Edit name: Edit the report name. {% endhint %}

Run a Compliance Report

  1. In the Compliance reports tab, click the desired report and then click Run report.
  2. Specify the following in the Run report pop-up:
    • Report title
    • Historical time interval. The report runs with the maximum possible interval if you do not specify an interval.
  3. Click Run report.

The report's results, available from the Report results tab, show if the report was compliant or has violations. Click the report name to fetch detailed results about the report. If there are violations, you can use the View details option to extract a diff of configuration.