T.R | Title | User | Personal Name | Date | Lines |
---|
699.1 | Sorry! | WOTVAX::HATTOS | I think, Therefore I'm paid less | Mon Feb 07 1994 07:06 | 3 |
| Apologies for the long lines... PC Conferencing...
Stuart
|
699.2 | | WOTVAX::STUS::Stuart Hatto | ACB actually means A Cold Beer | Mon Feb 07 1994 11:06 | 25 |
| <<< 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.3 | Community strings must be unique between communities | ROGER::GAUDET | Because the Earth is 2/3 water | Mon Feb 07 1994 14:46 | 8 |
| 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.4 | Hmm, not what the docs say! | WOTVAX::HATTOS | I think, Therefore I'm paid less | Tue Feb 08 1994 03:58 | 9 |
| 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.
|