How do I add sensors to my dashboard?
For hardware sensors, first add them to the greenlake cloud platform device inventiry, then assign the sensors to the UXI service. These steps are detailed in steps 4 and 5 of the Getting Started guide.
Which network is the sensor using to connect to the cloud?
The sensor attempts to connect to the UXI cloud over an Ethernet network, then to any Wi-Fi network, and finally to mobile data if available, in that order, and will use the first online connection.
UXI Sensors Supports EAP-TLS
The certificate can be manually generated from your CA in PKCS12 format or obtained via SCEP.
How does the Sensor learn its location and then show it on the map?
We use Google's BSSID geolocation service with data we collect from sensor Wi-Fi scans. Please refer to links below for more details:
https://en.wikipedia.org/wiki/Wi-Fi_positioning_system
https://www.lifewire.com/wifi-positioning-system-1683343
What does "NA" mean in the test result charts?
In the dashboard, "n/a" simply means there is no data for that specific time period. In most cases this is expected as the sensor only has connecting lines between data points if there is data in consecutive time buckets. For more information, see the sensor test cycle and time navigation and test result charts.
"NA Screenshot"
UXI sensor tests WiFi association every 3 minutes but can we configure to keep it to connect WiFi? This test configuration seems not to be configured.
That is right. The core network test timings are not configurable. The sensor associates to a Wi-Fi SSID, conducts the core network tests serially (DHCP, DNS etc.) and then moves on to conducting internal and external application tests. Once this is done, the sensor disconnects and moves on to the next SSID. Hence, the time taken to test each SSID is at a minimum of 3 minutes but highly depends on the number of networks and applications it is testing. For more information, see the sensor test cycle
Laptops vs phones vs IOT devices all have different quality of antennas and power outputs. Do you think the UXI Sensor is comparable to the average laptop regarding the antenna quality and power or would it be more like an iphone? The reason I need to know is because the Cape graphs may look much better than what the average iphone user would experience in the same location.
The sensor is designed specifically towards the performance of a client device. There is no extra power, and it is not more sensitive than a client. The device should represent a phones performance fairly well in so far as RF characteristics are to do this we limited the receive sensitivity, and specifically did not use custom designed antennas. However, throughput measurements from the sensor will be lower than what you can usualy measure from a client due to the sensors rolling buffer packet capture capabilities.
How do I get a new user account started?
Provision UXI on your HPE Greenlake Cloud Workspace. Here is the Getting Started Guide.
Can I have multiple e-mail accounts in the "Alert e-mail address" field on the Alerts banner?
Each user needs to log in to his/her dashboard and enable/disable their user details under Settings -> Notifications. As this user, you can set the alternate email address to have the notification emails sent to an email alias. Please make sure to let the people of the alias know before you set this setting.
Does sensor perform user experience over wired connections also?
Yes, the sensor has an option to test the wired connections. Simply create a wired network and assign the network to the group the sensor is located in.
What are all the possible OUIs of the cape sensors?
These are the only two possible OUIs at the moment:
20:4C:03
40:ED:98 (sensors built before June 2018)
Can I see why the sensor is choosing a dedicated AP to connect to?
The sensor is a Linux client and acts like one. So when it would generally connect to the best available BSSID. This does not necessarily mean strongest signal strength. But could be a combination of various RF metrics. Unless you lock the sensor to a specific BSSID, the BSSID selection is a function of the Linux driver rather than that of device software. It will connect to whichever AP responds to the probe.
Is there anyway to run a report when you see errors reported-to be able to capture and review them? I'd like to run a report or gather data when i see an error or alert reported.
If a test failure occurs, the issue will be captured and will be displayed on the dashboard as an issue. The types of Issues are described here. Test failures also typically include packet captures as described here.
Can the sensor monitor its power inlet, in case it is connected to both DC and PoE?
The LTE sensor should never be plugged into two sources at the same time. The DC will be used in your case but the PoE circuit will keep switching on and off, which is why we don't allow users to use both power sources. When connected to a single source, the LTE sensor has a power back up using super capacitors for up to 45 seconds in which it phones home and informs that back end of the power loss. This creates an error on the dashboard which says “power outage detected” as opposed to generating a connectivity error. If the non-LTE sensor is unplugged from power then it will not send "power outage detected" so it will just go grey in dashboard.
When the sensor goes offline. If the sensor goes "grey" in the dashboard. Can I get an alert?
If the cellular sensor can self-report a power outage, then it will go red and the customer will get an alert. If the non-cellular sensor, or during the last gasp phase, the cellular sensor is not able to self-report a power outage, then the sensor will go grey, and the customer will not get an alert.
Can I remove SIM card in sensor and put my own in?
No, you can not. Right now we provide the mobile backhaul as a managed service. The installed SIM card in sensor forms part of this service.
Can tests be assigned to each group?
Yes, there is a help document on this topic here - https://help.capenetworks.com/en/articles/3404387-selecting-groups-and-networks-while-configuring-tests
Can UXI export test result data in CSV format?
Yes, you can download CSV file with test result and it will be forward to your email.
Select any sensor from the main dashboard and under all resolved and ongoing alerts you will find "Download Data" box.
Is it true that the ZAP test can be done only if the customer has a Iphone or an Ipad? and after they have installed a ZAP application there in the mobile or Ipad ?
The ZAP test is between the sensor and a compatible Ruckus access point, I believe the IoS/Android ZAP app performs the same actions as the UXI sensor, so the test IS NOT between the UXI sensor and a mobile phone / table. In order to configure a target / endpoint for the AP being tested must be a Ruckus access point.
Customer's main requirement is to initiate a packet from wired VLAN to UDP port number. Is this possible or not? Can they test UDP ports in custom test?
At the time of writing we do not have a UDP specific test, we have the generic test template which performs TCP and ICMP pings against a target but no UDP port tests. This can be requested as a use case here.
I understand that the time taken for core tests, internal and external test varies and it is based on many parameters such as network speed and number of networks and tests configured. However, is it possible to estimate the time taken for either the core test alone or the time taken per internal or external test?
Since the association is the first test that is performed, the best way to know how long the test cycles are is to look at a sensor's 1-hour view and look at the distance between Association measurements on a wireless network. This distance between these measurements is roughly how long the test cycles are.
LED Status Lights, what do they mean?
You can find all details here:
http://help.capenetworks.com/en/articles/1941715-sensor-led-status-light
Please note:
The sensor needs a "configuration" which tells it how to connect to it's configured networks. In order for the sensor to receive this configuration it needs to be able to communicate with our cloud. If the sensor is cellular-capable, it will attempt to use its cellular connection to download the configuration. However, it's possible that the sensor's location lacks adequate cellular reception for the supported LTE network in that region.
If the sensor is a non-cellular unit, it will need access to an unrestricted ethernet network to be able to download its configuration. This networks needs to have our required URLS allow-listed. The device will then use the ethernet network to download its configuration so it can start communicating with our cloud.
Alternatively, the device can be onboarded using our Bluetooth onboarding application, where the sensor's configuration file is transferred over a Bluetooth connection. When the device is un-configured it will flash blue (meaning it's waiting for a bluetooth connection), this sensor is in an un-configured state and the above steps should be completed to onboard and configure the device.