IPMAP failure

[sbeaulieu]

I'm running NNM for NT 6.2. My problem is that at first, the segment which the server belonged to was not being discovered, but everything beyond it was. I blew away the map database and redid the seed file and tried opening up the OpenView application and now I'm getting nothing but a bunch of the following:

(hostname): Fatal IPMap Error: Field name is not unique

Any ideas of where I should start looking? I've verified the hostname (computer name is a CNAME) and cross checked the CNAME forward and reverse.

This problem came about after I blew away the map database and reaccomplished the seed file, along with the ovaddobj command. Thanks.

SBeaulieu

 

[vlan52]

Hi there sbeaulieu, looks like you have a corrupted object db, anyway, down below you'll find a great procedure that works all the time, I haven't wrote this one, but since I'm sure you are in a hurry go ahead and give it a try, step by step:

1. ovmapdump -v|grep 'Application Object Id'

Application Object Id: 18627

2. ovobjprint -o 18627


OBJECT: 18627

FIELD ID FIELD NAME FIELD VALUE
10 Selection Name "IP Map [default]"
526 IPMap Enabled TRUE
528 Status On TRUE
529 Status to Lines TRUE
530 Node IP Status TRUE
531 IPMap App Config IV Switch FALSE
532 IPMap Map Close Time 952575245
533 IPMap Demand Level All Levels(1)
534 IPMap Apply Filters TRUE
535 IPMap Map Filter 1 ""
536 IPMap Map Filter 2 ""
537 IPMap Map Filter 3 ""
538 IPMap Map Filter 4 ""
539 IPMap Map Filter 5 ""
540 IPMap Persistence Filter 1 ""
541 IPMap Persistence Filter 2 ""
542 IPMap Persistence Filter 3 ""
543 IPMap Persistence Filter 4 ""
544 IPMap Persistence Filter 5 ""
545 IPMap Version 3

3. If you get the error on the step 2 that the object was not found ,
it means the object DB was corrupted. IPMAP can not find that object
in the object DB and complains of it. You can check this for other
maps using

ovmapdump -v -m <map name>|grep 'Application Object Id'

I was able to reproduce the problem. I renamed $OV_DB/openview/ovwdb
and did
ovstart ovwdb
ovw -fields
ovstart
ovw
and got the same errors.

4. To fix the problem you have to restore the whole directory
$OV_DB/openview from the backup or do the procedure

Stop Everything and Start Discovery Over Again
(on page 169 of &quot;Managing Your Network&quot; for NNM 6.1.)

1. Stop all of NNM's services (background processes):
As root, at the command prompt, type ovstop

2. Since this step deletes NNM?s topology, object, and map databases
and your maps, you may wish to back up your existing databases
before proceeding (see &quot;Backup/Restore to Protect Your Investment of
Time&quot.
If you have customized NNM's configuration (discovery configuration,
SNMP configuration, event configuration, or data collection and
threshold monitoring, etc.) none of these configurations are affected
by this step.

Execute the following:

Type cd /var/opt/OV/share/databases/openview

rm -rf /var/opt/OV/share/databases/openview/*/*

NOTE If you are using a database other than the one embedded in NNM, see
NNM's online manual, Reporting and Data Analysis.

3. Optional: To remove the old error messages and start again, execute
the following:

Type cd /var/opt/OV/share/databases/eventdb
rm -rf /var/opt/OV/share/databases/eventdb/*/*

4. Restart NNM's services. NNM runs initial discovery, populates the
databases, and generates a new map:

At the command prompt, type:

xnmsnmpconf -clearCache

/opt/OV/bin/ovstart ovwdb

/opt/OV/bin/ovw -fields

/opt/OV/bin/ovstart

Hope this helps, let us know if it doesn't, regards,
vlan52
vlan52
The end of wisdom is freedom. The end of culture is perfection. The end of
education is character. The end of knowledge is love.