Reset Search
 

 

Article

Specifying an IPv6 ping count greater than the default of 5 reports inaccurate results

« Go Back

Information

 
TitleSpecifying an IPv6 ping count greater than the default of 5 reports inaccurate results
Symptoms
  • A default ping (count of 5) reports accurate results
SLX# ping ipv6 2600:3c01:e000:e2::2 source 2600:3c01:e000:e2::8 vrf mgmt-vrf
Type Control-c to abort
PING 2600:3c01:e000:e2::2 (2600:3c01:e000:e2::2) from 2600:3c01:e000:e2::8: 56 data bytes
64 bytes from 2600:3c01:e000:e2::2: icmp_seq=0 ttl=64 time=2.498 ms
64 bytes from 2600:3c01:e000:e2::2: icmp_seq=1 ttl=64 time=0.330 ms
64 bytes from 2600:3c01:e000:e2::2: icmp_seq=2 ttl=64 time=0.378 ms
64 bytes from 2600:3c01:e000:e2::2: icmp_seq=3 ttl=64 time=0.913 ms
64 bytes from 2600:3c01:e000:e2::2: icmp_seq=4 ttl=64 time=0.441 ms
--- 2600:3c01:e000:e2::2 ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max/stddev = 0.330/0.912/2.498/0.820 ms
  • Specifying a count less than the default also reports accurate results
SLX# ping ipv6 2600:3c01:e000:e2::2 source 2600:3c01:e000:e2::8 vrf mgmt-vrf count 3
Type Control-c to abort
PING 2600:3c01:e000:e2::2 (2600:3c01:e000:e2::2) from 2600:3c01:e000:e2::8: 56 data bytes
64 bytes from 2600:3c01:e000:e2::2: icmp_seq=0 ttl=64 time=0.407 ms
64 bytes from 2600:3c01:e000:e2::2: icmp_seq=1 ttl=64 time=0.308 ms
64 bytes from 2600:3c01:e000:e2::2: icmp_seq=2 ttl=64 time=0.337 ms
--- 2600:3c01:e000:e2::2 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max/stddev = 0.308/0.351/0.407/0.042 ms
  • Specifying a counter greater than 5 reports inaccurate results
SLX# ping ipv6 2600:3c01:e000:e2::2 source 2600:3c01:e000:e2::8 vrf mgmt-vrf count 6
Type Control-c to abort
PING 2600:3c01:e000:e2::2 (2600:3c01:e000:e2::2) from 2600:3c01:e000:e2::8: 56 data bytes
64 bytes from 2600:3c01:e000:e2::2: icmp_seq=0 ttl=64 time=0.455 ms
64 bytes from 2600:3c01:e000:e2::2: icmp_seq=1 ttl=64 time=0.298 ms
64 bytes from 2600:3c01:e000:e2::2: icmp_seq=2 ttl=64 time=0.302 ms
64 bytes from 2600:3c01:e000:e2::2: icmp_seq=3 ttl=64 time=0.318 ms
64 bytes from 2600:3c01:e000:e2::2: icmp_seq=4 ttl=64 time=0.425 ms
--- 2600:3c01:e000:e2::2 ping statistics ---
6 packets transmitted, 5 packets received, 16% packet loss
round-trip min/avg/max/stddev = 0.298/0.360/0.455/0.067 ms
 
SLX# ping ipv6 2600:3c01:e000:e2::2 source 2600:3c01:e000:e2::8 vrf mgmt-vrf count 10
Type Control-c to abort
PING 2600:3c01:e000:e2::2 (2600:3c01:e000:e2::2) from 2600:3c01:e000:e2::8: 56 data bytes
64 bytes from 2600:3c01:e000:e2::2: icmp_seq=0 ttl=64 time=0.390 ms
64 bytes from 2600:3c01:e000:e2::2: icmp_seq=1 ttl=64 time=0.305 ms
64 bytes from 2600:3c01:e000:e2::2: icmp_seq=2 ttl=64 time=0.348 ms
64 bytes from 2600:3c01:e000:e2::2: icmp_seq=3 ttl=64 time=0.392 ms
64 bytes from 2600:3c01:e000:e2::2: icmp_seq=4 ttl=64 time=0.351 ms
--- 2600:3c01:e000:e2::2 ping statistics ---
6 packets transmitted, 5 packets received, 16% packet loss
round-trip min/avg/max/stddev = 0.305/0.357/0.392/0.032 ms
  • IPv4 pings do not report the same issue
  • Issue was not present when testing on 18r.1.x firmware
  • Issue is present on 18r.2.x firmware
Environment
  • SLX
  • SLXOS 18r.2.00b and earlier 18r.2.x releases
Cause
  • CLI is not accepting the count parameter
Resolution
  • Issue is scheduled to be addressed in the 20.1.1 and 18r.2.00c releases
  • Issue is also not present in the 18r.1.x releases
Additional notes

Feedback

 

Was this article helpful?


   

Feedback

Please tell us how we can make this article more useful.

Characters Remaining: 255