[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
Title: | DECmcc user notes file. Does not replace IPMT. |
Notice: | Use IPMT for problems. Newsletter location in note 6187 |
Moderator: | TAEC::BEROUD |
|
Created: | Mon Aug 21 1989 |
Last Modified: | Wed Jun 04 1997 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 6497 |
Total number of notes: | 27359 |
6084.0. "Frame Check errors with MCC sink" by EDUOZ::BOERS (Jack - singed by the candlestick!) Sat Aug 13 1994 02:55
Cross ported n DECNET-OSI_for_VMS
================================================================================
Note 1721.0 Frame Check Errors with remote event sink No replies
EDUOZ::BOERS "Jack - singed by the candlestick!" 20 lines 13-AUG-1994 01:53
--------------------------------------------------------------------------------
I have two workstations side by side. A VAXStation 4000/90 running
OpenVMS 5.5-2 and DECnet-OSI, as well as DecMCC. Beside it is a
DEC 3000 model 300 running OpenVMS AXP V1.5. I use the AXP as a display
for MCC, so usually have 8-10 connections from the 4000 to the 3000.
There are never any errors reported between them.
I set up an event dispatcher outbound stream to the 4000, user Name =
MCC_ECL_SINK - as per the documentation. I also did this on the local
4000, to sink to itself. As soon as I did that on either node, that
node started reporting frame check errors randomly, but only about 2-3
every 5 minutes.
I believe frame check errors are a hardware problem, but the network is
fairly quiet, and these have only come up since I set up a remote sink.
Also, these systems are only a few months old.
Any suggestions as to where to start looking?
Regards
Jack Boers
T.R | Title | User | Personal Name | Date | Lines |
---|
6084.1 | Reported on the 4000 | EDUOZ::BOERS | Jack - singed by the candlestick! | Sat Aug 13 1994 02:57 | 6 |
| re .0
I should have said that the errors are being reported on the 4000 MCC
station node, the target of the sink. The sink is connected.
JB (~;
|
6084.2 | Solved by addressing | EDUOZ::BOERS | Jack - singed by the candlestick! | Wed Aug 17 1994 22:16 | 7 |
| Just in case anyone else gets this, I finally solved it. Even though
both stations were running DECnet/OSI, the management VAXstation only
had a Phase 4 address. Both systems are now at Phase V addressing only
and the problem has dissappeared.
Regards
Jack
|