Dave Genton
Contributor
- Joined
- Feb 27, 2014
- Messages
- 133
Wondering if anyone else is having issues with SSH on FreeNAS 9.3 Beta when using jumbo mtu ? My storage network is jumbo mtu's. I have multiple FreeNAS servers setup each with 2 NIC's live, one on management network with 1500 mtu and other on storage network with 9000 mtu. I was setting up replication but find that the ssh key scan fails when using the jumbo mtu network. I try to ssh between the boxes natively via shell and it also fails. If I set the NIC's back to 1500 between 2 of the 3 FreeNAS I can instantly SSH between them and of course complete the ssh key scan instantly. Is there something in SSH config that needs changed when using jumbo mtu or should I "let it slide" being a beta build ?? Being a data center network architect its common practice to use jumbo mtu on any isolated layer 2 vlan where data replication, iSCSI storage, etc. takes place but with freenas I've yet to see why ssh wont work when on 9000 mtu.
Also for FYI, I have been doing HEAVY data replication this week moving large amounts of data mostly just to stress the data center and also freenas 9.3 beta as I'm installing on 3 different networks currently. last night I had continuous replication failures I didn't have the last 3 nights prior on those builds. Again ssh says to be the culprit with either corrupted packet or stream being the error but the only change was the nightly build updates via the automated client. Then finally one of the 3 freenas boxes is sitting at a "db" prompt and it wont recover. Got notified a replication failed after about 400gig or so and in checking found one box console sitting at db>. did a reset, a reboot, nothing brings it back up. Power failed the box, returns to db.
Back to testing the two running boxes and replications appear to be flying by with reporting showing 800mbps network traffic and steady read/writes across all drives and no errors. This is of course after changing both storage nic's to 1500 from 9000 otherwise they dont talk at all. Any advice on box dropping dead to db prompt ?? Been doing this over 20 years and know networking and storage networking inside and out but admit I am not an expert on OS when it comes to Unix/BSD types, not new but not my area of expertise.
Boxes in lab have 16gb ram in 2, 32gb in 3rd, production box borrowed for testing, all use broadcom nic's, core i7 CPU's, all network switches are Cisco Systems being a Cisco Engineer :) So servers are using very little cpu but I can make them use most memory for cache and flood the NIC's between 800-900mbs with zero frame errors on network to be found although strangely detailed analysis is showing majority of frames being quite small in size despite attempts to make segments and frames larger.
Dave
Also for FYI, I have been doing HEAVY data replication this week moving large amounts of data mostly just to stress the data center and also freenas 9.3 beta as I'm installing on 3 different networks currently. last night I had continuous replication failures I didn't have the last 3 nights prior on those builds. Again ssh says to be the culprit with either corrupted packet or stream being the error but the only change was the nightly build updates via the automated client. Then finally one of the 3 freenas boxes is sitting at a "db" prompt and it wont recover. Got notified a replication failed after about 400gig or so and in checking found one box console sitting at db>. did a reset, a reboot, nothing brings it back up. Power failed the box, returns to db.
Back to testing the two running boxes and replications appear to be flying by with reporting showing 800mbps network traffic and steady read/writes across all drives and no errors. This is of course after changing both storage nic's to 1500 from 9000 otherwise they dont talk at all. Any advice on box dropping dead to db prompt ?? Been doing this over 20 years and know networking and storage networking inside and out but admit I am not an expert on OS when it comes to Unix/BSD types, not new but not my area of expertise.
Boxes in lab have 16gb ram in 2, 32gb in 3rd, production box borrowed for testing, all use broadcom nic's, core i7 CPU's, all network switches are Cisco Systems being a Cisco Engineer :) So servers are using very little cpu but I can make them use most memory for cache and flood the NIC's between 800-900mbs with zero frame errors on network to be found although strangely detailed analysis is showing majority of frames being quite small in size despite attempts to make segments and frames larger.
Dave