× Introducing the Orbi 970 Series Mesh System with WiFi 7 technology. For more information visit the NETGEAR Press Room.
Orbi WiFi 7 RBE973
Reply

Re: Netgear AX12 and CM1100 Port Aggregation

kc6108
Luminary

Re: Netgear AX12 and CM1100 Port Aggregation

Anyone familiar with setting up an LACP LAG between a QNAP NAS and Netgear switch?

 

@schumaku maybe?

Message 51 of 58
schumaku
Guru

Re: Netgear AX12 and CM1100 Port Aggregation


@kc6108 wrote:

Sorry, this is all I can help with as I'm not familiar with QNAP NAS's... only Synology NAS's.


Very similar - things need to be configured accordingly.

 


@kc6108 wrote:

Anyone familiar with setting up an LACP LAG between a QNAP NAS and Netgear switch? @schumaku maybe?


That might be a good guess 8-)

 

Let's see if  @jimlenz  confirms the LACP 802.3d LACP config on the four NAS GbE ports to start with. Can bring up a TVS-473 with a four port LAG on a MS510TX if required for a test.

Message 52 of 58
jimlenz
Aspirant

Re: Netgear AX12 and CM1100 Port Aggregation

I went into the NAS and setup port trunking with the 4 lan spots.  Once I rebooted, the NAS runs very slow and when I reboot it takes forever.  Obviously, something is wrong with the setup either from the NAS or switch side.  

 

When it diid finally login I tried to get back to the network section of control panel to change things back but it continues to say it is loading and wait.  

 

When I connect the Lan cables to the switch do they have to line up 1 to 1, 2 to 2 and so forth?  If so, that may be a problem but cant imagine it would be.  

 

I utilized these instructions to setup.

https://kb.netgear.com/000053557/How-do-I-set-up-a-static-LAG-between-a-Smart-Managed-Plus-Switch-an...

 

When I reboot and go into qfinder pro it says the NAS has entered an abnormal state and says to contact the system administrator.  I can never get to the login page.  Definitely something is wrong.  

 

Any advice is helpful.  

 

I tried to disconnect the other lan cables and onlly have #1 but continue to have the same problem.  When I disconnect from the switch and connect back into my router, everything is back to normal.

Message 53 of 58
schumaku
Guru

Re: Netgear AX12 and CM1100 Port Aggregation

Sequence doesn't matter. 

 

Operating a Virtual Switch or four native interfaces with the Port Trunking on QTS?

Message 54 of 58
schumaku
Guru

Re: Netgear AX12 and CM1100 Port Aggregation

I would opt for an LACP (803.3ad) trunk - obviously on both ends - instead of going for a static LAG with balanced-xor policy.

 


@jimlenz wrote:

I tried to disconnect the other lan cables and onlly have #1 but continue to have the same problem.  When I disconnect from the switch and connect back into my router, everything is back to normal.


This reads similar to the problems we're experiencing with the LAG on the two 10G ports.

 

 

Message 55 of 58
kc6108
Luminary

Re: Netgear AX12 and CM1100 Port Aggregation


@schumaku wrote:

This reads similar to the problems we're experiencing with the LAG on the two 10G ports.

 


That is exactly what I was thinking.

Message 56 of 58
schumaku
Guru

Re: Netgear AX12 and CM1100 Port Aggregation

Quickly set-up an LACP LAG over the four GbE ports g1..g4 on the MS510TX and the four GbE ports on a TVS-473:

 

MS510TX LACP LAG QTS 473.PNG

TVS-473 LACP LAG eth0-3.PNGTVS-473 LACP LAG 4 Gbps.PNG

 

[~] # cat /proc/net/bonding/bond*
Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)

Bonding Mode: IEEE 802.3ad Dynamic link aggregation
Transmit Hash Policy: layer2+3 (2)
MII Status: up
MII Polling Interval (ms): 100
Up Delay (ms): 0
Down Delay (ms): 0

802.3ad info
LACP rate: slow
Min links: 0
Aggregator selection policy (ad_select): stable
System priority: 65535
System MAC address: 24:5e:be:XX:XX.X2
Active Aggregator Info:
Aggregator ID: 4
Number of ports: 4
Actor Key: 9
Partner Key: 1000
Partner Mac Address: 10:XX:XX:XX:XX:55

Slave Interface: eth0
MII Status: up
Speed: 1000 Mbps
Duplex: full
Link Failure Count: 0
Permanent HW addr: 24:5e:be:XX:XX.X2
Slave queue ID: 0
Aggregator ID: 4
Actor Churn State: none
Partner Churn State: none
Actor Churned Count: 0
Partner Churned Count: 0
details actor lacp pdu:
system priority: 65535
system mac address: 24:5e:be:XX:XX.X2
port key: 9
port priority: 255
port number: 1
port state: 61
details partner lacp pdu:
system priority: 32768
system mac address: 10:XX:XX:XX:XX:55
oper key: 1000
port priority: 128
port number: 1
port state: 61

Slave Interface: eth1
MII Status: up
Speed: 1000 Mbps
Duplex: full
Link Failure Count: 0
Permanent HW addr: 24:5e:be:XX:XX.X3
Slave queue ID: 0
Aggregator ID: 4
Actor Churn State: none
Partner Churn State: none
Actor Churned Count: 0
Partner Churned Count: 0
details actor lacp pdu:
system priority: 65535
system mac address: 24:5e:be:XX:XX.X2
port key: 9
port priority: 255
port number: 2
port state: 61
details partner lacp pdu:
system priority: 32768
system mac address: 10:XX:XX:XX:XX:55
oper key: 1000
port priority: 128
port number: 2
port state: 61

Slave Interface: eth2
MII Status: up
Speed: 1000 Mbps
Duplex: full
Link Failure Count: 0
Permanent HW addr: 24:5e:be:XX:XX.X4
Slave queue ID: 0
Aggregator ID: 4
Actor Churn State: none
Partner Churn State: none
Actor Churned Count: 0
Partner Churned Count: 0
details actor lacp pdu:
system priority: 65535
system mac address: 24:5e:be:XX:XX.X2
port key: 9
port priority: 255
port number: 3
port state: 61
details partner lacp pdu:
system priority: 32768
system mac address: 10:XX:XX:XX:XX:55
oper key: 1000
port priority: 128
port number: 3
port state: 61

Slave Interface: eth3
MII Status: up
Speed: 1000 Mbps
Duplex: full
Link Failure Count: 0
Permanent HW addr: 24:5e:be:XX:XX.X5
Slave queue ID: 0
Aggregator ID: 4
Actor Churn State: none
Partner Churn State: none
Actor Churned Count: 0
Partner Churned Count: 0
details actor lacp pdu:
system priority: 65535
system mac address: 24:5e:be:XX:XX.X2
port key: 9
port priority: 255
port number: 4
port state: 61
details partner lacp pdu:
system priority: 32768
system mac address: 10:XX:XX:XX:XX:55
oper key: 1000
port priority: 128
port number: 4
port state: 61
Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)

 

 

Looks OK to me.

 

Message 57 of 58
schumaku
Guru

Re: Netgear AX12 and CM1100 Port Aggregation

 

04 May 2019 21:52:33 UTC+1:00%STP-W-PORTSTATUS: ch1 of instance 0: STP status Forwarding
04 May 2019 21:52:28 UTC+1:00%LINK-I-Up: ch1
04 May 2019 21:52:27 UTC+1:00%TRUNK-I-PORTADDED: Port g4 added to ch1
04 May 2019 21:52:27 UTC+1:00%TRUNK-I-PORTADDED: Port g3 added to ch1
04 May 2019 21:52:27 UTC+1:00%TRUNK-I-PORTADDED: Port g2 added to ch1
04 May 2019 21:52:27 UTC+1:00%TRUNK-I-PORTADDED: Port g1 added to ch1
04 May 2019 21:52:24 UTC+1:00%LINK-I-Up: g1
04 May 2019 21:52:23 UTC+1:00%LINK-I-Up: g2
04 May 2019 21:52:23 UTC+1:00%LINK-I-Up: g3
04 May 2019 21:52:22 UTC+1:00%LINK-I-Up: g4
Message 58 of 58
Top Contributors
Discussion stats
  • 57 replies
  • 11611 views
  • 5 kudos
  • 5 in conversation
Announcements

Orbi WiFi 7