300-510 · Question #269
Refer to the exhibit. A network engineer must enable connections from customers on PE1 to the external network via the SR-MPLS forwarding plane with a range of 8000 SID. In the current environment…
The correct answer is B. PE1(config)# router isis SR. To enable SR-MPLS forwarding via IS-IS while coexisting with existing LDP labels (16100-16199 on PE1, 16200-16299 on PE2), the engineer must configure the SRGB (Segment Routing Global Block) under IS-IS with a range of 8000 SIDs that does not overlap with those LDP ranges. The…
Question
Refer to the exhibit. A network engineer must enable connections from customers on PE1 to the external network via the SR-MPLS forwarding plane with a range of 8000 SID. In the current environment:
- The MPLS forwarding tables on PE1 and PE2 are populated with LDP-
originated LDP labels.
- The current ranges are 16100 - 16199 on PE1 and 16200 - 16299 on PE2.
Which configuration must the engineer apply?
Exhibit
Options
- APE1 (config)# router isis SR
- BPE1(config)# router isis SR
- CPE1(config)# router isis SR
- DPE1(config)# router isis SR
How the community answered
(25 responses)- A4% (1)
- B76% (19)
- C16% (4)
- D4% (1)
Explanation
To enable SR-MPLS forwarding via IS-IS while coexisting with existing LDP labels (16100-16199 on PE1, 16200-16299 on PE2), the engineer must configure the SRGB (Segment Routing Global Block) under IS-IS with a range of 8000 SIDs that does not overlap with those LDP ranges. The correct configuration (Answer B) includes enabling segment routing under IS-IS, setting a valid non-overlapping SRGB base and size of 8000, and ensuring SR is activated globally. The other answer choices (A, C, D) likely contain errors such as incorrect SRGB base values that would conflict with the existing LDP label ranges, missing the 'metric-style wide' requirement for SR-capable IS-IS, or other misconfiguration that would prevent correct SR label allocation and forwarding.
Topics
Community Discussion
No community discussion yet for this question.