You are building a blueprint using Juniper Apstra and must change the cable map to...

In Apstra 5.1, the cabling map is part of the blueprint’s intended physical topology. Cable-map edits are performed in the Staged workspace because Staged is where you modify intent (what the fabric should look like) before committing those changes and deploying them. The Staged → Physical → Links view provides both a tabular and topology-oriented representation of spine-to-leaf and other physical connections. When Apstra auto-assigns interfaces during initial build, the logical mapping may not match the real patching in the data center. The cabling map editor allows you to override interface names (and where applicable, link addressing metadata) so the blueprint accurately reflects the actual patch panel and switchport usage.

This accuracy is critical in a Junos v24.4 leaf-spine fabric because underlay correctness depends on the real physical adjacencies: link membership, LAG expectations (where used), and the resulting BGP neighbor relationships that carry EVPN signaling for VXLAN overlays. By updating the cabling map in Staged, you ensure Apstra can correctly validate neighbor discovery, verify intent, and produce consistent device configuration aligned to the real-world wiring. After making the cabling corrections, you commit the staged changes and then deploy/apply so that Apstra’s intent and the running network converge. This work is not performed under Active (which reflects deployed state) and is not a function of Connectivity Templates (which are for endpoint/service attachment rather than fabric cabling).

Verified Juniper sources (URLs):

https://www.juniper.net/documentation/us/en/software/apstra5.0/apstra-user-guide/topics/topic-map/cabling-map-edit-datacenter.html

https://www.juniper.net/documentation/us/en/software/apstra6.0/apstra-user-guide/topics/topic-map/cabling-map-edit-datacenter.html

https://www.juniper.net/documentation/us/en/software/jvd/jvd-dcfabric-5-stage/configuration_walkthrough.html