Stratus Redundant Linux Release 2.1.0.0 Release Notes

Note: 有关最新的技术信息和更新(中文),请参阅 http://ztcedgedoc.stratus.com 上的 ztC Edge 版本 2.1.0.0 发行说明。.
Note: Die neuesten technischen Informationen und Updates (auf Deutsch) finden Sie in den ztC Edge Version 2.1.0.0 Versionshinweisen unter http://ztcedgedoc.stratus.com.
Note: 最新の技術情報およびアップデートは、ztC Edge リリース 2.1.0.0 リリース ノート (http://ztcedgedoc.stratus.com) を参照してください。
Note: Para obter as informações técnicas e atualizações mais recentes (em Português), consulte as Notas da versão do ztC Edge 2.1.0.0 em http://ztcedgedoc.stratus.com.

These Release Notes (updated at 10:25 PM on 4/29/2021) are for Stratus Redundant Linux Release 2.1.0.0, which runs on ztC Edge systems. See the following sections:

New Features and Enhancements

New in Stratus Redundant Linux Release 2.1.0.0

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

New in Stratus Redundant Linux Release 2.0.1.0

For information, see New in Stratus Redundant Linux Release 2.0.1.0.

New in Stratus Redundant Linux Release 2.0.0.0

For information, see New in Stratus Redundant Linux Release 2.0.0.0.

Bug Fixes

Bugs Fixed in Stratus Redundant Linux Release 2.1.0.0

EV-50970: A USB may still be displayed in the user interface after it is pulled. Also, attempts to attach a USB to a guest may result in the incorrect USB being attached.

EV-50954: After power is restored to a single-node system after a power outage, a VM with an attached USB device does not boot.

EV-50772: An HA VM running Microsoft Windows Server 2016 crashes during a kit upgrade from Release 1.3.0 (CentOS 7.5) to Release 2.1.0 (CentOS 7.7) when migrating from node0 to node1.

EV-50699: Security scan fails because SNMP services are running, even when SNMP is not configured.

EV-50555: When you change the static IP address (DNS) in the console and you then reboot the system, the previous IP address is updated in resolv.conf.

EV-50407: The algorithm that determines when to reset the biz network may take up to 24 hours for the biz network to re-negotiate its speed.

EV-50330: On initial deployment, the ibiz0 link speed is set to 10 Mbps on node0 until reboot.

EV-50232: Virtual CD Creation Wizard garbles text and button in Japanese version.

EV-50224: Active Directory User requires Domain Administrator rights.

EV-50213: Loading a VMware exported VM results in the console reporting "failed to load volume".

EV-50145: With a German Language version of Windows, the guest monitoring feature reports "not found" for all values.

EV-49949: VM-specific axstore settings are removed during a node power cycle, but not during a simple node reboot.

EV-49947: After upgrading a system to 7.6.0.0/2.0.0.0, the system no longer sends some e-Alerts, call-home messages, and SNMP traps.

EV-49916: P2V using virt-p2v 1.36.10 fails with the error "Can't have a partition outside the disk!" when attempting to transfer a disk.

EV-49898: Importing an exported VMware VM fails if the vmdk file name does not include "disk".

EV-49881: When a DNS server does not respond, an alert is sent stating that the management port lost connection, and the port state is changed to a warning, "lost connectivity with network".

EV-49868: A VM with an attached USB device will not boot after in-guest shutdown.

EV-49795: Cannot perform a one-node recovery of VMs.

EV-49380: The console is inaccessible after node reboot when a guest has a large, fragmented volume.

EV-49361: Attempts to generate diagnostics file can cause primary node to report an out-of-memory error.

EV-49041: A node fails to mount the root during a node replacement.

EV-47842: The Reprovision Virtual Machine wizard initially accepts container-size values that are very close to the available size of the storage group, but later reports an insufficient-space error.

Bugs Fixed in Stratus Redundant Linux Release 2.0.1.0

For information, see Bug Fixes in Stratus Redundant Linux Release 2.0.1.0.

Bugs Fixed in Stratus Redundant Linux Release 2.0.0.0

For information, see Bug Fixes in Stratus Redundant Linux Release 2.0.0.0.

CVE Fixes

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

Important Considerations

Upgrading to Release 2.1.0.0

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

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 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 2.1.0.0, download the Stratus Redundant Linux 2.1.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.

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 KB-8219.

Redeploying a ztC Edge System

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:

Deploying ztC Edge Nodes at Separate Physical Sites

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 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.

Known Issues

Temperature Sensor Information No Longer Appears on the Physical Machines Page

The Physical Machines page no longer displays temperature sensor information.

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. So, 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.

USB 3.1 Devices Not Supported

USB 3.1 devices are not supported. Use USB 3.0 devices, instead.

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.

Importing an OVA File Sometimes Fails

If you begin to import an OVA file and then the node is placed into maintenance mode or loses power, the OVA import fails, and any future attempt to import an OVA file fails. For information on a work-around for this problem, see KB-10034.

After Importing a Linux VMware OVA File, Manually Configure Network Information

Importing a Linux VMware OVA file changes the network interface and networks-scripts file. After you import the file, you need to manually configure the network information using the following procedure:

  1. On the Virtual Machines page, select the VM.

  2. Click Console in the bottom panel to open the VM login page (for additional information, see Opening a Virtual Machine Console Session).

  3. Login into the VM.

  4. Open a command prompt window.

  5. Issue the ifconfig command. In the command output, check if ip address is assigned to the virtual network interface eth0.

  6. If ip address is not assigned to eth0, list the contents of the /etc/sysconfig/network-scripts directory.

  7. Note the value of ifcfg-xxxx (though not ifcfg-lo).

  8. Rename ifcfg-xxxx to be ifcfg-eth0.

  9. Edit the ifcfg-eth0 file, changing the values of DEVICE and ONBOOT, as follows:

    DEVICE=eth0
    ONBOOT=yes

    Save the file.

  10. Issue the following command to restart network services:

    systemctl restart network
  11. Verify the IP assignment by issuing the command ifconfig. In the command output, confirm that ip address is assigned to eth0.

"Import from USB" Search Lists OVA Files in Various Directories

When you select Import from USB in the Import/Restore Virtual Machine wizard to import an OVA file, you can enter a file name or partial file name in the Search Files box. The box lists OVA files that have names matching the name entered in the box, and that reside in various directories:

For complete information on importing an OVA file, see Importing an OVF or OVA File.

Maximum Resolution of a UEFI VM Console Session

On the Virtual Machines page of the ztC 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 has a maximum resolution of 800x600. For a higher resolution, connect to the VM using a Remote Desktop Connection.

Restart VMs for vmgenid Support

After a system is upgraded to Stratus Redundant Linux Release 2.1.0.0 using an upgrade kit, support for vmgenid on VMs running Windows Server 2019, Windows Server 2016, or Windows Server 2012 is not present until after the VMs are restarted. Therefore, you must restart such VMs to enable vmgenid support after the upgrade.

Creating VCD fails when console browser is Microsoft Edge

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

To import a VMware VM, use operating system shutdown commands

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.

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

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.

After Upgrading to a Dual-Node System, VMs Display Warning Icon

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.

Mapping of Japanese Keyboards 106 and 109 For Console in IE10, IE11, or Firefox May Be Incorrect

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.

Migrating a VM With Monitoring Set Causes "No response"

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.

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 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 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 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):

The VNC console appears.

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.

Documentation Updates

The following Help topics have been added or updated since translation:

Beginning in Release 2.0.0.0, Help is available in German, Japanese, Chinese, and Portuguese.

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 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

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

    If needed, create a new account as follows:

    1. Click Register Account.
    2. 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.

    3. 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 service portal, click Knowledge Base in the left pane.
  3. 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.

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://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.