F5 BIG-IP SSL Orchestrator Training Lab > SSL Orchestrator v7 - SSLO 201: Real World Use Cases / Putting It to Use (Agility | 2 hours) > 3. Understanding SSL Orchestrator logging Source | Edit on
3.6. Local Traffic logging¶
While not the primary log destination for SSL Orchestrator some pertinent information may be logged to the Local Traffic log (/var/log/ltm). Log messages concerning pool and pool member availability (i.e. security service availability) and SSL/TLS handshake errors will appear in this log file and may help you ascertain why a particular connection (or multiple connections) are failing.
An example of an SSL handshake failure can be seen in the example below:
May 4 14:05:35 sslo1 warning tmm2: 01260013:4: SSL Handshake failed for TCP 10.1.10.50:61863 -> 184.108.40.206:443
While not overly descriptive on its own, this message indicates that either the client-side (client to SSLO) or server-side (SSLO to server) SSL/TLS handshake was unsuccessful. This can be due to a number of reasons, such as a handshake timeout or negotiation failure. To troubleshoot this further, an administrator may refer to K15292: Troubleshooting SSL/TLS handshake failures for next steps.