Serviceguard package multiple subnets

[Jeff Disney]

I have a package that has an address of 10.224.217.xxx

The original subnet was 10.224.216.0 with a 255.255.255.0 subnet mask, it has been expanded to a .252 subnet mask to allow addresses on the .217 range.

My package will not bring up the .217 address, I receive the following error:
ode "kyarpd0c": Remove IP address 10.224.217.28 from subnet 10.224.216.0
cmmodnet : IP address 10.224.217.28 is not configured on the subnet.

How can I fix it?

[Sandman!]

After expansion what is the netmask...255.255.255.252 or 255.255.252.0?

[Mel Burslan]

If you can post your cluster's ascii definition file located under /etc/cmcluster directory (something.ascii is the convention used by the most) as well as your routing tables from the output of 'netstat -rn' command from all cluster members, I think the help you'll get will be more accurate.

From what you say in your question, I guess your network configuration is somehow incorrect but again without seeing the routing tables and your cluster network configuration, it is very hard to say.

[Jeff Disney]

netmask has been changed to 255.255.252.0


output of netstat:
Routing tables
Destination Gateway Flags Refs Interface Pmtu
127.0.0.1 127.0.0.1 UH 0 lo0 4136
10.224.216.121 10.224.216.121 UH 0 lan2:3 4136
10.224.216.123 10.224.216.123 UH 0 lan2:12 4136
10.224.216.124 10.224.216.124 UH 0 lan2:14 4136
10.224.216.125 10.224.216.125 UH 0 lan2:19 4136
10.224.216.118 10.224.216.118 UH 0 lan2:13 4136
10.224.216.109 10.224.216.109 UH 0 lan2:7 4136
10.224.216.110 10.224.216.110 UH 0 lan2:17 4136
10.224.216.100 10.224.216.100 UH 0 lan2:21 4136
10.224.216.103 10.224.216.103 UH 0 lan2 4136
10.224.216.153 10.224.216.153 UH 0 lan2:6 4136
10.224.216.154 10.224.216.154 UH 0 lan2:4 4136
10.224.216.158 10.224.216.158 UH 0 lan2:18 4136
10.224.216.144 10.224.216.144 UH 0 lan2:25 4136
10.224.216.146 10.224.216.146 UH 0 lan2:1 4136
10.224.216.147 10.224.216.147 UH 0 lan2:5 4136
10.224.216.150 10.224.216.150 UH 0 lan2:8 4136
10.224.216.137 10.224.216.137 UH 0 lan2:20 4136
10.224.216.139 10.224.216.139 UH 0 lan2:11 4136
10.224.216.140 10.224.216.140 UH 0 lan2:10 4136
10.224.216.143 10.224.216.143 UH 0 lan2:16 4136
10.224.216.128 10.224.216.128 UH 0 lan2:9 4136
10.224.216.242 10.224.216.242 UH 0 lan2:24 4136
10.224.216.203 10.224.216.203 UH 0 lan2:15 4136
10.224.216.205 10.224.216.205 UH 0 lan2:22 4136
10.224.216.197 10.224.216.197 UH 0 lan2:2 4136
10.224.216.199 10.224.216.199 UH 0 lan2:23 4136
10.224.216.0 10.224.216.103 U 27 lan2 1500
10.224.216.0 10.224.216.144 U 27 lan2:25 1500
10.224.216.0 10.224.216.242 U 27 lan2:24 1500
10.224.216.0 10.224.216.199 U 27 lan2:23 1500
10.224.216.0 10.224.216.205 U 27 lan2:22 1500
10.224.216.0 10.224.216.100 U 27 lan2:21 1500
10.224.216.0 10.224.216.137 U 27 lan2:20 1500
10.224.216.0 10.224.216.125 U 27 lan2:19 1500
10.224.216.0 10.224.216.158 U 27 lan2:18 1500
10.224.216.0 10.224.216.110 U 27 lan2:17 1500
10.224.216.0 10.224.216.143 U 27 lan2:16 1500
10.224.216.0 10.224.216.203 U 27 lan2:15 1500
10.224.216.0 10.224.216.124 U 27 lan2:14 1500
10.224.216.0 10.224.216.118 U 27 lan2:13 1500
10.224.216.0 10.224.216.123 U 27 lan2:12 1500
10.224.216.0 10.224.216.139 U 27 lan2:11 1500
10.224.216.0 10.224.216.140 U 27 lan2:10 1500
10.224.216.0 10.224.216.128 U 27 lan2:9 1500
10.224.216.0 10.224.216.150 U 27 lan2:8 1500
10.224.216.0 10.224.216.109 U 27 lan2:7 1500
10.224.216.0 10.224.216.153 U 27 lan2:6 1500
10.224.216.0 10.224.216.147 U 27 lan2:5 1500
10.224.216.0 10.224.216.154 U 27 lan2:4 1500
10.224.216.0 10.224.216.121 U 27 lan2:3 1500
10.224.216.0 10.224.216.197 U 27 lan2:2 1500
10.224.216.0 10.224.216.146 U 27 lan2:1 1500
127.0.0.0 127.0.0.1 U 0 lo0 0
default 10.224.216.1 UG 0 lan2 0

[melvyn burnard]

have you made the relevant changes to your cluster and package configurations?
If you have changed subnets, you need to reqapply the Serviceguard binary

[Sandman!]

Did you update the subnet information in the package control script? That is the only place (I can think of) where it goes. Though HP-UX automatically updates the routing table to reflect the interface's new netmask you can do it manually.