Changeing MTU size on bond requires restart?

Printable View

05-26-2009, 10:22 AM
budy

Changeing MTU size on bond requires restart?

Hi all,

I am playing a bit with different MTU sizes and it seems that I always have to restart my DSS once I change the MTU size of a bond, since the connection drops and won't come up again.

I have tried to disable/enable the bond with no success and restarting seems to be the only thing to get the connection going again?

Anybody can confirm this? And if yes, is this to be considered as a bug?

Cheers,
budy
05-26-2009, 11:57 AM
red

same issue here, although didnt try a restart - just went back to 1500, nic does support 9000
05-26-2009, 11:58 AM
red

Quote:

Originally Posted by red

same issue here, although didnt try a restart - just went back to 1500, nic does support 9000

open-e dss 3511
05-26-2009, 07:37 PM
budy

Ehh… yes - forgot to mention that as well.

Version: 5.0up60.7101.3511

Cheers,
budy
05-27-2009, 02:25 PM
To-M

Our engineers checked this on DSS Atlanta build 3513 and it works. Can you send logs to support using the Ticket number [ Zoom Ticket#: 1009134 ] FW: New Post/Thread Notification: DSS - Data Storage Server. So engineers can look into this.
05-28-2009, 07:09 AM
budy

Done.

Cheers,
budy
05-29-2009, 02:24 AM
tjk

Quote:

Originally Posted by To-M

Our engineers checked this on DSS Atlanta build 3513 and it works. Can you send logs to support using the Ticket number [ Zoom Ticket#: 1009134 ] FW: New Post/Thread Notification: DSS - Data Storage Server. So engineers can look into this.

Todd, is 3513 out or in beta/qa still?

Tom
05-29-2009, 03:49 AM
To-M

it's official so please download.
05-29-2009, 01:03 PM
tjk

Quote:

Originally Posted by To-M

it's official so please download.

Todd, 3513 isn't on the support web site for download - how can we obtain it?

Also, is there a documented process to update a pair of DSS systems running in failover mode?

Thanks,
Tom
05-29-2009, 02:09 PM
To-M

Update below from link - stop the replication process on both systems then update is the best or failover to the secondary and update the primary and so forth to the reverse.

ftp://software:enterforupdate@ftp.op...or_build_3511/
05-29-2009, 02:34 PM
mhubert

Error on update

Hi Todd!

I've tried the update from 3511 to 3513.
After reboot I get the following error:

Code:

Update in progress.... It may take several minutes. After update, the system will be automatically rebooted! THIS UPDATE IS FOR BUILD 3511 ONLY! UPDATE FAILED!!! The system will start the last working version after reboot. Press ENTER to continue

???

regards
Matthias
05-29-2009, 02:39 PM
To-M

I thought you already had the Atlanta version build 3511 as our engineers did not see a problem when changing the MTU size with this version of 3513.
05-30-2009, 02:15 PM
budy

Hi Todd,

I am having 3511 on both of my nodes. I will perform the update on one of my nodes on monday and report back.

Cheers,
budy
05-30-2009, 02:24 PM
budy

Uh, by the way - my Atlanta 3511 resides on a local hard drive. Will the update work an that as well. There had been issues before, you know.

Thanks,
budy
05-31-2009, 05:42 PM
budy

Hi all,

I have just updated both of my two Atlanta 3511 nodes to 3513 without a single problem.

Cheers,
budy