![Juniper MEDIA FLOW CONTROLLER 2.0.4 - Administrator'S Manual Download Page 345](http://html1.mh-extra.com/html/juniper/media-flow-controller-2-0-4/media-flow-controller-2-0-4_administrators-manual_2032854345.webp)
network
345
Media Flow Controller Administrator’s Guide
Media Flow Controller CLI Commands
allocate more than this value for a session. When there is a full download, Media Flow
Controller tries to allocate this value to the session. Default is 0 kbps (unbounded)
with Media Flow Controller license, 200 kbps without it. Use no network connection
max-bandwidth to reset default (unbounded).
Important!
You must have the Media
Flow Controller license installed to change the unlicensed default.
•
tcp
—Set TCP parameters. Use the no form to reset a value to its default.
•
fin-timeout
—Define the time that must elapse before TCP can release a closed
connection and reuse its resources. Acceptable values are 5 to 120. Default value is
20 seconds.
•
max-orphans
—Define the maximum allowable number of sockets not attached to any
user file handle; use this to prevent simple DOS attacks. If this number is exceeded,
orphaned connections are reset immediately and a warning is displayed. Acceptable
values are 1024 to 524288, default value is 131072.
•
max-tw-buckets
—Define the maximum allowed number of TIME_WAIT sockets held
by the system simultaneously. If this number is exceeded, TIME-WAIT sockets are
immediately destroyed and warning is displayed. Acceptable values are 16384 to
1048576. Default value is 180000.
•
memory low high maxpage
—Define the TCP stack value for memory usage, in pages
of 4KB.
•
low
—When the amount of memory allocated by TCP is below this number of
pages, TCP is memory allocation is acceptable. Acceptable values are 98304 to
393216, default is 196608.
•
high
—When the amount of memory allocated by TCP exceeds this number of
pages, TCP moderates its memory consumption and enters memory pressure
mode, which is exited when memory consumption falls below the configured low
value. Acceptable values are 131072 to 524288, default is 262144.
•
maxpage
—Define the number of pages allowed for queuing by all TCP sockets.
Acceptable values are 196608 to 6291456, default is 6291456.
•
read-memory min default max
—Define the memory usage values for the READ
buffer.
•
min
—Define the minimum size of the TCP socket RECEIVE buffer. Acceptable
values are 4096 to 32768, default is 4096.
•
default
—Define the default size of the TCP socket RECEIVE buffer. This value
overrides net.core.rmem_default used by other protocols. Acceptable values are
32768 to 1048576, default is 87380.
•
max
—Define the maximum size of automatically-selected TCP socket RECEIVE
buffers. This value does not override net.core.rmem_max. Acceptable values
are 65536 to 16777216, default is 16777216.
•
syn-cookie half-open-conn
—Define the maximum number of remembered
connection requests (those that still had not received an acknowledgement from a
connecting client); use this to prevent a SYN flood attack. After Media Flow Controller
starts listening on the server socket, the value cannot be changed unless the LISTEN
socket of the delivery module is re-initialized (service restart of mod-delivery).
Default value is 1024.
Summary of Contents for MEDIA FLOW CONTROLLER 2.0.4 -
Page 6: ...Media Flow Controller Administrator s Guide VI Copyright 2010 Juniper Networks Inc...
Page 24: ...LIST OF FIGURES XXIV Copyright 2010 Juniper Networks Inc...
Page 37: ...Copyright 2010 Juniper Networks Inc 37 PART 1 Media Flow Controller Administration...
Page 38: ...Media Flow Controller Administrator s Guide 38 Copyright 2010 Juniper Networks Inc...
Page 285: ...Copyright 2010 Juniper Networks Inc 285 PART 2 Media Flow Controller Command and MIB Reference...
Page 286: ...Media Flow Controller Administrator s Guide 286 Copyright 2010 Juniper Networks Inc...