Endpoint dial logs is a new feature launched in March 2023 on CloudZiti. The feature is aimed to provide details for troubleshooting failures in service dials and also for detailed logging.
The dial logs of an endpoint can be accessed via the endpoint details against each endpoint in the endpoints table of the console. This feature is supported currently for services hosted by ERT ( Edge Router Tunneler)
The dial logs provide details of services dialed by the endpoint along with the status of the dial - success / failure along with the reason for failure.
Terminator Remote - is the ip/port of the hosting application
Terminator Local - is the ip/port on the Edge Router used to make the outbound connection
If hosting application is co-hosted with the ER, then local and remote IP address would be the same - example SSH service to the ER
The following table lists the circuit errors, failure cause and the description.
|
Error |
Failure Cause |
Description |
|---|---|---|
|
CircuitFailure InvalidService |
INVALID_SERVICE |
The service identity given to the controller in the connection request is not found in the controller's configuration database. The endpoint has gotten out of sync with the controller, most likely due to very near-term changes, or failure of the client software to properly process service changes.
|
|
CircuitFailureId GenerationError |
ID_GENERATION _ERR |
The circuit identity generation function has failed to generate and return a circuit identity string |
|
CircuitFailure NoTerminators |
NO_TERMINATORS |
The service requested in the connection request has no terminators. This is normally indicative of a hosting device having lost connection to the network, either due to process, network, or power issues. The controller is unable to create a path. |
|
CircuitFailure NoOnlineTerminators |
NO_ONLINE_ TERMINATORS |
The only terminators in the controller network map are hosted by routers that are currently in an offline state. |
|
CircuitFailure NoPath |
NO_PATH |
During the routing evaluation, no path was calculable between the initiating and terminating devices. |
|
CircuitFailure PathMissingLink |
PATH_MISSING _LINK |
There is no set of links that can create a valid path from the initiating router to the terminator. This may be caused by link failures, router failures, or policies that preclude certain paths. |
|
CircuitFailure InvalidStrategy |
INVALID_STRATEGY |
There are multiple routing strategies allowed, though at this time, only smart routing is in use. This failure would indicate that a service has a routing strategy defined that the controller is unaware of. |
|
CircuitFailure StrategyError |
STRATEGY_ERR |
This would indicate that the service's defined routing strategy returned an error not otherwise captured |
|
CircuitFailure RouterErrGeneric |
ROUTER_ERR_ GENERIC |
Failure on route creation not otherwise captured |
|
CircuitFailureRouter ErrInvalidTerminator |
ROUTER_ERR_ INVALID_TERMINATOR |
The service requested in the connection request has no online terminators. This is normally indicative of a terminator state problem, where the controller believes there is a valid terminator, however, the device hosting that terminator has responded that the terminator is not valid |
|
CircuitFailureRouterErr MisconfiguredTerminator |
ROUTER_ERR_ MISCONFIGURED _TERMINATOR |
The returned data object for the terminator is not correctly formatted or otherwise unusable, resulting in an inability of the system to properly utilize the terminator to create a fabric circuit |
|
CircuitFailure RouterErrDialTimedOut |
ROUTER_ERR_DIAL _TIMED_OUT |
The dial (connection) from the terminating host to the socket configured for the service experienced a timeout when attempting to connect. This is most likely caused by a routing or service issue preventing the TCP or UDP connection from the hosting device to the configured service definition. |
|
CircuitFailure RouterErrDialConnRefused |
ROUTER_ERR_ CONN_REFUSED |
The dial from the terminating host to the socket configured for the service received a TCP reset (RST) packet when attempting to connect. This is most likely caused by a routing or service issue preventing the TCP or UDP connection from the hosting device to the configured service definition. |