Conference azur::mcc

	Normally, enterprise specific trap definitions are a small part
	of the mib. Many vendor mibs do not have any traps defined
	at all. A major portion of most mibs are devoted to definitions
	of objects on which you can do SHOW and SET operations. ( Novell's
	mib may be an exception). Once you compile and load the mib into
	the DECmcc dictionary, the SNMP AM effectively gets to know of the
	existence of these objects and allows you to do SET and SHOW operations
	on them.

	V1.3 of DECmcc SNMP AM will be able to provide to the user all the
	information provided in enterprise specific traps. It is ready to
	go into field test any day. 

	Hope this answers all your questions.

	Rahul.

    
    Hi Timo,
    
    I'm interested by your NOVELL private MIBs. Is it possible for you either 
    to post them in the current note, or to send me them to ZTOIS1::VISTA ?
    
    Thank you for your cooperation.                                      
    
    Regards,
    Renato
    

Well, after having done some browsing around, I found some more MIB pieces for 
Novell. Actually I have 2 files. One is called NM2SNMP.MIB, which seems to
contain all the enterprisespecific traps that I was talking about in 0. 
Another one is called NXPPLUS.MIB. This one works together with the NXPPLUS
software that comes with NMS (Novell's 'mcc'). This MIB containes some protocol
tables and other Novell info.
So I wanted to load both files, and that's where I ran into the following 
problem :

As stated in .0, I first compiled NM2SNMP.MIB without problems. Than I compiled
NXPPLUS.MIB. When doing this, the compiler said that the Novell brach already
existed and if I wanted to replace or augment the tree. By accident I selected
REPLACE . This worked fine. I now could have a look at some specific tables
on Novell servers. Than I tried to compile NM2SNMP.MIB again, since I had 
REPLACED them. Again, the compiler said that Novell already existed and if
I wanted to REPLACE or augment. I selected AUGMENT. Than I got the following 
error:

  $ MTU NSDP$SYSTEM:[MCC.NOVELL.TRAPMIBS]NW2SNMP.MIB;
Entity Model tree is being pruned.
The following non-leaf objects are being removed:
Child entity netware_MIB
Child entity netware_GA_alert_mib
MIB translation completed successfully.
   2-DEC-1992 14:08:45

Phase 1 for file NSDP$SYSTEM:[MCC.NOVELL.TRAPMIBS]NW2SNMP.MIB; completed.

Beginning Phase 2 for file NSDP$SYSTEM:[MCC.NOVELL.TRAPMIBS]NW2SNMP.MIB;

Now checking DECmcc data dictionary for subclass novell ...
%DAP-S-USE_DICT, Using dictionary file: nsdp$system:[mcc]mcc_fdictionary.dat;6
Found definition.

The definition for the novell MIB
  already exists in the DECmcc data dictionary.
You have the option of REPLACING or AUGMENTING this definition.

Do you want to REPLACE the existing definition? (Y/N) [Y]: n

Do you want to AUGMENT the existing definition? (Y/N) [Y]:

   2-DEC-1992 14:09:05
Now starting to run the MSL Translator ...
This may take approximately 1-10 minutes.
Issuing following command:
  $ MANAGE/TOOLKIT/SPECIFICATION NW2SNMP.MS
DECmcc Management Specification Language Translation Tool
               Version V1.2

%MCCMSL-S-NORMAL, Scan of MS file has completed successfully
MSL translation completed successfully.
   2-DEC-1992 14:09:18

Editing NW2SNMP.COM ...
Editing of NW2SNMP.COM completed.

   2-DEC-1992 14:09:22
Now starting to update the DECmcc data dictionary ...
This may take approximately 1-15 minutes.
Issuing following command:
  $ MANAGE/TOOLKIT/DICTIONARY LOAD FROM NW2SNMP.COM
%DAP-S-USE_DICT, Using dictionary file: nsdp$system:[mcc]mcc_fdictionary.dat;6
%DAP-I-LINENUMB, At or near line number 6.
%DAP-I-CMD_LINE, Command: CREATE CLASS SNMP  SUBCLASS NOVELL  SUBCLASS PRODUCTTY
PE CODE 1
%MCC-E-ENTEXIST,  specified entity definition exists already

An error occurred while trying to update the DECmcc data dictionary.

   2-DEC-1992 14:09:29

Procedure terminated in error.
%NONAME-E-NOMSG, Message number 0326CEDA


Any ideas how to solve this?

reply .-1: The NW2SNMP.MIB that came with the NMS software works with the agent
   that comes with 3.11 server software. It only seems to contain netware 
    specific traps. I don't think there is a problem with distributing this MIB.
   The NXPPLUS.MIB, which gives you additional info about the server, like
   protocol tables,login names etc. is only of use, if you have the NXPPLUS
    software on your server. This software is coming with the NMS software.
   I'll try to find out from Novell, what pieces of software/MIBS can be
   freely distributed and for which ones we have to pay. 
   Stay tuned

Timo

	Unfortunately, in V1.2 the ability to augment an existing mib 
	in the dictionary is limited. The augmentation works for mibs
	with a certain structure, but does not work for others. The only
	option you have is to combine the two mibs by hand and then load
	it into the dictionary as a single mib. If you have trouble doing
	this, then mail me the two mibs and I will merge it for you.

	All restrictions for augmenting mibs have been removed for V1.3.
	If you are not in a hurry, you might want to wait for V1.3.

	Rahul.

>	V1.3 of DECmcc SNMP AM will be able to provide to the user all the
>	information provided in enterprise specific traps. It is ready to
>	go into field test any day. 

Well, I installed T 1.3 and repeated my experiment with enterprisespecific
traps. When such a trap comes in, I see:

MCC> notify domain .valbonne events=(any event), entity=(snmp nmssrv)
%MCC-S-NOTIFSTART, Notify request 1 started
MCC>

%%%%%%%%%%%%%% Event, 21-DEC-1992 11:14:56 %%%%%%%%%%%%%% [1]
Domain: LOCAL_NS:.valbonne                            Severity: Indeterminate
Notification Entity: SNMP LOCAL_NS:.nmssrv
Event Source: SNMP LOCAL_NS:.nmssrv
Event: enterpriseSpecific
An enterpriseSpecific trap was received:
                             enterprise = "1.3.6.1.4.1.23.2.8"
                             agent-addr = 16.36.144.53
                           generic-trap = enterpriseSpecific
                          specific-trap = 3
                             time-stamp = 7000

while the MIB , that I used to load the trap definition , shows:

translatorUp            TRAP-TYPE
                        ENTERPRISE      netware-GA-alert-mib
                        DESCRIPTION
                                "The Netware to SNMP translator NLM is up."
                        --#TYPE "NW2SNMP NLM up"
                        --#SUMMARY "NetWare to SNMP NLM up on %s"
                        --#ARGUMENTS {0}
                        --#SEVERITY INFORMATIONAL
                        --#TIMEINDEX 2
                        --#HELP "nmm.hlp"
                        --#HELPTAG 64587
                        --#STATE  OPERATIONAL
                        ::= 3

So what is 'additional' info, compared with V1.2? I would have expected for
example the 'DESCRIPTION' text when the notify goes of. 
If I look at the notification with IMPM, there is a 'Details' field, which
is always empty in my case. What is this field used for? 
It doesn't look to me as if I  am getting more info about an 'enterprisespecific' 
trap, in T1.3 compared with V1.2. Or am I doing something wrong?

Thanks

Timo 

>while the MIB , that I used to load the trap definition , shows:
>
>translatorUp            TRAP-TYPE
>                        ENTERPRISE      netware-GA-alert-mib
>                        DESCRIPTION
>                                "The Netware to SNMP translator NLM is up."
>                        --#TYPE "NW2SNMP NLM up"
>                        --#SUMMARY "NetWare to SNMP NLM up on %s"
>                        --#ARGUMENTS {0}
>                        --#SEVERITY INFORMATIONAL
>                        --#TIMEINDEX 2
>                        --#HELP "nmm.hlp"
>                        --#HELPTAG 64587
>                        --#STATE  OPERATIONAL
>                        ::= 3
>
>So what is 'additional' info, compared with V1.2? I would have expected for
>example the 'DESCRIPTION' text when the notify goes of. 
>If I look at the notification with IMPM, there is a 'Details' field, which
>is always empty in my case. What is this field used for? 
>It doesn't look to me as if I  am getting more info about an 'enterprisespecific' 
>trap, in T1.3 compared with V1.2. Or am I doing something wrong?



    Please not that almost all of the fields in the trap definition were
    commented out (the lines preceded by the "--" characters).  If you
    comment out all of the variables that describe the event, then how do
    you expect the DECmcc to be able to decode the trap?!?!

    /doug

>    Please not that almost all of the fields in the trap definition were
>    commented out (the lines preceded by the "--" characters).  If you
>    comment out all of the variables that describe the event, then how do
>    you expect the DECmcc to be able to decode the trap?!?!

Point taken. However, I don't see the 'description' either. I just loaded the
MIB as I got it. Do you mean that I can just remove all the '--#' and DECmcc
will show me than all this info?
I could give it a try..

thanks

Timo

>>Point taken. However, I don't see the 'description' either. I just loaded the
>>MIB as I got it. Do you mean that I can just remove all the '--#' and DECmcc
>>will show me than all this info?
>>I could give it a try..


	Not really. The comments (prefixed with "--") does not use SMI 
	syntax and would cause the mib compiler to complain.

	There are two things you are missing.

	1) The enterprise specific events have to be requested under the
	   enterprise child entity to get additional information.

	MCC> GETEVENT SNMP * NOVELL ANY EVENT

	or

        MCC> notify domain .valbonne events=(any event), -
	MCC_> entity=(snmp nmssrv novell)

	2) The VARIABLES clause in the trap definition in the mib indicates
	   what the additional information is. From your mib definition
	   it seems that no VARIABLES clause is present, and hence no
	   additional information will be displayed by the SNMP AM.

	Rahul.

Well, I tried this and it does work from the FCL, but not when I set it up
through IMPM. 

	MCC> GETEVENT SNMP * NOVELL ANY EVENT

SNMP LOCAL_NS:.nmssrv novell
AT 22-DEC-1992 14:47:24 Any Event

Received event had more object ids than were defined in the dictionary:
Event: translatorUp
A translatorUp trap was received:
                             enterprise = "1.3.6.1.4.1.23.2.8"
                             agent-addr = 16.36.144.53
                           generic-trap = enterpriseSpecific
                          specific-trap = 3
                             time-stamp = 30360

>	2) The VARIABLES clause in the trap definition in the mib indicates
>	   what the additional information is. From your mib definition
>	   it seems that no VARIABLES clause is present, and hence no
>	   additional information will be displayed by the SNMP AM.

I realize that DECmcc cannot show the variables , since I removed them from
the MIB (I still haven't found out where these variables are defined).

Now that things are more clear, leaves me with three questions:

1. Does the above mean that for enterprisespecfic traps, I would ONLY see
   the VARIABLES section? If so, in what format?

2. Would I somewhere see the DESCRIPTION field from the MIB?

3. Would all this be shown in the 'details' field in the IMPM window?

Thanks

Timo

>>Now that things are more clear, leaves me with three questions:

>>1. Does the above mean that for enterprisespecfic traps, I would ONLY see
>>   the VARIABLES section? If so, in what format?

	You would see all the variables defined in the mib under the
	VARIABLES clause. These variables will be displayed in the same
	format as the other event arguments.

>>2. Would I somewhere see the DESCRIPTION field from the MIB?

	The text in the DESCRIPTION clause will end up as help text, if
	you chose YES to help generation while running MTU. It will not
	show up as part of the enterprise specific trap.

>>3. Would all this be shown in the 'details' field in the IMPM window?

	It should.

	Rahul.

    one more quick note.  When entering the notify command with
    an entity list argument, if the entity specified is a global
    entity (eg: SNMP *) then the notify command assumes that you
    want events on the global entity *AND* all of its children. 
    You whould not have to specify SNMP * NOVELL to see them
    unless they are the only events you want (if a child is specified
    we assume that you want events only on that child).