Jace_45978
Nov 02, 2009Nimbostratus
v10.0.1 cpu0 goes off on its own
6900 LTM running v10.0.1 HF2 4 core unit
LTM shows that the CPUs are all balanced during the day normally around 40% (during peek time traffic) we are doing ssl termination and hardware compression.
There was a need to add the following iRule:
rule XXComRestrictVHostsProd {
when HTTP_REQUEST priority 50 {
if {[HTTP::header exists Host]} {
set hostHeader [HTTP::header Host]
if { $hostHeader equals {admin.xx.com} or $hostHeader equals {tool.xx.com} } {
log local0. "Potential header manipulation detected. Received request for $hostHeader from [IP::client_addr]"
HTTP::header replace Host www.xx.com
}
}
}
}
When this rule was applied to the VS it was originally applied with the log local0 un-commented and the cpu0 would run a 80% during mid traffic time while the other 3 cores would be 10%...during peek time the cpu0 would max at 100% and cause the site to be extremely slow. Commenting the log local0 causes the cpu0 and the other cpus to line up and have a nice balance around 40% during peek time.
We do have a ticket open but was curious if anyone has any insight to why cpu0 would max out while using the above iRule and the log function. Even with the log function enabled the /var/log/ltm was not getting much if any data from this irule unless we generated the known condition.
normal operation of this LTM is over 100k connections, 250ssl_tps, 600 new connects/sec,
thanks