SD-Access brings identity, device context and policy into the campus network.
Campus access, distribution and core switching designed as one fabric, not isolated boxes. SD-Access brings identity, device context, policy and segmentation into the campus network so access decisions can be managed more consistently across every port and every site.
- 01 · Design Access, distribution and core One fabric · resiliency · PoE++
- 02 · Fabric Identity and segmentation SD-Access · DNA Center · ISE
- 03 · Deploy Migrate and validate Migration · as-built · handover
A conceptual sequence used to explain the service, not a customer deployment.
What it is
Campus access, distribution and core switching designed as one fabric rather than isolated boxes, with SD-Access as the layer that carries identity, device context, policy and segmentation across every port and every site.
- 01
Access, distribution and core switch design
- 02
SD-Access fabric and identity-based segmentation
- 03
Resiliency and PoE++ planning for IoT and AP density
- 04
Migration, as-built documentation and validated handover
What CDS delivers
- Access, distribution and core switch designThe campus switched as one fabric, not isolated boxes
- SD-Access fabric and identity-based segmentationConsistent access decisions across every port and site
- StackWise resiliency and PoE++ planningSized for IoT and access-point density
- Migration planning from legacy estatesStaged transition from existing switching
- As-built documentation and validated handoverRecords and sign-off at completion
Platforms CDS builds on
Cisco Catalyst 9000 Series · SD-Access.
- Catalyst 9200 / 9300 SeriesAccess-layer switching
- Catalyst 9400 / 9500 / 9600 SeriesDistribution and core switching
- Cisco DNA CenterSD-Access fabric control
- Identity Services Engine (ISE)Identity and policy integration
How we deliver it
- Step 1
Discover
Assess the current estate, port density, IoT and AP needs and constraints.
- Step 2
Design
Shape the access/distribution/core fabric, SD-Access policy and segmentation.
- Step 3
Prove
Validate identity policy and resiliency where the design calls for it.
- Step 4
Deploy
Migrate in an approved sequence, then test and document the handover.
Questions about this service
What is SD-Access, and where does it fit?+
SD-Access is the fabric and policy layer of the campus switching design. It brings identity, device context and segmentation into the network so access decisions can be managed consistently across every port and site, controlled through Cisco DNA Center with Identity Services Engine (ISE).
Can CDS migrate a legacy switching estate?+
Yes. CDS plans migration from legacy switching estates in stages, with as-built documentation and a validated handover.
Start with the conditions around switching.
Describe the current environment, the change you are considering and what the result must support.