IPSLA configuration for HTTP

Unanswered Question
Jul 9th, 2009

Hi,

We have requirement for generating latency report for few of our Web applications which runs on http & https.

I tried configuring IPSLA using our LMS 3 - IPM, 6500 switch as Source (collector), web server IP as target and custom operation created for HTTP.

But collector status showing as config failed

I was not clear with the procedure for creating HTTP operation (URL relative path ?).

Need help on creating a operation & collector for generating a latency report for web applications.

Thanks,

Guru

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
Joe Clarke Thu, 07/09/2009 - 10:27

What version of code is running on the 6500? You must also make sure you have DNS configured on the switch in order to use hostnames in your collector.

gururajan Thu, 07/09/2009 - 10:30

Thanks for your reply.

6500 Code is 12.2(33)SXH and i will check the DNS configuration part.

Can you provide me more clarity on configuring the HTTP operation

Thanks,

Guru

Joe Clarke Thu, 07/09/2009 - 10:38

Create a new operation of type HTTP. Specify the relative path as the URI you want to download. For example, if you want to test http://www.domain.com/index.php, the relative path is /index.php. Unless you need to use a custom HTTP port, or proxy, everything else can be the default.

When creating the collector, just specify the correct target host (www.domain.com in this example), and that should work provided DNS is configured correctly, and you have entered the switch's correct SNMP read-write credentials in DCR.

gururajan Tue, 07/14/2009 - 22:22

Thanks for your response.

I have checked the DNS configuration and it is fine. But collector configuration is still getting failed.

Attached the screen shots and output from Switch for your reference.

Please suggest how to fix this.

Thanks & Regards,

Guru

Attachment: 
Joe Clarke Wed, 07/15/2009 - 08:30

Get a sniffer trace of all SNMP traffic between the IPM server and the device when configuring your collector. That will indicate what object is triggering the configuration failure.

Actions

This Discussion