Token migration errors
After you run the Token Migration Utility (TMU), check the log in the logs subdirectory for errors. If it contains any of the following error messages, complete the troubleshooting steps before you run the utility again.
- Cache at {address:port} is not responsive. The proxy may be down or using an incorrect remote port.
-
The proxy to either the QES or gateway-peering token cache is not responsive. The gateway might be down or the cache might be unreachable.
- Verify that the proxy ports specified in
config.json
are not used by another service. - If the DataPower Gateway is in a container, verify that the ports specified in
v10-cache-proxy-port
,v5-cache-proxy-port
, or both, are exposed in the container. The exposed container ports must be specified inv10-cache-container-port
,v5-cache-container-port
, or both. - Verify that the correct host interface (IP address) is selected for the cache proxy at runtime.
- If the v5 QES is unresponsive, check the following settings.
- Verify that the v5 QES uses the default address and that it is enabled.
- Check the logs in debug mode and search for a line that contains
Making TCP Proxy with URL
. If the log contains this line, check for an error that explains why the TCP proxy was not created. If the error is present, fix the error to allow the proxy to connect to the QES, then run the TMU again. - If the log contains the line
Making TCP Proxy with URL
but there is no error, verify that there is a TCP proxy service configuration called TMUProxyForMigration. The remote IP address and remote port must be set to the QES default address and port. If necessary, modify the proxy configuration with correct information to connect to the QES, and then run the TMU again. If TMUProxyForMigration does not exist, create it and configure it to connect to the QES, and then run the TMU again.
- If the v10 gateway-peering token cache is unresponsive, check the following configuration settings.
- Verify that the gateway-peering object is enabled and specified in
config.json
. - Check the logs in debug mode and search for a line that contains
Gateway peering info
. Verify that the information for the gateway-peering object is correct as specified inconfig.json
. - If TLS is disabled, check the logs in debug mode and search for a line that contains
Making TCP Proxy with URL
. If the log contains this line, check for an error that explains why the TCP proxy was not created. If this error is present, fix the error and then run the TMU again. - If the log contains the line
Making TCP Proxy with URL
but there is no error, verify that there is a TCP proxy configuration called TMUProxyForMigration in DataPower Gateway. The remote host and port must be set to the local host and port of the gateway-peering object. If necessary, modify the proxy with the correct information to connect to the gateway-peering object, and then run the TMU again. If TMUProxyForMigration does not exist, create it and configure it to connect to the gateway-peering object, and then run the TMU again. - If TLS is enabled, check the logs in debug mode and search for lines that contain
Making TLS Client Profile with URL
andMaking TLS Proxy with URL
. If the log contains these lines, check for an error that explains why the TLS client and TLS proxy were not created. Fix the error and run the TMU again. - If the log contains the lines
Making TLS Client Profile with URL
andMaking TLS Proxy with URL
but there is no error, verify that there is a TLS proxy configuration called TMUProxyForMigration and a TLS client profile configuration called TMUProfileForMigration in DataPower Gateway. The remote host and port of the proxy must be set to the local host and port of the gateway-peering object. If necessary, modify the configurations to connect to the gateway-peering token cache, and then run TMU again. If either the TLS proxy calledTMUProxyForMigration
or the TLS client profile calledTMUProfileForMigration
do not exist, create these objects, configure them to connect to the gateway-peering object, and then run the TMU again.
- Verify that the gateway-peering object is enabled and specified in
- Verify that the proxy ports specified in
- Failed to establish a connection with {address:port}.
-
The gateway may be down or the DataPower Gateway REST management interface may be down.
- Verify that the gateway and the REST management interface are up.
- Verify that the port in the message is the port of the REST management interface. If it is not,
modify the
v5-rest-management-interface-port
orv10-rest-management-interface-port
field inconfig.json
. - If the DataPower Gateway is in a container, verify that v5 and v10 REST management interface ports are exposed by the container that is mapped to the DataPower Gateway REST management interface.
- Could not get Gateway Peering information.
- The DataPower Gateway REST management interface could not retrieve gateway-peering information.
- Verify that the gateway-peering object specified in
config.json
is created and enabled in the chosen DataPower Gateway domain.
- Verify that the gateway-peering object specified in