<div>
The timeout needs to be 3x the interval plus 1 second, and the defaults are 5 and 16 seconds, respectively. If you shorten those numbers and you have a high latency network, you might see the health monitor churn the pool members in and out of available status. I wouldn't shorten those timers for standard web traffic, especially if your health check is ICMP or a TCP half-open check.
</div>


The timeout needs to be 3x the interval plus 1 second, and the defaults are 5 and 16 seconds, respectively. If you shorten those numbers and you have a high latency network, you might see the health monitor churn the pool members in and out of available status. I wouldn't shorten those timers for standard web traffic, especially if your health check is ICMP or a TCP half-open check.

<div>
So you want to keep it the default or is there any recommended timer i need to configure it.<br />
What is the standard practice Administrators follow.
</div>


So you want to keep it the default or is there any recommended timer i need to configure it.
What is the standard practice Administrators follow.

<div>
<div class="content wysiwyg-content">
I have a BIG IP F5 load balancer load balancing 2 Web servers.<br />
I want to set the monitoring parameter to check the health check of both the Web servers.<br />
In case if any one of the Web server is down the BIG IP will alert via mail.<br />
I would like to understand what is the standard &amp;&nbsp;best practice to set the • &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;interval-in-seconds &nbsp;&amp; time out in interval.<br />
what is the recommened values suggested for this .
</div>
</div>


I have a BIG IP F5 load balancer load balancing 2 Web servers.
I want to set the monitoring parameter to check the health check of both the Web servers.
In case if any one of the Web server is down the BIG IP will alert via mail.
I would like to understand what is the standard & best practice to set the •	interval-in-seconds  & time out in interval.
what is the recommened values suggested for this .

BIG IP F5 LB

Networking software modules are interfaced with a framework implemented on the machine's operating system that implements the networking functionality of the operating system. The best known frameworks are the TCP/IP model and the OSI model. Systems typically do not use a single protocol to handle a transmission. Instead they use a set of cooperating protocols, sometimes called a protocol family or protocol suite.[9] Some of the best known protocol suites include: IPX/SPX, X.25, AX.25, AppleTalk and TCP/IP. Other protocols indirectly related to networking include the hypertext transfer protocol (HTTP) and its related technologies, Dynamic Host Configuration Protocol (DHCP), Domain Name Server (DNS) and other Internet protocols.

Networking Protocols

Network Management involves issues that are independent of specific hardware or software, including email policies, upgrade planning, backup scheduling and working with managed service providers for Desktop-As-A-Service (DaaS), Software-As-A-Service (SaaS) and the like through the use of tools, coupled with manufacturer standards, best practice guidelines, policies and procedures plus all other relevant documentation. Network management also includes monitoring, alerting and reporting, management reporting, planning for device or service updates, the backup of configurations, the setting of key performance indicators and measures (KPIs/KPMs), associated service level agreements and problem records as part of the IT Service Management (ITSM) framework.

Network Management

Networking hardware includes the physical devices facilitating the use of a computer network. Typically, networking hardware includes gateways, routers, network bridges, modems, wireless access points, networking cables, line drivers, switches, hubs, and repeaters. But it also includes hybrid network devices such as multilayer switches, protocol converters, bridge routers, proxy servers, firewalls, network address translators, multiplexers, network interface controllers, wireless network interface controllers, ISDN terminal adapters and other related hardware.