SUMMARY: out of buffers(!?)

From: Richard A. Muirden <richard_at_rmit.edu.au>
Date: Thu, 31 Aug 1995 16:48:07 +1000 (EST)

Hi all.

Here was my orig. request:

----
Hi all.
I have a problem and no DEC manual is at all useful in tracking it
down to fix it. As DEC have still to respond to my erlier problem
regarding system performance (I put in a fault call last week) I
thought I would try here first.
Situation:
* Have just enabled fta0 device (FDDI).
The link is unavailable due to a "physical FDDI problem" (so says our comms
guy). 
netstat -i gives:
# netstat -i
Name  Mtu   Network     Address               Ipkts Ierrs    Opkts Oerrs  Coll
tu0   1500  DLI         none                5148835     0  3360782     0 72207
tu0   1500  <Link>      08:00:2b:e2:8d:60   5148835     0  3360782     0 72207
tu0   1500  131.170.8   minyos              5148835     0  3360782     0 72207
fta0  4352  DLI         none                      0     0      512     0     0
fta0  4352  <Link>      08:00:2b:a6:e2:ff         0     0      512     0     0
fta0  4352  131.170.2   minyos                    0     0      512     0     0
sl0*  296   <Link>                                0     0        0     0     0
sl1*  296   <Link>                                0     0        0     0     0
lo0   1536  <Link>                           128980     0   128980     0     0
lo0   1536  loop        localhost            128980     0   128980     0     0
netstat -I <interface> -s gives no clues as to the following problem:
when a user tries to use talk to a local user they get:
[Error on write to talk daemon : No buffer space available (55)]
and when I try and do a ping out via the FDDI link, I also see:
ping: sendto: No buffer space available
What buffer space? And how can I get these buffers back? is it because the
FDDI device is down? I have tried taking the interface down (ie: ifconfig
fta0 down) but that does nothing, and I can't find anything in the kernel
docs or the network administration or problem solving guide.
Any ideas?
OSF/1 V3.2A btw.
-richard
--------------
Thank you to the following people:
Hellebo Knut
John Stoffel
Dave Cherkus
The reason for my problem was that I had configured both my interfaces
with the same name, which is a no no I am told. ie, I had:
Name  Mtu   Network     Address               Ipkts Ierrs    Opkts Oerrs  Coll
tu0   1500  131.170.8   minyos              5148835     0  3360782     0 72207
fta0  4352  131.170.2   minyos                    0     0      512     0     0
Nasty!
Changing this to:
Name  Mtu   Network     Address               Ipkts Ierrs    Opkts Oerrs  Coll
tu0   1500  131.170.8   minyos             10924040     0  7299253     0 163158
fta0  4352  131.170.2   minyos-fddi               0     0      512     0     0
Using netsetup...worked fine!
The "out of buffers" referred to the fact that as our physical FDDI
link had been down (the card understands this and gives us Link Unavailable
and the green flashing lights) the network send buffers were full and
not being emptied by the card (for obvious reasons), this is why this
error occured.
Thanks again to everyone for your help.
-richard
-- 
Richard A. Muirden, Sys. Admin |Fan of Shostakovich, "Star Trek" and BOEING! 
Mailto: richard_at_rmit.EDU.AU    |Fly the Friendly Skies of United Airlines !
Phone: (+61 3) 9660 3814       |I created alt.fan.shostakovich! Fly: UA,AN,WN
http://www.rmit.edu.au/richard |Can *YOU* beat my 117 Shost CD's? :-)
                 Jolt Cola Can Tower Counter: 40 cans
   * 1995: Remembering 20 years since the death of Shostakovich (1906-75) *

Received on Thu Aug 31 1995 - 09:10:49 NZST