Hi,
Has anyone else looked into changing the SCSI controller of the vCenter appliance? I find it strange that the appliance is shipped without using the paravirtual SCSI controller, we have seen good returns when moving to this and would like to across the board where possible (known limitations taken into consideration).
I appreciate the appliance is distributed 'as is' and modifying it in such a way would likely void any support but I'm still curious to know whether anyone has tried it.
Dears,
I would like to set an Alarm if someone removed a VM, however I am not able to set the triggered alarm VM being removed or VM deleted as it does not exist.
anyone faced a similar problem?
on other note: How do I set an alarm for a event regarding: Device naa.00000xxx0x0xx0xx0x performance has deteriorated. I/O Latency increased .....?
thanks!
I am having problems with Vcenter. I am getting "503 Service Unavailable (Failed to connect to endpoint: [N7Vmacore4Http20NamedPipeServiceSpecE: 0x0000562aca3f19b0] _serverNamespace = / action = Allow _pipeName = / var / run / vmware / vpxd-webserver-pipe)" when I connect via https.
I did some troubleshooting and narrowed down the issue to postgresql does not come up.
root @ photon-machine [~] # service-control - status
StartPending:
vmware-vpxd-svcs
Running:
applmgmt lwsmd vmafdd vmcad vmdird vmdnsd vmonapi vmware-cis-license vmware-cm vmware-eam vmware-psc-client vmware-rhttpproxy vmware-sca vmware-statsmonitor vmware-sts-idmd vmware-stsd vmware-vapi-endpoint vmware-vmon vsphere- client vsphere-ui
Stopped:
pschealth vmcam vmware-content-library vmware-imagebuilder vmware-mbcs vmware-netdumper vmware-perfcharts vmware-rbd-watchdog vmware-sps vmware-updatemgr vmware-vcha vmware-vpostgres vmware-vpxd vmware-vsan-health vmware-vsm
root @ photon-machine [~] # more / var / log / vmware / vpostgres / serverlog
LOG: syntax error in file "/storage/db/vpostgres/health_status_worker.conf" line 1, near token ""
LOG: skipping missing configuration file "/storage/db/vpostgres/postgresql.conf.repl"
FATAL: configuration file "/storage/db/vpostgres/postgresql.conf" contains errors
I am using the vcenter to manage NSX and do not want to rebuild the complete environment from scratch.
Hi,
Actually i am confused with the concept of enhanced vmotion.What my understanding is that enhanced vmotion is used for situation where no shared storage available and it will do vmotion same like the normal vmotion without powered off.But recently we had a POC where servers are without shared storage and the servers used are different compatibility.So first we enabled EVC in the cluster since both hosts are of different cpu.and when i tried to do vmotion from web client and selected change host it was not showing the destination host to move.i can see the host where the vm is residing.Same when i tried to change the datastore.But when i selected change both host and datastore its showing the both hosts and when i initiated that it got stuck and failed after some time showing check vmotion network error in the web client and when checked progress of the vmotion from windows client its showing stuck at 29% showing migrating active state and got failed.But when i tried to powered off the vm and do the vmotion with change both host and datastore its migrating .
so in the case of hosts without shared storage whether we need to poweroff the vm and do the migration?
when we selected for changing the host and changing the datastore option separately why we are not able to see the host and datastore.But they appear when we selected to move both host and datastore at same time?
in our setup we had a standard switch which is carrying the management traffic to the vcenter connected to switch1 and distributed switch carrying the vm network and vmotion network connected to switch 2.
when i tried to give the same management ip range 172.19.19.x in the vmkernel port for the host 1 connected to distributed switch.i am able to set the ip.But when i tried to give same ip range in the vmkernel port of the host2 from the distributed switch its not getting set showing the setting got reverted back since it caused host management to become unreachable.I dont understand for both the host same configuration but why for the second host i am not able to the set the vmkernel ip.so finally i used some other ip range for the vmkernel port and did the above vmotion metioned.
can anyone please help on this ?
thanks in advance
ritchie
Hi all,
Having an issue with the VCS certificate Manager w/ESXi hosts.
VCS is 6.5 latest build, ESXi hosts are 6.5 latest build. VCS is on Windows, not VMCA.
edit* the VCS does have a valid trusted cert from our CA. No issues there.
I'm having two issues that are more than likely related:
First in the VCS under the certificate tab of a selected host - the certificate data field is just blank. No data. Cannot figure out why I'm not seeing ESXi host certificates.And when i say blank - just a blank field.
Second, when I try to renew the host certificates, the job says it completed, but it actually never did. After restart of the host/agent - the ESXi still shows the old certificate. Obviously nothing is reflected in the VCS because the cert tab is blank.
I have 12 hosts and they all do the same thing.
Google has been useless as well VMWare docs.
Any help would be appreciated!
-James
Our certificate for our VCSA appliance showed as revoked (expired) and would not allow access to manage the vSPhere environment via web browser (at least in Firefox). Using Chrome, I was able to use the HTML5 version to get in, and was also able to get into the GUI manager for the PSC where you can manage the certificates. The language was a bit confusing for the cert files I was provided, but there were 3 tabs from what I recall: Machine Certs, Solution User Certs and Root Certs, which I thought I had uploaded properly. There's some technique to be employed where combining certs to create a chain is necessary so that might have been why that part didn't work. The problem now is, I can't get back to that manager GUI, and when I try to use the Certificate Manager via CLI, I'm getting errors trying to both upload what I did in the GUI and trying to reset to get back to square 1 and start over with, perhaps, a self-signed cert or something...
When I choose any of the options in the cert manager, including resetting all or generate certificates, no matter what I changed or what defaults I use for the config, it always seems to give errors "updating services", then it rolls back the changes it was trying to make. Each time it takes roughly 15-20 minutes before I see that nothing has changed and I still can't get back into the GUI to manage the VMs, etc., and the browser just shows there's an invalid certificate (Chrome) or won't allow me to even proceed with caution (Firefox). It says check the /var/[directory]/log for details, but the log only shows the errors that I get (maybe I'm not seeing the right thing?). ANy assistance on this would be great as I need to get back into the system to manage and update the certificates ASAP. Thanks.
I use VM-Ware vSphere 5.5, vCenter 5.5 and MS.SQL 2008
Express.
The problem is the Database Log is full and I already solve
this problem as following;
Purging old data from the database used by vCenter Server
https://kb.vmware.com/s/article/1025914 but
is still cannot solve it so I have a question as below.
1. After the Purge has been restored, we get available space
at 10-15 MB. Is there another method to get more space?
2. From the table of the database as attached picture, which
column, row or data that I can delete in order to get more space? please kindly
advice.
Hello,
Running vCenter Server Appliance 6.5
This morning I changed vCenter SSO Identity Source from Active Directory as an LDAP Server to Active Directory (Integrated Windows Authentication using machine account for security reason. One of the AD user accounts is getting locked out like every 2 seconds. User account getting locked was managing the VMware environment before I came aboard. All other AD user accounts added to the vCenter are working fine.
On the Domain Controller, the sources of the machine that getting the account is vcenter server with its IP address. I am stuck what to look for and what in vCenter is causing this lockout.
Appreciate your help on this issue.
Thanks,
Hi everyone,
I noticed that VCSA 6.7.0.14000 appliance management GUI (port 5480) would show blank graphs for CPU, RAM and Network. Digging deeper I found an anomaly other than blank graphs. The disk monitor status shows NaN for all disks?
Anyone have any suggestions? Other than this VCSA works with no identifiable defects. This is a brand new install straight from the executable installer. No upgrades, no prior versions. The health status is green on all categories and the VM's usage as seen from ESXi is minimal.
Here's the details on this installation:
Type: vCenter Server with an embedded Platform Services Controller
Product: VMware vCenter Server Appliance
Version: 6.7.0.14000 Build number 9451876
Thank you
This happened after my vCenter has restarted yesterday, before vCenter was restarted I can get all stat normally so why the metric counter doesn't exist and how to fix this?
Here's my environment and error log from PowerCLI.
My environment contains 1 vCenter(6.7.0.10000) and 1 ESXi
Get-Stat : 1/24/2019 11:36:02 AM Get-Stat The metric counter "mem.usage.average" doesn't exist for entity "PCMS".
At line:1 char:21
+ Get-VM -Name PCMS | Get-Stat -IntervalMins 1440
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : ResourceUnavailable: (mem.usage.average:String) [Get-Stat], VimException
+ FullyQualifiedErrorId : Client20_RuntimeDataServiceImpl_CheckUserMetrics_MetricDoesntExist,VMware.VimAutomation.ViCore.Cmdlets.Commands.GetViStats
Get-Stat : 1/24/2019 11:36:02 AM Get-Stat The metric counter "net.usage.average" doesn't exist for entity "PCMS".
At line:1 char:21
+ Get-VM -Name PCMS | Get-Stat -IntervalMins 1440
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : ResourceUnavailable: (net.usage.average:String) [Get-Stat], VimException
+ FullyQualifiedErrorId : Client20_RuntimeDataServiceImpl_CheckUserMetrics_MetricDoesntExist,VMware.VimAutomation.ViCore.Cmdlets.Commands.GetViStats
Hello.
We have some infrastructure looks like:
vCenter: vCenter 5.5 Appliance 3721164( vCenter Server 5.5 Update 3d)
ESXi x2:VMware ESXi 5.5.0 build-356872 ((Updated) Vmware-ESXi-5.5.0-2068190-custom-Cisco-5.5.2.3)
We are using this infrastructure for some our network monitoring.
Our goal is vSphere 6.7 U1
According to this matrices we should perform this upgrade is 2 waves:
Today and yesterday we tried upgraded this vCenter by ISO:
VMware-VCSA-all-6.5.0-9451637
But looks like was some problem with hostname and DNS record
During upgrade i received warning:
"Warning
This ESXi host[10.x.x.35]is managed by vCenter Server[10.x.x.40].
Resolution
Make sure the cluster where this ESXi host resides is not set to Fully Automated DRS for the duration of the upgrade process.
Warning
Host name localhost.localdom is not DNS resolvable, but matches the machine certificates. If you do not configure a valid DNS resolvable hostname mapping, then you might not be able to connect to the vCSA afterwards
Description
Host name localhost.localdom is not DNS resolvable, but matches the machine certificates. If you do not configure a valid DNS resolvable hostname mapping, then you might not be able to connect to the vCSA afterwards
Resolution
Update appliance /etc/hosts or /etc/resolv.conf file to properly access DNS servers or update appliance DNS servers with the proper host name mapping or configure right network configuration on eth0. To check if DNS server has record about local host name, execute `dig localhost.localdom +short` locally on the appliance, or `nslookup localhost.localdom` on a windows machine."
And now after succesfull upgrade and migration process to new appliance we have situation:
When we are using adress for vCenter IP or DNS nane:
( example: https://10.x.x.40/ui or https://vcenter.mydomain.local:9443/ ) next browser is converting this IP for:
I checked hostname for this vcenter before upgrade and after and is configured localhost.localdom
DNS record was before and we have now this same: vcenter.mydomain.local for IP: 10.x.x.40
Looks like DNS record is not that same how hostname…
We use this KB for upgrade too https://kb.vmware.com/s/article/2110772
During investigation we found that option from this KB "Certificate regeneration enabled" had options YES for yesterday upgrade. Today we change this option to NO and start upgrade. Then looks like upgrade is not working for both options.
What solution we have in this situatin to proper perform this upgrade ?
From my perspective we can:
Build new vCSA 6.5u2 and reconnect ESXi 5.5u3 to this vCSA.
Upgrade ESXi 5.5u2 to 6.5u2
Upgrade vCSA and ESXi 6.5u2 to 6.7u1
additional what i found but not tested yet is:
www.virtualvmx.com/2018/05/changing-fqdn-of-vcenter-appliance.html (not supported) and maybe according to this KB (VMware Knowledge Base ) regenerate certificate after hostname change...
but this is workaround... Maybe is some other supported resolution ?
Cheers
Sebastian
vSebastian.net
I'm converting a physical openSUSE 11.1 machine and receive the following error:
--> }
2019-01-24T10:06:04.823-05:00 verbose converter-gui[10764] [Originator@6876 sub=ConverterDataProviderImpl] Converter::Client::Gui::Wizard::ConverterDataProviderImpl::PropertyCollectorThread[14] - (vmodl.query.PropertyCollector.UpdateSet) {
--> version = "14",
--> filterSet = (vmodl.query.PropertyCollector.FilterUpdate) [
--> (vmodl.query.PropertyCollector.FilterUpdate) {
--> filter = 'vmodl.query.PropertyCollector.Filter:session[52ddbdd9-aa93-38e0-1f7f-cc54e887400e]5235eee5-c532-9c76-53aa-ab3212e793f7',
--> objectSet = (vmodl.query.PropertyCollector.ObjectUpdate) [
--> (vmodl.query.PropertyCollector.ObjectUpdate) {
--> kind = "modify",
--> obj = 'converter.task.Task:task-4',
--> changeSet = (vmodl.query.PropertyCollector.Change) [
--> (vmodl.query.PropertyCollector.Change) {
--> name = "event[72]",
--> op = "add",
--> val = (converter.event.UnixP2VDiskPartitionFailedEvent) {
--> key = 72,
--> chainId = 64,
--> type = "error",
--> createdTime = "2019-01-24T15:06:04.820107Z",
--> userName = "Administrador",
--> fullMessage = "Unable to partition the destination disks.",
--> job = <unset>,
--> reason = (converter.fault.CloneFault) {
--> faultCause = (vmodl.MethodFault) null,
--> description = "Failed to find matching disk device for VMODL Param Disk #0, 1447909153, controller: scsi, bus ID: 0, and unit ID: 0",
--> msg = "An error occurred during the conversion: 'Failed to find matching disk device for VMODL Param Disk #0, 1447909153, controller: scsi, bus ID: 0, and unit ID: 0'"
--> }
--> }
--> }
--> ],
--> }
--> ],
--> }
--> ],
--> truncated = <unset>
--> }
Does anyone know how I can resolve this please?
I have a PowerShell script that I use to deploy vCSA. It generates the JSON template file for the vcsa-deploy.exe to use as an answer file.
The JSON being produced has worked perfectly fine with the vcsa-deploy.exe file from vCSA 6.0 and 6.5 media.
I tried today with the latest 6.7 media from the VMware-VCSA-all-6.7.0-10244745.iso and the syntax validator is tripping up all over the place.
PowerShell by default escapes certain characters, such as the apostrophe, within a string value - it replaces it with a \u0027 - which is valid JSON. I know that the apostrophe does not need to be escaped since it is enclosed in double-quotes, but for some reason PowerShell decides to do it anyway. (I know how to make PowerShell not do that.) But the previous JSON syntax validator from 6.0 and 6.5 media had absolutely no issue with this escape sequence. The new syntax validator does not like the backslash and feels it should have been escaped itself.
The other issue - and the one way more pressing - is that the JSON validator for 6.7 keeps failing a completely valid JSON file. It is being rejected because of the last closing curly bracket:
Here is the error message:
====== [START] Start executing Task: To validate CLI options at 15:45:37 ====== |
Command line arguments verfied. |
[SUCCEEDED] Successfully executed Task 'CLIOptionsValidationTask: Executing CLI |
optionsValidation task' in TaskFlow 'template_validation' at 15:45:37 |
SyntaxValidationTask: Executing Template Syntax Validation task |
[START] Start executing Task: To validate the syntax of the template. at 15:45:37 |
Template syntax validation failed for template |
C:\Users\OSCHRO~1\AppData\Local\Temp\vcsainstall-20181023-154534.json. |
Error: Redundant character. Cause: The character '}' on line 45 (character 1) is |
possibly redundant. Resolution: Consider removing the character '}'. |
================ [FAILED] Task: SyntaxValidationTask: Executing Template Syntax |
Validation task execution failed at 15:45:37 ================ |
Task 'SyntaxValidationTask: Executing Template Syntax Validation task' execution |
failed because [Error: Redundant character. Cause: The character '}' on line 45 |
(character 1) is possibly redundant. ], possible resolution is [Consider |
removing the character '}'.] |
The character the syntax validator is complaining about, is the very last curly bracket that needs to be there. I triple checked the JSON file to make sure I don't have an errand bracket, and it does not.
To me this sounds like the syntax validator has a bug. Does anyone have any insight?
Hello Guys,
I just upgraded my vcenter server 5.5 to VCSA 6.5. The upgrade was done successfully except few things. In the second stage of migration I was asked to enter AD domain credential but it gave me an error stating that do you want to deploy it from scratch or continue with the deployment? I selected continue and after that the deployment was complete but the AD domain was disconnected. Can someone provide me how can I avoid this error? I later joined the domain but what can I do to avoid that in the first place. Second error I encountered was that on one of my host earlier I had nine alerts stating that the disk has failed on one of the. After upgrade to vcsa I get 10 alerts . The alert is "Vmware Rollup Health State". Can some one give me an explanation of what Vmware Rollup Health State is and why I am getting this now. Is it an additional feature of Vcenter 6.5?
Thank you
I am building the VM machine on a vCenter 6.5. Curious as to what the Guest Operating Systems selection should be. I have chosen "Linux - Centos 7 (64 bit)" option. There is another choice for "Centos 4/5 or later (64bit)".
In the past, I have chosen other, etc.
Tt
Hello,
I've been banging my head trying to fix this issue with a Linux conversion. I've searched the net high and low, nothing seems to fix the problem. I've attached the Converter log files. The included lines below are the last few of the worker log. I've highlighted in red the possible problem areas, but none of the "fixes" seem to work. Any help is greatly appreciated!
--> [2019-01-24 08:34:29,521 INFO bootLoader ]: Command '/usr/sbin/grub2-install --version' returned:
--> [2019-01-24 08:34:29,521 INFO bootLoader ]: --> /usr/sbin/grub2-install (GRUB) 2.02~beta2
--> [2019-01-24 08:34:29,521 INFO bootLoader ]: PopulateBootLoaderType: Detected GRUB version as GRUB2
--> [2019-01-24 08:34:29,521 WARN bootLoader ]: ResolveSymbolicLink: Cannot find /boot/grub/grub.cfg
--> [2019-01-24 08:34:29,521 INFO bootLoader ]: Looking for grub.cfg in /boot
--> [2019-01-24 08:34:29,523 INFO bootLoader ]: Command 'find /boot -name grub.cfg' returned:
--> [2019-01-24 08:34:29,523 INFO bootLoader ]: --> /boot/grub2/grub.cfg
--> [2019-01-24 08:34:29,523 INFO bootLoader ]: PopulateLoaderConfigFile: Found /boot/grub2/grub.cfg
--> [2019-01-24 08:34:29,523 INFO bootLoader ]: File '/tmp/vmware-sysinfo-grub-device.map' does not exist.
--> [2019-01-24 08:34:29,523 INFO bootLoader ]: Trying to create device map file /tmp/vmware-sysinfo-grub-device.map
--> [2019-01-24 08:34:29,523 INFO bootLoader ]: Running command: grub --batch --no-floppy --device-map=/tmp/vmware-sysinfo-grub-device.map > /dev/null 2>&1
--> [2019-01-24 08:34:29,525 INFO bootLoader ]: Writable command 'grub --batch --no-floppy --device-map=/tmp/vmware-sysinfo-grub-device.map > /dev/null 2>&1' succeeded.
--> [2019-01-24 08:34:29,525 ERROR bootLoader ]: Unable to open file: /tmp/vmware-sysinfo-grub-device.map
-->
2019-01-24T08:34:32.233-08:00 info vmware-converter-worker[05332] [Originator@6876 sub=Default] Converter Agent SysinfoQuery obtained XML output
2019-01-24T08:34:32.233-08:00 info vmware-converter-worker[05332] [Originator@6876 sub=Default] Caching vmware-sysinfo XML output with key LiveLinuxComputer::GetSysinfoXml=e27b3b56c443a35fe5b22d7650c1d9e0c9d03053
2019-01-24T08:34:32.239-08:00 warning vmware-converter-worker[05332] [Originator@6876 sub=Default] No volume for partition /dev/xvda2
2019-01-24T08:34:32.239-08:00 error vmware-converter-worker[05332] [Originator@6876 sub=Default] No disks for volume with id '/dev/rhel/root' and label ''
2019-01-24T08:34:32.239-08:00 info vmware-converter-worker[05332] [Originator@6876 sub=Default] Scheduled timer canceled, StopKeepAlive succeeds
2019-01-24T08:37:05.620-08:00 info vmware-converter-worker[05968] [Originator@6876 sub=Default] [Converter.Worker.DiagnosticManagerImpl] Generating LogBundle.
Hi,
from time to time the VCSA 6.5e statsmonitor service stops unexpectedly. This breaks the ability to backup VCSA data via PowerCLI script. Another consequence is that there are no CPU/Memory/Database Statistics collected in VCSA management backend.
vRealize LogInsight Log excerpt is attached for the considered timeframe and filtered by "statsmonitor". I cannot tell from this log why it tried to add this service, tried to start it and then failed.
So the stop occurred on June, 13th for the last time. It remained stopped since then. Before June, 13th, I realized it and fixed it on June, 8th.
I see this problem occurring one one of our VCSA 6.5 instances but not on the other ones.
Does anyone else see this behavior or any idea what's wrong?
I'm not really sure when I started, I think with 6.7, but I realized it when troubleshooting automatic backups couldn't be setup.
Every time I restart the VCSA, I have tu manually start VMware Appliance Monitoring Service through the Appliance Management UI, or through the console. It starts with no issue manually, but not at boot.
The service is correctly set as Automatic.
Not sure where this service is logged, any idea?
Hi,
I did an update of vcenter appliance from 6.5U1g to 6.5U2c . Now I see many hosts reporting issues with vSphere HA agent - cannot be installed or configured.
If I try to turn off HA on the cluster, I get the following error:
License not available to perform the operation.
The license may not include some features. Make sure the License Service is available.
After rebooting one esxi host, I cannot connect it to the cluster:
Cannot complete the license assignment operation
Can not assign a license to "Host" xxxx. Make sure the License Service is available.
The only change was this update to 6.5 9451637 (u2c) from 6.5 U1g.
Anyone has seen something like this?
WMware ESXI 6.5
Serveral hosts.
One Host drop one of its network adapters then can back without any ip address range Show No Networks
See image below How do I get the ip addresses back on this adapter?
