[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

438.0. "DECbrouter 90, DECNIS, & Hubwatch" by CSOA1::TEATER (Fight the Good Fight) Mon Oct 18 1993 18:01

    My customer has the existing network shown below.  They want to add
    the five remote sites off the DECNIS.  They do not have HUBwatch at this
    time but we want to sell it to them.  Is the DECagent module required
    to manage all the cards in the remote hubs?  Do the routers add any
    complexity for the configuration for management, i.e. is a DECagent
    needed at every hub or can one sit in the top hub, see through the
    routers and manage the rest.
    
    
               DEChub 90
               +-----------+
               |DETMR      |-------- VAX system
               |DETMR      |
          +----|DETMR      |
          |    +-----------+
          |
         && TP 
         && mau
    +-----------+
    |  DECNIS   |                                ^
    +-----------+                      Existing  |
      | | | | |    ................................
              |         DEChub 90      New       |
              |        +-----------+             v
              +---//---|DECbrouter |
                       |DSRVE      |
                       |DECMR      |
                       |DETMR      |
                       +-----------+
                              ^
                              |
                       Repeat this DEChub config
                       for a total of 5 remote sites

T.R	Title	User	Personal Name	Date	Lines
438.1	Probably not what you want to hear, but...	ROGER::GAUDET	Because the Earth is 2/3 water	`Tue Oct 19 1993 13:31`	8
	The DECagent 90 will not manage hubs through the DECbrouter 90, nor are there plans to allow it to do so. Given the configuration you described, the only solution I can see is to install a DECagent 90 with V2.0 code in each hub (V2.0, not available till Q3FY94, will do hub management via the backplane) and configure a management station running HUBwatch to manage each hub through the DECagent 90s. ...Roger...
438.2	DB90 and HUBwatch Ok?	CSOA1::TEATER	Fight the Good Fight	`Tue Oct 19 1993 14:08`	3
	Can we still sell HUBwatch and manage the DB90 at least? greg_t
438.3	yes	SLINK::HOOD	I'd rather be surfing	`Tue Oct 19 1993 15:28`	4
	> Can we still sell HUBwatch and manage the DB90 at least? HUBwatch V2.0 will happily manage DECbrouter 90's as stand-alone modules and as modules within a hub.
438.4	Brute manage repeaters?	CGOS01::DMARLOWE	dsk dsk dsk (tsk tsk tsk)	`Wed Oct 20 1993 13:37`	5
	I have customers that could use repeater management as part of the DECbrouter 90. How much interest is there in this and anything being done to looking into adding this functionality? dave
438.5	no repeater management in DECbrouter 90	NAC::FORREST		`Thu Dec 23 1993 15:28`	6
	Dave, we decided not to add repeater management to the DECbrouter, since we would have it in the DECagent 90, and we would have 90 size repeaters (DETMI) soon. The DECagent 90 V2.0 code should get released within a month or so. Unfortunately the DETMI schedule has slipped to June.