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

IPM Collector - Stuck on configuring

Hello,

I defined DefaultIpEcho collector between CAT65K (source) and GSS, CAT65K (source) and ASA. But in both cases the collector status is showing as 'configuring'.

What does it imply.

Thanks.

18 REPLIES
Cisco Employee

Re: IPM Collector - Stuck on configuring

This could simply mean you need to force a refresh of the Collector Management screen. However, it could indicate a problem with the SNMP read-write credentials in DCR, configuration on the switch, or the software running on the switch.

New Member

Re: IPM Collector - Stuck on configuring

CAT65K is running 12.2(33)SXH3 which support "ip sla monitor" commands.

Is SNMP read only string sufficient for IPM or is write string mandatory.

If I need to modify the device credentials and do the changes in DCR via Common Services would it automatically be picked by device listing in RME, IPM, HUM etc or is there a refresh mechanism for these modules.

New Member

Re: IPM Collector - Stuck on configuring

Now the IPM Collectors are stuck on "deleting" after I deleted couple of them. How can these by removed from the list.

Cisco Employee

Re: IPM Collector - Stuck on configuring

Try restarting Daemon Manager, or try adding the missing credentials, then see if the collectors can be deleted.

Cisco Employee

Re: IPM Collector - Stuck on configuring

You must have SNMP read-write to use IPM. Yes, as soon as you add new credentials to DCR, they will be picked up by the various applications.

New Member

Re: IPM Collector - Stuck on configuring

I restart the Daemon Manager and then restarted the server itself. When I invoke IPM, I get the following error

Error in communicating with IPMProcess or IpmDbEngine.

It may be down or not yet up. Please make sure processes are up and running

Please assist.

Cisco Employee

Re: IPM Collector - Stuck on configuring

You may just need to wait. It can take the daemons a good 30 minutes to fully initialize after a restart.

New Member

Re: IPM Collector - Stuck on configuring

Ok. Its running now.

Thanks.

New Member

Re: IPM Collector - Stuck on configuring

Will I be able to use ASA as the target device because ASA's do not support SNMP write strings. Does IPM use read-write only for the IP SLA device (Source device).

Cisco Employee

Re: IPM Collector - Stuck on configuring

SNMP is only required for the source device. The target devices can be any IP addressable node for the icmpEcho operation.

New Member

Re: IPM Collector - Stuck on configuring

How can I open up UDP ports (numbers) on the firewall for Default icmpJitter operation to work.

Cisco Employee

Re: IPM Collector - Stuck on configuring

ICMP jitter uses ICMP. No UDP ports need to be open between source and target.

New Member

Re: IPM Collector - Stuck on configuring

Ok. I will check on that.

What is the difference between operation types defaultIpecho, Echo connectionloss, Echo timeout, Echo rtt.

They all show Latency graph with the same value.

Also what is the difference between Echo and EthernetPing operation types.

Lastly, why doesn't EthernetPing show on the system-defined operation list but only user defined.

Thanks

Cisco Employee

Re: IPM Collector - Stuck on configuring

Are you referring to reaction types? There is only one icmpEcho. There are other built-in operations to adjust the QoS for the ICMP data, but everything else is the same. The reaction types allow you to control when a reaction event is triggered (e.g. when a trap is sent). This can be if a connection loss event is detected, if the collector exceeds the pre-configured timeout, or if the total round-trip response time is above a configured threshold. A reaction configuration is optional.

Echo refers to ICMP ping. Ethernet Ping is used in metro ethernet configurations to test layer 2 connectivity over ethernet.

The Ethernet Ping requires additional configured, and a completely configured pre-built operation cannot be created.

New Member

Re: IPM Collector - Stuck on configuring

With regards to DCR if the management IP's are configured, all modules RME, Campus Manager etc would use them.

However, if the application performance is to be gauged then IPM should be configured on Production traffic Interface and not the Management interface/IPs.

How can we manage different set of IPs for IPM target device to check the network performance.

Cisco Employee

Re: IPM Collector - Stuck on configuring

While IPM is capable of using a configurable source IP address, it is not yet capable of using a specific destination target address. I filed an enhancement request for this a while ago (CSCsz66719). However, a patch has been created to add this functionality. The patch (for IPM 4.2) is available from the TAC.

New Member

Re: IPM Collector - Stuck on configuring

I think using Adhoc Target Device for this purpose is quite helpful. It worked for me.

Cisco Employee

Re: IPM Collector - Stuck on configuring

Yes, if possible, that will work. However, if you want to measure UDP jitter, then adhoc targets will not work.

325
Views
5
Helpful
18
Replies
CreatePlease to create content