From: Mujica, Raul - (Per) (raul.mujica@telmex.com)
Date: Wed May 05 2004 - 11:19:08 GMT-3
Richar,
On R2, I have multiacces interfaces.
I have also tried with sparse mode and nbma mode, but the same behavior, the
traffic flows during a period of time.
Raul
-----Mensaje original-----
De: Richard Dumoulin [mailto:richard.dumoulin@vanco.es]
Enviado el: Miircoles, 05 de Mayo de 2004 08:50 a.m.
Para: Mujica, Raul - (Per); 'ccielab@groupstudy.com'
Asunto: RE: X - Proxy Join Timer Running - Multicast Flag
On R2 do you have only one multiaccess interface or two subinterfaces ? If
only one multiaccess interface do you have sparse mode with nbma mode
configured ?
--Richard
-----Original Message-----
From: Mujica, Raul - (Per) [mailto:raul.mujica@telmex.com
<mailto:raul.mujica@telmex.com> ]
Sent: miircoles, 05 de mayo de 2004 0:51
To: 'ccielab@groupstudy.com'
Subject: X - Proxy Join Timer Running - Multicast Flag
Group:
I have been searching without success in the group archive and in the cisco
web-site an example or explanation for the flag X - Proxy Join Timer
Running.
This is because in the following scenario with three routers: R2 (hub), R5
and R6 (spoken) with a source in (R5) and a group member in the LAN
interface of (R6), the multicast traffic just flows for a period of time and
then it4s pruned (I4m using mrm to generate traffic but I don4t stop it to
justify the prunning). I think the flag X could be the problem.
****************************************************************************
*******
Traffic flow is OK
R2#sh ip mroute 238.1.1.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
Outgoing interface flags: H - Hardware switched
Timers: Uptime/Expires
Interface state: Interface, Next-Hop or VCD, State/Mode
(*, 238.1.1.1), 00:28:43/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-Dense, 00:21:11/00:02:44
(200.0.0.5, 238.1.1.1), 00:21:11/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-Dense, 00:01:44/00:01:45
****************************************************************************
****
R5
Mar 2 00:28:38.032: PIM: Send v2 Data-header Register to 200.0.0.2 for
200.0.0.5, group 238.1.1.1
Mar 2 00:28:38.036: PIM: Received v2 Register-Stop on Serial0/0 from
200.0.0.2
Mar 2 00:28:38.040: PIM: for source 200.0.0.5, group 238.1.1.1
Mar 2 00:28:38.040: PIM: Clear register flag to 200.0.0.2 for
(200.0.0.5/32, 238.1.1.1)
Mar 2 00:29:02.244: PIM: Received v2 Join/Prune on Serial0/0 from
150.50.100.2, to us
Mar 2 00:29:02.244: PIM: Join-list: (200.0.0.5/32, 238.1.1.1), S-bit set
Mar 2 00:29:02.244: PIM: Add Serial0/0/150.50.100.2 to (200.0.0.5/32,
238.1.1.1), Forward state
Mar 2 00:29:23.056: PIM: Building Join/Prune message for 238.1.1.1
Mar 2 00:29:23.056: PIM: No sources in join or prune list
Mar 2 00:29:34.284: PIM: Received v2 Join/Prune on Serial0/0 from
150.50.100.2, to us
Mar 2 00:29:34.284: PIM: Prune-list: (200.0.0.5/32, 238.1.1.1)
Mar 2 00:29:34.284: PIM: Schedule to prune Serial0/0 for (200.0.0.5/32,
238.1.1.1)
Mar 2 00:29:39.056: PIM: Prune Serial0/0/224.0.0.2 from (200.0.0.5/32,
238.1.1.1) - deleted
Mar 2 00:30:22.084: PIM: Building Join/Prune message for 238.1.1.1
Mar 2 00:30:22.084: PIM: No sources in join or prune list
Mar 2 00:30:31.716: PIM: Received v2 Join/Prune on Serial0/0 from
150.50.100.6, not to us
Mar 2 00:30:31.716: PIM: Prune-list: (*, 238.1.1.1) RP 200.0.0.2
Mar 2 00:30:38.084: PIM: Send v2 Data-header Register to 200.0.0.2 for
200.0.0.5, group 238.1.1.1
Mar 2 00:30:38.088: PIM: Received v2 Register-Stop on Serial0/0 from
200.0.0.2
Mar 2 00:30:38.088: PIM: for source 200.0.0.5, group 238.1.1.1
****************************************************************************
****
R2
Mar 2 00:28:38.033: PIM: Received v2 Register on Serial0/0.256 from
150.50.100.5
Mar 2 00:28:38.037: (Data-header) for 200.0.0.5, group 238.1.1.1
Mar 2 00:28:38.037: PIM: Send v2 Register-Stop to 150.50.100.5 for
200.0.0.5, group 238.1.1.1
Mar 2 00:29:02.241: PIM: Building Join/Prune message for 238.1.1.1
Mar 2 00:29:02.241: PIM: For 150.50.100.5, Join-list: 200.0.0.5/32
Mar 2 00:29:02.241: PIM: Send v2 periodic Join/Prune to 150.50.100.5
(Serial0/0.256)
Mar 2 00:29:02.613: PIM: Received v2 Join/Prune on Serial0/0.256 from
150.50.100.6, to us
Mar 2 00:29:02.613: PIM: Join-list: (*, 238.1.1.1) RP 200.0.0.2, RPT-bit
set, WC-bit set, S-bit set
Mar 2 00:29:02.613: PIM: Add Serial0/0.256/150.50.100.6 to (*, 238.1.1.1),
Forward state
Mar 2 00:29:02.617: PIM: Prune-list: (200.0.0.5/32, 238.1.1.1) RPT-bit set
Mar 2 00:29:07.241: PIM: Send RP-reachability for 238.1.1.1 on
Serial0/0.256
Mar 2 00:29:34.282: PIM: Prune Serial0/0.256/150.50.100.6 from
(200.0.0.5/32, 238.1.1.1) - deleted
Mar 2 00:29:34.282: 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 00:29:34.290: PIM: Received v2 Join/Prune on Serial0/0.256 from
150.50.100.2, not to us
Mar 2 00:30:01.715: PIM: Received v2 Join/Prune on Serial0/0.256 from
150.50.100.6, to us
Mar 2 00:30:01.715: PIM: Join-list: (*, 238.1.1.1) RP 200.0.0.2, RPT-bit
set, WC-bit set, S-bit set
Mar 2 00:30:01.715: PIM: Add Serial0/0.256/150.50.100.6 to (*, 238.1.1.1),
Forward state
Mar 2 00:30:01.719: PIM: Prune-list: (200.0.0.5/32, 238.1.1.1) RPT-bit set
****************************************************************************
****
Traffic Stops
R2#
R2#sh ip mroute 238.1.1.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
Outgoing interface flags: H - Hardware switched
Timers: Uptime/Expires
Interface state: Interface, Next-Hop or VCD, State/Mode
(*, 238.1.1.1), 00:31:01/00:03:25, 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-Dense, 00:23:29/00:03:25
(200.0.0.5, 238.1.1.1), 00:23:29/00:02:32, flags: PT
Incoming interface: Serial0/0.256, RPF nbr 150.50.100.5
Outgoing interface list: Null
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-dense-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
R5
interface Loopback0
ip address 200.0.0.5 255.255.255.255
ip pim sparse-mode
ip mrm test-sender
interface Serial0/0
ip address 150.50.100.5 255.255.255.224
ip pim sparse-dense-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
R6
interface Serial0/0
ip address 150.50.100.6 255.255.255.224
ip pim sparse-dense-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
interface FastEthernet0/0
ip address 150.50.7.6 255.255.255.128
ip pim sparse-mode
duplex auto
speed auto
Source
interface FastEthernet0/0
ip address 150.50.7.7 255.255.255.128
ip pim sparse-mode
ip mrm test-receiver
MRM manager
ip mrm manager hola1
manager Loopback0 group 238.1.1.1
senders 3
receivers 1 sender-list 3
!
access-list 1 permit 150.50.7.7
access-list 3 permit 200.0.0.5
Thank for your help
Razl Mujica Esquivel
Direccisn de Ingenierma
TELMEX - Perz
Telifono (51 1 ) 610 2579
Fax: (51 1 ) 610 2594
Email: raul.mujica@telmex.com
"Este mensaje y sus anexos pueden contener informacisn confidencial. Si
usted no es el destinatario de este mensaje (o la persona responsable de
entregar al destinatario este mensaje), se le notifica que cualquier
revisisn, divulgacisn, retransmisisn, distribucisn, copiado u otro uso o
acto realizado con base en o relacionado con el contenido de este mensaje y
sus anexos, estan prohibidos. Si usted ha recibido este mensaje y sus anexos
por error, le suplicamos lo notifique al remitente respondiendo el presente
correo electrsnico y borre el presente y sus anexos de su sistema sin
conservar copia de los mismos. Muchas gracias."
"This message and any attachments to it are being sent by a law firm and may
contain information which is confidential. If your are not the intended
recipient(s) for this message (or the employee or agent responsible for the
delivery of this message to the intended recipient(s)), you are on notice
that any review, disclosure, retransmission, dissemination, distribution,
copying or other use or taking any action based upon or relative to the
information contained in this message and its attachments, is prohibited. If
you are not the intended recipient(s) of this message or its attachments,
please immediately advise the sender by reply e-mail and delete this message
and its attachments from your system without keeping a copy. Thank you."
This archive was generated by hypermail 2.1.4 : Wed Jun 02 2004 - 11:12:05 GMT-3