Explore the Installation
Explore NSO contents after finishing the installation.
Applies to Local Install.
Before starting NSO, it is recommended to explore the installation contents.
Navigate to the newly created Installation Directory, for example:
Contents of the Installation Directory
The installation directory includes the following contents:
Documentation
Along with the binaries, NSO installs a full set of documentation available in the doc/
folder in the Installation Directory. There is also an online version of the documentation available on DevNet.
Run index.html
in your browser to explore further.
Examples
Local Install comes with a rich set of examples to start using NSO.
Network Element Drivers (NEDs)
In order to communicate with the network, NSO uses NEDs as device drivers for different device types. Cisco has NEDs for hundreds of different devices available for customers, and several are included in the installer in the /packages/neds
directory.
In the example below, NEDs for Cisco ASA, IOS, IOS XR, and NX-OS are shown. Also included are NEDs for other vendors including Juniper JunOS, A10, ALU, and Dell.
The example NEDs included in the installer are intended for evaluation, demonstration, and use with the examples.ncs
. These are not the latest versions available and often do not have all the features available in production NEDs.
Install New NEDs
A large number of pre-built supported NEDs are available which can be acquired and downloaded by the customers from Cisco Software Download. Note that the specific file names and versions that you download may be different from the ones in this guide. Therefore, remember to update the paths accordingly.
Like the NSO installer, the NEDs are signed.bin
files that need to be run to validate the download and extract the new code.
To install new NEDs:
Change to the working directory where your downloads are. The filenames indicate which version of NSO the NEDs are pre-compiled for (in this case NSO 6.0), and the version of the NED. An example output is shown below.
Use the
sh
command to runsigned.bin
to verify the certificate and extract the NED tar.gz and other files. Repeat for all files. An example output is shown below.You now have three tar (.
tar.gz
) files. These are compressed versions of the NEDs. List the files to verify as shown in the example below.Navigate to the
packages/neds
directory for your Local Install, for example:In the
/packages/neds
directory, extract the .tar files into this directory using thetar
command with the path to where the compressed NED is located. An example is shown below.Here is a sample list of the newer NEDs extracted along with the ones bundled with the installation:
Shell Scripts
The last thing to note is the files ncsrc
and ncsrc.tsch
. These are shell scripts for bash
and tsch
that set up your PATH and other environment variables for NSO. Depending on your shell, you need to source this file before starting NSO.
For more information on sourcing shell script, see the Local Install steps.
Last updated