[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

2609.0. "Hubwatch for VMS : Maximum # of agents" by IAMOSI::LEUNG (Dennis Leung, Sydney CSC) Fri Aug 04 1995 01:31

    HubWatch for VMS V3.1.3
    VMS V6.1
    
    Is there a limit to the number of agents that can be defined in
    Hubwatch?
    
    Customer is encountering the following problem :
    He cannot see more than 256 agents in the "Manage Table" window even
    though he has defined 258 agents and they are all in the agent file,
    hubwatch_agent.dat.
    For example, if he adds a new agent, say at the top, then the last one
    in the list will disappear from the list.
    Customer has checked the documentation and said that there is no
    mention of a limit on the number of agents that can be defined in
    hubwatch.
    
    Thanks for all replies
    Dennis
    CSC Sydney

T.R	Title	User	Personal Name	Date	Lines
2609.1		SLINK::HOOD	Maine state bird: The black fly	`Fri Aug 04 1995 17:37`	13
	256 sounds like a magic programming number to me... I looked briefly thru the code and couldn't find a max allocation size. If your customer's table stopped adding entries at 213, it'd be a coincidental kind fo number. "256" sounds like software-ese for "let's assume it can be a fairly large number of entries". There's not supposed to be a limit... A clumsy workaround would be to have two agent files... Or to remove some of the agents. There are very few modules that need to be in that file. Tom Hood
2609.2		IAMOSI::LEUNG	Dennis Leung, Sydney CSC	`Tue Aug 08 1995 02:37`	12
	Tom, Thanks for your reply and the suggested workaround. However, customer is running Hubwatch from DECMCC and given that his system is already overloaded, he is not willing to have 2 Hubwatch sessions running at the same time. Should we wait for Hubwatch V4.0 (or V4.1) for VMS (do you have an estimate of the scheduled release date? are we talking weeks or months?) or should I IPMT the problem. Dennis
2609.3		SLINK::HOOD	Maine state bird: The black fly	`Fri Aug 11 1995 14:12`	9
	It is unchanged in V4.1. IPMT it. Why does your customer have such a large agents file? You do not need an entry for every hub. You do not need an entry for most modules. Tom
2609.4	How does it work?	SNOFS1::KHOOJEANNIE	Humpty Dumpty was pushed	`Mon Sep 04 1995 03:11`	10
	One of our customers is having the same problem. The large number of agents is the result of a lot of DECrptr 90TSs in the network. Re the workaround in .1, to have multiple agent files, how does this work? I'm not familiar with the VMS version at all - how would you create a second agent file and toggle between them in HUBwatch? Thanks Jeannie
2609.5		SLINK::HOOD	Maine state bird: The black fly	`Tue Sep 05 1995 10:56`	26
	$ define HUBWATCH_LIBRARY <directory with first agents file> $ WATCH /AGENT 1.3.4.5 $ define HUBWATCH_LIBRARY <directory with second agents file> $ WATCH /AGENT 3.4.5.6 Just a reminder... There are very few modules that need to be in the agents file. (DECbridge 90's, DECserver 90L's and one or two others) You do not need to put every agent and every module in that file. In fact, both the Unix and the OpenVMS versions of HUBwatch will do an ARP cache search for the agent name you specify on the command line to invoke HUBwatch, so you can say: # hubwatch -a myagent or $ watch /agent myagent and HUBwatch will successfully translate myagent into 3.4.5.6 or whatever. At any rate, we'll try to fix this for V5.0 Tom Hood HUBwatch
2609.6	Thanks!	SNOFS1::KHOOJEANNIE	Humpty Dumpty was pushed	`Tue Sep 05 1995 20:55`	8
	Thanks Tom, I'll convey all your thoughts to our customer. The reason that this customer has so many agents is because of a large number of DECrptr 90TSs (that are not in hub900s). Don't these all need to be in the agents file? :-) Jeannie
2609.7		SLINK::HOOD	Maine state bird: The black fly	`Wed Sep 06 1995 14:35`	1
	Not a single one of them needs to be in an agents file.
2609.8	If you can go higher what would you want?	NETCAD::FORINO		`Tue Sep 26 1995 13:37`	7
	After looking into this the number of agent's is hardwired to a max of 256. I have to examine the implications of making it larger but if we decided to what (opening a can of worms here) maximum would people be satisfied? I would think 512 would be the limit but wonder if even this is a bit too much. John
2609.9		SLINK::HOOD	My God, what have I done to my spleen?	`Tue Sep 26 1995 19:21`	1
	There should not be a limit.
2609.10	Update to this note?	SNOFS1::KHOOJEANNIE	Humpty Dumpty was pushed	`Tue Mar 12 1996 02:59`	11
	Hope the "bad news bear" bears some good news here ... 8-) I wanted to confirm whether the maximum number of agents in HW for VMS v4.1 has actually stayed the same or has it increased? Also, what is the maximum number of agents for ClearVISN Multichassis Manager for Windows - and will this increase as we move to Win 95 and Win NT? Thank you Jeannie
2609.11	I'll check	SLINK::HOOD	Your bad news bear	`Tue Mar 12 1996 09:52`	13
	Jeannie, I don't know if anyone has changed the max size. However, the OpenVMS port is my job this week, so I'll take a look at upping it. Advance warning: We are going to be making the agents file disappear sometime this year as all clearVISN products move to a (still-undefined) common database. There will be conversion utilities to import HUBwatch agents files and update Router Manager databases, so customer impact should be minimal. Tom Hood clearVISN not-so-bad-news bear, I hope