Veritas Storage Foundation 5.1 SP1 for Oracle RAC Administrator"s Guide (5900-1512, April 2011)

Table 5-4
LLT flow control tunable parameters (continued)
Dependency with other
LLT tunable parameters
When to changeDefaultDescriptionLLT
parameter
This flow control value
should be lower than the
highwater flow control value.
The value should not be close
the highwater flow control
value.
Not applicable100When 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.
lowwater
This flow control value
should always be higher than
the rportlowwater flow
control value.
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.
200When the number of packets
in the receive queue for a
port reaches highwater, LLT
is flow controlled.
rporthighwater
This flow control value
should be lower than the
rpothighwater flow control
value. The value should not
be close the rporthighwater
flow control value.
Not applicable100When LLT has flow
controlled the client, 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.
rportlowwater
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.
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.
50This is the maximum number
of un-ACKed packets LLT will
put in flight.
window
257Tunable parameters
About LLT tunable parameters