[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

699.0. "Need help adding a community, DA90 T2.0" by --UnknownUser-- () Mon Feb 07 1994 08:30

T.RTitleUserPersonal
Name
DateLines
699.1Sorry!WOTVAX::HATTOSI think, Therefore I'm paid lessMon Feb 07 1994 10:063
    Apologies for the long lines... PC Conferencing...
    
    Stuart
699.2WOTVAX::STUS::Stuart HattoACB actually means A Cold BeerMon Feb 07 1994 14:0625
         <<< NOTED::DISK$NOTES6:[NOTES$LIBRARY_6OF4]HUB_MGNT.NOTE;2 >>>
                        -< Hub Management Conference >-
===============================================================================,
Note: 699.0            Need help adding a community, DA90 T2.0      1 reply
WOTVAX::STUS::Stuart Hatto "ACB actually means A    19 lines   7-FEB-1994 05:30
--------------------------------------------------------------------------------
Hi,

I have a problem with HW for W (T2.3) and HW for V (V2.0) when trying to add communities to a
DA90 (T2.0).

I select the agent and make it current.

Then I click the 'add' button in the community section. The dialog box pops up and I select an 8
slot hub with a READ only Community of 'public' and a R/W of something else. I then click apply.

The pointer changes to a watch and then the agent and community display gets refreshed. However
the community I have just added does not appear.

Now it would seem that the common thing is the DA90 (T2.3), is there a restriction on adding
communities, in which case I will go back to V1.1?

Help!

Stuart
699.3Community strings must be unique between communitiesROGER::GAUDETBecause the Earth is 2/3 waterMon Feb 07 1994 17:468
You cannot have two communities with the same community string.  I suspect that
one of your other communities has 'public' as one of its community strings.  For
reasons unknown, HUBwatch does exactly what you described (refreshes the
community display) but does not issue an error when you attempt to add a
community with a community string that is already in use.  Methinks this is a
HUBwatch bug.

...Roger...
699.4Hmm, not what the docs say!WOTVAX::HATTOSI think, Therefore I'm paid lessTue Feb 08 1994 06:589
    Thanks for that,
    
    However the HW documentation says to leave the Read Only community name
    as public because this will aid 'auto-discovery'. Therefore I left all
    the read only communities as public in all 4 agents.
    
    I will try as you suggest and report back later.
    
    Scotty out.