ESXi partition layout

The following partitions are created on the boot disk of ESXi.

Size Purpose
4.2 MB Boot
250 MB Boot Bank
250 MB Alternate Boot Bank
110 MB Coredump. Not used since ESXi 5.5. It exists for backward compatibility
2.5 GB Coredump. Introduced in ESXi 5.5, required for hosts with huge RAM
286 MB Store. Used for storing VMware tools etc..
4 GB Scratch. Persistent storage for log files, not created on USB and SD card installation
Remaining Space VMFS, local datastore. Not created on USB and SD card installation

Get partition table of the disk where ESXi is installed:

esxcli storage core device partition list
partedUtil getptbl /vmfs/devices/disks/ESXi_install_disk

The size of a partition is (End Sector – Start Secore) * 512 bytes.

Check active coredump partition:

esxcli system coredump partition list

Get a list of mounted filesystems. The boot partition and coredump partitions will not be mounted.

df
Advertisements

IPMI interface: dedicate, share, failover

Chris Wahl said it short and best:

Dedicate – the IPMI port is used exclusively for out of band access
Share – the on-board NIC’s first port is used exclusively for out of band access
Failover – try to use the IPMI port, and if it is not connected, fail over to the on-board NIC port

From Supermicro:

* The default setting is Failover, which will allow IPMI to be connected from either
the shared LAN port (LAN1/0) or the dedicated IPMI LAN port. Precedence is
given to the Dedicated LAN port over the shared LAN port.
* Select Dedicate for IPMI to connect through the IPMI Dedicated LAN port
at all time.
* Select Share for IPMI to connect through the LAN port on the board

Longer with more detail.

Check the current mode:

ipmitool raw 0x30 0x70 0x0c 0

The output will be one of these:

0x00 = Dedicated
0x01 = Onboard / Shared
0x02 = Failover

To set the mode to

  1. Dedicated
    ipmitool raw 0x30 0x70 0xc 1 1 0
    
  2. Shared
    ipmitool raw 0x30 0x70 0xc 1 1 1
    
  3. Failover
    ipmitool raw 0x30 0x70 0xc 1 0 0 
    

Via http://www.supermicro.com/support/faqs/faq.cfm?faq=9848