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 XNC
There is no direct upgrade path from Cisco XNC Release 1.0 to Cisco XNC Release 1.7. If you have Cisco XNC Release 1.0 installed and you want to update to Cisco XNC Release 1.7, you must first upgrade to Cisco XNC Release 1.5. See the Cisco Extensible Network Controller Deployment Guide, Release 1.5 for the procedure.
To complete a new installation of Cisco XNC, see Installing the Cisco Extensible Network Controller Application.
To upgrade Cisco XNC Release 1.5 or Release 1.6 to Cisco XNC Release 1.7, see Upgrading the Application Software.
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 | 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 Extensible Network Controller (XNC). | ||||||
Step 6 | Download the Cisco XNC application bundle and any additional applications that you have purchased. | ||||||
Step 7 | Create a directory
in your Linux machine where you plan to install
Cisco
XNC.
For example, in your Home directory, create CiscoXNC. | ||||||
Step 8 | Copy the Cisco XNC zip file into the directory that you created. | ||||||
Step 9 | Unzip the
Cisco
XNC zip file.
The Cisco XNC software is installed in a directory called xnc. The directory contains the following:
|
You can use the upgrade command to upgrade a Cisco XNC Release 1.5 or Release 1.6 installation to Cisco XNC Release 1.7. This upgrade is called an in-place upgrade, which means that the product bits are replaced. A backup archive is created to restore your original installation, if necessary.
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.
Use the same type of installer that you used when installing Cisco Extensible Network Controller (XNC) Release 1.5 or Release 1.6. For example, if you have Cisco XNC with the Topology Independent Forwarding (TIF) application installed, you must use the installation software for Cisco XNC with TIF.
If you have upgraded from Cisco XNC Release 1.5 to Cisco XNC Release 1.6, reset the password, start the controller and save the configuration using the Save button at the top of the menu bar in the Cisco XNC GUI.
Stop all controller instances that use the Cisco XNC 1.5 or 1.6 installation. This will avoid conflicts with the file system, which is updated during 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.
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 Extensible Network Controller (XNC). | ||||||||||||||||||
Step 5 | Download the Cisco Extensible Network Controller (XNC) Release 1.7 application bundle and any additional applications that you currently have installed. | ||||||||||||||||||
Step 6 | Create a
temporary directory in your Linux machine where you plan to upgrade
Cisco
XNC.
For example, in your Home directory, create CiscoXNC_Upgrade. | ||||||||||||||||||
Step 7 | Extract the Cisco XNC Release 1.7 zip file into the temporary directory that you created. | ||||||||||||||||||
Step 8 | Navigate to the xnc directory that was created when you installed the Cisco XNC Release 1.5 or 1.6 software. | ||||||||||||||||||
Step 9 | Stop all running release 1.5 or release 1.6 processes. | ||||||||||||||||||
Step 10 | Backup your release 1.5 or release 1.6 installation using your standard backup procedures. | ||||||||||||||||||
Step 11 | Navigate to the xnc/bin directory in the temporary directory that you created for the Cisco XNC Release 1.7 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. | ||||||||||||||||||
Step 14 | Start the
application processes
that you previously stopped.
| ||||||||||||||||||
Step 15 | If you have
any upgrade-related issues, perform the following tasks:
|
You must purchase additional Cisco XNC applications and download the .zip files from Cisco.com. We recommend that you backup your configuration before you install new applications.
Step 1 | Open a command window where you installed Cisco XNC. |
Step 2 | Navigate to the xnc directory that was created when you installed the software. |
Step 3 | 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.