Loading...
Loading...
When trying to Modify vRPA cluster Network, WDM fails with error: Failed to retrieve NIC VLAN information: Failed retrieving Cluster's NICs VLAN information (VLAN map does not match topology).
From ClusterLogic.log (/home/kos/RPServers/RPServers_logs/clusterlogic): 2023/02/21 10:34:45.560 [pool-305-thread-6] (BaseInstallationServerAdapter.java:245) DEBUG - Result from Installation Server: Result [completedSuccessfully=true, errorMessage=null, errorType=null, value=EthToVLans [ethToVLan=[EthToVLan [ethNumber=1, vLanName=RP4VMs_Data (DSwitch)], EthToVLan [ethNumber=0, vLanName=VM Network (DSwitch)], EthToVLan [ethNumber=2, vLanName=RP4VMs_Data (DSwitch)]]]] 2023/02/21 10:34:45.561 [pool-305-thread-6] (GetVmEthToVLansMapTask.java:64) DEBUG - got ETH to VLAN map: {0=VM Network (DSwitch), 1=RP4VMs_Data (DSwitch), 2=RP4VMs_Data (DSwitch)} 2023/02/21 10:34:45.561 [pool-305-thread-6] (Task.java:93) DEBUG - GetVmEthToVLansMapTask: Task successful: Getting the VM's map from ETH port number to VLAN. 2023/02/21 10:34:45.561 [pool-305-thread-6] (Task.java:111) DEBUG - GetVmEthToVLansMapTask: task: Getting the VM's map from ETH port number to VLAN.old status is: RUNNING, setting status to SUCCESS. 2023/02/21 10:34:45.561 [pool-305-thread-6] (GetNicsVLANInfoTask.java:58) DEBUG - Got eth to vlan mapping : {0=VM Network (DSwitch), 1=RP4VMs_Data (DSwitch), 2=RP4VMs_Data (DSwitch)} 2023/02/21 10:34:45.561 [pool-305-thread-6] (GetNicsVLANInfoTask.java:93) ERROR - number of NICs does not match... 2 != 3 2023/02/21 10:34:45.562 [pool-305-thread-6] (Task.java:116) DEBUG - GetNicsVLANInfoTask: task: Retrieving Cluster's NICs VLAN information.old status is: SUCCESS, setting status to ERROR. 2023/02/21 10:34:45.562 [pool-305-thread-6] (Task.java:98) ERROR - GetNicsVLANInfoTask :Task failed: Retrieving Cluster's NICs VLAN information. com.emc.recoverpoint.utils.javainfra.status.tasks.exception.TaskFailedException: Failed retrieving Cluster's NICs VLAN information (VLAN map does not match topology). at com.emc.recoverpoint.deployment.task.GetNicsVLANInfoTask.verifyTopologyMatchesVlansSize(GetNicsVLANInfoTask.java:94) at com.emc.recoverpoint.deployment.task.GetNicsVLANInfoTask.generateNicRolesToVlanName(GetNicsVLANInfoTask.java:68) at com.emc.recoverpoint.deployment.task.GetNicsVLANInfoTask.calculateReturnValue(GetNicsVLANInfoTask.java:60) at com.emc.recoverpoint.deployment.task.GetNicsVLANInfoTask.calculateReturnValue(GetNicsVLANInfoTask.java:19) at com.emc.recoverpoint.utils.javainfra.status.tasks.SerialTask.perform(SerialTask.java:39) at com.emc.recoverpoint.utils.javainfra.status.tasks.Task.executeSync(Task.java:91) at com.emc.recoverpoint.utils.javainfra.status.tasks.SerialTask.perform(SerialTask.java:32) at com.emc.recoverpoint.utils.javainfra.status.tasks.Task.executeSync(Task.java:91) at com.emc.recoverpoint.utils.javainfra.status.tasks.Task.call(Task.java:142) at java.util.concurrent.FutureTask.run(FutureTask.java:266) 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:823) 2023/02/21 10:34:45.562 [pool-305-thread-6] (Task.java:116) DEBUG - GetNicsVLANInfoExternalTask: task: Retrieving Cluster's NICs VLAN information.old status is: ERROR, setting status to ERROR. 2023/02/21 10:34:45.572 [pool-305-thread-6] (Task.java:124) DEBUG - GetRecentOperationsTask: Start running task: Getting recent operations. 2023/02/21 10:34:45.573 [pool-305-thread-6] (BaseRpaCall.java:36) DEBUG - Starting GetAllPersistedDataCall 2023/02/21 10:34:45.580 [pool-305-thread-6] (Task.java:93) DEBUG - GetRecentOperationsTask: Task successful: Getting recent operations. 2023/02/21 10:34:45.580 [pool-305-thread-6] (Task.java:111) DEBUG - GetRecentOperationsTask: task: Getting recent operations.old status is: RUNNING, setting status to SUCCESS. 2023/02/21 10:34:45.580 [pool-305-thread-6] (Task.java:98) ERROR - GetNicsVLANInfoExternalTask :Task failed: Retrieving Cluster's NICs VLAN information. com.emc.recoverpoint.utils.javainfra.status.tasks.exception.TaskFailedException: Failed retrieving Cluster's NICs VLAN information (VLAN map does not match topology). at com.emc.recoverpoint.utils.javainfra.status.tasks.SerialTask.perform(SerialTask.java:35) at com.emc.recoverpoint.utils.javainfra.status.tasks.Task.executeSync(Task.java:91) at com.emc.recoverpoint.utils.javainfra.status.tasks.Task.call(Task.java:142) at java.util.concurrent.FutureTask.run(FutureTask.java:266) 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:823) Caused by: com.emc.recoverpoint.utils.javainfra.status.tasks.exception.TaskFailedException: Failed retrieving Cluster's NICs VLAN information (VLAN map does not match topology). at com.emc.recoverpoint.deployment.task.GetNicsVLANInfoTask.verifyTopologyMatchesVlansSize(GetNicsVLANInfoTask.java:94) at com.emc.recoverpoint.deployment.task.GetNicsVLANInfoTask.generateNicRolesToVlanName(GetNicsVLANInfoTask.java:68) at com.emc.recoverpoint.deployment.task.GetNicsVLANInfoTask.calculateReturnValue(GetNicsVLANInfoTask.java:60) at com.emc.recoverpoint.deployment.task.GetNicsVLANInfoTask.calculateReturnValue(GetNicsVLANInfoTask.java:19) at com.emc.recoverpoint.utils.javainfra.status.tasks.SerialTask.perform(SerialTask.java:39) at com.emc.recoverpoint.utils.javainfra.status.tasks.Task.executeSync(Task.java:91) at com.emc.recoverpoint.utils.javainfra.status.tasks.SerialTask.perform(SerialTask.java:32) ... 6 more Then, after reviewing the RPA VM settings, you may see that there is an extra vNIC assigned . The below image shows an example of it: RecoverPoint cluster network topology differs from the configuration of the VM. In the example, RPA topology is "data is separated". This kind of topology implies 1 vNIC for WAN+LAN traffic and 1 vNIC for data traffic, while the VM is configured with 3 vNIC. NOTE: The example shown may differ from your environment.
Workaround: Remove the extra vNIC attached to the RPA VM/s. Go to RPA VM settings and remove the extra vNIC, see example below: NOTE: The example shown may differ from your environment. Resolution: The issue stated in this article is not related to RecoverPoint functionalities, no change is needed at product level.
Click on a version to see all relevant bugs
Dell Integration
Learn more about where this data comes from
BugZero Plan
Streamline upgrades with automated vendor bug scrubs
BugZero Prevent
Wish you caught this bug sooner? Get proactive today.