Quantcast
Channel: IEOC - INE's Online Community
Viewing all articles
Browse latest Browse all 10744

in which case, you can only get a few of reply when ping is used to test multicast connectivity|

$
0
0

Rack1R1#ping
Protocol Paradise:
Target IP address: 225.25.25.25
Repeat count [1]: 100
Datagram size [100]:
Timeout in seconds [2]:
Extended commands : y
Interface [All]: serial1/0.1
Time to live [255]:
Source address or interface: 192.10.1.1
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 :
Type escape sequence to abort.
Sending 100, 100-byte ICMP Echos to 225.25.25.25, timeout is 2 seconds:
Packet sent with a source address of 192.10.1.1
..................
Reply to request 18 from 141.1.37.3, 140 ms...................................................
..............................
Rack1R1#ping         
Protocol Paradise:
Target IP address: 225.25.25.25
Repeat count [1]: 100
Datagram size [100]:
Timeout in seconds [2]:
Extended commands : y
Interface [All]: serial1/0.1
Time to live [255]:
Source address or interface: 192.10.1.1 
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 :
Type escape sequence to abort.
Sending 100, 100-byte ICMP Echos to 225.25.25.25, timeout is 2 seconds:
Packet sent with a source address of 192.10.1.1

Reply to request 0 from 141.1.37.3, 164 ms.....................................................................
....................
Reply to request 90 from 141.1.37.3, 105 ms.........
Rack1R1#

As above, when I do a ping on R1 to test R3's IGMP joined-group, you can see I just got 1 or 2 replies of a 100 pings. Anybody know what the possible reason is?

 


Viewing all articles
Browse latest Browse all 10744

Latest Images

Trending Articles



Latest Images