12-18-2020 06:20 AM
Solved! Go to Solution.
01-08-2021
07:54 AM
- last edited on
01-12-2021
06:24 AM
by
Jonathan Cuthbert
Answering my own question:
Though in SDA we provide subnet across FEs and mobility between them, The multicast however works over L3 and not L2 even when source and receiver are in same subnet but attached to different FEs.
This requires every HOP to decrement TTL. There are applications which work within same subnet with TTL=1 which doesn't work in SDA. Today SDA has no solution to such problems. There is an ongoing enhancement request to address this issue.
01-08-2021
07:54 AM
- last edited on
01-12-2021
06:24 AM
by
Jonathan Cuthbert
Answering my own question:
Though in SDA we provide subnet across FEs and mobility between them, The multicast however works over L3 and not L2 even when source and receiver are in same subnet but attached to different FEs.
This requires every HOP to decrement TTL. There are applications which work within same subnet with TTL=1 which doesn't work in SDA. Today SDA has no solution to such problems. There is an ongoing enhancement request to address this issue.
02-08-2024 07:11 AM
Hello, I have a similar problem too. The application is PTPv1 that use TTL=1. Has Cisco deployed any enhancement to address this issue? Thanks
02-08-2024 08:54 AM
For PTPv1 and TTL=1 you need 17.6+ and L2 Flooding for it to work.Which requires underlay multicast.
This was introduced in via https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvr13592
Regards
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