Radius traffic is no loner SNAT'd after a failover, CSS-CSS
I have case where i have 2 CSS's in active standby mode. We use a VIP for radius traffic ie. UDP 1813. When in normal operation, all is OK. The IP src of the packet from CSS to the GGSN (NAS) has the CSS VIP IP. After we failover to the other CSS, this new CSS stops un NATing. This means the the packet from CSS to the GGSN in the radius response has the src IP of the real radius server. The GGSN doesn't accept this as this ip is unexpected.
Why is CSS stopping doing NAT after a switchover. Software is 7.10.504.
Introduction This article will help you understand the steps on how to
download the UCS licenses from the Cisco Systems website and then
installing it on the UCS. The redacted (blue lines) just covers up
certain numbers for privacy please do not take them...
Introduction This article will help you understand and educate the
customer on how to clear their "expired licenses"
(license-graceperiod-expired) from their UCS-M. If a customer just
purchased a license and needs a step by step guide on how to download
Introduction Prepositioning is a powerful tools on the WAAS platform but
it is not always easy to figure out why your jobs are failing when
trying to retrieve the files.Here is a method that should help you to
figure out the reason why they are not succes...