Wireless Access

I'm configuring a new school with a 6 member stack.

I configure the first switch which has the following config in it:

!

stack-profile

   member-id 0 serial-number BZ000123 role primary-capable

   member-id 1 serial-number BZ000234 role primary-capable

   member-id 2 serial-number BZ000345 role line-card

   member-id 3 serial-number BZ000456 role line-card

   member-id 4 serial-number BZ000567 role line-card

   member-id 5 serial-number BY001678 role line-card

!

After saving the config I connect the second switch in the stack and the second switch deletes the config on the first switch and makes itself Primary. How do I stop this? Its REALLY annoying.

Why  is the Dynamic election overriding my configuration?

How do I revert it without Facorty-defaulting everything...again?

Playinpearls,

So I assume the first switch where you have the configuration is serial-number BZ000123? Is the second switch factory defaulted? Was it powered up at the same time as the first?

Best regards,

Madani

well its fake but yes, its member 1 that is configured first.

All the rest are factory defaulted from the first time it did this.

So member 1 is configured first, then you attached member 0? I'm just trying to follow your order of operations. I ran a quick test with two switches and can't replicate it.

(ArubaS1500-12P) >en
Password:******
Zero Touch Provisioning (Activate or DHCP based) of the system has been stopped.

Would you like to use Quick-Setup to help with the basic configuration of the system (y|n)?n
Quick-setup dialog can be launched by executing "quick-setup" command in enable mode

(ArubaS1500-12P) #configure t
Enter Configuration commands, one per line. End with CNTL/Z

(ArubaS1500-12P) (config) #hostname ARUBASTACK
(ARUBASTACK) (config) #stack-profile
(ARUBASTACK) (stack-profile) #member-id 0 serial-number CD0005213 role primary-capable
WARNING!! This profile will not be applied till the configuration is saved.


(ARUBASTACK) (stack-profile) #member-id 1 serial-number CF0000005 role primary-capable
WARNING!! This profile will not be applied till the configuration is saved.


(ARUBASTACK) (stack-profile) #exit
(ARUBASTACK) (config) #mgmt-user admin root
Password:********
Re-Type password:********
(ARUBASTACK) (config) #write mem
Saving Configuration...


Configuration Saved.

(ARUBASTACK) (config) #exit
(ARUBASTACK) #show stacking members

Stack status: Active, Stack Id: 000b86991c375491fa6a
Stack uptime: 1 minutes 35 seconds
Id    Role       MAC Address        Priority  State     Model            Serial      Location
--    ----       -----------        --------  -----     -----            ------      --------
0  *  Primary    00:0b:86:99:1c:37  Preset    Active    ArubaS1500-12P   CD0005213   Not Set

# I attached the second switch at this point which should become member 1.

(ARUBASTACK) #show stacking members

Stack status: Active, Stack Id: 000b86991c375491fa6a
Stack uptime: 2 minutes 56 seconds
Id    Role       MAC Address        Priority  State     Model            Serial      Location
--    ----       -----------        --------  -----     -----            ------      --------
0  *  Primary    00:0b:86:99:1c:37  Preset    Active    ArubaS1500-12P   CD0005213   Not Set
?     NA         00:0b:86:8f:af:b7  NA        Away      ArubaS1500-48P   CF0000005   Not Set

(ARUBASTACK) #show stacking members

Stack status: Active, Stack Id: 000b86991c375491fa6a
Stack uptime: 5 minutes 36 seconds
Id    Role       MAC Address        Priority  State     Model            Serial      Location
--    ----       -----------        --------  -----     -----            ------      --------
0  *  Primary    00:0b:86:99:1c:37  Preset    Active    ArubaS1500-12P   CD0005213   Not Set
1     Secondary  00:0b:86:8f:af:b7  Preset    Active    ArubaS1500-48P   CF0000005   Not Set

Fortunately, I've found that there is not a tiny space in the 6 of that serial thus member 0 had the wrong serial number in place. The stack is now up correctly.

I guess its time for some glasses, lol.

thanks!