CNS provides Middleware's load balancing solution, which is a pair of Foundry Server Iron 450s. (wsm6-ssl module)
The Server Irons are accessible via SSH at isb-118-si-1.cns.vt.edu and isb-118-si-2.cns.vt.edu.
Access is provided via PID/Password.
Configuration changes are replicated between these two nodes, so it does not matter which one you connect to.
For all these commands the id param is optional. If not provided all data is displayed and must be paged through.
show server bind <mw.webapp-dev>
show server virtual <mw.webapp-dev>
show server real <mw.webapp-dev-1>
sh hc-track-group-state | i <ash.cas-dev-1>
In order for services to resolve the correct IP address of other services on the load balanced network each service must be quarantined into it's own subnet.
These micro subnets take the form of /29 networks:
The consequence of this design is that each service consumes 7 IP addresses.
It is possible to use both Reals, but take caution that these servers will not be able to correctly resolve the other's IP address.
these checks perform packet inspection
In our configuration there are 2 SLOBs. For each virtual, only one SLOB is active. If your ping goes to the inactive SLOB, you'll get no request. This is not indicative of a server being down.
Short version: It's because the load balancers are POS's.