Conference azur::mcc

4980.0. "SNMP AM V1.3.0 : traps & variables pb ?!?" by ZTOIS1::VISTA (Renato VISTA, SIS Strasbourg, France) Fri Apr 30 1993 05:10

    Hi,
    
    Working with DECmcc/BMS V1.3.0 an trying to get enterpriseSpecific
    traps from a CHIPCOM EMM V3.0 and CHIPCOM EMM V3.2 Advanced, I've got
    the following message :
    
    MCC> getevent snmp * chipcom chipportdown
    
    SNMP LOCAL_NS:.snmp.etoile1 chipcom
    AT 1993-04-30-08:42:43.637I----- CONFIGURATION EVENTS
    
    Received event had less object ids than were defined in the dictionary:
    Event: chipPortDown
    A chipPortDown trap was received:
                                 enterprise = "1.3.6.1.4.1.49"
                                 agent-addr = 16.188.48.108
                               generic-trap = enterpriseSpecific
                              specific-trap = 11
                                 time-stamp = 62451
                            olPortSlotIndex = 3
                                olPortIndex = 1
                           olPortAdminState = enabled
                               olPortStatus = linkFailure
    
    The ASN1 source file is for this trap :
    ...
    chipPortDown TRAP-TYPE
            ENTERPRISE      chipcom
            VARIABLES       { olPortSlotIndex,
                              olPortIndex,
                              olPortAdminState,
                              olPortStatus,
                              olEnetStatsPortLastSrcAddr}
            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
    ...
    
    Please note that I've got this file from CHIPCOM themselves (to manage
    EMM V3.0/V3.2 Advanced and TRMM V1.0/V1.11/V2.0).
    Please also note that the field 'olEnetStatsPortLastSrcAddr' has been
    set by me, to receive and display the MAC address which may set to
    DISABLE a port when the active MAC address is NOT the expected MAC
    address ; in this case, the GETEVENT request is good...
    
    MCC>notify domain .demo_openlink_v13 entity list=(snmp * chipcom),
    		events=(any events)
    %%%%%%%%%%%%%% Event, 1993-04-30-09:04:37. %%%%%%%%%%%%%% [1]
    Domain: LOCAL_NS:.demo_openlink_v13                   Severity:
    Indeterminate
    Notification Entity: SNMP LOCAL_NS:.snmp.etoile1 chipcom
    Event Source: SNMP LOCAL_NS:.snmp.etoile1 chipcom
    Event: chipPortDown
    A chipPortDown trap was received:
                                 enterprise = "1.3.6.1.4.1.49"
                                 agent-addr = 16.188.48.108
                               generic-trap = enterpriseSpecific
                              specific-trap = 11
                                 time-stamp = 4507
                            olPortSlotIndex = 4
                                olPortIndex = 2
                           olPortAdminState = disabled
                               olPortStatus = security_breach
                 olEnetStatsPortLastSrcAddr = %X08002b047f37
    
    
    My question is : 
    
    Is there any way of describing that an SNMP variable sent to DECmcc,
    may be OPTIONAL (instead to be considered as MANDATORY, as it seems
    to be the case here) ?
    
    Thank you for your replies.
    Regards,
    Renato