Conference azur::mcc

3051.0. "CHIPCOM/ASN.1/SNMP_AM T1.2.7/TRAPS messages" by ZTOIS1::VISTA (Renato VISTA, SIS Strasbourg, France) Thu May 21 1992 10:51

    
    Hi,
    
    I'm working in a DECmcc/ULTRIX T1.2.7 environment on a DECstation
    5000/25 (24 MB) platform for managing CHIPCOM hubs via SNMP/TCPIP AM
    and CHIPCOM private MIBs.
    
    Note that I've added the CHIPCOM private ASN.1 MIB, by loaded the
    file CHIPCOM_HUB3_BRG_10BT_MIBDEF.TXT because I've downloaded the new
    V3.0 firware (BASIC) for EMM (Ethernet Management Module).
    
    With that configuration, I've tested the ability of DECmcc to track
    SNMP traps from CHIPCOM EMM V3.0 Agent.
    
    Two main actions have been firstly done :
    
    1) On CHIPCOM EMM V3.0 console mode (serial RS-232 port), I've done the
    command :
    
    SET COMMUNITY traps 16.188.48.8 OldTrap
    
    	...to be able to receive old traps (ie non-enterprise specific
    	traps like Linkup, Linkdown, WarmStart, ColdStart, ...see file
    	chipcom_hub21_mibdef.txt ASN.1 file corresponding to previous CHIPCOM
    	EMM V2.1 module)
    
    	...and...
    
    SET COMMUNITY traps 16.188.48.8 Trap
    
    	...to be able to receive new Traps, enterprise specific traps
    	ONLY !!
    
    Of course...
    
    SET ALERT CHANGE ENABLE
    
    ...has also been done.
    
    
    
    2) On DECmcc, I've created the following request :
    
    NOTIFY REQUEST .demo_openlink ENTITY LIST = (SNMP *), -
    	EVENTS = (ANY EVENTS)
    
    
    
    To test to configuration, I've simply plug out one of the three ports
    of a 5103M-AUIM module (ie Ethernet Transceiver AUI Male 3 Ports Module)
    currently set in slot 3 of the CHIPCOM hub.
    
    At this moment I've got messages...
    
    1) ON the CHIPCOM console :

    Enterprise:                 Chipcom
    Enterprise Specific trap:   Port Down
    
    Message Information:
            Slot Number :   3
            Port Number :   1
            Port Mode :     ENABLED
            Port Status :   LINK FAILURE
                                                                                    
    
    2) ON the DECmcc session :
    
--> The new trap ... Note that specific-trap 11 means "chipPortDown" and
    that I've got NO INFORMATION about the port itself !!!...
    
%%%%%%%%%% Event, 1992-05-21-12:48:43. %%%%%%%%%%%%%% [3,33]
Domain: LOCAL_NS:.demo_openlink                       Severity: Indeterminate
Notification Entity: SNMP LOCAL_NS:.snmp.etoile 
Event Source: SNMP LOCAL_NS:.snmp.etoile 
Successfully received event(s): 
Event: enterpriseSpecific
An enterpriseSpecific trap was received:
                             enterprise = "1.3.6.1.4.1.49"
                             agent-addr = 16.188.48.100
                           generic-trap = enterpriseSpecific
                          specific-trap = 11
                             time-stamp = 788729
    
    

--> The old trap ... (note that the ifIndex 33 is the logical IP interface
    number of the Port 1, Slot 3 physical port, i.e. 16*2 + 1)...

%%%%
%%%%%%%%%%%%%% Event, 1992-05-21-12:48:44. %%%%%%%%%%%%%% [3,34]
Domain: LOCAL_NS:.demo_openlink                       Severity: Indeterminate
Notification Entity: SNMP LOCAL_NS:.snmp.etoile 
Event Source: SNMP LOCAL_NS:.snmp.etoile 
Successfully received event(s): 
Event: linkDown
A linkDown trap was received:
                             enterprise = "1.3.6.1.4.1.49.1.3.1.0"
                             agent-addr = 16.188.48.100
                           generic-trap = linkDown
                          specific-trap = 0
                             time-stamp = 788729
                                ifIndex = 33


    
    
    
    In fact, the enterpriseSpecific trap sent by the EMM V3.0 agent and
    received in a CHIPCOM_HUB3_BGR_10BT new CHIPCOM private MIB context, is
    described in ASN.1 as following :
    
    
    ...
    
-- Traps for use by Chipcom

-- Traps are defined using the conventions in RFC 1215.


chipPortDown TRAP-TYPE
	ENTERPRISE 	chipcom
	VARIABLES	{ onlinePortAdminState, onlinePortStatus }
	DESCRIPTION
		"A chipPortDown trap indicates that a port's status
		has changed to an error condition.  Multiple chipPortDown
		traps may be sent if the port's status changes from
		one error to another."
	::= 11

    ...
    
    Note that the syntax allows the ability of describing accurate
    information about the port itself.
    
    Note alse that the ONLY value returned and displayed by DECmcc is the
    final assigned value, i.e. ::= 11 (meaning = ChipPortDown)
    
    
    For my customer, it would strongly interesting to be notified via
    DECmcc interface about more detailed information !!! (example of the 
    chipSlotDown trap which seems to be able to the Slot Index
    information...)
    
chipSlotDown TRAP-TYPE
	ENTERPRISE 	chipcom
	VARIABLES	{ onlineModSlotIndex }
	DESCRIPTION
		"A chipSlotDown trap indicates that management communications
		with the slot indicated by onlineModSlotIndex has been 
		broken.  This event usually occurs when a module has been
		physically removed from the concentrator.  However, it
		is possible for this event to occur when the particular
		module fails."
	::= 2
    
    
    So, the questions are :
    
    1)	Is the ASN.1 CHIPCOM private MIB for EMM V3.0 source file, in the
    expected ASN.1 consise definition language ?
    
    2)  Is the the MTU MIB Translator Utility able to translate and
    integrate in DECmcc Dictionary those kinds of syntax and semantic
    correctly ? (Note that no track of those new enterprise specific traps
    and their related detailed information, has been recorded in the DECmcc
    Dictionary)
    
    3)	Is that message limite due to ULTRIX SNMP Daemon definition (i.e.
    options to set in snmpd.conf file) ?
    
    4)	Is the NOTIFICATION_FM of DECmcc/ULTRIX T1.2.7 able (or has to
    be set to) to decode SNMP Traps detailed messages ?
    
    
    Thank you for your ideas, your opinion and your help !!!
    
    Regards,
    Renato
                                                       

Renato,

	V1.2 of DECmcc (more specifically the SNMP am and Mib Translator),
doesn't support handling the objects included in a vendor specific trap.

	This functionality is planned for the next release.

Dan

    I am in the process of setting up DECmcc to manage about 35 Chipcom hubs.
    The hubs have UTP cards and mainly connect PCs. I want to set up alarms
    so that if I loose a module I get an alarm. I don't want to alarm at
    the port level.
    The only way that I have worked out how I can do this is by setting
    alarms on the generic_trap "enterpriseSpecific".
    
    So my alarm :
    	occurs(SNMP Chip1 enterpriseSpecific)  etc etc
    
    triggers twice, once when the slot goes down and then again when the
    slot comes up. 
    
    I see from .1 of this note that the TCp/IP am does not support
    specific_trap information. So the fact that when the slot goes down and
    the trap reports:
    			generic-trap = enterprisespecific
    			specific-trap = 2
    
    and when it comes back up it reports
    			generic-trap = enterprisespecific
    			specific-trap = 3
    
    it is no good to me as I can not alarm on this specific information. 
    
    What I would like to know is
    
    1. Is there a better way to alarm on a slot going down, ie have I
    missed something here. What would be nice is for the alarm information
    to be able to tell you what slot went down as well. My method does not
    do this. 
    
    2. The other thing that is worrying me is that I have no idea what
    other things cause a "enterprisespecific" trap to happen.
    So by using this trap as my method it may give me alarms on other
    events that I don't want. I only fell onto using this trap name by picking 
    up information from .0 of this note. I have the Chipcom manual but it does
    not mention traps. How do I find out what traps are generated by the
    chipcom and their names. Does any one have a list ??
    
        
    Thanks for any help,
    Jill