From: gladston@br.ibm.com
Date: Tue Apr 20 2004 - 14:59:49 GMT-3
Any help to understand the following debug result and if it is the normal behavior?
The network is the one at http://www.cisco.com/en/US/tech/tk828/tk363/technologies_white_paper09186a00800d6b61.shtml#xtocid3
C and A joined group 228.1.1.1. A router connected to B's ethernet is sending traffic (ping) to the group. It is receiving answer from A but not from C. It does receive few answers from C, until B sends prune to A.
#sh deb
IP multicast:
PIM debugging is on
A#sh logg
Syslog logging: enabled (0 messages dropped, 1 messages rate-limited, 0 flushes, 0 overruns)
Console logging: disabled
Monitor logging: level debugging, 0 messages logged
Buffer logging: level debugging, 11959 messages logged
Logging Exception size (4096 bytes)
Trap logging: level informational, 37 message lines logged
Log Buffer (4096 bytes):
.125.2
*Mar 1 20:50:13.154: PIM: Received v2 Hello on Serial0/0 from 150.20.125.1
*Mar 1 20:50:22.946: PIM: Send RP-reachability for 228.1.1.1 on Serial0/0
*Mar 1 20:50:22.946: PIM: Send RP-reachability for 228.1.1.1 on Serial0/0
*Mar 1 20:50:26.946: PIM: Send v2 Hello on Loopback0
*Mar 1 20:50:26.946: PIM: Received v2 Hello on Loopback0 from 150.20.5.5
*Mar 1 20:50:30.946: PIM: Send v2 Hello on Serial0/0
*Mar 1 20:50:41.474: PIM: Received v2 Hello on Serial0/0 from 150.20.125.2
*Mar 1 20:50:41.474: PIM: Received v2 Hello on Serial0/0 from 150.20.125.2
*Mar 1 20:50:43.154: PIM: Received v2 Hello on Serial0/0 from 150.20.125.1
*Mar 1 20:50:47.454: PIM: Received v2 Join/Prune on Serial0/0 from 150.20.125.2, to us
*Mar 1 20:50:47.458: PIM: Prune-list: (150.20.5.5/32, 224.0.1.39)
*Mar 1 20:50:52.970: PIM: Building Join/Prune message for 228.1.1.1
*Mar 1 20:50:56.970: PIM: Send v2 Hello on Loopback0
*Mar 1 20:50:56.970: PIM: Received v2 Hello on Loopback0 from 150.20.5.5
*Mar 1 20:51:00.970: PIM: Send v2 Hello on Serial0/0
*Mar 1 20:51:11.474: PIM: Received v2 Join/Prune on Serial0/0 from 150.20.125.2, to us
*Mar 1 20:51:11.478: PIM: Join-list: (*, 228.1.1.1) RP 150.20.5.5, RPT-bit set, WC-bit set,
S-bit set
*Mar 1 20:51:11.478: PIM: Add Serial0/0/150.20.125.2 to (*, 228.1.1.1), Forward state
*Mar 1 20:51:11.490: PIM: Received v2 Hello on Serial0/0 from 150.20.125.2
*Mar 1 20:51:11.490: PIM: Received v2 Hello on Serial0/0 from 150.20.125.2
*Mar 1 20:51:13.226: PIM: Received v2 Hello on Serial0/0 from 150.20.125.1
*Mar 1 20:51:26.970: PIM: Send v2 Hello on Loopback0
*Mar 1 20:51:26.970: PIM: Received v2 Hello on Loopback0 from 150.20.5.5
*Mar 1 20:51:30.970: PIM: Send v2 Hello on Serial0/0
*Mar 1 20:51:41.618: PIM: Received v2 Hello on Serial0/0 from 150.20.125.2
*Mar 1 20:51:41.618: PIM: Received v2 Hello on Serial0/0 from 150.20.125.2
*Mar 1 20:51:43.198: PIM: Received v2 Hello on Serial0/0 from 150.20.125.1
*Mar 1 20:51:47.230: PIM: Received v2 Join/Prune on Serial0/0 from 150.20.125.1, to us
*Mar 1 20:51:47.230: PIM: Prune-list: (150.20.5.5/32, 224.0.1.39)
*Mar 1 20:51:47.934: PIM: Received v2 Register on Serial0/0 from 150.20.125.1
*Mar 1 20:51:47.934: for 150.20.13.3, group 228.1.1.1
*Mar 1 20:51:47.938: PIM: Send v2 Join on Serial0/0 to 150.20.125.1 for (150.20.13.3/32, 228
.1.1.1), S-bit
*Mar 1 20:51:47.942: PIM: Forward decapsulated data packet for 228.1.1.1 on Serial0/0
*Mar 1 20:51:47.942: PIM: Forward decapsulated data packet for 228.1.1.1 on Serial0/0
*Mar 1 20:51:47.966: PIM: Received v2 Join/Prune on Serial0/0 from 150.20.125.2, to us
*Mar 1 20:51:47.966: PIM: Prune-list: (150.20.13.3/32, 228.1.1.1) RPT-bit set
*Mar 1 20:51:48.230: PIM: Received v2 Register on Serial0/0 from 150.20.125.1
*Mar 1 20:51:48.230: PIM: Send v2 Register-Stop to 150.20.125.1 for 0.0.0.0, group 0.0.0.0
*Mar 1 20:51:49.938: PIM: Received v2 Register on Serial0/0 from 150.20.125.1
*Mar 1 20:51:49.938: for 150.20.13.3, group 228.1.1.1
*Mar 1 20:51:49.938: PIM: Send v2 Join on Serial0/0 to 150.20.125.1 for (150.20.13.3/32, 228
.1.1.1), S-bit
*Mar 1 20:51:49.938: PIM: Forward decapsulated data packet for 228.1.1.1 on Serial0/0
*Mar 1 20:51:49.942: PIM: Forward decapsulated data packet for 228.1.1.1 on Serial0/0
*Mar 1 20:51:51.942: PIM: Received v2 Register on Serial0/0 from 150.20.125.1
*Mar 1 20:51:51.942: for 150.20.13.3, group 228.1.1.1
*Mar 1 20:51:51.942: PIM: Send v2 Register-Stop to 150.20.125.1 for 150.20.13.3, group 228.1
.1.1
*Mar 1 20:51:52.994: PIM: Send RP-reachability for 228.1.1.1 on Serial0/0
*Mar 1 20:51:52.994: PIM: Send RP-reachability for 228.1.1.1 on Serial0/0
*Mar 1 20:51:52.994: PIM: Building Join/Prune message for 228.1.1.1
*Mar 1 20:51:52.998: PIM: For 150.20.125.1, Join-list: 150.20.13.3/32
*Mar 1 20:51:52.998: PIM: Send v2 periodic Join/Prune to 150.20.125.1 (Serial0/0)
*Mar 1 20:51:56.994: PIM: Send v2 Hello on Loopback0
*Mar 1 20:51:56.994: PIM: Received v2 Hello on Loopback0 from 150.20.5.5
*Mar 1 20:52:00.994: PIM: Send v2 Hello on Serial0/0
This is the result of the ping to group 228.1.1.1 from a router connected to router B.
Reply to request 0 from 150.20.125.2, 80 ms
Reply to request 1 from 150.20.125.5, 64 ms
Reply to request 1 from 150.20.125.2, 76 ms
Reply to request 2 from 150.20.125.5, 104 ms
Reply to request 3 from 150.20.125.5, 40 ms
Reply to request 2 from 150.20.125.5, 104 ms
Reply to request 3 from 150.20.125.5, 40 ms
Reply to request 2 from 150.20.125.5, 104 ms
Reply to request 3 from 150.20.125.5, 40 ms
Reply to request 2 from 150.20.125.5, 104 ms
Reply to request 3 from 150.20.125.5, 40 ms
Reply to request 2 from 150.20.125.5, 104 ms
Reply to request 3 from 150.20.125.5, 40 ms
Reply to request 2 from 150.20.125.5, 104 ms
Reply to request 3 from 150.20.125.5, 40 ms
Reply to request 2 from 150.20.125.5, 104 ms
Reply to request 3 from 150.20.125.5, 40 ms
This archive was generated by hypermail 2.1.4 : Mon May 03 2004 - 19:48:51 GMT-3