3.10 alternate verification using extended ping

I am really liking my latest path verification tool: EXTENDED PING

 

If anyone has any opinions on the limitations please share.

 

The solution guide for 3.10 has the ip route-cache verification method....  I think that is great but for me it is a bunch of extra steps.

 

Here is the verification for this task using Traceroute and Extended Ping:

 

Rack13SW4#trace 172.16.0.9

Type escape sequence to abort.
Tracing the route to 172.16.0.9

  1 10.34.0.9 44 msec *  40 msec
Rack13SW4#ping
Protocol [ip]:
Target IP address: 172.16.0.9
Repeat count [5]:
Datagram size [100]:
Timeout in seconds [2]:
Extended commands [n]: y
Source address or interface: 172.16.0.10
Type of service [0]:
Set DF bit in IP header? [no]:
Validate reply data? [no]:
Data pattern [0xABCD]:
Loose, Strict, Record, Timestamp, Verbose[none]: record
Number of hops [ 9 ]:
Loose, Strict, Record, Timestamp, Verbose[RV]:
Sweep range of sizes [n]:
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 172.16.0.9, timeout is 2 seconds:
Packet sent with a source address of 172.16.0.10
Packet has IP options:  Total option bytes= 39, padded length=40
 Record route: <*>
   (0.0.0.0)
   (0.0.0.0)
   (0.0.0.0)
   (0.0.0.0)
   (0.0.0.0)
   (0.0.0.0)
   (0.0.0.0)
   (0.0.0.0)
   (0.0.0.0)

Reply to request 0 (72 ms).  Received packet has options
 Total option bytes= 40, padded length=40
 Record route:
   (10.34.0.10)
   (10.34.0.9)
   (10.34.0.9)
   (10.34.0.10) <*>
   (0.0.0.0)
   (0.0.0.0)
   (0.0.0.0)
   (0.0.0.0)
   (0.0.0.0)
 End of list

Reply to request 1 (72 ms).  Received packet has options
 Total option bytes= 40, padded length=40
 Record route:
   (10.34.0.10)
   (10.34.0.9)
   (10.34.0.9)
   (10.34.0.10) <*>
   (0.0.0.0)
   (0.0.0.0)
   (0.0.0.0)
   (0.0.0.0)
   (0.0.0.0)
 End of list

Reply to request 2 (68 ms).  Received packet has options
 Total option bytes= 40, padded length=40
 Record route:
   (10.34.0.10)
   (10.34.0.9)
   (10.34.0.9)
   (10.34.0.10) <*>
   (0.0.0.0)
   (0.0.0.0)
   (0.0.0.0)
   (0.0.0.0)
   (0.0.0.0)
 End of list

Reply to request 3 (72 ms).  Received packet has options
 Total option bytes= 40, padded length=40
 Record route:
   (10.34.0.10)
   (10.34.0.9)
   (10.34.0.9)
   (10.34.0.10) <*>
   (0.0.0.0)
   (0.0.0.0)
   (0.0.0.0)
   (0.0.0.0)
   (0.0.0.0)
 End of list

Reply to request 4 (72 ms).  Received packet has options
 Total option bytes= 40, padded length=40
 Record route:
   (10.34.0.10)
   (10.34.0.9)
   (10.34.0.9)
   (10.34.0.10) <*>
   (0.0.0.0)
   (0.0.0.0)
   (0.0.0.0)
   (0.0.0.0)
   (0.0.0.0)
 End of list

Success rate is 100 percent (5/5), round-trip min/avg/max = 68/71/72 ms            

 

NET_OG

Comments

  • For the lab it should be fine. On the Internet or in production, packets with IP options are usually dropped. 

    Brian McGahan, CCIE #8593 (R&S/SP/Security)
     
    Internetwork Expert, Inc.
    Toll Free: 877-224-8987 x 705
    Outside US: 775-826-4344 x 705
    Online Community: http://www.IEOC.com

    On Sep 15, 2010, at 9:56 AM, "Net_OG" <[email protected]> wrote:

    I am really liking my latest path verification tool: EXTENDED PING

     

    If anyone has any opinions on the limitations please share.

     

    The solution guide for 3.10 has the ip route-cache verification method....  I think that is great but for me it is a bunch of extra steps.

     

    Here is the verification for this task using Traceroute and Extended Ping:

     

    Rack13SW4#trace 172.16.0.9

    Type escape sequence to abort.
    Tracing the route to 172.16.0.9

      1 10.34.0.9 44 msec *  40 msec
    Rack13SW4#ping
    Protocol Paradise:
    Target IP address: 172.16.0.9
    Repeat count [5]:
    Datagram size [100]:
    Timeout in seconds [2]:
    Extended commands : y
    Source address or interface: 172.16.0.10
    Type of service [0]:
    Set DF bit in IP header? [no]:
    Validate reply data? [no]:
    Data pattern [0xABCD]:
    Loose, Strict, Record, Timestamp, Verbose[none]: record
    Number of hops [ 9 ]:
    Loose, Strict, Record, Timestamp, Verbose[RV]:
    Sweep range of sizes :
    Type escape sequence to abort.
    Sending 5, 100-byte ICMP Echos to 172.16.0.9, timeout is 2 seconds:
    Packet sent with a source address of 172.16.0.10
    Packet has IP options:  Total option bytes= 39, padded length=40
     Record route: <*>
       (0.0.0.0)
       (0.0.0.0)
       (0.0.0.0)
       (0.0.0.0)
       (0.0.0.0)
       (0.0.0.0)
       (0.0.0.0)
       (0.0.0.0)
       (0.0.0.0)

    Reply to request 0 (72 ms).  Received packet has options
     Total option bytes= 40, padded length=40
     Record route:
       (10.34.0.10)
       (10.34.0.9)
       (10.34.0.9)
       (10.34.0.10) <*>
       (0.0.0.0)
       (0.0.0.0)
       (0.0.0.0)
       (0.0.0.0)
       (0.0.0.0)
     End of list

    Reply to request 1 (72 ms).  Received packet has options
     Total option bytes= 40, padded length=40
     Record route:
       (10.34.0.10)
       (10.34.0.9)
       (10.34.0.9)
       (10.34.0.10) <*>
       (0.0.0.0)
       (0.0.0.0)
       (0.0.0.0)
       (0.0.0.0)
       (0.0.0.0)
     End of list

    Reply to request 2 (68 ms).  Received packet has options
     Total option bytes= 40, padded length=40
     Record route:
       (10.34.0.10)
       (10.34.0.9)
       (10.34.0.9)
       (10.34.0.10) <*>
       (0.0.0.0)
       (0.0.0.0)
       (0.0.0.0)
       (0.0.0.0)
       (0.0.0.0)
     End of list

    Reply to request 3 (72 ms).  Received packet has options
     Total option bytes= 40, padded length=40
     Record route:
       (10.34.0.10)
       (10.34.0.9)
       (10.34.0.9)
       (10.34.0.10) <*>
       (0.0.0.0)
       (0.0.0.0)
       (0.0.0.0)
       (0.0.0.0)
       (0.0.0.0)
     End of list

    Reply to request 4 (72 ms).  Received packet has options
     Total option bytes= 40, padded length=40
     Record route:
       (10.34.0.10)
       (10.34.0.9)
       (10.34.0.9)
       (10.34.0.10) <*>
       (0.0.0.0)
       (0.0.0.0)
       (0.0.0.0)
       (0.0.0.0)
       (0.0.0.0)
     End of list

    Success rate is 100 percent (5/5), round-trip min/avg/max = 68/71/72 ms            

     

    NET_OG




    Internetwork Expert - The Industry Leader in CCIE Preparation

    http://www.internetworkexpert.com



    Subscription information may be found at:

    http://www.ieoc.com/forums/ForumSubscriptions.aspx
  •  

    thank you, Brian.  great point.

  • Thank you Net_OG for the share.

Sign In or Register to comment.