Which two actions describe LSP delegation to PCE servers? (Choose two.)
Which two actions describe LSP delegation to PCE servers? (Choose two.)
LSP delegation to PCE servers involves actions that trigger the re-evaluation of LSP delegation. Entering the mpls traffic-eng reoptimize command manually triggers traffic engineering re-optimization, forcing a re-evaluation of LSP delegation. Adding a new PCE server with lower precedence than the primary PCE can make the new server the primary server if it has a lower precedence value, effectively delegating LSP control to it. These actions specifically relate to the process of changing which PCE server is managing the LSPs.
i Think this is B and C The question does not specify which PCE server is to be the primary. so technically both D and E are correct depending on what you want to accomplish. if you want the Primary PCE to remain the primary then add a PCE with a higher precedence. If you want the Primary PCE to switch to the new PCE then set it at a lower precedence. For this reason is why i think the answer is B and C. Triggering PCE server precedence re-evaluation A change in a PCE server’s precedence is not considered a PCE server failure. So, the change in precedence does not trigger a redelegation timeout or a re-evaluation of LSP delegation to the PCE server at a PCC. Re-evaluation of LSP delegation to PCE servers after CLI reconfiguration is controlled by the TE reoptimisation timer. By default, the TE reoptimisation timer is set to 3600 seconds. You can accelerate the re-evaluation of LSP delegation from a PCC to PCE servers after you have changed the precedence of PCE servers or added new PCE servers. To do so, manually trigger TE reoptimisation.
Correct answer is B and C. rm868, I agree with your post. The meaning of question, it implies that PCE servers have already configured. Answer D and E are incorrect based on this assumption. Answer A is incorrect, it is unable to disable re-optimization timer (By default, the TE reoptimisation timer is set to 3600 seconds.).
sorry, i meant C and D
I think C and D are the right answers. Here is why from the same link: lower precedence => PCE is primary The IP addreseses are compared incase of equal priority. If the precedence for two PCEs is same, PCE with smaller IP address has a higher precedence. You can accelerate the re-evaluation of LSP delegation from a PCC to PCE servers after you have changed the precedence of PCE servers or added new PCE servers. To do so, manually trigger TE reoptimisation using the following command in privileged EXEC mode: mpls traffic-eng reoptimiz
its definitely E If the precedence for two PCEs is same, PCE with smaller IP address has a higher precedence. and its C. You can accelerate the re-evaluation of LSP delegation from a PCC to PCE servers after you have changed the precedence of PCE servers or added new PCE servers. To do so, manually trigger TE reoptimisation using the following command in privileged EXEC mode: mpls traffic-eng reoptimize all found on the same URL provided.
If a PCC is connected to multiple PCEs, the PCC selects a PCE with the lowest precedence value. If there is a tie, a PCE with the highest IP address is chosen for computing path. https://www.cisco.com/c/en/us/td/docs/iosxr/ncs5500/segment-routing/72x/b-segment-routing-cg-ncs5500-72x.pdf But in the question does not mention anything about the IPs, only regarding the precedence, no? and lower precedence --> primary PCE
you are right sir!
Yes, but lower precedence means it has a better chance to be the primary, so definitely not E
yes you are right! ( I also said this about Murmelika earlier)
A and C?. According to the link provided in the answer, a lower precedence PCE becomes the primary PCE and then "You can accelerate the re-evaluation of LSP delegation from a PCC to PCE servers after you have changed the precedence of PCE servers or added new PCE servers. To do so, manually trigger TE reoptimisation using the following command in privileged EXEC mode:mpls traffic-eng reoptimize"
The answer is in the question somewhat, as it talks about delegating the current primary, so C and D seem the best fit.
In the above code snippet, 100 is a lower precedence than 255, which is the default precedence. Therefore, the device with IP address 192.0.2.2 becomes the primary PCE and the device with 192.0.2.1 becomes the standby PCE. Triggering PCE server precedence re-evaluation A change in a PCE server’s precedence is not considered a PCE server failure. So, the change in precedence does not trigger a redelegation timeout or a re-evaluation of LSP delegation to the PCE server at a PCC. Re-evaluation of LSP delegation to PCE servers after CLI reconfiguration is controlled by the TE reoptimisation timer. By default, the TE reoptimisation timer is set to 3600 seconds. You can accelerate the re-evaluation of LSP delegation from a PCC to PCE servers after you have changed the precedence of PCE servers or added new PCE servers. To do so, manually trigger TE reoptimisation using the following command in privileged EXEC mode: mpls traffic-eng reoptimize
Answers are B/C
B and C
C and D are better for me than C and B
why not B? from the link in the question i quote: "A change in a PCE server’s precedence is not considered a PCE server failure. So, the change in precedence does not trigger a redelegation timeout or a re-evaluation of LSP delegation to the PCE server at a PCC." so basically changing the precedence do not trigger a delegation, but adding a new PCE server does
LSP Delegations as per link: -Enter "#mpls traffic-eng reoptimize", and add new PCE server (lower precedence)
Triggering PCE server precedence re-evaluation A change in a PCE server’s precedence is not considered a PCE server failure. So, the change in precedence does not trigger a redelegation timeout or a re-evaluation of LSP delegation to the PCE server at a PCC. Re-evaluation of LSP delegation to PCE servers after CLI reconfiguration is controlled by the TE reoptimisation timer. By default, the TE reoptimisation timer is set to 3600 seconds. You can accelerate the re-evaluation of LSP delegation from a PCC to PCE servers after you have changed the precedence of PCE servers or added new PCE servers. To do so, manually trigger TE reoptimisation using the following command in privileged EXEC mode: mpls traffic-eng reoptimize