|
highwater
|
When the number of packets in transmit queue for a node reaches highwater, LLT is flow controlled. |
200 |
If a client generates data in bursty manner, increase this value to match the incoming data rate. Note that increasing the value means more memory consumption so set an appropriate value to avoid wasting memory unnecessarily.
Lowering the value can result in unnecessary flow controlling the client.
|
This flow control value should always be higher than the lowwater flow control value. |
|
lowwater
|
When LLT has flow controlled the client, it will not start accepting packets again till the number of packets in the port transmit queue for a node drops to lowwater. |
100 |
Symantec does not recommend to change this tunable. |
This flow control value should be lower than the highwater flow control value. The value should not be close the highwater flow control value. |
|
rporthighwater
|
When the number of packets in the receive queue for a port reaches highwater, LLT is flow controlled. |
200 |
If a client generates data in bursty manner, increase this value to match the incoming data rate. Note that increasing the value means more memory consumption so set an appropriate value to avoid wasting memory unnecessarily.
Lowering the value can result in unnecessary flow controlling the client on peer node.
|
This flow control value should always be higher than the rportlowwater flow control value. |
|
rportlowwater
|
When LLT has flow controlled the client on peer node, it will not start accepting packets for that client again till the number of packets in the port receive queue for the port drops to rportlowwater. |
100 |
Symantec does not recommend to change this tunable. |
This flow control value should be lower than the rpothighwater flow control value. The value should not be close the rporthighwater flow control value. |
|
window
|
This is the maximum number of un-ACKed packets LLT will put in flight. |
50 |
Change the value as per the private networks speed. Lowering the value irrespective of network speed may result in unnecessary retransmission of out of window sequence packets. |
This flow control value should not be higher than the difference between the highwater flow control value and the lowwater flow control value.
The value of this parameter (window) should be aligned with the value of the bandwidth delay product.
|
|
linkburst
|
It represents the number of back-to-back packets that LLT sends on a link before the next link is chosen. |
32 |
For performance reasons, its value should be either 0 or at least 32. |
This flow control value should not be higher than the difference between the highwater flow control value and the lowwater flow control value. |
|
ackval
|
LLT sends acknowledgement of a packet by piggybacking an ACK packet on the next outbound data packet to the sender node. If there are no data packets on which to piggyback the ACK packet, LLT waits for ackval number of packets before sending an explicit ACK to the sender. |
10 |
Do not change this value for performance reasons. Increasing the value can result in unnecessary retransmissions. |
Not applicable |
|
sws
|
To avoid Silly Window Syndrome, LLT transmits more packets only when the count of un-acked packet goes to below of this tunable value. |
40 |
For performance reason, its value should be changed whenever the value of the window tunable is changed as per the formula given below:
sws = window *4/5.
|
Its value should be lower than that of window. Its value should be close to the value of window tunable.
|
|
largepktlen
|
When LLT has packets to delivers to multiple ports, LLT delivers one large packet or up to five small packets to a port at a time. This parameter specifies the size of the large packet. |
1024 |
Symantec does not recommend to change this tunable. |
Not applicable |
