Study guide

3.2 VSF Split Detection, Failover, and Auto-Stacking

HPE Aruba Networking Certified Associate - Campus Access HPE6-A85

Track your progress as you read

Finished sections get a check mark.

1 Introduction: HPE6-A85 Exam Overview

HPE6-A85 Exam Facts and Current Blueprint

2 Chapter 1: Network Stack Fundamentals

1.1 OSI Reference Model and Encapsulation 1.2 TCP/IP Protocol Suite and IP Headers 1.3 Layer 2 Operation, ARP, and 802.1Q Tagging

3 Chapter 2: Physical Connectivity and Host Addressing

2.1 Ethernet Media and Transceiver Standards 2.2 Power over Ethernet (PoE, PoE+, PoE++) Standards and Budgeting 2.3 LLDP, LLDP-MED, and Voice VLAN Configuration 2.4 Host IP Addressing and DHCP Relay Operations

4 Chapter 3: Network Resiliency and Virtualization

3.1 Virtual Switching Framework (VSF) Architecture and Topologies 3.2 VSF Split Detection, Failover, and Auto-Stacking 3.3 Virtual Switching Extension (VSX) Architecture and Operations 3.4 High-Availability Gateways: VRRP and VSX Active-Gateway

5 Chapter 4: AOS-CX Architecture and Switch Operation

4.1 AOS-CX Hardware Portfolio and State Database Architecture 4.2 Network Analytics Engine (NAE) and Automated Telemetry 4.3 AOS-CX Interface Configuration and Port Control 4.4 Link Aggregation (LAG) and LACP Configuration

6 Chapter 5: Layer 2 Protocols and Spanning Tree

5.1 AOS-CX VLAN Configuration and Native VLAN Handling 5.2 Spanning Tree Protocols: STP, RSTP, and MSTP 5.3 Spanning Tree Protections and Loop Prevention 5.4 MAC Address Table Learning, Aging, and Forwarding

7 Chapter 6: Wireless Fundamentals, Standards, and RF

6.1 IEEE 802.11 Standards and Wi-Fi Generations 6.2 RF Fundamentals, Signal Propagation, and Channel Design 6.3 Aruba Access Point Hardware Portfolio and Suffix Conventions 6.4 WLAN Topologies, BSSID/ESSID, and Roaming Standards

8 Chapter 7: Aruba Wireless Architecture and Management

7.1 AOS 10 Architecture and Aruba Central Integration 7.2 Wireless Forwarding Modes: Bridge vs Tunnel Mode 7.3 Automated RF and Client Optimization: AirMatch and ClientMatch 7.4 Secure Wireless Access: WPA3, SAE, and MPSK Implementation

9 Chapter 8: IP Routing Fundamentals and OSPF

8.1 IP Routing Principles and Packet Forwarding 8.2 OSPFv2 Protocol Mechanics and Adjacency Formation 8.3 OSPF Designated Routers and Multi-Area Deployments 8.4 ECMP, Static Routing, and VRF Isolation

10 Chapter 9: Campus Network Security and Segmentation

9.1 DHCP Snooping and Dynamic ARP Inspection 9.2 Port Security and MAC Address Limiting 9.3 ClearPass Policy Management and RADIUS Change of Authorization 9.4 Dynamic Segmentation, User-Based Tunneling, and Policy Enforcement

11 Chapter 10: Authentication, Authorization, and Accounting

10.1 The AAA Framework and Architecture 10.2 802.1X Authentication and EAP Methods 10.3 MAC Authentication and Captive Portal Onboarding 10.4 Administrative Access Control: RADIUS vs TACACS+

12 Chapter 11: Network Management and Telemetry

11.1 Aruba Central Cloud Architecture and Group Configuration 11.2 Zero-Touch Provisioning (ZTP) and Aruba Activate 11.3 AI Insights and Aruba User Experience Insight (UXI) 11.4 Network Telemetry, Streaming APIs, and SNMP/Syslog

13 Chapter 12: Troubleshooting the Solution

12.1 Structured Troubleshooting Methodologies and Scope Isolation 12.2 AOS-CX Layer 2 and Interface Diagnostic Commands 12.3 Layer 3, IP Services, and End-to-End Diagnostics 12.4 Physical-Layer Troubleshooting 12.5 Troubleshooting Wireless Clients and Network Access

14 Chapter 13: Optimizing Performance: QoS, Baselines, and Comparisons

13.1 Quality of Service (QoS) Classification and Marking 13.2 Queuing Algorithms and Congestion Management 13.3 Traffic Policing, Shaping, and Broadcast Rate Limiting 13.4 Establishing a Performance Baseline 13.5 Comparing Results to the Baseline

15 Chapter 14: Plan the Solution

14.1 Analyzing the Current Environment 14.2 Interpreting an Architect's High-Level Design 14.3 Creating a Low-Level Design 14.4 Preparing for Implementation

16 Chapter 15: Validate and Operate the Solution

15.1 Validating the Solution 15.2 Performing Firmware Updates 15.3 Making Basic Ongoing Configuration Changes 15.4 Maintaining Network Documentation

3.2 VSF Split Detection, Failover, and Auto-Stacking

Key Takeaways Explain This Topic AI

A VSF stack split leaves two fragments that can both try to forward with the same MAC and IP addresses, which is why chain topologies need split detection.

AOS-CX VSF split detection uses the management (OOBM) interfaces of the primary and secondary members, configured with vsf split-detect mgmt .

When fragments are discovered, the fragment containing the primary member (member 1) always wins, and the losing fragment brings down all its non-VSF interfaces.

The losing fragment's interfaces stay down until the stack is reconnected or the primary fragment goes down; the primary fragment's interfaces always stay up.

Auto-stacking lets factory-default switches join through the reserved VSF ports (for example ports 49 and 50 on 48-port models), receiving the lowest free member ID and rebooting into the stack.

Last updated: October 2026

3.2 VSF Split Detection, Failover, and Auto-Stacking

Virtual Switching Framework (VSF) makes several physical switches act as one, which is convenient until the stack loses the links that hold it together. This section covers the failure cases you are expected to recognize on HPE6-A85: what a stack split is, how AOS-CX split detection limits the damage, how the Conductor and Standby roles fail over, and how auto-stacking and VSF in-service software upgrade (ISSU) simplify operations. All behavior described here comes from the AOS-CX 10.14 VSF Guide for the 6200 and 6300 switch series.

Why a Split Is Dangerous

A VSF stack shares one configuration, one management IP address, and one set of system MAC addresses. In a chain topology there is only one path between any two members, so a single VSF link or member failure can divide the stack into two fragments .

Consider a four-member chain: member 1 (primary, Conductor), member 2 (secondary, Standby), members 3 and 4. If the VSF link between members 2 and 3 fails:

Members 1 and 2 remain together. Member 1 is still the Conductor.

Members 3 and 4 lose contact with both the Conductor and the Standby.

If both fragments kept their front-panel ports active, the network would see the same router MAC, gateway IP addresses, and LACP system ID from two places. Upstream switches would see MAC moves, LAGs could mis-hash, and clients could receive conflicting ARP replies.

A ring topology avoids most of this: every member has two VSF links, so any single link or member failure leaves a path between the survivors and the ring simply operates as a chain. HPE strongly recommends rings whenever feasible. Split detection is the safety net for the failures a ring cannot absorb, and the main protection for chains.

Terminology note: Older documents and other vendors call this "split-brain" protection or "multi-active detection (MAD)". On AOS-CX VSF the command and the documentation use split detection .

How AOS-CX Split Detection Works

AOS-CX VSF supports split detection over the management interfaces of the primary and secondary members:

Connect the mgmt ports of the primary (member 1) and secondary members to the same Layer 2 network. They can also be cabled directly to each other.

Enable the method once for the stack: switch(config)# vsf split-detect mgmt

Remove it with no vsf split-detect .

If a split occurs and the primary and secondary end up in different fragments, the secondary's fragment uses the management connection to learn that the primary fragment is still operational. The decision rule is fixed:

Fragment Result

Contains the primary member (member 1) Always wins. All interfaces stay operational.

Does not contain the primary (for example, the secondary's fragment) Brings down all front-plane non-VSF interfaces to avoid duplicate MAC and IP addresses.

The losing fragment's interfaces remain down until the stack is reconnected or the primary fragment goes down . Management access through the console and the management interface remains available so you can investigate.

Use show vsf to check the stack. The output includes the topology (Ring or Chain), the stack status (for example "No Split" or "Active Fragment"), and the configured split detection method ("None" or "mgmt"). switch# show vsf

  • Force Autojoin : Disabled
  • Autojoin Eligibility Status: Not Eligible
  • MAC Address : 38:21:c7:5d:d0:c0
  • Secondary : 2
  • Topology : Ring
  • Status : No Split
  • Split Detection Method : mgmt

Additional commands such as show vsf detail , show vsf link , and show vsf topology help you trace which link failed.

Conductor and Standby Failover

Failover depends on the role that was lost:

Event What happens

A member (not primary or secondary) fails Its ports go down; the rest of the stack keeps running. In a ring, the remaining members stay connected.

The Conductor fails or becomes unreachable The Standby automatically assumes the Conductor role, because it already holds a synchronized copy of the configuration database.

The Standby fails The Conductor keeps running; the stack has no control-plane backup until the secondary returns.

No secondary member is configured Losing the Conductor stops the stack's control plane, which is why HPE recommends always configuring vsf secondary-member .

Design tips that follow from these rules:

Take uplinks from both the primary and the secondary member (for example a cross-stack LAG), so either one can carry traffic.

Connect both management ports to the management network so management access and split detection survive the loss of one member.

Prefer a ring so a single failure does not create fragments.

Auto-Stacking

Building a stack manually means logging in to each switch, configuring VSF links, and renumbering. Auto-stacking reduces this to cabling:

A switch with a factory-default configuration is "auto-join eligible".

Connect it to a VSF link port of an existing stack member. Most models reserve two ports for auto-stacking: ports 13 and 14 on 12-port models, 25 and 26 on 24-port models, and 49 and 50 on 48-port models.

Peer discovery runs from the Conductor. The new switch replies with its eligibility, MAC address, and part number.

The Conductor adds the member and link configuration automatically, assigns the lowest available member ID , and the new switch reboots and joins the stack.

A switch that is no longer at factory default is not auto-join eligible; you can configure its links and member number manually instead, or use the documented force auto-join option. The stack configuration is stored separately from the startup configuration, so erase startup-config does not break the stack; erase all zeroize returns all members to factory default.

Upgrading a VSF Stack

A standard upgrade reboots the stack. On the CX 6300 , VSF ISSU ( issu update-software ) upgrades the Conductor, Standby, and members with minimal downtime by keeping the data plane forwarding while the control plane is upgraded. It applies to upgrades between minor releases, so always read the release notes before choosing the method.

Common Exam Traps

The primary always wins. Split resolution does not compare priorities or uptime; the fragment with member 1 keeps its ports up.

Only mgmt split detection. AOS-CX VSF split detection uses the management interfaces of the primary and secondary members; do not pick LLDP- or data-port-based answers for VSF.

Losing fragment = non-VSF ports down. The losing fragment does not reboot or erase its configuration; it disables its front-plane non-VSF interfaces until the stack is rejoined or the primary fragment goes away.

Loading diagram... VSF Split Detection Decision Flow