Veritas InfoScale™ Operations Manager 8.0.2 Release Notes

Last Published:
Product(s): InfoScale & Storage Foundation (8.0.2)
Platform: AIX,HP-UX,Linux,Solaris,VMware ESX,Windows
  1. Overview of this release
    1.  
      About Veritas InfoScale Operations Manager
    2. New features and changes in Veritas InfoScale Operations Manager 8.0.2
      1.  
        Enhancement in configuring replication
    3.  
      Issues fixed in the Veritas InfoScale Operations Manager 8.0.2 release
  2. System requirements
    1.  
      Operating system requirements
    2. Third-party required libraries
      1.  
        32-bit SNIA Common HBA API required on Windows hosts
    3. System resource requirements
      1.  
        About space estimation for data logs
      2.  
        About the frequency of managed host, enclosure and switch information discovery
    4.  
      Supported hardware
    5.  
      Web browser requirements
    6. Network and firewall requirements
      1.  
        Internet Protocol version requirements
    7.  
      About the consumption of the managed host components
  3. Software limitations
    1.  
      Veritas InfoScale Operations Manager 8.0.2 managed host not supported on AIX in Network Installation Manager
    2.  
      Veritas InfoScale Operations Manager 8.0.2 does not support HA Plugin functionality
    3.  
      Control host add-on is not compatible with the Windows platform (4119171)
    4.  
      No coexistence of managed host and CommandCentral Storage Management Server
    5.  
      Volume layout not discovered for LDM-managed volumes mounted without a drive letter
    6.  
      Backup and restore limitations in Veritas InfoScale Operations Manager 8.0.2
    7.  
      Veritas InfoScale Operations Manager does not support the discovery of LDoms and Zones together on the same host
    8.  
      Deployment-related limitations
    9.  
      Windows Management Server high availability configuration limitations
    10.  
      Solaris Zones virtualization support limitations
    11.  
      Discovery limitations for virtualization support
    12.  
      VCS configuration check reports violations only if at least one node in the cluster is running Cluster Server
    13.  
      Limitations related to the correlation between the disks and the disk groups
    14.  
      CIFS shares from NetApp and Celerra arrays that are mapped to a Windows host are not discovered
    15.  
      Limitations on SF operations on Windows CVM cluster
    16.  
      Add host operation fails for RHEL 7.x managed hosts
    17.  
      ESX servers not able to access an RDM disk associated with a shared datastore might cause failed discovery of RDM disk by Veritas InfoScale Operations Manager
    18.  
      Sometimes Internet Explorer displays a security warning when you navigate between pages in the console
    19.  
      Cannot configure an EMC CLARiiON enclosure on a Windows control host using a security file
    20.  
      Veritas InfoScale Operations Manager does not validate if the cluster node is managed by the Management Server during the VBS start operation
  4. Known issues
    1. Management Server issues
      1.  
        Browser may experience crashes when performing tasks using the Veritas InfoScale Operations Manager GUI (4118252)
      2.  
        Single Sign-On does not work with FIPS-enabled VIOM CMS (4040700)
      3.  
        When a Policy Signature Scan is run on a Linux system, the Policy Signature Scan task fails (4043408)
      4.  
        Web service API fails with FIPS-enabled VIOM CMS (4040990)
      5.  
        Service group may go into faulted state when the SFM_Services service group fails over to slave node (4004244)
      6.  
        VIOM CMS upgrade fails while upgrading from version 7.3.1 or 7.3.1 with an appropriate patch to 7.4.2 (4002920)
      7.  
        The database services, authentication services, and the web server fail to start when the VIOM CMS server is rebooted on SLES 15 SP1 (4002789)
      8.  
        Availability perspective does not show correct nodes for a Linux cluster (3932149)
      9.  
        Manual upgrade of a VRTS package fails if publisher is set to Symantec (3869503)
      10.  
        Delayed discovery of VMware VirtualCenter server by Control Hosts in Veritas InfoScale Operations Manager (2342314)
      11.  
        Authentication broker crashes while performing LDAP authentication (2017319)
      12.  
        XPRTLD daemon fails when Veritas InfoScale Operations Manager starts because of the corrupt AT pem files in the VRTSsfmh package (2145925)
      13.  
        Uninstalling Management Server removes the managed host package from a Storage Foundation for Windows host
      14.  
        Veritas InfoScale Operations Manager displays stale application status (2564572)
      15.  
        Manual refresh of HMC Server and VMware vCenter Server required after migration of virtual machines (2605533)
      16.  
        Performance metering of a VMware ESX server may not work properly after failover (2814844)
      17.  
        For VMware virtual machine, the virtual storage correlation is not functional if a SCSI controller of non-default type is used (3056561)
      18.  
        Erroneous managed host status reported in Veritas InfoScale Operations Manager high availability (HA) environment (2780631)
      19.  
        Information on running tasks is accurate only for managed hosts 6.0 and later (3077899)
      20.  
        Managed hosts previous to version 5.x are not listed for storage provisioning and volume migration
      21.  
        Veritas InfoScale Operations Manager does not discover virtual machines with same BIOS GUID on a Hyper-V Server (3509138)
      22.  
        Disk information for the cluster does not display correct data for host (3532746)
      23.  
        Disk correlation does not happen for LDOM storage container after enabling MPxIO on the SAN disks (3370824)
      24.  
        Qualsys scan may at times fail for port 5634 (2903776)
      25.  
        Remote switch operation fails because of group operator privileges (3899833)
      26.  
        Adding managed host version 7.0 to VIOM 7.3 CS fails (3902108)
      27.  
        Service group status is not displayed correctly (3915580)
      28.  
        Windows: Unable to set up or reconfigure CMS HA (3916993)
    2. Managed host issues
      1.  
        Quick I/O cache value is not enabled after performing the storage provisioning operation on AIX managed hosts (2131183)
      2.  
        Unable to view performance graphs for VxVM disk and volume on Windows platform (3054870)
      3.  
        Incorrect statistics returned by DMP if Storage Foundation version is prior to 5.0 MP3 (2796418)
      4.  
        Create disk group operation fails when triggered from slave node in a clustered configuration (3196104)
      5.  
        Network File System on Solaris cannot be discovered if the Fully Qualified Host Name is used in vfstab file but not used for mounting the file system (2747735)
      6.  
        Bandwidth tab displays incorrect data for a UNIX host (3484788)
      7.  
        CVR operations may not work correctly in case of managed host versions lower than 7.0(3745404)
      8.  
        Management Server console displays incorrect version for ApplicationHA guests (3873640)
      9.  
        Unable to add older managed hosts to freshly installed Management Server 7.0 or higher
      10.  
        Management Server console displays incorrect version for ApplicationHA guests (3873640)
      11.  
        Unable to complete 'add secondary' workflow in some cases (3874690)
      12.  
        VRTSsfmh 7.1 and VxVM 7.0 co-existence issue on AIX (3870438)
      13.  
        Windows CS: Unable to configure arrays discovered through SSH (3915564)
      14.  
        Unable to upgrade AIX MH from 7.2 to 7.3 or higher through VIOM GUI (3914690)
      15.  
        hbaapp binary core dumps while discovering QEMU disks (3932120)
      16.  
        Unable to add secondary node to RVG on RHEL 7.x (3903111)
      17.  
        Unable to configure 3PAR array using Windows MH
    3. Storage Insight Add-on issues
      1.  
        After the first discovery of IBM SVC array, manual refresh of putty cache may be required (3114164)
      2.  
        For locally replicated EMC Symmetrix LUNs, last synchronization time is available only for SYMCLI version 7.4 or later (3249430)
      3.  
        Manual discovery of Symmetrix enclosure is required when SYMCLI version is upgraded on the Storage Insight add-on discovery host (3289628)
      4.  
        Performance metering of enclosures may not work properly after failover (2814844)
      5.  
        Information on FAST managed storage groups for EMC Symmetrix VMAX enclosures is not discovered periodically (2842124)
      6.  
        Password file option does not work while configuring HP EVA enclosures on Windows hosts (2757601)
      7.  
        EMC Celerra enclosure details are not discovered for users with read-only access rights, and Imported Administrator or Operator role
      8.  
        Tier information is not displayed for some devices in a FAST managed storage group (2795204)
      9.  
        IBM System Storage DS enclosure discovery is not supported through HiCommand Server 7 in Veritas InfoScale Operations Manager (2708346)
      10.  
        Shares discovery not happening properly for NetApp cDOT (3932671)
    4. Virtual Business Service issues
      1.  
        Virtual Business Service start operation does not validate the service group's resource criticality (2169223)
      2.  
        Virtual Business Services (VBS) does not discover cluster(s) and service group(s) (3913474)
    5. Storage Insight SDK Add-on issues
      1.  
        Edit and Test operations on Storage Insight Plug-in are not supported using Internet Explorer on 64-bit Windows hosts (2826079)
      2.  
        Storage Insight Plug-in upload operation sometimes fails on Internet Explorer Web browser (3485662)
    6. Fabric Insight Add-on issues
      1.  
        SAN switch discovery fails when Veritas InfoScale Operations Manager Management Server, configured in high availability mode, is used as a discovery host (3513295)
    7. Application Migration Add-on issues
      1.  
        Application migration plan execution fails if the web server goes down
      2.  
        Error displayed during executing vxlist utility (3870438)
      3.  
        DiskGroup or CVMVolDg type resources may not be displayed in the Target Disk Information panel
      4.  
        Recurrent failure of either the Setup Storage operation during mirror creation or Rehearse/Migrate operation during mirror detach
      5.  
        Unable to install the Application Migration add-on on slave node (3915236)
    8. Other issues
      1.  
        Duplicate entries for the disks that are part of a virtual machine (2481982)
      2.  
        Unable to configure Management Server with a user name in Russian language using Firefox browser
      3.  
        Resource attributes not discovered for RVGPrimary Resource
      4.  
        Discovery of VMware VirtualCenter server or ESX server is not case - sensitive (2567318)
      5.  
        Offline instances not displayed in instance tab for MSSQL HA configuration (3516063)
      6.  
        Only one virtual machine configured as resource gets discovered (3488469)
      7.  
        A single host may have two entries on the host tab in certain conditions(3724295)
      8.  
        Incorrect virtual machine count in case of duplicate biosuuid (3782776)
      9.  
        Need to refresh the array for Datastore to NFS correlation
      10.  
        Applicable hosts pane disappears if you filter hot fixes by platform (3874690)
      11.  
        vxlicrep (license reporting) utility fails to execute if Microsoft Visual C++ 2010 x86 Runtime is not installed (3902028)
      12.  
        Creating ecoded volume not supported through Veritas InfoScale Operations Manager 8.0.2 GUI (3943301)
      13.  
        Service group state not showing properly in Veritas InfoScale Operations Manager for a single node cluster
      14.  
        Renaming volume not working (3945801)
      15.  
        Subdisks and Disks are not shown for shared volume in Linux (3946016)
      16.  
        Licensing information not discovered if only the SFMH package is upgraded
  5. Appendix A. Getting help
    1.  
      Veritas InfoScale Operations Manager on the Web
    2.  
      Getting help
    3.  
      Using the product documentation

XPRTLD daemon fails when Veritas InfoScale Operations Manager starts because of the corrupt AT pem files in the VRTSsfmh package (2145925)

The XPRTLD daemon fails when Veritas InfoScale Operations Manager starts, if the AT pem files (the certificate files in the VRTSsfmh package) are corrupt.

Workaround:

To repair the corrupt AT pem files on UNIX:

  1. Stop the XPRTLD daemon by using the following command:

    /opt/VRTSsfmh/adm/xprtldctrl stop

  2. Delete all the files in the directory /var/VRTSat_lhc/ by using the following command :

    #cd /var

    rm -rf /var/VRTSat_lhc/*

  3. Take a backup of the credentials in the /var/VRTSat/.VRTSat/profile/certstore/ directory, by using the following command:

    mv /var/VRTSat/.VRTSat/profile/certstore/*.0 /tmp/backupcreds/

  4. In the directory, delete the pem files by using the following commands:

    • rm /var/VRTSat/.VRTSat/profile/certstore/keystore/PubKeyFile.pem

    • rm /var/VRTSat/.VRTSat/profile/certstore/keystore/PrivKeyFile.pem

  5. Restart any running shared broker process by using the following command:

    /opt/VRTSat/bin/vxatd

  6. Authenticate the local host to create a self-signed certificate by using the following commands:

    export EAT_HOME_DIR=/opt/VRTSsfmh

    export EAT_DATA_DIR=/var/opt/VRTSsfmh/sec

    cd $EAT_HOME_DIR/bin

    ./vssat authenticate -d localhost

  7. Start the XPRTLD daemon by using the following command:

    /opt/VRTSsfmh/adm/xprtldctrl start

To repair the corrupt AT pem files on Windows:

  1. Stop the XPRTLD daemon by using the following command:

    net stop xprtld

  2. Delete all the files in the following directory:

    %ALLUSERSPROFILE%\Application Data\VERITAS\Security\Authentication\VRTSat_lhc

  3. Take a backup of the credential in the following directory:

    AT_PROFILE_DIR\certstore\* c:\temp\*

    You can get the AT Profile directory from the following locations:

    • For 64-bit Windows:

      HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\VERITAS\Security\Authentication\Credential Manager\Profiles\SYSTEM\ ProfileDir

    • For 32-bit Windows:

      HKEY_LOCAL_MACHINE\SOFTWARE\Veritas\Security\Authentication\Credential Manager\Profiles\SYSTEM\ProfileDir

  4. Delete the following pem files:

    • AT_PROFILE_DIR\certstore\keystore\PubKeyFile.pem

    • AT_PROFILE_DIR\certstore\keystore\PrivKeyFile.pem

  5. Restart any running shared broker process by using the following commands:

    • sc stop vrtsat

    • sc start vrtsat

  6. Authenticate the local host to create a self-signed certificate by using the following commands:

    set EAT_HOME_DIR=%PROGRAMFILES%\VERITAS\VRTSsfmh

    set EAT_DATA_DIR=%ALLUSERSPROFILE%\Symantec\VRTSsfmh\sec

    cd %EAT_HOME_DIR%\bin

    vssat authenticate -d localhost

  7. Start the XPRTLD daemon by using the following command:

    net start xprtld