From: gladston@br.ibm.com
Date: Thu Sep 30 2004 - 14:37:05 GMT-3
Why the F (register) flag? Debug shows that r1 is sending packets as native multicast, and has received stop register. But the flag F is still there. I have studied RP on Stick but it seems not to be the case. R1 is directed connected to the multicast source and connected to the RP (R2). R4 is connected directly to RP.
r1#sh ip mrou
(*, 224.0.1.40), 00:13:55/00:00:00, RP 172.16.2.1, flags: SJCL
Incoming interface: Serial0/0.12, RPF nbr 172.16.12.2
Outgoing interface list:
FastEthernet0/0.16, Forward/Dense, 00:13:55/00:00:00
(*, 239.1.1.1), 00:13:54/00:02:59, RP 172.16.2.1, flags: SPF
Incoming interface: Serial0/0.12, RPF nbr 172.16.12.2
Outgoing interface list: Null
(172.16.16.6, 239.1.1.1), 00:13:54/00:03:29, flags: FTA
Incoming interface: FastEthernet0/0.16, RPF nbr 0.0.0.0
Outgoing interface list:
Serial0/0.12, Forward/Sparse, 00:12:39/00:02:33
r1#
04:09:54: IP: s=172.16.16.6 (FastEthernet0/0.16) d=239.1.1.1 (Serial0/0.12) len
114, mforward ps
r1#
r1#
04:09:56: IP: s=172.16.16.6 (FastEthernet0/0.16) d=239.1.1.1 (Serial0/0.12) len
114, mforward ps
r1#
04:09:58: IP: s=172.16.16.6 (FastEthernet0/0.16) d=239.1.1.1 (Serial0/0.12) len
114, mforward ps
r1#
04:07:32: PIM: Send v2 Data-header Register to 172.16.2.1 for 172.16.16.6, group
239.1.1.1
04:07:32: PIM: Send v2 Null Register to 172.16.2.1
04:07:32: PIM: Received v2 Register-Stop on Serial0/0.12 from 172.16.2.1
04:07:32: PIM: for source 172.16.16.6, group 239.1.1.1
04:07:32: PIM: Clear register flag to 172.16.2.1 for (172.16.16.6/32, 239.1.1.1)
This archive was generated by hypermail 2.1.4 : Fri Oct 01 2004 - 15:00:51 GMT-3