[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

3763.0. "Different modules show different IP addresses in Hubwatch...(couldn't think of a better title)" by CSC32::B_GOODWIN (MCI Mission Critical Support Team) Thu Aug 01 1996 18:41

My customer asked my the following question, they are running Hubwatch V4.1.1
for D-unix.

Why when I click on various modules, the management information is different for
the IP Address. On a DECrepeater 90TS, it shows the IP address for the 90TS,
same with a DC900MX. On a DR900TM and DECswitch900EF, it shows the IP address of
the MAM. Is there any reason for this?

Thanks,
Brad

T.R	Title	User	Personal Name	Date	Lines
3763.1	We don't need no stinkin' reason!	SLINK::HOOD	Your bad news bear	`Wed Aug 07 1996 17:33`	25
	>Is there any reason for this? Brad, there is reason behind everything we do! Sometimes it's a good reason, sometimes not. When HUBwatch is trying to figure out which IP/Community pair to use, it asks the MAM for the list of all possible agents associated with a module. The net effect of the algorithm used by HUBwatch 4.1 and previous versions, is that the highest non-MAM IP address for the module is used. HUBwatch sends an SNMP test message to that address/community. If it is successful, that's the address/community it uses. If not, it uses the MAM's address and uses <comm>-<slot> as the community Lack of success can come from many things - typical case is that the module is on a LAN that's not IP accessible to the HUBwatch workstation. [I haven't looked at this in a few months; it might use the lowest numbered IP address, but everything else is the same.] I think (not sure) the algorithm was beefed up for V5.0 Tom Hood clearVISN eng (VLAN Mgr)
3763.2		CSC32::B_GOODWIN	MCI Mission Critical Support Team	`Wed Aug 07 1996 18:49`	12
	Well Tom, You are correct that the DR900TM and DS900EF where not accessible to the Hubwatch mgmt station. So, they did put up the mam address in the mgmt info. When I connected them so they could be reachable by the mgmt station, the mgmt info changed to their respective addresses. I hope in future releases, they put management info separate from module info so the actual ip address of the device can be seen. Reason for this is we have several dis-jointed lans in one hub. Brad