Skip to Main Content
Integration


This is an IBM Automation portal for Integration products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.


Status Functionality already exists
Created by Guest
Created on Feb 21, 2024

Invalid credentials - suspended - for Distributed type.

Pretty sure some of you running into this problem in a midsize or larger ILMT environment where you might have hundreds of VMMan configurations defined (Local or Distributed).

For time to time, you might need to deal with this type of error below which can be very stressful. If VMMan configurations are defined as "Local", you could use the "Resume" button to reset this action on the same portal page. If VMMan configurations are defined as "Distributed" on a BES Relay server and you have more than 10 or 20 or etc...to go through the manual steps described below, it can stress you out very fast.

I have gone thru up to 50 to reset that setting manually, it took me very long time to complete as I needed to identify which .properties file name in question and manually reset that setting.

To development team, do you have plan to implement an automate solution similar to use the Resume button to reset this setting for the Distributed mode. It will save a lot of time?



======================


Invalid credentials - suspended

Connection to the VM manager is suspended because the number of failed login attempts was exceeded. The status is used to prevent the account from locking if invalid credentials were provided.

Action:

  • Ensure that the VM manager credentials are correct. Then, click Resume.

  • Go to vmmconf_*.properties file and make sure that the vmm_communication_locked parameter is set to false.

  • Check the connection between the VM Manager Tool and the VM manager. Make sure that the firewall, proxy and NAT settings are correct.

Idea priority High
  • Admin
    Tomasz Zeller
    Reply
    |
    Mar 29, 2024

    Our current design does not allow to comminicate from LMT server to distributed vm manager, so there is no possibility for LMT server to send an infrormation to selected ditributed/disconnected VM Manager to e.g. 'Resume' suspendedd credentials, but... if it is a problem for some cutomer that his VM Managers (ESX server/ Hyper-V host) have temporary authentication issues from time to time which are causing the 'Invalid credentials - suspended' to appear then it is possible to turn off this 'suspension' completely by changing the value of 'vmm_max_subsequent_login_failures' VM Manager tool setting to 0, according to this param description in config file:# If you set this parameter to 0, an unlimited number of attempts is allowed.


    # If the specified number of failed attempts is exceeded, the connection from the VM manager is locked


    # and the vmm_communication_locked parameter is set to 'true'.


    # Check the vmm_communication_locked parameter for further details.

  • Guest
    Reply
    |
    Feb 21, 2024

    If implemented please be aware that VM Manager with Distributed Typ can also be a disconneted VM Manager.