GNS3 on windows 7 vms - networking VMware ESXi 5.1

Installed windows 7 as vms on VMware ESXi 5.1 then installed gns3 onto that.
Now trying to figure out how to get the networking to work. This is based on an install I have running on a standalone win7 box where gns3 works fine but then it's a single NIC on physical hardware.

Wondering if someone could walk me through this and help get gns3 working.

Thanks.
projectsAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Your VM just has a single nic, on virtual hardware, treat it exactly the same, and forget it's hosted on ESXi 5.1.
0
projectsAuthor Commented:
Thing is, I'm not sure what is needed. I didn't set up gns3 on the physical server. I converted the physical server to the VM which is why I'm stumped now.
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Does it not work ?

what is the issue ?

As you have converted it to a VM, via P2V, all the networking would have been replaced, with virtual hardware.

I would also recommend you install VMware Tools, and add new VMXNET3 interfaces.

So you will want to setup/reconfigure networking, to select you existing nics.

How many network interfaces did you physical have ?

add the same.
0
Prepare for an Exciting Career in Cybersecurity

Help prevent cyber-threats and provide solutions to safeguard our global digital economy. Earn your MS in Cybersecurity. WGU’s MSCSIA degree program curriculum features two internationally recognized certifications from the EC-Council at no additional time or cost.

projectsAuthor Commented:
The issue is;
At first, gns didn't want to start, complaining about missing directories then that just went away on it's own.
Now gns3 seems to start but the previous 10.0.100.1 target I was pinging is no longer pingable.
I figured this was because of the virtual NIC or something missing.

On physical machine, there is one NIC and one loopback interface.
Once converted, the NIC was renamed from Local Area Connection to Local Area Network and seemed to have more than one NIC. I deleted the multiple NICs leaving only the one and renamed it.

When you say setup/reconfigure networking, do you mean on the VMs networking or on gns3 on the VM?
Should I replace the current NIC with a VMXNET3 NIC?
0
projectsAuthor Commented:
The error just showed up again;

GNS3 management console. Running GNS3 version 1.2.3 on Windows (64-bit).
Copyright (c) 2006-2014 GNS3 Technologies.

=> Server error [-3200] : Dynamips executable C:\Program Files\GNS3\dynamips doesn't exist
Server error [-3200] : Dynamips executable C:\Program Files\GNS3\dynamips doesn't exist
Server error [-3200] : Dynamips executable C:\Program Files\GNS3\dynamips doesn't exist
Server error [-3200] : Dynamips executable C:\Program Files\GNS3\dynamips doesn't exist
Server error [-3200] : Dynamips executable C:\Program Files\GNS3\dynamips doesn't exist

The directory does exist and gns3 seems to be see it randomly. One time it might not, the next it might.
0
projectsAuthor Commented:
I removed the old NIC and installed the one you suggested.
Now the NIC is named Local Area Connection 2 which means I probably have to change something in ngs3?
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
if the directory does not exist, something went wrong with your conversion. (e.g. P2V).

1. Install VMware Tools.

Part 8: HOW TO: Install VMware Tools for Windows on a VMware Windows virtual machine on a VMware vSphere Hypervisor 5.1 (ESXi 5.1) Host Server

2. Remove the current NIC form the Virtual Machine.

3. Remove ALL Hidden Network Interfaces, and Ghost Interfaces.

4. Setup TCP/IP information as per physical machine.

To be honest, you would probably better, creating a new Windows 7 VM from scratch and install GNS3.
0
projectsAuthor Commented:
No, the directory does exist as I mentioned :)
VMware Tools are installed.
Hidden and ghost interfaces were removed.
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
If the directory does not exist.

P2V did not complete correctly - re do it.
0
projectsAuthor Commented:
I renamed the network connection back to Local Area Network, then restarted gns3 and now the directory errors are gone.

Just how long does it take for gns3 to start a configuration? Seems to take a few minutes to get started.
Waiting for that to come alive so I can see if the IP can be pinged now.
0
projectsAuthor Commented:
All green but nothing happening. Do I need to run or reset something?
Is there an alias needed on the interface maybe?
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Re-install GN3, or create a new VM, and re-install GNS3.

Is your VM, exactly the same configuration as the physical machine ?
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
projectsAuthor Commented:
I'm trying to avoid having to rebuild since the physical machine had a bunch of things installed and I'd have to reconfigure it all.
as far as I can see, the conversion went well and everything appears to be intact and there. I can't swear it's 100% identical because drivers change, etc when you fire up the conversion.

Here is something interesting.

The physical machine had a 192.168.2.106 IP.
On any test device I wanted to test I would add;
 route add -net 10.0.100.1 netmask 255.255.255.255 gw 192.168.2.150 dev eth0

Now, the machine is running on an ESXi server which has an IP of 10.0.1.x and the new VM still has the 192.168.2.106 IP.

Should I be changing the route I'm adding into my test device, something along those lines?
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
The difference here is the networking stack of the VM, has been ripped out and replaced.

The HOST IP address is irrelevant, and does not affect the VM.

The question is does the ESXi host have the same physical network connection as the physical server, you P2Ved.

The virtual machine configuration should be exactly the same as the physical machine.
0
projectsAuthor Commented:
Ok, now we're getting somewhere :)

>The question is does the ESXi host have the same physical network connection as the
>physical server, you P2Ved.

This is what I've been thinking all along but looking at the gns3 configurations, I'm not seeing anything I can change.
The network that the P server was on was also a 192.168.x.x network but now the VM resides on a server which has a 10.0.1.x address for management BUT has a direct connection to the same 192.168.x.x network.
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
That's just an IP Address which is assign to the Host, it has nothing to do with the VM.

The VM has a unique IP Address and MAC Address, which is connected to vSwitch, which is connected to a physical uplink.

Network Traffic 10.0.1.x and traffic from the VM will leave the same physical NIC!

Now are you sure, that the physical port the ESXi server management port is connected to, is also on the 192.168.x.x network?

So do you run both 10.0.1.x network traffic over the same physical network as 192.168.x.x ?

or do you have to make another physical network connection from the ESXi server to a physical switch somewhere...or port.
0
projectsAuthor Commented:
>Now are you sure, that the physical port the ESXi server management port is connected to,
>is also on the 192.168.x.x network?

On this blade yes. The blade has both it's NICS bonded and connected to one switch which handles both 192.168.x.x and 10.x.x.x along with 172. 30.x.x. in fact.

>So do you run both 10.0.1.x network traffic over the same physical network as 192.168.x.x ?

In this case yes.

>or do you have to make another physical network connection from the ESXi server to a physical switch >somewhere...or port.

Most of the blades are connected to multiple switches, one for management, one for traffic. In this case, the blade is to the one switch.
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
In that case, from what you have told me the ESXi host server and physical computer should both see the same networks.
0
projectsAuthor Commented:
This is a multi segment LAN setup where you'll have different LAN's all separated from each other through  firewall. The only two LAN segments that have the same non firewalled paths are 192.168.x.x and 10.x,x,x.

I'm looking closer now and on this blade, only NIC0 is being used, the other is in stand by.
On that NIC, both the VM Network and the Management Network exist.

In the vSwitch0 Properties, I see 192.168.1.201-192.168.1.201 for both active and standby adapters. That is odd since there is a workstation which also uses that IP.
For management, I have 10.0.1.201 in the Management Network Properties IP Settings and in the NIC Teaming section, it shows Active Adapters as vmnic0/1 having 192.168.1.201-192.168.1.201.
Same IPs in the VM Network Properties.

The above seems to be confusing to me. All of the VMs on this blade use 192.168.1.x and all work fine, yet, the above states 192.168.1.201 which is a workstation IP? That workstation works fine too, never had a problem with it and it having access or IP conflicts.
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Is this Observed IP Address Network Range ?

Only the Management VMKernel Portgroup has a MAC Address, which can be assigned an IP Address, which I believe you have shared is 10.0.1.201.

The information you have listed, is the Observed Network Range, which the network interfaces tries to display!

This is NOT an IP Address associated with the nic.

Please screenshot.
0
projectsAuthor Commented:
Which part do you want to see?
2015-04-15-091314.png
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
where are you getting

192.168.1.201-192.168.1.201  from ? networks adaptors ?
0
projectsAuthor Commented:
When looking at the various network configuration settings.
2015-04-15-100426.png
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Yes, that's the observed network range, that the network interfaces in the servers have detected or sniffed on it's adaptors....

and that depends on how much traffic is hitting the nics, sometimes it's blank or not accurate.

that's not an IP Assignment to a NIC anywhere! just what has been "seen" on the nic interface.

have you tested this VM can reach ALL the network devices on the 192.168.x.x network ?
0
projectsAuthor Commented:
Yes, tested that also, and I can ping 10.0.x.x and 192.168.x.x IPs
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
from the VM.

So GNS3 is broke, probably because of the network rip out and replace change.
0
projectsAuthor Commented:
It was broken before I did that remember :).
I only did that because you suggested using a different NIC type.

I could always try converting the machine again, which would take about 2hrs but then what? When I create the VM, I would make sure to use the NIC you suggested. Would that make any difference?
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
The Conversion of a P2V rips and replaces the NICS!

e.g. your physical server may have an Broadcom Network Interface, that is not available in the VM, and a new nic is added.

this is in a different slow, different make and mode, different mac address... etc

not the same,

Everything is changed, the data remains, but the CPU, BIOS, Memory, Hard Disk, NICS - all change!

if you have hardware dependencies on any of the above they will break!

I could always try converting the machine again, which would take about 2hrs but then what? When I create the VM, I would make sure to use the NIC you suggested. Would that make any difference?

No.
0
projectsAuthor Commented:
If I have hardware dependencies in terms of what, gns3? The only one I can recall was the video card. The person who installed gns3 said that he needed a well supported video driver for something or other. Nothing else seemed to be hardware dependent.
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
What I'm trying to get you to understand, is

1. Does GNS3 work in a virtual machine ?

2. Does GNS3 work with a virtual network interface ?

3. Will it continue to work, when a nic or nics are changed ?
0
projectsAuthor Commented:
I don't know those things... that's why I posted the question.
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
If it worked before, on the physical server, and it's been converted, it's broke.

I would quickly install a copy on a virtual machine, and test, and  check it works.
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
I've had a lightbulb moment....

this software may require hardware or low level access to the network interface, which is called...

Promiscuous mode.... which it can normally do when the hardware is physical, but maybe cannot do this when virtual...

BUT, you can enable this mode on the vSwitch.

Select the properties of the vSwitch, and you will see an option for it.
0
projectsAuthor Commented:
The machine looks intact as a vm.
The networking seems to work.
GNS3 seems to start up but the simulated network can't be reached.

I could build a new vm instead of converting but that would mean a lot of work re-installing lots of other things.
I could try and understand what gns3 is missing instead since everything else seems to be working.

I've looked at gns3, don't know it well enough to know what I'm looking for but it seems it might simply be a configuration issue.
0
projectsAuthor Commented:
Ok, I did that and tried the client again but still no dice. Nothing pings back.
Am I supposed to restart the interface or something along those lines?
0
projectsAuthor Commented:
There is one interesting item in the Settings of that VM for the Network adapter, it says;

DirectPath I/O disabled
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Ok, I did that and tried the client again but still no dice. Nothing pings back.
Am I supposed to restart the interface or something along those lines?

just enable will do it.

DirectPath I/O disabled
- default and normal.
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
did you install the loopback interface ?
0
projectsAuthor Commented:
On the VM? It was converted and seems to be there.
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
what simulation are you running ?
0
projectsAuthor Commented:
A multi-router multi-path/fail-over path similar to intranet/internet traffic with a target at the end.
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
It would be interesting if you installed it on a VM, as per opening question, if it works.

(and configuration the same as your physical server - for tests).

I suspect the virtual networking stack may not be compatible, if it uses low layer networking functions.

Although wireshark works in a VM, in prom. mode.
0
projectsAuthor Commented:
That's an interesting thought. I'll install wireshark and see what I get.

As for installing gns3 on a VM, I can do that, it's just that I'm not sure what settings I would have to go over to make sure the two instances are the same.
0
projectsAuthor Commented:
Oh, look what I found on the VM

The 10.0.100.1 is that target I'm trying to ping from a workstation to the gns3 setup. The firewall on the VM is disabled, I'm not sure what would be preventing it from echoing back.
2015-04-15-161714.png
0
projectsAuthor Commented:
Never mind, that's just the remote trying to get a ping response.
0
projectsAuthor Commented:
I enabled debug on the first router and the moment I ping from the remote, I see this, once.

ICMP packet debugging is on
ESW1#
*Mar  1 00:08:12.175: ICMP: echo reply rcvd, src 10.10.22.2, dst 10.10.22.1

Those interfaces however are past the first router, into the next routers.
2015-04-15-164455.png
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
VMware

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.