Operating System - HP-UX
1832058 Members
3182 Online
110034 Solutions
New Discussion

hearbit configuration in service guard cluster

 
dgkedkwekw
Occasional Contributor

hearbit configuration in service guard cluster

hi

 

i have one hearbit cable in my  two node service guard cluster..existing heartbit ip is (lan0)192.168.1.1 and other  is lan1(192.168.1.2)

when i configuring one more heart bit ip...my system is some time getting reboot and from node 1  hear bit  "192.168.1.2" is not pinging and same thing happeing from node 2 not able to ping "192.168.1.1"......before this i was  able to ping .     other 2 ip i m giving "192.168.1.3" and "192.168.1.4"......even i have choosed different interface ..but not sure why its happening

 

while running cmcheckconfv  getting below error

 

bash1-4.2# cmcheckconf -v -C cmclconfig.ascii

Checking cluster file: cmclconfig.ascii

Note : a NODE_TIMEOUT value of 2000000 was found in line 127. For a

significant portion of installations, a higher setting is more appropriate.

Refer to the comments in the cluster configuration ascii file or Serviceguard

manual for more information on this parameter.

Checking nodes ... Done

Checking existing configuration ... Done

Volume group /dev/vg2 is configured differently on node libj026 than on node libj028

Volume group /dev/vg2 is configured differently on node libj028 than on node libj026

libj026 lan3 can communicate with libj026 lan1 over subnet 192.168.0.0

on the IP level, but not on the DLPI level.

There is possibly a network component between the two interfaces

that does not allow any data link level traffic through, which violates

a Serviceguard requirement.

libj026 lan3 can communicate with libj028 lan0 over subnet 192.168.0.0

on the IP level, but not on the DLPI level.

There is possibly a network component between the two interfaces

that does not allow any data link level traffic through, which violates

a Serviceguard requirement.

libj026 lan1 can communicate with libj026 lan3 over subnet 192.168.0.0

on the IP level, but not on the DLPI level.

There is possibly a network component between the two interfaces

that does not allow any data link level traffic through, which violates

a Serviceguard requirement.

Non-uniform connections detected,

 libj026 lan3 192.168.1.3 successfully received from libj028 lan0 192.168.1.2

 but libj028 lan0 192.168.1.2 did not receive from libj026 lan3 192.168.1.3.

 This could be due to heavy network traffic, or heavy load on libj026.

Failed to evaluate network

cmcheckconf: Unable to reconcile configuration file cmclconfig.ascii

 with discovered configuration information.

 

 

 

can any one  pls help me.....and one more thing can we use hp iscsi lan card as a heartbit????i m using iscsi lan port

1 REPLY 1
Andres_Stickar
Regular Visitor

Re: hearbit configuration in service guard cluster

If you add a new heartbeat network, you CANNOT use the same network. You must use a new one.

In fact, you must not have two interfaces with two IP addresses on the same network.

A.