Licensing, Upgrading, and Downgrading

Transcription

1 Licensing, Upgrading, and Downgrading :52:06 UTC 2015 Citrix Systems, Inc. All rights reserved. Terms of Use Trademarks Privacy Statement

2 Contents Licensing, Upgrading, and Downgrading... 4 Citrix NetScaler Migration... 5 New and Deprecated Commands, Parameters, and SNMP OIDs... 6 New Commands... 7 Deprecated Commands... 8 New Parameters... 9 Deprecated Parameters New SNMP OIDs Upgrading or Downgrading the System Software Changes to the Licensing Framework NetScaler Licenses Obtaining NetScaler Licenses Installing NetScaler Licenses Verifying the Licensed Features Enabling or Disabling a Feature Access Gateway Universal License Obtaining the Universal License Installing the Universal License Verifying Installation of the Universal License Upgrading to Release Upgrading a Standalone NetScaler Upgrading a High Availability Pair Upgrading to a Later Build within Release Upgrading a Standalone NetScaler to a Later Build Upgrading a NetScaler High Availability Pair to a Later Build Downgrading from Release Downgrading a Standalone NetScaler Downgrading a High Availability Pair Downgrading to an Earlier Build within Release

3 Downgrading a Standalone NetScaler to an Earlier Build Downgrading a NetScaler High Availability Pair to an Earlier Build 54 Auto Cleanup

4 Licensing, Upgrading, and Downgrading The following topics describe the migration instructions for setting up a new version of a NetScaler with a list of all new and deprecated commands, parameters, and SNMP OIDs. New and Deprecated Commands, Parameters, and SNMP OIDs Upgrading or Downgrading the System Software Lists the foundational changes that affect the base system and its configuration, including new and deprecated commands, parameters, and SNMP OIDs. Describes the licensing framework and the procedure for upgrading or downgrading the system software across releases and within a release. 4

5 New and Deprecated Commands, Parameters, and SNMP OIDs Welcome to the NetScaler 10 system software release. There are new commands, parameters, and SNMP OIDs in this release. Some commands, parameters, and SNMP OIDs will be deprecated in this release. For complete descriptions of the new commands and parameters, see "Command Reference". For complete descriptions of the SNMP OIDs, see the Citrix NetScaler SNMP OID Reference Guide at " 5

6 New and Deprecated Commands, Parameters, and SNMP OIDs Welcome to the NetScaler 10 system software release. There are new commands, parameters, and SNMP OIDs in this release. Some commands, parameters, and SNMP OIDs will be deprecated in this release. For complete descriptions of the new commands and parameters, see "Command Reference". For complete descriptions of the SNMP OIDs, see the Citrix NetScaler SNMP OID Reference Guide at " 6

7 ns-migration-new-cmds-10-ref Due to technical difficulties, we are unable to display this topic. Citrix is currently fixing this problem. In the meantime, you can view this topic online: 7

8 Deprecated Commands The following commands are deprecated in release 10. rm vserver set vserver unset vserver enable vserver disable vserver add lb wlm rm lb wlm set lb wlm show lb wlm bind lb wlm unbind lb wlm add ns limitselector rm ns limitselector set ns limitselector show ns limitselector add ns appflowcollector rm ns appflowcollector show ns appflowcollector set ns appflowparam show ns appflowparam 8

9 ns-migration-new-params-10-ref Due to technical difficulties, we are unable to display this topic. Citrix is currently fixing this problem. In the meantime, you can view this topic online: 9

10 Deprecated Parameters The following parameters are deprecated in release 10. add service -serverid set service -serverid unset service -serverid bind servicegroup -serverid add dns policy -viewname -preferredlocation -drop -cachebypass set dns policy -viewname -preferredlocation -drop -cachebypass show dns aaaarec [<IPv6Address>] show dns addrec [<IPAddress>] show dns mxrec [-mx <string>] show dns nsrec [<nameserver>] show dns ptrrec [<domain>] add lb monitor -destip * set lb monitor -destip * add gslb vserver -backupsessiontimeout set gslb vserver -backupsessiontimeout set ns config -httpport -maxconn -maxreq -cip -cookieversion -securecookie -pmtumin -pmtutimeout -ftpportrange -crportrange -timezone -grantquotamaxclient -exclusivequotamaxclient -grantquotaspillover -exclusivequotaspillover unset ns config -ftpportrange -crportrange -timezone set ns -tcpparam -KAprobeUpdateLastactivity add ssl policy -reqaction 10

11 New SNMP OIDs The following table lists the new SNMP OIDs in release 10. OID Application firewall Description AppFirewall SNMP traps dropped due to time limit. Cluster The cluster table. This is indexed on the clid This represents the unique id of the cluster node This represents the IP address of the cluster node Load Balancing The name of the server of the servicegroup member Number invalid requests/responses on this vserver Number invalid requests/responses dropped on this vserver Networking This represents whether ISIS feature is enabled or disabled on NetScaler This provides statistical information about the configured PBR6s, in the rs9000 product family of NetScaler products This table contains all the PBRs configured. This is indexed on the acpbrname The name of the PBR6 The full name of the PBR6 The priority of the PBR6 Number of times the pbr6 was hit Total packets that matched the PBR6 with action ALLOW Total packets that matched PBR6 with action DENY Total packets that matched one of the configured PBR6 11

12 New SNMP OIDs Total packets that did not match any PBR This provides statistical information about the total number of megabits received/transmitted on the Network Interfaces configured in the Netscaler product Number of megabits received by the NetScaler appliance Number of megabits transmitted by the NetScaler appliance the state of HA License check SSL This represents the interpretation details of sslcardstatus. System The model ID is populated if the system is such that it is license controlled. If the system does not support license based models, then the model id will be zero Current threshold for TCP rate control. By default, there is no rate control for TCP This represents the status of CallHome Upload Event. 12

13 Upgrading or Downgrading the System Software NetScaler 10 offers new and updated features with increased functionality. A comprehensive list of enhancements is listed in the release notes accompanying the release announcement. Take a moment to read this document before you upgrade your software. It is important to understand the licensing framework and types of licenses before you upgrade your software. A software edition upgrade may require new licenses, such as upgrading from the standard edition to the enterprise edition, the standard edition to the platinum edition, or the enterprise edition to the platinum edition. Note: For upgrading or downgrading the nodes in a cluster setup, see "Upgrading or Downgrading the Cluster Software". 13

14 Changes to the Licensing Framework The licensing framework has changed since release 8.1, build For more information, see " Citrix NetScaler Application Accelerator users have been upgraded to the Access Gateway Enterprise Edition without any change in functionality. 14

15 NetScaler Licenses A NetScaler must be properly licensed before it can be deployed to distribute, optimize, or secure network traffic for Web applications. After you have obtained the licenses, you must install the licenses on your appliance, and then verify that the features corresponding to these licenses are enabled. 15

16 Obtaining NetScaler Licenses The procedure to obtain NetScaler licenses has changed. For more information, see " 16

17 Installing NetScaler Licenses Install each license to use the feature controlled by that license. To install the licenses by using the command line interface 1. Open an SSH connection to the NetScaler by using an SSH client, such as PuTTY. 2. Log on to the NetScaler by using the administrator credentials. 3. Switch to the shell prompt, create a license subdirectory in the nsconfig directory, if it does not exist, and copy the new license file(s) to this directory. Example login: nsroot Password: nsroot Last login: Mon Aug 4 03:37: from Done > shell Last login: Mon Aug 4 03:51:42 from root@ns# mkdir /nsconfig/license root@ns# cd /nsconfig/license Copy the new license file(s) to this directory. Note: The NetScaler appliance does not prompt for a reboot option when you use the command line interface to install the licenses. Run the reboot -w command to warm reboot the system, or run the reboot command to reboot the system normally. 17

18 Installing NetScaler Licenses To install the licenses by using the configuration utility 1. In a Web browser, type the IP address of the NetScaler, such as 2. In User Name and Password, type the administrator credentials. 3. In Start in, select Configuration, and then click Login, as shown in the following figure. Figure 1. Login Screen 4. In the navigation pane, expand System, and then click Licenses. 5. In the Licenses pane, click Manage Licenses. If the /nsconfig/license directory does not exist, you are prompted to create it. 6. In the Manage Licenses dialog box, click Add. 7. In the Select License Files dialog box, navigate to the location of the license files and select the file you want to upload (for example, Citrix NetScaler IPv6 - Option.lic). 8. Click Select. 18

19 Installing NetScaler Licenses 9. After your file is uploaded to the license directory, click OK. 10. When prompted to restart the NetScaler, do one of the following: If you plan to upgrade your software, click No. If you don t plan to upgrade your software, click Yes to restart the NetScaler. 19

20 Verifying the Licensed Features Before using a feature, make sure that your license supports the feature. To verify the licensed features by using the command line interface 1. Open an SSH connection to the NetScaler by using an SSH client, such as PuTTY. 2. Log on to the NetScaler by using the administrator credentials. 3. At the command prompt, enter the sh ns license command to display the features supported by the license. Example sh ns license License status: Web Logging: YES Surge Protection: YES... Done HTML Injection: YES 20

21 Verifying the Licensed Features To verify the licensed features by using the configuration utility 1. In a Web browser, type the IP address of the NetScaler, such as 2. In User Name and Password, type the administrator credentials. 3. In Start in, select Configuration, and then click Login, as shown in the following figure. Figure 1. Login Screen 4. In the navigation pane, expand System, and then click Licenses. You will see a green check mark next to the licensed features. 21

22 Enabling or Disabling a Feature When you use the NetScaler for the first time, you need to enable a feature before you can use its functionality. If you configure a feature before it is enabled, a warning message appears. The configuration is saved but it will apply only after the feature is enabled. To enable a feature by using the command line interface At the NetScaler command prompt, type the following commands to enable a feature and verify the configuration: enable feature <FeatureName> show feature Example enable feature lb cs done >show feature Feature Acronym Status ) Web Logging WL OFF 2) Surge Protection SP ON 3) Load Balancing LB ON 4) Content Switching CS ON 5) Cache Redirection CR ON... 24) NetScaler Push push OFF Done The example shows how to enable load balancing (lb) and content switching (cs). If the license key is not available for a particular feature, the following error message appears for that feature: ERROR: feature(s) not licensed Note: To enable an optional feature, you need a feature-specific license. For example, if you have purchased and installed the Citrix NetScaler Enterprise Edition license and need to enable the Integrated Caching feature, you first need to purchase and install the AppCache license. 22

23 Enabling or Disabling a Feature To disable a feature by using the command line interface At the NetScaler command prompt, type the following commands to disable a feature and verify the configuration: disable feature <FeatureName> show feature Example > disable feature lb Done > show feature Feature Acronym Status ) Web Logging WL OFF 2) Surge Protection SP ON 3) Load Balancing LB OFF 4) Content Switching CS ON... 24) NetScaler Push push OFF Done > The example shows how to disable load balancing (lb). 23

24 Access Gateway Universal License The Access Gateway universal license limits the number of concurrent user sessions to the number of licenses purchased. If you purchase 100 licenses, you can have 100 concurrent sessions at any time. When a user ends a session, that license is released for the next user. A user who logs on to the Access Gateway from more than one computer occupies a license for each session. If all licenses are occupied, no additional connections can be opened until a user ends a session or the administrator terminates the session using the configuration utility. When a connection is closed, the license is released and can be used for a new user. 24

25 Obtaining the Universal License You need the following information before going to the Citrix Web site for the universal license. The license code You can find the code on the Access Gateway CD, in an you receive from Citrix, or from the Subscription Advantage Management-Renewal-Information (SAMRI) system. Your user ID and password for My Citrix Register at My Citrix ( to receive your user ID and password. Note: If you cannot locate either the license code or your user ID and password, contact Citrix Customer Service. The host name of the Access Gateway The entry field for this name on My Citrix is case-sensitive, so make sure that you copy the host name exactly as it is configured on the NetScaler. The number of licenses you want to include in the license file You do not have to download all of the licenses you are entitled to at once. For example, if your company purchased 100 licenses, you can choose to download 50. You can allocate the rest in another license file at a later time. Multiple license files can be installed on the Access Gateway. Note: Before obtaining your licenses, make sure you configure the host name of the NetScaler using the Setup Wizard and then restart the NetScaler. To obtain your universal license 1. In a Web browser, go to and click My Citrix. 2. Enter your user name and password. If this is the first time you are logging on to the site, you are asked for additional background information. 3. Under My Tools, point to Choose a toolbox, and click Activation System/Manage Assets. 4. In the Current Tool drop-down menu, select Activate/Allocate and follow the directions to obtain your license file. 25

26 Installing the Universal License To install the license, see "Installing NetScaler Licenses". After installation, verify that the license was installed correctly. 26

27 Verifying Installation of the Universal License Before proceeding, verify that your universal license is installed correctly. To verify installation of the universal license by using the command line interface 1. Open an SSH connection to the NetScaler by using an SSH client, such as PuTTY. 2. Log on to the NetScaler by using the administrator credentials. 3. Use the show license command to verify that SSL VPN = YES and that Maximum Users has increased from 5 to the expected number of concurrent users. To verify installation of the universal license by using the configuration utility 1. In a Web browser, type the IP address of the NetScaler, such as 2. In User Name and Password, type the administrator credentials. 3. In the navigation pane, expand System, and then click Licenses. 4. In the Licenses pane, you will see a green check mark next to Access Gateway. The field Maximum Access Gateway Users Allowed displays the number of concurrent user sessions licensed on the NetScaler. 27

28 Upgrading to Release 10 You can upgrade to release 10 on a standalone NetScaler or a high availability (HA) pair by using the configuration utility or the command line interface. Important: If an IPv6 address is configured as the NetScaler IP (NSIP) address, upgrading from release 8.1 to release 10 changes the NSIP address to the subnet IP (SNIP) address. To add the NSIP address after the upgrade, at the command line interface, type: rm ns ip6 add ns ip6 <ipv6 address> -type NSIP. There is no change if the NSIP address is an IPv4 address. 28

29 Upgrading a Standalone NetScaler Before upgrading the system software, make sure that you have the required licenses. For more information, see "NetScaler Licenses". Software upgrades from 8.x to 9.x, 8.x and 9.x to 10, and 8.x, 9.x, and 10.x to 10.1 do not require a new license. Note: When upgrading from release 8.0, 8.1, 9.0, 9.1, 9.2, or 9.3 you have the option to use the configuration utility. All upgrades can be performed by using the command line interface, which is the recommended option. When using the upgrade wizard in the configuration utility to upgrade from release 8.0, do not use the Device option to upload your software. To upgrade a standalone NetScaler running release 8.1, 9.0, 9.1, 9.2, 9.3 by using the command line interface In the following procedure, <release> and <releasenumber> represent the release version you are upgrading to, and <targetbuildnumber> represents the build number that you are upgrading to. Refer to the table below for specific values. Table 1. Release Version Values Release Version <release> <releasenumber> rhodes andes Open an SSH connection to the NetScaler by using an SSH client, such as PuTTY. 2. Log on to the NetScaler by using the administrator credentials. Save the running configuration. At the prompt, type:save config 3. Create a copy of the ns.conf file. At the shell prompt, type: a. cd /nsconfig b. cp ns.conf ns.conf.ns<releasenumber><currentbuildnumber> You should backup a copy of the configuration file on another computer. 4. Create a <releasenumber>nsinstall subdirectory in the /var/nsinstall directory. 5. Change directory to /var/nsinstall/<releasenumber>nsinstall, create a directory named build_<targetbuildnumber>, and change to this directory. 29

30 Upgrading a Standalone NetScaler 6. Download or copy the installation package (build-<release>-<build number>_nc.tgz) and the documentation bundle (ns-<releasenumber>-<build number>-doc.tgz) to this directory and extract the contents of the installation package. To download the installation package from the Citrix Web site, follow the steps below: a. Go to MyCitrix.com, log on using your credentials, and click Downloads. b. In the Select a Product, select NetScaler ADC. c. Under Firmware, click the release and build number to download. d. Click Get Firmware. e. Click Show Documentation and then click Get Documentation. 7. Run the installns script to install the new version of the system software. Note: To install a FIPS appliance, run the installns script with the -F option. To automatically clean up the flash, run the installns script with the -c option. If the configuration file for the build that you are upgrading to exists on the appliance, you are prompted to load that configuration, as shown in the following figure. Figure 1. Upgrade menu if configuration file exists Warning: When upgrading to the NetScaler 10 ncore build, the installation script prompts you to delete the /var directory if the swap partition is smaller than 32 gigabytes (GB). If you receive this prompt, type N, save any important files located in /var to a backup location, and then re-run the installation script. 30

31 Upgrading a Standalone NetScaler If the free space available on the flash drive is insufficient to install the new build, the NetScaler prompts you to initiate a cleanup of the flash drive. For more information, see "Auto Cleanup". 8. When prompted, restart the NetScaler. Example login: nsroot Password: nsroot Last login: Mon Mar 26 03:37: from Done > save config > shell Last login: Mon Mar 26 03:51:42 from root@nsnnn# cd /var/nsinstall root@nsnnn# cd 10nsinstall root@nsnnn# mkdir build_53 root@nsnnn# cd build_53 root@nsnnn# ftp... get build _nc.tgz root@nsnnn# get ns doc.tgz root@nsnnn# tar xzvf build _nc.tgz root@nsnnn#./installns installns version ( ) kernel (ns _nc.gz) Copying ns _nc.gz to /flash/ns _nc.gz... Installing documentation Installation has completed. Reboot NOW? [Y/N] Y 31

32 Upgrading a Standalone NetScaler To upgrade a standalone NetScaler running release 8.1, 9.0, 9.1, 9.2, 9.3 by using the configuration utility 1. In a Web browser, type the IP address of the NetScaler, such as 2. In User Name and Password, type the administrator credentials. 3. In Start in, select Configuration, and then click Login, as shown in the following figure. 4. In the configuration utility, in the navigation pane, click System. 5. In the System Overview page, click Upgrade Wizard. 6. Follow the instructions to upgrade the software. 7. When prompted, select Reboot. Note: After the upgrade, close all browser instances and clear your computer's cache before accessing the appliance. 32

33 Upgrading a High Availability Pair To upgrade the system software on NetScaler units in a high availability pair, you need to upgrade the software first on the secondary node and then on the primary node. To upgrade NetScaler units in a high availability pair running release 8.1, 9.0, 9.1, 9.2, 9.3 by using the command line interface Machine A is the primary node and machine B is the secondary node before the upgrade. On machine B (original secondary node) 1. Follow the procedure for upgrading a standalone node as described in "Upgrading a Standalone NetScaler". 2. After the NetScaler restarts, log on using the administrator credentials and enter the show ha node command to verify that the NetScaler is a secondary node and synchronization and propagation are disabled. Example login: nsroot Password: nsroot Last login: Mon Mar 26 08:37: from Done show ha node 2 nodes: 1) Node ID: 0 IP: Node State: UP Master State: Secondary... Sync State: AUTO DISABLED Propagation: AUTO DISABLED... Done Note: Before upgrading the primary node (machine A), you have the option to test the new release by entering the force failover command on the secondary node (machine B). When you do so, machine B becomes the primary node. If machine B does not function as expected, enter the force failover command on the new primary node (machine B) forcing it to again become the secondary node, and contact Citrix Customer Service before proceeding. If machine B properly assumes the role of primary node, proceed with upgrading the former primary node (machine A). 33

34 Upgrading a High Availability Pair On machine A (original primary node) 3. Follow the procedure for upgrading a standalone node as described in "Upgrading a Standalone NetScaler". 4. After the NetScaler restarts, log on using the administrator credentials and enter the show ha node command to verify that the NetScaler is a secondary node and synchronization is disabled. On machine B (new primary node) 5. Enter the show ha node command to verify whether machine B is the primary node. On machine A (new secondary node) 6. Enter the show ns runningconfig command to verify whether the configuration of machine A has been synchronized with that of machine B On machine B (new primary node) 7. Enter the save ns config command to save the configuration. Machine B (original secondary node) is now the primary node and machine A (original primary node) is now the secondary node. To upgrade NetScaler units in a high availability pair running release 8.1, 9.0, 9.1, 9.2, 9.3 by using the configuration utility 1. Log on to the secondary node and perform the upgrade as described in "To upgrade a standalone NetScaler running release 8.0, 8.1, 9.0, 9.1, 9.2, or 9.3 by using the configuration utility:. Note: Before upgrading the primary node (machine A), you have the option to test the new release by entering the force failover command at the command line interface on the secondary node (machine B). When you do so, machine B becomes the primary node. If machine B does not function as expected, enter the force failover command at the command line interface on the new primary node (machine B) forcing it to again become the secondary node, and contact Citrix Customer Service before proceeding. If machine B properly assumes the role of primary node, proceed with upgrading the former primary node (machine A). 2. Log on to the primary node and perform the upgrade as described in "To upgrade a standalone NetScaler running release 8.0, 8.1, 9.0, 9.1, 9.2, or 9.3 by using the configuration utility". 34

35 Upgrading to a Later Build within Release 10 You can upgrade from an earlier 10 build to a later 10 build on a standalone NetScaler or a high availability pair. This procedure can be performed by using the configuration utility or the command line interface. 35

36 Upgrading a Standalone NetScaler to a Later Build In the following procedure, <targetbuildnumber> is the build number that you are upgrading to within the 10 release. 36

37 Upgrading a Standalone NetScaler to a Later Build To upgrade a standalone NetScaler running release 10 to a later build by using the command line interface 1. Open an SSH connection to the NetScaler by using an SSH client, such as PuTTY. 2. Log on to the NetScaler by using the administrator credentials. Save the running configuration. At the prompt, type: save ns config 3. Create a copy of the ns.conf file. At the shell prompt, type: a. cd /nsconfig b. cp ns.conf ns.conf.ns<releasenumber><currentbuildnumber> You should backup a copy of the configuration file on another computer. 4. Download or copy the installation package (build-10-<targetbuildnumber>_nc.tgz) and the documentation bundle (ns-10-<targetbuildnumber>-doc.tgz) to this directory and extract the contents of the installation package. 5. Run the installns script to install the new version of the system software. Note: To install a FIPS appliance, run the installns script with the -F option. To automatically clean up the flash, run the installns script with the -c option. If the configuration file for the build that you are upgrading to exists on the appliance, you are prompted to load that configuration, as shown in the following figure. 37

38 Upgrading a Standalone NetScaler to a Later Build Figure 1. Upgrade menu if configuration file exists If the free space available on the flash drive is insufficient to install the new build, the NetScaler prompts you to initiate a cleanup of the flash drive. For more information, see "Auto Cleanup". 6. When prompted, restart the NetScaler. Example login: nsroot Password: Last login: Thu Aug 9 12:12: from Done > save config > shell Last login: Mon Aug 9 03:51:42 from root@nsnnn# cd /var/nsinstall root@nsnnn# cd 10.0nsinstall root@nsnnn# mkdir build_70 root@nsnnn# cd build_70 root@nsnnn# ftp... get build _nc.tgz root@nsnnn# get ns doc.tgz root@nsnnn# tar build _nc.tgz root@nsnnn#./installns installns version ( ) kernel (ns _nc.gz) The Netscaler version checksum file is located on under Support > Downloads > Citrix NetScaler. Select the Release link and expand the "Show Documentation" link to view the MD5 checksum file for build

39 Upgrading a Standalone NetScaler to a Later Build There may be a pause of up to 3 minutes while data is written to the flash. Do not interrupt the installation process once it has begun Copying ns _nc.gz to /flash/ns _nc.gz Installing documentation Installation has completed. Reboot NOW? [Y/N] Y 39

40 Upgrading a Standalone NetScaler to a Later Build To upgrade a standalone NetScaler running release 10 to a later build by using the configuration utility 1. In a Web browser, type the IP address of the NetScaler, such as 2. In User Name and Password, type the administrator credentials. 3. In Start in, select Configuration, and then click Login, as shown in the following figure. 4. In the configuration utility, in the navigation pane, click System. 5. In the System Overview page, click Upgrade Wizard. 6. Follow the instructions to upgrade the software. 7. When prompted, select Reboot. Note: After the upgrade, close all browser instances and clear your computer's cache before accessing the appliance. 40

41 Upgrading a NetScaler High Availability Pair to a Later Build To upgrade the system software on NetScaler units in a high availability pair, you need to upgrade the software first on the secondary node and then on the primary node. Warning: In certain rare cases, synchronization and propagation are disabled if you upgrade only one of the nodes in an HA pair to a later build. To determine whether synchronization and propagation are disabled, at the command line interface, type: show ha node Note: In an HA setup, both nodes must run NetScaler ncore or NetScaler classic. If the nodes are running NetScaler classic and you want to migrate to NetScaler ncore of the same NetScaler release, propagation and synchronization are not supported during the migration process. Once migration is complete, you have to manually enable propagation and synchronization. The same applies if you migrate from NetScaler ncore to NetScaler classic. If synchronization and propagation are disabled, a new command added on the new primary node will not be propagated to the new secondary node. Also, if you restart the new secondary node, it will not synchronize and fetch the running configuration from the new primary node, but it will use the configuration that was last saved before the node was restarted. To resolve this situation, upgrade both of the nodes to the same build as soon as possible and make sure that no new command is added on the new primary node when a different build is running on the new secondary node. In the following procedure, machine A is the original primary and machine B is the original secondary node, and <targetbuildnumber> is the build number that you are upgrading to within the 10 release. To upgrade a NetScaler high availability pair to a later build by using the command line interface On machine B (original secondary node) 1. Open an SSH connection to the NetScaler by using an SSH client, such as PuTTY. 2. Log on to the NetScaler by using the administrator credentials. Save the running configuration. At the prompt, type: save config 41

42 Upgrading a NetScaler High Availability Pair to a Later Build 3. Create a copy of the ns.conf file. At the shell prompt, type: a. cd /nsconfig b. cp ns.conf ns.conf.ns10.0-<currentbuildnumber> 4. Disable synchronization and propagation manually by entering the following commands in the order shown at the command line interface: a. set HA node -hasync DISABLED b. set HA node -haprop DISABLED c. save config On machine A (original primary node) 5. Open an SSH connection to the NetScaler by using an SSH client, such as PuTTY. 6. Log on to the NetScaler by using the administrator credentials. 7. Disable synchronization and propagation manually by entering the following commands in the order shown at the command line interafce: a. set HA node -hasync DISABLED b. set HA node -haprop DISABLED c. save config On machine B (original secondary node) 8. Change directory to /var/nsinstall/10nsinstall, create a directory named build_<targetbuildnumber>, and change to this directory. 9. Download or copy the installation package (build-10-<targetbuildnumber>_nc.tgz) and the documentation bundle (ns-10-<targetbuildnumber>_nc.tgz) to this directory, by using a Secure File Transfer Protocol (SFTP), and extract the contents of the installation package. 10. Run the installns script to install the new version of the system software. Note: To install a FIPS appliance, run the installns script with the -F option. To automatically clean up the flash, run the installns script with the -c option. If the free space available on the flash drive is insufficient to install the new build, the NetScaler prompts you to initiate a cleanup of the flash drive. For more information, see Auto Cleanup. 11. When prompted, restart the NetScaler. 12. After the NetScaler restarts, log on using the administrator credentials and enter the show ha node command to verify that the NetScaler is a secondary node. 42

43 Upgrading a NetScaler High Availability Pair to a Later Build Note: Before upgrading the primary node (machine A), you have the option to test the new build by entering the force failover command on the secondary node (machine B). When you do so, machine B becomes the primary node. If machine B does not function as expected, enter the force failover command on the new primary node (machine B) forcing it to again become the secondary node, and contact Citrix Customer Service before proceeding. If machine B properly assumes the role of primary node, proceed with upgrading the former primary node (machine A) by following steps 13 through 19. On machine A (original primary node) 13. Follow the procedure for upgrading a standalone node. 14. After the NetScaler restarts, log on using the administrator credentials and enter the show ha node command to verify that the NetScaler is a secondary node. 15. Enable synchronization and propagation manually by entering the following commands in the order shown at the command line interface: a. set HA node -hasync ENABLED b. set HA node -haprop ENABLED c. save config On machine B (new primary node) 16. Enter the show ha node command to verify that machine B is the primary node. 17. Enable synchronization and propagation by entering the following command in the order shown at the command line interface: a. set HA node -hasync ENABLED b. set HA node -haprop ENABLED c. save config On machine A (new secondary node) 18. Enter the show ns runningconfig command to verify that the configuration of machine A has been synchronized with that of machine B. On machine B (new primary node) 19. Enter the save ns config command to save the current configuration. Machine B (original secondary node) is now the primary node and machine A (original primary node) is now the secondary node. 43

44 Downgrading from Release 10 You can downgrade to any release on a standalone NetScaler or a high availability pair by using the command line interface. Caution: Loss in configuration may occur when downgrading. You should compare the configurations before and after the downgrade, and then manually read any missing entries. This procedure provides steps to downgrade from release 10 to an earlier release. For downgrading to an earlier build within release 10, see "Downgrading to an Earlier Build within Release 10". Note: Downgrading using the configuration utility is not supported. 44

45 Downgrading a Standalone NetScaler In the following procedure, <release> and <releasenumber> represent the release version you are downgrading to, and <targetbuildnumber> represents the build number that you are downgrading to. Refer to the table below for specific values. Table 1. Release Version Values Release Version <release> <releasenumber> rhodes andes sierra

46 Downgrading a Standalone NetScaler To downgrade a standalone NetScaler 1. Open an SSH connection to the NetScaler by using an SSH client, such as PuTTY. 2. Log on to the NetScaler by using the administrator credentials. Save the running configuration. At the prompt, type: save config 3. Create a copy of the ns.conf file. At the shell prompt, type: a. cd /nsconfig b. cp ns.conf ns.conf.ns10<currentbuildnumber> You should backup a copy of the configuration file on another computer. 4. Copy the <releasenumber> configuration file (ns.conf.ns<releasenumber>) to ns.conf. At the shell prompt, type: cp ns.conf.ns<releasenumber> ns.conf Note: ns.conf.ns<releasenumber> is the backup configuration file that is automatically created when the system software is upgraded from release version <releasenumber> to the current release version. There may be some loss in configuration when downgrading. After the appliance restarts, compare the configuration saved in step 3 with the running configuration, and make any adjustments for features and entities configured before the downgrade. Save the running configuration after making the changes. Important: If routing is enabled, perform step 5. Otherwise, skip to step If routing is enabled, the ZebOS.conf file will contain the configuration. At the shell prompt, type: a. cd /nsconfig b. cp ZebOS.conf ZebOS.conf.NS10 c. cp ZebOS.conf.NS<targetreleasenumber> ZebOS.conf 6. Change directory to /var/nsinstall/<releasenumber>nsinstall, or create one if it does not exist. 7. Change directory to build_<targetbuildnumber>, or create one if it does not exist. 8. Download or copy the installation package (build-<release>-<targetbuildnumber>.tgz) and the documentation bundle (ns-<releasenumber>-<targetbuildnumber>-doc.tgz) to this directory and extract the contents of the installation package. 9. Run the installns script to install the new version of the system software. If the configuration file for the build that you are downgrading to exists on the appliance, you are prompted to load that configuration, as shown in the following figure. 46

47 Downgrading a Standalone NetScaler Figure 1. Downgrade menu if configuration file exists If the free space available on the flash drive is insufficient to install the new build, the NetScaler prompts you to initiate a cleanup of the flash drive. For more information, see "Auto Cleanup". 10. When prompted, restart the NetScaler. Example login: nsroot Password: nsroot Last login: Tue Mar 27 01:38: from Done > save config > shell Last login: Tue Mar 27 02:07:06 from root@nsnnn# cp ns.conf.ns9.3 ns.conf root@nsnnn# cd /var/nsinstall root@nsnnn# mkdir 9.3nsinstall root@nsnnn# cd 9.3nsinstall root@nsnnn# mkdir build_55 root@nsnnn# cd build_55 root@nsnnn# ftp... get build_93_55_nc.tgz root@nsnnn# get ns doc.tgz root@nsnnn# tar xzvf build_93_55_nc.tgz root@nsnnn#./installns installns version (9.3-55) kernel (ns gz)

48 Downgrading a Standalone NetScaler... Copying ns gz to /flash/ns _nc.gz... Changing /flash/boot/loader.conf for ns Installing documentation... Installation has completed. Reboot NOW? [Y/N] Y 48

49 Downgrading a High Availability Pair To downgrade the system software on NetScaler units in a high availability pair, you need to downgrade the software first on the secondary node and then on the primary node. For instructions on downgrading each node separately, see "Downgrading a Standalone NetScaler". 49

50 Downgrading to an Earlier Build within Release 10 You can downgrade from a later 10 build to an earlier 10 build on a standalone NetScaler or a high availability pair. This procedure must be performed by using the command line interface. Note: Loss in configuration may occur when downgrading. You should compare the configurations before and after the downgrade, and then manually read any missing entries. 50

51 Downgrading a Standalone NetScaler to an Earlier Build In the procedure below, <targetbuildnumber> is the build number that you are downgrading to within the same release. 51

52 Downgrading a Standalone NetScaler to an Earlier Build To downgrade a standalone NetScaler to an earlier build 1. Open an SSH connection to the NetScaler by using an SSH client, such as PuTTY. 2. Log on to the NetScaler by using the administrator credentials. Save the running configuration. At the prompt, type: save ns config Caution: If ns.conf.ns10-<targetbuildnumber> does not exist, loss in configuration may occur when downgrading to an earlier build. The errors and warnings appear only on the console. Please watch the console closely for these errors and warnings. After the appliance restarts, compare the configuration saved in step 3 with the running configuration, and make any adjustments for features and entities configured before the downgrade. Save the running configuration after making the changes. 3. Change directory to /var/nsinstall/10nsinstall. 4. Change directory to build_<targetbuildnumber>, or create one if it does not exist. 5. Run the installns script to install the old version of the system software. If the configuration file for the build that you are downgrading to exists on the appliance, you are prompted to load that configuration, as shown in the following figure. Figure 1. Downgrade menu if configuration file exists 52

53 Downgrading a Standalone NetScaler to an Earlier Build If the free space available on the flash drive is insufficient to install the new build, the NetScaler prompts you to initiate a cleanup of the flash drive. For more information, see "Auto Cleanup". 6. When prompted, restart the NetScaler. Example login: nsroot Password: nsroot Last login: Sun Aug 5 08:38: from Done > save ns config > shell Last login: Sun Aug 5 09:07:06 from root@nsnnn# cp ns.conf.ns ns.conf root@nsnnn# cd /var/nsinstall root@nsnnn# cd 10nsinstall root@nsnnn# cd build_69_4 root@nsnnn# ftp... get build _nc.tgz root@nsnnn# get ns doc.tgz root@nsnnn# tar xzvf build _nc.tgz root@nsnnn#./installns installns version ( ) kernel (ns gz) Copying ns _nc.gz to /flash/ns _nc.gz... Changing /flash/boot/loader.conf for ns Installing documentation... Installation has completed. Reboot NOW? [Y/N] Y 53

54 Downgrading a NetScaler High Availability Pair to an Earlier Build To downgrade the system software on NetScaler units in a high availability pair, you need to downgrade the software first on the secondary node and then on the primary node. For instructions on downgrading each node separately, see "Downgrading a Standalone NetScaler to an Earlier Build". Note: Note: In an HA setup, both nodes must run NetScaler ncore or NetScaler classic. If the nodes are running NetScaler classic and you want to migrate to NetScaler ncore of the same NetScaler release, propagation and synchronization are not supported during the migration process. Once migration is complete, you have to manually enable propagation and synchronization. The same applies if you migrate from NetScaler ncore to NetScaler classic. 54

55 Auto Cleanup The cleanup procedure has been simplified in the later versions of release 7.0 (build 48 and later) and in releases 8.0, 8.1, 9.0, 9.1, 9.2, 9.3, and 10. You no longer have to manually delete build files from the flash drive. During the installation process, if the free space on the flash drive is found to be insufficient, the NetScaler prompts you to initiate the cleanup process. Note: To automatically clean up the flash, run the installns script with the -c option. When downgrading to release 7.0, the prompt looks like this: Installation path for kernel will be /flash Size of kernel ns gz is kilobytes Available space on /flash/ filesystem is kilobytes Available space on /flash/ filesystem is insufficient to install ns gz Do you want Auto Cleanup [Y/N]? When upgrading to release 8.1, the prompt looks like this: Installation path for kernel is /flash Size of kernel ns gz is kilobytes Available space on /flash/ filesystem is kilobytes Available space on /flash/ filesystem is insufficient to install ns gz Do you want installns to free space by archiving older releases? [Y/ N] To initiate the cleanup process, press Y. Messages similar to the following appear: Archiving older releases... Creating the archive directory /var/nsbackup/ns_2007_2_16_1_6_26... Move //flash//ns m.gz /var/nsbackup/ ns_2007_2_16_1_6_26ns m.gz... Move //flash//ns gz /var/nsbackup/ns_2007_2_16_1_6_26ns gz... Archive operation completed, free space is , required space is The installation process automatically continues after successful completion of the cleanup. 55