1 Pre-check Handling

Procedure

1. Check whether the storage array version is any of the following: V300R002C10 or a version that is earlier than V300R001C20, V100R0001C30, or V200R002C20.

·         If yes, go to 2.

·         If not, go to step 3.

2. Check whether port groups exist in the mapping view of the storage array.

·         If port groups exist, log in to the host in the mapping view to perform a check.

·         If no port group exists, perform a check by referring to "Front-End Redundancy Path Check B."

3. Check whether the storage array version is later than V300R006C20.

·         If yes, perform a check by referring to "Front-End Redundancy Path Check B."

·         If not, perform a check by referring to "Front-End Redundancy Path Check A."

2 Front-End Redundant Path Check A

Procedure

1. Log in to DeviceManager and choose Provisioning > Host. Traverse all hosts to check whether mapped LUNs exist on the host.

 

The preceding figure shows that mapped LUNs exist on host Host001.

• If mapped LUNs exist on the host, go to 2.
• If no mapped LUN exists on the host, the redundant path check is passed.

2. Click the Initiator tab on the Host page, and check whether initiators whose Status is Online are displayed on the Initiator tab.

 

The preceding figure shows that three online initiators exist on host Host001.

• If such initiators are displayed, go to 3.
• If no such initiator is displayed, the redundant path check is passed.

 

3. On DeviceManager, choose Provisioning > Mapping View. Find the mapping view of the host and check whether port groups exist in the mapping view.

 

 

The preceding figure shows that MappingView003 is the mapping view of Host001. PortGroup001 exists in the mapping view, and there are four connected ports.

• If port groups exist in the mapping view, go to 4.
• If no port group exists in the mapping view, go to 5.

4. On DeviceManager, choose Provisioning > Port. Transverse ports whose Running Status is Connected obtained in step 3 and query the initiators that are in the Online state. Compare the initiators with those obtained in step 2, and check whether a port corresponding to initiators of the same type contains any of the following controller groups: controllers A and B, A and D, C and B, or C and D.

 

The preceding figure shows that an online iSCSI initiator is obtained on port CTE0.A3.P0.

• If there is such a port, the redundant path check for the current host is passed.
• If no such a port exists, the redundant path check for the current host is not passed.

5. On DeviceManager, choose Provisioning > Port. Transverse all ports whose Running Status is Connected and query the initiators that are in the Online state. Compare the initiators with those obtained in step 2, and check whether a port corresponding to initiators of the same type contains any of the following controller groups: controllers A and B, A and D, C and B, or C and D.

 

The preceding figure shows that an online iSCSI initiator is obtained on port CTE0.A3.P0.

• If there is such a port, the redundant path check for the current host is passed.
• If no such a port exists, the redundant path check for the current host is not passed.

 

3 Front-End Redundancy Path Check B

Procedure

1. Log in to DeviceManager and choose Provisioning > Host. Traverse all hosts to check whether mapped LUNs exist on the host.

The preceding figure shows that mapped LUNs exist on host Host001.

• If mapped LUNs exist on the host, go to 2.
• If no mapped LUN exists on the host, the redundant path check for the current host is passed.

2. On DeviceManager, choose Provisioning > Mapping View. Find the mapping view of the host and check whether port groups exist in the mapping view.

 

The preceding figure shows that MappingView003 is the mapping view of Host001. PortGroup001 exists in the mapping view, and there are four connected ports.

• If port groups exist in the mapping view, go to 3.
• If no port group exists in the mapping view, go to 5.

3. On DeviceManager, choose Provisioning > Host. Click the Initiator tab, and check whether initiators whose Status is Online are displayed on the Initiator tab.

 

The preceding figure shows that three online initiators exist on host Host001.

• If such initiators are displayed, go to 4.
• If no such initiator is displayed, the redundant path check for the current host is passed.

4. On DeviceManager, choose Provisioning > Port. Transverse ports whose Running Status is Connected obtained in step 2 and query the initiators that are in the Online state. Compare the initiators with those obtained in step 3, and check whether a port corresponding to initiators of the same type contains any of the following controller groups: controllers A and B, A and D, C and B, or C and D.

 

The preceding figure shows that an online iSCSI initiator is obtained on port CTE0.A3.P0.

• If there is such a port, the redundant path check for the current host is passed.
• If no such a port exists, the redundant path check for the current host is not passed.

5. Click the Path tab on the Host page and check whether the path of the host meets the following conditions: 1. An online link exists. 2. Online links of the same initiator type involve paths to any of the following controller groups: controllers A and B, A and D, C and B, or C and D.

 

The preceding figure shows that four online links exist on host Host001.

• If there is such a path, the redundant path check for the current host is passed.
• If no such a path exists, the redundant path check for the current host is not passed.

 

4 Handling Procedure Used When the Results Are Not Passed

Procedure

1. Check whether the host operating system is HP UNIX and whether iSCSI links exist on the network.

• If yes, log in to the host to manually check for redundant links. For details, see "Checking Links of Multipath Software on a Host."
• If no, go to step 2.

2. Check whether the current storage array version is any of the following: V300R002C10 or a version that is earlier than V300R001C20, V100R001C30, or V200R002C20.

• If yes, go to 3.
• If no, go to step 5.

3. Check whether a 16 Gbit/s FC/SmartIO interface module exists on the storage array.

• If yes, log in to the host to manually check for redundant links. For details, see "Checking Links of Multipath Software on a Host."
• If no, go to step 4.

4. Check whether the number of host links is 9 on the host that fail to pass the check.

• If yes, log in to the host to manually check for redundant links. For details, see "Checking Links of Multipath Software on a Host."
• If no, go to step 5.

5. Log in to the host and restore the redundant paths of the host that are not redundant. For details, see the host compatibility evaluation and rectification cases.

 

5 Checking Links of Multipath Software on a Host

This chapter describes how to check the host multipathing link status before an upgrade to ensure that services are not affected during the upgrade.

Context

Online upgrade of storage devices is performed by upgrading controllers in a batch. By default, controllers are upgraded in two batches by controller ID (for example, 0, 1, 2, or 3) and odd or even plane of a single-engine four-controller device (controller 0A, 0B, 0C, and 0D). During the upgrade and restart of each batch of controllers, ensure that there are available links between other controllers and hosts to avoid host I/Os interruption. Therefore, the link between the multipath software and controllers must meet the following redundancy requirements:

1.         At least one available link exists between the host and controller even plane (Controllers 0, 2, 4, 6, 8, 10, 12, and 14: controllers XA and XC for a single-engine four-controller device, and controller XA for a single-engine dual-controller device).

2.         At least one available link exists between the host and controller odd plane (Controllers 1, 3, 5, 7, 9, 11, 13, and 15: controllers XB and XD for a single-engine four-controller device, and controller XB for a single-engine dual-controller device).

Take a single-engine four-controller storage device with the controller number being 0A/0B/0C/0D as an example.

l   You can perform an online upgrade if the following networking mode is used: 0A/0B, 0A/0D, 0B/0C, or 0B/0D has links, or more than three controllers have links.

l   You cannot perform an online upgrade if the following networking mode is used: 0A/0C or 0B/0D has links but other controllers do not have links, or there is only one link between the host and all controllers.

• The preceding networking requirements are the minimum networking requirements for an online upgrade. To improve service reliability during the online upgrade, it is strongly recommended that there should be available links between the host and each controller or there should be available links between the host and even planes of each engine.
• To ensure that each LUN mapped to the host has redundant links, this chapter describes how to check redundant links based on each LUN mapped to the host. If the number of LUNs mapped to the host cannot be checked one by one, you can randomly select some LUNs to check redundant links between the host and controllers.
• This chapter describes how to check redundant links, which applies only to Huawei UltraPath and multipathing software provided by the system. If third-party multipath software is used, perform a check by referring to the check method for the third-party multipath software or the preceding networking requirements.

5.1 VMware ESX

This section describes how to check redundant links for VMware ESX or ESXi.

5.1.1 Checking Redundant Links When UltraPath Is Used

   Step 1      Log in to the VMware ESX system and run the esxcli upadm show version command. Check whether Software Version and Driver Version are contained in the command output. If yes, UltraPath has been installed, as shown in the following figure. Go to the next step. If no, perform a check by referring to section 5.1.2 "Checking Redundant Links When Multipath Software Provided by VMware Is Used."

 

   Step 2      Run the esxcli upadm show vlun command to view the value of Vlun ID, as shown in the following figure. If no VLUN information is not displayed, UltraPath does not take over any LUNs. Perform a check by referring to section 5.1.2 "Checking Redundant Links When Multipath Software Provided by VMware Is Used." Otherwise, go to the next step.

 

   Step 3      Run the esxcli upadm show vlun -l [VLUN ID] (applicable to multipath software whose version is 8.01.051 or earlier) or esxcli upadm show vlun -l [VLUN ID] -t all (when the UltraPath version is later than 8.01.051) commands in sequence to query path information about all LUNs, as shown in the following figures.

 

 

   Step 4      View the VLUN path information to check whether available paths in the Normal state exist on controllers of the odd plane (controllers XB and XD for a single-engine four-controller device, and controller XB for a single-engine dual-controller device) and controllers of the even plane (controllers XA and XC for a single-engine four-controller device, and controller XA for a single-engine dual-controller device). In  the following figure, each of controllers 0A and 0B has two paths, meeting the online upgrade requirements.

 

----End

5.1.2 Checking Redundant Links When Multipath Software Provided by VMware Is Used

   Step 1      Run the esxcfg-mpath -b | grep -E -i "huawei|huasy|symantec|hs|eisoo|udsafe|marstor|sanm|anystor|sugon|netposa" command to check whether Huawei disks exist. If no Huawei disk is found, as shown in the following figure, the check result is Passed. Otherwise, go to the next step.

Figure 5-1 Viewing Huawei disk information

 

   Step 2      Run the esxcfg-mpath -b -d DeviceName command to obtain the path information of a specified LUN. Obtain information in the last column of the command output (WWN of the array controller port).

 

DeviceName is the information about naa.xxx queried as shown in Figure 5-1.

   Step 3      Convert each WWPN to a binary value and check the value of the 53nd to 56th bit. After the value is converted into a decimal number, the value indicates the controller ID, for example, controller 1 as shown in the following figure.

 

 

   Step 4      Based on the calculated controller IDs, check whether at least one available link exists between each LUN and controllers on the even plane (0, 2, 4, 6, 8, 10, 12, and 14) and those on the odd plane (1, 3, 5, 7, 9, 11, 13, and 15). If yes, you can perform an online upgrade. Otherwise, online upgrade cannot be performed.

----End

5.2 Windows

This section describes how to check redundant links for Windows.

5.2.1 Checking Redundant Links When UltraPath Is Used

   Step 1      Open the CMD command line interface (CLI) or run the cmd command on PowerShell to go to the CMD window. Run the upadm show version command to view the UltraPath version, as shown in the following figure. If no version information is displayed after the command is executed or a message is reported indicating that the command does not exist, UltraPath is not installed. In this case, the check result is Passed.

 

   Step 2      If the UltraPath version is 8.01.051 or earlier, run the upadm show vlun command. If the UltraPath version is later than 8.01.051, run the upadm show vlun type=all command, as shown in the following figure, to check values in the Vlun ID column.

 

 

   Step 3      Run the upadm show vlun id=[VLUN ID] (when the UltraPath version is 8.01.051 or earlier) or upadm show vlun vlun id =< VLUN ID > -t type=all (when the UltraPath version is later than 8.01.051) command to query path information about all LUNs.

   Step 4      View the VLUN path information to check whether available paths in the Normal state exist on controllers of the odd plane (controllers XB and XD for a single-engine four-controller device, and controller XB for a single-engine dual-controller device) and controllers of the even plane (controllers XA and XC for a single-engine four-controller device, and controller XA for a single-engine dual-controller device). If all controllers on both odd and even planes have available links, online upgrade can be performed. Otherwise, online upgrade cannot be performed.

----End

5.3 Linux

This section describes how to check redundant links for Linux.

5.3.1 Checking Redundant Links When UltraPath Is Used

   Step 1      Log in to the Linux host and run the upadm show version command to view the UltraPath version, as shown in the following figure.

 

   Step 2      If the UltraPath version is 5.01.017 or earlier, run the upadm show array command to query information about all disk arrays managed by UltraPath and obtain the value in the Array ID column. If the UltraPath software version is later than 5.01.017, go to Step 6.

 

   Step 3      Run the upadm show lun array=<Array ID> command based on the obtained Array ID to view the path information of all LUNs, as shown in the following figure.

 

   Step 4      Check the Controller xx information in the preceding step, for example, Controller 0A and Controller 0B. Check the value of NumLunObjects in the command output. If the value is greater than 0 and the value of DevState is OPTIMAL, there are available links on the controller.

   Step 5      Based on available links, check whether available paths exist on controllers of the odd plane (controllers XB and XD for a single-engine four-controller device, and controller XB for a single-engine dual-controller device) and controllers of the even plane (controllers XA and XC for a single-engine four-controller device, and controller XA for a single-engine dual-controller device). If all controllers on both odd and even planes have available links, online upgrade can be performed. Otherwise, online upgrade cannot be performed.

   Step 6      If the UltraPath version is later than 5.01.017, run the upadmin show vlun command (when the UltraPath version is 8.01.051 or earlier) or upadmin show show vlun type=all (when the UltraPath version is later than 5.01.017) to query information about all LUNs managed by UltraPath for Linux and to obtain values in the VLun ID column.

 

   Step 7      Run the upadm show vlun id=[VLUN ID] (when the UltraPath version is 8.01.051 or earlier) or upadm show vlun vlun id =< VLUN ID > -t type=all (when the UltraPath version is later than 8.01.051) command to query path information about all LUNs.

   Step 8      View the VLUN path information to check whether available paths in the Normal state exist on controllers of the odd plane (controllers XB and XD for a single-engine four-controller device, and controller XB for a single-engine dual-controller device) and controllers of the even plane (controllers XA and XC for a single-engine four-controller device, and controller XA for a single-engine dual-controller device). If all controllers on both odd and even planes have available links, online upgrade can be performed. Otherwise, online upgrade cannot be performed.

----End

5.3.2 Checking Redundant Links When Multipath Software Provided by Linux Is Used

   Step 1      Run the lsscsi command and obtain the target port number reported by the storage array based on the first column in the command output. Check whether disks mapped by Huawei storage exist based on the third column, as shown in the following figure.

 

   Step 2      Check whether there are disks mapped from Huawei storage devices based on the information displayed in the third column. The following types of disks (case insensitive) belong to Huawei storage devices: huawei|huasy|symantec|hs|eisoo|udsafe|marstor|sanm|anystor|sugon|netposa. If no Huawei device disk exists, skip this section.

   Step 3      After obtaining the Huawei disk list, classify the disks according to the first three digits in the first column. As shown in the preceding figure, there are four types of disks: 0:0:0, 0:0:1, 1:0:0, and 1:0:1, indicating the port numbers of different targets reported by the storage device.

   Step 4      Run the cat /sys/class/fc_transport/targetX:X:X/port_name command (X:X:X is the first three digits in the first column, which is 0:0:0, 0:0:1, 1:0:0, and 1:0:1 in this example) to query the target of the controllers connected to the host. The result obtained is a hexadecimal port name (WWPN), as shown in the following figure.

 

   Step 5      Convert each port name (WWPN) to a binary value and check the value of the 53nd to 56th bit. After the value is converted into a decimal number, the value indicates the controller ID, for example, controller 0 as shown in the following figure.

 

 

   Step 6      Based on the calculated controller IDs, check whether at least one available link exists between each LUN and controller even plane (0, 2, 4, 6, 8, 10, 12, and 14) and odd controller plane (1, 3, 5, 7, 9, 11, 13, and 15). If yes, you can perform an online upgrade. Otherwise, online upgrade cannot be performed.

----End

5.4 Solaris

This section describes how to check redundant links for Solaris

5.4.1 Checking Redundant Links When UltraPath Is Used

   Step 1      Log in to the Linux host and run the upadm show version command to view the UltraPath version, as shown in the following figure.

 

   Step 2      Run the upadm show vlun command (when the UltraPath version is 8.01.051 or earlier) or upadm show vlun type=all (when the UltraPath version is later than 8.01.051) to query information about all VLUNs managed by UltraPath. Obtain values in the VLun ID column, as shown in the following figure.

 

If "can't find any vlun" is displayed, UltraPath does not manage any Huawei disk. In this case, skip this section.

   Step 3      Run the upadm show vlun id=[VLUN ID] (when the UltraPath version is 8.01.051 or earlier) or upadm show vlun id=<VLun ID>  type=all (when the UltraPath version is later than 8.01.051) command to query path information about all LUNs, as shown in the following figure.

 

   Step 4      View the VLUN path information to check whether available paths in the Normal state exist on controllers of the odd plane (controllers XB and XD for a single-engine four-controller device, and controller XB for a single-engine dual-controller device) and controllers of the even plane (controllers XA and XC for a single-engine four-controller device, and controller XA for a single-engine dual-controller device). If all controllers on both odd and even planes have available links, online upgrade can be performed. Otherwise, online upgrade cannot be performed.

----End

5.4.2 Checking Redundant Links When Multipath Software Provided by Solaris Is Used

   Step 1      Run the mpathadm list lu|grep rdsk command to obtain the disks managed by STMS, as shown in the following figure.

 

If no command output is displayed, no disk is managed by STMS. In this case, skip this section.

   Step 2      For each STMS disk, run the mpathadm show lu /dev/rdsk/XXXX command to check whether Vendor is HUAWEI, as shown in the following figure.

 

• If the Vendor field is any of the following (case-insensitive), the disk is a Huawei disk. Otherwise, it is not a Huawei disk: huawei|huasy|symantec|hs|eisoo|udsafe|marstor|sanm|anystor|sugon|netposa
• If all disks are not Huawei disks, skip this section.

   Step 3      Check values of Target Port Name under Paths. Convert each port name (WWPN) to a binary value and check the value of the 53nd to 56th bit. After the value is converted into a decimal number, the value indicates the controller ID, for example, controller 0, as shown in the following figure.

 

   Step 4      Based on the calculated controller IDs, check whether at least one available link exists between each LUN and controller even plane (0, 2, 4, 6, 8, 10, 12, and 14) and odd controller plane (1, 3, 5, 7, 9, 11, 13, and 15). If yes, you can perform an online upgrade. Otherwise, online upgrade cannot be performed.

----End

5.5 HP_UX

This section describes how to check redundant links for HP_UX. Huawei UltraPath does not support HP_UX. This section describes only the check method for multipath software provided by HP_UX.

5.5.1 Checking Redundant Links When Multipath Software HP_UX 11i V1/V2 PVlinks Is Used

   Step 1      Log in to the host and run the uname -a command, for example. The information in red indicates the system version, B.11.11 indicates HP-UX 11i v1, B.11.23 indicates HP-UX 11i v2, and B.11.31 indicates HP-UX 11i v3.

 

   Step 2      If the version is HP-UX 11i v1/v2, that is, B.11.11 or B.11.23, go to the next step. Otherwise, skip this section.

   Step 3      Run the ioscan -fnC fc command to obtain values of H/W Path for HBAs of the current HP-UX system.

 

   Step 4      Run the ioscan -funC disk command to obtain the mapped disk device list. Obtain the device whose H/W Path value is the same as that obtained in the previous step and Description value contains HUAWEI. For example: /dev/dsk/c23t0d2, as shown in the following figure.

 

   Step 5      After obtaining the device information, run the pvdisplay xxx| grep 'PV Name' command. In the command, xxx indicates the device name obtained in the previous step, for example, /dev/dsk/c23t0d2. If the command output contains Alternate Link, the disk has no redundant links and no further check is required.

 

   Step 6      Run the fcmsutil /dev/xxx get remote all | grep 'Target Port Word Wide Name' command in sequence based on the driver information obtained in step 3. xxx indicates the driver name. Then query the information about the target connected to the port, as shown in the following figure.

 

   Step 7      Check values of Target Port World Wide Name. Convert each port name (WWN) to a binary value and check the value of the 53nd to 56th bit. After the value is converted into a decimal number, the value indicates the controller ID, for example, controller 0, as shown in the following figure.

 

   Step 8      Based on the calculated controller IDs, check whether at least one available link exists between each LUN and controller even plane (0, 2, 4, 6, 8, 10, 12, and 14) and odd controller plane (1, 3, 5, 7, 9, 11, 13, and 15). If yes, you can perform an online upgrade. Otherwise, online upgrade cannot be performed.

----End

5.5.2 Checking Redundant Links When Multipath Software HP_UX 11i V3 NMP Is Used

   Step 1      Log in to the host and run the uname -a command. The information in red indicates the system version, B.11.11 indicates HP-UX 11i v1, B.11.23 indicates HP-UX 11i v2, and B.11.31 indicates HP-UX 11i v3.

 

   Step 2      If the value is HP-UX 11i v3, that is, B.11.31, run the scsimgr get_attr -a leg_mpath_enable command to check whether the NMP multipath software is installed and enabled, as shown in the following figure. If both current and default are true, NMP is installed and enabled. Otherwise, the check is complete.

 

   Step 3      Run the ioscan -funNC disk command to obtain information about all disks on the host. Then obtain the disks of Huawei and CLAIMED based on the Description and S/W State fields, as shown in the following figure.

 

• If the Description field is any of the following (case-insensitive), the disk is a Huawei disk. Otherwise, it is not a Huawei disk: huawei|huasy|symantec|hs|eisoo|udsafe|marstor|sanm|anystor|sugon|netposa
• If all disks are not Huawei disks, skip this section.

   Step 4      Run the ioscan -P health | grep lunpath command to obtain all online LUN WWPNs, as shown in the following figure.

 

   Step 5      Run the scsimgr lun_map -D xxx command (xxx indicates the Huawei CLAIMED disk obtained in step 3) to obtain the disk path information, as shown in the following figure.

 

   Step 6      Check each LUN path and convert the WWN under Hardware path whose State and Last Open or Close state is ACTIVE to a binary value and check the value of the 53nd to 56th bit. After the value is converted into a decimal number, the value indicates the controller ID, for example, controller 0 as shown in the following figure.

 

   Step 7      Based on the calculated controller IDs, check whether at least one available link exists between each LUN and controller even plane (0, 2, 4, 6, 8, 10, 12, and 14) and odd controller plane (1, 3, 5, 7, 9, 11, 13, and 15). If yes, you can perform an online upgrade. Otherwise, online upgrade cannot be performed.

----End

5.6 AIX

This section describes how to check redundant links for AIX. In the AIX operating system, the method of checking UltraPath is the same as that for checking the multipathing software provided by the AIX system.

   Step 1      Run the lsdev -Cc disk | grep FC command on the active node to obtain hdiskx of all disks taken over by the host, as shown in the following figure.

 

If no disk is found, the check result is Passed and no further check is required.

   Step 2      Run the lscfg -vpl hdisk1 command (for example, hdisk1) to obtain disk information one by one. Check whether the disk is a Huawei disk based on the Manufacturer field, and record the Huawei disk information, as shown in the following figure.

 

• If the Manufacturer field is any of the following (case-insensitive), the disk is a Huawei disk. Otherwise, it is not a Huawei disk: huawei|huasy|symantec|hs|eisoo|udsafe|marstor|sanm|anystor|sugon|netposa
• If all disks are not Huawei disks, skip this section.

   Step 3      For each Huawei disk, run the lspath -F "name:parent:connection:path_id:status" -l hdisk1 command (hdisk1 is used as an example) to obtain the path information, as shown in the following figure.

 

   Step 4      Convert each port name (WWN) whose path status is Enabled to a binary value and check the value of the 53nd to 56th bit. After the value is converted into a decimal number, the value indicates the controller ID, for example, controller 0 as shown in the following figure.

 

   Step 5      Based on the calculated controller IDs, check whether at least one available link exists between each LUN and controller even plane (0, 2, 4, 6, 8, 10, 12, and 14) and odd controller plane (1, 3, 5, 7, 9, 11, 13, and 15). If yes, you can perform an online upgrade. Otherwise, online upgrade cannot be performed.

----End