HP -UX 11i Installation And Update Manual page 106

In Case of Trouble
Common Update Problems
rolling upgrade from HP-UX 11.0 to 11i with the Mission Critical
Operating Environment (MC-OE), you are likely to be in a situation
where the problem can occur. To verify this before you upgrade, enter
this command on each cluster node to see if you have Auto-Port
Aggregation software installed:
swlist | grep J4240A
If the software is installed, use cmviewcl to display the cluster's network
configuration. Link aggregates appear in the output with a path of
LinkAgg x and a PPA name of lan1 xx , as in this example:
cmviewcl -v
CLUSTER STATUS
cluster1 down
NODE STATUS
node001 down
Network_Parameters:
INTERFACE
PRIMARY
STANDBY
NODE STATUS
node002 down
Network_Parameters:
INTERFACE
PRIMARY
STANDBY unknown
If your network parameter display includes LinkAgg x entries instead of
conventional hardware paths, then you are using automatic port
aggregation, and you should follow the procedure below.
In a rolling upgrade of the cluster, the MC/ServiceGuard nodes with the
higher revision level will not be able to join the existing cluster via the
cmrunnode command because MC/ServiceGuard continues to attach to
the DLPI using the original link aggregate PPA values. In fact, running
the cmrunnode command could result in freezing the network.
Re-run the Binary Conversion Utility: During an 11i rolling
upgrade, MC/ServiceGuard is not aware that the PPA values of
configured link aggregates have been changed. MC/ServiceGuard will
continue using the old PPA values, which are stored in the cluster
configuration database (CDB) to start the upgrading node. This may
cause unexpected behavior such as command hang. Manually
re-executing the binary conversion utility will convert the values to
latest ones in the CDB and effectively avoid the situation. Use the
106
STATE
unknown
STATUS PATH
unknown LinkAgg0
unknown LinkAgg1
STATE
unknown
STATUS PATH
unknown LinkAgg0
LinkAgg1
NAME
lan100
lan101
NAME
lan100
lan101
Appendix B