The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This chapter contains the following sections:
Installing Cisco Nexus Data Broker in Centralized Mode
Direct upgrade path to Cisco Nexus Data Broker Release 3.2.2 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.2.2.
Use the upgrade command to upgrade to Cisco Nexus Data Broker Release 3.2.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 or Release 3.1.0 or Release 3.2.0, or Release 3.2.1 and only then you can upgrade to Cisco Nexus Data Broker Release 3.2.2. 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.2.2, you cannot use the downgrade option to rollback to 3.2.1, 3.2.0 or 3.1.0 or 3.0.0. You have to use the configuration archive that is created during the upgrade process to rollback the software. |
Note | When you upgrade the software, the hostname should not be changed during the upgrade process. While upgrading to Cisco Nexus Data Broker Release 3.2.2, user should not allowed to change the hostname. If the hostname is changed during the upgrade, the upgrade process is not done successfully. |
When you execute the upgrade command, the installation and the configuration are upgraded. However, any changes you made to the shell scripts or configuration files, for example, runxnc.sh and config.ini, are overwritten. After you complete the upgrade process, you must manually reapply your changes to those files.
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.
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 and runxnc.sh files.
You should manually backup your config.ini and runxnc.sh files 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 after upgrading from Cisco Nexus Data Broker, make sure that you upgrade your current Java version and you have set JAVA_HOME to point to the correct JAVA version. If the current Java version used is lower than 1.8.0_45, the Java process does not start and it does not get the Web access. |
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. |
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.2.1 application bundle: Cisco Nexus Data Broker Software Application—ndb1000-sw-app-k9-3.2.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.2.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.2.2 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.
| ||||||||||||||||||
Step 15 | If you have
any upgrade-related issues, perform the following tasks:
|
You can use one of the following options:
|
Step 1 | Navigate to the xnc directory that was created when you installed the software. |
Step 2 | Verify that the
application is running by entering the
./runxnc.sh
-status command.
The controller outputs the following, which indicates that the controller is running the Java process with PID 21680: Controller with PID:21680 -- Running! |
Connect the switches to the controller. For more information, see the configuration guide for your switches.