Conference netcad::hub_mgnt

    re: .0
    Same problem at another site.
    Is there any fix to this available? (or is it possible to make it
    work?)
    
    I will open a CLD on this...
    thanks,
    Mike

From: LOMICKAJ
To:   ZUR01::SCHNEIDERR,MEMIT::SEAVER
Subj: DECbridge 90FL response
Is it possible that one of the ports of the DECbridge 90FL was left
unterminated or disconnected?

In any DECbridge 90, communication with network management will be
unreliable if one of the ports is disconnected.  Every five seconds,
the bridge disconnects both ports in order to perform a self test on
the broken port, in hopes that the port will pass.  For the duration of
the test (about half a second) the bridge is unreachable.  (It is not
possible in the hardware to self test one port while the other is on
line.)  If MCC's retry interval is also a multiple of 5 seconds, you
would have a problem communicating at all.

	Is the DECbridge 90 managable directly from DECmcc or DECelms?

	When I read the the 256.0 note, it suggested that this was possible
and that the DECagent 90 was not involved.

	We have a large customer that is looking at installing the 90FL bridge
into their fibre network, and the unit will be standalone. They currently use 
DECmcc to manage many LANbridge 200s in their large LAN and would like to 
manage the remote bridge using the same method.

	-Larry
	 NIS London, Ontario

The DECbridge 90 is managable from DECmcc to a certain extent. DECmcc's
Bridge Access Module uses RBMS to talk to the Bridge but doesn't know 
all details about the 90's. Also the repeaters in a hub would not be 
seen, but this won't affect you since you're running standalone.

I don't know exactly off hand, but I would expect problems in the area 
of Forwarding Database and filtering. There is discussion about it in 
NOTED::MCC.

*Robert

Hi,

What happend with the problems in .0 and .1 , any solution ?
I have the same problem with both Fiber and AUI bridges.   

VERSIONS are:

DEWGF V2.1 08-00-2B-36-61-D1 �1991,92 Digital Equip Corp
FPROM V3.1 �1991,93 Digital Equip Corp 15-JAN-93				


/Niklas

    Hi, 
    
    >>What happend with the problems in .0 and .1 , any solution ?
    
    No it's still the same. I connected both ports same error message.
    MCC> reg bridge .telco.v.my_bridge address 08-00-2B-31-D5-E5
    
    Bridge PTTCH:.telco.v.my_bridge
    AT 13-OCT-1993 17:11:47
    
    Partial registration success. Please retry later to complete the
    registration.
            Reason for Partial Registration = Communication with the target
                                              has been interrupted
    
    The registrations command wants to read the Bridges Characteristic's
    and there, my guess, the registration fails because one can do
    
    MCC> sho bridge .telco.v.my_bridge
    Using default ALL IDENTIFIERS
    
    Bridge PTTCH:.telco.v.my_bridge
    AT 13-OCT-1993 17:16:26 Identifiers
    
    Examination of attributes shows:
                                       Name = PTTCH:.telco.v.my_bridge
                                    Address = { 08-00-2B-31-D5-E5,
                                                08-00-2B-71-D5-E5 }
    or
    
    MCC> sho bridge .telco.v.my_bridge all status
    
    Bridge PTTCH:.telco.v.my_bridge
    AT 13-OCT-1993 17:17:16 Status
    
    Examination of attributes shows:
                            Bridge Function = Bridge
                      Management Heard Port = 1
                               Device State = Operating
                         Best Root Priority = 128
                                  Best Root = 08-00-2B-03-F6-4C
                              Best Root Age = 256 Seconds
                                    My Cost = 10
                                  Root Port = 1
                 Time Since Last Hello Sent = 0 Seconds
                       Topology Change Flag = False
          Topology Change Notification Flag = False
                      Topology Change Timer = 30 Seconds
                      Actual Hello Interval = 256 Seconds
                       Actual Forward Delay = 3840 Seconds
                         Spanning Tree Mode = LAN Bridge 100 Mode
                 LANBridge 100 Being Polled = 00-00-00-00-00-00
                          NVRAM Failed Flag = False
    
    MCC> sho bridge .telco.v.my_bridge all ref
    
    Bridge PTTCH:.telco.v.my_bridge
    AT 13-OCT-1993 17:17:37 References
    
    Examination of attributes shows:
                                   Location = -- Attribute Not Available
                        Implementation Desc = -- Attribute Not Available
                         Responsible Person = -- Attribute Not Available
                               Phone Number = -- Attribute Not Available
                               MAIL Account = -- Attribute Not Available
                                    Remarks = -- Attribute Not Available
                                  Text File = -- Attribute Not Available
    but it fails with
    MCC> sho bridge .telco.v.my_bridge all char
    
    Bridge PTTCH:.telco.v.my_bridge
    AT 13-OCT-1993 17:19:10 Characteristics
    
    Communication with the target has been interrupted
    
    Hope it helps and may someone has a solution
    
    Regards Fred

    Are there any news (solutions) for this problem?
    
    I have a customer with the same problem.
    
    
    Regards
    
       Birgit Ferstl / Digital Service Center Munich

    re  -.1
    
    What HW version of the bridge did you use ?
    If it's the old one please try 2.1
    
    /Niklas

    This same problem is discussed in 1598.*
    
    At the moment it looks like it only happens with the V2.1 ROM bridges
    and the V1.14 ROM bridges are ok.