HP3000-L Archives

September 2015, Week 5

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Donna Hofmeister <[log in to unmask]>
Reply To:
Donna Hofmeister <[log in to unmask]>
Date:
Wed, 30 Sep 2015 09:01:34 -0600
Content-Type:
text/plain
Parts/Attachments:
text/plain (59 lines)
On Tue, Sep 29, 2015 at 9:30 PM, Mark Ranft <[log in to unmask]> wrote:

>
>  TRANSMISSION CONTROL PROTOCOL (TCP) CONFIGURATION:
>    Checksum Enabled:                                Y
>    Maximum Number of Connections:                   20000
>    Retransmission Interval Lower Bound (Secs):      1
>    Maximum Time to Wait For Remote Response (Secs): 180
>    Initial Retransmission Interval:                 2
>    Maximum Number of Retransmissions:               8
>    Connection Assurance Interval:                   60
>    Maximum Connection Assurance Retransmissions:    4
>
>  CONFIGURED NETWORK INTERFACES:
>
>    Network Interface Type:              LAN
>    Network Interface Name:              LAN1
>    Network Interface IP Address:        C 192.168.001 001
>    IP Subnet Mask:                        255.255.255.000
>    Network Segment Size:                1514
>

From the nmmgr reference manual:

This field specifies the largest packet
(including all data, protocol headers, and link level
headers) that will be sent by the LAN device. The only
reason for entering a value smaller than 1514 is to
make better use of memory for those systems where it
is known that upper layer services will always send
shorter messages. Note that whenever packets larger
than the network segment size are sent, they will be
fragmented to the network segment size, thus incurring
fragmentation overhead at the source and assembly
overhead at the destination node.
Default value: 1514 bytes
Range: 300–1514


what the above is not saying is -- for most systems setting this to
anything other than 1514 will result in abysmal network performance -- much
like a 100bt system acting like it's configured for 10bt -- because the
system is busy fragmenting packets to fit into whatever number you've got.
 on mpe, the tcp headers are stored in those 14 'extra' bytes.

regarding your tcp timers, click on the link (
http://www.allegro.com/?page_id=1391) and react accordingly ;-)       - d

-- 
Donna Hofmeister
Allegro Consultants, Inc.
408-252-2330
Visit us on Linkedin
<https://www.linkedin.com/company/allegro-consultants-inc->
Like us on Facebook <http://www.facebook.com/allegroconsultantsinc>

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

ATOM RSS1 RSS2