From: Chris Atkins (chris_atkins@blueyonder.co.uk)
Date: Thu Dec 15 2005 - 13:08:05 GMT-3
Still no joy, fault is now full time.
Debug on R3
*Mar 6 00:49:49.182: IP(0): s=172.16.4.4 (Serial0/0.1) d=225.5.5.5
(Serial0/0.3) id=6571, prot=1, len=36(36), mforward
*Mar 6 00:49:51.182: IP(0): s=172.16.4.4 (Serial0/0.1) d=225.5.5.5
(Serial0/0.3) id=6572, prot=1, len=36(36), mforward
*Mar 6 00:49:53.182: IP(0): s=172.16.4.4 (Serial0/0.1) d=225.5.5.5
(Serial0/0.3) id=6573, prot=1, len=36(36), mforward
However nothing received on R1.
Lab_R3#sh ip mroute 225.5.5.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
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
(*, 225.5.5.5), 00:44:56/00:03:10, RP 172.16.1.1, flags: SJCLF
Incoming interface: Serial0/0.3, RPF nbr 172.16.123.1
Outgoing interface list:
Serial0/0.1, Forward/Sparse, 00:18:12/00:03:10
Loopback0, Forward/Sparse, 00:44:56/00:02:33
(172.16.4.4, 225.5.5.5), 00:44:51/00:03:28, flags: LT
Incoming interface: Serial0/0.1, RPF nbr 172.16.34.4
Outgoing interface list:
Serial0/0.3, Forward/Sparse, 00:04:17/00:03:02
Loopback0, Forward/Sparse, 00:44:52/00:02:32
################################################################
Lab_R1#debug ip mpacket
IP multicast packets debugging is on
Lab_R1#
Lab_R1#
Lab_R1#
Lab_R1#
Lab_R1#
Lab_R1#
Lab_R1#
Lab_R1#
Lab_R1#show 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
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
(*, 225.5.5.5), 00:06:38/00:03:24, RP 172.16.1.1, flags: SJCL
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
Loopback0, Forward/Sparse, 00:06:38/00:02:11
Serial0/1.1, 172.16.123.2, Forward/Sparse, 00:05:58/00:03:24
Serial0/1.1, 172.16.123.3, Forward/Sparse, 00:06:30/00:02:55
(172.16.4.4, 225.5.5.5), 00:06:28/00:02:59, flags: LT
Incoming interface: Serial0/1.1, RPF nbr 172.16.123.3
Outgoing interface list:
Loopback0, Forward/Sparse, 00:06:30/00:02:10
(*, 224.0.1.40), 00:06:40/00:02:53, RP 172.16.1.1, flags: SJCL
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
Loopback0, Forward/Sparse, 00:06:40/00:02:09
Serial0/1.1, 172.16.123.2, Forward/Sparse, 00:05:48/00:02:39
Serial0/1.1, 172.16.123.3, Forward/Sparse, 00:06:31/00:02:53
Lab_R1#
----- Original Message -----
From: "Vincent Mashburn" <vmashburn@fedex.com>
To: "Schulz, Dave" <DSchulz@dpsciences.com>; "Godswill Oletu "
<oletu@inbox.lv>; <nobody@groupstudy.com>; "Chris "
<chris_atkins@Blueyonder.co.uk>; <ccielab@groupstudy.com>
Sent: Thursday, December 15, 2005 2:27 PM
Subject: RE: Pim Issue
Are there any alternate routes from R4 to R2 that have a better metric
than going thru R1? I am wondering if sparse mode switching the traffic
to a shortest patch cutover after a specified amount of time has
anything to do with it. I am thinking that maybe a access-list has been
placed on one of the routers that block ping. This may not be taken
into affect upon startup, but when sparse mode switches over to dense
mode, the traffic may take a path thru the ping-blocked access list.
Just a thought.
Vince Mashburn
Engineer
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Schulz, Dave
Sent: Wednesday, December 14, 2005 8:33 PM
To: Godswill Oletu ; nobody@groupstudy.com; Chris ;
ccielab@groupstudy.com
Subject: RE: Pim Issue
These are all great questions, Godswill. But I am wondering which ones
could
possibly cause the pings to start and then fail. Hmmmm.
Dave
-----Original Message-----
From: nobody@groupstudy.com
To: Chris; ccielab@groupstudy.com
Sent: 12/14/2005 8:34 PM
Subject: Re: Pim Issue
couple of questions:
1. which router joined the group 225.5.5.5?
2. Are you running Auto-RP or static RP?
3. If Auto-RP, which Router is your MA?
4 If static-RP, hope it is configured on all Routers?
4. If Auto-RP, did you enable nbma-mode on R1?
5. If Auto-RP, did youu enable Auto-RP listener?
Answer to these questions, will give one a better understanding of your
scenario.
HTH
Godswill Oletu
----- Original Message -----
From: "Chris" <chris_atkins@Blueyonder.co.uk>
To: <ccielab@groupstudy.com>
Sent: Wednesday, December 14, 2005 6:19 PM
Subject: Pim Issue
> R4----------------------R3
> |
> |
> |
> R1------------- R2
>
> Hi
> I hope someone can help me with this as pulling hair out.
>
> R1is hub and R2 and R3 are spokes NBMA multipoint.
>
> R4 to R3 is serial HDLC.
>
> Running pim sparse RP is R1.
>
> Can ping fine, however pings( multicast group 225.5.5.5) from R4 time
out
> aftrer approx 90 - 100 pings. A bit lost what going on (If restart
ping
> still
> fails.), any help most apprciated in advance.
>
> Cheers
>
> Chris
>
>
This archive was generated by hypermail 2.1.4 : Mon Jan 09 2006 - 07:07:51 GMT-3