The show system resources command is the correct and standard command used in the ArubaOS-CX command-line interface (CLI) to display a summary of system resource utilization. The output of this command provides essential performance metrics, including the overall CPU utilization (broken down into user, system, and idle percentages) and the total, used, and free memory on the switch. This command gives a quick, high-level overview of the switch's health and current load.

B. The display command syntax is not used in ArubaOS-CX; it is characteristic of other vendor operating systems like HPE Comware.

C. show hardware utilization is not a valid command in the ArubaOS-CX CLI. Hardware status is checked with different show hardware sub-commands.

D. show process status is not a valid ArubaOS-CX command. To view CPU usage per process, the command show system processes-cpu is used.

1. HPE Aruba. (2023). ArubaOS-CX 10.12 Command-Line Interface Guide. Part Number: 5200-8121a.

Page 2298

"show system resources": The guide explicitly states

"Displays the system resource utilization information such as CPU and memory utilization." This directly confirms that option A is the correct command for the described purpose. The guide's command index also confirms the non-existence of the commands listed in options B

C

and D.

The Aruba CX 8400 Switch Series is a high-performance, modular core and aggregation switch designed for demanding campus and data center networks. It supports a variety of line cards, including modules with high-density 100GbE QSFP28 ports, making it the only option listed that provides high-speed 100GbE interconnects. The other switch series listed are primarily designed for access or aggregation roles and support lower uplink speeds, such as 10GbE, 25GbE, or 50GbE, but not 100GbE.

A. The Aruba CX 6200 is an access layer switch series that supports a maximum uplink speed of 10GbE SFP+.

C. The Aruba CX 6300 is a stackable access and aggregation switch series with uplink speeds up to 50GbE SFP56.

D. The Aruba CX 4100i is a ruggedized access switch series designed for IoT, with uplink speeds limited to 1GbE SFP.

1. Aruba CX 8400 Switch Series Datasheet: "The Aruba CX 8400 Switch Series is a modern

intelligent

and high-availability modular switch... with line rate 10GbE

25GbE

40GbE and 100GbE." (Page 1

Overview). The datasheet also lists specific modules like the "8-port 40/100GbE QSFP28 (LSW1C80) module" and "8-port 100GbE QSFP28 (LSW1C81) module". (Page 4

Table: Aruba 8400X Series line cards).

2. Aruba CX 6300 Switch Series Datasheet: "Built-in 1/10/25/50 GbE uplinks..." (Page 1

Product Highlights). The models table confirms SFP ports supporting up to 50G.

3. Aruba CX 6200 Switch Series Datasheet: "Built-in 1/10GbE uplinks..." (Page 1

Product Highlights). The models table confirms SFP+ ports supporting 1G/10G.

4. Aruba CX 4100i Switch Series Datasheet: "Convenient built-in 1GbE uplinks..." (Page 1

Product Highlights). The models table confirms SFP ports supporting 1G.

The Aruba Network Analytics Engine (NAE) is an on-box framework for Aruba CX switches that enables automated monitoring and troubleshooting. NAE uses scripts and agents to monitor switch components and network conditions. When a predefined condition is met, it can automatically collect diagnostic data or trigger corrective actions, feeding this information back to Aruba Central for analysis.

Aruba Central's alerting framework functions on event-based triggers. Administrators can configure alerts for specific switch events (e.g., high CPU utilization, port flaps). When an event occurs, it triggers an automated action, such as sending a notification or initiating a webhook to an external system, which can be used to start an automated troubleshooting workflow.

B. Dynamic Segmentation: This is a security feature that unifies policy enforcement across wired and wireless networks using user roles, not a tool for automated troubleshooting of switch hardware or software issues.

D. Smart Rate Ports: This is a hardware feature that allows Ethernet ports to operate at multiple speeds (1, 2.5, 5, 10 Gbps). It relates to physical connectivity, not automated troubleshooting software.

1. ArubaOS-CX 10.11 Network Analytics Engine Guide

Page 6: "The Aruba Network Analytics Engine (NAE) provides a framework for switch monitoring and troubleshooting. NAE enables you to detect network problems in near real time

and to analyze problems to determine their root cause... NAE agents are scripts that are triggered by the state of some condition in the switch."

2. Aruba Central User Guide (2024-02-27)

"Managing Alerts & Events" section

"Configuring Alerts" subsection: "Aruba Central supports configuring alerts to notify you when a critical event is detected in the network... You can configure alerts for a wide range of events and conditions... When an alert is generated

Aruba Central can send notifications through email

webhook

or other third-party applications." This describes the event-based trigger mechanism for automated notifications and actions.

3. ArubaOS-CX 10.11 Fundamentals Guide

Page 21: "Dynamic Segmentation simplifies and secures the network by creating a single

unified policy for both wired and wireless clients." This confirms its role as a security and policy feature.

This command sets the Link Aggregation Group to use LACP in 'active' mode. In LACP, the operational mode (active or passive) is a property of the logical aggregate interface (the group), not the individual physical member ports. Setting the LAG to 'active' mode is the essential step to enable the switch to actively initiate LACP negotiations on all member ports. While the specific command syntax lacp group 1 mode active is not native to ArubaOS-CX, it correctly represents the concept of enabling LACP at the group level, which is the most accurate choice among the options provided. The correct ArubaOS-CX command is lacp mode active under the interface lag context.

A. LACP mode is not configured on physical interfaces, and 'enable' is not a valid LACP mode; 'active' or 'passive' are used.

C. channel-group is Cisco-specific syntax, and the 'auto' mode typically refers to the proprietary PAgP protocol, not the industry-standard LACP.

D. The LACP mode is a property of the logical LAG interface, not configured directly on a physical member port in ArubaOS-CX.

1. ArubaOS-CX 10.12 Fundamentals Guide

Page 268

"Configuring a static LACP LAG". The official documentation shows that LACP is enabled on the logical LAG interface

not the physical port. The command is lacp mode active or lacp mode passive within the interface lag configuration context. This supports the reasoning that the mode is a group-level property

making option B the most conceptually correct answer.

Document Snippet: "The LACP mode can be configured as active or passive. The default mode is passive. switch(config)# interface lag 1 switch(config-lag-if)# lacp mode active"

2. ArubaOS-CX 10.12 Link Aggregation Guide

Page 10

"LACP modes". This guide explicitly states

"LACP can be configured in active or passive mode on a LAG interface." This confirms that the LACP mode is set on the LAG interface itself

reinforcing that options attempting to configure it on a physical port (A and D) are incorrect.

In ArubaOS-CX, to redistribute routes from one protocol into another, you enter the configuration context of the destination routing protocol. For redistributing static routes into OSPF, an administrator would first enter the OSPF router configuration mode (router ospf ). Within this context, the redistribute static command is used to import all static routes into the OSPF process, which then advertises them as Type 5 AS-External LSAs (or Type 7 if in an NSSA) to other OSPF routers.

B. ip ospf static redistribute: This is an invalid command syntax. ip ospf commands are typically applied at the interface level to configure OSPF parameters for that specific interface, not for global redistribution.

C. ospf inject static: The keyword inject is not used for this purpose in the ArubaOS-CX command-line interface. The correct and standard keyword is redistribute.

D. route redistribution static: This is an incorrect command structure. Redistribution is configured from within the routing protocol that is receiving the routes, not as a separate global route command.

1. ArubaOS-CX 10.12 Multicast and Routing Guide

Page 161

"Redistributing routes into OSPF". The guide explicitly lists the command syntax: redistribute {bgp | connected | rip | static | ospf } [route-map ]. The example for static routes confirms the usage.

2. ArubaOS-CX 10.10 Fundamentals Guide

Page 318

"Redistributing routes". This section states

"Redistribution is configured within a routing protocol using the redistribute command." It provides a clear example: switch(config-ospf-1)# redistribute static.

The Aruba Network Analytics Engine (NAE) is a built-in framework unique to the ArubaOS-CX operating system. It provides deep network visibility by allowing administrators to monitor and troubleshoot network, system, and application issues using simple scripts called agents. These agents collect and analyze real-time and historical data from an on-box time-series database. Based on this analysis, NAE can be configured to automatically trigger actions, such as sending alerts or making configuration changes, thus providing a powerful combination of real-time visibility and automation directly on the switch.

A. Smart Rate Ports: This is a hardware feature that provides flexible, multi-gigabit port speeds (1/2.5/5/10GbE) over standard cabling, not an analytics or automation function.

C. NetEdit: This is a centralized software solution for orchestrating configuration, validation, and deployment across multiple Aruba CX switches, not a real-time, on-box analytics engine.

D. Virtual Switching Framework (VSF): This is a stacking technology that allows multiple physical switches to be combined and managed as a single logical device, simplifying network topology and management.

1. ArubaOS-CX 10.12 Network Analytics Engine Guide

Chapter 1

"Introduction to the Network Analytics Engine"

Page 5. "The Aruba Network Analytics Engine (NAE) is a first-of-a-kind

built-in framework for network monitoring and troubleshooting. NAE provides the ability to monitor and troubleshoot network

system

and application-related problems through a simple scripting engine and the REST API... NAE agents can be configured to perform actions based on the state of the network."

2. Aruba CX 6300 Switch Series Data Sheet

Page 3

"Software-defined networking" section. "Aruba Network Analytics Engine (NAE) - This industry-first provides the ability to monitor and troubleshoot network

system

application and security related issues easily

through simple python agents and REST APIs. This powerful

built-in

distributed and customizable engine provides advanced telemetry and automation..."

3. ArubaOS-CX Fundamentals Guide

Chapter "Network Analytics Engine"

Section "NAE overview". "The Network Analytics Engine provides visibility into the network by monitoring the switch and performing root cause analysis of network issues. The Network Analytics Engine also provides automation capabilities by running scripts that are triggered by network events."

The Aruba CX 6200 and CX 6300 series are specifically designed for the network access layer. The CX 6200 series provides fixed 1/10GbE SFP+ uplinks, which are considered high-speed for access deployments. The CX 6300 series offers even more flexibility and higher performance with up to 10/25/50GbE uplinks, making it a robust choice for modern access layer requirements. Both series are positioned within the Aruba portfolio to serve campus edge and branch access roles, connecting end-user devices and IoT while providing high-speed connections to the aggregation or core layer.

B. Aruba CX 8400: This is a high-availability modular chassis switch designed for the campus core and aggregation layers, not for access layer deployments.

D. Aruba CX 8325: This is a high-performance fixed-configuration switch intended for use as a campus core/aggregation switch or a data center Top-of-Rack (ToR) switch.

1. Aruba CX 6200 Switch Series Data Sheet (Document ID: DSCX6200Series

Published: March 2023)

Page 1: "The Aruba CX 6200 Switch Series is a next-gen family of stackable access switches... This series has built-in 1/10GbE uplinks and up to 740W of PoE to support IoT devices..."

2. Aruba CX 6300 Switch Series Data Sheet (Document ID: DSCX6300Series

Published: March 2023)

Page 1: "The Aruba CX 6300 Switch Series is a modern

flexible

and intelligent family of AOS-CX stackable switches ideal for access

aggregation

and data center top-of-rack (ToR) deployments... with high-speed 10GbE/25GbE/50GbE uplinks."

3. Aruba CX 8400 Switch Series Data Sheet (Document ID: DSCX8400Series

Published: March 2023)

Page 1: "The Aruba CX 8400 Switch Series is a modern

intelligent and high-availability modular solution ideal for use in the campus core and aggregation."

4. Aruba CX 8325 Switch Series Data Sheet (Document ID: DSCX8325Series

Published: March 2023)

Page 1: "The Aruba CX 8325 Switch Series is a campus core and aggregation switch series ideal for enterprise campus and data center deployments."

The Aruba CX 9300 and CX 8325 switch series are specifically designed and recommended for data center leaf-spine architectures. The CX 9300 series offers high-density 100GbE/400GbE connectivity, making it an ideal choice for high-performance spine or leaf roles. The CX 8325 series provides flexible high-density 1/10/25/40/100GbE ports, positioning it as a versatile and powerful switch for both leaf and spine deployments in modern data centers. Both series are built on a non-blocking, distributed architecture required for the high east-west traffic demands of a leaf-spine fabric.

A. Aruba CX 10000: This is a specialized Distributed Services Switch with an integrated DPU for stateful services. While used as a Top-of-Rack leaf, it's not a general-purpose recommendation for a standard leaf-spine fabric.

C. Aruba CX 6300: This series is primarily designed for campus access and aggregation roles. It lacks the high-performance, non-blocking architecture and port density typically required for data center spine or demanding leaf roles.

1. Aruba CX 9300 Switch Series Data Sheet: "The Aruba CX 9300 Switch Series is a next-generation 100GbE/400GbE data center switch designed for spine-and-leaf architectures that require high-performance server connectivity..." (Page 1

Overview).

2. Aruba CX 8325 Switch Series Data Sheet: "It is ideal for use as a spine or leaf switch in modern data centers that require high performance and a non-blocking architecture." (Page 1

Product overview).

3. Aruba Data Center Networking Solution Overview: This document frequently positions the CX 8325 and CX 9300 as the core components for leaf-spine fabrics. For example

in topology diagrams

the CX 9300 is shown as a spine and the CX 8325 as a leaf. (Page 5

Figure 2: Aruba CX switching for modern data centers).

4. Aruba CX 6300 Switch Series Data Sheet: "The Aruba CX 6300 Switch Series is a modern

flexible

and intelligent family of AOS-CX stackable switches ideal for access

aggregation

and data center Top-of-Rack (ToR) deployments." (Page 1

Product overview). This highlights its primary role is outside the core leaf-spine fabric

though it has ToR applicability.

The command clear mac-address-table dynamic is used in ArubaOS-CX to remove all dynamically learned MAC address entries from the forwarding database (MAC table). This action forces the switch to relearn the MAC addresses of connected devices as they transmit frames. This is a standard administrative procedure for troubleshooting Layer 2 connectivity issues or clearing stale entries after network topology changes. The dynamic keyword specifically targets entries learned through traffic observation, leaving any statically configured MAC addresses untouched.

B. The verb delete and the object name mac-table are not the correct syntax for this operation in the ArubaOS-CX command-line interface.

C. The verb flush is not used for clearing the MAC address table in ArubaOS-CX; the correct command verb is clear.

D. The correct object name is mac-address-table, not mac-table. This command is syntactically incorrect and would not be recognized by the switch.

1. ArubaOS-CX 10.12 Command-Line Interface Guide

Page 1

"clear mac-address-table" command section. The guide provides the full command syntax: clear mac-address-table [dynamic | ] [vlan ] [interface ]. The description for the dynamic parameter explicitly states it "Clears all dynamic MAC address entries."

2. ArubaOS-CX 10.10 Fundamentals Guide

Page 211

"Monitoring MAC addresses" section. The guide discusses viewing the MAC address table and mentions the clear mac-address-table command as the method for removing entries.

The ping command is a fundamental utility used to test Layer 3 reachability by sending ICMP echo requests to a target IP address and waiting for a reply. A successful reply confirms that a valid two-way IP path exists between the source and destination. The traceroute command is used to discover the Layer 3 path (the sequence of routers) that packets take to a network host. It helps identify routing loops or points of failure along the path by showing which hop is the last to respond. Both are essential tools for diagnosing IP connectivity issues.

show vlan: This command displays information about Layer 2 Virtual LANs. While VLAN configuration is crucial for network operation, this command verifies Layer 2 settings, not Layer 3 connectivity.

show clock: This command displays the system's current time and date. It is a system management command and is not used for troubleshooting network connectivity.

1. ArubaOS-CX 10.12 Command-Line Interface Guide

Page 1

"Troubleshooting commands" section.

ping: "Sends ICMPv4 or ICMPv6 echo request packets to a remote host to determine if the host is reachable."

traceroute: "Traces the path from the switch to a remote host."

2. ArubaOS-CX 10.12 Command-Line Interface Guide

Page 1

"VLAN commands" section.

show vlan: "Shows information for all configured VLANs

or for the specified VLANs." This confirms its function is related to Layer 2 VLANs.

3. ArubaOS-CX 10.12 Command-Line Interface Guide

Page 1

"System information commands" section.

show clock: "Displays the current system time." This confirms its function is unrelated to network troubleshooting.