Verify critical site and EdgeConnect connectivity, then capture the same artifacts you captured in the Before Maintenance Window Checklist and compare. The sections below are in the same order as the before page.

📘
Let the fabric settle before you capture. Field practice: wait 5 minutes; if tunnels are not yet up, wait another 10-15. Judge readiness on tunnel status, not the clock. A flow or route capture taken too early will show differences that are still converging.

Gather Organization Resources

Alert the following that they can begin validation testing:

What goes in the folder

Same filenames as the before folder, saved to after. Where a filename starts with hostname, use that EdgeConnect's hostname.

Artifact	Where	Filename
Orchestrator active alarms	Alarms > Active	orch-alarms (export or screenshot)
Reachability	Monitoring > Reachability	reachability (export or screenshot)
NMS alarms and down devices	Enterprise NMS	nms-alarms, nms-down-devices
Tunnels - overlay	Configuration > Tunnels > Overlay	tunnels-report-overlay.csv
Tunnels - underlay	Configuration > Tunnels > Underlay	tunnels-report-underlay.csv
Tunnels - passthrough	Configuration > Tunnels > Passthrough	tunnels-report-passthrough.csv
Routes - Method 1 (all gateways)	Configuration > Routes	routes-report.csv
Routes - Method 2 (per gateway)	Configuration > Routes	hostname_routes_report.csv
BGP summary	Configuration > BGP > Summary	bgp-summary-report.csv
BGP peers	Configuration > BGP > Peers	bgp-peers-report.csv
OSPF state	Configuration > OSPF	ospf-report (export or screenshot)
Flows - hubs and critical spokes	Monitoring > Active & Recent Flows	hostname_flows.csv
Configuration backup	Administration > Backup Now	Held in Orchestrator, comment After outage (change control number)
Application test evidence	Flow details, app performance stats	hostname_app_flows.csv, screenshots

Orchestrator Alarms and Reachability

Navigate to: Alarms > Active
Export or screenshot, save to after as orch-alarms
Compare with the before capture
- Investigate unexpected alarms
- Limit this to one or two people to prevent clearing alarms that may be critical
Navigate to: Monitoring > Reachability
Note any "Not connected" EdgeConnect gateways - compare with before
Verify connected gateways are reachable (via both Orchestrator and Portal websockets)
Export or screenshot, save to after as reachability

Enterprise NMS Tools - State Capture

Remove maintenance mode from the devices you set before the window
Any down sites?
Any down devices?
Any new alarms?
Export or screenshot the state details, save to after as nms-alarms and nms-down-devices
Compare with before

Tunnel States

Edge Connect Route Verification

❗️
Follow the same method you chose before the window. Method #1 and Method #2 exports cannot be compared against each other.

Method #1 - Global report including all gateways (single CSV file)

Select all gateways in the navigation tree
Navigate to Configuration > Routes
Ensure "All" is selected and all filters are cleared
Choose "Export"
Save to after as routes-report.csv

Method #2 - Single report for each gateway (multiple CSVs)

Select one gateway in the navigation tree
Navigate to Configuration > Routes
Ensure "All" is selected and all filters are cleared
Choose "Export"
Save to after as hostname_routes_report.csv
Repeat for each gateway in the SD-WAN fabric

Compare the route tables

Once you have the routes captured you need to compare them. Depending on the size of your route tables the options are:

Use the Snapshot Sentinel. Drop the before and after routes exports on it and it lists the routes missing after, the routes new after, and the routes whose metric, state or zone changed, per appliance. It runs in your browser with no network, so download it before the window.
Manual comparison
1. Paste the before and after routes into the same Excel sheet
  1. Use the filter options to remove duplicates
  2. Do you expect the new routes you see?
2. Compare the raw number of routes
  1. Do the before and after match?
  2. Rarely is this exactly the same, but a difference of more than 5 routes should be investigated
Use an internal script to compare differences

❗️
What a CSV compare cannot see: the routes export drops the P/B (primary/backup) tag and the admin distance that the Routes page shows (GMS-46509). A prefix that flipped from primary to backup looks identical in the CSV. Spot-check P/B in the UI for the critical prefixes at hubs and critical spokes.

BGP and OSPF State Verification

Select all gateways in the navigation tree
Navigate to Configuration > BGP
Choose "Summary" and click "Export", save to after as bgp-summary-report.csv
Choose "Peers" and click "Export", save to after as bgp-peers-report.csv
Navigate to Configuration > OSPF
Export or screenshot the neighbor state, save to after as ospf-report
Compare with before - every peer and neighbor that was Established before should be Established now

Flow Table Snapshot (Hubs and Critical Spokes)

Active flow analysis

With no flow filter applied and Bytes set to "Total"
- Sort the flow table by bytes IN - note the number of flows with 0 bytes
- Sort the flow table by bytes OUT - note the number of flows with 0 bytes
- Do they match the before counts? Is any difference expected?

Configuration Backup

Select all appliances
Navigate to: Administration > Backup Now
Add comment "After outage (change control number)"
Click Backup
If you have an issue, use the configuration compare tool in Orchestrator to see what changed between the before and after backups

Test Applications for Function

Test all used applications for voice/video, or at least those "critical" to the organization. Compare each result against the baseline the testers recorded before the window.

💻
Teams, Zoom, Google, VoIP phones, etc.