superMaru

  • Home
  • About

Tag Archives: esxi

Finding an associated Cisco Fabric Interconnect in ESXi

02/28/17 / / Leave a comment / ESXi, tips and tricks, VMware / cisco, esxi, fabric interconnect, ucsm

If you have SSH access to your ESX server, smbiosDump has some very useful information. If you look in “OEM Strings: #14”, you can see some very useful information:

[root@ucs-test1:~] smbiosDump | grep “OEM Strings: #14” -A 4
OEM Strings: #14
$SPI:rack-unit-13 <- Server ID
$SPT:hx-nodes <- Service Profile Template
$SYS:test-fi1 <- Fabric Interconnect

This info can be nicely scripted so you can find what host is associated with which FI, or what server ID (rack-unit) shows via UCSM.

Modifying an OVA vmx hardware version

07/28/15 / / 3 Comments / ESXi, tips and tricks, VMware / esxi, ova, ovf, sha1sum, vm, vmware, vmx

Ever tried deploying an OVA but the VM version is not supported by your ESX host? Heres how you can modify the vmx file to make it compatible with your host

ovf-vmxhwver

Uncompress the OVA archive. It can be done with a compression utility like 7-zip. You should now have three different type of files:

  • .mf
  • .ovf
  • .vmdk

.mf is the manifest file, which are typically optional and used for integrity and authenticity checks. It contains the SHA1 digest of all files in the package except the manifest file itself.

.ovf is the main document of the OVF package, which contains all meta-data that includes external files and virtual disks.

.vmdk is the file format that describes the virtual hard drive.

Here is an example of an OVA of a Windows 7 VM that I had uncompressed:

[macky.macky-dev] > ls
Win7-GI-disk1.vmdk Win7-GI.mf Win7-GI.ovf

Changing the vmx hardware version:

Edit the *.ovf file and look for the following line:

<vssd:VirtualSystemType>vmx-11</vssd:VirtualSystemType>

Go ahead and change the vmx version to a different version like so:

<vssd:VirtualSystemType>vmx-10</vssd:VirtualSystemType>

Now that the .ovf file has been modified, we’ll need to update the .mf file with the updated SHA1 hash key.

Here is what my *.mf file looks like:

[macky.macky-dev] > cat *.mf
SHA1(Win7-GI-disk1.vmdk)= 4b38254df053bc2672970f73b7d2a8d20ef93397
SHA1(Win7-GI.ovf)= c3c341f16f5bdd60f2e05136b280e4edf1a034c5

Run SHA1sum on the *.ovf file to get the new hash

[macky.macky-dev] >  sha1sum Win7-GI.ovf
351dbf5a810d17d7c9e672aa5a12a1fd44ddafef Win7-GI.ovf

Take the new hash and update the .mf file like so:

[macky.macky-dev] > cat *.mf
SHA1(Win7-GI-disk1.vmdk)= 4b38254df053bc2672970f73b7d2a8d20ef93397
SHA1(Win7-GI.ovf)= 351dbf5a810d17d7c9e672aa5a12a1fd44ddafef

Now you’re ready to deploy!

Recent Posts

  • Ethical Hacking Final – Fall 2018 (Mission College)
  • Hackthissite.org – Basic 2 and 3
  • New YouTube Channel!
  • Ethical Hacking Midterm – Fall 2018 (Mission College)
  • Windows Subsystem for Linux – Ubuntu GUI with xfce

Categories

  • data center
  • ESXi
  • Home DIY
  • linux
  • Networking
  • Raspberry Pi
  • security
  • tips and tricks
  • Uncategorized
  • VMware
  • vSphere
  • Wireless

Archives

  • December 2018
  • November 2018
  • October 2018
  • September 2018
  • October 2017
  • August 2017
  • July 2017
  • May 2017
  • March 2017
  • February 2017
  • November 2016
  • October 2016
  • October 2015
  • July 2015
  • May 2015
  • April 2015
  • January 2015
  • September 2014
  • August 2014

Tags

authentication bind bootable image cit016 cli console cooling dcui dns DOS esxi freenas hackthissite.org html kernel linux mssh networking ova ovf preview build raspberry pi RDP security serial sha1sum spotify ssh storage telnet temperature tips and tricks tradeshows two factor ubuntu vCenter virtualization vm vmware vmworld vmworld2014 vmx vulnerability Windows zfs
© superMaru 2017
TwitterLinkedIn