Alcatel OmniSwitch 6350-10, OmniSwitch 6350-P10, OmniSwitch 6350-48, OmniSwitch 6350-P48, OmniSwitch 6350-24 User Manual

Part No. 060406-10, Rev. C
October 2016

OmniSwitch 6350

Hardware Users Guide

enterprise.alcatel-lucent.com

This user guide documents OmniSwitch 6350 hardware, including chassis and associated components.
The specifications described in this guide are subject to change without notice.

enterprise.alcatel-lucent.com Alcatel-Lucent and the Alcatel-Lucent Enterprise logo are trademarks of
Alcatel-Lucent. To view other trademarks used by affiliated companies of ALE Holding, visit:
enterprise.alcatel-lucent.com/trademarks. All other trademarks are the property of their respective owners.
The information presented is subject to change without notice. Neither ALE Holding nor any of its affiliates
assumes any responsibility for inaccuracies contained herein. (July 2015)

26801 West Agoura Road

Calabasas, CA 91301

[phone] FAX [phone]

Service & Support Contact Information

North America: 800-995-2696

Latin America: 877-919-9526

EMEA: [phone] (Toll Free) or [phone]

Asia Pacific: [phone]

Web: service.esd.alcatel-lucent.com

Email: [e-mail]

Contents

About This Guide ..........................................................................................................ix

Supported Platforms ..........................................................................................................ix

Who Should Read this Manual? .........................................................................................x

When Should I Read this Manual? .....................................................................................x

What is in this Manual? ...................................................................................................... x

What is Not in this Manual? ...............................................................................................x

How is the Information Organized? ................................................................................... x

Documentation Roadmap ......................................................................................... .... ... ..xi

Related Documentation ...................................................................................................xiii

Published / Latest Product Documentation .....................................................................xiv

Technical Support ...........................................................................................................xiv

Documentation Feedback ................................................................................................xiv

Chapter 1 OmniSwitch 6350 Switches ......................................................................................1-1

Chassis Configurations ....................................................................................................1-1

10-Port Models .........................................................................................................1-1

24-Port Models .........................................................................................................1-1

48-Port Models .........................................................................................................1-1

OmniSwitch 6350 Feature Overview ..............................................................................1-2

Security Features ......................................................................................................1-2

Availability Features ................................................................................................1-2

Software Rollback .............................................................................................1-2

Hot Swapping ....................................................................................................1-2

Hardware Monitoring .................................. .... .... .... ..........................................1-2

Chapter 2 Getting Started ...........................................................................................................1-1

Installing the Hardware ...................................................................................................1-1

Items Required ...................................................................................... .... .... ...........1-1

Site Preparation ........................................................................................................1-1

Environmental Requirements ............................................................................1-1

Electrical Requirements .....................................................................................1-1

Unpacking and Installing the Switch .......................................................................1-4

Items Included ..................................................... .... ... .... ...................................1-4

Weight Considerations ......................................................................................1-4

Airflow Considerations .....................................................................................1-5

Mounting the Switch .......................................................................................................1-5

OmniSwitch 6350 Hardware Users Guide October 2016 iii

Contents

Connections and Cabling ................................................................................................1-6

Serial Connection to the Console Port ...............................................................1-6

Serial Connection Default Settings ...................................................................1-6

Booting the Switch ..........................................................................................................1-7

Component LEDs ..............................................................................................1-7

Your First Login Session ................................................................................................1-8

Logging In to the Switch ..........................................................................................1-8

Unlocking Session Types .................................................................................. .... ...1-9

Changing the Login Password ................................................................................1-10

Setting the System Time Zone ............................................................................... 1 -10

Setting the Date and Time ...................................................................................... 1 -10

Setting Optional Parameters ...................................................................................1-11

Specifying an Administrative Contact ........................................ .... .... .... .........1-11

Specifying a System Name ..............................................................................1-11

Specifying the Switch’s Location ....................................................................1-11

Viewing Your Changes ..........................................................................................1-11

Saving Your Changes .............................................................................................1-11

Chapter 3 OmniSwitch 6350 Chassis and Hardware Components ..................................2-1

OmniSwitch 6350-10 ......................................................................................................2-2

Chassis Features .................................................................................................... ...2-2

Front Panel ...............................................................................................................2-2

OmniSwitch 6350-10 Rear Panel .............................................................................2-3

OmniSwitch 6350-P10 ....................................................................................................2-5

Chassis Features .................................................................................................... ...2-5

Front Panel ...............................................................................................................2-5

OmniSwitch 6350-P10 Rear Panel ...........................................................................2-6

OmniSwitch 6350-24 ......................................................................................................2-8

Chassis Features .................................................................................................... ...2-8

Front Panel ...............................................................................................................2-8

OmniSwitch 6350-24 Rear Panel .............................................................................2-9

OmniSwitch 6350-24 Internal AC Power Supply ....................................................2-9

OmniSwitch 6350-P24 ..................................................................................................2-11

Chassis Features .................................................................................................... .2-11

Front Panel .............................................................................................................2-11

OmniSwitch 6350-P24 Rear Panel .........................................................................2-12

OmniSwitch 6350-P24 Internal AC Power Supply ................................................2-12

OmniSwitch 6350-48 ....................................................................................................2-14

Chassis Features .................................................................................................... .2-14

Front Panel .............................................................................................................2-14

OmniSwitch 6350-48 Rear Panel ...........................................................................2-15

OmniSwitch 6350-48 Internal AC Power Supply ..................................................2-15

OmniSwitch 6350-P48 ..................................................................................................2-17

Chassis Features .................................................................................................... .2-17

Front Panel .............................................................................................................2-17

OmniSwitch 6350-P48 Rear Panel .........................................................................2-18

OmniSwitch 6350-P48 Internal AC Power Supply ................................................2-19

iv OmniSwitch 6350 Hardware Users Guide October 2016

Contents

OmniSwitch 6350 LED Status ......................................................................................2-21

AC Power Cords ...........................................................................................................2-22

Specifications .........................................................................................................2-22

Console Port ..................................................................................................................2-23

Serial Connection Default Settings ........................................................................2-23

Port Pinouts ............................................... .... .... ....................................................... .....2-24

RJ-45 Console Port – Connector Pinout ................................................................2-24

10/100 Ethernet Port – RJ-45 Pinout (non-PoE) .................................................... 2-24

Gigabit Ethernet Port – RJ-45 Pinout .....................................................................2-24

10/100/1000 Mbps Power over Ethernet Port – RJ-45 Pinout ..............................2-25

Overtemp Condition ..................................................................................................... .2-25

Chapter 4 Managing OmniSwitch 6350 Stacks .....................................................................3-1

In This Chapter ................................................................................. .... .... .... ...................3-1

OmniSwitch 6350 Stacking Specifications .............................................................. 3-2

OmniSwitch 6350 Stack Overview .................................................................................3-2

OmniSwitch 6350 Stacking/Standalone Mode ...............................................................3-3

Roles Within the Stack ....................................................................................................3-3

Primary and Secondary Management Modules .......................................................3-3

Primary Management Module Selection ...........................................................3-6

Secondary Management Module Selection ....................................................... 3-9

Idle Module Role ....................................................................................................3-11

Pass-Through Mode ...............................................................................................3-12

Recovering from Pass-Through Mode (Duplicate Slot Numbers) ..................3-13

Stack Cabling ........................................................ .... .... ................................................3-16

Redundant Stacking Cable Connection ..................................................................3-17

Checking Redundant Stacking Cable Status ..........................................................3-18

Slot Numbering .............................................................................................................3-19

Dynamic Slot Number Assignment ........................................................................3-20

Manual Slot Number Assignment ..........................................................................3-22

Reverting to the Dynamic Slot Numbering Model ..........................................3-23

Hot-Swapping Modules In a Stack ...............................................................................3-24

Removing Switches from an Existing Stack ..........................................................3-24

Inserting Switches Into an Existing Stack ..............................................................3-24

Merging Stacks .......................................................................................................3-25

Reloading Switches .......................................................................................................3-26

Reloading the Primary Management Module ........................................................3-26

Reloading the Secondary Management Module ....................................................3-28

Reloading Switches with Idle Roles .......................................................................3-30

Reloading Switches in Pass-Through Mode ..........................................................3-30

Reloading All Switches in a Stack .........................................................................3-31

Software Synchronization During a Full Reload .............................................3-31

Effects of Saved Slot Number Information on the Reload Process .................3-31

Avoiding Split Stacks .............................................................................................3-33

Changing the Secondary Module to Primary ................................................................3-34

OmniSwitch 6350 Hardware Users Guide October 2016 v

Contents

Synchronizing Switches in a Stack ...............................................................................3-36

Automatic Synchronization During a Full Reload .................................................3-36

Stack Split Detection (SSP) ..........................................................................................3-37

Stack Split Key Components and Terms ................................................................3-37

Basic Operation ................................................................................. .....................3-38

Protection States .....................................................................................................3-38

Stack Split Recovery .......................................................................................3-38

Monitoring the Stack .....................................................................................................3-40

Chapter 5 Mounting OmniSwitch 6350 Switches ................................................................... 4-1

General Installation Recommendations ..........................................................................4-2

Airflow Recommendations ......................................................................................4-2

Mechanical Loading .................................................................................................4-4

Circuit Overloading ..................................................................................................4-4

Reliable Earthing ......................................................................................................4-4

General Table-Mounting Guidelines ........................................................................ 4-4

Rack-Mounting ...............................................................................................................4-5

Installing Rack Mount Flanges ................................................................................4-5

Installing the Chassis In the Rack ............................................................................4-7

Connecting the Chassis to a Power Source ..................................................................... 4-8

AC Power Supply Connections ................................................................................4-8

Powering On a Chassis ......................................................................................4-8

Chapter 6 Booting OmniSwitch 6350 Switches ...................................................................... 5-1

Booting an OmniSwitch ...........................................................................................5-1

Component LEDs ..............................................................................................5-1

Console Port ....................................................................................................................5-2

Serial Connection Default Settings ..........................................................................5-2

Modifying the Serial Connection Settings ...............................................................5-2

Monitoring the Chassis ...................................................................................................5-4

Checking the Overall Chassis Status ........................................................................5-4

Checking the Temperature Status ............................................................................5-4

Viewing the Power Supply Status ............................................................................ 5-5

Additional Monitoring Commands ..........................................................................5-5

Using LEDs to Visually Monitor the Chassis ..........................................................5-5

Chapter 7 Managing Power over Ethernet (PoE) .................................................................. 6-1

In This Chapter ................................................................................. .... .... .... ...................6-2

Power over Ethernet Specifications ................................................................................6-3

Viewing PoE Power Supply Status .................................................................................6-4

vi OmniSwitch 6350 Hardware Users Guide October 2016

Contents

Configuring Power over Ethernet Parameters .................................................................6-4

Power over Ethernet Defaults ..................................................................................6-4

Understanding and Modifying the Default Settings .................................................6-4

PoE Class Detection .................................................................................. .... .... .......6-5

Setting the PoE Operational Status ....................................................................6-5

Configuring the Total Power Available to a Port ..............................................6-6

Configuring the Total Power Available to a Switch .........................................6-6

Setting Port Priority Levels ...............................................................................6-7

Understanding Priority Disconnect .................................................................................6-8

Setting Priority Disconnect Status ............................................................................6-8

Disabling Priority Disconnect ...........................................................................6-8

Enabling Priority Disconnect ............................................................................6-8

Monitoring Power over Ethernet via CLI .....................................................................6-10

Appendix A Regulatory Compliance and Safety Information .............................................. A-1

Declaration of Conformity: CE Mark ............................................................................A-1

Waste Electrical and Electronic Equipment (WEEE) Statement ...................................A-3

Standards Compliance ....................................................................................................A-4

Safety Standards ......................................................................................................A-4

EMC Standards .......................................................................................................A-4

Environmental Standards ........................................................................................A-4

FCC Class A, Part 15 ..............................................................................................A-5

Canada Class A Statement ........................................................................ ..............A-5

JATE ........................................................................................................................A-5

CISPR22 Class A Warning .....................................................................................A-5

Korea Emissions Statement .....................................................................................A-6

VCCI .......................................................................................................................A-6

Class A Warning for Taiwan and Other Chinese Markets ......................................A-6

Network Cable Installation Warning .............................................................................A-7

Translated Safety Warnings ........................................................................................... A-7

Chassis Lifting Warning ........................................................................ .... ..............A-7

Electrical Storm Warning ........................................................................................ A-7

Installation Warning ................................................................................................A-8

Invisible Laser Radiation Warning .........................................................................A-8

Power Disconnection Warning ................................................................................A-8

Proper Earthing Requirement Warning ...................................................................A-9

Read Important Safety Information Warning ........................................................ A-10

Restricted Access Location Warning ....................................................................A-10

Wrist Strap Warning ..............................................................................................A-11

OmniSwitch 6350 Hardware Users Guide October 2016 vii

Contents

Instrucciones de seguridad en español .........................................................................A-12

Advertencia sobre el levantamiento del chasis .....................................................A-12

Advertencia de las tapaderas en blanco .................................................................A-12

Advertencia en caso de tormenta eléctrica ............................................................ A-12

Advertencia de instalación ....................................................................................A-12

Advertencia de radiación láser invisible ...............................................................A-12

Advertencia de la batería de litio ...........................................................................A-12

Advertencia sobre la tensión de operación ............................................................A-12

Advertencia sobre la desconexión de la fuente .....................................................A-12

Advertencia sobre una apropiada conexión a tierra .............................................. A-13

Leer “información importante de seguridad” ........................................................ A-13

Advertencia de acceso restringido .........................................................................A-13

Advertencia de pulsera antiestática .......................................................................A-13

Clase de seguridad ................................................................................. .... .... .... ....A-13

viii OmniSwitch 6350 Hardware Users Guide October 2016

About This Guide

This OmniSwitch 6350 Hardware Users Guide describes your switch hardware components and basic
switch hardware procedures.

Supported Platforms

The information in this guide applies to the following products:

• OS6350-10

• OS6350-P10

• OS6350-24

• OS6350-P24

• OS6350-48

• OS6350-P48

OmniSwitch 6350 Hardware Users Guide October 2016 page ix

Who Should Read this Manual? About This Guide

Who Should Read this Manual?

The audience for this users guide is network administrators and IT support personnel who need t o con fig­ure, maintain, and monitor switches and routers in a live network. However, anyone wishing to gain
knowledge on the OmniSwitch 6350 hardware will benefit from the material in this guide.

When Should I Read this Manual?

Read this guide as soon as you are ready to familiarize yourself with your switch hardware components.
You should have already stepped through the first login procedures.

You should already be familiar with the very basics of the switch hardwa re, such as module LEDs and
module installation procedures. This manual will help you understand your switch hardware components
(e.g., chassis, cables, power supplies, etc.) in greater depth.

What is in this Manual?

This users guide includes the following hardware-related information:

• Descriptions of switch configurations.

• Descriptions of “availability” features.

• Descriptions of chassis types.

• Instructions for mounting the chassis.

• Descriptions of hardware components (status LEDs, chassis, cables, etc.).

• Managing a chassis.

• Hardware-related Command Line Interface (CLI) commands

What is Not in this Manual?

The descriptive and procedural information in this manual focuses on switch hardware. It includes infor­mation on some CLI commands that pertain directly to hardware configuration, bu t it is not intended as a
software users guide. There are several OmniSwitch 6350 users guides that focus on switch software
configuration. Consult those guides for detailed information and examples for configuring your switch
software to operate in a live network environment. See “Documentation Roadmap” on page -xi and

“Related Documentation” on page -xiii for further information on software configuration guides available

for your switch.

How is the Information Organized?

This users guide provides an overview of OmniSwitch 6350 switches, specificat ions of the hardware
components, steps for setting up and managing OmniSwitch 6350 switches, and an overview and proce­dures for managing Power over Ethernet (PoE).

page x OmniSwitch 6350 Hardware Users Guide October 2016

About This Guide Documentation Roadmap

Documentation Roadmap

The OmniSwitch user documentation suite wa s design ed to supply you with information at several critical
junctures of the configuration process.The following section outlines a roadmap of the manuals that will
help you at each stage of the configuration process. Under each stage, we point you to the manual or
manuals that will be most helpful to you.

Stage 1: Using the Switch for the First Time

Pertinent Documentation: Getting Started Chapter

Release Notes

The Getting Started chapter i n this manual provid es all th e info rmation you need to get y our switch u p and
running the first time. This chapter provides information on unpacking the switch, installing power
supplies, unlocking access control, setting the switch’s IP address, and setting up a password. It also
includes succinct overview information on fundamental aspects of the switch, such as hardware LEDs, the
software directory structure, CLI conventions, and web-based management.

At this time you should also familiarize yourself with the Release Notes that accompanied your switch.
This document includes important information on feature limitations that are not included in other user
guides.

Stage 2: Gaining Familiarity with Basic Switch Functions

Pertinent Documentation: Hardware Users Guide

Switch Management Guide

Once you have your switch up and running, you will want to begin investigating basic aspects of its hard
ware and software. Information about switch hardware is provided in the Hardware Users Guide. This
guide provides specifications, illustrations, and descriptions of all hardware components—e.g., chassis,
power supplies, etc.

The Switch Management Guide is the primary user guide for the basic software features on a switch. This
guide contains information on the switch directory structure, basic file and directory utilities, switch
access security, SNMP, and web-based management. It is recommended that you read this guide before
connecting your switch to the network.

OmniSwitch 6350 Hardware Users Guide October 2016 page xi

Documentation Roadmap About This Guide

Stage 3: Integrating the Switch Into a Network

Pertinent Documentation: Network Configuration Guide

When you are ready to connect your switch to the network, you will need to learn how the OmniSwitch
implements fundamental softwa re features, such as 802.1Q, VLANs, and Spanning Tree. The Network
Configuration Guide contains overview information, procedures and examples on how standard network­ing technologies are configured in the OmniSwitch.

Anytime

TheCLI Reference Guide contains comprehensive information on all CLI commands supported by the
switch. This guide includes syntax, default, usage, example, related CLI command, and CLI-to-MIB vari­able mapping information for all CLI commands supported by the switch. This guide can be consulted
anytime during the configuration process to find detailed and specific information on each CLI command.

page xii OmniSwitch 6350 Hardware Users Guide October 2016

About This Guide Related Documentation

Related Documentation

The following are the titles and descriptions of OmniSwitch 6350-related user manuals:

• OmniSwitch 6350 Hardware Users Guide

Detailed technical specifications and procedures for the OmniSwitch chassis and components.

• CLI Reference Guide

Complete reference to all CLI commands supported on OmniSwitch 6350 products. Includes syntax
definitions, default values, examples, usage guidelines and CLI-to-MIB variable mappings.

• Switch Management Guide

Includes procedures for readying an individual switch for integration into a network. Topics include
the software directory architecture, image rollback protections, authenticated switch access, managing
switch files, system configuration, using SNMP, and using web management software (WebView).

• Network Configuration Guide

Includes network configuration procedures and descriptive information on all the major software
features and protocols included in the base software package. Chapters cover Layer 2 information
(Ethernet and VLAN configuration), Layer 3 information (routing protocols, such as RIP), security
options (authenticated VLANs), Quality of Service (QoS), and link aggregation.

• Transceivers Guide

Includes SFP transceiver specifications and product compatibility information.

• Technical Tips, Field Notices

Includes information published by Alcatel-Lucent’s Customer Support group.

• Release Notes and Upgrade Instructions

Includes open problem reports, feature exceptions, and other important information on the features
supported in the current release and any limitations to their support.

OmniSwitch 6350 Hardware Users Guide October 2016 page xiii

Published / Latest Product Documentation About This Guide

Published / Latest Product Documentation

All user guides for the OmniSwit ch Series are included on the Alcatel-Lucent public website. This web site
also includes user guides for other Alcatel-Lucent Enterprise prod ucts.

The latest user guides can be found on our website at:

http://enterprise.alcatel-lucent.com/UserGuides

Technical Support

An Alcatel-Lucent Enterprise service agreement brings your company the assurance of 7x24 no-excuses
technical support. You’ll also receive regular software updates to maintain and maximize your Alcatel­Lucent Enterprise product’s features and functionality and on-site hardware replacement through our
global network of highly qualified service delivery partners. Additionally, with 24-hour-a-day access to
Alcatel-Lucent’s Service and Support web page, you’ll be able to view and update any case (open or
closed) that you have reported to Alcatel-Lucent’s technical support, open a new case or access helpful
release notes, technical bulletins, and manuals. For more information on Alcatel-Lucent Enterprise’s
Service Programs, see our web page at service.esd.alcatel-lucent.com, call us at 1-800-995-2696, or email
us at [e-mail].

Documentation Feedback

Alcatel-Lucent values comments on the quality and usefulness of the documentation. To send comments
on the OmniSwitch documentation use the following email address: [e-mail].

For document identification it's helpful to include the Document Title, Part Number and Revision (which
can be found on the title page) with any comments.

page xiv OmniSwitch 6350 Hardware Users Guide October 2016

1 OmniSwitch 6350 Switches

OmniSwitch 6350 switches are fixed-configuration Gigabit Ether net switches available in 10-, 24-, and
48-port models. Options also include 10-, 24-, and 48-port Power-over-E thernet (PoE). All models provide
internal AC power.

Chassis Configurations

10-Port Models

• OmniSwitch 6350-10: Provides eight (8) 10/100/1000 BaseT ports; two (2) RJ-45/SFP combo ports.

The chassis features fanless design and internal AC power.

• OmniSwitch 6350-P10: Provides eight (8) 10/100/1000 BaseT PoE ports; two (2) RJ-45/SFP combo

ports. The chassis features fanless design and internal AC power.

24-Port Models

• OmniSwitch 6350-24: Provides 24 10/100/1000 BaseT port s and four (4) fixed SFP ports. The chassis

features fanless design and internal AC power.

• OmniSwitch 6350-P24: Provides 24 PoE 10/100/1000 PoE ports and four (4) fixed SFP ports.

The chassis provides three (3) fans and internal AC power.

48-Port Models

• OmniSwitch 6350-48: Provides 48 10/100/1000 BaseT ports and four (4) fixed SFP ports.

The chassis provides one (1) fan and internal AC power.

• OmniSwitch 6350-P48: Provides 48 10/100/1000 PoE ports and four (4) fixed SFP ports.

The chassis provides four (4) fans and internal AC power.

OmniSwitch 6350 Hardware Users Guide October 2016 page 1-1

OmniSwitch 6350 Feature Overview OmniSwitch 6350 Switches

OmniSwitch 6350 Feature Overview

Security Features

OmniSwitch 6350 switches offer security features for network access control, policy enforcement
and attack containment, enabling fully secure networks and OmniVista Network Management System
(NMS) support.

Availability Features

OmniSwitch 6350 switches incorporate advanced Alcatel-Lucent Operating System (AOS) protocol s to
ensure high availability for mission critical applications. Availability features are hardware- and software­based safeguards that help to prevent the loss of data flow in the unlikely event of a subsystem failure.

In addition, some availability features allow users to maintain or replace hardware components without
powering off the switch or interrupting switch operations. Combined, these features provide added
resiliency and help to ensure that the switch or virtual chassis is consistently available for high-impact
network operations.

Hardware-related availability features include:

• Software Rollback

• Hot Swapping

• Hardware Monitoring

Software Rollback

Software rollback (also referred to as image rollback) essentially allows the switch to return to a prior “la st
known good” version of software in the event of a system software problem. The switch controls software
rollback through its resilient directory structure design (i.e., /flash/working and /flash/certified).

For detailed information on the software rollback feature, as well as the switch’s /flash/working and

/flash/certified directories, refer to the “Managing CMM Directory Content” chapter in the Switch
Management Guide.

Hot Swapping

Hot swapping refers to the action of adding, removing, or replacing components without powering off
switches or disrupting other components.This feature facilitates hardware upgrades and maintenance and
allows users to easily replace components in the unlikely event of hardware failure.

The following components can be hot swapped:

• SFP transceivers. Refer to OmniSwitch 6350 Transceivers Guide for more information.

Hardware Monitoring

Automatic Monitoring

Automatic monitoring refers to the switch’s built-in sensors that automatically monitor operations. If an
error is detected (e.g., over-threshold temperature), the switch immediately sends a trap to the user. The
trap is displayed on the console in the form of a text error message.

page 1-2 OmniSwitch 6350 Hardware Users Guide October 2016

OmniSwitch 6350 Switches OmniSwitch 6350 Feature Overview

LEDs

LEDs, which provide visual status information, are provided on the chassis front panel. LEDs are used to
indicate conditions such as hardware and software status, temperature errors, link integrity, data flow, etc.
For detailed LED descriptions, refer to Chapter 3, “OmniSwitch 6350 Chassis and Hardware

Components.”

User-Driven Monitoring

User-driven hardware monitoring refers to CLI commands that are entered by the user in order to access
the current status of hardware components. The user enters “show” commands that output information to
the console. Monitoring information for chassis components, such as the optional back up power supply,
chassis temperature sensor, and chassis fans is provided in Chapter 3, “OmniSwitch 6350 Chassis and

Hardware Components.” The show commands for all the featu res are described in detail in the CLI

Reference Guide.

OmniSwitch 6350 Hardware Users Guide October 2016 page 1-3

OmniSwitch 6350 Feature Overview OmniSwitch 6350 Switches

page 1-4 OmniSwitch 6350 Hardware Users Guide October 2016

2 Getting Started

Installing the Hardware

Items Required

• Grounding wrist strap

• Phillips screwdriver

• Flat-blade screwdriver

Site Preparation

Environmental Requirements

OmniSwitch 6350 switches have the following environmental and airflow requirements:

• The installation site must maintain a temperature between 0° and 45° Celsius (32° and 113° Fahrenhe it)

and not exceed 95 percent maximum humidity (non-condensing) at any time.

• Be sure to allow adequate room for proper air ventilation at the front, back, and sides of the switch.

Refer to “Airflow Considerations” on page 2-5 for minimum clearance requirements. No clearance is
necessary at the top or bottom of the chassis.

Electrical Requirements

Note. Alcatel-Lucent switches must be installed by a professional installer. It is the responsibility of the
installer to ensure that proper grounding is available and that the installation meets applicable local and
national electrical codes.

OmniSwitch 6350 Hardware Users Guide October 2016 page 2-1

Installing the Hardware Getting Started

Reliable Earthing

Reliable earthing of rack-mounted equipment should be maintained. P articular attention should be given
to supply connections other than direct connections to the branch (e.g., use of power strips).

OmniSwitch 6350 switches have the following general electrical requirements:

• Each switch requires one grounded electrical outlet for each power supply installed in the chassis.

• OmniSwitch 6350 switches offer both AC and DC power supply support.

• For switches using AC power connections, each supplied AC power cord is 2 meters (approx. 6.5
feet). Do not use extension cords.

Redundant AC Power. It is recommended that each AC outlet resides on a
separate circuit. With redundant AC power, if a single circuit fails, the switch’s
remaining power supplies (on separate circuits) can remain operational.

For switches using DC power, refer to the “DC Power Supply Connections” for more information.

Electrical Surge Warning

In order to help protect equipment against electrical surges please take note of the following
recommendations and guidelines:

1. Earth grounding of all devices is fundamental to ensure long term reliability.

• All electrical equipment must be installed by a qualified, licensed electrician.

• Every power supply that is connected to building power should be earth grounded.

• Earth grounding for the power cable, should be verified to be 0.01 ohm or less.

• Each switch should be grounded to same earth ground as the power supply.

• Each powered device, such as an AP or camera, should be connected to earth ground.

• Each surge suppression device should be connected to earth ground.

2. Shielded cables (STP) offer some minimal level of additional protection over unshielded Ethernet
cables (UTP) but the use of a surge protector is still recommended.

• It is suggested to use STP Cat5e or better for 1Gbps Ethernet switches for any outdoor application or
applications where Ethernet cables come in close proximity to alternating current conductors.

• Always install cables according to manufacturer requirements.

3. For any connections where integrity of the cabling within a building ground is questionable (i.e
outdoor connections), copper Ethernet ports must be connected with an appropriate surge
protection device, inline, between the PSE and PD per the manufacturer’s recommendations for
connection and grounding.

page 2-2 OmniSwitch 6350 Hardware Users Guide October 2016

Installing the Hardware Getting Started

4. Caution should be taken for any cable connected to any outdoor device, not only on the device
grounding, but to ensure that any outdoor device cables that could carry surge currents, do not pass
those surge currents to upstream Ethernet switches.

Caution - Category 5e, Category 6, and Category 6a cables can store large amounts of static
electricity due to the dielectric properties of their construction materials in addition, this build up
of electricity could lead to a Cable Discharge Event (CDE). A CDE can occur due to the differential in
charges on the cable and the equipment it’s being connected to. It is recommended that installers
momentarily ground all copper Ethernet cables (especially in new cable runs) to a suitable and safe
earth ground before connecting them to the port.

page 2-3 OmniSwitch 6350 Hardware Users Guide October 2016

Installing the Hardware Getting Started

Unpacking and Installing the Switch

To protect your switch components from damage, read all unpacking recommendation s and instructions
carefully before beginning.

Unpack your OmniSwitch 6350 chassis as close as possible to the location where it will be in stalled.

Items Included

Your OmniSwitch 6350 includes the following items:

• OmniSwitch chassis

• Transceivers, per order

• Rack mount brackets

• Country-specific power cord(s)

• Assorted instructional cards, anti-static bags and additional packaging

Weight Considerations

Check the specifications table for the OmniSwitch 6350 being installed for chassis weights.

page 2-4 OmniSwitch 6350 Hardware Users Guide October 2016

Mounting the Switch Getting Started

}

}

Rear. 6 inches minimum
at rear of chassis.

Front. 6 inches minimum
at front of chassis.

Sides. 2 inches minimum
at left and right sides.

Airflow Considerations

To ensure proper airflow, be sure that your switch is placed in a well-ventilated area and provide minimum
recommended clearance at the front, back and sides of the switch.

Never obstruct chassis air vents.

Chassis Top View

Note. Clearance is not required at the top and bottom of the chassis.

Mounting the Switch

For information on mounting OmniSwitch 6350 switches, refer to Chapter 3, “OmniSwitch 6350 Chassis and

Hardware Components.”

page 2-5 OmniSwitch 6350 Hardware Users Guide October 2016

Connections and Cabling Getting Started

Connections and Cabling

Once your switch is properly installed, you should connect all network and management cables required for
your network applications. Connections may include:

• DB9-to-RJ-45 cable to the console connector

• Cables to 10/100/1000 Ethernet or SFP ports

Note. For additional information on cabling connections, refer to the OmniSwitch AOS Release 6 Switch

Management Guide.

Serial Connection to the Console Port

The console port provides a serial connection to the switch using a USB connector and is required when
logging into the switch for the first time. By default, this connector provides a DCE console connection.

Serial Connection Default Settings

baud rate 9600
parity none
data bits (word size) 8
stop bits 1

For information on modifying these settings, refer to the Switch Management Guide.

page 2-6 OmniSwitch 6350 Hardware Users Guide October 2016

Booting the Switch Getting Started

Booting the Switch

Now that you have installed the switch components and connected network and management cables, you can
boot the switch. To boot the switch, plug the po wer supply cord into an easily-accessible, properly grounded
power outlet. (Do not use extension cords.) The switch will power on and boot automatically.

Note. For a few seconds, at the beginning of the boot up process, random characters may briefly display
on the console of an OS6350. This is due to an initial baud rate mismatch. As soon as the bootrom is
initialized, the issue is automatically resolved.

Component LEDs

During the boot process, component LEDs will flash and change color, indi cating different stages of the boot.
Following a successful boot, chassis LEDs should display as follows:

OK1 Solid Green
PRI Solid Green
PWR Solid Green

Note. If the LEDs do not display as indicated, make sure the boot process is complet e. If t he LEDs do not

display as indicated following a complete boot sequence, contact Alcatel-Lucent Enterprise Customer
Support. For information on LED states, refer to “OmniSwitch 6350 LED Status” on page 3-21.

Once the switch has completely booted and you have accessed your computer’s terminal emulation software
via the console port, you are ready to log in to the switch’s Command Line Interface (CLI) and configure basic
information. Continue to “Your First Login Session” on page 2-8.

page 2-7 OmniSwitch 6350 Hardware Users Guide October 2016

Your First Login Session Getting Started

Your First Login Session

In order to complete the setup process for the switch, you must complete the following steps during your first
login session:

• Log in to the switch

• Unlock session types

• Change the login password

• Set the date and time

• Set optional system information

• Save your changes

Important. You must be connected to the switch via the console port before initiating your first

login session.

Logging In to the Switch

When you first log in to the switch, you will be prompted for a login name and password. Use the switch’s
default settings:

• Login: admin

• Password: switch

The default welcome banner, which includes informatio n such as the current software version and system date,
is displayed followed by the CLI command prompt:

Welcome to the Alcatel-Lucent OmniSwitch 6350
Software Version 6.7.1.80.R01 Development, July 08, 2015.

Copyright(c), ALE USA Inc., 2015. All Rights reserved.

OmniSwitch(TM) is a trademark of Alcatel-Lucent Enterprise registered
in the United States Patent and Trademark Office.

->

Note. A user account includes a login name, password, and user privileges. Privileges determine whether
the user has read or write access to the switch and which commands the user is authorized to execute. For
detailed information on setting up and modifying user accounts, refer to the Switch Management Guide.

page 2-8 OmniSwitch 6350 Hardware Users Guide October 2016

Your First Login Session Getting Started

Unlocking Session Types

Security is a key feature on OmniSwitch 6350 switches. As described on page 2-8, when you access the switch
for the first time, you must use a direct console port connection. All other session types (Telnet, FTP,
WebView, and SNMP) are locked out until they are manually unlocked by the user.

The CLI command used to unlock session types is aaa authentication.

Note. When you unlock session types, you are granting switch access to non-local sessions (e.g., Telnet).
As a result, users who know the correct user login and password will have remote access to the switch. For
more information on switch security, refer to the Switch Management Guide.

Unlocking All Session Types

To unlock all session types, enter the following command syntax at the CLI prompt:

-> aaa authentication default local

Unlocking Specified Session Types

You can also unlock session types on a one-by-one basis. For example, to unlock Telnet sessions only, enter
the following command:

-> aaa authentication telnet local

To unlock WebView (HTTP) sessions only, enter the following command:

-> aaa authentication http local

You cannot specify more than one session type in a single command line. However, you can still unlock
multiple session types by using the aaa authentication command in succession. For example:

-> aaa authentication http local

-> aaa authentication telnet local

-> aaa authentication ftp local

Refer to the CLI Reference Guide for complete aaa authentication command syntax options.

page 2-9 OmniSwitch 6350 Hardware Users Guide October 2016

Your First Login Session Getting Started

Changing the Login Password

Change the login password for admin user sessions by following the steps below:

1 Be sure that you have logged into the switch as user type admin (see “Logging In to the Switch” on

page 2-8).

2 Enter the keyword password and press Enter.
3 Enter your new password at the prompt.

Note. Be sure to remember or securely record all new passwords; overriding configured passwords on an
OmniSwitch is restricted.

4 You will be prompted to re-enter the password. Enter the password a second time.

New password settings are automatically saved in real time to the local user database; the user is not required
to enter an additional command in order to save the password information. Also note that new password
information is retained following a reboot. All subsequent login sessions, including those through the console
port, will require the new password to access the switch.

For detailed information on managing login information, including user names and passwords, refer to the
Switch Management Guide.

Setting the System Time Zone

The switch’s default time zone is UTC. If you require a time zone that is spe cifi c to y ou r region , or if you nee d
to enable Daylight Savings Time (DST) on the switch, you can configure these settings via the system
timezone and system daylight-savings-time commands.

For detailed information on configuring a time zone for the switch, refer to the Switch Management Guide.

Setting the Date and Time

Set the current time for the switch by entering system time, followed by the current time in hh:mm:ss.

To set the current date for the switch, enter system date, followed by the current date in mm/dd/yyyy.

page 2-10 OmniSwitch 6350 Hardware Users Guide October 2016

Your First Login Session Getting Started

Setting Optional Parameters

Specifying an Administrative Contact

An administrative contact is the person or department in charge of the switch. If a contact is specified, users
can easily find the appropriate network administrator if they have questions or comments about the switch.

To specify an administrative contact, use the system contact command.

Specifying a System Name

The system name is a simple, user-defined text description for the switch.

To specify a system name, use the system name command.

Specifying the Switch’s Location

It is recommended that you use a physical labeling system for locating and identifying your switch(es).
Examples include placing a sticker or placard with a unique identifier (e.g., the switch’s default IP address) on
each chassis.

However, if no labeling system has been implemented or if you need to determine a switch’s location from a
remote site, entering a system location can be very useful.

To specify a system location, use the system location command.

Viewing Your Changes

To view your current changes, enter show system at the CLI prompt.

Saving Your Changes

Once you have configured this basic switch information, save your changes by entering write memory at the
CLI command prompt.

page 2-11 OmniSwitch 6350 Hardware Users Guide October 2016

Your First Login Session Getting Started

page 2-12 OmniSwitch 6350 Hardware Users Guide October 2016

3 OmniSwitch 6350

Chassis and Hardware

Components

OmniSwitch 6350 (OS6350) switches are available in the chassis configurations as shown in the
table below:

OS6350-10 Eight (8) 10/100/1000 BaseT ports; two (2) RJ-45/ SFP combo

ports; fanless design; internal AC power.

OS6350-P10 Eight (8) 10/100/1000 BaseT PoE ports; two (2) RJ-45/SFP

combo ports; fanless design; internal AC power.

OS6350-24 (24) 10/100/1000 BaseT ports; four (4) fixed SFP ports;

fanless design; internal AC power.

OS6350-P24 (24) PoE 10/100/1000 BaseT ports; four (4) fixed SFP ports;

three (3) fans; internal AC power.

OS6350-48 (48) 10/100/1000 BaseT ports; four (4) fixed SFP ports;

one (1) fan; internal AC power.

OS6350-P48 (48) 10/100/1000 BaseT PoE ports; four (4) fixed SFP ports;

four (4) fans; internal AC power.

This chapter includes detailed information on these chassis types. Topics include:

• OmniSwitch 6350 chassis descriptions

• Technical specifications

• Power Supplies

• Cables and power cords

• Console port and pinout specifications

OmniSwitch 6350 Hardware Users Guide October 2016 page 3-1

OmniSwitch 6350-10 OmniSwitch 6350 Chassis and Hardware Components

G

A DEB CF

OmniSwitch 6350-10

Chassis Features

System status LEDs Internal AC Power Supply
(8) 10/100/1000Base-T Ports Console port (RJ-45)
(2) RJ-45/SFP 10/100/1000 combo ports USB port (USB 2.0)

Front Panel

OmniSwitch 6350-10 Front Panel

Item Description

A
B
C
D
E
F
G

Refer to “OmniSwitch 6350 LED Status” on page 3- 21 for LED status information.

(8) 10/100/1000Base-T Ports
Ethernet Port Status LEDs
Console Port
System Status LEDs
(2) RJ-45/SFP 10/100/1000 combo ports
Combo Port Status LEDs
USB Port

page 3-2 OmniSwitch 6350 Hardware Users Guide October 2016

OmniSwitch 6350 Chassis and Hardware Components OmniSwitch 6350-10

A B

OmniSwitch 6350-10 Rear Panel

Note. The figure shows a pre-production version of the chassis without product, safety, and compliance
information labels. All production versions of the chassis have these labels.

OmniSwitch 6350-10 Rear Panel

Item Description

A

Power Supply Connector

Internal AC power supply.

B

Grounding Block

Type LCD8-10A-L grounding lug

OmniSwitch 6350-10 Specifications
Fans None
Power Supplies One (1) internal power supply
Rack Unit Dimensions 1 RU
Dimensions (WxHxD) 21.5 cm (8.50 in) x 4.4 cm (1.73 in) x 29.21 cm (11.5 in)
Weight 1.97 kg (4.34 lb)
Operating Temperature 0°C to +45°C (32°F to +113°F)
Storage Temperature -40°C to +75°C (-40°F to +167°F)
Upper Threshold Temperature 71°C
Danger Threshold Temperature 80°C
Operating and Storage Humidity 5% to 95% non-condensing
Acoustic (dB) 0
RJ-45 10/100/1000 Ports 8
RJ-45/SFP 10/100/1000 Combo Ports 2
PoE Ports N/A
PoE Power Budget N/A

OmniSwitch 6350 Hardware Users Guide October 2016 page 3-3

OmniSwitch 6350-10 OmniSwitch 6350 Chassis and Hardware Components

OmniSwitch 6350-10 Specifications
Input Voltage 100 VAC to 240 VAC, 0.9 A, 50-60 Hz
Output Voltage 12 VDC, 2.5 A
Max Power 30 W

page 3-4 OmniSwitch 6350 Hardware Users Guide October 2016

OmniSwitch 6350 Chassis and Hardware Components OmniSwitch 6350-P10

G

A DEB CF

OmniSwitch 6350-P10

Chassis Features

System status LEDs Internal AC Power Supply
(8) 10/100/1000Base-T PoE ports Console port (RJ-45)
(2) RJ-45/SFP 10/100/1000 combo ports USB port (USB 2.0)

Front Panel

OmniSwitch 6350-P10 Front Panel

Item Description

A
B
C
D
E
F
G

Refer to “OmniSwitch 6350 LED Status” on page 3- 21 for LED status information.

(8) 10/100/1000 Power over Ethernet (PoE) Ports
Ethernet Port Status LEDs
Console Port
System Status LEDs
(2) RJ-45/SFP 10/100/1000 combo ports
Combo Port Status LEDs
USB Port

OmniSwitch 6350 Hardware Users Guide October 2016 page 3-5

OmniSwitch 6350-P10 OmniSwitch 6350 Chassis and Hardware Components

A BA B

OmniSwitch 6350-P10 Rear Panel

Note. The figure shows a pre-production version of the chassis without product, safety, and compliance
information labels. All production versions of the chassis have these labels.

OmniSwitch 6350-P10 Rear Panel

Item Description

A

Power Supply Connector

Internal AC power supply.

B

Grounding Block

Type LCD8-10A-L grounding lug

OmniSwitch 6350-P10 Specifications
Fans None
Power Supplies One (1) internal power supply
Rack Unit Dimensions 1 RU
Dimensions (WxHxD) 21.5 cm (8.50 in) x 4.4 cm (1.73 in) x 29.21 cm (11.5 in)
Weight 1.97 kg (4.34 lb)
Operating Temperature 0°C to +45°C (32°F to +113°F)
Storage Temperature -40°C to +75°C (-40°F to +167°F)
Upper Threshold Temperature 73°C
Danger Threshold Temperature 82°C
Operating and Storage Humidity 5% to 95% non-condensing
Acoustic (dB) 0
RJ-45 10/100/1000 Ports 8
RJ-45/SFP 10/100/1000 Combo Ports 2
PoE Ports 8
PoE Power Budget 120W

page 3-6 OmniSwitch 6350 Hardware Users Guide October 2016

OmniSwitch 6350 Chassis and Hardware Components OmniSwitch 6350-P10

OmniSwitch 6350-P10 Specifications
Input Voltage 100 VAC to 240 VAC, 2.2 A, 50-60 Hz
Output Voltage 54.5 VDC, 2.5 A
Max Power 150 W (30 W System Power; 120 W PoE Power)

OmniSwitch 6350 Hardware Users Guide October 2016 page 3-7

OmniSwitch 6350-24 OmniSwitch 6350 Chassis and Hardware Components

G

A D EB C F

OmniSwitch 6350-24

Chassis Features

System status LEDs Internal AC Power Supply
(24) 10/100/1000Base-T Ports Console port (RJ-45)
(4) Non-combo SFP Ports USB port (USB 2.0)

Front Panel

OmniSwitch 6350-24 Front Panel

Item Description

A
B
C
D
E
F
G

Refer to “OmniSwitch 6350 LED Status” on page 3- 21 for LED status information.

(24) 10/100/1000 BaseT Ethernet Ports
Ethernet Port Status LEDs
Console Port
System Status LEDs
Four (4) Fixed SFP Ports
SFP Port Status LEDs
USB Port

page 3-8 OmniSwitch 6350 Hardware Users Guide October 2016

OmniSwitch 6350 Chassis and Hardware Components OmniSwitch 6350-24

A B

OmniSwitch 6350-24 Rear Panel

Note. The figure shows a pre-production version of the chassis without product, safety, and compliance
information labels. All production versions of the chassis have these labels.

OmniSwitch 6350-24 Rear Panel

Item Description

A

B

Grounding Block

Type LCD8-10A-L grounding lug

Power Supply Connector

Internal AC power supply.

OmniSwitch 6350-24 Internal AC Power Supply

P/S Component Description

Model O mniSw itch 6350-24
Nominal Input Voltage 90-220 VAC
Maximum Output Power 30 W
Output Voltage 12V DC

OmniSwitch 6350 Hardware Users Guide October 2016 page 3-9

OmniSwitch 6350-24 OmniSwitch 6350 Chassis and Hardware Components

OS6350-24 Specifications

10/100/1000BaseT ports 24
SFP ports 4
Chassis Width 44.0 cm (17.32 in)
Chassis Height 4.4 cm (1.73 in) (1 RU)
Chassis Depth 23.87 cm (9.4 in)
Weight 4.08 kg (9.0 lb)
Operating Humidity 5% to 95%
Storage Humidity 5% to 95%
Operating Temperature 0C to +45C
Storage Temperature -40C to +75C
Upper Threshold Temperature 75C
Danger Threshold Temperature 80C

page 3-10 OmniSwitch 6350 Hardware Users Guide October 2016

OmniSwitch 6350 Chassis and Hardware Components OmniSwitch 6350-P24

G

A D EB C F

OmniSwitch 6350-P24

Chassis Features

System status LEDs Internal AC Power Supply
(24) 10/100/1000Base-T PoE ports Console port (RJ-45)
(4) Non-combo SFP Ports USB port (USB 2.0)

Front Panel

OmniSwitch 6350-P24 Front Panel

Item Description

A
B
C
D
E
F
G

Refer to “OmniSwitch 6350 LED Status” on page 3- 21 for LED status information.

(24) 10/100/1000 Power over Ethernet (PoE) Ports
Ethernet Port Status LEDs
Console Port
System Status LEDs
Four (4) Fixed SFP Ports
SFP Port Status LEDs
USB Port

OmniSwitch 6350 Hardware Users Guide October 2016 page 3-11

OmniSwitch 6350-P24 OmniSwitch 6350 Chassis and Hardware Components

A B

OmniSwitch 6350-P24 Rear Panel

Note. The figure shows a pre-production version of the chassis without product, safety, and compliance
information labels. All production versions of the chassis have these labels.

OmniSwitch 6350-P24 Rear Panel

Item Description

A

B

Grounding Block

Type LCD8-10A-L grounding lug

Power Supply Connector

Internal AC power supply.

OmniSwitch 6350-P24 Internal AC Power Supply

P/S Component Description

Model O mniSwitch 6350-P24
Nominal Input Voltage 90-220 VAC
Maximum Output Power 525 W
PoE Power Budget 380 W
Output Voltage 12V DC/54V DC

page 3-12 OmniSwitch 6350 Hardware Users Guide October 2016

OmniSwitch 6350 Chassis and Hardware Components OmniSwitch 6350-P24

OmniSwitch 6350-P24 Specifications

Standard(s) Supported 802.3at
10/100/1000BaseT Power over

24

Ethernet (PoE) Ports
SFP ports 4
Chassis Width 44.0 cm (17.32 in)
Total Power Budget 525 W
System Power Budget 145 W
PoE Power Budget 380 W
Chassis Height 4.4 cm (1.73 in) (1 RU)
Chassis Depth 23.87 cm (9.4 in)
Weight 5.05 kg (11.0 lb)
Operating Humidity 5% to 95%
Storage Humidity 5% to 95%
Operating Temperature 0C to +45C
Storage Temperature -40C to +75C
Upper Threshold Temperature 60C
Danger Threshold Temperature 65C

OmniSwitch 6350 Hardware Users Guide October 2016 page 3-13

OmniSwitch 6350-48 OmniSwitch 6350 Chassis and Hardware Components

PRIPWR

OK1

Console

USB

1 2 3 4 5 6 7 8 9 10 1112 1314 1516 1718 1920 2122 2324 2526 2728 2930 3132 3334 3536 3738 3940 4142 4344 4546 4748 4950 5152

OS6350-48

G

A D EB C F

OmniSwitch 6350-48

Chassis Features

System status LEDs Internal AC Power Supply
(48) 10/100/1000Base-T Ports Console port (RJ-45)
(4) Non-combo SFP Ports USB port (USB 2.0)

Front Panel

OmniSwitch 6350-48 Front Panel

Item Description

A
B
C
D
E
F
G

(48) 10/100/1000 BaseT Ports
Ethernet Port Status LEDs
Console Port
System Status LEDs
Four (4) Fixed SFP Ports
SFP Port Status LEDs
USB Port

Refer to “OmniSwitch 6350 LED Status” on page 3- 21 for LED status information.

page 3-14 OmniSwitch 6350 Hardware Users Guide October 2016

OmniSwitch 6350 Chassis and Hardware Components OmniSwitch 6350-48

A B

OmniSwitch 6350-48 Rear Panel

Note. The figure shows a pre-production version of the chassis without product, safety, and compliance
information labels. All production versions of the chassis have these labels.

OmniSwitch 6350-48 Rear Panel

Item Description

A

B

Grounding Block

Type LCD8-10A-L grounding lug

Power Supply Connector

Internal AC power supply.

OmniSwitch 6350-48 Internal AC Power Supply

P/S Component Description

Model O mniSw itch 6350-48
Nominal Input Voltage 90-220 VAC
Maximum Output Power 60 W
Output Voltage 12V DC

OmniSwitch 6350 Hardware Users Guide October 2016 page 3-15

OmniSwitch 6350-48 OmniSwitch 6350 Chassis and Hardware Components

OmniSwitch 6350-48 Specifications

10/100/1000BaseT ports 48
SFP ports 4
Chassis Width 44.0 cm (17.32 in)
Chassis Height 4.4 cm (1.73 in) (1 RU)
Chassis Depth 23.87 cm (9.4 in)
Weight 5.44 kg (12.0 lb)
Operating Humidity 5% to 95%
Storage Humidity 5% to 95%
Operating Temperature 0C to +45C
Storage Temperature -40C to +75C
Upper Threshold Temperature 62C
Danger Threshold Temperature 67C

page 3-16 OmniSwitch 6350 Hardware Users Guide October 2016

OmniSwitch 6350 Chassis and Hardware Components OmniSwitch 6350-P48

PRIPWR

OK1

Console

USB

1 2 3 4 5 6 7 8 9 10 1112 1314 1516 1718 1920 2122 2324 2526 2728 2930 3132 3334 3536 3738 3940 4142 4344 4546 4748 4950 5152

G

A D EB C F

OmniSwitch 6350-P48

Chassis Features

System status LEDs Internal AC Power Supply
(48) 10/100/1000Base-T PoE Ports Console port (RJ-45)
(4) Non-combo SFP Ports USB port (USB 2.0)

Front Panel

OmniSwitch 6350-P48 Front Panel

Item Description

A
B
C
D
E
F
G

(48) 10/100/1000 BaseT Power over Ethernet (PoE) Ports
Ethernet Port Status LEDs
Console Port
System Status LEDs
Four (4) Fixed SFP Ports
SFP Port Status LEDs
USB Port

Refer to “OmniSwitch 6350 LED Status” on page 3- 21 for LED status information.

OmniSwitch 6350 Hardware Users Guide October 2016 page 3-17

OmniSwitch 6350-P48 OmniSwitch 6350 Chassis and Hardware Components

A B

OmniSwitch 6350-P48 Rear Panel

Note. The figure shows a pre-production version of the chassis without product, safety, and compliance
information labels. All production versions of the chassis have these labels.

OmniSwitch 6350-P48 Rear Panel

Item Description

A

Grounding Block

Type LCD8-10A-L grounding lug

B

Power Supply Connector

Internal AC power supply.

page 3-18 OmniSwitch 6350 Hardware Users Guide October 2016

OmniSwitch 6350 Chassis and Hardware Components OmniSwitch 6350-P48

OmniSwitch 6350-P48 Internal AC Power Supply

P/S Component Description

Model O mniSwitch 6350-P48
Nominal Input Voltage 90-220 VAC
Maximum Output Power 900 W
PoE Power Budget 780 W
Output Voltage 12V DC/53V DC

OmniSwitch 6350 Hardware Users Guide October 2016 page 3-19

OmniSwitch 6350-P48 OmniSwitch 6350 Chassis and Hardware Components

OmniSwitch 6350-P48 Specifications

Standard(s) Supported 802.3at
10/100/1000BaseT Power over

48

Ethernet (PoE) Ports
SFP ports 4
Chassis Width 44.0 cm (17.32 in)
Total Power Budget 900 W
System Power Budget 120 W
PoE Power Budget 780 W
Chassis Height 4.4 cm (1.73 in) (1 RU)
Chassis Depth 23.87 cm (9.4 in)
Weight 5.05 kg (11.0 lb)
Operating Humidity 5% to 95%
Storage Humidity 5% to 95%
Operating Temperature 0C to +45C
Storage Temperature -40C to +75C
Upper Threshold Temperature 60C
Danger Threshold Temperature 65C

page 3-20 OmniSwitch 6350 Hardware Users Guide October 2016

OmniSwitch 6350 Chassis and Hardware Components OmniSwitch 6350 LED Status

OmniSwitch 6350 LED Status

LED State Description

OK1 Solid Green

Blinking Green
Solid Amber

PRI Solid Green

Solid Amber
Off

PWR Solid Green

Solid Amber
Off

10/100/1000 Ports Solid Green

Blinking Green

Solid Amber
Blinking Amber
Off

SFP Ports Solid Green

The switch has passed hardware diagnostic tests and the
system software is operational

Normal diagnostics and/or Remote Config Load in progress
System fan failure or temperature threshold exceeded

Switch is idle.

P/S Normal Operation
P/S Present and Bad
P/S Not Present.

Valid Link
Transmitting or receiving packets in a link up state for non-

PoE
Valid PoE Link
Transmitting or receiving packets in a link up state for PoE
No Link Detected

Valid Link
Blinking Green
Off

Transmitting or receiving packets in a link up state

No Link Detected

OmniSwitch 6350 Hardware Users Guide October 2016 page 3-21

AC Power Cords OmniSwitch 6350 Chassis and Hardware Components

Power Cord Types User Si de Connectors

North America NEMA 5-15-P
United Kingdom / Ireland BS 1363 UK
Europe CEE 7/7
Japan JIS 8303
Australia AS 3112
India BS 546
Italy CIE 23-16
Switzerland / Liechtenstein SEV 1011
Denmark / Greenland SRAF 1962 / DB 16/87
Argentina A-10

IEC-60320-C13

AC Power Cords

Since the power cord is the switch’s only disconnect device, it should be plugged into an easily accessible
outlet. In the event that your power cord is lost or damaged, refer to the specifications below.

Specifications

The power cord included with this product contains three (3) in sulated #18AWG stranded copper wires
and is rated between 85-265 VAC (region dependent), 10 amps with a nominal length of 2 meters. The
female end terminates in an IEC-60320-C13 attachment plug and the male end termination varies
dependent upon region, as listed below.

European cords must be Harmonized (HAR) type. Refer to the information below for power plug types
by region:

Power Cord Specifications

page 3-22 OmniSwitch 6350 Hardware Users Guide October 2016

OmniSwitch 6350 Chassis and Hardware Components Console Port

Console Port

The console port, located on the chassis front panel, provides a console connection to the switch and is
required when logging into the switc h for the first time. By default, this RJ-45 connector provides a DTE
console connection.

Serial Connection Default Settings

The factory default settings for the serial connection are as follows:

baud rate 9600
parity none
data bits (word size) 8
stop bits 1
flow control none

OmniSwitch 6350 Hardware Users Guide October 2016 page 3-23

Port Pinouts OmniSwitch 6350 Chassis and Hardware Components

Port Pinouts

RJ-45 Console Port – Connector Pinout

Pin Number Signals as DTE Console Port

1NC
2NC
3RXD
4Ground
5Ground
6TXD
7NC
8NC

10/100 Ethernet Port – RJ-45 Pinout (non-PoE)

Pin Number Description

1RX+
2RX­3TX+
4 not used
5 not used
6TX­7 not used
8 not used

Gigabit Ethernet Port – RJ-45 Pinout

Pin Number Description

1BI_DB+
2BI_DB­3BI_DA+
4BI_DD+
5BI_DD­6BI_DA­7BI_DC+
8BI_DC-

page 3-24 OmniSwitch 6350 Hardware Users Guide October 2016

OmniSwitch 6350 Chassis and Hardware Components Overtemp Condition

10/100/1000 Mbps Power over Ethernet Port – RJ-45 Pinout

Pin Number Description

1 RX+ (-VDC)
2 RX- (-VDC)
3TX+ (+VDC)
4
5
6 TX- (+VDC)
7
8

Overtemp Condition

The OmniSwitch is designed to operate within a specified operating temperature as noted under the
specifications section. However, in the event that the normal operating temperature of the switch is
exceeded, the following will occur:

• Upon crossing the configured Upper Threshold, a trap will be sent. (See the OmniSwitch 6250/6350/

6450 Network Configuration Guide for information on configuring switch thresholds.)

If the temperature continues to rise and reaches the Danger Threshold, the following will occur:

• OK1 LED will display solid Amber.

• The switch will automatically shutdown

• Once the temperature drops to an acceptable operating level, the switch will automatically restart.

Check the following if an overtemp condition exists:

• Verify that the switch is installed properly in an environment that adheres to the installation

instructions in the following chapters.

• Verify proper airflow to the chassis.

• Time of the failure

Use the snmp station command and refer to the SNMP Configuration chapter for information on
configuring an SNMP station.

OmniSwitch 6350 Hardware Users Guide October 2016 page 3-25

Overtemp Condition OmniSwitch 6350 Chassis and Hardware Components

page 3-26 OmniSwitch 6350 Hardware Users Guide October 2016

7 Managing

OmniSwitch 6350 Stacks

In addition to their working as individual stand-alone switches OmniSwitch 6350 switches can also be
linked together to work as a single virtual chassis known as a stack. With stacks, users can easily expand
their switching capacity simply by adding additional switches to the stack. In addition, stacks provide
enhanced resiliency and redundancy features. For more information, refer to page 7-2.

In This Chapter

This chapter provides information on OmniSwitch 6350 switches configured to operate as a single virtual
chassis. Topics described in the chapter include:

• OmniSwitch 6350 stack overview on page 7-2.

• Roles within the stack on page 7-3.

• Stack cabling on page 7-16.

• Slot numbering on page 7-19.

• Hot-Swapping modules in a stack on page 7-24.

• Reloading switches on page 7-26.

• Changing the secondary module to primary on page 7-34.

• Synchronizing switches in a stack on page 7-36.

• Stack Split Detection (SSP) on page 7-37.

• Monitoring the stack on page 7-40.

Note. You can also manage and monitor OmniSwitch 6350 stacks through WebView, Alcatel-Lucent

Enterprise’s embedded web-based device management application. WebView is an interactive and easy­to-use GUI that can be launched from OmniVista or a web browser. Please refer to WebView’s online
documentation for more information.

OmniSwitch 6450 Hardware Users Guide October 2016 page 7-1

OmniSwitch 6350 Stack Overview Managing OmniSwitch 6350 Stacks

OmniSwitch 6350 Stacking Specifications

Models Supporting Stacking OS6350-24, OS6350-P24, OS6350-48, OS6350-P4

(Stacking OS6350-10/P10 switches is not currently

supported.)
Maximum Switches in a Stack 4
Required Stacking Module N/A (Uses built-in stacking ports)
Required Transceiver Type Direct Attach Copper
Cable Lengths - Copper 60cm, 1m, 3m, 7m
Cable Lengths - Fiber (SFP+) Up to 10KM (Remote Stacking)
Default Chassis Mode Standalone

Note. Stackable OS6350 models (see table above) have 4x1G uplink ports, two of which are capable of
5Gbps stacking. For OS6350-24/P24 switches, ports 27 and 28 can be used for stacking and, for
OS6350-48/P48 switches, ports 49 and 50 are both uplink (1Gbps) and stacking capable (5Gbps) ports.

OmniSwitch 6350 Stack Overview

Users can configure OmniSwitch 6350 switches into a single virtual chassis know n as a stack. With stac ks,
switching capacity can be easily expanded simply by ad di ng ad ditional switches to the stack. For example,
a user can start with a stack composed of two switches and add additional switches to that stack as network
demands increase over time.

Note. Switches should be added one at a time in a stack.

Stacks also provide enhanced resiliency and redundancy features. If a switch in a stack goes down or is
taken offline, the other elements in the stack will continue to operate without disruption. In addition, when
a switch auto-synchronizes at boot-up, or if the user manually synchronize the switches (see

“Synchronizing Switches in a Stack” on page 7-36 for more information), operating software and

configuration parameters are backed up on all switches in the stack. As a result, the original operating
software and configuration parameters can be easily recovered if corrupted or otherwise lost.

Note. In the user guides provided with your OmniSwitch 6350 switch, the terms stack and virtual chassis
are interchangeable referring to OmniSwitch 6350 switches in a stacked configuration. The terms module,

switch, slot, and element are used to refer to individual switches within a stacked configuration. The terms
Chassis Management Module (CMM) and ma nagement module refer to those switches operating in a

stack either in the primary or secondary management roles. OmniSwitch 6350 switches operating in an
idle role are essentially acting as network interface modules and therefore may be referred to as Network
Interfaces (NIs).

page 7-2 OmniSwitch 6450 Hardware Users Guide October 2016

Managing OmniSwitch 6350 Stacks OmniSwitch 6350 Stacking/Standalone Mode

OmniSwitch 6350 Stacking/Standalone Mode

The mode of the OS6350 can be manually configured using the stack set slot mode as shown below:

-> stack set slot 1 mode stackable

The switch must be rebooted for the new mode to take affect.

Roles Within the Stack

In order to operate as a virtual chassis, switches within an OmniSwitch 6350 stack are assigned specific
roles. These roles include primary and secondary management roles, idle status, and pass-through. For
detailed descriptions of each of these roles, including their practical functions within the virtual chassis,
refer to the sections below.

Primary and Secondary Management Modules

When OmniSwitch 6350 switches operate in a stack, one switch in the stack always assumes the primary
management role. This primary element is responsible for functions, such as software and configuration

management, web-based management (i.e., WebView), SNMP management, switch diagnostics, and
software rollback.

One additional switch in the stack operates in a secondary management role. This switch serves as a
backup, and is always ready to assume the primary management role in the stack if the switch with the
primary role fails or is taken offline for any reason.

Since the secondary module quickly and automatically assumes management responsibilities, switches
operating in idle mode elsewhere in the stack continue to pass traffic without disruption. This redundancy
provides effective safeguards for mission-critical network traffic and is one of the stack’s most important
failover features. Diagrams showing the management module failover sequence for stacks of three or more
switches and stacks of two switches are provided on pages 7-4 and 7-5, respectively.

OmniSwitch 6450 Hardware Users Guide October 2016 page 7-3

Roles Within the Stack Managing OmniSwitch 6350 Stacks

Secondary

Primary

Idle
Idle

Secondary

Offline

Idle
Idle

Primary

Offline

Secondary
Idle

!

Primary

Idle

Secondary
Idle

A stack of four OmniSwitch 6350 switches is
operating normally. The stack consi sts of a pri­mary module, secondary module, and two ele­ments operating in idle status. (The software
on all elements in the stack is synchronized.)

The primary management module in the stack
fails or is taken offline (e.g., powered off or
rebooted by the user).

The switch operating as the secondary manage­ment module immediately takes over the primary
role. Meanwhile, the adjacent switch—previously
operating in idle status—now assumes the second­ary management role.

If the switch that failed or was taken off line c omes
back online, it will assume an idle role in the
stack. In other words, it will act essentially as an
NI module in the virtual chassis, passing traffic via
its Ethernet.

1

2

3

4

Note. For management module redundancy to work effectively, the software on all switches operating in
the stack must be synchronized at all times. Refer to “Synchronizing Swit ches in a Stac k” on page 7-36 for
more information.

page 7-4 OmniSwitch 6450 Hardware Users Guide October 2016

Redundant Management Module Failover (Three or More Switches)

Managing OmniSwitch 6350 Stacks Roles Within the Stack

Primary

Secondary

Secondary

Offline

Primary

Offline

Secondary

Primary

!

A stack of two OmniSwitch 6350 switches is
operating normally. The stack consi sts of a pri­mary module and a secondary module. (The
software on both elements in the stack is syn­chronized.)

The primary management module fails or is
taken offline (e.g., powered off or rebooted by
the user).

The switch operating as the secondary manage­ment module immediately takes over the primary
role. It is at this point essentially operating as a
stand-alone switch.

If the switch that previously failed or was taken
offline comes back online, it will assume the sec­ondary role in the stack.

1

2

3

4

Redundant Management Module Failover (Two Switches)

OmniSwitch 6450 Hardware Users Guide October 2016 page 7-5

Roles Within the Stack Managing OmniSwitch 6350 Stacks

A stack of four OmniSwitch 6350 switches is
booted. All switches are powered on within 15 sec­onds of each other. In addition, there is no precon­figured slot information on any of the switches.

00:d0:95:b2:3c:8e

00:d0:95:b2:2a:ab

00:d0:95:b2:1c:ff

00:d0:95:b2:5b:8d

When the stack is booted, system software detects
the lowest MAC address. In this stacked configura­tion, the lowest MAC address is 00:d0:95:b2:1c:ff.

2

1

00:d0:95:b2:3c:8e

00:d0:95:b2:2a:ab

Primary Module

00:d0:95:b2:5b:8d

The system software immediately assigns the cor­responding switch the primary managem ent role.
When the switch is assigned as primary, it is also
dynamically assigned the lowest slot number in
the stack—i.e., slot 1. This slot number informa­tion is saved to the boot.slot.cfg file, located in
the switch’s /flash file directory.

3

Primary Management Module Selection

For a stack of OmniSwitch 6350 switches to operate as a virtual chassis, there must be a mechanism for
dynamically selecting the switch within the stack that will assume the primary management role.
OmniSwitch 6350 switches use three different methods for selecting the primary switch.
These methods are:

• Chassis MAC address

• Saved slot number

• Chassis uptime

Note. Information on secondary management module selection is provided on page 7-9. Information on

dynamic assignment of idle module roles is provided on page 7-11.

Using the Chassis MAC Address

By default, the primary management role will be giv en to the swi tch with th e lowest c has sis MAC a ddress.
However, for this to occur, all switches in the stack must be booted within 15 seconds of each other. In
addition, switches in the stack must have no preconfigured slot information. Because of these two
conditions, the MAC address method for selecting the primary mod ule usua lly occ urs with new “o ut of the
box” switches, or switches from which any preconfigured slot information has been cleared.

For more information on using the lowest MAC address to determine the primary switch in a stack, refer
to the diagram below:

Note. During the boot process, all other switches in the stack are also dynamically assigned unique slot
numbers. As with the primary switch, these slot numbers are saved to the boot.slot.cfg file, located in the
/flash file directory of each switch. For more information on dynamic slot number assignment, refer to

“Slot Numbering” on page 7-19.

page 7-6 OmniSwitch 6450 Hardware Users Guide October 2016

Primary Management Module Selection Using the Lowest Chassis MAC Address

Managing OmniSwitch 6350 Stacks Roles Within the Stack

Slot 6

Slot 5

Slot 4

Primary: Slot 3

Assumes Slot 6

Assumes Slot 5

Assumes Slot 4

Assumes Slot 3

Saved Slot 6

Four OmniSwitch 6350 switches are stacked; all
switches are connected via stacking cables. The user
configures each switch to have a unique saved slot
number. When each saved slot number is configured,
the information is automatically
written to the boot.slot.cfg file located in the /flash
directory of each switch.

The user reloads all the elements in the stack
either by issuing the reload all command or by
physically powering off and then powering on all
switches.

Instead of assigning the primary management
module based on the lowest MAC address, the
system software reads the slot information from
each switch’s boot.slot.cfg file during the boot
process. The switches in the stack come up
using their assigned slot numbers.

The switch with the lowest assigned slot number
automatically assumes the primary management role.
In this case, the switch assigned slot 3 has the lowest
slot number in the stack and becomes the primary
management module.

1

2

3

4

Saved Slot 5
Saved Slot 4

Saved Slot 3

Reload

Using Saved Slot Information

The saved slot number is the slot number the switch will assume following a reboot. This information is
stored in a switch’s boot.slot.cfg file; the switch reads its slot number assi gn ment from this file at bootu p
and assumes the specified slot number within the stack.

If switches in a stacked configuration have no preconfigured slot assignments, the slot number for each
switch is dynamically assigned by the system software. Slot numbers can also be manually assigned by the
user. For more information on manually assigning slot numbers, refer to “Manual Slot Number

Assignment” on page 7-22.

When a stack with preconfigured slot information is booted, it is not the lowest MAC address that
determines the primary management module. Instead, the slot information stored in each switch’s
boot.slot.cfg is read by the system software and used in determining the primary. The switch with the
lowest saved slot number becomes the primary management module.

Note. Although, for ease-of-management purposes, it is recommended that slot numbers are assigned
beginning with slot number 1, it is not a requirement. In other words, a stack of four switches can have
slot assignments 3, 4, 5, and 6. However, it is important that each element in a stack is assigned a unique
slot number. Do not assign duplicate slot numbers to elements in a stack. Otherwise, one or more switches
will be forced into pass-through mode. For more information on pass-through mode, refer to page 7-12.

For more information on using saved slot information to determine the primary switch in a stack, refer to
the diagram below:

OmniSwitch 6450 Hardware Users Guide October 2016 page 7-7

Primary Management Module Selection Using Saved Slot Information

Roles Within the Stack Managing OmniSwitch 6350 Stacks

Powered On

Powered On

Powered On

Off

Four OmniSwitch 6350 switches are stacked and connected
via stacking cables. All switches are currently powered off.
The user powers on a single switch in the stack. In this case,
the bottom-most switch is powered on.

The user now powers on the remaining switches in the stack
in short succession.

In this example, when the remaining switches come online,
each has a lower saved slot value than the switch powered on
at step 1. However, the switch powered on at step 1—with its
slot value of 8—retains its primary management role. The
joining switches are essentially ineligible for primary status
because they are considered “late arrivals.”

For the primary
switch to forfeit its role to the switch with the lowest assigned slot
number (in this case, slot number 1), the stack must be rebooted
by the user either by issuing the reload all command or by pow­ering off and powering on all switches in close succession.

1

2

3

Off
Off

Powered On

Off

Off
Off

Primary
(Saved Slot 8)

Primary

(Saved Slot 8)

Saved Slot 3

Saved Slot 1

Saved Slot 2

Primary
(Saved Slot 8)

The user allows a minimum of 15 seconds to pass.
Because no other switches have joined the stack, the
switch that was powered on considers itself a stand­alone. The switch assumes a primary role by default—
even if there is a high saved slot number in its
boot.slot.cfg file (e.g., 8).

4

Using Switch Uptime

A user can override both the MAC address and saved slot methods for determining a stack’s primary
management module. This is done by controlling the uptime of switches in the stack. If all elements of a
stack are powered off, the user can force a particular switch to become primary by poweri ng on that switch
and waiting a minimum of 15 seconds before powering on any other switches. This can be useful if the
user wants a switch placed in a specific location, e.g., the top-most switch in a stack, to become the
primary.

As with the lowest MAC address method, the primary management module is dynamically assigned slot
number 1 when the stack is booted.

For more information on using saved slot information to determine the primary switch in a stack, refer to
the diagram below:

Primary Management Module Selection Using Switch Uptime

page 7-8 OmniSwitch 6450 Hardware Users Guide October 2016

Managing OmniSwitch 6350 Stacks Roles Within the Stack

Four OmniSwitch 6350 switches are stacked
and connected via stacking cables, as shown.
All switches are currently powered off. None
of the switches have preassigned slot num­bers—i.e., there are no boot.slot.cfg files pres­ent. The user powers on all switches in the
stack in close succession and the stack begins
the boot process.

By default, the switch connected to
the primary’s stacking port A is
automatically assigned the second­ary management role. The second­ary switch is dynamically assigned
slot number 2.

1

2

3

When the elements in the stack come
online, the switch with the lowest
MAC address is given the primary
management role and is dynamically
assigned slot number 1.

A B

A B

00:d0:95:b2:3c:8e
00:d0:95:b2:2a:ab

00:d0:95:b2:1c:ff

00:d0:95:b2:5b:8d

Idle

Idle
Primary

Secondary - Slot 2

(Primary - Slot 1)

Secondary Management Module Selection

In order to provide effective management module redundancy, all OmniSwitch 6350 stacked
configurations dynamically assign a backup, or secondary, management module during the boot process.
OmniSwitch 6350 stacks use two different methods for selecting the secondary switch.
These methods are:

• Stacking connection to the primary switch

• Saved slot number

Using the Stacking Connection to the Primary Switch

By default, the switch that is connected to the primary switch’s stacking port A is automatically assigned
the secondary management role. This applies to stacks on which there is no preassigned slot information—
i.e., there is no boot.slot.cfg file present in any switch.

For more information on using the stacking connection to the primary switch to determine the secondary
management module, refer to the diagram below:

Secondary Management Module Selection Using the Stacking Connection to the Primary Switch

Note. For information on dynamic slot numbering for idle elements within th e stack, re fer to “Idle Module

Role” on page 7-11 and “Slot Numbering” on page 7-19.

OmniSwitch 6450 Hardware Users Guide October 2016 page 7-9

Roles Within the Stack Managing OmniSwitch 6350 Stacks

Primary - Slot 1

Slot 3
Slot 4

Secondary - Slot 2

Assumes Slot 1

Assumes Slot 3
Assumes Slot 4

Assumes Slot 2

Saved Slot 1

Four OmniSwitch 6350 switches are stacked; all
switches are connected via stacking cables. The user
configures each switch to have a unique saved slot num­ber, as shown. When the saved slot nu mber is config­ured, the information is automatically written to the
boot.slot.cfg file located in the /flash directory of each
switch.

The user reloads all the elements in the stack eith er by
issuing the reload all command or by physically pow­ering off and then powering on all switches.

The system software reads the slot information from
each switch’s boot.slot.cfg file during the boot pro­cess. The switches in the stack come up using their
assigned slot numbers.

The switch with the lowest assigned slot number auto­matically assumes the primary management role. The
switch with the second lowest assigned slot number
becomes the secondary management rol e, rega rdless of
whether it is attached to stacking port A of the primary
switch. In this case, the switch assigned
slot 2 has the second-lowest slot number in the stack
and becomes the secondary management module.

1

2

3

4

Saved Slot 3

Saved Slot 4

Saved Slot 2

Reload

Using Saved Slot Information

If a stack with preassigned slot information for each switch is booted, the switch with the second lowest
slot value is assigned the secondary management role. For example, if a stack of four switches is booted
and the preassigned slot values for each switch are 1, 2, 3, and 4, the switch with the slot value of 2 is
assigned the secondary role. Meanwhile, the switch with the slot value of 1 is assigned the primary
management role (see page 7-7).

For more information on using saved slot information to determine the secondary management module in
a stack, refer to the diagram below:

page 7-10 OmniSwitch 6450 Hardware Users Guide October 2016

Secondary Management Module Selection Using Saved Slot Information

Note. Each element in a stack should always be assigned a unique slot number. Do not assign

duplicate slot numbers to elements in a stack. Otherwise, one or more switches will be forced into
pass-through mode. For more information on pass-through mode, refer to page 7-12.

Managing OmniSwitch 6350 Stacks Roles Within the Stack

Four OmniSwitch 6350 switches are stacked; all switches
are connected via stacking cables. The stack is booted.

Primary

Secondary

The primary and secondary management modu le s are
dynamically assigned using any of the methods outlined on
pages

7-6 through 7-10.

2

1

Idle
Idle

Primary

Secondary

The system software automatically assigns the remain­ing elements in the stack the idle module role. These
modules act as Network Interface (NI) modules.

In the event of a primary-to-secondary failover,
the idle module with the next-lowest slot number
in the stack will assume the secondary—or
backup—management role.

3

Idle Module Role

Switches that are not assigned either the primary or secondary role in a stack are, by default, assigned the
role of idle modules. These idle modules operate similarly to Network Interface (NI) modules in a chassis­based switch. It is the job of idle modules to send and receive traffic.

In the event of a management module failure within the stack, the idle module with the next lowest slot
number in the stack will automatically assume the secondary management role. In other words, if the
primary module in a stack goes down for any reason and the secondary takes over the primary
management role, the switch must now assign a new secondary module. The idle element with the next
lowest slot number assumes this new responsibility until the situation is corrected and all elements in the
stack are reloaded.

Note. Primary and secondary management modules also send and receive traffic on their Ethernet. The
primary management module is like an NI module with the added task of overall stack management; the
secondary management module is like an NI with the added responsibility of backing up the primary
module in the event of a primary module failure. In other words, all modules in the virtual chassis can
send and receive user data, regardless of their roles.

For more information on dynamic assignment of idle modules in a stack, refer to the diagram below:

Secondary Management Module Selection Using Saved Slot Information

OmniSwitch 6450 Hardware Users Guide October 2016 page 7-11

Roles Within the Stack Managing OmniSwitch 6350 Stacks

Pass-Through Mode

The pass-through mode is a state in which a switch has attempted to join a stack but has been denied
primary, secondary, and idle status. When a switch is in the pass-through mode, its Ethernet ports are
brought down (i.e, they cannot pass traffic). Its stacking cable connections remain fully functional and can
pass traffic through to other switches in the stack. In this way, the pass-through mode provides a
mechanism to prevent the stack ring from being broken. However, note that when a switch comes up in
pass-through mode, it should not be left unresolved. Pass-through mode is essentially an error state that
should be corrected immediately.

Note. When a switch is in pass-through mode, its information will not display in hardware monitoring
commands such as show chassis, show ni, show module, etc.

Conditions that can trigger a swit ch to enter pass-through mode include:

• Duplicate slot numbers have been assigned within the stack

• The user has manually forced the switch into pass-through mode using the stack clear slot command

Note. If a switch is forced into pass-through mode, the rest of the stack will not b e disrupted. Any

elements in the stack not operating in pass-through mode continue to operate normally.

The most common reason for one or more switches to enter pass-through is duplicate slot number
assignments within the stack. So, in order to avoid pass-through mode, it is useful to keep track of the
current saved slot numbers on all elements in the stack. Slot number assignments are stored in the
boot.slot.cfg file in the /flash directory of each switch.

If the stack is booted and the same slot number is discovered on two or more switches, the switch with the
lowest MAC address is allowed to come up and operate normally. Meanwhile, switches with the duplicate
slot number and a higher MAC address come up in pass-through mode. To check the current slot number
stored in each switch’s boot.slot.cfg file, use the show stack topology command. For example:

-> show stack topology
Link A Link A Link B Link B
NI Role State Saved Link A Remote Remote Link B Remote Remote
Slot State NI Port State NI Port

----+-----------+--------+------+-------+-------+-------+-------+-------+------­ 1 PRIMARY RUNNING 1 UP 3 StackA UP 2 StackA
2 SECONDARY RUNNING 2 UP 1 StackB UP 3 StackB
3 IDLE RUNNING 2 UP 1 StackA UP 2 StackB

In this example, note that both slots 2 and 3 have a saved slot value of 2. If this stack is rebooted, a
duplicate slot error will occur and the switch with the lower MAC address will be given the secondary
management role. The slot with the higher MAC address will be forced into the pass-through mode.

page 7-12 OmniSwitch 6450 Hardware Users Guide October 2016

Managing OmniSwitch 6350 Stacks Roles Within the Stack

To avoid a pass-through condition foll ow in g a reboot, make sure that all saved slot values for the stack are
unique. Use the stack set slot command. For example, change the saved slot value for the idle switch in
slot 3 from 2 to 3:

-> stack set slot 3 saved-slot 2

Use the show stack topology command to verify the change:

-> show stack topology
Link A Link A Link B Link B
NI Role State Saved Link A Remote Remote Link B Remote Remote
Slot State NI Port State NI Port

----+-----------+--------+------+-------+-------+-------+-------+-------+------­ 1 PRIMARY RUNNING 1 UP 3 StackA UP 2 StackA
2 SECONDARY RUNNING 2 UP 1 StackB UP 3 StackB
3 IDLE RUNNING 3 UP 1 StackA UP 2 StackB

Recovering from Pass-Through Mode (Duplicate Slot Numbers)

The first step in recovering from pass-through is to determine which modules are currently operating in
pass-through, as well as the reason for the pass-through state. To view this information, use the
show stack topology command. For example:

-> show stack topology
Link A Link A Link B Link B
NI Role State Saved Link A Remote Remote Link B Remote Remote
Slot State NI Port State NI Port

----+-----------+--------+------+-------+-------+-------+-------+-------+------­ 1 PRIMARY RUNNING 1 UP 1001 StackA UP 2 StackA
2 SECONDARY RUNNING 2 UP 1 StackB UP 1001 StackB
1001 PASS-THRU DUP-SLOT 2 UP 1 StackA UP 2 StackB

Switches operating in pass-through mode are given distinct slot numbers. These slot numbers are not
related to their position in the stack. Instead, they are assigned the prefix “100, ” followed by the numerical
order in which they were forced into pass-through (1001–1008).

Note. For pass-through elements 1001 through 1008, the slot indicator LED on the chassis front panel
blinks 1 through 8, respectively. For example, if a module enters pass-through and has the slot number
1004, the LED for the module blinks the number 4. For more information on the slot indicator LED, refer
to “OmniSwitch 6350 LED Status” on page 3-21.

In the example above, the switch with the NI (i.e., slot) number 1001 is operating in pass-through. Note
that the role assignment is PASS-THRU; also, the state displays DUP-SLOT, or duplicate slot number.
This can be further verified by looking down the saved slot column in the table. Note that slot 2, operating
in the secondary management role, has a saved slot value of 2. Slot 1001, operating in pass-through, also
has a saved slot value of 2.

OmniSwitch 6450 Hardware Users Guide October 2016 page 7-13

Roles Within the Stack Managing OmniSwitch 6350 Stacks

To resolve this pass-through condition, simply assign slot 1001 a new saved slot value and reboot the
module. This can be done in either of two ways:

• Use the stack set slot command to assign the new value, then use the reload pass-through command

to reboot the module:

-> stack set slot 1001 saved-slot 3

-> reload pass-through 1001

• Use the stack set slot command to assign the new slot value and, using the optional reload syntax in

the command line, reboot the module:

-> stack set slot 1001 saved-slot 3 reload

When the module comes up, it assumes the new, unique slot position—in this case, slot 3—and, because it
now has the highest slot number in the stack, it assumes an idle role (leaving the primary and secondary
roles to slots 1 and 2, respectively). There are now no duplicate numbers in the stack and all elements are
operating normally:

-> show stack topology
Link A Link A Link B Link B
NI Role State Saved Link A Remote Remote Link B Remote Remote
Slot State NI Port State NI Port

----+-----------+--------+------+-------+-------+-------+-------+-------+------­ 1 PRIMARY RUNNING 1 UP 3 StackA UP 2 StackA
2 SECONDARY RUNNING 2 UP 1 StackB UP 3 StackB
3 IDLE RUNNING 3 UP 1 StackA UP 2 StackB

page 7-14 OmniSwitch 6450 Hardware Users Guide October 2016

Managing OmniSwitch 6350 Stacks Roles Within the Stack

In some pass-through conditions (for example, larger stacks where multiple switches are in pass-through
mode), it might be desirable to correct any duplicate saved slot assignments and then reboot the entire
stack. The recovery from pass-through can be accomplished with fewer steps than reassigning slot
numbers and rebooting modules on a slot-by-slot basis. However, be sure that there i s no mission-critical
traffic being passed on the non-pass-though modules; traffic will be interrupted on these modules during
the reboot.

The following example shows a large stack with multiple elements operating in pass-through mode:

-> show stack topology
Link A Link A Link B Link B
NI Role State Saved Link A Remote Remote Link B Remote Remote
Slot State NI Port State NI Port

----+-----------+--------+------+-------+-------+-------+-------+-------+------­ 4 IDLE RUNNING 4 UP 5 StackB UP 3 StackA
5 IDLE RUNNING 5 UP 1001 StackB UP 4 StackA
1001 PASS-THRU DUP-SLOT 2 UP 2 StackB UP 5 StackA
2 SECONDARY RUNNING 2 UP 1003 StackB UP 1001 StackA
1003 PASS-THRU DUP-SLOT 2 UP 1002 StackB UP 2 StackA
1002 PASS-THRU DUP-SLOT 2 UP 1 StackB UP 1003 StackA
1 PRIMARY RUNNING 1 UP 3 StackB UP 1002 StackA
3 IDLE RUNNING 3 UP 4 StackB UP 1 StackA

This disordered stack topology, with its three modules operating in pass-through mode, can be corrected
by entering the following commands:

-> stack set slot 4 saved-slot 1

-> stack set slot 5 saved-slot 2

-> stack set slot 1001 saved-slot 3

-> stack set slot 2 saved-slot 4

-> stack set slot 1003 saved-slot 5

-> stack set slot 1002 saved-slot 6

-> stack set slot 1 saved-slot 7

-> stack set slot 3 saved-slot 8

-> reload all

When all elements in the stack come up following the reboot, there are no longer any duplicate slot
numbers in the stack. In addition, the stack topology is more orderly and, as a result, easier to manage:

-> show stack topology
Link A Link A Link B Link B
NI Role State Saved Link A Remote Remote Link B Remote Remote
Slot State NI Port State NI Port

----+-----------+--------+------+-------+-------+-------+-------+-------+------­ 1 PRIMARY RUNNING 1 UP 2 StackB UP 8 StackA
2 SECONDARY RUNNING 2 UP 3 StackB UP 1 StackA
3 IDLE RUNNING 3 UP 4 StackB UP 2 StackA
4 IDLE RUNNING 4 UP 5 StackB UP 3 StackA
5 IDLE RUNNING 5 UP 6 StackB UP 4 StackA
6 IDLE RUNNING 6 UP 7 StackB UP 5 StackA
7 IDLE RUNNING 7 UP 8 StackB UP 6 StackA
8 IDLE RUNNING 8 UP 1 StackB UP 7 StackA

OmniSwitch 6450 Hardware Users Guide October 2016 page 7-15

Stack Cabling Managing OmniSwitch 6350 Stacks

A stack of four switches in a crossed (stack­ing port A to stacking port B) configuration.
Note that a redundant stacking cable con­nection exists between the top and bottom
switches. This connection is required for
effective redundancy across the stack.

A B

Stack Cabling

Switches in a stack are connected to each other by stacking cables. These stacking cables provide high­speed, dual-redundant links between switches in a stack.

Stacking cables for OmniSwitch 6350 switches must be connected in an A-B pattern. In other words, the
cable connected to stacking port A of one switch must be connected to stacking port B of the adjacent
switch. In addition, for a stack to have effective redundancy, a redundant stacking cable must be installed
between the upper-most and bottom-most switch at all times. This provides effective failover in the event
of a stacking link or module failure within the stack.

The diagram below shows the required stacking cable pattern. For detailed information on assembling a
stack and connecting the cables, refer to Chapter 3, “OmniSwitch 6350 Chassis and Hardware

Components.”

Note. When planning the stack cabling configuration, keep in mind that the switch connected to stacking
port A of the primary switch will be assigned the secondary management role by default.

Example of Stacking Cable Pattern (Chassis Rear Panels Shown)

page 7-16 OmniSwitch 6450 Hardware Users Guide October 2016

Managing OmniSwitch 6350 Stacks Stack Cabling

Data enters slot 1 via an Ethernet port. The data
is passed to slot 2 over the stacking cable connec­tion, then exits slot 2 via one of its Ethernet ports.

1

2

The stacking connection between slots 1 and 2
goes down unexpectedly. Data can no longer
travel directly between slot 1 and 2.

However, because there is a redundant con­nection (the cable between slot 1 and slot 4),
data is immediately passed to slot 4, then
quickly traverses slot 3 and exits slot 2 to its
destination.

Slot 1
Slot 2
Slot 3
Slot 4

Chassis FrontStacking Cables

Slot 1
Slot 2
Slot 3
Slot 4

Redundant Stacking Cable Connection

OmniSwitch 6350 switches allow redundant stacking cable connections between the top-most and bottom­most switches in a stack.

Note. For a stacked configuration to have effective redundancy, a redundant stacking cable must be
installed between the upper-most and bottom-most switch in the chassis at all times.

The figure below shows how the redundant connection between the top and bottom switches in the stack
ensures that data will continue to flow throughout the stack, even in the event of a connection failure at
one of the stacking cables.

Stacking Cable Redundancy: Recovery Following a Stacking Link Failure

OmniSwitch 6450 Hardware Users Guide October 2016 page 7-17

Stack Cabling Managing OmniSwitch 6350 Stacks

Slot 1
Slot 2
Slot 3
Slot 4

Chassis FrontStacking Cables

Data enters slot 1 through an Ethernet port. The
data traverses slot 2 via the stacking cables and
exits slot 3 through one of its Ethernet ports.

1

2

The slot 2 switch goes down unexpectedly.
Data can no longer move through slot 2.

However, because there is a redundant con­nection (the cable between slot 1 and slot 4),
data immediately traverses slot 4 and then
exits slot 3 to its destination.

Slot 1
Slot 2
Slot 3
Slot 4

Redundant stacking cables provide a form of dual redundancy. As shown in the figure above, the
redundant cable allows traffic to flow in the event of a stacking link failure. The redundant cable also
provides failover if a switch goes down within the stack. Traffic continues to flow between the modules
that remain operational, as shown in the diagram below:

Stacking Cable Redundancy: Recovery Following a Switch Failure within the Stack

Checking Redundant Stacking Cable Status

To check whether a redundant stacking cable connection exists between the top-most and bottom-most
switches in the stack, use the show stack status command. For example:

Redundant cable status : present
Tokens used : 1
Tokens available : 31

In this example, a redundant stacking cable connection is present between the top-most and bottom-most
switches in the stack.

page 7-18 OmniSwitch 6450 Hardware Users Guide October 2016

Managing OmniSwitch 6350 Stacks Slot Numbering

Slot Numbering

For a stack of OmniSwitch 6350 switches to operate as a virtual chassis, each module in the stack must be
assigned a unique slot number. To view the current slot assignments for a st ack, use the show ni or show

module commands. The slot number is also displayed on the front panel of each switch by the LED

located on the left side of the chassis (refer to “OmniSwitch 6350 LED Status” on page 3-21 for more
information).

There are two ways stacking modules are assigned slot numbers:

• Dynamic slot number assignment by the system software

• Manual slot number assignment by the user

OmniSwitch 6450 Hardware Users Guide October 2016 page 7-19

Slot Numbering Managing OmniSwitch 6350 Stacks

Slot 1 - Primary

Slot 2 - Secondary

Slot 3 - Idle

In this example, the fourth switch from the top is
elected the primary management module for the
stack. (It can be assumed that this switch has the low­est MAC address in the stack.) This switch is auto­matically assigned slot number 1.

The switch immediately below is connected to the pri­mary switch’s stacking port A and, as a result, is
assigned the secondary management role and given
slot number 2.

The system software allows the switch immediately
below slot 2 to have the next slot number preference. It
is assigned an idle role and given the slot number 3. The
switch immediately below slot 3 is given the slot number
4, and so on. When the bottom of the stack is reached,
the slot numbering sequence resumes at the top of the
stack, as shown. This helps ensure a more ordered and
manageable stack topology.

Slot 4 - Idle

Dynamic Slot Number Assignment

Dynamic slot number assignment occurs when there are no boot.slot.cfg files present in the switches’
/flash directories. This is the case for ne w, “out of the box,” switches that have not been previously booted.

When a brand new stack (or stack with no boot.slot.cfg files) is booted, the system software automatically
detects the module with the lowest MA C address. This module is assigned the primary management role
(see page 7-3) and, by default, is given the slot number 1. The module connected to th e primary’s stacking
port A is automatically assigned the secondary management role and given the slot number 2.

As the other modules in the stack become operational, they are assigned idle roles and are automatically
assigned unique slot numbers. The slot numbering for idle modules is determined by each module’s
physical location in the stack. Refer to the diagrams below for more information on dynamic slot
numbering.

Note. As the slot numbers are dynamically assigned, boot.slot.cfg files are auto-generated in the /flash
directory of each switch. When modules are subsequently booted, each switch reads its slot number
assignment from this file and comes up accordingly.

Dynamic Slot Numbering Example 1

page 7-20 OmniSwitch 6450 Hardware Users Guide October 2016

Managing OmniSwitch 6350 Stacks Slot Numbering

Slot 4 - Idle

Slot 3 - Idle

In this example, the bottom switch is elected
the primary management module for the
stack. (It can be assumed that this switch has
the lowest MAC address in the stack.) This
switch is automatically assigned slot number

1.

The switch immediately above is connected to
the primary switch’s stacking port A and, as
a result, is assigned the secondary manage­ment role and given slot number 2.

The system software then sequentially assigns
slot numbers up the stack. In other words, the
switch immediately above slot 2 is assigned the
slot number 3; the switch immediately above
slot 3 is assigned the slot number 4, and so on.
This default procedure ensur es the most order ed
and manageable stack topology out of the box.

Slot 2 - Secondary

Slot 1 - Primary

If the switch with the lowest MAC address happens to be the bottom-most module in the stack, slot
numbering will not resume from the top of the stack. Instead, the system software will select the
secondary module using the standard method (i.e., the switch connected to the primary’s stacking port A),
then continue to number the stack from the bottom up. This intuitive slot assignment provides the cleanest
and most manageable stack topology. Refer to the diagram below for more information:

Dynamic Slot Numbering Example 2

OmniSwitch 6450 Hardware Users Guide October 2016 page 7-21

Slot Numbering Managing OmniSwitch 6350 Stacks

Slot 1 - Primary

Slot 2 - Secondary

Slot 3 - Idle

Slot 4 - Idle

Manual Slot Number Assignment

To manually assign slot numbers to one or more modules in a stack, use the stack set slot command. This
command writes slot information to the boot.slot.cfg file located in a switch’s /flash directory. It is this
saved slot information that the switch will assume following a reboot.

Manually assigning slot numbers can be useful in reordering existing slot numbers in order to create a
sequential numbering scheme from the top of the stack to the bottom (or vice-versa). Refer to the
following example:

Stack Numbering Before Manual Assignment

This example, taken from page 7-20, shows a stack in which the primary and secondary switches are
physically positioned in the middle of the stack. Although the stack will operate normally with this
primary and secondary module positioning, it may be preferable for management purposes to have the
primary and secondary switches at either the top or the bottom of the stack. For this example, the primary
and secondary roles will be assigned to the top of the stack. This is acco mplishe d by ente ring the follow ing
commands:

-> stack set slot 3 saved-slot 1

-> stack set slot 4 saved-slot 2

-> stack set slot 2 saved-slot 3

-> stack set slot 1 saved-slot 4

-> reload all

Because slot 3 is the top-most switch in the stack, it is reassigned the slot 1 (i.e., primary) position;
because slot 4 is located immediately below slot 3, it is reassigned the slot 2 (i.e., secondary) position, etc.

Note that the modules were not reloaded one-by-one, even though the stack set slot command provides
optional syntax for doing so. Instead, new slot number information is first saved to each boot.slot.cfg file
across the stack. The reboot is saved for last in order to avoid duplicate slot numbers within the stack,
which would cause unwanted pass-though mode conditions (see page 7-12).

page 7-22 OmniSwitch 6450 Hardware Users Guide October 2016

Managing OmniSwitch 6350 Stacks Slot Numbering

Slot 4 - Idle

Slot 1 - Primary

Slot 2 - Secondary

Slot 3 - Idle

When the stack comes up following the reboot, the manually-configu red slot numbers display as follows:

Stack Numbering Before Manual Assignment

The stack set slot command can also be used to manually correct duplicate saved slot assignments within
the stack topology. Refer to pages 7-12 through 7-14 for detailed information.

Reverting to the Dynamic Slot Numbering Model

To clear the boot.slot.cfg files from the stack’s /flash directories, use the stack clear slot command on all
modules and then reboot the stack. For example:

-> stack clear slot 1

-> stack clear slot 2

-> stack clear slot 3

-> stack clear slot 4

-> reload all

The commands shown above clear the saved slot information from all modules in an eight-module stacked
configuration and then reboot the stack. Becaus e the system software no longer has preassigned slot
information to read during the boot process, the stack uses the dynamic slot number assignment method
described on page 7-20.

OmniSwitch 6450 Hardware Users Guide October 2016 page 7-23

Hot-Swapping Modules In a Stack Managing OmniSwitch 6350 Stacks

Hot-Swapping Modules In a Stack

As with chassis-based switches, NI modules within an OmniSwitch 6350 virtual chassis are hot­swappable. NI modules are essentially those modules operating in the stack in idle mode. These modules
can be removed from, or added to, an existing stack without disrupting other modules in the stack.

Removing Switches from an Existing Stack

When removing switches from an existing stack, observe the following important guidelines:

• Do not attempt to hot-swap modules operating in primary or secondary management roles

• Be sure the stacking cables and stacking cable redundancy are not disrupted

Hot-swapping is intended for switches in idle and, if applicable, pass-through status only. Removing
primary or secondary management modules from a stack will trigger a failover sequence, i.e., one or more
additional modules within the stack must reload in order to reassign the management roles. Whenever
possible, avoid removing a switch that is operating as a primary or secondary management module.

Also, removing a switch from a stacked configuration can disrupt stack cabling at the rear of the stack.
When removing a module, be sure that stacking link integrity, including important stacking cable
redundancy, is maintained between all remaining modules. For more information on stacking cable
connections, refer to page 7-16.

Inserting Switches Into an Existing Stack

When inserting switches into an existing stack, observe the following important guidelines:

• Avoid duplicate saved slot numbers

• Never attempt to operate more than the supported number of switches in a single stack

• Make sure all switches are running the same software version.

To avoid duplicate slot numbers, simply ma ke sure t ha t a ny mod ul es bein g added to an existing stack have
been cleared of preassigned slot information. In other words, verify that there is no boot.slot.cfg file
present in the /flash directory of any switch being added. When the switch is connected to the existing
stack and booted, the system software automatically assigns it a unique slot number. No duplicate slot
errors occur.

Note. If it is preferable to add a switch with an existing boot.slot.cfg file to a stack, be sure that the saved
slot number of the incoming switch is not already assigned to a switch operating in the stack.

page 7-24 OmniSwitch 6450 Hardware Users Guide October 2016

Managing OmniSwitch 6350 Stacks Hot-Swapping Modules In a Stack

Merging Stacks

Merging stacks involves connecting two or more operational stacks and attempting to reboot them as a
single virtual chassis. In most cases, errors will result. To merge stacks without causing errors, select one
stack that is to remain up and running and then add modules from the other stack(s) by fol lowing the steps
below:

1 Make sure all switches are running the same software version.
2 Clear the saved slot information from all incoming modules. This will ensure that they are each

assigned unique slot numbers when they join the stack.

3 After clearing the saved slot information, power off all incoming modules.
4 Connect the stacking cables for all incoming modules to the existing, operational stack as required. Be

sure to provide stacking cable redundancy. For information on stack cabling, refer to page 7-16.

5 Power on all incoming modules.

Note. No more than eight switches can operate in a single stacked configuration at any time.

OmniSwitch 6450 Hardware Users Guide October 2016 page 7-25

Reloading Switches Managing OmniSwitch 6350 Stacks

In this stack of four OmniSwitch 6350 switches, the slot
1 switch is the primary management module. The slot 2
switch is the secondary. Slots 3 and 4 are operating in
idle roles.

The user reloads the stack’s primary management module
by issuing the reload primary comman d. Any data flow on
the primary switch’s Ethernet is interrupted.

The secondary switch automatically takes over the pri ­mary role. The idle switch with the next-lowest slot num­ber—in this case, slot 3—automatically becomes the
secondary management module. The slot 4 switch
remains unaffected. In addition, Ethernet traf fic on slots
2, 3, and 4 remains unaffected.

1

2

3

-> reload primary

Primary - Slot 1

Secondary - Slot 2
Idle - Slot 3

Idle - Slot 4

Booting...

Primary - Slot 2
Secondary - Slot 3

Idle - Slot 4

When the rebooted switch comes back up, it assumes an
idle role within the stack.

4

Idle - Slot 1

Primary - Slot 2
Secondary - Slot 3

Idle - Slot 4

Reloading Switches

Reloading is essentially a soft boot of a switch. Users can reload stacked modules operating in any role—
i.e., primary, secondary, idle, and pass-through. Refer to the sections below for more information.

Reloading the Primary Management Module

If the switch with the primary management role is reloaded, the switch with the secondary role
automatically takes over primary management functions. In other words, the switch with the secondary
role assumes the primary role as soon as the reload is initiated.

Meanwhile, the idle switch with the next lowest slot number automatically assumes the secondary role.
When the reloaded switch (the former primary module) comes back up, it assumes an idle role within the
stack.

To reload the primary management module, use the reload command. The optional syntax primary can
be used in the command line, but is not required. For example:

-> reload primary

Note. A primary management module reload can also be scheduled for a later time or date. For
information on scheduling a primary module reload, as well as additional command details, refer to the
OmniSwitch 6250/6350/6450 CLI Reference Guide.

page 7-26 OmniSwitch 6450 Hardware Users Guide October 2016

Reloading the Primary Management Module In a St ack of Three or More

Managing OmniSwitch 6350 Stacks Reloading Switches

In this stack of two OmniSwitch 6350 switches, the slot
1 switch is the primary management module. The slot 2
switch is the secondary.

The user reloads the stack’s primary management module
by issuing the reload primary command. Any data flow on
the primary switch’s Ethernet is interrupted.

The secondary switch automatically takes over the pri ­mary role. Ethernet traffic on slot 2 remains unaffected.
Meanwhile the stack has no interim secondary manage­ment module as the switch reboots.

1

2

3

-> reload primary

Primary - Slot 1

Secondary - Slot 2

When the rebooted switch comes back up, it assumes the
secondary management role within the stack.

4

Booting...

Primary - Slot 2

Secondary - Slot 1

Primary - Slot 2

If there are only two switches in the stack, the switch that was reloaded (the former primary) assumes the
secondary role when it comes back up.

Reloading the Primary Management Module In a Stack of Two

OmniSwitch 6450 Hardware Users Guide October 2016 page 7-27

Reloading Switches Managing OmniSwitch 6350 Stacks

In this stack of four OmniSwitch 6350 switches, the slot
1 switch is the primary management module. The slot 2
switch is the secondary. Slots 3 and 4 are operating in
idle roles.

The user reloads the stack’s secondary management
module by issuing the reload secondary command. Any
data flow on the secondary switch’s Ethernet is inter­rupted.

The idle switch with the lowest slot number—in this
case, slot 3—automatically becomes the secondary
management module. The slot 4 switch remains unaf­fected. In addition, Ethernet traffic on slots 1 , 3, and 4
remains unaffected.

1

2

3

-> reload secondary

Primary - Slot 1

Secondary - Slot 2
Idle - Slot 3

Idle - Slot 4

Primary - Slot 1

Booting...

Secondary - Slot 3

Idle - Slot 4

When the rebooted switch comes back up, it assumes an
idle role within the stack.

4

Primary - Slot 1

Idle - Slot 2

Secondary - Slot 3

Idle - Slot 4

Reloading the Secondary Management Module

If the switch with secondary management role is reloaded, the idle switch with the lowest slot number will
automatically assume the secondary role. The reloaded switch (the former secondary) will assume an idle
role when it comes back up.

Meanwhile, the switch with the p rimary management role, as well as any other idle modules in the stack,
continue operations without interruption.

To reload the secondary management module, use the reload command. Be sure to include the syntax
secondary in the command line. For example:

-> reload secondary

Note. A secondary management module reload can also be scheduled for a later time or date. For
information on scheduling a secondary module reload, as well as additional command details, refer to the
OmniSwitch 6250/6350/6450 CLI Reference Guide.

page 7-28 OmniSwitch 6450 Hardware Users Guide October 2016

Reloading the Secondary Management Module In a Stack of Three or More

Managing OmniSwitch 6350 Stacks Reloading Switches

In this stack of two OmniSwitch 6350 switches, the slot
1 switch is the primary management module. The slot 2
switch is the secondary.

The user reloads the stack’s secondary management
module by issuing the reload secondary command. Any
data flow on the secondary switch’s Ethernet is inter­rupted.

As the secondary switch reboots, the primary manage­ment module continues to operate withou t interrupt ion.
Meanwhile the stack has no interim secondary manage­ment module as the switch reboots.

1

2

3

-> reload secondary

Primary - Slot 1

Secondary - Slot 2

When the rebooted switch comes back up, it assumes the
secondary management role within the stack.

4

Primary - Slot 1

Booting...

Primary - Slot 1

Secondary - Slot 2

If there are only two switches in the stack, the switch that was reloaded (the former secondary) resumes
the secondary role when it comes back up.

Reloading the Secondary Management Module In a Stack of Two

OmniSwitch 6450 Hardware Users Guide October 2016 page 7-29

Reloading Switches Managing OmniSwitch 6350 Stacks

Reloading Switches with Idle Roles

Similar to reloading Network Interface (NI) modules on chassis-based switches, modules operating in idle
status within a stack can be reloaded via the CLI.

Note. Any traffic being passed on the module’s Ethernet will be interrupted during the reboot. Other
modules within the stack will continue to operate without interruption.

To reset a single module operating in idle mode, use the reload ni command. Be sure to include the slot
number of the idle switch in the command line. For example:

-> reload ni 3

Only one idle switch can be reloaded at a time. In order to reload multiple idle switches at once, the entire
stack must be reloaded using the reload all command.

After reloading a switch operating in an idle role, the switch resumes idle status when it comes back up,
despite its saved slot number. In other words, if an idle switch with a saved slot number of 1 is reloaded, it
resumes its previous idle role. Although it has the lowest possible saved slot number, it does not take over
the primary management role. In order for this switch to take over the primary role, all swit ches in the
stack must be reloaded.

Note. For more information on reloading all the switches in a stack, refer to pa ge 7-31 . For more
information on idle status, refer to page 7-11.

Reloading Switches in Pass-Through Mode

Pass-through mode is a state in which a switch has attempted to join a stack but has been denied primary,
secondary, and idle status. Because this is essentially an error state, the pass-through condition m ust be
resolved and any modules operating in pass-through mode must be reloaded.

To reload a module operating in pass-through mode, use the reload pass-through command. Be sure to
include the slot number of the pass-through switch in the command line. For example:

-> reload pass-through 1001

Note. Before issuing the reload pass-through command, be sure to resolve any conditions causing the
switch to operate in pass-through mode. Otherwise, the switch is likely to come up again in pass-through
mode. For detailed information, including steps used to recover from pass-through, refer to page 7-12.

page 7-30 OmniSwitch 6450 Hardware Users Guide October 2016

Managing OmniSwitch 6350 Stacks Reloading Switches

Reloading All Switches in a Stack

Reloading all switches in the stack is essentially a full reboot of the virtual chassis. This can be useful in
restoring a stack’s previously configured topology—i.e., the stack’s saved slot numbers and management
roles. Note, however, that all data flow on the stack is interrupted whenever a full reboot is issued.

To reset all switches in a stack use the reload all command. For example:

-> reload all

Note. Before issuing the reload all command, be sure to read the sections below. Understanding topics
such as software synchronization and the effects of saved slot information can help users avoid
unexpected results following a full stack reboot.

Software Synchronization During a Full Reload

If the checksum value on the stack’s non-primary switches differs in any way from the checksum value on
the primary switch, the primary switch automatically distributes its system and configuration software to
all other switches in the stack whenever a full reload is executed.

During this automatic software synchronization, system and configuration software on the secondary and
idle switches is overwritten. Because the primary switch’s “last known good” software is propagated to all
switches, the synchronization process helps ensure effective redundancy across the stack.

Effects of Saved Slot Number Information on the Reload Process

Depending on the status of saved slot information across the stack, there are different slot numbering and
management role scenarios that can occur following a full reboot. For this reason, checking the current
stack topology before issuing a full reboot is strongly recommended. To check the current stack topology,
use the show stack topology command. Refer to the OmniSwitch 6250/6350/6450 CLI Ref erence Guide
for detailed command information.

Possible saved slot number conditions include:

• All switches have unique saved slot information

• No switches in the stack have saved slot information

• Some switches have saved slot information, others do not

• Two or more switches have duplicate slot information

All Switches Have Unique Saved Slot Information

If a full reload is issued and all switches have unique slot numbers saved to their boot.slot.cfg files, the
slot numbers will be assigned according to the saved slot information. The primary management role will
be given to the switch with the lowest saved slot number. The secondary management role will be given to
the switch with the second-lowest saved slot number. All other switches will be assigned to idle roles.

An illustrated example of this method for assigning slot numbers and management roles is provided on
pages 7-22 and 7-23.

OmniSwitch 6450 Hardware Users Guide October 2016 page 7-31

Reloading Switches Managing OmniSwitch 6350 Stacks

No Switches In the Stack Have Saved Slot Information

If a full reload is issued and no switches in the stack have unique slot numbers, slot numbers will be
assigned beginning with the switch with the lowest MAC address. (This can occur if the boot.slot.cfg file
has been deleted from each switch’s /flash directory—e.g., by issuing the stack clear slot command for all
modules in the stack.)

The switch with the lowest MAC address is assigned slot number 1 and given the primary management
role. The switch connected to stacking port A of the primary switch is automatically assigned slot
number 2 and given the secondary management role. Stack cabling is then used to determine the dynamic
slot numbering of the remaining modules in the stack. The switch immediately adjacent to slot 2 is
assigned slot number 3 and given an idle role, etc.

An illustrated example of this method for assigning slot numbers and management roles is provided on
pages 7-20 and 7-21.

Some Switches Have Saved Slot Information, Others Do Not

If only some switches in the stack have boot.slot.cfg files in their /flash directories, the system software
will first read the contents of these files and then dynamically assigns unique slot numbers to any switches
that do not have saved slot information. The primary management role will be given to the switch with the

lowest saved slot number. The secondary management role will be given to the switch with the second-
lowest saved slot number. All other switches will be assigned to idle roles.

When unique slot numbers are dynamically assigned by the system software, a boot.slot.cfg file is
automatically generated with the new slot information. Because all switches now have unique saved slot
information, any subsequent reload all commands issued will cause the stack to come up as described in
the section, “All Switches Have Unique Saved Slot Information” on page 7-31.

Two or More Switches Have Duplicate Slot Information

If a full stack reboot is issued and the same slot number is found in the boot.slot.cfg file of two or more
switches, the switch with the lowest MAC address is allowed to come up and operate normally.
Meanwhile, any other switches with the duplicate slot number come up in pass-through mode.

The pass-through mode is essentially an error state in which a switch has been denied primary, secondary,
and idle roles within the stack. When a switch is in pass-through mode, its Ethernet are brought down and
cannot pass traffic. It is for this reason that users should always check the current saved slot number for
each switch before issuing the reload all command. To check the current saved slot information across the
stack, use the show stack topology command. For detailed information on pass-through mode, refer to

“Pass-Through Mode” on page 7-12.

page 7-32 OmniSwitch 6450 Hardware Users Guide October 2016

Managing OmniSwitch 6350 Stacks Reloading Switches

Avoiding Split Stacks

The term “splitting” a stack refers to the creation of isolated modules within the virtual chassis. A split
stack can result from the following conditions:

• Two or more non-adjacent switches are reloaded simultaneously

• The stack is reloaded without a redundant stacking cable connection

The sections below offer simple guidelines for avoiding splitting the stack during the reload process.

Do Not Reload Non-Adjacent Switches Simultaneously

If non-adjacent switches in the stack—for example, the top switch in the stack and the third-from-top
switch in the stack—are reloaded simultaneously, a problem will occur. The switch between the two non­adjacent switches will become isolated and the virtual chassis will be effectively split.

To avoid splitting the stack, do not reload the two non-adjacent switches simultaneously. Instead, simply
reload the top switch first, then reload the third-from-top switch, or vice-versa.

Be Sure a Redundant Stacking Cable is Installed at All Times

Another important guideline for avoiding split stacks involves the redundant stacking cable. In order to
avoid isolated modules within the virtual chassis, simply make sure that a redundant stacking cable
connection exists between the top-most and bottom-most switches at all times.

For more information on the redundant stacking cable connection, refer to page 7-17.

OmniSwitch 6450 Hardware Users Guide October 2016 page 7-33

Changing the Secondary Module to Primary Managing OmniSwitch 6350 Stacks

In this stack of four OmniSwitch 6350 switches, the slot
1 switch is the primary management module. The slot 2
switch is the secondary. Slots 3 and 4 are operating in
idle roles.

A takeover is initiated by the user; the primary manage­ment module is automatically reload ed . An y da ta flow on
the primary switch’s Ethernet is interrupted.

The secondary switch takes over the primary role. The idle
switch with the next-lowest slot number—in this case, slot
3—automatically becomes the secondary management
module. The slot 4 switch remains unaffected. In addition,
Ethernet traffic on slots 2, 3, and 4 remains unaffected.

1

2

3

-> takeover

Primary - Slot 1

Secondary - Slot 2

Idle - Slot 3

Idle - Slot 4

Booting...

Primary - Slot 2
Secondary - Slot 3

Idle - Slot 4

When the former primary switch comes back up, it
assumes an idle role within the stack.

4

Idle - Slot 1

Primary - Slot 2
Secondary - Slot 3

Idle - Slot 4

Changing the Secondary Module to Primary

OmniSwitch 6350 stacks allow users to manually force the secondary switch to assume the primary
management role. This is referred to as “takeover.” The behavior of a takeover is similar to that of
reloading the primary management module (see page 7-26).

Whenever a takeover is initiated, the switch with the secondary role automatically takes over primary
management functions. The primary switch is automatically reloaded and any traffic being passed on the
primary switch’s Ethernet is interrupted.

Meanwhile, the idle switch with the next-lowest slot number automatically assumes the secondary role.
When the former primary module comes back up, it assumes an idle role within the stack.

To initiate a takeover sequence, use the takeover command. For example:

-> takeover

Note. Before using the takeover command, verify that the switches in the stack are synchronized.
Otherwise, data flow and switch management functions may be interrupted due to incorrect or outdated
software when a switch takes over the primary management role. For more information, refer to

“Synchronizing Switches in a Stack” on page 7-36.

Takeover Behavior In a Stack of Three or More

page 7-34 OmniSwitch 6450 Hardware Users Guide October 2016

Managing OmniSwitch 6350 Stacks Changing the Secondary Module to Primary

In this stack of two OmniSwitch 6350 switches, the slot
1 switch is the primary management module. The slot 2
switch is the secondary.

A takeover is initiated by the user; the primary man­agement module is automatically reloaded. Any data
flow on the primary switch’s Ethernet is interrupted.

The secondary switch takes over the primary role.
Ethernet traffic on slot 2 remains unaffected. Mean­while the stack has no interim secondary management
module as the switch reboots.

1

2

3

-> takeover

Primary - Slot 1

Secondary - Slot 2

When the former primary switch comes back up, it
assumes the secondary management role within the
stack.

4

Booting...

Primary - Slot 2

Secondary - Slot 1

Primary - Slot 2

If there are only two switches in the stack, the former primary switch resumes the secondary role when it
comes back up following the takeover.

Takeover Behavior In a Stack of Two

OmniSwitch 6450 Hardware Users Guide October 2016 page 7-35

Synchronizing Switches in a Stack Managing OmniSwitch 6350 Stacks

Synchronizing Switches in a Stack

Management module synchronization refers to the process of copying all files in the /flash/working and
/flash/certified directories of the primary management module to the /flash/working and /flash/certified

directories of all the other switches in the stack. The system and configuration software on the non­primary switches—i.e., the secondary management module and any modules operating in idle—is
overwritten.

The synchronization process ensures that the contents of these directories match exactly for all switches
across the stack. This can be especi ally useful after new software has been loaded to the primary
management module. Further, synchronization prevents any switch from assuming a management role
within the stack with incorrect or outdated software or configuration files. Because the primary switch’s
“last known good” software is propagated to all switches, the synchronization process helps ensure
effective redundancy across the stack.

In order to maintain effective management module redundancy, switches in the stack must be
synchronized at all times. To determine whether a stack is in need of synchronization, use the show

running-directory command. For example:

-> show running-configuration

CONFIGURATION STATUS
Running CMM : PRIMARY,
CMM Mode : MONO CMM,
Current CMM Slot : 1,
Running configuration : CERTIFIED,
Certify/Restore Status : CERTIFY NEEDED
SYNCHRONIZATION STATUS
Running Configuration : NOT SYNCHRONIZED,

This example shows a switch on which the /flash directories between the management modules are not
synchronized. To manually synchronize all switches in the stack, enter the following command:

-> copy working certified flash-syncro

When the synchronization process is initiated, modules within the stack continue to operate without
interruption and data flow across the stack is unaffected.

Automatic Synchronization During a Full Reload

If the checksum value on the stack’s non-primary switches differs in any way from the checksum value on
the primary switch, the primary switch automatically distributes its system and configuration software to
all other switches in the stack whenever a full reload is executed.

For more information on initiating a full reload, see “Reloading All Switches in a Stack” on page 7-31.

Note. For more information on management module synchronization and managing the /flash/working
and /flash/certified directories, refer to the “Managing CMM Directory Content” chapter in the
OmniSwitch 6250/6350/6450 Switch Management Guide.

page 7-36 OmniSwitch 6450 Hardware Users Guide October 2016

Managing OmniSwitch 6350 Stacks Stack Split Detection (SSP)

Stack Split Detection (SSP)

In the case of a stack split due to a stacking link failure or the failure of one of the stack elements, both of
the resulting stacks could end up having the same system MAC and IP addresses. Since there is no
communication between these individual stacks due to the stacking link failure they end up
communicating with the rest of the network devices using the same MAC and IP addresses. This stack
split scenario is disruptive to the network as the conflicting MAC and IP addresses can lead to layer 2
loops and L3 traffic disruption.

Stack Split Detection provides the following ben efits:

• Avoid network disruptions by preventing duplicate MAC and IP addresses on the network when MAC

retention is enabled and a stack split occurs.

• The sub-stack that forms out of the stack split is able to detect that a stack split has occurred.

• Once the stack split condition has been determined, the sub-stack will put its front-panel ports into an

operationally down state preventing traffi c forwarding and avoiding loops and possible traffic
disruption. The SSP link will be shut down after the protection mode SSP PDU is sent to the helper and
the acknowledgment is rece ived from the helper by the protection mode unit.

• A trap can be sent by the active-stack indicating the stack split state. The trap indicates that the stack

split has occurred and which elements are in the operationally down sub-stack.

• A mechanism is available to recover the non-operational sub-stack.

• A method of detecting a stack split in a remote stacking topology where the stack may consist of

elements located in different physical locations such as a remote site, or multiple floors of a building.

A redundant stacking cable connection should be used for proper SSP functionality. For more information
on helping to avoid stack splits with redundant stacking cable connections, refer to page 7-17.

Stack Split Key Components and Terms

• SSP PDU - A proprietary packet forwarded between stack elements to help determine that state of the

stack.

• SSP Helper - A neighboring OmniSwitch, not an element of the stack, responsible for forwarding SSP

PDUs between the stack elements. The SSP feature and the SSP Helper functionality cannot be enabled
on the same switch for the same link aggregate ID.

• SSP Link Aggregate - A dedicated link aggregate configured between elements of a stack and a helper

switch to be used for forwarding SSP PDUs.

• Active-stack - An element, or multiple elements, that results when a split stack occurs. The active-

stack will keep its front panel ports enabled and continue to forward traffic on the network.

• Sub-stack - An element, or multiple elements, that results when a split stack occu rs. The sub-stack will

disable its front panel ports to prevent traffic disruption caused by duplicate MAC/IP addresses with
the active stack.

• Protection State - A state an element will transition to after determining a stack split has occurred. Its

ports will be operationally disabled to to prevent duplicate MAC and IP addresses and network
disruption.

• Guard Timer - A configurable timer determining how long a unit will wait before beginning to send

SSP PDUs after a stack recovery.

OmniSwitch 6450 Hardware Users Guide October 2016 page 7-37

Stack Split Detection (SSP) Managing OmniSwitch 6350 Stacks

Basic Operation

When stack split detection is enabled, a proprietary pr otocol runs on a configured link aggregate to carry
the stack information necessary for stack split detection. Stack elements share a link aggregate with an
OmniSwitch that can act as a helper to assist in the stack split detection.

The lowest member port of the link aggregate hosted on the primary element is responsible for sending the
SSP PDUs on the member link. When the packet arrives on the remote helper device then the helper
device will forward the packet out on all member ports of the link aggregate so that the packet reaches the
remote stack elements.

Use the the stack split-protection and stack split-protection linkaggid commands to enable SSP and
create the SSP link aggregate on the stack.

Use the the stack split-protection helper and stack split-protection helper linkagg commands to enable
the SSP helper and create the SSP helper link aggregate on the helper switch.

Protection States

Under normal stack circumstances the SSP PDUs are sent once every 3 seconds. When the stack detects a
scenario which leads to a change in its size the protocol sends the SSP PDUs at a rate of 1 per 250
milliseconds for 120 seconds. This helps to quickly identify a stack spli t.

On reception of a SSP frame, the receiving elements match the primary of their current stack against the
MAC address of the SSP sender. If there is a mismatch between the two, then that indicates the presence
of an active stack in the network which is disconnected from the current stack. In this condition the stack
element will monitor 3-5 such consecutive frames, after which it will transition to the protection state.

When an element transitions to the protection state, the following occurs:

• Each of the stack elements will independently transition into the protection state.

• In the protection state each of the stack elements will disable all the user ports except the ones

belonging to the SSP protection link aggregate.

• The stack element will store the protection state transi tio n info rmation in a non-volatile location

(EEPROM/ boot.params). This information will be used whenever an element in the protection state re­boots and needs to check its current operational state.

• An element in the protection state will send an SSP PDU back on the link aggregate carrying the SSP

state as PROTECTION. This is the only frame that is sent by the protection sub-stack. The purpose of
this message is to inform the active-stack to generate an SNMP trap regarding the stack split state of
the stack element.

Stack Split Recovery

Once a sub-stack goes into the protection state then all the front panel ports are put into an operationally
down state. There are two ways to recover the stack, manually or automatically.

Manual Recovery:

If the guard timer is 0, automatic recovery is disabled and the sub-stack stays in protection mode until the
unit is reloaded by the administrator. After the re-boot the administrator has to manually recover the
switch by first disabling SSP and then re-enabling SSP. This clears the protection state variables stored in
the EEPROM/boot.params.

page 7-38 OmniSwitch 6450 Hardware Users Guide October 2016

Managing OmniSwitch 6350 Stacks Stack Split Detection (SSP)

1. Stack split detected, substack transitions to PROTECTION state.

2. Sub-stack front panel ports shutdown to avoid duplicate addresses on network

3. PROTECTION PDUs sent by sub-stack to active-stack over helper linkagg.

4. Active-stack sends trap indicating stack split.

1

Normal Opera­tion

SSP PDUs sent over helper linkagg and relayed by helper switch.

2

Stack Split

Helper switch.

Sub-stack

Active-stack

3

Recovery

Helper switch.

1. Stacking link recovers, new elements detected by Primary.

2. Manual Recovery - Administrator disables/enables SSP to clear PROTECTION state.

3. Automatic Recovery - After guard-timer expiration, Primary will bring up elements one at a time.

4. Once stack is functioning, Primary will send trap indicating stack recovery.

Use the stack split-protection guard-timer and the stack split-protection commands to configure the
guard timer and enable/disable SSP.

Automatic Recovery

If the stacking link recovers and the sub-stack reconnects to the active stack the sub-stack will
automatically reboot. The protection units will come up in the protection state; however they will now be
part of the active stack but their front panel ports will still be disabled. The primary of the combined stack
will detect that there are new elements in the protection state. The primary will wait for the guard timer to
expire and will then bring one element at a time from the protection state until all elements are active.

Once complete, the primary will generate a trap indicating the stack has been recovered.

Stack Split Example

OmniSwitch 6450 Hardware Users Guide October 2016 page 7-39

Monitoring the Stack Managing OmniSwitch 6350 Stacks

Monitoring the Stack

As shown in the previous sections, monitoring the current status and operation of all elements in a stack
can help users avoid unexpected stack conditions. The table below includes CLI commands that are useful
in monitoring stack conditions.

CLI Commands Used for Monitoring a Stack

show stack topology Displays the current operating topology of switches within a stack.
show stack status Displays the current redundant stacking cable status.
show running-directory Displays the directory from where the switch was booted. This com-

mand also shows important information, including whether the soft ­ware across the stack is synchronized.

show chassis Displays basic configuration and status information for the switch

chassis.

show cmm Displays basic hardware and status information for primary and

secondary management modules operating in the stack.

show ni Displays basic hardware and status information for modules currently

operating in the stack.

show module Displays basic information for modules installed in the stack. Modules

include primary and secondary management mod ule s an d any modules
operating in idle status.

show module long Displays detailed information for modules installed in the stack. Mod-

ules include primary and secondary management modules and any
modules operating in idle status.

show module status Displays basic status information for modules installed in the stack.

Modules include primary and secondary management modules and any
modules operating in idle status.

show power Displays hardware information and current status for chassis power

supplies. This includes the status of backup power supplies, if applica­ble.

show fan Displays the current operating status of each of the six fans operating in

each chassis.

show temperature Displays the current operating chassis ambient temperature, as well as

current temperature threshold settings for each of the modules in the
stack.

Visually Monitoring the Stack

Users can also monitor many stack operations by viewing the front panel LEDs on all elements in the
stack. Refer to “OmniSwitch 6350 LED Status” on page 3-21 for detailed information on LEDs and stack
status.

page 7-40 OmniSwitch 6450 Hardware Users Guide October 2016

Managing OmniSwitch 6350 Stacks Monitoring the Stack

CLI Commands Supported on Both Primary and Secondary Management Modules

Although most CLI commands are executed when logged into the switch with the primary management
role, there is a group of commands that is supported when logged in to either the primary or secondary
management module. For a list of these commands, refer to the tables below.

Note. For detailed information on these commands, including command syntax options and definitions,
refer to the OmniSwitch 6250/6350/6450 CLI Reference Guide.

CMM Commands

reload
takeover
install

debug chassis auto-reboot
show running-directory
show reload

Chassis Management and Monitoring Commands

show system
show hardware info
show chassis

show module
show module long
show module status

File Management Commands

cd
pwd
mkdir
rmdir
ls
dir
rename
rm

delete
cp
mv
move
chmod
attrib
fsck
newfs

show microcode

show cmm
show ni

ed
vi
view
tty
show tty
rz
more
install

Switch Logging and Monitoring Commands

swlog
swlog appid level
swlog output
show log swlog
show swlog

debug ktrace
debug ktrace appid level
debug ktrace show
debug systrace
debug systrace appid level

debug systrace show
debug systrace show log
debug memory monitor
debug memory monitor show log

Memory Monitoring Commands

show log pmd

OmniSwitch 6450 Hardware Users Guide October 2016 page 7-41

Monitoring the Stack Managing OmniSwitch 6350 Stacks

page 7-42 OmniSwitch 6450 Hardware Users Guide October 2016

4 Mounting

OmniSwitch 6350 Switches

This chapter covers different mounting and installation options. OmniSwitch 6350 switches may be
either table- or rack-mounted.

Anti-Static Warning. Before handling any components, free yourself of static by wearing a grounding
strap or by grounding yourself properly. Static discharge can damage the switch and related components.

OmniSwitch 6350 Hardware Users Guide October 2016 page 4-1

General Installation Recommendations Mounting OmniSwitch 6350 Switches

6 inches minimum at
front of chassis.

2 inches minimum at
left and right sides.

}

}

6 inches minimum at
rear of chassis.

General Installation Recommendations

Airflow Recommendations

To ensure proper airflow, be sure that your switch is pl aced i n a wel l-ventilated area and provide minimum
recommended clearance at the front, back and sides of the switch, as shown below. Restricted airflow can
cause your switch to overheat, which can lead to switch failure.

Note. Clearance is not required at the top and bottom of the chassis. Clearance recommendations at the
front and rear of chassis are for access to cabling and components only and are not intended as a specific
airflow requirement.

page 4-2 OmniSwitch 6350 Hardware Users Guide October 2016