| Title: | FDDI - The Next Generation |
| Moderator: | NETCAD::STEFANI |
| Created: | Thu Apr 27 1989 |
| Last Modified: | Thu Jun 05 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 2259 |
| Total number of notes: | 8590 |
<<< NAC::DISK$WORK295:[NOTES$LIBRARY]RBMS_LANBRIDGE100.NOTE;1 >>>
-< RBMS and LAN Bridge 100 Notes >-
================================================================================
Note 371.0 DECelms v1.01 - MONITOR error - "protocol in use" No replies
HGOVC::LILLIANTANG 9 lines 24-OCT-1990 05:25
--------------------------------------------------------------------------------
When using the "Monitor .. line 2" command on a DECbridge 500,
frequently error "protocol in use" is encountered. No TSM, Ethernim, or
NCP is running at the time. Listener and Poller, however, are started.
Does the Monitor command uses the MOP protocol as well, and thus in
conflict with the latter two processes or there are other reasons
for such error? A customer wants to use both the Poller and Monitor
commands simultaneously.
regards, Lillian
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 162.1 | BAGELS::WILLIAMS | Bryan Williams | Mon Oct 29 1990 12:37 | 3 | |
Have you tried escalating the problem?
Bryan
| |||||
| 162.2 | Known Limitation | LEVERS::COLELLA | Thu Nov 01 1990 12:31 | 28 | |
In the future, please indicate cross-posted notes. -Thanks.
================================================================================
<<< NAC::DISK$WORK295:[NOTES$LIBRARY]RBMS_LANBRIDGE100.NOTE;1 >>>
-< RBMS and LAN Bridge 100 Notes >-
================================================================================
Note 371.1 DECelms v1.01 - MONITOR error - "protocol in use" 1 of 1
LEVERS::COLELLA 17 lines 1-NOV-1990 11:10
-< Known Limitation >-
--------------------------------------------------------------------------------
The key is that Polling and Monitoring use the same protocol,
(the RBMS protocol 80-38, in shared-with-destination mode)
so the two processes do in fact conflict when sending/receiving with
the same device at the same time. This usually isn't a problem with
a large database, since that reduces the chance of collisions with
the same device. However, with a smaller DB, the same couple of
devices are continually polled/monitor, and eventaully you will see
a collision.
One thing that might help is to cut down the frequency of monitoring
with the EVERY feature. (ex. MON LINE 2 EVERY 30 MIN)
Or, you could write a command file to turn the poll/mon on and off
at certain times of the day.
Hope that helps.
Barry
| |||||