VMware Cloud Community
bjselman
Contributor
Contributor

LUN Path Selection ?

I have 2 ESX servers in a cluster and a LUN placed in its own resource pool in the cluster. On ESX2, the Path Selection shows it's Fixed and when I click on Properties, it shows 1 extent. However, on ESX1, it doesn't show these things. When I click on Properties it doesn't show any extents, yet I can "Manage Paths" (with an error though). Should I be concerned with this? I have rescanned and refreshed. The other LUN does not differ across ESX servers in this regard.

I've attached screen shots showing what i'm looking at.

(I should note that I'm not currently having any issue's with the LUN - that I know of)

"Mr. Madison, what you've just said is one of the most insanely idiotic things I have ever heard. At no point in your rambling, incoherent response were you even close to anything that could be considered a rational thought. Everyone in this room is now dumber for having listened to it. I award you no points, and may God have mercy on your soul."

Reply
0 Kudos
5 Replies
RParker
Immortal
Immortal

Well something isn't right, assuming both machines are pointing to the same LUN, and that's a big if. Are you sure they are the same LUN? If one machine says it's an extent the other doesn't.. yet you get an error, that's a red flag. You may not have any issues yet, but this isn't good.

You need to get this resolved.

And what is up with the "Mr. Madison..." tagline? IS that meant as a joke.. or do you plan to keep this as your tagline on all your posts, because it makes zero sense, just like the tagline suggest..

Reply
0 Kudos
bjselman
Contributor
Contributor

It is the same LUN. But yet i DON'T get an error. I'm sure that is what you meant.

i'll call VMware tomorrow.

yeah, the tagline is a joke. i'm glad you got it. and i'll remove it just for you. Smiley Happy

Reply
0 Kudos
kastlr
Expert
Expert

Hi,

for unknown reasons the VC is sometimes "outdated", so you should verify your findings and connect directly to both ESX Servers using the VIC.

If there's a mismatch between direct connection and via VC, restart the VC Server Service.

If there's no mismatch, perform the following commands from the service console.

esxcfg-mpath -l

esxcfg-vmhbadevs -a

esxcfg-vmhbadevs -m

Compare the informations regarding your LUN, they should be identical.

If not, post the output here, maybe we could help you with that problem.


Hope this helps a bit.
Greetings from Germany. (CEST)
bjselman
Contributor
Contributor

Thanks Ghost.

When I connect directly to ESX1, it does show the information not listed when connecting via VIC. I have restarted the VS and both ESX servers. When I connect via VIC, ESX1 is still not consistent with ESX2. Here are the outputs:

ESX1

# esxcfg-mpath -l

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

Local 6:0.0 vmhba0:0:0 On active preferred

Disk vmhba32:2:0 /dev/sdb (32768MB) has 1 paths and policy of Fixed

iScsi sw iqn.thdal9esx1.travelhost.com<->iqn.2003-10.com.lefthandnetworks:travelhost:214:productionserversvol vmhba32:2:0 On active preferred

Disk vmhba32:0:0 /dev/sda (102400MB) has 1 paths and policy of Fixed

iScsi sw iqn.thdal9esx1.travelhost.com<->iqn.2003-10.com.lefthandnetworks:travelhost:87:testvol1 vmhba32:0:0 On active preferred

# esxcfg-vmhbadevs -a

vmhba0:0:0 /dev/cciss/c0d0

vmhba32:0:0 /dev/sda

vmhba32:2:0 /dev/sdb

# esxcfg-vmhbadevs -m

vmhba32:2:0:1 /dev/sdb1 480a4e6b-3e5b36b0-59c4-001cc4484de7

vmhba32:0:0:1 /dev/sda1 47fc0fec-aab23100-e689-001cc4483efb

vmhba0:0:0:3 /dev/cciss/c0d0p3 47bc1078-008c54a8-8b7d-001cc4eb96fc

ESX2

# esxcfg-mpath -l

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

Local 6:0.0 vmhba0:0:0 On active preferred

Disk vmhba32:1:0 /dev/sdb (32768MB) has 1 paths and policy of Fixed

iScsi sw iqn.thdal9esx2.travelhost.com<->iqn.2003-10.com.lefthandnetworks:travelhost:214:productionserversvol vmhba32:1:0 On active preferred

Disk vmhba32:0:0 /dev/sda (102400MB) has 1 paths and policy of Fixed

iScsi sw iqn.thdal9esx2.travelhost.com<->iqn.2003-10.com.lefthandnetworks:travelhost:87:testvol1 vmhba32:0:0 On active preferred

# esxcfg-vmhbadevs -a

vmhba0:0:0 /dev/cciss/c0d0

vmhba32:0:0 /dev/sda

vmhba32:1:0 /dev/sdb

# esxcfg-vmhbadevs -m

vmhba32:1:0:1 /dev/sdb1 480a4e6b-3e5b36b0-59c4-001cc4484de7

vmhba32:0:0:1 /dev/sda1 47fc0fec-aab23100-e689-001cc4483efb

vmhba0:0:0:3 /dev/cciss/c0d0p3 47bc0e55-e0a3aac0-88ec-001cc4ebc860

Reply
0 Kudos
kastlr
Expert
Expert

Hi,

the output you provided does show that both ESX Server does see the identical LUN's.

Right now, the VC Server does provide incorrect data about your environment while the ESX Servers are fine.

So, if rebooting the whole environment doesn't fix the display[/b] issue, remove and re-add the host from the VC.

This should force VC to reread the informations from scratch.


Hope this helps a bit.
Greetings from Germany. (CEST)
Reply
0 Kudos