This message was deleted.

you can run the following commands to see what nspepi would change: check_invalid_config /nsconfig/ns.conf In my case everything was either a use of newer expressions that I could tell were equivocal or disabling a feature I wasn't using anyway. If you are ultra paranoid you can copy your ns config to another instance like a new dev vpx instance and run nspepi against it from that machine. I ran all my nspepi commands from a central instance just to keep all my befores, comments, and afters in one place. When you run the actual nspepi conversion, the warn file output should match what you saw from the check_invalid_config. More reference for nspepi here: https://github.com/netscaler/ADC-scripts/tree/master/nspepi

Ok awesome. Looks like that there are some binding.. I am not really sure how to tweak these. I will have to google-fu some of these. But here they are, if you have any info. The 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

The compression stuff (cmp) is something I saw as well. Not used in my environment. I think they give an upgrade path in release notes that (off the top of my head) are hitting the major versions in stepping stone fashion. I had previously gone from 12.1 to 13.0 and only recently made the move to 13.1. Testing 14.1 now but probably not going there any time soon.

At this time and point I would rip and replace with all the exploits out there and do a forensic check at your network as well

Go to 14.1 , makes no sense to go anything before because of EoL. That being said, do upgrade properly: 13.0 - 13.1 - 14.1

A bit wrong advise there, take a look at the Citrix Product Matrix - Citrix and NetScaler ADC Firmware Release Cycle (citrix.com) for a good explanation. MR/FR is a hassle and 14.1 is as green as it gets with FR.

? - There is no really LTSR of Netscaler....14.1 is the longest supported (2029)

13.0 / 13.1 are Maintenance Releases (MR), 14.1 is Feature release (FR), no one is saying that there is a LTSR that is something else. The question isn't about support or longest supported but which requirements you have and can align with those. MR is more stable than the FR releases, there is a strong track record for that.

Go to 14.1. lol. Nobody that does this for a living would defacto be telling anybody to go to 14.1 just because, well that's the latest build. Its completely different branch as Henry stated as far as feature and maintenance releases. 13.1 is what you will target here so agree w/Henry on this advice.

There is a big difference between telling someone to go to LTSR vs CR in CVAD and Netscaler. when it comes to support...Mentality like "not going to the latest build" are outdated sysadmin dinosaurs that still believe to install Windows Server 2019 or Windows 10 instead of the latest version. Of course there will always be issues/bugs/etc. but this is common in all platforms and all software! Please stop living in the past

You are all sorts of fun mate. Good luck with all your vast experience and the many upgrades you are doing. But first, figure out threads and then go from there.

Thanks for they help everyone. I was able to bump it up to 13.0 92.19. I am going to let it sit for a while then bump up to 13.1. I am going to build out some new Netscalers just to make migrate stuff over, just in case.