# Plan TrueNAS HA network configuration from controller 1 to its peer > Review the Enterprise HA controller-one configuration and peer-sync sequence, rather than independently editing both controllers. - Canonical URL: https://update.dsesecurity.com/updates/plan-truenas-ha-network-configuration-from-controller-1-to-its-peer/ - Publisher: Detection Systems & Engineering (DSE Security) - Author: DSE Security Editorial Team - Published: 2026-10-30T06:04:36+00:00 - Modified: 2026-10-30T06:05:14+00:00 - Last reviewed by DSE: 2026-10-30 - Resource type: Guide - DSE priority: Advisory - Topics: Business Continuity, Networks & Infrastructure - Reading time: 3 minutes ## What you need to know Review the Enterprise HA controller-one configuration and peer-sync sequence, rather than independently editing both controllers. ## Potentially affected TrueNAS Enterprise HA systems following the 25.10 network-configuration guide. ## DSE recommendation Prepare both controllers, management addresses and the documented failover/synchronization sequence before editing HA networking. ## Article 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. ## Source fact: what the authority says The [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. ## What the source does not establish This 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. ## Applicability questions - Is this the documented Enterprise HA deployment and installed-release procedure? - Are both controller identities and readiness states established? - What virtual and per-controller management addresses are approved? - Who owns the failover-disable, controller-one edit and peer-sync maintenance sequence? ## DSE recommendation: controlled next steps The following steps are DSE recommendations based on the cited source. DSE 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. Plan 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. Write 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. Prepare 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. ## Verification and evidence Proposed 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. Check 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. ## Official references - [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. Source review completed October 30, 2026. Recheck the official documentation and deployment-specific applicability before a production change. ## Primary reference - Name: TrueNAS — Managing Network Settings (Enterprise HA) - Authority: www.truenas.com - URL: https://www.truenas.com/docs/scale/25.10/scaletutorials/network/managenetworksettingsha/ - Source publication date: Not stated by the source ## Citation and use Preferred citation: “Plan TrueNAS HA network configuration from controller 1 to its peer,” DSE Security, https://update.dsesecurity.com/updates/plan-truenas-ha-network-configuration-from-controller-1-to-its-peer/ 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.