OCC/EXACC: ICMP Ping or Traceroute showing high latency/slowness on TOR switch
(Doc ID 2793363.1)
Last updated on APRIL 01, 2024
Applies to:
Oracle Public Cloud Machine X6 Hardware - Version X6 and laterExadata Cloud at Customer X7-2 Hardware - Version All Versions and later
Exadata Cloud at Customer X6-2 Hardware - Version All Versions and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Big Data Cloud at Customer X7-2 Hardware - Version All Versions and later
Information in this document applies to any platform.
Symptoms
Customer is pinging our side of the handoff network from his switch and is concerned at high latency (see below output), given that the two switches are directly connected and suspect the ToR switch is unhealthy.
PING 172.xx.xxx.x (172.xx.xxx.x) 56(84) bytes of data.
64 bytes from 172.xx.xxx.x: icmp_seq=1 ttl=62 time=22.1 ms
64 bytes from 172.xx.xxx.x: icmp_seq=2 ttl=62 time=20.8 ms
64 bytes from 172.xx.xxx.x: icmp_seq=3 ttl=62 time=20.1 ms
64 bytes from 172.xx.xxx.x: icmp_seq=4 ttl=62 time=21.7 ms
64 bytes from 172.xx.xxx.x: icmp_seq=5 ttl=62 time=41.8 ms
64 bytes from 172.xx.xxx.x: icmp_seq=6 ttl=62 time=41.8 ms
64 bytes from 172.xx.xxx.x: icmp_seq=7 ttl=62 time=12.8 ms
64 bytes from 172.xx.xxx.x: icmp_seq=8 ttl=62 time=26.1 ms
64 bytes from 172.xx.xxx.x: icmp_seq=9 ttl=62 time=33.2 ms
64 bytes from 172.xx.xxx.x: icmp_seq=10 ttl=62 time=17.6 ms
64 bytes from 172.xx.xxx.x: icmp_seq=11 ttl=62 time=24.0 ms
64 bytes from 172.xx.xxx.x: icmp_seq=12 ttl=62 time=17.0 ms
64 bytes from 172.xx.xxx.x: icmp_seq=13 ttl=62 time=18.3 ms
They also can show a traceroute/tracert where the high latency is shown when they access the ToR switch IP
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Cause |
| Solution |