MENU
Refer to the exhibit.
A customer reports that they are not able to reach subnet 10.10.10.0/24 from their FortiGate device.
Based on the exhibit, what should you do to correct the situation?
Suggested Answer: A
Get Premium NSE8_812 Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
A is correct because using network-overlay id allows you to configure multiple ADVPN tunnels on a single interface with a single IP address on the DC FortiGate. This is explained in the FortiGate Administration Guide under ADVPN > Configuring ADVPN > Configuring ADVPN on the hub. References: https://docs.fortinet.com/document/fortigate/7.4.0/administration-guide/978793/advpn https://docs.fortinet.com/document/fortigate/7.4.0/administration-guide/978793/advpn/978794/configuring-advpn
31 comments · newest first
OL
Olive
10 months ago
Additional-path feature could help, but not sure if it's necessary.
AL
Alexis
11 months ago
Definitely need to check the routing table first before making changes.
LU
Lucina
11 months ago
Surprised that enabling iBGP multipath is even an option for this issue.
FR
Frederica
11 months ago
I disagree, next-hop-self feature seems more relevant here.
VE
Verda
11 months ago
Looks like enabling recursive resolution for BGP routes is the way to go.
CA
Caitlin
12 months ago
I think enabling iBGP multipath was mentioned in a different context, but I'm not confident it applies to this specific subnet issue.
DY
Dyan
12 months ago
I vaguely recall that enabling recursive resolution can sometimes solve reachability problems, but I need to double-check if that's applicable here.
IR
Irene
12 months ago
This question feels similar to one we practiced where we had to troubleshoot BGP routes. I think enabling next-hop-self might help, but I could be wrong.
ED
Edison
1 year ago
I remember studying BGP configurations, but I'm not entirely sure which option directly addresses the reachability issue.
NO
Norah
1 year ago
Aha, this is a classic routing problem! I bet the issue is with the next-hop configuration. Enabling next-hop-self should do the trick.
VI
Viva
1 year ago
Okay, the exhibit shows some BGP settings, so I think the answer is likely related to BGP configuration. I'll need to understand the purpose of the different BGP features mentioned.
EL
Elliot
1 year ago
Hmm, the question mentions a FortiGate device, so I'm guessing the issue is with the firewall configuration. I'll need to check the routing table and security policies.
OR
Oretha
1 year ago
This looks like a routing issue, so I'll need to carefully review the network topology and BGP configuration to determine the best solution.
SH
Shenika
1 year ago
This question is like a game of 'Where's Waldo?' - the exhibit is nowhere to be found! I guess I'll have to rely on my network troubleshooting skills to figure this one out.
SA
Samira
1 year ago
Okay, let's think this through. The options seem to be related to BGP configuration, but I'm not sure if that's the right approach here. I might need to dig deeper into the network topology.
ED
Edna
1 year ago
User 3: Good point. Let's check the routing table first to see if the subnet is even being advertised.
DY
Dyan
1 year ago
User 2: No, I haven't. Maybe we should start there before diving into BGP configuration.
RE
Rebbecca
1 year ago
User 1: Have you checked the routing table on the FortiGate device?
PA
Paola
1 year ago
Haha, the question says 'Refer to the exhibit', but there's no exhibit to be seen. Is this a trick question or what?
TA
Talia
1 year ago
User 3
MI
Millie
1 year ago
User 2
CH
Chuck
1 year ago
User 1
GR
Gregg
1 year ago
Ah, the classic 'can't reach the subnet' problem. I bet it's a misconfigured static route or a missing dynamic routing protocol.
PE
Pearlene
1 year ago
Could be a next-hop issue, check that configuration
TR
Trina
1 year ago
Make sure the subnet is correctly advertised in BGP
CO
Cordelia
1 year ago
Maybe the dynamic routing protocol is not running properly
NA
Nan
1 year ago
Check the static routes first
SO
Son
1 year ago
Hmm, this seems like a routing issue. I'd start by checking the routing table and the interface configurations on the FortiGate device.
CA
Carylon
2 years ago
I'm not sure, but I think enabling additional-path feature could also be a possible solution.
MA
Marta
2 years ago
I agree with Mozell, enabling next-hop-self feature should help resolve the issue.
MO
Mozell
2 years ago
I think the correct answer is C) Enable next-hop-self feature.