TCP/IPv6 Configuration and Management Manual (G06.24+)

SCF Reference for NonStop TCP/IPv6
HP NonStop TCP/IPv6 Configuration and Management Manual—524523-008
8-48
ALTER MON Command for TCP6MAN
TCP-MAX-REXMIT-COUNT
is the maximum number of continuous retransmissions allowed before a TCP
connection is dropped. The default is 12. The range is 1 to 12.
TCP-TOTAL-REXMIT-DURATION
is the total time a TCP connection can be in the retransmission state without
receiving an acknowledgement from the other endpoint before the TCP connection
is dropped. The default is 720000 milliseconds. The range is 500 to 14400000 (.5
seconds to 4 hours). Note that a connection can be dropped sooner if the TCP-
MAX-REXMIT-COUNT multiplied by the TCP-MAX-REXMIT-TIMEOUT is a value
less than the TCP-TOTAL-REXMIT-DURATION.
PORT-SHARE-ENABLE { ON | OFF }
allows applications running in different processors to share a port but have different
IP addresses when set to ON. When set to OFF, applications trying to share a port
while having different IP addresses fail to bind. The default setting is OFF.
Examples
•
To alter the DELAYACKS and DELAYACKSTIME attributes on all configured
TCP6MONs:
-> ALTER MON $ZZTCP.*, DELAYACKS ON, DELAYACKSTIME 20
•
To alter the TCPSENDSPACE to 4096 on all configured TCP6MONs:
-> ALTER MON $ZZTCP.*, TCPSENDSPACE 4096
•
To change the TCP and UDP port range to 32768 to 65535:
-> ALTER MON $ZZTCP.*, MIN-EPHEMERAL-PORT 32768
•
To alter the NonStop TCP/IPv6 subsystem TCP-MAX-REXMIT-COUNT attribute on
all configured monitors:
-> ALTER MON $ZZTCP.*, TCP-MAX-REXMIT-COUNT 10
Considerations
The MIN-EPHEMERAL-PORT and MAX-EPHEMERAL-PORT attributes have been
added to allow you to modify the ephemeral port-range used by the TCP6MONs to be
more usable in your environment. The ephemeral port range is between 1024 and
65024. Each processor is allocated one sixteenth of this range.
Prior to the G06.24 RVU, if two applications in the same processor bound to a local
port and specified different addresses, the bind would fail. However, if the applications
ran in different processors, the bind succeeded. The successful bind for applications
running in different processors and binding to the same port but to different addresses
was non-standard behavior for most TCP/IP implementations.