HPE6-A47 Exam Dumps : Designing Aruba Solutions

ClearPass OnConnect is a feature of the ClearPass Policy Manager that allows wired authentication on switches that do not support 802.1X or RADIUS protocols. ClearPass OnConnect uses SNMP to monitor and control the switch ports based on the device profiles and policies defined in ClearPass12. ClearPass OnConnect can provide the following benefits for the customer:

• It can enable wired authentication without requiring any changes to the existing switch infrastructure or the end-user devices. This can save the customer’s budget and time, as well as minimize the network disruption and user impact.
• It can provide visibility and control over the wired devices, such as printers, IoT devices, and laptops, that connect to the network. ClearPass OnConnect can identify the device type, user role, and location, and apply the appropriate access policies based on the customer’s security and compliance requirements. For example, ClearPass OnConnect can allow only authorized devices and users to access certain network resources, or quarantine or block any unknown or non-compliant devices.
• It can integrate with the other components of the Aruba solution, such as the MCs, MMs, APs, AirWave, and ClearPass Guest, to provide a consistent and unified network management and security solution across the wired and wireless networks. For example, ClearPass OnConnect can leverage the device profiles and policies from ClearPass Guest, or share the network health and performance data with AirWave.

Therefore, by explaining this feature, the architect can justify the proposed solution and show how it can meet the customer’s needs and expectations for wired authentication, as well as wireless authentication.

References:

• 1: https://www.arubanetworks.com/techdocs/ClearPass/6.7/PolicyManager/index.htm#CPPM_UserGuide/Admin/OnConnect.htm
• 2: https://www.arubanetworks.com/assets/tg/TB_ClearPass_OnConnect.pdf

 A collision domain is a logical area of the network where devices share the same wireless medium and may interfere with each other’s transmissions. In a WLAN, a collision domain is defined by the channel and the coverage area of an AP or a client. Devices that operate on the same channel and are within range of each other belong to the same collision domain and must contend for access to the medium using the Carrier Sense Multiple Access with Collision Avoidance (CSMA/CA) protocol. Devices that operate on different channels or are out of range of each other belong to different collision domains and do not interfere with each other.

In this scenario, the architect plans 12 APs for an auditorium that is 325 square meters (3,498 square feet). Each AP has one 2.4 GHz radio and one 5 GHz radio. Both types of radios use 20 MHz channels. Assuming that DFS channels can be used in this design, the question is how many 5 GHz collision domains does this design provide.

To answer this question, we need to consider the following factors:

• The number of available 5 GHz channels in the regulatory domain of the auditorium. Different countries have different regulations on the use of the 5 GHz band, which affects the number and availability of channels for WLANs. For example, in the United States, there are 25 non-overlapping 20 MHz channels in the 5 GHz band, but some of them are subject to Dynamic Frequency Selection (DFS) requirements, which means that they must avoid interfering with radar systems by detecting and switching to another channel if radar signals are present. In other countries, such as Japan, there are 19 non-overlapping 20 MHz channels in the 5 GHz band, but some of them are restricted to indoor use only. Therefore, the number of available 5 GHz channels for the design depends on the regulatory domain of the auditorium.
• The channel assignment and distribution of the 12 APs in the auditorium. The channel assignment and distribution of the APs affect the number and size of the collision domains in the WLAN. Ideally, the APs should be assigned to non-overlapping channels and distributed evenly across the auditorium to provide optimal coverage and capacity, while minimizing co-channelinterference and adjacent channel interference. Co-channel interference occurs when devices on the same channel interfere with each other, while adjacent channel interference occurs when devices on nearby channels interfere with each other. Both types of interference degrade the performance and quality of the WLAN. Therefore, the channel assignment and distribution of the APs should follow the best practices of RF design, such as using a channel reuse plan, avoiding channel overlap, and adjusting the transmit power and antenna gain of the APs to match the coverage and capacity requirements of the auditorium.
• The coverage and capacity requirements of the auditorium. The coverage and capacity requirements of the auditorium affect the number and placement of the APs and the transmit power and antenna gain settings of the radios. The coverage requirement refers to the minimum signal strength and signal-to-noise ratio (SNR) that the APs and clients need to maintain a reliable wireless connection. The capacity requirement refers to the maximum number of clients and the minimum throughput and quality of service (QoS) that the APs and clients need to support the applications and services of the auditorium. The coverage and capacity requirements of the auditorium depend on the size and shape of the space, the density and distribution of the clients, the types and characteristics of the applications and services, and the performance and capabilities of the devices. Therefore, the coverage and capacity requirements of the auditorium should be determined by conducting a site survey and a network analysis, and then used to guide the design and configuration of the APs and radios.

Based on these factors, we can estimate the number of 5 GHz collision domains in the design as follows:

• Assuming that the auditorium is located in the United States and that DFS channels can be used in the design, there are 25 non-overlapping 20 MHz channels in the 5 GHz band. However, not all of them may be available or suitable for the design, depending on the presence and activity of radar systems in the area, the compatibility and support of the APs and clients, and the interference and noise level of the environment. Therefore, we will use a conservative estimate of 15 available 20 MHz channels in the 5 GHz band for the design.
• Assuming that the 12 APs are assigned to non-overlapping channels and distributed evenly across the auditorium, each AP will have its own 5 GHz collision domain, as there will be no co-channel interference or adjacent channel interference among the APs. Therefore, there will be 12 5 GHz collision domains in the design, corresponding to the 12 APs.
• Assuming that the coverage and capacity requirements of the auditorium are moderate and that the transmit power and antenna gain settings of the radios are adjusted accordingly, each AP will cover an area of about 27 square meters (290 square feet), which is roughly the size of a small classroom. This means that the APs will provide adequate signal strength and SNR for the clients, while avoiding excessive overlap and interference among the APs. Therefore, there will be no need to further divide or merge the 5 GHz collision domains in the design, as they will match the coverage and capacity requirements of the auditorium.

Hence, the number of 5 GHz collision domains in the design is 12, which is the answer option C. References:

• RF Design | Validated Solution Guide - Aruba
• Configuring 2.4 Ghz and 5 Ghz Radios - Aruba
• Chapter T-5: Understanding RF Collision Domains - Aruba
• [Aruba Certified Design Professional Official Certification Study Guide (HPE6-A47)]

whether the MC needs to support advanced 8.x features. This is because the Aruba 7000 Series MCs are based on the older hardware platform and can only run up to ArubaOS 6.5.x, while the Aruba 7200 Series MCs are based on the newer hardware platform and can run ArubaOS 8.x and above. ArubaOS 8.x introduces many advanced features, such as clustering, MultiZone, AirMatch, and dynamic segmentation, that are not supported by the Aruba 7000 Series MCs. Therefore, if the architect needs to design a solution that leverages these features, the Aruba 7200 Series MCs are the better choice.

Option A is incorrect because the number of wireless devices that the MC needs to support is not a key criteria to choose between the Aruba 7000 Series or 7200 Series MCs.Both series can support a similar number of devices, depending on the model and license.

Option B is incorrect because whether the MC needs to terminate VPN tunnels is not a key criteria to choose between the Aruba 7000 Series or 7200 Series MCs. Both series can terminate VPN tunnels, such as IPSec, GRE, and RAP, depending on the model and license.

Option C is incorrect because the need to deploy controllers in a cluster is not a key criteria to choose between the Aruba 7000 Series or 7200 Series MCs. Both series can participate in a cluster, as long as they run the same ArubaOS version and have the same license.

References: The information can be referenced from the official HPE documents and learning materials available on HPE Press and Aruba Networks. Specifically, it aligns with the objectives outlined in Chapter 6: Wireless Network Design, where the MC selection and ArubaOS 8.x features are discussed. Designing Aruba Solutions Official Certification Study Guide Aruba Mobility Controller Data Sheet ArubaOS 8.7 User Guide