Recently I wrote an article about a new VMware fling VM Resource and Availability Service which can be used to simulate failure of one or more ESXi hosts. In this article I’ll describe how to associate the DRS dump with the particular cluster, using the Managed Object Reference ID (MoRef ID).
DRS dump can be found here:
- vCenter Server 5.x and earlier versions on Windows XP, 2000, 2003: %ALLUSERSPROFILE%\Application Data\VMware\VMware VirtualCenter\Logs\drmdump\
- vCenter Server 5.x and earlier versions on Windows Vista, 7, 2008: C:\ProgramData\VMware\VMware VirtualCenter\Logs\drmdumb\
- vCenter Server Appliance 5.x: /var/log/vmware/vpx/drmdump/
When you open the location where the DRS dump is stored you’ll find similar folder structure:
These folders with some numbers don’t tell you anything which cluster it represents. This ID belongs to Managed Object Reference ID (MoRef ID).
To match the MoRef ID with cluster name open the following page https://vCenter_Server_IP/mob/?moid=group-d1 and it will load a list containing all the managed object by vCenter Server, which are under group-d1 folder (Datacenters).
Select the datacenter where the cluster is located:
then select host folder group:
and in the child entity find the ID which corresponds with the cluster:
This is not the only case where MoRef ID is used. vCenter server creates for each and every object in the inventory an unique ID. MoRef ID is a vCenter identifier which is assigned to every single entity, introduced in vSphere 4.0.
Every object has it’s own address https://vCenter_server_IP/mob/?moid=<OBJECT_ID>
An example how it can be used is a vCloud Director which reads the vCenter objects leveraging API.
Latest posts by Jan Hosek (see all)
- Update of Cloud Storage Gateways category on WhatMatrix - August 23, 2016
- Cloud Storage Gateways Comparison on WhatMatrix - October 1, 2015
- VMware vCenter Server top level inventory – MoRef ID - April 2, 2015
