LACP with SR2208P via Supplemental CLI and fixed IP requirement

  • 1
  • Question
  • Updated 11 months ago
We have managed to configure several SR2208P switches for link aggregation with LACP, via Supplemental CLI, and it is working.

BUT: We had to assign the switch a static IP address. With management IP via DHCP the link aggregation would still go up, but then the switch loses its IP (displayed with 0.0.0.0).

Can anyone confirm that this is the case, and why? And if it's maybe a known bug?

Here is our CLI configuration for LACP:

enable
configure
port-channel name lag 1 UPLINK
interface lag 1
switchport mode trunk
no port-channel static
exit
interface 1/0/9
addport lag 1
exit
interface 1/0/10
addport lag 1
exit
exit
Photo of Carsten Buchenau

Carsten Buchenau, Champ

  • 356 Posts
  • 117 Reply Likes

Posted 1 year ago

  • 1
Photo of BJ

BJ, Champ

  • 374 Posts
  • 45 Reply Likes
Carsten, you have made more progress on LACP integration than I have been able. I can confirm that dhcp has indeed failed. Does anyone from Aerohive have a timeline on documentation for LACP integration yet? 
Photo of Carsten Buchenau

Carsten Buchenau, Champ

  • 356 Posts
  • 117 Reply Likes
No, unfortunately not.

My guess (and hope) is that the error is on the HiveAgent side, not the underlying Fastpath OS, which means that it is on Aerohive's side to fix it. When we were working on getting those switches into our NGVM, we had massive issues which were finally fixed with the latest HiveAgent - so I hope a newer update will fix this issue as well. Need to try again one day :-)

carsten