WHAT TO EXPECT
In this article, users will learn to use High Availability, how to view, add, edit, and remove HA Configurations.
Navigating to the High Availability tab
The High Availability tab is located in the Settings page on wXcked Eye. To learn how to navigate there, users should review the wXcked Eye System Management article.
To learn about High Availability, users can read the High Availability section in the cloudSwXtch Licenseable features.
The High Availability tab is organized into 3 functions:
In this article, we will discuss each function and how it offers the user additional control over their cloudSwXtch network.
.png?sv=2022-11-02&spr=https&st=2025-11-03T06%3A28%3A07Z&se=2025-11-03T06%3A42%3A07Z&sr=c&sp=r&sig=JzJ%2FU9ffc1lThTbE2SPT%2Fbvgx%2BHu1H72V0dTvmaGpk8%3D)
Create HA
Create a cluster for each path for the HA array. To create a cluster, refer to Add Cluster.
Once the clusters are in place, click the "Add Config" button in the Clusters tab. A pop-up will open.

Name the HA configuration. In this example, the HA is named HA_1.
Select the appropriate cluster for each path, and the swXtch Addresses will populate.
Name each path.
Assign a color for each path. In this example, the user selected Red for RedPath and Blue for BluePath.
Click "Add Config." A new High Availability topology has been created.
.png?sv=2022-11-02&spr=https&st=2025-11-03T06%3A28%3A07Z&se=2025-11-03T06%3A42%3A07Z&sr=c&sp=r&sig=JzJ%2FU9ffc1lThTbE2SPT%2Fbvgx%2BHu1H72V0dTvmaGpk8%3D)
With High Availability now configured, users can switch between different cloudSwXtches in their HA.
Renaming High Availability and Path Names
To rename the high availability configuration or paths, users will need to destroy the HA and reconfigure it.
Destroy HA
To destroy an HA configuration, the user will need to go to the HA page of any associated cloudSwXtches.
Click "Destroy HA config." A new prompt will appear, asking to confirm the action.

Select "Confirm."

The HA array is now destroyed.
Removing a cloudSwXtch from an HA configuration
To remove a cloudSwXtch from a user's HA configuration, users will need to delete and recreate their HA cluster without that cloudSwXtch.
Configuring HA for Multiple Multicast (MMc) and Source Specific Multicast (SSM)
wXcked Eye enables users to group multiple multicast IP addresses with the same traffic under a single multicast group IP. The xNIC, or application at the end point, is then tasked with listening for the multicast group IP and deduplicating the data from the two paths. This is what we call a multiple multicast, or MMc, high availability configuration.
In addition, users can also configure their path streams for source specific multicast (SSM). This is a method for delivering multicast packets in which the only packets that are delivered to the receiver are those originating from a specific source IP address.
Go to the High Availability tab on the wXcked Eye System Management page.
In the desired HA configuration, click HA Streams.

Enter the Stream (Parent IP address and Port), followed by the Path Streams.
In the example below, the user assigns the parent and port as 224.2.2.2:8400 with the two path streams as 224.2.2.3:8400 and 224.2.2.4:8400.

b. Alternatively, users can also select an existing parent from the dropdown menu. Considered a Group in the wXcked Eye Settings page, choosing a parent will automatically populate the path streams. For this to work, the group name must be the Parent IP:Port (224.3.2.2:8400).

c. Adding a new Parent IP address and its path streams will create a new Group.
If Source Specific Multicast is required, users may follow the next steps. If not, fields can be left blank and continue to Step 5.
For each stream path, select Include in the SSM Filters dropdown menu.
Enter the Override Source IP address into one of the Source IP fields.
Enter the second Source IP for the second path.

If users would like to exclude xNICs from the HA Streams configuration, enter the IP addresses in the Exclude xNICs field. If not, continue on to Step 6.

Select Update Config to apply changes.
Exporting HA Streams Config
Users can export their HA streams configuration as a JSON file from the wXcked Eye UI. The stored configuration can later be imported to reconstruct the setup.
To accomplish this:
Navigate to the High Availability Tab in the wXcked Eye System Management page.
Select the HA Configuration to export.
Select Export HA Streams Config.
Note: This will only work if there’s an existing HA Streams config populated as shown below.
An ha_streams_config.json file should automatically download.

Clearing HA Streams Config
Users can clear or delete their HA streams configuration as a JSON file from the wXcked Eye UI.
To accomplish this:
Navigate to the High Availability Tab in the wXcked Eye System Management page.
Select the HA Configuration to export.
Select Clear HA Streams Config.

The following options will be presented.
Clicking Save without any options, then the configuration will be cleared.

b. Selecting Import config, the following dialog will appear. Select OK to import the new configuration and remove the old configuration.

Importing HA Streams Config
Users can import their HA Streams configuration JSON file into wXcked Eye to automatically populate their high availability settings page.
To accomplish this:
Navigate to the High Availability Tab in the wXcked Eye System Management page.
Select the HA Configuration to import.
Select Import in the HA Streams Config. The following screen will appear.

Select OK.
The File Explorer will open.
Select and open the ha_streams_config.json file to use. Note that the file name may be different if the user reassigned it during export.
The HA Streams Config section should populate with the contents of the JSON file.
.png?sv=2022-11-02&spr=https&st=2025-11-03T06%3A28%3A07Z&se=2025-11-03T06%3A42%3A07Z&sr=c&sp=r&sig=JzJ%2FU9ffc1lThTbE2SPT%2Fbvgx%2BHu1H72V0dTvmaGpk8%3D)
Click Save to apply changes.
NOTE
Bear in mind that the imported configuration should match the current setup. That means that, in order to be useful, the export operation and the later import operation shuold be placed on the same IPs of the components to be meaningful.