Advanced parameters
The parameters of this tab allow you defined specific aspects of the communication between the agents and agents and console.
Parameter | Default value | Description |
|---|---|---|
Default Timeout for TCP Based Communications (sec) | 30 | A timeout defined in seconds used by the agent for network communication. |
Default Timeout for TCP Based Connections (sec) | 30 | A timeout defined in seconds used by the agent for network connection. |
Frame Size (Bytes) | 262144 | Defines the frame size of the network type which the device uses for communication. This parameter must only be modified for devices using non-ethernet networks, such as token ring, frame relays or ATM networks. |
Connection Queue Max Size | 20 | The maximum number of queued incoming connections. |
Preferred Protocol | ipv6 | Defines the preferred protocol address when resolving the DNS aliases. |
Recorder | relay | Defines the device on which the recording is stored during capture. It could be either on a relay or on the video manager. By default, if nothing is specified, the recording is stored on a relay. If it fails, a retry is performed on the video manager. Note that if the Remote Control module of the parent is not loaded or is in a version that doesn't support this feature, a fallback connection is established with the video manager to handle the remote recording. |
Listening Socket Backlog | 100 | Size of the listening socket backlog at the kernel level. If the number of incoming connections exceed the maximum backlog size, the system refuses the overloading client connections. |
Number of select per thread | 20 | Maximum number of socket (TCP or UDP) that a thread can deal with. This parameter is valid only for Windows OS. |
Keep Alive Timeout (ms) | 4000 | Maximum time to keep the TCP connections open to make another requests afterwards when the HTTP client requests it. |
Number of socket filter threads | 10 | Number of threads that are created at an agent startup and these will be used by the SSL sockets and compressed sockets dedicated to encryption and compression. |
Compressed Socket Send Buffer Size (bytes) | 10000 | Size of the input buffer used by the compressed sockets to compress or decompress the data. |
Compressed Socket Receive Buffer Size (bytes) | 10000 | Size of the output buffer used by the compressed sockets to compress or decompress the data. |
Compressed Socket Compression Buffer Size (bytes) | 5000 | Size of the buffer used by the compressed sockets to store data after compression. |
Compressed Socket Decompression Buffer Size (bytes) | 5000 | Size of the buffer used by the compressed sockets to store data before decompression. |
SSL Socket Send Buffer Size (bytes) | 10000 | Size of the input buffer used by the SSL sockets to compress or decompress the data. |
SSL Socket Receive Buffer Size (bytes) | 10000 | Size of the output buffer used by the SSL sockets to compress or decompress the data. |
SSL Socket Encrypted Send Buffer Size (bytes) | 20000 | Size of the buffer used by the SSL sockets to store data after encryption. This parameter is valid only for Windows OS. |
SSL Socket Encrypted Receive Buffer Size (bytes) | 20000 | Size of the buffer used by the SSL sockets to store data after decryption. This parameter is valid only for Windows OS. |
WEB Socket Send Buffer Size (bytes) | 10000 | Size of the input buffer used by the WEB sockets to compress or decompress the data. |
WEB Socket Receive Buffer Size (bytes) | 10000 | Size of the output buffer used by the WEB sockets to compress or decompress the data. |
Tunneled Sockets Send Buffer Size (bytes) | 30000 | Size of the input buffer used by the tunneled sockets to compress or decompress the data. |
Tunneled Sockets Receive Buffer Size (bytes) | 30000 | Size of the output buffer used by the tunneled sockets to compress or decompress the data. |
Tunneled Sockets Max Packet Data Size | 10000 | Max size of a data packet to be sent inside a tunneled socket. The acknowledgement of the data packet depends on the value of this parameter. The acknowledgement is sent only if the maximum packet data size is reached. If you have more than one socket using the same tunnel, the sockets share the tunnel bandwidth more efficiently. |
Tunneled Socket Acknowledge Minimum Size Factor (bytes) | 20 | Tunneled sockets must acknowledge freed reception buffers. If you have too many small packets, you don't want to acknowledge each byte. To avoid sending too many acknowledgments, this factor sets the proportion of the buffer that must be freed before sending this acknowledgment. For example, if you have 1000 bytes buffer and this parameter is set to 20, then the acknowledgement is sent after (1000/20) 50 bytes are freed. |
Tunneled Sockets Holding Tunnel Send Buffer Size (bytes) | 60000 | If you have stacked tunnels, there will be too many acknowledgements which can result into an overload. To avoid this, you need to increase the buffer size by setting this parameter. This is the send buffer size for the tunneled sockets that are used as the base socket for a secondary tunnel to increase the buffer size. |
Tunneled Sockets Holding Tunnel Receive Buffer Size (bytes) | 60000 | This is the receive buffer size for the tunneled sockets that are used as the base socket for a secondary tunnel to increase the buffer size. |
Tunnel Timeout (sec) | 120 | The timeout in seconds is used to verify if the tunnel connection is still alive. This helps in detecting the malfunctioning network connections |
Nagle algorithm size (bytes) | 1500 | Nagle algorithm size. Every time you send TCP packet, the packet data may cause overhead. To avoid this, all the data that is stored in the system buffer is 1500 at least. The Nagle algorithm is used at the TCP layer to avoid fragmentation of network packets. The same algorithm is implemented for other socket types. |
Nagle algorithm time (ms) | 200 | Nagle algorithm time before sending the TCP data packet. |
Socket Relay Buffer Size (bytes) | 30100 | Socket relays are used when a tunnel goes through a device to reach another. This is the buffer size that is used by the socket relays. Note that two buffers are used for each instance, one for each direction. |
WMI connection timeout (sec) | 120 | The timeout in seconds is used to verify if the WMI Remote connection is still alive. |