I have 2 PSC which are replicating. I can find the replication status using federation status using CLI. Is there a way I can do this using API (Rest/SOAP)

./vdcrepadmin -f showfederationstatus -h psc01.vsphere.local  -u 'administrator' -w 'secret!'
Domain Controller: psc01.vsphere.local
Invocation ID: b67838a0-1935-4094-8611-584fb19fba6c
Replication cycle count: 2485
Max consumable  USN: 2922
Max originating USN: 2922
Has seen 5206 USN from 9db429c3-4a1c-4f78-8eae-b5be980197b5
Has processed 5209 USN from psc02.vsphere.local


Domain Controller: psc02.vsphere.local
Invocation ID: 9db429c3-4a1c-4f78-8eae-b5be980197b5
Replication cycle count: 4155
Max consumable  USN: 5209
Max originating USN: 5206
Has seen 2922 USN from b67838a0-1935-4094-8611-584fb19fba6c
Has processed 2922 USN from psc01.vsphere.local

./vdcrepadmin -f showpartnerstatus -h psc01.vsphere.local  -u 'administrator' -w 'secret!'
Partner: psc02.vsphere.local
Host available:   Yes
Status available: Yes
My last change number:             2922
Partner has seen my change number: 2922
Partner is 0 changes behind.

When selecting a VM to migrate the option to migrate is greyed out.  In fact, Power On, Migrate, Revert to Current Snapshot are greyed out.  I would like to migrate this VM to another host and datastore.

ESXi version 5.1.0 build 1021289

VMware vCenter Server, 5.1.0 build 947673

I've migrated 154 VMs and out of the 154 VMs migrated approximately a dozen VMs would not allow for live migrations(migrate... option greyed out).  I could not identify any commonality between the dozen VMs that did not allow for live migrations.

I really need to migrate this VM in a live state if at all possible.

When vCenter checks to see if a VM is a valid candidate to migrate, what does it check for because the migrate option is NOT grey for about a second before it becomes greyed out?

I'd like to configure a "datastore usage on disk" trigger (which is a conditional trigger) but the "condition length" field for either warning or alert -- don't let me pick or type any values.

What am I missing?

vCenter standard 5.1, hosts licensed with Enterprise

Hello

Since we have updatet from ESXi 4.1 to Update 1 we have problems with taking quiesced snapshot. Before we have installed the update 1 quiesced snapshot worked witout problems.

When we take a quiesced snapshot, Windows 2008 R2 mount a new volumes and remove them after the snapshot is taken.

In the Eventlog i can see following errors and infos:

multiple entrys from this 2 event:

Log Name:      System
Source:        Virtual Disk Service
Date:          11.04.2011 22:40:26
Event ID:      3
Task Category: None
Level:         Information
Keywords:      Classic
User:          N/A

Description:
Service started.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Virtual Disk Service" />

and

Log Name:      System
Source:        Service Control Manager
Date:          11.04.2011 22:40:26
Event ID:      7036
Task Category: None
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      TESTTEMPLATE.gef.be.ch
Description:
The Virtual Disk service entered the running state.

and

Log Name:      System
Source:        Ntfs
Date:          11.04.2011 22:20:57
Event ID:      57
Task Category: (2)
Level:         Warning
Keywords:      Classic
User:          N/A
Description:
The system failed to flush data to the transaction log. Corruption may occur.

and

Log Name:      System
Source:        Ntfs
Date:          11.04.2011 22:20:57
Event ID:      137
Task Category: (2)
Level:         Error
Keywords:      Classic
User:          N/A
Description:
The default transaction resource manager on volume \\?\Volume{d533451f-6478-11e0-94e8-005056ae007a} encountered a non-retryable error and could not start.  The data contains the error code.

and

Log Name:      Application
Source:        VSS
Date:          11.04.2011 18:05:48
Event ID:      12289
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      G3110SRV014APL.gef.be.ch
Description:
Volume Shadow Copy Service error: Unexpected error DeviceIoControl(\\?\fdc#generic_floppy_drive#6&2bc13940&0&0#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b} - 0000000000000418,0x00560000,0000000000000000,0,000000000027CDB0,4096,[0]).  hr = 0x80070001, Incorrect function.
.

Operation:
   Exposing Recovered Volumes
   Locating shadow-copy LUNs
   PostSnapshot Event
   Executing Asynchronous Operation

Context:
   Device: \\?\fdc#generic_floppy_drive#6&2bc13940&0&0#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}
   Examining Detected Volume: Existing - \\?\fdc#generic_floppy_drive#6&2bc13940&0&0#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}
   Execution Context: Provider
   Provider Name: VMware Snapshot Provider
   Provider Version: 1.0.0
   Provider ID: {564d7761-7265-2056-5353-2050726f7669}
   Current State: DoSnapshotSet
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="VSS" />
    <EventID Qualifiers="0">12289</EventID>
    <Level>2</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2011-04-11T16:05:48.000000000Z" />
    <EventRecordID>6430</EventRecordID>
    <Channel>Application</Channel>
    <Security />
  </System>
  <EventData>
    <Data>DeviceIoControl(\\?\fdc#generic_floppy_drive#6&amp;2bc13940&amp;0&amp;0#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b} - 0000000000000418,0x00560000,0000000000000000,0,000000000027CDB0,4096,[0])</Data>

When we remove the snapshot the vm freeze for about 30second (no Ping no RDP)

Have anyone the same issue?

I have try to install a new clean server 2008 r2 but have the same problem.

Best Regards
Simon

I did this once before without any issues, but I am getting an error when trying to do so again.  The VCSA with the embedded PSC is on 6.0 U1, as are the external PSC's.  I have tried with both FQDN and IP. 

Actual FQDN and password removed

cmsso-util reconfigure --repoint-psc FQDN  --username administrator --domain-name vsphere.local --passwd password

                  Validating Provided Configuration ...

                  Error: The provided Platform Services Controller(PSC) FQDN is not a replication partner of the localhost

                  Please make sure to provide the Primary Network Identifier (PNID) of the PSC.

Any tips or advice?

I have a single sso domain with 6 vcenters each have their own psc.

can i upgrade directly to 6.5 without any issues?

1. PSC

2. vcenter

3. VUM

is that the order?

We had a ESXi 5.5 cluster which has 8 hosts and the CPU usage (NOT speaking about CPU Util) was around 50% for each host.

We upgraded the vCenter and ESXi to 6.0 version. vCenter build 3339083 and ESXi build 3568940.

Right after upgrading the CPU usage for each host stands steady at 100% at vCenter and the ESXtop still shows %USED as around 50% as before.

In vCenter, for CPU usage reatime data, there are 32 cores (0 -31) all have average of around 50% but when i select host entry the usage is 100%.

Confused how 32 cores are showing up 50% average and the host entry which is a sum of all core entry shows 100% usage after upgrading to ESXi 6?

Whether to believe ESXTOP or vCenter performance data?

I also posted this in the storage forum, but I figured I'd ask here too.

TLDR:  Does anyone know a good way to migrate the networking on a host that was on a distributed switch and its vCenter is dead and being rebuilt from scratch?

We have a dead vCenter.  Utterly dead.  I'm rebuilding vCenter and will add the hosts into the new vCenter.  The complication comes in with the distributed virtual switch with iSCSI vmks.  Each host has a proxy switch (the offline copy of the dvs), so the hosts can see its iSCSI storage.  We wont be able to export the DVS config from the dead vCenter, so I will have to migrate each hosts networking and iSCSI storage adapter to a standard switch, build a new DVS, and migrate the hosts over to that.  All without the hosts losing network or storage connectivity.  Each host has two iSCSI VMKs with a NIC associated with each on the DVS

This is my plan:

• Add a standard switch to each host.
• Remove one of the iSCSI VMKs from the iSCSI storage adapter
• Remove the associated nic from the DVS
• Add that NIC to the standard switch
• Migrate the iSCSI VMK that I removed from the storage adapter to the standard switch
• Add the iSCSI VMK on the standard switch to the iSCSI storage adapter

Once I confirm that the new VMK on the standard switch has a path to storage I should be able to do the same for the remaining iSCSI vmk on the host proxy switch (VDS).

Does this sound like it will work?  I've never migrated iSCSI between standard and distributed switches.  These are old 5.0 hosts so I really want to avoid an APD event.

Recently after upgrade our servers esx to 6.5 and vmware vcenter server to we have problem with java high cpu usage. I reinstaled the vmware vcenter and the problem still persist. The server Windows Server 2012 R2 HP DL 320e Gen8. I found out in log someting like that and the dmp file was created.

can someone help me out what can be the problem i can upload the dump.

2017-06-09T11:37:16.602+02:00 info vpxd[08704] [Originator@6876 sub=vpxLro opID=257a550a] [VpxLRO] -- BEGIN lro-20641 -- SessionManager -- vim.SessionManager.sessionIsActive -- 5226e485-e1a8-8582-7e34-c74a698ba0be(52f71a54-83be-daf0-bb0e-820e977daa28)

2017-06-09T11:37:16.730+02:00 warning vpxd[08596] [Originator@6876 sub=VpxProfiler opID=HB-host-9@3640-43553b7b] InvtHostSyncLRO::StartWork [HostSyncTime] took 2780 ms

2017-06-09T11:37:16.730+02:00 info vpxd[08704] [Originator@6876 sub=vpxLro opID=257a550a] [VpxLRO] -- FINISH lro-20641

2017-06-09T11:37:29.057+02:00 info vpxd[08460] [Originator@6876 sub=vpxLro opID=795025c4-3e9f-40bc-be03-0c074ffbc7a4-609-ngc-c3] [VpxLRO] -- BEGIN lro-20643 -- ServiceInstance -- vim.ServiceInstance.retrieveContent -- 52b2c2e7-b4d3-c799-5886-c787e50fd391

2017-06-09T11:37:29.057+02:00 info vpxd[08460] [Originator@6876 sub=vpxLro opID=795025c4-3e9f-40bc-be03-0c074ffbc7a4-609-ngc-c3] [VpxLRO] -- FINISH lro-20643

2017-06-09T11:37:29.534+02:00 info vpxd[08328] [Originator@6876 sub=vpxLro opID=795025c4-3e9f-40bc-be03-0c074ffbc7a4-611-ngc-d4] [VpxLRO] -- BEGIN lro-20645 -- SessionManager -- vim.SessionManager.loginByToken -- 5223691c-bebd-0e65-d97c-f7cebf6c5264

2017-06-09T11:37:29.538+02:00 info vpxd[08328] [Originator@6876 sub=vpxLro opID=795025c4-3e9f-40bc-be03-0c074ffbc7a4-611-ngc-d4] [VpxLRO] -- FINISH lro-20645

2017-06-09T11:37:32.619+02:00 info vpxd[08512] [Originator@6876 sub=vpxLro opID=795025c4-3e9f-40bc-be03-0c074ffbc7a4-613-ngc-34] [VpxLRO] -- BEGIN lro-20646 -- SessionManager -- vim.SessionManager.logout -- 5223691c-bebd-0e65-d97c-f7cebf6c5264(527b75df-0f33-1953-7cb7-86bd42c0af97)

2017-06-09T11:37:32.619+02:00 info vpxd[08512] [Originator@6876 sub=vpxLro opID=795025c4-3e9f-40bc-be03-0c074ffbc7a4-613-ngc-34] [VpxLRO] -- FINISH lro-20646

2017-06-09T11:37:48.743+02:00 info vpxd[08372] [Originator@6876 sub=Default opID=HB-host-9@3627-1f6995b7] CoreDump: Writing minidump

2017-06-09T11:38:03.276+02:00 warning vpxd[08412] [Originator@6876 sub=VpxProfiler opID=795025c4-3e9f-40bc-be03-0c074ffbc7a4-611-ngc-d4-EventManagerProcessJobs-728f7d10] EventManagerProcessJobs [TotalTime] took 33738 ms

2017-06-09T11:38:03.276+02:00 panic vpxd[08372] [Originator@6876 sub=Default opID=HB-host-9@3627-1f6995b7]

-->

--> Panic: Unrecoverable VmRootError. Panic!

--> Backtrace:

--> [backtrace begin] product: VMware VirtualCenter, version: 6.5.0, build: build-5318154, tag: vpxd, cpu: x86_64, os: windows, buildType: release

--> backtrace[00] vmacore.dll[0x001F4ABA]

--> backtrace[01] vmacore.dll[0x00067FB0]

--> backtrace[02] vmacore.dll[0x0006A42E]

--> backtrace[03] vmacore.dll[0x00225887]

--> backtrace[04] vmacore.dll[0x00225A51]

--> backtrace[05] vpxd.exe[0x0008B8CB]

--> backtrace[06] vpxd.exe[0x0121723E]

--> backtrace[07] MSVCR120.dll[0x00066920]

--> backtrace[08] MSVCR120.dll[0x0005E36D]

--> backtrace[09] ntdll.dll[0x00092A63]

--> backtrace[10] vpxd.exe[0x000BDAD1]

--> backtrace[11] vpxd.exe[0x000B9FBD]

--> backtrace[12] vpxd.exe[0x000BC796]

--> backtrace[13] vmacore.dll[0x0018891B]

--> backtrace[14] vmacore.dll[0x0018990C]

--> backtrace[15] vmacore.dll[0x00221599]

--> backtrace[16] MSVCR120.dll[0x00024F7F]

--> backtrace[17] MSVCR120.dll[0x00025126]

--> backtrace[18] KERNEL32.DLL[0x000013D2]

--> backtrace[19] ntdll.dll[0x000154E4]

--> [backtrace end]

2017-06-09T11:38:03.279+02:00 info vpxd[08372] [Originator@6876 sub=SupportMgr opID=HB-host-9@3627-1f6995b7] Wrote uptime information

I created datastore that located on iSCSI SAN and connect it to three  ESXi 6.5 hosts. I deployed VM on this datastore for testing storage performance. Then I've destroyed LUN on SAN and didn't unmount datastore from ESXi hosts. Now my host don't see connected datastore. But datastore and VM exist in vCenter and i can't delete them, only rename or move to folder.

Hi everyone

We had a scheduled maintenance window over the weekend while some work was carried out elsewhere in the building. As a precaution we shutdown the infrastructure that we we still keep onsite (the rest is in colo). So all we have is a 2 node ESXi cluster, managed by vCenter Server Appliance (Novell SUSE Linux Enterprise 11 64bit). It only has 6 VMs running on it as most of them have been migrated offsite.

This morning we started up the OpenFiler NFS storage box and the ESXi nodes. All VMs started ok, including the vCenter Server Appliance.

However I was unable to connect to the vCenter Appliance using vSphere Client. I could connect to the ESXi nodes directly without problems. DNS hostnames all resolve to the IP addresses without problems.

Looking at the vSphere Client logs I see the following message each time I tried to connect:

System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 10.10.0.205:443

So I connected to the vCenter Appliance over SSH and it looks like it's run out of disk space. Here's the df and mount output:

vlevcenter01:/ # df -h

Filesystem            Size  Used Avail Use% Mounted on

/dev/sda3             9.8G  9.8G     0 100% /

devtmpfs              4.0G  104K  4.0G   1% /dev

tmpfs                 4.0G  4.0K  4.0G   1% /dev/shm

/dev/sda1             130M   18M  105M  15% /boot

/dev/sdb1              20G  3.8G   15G  21% /storage/core

/dev/sdb2              20G  717M   18G   4% /storage/log

/dev/sdb3              20G   19G     0 100% /storage/db

vlevcenter01:/ # mount -l

/dev/sda3 on / type ext3 (rw,acl,user_xattr)

proc on /proc type proc (rw)

sysfs on /sys type sysfs (rw)

debugfs on /sys/kernel/debug type debugfs (rw)

devtmpfs on /dev type devtmpfs (rw,mode=0755)

tmpfs on /dev/shm type tmpfs (rw,mode=1777)

devpts on /dev/pts type devpts (rw,mode=0620,gid=5)

/dev/sda1 on /boot type ext3 (rw,acl,user_xattr)

/dev/sdb1 on /storage/core type ext3 (rw)

/dev/sdb2 on /storage/log type ext3 (rw)

/dev/sdb3 on /storage/db type ext3 (rw)

So the database and root partitions have run out of space. Looking in /var/log/localmesages:

Jul 15 10:10:51 vlevcenter01 startproc: startproc: Empty pid file /var/run/slapd/slapd.pid for /usr/lib/openldap/slapd
Jul 15 10:10:51 vlevcenter01 startproc: startproc:  exit status of parent of /usr/lib/openldap/slapd: 1
Jul 15 10:10:52 vlevcenter01 checkproc: checkproc: Empty pid file /var/run/slapd/slapd.pid for /usr/lib/openldap/slapd
It looks like it can't create the pid files for the services because there is no disk space.

We already have 60GB of vmdks allocated to this VM though we do have space on our datastore to add more. But I'm concerned that the vCenter Appliance will just grow and grow.

1) Is there any scheduled maintenance that runs on the vCenter Appliance to keep disk usage under control? This is what I would expect from an enterprise product, I'm very surprised to see such a problem happen.

2) Where should I start looking to clear some disk space so we can get the vCenter service back up and running?

I'd like to find a longer term solution to this otherwise we might have to just keep adding vmdks until our datastore runs out of space.

Cheers, B

I'm trying to reset the administrator@vsphere.local password but it fails every time...

==================

Please select:

0. exit

1. Test LDAP connectivity

2. Force start replication cycle

3. Reset account password

4. Set log level and mask

5. Set vmdir state

==================

3

  Account DN: cd=administrator,cn=users,dc=vsphere,dc=local

VmDirForceResetPassword failed (9106)

Anyone know how to fix this ??

Hi, all. I keep putting off this change, but I think I'm ready. I have one vCenter server, 3 esxi hosts and one Windows server running update manager. I need to move them all into a new trust vlan from the current flat vlan. I have separate dual nic'd vswitches for the flat vlan and the new vlan, plus separate vswitches for vmotion and iscsi. I'd like thoughts on this plan that I partially cribbed from another post, plus I have a couple of questions.

1. On each host, add a vmkernel to the vswitch for the trust vlan (no vmkernel currently); assign IP from trust vlan
2. Disconnect the hosts from vCenter
3. When the hosts are disconnected, remove them from the old vCenter (this should remove the vCenter configs on the hosts and cleanup any certificates tied to the old vCenter)
4. Change the vCenter IP and edit VM to use trust network (vcenter is a VM, so log into that host directly with client)
5. On each host, set the new vmkernel in trust to be the management network
6. Add the hosts to the new vCenter

Post migration

Add proxy information for Update Manager

Questions:

The new vmkernel on the hosts will be vmk5. Is that OK for the management network, or does the mgmt network have to be on vmk0?

I understand that in vSphere 6.0, I'll lose the performance history. That's fine, but will I lose anything else that will make this change more complicated?

Thanks.

I’m trying to remove an iSCSI datastore from about 10 x 6.0 U2 hosts. I’ve unmounted it as usual but its errored on 2 hosts saying “HostStorageSystem.UnmountVmfsVolume" and “Unmount VMFS volume The operation is not allowed in the current state” The rest have dismounted fine.

If I go on the two hosts with the C# client directly, it tells me under Config / Storage that the DS is unmounted. It just seems its unmounted in vCenter which Ive restarted several times but to no avail. Ive also restarted the management agents on the hosts again to no avail.

Any ideas how I unmount from these hosts so it shows in vCenter? I guess I could delete it anyway in VC seeing as its really unmounted on all the hosts even if not showing .

Thanks

I`m needing to create a Cluster, which is relatively straight forward...

My only query is can I do this and move hosts to the Cluster on a live system? i.e Whilst all Hosts and VM`s are powered on?

(without any faults occurring)

our vcenter 6.0 ( windows 2012 r2 ) working ccc.local domain. now we will change the our domain controller. how to change vcenter settings and esxi 6.0 settings for new domain controller.

Windows 10 v1607

Chrome 58
Firefox 53

vSphere Server Appliance 6.0.0.30200 Build Number 5326079

Used to be working but ever since browser updates, I am unable to get CIP working. It's either not recognized as being installed or if it does try to run it crashes. Also triggers additional popup regarding updating SSL cert in Firefox.

vmware-csd.exe - Application Error

The application was unable to start correctly (0xc0000018). Click OK to close the application.

The VMware Client Integration Plugin has update its SSL certificate in Firefox. Please restart Firefox

I've tried to install different versions of the CIP (obtained from the link from within vCenter --> About, from VMware website), and have also tried installing plugin by the direct installer (extracted from the parent installer), can't seem to get anything to work.

Also can't find any recent threads on this, only from a while ago. (I can't be the only one!)

Would gladly use the HTML5 client but haven't upgraded to 6.5 yet.

Trying to upgrade windows vCenter 6.0 update 2 to update 3 ( embedded PSC ) but failed with error code 3010 and error code 1603.

• Installation of component VCSServiceManager failed with error code '1603'. Check the logs for more details.
• Installation of component VMware vCenter Server failed with error code '3010'. Check the logs for more details.

1. Updated all the pending windows updates on the VC server
2. killed any process holding vmeventmsg.dll , also renamed the dll and created the copy of original file
3. Rebooted server after updates or any changes done. still the upgrade is not successful.
4. Ensured the ipv4 stack is installed

Any suggestions please ?

Hey all,

I just wanted to update a vCSA appliance. Unfortunately it hangs in the status "Checking for aivailable updates..." as has no internet access.

I changed the settings to CD-ROM  updates, mounted the update-repo iso and restarted the appliance, but no luck, it's still in the checking for updates mode.

Anyone has an idea how to stop this process? As the check and install update buttons are disabled during the update search.

Thanks

Tim

Basically, let's say I have a /24, and these IPs are accessible from a specific server.         

I'd like to run a GRE tunnel from that server to the ESXi host and then allow VMs to be made using those IPs as it's main IP.

Does ESXi or ESX support this?