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

# Verify the CoPilot Deployment and the Connectivity with Controller

> You are now successfully logged into CoPilot. To verify Copilot has connected successfully to your Aviatrix Controller, perform the following steps:

You are now successfully logged into CoPilot. To verify Copilot has connected
successfully to your Aviatrix Controller, perform the following steps:

1. From the CoPilot dashboard, confirm that you can see your resource inventory
   across all clouds in your multicloud network that is managed by Aviatrix
   Controller.

   <Note>
     The expected page load time in the CoPilot UI is less than 10 seconds. If
     you see significantly slower behavior, contact Support for assistance.
   </Note>

2. Confirm that the inventory tiles show the number and status of each of your
   managed resources and that the global location of your managed VPCs/VNets is
   represented on the geographic map.

3. After deployment, the CoPilot virtual machine ports 31283 and 5000 will be
   open for any IP (0.0.0.0/0). It is strongly recommended to remove the
   0.0.0.0 entry from the CoPilot security group for these ports and add
   entries for all of your gateway IP addresses as described in the next steps.

   <Note>
     In Controller 6.8, the CoPilot Security Group Management feature (From
     Controller User Interface, *SETTINGS > CoPilot > CoPilot Security Group
     Management*) is automatically enabled so this configuration is expected to
     be completed. This is only a verification step.
   </Note>

4. (Verify NetFlow Agent is enabled in Controller) To use the FlowIQ feature in
   CoPilot, ensure that the Controller is configured to forward NetFlow logs to
   CoPilot.

   <Note>
     In Controller 6.8, the CoPilot Netflow Agent feature is automatically
     enabled so this configuration is expected to be completed. This is only a
     verification step.
   </Note>

   a. Log in to Aviatrix Controller UI. b. Go to *SETTINGS > Logging > NetFlow
   Agent*. c. Use the static IP address of CoPilot as the Netflow server IP and
   UDP port 31283 (default, port is configurable). d. Use version 9. e. Click
   *EDIT OPTIONS* to enable the edit the Netflow Agent settings. Tick the
   Advanced check-box. In Gateways, verify all of your Aviatrix gateways are in
   the Include List. f. Click *Enable*.

   <Note>
     If you launch new gateways from your Controller later, you must transfer the newly launched gateways to the Include List here. In addition, in your native cloud console, you must open your CoPilot security group for UDP 31283 from each newly launched gateway.
   </Note>

5. (Verify Remote Syslog is enabled in Controller) Remote syslog index 9 is
   used for the *Settings > Logging > Remote Syslog* page. Ensure the
   controller is configured to specify CoPilot as the loghost server.

   <Note>
     In Controller 6.8, the CoPilot Security Group Management feature (in
     Controller > SETTINGS> CoPilot > CoPilot Security Group Management) is
     automatically enabled so this configuration is expected to be completed.
     This is only a verification step.
   </Note>

   a. Log in to Aviatrix Controller. b. Go to *SETTINGS > Logging > Remote
   Syslog*. c. Choose Profile Index 9. d. Click *EDIT OPTIONS* to edit the
   Remote Syslog settings. e. In Enable Remote Syslog, enter the profile name
   you want to use, the static IP address of CoPilot as the server, and UDP
   port 5000 (default). f. If you want to use custom certificates, choose your
   custom Server CA certificate, Client certificate, and Client Private Key. g.
   Tick the Advanced checkbox. In Gateways, verify all of your Aviatrix
   gateways are in the Include List. h. Click *Enable*.

   <Note>
     If you launch new gateways from your Controller later, you must transfer the newly launched gateways to the Include List here. In addition, in your native cloud console, you must open your CoPilot security group for UDP 5000 from each newly launched gateway.
   </Note>