VLAN Configuration with Avaya Switch

[scottgutman]

This is a little off topic as it is more about linux config and not about vicidial. I am new to VLAN's so hopefully this will be easy.

I am trying to configure a nic in the dialer 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 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?

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

[williamconley]

I know what you're missing: A 2nd NIC Card or A+/Net+ certification (or you got it and NOW you're getting old).

1) Why VLAN instead of just a new subnet (OK, Now *I* am missing my Net+ certification, sorry)

2) I have an A+ on staff ... I'm sure she'd be happy to "Pontificate", but I do NOT pay her to "EFLO.net forum surf" (she's way too expensive for that and cares not one whit about Vicidial)

3) I know you don't WANT to run extra cat5e to each workstation so the 'puters and phones can actually BE on sep wiring runs and even a sep switch ... but it is a good idea. Thought I'd mention it, though. You KNOW you would not be experiencing this issue if you did that and used 2 nics.

OK, all that being said: You have only one set of wires, you have a wish for the phones and the computers which are on the same physical wires to have different (read: no-noise sharing) LANs so that they both hit the SAME server without interfering with one another because they can't even see each other, right?

Do these computers need to see outside the building? (OK, off the LAN through a gateway?)

OK, also you said one is "pingable" [sic] with tagging mode 802, the other with clear. I presume that you mean other computers on the subnet can see (ping) one or the other, but never both.

Can IT see "out" in both circumstances? Can IT see (ping) the phones and the computers at all times?

Beyond this, I would have to pass to Net+ ... (and you should be on one of THOSE sites, as I'm sure they would not be guessing, like I am).

[tweidner6471]

I'm not sure about Avaya switches, but normally if you plan on carrying more than one vlan on a single port you need to configure it to be a trunk port instead of an access port (which is normally the default in most networking equipment).

Generally speaking if you have more than one device connected to a single switch port (even if it's only a virtual device, as in your case), you should have it configured for trunking. There should be an option in the switch somewhere for that.

You'd probably be better off, however, installing a second NIC into the linux machine, in that way you're not compromising on any front. By creating a secondary interface on that single NIC you're limiting the throughput since they're sharing the same actual hardware.

EDIT: A quick note, switches normally can't do routing, so if you're trying to get traffic to cross multiple networks you'll need some kind of routing device.