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

LMS/IPM 4.0.0 - Problem With Collector Source Device

Previously I only add 2 device on IPM device management. Later I add all devices. But the problem now is when I want to create the collector, the source only shown 2 devices, for destination it shown all. I had add/removed...restart service..all not help.

Why this happen, anything I missed out ?

7 REPLIES
Cisco Employee

Re: LMS/IPM 4.0.0 - Problem With Collector Source Device

How did you add all devices to IPM? If you added them as adhoc targets, then that's what they will be: targets. If you want all devices to be sources, you can either enable auto-sync with DCR under IPM > Admin > Application Settings, or you can go to IPM > Collector Management > Add Devices, and add devices from DCR by clicking the Add Devices button. Devices that support the CISCO-RTTMON-MIB will be automatically added as Source devices. If they do not support this MIB, they will only be available as Targets.

New Member

Re: LMS/IPM 4.0.0 - Problem With Collector Source Device

Hi,

I am only add all devices via IPM > Collector Management > Add Devices. I did turn off auto-sync, it remain the same, the source is only 2 device shown.

The router that appear in list was CISCO3825 and I had 4 unit of it same IOS, but only one appear.

How to check the router support CISCO-RTTMON-MIB ?

Cisco Employee

Re: LMS/IPM 4.0.0 - Problem With Collector Source Device

Please post the output of an snmpwalk of 1.3.6.1.4.1.9.9.42 for routers missing from the source list. Note: these days you need a feature set higher than IP BASE to get IP SLA support.

New Member

Re: LMS/IPM 4.0.0 - Problem With Collector Source Device

I did on all the routers, 7206/3825 router have no problem.

The following is a SNMP walk of device 122.255.97.7 starting from .1.3.6.1.4.1.9.9.42

SNMP Walk Output

--------------------------------------------------------------------------------

.1.3.6.1.4.1.9.9.42

CISCO-RTTMON-MIB::rttMonApplVersion.0 = STRING: 2.2.0 Round Trip Time MIB

CISCO-RTTMON-MIB::rttMonApplMaxPacketDataSize.0 = INTEGER: 16384 octets

CISCO-RTTMON-MIB::rttMonApplTimeOfLastSet.0 = Timeticks: (0) 0:00:00.00

CISCO-RTTMON-MIB::rttMonApplNumCtrlAdminEntry.0 = INTEGER: 27962

CISCO-RTTMON-MIB::rttMonApplReset.0 = INTEGER: ready(1)

CISCO-RTTMON-MIB::rttMonApplPreConfigedReset.0 = INTEGER: ready(1)

CISCO-RTTMON-MIB::rttMonApplSupportedRttTypesValid.echo = INTEGER: true(1)

CISCO-RTTMON-MIB::rttMonApplSupportedRttTypesValid.pathEcho = INTEGER: true(1)

CISCO-RTTMON-MIB::rttMonApplSupportedRttTypesValid.udpEcho = INTEGER: true(1)

CISCO-RTTMON-MIB::rttMonApplSupportedRttTypesValid.tcpConnect = INTEGER: true(1)

CISCO-RTTMON-MIB::rttMonApplSupportedRttTypesValid.http = INTEGER: true(1)

CISCO-RTTMON-MIB::rttMonApplSupportedRttTypesValid.dns = INTEGER: true(1)

CISCO-RTTMON-MIB::rttMonApplSupportedRttTypesValid.jitter = INTEGER: true(1)

CISCO-RTTMON-MIB::rttMonApplSupportedRttTypesValid.dhcp = INTEGER: true(1)

CISCO-RTTMON-MIB::rttMonApplSupportedRttTypesValid.ftp = INTEGER: true(1)

CISCO-RTTMON-MIB::rttMonApplSupportedRttTypesValid.13 = INTEGER: true(1)

CISCO-RTTMON-MIB::rttMonApplSupportedRttTypesValid.16 = INTEGER: true(1)

CISCO-RTTMON-MIB::rttMonApplSupportedProtocolsValid.ipIcmpEcho = INTEGER: true(1)

CISCO-RTTMON-MIB::rttMonApplSupportedProtocolsValid.ipUdpEchoAppl = INTEGER: true(1)

CISCO-RTTMON-MIB::rttMonApplSupportedProtocolsValid.ipTcpConn = INTEGER: true(1)

CISCO-RTTMON-MIB::rttMonApplSupportedProtocolsValid.httpAppl = INTEGER: true(1)

CISCO-RTTMON-MIB::rttMonApplSupportedProtocolsValid.dnsAppl = INTEGER: true(1)

CISCO-RTTMON-MIB::rttMonApplSupportedProtocolsValid.jitterAppl = INTEGER: true(1)

CISCO-RTTMON-MIB::rttMonApplSupportedProtocolsValid.dhcpAppl = INTEGER: true(1)

CISCO-RTTMON-MIB::rttMonApplSupportedProtocolsValid.ftpAppl = INTEGER: true(1)

CISCO-RTTMON-MIB::rttMonApplSupportedProtocolsValid.32 = INTEGER: true(1)

CISCO-RTTMON-MIB::rttMonApplSupportedProtocolsValid.34 = INTEGER: true(1)

CISCO-RTTMON-MIB::rttMonApplProbeCapacity.0 = INTEGER: 27962

CISCO-RTTMON-MIB::rttMonApplFreeMemLowWaterMark.0 = INTEGER: 38177468

CISCO-RTTMON-MIB::rttMonApplLatestSetError.0 = STRING:

CISCO-RTTMON-MIB::rttMonApplResponder.0 = INTEGER: false(2)

CISCO-RTTMON-MIB::rttMonAppl.15.0 = INTEGER: 0

New Member

Re: LMS/IPM 4.0.0 - Problem With Collector Source Device

2 device appear on source , 1 unit is 3825 router , another unit is cat3560 switch.

This switch I did snmpwalk, no RTT MIB, but it do appear.

It is a way to reset the IPM db or configuration. SO can start from ground zero.

I did reset db on CM/DFM , it help on this kind devices inconsistent problem.

The following is a SNMP walk of device 122.255.97.242 starting from .1.3.6.1.4.1.9.9.42

SNMP Walk Output

--------------------------------------------------------------------------------

.1.3.6.1.4.1.9.9.42

Failed to snmpwalk the device. Please check your community string and starting OID, and try again.

cgm
New Member

Re: LMS/IPM 4.0.0 - Problem With Collector Source Device

Did you find an answer for this ?

I kind of have the same issue.

One of four identical routers shows as valid source, all show ok as destinations.

This router was not being added at first (auto) because it showed as already in ipm !!???

After an ipm delete, it was added an it's the

only one working.

More info: IPM is running in a slave DCR, at first the synch was not ok, so I broke it (standalone) and made it again.

cgm
New Member

Re: LMS/IPM 4.0.0 - Problem With Collector Source Device

Found another thread with the "answer".

Somehow DCR had bad credentials for some of the devices, SNMP WR is the one that matters for

collection sources.

I say "somehow" because all routers have same

credentials, and the same default credentials

were used at discovery for all...

610
Views
0
Helpful
7
Replies
CreatePlease to create content