Aruba Central Online Help
You are here: Home > All Clients > Client Details > Client Live Troubleshooting

Client Live Troubleshooting

Aruba Central (on-premises) allows you to troubleshoot issue related to client at both client device level and site level in real time for detailed analysis. Live troubleshooting is supported only if the wireless client is connected to the access point running Aruba Instant 8.4.0.0 or a later version. You can also enable packet capture during live troubleshooting and download the PCAP file if the access point is running Aruba Instant 8.6.0.5 or a later version.

The live troubleshooting can only be performed at a site level or for a specific client.

Live Events are supported only on Instant APs.

Troubleshooting a Client

To troubleshoot a client at a site level, perform the following steps:

  1. In the Network Operations app, set the filter to one of the options under Sites that contains at least one device.

    The dashboard context for the selected site is displayed.

  2. Under Analyze, click Live Events.

    The Live Events page is displayed.

  3. Enter the MACMedia Access Control. A MAC address is a unique identifier assigned to network interfaces for communications on a network.  address of the client and click Start Troubleshooting.

To troubleshoot a wireless or wired client, perform the following steps:

  1. In the Network Operations app, 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.

  2. Under Manage, click Clients.

    The clients overview page is displayed in List view.

  3. By default, the Clients table displays a unified list of clients.
  4. Click the name of the wireless or wired client to open the corresponding Client Details page. If there are many clients connected to the network, click Wireless or Wired to filter the clients connected to the wireless or wired client respectively.
  5. Enter the client name in the Client Name column, and then click the client name.
  6. Under Analyze, click Live Events.

    The Live Events page is displayed.

The client live troubleshooting starts automatically for the selected client.

The status of the troubleshooting is displayed every minute. The troubleshooting session runs for a duration of 15 minutes. You can stop live troubleshooting at any point by clicking Stop Troubleshooting and to go back to the historical view.

After the live troubleshooting session ends, the details of the events are displayed in the live events table.

Live Events Details

The following details are captured and displayed in the Live Events table:

  • Occurred On—Displays the timestamp of the event. Use the filter option to filter the events by date and time.
  • Device Name—Displays the name of the device the client is connected to. Set the filter to select a specific device under Site.
  • Device Type—Displays the type of device the client is connected to.
  • Category—Displays the category of the event. Use the filter option to filter the events by category.
  • Description—Displays a description of the event. Use the filter option to filter the events based on description.

Packet Capture

Aruba Central (on-premises) allows you to interact and launch a targeted packet capture on a client connected to a specific access point. After you start packet capture from the UI, Aruba Central notifies the access point and the switch. The default packet capture duration is 15 minutes. After you start packet capture, use the toggle button to stop packet capture, or go back to the Client Overview page.

Starting Packet Capture

You can start packet capture from the wireless or wired clients page. Packet capture can be done at a site level (wireless client only) or for a selected client.

To start packet capture at a site level, perform the following steps:

  1. In the Network Operations app, set the filter to a Site that contains at least one device. The dashboard context for the selected site is displayed.
  2. Under Analyze, click Live Events.The Live Events page is displayed.
  3. Enter the MAC address of the client.

    At a site level, Aruba Central (on-premises) does not support packet capture for a wired client connected to a switch.

  4. Enable the Packet Capture toggle button to start live packet capture for the selected client.
  5. Click Start Troubleshooting.

To start packet capture for a wireless or wired client, perform the following steps:

  1. In the Network Operations app, 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.

  2. Under Manage, click Clients. The clients overview page is displayed in List view.
  3. By default, the Clients table displays a unified list of clients.
  4. Click the name of the wireless or wired client to open the corresponding Client Details page. If there are many clients connected to the network, click Wireless or Wired to filter the clients connected to the wireless or wired client respectively.
  5. Enter the client name in the Client Name column, and click the client name.
  6. Under Analyze, click Live Events. The Live Events page is displayed. The client live troubleshooting starts automatically for the selected client.
  7. Click Stop Troubleshooting to stop live troubleshooting.
  8. Enable the Packet Capture toggle button to start live packet capture for the selected client.
  9. Click Start Troubleshooting to live troubleshoot the selected client. Live packet capture starts for the selected client.

    The live troubleshooting session runs for a duration of 15 minutes. After the live troubleshooting session ends, a Download PCAP text appears above the live events table. Click Download PCAP to download the generated pcap file on your local system.

Packet capture can only be enabled or disabled before live troubleshooting is started. You cannot enable or disable packet capture while a live troubleshooting session is in progress.

Packet capture is not supported in single node deployments.