Sie sind auf Seite 1von 42

SummitStack Stacking Technology

ExtremeXOS Operation and Configuration, Version 12.1

2008 Extreme Networks, Inc. All rights reserved. ExtremeXOS Operation and Configuration, Version 12.1. Part number DOC-00919.

Student Objectives
Upon completion of this module, you will be able to: Describe the benefits of SummitStack Stacking Technology Explain how stacking operates Identify the various components of stacking Configure a set of devices to employ stacking Verify the stacking configuration Troubleshoot stacking issues

Slide 2

SummitStack Stacking Technology Benefits


Chassis Simplifies management More redundancy and highavailability options

Requires the allocation of more


space than justified by initial need

More expensive Standalone fixed-format switches Less expensive Easier to fit into open rack slots Each new addition of access ports
brings with it another device to manage

Typically not as redundant

Slide 3

Combined Management

SummitStack Stacking Technology Benefits (Continued)


Combined Management ExtremeXOS SummitStack creates a
single management point of control Manage all units with a single IP

Pay as You Grow Start out with a single switch and grow to
eight switches in a single stack

Mix Products to Fit Mix switches with different interface types


and port densities in a single stack
10/100/1000BASE-T / TX / mini-GBIC / AC and DC powered / PoE and non-PoE

Optimized Stacking Architecture Throughput of up to 320 Gigabits per


Second (Gbps) per stack

Decreased Connectivity Cost Using Extreme Networks stacking is less


expensive than interconnecting the devices using 10 Gigabit Ethernet links
Slide 4

Hardware Requirements
ExtremeXOS allows the following hardware platforms to be joined together in a stack Summit x250e Summit x450, Summit x450a, Summit x450e

Stacking Cable Cables with special connectors minimum length of 0.5 Maximum length of 5 M,
Order # 16106 16107 16108 Name Stacking Cable, 0.5M Stacking Cable, 1.5M Stacking Cable, 3.0M Description SummitStack/UniStack stacking cable, 0.5M SummitStack/UniStack stacking cable, 1.5M SummitStack/UniStack stacking cable, 3.0M

16105

Stacking Cable, 5.0M

SummitStack Stacking Cable, 5.0M (not supported for UniStack)

Slide 5

Software Requirements
SummitStack Stacking Technology requires ExtremeXOS Software Version 12.0 or later Units running less than ExtremeXOS 12.0 will not join stack Exact same version required Units with software version greater than or equal to 12.0 but not equal to
stack master version become active stack members with disabled front panel ports

Units equal or greater than 12.0 can download software while in stack download image <ipaddress> <filename> slot <slot number>
Stage and configure devices before deploying

Slide 6

Stacking Ports - Stacking Architecture


Stacking bandwidth: up to 320 Gbps per stack

Stacking Ports 2 stacking ports per device 10 Gbps, Full Duplex per port 40 Gbps stack capacity per switch 320 Gbps stack capacity per 8
devices

20 Gbps per port

40 Gbps per switch

Slide 7

Unit Roles - Stacking Architecture


Master Unit Manages the configuration of all units Acquires ownership of other unit's configuration Share configuration database with Backup Master Unit Functionality similar to a Master MSM Backup Master Unit Ready should the Master Unit fails Does not own its own configuration Acquires co-ownership of standby units Functionality similar to a secondary MSM in a chassis Standby Unit Essentially Slaves to the Master Unit ASICs programmed by Master Unit Functionality similar to an I/O module in a chassis
Slide 8

Ring Topology - Stacking Architecture


RING SEGMENTED
1 1

Provides redundancy Works around stack cable failure Works around a loss of a unit Daisy chain not supported for continuous operations No resiliency Can lead to stack segmentation Behaves like a chassis Stack cable similar to backplane


2 2 3 3 4 4

DAISY-CHAIN
Slide 9

Topology Traffic - Traffic Handling - Stacking Architecture


Traffic classified as: Topology Traffic Known Unicast Traffic Known Multicast Traffic VLAN Traffic (Unknown Unicast,
Unknown Multicast, Broadcast Traffic)

1 2 3 4 5 6 7 8

Topology Traffic: Uses hop-by-hop protocol Manages the stack Only stack configuration messages Processed by the CPU Can be used to configure stacking on
devices even if the stack cannot form

Very low bandwidth consumption


Slide 10

Unicast Traffic - Traffic Handling - Stacking Architecture


Units send and receive traffic on both ports Enables a shortest path algorithm Handled by switching fabric Source switching ASIC forwards to
Destination switching ASIC

1
2 3 4 5 6

No stacking ports blocked Known unicast traffic will not loop


because it is not flooded

7
8

stack port 1

stack port 2
2 "hops" to unit 8 through stack port 1 3 "hops" to unit 3 through stack port 2

Slide 11

Known Multicast Traffic - Traffic Handling Stacking Architecture


Handled by switching fabric Each ASIC aware of relevant
Multicast configurations on other units

1 2 3 4 5 6 7 8

Blocks ports to prevent loops Based upon multicast address Attempts to distribute multicast traffic
evenly

Blocked Ports for Multicast Address 1


Slide 12

Blocked Ports for Multicast Address 2

Unknown Unicast / Broadcast / Unknown Multicast - Traffic Handling - Stacking Architecture


Also referred to as VLAN Traffic Unknowns must be flooded since destination location is unknown All VLANs will have the same stacking ports blocked Blocked port is Stack Port 1 on unit
with lowest MAC address plus interconnected port
1
2 3 4 5 6

7
8

Blocked Ports for all VLAN Traffic

Slide 13

Stack Join - Stacking Operations


1. Discover Stack Topology 2. Elect Master 3. Elect Backup Master 4. Stack Configuration 5. Operational Phase
1 2 3

4
5 6 7 8

Slide 14

Discover Stack Topology - Stack Topology


Units exchange information until they determine stack topology Must be ExtremeXOS 12.0 or greater Occurs whether or not stacking is enabled Units broadcast discovery packet The CPU on each unit processes the packet
1 2 3

4
5 6 7 8

Each Unit then increments hop count and forwards packet


Units remove packets with own MAC address

Slide 15

Master / Backup Master Election - Stacking Operations


Election based upon Only units with master-capability can participate Highest Stacking Priority
User configured Possible Values: AUTOMATIC, 1-100 Highest priority wins Default: AUTOMATIC

Slot Number (If Priority Tie)


User configured Must be unique Not necessarily related to physical position in stack or distance from Master Lowest slot number wins Default: 1

Automatic priority
EXOS decides the election priority Currently slot number alone used, subject to revision

The Backup Master is the one that came in second


Slide 16

Stack Configuration - Stacking Operations


Master reads the configuration file Master shares configuration with backup Master / Backup Master acquire ownership of other units configuration Master implements configuration 1. Configures self (Only master self-configures) 2. Configures backup master with RPC-like calls
Uses Control VLAN (control channel)

3. Configures standby units with RPC-like calls


Switching engines updated as configuration is implemented

Slide 17

Operational Phase - Stacking Operations


Topology continuously verified Relevant configuration changes propagated throughout Switching decision made by ingress
switch engine
Forwarded to destination port(s) Local switching requires no stack port

Stack is manageable Uses VLAN mgmt Stack MAC Address Stack IP Address

red vlan limited to single unit yellow vlan exists on multiple units - requires stack ports

Slide 18

Stack Link Failure Recovery - Stack Operations


Single link failure Shortest path recalculated by all
units
1 2 3 4 5 6 7

Block ports removed

before: U5 to U4 - 1 hop via stack port 2 after: U5 to U4 - 7 hops via stack port 1
Slide 19

Multiple Link Failure Recovery - Stack Operations


Calculate new shortest path

Stack segmentation occurs Master / Backup master on different segments Segment with master
Elect new backup master

NEW BACKUP MASTER

Path recalculated on all units


Switching ASICs updated for missing units

Segment with backup master


Backup master becomes master Elect new backup master Recalculated path on all units

MASTER

Switching ASICs updated for missing units

Issues
Both segments retain Stack IP address Both segments retain Stack MAC address

BACK MU AP ST ME AR STER NEW BACKUP MASTER

Backup Master becomes Master Unit


Slide 20

Multiple Link Failure Recovery - Stack Operations (Continued)


Calculate new shortest path

Master / Backup master on same segment Segment with no masters


Elect new masters (using same stack MAC as other segment!) NEW BACKUP MASTER NEW MASTER

Both Segments
Switching ASICs updated for missing units Recalculate shortest path on all units

BACKUP MASTER MASTER

Slide 21

Unit Failure Recovery - Stack Operations


Involves both the loss of the unit and the loss of the stacking ports Ring integrity is compromised due to loss
of stacking port Is master lost? N O Is backup master lost? N O YES

Lost-Master Recovery Tasks

Stack enters fallback daisy-chain operation

Lost-Master Recovery Tasks Backup Master immediately becomes


Master

YES

Lost-BUMaster Recovery Tasks

New Backup Master unit selected Lost-BU-Master Recovery Tasks New Backup Master elected Common Lost Unit Recovery Tasks Block ports removed Shortest path recalculated by all units Switching ASICs updated for missing units

Common Lost Unit Recovery Tasks

Slide 22

Preparing a Stack for Configuration


Use the following procedure to prepare a stack for configuration: 1. Select the appropriate stack units for your application and plan to use the
stack as if it were a single multi-slot switch.

2. Physically locate the stack nodes adjacent to one another. 3. Ensure the exact same version of software is running on all stack nodes. 4. Ensure all units have a default configuration 5. Connect the stacking cables. If you intend to deploy new units that might be part of a stack in the future, you might want to turn on stacking mode during initial deployment to avoid a future restart.

Slide 23

enable stacking

Configuring a New Stack


1. Apply power to all units in the stack. 2. Log in to the intended stack master through the console port. 3. Remove any legacy stacking configuration using the unconfigure stacking command. 4. Verify the stack configuration using the show stacking and show stacking configuration commands. 5. If necessary, configure license level restrictions using the configure stacking license-level command. 6. Issue the enable stacking command.

Answer "Yes" to perform easy setup Answer "Yes" to proceed 7. Log into the switch with admin privileges. safe-default script runs. Select values for normal operation 8. Verify that the master node is the one you intended to be the master using the show stacking command.
9. Verify remainder of configuration. 10. Save the configuration using the

save configuration command.


Slide 24

configure stacking easy-setup

Describing the Easy-Setup Option


The easiest way to configure the stack is to use the following command: configure stacking easy-setup The easy-setup option enables the administrator to effectively execute the following five commands: enable stacking configure stacking slot-number automatic configure stacking mac-address automatic configure stacking redundancy minimal reboot stack-topology

Slide 25

enable / disable stacking

Enabling / Disabling Stacking


To enable stacking on one or all nodes in the stack [ enable | disable ]
stacking {node-address <node-address>}

Disabled nodes Do not forward customer's data


through their stacking links

Will not become a member of the


active topology

Targets a specific node or all units if node-address is absent


When Stacking Enabled QoS profiles QP6 and QP7 are unavailable

Will become their own master and


will process and execute their own configuration independently

Command takes effect at the node(s) next reboot

Performs analysis of current stacking configuration if a nodeaddress is not specified Prompts for easy setup if stack is
unconfigured or configuration inconsistencies
Slide 26

To Verify show stacking configuration Uppercase E flag indicates if enabled


Default: Disabled

configure stacking slot-number

Configuring the Stacking Slot-number


Configure the node's slot number configure stacking slot-number automatic configure stacking nodeaddress <node-address> slotnumber <slot-number> Automatic parameter assigns slot numbers automatically In ring configuration: current node is
assigned slot 1, unit connected to current node, stack port 2 is assigned slot 2, assignment continues to slot 8

The Easy-Setup option executes the configure stacking slotnumber automatic command Ports addressed slot:port_number. Example 3:22 Command takes effect at the node(s) next reboot Verify with show stacking configuration Default: 1

In daisy chain configuration: slot 1 is assigned to the node at the end of the chain that begins with the node connected to the current node's stack port 1

Node-address parameter allows administrator to target specific unit


Slide 27

configure stacking node-address

Configure the Stacking MAC Address


You must configure the stacking MAC address to make the stack manageable over the network by selecting a source node The system sets the Universal /
Local bit to local to form the stack mac-address and then configure it on every node in the stack

To derive the stack MAC address from another unit in the stack: configure stacking nodeaddress <node-address> macaddress

configure stacking slot


<slot-number> macaddress

To derive the stack MAC address from the current unit: configure stacking macaddress

This command takes effect only after you restart the node. Verify using: show stacking detail Default: No stack MAC address is configured.

The easy setup option causes the stacking MAC address to be derived from the current unit.

Slide 28

configure stacking redundancy

Configure Stacking Redundancy


To automatically configure master capabilities on all units in the stack, use this command: configure stacking redundancy [ none | minimal | maximal] none - Only one node has mastercapability turned on

None and Minimal configurations use the slot-number and priority Takes effect on next reboot The Easy setup option executes the configure stacking redundancy minimal command. Verify using: show stacking configuration lowercase c flag indicates if the
command has been executed

minimal - Two nodes have mastercapability turned on

maximal - All nodes have mastercapability turned on

Must be run on a stack with 8 nodes or less

Slide 29

reboot

Rebooting the Stack


The reboot option has a number of stack oriented options: reboot slot<slot-number>
specifies the slot number currently being used by the active stack node that isto be rebooted.

reboot node-address <node-address>


specifies the MAC address of the SummitStack node to be rebooted

reboot stack-topology
specifies that the entire SummitStack is to be rebooted whether or not nodescare active.

reboot stack-topology as-standby


specifies that all stack nodes that are to be rebooted are to operate as if configured to not be master-capable

The Easy-Setup executes a reboot stack-topology command after configuring the stack
Slide 30

configure stacking alternate-ip-address configure stacking alternate-ip-address

Making the Non-Master Nodes IP Manageable


Configure an IP address to make the individual units in the stack manageable over the network. configure stacking alternate-ip-address [<ipaddress> <netmask> | <ipNetmask>] <gateway> automatic
configure stacking [node-address <node-address> | slot <slot-number>] alternate-ip-address [<ipaddress> <netmask> | <ipNetmask>] <gateway> Assigns a secondary IP address to the each node Automatic assign the specified IP Address to current node Subsequent nodes assigned specified IP Address + 1

Alternate not configured if subnet mask differs from "Mgmt" VLAN


Alternate configured if no "Mgmt" VLAN IP defined Configuration take effect immediately Verify using: show stacking configuration

Default: No address
Slide 31

configure stacking license-level unconfigure stacking license-level

Configuring Stacking License Level


To enable a unit to run at a lower license level than is installed: configure stacking {node-address <node-address> | slot <slot-number>} license-level [core | advancededge | edge]

Target a particular node using node-address or slot parameters. If node-address or slot parameter not specified, all nodes configured. Does not change the installed license level.
Cannot be used to upgrade a nodes behavior.

This command takes effect after you restart the node.


Verify with: show stacking configuration All nodes must be at the same effective level Default: No license level restriction is configured.
Slide 32

synchronize stacking

Synchronizing Stacking Parameters


To apply the stacking parameters from one node to another, use the command: synchronize stacking {node-address <node-address> | slot <slot-number>}

Copies NVRAM based configuration parameters to target node: stacking mode stack MAC address failsafe account and password failsafe account access point permissions the selected partition
Takes effect next node reboot. Verify using: show stacking detail Default: Not applicable.
Slide 33

show stacking configuration

Verifying Stack Configuration


Stack MAC in use: 02:04:96:27:2c:9f Node Slot Alternate Alternate MAC Address Cfg Cur Prio Mgmt IP / Mask Gateway Flags Lic ------------------ --- --- ---- ------------------ --------------- ------- --*00:04:96:27:2c:9f 1 1 Auto <none> <none> CcEeMm- -00:04:96:27:2f:52 2 2 Auto <none> <none> CcEeMm- -00:04:96:20:b4:05 3 3 Auto <none> <none> --EeMm- -00:04:96:20:aa:25 4 4 Auto <none> <none> --EeMm- -* - Indicates this node Flags: (C) master-Capable in use, (c) master-capable is configured, (E) Stacking is currently Enabled, (e) Stacking is configured Enabled, (M) Stack MAC in use, (m) Stack MACs configured and in use are the same, (i) Stack MACs configured and in use are not the same or unknown, (-) Not in use or not configured License level restrictions: (C) Core, (A) Advanced edge, or (E) Edge in use, (c) Core, (a) Advanced edge, or (e) Edge configured, (-) Not in use or not configured Slot-1 Stack.4 #

Slide 34

show stacking ports

Troubleshooting Stack Operation


If the stack is having problems forming, you can isolate the issue with the show stacking ports command.
Stack Topology is a Ring Slot Port Node MAC Address ---- ---- ----------------*1 1 00:04:96:27:2c:9f *1 2 00:04:96:27:2c:9f 2 1 00:04:96:27:2f:52 2 2 00:04:96:27:2f:52 3 1 00:04:96:20:b4:05 3 2 00:04:96:20:b4:05 4 1 00:04:96:20:aa:25 4 2 00:04:96:20:aa:25 * - Indicates this node Flags: (C) Control path is Slot-1 Stack.8 # Port State ----------Operational Operational Operational Operational Operational Operational Operational Operational Flags ----CCCCCCB CB C-

active, (B) Port is Blocked

Slide 35

show stacking

Verifying Stack Operations


To verify stack operation, use the show stacking command. The show stacking command provides:
Node MAC Address, Slot, Stack State, Role, Flags
Active Topology is a Ring Node MAC Address Slot Stack State Role Flags ------------------ ---- ----------- ------- --*00:04:96:27:2c:9f 1 Active Master CA00:04:96:27:2f:52 2 Active Backup CA00:04:96:20:b4:05 3 Active Standby CA00:04:96:20:aa:25 4 Active Standby CA* - Indicates this node Flags: (C) Candidate for this active topology, (A) Active Node (O) node may be in Other active topology

Slide 36

show stacking details

Verifying Stack Operations (Continued)


Stacking Node 00:04:96:27:2c:9f information: Current: Stacking : Enabled Role : Master Priority : Automatic Slot number : 1 Stack state : Active Master capable? : Yes License level restriction : <none> In active topology? : Yes Factory MAC address : 00:04:96:27:2c:9f Stack MAC address : 02:04:96:27:2c:9f Alternate IP address : <none> Alternate gateway : <none> Stack Port 1: State : Operational Blocked? : No Control path active? : Yes Stack Port 2: State : Operational Blocked? : No Control path active? : Yes Configured: Stacking : Enabled Master capable? : Yes Slot number : 1 Stack MAC address : 02:04:96:27:2c:9f License level restriction : <none>
Slide 37

Summary
You should now be able to: Describe the benefits of SummitStack Stacking Technology Explain how stacking operates Identify the various components of stacking Configure a set of devices to employ stacking Verify the stacking configuration Troubleshoot stacking issues

Slide 38

Demonstration
Turn to the Configuring a Stacked Switch Demonstration in the ExtremeXOS Operations and Configuration - Lab Guide Rev. 12.1

Slide 39

Review Questions

2008 Extreme Networks, Inc. All rights reserved. ExtremeXOS Operation and Configuration, Version 12.1. Part number DOC-00919.

This presentation contains forward-looking statements that involve risks and uncertainties, including statements regarding our expectations as to products, trends and our performance. There can be no assurances that any forward-looking statements will be achieved, and actual results could differ materially from forecasts and estimates. For factors that may affect our business and financial results please refer to our filings with the Securities and Exchange Commission, including, without limitation, under the captions: Managements Discussion and Analysis of Financial Condition and Results of Operations, and Risk Factors, which is on file with the Securities and Exchange Commission (http://www.sec.gov). We undertake no obligation to update the forward-looking information in this release.

2008 Extreme Networks, Inc. All rights reserved. ExtremeXOS Operation and Configuration, Version 12.1. Part number DOC-00919.

The End

2008 Extreme Networks, Inc. All rights reserved. ExtremeXOS Operation and Configuration, Version 12.1. Part number DOC-00919. 2008 Extreme Networks, Inc. All rights reserved. ExtremeXOS Operation and Configuration, Version 12.1. Part number DOC-00919.