[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

725.0. "Impressions of T2.5 and some bug reports" by WOTVAX::HATTOS (I think, Therefore I'm paid less) Sat Feb 12 1994 06:03

    I have been playing with T2.5 and here are some brief comments so far.
    
    
    In the Repeater Port Summary window for an 90C, if I click on the
    REFRESH button, the connected stations list does not clear and refresh
    as expected, but simply repeats the list of connected stations.
    
    I am having the devils job adding new communities. I have four
    Agent90's. They each have a Read Only community of PUBLIC and a unique
    R/W community name. When I select the Agent I wish to add a community
    to and then click the ADD community button, two things happen which I
    feel are undesirable.
    
    Firstly, the add community dialog box pops up with the community names
    already filled in, unfortunately they are the wrong way round. What I
    mean is, if the agent I am adding a community to has a read only
    community of PUBLIC and a R/W of PRIVATE, when the add community dialog
    pops up, the read only community is filled in with PRIVATE and the R/W
    with PUBLIC!
    
    Secondly, even after adding the community and changing the community
    strings with the R/W string being unique again, my new community does
    not appear on the community list. This means I can only manage 4 of my
    24 hubs!!
    
    The next observation is a cosmetic one. The DIGITAL logo which appears
    on the PSU of the 90 and the front panel of the 900 is appalling. It is
    not Burgundy, and it is not readable as DIGITAL. This needs to be
    changed as with a highly visual management tool such as Hubwatch,
    sights such as this do not sell well!
    
    I would appreciate some help with my community problem, other than that
    looks good, especially now polling is working, now how about alarming!
    
    Well Done,
    Stuart
T.RTitleUserPersonal
Name		DateLines
725.1Maybe its the T2.0.10 code?WOTVAX::HATTOSI think, Therefore I'm paid lessSat Feb 12 1994 06:4112
    I take it back about the communities.
    
    I have just tried to add communities using Hubwatch for VMS V2.0.1.
    
    I am having the same problems as with Hubwatch for Windows T2.5.
    
    The common thing therefore is the Agents... they are running the latest
    T2.0.10 code. Could this be the problem?
    
    Please help..
    
    Stuart
725.2Bit happier now!WOTVAX::HATTOSI think, Therefore I'm paid lessMon Feb 14 1994 06:2116
    I take it back about the Agent code.
    
    I have now successfully added all 2 of my hubs. My problem was that I
    was using PUBLIC as my read only community for every hub. It seems that
    even the read only community has to be unique.
    
    The documentation is very weak in the area of communities, can
    something be done about it?
    
    For example...wish I could give you the Hubwatch page no....
    
    The Use manaual states that where autodiscovery is required that the
    read only community be left as PUBLIC. If you do this however you have
    the problem I had.....
    
    Stuart
725.3More T2.5 problems.CGOS01::DMARLOWEdsk dsk dsk (tsk tsk tsk)Fri Feb 18 1994 13:4325
    I have been working with T2.5 for Windows for awhile and have found
    some problems.
    
1.  I click on COMMUNITY and then click on AGENT TYPE (DECagent 90).
    However under the COMMUNITIES for that agent, only the strings (R/O 
    and R/W) for the community that the DECagent resides in show up.  The 
    strings for any other communities for that agent are blank.  If you 
    click on REFRESH then the rest of the strings appear.

2.  When you start HUBWATCH you get the SPECIFY AGENT window.  Enter
    in the IP address and then change the COMMUNITY from PUBLIC to whatever
    the agent is.  Click OK and it fails.  If the community is anything
    other than PUBLIC it fails.
    
    Go into the DECagent and make sue that either the R/O or R/W is
    PUBLIC and then it works just fine.  You can then go into COMMUNITY
    and select anything and no matter what the strings are it fine.
    
3.  I have also found problems with adding a COMMUNITY and the R/O and
    R/W strings are reversed between the "add agent" window and what
    the COMMUNITY window shows.
    
    Hope these can be reproduced.
    
    dave