[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

2995.0. "IP services, SNMP, hub management" by LEXSS1::HEBERTJ () Tue Nov 21 1995 21:29

Hi,

	I'm trying to verify some information on the DEChub 900 and HUBwatch.
My understanding is that to manage the DEChub900 you can do it one of two ways:
via out-of-bound management where an IP address is assigned to the console port 
and a VT terminal is used to configure the DEChub or it can be done by
inserting one of the 900 modules that provides IP services (or certain 90
modules) so that HUB watch can then be used to access the hub via in-band
management.  The 900 module (or 90) would have the IP addres assigned to it.
Is this correct? 

	A further clarification: the DEChub 900 has the HUB manager (SNMP
agent?) in it and that the module providing the IP services is what allows the
SNMP packets to communicate between HUBwatch and the hub.  Is this correct?

Regards,

Jim

T.R	Title	User	Personal Name	Date	Lines
2995.1	It works like this	NETRIX::"[email protected]"	Steven Freke	`Wed Nov 22 1995 08:18`	19
	Jim The hub900 as you say has an agent built in. THis is called the MAM module. IT provides a means by which the modules can talk to hubwatch. In the case of a dechub 90, you would use a decagent 90, and this will act a as a busmaster, and would provide IP services. Because the hub900 has a MAM module, this acts as bus master. So all you now need is a module to provide IP services. THis can be either an agent90, or an repeater900 series. There is also some debate as to whether a 90TS repeater will work. This is because the spec says that it is capable of SNMP management. I am still waiting on a customer test to see if this is the case. As we do not have one here. I hope this answers you questions. If you are still confused then give me a call. Regards Steven Freke LAN Team, UK CSC [Posted by WWW Notes gateway]
2995.2		SLINK::HOOD	My God, what have I done to my spleen?	`Wed Nov 22 1995 12:43`	21
	IP Services Module: Supplies the MAC to the agent in the DEChub 900 backplane. Required if you want to ever talk to the DEChub 900 agent (MAM) using a PC or a workstation over the network. In-band management: You connect your PC or workstation running HUBwatch to your network. You make sure there is a connection between the network and the IP services module of hub being managed. (This connection can be any legal network connection; direct, through bridges and/or routers, over the backplane, etc. as long as there's IP connectivity). In-band mgmt requires an IP services module. Out-of-band management: You connect your PC (*not a VT terminal*) to the 9-pin (rightmost) connector on the top front of the DEChub 900. You then talk SNMP over SLIP between the PC and the DEChub 900's MAM. The DB connector (used by VT terminals) is strictly the setup port. Almost all it can do is be used to assign IP addresses, perform resets, and show basic setup config. Tom Hood
2995.3	Did I pass, did I, did I??	CGOS01::DMARLOWE	Have you been HUBbed lately?	`Wed Nov 22 1995 13:34`	11
	re. .2 >> The DB connector (used by VT terminals) is strictly the setup port. You mean the RJ45?? You're just testing the field again. Making sure we're awake or something like that. Now thats out of the way I can go back to sleep again. 8^) dave