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

OceanStor V3 Series V300R006

This document is applicable to OceanStor 2200 V3, 2600 V3, 5300 V3, 5500 V3, 5600 V3, 5800 V3, 6800 V3, 18500 V3, and 18800 V3. 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 is intended for 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).
Configurations and Operations After an HBA Replacement (in AIX)

Configurations and Operations After an HBA Replacement (in AIX)

This section describes after replacing the HBA of an AIX host, how to configure the HBA on the storage system and the host to make it work correctly.

Preparing for Configuration (in AIX)

Before configuring the new HBA, you must finish preparatory work such as backing up host multipath and disk information and checking the storage device's running status to ensure that the space configuration can be successfully implemented.

Prerequisites
  • The UltraPath software has been installed on the host.
  • The old HBA of the host has been replaced.
Procedure
  1. Back up UltraPath and disk information.

    1. Run upadm show vlun and upadm show path to view and back up the UltraPath status information.
    2. Run lsvg and lsvg vgname to view and back up volume group (VG) information where vgname represents the name of the VG.
    3. Run pvdisplay to view physical volume (PV) information.
    4. Run lsdev -Cc disk and lsdev -Cc adapter respectively to back up disk and HBA information.

  2. Check the storage system status. If there are alarms, clear them and then proceed to the next step.
  3. On the storage system, export the storage system configuration data.

    1. Log in to the CLI of the storage system using PuTTY.
      NOTE:

      The default user name and password are admin and Admin@storage respectively.

    2. Run export running_data to export and save the current configuration file.

  4. (Optional) If online replacement is used, you need to delete path information.

    • If the HBA is replaced due to a failure, do the following:
      1. Run upadm show path to show UltraPath status information.
      2. Run rmpath -dl hdiskX -p fscsiY to delete paths whose parent is fscsiY, where hdiskX and fscsiY indicate the device file name of a host disk and a to-be-replaced HBA respectively.
      3. Run upadm show iostat array_id=? to monitor the load balancing of paths. Specify the storage device using the array_id parameter.

        If I/Os are evenly distributed in the remaining paths and there are no errors after 30 seconds, press Ctrl+C to exit.

      4. Run upadm show path to show UltraPath status information.

        The information about the deleted paths should not appear in the execution result.

    • If the HBA is replaced proactively, do the following:
      1. Run upadm show path and upadm show vlun to show UltraPath status information.
      2. Run chpath -s disable -l hdiskX -p fscsiY to disable paths whose parent is fscsiY, where hdiskX and fscsiY indicate the device file name of a host disk and a to-be-replaced HBA.
      3. Run upadm show iostat array_id=? to monitor the load balancing of paths. Specify the storage device using the array_id parameter.

        If I/Os are evenly distributed in the remaining paths and there are no errors after 30 seconds, press Ctrl+C to exit.

      4. Run rmpath -dl hdiskX -p fscsiY to delete all disabled links.
      5. Run upadm show path to show UltraPath status information.

        The information about the deleted paths should not appear in the execution result.

  5. (Optional) If the HBA is replaced online, you need to delete disk devices connected to the links.

    1. Run lsdev -Cc disk and lsdev -Cc disk | wc -l to view system disk status.
    2. Run lsdev -p fscsiY and lsdev -p fscsiY -c disk -F name | xargs -n1 rmdev -dl to delete disks connected to the path.
    3. Rerun lsdev -Cc disk and lsdev -Cc disk | wc -l to view system disk information in which the deleted disks should not exist.

  6. Check whether the new HBA is compatible with the storage system.

    1. Run lscfg -vpl fcsY | grep Address to check whether the WWN of the new HBA is as planned, where fcdY represents the new HBA.
    2. Run fcstat fcsY to check whether the HBA model is compatible with the storage system.
    NOTE:

    Systems earlier than AIX 5.3 TL03 do not support the fcstat command.

  7. Check the system status and see whether there are disks or tapes connected to the HBA.

    1. Run errpt to check the storage system status. If an error exists on the HBA or any disk, remove it and proceed to the next step.
    2. Run lsdev -p fcsY and lsdev -p fscsiY to check whether there are disks or tapes connected to the new HBA, where fcsY indicates the device file name of the new HBA and fscsiY indicates the subdevice of fcsY.

      There should be no disk or tape under fscsiY.

    3. Modify the properties of the device fscsiY.
      1. Run the lsattr -El fscsiY command to check whether fc_err_recov is fast_fail and dyntrk is yes. If yes, go to Step 7.4. If no, go to Step 7.3.b.
      2. Run the rmdev -l fscsiY -R command to clear the configuration of device fscsiY.
      3. Run the chdev -l fscsiY -a fc_err_recov=fast_fail and chdev -l fscsiY -a dyntrk=yes commands to modify the properties of device fscsiY.
    4. Run cfgmgr -vl fcsY to scan for the HBA and generate the fscsiY device.
    5. Run lsattr -El fcsY and lsattr -El fscsiY to see whether device parameters are changed successfully.
    6. Run lscfg -vpl fcsY | grep Address to view the WWN of the new HBA and record it.

  8. On the switch, check whether the zoning of the new HBA is complete.

Configurations and Operations (in AIX)

Prerequisites
  • The old HBA has been replaced and the new HBA has been correctly installed.
  • The WWNs of the old and new HBAs have been obtained.
  • UltraPath has been installed on the application server.
Procedure
  1. On the storage system, replace the old WWN.

    1. Run show initiator initiator_type=FC to view the connection status between the HBA and the storage device and obtain the ID of the host to which the old HBA belongs.
       
           WWN                 Running Status        Free       Alias      Host ID         Multipath Type 
           ----------------- ------------------- -----      -------    ----------      ------------------ 
           100000000000*       Online                Yes        --         --              Default
    2. Run remove host initiator initiator_type=FC to remove the WWN of the old HBA. Specify the WWN of the old HBA using the wwn parameter.
    3. Run add host initiator host_id=? initiator_type=FC wwn=? to add the new WWN to the host. Specify the host and WWN of the new HBA using the host_id and wwn parameters.
      NOTE:

      If the system reports a failure in querying the WWN of a new HBA, run the cfmgr command and then the add host initiator host_id=? command.

    4. Run show initiator initiator_type=FC. If in the command output, the WWN status of the new HBA is not Free, then the replacement is successful.

  2. Scan for disks on the host.

    1. Run lsdev -Cc disk and lsdev -Cc disk | wc -l to show disks on the host.
    2. Run cfgmgr -vl fcsY to scan for the HBA and recognize the storage device.
    3. Rerun lsdev -Cc disk and lsdev -Cc disk | wc -l and compare the result with that in 2.a. The number of newly generated device files should be the same as expected, and the vendors should all be Huawei.
    4. Run upadm show vlun and compare the result with that in 2.a to check whether the number of disks managed by UltraPath is the same as planned.
    5. Run upadm show path to check whether the disk path status is Enable. If you find a path whose status is Degrade, check the path connection status on the storage device.

  3. Run upadm show iostat array_id=? to monitor the load balancing of paths. Specify the storage device using the array_id parameter.

    If I/Os are evenly distributed in all paths and there are no errors after 30 seconds, press Ctrl+C to exit.

Download
Updated: 2019-07-12

Document ID: EDOC1000138854

Views: 35805

Downloads: 2043

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