Bottom line: Plan the controller-one change and peer synchronization as one HA maintenance operation. Keep both controller identities and the virtual management address explicit before altering network settings.
\nThe TrueNAS 25.10 HA network guide applies only to Enterprise HA and requires both controllers powered on and ready. It requires disabling the failover service before network configuration and says to configure settings only on controller 1, then use Sync to Peer for controller 2. The HA design uses three static management addresses: one virtual IP and one address for each controller. The peer-sync procedure waits for controller 2 to be ready and includes a standby-controller reboot before settings are synchronized.
\nThis article concerns the Enterprise HA configuration ownership and synchronization sequence. It does not qualify a failover outcome or replace the installed-release procedure, support coordination and application maintenance plan.
\nThe following steps are DSE recommendations based on the cited source.
\nDSE recommends a maintenance diagram naming controller 1, controller 2 and the virtual management address before opening network configuration. Have the network and storage owners reconcile the physical controller identities and approved addresses together. Do not assume the currently viewed screen identifies the controller intended to own the change.
\nPlan the documented failover-service disablement and controller-one configuration as controlled steps with explicit readiness checkpoints. Use the installed-release instructions and applicable support guidance. Keep independent edits on the peer outside the proposed sequence; resolve any discrepancy in displayed controller state before continuing the maintenance operation.
\nWrite the peer-sync and standby-reboot stages into the service window rather than treating them as administrative cleanup. Assign an operator to observe controller 2 and record when the required ready state is actually reached. Keep an alternative management and recovery arrangement available through the approved support process.
\nPrepare harmless management and application observations with the relevant owners before the change. Separate acceptance of synchronized configuration from a separately authorized failover exercise. Preserve the original addresses and controller records, and agree a stopping condition for an unexpected peer state or loss of the intended management path.
\nProposed verification: compare the actual controller-one configuration, virtual address and individual controller addresses with the reviewed diagram. Observe the documented peer-readiness, reboot and synchronization stages in the authorized procedure, retaining real timestamps and status evidence. Stop on an unexplained state instead of repeating configuration independently on controller 2.
\nCheck management access through the approved paths and run the named harmless workload observations after synchronization. Have the owners review both controllers’ resulting configuration and unresolved warnings. Record any separately approved failover test as separate evidence; do not infer an availability guarantee merely from a completed synchronization action.
\nSource review completed October 30, 2026. Recheck the official documentation and deployment-specific applicability before a production change.
\n", "content_text": "Bottom line: Plan the controller-one change and peer synchronization as one HA maintenance operation. Keep both controller identities and the virtual management address explicit before altering network settings.\nSource fact: what the authority says\nThe TrueNAS 25.10 HA network guide applies only to Enterprise HA and requires both controllers powered on and ready. It requires disabling the failover service before network configuration and says to configure settings only on controller 1, then use Sync to Peer for controller 2. The HA design uses three static management addresses: one virtual IP and one address for each controller. The peer-sync procedure waits for controller 2 to be ready and includes a standby-controller reboot before settings are synchronized.\nWhat the source does not establish\nThis article concerns the Enterprise HA configuration ownership and synchronization sequence. It does not qualify a failover outcome or replace the installed-release procedure, support coordination and application maintenance plan.\nApplicability questions\n\nIs this the documented Enterprise HA deployment and installed-release procedure?\nAre both controller identities and readiness states established?\nWhat virtual and per-controller management addresses are approved?\nWho owns the failover-disable, controller-one edit and peer-sync maintenance sequence?\n\nDSE recommendation: controlled next steps\nThe following steps are DSE recommendations based on the cited source.\nDSE recommends a maintenance diagram naming controller 1, controller 2 and the virtual management address before opening network configuration. Have the network and storage owners reconcile the physical controller identities and approved addresses together. Do not assume the currently viewed screen identifies the controller intended to own the change.\nPlan the documented failover-service disablement and controller-one configuration as controlled steps with explicit readiness checkpoints. Use the installed-release instructions and applicable support guidance. Keep independent edits on the peer outside the proposed sequence; resolve any discrepancy in displayed controller state before continuing the maintenance operation.\nWrite the peer-sync and standby-reboot stages into the service window rather than treating them as administrative cleanup. Assign an operator to observe controller 2 and record when the required ready state is actually reached. Keep an alternative management and recovery arrangement available through the approved support process.\nPrepare harmless management and application observations with the relevant owners before the change. Separate acceptance of synchronized configuration from a separately authorized failover exercise. Preserve the original addresses and controller records, and agree a stopping condition for an unexpected peer state or loss of the intended management path.\nVerification and evidence\nProposed verification: compare the actual controller-one configuration, virtual address and individual controller addresses with the reviewed diagram. Observe the documented peer-readiness, reboot and synchronization stages in the authorized procedure, retaining real timestamps and status evidence. Stop on an unexplained state instead of repeating configuration independently on controller 2.\nCheck management access through the approved paths and run the named harmless workload observations after synchronization. Have the owners review both controllers’ resulting configuration and unresolved warnings. Record any separately approved failover test as separate evidence; do not infer an availability guarantee merely from a completed synchronization action.\nOfficial references\n\nTrueNAS — Managing Network Settings (Enterprise HA) — official product documentation; confirm the installed release and configuration.\n\nSource review completed October 30, 2026. Recheck the official documentation and deployment-specific applicability before a production change.", "content_markdown": "Bottom line: Plan the controller-one change and peer synchronization as one HA maintenance operation. Keep both controller identities and the virtual management address explicit before altering network settings.\n\n## Source fact: what the authority says\n\nThe [TrueNAS 25.10 HA network guide](https://www.truenas.com/docs/scale/25.10/scaletutorials/network/managenetworksettingsha/) applies only to Enterprise HA and requires both controllers powered on and ready. It requires disabling the failover service before network configuration and says to configure settings only on controller 1, then use Sync to Peer for controller 2. The HA design uses three static management addresses: one virtual IP and one address for each controller. The peer-sync procedure waits for controller 2 to be ready and includes a standby-controller reboot before settings are synchronized.\n\n## What the source does not establish\n\nThis article concerns the Enterprise HA configuration ownership and synchronization sequence. It does not qualify a failover outcome or replace the installed-release procedure, support coordination and application maintenance plan.\n\n## Applicability questions\n\n- Is this the documented Enterprise HA deployment and installed-release procedure?\n\n- Are both controller identities and readiness states established?\n\n- What virtual and per-controller management addresses are approved?\n\n- Who owns the failover-disable, controller-one edit and peer-sync maintenance sequence?\n\n## DSE recommendation: controlled next steps\n\nThe following steps are DSE recommendations based on the cited source.\n\nDSE recommends a maintenance diagram naming controller 1, controller 2 and the virtual management address before opening network configuration. Have the network and storage owners reconcile the physical controller identities and approved addresses together. Do not assume the currently viewed screen identifies the controller intended to own the change.\n\nPlan the documented failover-service disablement and controller-one configuration as controlled steps with explicit readiness checkpoints. Use the installed-release instructions and applicable support guidance. Keep independent edits on the peer outside the proposed sequence; resolve any discrepancy in displayed controller state before continuing the maintenance operation.\n\nWrite the peer-sync and standby-reboot stages into the service window rather than treating them as administrative cleanup. Assign an operator to observe controller 2 and record when the required ready state is actually reached. Keep an alternative management and recovery arrangement available through the approved support process.\n\nPrepare harmless management and application observations with the relevant owners before the change. Separate acceptance of synchronized configuration from a separately authorized failover exercise. Preserve the original addresses and controller records, and agree a stopping condition for an unexpected peer state or loss of the intended management path.\n\n## Verification and evidence\n\nProposed verification: compare the actual controller-one configuration, virtual address and individual controller addresses with the reviewed diagram. Observe the documented peer-readiness, reboot and synchronization stages in the authorized procedure, retaining real timestamps and status evidence. Stop on an unexplained state instead of repeating configuration independently on controller 2.\n\nCheck management access through the approved paths and run the named harmless workload observations after synchronization. Have the owners review both controllers’ resulting configuration and unresolved warnings. Record any separately approved failover test as separate evidence; do not infer an availability guarantee merely from a completed synchronization action.\n\n## Official references\n\n- [TrueNAS — Managing Network Settings (Enterprise HA)](https://www.truenas.com/docs/scale/25.10/scaletutorials/network/managenetworksettingsha/) — official product documentation; confirm the installed release and configuration.\n\nSource review completed October 30, 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-truenas-ha-network-configuration-from-controller-1-to-its-peer/", "url": "https://update.dsesecurity.com/updates/plan-truenas-ha-network-configuration-from-controller-1-to-its-peer/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-10-30" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/plan-truenas-ha-network-configuration-from-controller-1-to-its-peer/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Business Continuity", "item": "https://update.dsesecurity.com/topic/business-continuity/" }, { "@type": "ListItem", "position": 3, "name": "Plan TrueNAS HA network configuration from controller 1 to its peer", "item": "https://update.dsesecurity.com/updates/plan-truenas-ha-network-configuration-from-controller-1-to-its-peer/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/plan-truenas-ha-network-configuration-from-controller-1-to-its-peer/#article", "identifier": "https://update.dsesecurity.com/updates/plan-truenas-ha-network-configuration-from-controller-1-to-its-peer/", "url": "https://update.dsesecurity.com/updates/plan-truenas-ha-network-configuration-from-controller-1-to-its-peer/", "headline": "Plan TrueNAS HA network configuration from controller 1 to its peer", "description": "Review the Enterprise HA controller-one configuration and peer-sync sequence, rather than independently editing both controllers.", "abstract": "Review the Enterprise HA controller-one configuration and peer-sync sequence, rather than independently editing both controllers.", "articleBody": "Bottom line: Plan the controller-one change and peer synchronization as one HA maintenance operation. Keep both controller identities and the virtual management address explicit before altering network settings.\nSource fact: what the authority says\nThe TrueNAS 25.10 HA network guide applies only to Enterprise HA and requires both controllers powered on and ready. It requires disabling the failover service before network configuration and says to configure settings only on controller 1, then use Sync to Peer for controller 2. The HA design uses three static management addresses: one virtual IP and one address for each controller. The peer-sync procedure waits for controller 2 to be ready and includes a standby-controller reboot before settings are synchronized.\nWhat the source does not establish\nThis article concerns the Enterprise HA configuration ownership and synchronization sequence. It does not qualify a failover outcome or replace the installed-release procedure, support coordination and application maintenance plan.\nApplicability questions\n\nIs this the documented Enterprise HA deployment and installed-release procedure?\nAre both controller identities and readiness states established?\nWhat virtual and per-controller management addresses are approved?\nWho owns the failover-disable, controller-one edit and peer-sync maintenance sequence?\n\nDSE recommendation: controlled next steps\nThe following steps are DSE recommendations based on the cited source.\nDSE recommends a maintenance diagram naming controller 1, controller 2 and the virtual management address before opening network configuration. Have the network and storage owners reconcile the physical controller identities and approved addresses together. Do not assume the currently viewed screen identifies the controller intended to own the change.\nPlan the documented failover-service disablement and controller-one configuration as controlled steps with explicit readiness checkpoints. Use the installed-release instructions and applicable support guidance. Keep independent edits on the peer outside the proposed sequence; resolve any discrepancy in displayed controller state before continuing the maintenance operation.\nWrite the peer-sync and standby-reboot stages into the service window rather than treating them as administrative cleanup. Assign an operator to observe controller 2 and record when the required ready state is actually reached. Keep an alternative management and recovery arrangement available through the approved support process.\nPrepare harmless management and application observations with the relevant owners before the change. Separate acceptance of synchronized configuration from a separately authorized failover exercise. Preserve the original addresses and controller records, and agree a stopping condition for an unexpected peer state or loss of the intended management path.\nVerification and evidence\nProposed verification: compare the actual controller-one configuration, virtual address and individual controller addresses with the reviewed diagram. Observe the documented peer-readiness, reboot and synchronization stages in the authorized procedure, retaining real timestamps and status evidence. Stop on an unexplained state instead of repeating configuration independently on controller 2.\nCheck management access through the approved paths and run the named harmless workload observations after synchronization. Have the owners review both controllers’ resulting configuration and unresolved warnings. Record any separately approved failover test as separate evidence; do not infer an availability guarantee merely from a completed synchronization action.\nOfficial references\n\nTrueNAS — Managing Network Settings (Enterprise HA) — official product documentation; confirm the installed release and configuration.\n\nSource review completed October 30, 2026. Recheck the official documentation and deployment-specific applicability before a production change.", "datePublished": "2026-10-30T06:04:36+00:00", "dateModified": "2026-10-30T06:05:14+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/plan-truenas-ha-network-configuration-from-controller-1-to-its-peer/" }, "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-truenas-ha-network-configuration-from-controller-1-to-its-peer/#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 TrueNAS HA network configuration from controller 1 to its peer" }, "articleSection": [ "Business Continuity", "Networks & Infrastructure" ], "keywords": [ "Business Continuity", "Networks & Infrastructure", "Guide", "Advisory priority" ], "genre": "Guide", "about": [ { "@type": "Thing", "name": "Business Continuity", "url": "https://update.dsesecurity.com/topic/business-continuity/" }, { "@type": "Thing", "name": "Networks & Infrastructure", "url": "https://update.dsesecurity.com/topic/networks-infrastructure/" } ], "wordCount": 516, "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 — Managing Network Settings (Enterprise HA)", "url": "https://www.truenas.com/docs/scale/25.10/scaletutorials/network/managenetworksettingsha/" } } ] } }