The following Generic ARK for AWS Transit Gateway message catalog lists all messages that may appear during the use of Generic ARK for AWS Transit Gateway.
| Code |
Severity |
Message |
Cause/Action |
|---|---|---|---|
| 127001 |
ERROR |
Amazon describe-route-tables call failed $detail |
Cause: Failed to retrieve information from the routing table. Action: Verify that ec2:DescribeRouteTables is permitted. Also, ensure that the aws command is correctly installed and can connect to the service endpoint. |
| 127002 |
ERROR |
Amazon replace-route call failed $detail |
Cause: Failed to update the route table. Action: Verify that ec2:ReplaceRoute is permitted. Also, ensure that the aws command is correctly installed and can connect to the service endpoint. |
| 127003 |
ERROR |
Amazon describe-transit-gateway-vpc-attachments call failed $detail |
Cause: Failed to retrieve information about the Transit Gateway’s VPC attachment. Action: Verify that ec2:DescribeTransitGatewayVpcAttachments is permitted. Also, ensure that the aws command is correctly installed and can connect to the service endpoint. |
| 127004 |
ERROR |
Amazon describe-transit-gateway-route-tables call failed $detail |
Cause: Failed to retrieve information from the Transit Gateway route table. Action: Verify that ec2:DescribeTransitGatewayRouteTables is permitted. Also, ensure that the aws command is correctly installed and can connect to the service endpoint. |
| 127005 |
ERROR |
Amazon search-transit-gateway-routes call failed $detail |
Cause: Failed to look up the Transit Gateway route table. Action: Verify that ec2:SearchTransitGatewayRoutes is permitted. Also, ensure that the aws command is correctly installed and can connect to the service endpoint. |
| 127006 |
ERROR |
Amazon replace-transit-gateway-route call failed $detail |
Cause: Failed to update the Transit Gateway route table. Action: Verify that ec2:ReplaceTransitGatewayRoute is permitted. Also, ensure that the aws command is correctly installed and can connect to the service endpoint. |
| 127007 |
ERROR |
Amazon describe-transit-gateway-peering-attachments call failed $detail |
Cause: Failed to retrieve information about the Transit Gateway’s Peering attachment. Action: Verify that ec2:DescribeTransitGatewayPerringAttachments is permitted. Also, ensure that the aws command is correctly installed and can connect to the service endpoint. |
| 127008 |
ERROR |
Amazon describe-transit-gateway-vpc-attachments call failed $detail |
Cause: Failed to retrieve information about the Transit Gateway’s VPC attachment. Action: Verify that ec2:DescribeTransitGatewayVpcAttachments is permitted. Also, ensure that the aws command is correctly installed and can connect to the service endpoint. |
| 127009 |
ERROR |
Route for $ip is $route. It does not match $eni_id |
Cause: The virtual IP address on the route table has been updated to an unintended target. Action: It will be automatically restored via local recovery, so no action is required. |
| 127010 |
ERROR |
Failed to update route table $rt |
Cause: Failed to update the route table. Action: Verify that ec2:ReplaceRoute is permitted. Also, ensure that the aws command is correctly installed and can connect to the service endpoint. |
| 127011 |
ERROR |
There is no route for $ip in VPC $vpc_id |
Cause: There is no route table with a virtual IP address configured in the VPC. Action: Add the following route table entry to the main route table of the VPC where the local node is located. Destination: Virtual IP address Target: ENI of local node |
| 127012 |
ERROR |
No TransitGateway is attached to local VPC $vpc_id |
Cause: No Transit Gateway is attached to the VPC. Action: Attach the Transit Gateway to the VPC where the local node is deployed. |
| 127013 |
WARN |
TransitGateway attached from local VPC $vpc_id is more than 1 ($tgw_num). Using $tgw_id. |
Cause: Multiple Transit Gateways are attached to the VPC. Action: Attach only one Transit Gateway to the VPC where the local node is deployed. |
| 127014 |
ERROR |
No route table found for $ip in $tgw_id |
Cause: The virtual IP is not configured in the Transit Gateway route table. Action: Add the following route table entry to the Transit Gateway route table in the VPC where the local node is deployed. Destination: Virtual IP address Target: VPC attachment connecting to the VPC where the local node is located |
| 127015 |
ERROR |
Route for $ip is $route. It does not match $tgwa_id |
Cause: The virtual IP address on the route table has been updated to an unintended target. Action: It will be automatically restored via local recovery, so no action is required. |
| 127016 |
ERROR |
Failed to update route table $rt |
Cause: Failed to update the Transit Gateway route table. Action: Verify that ec2:ReplaceTransitGatewayRoute is permitted. Also, ensure that the aws command is correctly installed and can connect to the service endpoint. |
| 127017 |
ERROR |
Route for $ip is $route. It does not match $remote_tgw_id |
Cause: The virtual IP address on the route table has been updated to an unintended target. Action: It will be automatically restored via local recovery, so no action is required. |
| 127018 |
ERROR |
Failed to update route table $rt |
Cause: Failed to update the Transit Gateway route table. Action: Verify that ec2:ReplaceTransitGatewayRoute is permitted. Also, ensure that the aws command is correctly installed and can connect to the service endpoint. |
| 127019 |
WARN |
There is no remote region for $ip in VPC $vpc_id |
Cause: Not connected to another region. Action: Verify the Transit Gateway settings. |
| 127020 |
ERROR |
Route for $ip is $route. It does not match $remote_tgw_id |
Cause: Failed to update the Transit Gateway route table. Action: Verify that ec2:ReplaceTransitGatewayRoute is permitted. Also, ensure that the aws command is correctly installed and can connect to the service endpoint. |
| 127021 |
ERROR |
Failed to update route table $rt |
Cause: Failed to update the route table. Action: Verify that ec2:ReplaceRoute is permitted. Also, ensure that the aws command is correctly installed and can connect to the service endpoint. |
| 127022 |
WARN |
There is no route for $ip in remote VPCs |
Cause: There is no route table with a virtual IP address configured in the VPC. Action: Add the following route table entry to the main route table of the VPC where the remote node or client is located. Destination: Virtual IP address Target: The Transit Gateway attached to the VPC |
| 127023 |
ERROR |
Failed to get local region. |
Cause: Failed to retrieve region information from EC2 instance metadata. Action: Ensure that the instance metadata service is enabled in the EC2 instance settings for the cluster node. Verify that access to the instance metadata service IP address 169.254.169.254 is not blocked by the operating system firewall, security groups, or network access control lists (ACLs). Confirm the configuration of static routing for 169.254.169.254. |
| 127024 |
ERROR |
Failed to get local VPC Id. mac=$mac |
Cause: Failed to retrieve VPC information from EC2 instance metadata. Action: Ensure that the instance metadata service is enabled in the EC2 instance settings for the cluster node. Verify that access to the instance metadata service IP address 169.254.169.254 is not blocked by the operating system firewall, security groups, or network access control lists (ACLs). Confirm the configuration of static routing for 169.254.169.254. |
| 127025 |
ERROR |
Failed to get local ENI Id. mac=$mac |
Cause: Failed to retrieve Elastic Network Interface information from EC2 instance metadata. Action: Ensure that the instance metadata service is enabled in the EC2 instance settings for the cluster node. Verify that access to the instance metadata service IP address 169.254.169.254 is not blocked by the operating system firewall, security groups, or network access control lists (ACLs). Confirm the configuration of static routing for 169.254.169.254. |
| 127033 |
WARN |
No route table found for $ip in $remote_tgw_id |
Cause: The virtual IP is not configured in the Transit Gateway route table. Alternatively, an AWS outage may be preventing access to the Transit Gateway or the region where it is located. Action: Add the following route table entry to the Transit Gateway route table. Destination: Virtual IP address Target: Peering attachment connecting to the Transit Gateway in the VPC where the local node is deployed In the event of an AWS outage, wait for AWS to recover. |
| 127034 |
WARN |
_getMetadata for $item returns empty string. Retrying after $retry_interval micro secs. |
Cause: Failed to retrieve information from EC2 instance metadata. Action: It will automatically retry, so no action is required. |
| 127035 |
ERROR |
Failed to retrieve IP address from resource info. |
Cause: The resource information entered in the Application Information field during resource creation is empty, resulting in a failure to obtain the IP address. Action: Recreate the resource and ensure the virtual IP address is correctly entered in the Application Information field during creation. |
| 127036 |
ERROR |
Invalid IPv4 address format in resouce info ($ip) . |
Cause: The resource information entered in the Application Information field during resource creation is not a valid string for an IP address. Action: Recreate the resource and ensure the virtual IP address is correctly entered in the Application Information field during creation. |
| 127037 |
WARN |
Failed to get device name for $ip. We will use the first device found |
Cause: The device name could not be obtained from the IP address. The IP address may not be recognized by the operating system. Action: Ensure the IP resource is in the Active state. Verify that the dependency is created such that the Generic ARK for AWS Transit Gateway resource is the parent resource and the IP resource is the child resource. |
| 127038 |
WARN |
IMDS v2 failed to retrieve a secret token. (ret=$ret, err=$err) |
Cause: Failed to retrieve the secret token when obtaining information from EC2 instance metadata. Action: It will automatically retry, so no action is required unless another error message appears. If another error message appears, please take the necessary steps to address it. |
| 127039 |
WARN |
IMDS v2 failed to retrieve a secret token. The token is empty. |
Cause: When retrieving information from EC2 instance metadata, the secret token became an empty string. Action: It will automatically retry, so no action is required unless another error message appears. If another error message appears, please take the necessary steps to address it. |
| 127040 |
WARN |
curl call failed. (ret=$ret, err=$err)(output=@response) |
Cause: The curl command used to retrieve information from EC2 instance metadata terminated abnormally. Action: It will automatically retry, so no action is required unless another error message appears. If another error message appears, please take the necessary steps to address it. |
| 127041 |
WARN |
curl response error. (HTTP status=[$http_status], response=[@response]) |
Cause: When retrieving information from EC2 instance metadata, the HTTP response code returned an abnormal status code. Action: It will automatically retry, so no action is required unless another error message appears. If another error message appears, please take the necessary steps to address it. |
Post your comment on this topic.