1 gen 2023 — See the Upgrade the System (Upgrade Firmware) for the instructions for upgrading system firmware. ... ghostscript-cups, ghostscript-fonts, java-.
StorNext 7.x Xcellis Workflow Director Release Notes Contents Revision History 2 About the Xcellis Workflow Director 2 Training and Documentation Resources 2 Learn more about StorNext 7.x 3 What StorNext Releases are compatible with my system? 3 Upgrade StorNext Software and System Firmware 3 General Notes 4 Enhancements, Fixed Issues, and Notes 4 Known Issues 11 Quantum Appliance Licenses 44 Contacting Quantum 44 © 2022 Quantum Corporation. All rights reserved. Your right to copy this manual is limited by copyright law. Making copies or adaptations without prior written authorization of Quantum Corporation is prohibited by law and constitutes a punishable violation of the law. ActiveScale, DXi, DXi Accent, FlexSync, FlexTier, iLayer, Lattus, Quantum, The Quantum Logo, QXS, Scalar, StorNext, SuperLoader, Vision, and Xcellis are either registered trademarks or trademarks of Quantum Corporation and its affiliates in the United States and/or other countries. All other trademarks are the property of their respective owners. Quantum specifications are subject to change. December 2022 6-68787-01 Rev E Revision History Revision History The following StorNext Releases are supported by these Release Notes: StorNext 7 Releases Supported StorNext 7.1 StorNext 7.0.3 StorNext 7.0.2 StorNext 7.0.1 Release Notes Date January 2023 June 2022 December 2021 December 2020 About the Xcellis Workflow Director The Quantum Xcellis Workflow Director system is a workflow storage system with various configurations and options to meet your evolving storage performance and capacity needs. StorNext Connect, which is used to perform initial configuration of the server, provides ongoing, holistic monitoring of your entire StorNext environment after initial configuration. The system can operate as a StorNext SAN Client in a StorNext Metadata Network, providing LAN client access to the StorNext disk SAN. It can also provide NFS and SMB NAS access using StorNext NAS software. Training and Documentation Resources Xcellis Workflow Director Gen 2 training and documentation If you are unsure about which type of system you have visit the "Identify My System" page to determine which system you have, and to find the training and documentation resources for that specific system. Xcellis Workflow Director Release Notes 2 Learn more about StorNext 7.x Learn more about StorNext 7.x What is StorNext? StorNext® is high-performance, multi-tier shared storage designed for large, data-intensive workloads. It includes Xcellis workflow storage, extended online storage, and tape archives--all powered by StorNext, the industry's fastest streaming file system and policy-driven data management software. At the core of all Quantum scale-out storage is StorNext advanced data management--engineered to tackle the world's most demanding workloads, with the performance and efficiency needed to costeffectively achieve desired business results. StorNext 6 delivers the unique combination of high performance and advanced data management, providing cost-effective scalability and access for a wide variety of workloads and use cases, including media production, genomics research, video surveillance, geospatial imaging, VR content, and more. Learn More on the Web... Learn more about StorNext 7 and Scale-Out Storage and take a look at the StorNext 7 Documentation Center, which includes training and documentation resources for StorNext 7, including StorNext software Release Notes. What StorNext Releases are compatible with my system? See the "StorNext Upgrade Matrix" and "StorNext Appliance Compatibility" sections of the StorNext 7.x Compatibility Guide on quantum.com for information about system compatibility. Upgrade StorNext Software and System Firmware Before upgrading your system, refer to Known Issues on page 11. This section contains important information you need to know before upgrading. Xcellis Workflow Director Release Notes 3 General Notes See Upgrade the System (Upgrade Firmware) for the steps necessary to upgrade to the latest StorNext release and hardware firmware for your system. General Notes Refer to the General Notes page on quantum.com for important information you should know about your system. Enhancements, Fixed Issues, and Notes This section lists the fixed issues, enhancements and notes for different StorNext Releases supported for your system. l Enhancements and Fixed Issues for StorNext 7.1 below l Fixed Issues, and Enhancements for StorNext 7.0.3 on page 6 l Fixed Issues, and Enhancements for StorNext 7.0.2 on page 6 l Fixed Issues and Enhancements for StorNext 7.0.1 on page 8 Enhancements and Fixed Issues for StorNext 7.1 Enhancements: l As of the StorNext 7.1 release, Quantum H2000 and F2100 storage is now supported for metadata (metadata and HAFS), and combo (metadata, HAFS, and data) storage configurations for Xcellis Workflow Director systems. l For Xcellis Workflow Director Gen 2 systems, within the next few months, the server used in these systems will no longer be shipped with a PERC RAID card installed. For systems without the PERC card, a software RAID is used instead. This release adds support for the software RAID used in those systems. Fixed Issues: CR Number 80416 SR Number(s) n/a Description StorNext upgrades update R640 BIOS firmware to 2.15.1 for new security fixes Xcellis Workflow Director Release Notes 4 Enhancements, Fixed Issues, and Notes CR Number 80550 80446 80289 80276 80274 SR Number(s) n/a 680010 671453 668727 668727 80086 80061 79952 663515 n/a 651056 79518 638473 Description StorNext no longer issues RAS messages for omcliproxy core failures Nessus flagged PHP on ports 416, 441 and 442 as vulnerable for 4 newest CVEs - Upgrade php to 7.4.31 The pre-upgrade check ignores http_proxy settings and completes successfully The pre-upgrade check provides vaild error messages when it fails, even when the root file system is running low on available space The upgrade timeout found in /opt/DXi/Upgrade/UPGRADESYNCDELAY has been increased from 10800 to 14400, which allows for upgrades longer than 10800 seconds to succesfully upgrade. Fix for an issue identified during a Qualys security scan CentOS Security Update for Open Secure Sockets Layer (OpenSSL) Upgraded Nessus PHP from 7.4.x to 7.4.25 . On the pre-upgrade check, if a firmware bundle (fw_bundle) version mismatch shows that the firmware installed is newer than the firmware expected, the message is now "INFORMATIONAL" rather than being listed as a "WARNING" Example of a 7.1 firmware mismatch message: INFORMATIONAL: Dell iDRAC9/Life Cycle Controller - iDRAC Information, iDRAC Firmware Information,Firmware Version: Mismatch; Expected: 'lower', Found: higher' For StorNext upgrades, we now verify the md5 checksum file for both .fw files and warn about the image file not matching. We no longer support beginning the upgrade if one of the files does not match the checksum it is validated against. Xcellis Workflow Director Release Notes 5 Enhancements, Fixed Issues, and Notes CR Number 78885 SR Number(s) 610068 628424 Description Replacement 1TB drives are now rebuilt correctly on Xcellis R640 systems. l See the StorNext 7.1 Release Notes for information about StorNext software updates for this release. l See the "StorNext Software Compatibility" section of the StorNext 7.x Compatibility Guide for supported appliances. l See the Upgrade the System (Upgrade Firmware) for the instructions for upgrading system firmware. Fixed Issues, and Enhancements for StorNext 7.0.3 Fixed Issues: CR Number 79783 79890 80006 80161 SR Number(s) n/a n/a 631455 653040, 655940, 655938, 657852 Description In the /etc/multipath.conf file included with 7.0.3, the entries for all devices using rr_min_io have been changed to rr_min_io_rq. After an upgrade to 7.0.2 and Appliance Controller 3.1.0, during an iSCSI conversion from v2 to v3, the MDC could SMITH itself. This is longer a problem after upgrading to 7.0.3 and Appliance Controller 3.1.1. The qxsarray utility in the Appliance Controller CLI now uses https for secure data transfer rather than as plain text. Upgrades now correctly install BIOS and iDRAC on Xcellis Workflow Director (R630) systems. l See the StorNext 7.0.3 Release Notes for information about StorNext software updates for this release. l See the "StorNext Software Compatibility" section of the StorNext 7.x Compatibility Guide for supported appliances. l See the Upgrade the System (Upgrade Firmware) for the instructions for upgrading system firmware. Fixed Issues, and Enhancements for StorNext 7.0.2 Enhancements: l Upgraded the appliance operating system to CentOS 7.9 Fixed Issues: Xcellis Workflow Director Release Notes 6 Enhancements, Fixed Issues, and Notes CR Number 79350 79317 79300 79275 79273 79254 79181 79126 79052 78835 SR Number(s) N/A N/A N/A 612947, 612900 618931 N/A 616975 N/A 612947, 612900 N/A Description Mellanox InfiniBand drivers now correctly identify Mellanox cards after MLNX_OFED installation. The MLNX_OFED_LINUX LTS versions have been updated to include support for ConnectX-3 cards. The Infiniband Service Menu no longer uses the connectx_port_config command since it's no longer supported in new MLNX_OFED_LINUX package. To avoid lengthy database shutdowns during upgrades, in 7.0.2 we now check the installed MySQL version. A script is now installed which determines if a MySQL clean shutdown should performed before upgrading. Consistency checks have been added into StorNext appliance software to assist with drive failures. R640 hardware - updated iDRAC firmware to v4.22.00.53 to address a security issue in v4.40.00.00 and later iDRAC firmware. The collect_snconnect routine in collect-local now creates snapshots which no longer include prior snapshots and dset output in /usr/adic/HAM/shared/capture_state, making for significantly smaller capture log files. Note: This change requires an update to the latest StorNext Connect release. iDRAC/IPMI password requirements have changed for R640 appliances. On a system reboot, you will see an admin alert indicating that the IPMI remote password needs to be changed. To change the IPMI remote password, see: https://qsupport.quantum.com/kb/Flare/Content/appliances /ChangeiDRAC.htm Upgrades to StorNext 7.0.1 took many more hours longer than previous upgrades to shut down the MySQL database. This is fixed for 7.0.2 and is no longer an issue. Modified firmware install scripts to handle both .BIN and .EXE files. Xcellis Workflow Director Release Notes 7 Enhancements, Fixed Issues, and Notes CR Number SR Number(s) Description 78663 N/A Removed unused packages previously installed with NAS. This includes: cups, cups-filesystem, cupsfilters, cups-filters-libs, ghostscript, ghostscript-cups, ghostscript-fonts, java1.8.0-openjdk, and xorg-x11-fonts-Type1. 76153 * Multiple SRs addressed. See below Qualys scans have been completed for 7.0.2. * 443251,443252,443253,443254,443255,443256,443258,443259,443260,443261,609514, 443251,443252,443253,443254,443255,443256,443258,443259,443260,443261 l See the StorNext 7.0.2 Release Notes for information about StorNext software updates for this release. l See the "StorNext Software Compatibility" section of the StorNext 7.x Compatibility Guide for supported appliances. l See the Upgrade the System (Upgrade Firmware) for the instructions for upgrading system firmware. Fixed Issues and Enhancements for StorNext 7.0.1 Enhancements: l Upgraded the appliance operating system to CentOS 7.7 CR Number 78030 77951 77884 77407 77357 77326 SR Number(s) N/A N/A N/A N/A N/A N/A Description Updated the FlexSync software to 2.2.1. Updated the Appliance Controller software to 3.0.1. Updated the CBA (computer-based analytics) StorNext Appliance Agent to 2585. Support for the QLogic 2772 FC HBA has been added. This card replaces the QLogic 2742 FC HBA. Added the fcoe-utils RPM (which includes the fcc.sh tool for troubleshooting Fibre Channel issues from the RHEL "fcoeutils" package) to the StorNext 7.0.1 appliance software. Updated iDRAC firmware to address safety issues in previous iDRAC firmware. Xcellis Workflow Director Release Notes 8 Enhancements, Fixed Issues, and Notes CR Number 77110 77096 76834 76743 76688 76685 SR Number(s) N/A N/A N/A N/A N/A 545545 76539 76484 75963 75926 75835 75726 75395 N/A 540318 N/A N/A N/A 544346 517419 Description Updated default iscsi initiator tuning configuration in the iscsid.conf file. Updated the /etc/multipath.conf file to include additional Quantum hardware, such as FSeries storage arrays. Updated the OpenManage Server Administrator (OMSA) agent from 9.2.0 to 9.4.0. Remove the Object Store (SWIFT stack) from StorNext 7.0.1 appliance software and the Appliance Controller. Set the permitted/supported software upgrade paths for StorNext 7.0.1 appliance software. Fixed an issue where enabling the SNMP stornext agent (dsm_sa_snmpd) could cause the agent to be stopped, which, as a result, would cause the server node's hardware status to be reported as unknown(Red) in the StorNext GUI under Reports > Hardware Status. Updated Moilla Firefox shipped in CentOS7 to 68.4.1-1. Moved code to fix an issue for management of DAE VMs from the StorNext GUI. Updated Java from JRE 1.8.0.192-1 to the open JDK 1.8.0_ 242 version included in CentOS7. Updated the StorNext 7.0.1 appliance software to include the lldpad utility. Updated the StorNext 7.0.1 appliance software to include the fio (Flexible I/O Tester) RPM included in CentOS7. Operating system software has been upgraded to CentOS 7.7. Mellanox drivers are no longer removed from the system if a Mellanox card is not detected in the system during firmware upgrades. This previously could have caused DAE to malfunction. Xcellis Workflow Director Release Notes 9 Enhancements, Fixed Issues, and Notes CR Number 75394 74930 74811 73126 SR Number(s) 517419 520303, 556391 N/A N/A Description DAE updated to correctly displays all configured StorNext file systems on the Tools > Dynamic Application Environment page in the StorNext GUI after a DAE VM is started. When the system is upgraded to StorNext 7.0.1, it no longer exports /usr/cvfs/CLIENTS. StorNext RPMs with Intel MDS security fixes have been updated for StorNext 7.0.1 appliance software. StorNext 7.0.1 appliance software updates have been implemented to address CVE-1999-0514 Fraggle UDP attacks. l See the StorNext 7.0.1 Release Notes for information about StorNext software updates for this release. l See the "StorNext Software Compatibility" section of the StorNext 7.x Compatibility Guide for supported appliances. l See the Upgrade the System (Upgrade Firmware) for the instructions for upgrading system firmware. Xcellis Workflow Director Release Notes 10 Known Issues Known Issues This section lists the known issues that could potentially affect your system. CR Number Customer SR Description Number 80650 N/A If Bond 1 (typically configured with port em2) is not configured during initial system configuration the system can apply settings to Bond 1 which cause the cvfs file system to not mount. If you check, the following error will be included in the /var/log/messages file: 2023-01-18-09:13:46.244095 leo kernel: CVFS: Cannot get IP address of NIC with MAC 24-6e-96-a2-a2-59 error 'Not found' (2) 80640 N/A Workaround: To fix this issue, see 80650 Workaround: Fix the Bond 1 configuration Applies to Xcellis Workflow Director (R630), Xcellis Foundation, Artico (R630), and Xcellis Workflow Extender (R630) systems. On systems reinstalled from ISO or if a Mellanox Connect CX3 card is installed after initial system configuration, DNS configuration settings are removed during the ISO rebuild or after the card is added, causing DNS resolution to fail. Workaround: If DNS resolution fails on your system, you will need to reconfigure StorNext DNS server settings. See 80640 Workaround: Configure missing DNS settings. Xcellis Workflow Director Release Notes 11 Known Issues CR Number Customer SR Description Number 80637 N/A In some rare occasions upgrades to the Appliance Controller might report an upgrade failure even if the upgrade was successful. To validate if the upgrade failure is a false positive look for this message in the controller log: server.py:142 Appliance controller Failed: local variable 'pid_list' referenced before assignment 80565 N/A 80541 80472 678713 80393 676195 Workaround: To resolve this issue, see 80637 Workaround: Appliance Controller upgraded but indicates it did not. In StorNext 7.1, when a StorNext VIP is set in the StorNextUI during HA configuration steps, the HA conversion on Node 2 prevents the StorNext GUI from working. Workaround: See 80565 Workaround: Restart "docker services" on Node 2. The appliance StorNext upgrade can report errors and BIOS and iDRAC mismatch errors during the upgrade. Workaround: If this issue is seen, reboot the iDRAC. See 80541 Workaround: Reboot iDRAC on page 24. Then attempt to upgrade the system again. If your system's root file system uses a lot of storage space, attempting to import a large OVA file into DAE can fill up /var, which will trigger RAS events and prevents import of the virtual machine in DAE. Workaround: If you experience this issue, contact Quantum support. When you contact Quantum, reference Bug 80453. A RAS ticket may be displayed in the StorNext GUI that indicates an omcliproxy segfault error happened while an IPv6 is bounced on server node , especially when workload on the system is high. Workaround: A workaround for this issue is being investigated. For now, since the omcliproxy utility error message is benign, it can be ignored, and the core file can be deleted. Xcellis Workflow Director Release Notes 12 Known Issues CR Number Customer SR Description Number 80334 673385 When attempting to access HPE 3par configured LUNs on Xcellis Workflow Director host systems using QLE2694L Fibre Channel HBAs, the HBAs can initiate a qla2xxx 10.02.01.00.a14-k1 crash, and produce firmware dump files. When this happens, it may cause the server to reboot. Workaround: See 80334 Workaround: HBA crash and firmware dump files 80181 N/A When there is a disk or disk partition failure in software RAID partitions, a RAS ticket will be generated in the StorNext GUI. However, currently under the Event Details on the ticket the "View Recommended Actions" is missing the workaround for this failure. Workaround: There is no workaround for the missing information from the "View Recommended Actions" link in the ticket. We are providing the information here. See 80181: RAS ticket recommended actions for software RAID failures. 80121 N/A The StorNext upgrade firmware/bios fails silently even though the upgrade progress shows that the firmware update had completed. Workaround: See 80121 Workaround: Firmware/BIOS fails silently during StorNext upgrade on page 27. 80099 N/A After the StorNext upgrade completes, StorNext Connect may be left in a partially-operational or inoperable state. If this happens stop and start StorNext Connect manually to attempt to resolve the situation. Workaround: See 80099 Workaround: Potential StorNext Connect issues after you upgrade StorNext on page 31. Xcellis Workflow Director Release Notes 13 Known Issues CR Number Customer SR Description Number 79545 N/A Boot errors may be displayed when connected to F-Series RAID storage. Example: 2021-11-10-09:31:29.643969 rhel-dmraid-activation: ERROR: unsupported sector size 4096 on /dev/sdd. 79052 612947, 612900 This error is shown because the dmraid software RAID device running on the appliance only supports disk partitions that have 512 byte sector block size, and F-Series storage is configured with disk partitions configured with a 4096 byte sector block size. Workaround: There is no workaround for this error. However, these errors do not cause any operational errors, and may be safely ignored. The following applies to Xcellis Workflow Director Gen 2 and Xcellis Workflow Director (R630) systems ONLY. It does not apply to other server model names/generations. Upgrades to StorNext 7.0.1 may take many more hours longer than previous upgrades. It can take several hours to shut down the MySQL database. If the upgrade is taking an unusually long time, this database issue is most likely affecting the delay. Caution: DO NOT attempt to shut down or reboot the server nodes if the upgrade is taking a long time. Note: This was fixed in StorNext 7.0.2, so any upgrades directly to 7.0.2 without first upgrading to 7.0.1 will not experience this issue. Workaround: There is no workaround for this for StorNext 7.0.1. To speed up the MySQL database conversion, upgrade to StorNext 7.0.2 or later and skip the upgrade to 7.0.1, if possible. Xcellis Workflow Director Release Notes 14 Known Issues CR Number Customer SR Description Number 77317 N/A Adding a DAE virtual machine to a file system created on a QXS or H-Series LUN can create a RAS alert stating: Excessive fragmentation detected in file "/DAE_Boot_ Disk_location/pk-DAE-vm.qcow2", inode 0x4e800000ef0b19 (decimal inum 15665945)' Workaround: While this issue is not currently fixed, the message itself may be disabled. To disable the RAS alert, change the value of the extentCountThreshold parameter in the file system configuration file to "0". For information about file system configuration files, see: https://qsupport.quantum.com/kb/flare/Content/stornext/SN6_ DocSite/Default.htm#Guide_Tuning/Topics/Example_FSM_Configuratio.htm 74202, N/A 67955, HYDRA4326 If NAS is configured on the system and StorNext services are stopped, StorNext services can fail to stop completely. This can block server fail-over and potentially leaves managed file systems without running FSMs. See 74202 StorNext services can fail to stop completely when NAS is Configured and StorNext services are stopped on page 32 for an in-depth explanation of the issue and several alternate workarounds. 73688 N/A When the /var directory on the appliance gets full, the following serious errors can occur: l Network communication errors on the server node l iDRAC is not accessible l The server node gets stuck during reboot and require a physical power cycle See also Leave Space on Appliance File Systems on the Appliance InfoHub. Workaround: Keep additional space available on /var. Xcellis Workflow Director Release Notes 15 Known Issues CR Number Customer SR Description Number 70067 N/A Issue: CentOS 7 systems display log files with the journalctl command. Any commands executed as the rootsh user are logged to the system log file . A syslog filter sends all rootsh log commands to /var/log/rootshell. This causes excessive information to be captured in the journalctl log file, and makes the log file difficult to read. Workaround: There is a script to use which removes unnecessary command line output from the syslog file for CentOS7 systems running StorNext 6.0.5 or later: See the journalctl Filter Script For StorNext releases prior to 6.0.5, contact Contacting Quantum on page 44 and refer to TSB 2998. 68732 N/A Issue: If a configured bridge device assigned to a DAE virtual machine (VM) is removed on the Networking page of the StorNext GUI, you will not be able to start the DAE VM. Workaround: If the virtual machine cannot be started because the bridge was removed, do the following: 1. Recreate the bridge in the StorNext GUI. OR a. Open an ssh session to the command line of the system and run virsh edit <vmname>. This opens the <vmname> file for editing using vi commands. b. Remove the bridge entries from the XML file using vi commands. 2. When finished making the changes, enter the following to save the changes and exit the editor: :wq Xcellis Workflow Director Release Notes 16 Known Issues CR Number Customer SR Description Number 55384 N/A Issue: If dmnfsthreads is not set on mount, nfsds may be over-commited when there are many NFS processes waiting for offline files. Workaround: For managed file systems serving NFS, Quantum recommends using the "dmnfsthreads=16" mount option. This setting ensures that NFS remains responsive when Storage Manager is retrieving data from an archive tier. 55318 N/A Issue: Strange UID on ACL when file created on non ads client. Workaround: All systems accessing the StorNext SAN or LAN clients, or the NAS clients, must be part of the same identity domain. Accessing StorNext from different identity domains can result in inconsistent file ownership attributes, as well as potential access problems. 45702 N/A Issue: If you replace an HDD drive with an SSD or vice versa, the StorNext GUI may display a "Missing" status and an equivalent RAS ticket, instead of displaying an "Incompatible" status. Workaround: Replacement drives must be the identical type of drive removed. HDDs can only use HDD spares, and SSDs can only use SSD spares. Replacement drives must also be the same size or larger than the failed drive. The array controller will generate errors if an incompatible drive is used as a replacement. 38128 1395540 Issue: Using the GUI while a large Media import is kicked off via the command line can cause the StorNext GUI to timeout or crash. Workaround: Wait until a bulk load from tape is finished prior to opening the StorNext GUI. Xcellis Workflow Director Release Notes 17 Known Issues 80650 Workaround: Fix the Bond 1 configuration 1. Log in to the CLI: a. Open an SSH connection to the appropriate server and use the IP address assigned to the node on the Management or LAN Client network, or use the Service Port IP address. Service Port IP addresses: l Node 1 : 10.17.21.1 (dual-server node systems) l Node 2 : 10.17.21.2 (dual-server node, or "HA-ready" single-server node systems) Note: Node 2 is the server node sold with single-node (non-HA) Xcellis Workflow Director and Artico systems. It is also used for installation using the StorNext Connect Install app, for both single-node and dual-node systems only. b. Initiate an ssh session to the system using Terminal or PuTTY: To ssh into the system a. Log in to the command line using the following credentials: l User name: stornext l Password: <stornext user account password> Note: "password" is the default password for the stornext user account. If the password has been changed, use the current password. Beginning with StorNext 7.0.2, you must change the default password for the stornext user account. As of StorNext 7.0.2, the first time you log in, you will be prompted to change the password to a different one. b. Enter sudo rootsh to gain root user access. c. Enter the password for the stornext user account again. 2. Manually change the first line of the /etc/sysconfig/network-scripts/ifcfg-bond1 file from DEVICE=bond0:2 to DEVICE=bond1:2. The vi editor is included in CentOS installed on your system. The following Google search link provides links for editing with vi: https://www.google.com/search?q=edit+with+vi Note: When finished making changes with the vi editor, save and exit the file using :wq!. 80640 Workaround: Configure missing DNS settings Configure your DNS settings: Xcellis Workflow Director Release Notes 18 Known Issues 1. Log in to the CLI: a. Open an SSH connection to the appropriate server and use the IP address assigned to the node on the Management or LAN Client network, or use the Service Port IP address. Service Port IP addresses: l Node 1 : 10.17.21.1 (dual-server node systems) l Node 2 : 10.17.21.2 (dual-server node, or "HA-ready" single-server node systems) Note: Node 2 is the server node sold with single-node (non-HA) Xcellis Workflow Director and Artico systems. It is also used for installation using the StorNext Connect Install app, for both single-node and dual-node systems only. b. Initiate an ssh session to the system using Terminal or PuTTY: To ssh into the system a. Log in to the command line using the following credentials: l User name: stornext l Password: <stornext user account password> Note: "password" is the default password for the stornext user account. If the password has been changed, use the current password. Beginning with StorNext 7.0.2, you must change the default password for the stornext user account. As of StorNext 7.0.2, the first time you log in, you will be prompted to change the password to a different one. b. Enter sudo rootsh to gain root user access. c. Enter the password for the stornext user account again. 2. Open the Service Menu: a. Launch the Service Menu. Enter: sh /opt/DXi/scripts/service.sh -admin The Service Menu displays. 3. Navigate to More Tools > Engineering Tools > Base OS Network Setup > Configure host settings. 4. Click <ENTER> for Hostname. 5. Click <ENTER> for Default Gateway IP. Xcellis Workflow Director Release Notes 19 Known Issues 6. Enter the Domain Name,default will show the node name, so replace node-1 or node-2 (the system defaults) with a valid domain name to use. 7. Enter one or more (comma-separated) DNS IP addresses for the system. Once you press <ENTER>, you should see the settings apply similar to: INFO: *** script started with arguments: addhost --hostname myhostname1 -domain mydomain.local --dns 10.20.219.63 --defaultgateway 10.20.216.1,10.20.216.2 *** INFO: *** script completed successfully *** The Network Menu displays again. 8. Select the Activate Network Changes option to apply the DNS changes. 9. Close the SSH session for this server node. For single-server node systems, the DNS settings change is now complete. For dual-server node systems, continue to the next step. 10. Log in to the CLI for the other server node: a. Open an SSH connection to the appropriate server and use the IP address assigned to the node on the Management or LAN Client network, or use the Service Port IP address. Service Port IP addresses: l Node 1 : 10.17.21.1 (dual-server node systems) l Node 2 : 10.17.21.2 (dual-server node, or "HA-ready" single-server node systems) Note: Node 2 is the server node sold with single-node (non-HA) Xcellis Workflow Director and Artico systems. It is also used for installation using the StorNext Connect Install app, for both single-node and dual-node systems only. b. Initiate an ssh session to the system using Terminal or PuTTY: Xcellis Workflow Director Release Notes 20 Known Issues To ssh into the system a. Log in to the command line using the following credentials: l User name: stornext l Password: <stornext user account password> Note: "password" is the default password for the stornext user account. If the password has been changed, use the current password. Beginning with StorNext 7.0.2, you must change the default password for the stornext user account. As of StorNext 7.0.2, the first time you log in, you will be prompted to change the password to a different one. b. Enter sudo rootsh to gain root user access. c. Enter the password for the stornext user account again. 11. Open the Service Menu: a. Launch the Service Menu. Enter: sh /opt/DXi/scripts/service.sh -admin The Service Menu displays. 12. Navigate to More Tools > Engineering Tools > Base OS Network Setup > Configure host settings. 13. Click <ENTER> for Hostname. 14. Click <ENTER> for Default Gateway IP. 15. Enter the Domain Name,default will show the node name, so replace node-1 or node-2 (the system defaults) with a valid domain name to use. 16. Enter the identical DNS IP address/addresses entered for the other server node. 17. Once you press <ENTER>, you should see the settings apply similar to: 18. INFO: *** script started with arguments: addhost --hostname myhostname1 -domain mydomain.local --dns 10.20.219.63 --defaultgateway 10.20.216.1,10.20.216.2 *** INFO: *** script completed successfully *** 19. The Network Menu displays again. 20. Select the Activate Network Changes option to apply the DNS changes. 21. Close the SSH session for this server node. Xcellis Workflow Director Release Notes 21 Known Issues For dual-server node systems, the DNS settings change is now complete. 80637 Workaround: Appliance Controller upgraded but indicates it did not 1. To determine if the upgrade is incomplete, locate the following error message in the /var/log/snnas_ controller log file: server.py:142 Appliance controller Failed: local variable 'pid_ list' referenced before assignment 2. Log in to the server node: a. Open an SSH connection to the appropriate server and use the IP address assigned to the node on the Management or LAN Client network, or use the Service Port IP address. Service Port IP addresses: l Node 1 : 10.17.21.1 (dual-server node systems) l Node 2 : 10.17.21.2 (dual-server node, or "HA-ready" single-server node systems) Note: Node 2 is the server node sold with single-node (non-HA) Xcellis Workflow Director and Artico systems. It is also used for installation using the StorNext Connect Install app, for both single-node and dual-node systems only. b. Initiate an ssh session to the system using Terminal or PuTTY: To ssh into the system a. Log in to the command line using the following credentials: l User name: stornext l Password: <stornext user account password> Note: "password" is the default password for the stornext user account. If the password has been changed, use the current password. Beginning with StorNext 7.0.2, you must change the default password for the stornext user account. As of StorNext 7.0.2, the first time you log in, you will be prompted to change the password to a different one. b. Enter sudo rootsh to gain root user access. c. Enter the password for the stornext user account again. 3. Verify the Appliance Controller was upgraded and is running the latest/expected release on the current server node: Xcellis Workflow Director Release Notes 22 Known Issues qtmcontroller -c 'system show version' 4. If the release is installed as expected. Enter the following on the server node to remove the touch file placed on the system to indicate an upgrade issue on the server node: rm /var/DXi/upgrade_ notify 80565 Workaround: Restart "docker services" on Node 2 1. Log into the CLI of server node 2: a. Open an SSH connection to the appropriate server and use the IP address assigned to the node on the Management or LAN Client network. b. Initiate an ssh session to the system using Terminal or PuTTY: To ssh into the system a. Log in to the command line using the following credentials: l User name: stornext l Password: <stornext user account password> Note: "password" is the default password for the stornext user account. If the password has been changed, use the current password. Beginning with StorNext 7.0.2, you must change the default password for the stornext user account. As of StorNext 7.0.2, the first time you log in, you will be prompted to change the password to a different one. b. Enter sudo rootsh to gain root user access. c. Enter the password for the stornext user account again. 2. Enter the docker restart command: systemctl restart docker 3. Exit the CLI. 4. Launch the StorNext User Interface again. Xcellis Workflow Director Release Notes 23 Known Issues 80541 Workaround: Reboot iDRAC 1. Log in to the server node: a. Open an SSH connection to the appropriate server and use the IP address assigned to the node on the Management or LAN Client network, or use the Service Port IP address. Service Port IP addresses: l Node 1 : 10.17.21.1 (dual-server node systems) l Node 2 : 10.17.21.2 (dual-server node, or "HA-ready" single-server node systems) Note: Node 2 is the server node sold with single-node (non-HA) Xcellis Workflow Director and Artico systems. It is also used for installation using the StorNext Connect Install app, for both single-node and dual-node systems only. b. Initiate an ssh session to the system using Terminal or PuTTY: To ssh into the system a. Log in to the command line using the following credentials: l User name: stornext l Password: <stornext user account password> Note: "password" is the default password for the stornext user account. If the password has been changed, use the current password. Beginning with StorNext 7.0.2, you must change the default password for the stornext user account. As of StorNext 7.0.2, the first time you log in, you will be prompted to change the password to a different one. b. Enter sudo rootsh to gain root user access. c. Enter the password for the stornext user account again. 2. Open the Service Menu: a. Launch the Service Menu. Enter: sh /opt/DXi/scripts/service.sh -admin The Service Menu displays. 3. Navigate to Hardware Configuration > Setup IPMI > Configure IPMI. 4. On the prompt to set to system defaults, enter yes. 5. Confirm setting IPMI to system defaults. The iDRAC/IPMI will reboot. For single-server node systems, the procedure is complete. Xcellis Workflow Director Release Notes 24 Known Issues For dual-server node systems: 6. Reboot the iDRAC on the other server node using the steps you just completed on this server node. 80334 Workaround: HBA crash and firmware dump files When you experience this issue, you need to set the ql2xenabledif_tgt value to 0 and the qlport_ down_retry value to 14: 1. Create the /etc/modprobe.d/hpe.conf file. Or, if it exists, create another unique but identifiable file name for this setting) 2. Log in to the server node: a. Open an SSH connection to the appropriate server and use the IP address assigned to the node on the Management or LAN Client network. b. Initiate an ssh session to the system using Terminal or PuTTY: To ssh into the system a. Log in to the command line using the following credentials: l User name: stornext l Password: <stornext user account password> Note: "password" is the default password for the stornext user account. If the password has been changed, use the current password. Beginning with StorNext 7.0.2, you must change the default password for the stornext user account. As of StorNext 7.0.2, the first time you log in, you will be prompted to change the password to a different one. b. Enter sudo rootsh to gain root user access. c. Enter the password for the stornext user account again. 3. Display the contents of the /etc/modprobe.d/hpe.conf file: cat /etc/modprobe.d/hpe.conf It should contain the following entries: options qla2xxx qlport_down_retry=14 options qla2xxx ql2xenabledif_tgt=0 If not, add retry and tgt options to the file. Xcellis Workflow Director Release Notes 25 Known Issues 4. If you made changes to the file, save the file. 5. Recreate the initramfs with this new information. Note: Do not reboot the system before completing the following 3 steps. 6. Move the img: mv /boot/initramfs-$(uname -r).img /boot/initramfs-$(uname -r).img.prehpe 7. Create the initial image used by the kernel for preloading the block device modules: Note: There are two dashes before kver in the following command. dracut -kver $(uname -r) 8. Enter the following to set the reboot options that ensure the new initramfs file is generated: ls /boot/initramfs-$(uname -r).img 9. Reboot the node. Enter: reboot 10. After the reboot, verify the qlport_down_retry value is now set to 14 as described here: cat /sys/module/qla2xxx/parameters/qlport_down_retry 80181: RAS ticket recommended actions for software RAID failures 1. Log in to the CLI: a. Open an SSH connection to the appropriate server and use the IP address assigned to the node on the Management or LAN Client network, or use the Service Port IP address. Service Port IP addresses: l Node 1 : 10.17.21.1 (dual-server node systems) l Node 2 : 10.17.21.2 (dual-server node, or "HA-ready" single-server node systems) Xcellis Workflow Director Release Notes 26 Known Issues Note: Node 2 is the server node sold with single-node (non-HA) Xcellis Workflow Director and Artico systems. It is also used for installation using the StorNext Connect Install app, for both single-node and dual-node systems only. b. Initiate an ssh session to the system using Terminal or PuTTY: To ssh into the system a. Log in to the command line using the following credentials: l User name: stornext l Password: <stornext user account password> Note: "password" is the default password for the stornext user account. If the password has been changed, use the current password. Beginning with StorNext 7.0.2, you must change the default password for the stornext user account. As of StorNext 7.0.2, the first time you log in, you will be prompted to change the password to a different one. b. Enter sudo rootsh to gain root user access. c. Enter the password for the stornext user account again. 2. Open the Service Menu: a. Launch the Service Menu. Enter: sh /opt/DXi/scripts/service.sh -admin The Service Menu displays. 3. Navigate to More Tools > SW RAID Tools. 4. To repair a software RAID configuration, select the SW RAID Repair option. 80121 Workaround: Firmware/BIOS fails silently during StorNext upgrade To check if there was a failure of applying Dell f/w updates, do the following. First, og in to the CLI of the server node that is currently not acting as primary, which prevents a failover if a manual CLI re-install of the StorNext software/reboot is required after the check. We will repeat the steps for the other server node during this process, and upgrade that firmware manually from the CLI, if needed. 1. Open an SSH connection to the appropriate server and use the IP address assigned to the node on the Management or LAN Client network, or use the Service Port IP address. Xcellis Workflow Director Release Notes 27 Known Issues Service Port IP addresses: l Node 1 : 10.17.21.1 (dual-server node systems) l Node 2 : 10.17.21.2 (dual-server node, or "HA-ready" single-server node systems) Note: Node 2 is the server node sold with single-node (non-HA) Xcellis Workflow Director and Artico systems. It is also used for installation using the StorNext Connect Install app, for both single-node and dual-node systems only. 2. Initiate an ssh session to the system using Terminal or PuTTY: To ssh into the system a. Log in to the command line using the following credentials: l User name: stornext l Password: <stornext user account password> Note: "password" is the default password for the stornext user account. If the password has been changed, use the current password. Beginning with StorNext 7.0.2, you must change the default password for the stornext user account. As of StorNext 7.0.2, the first time you log in, you will be prompted to change the password to a different one. b. Enter sudo rootsh to gain root user access. c. Enter the password for the stornext user account again. 3. From the CLI, change to the firmware directory. Enter: cd /opt/DXi/firmware 4. From the CLI, run the following command. Enter: ./fw_regenall.sh Example output: fw_bundle: Performing firmware cleanup. fw_bundle: Firmware cleanup completed successfully. fw_bundle: Checking Firmware Bundle Version. fw_bundle: Need to generate CoR files for the first time. fw_bundle: Performing firmware CoR generation... fw_bundle: Firmware CoR generation completed successfully. Xcellis Workflow Director Release Notes 28 Known Issues fw_bundle: Performing firmware description report. fw_bundle: Generating firmware description manifests. fw_bundle: Firmware manifest generation is disabled. fw_bundle: Generating firmware bundle manifest. fw_bundle: Firmware manifest generation is disabled. fw_bundle: Generation of the firmware bundle manifest completed successfully. fw_bundle: Performing firmware bundle report. fw_bundle: Performing TXT firmware report. fw_bundle: Performing GUI firmware report. fw_bundle: GUI Firmware reporting completed successfully. fw_bundle: TXT Firmware reporting completed successfully. fw_bundle: Firmware reporting completed successfully. At this time, you could check the firmware versions installed by checking the FirmwareReport.txt file. To view the file contents, enter: cat /opt/DXi/hwdetect/FirmwareReport.txt 5. From the CLI, run the following command. Enter: ./fw_check.sh There are three possible outputs that you may seewhen you run the fw_check.sh command: l Example Output #1 - If you see the following message, a firmware IS NOT required: fw_bundle: Performing firmware check. . . fw_bundle: Firmware check completed successfully. All firmware is up-to-date. The firmware check output above shows that the firmware installed on the system is up-to-date. There are no further actions to take. You can exit the rootsh session, and close the SSH terminal client. l Example Output #2 - If you see the following message, a firmware update IS NOT required: Xcellis Workflow Director Release Notes 29 Known Issues fw_bundle: Performing firmware check. fw_bundle: WARNING: Dell r630 iDRAC8/Life Cycle Controller - iDRAC Information, iDRAC Firmware Information, Firmware Version: Mismatch; Expected: '2.70.70.70', Found: '2.75.75.75' fw_bundle: WARNING: Dell r630 BIOS - BIOS Information, BIOS Firmware Information, Version: Mismatch; Expected: '2.9.1', Found: '2.11.0'e. . . fw_bundle: WARNING: One or more firmware packages have a mismatched configuration. The firmware check output above shows that the firmware installed on the system is newer than the firmware included in the StorNext software update. There are no further actions to take. You can exit the rootsh session, and close the SSH terminal client. l Example Output #3 - If you see the following message, a firmware update IS required. The firmware check shows that there is one or more firmware on the system that is older than what is included in the included in the StorNext software update: fw_bundle: Performing firmware check. fw_bundle: WARNING: Dell r630 iDRAC8/Life Cycle Controller - iDRAC Information, iDRAC Firmware Information, Firmware Version: Mismatch; Expected: '2.70.70.70', Found: '2.75.75.75' fw_bundle: WARNING: Dell r630 BIOS - BIOS Information, BIOS Firmware Information, Version: Mismatch; Expected: '2.11.0', Found: '2.9.1'. Continue to Step 6. 6. If you need to re-apply the f/w update, run the following command: ./fw_install.sh If a server reboot is required, the system will reboot. 7. Exit the rootsh session. 8. Exit the SSH terminal session. 9. Repeat Step 1 through Step 8 for the server node acting as primary. Xcellis Workflow Director Release Notes 30 Known Issues If this does not fix the StorNext Connect issue, contact Quantum Support for assistance. 80099 Workaround: Potential StorNext Connect issues after you upgrade StorNext Do the following to stop and restart StorNext Connect. Log in to the CLI of node 2 ONLY, since StorNext Connect does not run on node 1: 1. Open an SSH connection to the appropriate server and use the IP address assigned to the node on the Management or LAN Client network, or use the Service Port IP address. Service Port IP addresses: l Node 1 : 10.17.21.1 (dual-server node systems) l Node 2 : 10.17.21.2 (dual-server node, or "HA-ready" single-server node systems) Note: Node 2 is the server node sold with single-node (non-HA) Xcellis Workflow Director and Artico systems. It is also used for installation using the StorNext Connect Install app, for both single-node and dual-node systems only. 2. Initiate an ssh session to the system using Terminal or PuTTY: To ssh into the system a. Log in to the command line using the following credentials: l User name: stornext l Password: <stornext user account password> Note: "password" is the default password for the stornext user account. If the password has been changed, use the current password. Beginning with StorNext 7.0.2, you must change the default password for the stornext user account. As of StorNext 7.0.2, the first time you log in, you will be prompted to change the password to a different one. b. Enter sudo rootsh to gain root user access. c. Enter the password for the stornext user account again. 3. From the CLI of node 2, stop StorNext Connect. Enter: /opt/quantum/connect/bin/connect stop 4. From the CLI of node 2, start StorNext Connect. Enter: Xcellis Workflow Director Release Notes 31 Known Issues /opt/quantum/connect/bin/connect start 5. Exit the rootsh session. 6. Exit the SSH terminal session. If this does not fix the StorNext Connect issue, contact Quantum Support for assistance. 74202 StorNext services can fail to stop completely when NAS is Configured and StorNext services are stopped How might this be seen? There are two basic scenarios where this might be exposed: Scenario # 1 When StorNext stops, it signals NAS to vacate the StorNext file systems that NAS is using. However, if these file systems remain available for too long, the Appliance Controller will attempt to automatically restart NAS services. This is what happens, in order: 1. Restarting NAS services can resume use of StorNext resources. 2. Resuming StorNext resources interferes with attempts to stop StorNext. 3. Continued use of these StorNext resources can result in mounted StorNext file systems that do not have a running fsm process which blocks access to the StorNext file system. If experience this on your system, temporarily stop NAS services: 1. Log in to the command line of the server (as "sudo rootsh"): Launch the Command Line With an SSH Utility a. Open an SSH connection to the appropriate server and use the IP address assigned to the node on the Management/LAN Client network. a. Log in to the command line using the following credentials: l User name: stornext l Password: <stornext user account password> Note: "password" is the default password for the stornext user account. If the password has been changed, use the current password. Beginning with StorNext 7.0.2, you must change the default password for the stornext user account. As of StorNext 7.0.2, the first time you log in, you will be prompted to change the password to a different one. b. Enter sudo rootsh to gain root user access. c. Enter the password for the stornext user account again. Xcellis Workflow Director Release Notes 32 Known Issues 2. Stop NAS by executing the following command: /usr/cvfs/lib/snnas_control stop 3. Stop the Appliance Controller by executing the following command: /usr/local/quantum/bin/sml_service_tool stop snnas_controller 4. When you have finished Restart NAS and the Appliance Controller: a. Start NAS by executing the following command: /usr/cvfs/lib/snnas_control start b. Start the Appliance Controller by executing the following command: /usr/local/quantum/bin/sml_service_tool start snnas_controller Scenario # 2 If you need to stop the system during a maintenance window. This is an extension of Scenario #1, but NAS must vacate the file systems for an extended period of time. If NAS services are resumed when they should be suspended, those service processes may interfere with maintenance operations. To affect both scenarios, timers exist that you can adjust to extend the amount of time required between the stornext stop operation and before NAS services resume. The timers are controlled by the following Controller Registry values: l nas.heartbeat.check_state_secs l stornext_service.stop_period To see what values are currently assigned, enter: su sysadmin -c 'reg show nas.heartbeat.check_state_secs' to display the setting of the frequency interval of the NAS heartbeat state check, or enter: su sysadmin -c 'reg show stornext_service.stop_period' Xcellis Workflow Director Release Notes 33 Known Issues to display the duration that StorNext services are stopped. Note: By default, both timers are set to 120 (in seconds=2 minutes). Workarounds Workaround #1 If StorNext fails to stop due to NAS resource usage, do the following: 1. Log in to the command line of the server: Launch the Command Line With an SSH Utility a. Open an SSH connection to the appropriate server and use the IP address assigned to the node on the Management/LAN Client network. a. Log in to the command line using the following credentials: l User name: stornext l Password: <stornext user account password> Note: "password" is the default password for the stornext user account. If the password has been changed, use the current password. Beginning with StorNext 7.0.2, you must change the default password for the stornext user account. As of StorNext 7.0.2, the first time you log in, you will be prompted to change the password to a different one. b. Enter sudo rootsh to gain root user access. c. Enter the password for the stornext user account again. 2. Verify that the StorNext file systems are mounted: grep cvfs /proc/mounts If any StorNext file systems are not mounted, mount them now. 3. Mount the HA shared file system: mount /usr/adic/HAM/shared 4. Start fsm for each StorNext file system (shown below as "<FSNAME>") mounted on the server node: cvadmin -e "start <FSNAME> on localhost" Xcellis Workflow Director Release Notes 34 Known Issues 5. Stop StorNext services: For CentOS7 systems, enter: systemctl stop cvfs For CentOS6 systems, enter: service cvfs stop 6. To stop NAS, enter: /usr/cvfs/lib/snnas_control stop 7. To stop the Appliance Controller, enter: /usr/local/quantum/bin/sml_service_tool stop snnas_controller When you are ready, restart the Appliance Controller and NAS services: 8. To restart the Appliance Controller, enter: /usr/local/quantum/bin/sml_service_tool start snnas_controller 9. To restart NAS, enter: /usr/cvfs/lib/snnas_control start Workaround #2 For Scenario #1, Quantum recommends that you extend the time period to a value of 10 minutes (600 seconds) for both variables. Set a value that exceeds the amount of time necessary for typical StorNext shutdown. To set new values: Xcellis Workflow Director Release Notes 35 Known Issues 1. Log in to the command line: Launch the Command Line With an SSH Utility a. Open an SSH connection to the appropriate server and use the IP address assigned to the node on the Management/LAN Client network. a. Log in to the command line using the following credentials: l User name: stornext l Password: <stornext user account password> Note: "password" is the default password for the stornext user account. If the password has been changed, use the current password. Beginning with StorNext 7.0.2, you must change the default password for the stornext user account. As of StorNext 7.0.2, the first time you log in, you will be prompted to change the password to a different one. b. Enter sudo rootsh to gain root user access. c. Enter the password for the stornext user account again. 2. Change the frequency interval of the NAS heartbeat state check to 600 seconds (10 minutes). Enter: su sysadmin -c 'reg set nas.heartbeat.check_state_secs 600' Note: This is run with a temporary log in to the Appliance Controller as the sysadmin user. 3. Change the duration that StorNext services are stopped to 600 seconds (10 minutes). Enter: su sysadmin -c 'reg set stornext_service.stop_period 600' 4. Note: This is run with a temporary log in to the Appliance Controller as the sysadmin user. Workaround #3 For Scenario #2, to eliminate the confusion of setting a long duration for a maintenance window, and then having to change the values back again to a shorter value again, you can simply stop NAS services and the Appliance Controller, and then restart these services when you are finished. To stop the services and restart them: Xcellis Workflow Director Release Notes 36 Known Issues 1. Log in to the command line: Launch the Command Line With an SSH Utility a. Open an SSH connection to the appropriate server and use the IP address assigned to the node on the Management/LAN Client network. a. Log in to the command line using the following credentials: l User name: stornext l Password: <stornext user account password> Note: "password" is the default password for the stornext user account. If the password has been changed, use the current password. Beginning with StorNext 7.0.2, you must change the default password for the stornext user account. As of StorNext 7.0.2, the first time you log in, you will be prompted to change the password to a different one. b. Enter sudo rootsh to gain root user access. c. Enter the password for the stornext user account again. 2. Stop NAS by executing the following command: /usr/cvfs/lib/snnas_control stop 3. Stop the Appliance Controller by executing the following command: /usr/local/quantum/bin/sml_service_tool stop snnas_controller When you are ready, restart the Appliance Controller and NAS services: 4. To restart the Appliance Controller, enter: /usr/local/quantum/bin/sml_service_tool start snnas_controller 5. To restart NAS, enter: /usr/cvfs/lib/snnas_control start 6. Change the settings for the NAS heartbeat state check and the duration that StorNext services are stopped according to Workaround #2 on page 35. Workaround #4 Xcellis Workflow Director Release Notes 37 Known Issues An alternate method for maintenance windows, instead of implementing workaround #3 for Scenario #2, you can choose a much longer value if you need the NAS heartbeat state check interval and StorNext services stopped for a long period of time (for example, during a planned maintenance window in a data center). While this is another option, the downside of this is that you will need to know how much downtime to expect maintenance to take, and then set these times to be less than what is needed for that maintenance. It is also difficult to extend the maintenance period reliably once those timers have started. In addition, you will most likely have to reset the values back to their original settings when the maintenance window is complete, which could be a hassle. Here is one example which extends the time values to 2 hours (7,200 seconds): 1. Log in to the command line: Launch the Command Line With an SSH Utility a. Open an SSH connection to the appropriate server and use the IP address assigned to the node on the Management/LAN Client network. a. Log in to the command line using the following credentials: l User name: stornext l Password: <stornext user account password> Note: "password" is the default password for the stornext user account. If the password has been changed, use the current password. Beginning with StorNext 7.0.2, you must change the default password for the stornext user account. As of StorNext 7.0.2, the first time you log in, you will be prompted to change the password to a different one. b. Enter sudo rootsh to gain root user access. c. Enter the password for the stornext user account again. 2. Change the frequency interval of the NAS heartbeat state check to 7,200 seconds (10 minutes). Enter: su sysadmin -c 'reg set nas.heartbeat.check_state_secs 7200' Note: This is run with a temporary log in to the Appliance Controller as the sysadmin user. 3. Change the duration that StorNext services are stopped to 7,200 seconds (10 minutes). Enter: su sysadmin -c 'reg set stornext_service.stop_period 7200' 4. Note: This is run with a temporary log in to the Appliance Controller as the sysadmin user. Xcellis Workflow Director Release Notes 38 Known Issues journalctl Filter Script Step 1: Upgrade to StorNext 6.0.5 Note: StorNext 6.0.5 provides the script, so you need to upgrade to StorNext 6.0.5 to access the file. See Upgrade a Gateway System (Upgrade Firmware) Using the Service Menu. Step 2: Log in to the System Command Line 1. Open an SSH connection to the appropriate server and use the IP address assigned to the node on the Management or LAN Client network, or use the Service Port IP address. Service Port IP addresses: l Node 1 : 10.17.21.1 (dual-server node systems) l Node 2 : 10.17.21.2 (dual-server node, or "HA-ready" single-server node systems) Note: Node 2 is the server node sold with single-node (non-HA) Xcellis Workflow Director and Artico systems. It is also used for installation using the StorNext Connect Install app, for both single-node and dual-node systems only. 2. Initiate an ssh session to the system using Terminal or PuTTY: To ssh into the system a. Log in to the command line using the following credentials: l User name: stornext l Password: <stornext user account password> Note: "password" is the default password for the stornext user account. If the password has been changed, use the current password. Beginning with StorNext 7.0.2, you must change the default password for the stornext user account. As of StorNext 7.0.2, the first time you log in, you will be prompted to change the password to a different one. b. Enter sudo rootsh to gain root user access. c. Enter the password for the stornext user account again. 3. Continue to Step 3: Run the Journal Filter Script and View the Script Help below. Step 3: Run the Journal Filter Script and View the Script Help l Enter the following to use the script to view the log output in a way that filters out all the rootsh commands: /opt/DXi/scripts/journalctl_filter.sh -f Xcellis Workflow Director Release Notes 39 Known Issues l Enter the following to view the script's help file: /opt/DXi/scripts/journalctl_filter.sh --help Note: The journalctl_filter.sh output can also be saved to a file. Restart the Appliance Controller On the server node hosting NAS, do the following (use node 2 on dual-server node systems): 1. Open an SSH connection to the appropriate server node and use the IP address assigned to the node on the Management or LAN Client network. 1. Log in to the command line using the following credentials: l User name: stornext l Password: <stornext user account password> Note: "password" is the default password for the stornext user account. If the password has been changed, use the current password. Beginning with StorNext 7.0.2, you must change the default password for the stornext user account. As of StorNext 7.0.2, the first time you log in, you will be prompted to change the password to a different one. 2. Enter sudo rootsh to gain root user access. 3. Enter the password for the stornext user account again. 4. Enter the following: chown -R ldap:ldap /var/lib/ldap 5. Enter the following : systemctl restart slapd 6. Restart the appliance controller: systemctl start snnas_controller systemctl stop snnas_controller Xcellis Workflow Director Release Notes 40 Known Issues How to Disable NFS v4 To disable NFSv4 on Xcellis Workflow Director systems, especially those systems running NAS 1.2.0 or earlier, perform the following on node 2: Edit the nfs File 1. Open an SSH connection to the appropriate server and use the IP address assigned to the node on the Management or LAN Client network, or use the Service Port IP address. Service Port IP addresses: l Node 1 : 10.17.21.1 (dual-server node systems) l Node 2 : 10.17.21.2 (dual-server node, or "HA-ready" single-server node systems) Note: Node 2 is the server node sold with single-node (non-HA) Xcellis Workflow Director and Artico systems. It is also used for installation using the StorNext Connect Install app, for both single-node and dual-node systems only. 2. Initiate an ssh session to the system using Terminal or PuTTY: To ssh into the system a. Log in to the command line using the following credentials: l User name: stornext l Password: <stornext user account password> Note: "password" is the default password for the stornext user account. If the password has been changed, use the current password. Beginning with StorNext 7.0.2, you must change the default password for the stornext user account. As of StorNext 7.0.2, the first time you log in, you will be prompted to change the password to a different one. b. Enter sudo rootsh to gain root user access. c. Enter the password for the stornext user account again. 3. Edit /etc/sysconfig/nfs file. (See Example: Use vi to Edit the nfs File on the next page) 4. Change the value for RPCNFSDARGS to "-N 4". When finished, the line must be: RPCNFSDARGS="-N 4" 5. Change the value for RPCMOUNTDOPTS to "-N 4". When finished the line must be: RPCMOUNTDOPTS="-N 4" 6. Save the file. Xcellis Workflow Director Release Notes 41 Known Issues Restart NFS For Xcellis Workflow Director (R630) systems. 1. Enter the following to restart the NFS configuration.: systemctl restart nfs-config 2. Enter the following to restart the NFS server.: systemctl restart nfs-server After You Restart NFS on Node 2 Repeat both the Edit the nfs File on the previous page and Known Issues on page 11 sections on node 1( for dual-node systems). If you need to create new NFS shares to export for user access, you may do this now. See the About the NAS App section of the StorNext Connect Documentation Center for information about NAS configuration using StorNext Connect. Example: Use vi to Edit the nfs File 1. Enter the following: vi /etc/sysconfig/nfs 2. Move the cursor to the closing quotation mark in RPCNFSDARGS. 3. Enter the following: i -N 4 4. Write the file and quit vi as follows: :wq Xcellis Workflow Director Release Notes 42 Known Issues 5. For this example, you would have to Restart NFS on the previous page, and repeat the Edit the nfs File on page 41, and Restart NFS on the previous page again on node 1 (for dual-node systems). 6. Close the SSH session for the server(s) ( for dual-node systems). Re-enable DDM on the Secondary Node After HA Failover Once the MDC node acting as secondary finishes rebooting and becomes functional again, use fsddmconfig (or the GUI) from the server node currently acting as primary to re-enable DDM for the standby server node, as follows: 1. Open an SSH connection to the appropriate server and use the IP address assigned to the node on the Management or LAN Client network, or use the Service Port IP address. Service Port IP addresses: l Node 1 : 10.17.21.1 (dual-server node systems) l Node 2 : 10.17.21.2 (dual-server node, or "HA-ready" single-server node systems) Note: Node 2 is the server node sold with single-node (non-HA) Xcellis Workflow Director and Artico systems. It is also used for installation using the StorNext Connect Install app, for both single-node and dual-node systems only. 2. Initiate an ssh session to the system using Terminal or PuTTY: To ssh into the system a. Log in to the command line using the following credentials: l User name: stornext l Password: <stornext user account password> Note: "password" is the default password for the stornext user account. If the password has been changed, use the current password. Beginning with StorNext 7.0.2, you must change the default password for the stornext user account. As of StorNext 7.0.2, the first time you log in, you will be prompted to change the password to a different one. b. Enter sudo rootsh to gain root user access. c. Enter the password for the stornext user account again. 3. On the command line of the system enter the following: fsddmconfig -u -s e standby_system_hostname Xcellis Workflow Director Release Notes 43 Quantum Appliance Licenses If a system running DDMs periodically displays an Admin Alert when it fails over, cycles a client node, or upgrades while the server node operating as secondary is rebooting but not completely down, change the timeout value to allow more time to communicate with the node. Update the TSM configuration parameter DDM_CLIENT_RETRY_TIMEOUT from the default 30 seconds to a larger value depending on how long the node is taking to reboot. In the event the server node acting as secondary will be down for an extended period of time, the node should be taken offline. Additionally, if this parameter is set too high, and the standby server does not come back, the command that is currently running (e.g., store or retrieve) will not return until after the specified timeout. For more information about the DDM_CLIENT_RETRY_TIMEOUT parameter that can be placed into the fs_sysparm_override configuration file, refer to the /usr/adic/TSM/config/fs_ sysparm.README file. Caution: Incorrect modification of the fs_sysparm_override configuration file can cause a serious, adverse effect on StorNext functionality. Before modifying this file, we recommend you contact Contacting Quantum below. . Quantum Appliance Licenses See Quantum Appliance Licenses page on quantum.com. Contacting Quantum For further assistance, contact the Quantum Customer Support Center: Region North America EMEA Asia Pacific For worldwide support: https://www.quantum.com/en/company/contact-us/ Support Contact 1-800-284-5101 (toll free) +1-720-249-5700 +800-7826-8888 (toll free) +49 6131 324 185 +800-7826-8887 (toll free) +603-7953-3010 Xcellis Workflow Director Release Notes 44madbuild