cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
323
Views
1
Helpful
3
Replies

When updating the C1000 software only active was updated

I have uploaded a new image c1000-universalk9-mz.152-7.E10.bin
show flash:

krzysztofmaciejewskiit_0-1722929596428.png

I used the "boot system switch all flash:c1000-universalk9-mz.152-7.E10.bin" command to set the software on all members of the stack, but it did not set the variable with the new software on all units. So I did it manually:
boot system switch 1 flash:c1000-universalk9-mz.152-7.E10.bin
boot system switch 2 flash:c1000-universalk9-mz.152-7.E10.bin
boot system switch 3 flash:c1000-universalk9-mz.152-7.E10.bin
boot system switch 4 flash:c1000-universalk9-mz.152-7.E10.bin

krzysztofmaciejewskiit_1-1722929791038.png

You can see that only Active Member has updated.

krzysztofmaciejewskiit_2-1722929826217.png

Do you have any ideas why this happened? I also tried unplugging one unit from the power supply however that didn't help either. I also reset the stack members one by one, but also with no effect.

 

1 Accepted Solution

Accepted Solutions

Leo Laohoo
Hall of Fame
Hall of Fame

The behaviour is not "unusual" because someone updated the stack by manually "copying" the BIN files. 

This is not a recommended process nor is it a best practice either. 

The most effective way is to use the TAR file and use the following command   

 

archive download-sw tftp://<TFTP_IP_ADDRESS>/filename.tar

 

With the above command, the process will:

1.  Distribute the BIN file across all switch members;
2.  Correctly change the boot variable string; and
3.  Perform an MD5 hash check to make sure the BIN file is not corrupt.  

View solution in original post

3 Replies 3

Has anyone had a similar problem?
Do you think updating from a .tar file will be a better idea than from a .bin file?

Leo Laohoo
Hall of Fame
Hall of Fame

The behaviour is not "unusual" because someone updated the stack by manually "copying" the BIN files. 

This is not a recommended process nor is it a best practice either. 

The most effective way is to use the TAR file and use the following command   

 

archive download-sw tftp://<TFTP_IP_ADDRESS>/filename.tar

 

With the above command, the process will:

1.  Distribute the BIN file across all switch members;
2.  Correctly change the boot variable string; and
3.  Perform an MD5 hash check to make sure the BIN file is not corrupt.  

I tested this during today's service window. It works.