1 / 18

Comprehensive Connectivity Testing using Ping and ICMP Protocols

This document outlines various connectivity testing methodologies using the Ping and ICMP protocols. It includes details about Fast Ping (fping) and AutoStatus, emphasizing one-way ping tests and statistics for different servers, including response times and packet loss. The report pipes into multi-site testing, offering insights into RTT, with specific examples like Berkeley and IT-Sudparis. The document also touches on tools for reverse traceroute and introduces AutoStatus for service checks. Essential for network administrators seeking to enhance connectivity evaluation.

macha
Download Presentation

Comprehensive Connectivity Testing using Ping and ICMP Protocols

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Connectivity Test

  2. Outline • Ping & ICMP • Fast Ping (fping) & AutoStatus • One-Way Ping

  3. Ping • Pinging 163.22.20.115 with 32 bytes of data: • Reply from 163.22.20.115: bytes=32 time<1ms TTL=64 • Reply from 163.22.20.115: bytes=32 time<1ms TTL=64 • Reply from 163.22.20.115: bytes=32 time<1ms TTL=64 • Reply from 163.22.20.115: bytes=32 time<1ms TTL=64 • Ping statistics for 163.22.20.115: • Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), • Approximate round trip times in milli-seconds: • Minimum = 0ms, Maximum = 0ms, Average = 0ms

  4. ICMP Packet Format • RFC 792 – Internet Control Message Protocol

  5. Probing Packets

  6. Round-Trip Time Client Server 0.000 ms request reply 9.952 ms 1006.122 ms request reply 1017.039 ms

  7. 166ms to Berkeley • Pinging www.berkeley.edu [169.229.131.81] with 32 bytes of data: • Reply from 169.229.131.81: bytes=32 time=166ms TTL=46 • Reply from 169.229.131.81: bytes=32 time=166ms TTL=46 • Reply from 169.229.131.81: bytes=32 time=166ms TTL=46 • Reply from 169.229.131.81: bytes=32 time=166ms TTL=46 • Ping statistics for 169.229.131.81: • Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), • Approximate round trip times in milli-seconds: • Minimum = 166ms, Maximum = 166ms, Average = 166ms

  8. 330ms to France • Pinging www.it-sudparis.eu [157.159.11.8] with 32 bytes of data: • Reply from 157.159.11.8: bytes=32 time=330ms TTL=39 • Reply from 157.159.11.8: bytes=32 time=330ms TTL=39 • Reply from 157.159.11.8: bytes=32 time=330ms TTL=39 • Reply from 157.159.11.8: bytes=32 time=330ms TTL=39 • Ping statistics for 157.159.11.8: • Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), • Approximate round trip times in milli-seconds: • Minimum = 330ms, Maximum = 330ms, Average = 330ms

  9. Looking Glass Server • Reverse traceroute • http://www.six-de.net/lg/

  10. HW 1 • Find a website which provides the reverse traceroute service. • Mail the following information to voip-ta@ipv6.club.tw. • URL of the service • Is it dual-stack or IPv4-only? • What interesting services (in addition to ping and traceroute) did you find? • Due: 2009.9.29 (Tue) 13:00

  11. fping • fping < FILENAME • fping -g 163.22.20.0/24 • A class C subnet is scanned in 30 seconds.

  12. AutoStatus

  13. AutoStatus • Use “fping” to check whether servers are on-line. • Use “tcp_check.c” to check that services are running. • If the FTP server is listening at TCP port 21, the attempt to establish a connection at ftp.ncnu.edu.tw:21 will succeed. • No way to check UDP services!

  14. HW 2 • Query an IP phone with the OPTIONS method. • Write a SIPp script or a sipcheck.c (similar to the tcpcheck.c in AutoStatus) • Return -1 on failure; 0 on success. • Try to integrate this tool to AutoStatus • You may need to modify AutoStatus so that its “hosts” configuration file can specify the UDP port.

  15. Tools Presentation • Two independent speakers for each tool: • SIPp • Cacti • BWCTL • perfSONAR

More Related