Re: [nv-l] trapd.conf and 40 character trap name length

[James Shanks <jshanks@us.ibm.com>]

That 40 character limit is as old as
the hills as far as NetView for UNIX is concerned.  Many other processes
depend on it (like the Trap Settings node in a ruleset) for us to consider
changing it.  And the xnmtrap GUI has always enforced it, to prevent
one from creating too long a name to start with. So I am curious to know
how Dell had you add this trap configuration added to trapd.conf.  


An addtrap script?   We took an
APAR some time ago to have addtrap truncate names if they were too long
and put out a message to that effect.  

Was it by nvaddtrapdconf from an existing
trapd.conf extract?  
Or just by manual edit and include?
  

 The only way you could test these
last two ways first would be to issue "event -e FMTCHG"  while
trapd was still running.  Then he'd tray to load the new one, and
if there were errors, spit out a message to trapd.log and the event window
telling you the line of the first error, just like what you saw when you
tried to bring him back up. Except that if he were already up, he'd stay
running and continue to use the old configuration, to give you a chance
to fix it and try again.  

Dell may have based their trapd.conf
file on the Windows product, which has a bigger limit, because it does
not have the same facilities (like nvrsEdit) and thus the same limitations.

James Shanks
Level 3 Support  for Tivoli NetView for UNIX and Windows
Tivoli Software / IBM Software Group

"Bursik, Scott {PBSG}" <Scott.Bursik@pbsg.com>
Sent by: owner-nv-l@lists.us.ibm.com

05/27/2004 03:18 PM

Please respond to
nv-l

To	"Nv-L (nv-l@lists.us.ibm.com)" <nv-l@lists.us.ibm.com>
cc
Subject	[nv-l] trapd.conf and 40 character trap name length

NetView 7.1.3 AIX 4.3.3
 
 
Dell has a product called
 
Dell OpenManage Connection for Tivoli TME
10 Netview for AIX, AIX, English, Multi System, v. 1.4, A00 dated 3/27/2002
 
Basically it loads the MIBS and trap configuration
for the Dell Openmanage applications into NetView using a shell script.
The nice thing is all of the MIBS are in one location and the trap configuration
is already done. It’s one stop shopping for loading Dell SNMP information.
 
Here is the issue I had. After running the
script everything appeared to be OK. I was doing some testing and attempted
to restart the daemons. Trapd failed to come back up and I got this message:
 
[/usr/OV/bin]>ovstart trapd
 object manager name: trapd
 behavior:        
   OVs_WELL_BEHAVED
 state:        
      FAILED
 PID:          
      30922
 last message:      
 trapd.conf file not loaded because trap name length [41] exceeds
maximum size permitted of 40
  in line #14149 of "/usr/OV/conf/C/trapd.conf":
dmtfMotherboardPhysicalDeviceStatusChange
{.1.3.6.1.4.1.412.2.4.6} 6 2 a 1 0 "Status Events".
 exit status:        
-
 
After looking in the /usr/OV/conf/C/trapd.conf
I saw that there were 42 traps loaded that exceeded 40 characters in the
trap name. I had to manually delete the traps from the trapd.conf before
I could get the trapd daemon to start.
 
Has anyone else had this issue? Was my solution
in editing the trapd.conf an acceptable solution?
 
I am going to open a ticket with Dell and
let them know about the trouble.
 
Thanks,
 
Scott Bursik