Symbol AP-51xx, Руководство по продукции, Страница: 576 / 622

AP-51xx Access Point Product Reference Guide 9-42
Thus, MU traffic will be segregated from the mesh traffic proliferating each AP’s 802.11a
radio.
13. again, the team wants to limit the number of MUs connecting to the mesh WLAN (for the
present time). Therefore, the team sets the Maximum MUs field to 10, and will use the
Radio Configuration page to control the number of client bridge connections.
14. The team verifies the Enable Client Bridge Backhaul checkbox is selected for both AP5
and AP6 to ensure the WLAN is available in the WLAN drop-down menu within the Radio
Configuration screen.
15. The IT team then verifies that steps 10 through 14 have been carried out identically for both
AP5 and AP6.
The IT team now needs to define a security policy for AP5 and AP4 complimentary with the
policy created for APs 1-4.
16. The IT Team defines a WPA2/CCMP security policy exactly like the one created for APs 1-4.
For more information, see how the team initially defined the security policy starting on step
16 within
Trion’s Initial Deployment on page 9-20 .
17. Existing MU traffic within the mesh network will be used within the expanded shipping yard.
Thus, the IT team refers to the ACLs created for APs 1-4 and defines an ACL exactly like it
for AP5 and AP6. The team also remembers to go to the ACL for AP1, AP3 and AP4 and add
AP5 and AP6 in order for each device in the mesh network to communicate with one another.
For more information, refer to step 22 within Trion’s Initial Deployment on page 9-20 .
18. The team decides to leave the Disallow MU to MU Communication checkbox unselected
for AP5 and AP6, as the team still considers all MU traffic within the shipping yard known
and not a threat to the growing mesh network.
19. The team selects the Use Secure Beacon checkbox from the Edit WLAN screen to not
transmit the AP- 5131’s ESSID between APs 1 through 6. If a hacker tries to find an ESSID
via an MU, the AP- 5131’s ESSID does not display since the ESSID is not in the beacon.
20. The team does not select the Accept Broadcast ESSID checkbox, as they still do not want
MUs randomly joining their carefully constructed mesh network.
21. The IT Team still envisions little (if any) video or voice traffic within the shipping as the MUs
within primarily scan bar codes and upload data. This still holds true for the QoS
requirements for AP5 and AP6, as the required coverage area has continued to grow, but not
the security, access permissions or QoS considerations. For more information, see how the
team defined the QoS policy for APs 1-4 starting on step 25 within
Trion’s Initial Deployment
on page 9-20 .