I notice today when I login to a host, the prompt no longer reads "root@esxhost1". It now reads "root@?". Any thoughts on how to fix this. I checked the /etc/sysconfig/network file and it looks correct. I have not rebooted the host as it ius in production.
Charles Killmer, VCP
If you found this or other information useful, please consider awarding points for "Correct" or "Helpful".
That's weird perhaps, what happen if you use "hostname esxnameindnsentry" and exit and log back in to see if it works? Does it reply with hostname if you do nslookup against it?
If you found this information useful, please consider awarding points for "Correct" or "Helpful". Thanks!!!
Regards,
Stefan Nguyen
VMware vExpert 2009
iGeek Systems Inc.
VMware, Citrix, Microsoft Consultant
what happens if you type hostname at the prompt?
weird indeed.
what does DNS and Routing within the VIC show by name?
maybe restart hostd?
service mgmt-vmware restart
Do you have console access to see the main splash screen of the host?
That's weird perhaps, what happen if you use "hostname esxnameindnsentry" and exit and log back in to see if it works? Does it reply with hostname if you do nslookup against it?
If you found this information useful, please consider awarding points for "Correct" or "Helpful". Thanks!!!
Regards,
Stefan Nguyen
VMware vExpert 2009
iGeek Systems Inc.
VMware, Citrix, Microsoft Consultant
This fixed it. Wonder why it was incorrect.
Thanks
Charles Killmer, VCP
If you found this or other information useful, please consider awarding points for "Correct" or "Helpful".
be careful though, that may only be a temp fix.
Outlined in Changing the IP address, default gateway, and hostname of the Service Console in ESX 3.0.x
>Changing the hostname without rebooting
>To dynamically change the hostname, run the command:
>root@server root# hostname newname
>Note: This command creates a temporary hostname change. This change is lost when the system is rebooted
Thanks, I will keep an eye on it when it reboots. Won't be an issue for long as we are preparing to upgrade to vSphere 4.
Charles Killmer, VCP
If you found this or other information useful, please consider awarding points for "Correct" or "Helpful".