Configuring Access Guardian OmniAccess Stellar AP Integration
OmniSwitch AOS Release 8 Network Configuration Guide December 2017 page 28-69
OmniAccess Stellar AP Integration
Access Guardian provides the framework through which OmniAccess Stellar Access Points (APs)
connected to an OmniSwitch are detected, learned, and managed. Wireless client traffic is then forwarded
from the AP to the OmniSwitch and onto the wired network. This integration provides a unified wireless
over wired network access solution.
How it Works
The OmniSwitch boots up with specific default configuration and operational settings that trigger the
following process to detect, learn, and classify connected Stellar AP devices:
1 The switch and any Stellar AP device that is connected to a UNP bridge port initially exchange Link
Layer Detection Protocol (LLDP) TLV packets. Through this exchange of LLDP packets, the switch
identifies and learns the device MAC address as an AP.
2 If the UNP AP mode is globally enabled (the default) and an AP device is detected on a UNP bridge
port, the following actions are triggered to automatically change the operational status of the specified
options (the operational status overrides the configured status):
– The transmission of LLDP Port VLAN ID and AP Location TLVs is operationally enabled on the
UNP bridge port.
– The trust tag status for the UNP bridge port is operationally enabled.
– The global status for dynamic VLAN configuration is operationally enabled for the switch.
3 Once the AP MAC address is detected and learned, a built-in LLDP UNP classification rule for access
points classifies the AP device into a built-in default profile (defaultWLANProfile). The profile is
associated with a VLAN into which the AP device is classified. This establishes a VLAN-port association
(VPA) between the UNP port and profile VLAN on which the AP MAC address is learned and forwarded.
4 After the AP device connection is established, classified, and the management VLAN assigned, any of
the following actions can occur:
– The AP device sends DHCP packets.
– The switch transmits LLDP packets to the AP device to advertise the management VLAN and AP
location information.
– The AP device starts to send client-tagged traffic (tagged with the SSID VLAN). The switch will
trust the VLAN tag of the AP client traffic and attempt to assign the traffic to a switch VLAN that
matches the tag of the client traffic. If a matching switch VLAN does not exist, then the switch will
dynamically create the necessary VLAN on which to forward the AP client traffic.
5 MVRP will then propagate the VLAN configuration (AP management VLAN and any static or
dynamic VLAN that was automatically tagged to carry AP client traffic) to adjoining switches in the
network. This process creates specific VLAN domains through which the untagged AP management
traffic and tagged wireless client traffic is forwarded on the wired network.
The OmniSwitch detection and integration of OmniAccess Stellar APs results in a switch configuration
that includes a management VLAN for the AP device and additional VLANs for wireless client-tagged
traffic that is forwarded by the AP onto the wired network.
The following diagram shows an example of a network topology in which a Stellar AP connected to an
OmniSwitch serves as a bridge between a wireless and wired network:
To Next Page
Loading...
