Selected HPE6-A90 HPE Networking Questions Answers

Technical explanation

Run tests and, where authorized, command sessions from Troubleshooting so their timestamps, device context and results appear in History. The session record allows comparison before and after an intervention and can be exported as operational evidence. For accountability, also consult Audit Trail, which records administrative actions rather than being a substitute for diagnostic output. Preserve results externally when a regulatory or investigation retention period exceeds Central's operational history retention window. Central records troubleshooting sessions under Troubleshoot > History; select a session ID to read its outputs and any associated notes.

A configuration-change event cannot replay the output of a cable test or ping. The site timeline helps correlate incidents but is not a test archive. History contains prior sessions and can be reviewed for repeated diagnostics or handover.

Official HPE references | Troubleshooting Tools • Troubleshooting History | Study-guide topic: Network Management with HPE Aruba Networking Central

Technical explanation

The timeline allows metrics and events to be viewed within the same historical period as the reported slowdown, making temporal correlation possible. Compare interface throughput, link errors, CPU alarms, client health and configuration changes for the chosen window. A coincident alert is only a lead; corroborate a causative relationship through device counters or reproducible symptoms. The Hardware card is best for component condition, and the Connectivity card may expose the metrics, but the time-range widget is what makes historical comparison practical.

Hardware inventory does not reveal the past throughput curve. Connectivity data is useful only when viewed at the required period; the Timeline widget is the explicit control for changing the observation window.

Official HPE references | Device Health Card • Troubleshooting Tools | Study-guide topic: Managing Wired Networks with HPE Aruba Networking Central

Technical explanation

Use LACP to bundle four physical uplinks into one logical LAG, with consistent speeds, VLAN configuration and link settings on both endpoints. The port-channel distributes traffic across members according to a hashing algorithm, so a single conversation does not necessarily multiply its own throughput by four. The bundle also preserves connectivity when one member fails if sufficient links remain active. Verify the partner system ID, active member count, collecting/distributing state and any minimum-links requirement before production cutover. The aggregate offers more total bandwidth, but any single flow may remain limited to one physical member depending on the hash. Confirm matching LACP mode, allowed VLANs and MTU at both ends.

Turning off STP on four unmanaged parallel L2 links creates an obvious loop risk. Four independent VLAN access ports do not aggregate throughput for the same logical connection. LACP forms one port-channel and detects member mismatches.

Official HPE references | Creating a Port Profile for Switches • VSX and VSF Connectivity Design - Validated Solution Guide | Study-guide topic: Managing Wired Networks with HPE Aruba Networking Central

Technical explanation

DPI identifies traffic according to application signatures and behavioral characteristics beyond traditional IP-address, port and protocol matches. That classification enables role-based rules and QoS decisions for applications such as collaboration, streaming or file sharing, even when services reuse common transport ports. DPI should not be equated with universal SSL interception; decryption requires separate, explicit capabilities and trust arrangements. Nor does it perform DHCP address allocation or Wi-Fi channel selection, which belong to different network subsystems.

DHCP relaying and RF channel selection are separate functions. Decrypting arbitrary SSL traffic is not implied by DPI; that would require additional TLS-interception capabilities and trust. DPI is useful because recognized application identities can be inputs to traffic policy.

Official HPE references | Application Visibility • AOS-10 Cloud Services | Study-guide topic: Introduction to AOS-10