What could cause this problem?

Refer to the exhibit.

An administrator implements the MultiZone feature. The administrator sets up five zones as shown in the exhibit in this configuration:
-Zone A has six controllers that form a cluster.
-Zone B has three controllers that from a cluster.
-Zones C, D, and E have a single standalone controller each.
A total of 13 VAPs are created across the five zones, Aruba Mobility Controllers (MCs) in Zones A, B and C run ArubaOS 8.1.0.1 MCs in zones D and E run ArubaOS 8.1.0.2. Some APs do not join their respective data zones.
What could cause this problem?
A. The number of controllers exceeds the maximum for MultiZone.
B. The MCs run different versions of the ArubaOS code.
C. The number of zones exceeds the maximum for MultiZone.
D. The number of VAPs exceeds the maximum for MultiZone.

Download Printable PDF. VALID exam to help you PASS.

One thought on “What could cause this problem?

  1. MultiZone limitations
    Mobility Controllers in all zones must run the same ArubaOS version. The DZ and PZ must have the same group
    names defined. Notice also that you cannot manage PZ and DZ controllers from the same MM. Mesh AP and
    RAP are not supported, and the following maximums apply:
    Maximum five zones (one PZ and four DZ)
    Maximum 12 controllers for all zones
    Maximum 16 VAPs per radio for all zones

Leave a Reply

Your email address will not be published. Required fields are marked *


The reCAPTCHA verification period has expired. Please reload the page.