Config Applied to switch 1 in a stack only

[shills1]

Hi experts,

We are deploying 9200L switch stacks for a customer and are pre-staging before shipping to site. We have unboxed, stacked, configured, tested, un stacked and reboxed quite a few now and everything has gone great. However the customer now wants to add some new ACLs before the kit is shipped to site. I am hoping that rather than have to unbox and stack all the switches in the switch stack (AGAIN!!) I can just unbox switch 1 in the stack and apply the config. Then when all the switch stacks are dispatched to site, stacked and turned on the new config from switch 1 will be applied to all switches in the stack.

Am I right in thinking this?? Can you foresee any issues??

Many thanks

Steve

[marce1000 · Accepted solution]

   - Normally that is right BUT you must provision the stack master switch priority so that it always has that role
     as such. So that would then be another value then the default. To test local at your place for one 'example' before
     shipping other packages containing switches , stack master should then be labeled accordingly.

  M..

[Joseph W. Doherty]

BTW, an alternative to what @marce1000 suggests, would be to insure stack member #1 is powered up and finishes boot (and stack election) before other stack members are powered on.  (This would only need to be done the first time.)

That said, as you need to apply the ACL config change, you could also set the stack priority at the same time.  I.e., I believe what @marce1000 suggested is the better approach.

Another approach might be to apply the ACL update after the stack is booted at customer site.  I don't know what your on-going maintenance plans are, but if any is required, I presume it's not to ship these stacks back to you for configuration changes.

[shills1]

Thanks both of you for your responses.

When we initially configured the stack they were powered on top to bottom so the top switch would have been switch 1, the one underneath would be switch 2. As part of the configuration process they were then configured with decreasing priorities with switch 1 having the highest, switch 2 the 2nd highest etc. So from what you are saying I just need to configure the ACL on switch 1....makes my life easier??

I should maybe have mentioned the switch priorities that were configured on my original post....apologies.

[Joseph W. Doherty]

Yup, if switch one has the only and highest priority, and if all the switch stack members are powered on, at the same time, that switch should become the active/master switch and its config should be pushed to all the other stack member switches.

[Joseph W. Doherty]

BTW, you understand switch number is different from switch priority, right?

[marce1000]

- @shills1                    Yes , if switch 1 is intended to become the stack master

                   - The customer should  then for instance when installing the stacked switches :  power up the stack  master switch
      first and connect to SSH with it; and issue the command terminal monitor.
     Then connect the other stack 'child'  members   and watch for  errors , if any,

 M.