Skip to main content
Question

Network behavior with Hardened Repo ISO

  • January 12, 2026
  • 4 comments
  • 25 views
G

Hi team

I was wondering if anyone has noticed some strange behavior when configuring network during ISO installer workflow?

I have done two installs now. When I go into the network portion and I select the connection toggle, it stays in the connecting state and eventually disconnects.
For one repo, one nic actually connected.

From a switch perspective, all is up and connected

I made the changes as per documentation

Installing from Veeam Hardened Repository ISO - Veeam Backup & Replication User Guide for VMware vSphere

For the repo that manages to connect to one nic, I configured LACP as per document but only with one nic. This got the repo on the network and I manually added added the second nic the bond from the CLI.

The second repo, in the network workflow, the two nic are discovered but are not connecting.
I ended up configuring one nic as an ethernet link. Then I created the LACP bond from the CLI and added the links manually. This worked.

So not sure why I am seeing this strange behavior. As it works when doing manually I assume there is something not right in installer?

I am using ISO 2.0.0.8 on 12.3.2

Cheers

    4 comments

    Link State
    Forum|alt.badge.img+11
    • Link State
    • Veeam Legend
    • January 12, 2026

    Hi ​@gravelrider 

    Hi, in my opinion there is no problem with the ISO. The problem is that the UI interface is fragile and unreliable during LACP configuration.
    LACP is stateful and timing-sensitive amd slight differences cause very different outcomes.
    Here are some possible causes of the abnormal behaviour; NIC enumeration order changed,
    one NIC negotiated faster, switch port already had cached LACP state, timing difference during boot.
    The recommended advice is always to skip network configuration in the UI entirely and configure everything via NMCLI post-install.
    Manual bonding is the real-world best practice.
    regards   

     

    Veeam: VMCA | VMCE | VMXP | Veeam Legend - Microsoft: MCITP | MCP | MCSA | 2008 R2 | 2012R2 | 2016 | MCSE Core Infrastructure | MCSE Cloud Platform - Azure: AZ900 | AZ104| AZ500|AZ305 - AWS Cloud Practitioner - VMWare: VCP-DCV Vsphere 7.x - Cisco: CCNA (Expired)
      coolsport00
      Forum|alt.badge.img+21
      • coolsport00
      • Veeam Legend
      • January 12, 2026

      Hi ​@gravelrider -

      I honestly haven’t played with the VHR ISO much, but generally...when I configure any networking within Linux, I do so as ​@Link State suggested (after install). I recommend trying that alternative route and see if it works. At the very least, you can ping Veeam Support and see if they’re able to replicate your configuratin behavior and see if there is a bug.

      Keep us posted.

      Best.

      Shane Williford - Veeam VMCA/VMCE | Veeam Legend | VUG Leader | VCP-DCV | Twitter: @coolsport00
        wolff.mateus
        Forum|alt.badge.img+11
        • wolff.mateus
        • Veeam Vanguard
        • January 12, 2026

        I have use VHR ISO with LACP with some environments and everything is working fine.

        Have you tried to configure the LACP on avanced network mode?

        This mode is more complete.

        IT Lover | Veeam Vanguard | VUG Leader | Blogger
          G
          • gravelrider
          • Author
          • Comes here often
          • January 12, 2026

          Thank you all. Yes, manual setup works fine. No biggie.
          Good to hear others have seen issues with the UI.

            Terms & ConditionsAccessibility statement