...
Field | Description | ||
---|---|---|---|
Data Transfer Options | Set Default Send Buffer size to When this option is selected, a value may be specified that overrides the default size of the application buffer used to send data across a network connection. A buffer size of 0 (zero) is saved when this option is left un-selected. UDM will then manage the size of the buffers itself based on internal limits. Exercise caution when changing this option, as it could have a significant performance impact. See the send_buffer_size configuration option in the UDM Reference Manual for more information. Set default receive buffer Compress Data When the data encryption option is checked and the (negotiate using data SSL/TLS cipher list) item is selected, the encrypt option is set to yes, which instructs UDM Manager to negotiate the encryption method with the Server, using their respective data SSL/TLS cipher lists. | Send/Receive Buffer Sizes |
When the data encryption option is checked and the (negotiate using data SSL/TLS cipher list) item is selected, the encrypt option is set to yes, which instructs UDM Manager to negotiate the encryption method with the Server, using their respective data SSL/TLS cipher lists. |
Send/Receive Buffer Sizes | Set Default Send Buffer size to | ||
Default mode for data transfer | Specifies the default manner in which files will be transferred (Binary or Text). |
Universal Data Mover Manager: Network Options - Fault Tolerance
Field | Description |
---|---|
Network Fault Tolerance | Enable Network Fault Tolerance When this option is selected, network fault tolerance will be requested for each instance of a Universal Data Mover Manager that is run from this location. This means that if the remote Universal Data Mover Server supports network fault tolerance, all lost network connections will be detected and recovered. Network Delay The number of seconds that can be attributed to network latency for any transmission of data among Universal components. This value is |
Default mode for data transfer | Specifies the default manner in which files will be transferred (Binary or Text). |
Universal Data Mover Manager: Network Options - Fault Tolerance
Field | Description |
---|---|
Network Fault Tolerance | Enable Network Fault Tolerance
The maximum value permitted is 500M. A value of 0 (zero) causes every message that contains data for a file transfer to be acknowledged (default NFT behavior). |
...
Field | Description |
---|---|
Override the default TCP receive buffer and set to | Allows the UDM manager to set the TCP receive buffer for a UDM server larger than the default maximum of 64k bytes. Setting this value enables RFC 1323 window scaling support, which can increase TCP buffer sizes over a fast, high-bandwidth network to almost 1 gigabyte (1,073,725,400 bytes).
Note that the maximum allowable value for this option is 1073725440 bytes, which can be requested using a value of 1g. |
Override the default TCP send buffer and set to | Specifies the TCP send buffer size for the TCP socket connections from the UDM manager to the UDM server. The option has no effect for UDM three party transfers. The UDM server and Universal Broker configuration affects UDM three party transfers.
Note that the maximum allowable value for this option is 1073725440 bytes, which can be requested using a value of 1g. |
Disable TCP packet coalescing | Select this option to disable the TCP packet coalescing algorithm (that is, Nagle algorithm). When this option is unchecked, the default TCP implementation is used, which may or may not disable the algorithm. |
...
Field | Description | ||
---|---|---|---|
Control Session SSL cipher List | Universal Data Mover uses the SSL/TLS protocol for internal communication between application components. A control session is established within the application that provides the connections necessary for this communication to take place. The SSL/TLS cipher suites available for communication across the control session are listed here. To disable SSL/TLS encryption and message authentication for messages transmitted across the control session, select the NULL-NULL entry. Use of this cipher requires that the remote UDM Server's encrypt_control_session option be set to no. Otherwise, the UDM Server will issue a protocol error when the Manager tries to establish the control session with it. | Data Session SSL Cipher List | Universal Data Mover uses the SSL/TLS protocol for transmission of data across the network. A data session is established within the application that provides the connections necessary for the transfer of data to take place. The SSL/TLS cipher suites available for communication across the data session are listed here. The selected cipher suites will be forwarded to the Universal Data Mover Server. The Server will compare this list to its own list of ciphers it is capable of accepting. The result of the comparison will be an agreed-upon cipher used for communication over the data session. If you are unsure which ciphers will be accepted by the Server, it is best to leave them all selected. Use the up/down arrows on the right to sort the list and establish a priority for the selected ciphers. The first one in the list that is accepted by the Server will be the one used.
To disable SSL/TLS encryption and message authentication for messages transmitted across the control session, select the NULL-NULL entry. Use of this cipher requires that the remote UDM Server's encrypt_control_session option be set to no. Otherwise, the UDM Server will issue a protocol error when the Manager tries to establish the control session with it. |
Data Session SSL Cipher List | Universal Data Mover uses the SSL/TLS protocol for transmission of data across the network. A data session is established within the application that provides the connections necessary for the transfer of data to take place. The SSL/TLS cipher suites available for communication across the data session are listed here.
| ||
Negotiate sessions using | (No help provided.) |
...
Field | Description |
---|---|
Event Generation Options | Generate activity monitoring events
Entries are processed from left to right, and the list is order dependent. For example, an entry of x*,100 prevents generation of all event types except 100, while an entry of 100,x* prevents generation of all event types (the right-most entry takes precedence). |
...