Release Notes: Automated Uptime Layer with Smart Exchange Release 2.0.0.0 (Linux)

These Release Notes (updated 3:14 PM EST on 7/8/2025) are for Automated Uptime Layer with Smart Exchange Release 2.0.0.0. See the following sections:

New Features and Enhancements

Stratus Technologies is now part of Penguin Solutions. To learn more about Penguin Solutions, visit https://www.penguinsolutions.com.

Automated Uptime Layer with Smart Exchange Release 2.0.0.0 introduces the following ztC Endurance systems running on Red Hat Enterprise Linux (RHEL) version 9.4 and Automated Uptime Layer with Smart Exchange:

  • ztC Endurance 3100 and 3110

  • ztC Endurance 5100 and 5110

  • ztC Endurance 7100 and 7110

  • ztC Endurance 9110

See Overview of Stratus ztC Endurance Systems for more information.

Important Considerations

KVM Not Supported in Automated Uptime Layer with Smart Exchange Release 2.0.0.0

Kernel-based Virtual Machine (KVM) functionality is not supported in Release 2.0.0.0.

Do Not Update the Ubuntu System Software

Do not enable Ubuntu unattended upgrades or update the Ubuntu system software of the Standby OS from any source other than Stratus unless instructed to do so. To prevent incompatibilities and ensure the proper fault-tolerant operation of your system, use only the release and software packages that are installed with the Automated Uptime Layer with Smart Exchange software. All supported Ubuntu package updates will be bundled in future releases.

Do Not Change BIOS Settings

Do not change any BIOS settings from their default settings without first being told to do so by Penguin Solutions Customer Service.

Known Issues

Missing Management IP Addresses After sra-sysconfig.exe Runs

If network changes during system configuration take longer than expected to take effect, the sra_sysconfig.exe script may not display any IP addresses after printing the message Management Addresses for ztC Endurance console.

The workaround is to wait two minutes, then run the following command to ensure the addresses are available:

/opt/stratus/sbin/zencli mgmt_addrs

Run Installation Locally When Setting Management Network IPs to Static Addresses

When performing a ztC Endurance installation that changes the management network IPs to static addresses, perform the installation from the BMC Web console Remote Control H5Viewer (the KVM), or from the monitor and keyboard connected directly to the ztC Endurance system. Otherwise, the installation may not complete successfully.

Possible Message About Duplicate IPv4 Address When snmpd.service Starts

When the Simple Network Management Protocol (SNMP) Daemon is started, the following error message may appear in the messages log:

DuplicateIPv4 address detected, some interfaces may not be visible in IP-MIB

This error message is harmless and can be safely ignored. For more information, see the RHEL documentation at https://access.redhat.com/solutions/3660111.

Embedded Network Interface Requires Manual Activation After Smart Exchange​

After removing an I/O module, the embedded I210 network interface (eno1 or eno2) is disconnected. If a Smart Exchange​ occurs and the I/O module is then re-inserted, NetworkManager does not re-establish the connection for the embedded I210 network interface, and it no longer has an assigned IP address.

To fix this issue, manually activate the connection by running the following command from the host:

  • If I/O module A is removed and re-inserted:

    nmcli con up eno1

  • If I/O module B is removed and re-inserted:

    nmcli con up eno2

Restart NetworkManager After Adapter Replacement

In cases where a PCIe adapter is part of a bonded team, the adapter is not automatically added back to the bond after it is swapped out and replaced. The new PCIe adapter appears as Online, but ztC Endurance management reports its state as Simplex.

To re-add the new PCIe adapter to the bonded team, restart NetworkManager using the following command: 

systemctl restart NetworkManager

Enable SNMP Requests to Fix Location of snmpd.conf File

On a newly installed system, the Enable SNMP Requests check box on the ztC Endurance console​ SNMP Configuration page is disabled by default. This results in the system's /etc/snmp/snmpd.conf file pointing to a non-existent file, preventing the RHEL SNMP daemon from working correctly.

To fix this problem, activate the Enable SNMP Requests check box on the ztC Endurance console​ SNMP Configuration page.

802.3ad Bond Mode Requires Setting lacp_rate to Fast to Avoid Delays

When using 802.3ad bonding mode, ping delays of 10-12 seconds can occur.

To increase response time, change lacp_rate from slow (the default) to fast by manually editing the configuration file as follows:

  1. Access the 802.3ad bonding team file: /etc/NetworkManager/system-connections/bondN.nmconnection.

  2. Add the line lacp_rate=fast under the [bond] section:

    [bond]
    lacp_rate=fast
    mode=802.3ad

  3. Run the following commands, where N is the bond number, to have NetworkManager process the change: 

    4. nmcli c reload
nmcli c down bondN
nmcli c up bondN

Static Link Aggregation Bonding Modes Encounter Delays

Adding a PCIe adapter to a team configured in static-bonding mode could result in long network delays when an I/O module is being brought up.

Certain bonding modes require that the physical switch be set up with a static link aggregation group. These bonding modes are: Balance-XOR, Balance-RR, BC, and Broadcast. However, I/O failovers may encounter delays of between 20 and 30 seconds in these conditions.

Avoid using these modes unless absolutely necessary. Alternate modes include: active-backup (default), balance-tlb, balance-alb, and 802.3ad.

Incorrect Suffix Added to Hostname After Successful Installation

After a successful ztC Endurance installation, hostnames may have an extra domain name appended, causing access failures. For example, the expected host system name is XX.cdx.eng.stratus.com, but it is incorrectly named XX.cdx.eng.stratus.com.cdx.eng.stratus.com.

To fix this issue, reset the hostname to the correct format using the following command:

hostnamectl set-hostname XX.cdx.eng.stratus.com

Verify the change by entering hostname or hostnamectl.

Do Not Modify Graphical Mode Install in Kickstart File

This note applies only if you plan to customize your RHEL installation by modifying the ztC Endurance kickstart file.

When making kickstart file modifications, do not make changes to the section # === Use graphical mode install ===. Graphic mode must remain set to graphic.

Do Not Use BIOS to Disable Wake On LAN

Setting Wake On LAN to Disabled in the BIOS does not disable this functionality. Instead, use the ethtool command with the --wol option to disable Wake On LAN. For more information, see the RHEL documentation at https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/6/html/deployment_guide/s1-ethtool#s1-ethtool.

Install ASNConnect After You Replace a Compute Module

If you replace a compute module, you must contact your authorized Penguin Solutions service representative (see Getting Help) so they can remove the ASNConnect software associated with the old compute module. After that, you can install ASNConnect on the new compute module as described in Enabling ASNConnect.

IPv6 Must Be Enabled in BMC Web Console

ztC Endurance systems are shipped with the Enable IPv6 setting selected in the BMC Web console. The ztC Endurance system does not work if you disable this setting.

The Enable IPv6 setting is located in Settings>Network Settings>Network IP Settings. When you select this setting, the Enable IPv6 DHCP setting appears; select this setting as well. For more information about the BMC Web console, see Overview of the BMC Web Console.

Installation with IPv6 Static Addresses in the yaml File Failed to Set RHEL Host IPs

If you are using an installation configuration file (zen_config.yaml) that includes IPv6 static addresses, the ztC Endurance installation may fail with error messages similar to the following:

Unable to install ztC Endurance components on the RHEL host

Or:

Error: failed to modify ipv6.addresses: invalid prefix

These errors occur because the IPv6 prefix is incorrectly appended twice to the end of the address.

To avoid this issue, specify the IPv6 prefix only at the IPv6 prefix prompt, or in the yaml field that asks for the IPv6 prefix. Do not include the prefix at the IPv6 address prompt, or in the yaml field that asks for the IPv6 address.

If this issue does occur, manually set the necessary static IPV6 addresses on the host.

Reconfiguring System from Static IPv6 Addresses to Dynamic IPv4 Addresses

If your ztC Endurance system has been configured with static IPv6 addresses and you are reconfiguring the system to use dynamic (DHCP) IPv4 addresses, perform the following procedure before running net_config.sh:

  1. Log in to one of the BMC Web consoles.

  2. Select Settings, then select Network Settings, and then select Network IP Settings.

  3. On the Network IP Settings page:

    1. Select the Enable IPv6 DHCP check box.

    2. Enter 0 in the IPv6 Address field.

    3. Click Save and exit the BMC Web console.

Repeat this procedure on the other BMC Web console.

Resolve Active Alerts Before Upgrading System Software

If you attempt to upgrade the system software and the ztC Endurance system has active alerts of any kind, including informational alerts, the upgrade fails with the following message:

Upgrade cannot proceed until all active alerts have been resolved.

After you resolve all active alerts, you can proceed with the upgrade.

Use the --forcerescan Argument to View a Mapped LUN 0

Generally, you should not map a LUN 0. However, if you do attempt to map a LUN 0 and it is not visible in the output after you run rescan-scsi-bus.sh, you may need to add the argument --forcerescan.

The current LUN numbers appear as the last digit in the host:channel:id:lun SCSI array. In the following example, LUNs 1 and 2 already exist and are mapped, and a LUN 0 has been added to the array, but the LUN 0 does not appear when you run the rescan-scsi-bus.sh: 

rescan-scsi-bus.sh
Scanning SCSI subsystem for new devices
Scanning host 0 for  all SCSI target IDs, all LUNs
sg0 changed:  device 0 0 0 0 ...
from:Enclosure 0 Channel: 00 Id: 00 Lun: 00
to: Direct-Access  TE  Model: 4006             Rev: I200
	Type:   Enclosure                        ANSI SCSI revision: 06

Scanning for device 0 0 0 1 ...
OLD: Host: scsi0 Channel: 00 Id: 00 Lun: 01
Vendor: SEAGATE  Model: 4006             Rev: I200
Type:   Direct-Access                    ANSI SCSI revision: 06
Scanning for device 0 0 0 2 ...
OLD: Host: scsi0 Channel: 00 Id: 00 Lun: 02
Vendor: SEAGATE  Model: 4006             Rev: I200
Type:   Direct-Access                    ANSI SCSI revision: 06
Scanning host 1 for  all SCSI target IDs, all LUNs
sg3 changed:  device 1 0 0 0 ...
from:Enclosure 1 Channel: 00 Id: 00 Lun: 00
to: Direct-Access  TE  Model: 4006             Rev: I200
	Type:   Enclosure                        ANSI SCSI revision: 06
Scanning for device 1 0 0 1 ...
OLD: Host: scsi1 Channel: 00 Id: 00 Lun: 01
	Vendor: SEAGATE  Model: 4006             Rev: I200
	Type:   Direct-Access                    ANSI SCSI revision: 06
Scanning for device 1 0 0 2 ...
OLD: Host: scsi1 Channel: 00 Id: 00 Lun: 02
	Vendor: SEAGATE  Model: 4006             Rev: I200
	Type:   Direct-Access                    ANSI SCSI revision: 06
0 new or changed device(s) found.
0 remapped or resized device(s) found.
0 device(s) removed.
multipath -ll
mpathb (3600c0ff0005d03e8c12e856701000000) dm-0 SEAGATE,4006
size=279G features='0' hwhandler='1 alua' wp=rw
|-+- policy='service-time 0' prio=50 status=active
| `- 0:0:0:1 sda     8:0    active ready running
`-+- policy='service-time 0' prio=10 status=enabled
`- 1:0:0:1 sdc     8:32   active ready running
mpathc (3600c0ff0005d0637839fa76701000000) dm-1 SEAGATE,4006
size=186G features='0' hwhandler='1 alua' wp=rw
|-+- policy='service-time 0' prio=50 status=active
| `- 1:0:0:2 sdd     8:48   active ready running
`-+- policy='service-time 0' prio=10 status=enabled
`- 0:0:0:2 sdb     8:16   active ready running

To view the LUN 0 along with the other LUNs in the array, add the --forcerescan argument as shown in the following example:

rescan-scsi-bus.sh --forcerescan
Syncing file systems
Scanning SCSI subsystem for new devices and remove devices that have disappeared
Scanning host 0 for  all SCSI target IDs, all LUNs
sg0 changed:  device 0 0 0 0 ...
from:Enclosure 0 Channel: 00 Id: 00 Lun: 00
to: Direct-Access  TE  Model: 4006             Rev: I200
REM: Host: scsi0 Channel: 00 Id: 00 Lun: 00    ANSI SCSI revision: 06
NEW: Host: scsi0 Channel: 00 Id: 00 Lun: 00
	Vendor: SEAGATE  Model: 4006             Rev: I200
	Type:   Direct-Access                    ANSI SCSI revision: 06
Scanning for device 0 0 0 1 ...
OLD: Host: scsi0 Channel: 00 Id: 00 Lun: 01
Vendor: SEAGATE  Model: 4006             Rev: I200
Type:   Direct-Access                    ANSI SCSI revision: 06
Scanning for device 0 0 0 2 ...
OLD: Host: scsi0 Channel: 00 Id: 00 Lun: 02
	Vendor: SEAGATE  Model: 4006             Rev: I200
	Type:   Direct-Access                    ANSI SCSI revision: 06
Scanning host 1 for  all SCSI target IDs, all LUNs
sg3 changed:  device 1 0 0 0 ...
from:Enclosure 1 Channel: 00 Id: 00 Lun: 00
to: Direct-Access  TE  Model: 4006             Rev: I200
REM: Host: scsi1 Channel: 00 Id: 00 Lun: 00    ANSI SCSI revision: 06
NEW: Host: scsi1 Channel: 00 Id: 00 Lun: 00
	Vendor: SEAGATE  Model: 4006             Rev: I200
	Type:   Direct-Access                    ANSI SCSI revision: 06
Scanning for device 1 0 0 1 ...
OLD: Host: scsi1 Channel: 00 Id: 00 Lun: 01
Vendor: SEAGATE  Model: 4006             Rev: I200
Type:   Direct-Access                    ANSI SCSI revision: 06
Scanning for device 1 0 0 2 ...
OLD: Host: scsi1 Channel: 00 Id: 00 Lun: 02
	Vendor: SEAGATE  Model: 4006             Rev: I200
	Type:   Direct-Access                    ANSI SCSI revision: 06
2 new or changed device(s) found.
[0:0:0:0]
[1:0:0:0]
0 remapped or resized device(s) found.
2 device(s) removed.
[0:0:0:0]
[1:0:0:0]

Do Not Modify Time Zone Except on RHEL Host

Other than on the RHEL host, do not modify the time zone on your ztC Endurance system. For example, do not attempt to modify the time zone on the Standby OS or in the BIOS.

Delay in Client/Server-Based Applications During Smart Exchange​ While Communicating Over IP Addresses on X710 PCIe Adapters

Any client/server-based application that communicates over an IP address that is assigned to a networked team configured over an X710 PCIe adapter may experience a 7- to 25-second delay during or after a Smart Exchange​ operation.

Accessing Stratus Knowledge Base Articles

For information about accessing Stratus Knowledge Base articles, see Getting Help.

Getting Help

If you have a technical question about ztC Endurance systems, see Getting Help.