Pulse check on those who updated your netscalers last night. How you doing? All going well? Normal operations this morning?

No issues. Only need to update via CLI.

Did GUI fail for you? It hung for me. ADM worked fine. (I was just in the process of updating it so opted for GUI)

For me it failed with GUI on previous 13.1 releases. Did not even bother to try this one with GUI. Somebody else already mentioned it failed with GUI in a thread above.

I will review. Been a lot of posts and trying to keep up. My GUI hung on SAAS updates I think….

CLI worked fine for both 13.0 and 13.1 firmware updates

Is the consensus that the GUI does not work?

i always do updates thru the CLI, I feel like not having a browser involved in the update process is a cleaner way to go

Having upgraded a large number of NetScalers from around v10.0 onwards, the GUI has regularly been problematic on all versions, so I stick with CLI. Sometimes it works fine, but is not consistent between versions or different deployments on the same version. Upgrading from CLI takes no longer, but is consistent.

Upgrading via the GUI on the NetScaler itself has been failing at our location recently with 13.1, so I've stopped trying. I used the SVMs on our SDXes last night to upgrade a virtual HA pair and that worked.

Point being, if it’s available via GUI, it should work consistently. So will be reporting on that as a general consensus.

Many CLI upgrades, only issue I noted was the config.xml backup request, which I have not seen before. ALl are working well today. More fun tonight and tomorrow. GOod thing I have lots of coffee.

Two different clients had an issue where the ADM console blocked upgrade because of an HA configuration mismatch on the NSIP and RPC passwords. CLI upgrades for these and two other clients were fine.

CLI upgrades went perfectly, but I was in the process of an SDX to SDX migration with HA failovers, so breaking and rebuilding HA with clean nodes. Had a similar issue with RPC passwords being wiped/invalidated. Never saw that before on all the vpx instances I migrated in the past weeks with 53.17

GUI hung for me, I forget on which part, when I tried CLI after that I was getting some sort of Perl error and reverted to snapshot and will try again today.

Got burnt again last night on a VPX. Check and recheck you license file before you update. VPX appliances care about the date of the file apparently. It came up unlicensed and I did not check before failover. 😧

Just wrapped 2nd stage of NS Console/ADM managed 2 stage upgrades for all our VPXs. Had 2 of 5 jobs that hung on the 2nd upgrade in the NS Console (Upgrading secondary delayed task). Both jobs did send the commands to ./installns on the new secondaries so the VPXs did upgrade...but NS Console never proceeded to the post upgrade steps (reenable HA, post upgrade scripts etc). Had to finish those manually. Also, reminder, for those that it applies to, don't forget to upgrade those ADM/MAS agents as well.

Thank you Jon!