Hi, When using RVRs, the guest VMs still see the VR IP instead of the VIP for a number of things: * DHCP Server * Static NAT source IP for hairpin NAT
Just wondering what the reason is for this, as it causes a number of issues: * Password reset doesn't work if active VR has changed since VM boot * Issues with DHCP renewals if VR has changed since VM boot (will discuss later) * Some static NAT connections confusingly (for the end user) come from the VR IP rather than the VIP It seems to me that it would be better if anything referencing the VR IP actually used the VIP, but I'm assuming someone has made a decision not to do this at some point - just wondered what that reason is, and whether it's still valid. Regards, Richard
