10-23-2013 11:20 PM - edited 03-07-2019 04:12 PM
Hello Team,
I have a Cisco 3750 switch as core ( 48 Port) , we purchased a new Cisco 3750 (24 Port) switch with stack cable. below the information of both switch .
1) I would like to know whether the new switch once added to stack will upgrade automatically ( the version has a difference one is SE3 (Existing ) and other SE5 (New Switch to be added ).
2) both are auto upgrade , will this create issue to the production Switch , that is will the production switch get upgraded ( Master) or only the new switch will get upgraded as soon as I connect it , is there any problem in keeping both auto upgrade.
##### Existing Switch in production ( 48 port )#############
Core -SW_A #show boot
BOOT path-list : flash:c3750e-universalk9-mz.122-55.SE3/
c3750e-universalk9-mz.122-55.SE3.bin
Config file : flash:/config.text
Private Config file : flash:/private-config.text
Enable Break : no
Manual Boot : no
Auto upgrade : yes
##########New Switch to be added to Stack ( 24 port ) ############
New -SW_A #show boot
BOOT path-list : flash:c3750e-universalk9-mz.122-55.SE5/
c3750e-universalk9-mz.122-55.SE5.bin
Config file : flash:/config.text
Private Config file : flash:/private-config.text
Enable Break : no
Manual Boot : no
Auto upgrade : yes
10-24-2013 01:47 AM
Personally I have never used auto upgrade in a production environment, I have always upgraded the IOS on the new switch manually, adjusted the priority manually and then added to the stack.
10-24-2013 01:56 AM
Hi.
Another option is to add swithces to stack without auto upgrade and then copy ios from master's switch flash to other switches:
copy flash(SWn):ios.bin flash(SWn):
where SWn is the switch number of master and destination switch.
HTH
Regards
Carlo
Please rate all helpful posts
"The more you help the more you learn"
10-24-2013 02:20 AM
how do i upgrade the IOS which is in the Directory , if i upgrade it directly put the IOS in the flash without directory
flash:c3750e-universalk9-mz.122-55.SE5/
c3750e-universalk9-mz.122-55.SE5.bin
10-24-2013 02:39 AM
copy flash1:c3750e-universalk9-mz.122-55.SE5/c3750e-universalk9-mz.122-55.SE5.bin flash2:
than..
If master has the ios on flash:c3750e-universalk9-mz.122-55.SE5 directory and switch 2 has the image on flash: root, you can differentiate the boot point by issuing:
boot system switch 2 flash:c3750e-universalk9-mz.122-55.SE5.bin
Otherwise you could create the same directory also on switch 2 flash
Switch#mkdir flash2:c3750e-universalk9-mz.122-55.SE5
In this case you can copy the image directly to the switch 2 previously created directory.
copy flash1:/c3750e-universalk9-mz.122-55.SE5/c3750e-universalk9-mz.122-55.SE5.bin flash2:c3750e-universalk9-mz.122-55.SE5/c3750e-universalk9-mz.122-55.SE5.bin
In this case the boot command would be only one:
boot system flash:/c3750e-universalk9-mz.122-55.SE5/c3750e-universalk9-mz.122-55.SE5.bin for all switches in the stack
HTH
Regards
Carlo
Please rate all helpful posts
"The more you help the more you learn"
10-24-2013 03:03 AM
Thank you for the reply , I have just seen the below in cisco site , they say that if IOS are same and major version is same then it will form the stack , below attached both switch sh platform stack manager all , both are 1.45 version , does that mean that the stack will join with out any issue , if you look the IOS is similar but with a difference in the last part that is SE3 and SE5 (tail identifier) does that mean this IOS is different or its just the identifier.
A new switch might not join a stack when Cisco IOS versions or stack protocol versions differ. Review these points about Cisco IOS versions and stack protocol versions:
1Switches with the same Cisco IOS version also have the same stack protocol version and are compatible in the same switch stack.
2Switches with the same Cisco IOS version as the stack master can join the stack.
3Switches with different Cisco IOS versions can have different stack protocol versions.
4Switches with the same Cisco IOS version but different major version numbers are incompatible and cannot function in the same switch stack.
===
Core-SW #sh platform stack manager all
Switch/Stack Mac Address : 44d3.ca58.5500
H/W Current
Switch# Role Mac Address Priority Version State
----------------------------------------------------------
*1 Master 44d3.ca58.5500 1 1 Ready
Stack Port Status Neighbors
Switch# Port 1 Port 2 Port 1 Port 2
--------------------------------------------------------
1 Down Down None None
Stack Discovery Protocol View
==============================================================
Switch Active Role Current Sequence Dirty
Number State Number Bit
--------------------------------------------------------------------
1 TRUE Master Ready 001 FALSE
Stack State Machine View
==============================================================
Switch Master/ Mac Address Version Current
Number Member (maj.min) State
-----------------------------------------------------------
1 Master 44d3.ca58.5500 1.45 Ready
Last Conflict Parameters
Switch Master/ Cfgd Default Image H/W # of Mac Address
Number Member Prio Config Type Prio Members
-----------------------------------------------------------------------
Stack Discovery Protocol Counters
Messages Sent Messages Recvd
UP DOWN UP DOWN
--------------------------------------------------------
*1: 0000000000 0000000000 0000000000 0000000000
2: 0000000000 0000000000 0000000000 0000000000
3: 0000000000 0000000000 0000000000 0000000000
4: 0000000000 0000000000 0000000000 0000000000
5: 0000000000 0000000000 0000000000 0000000000
6: 0000000000 0000000000 0000000000 0000000000
7: 0000000000 0000000000 0000000000 0000000000
8: 0000000000 0000000000 0000000000 0000000000
9: 0000000000 0000000000 0000000000 0000000000
Misc Counters
Counter Up Down
---------------------------------------------------
Wrong Ver Number: Send: 0000000000 0000000000
Wrong Ver Number: Recv: 0000000000 0000000000
Missed Messages: 0000000000 0000000000
Orphaned Messages 0000000000 0000000000
Suppressed Messages 0000000000 0000000000
No Available Messages 0000000000 0000000000
Link Present 0000000000 0000000000
Link Not Present 0000000001 0000000001
Link RxReset 0000000010 0000000010
Link Sync Stuck Resets 0000000000 0000000000
Duplicates 0000000000 0000000000
RAC Not OK Resets 0000000000
Switch# of last duplicate 0000000256
Sequence Number Failures 0000000000
RAC Not OK Resets 0000000000
Sync Not OK Resets 0000000000 0000000000
Switch# of last Failure: 256 Last Difference 0
Switch Number Conflicts 0
Stack Changes 0
Int Stack Link changes 0
Int Stack Link state 0x0
Reciprocal Efficiency Changes: Upgrade 0, Downgrade 0
Resource Counters
-------------------------------------------
Chunk Alloc's 0000000001
Chunk Free's 0000000001
Enqueue Failures: 0000000000
Null Queue Failures: 0000000000
Chunk Alloc Errors: 0000000000
Stack State Machine Counters
Messages Sent Messages Recvd
-------------------------------------------------
*1: 0000000001 0000000001
2: 0000000000 0000000000
3: 0000000000 0000000000
4: 0000000000 0000000000
5: 0000000000 0000000000
6: 0000000000 0000000000
7: 0000000000 0000000000
8: 0000000000 0000000000
9: 0000000000 0000000000
======New-Switch
Switch#sh platform stack manager all
Switch/Stack Mac Address : c08c.60b6.b080
H/W Current
Switch# Role Mac Address Priority Version State
----------------------------------------------------------
*1 Master c08c.60b6.b080 1 1 Ready
Stack Port Status Neighbors
Switch# Port 1 Port 2 Port 1 Port 2
--------------------------------------------------------
1 Down Down None None
Stack Discovery Protocol View
==============================================================
Switch Active Role Current Sequence Dirty
Number State Number Bit
--------------------------------------------------------------------
1 TRUE Master Ready 001 FALSE
Stack State Machine View
==============================================================
Switch Master/ Mac Address Version Current
Number Member (maj.min) State
-----------------------------------------------------------
1 Master c08c.60b6.b080 1.45 Ready
Last Conflict Parameters
Switch Master/ Cfgd Default Image H/W # of Mac Address
Number Member Prio Config Type Prio Members
-----------------------------------------------------------------------
Stack Discovery Protocol Counters
Messages Sent Messages Recvd
UP DOWN UP DOWN
--------------------------------------------------------
*1: 0000000000 0000000000 0000000000 0000000000
2: 0000000000 0000000000 0000000000 0000000000
3: 0000000000 0000000000 0000000000 0000000000
4: 0000000000 0000000000 0000000000 0000000000
5: 0000000000 0000000000 0000000000 0000000000
6: 0000000000 0000000000 0000000000 0000000000
7: 0000000000 0000000000 0000000000 0000000000
8: 0000000000 0000000000 0000000000 0000000000
9: 0000000000 0000000000 0000000000 0000000000
Misc Counters
Counter Up Down
---------------------------------------------------
Wrong Ver Number: Send: 0000000000 0000000000
Wrong Ver Number: Recv: 0000000000 0000000000
Missed Messages: 0000000000 0000000000
Orphaned Messages 0000000000 0000000000
Suppressed Messages 0000000000 0000000000
No Available Messages 0000000000 0000000000
Link Present 0000000000 0000000000
Link Not Present 0000000001 0000000001
Link RxReset 0000000010 0000000010
Link Sync Stuck Resets 0000000000 0000000000
Duplicates 0000000000 0000000000
RAC Not OK Resets 0000000000
Switch# of last duplicate 0000000256
Sequence Number Failures 0000000000
RAC Not OK Resets 0000000000
Sync Not OK Resets 0000000000 0000000000
Switch# of last Failure: 256 Last Difference 0
Switch Number Conflicts 0
Stack Changes 0
Int Stack Link changes 0
Int Stack Link state 0x0
Reciprocal Efficiency Changes: Upgrade 0, Downgrade 0
Resource Counters
-------------------------------------------
Chunk Alloc's 0000000001
Chunk Free's 0000000001
Enqueue Failures: 0000000000
Null Queue Failures: 0000000000
Chunk Alloc Errors: 0000000000
Stack State Machine Counters
Messages Sent Messages Recvd
-------------------------------------------------
*1: 0000000001 0000000001
2: 0000000000 0000000000
3: 0000000000 0000000000
4: 0000000000 0000000000
5: 0000000000 0000000000
6: 0000000000 0000000000
7: 0000000000 0000000000
8: 0000000000 0000000000
9: 0000000000 0000000000
10-24-2013 03:44 AM
I would make sure the IOS is exactly the same on the new switch before adding it.
Stackable switches are very picky an the last thing you want is for the stack to reboot when adding the new switch!
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide