HPE6-A47 Questions and Answers

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

Aruba Central Managed Portal (MSP) is a cloud-based network management platform that enables service providers to centrally manage and monitor multiple tenant accounts from a single interface1. MSP mode is a multi-tenant operational mode that Aruba Central accounts can be converted into, provided these accounts have subscribed to the Aruba Central app2. MSP mode allows service providers to provision and manage tenant accounts, assign devices to tenant accounts, manage subscription keys and perform other functions such as configuring network profiles and viewing alerts3. MSP mode is suitable for the scenario where a service provider needs to manage multiple customer networks, as it simplifies tenant network operations using capabilities such as zero-touch setup, historical data reporting, PCI compliance monitoring, and troubleshooting2. References:

• 1: MSP Overview - Aruba
• 2: MSP Architecture - Aruba
• 3: Managed Service Portal - Aruba

According to the Aruba Validated Design: Campus Wireless LAN1, MCs that are in different subnets cannot form a cluster, which is a logical group of MCs that share the same configuration and provide redundancy and load balancing for each other. However, MCs that are in different subnets can still provide backup LMS (local mobility switch) functionality for each other’s APs. This means that if the primary MC that controls an AP fails, the AP can fail over to the backup MC that is in a different subnet. However, this failover is not stateful, meaning that the user sessions and firewall states are not preserved. Therefore, option D is the correct answer.

Option A is incorrect because the MCs can provide some level of redundancy for each other without being in the same subnet, as explained above. Option B is incorrect because VRRP is not required to provide redundancy for MCs that are in different subnets. VRRP is a protocol that provides redundancy for routers by creating a virtual router with a shared IP address. However, MCs do not act as routers, and they do not need a shared IP address to provide backup LMS functionality. Option C is incorrect because the MCs cannot be in a cluster if they are in different subnets, as explained above. Therefore, the cluster will not support any features, such as stateful failover, load balancing, or centralized configuration. References: Aruba Validated Design: Campus Wireless LAN)

 Aruba Instant APs are a simple, easy to deploy, and cost-effective solution for small office buildings that need wireless access. Aruba Instant APs can form a self-organizing and self-healing mesh network that supports basic rogue AP detection and provides a stateful firewall with role-based policies. Aruba Instant APs do not require a separate controller or license, and can be managed from the cloud or a mobile app. Aruba remote APs are designed for branch or home offices that need to connect to a central controller over a WAN link. Aruba campus APs and a Virtual Mobility Controller are suitable for larger or more complex deployments that need more scalability and flexibility. Aruba campus APs and an Aruba 7005 Mobility Controller are also more expensive and require additional hardware and licensing. References: Aruba Instant Access Points), Aruba Validated Design: Campus Wireless LAN)

The Virtual Switching Framework (VSF) is a technology that allows two or more Aruba switches to operate as a single logical device, providing high availability, simplified management, and increased performance. VSF is supported on Aruba 5400R zl2 switches, which are modular switches that can accommodate different types of line cards and power supplies1.

The VSF fabric requires two types of connections between the member switches: VSF links and VSF ports. VSF links are the physical connections that carry the VSF control and data traffic, while VSF ports are the logical interfaces that bundle the VSF links into a single logical link. VSF links can be either 10 GbE or 40 GbE, and VSF ports can be either 10 GbE or 40 GbE1.

To create a VSF fabric with two 5406R zl2 switches, the architect needs to ensure that the switches have the compatible modules, transceivers, and cables for the VSF links and ports. According to the ArubaOS-Switch Management and Configuration Guide1, the following requirements apply for the VSF fabric:

• The switches must have the same chassis model, the same number and type of modules, and the same firmware version.
• The switches must have at least one v3 module in slot A or B. The v3 modules are the ones with the letter “M” in the part number, such as J9990A, J9991A, and J9992A. The v2 modules are the ones with the letter “A” in the part number, such as J9534A, J9535A, and J9536A.
• The switches must have the same type of transceivers and cables for the VSF links. The supported transceivers are the Aruba 10G SFP+ LC SR, the Aruba 10G SFP+ LC LR, the Aruba 40G QSFP+ LC SR4, and the Aruba 40G QSFP+ MPO SR4. The supported cables are the Aruba 10G SFP+ to SFP+ 1m DAC Cable, the Aruba 10G SFP+ to SFP+ 3m DAC Cable, the Aruba 40G QSFP+ to QSFP+ 1m DAC Cable, and the Aruba 40G QSFP+ to QSFP+ 3m DAC Cable.

Based on the exhibit, the architect has planned to use the Aruba 40G QSFP+ to QSFP+ 1m DAC Cable (JH234A) for the VSF links, which is a supported option. However, the architect has also selected the Aruba 24p 10GBASE-T v2 zl Module (J9536A) and the Aruba 20p 10GbE SFP+ v2 zl Module (J9535A) for the switches, which are not compatible with the VSF fabric. The architect should change these v2 modules to v3 modules, such as the Aruba 24p 10GBASE-T v3 zl2 Module (J9996A) and the Aruba 20p 10GbE SFP+ v3 zl2 Module (J9990A), to meet the VSF requirements.

The other options are not issues with the plan. Adding two QSPF+ MP0 SR4 transceivers (A) is not necessary, as the DAC cable already provides the 40 GbE connection for the VSF links. Adding stacking modules and cables © is not required, as the VSF fabric does not use the traditional stacking technology. Changing the power supply type (D) is not relevant, as the VSF fabric does not impose any restrictions on the power supply type.

References: 1: ArubaOS-Switch Management and Configuration Guide - Aruba, Chapter 12: Virtual Switching Framework, pages 219-227.

Air Monitors (AMs) are Aruba access points (APs) that are configured to operate in a dedicated mode for scanning the RF spectrum and detecting rogue APs, clients, and intrusion attacks. AMs do not serve any wireless clients and can scan all channels in both 2.4 GHz and 5 GHz bands. AMs provide better visibility and coverage of the RF environment than APs that serve clients, as they can scan more frequently and thoroughly. However, AMs also consume more power and network resources than APs, and require additional hardware and licensing costs. Therefore, the optimal number of AMs per floor depends on several factors, such as the size and shape of the floor, the density and distribution of APs and clients, the security and compliance requirements, and the budget and availability of the organization.

According to the Aruba Wireless Intrusion Protection (WIP) Technology Guide1, a general rule of thumb is to deploy one AM for every four to six APs. This ratio can provide adequate coverage and detection for most environments, while balancing the trade-offs between performance and cost. However, this ratio is not fixed and can vary depending on the specific needs and characteristics of each deployment. For example, if the floor has a high density of APs and clients, or a high risk of rogue or malicious activity, more AMs may be needed to provide better security and visibility. Conversely, if the floor has a low density of APs and clients, or a low risk of rogue or malicious activity, fewer AMs may be sufficient to provide adequate security and visibility.

In this case, the floor has 20 APs, which implies a moderate to high density of APs and clients. Assuming that the floor has a rectangular shape and a uniform distribution of APs and clients, a reasonable estimate of the number of AMs per floor would be about 3 to 5, based on the general rule of thumb. This would provide enough coverage and detection for most scenarios, while minimizing the additional costs and resources. However, this estimate may need to be adjusted if the floor has a different shape or a non-uniform distribution of APs and clients, or if the organization has specific security and compliance requirements that demand more or less AMs per floor. References:

• Wireless Intrusion Protection (WIP) Technology Guide
• Installing Air Monitors | Wireless Access - Airheads Community
• Aruba Certified Design Professional Official Certification Study Guide (HPE6-A47)

The frequency of the radio wave is one of the most important factors that determines the antenna performance and compatibility. The antenna must be designed to operate at the same frequency band as the radio, otherwise the impedance mismatch will cause signal loss and reflection. The frequency also affects the size, shape, and radiation pattern of the antenna. For example, a lower frequency requires a larger antenna to achievethe same gain and directivity as a higher frequency antenna. The frequency also determines the available bandwidth and channel spacing for the wireless communication12. Therefore, it is essential to ensure that the antenna is designed for the frequency used by the radio. References:

• 1: Antenna selection guidelines - STMicroelectronics
• 2: Guide to Selecting the Right Antenna - Telco Antennas

The minimum acceptable signal for an active site survey depends on the type of applications and the data rates that the users require. For 802.11ac, which operates in the 5 GHz band, Aruba recommends a signal of -65 dBm or better for high-performance applications such as voice and video, and a signal of -72 dBm or better for basic applications such as Web and email1. These values are based on the receiver sensitivity of typical 802.11ac clients and the expected signal-to-noise ratio (SNR) for different modulation and coding schemes (MCS). A higher SNR means a higher data rate and a better user experience.

Therefore, the architect should look for a signal of -65 dBm in the 5 GHz band to determine the test AP range for 802.11ac, assuming that the users run high-performance applications. A signal of -75 dBm in the 5 GHz band might be too weak to support the desired data rates and quality of service. A signal of -65 dBm or -75 dBm in the 2.4 GHz band is irrelevant for 802.11ac, as it does not operate in that band.

References:

• Aruba Validated Reference Design: 802.11ac Networks
• Best Practices for Monitoring and Troubleshooting 802.11ac Networks

802.1X authentication without tunnelled node is a form of port-based network access control that uses the Extensible Authentication Protocol (EAP) to authenticate users and devices on a wired network. This form of authentication provides several benefits, such as:

• It enables user access control and ensures only authorized users connect. This prevents unauthorized access to the network and its resources, and enhances security and compliance.
• It allows dynamic assignment of VLANs and roles based on user identity and device type. This simplifies network management and improves user experience.
• It supports multiple authentication methods, such as certificates, passwords, tokens, or biometrics. This provides flexibility and choice for users and administrators.
• It integrates with Aruba ClearPass Policy Manager (CPPM) for centralized policy enforcement and visibility. This enables granular control and monitoring of wired user traffic and devices. References:
• Aruba 2930M Switch Series - Data sheet)
• Aruba ClearPass Policy Manager - Data sheet)
• ArubaOS-Switch Wired Access with ClearPass - Configuration guide)

To plan a wireless solution upgrade for printers, the architect needs to know whether the printers support 802.1X and the 802.11 standards supported by the printer. These two factors are important for ensuring the compatibility, security, and performance of the wireless network.

• 802.1X is a standard for network access control that provides authentication, authorization, and encryption for devices that connect to a wireless network1. It prevents unauthorized devices from accessing the network resources and protects the data transmission from eavesdropping or tampering. If the printers support 802.1X, the architect can design a wireless solution that leverages this feature to enhance the security and compliance of the network. If the printers do not support 802.1X, the architect may need to consider alternative methods of securing the wireless access, such as MAC address filtering, VPN, or WPA2-PSK2.
• 802.11 is a set of standards that define the specifications and protocols for wireless communication3. Different 802.11 standards have different characteristics, such as frequency, bandwidth, data rate, range, and compatibility. For example, 802.11a operates at 5 GHz and offers up to 54 Mbps, while 802.11b operates at 2.4 GHz and offers up to 11 Mbps3. If the printers support the same or higher 802.11 standards as the wireless network, the architect can design a wireless solution that ensures the optimal performance and reliability of the wireless communication. If the printers support lower or different 802.11 standards than the wireless network, the architect may need to consider the impact of the compatibility issues, such as interference, congestion, or degradation4.

The other options are not as relevant for planning a wireless solution upgrade for printers. Whether the printers are physically locked down or not does not affect the wireless connectivity, unless the lock interferes with the antenna or signal reception. The identity of users who need to access printers is more related to the access control and user management policies, rather than the wireless solution design. Whether the printers support PoE or not does not affect the wireless connectivity, unless the power source is unreliable or insufficient.

References:

• 1: https://www.arubanetworks.com/techdocs/ArubaOS_86_Web_Help/Content/arubaos-solutions/1-overview/802.1x.htm
• 2: https://www.arubanetworks.com/techdocs/ArubaOS_86_Web_Help/Content/arubaos-solutions/1-overview/securing-wireless-access.htm
• 3: https://www.arubanetworks.com/techdocs/ArubaOS_86_Web_Help/Content/arubaos-solutions/1-overview/802.11-standards.htm
• 4: https://www.arubanetworks.com/techdocs/ArubaOS_86_Web_Help/Content/arubaos-solutions/1-overview/compatibility-issues.htm

The customer wants to use certificates to authenticate user devices, which means that they need a strong and secure method of verifying the identity of the devices that connect to the employee WLAN. The best option for this is to use EAP-TLS instead of PEAP-MSCHAPv2. EAP-TLS stands for Extensible Authentication Protocol-Transport Layer Security, and it is a protocol that uses certificates on both the client and the server side to establish a mutual authentication and a secure channel for data exchange. EAP-TLS is considered the most secure EAP method, as it prevents common attacks such as dictionary attacks, man-in-the-middle attacks, and replay attacks.

The other options are not suitable for the customer requirements:

• Option B is incorrect because TKIP encryption is weaker than AES encryption. TKIP stands for Temporal Key Integrity Protocol, and it is an older encryption method that was designed to replace WEP, which had serious security flaws. However, TKIP also has some vulnerabilities, and it is not recommended for modern WLANs. AES stands for Advanced Encryption Standard, and it is a newer and stronger encryption method that provides better security and performance for WLANs.
• Option C is incorrect because WPA2-PSK is less secure than WPA2-Enterprise. WPA2-PSK stands for Wi-Fi Protected Access 2-Pre-Shared Key, and it is a security mode that uses a common passphrase or key to authenticate all devices that connect to the WLAN. However, this passphrase or key can be easily compromised or shared, and it does not provide individual authentication or encryption for each device. WPA2-Enterprise stands for Wi-Fi Protected Access 2-Enterprise, and it is a security mode that uses a RADIUS server to authenticate each device individually and dynamically generate encryption keys for each session. WPA2-Enterprise provides better security and scalability for WLANs.
• Option D is incorrect because TTLS does not use certificates to authenticate user devices. TTLS stands for Tunneled Transport Layer Security, and it is a protocol that uses certificates only on the server side to establish a secure tunnel for data exchange. The client side can use different methods to authenticate, such as passwords, tokens, or certificates. However, TTLS does not require certificates on the client side, and it is less secure than EAP-TLS.

References:

• ArubaOS 8.5 User Guide)
• ArubaOS 8.5 Security Guide)
• Aruba Certified Design Professional Official Certification Study Guide (HPE6-A47))

In a high-client device turnover environment like an airport, the network management and monitoring solution needs to handle a large number of devices connecting and disconnecting frequently. This can put a significant load on the system. Therefore, it would be beneficial to recommend additional hardware resources beyond those typically recommended for the AirWare platform. This would ensure that the system can handle the high turnover and provide reliable service1.

References:

• Solution Architect - Scaled Agile Framework

This answer is correct because it matches the scenario for which the Aruba backplane stacking technology is designed. Aruba backplane stacking technology allows up to 10 switches to be interconnected using high-speed backplane cables, creating a single logical device with a single IP address and configuration. This simplifies the management and operation of the network, as well as the redundancy design, as the stack can operate in ring or chain topology and provide fast failover in case of link or switch failure. This technology is suitable for customers who need to deploy a pair of aggregation switches in the same closet, as it reduces the number of devices and links to manage, and provides high availability and scalability for the network.

The other options are incorrect because:

• B. The customer needs to simplify the deployment of core switches which are located in different closets for redundancy purposes. This scenario is not suitable for Aruba backplane stacking technology, as it requires the switches to be physically close to each other and connected with backplane cables. A better option for this scenario would be to use Aruba Virtual Switching Framework (VSF) technology, which allows up to twoswitches to be interconnected using standard Ethernet links, creating a virtual switch that can span across different closets or racks.
• C. The customer needs to expand the network and make it possible for the current core switches to support more MAC forwarding and ARP entries. This scenario is not suitable for Aruba backplane stacking technology, as it does not increase the MAC or ARP table size of the switches. The MAC and ARP table size is determined by the hardware specifications of each switch model, and stacking them together does not change that. A better option for this scenario would be to upgrade the core switches to a higher-end model that supports more MAC and ARP entries, or to segment the network into smaller subnets to reduce the MAC and ARP traffic.
• D. The customer needs to deploy a switch at a branch office and have the switch automatically discover and join the network stack at the main office. This scenario is not suitable for Aruba backplane stacking technology, as it requires the switches to be on the same LAN and connected with backplane cables. A better option for this scenario would be to use Aruba Central, which is a cloud-based management platform that allows remote provisioning and monitoring of Aruba switches and other devices. Aruba Central can automatically discover and join the switch to the network, and apply the configuration and policies from the main office.

References:

• Aruba 2930M Switch Series - Data sheet)
• ArubaOS-Switch Virtual Switching Framework - Configuration guide)
• Aruba Central - Data sheet)

SmartLink is a technology that provides fast failover for access switches connected to the core VSF fabric. It detects link failures on the uplink ports and switches to the backup link within 50 ms. It also shuts down the primary link to prevent loops. SmartLink works with any routing protocol and does not require any additional configuration on the core switches. OSPF graceful restart is a feature that allows OSPF to continue forwarding traffic during a planned or unplanned restart of the routing process. However, it does not provide fast failover for link or device failures. BGP is a routing protocol that is mainly used for inter-domain routing and does not provide fast failover for link or device failures. VRRP is a protocol that provides redundancy for routers by creating a virtual router with a shared IP address. However, it does not provide fast failover for link or device failures. References: ArubaOS-Switch Management and Configuration Guide for WC.16.10), Aruba Validated Design: Campus Wired LAN)