DFM reports no devices

eosborg · ‎08-10-2011

Hi

Have a problem with LMS 4.0.1 and DFM. In DFM no of the devices leaves the questioned state. Trying to rediscover them starts a process that ends after 20% completion every time. I've put on some debuging, but that does not enable more error messages... Only thing i find is in the log file

D:\CSCOpx\objects\smarts\local\logs\dfm.txt:

[10-Aug-2011 9:47:01 PM+579ms] t@8152 SM_ProtocolEngine-2

ADTM-E-AD_MSG-While discovering 'nts-nro-26.sb1.dh.intra',

CI-EINVALID-Invalid argument "80:0:0:9:3:0:64:0:f1:47:80:80"

CI-EENCODING-Incorrect encoding of hex

As I've encoded this to be the SNMP engine ID, which on the device is:

NTS-NRO-26#show snmp engineID

Local SNMP engineID: 8000000903006400F1478080

Remote Engine ID IP-addr Port

And then I do not understand how to fix the problem :-)

Anyone with a clue ?

kind regards

Erlend Osborg, CCIE# 7224

Gaganjeet Chug · ‎08-11-2011

Hi,

For tesing purpose, kindly check if you have the Engine mentioned for the devices in DCR. If it do exist, delete the Engine ID field and then rediscover the device in DFM.

I have seen this issue before, where deleting the Engine ID from DCR fix the issue.

Thanks,

Gaganjeet

eosborg · ‎08-16-2011

Nope dit not help to delete the engine ID... BTW, I see this on all devices ASR 1002/4 and ISR 3925E

Regards

Erlend

eosborg · ‎08-17-2011

Some info from the DFM.log:

ADTM-N-AD_LOG-17-Aug-2011 12:37:26 PM, at 'TM: create', while discovering

'nts-nro-26.sb1.dh.intra', starting ...

ADTM-N-AD_LOG-17-Aug-2011 12:37:26 PM, at 'DNSClosure', while discovering

'nts-nro-26.sb1.dh.intra', nts-nro-26.sb1.dh.intra Could not be used to

find the System

ADTM-N-AD_LOG-17-Aug-2011 12:37:26 PM, at 'DNSClosure', while discovering

'nts-nro-26.sb1.dh.intra', nts-nro-26.sb1.dh.intra Could not be used to

find the System

ADTM-N-AD_LOG-17-Aug-2011 12:37:26 PM, at 'DNSClosure', while discovering

'nts-nro-26.sb1.dh.intra', send to resolver, default.

ADTM-N-AD_LOG-17-Aug-2011 12:37:29 PM, at 'Callback, bad response', while

discovering 'nts-nro-26.sb1.dh.intra',

. InputData:

. NameOrAddr = nts-nro-26.sb1.dh.intra

. IPAddress = 10.255.0.146

. Community =

. SNMPPort = 161

. SNMPVersion = V3

. SystemType =

. NameFormat =

. SeedName = nts-nro-26.sb1.dh.intra

. DisplayName =

. DomainName =

. DomainSource =

. SourceAddress =

. SNMPState = TM_SNMP

. SourceType = TM_USERADDED

. AccessMode = ICMPSNMP

. AccessAddressFormat = UNKNOWNADDRESSFORMAT

. User = daxuser

. AuthProtocol = SHA

. PrivProtocol = DES

. Context =

. EngineID =

. EngineBoots= 0

. EngineBootTime = 17-Aug-2011 12:37:26 PM

. StartTime = 17-Aug-2011 12:37:26 PM

ADTM-N-AD_LOG-17-Aug-2011 12:37:29 PM, at 'Callback, bad response', while

discovering 'nts-nro-26.sb1.dh.intra',

. OutputData:

. IPAddress = 10.255.0.146

. Community =

. SNMPVersion = V3

. SNMPPort = 161

. IsICMP = FALSE

. IsSNMP = FALSE

. SysDescr =

. SysObjectID =

. SysContact =

. SysName =

. SysLocation =

. DomainName =

. SNMPError =

. User = daxuser

. AuthProtocol =

. PrivProtocol =

. Context =

. EngineID =

. EngineBoots= 0

. EngineBootTime = 17-Aug-2011 12:37:26 PM

.

ADTM-N-AD_LOG-17-Aug-2011 12:37:29 PM, at 'SeedResponse', while discovering

'nts-nro-26.sb1.dh.intra', system name is nts-nro-26.sb1.dh.intra

ADTM-N-AD_LOG-17-Aug-2011 12:37:29 PM, at 'SeedResponse', while discovering

'nts-nro-26.sb1.dh.intra', system type is Host

ADTM-N-AD_LOG-17-Aug-2011 12:37:29 PM, at 'SeedResponse', while discovering

'nts-nro-26.sb1.dh.intra', No response from Ping

ADTM-N-AD_LOG-17-Aug-2011 12:37:29 PM, at 'SeedResponse', while discovering

'nts-nro-26.sb1.dh.intra', add to pending, UNDISCOVERED

IPCheckList is empty.

ADTM-N-AD_LOG-17-Aug-2011 12:37:29 PM, at 'post process', while discovering

'', start ...

Anyone with a clue ?

Kind regards

Erlend

Gaganjeet Chug · ‎08-17-2011

Hi,

Good catch on the logs. So are the devices DNS resolveable. You can check the same with the resolver.pl command from CSCOpx\bin like this :-

C:\Progra~1\CSCOpx\bin>perl resolver.pl .

Also, check if you are able to do snmp walk on the device from the CLI of the server with SNMPv3

Please Navigate to NMSROOT/Objects/smarts/bin.

AuthPriv Mode :

sm_snmpwalk --snmp=3 --user= --auth=

--authPass= --priv=

--privPass= --authengine=

Example :

sm_snmpwalk --snmp=3 --user=cisco --auth=MD5 --authPass=authpwd --priv=DES

--privPass=privpwd --authengine=800000090300020000000100 10.77.213.87

AuthNoPriv Mode :

sm_snmpwalk --snmp=3 --user= --auth=

--authPass= --authengine=

Example :

AuthNoPriv Mode :

sm_snmpwalk --snmp=3 --user=cisco --auth=MD5 --authPass=authpwd

--authengine=800000090300020000000100 10.77.213.87

Without Engine ID :

sm_snmpwalk --snmp=3 --user=cisco --auth=MD5 --authPass=authpwd 10.77.213.87

One issue could be the Engine id issue as I hav seen few cases where after configuring the new engine id on the device, the old user was still there which bind to old engine id and hence the device discovery got failed in DFM.

* Please configure different EngineID (unique) for 2 problematic device.

* Configure SNMP V3 (After change the EngineID, We need to configure the device with v3, Then only the new user will map to new Engine ID.)

* Remove the device from DCR .Then add the device with new credential then Import into DFM.

This may help you to configure the Engine ID :

Example :

CISCO2900(config)#snmp-server engineID local 00000009020000D058EEE700 -----> Create Unique Engine ID

===> After change the EngineID we need to configure the device with v3 then only the new user will map to new Engine ID.

CISCO2900(config)#snmp-server group dec-group v3 auth ---> Snmpv3 configuration

CISCO2900(config)#snmp-server user decuser dec-group v3 auth md5 changeme ----> snmp v3 configuration

Based on this configuration readd the device to DCR.And Import into DFM perform the Discovery.

Hope it helps,

Many Thanks,

Gaganjeet