MENU
Exhibit.
You are troubleshooting a DCI connection to another data center The BGP session to the provider is established, but the session to Border-Leaf-2 is not established. Referring to the exhibit, which configuration change should be made to solve the problem?
Suggested Answer: D, D
Get Premium JN0-683 Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
Understanding the Configuration:
The exhibit shows a BGP configuration on a Border-Leaf device. The BGP group UNDERLAY is used for the underlay network, OVERLAY for EVPN signaling, and PROVIDER for connecting to the provider network.
The OVERLAY group has the accept-remote-nexthop statement, which is designed to accept the next-hop address learned from the remote peer as is, without modifying it.
Problem Identification:
The BGP session to Border-Leaf-2 is not established. A common issue in EVPN-VXLAN environments is related to next-hop reachability, especially when accept-remote-nexthop is configured.
In typical EVPN-VXLAN setups, the next-hop address should be reachable within the overlay network. However, the accept-remote-nexthop can cause issues if the next-hop IP address is not directly reachable or conflicts with the expected behavior in the overlay.
Corrective Action:
33 comments · newest first
NI
Nida
10 months ago
Definitely need to set the right export policies for BGP.
RO
Rory
10 months ago
Isn't it risky to just delete commands like that?
YO
Yolande
11 months ago
Wow, I didn't realize next-hop settings were so crucial!
TE
Teri
11 months ago
I disagree, I think option B might be better.
MA
Maricela
11 months ago
Looks like option D is the way to go!
LE
Lezlie
11 months ago
I think removing the accept-remote-nexthop command makes sense, but I’m not confident if that’s the only change needed to fix the BGP session.
CH
Christene
11 months ago
I feel like I’ve seen something similar before, but I’m torn between options B and D. I need to think about how next-hop attributes work in this context.
BR
Bronwyn
12 months ago
This question reminds me of a practice scenario where we had to adjust next-hop settings. I think option D could be the right choice.
CA
Carissa
12 months ago
I remember studying BGP configurations, but I'm not entirely sure which option directly affects the session with Border-Leaf-2.
RO
Rozella
12 months ago
Okay, let me think this through step-by-step. The BGP session to the provider is up, but the one to Border-Leaf-2 is not. The options seem to be related to BGP group configurations, so I'll need to carefully analyze each one to determine the best course of action.
LA
Lashon
1 year ago
Option D is the way to go here. Accepting remote next-hops can cause issues in certain EVPN-VXLAN setups, so removing that configuration should help establish the BGP session with Border-Leaf-2. I've seen this problem before and this is usually the fix.
MA
Marshall
1 year ago
Hmm, this looks tricky. I'm a bit unsure about the different BGP groups and how they're configured. I might need to review the EVPN-VXLAN design and troubleshooting steps before I can confidently select the right option.
CO
Cornell
1 year ago
The key here seems to be the BGP next-hop configuration. I'd try option D and remove the accept-remote-nexthop command to see if that resolves the issue with the Border-Leaf-2 session.
CE
Celestina
1 year ago
Wait, we're supposed to be troubleshooting a data center connection, not playing a game of BGP Bingo! Someone call the IT Avengers, we need a superhero to fix this mess.
KA
Kathrine
1 year ago
User 2: Good idea, that could help establish the BGP session with Border-Leaf-2.
CH
Chauncey
1 year ago
We need to follow best practices to ensure stable BGP sessions in our data center environment.
JU
Justine
1 year ago
Removing the accept-remote-nexthop command should help establish the BGP session with Border-Leaf-2.
CU
Curt
1 year ago
User 1: Maybe we should try removing the accept-remote-nexthop command.
CA
Catalina
1 year ago
Let's focus on the task at hand and make the necessary configuration change to solve the problem.
JA
Jacquline
1 year ago
Option D it is! Removing that accept-remote-nexthop command sounds like the perfect solution to get that BGP session with Border-Leaf-2 up and running. Textbook stuff, really.
RE
Remedios
1 year ago
Agreed! It's important to follow best practices when troubleshooting BGP sessions in complex environments like EVPN-VXLAN.
AR
Aretha
1 year ago
Option D it is! Removing that accept-remote-nexthop command sounds like the perfect solution to get that BGP session with Border-Leaf-2 up and running. Textbook stuff, really.
LE
Levi
1 year ago
I'm with Margret on this one. Option D is the way to go. Gotta love it when the answer is right there in the explanation!
MO
Moon
1 year ago
Haha, this one's a no-brainer. The answer is right there in the explanation - 'Removing this command will ensure that the device uses its own IP address as the next-hop in BGP advertisements.' Simple fix!
FL
Floyd
1 year ago
User 2: Got it, thanks for the tip!
ST
Starr
1 year ago
User 1: Yeah, just remove that command and it should work fine.
DO
Dorethea
1 year ago
I'm not sure, but I think option D is the best choice based on the exhibit.
MA
Margret
1 year ago
Definitely go with option D - deleting the accept-remote-nexthop command. That's a common fix for BGP session issues in EVPN-VXLAN setups.
DO
Dominic
1 year ago
Proper handling of BGP next-hop attributes is crucial for stable BGP sessions in complex environments like EVPN-VXLAN.
EN
Enola
1 year ago
Removing accept-remote-nexthop is a common fix for BGP session issues in EVPN-VXLAN setups.
LA
Lavera
1 year ago
Option D is the way to go. It should help establish the BGP session with Border-Leaf-2.
JA
Janine
1 year ago
I agree with Holley, removing accept-remote-nexthop makes sense.
HO
Holley
1 year ago
I think the answer is D.