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

GitBook: [master] 25 pages and 2 assets modified

Browse Source
This commit is contained in:
Chris Busch
2021-03-29 14:56:09 +00:00
committed by gitbook-bot
parent eec8966228
commit 6f50e0d410
4 changed files with 63 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

BIN
.gitbook/assets/screen-shot-2021-03-29-at-9.07.55-am.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 87 KiB

BIN
.gitbook/assets/screen-shot-2021-03-29-at-9.23.14-am.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 88 KiB

1
SUMMARY.md
View File

@@ -24,6 +24,7 @@
## Configuration Examples
* [Basic Device Provisioning](configuration-examples/basic-device-provisioning.md)
* [Bridge Mode SSID](configuration-examples/bridge-mode-ssid.md)
* [Multi-VLAN SSID](configuration-examples/multi-vlan-ssid.md)
* [NAT Gateway Mode SSID](configuration-examples/nat-gateway-mode-ssid.md)

62
configuration-examples/basic-device-provisioning.md Normal file
View File

@@ -0,0 +1,62 @@
---
description: Cloud SDK Profile Use
---
# 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)