604| Secure Enterprise Mesh AOS-W 6.5.3.x| User Guide
Figure 74 Working of RMP
By default, the data frames the mesh portal receives on its mesh link are forwarded according to the bridge
table entries on the portal. However, frames received on mesh private VLAN (MPV) are treated differently by
the remote mesh portal. These frames are treated the same as frames received on a split SSID and are routed
rather than bridged. Mesh points obtain DHCP addresses from the corporate network. then register with the
switch using these IP addresses. When these mesh points send and receive PAPI control traffic from the main
office switch, it controls these mesh points just as if they were on a local VLAN. PAPI traffic containing keys and
other secret information receives IPsec encryption and decryption when it is forwarded to the switch through
the VPN tunnel.
Not all traffic from a mesh point is sent on the mesh private VLAN. When a mesh point bridges data received
via its Ethernet interface or from clients connected to an access radio VAP, the mesh point does not tag the
frame with the mesh private VLAN tag when it sends the data through mesh link to the remote mesh portal.
Note that the mesh point may still tag the frame depending on the VLAN of the virtual AP and the native VLAN
specified in the system profile. Care must be taken to assign the MPV value so that it does not clash with any
local tags assigned in the mesh network. In this scenario, the portal performs the default operation and bridges
the frame based on its bridge table. Traffic destined to the Internet is recognized as such by the remote mesh
portal based on ACL rules. This traffic is NATed on the remote mesh portal’s Ethernet interface.
For information on the procedure to configure remote mesh portals, see Configuring Remote Mesh Portals
(RMPs) on page 630
Understanding the AP Boot Sequence
The section describes the boot sequence for mesh APs in detail. Depending on its configured role, the AP
performs a slightly different boot sequence.
Booting the Mesh Portal
When the mesh portal boots, it recognizes that one radio is configured to operate as a mesh portal. It then
obtains an IP address from a DHCP server on its Ethernet interface, discovers the master switch on that
interface, registers the mesh radio with the switch, and obtains regulatory domain and mesh radio profiles for
each mesh point interface. A mesh virtual AP is created on the mesh portal radio interface, the regulatory
To Next Page
Loading...