[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference azur::mcc

Title:DECmcc user notes file. Does not replace IPMT.
Notice:Use IPMT for problems. Newsletter location in note 6187
Moderator:TAEC::BEROUD
Created:Mon Aug 21 1989
Last Modified:Wed Jun 04 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:6497
Total number of notes:27359

5622.0. "Looking for Vitalink MIB" by EVTAI1::RENOUVEL () Tue Sep 28 1993 13:09

    
    
    Hye ,
    
    Could somebody tell me where to find the last VITALINK MIB.
    
    We use DECmcc V1.3 using VITALINK_MIBDEF.TXT.
    
    Thanks for your help 
    
    Does a Mib exist for SNMP's ... (certainaly a stupid question...)
    
    Patrick.
T.RTitleUserPersonal
Name
DateLines
5622.1VITALINK MIB - see Vitalink.CUJO::HILLDan Hill-Net.Mgt.-Customer ResidentWed Sep 29 1993 00:2111
    Patrick,
    The best thing would be to call Vitalink and ask for the latest MIB,
    but be sure you have the latest SNMP agent, too.
    
    The SNMP MIB definition file is VITALINK_MIBDEF.TXT .  This is the
    convention used by DECmcc (*_MIBDEF.TXT) development groups.
    
    You may be able to get a pointer to the latest MIB file on the Internet
    if you call Vitalink.
    
    -Dan
5622.2Enterprise specificEVTAI1::RENOUVELWed Sep 29 1993 05:1410
    
    
    Hye,
    
    	Just one more thing ,where could I find the exact definition of
    the Enterprise specific .(SNMP)
    
    Thanks a lot.
    
    Patrick
5622.3More SNMP infoCUJO::HILLDan Hill-Net.Mgt.-Customer ResidentThu Sep 30 1993 01:4017
    Patrick,
    
    I'm not sure I really understand what you're asking, but I'll take a
    shot.
    
    If you are looking for the Enterprise-specific portions of the Simple
    Network Management Protocol, try reading "The Simple Book" by Marshall
    Rose.  Enterprise-specific portions of the MIB tree are discussed.
    
    Basically, enterprise-specific is anything you want it to be, as long
    as your company or your "enterprise" uses a unique (and hopefully
    registered) portion of the MIB tree that follows the ASN.1 syntax
    properly.
    
    Hope this helps.
    
    -Dan
5622.4Just one more thingEVTAI1::RENOUVELThu Sep 30 1993 05:4410
    
    Thanks Dan,
    
    In fact what I would like is to see something else than Enterprise
    specific word appears in my notify request window.
    Could I make the messages of the translan clearly visible.
    
    Thanks for your help.
    
    Patrick.
5622.5Set up your own trap nameCUJO::HILLDan Hill-Net.Mgt.-Customer ResidentMon Oct 04 1993 01:0913
    Patrick,
    
    You can do this by changing the name of the variable in the MIB, or by
    setting up your own enterprise-specific trap variable name which will
    be displayed in the notification window.  Use descriptive variable
    names.
    
    
    You don't have much else you can do in terms of text that can be
    displayed in the notification window.  You are very limited as to what
    you can do here.
    
    -dan
5622.6Pardon ..?EVTAI1::RENOUVELTue Nov 02 1993 07:1011
    
    Hye Dan,
    
    Could you explain me a little bit more ,how to do this.
    
    I'm very interested by.
    
    
    Thanks.
    
    Patrick.
5622.7Quick and dirty HP enterprise SNMP trap setupCUJO::HILLDan Hill-Net.Mgt.-Customer ResidentWed Nov 03 1993 21:5862
The following is a quick and dirty look at setting up an HP MIB to use the 
HP MIB variable "fileSystemName" as a mechanism of shipping your own 
enterprise-specific trap.  Note that you can assign this variable name any
value of the datatype defined for fileSystemName at the top of the MIB.  You
are simply going to use the variable for a quick trap transmission.

	(The top part of the MIB goes here.)
		.
		.
		.
	(At the bottom, just before the END statement, include the following:)

hpVendorTrap1 TRAP-TYPE
	ENTERPRISE	hp
	VARIABLES	{ fileSystemName }
	::=1
 
hpVendorTrap2 TRAP-TYPE
	ENTERPRISE	hp
	VARIABLES	{ fileSystemName }
	::=2
 
hpVendorTrap3 TRAP-TYPE
	ENTERPRISE	hp
	VARIABLES	{ fileSystemName }
	::=3
 
END
---------------------
That's it for the MIB.  Now compile it and load the dictionary via the 
MCC_TCPIP_MTU.COM  MIB translation utility.  Your new MIB trap objects will
be in the dictionary for MCC to use.  
 
You must also set up a notify request via Notification Services.  Bring up the
notification window in the Iconic Map and select "Notify Requests..." & 
"Create..." .   Use Mouse button 3 to display choices for each field.  You
will see your new trap objects in the events field choices.
 
The notify requests may look something like these when completed:
 
Notify Domain .MyDomain Entity List = (snmp * hp *), -
   Event = (hpVendorTrap1, hpVendorTrap2)
 
Notify Domain .MyDomain Entity List = (snmp * hp *), -
   Event = (hpVendorTrap2)
 
Notify Domain .MyDomain Entity List = (snmp * hp *), -
   Event = (Any Configuration Event)
 
 
 
To test that you are getting your traps, use the forms command line thusly:
 
MCC> getevent snmp * hp * any configuration event, for duration 00:10
 
Once you've executed this command, MCC will display all traps received for up
to 10 minutes, that is, any trap that is generated by an HP SNMP agent.
 
If you want to see all traps generated by any agent, don't include the "hp *".
 
-Dan