BGP policy is how large infrastructure teams express intent: which paths are preferred, how traffic exits under failure, and what changes are safe to automate. When policy is inconsistent across sites, every peering change becomes a bespoke engineering event.
Treat policy as a controlled interface
- Standardize community semantics across edge and backbone domains.
- Document prefix origination and export policy before production turn-up.
- Require pre-check and post-check for any policy or peering change.
- Maintain rollback configuration for every BGP maintenance window.
Automation follows policy clarity
Teams cannot safely automate BGP changes until policy is predictable and auditable. Start with validated MOPs and monitoring tied to expected path behavior. Automation and AIOps integrations come after the routing domain has a clear, documented contract.