[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

3523.0. "Problem with DETMI in remote HUB90" by STU03::RUEGGEN () Fri May 10 1996 09:31

    
            Hello,
    
    
            customer has a central DEChub90 with a DECagent 90 V.31 and
            several remote DEChub90 with DEcbridge90 V3.9 acting as proxy.
    
            Recently he added the DECrepeater90TS V2.0 and the DECrepeater90-T16
            into one of the remote hub's.
            Both modules were shown as unknown by HUBwatch V4.1. When he
    	    added them manually he got "no agent defined for slot".
    
            He then moved both new modules into the central hub. There he
            could manage the DECrepeater90-T16 but not the DECrepeater90TS.
    
            What can be done to make both modules managable in the remote
            hub's ?
    
            
            Ulrich Rueggen

T.R Title User Personal
Name Date Lines

3523.1 You can not do it BARNA::DSMAIL Fri May 10 1996 11:17 8

T.R	Title	User	Personal Name	Date	Lines
3523.1	You can not do it	BARNA::DSMAIL		`Fri May 10 1996 11:17`	8
	90T16 can not be managed by a DECbridge.(Memory reasons) You can make 90TS hub master and add it as a new agent and then this will manage 90T16 that were in the same hub, but not the bridge. There are previous notes explaining this in detail. Jordi Manchon

    
    
    90T16 can not be managed by a DECbridge.(Memory reasons)
    You can make 90TS hub master and add it as a new agent and then
    this will manage 90T16 that were in the same hub, but not the bridge.
    There are previous notes explaining this in detail.
    
    Jordi Manchon