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.


Overlapped LUN IDs Cause that LUN Links Are in the Down State on an Application Server

Publication Date:  2013-05-23 Views:  323 Downloads:  0

Issue Description

Product and version information:
  • S2600
  • S5000 series
  • The operating system of application servers running Linux or UNIX.
A storage device and an application server use the switch networking mode (Fibre Channel switches). Two initiators of the application server are added to Host1 and Host2 respectively on the storage device. After the upTools –S command is executed to check the LUN link status, Path State is displayed as Down.
Figure 1-1 shows the switch networking mode.
Figure 1-1 Switch networking mode

After the LUN status of the storage device is checked, the health status of LUNs is normal.
After host LUN IDs of LUNs mapped to the application server are checked, overlapped host LUN IDs exist.

Alarm Information


Handling Process

Step 1 Stop services on a host such as Host1.
Step 2 Delete initiators and LUN mappings on Host1.
Step 3 Add the deleted initiators and LUN mappings to Host2.
Step 4 On the application server, run the upTools –S command to check the LUN link status. Under normal conditions, the LUN link status is UP.

Root Cause

Host LUN IDs of LUNs mapped to the application server are overlapped.


You are advised to add all initiators of an application server to the same host on a storage device. Otherwise, host LUN IDs may be overlapped when LUN mappings are allocated. If host LUN IDs are overlapped, the link status of LUNs detected on the application server will be abnormal.