When setting up CV-CUE for the first time, it must be enabled on all the nodes of a cluster. Once CV-CUE is enabled, then at boot time, the CV-CUE service on the primary node automatically becomes the Active instance, and the one on the secondary node becomes the Standby instance. The HA failover and recovery mechanisms work exactly as expected. If the primary node goes down, the CV-CUE instance on the secondary node becomes active. When the primary node rejoins the cluster, a split-brain recovery kicks in and re-elects the new active and standby containers.

Except for OS and kernel processes, the CV-CUE service on CV runs all the application processes required to manage Arista CV-CUE and wireless intrusion prevention system (WIPS). Some key features of the CV-CUE service are as follows:

• CV-CUE uses ports 3851 and 161 (both UDP) for all CV communication with external entities. These ports need to be opened in your network.
• CV-CUE consists of two key components:
  • wifimanager, the server that manages the CV-CUE network.
  • aware, the cognitive CV-CUE UI of the server.

The table below shows the number of access points (APs) that a CV-CUE container supports for the given CPU, RAM, and hard disk settings. The CPU and RAM values displayed in this table are the default settings for a DCA-200 device; the actual capacity may vary based on deployment, environment, and load.