[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

302.0. "DECagent & Multiple hubs with DECservers only ?" by SMAC10::BARKER_E (Ummm...) Tue Jul 13 1993 16:09

    Hi,
    
    	I just want to check some functionality issues regarding terminal
    servers in DEChub 90's :-
    
    	Customer is planning on locating a number of hubs with DECserver
    90TL's and DECrepeater 90 T's and 90FA's. They would like management of
    the DECserver 90TL's via Hubwatch but aren't bothered about management
    of the repeaters at this stage. If we supply one DECagent 90 in one of
    the three hubs planned, will they be able to get graphical hubwatch
    displays of the DECserver 90TL's in the other hubs via the single
    DECagent 90 ?  Presumably the repeater slots will show blank. 
    
    	I've got the feeling from other notes and other configs I've done
    that the answer's no and they need a bridge in each hub but want to
    check !
    
    	Thanks,	Euan

T.R	Title	User	Personal Name	Date	Lines
302.1	Should work without a BRIDGE, or A DECagent90.	MSDOA::REED	John Reed @CBO - DTN: 367-6463 = DNIS	`Tue Jul 13 1993 16:53`	17
	I have been playing with DECserver 90TL's and HUBwatch this week. I beleive that the HUBwatch software will directly manage the 90TL terminal servers, without an external DECagent 90 module. The DECagent 90 effectively is just a converter from DECbridge90 to SNMP. Since you don't need to manage repeaters, or DECserver 90L, or L+, then you don't need to worry about a bridge. The DECserver90TL includes it's own SNMP agent software, so you can manage it using the HUBwatch graphics. You will just get a single module side-ways view, by default. I don't know if you can represent other DECserver90TL's in a hub without the DECagent, since I have a DECagent installed, and I haven't tried managing the 90TL without the DECagent online. Just be sure to define the 90TL in the HUBWATCH$LIBRARY: data file, and go for it. JR
302.2	Manage them standalone	LEVERS::SWEET		`Tue Jul 20 1993 01:22`	4
	The previous reply is correct, you don't need a DECagent 90 to manage the 90TL standalone. You only the agent if you want the hub view. Bruce
302.3	Got the kit, gota few problems !	SMAC10::BARKER_E	Ummm...	`Wed Aug 18 1993 04:06`	20
	As a follow-on, we twisted the customers arm and they stumped up for a brudge in each hub and 1 DEcagent to manage the three hubs. The hub with the DECagent in also has a DECbridge 90FL and two DEcserver 90TL's and works fine. The other hub in use has a DECbridge 90 in Slot 8, DEcrepeater 90T's in slots 7/6 and DEcserver 90TL in slots 4 & 5. Repeaters show up fine. When I choose add module options and add one of the terminal servers that works ok, but when I add the second 90TL the first one disappears. I can round-robin on this for hours and it's dead frustrating ! Can anyone provide any pointers as to what the problem could be please ? I've checked the agent setups in the community tables and they all seem OK, correct MAC addresses etc. Thanks for any help, Euan PS Config is Hubwatch for VMS 1.1 UCX DECmcc 1.3 DECagent 1.1 software
302.4	Old 90TLs need polling disabled	ROGER::GAUDET	Because the Earth is 2/3 water	`Wed Aug 18 1993 10:09`	7
	If the 90TLs are of the 1-Meg variety or you are loading the old load image into a 4-Meg device, you must add the 90TL with slot polling disabled. When the HUBwatch Add Module screen comes up, enter everything as you have been and then click on the green box next to "Enable Status Polling." This will disable slot polling for the device. ...Roger...