In our example the microkernel traffic shows under the "error" field a handler counters that's incrementing.
see the following snapshot and the highlighted area { arrow }
![](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh4bfTTRByA6dbvy3WOWZE4HbvBcGsO8ZkSOI-VCBYidrHYltIrE9W5j0oZc6ca-q3ij4y7NstEgopj6KB9aFjQ21Ey8mj2BOl2LYoT3cOBDM1bgshQsQvcSgbrKsXcUxhfvXZYesGrJjw/s640/Screen+Shot+2017-04-12+at+3.39.06+PM.png)
From the webGUI you have something similar;
This is not a error per-se . When the TMM tries to process a traffic flow for packets that it has no reference for, this counter will increment.
This is could be caused by numerous conditions.
static ARP for a address not bound on the LTM
inbound traffic for a service port not configured
traffic for a VS not on the LTM
etc.......
Speaking with a f5 support engineer, we didn't find any quick means for monitoring the specific traffic that triggers this counter , but you can lab this up and by using a static arp entry send a traffic request to the F5 and for a VS or Self not-reference for that dst-ip and you will see the counter increment per-request.
Ken
NSE ( network security expert) and Route/Switching Engineer
kfelix -----a----t---- socpuppets ---dot---com
^ ^
=( @ @ )=
o
/ \
No comments:
Post a Comment