This message was deleted.
# citrix-netscaler
s
This message was deleted.
c
Weird, 12.1 61.18 should be there, I did a heap of them just very recently
n
Oh aye, it was replaced yesterday according to the release notes, so it was there for what, almost a good month? before being replaced. I did a pair about an hour ago, and then I see this. Haha. I’m worried I added a bugridden version now since it’s been replaced.
s
was it the HA problem they fixed?
c
HA problem??? 🙂 I should read the latest release notes
n
Hhaahahah, my take exactly, the what now?
The only difference between the two versions are known issues.. I’ve not scoured them and compared side by side, of course. https://docs.citrix.com/en-us/citrix-adc/downloads/release-notes-12-1-61-18.html https://docs.citrix.com/en-us/citrix-adc/downloads/release-notes-12-1-61-19.html
s
lol, the failed syncs of HA nodes, i know this was an issue with the lastest 13, wasn't sure if 12.1 was affected by that as well
not all fixes are made public as well....
n
We’ve not seen that - yet, with 12.1, but who knows.. Good to know if it occurs, for now.
c
Fixed Issues "After you upgrade the Citrix ADC appliance to release 13.0 build 64.35 and later or release 12.1 build 61.18 and later, the Secure option for all the RPC nodes is turned ON by default. This option secures the communication between the ADC nodes in the high availability, cluster, and GSLB deployments, which use the port number 3008 and 3009. If the firewall between the ADC nodes blocks the port number 3008, 3009, or both, unblock the ports and proceed. Otherwise, configuration synchronization, configuration propagation, and MEP synchronization might fail. You can change this option anytime using the CLI or the GUI."
k
I'm seeing some JSON errors in GUI with 61.18... we have pushed this release to our managed customers, I don't love this.
n
Yeah, I saw the note about secure, but I’m unsure why that’s a fixed issue in that way, when it’s mentioned in the installer and the first time you login too. It’s not exactly worth of a replacement build to note that, to me.
d
I had the JSON Errors on 13.0 Build 76.29 as well.
j
Yeah rollback that release for the JSON errors massive pain in the ass
e
Apparently a SAML fix went into the new builds. I believe Citrix will share further info soon.
c
havent seen any JSON issues yet in the GUI, seems stable for this client at this stage.
k
@Carl Behrent, on the 61.19 or the 61.18? ... or are you running 13.0?
c
61.18
k
is there any info on what exactly was changed between the builds? the last time I checked the release notes, there was nothing
one managed environment for us is crashing and I got the core dumps, so I'm going to create a case for this any ways
Found it... we don't have the drop down In some cases, SAML authentication breaks when the following conditions are met: The Citrix ADC appliance is configured as a SAML SP. "Domain drop-down" is configured as a factor on the Citrix ADC appliance. SAML policies are evaluated based on inputs from the "Domain drop-down" factor. [ NSAUTH-10135 ]
n
Thank you Kari, I didn’t see any more than that in the release notes, either. I finally(!) ran into an issue on 12.1 61.18, at least, and got the JSON bug when adding a PSK for Radius that included special characters, like % and $, probing the server in CLI says that no such characters are OK to use anymore, for some reason - filed a bug in a case and it’s been sent on it’s merry way to the devs. PSK works, but it’s unable to test the functionality, hah.
k
All the sudden we're experiencing a great deal of issues with ADC 12.1-61.18 (ADCs failovering and crashing), the escalation has identified a suspected issue already (NSHELP-27132), but there's nothing of it in the release notes.
n
Me too! I was literally about to pop back into Slack, and say just this. It seems to be a known issue on VMware, but not all of our ADC’s on VMware are impacted.
s
could be new DDOS attacks? Sounds like it's accelerating
check your outbound throughput on the ADC dashboard, if it's abnormally high, that could be the case....regardless i'd get the fix in or disable DTLS profile
k
we already downgraded back to 12.1-58.15 and disabled DTLS
we're seeing management CPU at 100% constantly even after these changes