Diagnosis

Zebra Wireless Insights Analysis Use Cases for Aruba UXI

Diagnosis

Select one of the failed devices. The following screen indicates the cause of the issue is

Unable to connect to telnet service

. Note that this coincides with

Roam failed

events around the same time.

1	Unable to connect to telnet service issue is ongoing
2	Roam failed events during that time

Select the event under

ONGOING

to view the Telnet failure details.

1	Time when problem was detected
2	Still ongoing

Return to the listed events and select one of the

Roam failed

instances.

The following screen shows that within the period of this instance, the device attempts to roam (to a better AP) due to a

Poor Coverage Area

caused by a poor signal combined with poor traffic (packets) performance, which can occur even during a period of successful connection.

Note that shortly prior to the roam, a

Connection Completed

event was followed by

ARP Failed

. This is another indication that in the same area, while the Wi-Fi connection is maintained, the ARP packet exchange with the network fails, corresponding to Telnet failing to send or receive data packets during very poor coverage.

Lastly, there is no evidence of a problem with the roam’s 802.11 management packets between the device and the AP, indicating that the roam occurred due to poor coverage, but was able to complete successfully with no issues. The problem is due to Layer 3 data packets.

1	ARP Failed while the device is connected.
2	The device tries to roam again to another AP due to the Poor Coverage Area . The device shows Roam Completed (Successful) but the new AP also creates a Poor Coverage Area condition (not shown), indicating the problem is recurring.