Installing or Upgrading the Cisco Nexus Data Broker Software in Centralized Mode
Important |
Beginning with Cisco Nexus Data Broker, Relese 3.8.1, you can directly upgrade the previous versions of Cisco Nexus Data Broker to the latest Cisco Nexus Data Broker version. |
Note |
To add a device to NDB in centralized mode, use the device IP address or the device hostname. |
-
To complete a new installation of Cisco Nexus Data Broker, see the Installing the Cisco Nexus Data Broker Software section.
Installing the Cisco Nexus Data Broker Software in Centralized Mode
Complete these steps to install Cisco Nexus Data Broker software in Centralized mode:
Procedure
Step 1 |
In a web browser, navigate to www.cisco.com. |
||||||
Step 2 |
Under Support, click All Downloads. |
||||||
Step 3 |
In the center pane, click Cloud and Systems Management. |
||||||
Step 4 |
If prompted, enter your Cisco.com username and password to log in. |
||||||
Step 5 |
In the right pane, click Network Controllers and Applications, and then click Cisco Nexus Data Broker. The file information for Release 3.8.1 is displayed: Cisco Nexus Data Broker Software Application: ndb1000-sw-app-k9-3.8.1.zip |
||||||
Step 6 |
Download the Cisco Nexus Data Broker application bundle. |
||||||
Step 7 |
Create a directory in your Linux machine where you plan to install Cisco Nexus Data Broker. For example, in your Home directory, create CiscoNDB. |
||||||
Step 8 |
Copy the Cisco Nexus Data Broker zip file into the directory that you created. |
||||||
Step 9 |
Unzip the Cisco Nexus Data Broker zip file. The Cisco Nexus Data Broker software is installed in a directory called xnc. The directory contains the following:
|
Upgrading the Application Software in Centralized Mode Using CLI
Use the upgrade command to upgrade to Cisco NDB Release 3.8.1.
Note |
|
Before you begin
-
Stop all controller instances that use the Cisco Nexus Data Broker installation. This will avoid conflicts with the file system, which is updated during the upgrade.
-
For NDB configuration upload or Backup/Restore process, first bring up the NDB instance where configuration is uploaded or where Backup/Restore is done, then start rest of the nodes in the cluster.
-
Backup up the NDB configuration. For more information, see Backing Up or Restoring the Configuration Using NDB GUI section.
-
If you are using high availability clustering, stop all application instances in the cluster to ensure that there are no inconsistencies.
-
Back up your config.ini file.
Important |
You should manually backup your config.ini file before upgrading, because the backup process does not back them up for you. If you do not backup your files before upgrading, any changes you made will be lost. |
Note |
When you run runxnc.sh script, there is a thread in the script that monitors the log and the Cisco Nexus Data Broker JAVA process to monitor the health of the Cisco Nexus Data Broker. The default value for this option is 30 Seconds. |
Procedure
Step 1 |
In a web browser, navigate to Cisco.com. |
||||||||||||||
Step 2 |
Under Support, click All Downloads. |
||||||||||||||
Step 3 |
In the center pane, click Cloud and Systems Management. |
||||||||||||||
Step 4 |
In the right pane, click Network Controllers and Applications, and then click Cisco Nexus Data Broker. |
||||||||||||||
Step 5 |
Download the Cisco NDB Release 3.8.1 applicable bundle: Cisco Nexus Data Broker Software Application—ndb1000-sw-app-k9-.zip |
||||||||||||||
Step 6 |
Create a temporary directory in your Linux machine where you plan to upgrade to Cisco NDB. |
||||||||||||||
Step 7 |
Unzip the Cisco NDB Release 3.8.1 zip file into the temporary directory that you created. |
||||||||||||||
Step 8 |
Navigate to the xnc directory that was created when you installed the Cisco Nexus Data Broker release earlier. |
||||||||||||||
Step 9 |
Backup your Cisco Nexus Data Broker release installation using your standard backup procedures. |
||||||||||||||
Step 10 |
Stop running all Cisco Nexus Data Broker release processes. |
||||||||||||||
Step 11 |
Navigate to the xnc/bin directory in the temporary directory that you created for Cisco NDB Release 3.8.1 upgrade software. |
||||||||||||||
Step 12 |
Upgrade the application by entering the ./xnc upgrade --perform --target-home {xnc_directory_to_be_upgraded} [--verbose] [--backupfile {xnc_backup_location_and_zip_filename}] command. You can use one of the following options:
|
||||||||||||||
Step 13 |
Navigate to the xnc directory where you originally installed Cisco XNC Monitor Manager. |
||||||||||||||
Step 14 |
If TLS certification is enabled between NDB server and NXOS switch, copy the tlsTrustStore and tlsKeyStore files to /xnc/configuration from the old xnc backup. |
||||||||||||||
Step 15 |
Start the application processes that you previously stopped.
|
||||||||||||||
Step 16 |
If the secondary/cluster NDB server is configured, start the server.
|
Upgrading the Application Software in Centralized Mode Using GUI
Complete the following steps to upgrade the application software in the Centralized mode using GUI:
Procedure
Step 1 |
Log into NDB. |
Step 2 |
Navigate to the System tab under Administration. The System Administration window is displayed. |
Step 3 |
Click Download Configuration to download the switch configuration file in a .zip file format. The default name of the zip file is configuration_startup.zip. OR Navigate to the Backup/Restore tab under Administration > System tab. Click Backup and Backup Locally to download the configuration in zip file format. |
Step 4 |
Stop the current NDB instance using the runxnc.sh -stop command. Example:
|
Step 5 |
If TLS certification is enabled between NDB server and NXOS switch, copy the tlsTrustStore and tlsKeyStore files to /xnc/configuration from the old xnc backup. |
Step 6 |
Start the new NDB installation using the runxnc.sh -start command. Example:
|
Step 7 |
Navigate to the Backup/Restore tab under Administration > System tab. |
Step 8 |
Click Restore Locally and upload the configuration_startup.zip |
Step 9 |
Restart the new NDB instance using the runxnc.sh -restart command. Example:
|
Upgrading NDB Using the Hitless Method
You can upgrade Cisco NDB using the either the upload or the CLI upgrade hitless methods.
Upgrading Cisco NDB - Hitless Method (Using Upload)
You can upgrade Cisco NDB to Release 3.8.1 with the hitless method using upload.
Before you begin
If the Cisco NDB version is earlier than Release 3.8, you must edit the config.ini file and update the skipConfigurtionStateDBfiles key to false on both the controllers, and restart all the earlier version controllers.
Procedure
Step 1 |
Log into NDB. |
||
Step 2 |
Navigate to the location (/home/3.8.1/xnc) of the xnc for Release 3.8.1 in both, server 1 and server 2. |
||
Step 3 |
Navigate to the System tab under Adminstration to view the System Administration window. |
||
Step 4 |
Navigate to to download the configuration in zip file format and save it on your local desk.
|
||
Step 5 |
Verify the versions of the servers to confirm that it displays Release 3.8.1. Also, verify that the primary server and member is assigned. |
||
Step 6 |
If TLS certification is enabled between NDB server and NXOS switch, copy the tlsTrustStore and tlsKeyStorefiles to /xnc/configuration from the old xnc backup. |
||
Step 7 |
Navigate to to upload the configuration to the primary server. Stop Cisco NDB on the second server and restart the first server. After you restart the server, Release 3.8.1 configurations are successfully uploaded in Cisco NDB Release 3.8.1 Verify all the configurations. |
||
Step 8 |
If secondary / cluster NDB server is configured, start the server.
|
Upgrading NDB - Hitless Method (Using CLI)
You can upgrade Cisco NDB to Release 3.8.1 with the hitless method using CLI.
Before you begin
If the Cisco NDB version is earlier than Release 3.8, you must edit the config.ini file and update the skipConfigurtionStateDBfiles key to false on both the controllers, and restart all the earlier version controllers.
Procedure
Step 1 |
Stop both the servers. |
||
Step 2 |
Navigate to the the s server location /home/3.8.1/xnc/bin and enter the . /xnc upgrade --perform --target-home {xnc directory to be upgraded} --verbose command.
|
||
Step 3 |
Navigate to the the secondary server location /home/3.8.1/xnc/bin and enter the . /xnc upgrade --perform --target-home {xnc directory to be upgraded} --verbose command.
|
||
Step 4 |
If TLS certification is enabled between NDB server and NXOS switch, copy the tlsTrustStore and tlsKeyStore files to /xnc/configuration from the old xnc backup in the primary and secondary servers. |
||
Step 5 |
Navigate to the Cisco NDB Release 3.8.1 XNC directory in the primary server and start Cisco NDB using the ./runxnc.sh –start command. |
||
Step 6 |
Login to Cisco NDB and verify that the Cisco NDB version is displayed as Release 3.8.1. Verify that the primary configuration and the other configurations are retained. |
||
Step 7 |
If secondary / cluster NDB server is configured, start the server.
|