From owner-freebsd-questions@freebsd.org Tue Oct 6 21:58:17 2015 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BC0D99D178A for ; Tue, 6 Oct 2015 21:58:17 +0000 (UTC) (envelope-from dean_forester@hotmail.com) Received: from SNT004-OMC4S14.hotmail.com (snt004-omc4s14.hotmail.com [65.55.90.217]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "*.outlook.com", Issuer "MSIT Machine Auth CA 2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7A4C9FE1 for ; Tue, 6 Oct 2015 21:58:17 +0000 (UTC) (envelope-from dean_forester@hotmail.com) Received: from SNT148-W14 ([65.55.90.199]) by SNT004-OMC4S14.hotmail.com over TLS secured channel with Microsoft SMTPSVC(7.5.7601.23008); Tue, 6 Oct 2015 14:57:10 -0700 X-TMN: [tH9KV/ht40fb/W4oVO0NGmGPzQZkIsxi] X-Originating-Email: [dean_forester@hotmail.com] Message-ID: From: Dean Forester To: "freebsd-questions@freebsd.org" Subject: RE: FreeBSD 10.2 - LAGG interfaces "possible flapping" during shutdown Date: Tue, 6 Oct 2015 17:57:10 -0400 Importance: Normal In-Reply-To: References: MIME-Version: 1.0 X-OriginalArrivalTime: 06 Oct 2015 21:57:10.0541 (UTC) FILETIME=[F36F8BD0:01D10081] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Oct 2015 21:58:17 -0000 Hi=2C Just in case it has an effect on things I have also included the switch sid= e of the configuration below: # version 5.20=2C Release 1513P89# sysname HP_V1910-24G-PoE#vlan 1 arp dete= ction enable#vlan 101 description MGMT VLAN - 192.168.1.0/24 arp detection = enable#vlan 102 description VLAN 102 - 192.168.2.0/24 arp detection enable#= vlan 103 description VLAN 103 - 192.168.3.0/24 arp detection enable#interfa= ce Vlan-interface1 ip address 192.168.0.3 255.255.255.0 #interface Vlan-int= erface101 ip address 192.168.1.3 255.255.255.0 #interface Vlan-interface102= ip address 192.168.2.3 255.255.255.0 #interface Vlan-interface103 ip addre= ss 192.168.3.3 255.255.255.0 #interface Bridge-Aggregation2 port link-type = hybrid port hybrid vlan 101 to 103 tagged port hybrid vlan 1 untagged link-= aggregation mode dynamic arp detection trust#interface GigabitEthernet1/0/5= port link-type hybrid port hybrid vlan 101 to 103 tagged port hybrid vlan = 1 untagged stp edged-port enable port link-aggregation group 2#interface Gi= gabitEthernet1/0/6 port link-type hybrid port hybrid vlan 101 to 103 tagged= port hybrid vlan 1 untagged stp edged-port enable port link-aggregation gr= oup 2#interface GigabitEthernet1/0/7 port link-type hybrid port hybrid vlan= 101 to 103 tagged port hybrid vlan 1 untagged stp edged-port enable port l= ink-aggregation group 2#interface GigabitEthernet1/0/8 port link-type hybri= d port hybrid vlan 101 to 103 tagged port hybrid vlan 1 untagged stp edged-= port enable port link-aggregation group 2# The view of the LAGG from the system side:root@Pine:~ # ifconfig lagg1=0A= lagg1: flags=3D8843 metric = 0 mtu 1500=0A= options=3D403bb=0A= ether a0:36:9f:64:6d:d5=0A= nd6 options=3D29=0A= media: Ethernet autoselect=0A= status: active=0A= laggproto lacp lagghash l2=2Cl3=2Cl4=0A= laggport: igb1 flags=3D1c=0A= laggport: igb4 flags=3D1c=0A= laggport: igb7 flags=3D1c=0A= laggport: igb8 flags=3D1c The one thing that I just noticed is that I have VLAN 1 untagged on the Bri= dge Aggregate 2 but I can't see how that would cause this affect. My assump= tion is that the LAGG interface is being shutdown but the four ethernet por= ts are not=3B therefore the kernel notices traffic on all four ports and co= mplains. With this same server I also have another LAGG setup that is going= to a Cisco SG200-26 switch (which carries VLAN 104 and VLAN 105) with the = same issue. All 8 interfaces show up during the shutdown after the Uptime m= essage with the Interface stopped DISTRIBUTING=2C possible flapping issue. My main concern at this point is how can I do a complete system reboot from= remote without it hanging with no access to the power button or console. Regards=2C Dean From: dean_forester@hotmail.com To: freebsd-questions@freebsd.org Subject: FreeBSD 10.2 - LAGG interfaces "possible flapping" during shutdown Date: Tue=2C 6 Oct 2015 12:28:01 -0400 =0A= =0A= =0A= Hi I am having an issue with a new FreeBSD 10.2-RELEASE system when using LAGG= s. Everything works fine until I try to do a reboot of the system. With thi= s issue the system does a shutdown but reports an error with the interfaces= that belong to the LAGG (which also have VLANs define) and then halts=2C i= t will not reboot=3B a power cycle is required. root@Pine:~ # uname -a FreeBSD Pine.local 10.2-RELEASE FreeBSD 10.2-RELEASE #0 r286666: Wed Aug 12= 15:26:37 UTC 2015 root@releng1.nyi.freebsd.org:/usr/obj/usr/src/sys/GE= NERIC amd64 /etc/rc.conf: if_vlan_load=3D"YES" # HP V1910-24G Switch Trunk ifconfig_igb1=3D"up mtu 1500" ifconfig_igb4=3D"up mtu 1500" ifconfig_igb7=3D"up mtu 1500" ifconfig_igb8=3D"up mtu 1500" # Setup new Virtual Interfaces cloned_interfaces=3D"lagg1 vlan101 vlan102 vlan103" # LAGG Configuration ifconfig_lagg1=3D"laggproto lacp laggport igb1 laggport igb4 laggport igb7 = laggport igb8" # Setup VLANs ifconfig_vlan101=3D"inet 192.168.1.208/24 vlan 101 vlandev lagg1" ifconfig_vlan102=3D"inet 192.168.2.208/24 vlan 102 vlandev lagg1" ifconfig_vlan103=3D"inet 192.168.3.208/24 vlan 103 vlandev lagg1" # Setup extra IPs for Layer 3 Load Balancing ifconfig_vlan101_aliases=3D"inet 192.168.1.209/32" ifconfig_vlan102_aliases=3D"inet 192.168.2.209/32" ifconfig_vlan103_aliases=3D"inet 192.168.3.209/32" Errors on shutdown -r now =0A= =0A= Uptime: 3d20h44m15sigb8: Interface stopped DISTRIBUTING=2C=0A= possible flappingigb1: Interface stopped DISTRIBUTING=2C=0A= possible flapping=0A= =0A= igb7: Interface stopped DISTRIBUTING=2C=0A= possible flapping=0A= =0A= igb4: Interface stopped DISTRIBUTING=2C=0A= possible flapping=0A= =0A= =0A= =0A= =0A= =0A= Has anyone else run into this behavior with LAGGs and VLANs? Any help would= greatly be appreciated. Regards=2C Dean Forester dean_forester@hotmail.com =