# lspci | grep -i emulex
05:0d.0 Fibre Channel: Emulex Corporation LP9802 Fibre Channel Host Adapter (rev 01)
#
# cat /sys/class/scsi_host/host0/fwrev
1.90A4 (H2D1.90A4)
#
# cat /sys/class/scsi_host/host0/node_name
0x20000000c94f7dd9
#
# cat /sys/class/scsi_host/host0/port_name
0x10000000c94f7dd9
#
# cat /sys/class/scsi_host/host0/lpfc_drvr_version
Emulex LightPulse Fibre Channel SCSI driver 8.0.16.27
#
# cat /sys/class/scsi_host/host0/serialnum
MS54376943
#
# cat /sys/class/scsi_host/host0/speed
2 Gigabit
#
# cat /sys/class/scsi_host/host0/state
Link Up - Ready:
Fabriccat /etc/redhat-release
[root@localhost ~]# cd /sys/class/scsi_host/host1/device/fc_host\:host1/
[root@localhost fc_host:host1]# more port_name
0x10000000c96dffce
===========
How to identify/get QLogic WWN on Red Hat Enterprise Linux 5 (RHEL5).
First identify your installed or recognized
# lspci | grep -i fibre
04:00.0 Fibre Channel: QLogic Corp. ISP2432-based 4Gb Fibre Channel to PCI Express HBA (rev 03)
04:00.1 Fibre Channel: QLogic Corp. ISP2432-based 4Gb Fibre Channel to PCI Express HBA (rev 03)
05:00.0 Fibre Channel: QLogic Corp. ISP2432-based 4Gb Fibre Channel to PCI Express HBA (rev 03)
05:00.1 Fibre Channel: QLogic Corp. ISP2432-based 4Gb Fibre Channel to PCI Express HBA (rev 03)
On Red Hat Enterprise Linux 5 (5.x) is on /sys/class/fc_host/hostX/port_name
(X is your device 1,2,3,…N)
For get use:
cat /sys/class/fc_host/hostX/port_name
Sample with multiple HBA (Fibre) QLogic
# ls /sys/class/fc_host/
host3 host4 host5 host6
# cat /sys/class/fc_host/host[3-6]/port_name
0x2100001b32936e24
0x2101001b32b36e24
0x2100001b32932821
0x2101001b32b32821
On Red Hat Enterprise Linux 4 (AS/ES) is on /proc/scsi/qla2xxx/1 (1,2,3,..N)
Sample:
# egrep [node|port] /proc/scsi/qlx2xxx/0
scsi-qla0-adapter-node=200000e08b1c19f2;
scsi-qla0-adapter-port=210000e08b1c19f2;
======================
# ls /sys/class/fc_host
host0 host1 host2 host3
fdisk -l 2>/dev/null | egrep '^Disk' | egrep -v 'dm-' | wc -l
echo "1" > /sys/class/fc_host/host0/issue_lip
echo "- - -" > /sys/class/scsi_host/host0/scan
echo "1" > /sys/class/fc_host/host1/issue_lip
echo "- - -" > /sys/class/scsi_host/host1/scan
echo "1" > /sys/class/fc_host/host2/issue_lip
echo "- - -" > /sys/class/scsi_host/host2/scan
echo "1" > /sys/class/fc_host/host3/issue_lip
echo "- - -" > /sys/class/scsi_host/host3/scan
cat /proc/scsi/scsi | egrep -i 'Host:' | wc -l
fdisk -l 2>/dev/null | egrep '^Disk' | egrep -v 'dm-' | wc -l
== delete LUN ==
#echo 1 > /sys/block/sdb/device/delete
#echo 1 > /sys/block/sdd/device/delete
================
===============
How to rescan LINUX OS for new Storage with Emulex HBA card
by Kumar on September 9, 2011
1.How to rescan the new Storage in RHEL4/RHEL5 with Emulex HBA Cards
In order to get the fiber channel adapters detail to rescan, list the /sys/class/fc_host directory. In old RHEL 4 host you will not be getting this listing. In this case you can use the /sys/class/scsi_host directory but it will list all internal adapters too.
# ls -l /sys/class/fc_host
total 0
drwxr-xr-x 3 root root 0 Jul 9 02:37 host0
drwxr-xr-x 3 root root 0 Jul 9 02:37 host1
#echo "1" > /sys/class/fc_host/host1/issue_lip
#echo "1" > /sys/class/fc_host/host2/issue_lip
#echo "- - -" > /sys/class/scsi_host/host1/scan
#echo "- - -" > /sys/class/scsi_host/host2/scan
2. After rescanning, confirm whether you are seeing the new storage disks[LUN] by listing the content under proc
cat /proc/scsi/scsi or cat /proc/scsi/scsi | grep scsi | uniq
3. If you are using powerpath for multipathing, run the below command to scan the powerpath to get the newly added storage devices under powerpath control
powermt config
4. Then Check the newly added device under powerpath using the below command.
powermt display dev=all
5.If you are using device mapper multipathing, run the below command to scan the DMP to get the newly added storage devices under Linux DMP control
multipath -v1
multipath -v2
6.Then Check the newly added device under Linux DMP using the below command.
multipath -ll
=================
How to scan newly added LUN using rescan-scsi-bus.sh ?
ENV : RHEL 5.4 and later
I suggest you NOT to scan the existing LUNs since I/O operations are still in use and if you scan them it will/may corrupt the file system.
So, I always suggest you to scan the new added device or storage. Once you add it,
HBA will detect the device and then you can scan this non-existent LUNs to the HBA. As an example you can execute the command like :
---
#rescan-scsi-bus.sh --hosts=1 --luns=2
---
Note : I assume that on host 1/or on HBA 1, lun 2 doesn't exist.
For more details please get help from :
---
#rescan-scsi-bus.s --help
http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5/html/Online_Storage_Reconfiguration_Guide/rescan-scsi-bus.html
================
Here are outputs for commands:
# uname -a
Linux 64-cncrclinrpts 2.6.38-11-generic-pae #48-Ubuntu SMP Fri Jul 29 20:51:21 UTC 2011 i686 i686 i386 GNU/Linux
# file jasperreports-server-cp-4.1.0-linux-x64-installer.run
jasperreports-server-cp-4.1.0-linux-x64-installer.run: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.4.0, stripped
# ldd -r jasperreports-server-cp-4.1.0-linux-x64-installer.run
not a dynamic executable
== install CCI==
cd /
cpio -idmu < ./program/RM/HP-UX/RMHORC
/HORCM/horcminstall.sh
=============
This version supports hot adding new luns, etc. Please see text below on how
to perform the lun hot add procedure. The latest driver-v7.00.60-fo has the
mechanism which allows the user to force the driver to do re-scan of the
devices to allow a new device to be added. This triggers the driver to
initiate lun discovery process.
To do this from the command line:
#echo "scsi-qlascan" > /proc/scsi/<driver-name>/<adapter-id> (qlogic
driver will re-scan)
Where <driver-name> can be either one : qla2100/qla2200/qla2300 <adapter-id>
~ is the instance number of the HBA.
Once that has been done , user then can force the scsi mid layer to do
its own scan
and build the device table entry for the new device:
# echo "scsi add-single-device 0 1 2 3" >/proc/scsi/scsi
(scsi mid layer will re-scan) with "0 1 2 3"
replaced by your "Host Channel Id Lun". The scanning has to be done in
the above mentioned order.
First the driver (qla2300/qla2200 driver etc) and then the Linux scsi
mid layer.
---schnipp---
You take a look into "dmesg | less" and search for the information about
"Host Channel Id Lun", the Lun you have to know, from the Storage
Administrator.
echo "scsi-qlascan" > /proc/scsi/qla2200/1
echo "scsi-qlascan" > /proc/scsi/qla2200/2
echo "scsi add-single-device 1 0 0 6" >/proc/scsi/scsi
than take a look into "cat /proc/partions" if the pation is not there
you can do a "partprobe" (man partprobe).
==================
+ Multi Path
==================
#cat /etc/multipath.conf
multipaths {
multipath {
wwid 360060e80105425e0056fcaee0000000d
alias tuan
}
}
defaults {
user_friendly_names yes
}
blacklist {
devnode "sda"
}
# multipath -ll
tuan (360060e80105425e0056fcaee0000000d) dm-2 HITACHI,DF600F
[size=100G][features=0][hwhandler=0][rw]
\_ round-robin 0 [prio=1][active]
\_ 1:0:0:0 sdb 8:16 [active][ready]
\_ round-robin 0 [prio=0][enabled]
\_ 2:0:0:0 sdc 8:32 [active][ready]
==============
This blog post is also available as a TechRepublic download in PDF form.Internet Small Computer System Interface (iSCSI) has taken the storage world by storm. No longer is shared storage a niche enjoyed by only large, wealthy corporations. Internet SCSI is leveling the playing field by making shared storage available at a reasonable cost to anyone. By leveraging the ubiquitous Ethernet networks prevalent in most organizations, IT staff training costs for iSCSI are very low and result in quick, seamless deployments.
Further, operating system vendors are making it easier than ever to get into the iSCSI game by making iSCSI initiator software freely available. iSCSI networks require three components:
- An iSCSI target — A target is the actual storage array or volume, depending on how you have things configured.
- An iSCSI initiator — An iSCSI initiator is the software component residing on a server or other computer that is installed and configured to connect to an iSCSI target. By using an iSCSI initiator, target-based volumes can be mounted on a server as if they were local volumes and are managed as such.
- A gigabit Ethernet network infrastructure — iSCSI requires an IP-based Ethernet network for its transport between systems with initiators (servers) and targets (storage arrays).
Step 1: Set up your target and communications infrastructure
Before you install the iSCSI initiator on any of your servers or workstations, you must have something to which the initiator will connect. This can be one of the enterprise class arrays, such as those available from LeftHand, EqualLogic, Dell, or EMC or, if you’re on a tighter budget and want to build your own array, a target running iSCSI target software, such as StarWind. For more information about building a SAN on the cheap, take a look at:- For the small IT shop: Building a SAN on the cheap
- iSCSI on the cheap: Turn your Windows server into an iSCSI storage target
Setting up and configuring your target is beyond the scope of this article.
Step 2: Configure your local iSCSI network adapter
One best practice is to assign either a dedicated gigabit Ethernet NIC or TCP offload adapter (ToE adapter) in each server to handle iSCSI traffic — in other words, don’t share your user-facing network connection for storage traffic. If you’ve created a separate physical network or VLAN for storage traffic, assign this adapter an IP address that works on the storage network. By placing storage traffic on its own network that is routed separately from the main network, you increase the overall security of your storage infrastructure and simplify the overall configuration.Step 3: Download Microsoft’s iSCSI initiator — if necessary
Depending on the operating system you’re using, you may need to download Microsoft’s iSCSI initiator software. If you’re planning to connect to an iSCSI target from a Windows XP or Windows Server 2003 system, visit Microsoft’s iSCSI initiator download page and obtain the software. If you’re connecting from a Windows Vista or Windows Server 2008 computer, Microsoft’s iSCSI initiator is included with these operating systems, so you can safely skip this step.Make sure to download the initiator that is designed for your operating system. Microsoft provides builds for both 32-bit and 64-bit Windows. In the 64-bit category, versions are available for both x64-based processors and Itanium-based processors.
Step 4: Install the iSCSI initiator
If you’re running an operating system on which the iSCSI initiator software is not installed, execute the file you downloaded and follow the installation instructions (Figure A). The installer will ask you to decide which components you would like to install.Figure A
Choose your installation options.
- Initiator service — This is the service behind the actual work.
- Software initiator — The software initiator is the software service that handles iSCSI traffic.
- Microsoft MPIO Multipathing Support for iSCSI — MPIO is a way that you can increase the overall throughput and reliability of your iSCSI storage environment. See Step 6 for more information about how MPIO can be of benefit.
Step 5: Connect to the iSCSI array
Now that you have the initiator software installed, you need to tell it where to look for mountable volumes. Start the initiator configuration by going to the Control Panel and choosing the iSCSI Initiator option. From the initiator, choose the Discovery tab, shown in Figure B.Figure B
The iSCSI initiator’s Discovery tab.
On the Discovery tab, click the Add button under the Target Portals box. This will open the Add Target Portal dialog box, shown in Figure C.Figure C
The Add Target Portal dialog box.
In the Add Target Portal dialog box, provide the name or IP address of your iSCSI array. The default communication port for iSCSI traffic is 3260. Unless you have changed your port, leave this as is. If you have configured CHAP security or are using IPSec for communication between your client and the array, click on the Advanced button and make necessary configuration changes. The Advanced Settings dialog box is shown in Figure D.Figure D
Advanced options for connecting to your iSCSI array.
Back on the Add Target Portal, click the OK button to make the initial connection to the iSCSI array. Note that, at this point, you’re not connecting to an actual volume, but only to the array in general. (Figure E)Figure E
The target portal has been added to the initiator.
Step 6: Connect to a target/volume
Even though you’re connected to the array itself, you still need to tell the initiator exactly which target or volume you want to mount on your local machine. To see the list of available targets on the array you selected, choose the Targets tab, shown in Figure F.Figure F
The iSCSI initiator Target tab in this example has only a single volume available.
To connect to an available target, choose the target and click the Log On button. A window pops up (Figure G) with the target name and two options from which you can choose.Figure G
iSCSI target Log On options.
The two options are important. If you want your server to connect to this volume automatically when your system boots, make sure you choose the Automatically Restore This Connection When The System Boots check box. Unless you have a good reason otherwise, you should always select this check box. If you do not, you can’t make the iSCSI target persistent after a reboot and will need to manually reconnect it.To enable high availability and to boost performance, choose the Enable Multi-path check box. Make sure to understand that multi-pathing (MPIO) requires multiple network adapters dedicated to the iSCSI task, and for maximum availability, you should also have a fully meshed gigabit Ethernet architecture for your storage traffic.
Again, if you are using CHAP or IPSec for communication with a target, click the Advanced button to bring up the Advanced Settings dialog box you saw in Figure D.
Once you finish making decisions regarding how you want to connect to your target, from the Log On To Target window, click the OK button. The target status in the imitator window should change to Connected. (Figure H)
Figure H
The target is now connected.
Step 7: Bind the targets
Now, you have successfully connected to a shared target on your iSCSI array. If you selected the Automatically Restore This Connection When The System Boots check box as explained in the previous step, you can now add the target to the iSCSI service’s binding list. By doing so, you make sure that Windows does not consider the iSCSI service fully started until connections are restored to all volumes on the binding list. This is important if you have data on an iSCSI target that other services depend on. For example, if you create a share on your server and that shared data resides on an iSCSI target, the Server service that handles the share depends on the iSCSI service’s complete availability to bring up the shares.Note: With older versions of the iSCSI initiators, creating this kind of dependency structure required you to reconfigure individual service dependencies — a process that could get complicated. With the iSCSI Initiator version 2, Microsoft has fixed this issue, but you still need to bind the targets.
The best option is to choose the Bound Volumes/Devices tab from the iSCSI Initiator’s control panel and click the Bind All button at the bottom of the window (Figure I). This will bind all available iSCSI targets (that can be bound) to the iSCSI startup process. If you want to choose individual targets to bind, click the Add button. However, you will need to know the target’s drive letter or mount point. At this point in these instructions, we haven’t gotten quite that far.
Figure I
Bound volumes are listed on this tab.
Step 8: Manage the new volume(s)
When you mount a brand new iSCSI-based volume on your server, Windows treats it the same as if you had added a new hard drive to your computer. Take a look at this: Open Computer Management (Start | Right-click My Computer | Manage). Choose the Disk Management option. If the volume you are using is still blank — that is, newly created on your iSCSI target and does not contain data — Windows will pop up the Disk Initialization wizard, as shown in Figure J.Figure J
The Windows Disk Initialization wizard.
Note in Figure J that Disk 1 is not yet initialized and has a size of 1,020 MB. This disk is a small target I created on my iSCSI host. An iSCSI-based volume follows the same rules as any other Windows volume. You can create this volume as basic or dynamic (although dynamic is not recommended for iSCSI) or even as GPT (GUID partition table) volumes, which support volumes in excess of 2TB.Just as is the case with any Windows volume, you need to initialize the new drive, create a partition, and format the new volume. Take note in Figure J that Windows truly sees this disk as just another typical volume. There is nothing on the Disk Management screen to indicate that Windows is treating this volume any differently because it is stored on an iSCSI array.
and the landmark is below. There is a parameter on LOM/ALOM (for Sparc
arch.) and ILOM (for intel arch.) which you wont find in help. The
default value for that parameter is FALSE which wont allow your OS
instance to boot up and hence it just stuck and wait for manual
intervention at LOM level only.