IBM Support

IT39001: AFTER A TRIGGERED RECONFIGURATION THE VIRTUAL MACHINES CAN NO LONGER BE LISTED IN THE MMC

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • This issue occurs after IBM Spectrum Protect for
    Virtual Environments - Data Protection for Microsoft Hyper-V
    is installed and configured successfully and the data mover
    node password is changed.
    
    
    Starting the Data Protection for Microsoft Hyper-V Management
    Console (MMC) then immediately results in starting the
    configuration wizard. After all steps are completed
    successfully, the MMC is unable to display the list of
    available virtual machines.
    
    A "Verify Node" action can be started and results in:
    
    ANS2604S The Web client agent was unable to authenticate with
    the server.
    
    This is also logged in the file messages.log file in:
    %systemdrive%\IBM\SpectrumProtect\webserver\usr\servers\veProfi
    le\logs
    
    The data mover node error log shows:
    
    ANS1835E PASSWORDACCESS is GENERATE, but password needed for
    server 'IGSTSM52'.
    Either the password is not stored locally, or it was changed at
    the server.
    
    A data mover service trace will not provide further hints.
    But the server actlog will show messages like the following at
    the time the reconfiguration steps were taken:
    
    ANR2017I Administrator ADMIN issued command: SELECT DOMAIN_NAME
    FROM NODES WHERE NODE_NAME='NOENAME_HV_TGT'
    ANR2017I Administrator ADMIN issued command: SELECT DOMAIN_NAME
    FROM NODES WHERE NODE_NAME='NODENAME_HV_DM'
    ANR2017I Administrator ADMIN issued command: UPDATE NODE
    NOENAME_HV_DM ?***? forcep=y sessionsecurity=transitional
    ANR2063I Node NODENAME_HV_DM updated.
    ANR2017I Administrator ADMIN issued command: GRANT PROXYNODE
    target=NODENAME_HV_TGT agent=NODENAME_HV_DM
    ANR0145E GRANT PROXYNODE: failed.  Node NODENAME_HV_TGT already
    has been granted proxynode authority to node NODENAME_HV_DM.
    
    
    ======================
    Diagnostic steps:
    
    When starting the MMC and the configuration wizard is
    triggered, stop the remote agent service (dsmagent.exe) for the
    data mover node.
    This avoids running into the authentication issue.
    After completing the reconfiguration steps, the
    available virtual machines will be listed in the MMC.
    
    =======================
    Affected product versions:
    IBM Spectrum Protect for Virtual Environments
    - Data Protection for Microsoft Hyper-V versions 7.1 and 8.1
    on all supported Windows platforms
    
    
    =======================
    Additional Keywords:
    
    TS005061741 tsm hyperv tdpve mmc gui
    

Local fix

  • There are two ways to work around the issue:
    1)
    
    Update the data mover node password using an IBM Spectrum
    Protect server administrative interface, then using a
    backup-archive client user interface save the password on the
    client and update all configured services for the data mover
    node with its new password.
    2)
    When starting the MMC and the configuration wizard is
    triggered, stop the remote agent service (dsmagent.exe) for the
    data mover node.
    After completing the reconfiguration steps, the
    available virtual machines will be listed in the MMC.
    
    Repeat one of the two local fixes each time the issue occurs
    again.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * IBM Spectrum Protect for Virtual Environments component Data *
    * Protection for Microsoft Hyper-V 7.1.6, 7.1.8, 8.1.4, 8.1.6, *
    * 8.1.8, 8.1.9, 8.1.10, 8.1.11, 8.1.12 and 8.1.13 on the       *
    * Windows Server platform.                                     *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See ERROR DESCRIPTION.                                       *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * This issue is projected to be fixed in the IBM Spectrum      *
    * Protect Data Protection for Microsoft Hyper-V client 8.1.14  *
    * version on Windows platform.                                 *
    * Note that this is subject to change at the discretion of     *
    * IBM.                                                         *
    ****************************************************************
    

Problem conclusion

  • Data Protection for Microsoft Hyper-V Configuration Wizard can
    fail to authentificate with the Spectrum Protect server because
    of the old password   is used. The wizard was updated to use
    correct password.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT39001

  • Reported component name

    TSM VE DP MS HY

  • Reported component ID

    5725TVEHV

  • Reported release

    81W

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2021-11-08

  • Closed date

    2022-01-14

  • Last modified date

    2022-01-14

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Modules/Macros

  • DpHv.msc
    

Fix information

  • Fixed component name

    TSM VE DP MS HY

  • Fixed component ID

    5725TVEHV

Applicable component levels

[{"Line of Business":{"code":"LOB26","label":"Storage"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SS8TDQ","label":"Tivoli Storage Manager for Virtual Environments"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"81W"}]

Document Information

Modified date:
15 January 2022