Hi ILMT L3 Team, as you all aware that changing or resetting values in the vmmconf_xxxx.properties file is extremely painful.   Especially vmm_communication_locked setting which constantly changing to "true" value due to a number of reasons.  When manually resetting this value back to "false" in  vmmconf_xxxx.properties can be very challenging in a very large environment where there could be over 30+ vmmconf_xxxx .properties required to reset that value.  

Awhile back (over 3 years ago), I have opened an enhancement to have ability to change the vmmconf_.properties file especially for vmm_communication_locked via the ILMT web portal.   It should be very straight forward by selecting the vmman config in question and providing an option to change this setting or other settings.   Then it should find its way to update that particular vmmconf_.properties file for me.    

Can you someone look into this and what is the status of this ER opened awhile back?

Hello York,

Actually, there is an ability to change vmm_communication_locked property via the ILMT web portal...by means of 'Resume' button :
https://www.ibm.com/docs/en/license-metric-tool?topic=managers-vm-panel

I suppose that the way how it is documented is slightly misleading :
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.

The second step is unnecessary as clicking 'Resume' button will automatically change vmm_communication_locked parameter to false.

Hi ILMT L3 Team, as you all aware that changing or resetting values in the vmmconf_xxxx.properties file is extremely painful.   Especially vmm_communication_locked setting which constantly changing to "true" value due to a number of reasons.  When manually resetting this value back to "false" in  vmmconf_xxxx.properties can be very challenging in a very large environment where there could be over 30+ vmmconf_xxxx .properties required to reset that value.  

Awhile back (over 3 years ago), I have opened an enhancement to have ability to change the vmmconf_.properties file especially for vmm_communication_locked via the ILMT web portal.   It should be very straight forward by selecting the vmman config in question and providing an option to change this setting or other settings.   Then it should find its way to update that particular vmmconf_.properties file for me.    

Can you someone look into this and what is the status of this ER opened awhile back?

I will do a quick test if I find one.   However that option can only work (if it works) for Local and not for Distributed mode.    That is still an issue for Distributed mode vm manager.

Hello York,

Actually, there is an ability to change vmm_communication_locked property via the ILMT web portal...by means of 'Resume' button :
https://www.ibm.com/docs/en/license-metric-tool?topic=managers-vm-panel

I suppose that the way how it is documented is slightly misleading :
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.

The second step is unnecessary as clicking 'Resume' button will automatically change vmm_communication_locked parameter to false.

Hi ILMT L3 Team, as you all aware that changing or resetting values in the vmmconf_xxxx.properties file is extremely painful.   Especially vmm_communication_locked setting which constantly changing to "true" value due to a number of reasons.  When manually resetting this value back to "false" in  vmmconf_xxxx.properties can be very challenging in a very large environment where there could be over 30+ vmmconf_xxxx .properties required to reset that value.  

Awhile back (over 3 years ago), I have opened an enhancement to have ability to change the vmmconf_.properties file especially for vmm_communication_locked via the ILMT web portal.   It should be very straight forward by selecting the vmman config in question and providing an option to change this setting or other settings.   Then it should find its way to update that particular vmmconf_.properties file for me.    

Can you someone look into this and what is the status of this ER opened awhile back?

it works for Local and Central.
By design, there is no 'interaction' with VM managers configured in the distributed mode (read-only view).
Still, VM Manager Tool in distributed mode is not very popular so I would not count on any UI enhancements for that deployment type. 

I will do a quick test if I find one.   However that option can only work (if it works) for Local and not for Distributed mode.    That is still an issue for Distributed mode vm manager.

Hello York,

Actually, there is an ability to change vmm_communication_locked property via the ILMT web portal...by means of 'Resume' button :
https://www.ibm.com/docs/en/license-metric-tool?topic=managers-vm-panel

I suppose that the way how it is documented is slightly misleading :
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.

The second step is unnecessary as clicking 'Resume' button will automatically change vmm_communication_locked parameter to false.

Hi ILMT L3 Team, as you all aware that changing or resetting values in the vmmconf_xxxx.properties file is extremely painful.   Especially vmm_communication_locked setting which constantly changing to "true" value due to a number of reasons.  When manually resetting this value back to "false" in  vmmconf_xxxx.properties can be very challenging in a very large environment where there could be over 30+ vmmconf_xxxx .properties required to reset that value.  

Awhile back (over 3 years ago), I have opened an enhancement to have ability to change the vmmconf_.properties file especially for vmm_communication_locked via the ILMT web portal.   It should be very straight forward by selecting the vmman config in question and providing an option to change this setting or other settings.   Then it should find its way to update that particular vmmconf_.properties file for me.    

Can you someone look into this and what is the status of this ER opened awhile back?

Well, I tested the Resume bottom for the VM Manager Type "VMWare ESXi...." as shown below,  its vmmconf*.properties file did not get updated.   Also I executed the data import manually, it still did not update that setting.  

Please explain

# Indicates if a connection to the VM manager is locked.
# Unit: boolean (true/false)
# Default: false
# Comments:
# To disable the connection to the VM manager but keep the configuration file, set the parameter to 'true'.
# If the number of failed logging attempts is exceeded, the parameter is automatically set to 'true'. 
# To unlock the communication, and reset the count of subsequent logging errors, set the parameter to 'false'
# To set the maximum number of failed logging attempts, see the vmm_max_subsequent_login_failures parameter.
vmm_communication_locked=true

it works for Local and Central.
By design, there is no 'interaction' with VM managers configured in the distributed mode (read-only view).
Still, VM Manager Tool in distributed mode is not very popular so I would not count on any UI enhancements for that deployment type. 

I will do a quick test if I find one.   However that option can only work (if it works) for Local and not for Distributed mode.    That is still an issue for Distributed mode vm manager.

Hello York,

Actually, there is an ability to change vmm_communication_locked property via the ILMT web portal...by means of 'Resume' button :
https://www.ibm.com/docs/en/license-metric-tool?topic=managers-vm-panel

I suppose that the way how it is documented is slightly misleading :
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.

The second step is unnecessary as clicking 'Resume' button will automatically change vmm_communication_locked parameter to false.

Hi ILMT L3 Team, as you all aware that changing or resetting values in the vmmconf_xxxx.properties file is extremely painful.   Especially vmm_communication_locked setting which constantly changing to "true" value due to a number of reasons.  When manually resetting this value back to "false" in  vmmconf_xxxx.properties can be very challenging in a very large environment where there could be over 30+ vmmconf_xxxx .properties required to reset that value.  

Awhile back (over 3 years ago), I have opened an enhancement to have ability to change the vmmconf_.properties file especially for vmm_communication_locked via the ILMT web portal.   It should be very straight forward by selecting the vmman config in question and providing an option to change this setting or other settings.   Then it should find its way to update that particular vmmconf_.properties file for me.    

Can you someone look into this and what is the status of this ER opened awhile back?

Well, I don't think so...

What has probably happened is the vmm_communication_locked parameter got changed to false,
A subsequent connection test has failed, so, vmm_communication_locked parameter got changed to true once again.
Pls. keep in mind that the whole 'connection test' procedure takes couple of seconds...so, vmmconf*.properties file update is rather quick.
(the whole procedure been design to prevent the account from locking)

Data import has nothing to do with this...

If you want to take a closer look VM Manager Tool logs is the way to go...

Well, I tested the Resume bottom for the VM Manager Type "VMWare ESXi...." as shown below,  its vmmconf*.properties file did not get updated.   Also I executed the data import manually, it still did not update that setting.  

Please explain

# Indicates if a connection to the VM manager is locked.
# Unit: boolean (true/false)
# Default: false
# Comments:
# To disable the connection to the VM manager but keep the configuration file, set the parameter to 'true'.
# If the number of failed logging attempts is exceeded, the parameter is automatically set to 'true'. 
# To unlock the communication, and reset the count of subsequent logging errors, set the parameter to 'false'
# To set the maximum number of failed logging attempts, see the vmm_max_subsequent_login_failures parameter.
vmm_communication_locked=true

it works for Local and Central.
By design, there is no 'interaction' with VM managers configured in the distributed mode (read-only view).
Still, VM Manager Tool in distributed mode is not very popular so I would not count on any UI enhancements for that deployment type. 

I will do a quick test if I find one.   However that option can only work (if it works) for Local and not for Distributed mode.    That is still an issue for Distributed mode vm manager.

Hello York,

Actually, there is an ability to change vmm_communication_locked property via the ILMT web portal...by means of 'Resume' button :
https://www.ibm.com/docs/en/license-metric-tool?topic=managers-vm-panel

I suppose that the way how it is documented is slightly misleading :
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.

The second step is unnecessary as clicking 'Resume' button will automatically change vmm_communication_locked parameter to false.

Hi ILMT L3 Team, as you all aware that changing or resetting values in the vmmconf_xxxx.properties file is extremely painful.   Especially vmm_communication_locked setting which constantly changing to "true" value due to a number of reasons.  When manually resetting this value back to "false" in  vmmconf_xxxx.properties can be very challenging in a very large environment where there could be over 30+ vmmconf_xxxx .properties required to reset that value.  

Awhile back (over 3 years ago), I have opened an enhancement to have ability to change the vmmconf_.properties file especially for vmm_communication_locked via the ILMT web portal.   It should be very straight forward by selecting the vmman config in question and providing an option to change this setting or other settings.   Then it should find its way to update that particular vmmconf_.properties file for me.    

Can you someone look into this and what is the status of this ER opened awhile back?