Conference netcad::hub_mgnt

    The DECserver 900TM must have enough IP running to download via that 
    protocol. Hence, it probably has ICMP in ROM too, and therefore 
    responds to a Ping. The SNMP code must be in the download image 
    though. 
    
    For it to show up as unavailable until it's loaded, perhaps there's 
    a way in NetView to have it poll using SNMP, rather than by Ping.
    
    We'll take a look at the LED problem you reported in HUBwatch.

HUBwatch:  As soon as the DECserver identifies itself to the hub manager,
it will be displayed by HUBwatch.  The 7-segment race-track displayed by
HUBwatch DOES NOT INDICATE MODULE STATUS.  That information is not available
through SNMP from the DECserver.

For any and all questions about the DECserver 900 and its software, your best
bet is the TOOK::TERMINAL_SERVERS notesfile.

Tom Hood
HUBwatch

Hi,

"Topic cross-posted to Terminal Server"

Sorry for this question, but is this notesfile available for the power 
problem listed in the .0 or do I have to cross-posted this problem to a 
another notesfile too ?

Thanks a lot

yves



**** copy from Terminal_Server Notesfile ********

Tom,

Refer to your answer .2, I think that it is important to
make the module DS900 grey or whatever, ( even if the "7-segment race-track
displayed by HUBwatch DOES NOT INDICATE MODULE STATUS" ) if it is installed
successfully but not available for any reason (like a DLL  software
 unsuccessfull) 

The digit value is not really crucial, but making a difference between a 
module running or not-running is very important from a customer or any 
network manager point of view: for  fast troubleshooting and for
credibility of the product. 

I have started a script on PNV to make the icon of the decserver900
appears red as long as the software is not loaded and the ifsystem up
status not reachable.

But the problem is that from a GUI like Hubwatch, it is important to
have a minimum of WYSIWYG on module status because there is no workaround
if the customer uses only hubwatch.

I know again that it's not the good notes-file conference to make this
comment , but if you want, for example, to manage traps coming  from 
any hub module, you have to order a software like PNV or DECmcc and so
a station with its OS.
I know it's stupid, but sometime this is how we can lost project.


Thanks a lot if you can do something to make a difference (even a small)
on Hubwatch between two systems status different of a module.

Best Regards

yves 

Any HUBwatch issues around the DECservers are OK here.

Any DECserver firmware/software issues should go to the terminal_servers
conference.

The race-track on the HUBwatch bezel for the DECservers wasn't meant to
show status.  When it was designed (simply to look spiffy) we hadn't even
thought that anyone would think it was true.  Then, this past autumn, we
started hearing a lot of comments from the field about it.  It does have
to change.  The easiest thing is to simply keep the 7-segment display
turned-off on the bezel all the time.  Maybe later we could do as you
suggested and make it red if the module is not running.

Tom Hood
HUBwatch

Thanks Tom,

Just the last question concerning this problem.
- Do you have any idea about when this kind of implementation 
will be available ? (release 4 of Hbwtch ?) 


regards

yves