IBM Support

Readme and Release notes for release 5.0.0.0 IBM Spectrum Scale 5.0.0.0 Spectrum_Scale_Standard-5.0.0.0-ppc64LE-Linux Readme

Fix Readme


Abstract

xxx

Content

Readme file for: Spectrum Scale
Product/Component Release: 5.0.0.0
Update Name: Spectrum_Scale_Standard-5.0.0.0-ppc64LE-Linux
Fix ID: Spectrum_Scale_Standard-5.0.0.0-ppc64LE-Linux
Publication Date: 15 December 2017
Last modified date: 15 December 2017

Installation information

Download location

Below is a list of components, platforms, and file names that apply to this Readme file.

Fix Download for Linux

Product/Component Name: Platform: Fix:
IBM Spectrum Scale Linux PPC64LE RHEL
Linux PPC64LE SLES
Linux PPC64LE Ubuntu
Spectrum_Scale_Standard-5.0.0.0-ppc64LE-Linux

Prerequisites and co-requisites

  • - Prerequisites

    You may use this 5.0.0.0 package to perform a First Time Install or to upgrade from an existing 4.2.0.0 - 4.2.3.6 (If upgrading node by node ) or 3.5.0 - 4.2.3.6 (If you shutdown and upgrade the entire cluster).

Known issues

  • - Problems discovered in IBM Spectrum Scale releases

    None.

Installation information

  • - Downloading Images

    Choose the download option "Download using Download Director" to download the new Spectrum Scale package and place it in any location desired on the install node.
    Note, if you must (not recommended) use download option "Download using your browser (HTTPS)", instead of clicking on the down arrow to the left of the package name, you must right-click on the package name and select the Save Link As.. option. If you just click on the download arrow, the browser will likely hang.

  • - Installing IBM Spectrum Scale update for Linux on Power Little Endian Systems

    After you have downloaded the IBM Spectrum Scale 5.0.0.0 update, follow the steps below to install the fix package:

    1. Ensure the package is executable using ls -l command.

      You should see something similar with permissions like:
           -rwx r--r-- l root root 110885866 Apr 27 15:52 /download_dir/package_name.

      If it's not executable, you can always make the package executable using the following command:
           chmod +x /download_dir/package_name
    2. Extract RPMs and Debian Linux Packages from Self Extracting Package downloaded using following commands:

      For Standard Edition:

      ./Spectrum_Scale_Standard-5.0.0.0-ppc64LE-Linux-install

      For Advanced Edition:

      ./Spectrum_Scale_Advanced-5.0.0.0-ppc64LE-Linux-install

      For Data Management Edition:

      ./Spectrum_Scale_Data_Management-5.0.0.0-ppc64LE-Linux-install

      Optional Package for SLES and RedHat Enterprise Linux:

      • gpfs.docs-5.0.0.0.noarch.rpm
      • gpfs.gss.pmcollector-5.0.0.0.xxx.*.rpm (where xxx is the OS version)
      • gpfs.gss.pmsensors-5.0.0.0.xxx.*.rpm (where xxx is the OS version)
      • gpfs.gui-5.0.0.0.noarch.rpm
      • gpfs.java-5.0.0.0.*.rpm
      • gpfs.callhome-5.0.0.0.xxx.noarch.rpm (where xxx is the OS type)
      • gpfs.callhome-ecc-client-5.0.0.0.noarch.rpm
      • gpfs.kafka-5.0.0-0.*.rpm (x86_64 only)
      • gpfs.librdkafka-5.0.0-0.*.rpm (x86_64 only)
      • gpfs.hdfs-protocol-2.7.3-1.*.rpm (x86_64, ppc64, and ppc64le only)
      • gpfs.tct.client-1.1.4.*.rpm (IBM Spectrum Scale Advanced or Data Management Edition only, x86_64 and ppc64le only)
      • gpfs.tct.server-1.1.4.*.rpm (IBM Spectrum Scale Advanced or Data Management Edition only, x86_64 and ppc64le only)

      Optional Package for Ubuntu Linux:

      • gpfs.docs_5.0.0.0_all.deb
      • gpfs.gui_5.0.0.0_all.deb
      • gpfs.java_5.0.0.0_*.deb
      • gpfs.callhome_5.0.0.0.000_all.deb (x86_64 only)
      • gpfs.callhome-ecc-client_5.0.0.0.000_all.deb (x86_64 only)
      • gpfs.kafka_5.0.0-0_*.deb (x86_64 only)
      • gpfs.librdkafka_5.0.0-0_*.deb (x86_64 only)
      • gpfs.gss.pmcollector_5.0.0.0.xxx_*.deb (where xxx is the OS version)
      • gpfs.gss.pmsensors_5.0.0.0.xxx_*.deb (where xxx is the OS version)
      • gpfs.tct.client-1.1.4.*.deb (IBM Spectrum Scale Advanced or Data Management Edition only, x86_64 only)
    3. Follow the installation and migration instructions in your IBM Spectrum Scale Installing and upgrading.
  • - Upgrading GPFS nodes

    In the below instructions, node-by-node upgrade cannot be used to migrate from GPFS 4.1 or prior releases. For example, upgrading from 4.1.1.16 to 5.0.0.0 requires complete cluster shutdown, upgrade install on all nodes and then cluster startup.

    Upgrading GPFS may be accomplished by either upgrading one node in the cluster at a time or by upgrading all nodes in the cluster at once. When upgrading GPFS one node at a time, the below steps are performed on each node in the cluster in a sequential manner. When upgrading the entire cluster at once, GPFS must be shutdown on all nodes in the cluster prior to upgrading.

    When upgrading nodes one at a time, you may need to plan the order of nodes to upgrade. Verify that stopping each particular machine does not cause quorum to be lost or that an NSD server might be the last server for some disks. Upgrade the quorum and manager nodes first. When upgrading the quorum nodes, upgrade the cluster manager last to avoid unnecessary cluster failover and election of new cluster managers.

    1. Prior to upgrading GPFS on a node, all applications that depend on GPFS (e.g. DB2) must be stopped. Any GPFS file systems that are NFS exported must be unexported prior to unmounting GPFS file systems.
    2. Stop GPFS on the node. Verify that the GPFS daemon has terminated and that the kernel extensions have been unloaded (mmfsenv -u). If the command mmfsenv -u reports that it cannot unload the kernel extensions because they are "busy", then the install can proceed, but the node must be rebooted after the install. By "busy" this means that some process has a "current directory" in some GPFS filesystem directory or has an open file descriptor. The freeware program lsof can identify the process and the process can then be killed. Retry mmfsenv -u and if that succeeds then a reboot of the node can be avoided.
    3. Upgrade GPFS as follows(make sure to be in the same directory as the files):

      1. For Linux:

        For SLES or RedHat Enterprise Linux:

        rpm -Fvh gpfs*.rpm
        rpm -ivh gpfs.license.*.rpm (if you are updating from 4.2.1.2 or older version)
        rpm -ivh gpfs.compression.*.rpm

        For Debian and Ubuntu Linux:

        dpkg -i gpfs*.deb

        Recompile any GPFS portability layer modules you may have previously compiled. For more information, reference: Building the GPFS portability layer on Linux nodes




      2. For AIX:
        Use the 'inutoc .' command to create a .toc file which will be used by the installp command. The .toc file will be created in the current working directory.
        Once the .toc file is created, Upgrade GPFS using the installp command or via SMIT on the node. If you are in the same directory as the install packages and the .toc file, an example command might be:

        installp -agXYd . gpfs

Additional information

  • - Notices
  • - Package information

    The images listed below and contained in the Self Extracting Package (SE-Package) are maintenance packages for IBM Spectrum Scale. The images are a mix of normal RPM or DEB images that can be directly applied to your system.

    The packages can be used for new install or update from a prior level of IBM Spectrum Scale.

    After all RPMs or DEBs are installed, you have successfully updated your IBM Spectrum Scale product.

    Before installing IBM Spectrum Scale, it is necessary to verify that you have the correct levels of the prerequisite software installed on each node in the cluster. If the correct level of prerequisite software is not installed, see the appropriate installation manual before proceeding with your IBM Spectrum Scale installation.

    For the most up-to-date list of prerequisite software, see the IBM Spectrum Scale FAQ in the IBM® Knowledge Center .

    Update to Version:

    5.0.0.0

    Update from Version:

    4.2.0.0 - 4.2.3.6 (If upgrading node by node )
    3.5.0 - 4.2.3.6 (If you shutdown and upgrade the entire cluster)

    SE Package Content (SLES and RHEL Linux):

    • gpfs.msg.en_US-5.0.0.0.noarch.rpm
    • gpfs.base-5.0.0.0.*.rpm
    • gpfs.gpl-5.0.0.0.noarch.rpm
    • gpfs.docs-5.0.0.0.noarch.rpm
    • gpfs.ext-5.0.0.0.*.rpm
    • gpfs.compression-5.0.0.0.*.rpm
    • gpfs.gskit-8.0.50-79.*.rpm
    • gpfs.gui-5.0.0.0.noarch.rpm
    • gpfs.hdfs-protocol-2.7.3-1.*.rpm (x86_64, ppc64, and ppc64le only)
    • gpfs.java-5.0.0.0.*.rpm
    • gpfs.license.xxx-5.0.0.0.*.rpm (where xxx is the license type)
    • gpfs.callhome-5.0.0.0.000.xxx.noarch.rpm (where xxx is the OS type)
    • gpfs.callhome-ecc-client-5.0.0.0.000.noarch.rpm
    • gpfs.gss.pmcollector-5.0.0.0.xxx.*.rpm (where xxx is the OS type)
    • gpfs.gss.pmsensors-5.0.0.0.xxx.*.rpm (where xxx is the OS type)
    • gpfs.kafka-5.0.0-0.*.rpm (x86_64 only)
    • gpfs.librdkafka-5.0.0-0.*.rpm (x86_64 only)
    • gpfs.adv-5.0.0.0.*.rpm (IBM Spectrum Scale Advanced or Data Management Edition only)
    • gpfs.crypto-5.0.0.0.*.rpm (IBM Spectrum Scale Advanced or Data Management Edition only)
    • gpfs.tct.client-1.1.4.*.rpm (IBM Spectrum Scale Advanced or Data Management Edition only, x86_64 and ppc64le only)
    • gpfs.tct.server-1.1.4.*.rpm (IBM Spectrum Scale Advanced or Data Management Edition only, x86_64 and ppc64le only)

    SE Package Content (Ubunut Linux):

    • gpfs.msg.en_us-5.0.0.0_all.deb
    • gpfs.base-5.0.0.0_*.deb
    • gpfs.gpl-5.0.0.0_all.deb
    • gpfs.docs-5.0.0.0_all.deb
    • gpfs.ext-5.0.0.0_*.deb
    • gpfs.compression-5.0.0.0_*.deb
    • gpfs.gskit_8.0.50-79.*.deb
    • gpfs.gui_5.0.0.0_all.deb
    • gpfs.java_5.0.0.0_*.deb
    • gpfs.kafka_5.0.0-0_*.deb (x86_64 only)
    • gpfs.librdkafka_5.0.0-0_*.deb (x86_64 only)
    • gpfs.license.xxx_5.0.0.0_*.deb (where xxx is the license type)
    • gpfs.gss.pmcollector_5.0.0.0.xxx_*.deb (where xxx is the license type)
    • gpfs.gss.pmsensors_5.0.0.0.xxx_*.deb (where xxx is the license type)
    • gpfs.adv_5.0.0.0_*.deb (IBM Spectrum Scale Advanced or Data Management Edition only)
    • gpfs.tct.client-1.1.4.*.deb (IBM Spectrum Scale Advanced or Data Management Edition only, x86_64 only)
  • - Summary of changes for IBM Spectrum Scale

    Unless specifically noted otherwise, this history of problems fixed for IBM Spectrum Scale 5.0.x applies for all supported platforms.

    Changes to the IBM Spectrum Scale 5.0.0.0 include the following:

    • Added DMPs for TIP events
              A topic is added listing the directed maintenance procedures for TIP events.         The DMPs help users resolve issues caused due to TIP events. 
    • AFM and AFM DR
              - Compression and snapshot ILM policy supported.        - A general recommendation added for the Gateway node.        - Configuration parameters added - afmMaxParallelRecoveries, afmAsyncOpWaitTimeout,             afmSyncOpWaitTimeout, and afmRevalOpWaitTimeout.        - Configuration parameters modified - afmRPO and afmHashVersion. 
    • Authentication: Authentication packages
              Updated the authentication page to include packages specific to Ubuntu. 
    • Authentication: AD-based authentication
              New information is added on NFS with server-side group         lookup and Active Directory authentication. 
    • Authentication: Primary group selection configurable for AD + RFC2307 based authentication
              Ability to choose primary group as set in "UNIX attributes" of a user on         Active Directory introduced with AD + RFC2307 based authentication scheme.        Earlier, Windows primary group was by default selected as the primary group. 
    • Big data and analytics
              - The GPFS Ambari integration package is now called the IBM Spectrum           Scale Ambari management pack (in short, management pack or MPack).        - IBM Spectrum Scale Ambari management pack version 2.4.2.1 with           HDFS Transparency version 2.7.3.1 supports BI 4.2/BI 4.2.5 IOP migration           to HDP 2.6.2.        - Supports the remote mount configuration in Ambari.        - Supports the multiple file systems configuration. In management           pack version 2.4.2.1, the current limit is two file systems.        - The Short circuit write is supported for better performance.        - In HDFS Transparency, the Ranger performance is enhanced. 
    • Changes to IBM Spectrum Scale management API
          Added the following new commands:          GET /perfmon/data         GET /filesystems/{filesystemName}/afm/state        DELETE /nodes/{name}        POST /nodes        GET /nodeclasses        POST /nodeclasses        DELETE /nodeclasses/{nodeclassName}        GET /nodeclasses/{nodeclassName}        PUT /nodeclasses/{nodeclassName}        DELETE /jobs/jobId        POST /filesystems/{filesystemName}/filesets/{filesetName}/psnaps         DELETE /filesystems/{filesystemName}/filesets/{filesetName}/psnaps/{snapshotName}        GET /thresholds        GET /thresholds/{name}        POST /thresholds        DELETE /thresholds/{name} 
    • IBM Spectrum Scale GUI changes
            - Added new Networks page to monitor the performance, configuration, and        adapters of network configurations in the cluster. You can monitor the       network performance with respect to the IP and RDMA interfaces used in the configuration.     - Added new Monitoring > Thresholds page to create and monitor the threshold rules        that are defined in the system.     - Added Access > Remote Connections page to enable the GUI node of the       local cluster to monitor the remote cluster by establishing a connection       with the GUI node of the remote cluster.      - Added Settings > Call Home page to configure call home. Configuring       the call home feature helps the IBM® Support to monitor the system.       Configuring call home also helps to reduce the response time of the        IBM Support to resolve any issues.       The diagnostic data that is downloaded through the Settings > Diagnostic Data        can be uploaded to a problem management record (PMR) by using       the call home feature in the backend. To upload the diagnostic data, right-click       the relevant data set from the Previously Collected Diagnostic Data, and        select Upload to PMR.     - Added file system creation capabilities in GUI. Use the Files > File Systems > Create File System       option to launch the Create File System wizard. In the Create File System wizard, you can specify       the following details of the file system:          - File system name          - Storage pools          - NSDs for the file systems          - Failure groups          - NSD order for data writes          - Maximum number of Spectrum Scale clients          - Maximum number of inodes of the root fileset          - Whether to enable quota and scope for the quota definition          - Whether to enable DMAPI          - Mount point and automatic mount mode     - Added the aggregation levels Access Point and Filesets and removed Account       for the resource type Transparent Cloud Tiering in the Monitoring > Statisitics page.     - The Files > Transparent Cloud Tiering page now displays the file systems        and filesets that are mapped with the cloud service. It also shows the       connection of such a container pair configuration to a cloud account and       the corresponding CSAP that is configured for the cloud account.     - Changes to capacity monitoring in the GUI          - Moved the Capacity page from Monitoring to Files menu in the navigation            and renamed the GUI page to User Capacity.           - Only the file data user capacity can be viewed from the Files > User Capacity page.            Removed the pools, filesets, file system capacity monitoring options from the Files > User Capacity page.            You can monitor the capacity of these components from the respective GUI pages.          - Replaced the GPFSPoolCap sensor with the GPFSPool sensor and separate data and metadata            level capacity monitoring are introduced in the performance charts available in the             Files > File Systems and Storage > Pools pages.           - New GPFSPool-based data and metadata performance monitoring metrics are available            for selection in the Files > Statistics > Edit > Capacity section.            You need to select the aggregation level as Pool to view these metrics.     - AFM monitoring changes in the GUI          - Provides the number of AFM filesets and the corresponding export server maps.            Each export map establishes a mapping between the gateway node and the NFS            host name to allow parallel data transfers from cache to home.          - By using the Request Access option available in the Files > Active File Management             or Access > Remote Connection page in the GUI, you can now establish connection with remote clusters.            After establishing the connection, you can monitor the following AFM and AFM DR            configuration details across clusters:               * On home and secondary, you can see the AFM relationships configuration,                  health status, and performance values of the Cache and Disaster Recovery grids.               * On the Overview tab of the detailed view, the available home and secondary inodes are available.               * On the Overview tab of the detailed view, the details such as NFS throughput,                  IOPs, and latency details are available, if the protocol is NFS.     - New option to create AFM peer snapshots through GUI. Use the Create Peer Snapshot option       in the Files > Snapshots page to create peer snapshots. You can view and delete these peer snapshots from       the Snapshots page and also from the detailed view of the Files > Active File Management page. 
    • Encryption: GSKit V8 improves cryptographic performance on IBM POWER8
          The IBM Global Security Kit (GSKit) Version 8 and later improves cryptographic performance     on IBM POWER8 hardware. The version of GSKit that is shipped with IBM Spectrum Scale v5.0.0    offers better performance on POWER8, compared with the versions shipped with earlier releases. 
    • File compression: The lz4 library provides fast access to compressed data
          File compression supports the lz4 compression library. Lz4 is intended primarily for active data and    favors read-access speed over maximized space saving.   
    • File data: Block and subblock sizes improve I/O performance and reduce fragmentation
          The default block size is larger, 4 MiB instead of 256 KiB, and the sizes of subblocks relative to blocks    s are smaller, for example, 8 KiB subblocks in a 4 MiB block. A larger block size improves the     file system performance and a smaller subblock size reduces the amount of unused space. For many business    applications, the default value of 4 MiB provides the best balance of improved performance    and reduced fragmentation. 
    • File encryption: AES-XTS encryption is faster on x86 in non-FIPS mode
           On x86 architecture in non-FIPS mode, file encryption with the AES algorithm in XTS mode     is faster than it was. 
    • File systems: File system rebalancing is faster
           Rebalancing is implemented by a lenient round-robin method that typically runs faster than the     previously used method of strict round robin. The strict round robin method is available as an option. 
    • installation toolkit changes
           - The installation toolkit has added support for the installation and the deployment        of IBM Spectrum Scale in a cluster containing Elastic Storage Server (ESS).      - The installation toolkit has added support for enabling and configuring call home.     - The installation toolkit has added support for enabling and configuring file audit logging.     - The installation toolkit has added support for the installation and the       deployment of IBM Spectrum Scale on Ubuntu 16.04 LTS nodes.     - The installation toolkit has added verification of passwordless SSH during       prechecks before installation, deployment, or upgrade.     - The installation toolkit has added support for cumulative object upgrade. 
    • mmafmctl command
           The --outband parameter is deprecated. 
    • mmcallhome command: Enhancements
           - Addition of -Y option         * The -Y displays the command output in a parseable format with a colon (:) as a field delimiter.      - Addition of --pmr option         * The --pmr option allows you to upload data to existing PMRs using the           mmcallhome run SendFile command. 
    • mmchconfig command: Enhancements
           - Encrypted files can be copied into an LROC device            * With the lrocEnableStoringClearText attribute, you can control whether file           data from encrypted files, which is held in memory as cleartext, is           copied into a local read-only cache (LROC) device.     - InfiniBand addresses can be specified for RDMA transfers         * In the verbsPorts attribute, you can specify InfiniBand addresses           for RDMA transfers between an NSD client and server. 
    • mmchnsd command: Change NSDs without unmounting the file system
           When you add or remove NSDs or do other operations with mmchnsd,      you do not need to unmount the file system. 
    • mmcrfs command: Enhancements
            - The default data block size is 4 MiB with an 8 KiB subblock size          * If no block size is specified, a file system is created with a 4 MiB block size and an            8 KiB subblock size. The minimum release level (minReleaseLevel) of the            cluster must be 5.0.0 or greater when the file system is created.       - The default log file size depends on block size and metadata size          * If the block size is 512 KiB or larger and the metadata block size 256 KiB or larger,            then the default log file size is 32 MiB. Otherwise, the default log file            size is 4 MiB or the metadata block size, whichever is larger.      - The default method for updating atime is relatime          * If the minimum release level (minReleaseLevel) of the cluster is 5.0.0 or greater            when the file system is created, the default method for updating atime is relatime. 
    • mmdsh command: Several options are no longer supported
            The --ignoreSignal, -I, and -d options are no longer supported.       Do not use these options unless instructed to by IBM support personnel. 
    • mmfsck command: Display an interim status report at any time
            While a long-running instance of mmfsck is in progress, you can start another instance      of mmfsck with the --status-report parameter to display current      status information from all the nodes that are participating in the mmfsck run. 
    • mmgetstate command: Display the unresponsive state
            The command returns the unresponsive state when the GPFS      daemon is running but is not responding. 
    • mmhealth command: Addition to measurement options
            Measurement options for filesystem, SMB node, and NFS node      has been added to the mmhealth command.  
    • mmkeyserv command: The simplified method supports certificate chains from a certificate authority.
            In the simplified method, with the --kmip-cert parameter, you can set up encryption with IBM®      Security Key Lifecycle Manager (SKLM) as the key management server and with a certificate signed      by a certificate authority (CA) on the KMIP port of the SKLM server. 
    • mmnetverify command: Enhancements
            - Verify the network operation of nodes in a subnet          * With the --subnets parameters, you can specify the subnet             addresses of the nodes that you want to verify.      - Verify that nodes can handle a new MTU size          * With the ping-packet-size parameter, you can specify the size            of the ICMP echo request packets that are sent between local node and the target            node during the ping test. 
    • mmtracectl command: Display the tracing status
            The --status parameter displays the tracing status of the specified nodes. 
    • New feature for threshold monitoring
             Starting from IBM Spectrum Scale version 5.0.0, if multiple thresholds rules       have overlapping entities for the same metrics, only one of the concurrent rules is       made actively eligible. 
    • NFS: Dynamic export changes
             You can dynamically change the export configuration without restarting the NFS service. 
    • Object
             - Support for Ubuntu       - Support for sudo wrapper for Object on Ubuntu       - Support for cumulative upgrades from older versions       - Object snap enhancement to contain keystore logs 
    • Protocol support: Enhanced
             Protocol support is extended to Ubuntu 10.04 
    • Setting up a system for storing crash files for Ubuntu
             A topic is added to describe how to set up a system for storing crash files for Ubuntu. 
    • SMB: DFS redirects for SMB shares
             New option to configure DFS redirects for SMB shares. 
    • SMB: SMB server upgrade changes
             Two events on CTDB version match/mismatch are added to the RAS events. 
    • Sudo wrappers: Root-level processes can call administration commands directly
             Root-level background processes, such as cron and callback programs, can       successfully call administration commands directly rather than through sudo       when sudo wrappers are enabled. 
    • Supported clients for NFS
             A topic is added listing the clients that are supported by NFS protocol. 
    • Transparent cloud tiering
             - Support for multiple cloud storage accounts       - Support for multiple file systems or filesets per node group       - Enhanced support for large file systems provided by container spillover       - Support for associating file sets with containers for enhanced granularity       - Multiple URL and region support at the node level       - Support for creating a cloud service separately for tiering and sharing operations.       - Unique encryption key per cloud container       - Support for remotely mounted clients.       - Support for Amazon S3 regions requiring Sigv4 security support,          including the US government cloud region.       - Ability to enable or disable transparent recall for files for a given file         system instantly, without having to rewrite a policy.       - Support for backing up and restoring the Cloud services configuration in case of any disaster.        - Support for backing up the Cloud services database to the cloud.        - Support for restoring Transparent cloud tiering service on an identical backup cluster.        - Support for checking the integrity of the Cloud services         database after any system crash or outage.       - Support for auditing events relating to each operation performed in Cloud services.    
    • New commands
              mmaudit mmmsgqueue 
    • Changed commands
             mmafmctl mmadddisk mmcallhome mmchattr mmchcluster mmchconfig mmchfs mmchnsd       mmcloudgateway mmcrcluster mmcrfs mmdeldisk mmdsh mmfsck mmgetstate       mmkeyserv mmnetverify mmnfs mmrestripefile mmrestripefs mmsmb mmtracectl       mmuserauth 
    • Deleted commands
             mmrest 
    • New messages
             6027-1264, 6027-1757, 6027-2394, 6027-2395, 6027-2396, 6027-2397       6027-2398, 6027-2399, 6027-2400, 6027-2401, 6027-3259, 6027-3408       6027-3597, 6027-3598, 6027-3599, 6027-3600, 6027-3601, 6027-3602       6027-3603, 6027-3604, 6027-3730, 6027-3921, 6027-3922, 6027-3923       6027-3924, 6027-3925, 6027-3926, 6027-3927, 6027-3928       6027-3929, 6027-3930, 6027-3931, 6027-4019 
    • Changed messages
             6027-928 

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"STXKQY","label":"IBM Spectrum Scale"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"","Edition":"","Line of Business":{"code":"LOB26","label":"Storage"}}]

Document Information

Modified date:
16 February 2018

UID

isg400003647