| Title: | DEChub/HUBwatch/PROBEwatch CONFERENCE |
| Notice: | Firmware -2, Doc -3, Power -4, HW kits -5, firm load -6&7 |
| Moderator: | NETCAD::COLELLA DT |
| 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 |
I have a situation that I wonder if anyone has seen. I have a
community #2 setup in a remote building with the DECagent in this
building (community #1) watching the hub.
The DECagent (1.0) sees the DECbridge (3.0) in the other building just
fine however when you add 90TL modules, the agent will see the modules
for about 30 seconds and then call the slot empty, however the bridge
and repeater are seen all the time.
The agent resides in community 1 and has no problems in seeing the
servers in it's own community.
Is this a bug?
�
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 172.1 | So.. s o c k s! | GLDOA::STOUGHTON | Thu Feb 25 1993 13:56 | 6 | |
After review of earlier notes I found that its a polling problem.
but fixed if the server is running v2.0. Is this correct?
Where is this button located that kills polling???
Thanks in advance
| |||||
| 172.2 | How to make a 90TL stay | LEVERS::SWEET | Thu Feb 25 1993 16:18 | 8 | |
V1.0 of the DECagent does not support management of the 90TL.
Further the 90TL is not a "good" Hub citizen when it is loaded
and running terminal server software. In HUBwatch V1.1 and
DECagent V1.1 you will be able to add the TL and disbale the
DEcagent polling (In the HUBwatch ADD screen) and the TL will then
stay in the HUB.
Bruce
| |||||
| 172.3 | More details... | NAC::D_NELSON | Dave Nelson LKG2-2/BB9 226-5358 | Fri Feb 26 1993 14:21 | 4 |
RE: .2
Also see Note 171.3.
| |||||