I have a new ReadyNAS 4220. I'm trying to bond all 4 1GbE NIC ports to a Cisco 3750G switch. I'm connecting to the management tool via the 10GbE port so the tool connectivity isn't affected by my tweaking.I have configured the 4 ports on the switch using the Cisco Network Assistant by going to the "Etherchannels.." menu, adding a group 1 and assigning port 3,4,5 and 6 to the group and configured all 4 as LACP.All 4 ports show green...suggesting they aren't disabled ;).When I go into the ReadyNAS configuration: - select "Network" tab - click eth0 and select "New Bond...". - I add eth1, eth2 and eth3 interfaces to the new group - select IEEE 802.3ad LACP - select Layer 2 - Click Create.The busy wheel starts spinning, the lights on the 3750 go orange for a bit then turn green.Now I don't have connectivity (can't find DHCP server). I change the IP address to static and configure the IP settings, but still no connectivity. I am unable to ping the interface. Before I bond them, I can ping it just fine.What setting am I missing?I bonded the two 10GbE ports to my Juniper EX4550 switch this same way and that seems to work. Thoughts?

Can you check what the groupstate is?What version of ReadyNAS OS is on the 4220?Have you contacted support? If so, have you got a case number?If you haven't got a support case open yet you could give support a call (faster) or if you prefer open an online case at my.netgear.comIf you could reproduce the problem, then download your logs and either attach it to your case (if opened online) or email them to me (http://kb.netgear.com/app/answers/detail/a_id/21543) that would be good.

Version is 6.1.8If groupstate is the channel-group or etherswitch group, then it is showing in the Cisco configuration as "Static Access" for both "Administrative Mode" and "Operational Mode" for VLAN 124 just like all the other ports.I hadn't opened a ticket yet. I will in the morning.I rewound and cleared all LACP, port groups and bonding from both the switch and the ReadyNAS. I rebooted both (actually powering them both off).I then brought the switch back up, and configured "EtherSwitch.." group 1 by adding port 3 - 6 in LACP mode.I then brought ReadyNAS back up, and configured the 4 interfaces individually with their own IP's and was able to ping all 4.I then created a new Bond1 group and added them in. The progress spinner has not gone away in 20 minutes after committing. However, if I open another browser window and go to networking, the Bond1 group shows up with all 4 NIC's in it. But I still can't ping the interface IP.I sent the logs I have, Thanks.

You may need to get someone who knows Cisco to have a look at your switch. It could be configured incorrectly or may even be incompatible.

Yeah, I was hoping to find someone on this forum that knows both the switch and ReadyNAS settings. No one at my work would know the nuances of ReadyNAS compatibility.

The ReadyNAS docs regarding Bonding modes lists:IEEE 802.3ad: This option requires the switch or router in front of the ReadyNAS to be configured for dynamic link aggregation – it will not work if the router/switch is configured for static link aggregationSo I'm wondering whether the 3750G supports "dynamic link aggregation" and how does that map to the Cisco terminology.When I create the Ethernchannel/port-channel, the modes on the 3750 that are available include:LACPLACP (Passive)DesirableAutoDesirable non-silentAuto non-silentOn(No LACP)None of the above seem to be specifically related to "static" vs "dynamic" link aggregation and my searches as to whether these switches support dynamic vs static aggregation have been unfruitful....so frustrating.

Bonding multiple NIC's w/ Cisco 3750

15 Replies

Replies have been turned off for this discussion

PredatorVI
Tutor
Jul 29, 2014
The 3750G we have does not have PoE. The actual model is Cisco Catalyst 3750G-48TS-48 and I believe is Layer2/3 capable. I've been attempting to configure Layer 2 LACP.

The ReadyNAS 4220 doesn't have a VLAN setting that I can find. My older ReadyNAS at home did, but I can't find it on this one. With teaming/bonding disabled it seems to work fine without explicit VLAN settings. The IP for that interface is statically assigned (10.131.24.6) for subnet 10.131.24.0/22. VLAN 124 on the switch as an IP configured as 10.131.24.2.

Port 1 on the switch is trunked to the MDF which routes VLAN 124 to this switch. The vtp mode is set to transparent.

Before attempting to bond/group the ports, all ports were configured as "mode access" and "allow vlan 124" which works just fine.

As for the config, I thought I saved the config so it would restore on reboot (of the switch) using `copy runtime-config startup-config` but to my knowledge it was not rebooted. Nevertheless, it was working until I changed some volume settings on the NAS and rebooted it.

I'll try to set the ip on the etherchannel tomorrow and give it a whirl.
xeltros
Apprentice
Jul 29, 2014
Can you do a "show vlans" or a "sh vlan-switch" just to see if the vlan 124 is effectively known by the switch and if VTP is well propagated.
You may also send some etherchannel show commands. show etherchannel port-channel for example or a show interface on the ether channel. to see if ports are taken into account.

I would think that everything needs to be on "access" and "trunk" only between switches.
http://www.cisco.com/c/en/us/td/docs/sw ... Trunk.html

Do you have some spare switch to test without impacting production devices ? You seem to have a pretty big network if a 48 ports 3750G is only secondary device... and using a spare switch and a clean config may eliminate some errors regarding the etherchannel config itself.
As far as I saw on google your config seems correct admitting your VTP and Vlans are set properly and that your cables are good too.

For the NAS, my bad, my UTM has a similar interface. I just checked and indeed readyNAS OS doesn't seem to have this setting.
PredatorVI
Tutor
Jul 30, 2014
I don't have a spare switch...I wish. :) Although as a last ditch attempt, I may reset the switch to factory defaults and start from scratch.

Although, I'm thinking it's a ReadyNAS bonding issue at this point. I tried to revert back to Bonding using "Transmit and Load Balancing" which supposedly requires NO special switch settings. I cleared all LACP/aggregation settings from the switch ports, verified they work unbonded. I then bond them, save settings and then Power Down/unplug/plug-in/poweron ReadyNAS, and nothing.

When the ReadyNAS documentation says that it only supports "dynamic link aggregation", what does that translate to in Cisco-speak?

I'll open a support ticket and see what falls out. I'd love to get using this thing to it's potential, but maybe I'll just have to use the interfaces individually.
xeltros
Apprentice
Jul 30, 2014
Cisco devices are pretty much as standard as you can get for network devices. 3750G is a potent device, I can't see any valid reason why a supported standard on both ends like LACP wouldn't work. On top of that I'm pretty sure the 4220 is classified as professional and thus is expected to handle many users via bonding but also support professional devices like Cisco's.

If they work unbound, yes, they should work bound with either TLB or ALB modes as far as I understand them.

Support is a good call, they at least can rule out a wrong NAS config and I wouldn't be surprised if they could find someone that knows how to handle your 3750G etherchannels better than I do in their ranks (they sell network products, chances are some of them got Cisco certifications at some point).
StephenB
Guru - Experienced User
Jul 30, 2014
Perhaps it is an interaction with another ethernet facility?

Does LACP work if you disable VLAN on the switch?

If you are using jumbo frames, then perhaps try disabling them.

Forum Discussion

Bonding multiple NIC's w/ Cisco 3750

15 Replies

Related Content

NIC Bonding on ReadyNAS

Setting up NIC Bonding through a non managed switch

RBR760 MULTIPLE ISSUES

Bonded MoCA 2.0

Bonding

NETGEAR Academy

ProSupport for Business