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.
\nThe TrueNAS LAGG setup guide 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.
\nThe 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.
\nThe following steps are DSE recommendations based on the cited source.
\nDSE 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.
\nRehearse 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.
\nChoose 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.
\nPut 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.
\nProposed 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.
\nAfter 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.
\nSource review completed October 28, 2026. Recheck the official documentation and deployment-specific applicability before a production change.
\n", "content_text": "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.\nSource fact: what the authority says\nThe TrueNAS LAGG setup guide 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.\nWhat the source does not establish\nThe 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.\nApplicability questions\n\nWhich current address and physical interface carry the management session?\nWhat address, gateway and switch configuration are intended after the change?\nWho can use the prepared console or other approved recovery connection?\nWhat test duration and observations determine save, revert or escalation?\n\nDSE recommendation: controlled next steps\nThe following steps are DSE recommendations based on the cited source.\nDSE 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.\nRehearse 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.\nChoose 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.\nPut 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.\nVerification and evidence\nProposed 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.\nAfter 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.\nOfficial references\n\nTrueNAS — Setting Up a Link Aggregation — official product documentation; confirm the installed release and configuration.\n\nSource review completed October 28, 2026. Recheck the official documentation and deployment-specific applicability before a production change.", "content_markdown": "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.\n\n## Source fact: what the authority says\n\nThe [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.\n\n## What the source does not establish\n\nThe 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.\n\n## Applicability questions\n\n- Which current address and physical interface carry the management session?\n\n- What address, gateway and switch configuration are intended after the change?\n\n- Who can use the prepared console or other approved recovery connection?\n\n- What test duration and observations determine save, revert or escalation?\n\n## DSE recommendation: controlled next steps\n\nThe following steps are DSE recommendations based on the cited source.\n\nDSE 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.\n\nRehearse 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.\n\nChoose 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.\n\nPut 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.\n\n## Verification and evidence\n\nProposed 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.\n\nAfter 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.\n\n## Official references\n\n- [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.\n\nSource review completed October 28, 2026. Recheck the official documentation and deployment-specific applicability before a production change." }, "json_ld": { "@context": "https://schema.org", "@graph": [ { "@type": "Organization", "@id": "https://dsesecurity.com/#organization", "name": "Detection Systems & Engineering", "alternateName": "DSE Security", "url": "https://dsesecurity.com/", "logo": { "@type": "ImageObject", "url": "https://update.dsesecurity.com/assets/dse-logo-20260812.png?v=1.8.20" } }, { "@type": "Organization", "@id": "https://update.dsesecurity.com/#editorial-team", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/", "parentOrganization": { "@id": "https://dsesecurity.com/#organization" } }, { "@type": "WebSite", "@id": "https://update.dsesecurity.com/#website", "name": "DSE Updates", "alternateName": "DSE Security Knowledge Hub", "url": "https://update.dsesecurity.com/", "inLanguage": "en-US", "publisher": { "@id": "https://dsesecurity.com/#organization" }, "potentialAction": { "@type": "SearchAction", "target": { "@type": "EntryPoint", "urlTemplate": "https://update.dsesecurity.com/?q={search_term_string}" }, "query-input": "required name=search_term_string" } }, { "@type": "WebPage", "@id": "https://update.dsesecurity.com/updates/plan-the-truenas-lagg-test-and-save-window-before-cutover/", "url": "https://update.dsesecurity.com/updates/plan-the-truenas-lagg-test-and-save-window-before-cutover/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-10-28" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/plan-the-truenas-lagg-test-and-save-window-before-cutover/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "IT", "item": "https://update.dsesecurity.com/topic/it/" }, { "@type": "ListItem", "position": 3, "name": "Plan the TrueNAS LAGG test-and-save window before cutover", "item": "https://update.dsesecurity.com/updates/plan-the-truenas-lagg-test-and-save-window-before-cutover/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/plan-the-truenas-lagg-test-and-save-window-before-cutover/#article", "identifier": "https://update.dsesecurity.com/updates/plan-the-truenas-lagg-test-and-save-window-before-cutover/", "url": "https://update.dsesecurity.com/updates/plan-the-truenas-lagg-test-and-save-window-before-cutover/", "headline": "Plan the TrueNAS LAGG test-and-save window before cutover", "description": "TrueNAS documents a timed Test Changes and Save Changes workflow for interfaces; prepare management recovery access before a LAGG cutover.", "abstract": "TrueNAS documents a timed Test Changes and Save Changes workflow for interfaces; prepare management recovery access before a LAGG cutover.", "articleBody": "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.\nSource fact: what the authority says\nThe TrueNAS LAGG setup guide 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.\nWhat the source does not establish\nThe 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.\nApplicability questions\n\nWhich current address and physical interface carry the management session?\nWhat address, gateway and switch configuration are intended after the change?\nWho can use the prepared console or other approved recovery connection?\nWhat test duration and observations determine save, revert or escalation?\n\nDSE recommendation: controlled next steps\nThe following steps are DSE recommendations based on the cited source.\nDSE 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.\nRehearse 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.\nChoose 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.\nPut 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.\nVerification and evidence\nProposed 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.\nAfter 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.\nOfficial references\n\nTrueNAS — Setting Up a Link Aggregation — official product documentation; confirm the installed release and configuration.\n\nSource review completed October 28, 2026. Recheck the official documentation and deployment-specific applicability before a production change.", "datePublished": "2026-10-29T00:10:02+00:00", "dateModified": "2026-10-29T00:10:35+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/plan-the-truenas-lagg-test-and-save-window-before-cutover/" }, "inLanguage": "en-US", "isAccessibleForFree": true, "author": { "@type": "Organization", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team" }, "publisher": { "@id": "https://dsesecurity.com/#organization" }, "image": { "@type": "ImageObject", "@id": "https://update.dsesecurity.com/updates/plan-the-truenas-lagg-test-and-save-window-before-cutover/#primaryimage", "url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20", "contentUrl": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20", "width": 1200, "height": 630, "caption": "Plan the TrueNAS LAGG test-and-save window before cutover" }, "articleSection": [ "IT", "Networks & Infrastructure" ], "keywords": [ "IT", "Networks & Infrastructure", "Guide", "Advisory priority" ], "genre": "Guide", "about": [ { "@type": "Thing", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" }, { "@type": "Thing", "name": "Networks & Infrastructure", "url": "https://update.dsesecurity.com/topic/networks-infrastructure/" } ], "wordCount": 583, "timeRequired": "PT3M", "publishingPrinciples": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usageInfo": "https://update.dsesecurity.com/usage/", "copyrightHolder": { "@id": "https://dsesecurity.com/#organization" }, "copyrightNotice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "citation": { "@type": "CreativeWork", "name": "TrueNAS — Setting Up a Link Aggregation", "url": "https://www.truenas.com/docs/scale/25.10/scaletutorials/network/interfaces/settinguplagg/" } } ] } }