In a multi-context ACE module configuration, is there a reason why we can't access a virtual server using it's virtual IP address (VIP) from machines located in the same context? It works fine from other contexts, but I can't get it to work from within the same context.
Here are some general details on our config.
We have an ACE2 module running the latest version of the code, A2(1.2). We have an Admin context and 2 user contexts. In contextA, we have a virtual server that load-balances two real web servers that are located in the same VLAN, let's call it VLAN A1.
In contextB, we have one virtual server that is load-balanced to two real SMTP servers in VLAN B1. On the same VLAN B1, there's one real IMAPS server; we will soon add others and will define a virtual IMAPS server that will load-balance the real IMAPS servers. In another VLAN of the same contextB (let's call it VLAN B2), there's a real Web server. Again, we will add others and define a new virtual Web server to load-balance between these real web servers.
From any network outside of the ACE module, we can use the virtual IP of the SMTP server in contextB. We can also use it from the real servers in contextA (VLAN A1). But from any of the machines in VLANs of contextB (VLAN B1, VLAN B2), we can't use the VIP of the SMTP server in contextB.
I enabled the "VIP Advertise" option (it seemed that it could help) but it didn't.
When I try: "telnet VIP 25" (replacing VIP by the actual virtual IP of the SMTP server in contextB), it works from the real servers in VLAN A1 (ContextA) but from the real IMAPS server in VLAN B1 or from the real Web server in VLAN B2, I get the following error:
$ telnet 10.32.33.2 25
telnet: connect to address 10.32.33.2: Connection refused
telnet: Unable to connect to remote host: Connection refused
Any help would be greatly appreciated, because as we move new services behind the ACE module, we will need to access virtual servers using their VIP from within the same context.
Thank you very much!