Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
Hi,we have version 3.3.0.430 with patch 3,4,6,7 installed and we are hitting this bug still.The known fixed version is 3.3.0.430 patch 5. Won't patch 6 and 7 contain the fix from patch 5?Additionally: we are hitting this when modifying a device on th...
This is confusing to me as well, also the workaround doesn't help.I've seen cases where the username was empty in a log, even though the client sent it correctly. Not sure if it is related?
Indeed, I opened a TAC case and they released a new patch for 3.4 (patch 4) - and it seem to have fixed the issue in our Lab.The patch for 3.3 will be released at the end of the month, I'm looking forward to patch our Production and test it.
Could be, but I reinstalled our LAB device and the issue remained.I'm in the process of opening a TAC case for it, but run into issues with our contracts....... anyway I will revert back when it progresses.
Thanks Dustin in advance!I use Edge, can't use anything else due to company policy.To test it: Go to Administration -> Network devices -> select a device -> add a new IP address (do not unhide the radius password) -> saveGo back to Network devices ->...
