Troubleshooting Edge Gateway Connectivity

This document provides information about using the Edge Gateway’s command-line interface and troubleshooting common connectivity issues.

Using the Edge Gateway’s Command Line Interface

You can connect to the 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.

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.

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”.

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 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 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:

Connect to the Edge Gateway’s Command Line Interface CLI) or Console.
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 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.

In Aviatrix CoPilot, go to Cloud Fabric > Edge > Gateways tab.
In the table, locate the Edge Gateway and click its Edit icon on the right.
In the Edit Edge Gateway dialog box, scroll to Interface Configuration section, and click MGMT.
Update the Egress CIDR with the correct Public IP.
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.