3.In the case of a legacy package, add the new networking information to the package control script if necessary

4.Apply the new package configuration, and redistribute the control script if necessary.

For more information, see “Reconfiguring a Package on a Running Cluster ” (page 311).

Example: Deleting a Subnet Used by a Package

In this example, we are deleting subnet 15.13.170.0 (lan0). This will also mean deleting lan3, which is a standby for lan0 and not shared by any other primary LAN. Proceed as follows.

1.Halt any package that uses this subnet and delete the corresponding networking information: monitored_subnet, ip_subnet, ip_address (page 241).

See “Reconfiguring a Package on a Running Cluster ” (page 311) for more information.

2.Run cmquerycl to get the cluster configuration file: cmquerycl -c cluster1 -C clconfig.ascii

3.Comment out the network interfaces lan0 and lan3 and their network interfaces, if any, on all affected nodes. The networking portion of the

NODE_NAME

ftsys9

NETWORK_INTERFACE

lan1

HEARTBEAT_IP

192.3.17.18

# NETWORK_INTERFACE

lan0

# STATIONARY_IP

15.13.170.18

# NETWORK_INTERFACE

lan3

#Possible standby Network Interfaces for lan1, lan0: lan2.

NODE_NAMEftsys10

NETWORK_INTERFACE lan1

 

HEARTBEAT_IP

192.3.17.19

# NETWORK_INTERFACE

lan0

#

STATIONARY_IP

15.13.170.19

#

NETWORK_INTERFACE

lan3

# Possible standby Network Interfaces for lan0, lan1: lan2

4.Verify the new configuration: cmcheckconf -C clconfig.ascii

5.Apply the changes to the configuration and distribute the new binary configuration file to all cluster nodes:

cmapplyconf -C clconfig.ascii

Removing a LAN or VLAN Interface from a Node

You must remove a LAN or VLAN interface from the cluster configuration before removing the interface from the system.

On an HP-UX 11i v3 system, you can then remove the interface without shutting down the node. Follow these steps on the affected node:

NOTE: This can be done on a running system only on HP-UX 11i v3. You must shut down an HP-UX 11i v2 system before removing the interface.

1.If you are not sure whether or not a physical interface (NIC) is part of the cluster configuration, run olrad -Cwith the affected I/O slot ID as argument. If the NIC is part of the cluster configuration, you’ll see a warning message telling you to remove it from the configuration before you proceed. See the olrad(1M) manpage for more information about olrad.

2.Use the cmgetconf command to store a copy of the cluster’s existing cluster configuration in a temporary file. For example:

cmgetconf clconfig.ascii

300 Cluster and Package Maintenance

Page 300
Image 300
HP Serviceguard manual Removing a LAN or Vlan Interface from a Node, Cmgetconf clconfig.ascii