Simple networking question for 3.0.2

[strebormj]

We have a ProLiant running ESX 3.0.2. (Haven't upgraded to 3.5 yet -- weren't sure if we would lose config or VMs.) For the last year or so, it was configured to use DHCP, due to some oversight, and it was humming along on 192.168.xx.xxx. For some reason, the iron went down Friday, and when I brought it back up yesterday, it came up with the IP 0.0.0.0 displayed on the console. Interpreting this as an IP conflict, and finding this an opportune time to configure it to use a static IP not in our DHCP pool, I set it to .87 using

esxcfg-vswif -d vswif0

esxcfg-vswif -a vswif0 -p Service\ Console -i 192.168.xx.87 -n 255.255.255.0 // wasn't sure what to use for the broadcast param. It defaulted to 192.168.xx.255

1. I edited /etc/sysconfig/network and /etc/hosts to contain the proper variable values.

2. I also edited /etc/sysconfig/network-scripts/ifcfg-vswif0 to contain the proper values. My network guy didn't know what NETWORK should be set to, and advised me to set it to 192.168.xx.0. I noticed that PORTGROUP said portgroup0 instead of "Service Console" so I set it to "Service Console" after reading http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=100379....

3. I set the values in /etc/resolv.conf

4. I ran route -n and noticed the the routing table was not based on what I had entered. (It said "default 0.0.0.0 local subnet".) I tried using esxcfg-route to add the default gateway, but got an error saying "Cannot set gateway until kernel TCP stack has at least 1 ip address"

5. I did a service network restart and repeated the steps over, to no avail.

Looks like I'm missing missing a step (or two). Any idea what NETWORK and BROADCAST should be set to, and what I am missing?

Thanks!

[martipc]

Hello

what is the value for the bootpro parameter in the /etc/sysconfig/network-scripts/ifcfg-vswif0 file?

The broadcast that you have to set up is:192.168.xx.255, the network paramaeter is: 192.168.xx.0

[strebormj]

Thanks for replying.

BOOTPROTO=static

Based on what you said, it looks like I had the other two settings correct.

Any ideas?

[martipc]

can you attach the result from execute : esxcfg-vswif -l / route -n / cat /etc/sysconfig/network / ifconfig

[strebormj]

esxifg-vswif -l:

"ERROR: unable to retrieve information about vswif0"

route -n:

Dest, GW, Genmask

192.168.xx.0, 0.0.0.0, 255.255.255.0

169.254.0.0, 0.0.0.0, 255.255.0.0

0.0.0.0, 192.168.50.1, 0.0.0.0

---

cat /etc/sysconfig/network:

NETWORKING=yes, GATEWAYDEV=vswif0, GATEWAY=192.168.xx.1, HOSTNAME=<boxname.company.com>

---

cat /etc/sysconfig/network-scripts/ifcfg-vswif0:

DEVICE=vswif0, MACADDR=<mac>, PORTGROUP="Service Console", BOOTPROTO=static, BROADCAST=192.168.xx.255, IPADDR=192.168.xx.87, NETMASK=255.255.255.0, NETWORK=192.168.xx.0, ONBOOT=yes

[Rob_Bohmann1]

From you post:

NETWORKING=yes, GATEWAYDEV=vswif0, GATEWAY=122.168.xx.1, HOSTNAME=<boxname.company.com>

I think that 122 may be a problem...

[strebormj]

That was a typo, actually. It's 192.168.xx1. Since the box isn't on the network, I actually had to write everything down and then type it in to this forum. I'll fix my previous post.

[strebormj]

Apparently, this wasn't as simple as I'd hoped.

I have to imagine that a lot of folks are running ESX servers with statically-assigned IP addresses, and also that I'm missing something subtle....

[Karunakar]

Hi,

i think the misake done is in the file /etc/sysconfig/network-scripts/ifcfg-vswif0

here you changed the portgroup from portgroup0 to Service Console.

This is a mistake, as Service console is the Portgroup name, and portgroup0 was int eh internal ID of that portgroup Service console.

Please change it back to portgroup0, and then try to restart network service.

Let me know if this works.

-Karunakar

[strebormj]

Thanks for responding. I did as you suggested, but I still cannot connect to the network. Any other ideas?

[strebormj]

It looks like the NIC was flaky, and was having intermittent connectivity issues.

Case closed.