Symptoms:
FIPS is not configured correctly on the appliance. Click Enable or Disable to resolve it. If the problem persists, raise a technical support ticket.
root@###### [ /home/usagemeter ]# locale
LANG=ja_JP.utf8
LC_CTYPE="ja_JP.utf8"
LC_NUMERIC="ja_JP.utf8"
LC_TIME="ja_JP.utf8"
LC_COLLATE="ja_JP.utf8"
LC_MONETARY="ja_JP.utf8"
LC_MESSAGES="ja_JP.utf8"
LC_PAPER="ja_JP.utf8"
LC_NAME="ja_JP.utf8"
LC_ADDRESS="ja_JP.utf8"
LC_TELEPHONE="ja_JP.utf8"
LC_MEASUREMENT="ja_JP.utf8"
LC_IDENTIFICATION="ja_JP.utf8"
LC_ALL=
VCF Usage Meter 9.x
Changing locale causes the issue. Usage Meter does not support changing locale configuration. See more details in "Changing the locale is not supported in Usage Meter".
To workaround the issue, follow the steps below:
1. log in appliance via SSH as usagemeter
2. run following command and confirmed locale configuration is not default settings
locale
3. run following to disable FIPS mode (this command will reboot appliance automatically)
/opt/vmware/cloudusagemetering/scripts/fips-util.sh -fr off
4. log in appliance via SSH as usagemeter
5. backup get-keystore-type.sh file
cp /opt/vmware/cloudusagemetering/scripts/get-keystore-type.sh /opt/vmware/cloudusagemetering/scripts/get-keystore-type.sh.bak
6. vi get-keystore-type.sh and add "export LC_ALL=C" as below
get-keystore-type.sh
---------------------------------
provider="org.bouncycastle.jcajce.provider.BouncyCastleFipsProvider"
provider_details="-providerclass ${provider} -providerpath ${provider_path}"
export LC_ALL=C /* <<== add this line */
if
---------------------------------
7. save the file by :wq
8. run following command to enable FIPS mode (this command will reboot appliance automatically)
/opt/vmware/cloudusagemetering/scripts/fips-util.sh -fr on