Nat oversubscription mismatch during upgrade
During a 3220 cluster upgrade, our client saw the active member report that the passive was non-functional due to a NAT oversubscription mismatch. Both members were set to default and matched before the passive was upgraded from 9.0.9 to 9.0.12. As far as I can tell, there is no change to the default oversubscription rate, but this reddit post suggests that there may be a change in behavior. Is there a change in the default behavior and is it officially documented somewhere?
935 Views
Yes, that fixes the issue, the problem is "default" doesn't match between the OS versions