Conference netcad::hub_mgnt

1882.0. "Bogus show address results" by ODIXIE::FLAHERTY () Fri Jan 13 1995 03:25

    Hi,
    
    	I am experiencing what appears to be a known problem with
    DECbridge/DECHUB 90 configurations where "show address" command can
    provide different hub, slot, port results. Notes 56, 112, and 333 seem
    to very similar in nature, but with no resolution. Note 112.16
    indicates that Engineering is aware and actively working this issue.
    That note is from July 1993. Is there any known resolution to this? My
    firmware configuration is as follows:
    Thank you in advance, rick
    
                                    
    	DECbridge> SHO BRIDGE
    DECbridge 90 V1.14  08-00-2B-31-4E-94 � 1991 Digital Equipment Corp
    FPROM V3.1 �1991,93 Digital Equip Corp 15-JAN-93
    Bridge states:
            Console owner: AA-00-04-00-A9-84        Uptime: 4,439,286.49
    seconds
            Bridge state: 17                        Work group size: 58
            Hub mgmt enable: 1                      Spanning tree enable: 1
            Flash ROM erasures:  2                  Address lifetime: 450*2
    sec.
    Event counters:
            Sys buffer unavail. errors: 1
            WG size exceeded errors: 0
    
    Spanning tree parameters:
            Bridge id:       FF-FF-08-00-2B-31-4E-94        Root port: 1
            Designated_root: 00-0C-08-00-7C-00-4C-CE        Root path cost:20
            Current Forward delay: 15, Hello interval: 1, Listen time: 15
            Def. Forward delay: 15, Hello interval: 1, Listen time: 15
            Topology change flag: 0         Topology change timer: 30
            Bad hello limit: 15             Bad hello reset interval: 5
            Epoch_mode: 1   Epoch1 who: 00-00-00-00-00-00   Mode changes:81
            Epoch 1 poll time: 18 seconds   Epoch 1 response time: 15 seconds
    

 know problem fixed in V3.9 on Decbridge90

  jean-yves

RE; .1, NOT NECESSARILY !!!

There are SEVERAL different symptoms of this problem.

	1).  Port and slot number are correct but HUIIB number is wrong.
		FIXED in V3.9 which is currently in the release cycle.

	2).  Data which USED TO BE correct but is now obsolete continues
	     to be displayed for a LONG time after a configuratin change.
		FIXED in V3.9.

	3).  Real phy addresses showing up at totally random Hub/slot/port
	     locations, ocurring in hubs that contain one or more DR90T's.
		NOT FIXED.  This is NOT a bridge problem.  It is a DR90T
		collision detect logic bug which will be fixed in a future
		DR90T hardware.

The bottom line is that we have fixed all the problems for which the Bridge
is the cause (or at least we think we have).  The problem caused by the 90T
has been identified and a new gate array has been designed but it takes quite a
while to get new silicon into production and out to the Field.

/mj  

               Real phy addresses showing up at totally random Hub/slot/port
	       locations, ocurring in hubs that contain one or more DR90T's.
		NOT FIXED.  This is NOT a bridge problem.  It is a DR90T
		collision detect logic bug which will be fixed in a future
		DR90T hardware.
 

very interesting  mike 

   Do you have any informations about 90T+ it's fixed in this hardware ??

   jean-yves 

Yes, as stated in my previous reply - This is a known hardware bug in the 90T's
collision detect logic.  A new gate array HAS been designed and will be phased 
in.  The problem with this phase-in is that, like the introduction of any new 
piece of silicon, it takes a while.

/mj

 thanks