Subject: | |
From: | |
Reply To: | |
Date: | Tue, 25 May 1999 13:10:31 -0400 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
Hello Friends @ 3000-L,
Re: MPE/ix unidentified network buffer
-----------------------------------------------------------Andy Seiposwrites--
Ï duplicated this on our production-box, and, after this (James') message,
tried it on our test-box (which is more patched; pp6 vs pp4). The result was:
Item Subsystem Name G/N Description Used High Max
____________________________________________________________________
11 NS XPORT (G) TCP Control pool 1 22 2048 :)
^^^^^
-----------------------------------------------------------Andy Seiposwrites--
OK, If I go to my system I see:
:nettool.net.sys;info="res;di"
...
22 NS XPORT (G) TCP Control pool 1 5 2048 :)
...
Note: The "TCP Control pool" is 11 on your system and 22 on mine since I
have *MANY* more NI's active.
[4]RESOURCE>>>item 22
Enter item number for detailed information :22
[5]RESOURCE>>>detail
[6]RESOURCE>>>di
Entry pointer : $00000000.00000000
TCP Control Buffer Pool
Description: TCP Control Buffer Pool is used to pass internal data such as
configuration data between modules (eg NETCP, TCP SIP/PM, etc)
. A control buffer is freed once the data is copied to the
local data structure.
High Value If the buffer pool is exhausted errors should be logged
Implications: indicating a buffer manager error. Any resultant errors
logged would probably occur at network start (when
configuration data is read in bulk) and should be reported.
Low Value NONE
Implications:
Configuration NONE
Relationship
[7]RESOURCE>>>quit
OK, not much to tell here. It is a internal buffer pool used to pass messages
between internal HP network modules... It is not possible to change the
config size of this pool.
I can give you 2 hints:
1. The "TCP Control Buffer Pool" is a new item displayed in Nettool. It is
very likely this item was added as a result of someone else running into
this full condition in the recent past. I re-itterate it would be good
to install NSTFD10 on this machine.
2. I seem to recollect that the "TCP Control Buffer Pool" also held the
buffer pointers to outbound TCP Packet Ack's. If you have a LAN link
problem and are having difficulty getting frames on the physical LAN
cable (due to it being too busy as an example), the "TCP Control Buffer
Pool" might start filling up... i.e. recommend link trouble shooting.
Regards,
James Hofmeister
Hewlett Packard
Worldwide Technology Network Expert Center
P.S. My Ideals are my own, not necessarily my employers.
|
|
|