Why tracert showing OLD wan address?!?!

[40User]

I am pulling my hair out here. We changed ISP' s so i setup the NEW IP scheme on the WAN2 of the 100A of our remote office. I kept the WAN1 link enabled until we were satisfied with the new setup. The new ISP link is live and working great with all the policies and VPN tunnels etc. When i tracert an LOCAL IP on the remote office form our corp office through the IPSEC VPN tunnel, the first hop is the corp Forti and the second hop is the OLD WAN address NOT the new one??? The old link is dead and down. Odd thing is that the tracert is successful and pings. We are having another issue that I am hoping is part of this problem. Thoughts?

[Fullmoon]

Maybe a sort of cache on fortigate box. have you tried to reboot both fortigate units and perform another traceroute?

[40User]

yup...did a reboot on both but still shows the previous WAN address???? What is odd is that we have literally disconnected the line to the old ISP router.

[rwpatterson]

Take the IP address off the interface and see what happens.

[emnoc]

I was going to suggest the same earlier when I 1st seen this thread

[40User]

Thanks RWpat! By taking the previous WAN IP info on WAN1 completely out and replacing it with with zeros' .....tracert is sane again. It also fixed another routing issue we were having. Is this a bug? As always, thanks!

[rwpatterson]

I don' t know, but I have seen this bizarre behavior in the past. The FGTs sometimes like to hang onto the past....