Thanks buddy for your compliments ... My comments are in-lined in ur below mail . -Jason.
--- On Tue, 29/7/08, vprabu vprabu <[EMAIL PROTECTED]> wrote: From: vprabu vprabu <[EMAIL PROTECTED]> Subject: Re: [cbe-linux] Steps To Configure SAN disk in RHEL4 & 5 To: cbe-linux@yahoogroups.com Date: Tuesday, 29 July, 2008, 11:06 PM Jason ... you rock :-) So if my understanding is right... 1) First the devices(LUN' s ) are to be detected by HBA's We do this by scaning BOTH the HBA's using qla-scan 2) We can find the new LUNs in /proc/scsi/qla200/ 0 /proc/scsi/qla200/ 1 (Id:Lun) * - indicates lun is not registered with the OS. ( 0: 0): Total reqs 1, Pending reqs 0, flags 0x0*, 0:0:81, ( 0:15): Total reqs 0, Pending reqs 0, flags 0x0*, 0:0:81, If a new LUN is added, after a scan i may see something like (0:16): Total reqs 0, Pending reqs 0, flags 0x0*, 0:0:81, where 0 is the target ID and 16 is LUN ??????? (( echo 1 > /sys/class/fc_ host/hostn/ issue_lip echo "- - -" > /sys/class/scsi_ host/host2/ scan works for upstream kernels ) 3) echo scsi add-single-device 2 0 0 16 > /proc/scsi/scsi so the new LUN discovered at HBA 2, BUS 0, TARGET 0, LUN ID 16 will be understood by the kernel/OS ?# 4) Now we do a normal fdisk.... ( Okay.. Jason please let me know 1) how HBA , LUN order is persistent. where is this information stored. - In Linux mostly HBA and LUN order is Persistant ( by default) , it will be stored in /proc/scsi/<Driver Name > and /etc/modules.conf 2) how are the naming conventions done on the newly added scsi LUN. Assume my first INTERNAL DISK was sda. - The Newly added device might be appear you as sdb how will be the new LUN's named. ( This question may sound silly to you :-) ) - LUN is basically named or idendified by WWW number( 16 digit ) which will communicate with SAN switch and Disk. Anyways. Your document was very useful. cbe-linux guys...give a applause for Jason Thanks --- On Tue, 7/29/08, azariah jason <smart_jazzi@ yahoo.co. in> wrote: From: azariah jason <smart_jazzi@ yahoo.co. in> Subject: Re: [cbe-linux] Steps To Configure SAN disk in RHEL4 & 5 To: [EMAIL PROTECTED] ps.com Date: Tuesday, July 29, 2008, 8:21 PM Hey, Here you go... Make sure that newly configured LUN's are properly configured and mapped to correct HBA's 2. If you have installed SANsurfer GUI/CLI, make sure newly added LUN's are visible from these tools 3. For each QLogic HBA installed in the system, do the following: a. Determine the host ID (H) associated with the HBA. Each installed HBA has a numeric filename that is the host identifier. # /bin/ls /proc/scsi/qla2300 b. Rescan for all the LUNs on all the ports. H is the host identifier associated with HBA. # /bin/echo scsi-qlascan > /proc/scsi/qla2300/ H c. Determine the target ID (T) associated with the new LUN. This file lists the ID:LUN numbers recognized by the QLA driver. T is the target ID value. # /bin/cat /proc/scsi/qla2300/ H d. Add the LUN to HBA. H is the host identifier associated with the HBA; T is the target identifier obtained in Step c; and L is the LUN identifier. # /bin/echo scsi add-single-device H 0 T L > /proc/scsi/scsi 4. use "/sbin/fdisk -l" to verify if the newly added LUN is visible to the OS 5. use InfoDoc 85804 "How to create a new partition table under Redhat Linux" for creating properly a partition and a file system on the LUN Find below example illustrating addition of a newly mapped T4 lun on RedHat Linux using QLA driver version 7.07.04 ============ ========= ========= ========= ========= ========= ========= ========= 1) Determine host ID [EMAIL PROTECTED] root]# /bin/ls /proc/scsi/qla2300/ 2 2) Re-scan for LUN's on both HBA's [EMAIL PROTECTED] root]# /bin/echo scsi-qlascan > /proc/scsi/qla2300/ 2 3) Verify newly mapped LUN's [EMAIL PROTECTED] root]# /bin/cat /proc/scsi/qla2300/ 2 QLogic PCI to Fibre Channel Host Adapter for QLA2342: Firmware version: 3.03.19, Driver version 7.07.04 Entry address = f88ae060 HBA: QLA2312 , Serial# F05179 Request Queue = 0x377e0000, Response Queue = 0x377d0000 Request Queue count= 512, Response Queue count= 512 Total number of active commands = 0 Total number of interrupts = 35 Total number of active IP commands = 0 Total number of IOCBs (used/max) = (0/600) Total number of queued commands = 0 Device queue depth = 0x20 Number of free request entries = 510 Number of mailbox timeouts = 0 Number of ISP aborts = 0 Number of loop resyncs = 2 Number of retries for empty slots = 0 Number of reqs in pending_q= 0, retry_q= 0, done_q= 0, scsi_retry_q= 0 Host adapter:loop state= <READY>, flags= 0x820813 Dpc flags = 0x0 MBX flags = 0x0 SRB Free Count = 4096 Link down Timeout = 000 Port down retry = 030 Login retry count = 030 Commands retried with dropped frame(s) = 0 Configured characteristic impedence: 50 ohms Configured data rate: 1-2 Gb/sec auto-negotiate SCSI Device Information: scsi-qla0-adapter- node=200100e08b2 75bb5; scsi-qla0-adapter- port=210100e08b2 75bb5; scsi-qla0-target- 0=20030003ba27cf a2; SCSI LUN Information: (Id:Lun) * - indicates lun is not registered with the OS. ( 0: 0): Total reqs 1, Pending reqs 0, flags 0x0*, 0:0:81, ( 0:15): Total reqs 0, Pending reqs 0, flags 0x0*, 0:0:81, Note "*" in the above outputs, which indicates lun as not registered with OS, hence not visible to OS. 4) Register the new LUN's with OS # /bin/echo scsi add-single-device 2 0 0 15 > /proc/scsi/scsi 5) verify from OS using "fdisk -l" [EMAIL PROTECTED] root]# /sbin/fdisk -l Disk /dev/sda: 36.4 GB, 36420075008 bytes 255 heads, 63 sectors/track, 4427 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/sda1 * 1 13 104391 83 Linux /dev/sda2 14 4173 33415200 83 Linux /dev/sda3 4174 4427 2040255 82 Linux swap Disk /dev/sdb: 5372 MB, 5372116992 bytes 255 heads, 63 sectors/track, 653 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/sdb1 1 653 5245191 83 Linux In the above output 'sdb' is the new LUN, which was partitioned earlier Thanks Jason. --- On Tue, 29/7/08, vprabu vprabu <prabu_online2005@ yahoo.com> wrote: From: vprabu vprabu <prabu_online2005@ yahoo.com> Subject: [cbe-linux] Steps To Configure SAN disk in RHEL4 & 5 To: [EMAIL PROTECTED] ps.com Date: Tuesday, 29 July, 2008, 3:34 PM Please provide simple and detailed steps by step instruction for 1) Detecting SAN device using Qlogic aswell as Emulex HBA's 2) Creating Psuedo device with Powermt / Device Mapper [Non-text portions of this message have been removed] Unlimited freedom, unlimited storage. Get it now, on http://help. yahoo.com/ l/in/yahoo/ mail/yahoomail/ tools/tools- 08.html/ [Non-text portions of this message have been removed] [Non-text portions of this message have been removed] Connect with friends all over the world. Get Yahoo! India Messenger at http://in.messenger.yahoo.com/?wm=n/ [Non-text portions of this message have been removed]
