Great stuff. I would be willing to put this in place for a test/dev setup. Still feel uneasy that machines might not come out of standby cleanly. I am performing Capacity Planning lately and it is amazing how much money VMware can save you when it comes to power alone.
VMwarewolf just posted Common system management issues in VMware Infrastructure. Take a look. Very usefully grouped troubleshooting steps for common issues. Thanks!
Storage – Create and Administer VMFS Datastores using advanced Techniques
Describe how to identify iSCSI, Fibre Channel, SATA and NFS configurations using CLI commands and log entries.
First, there are several commands relating to storage. Two of which I have discovered give me very useful information.
First is esxcfg-vmhbadevs
[[email protected] log]# esxcfg-vmhbadevs -h
Print the mappings between vmhba names and /dev names
-m–vmfs Print mappings for VMFS volumes to their Service Console partitions and vmhba names.
-f–vfat Print mappings for VFAT volumes to their Service Console partitions and vmhba names.
-q–query Print mapping in 2.5 compatibility mode to mimic vmkpcidivy -q vmhba_devs.
-a–all Print all devices, regardless of whether they have console device or not.
-h–help Show this message.
The useful switch is the –m, this will also print the VMFS id for easy identification of the HBA, Service Console device path and the VMFS volume.
[[email protected] log]# esxcfg-vmhbadevs -m
vmhba0:0:0:3 /dev/cciss/c0d0p3 48c64d26-b496c344-0a0f-001cc4be79c0
vmhba0:1:0:1 /dev/cciss/c0d1p1 48c64f2c-f4eb2f06-df8b-001cc4be79c0
Next is the command esxcfg-mpath
[[email protected] root]# esxcfg-mpath -l
Disk vmhba1:0:1 /dev/sdc (1342249MB) has 2 paths and policy of Most Recently Used
FC 13:0.0 2100001b320b1e1f<->5006016030230c0d vmhba1:0:1 On active preferred
FC 15:0.0 2100001b320b6b31<->5006016830230c0d vmhba2:0:1 Standby
Disk vmhba1:0:2 /dev/sdd (2072576MB) has 2 paths and policy of Fixed
FC 13:0.0 2100001b320b1e1f<->5006016030230c0d vmhba1:0:2 Standby
FC 15:0.0 2100001b320b6b31<->5006016830230c0d vmhba2:0:2 On active preferred
Disk vmhba1:0:0 /dev/sdb (2072576MB) has 2 paths and policy of Fixed
FC 13:0.0 2100001b320b1e1f<->5006016030230c0d vmhba1:0:0 Standby
FC 15:0.0 2100001b320b6b31<->5006016830230c0d vmhba2:0:0 On active preferred
Disk vmhba0:0:0 /dev/sda (69376MB) has 1 paths and policy of Fixed
Local 1:0.0 vmhba0:0:0 On active preferred
This command is intended to supply multi-pathing information for the VMFS volumes. It additionally tells you the type of disk the service console device path the HBA identifier. I can see local, iSCSI, NFS, and Fibre Channel disk information from this command.
Any other commands to get this information? Let me know. As I (slowly) make my way into studying for the VCDX I hope to compile a big list
It is nice to find out someone actually found this website. When I started the site my goal was to share the bits I know about VMware and other technology.
With the flood of Virtualization related blogs out there it is increasingly difficult to share something that I would find valuable and unique. I am not a great writer, so my challenge is to tell what I know and make the content compelling enough to overcome my poor sentence structure.
Thanks again, to John Troyer at VMTN for linking to my little blog I hope I can provide something of value so that people would return to read again.
Here is my Bluebear Kodiak 0.02 beta screenshot. I used Ubuntu because of Windows having problems with the certificates. The UI is very slick. I am going to test various applications and tasks and see how it goes. I just thought I would post something now so I can be cool.
This week I had a weird thing happen. A already problematic VM in the OS and never really a problem in ESX. The machine shutdown because it is convinced there is another Windows 2003 SBS server on the domain, which there is not. This time it turned off and could not be powered back on. The VMDK file for the C drive was missing! I didn’t panic, much. The -flat.vmdk file was still there. I was able to track down a way to fix it:
1. Create a new vmdk the same size.
2. Copy and rename the .vmdk file to the needed location.
3. Edit the .vmdk to point to the -flat.vmdk.
4. Add the virtual disk to the VM.
Everything was ok. I still don’t know how the file could up and dissapear.
Looking at the analytics a few people reach my site because I simply posted a link to a VMware video showing the comparison of installing Hyper-v and ESXi.
Funny to me is my link to the video shows up higher than the VMware version.
All good. Maybe someday people will start to check my own stuff out?
I would even argue that the installation of ESX 3.5 can be done nearly as easy. ESX setup puts any Microsoft product to shame. Now don’t get me wrong, I benefit from the fact that most people find all IT operations confusing. It keeps me working everyday.
So I wanted to put a new script up every week. Hopefully I can be more persistent.
I wanted a quick way to deploy network settings to a number of ESX hosts I would build for a client.