Configuring Access Guardian OmniAccess Stellar AP Integration
OmniSwitch AOS Release 8 Network Configuration Guide December 2017 page 28-72
• Dynamic VLAN configuration. The switch operationally enables dynamic VLAN configuration to
ensure that when the VLAN tag of AP client-tagged traffic does not match an existing switch VLAN,
the switch will dynamically create the VLAN.
– Dynamic VLANs created by UNP are identified as a separate type of VLAN; the default name is set
to “UNP-DYN-VLAN” and the designated type is set to “UNPD”.
– The switch will automatically remove dynamically created VLANs when all the MAC addresses
learned on the VLAN have aged out.
• Multiple VLAN Registration Protocol (MVRP). By default, MVRP is disabled for the switch.
Enable this protocol to ensure the propagation of the AP management VLAN and any VLAN (static or
dynamic) that was automatically tagged to carry AP client traffic to other switches.
– AP management VLANs dynamically created by MVRP are converted to UNP dynamic VLANs
(type UNPD).
– If an AP client tag matches a VLAN that was dynamically created by MVRP, then that VLAN is
converted to a UNP dynamic VLAN (type UNPD).
OmniAccess Stellar AP Configuration Guidelines
The Stellar AP device must meet the following configuration and operational requirements to ensure
successful discovery and integration into an OmniSwitch network:
• The AP device must connect to an OmniSwitch UNP bridge port. This triggers the Access Guardian
process to detect and integrate the AP device.
• The first packet a connected AP device sends (before an 802.1X or DHCP packet) must be an LLDP
frame with the “WLAN AP” bit set in the System Capabilities TLV and the LLDP media TLV device
type set as 4("Endpoint class 1V"). If this requirement is not met, the device may not get properly
identified as an AP; this could trigger a different process for classifying the device MAC address or
cause the address to be filtered.
• The AP device should always get an IP address using DHCP. Configure the DHCP server to use
Option 138 for the scope of IP addresses that will be assigned to AP devices.
• AP management traffic is always sent untagged on the management VLAN advertised by the switch.
• The wireless client traffic forwarded by the AP is always tagged with the assigned SSID VLAN.
Access Guardian will automatically assign the client traffic to switch VLANs that correspond to the
VLAN tags of the client traffic.
Quick Steps for Configuring OmniSwitch AP Discovery
The following procedure provides a brief tutorial for configuring existing OmniSwitch features to discover
and interact with OmniAccess Stellar APs.
1 Create the VLAN that will serve as the AP management VLAN on each participating switch in the
network. For example:
-> vlan 200 name “AP Management VLAN”
2 Tag switch ports that connect to other switches with the VLAN created in Step 1. For example,
-> vlan 200 members port 1/1/24 tagged
3 Map the VLAN created in Step 1 to the built-in defaultWLANProfile. For example:
-> unp profile defaultWLANProfile map vlan 200
To Next Page
Loading...
Need help?
General
