VERITAS Cluster Server (VCS) did not failover after node lost connection to storage on a HP-UX using HP Logical Volumes and Volume Groups.

Article:TECH8166  |  Created: 2000-01-19  |  Updated: 2001-01-25  |  Article URL http://www.symantec.com/docs/TECH8166
Article Type
Technical Solution

Product(s)

Environment

Issue



VERITAS Cluster Server (VCS) did not failover after node lost connection to storage on a HP-UX using HP Logical Volumes and Volume Groups.

Error



TAG_C 2000/08/14 13:35:39 Agent LVMLogicalVolume not sending alive messages since Mon Aug 14 13:33:26 2000

Solution



When using HP Logical Volumes with VCS it is important to change the IO Timeout value from the DEFAULT (default is 0 seconds, which means no timeout) to some positive value.  The '-v' option of the lvdisplay command can be used to determine the current IO Timeout value.  To change the value use the '-t' option of the lvchange command.  Please refer to the man pages for lvdisplay and lvchange for more information about these commands and options.

Use lvdisplay -v /dev/<VG name>/<LV name> to display the current timeout value:

    # lvdisplay -v /dev/vg00/lvol1
    --- Logical volumes ---
    LV Name                     /dev/vg00/lvol1
    VG Name                     /dev/vg00
    LV Permission               read/write
    LV Status                   available/syncd
    Mirror copies               0
    Consistency Recovery        MWC
    Schedule                    parallel
    LV Size (Mbytes)            84
    Current LE                  21
    Allocated PE                21
    Stripes                     0
    Stripe Size (Kbytes)        0
    Bad block                   off
    Allocation                  strict/contiguous
    IO Timeout (Seconds)        default

      --- Distribution of logical volume ---
      PV Name            LE on PV  PE on PV
      /dev/dsk/c1t6d0    21        21

      --- Logical extents ---
      LE    PV1                PE1   Status 1
      00000 /dev/dsk/c1t6d0    00000 current
      00001 /dev/dsk/c1t6d0    00001 current
      00002 /dev/dsk/c1t6d0    00002 current
      00003 /dev/dsk/c1t6d0    00003 current
      00004 /dev/dsk/c1t6d0    00004 current
      00005 /dev/dsk/c1t6d0    00005 current
      00006 /dev/dsk/c1t6d0    00006 current
      00007 /dev/dsk/c1t6d0    00007 current
      00008 /dev/dsk/c1t6d0    00008 current
      00009 /dev/dsk/c1t6d0    00009 current
      00010 /dev/dsk/c1t6d0    00010 current
      00011 /dev/dsk/c1t6d0    00011 current
      00012 /dev/dsk/c1t6d0    00012 current
      00013 /dev/dsk/c1t6d0    00013 current
      00014 /dev/dsk/c1t6d0    00014 current
      00015 /dev/dsk/c1t6d0    00015 current
      00016 /dev/dsk/c1t6d0    00016 current
      00017 /dev/dsk/c1t6d0    00017 current
      00018 /dev/dsk/c1t6d0    00018 current
      00019 /dev/dsk/c1t6d0    00019 current
      00020 /dev/dsk/c1t6d0    00020 current

Use lvchange -t <new IO timeout value> /dev/<VG name>/<LV name> to modify the timeout value:

    # lvchange -t 5 /dev/vg00/lvol1
    Logical volume "/dev/vg00/lvol1" has been successfully changed.
    Volume Group configuration for /dev/vg00 has been saved in /etc/lvmconf/vg00.conf


Legacy ID



231128


Article URL http://www.symantec.com/docs/TECH8166


Terms of use for this information are found in Legal Notices