[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

864.0. "Two ways of in-band management?" by HGRNCC::FARADAYCHONG (Faraday Chong@hgo 852-8053590) Mon Mar 28 1994 05:13

    In reading DEChub 900 MIBs, I have the impression there are two ways of
    in-band management:
    
    (1) Assign an IP address to Hub Manager - use the IP address to manage
    everything in the hub,
    
    (2) In addition to IP address for Hub Manager, one can assign IP
    address to module inserted in the hub, this ends up with one IP address
    for the Hub Manager, and some hub module may have it's own IP address -
    the module can be managed through either IP address,
    
    Please
    
    (a) confirm the above understanding
    (b) explain pros and cons
    
    Faraday

T.R	Title	User	Date	Lines
864.1	Correct	QUIVER::SLAWRENCE	`Mon Mar 28 1994 14:59`	18
	Your understanding is correct; you can do either. Most devices are managable via the hub IP address (notable exceptions: DECbridge90's, all DECservers, DECbrouter90s, WANrouter90, MUXserver). Using the IP address of the hub is the only way to get Out of Band Management of the hub devices. Obviously, you save lots of addresses. There is some performance penalty for using the HUBs address, but I don't have any numbers for that. Note that current versions of HUBwatch don't make any attempt to optimize the choice of IP addresses; if a device is in a hub and you select it by double clicking on it in the hub, then you'll use the hubs address even if it has one of its own - you need to switch agents explicitly using the agents table to use its own address.
864.2	more exceptions...	NAC::FORREST	`Tue Mar 29 1994 11:46`	11
	Add all currently shipping Token Ring modules and the DECpacketprobes to the list of exceptions. A new TR mau is coming, and should allow either its own or the hub's IP address to be used. The DECpacketprobes require you to use the module IP address. The DECagent 90 is also on the exception list, although I'm not sure why anyone would want to try to manage it using another IP address. This has to do with backplane management protocols supported by a module; some modules just support the minimum (older 90 modules and most 3rd party modules are like this).