Good suggestions James. It worked!
Here is what happened. The installation script of SPMA changed the
snmpmib and snmpmib.bin files to snmpmib.bak and snmpmib.bin.bak,
respectively. It then created/updated the snmpmib but didn't create a new
snmpmib.bin file. Therefore, the snmpmib.bin file didn't exist in
/usr/OV/conf directory.
I moved the /usr/OV/conf/snmpmib.bin.bak to /usr/OV/conf/ snmpmib.bin and
started NetView successfully.
Thanks,
Phat
From: James Shanks <James_Shanks@TIVOLI.COM> on 07/14/99 01:28 PM
Please respond to Discussion of IBM NetView and POLYCENTER Manager on
NetView <NV-L@UCSBVM.ucsb.edu>
To: NV-L@UCSBVM.ucsb.edu
cc: (bcc: Phat D Doan/BCBSO/TBG)
Subject: Re: Spectrum SPMA v3.2 Rev1 on AIX
Well, of all those trapd is the most fundamental. So if you get him
started,
the others will probably follow.
The message says "unable to load mib file". I have not seen that before
but it
sounds like something is wrong with
/usr/OV/conf/snmpmib.bin. One thing you could try then would be to rename
the
existing one and
create a new one, especially if you don't have a backup.
Try this.
(1) mv /usr/OV/conf/snmpmib.bin usr/OV/conf/snmpmib.bin.org
(2) mv /usr/OV/conf/snmpmib usr/OV/conf/snmpmib.org
(3) xnmloadmib
(4) click the Load button and select some very basic MIB like
rfc1213-MIB-II and
load it.
(5) assuming it loads correctly, ovstart trapd
(6) ovstart
Now you can try to figure out how the mib file got messed up.
Good luck.
James Shanks
Tivoli (NetView for UNIX) L3 Support
Phat D Doan <pddoan@REGENCE.COM> on 07/14/99 01:38:48 PM
Please respond to Discussion of IBM NetView and POLYCENTER Manager on
NetView
<NV-L@UCSBVM.UCSB.EDU>
To: NV-L@UCSBVM.UCSB.EDU
cc: (bcc: James Shanks/Tivoli Systems)
Subject: Spectrum SPMA v3.2 Rev1 on AIX
After installing Spectrum SPMA v3.2 Rev1 for AIX, the following Netview
(v5.1.0 on AIX 4.2.1) daemons will not start: trapd, ovtopmd, ovactiond,
nvcorrd, actionsvr, nvserverd, etc. Do you have any suggestion? Thanks.
Phat
******
object manager name: OVsPMD
behavior: OVs_PMD
state: RUNNING
PID: 12624
exit status: -
object manager name: nvsecd
behavior: OVs_WELL_BEHAVED
state: RUNNING
PID: 12370
last message: Initialization complete.
exit status: -
object manager name: pmd
behavior: OVs_WELL_BEHAVED
state: RUNNING
PID: 13558
last message: pmd completed initialization
exit status: -
object manager name: OVORS_M
behavior: OVs_WELL_BEHAVED
state: RUNNING
PID: 14658
last message: orsd completed initialization
exit status: -
object manager name: trapd
behavior: OVs_WELL_BEHAVED
state: NOT_RUNNING
PID: 12100
last message: Unable to load mib file
exit status: exit(1)
object manager name: ovtopmd
behavior: OVs_WELL_BEHAVED
state: NOT_RUNNING
PID: (never run)
last message:
exit status: -
object manager name: mgragentd
behavior: OVs_NON_WELL_BEHAVED
state: RUNNING
PID: 18502
exit status: -
object manager name: ovactiond
behavior: OVs_WELL_BEHAVED
state: NOT_RUNNING
PID: (never run)
last message:
exit status: -
object manager name: nvcorrd
behavior: OVs_WELL_BEHAVED
state: NOT_RUNNING
PID: (never run)
last message:
exit status: -
object manager name: nvpagerd
behavior: OVs_WELL_BEHAVED
state: RUNNING
PID: 16200
last message: PMD initialization complete
exit status: -
object manager name: actionsvr
behavior: OVs_WELL_BEHAVED
state: NOT_RUNNING
PID: (never run)
last message:
exit status: -
object manager name: nvserverd
behavior: OVs_WELL_BEHAVED
state: NOT_RUNNING
PID: (never run)
last message:
exit status: -
object manager name: nvcold
behavior: OVs_WELL_BEHAVED
state: RUNNING
PID: 16986
last message: Initialization complete.
exit status: -
object manager name: snmpCollect
behavior: OVs_WELL_BEHAVED
state: NOT_RUNNING
PID: (never run)
last message:
exit status: -
object manager name: nvlockd
behavior: OVs_WELL_BEHAVED
state: RUNNING
PID: 16458
last message: Initialization complete.
exit status: -
object manager name: gtmd
behavior: OVs_WELL_BEHAVED
state: NOT_RUNNING
PID: (never run)
last message:
exit status: -
object manager name: noniptopod
behavior: OVs_NON_WELL_BEHAVED
state: NOT_RUNNING
PID: (never run)
exit status: -
object manager name: ems_sieve_agent
behavior: OVs_WELL_BEHAVED
state: NOT_RUNNING
PID: (never run)
last message:
exit status: -
object manager name: ems_log_agent
behavior: OVs_WELL_BEHAVED
state: NOT_RUNNING
PID: (never run)
last message:
exit status: -
object manager name: wtpbxd
behavior: OVs_WELL_BEHAVED
state: RUNNING
PID: 19548
last message: Initialization complete.
exit status: -
object manager name: trapgend
behavior: OVs_NON_WELL_BEHAVED
state: RUNNING
PID: 19020
exit status: -
object manager name: ovwdb
behavior: OVs_WELL_BEHAVED
state: RUNNING
PID: 18766
last message: Initialization complete.
exit status: -
object manager name: netmon
behavior: OVs_WELL_BEHAVED
state: NOT_RUNNING
PID: (never run)
last message:
exit status: -
|