Conference azur::mcc

    Hi,
    
    The following is a more detailed description from the customer:
    
    Polycenter Network Manager 200 V1.3 for Ultrix (i.e. DECmcc V1.3)
    
    The customer defines a MIB extension using the following SMI:
    
     bcMonitorDoorTrap      TRAP-TYPE
            ENTERPRISE         bcMonitor
            VARIABLES          { bcMonitorDoorEntryId,
                                 bcMonitorDoorEntryDescription,
                                 bcMonitorDoorEntryStatus }
            DESCRIPTION        
                     "This trap is generated whenever a door sensor
                      leaves the secure state and a trap generation for
                      that sensor is not disabled."
            ::=1
    
    When this trap was received by DECmcc notification FM, the notification
    window did not show up the variable bindings list (i.e.
    bcMonitorDoorEntryId, bcMonitorDoorEntryDescription and
    bcMonitorDoorEntryStatus). The things that the customer got were
    enterprise, agent-addr, generic-trap, specific trap and time-stamp.
    
    The customer claimed that he is sure the agent has sent those variables
    to the Director.
    
    Any ideas?
    
    Regards,
    Charles.

	Are you posting the getevent (or notify request) against the child 
	entity correponding to the mib ?

	MCC> GETEVENT SNMP * mib_entity ANY EVENT

	rb.

    Hi, there,
    
    Thanks for the suggestion. I've asked the customer to cross-check
    whether the GETEVENT has been done. However, their hardware is down for
    these 2 days.
    
    Will post the result later.
    
    Thanks and regards,
    Charles.

I have similar problems with a CHIPCOM and a ODS MIB. I wrote about the CHIPCOM 
MIB in earlier entries. I will do a trace of the trap packets and send it to 
Rahul. He already checked our ODS MIB. So at this time we have different MIBS 
and on all we can't see the "VARIABLES fields".
With the CHIPCOM MIB there is in note 4493 an updated version and an example 
but I do not receive the same as in the example. I tested this with different 
MCC systems (all V1.3) and different agent versions. Exactly the same view, no 
"VARIABLES fields".


Roland

	It works fine for me on VMS. I know that there is a problem on Ultrix
	with enterprise specific traps and it will be fixed in the V1.3 MUP.
	(BTW, are you folks running DECmcc on VMS or Ultrix ?).

	The following is the FCL log using notification.

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

%%%%%%%%%%%%%% Event, 18-MAY-1993 15:21:11 %%%%%%%%%%%%%% [2]
Domain: LOCAL_NS:.discovery                           Severity: Indeterminate
Notification Entity: SNMP LOCAL_NS:.chipcom chipcom
Event Source: SNMP LOCAL_NS:.chipcom chipcom
Event: chipSlotUp
A chipSlotUp trap was received:
                             enterprise = "1.3.6.1.4.1.49"
                             agent-addr = 16.31.112.23
                           generic-trap = enterpriseSpecific
                          specific-trap = 3
                             time-stamp = 71859
                     onlineModSlotIndex = 12
                          onlineModType = module_51nnMFIB

 MCC>

%%%%%%%%%%%%%% Event, 18-MAY-1993 15:21:15 %%%%%%%%%%%%%% [2]
Domain: LOCAL_NS:.discovery                           Severity: Indeterminate
Notification Entity: SNMP LOCAL_NS:.chipcom chipcom
Event Source: SNMP LOCAL_NS:.chipcom chipcom
Event: chipPortDown
A chipPortDown trap was received:
                             enterprise = "1.3.6.1.4.1.49"
                             agent-addr = 16.31.112.23
                           generic-trap = enterpriseSpecific
                          specific-trap = 11
                             time-stamp = 72668
                   onlinePortAdminState = enable
                       onlinePortStatus = remoteLinkFailure

MCC>

%%%%%%%%%%%%%% Event, 18-MAY-1993 15:21:20 %%%%%%%%%%%%%% [2]
Domain: LOCAL_NS:.discovery                           Severity: Indeterminate
Notification Entity: SNMP LOCAL_NS:.chipcom chipcom
Event Source: SNMP LOCAL_NS:.chipcom chipcom
Event: chipPortUp
A chipPortUp trap was received:
                             enterprise = "1.3.6.1.4.1.49"
                             agent-addr = 16.31.112.23
                           generic-trap = enterpriseSpecific
                          specific-trap = 12
                             time-stamp = 72668
                   onlinePortAdminState = enable
                       onlinePortStatus = okay

MCC>

    Hi, there,
    
    We tested again (after fixing the hardware) and found that we got the
    variable binding list for the very first time.
    
    Afterwards, it is no longer there even after we have re-booted the
    director machine.
    
    Where can I find the mandatory update?
    
    Thanks and regards,
    Charles.

	The MUP kit is not released yet. If you desperately need a copy of	
	executable that works, send me mail and I will give you a pointer
	to it. (The executable built for V1.3 SSB does not work for no
	apparent reason. Rebuilding the executable from the same build 
	directory, with the same sources, seemed to have solved the problem).

	Rahul.