6.2 unreliable pings to 228.28.28.28

Hi,

I got the problem that pinging from R6 with:

ping 228.28.28.28 source 132.1.6.6 rep 20

showed up as:

Rack1R2#
*Mar 16 23:59:22.207: IP(0): s=132.1.26.6 (FastEthernet0/0) d=228.28.28.28 (Serial0/0) id=720, ttl=254, prot=1, len=100(100), mforward

on R2 and though the route back from SW1 to 132.1.26.6 was failing.
Rack1SW1#mtrace 132.1.26.6 228.28.28.28
Type escape sequence to abort.
Mtrace from 132.1.26.6 to 132.1.17.7 via group 228.28.28.28
From source (?) to destination (?)
Querying full reverse path...
0 132.1.17.7
-1 132.1.17.7 PIM [132.1.26.0/24]
-2 132.1.17.1 PIM [132.1.26.0/24]
-3 132.1.0.3 PIM [default]
-4 132.1.23.2 None Multicast disabled [132.1.26.0/24]


R1 has two routes to 132.1.26.0....

Rack1R1#r 132.1.26.6
Routing entry for 132.1.26.0/24
Known via "ospf 1", distance 110, metric 20, type extern 2, forward metric 64
Last update from 132.1.0.3 on Serial0/0, 00:00:08 ago
Routing Descriptor Blocks:
* 132.1.0.2, from 150.1.2.2, 00:00:08 ago, via Serial0/0
Route metric is 20, traffic share count is 1
132.1.0.3, from 150.1.3.3, 00:00:08 ago, via Serial0/0
Route metric is 20, traffic share count is 1

So sometimes the first one or two pings got through, but then when the route over R3 is chosen the multicast ping would fail.

So for completing the lab i had to adjust the distance on R1:

R1
router ospf 1
distance 111 150.1.3.3 0.0.0.0 40
!
access-list 40 permit 132.1.26.0 0.0.0.255


Frank

Comments

Sign In or Register to comment.