Wired Intelligent Edge

Hello,

we are using two 6300M switches with VSF configuration (ring topology)
we would like to upgrade the (old) firmware FL.10.09.1020 to firmware FL.10.13.1101

as I have never updated a VSF cluster myself I wanted to ask you which procedure is the right one here with as little downtime as possible. Thanks!

kind regards,

Juergen N.

Since 10.9 is a Short Support Release (SSR) it's generally recommended to not upgrade more than 2 major versions at a time (ie. 10.9 to 10.11 and then 10.11 to 10.13).  However 10.13 is a Long Support Release (LSR) and going from one LSR to the next is also supported and (in my opinion) is generally more stable. The next LSR after 10.9 is 10.10 so what I would do is upgrade to 10.10 and then upgrade to 10.13.

The actual upgrade process is pretty straight forward.

1. Backup your config
2. Upload the new firmware to whichever flash partition you're not currently using (you're currently booted from primary so upload to secondary)
3. (optionally) Run the command allow-unsafe-updates 30
4. Boot to the partition where you uploaded your new firmware.

VSF will take care of copying the firmware to all the members and rebooting them.  From your perspective it's no different than upgrading a standalone switch.  Keep in mind that VSF does not have live upgrades so both members will reboot at the same time and network service will be interrupted.

The optional unsafe updates command will allow the switch to upgrade things like the boot ROM and serviceOS firmware.  These are important things to update BUT they make the reboot take longer and if you lose power during them the hardware may be unable to boot.

Hello,

we are using two 6300M switches with VSF configuration (ring topology)
we would like to upgrade the (old) firmware FL.10.09.1020 to firmware FL.10.13.1101

as I have never updated a VSF cluster myself I wanted to ask you which procedure is the right one here with as little downtime as possible. Thanks!

kind regards,

Juergen N.

Hello davidwk,

thanks for then answer, very useful! So there is no possibility without downtime as both devices restart at the same time ...
I thought that with this configuration would be possible

I have already performed an update on all the other standalone switches (6000/6100) to 10.13 with the command "allow-unsafe-udpates". As we have an UPS for the main switches (6300M), possible power interruptions should not be a problem.

Since 10.9 is a Short Support Release (SSR) it's generally recommended to not upgrade more than 2 major versions at a time (ie. 10.9 to 10.11 and then 10.11 to 10.13).  However 10.13 is a Long Support Release (LSR) and going from one LSR to the next is also supported and (in my opinion) is generally more stable. The next LSR after 10.9 is 10.10 so what I would do is upgrade to 10.10 and then upgrade to 10.13.

The actual upgrade process is pretty straight forward.

1. Backup your config
2. Upload the new firmware to whichever flash partition you're not currently using (you're currently booted from primary so upload to secondary)
3. (optionally) Run the command allow-unsafe-updates 30
4. Boot to the partition where you uploaded your new firmware.

VSF will take care of copying the firmware to all the members and rebooting them.  From your perspective it's no different than upgrading a standalone switch.  Keep in mind that VSF does not have live upgrades so both members will reboot at the same time and network service will be interrupted.

The optional unsafe updates command will allow the switch to upgrade things like the boot ROM and serviceOS firmware.  These are important things to update BUT they make the reboot take longer and if you lose power during them the hardware may be unable to boot.

Hello,

we are using two 6300M switches with VSF configuration (ring topology)
we would like to upgrade the (old) firmware FL.10.09.1020 to firmware FL.10.13.1101

as I have never updated a VSF cluster myself I wanted to ask you which procedure is the right one here with as little downtime as possible. Thanks!

kind regards,

Juergen N.

Yeah, that's the downside of VSF.  Updates always result in downtime.

Hello davidwk,

thanks for then answer, very useful! So there is no possibility without downtime as both devices restart at the same time ...
I thought that with this configuration would be possible

I have already performed an update on all the other standalone switches (6000/6100) to 10.13 with the command "allow-unsafe-udpates". As we have an UPS for the main switches (6300M), possible power interruptions should not be a problem.

Since 10.9 is a Short Support Release (SSR) it's generally recommended to not upgrade more than 2 major versions at a time (ie. 10.9 to 10.11 and then 10.11 to 10.13).  However 10.13 is a Long Support Release (LSR) and going from one LSR to the next is also supported and (in my opinion) is generally more stable. The next LSR after 10.9 is 10.10 so what I would do is upgrade to 10.10 and then upgrade to 10.13.

The actual upgrade process is pretty straight forward.

1. Backup your config
2. Upload the new firmware to whichever flash partition you're not currently using (you're currently booted from primary so upload to secondary)
3. (optionally) Run the command allow-unsafe-updates 30
4. Boot to the partition where you uploaded your new firmware.

VSF will take care of copying the firmware to all the members and rebooting them.  From your perspective it's no different than upgrading a standalone switch.  Keep in mind that VSF does not have live upgrades so both members will reboot at the same time and network service will be interrupted.

The optional unsafe updates command will allow the switch to upgrade things like the boot ROM and serviceOS firmware.  These are important things to update BUT they make the reboot take longer and if you lose power during them the hardware may be unable to boot.

Hello,

we are using two 6300M switches with VSF configuration (ring topology)
we would like to upgrade the (old) firmware FL.10.09.1020 to firmware FL.10.13.1101

as I have never updated a VSF cluster myself I wanted to ask you which procedure is the right one here with as little downtime as possible. Thanks!

kind regards,

Juergen N.

Hi, 

there also is an in-service update option for the 6300-series with VSF. But it is only intended for upgrades between minor releases.

I never tried it, but I know it is possible. 

For future updates you can check: VSF In-Service Software Upgrade

Best

Yeah, that's the downside of VSF.  Updates always result in downtime.

Hello davidwk,

thanks for then answer, very useful! So there is no possibility without downtime as both devices restart at the same time ...
I thought that with this configuration would be possible

I have already performed an update on all the other standalone switches (6000/6100) to 10.13 with the command "allow-unsafe-udpates". As we have an UPS for the main switches (6300M), possible power interruptions should not be a problem.

Since 10.9 is a Short Support Release (SSR) it's generally recommended to not upgrade more than 2 major versions at a time (ie. 10.9 to 10.11 and then 10.11 to 10.13).  However 10.13 is a Long Support Release (LSR) and going from one LSR to the next is also supported and (in my opinion) is generally more stable. The next LSR after 10.9 is 10.10 so what I would do is upgrade to 10.10 and then upgrade to 10.13.

The actual upgrade process is pretty straight forward.

1. Backup your config
2. Upload the new firmware to whichever flash partition you're not currently using (you're currently booted from primary so upload to secondary)
3. (optionally) Run the command allow-unsafe-updates 30
4. Boot to the partition where you uploaded your new firmware.

VSF will take care of copying the firmware to all the members and rebooting them.  From your perspective it's no different than upgrading a standalone switch.  Keep in mind that VSF does not have live upgrades so both members will reboot at the same time and network service will be interrupted.

The optional unsafe updates command will allow the switch to upgrade things like the boot ROM and serviceOS firmware.  These are important things to update BUT they make the reboot take longer and if you lose power during them the hardware may be unable to boot.

Hello,

we are using two 6300M switches with VSF configuration (ring topology)
we would like to upgrade the (old) firmware FL.10.09.1020 to firmware FL.10.13.1101

as I have never updated a VSF cluster myself I wanted to ask you which procedure is the right one here with as little downtime as possible. Thanks!

kind regards,

Juergen N.

Yeah, that's the downside of VSF.  Updates always result in downtime.

Hello davidwk,

thanks for then answer, very useful! So there is no possibility without downtime as both devices restart at the same time ...
I thought that with this configuration would be possible

I have already performed an update on all the other standalone switches (6000/6100) to 10.13 with the command "allow-unsafe-udpates". As we have an UPS for the main switches (6300M), possible power interruptions should not be a problem.

Since 10.9 is a Short Support Release (SSR) it's generally recommended to not upgrade more than 2 major versions at a time (ie. 10.9 to 10.11 and then 10.11 to 10.13).  However 10.13 is a Long Support Release (LSR) and going from one LSR to the next is also supported and (in my opinion) is generally more stable. The next LSR after 10.9 is 10.10 so what I would do is upgrade to 10.10 and then upgrade to 10.13.

The actual upgrade process is pretty straight forward.

1. Backup your config
2. Upload the new firmware to whichever flash partition you're not currently using (you're currently booted from primary so upload to secondary)
3. (optionally) Run the command allow-unsafe-updates 30
4. Boot to the partition where you uploaded your new firmware.

VSF will take care of copying the firmware to all the members and rebooting them.  From your perspective it's no different than upgrading a standalone switch.  Keep in mind that VSF does not have live upgrades so both members will reboot at the same time and network service will be interrupted.

The optional unsafe updates command will allow the switch to upgrade things like the boot ROM and serviceOS firmware.  These are important things to update BUT they make the reboot take longer and if you lose power during them the hardware may be unable to boot.

Hello,

we are using two 6300M switches with VSF configuration (ring topology)
we would like to upgrade the (old) firmware FL.10.09.1020 to firmware FL.10.13.1101

as I have never updated a VSF cluster myself I wanted to ask you which procedure is the right one here with as little downtime as possible. Thanks!

kind regards,

Juergen N.

according to this post, newer firmware versions offer VSF ESU functionality for 6300 models without downtime. I'll see when I install the two firmware versions ...

thanks!

Yeah, that's the downside of VSF.  Updates always result in downtime.

Hello davidwk,

thanks for then answer, very useful! So there is no possibility without downtime as both devices restart at the same time ...
I thought that with this configuration would be possible

I have already performed an update on all the other standalone switches (6000/6100) to 10.13 with the command "allow-unsafe-udpates". As we have an UPS for the main switches (6300M), possible power interruptions should not be a problem.

Since 10.9 is a Short Support Release (SSR) it's generally recommended to not upgrade more than 2 major versions at a time (ie. 10.9 to 10.11 and then 10.11 to 10.13).  However 10.13 is a Long Support Release (LSR) and going from one LSR to the next is also supported and (in my opinion) is generally more stable. The next LSR after 10.9 is 10.10 so what I would do is upgrade to 10.10 and then upgrade to 10.13.

The actual upgrade process is pretty straight forward.

1. Backup your config
2. Upload the new firmware to whichever flash partition you're not currently using (you're currently booted from primary so upload to secondary)
3. (optionally) Run the command allow-unsafe-updates 30
4. Boot to the partition where you uploaded your new firmware.

VSF will take care of copying the firmware to all the members and rebooting them.  From your perspective it's no different than upgrading a standalone switch.  Keep in mind that VSF does not have live upgrades so both members will reboot at the same time and network service will be interrupted.

The optional unsafe updates command will allow the switch to upgrade things like the boot ROM and serviceOS firmware.  These are important things to update BUT they make the reboot take longer and if you lose power during them the hardware may be unable to boot.

Hello,

we are using two 6300M switches with VSF configuration (ring topology)
we would like to upgrade the (old) firmware FL.10.09.1020 to firmware FL.10.13.1101

as I have never updated a VSF cluster myself I wanted to ask you which procedure is the right one here with as little downtime as possible. Thanks!

kind regards,

Juergen N.

according to this post, newer firmware versions offer VSF ESU functionality for 6300 models without downtime. I'll see when I install the two firmware versions ...

thanks!

Yeah, that's the downside of VSF.  Updates always result in downtime.

Hello davidwk,

thanks for then answer, very useful! So there is no possibility without downtime as both devices restart at the same time ...
I thought that with this configuration would be possible

I have already performed an update on all the other standalone switches (6000/6100) to 10.13 with the command "allow-unsafe-udpates". As we have an UPS for the main switches (6300M), possible power interruptions should not be a problem.

Since 10.9 is a Short Support Release (SSR) it's generally recommended to not upgrade more than 2 major versions at a time (ie. 10.9 to 10.11 and then 10.11 to 10.13).  However 10.13 is a Long Support Release (LSR) and going from one LSR to the next is also supported and (in my opinion) is generally more stable. The next LSR after 10.9 is 10.10 so what I would do is upgrade to 10.10 and then upgrade to 10.13.

The actual upgrade process is pretty straight forward.

1. Backup your config
2. Upload the new firmware to whichever flash partition you're not currently using (you're currently booted from primary so upload to secondary)
3. (optionally) Run the command allow-unsafe-updates 30
4. Boot to the partition where you uploaded your new firmware.

VSF will take care of copying the firmware to all the members and rebooting them.  From your perspective it's no different than upgrading a standalone switch.  Keep in mind that VSF does not have live upgrades so both members will reboot at the same time and network service will be interrupted.

The optional unsafe updates command will allow the switch to upgrade things like the boot ROM and serviceOS firmware.  These are important things to update BUT they make the reboot take longer and if you lose power during them the hardware may be unable to boot.

Hello,

we are using two 6300M switches with VSF configuration (ring topology)
we would like to upgrade the (old) firmware FL.10.09.1020 to firmware FL.10.13.1101

as I have never updated a VSF cluster myself I wanted to ask you which procedure is the right one here with as little downtime as possible. Thanks!

kind regards,

Juergen N.

Hello!

thanks for the information.I upgraded the VSF switches without issues from 10.09 -> 10.10 -> 10.13 with network downtime of about 40min

kind regards,

Juergen

according to this post, newer firmware versions offer VSF ESU functionality for 6300 models without downtime. I'll see when I install the two firmware versions ...

thanks!

Yeah, that's the downside of VSF.  Updates always result in downtime.

Hello davidwk,

thanks for then answer, very useful! So there is no possibility without downtime as both devices restart at the same time ...
I thought that with this configuration would be possible

I have already performed an update on all the other standalone switches (6000/6100) to 10.13 with the command "allow-unsafe-udpates". As we have an UPS for the main switches (6300M), possible power interruptions should not be a problem.

Since 10.9 is a Short Support Release (SSR) it's generally recommended to not upgrade more than 2 major versions at a time (ie. 10.9 to 10.11 and then 10.11 to 10.13).  However 10.13 is a Long Support Release (LSR) and going from one LSR to the next is also supported and (in my opinion) is generally more stable. The next LSR after 10.9 is 10.10 so what I would do is upgrade to 10.10 and then upgrade to 10.13.

The actual upgrade process is pretty straight forward.

1. Backup your config
2. Upload the new firmware to whichever flash partition you're not currently using (you're currently booted from primary so upload to secondary)
3. (optionally) Run the command allow-unsafe-updates 30
4. Boot to the partition where you uploaded your new firmware.

VSF will take care of copying the firmware to all the members and rebooting them.  From your perspective it's no different than upgrading a standalone switch.  Keep in mind that VSF does not have live upgrades so both members will reboot at the same time and network service will be interrupted.

The optional unsafe updates command will allow the switch to upgrade things like the boot ROM and serviceOS firmware.  These are important things to update BUT they make the reboot take longer and if you lose power during them the hardware may be unable to boot.

Hello,

we are using two 6300M switches with VSF configuration (ring topology)
we would like to upgrade the (old) firmware FL.10.09.1020 to firmware FL.10.13.1101

as I have never updated a VSF cluster myself I wanted to ask you which procedure is the right one here with as little downtime as possible. Thanks!

kind regards,

Juergen N.