

# Reachability Analyzer additional detail codes
Additional detail codes

Reachability Analyzer uses additional detail codes to provide information about the result of a path analysis.

The following additional detail codes are supported.

**ASSUMPTION\$1PRESERVE\$1CLIENT\$1IP\$1IS\$1DISABLED**  
The analysis could not describe target group attributes for the target group, so the network path is based on the assumption that client IP preservation is disabled on the target group. You should verify this assumption.

**ASSUMPTION\$1PRESERVE\$1CLIENT\$1IP\$1IS\$1ENABLED**  
The analysis could not describe target group attributes for the target group, so the network path is based on the assumption that client IP preservation is enabled on the target group. You should verify this assumption.

**AVAILABILITY\$1ZONE\$1CROSSED**  
The network path crosses Availability Zones.

**FIREWALL\$1UNSUPPORTED\$1HIGHER\$1PRIORITY\$1RULE\$1GROUP\$1TYPE**  
There is at least one higher priority rule that could match the traffic in this path, but we ignored because it contains an unsupported rule type. Verify that the result of the analysis matches the behavior of AWS Network Firewall in your network.

**FIREWALL\$1UNSUPPORTED\$1HIGHER\$1PRIORITY\$1RULES**  
There is at least one higher priority rule that could match the traffic in this path, but we ignored because it contains an unsupported rule option. Verify that the result of the analysis matches the behavior of AWS Network Firewall in your network.

**FIREWALL\$1UNSUPPORTED\$1RULE\$1OPTIONS**  
The matching firewall rule contains an unsupported rule option. Verify that the result of the analysis matches the behavior of AWS Network Firewall in your network.

**MISSING\$1TARGET\$1GROUP\$1ATTRIBUTES**  
The target group attributes for the target were missing, so the analysis could not consider them.

**PATH\$1THROUGH\$1GWLB\$1NOT\$1CHECKED**  
The analysis does not consider that traffic entering the VPC endpoint is forwarded to a Gateway Load Balancer for inspection before exiting the VPC endpoint.

**RESPONSE\$1RTB\$1HAS\$1NO\$1ROUTE\$1TO\$1TRANSIT\$1GATEWAY**  
Traffic is routed from the transit gateway to the VPC endpoint. However, there is no route from the VPC endpoint to the transit gateway, so the network might drop the response traffic.

**TRANSIT\$1GATEWAY\$1APPLIANCE\$1MODE\$1RECOMMENDED**  
The transit gateway VPC attachment has [appliance mode](https://docs.aws.amazon.com/vpc/latest/tgw/how-transit-gateways-work.html#tgw-az-overview) disabled, but traffic is inspected through a Network Firewall. We recommend that you enable appliance mode for the VPC attachment.

**UNIDIRECTIONAL\$1PATH\$1ANALYSIS\$1ONLY**  
The results include forward path analysis from the source to the destination. There might be a blocking configuration in the reverse path, which could not be analyzed.