4.5 rule seems to sometimes fail

Hi Farid--

 

 

While this is more of a tech supportish question, a representative manual testing strategy would be something like the following:

 

 

1) start tcpdump (snapsize > MTU) on both sides of the traffic

 

2) wait for an occurrence of the problem you're seeing

 

3) verify the dumps verify that what you think you're seeing is really occurring

 

 

Keeping things on-topic, you might use iControl to do something like the following from a test client (assumption: a pristine bigip is available as a device under test -- DUT):

 

 

1) use iControl to reset* the configuration on the DUT

 

2) use iControl to create a new appropriate configuration

 

2) generate scads of requests with 00 at the end that span the DUT

 

3) use iControl to query* the DUT's stats to ensure your numbers are reasonable

 

 

*while there's generally adequate protection to ensure you don't lock yourself out when you do this, it's possible. Bottom line: initial testing may require a box with easy physical access.

 

 

**theoretically, the idea of using information from the DUT to validate the rule evaluation is BAD but (unless you're explicitly testing statistics) it's surprisingly useful in practice. For those who're ideological about this, it's only slightly more cumbersome to have the servers themselves report who they are. You then coalesce the statistics yourself to verify you have the right answer. *chuckle* I suppose for extra credit you could then use iControl or SNMP to query the DUT to verify your answer.

 

 

--Brad