Forum Discussion
NimbostratusASM bypass_upon_load variable
By default, the bypass kicks in if the system idle is under 10% (i.e., is 90% used); this can be altered by changing the "bypass_under_high_cpu" system variable from 10 to some other value.
/usr/share/ts/bin/add_del_internal update bypass_under_high_cpu <value>
Sample log when the event has started:
"High CPU Utilization: event code I617 Bypassing ASM"
There is no log indicating the event has ceased, you'll just stop seeing additional logs.
NimbostratusAndrew we have a follow up question:
if bypass_upon_load is left disabled, meaning upon high load the 'spill over' traffic will be blocked, what can we expect the customer experience to be like during that? Is the response page issue for the block or does it simply appear as latency in the browser?
Please advise.
Thank you.
EmployeeTo the best of knowledge the F5 will simply drop SYNs for new connections.
