) in the ztC Console, even though the VM still has another active A-link connection. The availability of the VM is unaffected.These Release Notes are for ztC Edge Release 1.3.0.0 (updated at 10:19 PM on 4/29/2021). See the following sections:
The Stratus Customer Service Portal provides a searchable Knowledge Base with technical articles about all Stratus products, including ztC Edge. 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.
EV-48289,EV-48275,EV-47731,EV-48317,EV-48399: Fixed restart issues with an internal process.
EV-46765: Nodes may fail to return to service after power loss.
EV-47788: The eAC may become inaccessible after system power loss.
EV-47803: A spine restart may cause a false "Node has Rebooted" alert.
EV-47807: Refine the install checks that identify the ztC Edge 100i platform.
EV-47824: The fatal alert "A sensor on node0 (or 1) is indicating a fatal problem" can be seen when it should not be.
EV-47858: Insulate volume replication status and epoch values against node power loss.
EV-47865: The heartbeat configuration file /etc/ha.d/ha.cf can be truncated on node power loss resulting in heartbeat and spine failing to start and the node failing to join the cluster.
EV-47944: /etc/lvm/lvm.conf can be truncated after ztC node power loss.
Major new features and enhancements are listed below under the release in which they became available.
ztC Edge Release 1.3.0.0 includes support for the following new features:
Release 1.2.1.0 is for bug fixes. See Bug Fixes for information.
ztC Edge Release 1.2.0.5 includes the following new features:
Also, beginning in Release 1.2.0.5, the online Help is available in German, Japanese, and Chinese.
To upgrade to the current release of ztC Edge, 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 1.3.0.0, download the Stratus Redundant Linux 1.3.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.
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:
Disable any NFS/CIFS shares before redeploying a system.
Active NFS/CIFS shares interfere with the redeployment feature. Disable the shares until you finish configuring the network settings on the new network.
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
For other important considerations about ztC Edge systems, see Important Physical Machine and Virtual Machine Considerations.
Do not click the Remove button on the Physical Machines page of the ztC Console. If you remove a node from the system, you will be unable to restore the node to service and also unable to create new VMs. If you have already clicked the Remove button, contact your Stratus service representative to restore the node to service and correct the VM issue.
If an NFS or SMB/CIFS share is mounted on a ztC Edge system and the ibiz0 (P1) network connection is lost, you may lose access to the ztC Console for several minutes, and you may need to refresh the web browser to restore the connection. To avoid failover delays, disable any shares in the host operating system when they are not in use.
When using a Windows share to import or export VMs, the share may not show up as a valid option or may not allow connection because the operating system hosting the share does not support SMB v1.0. For more information about this issue, see KB-9541.
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.
There are two methods for ejecting media from a Windows-based guest operating system:
Clicking Eject in File Explorer
If you eject media from File Explorer, you must eject the media in the ztC Console and then physically disconnect the media from the ztC Edge system before reconnecting it.
Clicking Safely Remove Hardware and Eject Media in the taskbar
If you eject media from the taskbar, you must eject the media in the ztC Console, but you do not need to physically disconnect the media from the ztC Edge system before reconnecting it.
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.
To avoid downtime, before removing a VM, always ensure that both nodes are in the running state and that neither node is in maintenance mode or in the process of synchronizing.
If you remove a VM while one node is shut down in maintenance mode, the operation may stall with the error, "There was a problem deleting vm-name." To correct the problem, you must restart the only running node.
The ztC Console may improperly validate VM names to ensure that they meet the software requirements. If you are creating, reprovisioning, or renaming a VM with an unsuitable name, the operation may fail to execute.
To avoid any problems with VM operations, ensure that your VM names meet the following requirements:
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:
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 an ztC Edge node as described in Configuring IP Settings, you must reboot the node or the system for the changes to take effect. If you do not reboot the node or the system, both the new and old settings will remain in effect, which may cause routing or connection issues.
If you change the maximum transmission unit (MTU) setting of either network0 (P1) or network1 (P2), the system automatically migrates the VMs from one node to the other. If you change the MTU for network0 (P1) specifically, the system also automatically fails over from the primary node to the secondary node.
To avoid this issue, avoid changing the MTU setting of the business networks, or change the MTU only during a planned maintenance period.
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.
Product Support and Downloads