Virtual Server in Unknown Status

What were the monitors used to check "health" of your pool members? Were they the right method of polling your backend servers?

VS inherits health status from Pool while Pool inherits health status from pool members (Node, real servers, etc)

You'll need to put a pool behind the virtual server - You may want to put the pool of the most critical/most used application.

No impact as an unknown status, but you're not using any of the features/benefits of health checking application servers.

Below are the configuration. As i mentioned, there is no pool directly associated to this virtual server:

ltm virtual PROD_80_VS { destination 10.20.30.40:http ip-protocol tcp mask 255.255.255.255 persist { source_addr { default yes } } policies { PROD1_UAT_Switching { } } profiles { Xforward_Profile { } tcp { } } source 0.0.0.0/0 translate-address enabled translate-port enabled vs-index 7 }

As everyone mentioned above, you are not using health monitor to determine the availability.

Can you give us more detail about the policy PROD1_UAT_Switching?

-Jinshu

This should explain your scenario The BIG-IP system may not reflect the expected status for virtual servers that use iRules, HTTP classes or local traffic policies to select a pool

Not sure why LTPs can't update a VS status like an iRule can.

N

Hi Vikneswaran,

you can attach the iRule below to your Virtual Server to update the status as outlined in SOL6514...

when LB_FAILED {
    if 0 {
        pool UAT_SKY_POOL
        pool UAT_CLOUD_POOL
        pool UAT_BLUE_POOL
        pool UAT_MOON_POOL
    }
}

Note: The

LB_FAILED

if 0 { scriptblock }

Cheers, Kai