cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
902
Views
10
Helpful
9
Replies

IPM 4.1 with IOS 12.4(20)T

longfanterry
Level 1
Level 1

Hello,

I am using IPM 4.1 with ICMP-Echo to monitor C1841 ( IOS 12.4(20)T ). But the monitor is always fail. Using snmp browser tools, i find that oid "rttMonEchoAdminTargetAddress" value is "00:00:00:00". But before IOS 12.4(20)T, "rttMonEchoAdminTargetAddress" value should be icmp-echo target ip address. Does anyone has solution on this problem? Thanks!

9 Replies 9

Joe Clarke
Cisco Employee
Cisco Employee

Yes, the target address should be the IP address of the target node. It would be useful to see a sniffer trace of SNMP traffic to the source router when you configure this collector in IPM. Perhaps there is a misconfiguration in IPM as I could not find any bugs specific to this on 12.4(20)T.

Hi jclarke,

Yes, i know what you said. But i can use the same icmp-echo monitor in IPM 4.1 to monior this C1841 with any IOS version before 12.4(20)T. No matter what i config in IPM 4.1, even i set CLI commands in C1841 console as below:

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

ip sla 30

icmp-echo 192.168.11.134

ip sla schedule 30 start-time now life forever

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

Using snmp browser tools, the value of "rttMonEchoAdminTargetAddress" is also "00:00:00:00", not the icmp-echo target address.

I don't know why. If anyone don't believe this, all can try to see the result.

I still can't find an exact matching bug. However, I did find two serious IP SLA bugs in 12.4(20)T which were both fixed in 12.4(20)T2. I also tested this on 12.4(22)T, and it works correctly. Is it possible that you can upgrade your 1841 to 12.4(20)T2, and see if this problem persists?

Hi jclarke,

So thanks for your help. I will try later. Btw, which feature set you use for test? i use "sp services" for test now.

My 12.4(22)T router is running adventservicesk9.

Hi jclarke,

I have tested both "c1841-adventerprisek9-mz.124-22.T.bin" and "c1841-spservicesk9-mz.124-22.T.bin". "adventerprisek9" is ok, but "spservicesk9" is fail. You may try the following command in CLI:

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

ip sla 30

icmp-echo 192.168.11.134

ip sla schedule 30 start-time now life forever

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

Then using SNMP Browser tools to see the different value of "rttMonEchoAdminTargetAddress" in the above IOS versions.

I have been able to reproduce this. The source and target addresses are being reversed. I'm checking with development to see if this is a bug.

Hi jclarke,

Thanks for your kindly help. And i can give you some more information about this case. I have tested 12.4(20)T/12.4(20)T2/12.4(22)T/12.4(22)T1/12.4(24)T, only advance enterprise services feature set edition can be monitored by IPM ICMP-Echo.

I have filed CSCsy37122 to track this.

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: