Happy Fridays all! I am on 13.1 and upgraded to 13...
# citrix-netscaler
j
Happy Fridays all! I am on 13.1 and upgraded to 13.1 53.17. 2 out of my 5 HA pair got hit by a known bug NSHELP-37950 which crash the secondary when sync is enabled back. No ETA yet for the fix on 13.1 but 14.1 has this fixed. I am on 13.1 for stability but that's the second firmware I hit some bugs. How is your experience with 14.1? thumb up for happy and down for not. Give any details if you want!! Thanks a mill
👍 4
🤷‍♂️ 2
j
14.1 working fine so far. But remember the latest 14.1 has also the bug when using an AlwaysUp Dummy Service with 127.0.0.1, you have to switch to (for example) an APIPA IP with Healthcheck disabled before upgrading to 14.1. There's no HA-Crash like in 13.1, but the 127.0.0.1 service will be deleted without any info and you can get some issues, depends on the bindings of the Dummy Service. This will also be fixed a next build
👍 1
e
Can you share some more details of the bug? I have upgraded several instances from 13.1-51.15 to 13.1-53.17 and it has been rock solid.
j
Thanks Guys, very interesting this issue with the dummy service 127.0.0.1 as it turns out the issue as per Citrix Jira, the crash is observed when an explicit service is configured on loop back and HA sync triggered. I'll try the APIPA IP as those 2 NS crashing have this service 127.0.0.1 set.
I replaced my 127.0.0.1 AlwaysOn service by one using a VIP e.g. 192.168.1.20, I made sure no 127.0.0.1 remained on primary and it fixed the issue after a first crash (when I re-enabled the Sync) and then it was fine. Thanks guys :)
👍 1
k
For us the 13.1-51.15 has been the last completely problem-free release and the majority of our managed services are on that one still
j
Thanks Kari! Except from this problem, 53.17 is stable now!
k
yeah, we have a couple on that build and on the latest 14.1 also, the biggest issue is EPA related (domain membership scan fails)
j
OK thanks Kari, I'll stick to 13.1 for now. :)