Posted by ddesmidt VCS (Virtual Chassis System) provides the following benefits: . Centralized management . Automatic AX config sync VCS does not provide AX High-Availability. This is achieved by the “old-HA” (called HA) or the “new HA” (called VRRP from 2.6). So if you have 2 AXs in active/standby mode: . 2 AX in high-availability (via “old-HA” or “VRRP”) . 1 unique HA group (“old-HA”) or VRRP vrid (“new-HA”) for all the VIPs with Floating IP1 . AX1 is active for HA group1, so: - active for VIP1 using servers S1A+S1B without SNAT - active for VIP2 using servers S2A+S2B without SNAT . AX2 is standby for HA group1, so: - standby for VIP1 using servers S1A+S1B without SNAT - standby for VIP2 using servers S2A+S2B without SNAT Both VIP1+VIP2 traffic is processed by AX1. And the servers S1A+S1B+S2A+S2B default gateway has to be AX floating IP1 (active on AX1). Now if you have 2 AXs in active/standby mode: . 2 AX in high-availability (via “old-HA” or “VRRP”) . 1 HA group (“old-HA”) or VRRP vrid (“new-HA”) for some VIPs with Floating IP1 . 1 other HA group (“old-HA”) or HA vrid (“VRRP”) for some VIPs with Floating IP2 . AX1 is active for HA group1 and standby for group2, so: - active for VIP1 using servers S1A+S1B without SNAT - standby for VIP2 using servers S2A+S2B without SNAT . AX2 is standby for HA group1 and active for group2, so: - standby for VIP1 using servers S1A+S1B without SNAT - active for VIP2 using servers S2A+S2B without SNAT VIP1 traffic is processed by AX1. The servers S1A+S1B default gateway has to be AX floating IP1 (active on AX1). VIP2 traffic is processed by AX2. The servers S2A+S2B default gateway has to be AX floating IP2 (active on AX2). Note: You can’t have 1 VIP active on 2 different AXs. AX Active/Active deployment requires at least 2 VIPs. Dimitri