Stratus Redundant Linux Release 3.0.0.0 Release Notes

These Release Notes (updated at 12:12 AM on 4/23/2025) are for Stratus Redundant Linux Release 3.0.0.0, which runs on ztC Edge systems. See the following sections:

New Features and Enhancements

New in Stratus Redundant Linux Release 3.0.0.0

The following features are new in Stratus Redundant Linux Release 3.0.0.0:

VM Backup and Recovery (Technology Preview)

The new VM backup and recovery feature is a Technology Preview only and is under development for potential availability in a future release. Access to the feature requires a separate license and is disabled by default. The feature is not supported nor intended for use in production environments. Contact your authorized service provider for more information.

For information about how the proposed VM backup and recovery feature might work, see Backing Up a Running Virtual Machine and Recovering a Virtual Machine from a Backup.

Features No Longer Supported

The following features and products are not supported with Stratus Redundant Linux Release 3.0.0.0 or higher:

Bug Fixes

Bugs Fixed in Stratus Redundant Linux Release 3.0.0.0

ZTC-20585: Guest shutdown can result in guest volume being marked inconsistent.

ZTC-19756: Unable to restore an OVF/VHDX VM with the Import/Restore button.

ZTC-18685: Reserved name for VM is not checked at VM creation and generates subsequent error conditions.

ZTC-17370: The drbd5 service port 8905 is not defined in the iptables utility.

ZTC-17177: Missing Ethernet PCI slot prevents UI from rendering the portal, UI remains stuck on loading.

ZTC-17175: Setting MTU 9000 on the P1 interface will cause Link DOWN and then UP again, but all network traffic stops through the P1 interface.

ZTC-17164: Opening a VNC console in UI, seeing port:0 instead of port:8000.

ZTC-17161: Exported VMs may show incorrect network ordering and MAC address settings in the Import/Restore Virtual Machine Wizard.

ZTC-16990: SMART information for NVMe disks and gdisk data are missing from buggrab results.

ZTC-16733: Upgrade is hung if there is a node already in maintenance mode. Update Qualify script to check for this.

ZTC-17133: libvirt log files can grow indefinitely.

ZTC-17128: Increase SSH Root Public Key length from 2048 to 4096 for increased security.

ZTC-20626: Add Dubai/UAE Timezone Configuration in UI.

ZTC-21795: Customer Requests to be able to modify the UI inactivity timeout.

ZTC-21225: Include Activated_License_Key_Download_assetID.htm file when generating a diagnostic file.

ZTC-19150: Alert reports network status for priv0 incorrectly for short duration of time.

ZTC-17938: Eliminate appearance of upgrade failures and unnecessary calls to support.

ZTC-17901: When priv0 is lost, VNC console will not work when the VM is active on secondary node.

ZTC-17136: ntpd_periodic_restart has an error for the ntpdate command, which cannot be found in PATH.

ZTC-17314: Customer is able to create more than 32 VMs, but if 33rd one is activated, it will not start.

ZTC-18314: System management architecture should permit proper cold start initialization when ibiz0 is working but priv0 is not.

ZTC-1903: Bug grabs should abort if either node is in swap. This includes all levels.

ZTC-11759: When creating a VM with the Copy option, the created VM always enters the running state.

ZTC-3011: Extend the buggrabber default timer.

ZTC-9961: Scanner is detecting that python is vulnerable because it is no longer receiving security updates.

ZTC-11817: VMs do not start if each node is issued a Work On then Shutdown, and the first node to be powered off is powered on first followed by the other node.

ZTC-3011: Exclude both process core files and Linux kernel panic vmcore from the FULL buggrab.

CVE Fixes

For a list of the CVE fixes, see Fixed CVEs.

Important Considerations

Upgrading to Release 3.0.0.0

To upgrade to Stratus Redundant Linux Release 3.0.0.0, follow the upgrade path for the release that is running on your system:

After upgrading to Stratus Redundant Linux Release 3.0.0.0, to upgrade to a later 3.x.x.x maintenance release, see Upgrading Stratus Redundant Linux Software Using an Upgrade Kit.

Determining the Version of System Software

To determine the version of Stratus Redundant Linux running on a ztC Edge system, log on to the ztC Edge Console for the system and check the system information in the masthead:

ocean.abc.com
IP: 123.109.50.34 | Asset ID: ze-12345
Version: n.n.n-nnn

Alternatively, you can click Software Updates on the Preferences page, which also displays the current version number of the Stratus Redundant Linux software on your system.

If the software release is lower than Release 3.0.0.0, download the Stratus Redundant Linux 3.0.0.0 Upgrade Kit from the Downloads page at https://www.stratus.com/services-support/downloads/?tab=ztcedge and upgrade the software on the system as described in Upgrading Stratus Redundant Linux Software Using an Upgrade Kit.

SNMP Disabled by Default on ztC Edge Systems

SNMP is disabled by default on ztC Edge systems. Starting with Stratus Redundant Linux Release 2.3.0.0 or higher, the SNMP process is also stopped in the console operating system on each node. For security reasons, if you need to enable SNMP, you should disable SNMP v1 and v2, and enable only version 3 by using the SNMP Restricted configuration. For details, see Configuring SNMP Settings and Security Hardening, as well as KB0015428.

Deploying Spare Nodes with Stratus Redundant Linux Release 3.0.0.0 or Higher

If you have a factory-fresh node installed with Stratus Redundant Linux Release 3.0.0.0 or higher, you can deploy the node as a single-node system, or as the second node or replacement node in a dual-node system if the running node is already running either Release 2.3.x.x or Release 3.x.x.x.

If you need to use a spare node that is imaged with any release prior to Release 3.0.0.0, you must exchange it for a factory-imaged Release 3.x.x.x node to support pairing with any Release 3.x.x.x primary node. Contact your authorized Stratus service representative for assistance.

To deploy, add, or replace nodes that meet these requirements, see Deploying the System, Adding a Node to a Single-Node System, and Replacing Physical Machines (Automated).

Using Intel Active Management Technology (AMT) for Lights-Out Support

ztC Edge systems incorporate Intel Active Management Technology (AMT) lights-out support for remote power management, remote console, and remote media. For important information about AMT configuration and restrictions, see KB0014200.

Deploying ztC Edge Nodes at Separate Physical Sites

When you deploy a ztC Edge system in a redundant, dual-node configuration, you must deploy both nodes at the same site and directly connect the A-links between the blue (A2) and yellow (A1) network ports of each node. If you want to set up a ztC Edge system in an automated local site recovery (ALSR) configuration, where each node is located at a separate physical site for increased redundancy, contact your authorized Stratus service representative for assistance. Because of the geographic separation, an ALSR configuration requires careful planning of component placement and networking topologies.

Tested Guest Operating Systems

For a list of the guest operating systems tested with the current release, see Tested Guest Operating Systems. For information on guest operating systems tested or supported in previous releases, go to http://ztcedgedoc.stratus.com, select the appropriate release, and then search for the guest operating system.

Known Issues

Upgrading from Release 2.x to 3.x Does Not Preserve System Logs from Original 2.x System

When you upgrade from Stratus Redundant Linux Release 2.x to 3.x, the upgrade process does not preserve the system logs from the original Release 2.x (CentOS) system. To preserve the log data before upgrading, create a diagnostic file as described in Creating a Diagnostic File and download it to a management PC.

Windows Server Guest Stuck in Booting State After Upgrading from Release 2.x to 3.x

After upgrading from Stratus Redundant Linux Release 2.x to 3.x, in rare cases, a Windows Server guest might remain stuck in the booting state, waiting for its storage to be ready. As a workaround, stop and start the VM to allow it to continue booting.

Lengthy VM Volume Synchronization After Upgrading from Release 2.x to 3.x

After upgrading from Stratus Redundant Linux Release 2.x to 3.x, the volumes associated with some VMs might take longer than normal to synchronize between nodes because the system performs a full mirror copy of each volume instead of a delta mirror copy. The amount of time required for synchronization varies by system hardware, overall system load, and guest disk activity.

Monitor Tab of Physical Machines Page Disabled After Upgrading from Release 2.x to 3.x

After upgrading from Stratus Redundant Linux Release 2.x to 3.x, the Monitor tab of the Physical Machines page is disabled with a message that the license for this feature is not activated, even though it should not require a license in Release 3.x or higher. To obtain a license at no cost, contact your authorized Stratus service representative.

Guest Monitoring Alerts Persist After Upgrading from Release 2.x to 3.x

After upgrading from Stratus Redundant Linux Release 2.x to 3.x on a system where Windows guest OS monitoring was previously enabled, the Alert History page might still contain guest alerts from Release 2.x even though guest monitoring is no longer supported in Release 3.x. You must manually remove these alerts from the Alert History page to allow the system to reach a healthy state and clear alerts from the Dashboard page and the masthead of the ztC Edge Console.

ztC Edge 100i/110i System Power Button Cannot Shut Down Primary Node

On ztC Edge 100i/110i systems, if you press the power button on the primary node, it does not shut down the node as expected. If you need to shut down the primary node for maintenance, use the ztC Edge Console as described in Shutting Down a Physical Machine.

ztC Edge 100i/110i System SYS LED Cannot Flash to Identify Node

For ztC Edge 100i/110i systems, if you click Identify on the Physical Machines page of the ztC Edge Console, the SYS LED does not flash to identify the node.

Windows Server 2022 Guest Uses Windows Server 2016 VirtIO Drivers

When you install VirtIO drivers in a Windows Server 2022 guest operating system as described in Updating the VirtIO Drivers (Windows-based VMs), the system installs the VirtIO drivers associated with Windows Server 2016. The Windows Server 2022 guest performs normally with these drivers.

Remote Desktop Session to Windows Server 2022 Guest Hangs

In rare cases, a Remote Desktop session to a Windows Server 2022 guest hangs. As a workaround, you can open a connection to the console of the guest by selecting the guest on the Virtual Machines page and clicking Console.

No Statistics Available for Node on System Page of ztC Edge Console

On the System page of the ztC Edge Console, under Node0 or Node1, the system displays no statistics for a node even though the node is currently running.

To display statistics for the node

  1. In the ztC Edge Console, open Preferences and then IP Configuration.

  2. Record the IP address for the node that lacks statistics.

  3. Open an SSH connection to the node as described in Accessing the Host Operating System.

  4. Run the following command to restart the collectd service that provides the statistics.

    # systemctl restart collectd

No Statistics Available for Node1 on Monitor Tab After Adding Node to Single-Node System

After adding a node to a single-node ztC Edge system, the Monitor tab on the Physical Machines page of the ztC Edge Console displays no statistics for the node even though the node is currently running.

As a workaround, to display statistics for the node, disable and re-enable monitoring on the Monitor tab. Clear the Enable checkbox for the parameter you are monitoring and click Save, then activate the checkbox for the parameter and click Save again.

ztC Edge Console Displays HTTP 500 Error After Putting Primary Node Into Maintenance

If you put the primary node of a ztC Edge system into maintenance mode and both nodes in the system lose power asynchronously (one node loses power and restarts, and then the next node loses power and restarts), the ztC Edge Console might display an HTTP Status 500: Internal Server Error page because the web server files on the system have been corrupted.

To correct the issue and restore access to the ztC Edge Console

  1. Open an SSH connection to the primary node as described in Accessing the Host Operating System.

  2. Delete the Apache Tomcat org folder by executing the following command:

    # rm -rf /opt/apache-tomcat-9.0.55/work/Catalina/localhost/ROOT/org/

  3. Refresh the web browser to display the ztC Edge Console.

VM Names Display Incorrectly in OPC Utilities

If you use an Open Platform Communications (OPC) client to monitor a ztC Edge system configured for OPC monitoring (as described in Configuring OPC Settings), the OPC client cannot properly display the VM names from the ztC Edge system.

Cannot Restore Console Inactivity Logout Preferences

On a system recently upgraded from Stratus Redundant Linux Release 2.x to Release 3.0.0.0 or higher, when restoring system preferences as described in Saving and Restoring System Preferences, the ztC Edge Console displays a Failed status for the Console Inactivity Logout preference. This is expected behavior because the Console Inactivity Logout is a new feature in Release 3.0.0.0 or higher, and there is no preference data to restore from the previous 2.x release. For more information about this new feature, see Configuring the Console Inactivity Logout.

Windows Server 2016 Guest Stuck in Booting State After Installation in Localized German Language

After installing Windows Server 2016 with the localized German version of the Windows Installer (ISO) in a VM with a single virtual network adapter, the VM is stuck in the booting state because its network is not working. To resolve this issue, see KB0017023.

Removable Media and Migrating a PM or VM Using the P2V Client

Before migrating a PM or VM using a bootable P2V client (virt-p2v) ISO file, check if any removable media (for example, floppy disks, DVD drives, or external USB disks) are attached to the source image. If removable media are attached to the source image when you attempt to migrate a PM or VM, the error message Conversion failed appears. To prevent this issue, deselect the media in the virt-p2v window before starting the migration. To do so, access the virt-p2v window with the sections Target properties and Fixed hard disks, and then beneath Fixed hard disks, uncheck the box in the Convert column next to the removable media. See Migrating a Physical Machine or Virtual Machine to a System, particularly the section To migrate a PM or VM to the ztC Edge system, for more information on using virt-p2v.

"The VM name has failed to start" Alert While Running the P2V Client Is Normal

While using the P2V client to migrate a VM from an everRun or ztC Edge system, it is normal if the source system displays the alert "The VM name has failed to start" during the migration process, because although the source VM is powered on and running the P2V client, the guest operating system does not start.

Importing VM from OVA File May Succeed Despite Failure Message

When you import a VM from an OVA file, the import might appear to fail with the error message Failed to import OVA; however, if you are able to manually start the VM, the import was successful. If the VM does not start, delete the VM and its volumes and retry the import.

Unknown Error in ztC Edge Console When Importing an Unprotected VM

When you an import an unprotected VM (see Unprotected Operation), the ztC Edge Console might display an alert that "An unknown error has occurred." You can safely ignore this message and click OK to continue the import.

Maximum Path Length When Importing a VM

When you import a VM using the Import/Restore Virtual Machine wizard, the maximum length of the path to the VM, including the VM name, is 4096 characters for the import options Import from remote/network Windows Share(CIFS/SMB) and Import from remote/network NFS.

Maximum Resolution of a UEFI VM Console Session

On the Virtual Machines page of the ztC Edge Console, you can open a VM console session to display the console of the guest operating system running in the VM. When you open a console session to access a guest VM with a UEFI boot type, the console session may have a maximum resolution of 800x600. If needed, you can configure a higher resolution in the BIOS setup utility, as described in KB0015299.

Creating VCD fails When Console Browser is Microsoft Edge

When you are using Microsoft Edge as the browser for the ztC Edge Console you cannot create a VCD: the process will fail. Instead, use another compatible browser (see Compatible Internet Browsers).

In a Single-Node System, VM Creation Wizard Display of Added vCPUs Is Incorrect

When you create a VM on a system configured for one node, the VM Creation Wizard displays that it is adding two vCPUs to the number vCPUs you specify. However, once the VM is created, the user-specified number of vCPUs is attached to the VM. The additional two (incorrectly displayed) vCPUs are not added.

Mapping of Japanese Keyboards 106 and 109 For Console in Firefox May Be Incorrect

The mapping of the Japanese keyboards 106 and 109 may be incorrect when using Firefox to access the ztC Edge Console. Use Chrome or remote connection software (VNC or RDP), instead.

Cannot Enable SNMP Requests Without Traps

If you create an SNMP request in the ztC Edge Console, you must also create a trap; otherwise, the ztC Edge Console displays the error "Problem encountered updating SNMP. Make sure your settings are correct. Error: Configure SNMP failed." As a workaround, when creating a new SNMP request, click Enable SNMP Requests and Enable SNMP traps, do not define a Version 3 user, keep the default of Restricted requests, and specify at least one trap recipient. Adding a Version 3 user or clicking Unrestricted during the initial configuration might cause the configuration to fail. After the initial configuration is complete, you can then modify it to specify any settings that you require.

System Fails to Generate SNMPv3 Traps When Authentication Is Enabled

If you configure an SNMPv3 user and send SNMP traps with authentication enabled, the system fails to generate the SNMP traps.

VMs Reported as Broken Instead of Degraded When A-Link Is Offline

If an A-link cable or network is disconnected on one node, the state of a VM on that node may be reported as broken () in the ztC Edge Console, even though the VM still has another active A-link connection. The availability of the VM is unaffected.

Ejected VCD Still Displayed in a Linux-based VM Console

If you use the ztC Edge Console to eject a VCD from a VM running a Linux-based guest operating system, the VCD may still be displayed in the guest operating system. If needed, you can eject the VCD in the guest operating system to stop displaying the VCD.

Some Browsers Unable to Connect a VNC When Using https

If you are connected to the ztC Edge Console using an https URL in some browsers, including the Mozilla® Firefox® browser, and you click Console after selecting a running VM from the Virtual Machines page, the message VNC: Unable to connect, retrying in n seconds may appear. To enable the VNC connection, click the https link to the VNC console page in the upper right-hand corner of the masthead. In the Firefox browser, when the Your connection is not secure window appears:

  1. Click Advanced. A message about an invalid security certificate appears.
  2. Click Add Exception. The Add Security Exception dialog box appears with the console's location in Location.

  3. Click Confirm Security Exception.

The VNC console appears.

Some Browsers Unable to Connect a VNC When Using http

If you are connected to the ztC Edge Console using an http URL in some browsers, including the Google® Chrome™ browser, and you click Console after selecting a running VM from the Virtual Machines page, the message VNC: Unable to connect, retrying in n seconds may appear. If you cannot establish a connection, try using either the Mozilla Firefox or Microsoft Edge browser.

Reboot Required When Changing Node IP Address or Netmask Network Settings

When you change the IP address or netmask settings of a node as described in Configuring IP Settings, both the old and new settings are in effect until you reboot the node. Having both settings active may cause routing or connection issues.

Accessing Stratus Knowledge Base Articles

The Stratus Customer Service Portal provides a searchable Knowledge Base with technical articles about all Stratus products, including ztC Edge. In some cases, the online Help directly references these Knowledge Base articles (for example, KBnnnnnnn). You can access the Stratus Customer Service Portal and its Knowledge Base by using your existing portal credentials, or by creating a new user account, as follows.

To access the Knowledge Base

  1. Log on to the Stratus Customer Service Portal at https://service.stratus.com.

    If needed, create a new account as follows:

    1. Click Register.

    2. Enter your contact information including your company email address and registration code, and then click Submit.

      Your company email address must include a domain name (for example, stratus.com) for a company that is a registered customer of Stratus. The portal sends an email to administrators of the company's account to approve the request.

    3. Upon approval, click the link in the email that you receive from Stratus.
    4. Enter a new password and finish configuring your account.

    If you need assistance creating an account, contact your authorized Stratus service representative.

  2. In the portal, do one of the following:

    • In the Search box, enter keywords or the KB article number (KBnnnnnnn) associated with the information you need, and then click the search button.
    • Click Knowledge, click the name of a product, and then browse available articles.

Getting Help

If you have a technical question about ztC Edge systems, you can find the latest technical information and online documentation at the Downloads page at https://www.stratus.com/services-support/downloads/?tab=ztcedge. You can also search the Knowledge Base in the Stratus Customer Service Portal at https://service.stratus.com.

If you cannot resolve your questions with these online resources, and the system is covered by a service agreement, contact your authorized Stratus service representative. For information, see the ztC Edge Support page at https://www.stratus.com/services-support/customer-support/?tab=ztcedge.