RE: [nv-l] Unknown trap in trapd.log

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

Actually, you'll have to do more than
just load rfc2737 to format the trap.  That requires mib2trap, and
because the Entity MIB (RFC 2737) isn't complete you'll need to concatenate
it's predecessor.  Or just use this  script
=================================================================

/usr/OV/bin/addtrap -l entConfigChange -g 6 -s 1 \
  -i 1.3.6.1.2.1.47.2 \
  -n entityMIBTrapPrefix  \
  -o A  -c "LOGONLY" -t 0 \
  -S 1  \
  -D "An entConfigChange notification is generated when the value
of entLastChangeTime changes. It can be utilized by an NMS
to trigger logical/physical entity table maintenance polls.

An agent should not generate more than one entConfigChange
'notification-event' in a given time interval (five seconds
is the suggested default).  A 'notification-event' is the
transmission of a single trap or inform PDU to a list of
notification destinations.

If additional configuration changes occur within the
throttling period, then notification-events for these
changes should be suppressed by the agent until the current
throttling period expires.  At the end of a throttling
period, one notification-event should be generated if any
configuration changes occurred since the start of the
throttling period. In such a case, another throttling period
is started right away.

An NMS should periodically check the value of
entLastChangeTime to detect any missed entConfigChange
notification-events, e.g., due to throttling or transmission
loss."  \
  -e entConfigChange  \
  -F '$E $G $S $# args: $*'

=============================================================================

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

"Stringfellow, William" <William.Stringfellow@bankofamerica.com>
Sent by: owner-nv-l@lists.us.ibm.com

02/19/2004 01:32 PM

Please respond to
nv-l

To	nv-l@lists.us.ibm.com
cc
Subject	RE: [nv-l] Unknown trap in trapd.log

Scott,
                Try loading the RFC 2737 MIB and see if that doesn't make your trap format correctly.

                Regards,
                Bill

Bill Stringfellow
EDS - Bank of America Account Team
Network Management Support
CA4-704-02-03
2000 Clayton Road, Building D
Concord, CA 94520

Office:     925.692.7283
Fax:        925.675.1763
Email:     william.stringfellow@eds.com
Cell:       925.765.2648

-----Original Message-----
From: Bursik, Scott {PBSG} [mailto:Scott.Bursik@pbsg.com]
Sent: Thursday, February 19, 2004 9:56 AM
To: Nv-L (nv-l@lists.us.ibm.com)
Subject: [nv-l] Unknown trap in trapd.log


NetView 7.1.3 AIX 4.3.3

I am receiving these traps from some Cisco Switches and I am not sure what I
need to load to get this resolved.


1077212826 2  Thu Feb 19 11:47:06 2004 paintsr1.pepsi.com        ? NO FMT IN
TRAPD.CONF: mgmt.mib-2.47.2 (1.3.6.1.2.1.47.2) generic:6 specific:1 args(1):
[1] mgmt.mib-2.47.1.4.1.0 (Ticks): 1254

Thanks,

Scott Bursik