Conference azur::mcc

5093.0. "Problem with VARIABLES list for traps in the MTU" by ANTIK::WESTERBERG (Stefan Westerberg DS Stockholm) Thu May 20 1993 09:00

	Hi, I trying to add the enterprise specific trap definition for
	the DECconcentrator 500. But I can't get MTU to accept a reference
	to a definition in the FDDI mib. Is there a way of doing this ?

Beginning Phase 1 for file WRK:[MCC.MIBDEF]DEC_EXT_MIB.TXT;

  20-MAY-1993 13:43:58
Now starting to run the MIB Translator ...
This may take approximately 1-5 minutes.
Issuing following command:
  $ MTU WRK:[MCC.MIBDEF]DEC_EXT_MIB.TXT; -p
Variable snmpFddiPORTConnectState in trap defn. defcnPortTrap not previously def
ined
An error occurred while running the MIB Translator.
Check file DEC_EXT_MIB.LIS,
  if it exists, for any further information.
Files DEC_EXT_MIB.MS and DEC_EXT_MIB_ENUM.MS
  may also have been created; delete these files, as appropriate.

  20-MAY-1993 13:44:19

Procedure terminated in error.


defcnPortTrap     TRAP-TYPE
    ENTERPRISE  defcn -- 1.3.6.1.4.1.36.2.15.5.1
    VARIABLES   { snmpFddiPORTConnectState }
    DESCRIPTION
        "The DECconcentrator 500 (DEFCN) sends this trap
        when the value of the snmpFddiPORTConnectState changes.
        The port trap can take one of the following values:

                disabled (1)
                connecting (2)
                standby (3)
                active (4)
   
         When you connect to a port on the DECconcentrator 500
         unit, the snmpFddiPortConnectState transitions to the
         (4) state. When the port connection is removed, the
         snmpFddiPortConnectState transitions to the connecting
         (2) state.
	 
	 This variable is included in the var-bind-list of the trap.
         The snmpFddiPortConnectState is instanced by the SMT
         index and the port number. For example, snmpFddiPortConnect
         State.1.4 with a value of 2 indicates that SMT 1's port
         4 has moved to the connecting (2) state.         

	 To enable or disable the snmpFddiPortConnectState port
         trap, use the esysFDDIPort. The TrapSwitch object is in the
         DEC private elan extension MIB. The esysFDDIPortTrapS
         has two values, true (1) or false (2). When the switch
         is true (1) enabled, the port traps work as described
         above. When the switch is set to false (2) disabled, no
         port traps occur because of a change in the SMT state
         The default value of the switch is false."
    :: = 1

	MTU, in its current form, does not allow import of mib objects from
	other mibs, except mib II. A cludge may be to append you extension
	to the FDDI mib, and then run it through MTU. If you mail me the
	DEC_EXT_MIB.TXT, I might be able to help you out.

	Rahul.