Notice: Page may contain affiliate links for which we may earn a small commission through services like Amazon Affiliates or Skimlinks.
Interesting! I even remember a paragraph in the v8 manual that said something similar to this, it said something like "unplug or disable the ports on the other device while configuring a new LACP group or flapping may occur while the other device attempts to negotiate the LACP group before it has been fully defined on all interfaces"
Since it's clearly not a timing issue, I wonder why I can't make the flapping happen on v8.....I've tried it with a lot of random devices as of today and it just works.
Only thing I can think of.....how are you configuring the lacp? Are you adding the lacp commands to each interface one at a time? (Like int ethe 1, add link-aggregate commands, then ethe 2, add link-agg commands, etc)?
I'm setting them up by selecting all interfaces at once "int ethe 1 to 3", then putting in the lacp commands so they get added to each interface simultaneously...maybe that's why it's not flapping as there's no point where only half of it is configured?
Yes I did that too. Select all interfaces at all. I even rebooted the switch afterwards so it the config is on all ports but still the same issue. Note that it also flaps when I reboot the switch so it's definitely not a timing issue.
I have the feeling that spanning-tree could cause this because the port is in a BLOCKING state and then goes back to FORWARDING and I believe that it causing the flap. Do you have spanning tree enabled on your VLANs? However with the same configuration the V7 image works so I wonder if spanning-tree behaves different in the two versions. Even tried to disable spanning-tree and the port was still in a BLOCKING/FORWARDING state. Note sure if it still does that if spanning-tree is disabled.
Switch configuration:
Quanta configured as:
I have the feeling that spanning-tree could cause this because the port is in a BLOCKING state and then goes back to FORWARDING and I believe that it causing the flap. Do you have spanning tree enabled on your VLANs? However with the same configuration the V7 image works so I wonder if spanning-tree behaves different in the two versions. Even tried to disable spanning-tree and the port was still in a BLOCKING/FORWARDING state. Note sure if it still does that if spanning-tree is disabled.
Switch configuration:
Code:
global-stp
vlan 1 name DEFAULT-VLAN by port
spanning-tree
!
vlan 22 by port
tagged ethe 5 to 6
router-interface ve 22
spanning-tree
!
interface ethernet 5
link-aggregate configure timeout short
link-aggregate configure key 10000
link-aggregate active
link-error-disable 3 60 300
!
interface ethernet 6
link-aggregate configure key 10000
link-aggregate configure timeout short
link-aggregate active
Code:
interface 0/5
port lacptimeout actor short
port lacptimeout partner short
no lacp actor admin state longtimeout
lacp partner admin key 10000
no lacp partner admin state longtimeout
addport 1/2
exit
interface 0/6
port lacptimeout actor short
port lacptimeout partner short
no lacp actor admin state longtimeout
lacp partner admin key 10000
no lacp partner admin state longtimeout
addport 1/2
exit
interface 1/2
no port-channel static
vlan acceptframe vlanonly
vlan ingressfilter
vlan participation include 22
vlan tagging 22
exitI'm not using STP with LACP, but you said you turned off stp and it still happened? Did you remove all stp commands (including vlan and global stp commands and reboot for good measure). If so that definitely rules out stp. (Stp defaults to on in layer2 image, and off in layer3, so without stp commands it will be off for you).
This could very well be a bug in v8, but I want to find out why I can't make it happen. I guess I could just be lucky with the devices I have to test?
This could very well be a bug in v8, but I want to find out why I can't make it happen. I guess I could just be lucky with the devices I have to test?
Also I meant to ask this earlier: how'd you find out about the guide? Curious to where all these new sth members are coming from 
I found out about it from the homelab subredditAlso I meant to ask this earlier: how'd you find out about the guide? Curious to where all these new sth members are coming from
Simplified the SSH section of the quick guide, and added a new section on securing access to the switch as well as setting up key based ssh access - Brocade L3 Quick Guide - Brokeaids
in the next couple of days I'll add a section on the ACL's and how they can be used to secure/block access to the switch in a routed colo environment for example. Then will probably add LACP section as that seems to be the most used feature.
Any other suggestions of useful guide info to add? I think I've become addicted to writing technical documentation
will also try to further debug the v8 LACP flapping a couple people have seen without the short timeout command, I need to find a piece of gear that makes my switch flap
in the next couple of days I'll add a section on the ACL's and how they can be used to secure/block access to the switch in a routed colo environment for example. Then will probably add LACP section as that seems to be the most used feature.
Any other suggestions of useful guide info to add? I think I've become addicted to writing technical documentation
will also try to further debug the v8 LACP flapping a couple people have seen without the short timeout command, I need to find a piece of gear that makes my switch flap
Last edited:
dont know really.. maybe that's the right question.
so, there is web interface on brocade OS? 7 and 8 ?
The Turboiron does not support the Webinterface that is included in the Fastiron firmware. The web interface is for other ICX devices.
Hi,
Newbie alert here.
What does this command mean in the list of instructions :
"setenv ipaddr 192.168.1.50
setenv serverip 192.168.1.49"
Which workstation or server is the 2 referring to?
Is it normal for it to repeat loading over and over again, after inputing this command?
"tftpboot 0x100000 brocadeboot.bin"
I stopped right here in the flashing process as I am uncertain if I am doing something catastrophic
thanks!
Newbie alert here.
What does this command mean in the list of instructions :
"setenv ipaddr 192.168.1.50
setenv serverip 192.168.1.49"
Which workstation or server is the 2 referring to?
Is it normal for it to repeat loading over and over again, after inputing this command?
"tftpboot 0x100000 brocadeboot.bin"
I stopped right here in the flashing process as I am uncertain if I am doing something catastrophic
thanks!
The first is the IP Address you are assigning the switch.
The second is the IP Address of a TFTP server that is serving the brocadeboot.bin file.
You will need to setup a TFTP server so the switch can copy the file to memory.
Sent from my SM-N950U using Tapatalk