[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

487.0. "900 config questions" by VAXRIO::ROLF (Vaporware Design Specialist) Wed Nov 10 1993 13:55

    HUB900 configuration guidlines are very scarce here so far, and I need
    to configure something in a hurry. Two questions:
    
    1. I need two HUB900s side by side because of the number of 10baseT
       ports required. What is the best and cheapest way to interconnect
       two HUB900s?  Can I simply use a 10baseT patch cable and inter-
       connect two DETMM modules (one in each hub)? (Other 10baseT vendors
       seem to be doing it)
    
    2. I'd like to be able to configure up to six LANs in each HUB. Each 
       should be bridged off from the main backbone. How do I do that the 
       easiest and cheapest way?
    
    Sorry if these questions have been answered before, but I have no time
    at the moment to dig into the past. 
    
    Any pointers welcome. Also, pointers for a place where these configuration
    rules can be looked up.
    
    Many thanks
    
    Rolf. DEC Brazil
T.RTitleUserPersonal
Name
DateLines
487.1QUIVER::SLAWRENCEWed Nov 10 1993 15:3122
    1) You _can_ connect two hubs with a repeater-repeater cable, but if
    you are going to create 6 LAN segments in each hub then you've only
    connected the segments that those repeaters are on.  At the risk of
    repeating myself:
    
    	The DEChub 900 _does_not_ provide any interconnect between LANs on
        the backplane.
    
    2) Right now, if you create independant LANs on the backplane you must
    do any interconnect between them outside the hub (we don't yet have a
    bridge or router that can connect to anything on the backplane except
    the DEChub90 Thinwire).  The only benefit (without an external
    bridge/router) of using the flexible Ethernet channels is that they
    don't count as repeater hops. 
    
    As for bridging to the main backbone, what is the backbone?  If you are
    bridging each hub to the backbone anyway, why connect them directly?
    
    Note:  If you use the DECbridge 90 (any flavor) to connect the hubs to
    the backbone, you _MAY_NOT_ connect the two hubs directly to each other
    (doing so would violate the restrictions on DECbridge90 configuration).
    
487.2An example...QUIVER::SLAWRENCEWed Nov 10 1993 15:372
    See also 457.1 for an example configuration with many repeaters and 1
    bridge.
487.3thanks so farVAXRIO::ROLFVaporware Design SpecialistWed Nov 10 1993 16:238
    Thanks -.1
    
    Item 1 OK,
    
    Item 2: I will have to re-think and re-formulate my question.
    
    Thanks so far!
    Rolf
487.4rethinking:VAXRIO::ROLFVaporware Design SpecialistThu Nov 11 1993 06:5517
    Based on -.2/-.3 response, what I'd like to do is have say
    three R900TMs and three B90FLs and somehow make each R900TM a separate
    LAN, each connected via its own B90FL to a backbone to which all
    B90FLs are connected.
    
    I think this is not possible with the B90FL as it can only connect to
    the ONE Thinwire on the backplane. Correct?
    
    The multiport bridge which is somewhere in the future would be able to
    do just that. Correct?
    
    Or is there any other way to do it with presently available components
    other than using a separate HUB900 for each LAN, of course?
    
    Your help is greatly appreciated!
    
    Rolf                                      
487.5The modular solution...QUIVER::SLAWRENCEFri Nov 12 1993 08:3541
    Much as it pains me as a hub person, the only way I can think of to
    accomplish what you describe is to build it from standalone modules,
    not hubs.  Replicate the following as many times as you need:
    
              +-----------+-----+  thinwire
              |DEChub ONE |DECXM|------------T-
              +-----------+-----+            |
              |           |              +----------+
              | Rptr900TM |              |Bridge90FL|
              +-----------+              +----------+
               | | | | | |                    |
                10baseT                     fiber to backbone
               to systems
    
    This isn't nearly as kludgy as it looks in ascii :-)
    
    The DECrepeater900TM mounted in a DEChub ONE rack mounts nicely; the
    back of the DEChub ONE has a notch in it like this:
    
           +-----------------+
           |              AUI=
           |                 +----+
           |                      |
           +----------------------+
           |    (900 module)      |
    
    The notch exactly fits the DECXM (I think I have that name right; I
    mean the replacement for a DESTA that converts AUI to Thinwire).
    
    The thinwire connection to the DECbridge90FL is on the flat upper
    surface (and may be used _only_ when _not_ in a hub).  This way the
    repeater is on the Workgroup side of the bridge.
    
    Note that you'll need a DECagent90 somewhere on the net in order to
    manage the bridges; the DECrepeater900TM has its own agent.
    --------
    
    Yes, a configuration like you wanted to do is exactly what the
    multiport bridge is meant to do... so when it comes out you could
    replace all three 90 bridges and do all this in one 900 hub.