> ## Documentation Index
> Fetch the complete documentation index at: https://docs.aviatrix.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Troubleshooting Edge Gateway Connectivity

> This document provides information about using the Aviatrix Edge Gateway's command-line interface to troubleshoot common connectivity issues.

This document provides information about using the Aviatrix Edge Gateway's command-line interface to troubleshoot common connectivity issues.

## Using the Edge Gateway's Command Line Interface

You can connect to the Aviatrix Edge Gateway's command-line interface (CLI) or console and use the Clish commands below to change the password, show gateway diagnostics, and troubleshoot Edge Gateway connectivity.

<Note>
  Once the Edge Gateway registers with the Aviatrix Controller, the password for the CLI login changes to the Management IP address of the Edge Gateway.
</Note>

| **Command**                           | **Description**                                                                                                        |
| ------------------------------------- | ---------------------------------------------------------------------------------------------------------------------- |
| change\_console\_password             | Changes the password for the CLI login.                                                                                |
| check\_conduit                        | Check conduit state.                                                                                                   |
| check\_network \[dns]\[reachability]  | Troubleshoot network connectivity.                                                                                     |
| diagnostics                           | Show gateway diagnostics.                                                                                              |
| logout                                | Log out of the console.                                                                                                |
| ping \[-c count] \[dest]              | Ping destination, optional parameter ping packet count. The default is 5.                                              |
| reboot                                | Reboot the system.                                                                                                     |
| set\_controller\_ip \[controller\_ip] | Set the Controller IP address, usually performed after Controller migration when the Controller IP address is changed. |
| show\_interfaces                      | Show output from the command "ifconfig -a more".                                                                       |
| show\_routes                          | Show output from the command "ip route show table all".                                                                |

## Diagnosing and Resolving Edge Gateway Connectivity Issues

After you deploy an Aviatrix Edge Gateway, the Edge Gateway registers with the Aviatrix Controller. The registration process takes about five minutes.

If the registration is successful, the Edge Gateway status changes from *Waiting* to *Up*.

If the registration fails, it is because the Edge Gateway is unable to communicate with the Aviatrix Controller.  You could use the **diagnostics** Clish command to diagnose the network connectivity.

## Updating the Controller IP for Edge Gateways when Controller IP Changes

If the Aviatrix Controller IP has changed, you must manually update the Controller IP configuration on the Aviatrix Edge Gateways that are connected to the Controller. Otherwise, the Edge Gateways may not be able to communicate with the Controller.

To update the Controller IP configuration on the Edge Gateway:

1. Connect to the Edge Gateway's command-line interface (CLI).

2. Run the following Clish command:

   **set\_controller\_ip** `<new_controller_ip_address>`, where `new_controller_ip_address` is the IP address of the new Controller.

## Verifying the Management CIDR Configuration

One common reason the Aviatrix Edge Gateway is unable to communicate with the Aviatrix Controller is the MGMT CIDR is incorrect. You could use the Edge Gateway's command-line interface and run the **check\_network** Clish command to view if the Edge Gateway can reach the Controller.

Ensure that the correct MGMT CIDR is configured for the gateway.

1. In Aviatrix CoPilot, go to **Cloud Fabric > Hybrid Cloud > Edge Gateways** tab.
2. Click **Spoke Gateways** or **Transit Gateways**.
3. In the table, locate the Edge Gateway and click its Edit icon on the right side of the row.
4. In Edit Edge Gateway, click **Next** to go to **Interface Configuration**.
5. Click **MGMT**.
6. Update the **Egress CIDR** with the correct public IP.
7. Click **Save**.

## Verifying Edge Gateway Access in the Controller Security Group

In the Aviatrix Controller's Security Group, ensure the security group rule allows access to the Controller's HTTPS port from the Management Egress CIDR of the Edge Gateway.