HPE6-A47 Exam Dumps : Designing Aruba Solutions

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.

The customer needs a solution that can terminate VPN tunnels for Aruba RAPs, which are remote access points that connect to the corporate network over the Internet. The customer has only one public IP address, which means that they need to use NAT to forward the IPsec traffic to the device that will terminate the VPN tunnel. The customer also wants N+1 redundancy, which means that they need at least two devices that can act as backup for each other in case of failure.

The solution that meets the customer requirements is to use two Aruba MCs on the same subnet that use VRRP without clustering. VRRP stands for Virtual Router Redundancy Protocol, and it is a protocol that allows multiple devices to share a virtual IP address and act as a single gateway for the network. This way, the customer can use the virtual IP address as the public IP address for the NAT, and the IPsec traffic will be forwarded to the device that is the VRRP master. If the master device fails, the backup device will take over the role of the master and continue to terminate the VPN tunnels. This provides N+1 redundancy for the customer.

The other options are not suitable for the customer requirements:

• Option B is not suitable because a Layer 3 cluster requires two public IP addresses, one for each MC. The customer only has one public IP address, so they cannot use this option.
• Option C is not suitable because VRRP does not work across different subnets. The customer needs to have the MCs on the same subnet to use VRRP.
• Option D is not suitable because a Layer 2 cluster does not support NAT. The customer needs to use NAT to forward the IPsec traffic to the MCs.

References:

• Aruba Remote Access Point (RAP) Networks Validated Reference Design)
• Aruba Mobility Controller Virtual IP Configuration Guide)
• ArubaOS 8.5 User Guide)

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)