Comware Based
cancel
Showing results for 
Search instead for 
Did you mean: 

ping -r does not record why ??

rodrigohpadilla
Occasional Visitor

ping -r does not record why ??

Hi guys!


I have problems with ping -r command. I ping a host out of my LAN and want to know the record for this request. Is not working! Do you know why ?

 

 

<CORE>ping -r 192.168.38.95
  PING 172.18.38.95: 56  data bytes, press CTRL_C to break
    Reply from 192.168.38.95: bytes=56 Sequence=0 ttl=124 time=20 ms
    Reply from 192.168.38.95: bytes=56 Sequence=1 ttl=124 time=17 ms
    Reply from 192.168.38.95: bytes=56 Sequence=2 ttl=124 time=15 ms
    Reply from 192.168.38.95: bytes=56 Sequence=3 ttl=124 time=18 ms
    Reply from 192.168.38.95: bytes=56 Sequence=4 ttl=124 time=17 ms

  --- 192.168.38.95 ping statistics ---
    5 packet(s) transmitted
    5 packet(s) received
    0.00% packet loss
    round-trip min/avg/max = 15/17/20 ms

<CORE>

 

The system version is:
<CORE>dis version
HP Comware Platform Software
Comware Software, Version 5.20.105, Release 6708-US

Thanks!!!

3 REPLIES
Vince-Whirlwind
Honored Contributor

Re: ping -r does not record why ??

Try

ping -R 192.168.38.95

 

 

rodrigohpadilla
Occasional Visitor

Re: ping -r does not record why ??

Hi Vince.  Thanks for your response but is not working with -R

 

<CORE>ping -R 192.168.38.95
  PING 192.18.38.95: 56  data bytes, press CTRL_C to break
    Reply from 192.168.38.95: bytes=56 Sequence=0 ttl=124 time=15 ms
    Reply from 192.168.38.95: bytes=56 Sequence=1 ttl=124 time=16 ms
    Reply from 192.168.38.95: bytes=56 Sequence=2 ttl=124 time=17 ms
    Reply from 192.168.38.95: bytes=56 Sequence=3 ttl=124 time=14 ms
    Reply from 192.168.38.95: bytes=56 Sequence=4 ttl=124 time=16 ms

  --- 192.168.38.95 ping statistics ---
    5 packet(s) transmitted
    5 packet(s) received
    0.00% packet loss
    round-trip min/avg/max = 14/15/17 ms

<CORE>

Vince-Whirlwind
Honored Contributor

Re: ping -r does not record why ??

It also depends on the router - not all routers will agree to send back the info in the header - try a different path through different routers to see if the result changes.

 

Maybe also try a count number after the -R, in (the unlikely) case that makes a difference.