Make the current network and dependencies visible
Transformation starts with workflows, before a device list. Record the networks used by employees, printers, cameras and critical applications. Assign owners to IP pools, DHCP, DNS, NTP, identity services and external connections. Two devices sharing a VLAN do not necessarily need the same access. Compare inventory with observed traffic and record a successful baseline. This helps distinguish changes introduced by the pilot from problems that already existed.
Validate the underlay and fabric roles
Cisco SD-Access uses Catalyst Center for management, LISP for the control plane, VXLAN for the data plane and TrustSec for policy. Assess these responsibilities alongside hardware, software and licensing compatibility. Plan edge, border and control-plane roles for capacity and redundancy. Define tests for underlay reachability, MTU and external connectivity. Routing at the fabric boundary must account for data centre, internet and WAN services. A healthy device is insufficient evidence that the campus works: application flows need separate validation.
Cisco SD-Access: small-site topology
Figure 29 of the Cisco design guide shows campus connectivity, the colocated border/control-plane pair, fabric edges and the wireless services block together.
- Routed link
- Access / Layer 2 link
- Edge firewall A
- Firewall pair shown in the remainder of the campus in the source figure.
- Edge firewall B
- The second firewall in the pair shown by the source.
- Catalyst Center
- Campus management and automation component. This figure does not depict management sessions as cabling.
- ISE PAN / MnT
- ISE administration and monitoring personas in the remainder of the campus.
- DHCP · DNS · AD
- Shared services grouped together on the campus side in the original figure.
- Campus routing
- Routing node shown between the upper campus connection and the two BN/CP nodes.
- BN / CP A
- Border and control-plane roles share one device; the source shows a crosslink to the other BN/CP.
- BN / CP B
- Second colocated border/control-plane node with alternate physical paths to edges and the services block.
- Local ISE PAN
- The local ISE node connected to the services block is labelled ISE PAN in the source; its role has not been changed.
- WLC
- Wireless controller linked to the services block by a Layer 2 port-channel in the reference design.
- Services block
- Switch-stack or StackWise Virtual services block; routed links to both BN/CP nodes and a Layer 2 WLC link are shown.
- Fabric edge A
- Fabric edge linked to both BN/CP nodes and a wired client in the source.
- Fabric edge B
- Fabric edge linked to both BN/CP nodes and the fabric access point.
- Fabric edge C
- Fabric edge linked to both BN/CP nodes and the second wired client.
- Fabric AP
- AP cabled to edge B. Wireless clients are shown with radio symbols in the source, not wired connections.
- Wired client
- Wired endpoint attached to fabric edge A in the source.
- Wired client
- Wired endpoint attached to fabric edge C in the source.
- Wireless client
- Wireless endpoint from the source; no physical cable has been added.
- Wireless client
- Second wireless endpoint from the source; no physical cable has been added.
Tie policy to identity and application needs
Virtual networks organise logical separation while security groups organise permitted relationships. Design Cisco ISE authentication and authorisation with certificate infrastructure and device diversity in mind. Document exceptions for devices that cannot authenticate; broad access should not become a permanent workaround. Obtain required resources and ports from application owners. Test denied paths as well as permitted ones. Defined ownership and review dates turn segmentation into an operating practice rather than a one-time configuration.
Test coexistence through a bounded pilot
Limit the first scope to a representative but manageable user group or floor. Prepare acceptance scenarios for wired and wireless access, roaming, guests and critical applications. Define coexistence boundaries between legacy VLANs and the fabric; extend Layer 2 only where needed. Agree on decision makers and rollback thresholds before the change window. Test identity service and connectivity failures alongside successful flows. Evaluate device evidence, application tests and user feedback together.
Make operational handover part of the design
After a successful pilot, order migration waves by application criticality. Current topology, access matrices, rollback steps and alarm ownership belong in the handover. Operators should trace a user access issue through authentication, policy and the data path. Assign responsibility for access transfer, configuration backups and policy review. Plan post-change monitoring and acceptance decisions in advance. A discussion with Trustnet can clarify current network constraints, business priorities and a practical transition scope.


