C
ONFIGURATION
The amount of configuration depends on the complexity of your deployment. As you can see in
Examples (CLI)" on page
69, you can enter a minimum of three commands to deploy a single HiveAP, and just a few
more to deploy a hive.
However, for cases when you need to fine tune access control for more complex environments, HiveOS offers a rich
set of CLI commands. The configuration of HiveAPs falls into two main areas:
"Policy-Level Configurations" on page
for guidance on the commands you need to configure them.
Note: To find all commands using a particular character or string of characters, you can do a search using the
following command: show cmds containing string
Device-Level Configurations
Device-level configurations refer to the management of a HiveAP and its connectivity to wireless clients, the wired
network, and other hive members. The following list contains some key areas of device-level configurations and
relevant commands.
•
Management
•
Administrators, admin privileges, and login parameters
admin { min-password-length | superuser | user } ...
•
Logging settings
log { buffered | console | debug | facility | flash | host } ...
•
Connectivity settings
•
Interfaces
interface { wifi0 | wifi1 } ...
•
Subinterfaces
interface { wifi0.number | wifi1.number } ...
•
Layer 2 and layer 3 forwarding routes
route mac_addr ...
ip route { host | net } ip_addr ...
•
VLAN assignments
For users:
user-profile string group-id number qos-policy string vlan-id number
For hive communications:
hive string native-vlan number
For the mgt0 interface:
interface mgt0 vlan number
•
Radio settings
radio profile string ...
Deployment Guide
O
VERVIEW
68. Consider your deployment plans and then refer to the following sections
C
ONFIGURATION
"Deployment
"Device-Level Configurations"
O
VERVIEW
and
67