# Plan the TrueNAS LAGG test-and-save window before cutover > TrueNAS documents a timed Test Changes and Save Changes workflow for interfaces; prepare management recovery access before a LAGG cutover. - Canonical URL: https://update.dsesecurity.com/updates/plan-the-truenas-lagg-test-and-save-window-before-cutover/ - Publisher: Detection Systems & Engineering (DSE Security) - Author: DSE Security Editorial Team - Published: 2026-10-29T00:10:02+00:00 - Modified: 2026-10-29T00:10:35+00:00 - Last reviewed by DSE: 2026-10-28 - Resource type: Guide - DSE priority: Advisory - Topics: IT, Networks & Infrastructure - Reading time: 3 minutes ## What you need to know TrueNAS documents a timed Test Changes and Save Changes workflow for interfaces; prepare management recovery access before a LAGG cutover. ## Potentially affected TrueNAS 25.10 LAGG setup affecting management reachability; confirm the actual interface, switch plan and available console access. ## DSE recommendation DSE recommends rehearsing the timed network test-and-commit path with a prepared recovery connection before changing the management interface. ## Article Bottom line: Prepare how the administrator will reach and commit the new interface before starting the cutover. Keep the original session available and assign the person responsible for deciding whether to save or revert the test. ## Source fact: what the authority says The [TrueNAS LAGG setup guide](https://www.truenas.com/docs/scale/25.10/scaletutorials/network/interfaces/settinguplagg/) warns that changing the interface used by the WebGUI can lose management access and may require IPMI or a physical console to recover. It describes a 60-second network-change test period and allows changing the allotted time in the test workflow. The guide says Save Changes makes the configuration permanent; if the timer expires first, the prior settings return. For LACP, it requires the switch-side aggregation to be configured and active before TrueNAS negotiates the group. ## What the source does not establish The timed safeguard is not proof that a proposed network or switch configuration is correct. This article concerns management reachability and commit timing, rather than aggregate bandwidth. DSE keeps client-service acceptance and any dependency-specific precautions in the wider approved cutover plan. ## Applicability questions - Which current address and physical interface carry the management session? - What address, gateway and switch configuration are intended after the change? - Who can use the prepared console or other approved recovery connection? - What test duration and observations determine save, revert or escalation? ## DSE recommendation: controlled next steps The following steps are DSE recommendations based on the cited source. DSE recommends writing the old and proposed management endpoints side by side before entering settings. Assign one operator to the interface change and another to the independent reachability observation where staffing permits. Prepare the console route and protected configuration recovery material in advance. Resolve the switch-side plan before starting the timed portion of an LACP change. Rehearse the browser sequence with an approved representative setup. For a proposed successful case, keep the original session open, use a new window for the new endpoint, and identify exactly where the reviewer will commit the change. For a proposed unsuccessful case, agree when to allow reversion or use the documented revert control. Do not begin by closing the only known working management session. Choose the test window from the actual work rather than rushing to fit an assumed countdown. Include required workload precautions and a service observation plan in the authorized change. Keep the decision to retain the interface settings distinct from later application checks; an accessible login page is a useful checkpoint, not the complete service acceptance. Put the intended save decision and the fallback contact on the same cutover card. Confirm that the observer knows the selected test duration before starting. Keep elapsed-time observations with the outcome so an expired review window is not mistaken for a deliberately retained setting. ## Verification and evidence Proposed verification: record the configured test duration and observed management access at both old and proposed endpoints during the rehearsal. Capture the operator’s save or revert decision and the resulting interface state. If the intended endpoint cannot be reached, follow the prepared recovery path rather than repeatedly adding unrelated network changes. After the retained configuration is confirmed, perform the selected client-service checks and inspect the actual switch and interface assignments. Preserve timestamps, endpoint identifiers and redacted configuration evidence. Record any untested console route or missing service check as unresolved before relying on the cutover procedure for a live system. ## Official references - [TrueNAS — Setting Up a Link Aggregation](https://www.truenas.com/docs/scale/25.10/scaletutorials/network/interfaces/settinguplagg/) — official product documentation; confirm the installed release and configuration. Source review completed October 28, 2026. Recheck the official documentation and deployment-specific applicability before a production change. ## Primary reference - Name: TrueNAS — Setting Up a Link Aggregation - Authority: www.truenas.com - URL: https://www.truenas.com/docs/scale/25.10/scaletutorials/network/interfaces/settinguplagg/ - Source publication date: Not stated by the source ## Citation and use Preferred citation: “Plan the TrueNAS LAGG test-and-save window before cutover,” DSE Security, https://update.dsesecurity.com/updates/plan-the-truenas-lagg-test-and-save-window-before-cutover/ Publishing principles: https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/ Usage and citation policy: https://update.dsesecurity.com/usage/ Copyright © 2026 Detection Systems & Engineering. All rights reserved.