[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference netcad::hub_mgnt

Title:	DEChub/HUBwatch/PROBEwatch CONFERENCE
Notice:	Firmware -2, Doc -3, Power -4, HW kits -5, firm load -6&7
Moderator:	NETCAD::COLELLADT

Created:	Wed Nov 13 1991
Last Modified:	Fri Jun 06 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	4455
Total number of notes:	16761

3551.0. "confused trap on 900MX concentrator" by COMICS::BILLINGJ () Thu May 23 1996 12:15

    Hello,
    
    Can anyone tell me if there is a bug in the DEC 900 MX concentrators
    traps ?
    
    I have been talking to a customer who recieves the following trap 
    from his 900 MX concentrator using Polycenter netview. 
    
    mgmt.mib-2.transmission.fddi.73.5.2.1.20.1.5 (Integer) : 2
    
    I've managed to break this down almost to completion using the rfc1512,
    but cannot deceipher the 1.5 on the end.
    
    mgmt.mib-2.transmission.fddi.fddimib.fddimibPORT.fddimibPORTTable.
                                   73         5              2
    
    fddimibPORTEntry.fddimibPORTConnectState
            1                 20
    
    I believe the next bit (ie the integer value part) to mean Break 
    
    
    This just leaves the 1.5 on the end.
    
    Is this a bug or do they stand for something ?
    Has this been amended in a particular version of the firmware ?
    
    Thanks
    
    Jan Billing

T.R Title User Personal
Name Date Lines

3551.1 NETCAD::GALLAGHER Thu May 23 1996 13:25 41

T.R	Title	User	Personal Name	Date	Lines
3551.1		NETCAD::GALLAGHER		`Thu May 23 1996 13:25`	41
	This is indeed fddimibPORTConnectState. The .1 and .5 comprise the instance. > fddimibPORTEntry OBJECT-TYPE > SYNTAX FddimibPORTEntry > ACCESS not-accessible > STATUS mandatory > DESCRIPTION > "A PORT entry containing information common to a > given PORT." > INDEX { fddimibPORTSMTIndex, fddimibPORTIndex } > ::= { fddimibPORTTable 1 } Entries in the fddimibPORTTable are indexed by fddimibPORTSMTIndex and fddimibPORTIndex. fddimibPORTSMTIndex is the 1. fddimibPORTIndex is the 5. This indicates the port 5 underwent a connect state change. The value associated with this object indicates exactly what the state change went to. > fddimibPORTConnectState OBJECT-TYPE > SYNTAX INTEGER { > disabled(1), > connecting(2), > standby(3), > active(4) > ----- etc ---- > Can anyone tell me if there is a bug in the DEC 900 MX concentrators > traps ? The trap is called a port trap. This is not a bug - it's a feature - really. If you don't think it's a feature, turn it off using the object in the elan MIB. (Let me know if you want to do this and I'll look it up.) -Shawn

This is indeed fddimibPORTConnectState.  The .1 and .5 comprise the instance.

>          fddimibPORTEntry OBJECT-TYPE
>              SYNTAX  FddimibPORTEntry
>              ACCESS  not-accessible
>              STATUS  mandatory
>              DESCRIPTION
>                      "A PORT entry containing information common to a
>                      given PORT."
>              INDEX   { fddimibPORTSMTIndex, fddimibPORTIndex }
>              ::= { fddimibPORTTable 1 }

Entries in the fddimibPORTTable are indexed by fddimibPORTSMTIndex
and fddimibPORTIndex.

fddimibPORTSMTIndex is the 1.  fddimibPORTIndex is the 5.

This indicates the port 5 underwent a connect state change.  The value
associated with this object indicates exactly what the state change went
to.

>          fddimibPORTConnectState OBJECT-TYPE
>              SYNTAX  INTEGER {
>                          disabled(1),
>                          connecting(2),
>                          standby(3),
>                          active(4)
>    ----- etc ----


>    Can anyone tell me if there is a bug in the DEC 900 MX concentrators
>    traps ?

The trap is called a port trap. This is not a bug - it's a feature - really.

If you don't think it's a feature, turn it off using the object in the
elan MIB.  (Let me know if you want to do this and I'll look it up.)


						-Shawn