Error Message

Error in log:

2012-11-30 20:25:41 nodeA VxVM VVR Warning V-5-20-6557 IpmHandle TAG_C Cannot connect to nodeB on port 8199
2012-11-30 20:25:41 nodeA VxVM VVR Notice V-5-20-6747 RDS TAG_D RDS datavg_rvg[datadg]: Forced cluster IPM to host nodeB failed
2012-11-30 20:25:41 nodeA VxVM VVR Debug V-5-20-0 RVG TAG_E RVG datavg_rvg[datadg]: set mConfigStatus to 0x0
2012-11-30 20:25:41 nodeA VxVM VVR Debug V-5-20-0 RVG TAG_E change cvm status of peer nodeB from 800000000000 to 800000000000
2012-11-30 20:26:02 VxVM VVR Warning V-5-20-0 TAG_C IpmHandle::handleTo No handle found to nodeB
2012-11-30 20:26:02 VxVM VVR Warning V-5-20-0 TAG_C IpmHandle::open: connect error(Invalid argument)
2012-11-30 20:26:02 nodeA VxVM VVR Warning V-5-20-6557 IpmHandle TAG_C Cannot connect to nodeB on port 8199
2012-11-30 20:26:02 nodeA VxVM VVR Notice V-5-20-6747 RDS TAG_D RDS datavg_rvg[datadg]: Forced cluster IPM to host nodeB failed
2012-11-30 20:26:02 nodeA VxVM VVR Debug V-5-20-0 RVG TAG_E RVG datavg_rvg[datadg]: set mConfigStatus to 0x0
2012-11-30 20:26:02 nodeA VxVM VVR Debug V-5-20-0 RVG TAG_E change cvm status of peer nodeB from 800000000000 to 80000000000
 

This behavior has been observed in cases where /etc/hosts contains invalid hostname entries. 
 

Review /etc/hosts to determine if the file contains any invalid hostname entries. In particular, confirm that the hostname entries for the loopback addresses (127.0.0.1 and ::1) contain valid data.