Conference netcad::hub_mgnt

692.0. "DECagent X2.0 and DEChub 900s?" by ARRODS::GILLJ (John, DTN 847-5849) Fri Feb 04 1994 07:46

Hi,

I have installed the pre-field test version of the DECagent 90 firmware 
(x2_0_0) onto DECagent 90, which are housed in DEChub 900s as shown in the 
diagram below.  

The reason we are using the DECagent 90s is as follows:

My understanding is that the HUB MANAGER functionality of the DEChub 900 
cannot be if the VAX host is connected to the hub via a DECrepeater 90FL 
(as is the case with this configuration).  Therefore it is necesary to use 
the DECagent 90.

V1.1 of the DECagent 90 firmware will not allow management of the DEChub 
900 unless there is a DECbridge present in the hub.

V2.0 removes the above limitation (i.e. it is not necessary to have a 
DECbridge in the DEChub 900 in order for it to be managed using a 
DECagent90.

My DEChub 900 configuration is as follows:

			SLIP
	      +------------------------------------------+
	      |						 |
	      |						OBM
     +--------------+				+----------+
     | D | D | D| A | Hub 5			| D | D |  |  Hub 6
     | R | R | S| G |				| R | R |  |
     | 9 | 9 | 9| T |				| 9 | 9 |  |
     | 0 | 0 | 0| 9 |				| 0 | 0 |  |
     | F | F | T| 0 |				| F | F |  |
     | L | L | L|   |				| L | L |  |
     +--------------+				+----------+
       |                                              |
       |	+-------------------------------------+
       | 	|
       | 	|
       O FOT    O FOT
       | 	|
     +-----------+				+-----------+
     | VAX       |				| VAX       |
     |load host  |				|load host  |
     +-----------+				+-----------+
       |	|  FOT				 |   |
       O FOT    +---O-----------+            FOT O   O FOT
       |                        |                |   |
       |   +-------------------------------------+   |
       |   |                    |                    |
       |   |                    +----------------+   |
       |   |                                     |   |
     +----------------+				+---------------+
     | D | D | D  | A | Hub 1			| D | D | D  | A| Hub 3
     | R | R | R  | G |				| R | R | R  | G|
     | 9 | 9 | 9  | T |				| 9 | 9 | 9  | T|
     | 0 | 0 | 0  | 9 |				| 0 | 0 | 0  | 9|
     | F | F | 0  | 0 |				| F | F | 0  | 0|
     | L | L | TM |   |				| L | L | TM |  |
     +----------------+				+---------------+
       |                                              |
       |                                              |
       |                                              |
       |                                              |
     +--------------+				+--------------+
     | D | D | D | A| Hub 2			| D | D | D | A| Hub 4
     | R | R | R | G|				| R | R | R | G|
     | 9 | 9 | 9 | T|				| 9 | 9 | 9 | T|
     | 0 | 0 | 0 | 9|				| 0 | 0 | 0 | 9|
     | F | F | 0 | 0|				| F | F | 0 | 0|
     | L | L | TM|  |				| L | L | TM|  |
     +--------------+      			+--------------+


I have sucessfully managed to down-line load the new firmware to the 
DECagents in HUBS 1,2,3,4 and 5.

I connect (using a VT220) to the console port on the DECagent and configure 
each DECagent with an IP address.

From the VAX host I can do a UCX ping to the DECagent 90 in hub 5,  I 
cannot "ping" the DECagents in hubs 1,2,3 and 4.  I have configured hubs 1 
through 4 in the same way as hub 5 (different IP addresses obviously).  Is 
there something I have forgotten to do?


When I invoke HUBwatch to manage HUB 5 it shows me a picture of a DEChub 90
rather than a DEChub 900.    Is this the expected behaviour?  

Any help or guidance appreciated,

John


    

    
    John,
    
    	Looking at what you have, you can go without DECagent 90s in all
        DEChub 900s except HUB6, which has no way for the VAX to get to the
        MAM (In Band or Out of Band). All the hubs have DECrepeater 900TMs,
        except for 2. The DECrepeater 900TMs will allow you to get to the
        MAM from your VAX even if your VAX is connected via the DECrepeater
        90FL (provided they share ThinWire LAN). In HUB5 you can get to the 
        MAM Out of Band using the DECserver 90TL and dedicating one of the 
        ports as a SLIP port connected to the MAM. So, you may want to add 
        another DECserver 90TL or DECrepeater 900TM to your configuration 
        (HUB6) and use 900 Style Management.
    
    Bob

    .1 is correct; the important point is:
    
    	The Module acting as IP Server need not be the module that
    	connects the hub to the NMS; it just needs to be itself reachable 
    	by the NMS.
    
    So Bob is correct; if the DR900TM in your hubs is on the Thinwire
    backplane network (which it will be, by default), then it can act as
    the IP server because the DR90FL is always on the Thinwire.
    
    For the hubs that don't contain a max repeater, you can use a port on a
    SLIP terminal server to provide in-band management using the OBM port.
    
    Using a DECagent 90 in a 900 looses a lot of functionality that the 900
    could provide (more of which will be visible in HUBwatch V3).