From 44049b0bd3c2bf709bf1d885df6735a31e738fce Mon Sep 17 00:00:00 2001 From: Chris Busch Date: Mon, 19 Apr 2021 18:42:28 +0000 Subject: [PATCH] GitBook: [2.0.0] 16 pages modified --- SUMMARY.md | 15 ++---- api.md | 2 + .../basic-device-provisioning.md | 50 ------------------- getting-started/README.md | 16 ------ getting-started/controller.md | 16 +----- user-interface.md | 8 +++ 6 files changed, 14 insertions(+), 93 deletions(-) create mode 100644 api.md create mode 100644 user-interface.md diff --git a/SUMMARY.md b/SUMMARY.md index 1328ff9..ba5e800 100644 --- a/SUMMARY.md +++ b/SUMMARY.md @@ -3,19 +3,10 @@ * [Open Wi-Fi](README.md) * [Ordering Open Wi-Fi APs](ordering-open-wi-fi-aps.md) * [Getting Started](getting-started/README.md) - * [Cloud SDK Installation](getting-started/controller-installation/README.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) + * [Release 2.0 SDK](getting-started/controller.md) * [Access Points](getting-started/access-points.md) -* [User Interface](user-interface/README.md) - * [Dashboard](user-interface/dashboard.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) +* [User Interface](user-interface.md) +* [API](api.md) ## MDU Quick Start diff --git a/api.md b/api.md new file mode 100644 index 0000000..47bb08a --- /dev/null +++ b/api.md @@ -0,0 +1,2 @@ +# API + diff --git a/configuration-examples/basic-device-provisioning.md b/configuration-examples/basic-device-provisioning.md index 907b8ae..f1d76ab 100644 --- a/configuration-examples/basic-device-provisioning.md +++ b/configuration-examples/basic-device-provisioning.md @@ -4,53 +4,3 @@ description: Cloud SDK Profile Use # Basic Device Provisioning -Cloud SDK processes Profiles by aggregating certain profile types as child profiles inherited during device configuration. - - - - - - - - - - - - - - - - - - - - - - -
ProfileProvisioning Role
RFRadio Operations
Access Point -

LAN & GRE Configuration

-

Association to RF Profile

-

Association to SSID Profile

-
SSIDService Set Identifier Wireless Network Operations
- -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) - diff --git a/getting-started/README.md b/getting-started/README.md index bb4c7ea..31dd91e 100644 --- a/getting-started/README.md +++ b/getting-started/README.md @@ -1,18 +1,2 @@ # 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 - diff --git a/getting-started/controller.md b/getting-started/controller.md index e96f155..4b4af06 100644 --- a/getting-started/controller.md +++ b/getting-started/controller.md @@ -2,19 +2,5 @@ description: TIP Open Wi-Fi --- -# Cloud 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 %} +# Release 2.0 SDK diff --git a/user-interface.md b/user-interface.md new file mode 100644 index 0000000..b9ef2b1 --- /dev/null +++ b/user-interface.md @@ -0,0 +1,8 @@ +--- +description: TIP Cloud SDK +--- + +# User Interface + +## +