cmcheckconf problem

[Co van Berkel]

Hey,

We run on two rp4440 servers and HP-UX 11.11 (11i v1). These servers are in a MC/SG cluster A.11.16.00.

LAN0 - We use lan0 for primary heart beat on both servers and use a cross cable.
LAN1 - The primary network interface, also heart beat.
LAN3 – Standby network interface

- Configured in “/etc/cmcluster/cmclconf.ascii”:
NODE_NAME
NETWORK_INTERFACE lan0
HEARTBEAT_IP
NETWORK_INTERFACE lan1
HEARTBEAT_IP
NETWORK_INTERFACE lan3

NODE_NAME
NETWORK_INTERFACE lan0
HEARTBEAT_IP
NETWORK_INTERFACE lan1
HEARTBEAT_IP
NETWORK_INTERFACE lan3

- Configured in “/etc/rc.config.d/netconf”:
INTERFACE_NAME[0]="lan0"
IP_ADDRESS[0]="IP-1a / IP-2a"
SUBNET_MASK[0]="0xfffffff8"
BROADCAST_ADDRESS[0]="x.x.x.x"
INTERFACE_STATE[0]=up
DHCP_ENABLE[0]=0

INTERFACE_NAME[1]="lan1"
IP_ADDRESS[1]="IP-1b / IP-2b"
SUBNET_MASK[1]="0xfffffe00"
BROADCAST_ADDRESS[1]="x.x.x.x"
INTERFACE_STATE[1]=up
DHCP_ENABLE[1]=0

# INTERFACE_NAME[2]="lan3"
# IP_ADDRESS[2]="0.0.0.0"
# SUBNET_MASK[2]="0x00000000"

> netstat -in
Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll
lan3* 1500 none none 0 0 0 0 0
lan1:1 1500 x.x.x.x x.x.x.x 10917141 0 39815 0 0
lan1 1500 x.x.x.x x.x.x.x 154861954 0 320669559 0 0
lan0 1500 x.x.x.x x.x.x.x 269681 0 138646 0 0
lo0 4136 127.0.0.0 127.0.0.1 16734222 0 16734224 0 0

> lanscan
Hardware Station Crd Hdw Net-Interface NM MAC HP-DLPI DLPI
Path Address In# State NamePPA ID Type Support Mjr#
0/1/2/0 0x00306EF44D01 0 UP lan0 snap0 1 ETHER Yes 119
0/2/1/0/6/0 0x00306E5E2B18 1 UP lan1 snap1 2 ETHER Yes 119
0/2/1/0/7/0 0x00306E5E2B19 2 UP lan2 snap2 3 ETHER Yes 119
0/6/1/0/6/0 0x00306E5E1BCC 3 UP lan3 snap3 4 ETHER Yes 119
0/6/1/0/7/0 0x00306E5E1BCD 4 UP lan4 snap4 5 ETHER Yes 119

> linkloop -i 0 0x00306EF44D01
Link connectivity to LAN station: 0x00306EF44D01
-- OK

> linkloop -i 1 0x00306E5E2B18
Link connectivity to LAN station: 0x00306E5E2B18
-- OK

> linkloop -i 3 0x00306E5E1BCC
Link connectivity to LAN station: 0x00306E5E1BCC
-- OK


The following problem occurred.

After a reboot and the cluster is not yet started:
1. Then I run the command “cmcheckconf –C … -p …” I’ll did a error message (sorry forgot to write it down) about lan3? On both nodes the same error!

2. Then I started the cluster, without any problem!

3. Run the “cmcheckconf –C … -p …” command and than no error message is displayed?

Does anybody know why I can’t do a cmcheckconf when the cluster is down?

Regards,
CvB

[melvyn burnard · Accepted solution]

without the error, there is not much information to go on, and therefore not much to say, other than that there may have been a networking issue

[Steven E. Protter]

Shalom,

Tough Diagnosis here.

What does the cmnodelist file look like.

Also cmquerycl probably failed and that needs to be dealt with.

cmcheckconf checks the configuration after make changes, whether or not the cluster is running.

SEP

[Co van Berkel]

Hey,
When I do a cmquerycl the next thing shows up:

...
Bridged networks (local node information only - full probing was not performed):

1 lan0 (node-1)

2 lan1 (node-1)

6 lan0 (node-2)

7 lan1 (node-2)
lan3 (node-2)

IP subnets:
IPv4:
x.x.x.x lan0 (node-1)
lan0 (node-2)

x.x.x.x lan1 (node-1)
lan1 (node-2)

IPv6:
Possible Heartbeat IPs:
x.x.x.x x.x.x.x (node-1)
x.x.x.x (node-2)

x.x.x.x x.x.x.x (node-1)
x.x.x.x (node-2)
...

I miss LAN3 by node-1?

Regards,
CvB

[Co van Berkel]

Hey,

NODE-1:
=======
node-1:> ifconfig lan3
lan3: flags=842
inet 0.0.0.0 netmask 0

node-1:> ifconfig lan1
lan1: flags=843
inet x.x.x.x netmask fffffe00 broadcast x.x.x.x

node-1:> ifconfig lan0
lan0: flags=1843
inet x.x.x.x netmask fffffff8 broadcast x.x.x.x

NODE-2:
=======
node-2:> ifconfig lan3
lan3: flags=842
inet 0.0.0.0 netmask 0

node-2:> ifconfig lan1
lan1: flags=843
inet x.x.x.x netmask fffffe00 broadcast x.x.x.x

node-2:> ifconfig lan0
lan0: flags=1843
inet x.x.x.x netmask fffffff8 broadcast x.x.x.x

Some more info.

Regards,
CvB

[Co van Berkel]

Close