Right, to cut a long story short, I've got a 3-switch stack of 3750-24TS-1U switches, and need to change the default "system mtu routing 1500" to "system mtu jumbo 9000" (switch is dedicated iSCSI fabric for a Dell Powervault MD3200i, MTU of 9000 is best practice here for throughput).
Obviously I can run the command no problem, but this requires a reboot of the whole stack?
[FONT="]ISCSI-SWITCH(config)#system mtu jumbo 9000[/FONT]
[FONT="]Changes to the system jumbo MTU will not take effect until the next reload is done[/FONT]
[FONT="]ISCSI-SWITCH(config)#[/FONT]
[FONT="]ISCSI-SWITCH#copy run start
[/FONT][FONT="]Destination filename [startup-config]?[/FONT]
[FONT="]Building configuration...[/FONT]
[FONT="][OK][/FONT]
Can these be done one at a time? How do stacked switches handle their startup-configs in the event of being rebooted individually (using "reload slot x" command)? Will an individually reloaded stack-member switch take the running-config of the master, or come up with previously built and saved startup-config?
Cisco's documentation doesn't seem to cover the specifics of startup-configs for reloading individual slots, so I'm struggling to work out the impact of issuing the reload command.
Essentially I guess I'm trying to ask, can I maintain a degree of service availability by reloading 1 or 2 switches at a time? (all three are essentially redundant links for SAN > Host connectivity, so in essence, losing 2 of 3 switches should only result in bandwidth loss rather than downtime), or do I need to reload the stack as a whole?
As a side note, is there actually any benefit from these switches being in a stack? This whole reload process would have been simplified were they 3 individual switches, sure, the management would end up being negligibly more complex, but I can't help but think that them being stacked is a pointless exercise ?
Any help appreciated guys
Obviously I can run the command no problem, but this requires a reboot of the whole stack?
[FONT="]ISCSI-SWITCH(config)#system mtu jumbo 9000[/FONT]
[FONT="]Changes to the system jumbo MTU will not take effect until the next reload is done[/FONT]
[FONT="]ISCSI-SWITCH(config)#[/FONT]
[FONT="]ISCSI-SWITCH#copy run start
[/FONT][FONT="]Destination filename [startup-config]?[/FONT]
[FONT="]Building configuration...[/FONT]
[FONT="][OK][/FONT]
Cisco's documentation doesn't seem to cover the specifics of startup-configs for reloading individual slots, so I'm struggling to work out the impact of issuing the reload command.
Essentially I guess I'm trying to ask, can I maintain a degree of service availability by reloading 1 or 2 switches at a time? (all three are essentially redundant links for SAN > Host connectivity, so in essence, losing 2 of 3 switches should only result in bandwidth loss rather than downtime), or do I need to reload the stack as a whole?
As a side note, is there actually any benefit from these switches being in a stack? This whole reload process would have been simplified were they 3 individual switches, sure, the management would end up being negligibly more complex, but I can't help but think that them being stacked is a pointless exercise ?
Any help appreciated guys