Fabric design
APIC cluster, spine-leaf on Nexus 9000, multi-pod or multi-site with Nexus Dashboard Orchestrator.
Datacenter · Cisco
ACI done properly, or ACI left behind — your call.
Design, deployment and operation of Cisco ACI fabrics — tenants, application profiles, contracts, multi-pod and multi-site — plus the honest alternative: a fixed-price migration to Apstra when ACI's model no longer fits.
What's included
01
02
Policy model
Tenants, VRFs, bridge domains, EPGs and contracts designed with the application teams, not for them.
03
Integration
VMM domains, L4-7 service insertion for Palo Alto and Fortinet, L3Outs to WAN and cloud.
04
Operations
Nexus Dashboard Insights, change workflow and the twin for contract changes.
05
Health and remediation
Fault review, contract sprawl cleanup, upgrade planning.
06
Exit path
ACI to Apstra migration program when you want multi-vendor freedom.
How an engagement runs
01
Assess or design
Existing fabric health review, or greenfield design.
02
Deploy
Fabric and policy built from code.
03
Operate
Insights, change workflow, optional managed operations.
Questions we get asked
Should we stay on ACI?
If your teams work well in the policy model and you are committed to Nexus, yes. If contracts have sprawled and every change is a project, we will show you the alternative with numbers.
Request a quote
Tell us about the project; a senior engineer responds the same business day.