TTM Network Administration Documentation
- What’s New In This Release
- TTM Overview
- Unicast And Multicast Network Communication
- Network Setup And Configuration
- Installing And Upgrading TTM And Guardian
- TTM Daemon
TTM Remote Host Daemon And Remote Clients
- Introduction to the TTM Remote Host Daemon
- Remote Mode: Pros and Cons
- Remote Mode Operations
- Network Considerations when Deploying the Remote Host Daemon
- Configuring a Remote Host Daemon
- Configuring the Remote Client
- Compressing Data
- Manually Configuring TCP Window Size
- Testing the Remote Connection
- Remote Host Daemon Failover (Disaster Recovery)
- Advanced Topics
- Maintenance And Troubleshooting
- Ttmd.cfg File Reference
Other Log Entries
Encryption Related Events and Log Messages
The following encryption related log messages may be logged to the ttmd.log file:
Encryption key length mismatch. Disconnecting Neighbor <router name>.
|Keysize Mismatch between two TTM Wan Routers|
Locally configured encryption key length does not match negotiated value. Using key size <Remote Host Daemon Setting>.
|Keysize Mismatch between the Remote Client and Remote Host Daemon||Warning|
Encryption algorithm <cipher name> mismatch. Disconnecting Neighbor <router name>.
|Encryption Algorithm Mismatch between two TTM Wan Routers|
Locally configured encryption algorithm does not match negotiated value. Using algorithm <Remote Host Daemon setting>.
|Encryption Algorithm Mismatch between the Remote Client and Remote Host Daemon||Warning|
Neighbor <router name> expects encryption, but local router does not. Disconnecting.
|Encryption_enabled is set to false on this WAN Router, but to true for the neighbor.|
Neighbor <router name> does not expect encryption, but local router does. Disconnecting.
|Encryption_enabled is set to true on this WAN Router, but to false for the neighbor.||Error|
Could not open RSA private key file.
Local certificate failed verification. Please contact your Certificate Authority.
Initialization of Encryption Context failed. Encrypted communication is not possible.
|Encryption_enabled is set to false on the Remote Host Daemon but true on the Remote Client||Error|
Encryption algorithm 3DES does not support key size other than 256 bit.
|The encryption_algorithm is 3des, but the encryption_key_length is not 256.||Error|
Certificate for <certificate name> failed to verify: Error verifying certificate: certificate has expired.
The local certificate has expired
Local certificate for <certificate name> will expire in 14 days or fewer. Expiry date: <date string>. Please contact your Certificate Authority for renewal.
|Certificate will expire in 14 days or less|
Invalid message received during Encryption STS handshake (pre-2.1.2 client trying to connect?). Encryption is enabled on this remote daemon, but it does not appear the client has encryption enabled. Disconnecting
A client using TTM 2.1.1 or earlier attempted to connect to a daemon that uses encryption.
Proxy client advertising HALF STS
A client is connected and encrypted using Anonymous Authentication and Encryption (half STS).
Proxy client attempting to login with no encryption parameters while XTRH is configured for encryption only. Disconnecting!
A 3.1.X or 3.2.0 client that does not have encryption parameters is trying to connect to a 4.2.2 or later Remote Host that is configured for encryption and has allow_insecure_connections disabled.
Proxy client advertising FULL STS while this is not supported. Disconnecting!
A 3.1.X or 3.2.0 client that has encryption enabled is trying to connect to a 4.2.2 or later Remote Host.
Proxy client attempting to login unencrypted, connection will be unencrypted.
A 3.1.X or 3.2.0 unencrypted client is connecting to an encrypted 4.2.2 or later Remote Host that has allow_insecure_connections enabled. The result is an unencrypted connection.
Proxy client advertising HALF STS, encryption is disabled. Disconnecting!
A 4.2.2 or later client that has encryption disabled is trying to connect to a 4.2.2 or later Remote Host.
Log File Entry: UDD Statistics Messages
When UDD (Unrecovered Dropped Data) packets are detected, TTM adds a message to the ttmd.log file.
Date Time INFO: Udd: <IP>=<UDD>
Date / Time
Date and time of the logged data in the format:DD/MM/YYYY HH.MM.SS.sss
|Severity||Message Severity||The severity for the message.|
|Udd||Unrecovered Dropped Data||Lists the total number of UDD packets sent from the listed IP address. If there are no UDD packets, this message will not appear.|
Log File Entry: Base Filtering Engine Enabled
TT requires you to disable the Base Filtering Engine (BFE) Windows service when TTM is installed on Windows Vista, Windows 2008 Server, or Windows 7. Failing to disable this service so allows Windows to block all PGM traffic.
If the Base Filtering Engine (BFE) Windows service is enabled, TTM adds the following error message to the ttmd.log file:
ERROR: Base Filtering Engine detected, no PGM traffic will be received by TTMD.
For more information about recommended and required server and client settings, refer to the Trading Technologies Hardware/Software Optimizations and Recommendations Reference Guide.