[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

621.0. "HUBwatch Questions" by HGRNCC::FARADAYCHONG (Faraday Chong@hgo 852-8053590) Fri Jan 14 1994 08:43

    Need help in managing DEChub 90/900.
    
    A national customer who has standardize their system and network
    management on NetView/6000 or POLYCENETR, as such all proposed network
    component must be manageable from POLYCENTER NetView platform.
    
    We cannot meet this requirement now, but that is okay if we have a
    migration path and defined timescale that falls within the customer's
    planned schedule.
    
    Now questions:
    
    (1) Today, only HUBwatch for OpenVMS VAX V2.0 can manage DEChub 900,
    what is the planned availability of OSF/1 AXP version?
    
    (2) Will the initial OSF/1 AXP version be launchable from POLYCENTER NetView?
    If not, when will it be?
    
    (3) Now the harder part, which the customer has not decided if they
    really need this. They may end up having some 20+ DEChub 900 in just
    one of their subnet. Being an element manager, HUBwatch can manage only
    one hub at a time, and there is no API to HUBwatch. How can one monitor
    (including display) and control (change some hub configuration in case
    there are fault in the network) automatically? (Can we write network
    application using POLYCENTER NetView APIs to do these?)
    
    Faraday

T.R	Title	User	Personal Name	Date	Lines
621.1		QUIVER::SLAWRENCE		`Fri Jan 14 1994 09:02`	9
	(3) The DEChub 900 can be managed with any SNMP management application; the MIBs are published and compilable. So if you can configure your application to watch for changes and take actions in response to them then you can do so with the 900. Some aspects of managing the 900 are quite complex (ask the HUBwatch developers :-), but all are possible. In fact, since we are developing the MAM concurrently with HUBwatch, we usually don't have it for our initial testing of new features and have to use a generic SNMP tool.
621.2	HUBwatch Answers	SLINK::HOOD	I'd rather be surfing	`Fri Jan 14 1994 10:08`	15
	(1) HUBwatch V3.0 will be ported to OSF/1 AXP. No dates are official, but it should be a little while after it ships for OpenVMS (SSB in March). (2) Initial OSF/1 version launchable via NetView? Not known yet, but as soon as we can make it work, it will be. This is the plan. (3) HUBwatch V3.0 includes alarming and polling of many hubs/agents. Once you set it up, it will simultaneously monitor as many hubs as you want. Repeating an earlier message, from now on, any given version of HUBwatch on one operating system is the same (more-or-less) as that version of HUBwatch on another operating system. So, V2.0 for OpenVMS = V2.0 for Windows. V3.0 for OpenVMS = V3.0 for Windows = V3.0 for OSF/1. There may be some slight differences due to differences in the environments, but they are functionally the same.