Insights /Network Maintenance and Cutovers

How to replace a core switch with a rollback path: configuration and validation checklist for enterprise cutovers

Core-switch replacement is more than copying configuration. Verify VLANs, trunks, gateways, STP, link aggregation, optics, routing, ACLs, DHCP relay and uplink relationships, then execute staged validation with a defined rollback plan.

How to replace a core switch with a rollback path: configuration and validation checklist for enterprise cutovers
Key assessment

Establish a factual baseline with “VLAN, trunk and gateway inventory” and “STP root and protection settings”, then move to “link aggregation and LACP”. Use routing, policy, session state and real application traffic as the evidence chain and avoid changing production before the fault boundary is clear.

Risk boundaries and prerequisites

Start by checking VLAN, trunk and gateway inventory, STP root and protection settings and link aggregation and LACP independently. A healthy result for one of these checks does not establish the state of the entire service path.

Evidence and safe checks

CheckWhy it mattersRecommended action
01 · VLAN, trunk and gateway inventoryChecking VLAN, trunk and gateway inventory helps establish whether the complete request, response and return path matches the intended policy; compare it with a known-good baseline and the incident timeline.Record the actual state of VLAN, trunk and gateway inventory. Record VLAN, routes, firewall hits and DNS results and gather relevant logs using non-disruptive tests first.
02 · STP root and protection settingsChecking STP root and protection settings helps establish whether the complete request, response and return path matches the intended policy; compare it with a known-good baseline and the incident timeline.Record the actual state of STP root and protection settings. Record VLAN, routes, firewall hits and DNS results and gather relevant logs using non-disruptive tests first.
03 · link aggregation and LACPChecking link aggregation and LACP helps establish whether the complete request, response and return path matches the intended policy; compare it with a known-good baseline and the incident timeline.Record the actual state of link aggregation and LACP. Record VLAN, routes, firewall hits and DNS results and gather relevant logs using non-disruptive tests first.
04 · static and dynamic routingChecking static and dynamic routing helps establish whether the complete request, response and return path matches the intended policy; compare it with a known-good baseline and the incident timeline.Record the actual state of static and dynamic routing. Record VLAN, routes, firewall hits and DNS results and gather relevant logs using non-disruptive tests first.
05 · ACL, DHCP relay and management addressesChecking ACL, DHCP relay and management addresses helps establish whether the complete request, response and return path matches the intended policy; compare it with a known-good baseline and the incident timeline.Record the actual state of ACL, DHCP relay and management addresses. Record VLAN, routes, firewall hits and DNS results and gather relevant logs using non-disruptive tests first.
06 · optics, link state and physical rollbackChecking optics, link state and physical rollback helps establish whether the complete request, response and return path matches the intended policy; compare it with a known-good baseline and the incident timeline.Record the actual state of optics, link state and physical rollback. Record VLAN, routes, firewall hits and DNS results and gather relevant logs using non-disruptive tests first.

Investigation and change sequence

  1. Capture a baseline for VLAN, trunk and gateway inventory and STP root and protection settings and compare it with a known-good system.
  2. Correlate evidence from link aggregation and LACP and static and dynamic routing to distinguish the direct fault from dependent symptoms.
  3. Only if evidence points to ACL, DHCP relay and management addresses, plan a controlled change with backups, a change window and rollback triggers.
  4. Finally check optics, link state and physical rollback and the real business workflow. Verify end-to-end business access, return routing and error logs, with a defined rollback check.

Validation and rollback evidence

  • Verify end-to-end business access, return routing and error logs, with a defined rollback check.
  • Recheck ACL, DHCP relay and management addresses and optics, link state and physical rollback against the expected business outcome.
  • Retain initial configuration, event evidence, validation results and rollback triggers for production changes.

Common actions that increase risk

  • Assuming VLAN, trunk and gateway inventory is sufficient while overlooking STP root and protection settings and dependent checks.
  • Changing several settings before preserving the original evidence for link aggregation and LACP.
  • A successful port probe is not proof of application functionality; do not broaden access rules blindly.

Common questions and acceptance criteria

What should be checked first?

Begin with VLAN, trunk and gateway inventory and STP root and protection settings. Capture reproducible errors and protect recoverable data before changing production.

What proves the issue is resolved?

Verify end-to-end business access, return routing and error logs, with a defined rollback check.

What evidence should be retained?

Retain original logs, configuration snapshots, the approved change scope, business verification and rollback conditions.

PreviousHow should a factory network be redesigned? Segmenting office, production and server networks with VLANs and firewallsNextWhat is the risk of broad ANY firewall rules, and how can enterprises tighten them without breaking production?

Need an assessment for your actual environment?

Share the current topology, device models, system versions, symptoms, impact, maintenance windows and available configuration/backup information. We can first assess risk, scope and rollback needs, then define remote, on-site or project work.

Implementation reference

Related service and delivery evidence

For a production issue, confirm impact, recoverability and a verifiable rollback point before changing the environment.