Jitu211003's Accepted Solutions

No no. It gives me options and i put everything. But once deployed. It ask me to configure the ip using vami_config_net  script under /opt/share/vmware/vami/ However, i deployed it again today and it is working fine.

Hi, I faced the same issue wherein storage went down unexpectedly and when it came online, 2 of 3 LUNs became inactive. What we tried Rescan serivce restart on host we rebooted the host. and finally took a graceful reboot of the storage controller one by one which fixed this issue. I had ESXi 5.0 with HP MSA storage DAS box. Thanks Vmwarediary.com/vmwarediary.in

Its been resolved by Vmware as this is bug in SSO login in the SRM 5.x & 6.0. As a workaround you need to add individual id to the SSO login administrators group on both site. https://kb.vmware.com/s/article/2095342 Vmwarediary.com

Yes, Data will be useless at recovery site as you wont be able to power on those VMs. It may happen to all of the VMs and may happen with most of the VMs. The VMs which has been replicated successfully those will be powered up only.

Hi, The error indicates that you are using an unsupported SRM. Go through the compatibility matrix of Vmware and make sure your Vcenter version is support with SRM version. Thanks Vmwarediary.com

Hi, Either you have added the NIC in unsued or standby of vswitch. Share the pic of Vswitch configuraiton. Else it should work with one NIC also. For more visit vmwarediary.com or vmwarediary.in Thanks

Hi Pranay, In 6.0 this settings is disabled by default for some reason, however you can do it on each port group basis individually. As per VMware, this is by design. You will not find this option on uplink port group when you login into webclient as this is now on port group basis. VMware should remove this option even from Vsphere client. Hope, this will solve your query.

Hi Below is the script for tools installation on windows PCs but i need to test it. That will take some time. Hope, till now you have got the required info, do not forget to mark this resolved. Connect-VIServer 192.168.0.106 $GuestCred = Get-credential Administrator $VM = Get-content "c:\hi.txt" #Mount vmware tools media mount-tools -vm $VM #Find the drive letter of the mounted media $DrvLetter = Get-WmiObject -class 'win32_CDROMDrive' ` -ComputerName $VM.Name ` -Credential $GuestCred | Where-Object {$_.Volumename -match "VMware Tools"} | Select-object -ExpandProperty Drive #Build our cmd line $cmd = "$($DrvLetter)\setup.exe /S /V`"/qn Reboot=ReallySuppress Addlocal=All`" #spawn a new process on the remote VM, and execute setup $go = Invoke-WmiMethod -path Win32_process` -Name Create` -Credential $GuestCred` -ArgumentList $cmdif ($go.Returnvalue -ne 0) { write-warning "Installer returned code $($go.ReturnValue)! Unmounting media" Dismount-Tools -VM $VM } else { Write-Verbose "Tool installation successfully triggered on` $($VM.Name) media will be ejected upon completion." }

In Tool upgrade, it will upgrade the tool then reboot but in hardware upgrade it will first shutdown the machine and then upgrade the hardware. In production environment, it is not recommended to make it via baseline as VMs may have issue and if it happed then you may come in trouble as many VMs will go down. However this process also takes the sanpshot before doing this but still not safer for a bulk of VMs. VA upgrade is for VMware virtual appliances like VCSA, Vsphere replicator and many other things.

Hi, See the command output df -h .  All data disk have right space allocated. In any case if you find any data disk lesser than its actual size then increase the size up to the original then your admin state will be removed. Thanks

Hi, As per logs, it shows that someone logged in ESXi host via putty with root user then hit the command dcui. Then he or she restarted the host refer the below two line. User dcui@127.0.0.1 logged in as VMware-client/5.1.0 info 13/05/2017 05:15:02 dcui User root@127.0.0.1 logged in as info 13/05/2017 05:13:11 root Adding/enabling firewall rules logs are generated with user name when any specific user make any changes or without user name when esxi host reboots and come up online. It refresh the firewall rules itself during the boot. So no worry about the logs. Just find out who rebooted and what was the reason. Thanks, Hope, it sorted out your query. Do not forget to mark it.