Ok,
Got a tough one.
I have a foundry Serviron on a DMZ Interface with a private address of 10.30.200.2, pix-gate 10.30.200.1. all statics and ACL's work great. All server monitoring for GSLB works good. They have statically trans'd Public ip's for the WEB VIP and DNS-VIP interfaces. NSLookup to the boxes from the big "I" work great and the web sites deliver fine through the load balancer.
But there is one issue.
Both of My foundry boxes in Irvine and Dallas can see each other, they can reach each others respective Name Servers, and Web VIP's.
But they cannot reach their own DNS or WEB VIP's. (they need this as part of the GSLB logic to determine best site selection. ie. (My DNS/WEB is down so the best site is my peer, etc.)
Well, to determine this it sends a ping to it's configred WEB and DNS VIP IP. (Which is the public, since it's what it has to deliver to a client via nslookup.)
Now, is there a way to allow the DMZ, statically translated, privately addressed foundry box to ping a virtual interface which has real IP associated with it?
IE, I want to ping 216.x.x.x and get a response from the DMZ, but that 216.x.x.x block lives on this PIX.
--BD
However,
Got a tough one.
I have a foundry Serviron on a DMZ Interface with a private address of 10.30.200.2, pix-gate 10.30.200.1. all statics and ACL's work great. All server monitoring for GSLB works good. They have statically trans'd Public ip's for the WEB VIP and DNS-VIP interfaces. NSLookup to the boxes from the big "I" work great and the web sites deliver fine through the load balancer.
But there is one issue.
Both of My foundry boxes in Irvine and Dallas can see each other, they can reach each others respective Name Servers, and Web VIP's.
But they cannot reach their own DNS or WEB VIP's. (they need this as part of the GSLB logic to determine best site selection. ie. (My DNS/WEB is down so the best site is my peer, etc.)
Well, to determine this it sends a ping to it's configred WEB and DNS VIP IP. (Which is the public, since it's what it has to deliver to a client via nslookup.)
Now, is there a way to allow the DMZ, statically translated, privately addressed foundry box to ping a virtual interface which has real IP associated with it?
IE, I want to ping 216.x.x.x and get a response from the DMZ, but that 216.x.x.x block lives on this PIX.
--BD
However,