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>

Reminder

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

upgrade

The initiation sequence of the iSCSI service is error causes the application server can’t mount the mapped LUN

Publication Date:  2012-11-23 Views:  31 Downloads:  0
Issue Description
In the ISM, the LUN has been mapped to the application server successfully, but after the application server has started, it can’t mount the LUN mapped from the storage system.

Alarm Information
None
Handling Process
Step 1. Execute the “” command to open the configuration file of the operating system.
Step 2. Press the “i” key and enter in to the VI’s file editing status.
Step 3. Add a new column in the end of the file, the content is “/etc/rc.local” or “bin/mount -a”.
Step 4. Press the “Esc” to exit from the VI’s editing mode.
Step 5. Enter “:wq” to save the file and quit the VI.
Step 6. Restart the application server, and then it can mount the LUN mapped from the storage system.
Root Cause
1. Enter in the application server operating system’s CLI mode.
2. Execute the “vi /etc/profile” command, and then open the configuration file of the operating system.
3. Confirm there isn’t contained the “/etc/rc.local” or “/bin/mount -a” in this file.
So, we conclude it is the wrong initiation sequence of the iSCSI service that causes the application server can’t mount the mapped LUN after it has started.

Suggestions
None

END