ACE how to debug probes

[sebastianvandijk]

Hi,

We have several probes configured for our serverfarms. Some of the probes and rservers are alerting for timeouts or regex's not found etc.

What's the best way to check if this is a rserver or probe problem ? Using captures ?

Or is it possible to debug the probes ?

Regards,

Sebastian

[Gilles Dufour]

The best solution is to use sniffer trace.

The debug would tell you there is a problem but you still will not be sure where it comes from.

So, go for the sniffer trace.

Gilles.

[sebastianvandijk]

Hi Gilles,

I am trying to capture the packets but i run into a problem :

I create an access-list :

access-list CAPTURE1 line 8 extended permit ip any host 172.30.9.101

access-list CAPTURE1 line 16 extended permit ip host 172.30.9.101 any

The I create the capture :

capture CAPTURE all access-list CAPTURE1 bufsize 5000 circular-buffer

Start the capture :

capture CAPTURE start

Make some bogus connection :

telnet 172.30.9.101 80

Trying 172.30.9.101...

Connected to 172.30.9.101.

Escape character is '^]'.

HTTP/1.1 400 Bad Request

Server: Microsoft-IIS/5.0

Date: Tue, 15 Apr 2008 11:44:35 GMT

Content-Type: text/html

Content-Length: 87

The parameter is incorrect. Connection closed by foreign host.

Stop the capture :

capture CAPTURE stop

Then when i want to display the results, nothing is displayed :

sh capture CAPTURE

What am I doing wrong here ?

Regards,

Sebastian

[igor.nepochatov]

I have had the same problem. Contacted TAC. Was told that Capture feature of ACE does not support capturing traffic for probes, but only works with traffic to/from VIPs. That was a disapointment.  The problem with using the sniffer is if your probes are HTTPS that are encripted which is what I am having an issue with right now.