Hmm, I commented out the public address from /etc/hosts. Maybe the parsing is still finding it though? I'll remove it entirely and try again tonight. Thanks!
On Mon, Feb 15, 2010 at 9:33 AM, Andy Kurth <andy_ku...@ncsu.edu> wrote: > Hi Jeff, > Remove the public address for the computer from /etc/hosts. The code finds > the first line in /etc/hosts containing "vcl-winxp" and uses this for the > private interface. Add the private address to /etc/hosts if you haven't > already done so. The code is collecting the private address from /etc/hosts > then parses the ipconfig output to find the public IP address. It assumes > the adapter not using the private address is public. > > Hope this helps, > Andy > > > > > Jeffrey Wisman wrote: > >> Thanks James. I added the VMs to my /etc/hosts file and my dhcpd.conf >> file, >> and the same thing is happening. I think the dhcp was working fine >> before, >> but VCL seems to be getting confused between what the public IP address is >> and what the private one is. Here is a snippet from the logs: >> >> 2010-02-13 23:10:02|21557|2:2|new|utils.pm: >> get_management_node_id(9346)|environment >> variable: 1 >> 2010-02-13 23:10:02|21557|2:2|new|new.pm: >> reserve_computer(1017)|user_standalone=1, >> image OS type=windows >> 2010-02-13 23:10:02|21557|2:2|new|utils.pm: >> getdynamicaddress(1596)|PrivateIP >> address for vcl-winxp collected 134.154.119.175 >> 2010-02-13 23:10:02|21557|2:2|new|utils.pm: >> run_ssh_command(6168)|executing >> SSH command on vcl-winxp: >> |21557|2:2|new| /usr/bin/ssh -i /etc/vcl/vcl.key -l root -p 22 -x >> vcl-winxp >> 'ipconfig' 2>&1 >> 2010-02-13 23:10:05|7225|vcld:main(165)|lastcheckin time updated for >> management node 1: 2010-02-13 23:10:05 >> 2010-02-13 23:10:08|21557|2:2|new|utils.pm: >> run_ssh_command(6250)|run_ssh_command >> output: >> |21557|2:2|new| Windows IP Configuration >> |21557|2:2|new| Ethernet adapter Local Area Connection: >> |21557|2:2|new| Connection-specific DNS Suffix . : csueastbay.edu >> |21557|2:2|new| IP Address. . . . . . . . . . . . : 10.75.144.124 >> |21557|2:2|new| Subnet Mask . . . . . . . . . . . : 255.255.255.128 >> |21557|2:2|new| Default Gateway . . . . . . . . . : >> |21557|2:2|new| Ethernet adapter Local Area Connection 2: >> |21557|2:2|new| Connection-specific DNS Suffix . : csueastbay.edu >> |21557|2:2|new| IP Address. . . . . . . . . . . . : 134.154.119.175 >> |21557|2:2|new| Subnet Mask . . . . . . . . . . . : 255.255.255.128 >> |21557|2:2|new| Default Gateway . . . . . . . . . : 134.154.119.254 >> 2010-02-13 23:10:08|21557|2:2|new|utils.pm:run_ssh_command(6264)|SSH >> command >> executed on vcl-winxp, returning (0, "Windows IP Configuration Ether...") >> 2010-02-13 23:10:08|21557|2:2|new|utils.pm: >> getdynamicaddress(1643)|dynamic >> IP address for vcl-winxp collected: 10.75.144.124 >> 2010-02-13 23:10:08|21557|2:2|new|new.pm:reserve_computer(1033)|retrieved >> dynamic DHCP IP address from 10.75.144.124: 10.75.144.124 >> 2010-02-13 23:10:08|21557|2:2|new|DataStructure.pm:_automethod(697)|data >> structure updated: computer_ip_address = 10.75.144.124 >> 2010-02-13 23:10:08|21557|2:2|new|utils.pm: >> update_computer_address(7049)|computer >> 13 IP address 10.75.144.124 updated in database >> 2010-02-13 23:10:08|21557|2:2|new|new.pm:reserve_computer(1039)|updated >> IP >> address in computer table >> >> >> As you can see, its taking the public IP (134.154.119.175) and making it >> the >> private one, and vice versa. End result is that it asks me to RDP to the >> private address, which of course is impossible. >> >> If I RDP to the 134.154.119.175, I can login just fine. I just need VCL >> to >> present that IP address to me instead of the private one. >> >> Any ideas on this? >> >> Thanks, >> Jeff >> >> >> >> On Sun, Feb 7, 2010 at 9:35 PM, James Patrick Sigmon <jpsig...@ncsu.edu >> >wrote: >> >> Hey Jeff, >>> >>> It looks like you have not filled in your mac address information for >>> your >>> virtual machine. Vmware likes a particular format for this. Try >>> 00:50:56:2A:3B:00 for eth0macaddress and 00:50:56:2A:3B:01 for >>> eth1macaddress. >>> >>> The field "IPaddress" corresponds to the "public" address. Though, I >>> don't >>> think this will matter here. A public IP address typically will be >>> generate >>> for your machine. Try a reservation with the mac addresses and see if >>> that >>> fixes this. >>> >>> You may have already done these steps but I thought I would add them to >>> be >>> safe: >>> >>> You should have an entry for your virtual machine in your /etc/hosts >>> file. >>> (ex. 10.75.144.15 csuvm15). >>> >>> You should also have an entry in your dhcpd.conf file as well for each >>> virtual machine. >>> >>> Hope this helps, >>> >>> Patrick >>> >>> >>> On Feb 8, 2010, at 12:14 AM, Jeffrey Wisman wrote: >>> >>> We're now at the point where we can create reservations and virtual >>>> >>> machines >>> >>>> get loaded with images. The issue we're having is that the virtual >>>> >>> machines >>> >>>> come up on their private IP addresses only. The reservation screen >>>> shows >>>> the private IP and the RDP file has that IP in it. We have the virtual >>>> machines configured with two interfaces - one on the private network for >>>> >>> VCL >>> >>>> admin stuff, and the other on the public network where we have the >>>> campus >>>> DHCP server configured to give it an IP. However, it doesn't seem to be >>>> working, or at least if it is getting a public IP, VCL isn't telling us >>>> >>> what >>> >>>> it is. >>>> >>>> I'm wondering if the issue is in the database. Each virtual machine has >>>> >>> an >>> >>>> "IPaddress" and a "privateIPaddress". On our virtual machines, they are >>>> >>> set >>> >>>> to the same thing. Here is an example: >>>> >>>> mysql> select * from computer; >>>> >>>> +----+---------+---------+------------+------------+----------------+------------------+-------------+-----------------+-------+------------+-----------+---------+-----------------------+-----------------+------------------+----------------+----------------+----------------+----------------+-----------+---------+-------+-----------+----------+------+--------+------+--------+------+---------+----------+----------+ >>> >>>> | id | stateid | ownerid | platformid | scheduleid | currentimageid | >>>> preferredimageid | nextimageid | imagerevisionid | RAM | procnumber | >>>> procspeed | network | hostname | IPaddress | >>>> privateIPaddress | eth0macaddress | eth1macaddress | type | >>>> provisioningid | drivetype | deleted | notes | lastcheck | location | >>>> dsa >>>> >>> | >>> >>>> dsapub | rsa | rsapub | host | hostpub | vmhostid | vmtypeid | >>>> >>>> +----+---------+---------+------------+------------+----------------+------------------+-------------+-----------------+-------+------------+-----------+---------+-----------------------+-----------------+------------------+----------------+----------------+----------------+----------------+-----------+---------+-------+-----------+----------+------+--------+------+--------+------+---------+----------+----------+ >>> >>>> <snip> >>>> | 24 | 2 | 1 | 1 | 1 | 4 >>>> | 0 | 0 | 0 | 512 | 1 >>>> | 2000 | 1000 | csuvm15 | 10.75.144.15 | >>>> 10.75.144.15 | NULL | NULL | virtualmachine >>>> | 4 | hda | 0 | NULL | NULL | NULL | >>>> >>> NULL >>> >>>> | NULL | NULL | NULL | NULL | NULL | 1 | NULL | >>>> >>>> >>>> Should one be NULLed out or set to something else? Should we put all >>>> the >>>> private entries in the /etc/hosts file of the VMWare management server? >>>> Currently I haven't done that, but read it in one of the posts here. >>>> Any >>>> other ideas? >>>> >>>> Thanks, >>>> Jeff >>>> >>> >>> >> > -- > Andy Kurth > Virtual Computing Lab > Office of Information Technology > North Carolina State University > andy_ku...@ncsu.edu > 919.513.4090 >
