mirror of
https://github.com/Telecominfraproject/wlan-docs.git
synced 2025-11-02 03:37:52 +00:00
GitBook: [master] 25 pages modified
This commit is contained in:
@@ -1,12 +1,14 @@
|
||||
---
|
||||
description: TIP SDK
|
||||
description: TIP Cloud SDK
|
||||
---
|
||||
|
||||
# User Interface
|
||||
|
||||
## Navigating the UI
|
||||
|
||||
TIP open source SDK offers a web based user interface supporting many common configurations. The web based interface uses the SDK API. It is possible to further extend functionality of the SDK user interface or to create other interfaces using the SDK API.
|
||||
TIP open source SDK offers a web based user interface supporting many common configurations. The web based interface uses the SDK north bound API.
|
||||
|
||||
It is possible to further extend functionality of the SDK user interface or to create other interfaces using the SDK API.
|
||||
|
||||
### Log In
|
||||
|
||||
|
||||
@@ -4,7 +4,7 @@ description: Cloud SDK Default Landing Page
|
||||
|
||||
# Dashboard
|
||||
|
||||
TIP Cloud SDK is organized into main components organized along the top of the screen.
|
||||
TIP Cloud SDK is organized into main components presented along the top of the screen.
|
||||
|
||||

|
||||
|
||||
@@ -12,10 +12,9 @@ Dashboard is the default landing page for the user interface.
|
||||
Network enables management of Access Points and display of Client Devices status.
|
||||
Profiles enables template based management of all provisioning parameters.
|
||||
System enables Manufacturer OUI Updates, Firmware Updates, Auto-Provisioning and Client Block List.
|
||||
Users enables configuration of local user accounts of the Cloud SDK.
|
||||
|
||||
Users enables configuration of local user accounts of the Cloud SDK.
|
||||
Alarm indicates an error condition has occurred with one or multiple Access Points.
|
||||
Gear icon to LogOut.
|
||||
Gear icon to Log Out.
|
||||
|
||||
### Dashboard Components
|
||||
|
||||
|
||||
@@ -10,22 +10,22 @@ From the Network page it is possible to create organizational regions to group d
|
||||
|
||||
### Location Tree
|
||||
|
||||
In a future release it will be possible to assign devices to new locations to help in building an administrative hierarchy supporting convenient organization of device to service location. This functionality is exposed in the API and may be further refined in subsequent UI releases.
|
||||
In a future release it will be possible to assign devices to new locations to help in building an administrative hierarchy supporting convenient organization of device to service location. This functionality is exposed in the API and may be further refined in subsequent open source UI releases.
|
||||
|
||||
### Access Points
|
||||
|
||||
For each Access Point that has contacted Cloud SDK, a row will populate within Access Points.
|
||||
Specific information for each Access Point including Device name, alarm state, model and IP address are shown.
|
||||
For each access point that has contacted Cloud SDK, a row will populate within Access Points.
|
||||
Specific information for each device including Device name, alarm state, model and IP address are shown.
|
||||
|
||||
Along the right side of each Access Point row are Profile, Channel, Occupancy, Noise Floor and Devices.
|
||||
Channel indicates the current provisioned RF Channel for each radio in the Access Point.
|
||||
Channel indicates the current provisioned RF Channel for each radio in the device.
|
||||
Occupancy indicates available RF bandwidth for Wi-Fi clients as a value over 100.
|
||||
Noise Floor represents the reported RF noise condition being measured by the Access Point within the operating channel and reported to the Cloud SDK.
|
||||
Devices indicated the total associated clients for each radio in the Access Point.
|
||||
Noise Floor represents the reported RF noise condition being measured by the device within the operating channel and reported to the Cloud SDK.
|
||||
Devices indicated the total associated clients for each radio in the access point.
|
||||
|
||||
#### Access Point Device Record
|
||||
|
||||
Each Access Point managed by Cloud SDK inherits provisioning information from Profiles in addition to supporting device specific configurations and reporting device specific operating conditions.
|
||||
Each access point managed by Cloud SDK inherits provisioning information from Profiles in addition to supporting device specific configurations and reporting device specific operating conditions.
|
||||
|
||||

|
||||
|
||||
@@ -37,7 +37,7 @@ Location permits the assignment of the device to a location in Cloud SDK hierarc
|
||||
|
||||

|
||||
|
||||
Operating System Stats are sent to Cloud SDK from each Access Point using the MQTT interface. These statistics are regularly received as part of the overall telemetry stream.
|
||||
Operating System Stats are sent to Cloud SDK from each device using the MQTT interface. These statistics are regularly received as part of the overall telemetry stream.
|
||||
|
||||
#### Firmware
|
||||
|
||||
|
||||
@@ -19,6 +19,6 @@ Sample default templates are provided on initial startup of Cloud SDK.
|
||||
| RADIUS | Authentication Authorization Accounting Configuration per SSID |
|
||||
| Equipment AP | 1:1 or 1:Many Device Association to RF Profile and SSID |
|
||||
| Captive Portal | Access Point Captive Portal configuration parameters |
|
||||
| Passpoint | R1 & R2 Compliant IEEE802.11u configuration parameters |
|
||||
| Passpoint | R1 & R2 Compliant IEEE 802.11u configuration parameters |
|
||||
| Passpoint ID Provider | R2 Compliant Offload, Venue, NAI and OpenRoaming configuration parameters |
|
||||
|
||||
|
||||
Reference in New Issue
Block a user