Last night was fun... after not really getting cle...
# citrix-netscaler
d
Last night was fun... after not really getting clear answers on firmware support for the MPX 8200 we tried updating with NetScaler Console... everything seemed fine until it took an hour to reboot; only to find that applying the new firmware caused all the HA and SSL to go dark with no warning. Lovely. So here's my question: What tools and methods to transition live VIPs from a physical pair to a new virtual pair? This is healthcare so I want to make this as seamless and quick as possible. My thought was import the config as administrative down until we are ready but if it can be even easier/better, I'd love to know what works for folks these days!
j
I'd get the new VPX wired correctly, same than MPX. Then break the HA of MPX, join the VPX with MPX for the replication. And then do other node. Standard process for new hardware. I think there is a Ctx for this. You're 8200 was prob not in support and when it happens, you become unlicensed and conf stripped ... Not nice for sure.
d
Hmmm... thought about that too but wasnt sure the 13.1 and 14.1 would HA properly
And lesson learned... always do the validation checks, lol
j
Ah sorry miss the mismatch of versions. I would do it on same version and then upgrade.
d
And thats the rub for same version... VPXs are now the latest 14.1 that I can't use. So much for easy, lol. The other rub is we already have VIPs active on the new pair so I have to be careful there too. Fun how these things work sometimes.
j
There is still 13.1 VPX, I DL them yesterday, no? If you are careful on removing the other MPX node, and wipe its conf, you will be fine. But yes be careful and have a backup handy in case you need to restore ... Using always stay primary helps, check the Ctx
d
Yup... stay primary is big for sure. The more I'm digging in the more I'm finding a lot of VIPs that are just ghosts... unused but never removed kind of thing, or a current migration from Horizon taking up a whopping 16 that will be gone ;-)
👍 1
ROFL... always good to have these little exercises for the good of the group... but in reviewing with their team, it turns out that a whopping four (4) of 62 VIPs need to actually stay active past next month. Let it never be said that I don't on occasion get very lucky!!
j
It sounds like it!
👍 1
m
Have gslb look after dns for the VIPs and then just down the old one to test the new one. If it doesn’t work, bring the old one back up. Then you don't need to worry about arp caching and all the other issues that go along with migrating vips