[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

4316.0. "enterpriseSpecific Traps & MCC T1.3.0 ???" by ZTOIS1::VISTA (Renato VISTA, SIS Strasbourg, France) Mon Dec 28 1992 09:31

    Hi,

    I'm testing DECmcc/BMS T1.3.0 and SNMP asynchronous traps sent by a
    CHIPCOM EMM V3.0 module as following (using
    CHIPCOM_HUB3_BRG_10BT_MIBDEF.TXT private MIB) :

    mcc>notify domain (snmp * chipcom),event=(any event)

    Of course, community name is correctly defined (checked by provoking an
    authenticationFailure by giving a bad password in any mcc/fcl
    command...).

    When I remove physically a module from the hub, expecting an
    enterpriseSpecific chipSlotDown (with OnlineModSlotIndex variable
    returned as argument to DECmcc/SNMP event sink process), NO trap
    message is displayed...

    When using the following command,

    MCC>getevent snmp * chipcom chipslotDown

    ... I obtain...

    SNMP LOCAL_NS:.snmp.etoile1 chipcom
    AT 28-DEC-1992 14:59:19 CONFIGURATION EVENTS

    Received event had more object ids than were defined in the dictionary:
    Event: chipSlotDown
    A chipSlotDown trap was received:
                                 enterprise = "1.3.6.1.4.1.49"
                                 agent-addr = 16.188.48.108
                               generic-trap = enterpriseSpecific
                              specific-trap = 2

                                 time-stamp = 986153
                         onlineModSlotIndex = 4



    MCC>getevent snmp * chipcom chipslotUp

    getevent snmp * chipcom chipslotUp

    SNMP LOCAL_NS:.snmp.etoile1 chipcom
    AT 28-DEC-1992 15:16:52 CONFIGURATION EVENTS

    Received event had more object ids than were defined in the dictionary:
    Event: chipSlotUp
    A chipSlotUp trap was received:
                                 enterprise = "1.3.6.1.4.1.49"
                                 agent-addr = 16.188.48.108
                               generic-trap = enterpriseSpecific
                              specific-trap = 3
                                 time-stamp = 1091485
                         onlineModSlotIndex = 4

    In this last command, expected onlineModType variable is NOT displayed...

    My questions are :

    1) what is the meaning of

    "Received event had more object ids than were defined in the
    dictionary:" ?

    2) why the expected variables are not displayed ?

    3) is it possible to ckeck what is really returned with MCC_TCPIP_MQ
    utility ? If YES, what is the number of the queried variable (no
    information about the number has been found in
    CHIPCOM_HUB3_BRG_10BT_MIBDEF.LIS file) ?

    Thank you for your help.
    Regards,
    Renato
                                  
    
T.RTitleUserPersonal
Name
DateLines
4316.12582::YAHEY::BOSETue Dec 29 1992 15:3252
	Renato,

		Notification of enterprise specific events seem to work
	correctly on my system (X1.3.5).

MCC> notify domain bose entity = (snmp * chipcom), event = (any event)
%MCC-S-NOTIFSTART, Notify request 2 started


%%%%%%%%%%%%%% Event, 29-DEC-1992 14:38:35 %%%%%%%%%%%%%% [2]
Domain: MOLAR_NS:.bose                                Severity: Indeterminate
Notification Entity: SNMP MOLAR_NS:.chipcom chipcom
Event Source: SNMP MOLAR_NS:.chipcom chipcom
Event: chipFatal
A chipFatal trap was received:
                             enterprise = "1.3.6.1.4.1.49"
                             agent-addr = 16.31.112.23
                           generic-trap = enterpriseSpecific
                          specific-trap = 8
                             time-stamp = 698


>>    MCC>getevent snmp * chipcom chipslotUp

>>    getevent snmp * chipcom chipslotUp

>>    SNMP LOCAL_NS:.snmp.etoile1 chipcom
>>    AT 28-DEC-1992 15:16:52 CONFIGURATION EVENTS

>>    Received event had more object ids than were defined in the dictionary:
>>    Event: chipSlotUp
>>    A chipSlotUp trap was received:
>>                                 enterprise = "1.3.6.1.4.1.49"
>>                                 agent-addr = 16.188.48.108
>>                               generic-trap = enterpriseSpecific
>>                              specific-trap = 3
>>                                 time-stamp = 1091485
>>                         onlineModSlotIndex = 4
>>
>>    In this last command, expected onlineModType variable is NOT displayed...


	This is a bug in the SNMP AM and a QAR (#69 in MCC013_EXT) has been
	filed against the SNMP AM.

>>    3) is it possible to ckeck what is really returned with MCC_TCPIP_MQ
>>    utility ? 

	Unfortunately, no.

	Rahul.
4316.2maybe an MS file mismatchGOSTE::CALLANDERThu Dec 31 1992 15:213
    rahul, could you post a copy of the MS you used to specify the trap
    in the dictinoary?
    
4316.3OK for QAR... What about MCC 1.3.x last kit ?ZTOIS1::VISTARenato VISTA, SIS Strasbourg, FranceMon Jan 04 1993 03:3414
    
    Hi Rahul,
    
    Thank you for your reply... and a Happy New Year 1993 !
    
    Is the MCC X1.3.5 an available Field Test version ? Do you think that
    the QAR about SNMP will be included in an available Field Test new
    version ? I would need to have a MCC X1.3.* version running SNMP
    correctly for a planned customer demonstration...
    
    Regards,
    Renato
    
    
4316.4X is for development group onlyTOOK::MINTZErik MintzMon Jan 04 1993 07:309
No, X kits are internal development kits only.
The next available kit will be the field test update, T1.3.x

If you have a problem that you feel must be fixed, please enter a QAR
as soon as possible (the deadline is fast approaching), and make
sure the importance of the problem is described in the text.
That will help us prioritize the work in relation to other reported problems.

-- Erik
4316.52582::YAHEY::BOSEMon Jan 04 1993 12:3939
	Happy New Year, Renato.

	QAR #69 in MCC013_INT has been addressed and the fix will be in 
	the field test update kit.

	RE .2
>>    rahul, could you post a copy of the MS you used to specify the trap
>>    in the dictinoary?
    
	Here's the event definition in the MS file :

    EVENT chipFatal = 8 :
      DISPLAY = TRUE,
      SYMBOL = EN49_Event_8,
      TEXT = "A chipFatal trap was received:",
      CATEGORIES = (CONFIGURATION),
      ARGUMENT enterprise = 01 : Latin1String
          DISPLAY = TRUE,
          SYMBOL = SNMP_EV_GEN_ENTERPRISE
      END ARGUMENT enterprise;
      ARGUMENT agent-addr = 02 : IpAddress
          DISPLAY = TRUE,
          SYMBOL = SNMP_EV_GEN_AGENT_ADDR
      END ARGUMENT agent-addr;
      ARGUMENT generic-trap = 03 : GenericTrap_enm
          DISPLAY = TRUE,
          SYMBOL = SNMP_EV_GEN_GENERIC_TRAP
      END ARGUMENT generic-trap;
      ARGUMENT specific-trap = 04 : Integer32
          DISPLAY = TRUE,
          SYMBOL = SNMP_EV_GEN_SPECIFIC_TRAP
      END ARGUMENT specific-trap;
      ARGUMENT time-stamp = 05 : MIBTimeTicks
          DISPLAY = TRUE,
          SYMBOL = SNMP_EV_GEN_TIME_STAMP
      END ARGUMENT time-stamp;
    END EVENT chipFatal;