DCOM error reported when attempting to add new Enterprise Vault node to an existing Veritas Cluster configuration

book

Article ID: 100050841

calendar_today

Updated On:

Description

Error Message

Error: DCOM was unable to communicate with the server xx.xx.xx.xxx (Virtual IP of already configured Enterprise Vault ServiceGroup)

Cause

Systems/Nodes that do not exist in the existing cluster configuration fail to ping the virtual IP due to incorrect IP configuration. 

The likely cause could be that the physical IP of the nodes and the virtual IP used in the Cluster are on different subnets. 

Resolution

1)  Identify if the physical IP and virtual IP configured in VCS are on different subnets.

If so, make sure all the IP (Physical, Virtual) belong to the same subnet for existing nodes.

Offline and online the Service Group for this change to take effect in VCS

2)  If LLT is configured over IP addresses, make sure the subnet used by the LLT configuration is from the same subnet as that of the cluster nodes. 

Re-run the Veritas Cluster Configuration Wizard (VCW) to update these changes. 

After Step #1 and Step #2 as applicable, attempt to ping the EV SG virtual IP from the node to be added, which should now be successful 

The "Add node" operation can now be run without issues. 

Issue/Introduction

When running the EV configuration wizard to join an Enterprise Vault(EV) node to an existing cluster, error "Error: DCOM was unable to communicate with the server 'Virtual_IP_Adress_Of_EV_ServiceGroup'" is reported