This article describes the steps required to perform network connectivity tests to ensure that the Broker has the necessary network access to deploy and manage workloads.
Please work with your network administrator to resolve any issues as a result of any failure of these tests.
Prerequisites
- Administrative access to the Admin Console UI
Performing a DNS Test
- Log in to the Admin Console UI
- Navigate to Network
- Select the Diagnostics tab
- Within the NSlookup function, enter a valid domain
- Click nslookup test
- Review the results to ensure that the test completes successfully
This is usually indicated by receiving a valid answer from the DNS server
Performing a Network Response Test
- Log in to the Broker Admin UI
- Navigate to Network
- Select the Diagnostics tab
- Within the Ping function, enter a valid domain
- Click ping test
- Review the results to ensure that the test completes successfully
This is usually indicated by successfully receiving response packets
- Repeat this test for the following:
- IP address of an internal resource
- IP address of an external resource
- FQDN of an internal resource
- FQDN of an external resource
Performing a HTTP Access Test
- Log in to the Broker Admin UI
- Navigate to Network
- Select the Diagnostics tab
- Within the Curl function, enter a valid domain
- Click curl test
- Review the results to ensure that the test completes successfully
This is usually indicated by receiving a HTTP 200 OK response
Note: The Broker appliance requires external connectivity to communicate with Buttonwood Services as well as cloud service providers. If curl tests fail, please reboot the appliance, validate proxy settings (if configured), and confirm firewall settings with the relevant networking/security teams.
- Repeat this test for the following:
- HTTP request to an internal web host
- HTTPS request to an internal web host
- HTTP request to an external web host
- HTTPS request to an external web host