Experience Sharing: configure the fabercard for linux + msl6030 + eva4000
Source: Internet
Author: User
Experience Sharing: For more information about how to configure a fiercard for linux + msl6030 + eva4000-Linux Enterprise Application-Linux server application, see the following. Experience Sharing: linux + msl6030 + eva4000 Configuration
Linux + msl6030 + eva4000 ConfigurationI have been doing an installation for the past few days. I have encountered some things that I haven't met before and I want to share them with you. I hope you don't think I am in the class. Environment: san structure, msl6030 * 1 + eva4000 * 1 * linux
Blade * 24
Requirement: the customer requires that the vdisks with libraries and eva be visible on each linux blade, and the path should be merged.
Steps:
1. Install the driver of the optical fiber card View the card model from the hardware manager of linux, and download the driver hp_qla2x00.rar for linuxon the hp website. After decompression, open readme.txt and follow the prompts to go through the following steps:
[Root @ idc] #./install? F (failover mode)
[Root @ idc] # cd/opt/hp/src/hp_qla2x00src is automatically generated after installation
[Root @ idc] #./master. sh? L
2.6.9-5.EL 2.6.9-5. ELsmp
[Root @ idc] #./master. sh-s linux-2.6.9-5.EL-m linux-2.6.9-5.EL smp (match new kernel)
OK. The driver is installed. It's easy. If there is any problem, you can take a closer look at the error message and the readme in the driver file.
2. Configure the msl6030 Library It's just getting on, changing, and configuring a configuration that everyone on Earth knows. The words are omitted here.
3. Install the following rmp packages on a linux machine: Sg3_utils-1.06-3.i386.rpm mtx-1.2.18-5.i386.rpm
It is reasonable to say that after the installation, the machine will automatically find the belt library after the restart, but it won't work if it is restarted several times. No way, my brother, I only have a yellow hand:
[Root @ idc] # cd/etc/rc. d/init. d
[Root @ idc] # vi msl6030
In msl6030, write:
#! /Bin/sh
# Chkconfig: 2345 80 05
# Descr resume ption: For rescan MSL and add drive module
Case "$1" in
"Start ")
/Opt/hp/hp_fibreutils/hp_rescan-
Insmod/lib/modules/2.6.9-5. ELsmp/kernel/drivers/scsi/sg. ko
;;
"Stop ")
;;
Esac
[Root @ idc] # chmod 755 msl6030
[Root @ idc] # chkconfig -- add msl6030
[Root @ idc] # chkconfig -- list | grep msl
Msl6030 0: off 1: off 2: on 3: on 4: on 5: on 6: off
Sci2 00
00 00 hp hsv 5031 RAID
Sci2 00
00 01 hp hsv 5031 Direct-Access
Sci2 00
01 00 hp hsv 5031 RAID
Scsi3 00
00 00 HP MSL6000 0513 Medium
Scsi3 00
01 00 hp hsv 5031 RAID
Scsi3 00
03 00 hp hsv 5031 RAID
Scsi3 00
00 01 HP Ultrium F59W Sequential-Access
Scsi3 00
00 02 HP Ultrium F59W Sequential-Access
Scsi3 00
00 03 hp ns 567a RAID
Check, find the database with and eva, restart the database, and check again. All OK items can be viewed by running the "User-Agent" command using the "User-Agent-agent" command (same as the mc command in unix)
[Root @ idc
~] # Maid status
Storage
Changer/dev/sg5: 2 Drives, 28 Slots (0 Import/Export)
Data
Transfer Element 0: Empty
Data
Transfer Element 1: Empty
Storage Element 1: Full: VolumeTag = SCH436L2
Storage Element 2: Full: VolumeTag = SCH437L2
Storage Element 3: Full: VolumeTag = SCH438L2
Storage Element 4: Full: VolumeTag = SCH439L2
Storage Element 5: Full: VolumeTag = SCH440L2
Storage Element 6: Full: VolumeTag = SCH441L2
Storage Element 7: Full: VolumeTag = SCH442L2
Storage Element 8: Full: VolumeTag = SCH443L2
Storage Element 9: Full: VolumeTag = SCH444L2
Storage Element 10: Full: VolumeTag = SCH445L2
Storage Element 11: Full: VolumeTag = SCH446L2
Storage Element 12: Full: VolumeTag = SCH447L2
Storage Element 13: Empty
Storage Element 14: Empty
Storage Element 15: Empty
Storage Element 16: Empty
Storage Element 17: Empty
Storage Element 18: Empty
Storage Element 19: Empty
Storage Element 20: Empty
Storage Element 21: Empty
Storage Element 22: Empty
Storage Element 23: Empty
Storage Element 24: Empty
Storage Element 25: Empty
Storage Element 26: Empty
Storage Element 27: Empty
Storage Element 28: Full: VolumeTag = SCH448L2
View the device file: [root @ idc
~] # Sg_map
/Dev/sg0
/Dev/sda
/Dev/sg1
/Dev/sdb
/Dev/sg2
/Dev/sg3
/Dev/sdc
/Dev/sg4
/Dev/sg5
/Dev/sg6
/Dev/sg7
/Dev/sg8
/Dev/st0
/Dev/sg9
/Dev/st1
/Dev/sg10
4. There is only one link in the vdisk divided by eva in linux., ^_^ [Root @ idc ~] # Fdisk/dev/sda is followed by basic lvm operations. Pai_^
The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion;
products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the
content of the page makes you feel confusing, please write us an email, we will handle the problem
within 5 days after receiving your email.
If you find any instances of plagiarism from the community, please send an email to:
info-contact@alibabacloud.com
and provide relevant evidence. A staff member will contact you within 5 working days.