From: Mujica, Raul - (Per) (raul.mujica@telmex.com)
Date: Wed May 05 2004 - 15:18:26 GMT-3
It was a typo, sorry, on R64s LAN there is a group member.
I will explain again:
Scenario: R2 (hub), R5 and R6 (spokens). The source is (loopback - R5) and
the group member is (LAN - R7) directly connected to R64s LAN. I'm using MRM
manager as multicast generator.
Problem: Multicast traffic only flows for 210 seconds and then it's stopped.
But it starts again after 210 seconds.
Clues:
1.- R2 is also the RP for this group.
2.- R7 always sends the report for 238.1.1.
3.- R6 always receives the report message from R7 and sends the periodic
join-prune message to R2
4.- R6 and R7 never send any leave or prune message.
5.- I also have X flag set for this group on R2 when the traffic flow
R2#sh ip mroute 238.1.1.1
(*, 238.1.1.1), 00:28:55/00:03:22, RP 200.0.0.2, flags: S
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
Serial0/0.256, 150.50.100.6, Forward/Sparse, 00:28:54/00:03:22
(200.0.0.5, 238.1.1.1), 00:28:55/00:03:29, flags: TX
Incoming interface: Serial0/0.256, RPF nbr 150.50.100.5
Outgoing interface list:
Serial0/0.256, 150.50.100.6, Forward/Sparse, 00:01:06/00:02:23
6.- R2 prunes the traffic after 210 seconds (expiration timer), in spite of
receiving the periodic join-prune messages from R6 and forwarding mpacket.
Mar 2 18:26:53.033: PIM: Add Serial0/0.256/150.50.100.6 to (*, 238.1.1.1),
Forward state
Mar 2 18:26:53.037: PIM: Add Serial0/0.256/150.50.100.6 to (200.0.0.5/32,
238.1.1.1)
Mar 2 18:30:23.837: PIM: Prune Serial0/0.256/150.50.100.6 from
(200.0.0.5/32, 238.1.1.1) - deleted
Mar 2 18:30:23.837: PIM: Send v2 Prune on Serial0/0.256 to 150.50.100.5 for
(200.0.0.5/32, 238.1.1.1), S-bit
Mar 2 18:33:50.666: PIM: Add Serial0/0.256/150.50.100.6 to (*, 238.1.1.1),
Forward state
Mar 2 18:33:50.670: PIM: Add Serial0/0.256/150.50.100.6 to (200.0.0.5/32,
238.1.1.1)
7.- The expiration time is over on R2 and the multicast traffic is stopped.
R2#sh ip mroute 238.1.1.1
(*, 238.1.1.1), 00:31:17/00:02:59, RP 200.0.0.2, flags: S
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
Serial0/0.256, 150.50.100.6, Forward/Sparse, 00:31:16/00:02:59
(200.0.0.5, 238.1.1.1), 00:31:17/00:03:29, flags: T
Incoming interface: Serial0/0.256, RPF nbr 150.50.100.5
Outgoing interface list:
Serial0/0.256, 150.50.100.6, Forward/Sparse, 00:03:28/00:00:01
Mar 2 20:16:35.000: MRT: Delete Serial0/0.256/150.50.100.6 from the olist
of (200.0.0.5, 238.1.1.1)
R2#sh ip mroute 238.1.1.1
(*, 238.1.1.1), 00:31:24/00:02:59, RP 200.0.0.2, flags: S
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
Serial0/0.256, 150.50.100.6, Forward/Sparse, 00:31:23/00:02:52
(200.0.0.5, 238.1.1.1), 00:31:24/00:02:59, flags: PT
Incoming interface: Serial0/0.256, RPF nbr 150.50.100.5
Outgoing interface list: Null
6.- There are periodic change in the OIL for the group 238.1.1.1 on R2 each
210 seconds
Mar 2 19:59:09.054: MRT: Add/Update Serial0/0.256/150.50.100.6 to the olist
of (200.0.0.5, 238.1.1.1), Forward state
Mar 2 20:02:39.422: MRT: Delete Serial0/0.256/150.50.100.6 from the olist
of (200.0.0.5, 238.1.1.1)
Mar 2 20:06:06.986: MRT: Add/Update Serial0/0.256/150.50.100.6 to the olist
of (200.0.0.5, 238.1.1.1), Forward state
7.- R5 receives a prune message from R2 and prunes the traffic.
Mar 2 18:30:23.840: PIM: Received v2 Join/Prune on Serial0/0 from
150.50.100.2, to us
Mar 2 18:30:23.840: PIM: Prune-list: (200.0.0.5/32, 238.1.1.1)
Mar 2 18:30:23.840: PIM: Schedule to prune Serial0/0 for (200.0.0.5/32,
238.1.1.1)
Questions:
1.- What is purpose of flag X - Proxy Join Timer Running ? I have been
searching without success on the group archive and on the cisco web-site.
2.- why the the expiration timer expired if the mpackets are being forwarded
on R2?
Config.
R7
interface FastEthernet0/0
ip address 150.50.7.7 255.255.255.128
ip mrm test-receiver
R6
interface FastEthernet0/0
ip address 150.50.7.6 255.255.255.128
ip pim sparse-mode
duplex auto
speed auto
!
interface Serial0/0
ip address 150.50.100.6 255.255.255.224
ip pim sparse-mode
encapsulation frame-relay
ip ospf priority 0
no arp frame-relay
frame-relay map ip 150.50.100.2 601 broadcast
frame-relay map ip 150.50.100.5 601
frame-relay map ip 150.50.100.6 601
frame-relay interface-dlci 601
no frame-relay inverse-arp
frame-relay lmi-type cisco
R2
interface Serial0/0.256 multipoint
ip address 150.50.100.2 255.255.255.224
ip pim dr-priority 100
ip pim nbma-mode
ip pim sparse-mode
frame-relay map ip 150.50.100.2 105
frame-relay map ip 150.50.100.5 105 broadcast
frame-relay map ip 150.50.100.6 106 broadcast
frame-relay interface-dlci 105
frame-relay interface-dlci 106
ip pim autorp listener
R5
interface Serial0/0
ip address 150.50.100.5 255.255.255.224
ip pim sparse-mode
encapsulation frame-relay
ip ospf priority 0
no arp frame-relay
frame-relay map ip 150.50.100.2 501 broadcast
frame-relay map ip 150.50.100.5 501
frame-relay map ip 150.50.100.6 501
frame-relay interface-dlci 501
no frame-relay inverse-arp
frame-relay lmi-type cisco
interface Loopback0
ip address 200.0.0.5 255.255.255.255
ip pim sparse-mode
ip mrm test-sender
Thanks
Razl
This archive was generated by hypermail 2.1.4 : Wed Jun 02 2004 - 11:12:05 GMT-3