RE: [nv-l] vpxdTrap

["Van Order, Drew \(US - Hermitage\)" <dvanorder@deloitte.com>]

Thanks James--it is an acknowledged bug with VMWare either at the agent or the MIB. They have decided not to fix it, rather make customers wait for the next version. We can't wait for them. I figured there was a way to look at what the trap actually sent and adjust NV accordingly. Unless someone eyeballs something obvious I figured the next step is to do a hex dump to see exactly what is coming across. But it does look like what you are listing below--ENTERPRISE. I will try to trick it one more time before hex dumping.

-----Original Message-----
From: owner-nv-l@lists.us.ibm.com [mailto:owner-nv-l@lists.us.ibm.com] On Behalf Of James Shanks
Sent: Thursday, November 18, 2004 11:59 AM
To: nv-l@lists.us.ibm.com
Subject: RE: [nv-l] vpxdTrap

Well, Drew, you'd probably have to get a hexdump of the incoming trap in a trapd.trace, and post it here (or open a problem send it to IBM Support), for me to be sure, but looking at the output message, I'd say offhand that the agent is sending the trap like this:

Enterprise 1.3.6.1.4.1
generic 6
specific 6876

which is why your definition isn't formatting the trap.

trapd.conf already has definitions for 1.3.6.1.4.1 (called ENTERPRISES)  but they only contain the generic entries for coldStart, warmStart, and so on (0 - 5).
Vendors are supposed to add their vendor number when they send unique traps.   You could always try adding an entry , say ENTERPRISE6 for generic 6 and specific 6876 and see whether that formats correctly.  This would get you out of your current problem, but it exposes another.

If I'm right about this, then there is a bug here, either in what vmware is sending, or in how trapd is reading it.    If you like, NetView support can help you determine which, but you'll have to open that problem and send the trace.

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

This message (including any attachments) contains confidential information intended for a specific individual and purpose, and is protected by law. If you are not the intended recipient, you should delete this message. Any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited.