Hi, I have vCenter 6.5 running on one ESXI, I have some requirement in which I have to change vCenter interface name eth0 to bond0. I check for the file in /etc/sysconfig/network and /etc/syscon...
See more...
Hi, I have vCenter 6.5 running on one ESXI, I have some requirement in which I have to change vCenter interface name eth0 to bond0. I check for the file in /etc/sysconfig/network and /etc/sysconfig/network-scripts but didn't get any configuration related to eth0 ( looking for ifcfg-eth0). I was planning to change file name ifcfg-eth0 to ifcfg-bond0, will this be okay ? Thanks.
Hi All, I have upgraded my ESXI and vCenter from 5.5 to 6.5, After upgrading to ESXI 6.5.0 build no. 5310538 I have applied a security patch which upgrade the ESXI to 6.5.0 build no 7388607. ...
See more...
Hi All, I have upgraded my ESXI and vCenter from 5.5 to 6.5, After upgrading to ESXI 6.5.0 build no. 5310538 I have applied a security patch which upgrade the ESXI to 6.5.0 build no 7388607. So, is it possible I can roll back to ESXI 5.5 again? As I know I can rollback to previous version only that would be 6.5.0 build no. 5310538. Thanks
Hi, I am about to install patch on one host having ESXI 6.5 version. I know both update manager and command line option to install/upgrade patch. I also know that VMware recommend to upgrade ...
See more...
Hi, I am about to install patch on one host having ESXI 6.5 version. I know both update manager and command line option to install/upgrade patch. I also know that VMware recommend to upgrade the patch instead of installing the patch. My Question is that how I we can rollback the recently upgraded patch ? Alok
Actually My scenario is, vCenter 5.5 has hostname/FQDN "localhost.localdom", I think it was left default during 5.5 deployment. Suppose I'll upgrade to 6.5 then FQDN will not change, localhost.lo...
See more...
Actually My scenario is, vCenter 5.5 has hostname/FQDN "localhost.localdom", I think it was left default during 5.5 deployment. Suppose I'll upgrade to 6.5 then FQDN will not change, localhost.localdom will set for 6.5 as well. So I have only choice to make entry in Local DNS for localhost.localdom.
thanks for the reply. I checked FQDN localhost.localdom is coming from vCenter 5.5 configuration during migration. I remember we don't provide FQDN ( incase we need to give new FQDN) in migrat...
See more...
thanks for the reply. I checked FQDN localhost.localdom is coming from vCenter 5.5 configuration during migration. I remember we don't provide FQDN ( incase we need to give new FQDN) in migration steps. Even I redeploy this vCenter It will be same situation.
After setting DNS, is there any way I can assign FQDN or I need to reinstall the vCenter? Pls Keep in mind that I have upgraded it from 5.5. Thanks for the support.
@daphnissov thanks for the reply. I am sure you are referring vCenter Server Appliance Management Interface ( VMAI) , I am able to open and login UI using URL https://<IP>:5480. I am able to...
See more...
@daphnissov thanks for the reply. I am sure you are referring vCenter Server Appliance Management Interface ( VMAI) , I am able to open and login UI using URL https://<IP>:5480. I am able to do SSH in vCenter. Thats is why I am looking for Cli option. Another thing I want to add that I am working in LAB environment, so setting FQDN will not serve the purpose as it will be not resolved.
Hi, I have upgrade vCenter 5.5 to 6.5 successfully , I am facing issue while opening the vsphere web client GUI When try to open GUI using below URL it is being redirected to other URL ...
See more...
Hi, I have upgrade vCenter 5.5 to 6.5 successfully , I am facing issue while opening the vsphere web client GUI When try to open GUI using below URL it is being redirected to other URL https://XXX.XXX.XXX.XXX/vsphere-client/ is redirecting to https://localhost.localdom/websso/SAML2/SSOSSL?RelyingPartyEntityId=aHR0cHM6Ly8xOTIuMTY4LjEzNC4yNDgvdnNwaGVyZS1jbGllbnQv… How I can disable this behaviour and login using IP not FQDN. Thanks for the support
