Installing or Upgrading the Cisco Nexus Data Broker Software in Centralized Mode
Important |
Direct upgrade path to Cisco Nexus Data Broker Release 3.7.1 is available from Cisco Nexus Data Broker release 3.0 or above. If you are running a previous release, upgrade to Release 3.0 first before upgrading to Release 3.7.1. |
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
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.7.1 is displayed: Cisco Nexus Data Broker Software Application: ndb1000-sw-app-k9-3.7.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
Use the upgrade command to upgrade to Cisco Nexus Data Broker Release 3.7.1. When you are upgrading from Release 2.2.0 and/or Release 2.2.1, you first need to upgrade to Release 3.0.0 and only then you can upgrade to Cisco Nexus Data Broker Release 3.7.1. This upgrade is an in-place upgrade, which means that the product bits are replaced. A backup archive is created to restore your original installation, if necessary.
Note |
Once you upgrade to Cisco Nexus Data Broker Release 3.7.1, you cannot use the downgrade option to rollback to a previous release. You have to use the configuration archive that is created during the upgrade process to rollback the software. |
Note |
When you upgrade the software to Cisco Nexus Data Broker Release 3.2 or later release, the hostname should not be changed during the upgrade process. If the hostname is changed during the upgrade process, the upgrade might fail. If you are upgrading from release 2.x, 3.0 and 3.1, the domain name configuration in the switch should be removed before upgrading the software. |
When you run the upgrade command, the installation and the configuration are upgraded. However, any changes you made to the shell scripts or configuration files, for example, config.ini, are overwritten. After you complete the upgrade process, you must manually reapply your changes to those files.
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.
-
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.
-
All the HA cluster members send keepalive message every 3 seconds. If a peer does not respond to keepalive message, peers attempt three retries to determine whether the peer is alive or dead. If a peer does not respond even after three retries, split-brain situation occurs where multiple HA members act as coordinators.
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 Nexus Data Broker Release 3.7.1 application bundle: Cisco Nexus Data Broker Software Application—ndb1000-sw-app-k9-3.7.1.zip |
||||||||||||||||
Step 6 |
Create a temporary directory in your Linux machine where you plan to upgrade to Cisco Nexus Data Broker. For example, in your Home directory, create CiscoNDB_Upgrade. |
||||||||||||||||
Step 7 |
Unzip the Cisco Nexus Data Broker Release 3.7.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 the Cisco Nexus Data Broker Release 3.7.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 |
Start the application processes that you previously stopped.
|