From: Brian (shotcaller30@xxxxxxxxxxx)
Date: Tue Nov 14 2000 - 00:42:23 GMT-3
Keith,
According to your tests the spoke to spoke ping still doesn't work. Maybe
I'm missing something here?
Thanks
Keith T. Hall Wrote:
r3#ping 225.4.4.4
Type escape sequence to abort.
Sending 1, 100-byte ICMP Echos to 225.4.4.4, timeout is 2 seconds:
*** r4 is the RP and subscribes to 225.4.4.4 ***
----- Original Message -----
From: Keith T. Hall <kthall@sprintmail.com>
To: <ccielab@groupstudy.com>
Sent: Monday, November 13, 2000 5:30 PM
Subject: RE: Repost: Multicast with RP as Spoke (2 of 2)
> *** r2 subscribes to 225.2.2.2, but is also the MA **
>
> r2#sh ip pim rp
> Group: 225.3.3.3, RP: 172.16.4.4, v1, uptime 00:40:52, expires 00:04:24
> Group: 225.2.2.2, RP: 172.16.4.4, v1, uptime 01:00:12, expires 00:04:24
> Group: 225.4.4.4, RP: 172.16.4.4, v1, uptime 00:07:30, expires 00:04:24
>
> r2#ping 225.2.2.2
>
> Type escape sequence to abort.
> Sending 1, 100-byte ICMP Echos to 225.2.2.2, timeout is 2 seconds:
>
> Reply to request 0 from 172.16.2.2, 8 ms
> Reply to request 0 from 172.16.2.2, 8 ms
>
> r2#ping 225.3.3.3
>
> Type escape sequence to abort.
> Sending 1, 100-byte ICMP Echos to 225.3.3.3, timeout is 2 seconds:
>
> Reply to request 0 from 172.16.1.3, 8 ms
> Reply to request 0 from 172.16.1.3, 20 ms
>
> r2#ping 225.4.4.4
>
> Type escape sequence to abort.
> Sending 1, 100-byte ICMP Echos to 225.4.4.4, timeout is 2 seconds:
>
> Reply to request 0 from 172.16.1.4, 8 ms
>
> *** r3 is a regular spoke subscribed to 225.3.3.3 ***
>
> r3#sh ip pim rp
> Group: 225.3.3.3, RP: 172.16.4.4, v1, uptime 00:43:15, expires 00:02:30
> Group: 225.2.2.2, RP: 172.16.4.4, v1, uptime 00:39:34, expires 00:02:30
> Group: 225.4.4.4, RP: 172.16.4.4, v1, uptime 00:06:09, expires 00:02:30
>
> r3#ping 225.2.2.2
>
> Type escape sequence to abort.
> Sending 1, 100-byte ICMP Echos to 225.2.2.2, timeout is 2 seconds:
>
> Reply to request 0 from 172.16.1.2, 4 ms
> Reply to request 0 from 172.16.1.2, 85 ms
>
> r3#ping 225.3.3.3
>
> Type escape sequence to abort.
> Sending 1, 100-byte ICMP Echos to 225.3.3.3, timeout is 2 seconds:
>
> Reply to request 0 from 172.16.3.3, 4 ms
> Reply to request 0 from 172.16.3.3, 4 ms
>
> r3#ping 225.4.4.4
>
> Type escape sequence to abort.
> Sending 1, 100-byte ICMP Echos to 225.4.4.4, timeout is 2 seconds:
> .
>
>
> *** r4 is the RP and subscribes to 225.4.4.4 ***
>
> r4#sh ip pim rp
> Group: 225.3.3.3, RP: 172.16.4.4, v1, next RP-reachable in 00:00:19
> Group: 225.2.2.2, RP: 172.16.4.4, v1, next RP-reachable in 00:00:35
> Group: 225.4.4.4, RP: 172.16.4.4, v1, next RP-reachable in 00:00:35
>
> r4#ping 225.2.2.2
>
> Type escape sequence to abort.
> Sending 1, 100-byte ICMP Echos to 225.2.2.2, timeout is 2 seconds:
>
> Reply to request 0 from 172.16.1.2, 14 ms
> Reply to request 0 from 172.16.1.2, 54 ms
> Reply to request 0 from 172.16.1.2, 14 ms
>
> r4#ping 225.3.3.3
>
> Type escape sequence to abort.
> Sending 1, 100-byte ICMP Echos to 225.3.3.3, timeout is 2 seconds:
> .
>
> r4#ping 225.4.4.4
>
> Type escape sequence to abort.
> Sending 1, 100-byte ICMP Echos to 225.4.4.4, timeout is 2 seconds:
>
> Reply to request 0 from 172.16.4.4, 12 ms
> Reply to request 0 from 172.16.4.4, 12 ms
>
>
> ** BEFORE YOU ASK 'WHY THE NUMBER OF PING RESPONSES?' CHECK OUT
PRUNING...!
>
> Whew! (I hope this ends this thread...)
>
>
>
> Keith T. Hall
> Sr. Network Engineer, Service Provider Accounts
> Greenwich Technology Partners
> 3810 Concorde Parkway, Suite 500
> Chantilly, VA 20151
> (703) 966-1854 Cell
> (703) 222-6465 Office
> (703) 222-6424 Fax
> khall@greenwichtech.com
> http://www.greenwichtech.com
>
>
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:25:44 GMT-3