Hi Black Shamrock,
I see a good chance to support your scenario by just configuring regular health-monitors. So you may try the following setup...
- PoolA
- Member1:
IP: 10.400.70.176
Priority Group: 5
Health Monitors: Member Specific
Availability Requirement: All
Select Monitors
- Build-in "tcp" monitor
- Custom "tcp" monitor with Alias Address / Alias Service Port settings for 10.400.70.177:Service_Port
- Member2:
IP: 10.500.42.161
Priority Group: 1
Health Monitors: Member Specific
Availability Requirement: All
Select Monitors
- Build-in "tcp" monitor
- PoolB
- Member1:
IP: 10.400.70.177
Priority Group: 5
Health Monitors: Member Specific
Availability Requirement: All
Select Monitors
- Build-in "tcp" monitor
- Custom "tcp" monitor with Alias Address / Alias Service Port settings for 10.400.70.176:Service_Port
- Member2:
IP: 10.500.42.162
Priority Group: 1
Health Monitors: Member Specific
Availability Requirement: All
Select Monitors
- Build-in "tcp" monitor
The above configuration should team the availibility of the members 10.400.70.176 and 10.400.70.177, so that if one of them becomes "offline" both will become "offline" at the same time.
Cheers, Kai