The current IT staff is used to working with legacy Aruba OS-S (ProCurve> equipment. They are worried that they cannot handle Aruba OS-CX switches due to the different command syntax. What are two ways to make the transition easier for them? (Select two.)
Based on the requirements provided by 'Don't Buy at Us,' the updated design needs to accommodate 25GbE uplinks and a minimum of 7 stacks of 48-port Aruba switches for the EMEA-DISTR. Option C is the most suitable based on best practices, as it proposes:
A core configuration consisting of two Aruba 8360-12C in VSX for the collapsed core with ISL of 2x100GbE DAC, which will provide robust core networking with high-speed interconnects, suitable for the demands of a regional distribution center and headquarters.
Aggregation with two stacks, each with 2 Aruba 8360-12C in VSX (ISL 2x100GbE DAC), accommodating the uplink capacity requirements.
Access stacks with a total of 17 stacks of Aruba 6300F 48-port 1GbE Class 4 PoE with 4-port SFP56 (each stack has 4 members, VSF with 50GbE VSF links, 2 x 25GbE uplinks per stack), which exceeds the minimum requirement of 7 stacks and provides the necessary uplink bandwidth.
This configuration supports the 25GbE uplink speeds, satisfies the required number of switch stacks for the EMEA distribution center, and is compatible with the existing 25GbE-certified fiber infrastructure at HQ2 and EMEA-DISTR.
Quentin
1 days agoYaeko
6 days agoGail
9 days ago