VMware Cloud Community
rifraf
Contributor
Contributor

Adding LUNS to hosts without rebooting?

Ok is there a way? I have an VI3 Cluster running 6 ESX 3.5u4 attached to two EVA4400's and a 6000. If I try to add a new lun, I have to reboot the hosts to see the new luns. Am I doing something wrong or is just the way it is?

Reply
0 Kudos
11 Replies
weinstein5
Immortal
Immortal

No you do not have to reboot - you should be able to rescan the SANs at the storage adapters - using the VI client go to the configuration tab of each host and highlight the adpters and click on the rescan link - if the LUNs are properly presented you should see them and have access to them - you will need to do this for each node in the cluster

If you find this or any other answer useful please consider awarding points by marking the answer correct or helpful

If you find this or any other answer useful please consider awarding points by marking the answer correct or helpful
Reply
0 Kudos
TheEsp
Enthusiast
Enthusiast

Hi

Is your new LUNs from a new SAN ? if so you'll need to reboot your ESX hosts. Additional LUNs from an existing SAN is fine , but a new SAN i.e target requires a reboot.

David

rifraf
Contributor
Contributor

Yes the Storage was already preexisting. That's why I'm stumped. I figured I could rescan, but no luck.. Is there something in the cluster or host that I need to look at?

Reply
0 Kudos
mike_laspina
Champion
Champion

Hi,

I have never had to reboot to add a shared LUN to any ESX host.

Can you share some more details of the configuration?

or perhaps post the output of

esxcfg-mpath -l

vExpert 2009

http://blog.laspina.ca/ vExpert 2009
Reply
0 Kudos
rifraf
Contributor
Contributor

Another question popped in my head, I thought the rule of thumb was not to do a rescan on storage adapters since the scan could disconnect or corrupt guests? Is that still the case?

Reply
0 Kudos
DougBaer
Commander
Commander

I generally rescan the adapters one at a time -- right-click on the adapter in the Storage Adapters configuration screen rather than clicking the "Rescan" link.

What size are the LUNs you are presenting?

Doug Baer, Solution Architect, Advanced Services, Broadcom | VCDX #019, vExpert 2012-23
Reply
0 Kudos
rifraf
Contributor
Contributor

We created a 50 gb lun to store our ISO's on that will be shared throughout the clusters. So not big.

Reply
0 Kudos
DougBaer
Commander
Commander

Yeah, 50gb shouldn't be a problem at all. I have an EVA 4400 in our lab and routinely present new LUNs from it to our ESX hosts without issue.

Doug Baer, Solution Architect, Advanced Services, Broadcom | VCDX #019, vExpert 2012-23
mike_laspina
Champion
Champion

I rescan multiple times without any issue.

vExpert 2009

http://blog.laspina.ca/ vExpert 2009
Reply
0 Kudos
rifraf
Contributor
Contributor

# esxcfg-mpath -l

RAID Controller (SCSI-3) vmhba1:1:0 (0MB) has 4 paths and policy of Fixed

FC 16:0.0 50014380011b99f4<->50014380025b3a9c vmhba1:1:0 On active preferred

FC 16:0.0 50014380011b99f4<->50014380025b3a98 vmhba1:0:0 On

FC 16:0.1 50014380011b99f6<->50014380025b3a99 vmhba2:0:0 On

FC 16:0.1 50014380011b99f6<->50014380025b3a9d vmhba2:1:0 On

Disk vmhba1:2:11 /dev/sdt (512000MB) has 4 paths and policy of Fixed

FC 16:0.0 50014380011b99f4<->50001fe1500a71c8 vmhba1:2:11 On active preferred

FC 16:0.0 50014380011b99f4<->50001fe1500a71cc vmhba1:3:11 On

FC 16:0.1 50014380011b99f6<->50001fe1500a71c9 vmhba2:2:11 On

FC 16:0.1 50014380011b99f6<->50001fe1500a71cd vmhba2:3:11 On

Disk vmhba1:2:12 /dev/sdu (512000MB) has 4 paths and policy of Fixed

FC 16:0.0 50014380011b99f4<->50001fe1500a71c8 vmhba1:2:12 On active preferred

FC 16:0.0 50014380011b99f4<->50001fe1500a71cc vmhba1:3:12 On

FC 16:0.1 50014380011b99f6<->50001fe1500a71c9 vmhba2:2:12 On

FC 16:0.1 50014380011b99f6<->50001fe1500a71cd vmhba2:3:12 On

Disk vmhba1:2:10 /dev/sds (512000MB) has 4 paths and policy of Fixed

FC 16:0.0 50014380011b99f4<->50001fe1500a71c8 vmhba1:2:10 On active preferred

FC 16:0.0 50014380011b99f4<->50001fe1500a71cc vmhba1:3:10 On

FC 16:0.1 50014380011b99f6<->50001fe1500a71c9 vmhba2:2:10 On

FC 16:0.1 50014380011b99f6<->50001fe1500a71cd vmhba2:3:10 On

Disk vmhba1:2:14 /dev/sdw (512000MB) has 4 paths and policy of Fixed

FC 16:0.0 50014380011b99f4<->50001fe1500a71c8 vmhba1:2:14 On active preferred

FC 16:0.0 50014380011b99f4<->50001fe1500a71cc vmhba1:3:14 On

FC 16:0.1 50014380011b99f6<->50001fe1500a71c9 vmhba2:2:14 On

FC 16:0.1 50014380011b99f6<->50001fe1500a71cd vmhba2:3:14 On

Disk vmhba0:0:0 /dev/cciss/c0d0 (69970MB) has 1 paths and policy of Fixed

Local 11:8.0 vmhba0:0:0 On active preferred

Disk vmhba1:2:15 /dev/sdx (512000MB) has 4 paths and policy of Fixed

FC 16:0.0 50014380011b99f4<->50001fe1500a71c8 vmhba1:2:15 On active preferred

FC 16:0.0 50014380011b99f4<->50001fe1500a71cc vmhba1:3:15 On

FC 16:0.1 50014380011b99f6<->50001fe1500a71c9 vmhba2:2:15 On

FC 16:0.1 50014380011b99f6<->50001fe1500a71cd vmhba2:3:15 On

Disk vmhba1:0:3 /dev/sdc (512000MB) has 4 paths and policy of Fixed

FC 16:0.0 50014380011b99f4<->50014380025b3a98 vmhba1:0:3 On active preferred

FC 16:0.0 50014380011b99f4<->50014380025b3a9c vmhba1:1:3 On

FC 16:0.1 50014380011b99f6<->50014380025b3a99 vmhba2:0:3 On

FC 16:0.1 50014380011b99f6<->50014380025b3a9d vmhba2:1:3 On

Disk vmhba1:0:9 /dev/sdi (51200MB) has 4 paths and policy of Fixed

FC 16:0.0 50014380011b99f4<->50014380025b3a98 vmhba1:0:9 On active preferred

FC 16:0.0 50014380011b99f4<->50014380025b3a9c vmhba1:1:9 On

FC 16:0.1 50014380011b99f6<->50014380025b3a99 vmhba2:0:9 On

FC 16:0.1 50014380011b99f6<->50014380025b3a9d vmhba2:1:9 On

Disk vmhba1:0:7 /dev/sdg (512000MB) has 4 paths and policy of Fixed

FC 16:0.0 50014380011b99f4<->50014380025b3a98 vmhba1:0:7 On active preferred

FC 16:0.0 50014380011b99f4<->50014380025b3a9c vmhba1:1:7 On

FC 16:0.1 50014380011b99f6<->50014380025b3a99 vmhba2:0:7 On

FC 16:0.1 50014380011b99f6<->50014380025b3a9d vmhba2:1:7 On

Disk vmhba1:0:4 /dev/sdd (512000MB) has 4 paths and policy of Fixed

FC 16:0.0 50014380011b99f4<->50014380025b3a98 vmhba1:0:4 On active preferred

FC 16:0.0 50014380011b99f4<->50014380025b3a9c vmhba1:1:4 On

FC 16:0.1 50014380011b99f6<->50014380025b3a99 vmhba2:0:4 On

FC 16:0.1 50014380011b99f6<->50014380025b3a9d vmhba2:1:4 On

Disk vmhba1:2:1 /dev/sdj (512000MB) has 4 paths and policy of Fixed

FC 16:0.0 50014380011b99f4<->50001fe1500a71c8 vmhba1:2:1 On active preferred

FC 16:0.0 50014380011b99f4<->50001fe1500a71cc vmhba1:3:1 On

FC 16:0.1 50014380011b99f6<->50001fe1500a71c9 vmhba2:2:1 On

FC 16:0.1 50014380011b99f6<->50001fe1500a71cd vmhba2:3:1 On

Disk vmhba1:0:8 /dev/sdh (512000MB) has 4 paths and policy of Fixed

FC 16:0.0 50014380011b99f4<->50014380025b3a98 vmhba1:0:8 On active preferred

FC 16:0.0 50014380011b99f4<->50014380025b3a9c vmhba1:1:8 On

FC 16:0.1 50014380011b99f6<->50014380025b3a99 vmhba2:0:8 On

FC 16:0.1 50014380011b99f6<->50014380025b3a9d vmhba2:1:8 On

Disk vmhba1:2:2 /dev/sdk (512000MB) has 4 paths and policy of Fixed

FC 16:0.0 50014380011b99f4<->50001fe1500a71c8 vmhba1:2:2 On active preferred

FC 16:0.0 50014380011b99f4<->50001fe1500a71cc vmhba1:3:2 On

FC 16:0.1 50014380011b99f6<->50001fe1500a71c9 vmhba2:2:2 On

FC 16:0.1 50014380011b99f6<->50001fe1500a71cd vmhba2:3:2 On

RAID Controller (SCSI-3) vmhba1:2:0 (0MB) has 4 paths and policy of Fixed

FC 16:0.0 50014380011b99f4<->50001fe1500a71c8 vmhba1:2:0 On active preferred

FC 16:0.0 50014380011b99f4<->50001fe1500a71cc vmhba1:3:0 On

FC 16:0.1 50014380011b99f6<->50001fe1500a71c9 vmhba2:2:0 On

FC 16:0.1 50014380011b99f6<->50001fe1500a71cd vmhba2:3:0 On

Disk vmhba1:0:1 /dev/sda (512000MB) has 4 paths and policy of Fixed

FC 16:0.0 50014380011b99f4<->50014380025b3a98 vmhba1:0:1 On active preferred

FC 16:0.0 50014380011b99f4<->50014380025b3a9c vmhba1:1:1 On

FC 16:0.1 50014380011b99f6<->50014380025b3a99 vmhba2:0:1 On

FC 16:0.1 50014380011b99f6<->50014380025b3a9d vmhba2:1:1 On

Disk vmhba1:2:13 /dev/sdv (512000MB) has 4 paths and policy of Fixed

FC 16:0.0 50014380011b99f4<->50001fe1500a71c8 vmhba1:2:13 On active preferred

FC 16:0.0 50014380011b99f4<->50001fe1500a71cc vmhba1:3:13 On

FC 16:0.1 50014380011b99f6<->50001fe1500a71c9 vmhba2:2:13 On

FC 16:0.1 50014380011b99f6<->50001fe1500a71cd vmhba2:3:13 On

Disk vmhba1:0:5 /dev/sde (512000MB) has 4 paths and policy of Fixed

FC 16:0.0 50014380011b99f4<->50014380025b3a98 vmhba1:0:5 On active preferred

FC 16:0.0 50014380011b99f4<->50014380025b3a9c vmhba1:1:5 On

FC 16:0.1 50014380011b99f6<->50014380025b3a99 vmhba2:0:5 On

FC 16:0.1 50014380011b99f6<->50014380025b3a9d vmhba2:1:5 On

Disk vmhba1:0:2 /dev/sdb (512000MB) has 4 paths and policy of Fixed

FC 16:0.0 50014380011b99f4<->50014380025b3a98 vmhba1:0:2 On active preferred

FC 16:0.0 50014380011b99f4<->50014380025b3a9c vmhba1:1:2 On

FC 16:0.1 50014380011b99f6<->50014380025b3a99 vmhba2:0:2 On

FC 16:0.1 50014380011b99f6<->50014380025b3a9d vmhba2:1:2 On

Disk vmhba1:2:9 /dev/sdr (512000MB) has 4 paths and policy of Fixed

FC 16:0.0 50014380011b99f4<->50001fe1500a71c8 vmhba1:2:9 On active preferred

FC 16:0.0 50014380011b99f4<->50001fe1500a71cc vmhba1:3:9 On

FC 16:0.1 50014380011b99f6<->50001fe1500a71c9 vmhba2:2:9 On

FC 16:0.1 50014380011b99f6<->50001fe1500a71cd vmhba2:3:9 On

Disk vmhba1:2:16 /dev/sdy (512000MB) has 4 paths and policy of Fixed

FC 16:0.0 50014380011b99f4<->50001fe1500a71c8 vmhba1:2:16 On active preferred

FC 16:0.0 50014380011b99f4<->50001fe1500a71cc vmhba1:3:16 On

FC 16:0.1 50014380011b99f6<->50001fe1500a71c9 vmhba2:2:16 On

FC 16:0.1 50014380011b99f6<->50001fe1500a71cd vmhba2:3:16 On

Disk vmhba1:0:6 /dev/sdf (512000MB) has 4 paths and policy of Fixed

FC 16:0.0 50014380011b99f4<->50014380025b3a98 vmhba1:0:6 On active preferred

FC 16:0.0 50014380011b99f4<->50014380025b3a9c vmhba1:1:6 On

FC 16:0.1 50014380011b99f6<->50014380025b3a99 vmhba2:0:6 On

FC 16:0.1 50014380011b99f6<->50014380025b3a9d vmhba2:1:6 On

Disk vmhba1:2:3 /dev/sdl (512000MB) has 4 paths and policy of Fixed

FC 16:0.0 50014380011b99f4<->50001fe1500a71c8 vmhba1:2:3 On active preferred

FC 16:0.0 50014380011b99f4<->50001fe1500a71cc vmhba1:3:3 On

FC 16:0.1 50014380011b99f6<->50001fe1500a71c9 vmhba2:2:3 On

FC 16:0.1 50014380011b99f6<->50001fe1500a71cd vmhba2:3:3 On

Disk vmhba1:2:6 /dev/sdo (512000MB) has 4 paths and policy of Fixed

FC 16:0.0 50014380011b99f4<->50001fe1500a71c8 vmhba1:2:6 On active preferred

FC 16:0.0 50014380011b99f4<->50001fe1500a71cc vmhba1:3:6 On

FC 16:0.1 50014380011b99f6<->50001fe1500a71c9 vmhba2:2:6 On

FC 16:0.1 50014380011b99f6<->50001fe1500a71cd vmhba2:3:6 On

Disk vmhba1:2:4 /dev/sdm (512000MB) has 4 paths and policy of Fixed

FC 16:0.0 50014380011b99f4<->50001fe1500a71c8 vmhba1:2:4 On active preferred

FC 16:0.0 50014380011b99f4<->50001fe1500a71cc vmhba1:3:4 On

FC 16:0.1 50014380011b99f6<->50001fe1500a71c9 vmhba2:2:4 On

FC 16:0.1 50014380011b99f6<->50001fe1500a71cd vmhba2:3:4 On

Disk vmhba1:2:7 /dev/sdp (512000MB) has 4 paths and policy of Fixed

FC 16:0.0 50014380011b99f4<->50001fe1500a71c8 vmhba1:2:7 On active preferred

FC 16:0.0 50014380011b99f4<->50001fe1500a71cc vmhba1:3:7 On

FC 16:0.1 50014380011b99f6<->50001fe1500a71c9 vmhba2:2:7 On

FC 16:0.1 50014380011b99f6<->50001fe1500a71cd vmhba2:3:7 On

RAID Controller (SCSI-3) vmhba2:4:0 (0MB) has 2 paths and policy of Most Recently Used

FC 16:0.1 50014380011b99f6<->50001fe150034c88 vmhba2:4:0 On active preferred

FC 16:0.1 50014380011b99f6<->50001fe150034c8c vmhba2:5:0 Standby

Disk vmhba1:2:5 /dev/sdn (512000MB) has 4 paths and policy of Fixed

FC 16:0.0 50014380011b99f4<->50001fe1500a71c8 vmhba1:2:5 On active preferred

FC 16:0.0 50014380011b99f4<->50001fe1500a71cc vmhba1:3:5 On

FC 16:0.1 50014380011b99f6<->50001fe1500a71c9 vmhba2:2:5 On

FC 16:0.1 50014380011b99f6<->50001fe1500a71cd vmhba2:3:5 On

Disk vmhba1:2:8 /dev/sdq (512000MB) has 4 paths and policy of Fixed

FC 16:0.0 50014380011b99f4<->50001fe1500a71c8 vmhba1:2:8 On active preferred

FC 16:0.0 50014380011b99f4<->50001fe1500a71cc vmhba1:3:8 On

FC 16:0.1 50014380011b99f6<->50001fe1500a71c9 vmhba2:2:8 On

FC 16:0.1 50014380011b99f6<->50001fe1500a71cd vmhba2:3:8 On

#

Reply
0 Kudos
mike_laspina
Champion
Champion

You have a fair number of LUN's (25). I would expect it to require two or more scans before the new LUN shows up as available for VMFS creation.

vExpert 2009

http://blog.laspina.ca/ vExpert 2009
Reply
0 Kudos