technology, networking and IP telephony
Posts tagged LLDP
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!
LLDP with Cisco 3750
25January 16, 2009
Nortel has released a Technical Configuration Guide designed to assist technical users configuring Nortel IP Phones connected to Cisco switches. The document makes specific references to the Cisco 3750 switch but the commands will apply to any Cisco switch that supports that specific feature.
I applaud Nortel for for making these Technical Configuration Guides available to users. It helps to broaden Nortel’s product reach and it empowers Nortel users to understand the different configuration options. I’d like to see Nortel get these documents indexed by Google or even there own internal Knowledgebase search engine.
In short you can use LLDP (802.1ab) on a Cisco 3750 to configure the Voice VLAN much the same way as you might on a Nortel ERS5520 switch using ADAC/LLDP. For those Cisco shops that are using Nortel Succession for voice this should be a welcome capability.
As in the past I’m going to post the document on my website;
http://www.michaelfmcnamara.com/files/ClientsInteropCisco_L2_1.1.pdf
As I’ve commented in the past it’s quite possible that Nortel may object to my “copying” of these documents. The goal is to make them readily available to Nortel users and allow them to be indexed by Google. I believe there are now quite a few Nortel corporate folks and engineers reading this blog, please contact me if you have concerns about me posting these documents.
Cheers!
ERS 5520 Switch v5.1 Software
0November 20, 2007
Nortel has just recently released v5.1 software for their Ethernet Routing Switch (ERS) 5500 Series.
There are some enhancements that affect how ADAC/LLDP function on the ERS 5520 switch. From the release notes;
IEEE 802.1ab and ADAC linkage
Nortel introduced the 802.1ab and Auto Detection Auto Configuration(ADAC) features to Release 5.0 to address converged applications. In Release 5.1, the functionality of 802.1ab and ADAC is combined: ADAC uses 802.1ab/LLDP as the detection mechanism to determine the identity of the attached device (that is, a Nortel IP phone that supports 802.1ab Media Endpoint Devices type, length, and value descriptions [MED TLV]). The Auto Configuration functionality of ADAC applies the configuration to the port.
Configurable using NNCLI, ACG, and Device Manager.
It looks like it will no longer be necessary to maintain the list of MAC prefixes for all Nortel Internet Telephones. If you recall from some of my previous posts I needed to manually update the list of MAC prefixes used by my ERS 5520 switches in order to get many of my i2002/i2004 Internet Telephones to be detected properly. The default list of MAC prefixes usually didn’t cover all the i2002/i2004/i2007/1140e Internet Telephones I had installed throughout my organization. In previous articles we enabled ADAC like so;
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)# 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: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:0a:e4:75:00:00 high-end 00:0a:e4:75: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: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 520-48T-PWR (config)# adac enable
I haven’t actually tested this myself yet but supposedly if LLDP detects an Internet Telephone it will pass that information to ADAC without the need of evaluating the device’s MAC address.
The 5.1 release also now supports the 1000Base-BX SFP;
BX SFP support
Many customers have high density gigabit requirements, but lack the fiber density to deploy. BX SFPs helps alleviate this issue by allowing a single strand of fiber to facilitate communication.
Nortel introduces support for 1000BaseBX10 module with release 5.1. The modules are single fiber, bidirectional SFP transceivers. Two types of modules are available:
• 1310nm (BX10-U) transceiver
• 1490nm (BX10-D) transceiver
The 1000BaseBX10-D device is always connected to a 1000BaseBX10-U device with a single strand of standard single-mode fiber. The operating transmission range is up to 10 km. The fiber uses a GBIC LC connector on each end.
If the 1000BaseBX10-U is not connected to the 1000BaseBX10-D device, the signals are not received properly and the Link LED does not illuminate. You can configure BX SFP Support through the NNCLI, ACG, or Device Manager.
The 1000BASE-BX bidirectional SFPs provide Gigabit Ethernet connectivity over a single fiber.
As shown in the figure, the transmit (Tx) and receive (Rx) paths share the same fiber by using two different wavelengths. One model transmits at 1310 nm and receives at 1490 nm, while the mating model transmits at 1490 nm and receives at 1310 nm. You can only connect a mating pair.
You can use 1000BASE-BX SFPs to double the number of your fiber links. For example, if you have 20 installed fiber pairs with 20 conventional ports connected, you can use 1000BASE-BX SFPs to expand to 40 ports, using the same fiber.
The long wavelength optical transceivers used in these models provide variable distance ranges using single mode fiber optic cabling.
Cheers!
