diff options
author | Anuradha Karuppiah <anuradhak@cumulusnetworks.com> | 2019-03-24 20:31:50 +0100 |
---|---|---|
committer | Anuradha Karuppiah <anuradhak@cumulusnetworks.com> | 2019-04-20 17:33:23 +0200 |
commit | 37c3fd98e7a91f5985a3fb5f8d9dacb39be92625 (patch) | |
tree | b58774b2083fb3adfe0b61d61eee72a5303b668f /pimd/pim_vxlan.h | |
parent | pimd: setup multicast vxlan tunnel termination device (diff) | |
download | frr-37c3fd98e7a91f5985a3fb5f8d9dacb39be92625.tar.xz frr-37c3fd98e7a91f5985a3fb5f8d9dacb39be92625.zip |
pimd: handling termination device in the MFC
1. special handling of term device in orig mroutes -
The multicast-vxlan termination device ipmr-lo is added to the (*, G)
mroute -
(0.0.0.0, 239.1.1.100) Iif: uplink-1 Oifs: uplink-1 ipmr-lo
This means that it will be inherited into all the SG entries including the
origination mroute. However we cannot terminate the traffic we originate
so some special handling is needed to exclude the termination device
in the origination entries -
27.0.0.7, 239.1.1.100) Iif: lo Oifs: uplink-1
2. special handling of term device on the MLAG pair -
Both MLAG switches pull down BUM-MDT traffic but only one (the DF) can
terminate the traffic. The non-DF must not exclude the termination device
from the MFC to prevent dups to the overlay.
DF -
root@TORC11:~# ip mr |grep "(0.0.0.0, 239.1.1.100)"
(0.0.0.0, 239.1.1.100) Iif: uplink-1 Oifs: uplink-1 ipmr-lo State: resolved
root@TORC11:~#
non-DF -
root@TORC12:~# ip mr |grep "(0.0.0.0, 239.1.1.100)"
(0.0.0.0, 239.1.1.100) Iif: uplink-1 Oifs: uplink-1 State: resolved
root@TORC12:~#
Signed-off-by: Anuradha Karuppiah <anuradhak@cumulusnetworks.com>
Diffstat (limited to 'pimd/pim_vxlan.h')
0 files changed, 0 insertions, 0 deletions