A 911 PSAP fabric edge shows different VN bindings than Catalyst Center inventory after a weekend of CLI troubleshooting. What should the municipal network team treat as the authoritative fabric inventory source?
Select an answer to reveal the explanation.
Short Explanation
Think of Catalyst Center as the city GIS map and CLI as sticky notes someone left on one street corner. The map is the source of truth for fabric membership and VN bindings; chasing every one-off CLI tweak without reconciling intent is how PSAP edges drift. Re-sync to the controller before making more local changes.
Full Explanation
In Cisco SD-Access, Catalyst Center maintains fabric inventory, device roles, and segmentation intent for edges, borders, and control-plane nodes. Ad-hoc CLI changes can temporarily alter underlay or overlay behavior, but they are not the authoritative design record. Municipal teams should reconcile observed CLI state to controller inventory and re-apply intent so fabric consistency is restored. Treating switch USB archives or vendor VLAN spreadsheets as authoritative bypasses fabric orchestration and invites further drift.