tagging vlans on a nic, DL380 procurve 2824,

[Chris Bullock_1]

Hardware: Dl380 G2
Switch: procurve 2824
OS RedHat clone (CentOS 4.4)
I am starting to play with vmware and I need to tag the port that my vmware box is connected to on the lan so that the vmware physical nterface is a member of all associated vlans, but I have not gotten it to successfully work, so I want to narrow my search to 1 the switch, 2 the
os, 3 the nic of the server.
I followed this kb article on red hats web site:
http://kbase.redhat.com/faq/FAQ_45_3681.shtm

When I tag the port on the switch, I lose all my networking to that host, even after restarting the network. Here is my eth0 config:
[cgb@apollo ~]$ sudo cat /etc/sysconfig/network-scripts/ifcfg-eth0*
DEVICE=eth0
ONBOOT=yes

DEVICE=eth0.4
BOOTPROTO=static
HWADDR=00:08:02:DF:89:4A
IPADDR=172.24.4.243
NETMASK=255.255.252.0
NETWORK=172.24.4.0
GATEWAY=172.24.4.1
ONBOOT=yes
TYPE=Ethernet
VLAN=yes

Here is the outcome of ifconfig:
[cgb@apollo ~]$ /sbin/ifconfig
eth0 Link encap:Ethernet HWaddr 00:08:02:DF:89:4A
inet addr:172.24.4.241 Bcast:172.24.7.255 Mask:255.255.252.0
inet6 addr: fe80::208:2ff:fedf:894a/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:7163372 errors:0 dropped:0 overruns:0 frame:0
TX packets:8645697 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:819521529 (781.5 MiB) TX bytes:3667339610 (3.4 GiB)

eth0.4 Link encap:Ethernet HWaddr 00:08:02:DF:89:4A
inet addr:172.24.4.243 Bcast:172.24.7.255 Mask:255.255.252.0
inet6 addr: fe80::208:2ff:fedf:894a/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:11 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:674 (674.0 b)


My question here is where in the world is it pulling the IP address for
eth0?

Here is some of the dmesg with eth0 in it:
bridge-eth0: enabling the bridge
bridge-eth0: enabled promiscuous mode
bridge-eth0: up
e100: eth0: e100_watchdog: link up, 100Mbps, full-duplex
divert: allocating divert_blk for eth0.4
eth0.4: add 33:33:00:00:00:01 mcast address to master interface
eth0.4: add 33:33:ff:df:89:4a mcast address to master interface
eth0.4: add 01:00:5e:00:00:01 mcast address to master interface
eth0: no IPv6 routers present
eth0.4: no IPv6 routers present
[cgb@apollo ~]$
Any help would be appreciated.
Chris

[Steven E. Protter]

Shalom Chris,

Its getting the IP address from eth0 because thats the real IP address.

Most network hardware can figure out the MAC address is the same anyway and if you look at netstat -in you'll see even if the actual traffic is on eth0:4 the system is runing it through the master not the virtual interface.

I'm not sure you can achieve this objective.

Most of my personal systems are CentOS, I've got some experience with it.

SEP