[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

1934.0. "Decserver 90l+ problem" by KERNEL::ARKLEYS () Thu Jan 26 1995 07:27

    Hello out there. Tiz time for another Decserver90l+ management
    problem......
    
    I have a customer who has a dechub900 firmware 3.1.0. he is using
    Hubwatch 3.1 for windows. cust has the following hub configuration.
    
    Slot 1 : Decrepeater 90FS 1.06 which is supposed to be the same as 1.1
    Slot 2 : Same as slot 1.
    Slot 3 : EMPTY
    Slot 4 : Decagent90 running 2.1.3
    Slot 5 : Decserver 90l+ v2.0 BL5.2
    Slot 6 : Decserver 90l+ v2.0 BL5.2
    Slot 7 : EMPTY
    Slot 8 : EMPTY
    
    Cust is using slot 1 for hubmanagement.
    
    Cust has three agents added into the management table
    1) for the hub 900, with it's IP address.
    2) For the decagent90, with it's correct IP address.
    3) For the Decserver90l+ with the IP address of the Agent.
    
    When cust selects on the agent in the management table the decserver
    90l+ becomes visable and useable, but when the customer switches back
    to the hub900 management view, he can still see the 90l+ but as soon as
    he tries to select it he gets NO RESPONCE FROM AGENT.
    
    I have gone through this with cust and I have managed to get it to
    work, all be it having to factory reset the agent and the hub now and
    again. But cust will just not work.
    
    The only diffence that I can see between mine and the customers setup
    is that the cust is using a 90FS to provide the IP services, where as I
    am using a 900TM repeater. The customer is also using a decserver90l+
    which is running firmware 5.2, and mine is running 4.9.
    
    Any ideas, of what the problem could be would be a great help
    
    Cheers Steve.

T.R	Title	User	Personal Name	Date	Lines
1934.1	Check your customer's HUBwatch agents file	ROGER::GAUDET	Because the Earth is 2/3 water	`Thu Jan 26 1995 09:56`	22
	Steve... Which device you use to provide IP services to the DEChub 900 Hub Manager is irrelevant. It has no bearing on the management of the DECserver 90L+. The problem sounds like your customer is missing one critical entry in their HUBwatch agents file (Community -> Manage Table window), the one that has the MAC address of the DECserver 90L+ and the IP address of the DECagent 90. This is required in order to manage the DECserver 90L+ from the DEChub 900 view (that is, when you are managing the hub using the IP address of the DEChub 900 Hub Manager). DECserver BL4.9 does not support auto-discovery. This device must be manually added to a hub/community. Your customer's BL5.2 DECserver does support auto-discovery. This is why it appears in the DEChub 900 view. However, this device still needs to be manually added to a DECagent community because when the DECagent is in the DEChub 900 and the Hub Manager has been given an IP address, the DECagent cannot be the hub master and therefore will not auto-discover the DECserver. Confused yet? :-) ...Roger...
1934.2	I've already added one of those.	KERNEL::ARKLEYS		`Thu Jan 26 1995 10:44`	16
	Ok for starters, thanks for the reply. But The customer has already added an entry for the decserver in the managed table, The cust has one for the hub, one for the agent, and one for the decserver, with a type of decserver, a community of public, and the IP address of the decagent, and the Mac address of the server. So his setup should work, I can't figure it out, it's not as if it only works now and again, it's as soon as he switches back to the hub in the managed table, that you get the AGENT DOES NOT RESPOND message, I have had this problem a few times, but a factory reset of the agent cleared this, but not on the customers. Any more ideas. Thanks for any help.. STEVE.
1934.3	Deja vu malheureusement /Already seen badly...	PADNOM::PEYRACHE	Jean-Yves Peyrache Country Support Group France	`Thu Jan 26 1995 14:02`	13
	In agent file have you 2 entries with : _ correct IP address correct MAC address for DS90L+ _ correct IP address + correct MAC address for DA90 have you tried after selecting the community of Decagent90 add/delete DS90L+ again ?? jean-yves
1934.4	Tried that one too :)	KERNEL::ARKLEYS		`Fri Jan 27 1995 04:23`	16
	Yep sure have, I have gone through this with the customer serveral times. If the customer selects on the DA90, then you can manage the DS90L+ it's only when you select, back on the management table of the hub900 that you get the agent does not respond message. At one point it seemed as if we were going round in circles, and every time we tried to manage the 90L+ from the hub900 view, the AGENT DOES NOT RESPOND message appears, and yet I can get it to work fine every time on our system. As I've mentioned the only difference I can see is that the cust is using BL5.2 on his DS90L+ and I am using BL4.9... Cheers Steve.
1934.5		NPSS::JOHNSON	Mike J., Network Products Support	`Fri Jan 27 1995 08:42`	17
	Steve, This is a shot in the dark, and something that should NOT affect a HUB900, but There is a bug in the DS90L+ V5.2 firmware which can, in a HUB90 configuration, cause the bus master (either a DA90 or a DB90) to "relinquish" mastership to the server. Afterwards, the modules in the HUB90 cease to be managable, mainly because no one is trying to manage them. This has been fixed, beginning with V5.4 of the DSRVG ROM. I do NOT see how this could affect a 900 configuration, but then, stranger things have been known to happen. In parallel to any other actions you are taking, I'd suggest that you consider upgrading your 90L+'s to V5.4. There is a kit for this that you can order under part number DSRVG-RK. It costs ONE DOLLAR. /mj
1934.6	I'll give that a go....	KERNEL::ARKLEYS		`Fri Jan 27 1995 09:10`	8
	Cheers Mike, After reading some of the other articles, about the decserver 90l+ in this notes entry, I was thinking about getting the customer to upgrade to version 5.4... Right I'll give this a try, and let you know what happens... Cheers Steve.
1934.7	It's not a problem with 5.4 on ds90l+	KERNEL::ARKLEYS		`Tue Jan 31 1995 10:44`	7
	Well I have got the customer upgraded to version 5.4 rom for the decserver 90l+ and this has still not fixed the problem, this is realy strange, I can't think of anything else to try... Any more ideads out there ... Please. Cheers Steve.
1934.8	DECagent does not poll when it is not the hub master	ROGER::GAUDET	Because the Earth is 2/3 water	`Thu Feb 02 1995 12:50`	24
	Steve, This is a problem with having a DECagent 90 in a DEChub 900 and wanting the DECagent to manage some of the devices in that hub. Since the DEChub 900 has been given an IP address, the DECagent will not be the hub master and therefore will not poll any of the devices in that hub. This includes the DECservers in your case. The solution is to take the DECagent out of the DEChub 900 and put it either in another hub or standalone. Now, why did it "seem to work" for you? I have two guesses: 1) When you manually add a DECserver to the DECagent's community, it is immediately available as a manageable device. However, since the agent is not the hub master, the DECserver becomes unreachable at the agent's next polling interval. 2) When you factory reset the DEChub 900, it no longer has an IP address. This does not affect the DECagent, however. During the time it takes to give the hub an IP address, the DECagent is the hub master and will show the DECserver when it is selected from HUBwatch. ...Roger...
1934.9	IS IT 5.2 & 5.4 that don't work ???	KERNEL::ARKLEYS		`Mon Feb 06 1995 10:00`	14
	Well the plot thickens.... I upgraded my 90L+ to match the customers setup, and strangely enough, my setup stopped working, with Agent does not respond. I have played with this for ages, and could not hubwatch to work with a ds90L+ running 5.4. As soon as I put the 4.9 90l+ back in the hub, it all worked away merrily, again. I am currently speaking with some one in engineering, but if some one manages to get this setup to work please let me know.. Cheers Steve.