Aruba Central Online Help
You are here: Home > Using Troubleshooting Tools > Troubleshooting Network Issues > Controller Connectivity Issues

Troubleshooting Controller Connectivity Issues

The following tests are available to diagnose issues pertaining to controller network connections:

Ping Test

Sends ICMPInternet Control Message Protocol. ICMP is an error reporting protocol. It is used by network devices such as routers, to send error messages and operational information to the source IP address when network problems prevent delivery of IP packets. echo packets to the IP addresses of the selected devices to check for latency issues.

To perform a ping test on Controllers:

  1. In the Network Operations app, select one of the following options:
    • To select a group, label, site, or all devices in the filter, set the filter to one of the options under Groups, Labels, or Sites. For all devices, set the filter to Global.

      The dashboard context for the selected filter is displayed.

    • To select a device in the filter:
      1. Set the filter to Global.
      2. Under Manage, click Devices > Controllers.

        A list of controllers is displayed in the List view.

      3. Click a controller listed under Device Name for which you want to perform diagnostic test.

        The dashboard context for the controller is displayed.

  2. Under Analyze > Tools, click Network Check.
  3. From the Device Type drop-down list, select Controller.
  4. From the Test drop-down list, select Ping Test.
  5. From the Sources drop-down list, select source(s). You can select multiple Controllers.
  6. From the Destination Type drop-down list, select one of the following:
  7. To use additional parameters, click Show Additional Test Settings and enter values in the following fields:

    Show Additional Test Settings is not displayed when a Test type is not selected.

    1. In the Packet Size field, enter the packet size to capture and store the data packet to analyze network issues at a later stage. The range is from 10 to 2000 bytes.
    2. In the Count field, enter the count. The value should be between 1 to 1000.
    3. In the Time to Live field, enter the time range. The value should be between 1 to 225 seconds.
    4. In the DSCPDifferentiated Services Code Point. DSCP is a 6-bit packet header value used for traffic classification and priority assignment. field, enter the packet header value. The value should be between 0 to 63.
    5. From the Source Interface drop-down list, select one of the following:
    6. Optionally, you can select the Don't Fragment toggle button. This option is used when the packet size is more than the Maximum Transmission Unit (MTUMaximum Transmission Unit. MTU is the largest size packet or frame specified in octets (eight-bit bytes) that can be sent in networks such as the Internet.) size of the interface.

  1. Click Run. The output is displayed in the Device Output section.

Traceroute

Tracks the packets routed from a network host.

To perform a traceroute test on Controllers:

  1. In the Network Operations app, select one of the following options:
    • To select a group, label, site, or all devices in the filter, set the filter to one of the options under Group, Label, or Site. For all devices, set the filter to Global.

      The dashboard context for the selected filter is displayed.

    • To select a device in the filter:
      1. Set the filter to Global.
      2. Under Manage, click Devices > Controllers.

        A list of s is displayed in the List view.

      3. Click a controller listed under Device Name for which you want to perform diagnostic test.

        The dashboard context for the controller is displayed.

  2. Under Analyze > Tools, click Network Check.
  3. From the Device Type drop-down list, select Controller.
  4. From the Test drop-down list, select Traceroute.
  5. From the Sources drop-down list, select source(s). You can select multiple Controllers.
  6. Enter the hostname or IP address.
  7. To use additional parameters, click Show Additional Test Settings, and from the Source Interface drop-down list, select VLAN Interface.
  8. From the VLAN Interface drop-down list, select the required VLAN ID displayed along with the IP address.
  9. Click Run. The output is displayed in the Device Output section.

If you navigate from the device details page, the Tools page appears, where the device context is already set and the Source field is automatically populated based on your selection.

Speed Test (iPerf)

Performs a speed test to measure network speed and bandwidth. To perform a speed test, you must provide the iPerf server address, protocol type, and speed test options such as bandwidth.

To execute a speed test on Controllers:

  1. In the Network Operations app, select one of the following options:
    • To select a group, label, site, or all devices in the filter, set the filter to one of the options under Group, Label, or Site. For all devices, set the filter to Global.

      The dashboard context for the selected filter is displayed.

    • To select a device in the filter:
      1. Set the filter to Global.
      2. Under Manage, click Devices > Controllers.
      3. A list of access points is displayed in the List view.
      4. Click an access point listed under Device Name for which you want to perform diagnostic test.

        The dashboard context for the access point is displayed.

  2. Under Analyze > Tools, click Network Check.
  3. From the Device Type drop-down list, select Controller.
  4. From the Test drop-down list, select Speed Test (iPerf).
  5. From the Sources drop-down list, select source(s). You can select multiple Controllers.
  6. In the Host field, enter a valid hostname or IP address.
  7. To use additional parameters, click Show Additional Test Settings and enter values in the following fields:

    Show Additional Test Settings is not displayed when a Test type is not selected.

  1. Port—Select the port.
  2. VLAN Interface—Select the VLAN ID from the drop-down list.
  1. Click Run. The test output is displayed in the Device Output section.

For more information about viewing and downloading the output, see Viewing the Device Output.