09-09-2024 04:11 PM - edited 09-09-2024 04:11 PM
Here is the tracker config:
tracker tracker1
endpoint-ip 8.8.8.8
It is applied here:
vpn 0
name VPN0_Underlay_VPN
dns 4.2.2.2 secondary
dns 8.8.8.8 primary
interface ge0/0
description INET1
ip dhcp-client
nat
respond-to-ping
!
tracker tracker1
vedge1# show tracker
VPN INTERFACE STATUS RTT
---------------------------------
0 ge0_0 UP Timeout
ame VPN0_Underlay_VPN
dns 4.2.2.2 secondary
dns 8.8.8.8 primary
interface ge0/0
description INET1
ip dhcp-client
nat
respond-to-ping
!
tracker tracker1
The status is down I pruned the output so you see tracker status is DOWN.
vedge1# show interface ge0/0 | tab
0 ge0/0 ipv4 192.168.3.10/24 Up Up Down
router1# ping 8.8.8.8
Ping in VPN 0
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=115 time=14.2 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=115 time=13.5 ms
Any ideas?
Solved! Go to Solution.
09-10-2024 07:18 AM
I believe the tracker needs to respond to http. I changed it to google.com and it works. This is pretty poorly documented but I found it on another forum.
09-09-2024 09:46 PM
Hello @dodgerfan78
On your tracker config, specify source IP address.
09-10-2024 07:09 AM - edited 09-10-2024 07:12 AM
It's DHCP, why should I need to do that? Plus, there is no source option in the tracker command.
09-10-2024 07:16 AM
I still checking I think the track is down because of rtt is long it 14 msec and I think the track by default use 1-3 msec
But let me complete checking
MHM
09-10-2024 07:18 AM
I believe the tracker needs to respond to http. I changed it to google.com and it works. This is pretty poorly documented but I found it on another forum.
09-10-2024 07:23 AM
Thanks a lot for update us
Can I know for which service you use track
To get completed pictures of issue
Thanks
MHM
09-10-2024 10:20 AM
I dont know what you are saying by which service. The config is above, i just changed it to google.com instead of 8.8.8.8.
11-16-2024 11:06 AM
yes you are right, the endpoint should respond to http. I also read it on someones blogpost. The only problem is now that somehow if the endpoint tracker is up the traffic is forced to internet tloc, ignoring the fact that mpls tloc is available and omp routing is available to the hub in datacenter. I did configure nat dia fallback accoring to the official configuration guide.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide