Task 5.2 Multicast testing

Dear All,

 

I have not added the static route which is mentioned in workbook, but still i am able to ping the R5. Instead i add the static route for 150.1.0.0/16 alone, but still i am able to get the response from R5.

 

Rack1R5#
IP(0): s=183.1.28.2 (Serial0/0/0) d=226.26.26.26 (FastEthernet0/0) id=849, ttl=253, prot=1, len=100(100), mforward
Rack1R5#
IP(0): s=183.1.28.2 (Serial0/0/0) d=226.26.26.26 (FastEthernet0/0) id=850, ttl=253, prot=1, len=100(100), mforward
Rack1R5#
IP(0): s=183.1.28.2 (Serial0/0/0) d=226.26.26.26 (FastEthernet0/0) id=851, ttl=253, prot=1, len=100(100), mforward
Rack1R5#
IP(0): s=183.1.28.2 (Serial0/0/0) d=226.26.26.26 (FastEthernet0/0) id=852, ttl=253, prot=1, len=100(100), mforward
Rack1R5#
IP(0): s=183.1.28.2 (Serial0/0/0) d=226.26.26.26 (FastEthernet0/0) id=853, ttl=253, prot=1, len=100(100), mforward
Rack1R5#
IP(0): s=183.1.28.2 (Serial0/0/0) d=226.26.26.26 (FastEthernet0/0) id=854, ttl=253, prot=1, len=100(100), mforward


Rack1R5#sh ip rpf 183.1.28.2
RPF information for ? (183.1.28.2)
  RPF interface: FastEthernet0/0  -----------> RPF check is towards Fa0/0
  RPF neighbor: ? (183.1.105.10)
  RPF route/mask: 183.1.28.0/24
  RPF type: unicast (eigrp 100)
  RPF recursion count: 0
  Doing distance-preferred lookups across tables

Rack1R2#ping
Protocol [ip]:
Target IP address: 226.26.26.26
Repeat count [1]: 1500
Datagram size [100]:
Timeout in seconds [2]:
Extended commands [n]: y
Interface [All]:
Time to live [255]:
Source address or interface:  fastEthernet0/0
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 1500, 100-byte ICMP Echos to 226.26.26.26, timeout is 2 seconds:
Packet sent with a source address of 183.1.28.2

Reply to request 0 from 183.1.0.5, 116 ms
Reply to request 1 from 183.1.0.5, 112 ms
Reply to request 2 from 183.1.0.5, 113 ms
Reply to request 3 from 183.1.0.5, 116 ms
Reply to request 4 from 183.1.0.5, 116 ms
Reply to request 5 from 183.1.0.5, 117 ms
Reply to request 6 from 183.1.0.5, 120 ms
Reply to request 7 from 183.1.0.5, 120 ms
Reply to request 8 from 183.1.0.5, 120 ms
Reply to request 9 from 183.1.0.5, 129 ms

 

Thanks,

Jayaram

Comments

  • what is the result of the trace and mtrace commands?

    Try troublshoot backwards from the receiver to the rp and from the rp to the source and use the debug if necessary.

    I also don't remember that we used R2's F0/0 interface in those labs so as i see you source the multicast stream from R2f0/0 let us know if your topology follow a different design.

Sign In or Register to comment.