mirror of
https://github.com/Telecominfraproject/wlan-docs.git
synced 2025-11-25 06:04:54 +00:00
GitBook: [#1] No subject
This commit is contained in:
Jaspreet Sachdev
committed by
gitbook-bot
gitbook-bot
parent
97caf995c6
commit
a3dea0eaea
58
sdk/user-interface/devices-view/README.md
Normal file
58
sdk/user-interface/devices-view/README.md
Normal file
@@ -0,0 +1,58 @@
|
||||
---
|
||||
description: OpenWiFi 2.0 SDK
|
||||
---
|
||||
|
||||
# Devices
|
||||
|
||||
Each device presents Metrics and Health check data to the Gateway. Devices view displays this information in the following organization:
|
||||
|
||||
* Status
|
||||
* Configuration
|
||||
* Logs
|
||||
* Health
|
||||
* Commands
|
||||
* Statistics
|
||||
* Command History
|
||||
|
||||
.png>)
|
||||
|
||||
## Status
|
||||
|
||||
Connection status reflects the Gateway to Device current communications status. Uptime and Last Contact reflect communication state. Load indicates processing load on the device. Memory Used indicates free memory on the device.
|
||||
|
||||
|
||||
|
||||
## Configuration
|
||||
|
||||
Device UUID, Serial Number, MAC Address and Device Type are displayed. Last configuration update date and timestamp reflects the last time a "configure" action completed on the device. Password may be set and device notes may be added.
|
||||
|
||||
|
||||
|
||||
## Logs
|
||||
|
||||
Log history of the device is presented within Logs. Expand the tile selecting the down arrow.
|
||||
|
||||
.png>)
|
||||
|
||||
## Health
|
||||
|
||||
Health score is an active tile reflecting the device health out of a score reported by the device to Gateway. Health metrics are configured on the device based on chosen data model options. When the device falls out of 100%, this tile changes to red. Expanding the tile will present all health reports. Those with less than 100% score will contain reasons for the result from this interface.
|
||||
|
||||
|
||||
|
||||
## Commands
|
||||
|
||||
Commands tile provides a number of administrative actions for the user:
|
||||
|
||||
| Command | Action |
|
||||
| ---------------- | ------------------------------------------------------- |
|
||||
| Reboot | Warm Restart remote device |
|
||||
| Firmware Upgrade | Initiate firmware upgrade process |
|
||||
| WiFi Scan | Initiate remote scan of surrounding Wi-Fi |
|
||||
| Connect | Initiate an rTTY Remote Shell session |
|
||||
| Blink | Set LEDs to On, Off or Blinking state |
|
||||
| Trace | Initiate a remote Packet Capture |
|
||||
| Factory Reset | Hard Reset remote device - destroys device local config |
|
||||
| Configure | Upload Device Configuration |
|
||||
|
||||
|
||||
25
sdk/user-interface/devices-view/command-history.md
Normal file
25
sdk/user-interface/devices-view/command-history.md
Normal file
@@ -0,0 +1,25 @@
|
||||
---
|
||||
description: OpenWiFi SDK 2.0
|
||||
---
|
||||
|
||||
# Command History
|
||||
|
||||
Multiple events are recorded in the Command History tile. Each line item will have a Result, Details, and Delete action.
|
||||
|
||||
|
||||
|
||||
When an rTTY session is executed, this is a displayed command history. Selecting the Result icons will display the Success or Fail of the command.
|
||||
|
||||
|
||||
|
||||
Each provisioning event is reflected as a configure command history. To see the entire JSON payload and the result, including success or error with message, simply select Details to expand the dialog below with this data. A date and time in the third column indicates when the configure command was executed successfully.
|
||||
|
||||
|
||||
|
||||
If a provisioning event has failed to complete, its command history for configure will show as pending.
|
||||
|
||||
|
||||
|
||||
Remote packet capture is shown as the trace command history. When packet captures are persisted in the OpenWiFi SDK, they may be downloaded again through the cloud download icon.
|
||||
|
||||
|
||||
69
sdk/user-interface/devices-view/commands.md
Normal file
69
sdk/user-interface/devices-view/commands.md
Normal file
@@ -0,0 +1,69 @@
|
||||
---
|
||||
description: OpenWiFi 2.0 SDK
|
||||
---
|
||||
|
||||
# Commands
|
||||
|
||||
Within the devices view, the Commands tile offers a number of features and administrative actions. Each of these represent API calls exposed on the OpenAPI northbound interface from the SDK.
|
||||
|
||||
## Reboot
|
||||
|
||||
Selecting the Reboot action will prompt the below dialog. Options presented permit an immediate reboot or a scheduled reboot based on date and time.
|
||||
|
||||
.png>)
|
||||
|
||||
## Firmware Upgrade
|
||||
|
||||
Multiple methods exist to execute a remote Firmware Upgrade of a device. When selecting Firmware Upgrade via the Commands tile, a simple dialog to upgrade immediately or at a scheduled time is presented. Alternatively using the Firmware Management Service provides a complete solution including managed access to all TIP firmware images.
|
||||
|
||||
|
||||
|
||||
## Wi-Fi Scan
|
||||
|
||||
OpenWiFi devices may perform channel scanning and return this neighbor and RF data to the SDK in an on demand or ongoing manner.
|
||||
|
||||
.png>)
|
||||
|
||||
### Wi-Fi Scan Results
|
||||
|
||||
Scan operations function over all channels. If 5GHz channels do not display in the returned results ( either via the UI or over API ) this indicates the device is configured in a DFS channel for which it may not return survey scans at this time.
|
||||
|
||||
.png>)
|
||||
|
||||
## Connect
|
||||
|
||||
OpenWiFi enables remote connection to any managed device using rTTY encrypted shell session. Selecting Connect will cause a browser tab to open with the login session to current device.
|
||||
|
||||
|
||||
|
||||
## Blink
|
||||
|
||||
To assist with remote identification of devices in the network, it is possible to turn the LED lights On, Off, of continuous blinking. This may be run on-demand or scheduled.
|
||||
|
||||
|
||||
|
||||
## Trace
|
||||
|
||||
Trace feature enables a remote packet capture to occur on the managed device, over a specified period of time or amount of traffic, returning the "pcap" packet capture file locally to the OpenWiFi admin user.
|
||||
|
||||
|
||||
|
||||
Once complete the user is asked to open or save the packet capture file locally.
|
||||
|
||||
 (1).png>)
|
||||
|
||||
## Factory Reset
|
||||
|
||||
It is possible to revert a device to initial out of box state from the OpenWiFi SDK. Sending a Factory Reset will remove all configuration on the device and optionally reset the discovered cloud stored as the 'Redirector' in the device configuration.
|
||||
|
||||
.png>)
|
||||
|
||||
{% hint style="info" %}
|
||||
Note: When Redirector is not kept, devices will re-contact the Certificate Authority to re-discover their OpenWiFi cloud address
|
||||
{% endhint %}
|
||||
|
||||
## Configure
|
||||
|
||||
Prior to the introduction of OpenWiFi 2.0 Provisioning Service, device configuration is done through creation of the JSON provisioning file and either loading that file or applying its contents using the dialog presented via Configure. The same options exist when using the API directly.
|
||||
|
||||
.png>)
|
||||
37
sdk/user-interface/devices-view/statistics.md
Normal file
37
sdk/user-interface/devices-view/statistics.md
Normal file
@@ -0,0 +1,37 @@
|
||||
---
|
||||
description: OpenWiFi 2.0 SDK
|
||||
---
|
||||
|
||||
# Statistics
|
||||
|
||||
Each device page presents statistics in traffic terms per interface as a line graph of bandwidth over time.
|
||||
|
||||
|
||||
|
||||
The generated image may be downloaded for offline use.
|
||||
|
||||
|
||||
|
||||
Accessing Wi-Fi Analysis and Last Statistics may be found at the top right of Statistics tile.
|
||||
|
||||
|
||||
|
||||
## Wi-Fi Analysis
|
||||
|
||||
Operating channels, channel width, noise floor and transmit power are the first values reported in Radios table.
|
||||
|
||||
Viewing associations, from the Associations table, and their use is important in terms of bandwidth and connection quality. Wi-Fi Analysis helps visualize each client association, this could be an end user device or a WDS or Mesh association.
|
||||
|
||||
Each association is known by their MAC address or BSSID value. The mode of connection will indicate if an end user client device entering the "ap" or if a client is associated as "wds" or "mesh.
|
||||
|
||||
|
||||
|
||||
The access point view of RSSI, Rx and Tx Rate, Modulation Coding Scheme and Number of Spatial Streams are exposed for each association.
|
||||
|
||||
Using the slider along the top, the last 15 to 30 minutes of performances data may be viewed.
|
||||
|
||||
## Latest Statistics
|
||||
|
||||
The option to view Latest Statistics is at time of the MVP release, intended to help the Community see on a per device basis how much, or how little depending on device configuration, is being sent to the OpenWiFi Gateway in terms of telemetry.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user