Validating the configuration
You can run the get router info bgp neighbors <neighbor_IP> received-routes and get router info bgp neighbors <neighbor_IP> advertised-routes commands on the side office and spoke FortiGates to validate the configuration.
The following shows the desired output for the side office FortiGate:
The following shows the desired output for the spoke FortiGate:
To check the connected and BGP routes on the FortiGate, you can run the get router info routing-table all and get router info routing-table database commands. See Technical Tip: FortiGate BGP configuration to announce specific routes and accept only a default route (prefix list and route map).
Verifying site-to-site connectivity
You can verify site-to-site connectivity by pinging an application in remote site 2 from an application in remote site 2, and vice-versa. The following shows the desired output from a site 1 application instance:
The following shows the desired output from a site 2 application instance:
The following lists Google Cloud commands for deployment verification:
|
Resource |
Describe command |
Delete command |
|---|---|---|
|
Cloud router |
gcloud compute routers describe <cloud_router> --region=<region_name> Example: |
gcloud compute routers delete <cloud_router> --region=<region_name> |
|
Hub |
gcloud alpha network-connectivity hubs describe <ncc_hub> Example: |
gcloud alpha network-connectivity hubs delete <ncc_hub> |
|
Spoke |
gcloud alpha network-connectivity spokes describe <spoke_name> --region=<region_name> Example: |
gcloud alpha network-connectivity spokes delete <spoke_name> --region=<region_name> |