Route issue or SDWAN issue ?
- 3 replies
- 3781 views
Hi, guys,
I have a network infrastructure:
1. Three sites: SiteA, SiteB and SiteC;
2. The Forti400E pair sits between SiteA and SiteC;
3. The Forti400E pair has individual static route table for SiteA and SiteC:
4. The Forti400E pair has a SDWAN ( Link01 (port08) and Link02 (port9) ) to SiteC.
5. The SDWAN is using Link01(port8) for primary link to access SiteC ( SDWAN is configured for this ), but the link02 (port9) has better SLA
My problem ( port9 is link02, in my test):
==========================
1. When I just opened the CLI mode, without any specified source interface :
1.1 Pingtest to siteC -- OK!!
1.2 traceroute is OK
2. When I specified an source interface,
2.1 Pintest to siteC failed
2.2 traceroute failed
3. What reason the SDWAN used link02/port9 for accessing SiteC ( not useing link01/port8 ), while specifying the source interface?
Noted: 10.10.32.65 is GW of the link01; 10.10.32.91 is GW of the link02
Test result refers to the attached captured.
Any idea or advice.
Thanks a lot
Benson LEI
