[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

2916.0. "Multistack managment question" by VAXRIO::ROLF (Vaporware Design Specialist) Fri Oct 27 1995 10:48

    Are we correct in assuming that in a distributed Multistack the
    various pieces of the stack can e.g. connect to various ports of
    a DECswitch900, while the managment bus is sequential, like this pix:
    
    
                           DS900EE
                           |  |  |
             F.O.cable     |  |  |      utp
        ___________________|  |  |___________________
       |                      |                      |
       |                      |utp                   |
       |                      |                      |
    90FS        mgt.bus    90T-16      mgt bus     90T-16
    90T-16 --------------- 90T-16 ---------------- 90T-16 
    90T-16       100ft     90T-16       100ft      90T-16
       |                                             |
       |               mgt bus return                |
        ---------------------------------------------
                          200ft
    
    If this works, only one "Agent" (the 90FS) would suffice for the whole
    stack and would be a nice saving.
    
    Any comments please!?
    
    Regards
    
    Rolf (MCS - DEC Brazil)
    
T.RTitleUserPersonal
Name
DateLines
2916.1NETCAD::BRANAMSteve, Hub Products Engineering, LKG2-2, DTN 226-6043Fri Oct 27 1995 14:2231
As long as you don't exceed the maximum distance on the serial management bus
cables between the stack units, this should work. However, why the "mgt bus
return"? Unless something has changed since I worked on this in the lab or I am
misunderstanding your question (both distinct possibilities!), I believe your
picture should be:

                           DS900EE
                           |  |  |
             F.O.cable     |  |  |      utp
        ___________________|  |  |___________________
       |                      |                      |
       |                      |utp                   |
       |                      |                      |
    90FS        mgt.bus    90T-16      mgt bus     90T-16
     |         _____________| |        _____________| |
     |        |               |       |               |
     |        | 100 ft        |       | 100 ft        |
    90T-16    |            90T-16     |            90T-16 
     |        |               |       |               |
     |        |               |       |               |
     |        |               |       |               |
    90T-16    |            90T-16     |            90T-16
     |________|               |_______|
      
Here the management bus starts at the 90FS, goes down to chain the two 90T-16's
with short serial hops, goes across the 100 ft. run to chain together the middle
group of three 90T-16's, goes across the next 100 ft. run to chain together the
rightmost group of three 90T-16's,  and ends at the lower right unit. The FO and
UTP cable segments are not part of the management bus. There is no need for a
managment bus return path, since it already has a full-duplex path from the 90FS
to the lower right 90T-16. The 90FS manages itself and the eight 90T-16's.
2916.2I may be wrong...VAXRIO::ROLFVaporware Design SpecialistFri Oct 27 1995 15:3310
    Thanks Steve,
    
    fine, but I thought I read somewhere that the managment bus can be
    closed, so that any module can be removed from a live stack without
    interrupting managment. It is quite possible that the "return" isn't
    really required, as long as one doesn't remove a module.
    
    Thanks again and have a nice weekend
    
    Rolf
2916.3NPSS::WADENetwork Systems SupportFri Oct 27 1995 16:055
    
    The ring configuration gives it the "management network resiliency".
    
    Bill
    
2916.4Oops!NETCAD::BRANAMSteve, Hub Products Engineering, LKG2-2, DTN 226-6043Fri Oct 27 1995 16:544
Yes, Rolf, you are correct, you can connect the management bus in a loop to
tolerate a single break anywhere in it (sort of like FDDI ring wrap, only
cheaper!). This was apparently a capability identified fairly late in product
development, so I apologize for confusing things.