did you get your reply? i have same question too.

I would suggest you confirm that you are using the same SFP or GBIC on each side…replace the fiber patch, replace the optic.

Good Luck

I have being working on our new VoIP Vlan and tried to configured the switch port with untagPVIDonly with Data VLAN as PVID vlan and it did not work, then when I changed the tagPvidonly with Data VLan as PVID VLan it worked with this setup it means that data Vlan is being tag and Voice VLAN dont, so according to your article it should not work as laptop and desktop will discard andy packet which has been tag by 801.2Q tagging as they dont understand the packet.

Please explain.

Thanks

Hi Hari,

The Arista is not tagged the frames in VLAN 1, hence they are untagged, hence they are being discarded.

This is similar to Cisco’s native VLAN command, frames in those VLANs are not tagged across a trunk interface.

Cheers!

First of all thanks for all the blogs you wrote on Avaya, saved me in lot of situations.

I got a question, in regards to traffic on VLAN1 between Nortel 5520 to Arista switch. The connections between them is a trunk connection.

For eg: i tagged 1,3,4,5….50 between them.

In Nortel port configs, i have got 2 things a) “DiscardUntaggFrames” checkbox is “ticked” b) DefaultVlanid:4 and got an IP on VLAN1 – 10.10.10.1/24

On Arista side, i have trunked the same vlans & configured an SVI for VLAN 1 – 10.10.10.2/24

But i couldn’t ping each other. Unless I “un-check” the “DiscardUntaggFrames” & change “DefaultVlanId:1”, then it pings.

Did some packet capture on Arista and Avaya side when defaultvlanid:4 . When a packet leaves Arista it’s tagged on VLANID:1 but when it’s hitting Avaya they are putting them into VLANID:4 , why is that? i thought VLAN 1 is tagged ??

Can you please advise ? It’s affecting our production traffic at this stage.

Thanks
Hari

I want to connect 2 avaya layer 3 switches using trunk.
a)Ist switch has vlan 5 for voice and val 10 for data
b)2nd switch has vlan 5 for voice and vlan 20 for data

I need to make communication between vlan 10 and vlan 20.Can you plz post the config?

Thanks for the quick reply!

The config includes “no auto-pvid”.

So with the following config on another 4548, port 12 is untagged but its a member of
vlan 6,160,161,162,163,170,172,173 & 180:

vlan ports 12-16 tagging unTagAll filter-untagged-frame disable filter-unregis
tered-frames enable priority 0
vlan members 1 NONE
vlan members 6 3,9,11-13,20,31,37,41-48
vlan members 160 1,4,10-13,19,32,38,41-48
vlan members 161 2,4,10-13,15,19,32,38,41-48
vlan members 162 4,9-13,19,32,38,41-48
vlan members 163 3-5,7-8,10-13,16-17,19-20,22,27-28,32,38,41-48
vlan members 170 1-5,7-13,15-23,27-48
vlan members 172 1,4,6,8,10-14,17-21,23-26,29,32,34-35,38-39,41-48
vlan members 173 2,5,11-13,18,23,25,30,33,36,40,43-48
vlan members 180 1-5,7-13,15-48
vlan ports 11-13 pvid 173

When traffic ingresses on port 12 untagged, which vlan is it sent over? When broadcast or unknown DA traffic comes into the switch, on other ports on these vlans, is it sent out port 12?

Am I right in assuming in the Nortel world untagged (access) ports should be a member of a single pvid vlan with “no auto-pvid” configured?

Thanks,
Bill

Hi Bill,

It’s a grey area. If you have autopvid set to strict the switch will error on that configuration. Not knowing anything else about your environment I would assume they are access ports.

Cheers!

Hi David,

If post to the discussion forums you’ll get a much quicker response.

http://networkinfrastructure.info

Cheers!

I’m in the process of swapping out some Nortel 4548 switches with Cisco Nexus devices and I’m trying to decipher the Nortel configs but I’m seeing what looks to be a conflict.

Below is a snapshot of the config. Ports 5-34 are untagged so my take is they are access ports but the vlan membership cmds allow multiple vlans on some of those ports. How can the config allow multiple vlans on an access port? For example; port 12 has vlan 172 as its PVID but it is also a member of vlans 170 and 163. Is this a mis-configuration?

—————————————————–
vlan ports 5-34 tagging unTagAll filter-untagged-frame disable filter-unregist ered-frames enable priority 0
vlan members 1 NONE
vlan members 163 1-11,13-14,36,42,46-48
vlan members 170 1-2,5-48
vlan members 172 3-4,12,15,36-37,39,42-43,46-48
vlan ports 3-11 pvid 163
vlan ports 12 pvid 172
vlan ports 13-14 pvid 163
vlan ports 15 pvid 172
vlan ports 16-34 pvid 5

Here is the VLAN information

vlan ports 1/1-24,2/20,2/22,2/46-47 tagging tagAll

vlan ports 2/48 tagging unTagPvidOnly

vlan configcontrol flexible

vlan members 1 1/1-32,2/11-43,2/45-50

vlan members 6 1/1-24

vlan members 150 1/1-24,2/1-10,2/20,2/22,2/48

vlan ports 1/3,1/12 pvid 6

vlan ports 2/1-10 pvid 150

no auto-pvid

The port on the Avaya connected to the working switch is 1/12. The non-working HP switch is connected to 1/8. This switch will mainly be VLAN 1 devices that need to communicate with all three VLANSDo you see what might be causing the issue? Thanks.

Hi wp4suso,

You can use whatever VLAN ID you’d like, the point is that they should match. I have seen issues with SONMP when the PVID is set to different VLANs between two switches. In my network it’s the same for every closet and it’s a known value everywhere (VLAN 200). Since it’s a fixed constant it’s much easier to configure and work with. If it was different at every site then I would need to look it up somewhere and it could be different at every site.

Cheers!

Can not be any better explanation but “It’s also a best practice to configure the PVID on all trunk (tagAll) ports with the VLAN ID of your management VLAN.” it’s no really secure, right ?

wp4suso

Hi Mike,

You’ve gotten Layer 1 to work, now you need to verify that your Layer 2 and Layer 3 configurations are correct.

You can read this post for an example of how to setup 801.1Q tagging between an Avaya and Cisco switch.

http://blog.michaelfmcnamara.com/2011/01/802-1q-vlan-tagging-on-a-cisco-catalyst-3750-e/

Good Luck!

Hi Khalil,

You’ve configured the WatchGuard Firebox with the same VLAN ID and appropriate IP addressing?

Good Luck!

I am connecting a WatchGuard Firebox device to our ERS 4526 on port 24 and I assume that the port should be a trunk port? Would it be possible for you to quickly review my ERS 4526 configuration for this connection and let me know if I am missing anything. The firebox has an IP address of 192.168.12.81:

enable
configure terminal

vlan configcontrol flexible

vlan port 24 tagging TagAll

vlan create 300 name “Name” type port
vlan members add 300 24
interface vlan 300
ip address 192.168.12.83 255.255.255.240 4
exit
ip routing

ip route 172.16.2.32 255.255.255.240 192.168.12.81 1
ip route 192.168.12.80 255.255.255.240 192.168.12.81 1
ip route 200.32.104.227 255.255.255.255 192.168.12.81 1
ip route 200.32.104.228 255.255.255.255 192.168.12.81 1

Autonegotiation requires 2-way communications. In this case the Cisco box is shouting out “I can do…” and the Nortel box is keeping silent. The 3550 should be able to determine what speed the link is running at, but not the duplex and by default will set it to half-duplex (don’t believe there is a way of changing this) which is the opposite of the BayStack.

Essentially, when configuring uplinks between different kit, always check the autonegotiation settings, see wikipedia for more info.

interface GigabitEthernet0/1
switchport trunk encap dot1q
speed 1000
duplex full
switchport mode trunk
no switchport mode access
no shutdown

It’s really an issue with the GBIC and chipsets than a software issue. In the PoE versions of the Ethernet Switch (formerly BayStack) 470 the chipset supports auto-negotiation on the GBIC/SFP ports. In the versions before that though there is no support for auto-negotiation on the GBIC/SFP ports.

I wouldn’t touch the software until you’ve had an opportunity to test the recommended fix.

Good Luck!