Article Number: 540847

printer Print mail Email

RP4VM: Consistency Groups in Error state when nested ESX hosts are present

Summary: Consistency Groups in Error state when nested ESX hosts are present

Primary Product: RecoverPoint for Virtual Machines

Product: RecoverPoint for Virtual Machines 5.1 more...

Last Published: 21 Apr 2020

Article Type: Break Fix

Published Status: Online

Version: 3

RP4VM: Consistency Groups in Error state when nested ESX hosts are present

Article Content

Issue


VCUpdater is failing with Null pointer exception, which is causing all CGs to go into error state.


In connector logs:
2020-01-20 14:13:45,267 [pool-6-thread-1] (SplitterUtils.java:66) INFO - ESX has null hostKernelModuleSystem: <HOST IP>. Assuming there is no vSCSI splitter...
2020-01-20 14:13:45,278 [pool-6-thread-1] (EntitiesUtils.java:953) WARN - Caught exception when looking for ESX advanced property: no value found for UserVars.RP_SPLITTER_GENERATED_UUID
2020-01-20 14:13:45,286 [pool-6-thread-1] (VCUpdater.java:305) ERROR - Exception caught
java.lang.NullPointerException
at com.emc.recoverpoint.connectors.vi.utils.SplitterUtils.getvScsiSplitterVersion(SplitterUtils.java:248) ~[vi_connector_commons.jar:?]
at com.emc.recoverpoint.connectors.vi.utils.EntitiesUtils.getSplitterVersion(EntitiesUtils.java:793) ~[vi_connector_commons.jar:?]
at com.emc.recoverpoint.connectors.vi.builder.ESXStateBuilder.create(ESXStateBuilder.java:74) ~[vi_connector_commons.jar:?]
at com.emc.recoverpoint.connectors.vi.builder.ESXClusterStateBuilder.createEsxStateMap(ESXClusterStateBuilder.java:45) ~[vi_connector_commons.jar:?]
at com.emc.recoverpoint.connectors.vi.builder.ESXClusterStateBuilder.create(ESXClusterStateBuilder.java:30) ~[vi_connector_commons.jar:?]
at com.emc.recoverpoint.connectors.vi.builder.DataCenterStateBuilder.createESXClusterStateMap(DataCenterStateBuilder.java:120) ~[vi_connector_commons.jar:?]
at com.emc.recoverpoint.connectors.vi.builder.DataCenterStateBuilder.create(DataCenterStateBuilder.java:41) ~[vi_connector_commons.jar:?]
at com.emc.recoverpoint.connectors.vi.builder.VCStateBuilder.createDataCenterStateMap(VCStateBuilder.java:72) ~[vi_connector_commons.jar:?]


Connection with VC will fail and all CGs will go into error state.
Cause
Issue occurs if the customer is using virtual ESX hosts with no kernel modules.
When RP tries to get the ESX host kernel module system, it returns null. VMware then tries to query the module to get the kernel module info on a null value, hence it throws the null pointer exception there.
Resolution

Workaround:
Remove Nested ESX from the ESX cluster replicated within RP4VM.

Upgrading to version 5.2.x and later will prevent CGs in a mixed environment going into Error.

Resolution:
No fix is available as the problem is caused by an unsupported environment.
Nested ESX hosts are not supported by VMware or RP4VM.

See 
https://kb.vmware.com/s/article/2009916 for more information.

Notes

Issue


VCUpdater is failing with Null pointer exception, which is causing all CGs to go into error state.


In connector logs:
2020-01-20 14:13:45,267 [pool-6-thread-1] (SplitterUtils.java:66) INFO - ESX has null hostKernelModuleSystem: <HOST IP>. Assuming there is no vSCSI splitter...
2020-01-20 14:13:45,278 [pool-6-thread-1] (EntitiesUtils.java:953) WARN - Caught exception when looking for ESX advanced property: no value found for UserVars.RP_SPLITTER_GENERATED_UUID
2020-01-20 14:13:45,286 [pool-6-thread-1] (VCUpdater.java:305) ERROR - Exception caught
java.lang.NullPointerException
at com.emc.recoverpoint.connectors.vi.utils.SplitterUtils.getvScsiSplitterVersion(SplitterUtils.java:248) ~[vi_connector_commons.jar:?]
at com.emc.recoverpoint.connectors.vi.utils.EntitiesUtils.getSplitterVersion(EntitiesUtils.java:793) ~[vi_connector_commons.jar:?]
at com.emc.recoverpoint.connectors.vi.builder.ESXStateBuilder.create(ESXStateBuilder.java:74) ~[vi_connector_commons.jar:?]
at com.emc.recoverpoint.connectors.vi.builder.ESXClusterStateBuilder.createEsxStateMap(ESXClusterStateBuilder.java:45) ~[vi_connector_commons.jar:?]
at com.emc.recoverpoint.connectors.vi.builder.ESXClusterStateBuilder.create(ESXClusterStateBuilder.java:30) ~[vi_connector_commons.jar:?]
at com.emc.recoverpoint.connectors.vi.builder.DataCenterStateBuilder.createESXClusterStateMap(DataCenterStateBuilder.java:120) ~[vi_connector_commons.jar:?]
at com.emc.recoverpoint.connectors.vi.builder.DataCenterStateBuilder.create(DataCenterStateBuilder.java:41) ~[vi_connector_commons.jar:?]
at com.emc.recoverpoint.connectors.vi.builder.VCStateBuilder.createDataCenterStateMap(VCStateBuilder.java:72) ~[vi_connector_commons.jar:?]


Connection with VC will fail and all CGs will go into error state.
Cause
Issue occurs if the customer is using virtual ESX hosts with no kernel modules.
When RP tries to get the ESX host kernel module system, it returns null. VMware then tries to query the module to get the kernel module info on a null value, hence it throws the null pointer exception there.
Resolution

Workaround:
Remove Nested ESX from the ESX cluster replicated within RP4VM.

Upgrading to version 5.2.x and later will prevent CGs in a mixed environment going into Error.

Resolution:
No fix is available as the problem is caused by an unsupported environment.
Nested ESX hosts are not supported by VMware or RP4VM.

See 
https://kb.vmware.com/s/article/2009916 for more information.

Notes

Article Attachments

Attachments

Attachments

Article Properties

First Published

Fri Jan 31 2020 08:53:37 GMT

First Published

Fri Jan 31 2020 08:53:37 GMT

Rate this article

Accurate
Useful
Easy to understand
Was this article helpful?
0/3000 characters