1828631 Members
1936 Online
109983 Solutions
New Discussion

Possible DECNET issue

 
Phillip Tusa
Advisor

Possible DECNET issue

Greetings to all ...

I feel the following description has to do
with DECNET. From the VMS prompt I enter
the following command line:

$MCR NCP
NCP>

The I enter the following:

NCP>SHOW KNOWN LINE COUNT

Then displayed is "receive failure" count
Each time the above command is entered, the count is constantly increasing.

Some where in all of this is an error message
stating "Excessive Block Check Error" is displayed.

Does anyone have an idea as to what is going on here? Any assistance would be appreciated!

Thanks;

Phil
"I'd rather be a VMS guy, any day of the week!"
6 REPLIES 6
Richard Brodie_1
Honored Contributor

Re: Possible DECNET issue

'Some where in all of this is an error message
stating "Excessive Block Check Error" is displayed.'

You have a hardware fault or configuration error, which has nothing in particular to do with DECnet. With Ethernet, I assume?

If you attached the output of
$MC LANCP
SHOW DEV/PAR
SHOW DEV/COUNT

that might be helpful in diagnosing the problem. Also knowing what is directly connected to the interface in question.
The Brit
Honored Contributor

Re: Possible DECNET issue

Phil,
what do you get if you leave off the "counters" piece? i.e. what do you get from a "show known lines" and/or a "list known lines"???

Dave
Hoff
Honored Contributor

Re: Possible DECNET issue

Bad router, bad switch, bad or flaky cable, bad hardware with the local NIC or with the network hardware, flaky hardware, screaming NIC, controller, potentially mis-matched duplex settings, etc.

DECnet itself is almost certainly just a bystander here.

There are a couple of ancient NICs that became notorious for corruptions and/or for screaming. The DEQNA is a salient example of NICs That Should Be Replaced.
Phillip Tusa
Advisor

Re: Possible DECNET issue

Thanks to all who posted a response.

Let me do a little research and testing. I will get back to you all with the solution that fixed my stated problem.


Phil

"I'd rather be a VMS guy, any day of the week!"
Dean McGorrill
Valued Contributor

Re: Possible DECNET issue

>DECnet itself is almost certainly just a bystander here.

True! of the many cases that came in just
like this, just about everyone turned out to be something
else then decnet. Dean
Robert Gezelter
Honored Contributor

Re: Possible DECNET issue

Phillip,

I concur. DECnet is, as Hoff eloquently put, "a bystander".

Hubs, bridges, and other network components that are supposed to be transparent also can be added to the list of possible candidates.

If you are using a separate transceiver, it is also a candidate (as are any settings on the transceiver).

- Bob Gezelter, http://www.rlgsc.com