06-02-2009 04:24 PM
Good day,
Hopefully someone can point me in the right direction. I have an environment that contains many different devices and approx 2000 devices. I have discovered approx 1/3. Looking at DFM(ver4 Solaris), I have many devices in the questioned state. Looking in the logs of DFM.log, I find the following:
ADTM-N-TMG2_STATUS_START-Last discovery started at 03-Jun-2009 09:25:16
[03-Jun-2009 09:25:15+884ms] t@52 Discovery #7
ADTM-E-AD_EACCESSADDRESS-While discovering 'lc-rtr-101.pacificaccess.com.au',
Qualified access address not found
ADTM-N-TMG2_STATUS_COMPLETE-Last discovery completed at 03-Jun-2009 09:25:16
But....doing a nslookup on a working device vs a "questioned device" shows the exact oppposite:
Discovered and working device:
bash-2.05# nslookup lc-rtr-121
Server: su-net-01.pacificaccess.com.au
Address: 161.117.200.200
*** su-net-01.pacificaccess.com.au can't find lc-rtr-121: Non-existent host/domain
Non - working device from logs:
bash-2.05# nslookup lc-rtr-101
Server: su-net-01.pacificaccess.com.au
Address: 161.117.200.200
Name: lc-rtr-101.pacificaccess.com.au
Address: 10.117.253.6
Any ideas? Its as if DFM has stored a different domain suffix for the device?
06-02-2009 05:32 PM
Under DFM > Device Management > Rediscover/Delete you will find a reason for why the devices are questioned. What is that reason? What version of DFM is this? DFM 4 is not a valid version.
06-02-2009 06:20 PM
Thanks,
Sorry, there are a few issues. The devices mentioned above are in the "learning state" and stay at 10% completed. No error codes or messages just the extract from the log.
DFM would be version 2.0.3 (no idea where I got the 4 from?)
06-02-2009 06:46 PM
Learning at 10% indicates a problem with one of the daemons. Post the output of the pdshow command. Is the fully qualified hostname of this server resolvable?
06-02-2009 07:40 PM
Ok,
Attached is the pdshow. The server hostname is resolvable:
w12499@cwksvrc101p$ nslookup cwksvrc101p
Server: su-net-01.pacificaccess.com.au
Address: 161.117.200.200
Name: cwksvrc101p.sensis.com.au
Address: 192.148.125.65
Here's what I have found:
1. When the CW is looking for the device, it is resolved to lc-rtr-101.pacificaccess.com.au
But,
The device is configured with:
ip domain-name sensis.com.au
The CW server also being part of sensis.com.au.
Think this is where it gets a bit confused?
06-02-2009 07:50 PM
This all checks out. Post the daemons.log, and the output of ps -efl.
06-02-2009 08:07 PM
06-02-2009 08:40 PM
Your DFM databases contain bad data. You will need to reinitialize. I also recommend you upgrade to LMS 2.6 with DFM 2.0.13 to prevent this from happening in the future. LMS 2.6 can be downloaded from http://www.cisco.com/cgi-bin/tablebuild.pl/lms26 .
To reinitialize the DFM databases, do the following:
/opt/CSCOpx/bin/dbRestoreOrig.pl dsn=dfmInv dmprefix=INV
/opt/CSCOpx/bin/dbRestoreOrig.pl dsn=dfmEpm dmprefix=EPM
/opt/CSCOpx/bin/dbRestoreOrig.pl dsn=dfmFh dmprefix=FH
Then delete /opt/CSCOpx/objects/smarts/local/repos/icf/DFM.rps. Then restart dmgtd.
06-02-2009 08:43 PM
Thank you,
I will get permission to do this. Just quickly, I do not require any more licensing to go 2.5.1 to 2.6? I am just making sure.
I will update post when I have done the above.
Also, how could you tell database corrupt?
Cheers
Pieter
06-02-2009 08:50 PM
No, the 2.5 license will work with 2.6. LMS 2.6 is a free upgrade for 2.5.1 users.
There were sync errors in the daemons.log that pointed to a problem with conflicting data in the various DFM databases.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide