Step 1
|
Log in to the Ubuntu server as root or a user with sudo privileges, where Cisco ONP is to be installed.
|
Step 2
|
Create the 5.1_Build folder under ONP_Builds to keep all the required files for the installation.
user@host:~/Desktop$ mkdir ONP_Builds/5.1_Build
Note
|
The example path here /home/ user/Desktop/ONP_Builds/5.1_Build is referenced as $ONP_HOME in this document.
The $ONP_HOME directory can be any other directory in your server. You can create a directory of your choice and copy the
ONP build tar file, signature file, and pubkey file to that directory.
|
|
Step 3
|
Copy or download the Cisco ONP build tar, signature file, and public key file to the created ONP_Builds directory.
|
Step 4
|
Go to the $ONP_HOME directory.
|
Step 5
|
Assign full permission to the build tar.
Example:
cd /home/user/Desktop/ONP_Builds
sudo chmod 777 CONP-xx-xx.xx.xx.tar.gz
|
Step 6
|
Untar the Cisco ONP build.
tar -xvf CONP-xx-xx-xx.xx.tar.gz
|
Step 7
|
Set read, write, and execute permissions for the Install script, LNI, and ONP folders using the following commands.
sudo chmod -R 777 ONP
sudo chmod -R 777 LNI
sudo chmod 777 ONPLniInstaller.sh
|
Step 8
|
Check whether curl is installed in the server by entering the following command:
root:~/$ONP_HOME# curl
If you see the following output, curl is installed. Otherwise, install curl.
curl: try 'curl --help' or 'curl --manual' for more information
To install curl, run the following command:
root:~/$ONP_HOME# sudo apt install curl
|
Step 9
|
Start Cisco ONP installation. Type command “sudo ./<install file> <tar file> <public key>,” and press Enter.
Example: sudo ./ONPLniInstaller.sh CONP-xx.xx.xx.xx.tar.gz CONP-xx.xx.xx.xx_pem.pubkey
|
Step 10
|
Enter y or n to change the default IP address.
Would you like to change the IP (y/n)
If you enter n, the installation proceeds with the same IP address as mentioned above and if you enter y, you must provide the IP address and the installation proceeds with the IP address that is provided by you.
ONP Host IP: 10.76.82.14
LNI Host IP: 10.76.82.14
|
Step 11
|
Enter y or n to install the ONP or ONP and LNI packages.
Would you like to install complete ONP+LNI package ? (y/n) [default: n] If no, then only ONP will be installed:
By default, the value that is considered for installation is n.
Install complete ONP and LNI packages for Live Network Import (LNI) feature. Otherwise proceed with only ONP installation.
Enter n for ONP package installation. Enter y for ONP and LNI packages installation.
|
Step 12
|
Enter your ONP database credentials:
Note
|
Make sure to use ONLY alphabets or numbers.
If you are installing Cisco ONP for the first time, you must set the username and password for the database.
Would you like to set database username and password (y/n).
If you enter y, then prompt appears and asks you to enter username and password. If you enter n, you can proceed with the next step.
From Release 5.1, Cisco ONP database is powered by Postgres DB. You must set the username and password for the Postgres database.
|
Enter your ONP database username, only alphanumeric characters are valid [user]:
Enter your ONP database password, only alpha numeric characters are valid (len >= 8 and <= 64 characters) [password]:
Repeat your ONP database password.
|
Step 13
|
Enter y or n to migrate your current data to the new release.
Are you on CONP 5.0 and would like to migrate data to CONP 5.1 (y/n):
-
If you enter y for data migration, you must provide Cisco ONP R5.0 Mongo DB username and password.
Enter your CONP 5.0 Mongo database username, only alpha numeric characters are valid [user]:
Enter your CONP 5.0 Mongo database password, only alpha numeric characters are valid (len >= 8 and <= 64 characters) [password]: *********
Note
|
MongoDB username and password is not recoverable. If you forget the MongoDB username and password, then reinstall Cisco ONP R5.0 by setting new username and password for MongoDB and then install R5.1.
|
-
If you enter n for data migration, the following prompt appears.
CONP 5.0 users, networks, aliens etc. will be lost. Are you sure NOT to migrate data to CONP 5.1 (y/n):
If you enter y, installation proceeds without migrating data from Release 5.0. After installation, no user profiles and networks information
will be present. This is equivalent to fresh installation of Release 5.1. But if needed, you can still recover the users and
networks information if MongoDB is present in the server. Delete postgres mount (/var/lib/postgresdb_cnp) and redo installation
with data migration from Release 5.0.
Note
|
For fresh Cisco ONP installation, you must enter n.
|
|
Step 14
|
If you chose to install ONP package alone, go to Step 20. Else continue with below steps which are required for ONP and LNI packages installation.
|
Step 15
|
Enter your LNI database credentials:
Please enter your Username LNI database: (Maximum 12 chars)
Please enter Password for LNI database (Min chars, Maximum 64 chars):
Please repeast Password for LNI database (Min chars, Maximum 64 chars):
|
Step 16
|
Enter y or n to reserve disk space for log storage.
Application will reserve 10 GB for logs. Do you want to change this value? (y/n):
If you enter n, Cisco ONP allocates the default disk space. If you enter y, you must allocate the disk space.
|
Step 17
|
Enter the disk space for the log storage:
Please enter maximum available disk space in GB for log storage (from 5 to 50):
|
Step 18
|
Enter y or n to provide encryption key for device credentials.
Do you want to provide encryption key for device credentials (y/n):
If you enter n, Cisco ONP uses the default encryption key. If you want to provide encryption key for the LNI device, enter y and enter the encryption key.
|
Step 19
|
If you entered n, skip this step. Otherwise, enter the encryption key for device credentials:
Please enter encryption key for device credentials (Min 8 chars, Max 64 chars):
|
Step 20
|
Wait for the installation to complete.
Note
|
The Cisco ONP services start automatically, after you successfully install the build.
The install logs are located in the following path:
/var/log/cnp/install.log
|
Run the following command to see the list of services running:root:~/$ONP_HOME# sudo docker ps
You can confirm the successful installation based on whether the following services are up and running for more than five
minutes:
For only ONP installation:
-
cnp_cnp
-
cnp_ode.1
-
cnp_ode.2
-
cnp_ode.3
-
cnp_pce.1
-
cnp_pce.2
-
cnp_cnp_frontend
-
cnp_gene
-
cnp_postgres
For ONP and LNI installation, you can see the following services along with the services that are mentioned earlier for ONP
only:
-
lni_modelaggregatorservice
-
lni_circuitservice
-
lni_inventoryservice
-
lni_topologyservice
-
lni_collectorservice
-
lni_lniBroker
-
lni_devicemanager
-
lni_apigw
-
lni_ncs1kinventoryadapterservice
-
lni_ncs4kinventoryadapterservice
-
lni_ncs2kinventoryadapterservice
-
lni_netconfadapterservice
-
lni_tl1adapterservice
-
lni_kafka
-
lni_netconfPluginService
-
cnp_postgres
-
lni_mongo_1
-
lni_servicediscovery
-
lni_tl1PluginService
-
lni_zookeeper
|
Step 21
|
After you confirm that all the mentioned services in the previous step are up, you can access the Cisco ONP using the Google Chrome browser pointing to Ubuntu server hostname or IP address.
|