NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
issue with GS308T connected with readynas 212 via LACP
I have issues with connecting my readynas 212 to switch GS308T via LACP.
At the moment I connect the readynas all other connection freezes and/or loses their connection to the internet.
I defined in my
READYNAS RN212:
BOND0 with teaming-mode: IEEE 802.3ad LACP with Hash Type: Layer 2+3
GS308T:
LAG-configuration: ReadyNAS ReadyNAS l1 Enabled 2 Src/Dest IP and TCP/UDP Port Fields Enable Enable LACP
LAG-membership: LAG-id l1 ; LAG-name: ReadyNAS ; ports 4 & 5 selected
What am I doing wrong, any help is appreciated
rgds Hans
see also attached PDF
thanks for your support, yesterday I started all over, disconnecting all cables etc... , during that process i noticed some cables were mixed up. After reconnecting and reconfigure the GS308T everything is working as it should.
So my issue is solved.
thx again.
4 Replies
Either we face a config issue, a problem with the LAG, wrong cabling - suspect some loop appears, or a port is shutdown.
Check it the GS308T does run on the current firmware - update to the latest one from https://www.netgear.com/support/product/GS308T.aspx#download
Double and tripple check the cabling and compare with the LAG ports configured.
Start with connecting one of the two LAG links. Access the switch, and check the LAG status again. At least one port should be a LG member.
Enable ssh root access in case it's not done already. Login using the root username and the (admin) password. Use (for example - assuming you are on a WIndows system) putty.
Check these and post:
root@RN212~# ifconfig -a
LeafNets Link encap:Ethernet ......
root@RN212:~# cat /proc/net/bonding/bond0
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...
The firmware of my GS308T is up-to-date
Model Name Boot Version Software Version GS308T 1.0.0.1 1.0.4.4 in the commands you proposed I see nothing strange, the commands are given at the moment the NAS is connected to a router (and not to the siwtch)
IFCONFIG -a gives:
root@Geldrop:~# ifconfig -a
bond0 Link encap:Ethernet HWaddr b0:b9:8a:5d:ce:f2
inet addr:192.168.1.130 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MASTER MULTICAST DYNAMIC MTU:1472 Metric:1
RX packets:11488654 errors:22 dropped:1337008 overruns:0 frame:27
TX packets:7720651 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:5006522075 (4.6 GiB) TX bytes:6258859308 (5.8 GiB)eth0 Link encap:Ethernet HWaddr b0:b9:8a:5d:ce:f2
UP BROADCAST RUNNING SLAVE MULTICAST MTU:1472 Metric:1
RX packets:9598419 errors:3 dropped:1828 overruns:0 frame:3
TX packets:7289494 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:511986373 (488.2 MiB) TX bytes:1864575003 (1.7 GiB)eth1 Link encap:Ethernet HWaddr b0:b9:8a:5d:ce:f2
UP BROADCAST RUNNING SLAVE MULTICAST MTU:1472 Metric:1
RX packets:524927 errors:15 dropped:823313 overruns:0 frame:19
TX packets:2770 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:34733465 (33.1 MiB) TX bytes:304700 (297.5 KiB)cat /proc/net/bonding/bond0 gives:
root@Geldrop:~# cat /proc/net/bonding/bond0
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): 0802.3ad info
LACP rate: slow
Min links: 1
Aggregator selection policy (ad_select): stable
System priority: 65535
System MAC address: b0:b9:8a:5d:ce:f2
Active Aggregator Info:
Aggregator ID: 3
Number of ports: 1
Actor Key: 9
Partner Key: 1
Partner Mac Address: 00:00:00:00:00:00Slave Interface: eth0
MII Status: up
Speed: 1000 Mbps
Duplex: full
Link Failure Count: 0
Permanent HW addr: b0:b9:8a:5d:ce:f2
Slave queue ID: 0
Aggregator ID: 3
Actor Churn State: none
Partner Churn State: churned
Actor Churned Count: 0
Partner Churned Count: 1
details actor lacp pdu:
system priority: 65535
system mac address: b0:b9:8a:5d:ce:f2
port key: 9
port priority: 255
port number: 1
port state: 77
details partner lacp pdu:
system priority: 65535
system mac address: 00:00:00:00:00:00
oper key: 1
port priority: 255
port number: 1
port state: 1Slave Interface: eth1
MII Status: up
Speed: 1000 Mbps
Duplex: full
Link Failure Count: 0
Permanent HW addr: b0:b9:8a:5d:ce:f3
Slave queue ID: 0
Aggregator ID: 4
Actor Churn State: churned
Partner Churn State: churned
Actor Churned Count: 1
Partner Churned Count: 1
details actor lacp pdu:
system priority: 65535
system mac address: b0:b9:8a:5d:ce:f2
port key: 9
port priority: 255
port number: 2
port state: 69
details partner lacp pdu:
system priority: 65535
system mac address: 00:00:00:00:00:00
oper key: 1
port priority: 255
port number: 1
port state: 1
HansRL wrote:
in the commands you proposed I see nothing strange, the commands are given at the moment the NAS is connected to a router (and not to the switch)
Lot of things odd or strange. Trouble is we don't know anything about the router links and config, even less when problems arised.
As requested, I suggest to test the LAG with the switch, start with one active link only. Reboot the NAS before so the strange errors on the LAG and the interfaces are reset.
Marking some oddities hitting my eyes ... but again, with just two links connected to the router (and I guess no LACP config there):
HansRL wrote:
root@Geldrop:~# ifconfig -a
bond0 Link encap:Ethernet HWaddr b0:b9:8a:5d:ce:f2
inet addr:192.168.1.130 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MASTER MULTICAST DYNAMIC MTU:1472 Metric:1
RX packets:11488654 errors:22 dropped:1337008 overruns:0 frame:27
TX packets:7720651 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:5006522075 (4.6 GiB) TX bytes:6258859308 (5.8 GiB)eth0 Link encap:Ethernet HWaddr b0:b9:8a:5d:ce:f2
UP BROADCAST RUNNING SLAVE MULTICAST MTU:1472 Metric:1
RX packets:9598419 errors:3 dropped:1828 overruns:0 frame:3
TX packets:7289494 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:511986373 (488.2 MiB) TX bytes:1864575003 (1.7 GiB)eth1 Link encap:Ethernet HWaddr b0:b9:8a:5d:ce:f2
UP BROADCAST RUNNING SLAVE MULTICAST MTU:1472 Metric:1
RX packets:524927 errors:15 dropped:823313 overruns:0 frame:19
TX packets:2770 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:34733465 (33.1 MiB) TX bytes:304700 (297.5 KiB)root@Geldrop:~# cat /proc/net/bonding/bond0
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): 0802.3ad info
LACP rate: slow
Min links: 1
Aggregator selection policy (ad_select): stable
System priority: 65535
System MAC address: b0:b9:8a:5d:ce:f2
Active Aggregator Info:
Aggregator ID: 3
Number of ports: 1
Actor Key: 9
Partner Key: 1
Partner Mac Address: 00:00:00:00:00:00Slave Interface: eth0
MII Status: up
Speed: 1000 Mbps
Duplex: full
Link Failure Count: 0
Permanent HW addr: b0:b9:8a:5d:ce:f2
Slave queue ID: 0
Aggregator ID: 3
Actor Churn State: none
Partner Churn State: churned
Actor Churned Count: 0
Partner Churned Count: 1
details actor lacp pdu:
system priority: 65535
system mac address: b0:b9:8a:5d:ce:f2
port key: 9
port priority: 255
port number: 1
port state: 77
details partner lacp pdu:
system priority: 65535
system mac address: 00:00:00:00:00:00
oper key: 1
port priority: 255
port number: 1
port state: 1Slave Interface: eth1
MII Status: up
Speed: 1000 Mbps
Duplex: full
Link Failure Count: 0
Permanent HW addr: b0:b9:8a:5d:ce:f3
Slave queue ID: 0
Aggregator ID: 4
Actor Churn State: churned
Partner Churn State: churned
Actor Churned Count: 1
Partner Churned Count: 1
details actor lacp pdu:
system priority: 65535
system mac address: b0:b9:8a:5d:ce:f2
port key: 9
port priority: 255
port number: 2
port state: 69
details partner lacp pdu:
system priority: 65535
system mac address: 00:00:00:00:00:00
oper key: 1
port priority: 255
port number: 1
port state: 1
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
