Study guide
8.4 ECMP, Static Routing, and VRF Isolation
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
8.4 ECMP, Static Routing, and VRF Isolation
Key Takeaways Explain This Topic AI
Equal-Cost Multi-Path (ECMP) distributes traffic flows across multiple parallel, equal-metric next hops using a deterministic 5-tuple hash to prevent packet reordering.
Static routing in AOS-CX provides deterministic, low-overhead path selection; ip route <prefix> <next-hop> distance <1-255> sets the administrative distance (default 1).
Floating static routes provide automated backup connectivity by configuring an administrative distance higher than the primary dynamic routing protocol (e.g., AD of 120 or 200 vs. OSPF's 110).
Virtual Routing and Forwarding (VRF) creates independent logical routing tables within a single physical switch, ensuring complete Layer 3 isolation for multi-tenant, guest, and management environments.
The AOS-CX out-of-band management interface lives in the dedicated mgmt VRF; give it a gateway with default-gateway under interface mgmt and add vrf mgmt to ping and traceroute tests.
Last updated: October 2026
ECMP, Static Routing, and VRF Isolation
Quick Summary: Modern enterprise networks demand both high-capacity transit performance and strict security segmentation. Equal-Cost Multi-Path (ECMP) balances traffic across redundant uplinks simultaneously using 5-tuple hashing, maximizing throughput while preventing packet reordering. For predictable perimeter connectivity, static routing and floating static routes deliver dependable primary and fallback paths. At the architectural level, Virtual Routing and Forwarding (VRF) virtualizes the switch's routing table into isolated logical routing instances, preventing traffic leakage between corporate, guest, IoT, and management domains at Layer 3.
Equal-Cost Multi-Path (ECMP) Routing
In traditional spanning tree environments, redundant Layer 2 links are blocked to prevent bridging loops, leaving expensive bandwidth completely idle. At Layer 3, however, redundant routed paths can be utilized concurrently through Equal-Cost Multi-Path (ECMP) .
ECMP Requirements and Operational Mechanics
When a routing protocol (such as OSPF) or static configuration discovers multiple paths to the exact same destination prefix, ECMP activates under three strict conditions:
The destination prefix and subnet mask must be identical .
The Administrative Distance must be identical (routes learned from the same source).
The metric/path cost must be identical .
When these conditions are met, AOS-CX installs the equal-cost next hops into the hardware Forwarding Information Base (FIB), up to the platform's ECMP limit (a static route can have up to 32 next hops). +-------------------------+
- | Agg-Switch A (NextHop)| Cost: 20
- +-----> | 10.0.1.2/30 | ----------+
- | +-------------------------+ |
- [ Access Switch ] -----+ +-----> [ Core / WAN ]
- | +-------------------------+ |
- +-----> | Agg-Switch B (NextHop)| ----------+
- | 10.0.2.2/30 | Cost: 20
- +-------------------------+
- The 5-Tuple Hashing Algorithm
A critical challenge in multi-path forwarding is ensuring that packets belonging to the same TCP or UDP dialogue do not arrive out of order. If a switch load-balanced packets using simple round-robin distribution (Packet 1 to Path A, Packet 2 to Path B), slight latency differences between links would cause packets to arrive out of sequence, triggering TCP window collapse, retransmissions, and severe application degradation.
To prevent this, AOS-CX switches implement deterministic per-flow 5-tuple hashing in the switch ASIC. The hash function inputs five header fields:
- Source IP Address
- Destination IP Address
- IP Protocol (e.g., TCP = 6, UDP = 17)
- Source Layer 4 Port
- Destination Layer 4 Port
Because all packets within a specific TCP/UDP flow have identical 5-tuple values, the mathematical hash generates the exact same numerical result. Consequently, all packets for that flow are consistently forwarded over the same physical next-hop link , guaranteeing sequential packet delivery while evenly distributing hundreds of concurrent client flows across all available paths.
Static Routing and Floating Static Routes
While dynamic routing protocols like OSPF are preferred across enterprise core and aggregation layers, static routing remains vital at network perimeters, branch offices, and firewall handoffs.
Standard Static and Default Routes
A static route maps a destination network to a specific next-hop IP address or egress interface:
Specific Static Route: Directs traffic destined for a particular remote subnet ( ip route 10.50.0.0/16 10.0.1.2 ).
Default Route (Gateway of Last Resort): Configured with a prefix of 0.0.0.0/0 ( ip route 0.0.0.0/0 10.0.1.1 ). Any packet whose destination address does not match a more specific route in the routing table is forwarded to this default gateway.
Floating Static Routes for Automated Failover
A floating static route is an administratively configured static route whose Administrative Distance is deliberately set higher than that of the primary dynamic routing protocol.
Under normal conditions, the primary dynamic protocol (e.g., OSPF with AD 110) installs its route into the active routing table.
Because the floating static route has a higher AD (e.g., AD 120 or 200), it remains dormant in configuration and is not installed in the active RIB.
If the primary link fails and the OSPF neighbor relationship drops, the OSPF route is removed from the routing table.
The switch immediately installs the floating static route into the active FIB, restoring connectivity across a backup circuit without manual administrator intervention. ! Configure Primary OSPF on Interface
- interface 1/1/48
- routing
- ip address 10.0.1.1/30
- ip ospf 1 area 0
- ! Configure Floating Static Route with AD 120 (higher than OSPF 110)
- ip route 0.0.0.0/0 192.168.100.1 distance 120
- Virtual Routing and Forwarding (VRF) Architecture
In traditional networking, a switch maintains a single global routing table. If an enterprise needs to isolate Guest Wi-Fi traffic, IoT building automation, and corporate finance systems, traditional solutions relied on complex Access Control Lists (ACLs) applied across shared VLANs. However, shared routing tables still allow attackers to probe switch control plane interfaces and route tables.
Virtual Routing and Forwarding (VRF) provides true Layer 3 multi-tenancy. VRF virtualizes the physical switch into multiple independent logical routers:
Independent Route Tables (RIB/FIB): Each VRF maintains its own isolated routing table. Routes existing in VRF_GUEST are completely invisible to VRF_CORP .
Independent ARP Tables: MAC-to-IP bindings are segregated per VRF.
Overlapping IP Address Spaces: Two different VRFs can use the exact same IP subnets (e.g., both using 192.168.1.0/24 ) without IP collision, because their forwarding tables are physically separated in hardware ASICs. +-----------------------------------------------------------------------------------+
- | AOS-CX VRF SEGREGATION MODEL |
- | |
- | +--------------------+ +--------------------+ +--------------------+ |
- | | default VRF | | mgmt VRF | | TENANT_A VRF | |
- | | Corporate Data | | Out-of-Band Port | | Isolated Guest/IoT | |
- | | Routed SVIs & LAGs | | Dedicated mgmt port| | SVI Vlan 100 | |
- | +--------------------+ +--------------------+ +--------------------+ |
- | | | | |
- | v v v |
- | [ Data Plane ASICs ] [ Control Plane CPU ] [ Data Plane ASICs ] |
- +-----------------------------------------------------------------------------------+
- Built-in VRFs in Aruba AOS-CX
AOS-CX switches incorporate two pre-defined, non-deletable VRFs out of the box:
default VRF: The primary operational VRF for all front-panel data ports, SVIs, and user traffic. Unless assigned elsewhere, all Layer 3 interfaces belong to the default VRF.
mgmt VRF: Dedicated strictly to the physical out-of-band management interface ( interface mgmt ). Isolating management traffic inside the mgmt VRF prevents denial-of-service (DoS) attacks on the data plane from impacting switch management access.
Working with the Management VRF
Because the mgmt VRF is completely isolated from the data plane, standard commands executed in the CLI operate in the default VRF by default. To interact with the management network, administrators must append the vrf mgmt parameter: ! Configure out-of-band management IP address
- switch(config)# interface mgmt
- switch(config-if-mgmt)# no shutdown
- switch(config-if-mgmt)# ip static 192.168.1.50/24
- switch(config-if-mgmt)# exit
- ! Configure the management default gateway (interface mgmt context)
- switch(config)# interface mgmt
- switch(config-if-mgmt)# default-gateway 192.168.1.1
- switch(config-if-mgmt)# exit
- ! Test reachability via management network
- switch# ping 192.168.1.1 vrf mgmt
- switch# traceroute 8.8.8.8 vrf mgmt
- Creating and Binding Custom User VRFs
Administrators can create custom VRFs to segment specific user communities or business units: ! Step 1: Create custom VRF
- switch(config)# vrf GUEST_USERS
- switch(config-vrf)# exit
- ! Step 2: Attach SVI to the VRF
- switch(config)# interface vlan 100
- switch(config-if-vlan)# description Guest-Gateway
- switch(config-if-vlan)# vrf attach GUEST_USERS
- switch(config-if-vlan)# ip address 10.100.1.1/24
- switch(config-if-vlan)# exit
- ! Step 3: Configure isolated static default route inside GUEST_USERS VRF
- switch(config)# ip route 0.0.0.0/0 10.100.1.254 vrf GUEST_USERS
Configuration Warning: Changing an interface's VRF membership removes its Layer 3 configuration (for example, no vrf attach warns that all Layer 3 configuration associated with the VRF will be deleted). Attach the VRF before configuring IP addresses on the interface.
WAN Edge Routing and Campus Fabrics Overview
While static routing and OSPF dominate internal campus aggregation and access layers, modern enterprise campus networks interface with broader wide-area and data center architectures:
Border Gateway Protocol (BGP): At the campus WAN edge, enterprise border routers peer with Internet Service Providers (ISPs) using External BGP (eBGP, AD 20). Within large multi-site campuses, Internal BGP (iBGP, AD 200) propagates external prefixes across redundant core switches.
EVPN-VXLAN Campus Fabrics: In advanced campus architectures, Aruba Central and AOS-CX switches implement Ethernet VPN (EVPN) with VXLAN encapsulation (RFC 7348). In this architecture, an underlying physical IP network (the underlay) runs OSPF and ECMP for rapid, resilient packet transport. Over this underlay, switches establish a virtualized overlay network using Multiprotocol BGP (MP-BGP EVPN) as the control plane. Customer VRFs map directly to Layer 3 Virtual Network Identifiers (VNIs), enabling campus-wide macro-segmentation and seamless Layer 2 extension across routed boundaries without Spanning Tree.
- AOS-CX CLI Verification Commands
- The following commands verify ECMP forwarding, static routes, and VRF segregation: switch# show ip route
- Displaying ipv4 routes selected for forwarding
- 0.0.0.0/0, vrf default
- via 10.0.1.2, [110/20], ospf
- via 10.0.2.2, [110/20], ospf
- switch# show ip route vrf GUEST_USERS
- Displaying ipv4 routes selected for forwarding
- 0.0.0.0/0, vrf GUEST_USERS
- via 10.100.1.254, [1/0], static
- 10.100.1.0/24, vrf GUEST_USERS
- via vlan100, [0/0], connected
- Key Verification Table
Command Output and Operational Purpose
show vrf Lists all configured VRFs (default, mgmt, user VRFs) and their operational states.
show ip route Displays the routing table for the default VRF, showing ECMP equal-cost next hops.
show ip route vrf <name> Displays the isolated routing table for a specified VRF.
show ip route 0.0.0.0/0 Details the next-hop entries, metrics, and protocols for the default route.
Common Exam Traps
VRF Order of Operations: Changing an interface's VRF membership deletes its Layer 3 configuration, so attach the VRF first and then configure the IP address.
Management Default Gateway: ip route 0.0.0.0/0 192.168.1.1 installs a route in the default VRF and does nothing for the management port. Give the management interface its gateway with default-gateway 192.168.1.1 under interface mgmt , and test it with ping 192.168.1.1 vrf mgmt .
Floating Static Route Distance: To serve as a backup to OSPF (AD 110), the static route's administrative distance must be set greater than 110 (such as 120 or 200). Setting the static distance to 10 or leaving it at the default of 1 will override OSPF completely rather than acting as a backup.