Tunneling CDP frames
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎09-28-2015 02:10 PM
Best solutions out there to tunnel CDP in a mixed Extreme network...
Edge is 150-460 summit running 12.6 to 15.6
Core is 670 or 8900 MSM 128 running 15.4 - 15.6
Some support L2PT and some do not. I think what I need to do is build a counter profile to see where the CDP are failing and then build the tunnel there for the vlans I need to forward cdp
Here is what I am using for this which when applied to specific vlan on edge uni port works or to trunk port on next hop works. Problem is this going to be a big tasks to go through 100 plus vlans one segment at a time to find the blocking points.
entry cdp_pdu {if {
ethernet-destination-address 01:00:0c??cc:cc ;
snap-type 0x2000 ;
} then {
count cdp_ingress ;
}
}
Another question is when did replace-ethernet-destination-add get added to the image and made active. I have not found a version of code that supports this statement yet. I guess it is not needed on switches that support L2PT profiles?
Problem started when we started updating code from 12.6 to 15.xx it seemed CDP started being blocked and not passing through the network.
Thanks ahead of time
Edge is 150-460 summit running 12.6 to 15.6
Core is 670 or 8900 MSM 128 running 15.4 - 15.6
Some support L2PT and some do not. I think what I need to do is build a counter profile to see where the CDP are failing and then build the tunnel there for the vlans I need to forward cdp
Here is what I am using for this which when applied to specific vlan on edge uni port works or to trunk port on next hop works. Problem is this going to be a big tasks to go through 100 plus vlans one segment at a time to find the blocking points.
entry cdp_pdu {if {
ethernet-destination-address 01:00:0c??cc:cc ;
snap-type 0x2000 ;
} then {
count cdp_ingress ;
}
}
Another question is when did replace-ethernet-destination-add get added to the image and made active. I have not found a version of code that supports this statement yet. I guess it is not needed on switches that support L2PT profiles?
Problem started when we started updating code from 12.6 to 15.xx it seemed CDP started being blocked and not passing through the network.
Thanks ahead of time
11 REPLIES 11
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎09-28-2015 11:48 PM
Hi Etherman,
From 15.4, We (EXOS) started supporting CDP protocol and it is enabled by default.
So, the CDP packets may be processed by the switch and not forwarded across to the Cisco device. Try disabling the CDP protocol on the Extreme switch(which were upgraded to 15.4 and above) ports and check if that helps.
Command: disable cdp ports <>
if that does not help, the following article will guide you to configure l2tp profile to allow the CDP packets.
https://gtacknowledge.extremenetworks.com/articles/Solution/Layer-two-layer-2-protocol-packets-does-...
Hope this helps!
From 15.4, We (EXOS) started supporting CDP protocol and it is enabled by default.
So, the CDP packets may be processed by the switch and not forwarded across to the Cisco device. Try disabling the CDP protocol on the Extreme switch(which were upgraded to 15.4 and above) ports and check if that helps.
Command: disable cdp ports <>
if that does not help, the following article will guide you to configure l2tp profile to allow the CDP packets.
https://gtacknowledge.extremenetworks.com/articles/Solution/Layer-two-layer-2-protocol-packets-does-...
Hope this helps!
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎09-28-2015 06:21 PM
I totally agree. CDP started blocking at 15.5. No idea why they implemented this "feature". Why not have the one that wants cdp enable it ?
