[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

478.0. "Configuration queries?" by ARRODS::GILLJ (John, DTN 847-5849) Tue Nov 09 1993 09:21

    I am currently planning the implementation of the following and would
    be grateful on some comments on my understanding.
    
    
    	DECHUB 900				DECHUB 90  (A)
      +------------+		FIBRE		+---------+  AUI
      |   DB90FL   |----------------------------| DR90FA  |-------
      |            |                            |---------|
      |            |                            | AGENT90 |
      |------------|                            +---------+
      |            |
      |            |		FIBRE		DECHUB 90  (B)
      |   DB90FL   |----------------------------+-----------+
      |------------|				| DB90FL    |
      |            |                            |-----------|
      |            |				| 3 * DR90T |
      |		   |				+-----------+
      |   DB90FL   |
      |		   |		FIBRE		DECHUB 90  (C)
      +------------+----------------------------+------------+
    						| DB90FL     |
    						|------------|
    						| 2 * DR90T  |
    						+------------+
    
    My understanding is that all modules in all hubs are manageable via
    HUBwatch (as the DB90FL supports management of the Hubs and Repeaters),
    and I only require an Agent in DEChub 90 (A).
    Am I right?
    
    I understand that the DR90FA can repeat on AUI, FOIRL and ThinWire so
    the configuration of the DR90FA in DEChub 90 (A) is valid.  (I.e. it
    can repeat on Fibre, AUI and onto the backplane.  Is this correct?
    
    Any help appreciated?
    
    John
    
    John
    
    
    Is the configuration
T.RTitleUserPersonal
Name
DateLines
478.1QUIVER::SLAWRENCETue Nov 09 1993 14:4921
    I don't know about repeating on all three interfaces of the DR90FA...
    I'll leave that one to someone else.
    
    To manage DECHUB 90 (A) with a DECagent but no DECbridge you'll need
    V2.* of the DECagent firmware (not yet available).
    
    You don't show any other modules in the DEChub900; if you don't have a
    DECrepeater900TM (or some other not-yet-available) module in the 900
    then it can't be managed in-band in this configuration _as_a_900_.  All
    that means is that you should _not_ configure any IP address on it's
    setup console; in that case it will revert to DEChub90 compatibility
    mode and one of the DECbridges in the hub will be allowed to take over
    as 'bus master' and provide management info to your DECagent as in a
    90.
    
    If you have a DECrepeater900TM in there, you should manage through it;
    another alternative is if you have a DECserver (any of 900TM, 90TL, or
    90M) you can connect a serial line from the DECserver to the OBM port
    of the DEChub900.  Note that this is _NOT_ out-of-band management in
    this configuration, but it does give you access to the 900 mode.
    
478.2Replace backbone bridges with repeatersQUIVER::SLAWRENCETue Nov 09 1993 16:2613
    Another point:
    
    In the configuration you diagram, the DB90FLs in the DEChub900 are
    being used as backbone bridges rather than workgroup bridges; that is,
    thier backplane port is toward the network backbone.  It will be easy
    to exceed the 199 address limit on that backplane port (since all
    addresses on the combined network will appear there).
    
    Since there is no additional benefit to having a bridge at both ends of
    a link, you should replace the bridges in the DEChub900 with
    DECrepeater90FLs (in which case you might want to put a bridge in
    DEChub 90(A) so that its traffic is not also the backbone).
    
478.3exARRODS::GILLJJohn, DTN 847-5849Wed Nov 10 1993 10:496
    Thanks for the replies,
    
    Are there any details on when v2.* For the DECagent will be available?
    
    John
    
478.4DECagent 90 V2.0 - making good progressNAC::FORRESTThu Dec 23 1993 20:292
	Look for it in February 1994, if not sooner.