Technorati 标签: M×××, DATA, MDT, MPLS, CCIE

(draft-rosen-***-multicast cisco rosen这个人写的草案主要描述了组播域的概念)

(RFC2784中定义如何采用MPLS进行组播转发 farinacci-mpls-multicast)

m×××的体系结构

mVRF 就是可以支持组播转发的VRF(组播路由转发表)

MDT (multicast distribution tree) 就是运行在SP网络里的组播树(有两种default-MDT,data-MDT)

default-MDT---用来发送低带宽组播流量或去行广泛公布接收都集合的流量,通常是用于在组播域的PE路由器之间发送组播控制流量

data-MDT---用于高带宽源流量穿过P网络到达感兴趣的PE路由器。它避免将不必要的客户组播流量泛洪到组播域中所有的PE路由器。
可能这里描述的不是太清楚.这样说吧,如果拿密集模式来做为示例,组播源每三分钟把流量发送到组播客户端,如果客户端B没有接收端,那么客户端的路由器会发送一个剪枝消息给源,这个时候组播流量不会继续再在客户端B进行泛红。至少,每三分钟我没有接收者的客户端就只收到一点无用的组播流量。保证了组播流量不在枝干上面泛红。
但是对于M×××来说,如果有三个PE, PE-A/B/C,三个PE配置相同的MDT default 224.1.1.1, 实际上就是每个PE之间建立了一个full mesh的全连接,这样来说,就没有什么每三分钟的事情了,假如A是源,B是接收者,C是非接收者,在MPLS ××× 域中,组播量会一直不停的泛红到PEB和PEC,不会像密集模式一样进行剪枝,通过GRE tunnel不停的泛红,虽然C是非接收者,组播流量也会泛红到C,然后被C丢弃,这样的话就对C PE的系统资源进行了无端的浪费。首先接收到了一堆没有用的报文,占用了宝贵的接口流量,然后CPU和相关表项需要判断是否需要丢包,占用了内存和CPU的资源。有百害而无一益.所以这里才推出了Data-MDT.

default-MDT是必须的,因为要发送组播控制流量,data-MDT是可选的.但是就运营商来说,因为PE数量众多,没有不配置data mdt的。

MTI (multicast tunnel interface) 在运行相同default-MDT的PE之间建立的点到多点GRE隧道用于封装客户组播流量。外层是SP组播消息。

几个特性:1.根据default-MDT自动创建,不能被配置。

2.源是MBGP的更新源,目标是defaul-MDT配置的组播地址。因为源是MBGP的更新源,且MTI是用于跑组播,且MTI是不可配置的,所以一定要在MBGP更新源上运行组播ip pim sparse/dense-mode.

3.MTI不会出现在相关的VRF的单播路由表中,没有单播流量会在MTI上转发。

实现原理

在SP(service privider)中有自己的组播路由,客户有自己的组播路由,当source发组播到达R2(PE MVRF)后,被封装成源是MBGP更新源,目标是配置的DEFAULT-MDT的组地址,所有已配置相同default-MDT组地址的PE都在同一P2M的TUNNEL中,通过SP的RP都能收到此组播报文,当这个被GRE封装的组播到达PE,PE去掉外层TUNNEL把原始组播报文发给CE的RP。对于receiver发送的join报文和RP的选举报文都是通过GRE封装通过default-MDT组播地址发给其它PE的。

因为组播控制信息是在default-MDT上传播,所以default-MDT是必须配置的。

clip_p_w_picpath002

default-MDT的问题是,所有的组播流量都会被所有的PE(如果它们配置了相同的default-mdt组播地址)收到,就算没有接收者。因为它们属于同一个tunnel.解决这个问题用DATA-MDT。

data-mdt的工作原理

先了解几个规则和概念:

1. 配置

ip vrf a

mdt default 239.192.10.2

mdt data 239.192.20.32 0.0.0.15 threshold 1

掩码15表示有239.192.20.32到239.192.20.47做为DATA的组。 1 是kb,指的是组播流量超过1kb就切换到data-mdt(注:这个threshold是对于每个组播流而言的,不是总的组播流量)

2. 数据MDT群组映射(S,G,Data-MDT)。data-mdt join (使用UDP port 3232, 发给ALL0PIM-ROUTERS(224.0.0.13),格式见下

type length reserve

customer ××× source

customer ××× group

3. P-join (PE下面如果有感兴趣的接收者,PE就会发P-join)

工作原理:

1. 接源的PE的MVRF收到源的组播流量会通过default-mdt发给所有的PE,不久就会超过threshold. 就会在DATA池里选择一个组,比如239.192.20.32做为将要把此组播流量切换的组地址。然后发一个'数据MDT群组映射‘ 包含 客户S,G,DATA组播地址‘给所有的PE。

2. PE收到这个s,g,data group后,如果他下面有对于S,G的接收者,它就发一个P-join,这样它就可以通过DATA组播地址来收流量了,在源PE处在把数据通过DATA组播地直发送时会等待几秒,允许接收PE从default-mdt切换时不丢失分组。

3. 没有相应接收者的PE,将在内部缓存S,G,DATA-MDT,这样如果一旦有加入者,就可能缩短加入延迟。源PE每隔一分钟发送一次S,G,DATA-MDT,缓存将被刷新,3分钟后没有收到,超时删除。

规则1. S,G,DATA-MDT只在接源的PE mVRF入口触发。

2. 当流量低于threshold,源将切换回default-mdt,为避免频繁切换流量只在DATA-MDT存在1分钟以上时才切回default-MDT.

下面举例说明:

clip_p_w_picpath004

在没有DATA-MDT之前,流量通过 default-mdt发送(1.1.1.1 239.1.1.1 192.168.0.100 224.200.200.200),当流量超过threshold,PE1 发送 192.168.0.100 224.200.200.200 239.100.100.100给所有PE。

PE2因为下面有receiver,所以它发P-JOIN给PE1,PE1在几秒钟后,通过1.1.1.1 239.100.100.100 192.168.0.100 224.200.200.200,发给PE2。

PE3没有reveiver,所以它只保存S,G,DATA-MDT信息,而不发P-join,所以它收到不PE1关于224.200.200.200的流量。

M×××RPF检测

与正常的RPF测试有所不同,它检测收到的的M×××报文中的C-source,到达这个C-source的下一跳是否是MBGP的更新源。

如上图: PE2 收到的M×××报文包是 1.1.1.1(P-source) 239.100.100.100(P-group) 192.168.0.100(C-source) 224.200.200.200 (C-group)

PE2会检测到192.168.0.100的MBGP的下一跳是否是1.1.1.1,是就通过。

补充:在使用default-mdt或data-mdt时, MDT群组信息是通过BGP扩展社区属性携带的。

比如使用default-mdt里如果组设置成239.1.1.1, PE通过MBGP把 0x0009 AS# MDT群组发给其它PE

10:239.1.1.1 10是AS, 0x0009是类型编码

 

m×××新状态标志:

Z 组播隧道 出现在全局组播表中,表示在组播隧道入口上接收或传输组播分组

Y 已加入的MDT-data群组 出现在mvrf的组播入口中。 表示该PE从一个源PE接收了一个data-mdt加入信息并且已经向它发出了P-join

y 正向MDT-data群组发送 已经在使用新的DATA-MDT

 

实验:

clip_p_w_picpath006

说明:

1.r1,r3,r7,r5 除与R2,R4,R6的接口外, 其它的接口包括lo0,运行ospf, mpls

r1 与 r5, r1 与 r7 IBGP (r1 起RR,为了让R4,R6可以互相学到。也可以全互联IBGP)

r1 r5 r7 起VRF,如果与CE之间不运行动态协议,bgp add ipv vrf 中重分布直联和静态。静态的写法 如在R1 ip route vrf 12 2.2.2.2 255.255.255.255 s0/0 192.1.12.2

2.r3做为isp的RP,r1,r3,r5,r7都运行组播,

3.r2 loopback0做客户RP.

测试1: R1,R5,R7 运行default-mdt

配置如下:

以R1为例

ip vrf 1

mdt default 239.1.1.1

ip multicast-routing vrf 1

interface Serial0/0

ip vrf forwarding 1

ip address 192.1.12.1 255.255.255.0

ip pim sparse-mode

会自动创建 tunnel 0

R1#sho int tun0

Tunnel0 is up, line protocol is up

Hardware is Tunnel

Interface is unnumbered. Using address of Loopback0 (1.1.1.1)

MTU 1514 bytes, BW 9 Kbit, DLY 500000 usec,

reliability 255/255, txload 1/255, rxload 1/255

Encapsulation TUNNEL, loopback not set

Keepalive not set

Tunnel source 1.1.1.1 (Loopback0), destination 239.1.1.1

Tunnel protocol/transport GRE/IP Multicast

Key disabled, sequencing disabled

Checksumming of packets disabled

Tunnel TTL 255

Fast tunneling enabled

Tunnel transmit bandwidth 8000 (kbps)

Tunnel receive bandwidth 8000 (kbps)

Last input 00:00:10, output 00:00:04, output hang never

Last clearing of "show interface" counters never

Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0

Queueing strategy: fifo

Output queue: 0/0 (size/max)

5 minute input rate 0 bits/sec, 0 packets/sec

5 minute output rate 0 bits/sec, 0 packets/sec

69 packets input, 5226 bytes, 0 no buffer

Received 0 broadcasts, 0 runts, 0 giants, 0 throttles

0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort

65 packets output, 4658 bytes, 0 underruns

0 output errors, 0 collisions, 0 interface resets

0 output buffer failures, 0 output buffers swapped out

现在让R4的lo0作为receiver 加入224.100.100.100

R2 做为源PING 224.100.100.100

结果:

R5#sho ip mroute

IP Multicast Routing Table

Flags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C - Connected,

L - Local, P - Pruned, R - RP-bit set, F - Register flag,

T - SPT-bit set, J - Join SPT, M - MSDP created entry,

X - Proxy Join Timer Running, A - Candidate for MSDP Advertisement,

U - URD, I - Received Source Specific Host Report,

Z - Multicast Tunnel, z - MDT-data group sender,

Y - Joined MDT-data group, y - Sending to MDT-data group

Outgoing interface flags: H - Hardware switched, A - Assert winner

Timers: Uptime/Expires

Interface state: Interface, Next-Hop or VCD, State/Mode

(*, 239.1.1.1), 00:20:21/stopped, RP 3.3.3.3, flags: SJCFZ

Incoming interface: Serial0/0, RPF nbr 192.1.35.3

Outgoing interface list:

MVRF 5, Forward/Sparse, 00:20:21/00:00:40

(1.1.1.1, 239.1.1.1), 00:20:20/00:02:55, flags: JTZ

Incoming interface: Serial0/0, RPF nbr 192.1.35.3

Outgoing interface list:

MVRF 5, Forward/Sparse, 00:20:20/00:00:41

P-SOURCE 1.1.1.1 到P-GROUP 来自s0/0,出口在VRF中这里看不到见下。

(5.5.5.5, 239.1.1.1), 00:20:21/00:03:25, flags: FT

Incoming interface: Loopback0, RPF nbr 0.0.0.0

Outgoing interface list:

Serial0/0, Forward/Sparse, 00:20:21/00:02:50

(7.7.7.7, 239.1.1.1), 00:20:03/00:02:45, flags: JTZ

Incoming interface: Serial0/0, RPF nbr 192.1.35.3

Outgoing interface list:

MVRF 5, Forward/Sparse, 00:20:03/00:00:58

R5#

R5#

R5#

R5#

R5#sho ip mroute vrf 5

IP Multicast Routing Table

Flags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C - Connected,

L - Local, P - Pruned, R - RP-bit set, F - Register flag,

T - SPT-bit set, J - Join SPT, M - MSDP created entry,

X - Proxy Join Timer Running, A - Candidate for MSDP Advertisement,

U - URD, I - Received Source Specific Host Report,

Z - Multicast Tunnel, z - MDT-data group sender,

Y - Joined MDT-data group, y - Sending to MDT-data group

Outgoing interface flags: H - Hardware switched, A - Assert winner

Timers: Uptime/Expires

Interface state: Interface, Next-Hop or VCD, State/Mode

(*, 224.100.100.100), 00:03:39/00:02:47, RP 2.2.2.2, flags: S

Incoming interface: Tunnel0, RPF nbr 1.1.1.1

Outgoing interface list:

Serial0/3, Forward/Sparse, 00:03:39/00:02:47

(2.2.2.2, 224.100.100.100), 00:01:36/00:03:28, flags: T

Incoming interface: Tunnel0, RPF nbr 1.1.1.1

Outgoing interface list:

Serial0/3, Forward/Sparse, 00:01:36/00:02:51

(192.1.12.2, 224.100.100.100), 00:01:36/00:03:28, flags: T

Incoming interface: Tunnel0, RPF nbr 1.1.1.1

Outgoing interface list:

Serial0/3, Forward/Sparse, 00:01:36/00:02:51

C-SOURCE, C-GROUP 出口是 s0/3

现在R4能收到组播流。

R7#sho ip mroute

IP Multicast Routing Table

Flags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C - Connected,

L - Local, P - Pruned, R - RP-bit set, F - Register flag,

T - SPT-bit set, J - Join SPT, M - MSDP created entry,

X - Proxy Join Timer Running, A - Candidate for MSDP Advertisement,

U - URD, I - Received Source Specific Host Report,

Z - Multicast Tunnel, z - MDT-data group sender,

Y - Joined MDT-data group, y - Sending to MDT-data group

Outgoing interface flags: H - Hardware switched, A - Assert winner

Timers: Uptime/Expires

Interface state: Interface, Next-Hop or VCD, State/Mode

(*, 239.1.1.1), 00:21:16/stopped, RP 3.3.3.3, flags: SJCFZ

Incoming interface: Serial0/2, RPF nbr 192.1.37.3

Outgoing interface list:

MVRF 7, Forward/Sparse, 00:21:16/00:02:47

(1.1.1.1, 239.1.1.1), 00:20:45/00:02:50, flags: JTZ

Incoming interface: Serial0/2, RPF nbr 192.1.37.3

Outgoing interface list:

MVRF 7, Forward/Sparse, 00:20:45/00:00:18

R7这个PE也收到P-SOURCE, P-GROUP流量就算他没有接收者。

(5.5.5.5, 239.1.1.1), 00:21:15/00:02:40, flags: JTZ

Incoming interface: Serial0/2, RPF nbr 192.1.37.3

Outgoing interface list:

MVRF 7, Forward/Sparse, 00:21:15/00:02:48

(7.7.7.7, 239.1.1.1), 00:21:16/00:03:08, flags: FT

Incoming interface: Loopback0, RPF nbr 0.0.0.0

Outgoing interface list:

Serial0/2, Forward/Sparse, 00:21:16/00:02:55

(*, 224.0.1.40), 00:34:53/00:02:35, RP 0.0.0.0, flags: DCL

Incoming interface: Null, RPF nbr 0.0.0.0

Outgoing interface list:

Loopback0, Forward/Sparse, 00:34:53/00:02:35

测试2, 改成DATA-MDT模式。

在R1,R5,R7配置如下:

以R1为例。

ip vrf 1

rd 1:1

route-target export 100:100

route-target import 100:100

mdt default 239.1.1.1

mdt data 239.1.1.128 0.0.0.7 threshold 1

结果:

R5#sho ip mroute

IP Multicast Routing Table

Flags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C - Connected,

L - Local, P - Pruned, R - RP-bit set, F - Register flag,

T - SPT-bit set, J - Join SPT, M - MSDP created entry,

X - Proxy Join Timer Running, A - Candidate for MSDP Advertisement,

U - URD, I - Received Source Specific Host Report,

Z - Multicast Tunnel, z - MDT-data group sender,

Y - Joined MDT-data group, y - Sending to MDT-data group

Outgoing interface flags: H - Hardware switched, A - Assert winner

Timers: Uptime/Expires

Interface state: Interface, Next-Hop or VCD, State/Mode

(*, 239.1.1.129), 00:04:39/stopped, RP 3.3.3.3, flags: SJCZ

Incoming interface: Serial0/0, RPF nbr 192.1.35.3

Outgoing interface list:

MVRF 5, Forward/Sparse, 00:04:39/00:01:21

(1.1.1.1, 239.1.1.129), 00:03:33/00:02:51, flags: JTZ

Incoming interface: Serial0/0, RPF nbr 192.1.35.3

Outgoing interface list:

MVRF 5, Forward/Sparse, 00:03:33/00:02:27

R5下面有接收者所以全局已有DATA的组播流

(*, 239.1.1.128), 00:04:39/stopped, RP 3.3.3.3, flags: SJCZ

Incoming interface: Serial0/0, RPF nbr 192.1.35.3

Outgoing interface list:

MVRF 5, Forward/Sparse, 00:04:39/00:01:21

(1.1.1.1, 239.1.1.128), 00:04:33/00:02:50, flags: JTZ

Incoming interface: Serial0/0, RPF nbr 192.1.35.3

Outgoing interface list:

MVRF 5, Forward/Sparse, 00:04:33/00:01:27

R5下面有接收者所以全局已有DATA的组播流

(*, 239.1.1.1), 00:04:40/stopped, RP 3.3.3.3, flags: SJCFZ

Incoming interface: Serial0/0, RPF nbr 192.1.35.3

Outgoing interface list:

MVRF 5, Forward/Sparse, 00:04:40/00:01:20

(1.1.1.1, 239.1.1.1), 00:04:40/00:02:40, flags: JTZ

Incoming interface: Serial0/0, RPF nbr 192.1.35.3

Outgoing interface list:

MVRF 5, Forward/Sparse, 00:04:40/00:01:20

(5.5.5.5, 239.1.1.1), 00:04:40/00:03:10, flags: FT

Incoming interface: Loopback0, RPF nbr 0.0.0.0

Outgoing interface list:

Serial0/0, Forward/Sparse, 00:04:09/00:03:14

(7.7.7.7, 239.1.1.1), 00:03:49/00:02:40, flags: JTZ

Incoming interface: Serial0/0, RPF nbr 192.1.35.3

Outgoing interface list:

MVRF 5, Forward/Sparse, 00:03:49/00:02:10

(*, 224.0.1.40), 00:04:40/stopped, RP 0.0.0.0, flags: DCL

Incoming interface: Null, RPF nbr 0.0.0.0

Outgoing interface list:

Serial0/0, Forward/Sparse, 00:04:40/00:00:00

R5#sho ip mroute vrf 5

IP Multicast Routing Table

Flags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C - Connected,

L - Local, P - Pruned, R - RP-bit set, F - Register flag,

T - SPT-bit set, J - Join SPT, M - MSDP created entry,

X - Proxy Join Timer Running, A - Candidate for MSDP Advertisement,

U - URD, I - Received Source Specific Host Report,

Z - Multicast Tunnel, z - MDT-data group sender,

Y - Joined MDT-data group, y - Sending to MDT-data group

Outgoing interface flags: H - Hardware switched, A - Assert winner

Timers: Uptime/Expires

Interface state: Interface, Next-Hop or VCD, State/Mode

(*, 224.100.100.100), 00:04:41/00:03:29, RP 2.2.2.2, flags: S

Incoming interface: Tunnel0, RPF nbr 1.1.1.1

Outgoing interface list:

Serial0/3, Forward/Sparse, 00:03:55/00:03:29

(2.2.2.2, 224.100.100.100), 00:03:54/00:03:28, flags: TY

Incoming interface: Tunnel0, RPF nbr 1.1.1.1, MDT:239.1.1.129/00:02:14

Outgoing interface list:

Serial0/3, Forward/Sparse, 00:03:54/00:03:29

(192.1.12.2, 224.100.100.100), 00:03:58/00:03:28, flags: TY

Incoming interface: Tunnel0, RPF nbr 1.1.1.1, MDT:239.1.1.128/00:02:14

Outgoing interface list:

Serial0/3, Forward/Sparse, 00:03:58/00:03:29

(*, 224.0.1.40), 00:04:43/stopped, RP 0.0.0.0, flags: DCL

Incoming interface: Null, RPF nbr 0.0.0.0

Outgoing interface list:

Serial0/3, Forward/Sparse, 00:04:43/00:00:00

Y 已加入的MDT-data群组

R7#sho ip mrou

R7#sho ip mroute

IP Multicast Routing Table

Flags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C - Connected,

L - Local, P - Pruned, R - RP-bit set, F - Register flag,

T - SPT-bit set, J - Join SPT, M - MSDP created entry,

X - Proxy Join Timer Running, A - Candidate for MSDP Advertisement,

U - URD, I - Received Source Specific Host Report,

Z - Multicast Tunnel, z - MDT-data group sender,

Y - Joined MDT-data group, y - Sending to MDT-data group

Outgoing interface flags: H - Hardware switched, A - Assert winner

Timers: Uptime/Expires

Interface state: Interface, Next-Hop or VCD, State/Mode

(*, 239.1.1.1), 00:05:06/stopped, RP 3.3.3.3, flags: SJCFZ

Incoming interface: Serial0/2, RPF nbr 192.1.37.3

Outgoing interface list:

MVRF 7, Forward/Sparse, 00:05:06/00:00:53

(1.1.1.1, 239.1.1.1), 00:05:06/00:02:50, flags: JTZ

Incoming interface: Serial0/2, RPF nbr 192.1.37.3

Outgoing interface list:

MVRF 7, Forward/Sparse, 00:05:06/00:00:54

(5.5.5.5, 239.1.1.1), 00:04:30/00:02:50, flags: JTZ

Incoming interface: Serial0/2, RPF nbr 192.1.37.3

Outgoing interface list:

MVRF 7, Forward/Sparse, 00:04:30/00:01:30

(7.7.7.7, 239.1.1.1), 00:04:56/00:03:10, flags: FT

Incoming interface: Loopback0, RPF nbr 0.0.0.0

Outgoing interface list:

Serial0/2, Forward/Sparse, 00:04:28/00:02:57

R7上没有接收者所以没有DATA的组流量,只有DEFAULT-MDT流量(用来传协议)

R7#sho ip mroute vrf 7

IP Multicast Routing Table

Flags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C - Connected,

L - Local, P - Pruned, R - RP-bit set, F - Register flag,

T - SPT-bit set, J - Join SPT, M - MSDP created entry,

X - Proxy Join Timer Running, A - Candidate for MSDP Advertisement,

U - URD, I - Received Source Specific Host Report,

Z - Multicast Tunnel, z - MDT-data group sender,

Y - Joined MDT-data group, y - Sending to MDT-data group

Outgoing interface flags: H - Hardware switched, A - Assert winner

Timers: Uptime/Expires

Interface state: Interface, Next-Hop or VCD, State/Mode

(*, 224.100.100.100), 00:11:32/stopped, RP 2.2.2.2, flags: SP

Incoming interface: Tunnel0, RPF nbr 1.1.1.1

Outgoing interface list: Null

(2.2.2.2, 224.100.100.100), 00:10:47/00:02:16, flags: P

Incoming interface: Tunnel0, RPF nbr 1.1.1.1, MDT:239.1.1.128/00:02:18

Outgoing interface list: Null

(192.1.12.2, 224.100.100.100), 00:10:47/00:02:15, flags: P

Incoming interface: Tunnel0, RPF nbr 1.1.1.1, MDT:239.1.1.129/00:02:18

Outgoing interface list: Null

(*, 224.0.1.40), 00:11:34/00:02:20, RP 0.0.0.0, flags: DCL

Incoming interface: Null, RPF nbr 0.0.0.0

Outgoing interface list:

Serial0/3, Forward/Sparse, 00:11:34/00:00:25

Tunnel0, Forward/Sparse, 00:03:42/00:02:20

R7上没大Y标志

R1#sho ip mroute vrf 1

IP Multicast Routing Table

Flags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C - Connected,

L - Local, P - Pruned, R - RP-bit set, F - Register flag,

T - SPT-bit set, J - Join SPT, M - MSDP created entry,

X - Proxy Join Timer Running, A - Candidate for MSDP Advertisement,

U - URD, I - Received Source Specific Host Report,

Z - Multicast Tunnel, z - MDT-data group sender,

Y - Joined MDT-data group, y - Sending to MDT-data group

Outgoing interface flags: H - Hardware switched, A - Assert winner

Timers: Uptime/Expires

Interface state: Interface, Next-Hop or VCD, State/Mode

(*, 224.100.100.100), 00:06:21/00:02:49, RP 2.2.2.2, flags: SF

Incoming interface: Serial0/0, RPF nbr 192.1.12.2

Outgoing interface list:

Tunnel0, Forward/Sparse, 00:05:51/00:02:49

(2.2.2.2, 224.100.100.100), 00:04:41/00:03:28, flags: Ty

Incoming interface: Serial0/0, RPF nbr 192.1.12.2

Outgoing interface list:

Tunnel0, Forward/Sparse, 00:04:49/00:02:49

(192.1.12.2, 224.100.100.100), 00:05:41/00:03:28, flags: FTy

Incoming interface: Serial0/0, RPF nbr 0.0.0.0

Outgoing interface list:

Tunnel0, Forward/Sparse, 00:05:52/00:02:49

(*, 224.0.1.40), 00:06:22/stopped, RP 0.0.0.0, flags: DCL

Incoming interface: Null, RPF nbr 0.0.0.0

Outgoing interface list:

Serial0/0, Forward/Sparse, 00:06:22/00:02:38

R1上小y标志,表示正向DATA发送组播数据。