ALU Enterprise OmniSwitch6400 Boilerplate PDF

A
AL
LC
CA
Diivv..
AT
TE
EL
L--L
LU
UC
CE
EN
NT
TE
EnntteerrpprriisseeSSoolluuttiioonnssD
E
Etthheerrnneett &
& IIP
PN
Neettw
woorrkkiinngg P
Poorrttffoolliioo
Internetworking Solutions with

OmniSwitch 6400 Product Family
Boilerplate Document
Table of Contents
Disclaimer ______________________________________________________________________ 4
Trademark Text _________________________________________________________________ 4
Revision History _________________________________________________________________ 4
Alcatel-Lucent Company Background ________________________________________________ 5
About Boilerplate _________________________________________________________________ 6
Introducing OmniSwitch 6400 Series _________________________________________________ 7
Overview _____________________________________________________________________________ 7
Alcatel-Lucent OmniSwitch 6400 Family __________________________________________________ 8
Network Positioning and Applications ____________________________________________________ 9
Gigabit Ethernet migration for Mid Size Campus __________________________________________________ 9

Residential and Business Ethernet Access _________________________________________________________ 9
Branch Office Internetworking ________________________________________________________________ 10
Key Customer Benefits ________________________________________________________________ 11
Key Technical Advantages ____________________________________________________________________ 11

Key Business Advantages _____________________________________________________________________ 12
Key Financial Advantages ____________________________________________________________________ 17
OmniSwitch 6400 Series Hardware Details ___________________________________________ 18

Hardware Overview of various 6400 Series Models _________________________________________ 18
OmniSwitch 6400-24 _______________________________________________________________________ 21

OmniSwitch 6400-24 Specifications __________________________________________________________ 22
OmniSwitch 6400-P24 ______________________________________________________________________ 23
OmniSwitch 6400-P24 Specifications_________________________________________________________ 24
OmniSwitch 6400-P24H ____________________________________________________________________ 25
OmniSwitch 6400-P24H Specifications _______________________________________________________ 26
OmniSwitch 6400-U24______________________________________________________________________ 28
OmniSwitch 6400-U24 Specifications ________________________________________________________ 29
OmniSwitch 6400-U24D ____________________________________________________________________ 30
OmniSwitch 6400-U24D Specifications _______________________________________________________ 31
OmniSwitch 6400-48 _______________________________________________________________________ 32
OmniSwitch 6400-48 Specifications __________________________________________________________ 33
OmniSwitch 6400-P48 ______________________________________________________________________ 34
OmniSwitch 6400-P48 Specifications_________________________________________________________ 35
OmniSwitch 6400-P48H ____________________________________________________________________ 36
OmniSwitch 6400-P48H Specifications _______________________________________________________ 37
Status LEDs ______________________________________________________________________________ 38
Internal Architecture__________________________________________________________________ 39
The OmniSwitch 6400-24 Internal Architecture __________________________________________________ 39

The OmniSwitch 6400-P24 Internal Architecture _________________________________________________ 40
The OmniSwitch 6400-48 Internal Architecture __________________________________________________ 41
The OmniSwitch P48 Internal Architecture ______________________________________________________ 42
The OmniSwitch U24 & U24D Internal Architecture ______________________________________________ 43
The OmniSwitch 6400 Series Power Supply System ________________________________________ 44

OS6400 Series Boilerplate Doc. Rev. B / October 2008 Page 1
Alcatel.Lucent-ESD
Calabasas/CA./USA
Power Supply Shelf ________________________________________________________________________ 44

Power Supply Redundancy __________________________________________________________________ 44
Monitoring Chassis Power __________________________________________________________________ 44
Power Supply Specifications _________________________________________________________________ 44
Specifications ___________________________________________________________________________ 51
Redundant AC Circuit Recommendation ______________________________________________________ 51
Grounding the Chassis _____________________________________________________________________ 51
Temperature Management ______________________________________________________________________ 51
Managing OmniSwitch 6400 Series Stacks ________________________________________________ 52
OmniSwitch 6400 Series Stack Overview ________________________________________________________ 52

Roles within the Stack ______________________________________________________________________ 52
Primary and Secondary Management _________________________________________________________ 52
Primary Management Module Selection _______________________________________________________ 52
Using the Chassis MAC Address ____________________________________________________________ 53
Using Saved Slot Information _______________________________________________________________ 53
Using Switch Uptime _____________________________________________________________________ 53
Secondary Management Module Selection _____________________________________________________ 53
Using the Stacking Connection to the Primary Switch ____________________________________________ 53
Using Saved Slot Information _______________________________________________________________ 53
Idle Module Role __________________________________________________________________________ 54
Pass-Through Mode _______________________________________________________________________ 54
Stack Cabling _____________________________________________________________________________ 55
Redundant Stacking Cable Connection ________________________________________________________ 56
Slot Numbering ___________________________________________________________________________ 56
Dynamic Slot Number Assignment ___________________________________________________________ 56
Manual Slot Number Assignment ____________________________________________________________ 56
Hot-Swapping Modules in a Stack ____________________________________________________________ 57
Removing Switches from an Existing Stack ____________________________________________________ 57
Inserting Switches into an Existing Stack ______________________________________________________ 57
Merging Stacks ___________________________________________________________________________ 57
Reloading Switches ________________________________________________________________________ 58
Reloading the Primary Management Module ___________________________________________________ 58
Reloading the Secondary Management Module _________________________________________________ 58
Reloading Switches with Idle Roles __________________________________________________________ 58
Reloading Switches in Pass-Through Mode ____________________________________________________ 58
Reloading All Switches in a Stack ___________________________________________________________ 58
Software Synchronization During a Full Reload_________________________________________________ 58
Effects of Saved Slot Number Information on the Reload Process ___________________________________ 59
Avoiding Split Stacks ______________________________________________________________________ 59
Changing the Secondary Module to Primary ___________________________________________________ 60
Synchronizing Switches in a Stack ____________________________________________________________ 60
Automatic Synchronization during a Full Reload _______________________________________________ 60
Monitoring the Stack_______________________________________________________________________ 60
Visually Monitoring the Stack_______________________________________________________________ 60
Managing Power over Ethernet (PoE) ____________________________________________________ 61
Power over Ethernet Specifications _____________________________________________________________ 61

Power over Ethernet Defaults _______________________________________________________________ 62
Port Priority Levels ________________________________________________________________________ 62
Capacitor Detection Method_________________________________________________________________ 62
Understanding Priority Disconnect ___________________________________________________________ 62
Monitoring Power over Ethernet via CLI ______________________________________________________ 63
Availability Feature ___________________________________________________________________ 64
Software Rollback ___________________________________________________________________________ 64
Alcatel.Lucent-ESD
Calabasas/CA./USA
Backup Power Supplies _______________________________________________________________________ 64

Hot Swapping_______________________________________________________________________________ 64
Simplified Manageability ______________________________________________________________ 65
Alcatel-Lucent Access Guardian and OmniVista 2770 Quarantine Manager ___________________________ 65

WebView __________________________________________________________________________________ 66
CLI _______________________________________________________________________________________ 66
MTBF Calculation Standards and Requirements __________________________________________ 67

OmniSwitch 6400 Series Hardware & Software Features Overview Table ____________________ 74
OmniSwitch 6400 Series IEEE/IETF Standards _________________________________________ 123
IEEE _____________________________________________________________________________________ 123

IETF -- RFCs ______________________________________________________________________________ 124
Regulatory Compliance and Safety Information __________________________________________ 126
Declaration of Conformity: CE Mark __________________________________________________________ 126

Waste Electrical and Electronic Equipment (WEEE) Statement ________________________________________ 127
Standards Compliance ______________________________________________________________________ 127
Safety Agency Certifications________________________________________________________________ 127
EMC Standards __________________________________________________________________________ 127
FCC Class A, Part 15 _____________________________________________________________________ 127
Canada Class A Statement _________________________________________________________________ 129
JATE___________________________________________________________________________________ 129
CISPR22 Class A Warning _________________________________________________________________ 129
VCCI ___________________________________________________________________________________ 129
Class A Warning for Taiwan and Other Chinese Markets _______________________________________ 129
Translated Safety Warnings ___________________________________________________________ 130
Important Warnings ________________________________________________________________________ 130

Blank Panels Warning ____________________________________________________________________ 130
Electrical Storm Warning __________________________________________________________________ 130
Installation Warning ______________________________________________________________________ 130
Invisible Laser Radiation Warning __________________________________________________________ 130
Lithium Battery Warning __________________________________________________________________ 130
Operating Voltage Warning ________________________________________________________________ 130
Power Disconnection Warning ______________________________________________________________ 130
Proper Earthing Requirement Warning ______________________________________________________ 130
Read Important Safety Information Warning _________________________________________________ 131
Restricted Access Location Warning _________________________________________________________ 131
Wrist Strap Warning _____________________________________________________________________ 131
Appendix A: Pin-Outs __________________________________________________________ 132

10/100Mbps Ethernet Port RJ-45 Pinouts (Non-PoE) ___________________________________________ 132
Gigabit Ethernet Port RJ-45 Pinouts_________________________________________________________ 132
10/100/1000Mbps Power over Ethernet Port -RJ-45 Pinouts _____________________________________ 132
RJ-45 Console Port Connector Pinouts _____________________________________________________ 132
Console Port / Serial Connection Default Settings ______________________________________________ 133
Alcatel.Lucent-ESD
Calabasas/CA./USA
Disclaimer
The information contained in this document represents the features of the listed Alcatel-Lucent Products.
Alcatel-Lucent makes no claims regarding the accuracy of this published information and specifically disclaims all liability for
loss or damages of any kind resulting from discussions made or actions taken by any party based on this information.
Product information contained in this document is subject to change and frequent updates without prior notice.
Contact your local Alcatel-Lucent representative for the most current information.
Copyright 2008 Alcatel-Lucent Internetworking, Inc. All rights reserved. This document will not be reproduced in
whole or in part without the express written permission of Alcatel-Lucent Internetworking.
Trademark Text
To protect the Alcatel-Lucent trademark, the following legal text must be inserted in the body of all RFPs, RFIs, and
quotations. Alcatel-Lucent is a registered trademark of Alcatel-Lucent, a society anonym organized under the laws of
the Republic of France. The first use of Alcatel-Lucent in any documents must include a "" registered trademark symbol.
Revision History
Rev.
Preliminary
Production
Release
Date:
August 2008
October 2008
Revision Description
Draft A1
Revision B
Alcatel.Lucent-ESD
Calabasas/CA./USA
Alcatel-Lucent Company Background

About Alcatel-Lucent
Alcatel-Lucent (Paris:ALU.PA - News) (NYSE:ALU - News) provides solutions that enable service providers, enterprises
and governments worldwide, to deliver voice, data and video communication services to end-users. As a leader in fixed,
mobile and converged broadband networking, IP technologies, applications, and services, Alcatel-Lucent offers the endto-end solutions that enable compelling communications services for people at home, at work and on the move. With
operations in more than 130 countries, Alcatel-Lucent is a local partner with global reach. The company has the most
experienced global services team in the industry, and one of the largest research, technology and innovation organizations
in the telecommunications industry. Alcatel-Lucent achieved adjusted proforma revenues of Euro 18.3 billion in 2006 and
is incorporated in France, with executive offices located in Paris. [All figures exclude impact of activities transferred to
Thales]. For more information, visit Alcatel-Lucent on the Internet:
http://www.Alcatel-Lucent.com
Alcatel-Lucents vision is to enrich peoples lives by transforming the way the world communicates. Alcatel-Lucent
provides solutions that enable service providers, enterprises and governments worldwide, to deliver voice, data and video
communication services to end-users. As a leader in fixed, mobile and converged broadband access, carrier and enterprise
IP technologies, applications, and services, Alcatel-Lucent offers the end-to-end solutions that enable compelling
communications services for people at home, at work and on the move.
With 79,000 employees (after the completion of the Thales transaction) and operations in more than 130 countries,
Alcatel-Lucent is a local partner with global reach. The company has the most experienced global services team in the industry,
and one of the largest Innovation and Technology organizations focused on communications. Alcatel-Lucent achieved
combined sales of Euro 18.6 billion* in 2005, and is incorporated in France, with executive offices located in Paris.
Organization
With a strong focus on complete solutions maximizing value for customers, Alcatel-Lucent is organized around five
business groups and four geographic regions. The Wireless, Wire-line, Convergence groups, which make up the Carrier
Business Group, are dedicated to serving the needs of the world's service providers. The Enterprise Business Group
focuses on meeting the needs of business customers. The Services Business Group designs, deploys, manages and
maintains networks worldwide. The company's geographic regions are Europe and North, Europe and South, North
America, and Asia-Pacific.
Innovation & Technology
Alcatel-Lucent today is one of the largest innovation powerhouses in the communications industry, boasting 23,000
research and development experts worldwide, representing a combined R&D investment of Euro 2.7 billion* in 2005, and
a portfolio of over 25,000 active patents spanning virtually every technology area. At the core of this innovation is
Alcatel-Lucents research, which includes the world-renowned Bell Labs and Research & Innovation groups, providing
Alcatel-Lucent with an innovation engine of 1,500 researchers and scientists at the forefront of research into areas such as
multimedia and convergent services and applications, new service delivery architectures and platforms, wireless and
Wire-line, broadband access, packet and optical networking and transport, network security, enterprise networking and
communication services and fundamental research in areas such as nanotechnology, algorithmic, and computer sciences.
History
Formed from the merger of Alcatel and Lucent Technologies, Alcatel-Lucent combines two entities that share a common
lineage that can be traced back to 1986, when Alcatels parent company, CGE (la Compagnie Gnrale dElectricit),
acquired ITTs European telecom business. Nearly 60 years earlier, ITT had purchased most of AT&Ts manufacturing
operations outside the United States. AT&T was Lucents former parent company.
By creating Alcatel-Lucent we are bringing our common lineages back together and starting an exciting new chapter of
our history -- creating the worlds first truly global communications solutions provider, with the most complete end-to-end
portfolio of solutions and services in the industry.
About Alcatel-Lucent Enterprise Networking Solutions

Alcatel-Lucent delivers standards-based IP communications solutions to a global customer base of over 500,000 small,
medium and large enterprises, government agencies, healthcare facilities, and educational institutions. Alcatel-Lucent's
award-winning Omni family of IP Communications solutions consists of an extensive portfolio of network switching
infrastructure products and IP telephony products built to provide long-term value.
Alcatel.Lucent-ESD
Calabasas/CA./USA
About Boilerplate
This boilerplate provides the information for newly introduced OmniSwitch 6400 series product family. It covers
hardware details of different models 6400 series and provides brief summary of AOS software features supported
on OmniSwitch 6400 series product family. For the details of AOS software features supported on OmniSwitch
6400 series product family users needs to refer generic AOS software features Boilerplate. AOS software features
Boilerplate provides the details of different AOS software features supported on various OmniSwitch products like
6400, 6800, 6850, 9000 series.
It is highly recommended that this Boilerplate document be used along with other Related Documents to
collectively gather the most up-to-date information required for responding to customers RFPs & RFIs proposals.
This document will not contain detailed design/functional/configuration, and/or software/hardware architectural
specifications. It will only provide an overview of such aforementioned specifications.
Alcatel.Lucent-ESD
Calabasas/CA./USA
Introducing OmniSwitch 6400 Series

Overview
The Alcatel-Lucent OmniSwitch 6400 Stackable LAN Switch is a layer 2+ Gigabit Ethernet LAN switch addressing
the small and medium-sized business needs for converged voice, data and video networks as well as residential and
business Ethernet access service providers requirements. The OmniSwitch 6400 addresses the fixed managed LAN
switch segment and expands the current enterprise portfolio, fitting between the Alcatel-Lucent OmniStack 6200
Stackable LAN Switch (layer 2 Fast Ethernet LAN switch) and the Alcatel-Lucent OmniSwitch 6850 Stackable LAN
Switch (Advanced layer 3 Gigabit LAN switch with 10G interfaces) in terms of speed and software features.
Similar to the existing Alcatel OmniSwitch products, the OS6400 series uses the Alcatel Operating System (AOS), which
ensures an easy and economical way to upgrade or deploy a new Ethernet network. The flexible configuration options
offered by the OS6400 family make it suitable for a small/medium network in the edge or at the core. Also, the OS6400
protects customers investment with native support of IPv4 and IPv6 switching.
The switches in OS6400 family provide:
Advanced layer-2 (L2) features with basic layer-3 (L3) routing.
Mix any combination of standard copper, PoE and Small Form Factor Pluggable (SFP) fiber withing a single
stack.
The OS6400-U24 24-port fiber models support both 100/1000BaseX SFP for service providers requiring both
port speeds.
Enhanced network availability features: Redundant stacking links, Chassis Management Module (CMM)
failover, hot swappable primary/secondary power (PoE models) and secondary power (non-PoE models) and
image rollback to automatically re-load previous configurations and software versions.
Performance: Wire-rate switching and routing at gigabit speeds to support real-time voice, data and video
applications.
10G stacking capability for virtual chassis redundancy
Advanced services: Quality of service (QoS) and access control lists (ACLs) for traffic control.
Native IPv4 and IPv6 support at no additional cost.
Ease of Management: Full support of OmniVista 2500 & 2700, WebView and 5620 SAM management
applications.
Security: Flexible 802.1X authentication and full support for CrystalSec applications.
Metro access features including virtual local area network (VLAN) stacking, operations, administration and
maintenance (OAM) support, IPTV multicast VLANs and 5620 Service Aware Manager (SAM) support with
5620 SAM release 6.1.
Metro Ethernet Forum (MEF) 9 and 14 certified.
The target applications for these versatile OS6400 LAN switches are:
Branch office workgroup / LAN wiring closets deployments
Small Medium Business core configurations
Metro Ethernet access for residential / metro triple-play applications
Converged data / voice / video networks
Alcatel.Lucent-ESD
Calabasas/CA./USA
Alcatel-Lucent OmniSwitch 6400 Family

The Alcatel-Lucent OmniSwitch 6400 Stackable LAN switch family offers a variety of PoE, non-PoE Gigabit and fiber
models. All models in the Alcatel-Lucent OmniSwitch 6400 family are stackable, fixed configuration chassis in a 1U form
factor. They can be optionally equipped with Alcatel-Lucent approved pluggable SFP transceivers supporting short, long
and very long distances. The following chart indicates the differences in the OS6400 models.
Fixed-Chassis
Types
POE
Ports
Non-POE
Ports
10 Gig.
Stacking
Ports
OS6400-24
N/A
24
OS6400-48
N/A
48
OS6400-U24
N/A
24
OS6400-U24D
N/A
24
OS6400-P24
20
N/A
OS6400-P24H
20
OS6400-P48
OS6400-P24H
10/100/1000Mbps
,GigE, or
10/100Mbps
Non-PoE Models
20 10/100/1000
Combo
Ports*
POE Power
Budget
Power Supplies
supported
N/A
44 10/100/1000
N/A
N/A
N/A
Powered by 126W
DC (internal)
22 GigE SFP or
100-Base-X
SFP**
22 GigE SFP or
100-Base-X
SFP**
PoE Models
20 10/100/1000
Powered by 126W
AC (internal)
Powered by 126W
AC (internal)
Powered by 126W
AC (internal)
N/A
360W AC
N/A
20 10/100/1000
N/A
510W AC
44
N/A
44 10/100/1000
N/A
360W AC
44
N/A
44 10/100/1000
N/A
510W AC
*Combo ports are ports individually configurable to be 10/100/1000BaseT or 1000BaseX that can support SFP
transceivers for short, long and very long distances.
** Gig fiber interfaces support Gig SFP or 100BaseX SFP optical transceivers.
Alcatel.Lucent-ESD
Calabasas/CA./USA
Network Positioning and Applications

Gigabit Ethernet migration for Mid Size Campus
The OmniSwitch 6400 series of switches provide a migration path to Gigabit on the LAN edge where high speed and
extensive features are needed. The OmniSwitch 6400s have the features necessary to provide intelligent, secure, and
available networking for the most demanding applications and user requirements. The OmniSwitch 6400s are ideal for use
at the edge because of their compact fixed form factor design suitable for closets. Their modular expandability, flexible
configuration provides an easy path to scale any workgroup up to 384 10/100/1000 ports in a single stack to support
campus wiring closet requirements. The OmniSwitch 6400s support of high power as well as standard powered PoE
ports, copper non-PoE and fiber ports in any combination in a stack provides exceptional flexibility in customizing the
closet/small core deployment to support applications ranging from just data to triple-play converged applications.
Residential and Business Ethernet Access

The OmniSwitch 6400 is ideal for triple play Ethernet access deployments installed as customer premise equipment (CPE)
or single/multiple tenant unit (STU/MTU) equipment. The AOS software offers service providers the features to fulfill the
demand for user-differentiated high-speed Internet, voice and video services, as well as, resiliency, performance, secure
access and traffic control. In addition, the OmniSwitch 6400 family is (MEF) 9 and 14 certified meaning they meet MEF
standards for end to end Ethernet access for residential and business deployments.
Alcatel.Lucent-ESD
Calabasas/CA./USA
Branch Office Internetworking

The OmniSwitch 6400 placed in the distribution layer of three-tier networks provides high capacity, wire speed layer-2
and basic layer-3 switching and intelligent services near the edge of the network. In addition, the copper models of the
OmniSwitch 6400 family have four combo ports that are individually configurable to provide users the choice of copper or
fiber connectivity to the data center.
Alcatel.Lucent-ESD
Calabasas/CA./USA
Key Customer Benefits

The new OS6400 switch family addresses the needs of network administrators: flexible, stackable configuration; power over
Ethernet, high availability, first-packet wire-speed performance, and dramatically improved network response time. Similar to
the other Alcatel-Lucent OmniSwitch, the OS6400 series uses the Alcatel-Lucent Operating System (AOS). This ensures an
easy and economical way to upgrade or deploy a new Ethernet network. The flexible configuration options offered by the
OS6400 family make the OS6400s suitable for a small/medium network in the core or at the edge. The OS6400 also future
proofs the network with support of IPv4 and IPv6.
The OmniSwitch 6400 series protects customers' long-term capital interests by including QoS features, advanced security
features, network management, and lifetime warranties.
OS6400 price/performance leadership means that Alcatel-Lucent consistently delivers the performance and functionality
that enterprise companies require today and in the future.
Key Technical Advantages

Customer Issue or Need
Wide variety of features /
Ports at an economical price
High performance, affordable, future proof

networks for triple-play applications
Enhanced security that is adaptive to user

mobility, is proactive and reactive at the edge,
core, and throughout the network
Simplified manageability
How we address the issue

The Omni product families offer many port /
feature option combinations that can fulfill the
majority of fixed config switch requirements.
Options include:
AC and/or DC powered switches
- 24 & 48 ports
Power-over-Ethernet
- 24 or 48 port stackable standard and high P/S
The Omni product families provide industry
leading price/feature performance with wirespeed packet classification and processing of all
packets in a data stream, including the first
packet. Supports advanced services such as PoE,
and IPv6.
The Omni product families provide extensive
security through:
Network access control by flexible and
powerful authentication mechanisms
- 802.1x, MAC-based authentication,
authenticated VLANs, PKI
Best in class VLAN classification capabilities:
MAC, IP subnet, protocol, DHCP based.
Access Control Lists (ACL)
Automatic containment and remediation
support provided by full integration with
Alcatel-Lucent OmniVista 2770 Quarantine
manager.
The Omni product families use the same
Alcatel-Lucent Operating System as the other
OmniSwitch products, reducing or eliminating
the need to train existing users. The Omni
product families models are fully manageable
by Alcatel-Lucent Network Manager
OmniVista.
Managing Alcatels entire suite of solutions and
equipment is OmniVista.
OmniVista eases the management burden in
many ways:
First, by centralizing the management activities
of device discovery, topology / health maps,
traps and health statistics, the LAN manager can
quickly ascertain the networks condition at a
glance.
Next, through streamlining bulk operations,
Benefits of our approach

The number of models offered meets any customer
configuration need.
The flexibility provides a lower price by eliminating
the functionality they dont need.
There is a noticeable performance boost in triple-play

networks from advanced services and at a great price
allowing customers to buy tomorrows capabilities
today.
Security domain VLAN classification helps to contain
viruses and network attacks maintaining network
uptime for critical operations.
Security domains provide safe network connectivity
for infected devices to be re-mediated. Reduces IT
support requirements and man-hours by using network
intelligence that automates otherwise manual
intervention.
By offering the same operating system, existing users

are familiar with the product from the first day,
reducing the cost of ownership by eliminating the need
for training.
Alcatel.Lucent-ESD
Calabasas/CA./USA
Always available, reliable critical network

applications
IPv6 support, a requirement of various corporate

and governments
Evolution / Migration
Interoperability
the IT staff has a mechanism to push

configurations, QoS, security, VLAN
memberships, and image files to the devices in
the network or to schedule after hours back up
of the configurations and image files.
Finally, OmniVista utilizes self-contained
applications - like the Automated Quarantine
Manager - to deliver value added services like
malicious behavior containment, or the
OneTouch QoS to deliver end-to-end QoS
policy enforcement.
From this single application, the IT staff can
access secure telnet and https GUI sessions with
the Alcatel devices, and discover 3rd party
equipment through their MIB identity.
OmniVista is the platform, which provides the
enterprise with the ease of management
necessary to grow securely.
The Omni product families provide a superior
By providing true redundancy, an enterprise can
architecture with no single point of failure in its
provide a reliable network for triple play applications.
stacked configuration. They offer:
Redundancy
- Replaceable and redundant power supplies
Virtual chassis
- Fault tolerant loop stacking
- Automatic election of primary and secondary
manager
- Single IP address for management
- Image roll back to automatically reload
previous configurations
Resiliency
- Network uptime is maximized by the wide
support of open advanced routing redundancy
protocols and mechanisms for fast
reconfiguration of links between switches,
servers, and other network devices.
The Omni product families family provide:
Extend the IP support from v4 to v4/v6 without
IPv6 support with hardware-based forwarding
compromising performance.
for wire-speed classification and tunneling.
Flexibility choice of deploying IPv4, IPv6, or
IPv4/IPv6 without compromising switch
performance.
Hardware-based classification (access control
lists (ACLs) and quality of service (QoS)),
forwarding and management for IPv6.
A transition from an existing IPv4 network by
support of tunneling
Alcatel-Lucent is strongly and fully committed to evolve its full array of comprehensive products and
solutions to meet the emerging requirements for the next generation technological advancements. To
remain highly competitive in the market place, the Omni family of innovative Products & Solutions
Technology will continue to evolve and develop to incorporate the most advanced feature set that meets the
new emerging networking requirements.
As a matter of fact, to remain highly competitive in the market place, the Omni family of innovative
Products & Solutions & Technologies has continued to evolve and develop to incorporate the most
advanced feature set that meets the new emerging networking requirements in the enterprise LAN, MAN
edge/access and WAN access. We can definitely today, compete very well with Cisco, Nortel and other
vendors as applicable in this space.
The new resilient, continuous switching, and standards-based architecture design of the Omni family of
innovative Products & Solutions is highly interoperable not only within the existing Alcatel-Lucents
family of enterprise network switching and routing products, but also within other vendors similar
enterprise-networking switching and routing products in the market place.
Key Business Advantages

The business Philosophy & Mission Statement
The Alcatel-Lucent Vision, Mission and Values form the cornerstones of our new company.
The statements set the tone for the way the new company will operate.
Alcatel.Lucent-ESD
Calabasas/CA./USA
Alcatel-Lucent pursues business on a global

scale and has significant business relationships
with all US major landline and wireless telecom
carriers and many Enterprise customers.
Value add with emphasis on the Wireless LAN

& Wired LAN solutions
Vendors Proven Track Record
Our Vision - Definition of future success

To enrich peoples lives by transforming the way the world communicates.
Our Mission - Purpose and path to realize the vision
To use our unique capabilities to ensure that our customers thrive, our business grows and we enrich the
personal communications experience for people around the world.
Our Values - A system of shared beliefs that are at the heart of everything we do.
Customers First: We exist to serve our customers. Our success will be determined by how well we perform
for our customers.
Innovation: We are intuitive, curious, inventive, practical and bold, which allows us to create new ideas for
our customers, our business and employees. These ideas come from anywhere throughout our global
operations.
Teamwork: Success requires teamwork. We are collaborative and respect the contributions of each person
to the teams success.
Respect: We are a global company with many cultures. We respect and embrace people and perspectives
from all over the world.
Accountability: We do what we say we will do. We own a collective responsibility towards customers,
colleagues, communities and shareholders.
Our Value proposition:
We believe that we must provide our customers with the industrys best value in highly available, secure
and easy to manage network solutions.
We recognize that the value of a network is greater to the enterprise when measured by its ability to be
reliable, secure and easily managed. Providing the strong foundation that is necessary for any business to
grow and prosper.
To optimize switch management and network security, we have developed the Alcatel-Lucents Operating
System - an O/S - common to our switches across the enterprise LAN infrastructure.
This common O/S enables operation expense relief to our customers through the homogeneity of features
and configurations, while supporting device and network based availability strategies.
Our enterprise LAN product families that leverages a 10-year history of embedded security features,
enabling synergies with existing 3rd party solutions Security solutions that provide assurance the
network will be able to react to and contain attacks - promoting productivity and reliability.
Alcatel-Lucent offers a comprehensive, system wide solution set allowing us to provide not only a
World-class WLAN solution but also the wired network upon which it runs applications to enhance the
WLANs ability to have a positive impact on our customers business. In addition to the WLAN we can
provide voice services for wired sets, VoIP set and VoWLAN into a seamless enterprise wide
communication system. Alcatel-Lucent can provide best in class wired transport for the wireless network
with a greater value than our main competition, integrated WAN solutions and across the board security;
all of this from one company. In addition we are leveraging our collaboration software to integrate into the
WLAN to take the concept of presence to a whole new level. Alcatel-Lucent can take all aspects of a
customers communication and security needs and provide a single, open solution set to our customers.
We can also leverage our professional services and provide these solutions turn-key to our customers.
Alcatel-Lucent (Paris:ALU.PA - News) (NYSE:ALU - News) provides solutions that enable service
providers, enterprises and governments worldwide, to deliver voice, data and video communication
services to end-users. As a leader in fixed, mobile and converged broadband networking, IP technologies,
applications, and services, Alcatel-Lucent offers the end-to-end solutions that enable compelling
communications services for people at home, at work and on the move. With operations in more than 130
countries, Alcatel-Lucent is a local partner with global reach. The company has the most experienced
global services team in the industry, and one of the largest research, technology and innovation
organizations in the telecommunications industry.
Alcatel-Lucent is a leading provider of communication solutions for small, medium, and large enterprise
networks worldwide. Alcatel-Lucent offers the industrys best value in IP networking solutions that are
highly available, secure and easy to manage. Designed for convergence, these solutions are comprised of
high-capacity switching platforms that are used in core, wiring closet, and edge implementations and can
include an advanced wireless LAN solution. Built from the ground up for IP communications and
convergence, they all feature an unparalleled manageability due to a common operating system AlcatelLucent Operating System, a superior availability for both chassis based and stackable solutions, and a best
of breed, built-in security.
Alcatel.Lucent-ESD
Calabasas/CA./USA
Extensive Experience
Innovation & Technology & Engineering
Strong IP Infrastructure Solution Offerings
With 23,000 technology patents and a history of more than 100 years in the communications field, AlcatelLucent has proven experience. Alcatel-Lucent serves more than 500,000 customers, including many of the
Fortune 500 and leading companies in most sectors.
Alcatel-Lucents century of innovation and engineering has allowed us to provide the enterprise network
with solutions that span the entire IP communications house. This house has at its top story the productivity
enhancing applications, which run on Alcatel-Lucents award winning IP telephony communication
servers. Supporting these products is the IP networking data products - the foundation of the IP
communications house. As you well know, any house is only as strong as its foundation. We understand
that an enterprise network must be able to rely on its infrastructure to deliver the communications and
applications necessary to conduct business and take care of users. The first requirement is availability- we
expect the phone and applications that expand the value of voice communications or integrate voice and
data communications to be available.
Our experience tells us that these networks must also be secure, and easily managed, otherwise valuable
capital is diverted from the business goals of the company, lessening the opportunity to react to market
changes and opportunities.
Alcatel-Lucent also knows that the value to the enterprise can be measured in multiple ways - from the
solutions purchased to the solutions enabled via partnerships and adherence to industry standards.
As you learn more about us and our business philosophy, you will come to know that our greatest benefit
to you and your company is not just the industry leading solutions we provide, but the synergies we create
with the other products and solutions already deployed in your network.
You see, we believe a strong foundation is not just to support the existing building, but to also support
future growth.
High Availability
Your business users demand much, but assume one thing above all: availability. Using a strong hardwaresoftware mix, Alcatel-Lucent IP infrastructure solutions create a single-entity network that is resistant to
configuration errors and doesn't need resetting after changes. Together with highly affordable, redundant
network management and continuous switching capabilities, Alcatel-Lucents IP infrastructure solutions
ensure fail-safe and cost effective business operations.
High Security
With Alcatel-Lucent IP infrastructure solutions, your information assets are really protected, from the core
to the edge. The same security features are embedded in all Alcatel-Lucent IP infrastructure components:
you dont need to go through a programming nightmare when deploying your network security policy or
adding a new switch to the system. Security problems can be isolated and contained; specific security tasks
can be addressed. In a nutshell, with an Alcatel-Lucent IP infrastructure, gaps in the communication
protection system are eliminated, including at the PBX level.
Simplified Management
Alcatel-Lucent IP infrastructure solutions leverage common components and feature sets, running on a
single operating system for centralized management. This simplifies both deployment and day-to-day
operations, while minimizing down time. As a result, total network running costs decrease, and you can
easily anticipate or react to evolving business needs. Last but not least, your IT people will appreciate the
one-touch graphical approach of fully featured yet easy-to-use network management applications, helping
them work more easily and quickly.
Managing Alcatel-Lucents entire suite of solutions and equipment is OmniVista.
OmniVista eases the management burden in many ways:
First, by centralizing the management activities of device discovery, topology / health maps, traps and
health statistics, the LAN manager can quickly ascertain the networks condition at a glance.
Next, through streamlining bulk operations, the IT staff has a mechanism to push configurations, QoS,
security, VLAN memberships, and image files to the devices in the network or to schedule after hours back
up of the configurations and image files.
Finally, OmniVista utilizes self-contained applications - like the Automated Quarantine Manager - to
deliver value added services like malicious behavior containment, or the OneTouch QoS to deliver end-toend QoS policy enforcement.
From this single application, the IT staff can access secure telnet and https GUI sessions with the AlcatelLucent devices, and discover 3rd party equipment through their MIB identity.
OmniVista is the platform, which provides the enterprise with the ease of management necessary to grow
securely.
Alcatel.Lucent-ESD
Calabasas/CA./USA
Product Portfolio
Service & Support, Integration & Installation
Escalation
Key Partners
The Alcatel-Lucent Internetworking product portfolio consists of a full range of Ethernet based switches
that address the Enterprises entire networking needs.
The family of Alcatel-Lucent Ethernet switches range from entry-level L2+ switches where price is the
main concern all the way up to advanced L3 modular or fixed configuration chassis providing state-of-theart and standard-based features that meet the stringent requirements for an highly available, highly secure
and highly manageable networking infrastructure.
The LAN switches, which support your business communications, come in two sets - entry level, fixed
configuration and AOS advanced featured core to wiring closet.
The entry level, fixed configuration solutions are provided for those customers who do not need to provide
the advance services and security features our AOS switches provide. Typically small businesses, these
solutions do provide great price/performance value for 10/100 and 10/100/1000.
Our AOS advanced services switches deliver on our promise to deliver the industrys best value. Our core
offerings of the OmniSwitch 6800, 6850, 7000 and 9000 family provide features which are important to the
enterprise core - native server load balancing, link aggregation, high density gigabit and 10 gigabit, as well
as support for routing protocols and multicast, classic IP addressing as well as IPv6, hot swappable
modules and full management and power supply redundancy to promote high availability. Our advanced
stackable line runs the same OS, and can be managed just like a chassis - one IP address, with management
module redundancy for high availability. Supporting PoE, standard routing protocols and multicast, classic
and IPv6 addressing as well as a host of other features, our AOS switch line is the easiest to manage in the
industry, with a price to performance relationship unmatched in the industry.
Expanding the IP communications foundation, Alcatel-Lucents OmniAccess WLAN family provides the
enterprise with the industrys most complete WLAN security, availability, and mobility solutions.
Further, the OmniAccess Service Gateways products perform at wire speed even with small packet sizes or
network services enabled and include a wide array of WAN integrated capabilities - eliminating the need to
purchase extra equipment to support additional WAN services.
Alcatel-Lucents enterprise SNMP manager, OmniVista, can manage the entire portfolio.
Alcatel-Lucent is fully committed to providing a comprehensive range of services and programs in support
of its vast array of products.
Alcatel-Lucents ecosystem of more than 1,500 partners helps ensure that solutions will be installed,
integrated, fully supported and maintained according to Alcatel-Lucents high standards, following global
best practices. Alcatel-Lucents Accreditation Program ensures that its partners are fully trained on the
latest technologies and techniques to meet and support customer requirements.
Technical Support
An Alcatel service agreement brings your company the assurance of 7x24 no-excuses technical support.
Youll also receive regular software updates to maintain and maximize your Alcatel products 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 Alcatels Service and Support web page,
youll be able to view and update any case (open or closed) that you have reported to Alcatels technical
support, open a new case or access helpful release notes, technical bulletins, and manuals.
SUPPORTbasic
7 X 24 Technical Response Center (7x24 phone support)
Includes e-service web access, software releases and repair and return of hardware to be completed in 10
business days from receipt for same version only. Excludes NMS & Authentication Services software.
SUPPORTplus
hardware support
Includes 7X24 phone support, software releases for same version only, e-service web access, advance
shipment for next business day arrival of replacement hardware. Excludes NMS & Authentication Services
software.
SUPPORTtotal
hardware support
Includes 7X24 phone support, software releases for same version only, e-service web access, same day
4-hour hardware replacement (labor & parts) 7 days a week 24 hours a day. Allow 30 days lead time from
receipt of sales order. Excludes NMS & Authentication Services software.
Upon opening a case, customers will receive a case number and may review, update, or escalate support
cases on-line. Escalation process is based on the severity level of the issue per the definitions below.
Severity 1: Production network is down resulting in critical impact on businessno workaround
Severity 2: Segment or Ring is down or intermittent loss of connectivity across network.
Severity 3: Network performances are slow or impairedno loss of connectivity or data.
Severity 4: Information or assistance on product feature, functionality, configuration, or installation.
Alcatel-Lucent has created a partnering program that enables it to work with a set of vendors in order to
provide solutions that fall outside of its core competencies. Partnerships provide channels and customers a
catalog of product solutions that are easy to find, evaluate, buy, install, and operate.
Alcatel.Lucent-ESD
Calabasas/CA./USA
Customer support / Professional Services
Customer Training
Warranty
Service & Support Programs & End Of Life
Lifetime Support
Hardware Warranty
Software Warranty
Life Span
Customers can access customer support 24 x 7 x 365 via toll free number or Internet.
Professional services can be contracted to perform a variety of functions, including customer network
operations center management, network audits, security installation, network design, equipment staging,
configuration and installation, resident engineering, proof of concept, solutions development and
integration. Customers may take advantage of professional services with regard to customizing the network
management system for optimal tuning in a multi-vendor environment. Professional Services also offers
Customer Network Operations Center Service, which proactively monitors the customer network and
responds to alarms and traps.
Alcatel-Lucent offers instruction on its enterprise data products in a variety of modes instructor-led
training (ILT), computer-based training (CBT), web-based training (WBT), and customized
seminars/workshops/webinars. ILT is offered at several locations or on-site at customer locations. All
instructors are Alcatel-Lucent Certified Switch Instructors (ACSIs).
This means they have attended all of the courses, completed all of the certifications and attended the
weeklong Train-the-Trainer program that includes a review of Alcatel-Lucent training policies, procedures,
and practices to assure consistent delivery of information around the world.
Standard Warranty Support
All Alcatel-Lucent's products come with a standard one-year warranty on hardware and a three-month
warranty on software.
Hardware DOA Warranty
If hardware fails within the first 30 days after delivery, call Alcatel-Lucent's Internetworking Division
Customer Service by 2:00 p.m. (Pacific Standard Time) and they will send a replacement part overnight.
One-year Hardware Warranty
After the first 30 days, call Alcatel-Lucent's Internetworking Division Customer Service for a Return
material Authorization (RMA) and ship the part back to them for factory repair. The repaired unit will be
shipped back to you from our facility within 10 business days. Next day, advanced replacement is available
for a small expedited fee.
All-in-One Maintenance: All maintenance fix releases will be provided free of charge during the first 90
days.
Service & Support Programs & End Of Life (EOL)
In accordance with Alcatel-Lucents established Product Life Cycle policy, as well as its customer
satisfaction policy, Alcatel-Lucent will honor its obligations to customers currently under warranty or with
valid purchased service agreements relating to a product line for five (5) years (Software: three (3) years
and Hardware: five (5) years) beyond the EOL (End Of Life) of a product line.
Lifetime Support
All versions of the stackable product families come with a Limited Lifetime Hardware Warranty, limited to
the original owner, and will be provided for up to five (5) years. Faulty parts will be replaced via a five (5)
business days AVR (Advance Replacement) RMA.
Limited Lifetime Warranty does not apply to SFPs.
Hardware Alcatel.Lucent warrants that, for the applicable warranty period of one (1) year for hardware
(a) Equipment shall, under normal use and service, be free from defects in material and workmanship, and
(b) Equipment shall materially conform to Alcatel.Lucents specification therefore in effect on the date of
shipment. The warranty period applicable to any product shall be one (1) year from the date of shipment
except if Alcatel.Lucent performs installation Services for any Product, then the warranty period applicable
to the product shall be one (1) year from the date Purchaser is deemed to have accepted the Product in
accordance with the Agreement. Hardware warranty only includes Standard Repair or Replacement of
Defective Parts (Standard R&R) support.
Lifetime Support
All versions of the stackable product families come with a Limited Lifetime Hardware Warranty, limited to
the original owner, and will be provided for up to five (5) years. Faulty parts will be replaced via a five (5)
business days AVR (Advance Replacement) RMA.
Software & Firmware Alcatel.Lucent warrants that, for the applicable warranty period of ninety (90)
days for software, (a) Software media shall, under normal use and service, be free from defects in material
and workmanship, and (b) Software shall materially conform to Alcatel.Lucents specification therefore in
effect on the date of shipment. However, Alcatel.Lucent makes no warranty that any software will operate
uninterrupted or error free. Software warranty includes software bug fixes and patches. Software upgrades
and/or enhancements are not included as a part of Alcatel.Lucents warranty, but can be purchased
separately.
The Alcatel Product Life Span depends on many conditions in the market place and varies from platform to
platform. Historically speaking, some platforms have been out in the market more than seven (7) years and
still continue to exist on our product portfolio, while others may have experienced shorter life spans.
Alcatel.Lucent-ESD
Calabasas/CA./USA
Key Financial Advantages

Value
Cost Effectivness
CAPEX savings
Lowering engineering and operational costs

utilizing a common NMS (such as OmniVista
& 5620 SAM management)
Per port / feature / price ratio
Pricing vs. the competition
Alcatel-Lucents enterprise networking mission is to provide its customers with the industry's best value in
highly available, secure and easy-to-manage network solutions. The industrys best value means having
leading features for availability, security and manageability and simultaneously reducing the total cost of
network ownership. In short, the best network at the best total cost.
Alcatel-Lucent IP infrastructure solutions are not only priced right upfront. They also fit your business
exactly, reducing both operating and upgrade costs. All solutions share common components and feature
sets for deployment flexibility, easy maintenance and upgrading. Highly scalable and able to run on one
operating system to simplify centralized management, they can be reused across your network as it changes
and grows, thus yielding an even higher return on investment.
Delivering the best value to the enterprise, Alcatel-Lucents Enterprise Product Portfolio delivers the best
price/performance/features of any manufacturer in the industry.
Faster fault isolation/restoration
Enhanced engineering and local & remote configuration tools
Alcatel-Lucent offers the best value in port / feature / price ratio of any manufacturer in the industry.
Alcatel.Lucent-ESD
Calabasas/CA./USA
OmniSwitch 6400 Series Hardware Details

Hardware Overview of various 6400 Series Models
OmniSwitch 6400 Series switches are available in eight stackable chassis configurations as mentioned below:
OmniSwitch 6400-24 (OS6400-24): 24 triple speed ports (includes 4 MiniGBIC combo SFP/RJ45 ports)
OmniSwitch 6400-P24 (OS6400-P24): 24 PoE triple speed ports (includes 4 MiniGBIC combo SFP/RJ45 ports)
OmniSwitch 6400-P24H (OS6400-P24H): 24 PoE triple speed ports with 470 watts for PoE (includes 4
MiniGBIC combo SFP/RJ45 ports)
OmniSwitch 6400-48 (OS6400-48): 48 triple speed ports (includes 4 MiniGBIC combo SFP/RJ45 ports)
OmniSwitch 6400-P48 (OS6400-P48): 48 PoE triple speed ports (includes 4 MiniGBIC combo SFP/RJ45 ports)
OmniSwitch 6400-P48H (OS6400-P48H): 48 PoE triple speed ports with 470 watts for PoE (includes 4
MiniGBIC combo SFP/RJ45 ports)
OmniSwitch 6400-U24 (OS6400-U24): 24 SFP fiber ports (includes 2 MiniGBIC combo SFP/RJ45 ports)
OmniSwitch 6400-U24D (OS6400-U24D): 24 SFP fiber ports (includes 2 MiniGBIC combo SFP/RJ45 ports)
with DC power supply.
OmniSwitch 6400 Series

This section contains the information required to order the OmniSwitch 6400 Gigabit Ethernet chassis, stacking cables, backup power supplies and
optional advanced routing software.
All of the OmniSwitch chassis bundles include power shelf, DB25M-DB25F cable for remote mounting of the power supply, user manuals access card,
rack mounts, and RJ-45 to DB-9 adapter. Ethernet optical transceivers (SFP), stacking cable, advanced routing software, and backup power supplies can
be ordered separately.
The product family model names have the format: OS6400-xxxx. Suffix letters in the model name indicate different functionality:
* Power supply:
- "P" means bundle comes with Standard PoE power supply (360w),
- "P and H" means bundle comes with High-PoE power supply (510w)
- U means bundle comes with SFP fiber ports.
- "D" means bundle comes with DC power supply,
- No P, H or D means bundle comes with standard AC power supply package
All members of the OS6400 series employ a reduced depth main chassis. Power supply could be directly plugged in the rear of the chassis or remotely
mounted in the rack. Chassis Bundles ship with two rack mounts for the power shelf, and one chassis connection cable for remote mounting of the power
supply. OS6400 supports power supply redundancy.
All versions of the OS6400 family come with hardware Limited Lifetime Warranty. Limited Lifetime Warranty is limited to the original owner, and will
be provided for up to five (5) years after product End of Sales (EoS) announcement. Faulty parts will be replaced via a five (5) business days AVR
(Advance Replacement) RMA. Limited Lifetime Warranty does not apply to transceivers.
Model
Description
Number
OmniSwitch 6400 Chassis Bundles
OS6400-P24 chassis Gigabit Ethernet chassis in a 1U form factor with 20 RJ-45 ports individually configurable to 10/100/1000
OS6400-24
BaseT, 4 combo ports configurable to be 10/100/1000 BaseT or 1000 BaseX, and two dedicated 10G stacking ports. Combo ports
supprt either copper or fiber can be used on a one for one basis. Ethernet optical transceivers (SFP), stacking cable, and backup
power supplies can be ordered separately. Internal AC supply. [ECCN 5A992]
OS6400-P24 chassis Gigabit Ethernet chassis in a 1U form factor with 20 RJ-45 POE ports individually configurable to
OS6400-P24
10/100/1000 BaseT, 4 combo ports configurable to be 10/100/1000 BaseT or 1000 BaseX, and two dedicated 10G stacking ports.
Combo ports supprt either copper or fiber can be used on a one for one basis. Ethernet optical transceivers (SFP), stacking cable,
and backup power supplies can be ordered separately. The bundle includes a 360W AC PoE power supply with
power shelf, country specific power cord, user manuals access card, rack mounts and RJ-45 to DB-9 adaptor. [ECCN 5A992]
OS6400-24P chassis Gigabit Ethernet chassis in a 1U form factor with 20 RJ-45 POE ports individually configurable to
OS6400-P24H
OS6400-U24 chassis Gigabit Ethernet chassis in a 1U form factor with 22 100/1000 Base-X SFP ports, 2 combo ports configurable
OS6400-U24
to be 10/100/1000 BaseT or 100/1000 Base-X, and two dedicated 10G stacking ports. Combo ports supprt either copper or fiber can
Alcatel.Lucent-ESD
Calabasas/CA./USA
OS6400-U24D
OS6400-48
OS6400-P48
OS6400-P48H
OS6400-BP
OS6400-BP-P
OS6400-BP-PH
OS6400-BP-D
SFP-GIG-EXTND
SFP-GIG-LH40
SFP-GIG-LH70
SFP-GIG-LX
SFP-GIG-SX
SFP-GIG-T
SFP4-GIG-LX
SFP-GIG-BX-D
SFP-GIG-BX-U
SFP4-GIG-SX
SFP-100-BX20LT
SFP-100-BX20NU
SFP-100-LC-MM
SFP-100-LC-SM15
SFP-100-LC-SM40
be used on a one for one basis. Ethernet optical transceivers (SFP), stacking cable, and backup power supplies can be ordered
separately. Internal AC supply. [ECCN 5A992]
OS6400-U24 chassis Gigabit Ethernet chassis in a 1U form factor with 22 100/1000 Base-X SFP ports, 2 combo ports configurable
to be 10/100/1000 BaseT or 100/1000 Base-X, and two dedicated 10G stacking ports. Combo ports supprt either copper or fiber can
be used on a one for one basis. Ethernet optical transceivers (SFP), stacking cable, and backup power supplies can be ordered
separately. Internal DC power supply. [ECCN 5A992]
OS6400-48 chassis Gigabit Ethernet chassis in a 1U form factor with 44 RJ-45 ports individually configurable to 10/100/1000
BaseT, 4 combo ports configurable to be 10/100/1000 BaseT or 1000 BaseX, and two dedicated 10G stacking ports. Combo ports
support either copper or fiber can be used on a one for one basis. Ethernet optical transceivers (SFP), stacking cable, and backup
power supplies can be ordered separately. Internal AC supply. [ECCN 5A992]
Power Supplies
OS6400-BP modular 126W AC backup power supply. Provides backup power to one non-PoE switch. Ships with chassis
connection cable and country specific power cord.
OS6400-BP-P modular 360W AC backup power supply. Provides backup power to one PoE switch. Ships with chassis connection
cable and country specific power cord.
OS6400-BP-PH modular 510W AC backup power supply. Provides backup power to one PoE switch. Ships with chassis
connection cable, country specific power cord, power shelf and rack mounts.
OS6400-BP-D modular 120W DC backup power supply. Provides backup power to one non-PoE switch. Ships with chassis
connection cable.
Transceivers
Extended 1000Base-SX Gigabit Ethernet optical transceiver (SFP MSA). Supports multimode fiber over 850nm
wavelength (nominal) with an LC connector. Reach of up to 2 km on 62.5/125 m MMF and 50/125 m MMF. Requires
SFP-GIG-EXTND or GBIC-GIG-EXTND at the remote termination.[Formerly known as GE-EXTND-SFP]
1000Base-LH Gigabit Ethernet optical transceiver (SFP MSA). Supports single mode fiber over 1310 nm wavelength
(nominal) with an LC connector. Typical reach of 40 Km on 9/125 m SMF.
1000Base-LH Gigabit Ethernet optical transceiver (SFP MSA). Supports single mode fiber over 1550nm wavelength
(nominal) with an LC connector. Typical reach of 70 Km on 9/125 m SMF.[Formerly known as MINIGBIC-LH-70]
1000Base-LX Gigabit Ethernet optical transceiver (SFP MSA). Supports single mode fiber over 1310nm wavelength
(nominal) with an LC connector. Typical reach of 10 Km on 9/125 m SMF.[Formerly known as MINIGBIC-LX]
1000Base-SX Gigabit Ethernet optical transceiver (SFP MSA). Supports multimode fiber over 850nm wavelength
(nominal) with an LC connector. Typical reach of 300m on 62.5/125 m MMF or 550m on 50/125 m MMF.[Formerly
known as MINIGBIC-SX]
1000Base-T Gigabit Ethernet Transceiver (SFP MSA) - Supports category 5, 5E, and 6 copper cabling up to 100m. SFP
only works in 1000 Mbit/s speed and full-duplex mode
Pack of four (4) 1000Base-LX Gigabit Ethernet optical transceiver (SFP MSA). Support single mode fiber over 1310nm
wavelength (nominal) with an LC connector. Typical reach of 10 Km on 9/125 m SMF.
1000Base-BX SFP transceiver with an LC type of interface. This bi-directional transceiver is designed for use over single
mode fiber optic on a single strand link up to 10 km. Transmits 1310 nm and receives 1490 nm optical signal.
1000Base-BX SFP transceiver with an LC type of interface. This bi-directional transceiver is designed for use over single
mode fiber optic on a single strand link up to 10 km. Transmits 1490 nm and receives 1310 nm optical signal.
Pack of four (4) 1000Base-SX Gigabit Ethernet optical transceiver (SFP MSA). Support multimode fiber over 850nm
wavelength (nominal) with an LC connector. Typical reach of 300m on 62.5/125 m MMF or 550m on 50/125 m MMF.
100Base-BX SFP transceiver with an SC type interface. This bi-directional transceiver is designed for use over single
mode fiber optic on a single strand link up to 20KM point-to-point. This transceiver is normally used in the central office
(OLT) transmits 1550nm and receives 1310nm optical signal
100Base-BX SFP transceiver with an SC type interface. This bi-directional transceiver is designed for use over single
mode fiber optic on a single strand link up to 20KM point-to-point. This transceiver is normally used in the client (ONU)
transmits 1310nm and receives 1550nm optical signal
100Base-FX SFP transceiver with an LC type interface. This transceiver is designed for use over multimode fiber optic
cable.
100Base-FX SFP transceiver with an LC type interface. This transceiver is designed for use over single mode fiber optic
cable up to 15KM.
100Base-FX SFP transceiver with an LC type interface. This transceiver is designed for use over single mode fiber optic
cable up to 40KM.
Alcatel.Lucent-ESD
Calabasas/CA./USA
OS6400-CBL-150
OS6400-CBL-30
OS6400-CBL-60
OS6400-MNT
Cables andAccessories
OS6400 150 centimeters long stacking cable.
Base/wall mounting kit for OS6400 models. Includes 4 brackets and screws.
Alcatel.Lucent-ESD
Calabasas/CA./USA
OmniSwitch 6400-24
The OmniSwitch 6400-24 is a stackable edge/workgroup switch offering 20 unshared 10/100/1000Base-T ports, as well as
four combo ports individually configurable to be 10/100/1000Base-T.
The front panel of the OS6400-24 chassis contains the following major components:
System status and slot indicator LEDs
(20) unshared 10/100/1000Base-T ports
(4) shared combo 10/100/1000Base-T ports
(4) Combo SFP slots for 1000Base-X connections
Console port (RJ-45)
USB port (USB 2.0) (Future Release)
Alcatel.Lucent-ESD
Calabasas/CA./USA
OmniSwitch 6400-24 Specifications

Total unshared 10/100/1000BASE-T ports
per switch (ports 5-24)
Total shared 10/100/1000BASE-T combo ports
Total shared 1000BASE-X combo ports
Total 10/100/1000BASE-T ports per stack
Total combo SFP slots per stack
Power Supply
Flash Memory size
RAM Memory size
Overall Width
Height
Height (rack units)
Chassis Depth
Weight
Humidity (Operating & Storage)
Operating Temperature
Storage Temperature
Altitude
Standards supported
Data rate (RJ-45 Ports)
Data rate (SFP ports)
Maximum frame size
Connections supported
Cables supported
Maximum cable distance
20
4
4
192 (stack of eight switches)
Powered by 126W AC (internal)
128MB
256MB SDRAM
17.32 inches
1.73 inch
1 RU 1U x 17.32W x 10.63D
10.63 inches (internal power supplies)
8.94 lbs. (4.65 kg)
5% o 95% non-condensing
32 to 113 (F) or 0 to 45 (C)
-40 to 167 (F) or 10 to 70 (C)
Operating altitude: sea level at 40 degrees, Celsius and
10000 feet at 0 degrees, Celsius
Storage altitude: sea level to 40000 feet
802.3z, 802.3ab, 1000BASE-T, IEEE 802.3u
10 or 100Mbps (full or half duplex)
1 Gigabit per second (full duplex)
9,216 bytes
10/100/1000BASE-T and 1000BASE-X
10BaseT: unshielded twisted-pair (UTP)
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
100 meters
Alcatel.Lucent-ESD
Calabasas/CA./USA
OmniSwitch 6400-P24
The OmniSwitch 6400-P24 is a stackable edge/workgroup switch offering 20 unshared 10/100/1000Base-T Power over
Ethernet (PoE) ports, as well as four combo ports individually configurable to be 10/100/1000 Base-T PoE or 1000 Base-X
high speed connections.
The front panel of the OS6400-P24 chassis contains the following major components:
(20) unshared 10/100/1000Base-T PoE ports
(4) shared combo 10/100/1000Base-T PoE ports
Alcatel.Lucent-ESD
Calabasas/CA./USA
OmniSwitch 6400-P24 Specifications

Power Supply
Flash Memory size
RAM Memory size
Overall Width
Height
Height (rack units)
Chassis Depth
Weight
Storage Temperature
Altitude
Standards supported
Maximum frame size
Cables supported
PoE Power supplied to port
20
4
4
360W system supply (320 watts for PoE)
128MB
256MB SDRAM
17.32 inches
1.73 inch
1 RU 1U x 17.32W x 10.63D
10.63 inches without power shelf.
17.56 inches with power supply shelf and backup supply
10.28 lbs. (3.51 kg) without Power Supply
32 to 113 (F) or 0 to 45 (C)
-40 to 167 (F) or 10 to 70 (C)
802.3z, 802.3ab, 1000BASE-T, IEEE 802.3u
9,216 bytes
Category 5, 100 ohm
Default 15.4 watts per port
Configurable from 3 watts to 15.4 watts per port
It uses 360 watts P/S, the maximum available PoE power is
240 watts (less 1watt per port of overhead) per unit.
Please refer to the Power Supply Specification Section for
more details.
100 meters
Alcatel.Lucent-ESD
Calabasas/CA./USA
OmniSwitch 6400-P24H
The OmniSwitch 6400-P24H is a stackable edge/workgroup switch offering 20 unshared 10/100/1000Base-T Power over
high speed connections. This model comes with High-PoE power supply (510w).
Alcatel.Lucent-ESD
Calabasas/CA./USA
OmniSwitch 6400-P24H Specifications

Power Supply
20
4
4
Alcatel.Lucent-ESD
Calabasas/CA./USA
Flash Memory size

RAM Memory size
Overall Width
Height
Height (rack units)
Chassis Depth
Weight
Storage Temperature
Altitude
Standards supported
Maximum frame size
Cables supported
128MB
256MB SDRAM
17.32 inches
1.73 inch
1 RU 1U x 17.32W x 10.63D
32 to 113 (F) or 0 to 45 (C)
-40 to 167 (F) or 10 to 70 (C)
802.3z, 802.3ab, 1000BASE-T, IEEE 802.3u
9,216 bytes
Category 5, 100 ohm
Using the 510 watts P/S, the maximum available PoE
power is 390 watts (less 1 watt per port of overhead) per
unit.
more details.
100 meters
Alcatel.Lucent-ESD
Calabasas/CA./USA
OmniSwitch 6400-U24
The OmniSwitch 6400-U24 is a stackable edge/workgroup switch offering 22 MiniGBIC SFP ports (100 or 1000 Base-X),
2 MiniGBIC combo SFP/RJ45 ports.
The front panel of the OS6400-U24 chassis contains the following major components:
(22) MiniGBIC SFP ports (100 or 1000 Base-X)
(2) MiniGBIC combo SFP/RJ45 ports
USB port (USB 2.0)
Alcatel.Lucent-ESD
Calabasas/CA./USA
OmniSwitch 6400-U24 Specifications

Total MiniGBIC SFP ports (100 or 1000 Base-X)
Total MiniGBIC combo SFP/RJ45 ports
Power Supply
Flash Memory size
RAM Memory size
Overall Width (rack-mount flanges included)
Height
Height (rack units)
Chassis Depth
Weight
Storage Temperature
Altitude
Standards supported
Maximum frame size
Cables supported
22
2
128MB
256MB SDRAM
17.32 inches
1.73 inch
1 RU 1U x 17.32W x 10.63D
10.63 inches
8.94 lbs. (3.7 kg)
32 to 113 (F) or 0 to 45 (C)
-40 to 167 (F) or 10 to 70 (C)
802.3z, 802.3ab, 1000BASE-T, IEEE 802.3u
9,216 bytes
Category 5, 100 ohm
100 meters
Alcatel.Lucent-ESD
Calabasas/CA./USA
OmniSwitch 6400-U24D
The OmniSwitch 6400-U24D is a stackable edge/workgroup switch offering 22 MiniGBIC SFP ports (100 or 1000 BaseX), 2 MiniGBIC combo SFP/RJ45 ports.
The front panel of the OS6400-U24D chassis contains the following major components:
(22) MiniGBIC SFP ports (100 or 1000 Base-X)
(2) MiniGBIC combo SFP/RJ45 ports
USB port (USB 2.0)
Alcatel.Lucent-ESD
Calabasas/CA./USA
OmniSwitch 6400-U24D Specifications

Total MiniGBIC SFP ports (100 or 1000 Base-X)
Total MiniGBIC combo SFP/RJ45 ports
Power Supply
Flash Memory size
RAM Memory size
Overall Width (rack-mount flanges included)
Height
Height (rack units)
Chassis Depth
Weight
Storage Temperature
Altitude
Standards supported
Maximum frame size
Cables supported
22
2
Powered by 126W DC (internal)
128MB
256MB SDRAM
17.32 inches
1.73 inch
1 RU 1U x 17.32W x 10.63D
10.63 inches
8.94 lbs. (3.7 kg)
32 to 113 (F) or 0 to 45 (C)
-40 to 167 (F) or 10 to 70 (C)
802.3z, 802.3ab, 1000BASE-T, IEEE 802.3u
9,216 bytes
Category 5, 100 ohm
100 meters
Alcatel.Lucent-ESD
Calabasas/CA./USA
OmniSwitch 6400-48
The OmniSwitch 6400-48 is a stackable edge/workgroup switch offering 44 unshared 10/100/1000Base-T ports, as well as
four combo ports individually configurable to be 10/100/1000Base-T.
The front panel of the OS6400-48 chassis contains the following major components:
(44) unshared 10/100/1000Base-T ports
(4) shared combo 10/100/1000Base-T ports
Alcatel.Lucent-ESD
Calabasas/CA./USA
OmniSwitch 6400-48 Specifications

Power Supply
Flash Memory size
RAM Memory size
Overall Width
Height
Height (rack units)
Chassis Depth
Weight
Storage Temperature
Altitude
Standards supported
Maximum frame size
Cables supported
44
4
4
128MB
256MB SDRAM
17.32 inches
1.73 inch
1 RU 1U x 17.32W x 13.0D
13 inches
10.28 lbs. (4.65 kg)
32 to 113 (F) or 0 to 45 (C)
-40 to 167 (F) or 10 to 70 (C)
802.3z, 802.3ab, 1000BASE-T, IEEE 802.3u
9,216 bytes
Category 5, 100 ohm
100 meters
Alcatel.Lucent-ESD
Calabasas/CA./USA
OmniSwitch 6400-P48
The OmniSwitch 6400-P48 is a stackable edge/workgroup switch offering 44 unshared 10/100/1000Base-T Power over
Alcatel.Lucent-ESD
Calabasas/CA./USA
OmniSwitch 6400-P48 Specifications

Power Supply
Flash Memory size
RAM Memory size
Overall Width
Height
Height (rack units)
Chassis Depth
Weight
Storage Temperature
Altitude
Standards supported
Maximum frame size
Cables supported
44
4
4
128MB
256MB SDRAM
17.32 inches
1.73 inch
1 RU 1U x 17.32W x 10.63D
32 to 113 (F) or 0 to 45 (C)
-40 to 167 (F) or 10 to 70 (C)
802.3z, 802.3ab, 1000BASE-T, IEEE 802.3u
9,216 bytes
Category 5, 100 ohm
It uses 360 watts P/S, the maximum available PoE power is
240 watts (less 1 watt per port of overhead) per unit.
more details.
100 meters
Alcatel.Lucent-ESD
Calabasas/CA./USA
OmniSwitch 6400-P48H
The OmniSwitch 6400-P48H is a stackable edge/workgroup switch offering 44 unshared 10/100/1000Base-T Power over
The front panel of the OS6400-P48H chassis contains the following major components:
Alcatel.Lucent-ESD
Calabasas/CA./USA
OmniSwitch 6400-P48H Specifications

Power Supply
Flash Memory size
RAM Memory size
Overall Width
Height
Height (rack units)
Chassis Depth
Weight
Storage Temperature
Altitude
Standards supported
Maximum frame size
Cables supported
44
4
4
128MB
256MB SDRAM
17.32 inches
1.73 inch
1 RU 1U x 17.32W x 10.63D
32 to 113 (F) or 0 to 45 (C)
-40 to 167 (F) or 10 to 70 (C)
802.3z, 802.3ab, 1000BASE-T, IEEE 802.3u
9,216 bytes
Category 5, 100 ohm
Configurable from 3watts to 15.4watts per port
Using the 510 watts P/S, the maximum available PoE
power is 390 watts (less 1 watt per port of overhead) per
unit.
more details.
100 meters
Alcatel.Lucent-ESD
Calabasas/CA./USA
Status LEDs
LEDs provide visual status information. These status lights are used to indicate conditions, such as hardware and
software status, primary role status (stacked configurations), power supply status, primary and secondary status (stacked
configurations), fan and temperature errors, slot number information, data speed, link integrity, and activity. Refer to the
diagram below for detailed information on LED states.
Alcatel.Lucent-ESD
Calabasas/CA./USA
Internal Architecture
The OmniSwitch 6400-24 Internal Architecture
RS-232
INF
Stack A
Stack B
SDRAM
CPU
FLASH/Boot
HI-GIG
USB
PCI Bus
Packet Processor
Switching chip
Copper
PHY
Phy Combo
x4
1X4
SFP
Copper
PHY
Copper
PHY
23
24
4 x 1G BaseT or
100/1000 BaseX
COMBO PORTS
20 x 1000BaseT (RJ-45) PORTS
OS6400-24 Base Unit Block Diagram
The base unit provides maximum 20 10/100/1000 Base-T ports and 4 combo ports. It is comprised of 1 Packet Processor
switching chip having different PHYs and is connected to CPU (400MHz) via 66MHz PCI Bus. The Host system includes
256MB SDRAM, 128MB Spansion Flash, RTC, Watchdog timer, Thermal detector, FAN failure detector, LED control
circuit, , and other glue logic. The Base unit used a 12VDC/48VDC output PWR. The on-board DC/DCs are used to
generate 5V/3.3V/2.5V/ 1.5V/1.25V/1.2V/1V from 12VDC.
Alcatel.Lucent-ESD
Calabasas/CA./USA
The OmniSwitch 6400-P24 Internal Architecture

RS-232
INF
Stack A
Stack B
SDRAM
CPU
FLASH/Boot
HI-GIG
USB
PCI Bus
POE
Control
Board
Packet Processor
Switching chip
Copper
PHY
Phy Combo
x4
1X4
SFP
Copper
PHY
Copper
PHY
23
24
4 x 1G BaseT or
100/1000 BaseX
COMBO PORTS
OS6400-P24 Base Unit Block Diagram
generate 5V/3.3V/2.5V/ 1.5V/1.25V/1.2V/1V from 12VDC. The 48VDC is for POE power supply.
Alcatel.Lucent-ESD
Calabasas/CA./USA
The OmniSwitch 6400-48 Internal Architecture

RS-232
INF
Stack A
Stack B
SDRAM
CPU
FLASH/Boot
HI-GIG
USB
PCI Bus
Packet Processor
Switching chip
Packet Processor
Switching chip
HI-GIG
Phy Combo
x4
1X4
SFP
1
2
4 x 1G BaseT or
100/1000 BaseX
COMBO PORTS
Copper
PHY
5
6
Copper
PHY
Copper
PHY
Copper
PHY
23
24
Copper
PHY
25
47
26
48
OS6400-48 Base Unit Block Diagram
generate 5V/3.3V/2.5V/1.5V/1.25V/1.2V/1V from 12VDC.
Alcatel.Lucent-ESD
Calabasas/CA./USA
The OmniSwitch P48 Internal Architecture

RS-232
INF
Stack A
Stack B
SDRAM
CPU
FLASH/Boot
HI-GIG
USB
PCI Bus
POE
Control
Board
Packet Processor
Switching chip
Packet Processor
Switching chip
HI-GIG
Phy Combo
x4
1X4
SFP
Copper
PHY
Copper
PHY
Copper
PHY
Copper
PHY
Copper
PHY
23
25
47
24
26
48
4 x 1G BaseT or
100/1000 BaseX
COMBO PORTS
OS6400-P48 Base Unit Block Diagram
generate 5V/3.3V/2.5V/1.5V/1.25V/1.2V/1V from 12VDC. The 48VDC is for POE power supply.
Alcatel.Lucent-ESD
Calabasas/CA./USA
The OmniSwitch U24 & U24D Internal Architecture

RS-232
INF
Stack A
Stack B
SDRAM
CPU
FLASH/Boot
HI-GIG
USB
PCI Bus
Packet Processor
Switching chip
Phy Combo
x2
2 RJ-45
Copper
23
24
2 - RJ45/SFP
Triple Speed
COMBO PORTS
22 x SFP 100FX/1000BaseX PORTS
OS6400-U24/OS6400-U24D Base Unit Block Diagram

The base unit provides 22 100BASE-FX/1000Base-X ports and 2 combo ports individually configurable to be
10/100/1000 Base-T or 1000Base-X/100BASE-FX with 2 CX4 ports for uplink or 2 Hi G ports for stacking. It is
comprised of 2 Packet Processor switching chip having different PHYs and is connected to CPU (400MHz) via 66MHz
PCI Bus. The Host system includes 256MB SDRAM, 128MB Spansion Flash, RTC, Watchdog timer, Thermal detector,
FAN failure detector, LED control circuit, , and other glue logic. The Base unit used a 12VDC/48VDC output PWR. The
on-board DC/DCs are used to generate 5V/3.3V/2.5V/1.5V/1.25V/1.2V/1V from 12VDC.
Alcatel.Lucent-ESD
Calabasas/CA./USA
The OmniSwitch 6400 Series Power Supply System

OmniSwitch 6400 Series switches supports redundant hot swappable power supplies.
AC supplies: 90-220V AC
DC supplies: 36-72V DC
Non-PoE models
Uses internal main power supplies and external backup power supplies directly connected to the rear of the unit or
remotely mounted
Backup power supplies use a power shelf to hold one 6400-BP (AC) or one 6400-BP-D (DC) supply
PoE models
360W (AC) and 510W (AC) power supplies only used with PoE models
Power shelf holds one 510W AC, or two 360W AC power supplies
Maximum estimated power for PoE with 360W power supply: 240 W
Maximum estimated power for PoE with 510W power supply: 390W
The power supplies can also be connected using a cable, in case there is a need for a less deep chassis. Same power shelf can
be mounted in the rack using the mounting ears (removable in case the power supply needs to be plugged into the rear of the
chassis).
Power Supply Shelf

Alcatel-Lucent requires the use of power supply shelf when the power supply is used in a 1U (i.e., 1.5 inches/3.8cm)
configuration.
In a 2U (i.e., 3 inches/7.6 cm) configuration, if you have a 510W power supply you can either use the power supply shelf or you
can mount the 510W power supply directly to a rack.
Power Supply Redundancy
OS6400-BP-P
Backup Power Supplies

OS6400-BP modular 126W AC backup power supply. Provides backup power to one non-PoE switch. Ships with chassis
OS6400-BP-P modular 360W AC backup power supply. Provides backup power to one PoE switch. Ships with chassis
OS6400-BP-PH
OS6400-BP-PH modular 510W AC backup power supply. Provides backup power to one PoE switch. Ships with chassis
connection cable, country specific power cord, power shelf and rack mounts.
OS6400-BP
OS6400-BP-D
OS6400-BP-D modular 120W DC backup power supply. Provides backup power to one non-PoE switch. Ships with chassis
connection cable.
Monitoring Chassis Power

OmniSwitch 6400 Series switches can be monitored and managed via the console port using Command Line Interface (CLI)
commands. The switches can also be monitored and managed via the Ethernet ports using CLI commands, WebView, SNMP,
and OmniVista.
Power Supply Specifications

OmniSwitch 6400 Series switches support the following power supplies:
PS-530W-AC power supply
Alcatel.Lucent-ESD
Calabasas/CA./USA
PS-120W-DC power supply
Alcatel.Lucent-ESD
Calabasas/CA./USA
Alcatel.Lucent-ESD
Calabasas/CA./USA
Alcatel.Lucent-ESD
Calabasas/CA./USA
Alcatel.Lucent-ESD
Calabasas/CA./USA
Power Supply Shelf

Alcatel-Lucent requires the use of the power supply shelf when connecting power supplies. The shelf can be attached
directly to the back of the chassis or rack mounted.
A power shelf is used to holds two 360W (primary & backup) or one 510W (primary). PS Shelf/supplies plug directly in
the back of the unit and total unit + shelf depth is 44.6 cm/17.56inch.
Two 360W in a shelf
One 510W in a shelf
Other possibility is power supplies can be connected with a cable for 2U configuration. A power shelf can hold one
backup 126W or 120W supply. The primary and backup PS on top of the unit and total unit + shelf depth is: 27 cm (10.63
inch).
2U configuration: the primary and backup PS on top of the unit Depth: 27 cm (10.63 in)
Alcatel.Lucent-ESD
Calabasas/CA./USA
Alcatel.Lucent-ESD
Calabasas/CA./USA
Power Cords
Because the power cord is the power supplys main 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 to be used with 115-Volt configuration is a minimum type SJT (SVT) 18/3, rated at 250Volts AC, 10 Amps with
a maximum length of 15 feet. One end terminates in an IEC 320 attachment plug and the other end terminates in a NEMA 5-15P
plugs. The power cord to be used with 230-Volt configuration is minimum type SJT (SVT) 18/3, rated 250 Volts AC, 10 Amps
with a maximum length of 15 feet. One end terminates in an IEC 320 attachment plug and the other end terminates as required by
the country where it will be installed. European cords must be Harmonized (HAR) type.
DC-to-DC Power Cords
For DC-to-DC connections please refer to the Hardware Users Manuals for additional guidelines and information.
Refer to the information below for power plug types by region:
North America
United Kingdom / Ireland
Europe
Japan
Australia
India
Italy
Switzerland / Liechtenstein
Denmark / Greenland
Argentina
Power Cord Types

NEMA 5-15-P (US), C22.2, No. 42 (Canada)
BS 1,363
CEE 7/7
JIS 8,303
AS 3,112
BS 546
CIE 2,316
SEV 1011
SRAF 1,962 / D816 / 87
AR1-10P
Redundant AC Circuit Recommendation

If possible, it is recommended that each AC outlet reside on a separate circuit. With redundant AC, if a single circuit fails,
the switchs remaining power supplies (on separate circuits) will likely be unaffected and can therefore continue operating.
Note. The switch must have power supply redundancy for the redundant AC circuit to be effective.
Grounding the Chassis

The switch has two threaded holes for grounding screws located on the back of the chassis. These holes use 10-32 screws
and are approximately one inch apart. These holes are surrounded by a small paint-free rectangular area, which provides
metal-to-metal contact for a ground connection.
Use this connector to supplement the ground provided by the AC power cord. To do so, install a Panduit Grounding Lug
(type LCD8-10A-L) using 8AWG copper conductors to the paint-free rectangular area. Be sure to use a crimping tool.
Temperature Management
The operating temperature of your switch is an important factor in its overall operability. In order to avoid a temperaturerelated system failure, your switch must always run at an operating temperature between 0 and 45 C (32 to 113 F).
To avoid chassis over-temperature conditions, follow these important guidelines:
Be sure that your switch is installed in a well-ventilated environment. To ensure adequate airflow, allow at least six inches of
clearance at the front and back of the chassis. In addition, leave at least two inches of clearance at the left and right sides.
Be sure that blank cover panels are installed at empty slot positions at all times. Blank cover panels help regulate airflow
and thus regulate the overall operating temperature in the switch. To check the switchs current temperature status, use the
show temperature command.
Alcatel.Lucent-ESD
Calabasas/CA./USA
Managing OmniSwitch 6400 Series Stacks

In addition to their working as individual stand-alone switches, OmniSwitch 6400 Series 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.
Note. You can also manage and monitor OmniSwitch 6400 Series stacks through WebView, Alcatel-Lucents 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.
OmniSwitch 6400 Series Stack Overview

Users can configure up to eight OmniSwitch 6400 Series switches, in any combination of OS6400-24 and OS6400-48 chassis types,
into a single virtual chassis known as a stack. With stacks, simply adding additional switches to the stack can easily expand
switching capacity. For example, a user can start with a stack composed of two switches and add up to six additional switches to
that stack as network demands increase over time.
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 synchronizes the switches operating software and configuration parameters are backed up on all switches in the stack.
As a result, the original operating software and configuration parameters can be easily recovered if corrupted or otherwise lost.
Roles within the Stack

In order to operate as a virtual chassis, switches within an OmniSwitch 6400 Series stack are assigned specific roles.
These roles include primary and secondary management roles, idle status, and pass-through.
Primary and Secondary Management

When OmniSwitch 6400 Series switches operate in a stack, one switch in the stack always assumes the primary management role.
This primary element is responsible for functions, such as software and configuration management, web-based management (i.e.,
WebView), SNMP management, switch diagnostics, and software rollback.
One additional switch in the stack operates in a secondary management role. This switch serves as a backup, and is always ready to
assume the primary management role in the stack if the switch with the primary role fails or is taken offline for any reason.
Since the secondary module quickly and automatically assumes management responsibilities, switches operating in idle mode
elsewhere in the stack continue to pass traffic without disruption. This redundancy provides effective safeguards for mission-critical
network traffic and is one of the stacks most important failover features.
Primary Management Module Selection

For a stack of OmniSwitch 6400 Series switches to operate as a virtual chassis, there must be a mechanism for dynamically
selecting the switch within the stack that will assume the primary management role.
OmniSwitch 6400 Series switches use three different methods for selecting the primary switch. These methods are:
Chassis MAC address
Saved slot number
Chassis uptime
Alcatel.Lucent-ESD
Calabasas/CA./USA
Using the Chassis MAC Address

By default, the primary management role will be given to the switch with the lowest chassis MAC address. However, for this to
occur, all switches in the stack must be booted within 15 seconds of each other. In addition, switches in the stack must have no
preconfigured slot information. Because of these two conditions, the MAC address method for selecting the primary module usually
occurs with new out of the box switches, or switches from which any preconfigured slot information has been cleared.
Using Saved Slot Information

The saved slot number is the slot number the switch will assume following a reboot. This information is stored in a switchs
boot.slot.cfg file; the switch reads its slot number assignment from this file at boot up and assumes the specified slot number within
the stack. If switches in a stacked configuration have no preconfigured slot assignments, the system software dynamically assigns
the slot number for each switch. The user can also manually assign slot numbers.
When a stack with preconfigured slot information is booted, it is not the lowest MAC address that determines the primary
management module. Instead, the slot information stored in each switchs boot.slot.cfg is read by the system software and used in
determining the primary. The switch with the lowest saved slot number becomes the primary management module.
Note. Although, for ease-of-management purposes, it is recommended that slot numbers are assigned beginning with slot number 1,
it is not a requirement. In other words, a stack of four switches can have slot assignments 3, 4, 5, and 6. However, it is important
that each element in a stack is assigned a unique slot number. Do not assign duplicate slot numbers to elements in a stack.
Otherwise, one or more switches will be forced into pass-through mode.
Using Switch Uptime

A user can override both the MAC address and saved slot methods for determining a stacks primary management module.
Controlling the uptime of switches in the stack does this. If all elements of a stack are powered off, the user can force a particular
switch to become primary by powering on that switch and waiting a minimum of 15 seconds before powering on any other switches.
This can be useful if the user wants a switch placed in a specific location, e.g., the top-most switch in a stack, to become the
primary. As with the lowest MAC address method, the primary management module is dynamically assigned slot number 1 when
the stack is booted.
Secondary Management Module Selection

In order to provide effective management module redundancy, all OmniSwitch 6400 Series stacked configurations dynamically
assign a backup, or secondary, management module during the boot process.
OmniSwitch 6400 Series stacks use two different methods for selecting the secondary switch. These methods are:
Stacking connection to the primary switch
Saved slot number
Using the Stacking Connection to the Primary Switch

By default, the switch that is connected to the primary switchs stacking port A is automatically assigned the secondary management
role. This applies to stacks on which there is no pre-assigned slot information i.e., there is no boot.slot.cfg file present in any switch.
Using Saved Slot Information

If a stack with pre-assigned slot information for each switch is booted, the switch with the second lowest slot value is assigned the
secondary management role. For example, if a stack of four switches is booted and the pre-assigned slot values for each switch are 1,
2, 3, and 4, the switch with the slot value of 2 is assigned the secondary role. Meanwhile, the switch with the slot value of 1 is
assigned the primary management role.
Alcatel.Lucent-ESD
Calabasas/CA./USA
Idle Module Role

Switches that are not assigned either the primary or secondary role in a stack are, by default, assigned the role of idle modules.
These idle modules operate similarly to Network Interface (NI) modules in a chassis-based switch such as the OmniSwitch 7700/7800.
It is the job of idle modules to send and receive 10/100/1000 Ethernet traffic on their ports.
In the event of a management module failure within the stack, the idle module with the next lowest slot number in the stack will
automatically assume the secondary management role. In other words, if the primary module in a stack goes down for any reason and
the secondary takes over the primary management role, the switch must now assign a new secondary module. The idle element with
the next lowest slot number assumes this new responsibility until the situation is corrected and all elements in the stack are reloaded.
Note. Primary and secondary management modules also send and receive 10/100/1000 traffic on their Ethernet ports. 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.
Pass-Through Mode
The pass-through mode is a state in which a switch has attempted to join a stack but has been denied primary, secondary, and idle
status. When a switch is in the pass-through mode, its Ethernet ports are brought down (i.e., they cannot pass traffic). Its stacking
cable connections remain fully functional and can pass traffic through to other switches in the stack. In this way, the pass-through
mode provides a mechanism to prevent the stack ring from being broken. However, note that when a switch comes up in
Pass-through mode, it should not be left unresolved. Pass-through mode is essentially an error state that should be corrected
immediately by the user.
Conditions that can trigger a switch to enter pass-through mode include:
Duplicate slot numbers have been assigned within the stack
The user has manually forced the switch into pass-through mode
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 assignments within the stack. So,
in order to avoid pass-through mode, it is useful to keep track of the current saved slot numbers on all elements in the stack. Slot
number assignments are stored in the boot.slot.cfg file in the /flash directory of each switch.
If the stack is booted and the same slot number is discovered on two or more switches, the switch with the lowest MAC address is
allowed to come up and operate normally. Meanwhile, switches with the duplicate slot number and a higher MAC address come up
in pass-through mode.
Alcatel.Lucent-ESD
Calabasas/CA./USA
Stack Cabling
Switches in a stack are connected to each other by stacking cables. The valid cable lengths are 1.5m (4.9 feet), 60cm (23.6 inches),
and 30cm (11.8 inches). These stacking cables provide high-speed, dual-redundant links between switches in a stack.
Stacking cables for OmniSwitch 6400 Series switches can be connected in any pattern. In other words, the cable connected to
stacking port A of one switch can be connected to either stacking port A or stacking port B of the adjacent switch.
However, it is strongly recommended that the cabling pattern remains consistent across the stack.
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.
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.
Alcatel.Lucent-ESD
Calabasas/CA./USA
Redundant Stacking Cable Connection

OmniSwitch 6400 Series switches allow redundant stacking cable connections between the top-most and bottom-most
switches in a stack.
Important: 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.
Redundant stacking cables provide a form of dual redundancy. As shown in the figure above, the redundant cable allows traffic
to flow in the event of a stacking link failure. The redundant cable also provides failover if a switch goes down within the stack.
Traffic continues to flow between the modules that remain operational.
Slot Numbering
For a stack of OmniSwitch 6400 Series 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 LED located on the left side of the chassis also displays the slot number on the front panel of each switch.
There are two ways stacking modules are assigned slot numbers:
Dynamic slot number assignment by the system software
Manual slot number assignment by the user
Dynamic Slot Number Assignment

Dynamic slot number assignment occurs when there are no boot.slot.cfg files present in the switches/flash directories.
This is the case for new, out of the box, switches that have not been previously booted.
When a brand new stack (or stack with no boot.slot.cfg files) is booted, the system software automatically detects the module with the
lowest MAC address. This module is assigned the primary management role and, by default, is given the slot number 1.
The module connected to the primarys stacking port A is automatically assigned the secondary management role and given the slot
number 2. As the other modules in the stack become operational, they are assigned idle roles and are automatically assigned unique
slot numbers (38, depending on the number of switches in the stack). The slot numbering for idle modules is determined by each
modules physical location in the stack.
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.
Manual Slot Number Assignment

To manually assign slot numbers to one or more modules in a stack, use the stack set slot command. This command writes slot
information to the boot.slot.cfg file located in a switchs /flash directory.
It is this saved slot information that the switch will assume following a reboot.
Manually assigning slot numbers can be useful in reordering existing slot numbers in order to create a sequential numbering scheme
from the top of the stack to the bottom (or vice-versa).
Alcatel.Lucent-ESD
Calabasas/CA./USA
Hot-Swapping Modules in a Stack

As with chassis-based switches, such as the OmniSwitch 7700/7800/8800 or OmniSwitch 9000, NI modules within an
OmniSwitch 6400 Series virtual chassis are hot swappable. NI modules are essentially those modules operating in the stack in idle
mode. These modules can be removed from, or added to, an existing stack without disrupting other modules in the stack.
Removing Switches from an Existing Stack

When removing switches from an existing stack, observe the following important guidelines:
Do not attempt to hot-swap modules operating in primary or secondary management roles
Be sure the stacking cables and stacking cable redundancy are not disrupted
Hot swapping is intended for switches in idle and, if applicable, pass-through status only. Removing primary or secondary
management modules from a stack will trigger a failover sequence, i.e., one or more additional modules within the stack must reload
in order to reassign the management roles.
Whenever possible, avoid removing a switch that is operating as a primary or secondary management module.
Also, removing a switch from a stacked configuration can disrupt stack cabling at the rear of the stack.
When removing a module, be sure that stacking link integrity, including important stacking cable redundancy, is maintained between
all remaining modules.
Inserting Switches into an Existing Stack

When inserting switches into an existing stack, observe the following important guidelines:
Avoid duplicate saved slot numbers
Never attempt to operate more than eight switches in a single stack
Make sure all switches are running the same software version.
Note. Other stackable Alcatel-Lucent products, cannot be added to an OmniSwitch 6400 Series virtual chassis.
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 present in the /flash directory of any switch being
added. When the switch is connected to the existing stack and booted, the system software automatically assigns it a unique slot
number. No duplicate slot errors occur.
Note. If it is preferable to add a switch with an existing boot.slot.cfg file to a stack, be sure that the saved slot number of the incoming
switch is not already assigned to a switch operating in the stack.
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.
5 Power on all incoming modules.
Note. No more than eight switches can operate in a single stacked configuration at any time.
Alcatel.Lucent-ESD
Calabasas/CA./USA
Reloading Switches
Reloading is essentially a soft boot of a switch. Users can reload stacked modules operating in any role i.e., primary,
secondary, idle, and pass-through. Refer to the sections below for more information.
Reloading the Primary Management Module

If the switch with the primary management role is reloaded, the switch with the secondary role automatically takes over
primary management functions. In other words, the switch with the secondary role assumes the primary role as soon as the
reload is initiated.
Meanwhile, the idle switch with the next lowest slot number automatically assumes the secondary role.
When the reloaded switch (the former primary module) comes back up, it assumes an idle role within the stack.
Note. A primary management module reload can also be scheduled for a later time or date.
Reloading the Secondary Management Module

If the switch with secondary management role is reloaded, the idle switch with the lowest slot number will automatically
assume the secondary role. The reloaded switch (the former secondary) will assume an idle role when it comes back up.
Meanwhile, the switch with the primary management role, as well as any other idle modules in the stack, continue
operations without interruption.
Note. A secondary management module reload can also be scheduled for a later time or date.
Reloading Switches with Idle Roles

Similar to reloading Network Interface (NI) modules on chassis-based switches such as the OmniSwitch 7700/7800 and
OmniSwitch 8800, modules operating in idle status within a stack can be reloaded via the CLI.
Note. Any traffic being passed on the modules Ethernet ports will be interrupted during the reboot. Other modules within
the stack will continue to operate without interruption.
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.
Reloading Switches in Pass-Through Mode

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

Reloading all switches in the stack is essentially a full reboot of the virtual chassis. This can be useful in restoring a
stacks previously configured topologyi.e., the stacks saved slot numbers and management roles.
Note, however, that all data flow on the stack is interrupted whenever a full reboot is issued.
Software Synchronization During a Full Reload

If the checksum value on the stacks non-primary switches differs in any way from the checksum value on the primary
switch, the primary switch automatically distributes its system and configuration software to all other switches in the stack
whenever a full reload is executed.
During this automatic software synchronization, system and configuration software on the secondary and idle switches is
overwritten. Because the primary switchs last known good software is propagated to all switches, the synchronization
process helps ensure effective redundancy across the stack.
Alcatel.Lucent-ESD
Calabasas/CA./USA
Effects of Saved Slot Number Information on the Reload Process

Depending on the status of saved slot information across the stack, there are different slot numbering and management
role scenarios that can occur following a full reboot. For this reason, checking the current stack topology before issuing a
full reboot is strongly recommended. To check the current stack topology, use the show stack topology command.
Possible saved slot number conditions include:
All switches have unique saved slot information
No switches in the stack have saved slot information
Some switches have saved slot information, others do not
Two or more switches have duplicate slot information
All Switches Have Unique Saved Slot Information
If a full reload is issued and all switches have unique slot numbers saved to their boot.slot.cfg files, the slot numbers will
be assigned according to the saved slot information. The primary management role will be given to the switch with the
lowest saved slot number. The secondary management role will be given to the switch with the second-lowest saved slot
number. All other switches will be assigned to idle roles.
No Switches In the Stack Have Saved Slot Information
If a full reload is issued and no switches in the stack have unique slot numbers, slot numbers will be assigned beginning
with the switch with the lowest MAC address. (This can occur if the boot.slot.cfg file has been deleted from each switchs
/flash directorye.g., by issuing the stack clear slot command for all modules in the stack.)
The switch with the lowest MAC address is assigned slot number 1 and given the primary management role. The switch
connected to stacking port A of the primary switch is automatically assigned slot number 2 and given the secondary
management role. Stack cabling is then used to determine the dynamic slot numbering of the remaining modules in the
stack. The switch immediately adjacent to slot 2 is assigned slot number 3 and given an idle role, etc.
Some Switches Have Saved Slot Information, Others Do Not
If only some switches in the stack have boot.slot.cfg files in their /flash directories, the system software will first read the
contents of these files and then dynamically assigns unique slot numbers to any switches that do not have saved slot
information. The primary management role will be given to the switch with the lowest saved slot number. The secondary
management role will be given to the switch with the second lowest saved slot number. All other switches will be assigned
to idle roles. When the system software dynamically assigns unique slot numbers, a boot.slot.cfg file is automatically
generated with the new slot information. Because all switches now have unique saved slot information, any subsequent
reload all commands issued will cause the stack to come up.
Two or More Switches Have Duplicate Slot Information
If a full stack reboot is issued and the same slot number is found in the boot.slot.cfg file of two or more switches, the
switch with the lowest MAC address is allowed to come up and operate normally. Meanwhile, any other switches with the
duplicate slot number come up in pass-through mode.
The pass-through mode is essentially an error state in which a switch has been denied primary, secondary, and idle roles
within the stack. When a switch is in pass-through mode, its Ethernet ports are brought down and cannot pass traffic. It is
for this reason that users should always check the current saved slot number for each switch before issuing the reload all
command. To check the current saved slot information across the stack, use the show stack topology command.
Avoiding Split Stacks

The term splitting a stack refers to the creation of isolated modules within the virtual chassis.
A split stack can result from the following conditions:
Two or more non-adjacent switches are reloaded simultaneously
The stack is reloaded without a redundant stacking cable connection
The sections below offer simple guidelines for avoiding splitting the stack during the reload process.
Do Not Reload Non-Adjacent Switches Simultaneously
If non-adjacent switches in the stackfor example, the top switches in the stack and the third-from-top switch in the
stackare reloaded simultaneously, a problem will occur. The switch between the two nonadjacent switches will become
isolated and the virtual chassis will be effectively split.
To avoid splitting the stack, do not reload the two non-adjacent switches simultaneously. Instead, simply reload the top
switch first, and then reload the third-from-top switch, or vice-versa.
Alcatel.Lucent-ESD
Calabasas/CA./USA
Be Sure a Redundant Stacking Cable is installed at All Times

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

OmniSwitch 6400 Series stacks allow users to manually force the secondary switch to assume the primary management role.
This is referred to as takeover. The behavior of a takeover is similar to that of reloading the primary management module.
Whenever a takeover is initiated, the switch with the secondary role automatically takes over primary management
functions. The primary switch is automatically reloaded and any traffic being passed on the primary switchs Ethernet
ports is interrupted.
Meanwhile, the idle switch with the next-lowest slot number automatically assumes the secondary role.
When the former primary module comes back up, it assumes an idle role within the stack.
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.
Synchronizing Switches in a Stack

Management module synchronization refers to the process of copying all files in the /flash/working and /flash/certified
directories of the primary management module to the /flash/working and /flash/certified directories of all the other
switches in the stack. The system and configuration software on the non-primary switchesi.e., the secondary
management module and any modules operating in idleis overwritten.
The synchronization process ensures that the contents of these directories match exactly for all switches across the stack.
This can be especially useful after new software has been loaded to the primary management module. Further,
synchronization prevents any switch from assuming a management role within the stack with incorrect or outdated
software or configuration files. Because the primary switchs last known good software is propagated to all switches, the
synchronization process helps ensure effective redundancy across the stack.
In order to maintain effective management module redundancy, switches in the stack must be synchronized at all times.
When the synchronization process is initiated, modules within the stack continue to operate without interruption and data
flow across the stack is unaffected.
Automatic Synchronization during a Full Reload

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

As shown in the previous sections, monitoring the current status and operation of all elements in a stack can help users avoid
unexpected stack conditions. The show CLI commands are useful in monitoring stack conditions.
Visually Monitoring the Stack

Users can also monitor many stack operations by viewing the front panel LEDs on all elements in the stack.
Alcatel.Lucent-ESD
Calabasas/CA./USA
Managing Power over Ethernet (PoE)

Power over Ethernet (PoE) is supported on OmniSwitch 6400 Series switches and provides inline power directly from the
switchs Ethernet ports. Powered Devices (PDs) such as IP phones, wireless LAN stations, Ethernet hubs, and other access
points can be plugged directly into the Ethernet ports. From these RJ-45 ports the devices receive both electrical power
and data flow. 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 the feature, PoE. The terms Power over Ethernet
(PoE), Power over LAN (PoL), Power on LAN (PoL), and Inline Power are synonymous terms used to describe the
powering of attached devices via Ethernet ports.
Additional terms, such as Powered Device (PD) and Power Source Equipment (PSE) are not synonymous with PoE, but
are directly related to the feature:
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, etc.
PSE refers to power sourcing equipment, which provides power to a single link section. PSE main functions include
searching the PD, optionally classifying the PD, supplying power to the link section only if the PD is detected, monitoring
the power on the link section, and scaling power back to detect level when power is no longer requested or required.
As the OmniSwitch 6400 Series switches fully support 10/100/1000 Ethernet connectivity, you may also attach non-PD
equipment, such as computer workstations, printers, servers, etc. to the PoE ports.
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).
Note. You can also monitor all chassis components and manage many chassis features, including Power over Ethernet,
with WebView; Alcatel-Lucents 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.
Power over Ethernet Specifications

IEEE Standards supported
Default PoE administrative status
Default PoE operational status
OmniSwitch 6400 Series platforms supporting PoE
Cable distances supported
Total number of PoE-capable ports per switch
Default amount of inline power allocated for each port
Range of inline power allowed for each port
PoE Current draw
IEEE 802.3af DTE Power via MDI

Enabled
Disabled (PoE must be activated on a switch-by-switch basis via the lanpower start
command)
OmniSwitch 6400 Models designated with the letter P
100 meters
Up to 48
15400 Milliwatts
3000-15400 Milliwatts
Approximately 4.3 amps
Default 15.4watts per port
Using the 360watts P/S, the maximum available PoE power is 240 watts (less 1watt
per port of overhead) per unit.
Using the 510watts P/S, the maximum available PoE power is 390watts (less 1watt per
port of overhead) per unit.
Please refer to the Power Supply Specification Section for more details.
Alcatel.Lucent-ESD
Calabasas/CA./USA
Power over Ethernet Defaults
Power Priority level for a port

The capacitor detection method
Disabled
15.4watts
Default 15.4watts per port
Using the 360watts P/S, the maximum available PoE power is 240 watts (less 1watt
per port of overhead) per unit.
Using the 510watts P/S, the maximum available PoE power is 390watts (less 1watt per
port of overhead) per unit.
Please refer to the Power Supply Specification Section for more details.
Low
Disabled
Priority discount status
Enabled
PoE operational status

Total power allocated to a port
Port Priority Levels

As not all Powered Devices (PDs) connected to the switch have the same priority within a customer network setting, the
OmniSwitch 6400 Series switches allow the user to specify priority levels on a port-by-port basis.
Priority levels include low, high, and critical. The default priority level for a port is low.
Low. This default value is used for port(s) that have low-priority devices attached. In the event of a power management
issue, inline power to low-priority ports is interrupted first (i.e., before critical and high-priority ports).
High. This value is used for port(s) that have important, but not mission-critical, devices attached. If other ports in the
chassis have been configured as critical, inline power to high-priority ports is given second priority.
Critical. This value is used for port(s) that have mission-critical devices attached, and therefore require top (i.e., critical)
priority. In the event of a power management issue, inline power to critical ports is maintained as long as possible.
Capacitor Detection Method

By default, the PowerDsine capacitor detection method is disabled on an OmniSwitch 6400 Series switch.
To enable it, use the lanpower capacitor-detection command by entering lanpower capacitor-detection followed by the slot
number of the OmniSwitch 6400 Series and enable.
Note. The capacitive detection method should only be enabled to support legacy IP phones. This feature is not compatible
with IEEE specification 802.3af. Please contact your Alcatel-Lucent sales engineer or Customer Support representative to
find out which Alcatel-Lucent IP phones models need capacitive detection enabled.
Understanding Priority Disconnect

The priority disconnect function differs from the port priority function in that it applies only to the addition of powered
devices (PDs) in tight power budget conditions. Priority disconnect is used by the system software in determining whether
an incoming PD will be granted or denied power when there are too few watts remaining in the PoE power budget for an
additional device. For example, if there are only 2 watts available in the current PoE power budget and a user plugs a
3.5W powered device into a PoE port, the system software must determine whether the device will be powered on.
Based on priority disconnect rules, in some cases one or more existing devices may be powered down in order to
accommodate the incoming device. In other cases, the incoming device will be denied power.
Priority disconnect rules involve the port priority status of an incoming device (i.e., low, high, and critical), as well as the
ports physical port number (i.e., 124). Understanding priority disconnect rules is especially helpful in avoiding power
budget deficits and the unintentional shutdown of mission-critical devices when PDs are being added in tight power
budget conditions.
Reminder. Priority disconnect applies only when there is inadequate power remaining in the power budget for an
incoming device. By default, priority disconnect is enabled in the switchs system software.
When priority disconnect is disabled and there is inadequate power in the budget for an additional device, 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., 124).
Alcatel.Lucent-ESD
Calabasas/CA./USA
Priority Disconnect is enabled; same Priority Level on All PD Ports

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 ports in the slot, the physical port number is
used to determine whether the incoming PD will be granted or denied power. Lower numbered ports receive higher priority
than higher-numbered ports. 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.
Priority Disconnect is enabled; Incoming PD Port has Highest Priority Level
When a PD is being connected to a port with a higher priority level than all other ports 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 ports 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 ports 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 ports, the high priority port with the highest physical port number
is automatically disconnected.
Priority Disconnect is enabled; Incoming PD Port has Lowest Priority Level
When a PD is being connected to a port with a lower priority level than all other ports in the slot, the incoming PD will be
denied power, regardless of its physical port number. Devices connected to other higher-priority ports will continue operating
without interruption.
Priority Disconnect is disabled
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., 124).
Monitoring Power over Ethernet via CLI

To monitor current PoE statistics and settings, use the show lanpower command. The command output displays a list of all
current PoE-capable ports, along with the following information for each port:
Maximum power allocated to the port, in Milliwatts
Actual power used by the port
Current port status
Power priority status
Power on/off status
Aggregate slot and chassis management information is also displayed. This information includes:
Maximum watts allocated to the corresponding slot
Amount of power budget remaining that can be allocated for PoE modules
Total amount of power remaining that can be allocated for additional switch functions
Alcatel.Lucent-ESD
Calabasas/CA./USA
Availability Feature
The switch provides a broad variety of availability features. 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 day-to-day 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 OmniSwitch 6400 Series switches 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).

The OmniSwitch 6400 Series switches support an optional backup power supply. This power supply is connected to the rear of
the unit. There is a power shelf provided with the unit that slides into the rear of the chassis and is used to hold the power
supplies. It can hold 510W or 360W power supplies (for PoE Models) and 120W DC or 126W AC power supplies (Non-PoE
Models).
This provides redundant chassis power on a 1:1 basis.
Backup power supplies operate in standby mode. If the primary power supply fails unexpectedly, the backup power supply
automatically takes up the full power load without disrupting the switch.
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 hardware components can be hot swapped:
Backup power supply
Backup power supply connector cables
SFPs
Alcatel.Lucent-ESD
Calabasas/CA./USA
Simplified Manageability
The OS6400s design provides all the benefits of managing a truly chassis-based switch including: simple and quick
software upgrades and switch configuration changes, single IP address for management, and a common look and feel with
the rest of the OmniSwitch solutions. The AOS-based OS6400 uses an intuitive CLI that is common across the
OmniSwitch line. A common and easy to use interface from the edge to the core can reduce total cost of ownership by
reducing training costs, simplifying and speeding up deployment, and making troubleshooting efforts more routine.
Following are the features on Simplified Manageabilty supported on OS6400:
Dual image and dual configuration file storage provides backup
Intuitive Alcatel-Lucent CLI with familiar interface reducing training costs
Extensive user manuals with examples
Easy to use, point-and-click web based element manager (WebView) with built-in help for easy configuration of
new technology features
Remote telnet management or secure shell access using SSH
Secured file upload using SFTP, or SCP
Human readable ASCII based config files for offline editing and bulk configuration
IGMPv1/v2/v3 snooping to optimize multicast traffic
BootP/DHCP client allows auto-config of switch IP information to simplify deployment
Auto-negotiating 10/100/1000 ports automatically configure port speed and duplex setting
Auto MDI/MDIX automatically configures transmit and receive signals to support straight through and crossover
cabling
DHCP relay to forward client requests to a DHCP server
SNMPv1/v2/v3
Integration with SNMP manager Alcatel-Lucent OmniVista for network wide management
Supports RFC 2819 RMON group (1-Statistics, 2-History, 3-Alarm & 9-Events)
Network Time Protocol (NTP) for network wide time synchronization
Alcatel-Lucent Mapping Adjacency Protocol (AMAP) for building topology maps within OmniVista
802.1AB Link Layer Discovery Protocol with MED extensions
Port-based mirroring for troubleshooting and lawful interception, supports four sessions with multiple sources-toone destination configuration
Policy based mirroring - Allows selection of the type of traffic to mirror by using QoS policies
Remote port mirroring
Port monitoring feature that allows capture of Ethernet packets to a file, or for on-screen display to assist in
troubleshooting
sFlow v5 support to monitor and effectively control and manage the network usage
Local (on the flash) and remote logging (Syslog)
GVRP for 802.1Q-compliant VLAN pruning and dynamic VLAN creation
Auto QoS for switch management traffic as well as traffic from Alcatel-Lucent IP phones
UDLD for detecting one way connections
Port based, port mirroring for troubleshooting and lawful interception, supporting four sessions with multiple
sources-to-one destination configuration
Port monitoring feature that allows capture of Ethernet packets to a file, or for on-screen display to assist in
troubleshooting
sFlow v5 support to monitor and effectively control and manage the network usage
Alcatel-Lucent Access Guardian and OmniVista 2770 Quarantine Manager

Alcatel-Lucents Access Guardian and OmniVista 2770 Quarantine Manager are secure network components of AlcatelLucents security framework for all of Alcatel-Lucents enterprise networking devices. This framework offers proactive
and reactive security solutions comprised of comprehensive switch-based security capabilities as well as integration with
security applications and appliances from industry leaders.
Alcatel.Lucent-ESD
Calabasas/CA./USA
Alcatel-Lucents Access Guardian is a feature set that enables network-wide and user-based security by automatically detecting and
authenticating the 802.1x and non-802.1x devices associated with a single port, in any combination. This provides users proactive
security by preventing unauthorized network access or restricted access for remediation. In addition to improved network security,
Alcatel-Lucents Access Guardian reduces to zero the time a network administrator spends for adding or moving users.
In addition to proactive security provided by Alcatel-Lucents Access Guardian, the Alcatel-Lucent OmniVista 2770
Quarantine Manager provides reactive security by using alerts from third-party intrusion detection and prevention systems
to identify malicious attacks and then swiftly handling them through automatic containment and remediation.
Alcatel-Lucent CrystalSec is the security framework and architecture for Alcatel-Lucents enterprise networking
devices. CrystalSec provides security that is extended to and deployed through a mixture of technologies, external
appliances and security functions from the network core to the edge. CrystalSec offers the best-in-class VLAN
classification capabilities (MAC, IP subnet, protocol, DHCP, ACLs) and provides plug-and-play security domains
ensuring automatic containment and remediation support. CrystalSec framework consists of network device
hardening for security by default, Access Guardian for proactive security, Alcatel-Lucent OmniVista 2770 Quarantine
manager for reactive security, secure network services to ensure high availability, security certifications of third
parties, and partnerships with leading security application providers such as Fortinet.
WebView
IT person have long ago abandoned web management because it was too slow, inefficient and incapable. WebView
updates happen instantly removing the biggest obstacle to simple fast management. Alcatel-Lucent WebView gives true
real-world capabilities back to web browser element management and allows an IT staff of varying capabilities to
quickly master and configure new features. The web interface provides point and click ease with quick access to help.
WebView is full-featured and can configure and manage all switch features.
CLI
The AOS-based OS6400 uses an intuitive CLI that is common across the OmniSwitch line. A common and easy to use
interface from the edge to the core can reduce total cost of ownership by reducing training costs, simplifying and speeding
up deployment, and making troubleshooting efforts more routine.
Alcatel.Lucent-ESD
Calabasas/CA./USA
MTBF Calculation Standards and Requirements

MTBF Notes:
One MTBF-Yr. = 8,760 MTBF-Hrs.
MTBF Prediction was based on Bellcore Handbook Technical Reference TR-332, Issue 6, Method I, and Case 3.
M.S.R. 5: Mission Success Rate (%) for 5 years (43,800 Hours) without failure.
M.S.R. 1: Mission Success Rate (%) for 1 year (8,760 Hours) without failure.
All MTBF calculations are performed at 25C Ground Benign
1. PURPOSE
The purpose of this section is to specify the basic standards and requirements for the MTBF calculations of all the
products of Alcatels Network Infrastructure Business Unit (NIBU).
2. RELIABILITY PREDICTION
A reliability prediction is simply the analysis of parts and components in an effort to predict and calculate the rate at which
an item will fail. Reliability predictions provide a quantitative basic for evaluating product reliability. A reliability
prediction is one of the most common forms of reliability analyses for calculating failure rate and MTBF.
3. MTBF DEFINITION
There are many forms of the MTBF definition. In general, MTBF (Mean Time Between Failures) is the mean value of the
lengths of time between consecutive failures, under stated conditions, for a stated period in the life of a functional unit. A
more simplified MTBF definition for reliability predictions can be stated as the average time (usually expressed in hours)
that a component works without failure.
3.1 Limitations of Reliability Prediction
Like all engineering models, the failure rate models that used for MTBF calculations, are approximations to reality. Thus,
one should not treat a reliability prediction number for a product as an absolute prediction of its field failure rate. In
general, higher MTBF correlates with fewer component failures, but an MTBF claim is not a guarantee of product
reliability and does not represent a condition of warranty. It is generally agreed that these predictions can be very good
when used for relative comparisons, such as comparing design alternatives, or comparing products. Note also that
reliability predictions do not account for substandard quality control for purchased parts, bad workmanship, poor product
level quality control, overstressed field operation, etc.
4. MTBF CALCULATION STANDARDS
The two most popular MTBF calculation standards are Telcordia (Bellcore) and MIL-HDBK-217.
The MTBF calculations of all the NIBU products, even for the industrial and military specifications products, are based on
the Telcordia standard document number SR-332, Issue 1 (which is an update of the Bellcore Handbook Technical
Reference TR-332, Issue 6), since the Telcordia models are specifically designed and oriented to focus on the
telecommunications products.
Furthermore, the Telcordia models are also widely accepted in the telecom market; they seem to give much more realistic
results; they are much more up to date; they can handle larger gate count ICs much better; they are quicker and easier to
use, since the Telcordia models require many less part parameters than the MIL-HDBK-217 models.
Alcatel.Lucent-ESD
Calabasas/CA./USA
5. MTBF CALCULATION REQUIREMENTS

5.1 Bill of Materials
The Bill of Materials (BOMs) is normally used to calculate the MTBFs of all the NIBU products.
5.2 MTBF Calculations
MTBF is a basic measure of reliability for repairable items. It can be described as the number of hours that pass before a
component, assembly, or system fails. It is a commonly-used variable in reliability and maintainability analyses.
MTBF can be calculated as the inverse of the failure rate for constant failure rate systems. For
Example: If a component has a failure rate of 2 failures per million hours, the MTBF would be the inverse of that failure rate:
MTBF = (1,000,000 hours) / (2 failures/million hours) = 500,000 hours
Thus, for an assembly with multiple components, the MTBF is calculated as the inverse of all the failure rates, as follows:
MTBF = 1 / (sum of all the part failure rates); or:
MTBF = 1 / (FR1 + FR2 + FR3 + ............ FRn)
Note: FR = Failure Rate
For a combination of multiple assemblies in Serial Mode:
MTBF (Combined) = 1 (1/MTBF1 + 1/MTBF2 + 1/MTBF3 + ..+1/MTBFn)
To ease the complexity of the MTBF calculations, a reliability prediction program called RelCalc for Windows, Version 5.0BELL7 (Release 2004.1), produced by T-Cubed Systems, Inc. (http://www.t-cubed.com/), is used to calculate the MTBFs of all
the NIBU products, with Telcordia SR-332, Issue 1, Method I (Parts Count), Case 3, Environment GB (Ground Benign),
Correction Factor 1, 100% Duty Cycle, components Quality Level II and under an ambient temperature of 25C.
5.3 Minimum MTBF Expectation
The minimum MTBF value for all NIBU products, including any module, unit or system is expected to be 43,800 hours (5 years).
Thus:
The minimum Mission Success Rate for 1 year (M.S.R. 1) = exp (-8760/43800) = 81.87%
The minimum Mission Success Rate for 5 years (M.S.R. 5) = exp (-43800/43800) = 36.79%
5.4 MTBF Calculation Results
A so called MTBF table is used to summarize the MTBF calculation results of all products. The MTBF table is periodically
updated to include the additional MTBF calculation results of new products. After each update, it will be sent out to interested
parties such as Engineering, Quality Assurance, Marketing and Sales departments. Beside the MTBF calculation results of each
product, the MTBF table also displays other results such as backplanes, fans, power supplies, PCBAs, fiber optic transceivers,
products with and without power supplies, products with and without fiber optic transceivers.
6. Additional Information
6.1 The History of the MTBF Standards
For electronic components, the two most popular and widely accepted reliability prediction handbooks are MIL-HDBK-217 and
Telcordia (Bellcore). These handbooks offer procedures for predicting electronic product reliability, providing a standard basis for
comparing reliability numbers.
6.2 MIL-HDBK-217
The original reliability prediction handbook was MIL-HDBK-217, the Military Handbook for Reliability Prediction of
Electronic Equipment. MIL-HDBK-217 (commonly referred to as 217) is published by the Department of Defense, based on
work done by the Reliability Analysis Center and Rome Laboratory at Griffiss AFB, NY.
The 217 handbook contains failure rate models for the various part types used in electronic systems, such as ICs, transistors,
diodes, resistors, capacitors, relays, switches and connectors.
These failure rate models are based on the best field data that could be obtained for a wide variety of parts and systems; this data
is then analyzed and massaged, with many simplifying assumptions thrown in, to create usable models.
The latest version of 217 is MIL-HDBK-217F, Notice 2 (217F2). A copy of MIL-HDBK-217F-2 can be obtained from any source
that provides Mil Specs, Mil Standards, Mil Handbooks, etc.
Alcatel.Lucent-ESD
Calabasas/CA./USA
6.3 Telcordia (Bellcore)

Bellcore was purchased by SAIC in 1997. The purchase agreement required Bellcore to change its name: Bellcore became
Telcordia Technologies in 1999. However, people still continue to use the Bellcore name in their documentation. Note that
Bellcore (Bell Communications Research, a spin-off of AT&T Bell Labs) was the research arm of the Bell Operating Companies.
Bellcore previously used MIL-HDBK-217 for their reliability predictions, but found that 217 gave pessimistic numbers for its
commercial quality products. A few years ago, Bellcore used 217 as a starting point, modified (and simplified) the models to
better reflect their field experience, and developed the Bellcore reliability prediction procedure, which is applicable to commercial
electronic products. A copy of the Telcordia document Reliability Prediction Procedure for Electronic Equipment (document
number SR-332, Issue 1) can be obtained directly from Telcordia Customer Service in New Jersey.
Many commercial electronic product companies, making products such as computers, telecommunications systems, medical
systems, and power supplies, are now choosing to use the Bellcore handbook for their reliability predictions.
6.4 Failure Rate Unit Conversions
Failure rate numbers can be expressed in many different units as shown in the following conversion equations.
Note that the FITs (Failures In Time) unit is failures per billion hours, and that the MTBF is in hours.
(Failures/million hours) = (1,000,000) / (MTBF)
(Failures/million hours) = (0.001) * (FITs)
(Failures/million hours) = (1000) * (failures/1000 hours)
(Failures/million hours) = (10) * (%failures/1000 hours)
(Failures/million hours) = (114.2) * (failures/year)
(Failures/million hours) = (1.142) * (%failures/year)
(FITs) = (1,000,000,000) / (MTBF)
(FITs) = (1000) * (failures/million hours)
(FITs) = (1,000,000) * (failures/1000 hours)
(FITs) = (10,000) * (%failures/1000 hours)
(FITs) = (114,200) * (failures/year)
(FITs) = (1142) * (%failures/year)
(MTBF) = (1,000,000) / (failures/million hours)
(MTBF) = (1,000,000,000) / (FITs)
6.5 MTBF Mission Success Rate
The Mission Success Rate (M.S.R.) is the probability that the circuit, including redundancy, will operate without failure for the
mission time. For example, if the Mission Success Rate = 0.999405, then the circuit has a probability of 99.94% of working
without a failure for the mission time duration.
Assuming that failures occur randomly during the useful life of a product, they can be described as an exponential distribution. So
the probability that a product will work for some time T without failure is given by:
R (T) = exp (-T/MTBF)
Thus, for a product with an MTBF of 250,000 hours, and an operating time of interest of 5 years (43,800 hours):
R = exp (-43800/250000) = 0.839289 = 83.93% (Mission Success Rate for 5 years = 83.93%)
This means that there is an 83.93% probability that the product will operate for the 5 years without a failure, or that 83.93% of the
units in the field will still be working at the 5 year point.
6.6 Serial and Parallel Mode MTBF Calculations
The following two typical model types are used to calculate the MTBFs of all the NIBU products:
Serial Mode MTBF Calculation
Parallel Mode MTBF Calculation
Alcatel.Lucent-ESD
Calabasas/CA./USA
6.6.1 Serial Mode MTBF Calculation

The MTBF calculation under serial mode requires all of the parts in the circuit to function for success. In other words, the whole
assembly will be considered failed if only one single component failed. Under serial mode MTBF calculation, the MTBF
calculation result usually goes lower with additional components. The serial mode is normally used to calculate the
MTBFs of all the modules and systems, except redundancy configurations, with the following formula:
MTBF (Combined) = 1 (1/MTBF1 + 1/MTBF2 + 1/MTBF3 ++ 1/MTBFn)
6.6.2 Parallel Mode MTBF Calculation
The MTBF calculation under parallel mode requires only 1 of the parts in the circuit to function for success. The parallel mode is
usually used to calculate the MTBFs of the units in redundancy mode, such as redundant power supplies or redundant chassis
management modules (CMMs). Under parallel mode MTBF calculation, the MTBF calculation result usually goes higher with
additional redundant units. There is no simple formula to calculate the MTBFs of the redundant modules or systems under parallel
mode. A reliability prediction program such as RelCalc for Windows is used instead to perform the MTBF calculations under
parallel mode.
6.7 MTBF and Other Related Terms
6.7.1 MTTF
MTTF (Mean Time to Failures) is a basic measure of reliability for non-repairable systems items (such as fans). It is the mean
time expected until the first failure of a piece of equipment. MTTF is a statistical value and is meant to be the mean over a long
period of time and a large number of units. For constant failure rate systems, MTTF is the inverse of the failure rate. If the
failure rate is in failures/millions of failure hours, MTTF = 1,000,000/Failure Rate for components with exponential distributions.
Technically, MTBF should be used only in reference to repairable items, while MTTF should be used for non-repairable items.
However, MTBF is commonly used for both repairable and non-repairable items. The MTBF figures can be used for this purpose.
MTTF = 1 / (sum of all the part failure rates); or:
MTTF = 1 / (FR1 + FR2 + FR3 + ............ FRn)
Note: FR = Failure Rate
MTTF = (1,000,000) / (failures/million hours)
6.7.2 MTTR (Mean Time to Repairs) for our systems depends on the failure. Our systems are designed to recover from simple
failures, but our systems engineers can help our customers develop a fault tolerant network that would use a combination of local
spares, distributed inventories and advanced replacements to optimize the availability rating.
Alcatel.Lucent-ESD
Calabasas/CA./USA
6.7.3 Availability Calculations

Availability (Ai) is the probability that the system will be available when required, or the proportion of total time that the system
is available for use. If the repair time is very small compared to the MTBF time, then the availability of the system can approach
to 100%. Availability is typically specified in nines notation. For example: 3-nines availability corresponds to 99.9% availability.
5-nines availability corresponds to 99.999% availability.
The following table shows the relationship of the availability and the corresponding percentage and downtime:
Availability
1-nine
2-nines
3-nines
4-nines
5-nines
6-nines
Availability Percentage
90%
99%
99.9%
99.99%
99.999%
99.9999%
Down Time per Year

36.5 days/year
3.65 days/year
8.76 hours/year
52.56 minutes/year
5.26 minutes/year
31.54 seconds/year
The Availability can be calculated as:

Ai = MTBF / (MTBF + MTTR)
MTTR = Mean Time To Repair (average service or repair time in hours)
Example:
With MTBF = 100,000 hours and MTTR = 4 hours
Ai = 100000 / (100000 + 4) = 0.999960001 99.99% (4-nines availability)
With MTBF = 500,000 hours and MTTR = 4 hours
Ai = 500000 / (500000 + 4) = 0.999992 99.999% (5-nines availability)
Availability is calculated as: MTTF / (MTTF + MTTR) or MTBF / (MTBF + MTTR)
Comment on 4 x 9s availability or 99.99% uptime carrier grade availability (Availability in % (ex: 100.00%)):
To achieve the highest levels of availability there must be cooperative efforts between Alcatel-Lucent and the customer, this
requires that in addition to device and network level capabilities, operational processes must also be in place across the many
facets of the network hardware, software, applications, security, networking, backup systems, local spares and server farms.
Network management must be designed to maintain availability with automated features to prevent and resolve problems, and
incorporate security with ease of use to reduce human error and the associated downtime.
6.7.4 Spare Units Calculations
The Mission Success Rate (M.S.R.) calculation should be used to determine the spare units that a customer should acquire:
M.S.R (T) = exp (-T/MTBF)
Example:
With 100 units that had an MTBF = 100,000 hours
M.S.R. for 1 year (8,760 hours) = exp (-8760/100000) = 91.61% 92%
M.S.R. for 5 years (43,800 hours) = exp (-43800/100000) = 64.53% 65%
This means that at the end of the first year, there is a probability that 92 units are still running with 8 units failed. Thus, the
customer needs to acquire about 8 spare units for the first year.
At the end of the 5th year, there is a probability that 65 units are still running with 35 units failed.
Thus, the customer needs to get about 35 units for their replacement.
However, some people prefer to use the following simpler method to calculate the spare units as an estimation figure:
Spare units in a period = (number of units) * (period in hours) / (MTBF in hours)
Example:
With 100 units that had an MTBF = 100,000 hours
Spare units in 1 year (8760 hours) = (100 units) * (8760 hours) / 100000 hours = 8.76 units 9 units
Spare units in 5 years (43,800 hours) = (100 units) * (43800 hours) / 100000 hours = 43.80 units 44 units
Alcatel.Lucent-ESD
Calabasas/CA./USA
Alcatel.Lucent-ESD
Calabasas/CA./USA
MTBF Values for OS6400
Family
Module Name
MTBF-Hr.
MTBF-Yr.
Failure
Rate
OS6400-24
OS6400-24-System
OS6400-24-Power
OS6400-24-Fan
OS6400-24-LED/USB Daughter
OS6400-24-Main Board
187,933
400,000
2,561,265
30,406,453
417,061
21.45
45.66
292.38
3471.06
47.61
5321.0
2,500.0
390.5
32.8
2397.7
OS6400-P24
OS6400-P24-System
OS6400-P24-Power
OS6400-P24-Fan
OS6400-P24-LED/USB Daughter
OS6400-P24-PoE Daughter
OS6400-P24-Main Board
149,166
300,000
2,561,265
34,148,018
4,318,553
367,740
17.03
34.25
292.38
3898.18
492.99
41.98
6703.9
3333.3
390.5
29.3
231.6
2719.3
OS6400-U24
OS6400-U24-System
OS6400-U24-Power
OS6400-U24-Fan
OS6400-U24-LED/USB Daughter
OS6400-U24-SFP Daughter Board
OS6400-U24-Main Board
189,983
400,000
2,561,265
30,406,453
2,172,382
531,919
21.69
45.66
292.38
3471.06
247.99
60.72
5263.6
2,500.0
390.5
32.8
460.3
1879.9
OS6400-U24D
OS6400-U24D-System
OS6400-U24D-Power
OS6400-U24D-Fan
OS6400-U24D-LED/USB Daughter
OS6400-U24D-SFP Daughter Board
OS6400-U24D-Main Board
424,657
400,000
2,561,265
30,406,453
2,172,382
537,164
48.48
45.66
292.38
3471.06
247.99
61.32
2354.8
2,500.0
390.5
32.8
460.3
1861.3
OS6400-48
OS6400-48-System
OS6400-48-Power
OS6400-48-Fan
158,837
400,000
3,130,434
30,406,453
265,937
18.13
45.66
357.36
3471.06
30.36
6612.6
2,500.0
319.4
32.8
3760.2
OS6400-P48
OS6400-P48-System
OS6400-48-Power
OS6400-48-Fan
OS6400-48-PoE Board
158,837
300,000
3,221,188
29,554,286
3,100,790
177,652
18.13
34.25
367.72
3373.78
353.97
20.28
6295.7
3333.3
310.4
33.8
322.5
5628.9
Alcatel.Lucent-ESD
Calabasas/CA./USA
OmniSwitch 6400 Series Hardware & Software Features Overview Table

C
C
T
Chhhaaassssssiiisss T
Teeeccchhhnnniiicccaaalll SSSpppeeeccciiifffiiicccaaatttiiiooonnnsss
Note: 1 inch = 2.54 centimeters & One Rack Unit = 1.75" & 1 kg = 2.2046 lbs & 1 watt 3.41214 BTU/hr.
Indicators /LEDs
LED per port:
10/100/1000: PoE, link/activity
SFP: link/activity
Stacking: link/activity
System LEDs:
Switch ID (indicates the stack ID of the unit in the stack: 1 to 7)
System (OK) (chassis HW/SW status)
PWR (primary power supply status)
PRI (virtual chassis primary)
BPS (backup power status)
Rack Mountable
OmniSwitch-6400 is rack mountable in 19 (W) racks (19" Rack-Mountable)
Physical Dimensions (W x D x H)
Chassis Size (without mounting brackets)
24 port Non-PoE and Fiber with internal power supply
17.32 x 10.63 x 1.73 in (44.0 x 27.0 x 4.4 cm)
The OS6400 Series chassis are 1U
(One Rack Unit)
48 port Non-PoE with internal power supply
17.32 x 13.00 x 1.73 in (44.0 x 33.0 x 4.4 cm)
24 port PoE without power shelf
17.32 x 10.63 x 1.73 in (44.0 x 27.0 x 4.4 cm)
48 port PoE without power shelf
17.32 x 10.63 x 1.73 in (44.0 x 27.0 x 4.4 cm)
Total sizes including power supply shelf for PoE and backup supply
17.32 x 17.56 x 1.73 in (48.2 x 44.6 x 4.4 cm) for 10.63 inch chassis
17.32 x 19.93 x 1.73 in (48.2 x 50.6 x 4.4 cm) for 13.00 inch chassis
Weights
CHASSIS
Non-PoE with internal supply
OS6400-24 9.43 lbs (4.28kg)
OS6400-48 11.97 lbs (5.42 kg)
OS6400-U24 9.76 lbs (4.43 kg)
OS6400-U24D 9.23 lbs (4.18 kg)
PoE models without supply
OS6400-P24 8.97 lbs (4.07 kg)
OS6400-P48 9.92 lbs (4.50 kg)
POWER SUPPLIES
OS6400-BP 126W AC 2.45 lb (1.11 kg)
OS6400-BP-D 120W DC 2.09 lb (0.95 kg)
OS6400-BP-P 360W AC 3.22 lb (1.46 kg)
OS6400-BP-PH 510W AC 5.71 lb (2.59 kg)
Power shelf 1.26 lb (0.57 kg )
Alcatel.Lucent-ESD
Calabasas/CA./USA
Maximum Power Consumption

The OmniSwitch 6400 Series
Maximum Power Consumption for the Non-PoE Models:

OS6400-24: 52
OS6400-48: 79
OS6400-U24: 80
OS6400-U24D: 80
Maximum Power Consumption for the PoE Models:
OS6400-P24: 69 (330)
OS6400-P48: 103 (330)
Heat Dissipation
The OmniSwitch 6400 Series
Notes: The power consumption measurements were obtained under fully loaded conditions.
Power consumption calculations are based on total power drawn from the AC line, in other words, the
Input Power = Output Power / Power Supply efficiency.
Chassis Pwr Consumption = Chassis Pwr / PS efficiency
1-watt 3.41214 BTU/hr.
Maximum Heat Dissipation for the Non-PoE Models:
OS6400-24: 180
OS6400-48: 269
OS6400-U24: 272
OS6400-U24D: 272
Maximum Heat Dissipation for the PoE Models:
OS6400-P24: 235 (1126)
OS6400-P48: 351 (1126)
Note: To calculate the heat dissipation for the PoE Models the following formula has been used:
Heat Dissipation = (Chassis Power Consumption / PS efficiency + Estimated power required to power
the PoE daughter card / PS efficiency) x 3.41214BTU/hr.
The reason that the PoE power budget has not been fully taken into account here, is that the heat is
dissipated on the PoE devices and not on the OmniSwitch 6400 chassis. Therefore, we only account for
the heat dissipated on the OmniSwitch 6400 chassis plus the heat dissipated on the PoE daughter card
inside the chassis including the P/S efficiency.
Alcatel.Lucent-ESD
Calabasas/CA./USA
Power Supply Requirements

Power Supply Requirements
PoE Power availability
Chassis Air-Flow
Power plug type
Electrical Requirements
Name Plates
Acoustic Noise level
OS6400-24, OS6400-48 & OS6400-U24 comes with Internal AC power supply (90-220V AC), where
as OS6400-U24D comes with Internal DC power supply (36-72V DC).
OS6400-P24 & OS6400-P48 which are PoE models comes with 360W AC or 510W AC power
supplies.
OS6400 Series Supports redundant hot swappable power supplies. Following are the Backup
Power Supplies supported:
OS6400-BP: AC 126 W Backup Power Supply
OS6400-BP-D: DC 126 W Backup Power Supply
OS6400-BP-P: Standard PoE 360W Backup Power Supply
OS6400-BP-PH: High PoE 510W Backup Power Supply

Notes:
For Non-PoE models, it uses internal main power supplies and external backup power
supplies directly connected to the rear of the unit or remotely mounted.
For Non-PoE models, Backup power supplies use a power shelf to hold one 6400-BP (AC)
or one 6400-BP-D (DC) supply.
For PoE models, Power shelf holds one 510W AC, or two 360W AC power supplies.
A shelf and a remote cable is provided within the shipping box to rack a power supply on
top of the unit
Remotely connected power supply allows for smaller depth space requirement.
The OS6400 product family Backup Power Supplies cannot be used for the OS68xx
product family and vice-versa.
The chassis P/S fail-over to the backup P/S is transparent to the users and without a reboot
of the switch. The fail-over time is negligible.
OS6400-P24 & OS6400-P48 are the models on which PoE capability is supported.
360W (AC) and 510W (AC) power supplies are supposed to be used with PoE models.
Note: Power for all POE ports is defaulted to 15.4 watts per port and each port is configurable between
3watts to 15.4watts (Port setting is in Milliwatts (3000 to 15400)). Please note that the available PoE
power budget must not be exceeded.
Chassis Airflow: The fans pull air from the air intake vent located on the left-hand side of the chassis.
The air is directed horizontally through the chassis and past the circuit board. Airflow is then
exhausted through the fan vents at the right-hand side of the chassis.
Important. Maintain a clearance of at least two inches at the left and right sides. Otherwise, airflow
can become restricted. Restricted airflow can cause your switch to overheat; overheating can lead to
switch failure.
North America: NEMA 5-15-P (US), C22.2, No. 42 (Canada)
United Kingdom / Ireland: BS 1,363, Europe: CEE 7/7
Japan: JIS 8,303, Australia: AS 3,112, India: BS 546, Italy: CIE 2,316
Switzerland / Liechtenstein: SEV 1011
Denmark / Greenland: SRAF 1,962 / D816 / 87, Argentina: AR1-10P
OmniSwitch 6400 switches have the following general electrical requirements:
Each switch requires one grounded electrical outlet for each power supply installed in the.
OmniSwitch 6400 switches offer both AC and DC power supply support.
Refer to the Hardware Users Guide for more information.
For switches using AC power connections, each supplied AC power cord is 2 meters (approximately
6. 5 feet) long. Do not use extension cords.
Redundant AC Power: If possible, it is recommended that each AC outlet reside on a separate circuit.
With redundant AC, if a single circuit fails, the switchs remaining power supplies (on separate
circuits) will likely be unaffected and can therefore continue operating.
For switches using DC power, the user must assemble the DC power cord. Refer to the Hardware
Users Guide for more information.
A nameplate in the front of the chassis will identify the product model name & number and the vendor
(in this case Alcatel-Lucent).
A nameplate in the back will clearly identify the following:
Model #, Assembly # with BAR CODE, and FCC statements
Electric Ratings and U.S. Patent information along with their respective symbols.
PoE Models:
OS6400-P24: under 44dB
OS6400-P48: under 44dB
Non-POE Models:
OS6400-24: under 40dB
Alcatel.Lucent-ESD
Calabasas/CA./USA
OS6400-48: under 40dB

OS6400-U24: under 40dB
OS6400-U24D: under 40dB
Emissions (EMC) & Immunity Compliance
Safety Agency Certifications
Metro Ethernet Forum (MEF) 9 and 14 certification
FCC CRF Title 47 Subpart B (Class A limits. Note: Class A with UTP cables)
VCCI (Class A limits. Note: Class A with UTP cables)
AS/NZS 3548 (Class A limits. Note: Class A with UTP cables)
CE marking for European countries (Class A Note: Class A with UTP cables)
EN 55022: 1995 (Emission Standard)
EN 61000-3-3: 1995
EN 61000-3-2: 2000
EN 55024: 1998 (Immunity Standards)
EN 61000-4-2: 1995+A1: 1998
EN 61000-4-3: 1996+A1: 1998
EN 61000-4-4: 1995
EN 61000-4-5: 1995
EN 61000-4-6: 1996
EN 61000-4-8: 1994
EN 61000-4-11: 1994
IEEE802.3: Hi-Pot Test (2250 VDC on all Ethernet ports)
US UL 60950
IEC 60950-1:2001; all national deviations
EN 60950-1: 2001; all deviations
CAN/CSA-C22.2 No. 60950-1-03
NOM-019 SCFI, Mexico
AS/NZ TS-001 and 60950:2000, Australia
UL-AR, Argentina
UL-GS Mark, Germany
EN 60825-1 Laser, EN60825-2 Laser
CDRH Laser
China CCC
Alcatel-Lucent is pleased to announce that both the Alcatel-Lucent OmniSwitch 6400 Stackable
LAN switch and the Alcatel-Lucent OmniSwitch 9000 Chassis LAN switch are now Metro Ethernet
Forum (MEF) 9 and 14 certified.
MEF benefits for Alcatel-Lucent
MEF certification strengthens LAN product positioning in Metro Access deployments for residential
and business Ethernet services where the OmniSwitch 6400 and OmniSwitch 9000 switches are used
as customer premises equipment (CPE) in single or multi-tenant unit (STU/MTU) installations.
With this certification, Alcatel-Lucent now offers a fully MEF compliant end-to-end solution for
Ethernet services based on LAN OmniSwitch switches and MPLS Service Routers (7710, 7750, 7450).
What is MEF and what does it mean to be MEF certified?
The Metro Ethernet Forum (MEF) is a global industry alliance comprising more than 120
organizations whose mission is to accelerate the worldwide adoption of carrier-class Ethernet networks
and services. The alliance members develop technical specifications and implementation agreements to
promote interoperability and deployment of carrier Ethernet worldwide.
Test certifications obtained while running on the Alcatel-Lucent Operating System (AOS) version
6.3.1.R01 were:
1. MEF 9 for equipment vendors Ethernet services at the user network interface (UNI)
2. MEF 14 for equipment vendors focused on traffic management, service performance, and quality
of service (QoS)
Certifications tests indicate that the OmniSwitch 6400 and 9000 meet the carrier-class standard for
Ethernet Private Line (EPL), Ethernet Virtual Private Line (EVPL), and Ethernet LAN (E-LAN)
services at the UNI.
Service providers benefit from this certification because it:
Provides immediate assurance that the vendors equipment complies with MEF specifications
Saves money and time on complex testing between vendors, especially on global accounts
Establishes a solid foundation for carrier Ethernet ubiquity and interoperability
Alcatel.Lucent-ESD
Calabasas/CA./USA
JATE
Reliability Tests
Compliancy
RoHS Requirements
RoHS
Restriction on Hazardous Substances
EU Council Decision 87/95/EEC

WEEE
NEBS-Level-3
Electrical Compliance
Electrostatic Discharge (ESD)
ISO-9001:2000 DNV Certification
Capability Maturity Model (CMM)
Mean Time Between Failure (MTBF) Standard
Quality Assurance and Customer Satisfaction
This equipment meets the requirements of the Japan Approvals Institute of Telecommunications
Equipment (JATE).
The OmniSwitch 6400 Series has been rigorously tested for:
Temperature
Humidity
Vibrations
Acoustic Noise
Altitude
Drop
Shock
Bench Handling
Please contact Alcatel-Lucent Internetworking Product Marketing and/or other Alcatel-Lucent
authorized representatives to obtain further data and/or a full test report.
1) RoHS-Alcatel's OmniSwitch 6400 family is among the first hardware to be in compliance with the
new European Community's directive Restriction on Hazardous Substances in Electrical and
Electronic Equipment (RoHS)
2) WEEE (Waste Electrical and Electronic Equipment)
3) NEBS Level 3 Certified All of the models
It is Alcatel-Lucent's position to be in compliance with the European R.O.H.S Directive 2002/95/EC
by the end of 2005. In doing so, all component selection decisions shall be influenced by offerings that
are a) ROHS compliant today or b) have planned date of cutover to ROHS compliance without
impacting the design (i.e. causing a redesign). It is Alcatel-Lucent's intention to choose
environmentally friendly component finishes that are today solder-able with SN63/Pb37 solders
(through late 2005), but can move to SnAgCu chemistries in Jan2006.
Compliance with Environmental procedure 020499-00, primarily focused on Restriction of Hazardous
Substances (ROHS Directive 2002/95/EC) and Waste Electrical and Electronic Equipment (WEEE
Directive 2002/96/EC).
Thus, all assemblies built after Dec. 31, 2005 shall be compliant with hazardous materials
requirements as defined in 020499-00. Upon request, documentation shall be provided certifying
compliance.
First Green switch in the Market RoHS compliancy
With the OmniSwitch 6400 family, Alcatel-Lucent will be the first switch manufacturer to be in
compliance with the new European Communitys directive Restriction on Hazardous Substances in
Electrical and Electronics Equipment (RoHS) which requires electric equipment to be free of six
hazardous substances by July 2006. Although, only required for European Union countries, the rest of
the World will benefit from these green switches by lessening the amount of hazardous substances
that find its way into the environment.
Compliance with regulation given in:
http://europa.eu.int/ISPO/infosoc/legreg/docs/8795eec.html
The product at end of life is subject to separate collection and treatment in the EU Member States,
Norway and Switzerland. 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).
NEBS Level-3 Certified All of the OmniSwitch 6400 models supports NEBS Level-3.
The Electrical Compliance requirements are met through the EMC Compliance Standards and the
Safety Compliance Standards as indicated above.
The chassis has been thoroughly tested to withstand ESD test voltage conditions at any point on the
enclosure using the test setups and conditions in accordance with IEC 61000-4-2 (EN61000-4-2).
The OmniSwitch 6400 is compliant with the ISO-9001: 2000 DNV
Alcatel-Lucent's Software Engineering Institute (SEI) Capability Maturity Model (CMM) rating for
software processes meets the Level-2 (CMM-level-2) requirements.
All AOS OmniSwitches support a commercial equivalent of MIL-HDBK-217F-2:
MTBF Predictions are based on Telcordia (Bellcore Handbook Technical Reference) SR-332, Issue 1.
It is the policy of Alcatel-Lucent USA to satisfy the Quality expectations of our customers both
internal and external. Total Quality performance means understanding who the customer is, what the
customer expectations are, and meeting those expectations without error, on time, every time. Total
Quality is doing the right things right today and better tomorrow.
As part of Alcatels overall Quality Assurance process Alcatels Cross-functional team continuously
evaluates Cost, Time to Market, Communication, Customer satisfaction and Process improvements.
Necessary and appropriate actions are subsequently taken as required.
Alcatel-Lucent's Enterprise Solutions Division adheres to the ISO 9001 certification program. It
measures Customer Satisfaction and Key Process Indicators that are reviewed on regular intervals with
the Executive Management Team.
Alcatel.Lucent-ESD
Calabasas/CA./USA
OS6400 chassis Temperature Requirements

Note: the switch must be operated normally at
Operating temperature: 0 C to 45 C
Temperature Sensors
Brownout/Blackout Tolerance or P/S Holt-up Time
HVAC (Heating, Ventilation, Air Conditioning)

Humidity
Altitude
Shock
Vibration: operating
Vibration: non-operating
The installation site must maintain a temperature between 0 and 45 C (32 and 113 F) and not
exceed 95 percent maximum humidity (non-condensing) at any time.
Standard ambient (outside environment or outside the chassis) operating temperature: 0 C to 45 C
Storage Temperature: -40 F to 167 F (-40C to 75C)
The Show Temperature command displays the current operating chassis ambient temperature, as
well as current temperature threshold settings for each of the modules in the stack.
In over-threshold temperature situations, the switch immediately sends a trap to the user.
Temperature errors LED is also provided in the front panel.
Temperature Sensor National Semi-Conductor LM77
The so-called brownout/blackout tolerance is what we call Power Supply Holdup Time:
The Holdup time across all switching and routing platforms power supplies is guaranteed to be:
20ms per each P/S at 100% load. Depending on the load and the input voltage, the holdup time can be
as high as 120ms to 280ms.
For RFP purposes please provide the Heat Dissipation (BTUs), Temperature, Fans and Chassis Air
Flow information as described elsewhere in this table.
Operating: 5% to 90% Relative Humidity (Non-condensing)
Storage: 0% to 95% Relative Humidity (Non-condensing)
Operating altitude: sea level at 40 degrees Celsius and 10000 feet at 0 degrees Celsius
Storage altitude: sea level at 40000 feet
Packed drop test: per MIL-STD-810 method 516.3 procedure IV from height of 30", one drop on each
side, no drop test at 4 corners is required;
Unpacked: 30G, 1/2 Sine, 11ms, 3 shocks in each direction along the 3 mutually perpendicular axes
(18 shocks total);
Unpacked bench handling: per MIL-STD-810 method 516.3 IV. Using one edge as pivot, lift the
opposite edge until one of the following occurs:
a) Chassis forms 45 angle with horizontal bench top.
b) Lifted edge is raised 4" above horizontal bench top.
c) Lifted edge is just below point of perfect balance.
Let chassis drop freely. Repeat using other practical edges of same horizontal face as pivot points for a
total of 4 drops. Repeat on other faces for a total of 4 times on each face, which the chassis could be
placed on practically during servicing.
0.25G, Sine, 5-500-5 Hz, maximum displacement of 0.060 inches, 1 octave/minute in its 3 mutually
perpendicular axes. Testing shall be repeated 4 times for each axis.
Packed: 1.6G, Sine, 5-500-5 Hz, maximum displacement of 0.060 inches, 1 octave/minute in its 3
mutually perpendicular axes. Testing shall be repeated 4 times for each axis;
Packed random: per Mil-Std-810, Category 1, Basic Transportation, 60 min. duration with vibration
level based on Fig. 514.3-1 through Fig. 514.3-3 in its 3 mutually perpendicular axes.
Service & Support

Default Warranty
Limited Lifetime Warranty
Warranty
Service & Support Programs & End Of Life
Lifetime Support
One year on Hardware, and 90-days on Software. Additional, optional support is available. Contact
your local Alcatel-Lucent representative for more information.
All versions of the Omni Stackable family come with a Limited Lifetime Hardware Warranty, limited
to the original owner, and will be provided for up to five (5) years. Faulty parts will be replaced via a
five (5) business days AVR (Advance Replacement) RMA.
Limited Lifetime Warranty does not apply to transceivers.
Standard Warranty Support
All Alcatel-Lucent's products come with a standard one-year warranty on hardware and a three-month
warranty on software.
Hardware DOA Warranty
If hardware fails within the first 30 days after delivery, call Alcatel-Lucent's Internetworking Division
Alcatel.Lucent-ESD
Calabasas/CA./USA
Hardware Warranty
Software Warranty
Life Span
Contracted S&S Programs:

Standard extended warranty offerings including
technical and maintenance support
Contracted Program: SupportBasic
Contracted Program: SupportPlus
Contracted Program: SupportTotal
(available only in N. America)
Customer Service by 2:00 p.m. (Pacific Standard Time) and they will send a replacement part
overnight.
One-year Hardware Warranty
After the first 30 days, call Alcatel-Lucent's Internetworking Division Customer Service for a Return
material Authorization (RMA) and ship the part back to them for factory repair. The repaired unit will
be shipped back to you from our facility within 10 business days. Next day, advanced replacement is
available for a small expedited fee.
All-in-One Maintenance: All maintenance fix releases will be provided free of charge during the first
90 days.
Service & Support Programs & End Of Life (EOL)
In accordance with Alcatel-Lucents established Product Life Cycle policy, as well as its customer
satisfaction policy, Alcatel-Lucent will honor its obligations to customers currently under warranty or
with valid purchased service agreements relating to a product line for five (5) years (Software: three
(3) years and Hardware: five (5) years) beyond the EOL (End Of Life) of a product line.
Lifetime Support
All versions of the stackaable product families come with a Limited Lifetime Hardware Warranty,
limited to the original owner, and will be provided for up to five (5) years. Faulty parts will be replaced
via a five (5) business days AVR (Advance Replacement) RMA.
Hardware Alcatel.Lucent warrants that, for the applicable warranty period of one (1) year for
hardware (a) Equipment shall, under normal use and service, be free from defects in material and
workmanship, and (b) Equipment shall materially conform to Alcatel.Lucents specification therefore
in effect on the date of shipment. The warranty period applicable to any product shall be one (1) year
from the date of shipment except if Alcatel.Lucent performs installation Services for any Product, then
the warranty period applicable to the product shall be one (1) year from the date Purchaser is deemed
to have accepted the Product in accordance with the Agreement. Hardware warranty only includes
Standard Repair or Replacement of Defective Parts (Standard R&R) support.
Lifetime Support
All versions of the stackable product families come with a Limited Lifetime Hardware Warranty,
limited to the original owner, and will be provided for up to five (5) years. Faulty parts will be replaced
via a five (5) business days AVR (Advance Replacement) RMA.
Software & Firmware Alcatel.Lucent warrants that, for the applicable warranty period of ninety (90)
days for software, (a) Software media shall, under normal use and service, be free from defects in
material and workmanship, and (b) Software shall materially conform to Alcatel.Lucents specification
therefore in effect on the date of shipment. However, Alcatel.Lucent makes no warranty that any
software will operate uninterrupted or error free. Software warranty includes software bug fixes and
patches. Software upgrades and/or enhancements are not included as a part of Alcatel.Lucents
warranty, but can be purchased separately.
The Alcatel.Lucent Product Life Span depends on many conditions in the market place and varies from
platform to platform. Historically speaking, some platforms have been out in the market more than
seven (7) years and still continue to exist on our product portfolio, while others may have experienced
shorter life spans.
Alcatel.Lucent provides a full suite of maintenance offerings including Technical Assistance Center 24
x 7 x 365, Standard Repair or Replacement of Defective Units, Advanced Repair or Replacement, and
Emergency Call Out to dispatch a qualified Field Engineer to provide on-site support. An overview is
provided below that provides information regarding support options available.
SupportBasic: One year 7x24 phone. Includes e-service Web access, software releases, repair and
return of hardware to be completed in 10 business days from receipt.
SupportPlus: One year - 7x24 phone. Includes e-service Web access, software releases and advanced
shipment for next business day arrival of replacement hardware.
SupportTotal: One year - 7x24 phone. Includes eService Web access, software releases, and same day
4-hour on site hardware replacement (labor and parts) 7 days a week, 24 hours a day. Excludes NMS
and Authentication Services software.
Alcatel.Lucent-ESD
Calabasas/CA./USA
OmniSwitch 6400 Series (OS6400) Hardware Technical Specifications

OmniSwitch 6400 (OS6400) family switches are advanced 10/100/1000Mbps copper and fiber based stackable workgroup switches that provide wire rate L2+,
basic L3 routing (RIP only) services with high availability for IPv4 and IPv6 communications and mission-critical environments. The new OmniSwitch 6400
family of switches provides feature-rich, yet value-priced, solutions for supporting converged applications.
The OS6400s high availability design makes them a great choice for:
Branch office workgroup / LAN wiring closets deployments
Small Medium Business core configurations
Metro Ethernet access for residential / metro triple-play applications
Converged data / voice / video networks

All members of the OS6400 series have a new space-saving design that provides the maximum flexibility in installation. Through use of a reduced depth main
chassis, the OS6400 can be installed in space-constrained cabinets.
The power options available for the OS6400s also provide great flexibility and include externally Pluggable or remote mounting power supplies as well as
standard or high-power PoE. This allows you to deploy PoE on every user port with only the amount of power needed generating a cost savings.
Additionally, for non-PoE switches interanl AC/DC power supplies are provided and external power supply can be attached in for backup roles. The
OmniSwitch 6400 along with OS6800 & OS9000 series are the first switches from the OmniSwitch family that meet European green standards.
The OmniSwitch 6400 Series benefits from a distributed switch architecture that provides redundancy of critical hardware and software elements for a
continuous traffic processing in any network conditions without a single point of failure.
OmniSwitch 6400 Series Switch Processing Scheme; Non-blocking, and store-and-forward
The product family model names have the format: OS6400-xxxx. Suffix letters in the model name
Chassis Options Notes
indicate different functionality:
* Power supply:
- "P" means bundle comes with Standard PoE power supply (360w),
- "P and H" means bundle comes with High-PoE power supply (510w)
- "D" means bundle comes with DC power supply,
- "U" means bundle comes with SFP Fiber (100 or 1000BaseX)
- No P, H, U or D means bundle comes with standard internal power supply package and is Non-PoE
model.
All members of the OS6400 series employ a reduced depth main chassis. Power supply could be
directly plugged in the rear of the chassis or remotely mounted in the rack. Chassis Bundles ship with
two rack mounts for the power shelf, and one chassis connection cable for remote mounting of the
power supply. OS6400 supports power supply redundancy.
All versions of the OS6400 family come with hardware Limited Lifetime Warranty. Limited Lifetime
Warranty is limited to the original owner, and will be provided for up to five (5) years after product
End of Sales (EoS) announcement. Faulty parts will be replaced via a five
(5) Business days AVR (Advance Replacement) RMA.
Limited Lifetime Warranty does not apply to transceivers.
System Requirements
Memory Requirements:
OmniSwitch 6400 Series Release 6.3.3.R01 requires 256 MB of SDRAM and 128MB of flash
memory. This is the standard configuration shipped.
Configuration files and the compressed software imagesincluding web management software
(WebView) imagesare stored in the flash memory. Use the show hardware info command to
determine your SDRAM and flash memory.
Uboot, FPGA, MiniBoot, BootROM, and Upgrade Requirements:
OmniSwitch 6400 Series
Uboot: 6.3.3 R01 or later
MiniBoot. Uboot: 6.3.3 R01 or later
POE Firmware
5.01
Alcatel.Lucent-ESD
Calabasas/CA./USA
MAC Address Table (L2 Unicast MAC addresses)

Learned Port Security
What is the maximum number of MAC addresses a
port can learn?
IP Address Table Routes (RIB)
L3 IPv4 Host Entries (FIB)
L3 IPv4 LPM Routes (FIB)
L3 IPv6 Host Entries (FIB)
L3 IPv6 LPM Routes (FIB)
Hardware Tunnels/Trunks
Flows/ACLs
Meters
Counters
Packet Buffer Size per system
Hardware Architecture
Up to 16 K (16,384) MAC Addresses is supported per system.
For the OmniSwitch 6400 family, the learned port security feature of the Alcatel-Lucent Operating
System allows up to 100 MAC addresses per port to be learned and acted upon, with up to 8,192 per
switch. The maximum number of MAC addresses the switch can learn for Layer 2 forwarding is
16,384 simultaneous MAC addresses.
2K routing table
1024
1024
512
512
128
2K
2K
2K
1 MB of buffering available per system
Each port type regardless of port speed is assigned a minimum and a maximum threshold buffer space.
Buffering is supported per port and there is a shared pool of up to 2MB available per system that is
based on an optimization algorithm that monitors buffer allocation per port. The buffering algorithm
could be optimized to allocate the unused buffering space for the inactive ports to the active ports. In
other words, inactive ports buffer space can be used by those ports that are active and require more
buffering space if need be.
* 1,048,575 bytes of buffering available per system.
* Two buffer allocation thresholds: LwmCosSetLimit and DynCellLimit. There is one of each type of
threshold per queue. Each queue is defined by a {port, COS} combination. There are 8 COS in our
system, the highest COS is reserved for internal traffic while the user can assign the other 7.
* LwmCosSetLimit is the Low Water Mark for buffer allocation per queue. Beyond this mark a queue
will tap into a dynamically shared buffer pool.
* DynCellLimit is the stop threshold for a queue to acquire more buffer from the pool.
CPU
BUS
Memory
Flash
USB Port (Future Release)
Main Switching Fabric ASIC
PHY
Connectors
Stacking
Console Port
Combo Ports
Both of the above thresholds have been pre-determined and calculated for optimal performance under
our benchmark. The default will automatically tap into shared buffer resources whenever the situation
demands it. If the users wish to customize the buffer sizes, we are usually able to accommodate the
request by analyzing their traffic pattern.
Free-scale MPC8248 processor (400MHZ)
Hi-Gig (Hi-Gig+ capable) & 32-bit 66MHZ PCI BUS & I2C BUS
256MB of SDRAM
Flash: 128MB Spansion Flash
Philips ISP1761 USB2.0 port on the front panel
BCM5632x (56322 or 56324)
XFP, SFP, and RJ45 connectors
Supports up to 8 unit stacking topology
Two built-in stacking ports to provide fault tolerant looped stacking configuration
10 Gbps full-duplex bandwidth per stacking port
RS-232 Console Port (RJ-45 connector).
The console-protecting chip SEMTEC LCDA15C-6 is used along with the RJ45 connector.
OS6400-24, -48, -P24, -P48, -P24H, -P48H: four Gigabit Ethernet SFP combo ports
OS6400-U24, -U24D: two Gigabit Ethernet SFP combo ports
Alcatel.Lucent-ESD
Calabasas/CA./USA
POE /(Power over Ethernet) In-line Power

EEPROM
Front Panel LED
Temperature Sensor
Thermal detection & Shutdown
Clock
Power Supply
LEDS
The OmniSwitch 6400 Series platforms are 1U

(Rack Unit) high
19" Rack-Mountable
The OmniSwitch 6400 Series platforms are No more
than 19.93 deep (including the backup power
supplies)
Dynamic and automatic module ID selection
All models conform to Alcatel-Lucent coloring and
labeling scheme
Switch Faade for Alcatel-Lucent label
100BASE-FX
1000BASE-T EXTND SFP
1000BASE-T LH (40Km) SFP
1000BASE-T LH (70Km) SFP
1000BASE-SX SFP
1000BASE-LX SFP
1000BASE-BX-D SFP
1000BASE-BX-U SFP
Grounding lugs
Mounting holes on the side, near the front and back of
the chassis
RS-232 connector for console connection on the front
pane
USB port on the front panel
(Version 2.0 full speed min.)
7 segment LED stack# display on the front panel
Port LED
Standard OK1 & OK2 LEDs
Port Numbering scheme with first port in the upper
left hand corner
Power Supply Failure LED
Temperature Threshold Exceeded LED
FAN failure LED
Primary unit LED (designate the master unit in a stack
configuration)
Secondary unit LED (designate the master unit in a
stack configuration)
LED for BPS status
AC and DC power supplies
AC Power Supply: power source 115-200 V AC,
Support POE with full compliance of IEEE 802.3af

Board ID EEPROM Atmel 24C02 (on based-board)
Front Panel 7-segment LED display for stack ID
Temperature Sensor National Semi-Conductor LM77 is supported
Thermal detection and shutdown is supported.
Real Time Clock chip M41T11
Backup power supplies are external either directly connected to the rear of the unit or remotely
mounted.
Non-PoE models has built-in internal power supply.
PER PORT LEDS
10/100/1000: PoE, link/activity
SFP: link/activity
Stacking: link/activity
SYSTEM LEDS
Switch ID (indicates the stack ID of the unit in the stack: 1 to 7)
System (OK) (chassis HW/SW status)
PWR (primary power supply status)
PRI (virtual chassis primary)
BPS (backup power status)
Hardware Device Level features supported
Supported.
Supported.
Supported.
Supported
Supported
Supported
Supported on all OS6400 SFP PORTS
Supported.
Supported.
Supported.
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported (Future Release)
Supported
Supported
Supported
Supported
Indicating which PS has failed: Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Alcatel.Lucent-ESD
Calabasas/CA./USA
50-60 Hz
DC power supply: 36 72 V DC (input)
Single main power supply to provide power for
chassis and POE
POE back up power
POE interface compatible with PowerDsine Ron chip
Low POE power (24 ports) 10watts/port
Low POE power (48 ports) 5watts/port
High POE power (24 ports)-16.25watts/port
High POE power (48 ports) 8.125watts/port
Redundant dual hot swappable Power Supplies.
Power supplies are able to attach to the rear of the unit
Insertion or removal of redundant power supply
Remote mounting of backup power supplies
Single BPS for chassis and POE
Modular 510W BPS for POE that fits in the OS6400
BPS shelf.
BPS Power Supply bundle (2.5U power shelf for
BPS, power cord, BPS, chassis connection cable)
Circuit breaker protected OS6400 units
Noise level
Storage Temperature
Loop protection against loop back
Cisco-like Proprietary UDLD
Support Cat 5, 5e, 6, and 6e
Capability to disable transmit function (or reset) of
each PHY individually
Capability to control the transmit function of the SFP
and XFP ports
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Insertion or removal of redundant power supply does not cause any power or service disruption to the
switch
Supported
Supported
Supported
Power supply bundle is 1U 360W or 510W + shelf_cable+19 Rack mounts ears .BPS can be either
connected at the back of the unit (360W) or on top of the unit (510W).
Supported
All OmniSwitch 6400 platforms: < 44dBa
0 C to 45 C (32 to 113 F)
- 40 C to 75 C (-40 to 167 F)
5% to 95% (non-condensing)
Supported
UDLD is supported.
support for monitoring the physical configuration of cables and detect unidirectional links
Supported
Supported
Supported
Alcatel.Lucent-ESD
Calabasas/CA./USA
Stacking (Virtual Chassis Architecture)
Stacking feature
Virtual chassis, single IP for management

o
Stack is managed through a single IP address - Virtual Chassis concept is
supported
Two built-in stacking ports
o
Fault tolerant looped stacking configuration
Dedicated 2 x 10Gigabit stacking links on each model
Stacking of OS6400 platforms is supported up to a maximum of 8 units per stack.
o
Up to 8 chassis in a stack
384 Gigabit ports
PoE and non-PoE can be mixed

Primary, secondary, idle and pass-through elements in the stack
Stack module IDs are set using CLI and displayed on the panel
Each module in the stack is capable to act as Primary
Stacking Guidelines
Stacking Redundancy
1.
Only support 8 stacks in a stacking configuration.
2.
The redundant stacking cable must be in place to support the full virtual Chassis.
3.
Auto Configuration of the stacks
4.
OmniSwitch 6400 units and OmniSwitch 6800 units should not be mixed in the same stack.
If the switches connected in a stack is having duplicate slot numbers one of the units will go into the
pass through mode. When a switch is in pass-through mode, its Ethernet ports are brought down but
stacking cable connections remain fully functional and can pass traffic through to other switches in the
stack. To avoid duplicate slot numbers, make sure that any modules being added to an existing stack
have been cleared of pre-assigned slot information.
When inserting switches into an existing stack, observe the following guidelines:
Make sure the stack is fully certified/synchronized
Avoid duplicate saved slot numbers
Make sure that the system is powered up and initialized completely.
Never attempt to operate more than eight switches in a single stack
Insert one unit at time with one stacking uplink only.
Repeat with other unit if needed
Once all units have been fully inserted, then close the stacking loop
Time measured for Synchronization of the stack on OS6400 (stack of 8): 7-8 min.
The new images are downloaded to the primary working directory. The reload working no rollback
which updates all the NIs working directories will take an activating time up to 5 minutes (i.e. size of
the configuration file does not impact the time).
After system is up and "copy working certified flash-synchro which synchronizes the whole stack
will take about 2 to 2.5 minutes (i.e. size of the configuration file does not impact the time)
As a remainder, the following features are impacted on takeover
-Spanning Tree may reconvergence after takeover, since base-Mac of the chassis will change (that Mac
change may cause a root bridge change)
-IPv4 routing: the router Mac change on takeover will cause the router to rediscover the new router
Mac
-Same for IPV6 (link local address changes on takeover)
-LACP protocol need to restart causing LACP ports to go down
Unit Self Management

Automatic Over-Temp Shutdown
Provide user configuration to disable/override
temperature shutdown
Temperature Threshold Exceeded
FAN Failure Trap (sent every 5-min)
Inventory Support
Supported
Supported
Supported Trap (Sent every 5-min.)
Supported
Supported
Alcatel.Lucent-ESD
Calabasas/CA./USA
Data Plane
IEEE 802.3z & 802.3ab & 802.3u & 802.3
Auto-Detect on both Copper and Fiber
Simultaneous detection configuration priority
Media failure failover capability
802.3af on POE Models
Hot Swappable
Auto-negotiation/Auto sensing 10/100/1000
Auto-Detect the insertion and removal of the SFP
Hardware to operate at HiGig and HiGig+ speeds
UNH (or equivalent) operation standards
Supported
Supported
Supported
Supported
Supported: Power over Ethernet is supported on 10/100/1000BASE-T ports only
SFP and XFP optical transceivers are hot swappable
Supported
Supported
Supported (currently the HiGig operation is implemented, but the hardware is HiGig+ capable)
Supported
Ethernet Specifications
Connectors/ Cabling
Connector type
Connectivity
Cable supported
IEEE Standards Supported

Data rates
Ports Supported
Switching/Routing Support
Backbone Support
Port Mirroring Support
802.1Q Hardware Tagging
Maximum Transfer Unit -- MTU
Management: 1 RJ-45 console interface configured as DCE/DTE for operation, diagnostics, status,
and configuration information. Ship kit includes RJ-45 to DB-9 connector adaptor
AC power connector
10/1000/1000BASE-T copper ports: RJ-45
10/100/1000BASE-T copper ports with PoE: RJ-45
1000BASE-X SFP ports: LC with Removable/Pluggable transceiver SFP-MSA
24 & 48 x 10/1000/1000BASE-T copper ports: RJ-45
24 & 48 x 10/100/1000BASE-T copper ports with PoE: RJ-45
24 & 48 x 1000BASE-X SFP ports: LC with Removable/Pluggable transceiver SFP-MSA
10BASE-T hub or device; 100BASE-TX hub or device; 1000BASE-T hub or device
1000BASE-X hub or device,
10BASE-T: unshielded twisted-pair (UTP)
100BASE-TX: unshielded twisted-pair (UTP), Category 5, EIA/TIA 568 or shielded twisted-pair
(STP), Category 5, 100 ohm
1000BASE-T: unshielded twisted-pair (UTP), Category 5, EIA/TIA 568 or shielded twisted-pair
(STP), Category 5, 100 ohm
Note: Category 6 cabling is also supported on the 10/100/1000BASE-T connections.
On 10/100/1000Mbps triple speed ports:
10Mbps speed: 100 meters on copper
On GigE. Fiber:
SFP-GIG-LH70: up to 70km
SFP-GIG-LX: up to 10km
SFP-GIG-SX: up to 550m
802.3 Carrier Sense Multiple Access with Collision Detection (CSMA/CD)
10/100/1000Mbps triple speed

o
10Mbps
o
100Mbps
o
1000Mbps (Gigabit Ethernet)
Gigabit Ethernet
Triple Speed ports is supported and includes:

o
Ethernet (10 Mbps)
o
Fast Ethernet (100 Mbps)
o
1000Mbps Ethernet (Gigabit Ethernet)
Gigabit Ethernet
Layer 2 Switching/Layer 3 Routing (RIP only)
10/100/1000Mbps, Gigabit Ethernet ports
MTU parameter for Routers is not configurable.
The ASIC does not include the notion of an MTU that applies to an IP interface. Instead, it uses the
physical long-frame-size of the egress port as the MTU. When the ASIC attempts to forward a packet,
it tests the size of the packet against the physical long-frame-size of the egress port, if the packet is too
large, it forwards the packet to the CPU for fragmentation (or ICMP processing in the case of a packet
with Don't Fragment set).
10/100 ports are set with a long-frame-size of 1553 bytes.
GigE ports are set with a long-frame-size of 9216 bytes (jumbo frames).
Packets larger than the long-frame-size are dropped at ingress. The above (& default) values are the
maximum configurable values.
Packets that are forwarded from a 10/100 to a 10/100 port cannot ever be reported as too big via ICMP
Alcatel.Lucent-ESD
Calabasas/CA./USA
Inter-Frame Gap
Interface Alias (Port Alias)

Peak Flood Rate Configuration
Trap Port Link Messages
Per port rate limiting

Per-port L2 broadcast flood limit is supported.
Re-settable Statistics Counters
Duplex Mode support
Auto-negotiation
Crossover
Verifying Ethernet Port Configurations
Diagnostics
because anything larger than 1553 would not be accepted.

The same holds true for packets forwarded between two GigE ports and from a 10/100 port to a
GigE/10GigE.
Layer-2 Ethernet Frame Size:
Untagged: 1,518 Bytes without IEEE 802.1Q tags
Tagged: 1,522 Bytes with IEEE 802.1Q tags
Long Frame Size (enabled by default): 1553 Bytes (IEEE 8021.Q tagged or untagged)
Frame Type: Type2, LLC, SNAP, RAW 802.3
The maximum frame size on the Gigabit Ethernet interfaces range from 1,518 to 9,216 Bytes
Jumbo frames up to 9K Bytes (9,216 Bytes) are supported on GigE/10GigE interfaces.
Untagged (without IEEE 802.1Q tags) Ethernet Packets: 1,518 Bytes
Tagged (with IEEE 802.1Q tags) Ethernet Packets: 1,522 Bytes
12 Bytes (by default)
Inter-frame gap is a measure of the minimum idle time between the end of one frame transmission and
the beginning of another. By default, the inter-frame gap is 12 bytes. Through the use of this feature,
the inter-frame gap value (in bytes) on a specific port, a range of ports, or all ports on a switch (slot)
can be configured. Values for this command range from 9 to 12 bytes.
Note. This command is only valid on Gigabit ports.
Supported (none configured by default): Through the use of this feature an alias (i.e., description) for a
single port can be configured. (You cannot configure an entire switch or a range of ports.) The text
description can be up to 40 characters long.
By default:
42Mbps (Fast Ethernet)
496Mbps (Gigabit Ethernet)
By default, the flood rate is 42 Mbps on 10/100/1000 ports and 496 Mbps on Gigabit ports. Through
the use of this feature, the peak ingress flood rate value on a specific port, a range of ports, or all ports
on a switch (slot) in megabits per second can be configured.
Note. The user can configure a flood rate equal to the line rate, but it is not recommended. AlcatelLucent recommends that you always configure the flood rate to be less than the line speed.
Supported (disabled by default)
This feature can be enabled or disabled (the default) on a specific port, a range of ports, or all ports on
a switch (slot). When enabled, a trap message will be displayed on a Network Management Station
(NMS) whenever the port state has changed.
Per-port multicast / broadcast / flood limit is supported. The ASIC provides a per port configuration on
the incoming and/or outgoing port basis that allows broadcast and/or multicast storm control. The CPU
can program a threshold value per port that indicates the number of broadcast and/or multicast
packets/bytes that are allowed in a given time interval.
Supported
The duplex mode feature is supported on a specific port, a range of ports, or all ports on a switch (slot).
It can be set to full (full duplex mode, which is the default on fiber ports), half (half duplex mode), and
auto (auto-negotiation, which is the default on copper ports). The Auto option causes the switch to
advertise all available duplex modes (half/full/both) for the port during auto-negotiation. In full duplex
mode, the interface transmits and receives data simultaneously. In half duplex mode, the interface can
only transmit or receive data at a given time.
Auto-negotiation is supported (enabled by default). It can be enabled or disabled on a single port, a
range of ports, or an entire slot.
Crossover can be configured on a single port, a range of ports, or an entire slot. If auto negotiation is
disabled, auto MDIX, flow control, auto speed, and auto duplex are not accepted.
Setting the crossover configuration to auto will configure the interface or interfaces to automatically
detect crossover settings. Setting crossover configuration to mdix will configure the interface or interfaces for MDIX (Media Dependent Interface with Crossover), which is the standard for hubs and
switches. Setting crossover to mdi will configure the interface or interfaces for MDI (Media
Dependent Interface), which is the standard for end stations. And setting the crossover configuration to
disable will disable crossover configuration on an interface or interfaces.
To display information about Ethernet port configuration settings, use the show commands. These
commands can be quite useful in troubleshooting and resolving potential configuration issues or
problems on your switch. For more information about the resulting displays from these commands, see
the OmniSwitch CLI Reference Guide.
Off-line Diagnostics for manufacturing
OmniSwitch 6400 Series supports the capability to reboot to support Diagnostics Mode for
Customers for hardware only troubleshooting
Not to require external PCs or test equipment for running diagnostics
Alcatel.Lucent-ESD
Calabasas/CA./USA
P
P
m
Peeerrrfffooorrrm
maaannnccceee
Raw Fabric Capacity
OS6400-24: 48Gbps Full Duplex or 96Gbps aggregate
OS6400-P24: 48Gbps Full Duplex or 96Gbps aggregate
OS6400-U24: 48Gbps Full Duplex or 96Gbps aggregate
OS6400-U24D: 48Gbps Full Duplex or 96Gbps aggregate
OS6400-48: 96Gbps Full Duplex or 192Gbps aggregate
OS6400-P48: 96Gbps Full Duplex or 192Gbps aggregate
Stacking Capacity & Throughput
Raw Capacity: 24Gbps FD (12Gbps FD Stack-A and 12Gbps FD Stack-B)

Throughput: The Stacking (Stack A & Stack B run at 10G) supports 2 x 10-Gigabit Eth ports at
wire-speed: 2 * 14,880,952.3 pps = 29,761,904.6pps (approx: 29.8Mpps)
Throughput Performance:
Or Forwarding Rate
Per Stacked Switch
@64 Byte Packets
Assuming:
All traffic is forwarded through
The Switch Fabric ASIC
And where applicable:
Stacking (Stack A & Stack B) throughput
Theoretical packet per second (pps) rates for Ethernet packets is normally calculated by adding 20
bytes to each packet size to account for the 0.096 microseconds inter frame gap (equivalent to 12
bytes) and the preamble (eight bytes). Thus, the theoretical 10 Mbps, 100 Mbps, Gigabit and 10Gigabit Ethernet packet rate in packets per second (pps) for a packet of X bytes is defined by the
following formulas.
Throughput calculations assume 64 byte packets and the throughput rate is calculated per-port.
(1 Gbps) / ((8 bits/ byte) * (X+20)) = 1,488,095.23 pps
(100 Mbps) / ((8 bits/ byte) * (X+20)) = 148,809.52 pps
Since the primary benefit of any switch is speed, the most appropriate performance metric is
throughput, which is typically expressed in millions of packets per second (Mpps). Throughput
measures the number of packets per second (measured in millions) that a switch can process for
outbound (egress direction only) transmission to another device.
Throughput (at Layer-2 or Layer-3) = wire-speed Eth. ports * throughput rate per port
Note: The following assumes that all traffic is forwarded through the Main Switch Fabric ASIC.
The Stacking (Stack A & Stack B) supports 2 x 10-Gigabit Eth ports at wire-speed:
2 * 14,880,952.3 pps = 29,761,904.6pps (approx: 29.8Mpps)
Full Gigabit Ethernet:
The 24 Gigabit Eth ports throughput at wire-speeds:
Fast Ethernet with Gigabit Ethernet combo:
The 20 x 10/100Mbps Eth ports throughput at wire-speeds:
20 * 148,809.52 pps = 2,976,190.4pps (approx: 2.97Mpps)
Throughput numbers per models ( in stacked configuration):
OS6400-24/P24/P24H (24 GE ports + 2 10G stacking): 65.5Mpps
OS6400-U24/U24D (24 GE ports + 2 10G stacking): = 65.5Mpps
Notes:
For stand-alone configuration throughput numbers on all models please substract 29.8Mpps
Alcatel.Lucent-ESD
Calabasas/CA./USA
Throughput Performance:
Or Forwarding Rate
Per Stacked Switch
@1518Byte Packets
Assuming:
All traffic is forwarded through
The Switch Fabric ASIC
And where applicable:
Stacking (Stack A & Stack B) throughput
Theoretical packet per second (pps) rates for Ethernet packets is normally calculated by adding 20
bytes to each packet size to account for the 0.096 microseconds inter frame gap (equivalent to 12
bytes) and the preamble (eight bytes). Thus, the theoretical 10 Mbps, 100 Mbps, Gigabit and 10Gigabit Ethernet packet rate in packets per second (pps) for a packet of X bytes is defined by the
following formulas.
Throughput calculations assume 1518 byte packets and the throughput rate is calculated per-port.
(1Gbps) / ((8 bits/ byte) * (X+20)) = 81,274.38 pps
(10 Mbps) / ((8 bits/ byte) * (X+20)) = 812.74 pps
Since the primary benefit of any switch is speed, the most appropriate performance metric is
throughput, which is typically expressed in millions of packets per second (Mpps). Throughput
measures the number of packets per second (measured in millions) that a switch can process for
outbound (egress direction only) transmission to another device.
Throughput (at Layer-2 or Layer-3) = wire-speed Eth. ports * throughput rate per port
Note: The following assumes that all traffic is forwarded through the Main Switch Fabric ASIC.
Stacking:
The Stacking (Stack A & Stack B) supports 2 x 10-Gigabit Eth ports at wire-speed:
Full Gigabit Ethernet:
Fast Ethernet with Gigabit combo ports:
20 * 8,127.43 pps = 162,548.6pps (approx: 162.5Kpps)
Models:
OS6400-U24/U24D (24 GE ports + 2 10G stacking): 3.57Mpps
Notes:
For stand-alone configuration throughput numbers on all models please substract 1.62Mpps
System
Boot time
Management fail-over
Image download time

System Resiliency Verification
Cold boot time in a stand-alone configuration when the switch can join the network and start passing
traffic: approximately 115 sec.
Cold boot time in a stackable configuration of up to 8 units when the switch(s) can join the network
and start passing traffic: approximately 115 sec.
Warm re-boot time in a stand-alone configuration when the switch can join the network and start
passing traffic: approximately 115 sec.
Warm re-boot time in a stackable configuration of up to 8 units when the switch(s) can join the
network and start passing traffic: approximately 115 sec.
The Fail-over time (Primary switch to Secondary switch in a stacked configuration) is:
Layer-2: 20 seconds maximum
Layer-3: 30 seconds maximum
Trap is sent (to the management station for the failure of the primary management) and log event is
logged upon primary management failure and after the redundant management unit takes over.
Approximately 65 sec
Alcatel-Lucent OmniSwitch 6400 switches are designed in such a way that is highly reliable under
extreme stress conditions. The OmniSwitch 6400 switches are rigorously tested to ensure that the
system is able to sustain heavy loads and allow for continued availability of all system resources.
The typical test setups involve:
Alcatel.Lucent-ESD
Calabasas/CA./USA
Running in normal operational mode where system is running under the specified CPU
threshold values.
Running above the CPU threshold values all the time.
Interfaces
Power over Ethernet
Stacking ports
IEEE 802.3af (supported on all POE type chassis)

Two built-in stacking ports
Fault tolerant looped stacking configuration
Combo ports
OS6400-24/-P24/-P24H/-48/-P48/-P48H = 4 x Combo ports which can be individually configured to
be 10/100/1000BaseT or 1000BaseX and that can support SFP transceivers.
OS6400-U24/-U24D = 2 x Combo ports which can be individually configured to be
10/100/1000BaseT or 1000BaseX and that can support SFP transceivers.
Notes:
The Combo 10/100/1000BaseTcopper RJ-45 ports support PoE.
The Combo 1000Base-X fiber SFP ports do not support PoE
Ethernet minimum size packet
64 Bytes
Ethernet IP packet maximum transmission _ MTU
1000Mbps (GigE); 9,216 Bytes (Jumbo frames)
10/100Mbps Eth IP packet max transmission unit; 1553 Bytes
Flood Control
You can rate limit the flooding traffic. Flood control is done on ingress and the rate is shared for all
interfaces on that switch.
By default flood control only applies for flooding with broadcast (ff:ff:ff:ff:ff:ff) and unknown
destination Mac address. You can enable flood control for multicast Mac as well.
Default settings:
Flood multicast disable
Flood rate set to 496 Mbps on 1G port
Flood rate set to 49Mbps on 100M ports
Flood rate set to 4Mbps on 10M ports

Note:
The above rates are met with packet size of 512 bytes. Different packet size will give different flood
rate.
The theoretical flood rate (the maximum TX rate at a given packet size you can send before you reach
the flood control rate limiting) is obtained with:
Theoretical Flood Rate = Interface Flood Rate * (Packet Size + 20) / 512
Flood rate limiting does not give a steady rate at the theoretical flood rate. It gives a sporadic/bursty
profile where the average rate is the theoretical flood rate.
Configuration Limitations
The maximum number of units possible in the stackable system is 8.
The stack may contain any combination of OS6400 Series platforms.
Please see the table below:
Fixed-Chassis
POE
Non-POE
10 Gig.
10/100/1000Mbps
Combo
POE Power
Power Supplies
Types
Ports
Ports
Stacking
,GigE, or
Ports*
Budget
supported
Ports
10/100Mbps
Non-PoE Models
OS6400-24
N/A
24
2
20 10/100/1000
4
N/A
Powered by 126W
AC (internal)
OS6400-48
N/A
48
2
44 10/100/1000
4
N/A
Powered by 126W
AC (internal)
OS6400-U24
N/A
24
2
22 GigE SFP or
2
N/A
Powered by 126W
100-Base-X
AC (internal)
SFP**
OS6400-U24D
N/A
24
2
22 GigE SFP or
2
N/A
Powered by 126W
100-Base-X
DC (internal)
SFP**
PoE Models
OS6400-P24
20
N/A
2
20 10/100/1000
4
N/A
360W AC
OS6400-P24H
20
N/A
20 10/100/1000
N/A
510W AC
OS6400-P48
44
N/A
44 10/100/1000
N/A
360W AC
OS6400-P24H
44
N/A
44 10/100/1000
N/A
510W AC
Alcatel.Lucent-ESD
Calabasas/CA./USA
*Combo ports are ports individually configurable to be 10/100/1000BaseT or 1000BaseX that can support SFP
transceivers for short, long and very long distances.
** Gig fiber interfaces support Gig SFP or 100BaseX SFP optical transceivers.
Alcatel.Lucent-ESD
Calabasas/CA./USA
Layer-2/Layer-3 Switching
Root bridge priority / path cost:
Group mobility Rules supported:
Binding rules supported
Rule Precedence:
Max. number of 1x1 STP instances

Maximum VLANs
Default spanning tree mode is RSTP (IEEE 802.1w)

The bridge priority can be any value between 0 and 65535 for STP and RSTP protocol in
the 16-bit mode. By default spanning tree follows the 16-bit path cost.
The bridge priority can only be in multiples of 4096 in the 32-bit mode or in MSTP mode.
MSTP can only operate in 32-bit mode.
Port
MAC
MAC range
Mobile-Tag
Protocol
IP
IPX
DHCP port
DHCP MAC
DHCP MAC Range
DHCP Generic
Port-Protocol Binding rule
MAC-Port Binding rule
MAC-IP-Port Binding rule
Mobile Tag
DHCP Mac
DHCP Mac Range
DHCP Port
DHCP Generic
Mac-Port-IP Binding
Mac-Port Binding
Port-Protocol Binding
Mac
Mac Range
Network Rule
Protocol
253 supported per system
VLAN Range Support
Up to 4094 VLANs for Flat Spanning Tree mode/MSTP and 253 VLANs for 1x1 Spanning Tree mode
are supported. In addition, it is now possible on the OmniSwitch 6400/6800/6850/9000 to specify a
range of VLAN IDs when creating or deleting VLANs and/or configuring VLAN parameters, such as
Spanning Tree bridge values.
Note: Although, up to 4094 VLANs has been configured and tested, we still recommend configuring
up to 1K (1,024) in a flat STP mode.
Is the native (untagged) VLAN required to be a specific VLAN?
Alcatel-Lucent Response: No.
Note: Alcatel-Lucent AOS OmniSwitch product family software refers to a native VLAN (a Cisco
term) as a default VLAN. Therefore, our default VLAN functionality is similar to that of native
VLAN as discussed here.
Is the management VLAN required to be a specific VLAN?
Alcatel-Lucent Response: No.
Can the management VLAN be tagged or untagged?
Alcatel-Lucent Response: YES.
Can the Native VLAN be excluded from an 802.1Q link (i.e., the ability to send only tagged traffic
over an 802.1Q link)?
How many VLAN IDs does this device support?
Alcatel-Lucent Response: Comply with up to 4093.
Maximum Number of Tagged VLANs per Port: 4093
Alcatel.Lucent-ESD
Calabasas/CA./USA
VLAN Stacking
& Translation
Maximum number of BPDUs the switch can handle

MAC Address Table
Routing Table
Layer-2 Table Hashing
RSTP Performance
Sub-second performance
Max number of configured VLANs per port

A-VLAN
Supported rules for AVLAN
Max number of configured VLANs per system
Maximum frame size

With the insertion of a 4-byte svlan tag by VLAN Stacking, the maximum frame size that can be
accommodated is jumbo frame size less 4 bytes = 9216 4 = 9212 bytes.
Maximum number of SVLANs:
For port level VLAN Stacking: 4093 (VLAN 2 through 4094).
For port / vlan level VLAN Stacking: 768 (can use any number from 2 through 4094 inclusive).
Approximately 800 BPDUs per second
Up to 16 K (16,384) MAC Addresses is supported per system.
1K (authenticated / mobile users) per module
2K routing table
1K forwarding LPM entries
The L2 Table size is 16K entries. This is organized as 2K buckets with each bucket having 8 entries.
The search key for the L2 Table is the 60 bit (i.e. 48-bit DA MAC address + 12 bit VLAN-ID) in the
Ethernet MAC header in the incoming flow. The key is hashed into a 11-bit value used to select the
bucket in the table using a CRC32 lower 11-bits algorithm. Each entry in the selected bucket is
compared with the key. The match must be an exact match since if it does, it must be a host MAC
address entry. If the key matches an entry in the bucket, then the information in the entry is used in the
ingress logic for the destination port
Link Fail-over: 459ms
Link Fail-over Reverse: 240ms
Port Fail-over: 220ms
Port Fail-over Reverse: 140ms
AGG Links Fail-over: 958ms
AGG Links Fail-over Reverse: 260ms
AGG Fail-over: 219ms
AGG Fail-over Reverse: 280ms
1 K (1,024) with support of full 4K IEEE 802.1Q VLAN Spectrum. Port based (w / IEEE 802.1Q)
VLANs.
Maximum number of Avlan authenticated user per system: 1024.
The system supports up to 1024 authenticated/mobile Mac-addresses
AVLAN supports RADIUS or LDAP as authentication servers. By configuring multiple servers, user
can gain server failover in case of server outage.
Supported rules for AVLAN.
MAC range (used for IP phone OUI Mac-addresses for instance)
MAC range (used for IP phone OUI Mac-addresses for instance)

4K (4,094)
The switch has indeed been tested with up to 4,094 active VLANs, but this is really based on switch
configuration and available resources.
Note: since configuring 4K VLANs consumes a lot of resources, the more practical, or more
realistic and/or recommended figure is the 1,024 active VLANs.
In the STP flat Mode: 4K VLANs are supported over 802.1Q or over a trunk.
In the STP 1x1 Mode: 253 VLANs are supported over 802.1Q or over a trunk.
In the STP Multiple Mode (IEEE 802.1s): 4K VLANs amongst 16 Multiple STP Instances (MSTPI).
Alcatel.Lucent-ESD
Calabasas/CA./USA
Maximum number of rules per chassis:
Max number of MAC Rules

Max number of Subnet Rules
Max Types of Protocols Rules supported
Max number of DHCP rules per system
Max number of Binding Rules
Max number of 802.1Q tags per port

Max number of Authenticated Users
Max number of 802.1x Users
Max number of STP instances per system

Max number of 802.1s STP instances per system
Max number of Link Aggregate
The following limitations are imposed by the NI hardware table sizes.

Since the tables are always synchronized between NI, the following numbers are the chassis
limitations:
1024 VLAN-MAC rules:
A vlan Mac rule consists in MAC, MAC range, MAC-Port-IP binding, MAC-Port binding, MAC-PortProtocol binding, MAC-IP binding and IPX Network rules.
Since hardware does not support IPX network rules, the system internally uses a vlan Mac rule to map
the Mac address matching the given IPX network to that vlan.
The VLAN-MAC table is also shared with authenticated Mac-addresses (AVLAN, 802.1x)
256 VLAN-SUBNET rules
A vlan subnet rule consists in IP network and Port-IP binding rules
16 VLAN-PROTOCOL rules
A vlan protocol rule consists in Protocol and Port-Protocol binding rules.
For IP protocol (ip-e2 or ip-snap), 2 rules are needed: 1 for ip packets and 1 for arp packets.
Notes:
Dual protocols Mac-address is supported. The same Mac with both IP protocol (ip-e2) and
IPX protocol (ipx-e2) can be classified into 2 different VLANs.
Duplicate Mac on different mobile vlan is only supported for IP network rules or protocol
rules. For rules falling into the VLAN MAC table, only one Mac/vlan is supported. For
instance, the same Mac with 2 IPX networks 0x111 and 0x222 cannot be classified into 2
VLANs.
Tagged packets on mobile ports are first classified by their VLAN-ID. If you do not have
mobile-tag enabled for that vlan or a mobile rule to classify that packet to that vlan, the
packet is dropped.
1 K (1,024)
Note: Maximum number of MAC rules, Authenticated VLAN Users, Binding Rules, and 802.1x Users
all share the 1,024 MAC Rules
256 (Maximum of 256 IP Subnet rules are supported.)
6 (Note: Support for IP, IPX, DECNet, AppleTalk, SNAP, and Ethertype)
64
1 K (1,024)
Maximum of 1024 rules of combining MAC-Port-IP binding, MAC-Port binging, MAC, MAC Range,
and IPX Network rules (The available MAC rule pool is also shared by AVLAN and 802.1x)
4K
1 K (1,024)
Maximum number of 802.1x authenticated user per system: 1 K (1,024)
Maximum number of 802.1x authenticated user per port: 253
The system supports up to 1024 authenticated/mobile mac-addresses.
all share the 1,024 Mac Rules
128
128
32 aggregates of up to 8 ports each, per stand-alone switch and/or across units
Support for static aggregate (aka OmniChannel)
Support for dynamic aggregate (IEEE 802.3ad)
LOAD BALANCE ALGORITHM
The load balance is the same for static and LACP link aggregation.
The load balance takes the 3 last bits of the source address and the 3 last bits of the destination address
and does an XOR. That gives a number between 0 and 7
Note that Link1 is the lowest port number, then Link2 is next port number
On the 6400's, the multiple ports must be on the same "Stack" of 6400's. They can be on separate
6400's but those 6400's must be cabled together with a Stacking cable and it must be functioning as a
stack.
Alcatel.Lucent-ESD
Calabasas/CA./USA
Static ARP with multicast Mac
The UDP Relay Services
Auto-negotiation
Traffic Control
Spanning Tree
Maximum Number of STP Instances:

Per Stack and/or Per Chassis
When you want to flood a routed unicast packet to ALL ports of the egress vlan, which can be
achieved by creating a static ARP with a multicast Mac address.
The flooding is done in hardware (wire speed).
Using a policy rule, you can rate limit the flooding to a specific rate.
The UDP Relay will verify that the forward delay (elapsed boot time specified by the user) has been
met before Relaying the UDP packet.
If the relay is configured with multiple Next Hop addresses, then the packet will be sent to all next-hop
destinations. The UDP Relay shall also verify that the maximum hop count (also set by the user) has
not been exceeded. If either of these conditions is not meet, the UDP Relay will discard the
BOOTP/DHCP packet.
In Release 6.3.3.r01 the NBNS/NBDD and generic service has been added to the UDP port relay.
As indicated in the table for NBNS and NBDD user can specify which vlan the packets are forwarded
to. User can not specify the next hop IP address or the next hop address type.
For all other generic services, user is able to configure which vlan (up to 10 VLANs) the UDP packet
is to be forwarded to. User cannot specify the next hop IP address or the next hop IP address type.
Service
UDP Port Number
Configurable Options
BOOTP/DHCP
67/68 (Request /
1.
Next Hop Address
(Bootstrap Protocol/
Response)
2.
Forward delay
Dynamic Host
3.
Maximum hops
Configuration
Protocol)
NBNS/NBDD
137/138
1.
VLANs to forward
to
Generic services
Any number
1.
VLANs to forward
to
Speed (10, 100, 1000Mbps) and duplex mode (half or full)
IEEE 802.3x
Note: the switch does not support honoring the incoming (RX) IEEE 802.3x pause frames, but it does
support generating outgoing (TX) IEEE 802.3x pause frames
IEEE 802.1D Standard Spanning Tree Algorithm and Protocol (STP)
IEEE 802.1w Rapid Spanning Tree Algorithm and Protocol (RSTP)
IEEE 802.1s / IEEE 802.1Q 2005 Multiple Spanning Tree Protocol (MSTP)
Ring Rapid Spanning Tree Protocol (RRSTP)
PVST+
Support of single and multiple instances for STP & RSTP BPDU Watch Guard
How many Multiple Spanning Tree Groups are supported? 253
Is one Spanning Tree per Group supported? Yes only in a STP 1x1 mode
Is one Spanning Tree per port supported? Yes
Is Single Instance Spanning Tree supported? Yes only in a STP flat mode
Does this device support any spanning tree enhancements (e.g., Root Guard, BPDU Guard, BPDU
Filtering, PortFast, etc.)?
Note: Alcatel-Lucent AOS OmniSwitch product family software refers to Root Guard as Restricted
Role which is supported.
Note: Alcatel-Lucent AOS OmniSwitch product family software refers to BPDU Guard as BPDU
Shutdown Ports which is supported.
BPDU Filtering is supported.
Note: Alcatel-Lucent AOS OmniSwitch product family software refers to PortFast as EdgePort
which is supported.
Does this device support an instance of spanning tree per 802.1Q VLAN (commonly referred to as
PVST+)?
Alcatel-Lucent Response: Comply.
a) Flat Mode:
STP 1 Instance
RSTP 1 Instance
MSTP 1 CIST and 16 MST Instances
b) 1x1 Mode:
STP 253 Instances
RSTP 8 Instances
Alcatel.Lucent-ESD
Calabasas/CA./USA
Spanning Tree
Root bridge priority / path cost
Port Monitoring
Port Mapping
STP convergence time (flat, 1x1, 802.1s)

802.1w rapid reconfiguration
Learned MAC addresses per port
Learned MAC addresses per system
Layer-2 forwarding on Ethernet ports
Layer-2 forwarding GigE, known MAC
Broadcast per Ingress port
Loopback Interface
a)
Default spanning tree mode is RSTP (IEEE 802.1w)
b)
The bridge priority can be any value between 0 and 65535 for STP and RSTP protocol in
the 16 bit mode. By default, spanning tree follows the 16 bit path cost.
c)
The bridge priority can only be in multiples of 4096 in the 32 bit mode or in MSTP mode.
d)
MSTP can support 32 bit mode per standard.
e)
Changing STP protocol to MSTP will reset all priority and path cost of a bridge to default
The default port path costs are: (IEEE Std 802.1D-1998- 16 Bit)
Port Speed
Path cost
10M
100
100M
19
1000 M
4
The default port path costs are: ( IEEE Std. 802.1Q-2005 32 Bit)
Port Speed
Path cost
10M
2000000
100M
200000
1000 M
20000
The default link aggregation path costs are (16 Bit):
Linkagg speed
Linkagg size
Path cost
2
60
10M
4
40
8
30
2
12
100M
4
9
8
7
1000M
N/A
3
The default link aggregation path costs are (32 Bit):
LinkAgg speed
LinkAgg size
Path cost
2
1200000
10M
4
800000
8
600000
2
120000
100M
4
80000
8
60000
1000M
2
12000
4
8000
6000
The same unit cannot support both mirroring and monitoring configuration i.e. a user cannot have a
port monitoring and a port mirroring session on the same unit.
Only one monitoring session at a time across the entire system
Only the first 64 bytes of the packet can be monitored. Due to the port monitoring file size, the system
can only store the first 2K packets (i.e. 140K/64 = 2187)
The port monitoring is not supported on the linkagg ports.
Enabling the monitoring function affects the performance. Consequently, Port Monitoring performance
is not at wire-rate.
Port mapping feature is supported on OS6400/6800/6850/9000. Following are the limitations for the
feature.
8 sessions supported per standalone switch and stack
An aggregable port of a link aggregation group cannot be a mapped port and vice versa
A mirrored port cannot be a mapped port and vice versa
A mobile port cannot be configured as a network port of a mapping session

30 sec
Less than 1 sec
Up to 16 K (16,384) MAC Addresses is supported
Up to 16 K (16,384) MAC Addresses is supported
Wire-speed (64 Bytes packets)
Wire-speed (64 Bytes packets)
Programmable
The loop-back interface allows you to uniquely identify a router in the network with one IP address.
The advantage of the loop-back interface is to be independent of the physical ip interfaces. In a
redundant routing network, the loop-back interface is always accessible when routing topology
changes or ip interfaces go down.
Alcatel.Lucent-ESD
Calabasas/CA./USA
User Definable Loopback Interface
Sever Load Balancing (SLB)
The main advantage of Loop-back interface is a more reliable Network Management path through
OmniVista or an NMS station.
Loopback0 is the name assigned to an IP interface to identify a consistent address for network
management purposes. The Loopback0 interface is not bound to any VLAN; therefore it always
remains operationally active. This differs from other IP interfaces, such that if there are no active ports
in the VLAN, all IP interfaces associated with that VLAN are not active. In addition, the Loopback0
interface provides a unique IP address for the switch that is easily identifiable to network management
applications.
There are 2 kind of server clusters:
-Server Farm: The traffic is truly destined to the Server Farm and the destination IP is the Virtual IP of
the Server Farm. Each server is also configured with a Loopback Interface for the Virtual IP
-Firewall Cluster: the traffic is not destined to the server, the server simply inspects the packet and
sends it back if accepted by the Firewall policies
Current limit of servers (on a per cluster basis) is 16.
Current limit of cluster (on a per switch basis) is 16.
20 Probes
Sever Load Balancing (SLB) Health monitoring is performed by the CPU of the Primary Management.
LOAD BALANCING HASHING
In both VIP and Condition SLB, the traffic is balanced among the servers using an hash algorithm
based on IPSA and IPDA.
Internally, each active server is seen as a host ECMP route to reach the cluster.
Therefore, the load balancing is the same than the ECMP load balancing.
Alcatel.Lucent-ESD
Calabasas/CA./USA
SERVER AVAILABILITY / PROBE
A server is detached from the cluster when:

-Disconnected, server goes to Link Down state
-Fails to respond to the probe, server goes to No Answer state
The default probe is a simple ping with 3 configurable parameters:
-period (sec)
-retry
-timeout (ms)
The switch sends a ping/probe to a server every period sec. If the server does not respond within
timeout for retry time, the server goes No Answer
With the default values (period =60 retry=3 timeout=3000), the switch can take up to 60+3*3=69
seconds to detect of server out of service
SLB Probes
In addition to Ping , the following probes are available:
-FTP: the probe checks the server runs a ftp server
-IMAP: the probe checks the server runs a mail server imap
-IMAPS: the probe checks the server runs a ssl mail server imap
-POP: the probe checks the server runs a mail server pop3
-POPS: the probe checks the server runs a ssl mail server pop3
-SMTP: the probe checks the server runs a smtp server
-NNTP: the probe checks the server runs a network news server
-HTTP: the probe checks the server runs a http server
-HTTPS: the probe checks the server runs a ssl http server
-UDP: the probe checks the server responds to a given udp port application
-TCP: the probe checks the server responds to a given tcp port application
COMMON PROBE PARAMETERS
Like ping, a probe is configured with a period, a retry and a timeout. If the server does not respond to
the probe, the server is detached from the cluster.
According to the period/retry/timeout, the switch will probe each server to make sure the server is still
running the appropriate application.
For instance, with ftp probe, the switch verifies the server is able to accept a ftp session.
PROBE PORT NUMBER
A tcp/udp port number is mandatory for TCP and UDP probes. It specifies on which port the server
must be listening for opening sessions.
For other probes, the port is optional (default port number is 0); the probes uses the well known
TCP/UDP ports:
-FTP: port 21
-IMAP: port 143
-IMAPS: port 993
-POP: port 110
-POPS: port 995
-SMTP: port 25
-NNTP: port 119
-HTTP: port 80
-HTTPS: port 443
TCP/UDP PROBES
These probes check the server can open a udp/tcp sessions on the given port
Optional parameters can be given:
-SSL : to use a secure socket layer application instead of basis tcp/ip layer
-Send/Expect : to verify the server response (expect) upon a given message (send)
HTTP/HTTPS PROBES
These probes try to load a page from the server.
The mandatory parameters are:
-url : the page the probe is trying to load
-status: the status of the page expected to be received (200 for OK, 400 for url not found ..).
Default is 200.
Optional parameters can be given:
-expect: a string expected to be seen in the content of the page
-username/password: the username/password to use when the web server requires an http
authentication
Alcatel.Lucent-ESD
Calabasas/CA./USA
Layer-3 Routing Unicast (IPv4)

Layer-3 Basic Routing Protocols
(IPv4)
Layer-3 Routing (IPX)

Residential Metro
Triple-play Ethernet Access
Large L3 table support
Routing Information Base (RIB) &

Forwarding Information Base (FIB)
Max number of IP routes

Max number of IP static routes
RIPv1&v2
IP Routing
Static routing
RIP v1 & v2
Multicast
IGMP v1, v2 & v3 snooping
Network Protocol
TCP/IP stack
ARP
DHCP relay
Generic UDP relay per VLAN
IP Routing
Static routing
RIP/SAP
DHCP Option 82 relay agent information
Q-in-Q (Vlan stacking)
Ethernet OAM compliant with 802.1ag version 7.0
Hardware:
Maximum number of active flows in the hardware: 12K

One active flow is usually one remote-subnet flow (not a per destination ip flow based)
Now with the ARP table enhancement, one active flow can also be a host routed flow
The table is shared for
- IPV4 active flow (remote ipv4 network): 1 entry
- IPV6 active flow (remote ipv6 network): 2 entries
- Host active flow (ARP entry): 1 entry
Maximum number of active ARP entries flows: 12K
Maximum number of ECMP Next-hops that can be stored: 512

Software:
Maximum number of IPv4 routes that can be held in the software routing table: 1024
Maximum number of ARP entries that can be held in software ARP table: 16K
Tested figures:
The IPv4 RIB and the IPv6 RIB are separate tables with different capacities.
RIB:
The RIB is 96K (IPv4).
FIB:
There are actually two IPv4 FIBs and IPv6 FIBs.
One is the software FIB which is separate for IPv4 & IPv6 and the second one is the hardware FIB
which is common for both IPv4 and IPv6.
In the hardware FIB there is room for 1024 IPv4 entries or 512 IPv6 entries.
Static Routes -1k IPv4 / 512 IPv6 and RIP Routes 1k IPv4 / 512 IPv6
1 K (1,024) routes
Maximum number of IP Routes: 1K
Maximum number of RIPv2 interfaces per router: 10
Maximum number of RIPv2 peers per router, one per interface: 10
Alcatel.Lucent-ESD
Calabasas/CA./USA
ARP Table: Max number of ARP entries per system

Layer-3 forwarding, known IP@64 bytes pkt
Layer-3 forwarding, known IP@ Jumbo pkt
Trunking 2 VLANs, 64 Bytes pkt
Up to 8K (8,192) L3 ARP entries are supported.

Wire-speed
Wire-speed
Wire-speed
Wire-speed
Wire-speed
Alcatel.Lucent-ESD
Calabasas/CA./USA
Layer-3 Routing Unicast (IPv6)

Layer-3 Routing Protocols (IPv6)
L3 table support
IPv6 routes
Max number of IPv6 static routes
IPv6 interfaces
RIPng
ARP Table: Max number of ARP entries per system
IPv6 REDISTRIBUTION
Layer-3 forwarding, known IP@ Jumbo pkt
IP Routing
Static routing
RIPng
Hardware:
Maximum number of active flows in the hardware: 12K

One active flow is usually one remote-subnet flow (not a per destination ip flow based)
Now with the ARP table enhancement, one active flow can also be a host routed flow
The table is shared for
- IPV4 active flow (remote ipv4 network): 1 entry
- IPV6 active flow (remote ipv6 network): 2 entries
- Host active flow (ARP entry): 1 entry
Maximum number of active ARP entries flows: 12K
Maximum number of ECMP Next-hops that can be stored: 512

Software:
Maximum number of ARP entries that can be held in software ARP table: 16K
The total number of IPv6 routes supported in hardware (with no IPv4 routes) is 512
512 routes
The recommended number of IPv6 interfaces is 16
The total number of RIPng interfaces is 16.
Up to 8K (8,192) L3 ARP entries are supported.
(a) Maximum number of route-maps that can be created on an OS6400 router: 200
(b) Maximum number of route-map sequences that can be created on an OS6400 router: 400
(c) Maximum number of IPv6 access-lists that can be configured on an OS6400 router: 200
Wire-speed
Wire-speed
Wire-speed
Wire-speed
Wire-speed
Alcatel.Lucent-ESD
Calabasas/CA./USA
Multinetting
Multinetting
This feature allows IP traffic from multiple subnets to
coexist on the same VLAN. A network is said to be
multinetted when multiple IP subnets are brought
together within a single broadcast domain (VLAN). It
is possible to assign up to eight different IP interfaces
per VLAN. Each interface is configured with a
different subnet.
Supported features:
A network is said to be multinetted when multiple IP subnets are brought together within a single
VLAN. For example, one may configure the subnet 192.168.1.0/24 and 194.2.10.0/24 to run on the
same switch interface. In other words, traffic from the 192.168.1.0 subnet and traffic from the
194.2.10.0 subnet would coexist on the same physical VLAN.
Within a Layer 2 environment, the traffic is broadcast between all subnets configured in the same
VLAN. Layer-3 traffic is routed between the configured subnets in the same VLAN.
Possible uses for Multinetting:
Subnet renumbering used during transition from one addressing scheme to another to
maintain connectivity.
Ability to support more hosts on one physical link used to add more hosts to a broadcast
domain than the addressing scheme allows.
Supporting multiple subnets on one interface where configurations do not allow complete
separation of subnet traffic. For example, a college campus may have departments where
users are connected to a switch via hubs. Connected to each of the hubs are users
configured to be in different subnets. The hubs are connected to the switches using portbased vlan configuration. Network administrators use Multinetting so they do not have to
worry about re-cabling or reconfiguring ports for users in different subnets.
Up to 8 subnets per VLAN
All existing dynamic routing protocols, routing between each of the multinetted subnets in
one VLAN and routing between each of the multinetted subnets and other VLANs
DHCP is only supported on the primary interface of the multinetted vlan. All devices are assigned to
the same scope (the one for the primary interface).
Layer-3 Routing (IPX)

Routes
IPX Routing
1K Routes
1K Host entries
64 IPX interfaces
Static routing (256 routes)
RIP/SAP, 1K routes
5000 RIP and SAP entries each are supported.
IPX routing is limited to 1900 packets per second per NI.
Each NI can independently route up to 1900 p/s.
Alcatel.Lucent-ESD
Calabasas/CA./USA
Policy/QoS
QoS / ACLs
Convergence / Triple Play
QoS Conditions & Actions supported
Priority Queues
Traffic Prioritization
Bandwidth Management
Queue Management
Features summary:
802.1p classification
TOS/DSCP classification
Ethertype classification
IP protocol classification
ICMP type and code classification
TCP Flag classification and established for implicit reflexive tcp flows
qos apply will not impact existing flows
Port disable rules to shutdown a port when incoming packets matches a rule
Rule logging
Port redirect action to force a packet to be sent out on a given port
User port profiles to filter and shutdown ports for BPDUs, IP spoofing and routing
protocols
DropServices to drop tcp/udp ports
IGMP ACLs
8 hardware queues per port

Traffic prioritization: Flow-based QoS with internal and external (a.k.a., remarking) prioritization
Bandwidth management: flow based bandwidth management, ingress policing/egress shaping and
port based egress shaping
Queue management: Random Early Detect/Discard (RED), configurable de-queuing algorithm; Strict
Priority, Weighted and Deficit Round Robin.
Power-over-Ethernet: IEEE 802.3af maximum total power of 390W for PoE
The following types of conditions are available:
L1 conditions: source port, destination port, source port group, destination port group
L2 conditions: source mac, source mac group, destination mac, destination mac group,
802.1p, ethertype, and source vlan (Destination vlan is not supported).
L3 conditions: ip protocol, source ip, source network group, destination ip, destination
network group, TOS, DSCP, ICMP type, ICMP code.
L4 conditions: source TCP/UDP port, source TCP/UDP port range, destination TCP/UDP
port, destination TCP/UDP port range, service, service group, tcp flags
The following actions are available:
ACL (disposition drop/accept default is accept)
Priority
802.1p/TOS/DSCP Stamping
802.1p/TOS/DSCP Mapping
Maximum bandwidth
Redirect Port
Note: Condition combinations and Action combinations are also supported.
Eight hardware based queues per port
Flow based QoS
Internal & External (aka remarking) prioritization
Port & Flow based ingress policing with 64kbps granularity
Port based egress shaping, with 64kbps granularity
Configurable de-queuing algorithm
Strict Priority
Weighted Round Robin
DRR (Deficit Round Robin). This mode is quite similar as WRR

In the Strict Priority mode, a port has 8 strict priority queues (SPQ) and all the queues on the port are
serviced strictly by priority.
In the WRR or DRR, queues are serviced on a round robin based on their weight. The higher the queue
weight, the higher is the throughput for that queue. Any queue can be configured with a weight of 0 to
make that queue strict priority. The weight ordering does not need to follow the queue order.
Alcatel.Lucent-ESD
Calabasas/CA./USA
Queuing Scheme and Servicing Mode
Queue Mapping Table
Power over Ethernet

Max number of Rules
Max number of Actions
Max number of Conditions
Max number of Policy Services
Max number of Policy Groups
Max number of Queues
Filtering or ACL Throughput
Rule logging
OS6400 has 8 queues per egress port

OS6400 has 3 Queuing schemes per egress port:
Strict-Priority (default mode)
WRR (Weighted Round Robin)
DRR (Deficit Round Robin). This mode is quite similar as WRR

In the Strict Priority mode, a port has 8 strict priority queues (SPQ) and all the queues on the port are
serviced strictly by priority.
In the WRR or DRR, queues are serviced on a round robin based on their weight. The higher the queue
weight, the higher is the throughput for that queue. Any queue can be configured with a weight of 0 to
make that queue strict priority. The weight ordering does not need to follow the queue order.
Queue Mapping Table
802.1p
TOS / DSCP
Priority Rule
Egress Queue
0
0 / 0-7
0
0
1
1 / 8-15
1
1
2
2 / 16-23
2
2
3
3 / 24-31
3
3
4
4 / 32-39
4
4
5
5 / 40-47
5
5
6
6 / 48-55
6
6
7
7 / 56-63
7
7
(*) SPQ Strict Priority Queue or Weighted Fair Queue if configured with a weight > 0
IEEE 802.3af (requires OS9-GNI-P24 & IP-Shelf)
128 per port; 2048 policy rules per chassis
128 per port; 2048 policy actions per chassis
128 per port; 2048 policy Conditions per chassis
256
1024
512 entries per policy group
8 / port
Wire-speed
OS6400 can log the packets matching a policy rule.
The most common use of that feature is to log packet matching an ACL drop policy. To enable logging
configure the policy rule with log [log interval x]
The log interval is optional and the default interval is 30 sec.
You can configure a log interval between 1 and 3600 sec.
Depending on the configured log interval, the system periodically set the hardware to send copy of the
packet matching the rule to CPU. As soon as the CPU receives a packet matching the rule, the system
reset the hardware to no longer send copy to CPU until the next interval, to keep CPU low.
The first packet is always logged. If one packet matching the rule is seen during the log interval time, it
will be logged.
Limitation:
More than one packet can be logged depending on the rate of the traffic (because of time
required by the CPU to stop the sampling).
Log interval less than 5 seconds will be accepted by CLI , but logging will be done every 5
sec
Logging does not lot all matching packets (not an IDS)

Note: CPU stays low with rule logging enable. We tested a logging drop rule with 10 Gbps of
incoming traffic and CPU stays low.
Alcatel.Lucent-ESD
Calabasas/CA./USA
Servicing
SPQ or W
SPQ or W
SPQ or W
SPQ or W
SPQ or W
SPQ or W
SPQ or W
SPQ or W
Egress Bandwidth Shaping
Ingress Max Bandwidth Policing
Untrusted Ports and Packet Priority
Trusted Ports and Packet Priority
Port shaping
Shaping limits the bandwidth on the egress port. Shaping implies that the shaping function controls the
rate at which the egress port sends the packets, regardless of egress queues. The granularity is 64Kbps.
Queue shaping
You can also configure maximum and minimu bandwidth on a per egress queue basis.
Configuring an egress queue max bandwidth will shape priority traffic mapped to that queue.
Configuring an egress queue min bandwidth will guarantee that bandwidth for priority traffic mapped
to that queue.
When a queue has a minimum bandwidth configured, traffic within that bandwidth has the HIGHEST
priority, regardless the servicing mode or the priority of that queue.
Limitation:
The egress bandwidth shaping is only on a per port basis; the system cannot do a per flow basis egress
bandwidth shaping.
Using policy rule with maximum bandwidth action, you can limit the bandwidth on the ingress.
Policing implies dropping the traffic when the programmed rate is exceeded. Policing is on a per flow
basis. The granularity is 64kpbs.
You can do the following:
Ingress port rate limiting by configure a policy using a source port
Ingress flow based rate limiting by configure a policy defining that flow
Mixed of ingress and flow based rate limiting

Limitations:
Ingress rate limiting is done at the ingress NI. Policies spread out on multiple NIs will make
the total egressing rate to be higher than the configured value (up to the N time the limit
where N is the number of NI being spread)
Show active policy rule will count the packets that exceed the rate limiting, not the
packets that matches the rule
On untrusted ports the priority/queue of the incoming packet is based on the port default 802.1p
value. By default, the port default 802.1p value is 0 making traffic to be mapped to Q0 (best effort).
Also, regardless or bridging or routing:
802.1p within the packets is set to the port default 802.1p
DSCP within the packets is set to the port default dscp

Changing the port default 802.1p will:
Change the priority of all traffic from that port. That is like a port priority
Set the 802.1p value in the packet to that port default 802.1p
Changing the port default DSCP will:
NOT change the internal priority
Set the DSCP value in the packet to that of the port default DSCP
Notes:
On untrusted port, the default 802.1p defines the default internal priority for all packets.
Untagged packets on untrusted ports get an 802.1p value from the port default 802.1p (if going out on
tagged interface).
Limitation:
On untrusted ports, if the packet matches a policy rule, the DSCP in the packet is unchanged; it is not
set to the port default dscp
On trusted ports the priority/queue of the incoming packet is based on the ingress packet 802.1p or
ToS/DSCP value.
Non IP packets are prioritized based on the packet 802.1p value
IP packets are prioritized based on the packet TOS/DSCP value

Port default 802.1p or DSCP has no effect on trusted ports.
Notes:
On IP packets, the 802.1p is set to match the packet ToS value.
Untagged non-IP packets always get an 802.1p of 0 and priority 0 (if going out on tagged interface).
The port default 802.1p is not applied.
Alcatel.Lucent-ESD
Calabasas/CA./USA
802.1p/TOS/DSCP Stamping/Mapping policies
Policy Based Routing
Policy Based Routing (Permanent Mode)
Policy Rules with Multiple Actions
QoS Precedence with Multiple Policy Rules
Regardless the condition or classification, the following stamping/mapping actions are allowed
Stamp 802.1p
Stamp TOS (precedence)
Stamp DSCP
Stamp 802.1p and TOS/DSCP
Map 802.1p to 802.1p
Map 802.1p to TOS
Map 802.1p to DSCP
Map ToS to 802.1p
Map ToS to TOS
Map ToS to DSCP
Map DSCP to 802.1p
Map DSCP to TOS
Map DSCP to DSCP

Stamping/mapping policies change the internal priority of the packets:
Internal Priority is always based on the new 802.1p or TOS/DSCP being stamped/mapped
Stamp/map TOS/DSCP also gives internal priority for non IP packets matching the rule
Mapping rules takes one TCAM rule entry for each entry in the map group
If both 802.1p and TOS/DSCP are stamped in a policy rule, priority is based on the stamped
802.1p value
Notes:
On trusted ports, stamping/mapping a tos/dscp also change the 802.1p value in the packet to the packet
ToS value.
If the policy rule has both a 802.1p stamp/map action and a priority action, the packet priority comes
from the stamped/mapped 802.1p value, not the priority action.
Policy Based Routing (PBR) allows a network administrator to define QoS policies that will override
the normal routing mechanism for traffic matching the policy condition.
Note. When a PBR QoS rule is applied to the configuration, it is applied to the entire switch, unless
you specify a built-in port group in the policy condition. Policy Based Routing may be used to redirect
traffic to a particular gateway based on source or destination IP address, source or destination network
group, source or destination TCP/UDP port, a service or service group, IP protocol, or built-in source
port group. Traffic may be redirected to a particular gateway regardless of what routes are listed in the
routing table.
Note that the gateway address does not have to be on a directly connected VLAN; the address may be
on any network that is learned by the switch.
Note. If the routing table has a default route of 0.0.0.0, traffic matching a PBR policy will be redirected
to the route specified in the policy. Policy Based Routing may be used to redirect untrusted traffic to a
firewall. In this case, note that reply packets will be not be allowed back through the firewall.
Policy Based Routing may be used to redirect traffic to a particular gateway based on source or
destination IP address, source or destination network group, source or destination TCP/UDP port, a
service or service group, IP protocol, or built-in source port group. Traffic may be redirected to a
particular gateway regardless of what routes are listed in the routing table.
Note that the gateway address does not have to be on a directly connected VLAN; the address may be
on any network that is learned by the switch.
Multiple policy actions can be combined together within a single rule. The policy actions that can be
combined in the same rule are:
Priority
Stamping/mapping
Max BW
Redirect Port
A flow can match multiple rules but ONLY the action for the highest precedence-matching rule is then
enforced. When rule are configured without precedence (default precedence is 0), the first created rule
has the highest precedence.
Alcatel.Lucent-ESD
Calabasas/CA./USA
IPv6 Classification & Combinations
IPv6 Actions
User-port shutdown profile
Port Disable
Policy Based Routing
Classification & Combinations

The following classification criteria are available (in Release 6.1.3.r01) for ipv6 packets
source ipv6 address
destination ipv6 address
Next header. Policies specifying the NH parameter, classify based on the first NH value
present in the V6 header of the IPV6 packet
Flow label
TCP Flags/Established. Policies specifying established or tcpflags, expect the first NH

value present in the V6 header to be 6
ToS/DSCP
source vlan
802.1p
source Mac
destination Mac
source port
destination port (only for bridged traffic)

Actions
All actions are available for Ipv6 policies
ACL (disposition drop/accept default is accept)
Priority
802.1p/TOS/DSCP Stamping
802.1p/TOS/DSCP Mapping
Maximum bandwidth/depth
Redirect Port / Link aggregation

Instead of filtering packets, you can configure a user-port profile to administratively disable an
interface upon reception of spoof/bpdu/rip packets. To make the interface operational again, the port
must be unplugged/plugged back or disabled/enabled using interfaces s/p admin down and
interfaces s/p admin up. Also, a SNMP trap will be sent when an interface goes down because of the
user-port shutdown profile.
You can configure a Port Disable rule to administratively disable an interface when matching a
policy rule. To make the interface operational again, the port must be unplugged/plugged back or
disabled/enabled using interfaces s/p admin down and interfaces s/p admin up.
Also, a SNMP trap will be sent when an interface goes down when matching a port disable rule
Policy routing allows the user to specify gateways to be used for routed data flows based on various
criteria.
IP Protocol (i.e. ICMP, TCP, ICMP)
Source IP address (or network group)
Destination IP address (or network group)
Source TCP/UDP port
Destination TCP/UDP port
Souce TCP/UDP service
Destination TCP/UDP service
Source TCP/UDP service group
Destination TCP/UDP service group
TOS, DSCP
Source vlan
Source slot/port
Source slot/port group

The action that can be specified is a gateway to be used overriding the routing database.
Permanent gateway is supported in 6.1.1.R02, alternate gateway is not supported. Permanent gateway
can be set to local next hop IP or remote hop IP.
PBR is done in hardware.
Note regarding bridged data flows
PBR is also supported on bridged packets if a static ARP is configured for the permanent gateway.
That way you can force bridged packets to be routed to that permanent gateway.
Alcatel.Lucent-ESD
Calabasas/CA./USA
High Availability
High Availability
The switch provides a broad variety of availability
features. 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 day-to-day
network operations.
Smart Continuous Switching: Hot Swap, Management Module Fail-over, Power

Monitoring, Redundant subsystems in stacked configurations, and Stackability
Virtual chassis design that provide management functionality and automatic election of
primary and secondary managers
Redundant Management & Switch Fabric (stacking configuration)
o
Virtual chassis that provides management functionality and automatic election
of primary and secondary managers
Fault tolerant loop stacking (Redundant Stacking link)
Hot swappable components & hot insertable support: switch modules, SFPs/XFPs
o
Hot swappable switch units and power supplies
Redundant (Backup) Power Supplies (Redundant 1:1 power provided by the OS6400-BPS)
Redundant 1: 1 PoE power provided by the PoE Power Supplies
Spanning Tree robustness (Single or Multiple STP options): IEEE 802.1D (STP) (802.1D
spanning tree for loop free topology and link redundancy) and IEEE 802.1w-Rapid
Reconfiguration of Spanning Tree (allows sub-second failover to redundant link)
o
Ring Rapid Spanning Tree optimized for ring topology to provide less than
100ms convergence time
o
IEEE 802.1s multiple spanning tree and Alcatel per-VLAN spanning tree (1x1)
o
PVST+
Fast forwarding mode on user ports to bypass 30-second delay for spanning tree
Prevents unauthorized spanning-tree enabled attached bridges from operating.
BPDU blocking automatically shuts down switch ports being used as user ports if a
spanning tree BPDU packet is seen. Prevents unauthorized spanning-tree enabled attached
bridges from operating.
Priority queues: eight hardware-based queues per port
Dynamic link aggregation IEEE 802.3ad (that supports automatic configuration of link
aggregates with other switches) with resilient uplink capabilities
Static link aggregation with OmniChannel (that supports automatic configuration of link
aggregates with other switches)
IEEE 802.1s: MISTP (802.1s) is an IEEE standard which allows several VLANs to be
mapped to a reduced number of spanning-tree instances. This is possible since most
networks do not need more than a few logical topologies. Each instance handles multiple
VLANs that have the same Layer 2 topology.
Software Resiliency: The AOS OmniSwitch product family provides fully redundant and
resilient system components to insure continuous, non-stop operation. This includes
redundant subsystems, hot swappable modules, load-sharing components, hitless software
loading, downloadable bootstrap, and image rollback which allows the system to
automatically re-load previous configurations and software versions.
o
Software image and configuration recovery (Software Rollback)
Image rollback to automatically re-load previous configurations and

software versions
o
Image and configuration synchronization for Management Modules
o
Hitless loading of optional advanced routing software without re-booting
Broadcast storm control
Downloadable bootstrap
Chassis thermal protection/shutdown
Hardware monitoring, temperature monitoring, and power monitoring & management
Short cold and warm boot times
Built-in security and device hardening
Topological Network Redundancy: In order to provide the highest levels of availability
throughout an enterprise, it is important to build redundancy and resiliency into the
topology at the network level to insure that links have backups and traffic is always
flowing. This includes:
o
Physical redundancy
o
Layer 2 and layer 3 redundancies
Alcatel.Lucent-ESD
Calabasas/CA./USA
Security
Advanced Security
The following is only a highlight of the advanced security features supported:
Partitioned Management PM: Protected multiple user access control (i.e. the switch
provides a full suite of commands that allow the user to create and modify User IDs and
Passwords (multiple administrative profiles) for access to switch management). The PM
feature utilizes an on-board database, or RADIUS, LDAP authentication servers (user
profiles are stored within these servers).
Authenticated Switch Access (ASA): the ASA feature (user access control or device access
control) with Secure Access Logging (AAA service) utilizes an on-board database,
RADIUS, LDAP, or ACE authentication servers
Automatic Log-out based on a pre-configured timer
Denial of Service Attack Defense (DOS protection)
IEEE 802.1x industry standard port based authentication challenges users with a password bef
allowing network access
o
IEEE 802.1x multi-client, multi-VLAN support for per-client authentication and
VLAN assignment
IEEE 802.1x with group mobility
IEEE 802.1x with MAC based authentication, group mobility or

guest VLAN support
MAC-based authentication for non-802.1x host
Alcatel-Lucent Access Guardian support
Port Mapping (Private VLANs)
Port Binding
Authenticated VLAN that challenges users with username and password and supports
dynamic VLAN access based on user
Support for host integrity check and remediation VLAN
Security through the implementation of OmniVista Quarantine Manager (OV2770-QM)

and quarantine VLAN, with OneTouch Security automation
PKI authentication for SSH access
Learned Port Security or MAC address lockdown allows only known devices to have
network access preventing unauthorized network device access
RADIUS and LDAP admin authentication prevents unauthorized switch management
TACACS+ client allows for authentication-authorization and accounting with a remote

TACACS+ server
Secure Shell (SSH), Secure Socket Layer (SSL) for HTTPS and SNMPv3 for encrypted
remote management communication
Access Control Lists (ACLs) to filter out unwanted traffic including denial of service
attacks; Access control lists (ACLs) are per port, MAC SA/DA, IP SA/DA, TCP/ UDP
port; Flow based filtering in hardware (L1-L4)
Support for Access Control List Manager (ACLMAN)
Supports Microsoft Network Access Policy (NAP) protocol
Switch protocol security

o
MD5 for RIPv2 and SNMPv3
o
SSHv2 for secure CLI session with PKI support
o
SSLv3 for secure HTTP session
DHCP Snooping, DHCP-option 82, and DHCP IP Spoof protection
Alcatel.Lucent-ESD
Calabasas/CA./USA
Switch accessibility under DoS Attack
IP security enhancement
802.1X/Device Authentication
The following type of packets are processed in software and will increase the CPU usage:
Unresolved L3 packet: unknown destination IP on a local subnet
Broadcast L2 packet (including ARP requests):
All IP packets going to a switch ip interfaces: ping, telnet, http

Under normal conditions, the protocol packets are always prioritized in order to maintain the network
topology. The following protocol packets are by default prioritized:
BPDUs
RIPv2
IP multicast protocol (IGMP...)
ARP (both request and reply)

ARP
To prevent an ARP attack, the system limits at 500 pps the number of arp packets sent to CPU
(flooding of arp on the network is not limited). Also, there is an early arp discard mechanism to
prevent the CPU from processing arp request not destined to a switch ip address. However, under
attacks towards the switch, the CPU usage could rise dramatically and makes the switch unreachable
for management (WebView, OmniVista or Telnet). In order to keep the switch reachable under attacks,
some policies can be created to protect the management access.
Detect ARP Flood
Detect packets received with invalid Source IP addresses
Detect packets received with invalid Destination IP addresses
Detect multicast packets with a source MAC that is multicast
Detect multicast packets with mismatching destination IP and MAC address
Detect multicast packets with a Unicast destination IP and Multicast destination MAC
address
Detect ping overload
Detect packets with Loopback source IP address

There are 4 levels of 802.1x/device classification:
-Basic 802.1x port. Only successful authenticated 802.1x devices are allowed in the network
-Basic 802.1x port + fail authentication policies. Only 802.1x capable devices are allowed in the
network. These policies allow the failed authenticated 802.1x devices to access non-secured (or non
authenticated) VLANs
-802.1x + non supplicant policies without Mac authentication. Non 802.1x devices are allowed on nonsecured VLANs according to the non-supplicant policies.
-802.1x + non supplicant policies with Mac authentication. In this mode, the non 802.1x devices will
follow either the non-supplicant authentication pass policies when the Mac
authentication is successful or the non-supplicant authentication fail policies when the Mac
authentication failed
The open-unique and open-global options are no longer applicable.
Device Authentication:
Maximum number of supplicants / non-supplicant users per system: 1024
Maximum number of non-supplicant users per port: 1024
Maximum number of supplicant users per port: 253
Maximum combined number of supplicant and non-supplicant users per port: 1024
The system supports up to 1024 authenticated/mobile Mac-addresses.
Supported/non-supported mobile rule on device authentication:
1. Support rule per tagged/untagged packet type.
Mac rule apply on UNTAGGED packet
IP subnet rule apply on UNTAGGED packet
Protocol rule apply on UNTAGGED packet
Port-protocol binding rule apply on UNTAGGED packet
Mac-port binding rule apply on UNTAGGED packet
Mac-IP-port binding rule apply on UNTAGGED packet
Mobile-tag apply on TAGGED packet
* Mobile tag only apply on tagged packets, all other rules apply on untagged packet.
2. DHCP related mobile rules are not supported with device authentication (i.e. supplicant/nonsupplicant cases)
DHCP generic rule
DHCP port rule
DHCP Mac / Mac range rule
Device authentication with Alcatel-Lucent IP phone:
Alcatel-Lucent Dynamic IP phone has 3 modes:
1.Untagged dynamic
Packet is always untagged.
2.Tagged dynamic
Packet is always tagged based on administrator config on phone.
Alcatel.Lucent-ESD
Calabasas/CA./USA
ACLMAN
DHCP Snooping
Traffic Filtering
User Authentication
Switch protocol security
Switch management
User-port shutdown profile
Port Disable
3.Alcatel-Lucent dynamic
First packet is untagged, second packet onward is tagged.
ACLMAN is a function of the QoS subsystem in AOS. ACLMAN allows a network administrator to
manage ACLs using default industry standard syntax on Alcatel-Lucent switches. To enforce the
ACLs, ACLMAN translates default industry standard syntax into Alcatel-Lucent QoS filtering policies
in a manner transparent to the ACLMAN user.
ACLMAN provides the following:
The ability to import text files from flash containing default industry standard ACL syntax
An interactive shell emulating the default industry standard CLI ACL command syntax
ACLMAN supports the following default industry standard ACL types:
Standard ACLs
Extended ACLs
Numbered ACLs
Named ACLs
Number of DHCP Bindings per ASIC: 126
Number of DHCP Bindings per port: 126
Flow based filtering in hardware (L1-L4)
IEEE 802.1x, with Group Mobility & Guest VLAN support
MAC based Authentication for non-802.1x host
Authenticated VLAN (web & telnet based authentication)
MD5 for RIPv2 and SNMPv3
SSH for secure CLI session and SSL for secure HTTP session
Local authentication database
Remote authentication RADIUS, LDAP & ACE servers
Instead of filtering packets, you can configure a user-port profile to administratively disable an
interface upon reception of spoof/BPDUs/rip packets. To make the interface operational again, the port
must be unplugged/plugged back or disabled/enabled using interfaces s/p admin down and
interfaces s/p admin up. Also, a SNMP trap will be sent when an interface goes down because of the
user-port shutdown profile.
Also, a SNMP trap will be sent when an interface goes down when matching a port disable rule
Alcatel.Lucent-ESD
Calabasas/CA./USA
Denial of Services (DOS) attacks
The system sustained Denial of Services attacks from Nessus and no switch anomalies (crash or
service interruptions) were observed while running the attacks. Nessus has reported the following
vulnerabilities:
alya.cgi (Backdoors)
AnalogX denial of service (Denial of Service)
cisco http DoS (Denial of Service)
AnalogX denial of service by long CGI name (Denial of Service)
Jigsaw webserver MS/DOS device DoS (Denial of Service)
Trend Micro OfficeScan Denial of service (Denial of Service)
BadBlue invalid GET DoS (Denial of Service)
DCShop exposes sensitive files (General)
OpenSSH < 3.0.1 (Gain a shell remotely)
Quicktime/Darwin Remote Admin Exploit (Gain a shell remotely)
OpenSSL overflow via invalid certificate passing (Gain a shell remotely)
TESO in.telnetd buffer overflow (Gain root remotely)
OpenSSH AFS/Kerberos ticket/token passing (Gain root remotely)
OpenSSH <= 3.3 (Gain root remotely)
OpenSSH < 3.7.1 (Gain root remotely)
Oracle Application Server Overflow (Gain Root Remotely)
AliBaba path climbing (Remote file access)
Note:
The Nessus suite was tested under the following platform.
The following are the versions of Nessus and the Linux platform used.
Nessus version: 2.2.0
Linux OS: Fedora Core Release 1
The reported failures are not a threat but a check against the switch which the test Nessus suite
reported as vulnerable. For example, when running port scan Nessus will report failures against ports
that should not respond or be open but are internal ports leveraged by the subsystem. As the report
stated there is no anomalies detected or crashes from the scan.
Alcatel.Lucent-ESD
Calabasas/CA./USA
Management
Configuration Mode
The following is only a highlight of the advanced network and switch management features supported
by the OmniSwitch 6400 Series:
OmniVista NMS: Alcatel-Lucents Single voice, data and services network management
including OneTouch QoS and SecureView.
Carrier-Class Dynamic Mobility
Through the application of a comprehensive QoS feature set, the AOS OmniSwitch product
family is capable of supporting converged applications such as the VoIP
Diagnosing Switch problems:

o
Port Mirroring; Port based, port mirroring for troubleshooting, supports two (2)
sessions with multiple sources-to-one destination configuration
o
Port monitoring feature that allows capture of Ethernet packets to a file, or for
on-screen display to assist in troubleshooting
o
SFlow v5 support to monitor and effectively control and manage the network
usage
o
RMON: Supports RFC 2819 RMON group (1-Statistics, 2-History, 3-Alarm,
and 9-Events)
o
Switch Health
o
Monitoring Memory Tools & Switch Configuration
o
Switch Logging
Logging into the Switch through Telnet, FTP, HTTP, SSH, SSL, and SNMPv1&v2&v3
o
Remote telnet management or secure shell access using SSH
o
o
SNMPv1/v2/v3
Authentication or AAA Servers
Policy Servers; Authentication Servers such as RADIUS, LDAP, and ACE servers
Policy-Based Management with LDAP Directory Services
System File Management
Dual image and dual configuration file storage provides backup
Intuitive Alcatel-Lucent CLI for familiar interface and reduced training costs
WebView Element Mgmt: Easy to use point & click web based element manager with
built-in help for easy configuration of new technology features
Remote telnet management or secure shell
Human readable ASCII based config files for offline editing and bulk configuration
Managing Switch Users Accounts & Partitioned Management feature
Managing Switch Security
IGMPv1/v2/v3 snooping to optimize multicast traffic
BootP/DHCP client allows auto-config of switch IP information to simplify deployment
Auto-negotiating 10/100/1000 ports automatically configure port speed and duplex setting
Auto MDI/MDIX automatically configures transmit and receive signals to support straight
thru and crossover cabling
DHCP relay to forward client requests to a DHCP server
DHCP Option-82 & DHCP Snooping
Integration with SNMP manager OmniVista for network wide management
System event log
Network Time Protocol (NTP) for network wide time synchronization
Alcatel-Lucent Interswitch Protocols (AIP)

o
AMAP: Alcatel-Lucent Mapping Adjacency Protocol (AMAP) for building
topology maps within OmniVista
o
802.1AB with MED Extensions / LLDP-MED

Command Line Interface (CLI), Telnet/SSH for remote CLI access, Web-based (HTTP/HTTPS)
and SNMPv1/v2c/v3 for complete NMS integration
Alcatel.Lucent-ESD
Calabasas/CA./USA
Management Access types

Seriral & In-band
System Maintenance
System file Transfer

Max number of users in local database
Max number of users in LDAP/RADIUS/ACE Server
database (depends on server capabilities)
Max number of SNMP users (login)
Max number of simultaneous SNMPv3 requests
Max number of simultaneous HTTP sessions
Max number of simultaneous Telnet sessions
Max number of simultaneous FTP sessions
Max number of simultaneous Syslog servers
Max number of simultaneous
SSH Telnet / FTP sessions
Max number of simultaneous User Login sessions
Max number of simultaneous Authentications
sessions (A-VLAN, A-ACL with RADIUS)
Max number of authenticated ports
Port Disable
SNMP Traps
Port Monitoring
Port Mirroring
Serial Console port for local & remote (modem dial up) access (RJ45)
Console Port / Serial Connection:
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.
In-band Ethernet access

Port Mirroring (one-to-one, many-to-one)
RMON (Remote Monitoring): Statistics, History, Alarm & Events, and sFlow
Local & Remote logging (Syslog)
Detailed Statistics / Alarm / Debug information per process
L3 OAM (ICMP Ping and Traceroute)
NTP (Network Time Protocol)
Internal flash (Compact Flash) to feature:
Working Directory
Certified Directory
XModem and FTP (File Transfer Protocol) / SFTP (Secure FTP) / SCP
65
Greater than 1000
50
50
4
4
4
4 concurrent sessions
Syslog to Multiple Hosts: You can send Syslog files to multiple hosts, up to a maximum of 4 servers.
8
13
30
48
Also, a SNMP trap will be sent when an interface goes down when matching a port disable rule.
A pktDrop SNMP trap will be sent out to the SNMP station when a port goes down because of a
user-port shutdown profile or a port disable rule.
The same unit cannot support both mirroring and monitoring configuration i.e. a user cannot have a
port monitoring and a port mirroring session on the same unit
Only one monitoring session at a time across the entire system
Only the first 64 bytes of the packet can be monitored. Due to the port monitoring file size, the system
can only store the first 2K packets (i.e. 140K/64 = 2187)
Enabling the monitoring function affects the performance. As every single monitored packet is
enqueued to the CPU, the Q-Dispatcher has to de-queue and look at each and every packet to
determine if the destination is PMM (port monitoring module). The performance will be limited by the
efficiency of Q-Dispatcher de-queuing speed and also the speed at which PMM can get the packets
from Q-Dispatcher through IPC. Due to the performance limitations, monitoring wire rate traffic is not
possible at this time.
The packets coming to CPU are always tagged and undergo the same FFP modifications as mirroring
Port Monitoring not supported on Link Aggregation
The N-to-1 port mirroring allows the user to specify multiple numbers of ports, range of ports as
mirrored source in a single command. However the maximum number of mirror source ports could be
set to 128 for the current release. A user can mirror multiple 10GigE towards 1 port GigE. Of course if
more than 1 GigE of traffic we don't expect one to mirror more that the port can deliver
Aggregate ports are allowed to be mirrored on the physical ports. Mirroring on the logical link
aggregated port ID is not supported.
In mirroring, the packet coming out of mirroring port may be different from the ingress packet, based
on the type of switching. For all types of mirroring, the mirrored packet carries the FFP (Fast Filtering
Processor) modification, mirrored packet may get modified.
To mirror port 1/1 to port 1/4, you can choose the following options:
In-port
Out-port
Bi-directional
Alcatel.Lucent-ESD
Calabasas/CA./USA
Port Mapping
(AKA Private VLAN)
Allows traffic segregation at L2
User ports in the same session cannot talk
to each other
Note: this feature is part of
Residential bridging features
SCP (Secure Copy)
SFLOW
Port Mapping is a security feature that controls peer users from communicating with each other. A Port
Mapping session comprises a session ID and a set of user ports and/or a set of network ports. User
ports within a session cannot communicate with each other and can only communicate via network
ports. In a Port Mapping session with user port set A and network port set B, ports in set A can only
communicate with ports in set B. If set B is empty, ports in set A can communicate with rest of the
ports in the system. A port mapping session can be configured in unidirectional or bidirectional mode.
In the unidirectional mode, the network ports can communicate with each other within the same
session. In the bidirectional mode, the network ports cannot communicate with each other. Network
ports of a unidirectional port mapping session can be shared with other unidirectional sessions, but
cannot be shared with any sessions configured in bidirectional mode. Network Ports of different
sessions can communicate with each other.
Port Mapping Specifications:
Ports Supported: Ethernet (10 Mbps)/Fast Ethernet (100 Mbps)/Gigabit Ethernet (1 Gb/1000 Mbps).
Mapping Sessions: Eight sessions supported per standalone switch and stack.
Port Mapping Defaults:
Mapping Session: Creation: No mapping sessions
Mapping Status configuration: Disabled
Port Mapping Direction: Bi-directional
SCP command can be used to get/put the file from/to the server.
The scp CLI command is available for copying files in a secure manner between hosts on the network.
The scp utility performs encrypted data transfers using the Secure Shell (SSH) protocol. In addition,
scp uses available SSH authentication and security features, such as prompting for a password if one is
required. Since OS6400/OS6800/OS6850 does not have any SCP-daemon running on the switch,
therefore this feature only works when OS6400/OS6800/OS6850 works as a client instead of the
server. This feature has been validated with SSH 4.0 on Solaris and Linux platforms. Since SSH 4.0
contains SCP, SFTP and SSH features, therefore the system allows the network administrator to create
the local user database to specify all domain or family of features (i.e. the family of feature that a user
can have access). When a user is being created, all allowed access need to be defined.
SFlow is a network monitoring technology that gives visibility to the activity of the network, by
providing network usage information. It provides the data required to effectively control and manage
the network usage. SFlow is a sampling technology that meets the requirements for a network traffic
monitoring solution.
SFlow is a sampling technology embedded within switches/routers defined in RFC 3176. It provides
the ability to monitor the traffic flows. It requires an sFlow Agent running in the Switch/Router and a
sFlow collector which receives and analyses the monitored data.
SFlow agent running on the OS6400, combines interface counters and traffic flow (packet) samples on
all the configured interfaces into sFlow Datagrams that are sent across the network to an sFlow
collector (3rd Party software). Packet sampling is done in hardware and is non-CPU intensive.
Current release (6.1.3r01) will not support IPv6 as Collector.
The switch sends the first 128 bytes of the sampled packet from which the entire layer 2/3/4
information can be extracted by the receiver. This could include:
- Source/Destination Mac address
- Source IP/ Destination IP
- Source/Destination TCP/UDP/ICMP port
- Source/Destination Physical port (Gigabit Port)
- IPv4/IPv6
- RIP (OK, but if this info. falls within the first 128Bytes of the packet)
- VLAN
- QoS 802.1Q, ToS and DiffServ (DSCP)
- Data Payload (OK, but if this information falls within the first 128 Bytes of the packet)
- Others (If this information falls within the first 128 Bytes of the packet)
Given an IP Address the SFLOW sampling information can be sent to a Collector such as the InMon
and/or the Crannog.
Alcatel.Lucent-ESD
Calabasas/CA./USA
SFLOW Back-off Algorithm
TACACS+
Since the CPU of switch is involved in the datagram processing, there is a built in back-off algorithm
which will automatically adjust the sampling rate in the case of CPU congestion on switch.
This back-off mechanism is not user-configurable in Release 6.1.3r01. If CPU is congested it
automatically continues to double the sampling rate, and will continue to do so up to a very low rate of
1 sample in 2147483647 (2exp31)-1. For a 1Gig interface, the bit rate is 1,000,000,000 bits per second.
The back-off algorithm is designed to take effect when the sample rate exceeds 10 samples per second
on any interface. Since each sample is configured by default for 128bytes this is 10x128x8 or 10
samples/sec x 1024 bits/sample or 10x1024 bps
1Gbps / 10x1024 bps = 97656 sampling rate.
Sampling with all available slot/ports at 10G wire-rates on OS9000 and all ports at 1G on the OS6850
keep backing-off up to 2,147,483,647 and stay fixed at this value until the traffic generation is halted
or reduced. That is even running only one 1G interface at wire rate on the OS6850 will back-off to
2147483647 and stay at this (maximum, safe) sampling rate.
Recommended sampling rates for various speeds at various load:
Link Speed
Sampling Rates
Medium
Heavy
Light Load Load
Load
10Mb/s
256
512
8192*
100Mb/s
512
1024
65536*
1Gb/s
1024
2048
Max*
10Gb/s
2048
4096
Max*
*8192 is the empirical value found in the lab for 10Mbs, 65536 for 100 Mbps
*Max: because the OS6850 always backs-off to a max sampling rate of 2147483647 for wire rate at
these rates. All other values are those recommended by Inmon. Whatever the configured sampling rate,
the back-off mechanism will set the meanskipcount higher or lower depending on what is the
unaffecting sampling rate for the CPU.
Release 6.3.3.R01 is the first release to support TACACS+ AAA.
AOS implementation is based on the Tacacs+ Protocol: draft-grant-tacacs-02.txt, January 1997.
Overview:
ASA or Authenticated Switch Access to AOS OmniSwitch running 6.1.3.R01 can be configured to add
servers and forward AAA requests to TACACS+. TACACS+ servers are configured similar to
RADIUS or LDAP servers; however, (MD5) encryption key is optional.
AAA authentication and accounting services must be configured to point to the desired TACACS+
server. It is possible to set authentication and authorization to one TACACS+ server and accounting
requests to a different server.
The number of configurable servers and fail over to second server is uniform across all AAA server
types: Up to 4 servers can be configured and all queries will be sent to the 1st server only. If 1st server
is online and user exists on 2nd server, the result will be failed authentication. If the 1st server is down,
authentication and authorization requests will only be sent to next available server. If all servers are
down, all logins will fail.
Different AAA services can be configured to query different authentication servers. All services may
use a common authentication protocol or mix of supported protocols: Telnet service may be configured
to query RADIUS while http/ftp may be configured to query TACACS+. Or all may query RADIUS.
Or all may query TACACS+. In all cases accounting server protocol must match
authentication/authorization server protocol.
AOS TACACS+ does not support authentication for network or windows domain access. Only AOS
switch access with Partition Management type domain family attribute/value pairs is supported.
This to say different users or groups of users may be assigned various levels of AOS switch
management privileges.
The TACACS+ servers run as an external server on Unix or Windows. We have tested with CISCO
TACACS+ freeware for Unix and Ciscos Secure ACSv4.0
TACACS+ uses TCP instead of UDP. Each login and supported command is queried back to the server
for authorization.
TACACS+ configuration is fully supported with AOS WebView.
Notes:
Tacacs+ supports Authenticated Switch Access and cannot be used for user authentication.
Authentication and Authorization operations are combined together and cannot be performed
independently. This implies that when Tacacs+ authentication is enabled, Tacacs+ authorization is also
enabled. Disabling Tacacs+ authentication automatically disables authorization.
A maximum of 50 simultaneous Tacacs+ sessions can be supported, when no other authentication
mechanism is activated. This is a limit enforced by the AAA application.
Alcatel.Lucent-ESD
Calabasas/CA./USA
Power over Ethernet
The Standard in brief
In IEEE 802.3af standard, POE transmits power over the same pair as the data.
This method is called the resistive detection method.
In non-802.3af or pre-802.3af standard, POE transmits power over a spare pair (not the
same pair as the data). This method is called the capacitor detection method.
Alcatel.Lucent-ESD
Calabasas/CA./USA
Source Learning
Source Learning
Hardware Learning
Transparent bridging relies on a process referred to as source learning to handle traffic flow. Network
devices communicate by sending and receiving data packets that each contains a source MAC address
and a destination MAC address. When packets are received on switch network interface (NI) module
ports, source learning examines each packet and compares the source MAC address to entries in a
MAC address database table. If the table does not contain an entry for the source address, then a new
record is created associating the address with the port it was learned on. If an entry for the source
address already exists in the table, a new one is not created.
Packets are also filtered to determine if the source and destination address are on the same LAN
segment. If the destination address is not found in the MAC address table, then the packet is forwarded
to all other switches that are connected to the same LAN. If the MAC address table does contain a
matching entry for the destination address, then there is no need to forward the packet to the rest of the
network. Source learning builds and maintains the MAC address table on each switch. New MAC
address table entries are created in one of two ways: they are dynamically learned or statically
assigned. Dynamically learned MAC addresses are those that are obtained by the switch when source
learning examines data packets and records the source address and the port and VLAN it was learned
on. Static MAC addresses are user-defined addresses that are statically assigned to a port and VLAN.
Accessing MAC Address Table entries is useful for managing traffic flow and troubleshooting network
device connectivity problems. For example, if a workstation connected to the switch is unable to
communicate with another workstation connected to the same switch, the MAC address table might
show that one of these devices was learned on a port that belonged to a different VLAN or the source
MAC address of one of the devices may not appear at all in the address table.
The ASIC is capable of Hardware Learning where the unknown source address of a packet could be
learned by the ASIC without software intervention. The advantage of Hardware Learning is to
eliminate excessive flooding problem due to the slow learning rate of Software Learning.
Default Chassis source learning mode is Hardware Learning.
Default Chassis source learning mode is Hardware Learning. New CLI commands are available to
allow user a choice of switching back to Software Learning mode. Mode will also change when the
user configures to be mobile, authentication, and/or LPS port.
Source Learning Specifications

Source Learning RFCs supported
Source Learning IEEE Standards supported
MAC Address Table entries
Maximum number of learned MAC addresses per

switch (distributed MAC mode disabled)
Maximum number of learned MAC addresses total for
a stack of up to 8 switches
2674 - Definitions of Managed Objects for Bridges with Traffic Classes, Multicast Filtering and
Virtual LAN Extensions
802.1Q - Virtual Bridged Local Area Networks
802.1D - Media Access Control Bridges
Source learning builds and maintains the MAC address table on each switch. New MAC address table
entries are created in one of two ways: they are dynamically learned or statically assigned.
Dynamically learned MAC addresses are those that are obtained by the switch when source learning
examines data packets and records the source address and the port and VLAN it was learned on. Static
MAC addresses are user-defined addresses that are statically assigned to a port and VLAN.
In addition, Source Learning also tracks MAC address age and removes addresses from the MAC
address table that have aged beyond the configurable aging timer value.
Accessing MAC Address Table entries is useful for managing traffic flow and troubleshooting network
device connectivity problems. For example, if a workstation connected to the switch is unable to
communicate with another workstation connected to the same switch, the MAC address table might
show that one of these devices was learned on a port that belonged to a different VLAN or the source
MAC address of one of the devices may not appear at all in the address table.
There are two types of source learning modes currently available: software and hardware. The software
mode performs all source learning using switch software. The hardware mode takes advantage of
hardware resources that are now available to perform source learning tasks. At the present time, it is
possible to select the mode that is active for the chassis and/or a given set of ports.
By default, hardware source learning mode is active for the switch. The exception to this is that
hardware source learning is not supported on mobile or Learned Port Security (LPS) ports. As a result,
only software source learning is performed on these types of ports.
16K
8K
Alcatel.Lucent-ESD
Calabasas/CA./USA
Using Static MAC Addresses
MAC address aging timer

300 seconds by default
Selecting the Source Learning Mode
Using Static Multicast MAC Addresses

(L2 Static Multicast)
Static MAC addresses are configured using the Mac-address-table command. These addresses direct
network traffic to a specific port and VLAN. They are particularly useful when dealing with silent
network devices. These types of devices do not send packets, so their source MAC address is never
learned and recorded in the MAC address table. Assigning a MAC address to the silent devices port
creates a record in the MAC address table and ensures that packets destined for the silent device are
forwarded out that port.
When defining a static MAC address for a particular slot/port and VLAN, consider the following:
Configuring static MAC addresses is only supported on non-mobile ports.
The specified slot/port must already belong to the specified VLAN. Use the vlan port
default command to assign a port to a VLAN before you configure the static MAC address.
Only traffic from other ports associated with the same VLAN is directed to the static MAC
address slot/port.
Static MAC addresses are permanent addresses. This means that a static MAC address
remains in use even if the MAC ages out or the switch is rebooted.
There are two types of static MAC address behavior supported: bridging (default) or
filtering. Enter filtering to set up a denial of service to block potential hostile attacks.
Traffic sent to or from a filtered
MAC addr. is dropped. Enter bridging for regular traffic flow to or from the MAC addr.
If a packet received on a port associated with the same VLAN contains a source address
that matches a static MAC address, the packet is discarded. The same source address on
different ports within the same VLAN is not supported.
If a static MAC address is configured on a port link that is down or disabled, an asterisk
appears to the right of the MAC address in the show Mac-address-table command display.
The asterisk indicates that this is an invalid MAC address. When the port link comes up,
however, the MAC address is then considered valid and the asterisk no longer appears next
to the address in the display.
Source learning also tracks MAC address age and removes addresses from the MAC address table that
have aged beyond the aging timer value. When a device stops sending packets, source learning keeps
track of how much time has passed since the last packet was received on the devices switch port.
When this amount of time exceeds the aging time value, the MAC is aged out of the MAC address
table. Source learning always starts tracking MAC address age from the time since the last packet was
received. By default, the aging time is set to 300 seconds (5 min) and is configured on a global basis.
Note. The MAC address table aging time is also used as the timeout value for the Address Resolution
Protocol (ARP) table. This timeout value determines how long the switch retains dynamically learned
ARP table entries.
There are two types of source learning modes currently available: software and hardware. The software
mode performs all source learning using switch software. The hardware mode takes advantage of
hardware resources that are now available to perform source-learning tasks. At the present time, it is
possible to select which mode is active for the chassis and/or a given set of ports.
By default, hardware source learning mode is active for the switch. The exception to this is that
hardware source learning is not supported on mobile or Learned Port Security (LPS) ports. As a result,
only software source learning is performed on these types of ports.
Using static multicast MAC addresses allows you to send traffic intended for a single destination
multicast MAC address to selected switch ports within a given VLAN. To specify which ports will
receive the multicast traffic, a static multicast address is assigned to each selected port for a given
VLAN. The ports associated with the multicast address are then identified as egress ports. When traffic
received on ports within the same VLAN is destined for the multicast address, the traffic is forwarded
only on the egress ports that are associated with the multicast address.
When defining a static multicast MAC address for a particular port and VLAN, consider the following:
A MAC address is considered a multicast MAC address if the least significant bit of the most
significant octet of the address is enabled. For example, MAC addresses with a prefix of 01, 03, 05, 13,
etc., are multicast MAC addresses.
If a multicast prefix value is not present, then the address is treated as a regular MAC address and not
allowed when using the Mac-address-table static-multicast command.
Multicast addresses within the following ranges are not supported:
01:00:5E:00:00:00 to 01:00:5E:7F:FF:FF & 01:80:C2:XX.XX.XX & 33:33:XX:XX:XX:XX
Configuring static multicast addresses is only supported on non-mobile ports.
In addition to configuring the same static multicast address for multiple ports within a given VLAN,
it is also possible to use the same multicast address across multiple VLANs.
The specified port or link aggregate ID must already belong to the specified VLAN. Use the vlan port
default command to assign a port or link aggregate to a VLAN before you configure the static
multicast address.
Alcatel.Lucent-ESD
Calabasas/CA./USA
Software
Third Party Licenses and Notices
Capability Maturity Model (CMM)

The Ethernet software
The licenses and notices related only to such third party software are set forth below:
Booting and Debugging Non-Proprietary Software
The OpenLDAP Public License: Version 2.4, 8 December 2000
Linux
GNU GENERAL PUBLIC LICENSE: Version 2, June 1991
University of California
Carnegie-Mellon University
Random.c
Apptitude, Inc.
Agranat
RSA Security Inc.
Sun Microsystems, Inc.
Wind River Systems, Inc.
Network Time Protocol Version 4

Alcatel-Lucent's Software Engineering Institute (SEI) Capability Maturity Model (CMM) rating for
software processes meets the Level-2 (CMM-level-2) requirements.
The Ethernet software is responsible for a variety of functions that support the Ethernet, Gigabit
Ethernet ports on OmniSwitch 6400 Series switches. These functions include diagnostics, software
loading, initialization, and configuration of line parameters, gathering statistics, and responding to
administrative requests from SNMP or CLI.
Operating Systems
Wind Rivers VxWorks multi-tasking O/S version 5.4 with a Kernel version 2.5. Alcatel-Lucent O/S AOS (Alcatel-Lucents Operating Systems).
O/S: AOS (Alcatel-Lucent Operating Systems) based common to OS9000, OS8800, OS7000, OS6800 and OS6400
The AOS is uploaded onto the Flash memory. The advantage of this switch running the AOS is that it is managed using the same interface as with the rest of the
Alcatel-Lucent AOS switching & routing platforms. The AOS on the OS6400 platforms provides support for the majority of the features of the larger modular
platforms including layer-3 unicast routing using RIPv1&v2. Group mobility and authenticated VLANs as well as QoS and ACL functionality are supported
making the OS6400 a highly functional solution for the edge & core (SMB) of the network.
The O/S supports the ability to detect operating system or other software errors, and report them to an EMS, independently of CPU hardware failures.
The operating system is set to detect software exceptions, software trouble reports, and monitor registered software tasks. Depending on the severity of the
problem detected the system may reboot; otherwise it just reports the problem and takes corrective action as necessary. In either case, it does communicate the
problem, to the NMS in the form of an SNMP trap.
Software
Each OmniSwitch 6400 Chassis is shipped with base software.
All advanced features (with the exception of Advanced Routing Software) are also included in the base software.
Alcatel.Lucent-ESD
Calabasas/CA./USA
Alcatel-Lucent Value Propositions:
Value
High Availability
Embedded Security
Distributed Intelligence
Alcatel-Lucents fixed & stackable configuration switches are part of the larger Alcatel-Lucent LAN enterprise switching & routing portfolio.
Together, this portfolio offers a complete core solution with high availability, intelligent performance, and enhanced security in an easy to manage,
flexible and scalable package.
V
V
Vaaallluuueee
Alcatel-Lucents enterprise networking mission is to provide its customers with the industry's best value in highly available, secure and easy-to-manage network
solutions. The industrys best value means having leading features for availability, security and manageability and simultaneously reducing the total cost of
network ownership. In short, the best network at the best total cost.
With up to 384Gbps FD switching capacity, the OS6400 can be a very cost-effective distribution layer, server aggregation, or core switch. The OS6400 value
offers the enterprise the opportunity to invest in the future at prices they can afford today.
Key Customers: specific names of key customers will be provided upon a successful bid and/or NDA.
Alcatel-Lucent provides communications solutions to telecommunication carriers, Internet service providers and enterprises for delivery of voice, data and video
applications to their customers or to their employees. Alcatel-Lucent leverages its leading position in fixed and mobile broadband networks, applications and
services to bring value to its customers in the framework of a broadband world.
As the largest supplier of telecommunications equipment to carriers in the world, Alcatel-Lucent possesses vast experience in providing carrier class Internet
routing and fiber optic solutions, including SONET multiplexing, IP and ATM switching, and wave division multiplexing equipment. For example, our 7750
routing platform is extensively used by carriers and by municipalities as a high-end routing platform with integral MPLS and VPN services. Similarly, we
provide a significant portion of the electronics that ties together both the terrestrial and the undersea fiber optic infrastructure throughout the world. With sales of
EURO 12.5 billion in 2003, Alcatel-Lucent operates in more than 130 countries.
For more information, visit Alcatel-Lucent on the Internet: http://www.Alcatel-Lucent.com
About Alcatel-Lucent Enterprise Networking Solutions
Alcatel-Lucent delivers standards-based IP communications solutions to a global customer base of over 500,000 small, medium and large enterprises,
government agencies, healthcare facilities, and educational institutions. Alcatel-Lucent's award-winning Omni family of IP Communications solutions consists
of an extensive portfolio of network switching infrastructure products and IP telephony products built to provide long-term value.
Key Partners: A longer list of Alcatel-Lucents Partners with specific Marketing relationships will be provided upon a successful bid and/or NDA.
Alcatel-Lucent has created a partnering program that enables it to work with a limited set of vendors in order to provide solutions that fall outside of its core
competencies. Partnerships provide channels and customers a catalog of product solutions that are easy to find, evaluate, buy, install, and operate. Some of the
security partnerships Alcatel-Lucent has established include:
Fortinet Security Technology Vendor: Resale, Service & Support
Sygate Security Technology Vendor: Resale, Service & Support
TruSecure: Professional Services
Aruba Corporation (Wireless LAN products): Resale, Service & Support
Funk Software Corporation: RADIUS
InterLink Networks RAD: RADIUS
RSA: SSL implementation and ACE Server
Open SSH: SSH
RSA, VASCO, ActivCard, CRYPTO Card, Secure Computing: Security Token
StoneSoft: High-Availability VLANs
Alcatel.Lucent-ESD
Calabasas/CA./USA
Alcatel.Lucent-ESD
Calabasas/CA./USA
OmniSwitch 6400 Series IEEE/IETF Standards

The OmniSwitch 6400 Series is fully compliant with the relevant industry standards to include the following:
For further references on these Standards, refer to: www.IEEE.com
For further references on these Standards, refer to: www.IETF.org
IEEE
Ethernet OAM IEEE Standards Supported:
IEEE 802.1ad/D6.0 (VLAN Stacking)
IEEE 802.1ag
IEEE 802.1D-1998
IEEE 802.1D for the GVRP support
IEEE 802.1p
IEEE 802.1Q
IEEE 802.1QinQ
IEEE 802.1s
IEEE 802.1x
Extended 802.1x
IEEE 802.1x MIB Port Access
IEEE 802.1w
IEEE 802.3
IEEE 802.3i
IEEE 802.3ab
IEEE 802.3ac
IEEE 802.3ad
IEEE 802.3af
IEEE 802.3x
IEEE 802.3u
IEEE 802.3z
IEEE 802.1agConnectivity Fault Management

IEEE 802.1DMedia Access Control (MAC) Bridges
IEEE 802.1QVirtual Bridged Local Area Networks
IEEE Standards Supported: 802.1ad/D6.0 Standard for Local and Metropolitan Area Networks Virtual Bridged Local Area Networks - Amendment 4: Provider Bridges
Connectivity Fault Management
STP - Bridging (Media Access Control Bridges)
IEEE Std. 802.1D - 2004, Media Access Control (MAC) Bridges
IEEE Draft Std. P802.1Q-REV/D5.0
CoS/QoS
VLANs - Virtual Bridged local Area Networks
Draft Standard P802.1Q/D11 IEEE Standards for Local And Metropolitan Area Network: Virtual
Bridged Local Area Networks, July 30, 1998
VLAN Stacking
MSTP - Multiple VLAN Spanning Tree
Security - Port-based Network Access (supplement to 802.1D)
Authenticated VLAN (multiple MAC, multiple VLANs per port)
IEEE 802.1x MIB Port Access is supported.
RSTP - Rapid reconfiguration
Carrier Sense Multiple Access with Collision Detection (CSMA/CD)
10BASE-T
The IEEE 802.3ab standard describes the specifications for the 1000BASE-T twisted-pair GigEth.
VLAN tagging
Link Aggregation (Dynamic)
Power over Ethernet (PoE)
Ethernet flow control
The IEEE 802.3u standard describes the specification 100BASE-TX, & 100BASE-FX Ethernet
The IEEE 802.3z standard describes the specifications for the 1000BASE-X fiber optic Gigabit Eth.
Alcatel.Lucent-ESD
Calabasas/CA./USA
IETF -- RFCs
RFC 768
RFC 791 / 894 / 1024 /1349
RFC 792
RFC 793 / 1156
RFC 826 / 903
RFC 854 / RFC 855
RFC 855
RFC 894
RFC 896
RFC 903
RFC 919 / 922
RFC 922
RFC 925 / 1027
RFC 950
RFC 951
RFC 959 / 2640
RFC 1027
RFC 1058
RFC 1024
RFC 1112
RFC 1122
RFC 1151
RFC 1155 / 2578-2580
RFC 1156
RFC 1157 / 2271
RFC 1191
RFC 1212 / 2737
RFC 1213 / 2011-2013
RFC 1215
RFC 1256
RFC 1305 / 2030
RFC 1321
RFC 1349
RFC 1493
RFC 1518 / 1519
RFC 1541 / 1542 / 2131 / 3396 / 3442
RFC 1542
RFC 1573 / RFC 2233 / RFC 2863
RFC 1643 / RFC 2665
RFC 1722 / 1723 / 2453 / 1724
RFC 1724 (which obsoletes RFC 1389)
RFC 1757 (formerly 1271) / 2819
UDP
IP & IP / Ethernet
ICMP
TCP / IP & MIB
ARP & Reverse ARP
Telnet & Telnet options
Telnet & Telnet options
IP & IP / Ethernet
Congestion Control
ARP & Reverse ARP
Broadcasting Internet Datagram
Broadcasting Internet Datagram
Multi-LAN ARP / Proxy ARP; Statically configured ARP entries
Subnetting
Bootstrap Protocol (BootP)
FTP
Multi-LAN ARP / Proxy ARP; Statically configured ARP entries
RIPv1
IP & IP / Ethernet
IGMPv1
Internet Hosts
RDP
SMIv1 & SMIv2
TCP / IP & MIB
SNMPv1
Path MTU Discovery
MIB & MIB-II
SNMPv2 MIB
Convention for SNMP Traps
ICMP Router Discovery Messages
NTPv3 & Simple NTP
MD5
IP & IP / Ethernet
Bridge MIB
CIDR
Dynamic Host Configuration Protocol (DHCP)
Clarifications and Extensions for the Bootstrap Protocol
Private Interface MIB
Ethernet MIB
RIPv2 Protocol Applicability Statement & MIB
RIPv2 MIB Extension
RMON & MIB
Alcatel.Lucent-ESD
Calabasas/CA./USA
RFC 1812 / 2644

RFC 1886
RFC 1901, 1902, 1903, 1904, 1905, 1906, 1907
RFC 1908
RFC 2003
RFC 2011
RFC 2012
RFC 2013
RFC 2030
RFC 2080
RFC 2096
RFC 2104
RFC 2131 / 3046
RFC 2132
RFC 2138 / 2865 / 2868 / 3575 / 2618
RFC 2139 / 2866 / 2867 / 2620
RFC 2228
RFC 2233
RFC 2236 / 2933
RFC 2271
RFC 2284
RFC 2292 / 2373 / 2374 / 2460 / 2462
RFC 2365
RFC 2452 / RFC 2454
RFC 2453
RFC 2461
RFC 2463 / 2466
RFC 2464 / 2553 / 2893 / 3493 / 3513
RFC 2474 / 2475 / 2597 / 3168 / 3246

RFC 2475
RFC 2570
RFC 2571
RFC 2572
RFC 2573
RFC 2574
RFC 2575
RFC 2576
RFC 2578, RFC 2579, and RFC 2580
RFC 2597
RFC 2616 / RFC 2854
RFC 2618
RFC 2620
RFC 2640
RFC 2644
RFC 2665
RFC 2667
RFC 2668 / RFC 3636
RFC 2674
IPv4 Router Requirements

DNS for IPv6
-SNMPv2c Management Framework
-Coexistence and transitions relating to SNMPv1 and SNMPv2c
-IP Encapsulation within IP.
SNMPv2 MIB
SNMPv2 MIB
SNMPv2 MIB
NTPv3 & Simple NTP
RIPng
IP MIB
HMAC Message Authentication
Dynamic Host Configuration Control (relay) DHCP / BootP Relay
DHCP Options and BOOTP Vendor Extensions
RADIUS Authentication & Client MIB
RADIUS
Note on RFC 2620: We support this RFC 2620 through our own Proprietary Private MIB.
Although, the mapping between the RFC 2620 and our own Private MIB is not one-to-one, we do
support many common objects between the standard version and that of our own Private MIB.
SFTP
IGMPv2 (Snooping for layer-2 multicast switching) & MIB
SNMPv1
PPP Extensible Authentication Protocol (EAP)
IPv6
Administratively Scoped IP Multicast
IPv6 TCP/UDP MIB
RIPv2
NDP
ICMPv6 & MIB
IPv6
Note: RFC 2893 has been obsoleted by RFC4213.
RFC4213 is now supported, but it does not include
Automatic tunnels. Therefore, the main difference is that the new RFC4213 does not contain an
automatic tunneling capability.
DiffServ
DiffServ
Version 3 of the Internet Standard Network Management Framework
Architecture for Describing SNMP Management Frameworks
Message Processing and Dispatching for SNMP
SNMPv3 Applications
User-based Security Model (USM) for version 3 of the Simple Network Management Protocol
(SNMPv3)
View-based Access Control Model (VACM) for SNMP
Coexistence between SNMP versions
SMIv1 & SMIv2
DiffServ
HTTP & HTML
Note: We support this RFC 2618 through our own Proprietary Private MIB.
RADIUS Accounting & Client MIB
Note: We support this RFC 2620 through our own Proprietary Private MIB.
FTP
Changing the Default for Directed Broadcast in Routers (complements IP router requirements)
Ethernet MIB
IP Tunnel MIB
IEEE 802.3 MAU MIB
Definitions of Managed Objects for Bridges with Traffic Classes, Multicast Filtering and Virtual LAN
Alcatel.Lucent-ESD
Calabasas/CA./USA
RFC 2737
RFC 2784
RFC 2787
RFC 2819
RFC 2863
RFC 2865
RFC 2866
RFC 2867
RFC 2868
RFC 2869/2869bits
RFC 2882
RFC 2893
RFC 2933
RFC 3046
RFC 3056
RFC 3060
RFC 3168
RFC 3176
RFC 3246
RFC 3376 (IGMPv3)
RFC 3396
RFC 3411
RFC 3412
RFC 3413
RFC 3414
RFC 3415
RFC 3416, RFC 3417, and RFC 3418
RFC 3442
RFC 3542 / RFC 3587
RFC 3575
RFC 3635
RFC 3636
Extensions / VLAN MIB

MIB & MIB-II
Generic Routing Encapsulation (GRE)
Definitions of Managed Objects for the Virtual Router Redundancy Protocol
Remote Network Monitoring Management Information Base
Remote Authentication Dial In User Service (RADIUS)
RADIUS Accounting & Client MIB
RADIUS Accounting Modifications for Tunnel Protocol Support / Accounting & Client MIB
RADIUS Attributes for Tunnel Protocol Support
RADIUS Extensions
Network Access Servers Requirements: Extended RADIUS Practices
IPv6/IPv4 Dual Stacks
Note: RFC 2893 has been obsoleted by RFC4213.
RFC4213 is now supported, but it does not include
Automatic tunnels. Therefore, the main difference is that the new RFC4213 does not contain an
automatic tunneling capability.
IGMP MIB
Dynamic Host Configuration Control (relay) DHCP / BootP Relay
IPv6 Tunneling
Policy Core
DiffServ
RFC 3176 is for sFlow support
DiffServ
Snooping for layer-2 multicast switching
SNMPv3
SNMPv3
SNMPv3
SNMPv3
SNMPv3
SNMPv2c
IPv6
Pause Control
IEEE 802.3 MAU MIB
Regulatory Compliance and Safety Information

This section provides information on regulatory agency compliance and safety for the OmniSwitch 6400 Series. AlcatelLucent has been a leader in terms of compliance with various green initiatives including:
RoHS The Alcatel-Lucent OmniSwitch family was among the first to be in compliance with the European
Communitys directive Restriction on Hazardous Substances in Electrical and Electronic Equipment
WEEE Waste Electrical and Electronic Equipment
NEBS Level3 Certified for all the non-PoE model
Declaration of Conformity: CE Mark

This equipment is in compliance with the essential requirements and other provisions of Directive 73/23/EEC and
89/336/EEC as amended by Directive 93/68/EEC.
Alcatel.Lucent-ESD
Calabasas/CA./USA
Waste Electrical and Electronic Equipment (WEEE) Statement

The product at end of life is subject to separate collection and treatment in the EU Member States, Norway and Switzerland.
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
The product bears the CE mark. In addition it is in compliance with the following other safety and EMC standards.
Note: EN = European Norm, IEC = International Electro-technical Commission
All hardware-switching platforms comply with Class A standards for digital devices per AS/NZS 3548, CISPR 22, EN55022,
the FCC Part 15, ICES-003, and VCCI standards. Modules with copper connectors meet Class A requirements using
unshielded (UTP) cables, but meet Class B requirements using shielded (STP) cables.
Safety Agency Certifications
US UL 60950
IEC 60950-1:2001; all national deviations
EN 60950-1: 2001; all deviations
CAN/CSA-C22.2 No. 60950-1-03
NOM-019 SCFI, Mexico
AS/NZ TS-001 and 60950:2000, Australia
UL-AR, Argentina
UL-GS Mark, Germany
EN 60825-1 Laser, EN60825-2 Laser
CDRH Laser
China CCC
EMC Standards
FCC CRF Title 47 Subpart B (Class A limits. Note: Class A with UTP cables)
VCCI (Class A limits. Note: Class A with UTP cables)
AS/NZS 3548 (Class A limits. Note: Class A with UTP cables)
CE marking for European countries (Class A Note: Class A with UTP cables)
EN 55022: 1995 (Emission Standard)
EN 61000-3-3: 1995
EN 61000-3-2: 2000
EN 55024: 1998 (Immunity Standards)
EN 61000-4-2: 1995+A1: 1998
EN 61000-4-3: 1996+A1: 1998
EN 61000-4-4: 1995
EN 61000-4-5: 1995
EN 61000-4-6: 1996
EN 61000-4-8: 1994
EN 61000-4-11: 1994
IEEE802.3: Hi-Pot Test (2250 VDC on all Ethernet ports)
FCC Class A, Part 15

This equipment has been tested and found to comply with the limits for Class A digital device pursuant to Part 15 of the
FCC Rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is
operated in a commercial environment. This equipment generates, uses, and can radiate radio frequency energy and, if not
installed and used in accordance with the instructions in this guide, may cause interference to radio communications.
Alcatel.Lucent-ESD
Calabasas/CA./USA
Operation of this equipment in a residential area is likely to cause interference, in which case the user will be required to
correct the interference at the owners expense.
The user is cautioned that changes and modifications made to the equipment without approval of the manufacturer could
void the users authority to operate this equipment. It is suggested that the user use only shielded and grounded cables to
ensure compliance with FCC Rules.
If this equipment does cause interference to radio or television reception, the user is encouraged to try to correct the
interference by one or more of the following measures:
Reorient the receiving antenna.
Relocate the equipment with respect to the receiver.
Move the equipment away from the receiver.
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.
Alcatel.Lucent-ESD
Calabasas/CA./USA
Canada Class A Statement

This equipment does not exceed Class A limits per radio noise emissions for digital apparatus, set out in the Radio
Interference Regulation of the Canadian Department of Communications.
JATE
This equipment meets the requirements of the Japan Approvals Institute of Telecommunications Equipment (JATE).
CISPR22 Class A Warning

This is a Class A product. In a domestic environment, this product may cause radio interference. Under such
circumstances, the user may be requested to take appropriate countermeasures.
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.
Class A Warning for Taiwan and Other Chinese Markets

This is a Class A Information Product. When used in a residential environment, it may cause radio frequency interference.
Under such circumstances, the user may be requested to take appropriate counter-measure.
Alcatel.Lucent-ESD
Calabasas/CA./USA
Translated Safety Warnings

Important Warnings
Blank Panels Warning
Because they regulate airflow and help protect internal chassis components, blank cover plates should remain installed at
empty module slots and power supply bays at all times.
Electrical Storm Warning

To avoid a shock hazard, do not connect or disconnect any cables or perform installation, maintenance, or reconfiguration
of this product during an electrical storm.
Installation Warning
Only personnel knowledgeable in basic electrical and mechanical procedures should install or maintain this equipment.
Invisible Laser Radiation Warning

Lasers emit invisible radiation from the aperture opening when no fiber-optic cable is connected. When removing cables
do not stare into the open apertures. In addition, install protective aperture covers to fiber ports with no cable connected.
Lithium Battery Warning

There is a danger of explosion if the Lithium battery in your chassis is incorrectly replaced. Replace the battery only with
the same or equivalent type of battery recommended by the manufacturer. Dispose of used batteries according to the
manufacturers instructions. The manufacturers instructions are as follows:
Return the module with the Lithium battery to Alcatel-Lucent. The Lithium battery will be replaced at Alcatel-Lucents
factory.
Operating Voltage Warning

To reduce the risk of electrical shock, keep your hands and fingers out of power supply bays and do not touch the
backplane while the switch is operating.
Power Disconnection Warning

Your switch is equipped with multiple power supplies. To reduce the risk of electrical shock, be sure to disconnect all
power connections before servicing or moving the unit.
Proper Earthing Requirement Warning

To avoid shock hazard:
The power cord must be connected to a properly wired and earth receptacle
Any equipment to which this product will attach must also be connected to properly wired receptacles
Alcatel.Lucent-ESD
Calabasas/CA./USA
Read Important Safety Information Warning

The Getting Started Guide and the Users Manual contain important safety information about which you should be aware
when working with hardware components in this system.
You should read this guide before installing, using, or servicing this equipment.
Restricted Access Location Warning

This equipment should be installed in a location that restricts access. A restricted access location is one where access is
secure and limited to service personnel who have a special key, or other means of security.
Wrist Strap Warning

Because electrostatic discharge (ESD) can damage switch components, you must ground yourself properly before
continuing with the hardware installation. For this purpose, Alcatel-Lucent provides a grounding wrist strap and a
grounding lug. For the grounding wrist strap to be effective in eliminating ESD, the power supplies must be installed and
plugged into grounded AC outlets.
Alcatel.Lucent-ESD
Calabasas/CA./USA
Appendix A: Pin-Outs
10/100Mbps Ethernet Port RJ-45 Pinouts (Non-PoE)
Pin Number
1
2
3
4
5
6
7
8
Description
RX+
RXTX+
Not used
Not used
TXNot used
Not used
Gigabit Ethernet Port RJ-45 Pinouts

Pin Number
1
2
3
4
5
6
7
8
Description
BI_DB+
BI_DBBI_DA+
BI_DD+
BI_DDBI_DABI_DC+
BI_DC-
10/100/1000Mbps Power over Ethernet Port -RJ-45 Pinouts

Pin Number
1
2
3
4
5
6
7
8
Description
RX+ (-VDC)
RX- (-VDC)
TX+ (+VDC)
N/C
N/C
TX- (+VDC)
N/C
N/C
RJ-45 Console Port Connector Pinouts

Pin Number
1
2
3
4
5
6
7
8
Description (Signals as DTE Console Port)

NC
NC
RXD
Ground
Ground
TXD
NC
NC
Alcatel.Lucent-ESD
Calabasas/CA./USA
Console Port / Serial Connection Default Settings

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.
The factory default settings for the serial connections are as follows:
Baud rate
Parity
Data bits (word size)
Stop bits
Flow Control
9600
None
8
1
None
Alcatel.Lucent-ESD
Calabasas/CA./USA

ALU Enterprise OmniSwitch6400 Boilerplate PDF

Cargado por

Información del documento

Descripción original:

Título original

Derechos de autor

Formatos disponibles

Compartir este documento

Compartir o incrustar documentos

Opciones para compartir

¿Le pareció útil este documento?

¿Este contenido es inapropiado?

Copyright:

Formatos disponibles

ALU Enterprise OmniSwitch6400 Boilerplate PDF

Cargado por

Copyright:

Formatos disponibles

A

Internetworking Solutions with

Gigabit Ethernet migration for Mid Size Campus __________________________________________________ 9

Key Customer Benefits ________________________________________________________________ 11

Key Technical Advantages ____________________________________________________________________ 11

OmniSwitch 6400 Series Hardware Details ___________________________________________ 18

OmniSwitch 6400-24 _______________________________________________________________________ 21

The OmniSwitch 6400-24 Internal Architecture __________________________________________________ 39

The OmniSwitch 6400 Series Power Supply System ________________________________________ 44

Power Supply Shelf ________________________________________________________________________ 44

Managing OmniSwitch 6400 Series Stacks ________________________________________________ 52

OmniSwitch 6400 Series Stack Overview ________________________________________________________ 52

Managing Power over Ethernet (PoE) ____________________________________________________ 61

Power over Ethernet Specifications _____________________________________________________________ 61

Availability Feature ___________________________________________________________________ 64

Software Rollback ___________________________________________________________________________ 64

OS6400 Series Boilerplate Doc. Rev. B / October 2008 Page 2

Backup Power Supplies _______________________________________________________________________ 64

Simplified Manageability ______________________________________________________________ 65

Alcatel-Lucent Access Guardian and OmniVista 2770 Quarantine Manager ___________________________ 65

MTBF Calculation Standards and Requirements __________________________________________ 67

IEEE _____________________________________________________________________________________ 123

Regulatory Compliance and Safety Information __________________________________________ 126

Declaration of Conformity: CE Mark __________________________________________________________ 126

Translated Safety Warnings ___________________________________________________________ 130

Important Warnings ________________________________________________________________________ 130

Appendix A: Pin-Outs __________________________________________________________ 132

OS6400 Series Boilerplate Doc. Rev. B / October 2008 Page 3

OS6400 Series Boilerplate Doc. Rev. B / October 2008 Page 4

Alcatel-Lucent Company Background

About Alcatel-Lucent Enterprise Networking Solutions

OS6400 Series Boilerplate Doc. Rev. B / October 2008 Page 6

Introducing OmniSwitch 6400 Series

OS6400 Series Boilerplate Doc. Rev. B / October 2008 Page 7

Alcatel-Lucent OmniSwitch 6400 Family

OS6400 Series Boilerplate Doc. Rev. B / October 2008 Page 8

Network Positioning and Applications

Residential and Business Ethernet Access

OS6400 Series Boilerplate Doc. Rev. B / October 2008 Page 9

Branch Office Internetworking

OS6400 Series Boilerplate Doc. Rev. B / October 2008 Page 10

Key Customer Benefits

Key Technical Advantages

High performance, affordable, future proof

Enhanced security that is adaptive to user

How we address the issue

OS6400 Series Boilerplate Doc. Rev. B / October 2008 Page 11

Benefits of our approach

There is a noticeable performance boost in triple-play

By offering the same operating system, existing users

Always available, reliable critical network

IPv6 support, a requirement of various corporate

the IT staff has a mechanism to push

Key Business Advantages

OS6400 Series Boilerplate Doc. Rev. B / October 2008 Page 12

Alcatel-Lucent pursues business on a global

Value add with emphasis on the Wireless LAN

Vendors Proven Track Record

Our Vision - Definition of future success

OS6400 Series Boilerplate Doc. Rev. B / October 2008 Page 13

Strong IP Infrastructure Solution Offerings

OS6400 Series Boilerplate Doc. Rev. B / October 2008 Page 14