5.3 Multicast Testing

Hello,

While all my testing on r3 and r4 turned out fine, is there a reason why I am not able to ping any of the two multicast groups on r3 (239.39.39.39 & 225.25.25.25) using an extended ping on r4 with source interface 204.12.1.4 from vlan 4, but instead of sending out FastEthernet0/0, using Serial0/0/0 as my destination interface?  I know the solution only uses FastEthernet0/0, but in my initial testing, I began by using r4's Frame Relay Interface Serial0/0/0 and when it didn't work, I wondered why not if the Frame Interface of both r4 and r5 are also ip pim sparse-mode enabled interfaces. Upon discovering this, I testing using FastEthernet0/0 as my destination with again 204.12.1.4 as my source interface (from vlan43) and that worked. So while the SG didn't use the Frame Interface, I pondered over why not and shouldn't it also work? These two interface are load balanced from previous tasks. Could that be the issue? RPF check? Not sure, but obviously in a real world scenario, which I know this is not, wouldn't we want this to work, assuming a link failure occured on FastEthernet0/0. Not to mention that the p2p s0/1/0 interface should also participate in the ip pim multicast, but that isn't a requirement here.

Thanks, Jorge.

Here is my test output:

RSRack1R4#ping
Protocol [ip]:
Target IP address: 239.39.39.39
Repeat count [1]: 100
Datagram size [100]:
Timeout in seconds [2]:
Extended commands [n]: y
Interface [All]: FastEthernet0/0
Time to live [255]:
Source address: 204.12.1.4
Type of service [0]:
Set DF bit in IP header? [no]:
Validate reply data? [no]:
Data pattern [0xABCD]:
Loose, Strict, Record, Timestamp, Verbose[none]:
Sweep range of sizes [n]:
Type escape sequence to abort.
Sending 100, 100-byte ICMP Echos to 239.39.39.39, timeout is 2 seconds:
Packet sent with a source address of 204.12.1.4

Reply to request 0 from 141.1.123.3, 88 ms
Reply to request 1 from 141.1.123.3, 84 ms
Reply to request 2 from 141.1.123.3, 84 ms
Reply to request 3 from 141.1.123.3, 84 ms


RSRack1R4#ping
Protocol [ip]:
Target IP address: 239.39.39.39
Repeat count [1]:
Datagram size [100]:
Timeout in seconds [2]:
Extended commands [n]: y
Interface [All]: Serial0/0/0
Time to live [255]:
Source address: 204.12.1.4
Type of service [0]:
Set DF bit in IP header? [no]:
Validate reply data? [no]:
Data pattern [0xABCD]:
Loose, Strict, Record, Timestamp, Verbose[none]:
Sweep range of sizes [n]:
Type escape sequence to abort.
Sending 1, 100-byte ICMP Echos to 239.39.39.39, timeout is 2 seconds:
Packet sent with a source address of 204.12.1.4
.

Sign In or Register to comment.