Release Notes StorNext Management Suite 2.4.1 SNMS Server Operating Systems: SGI IRIX 6.5.19f, 22f and 6.5.19m, 22m and 23m Solaris 8 and 9 SPARC (64-bit) Red Hat Enterprise Linux Advanced Server 3.0 (32-bit) Update 2 SNMS Client and StorNext FS Server Client Operating Systems: SGI IRIX 6.5.19f, 22f and 6.5.19m, 22m and 23m Solaris 8 and 9 SPARC (64-bit) Red Hat Enterprise Linux Advanced Server (32- and 64-bit) Update 2 SuSE Linux 8.1 (Enterprise Edition) IBM AIX 5.
Contents Page Topic 2 Purpose of this Release 3 Special Configuration Requirements 4 Using StorNext with Xsan 5 Certified System Components 6 System Requirements 7 Operating System Level Requirements 9 Upgrade Instructions 14 Known Issues 17 Resolved Issues 20 Limitations 23 Documentation Note • StorNext Management Suite (SNMS) is composed of the StorNext Storage Manager (StorNext SM) and the StorNext File System (StorNext FS).
• Support for HP MSL tape library • Support for HP EVA 3000 Disk Array with HP SecurePath failover • Support for HP MSA 1000 Disk Array with HP SecurePath failover • Support for EMC Clariion CX Series failover for dual-controller configuration • Support for STK 9840C tape drive Special Configuration Requirements The following libraries require special configurations to run SNMS or StorNext FS. Note StorNext 2.4.
Using StorNext with Xsan StorNext is interoperable with the Apple Xsan application. If you are testing a heterogeneous mix of Apple Xsan and ADIC StorNext clients, the Xsan build must be 7N125 or greater. For information on supported hardware environments when running Xsan, refer to the Apple Xsan documentation. To attach an Xsan client to a StorNext FS server, perform these special configuration steps on the Xsan client. 1 Install the Xsan application. The machine reboots. 2 Open a terminal window.
Certified System Components This table lists certified system components that support SNMS 2.4.1. Component Description Browsers Netscape 4.7x, 4.8x, 7.0 Microsoft Internet Explorer 5.5 and later HBA Emulex LP8000, LP850, LP9000, LP90002 QLogic: QLA2200, QLA2310, QLA2340, QLA2342 FC Router ADIC FCR 250, SNC 3000, SNC 5100 FC Switch Brocade 2x00 and Brocade 3x00 McData Cisco MDS 9000 Libraries ADIC Scalar 100, 1000, 10K, i2000, S24 AMU v3.10E2 AML/2, E, J ACSLS version 6.0.1, version 6.
System Requirements To successfully install SNMS 2.4.1, the requirements listed in the following tables must be met. StorNext FS Requirements For each StorNext FS mount, these requirements must be met. System/Component Requirement AIX StorNext FS clients: A minimum of 128 MB of RAM is required. IRIX StorNext FS clients: A minimum of 128 MB of RAM is required. Solaris StorNext FS clients: A minimum of 128 MB of RAM is required. Linux StorNext FS clients: A minimum of 128 MB of RAM is required.
StorNext Storage Manager Requirements Note StorNext SM only runs on SGI IRIX, Red Hat Linux, and Sun Solaris operating systems. System/Component Browser settings Requirement Reload the StorNext GUI pages. Perform these steps to enable the page reload. • In Netscape, click: Edit > Preferences > Advanced > Cache. Select Every Time and click OK. • In Internet Explorer, click: Tools > Internet Options > General > Settings > General. Under Settings, select Every visit to the page and click OK.
StorNext FS Requirements Server Platform Operating System Levels AIX 5.2 (64-bit) IRIX 6.5.19, 22f and 6.5.19, 22 and 23m Solaris Solaris 8 and 9 Red Hat Linux Uniprocessor or Multiprocessor, Red Hat Enterprise Linux Advanced Server 3.0, Update 2, kernel levels 2.4.21-15.0.x.EL and 2.4.21-15.0.x.ELsmp. To build a loadable kernel module, both the kernel and kernel source RPM packages must be installed.
Upgrade Instructions This section describes the following upgrades: • Upgrading to SNMS 2.4.1 • Upgrading to StorNext FS 2.4.1 • Upgrading SNMS from Red Hat Linux 8.0 to Red Hat Enterprise Linux Advanced Server 3.0 on page 10 • Upgrading SNMS on IRIX on page 13 Upgrading to SNMS 2.4.1 Use the following instructions to upgrade to SNMS 2.4.1. 1 Mount the SNMS 2.4.1 installation CD for the machine’s platform. 2 Upgrade the SNMS software. Type: inst.
• For Solaris, type: pkgrm ADICcvfs • For Linux, type: rpm -qa|grep cvfs-client cvfs-client_ rpm -ea cvfs-client_ rpm -qa|grep cvfs-server cvfs-server_ rpm -ea cvfs-server_ • For Windows click: Start > Settings > Control Panel > Add/Remove Programs and select StorNext File System. 4 Install the upgrade version of StorNext FS.
4 Mount the backup media. a. From the StorNext Storage Manager (SNSM) Home Page, click Media > Library > Mount. This action enables media to mount without requiring an operator to manually open the library and place backup media in the drive. b. Record the drive alias where the media is mounted. 5 Record the serial number of the drive where the backup media is mounted. This information is used during the restore process (after RHEL is installed).
Post-Upgrade Tasks After upgrading to RHEL, use this procedure to complete post-upgrade tasks. 1 Reconnect all disconnected internal disks. 2 Mount the SNMS 2.4.1 installation CD and install the SNMS software. Type: inst.StorNext 3 Add SNMS environment settings to the shell. Type: . /usr/adic/.profile - or source /usr/adic/.cshrc 4 Verify that all tape drives, archives, and disks are visible.
Upgrading SNMS on IRIX For instructions on upgrading an IRIX machine to SNMS 2.4.1, contact ATAC. After upgrading to SNMS 2.4.1, you must perform the following post-upgrade task to turn off mediaid. If you upgraded StorNext on a machine running IRIX (all supported versions), use this procedure to turn off mediad for any StorNext-managed storage device. 1 Log on as root. Type: su root 2 Edit the mediad.config file. Type: vi /etc/config/mediad.
Known Issues This table lists known issues in this release of StorNext. Operating System CR Number Service Request Number AIX 33986 N/A Description During a StorNext upgrade, if you encounter a DSM failure that resembles the following output: SNFS UPGRADE 2.4.1(48) Status 1) Upgrade Complete 2) Upgrade Complete 3) Upgrade Complete 4) Upgrade Failed 2.4.1(48) perl 2.4.1(48) GUI Workaround Reboot the machine and repeat the upgrade process.
Operating System CR Number Service Request Number Linux 34383 N/A Description FSM may panic and deleting files is difficult, after system reaches 100% capacity. Workaround 1 Add the following line (temporarily) to the configuration file: MaxMBPerClientReserve 0 2 Restart FSM and verify that files can be removed to free enough space to continue operations. 3 Remove files. 4 Remove the line added in Step 1 from the configuration file. 5 Restart the FSM.
Operating System CR Number Service Request Number Windows 34699 N/A Description File system does not automatically mount after a reboot due to GetByHostName failure. Workaround Do one of the following: • Add the server name to the etc\hosts file on the Windows client. - or • Type the IP address of the machine in the fsnameservers tab instead of the machine name.
Operating System CR Number Service Request Number All 34571 N/A Displayed quotas are different than requested quotas. N/A 34720 N/A Breaking an Ethernet connection causes a disconnect that invalidates locks (file locking). N/A 34875 N/A All SNMS components must be stopped and restarted after a disaster recovery audit is run. N/A 35235 N/A Dual Aisle: The Media Storage Manager logs a memory allocation error when mounts are cancelled.
Operating System CR Number Service Request Number Windows 15635 N/A StorNext FS errors when mapping a drive on Windows. 31013 N/A A daemon exception error was experienced on a Windows 2000 client. 31952 N/A The call to PnVerifyWindowsCompatable() is failing with an VOP_EINVAL error. I18N support on Windows is non-functional. 33646 N/A Getting a exception on W2K client going to a Linux server when running iozone. 33954 N/A 2.
Operating System CR Number Service Request Number All 31977 N/A After a file has been deleted, the SNSM File Recover page returns an "undefined" status rather than the filename. 32150 N/A The drive mount state is not updated for media that is missing from physical libraries during audits. 32239 N/A When using the GUI, network-attached libraries display incorrect information in the Library Configuration window.
Limitations This table lists the limitations that have been discovered in this release of SNMS. Operating System/ Component Affected IRIX Description StorNext FS uses 64-bit inode numbers. Programs compiled without 64-bit support may experience problems working with files with inode numbers greater than 2 GB. This issue is not unique to StorNext, but may be encountered by some legacy applications when working with StorNext FS.
Operating System/ Component Affected Linux Description StorNext FS is shipped as separate, installable versions for the Uniprocessor (up) and Multiprocessor (smp) Linux kernel versions. You need to select the correct kernel version of StorNext FS. Otherwise you will encounter problems during installation and while running the product. Use the uname -v command to determine the running version of Linux. The version includes the string smp for multi-processor kernels.
Operating System/ Component Affected Solaris Description StorNext FS only supports 64-bit inodes for installations of the software on Solaris 8. (CR 8208). For LUNs there is a maximum limit of 850 GB. Recommendation: To maximize support across all platforms, set LUNs to be no greater than 850 GB when you are using Solaris 8 or 9. On Solaris, by default, the /usr/lib/fs/nfs/nfsfind script is run nightly by the cron daemon.
Operating System/ Component Affected All Description Hot re-zoning of SAN fabrics is not supported. StorNext is incompatible with CXFS. StorNext File System is incompatible with third-party portmappers. The SNMS GUI does not support an isolated metadata network topology with a system configured for HA failover. If the browser does not have connectivity to the isolated metadata network, then it will fail to connect after a failover event.
September 2004, ADIC