IPM failed on add HTTP operations

Unanswered Question
Dec 5th, 2008

Hi,

I am experiencing problem when I try to add http operation in collectors. I have a Cat 3560 IP SLA setup as sources and trying to get HTTP IPM to work. I added the http operations by -> HTTP -> URL Lookup http://www.cisco.com. When I tried to add collection that associated source (3560) to operations (cisco.com) I getting this error box and back to IPM: Configuration menu.

IPM: Error Dialog Box

AddCollErrtest

REASON: Invalid Value Specified

LMS version 2.6

IPM 2.6.0

I able to see the IP SLA entry in 3560 but the ip of cisco shows up as 0.0.0.0

Any suggestions are greatly appreciated.

Thanks,

=JL=

====================

3560#show ip sla configuration 17846

IP SLAs, Infrastructure Engine-II.

Entry number: 17846

Owner:

Tag:

Type of operation to perform: http

Target address/Source address: 0.0.0.0/0.0.0.0

Target port/Source port: 80/0

Operation timeout (milliseconds): 5000

Type Of Service parameters: 0x0

HTTP Operation: get

HTTP Server Version: 1.0

URL: http://www.cisco.edu

Proxy:

Raw String(s):

Cache Control: disable

Schedule:

Operation frequency (seconds): 60

Next Scheduled Start Time: Pending trigger

Group Scheduled : FALSE

Randomly Scheduled : FALSE

Life (seconds): Forever

Entry Ageout (seconds): 3600

Recurring (Starting Everyday): FALSE

Status of entry (SNMP RowStatus): notInService

Threshold (milliseconds): 5000

Distribution Statistics:

Number of statistic hours kept: 2

Number of statistic distribution buckets kept: 1

Statistic distribution interval (milliseconds): 20

History Statistics:

Number of history Lives kept: 0

Number of history Buckets kept: 15

History Filter Type: None

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Joe Clarke Fri, 12/05/2008 - 11:43

First, your 3560 must be running 12.2(40)SE or higher as this was the first release to officially support IP SLA. Second, the URL name you're using, http://www.cisco.edu is not valid. Third, the switch must be configured with a DNS server first that is capable of resolving the URL hostname. For example:

ip name-server 10.1.1.1

Once those things are in place, the operation should work correctly.

jayshihlin Fri, 12/05/2008 - 12:01

Hi Jclarke,

Thanks for promptly reply. I am sorry that there was a mistaken in copy & paste because I copied the wrong entry number...

IOS:

I am running 12.2(46)

System image file is "flash:/c3560-advipservicesk9-mz.122-46.SE.bin"

Domain Name:

Name-server was defined already.

I have dns resolver collection in IP SLA which is working fine. Name-server and collector are the same ip address.

===========

3560#show ip sla config 3518

IP SLAs, Infrastructure Engine-II.

Entry number: 3518

Owner:

Tag:

Type of operation to perform: http

Target address/Source address: 0.0.0.0/0.0.0.0

Target port/Source port: 80/0

Operation timeout (milliseconds): 5000

Type Of Service parameters: 0x0

HTTP Operation: get

HTTP Server Version: 1.0

URL: http://www.cisco.com

Proxy:

Raw String(s):

Cache Control: disable

Schedule:

Operation frequency (seconds): 60

Next Scheduled Start Time: Start Time already passed

Group Scheduled : FALSE

Randomly Scheduled : FALSE

Life (seconds): Forever

Entry Ageout (seconds): 3600

Recurring (Starting Everyday): FALSE

Status of entry (SNMP RowStatus): notInService

Threshold (milliseconds): 5000

Distribution Statistics:

Number of statistic hours kept: 2

Number of statistic distribution buckets kept: 1

Statistic distribution interval (milliseconds): 20

History Statistics:

Number of history Lives kept: 0

Number of history Buckets kept: 15

History Filter Type: None

Joe Clarke Fri, 12/05/2008 - 12:15

Everything looks okay here except the SNMP row status. Once the collector has been scheduled, the row status should go to active. This might be a problem with your IPM configuration for this collector. Post a sniffer trace of all SNMP traffic to this switch when configuring your collector from IPM.

jayshihlin Fri, 12/05/2008 - 15:00

Just a curious.. I have DNS, PathEcho, DHCP, IPEcho, and TCP port 80 to MIT.edu. Every entry works expect http. If SNMP packet drop between ciscowork and 3560, should this happen on all entry?

One more though, Can I manually configure IP SLA in the 3560 and have CiscoWork IPM pull or link collector with 3560 rather than push configuration from CiscoWork? Perhaps upgrade to new IPM can help?

Thanks again!

Jay

=====

Entry number: 10879

Owner: 88|ipm-ful-cw2k-Unknown

Tag: IPSLA_143a255_M

Type of operation to perform: tcp-connect

Target address/Source address: 18.7.22.69/0.0.0.0

Target port/Source port: 80/0

Type Of Service parameter: 0x0

Operation timeout (milliseconds): 60000

Control Packets: disabled

Schedule:

Operation frequency (seconds): 61

Next Scheduled Start Time: Start Time already passed

Group Scheduled : FALSE

Randomly Scheduled : FALSE

Life (seconds): Forever

Entry Ageout (seconds): 3600

Recurring (Starting Everyday): FALSE

Status of entry (SNMP RowStatus): Active

Threshold (milliseconds): 5000

Distribution Statistics:

Number of statistic hours kept: 2

Number of statistic distribution buckets kept: 1

Statistic distribution interval (milliseconds): 20

History Statistics:

Number of history Lives kept: 0

Number of history Buckets kept: 15

History Filter Type: None

Enhanced History:

>>>>>>>>>>>>

Entry 3518 is http to cisco.com

3560##show ip sla stat

Round Trip Time (RTT) for Index 3518

Number of successes: Unknown

Number of failures: Unknown

Operation time to live: 0

Round Trip Time (RTT) for Index 5013

Latest RTT: 8 ms

Latest operation start time: 14:52:10.464 PST Fri Dec 5 2008

Latest operation return code: OK

Number of successes: 22

Number of failures: 0

Operation time to live: Forever

Round Trip Time (RTT) for Index 7097

Latest RTT: 125 ms

Latest operation start time: 14:52:07.654 PST Fri Dec 5 2008

Latest operation return code: OK

Number of successes: 5

Number of failures: 3

Operation time to live: Forever

Round Trip Time (RTT) for Index 10398

Latest RTT: 2 ms

Latest operation start time: 14:53:06.231 PST Fri Dec 5 2008

Latest operation return code: OK

Number of successes: 60

Number of failures: 0

Operation time to live: Forever

Round Trip Time (RTT) for Index 10879

Latest RTT: 100 ms

Latest operation start time: 14:52:53.632 PST Fri Dec 5 2008

Latest operation return code: OK

Number of successes: 27

Number of failures: 0

Operation time to live: Forever

jayshihlin Mon, 12/08/2008 - 11:45

Hi Joe,

I have the wireshark captured between SLA switch and Ciscowork. Since information is kind of sensitive I am wondering if I can email or PM you instead post here?

Thanks,

=J=

Joe Clarke Mon, 12/08/2008 - 11:49

If you cannot post the trace, then you will need to open a TAC service request with the information.

Joe Clarke Fri, 12/05/2008 - 15:20

The ability to import collects from devices is in IPM 4.1 using the CLI command "ipm importcollector".

jayshihlin Mon, 12/08/2008 - 11:52

Okay, I will try upgrade IPM to newer version and see if it works.

Thanks,

=J=

Actions

This Discussion