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

Reminder

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

upgrade

Administrator Guide 15

OceanStor 5300 V3, 5500 V3, 5600 V3, 5800 V3, and 6800 V3 Storage System V300R003

Routine maintenance activities are the most common activities for the storage device, including powering on or off the storage device, managing users, modifying basic parameters of the storage device, and managing hardware components. This document applies to the system administrators who are responsible for carrying out routine maintenance activities, monitoring the storage device, and rectifying common device faults.
Rate and give feedback :
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Making Storage Space Available (HP-UX)

Making Storage Space Available (HP-UX)

This section describes how to enable an HP-UX-based application server to use the space of a storage system.

Context

For versions earlier than HP-UX 11iv3, only the PV-Links multipathing software is supported. For HP-UX 11iv3, two multipathing software types are supported: PV-Links and NMP.
  • PV-Links adds multiple paths of a LUN to the same volume group (VG) and uses the VG functions to manage the multiple paths. To use PV-Links, you must manually configure data for each LUN.
  • NMP can be directly used without the need to set it. You can run the scsimgr get_attr -a leg_mpath_enable command to check the NMP service status.

Procedure

  1. Log in to the HP-UX-based application server as user root.
  2. View the information about disks identified by the operating system.

    If the host operating system version is HP-UX 11iv3, you can run the ioscan -funNC disk command to view disks identified by the host operating system. If the host operating system version is HP-UX 11iv2 or 11iv1, you can run the ioscan -funC disk command to view disks identified by the host operating system.

    # ioscan -funNC disk
    Class     I  H/W Path     Driver S/W State   H/W Type     Description
    =====================================================================
    disk   162  0/3/1/0/4/0.8.0.2.0.0.0  sdisk CLAIMED DEVICE ENGENIO INF-01-00
                             /dev/dsk/c36t0d0   /dev/rdsk/c36t0d0
    disk   164  0/3/1/0/4/0.8.0.2.0.0.1  sdisk CLAIMED DEVICE ENGENIO INF-01-00
                             /dev/dsk/c36t0d1   /dev/rdsk/c36t0d1
    disk     0  0/4/1/0.0.0.0.0          sdisk CLAIMED DEVICE HP      DG146BB976
                             /dev/dsk/c2t0d0   /dev/rdsk/c2t0d0
    disk     1  0/4/1/0.0.0.1.0          sdisk CLAIMED DEVICE HP      DG146BB976
                             /dev/dsk/c2t1d0     /dev/dsk/c2t1d0s2   /dev/rdsk/c2t1d0    /dev/rdsk/c2t1d0s2
                             /dev/dsk/c2t1d0s1   /dev/dsk/c2t1d0s3   /dev/rdsk/c2t1d0s1  /dev/rdsk/c2t1d0s3
    disk   194  0/6/1/0/4/0.1.14.232.0.0.0  sdisk CLAIMED DEVICE   XXXX
                             /dev/dsk/c45t0d0   /dev/rdsk/c45t0d0
    disk   195  0/6/1/0/4/0.1.14.232.0.0.1  sdisk CLAIMED DEVICE   XXXX
                             /dev/dsk/c45t0d1   /dev/rdsk/c45t0d1
    disk   196  0/6/1/0/4/0.1.14.232.0.0.2  sdisk CLAIMED DEVICE   XXXX
                             /dev/dsk/c45t0d2   /dev/rdsk/c45t0d2
    disk   197  0/6/1/0/4/0.1.14.232.0.0.3  sdisk CLAIMED DEVICE   XXXX
                             /dev/dsk/c45t0d3   /dev/rdsk/c45t0d3
    disk   206  0/6/1/0/4/0.1.14.232.0.1.0  sdisk CLAIMED DEVICE   XXXX
                             /dev/dsk/c45t1d0   /dev/rdsk/c45t1d0
    disk     4  255/1/0.0.0  sdisk CLAIMED DEVICE TEAC   DVD-ROM DW-224EV
                             /dev/dsk/c3t0d0   /dev/rdsk/c3t0d0
    
    
    NOTE:
    The host operating system creates a device file for a LUN that is mapped. If the host operating system does not create a device file, you must run the insf -e command to create or re-create device files for the existing LUNs.

    In the command output, XXXX indicates a specific product model or brand.

  3. Run the ioscan -kfNnC disk command to query the name of the logical disk mapped to the application server.

    # ioscan -kfNnC disk
    Class     I  H/W Path  Driver S/W State   H/W Type     Description
    ===================================================================
    disk      2  64000/0xfa00/0x0   esdisk CLAIMED DEVICE   HP    DG146BB976
                          /dev/disk/disk2      /dev/disk/disk2_p2   /dev/rdisk/disk2     /dev/rdisk/disk2_p2
                          /dev/disk/disk2_p1   /dev/disk/disk2_p3   /dev/rdisk/disk2_p1  /dev/rdisk/disk2_p3
    disk      3  64000/0xfa00/0x1   esdisk CLAIMED DEVICE   HP    DG146BB976
                          /dev/disk/disk3   /dev/rdisk/disk3
    disk      5  64000/0xfa00/0x2   esdisk CLAIMED DEVICE   TEAC DVD-ROM DW-224EV
                          /dev/disk/disk5   /dev/rdisk/disk5
    disk    172  64000/0xfa00/0x58  esdisk CLAIMED DEVICE   ENGENIO INF-01-00
                          /dev/disk/disk172   /dev/rdisk/disk172
    disk    173  64000/0xfa00/0x59  esdisk CLAIMED DEVICE   ENGENIO INF-01-00
                          /dev/disk/disk173   /dev/rdisk/disk173
    disk    202  64000/0xfa00/0x5b  esdisk CLAIMED DEVICE   XXXX
                          /dev/disk/disk202   /dev/rdisk/disk202
    disk    203  64000/0xfa00/0x5c  esdisk CLAIMED DEVICE   XXXX
                          /dev/disk/disk203   /dev/rdisk/disk203
    disk    204  64000/0xfa00/0x5d  esdisk CLAIMED DEVICE   XXXX
                          /dev/disk/disk204   /dev/rdisk/disk204
    disk    205  64000/0xfa00/0x5e  esdisk CLAIMED DEVICE   XXXX
                          /dev/disk/disk205   /dev/rdisk/disk205
    disk    208  64000/0xfa00/0x5f  esdisk CLAIMED DEVICE   XXXX
                          /dev/disk/disk208   /dev/rdisk/disk208

    In the command output, XXXX indicates a specific product model or brand.

    NOTE:
    • The disk displayed in the last line is newly mapped to the application server.
    • If no new logical disk is detected, troubleshoot the fault and rescan for logical disks. Possible faults include:
      • The application server is incorrectly connected to the storage system after the network cable has been removed and reinserted.
      • The link between the application server and storage system is down.
      • The rate of the Fibre Channel host port is inconsistent with that of the Fibre Channel HBA on the application server.
      • The HBA driver has been uninstalled.
      • The storage pool fails.
      • Multipathing software is not installed or an incorrect version is installed.
      • The device file on the application server is lost.

      For details, see Failure to Discover LUNs by an Application Server in the OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800 V3 Storage System V300R003 Troubleshooting.

  4. Create a physical volume.

    NOTE:
    If the PV-Links multipathing software is used, you must create physical volumes for the block devices corresponding to the paths of the LUN.
    Run the following command to create a physical volume:
    # pvcreate /dev/rdisk/disk208
    Physical volume "/dev/rdisk/disk208" has been successfully created.

    In this example, a physical volume is created for the newly mapped /dev/rdisk/disk208 disk.

  5. Create a physical volume group.

    NOTE:
    If the PV-Links multipathing software is used, you must create a volume group for the LUN. The volume group contains the physical volumes corresponding to the LUN's paths.

    1. Create a directory for the physical volume group.

      Run the following command to create a directory for the physical volume group:
      # mkdir /dev/vgnn

      In this example, the /dev/vgnn directory is created for the physical volume group.

    2. Create a device file in the newly created directory.

      Run the following command to create a device file:
      # mknod /dev/vgnn/group c 64 0x110000

      In this example, the name, type, major number, and minor number of the device file are group, c (character device), 64, and 0x110000 respectively.

      NOTE:
      • The major number of a device file is 64.
      • The minor number is a hexadecimal string in the format of 0xNN0000, where NN indicates the volume group number. The value of NN must be unique.

    3. Create a physical volume group and allocate physical volumes to it.

      Run the following command to create a physical volume group and add physical volumes to it:
      # vgcreate /dev/vgnn /dev/disk/disk208

      In this example, the /dev/vgnn physical volume group is created and is allocated the /dev/disk/disk208 physical volume.

      The following output is displayed:
      Increased the number of physical extents per physical volume to 1279.
      Volume group "/dev/vgnn" has been successfully created.
      Volume Group configuration for /dev/vgnn has been saved in /etc/lvmconf/vgnn.conf
      
      NOTE:

      This physical volume group contains 1279 partitions.

  6. Create a logical volume.

    Run the lvcreate command to create a logical volume:
    # lvcreate -l 279 /dev/vgnn
    Logical volume "/dev/vgnn/lvol1" has been successfully created with
    character device "/dev/vgnn/rlvol1".
    Logical volume "/dev/vgnn/lvol1" has been successfully extended.
    Volume Group configuration for /dev/vgnn has been saved in /etc/lvmconf/vgnn.conf
    

    In this example, the /dev/vgnn/lvoln logical volume contains 279 partitions. n in lvoln is automatically assigned by the LVM.

    NOTE:

    When the logical volume is being created, a block device file and a character device file are also created and saved in the /dev/vgnn directory.

  7. Create a file system on the logical volume.

    Run the newfs command to create a file system.
    # newfs /dev/vgnn/rlvol1
    newfs: /etc/default/fs is used for determining the file system type
        version 6 layout
        5238784 sectors, 5238784 blocks of size 1024, log size 16384 blocks
    largefiles supported
    

    In this example, a file system of the default type is created. To create other types of file system, see the corresponding manual of the HP-UX operating system.

  8. Create a file directory.

    Run the following command to create a file directory:
    # mkdir /directory

    In this example, the /directory directory is created.

  9. Mount the logical volume to the file directory.

    Run the following command to mount the logical volume to the file directory:
    # mount /dev/vgnn/lvol1 /directory

    In this example, the /dev/vgnn/lvol1 logical volume is mounted to /directory.

Result

Successful mounting ensures that the application server can read and write the logical disk as a normal disk. Run the mount command to check whether the logical disk is properly mounted.

Translation
Download
Updated: 2019-04-17

Document ID: EDOC1000084191

Views: 85684

Downloads: 2298

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next