scottk/wlan-docs
1
0
Fork 0
mirror of https://github.com/Telecominfraproject/wlan-docs.git synced 2025-11-04 12:48:08 +00:00
Code Issues Packages Projects Releases Wiki Activity

GitBook: [2.0.0] 16 pages modified

Browse Source
This commit is contained in:
Chris Busch
2021-04-19 18:42:28 +00:00
committed by gitbook-bot
parent 0ef68f2f7f
commit 44049b0bd3
6 changed files with 14 additions and 93 deletions
Download Patch File Download Diff File Expand all files Collapse all files

15
SUMMARY.md
View File

@@ -3,19 +3,10 @@
* [Open Wi-Fi](README.md) * [Open Wi-Fi](README.md)
* [Ordering Open Wi-Fi APs](ordering-open-wi-fi-aps.md) * [Ordering Open Wi-Fi APs](ordering-open-wi-fi-aps.md)
* [Getting Started](getting-started/README.md) * [Getting Started](getting-started/README.md)
* [Cloud SDK Installation](getting-started/controller-installation/README.md) * [Release 2.0 SDK](getting-started/controller.md)
* [AWS Install](getting-started/controller-installation/aws-install.md)
* [MicroK8s Install](getting-started/controller-installation/microk8s-install.md)
* [Cloud SDK](getting-started/controller.md)
* [Access Points](getting-started/access-points.md) * [Access Points](getting-started/access-points.md)
* [User Interface](user-interface/README.md) * [User Interface](user-interface.md)
* [Dashboard](user-interface/dashboard.md) * [API](api.md)
* [Network](user-interface/network.md)
* [Profiles](user-interface/profiles.md)
* [System](user-interface/system.md)
* [Accounts](user-interface/accounts.md)
* [API](api/README.md)
* [Open API](api/swagger.md)
## MDU Quick Start ## MDU Quick Start

2
api.md Normal file
View File

@@ -0,0 +1,2 @@
# API

50
configuration-examples/basic-device-provisioning.md
View File

@@ -4,53 +4,3 @@ description: Cloud SDK Profile Use
# Basic Device Provisioning # Basic Device Provisioning
Cloud SDK processes Profiles by aggregating certain profile types as child profiles inherited during device configuration.
<table>
<thead>
<tr>
<th style="text-align:left">Profile</th>
<th style="text-align:left">Provisioning Role</th>
</tr>
</thead>
<tbody>
<tr>
<td style="text-align:left">RF</td>
<td style="text-align:left">Radio Operations</td>
</tr>
<tr>
<td style="text-align:left">Access Point</td>
<td style="text-align:left">
<p>LAN &amp; GRE Configuration</p>
<p>Association to RF Profile</p>
<p>Association to SSID Profile</p>
</td>
</tr>
<tr>
<td style="text-align:left">SSID</td>
<td style="text-align:left">Service Set Identifier Wireless Network Operations</td>
</tr>
</tbody>
</table>
Association of devices to Access Point and SSID is possible as one-to-one \(1:1\) or one-to-many \(1:M\).
The decision on using 1:1 or 1:M is entirely based on the desired deployment.
Creating a 1:1 Access Point Profile could be useful in certain lab or specific network locations. If a specific RF Profile was desired on a select device, using an Access Point Profile with reference to the specific RF Profile would accomplish this provisioning logic.
Creating an RF Profile specifically for IEEE802.11ac Wi-Fi 5 Access Points to inherit may be a common approach with another RF Profile for all IEEE802.11ax Wi-Fi 6 Access Points. Another reason to create a unique RF Profile may configured outdoor RF configuration that is unique from other indoor based Access Points.
Creating RF Profile with specific Client Steering, Channel Hop, or general radio operation other than default settings are useful when defining behavior of Access Points individually or as a large group of managed devices.
## Wi-Fi 5 802.11AC Mode General RF Profile
Example Wi-Fi 5 IEEE802.11AC RF Profile:
![Wi-Fi 5 Basic RF Profile Settings](../.gitbook/assets/screen-shot-2021-03-29-at-9.07.55-am.png)
## Wi-Fi 6 802.11AX Mode General RF Profile
Example Wi-Fi 6 IEEE802.11AX RF Profile
![Wi-Fi 6 Basic RF Profile Settings](../.gitbook/assets/screen-shot-2021-03-29-at-9.23.14-am.png)

16
getting-started/README.md
View File

@@ -1,18 +1,2 @@
# Getting Started # Getting Started
Deploying the TIP Open Wi-Fi solution into a lab or into production is simple to do.
Some basic pre-requisites should be satisfied before beginning.
Ensure the following are known before beginning installation:
* Fully Qualified Domain Name \(FQDN\) is available and configurable
* Internet Protocol \(IP\) subnet with Dynamic Host Configuration Protocol \(DHCP\) for access points is available
* Internet Protocol \(IP\) subnet with static addressing is available for Cloud SDK
* If using VLAN features of the access points, an IEEE 802.1q compliant Ethernet switch and VLAN topology are supported in your network
* Network traffic is permitted for the following ports from Access Points to Cloud SDK:
* 80
* 443
* 1883
* 6640
* 6643

16
getting-started/controller.md
View File

@@ -2,19 +2,5 @@
description: TIP Open Wi-Fi description: TIP Open Wi-Fi
--- ---
# Cloud SDK # Release 2.0 SDK
With the Cloud SDK now installed into either a public cloud or on premises, logging in with default username **support@example.com** and password **support** are now possible.
![Default Login Page](../.gitbook/assets/screen-shot-2020-11-29-at-4.25.44-pm.png)
Once successfully logged in, please refer to [User Interface](../user-interface/) documentation for further details of specific configuration.
{% hint style="info" %}
Current TIP Cloud SDK deploys using self-signed certificates. This requires accepting the self-signed certificate in the UI for the following URLs:
[https://wlan-ui.wlan.local](https://wlan-ui.wlan.local)
[https://wlan-ui-graphql.wlan.local](https://wlan-ui-graphql.wlan.local)
Navigate to both URLs and accept the certificate exception.
Once the client browser has these certificate exceptions loaded login will succeed.
{% endhint %}

8
user-interface.md Normal file
View File

@@ -0,0 +1,8 @@
---
description: TIP Cloud SDK
---
# User Interface
##