Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 2 replies
  • Subscribers 2 subscribers
  • Views 2866 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

LAG created using active LAN interface not coming online

BJohnson

Hello,

I've created a LAG between a UTM 9 and an SG500 Cisco switch.  All 4 ports are configured to advertise 1 Gbps link speed, and LACP is enabled on the Cisco switch.  Since I created the LAG using the active LAN interface on the UTM, do I need to shut down my network and toggle the LAN interface before the LAG will begin functioning properly?

Thanks,

Brian



This thread was automatically locked due to age.
  • 0

    Apparently, trying to create a LAG was a big mistake.  After I did so, the UTM elected to use only the port that I linked to the already-interface-bonded default network port, not both of them.  Subsequently, I attempted to "de-create" the LAG by unlinking that second port, and the UTM bricked my entire network.  After rushing from the office to find WiFi and get my network back up, the LAG still exists, still exhibiting the same useless behavior.

  • 0 in reply to BJohnson

    For future reference, for anyone using VLANs who is creating a LAG on the UTM and is not setting up the network for the very first time:

    First, dissociate all VLANs from the 2 ports that you are using.

    Next, create the LAG using your default LAN interface and the unused port.

    Then, reassociate all VLANs with the LAG.

    Whatever you do, if you decide to break up the LAG and you haven't dissociated the VLANs from the port you're using, UNCHECK THE ORIGINAL, DEFAULT LAN INTERFACE when you break up the LAG.  Otherwise, you will lose wired access to the UTM.  When I created the LAG the first time and assigned all of the VLANs to it, the LAG deactivated the original port and only used the port that was added, so when I broke it by unchecking the newer port, bad times.

     Cheers!

Unfiltered HTML