Operating System - HP-UX
1829703 Members
2239 Online
109992 Solutions
New Discussion

Re: Error: IP netmasks don't match

 
hp_user_1
Regular Advisor

Error: IP netmasks don't match

We have a 2-node Serviceguard cluster of HP-UX 11iv1 nodes. The cluster has been running for quite some time without any issues. Recently the company had to move from 255.255.255.0 to 255.255.255.128 netmask. I modified in the package and cluster config files and ran cmcheckconf and get the following result:

============================
# cmcheckconf -v -C cmclconfig.ascii
Checking cluster file: cmclconfig.ascii
Checking nodes ... Done
Checking existing configuration ... Done
Gathering configuration information ... Done
Gathering configuration information ... Done
Gathering configuration information ..
Gathering storage information ..
Found 424 devices on node sd01
Found 415 devices on node sd02
Analysis of 839 devices should take approximately 29 seconds
0%----10%----20%----30%----40%----50%----60%----70%----80%----90%----100%
Found 10 volume groups on node sd01
Found 10 volume groups on node sd02
Analysis of 20 volume groups should take approximately 1 seconds
0%----10%----20%----30%----40%----50%----60%----70%----80%----90%----100%
.....
Gathering Network Configuration ........ Done

Error: IP netmasks don't match, interface lan8 on sd01
Error: IP netmasks don't match, interface lan8 on sd02
cmcheckconf : Unable to reconcile configuration file cmclconfig.ascii
with discovered configuration information.
===================================

What is causing the error "IP netmasks don't match" to generate. Any ideas .... Even if I now try to run cmcheckconf on the old netmask, it still produces the same error.

Thanks
5 REPLIES 5
Asif Sharif
Honored Contributor

Re: Error: IP netmasks don't match

Hi HP_user,

The log shows there is IP subnet mask problem.

Please post the output of these commands,

#netstat -in
#lanscan
#ifconfig lan8

for BOTH nodes.

Regards,
Asif Sharif
Regards,
Asif Sharif
VK2COT
Honored Contributor

Re: Error: IP netmasks don't match

Hello,

As recommended by other replies, you must
check lan8 configuration on both nodes
in the cluster. There is no doubt you have some
mismatch.

If your netmasks do match properly and currently in netconf, then the cluster binary file might need to be deleted and recreated from the ascii file.

If netmasks do not match, then you firstly
need to set interfaces to be identical on
both nodes.

Cheers,

VK2COT
VK2COT - Dusan Baljevic
Jeeshan
Honored Contributor

Re: Error: IP netmasks don't match

before changing package and cluster config files you need first change the netmask in interface.

in your case change the netmask of interface lan8 on sd01 and interface lan8 on sd02.

otherwise you change will not take any affect.
a warrior never quits
hp_user_1
Regular Advisor

Re: Error: IP netmasks don't match

SD01:
lan8: flags=843
inet 143.242.124.1 netmask ffffff80 broadcast 143.242.124.127

LANSCAN
Hardware Station Crd Hdw Net-Interface NM MAC HP-DLPI DLPI
Path Address In# State NamePPA ID Type Support Mjr#
0/0/6/0/0/4/0 0x000F20675B1C 0 UP lan0 snap0 1 ETHER Yes 119
0/0/6/0/0/5/0 0x000F20675B1D 1 UP lan1 snap1 2 ETHER Yes 119
0/0/6/0/0/6/0 0x000F20675B1E 2 UP lan2 snap2 3 ETHER Yes 119
0/0/6/0/0/7/0 0x000F20675B1F 3 UP lan3 snap3 4 ETHER Yes 119
0/0/8/0/0/4/0 0x000F202BF3BA 4 UP lan4 snap4 5 ETHER Yes 119
1/0/1/0/0/4/0 0x000F202B4464 6 UP lan6 snap6 6 ETHER Yes 119
1/0/14/0/0/4/0 0x000F20677B10 8 UP lan8 snap8 7 ETHER Yes 119
1/0/14/0/0/5/0 0x000F20677B11 9 UP lan9 snap9 8 ETHER Yes 119
1/0/14/0/0/6/0 0x000F20677B12 10 UP lan10 snap10 9 ETHER Yes 119
1/0/14/0/0/7/0 0x000F20677B13 11 UP lan11 snap11 10 ETHER Yes 119
1/0/6/0/0 0x00306EF4CC3E 7 UP lan7 snap7 11 ETHER Yes 119
0/0/14/0/0 0x00306EF4CC3B 5 UP lan5 snap5 12 ETHER Yes 119

NETSTAT -IN
Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll
lan8:1 1500 143.242.124.0 143.242.124.101 33894 0 88 0 0
lan11 1500 172.19.4.0 172.19.4.33 124212 0 65340 0 0
lan10* 1500 none none 0 0 0 0 0
lan2 1500 172.19.2.0 172.19.2.1 159571 0 732929 0 0
lan5:1 1500 172.19.3.0 172.19.3.101 430799 0 250238 0 0
lan1:1 1500 172.19.1.0 172.19.1.101 398 0 8 0 0
lan9* 1500 none none 0 0 0 0 0
lan1 1500 172.19.1.0 172.19.1.1 297332 0 298442 0 0
lan0* 1500 none none 0 0 0 0 0
lan8 1500 143.242.124.0 143.242.124.1 625243 0 630553 0 0
lo0 4136 127.0.0.0 127.0.0.1 1999052 0 1999052 0 0
lan2:1 1500 172.19.2.0 172.19.2.101 3593 0 8 0 0
lan7* 1500 none none 12 0 214 0 50
lan5 1500 172.19.3.0 172.19.3.1 272990 0 25308942 0 134877


SD02:
lan8: flags=843
inet 143.242.124.2 netmask ffffff80 broadcast 143.242.124.127

LANSCAN:
Hardware Station Crd Hdw Net-Interface NM MAC HP-DLPI DLPI
Path Address In# State NamePPA ID Type Support Mjr#
0/0/6/0/0/4/0 0x000F2068312C 0 UP lan0 snap0 1 ETHER Yes 119
0/0/6/0/0/5/0 0x000F2068312D 1 UP lan1 snap1 2 ETHER Yes 119
0/0/6/0/0/6/0 0x000F2068312E 2 UP lan2 snap2 3 ETHER Yes 119
0/0/6/0/0/7/0 0x000F2068312F 3 UP lan3 snap3 4 ETHER Yes 119
0/0/8/0/0/4/0 0x000F202B2332 4 UP lan4 snap4 5 ETHER Yes 119
1/0/1/0/0/4/0 0x000F202B3368 6 UP lan6 snap6 6 ETHER Yes 119
1/0/14/0/0/4/0 0x000F20688104 8 UP lan8 snap8 7 ETHER Yes 119
1/0/14/0/0/5/0 0x000F20688105 9 UP lan9 snap9 8 ETHER Yes 119
1/0/14/0/0/6/0 0x000F20688106 10 UP lan10 snap10 9 ETHER Yes 119
1/0/14/0/0/7/0 0x000F20688107 11 UP lan11 snap11 10 ETHER Yes 119
1/0/6/0/0 0x00306EF4CB07 7 UP lan7 snap7 11 ETHER Yes 119
0/0/14/0/0 0x00306EF4CB2C 5 UP lan5 snap5 12 ETHER Yes 119

NETSTAT -IN:
Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll
lan11 1500 172.19.4.0 172.19.4.34 69148 0 128043 0 0
lan10* 1500 none none 0 0 0 0 0
lan2 1500 172.19.2.0 172.19.2.2 72900 0 191410 0 0
lan9* 1500 none none 0 0 0 0 0
lan1 1500 172.19.1.0 172.19.1.2 55723 0 50707 0 0
lan8 1500 143.242.124.0 143.242.124.2 95814 0 141410 0 0
lan0* 1500 none none 0 0 0 0 0
lo0 4136 127.0.0.0 127.0.0.1 1364025 0 1364025 0 0
lan7* 1500 none none 0 0 0 0 31
lan5 1500 172.19.3.0 172.19.3.2 6870650 0 6247982 0 288759


Thanks
Stephen Doud
Honored Contributor

Re: Error: IP netmasks don't match

Though you may change the subnet masks assignd to the NICs, the cluster binary file will not be aware of the change until you can update it using cmapplyconf. However, if you find that cmapplyconf fails because of the change of LAN subnets, it may be necessary to dissolve the cluster and rebuild it.

First, locate the cluster configuration ASCII file and package configuration files.
Next, perform 'cmhaltcl -f' to halt the cluster
Then try 'cmdeleteconf -f' to dissolve the cluster.
Now, with the subnet masks configured the way that you want them (see /etc/rc.config.d/netconf), rebuild the cluster:
# cmapplyconf -C -P -P ...