These Release Notes (updated at 10:23 PM on 4/29/2021) are for Stratus Redundant Linux Release 2.0.1.0, which runs on ztC Edge systems. See the following sections:
Major new features and enhancements are listed below under the release in which they became available.
The following features are new in Stratus Redundant Linux Release 2.0.1.0:
The following features are new in Stratus Redundant Linux Release 2.0.0.0:
OEM Support—Enhanced customization capabilities: you can configure a banner for the ztC Console login page.
Availability—Support for Fault Tolerant (FT) operation on ztC Edge 110i systems.
Network—MTU default of 9000 for the A1 (alink1) and A2 (priv0) ports on ztC Edge 110i systems.
Network names are consistent in the Networks page and the Networks tab of the Physical Machines page.
Remaining life of SSD drives is displayed on the Storage tab of the Physical Machines page.
Supported browsers updated.
The default communication protocol is HTTPS.
When logging in to the ztC Console for the first time, most browsers display one or more security messages, but you can proceed to the console. You can add a security exception later, to allow the site to load without the message(s).
EV-50067: The host microcode update does not always properly set spec_ctrl flag that indicates Spectre mitigation is supported.
EV-50012: The host microcode may not be updated on an upgrade to the Stratus Redundant Linux 2.0.0.0 release.
EV-49917: Correct the secondary node NTP settings.
EV-49840: Physical to virtual (P2V) conversion fails due to unexpected partition table characteristics.
EV-49817: Virtual Machine (VM) fails to boot after an -in-guest shutdown when a USB device is attached to system.
EV-49807: The ztC Console displays lost connectivity with network warning for management port state if DNS server communication is lost.
EV-49802: Some e-alerts, call homes, and snmp traps no longer work after upgrading a system to Release 2.0.0.0.
EV-49788: VM import fails when name of disk image file does not contain the string disk.
EV-49738: The Stratus guest/application monitoring agent does not function on the German version of Windows.
EV-49680: The IPtables configuration is not restored after a node reboot or replacement.
EV-49603: Kit upgrade can hang if any unused network has a fault. The Qualify script should be enhanced to check for this condition.
EV-49537: Prevent potential loss of guest due to internal queue lockup.
EV-49528: Guest VMs with very large disks may cause the console to become non-responsive during certain operations.
EV-49527: Putting a node into Maintenance is blocked until all mirror copies for a VM are completed.
EV-48962: SMD logs unnecessary messages.
EV-48473: VM(s) will not start because axstore.db has a size of 0.
EV-48341: Windows VM crashes when last available network adapter is disabled.
EV-48304: Memory leaks.
EV-48191: System Manager does not start the AX-QEMU after it was shutdown due to CoreFT Fault Handler.
EV-47890: Modifying the MTU with the GUI on a system licensed for one node results in System Manager problems.
EV-47860: Guest AXs cannot communicate with each other if A-Links references were crossed.
EV-47802: System management state corrupted after power loss.
EV-47754: System management restart causes a false node reboot alert message.
EV-47673: Private branded customization lost during node replace.
EV-47611: Interrupting and restarting mirror copy can fail.
EV-47091: Importing FT VM onto HA system cannot start due to unlicensed feature.
For a list of the CVE fixes, see Fixed CVEs.
To upgrade to the current release of Stratus Redundant Linux, follow the instructions in Upgrading Stratus Redundant Linux Software Using an Upgrade Kit.
To determine the version of Stratus Redundant Linux running on a ztC Edge system, log on to the ztC Console for the system and check the system information in the masthead:
If the software release is lower than Release 2.0.1.0, download the Stratus Redundant Linux 2.0.1.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.
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 KB-8219.
Redeploying a ztC Edge system allows you to clear the network settings of the system to prepare it for deployment on a different network. If you need to move a system to a new network, redeploy and shut down the system before moving it, as described in Redeploying a ztC Edge System.
When you redeploy a system, note the following issues and workarounds:
System reboot needed when setting new static system IP address.
A system loses access to the secondary node if you redeploy and shut down the system, start it up in a new location, and then configure a new static system IP address. To regain access to the secondary node, reboot the system by opening the System page and clicking Reboot. Rebooting the system refreshes the gateway settings on the secondary node and allows it to connect to the system.
When you deploy a ztC Edge system, 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 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.
USB 3.1 devices are not supported. Use USB 3.0 devices, instead.
You can attach only supported USB devices to a guest operating system. ztC systems support USB devices and provide USB ports, as follows:
Some USB devices claim to be 3.0 compatible, but are not. If you are using such a device, switch to another USB device that is 3.0 compatible.
When you add a second node (node1) to a single-node system, and the single-node system has monitoring of CPU and/or memory enabled on the Monitoring tab of the Physical Machines page, the monitoring values do not automatically appear on the node1 Monitoring tab of the Physical Machines page.
In order to display the monitoring values for node1, you must disable the monitored parameter(s) (CPU and/or memory) and save the change. Then, enable the parameter(s) (CPU and/or memory) and save the change. After a few moments (a maximum of 3 minutes), both nodes appropriately display the monitored values.
You cannot import a VM from a VMware source if the VM firmware type is set to UEFI. The ztC Edge system supports importing VMs from a VMware source only if the VM firmware type is set to BIOS (that is, Legacy BIOS).
When importing a VMware VM, you must shutdown the VM using operating system shutdown commands in addition to powering it off from the VMware console. If you shutdown the VM using only the VMware console, the import will fail.
When you create a VM on a system licensed 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.
When you upgrade a system licensed for one node to a system licensed for two nodes, the VMs remain running, but the Dashboard displays the VM state with a warning icon (). The warning indicates that the VMs are running with only one or no A-Links because, during the upgrade, the system does not add A-Link1.
To avoid the issue, stop the VMs before the upgrade and then restart the VMs after the upgrade. If you encounter this problem, stop and restart the VMs after the upgrade.
After migrating a VM using P2V from a bare metal machine running Ubuntu 14.04, 16.04, or 18.04, the VM may have problems, such as no active network. To correct the problem, perform the appropriate procedure below after migrating the Ubuntu VM.
You do not need to reboot the VM because, after issuing these commands, the VM is on the network with its configured IP address.
The following procedure does not require you to reboot the system.
Note that the command output does not include eth0.
Enter the following command:. ifconfig -a.
Note that the command output includes eth0.
Enter the following command: sudo vi interfaces.
In the interfaces file, change em1 to eth0.
Enter the following command: sudo vi ifstate.eth0.
In the ifstate.eth0 file, insert eth0 at the top of the file.
The following procedure requires you to reboot the VM:
The mapping of the Japanese keyboards 106 and 109 may be incorrect when using IE10, IE11, or Firefox to access the ztC Console. Use Chrome or remote connection software (VNC or RDP), instead.
When monitoring on a VM is set for all three parameters (CPU, Memory, and Disk), and the VM is migrated to the other node, the Monitor tab displays No response from guest agent. It may take several minutes for the guest agent to reconnect.
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 Console, even though the VM still has another active A-link connection. The availability of the VM is unaffected.
If you use the ztC 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.
If you eject USB media from File Explorer in a Windows VM, you cannot re-mount the media without first physically disconnecting the media from the ztC Edge system.
If you use the P2V client (virt-p2v) to migrate a PM or VM from a source that is running VMware, the network driver might fail to install properly during the migration process, which leaves the VM network offline. If this happens, manually install the network driver in Device Manager. For instructions, see the Troubleshooting section of Migrating a Physical Machine or Virtual Machine to a System.
If you import a Windows-based VM with the Import/Restore Virtual Machine Wizard, the VirtIO network driver may fail to install properly the first time you start the VM, which leaves the VM network offline. If this happens, manually install the network driver in Device Manager. For instructions, see the Troubleshooting section of Importing an OVF File.
Before creating a VM, always ensure that the network you assign to the VM has an active network connection in each node of the system. You can verify the state of the networks on the Networks page of the ztC Console.
If you add a VM while one of the paired network interfaces is offline, the VM will not start. To start the VM, connect an active network cable to the offline interface, wait a few seconds, and start the VM.
If you are connected to the ztC Console using an https URL in a Microsoft Internet Explorer or 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, and continue with the appropriate procedure below (procedure in your browser may differ, depending on the version of your browser):
In Internet Explorer, the Security Alert wizard appears:
In FireFox, the Your connection is not secure window appears:
Click Confirm Security Exception.
The VNC console appears.
The Stratus Redundant Linux software on ztC Edge systems does not support the exFAT File system. If you need to mount a USB medium to import or export a VM, as described in Mounting a USB Device or Network-mounted Folder on the ztC Edge System, format the device with NTFS. (By default, most USB media are formatted with the FAT file system, which has a limited file size of 4 GB that may be too small for most VMs.)
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.
For Release 2.0.1.0, the following topics are new or have been updated since Release 2.0.0.0:
The following Help topics have been updated since translation:
Beginning in Release 2.0.0.0, Help is available in German, Japanese, Chinese, and Portuguese.
The Stratus Customer Service Portal provides a searchable Knowledge Base with technical articles about all Stratus products, including ztC Edge systems and Stratus Redundant Linux software. In some cases, the Release Notes directly reference these Knowledge Base articles (for example, KB-nnnn). You can access the Customer Service Portal and the Knowledge Base articles by using your existing service portal credentials, or by creating a new user account, as follows.
To access the Knowledge Base
Log on to the Stratus Customer Service Portal at https://support.stratus.com.
If needed, create a new account as follows:
Enter your company email address and contact info, and click Register.
Your company email address must include a domain name (for example, stratus.com) for a company that is a registered customer of Stratus.
If you need assistance creating an account, contact your authorized Stratus service representative.
In the Keyword Search box, enter keywords associated with the information you need, and then click Search.
To search for an article by its KB-nnnn number, click Advanced Search. Next to Search by ID, type the article ID number (nnnn) and click Display.
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://support.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.