Unsolved

This post is more than 5 years old

1 Rookie

 • 

17 Posts

1740

November 5th, 2007 08:00

eth2 not starting with default Virtual Network Settings in VMWare

eth2 does not come up during Simulator boot. by default eth2 is mapped to VMnet2 that is not bridged and not connected to any virtual adapter. Even if changed and mapped to an existing adapter eth2 does not come up unless remapped to a NAT or host only adapter. But it also does not come up with an IP address. Keeps coming up "Broadcast Multicast"

19 Posts

November 5th, 2007 18:00

Hi jwl,

which version of the simulator are you using?

-KC

4 Posts

February 1st, 2008 14:00

I have the same problem... Boot process says it brought eth2 online, but ifconfig does not show a inet address.... I tried to ping my router and it failed and reported my ip as 192.168.1.100.

I tried adding a "default route" to my router and the pings started working... Celerra Manager is still not reachable though.

I am running:
Host - Vista 32bit
Mem - 4gb
Storage - 400gb+
Guest - Simulator 5.5.29.1

4 Posts

February 1st, 2008 14:00

Ohhh....

Using VMware Workstation 6.0.2 build-59824.

I have a XP-sp2 and an OS-X running off this workstation so it seems to be using the Host hardware without any issues...

3 Posts

February 6th, 2008 10:00

I had a similar problem and found that the ifcfg script in /etc/sysconfig/network-scripts was incomplete. When I looked at it there were 2 lines missing:

DEV=eth2
ONBOOT=yes

I added them, restarted the network service and eth2 came up as expected.

90 Posts

February 20th, 2008 14:00

Hello All,

eth2 is the host only interface and so is designed to talk directly between the host OS and the Simulator (however, I think it can be configured like any other interface, but this is not a supported configuration). Normally, this interface is configured with dhcp. Vmware Workstation or Player has a dhcp server that will assign an IP address when it is configured.

Configure it with the netconfig command, setting it for dhcp. After that is done, run the command, 'ifup eth2' to bring it up. The Vmware dhcp server should assign it a private 192.168.x.x address. This interface will then be available on boot up (check and make sure the address didn't change.

I hope this helps,

Jim

90 Posts

April 16th, 2008 07:00

Hi Osama,

Chances are that you'll just have to wait a few minutes before you try the Celerra Manager. Give it a few more minutes and if it doesn't clear up, let me know.

Jim

46 Posts

April 16th, 2008 07:00

hi jimg,

i have tried your solution it worked for me and it gives me the ip address for thre eth2. but the problem was that after the login page of the celerra manager, it gives me "Internal Server Error
The server encountered an internal error or
misconfiguration and was unable to complete your
request."

i have tried to refresh but same thing.

please advice

best regards

osama

1 Rookie

 • 

71 Posts

April 16th, 2008 22:00

Hi,

I had the same trouble, however,
on my case, I was able to connect Celerra Manager after around 10 minutes.

Yasushi

Top