Re: aggr vs Nexus 3K
Sorry!, I was not attentive. in earlier oBSD versions, i think it was not necessary "up" in hostname.* configuration file when interface have IP address. if I add it to hostname.aggr0: trunkport oce0 trunkport oce1 172.20.253.12 netmask 255.255.255.255 description "." up LACP trunk is working! but interesting! hostname.trunk* is working without up! :) -- Üdvözlettel, Szél Gábor WanTax Kft. tel.: +36 20 3838 171 fax: +36 82 357 585 email: gabor.s...@wantax.hu web: http://wantax.hu web: http://halozatom.hu 2019. 11. 14. 17:45 keltezéssel, Szél Gábor írta: Yes of course! :) if aggr up, Nexus suspend port channel: "not receiving any LACP BPDUs suspending" If trunk up, nexus not suspend port channel. -- Üdvözlettel, Szél Gábor WanTax Kft. tel.: +36 20 3838 171 fax: +36 82 357 585 email:gabor.s...@wantax.hu web:http://wantax.hu web:http://halozatom.hu 2019. 11. 14. 17:35 keltezéssel, hrv...@srce.hr írta: Can you do ifconfig aggr1 up ... Is it active then? Dana 14. stu 2019. 04:51 PM osoba Szél Gábor napisala je: Dear @misc We want to try use aggr pseudo LACP device. We have a working setup with trunk interface: oBSD: hostname.trunk0 trunkproto lacp trunkport oce0 trunkport oce1 172.20.253.11 netmask 255.255.255.255 description "" trunk0: flags=8943 mtu 9000 lladdr 28:80:23:e0:ab:40 description: C1 LACP index 25 priority 0 llprio 3 trunk: trunkproto lacp trunk id: [(8000,28:80:23:e0:ab:40,40CD,,), (7F9B,00:23:04:ee:be:0a,8002,,)] trunkport oce1 active,collecting,distributing trunkport oce0 active,collecting,distributing groups: trunk media: Ethernet autoselect status: active inet 172.20.253.11 netmask 0x Nexus 3K: Cisco LACP|vPC config is very simple: interface Ethernet1/2 description FW2-oce1 switchport mode trunk channel-group 2 mode active interface port-channel2 speed 1 description FW2 switchport mode trunk vpc 2 lacp rate normal vPC domain id : 10 Peer status : peer adjacency formed ok vPC keep-alive status : peer is alive Configuration consistency status : success Per-vlan consistency status : success Type-2 consistency status : success vPC role : primary Number of vPCs configured : 8 Peer Gateway : Disabled Dual-active excluded VLANs : - Graceful Consistency Check : Enabled Auto-recovery status : Disabled vPC Peer-link status - id Port Status Active vlans -- -- -- 1 Po99 up 1-2,10,12-13,20,30,40,50-53,60,62,101 vPC status id Port Status Consistency Reason Active vlans -- --- -- --- -- --- 2 Po2 up success success 1-2,10,12-1 3,20,30,40, 50-53,60,62 ,101 If we change trunk driver to aggr driver: oBSD: hostname.aggr1 trunkport oce0 trunkport oce1 172.20.253.12 netmask 255.255.255.255 description "" LACP is not working: oce0: flags=8843 mtu 1500 lladdr fe:e1:ba:d0:cc:92 index 1 priority 0 llprio 3 trunk: trunkdev aggr1 media: Ethernet autoselect (10GbaseSR full-duplex,rxpause,txpause) status: active oce1: flags=8843 mtu 1500 lladdr fe:e1:ba:d0:cc:92 index 2 priority 0 llprio 3 trunk: trunkdev aggr1 media: Ethernet autoselect (10GbaseSR full-duplex,rxpause,txpause) status: active aggr1: flags=8802 mtu 1500 lladdr fe:e1:ba:d0:cc:92 description: C1 LACP index 7 priority 0 llprio 7 trunk: trunkproto lacp trunk id: [(8000,fe:e1:ba:d0:cc:92,0007,,), (,00:00:00:00:00:00,,,)] oce0 lacp actor system pri 0x8000 mac fe:e1:ba:d0:cc:92, key 0x7, port pri 0x8000 number 0x1 oce0 lacp actor state activity,aggregation,defaulted oce0 lacp partner system pri 0x0 mac 00:00:00:00:00:00, key 0x0, port pri 0x0 number 0x0 oce0 lacp partner state activity,sync oce0 port oce1 lacp actor system pri 0x8000 mac fe:e1:ba:d0:cc:92, key 0x7, port pri 0x8000 number 0x2 oce1 lacp actor state activity,aggregation,defaulted oce1 lacp partner system pri 0x0 mac 00:00:00:00:00:00, key 0x0, port pri 0x0 number 0x0
Re: SPAM: Re: aggr vs Nexus 3K
Yes of course! :) if aggr up, Nexus suspend port channel: "not receiving any LACP BPDUs suspending" If trunk up, nexus not suspend port channel. -- Üdvözlettel, Szél Gábor WanTax Kft. tel.: +36 20 3838 171 fax: +36 82 357 585 email: gabor.s...@wantax.hu web: http://wantax.hu web: http://halozatom.hu 2019. 11. 14. 17:35 keltezéssel, hrv...@srce.hr írta: Can you do ifconfig aggr1 up ... Is it active then? Dana 14. stu 2019. 04:51 PM osoba Szél Gábor napisala je: Dear @misc We want to try use aggr pseudo LACP device. We have a working setup with trunk interface: oBSD: hostname.trunk0 trunkproto lacp trunkport oce0 trunkport oce1 172.20.253.11 netmask 255.255.255.255 description "" trunk0: flags=8943 mtu 9000 lladdr 28:80:23:e0:ab:40 description: C1 LACP index 25 priority 0 llprio 3 trunk: trunkproto lacp trunk id: [(8000,28:80:23:e0:ab:40,40CD,,), (7F9B,00:23:04:ee:be:0a,8002,,)] trunkport oce1 active,collecting,distributing trunkport oce0 active,collecting,distributing groups: trunk media: Ethernet autoselect status: active inet 172.20.253.11 netmask 0x Nexus 3K: Cisco LACP|vPC config is very simple: interface Ethernet1/2 description FW2-oce1 switchport mode trunk channel-group 2 mode active interface port-channel2 speed 1 description FW2 switchport mode trunk vpc 2 lacp rate normal vPC domain id : 10 Peer status : peer adjacency formed ok vPC keep-alive status : peer is alive Configuration consistency status : success Per-vlan consistency status : success Type-2 consistency status : success vPC role : primary Number of vPCs configured : 8 Peer Gateway : Disabled Dual-active excluded VLANs : - Graceful Consistency Check : Enabled Auto-recovery status : Disabled vPC Peer-link status - id Port Status Active vlans -- -- -- 1 Po99 up 1-2,10,12-13,20,30,40,50-53,60,62,101 vPC status id Port Status Consistency Reason Active vlans -- --- -- --- -- --- 2 Po2 up success success 1-2,10,12-1 3,20,30,40, 50-53,60,62 ,101 If we change trunk driver to aggr driver: oBSD: hostname.aggr1 trunkport oce0 trunkport oce1 172.20.253.12 netmask 255.255.255.255 description "" LACP is not working: oce0: flags=8843 mtu 1500 lladdr fe:e1:ba:d0:cc:92 index 1 priority 0 llprio 3 trunk: trunkdev aggr1 media: Ethernet autoselect (10GbaseSR full-duplex,rxpause,txpause) status: active oce1: flags=8843 mtu 1500 lladdr fe:e1:ba:d0:cc:92 index 2 priority 0 llprio 3 trunk: trunkdev aggr1 media: Ethernet autoselect (10GbaseSR full-duplex,rxpause,txpause) status: active aggr1: flags=8802 mtu 1500 lladdr fe:e1:ba:d0:cc:92 description: C1 LACP index 7 priority 0 llprio 7 trunk: trunkproto lacp trunk id: [(8000,fe:e1:ba:d0:cc:92,0007,,), (,00:00:00:00:00:00,,,)] oce0 lacp actor system pri 0x8000 mac fe:e1:ba:d0:cc:92, key 0x7, port pri 0x8000 number 0x1 oce0 lacp actor state activity,aggregation,defaulted oce0 lacp partner system pri 0x0 mac 00:00:00:00:00:00, key 0x0, port pri 0x0 number 0x0 oce0 lacp partner state activity,sync oce0 port oce1 lacp actor system pri 0x8000 mac fe:e1:ba:d0:cc:92, key 0x7, port pri 0x8000 number 0x2 oce1 lacp actor state activity,aggregation,defaulted oce1 lacp partner system pri 0x0 mac 00:00:00:00:00:00, key 0x0, port pri 0x0 number 0x0 oce1 lacp partner state activity,sync oce1 port groups: aggr media: Ethernet autoselect status: no carrier inet 172.20.253.12 netmask 0x N3K logs: 2019 Nov 14 15:28:16 s1b %ETHPORT-5-SPEED: Interface Ethernet1/2, operational speed changed to 10 Gbps 2019 Nov 14 15:28:16 s1b %ETHPORT-5-IF_DUPLEX: Interface Ethernet1/2, operational duplex mode changed to Full 2019 Nov 14 15:28:16 s1b %ETHPORT-5-IF_RX_FLOW_CONTROL: Interface Ethernet1/2, operational Receive Flow Control state changed to off 2019 N
aggr vs Nexus 3K
Dear @misc We want to try use aggr pseudo LACP device. We have a working setup with trunk interface: oBSD: hostname.trunk0 trunkproto lacp trunkport oce0 trunkport oce1 172.20.253.11 netmask 255.255.255.255 description "" trunk0: flags=8943 mtu 9000 lladdr 28:80:23:e0:ab:40 description: C1 LACP index 25 priority 0 llprio 3 trunk: trunkproto lacp trunk id: [(8000,28:80:23:e0:ab:40,40CD,,), (7F9B,00:23:04:ee:be:0a,8002,,)] trunkport oce1 active,collecting,distributing trunkport oce0 active,collecting,distributing groups: trunk media: Ethernet autoselect status: active inet 172.20.253.11 netmask 0x Nexus 3K: Cisco LACP|vPC config is very simple: interface Ethernet1/2 description FW2-oce1 switchport mode trunk channel-group 2 mode active interface port-channel2 speed 1 description FW2 switchport mode trunk vpc 2 lacp rate normal vPC domain id : 10 Peer status : peer adjacency formed ok vPC keep-alive status : peer is alive Configuration consistency status : success Per-vlan consistency status : success Type-2 consistency status : success vPC role : primary Number of vPCs configured : 8 Peer Gateway : Disabled Dual-active excluded VLANs : - Graceful Consistency Check : Enabled Auto-recovery status : Disabled vPC Peer-link status - id Port Status Active vlans -- -- -- 1 Po99 up 1-2,10,12-13,20,30,40,50-53,60,62,101 vPC status id Port Status Consistency Reason Active vlans -- --- -- --- -- --- 2 Po2 up success success 1-2,10,12-1 3,20,30,40, 50-53,60,62 ,101 If we change trunk driver to aggr driver: oBSD: hostname.aggr1 trunkport oce0 trunkport oce1 172.20.253.12 netmask 255.255.255.255 description "" LACP is not working: oce0: flags=8843 mtu 1500 lladdr fe:e1:ba:d0:cc:92 index 1 priority 0 llprio 3 trunk: trunkdev aggr1 media: Ethernet autoselect (10GbaseSR full-duplex,rxpause,txpause) status: active oce1: flags=8843 mtu 1500 lladdr fe:e1:ba:d0:cc:92 index 2 priority 0 llprio 3 trunk: trunkdev aggr1 media: Ethernet autoselect (10GbaseSR full-duplex,rxpause,txpause) status: active aggr1: flags=8802 mtu 1500 lladdr fe:e1:ba:d0:cc:92 description: C1 LACP index 7 priority 0 llprio 7 trunk: trunkproto lacp trunk id: [(8000,fe:e1:ba:d0:cc:92,0007,,), (,00:00:00:00:00:00,,,)] oce0 lacp actor system pri 0x8000 mac fe:e1:ba:d0:cc:92, key 0x7, port pri 0x8000 number 0x1 oce0 lacp actor state activity,aggregation,defaulted oce0 lacp partner system pri 0x0 mac 00:00:00:00:00:00, key 0x0, port pri 0x0 number 0x0 oce0 lacp partner state activity,sync oce0 port oce1 lacp actor system pri 0x8000 mac fe:e1:ba:d0:cc:92, key 0x7, port pri 0x8000 number 0x2 oce1 lacp actor state activity,aggregation,defaulted oce1 lacp partner system pri 0x0 mac 00:00:00:00:00:00, key 0x0, port pri 0x0 number 0x0 oce1 lacp partner state activity,sync oce1 port groups: aggr media: Ethernet autoselect status: no carrier inet 172.20.253.12 netmask 0x N3K logs: 2019 Nov 14 15:28:16 s1b %ETHPORT-5-SPEED: Interface Ethernet1/2, operational speed changed to 10 Gbps 2019 Nov 14 15:28:16 s1b %ETHPORT-5-IF_DUPLEX: Interface Ethernet1/2, operational duplex mode changed to Full 2019 Nov 14 15:28:16 s1b %ETHPORT-5-IF_RX_FLOW_CONTROL: Interface Ethernet1/2, operational Receive Flow Control state changed to off 2019 Nov 14 15:28:16 s1b %ETHPORT-5-IF_TX_FLOW_CONTROL: Interface Ethernet1/2, operational Transmit Flow Control state changed to off 2019 Nov 14 15:28:16 s1b %ETHPORT-5-SPEED: Interface port-channel1, operational speed changed to 10 Gbps 2019 Nov 14 15:28:16 s1b %ETHPORT-5-IF_DUPLEX: Interface port-channel1, operational duplex mode changed to Full 2019 Nov 14 15:28:16 s1b %ETHPORT-5-IF_RX_FLOW_CONTROL: Interface port-channel1, operational Receive Flow Control state changed to off 2019 Nov 14 15:28:16 s1b %ETHPORT-5-IF_TX_FLOW_CONTROL: Interface port-channel1, operational Transmit Flow Control state changed to off 2019 Nov 14 15:28:26 s1b %LACP-5-LACP_SUSPEND_INDIVIDUAL: LACP port Ethernet1/2(0x1a00) of port-channel port-channel1(0x1600) not receiving any LACP BPDUs suspending (individual) port LACP interface status: Interface Ethernet1/2 is individual Channel group is 1 port chann