[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

2180.0. "connected stations revisited" by CSC32::MAULUCCI () Fri Apr 07 1995 21:49

    I am working with a customer that has questions around "connect
    stations" and have read notes 1115 and 1779. 
    He is telling me that when he used 1.2 (I know it's not current) hubwatch 
    software he was able to click on the port of his DECrepeater 90 in his
    DEChub 90 and see the address of the systems connected to that port.
    
    Since upgrading to hubwatch V3.1 (probably the "for windows" flavor) and 
    going to a DEChub900 with a DECrepeater 900tm, he can not merely click
    on the DR900 port and see the connected stations. He has to
    additionally click on stations, and get the "serveral minutes to complete"
    message before he can see the connected stations. 
    
    He thinks that at another site he knows about that has the same
    configuration and V3.1 hubwatch that all they have to do is click on
    the port and the connected stations information is automatically
    displayed. 
    
    Is there a way to set this up ? Why was it changed ?
    
    Thanks in advance,
    
    Gene Maulucci
T.RTitleUserPersonal
Name
DateLines
2180.1NETCAD::DRAGONMon Apr 10 1995 12:2516
    
    Gene,
    
    	There is no way to set this up. On the 900-style Repeater Port
        Summary View the user must use the [Stations] button and on
        90-style Repeater Port Summary View they do not have to, which 
        should explain the difference at the other site.
    
        It was changed for performance reasons. Instead of displaying all
        possible information that a user may or may not currently care
        about, certain views make some of the information optional. This
        way the user doesn't have to suffer the overhead of getting connected
        stations each and every time the view is invoked.
    
    Regards,
    Bob