Need to add new package in a different subnet

[Jose_C_Moraes]

Hi, I need help

HP-UX tst93 B.11.23 U ia64 0698804623 unlimited-user license

ia64 hp server rx2660

PHKL_35420 1.0 Overtemp shutdown / Serviceguard failover
SGManagerPI B.01.01 HP Serviceguard Manager
SGWBEMProviders A.02.00.00 HP Serviceguard WBEM Providers SD Product
ServiceGuard A.11.18.00 Serviceguard SD Product


I need to add a new package in MC/SG conf, with an IP addr in a diff subnet already used by the first package.

When I use cmcheckconf, it gives me the message:

MONITORED_SUBNET 10.210.11.0 not part of the cluster.

What should I do to fix it ?

I appreciate any help, best regards
Jose

[melvyn burnard · Accepted solution]

Make sure that subnet is added in to the cluster configuration, check your cluster ascii file and amend/apply where required

[Stephen Doud]

Before a package can be configured to work with a subnet, the cluster must know about the subnet.

Use cmviewconf (OR cmviewcl -v -f line | grep subnet) to inspect the cluster binary and verify that 10.210.11.0 is listed. You will not find it, since Serviceguard did not accept it.

If you have recently installed IPs/subnets on a NIC in each node that have that subnet but are not included in the cluster ASCII file, add HEARTBEAT_IP (or STATIONARY_IP) references for the IP addresses in the ASCII file
example:
NODE_NAME tst93
...skipped...
NETWORK_INTERFACE lan4
HEARTBEAT_IP 10.210.11.12

NODE_NAME tst94
...skipped...
NETWORK_INTERFACE lan4
HEARTBEAT_IP 10.210.11.13

And then 'cmapplyconf' the file to add the NICs/network to the cluster. cmapplyconf will identify the subnet assigned to the NICs that you add, and will include it in the cluster binary (use cmviewconf to verify).

Then cmapplyconf the package configuration file.

-----------
If you are attempting to add another IP to a NIC which doesn't support 10.210.11.0 subnet, you can only do that in the customer_defined_run_cmds section (and remove the IP/subnet in customer_defined_halt_cmds) of the package control script, or for modular packages, call a script via
external_pre_script or external_script in the package configuration file that adds/removes the IP/subnet combination.

[Jose_C_Moraes]

Thanks you all.

That solved the problem.

TIA, best regards
Jose