In the release notes, in the section in migration, it tells you to run a
script that checks trapd.conf for these too-long lines. The out
put tells you exactly which lines they are. Then you have to edit it.
This is required for this kind of a merge to work.
If you have no Cisco traps defined, and are brave, you could try
just appending the section of the file that has the definitions you
need. Make a backup of the correct file, look them both over
carefully, add the enterprises you need, and then concatenate
or paste them together. I have had pretty good luck doing this
if I am careful. (James is going to say this is a bad idea and he
is right, of course.) When you think you have it right, send that event
that tells trapd that it has changed (look at the help for the event
command), and try opening the dialog and see how it looks. If you
have a problem with it, restore the file.
Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking
"Mahesh Tailor" <MTailor@carilion.com> on 04/04/2001 01:33:01 PM
To: Leslie Clark/Southfield/IBM@IBMUS
Subject: Re: [NV-L] Format trap manually
Hope you don't mind my writing directly without going through the NV
I ran the above command as stated in the release notes and I get an error
that says that there is a 99-token limit. I opened a ticket with Tivoli
support and they told me I needed to go through my
/usr/OV/conf/C/trapd.conf file and edit all entries that have more than 99
words in them. I have a trapd.conf file that has about >14,000
definitions and this would be quite an undertaking. [And, that this was
an awk limitation.]
So, here's my question: have you had to deal with this with your clients?
If so, what have you done in this situation.
Most of the trap definitions were from Compaq Insight Manager and FORE
Systems and they registered just fine.
Any insight/help you can provide will be greatly appreciated.
Carilion Health System