{"id":204,"date":"2026-06-26T00:00:00","date_gmt":"2026-06-25T20:30:00","guid":{"rendered":"https:\/\/www.anynet.ir\/blog\/%d8%b4%d8%a8%da%a9%d9%87%d8%b3%d8%a7%d8%b2%db%8c-%d8%ae%d9%88%d8%af%da%a9%d8%a7%d8%b1-%d8%a8%d8%a7-cisco-crosswork-%d9%85%d8%af%db%8c%d8%b1%db%8c%d8%aa-%da%86%d8%b1%d8%ae%d9%87-%d8%ad%db%8c%d8%a7-en\/"},"modified":"2026-10-19T11:07:40","modified_gmt":"2026-10-19T07:37:40","slug":"%d8%b4%d8%a8%da%a9%d9%87%d8%b3%d8%a7%d8%b2%db%8c-%d8%ae%d9%88%d8%af%da%a9%d8%a7%d8%b1-%d8%a8%d8%a7-cisco-crosswork-%d9%85%d8%af%db%8c%d8%b1%db%8c%d8%aa-%da%86%d8%b1%d8%ae%d9%87-%d8%ad%db%8c%d8%a7-en","status":"publish","type":"post","link":"https:\/\/www.anynet.ir\/blog\/en\/%d8%b4%d8%a8%da%a9%d9%87%d8%b3%d8%a7%d8%b2%db%8c-%d8%ae%d9%88%d8%af%da%a9%d8%a7%d8%b1-%d8%a8%d8%a7-cisco-crosswork-%d9%85%d8%af%db%8c%d8%b1%db%8c%d8%aa-%da%86%d8%b1%d8%ae%d9%87-%d8%ad%db%8c%d8%a7-en\/","title":{"rendered":"Autonomous Networking with Cisco Crosswork: Multivendor Device and Service Lifecycle, Segment Routing, and AI-Ready Operations"},"content":{"rendered":"
<\/div>\n
\n
<\/div>\n<\/div>\n
\n
\n
\n

Autonomous networking depends on a closed operational loop: accurate inventory, transport visibility, intent-based service provisioning, device-side validation, and service-health telemetry that can be trusted by operators and automation systems. This article shows how Cisco Crosswork Network Controller 7.2 can operate in a multivendor environment with IOS XR provider edge routers, a Juniper vMX provider edge router, and Cisco SR-PCE.<\/p>\n

The workflow connects inventory discovery, Segment Routing traffic engineering, L3VPN service provisioning, Junos-specific Service Health extensions, and final symptom validation. The result is not only a monitored VPN service, but an AI-ready operational model where Crosswork can expose normalized state across vendors and distinguish real service degradation from collection or package gaps.<\/p>\n

Acknowledgements<\/h2>\n

Special Thanks to Krishnan Thirukonda, Michael Maddern, and Nicola Martino for their collaboration, guidance, and contributions to the multivendor CNC 7.2 work described in this article.<\/p>\n

Why This Matters<\/h2>\n

In a single-vendor network, inventory, topology, service intent, and health telemetry often align naturally because every layer understands the same device models and command outputs. In a multivendor network, that alignment has to be engineered. The Junos work in this lab shows the pieces required to make Crosswork useful for autonomous operations:<\/p>\n