JN0-480 · Question #8
You have recently committed a change after creating a new blueprint in Juniper Apstra. In the main dashboard, you see a number of anomalies related to BGR What is a likely cause of these anomalies?
The correct answer is B. The fabric has not converged yet. In Juniper Apstra, a blueprint is a logical representation of the network design and configuration. When you create a new blueprint, you need to commit the changes to apply them to the network devices. However, committing the changes does not mean that the network is…
Question
You have recently committed a change after creating a new blueprint in Juniper Apstra. In the main dashboard, you see a number of anomalies related to BGR What is a likely cause of these anomalies?
Options
- AYou have misconfigured ASNs.
- BThe fabric has not converged yet.
- CSpine-leaf links are incorrectly set.
- DA generic system has not been configured.
How the community answered
(50 responses)- A6% (3)
- B76% (38)
- C14% (7)
- D4% (2)
Explanation
In Juniper Apstra, a blueprint is a logical representation of the network design and configuration. When you create a new blueprint, you need to commit the changes to apply them to the network devices. However, committing the changes does not mean that the network is immediately updated and operational. It may take some time for the network to converge and reflect the new state of the blueprint. During this time, you may see some anomalies related to BGP in the main dashboard, which indicate that the BGP sessions are not established or stable between the devices. These anomalies are usually temporary and will disappear once the network converges and the BGP sessions are up and running.
Topics
Community Discussion
No community discussion yet for this question.