Creating a Two-unit Linear-topology Stack Using Stack Zero-touch Provisioning

Stack zero-touch provisioning elects to form a linear-topology trunk only when the active controller has a linear-topology trunk configuration for itself. If the active controller does not have a linear-topology trunk configuration, stack zero-touch provisioning forms a ring.

The following procedure uses an ICX 7250 stack as an example. A two-unit ICX 7250 stack has two potential linear-topology trunks, (x/2/1 to x/2/4) and (x/2/5 to x/2/8). The system configures a four-port trunk and removes the other direction.

Note: Neither stack interactive-setup nor stack zero-touch provisioning can convert a live two-unit stack to a linear-topology trunk. If you are working with a live system, you can enter the multi-stack-trunk 1/2/1 to 1/2/4 and 2/2/1 to 2/2/4 command to change the configuration on both units simultaneously. Refer to Changing a live two-unit stack to a linear-topology trunk for more information.

Complete the following steps to configure a two-unit linear-topology trunk using stack zero-touch provisioning.

Note: For more information on stack zero-touch provisioning, refer to Scenario 2 - Using zero-touch provisioning to configure a stack.

  1. Connect cables between the two units. (In this example, four cables are used as shown in ICX 7250-24P two-unit stack with linear-topology trunk as configured in example).
  2. On the unit that you want to become the active controller, create the desired trunk in stack unit 1 configuration sub-mode. 
    ICX7250# configure terminal
ICX7250(config)# stack unit 1
ICX7250(config-unit-1)# stack-trunk 1/2/1 to 1/2/4
ICX7250(config-unit-1)# exit
    The example configures ports 1/2/1 through 1/2/4 as a stacking trunk.
  3. On the prospective active controller, enable stacking and zero-touch provisioning as shown in the following example. 
    ICX7250(config)# stack enable
!
ICX7250(config)# stack zero-touch-enable
!

    The first unit detects the other unit within a few minutes.

    The first unit reloads the other unit as a stack member.

    A two-unit stack forms when the member boots up and joins the stack.

  4. Enter the write memory command to save the configuration. 
    ICX7250(config)# write memory

The following example shows the discovery of a two-unit ICX 7250 linear-topology stack using stack zero-touch provisioning. 

ICX7250-48P Router# show running-config
Current configuration:
!
ver 08.0.90
!
stack unit 1
  module 1 icx7250-48p-poe-port-management-module
  module 2 icx7250-sfp-plus-8port-80g-module
  stack-port 1/2/1
  stack-port 1/2/3
!
!                                                                
end

ICX7250-48P Router# configure terminal
ICX7250-48P Router(config)# stack unit 1
ICX7250-48P Router(config-unit-1)# stack-trunk 1/2/1 to 1/2/4
stack-trunk 1/2/1 to 1/2/4 replaces stack-port 1/2/1

ICX7250-48P Router(config)# stack enable
Enable stacking. This unit actively participates in stacking

ICX7250-48P Router(config)# stack zero-touch-enable  
ICX7250-48P Router(config)# exit
ICX7250-48P Router#

T=7m3.1: Election, was alone --> active, ID=1, pri=128, 2U(1-2), A=u1, nbr#=1 0, reason: u2: enable, , 
Detect stack member 2 POE capable
T=7m3.6: Synchronize webauth files to u2
T:7m5.3: Done hot swap: active controller u1 sets u2 to Ready.
T=7m5.9: Election, was active, no change, ID=1, pri=128, 2U(1-2), A=u1, nbr#=1 0, reason: u1: stk-po-chg, , 

Config changed due to add/del units. Do write mem if you want to keep it
T=8m6.7: Assigned unit 2 to be standby
T=8m8.7: start running config sync to standby u2
T=8m9.6: Running config sync to standby u2 is complete


====================unit 2 log=============================
Unit 1 receives stack zero-touch from U1, mac=609c.9f99.3f80
ID=2 D0=2/1 to 2/4, , will reload from Primary in 20 sec
Unmounting the External USB
We are in system reset 

#### Bootup printout is snipped

The system : started=warm start   reloaded=by "reload"
My stack unit ID = 2, bootup role = member


[MEMBER]local-2@ICX7250-48P Router>
Creating certificate, please wait...

SSL Client Certificate is successfully created

[MEMBER]local-2@ICX7250-48P Router>


T=45.2: Election, was member, no change, ID=2, pri=0, 2U(1-2), A=u1, nbr#=1 0, reason: u1: hitle-fail-en, , 
Unit 2 becomes ready
Connecting to active controller 1 console...(Press Ctrl Shift -  x to exit)

T=48.2: Election, was member, no change, ID=2, pri=0, 2U(1-2), A=u1, nbr#=1 0, reason: u1: stk-po-chg, , 

ICX7250-48P Router>UNIT2:T=1m49.1: Unit 2 is assigned standby by active u1. 
T=1m51.3: Standby u2 start parsing running config from active controller u1
T=1m51.5: Standby u2 finished parsing running config from active controller u1.
T:1m53.6: Done hot swap: standby controller u2 sets u1 to Ready.
========================================================================

ICX7250-48P Router# show running-config
Current configuration:
!
ver 08.0.90
!
stack unit 1
  module 1 icx7250-48p-poe-port-management-module
  module 2 icx7250-sfp-plus-8port-80g-module
  priority 128
  stack-trunk 1/2/1 to 1/2/4
  
stack unit 2
  module 1 icx7250-48p-poe-port-management-module
  module 2 icx7250-sfp-plus-8port-80g-module
  stack-trunk 2/2/1 to 2/2/4
  
stack enable
stack zero-touch-enable
stack mac 609c.9f99.3f80
!
!
hitless-failover enable
!
!
end

ICX7250-48P Router# show stack
T=41m18.8: alone: standalone, D: dynamic cfg, S: static
ID   Type          Role    Mac Address    Pri State   Comment                   
1  S ICX7250-48P   active  609c.9f99.3f80 128 local   Ready
2  D ICX7250-48P   standby 609c.9f99.1988   0 remote  Ready

    standby      active                                                        
     +---+        +---+                                                        
     | 2 |2/1==2/1| 1 |                                                        
     +---+        +---+                                                        
Standby u2 - protocols ready, can failover
Role history: N: standalone, A: active, S: standby, M: member
U1: N->A

Current stack management MAC is 609c.9f99.3f80
ICX7250-48P Router# write memory
Parent topic: Configuring Two-unit Stack Linear-topology Trunks