This message was deleted.
# citrix-netscaler
s
This message was deleted.
c
You have the ns.log and the newnslog which you have to use nsconmsg with
k
Usually If management is looking for an official analysis, I'll grab support bundles from both NetScalers. Open a low priority support case with Citrix requesting an RCA, and upload the bundles to the case. You can also check ADM, if available, for the failover event.
a
Thanks guys!
i'm sure not related but the appliance that hung up i found the reporting tab was super slow and showed that the data collection utility was disabled. once i enabled that everything seems quick again
well it happened again this morning and interesting thing is same as yesterday it happened RIGHT after vmware vMotioned the secondary appliance. i'd have to imagine this has happened plenty in the past w/out an issue or we would have heard about it. we did just upgrade our firmware to 13.0 92.19nc so not sure if its a bug or something else but i have a ticket opened so i'll see where that takes us
c
Check that the vpx firmware is supported on your version of esxi and vcenter. Was there any messages on the console of the vpx in vcenter?
a
good tip! so we're on 13.0 92.19 for our netscaler and vSphere 7.0 update k for reference. i found this documentation on Citrix but not sure if it means when you're on 7.0 you have to be at least 13.1 or newer to be supported?
c
That is correct. NS support lags behind VMWare patch levels and they don't generally go back and "certify" older releases.
a
gotcha.....so 13.0 COULD work fine on vSphere 7 but not "certified" officially?
c
yup, but if you run into an issue support will tell you to upgrade before touching it
a
yup i figured that was the case 🙂
c
that said I'm running 13.0 on 7.0.3 build 21930508, I don't recall offhand which letter that correlates to
a
cool that would be update n so you're even newer that our update k
which netscaler 13.0 build are you on ?
c
This one's on 92.18
a
thanks! we're on the 92.19 that just came out this month because of whatever that latest vulnerability that was published so hoping thats related to this.