Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!bloom-beacon!oberon!cit-vax!ucla-cs!zen!ucbvax!sdcsvax!ames!lll-tis!lll-lcc!pyramid!prls!philabs!klb
From: klb@philabs.Philips.Com (Ken Bourque)
Newsgroups: comp.os.vms
Subject: Re: System buffer unavailable from DECNET
Message-ID: <1808@briar.Philips.Com>
Date: Wed, 7-Oct-87 11:17:12 EDT
Article-I.D.: briar.1808
Posted: Wed Oct  7 11:17:12 1987
Date-Received: Sun, 11-Oct-87 02:21:54 EDT
References: <8710052221.AA23415@ucbvax.Berkeley.EDU>
Reply-To: klb@briar.philips.com.UUCP (Ken Bourque)
Organization: Philips Laboratories, Briarcliff Manor, NY
Lines: 17

In article <8710052221.AA23415@ucbvax.Berkeley.EDU> KHF@JHUIGF.BITNET writes:
>Hi gang:
>
>   We're having a DECnet problem that has finally driven me around the bend.
>We've got a pair of uVAX II's running uVMS 4.5/DECnet 4.5 (full routing).
>One has 5 MB, the other 9 MB.  On each machine, we are receiving what I
>consider to be an unusual number of SYSTEM BUFFER UNAVAILABLE counts from
>NCP SHOW LINE QNA-0 COUNTER --- 50 or more events PER HOUR!!!

It looks like you have a loading problem on the network.  It could be that one
or more nodes (not necessarily DECnet nodes) has a problem and is spraying out
garbage packets.  Or, maybe you have a genuinely heavy load (less likely).
If you have an Ethernet monitor check the traffic and see if any of the nodes
are transmitting heavily (esp. to broadcast or multicast addresses) - then
disconnect them and see if your buffer problem goes away.

Ken Bourque   klb@philabs.philips.com   ...!uunet!philabs!klb