indeed, this workaround worked Thank you very much, you have unlocked us !!!!!!!!
↧
Re: Application assignment
↧
ESXi 6.7 - NTP time drifting on one host
I have (2) ESXi 6.7 hosts setup to use the same NTP server (time.nist.gov). One host keeps the time fine, even though sometimes the logs will display a warning that it has lost connection to the NTP server. The other host loses time gradually. When I noticed the problem, I simply restarted the NTP Daemon and the time was corrected and in sync with the first host.
One week later, there is a 5 second difference between the 2 hosts. The NTP service is configured exactly the same on both hosts. Any suggestions on what I should try next? I figured I'd try the forums before contacting support.
↧
↧
Re: Cannot update Skyline
Hello KennyNoah,
Welcome to Skyline Communities !!!
Kindly follow the below-mentioned steps to isolate the issue and upgrade Skyline.
- Reboot the appliance (Skyline health services are needed to be started for the upgrade to initiate thereby all the required services are started.)
- Check the communicate status from Skyline to the VMware VAPP web
- Connect to the Skyline virtual machine collector using the VM console
- Login with root credentials
- Execute the command: curl -v https://vapp-updates.vmware.com:443
- Once executed you should see the connection status of the certificate to be Ok.
- If the certificate validation is not complete, then check the firewall rule and make sure Skyline Appliance is able to communicate on the network to vapp-update.vmware.com over port 443.
↧
Re: Alarm Definitions
LUCD
Yes that did it.
All the Alarm Rules are now set with my email address.
The Reset Rule is still not set
We need to make that change also
Thanks almost there.
↧
vSAN Streched cluster Preferred Fault Domain set to Null
Hi, we have been dealing with some issues in out vSAN Streched cluster when some VMs disappeared from inventory and from vSAN Datastore. When we took a deep look, the used space in the datastore didn't change. weird.
After some troubleshooting we manage to see the cluster Preferred Fault Domain was set to Null. We resolved the issue by disconnecting cluster Master vSAN VMKernel and rebooting al the host one by one.
My question is: Why would this happen? What are possible causes for that to happen?
↧
↧
Re: Alarm Definitions
PS C:\util> .\alarmv3.ps1
Exception calling "ReconfigureAlarm" with "1" argument(s): "A specified parameter was not correct: "
At C:\util\alarmv3.ps1:45 char:1
+ $alarm.ReconfigureAlarm($spec)
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [], MethodInvocationException
+ FullyQualifiedErrorId : VimException
Back to same error as before.
need log file again?
↧
Re: vSAN Streched cluster Preferred Fault Domain set to Null
Hello Lucas,
"some issues in out vSAN Streched cluster when some VMs disappeared from inventory and from vSAN Datastore."
So my first question would be what exactly do you mean by "disappeared", do you mean unavailable/inaccessible or permanently gone? - the only legitimate times I have seen such things (e.g. excluding something or someone deleting stuff) is when people have data Objects stored as FTT=0 (almost exclusively unknowingly) and lose a Disk/Disk-Group, aside from this it should be clear what happened to the data.
I would strongly advise to open a Support Request with vSAN GSS if this is not well understood already.
"Why would this happen? What are possible causes for that to happen?"
I would start with checking do you have leftover stale CMMDS entries from replaced Witness(es), from Master/Backup node (*should* be the same) this can be checked with:
# cmmds-tool find -t PREFERRED_FAULT_DOMAIN
# cmmds-tool find -t HOSTNAME
Other than that, potentially there was some other issue with CMMDS, I can only really think of one (which is actually a long knock-on effect from issues causing /scratch to be unavailable) as issues in this area are exceedingly rare (which they SHOULD be as this service places a critical role).
Bob
↧
Re: Alarm Definitions
That would help.
But I don't need the complete log.
Search for the last occurrence of vim.alarm.Alarm.reconfigure.
From that line till the end of the file.
↧
Re: vSAN Streched cluster Preferred Fault Domain set to Null
Thanks Bob. What i mean by disappear is that the files were no longer mapped in vsan file system until the master was rebooted.
I agree with you, really strange scenario. VMware is still looking for a root cause
↧
↧
Re: Alarm Definitions
Found the last occurrence of vim.alarm.Alarm.reconfigure.
Put it was a long way down to the bottom so I zipped the file again
↧
Personal Certificate Store being wiped on Refreshes
Howdy all!
I have recently become hung up on something I am struggling to find the answer to. I'd love to get some feedback or ideas on what y'all think.
Short explanation: Certificates stored in the cert:\CurrentUser\My directory are being deleted after a user refreshes their environment (disconnect and log off).
Long explanation: I am looking towards using Adobe's built in Digital ID creation to create a means of method for digitally signing documents with a signature that cannot be deleted. The validity behind the signature does not carry as much weight as the fact of whether or not it can be deleted does within my organization. I would specifically like for a user to be able to use Adobe to create a digital ID to be stored in the 'windows certificate store.' This certficate ends up in the Personal folder under Current User in certmgr. If a user disconnects from their session, the Id remains and all is well, but as soon as a user disconnects and logs offs, the ID is deleted from the Personal certificate store, resulting in it also being deleted from Adobe. How can I go about preserving this certificate store?
Thanks,
JU
↧
Re: Alarm Definitions
I only see an old call where the transition spec green to red is still in there.
And there are no Verbose entries in the file.
↧
Re: Alarm Definitions
PS C:\util> $logLevel = Get-AdvancedSetting -Entity $global:DefaultVIServer -Name 'log.level'
PS C:\util> Set-AdvancedSetting -AdvancedSetting $logLevel -Value 'verbose' -Confirm:$false
Name Value Type Description
---- ----- ---- -----------
log.level verbose VIServer Logging level
PS C:\util> .\alarmv3.ps1
Exception calling "ReconfigureAlarm" with "1" argument(s): "A specified parameter was not correct: "
At C:\util\alarmv3.ps1:45 char:1
+ $alarm.ReconfigureAlarm($spec)
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [], MethodInvocationException
+ FullyQualifiedErrorId : VimException
PS C:\util> $log = Get-Log -Key 'vpxd:vpxd.log'
PS C:\util> $log.Entries | Out-File -FilePath .\vpxd.log
PS C:\util> Set-AdvancedSetting -AdvancedSetting $logLevel -Value $logLevel.Value -Confirm:$false
Name Value Type Description
---- ----- ---- -----------
log.level verbose VIServer Logging level
what I ran
↧
↧
Re: Alarm Definitions
I'm afraid I don't see the call in the log extract you attached.
↧
vRO Guest script manager Authentication errors
I am getting an error when trying to run a script through GSM. It is stating that "This operation requires an interactive win dow station"
The script is as follows.
Basically we are trying to mount a disk in windows to a specific drive letter and format it.
initialize-disk [driveNumber] ; new-partition -disknumber [driveNumber] -driveletter [driveLetter] -usemaximumsize | format-volume
Please let me know if you have any ideas to get around this.
Thanks,
Matthew
↧
Licence key
hi
i buy on auction licence key for VMware Workstation Pro 15 1 Dev
when i want to register product i get this info
what is going on?
↧
Re: Alarm Definitions
Line 108382 is the error
2020-06-03T13:06:32.736-04:00 info vpxd[40450] [Originator@6876 sub=Default opID=619b15f6] [VpxLRO] -- ERROR task-56900 -- alarm-272 -- vim.alarm.Alarm.reconfigure: vmodl.fault.InvalidArgument:
--> Result:
--> (vmodl.fault.InvalidArgument) {
--> faultCause = (vmodl.MethodFault) null,
--> faultMessage = <unset>,
--> invalidProperty = <unset>
--> msg = ""
--> }
--> Args:
-->
--> Arg spec:
--> (vim.alarm.AlarmInfo) {
--> name = "vSphere Health detected new issues in your environment",
--> systemName = "vSphere Health detected new issues in your environment",
--> description = "vSphere Health detected new issues in your environment",
--> enabled = true,
--> expression = (vim.alarm.OrAlarmExpression) {
--> expression = (vim.alarm.AlarmExpression) [
--> (vim.alarm.EventAlarmExpression) {
--> comparisons = (vim.alarm.EventAlarmExpression.Comparison) [
--> (vim.alarm.EventAlarmExpression.Comparison) {
--> attributeName = "curstatus",
--> operator = "equals",
--> value = "skipped"
--> }
--> ],
--> eventType = "vim.event.EventEx",
--> eventTypeId = "vsphere.online.health.alarm.event",
--> objectType = <unset>,
--> status = "green"
--> },
--> (vim.alarm.EventAlarmExpression) {
--> comparisons = (vim.alarm.EventAlarmExpression.Comparison) [
--> (vim.alarm.EventAlarmExpression.Comparison) {
--> attributeName = "curstatus",
--> operator = "equals",
--> value = "green"
--> }
--> ],
--> eventType = "vim.event.EventEx",
--> eventTypeId = "vsphere.online.health.alarm.event",
--> objectType = <unset>,
--> status = "green"
--> },
--> (vim.alarm.EventAlarmExpression) {
--> comparisons = (vim.alarm.EventAlarmExpression.Comparison) [
--> (vim.alarm.EventAlarmExpression.Comparison) {
--> attributeName = "curstatus",
--> operator = "equals",
--> value = "unknown"
--> }
--> ],
--> eventType = "vim.event.EventEx",
--> eventTypeId = "vsphere.online.health.alarm.event",
--> objectType = <unset>,
--> status = "gray"
--> },
--> (vim.alarm.EventAlarmExpression) {
--> comparisons = (vim.alarm.EventAlarmExpression.Comparison) [
--> (vim.alarm.EventAlarmExpression.Comparison) {
--> attributeName = "curstatus",
--> operator = "equals",
--> value = "info"
--> }
--> ],
--> eventType = "vim.event.EventEx",
--> eventTypeId = "vsphere.online.health.alarm.event",
--> objectType = <unset>,
--> status = "green"
--> },
--> (vim.alarm.EventAlarmExpression) {
--> comparisons = (vim.alarm.EventAlarmExpression.Comparison) [
--> (vim.alarm.EventAlarmExpression.Comparison) {
--> attributeName = "curstatus",
--> operator = "equals",
--> value = "yellow"
--> }
--> ],
--> eventType = "vim.event.EventEx",
--> eventTypeId = "vsphere.online.health.alarm.event",
--> objectType = <unset>,
--> status = "yellow"
--> },
--> (vim.alarm.EventAlarmExpression) {
--> comparisons = (vim.alarm.EventAlarmExpression.Comparison) [
--> (vim.alarm.EventAlarmExpression.Comparison) {
--> attributeName = "curstatus",
--> operator = "equals",
--> value = "red"
--> }
],
--> eventType = "vim.event.EventEx",
--> eventTypeId = "vsphere.online.health.alarm.event",
--> objectType = <unset>,
--> status = "red"
--> }
--> ]
--> },
--> action = (vim.alarm.GroupAlarmAction) {
--> action = (vim.alarm.AlarmAction) [
--> (vim.alarm.AlarmTriggeringAction) {
--> action = (vim.action.SendEmailAction) {
--> toList = "systems-alert@tgcsnet.com",
--> ccList = "",
--> subject = "vSphere Health detected new issues in your environment",
--> body = ""
--> },
--> transitionSpecs = (vim.alarm.AlarmTriggeringAction.TransitionSpec) [
--> (vim.alarm.AlarmTriggeringAction.TransitionSpec) {
--> startState = "green",
--> finalState = "yellow",
--> repeats = false
--> },
--> (vim.alarm.AlarmTriggeringAction.TransitionSpec) {
--> startState = "green",
--> finalState = "red",
--> repeats = false
--> }
--> ],
--> green2yellow = false,
--> yellow2red = false,
--> red2yellow = false,
--> yellow2green = false
--> }
--> ]
--> },
--> actionFrequency = 0,
--> setting = (vim.alarm.AlarmSetting) {
--> toleranceRange = 0,
--> reportingFrequency = 0
--> },
--> alarmMetadata = <unset>,
--> key = "alarm-272",
--> alarm = 'vim.alarm.Alarm:alarm-272',
--> entity = 'vim.Folder:group-d1',
--> lastModifiedTime = "2020-02-15T16:55:21.644999Z",
--> lastModifiedUser = "VSPHERE.LOCAL\vpxd-extension-71bf5384-39f9-4785-b5cb-372cce80f1c2",
--> creationEventId = 0
--> }
2020-06-03T13:07:12.702-04:00 info vpxd[41264] [Originator@6876 sub=Default opID=sps-Main-649934-370-43] [VpxLRO] -- ERROR session[523133b2-2d8b-b2fd-486b-33e4e9fc0e74]52ad8409-016c-619b-6193-5460b785ca96 -- CatalogSyncManager -- vim.vslm.vcenter.CatalogSyncManager.queryCatalogChange: vim.fault.NotFound:
--> Result:
--> (vim.fault.NotFound) {
--> faultCause = (vmodl.MethodFault) null,
--> faultMessage = <unset>
--> msg = "The object or item referred to could not be found."
--> }
--> Args:
-->
--> Arg catalogChangeSpec:
--> (vim.vslm.CatalogChangeSpec) {
--> datastore = 'vim.Datastore:ds:///vmfs/volumes/5d629aba-2f383bce-c113-000af7a052c4/',
--> startVClockTime = (vim.vslm.VClockInfo) {
--> vClockTime = 1
--> },
--> fullSync = false
--> }
2020-06-03T13:07:12.704-04:00 warning vpxd[41431] [Originator@6876 sub=VpxProfiler opID=TaskLoop-host-3030] InvokeWithOpId [TotalTime] took 2566 ms
2020-06-03T13:07:12.736-04:00 info vpxd[41269] [Originator@6876 sub=Default opID=sps-Main-649934-370-f4] [VpxLRO] -- ERROR session[523133b2-2d8b-b2fd-486b-33e4e9fc0e74]522ce5b9-b83b-c3a9-43ac-c424169e589f -- CatalogSyncManager -- vim.vslm.vcenter.CatalogSyncManager.queryCatalogChange: vim.fault.NotFound:
--> Result:
--> (vim.fault.NotFound) {
--> faultCause = (vmodl.MethodFault) null,
--> faultMessage = <unset>
--> msg = "The object or item referred to could not be found."
--> }
--> Args:
-->
--> Arg catalogChangeSpec:
--> (vim.vslm.CatalogChangeSpec) {
--> datastore = 'vim.Datastore:ds:///vmfs/volumes/5d5de123-31532546-1805-000af73fc80c/',
--> startVClockTime = (vim.vslm.VClockInfo) {
--> vClockTime = 1
--> },
--> fullSync = false
--> }
↧
↧
Re: Esxi 6.5.0 Update 3 guest console not working
I am using IP address to access the esxi. I can open the webgui with no issue.
↧
Re: ESXi 6.7 - NTP time drifting on one host
If you ensure about the ESXi hosts have the same version and build number, and both of them have similar hardware platform, and NTP configuration is same, please check the NTP synchronization network traffics to find-out what's going on both of your hosts, via shell/SSH access:
tcpdum-uw -i vmk0 host x.y.z.w and port 123
Also, you can check the time settings via cat /etc/ntp.conf file. I explain about how to troubleshoot the ESXi NTP settings, in the following link:
↧
Re: Alarm Definitions
But that code only contains 2 transition specs, including the one with green to red.
Perhaps your latest version of the script doesn't correspond with what I posted last.
↧