Jump to content

Update from 13.0 to 13.1


Recommended Posts

Hello, 

we are on latest 13.0 release and we want to update to 13.1 , is there an upgrade path to follow or we can go straight to the latest 13.1 release?
 

Is it correct to perform first the SDX update then the VPX? 

 

Thank you 

Link to comment
Share on other sites

I have gone directly from 13.0 build 92.19 to 13.1 only issue was the compression found by running the nspepi tool 

 

image.thumb.png.c87e3c3f94c8d7dbded668047870b1f3.pngThe following configuration lines will get errors in 13.1 and both they and dependent configuration will be removed from the configuration:

 

bind cmp global ns_nocmp_xml_ie -priority 8700 -state DISABLED

bind cmp global ns_nocmp_mozilla_47 -priority 8800 -state DISABLED

bind cmp global ns_cmp_mscss -priority 8900 -state DISABLED

bind cmp global ns_cmp_msapp -priority 9000 -state DISABLED

bind cmp global ns_cmp_content_type -priority 10000 -state DISABLED

 

 

thus running the upgrade i did :

 

./installns -Y

 

Been running for two months so far no issues

 

 

image.png

Link to comment
Share on other sites

  • 5 months later...

HI
Using the "-Y" parameter is highly discouraged by Citrix and when moving from 13.0 to 13.1 you risk stopping services due to classic policies and other objects deprecated and removed on NS 13.1. 
image.thumb.png.a6eb102dffcd09b6f5d79f92e0c79ee9.png

Before upgrading, be sure to follow the documentation below and check for and fix any deprecated commands. nspepi tool can help

https://docs.netscaler.com/en-us/citrix-adc/13-1/upgrade-downgrade-citrix-adc-appliance/upgrade-considerations-classic-policies.html

Link to comment
Share on other sites

We've got those Compression policy warnings with pretty much all older NetScaler environments when upgrading from 13.0 to 13.1. As you can see, the policies are "disabled" so there's nothing to be worried about. If something outside the policies above is listed, then you need to take a look what they are and if they're in use.

Also, finally we decided to upgrade from the classic expressions to advanced with all environments. Not that it's required for even 14.1, but I think they might get a bit tricky if you run in to problems and need to establish a support case.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...