HPE6-A47 Exam Dumps : Designing Aruba Solutions

 A metal firewall is a significant RF obstacle that can be difficult to see visually and might require access to blueprints. A metal firewall is a type of fire-resistant barrier that is made of metal or metal-clad materials and is used to separate different sections of a building or a network. A metal firewall can block or attenuate RF signals that pass through it, causing coverage gaps, signal degradation, or interference in the wireless deployment. A metal firewall can also reflect RF signals, creating multipath fading or distortion in the wireless environment. Therefore, an architect needs to identify the location and thickness of any metal firewalls in the building and account for their impact on the RF design. A metal firewall may require additional access points, antennas, or cabling to provide adequate coverage and performance across the wireless deployment. A metal firewall may also affect the channel planning, transmit power settings, and antenna orientation of the access points and radios. A metal firewall can be difficult to see visually, as it may be hidden behind walls, ceilings, or floors, or blended with other materials.Therefore, an architect might need access to blueprints or other sources of information to locate and measure any metal firewalls in the building. References:

• RF Design | Validated Solution Guide - Aruba
• Managing and Optimizing RF Spectrum for Aruba WLANs | PDF - SlideShare
• RF Optimization - Aruba
• Advanced RF Design & Troubleshooting | PPT - SlideShare

The customer needs to upgrade their wireless network, which has a single large building with four floors. The customer requires 30 APs on each floor, totaling 120 APs for the whole building. The customer also wants to use a MM-based architecture, and deployone Aruba 7030 MC on each floor, with the MCs combined in a cluster for seamless client failover and roaming. However, the proposed solution does not meet the customer’s requirements, because the Aruba 7030 MC does not support enough APs for the customer’s needs. Each Aruba 7030 MC can only support up to 64 APs, which means that deploying one on each floor would not be enough to support all the required APs. The architect should explain this limitation to the customer, and suggest a different solution that can support more APs, such as using a higher-capacity MC model, or deploying more MCs per floor.

References:

• Aruba 7000 Series Mobility Controllers Data Sheet)
• ArubaOS 8.5 User Guide)
• Aruba Certified Design Professional Official Certification Study Guide (HPE6-A47))

The traditional guideline limits a wired VLAN to a /24 subnet, which provides enough IP addresses for 253 endpoints. You might have suggested one of three approaches: one VLAN per floor, one VLAN per building, or one VLAN per campus. The one VLAN per floor approach is not recommended because it interferes with roaming and adds complexity. If you did take this approach, the /24 subnets are not large enough for the requirements on every floor. You would need to ask for /23 subnets. The one VLAN per building approach would work if you considered each building its own RF domain. It provides roaming within a building and, if you are using a single cluster at the data center, between buildings. Ifyou deployed two MCs or clusters, one at each building, though, GRE tunneling would be required to support roaming between buildings.