I cloned a RedHat OS VM using VMSphere Client and the IP address is now the same on both VMs. How can I set/change the IP address of the cloned VM? I've checked several sources but couldn't see any resolution to this problem eg. http://discussions.citrix.com/topic/237224-changing-ip-address-after-cloning-vm/
This question would be better for ServerFault.
With that said, if the address is static, you will need to update your interface configuration file. Use the ifconfig command to determine the interface name, this will be $interfaceName. You will now need to update the ip address in the /etc/sysconfig/network-scripts/ifcfg-$interfaceName. You want to update the IPADDR field. See the Redhat docs here: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/s1-networkscripts-interfaces.html.
VMware does not handle the IP addressing, the VM will handle this itself. The reason you have the same IP address is because the file is exactly the same on both VMs. You will also need to update the MAC address in VMware under the network settings tab.
Edit:
From the VMware KB, "The /etc/udev/rules.d/70-persistent-net.rules may also need to be updated to the new MAC address." -http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2002767
I set BOOTPROTO=dhcp and ONBOOT=yes from /etc/sysconfig/network-scripts/ifcfg-eth0 followed by service network restart and that set a new IP address to the VM.
Related
I am migrating my vCenter Server 5.5 to a new server (databases have already been moved to a new SQL server and all is OK on existing vCenter Server 5.5 implementation). When I begin the simple install process on the new vCenter Server host the Single Sign-On component presents me with an IP address of 10.10.10.117 as the ip address of the FQDN file01.xxxxxxxxx.com. This is the iSCSI interface address. I need it to use the 10.1.1.17 ip address that is the address of the production NIC that the ESXi 5.5 hosts will be communicating with. I have already changed the binding order of the NIC cards and flushed the DNS cache. I also added file01.xxxxxxxx.com with the proper IP address to the hosts file and also file01 to the hosts file. Still, during the install, 10.10.10.117 is discovered. Thanks in advance! Babak C.
Just to get a quick clarification...are you freshly installing vCenter 5.5? Or are you migrating an existing vCenter server to a new host and using the update utility to upgrade? I am assuming you are doing a fresh install based on your details about the SQL server and SSO. Here is my suggestion, in case it is a fresh install.
We had a similar problem with 5.5 on a new install where the IP address that was discovered during the actual vCenter Server install was that of the public facing NIC which we never use for management traffic (it's for internet access on the vC server, for update manager, etc.)
The strange thing is that there had NEVER been an entry in ANY of our DNS servers for that interface. So, after looking into it a little bit, I started thinking the IP that was returned during install was not a DNS result at all. Rather, it was (most likely) simply gathered from the interfaces on the Server based on binding order (e.g. which NIC has the default gateway.)
In order to save having to uninstall and clean up a major mess if the install completed wrong, we stopped and got in touch with VMware support. They suggested we clear all of the temporary files both in the standard "temporary" folder on windows as well as under /ApplicationData/vmware/xxx, where 'xxx' would be whatever product is giving you trouble and HAS NOT been FULLY INSTALLED* (e.g. you started the install and noticed the incorrect IP, so you terminated the installer and there is metadata and cached files remaining from the partially run install).
Basically, what we had to do, was clear the temporary files and then make sure the NIC Binding Priority was correct (so you should check in Network Adapters|(press-alt)|Advanced Settings. Make sure the correct binding is checked (e.g. if you don't use IPv6 on the private network, clear it) and make sure that the Windows Network is at the top of the priority list on the second pane of the advanced settings. This helps tremendously with SSO by making sure the Windows Network stack is the first queried when you are signing in and SSO must submit a kerberos ticket to the AD DC for validation.
It is possible, that once you delete the partial install files and temporary files and fix the network settings (probably be a good idea to reboot as well), the next time you run the installer you might have success.
I will try to check this post later to see if it helped you at all... or it I just succeeded in making your life even more difficult (which I certainly hope not!) :)
One more thing...prior to initializing the installer, open up a PS session, perform ipconfig /flushdns and then ping the hostname of your vCenter server in order to get it in the DNS cache. You should also perform the following:
nslookup
NS>{your vcenter server IP address}
/* make sure the resulting hostname is correct..this ensures your PTRs and rDNS is working correctly. vCenter HEAVILY relies on accurate reverse DNS configuration...then do the following lookup for forward DNS */
NS>{your vcenter server FQDN}
Hope it helps. Best of luck my friend!
SIETEC
Win7 PC running Rails in an Ubuntu VM via VMWare Player. I'm working on a site and would like to show it to a friend who's outside my network.
I found this blog post, which got me very close: http://blog.fardad.com/2012/06/vmware-player-and-custom-nat-port-map.html
OK, so I have the VM that is using NAT. As I understand it, that means that the VM will appear to have the same IP address as the parent machine to outside traffic.
I went into NAT settings and added port forwarding:
Host Port: 8200 Type: UDP Virtual IP Address: 192.168.198.184:3000
OK so my understanding is that I should now be able to go to 192.168.1.1xx:8200 (the IP of my 'real' PC) and access the webserver running in the VM. But when I go to that address, I don't get anything. I can ping 192.168.198.184 (the VM) from the PC.
What I want to be able to do is go into my router and set up a port that will eventually forward into the VM.
It seems like I'm missing something very small but I don't know what that is. Help, please.
If anyone is curious how to get the Virtual Network Editor:
go to the vmware-directory and run in elevated cmd.exe-box
rundll32.exe vmnetui.dll VMNetUI_ShowStandalone
http://communities.vmware.com/message/2155960#2155960
Find the vmnetnat.conf file, usually located in
C:\ProgramData\VMware\vmnetnat.conf
or
C:\Users\Application Data\VMware\vmnetnat.conf
Edit vmnetnat, add similar line in the [incomingtcp] section
8200=192.168.198.184:3000
Restart VMware NAT Service.
Try using Bridged network option in vmware player instead of NAT. It replicates your physical network.
You can use an http proxy to do that, by doing that you don't need to expose your entire private network, check out this blog post for more information how to access docker containers from external devices
How to connect from a VMware guest (virtual) machine to the server installed on the host (physical) machine? Things like typing "localhost" in the address bar of a browser in a guest machine don't work. My host machine's OS is Windows 7 64 bit with WMware Workstation installed on it, if it matters.
EDIT: The Bridged network connection in combination with referring to 192.168.0.10* from the guest machine did work (replace * with a digit starting from 0 until it works).
If you use "Bridged" Network Connection (see Virtual Machine Settings: Network Adapter), your VM will be given an IP address on the same LAN as your host machine. At that point, you can just HTTP to your host's IP address, eg. http://192.168.0.100
You can also do that with the other options, but with NAT and Host-only (if I recall correctly) your host machine will appear to your guest machine to have a different IP address than its real LAN address. So Bridged is the easiest and is likely your best bet, unless you have some specific needs.
First thing to do: Check that you have the network up and running. Try to ping the host system or any web site from the console of the guest OS, let's say ping www.google.com.
If you received any answers then please try writing the IP number of the host machine in the addressbar of the browser on the guest machine (NOT localhost :P). You should be able to see any web service running (Tip: Open the console of your windows 7 and type ipconfig, then find the ethernet adapter corresponding to VMWare and you'll find the IP number of your host system).
If you didn't received any answer at all when you did ping then check the network configuration of VMWare to use Bridged Connection --at least that's how it works for me.
Good luck!
In a guest machine, localhost refers to the virtual machine itself. Refer to the host just as you would from any other machine: by its IP address.
Note that it may be using a second "virtual" network adapter to communicate with the guest. Check the VMware to find out, and to find the second IP address.
Just use the same IP sub net for your VMware machine, if your windows system has ip address class C 192.168.0.10 So assign 192.168.0.120 IP to your Vmware machine and make sure that Firewall allow the traffic in vmware and also add the listener port manually in vm machine. go to system - administration- firwal-add port 1521.
Thanks
I'm running vmware fusion and was wondering if its possible to to access the centos running on my virtual machine like I would access a regular server?
Maybe through ssh or an ip address?
Sure it is. On the virtual machine use ifconfig or ipconfigto find out the IP address it uses. You should be able to use that IP address.
Now, depending on the OS in the virtual machine, you may need to enable services, eg make sure you're running the needed daemon for ssh or enable telnet. Check the OS documentation (can you say "google?" for details.)
What is the best way to have a virtual operating system have a static IP address in VMWware. I would like to keep the IP address static since it is a virtual server.
You can configure VMware DHCP server [which runs on host OS] to assign a fix IP address to a VM each time.
According to vmware docs, configuration is stored at the following locations:
Windows XP
C:\Documents and Settings\All Users\Application Data\VMware\vmnetdhcp.conf
Windows Vista or Windows 7
C:\ProgramData\VMware\vmnetdhcp.conf
Linux (host-only)
/etc/vmware/vmnet1/dhcp/dhcp.conf
Linux (NAT)
/etc/vmware/vmnet8/dhcp/dhcp.conf
VMWare Fusion for Mac (host-only)
/Library/Preferences/VMware Fusion/vmnet1/dhcpd.conf
VMWare Fusion for Mac (NAT)
/Library/Preferences/VMware Fusion/vmnet8/dhcpd.conf
Static IP and DNS name by MAC example:
host ubuntu {
hardware ethernet 00:0c:29:c0:2c:58;
fixed-address 192.168.118.3;
}
For more details on this please see this blog post.
Assuming you're not using NAT-based VMWare networking, the answer isn't any different for a virtual (guest) server than for a real one. You can:
Assign a static IP via whatever mechanism the guest operating system supports.
Configure the guest operating system to get its IP address from a DHCP server, and configure the DHCP server to return a static IP address for the VMWare instance's MAC address.
If you want the VM slice / VM machine (guest) to have a static IP, assign it to the VM slice. Then on the VM Server select "Bridged" for the network adapter settings. This tells VMWare to use what ever IP settings you have established on the guest.
This works on my machine
Follow these simple steps. Takes just 5 minutes.
1. Note the MAC of the VM
2. On the host machine open C:\ProgramData\VMware\vmnetdhcp.conf
a. Or C:\Documents and Settings\All Users\Application Data\VMware\vmnetdhcp.conf
b. These 2 files are auto synced or mirrored.
c. Open the editor in Administrator mode. Eg notepad++. Otherwise you will get access denied message
3. Add a new entry at bottom of the configuration file, right before the "# End" marker. MyGuestVM is any unique name. Example below
host sunilW2008Server {
hardware ethernet 00-0C-29-05-2B-A0;
fixed-address 192.168.63.222;
}
3. Shutdown the VM and close the Workstation
4. Re-start the VMWare DHCP and NAT services for changes to take effect (From services.msc)
Notes:
the below folders are at sync automatically.. change at one place and the same will be reflected on the other folder
C:\ProgramData\VMware
C:\Documents and Settings\All Users\Application Data\VMware
A simple workaround, configure the vmware dhcp server to use longer leases.
In the vmware config folder (on windows 7 -- C:\ProgramData\vmware) edit the file
vmnetdhcp.conf and change the values of default-lease-time and max-lease-time to
something bigger say 4 months (4mo*30days*24hours*60min*60sec = 10368000).
Then restart the vmware dhcp server. Then release and renew the lease on the guest.
Now your guest IP is static for next four months.
If you prefer to leave the VM host configuration as default, it is also possible to configure the guest machine to request a fixed address for dhcp. This will work even for the NAT network. In the case of Ubuntu and dhclient, this is achieved by the following block in dhclient.conf:
interface "eth0" {
send dhcp-requested-address 192.168.1.222;
}
Source: https://serverfault.com/a/381137