Re: [nv-l] trapd.conf after migration
2004-08-02 13:34:29
I have no idea what went wrong, but
trapd.conf is easy to fix. And you should have received a message
when the script was run that trapd.conf was being saved as a backup, so
you could restore to that one temporarily.
The error message indicates that you
do not have an enterprise id defined for
IBM6611COLD {1.3.6.1.4.1.2.6.2} 0 0
A 1 0 "Status Events"
so either you should add one or simply
remove those two entries which reference it.
I'd try editing it with xnmtrap (less
chance of making an error) but if that fails, use another editor (vi, emacs,
whatever).
trapd.conf is divided into sections,
so just click add in the Enterprise box and add IBM6611 1.3.6.1.4.1.2.6.2,
then OK your way out and see whether that works.
Or use the other editor to do it or
to remove the traps you mentioned
James Shanks
Level 3 Support for Tivoli NetView for UNIX and Windows
Tivoli Software / IBM Software Group
wolfgang.bergbauer AT attglobal DOT net
Sent by: owner-nv-l AT lists.us.ibm DOT com
08/02/2004 01:04 PM
|
To
| nv-l AT lists.us.ibm DOT com
|
cc
|
|
Subject
| [nv-l] trapd.conf after migration |
|
Hi all,
I have some problems to migrate the trapd.conf. with the tecits_upgrade
script.
After starting trapd I get always the following error message:
object manager name: trapd
behavior: OVs_WELL_BEHAVED
state: FAILED
PID: 145348
last message: No such exact enterprise (7 vs
9) in line #7929 of "/usr/OV/conf/C/trapd.conf":
IBM6611COLD {1.3.6.1.4.1.2.6.2} 0 0 A 1 0 "Status Events".
This is the section:
###
### T h e s e e n t r i e s a d d e d
b y MigrateTrap
###
IBM6611COLD {1.3.6.1.4.1.2.6.2} 0 0 A 1 0 "Status Events"
IBM 6611 - agent up with possible changes (coldStart trap)
SDESC
A coldStart trap signifies that the sending
protocol entity is reinitializing itself such
that the agent's configuration or the protocol
entity implementation may be altered.
EDESC
IBM6611WARM {1.3.6.1.4.1.2.6.2} 1 0 A 1 0 "Status Events"
IBM 6611 - agent up with no changes (warmStart trap)
SDESC
A warmStart trap signifies that the sending
protocol entity is reinitializing itself such
that neither the agent configuration nor the
protocol entity implementation is altered.
EDESC
thanks for your help,
Wolfgang
|
|
|