VMware Cloud Community
listener
Contributor
Contributor

esxcfg-mpath question

I noticed some of the output of esxcfg-mpath -l changed.

It use to look like:

Disk vmhba2:0:26 /dev/sde (5122MB) has 8 paths and policy of Fixed

FC 14:3.0 10000000c9551b84<->500a098387c97db7 vmhba2:0:26 On

FC 14:3.0 10000000c9551b84<->500a098597c97db7 vmhba2:1:26 On active preferred

FC 14:3.0 10000000c9551b84<->500a098487c97db7 vmhba2:2:26 On

And now it looks like:

Disk vmhba1:2:32 vml.020020000060a98000572d43676c5a514164484d6d4c554e202020 /dev/sdt (512078MB) has 4 paths and policy
of Fixed
 FC 73:0.0 10000000c96b3654:20000000c96b3654<->500a0984998ad21b:500a0980898ad21b vmhba1:2:32 On active preferred
 FC 73:0.0 10000000c96b3654:20000000c96b3654<->500a0984898ad21b:500a0980898ad21b vmhba1:3:32 On
 FC 76:0.0 10000000c96b8f1b:20000000c96b8f1b<->500a0983998ad21b:500a0980898ad21b vmhba2:2:32 On
 FC 76:0.0 10000000c96b8f1b:20000000c96b8f1b<->500a0983898ad21b:500a0980898ad21b vmhba2:3:32 On

Did anyone else notice this? This must have happened in one of the recent patches for ESX 3.5 Update 5. Or are the multiple Target WWPNs a resultof something in my config?

thanks,

- h 

Reply
0 Kudos
1 Reply
kastlr
Expert
Expert

Hi,

the "new" output now contains an additional info, the WWNN.

In earlier days only the WWPN's were displayed.

Hope this helps a bit.

Greetings from Germany. (CET)


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