Milestone 3: Analytics service deployed

This is the third milestone checkpoint. The instructor will review the connectivity work you have just completed before you move on to monitoring and observability.

✅ Added an analytics server to the fabric as a generic system with redundant links to both leaf switches
✅ Applied connectivity templates to attach the server to the analytics-web and analytics-db virtual networks automatically
✅ Staged an external router in Undeploy mode — full configuration pre-built, ready to activate when the hardware arrives
✅ Configured BGP peering via a connectivity template, with Apstra generating all BGP and IP addressing configuration from the two values you entered

In a traditional environment, the work you just completed would span multiple tools, multiple engineers, and multiple maintenance windows. The server’s VLAN configuration, the trunk ports, the EVPN ESI-LAG, the BGP session, the routing policy — each of those would be a separate manual task.

In Apstra, every step is an expression of intent. You described the outcome you needed, and the platform handled the implementation. The single source of truth now reflects the complete picture: server connectivity, network segments, and external peering — all documented automatically as a side effect of the changes you made.

The analytics service is deployed. Now you will look at what happens when things go wrong — and how Apstra helps you investigate, understand, and recover from issues in a live fabric.

This section also includes an instructor-led demo of on-prem flow analytics. Read the note at the top of the next section carefully before you begin.

Ready? Let’s move on!