[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

46.0. "Questions about HUBwatch" by TRCOA::AHMED () Fri Jun 12 1992 10:48

    
    I want to get a better understanding of how HUBwatch will work with
    DECmcc.
    
    With there be access module, presentation modules and functional
    modules for DECmcc?
    
    Can you go directly to a hub from the iconic map?
    
    Will there be icons representing each hub on the iconic map?
    
    One other questions about the MS-Windows version
    
    Can you automatically mail alert messages through mail bus if you have
    pathworks?
    
    Thanks in advance,
    
    Nadeem

T.R Title User Personal
Name Date Lines

46.1 HUBwatch port to MCC - one possible approach MEMIT::FORREST Thu Jun 18 1992 15:56 28

T.R	Title	User	Personal Name	Date	Lines
46.1	HUBwatch port to MCC - one possible approach	MEMIT::FORREST		`Thu Jun 18 1992 15:56`	28
	Here's my guess, and it's only a guess, because there's no formal engineering effort started to put HUBwatch on DECmcc. This represents the fastest way we could port from MSU to MCC. HUBwatch speaks SNMP and uses Motif, and has a custom hub polling daemon on DECmcc MSU. We may be able to port the SNMP stack and Motif intact from MSU to DECmcc -EMA Ultrix version. I don't think the hub polling daemon will port very easy. This should give you the ability to click on an icon on the DECmcc map and launch HUBwatch bringing up a picture of the hub that you pointed to. If this is how we do it, you won't be using any of the EMA stuff on DECmcc. You won't even use the SNMP access module, because HUBwatch will have its own stack. You'll have the same HUBwatch GUI on MCC and MSU, but using the iconic map native to each. You won't get any alarming because HUBwatch uses it's own flat file and doesn't tie into the MCC Executive. One other thing - we wouldn't be able to port HUBwatch to the VMS version this way - the graphics would look the same, but we would have to use a different protocol stack. HUBwatch for Windows: No, the product doesn't support activating anything other than the beep on the PC when an alarm occurs. But we'll put this on the wish list for a future rev.

Here's my guess, and it's only a guess, because there's no formal engineering 
effort started to put HUBwatch on DECmcc. This represents the fastest way 
we could port from MSU to MCC.

HUBwatch speaks SNMP and uses Motif, and has a custom hub polling daemon on 
DECmcc MSU.

We may be able to port the SNMP stack and Motif intact from MSU to DECmcc 
-EMA Ultrix version. I don't think the hub polling daemon will port very easy. 
This should give you the ability to click on an icon on the DECmcc map and 
launch HUBwatch bringing up a picture of the hub that you pointed to.

If this is how we do it, you won't be using any of the EMA stuff on DECmcc.
You won't even use the SNMP access module, because HUBwatch will have its 
own stack. You'll have the same HUBwatch GUI on MCC and MSU, but using the 
iconic map native to each. You won't get any alarming because HUBwatch uses 
it's own flat file and doesn't tie into the MCC Executive.

One other thing - we wouldn't be able to port HUBwatch to the VMS version 
this way - the graphics would look the same, but we would have to use a 
different protocol stack.

HUBwatch for Windows:

No, the product doesn't support activating anything other than the beep 
on the PC when an alarm occurs. But we'll put this on the wish list for 
a future rev.