Os6450 HDW Revl
Os6450 HDW Revl
Os6450 HDW Revl
L
April 2017
OmniSwitch 6450
Hardware Users Guide
enterprise.alcatel-lucent.com
This user guide documents OmniSwitch 6450 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. (2017)
This OmniSwitch 6450 Hardware Users Guide describes your switch hardware components and basic
switch hardware procedures.
• Descriptions of hardware components (status LEDs, chassis, cables, backup power supplies, etc.).
• Managing a chassis.
Documentation Roadmap
The OmniSwitch user documentation suite was designed 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.
When you are ready to connect your switch to the network, you will need to learn how the OmniSwitch
implements fundamental software 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
The OmniSwitch AOS Release 6 CLI 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 variable 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 infor-
mation on each CLI command.
Related Documentation
The following are the titles and descriptions of OmniSwitch 6450-related user manuals:
• OmniSwitch 6450 Hardware Users Guide
Detailed technical specifications and procedures for the OmniSwitch chassis and components. This
manual also includes comprehensive information on assembling and managing stacked configurations.
• OmniSwitch AOS Release 6 CLI Reference Guide
Complete reference to all CLI commands supported on OmniSwitch products. Includes syntax defini-
tions, default values, examples, usage guidelines and CLI-to-MIB variable mappings.
• OmniSwitch AOS Release 6 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).
• OmniSwitch AOS Release 6 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.
• OmniSwitch AOS Release 6 Transceivers Guide
Includes open problem reports, feature exceptions, and other important information on the features
supported in the current release and any limitations to their support.
http://support.esd.alcatel-lucent.com
Technical Support
An Alcatel-Lucent 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 prod-
uct’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’s Service Programs, see our web page at
service.esd.alcatel-lucent.com, call us at 1-800-995-2696, or email us at ebg_global_supportcenter@al-
enterprise.com.
OS6450-10(L); OS6450-10M
OS6450-P10(L); OS6450-P10S
OS6450-24(L); OS6450-24X;
OS6450-24XM
OS6450-P24(L); OS6450-P24X
OS6450-48(L); OS6450-48X
OS6450-P48(L); OS6450-P48X
OS6450-U24; OS6450-U24X;
OS6450-U24S; OS6450-U24SXM
Chassis Configurations
10/100BaseT Models (with Available Upgrades*)
• OmniSwitch 6450-10(L)**
• OmniSwitch 6450-24(L)**
• OmniSwitch 6450-48(L)**
• OmniSwitch 6450-P24(L)**
• OmniSwitch 6450-P48(L)**
* Note. Available upgrades include 10/100/1000BaseT support, as well as factory-installed Metro support
and 10G uplink support. For Metro and 10G model numbers, refer to the “Metro Models” and “10G
Models” sections below.
** Note. “L” models have the same hardware characteristics as “non-L” models but can be upgraded to
support 10/100/1000BaseT via software license upgrade.
• OmniSwitch 6450-U24SXM (also includes 1588v2-PTP support, Metro support and factory-enabled
10G uplink support)
Metro Models
OmniSwitch 6450 “M” models provide factory-enabled Metro Ethernet support. Metro models include:
• OmniSwitch 6450-10M
10G Models
OmniSwitch 6450 “X” models provide factory-enabled 10G uplink support. 10G uplink models include:
• OmniSwitch 6450-24X
• OmniSwitch 6450-P24X
• OmniSwitch 6450-U24X
• OmniSwitch 6450-48X
• OmniSwitch 6450-P48X
• OmniSwitch 6450-U24S
• OmniSwitch 6450-U24SXM (also includes factory-enabled 10G uplink and Metro support)
Note. PoH is supported on OmniSwitch 6450-P10S models only. PoE support of up to 30W per port is
provided on PoE ports 5 through 8. The maximum PoE power budget available for all ports on the
OmniSwitch 6450-P10S is 280W. Refer to Chapter 3, “OmniSwitch 6450 Chassis and Hardware
Components” for more information.
Note. PTP is supported on OmniSwitch 6450-P10S and OmniSwitch 6450-U24S models only. When PTP
mode is enabled, OmniSwitch 6450-U24S switches act as a standalone devices and cannot become part of
a stack. Refer to Chapter 3, “OmniSwitch 6450 Chassis and Hardware Components” for more information.
Security Features
OmniSwitch 6450 switches offer extensive 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 6450 switches incorporate advanced Alcatel-Lucent Operating System (AOS) protocols 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
“last 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:
• Switches (virtual NI modules) within a virtual chassis stack. Refer to “Hot-Swapping Modules In a
Stack” on page 7-25 for more information.
• 1G uplink modules (“like” kinds only). Refer to “Swapping Expansion Modules” on page 7-3 for
more information.
• 10G stacking modules (“like” kinds only). Refer to “Swapping Expansion Modules” on page 7-3 for
more information.
• Power supply connector cables
Note. Backup power supplies are fully operational and may share the load with the primary power supply,
remaining operational in the event the primary power supply fails unexpectedly. If a failover occurs, the
backup power supply automatically takes up the full power load without disrupting the switch.
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.
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 6450 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 6450 Chassis and
Hardware Components.” The show commands for all the features are described in detail in the
OmniSwitch AOS Release 6 CLI Reference Guide.
Site Preparation
Environmental Requirements
OmniSwitch 6450 switches have the following environmental and airflow requirements:
• The installation site must maintain a temperature between 0° and 45° Celsius (32° and 113° Fahrenheit)
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-3 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.
Redundant AC Power. It is recommended that each AC outlet resides on a separate circuit. With
redundant AC, if a single circuit fails, the switch’s remaining power supplies (on separate circuits)
can remain operational.
Unpack your OmniSwitch 6450 chassis as close as possible to the location where it will be installed.
Items Included
Your OmniSwitch 6450 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
Depending on model type, the OmniSwitch 6450 chassis weighs between 4.08 kg (9.00 lbs) and
6.80 kg (15.00 lbs).
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.
Note. Clearance is not required at the top and bottom of the chassis.
Note. For additional information on cabling connections, refer to the OmniSwitch AOS Release 6 Switch
Management Guide.
For information on modifying these settings, refer to the OmniSwitch AOS Release 6 Switch
Management Guide.
Component LEDs
During the boot process, component LEDs will flash and change color, indicating different stages of the boot.
Following a successful boot, chassis LEDs should display as follows:
Note. If the LEDs do not display as indicated, make sure the boot process is complete. If the LEDs do not
display as indicated following a complete boot sequence, contact Alcatel-Lucent Customer Support. For
information on LED states, refer to “Chassis Status LEDs” on page 3-19.
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-6.
Important. You must be connected to the switch via the console port before initiating your first
login session.
->
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 OmniSwitch AOS Release 6
Switch Management Guide.
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 OmniSwitch AOS Release 6 Switch Management Guide.
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 OmniSwitch CLI Reference Guide for complete aaa authentication command syntax options.
1 Be sure that you have logged into the switch as user type admin (see “Logging In to the Switch” on
page 2-6).
2 Enter the keyword password and press Enter.
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
OmniSwitch AOS Release 6 Switch Management Guide.
For detailed information on configuring a time zone for the switch, refer to the OmniSwitch AOS Release 6
Switch Management Guide.
To set the current date for the switch, enter system date, followed by the current date in mm/dd/yyyy.
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.
OmniSwitch 6450 switches are available in the chassis configurations as shown in the table below:
Note. The 10/100BaseT “L” models have the same hardware characteristics as the other models but can be
upgraded to support 10/100/1000BaseT via a software license upgrade.
This chapter includes detailed information on these chassis types. Topics include:
• OmniSwitch 6450 chassis descriptions
• Technical specifications
• Power Supplies
• Cables and power cords
• Console port and pinout specifications
OmniSwitch 6450-10
Chassis Features
System status LEDs Internal AC Power Supply
(8) Non-combo 10/100/1000Base-T ports Console port (RJ-45)
(2) Non-combo 100/1000BaseX ports USB port (USB 2.0)
(2) Combo 10/100/1000Base-T or Fanless design
100/1000BaseX ports
Front Panel
A B
1 2 3 4 5 6 7 8 9 10 11 12
OS6450-10
Console
C D E F
G
Item Description
A System Status LEDs
Provides status on hardware, software, and power.
B Console Port
RS-232 console port with an RJ-45 connector. Provides access to the CLI for configuration and
management.
C 10/100/1000BaseT RJ-45 Ports
10/100/1000BaseT non-combo ports. Odd-numbered ports are on top row, even-numbered ports
are on bottom row.
D 10/100/1000BaseT or 100/1000BaseX SFP Combo Ports
Two 10/100/1000BaseT or SFP combo ports for various supported SFP transceivers.
E SFP Uplink Ports
Two SFP ports to be used for uplinks.
F USB Port
High speed USB 2.0 port.
G Push Button
When pushed, all LEDs will turn off and the LED of the Stack ID will remain lit.
(Applies to 24- and 48-port switches.)
Refer to “OmniSwitch 6450 LED Status” on page 3-33 for LED status information.
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.
A B
Item Description
A Power Supply Connector
Internal AC power supply.
B Grounding Block
Type LCD8-10A-L grounding lug
OS6450-10 Specifications
10/100/1000BaseT ports 8
Total combo ports 2
SFP uplink ports 2
802.3at PoE ports N/A
Flash memory size 128 MB
RAM memory size 256 MB SDRAM
Chassis Width 8.50 inches (21.5 cm)
Chassis Height 1.73 inches (4.40 cm)
Chassis Depth 11.50 inches (29.21 cm)
Weight 3.66 lbs (1.66 kg)
Operating Humidity 5% to 95%
Storage Humidity 5% to 95%
Operating Temperature 0C to +45C
Storage Temperature -40C to +75C
Default Upper Threshold 81C
Temperature
Danger Threshold Temperature 85C
Data rate (RJ-45) 10/100/1000 Mbps
Maximum frame size 9216 bytes
Cable supported 10BaseT: unshielded twisted-pair (UTP)
(RJ-45) 100BaseTX: unshielded twisted-pair (UTP), Category 5, EIA/TIA 568
or shielded twisted-pair (STP), Category 5, 100 ohm
1000BaseT: unshielded twisted-pair (UTP), Category 5e
Maximum cable distance 100 meters
(RJ-45)
Remote Stacking Support Does not support remote stacking
OmniSwitch 6450-P10
Chassis Features
System status LEDs Internal AC Power Supply
(8) Non-combo 10/100/1000Base-T PoE ports Console port (RJ-45)
(2) Non-combo 100/1000BaseX ports USB port (USB 2.0)
(2) Combo 10/100/1000Base-T or Fanless design
100/1000BaseX ports
Front Panel
A
B
1 2 3 4 5 6 7 8 9 10 11 12
OS6450-P10
Console
C D E F
G
Item Description
A System Status LEDs
Provides status on hardware, software, and power.
B Console Port
RS-232 console port with an RJ-45 connector. Provides access to the CLI for configuration and
management.
C 10/100/1000BaseT RJ-45 PoE Ports
10/100/1000BaseT non-combo ports. Odd-numbered ports are on top row, even-numbered ports
are on bottom row.
D 10/100/1000BaseT or 100/1000BaseX SFP Combo Ports
Two 10/100/1000BaseT or SFP combo ports for various supported SFP transceivers.
E SFP Uplink Ports
Two SFP ports to be used for uplinks.
F USB Port
High speed USB 2.0 port.
G Push Button
When pushed, all LEDs will turn off and the LED of the Stack ID will remain lit. (Not currently
supported. Functionality scheduled for future release.)
Refer to “OmniSwitch 6450 LED Status” on page 3-33 for LED status information.
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.
A B
Item Description
A Power Supply Connector
Internal AC power supply.
B Grounding Block
Type LCD8-10A-L grounding lug
OS6450-P10 Specifications
Total non-combo 10/100/ 8 (1-8)
1000BaseT PoE ports per switch
Total combo ports per switch 2 (9-10)
Total non-combo SFP ports per 2 (11-12 in Uplink mode)
switch
Flash memory size 128 MB
RAM memory size 256 MB SDRAM
Chassis Width 8.50 inches (21.5 cm)
Chassis Height 1.73 inches (4.40 cm)
Chassis Depth 11.50 inches (29.21 cm)
Weight 4.56 lbs (2.07 kg)
Operating Humidity 5% to 95%
Storage Humidity 5% to 95%
Operating Temperature 0C to +45C
Storage Temperature -40C to +75C
Default Upper Threshold Tem- 73C
perature
Danger Threshold Temperature 82C
Data rate (RJ-45) 10/100/1000 Mbps
Maximum frame size 9216 bytes
Cable supported 10BaseT: unshielded twisted-pair (UTP)
(RJ-45) 100BaseTX: unshielded twisted-pair (UTP), Category 5, EIA/TIA 568
or shielded twisted-pair (STP), Category 5, 100 ohm
1000BaseT: unshielded twisted-pair (UTP), Category 5e
Maximum cable distance 100 meters
(RJ-45)
Remote Stacking Support Does not support remote stacking
OmniSwitch 6450-P10S
The OmniSwitch 6450-P10S is a standalone switch with eight (8) 10/100/1000 Base-T PoE ports and two
(2) fixed fiber ports (100FX/1000-X).
OmniSwitch 6450-P10S switches support IEEE 1588 Precision Time Protocol (PTP).
All ports support IEEE 802.3af/802.3at.
PoE (four pair) ports 1-4 are compliant with the PoE portion of the Power over HD Base-T (PoH) standard
with a 280W PoE power budget. These ports are labeled “HPoE” on the chassis front panel.
PoE support of up to 30W per port is provided on PoE ports 5 through 8.
Note. The maximum PoE power budget available for all ports is 280W.
Front Panel
A B C D E
F G H
I
Item Description
A System Status LEDs
Provides status on hardware and software.
B PoH Port Status LEDs
Provides status on HPoE-capable (PoH) ports, including connectivity and link activity.
(These ports are labeled “HPoE” on the chassis front panel.)
C Back-lit Power Status LED
Illuminates model name on chassis front panel to indicate “power on” status.
D PoE Port Status LEDs
Provides status on PoE ports, including connectivity and link activity.
E Console Port
RS-232 console port with an RJ-45 connector. Provides console access to the CLI for
configuration and management.
F Four (4) 10/100/1000BaseT RJ-45 PoH Ports
Port numbers 1 through 4. Each port provides ~75W of PoH power. (These ports are labeled
“HPoE” on the chassis front panel.)
Item Description
G Four (4) 10/100/1000BaseT RJ-45 PoE Ports
Port numbers 5 through 8. Each port provides up to 30W of PoE power.
H Two (2) 100FX/1000-X Fixed Fiber Ports
I USB Port
High speed USB 2.0 port.
Refer to “OmniSwitch 6450 LED Status” on page 3-33 for LED status information.
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.
A B C
Item Description
A Air Vent
Intake vent for internal chassis airflow.
B Power Supply Connector
Internal AC power supply.
C Grounding Block
Type LCD8-10A-L grounding lug
* The maximum PoE power budget available for all ports is 280W.
OmniSwitch 6450-24
Chassis Features
System status LEDs Internal AC Power Supply
(24) Non-combo 10/100/1000Base-T ports Console port (RJ-45)
(2) Non-combo SFP/SFP+ ports USB port (USB 2.0)
Expansion Module Stacking LED
Front Panel
A B C D
E F
G
Item Description
A Stacking LED
Displays the chassis stack ID.
B Console Port
RS-232 console port with an RJ-45 connector. Provides access to the CLI for configuration and
management.
C System Status LEDs
Provides status on hardware, software, and power.
D 10/100/1000BaseT RJ-45 Ports
10/100/1000BaseT non-combo ports. Odd-numbered ports are on top row, even-numbered ports
are on bottom row.
E Rear Status LEDs
Displays link status for expansion module ports.
F USB Port
High speed USB 2.0 port.
G SFP/SFP+ Ports
Two SFP/SFP+ ports to be used for uplinks.
Refer to “OmniSwitch 6450 LED Status” on page 3-33 for LED status information.
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.
A B C D
Item Description
A Grounding Block
Type LCD8-10A-L grounding lug
B Power Supply Connector
Internal AC power supply
C Internal Backup Power Supply Slot
D Expansion Module Slot
OS6450-24 Specifications
RJ-45 10/100/1000BaseT ports 24
SFP+ Gigabit/10Gigabit uplink 2
ports
Ports per expansion module 2
Max. chassis per stack 8
Flash memory size 128 MB
RAM memory size 256 MB SDRAM
Chassis Width 17.32 inches (44.00 cm)
Chassis Height 1.73 inches (4.40 cm)
Chassis Depth 12.3 inches (31.24 cm)
Weight 9 lbs (4.08 kg)
Operating Humidity 5% to 95%
Storage Humidity 5% to 95%
Operating Temperature 0C to +45C (32F to 113F)
Storage Temperature -40C to +75C (-40F to +167F)
Default Upper Threshold 74C
Temperature
Danger Threshold Temperature 79C
Data rate (RJ-45) 10/100/1000 Mbps
Maximum frame size 9216 bytes
Cable supported 10BaseT: unshielded twisted-pair (UTP)
(RJ-45) 100BaseTX: unshielded twisted-pair (UTP), Category 5, EIA/TIA 568
or shielded twisted-pair (STP), Category 5, 100 ohm
1000BaseT: unshielded twisted-pair (UTP), Category 5e
Maximum cable distance 100 meters
(RJ-45)
Remote Stacking Support Supports remote stacking
OmniSwitch 6450-P24
Chassis Features
System status LEDs Internal AC Power Supply
(24) Non-combo 10/100/1000Base-T 802.3at PoE Backup Power Supply (BPS) Connector
ports
(2) Non-combo SFP/SFP+ ports Console port (RJ-45)
Expansion Module USB port (USB 2.0)
Stacking LED
Front Panel
A B C D
E F
G
Item Description
A Stacking LED
Displays the chassis stack ID.
B Console Port
RS-232 console port with an RJ-45 connector. Provides access to the CLI for configuration and
management.
C System Status LEDs
Provides status on hardware, software, and power.
D 10/100/1000BaseT RJ-45 PoE Ports
10/100/1000BaseT non-combo ports. Odd-numbered ports are on top row, even-numbered ports
are on bottom row.
E Rear Status LEDs
Displays link status for expansion module ports.
F USB Port
High speed USB 2.0 port.
G SFP/SFP+ Ports
Two SFP/SFP+ ports to be used for uplinks.
Refer to “OmniSwitch 6450 LED Status” on page 3-33 for LED status information.
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.
A B C D
Item Description
A Grounding Block
Type LCD8-10A-L grounding lug
B Power Supply Connector
Internal AC power supply.
C External Backup or PoE Power Supply Connector
OS6450-P24 Specifications
RJ-45 10/100/1000BaseT 24
802.3at PoE ports
SFP+ Gigabit/10Gigabit uplink 2
ports
Ports per expansion module 2
Max. chassis per stack 8
Flash memory size 128 MB
RAM memory size 256 MB SDRAM
Chassis Width 17.32 inches (44.00 cm)
Chassis Height 1.73 inches (4.40 cm)
Chassis Depth 12.30 inches (31.24 cm)
Weight 11 lbs (5.05 kg)
Operating Humidity 5% to 95%
Storage Humidity 5% to 95%
Operating Temperature 0C to +45C (32F to 113F)
Storage Temperature -40C to +75C (-40F to +167F)
Data rate (RJ-45) 10/100/1000 Mbps
Default Upper Threshold 60C
Temperature
Danger Threshold Temperature 66C
Maximum frame size 9216 bytes
Cable supported 10BaseT: unshielded twisted-pair (UTP)
(RJ-45) 100BaseTX: unshielded twisted-pair (UTP), Category 5, EIA/TIA 568
or shielded twisted-pair (STP), Category 5, 100 ohm
1000BaseT: unshielded twisted-pair (UTP), Category 5e
Maximum cable distance 100 meters
(RJ-45)
Remote Stacking Support Supports remote stacking
OmniSwitch 6450-48
Chassis Features
System status LEDs Internal AC Power Supply
(48) Non-combo 10/100/1000Base-T ports Console port (RJ-45)
(2) Non-combo SFP/SFP+ ports USB port (USB 2.0)
Expansion Module Stacking LED
Front Panel
A B C D
E F
G
Item Description
A Stacking LED
Displays the chassis stack ID.
B Console Port
RS-232 console port with an RJ-45 connector. Provides access to the CLI for configuration and
management.
C System Status LEDs
Provides status on hardware, software, and power.
D 10/100/1000BaseT RJ-45 Ports
10/100/1000BaseT non-combo ports. Odd-numbered ports are on top row, even-numbered ports
are on bottom row.
E Rear Status LEDs
Displays link status for expansion module ports.
F USB Port
High speed USB 2.0 port.
G SFP/SFP+ Ports
Two SFP/SFP+ ports to be used for uplinks.
Refer to “OmniSwitch 6450 LED Status” on page 3-33 for LED status information.
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.
A B C D
Item Description
A Grounding Block
Type LCD8-10A-L grounding lug
B Power Supply Connector
Internal AC power supply
C Internal Backup Power Supply Slot
D Expansion Module Slot
OS6450-48 Specifications
Total non-combo 10/100/ 48
1000BaseT ports per switch
Total non-combo SFP/SFP+ 2
ports per switch
Total expansion modules per 1
switch
Flash memory size 128 MB
RAM memory size 256 MB SDRAM
Chassis Width 17.32 inches (44.00 cm)
Chassis Height 1.73 inches (4.40 cm)
Chassis Depth 15.40 inches (39.10 cm)
Weight 12 lbs (5.44 kg)
Operating Humidity 5% to 95%
Storage Humidity 5% to 95%
Operating Temperature 0C to +45C (32F to 113F)
Storage Temperature -40C to +75C (-40F to +167F)
Data rate (RJ-45) 10/100/1000 Mbps
Default Upper Threshold 75C
Temperature
Danger Threshold Temperature 79C
Maximum frame size 9216 bytes
Cable supported 10BaseT: unshielded twisted-pair (UTP)
(RJ-45) 100BaseTX: unshielded twisted-pair (UTP), Category 5, EIA/TIA 568
or shielded twisted-pair (STP), Category 5, 100 ohm
1000BaseT: unshielded twisted-pair (UTP), Category 5e
Maximum cable distance 100 meters
(RJ-45)
Remote Stacking Support Supports remote stacking
OmniSwitch 6450-P48
Chassis Features
System status LEDs Backup Power Supply (BPS) Connector
(48) Non-combo 10/100/1000Base-T PoE ports Console port (RJ-45)
(2) Non-combo SFP/SFP+ ports USB port (USB 2.0)
Expansion Module Stacking LED
Internal AC Power Supply
Front Panel
A B C D
E F
G
Item Description
A Stacking LED
Displays the chassis stack ID.
B Console Port
RS-232 console port with an RJ-45 connector. Provides access to the CLI for configuration and
management.
C System Status LEDs
Provides status on hardware, software, and power.
D 10/100/1000BaseT RJ-45 PoE Ports
10/100/1000BaseT non-combo ports. Odd-numbered ports are on top row, even-numbered ports
are on bottom row.
E Rear Status LEDs
Displays link status for expansion module ports.
F USB Port
High speed USB 2.0 port.
G SFP/SFP+ Ports
Two SFP/SFP+ ports to be used for uplinks.
Refer to “OmniSwitch 6450 LED Status” on page 3-33 for LED status information.
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.
A B C D
Item Description
A Grounding Block
Type LCD8-10A-L grounding lug
B Power Supply Connector
Internal AC power supply.
C External Backup or PoE Power Supply Connector
OS6450-P48 Specifications
Total non-combo 10/100/ 48
1000BaseT 802.3at PoE ports
per switch
Total non-combo SFP/SFP+ 2
ports per switch
Total expansion modules per 1
switch
Flash memory size 128 MB
RAM memory size 256 MB SDRAM
Chassis Width 17.32 inches (44.00 cm)
Chassis Height 1.73 inches (4.40 cm)
Chassis Depth 15.40 inches (39.10 cm)
Weight 15 lbs (6.8 kg)
Operating Humidity 5% to 95%
Storage Humidity 5% to 95%
Operating Temperature 0C to +45C (32F to 113F)
Storage Temperature -40C to +75C (-40F to +167F)
Data rate (RJ-45) 10/100/1000 Mbps
Default Upper Threshold 67C
Temperature
Danger Threshold Temperature 73C
Maximum frame size 9216 bytes
Cable supported 10BaseT: unshielded twisted-pair (UTP)
(RJ-45) 100BaseTX: unshielded twisted-pair (UTP), Category 5, EIA/TIA 568
or shielded twisted-pair (STP), Category 5, 100 ohm
1000BaseT: unshielded twisted-pair (UTP), Category 5e
Maximum cable distance 100 meters
(RJ-45)
Remote Stacking Support Supports remote stacking
OmniSwitch 6450-U24
Chassis Features
System status LEDs Internal AC Power Supply
(22) Non-combo SFP ports Console port (RJ-45)
(2) Combo 10/100/1000BaseT or SFP USB port (USB 2.0)
(2) Non-combo SFP/SFP+ ports Stacking LED
Expansion Module
Front Panel
A B C D
E F
G
Item Description
A Stacking LED
Displays the chassis stack ID.
B Console Port
RS-232 console port with an RJ-45 connector. Provides access to the CLI for
configuration and management.
C System Status LEDs
Provides status on hardware, software, and power.
D 100/1000 Base-X SFP Ports
22 100/1000 Base-X SFP ports, 2 combo ports configurable to be
10/100/1000 BaseT or 100/1000 Base-X.
E Rear Status LEDs
Displays link status for expansion module ports.
F USB Port
High speed USB 2.0 port.
G SFP/SFP+ Ports
Two SFP/SFP+ ports to be used for uplinks.
Refer to “OmniSwitch 6450 LED Status” on page 3-33 for LED status information.
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.
A B C D
Item Description
A Grounding Block
Type LCD8-10A-L grounding lug
B Power Supply Connector
Internal AC power supply.
C Internal Backup Power Supply Slot
OS6450-U24 Specifications
Total non-combo SFP ports per 22
switch
Total RJ45/SFP combo ports per 2
switch
Total non-combo SFP/SFP+ 2
ports per switch
Total expansion modules per 1
switch
Flash memory size 128 MB
RAM memory size 256 MB SDRAM
Chassis Width 17.32 inches (44.00 cm)
Chassis Height 1.73 inches (4.40 cm)
Chassis Depth 12.30 inches (31.24 cm)
Weight 9 lbs (4.08 kg)
Operating Humidity 5% to 95%
Storage Humidity 5% to 95%
Operating Temperature 0C to +45C (32F to 113F)
Storage Temperature -40C to +75C (-40F to +167F)
Data rate (RJ-45) 10/100/1000 Mbps
Default Upper Threshold 54C
Temperature
Danger Threshold Temperature 61C
Maximum frame size 9216 bytes
Cable supported 10BaseT: unshielded twisted-pair (UTP)
(RJ-45) 100BaseTX: unshielded twisted-pair (UTP), Category 5, EIA/TIA 568
or shielded twisted-pair (STP), Category 5, 100 ohm
1000BaseT: unshielded twisted-pair (UTP), Category 5e
Maximum cable distance 100 meters
(RJ-45)
Remote Stacking Support Supports remote stacking
OmniSwitch 6450-U24S
The OmniSwitch 6450-U24S provides 22 SFP ports, two (2) RJ45/SFP combo ports, two (2) fixed SFP+
ports and a slot (located on the rear panel) for two (2) optional SFP+ stacking/expansion ports.
OmniSwitch 6450-U24S switches support IEEE 1588 Precision Time Protocol (PTP). (PTP is supported
on front panel ports only; PTP is not supported on rear panel expansion modules.)
Note. When PTP is disabled, the OmniSwitch 6450-U24S may be stacked with other stackable OS6450
models. When PTP is enabled, stacking is not supported and the switch operates as a standalone unit.
Front Panel
A B C D E F G
H I J K
Item Description
A Stacking LED
Displays the chassis stack ID.
B Back-lit Power Status LED
Illuminates model name on chassis front panel to indicate “power on” status.
C Console Port
RS-232 console port with an RJ-45 connector. Provides console access to the CLI for
configuration and management.
D System Status LEDs
Provides status on hardware and software.
E Port Status LEDs
Provides status on connectivity and link activity for the switch’s 22 SFP ports and two (2)
RJ45/SFP ports.
F RJ45/SFP Combo Ports
Port numbers 23 and 24.
G SFP+ Port LEDs
Displays link status for front panel fixed SFP+ ports.
H SFP+ Stacking/Expansion Module Port Status LEDs
Displays link status for rear panel SFP+ stacking/expansion ports.
I USB Port
High speed USB 2.0 port.
Item Description
J SFP Ports
22 SFP ports. Port numbers 1 through 22.
K Fixed SFP+ Ports
Port numbers 25 and 26.
Refer to “OmniSwitch 6450 LED Status” on page 3-33 for LED status information.
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.
A B C D
Item Description
A Grounding Block
Type LCD8-10A-L grounding lug
B Power Supply Connector
Internal AC power supply.
C External Backup Power Supply (BPS) Connector
Expansion Modules
OS6450-GNI-C2
The OS6450-GNI-C2 is an optional uplink module that supports two RJ45 Gigabit ports. The module
inserts into the expansion slot at the rear of 24- and 48-port OS6450 switches,
Item Description
A Captive Screws
B RJ45 Ports
OS6450-GNI-U2
The OS6450-GNI-U2 is an optional uplink module that supports two SFP Gigabit transceivers. The
module inserts into the expansion slot at the rear of 24- and 48-port OS6450 switches,
Item Description
A Captive Screws
B SFP ports
OS6450-XNI-U2
The OS6450-XNI-U2 is an optional 10 Gigabit stacking module that supports two SFP+ 10 Gigabit ports.
The module inserts into the expansion slot at the rear of 24- and 48-port OS6450 switches.
Item Description
A Captive Screws
B SFP+ 10 Gigabit ports.
Note: PS-90W-DC power supply has Input Marking as 36-75VDC. Please note that 36-75VDC is without
any tolerance. Please operate this power supply from the range of -48 to -60 VDC (nominal voltage).
2 Insert the module circuit board into the grooves at the left side of the expansion module slot. This
groove will ensure that the expansion module and backplane connectors are properly aligned.
3 Once the module circuit board is inserted in the grooves, slide the module back until the backplane
connectors are fully seated and the module front plate is flush with the front panel of the chassis.
Alignment groove
4 When the module is seated in the chassis slot, hand tighten the thumb screws at the left and right sides
of the module’s front plate.
5 Install transceivers and connect network cables as required. Refer to the OmniSwitch AOS Release 6
Transceivers Guide for additional information.
Note. If installing the OS6450-XNI-U2 stacking module, refer to the Chapter 6, “Managing OmniSwitch
6450 Stacks” for information on stacking cable requirements.
2 Loosen the thumb screws at the left and right sides of the module’s front plate.
3 When the thumb screws are loosened and the module front plate is free from the chassis, grasp the
thumbscrews and pull the module straight out of the chassis. Store the module in a static-free environment
(e.g., an anti-static bag).
4 If the expansion module is not being replaced with another module, be sure to install a blank plate over
the slot opening.
2 Slide the power supply back until it is securely seated in the chassis backplane.When the power supply
is fully seated, hand-tighten the thumb screws.
3 Plug the power cord (provided) into the power supply’s socket.
Completed Installation
2 Loosen the thumb screws at the left and right sides of the power supply face plate.
Note. If you are not replacing the power supply, be sure to install a blank cover panel over the empty
power supply bay.
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) insulated #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:
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 switch for the first time. By default, this RJ-45 connector provides a DTE
console connection.
Port Pinouts
RJ-45 Console Port – Connector Pinout
Pin Number Signals as DTE Console Port
1 NC
2 NC
3 RXD
4 Ground
5 Ground
6 TXD
7 NC
8 NC
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 AOS Release
6 Network Configuration Guide for information on configuring switch thresholds.)
If the temperature continues to rise and reaches the Danger Threshold, the following will occur:
• OK LED will display solid Amber.
• Once the temperature drops to an acceptable operating level, the switch will automatically restart.
Use the snmp station command and refer to the SNMP Configuration chapter for information on
configuring an SNMP station.
Dying Gasp
If the switch loses all power it will maintain power long enough to send a Dying Gasp message before
completely shutting down. An SNMP trap, Syslog message and Link OAM PDUs will be generated.
Scenarios
A Dying Gasp event will be generated in the following scenarios:
• Primary power supply failure (if only power supply present).
• Primary power supply failure and then backup power supply failure.
• Backup power supply failure and then primary power supply failure.
Note. Dying gasp will not work when both primary and backup power supplies fail simultaneously.
Connect each power supply to a separate independent power source to avoid simultaneous power failures.
SNMP Trap
As soon as the power failure is detected, an SNMP trap is sent to the first three configured SNMP stations.
The trap includes the following information:
• Slot number
Use the snmp station command and refer to the SNMP Configuration chapter for information on
configuring an SNMP station.
Syslog Message
As soon as the power failure is detected, the following Syslog message is sent to the first four configured
Syslog servers, along with the time of the failure:
Use the swlog output socket command to add a Syslog station. Refer to the Using Switch Logging
Configuration chapter in the OmniSwitch AOS Release 6 Network Configuration Guide for information on
configuring a Syslog server.
Use the efm-oam and efm-oam port propagate-events commands to enable the generation of an
802.3ah OAM Information PDU upon a dying gasp event:
1. Uplink ports
2. Combo ports
3. All other ports
This chapter covers different mounting and installation options. OmniSwitch 6450 switches may be either
table- or rack-mounted. 24- and 48-port OmniSwitch 6450 switches are rack mounted using factory-
installed rack mount flanges. 10-port (1/2 width) switches may be rack mounted using available rack
mounting kits. Refer to “Available 10-Port Rack-Mounting Kits” on page 4-6 for details.
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.
} 6 inches minimum at
rear of chassis.
2 inches minimum at
left and right sides.
} 6 inches minimum at
front of chassis.
} 6 inches minimum at
rear of chassis.
2 inches minimum at
left and right sides.
} 6 inches minimum at
front of chassis.
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.
Mechanical Loading
Mounting of the equipment in the rack should be such that a hazardous condition is not achieved due to
uneven mechanical loading.
Circuit Overloading
Consideration should be given to the connection of the equipment to the supply circuit and the effect that
overloading of the circuit might have on overcurrent protection and supply wiring. Appropriate
consideration of equipment nameplate ratings should be used when addressing this concern.
Reliable Earthing
Reliable earthing of rack-mount equipment should be maintained. Particular attention should be given to
supply connections other than direct connections to the branch circuit (e.g. use of power strips).
• 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.
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.
4 Caution should be taken for any cable connected to any outdoor device, not only on the device ground-
ing, 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.
Table-Mounting Installation
1 Locate the four indentations on the bottom of the chassis.
2 Using the adhesive on the rubber feet attach them to the indentations, pressing firmly to ensure they are
properly adhered.
Place the chassis on the table as desired.
Note. Some factory-installed screws may need to be removed prior to mounting, depending on the kit
being used.
Note. For information on rack mounting full width 24- and 48-port OS6450 switches, refer to
“Rack-Mounting 24 and 48-Port OS6450 Switches” on page 4-11.
• If you are installing the switch on a relay rack, be sure to install and secure the rack per the rack
manufacturer’s specifications.
Note. Some factory-installed screws may need to be removed prior to mounting, depending on the kit
being used.
2 Align the holes in the flanges with the rack holes and insert rack mount screws (not provided) through
the bottom hole of each flange and then the top of each flange. Tighten both screws until they are secure
When rack mounting, a clear-
ance of 0.875 inches is recom-
mended above the chassis.
Two chassis can be assembled side-by-side for mounting into a standard 19-inch rack as show in the figure
below.
Rear center brackets.
1 Attach the slot-brackets and slide-brackets to the front and back of the chassis using the attachment
screws (M3 flat head) provided for each bracket.
Attach Slot/Slide-Brackets
2 Align the chassis and slide both front and rear center brackets together.
3 Place bracket plate over front and rear brackets and secure with thumb screws.
4 Attach rack mount brackets to both sides of the front of the chassis.
5 Using one additional person, lift and position the assembly on the rack until the rack-mount flanges are
flush with the rack post.
6 Align the holes in the flanges with the rack holes and insert rack mount screws (not provided) through
the bottom hole of each flange and then the top of each flange. Tighten both screws until they are secure.
When rack mounting, a clearance of
0.875 inches is recommended above
the chassis.
Note. For information on rack mounting half width 10-port OS6450 switches, refer to “Rack-Mounting
10-Port OS6450 Switches” on page 4-6.
Refer to the important guidelines below before installing the OmniSwitch 6450 chassis on a rack.
Note. When rack mounting multiple switches in a stacked configuration, be sure to place all switches in
vertically-adjacent rack positions. This will ensure that all required stacking cables will have adequate
length for the installation.
• It is recommended that two people install the switch on the rack—one person to hold the chassis and
position it on the rack, and a second person to secure the chassis to the rack using attachment screws
(not supplied).
• Alcatel-Lucent provides two rack-mount flanges with each OmniSwitch 6450 switch. These flanges
support standard 19-inch rack-mount installations. These flanges must be attached to the chassis before
the switch can be rack mounted.
Note. If you are installing the switch in a 23-inch-wide rack, Alcatel-Lucent offers optional 23-inch rack-
mounting hardware. For more information, contact your Alcatel-Lucent representative.
• Alcatel-Lucent does not provide rack-mount screws. Use the screws supplied by the rack vendor.
• To prevent a rack from becoming top heavy, it is recommended that you install heavier equipment at
the bottom of the rack, whenever possible.
• If you are installing the switch on a relay rack, be sure to install and secure the rack per the rack manu-
facturer’s specifications.
• Review “Airflow Recommendations” on page 4-2 for important chassis airflow and access recommen-
dations before installing.
3 Lift and position the switch until the rack-mount brackets are flush with the rack post, then align the
holes in the brackets with the rack holes that were marked at step 1.
4 Once the holes are aligned, insert a rack mount screw (not provided) through the bottom hole of each
bracket. Tighten both screws until they are secure.
Note. Be sure to install the screws in the bottom hole of each bracket, as shown, before proceeding.
5 Once the screws at the bottom of each bracket are secure, install the remaining two rack mount screws.
Be sure that all screws are securely tightened.
These power supplies may be rack mounted above or below the chassis for a 2RU configuration. The
following sections describe how to rack-mount a power supply shelf and connect the power supply to the
chassis with a cable.
3 Carefully slide the power supply on to the power shelf and secure the power supply to the shelf using
the captive screws.
Captive Screws
4 After the rack-mount flanges and the power supply are secured to the shelf, mark the holes on the rack
where the shelf is to be installed.
5 Lift and position the shelf until the rack-mount flanges are flush with the rack post.
6 Align the holes in the flanges with the rack holes that were marked earlier.
7 Once the holes are aligned, insert a rack mount screw (not provided) through the bottom hole of each
flange. Tighten both screws until they are secure.
Note. Be sure to install the screws in the bottom hole of each flange, as shown, before proceeding.
8 Once the screws at the bottom of each flange are secure, install the remaining two rack mount screws.
Be sure that all screws are securely tightened.
1 Be sure the switch and power shelf are securely fastened to the rack.
2 Connect the proper end of the supplied power supply cable to the appropriately labeled connector at the
rear of the chassis and tighten securely.
3 Connect the other end of the power supply cable to the power supply and securely tighten.
Chassis Connector
• Use common DC return connections for the DC power supplies. The DC return terminal conductor
• A readily accessible disconnect device that is suitably approved and rated shall be incorporated in the
field wiring.
Powering On a Chassis
Follow the steps below to power on the chassis using and AC power source:
1 Connect the IEC-60320-C15 end of the supplied power cord to the chassis.
For information on booting stand-alone switches and switches in stacked configurations, refer to the
sections below.
Booting an OmniSwitch
The switch does not use an on/off switch. The power cord is the switch’s only connect/disconnect device.
The power connector socket is located on the power supply rear panel. For more information, refer to
“OmniSwitch 6450 Chassis and Hardware Components” on page 3-1.
To boot the switch, plug the power cord into an easily-accessible power source, such as a grounded AC
outlet or an Uninterruptible Power Supply (UPS).
The switch immediately begins the boot process. Allow a few moments for the switch to boot completely,
then verify the status of all LEDs on the switch’s front panel. A successful boot displays the following
LED states:
If any of the LED state differs from the states shown in the table above, refer to page 3-6 for more
information. Contact Alcatel-Lucent Customer Support if the LED state persists.
For information on logging in and configuring your switch, refer to the OmniSwitch 6450 Getting Started
Guide.
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 switch for the first time. By default, this RJ-45 connector provides a DTE
console connection.
Note. You must be connected to the switch via the console port before attempting to change serial
connection settings. Otherwise, an error message will display.
For switches in a stacked configuration, all changes must be configured before the switches are cabled
together. In other words, you must configure these settings when each switch is operating as a stand-alone
unit.
1 Enter the modify boot parameters command at the CLI prompt. The boot prompt displays:
Boot >
2 To change the baud rate, enter boot serialbaudrate, followed by the desired baud rate value. Options
include 1200, 2400, 4800, 9600 (default), 19200, 38400, 57600, 76800, and 115200. For example:
Boot > boot serialbaudrate 19200
Note. Setting the console port to speeds above 9600 baud can cause problems with Zmodem uploads.
3 To change the parity value, enter boot serialparity, followed by the desired parity value. Options
include none (default), even, and odd. For example:
Boot > boot serialparity even
4 To change the data bits (i.e., word size) value, enter boot serialwordsize, followed by the number of
data bits. Options include 7 and 8 (default). For example:
Boot > boot serialwordsize 7
5 To change the stop bits value, enter boot serialstopbits, followed by the number of stop bits. Options
include 1 (default) and 2. For example:
Boot > boot serialstopbits 2
7 You can save your changes to the boot.params file by entering commit file at the boot prompt:
When the commit file command is used, changes will not be enabled until after the next switch reboot.
8 You can also save your changes in real time to the switch’s running memory by entering commit
system at the boot prompt:
Boot > commit system
Caution. There are two important things to consider when using the commit system command to save
serial connection changes:
• Output to the terminal may become illegible due to incompatible serial connection settings between the
switch and the terminal emulation software.
• If you use the commit system command only, changes will not be saved to the switch’s boot.params
file and will be lost if the switch is rebooted. To save changes to the boot.params file, refer to step 7.
Chassis 1
Model Name: 6450 10 PORT COPPER GE,
Description: Virtual Chassis,
Part Number: 903005-90,
Hardware Revision: 03,
Serial Number: M338153P,
Manufacture Date: AUG 13 2011,
Admin Status: POWER ON,
Operational Status: UP,
Number Of Resets: 4
MAC Address: e8:e7:32:12:e6:6e,
For a complete list of output definitions for this command, refer to the OmniSwitch AOS Release 6 CLI
Reference Guide.
For a complete list of output definitions for this command, refer to the OmniSwitch AOS Release 6 CLI
Reference Guide.
For tables showing LED states operating normally, refer to “OmniSwitch 6450 LED Status” on page 3-33.
Power over Ethernet (PoE) is supported on OmniSwitch 6450 switches and provides inline power directly
from the switch’s Ethernet ports. Powered Devices (PDs) such as IP phones and wireless APs can be
powered directly from the switch’s RJ-45 ports.
As the feature reduces devices’ dependence on conventional power sources, PoE eliminates many
restrictions that traditional electrical considerations have imposed on networks.
In a PoE configuration, Power Source Equipment (PSE) detects the presence of a PD and provides an
electrical current that is conducted along the data cable. The PD operates using the power received via the
Ethernet data cable; no connection to an additional power source (e.g., an AC wall socket) is required.
Note on Terminology. There are several general terms used to describe this feature. The terms Power
over Ethernet (PoE), LAN Power, Power over LAN (PoL), Power on LAN (PoL), and Inline Power are
synonymous terms used to describe the powering of attached devices through Ethernet ports. This
documentation refers to the feature as Power over Ethernet (PoE) and related CLI commands use the
syntax, lanpower.
Additional terms, such as Powered Device (PD) and Power Source Equipment (PSE) are terms that are not
synonymous, but are directly related to PoE.
• PD refers to any attached device that uses a PoE data cable as its only source of power. Examples
include access points such as IP telephones, Ethernet hubs, wireless LAN stations, and so on.
• PSE refers to the actual hardware source of the electrical current for PoE.
As the OmniSwitch 6450 switches fully support Ethernet connectivity, you may also attach non-PD
equipment, such as computer workstations, printers, servers, etc. to PoE ports. See Chapter 3,
“OmniSwitch 6450 Chassis and Hardware Components,” for more information on the OmniSwitch 6450
chassis.
Important. Alcatel-Lucent recommends that PoE-enabled switches with attached IP telephones should
have operational power supply redundancy at all times for 911 emergency requirements. In addition, both
the switch and the power supply should be plugged into an Uninterruptible Power Source (UPS).
In This Chapter
This chapter provides specifications and descriptions of hardware and software used to provide PoE for
attached devices.
The chapter also provides information on configuring PoE settings on the switch through the Command
Line Interface (CLI). CLI commands are used in the configuration examples; for more details about the
syntax of commands, see the OmniSwitch AOS Release 6 CLI Reference Guide. Topics and configuration
procedures described in this chapter include:
• Power over Ethernet Specifications on page 6-3
Note. You can also monitor all chassis components and manage many chassis features, including Power
over Ethernet, with WebView, Alcatel-Lucent’s embedded web-based device management application.
WebView is an interactive and easy-to-use GUI that can be launched from the OmniVista or a web
browser. Please refer to WebView’s Online Documentation for more information.
* For OS6450-P10S switches, PoE support of up to ~75W per port is provided on ports 1 through 4.
These ports are labeled “HPoE” on the chassis front panel. HPoE at ~75W per port must be enabled via
the lanpower power command. PoE support of up to 30W per port is provided on PoE ports 5 through 8.
The maximum PoE power budget available for all ports is 280W.
For detailed information on the show power command output, refer to the OmniSwitch AOS Release 6 CLI
Reference Guide.
Note. PoE units support different wattage power supplies. If an unsupported power supply is used, a
console message and a trap are generated.
If power to a particular port has been disconnected via the lanpower stop command, you can reactivate
power to the port by specifying both the slot and port in the command line. For example:
-> lanpower start 1/1
Note. You cannot use the slot/port syntax to initially activate PoE on a port. This syntax is intended only
to reactivate power to those that have been disconnected via the lanpower stop command. To initially
activate PoE, you must use the lanpower start slot syntax only, as described above.
Disabling PoE
To disable PoE on a particular slot or port, use the lanpower stop command.
To disable PoE on a specific PoE-capable port, enter a slot/port number. For example:
-> lanpower stop 1/4
To disable PoE for all PoE-capable in a slot, enter the corresponding slot number only.
For example:
-> lanpower stop 1
reduces the power available on port 1 of the switch to 3000 milliwatts. This new value is now the
maximum amount of power the port can use to power any attached device (until the value is modified by
the user).
Important. Before changing the maximum slot-wide power allowance, you must disable PoE for the slot
via the lanpower stop command. Once the new value is assigned, re-enable PoE for the slot via the
lanpower start command.
To increase or decrease the total power available to a slot, use the lanpower maxpower command. Since
you are setting the power allowance for an individual slot, you must specify a slot number in the command
line. For example, the syntax
-> lanpower 1 maxpower 40
reduces the power allowance of slot 1 to 40 watts. This value is now the maximum amount of power the
slot can use to power all attached devices (until the value is modified by the user).
Note. Changing the maximum power available to a slot or port does not reserve or immediately allocate
that power. These settings are only used for configuring a maximum amount of power that may be used,
any unused power is still available and remains a part of the overall PoE budget.
changes the priority value of port 1 to the highest priority level of critical. Now that the default value has
been reconfigured, this port should be reserved for those PDs that are mission critical for network
operations.
Reminder. Priority disconnect applies only when there is inadequate power remaining in the power
budget for an incoming device.
For information on setting the priority disconnect status, refer to the section below. For information on
setting the port priority status (a separate function from priority disconnect), refer to “Setting Port Priority
Levels” on page 6-7.
Reminder. Priority disconnect examples are applicable only when there is inadequate power remaining to
power an incoming device.
When a PD is being connected to a port with the same priority level as all other in the slot, the physical
port number is used to determine whether the incoming PD will be granted or denied power.
Lower numbered receive higher priority than higher-numbered. In other words, a PD connected to Port 1
will have a higher power priority than a PD connected to Port 2; a PD connected to Port 23 will have a
higher power priority than a PD connected to Port 24.
In order to avoid a power budget deficit, another port in the slot is disconnected. In determining which
port to power off, the system software disconnects the port with the highest physical port number.
Reminder. Priority disconnect examples are applicable only when there is inadequate power remaining to
power an incoming device.
When a PD is being connected to a port with a higher priority level than all other in the slot, the incoming
PD will automatically be granted power over the other devices, regardless of its physical port number.
In order to avoid a power budget deficit, another port in the slot is disconnected. In determining which
port to power off, the system software first selects the port with the lowest configured priority level. For
example, if a critical priority device is being added to a slot in which five existing devices are attached to
high priority and one device is attached to a low priority port, the low priority port is automatically
disconnected, regardless of its physical port number.
If all existing devices are attached to with the same lower priority level, the system software disconnects
the port with both the lowest priority level and the highest physical port number. For example, if a critical
priority device is being added to a slot in which six existing devices are attached to high priority, the high
priority port with the highest physical port number is automatically disconnected.
Reminder. Priority disconnect examples are applicable only when there is inadequate power remaining to
power an incoming device.
When a PD is being connected to a port with a lower priority level than all other in the slot, the incoming
PD will be denied power, regardless of its physical port number. Devices connected to other higher-
priority will continue operating without interruption.
Reminder. Priority disconnect examples are applicable only when there is inadequate power remaining to
power an incoming device.
When priority disconnect is disabled, power will be denied to any incoming PD, regardless of its port
priority status (i.e., low, high, and critical) or physical port number (i.e., 1/1).
Aggregate slot and chassis management information is also displayed. This information includes:
• Maximum watts available to the corresponding slot
• Amount of power budget remaining that can be available for PoE modules
• Total amount of power remaining that can be available for additional switch functions
When entering the show lanpower command, you must include a valid slot number in the command line
syntax. For example:
Note. For detailed information on show lanpower command output, refer to the OmniSwitch AOS Release
6 CLI Reference Guide.
In addition to their working as individual stand-alone switches OmniSwitch 6450 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 6450 switches configured to operate as a single virtual
chassis. Topics described in the chapter include:
• OmniSwitch 6450 stack overview on page 7-2.
Note. You can also manage and monitor OmniSwitch 6450 stacks through WebView, Alcatel-Lucent’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.
Note. OS6450-10 switches can only be stacked with other OS6450-10 switches. Stacking OS6450-10
model with other OS6450 models is not supported.
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 “Synchroniz-
ing Switches in a Stack” on page 7-37 for more information), operating software and configuration param-
eters 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 6450 switch, the terms stack and virtual chassis
are interchangeable referring to OmniSwitch 6450 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 management module refer to those switches operating in a stack
either in the primary or secondary management roles. OmniSwitch 6450 switches operating in an idle role
are essentially acting as network interface modules and therefore may be referred to as Network Interfaces
(NIs).
Note. Because the 24-port and 48-port switches use auto-detection to determine which mode is needed,
the stack set slot mode command is not supported.
The switch must be rebooted for the new mode to take affect.
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 Switches in a Stack” on page 7-37
for more information.
Primary
1 A stack of four OmniSwitch 6450 switches is
Secondary operating normally. The stack consists of a pri-
Idle mary module, secondary module, and two ele-
ments operating in idle status. (The software
Idle on all elements in the stack is synchronized.)
Offline
! 2 The primary management module fails or is
taken offline (e.g., powered off or rebooted by
Secondary the user).
• Chassis uptime
Note. Information on secondary management module selection is provided on page 7-10. Information on
dynamic assignment of idle module roles is provided on page 7-12.
00:d0:95:b2:3c:8e
00:d0:95:b2:2a:ab
2 When the stack is booted, system software detects
the lowest MAC address. In this stacked configura-
00:d0:95:b2:1c:ff
tion, the lowest MAC address is 00:d0:95:b2:1c:ff.
00:d0:95:b2:5b:8d
3 The system software immediately assigns the cor-
responding switch the primary management role.
00:d0:95:b2:3c:8e
When the switch is assigned as primary, it is also
00:d0:95:b2:2a:ab dynamically assigned the lowest slot number in
Primary Module the stack—i.e., slot 1. This slot number informa-
tion is saved to the boot.slot.cfg file, located in
00:d0:95:b2:5b:8d
the switch’s /flash file directory.
Primary Management Module Selection Using the Lowest Chassis MAC Address
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-20.
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-13.
For more information on using saved slot information to determine the primary switch in a stack, refer to
the diagram below:
Saved Slot 6
1 Four OmniSwitch 6450 switches are stacked; all
Saved Slot 5
switches are connected via stacking cables. The user
Saved Slot 4 configures each switch to have a unique saved slot
Saved Slot 3 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.
Reload
2 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.
Assumes Slot 6
3 Instead of assigning the primary management
Assumes Slot 5 module based on the lowest MAC address, the
system software reads the slot information from
Assumes Slot 4
each switch’s boot.slot.cfg file during the boot
Assumes Slot 3 process. The switches in the stack come up
using their assigned slot numbers.
Slot 6
4 The switch with the lowest assigned slot number
Slot 5
automatically assumes the primary management role.
Slot 4 In this case, the switch assigned slot 3 has the lowest
Primary: Slot 3 slot number in the stack and becomes the primary
management module.
Primary Management Module Selection Using Saved Slot Information
Off
2 The user allows a minimum of 15 seconds to pass.
Off
Because no other switches have joined the stack, the
Off switch that was powered on considers itself a stand-
Primary alone. The switch assumes a primary role by default—
(Saved Slot 8) even if there is a high saved slot number in its
boot.slot.cfg file (e.g., 8).
Powered On
Powered On 3 The user now powers on the remaining switches in the stack
in short succession.
Powered On
Primary
(Saved Slot 8) 4 In this example, when the remaining switches come online,
each has a lower saved slot value than the switch powered on
Saved Slot 3
at step 1. However, the switch powered on at step 1—with its
Saved Slot 1 slot value of 8—retains its primary management role. The
joining switches are essentially ineligible for primary status
Saved Slot 2
because they are considered “late arrivals.”For the primary
Primary switch to forfeit its role to the switch with the lowest assigned slot
(Saved Slot 8)
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.
00:d0:95:b2:3c:8e
2 When the elements in the stack come
00:d0:95:b2:2a:ab
online, the switch with the lowest
00:d0:95:b2:1c:ff MAC address is given the primary
(Primary - Slot 1)
management role and is dynamically
00:d0:95:b2:5b:8d assigned slot number 1.
A B
Idle
3 By default, the switch connected to
Idle the primary’s stacking port A is
automatically assigned the second-
Primary ary management role. The second-
ary switch is dynamically assigned
Secondary - Slot 2
slot number 2.
Secondary Management Module Selection Using the Stacking Connection to the Primary Switch
Note. For information on dynamic slot numbering for idle elements within the stack, refer to “Idle Module
Role” on page 7-12 and “Slot Numbering” on page 7-20.
Saved Slot 1
1 Four OmniSwitch 6450 switches are stacked; all
Saved Slot 3
switches are connected via stacking cables. The user
Saved Slot 4
configures each switch to have a unique saved slot num-
ber, as shown. When the saved slot number is config-
Saved Slot 2 ured, the information is automatically written to the
boot.slot.cfg file located in the /flash directory of each
switch.
Reload
2 The user reloads all the elements in the stack either by
issuing the reload all command or by physically pow-
ering off and then powering on all switches.
Assumes Slot 1
Assumes Slot 3
3 The system software reads the slot information from
each switch’s boot.slot.cfg file during the boot pro-
Assumes Slot 4
cess. The switches in the stack come up using their
Assumes Slot 2 assigned slot numbers.
Primary - Slot 1 The switch with the lowest assigned slot number auto-
4 matically assumes the primary management role. The
Slot 3
switch with the second lowest assigned slot number
Slot 4
becomes the secondary management role, regardless of
Secondary - Slot 2 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.
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-13.
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
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.
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 mecha-
nism 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.
• 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 be 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 assign-
ments 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:
In this example, note that both slots 2 and 3 have a saved slot value of 2. If this stack is rebooted, a dupli-
cate slot error will occur and the switch with the lower MAC address will be given the secondary manage-
ment role. The slot with the higher MAC address will be forced into the pass-through mode.
To avoid a pass-through condition following 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:
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 numeri-
cal 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 6450 LED Status” on page 3-33.
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.
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:
• 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:
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:
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 is 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:
This disordered stack topology, with its three modules operating in pass-through mode, can be corrected
by entering the following commands:
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:
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 6450 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 6450 Chassis and Hardware Compo-
nents.”
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.
A B
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.
Redundant stacking cables provide a form of dual redundancy. As shown in the figure above, the redun-
dant 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
In this example, a redundant stacking cable connection is present between the top-most and bottom-most
switches in the stack.
Slot Numbering
For a stack of OmniSwitch 6450 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 stack, 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 6450 LED Status” on page 3-33 for more
information).
There are two ways stacking modules are assigned slot numbers:
• Dynamic slot number assignment by the system software
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.
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 second-
ary 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:
Slot 3 - Idle
Slot 4 - Idle
Slot 2 - Secondary
Slot 1 - Primary
This example, taken from page 7-21, shows a stack in which the primary and secondary switches are phys-
ically 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 second-
ary roles will be assigned to the top of the stack. This is accomplished by entering the following
commands:
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-13).
When the stack comes up following the reboot, the manually-configured slot numbers display as follows:
Slot 1 - Primary
Slot 2 - Secondary
Slot 3 - Idle
Slot 4 - Idle
The stack set slot command can also be used to manually correct duplicate saved slot assignments within
the stack topology. Refer to pages 7-13 through 7-15 for detailed information.
The commands shown above clear the saved slot information from all modules in an eight-module stacked
configuration and then reboot the stack. Because the system software no longer has preassigned slot infor-
mation to read during the boot process, the stack uses the dynamic slot number assignment method
described on page 7-21.
• 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 redun-
dancy, is maintained between all remaining modules. For more information on stacking cable connec-
tions, refer to page 7-17.
• 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 make sure that any modules being added to an existing stack have
been cleared of preassigned slot information. In other words, verify that there is no boot.slot.cfg file pres-
ent 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.
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 following 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-17.
5 Power on all incoming modules.
Note. No more than eight switches can operate in a single stacked configuration at any time.
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.
Note. A primary management module reload can also be scheduled for a later time or date. For informa-
tion on scheduling a primary module reload, as well as additional command details, refer to the OmniS-
witch AOS Release 6 CLI Reference Guide.
Primary - Slot 1
1 In this stack of four OmniSwitch 6450 switches, the slot
Secondary - Slot 2
1 switch is the primary management module. The slot 2
Idle - Slot 3 switch is the secondary. Slots 3 and 4 are operating in
Idle - Slot 4 idle roles.
-> reload primary 2 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.
Booting...
Primary - Slot 2
3 The secondary switch automatically takes over the pri-
mary role. The idle switch with the next-lowest slot num-
Secondary - Slot 3
ber—in this case, slot 3—automatically becomes the
Idle - Slot 4 secondary management module. The slot 4 switch
remains unaffected. In addition, Ethernet traffic on slots
2, 3, and 4 remains unaffected.
Idle - Slot 1
Primary - Slot 2
Secondary - Slot 3 4 When the rebooted switch comes back up, it assumes an
Idle - Slot 4
idle role within the stack.
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.
Primary - Slot 1
1 In this stack of two OmniSwitch 6450 switches, the slot
1 switch is the primary management module. The slot 2
Secondary - Slot 2
switch is the secondary.
Secondary - Slot 1 4 When the rebooted switch comes back up, it assumes the
secondary management role within the stack.
Primary - Slot 2
Note. A secondary management module reload can also be scheduled for a later time or date. For informa-
tion on scheduling a secondary module reload, as well as additional command details, refer to the OmniS-
witch AOS Release 6 CLI Reference Guide.
Primary - Slot 1
1 In this stack of four OmniSwitch 6450 switches, the slot
Secondary - Slot 2
1 switch is the primary management module. The slot 2
Idle - Slot 3 switch is the secondary. Slots 3 and 4 are operating in
Idle - Slot 4 idle roles.
-> reload secondary 2 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.
Primary - Slot 1
Booting... 3 The idle switch with the lowest slot number—in this
case, slot 3—automatically becomes the secondary
Secondary - Slot 3
management module. The slot 4 switch remains unaf-
Idle - Slot 4 fected. In addition, Ethernet traffic on slots 1, 3, and 4
remains unaffected.
Primary - Slot 1
Idle - Slot 2 4 When the rebooted switch comes back up, it assumes an
idle role within the stack.
Secondary - Slot 3
Idle - Slot 4
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.
Primary - Slot 1
1 In this stack of two OmniSwitch 6450 switches, the slot
1 switch is the primary management module. The slot 2
Secondary - Slot 2
switch is the secondary.
Primary - Slot 1 4 When the rebooted switch comes back up, it assumes the
secondary management role within the stack.
Secondary - Slot 2
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 switches in the
stack must be reloaded.
Note. For more information on reloading all the switches in a stack, refer to page 7-32. For more informa-
tion on idle status, refer to page 7-12.
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-13.
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 unex-
pected results following a full stack reboot.
The sections below offer simple guidelines for avoiding splitting the stack during the reload process.
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 “Synchro-
nizing Switches in a Stack” on page 7-37.
Primary - Slot 1
Secondary - Slot 2 1 In this stack of four OmniSwitch 6450 switches, the slot
1 switch is the primary management module. The slot 2
Idle - Slot 3
switch is the secondary. Slots 3 and 4 are operating in
Idle - Slot 4 idle roles.
Booting...
Primary - Slot 2
3 The secondary switch takes over the primary role. The idle
switch with the next-lowest slot number—in this case, slot
Secondary - Slot 3
3—automatically becomes the secondary management
Idle - Slot 4 module. The slot 4 switch remains unaffected. In addition,
Ethernet traffic on slots 2, 3, and 4 remains unaffected.
Idle - Slot 1
Primary - Slot 2
4 When the former primary switch comes back up, it
assumes an idle role within the stack.
Secondary - Slot 3
Idle - Slot 4
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.
Primary - Slot 1
1 In this stack of two OmniSwitch 6450 switches, the slot
1 switch is the primary management module. The slot 2
Secondary - Slot 2
switch is the secondary.
Secondary - Slot 1 4 When the former primary switch comes back up, it
assumes the secondary management role within the
Primary - Slot 2
stack.
Takeover Behavior In a Stack of Two
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 inter-
ruption and data flow across the stack is unaffected.
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 OmniS-
witch AOS Release 6 Switch Management Guide.
• Once the stack split condition has been determined, the sub-stack will put its front-panel ports into an
operationally down state preventing traffic forwarding and avoiding loops and possible traffic disrup-
tion. The SSP link will be shut down after the protection mode SSP PDU is sent to the helper and the
acknowledgment is received 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-18.
Basic Operation
When stack split detection is enabled, a proprietary protocol 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 milli-
seconds for 120 seconds. This helps to quickly identify a stack split.
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 belong-
ing to the SSP protection link aggregate.
• The stack element will store the protection state transition information 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.
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.
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 automati-
cally 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.
1 Normal Opera-
tion
Helper switch.
SSP PDUs sent over helper linkagg and relayed by helper switch.
2 Stack Split
Active-stack
Sub-stack
3 Recovery
Helper switch.
Note. For detailed information on these commands, including command syntax options and definitions,
refer to the OmniSwitch AOS Release 6 CLI Reference Guide.
CMM Commands
reload debug chassis auto-reboot show microcode
takeover show running-directory
install show reload
This appendix provides information on regulatory agency compliance and safety for
OmniSwitch 6450 switches.
Products are packaged using one or more of the following packaging materials:
CB FB
50
Treatment applied at end of life of the product in these countries shall comply with the applicable national
laws implementing directive 2002/96EC on waste electrical and electronic equipment (WEEE).
Standards Compliance
Safety Standards
• UL 60950-1, 2nd Edition
• CAN/CSA-C22.2 No. 60950-1-07, 2nd Edition
• EN 60950-1 with Amendment II
• IEC 60950-1 2nd Edition
• AS/NZS TS-001 and 60950, Australia
• UL-AR, Argentina
• TUV,UL-GS Mark, Germany
• NOM-019 SCFI, Mexico
• EN 60825-1 Laser
• EN 60825-2 Laser
• CDRH Laser
• CB Certification per IEC 60950-1, Second Edition
EMC Standards
• FCC Part 15 (CFR 47) Class A
• ICES-003 Class A
• EN 55022 Class A
• CISPR 22 Class A
• AS/NZS 3548 Class A
• VCCI Class A; A1 and A2
• EN 55024 (Immunity)
• EN 61000-3-2
• EN 61000-3-3
• EN 61000-4-2
• EN 61000-4-3
• EN 61000-4-4
• EN 61000-4-5
• EN 61000-4-6
• EN 61000-4-8
• EN 61000-4-11
Environmental Standards
• ETS 300 019 Storage Class 1.1
• ETS 300 019 Transportation Class 2.3
• ETS 300 019 Stationary Use Class 3.1
• Plug the equipment into a different outlet so that equipment and receiver are on different branch
circuits.
If necessary, the user should consult the dealer or an experienced radio/television technician for additional
suggestions.
JATE
This equipment meets the requirements of the Japan Approvals Institute of Telecommunications Equip-
ment (JATE).
VCCI
This is a Class A product based on the standard of the Voluntary Control Council for Interference by
Information Technology Equipment (VCCI). If this equipment is used in a domestic environment, radio
disturbance may arise. When such trouble occurs, the user may be required to take corrective actions.
Installation Warning
Only personnel knowledgeable in basic electrical and mechanical procedures should install or maintain
this equipment.
Français: Toute installation ou remplacement de l'appareil doit être réalisée par du personnel qualifié et
compétent.
Deutsch: Installationshinweise
Dieses Gerät soll nur von Personal installiert oder gewartet werden, welches in elektrischen und mecha-
nischen Grundlagen ausgebildet ist.
Español: Estos equipos deben ser instalados y atendidos exclusivamente por personal adecuadamente
formado y capacitado en técnicas eléctricas y mecánicas.
Advertencia de instalación
Solamente el personal bien informado en procedimientos eléctricos y mecánicos básicos debe instalar o
mantener este equipo.
Clase de seguridad
Cumple con 21CFR 1040.10 y 1040.11 ó sus equivalentes.