Test connector connectivity to applications with troubleshooting tools
Before you begin:
- Make sure the EAA connector card status appears as running.
- Enable remote debugging for a connector. See Enable or disable remote debugging for a connector.
Note: If a connector is unreachable
or Remote Debugging is not enabled, the troubleshooting tools
are not visible for a connector.
The EAA connectors page includes common networking tools that allow an administrator to troubleshoot connectivity issues between a connector and its associated applications. Each tool includes a field where administrators can enter information. A terminal window is also embedded in the EAA user interface to show query results.
Each tool includes a field where administrators can enter information. A terminal window is also embedded in the EAA user interface to show query results.
Troubleshooting tool utility | Description |
---|---|
dig | Queries the DNS server and retrieves information about a hostname such as its resolvable IP address. |
Ping | Determines if the application host or IP address is reachable from the connector and available to accept requests. |
Traceroute | Tracks the route that IP packets take from the connector to the application host or IP address. |
LFT | Traces the route from the connector to the application host or IP address and retrieves additional routing and network information such as the autonomous system (AS) number and detected firewalls. |
cURL | Checks if the application URL is reachable from the connector. To troubleshoot application reachability issues, you can use cURL to execute GET and POST requests and inject or add headers to the request. |
Fiddler | A third-party tool that is useful for capturing HTTP/HTTPS traffic and saving as a log file to trace traffic issues. See Gather a Fiddler trace for more information. |