[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

4351.0. " SNMP Traps /Enterprise specific info" by BAHTAT::TAYLOR () Thu Jan 07 1993 10:56

   I have been doing some work with a customer who has some specific needs for
managing Chipcom ON-Line Hubs. We have set up a system with Ultrix 4.3 DECmcc
BMS T1.3 to let him see how things are developing around the management of
Vendor products, but he still has some reservations about the product.

   I loaded up the Chipcom_hub3_brg_10bt_mibdef.txt (mibspec 1.39 2/27/92) and
set everything going.

   When I issued Getevent SNMP * Chipcom Any Event I got an error message when
a trap occured :-

  Received Event had more object ids than were defined in the dictionary

    Event: chipPortDown
  A chipPortDown trap was received

         "Valid trap information here"
               "
               "
         onlinePortAdminState =
%MCC-E-NOENTITY, No corresponding entity existence exists
-------------------"-------------------"-----------------


Anyone any idea why this occurs, is it something I have done or missed ?


Also when I enabled notification in the same way as the getevent ie

     Entity SNMP * Chipcom
     Event Any Event

when a trap occured, Getevent flagged it but nothing happened in notification.
     
   If I simply use Entity SNMP *
                   Event Any Event

then all the traps come through to notification as I would expect.
  Any ideas why ?
            
      Richard.

T.R	Title	User	Personal Name	Date	Lines
4351.1	MIB doesn't look like it matches implementation	GOSTE::CALLANDER		`Thu Jan 07 1993 11:57`	4
	the no correspondig entity message means that someone return unexpected data. In your case it looks like the event you received had more information in it than the MIB did.
4351.2	check with DECmcc dictionnary	ANNECY::HAGENMULLER	EIC Annecy - dtn 7887.41.99	`Thu Jan 07 1993 13:14`	20
	try to see if all the relevant fields in the trap are defined in the decmcc dictionnary by issuing the following commands : $manage/tool/dict >show class snmp >show subclass chipcom >show event the_trap_you_want_to_check and compare the upshot to the MIB definition. Anyhow, there is currently a limitation within DECmcc SNMP AM which prevents you from getting displayed more than the first VarBind in the trap. I got once a similar error which was due to a bad ip address (second field) transmitted in the trap (SNMP AM couldn't recognize the right entity). Yet, your problem seems to be a little bit different. Ch.
4351.3	Check the version of EMM ?	MQOSWS::F_MONETTE	Montreal Sales Support	`Thu Jan 07 1993 16:09`	13
	If you have a new ONline , you should have EMM V3.0. The MIB you installed I think is for EMM V2.1. I know that Chipcom has a new private MIB for EMM V3.0. You can have it using the Chipcom Hot-line. they will send you the MIB BY Internet if you want. I Hope this help regards francois
4351.4		MOLAR::YAHEY::BOSE		`Thu Jan 07 1993 19:13`	13
	>> " >> onlinePortAdminState = >>%MCC-E-NOENTITY, No corresponding entity existence exists >>-------------------"-------------------"----------------- onlinePortAdminState has an enumerated datatype. You are seeing the above error message because the chipcom agent is returning a value which is outside of the enumeration. I have seen similar behaviour from the chipcom agent we have here in our lab. Rahul.
4351.5	What about Notification ?	BAHTAT::TAYLOR		`Fri Jan 15 1993 04:42`	11
	Thanks for all the replies/suggestions. The concentrators are EMM V3, so since I am working with Chipcom on the FT ONdemand software for Ultrix I managed to get a new MIB as well. That should take care of the first problem. Has anyone any suggestions regarding the second (notification) problem ? regards, Richard.
4351.6	related problem	GOSTE::CALLANDER		`Tue Jan 19 1993 10:39`	3
	notification simply calls the getevent, the problems and resolution should simply be one in the same.