Configure network with console menu

Use the connector VM console menu to perform network configuration tasks.

Perform network configuration tasks in VMware or VirtualBox environments with the connector console.

  1. Open the console of the connector. If the screen is blank, press any key to bring it back.
    Connector is fully operational message appears.

  2. Follow the instructions on the screen and press ALT+F3 (Windows) or FN+ALT+F3 (MacOS).
    Connector VM network configuration console menu appears.

  3. Select an option from the console menu and enter the required information to perform network configuration task.

👍

These tasks apply only to connectors installed in VMware or VirtualBox environments.

Console menu optionTaskMore info
1) Configure Static IPv4 AddressAssign a static IP address to a connectorEnter a static IP, netmask, gateway and DNS server for this connector. Next, select 5).
2) Configure DHCPConfigure DHCP for a connectorIn Configuring DHCP. Proceed? type y. Next, select 4).
3) Configure DNS ServerConfigure a DNS configuration server to a connectorEnter the DNS server address. Connector points to a new DNS server, and pings google.com and the mgmt.bubblewrapp.net to ensure connectivity. Next, select 4).
4) Print Current IPv4 ConfigurationCheck connector connectivityNote the connector's IP address, netmask, gateway, DNS settings, and proxy configuration. Next, select 5).
5) Check Reachability To CloudVerify connectivityThe connector uses www.google.com and mgmt.stage.bubblewrapp.net to ensure connectivity.
6) Start SSH ServerStart the SSH serverMessage about SSH start and a process number appears.
7) Stop SSH ServerStop the SSH serverMessage about SSH stop and that no process was found appears.
8) Configure HTTP/HTTPS Proxy InformationConfigure a forward proxy serverType y, enter the URL, and port number for the forward proxy (for example, http://192.162.1.1:3128). Connector uses the new forward proxy server, and use Enterprise Application Access and pings google.com to ensure connectivity.
9) Unset HTTP/HTTPS Proxy InformationUnset a forward proxy serverType y. The forward proxy is unset and the service is restarted with a new IP configuration. After configuration change, it pings www.google.com and mgmt.bubblewrapp.net to ensure connectivity.
10) Reject Remote Debug ChannelDisable remote debuggingKeep remote debugging disabled by default.
11) Accept Remote Debug ChannelEnable remote debuggingEnable to solve connector issues with support. Next, select 10).
12) Set Forward Proxy EnabledEnable a forward proxyIn Configuring Set Forward Proxy. Proceed? type y. Connector establishes a connection to the applications behind the forward proxy.
13) Set Forward Proxy DisabledDisable a forward proxyIn Configuring Unset Forward Proxy. Proceed? type y. Connector disables a connection to the applications behind the forward proxy.
14) Specify NTP ServerConfigure an NTP serverIn Configuring NTP Server. Proceed? type y. In Specify NTP server name enter the server name.
15) Reset NTP Config To DefaultReset the NTP configuration to the default serverIn Configuring NTP Server To Default. Proceed? type y.
16) ExitLeave the console menu

Assign a static IP address to a connector

  1. Go to the connector console. If the screen is blank, press any key to bring the text back up. An operational status message appears for the connector.

  2. Pressing ALT+F3 (for Mac users: FN+ALT+F3 ).

  3. Select 1) Configure Static IPv4 Address.

  4. Follow the prompts and enter a static IP, netmask, gateway and DNS server for this connector.

  5. Once complete, press Esc to return to the configuration menu.

  6. Verify connectivity. Select 5) Check Reachability to Cloud.

Configure a DHCP address for a connector

DHCP is a network protocol used to assign dynamic IP addresses and provide configuration information to devices such as servers and others so they can communicate on a network using the Internet Protocol (IP).

  1. Open the connector console. If the screen is blank, press any key to bring it back. An operational status message appears for the connector.

  2. Press ALT+F3 (for Mac users: FN+ALT+F3 ).

  3. Select 2) Configure DHCP.

  4. When prompted at Configuring DHCP. Proceed? enter y.

  5. Once complete, press Esc to return to the configuration menu.
    Now that the connector has an IP address it will ping google.com and the EAA service to ensure connectivity.

  6. Select 4) Print Current IPv4 Configuration to verify the IP configuration and that the connector has been assigned an IP address.

Configure a DNS server for a connector

This procedure only applies to connectors installed in VMWare or VirtualBox environments.

  1. Open the console connector. If the screen is blank, press any key to bring it back. An operational status message appears for the connector.

  2. Press ALT+F3 (for Mac users, FN+ALT+F3 ).

  3. Select 3) Configure DNS Server.

  4. When prompted, enter the DNS server address and press Enter.
    Your connector is now pointing to a new DNS server. It will ping google.com and the EAA service (mgmt.bubblewrapp.net) to ensure connectivity.

  5. Once complete, press Esc to return to the configuration menu.

  6. Select 4) Print Current IPv4 Configuration to verify the IP configuration and that the DNS server address is the one you entered.

Check connector connectivity in the connector console

If your connector fails to check-in to Enterprise Application Access after five minutes, there may be a problem with it's networking dynamic host configuration protocol (DHCP) configuration or an outbound connection through your firewall or forward proxy.

  1. Go to the Connector Console. Press ALT+F3 (for Mac users: FN+ALT+F3 ).

  2. Select 4) Print Current IPV4 Configuration.
    Note the connector's IP address, netmask, gateway, DNS settings, and proxy configuration.

  3. Once complete, press Esc to return to the configuration menu.

  4. Verify connectivity. Select 5) Check Reachability to Cloud.

In Enterprise Center, the connector status for the connector changes to Connector is running.

If connectivity continues to fail, contact support.

Accelerate connector connectivity time with the cloud

Make sure that the connector VM can reach the Internet and the Akamai cloud. To confirm reachability:

  1. Go to the Connector Console. Press ALT+F3 (for Mac users: FN+ALT+F3 ).

  2. To verify your IP and DNS configuration in the connector console select 4) Print Current IPV4 Configuration.

  3. Once complete, press Esc to return to the configuration menu.

  4. To verify connectivity select 5) Check Reachability to Cloud. The connector 'uses www.google.com' and 'mgmt.stage.bubblewrapp.net' to ensure connectivity.

  5. Press Esc to return to the configuration menu.

📘

If your connectors run within Amazon, make sure the connector instance is configured with the correct security policies to allow outbound traffic to any IP for port 443.

Configure a forward proxy server for a connector

Depending on your network configuration, you may need to route all external communication to or from a connector through a forward proxy server.

  1. Go to the connector console. If the screen is blank, press any key to bring up the opening screen.

  2. Press ALT+F3 (for Mac users: FN+ALT+F3 ).

  3. Select 8) Configure HTTP/HTTPS Proxy Information.

  4. At the prompts, enter y and the URL and port number for the forward proxy (for example, http://192.162.1.1:3128).

Your connector now uses the new forward proxy server. It will ping google.com and use Enterprise Application Access to ensure connectivity.

Enable or disable remote debugging

Enable or disable remote debugging on Enterprise Application Access (EAA) from a connector console to run diagnostics.

  1. An operational status message appears for the connector. If this screen is blank, press any key to bring it back.

  2. Go to the Connector Console. Press ALT+F3 (for Mac users: FN+ALT+F3 ).

  3. Select 11) Accept Remote Debugging.
    After resolving the issue, select 10) Reject Remote Debug Channel to disable it again, which is the default value. Remote debugging must be disabled unless you are working with support to solve connector issues.

  4. Go to the Connector Console. Press ALT+F3 (for Mac users: FN+ALT+F3 ).

  5. Select 11) Accept Remote Debugging.
    After resolving the issue, select 10) Reject Remote Debug Channel to disable it again, which is the default value. Remote debugging must be disabled unless you are working with support to solve connector issues.


Did this page help you?