technology, networking and IP telephony
Posts tagged MLT
802.1Q VLAN Tagging on an Ethernet Routing Switch
14January 27, 2011
In my previous post I laid out the basics of how to configure multiple VLANs and enable IP routing on a stackable Avaya Ethernet Routing Switch. In this post I’m going to expand that topic to include trunking (802.1q) those VLANs to a second Ethernet Routing Switch. In this example I’ll add an Ethernet Routing Switch 4548 to the Ethernet Routing Switch 5520 that I had previously configured and deployed. We’ll create a Multi-Link Trunk between the two switches to bridge multiple VLANs across the 802.1q compliant link. Here’s a diagram of what the network should look like when we’re done;
In order to test I’ll move two of the IP phones to the Ethernet Routing Switch 4548 and I’ll use an old laptop to help verify the bridging.
Ethernet Routing Switch 4548
Let’s start with the Ethernet Routing Switch 4548GT-PWR and add the necessary configuration there first;
enable config t
We start by creating VLAN 100 and VLAN 200 on the Ethernet Routing Switch 4548;
vlan create 100 name "192-168-100-0/24" type port vlan members remove 1 25,27,29,31,33,35 vlan members add 100 25,27,29,31,33,35 vlan port 25,27,29,31,33,35 pvid 100 vlan create 200 name "192-168-200-0/24" type port vlan members remove 1 26,28,30,32,34,36 vlan members add 200 26,28,30,32,34,36 vlan port 26,28,30,32,34,36 pvid 200
I’m not going to create a Layer 3 IP interfaces on these VLANs since the Ethernet Routing Switch 5520 is already routing for us. We just want to bridge the frames between the two switches not route them (not in this post anyway). Now let’s configure the ports that will make up the Mulit-Link Trunk;
vlan port 47,48 tagging TagAll vlan members add 1 47,48 vlan members add 100 47,48 vlan members add 200 47,48 vlan port 47,48 pvid 1 mlt 1 disable mlt 1 name "MLT_to_ERS5520" mlt 1 learning disable mlt 1 member 47,48 mlt 1 enable
That’s pretty much it. We enabled tagging on the uplink/downlink ports, added the necessary VLANs to the ports and then created and enabled a MLT.
Ethernet Routing Switch 4548 – Show Configuration
That should be the configuration for the Ethernet Routing Switch 4548… let’s just have a quick look at the VLANs;
4548GT-PWR(config)#show vlan
Id Name Type Protocol User PID Active IVL/SVL Mgmt
--- -------------------- -------- ---------------- -------- ------ ------- ----
1 VLAN #1 Port None 0x0000 Yes IVL Yes
Port Members: 1-24,47-48
2 VLAN #2 Port None 0x0000 Yes IVL No
Port Members: 37-46
100 192-168-100-0/24 Port None 0x0000 Yes IVL No
Port Members: 25,27,29,31,33,35,47-48
200 192-168-200-0/24 Port None 0x0000 Yes IVL No
Port Members: 26,28,30,32,34,36,47-48
Total VLANs: 4Let’s just check the Multi-Link Trunk configuration… if that’s wrong we could end up with a loop in the network;
4548GT-PWR(config)#show mlt 1 Id Name Members Bpdu Mode Status -- -------------------- ---------------------- ------ -------------- ------- 1 MLT_to_ERS5520 47-48 All Basic Enabled
You can see from the commands above that the ports are configured with the appropriate VLANs and the MLT is enabled.
Ethernet Routing Switch 5520
Let’s add the necessary configuration to the Ethernet Routing Switch 5520-PWR. I’m not going to repeat all the commands I performed in the yesterday’s post, instead I’ll just build upon the previous configuration adding what we need for the 802.1q trunking and the Multi-Link Trunking;
enable config t
vlan port 47,48 tagging TagAll vlan members add 1 47,48 vlan members add 100 47,48 vlan members add 200 47,48 vlan port 47,48 pvid 1 mlt 1 disable mlt 1 name "MLT_to_ERS4548" mlt 1 learning disable mlt 1 member 47,48 mlt 1 enable
Ethernet Routing Switch 5520 – Show Configuration
That should be the configuration for the Ethernet Routing Switch 5520… let’s just have a quick look at the VLANs;
5520-48T-PWR#show vlan
Id Name Type Protocol PID Active IVL/SVL Mgmt
--- -------------------- -------- ---------------- -------- ------ ------- ----
1 test Port None 0x0000 Yes IVL Yes
Port Members: 1-12,37-48
100 192-168-100-0/24 Port None 0x0000 Yes IVL No
Port Members: 13-24,47-48
101 10-101-20-0/24 Port None 0x0000 Yes IVL No
Port Members: 25-36
200 192-168-200-0/24 Port None 0x0000 Yes IVL No
Port Members: 47-48
Total VLANs: 4Let’s just check the Multi-Link Trunk configuration… if that’s wrong we could end up with a loop in the network;
5520-48T-PWR#show mlt 1 Id Name Members Bpdu Mode Status Type -- ---------------- ---------------------- ------ -------------- ------- ------ 1 MLT_to_ERS4548 47-48 All Basic Enabled Trunk
Since all stackable Avaya Ethernet Routing Switches support Auto-MDIX I can just use two regular CAT5e patch cables to connect the switches together. If the switches didn’t support Auto-MDIX I would need to use two crossover cables between them.
Ethernet Routing Switch 4548 – Operational Status
With link up on ports 47 and 48 I can check the following information. The topology table will show me the physical connections between the two switches. The MAC/FDB table will show me that there are multiple MAC/FDB entries in VLANs 100 and 200 being learned across “Trunk 1″. The LLDP table will show me the Avaya IP phones that I’ve connected to ports 25 and 26.
4548GT-PWR#show autotopology nmm-table
LSlot RSlot
LPort IP Addr Seg ID MAC Addr Chassis Type BT LS CS RPort
----- --------------- -------- ------------ ---------------- -- --- ---- -----
0/ 0 192.168.1.25 0x000000 001E7E7C2C01 4548GT-PWR 12 Yes HTBT NA
1/47 192.168.1.50 0x000130 001F0ACEBC01 5520-48T-PWR 12 Yes HTBT 1/48
1/48 192.168.1.50 0x00012f 001F0ACEBC01 5520-48T-PWR 12 Yes HTBT 1/47
4548GT-PWR#show mac-address-table
Mac Address Table Aging Time: 300
Number of addresses: 20
MAC Address Vid Source MAC Address Vid Source
----------------- ---- ------- ----------------- ---- -------
00-02-B3-CB-77-A2 1 Port:19 00-04-61-9E-46-7E 1 Port:21
00-0C-29-64-33-F9 1 Port:19 00-0C-29-A5-CB-54 1 Port:19
00-18-01-EA-F4-45 1 Port: 1 00-1C-11-6B-DC-6B 1 Port: 1
00-1C-11-6D-15-27 1 Port: 1 00-1C-11-6D-15-DC 1 Port: 1
00-1E-7E-7C-2C-00 1 00-1E-7E-7C-2C-40 1
00-1F-0A-CE-BC-40 1 Trunk:1 00-1F-D0-D0-BE-2D 1 Port:17
00-23-EE-96-AA-21 1 Port: 1 00-24-B5-F6-94-02 1 Trunk:1
00-0A-E4-76-9C-C8 2 Port:45 00-1F-0A-CE-BC-01 2 Trunk:1
00-24-DC-DF-0D-08 2 Port:43 00-A0-F8-5E-CE-BC 2 Port:39
00-1F-0A-CE-BC-41 100 Trunk:1 00-24-7F-99-84-70 100 Port:25
00-24-7F-99-84-E9 100 Trunk:1 00-1E-CA-F3-1D-B4 200 Port:26
4548GT-PWR#show lldp neighbor
-------------------------------------------------------------------------------
lldp neighbor
-------------------------------------------------------------------------------
Port: 26 Index: 4 Time: 13 days, 22:42:31
ChassisId: Network address IPv4 192.168.200.5
PortId: MAC address 00:1e:ca:f3:1d:b4
SysCap: TB / TB (Supported/Enabled)
PortDesc: Avaya IP Phone
SysDescr: Avaya IP Telephone 1120E, Firmware:SIP1120e04.00.04.00
-------------------------------------------------------------------------------
Port: 25 Index: 6 Time: 13 days, 22:43:48
ChassisId: Network address IPv4 192.168.100.98
PortId: MAC address 00:24:7f:99:84:70
SysCap: TB / TB (Supported/Enabled)
PortDesc: Avaya IP Phone
SysDescr: Avaya IP Telephone 1220, Firmware:SIP12x004.00.04.00
-------------------------------------------------------------------------------
Sys capability: O-Other; R-Repeater; B-Bridge; W-WLAN accesspoint; r-Router;
T-Telephone; D-DOCSIS cable device; S-Station only.
Total neighbors: 2Ethernet Routing Switch 5520 – Operational Status
I can check all the same information on the ERS5520.. The topology table will show me the physical connections between the two switches. The MAC/FDB table will show me that there are multiple MAC/FDB entries in VLANs 100 and 200 being learned across “Trunk 1″. The LLDP table will show me the Avaya IP phones that I’ve connected to ports 13 and 25.
5520-48T-PWR#show autotopology nmm-table
LSlot RSlot
LPort IP Addr Seg ID MAC Addr Chassis Type BT LS CS RPort
----- --------------- -------- ------------ ---------------- -- --- ---- -----
0/ 0 192.168.1.50 0x000000 001F0ACEBC01 5520-48T-PWR 12 Yes TPCH NA
1/47 192.168.1.25 0x00012f 001E7E7C2C01 4548GT-PWR 12 Yes TPCH 1/47
1/48 192.168.1.25 0x000130 001E7E7C2C01 4548GT-PWR 12 Yes TPCH 1/48
5520-48T-PWR#show mac-address-table
Mac Address Table Aging Time: 300
Number of addresses: 16
MAC Address Vid Source MAC Address Vid Source
----------------- ---- ------- ----------------- ---- -------
00-02-B3-CB-77-A2 1 Trunk:1 00-04-61-9E-46-7E 1 Trunk:1
00-0C-29-64-33-F9 1 Trunk:1 00-0C-29-A5-CB-54 1 Trunk:1
00-18-01-EA-F4-45 1 Trunk:1 00-1C-11-6B-DC-6B 1 Trunk:1
00-1C-11-6D-15-27 1 Trunk:1 00-1C-11-6D-15-DC 1 Trunk:1
00-1E-7E-7C-2C-01 1 Trunk:1 00-1E-7E-7C-2C-40 1 Trunk:1
00-1F-0A-CE-BC-00 1 00-1F-0A-CE-BC-40 1
00-1F-D0-D0-BE-2D 1 Trunk:1 00-23-EE-96-AA-21 1 Trunk:1
00-24-B5-F6-94-02 1 Port: 9 00-1F-0A-CE-BC-41 100
00-24-7F-99-84-70 100 Trunk:1 00-24-7F-99-84-E9 100 Port:15
00-1E-CA-F3-1D-B4 200 Trunk:1
5520-48T-PWR#show lldp neighbor
-------------------------------------------------------------------------------
lldp neighbor
-------------------------------------------------------------------------------
Port: 13 Index: 5 Time: 0 days, 00:02:00
ChassisId: Network address IPv4 192.168.100.4
PortId: MAC address 00:24:b5:f6:94:02
SysCap: TB / TB (Supported/Enabled)
PortDesc: Avaya IP Phone
SysDescr: Avaya IP Telephone 1165E, Firmware:SIP1165e04.00.04.00
-------------------------------------------------------------------------------
Port: 25 Index: 6 Time: 0 days, 00:02:19
ChassisId: Network address IPv4 192.168.200.99
PortId: MAC address 00:24:7f:99:84:e9
SysCap: TB / TB (Supported/Enabled)
PortDesc: Avaya IP Phone
SysDescr: Avaya IP Telephone 1220, Firmware:SIP12x004.00.04.00
-------------------------------------------------------------------------------
Sys capability: O-Other; R-Repeater; B-Bridge; W-WLAN accesspoint; r-Router;
T-Telephone; D-DOCSIS cable device; S-Station only.
Total neighbors: 2Would you be interested in seeing a screencast of this whole process?
Let me know if you have any questions or would like to point out corrections!
Cheers!
Avaya and Cisco Interoperability Technical Configuration Guide
6June 20, 2010
Avaya has release an updated technical configuration guide geared towards the interoperability between Cisco and Avaya equipment.The document covers a lot of information including EtherChannel to MLT interoperability, Spanning Tree interoperability, Nortel IP phones connecting to Cisco switches and Cisco IP phones connecting to Nortel switches.
It’s definitely well worth the time to review.
Cheers!
Nortel ERS 5520 PwR Switch
79October 23, 2007
Update: July 30, 2009
I’ve added a command to disable the User Interface Button (UI Button) “no ui-button enable”.
I’ve added a command to disable the User Interface Button (UI Button) “no ui-button enable”.
Update: February 7, 2009
It was time to update this article with some additional information and settings that I’m now using in all my switch deployments. The big change is the updated ADAC MAC address table. Please also note the VLACP time-out scale change and I’ve updated the year field for the Daylight Saving Time change.
Update: August 13, 2008
This was one of the first articles I wrote back in October 2007 and it is by far the most popular article out of all 110 articles that I currently have published. With that said I decided to come back and spruce up this post with some additional “tweaks” that I’ve added over the past 10 months. I’m also going to attack a link to a text file so folks can just download the file of commands, tweak the specific individual settings such as IP address and VLAN information, and then cut and paste into the CLI interface of the Nortel Ethernet Routing Switch 5520. It will hopefully save folks from having to cut and paste each section.
Note: just a quick warning about cutting and pasting into the CLI interface, I’ve often found that the buffer will overflow if I try to paste an entire configuration at once. I usually need to break it into at least two or three sections and cut and paste those section one at a time.
In this post I’ll try to outline how you can configure the Nortel Ethernet Routing Switch 5520 in a VoIP environment using Nortel i2002/i2004 Internet Telephones (this procedure will also work the same with the i2007/1120E/
1140E phones).
You’ll obviously need a ERS 5520 switch and you’ll need SW 5.0.6.22 or later and FW 5.0.0.3 or later (there are known issues with earlier software versions that create inconsistent results using LLDP with the i2002/i2004 phones). I would strongly advise that you start with a default configuration. From the CLI issue the following commands to reset the switch to factory defaults;
5520-48T-PWR> enable 5520-48T-PWR# boot default
The switch should reboot with a default configuration. Let’s proceed with the configuration;
5520-48T-PWR> enable 5520-48T-PWR# configure terminal
Let’s set the local read-only and read-write passwords;
5520-48T-PWR (config)#cli password read-only readpass 5520-48T-PWR (config)#cli password read-write writepass 5520-48T-PWR (config)#cli password serial local 5520-48T-PWR (config)#cli password telnet local
Let’s disable the user interface button (UI button);
5520-48T-PWR (config)# no ui-button enableEnable AUTOPVID;
5520-48T-PWR (config)# vlan configcontrol autopvid
We’ll be up linking this switch using a MultiLink trunk on ports 47 and 48 so we’ll enable tagging on the fiber uplinks;
5520-48T-PWR (config)# vlan ports 47,48 tagging enable
Let’s create the data VLAN (VID 100) and management VLAN (VID 200) on the switch;
5520-48T-PWR (config)# vlan members remove 1 ALL 5520-48T-PWR (config)# vlan create 200 name "10-1-200-0/24" type port 5520-48T-PWR (config)# vlan members add 200 47,48 5520-48T-PWR (config)# vlan create 100 name "10-1-100-0/24" type port 5520-48T-PWR (config)# vlan members add 100 1-48 5520-48T-PWR (config)# vlan port 1-46 pvid 100 5520-48T-PWR (config)# vlan port 47,48 pvid 200
Let’s make VLAN 200 the management VLAN and assign the IP address;
5520-48T-PWR (config)# vlan mgmt 200 5520-48T-PWR (config)# ip address switch 10.1.200.10 netmask 255.255.255.0 default-gateway 10.1.200.1
Let’s setup Simple Network Management Protocol (SNMP);
5520-48T-PWR (config)# snmp-server authentication-trap disable 5520-48T-PWR (config)# snmp-server community ro 5520-48T-PWR (config)# snmp-server community rw 5520-48T-PWR (config)# snmp-server host
Let’s configure the logging so it will overwrite the oldest events;
5520-48T-PWR (config)# logging volatile overwrite 5520-48T-PWR (config)# logging enable
Let’s setup Simple Network Time Protocol (SNTP);
5520-48T-PWR (config)# sntp server primary address 5520-48T-PWR (config)# sntp server secondary address 5520-48T-PWR (config)# sntp enable
Depending on the version of switch software your running you may be able to configure Daylight Saving Time;
5520-48T-PWR (config)#clock time-zone EST -5 5520-48T-PWR (config)#clock summer-time EDT date 9 Mar 2009 2:00 2 Nov 2009 2:00 +60
Let’s setup the MultiLink trunk that will connect the switch back to the backbone;
5520-48T-PWR (config)# mlt 1 disable 5520-48T-PWR (config)# mlt 1 name "MLT-8600" 5520-48T-PWR (config)# mlt 1 learning disable 5520-48T-PWR (config)# mlt 1 member 47,48 5520-48T-PWR (config)# mlt 1 enable
Let’s setup ADAC (Automatic Detection and Automatic Configuration) for our i2002/i2004 phones. We’ll using VLAN 50 as our voice VLAN and we’ll use port 48 as our uplink (the switch will add 47 automatically because of the MLT configuration). There is a new command to clear the ADAC MAC address table that may be missing from earlier versions, “no adac mac-range-table”. I’ve also updated the list of entries that I use.
5520-48T-PWR (config)# adac voice-vlan 50 5520-48T-PWR (config)# adac op-mode tagged-frames 5520-48T-PWR (config)# adac uplink-port 48 5520-48T-PWR (config)# no adac mac-range-table 5520-48T-PWR (config)# adac mac-range-table low-end 00:0a:e4:75:00:00 high-end 00:0a:e4:75:ff:ff 5520-48T-PWR (config)# adac mac-range-table low-end 00:13:65:00:00:00 high-end 00:13:65:ff:ff:ff 5520-48T-PWR (config)# adac mac-range-table low-end 00:14:c2:00:00:00 high-end 00:14:c2:ff:ff:ff 5520-48T-PWR (config)# adac mac-range-table low-end 00:16:ca:00:00:00 high-end 00:16:ca:ff:ff:ff 5520-48T-PWR (config)# adac mac-range-table low-end 00:17:65:00:00:00 high-end 00:17:65:ff:ff:ff 5520-48T-PWR (config)# adac mac-range-table low-end 00:18:b0:00:00:00 high-end 00:18:b0:ff:ff:ff 5520-48T-PWR (config)# adac mac-range-table low-end 00:19:69:00:00:00 high-end 00:19:69:ff:ff:ff 5520-48T-PWR (config)# adac mac-range-table low-end 00:19:e1:00:00:00 high-end 00:19:e1:ff:ff:ff 5520-48T-PWR (config)# adac mac-range-table low-end 00:1b:ba:00:00:00 high-end 00:1b:ba:ff:ff:ff 5520-48T-PWR (config)# adac mac-range-table low-end 00:1e:ca:00:00:00 high-end 00:1e:ca:ff:ff:ff 5520-48T-PWR (config)# adac mac-range-table low-end 00:22:67:00:00:00 high-end 00:22:67:ff:ff:ff 5520-48T-PWR (config)# adac enable
We need to strip the 802.1q tag from any packets in the PVID VLAN from going to the phone. In this design we’re expecting to connect IP phones to ports 1 – 46.
5520-48T-PWR (config)# vlan port 1-46 tagging untagpvidOnly
Let’s configure LLDP for the ports we expect to connect IP phones (1 – 46);
5520-48T-PWR (config)# interface fastEthernet 1-46
5520-48T-PWR (config-if)# vlan ports 1-46 filter-unregistered-frames disable
5520-48T-PWR (config-if)# lldp tx-tlv port-desc sys-cap sys-desc sys-name
5520-48T-PWR (config-if)# lldp status txAndRx config-notification
5520-48T-PWR (config-if)# lldp tx-tlv med extendedPSE med-capabilities network-policy
5520-48T-PWR (config-if)# poe poe-priority high
5520-48T-PWR (config-if)# spanning-tree learning fast
5520-48T-PWR (config-if)# adac enable
5520-48T-PWR (config-if)# exitThe option in RED above was added after an issue was discovered when trying to upgrade the firmware on the IP phones. The filter-unregistered-frames is enabled by default and should be disabled to avoid and issues with upgrading the firmware on the IP phones. We are attempting to investigate further with Nortel and our voice vendor Shared Technologies.
Let’s disable the two remaining ports that share the GBIC interfaces incase we need those in the future;
5520-48T-PWR (config)# interface fastEthernet 45-46 5520-48T-PWR (config-if)# shutdown 5520-48T-PWR (config-if)# exit
Let’s setup a QoS interface group to trust all traffic that will ingress on the fiber uplinks. By default the ERS 5520 switch will strip all QoS tags on all ports. Thankfully ADAC will take care of the QoS settings for all VoIP traffic.
5520-48T-PWR (config)# qos if-group name allUpLinks class trusted 5520-48T-PWR (config)# interface fastEthernet 47,48 5520-48T-PWR (config)# qos if-assign port 47,48 name allUpLinks 5520-48T-PWR (config)# exit
Let’s set the SNMP information;
5520-48T-PWR (config)# snmp-server name "sw-icr1-1east.sub.domain.org" 5520-48T-PWR (config)# snmp-server location "Acme Internet Phone Company (ICR1)" 5520-48T-PWR (config)# snmp-server contact "Network Infrastructure Team"
Let’s enable rate limiting for all broadcast and multicast traffic to 10% of the link;
5520-48T-PWR (config)# interface fastEthernet ALL 5520-48T-PWR (config-if)# rate-limit both 5 5520-48T-PWR (config-if)# exit
Let’s setup VLACP (Virtual Link Aggregation Protocol) on the uplinks to the core;
5520-48T-PWR (config)# interface fastEthernet 47,48 5520-48T-PWR (config-if)# vlacp port 47,48 timeout short 5520-48T-PWR (config-if)# vlacp port 47,48 timeout-scale 5 5520-48T-PWR (config-if)# vlacp port 47,48 enable 5520-48T-PWR (config-if)# exit 5520-48T-PWR (config)# vlacp enable
That’s it your done! Well hopefully your done.
In my next post I’ll tell you what DHCP options you’ll need to configure on your DHCP server in order for the phones to boot properly and connect to the Nortel Call Server.
Cheers!
