No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.


ServiceGuard cluster can't start in HP-UX when data is being migrated by VIS

Publication Date:  2014-08-16 Views:  180 Downloads:  0

Issue Description

Service environment consisted of two HP-UX hosts, ST9990 storage and ServiceGuard cluster.
Following was the origin lock-disk labels in configuration file of ServiceGuard:
Because of the remapping via VIS, the lock-disk labels changed in the hosts. By camparision
the new lock-disk labels changed to disk2245 and disk2246, configuration file was been revised as following:
After the restart of ServiceGuard, the cluster still not running and sent an error: not find the PV in lock VG

Alarm Information

error: not find the PV in lock VG

Handling Process

1, Stop service and deactive the VG;
2, Export the configuration file of VG and delete the VG;
3, Add the "-N" parameter and reimport the VG ;
The device file change to persistent device after the reimport of VG, restart the ServiceGuard cluster successfully.

Root Cause

Obtained the information of lock VG by the command: vgdisplay -v vg01 and found that the device file of PV
had been changed to legacy(PV-link multi-path):
--- Physical volumes ---
   PV Name                     /dev/dsk/c13t0d1
   PV Name                     /dev/dsk/c15t0d1 Alternate Link
But NMP had been running before the import of VG, reconfirmed the status of NMP:
scsimgr get_attr –a leg_mpath_enable
It indicated that the ligacy DFSs(PV-link multi-path) for PV took effect under the running of NMP, conflicted with
the origin environment that used NMP.
The new parameter, -N, would be added when the VG was imported in HP-UX 11.31, otherwise the hosts
would use the legacy device file.


HP-UX 11.31 supports two kinds of multi-path software(PV-link and NMP), data migration will be in accordence with
the origin configuration of service.