[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

1891.0. "How do standalone DECrepeater 90TS appear in Hubwatch?" by UNITED::64397::nt () Mon Jan 16 1995 04:01

If i have 30 DECrepeater 90TS modules distributed amongst 30 sites, and they are to be managed with Hubwatch for MS-Windows, 
how will they be displayed? Lets assume there are no other DEChub modules in the network.


Will they appear in a Hub picture, will they be 'invisible', do i need any DECagents?


thanks
dave
T.RTitleUserPersonal
Name		DateLines
1891.1Screen overflow error...& recovery procedure :-)NETCAD::BATTERSBYMon Jan 16 1995 09:1521
    I've er...adjusted the base message so it would all appear in an
    80 column screen.
    
    Bob
    ------------------------------------------------------------------------
            <<< NETCAD::KALI$USER3:[NOTES$LIBRARY]HUB_MGNT.NOTE;1 >>>
                   -< DEChub/HUBwatch/PROBEwatch CONFERENCE >-
================================================================================
Note 1891.0  How do standalone DECrepeater 90TS appear in Hubwatch?   No replies
UNITED::64397::nt                                    10 lines  16-JAN-1995 04:01
--------------------------------------------------------------------------------
If i have 30 DECrepeater 90TS modules distributed amongst 30 sites, and 
they are to be managed with Hubwatch for MS-Windows,  how will they be 
displayed? Lets assume there are no other DEChub modules in the network.
Will they appear in a Hub picture, will they be 'invisible', do i need 
any DECagents?


thanks
dave
1891.2NETCAD::HERTZBERGHistory: Love it or Leave it!Mon Jan 16 1995 09:3615
    Each standalone DECrepeater 90TS which has been given an IP address can
    be seen and managed by Hubwatch and will appear in a standalone picture
    on the Hubwatch screen. 
    
    You can manage each module either in-band (over the network to which it
    is attached) or out-of-band via its front-panel console/OBM port.  I
    assume you'd manage in-band in the application you're describing.
    
    To be managed, each unit must have an IP address assigned.  If there
    are any units without IP addresses, they cannot be seen nor managed by
    Hubwatch; they are "invisible."
    
    Each 90TS contains an integrated agent... you need no other agent.
                                                             
    							Marc
1891.3UNITED::64397::ntMon Jan 23 1995 09:316
Thanks both for fixing my base note (how did I do that!)
and also answering my query!


/dt