Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Juniper JN0-650 Exam - Topic 1 Question 16 Discussion

Posted by Kanisha on Sep 29, 2026 at 11:32 AM

The network you support currently has a mixture of MC-LAG and Virtual Chassis being used to provide redundant connectivity from various IDFs. A project to modernize the architecture and move to EVPN-VXLAN using ESI-LAG will be starting soon. You want to avoid IDFs losing connectivity as the core devices are migrated to EVPN-VXLAN. Which action will accomplish this task?

Suggested Answer: C

In an EVPN-VXLAN environment using ESI-LAG (Ethernet Segment Identifier Link Aggregation), the Core Isolation feature is a safety mechanism designed to prevent traffic blackholing. When a leaf switch (acting as a VTEP) loses its BGP peering or its link to the IP fabric core, it assumes it is 'isolated' from the rest of the network. To protect the network, the switch automatically shuts down its local member links of any multi-homed ESI-LAG to force traffic to the peer switch that still has core connectivity.

However, during a migration or in specific transitional topologies where the core might be temporarily unreachable or not yet fully established, this feature can cause the leaf switches to shut down all downstream IDF (Intermediate Distribution Frame) connections, leading to a total loss of connectivity.

The Solution (Option C): By enabling the no-core-isolation statement under the [edit protocols evpn] hierarchy, you instruct the switch to disable this automatic shutdown behavior. This ensures that even if the BGP session or core links are not yet stable during the migration process, the ESI-LAG interfaces remain Up, allowing the IDFs to maintain connectivity to their local default gateways or other local resources.

Why others are incorrect: Enabling EVPN-VXLAN before migration (Option A) does not address the isolation logic. Removing MC-LAG/Virtual Chassis links prematurely (Option B) would cause an immediate outage. The network-isolation-profile (Option D) is typically used for different loop prevention scenarios and does not override the specific core-isolation check that affects multi-homed ESIs.


Get Premium JN0-650 Questions as Interactive Web-Based Practice Test or PDF Real Exam Format Detailed Explanations Instant Access Get Your Practice Test
9 comments · newest first
DI
Dino 3 days ago
A makes the most sense for a smooth transition!
NG
Nguyet 8 days ago
Enabling no-core-isolation sounds risky.
NA
Nancey 14 days ago
Wait, is disabling Virtual Chassis really a good idea?
CA
Cammy 19 days ago
I disagree, B could cause issues.
MY
Myra 24 days ago
A is the way to go!
BR
Brandon 29 days ago
The network-isolation-profile on the leaf devices sounds familiar; I think it might help during the migration, but I need to double-check the details.
JA
Jaime 1 month ago
I feel like enabling no-core-isolation could lead to problems, but I can't recall the exact implications from my studies.
GA
Galen 1 month ago
I remember a practice question where disabling Virtual Chassis caused issues. Removing links sounds risky, but maybe it’s necessary?
TO
Tora 1 month ago
I think enabling EVPN-VXLAN on the leaf devices first might help maintain connectivity, but I'm not entirely sure if that's the best approach.
0/2000 characters

Save Cancel