07-16-2014 11:10 PM - edited 03-07-2019 08:05 PM
Hi,
we are using a WS-C3750-48TS as a transparent switch for multiple separated networks. Now the switch shall also forward incoming LLDP frames to the appropriate egress ports. Therefore i have added the command "l2protocol-tunnel lldp" to each interface, where this feature is needed. So my configuration looks like (excerpt):
...
spanning-tree mode pvst
spanning-tree extend system-id
no spanning-tree vlan 1,4051-4062
!
vlan internal allocation policy ascending
!
vlan 4051-4062
!
interface FastEthernet1/0/1
switchport access vlan 4051
switchport mode dot1q-tunnel
l2protocol-tunnel lldp
no keepalive
no cdp enable
!
interface FastEthernet1/0/2
switchport access vlan 4051
switchport mode dot1q-tunnel
l2protocol-tunnel lldp
no keepalive
no cdp enable
!
...
I have tested this setup with SW version c3750-ipbasek9-mz.122-55.SE8 and c3750-ipbasek9-mz.122-55.SE9. The result was that no incoming LLDP frames have been counted by the switch (checked with "show l2protocol-tunnel") and also no LLDP frames have been forwarded. As a countercheck i have done the same procedure with STP (l2protocol-tunnel stp) and CDP (l2protocol-tunnel cdp), which was successful. So in principial the L2 tunneling is working but not for LLDP. Do i need to add something in addition in the configuration? Or is there a SW version which is known to work correctly? Or is this not fully implemented since LLDP tunneling is not explicitly mentioned in user manual?
Best regards
Benjamin
07-17-2014 12:54 AM
Hi,
You can check the cisco feature navigator to find with your requirement.
http://www.cisco.com/c/en/us/support/switches/catalyst-3750-series-switches/tsd-products-support-series-home.html?referring_site=bodynav
I believe 12.2.55SE version of IOS supports that. But better if you could search in that tool and findout with the requirement,
for 12.2.55SE
12-10-2015 03:21 AM
Can someone explain the difference between l2protocol forward <> and l2protocol tunnel <> ?? how are the packets edited on the ingress and egress PE nodes ??
03-22-2018 04:55 AM - edited 03-22-2018 04:56 AM
Hi,
I am testing L2 protocol tunnel for LLDP on ME3400 and cant make it work.
ME3400#4-fa0/1--------------fa0/1 ME3400#2-Gi0/1--------
( Customer Switch) ( Edge Switch )
Customer Switch
------------------
ME3400_4#sh running-config interface fastEthernet 0/1
Building configuration...
Current configuration : 48 bytes
!
interface FastEthernet0/1
port-type nni
end
ME3400_4#sh ll
ME3400_4#sh lldp in
ME3400_4#sh lldp interface fas
ME3400_4#sh lldp interface fastEthernet 0/1
FastEthernet0/1:
Tx: enabled
Rx: enabled
Tx state: IDLE
Rx state: WAIT FOR FRAME
ME3400_4#
Edge Switch
--------------
ME3400_2#sh running-config interface fastEthernet 0/1
Building configuration...
Current configuration : 103 bytes
!
interface FastEthernet0/1
l2protocol-tunnel cdp
l2protocol-tunnel lldp
l2protocol-tunnel stp
end
ME3400_2#
ME3400_2#show l2protocol-tunnel interface fastEthernet 0/1
COS for Encapsulated Packets: 5
Port Protocol Shutdown Drop Encaps Decaps Drop
Threshold Threshold Counter Counter Counter
------------------- ----------- --------- --------- --------- --------- ---------
Fa0/1 cdp ---- ---- 1 0 0
lldp ---- ---- 0 0 0 >>>>>>>>>>>>>no lldp counters
stp ---- ---- 27 0 0
--- ---- ---- ---- ---- ----
--- ---- ---- ---- ---- ----
--- ---- ---- ---- ---- ----
--- ---- ---- ---- ---- ----
ME3400_2#
I tried other configuration as well but it did not work.
Can anyone please help me with correct config. Below are the SW details I am using :-
Switch Ports Model SW Version SW Image
------ ----- ----- ---------- ----------
* 1 26 ME-3400-24TS-A 12.2(54)SE ME340x-METROACCESSK9-M
Regards
Naga
08-15-2019 11:20 PM
lldp needs to be enabled globally before the lldp l2protocol-tunnel will work.
lldp run
08-16-2019 02:06 AM - edited 08-16-2019 02:07 AM
Hello Perko,
it makes sense so the "provider side" switch needs to enable LLDP at global level in order to be able to process and tunnel LLDP frames received on 802.1Q tunnel interface(s).
Reading the thread I thought that it was an IOS version issue.
thanks for your valuable feedback
Best Regards
Giuseppe
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide