Nimbostratus
Have you tried creating the monitor manually as described on page 52 of the deployment guide (http://www.f5.com/pdf/deployment-guides/f5-siebel-dg.pdf)?
Can you share what version of Siebel you are running and provide more info about which components are failed when the health monitor does not react?
Do you by chance have a tcpdump of the app server's response to the BIG-IP monitor when all components are working vs. when some are down and the BIG-IP does not react?
We'd certainly like to improve our application-specific monitors to cover as many implementation scenarios as possible and appreciate any additional information you can provide.
Regards,
Holly Willey
F5 Product Management Engineer
