# Maestro VSX operations cause Configuration PNOTE, member DOWN, and topology push failures

## Product
Maestro HyperScale Firewall, VSX (Traditional)

## Version
R81.20, R82, R82.10

## OS
Gaia

## Last Modified
2026-07-23

## Symptoms
- In a Maestro VSX environment, VSX operations fail. These operations include Virtual System creation, Virtual System deletion, and Virtual System topology push.
- The cluster reports one or more of these Critical Devices: Configuration, VSX, ROUTED, or USER_DEFINED.
- Topology and policy installation to Virtual Systems fails on the affected Security Group Members.
- One Security Group Member stays in the DOWN state. At the same time, the peer member stays in the ACTIVE or ACTIVE(!) state.
- When you run the `vsx stat -v` command on different Security Group Members, a Virtual System that you recently added or deleted shows as `unknown` or does not show at all.

## Cause
When you add or remove a Virtual System, a race condition can occur between the freeze operation and the Critical Device operation. The freeze operation can complete before the Critical Device operation completes.

This timing condition causes an inconsistent VSX configuration state between the Security Group Members.

## Solution
We're here for you

Please log in / sign in to view solution

#### NOTE
This solution has been verified for the specific scenario, described by the combination of Product, Version and Symptoms. It may not work in other scenarios.

## Article Properties
Access Level: Advanced  
Status: Approved by TAC  
Date Created: 2026-07-13  
Last Modified: 2026-07-23