VLAN Configuration with Avaya Switch
I am new to VLAN's so hopefully this will be easy.
I am trying to configure a nic in the server to connect to 2 networks, one of which is on vlan2. The card is onboard and lspci -v is below. The switch is an AVAYA P333T-PWR and is using the native lan for data traffic and vlan 2 for sip traffic. I have set the ifcfg-vlan2 file as below and ifconfig show both addresses for the native lan (eth0) and vlan2. The native lan is pingable (is that a word?) when I set the tagging mode to Clear on the AVAYA switch, but VLAN2 is not. When I set the tagging mode to IEEE-802.1Q, VLAN2 is pingable but the native lan is not. I assume that the switch is forcing something on the native lan packets that should not be there. We have Grandstream sip phones, which allow us to plug our computers into the phone for network connection. Both native and vlan2 travel the same wire to the switch. The phones and computers work correctly. The AVAYA switch has tagging mode set to clear for the phone ports. I also tried compiling a new driver direct from realtek, but that made no difference. What am I missing here? Thanks in advance. ------------lspci -v------------------- 02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 02) Subsystem: Giga-byte Technology GA-EP45-DS5 Motherboard Flags: bus master, fast devsel, latency 0, IRQ 58 I/O ports at c000 [size=256] Memory at e3410000 (64-bit, prefetchable) [size=4K] Memory at e3400000 (64-bit, prefetchable) [size=64K] [virtual] Expansion ROM at e3420000 [disabled] [size=64K] Capabilities: [40] Power Management version 3 Capabilities: [50] Message Signalled Interrupts: 64bit+ Queue=0/1 Enable+ Capabilities: [70] Express Endpoint IRQ 1 Capabilities: [b0] MSI-X: Enable- Mask- TabSize=2 Capabilities: [d0] Vital Product Data Capabilities: [100] Advanced Error Reporting Capabilities: [140] Virtual Channel Capabilities: [160] Device Serial Number 78-56-34-12-78-56-34-12 ----------ifconfig(removed lo, eth1, eth2)----------- eth0 Link encap:Ethernet HWaddr 00:1F:D0:27:D0:09 inet addr:192.168.12.8 Bcast:192.168.12.255 Mask:255.255.255.0 inet6 addr: fe80::21f:d0ff:fe27:d009/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:5813 errors:0 dropped:181773725332 overruns:0 frame:0 TX packets:2048 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:571718 (558.3 KiB) TX bytes:365353 (356.7 KiB) Interrupt:58 Base address:0xa000 vlan2 Link encap:Ethernet HWaddr 00:1F:D0:27:D0:09 inet addr:192.168.100.8 Bcast:192.168.100.255 Mask:255.255.255.0 inet6 addr: fe80::21f:d0ff:fe27:d009/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:22 errors:0 dropped:0 overruns:0 frame:0 TX packets:36 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:1120 (1.0 KiB) TX bytes:1728 (1.6 KiB) -----------ifcfg-eth0----------- NAME="" BOOTPROTO=none HWADDR=00:1F:D0:27:D0:09 DEVICE=eth0 MTU="" NETMASK=255.255.255.0 BROADCAST=192.168.12.255 IPADDR=192.168.12.8 NETWORK=192.168.12.0 ONBOOT=yes ----------ifcfg-vlan2---------- VLAN=yes VLAN_NAME_TYPE=VLAN_PLUS_VID_NO_PAD DEVICE=vlan2 PHYSDEV=eth0 BOOTPROTO=static ONBOOT=yes TYPE=Ethernet IPADDR=192.168.100.8 NETMASK=255.255.255.0 ----------Server---------- Intel Quad Q6600 2.4G x64/8G Ram Linux Raid w/ 2 sata HD's CentOS 5.3-2.6.18-128.1.16.el5 |
What does your routing table look like. Perhaps you could post the output from:
netstat -nr Regards, Fordeck |
All times are GMT -5. The time now is 08:14 AM. |