On the ACM UI, the following error is seen:
In the server.log on ACM, the following errors is seen:
(/usr/local/dataprotection/var/configmgr/server_data/logs/server.log)
2019-11-13 18:11:55,413 INFO [pool-6-thread-7]-util.SSHUtil: Remote command using SSH execution status: Host : [10.x.x.x] User : [sysadmin] Password : [********] Command : [ifgroup add dataProtectionGrp interface 10.x.x.x client *] STATUS : [37]
2019-11-13 18:11:55,413 INFO [pool-6-thread-7]-util.SSHUtil: STDOUT : [Added interface "10.x.x.x" to ifgroup "dataProtectionGrp".]
2019-11-13 18:11:55,413 INFO [pool-6-thread-7]-util.SSHUtil: STDERR : [
**** Failed add client "*" to ifgroup "dataProtectionGrp": **** Error communicating with management service.]
2019-11-13 18:11:55,413 ERROR [pool-6-thread-7]-util.SSHUtil: Failed to executed remote command using SSH.
2019-11-13 18:11:55,413 INFO [pool-6-thread-7]-ddadapter.ConfigDataDomainTask: Failed to execute: ifgroup add dataProtectionGrp interface 10.x.x.x client *
2019-11-13 18:11:55,413 ERROR [pool-6-thread-7]-ddadapter.ConfigDataDomainTask: ApplianceException occurred while executing Datadomain config task.
com.emc.vcedpa.common.exception.ApplianceException: Failed to add interface.
at com.emc.vcedpa.ddadapter.ConfigDataDomainTask.addInterface(ConfigDataDomainTask.java:1010)
at com.emc.vcedpa.ddadapter.ConfigDataDomainTask.configureDD(ConfigDataDomainTask.java:399)
at com.emc.vcedpa.ddadapter.ConfigDataDomainTask.run(ConfigDataDomainTask.java:1590)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Caused by: com.emc.vcedpa.common.exception.ApplianceException: Failed to add interface.
at com.emc.vcedpa.ddadapter.ConfigDataDomainTask.addInterface(ConfigDataDomainTask.java:1007)
... 5 more
2019-11-13 18:11:55,413 INFO [pool-6-thread-7]-abstracts.ProductPlugin: Received notifyStatus from task : DATA_DOMAIN:CONFIG:DATA_DOMAIN_SERVER:0:FAILED:11:45%:1:0
The management services on the data domain (Protection Storage) were not fully up and functional when the workflow issued a command to add Data Domain data interfaces to "dataProtectionGrp" which caused the failure. This command should be manually attempted on Data Domain to confirm if it works to find the root cause for the failure.
If the command works on Data Domain, this appears to be a timing issue.
- Log in to the Data Domain system as 'sysadmin' user.
Note: The password on Data Domain system at this time should be "changeme".
Accept the configuration messages and say no to prompts to finish the config. If the Data Domain prompts to change password on the first log in, then it can be changed, however do not FORGET to revert it back to "changeme" before hitting "RETRY" to avoid issues with cleanup on Data Domain.
- Run the following command to check the network configuration on Data Domain:
net show settings
route show gateway
- Verify All Data Domain Interfaces can ping the Default gateway configured:
net ping <default_gateway_ip_address> interface EthV0
net ping <default_gateway_ip_address> interface EthV1
net ping <default_gateway_ip_address> interface EthV2
- Verify the DDBoost ifgroup configuration by issuing the following command:
ddboost ifgroup show config all
- Issue the ifgroup command ACM workflow issued which caused the Deployment to fail. This will test whether this was a timing issue due to management services not being up:
ifgroup add dataProtectionGrp interface x.x.x.x client *
If the above command works this time, it confirms this is a timing issue as the management services would have been down at the time when ACM issued this command. Hence, it is safe to rollback/retry and Retry the configuration.
Example:
sysadmin@abc.com# ifgroup add dataProtectionGrp interface x.x.x.x client *
Added interface "x.x.x.x" to ifgroup "dataProtectionGrp".
Added client "*" to ifgroup "dataProtectionGrp"
- Log in to Data Domain bash mode and revert the password back to "changeme". On bash mode, run the following command:
passwd sysadmin
- Hit 'Retry' button on ACM UI. Retry the configuration and monitor the progress.
NOTE: If any of the above steps show failures, those failures must be investigated accordingly before proceeding with the deployment again.