Get answers to frequently asked questions i.e. “Now that we have our sensors or agents onboarded what's next?” “What tests should be configured on UXI sensors and agents?”
When developing a plan, the UXI Team recommends working right-to-left when looking at the dashboard.
Identify WHAT business-critical applications need to be tested (external tests). Don’t only think about current applications, plan for any new applications requiring support in the future coming quarters.
If using Aruba Central or a tool monitoring from the core of the network, possibly identify the top applications being used per site. This way the testing mimics the local environment.
What services need to function at the company site/branch to run those applications (internal tests)?
How are these networks onboarded at those locations (authentication/captive portals/firewalls)?
What is the existing troubleshooting or monitoring workflow? Sensor grouping should best mimic that environment, so NOC or other business groups best understand. Also, keep in mind this could change as UXI further integrates into the organization and additional business units make use of the data.
Keep in mind each sensor on average could run approximately 20,000 tests per day. The data generated as a result could have many different businesses uses. Make use of “Data Push Destination” if possible.
Enabling a weekly report (now customizable) is also a great way to see the high level of life for users is better week over week.
Consider the following best practices while configuring networks:
It is recommended to use open networks like Guest SSID or an open VLAN ethernet network just to onboard the sensor so that you can get started onboarding sensors and test configurations easily.
Sensor onboard and test up to 4 networks (SSIDs/VLANs). UXI supports enterprise-grade authentication on wireless and wired networks like WPA2-PSK, EAP-TLS, SCEP, etc.
It’s suggested if there is a captive portal on SSID enable the captive portal recording feature using the Aruba UXI recorder (chrome extension) and reach out to the UXI support team to upload the recording onto the network with the captive portal.
For proxy-configured networks (like Zscaler) either upload a PAC URL or PAC file or manual setting. Otherwise, an "Unexpected captive portal or proxy" issue will alert on sensors. Opening issue triage and examining the HTML file will determine the proxy's presented page.
While configuring a wired network make sure not to double-tag a VLAN ID on sensors. For example, if there is access or a trunk port with native VLAN X on the switch port and the tag VLAN X is configured on the sensors network settings it will cause double tagging. In such scenarios, the UXI team recommends leaving the VLAN ID field blank by turning the toggle off for Specify VLAN.
Consider the following best practices while configuring tests:
“Legacy Groups” are for creating test groups, while “Groups” are for creating geo-location-based graphical representations of sensors on the main dashboard page.
Sensors support all test types offered. Something to keep in mind; the greater number of internal and external tests added to the sensor/legacy group, the longer the test cycle duration. A maximum of 20 tests per sensor typically creates an acceptable test cycle duration. Often it is recommended when planning what to test, to start from the right side of the dashboard – what applications are critical, what is required to be working optimally to run those applications, and what networks need to be tested.
UXI agents do not support Web Application Tests or any kind of throughput tests. Be aware while configuring tests on agents only ping, web server, and voice quality tests are supported on agents. Creating a “Legacy Group” dedicated to UXI agents makes it simple to configure the correct tests for UXI agents.
Some customers also consider configuring the testing legacy group for some ad-hoc changes when troubleshooting or quickly reviewing new tests that need to be added on certain test sensors or test beds of sensors temporarily.
Distribute the tests evenly among a fleet of sensors or groups. This way the round-robin testing cycle is somewhat equal across all groups.
Utilize the “Filter” icon for quick reviewing/troubleshooting of groups, sensor state, or network issues.
When setting up “Webserver Tests” it’s important to select the correct protocol (TCP/ICMP ping) as sensors NOW raise an issue if there is an ICMP ping failure.
Make use of the “Internal” and “External” test types. “Internal” tests are test types of devices/applications internal to organizations like printers or scanners or Intranet websites. “External” tests are for cloud or Internet-facing applications or a web server like services. “Pre-defined” tests are well-known applications and “Custom” tests are configured specifically to your organization's tests.
The following sheet explains a few questions that you should consider while setting up the tests:
Wireless and Wired network setup collection: https://help.capenetworks.com/en/collections/244256-wireless-and-wired-networks
Authentication on wired and wireless networks: https://help.capenetworks.com/en/collections/1839605-authentication
UXI Testing collection: https://help.capenetworks.com/en/collections/244230-testing
Adding sensors - Groups & Hierarchy: https://help.capenetworks.com/en/articles/3134346-onboarding-adding-sensors-groups-hierarchies-3
Onboarding Testing: https://help.capenetworks.com/en/articles/3134373-onboarding-testing-4
Groups & Sensors: https://help.capenetworks.com/en/articles/6454788-groups-sensors