Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

SLM 2.0 not using correct target IP address

Hi,

I'm using SLM 2.0 to do a roundtrip icmpecho on some of my routers. (router ios is 12.1E)

However, after enabling the SLC, i realise that my router does not show the correct target IP address.

My IP is 10.152.30.33, instead i get 10.63.30.33

I get the below from my router when i do a " sh rtr configuration ".

Entry Number: 3

Owner: 5:slmuser:IcmpEcho@@116@@nwhq01@@1064803881991:10.152.30.33

Tag: 3

Type of Operation to Perform: echo

Reaction and History Threshold (milliseconds): 200

Operation Frequency (seconds): 300

Operation Timeout (milliseconds): 5000

Verify Data: FALSE

Status of Entry (SNMP RowStatus): active

Protocol Type: ipIcmpEcho

Target Address: 10.63.30.33

Source Address: 0.0.0.0

Target Port: 0

Source Port: 0

Doing a sh rtr collection -statistics give me a time-out as below:

Entry Number: 3

Modification Time: 12:46:30.000 CCT Mon Sep 29 2003

Diagnostics Text:

Last Time this Entry was Reset: Never

Number of Octets in use by this Entry: 2802

Connection Loss Occurred: FALSE

Timeout Occurred: TRUE

Over Thresholds Occurred: FALSE

Number of Operations Attempted: 2

Current Seconds Left in Life: 2147483647

Operational State of Entry: active

Latest Completion Time (milliseconds): 0

Latest Operation Start Time: 12:51:30.000 CCT Mon Sep 29 2003

Latest Operation Return Code: timeout

Latest 10.63.30.33

Any advice appreciated.

Thanks.

1 ACCEPTED SOLUTION

Accepted Solutions
Silver

Re: SLM 2.0 not using correct target IP address

Seems like its hitting the bug CSCdv43095. The workaround given in the bug should fix the issue.

1 REPLY
Silver

Re: SLM 2.0 not using correct target IP address

Seems like its hitting the bug CSCdv43095. The workaround given in the bug should fix the issue.

88
Views
0
Helpful
1
Replies
CreatePlease to create content