Brad,
I don't think anyone really answered your question.
Correct me if I'm wrong, but, you don't really need the mib to identify what
NT is sending. 
You already know that it is the coldstart trap.
My guess is that you are seeing an error in the event log because the
Microsoft version of the Generic coldstart trap is not defined in NetView.

Fix (Adding a new trap definition):
1. Open the trap customization window (Options) and look at NetView's
coldstart trap definition.
2. Add Microsoft as a new Enterprise using 1.3.6.1.4.1.311 as the ID.
3. Add a new trap definition for coldstart
   Make it look just like NetView's ColdStart trap except in the Event Log
Message change IBM to Microsoft.
4. Click [OK] all the way back out.

That will fix those undefined ColdStart traps from Microsoft....
Loading the MIB (definition file) has nothing to do with defining the trap.
I used to tell my students that NetView does not need the MIB file loaded,,,
YOU do.
Loading the mib file makes life easier when using any of the mib
applications, like the browser, application builder or data collection. The
mib file is just the schema of the SNMP agent's Management Information Base.

Best regards,
Don Davis


-----Original Message-----
From: Brad Martin [mailto:bmartin AT MetLife DOT com]
Sent: Wednesday, August 08, 2001 1:45 PM
To: IBM NetView Discussion
Subject: [NV-L] Microsoft NT MIB





Does anyone know if there is a MIB definition file for Windows NT. I
haven't been able to find one on the Microsoft website or NT Resource Kit
that describes the coldStart traps we're receiving.

Example:

997287624  3  Wed Aug 08 12:20:24 2001 en1280.metlife.com        ? Agent Up
with Possible Changes (coldStart Trap) enterprise:ENTERPRISES
(1.3.6.1.4.1.311.1.1.3.1.3) args(0):


Brad Martin
MetLife





_________________________________________________________________________
NV-L List information and Archives: http://www.tkg.com/nv-l

------------------------------------------------------------------------------
This electronic mail and any files transmitted with it are confidential and are 
intended solely for the use of individual or entity to whom they are addressed. 
If you are not the intended recipient or the person responsible for delivering 
the electronic mail to the intended recipient, be advised that you have 
received this electronic mail in error and that any use, dissemination, 
forwarding, printing, or copying of this electronic mail is strictly 
prohibited. If you have received this electronic mail in error, please 
immediately notify the sender by return mail.