ALU Enterprise OmniSwitch6855 Boilerplate Rev 2.1a

ALCATEL-LUCENT Enterprise Solutions Div.
Ethernet & IP Networking Portfolio
OmniSwitch 6855 Hardened LAN Switch Boilerplate Document
Table of Contents
Disclaimer_______________________________________________________________________ 3 Trademark Text __________________________________________________________________ 3 Revision History __________________________________________________________________ 3 Alcatel-Lucent Company Background ________________________________________________ 4 About Boilerplate _________________________________________________________________ 5 OmniSwitch 6855 Introduction ______________________________________________________ 6
Target Market ________________________________________________________________________ 6 Whats New? _________________________________________________________________________ 6
The OmniSwitch 6855 Product Overview ______________________________________________ 7

Hardware Overview ___________________________________________________________________ 8
OmniSwitch OS6855-14 ________________________________________________________________________ 8 OmniSwitch 6855-14 Internal Architecture ____________________________________________________ 10 OmniSwitch OS6855-U10______________________________________________________________________ 10 OmniSwitch 6855-U10 Internal Architecture ___________________________________________________ 11 OmniSwitch OS6855-24 _______________________________________________________________________ 12 OmniSwitch 6855-24 Internal Architecture ____________________________________________________ 13 OmniSwitch OS6855-U24______________________________________________________________________ 14 OmniSwitch 6855-U24 Internal Architecture ___________________________________________________ 15 The OmniSwitch OS6855 Power Supply System ____________________________________________________ 17 Overtemp condition ___________________________________________________________________________ 20 Hardware Monitoring _________________________________________________________________________ 22 Managing Power over Ethernet (PoE) _____________________________________________________________ 22 Power over Ethernet Specifications ___________________________________________________________ 22 Port Priority Levels ________________________________________________________________________ 23 Understanding Priority Disconnect ___________________________________________________________ 23 Monitoring Power over Ethernet via CLI ______________________________________________________ 24 Power Cords ______________________________________________________________________________ 25 Specifications ___________________________________________________________________________ 25 Redundant AC Circuit Recommendation ______________________________________________________ 25 Grounding the Chassis _____________________________________________________________________ 25 Temperature Management ______________________________________________________________________ 25
MTBF ( Mean Time Between Failure)____________________________________________________ 26 Regulatory Compliance and Safety Information ___________________________________________ 38
Declaration of Conformit y: CE Mark _____________________________________________________________ 39 Waste Electrical and Electronic Equipment (WEEE) Statement _________________________________________ 39 Standards Compliance _________________________________________________________________________ 39 Safety Standards __________________________________________________________________________ 39 EMC Standards ___________________________________________________________________________ 39 Safety and Environmental Standards _________________________________________________________ 41
OmniSwitch 6855 Series Hardware & Software Features Overview Table ____________________ 41 Appedix A - Small Form Factor Pluggable (SFP MSA)______________________________________ 89
Handling Fiber and Fiber Optic Connectors ___________________________________________________ 89 OS6855 Series Boilerplate Doc. Rev.2.1a / Nov. 09 Page 1 Alcatel.Lucent-ESD Calabasas/CA./USA
Appendix B - Pin-Outs ________________________________________________________________ 91

RJ-45 Console Port Connector Pinouts ______________________________________________________ 91 RJ-45 Console Port Connector Pinouts ______________________________________________________ 91 10/100Mbps Ethernet Port RJ-45 Pinouts (Non-PoE) ____________________________________________ 91 Power over Ethernet Port RJ-45 Pinouts (with PoE) ____________________________________________ 91 1 Gigabit Ethernet Port RJ-45 Pinouts (Non-PoE)_______________________________________________ 92 10/100/1000Mbps Power over Ethernet Port -RJ-45 Pinouts ______________________________________ 92 Console Port / Serial Connection Default Settings _______________________________________________ 92 OS6855 DB-25 Ppower Connection PIN-OUT __________________________________________________ 93
Appendix C - MTBF Calculation Standards and Requirements ______________________________ 93
OS6855 Series Boilerplate Doc. Rev.2.1a / Nov. 09
Page 2
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 Rev. 1.0 Rev. 2.0 Rev. 2.1 Rev. 2.1a Date: December 08 February. 09 July 09 Aug 09 Nov. 09 Revision Description Preliminary draft. Removed all references to ASIC, CPU, tranceivers vendors Added OS6855-U24X and AOS6.4.2 Added OS6855-PSS-P-D Updates to the diagrams and added MTBFs for OS6855-U24X , updates on the power consumption numbers, as well as other minor modifications.
Page 3
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. OS6855 Series Boilerplate Doc. Rev.2.1a / Nov. 09 Page 4 Alcatel.Lucent-ESD Calabasas/CA./USA
About Boilerplate
Alcatel-Lucent Internetworking Boilerplate documents include the following series: AOS OmniSwitch 9000 Series AOS OmniSwitch 6850 Series AOS OmniSwitch 6855 Series AOS OmniSwitch 6400 Series OmniStack LS 6200 Product Families OmniAccess Wireless LAN (WLAN) Product Families OmniVista Network Management System Legacy Product Families: AOS OmniSwitch 8800 AOS OmniSwitch 7000 Series AOS OmniSwitch 6800 Series AOS OmniSwitch 6600/6602 Series OmniStack 6024/6124/6148/8008 Product Families OmniStack 6300 Product Families The scope of this document is to provide the reader with a basic understanding of all the main product features implemented in the Alcatel-Lucent OmniSwitch 6855 Hardened LAN Switch. Furthermore, it can be used as a reference for preparing replies to RFI/RFP/RFQ questions. (RFI : Request for Information RFP : Request for Proposal RFQ : Request for Quotation) NOTE: Throughout this document if a reference is made towards future releases of the OS6855 the content of these releases and functionality should be confirmed against the prior to quotation to a customer. This document is intended to be an evolving document that will be updated in view of: A new product release and new features, The need for additional information on existing features.
The document does not provide information related to the OmniVista network management platform. Please refer to the NMS roadmap and boilerplate documents for details.
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. Please check user manuals and AOS specific boiler plate for details.
Page 5
OmniSwitch 6855 Introduction

The Alcatel-Lucent OmniSwitch 6855 is an extension of the Alcatel-Lucent OmniSwitch 6850 Stackable LAN switch family and is a platform specifically built for deployments where operating conditions are more demanding than normal. The OmniSwitch 6855 inherits the benefits of the Alcatel-Lucent OmniSwitch 6850 product family and offers flexible, configurations, high availability and wire speed performance at L2 and L3 that dramatically improves network response time. The key feature differentiator for the Alcatel-Lucent OmniSwitch 6855 is that it is a hardened, fully managed Gigabit Ethernet LAN switch, designed to operate under wide operating temperatures and harsh industrial electromagnetic environments. Its superior hardware design complemented by the advanced Alcatel-Lucent operating system (AOS) makes the OmniSwitch 6855 an excellent choice for industrial and carrier class applications
Target Market
The Alcatel-Lucent OmniSwitch 6855 is designed to operate in environments where conditions are harsh. Typical target customers or applications include utilities, oil and gas installations, water treatment plants, manufacturing plants, traffic signal control systems, and military installations. In particular:
1. 2. 3. 4. 5.
Power utility: Electric utility companies are now automating their operations including their substations. The Ethernet products used in these locations must operate at extreme temperatures as well as in high electro-magnetic fields. Fiber optic media is recommended for connecting all devices used in a substation. Transportation: Intelligent Transportation Systems (ITS), such as railroad applications and advanced traffic management systems, require Ethernet based, hardened communication solutions for use in wayside cabinets to support control, signaling and video monitoring applications. Telecommunications and carrier Ethernet applications: Desirable for outdoor installations that require enhanced QoS to support voice, video and data. Military installations: Must meet stringent shock and vibration requirements as well as enhanced security and high network availability. All environmentally harsh deployments.
Whats New?
The Alcatel-Lucent OmniSwitch 6855 offers these new, unique features: Purpose built, rugged hardware comprised of industrial grade components designed to withstand operating temperatures from -40C to +70C Five different models: 14-port and 24-port copper, 10-port and 24-port fiber models and 24 port fiber mode with two 10 Gig ports,powered by a variety of AC and DC power supplies PoE is enabled on all copper models Enhanced network reliability: in addition to having hardened hardware the Alcatel-Lucent OmniSwitch 6855s have improved reliability by providing redundancy everywhere including power supplies that are hot swappable and image rollback to automatically re-load previous configurations and software versions Performance: Wire-rate switching and routing at gigabit speeds. The Alcatel-Lucent OmniSwitch 6855 family supports real-time voice, data, and video applications. Advanced services: QoS, ACLs for traffic control Native IPv4 and IPv6 support at no additional cost.
Page 6
The OmniSwitch 6855 Product Overview

There are five OmniSwitch 6855 models in the family. 10 and 24 port fiber models and 14 and 24 port copper models, which can be powered by AC or DC power supplies to create the following bundles in the price list:
OmniSwitch 6855 Series

This section contains the information required to order the OmniSwitch 6855 Hardened Gigabit Ethernet switch bundles and backup power supplies, industrial grade transceivers and accessories. The product family model names have the format : OS6855-xxxx. Suffix letters in the bundle name indicate the type of power supply included. No letters present means bundle comes with standard AC power supply package. - "D" means bundle comes with -48V DC power supply - "DL" means bundle comes with a low voltage 24V DC power supply - "P" means the bundle comes with PoE power supply Backup power supply naming - "PSS" denotes power supply for the small models ( OS6855-14 and OS6855-U10 ) - "PSL" denotes power supply for the 24 port models. Advanced routing software is included in the price. ( OSPFv2/v3, PIM-SM/DM and DVMRP) . Only industrial strenght tranceivers ( denoted by the letter "i" at the beginnning of the name) are supported on OmniSwitch 6855. For AC powered chassis and power supplies, the country-specific power cord must be specified by adding the variation extension (-xx) from the list of power cords in the "Power Cords for European Market" and "Power Cords for Rest of World" sections in the "Accessories -Power Cord Options" section of this price list. See the Alcatel Enterprise Solutions Division Worldwide Price List Addendum, "All Products General; Cable Options" for additional information and Power Cord Cross Reference chart. Limited lifetime warranty does not apply to transceivers or backup power supplies. See the Transceiver section of this Worldwide Price List to choose the appropriate optical or copper plug-in interface. Model Number OS6855-14 Description OmniSwitch 6855 PoE Chassis Bundles OS6855-14 Hardened Gigabit Ethernet L3 fixed configuration fanless chassis in a 1U form factor designed to operate in harsh environments. It has 12 RJ-45 connectors individually configurable to 10/100/1000 BaseT, and 2 SFP ports which support various distances. The bundle comes with OS6855-PSS power supply, power shelf , country specific power cord, user manual access card and rack mounts. Ethernet optical transceivers, PoE power supply ( OS6855-PSS-P) and backup power supplies can be ordered separately. OS6855-14D Hardened Gigabit Ethernet L3 fixed configuration fanless chassis in a 1U form factor designed to operate in harsh environments. It has 12 RJ-45 connectors individually configurable to 10/100/1000 BaseT, and 2 SFP ports which support various distances. The bundle comes with OS6855-PSS-D power supply, power shelf, user manual access card and rack mounts. Ethernet optical transceivers, PoE power supply ( OS6855-PSS-P) and backup power supplies can be ordered separately. OS6855-24 Hardened Gigabit Ethernet L3 fixed configuration chassis in a 1U form factor designed to operate in harsh environments. It has 20 RJ-45 connectors individually configurable to 10/100/1000 BaseT four of which provide PoE and 4 combo ports. On the combo ports, either copper or fiber can be used on a one for one basis. The bundle comes with OS6855PSL-P power supply, power shelf, country specific power cord, user manual access card and rack mounts. Ethernet optical transceivers and backup power supplies can be ordered separately. OS6855-24 Hardened Gigabit Ethernet L3 fixed configuration chassis in a 1U form factor designed to operate in harsh environments. It has 20 RJ-45 connectors individually configurable to 10/100/1000 BaseT four of which are PoE capable and 4 combo ports. On the combo ports, either copper or fiber can be used on a one for one basis. The bundle comes with OS6855PSL-D power supply, power shelf, user manual access card and rack mounts. OS6855-24 Hardened Gigabit Ethernet L3 fixed configuration chassis in a 1U form factor designed to operate in harsh environments. It has 20 RJ-45 connectors individually configurable to 10/100/1000 BaseT four of which are PoE capable and 4 combo ports. On the combo ports, either copper or fiber can be used on a one for one basis. The bundle comes with OS6855PSL-DL power supply, power shelf, country specific power cord, user manual access card and rack mounts. Ethernet optical transceivers and backup power supplies can be ordered separately. OS6855-U10 Hardened Gigabit Ethernet L3 fixed configuration fanless chassis in a 1U form factor designed to operate in harsh environments. It has 2 RJ-45 connectors individually configurable to 10/100/1000 BaseT, and 8 SFP ports which support various distances. The bundle comes with OS6855-PSS power supply, power shelf, country specific power cord, user manual access card and rack mounts. Ethernet optical transceivers and backup power supplies can be ordered separately. OS6855-U10 Hardened Gigabit Ethernet L3 fixed configuration fanless chassis in a 1U form factor designed to operate in harsh environments. It has 2 RJ-45 connectors individually configurable to 10/100/1000 BaseT, and 8 SFP ports which support various distances. The bundle comes with OS6855-PSS-D power supply, power shelf, user manual access card and rack mounts. Ethernet optical transceivers and backup power supplies can be ordered separately. OS6855-24 Hardened Gigabit Ethernet L3 fixed configuration chassis in a 1U form factor designed to operate in harsh environments. It has 22 SFP ports which support various distances, and 2 combo ports. On the combo ports, either RJ-45 connectors individually configurable to 10/100/1000 BaseT or fiber SFP can be used on a one for one basis. The bundle comes with OS6855-PSL power supply, power shelf, country specific power cord, user manual access card and rack mounts. OS6855-24 Hardened Gigabit Ethernet L3 fixed configuration chassis in a 1U form factor designed to operate in harsh
OS6855-14D
OS6855-24
OS6855-24D
OS6855-24DL
OS6855-U10
OS6855-U10D
OS6855-U24
OS6855-U24D
Page 7
OS6855-U24DL
OS6855-U24X
OS6855-U24XD
OS6855-U24XDL
environments. It has 22 SFP ports which support various distances, and 2 combo ports. On the combo ports, either RJ-45 connectors individually configurable to 10/100/1000 BaseT or fiber SFP can be used on a one for one basis. The bundle comes with OS6855-PSL-D power supply, power shelf, user manual access card and rack mounts.Ethernet optical transceivers and backup power supplies can be ordered separately. OS6855-U24 Hardened Gigabit Ethernet L3 fixed configuration chassis in a 1U form factor designed to operate in harsh environments. It has 22 SFP ports which support various distances, and 2 combo ports. On the combo ports, either RJ-45 connectors individually configurable to 10/100/1000 BaseT or fiber SFP can be used on a one for one basis. The bundle comes with OS6855-PSL-DL power supply, power shelf, user manual access card and rack mounts. OS6855-U24X Hardened Gigabit Ethernet L3 fixed configuration chassis in a 1U form factor designed to operate in harsh environments. It has two 10G SFP+ ports that can be used for stacking or uplinks, 22 SFP ports which support various distances, and 2 combo ports. On the combo ports, either RJ-45 connectors individually configurable to 10/100/1000 BaseT or fiber SFP can be used on a one for one basis. The bundle comes with OS6855-PSL power supply, power shelf, user manual access card and rack mounts. OS6855-U24X Hardened Gigabit Ethernet L3 fixed configuration chassis in a 1U form factor designed to operate in harsh environments. It has two 10G SFP+ ports that can be used for stacking or uplinks, 22 SFP ports which support various distances, and 2 combo ports. On the combo ports, either RJ-45 connectors individually configurable to 10/100/1000 BaseT or fiber SFP can be used on a one for one basis. The bundle comes with OS6855-PSL-D power supply, power shelf, user manual access card and rack mounts. OS6855-U24X Hardened Gigabit Ethernet L3 fixed configuration chassis in a 1U form factor designed to operate in harsh environments. It has two 10G SFP+ ports that can be used for stacking or uplinks, 22 SFP ports which support various distances, and 2 combo ports. On the combo ports, either RJ-45 connectors individually configurable to 10/100/1000 BaseT or fiber SFP can be used on a one for one basis. The bundle comes with OS6855-PSL-DL power supply, power shelf, user manual access card and rack mounts. OS6855-U24 OS6855-PSS power brick AC power supply. Provides only system power. Does not provide PoE. Ships with country specific power cord. OS6855-PSS-P power brick AC power supply. Provides PoE only power to one OS6855-14. Ships with country specific power cord. OS6855-PSS-D power brick 24V-48V DC power supply. Provides only system power to one switch. Does not provide PoE. OS6855-PSS-P-D power brick 48V DC power supply. Provides PoE only power to one OS6855-14. OmniSwitch 6855 Backup Power Supplies for OS6855-24 , OS6855-U24, OS6855-U24X OS6855-PSL modular AC backup power supply. Provides backup system power to one OS6855-U24 switch. Ships with chassis connection cable and country specific power cord. OS6855-PSL-P modular AC backup power supply. Provides backup system and PoE power to one OS6855-24 switch. Ships with chassis connection cable and country specific power cord. OS6855-PSL-D modular -48V DC backup power supply. Provides backup system power to one 24 port 6855 switch. Ships with chassis connection cable. OS6855-PSL-DL modular 24V DC backup power supply. Provides backup system power to one 24 port 6855 switch. Ships with chassis connection cable. OmniSwitch 6855 Accessories A pack of 4 air filters for 6855-24 model A pack of 4 air filters for 6855-U24 model Power supply shelf for OS6855-U10 and 6855-14 models; mounting brackets included
OS6855-PSS OS6855-PSS-P OS6855-PSS-D OS6855-PSS-P-D OS6855-PSL OS6855-PSL-P OS6855-PSL-D OS6855-PSL-DL
OS6855-24-FLTR OS6855-U24-FLTR OS6855-PSS-SHLF
Hardware Overview
.
OmniSwitch OS6855-14
The OmniSwitch 6855-C14 is a hardened LAN switch offering 12 10/100/1000 Base-T, and two SFP connectors. Additionally, the first four ports are PoE capable. ( Note: in order to provide PoE power OS6855-PSS-P have to be installed in addition to the system power AC or DC power supply) The front panel of the OS6855-14 chassis contains the following major components:
(12) Unshared 10/100/1000Base-T with PoE support on the first four ports (2) SFP connectors Console port (RJ-45) LEDs OS6855 Series Boilerplate Doc. Rev.2.1a / Nov. 09 Page 8 Alcatel.Lucent-ESD Calabasas/CA./USA
The rear panel of OS6855-14 switch contains the following major components: Two 3-pin connectors provided for primary and redundant system power supplies Two 4-pin connectors provided for primary and redundant PoE power supplies Grounding block for type LCD8-10A-L grounding lug
Page 9
For more information please see the hardware user guide.
OmniSwitch 6855-14 Internal Architecture

400MHz CPU 128 M flash for boot and OS storage 256M SDRAM 32 bit 66MHz PCI bus RJ45 console port USB (not used)
OmniSwitch OS6855-U10
The OmniSwitch 6855-U10 is a hardened LAN switch offering 8 SFP connectors and 2 10/100/1000 Base-T ports. Front panel :
Page 10
Back Panel:
OmniSwitch 6855-U10 Internal Architecture

CPU - 400MHz 128M flash for boot and OS storage 256M SDRAM
Page 11 Alcatel.Lucent-ESD Calabasas/CA./USA
32 bit 66MHz PCI bus RJ45 console port USB (not used)
OmniSwitch OS6855-24
The OmniSwitch 6855-24 is a hardened gigabit switch offering 20 unshared 10/100/1000Base-T, as well as four combo ports individually configurable to 10/100/1000Base-T or 1000Base-X . Additionally, only the first four ports support PoE. Front Panel :
Page 12
Back Panel :
OmniSwitch 6855-24 Internal Architecture

CPU 400MHz 32 bit 66MHz PCI bus 256M SDRAM 128 M flash for boot and OS storage
RJ45 console port USB (not used)
OmniSwitch OS6855-U24
The OmniSwitch 6855-U24 is a hardened gigabit switch offering 22 SFP connectors, and two combo
ports individually configurable to 10/100/1000Base-T or 1000Base-X .
Front Panel:
Page 14
Back Panel:

CPU 400MHz 32 bit 66MHz PCI bus 256M SDRAM
128 M flash for boot and OS storage RJ45 console port USB (not used)
OmniSwitch OS6855-U24X
The OmniSwitch 6855-U24 is a hardened gigabit switch offering 22 SFP connectors, two combo ports individually configurable to 10/100/1000Base-T or 1000Base-X and two 10 Gigabit ports which can be used as stacking or uplinks. Front Panel:
Page 16
OmniSwitch 6855-U24X Back Panel

CPU 400MHz 32 bit 66MHz PCI bus 256M SDRAM
128 M flash for boot and OS storage RJ45 console port USB (not used)
The OmniSwitch OS6855 Power Supply System

All of the OmniSwitch 6855 models support redundant, hot-swappable AC, DC or PoE power supplies which are external to the box. Primary as well as backup power supplies for all models are external to the device and hotswappable which allows for easier maintenance and replacement Power supplies can also be remotely mounted using a special cable, which allows OmniSwitch 6855 to be used in areas with reduced depth. There is no interruption of service in case of a new PS is installed or an old one replaced
Please note that the half chassis models (OS6855-14 and OS6855-U10) use different power supplies than the 24 port models. For detailed information regarding Input voltage range, rated frequency, inrush current, output voltage , output current, etc. see chapter 2 of OmniSwitch 6855 Series Hardware User Guide.
Power supplies for OS6855-14 and OS6855-U10

The power supplies for OS6855-U10 and OS6855-14 models come in the form of a power brick in either AC or DC variant. A separate power brick provides PoE power and is available for purchase when PoE is required. OS6855 Series Boilerplate Doc. Rev.2.1a / Nov. 09 Page 18 Alcatel.Lucent-ESD Calabasas/CA./USA
Power Supply Models

OS6855-PSS PS6855-PSS-P PS6855-PSS-D
Description
External PSU for OS6855-14 and OS6855-U10; 90-240VAC, 50-60Hz AC; 40W, 12V, AC-DC External PSU for OS6855-14; 66W, 48V PoE, AC-DC External PSU for 6855-14 and OS6855-U10; 40W, -48V and 24V input to 12V DC-DC
Specification
Power brick (AC, DC or PoE) Power brick and tray
Weight
1.30lb/0.65kg 2.65lb/1.2kg
Depth
5.50 7.50"
Width
3.20 8.50
Height
1.6 1.73 (1RU)
The power supply shelf holds two power bricks and can be mounted either in a side-by-side configuration with the switch for 19 rack mounting or attached at the back of the switch for bulkhead mounting options.
Power supplies for OS6855-24 and OS6855-U24

The primary as well as the backup power supplies for the OmniSwitch 6855-24 port models are external and connect to the rear of the unit. A power shelf provided with the unit, can slide into the rear of the switch and is used to hold two power supplies. Power Supply Models
OS6855-PSL PS6855-PSL-P PS6855-PSL-D PS6855-PSL-DL
Description
External PSU for OS6855-U24; 90-240VAC, 50-60Hz AC; 80W, 12V, AC-DC External PSU for OS6855-24; 90-240VAC, 50-60Hz AC; 160W, 48V PoE, 12V, AC-DC External PSU for OS6855-24 and OS6855-U24; 80W, -48V/12V DC-DC External PSU for OS6855-24 and OS6855-U24; 80W, 24V/12V DC-DC
Specification
Power supply (AC, DC or PoE) Power supply and Tray
Weight
2.00lb/1.00kg 3.52lb/1.60kg
Depth
6.50" 7.00"
Width
6.30 13.88
Height
1.73 (1RU) 1.73 (1RU)
Any power supply can be remotely connected using a cable, which enables rack mounting using the mounting ears provided with the unit. This feature allows for space sensitive installations requiring reduced-depth (e.g., a wall-mounted cabinet).
OmniSwitch 6855 Backup Power Supplies Matrix

The OmniSwitch 6855 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. 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. Please take a note of the backup power supply naming convention: - "PSS" denotes power supply that can only be used with for the small models ( OS6855-14 and OS6855-U10 ) OS6855 Series Boilerplate Doc. Rev.2.1a / Nov. 09 Page 19 Alcatel.Lucent-ESD Calabasas/CA./USA
- "PSL" denotes power supply for the 24 port models only.
OS6855-14 OS6855-PSS OS6855-PSS-P OS6855-PSS-D OS6855-PSS-P-D OS6855-PSL OS6855-PSL-P OS6855-PSL-D OS6855-PSL-DL Yes Yes Yes Yes Not supported Not supported Not supported Not supported
OS6855-U10 Yes Not supported Yes Not supported Not supported Not supported Not supported Not supported
OS6855-24 Not supported Not supported Not supported Not supported Not supported Yes Yes Yes
OS6855-U24 Not supported Not supported Not supported Not supported Yes Not supported Yes Yes
OS6855-U24X Not supported Not supported Not supported Not supported Yes Not supported Yes Yes
Overtemp condition
The OmniSwitch 6855 is designed to operate within a wider operating temperature range than normal network equipment as noted under the specifications section. However, in the event that the normal operating temperature of the switch is exceeded, the following will occur: Upon crossing the configured overtemperature threshold, a trap will be sent. (See the OmniSwitch AOS Release 6 Network Configuration Guide) for information on configuring switch thresholds. If the temperature continues to rise above the maximum operating temperature, the following will occur: OK LED will display solid Amber. The switch will automatically shutdown Once the temperature drops to an acceptable operating level, the switch will automatically restart.
OS6855-U10 OS6855-14 OS6855-U24X
Operating Temperature Shutdown temperature Warning temperature (interrupt) Automatic Recovery temperature Fan turn on temperature Fan turn off temperature -40 to +70C 73C 71C 60C Not applicable Not applicable
OS6855-U24 OS6855-24
-40 to +75C 78C 76C 65C 50C 35C
Check the following if an overtemp condition exists: Verify that the switch is installed properly in an environment that adheres to the installation instructions in the following chapters. Verify proper airflow to the chassis.
Tranceivers
For more information on supported tranceivers please refer to OmniSwitch Tranceivers Guide located at : http://enterprise.all.alcatellucent.com/private/active_docs/os_xcvr_632r01.pdf?CFID=408480&CFTOKEN=21326601 You can also find a separate section in the WWPL listing the industrial grade tranceivers supporte on OS6855 familiy. Please note that, third party tranceivers not qualified by Alcatel-Lucent ESD, are not supported.
OS6855 Series Boilerplate Doc. Rev.2.1a / Nov. 09 Page 20 Alcatel.Lucent-ESD Calabasas/CA./USA
All optical transceivers qualified for OmniSwitch 6855 operate at wider operating temperature range then the corresponding commercial types. Gigabit Ethernet Transceivers
iSFP-GIG-LH70 1000Base-LH Industrial 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. 1000Base-LH Industrial 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-LX Industrial 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. 1000Base-SX Industrial 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.
iSFP-GIG-LH40
iSFP-GIG-LX
iSFP-GIG-SX
100 FX Ethernet Transceivers

iSFP-100-MM iSFP-100-SM15 iSFP-100-SM40 100Base-FX Industrial SFP transceiver with an LC type interface. This transceiver is designed for use over multimode fiber optic cable. 100Base-FX Industrial SFP transceiver with an LC type interface. This transceiver is designed for use over single mode fiber optic cable up to 15KM. 100Base-FX Industrial SFP transceiver with an LC type interface. This transceiver is designed for use over single mode fiber optic cable up to 40KM. 100Base-BX Industrial 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-BX Industrial 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
iSFP-100-BX-U
iSFP-100-BX-D
Supported Configuration Matrix for industrial grade tranceivers

Transceivers OS6855-14 Gigabit Ethernet Transceivers Yes iSFP-GIG-LH70 Yes iSFP-GIG-LH40 Yes iSFP-GIG-LX Yes iSFP-GIG-SX 100 FX Ethernet Transceivers Yes iSFP-100-MM Yes iSFP-100-SM15 Yes iSFP-100-SM40 Yes iSFP-100-BX-U Yes iSFP-100-BX-D Yes iSFP-100-BXLC-U Yes iSFP-100-BXLC-D OS6855-U10 Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes OS6855-24 Yes Yes Yes Yes No No No No No No No OS6855-U24 Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes
The technical specification for each transceiver are provided in the OS6855 hardware user guide. For SFP MSA tranceivers specifications and definitions see appendix A.
Page 21
Hardware Monitoring
Automatic monitoring refers to the switchs built-in sensors that automatically monitor operations. If an error is detected (e.g., over-threshold temperature), the switch immediately sends a trap to the user. The trap is displayed on the console in the form of a text error message. (In the case of an over-threshold temperature condition, the chassis displays an amber TMP LED in addition to sending a trap.) LEDs, which provide visual status information, are provided on the chassis front panel. LEDs are used to indicate conditions such as hardware and software status, temperature errors, link integrity, data flow, etc. User-driven hardware monitoring refers to CLI commands that are entered by the user in order to access the current status of hardware components. The user enters show commands that output information to the console.
Managing Power over Ethernet (PoE)

Power over Ethernet (PoE) is supported on OmniSwitch 6855 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 6855 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 IEEE 802.3af DTE Power via MDI Enabled Disabled - PoE must be activated on a switch-by-switch basis via the lanpower start command - Separate PoE power supply need to be installed for 6855-14 model. Only the copper models of the family support PoE : OS6855-14 and OS6855-24
OmniSwitch 6855 Series platforms supporting PoE
Page 22
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 PoE Power supplied to port
Power Priority level for a port The capacitor detection method Priority discount status
100 meters Up to 4 15400 Milliwatts 3000-20000 Milliwatts Approximately 4.3 amps On 6855-14 the maximum available PoE power is 66 watts On 6855-24 the maximum available PoE power is 80 watts Please refer to the Power Supply Specification Section for more details. Low Disabled Enabled
Port Priority Levels

As not all Powered Devices (PDs) connected to the switch have the same priority within a customer network setting, the OmniSwitch 6855 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.
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).
Page 23
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 Reminder. Priority disconnect examples are applicable only when there is inadequate power remaining to power an incoming device. When a PD is being connected to a port with a higher priority level than all other 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 Reminder. Priority disconnect examples are applicable only when there is inadequate power remaining to power an incoming device. When a PD is being connected to a port with a lower priority level than all other 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 Reminder. Priority disconnect examples are applicable only when there is inadequate power remaining to power an incoming device. When priority disconnect is disabled, power will be denied to any incoming PD, regardless of its port priority status (i.e., low, high, and critical) or physical port number (i.e., 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
Page 24
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: 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
North America United Kingdom / Ireland Europe Japan Australia India Italy Switzerland / Liechtenstein Denmark / Greenland Argentina
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.
Page 25
MTBF ( Mean Time Between Failure)

For MTBF definitions, calculation standards and methods, please see Appendix C.
Family OS6855-14 Module Name PS-I40AC (40W AC Pwr Supply) PS-I40DC2448 (40W DC Pwr Supply) PS-I66AC-P (66W AC PoE Pwr Supp.) OS6855-14-PCBA (No PS. No SFP) OS6855-14+PS-I40AC (No SFP) OS6855-14+2(PS-I40AC) (No SFP) OS6855-14+PS-I40DC2448 (No SFP) OS6855-14+2(PS-I40DC2448) (No SFP) OS6855-14+PS-I40AC +PS-I40DC2448 (No SFP) OS6855-14+PS-I40AC +PS-I66AC-P (No SFP) OS6855-14+2(PS-I40AC) +2(PS-I66AC-P) (No SFP) OS6855-14+PS-I40DC2448 +PS-I66AC-P (No SFP) OS6855-14+2(PS-I40DC2448) +2(PS-I66AC-P) (No SFP) OS6855-14+PS-I40AC+PS-I40DC2448 +2(PS-I66AC-P) (No SFP) ISFP-100-MM ISFP-100-SM15 ISFP-100-SM40 ISFP-100-BX-U ISFP-100-BX-D ISFP-GIG-SX ISFP-GIG-LX ISFP-GIG-LH40 ISFP-GIG-LH70 OS6855-14+PS-I40AC +2(ISFP-100-MM) OS6855-14+PS-I40AC +2(ISFP-100-SM15) OS6855-14+PS-I40AC +2(ISFP-100-SM40) OS6855-14+PS-I40AC +2(ISFP-100-BX-U) OS6855-14+PS-I40AC +2(ISFP-100-BX-D) OS6855-14+PS-I40AC+2(ISFP-GIG-SX) OS6855-14+PS-I40AC +2(ISFP-GIG-LX) OS6855-14+PS-I40AC +2(ISFP-GIG-LH40) OS6855-14+PS-I40AC +2(ISFP-GIG-LH70) OS6855-14+2(PS-I40AC) +2(ISFP-100-MM) OS6855-14+2(PS-I40AC) +2(ISFP-100-SM15) OS6855-14+2(PS-I40AC) +2(ISFP-100-SM40) OS6855-14+2(PS-I40AC) +2(ISFP-100-BX-U) OS6855-14+2(PS-I40AC) +2(ISFP-100-BX-D) OS6855-14+2(PS-I40AC) +2(ISFP-GIG-SX) OS6855-14+2(PS-I40AC) +2(ISFP-GIG-LX) MTBF-Hr 300687 273120 339545 430389 177016 242606 167088 230504 236695 116356 191593 111982 185036 188405 5220297 4491556 4491556 8861320 8861320 7363770 4794094 7053678 7041758 165774 164083 164083 170216 170216 168896 164843 168556 168543 224683 222007 222007 231738 231738 229639 223209 MTBF-Yr 34.325 31.17808219 38.76084475 49.13116438 20.20730594 27.69474886 19.0739726 26.31324201 27.01997717 13.2826484 21.87134703 12.78333333 21.12283105 21.50742009 595.9243151 512.7347032 512.7347032 1011.56621 1011.56621 840.6130137 547.2710046 805.2143836 803.853653 18.9239726 18.73093607 18.73093607 19.43105023 19.43105023 19.2803653 18.81769406 19.24155251 19.24006849 25.64874429 25.34326484 25.34326484 26.45410959 26.45410959 26.21449772 25.48047945
Page 26
OS6855-14+2(PS-I40AC) +2(ISFP-GIG-LH40) OS6855-14+2(PS-I40AC) +2(ISFP-GIG-LH70) OS6855-14+PS-I40DC2448 +2(ISFP-100-MM) OS6855-14+PS-I40DC2448 +2(ISFP-100-SM15) OS6855-14+PS-I40DC2448 +2(ISFP-100-SM40) OS6855-14+PS-I40DC2448 +2(ISFP-100-BX-U) OS6855-14+PS-I40DC2448 +2(ISFP-100-BX-D) OS6855-14+PS-I40DC2448 +2(ISFP-GIG-SX) OS6855-14+PS-I40DC2448 +2(ISFP-GIG-LX) OS6855-14+PS-I40DC2448 +2(ISFP-GIG-LH40) OS6855-14+PS-I40DC2448 +2(ISFP-GIG-LH70) OS6855-14+2(PS-I40DC2448) +2(ISFP-100-MM) OS6855-14+2(PS-I40DC2448) +2(ISFP-100-SM15) OS6855-14+2(PS-I40DC2448) +2(ISFP-100-SM40) OS6855-14+2(PS-I40DC2448) +2(ISFP-100-BX-U) OS6855-14+2(PS-I40DC2448) +2(ISFP-100-BX-D) OS6855-14+2(PS-I40DC2448) +2(ISFP-GIG-SX) OS6855-14+2(PS-I40DC2448) +2(ISFP-GIG-LX) OS6855-14+2(PS-I40DC2448) +2(ISFP-GIG-LH40) OS6855-14+2(PS-I40DC2448) +2(ISFP-GIG-LH70) OS6855-14+PS-I40AC+PS-I40DC2448 +2(ISFP-100-MM) OS6855-14+PS-I40AC+PS-I40DC2448 +2(ISFP-100-SM15) OS6855-14+PS-I40AC+PS-I40DC2448 +2(ISFP-100-SM40) OS6855-14+PS-I40AC+PS-I40DC2448 +2(ISFP-100-BX-U) OS6855-14+PS-I40AC+PS-I40DC2448 +2(ISFP-100-BX-D) OS6855-14+PS-I40AC+PS-I40DC2448 +2(ISFP-GIG-SX) OS6855-14+PS-I40AC+PS-I40DC2448 +2(ISFP-GIG-LX) OS6855-14+PS-I40AC+PS-I40DC2448 +2(ISFP-GIG-LH40) OS6855-14+PS-I40AC+PS-I40DC2448 +2(ISFP-GIG-LH70) OS6855-14+PS-I40AC+PS-I66AC-P +2(ISFP-100-MM) OS6855-14+PS-I40AC+PS-I66AC-P +2(ISFP-100-SM15) OS6855-14+PS-I40AC+PS-I66AC-P +2(ISFP-100-SM40) OS6855-14+PS-I40AC+PS-I66AC-P +2(ISFP-100-BX-U) OS6855-14+PS-I40AC+PS-I66AC-P +2(ISFP-100-BX-D) OS6855-14+PS-I40AC+PS-I66AC-P +2(ISFP-GIG-SX) OS6855-14+PS-I40AC+PS-I66AC-P +2(ISFP-GIG-LX) OS6855-14+PS-I40AC+PS-I66AC-P +2(ISFP-GIG-LH40) OS6855-14+PS-I40AC+PS-I66AC-P +2(ISFP-GIG-LH70) OS6855-14+2(PS-I40AC) +2(PS-I66AC-P)+2(ISFP-100-MM) OS6855-14+2(PS-I40AC) +2(PS-I66AC-P)+2(ISFP-100-SM15) OS6855-14+2(PS-I40AC) +2(PS-I66AC-P)+2(ISFP-100-SM40) OS6855-14+2(PS-I40AC) +2(PS-I66AC-P)+2(ISFP-100-BX-U) OS6855-14+2(PS-I40AC) +2(PS-I66AC-P)+2(ISFP-100-BX-D) OS6855-14+2(PS-I40AC) +2(PS-I66AC-P)+2(ISFP-GIG-SX) OS6855-14+2(PS-I40AC) +2(PS-I66AC-P)+2(ISFP-GIG-LX)
229098 229077 157035 155517 155517 161016 161016 159835 156200 159530 159518 214359 211938 211938 220730 220730 218836 213026 218349 218329 219645 217094 217094 226364 226364 224366 218240 223851 223831 111390 110624 110624 113378 113378 112791 110969 112640 112634 180834 179191 179191 185119 185119 183851 179930
26.15273973 26.15034247 17.92636986 17.75308219 17.75308219 18.38082192 18.38082192 18.24600457 17.83105023 18.21118721 18.20981735 24.47020548 24.19383562 24.19383562 25.19748858 25.19748858 24.98127854 24.31803653 24.92568493 24.92340183 25.07363014 24.78242009 24.78242009 25.84063927 25.84063927 25.61255708 24.91324201 25.55376712 25.55148402 12.71575342 12.6283105 12.6283105 12.94269406 12.94269406 12.87568493 12.66769406 12.85844749 12.85776256 20.64315068 20.45559361 20.45559361 21.13230594 21.13230594 20.98755708 20.53995434
Page 27
OS6855-14+2(PS-I40AC)+2(PS-I66AC-P)+2(ISFP-GIG-LH40) OS6855-14+2(PS-I40AC) +2(PS-I66AC-P)+2(ISFP-GIG-LH70) OS6855-14+PS-I40DC2448 +PS-I66AC-P+2(ISFP-100-MM) OS6855-14+PS-I40DC2448 +PS-I66AC-P+2(ISFP-100-SM15) OS6855-14+PS-I40DC2448 +PS-I66AC-P+2(ISFP-100-SM40) OS6855-14+PS-I40DC2448 +PS-I66AC-P+2(ISFP-100-BX-U) OS6855-14+PS-I40DC2448+PS-I66AC-P+2(ISFP-100-BX-D) OS6855-14+PS-I40DC2448 +PS-I66AC-P+2(ISFP-GIG-SX) OS6855-14+PS-I40DC2448 +PS-I66AC-P+2(ISFP-GIG-LX) OS6855-14+PS-I40DC2448 +PS-I66AC-P+2(ISFP-GIG-LH40) OS6855-14+PS-I40DC2448 +PS-I66AC-P+2(ISFP-GIG-LH70) OS6855-14+2(PS-I40DC2448) +2(PS-I66AC-P)+2(ISFP-100-MM) OS6855-14+2(PS-I40DC2448) +2(PS-I66AC-P)+2(ISFP-100-SM15) OS6855-14+2(PS-I40DC2448)+2(PS-I66AC-P)+2(ISFP-100-SM40) OS6855-14+2(PS-I40DC2448) +2(PS-I66AC-P)+2(ISFP-100-BX-U) OS6855-14+2(PS-I40DC2448) +2(PS-I66AC-P)+2(ISFP-100-BX-D) OS6855-14+2(PS-I40DC2448) +2(PS-I66AC-P)+2(ISFP-GIG-SX) OS6855-14+2(PS-I40DC2448) +2(PS-I66AC-P)+2(ISFP-GIG-LX) OS6855-14+2(PS-I40DC2448) +2(PS-I66AC-P)+2(ISFP-GIG-LH40) OS6855-14+2(PS-I40DC2448) +2(PS-I66AC-P)+2(ISFP-GIG-LH70) OS6855-14+PS-I40AC+PS-I40DC2448 +2(PS-I66AC-P)+2(ISFP-100-MM) OS6855-14+PS-I40AC+PS-I40DC2448 +2(PS-I66AC-P)+2(ISFP-100SM15) OS6855-14+PS-I40AC+PS-I40DC2448 +2(PS-I66AC-P)+2(ISFP-100SM40) OS6855-14+PS-I40AC+PS-I40DC2448 +2(PS-I66AC-P)+2(ISFP-100-BXU) OS6855-14+PS-I40AC+PS-I40DC2448 +2(PS-I66AC-P)+2(ISFP-100-BXD) OS6855-14+PS-I40AC+PS-I40DC2448 +2(PS-I66AC-P)+2(ISFP-GIG-SX) OS6855-14+PS-I40AC+PS-I40DC2448 +2(PS-I66AC-P)+2(ISFP-GIG-LX) OS6855-14+PS-I40AC+PS-I40DC2448+2(PS-I66AC-P)+2(ISFP-GIGLH40) OS6855-14+PS-I40AC+PS-I40DC2448 +2(PS-I66AC-P)+2(ISFP-GIGLH70) OS6855-U10 PS-I40AC (40W AC Pwr Supply) PS-I40DC2448 (40W DC Pwr Supply) OS6855-U10-PCBA (No PS. No SFP) OS6855-U10+PS-I40AC (No SFP) OS6855-U10+2(PS-I40AC) (No SFP) OS6855-U10+PS-I40DC2448 (No SFP) OS6855-U10+2(PS-I40DC2448)(No SFP) OS6855-U10+PS-I40AC +PS-I40DC2448 (No SFP) ISFP-100-MM ISFP-100-SM15 ISFP-100-SM40 ISFP-100-BX-U ISFP-100-BX-D ISFP-GIG-SX
183523 183510 107376 106664 106664 109222 109222 108677 106984 108536 108530 175014 173480 173480 179010 179010 177828 174170 177523 177511 178006 176416 176416 182150 182150 180924 177132 180607 180595 300687 273120 508942 189015 261965 177738 247801 255040 5220297 4491556 4491556 8861320 8861320 7363770
20.95011416 20.94863014 12.25753425 12.17625571 12.17625571 12.46826484 12.46826484 12.40605023 12.21278539 12.38995434 12.38926941 19.97876712 19.80365297 19.80365297 20.43493151 20.43493151 20.3 19.88242009 20.26518265 20.26381279 20.32031963 20.13881279 20.13881279 20.793379 20.793379 20.65342466 20.22054795 20.61723744 20.61586758 34.325 31.17808219 58.09840183 21.57705479 29.90468037 20.28972603 28.28778539 29.11415525 595.9243151 512.7347032 512.7347032 1011.56621 1011.56621 840.6130137
Page 28
ISFP-GIG-LX ISFP-GIG-LH40 ISFP-GIG-LH70 OS6855-U10+PS-I40AC +8(ISFP-100-MM) OS6855-U10+PS-I40AC +8(ISFP-100-SM15) OS6855-U10+PS-I40AC +8(ISFP-100-SM40) OS6855-U10+PS-I40AC +8(ISFP-100-BX-U) OS6855-U10+PS-I40AC +8(ISFP-100-BX-D) OS6855-U10+PS-I40AC +8(ISFP-GIG-SX) OS6855-U10+PS-I40AC +8(ISFP-GIG-LX) OS6855-U10+PS-I40AC +8(ISFP-GIG-LH40) OS6855-U10+PS-I40AC +8(ISFP-GIG-LH70) OS6855-U10+2(PS-I40AC) +8(ISFP-100-MM) OS6855-U10+2(PS-I40AC) +8(ISFP-100-SM15) OS6855-U10+2(PS-I40AC) +8(ISFP-100-SM40) OS6855-U10+2(PS-I40AC) +8(ISFP-100-BX-U) OS6855-U10+2(PS-I40AC) +8(ISFP-100-BX-D) OS6855-U10+2(PS-I40AC) +8(ISFP-GIG-SX) OS6855-U10+2(PS-I40AC) +8(ISFP-GIG-LX) OS6855-U10+2(PS-I40AC) +8(ISFP-GIG-LH40) OS6855-U10+2(PS-I40AC)+8(ISFP-GIG-LH70) OS6855-U10+PS-I40DC2448 +8(ISFP-100-MM) OS6855-U10+PS-I40DC2448 +8(ISFP-100-SM15) OS6855-U10+PS-I40DC2448 +8(ISFP-100-SM40) OS6855-U10+PS-I40DC2448 +8(ISFP-100-BX-U) OS6855-U10+PS-I40DC2448 +8(ISFP-100-BX-D) OS6855-U10+PS-I40DC2448 +8(ISFP-GIG-SX) OS6855-U10+PS-I40DC2448 +8(ISFP-GIG-LX) OS6855-U10+PS-I40DC2448 +8(ISFP-GIG-LH40) OS6855-U10+PS-I40DC2448 +8(ISFP-GIG-LH70) OS6855-U10+2(PS-I40DC2448) +8(ISFP-100-MM) OS6855-U10+2(PS-I40DC2448) +8(ISFP-100-SM15) OS6855-U10+2(PS-I40DC2448) +8(ISFP-100-SM40) OS6855-U10+2(PS-I40DC2448) +8(ISFP-100-BX-U) OS6855-U10+2(PS-I40DC2448) +8(ISFP-100-BX-D) OS6855-U10+2(PS-I40DC2448) +8(ISFP-GIG-SX) OS6855-U10+2(PS-I40DC2448) +8(ISFP-GIG-LX) OS6855-U10+2(PS-I40DC2448) +8(ISFP-GIG-LH40) OS6855-U10+2(PS-I40DC2448) +8(ISFP-GIG-LH70) OS6855-U10+PS-I40AC+PS-I40DC2448 +8(ISFP-100-MM) OS6855-U10+PS-I40AC+PS-I40DC2448 +8(ISFP-100-SM15) OS6855-U10+PS-I40AC+PS-I40DC2448 +8(ISFP-100-SM40) OS6855-U10+PS-I40AC+PS-I40DC2448 +8(ISFP-100-BX-U) OS6855-U10+PS-I40AC+PS-I40DC2448 +8(ISFP-100-BX-D) OS6855-U10+PS-I40AC+PS-I40DC2448 +8(ISFP-GIG-SX)
4794094 7053678 7041758 146562 141409 141409 161463 161463 156814 143693 155648 155602 194586 186511 186511 217869 217869 210560 190020 208733 208660 139690 135001 135001 153162 153162 148972 137081 147920 147878 186955 179654 179654 208188 208188 201546 182887 199883 199817 190869 183236 183236 213146 213146 206165
547.2710046 805.2143836 803.853653 16.73082192 16.14257991 16.14257991 18.43184932 18.43184932 17.90114155 16.4033105 17.76803653 17.76278539 22.2130137 21.29121005 21.29121005 24.87089041 24.87089041 24.03652968 21.69178082 23.82796804 23.8196347 15.94634703 15.41107306 15.41107306 17.48424658 17.48424658 17.00593607 15.64851598 16.88584475 16.88105023 21.34189498 20.50844749 20.50844749 23.76575342 23.76575342 23.00753425 20.87751142 22.81769406 22.81015982 21.78869863 20.9173516 20.9173516 24.33173516 24.33173516 23.53481735
Page 29
OS6855-U10+PS-I40AC+PS-I40DC2448 +8(ISFP-GIG-LX) OS6855-U10+PS-I40AC+PS-I40DC2448 +8(ISFP-GIG-LH40) OS6855-U10+PS-I40AC+PS-I40DC2448 +8(ISFP-GIG-LH70) OS6855-24 OS6855-24-Fans PS-126I80AC (80W AC Pwr Supply) PS-120I80DC48 (80W-48VDC PS) PS-100I80DC24 (80W-24VDC PS) PS-360I160AC-P (160W AC PoE PS) OS6855-24-PCBA(No Fan.No PS.No SFP) OS6855-24 (No PS. No SFP) OS6855-24+PS-126I80AC (No SFP) OS6855-24+2(PS-126I80AC) (No SFP) OS6855-24+PS-120I80DC48 (No SFP) OS6855-24+2(PS-120I80DC48)(No SFP) OS6855-24+PS-100I80DC24 (No SFP) OS6855-24+2(PS-100I80DC24)(No SFP) OS6855-24+PS-126I80AC+PS-120I80DC48 (No SFP) OS6855-24+PS-126I80AC +PS-100I80DC24 (No SFP) OS6855-24+PS-126I80AC +PS-360I160AC-P (No SFP) OS6855-24+PS-120I80DC48 +PS-100I80DC24 (No SFP) OS6855-24+PS-120I80DC48 +PS-360I160AC-P (No SFP) OS6855-24+PS-100I80DC24 +PS-360I160AC-P (No SFP) ISFP-100-MM ISFP-100-SM15 ISFP-100-SM40 ISFP-100-BX-U ISFP-100-BX-D ISFP-GIG-SX ISFP-GIG-LX ISFP-GIG-LH40 ISFP-GIG-LH70 OS6855-24+PS-126I80AC +4(ISFP-100-MM) OS6855-24+PS-126I80AC +4(ISFP-100-SM15) OS6855-24+PS-126I80AC+4(ISFP-100-SM40) OS6855-24+PS-126I80AC +4(ISFP-100-BX-U) OS6855-24+PS-126I80AC +4(ISFP-100-BX-D) OS6855-24+PS-126I80AC +4(ISFP-GIG-SX) OS6855-24+PS-126I80AC +4(ISFP-GIG-LX) OS6855-24+PS-126I80AC+4(ISFP-GIG-LH40) OS6855-24+PS-126I80AC +4(ISFP-GIG-LH70) OS6855-24+2(PS-126I80AC)+4(ISFP-100-MM) OS6855-24+2(PS-126I80AC) +4(ISFP-100-SM15) OS6855-24+2(PS-126I80AC) +4(ISFP-100-SM40) OS6855-24+2(PS-126I80AC) +4(ISFP-100-BX-U) OS6855-24+2(PS-126I80AC) +4(ISFP-100-BX-D)
186614 204418 204349 562238 561803 314515 316907 391673 529644 272727 183599 228757 146067 192263 146581 192812 213638 213829 125003 192538 106391 106663 5220297 4491556 4491556 8861320 8861320 7363770 4794094 7053678 7041758 160956 157798 157798 169548 169548 166949 159210 166286 166260 196761 192365 192365 208806 208806
21.30296804 23.33538813 23.32751142 64.18242009 64.13276256 35.90353881 36.17659817 44.71152968 60.46164384 31.13321918 20.95878995 26.11381279 16.67431507 21.94783105 16.73299087 22.01050228 24.38789954 24.4097032 14.26974886 21.97922374 12.14509132 12.17614155 595.9243151 512.7347032 512.7347032 1011.56621 1011.56621 840.6130137 547.2710046 805.2143836 803.853653 18.3739726 18.01347032 18.01347032 19.35479452 19.35479452 19.05810502 18.17465753 18.98242009 18.97945205 22.46130137 21.95947489 21.95947489 23.83630137 23.83630137
Page 30
OS6855-24+2(PS-126I80AC) +4(ISFP-GIG-SX) OS6855-24+2(PS-126I80AC) +4(ISFP-GIG-LX) OS6855-24+2(PS-126I80AC) +4(ISFP-GIG-LH40) OS6855-24+2(PS-126I80AC) +4(ISFP-GIG-LH70) OS6855-24+PS-120I80DC48 +4(ISFP-100-MM) OS6855-24+PS-120I80DC48 +4(ISFP-100-SM15) OS6855-24+PS-120I80DC48 +4(ISFP-100-SM40) OS6855-24+PS-120I80DC48 +4(ISFP-100-BX-U) OS6855-24+PS-120I80DC48 +4(ISFP-100-BX-D) OS6855-24+PS-120I80DC48 +4(ISFP-GIG-SX) OS6855-24+PS-120I80DC48 +4(ISFP-GIG-LX) OS6855-24+PS-120I80DC48 +4(ISFP-GIG-LH40) OS6855-24+PS-120I80DC48 +4(ISFP-GIG-LH70) OS6855-24+2(PS-120I80DC48) +4(ISFP-100-MM) OS6855-24+2(PS-120I80DC48) +4(ISFP-100-SM15) OS6855-24+2(PS-120I80DC48) +4(ISFP-100-SM40) OS6855-24+2(PS-120I80DC48) +4(ISFP-100-BX-U) OS6855-24+2(PS-120I80DC48) +4(ISFP-100-BX-D) OS6855-24+2(PS-120I80DC48) +4(ISFP-GIG-SX) OS6855-24+2(PS-120I80DC48) +4(ISFP-GIG-LX) OS6855-24+2(PS-120I80DC48) +4(ISFP-GIG-LH40) OS6855-24+2(PS-120I80DC48) +4(ISFP-GIG-LH70) OS6855-24+PS-100I80DC24+4(ISFP-100-MM) OS6855-24+PS-100I80DC24 +4(ISFP-100-SM15) OS6855-24+PS-100I80DC24 +4(ISFP-100-SM40) OS6855-24+PS-100I80DC24 +4(ISFP-100-BX-U) OS6855-24+PS-100I80DC24 +4(ISFP-100-BX-D) OS6855-24+PS-100I80DC24 +4(ISFP-GIG-SX) OS6855-24+PS-100I80DC24 +4(ISFP-GIG-LX) OS6855-24+PS-100I80DC24 +4(ISFP-GIG-LH40) OS6855-24+PS-100I80DC24 +4(ISFP-GIG-LH70) OS6855-24+2(PS-100I80DC24) +4(ISFP-100-MM) OS6855-24+2(PS-100I80DC24) +4(ISFP-100-SM15) OS6855-24+2(PS-100I80DC24) +4(ISFP-100-SM40) OS6855-24+2(PS-100I80DC24)+4(ISFP-100-BX-U) OS6855-24+2(PS-100I80DC24) +4(ISFP-100-BX-D) OS6855-24+2(PS-100I80DC24) +4(ISFP-GIG-SX) OS6855-24+2(PS-100I80DC24) +4(ISFP-GIG-LX) OS6855-24+2(PS-100I80DC24) +4(ISFP-GIG-LH40) OS6855-24+2(PS-100I80DC24) +4(ISFP-GIG-LH70) OS6855-24+PS-126I80AC +PS-120I80DC48+4(ISFP-100-MM) OS6855-24+PS-126I80AC +PS-120I80DC48+4(ISFP-100-SM15) OS6855-24+PS-126I80AC +PS-120I80DC48+4(ISFP-100-SM40) OS6855-24+PS-126I80AC +PS-120I80DC48+4(ISFP-100-BX-U) OS6855-24+PS-126I80AC +PS-120I80DC48+4(ISFP-100-BX-D)
205151 194329 204220 204183 131365 129254 129254 137032 137032 135330 130199 134894 134876 169982 166821 166821 178518 178518 175947 168236 175289 175263 131780 129656 129656 137484 137484 135771 130608 135332 135314 170400 167222 167222 178984 178984 176398 168644 175737 175710 185787 181914 181914 196341 196341
23.41906393 22.1836758 23.31278539 23.30856164 14.99600457 14.75502283 14.75502283 15.64292237 15.64292237 15.44863014 14.86289954 15.39885845 15.39680365 19.4043379 19.04349315 19.04349315 20.37876712 20.37876712 20.08527397 19.20502283 20.01015982 20.00719178 15.043379 14.80091324 14.80091324 15.69452055 15.69452055 15.4989726 14.90958904 15.44885845 15.44680365 19.45205479 19.08926941 19.08926941 20.43196347 20.43196347 20.13675799 19.25159817 20.06130137 20.05821918 21.20856164 20.76643836 20.76643836 22.41335616 22.41335616
Page 31
OS6855-24+PS-126I80AC +PS-120I80DC48+4(ISFP-GIG-SX) OS6855-24+PS-126I80AC +PS-120I80DC48+4(ISFP-GIG-LX) OS6855-24+PS-126I80AC +PS-120I80DC48+4(ISFP-GIG-LH40) OS6855-24+PS-126I80AC +PS-120I80DC48+4(ISFP-GIG-LH70) OS6855-24+PS-126I80AC +PS-100I80DC24+4(ISFP-100-MM) OS6855-24+PS-126I80AC +PS-100I80DC24+4(ISFP-100-SM15) OS6855-24+PS-126I80AC +PS-100I80DC24+4(ISFP-100-SM40) OS6855-24+PS-126I80AC +PS-100I80DC24+4(ISFP-100-BX-U) OS6855-24+PS-126I80AC +PS-100I80DC24+4(ISFP-100-BX-D) OS6855-24+PS-126I80AC +PS-100I80DC24+4(ISFP-GIG-SX) OS6855-24+PS-126I80AC +PS-100I80DC24+4(ISFP-GIG-LX) OS6855-24+PS-126I80AC +PS-100I80DC24+4(ISFP-GIG-LH40) OS6855-24+PS-126I80AC +PS-100I80DC24+4(ISFP-GIG-LH70) OS6855-24+PS-126I80AC +PS-360I160AC-P+4(ISFP-100-MM) OS6855-24+PS-126I80AC +PS-360I160AC-P+4(ISFP-100-SM15) OS6855-24+PS-126I80AC +PS-360I160AC-P+4(ISFP-100-SM40) OS6855-24+PS-126I80AC +PS-360I160AC-P+4(ISFP-100-BX-U) OS6855-24+PS-126I80AC +PS-360I160AC-P+4(ISFP-100-BX-D) OS6855-24+PS-126I80AC +PS-360I160AC-P+4(ISFP-GIG-SX) OS6855-24+PS-126I80AC +PS-360I160AC-P+4(ISFP-GIG-LX) OS6855-24+PS-126I80AC +PS-360I160AC-P+4(ISFP-GIG-LH40) OS6855-24+PS-126I80AC +PS-360I160AC-P+4(ISFP-GIG-LH70) OS6855-24+PS-120I80DC48+PS-100I80DC24+4(ISFP-100-MM) OS6855-24+PS-120I80DC48 +PS-100I80DC24+4(ISFP-100-SM15) OS6855-24+PS-120I80DC48 +PS-100I80DC24+4(ISFP-100-SM40) OS6855-24+PS-120I80DC48 +PS-100I80DC24+4(ISFP-100-BX-U) OS6855-24+PS-120I80DC48 +PS-100I80DC24+4(ISFP-100-BX-D) OS6855-24+PS-120I80DC48 +PS-100I80DC24+4(ISFP-GIG-SX) OS6855-24+PS-120I80DC48 +PS-100I80DC24+4(ISFP-GIG-LX) OS6855-24+PS-120I80DC48 +PS-100I80DC24+4(ISFP-GIG-LH40) OS6855-24+PS-120I80DC48 +PS-100I80DC24+4(ISFP-GIG-LH70) OS6855-24+PS-120I80DC48 +PS-360I160AC-P+4(ISFP-100-MM) OS6855-24+PS-120I80DC48 +PS-360I160AC-P+4(ISFP-100-SM15) OS6855-24+PS-120I80DC48 +PS-360I160AC-P+4(ISFP-100-SM40) OS6855-24+PS-120I80DC48 +PS-360I160AC-P+4(ISFP-100-BX-U) OS6855-24+PS-120I80DC48 +PS-360I160AC-P+4(ISFP-100-BX-D) OS6855-24+PS-120I80DC48 +PS-360I160AC-P+4(ISFP-GIG-SX) OS6855-24+PS-120I80DC48 +PS-360I160AC-P+4(ISFP-GIG-LX) OS6855-24+PS-120I80DC48 +PS-360I160AC-P+4(ISFP-GIG-LH40) OS6855-24+PS-120I80DC48 +PS-360I160AC-P+4(ISFP-GIG-LH70) OS6855-24+PS-100I80DC24 +PS-360I160AC-P+4(ISFP-100-MM) OS6855-24+PS-100I80DC24 +PS-360I160AC-P+4(ISFP-100-SM15) OS6855-24+PS-100I80DC24 +PS-360I160AC-P+4(ISFP-100-SM40) OS6855-24+PS-100I80DC24 +PS-360I160AC-P+4(ISFP-100-BX-U) OS6855-24+PS-100I80DC24 +PS-360I160AC-P+4(ISFP-100-BX-D)
193147 183645 192333 192300 185930 182051 182051 196502 196502 193303 183785 192487 192454 114077 112481 112481 118326 118326 117055 113197 116729 116715 170192 167022 167022 178751 178751 176173 168441 175514 175487 98371 97183 97183 101515 101515 100578 97717 100337 100327 98604 97410 97410 101763 101763
22.04874429 20.9640411 21.95582192 21.95205479 21.22488584 20.78207763 20.78207763 22.43173516 22.43173516 22.06655251 20.98002283 21.97340183 21.9696347 13.02248858 12.8402968 12.8402968 13.50753425 13.50753425 13.36244292 12.92203196 13.32522831 13.32363014 19.4283105 19.06643836 19.06643836 20.4053653 20.4053653 20.11107306 19.22842466 20.03584475 20.03276256 11.22956621 11.09394977 11.09394977 11.58847032 11.58847032 11.48150685 11.15490868 11.45399543 11.45285388 11.25616438 11.11986301 11.11986301 11.61678082 11.61678082
Page 32
OS6855-24+PS-100I80DC24 +PS-360I160AC-P+4(ISFP-GIG-SX) OS6855-24+PS-100I80DC24 +PS-360I160AC-P+4(ISFP-GIG-LX) OS6855-24+PS-100I80DC24 +PS-360I160AC-P+4(ISFP-GIG-LH40) OS6855-24+PS-100I80DC24 +PS-360I160AC-P+4(ISFP-GIG-LH70) OS6855-U24 OS6855-U24-Fans PS-126I80AC (80W AC Pwr Supply OS6855-PSL) PS-120I80DC48 (80W-48VDC PS OS6855-PSL-D ) PS-100I80DC24 (80W-24VDC PS OS6855-PSL-DL ) OS6855-U24-PCBA(No Fan.No PS.No SFP) OS6855-U24 (No PS. No SFP) OS6855-U24+PS-126I80AC (No SFP) OS6855-U24+2(PS-126I80AC) (No SFP) OS6855-U24+PS-120I80DC48 (No SFP) OS6855-U24+2(PS-120I80DC48)(No SFP) OS6855-U24+PS-100I80DC24 (No SFP) OS6855-U24+2(PS-100I80DC24)(No SFP) OS6855-U24+PS-126I80AC +PS-120I80DC48 (No SFP) OS6855-U24+PS-126I80AC +PS-100I80DC24 (No SFP) OS6855-U24+PS-120I80DC48 +PS-100I80DC24 (No SFP) ISFP-100-MM ISFP-100-SM15 ISFP-100-SM40 ISFP-100-BX-U ISFP-100-BX-D ISFP-GIG-SX ISFP-GIG-LX ISFP-GIG-LH40 ISFP-GIG-LH70 OS6855-U24+PS-126I80AC +24(ISFP-100-MM) OS6855-U24+PS-126I80AC +24(ISFP-100-SM15) OS6855-U24+PS-126I80AC +24(ISFP-100-SM40) OS6855-U24+PS-126I80AC +24(ISFP-100-BX-U) OS6855-U24+PS-126I80AC +24(ISFP-100-BX-D) OS6855-U24+PS-126I80AC +24(ISFP-GIG-SX) OS6855-U24+PS-126I80AC +24(ISFP-GIG-LX) OS6855-U24+PS-126I80AC +24(ISFP-GIG-LH40) OS6855-U24+PS-126I80AC +24(ISFP-GIG-LH70) OS6855-U24+2(PS-126I80AC) +24(ISFP-100-MM) OS6855-U24+2(PS-126I80AC) +24(ISFP-100-SM15) OS6855-U24+2(PS-126I80AC) +24(ISFP-100-SM40) OS6855-U24+2(PS-126I80AC) +24(ISFP-100-BX-U) OS6855-U24+2(PS-126I80AC)+24(ISFP-100-BX-D) OS6855-U24+2(PS-126I80AC) +24(ISFP-GIG-SX) OS6855-U24+2(PS-126I80AC) +24(ISFP-GIG-LX) OS6855-U24+2(PS-126I80AC) +24(ISFP-GIG-LH40)
100822 97946 100579 100570 562238 561803 314515 316907 488705 261449 178418 221365 142769 187226 143260 187744 207256 207436 187485 5220297 4491556 4491556 8861320 8861320 7363770 4794094 7053678 7041758 98018 91339 91339 120290 120290 112816 94242 111021 110950 112572 104108 104108 141491 141491 131671 107775 129331
11.50936073 11.18105023 11.481621 11.48059361 64.18242009 64.13276256 35.90353881 36.17659817 55.78824201 29.84577626 20.3673516 25.26997717 16.29783105 21.37283105 16.35388128 21.43196347 23.65936073 23.67990868 21.40239726 595.9243151 512.7347032 512.7347032 1011.56621 1011.56621 840.6130137 547.2710046 805.2143836 803.853653 11.18926941 10.42682648 10.42682648 13.73173516 13.73173516 12.87853881 10.75821918 12.67363014 12.66552511 12.85068493 11.88447489 11.88447489 16.15194064 16.15194064 15.03093607 12.30308219 14.76381279
Page 33
OS6855-U24+2(PS-126I80AC) +24(ISFP-GIG-LH70) OS6855-U24+PS-120I80DC48 +24(ISFP-100-MM) OS6855-U24+PS-120I80DC48 +24(ISFP-100-SM15) OS6855-U24+PS-120I80DC48 +24(ISFP-100-SM40) OS6855-U24+PS-120I80DC48 +24(ISFP-100-BX-U) OS6855-U24+PS-120I80DC48 +24(ISFP-100-BX-D) OS6855-U24+PS-120I80DC48 +24(ISFP-GIG-SX) OS6855-U24+PS-120I80DC48 +24(ISFP-GIG-LX) OS6855-U24+PS-120I80DC48 +24(ISFP-GIG-LH40) OS6855-U24+PS-120I80DC48 +24(ISFP-GIG-LH70) OS6855-U24+2(PS-120I80DC48) +24(ISFP-100-MM) OS6855-U24+2(PS-120I80DC48) +24(ISFP-100-SM15) OS6855-U24+2(PS-120I80DC48) +24(ISFP-100-SM40) OS6855-U24+2(PS-120I80DC48)+24(ISFP-100-BX-U) OS6855-U24+2(PS-120I80DC48)+24(ISFP-100-BX-D) OS6855-U24+2(PS-120I80DC48) +24(ISFP-GIG-SX) OS6855-U24+2(PS-120I80DC48) +24(ISFP-GIG-LX) OS6855-U24+2(PS-120I80DC48) +24(ISFP-GIG-LH40) OS6855-U24+2(PS-120I80DC48) +24(ISFP-GIG-LH70) OS6855-U24+PS-100I80DC24 +24(ISFP-100-MM) OS6855-U24+PS-100I80DC24 +24(ISFP-100-SM15) OS6855-U24+PS-100I80DC24 +24(ISFP-100-SM40) OS6855-U24+PS-100I80DC24 +24(ISFP-100-BX-U) OS6855-U24+PS-100I80DC24 +24(ISFP-100-BX-D) OS6855-U24+PS-100I80DC24+24(ISFP-GIG-SX) OS6855-U24+PS-100I80DC24 +24(ISFP-GIG-LX) OS6855-U24+PS-100I80DC24+24(ISFP-GIG-LH40) OS6855-U24+PS-100I80DC24+24(ISFP-GIG-LH70) OS6855-U24+2(PS-100I80DC24)+24(ISFP-100-MM) OS6855-U24+2(PS-100I80DC24) +24(ISFP-100-SM15) OS6855-U24+2(PS-100I80DC24) +24(ISFP-100-SM40) OS6855-U24+2(PS-100I80DC24) +24(ISFP-100-BX-U) OS6855-U24+2(PS-100I80DC24) +24(ISFP-100-BX-D) OS6855-U24+2(PS-100I80DC24) +24(ISFP-GIG-SX) OS6855-U24+2(PS-100I80DC24) +24(ISFP-GIG-LX) OS6855-U24+2(PS-100I80DC24) +24(ISFP-GIG-LH40) OS6855-U24+2(PS-100I80DC24) +24(ISFP-GIG-LH70) OS6855-U24+PS-126I80AC +PS-120I80DC48+24(ISFP-100-MM) OS6855-U24+PS-126I80AC +PS-120I80DC48+24(ISFP-100-SM15) OS6855-U24+PS-126I80AC +PS-120I80DC48+24(ISFP-100-SM40) OS6855-U24+PS-126I80AC +PS-120I80DC48+24(ISFP-100-BX-U) OS6855-U24+PS-126I80AC +PS-120I80DC48+24(ISFP-100-BX-D) OS6855-U24+PS-126I80AC +PS-120I80DC48+24(ISFP-GIG-SX) OS6855-U24+PS-126I80AC +PS-120I80DC48+24(ISFP-GIG-LX) OS6855-U24+PS-126I80AC +PS-120I80DC48+24(ISFP-GIG-LH40)
129238 86194 80987 80987 102958 102958 97432 83261 96091 96038 104716 97556 97556 128313 128313 120448 100672 118551 118476 86372 81145 81145 103213 103213 97661 83427 96313 96260 104853 97672 97672 128534 128534 120638 100797 118734 118659 109471 101534 101534 136212 136212 127197 104979 125038
14.75319635 9.839497717 9.245091324 9.245091324 11.75319635 11.75319635 11.12237443 9.504680365 10.96929224 10.96324201 11.95388128 11.13652968 11.13652968 14.64760274 14.64760274 13.74977169 11.49223744 13.53321918 13.52465753 9.859817352 9.263127854 9.263127854 11.78230594 11.78230594 11.14851598 9.523630137 10.9946347 10.98858447 11.96952055 11.14977169 11.14977169 14.67283105 14.67283105 13.77146119 11.50650685 13.55410959 13.54554795 12.4966895 11.59063927 11.59063927 15.54931507 15.54931507 14.52020548 11.98390411 14.27374429
Page 34
OS6855-U24+PS-126I80AC +PS-120I80DC48+24(ISFP-GIG-LH70) OS6855-U24+PS-126I80AC +PS-100I80DC24+24(ISFP-100-MM) OS6855-U24+PS-126I80AC +PS-100I80DC24+24(ISFP-100-SM15) OS6855-U24+PS-126I80AC +PS-100I80DC24+24(ISFP-100-SM40) OS6855-U24+PS-126I80AC +PS-100I80DC24+24(ISFP-100-BX-U) OS6855-U24+PS-126I80AC +PS-100I80DC24+24(ISFP-100-BX-D) OS6855-U24+PS-126I80AC +PS-100I80DC24+24(ISFP-GIG-SX) OS6855-U24+PS-126I80AC +PS-100I80DC24+24(ISFP-GIG-LX) OS6855-U24+PS-126I80AC +PS-100I80DC24+24(ISFP-GIG-LH40) OS6855-U24+PS-126I80AC +PS-100I80DC24+24(ISFP-GIG-LH70) OS6855-U24+PS-120I80DC48 +PS-100I80DC24+24(ISFP-100-MM) OS6855-U24+PS-120I80DC48 +PS-100I80DC24+24(ISFP-100-SM15) OS6855-U24+PS-120I80DC48 +PS-100I80DC24+24(ISFP-100-SM40) OS6855-U24+PS-120I80DC48 +PS-100I80DC24+24(ISFP-100-BX-U) OS6855-U24+PS-120I80DC48 +PS-100I80DC24+24(ISFP-100-BX-D) OS6855-U24+PS-120I80DC48 +PS-100I80DC24+24(ISFP-GIG-SX) OS6855-U24+PS-120I80DC48 +PS-100I80DC24+24(ISFP-GIG-LX) OS6855-U24+PS-120I80DC48+PS-100I80DC24+24(ISFP-GIG-LH40) OS6855-U24+PS-120I80DC48 +PS-100I80DC24+24(ISFP-GIG-LH70) OS6855-U24X OS6855-U24X (No PS. No SFP) OS6855-U24X+PS-126I80AC (No SFP) OS6855-U24X+2(PS-126I80AC)(No SFP) OS6855-U24X+PS-120I80DC48(No SFP) OS6855-U24X+2(PS-120I80DC48)(No SFP) OS6855-U24X+PS-100I80DC24(No SFP) OS6855-U24X+2(PS-100I80DC24)(No SFP) OS6855-U24X+PS-126I80AC +PS-120I80DC48 (No SFP) OS6855-U24X+PS-126I80AC +PS-100I80DC24 (No SFP) OS6855-U24X+PS-120I80DC48 +PS-100I80DC24 (No SFP) OS6855-U24X+PS-126I80AC +24(ISFP-100-MM) OS6855-U24X+PS-126I80AC +24(ISFP-100-SM15) OS6855-U24X+PS-126I80AC +24(ISFP-100-SM40) OS6855-U24X+PS-126I80AC +24(ISFP-100-BX-U) OS6855-U24X+PS-126I80AC +24(ISFP-100-BX-D) OS6855-U24X+PS-126I80AC +24(ISFP-100-BXLC-U) OS6855-U24X+PS-126I80AC +24(ISFP-100-BXLC-D) OS6855-U24X+PS-126I80AC +24(ISFP-GIG-SX) OS6855-U24X+PS-126I80AC +24(ISFP-GIG-LX) OS6855-U24X+PS-126I80AC +24(ISFP-GIG-LH40) OS6855-U24X+PS-126I80AC +24(ISFP-GIG-LH70) OS6855-U24X+PS-126I80AC +24(ISFP-GIG-BX-U) OS6855-U24X+PS-126I80AC +24(ISFP-GIG-BX-D) OS6855-U24X+PS-126I80AC +24(ISFP-GIG-T) OS6855-U24X+PS-126I80AC +2(ISFP-10G-SR) OS6855-U24X+PS-126I80AC +2(ISFP-10G-LR)
124953 109515 101571 101571 136286 136286 127259 105019 125098 125013 104785 97614 97614 128424 128424 120543 100735 118643 118568 373980 224521 288502 170840 230969 171543 231784 264149 264441 231378 110481 102069 102069 139620 139620 144596 144596 129649 105707 127285 127191 109241 109427 138157 212748 195212
14.2640411 12.50171233 11.59486301 11.59486301 15.55776256 15.55776256 14.52728311 11.98847032 14.28059361 14.27089041 11.96175799 11.14315068 11.14315068 14.66027397 14.66027397 13.76061644 11.49942922 13.54372146 13.53515982 42.69178082 25.63025114 32.93401826 19.50228311 26.3663242 19.58253425 26.45936073 30.15399543 30.18732877 26.4130137 12.6119863 11.65171233 11.65171233 15.93835616 15.93835616 16.50639269 16.50639269 14.80011416 12.06700913 14.53025114 14.51952055 12.47043379 12.49166667 15.77134703 24.28630137 22.28447489
Page 35
OS6855-U24X+2(PS-126I80AC) +24(ISFP-100-MM) OS6855-U24X+2(PS-126I80AC) +24(ISFP-100-SM15) OS6855-U24X+2(PS-126I80AC) +24(ISFP-100-SM40) OS6855-U24X+2(PS-126I80AC) +24(ISFP-100-BX-U) OS6855-U24X+2(PS-126I80AC) +24(ISFP-100-BX-D) OS6855-U24X+2(PS-126I80AC) +24(ISFP-100-BXLC-U) OS6855-U24X+2(PS-126I80AC) +24(ISFP-100-BXLC-D) OS6855-U24X+2(PS-126I80AC) +24(ISFP-GIG-SX) OS6855-U24X+2(PS-126I80AC) +24(ISFP-GIG-LX) OS6855-U24X+2(PS-126I80AC) +24(ISFP-GIG-LH40) OS6855-U24X+2(PS-126I80AC) +24(ISFP-GIG-LH70) OS6855-U24X+2(PS-126I80AC) +24(ISFP-GIG-BX-U) OS6855-U24X+2(PS-126I80AC) +24(ISFP-GIG-BX-D) OS6855-U24X+2(PS-126I80AC) +24(ISFP-GIG-T) OS6855-U24X+2(PS-126I80AC) +2(ISFP-10G-SR) OS6855-U24X+2(PS-126I80AC) +2(ISFP-10G-LR) OS6855-U24X+PS-120I80DC48 +24(ISFP-100-MM) OS6855-U24X+PS-120I80DC48 +24(ISFP-100-SM15) OS6855-U24X+PS-120I80DC48 +24(ISFP-100-SM40) OS6855-U24X+PS-120I80DC48 +24(ISFP-100-BX-U) OS6855-U24X+PS-120I80DC48 +24(ISFP-100-BX-D) OS6855-U24X+PS-120I80DC48 +24(ISFP-100-BXLC-U) OS6855-U24X+PS-120I80DC48 +24(ISFP-100-BXLC-D) OS6855-U24X+PS-120I80DC48 +24(ISFP-GIG-SX) OS6855-U24X+PS-120I80DC48 +24(ISFP-GIG-LX) OS6855-U24X+PS-120I80DC48 +24(ISFP-GIG-LH40) OS6855-U24X+PS-120I80DC48 +24(ISFP-GIG-LH70) OS6855-U24X+PS-120I80DC48 +24(ISFP-GIG-BX-U) OS6855-U24X+PS-120I80DC48 +24(ISFP-GIG-BX-D) OS6855-U24X+PS-120I80DC48 +24(ISFP-GIG-T) OS6855-U24X+PS-120I80DC48 +2(ISFP-10G-SR) OS6855-U24X+PS-120I80DC48 +2(ISFP-10G-LR) OS6855-U24X+2(PS-120I80DC48) +24(ISFP-100-MM) OS6855-U24X+2(PS-120I80DC48) +24(ISFP-100-SM15) OS6855-U24X+2(PS-120I80DC48) +24(ISFP-100-SM40) OS6855-U24X+2(PS-120I80DC48) +24(ISFP-100-BX-U) OS6855-U24X+2(PS-120I80DC48) +24(ISFP-100-BX-D) OS6855-U24X+2(PS-120I80DC48) +24(ISFP-100-BXLC-U) OS6855-U24X+2(PS-120I80DC48) +24(ISFP-100-BXLC-D) OS6855-U24X+2(PS-120I80DC48) +24(ISFP-GIG-SX) OS6855-U24X+2(PS-120I80DC48) +24(ISFP-GIG-LX) OS6855-U24X+2(PS-120I80DC48) +24(ISFP-GIG-LH40) OS6855-U24X+2(PS-120I80DC48) +24(ISFP-GIG-LH70) OS6855-U24X+2(PS-120I80DC48) +24(ISFP-GIG-BX-U) OS6855-U24X+2(PS-120I80DC48) +24(ISFP-GIG-BX-D)
128627 117755 117755 167388 167388 174168 174168 153941 122440 150780 150655 127015 127257 165404 271080 245469 95686 89311 89311 116797 116797 120259 120259 109738 92084 108039 107972 94754 94895 115772 163937 153324 117979 109043 109043 148371 148371 153463 153463 138076 112916 135619 135522 116666 116864
14.68344749 13.4423516 13.4423516 19.10821918 19.10821918 19.88219178 19.88219178 17.57317352 13.97716895 17.21232877 17.19805936 14.49942922 14.52705479 18.88173516 30.94520548 28.02157534 10.92305936 10.19531963 10.19531963 13.33299087 13.33299087 13.72819635 13.72819635 12.52716895 10.51187215 12.33321918 12.32557078 10.81666667 10.83276256 13.21598174 18.71426941 17.50273973 13.46792237 12.44783105 12.44783105 16.93732877 16.93732877 17.51860731 17.51860731 15.76210046 12.88995434 15.481621 15.47054795 13.31803653 13.34063927
Page 36
OS6855-U24X+2(PS-120I80DC48) +24(ISFP-GIG-T) OS6855-U24X+2(PS-120I80DC48) +2(ISFP-10G-SR) OS6855-U24X+2(PS-120I80DC48) +2(ISFP-10G-LR) OS6855-U24X+PS-100I80DC24 +24(ISFP-100-MM) OS6855-U24X+PS-100I80DC24 +24(ISFP-100-SM15) OS6855-U24X+PS-100I80DC24 +24(ISFP-100-SM40) OS6855-U24X+PS-100I80DC24+24(ISFP-100-BX-U) OS6855-U24X+PS-100I80DC24 +24(ISFP-100-BX-D) OS6855-U24X+PS-100I80DC24 +24(ISFP-100-BXLC-U) OS6855-U24X+PS-100I80DC24 +24(ISFP-100-BXLC-D) OS6855-U24X+PS-100I80DC24 +24(ISFP-GIG-SX) OS6855-U24X+PS-100I80DC24 +24(ISFP-GIG-LX) OS6855-U24X+PS-100I80DC24 +24(ISFP-GIG-LH40) OS6855-U24X+PS-100I80DC24 +24(ISFP-GIG-LH70) OS6855-U24X+PS-100I80DC24 +24(ISFP-GIG-BX-U) OS6855-U24X+PS-100I80DC24 +24(ISFP-GIG-BX-D) OS6855-U24X+PS-100I80DC24 +24(ISFP-GIG-T) OS6855-U24X+PS-100I80DC24 +2(ISFP-10G-SR) OS6855-U24X+PS-100I80DC24 +2(ISFP-10G-LR) OS6855-U24X+2(PS-100I80DC24) +24(ISFP-100-MM) OS6855-U24X+2(PS-100I80DC24) +24(ISFP-100-SM15) OS6855-U24X+2(PS-100I80DC24) +24(ISFP-100-SM40) OS6855-U24X+2(PS-100I80DC24) +24(ISFP-100-BX-U) OS6855-U24X+2(PS-100I80DC24) +24(ISFP-100-BX-D) OS6855-U24X+2(PS-100I80DC24) +24(ISFP-100-BXLC-U) OS6855-U24X+2(PS-100I80DC24) +24(ISFP-100-BXLC-D) OS6855-U24X+2(PS-100I80DC24) +24(ISFP-GIG-SX) OS6855-U24X+2(PS-100I80DC24) +24(ISFP-GIG-LX) OS6855-U24X+2(PS-100I80DC24) +24(ISFP-GIG-LH40) OS6855-U24X+2(PS-100I80DC24) +24(ISFP-GIG-LH70) OS6855-U24X+2(PS-100I80DC24) +24(ISFP-GIG-BX-U) OS6855-U24X+2(PS-100I80DC24) +24(ISFP-GIG-BX-D) OS6855-U24X+2(PS-100I80DC24) +24(ISFP-GIG-T) OS6855-U24X+2(PS-100I80DC24) +2(ISFP-10G-SR) OS6855-U24X+2(PS-100I80DC24) +2(ISFP-10G-LR) OS6855-U24X+PS-126I80AC +PS-120I80DC48+24(ISFP-100-MM) OS6855-U24X+PS-126I80AC +PS-120I80DC48+24(ISFP-100-SM15) OS6855-U24X+PS-126I80AC +PS-120I80DC48+24(ISFP-100-SM40) OS6855-U24X+PS-126I80AC +PS-120I80DC48+24(ISFP-100-BX-U) OS6855-U24X+PS-126I80AC +PS-120I80DC48+24(ISFP-100-BX-D) OS6855-U24X+PS-126I80AC +PS-120I80DC48+24(ISFP-100-BXLC-U) OS6855-U24X+PS-126I80AC +PS-120I80DC48+24(ISFP-100-BXLC-D) OS6855-U24X+PS-126I80AC+PS-120I80DC48+24(ISFP-GIG-SX) OS6855-U24X+PS-126I80AC +PS-120I80DC48+24(ISFP-GIG-LX) OS6855-U24X+PS-126I80AC +PS-120I80DC48+24(ISFP-GIG-LH40)
146869 220104 203568 95906 89503 89503 117126 117126 120608 120608 110027 92288 108320 108252 94970 95111 116095 164584 153890 118160 109194 109194 148679 148679 153795 153795 138337 113080 135869 135772 116843 117041 147170 220839 204188 124388 114306 114306 159681 159681 165753 165753 147550 118660 144681
16.76586758 25.1260274 23.23835616 10.94817352 10.21723744 10.21723744 13.37054795 13.37054795 13.76803653 13.76803653 12.56015982 10.53515982 12.3652968 12.35753425 10.8413242 10.85742009 13.25285388 18.78812785 17.5673516 13.48858447 12.46506849 12.46506849 16.97248858 16.97248858 17.55650685 17.55650685 15.79189498 12.9086758 15.51015982 15.49908676 13.33824201 13.36084475 16.80022831 25.20993151 23.30913242 14.19954338 13.04863014 13.04863014 18.22842466 18.22842466 18.92157534 18.92157534 16.84360731 13.5456621 16.51609589
Page 37
OS6855-U24X+PS-126I80AC +PS-120I80DC48+24(ISFP-GIG-LH70) OS6855-U24X+PS-126I80AC +PS-120I80DC48+24(ISFP-GIG-BX-U) OS6855-U24X+PS-126I80AC +PS-120I80DC48+24(ISFP-GIG-BX-D) OS6855-U24X+PS-126I80AC +PS-120I80DC48+24(ISFP-GIG-T) OS6855-U24X+PS-126I80AC +PS-120I80DC48+2(ISFP-10G-SR) OS6855-U24X+PS-126I80AC +PS-120I80DC48+2(ISFP-10G-LR) OS6855-U24X+PS-126I80AC +PS-100I80DC24+24(ISFP-100-MM) OS6855-U24X+PS-126I80AC +PS-100I80DC24+24(ISFP-100-SM15) OS6855-U24X+PS-126I80AC +PS-100I80DC24+24(ISFP-100-SM40) OS6855-U24X+PS-126I80AC +PS-100I80DC24+24(ISFP-100-BX-U) OS6855-U24X+PS-126I80AC +PS-100I80DC24+24(ISFP-100-BX-D) OS6855-U24X+PS-126I80AC +PS-100I80DC24+24(ISFP-100-BXLC-U) OS6855-U24X+PS-126I80AC +PS-100I80DC24+24(ISFP-100-BXLC-D) OS6855-U24X+PS-126I80AC +PS-100I80DC24+24(ISFP-GIG-SX) OS6855-U24X+PS-126I80AC +PS-100I80DC24+24(ISFP-GIG-LX) OS6855-U24X+PS-126I80AC +PS-100I80DC24+24(ISFP-GIG-LH40) OS6855-U24X+PS-126I80AC +PS-100I80DC24+24(ISFP-GIG-LH70) OS6855-U24X+PS-126I80AC +PS-100I80DC24+24(ISFP-GIG-BX-U) OS6855-U24X+PS-126I80AC +PS-100I80DC24+24(ISFP-GIG-BX-D) OS6855-U24X+PS-126I80AC +PS-100I80DC24+24(ISFP-GIG-T) OS6855-U24X+PS-126I80AC +PS-100I80DC24+2(ISFP-10G-SR) OS6855-U24X+PS-126I80AC +PS-100I80DC24+2(ISFP-10G-LR) OS6855-U24X+PS-120I80DC48 +PS-100I80DC24+24(ISFP-100-MM) OS6855-U24X+PS-120I80DC48 +PS-100I80DC24+24(ISFP-100-SM15) OS6855-U24X+PS-120I80DC48 +PS-100I80DC24+24(ISFP-100-SM40) OS6855-U24X+PS-120I80DC48 +PS-100I80DC24+24(ISFP-100-BX-U) OS6855-U24X+PS-120I80DC48 +PS-100I80DC24+24(ISFP-100-BX-D) OS6855-U24X+PS-120I80DC48 +PS-100I80DC24+24(ISFP-100-BXLC-U) OS6855-U24X+PS-120I80DC48 +PS-100I80DC24+24(ISFP-100-BXLC-D) OS6855-U24X+PS-120I80DC48 +PS-100I80DC24+24(ISFP-GIG-SX) OS6855-U24X+PS-120I80DC48 +PS-100I80DC24+24(ISFP-GIG-LX) OS6855-U24X+PS-120I80DC48 +PS-100I80DC24+24(ISFP-GIG-LH40) OS6855-U24X+PS-120I80DC48 +PS-100I80DC24+24(ISFP-GIG-LH70) OS6855-U24X+PS-120I80DC48 +PS-100I80DC24+24(ISFP-GIG-BX-U) OS6855-U24X+PS-120I80DC48 +PS-100I80DC24+24(ISFP-GIG-BX-D) OS6855-U24X+PS-120I80DC48+PS-100I80DC24+24(ISFP-GIG-T) OS6855-U24X+PS-120I80DC48 +PS-100I80DC24+2(ISFP-10G-SR) OS6855-U24X+PS-120I80DC48 +PS-100I80DC24+2(ISFP-10G-LR)
144568 122899 123123 157899 249607 227958 124448 114355 114355 159785 159785 165865 165865 147638 118713 144765 144651 122957 123181 158000 249869 228176 118070 109118 109118 148525 148525 153629 153629 138207 112998 135744 135647 116755 116953 147020 220472 203879
16.50319635 14.02956621 14.05513699 18.025 28.49394977 26.02260274 14.20639269 13.05422374 13.05422374 18.2402968 18.2402968 18.93436073 18.93436073 16.85365297 13.55171233 16.52568493 16.51267123 14.03618721 14.06175799 18.03652968 28.52385845 26.04748858 13.4783105 12.45639269 12.45639269 16.95490868 16.95490868 17.53755708 17.53755708 15.77705479 12.89931507 15.49589041 15.48481735 13.32819635 13.35079909 16.78310502 25.16803653 23.27385845
Regulatory Compliance and Safety Information

This section provides information on regulatory agency compliance and safety for the OmniSwitch 6855 Series.
Page 38
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.
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 Standards
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 for UL (Safety Laser Evaluation)
EMC Standards
Commercial EMI/EMC FCC CRF Title 47 Subpart B (Class A and Class B* limits) VCCI (Class A and Class B* limits AS/NZS 3548 (Class A and Class B*) CE marking for European countries (Class A and Class B*) EN 55022: 2006 (Emission Standard) EN 61000-3-3: 1995 EN 61000-3-2: 2006 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) * Class A with UTP cables and Class B with STP cables OS6855 Series Boilerplate Doc. Rev.2.1a / Nov. 09 Page 39 Alcatel.Lucent-ESD Calabasas/CA./USA
Industrial IEC 60870-2-2 (operational temperature) IEC 60068-2-1 (temperature type test cold) IEC 60068-2-2 (temperature type test hot) IEC 60721-3-1: Class 1K5 (storage temperature) IEC 68-2-30 95% non-condensing humidity IEC 60255-21-2 (mechanical shock) IEC 60255-21-1 (vibration) EN 61131-2 EN 61000-6-4 :2007 (emission standard for industrial environments) EN 61000-6-2 :2005 ( immunity standard for industrial environments) EN 55024: 1998 (Immunity Standards) -IEC 61000-4-3 -IEC 61000-4-12 -IEC 61000-4-16 -IEC 61000-4-17 -IEC 61000-4-29 IEC 60255-5 IEC 61850-3 (Electric power Substations) see details in table below IEEE 1613 (C37.90.x) C37.90.3 (ESD) C37.90.2 (Radiated RFI) IEEE1613 C37.90.1 (Fast Transient ) IEEE1613 C37.90.1 ( Oscillatory ) IEEE1613 C37.90 (H.V. Impulse) IEEE1613 C37.90 (Dielectric Strength) IEC 62236-4:2008- Railway applications: Electromagnetic compatibility Part 4 EN 50121-4:2006 for Class A device
IEC 61850-3:2002 Details

Standards/Specification EN 55022:2006 EN 55022:2006 EN 55022:2006 EN 61000-3-2:2000 Test Description Conducted Emissions - Voltage Conducted Distrubance at Telecom Ports Radiated Emissions Harmonic Current Emissions Limits/Test Specification Class A & Class B Class A & Class B Class A & Class B Quasi-Stationary Current Harmonics Test 230V@50Hz, 39th Odd Harmonics and 40th Even harmonics Voltage Fluctuation and Flicker Test 230V@50Hz. Air Discharge: + 15kV Contact Discharge: + 8kV Amplitude modulated 80% over the frequency range 80MHz to 2.5GHz at a level of 3 V/m + 4kV Line to Neutral: + 2kV Line to Ground: + 4kV .150 MHz to 80 MHz, 10Vrms with an amplitude modulated 1 kHz sine wave at 80%. 40 A/m cont. 1000 A/m for 1 Sec Field @ 50Hz, X, Y, & Z-axis. Voltage Dips: 30% drop for 20ms, 3 time Voltage Dips: 60% drop for 1000ms, 3 time Short Interrupt: 100% drop for 100ms, 3 time Short Interrupt: 100% drop for 1000ms, 3 time Voltage Dips: 30% drop for 20ms or 1 cycle, 3 time
EN 61000-3-3:1995+A1:2001 EN61000-4-2:1995+A1:1998+A2:2002 EN61000-4-3:2002+A1:2002 EN61000-4-4:1995+A1:2001+A2:2001 EN61000-4-5:1994+A1:2001 EN61000-4-6:1994+A1:2001 EN61000-4-8:1994+A1:2001 EN61000-4-29:2000
Voltage Fluctuations/Flicker Electrostatic Discharge Immunity Radiated Electromagnetics Field Immunity Electrical Fast Transient/Burst Immunity Test Surge Immunity Test Conducted Radio-Frequency Immunity Power Frequency Magnetic Fields Immunity Voltage Dips and Interrupts DC Input Power Ports
EN61000-4-11:1994+A1:2001
Voltage Dips, Interruptions and Variations
Page 40
EN61000-4-12:2006
Ring Wave immunity Test (Damped Oscillatory) Test for Immunity to conducted, common mode distrubances in the frequency range 0 Hz to 150 kHz Ripple on DC Power Supply
EN61000-4-16:1998+A1:2004
Voltage Dips: 60% drop for 1000ms or 50 cycle, 3 time Short Interrupt: 100% drop for 100ms or 5 cycle, 3 time Short Interrupt: 100% drop for 1000ms or 50 cycle, 3 time AC, Differntial Mode Line to Neutral: + 2.0kV (0, 90, 270) Line to Ground: + 4.0kV (0, 90, 270) 10 Vrms, 0.15 MHz to 80 MHz
EN61000-4-17:2002
Voltage Dips: 30% drop for 20ms, 3 time Voltage Dips: 60% drop for 1000ms, 3 time Short Interrupt: 100% drop for 100ms, 3 time Short Interrupt: 100% drop for 1000ms, 3 time Enclosure Contact: + 8 kV Enclosure Ports: + 15 kV 35 V/m Signal Ports: + 4kV @2.5KHz D.C Power Ports: + 4kV A.C Power Ports: + 4kV Earth Ground Ports: + 4kV Signal Ports: 2.5kV common mode @1 MHz DC Power Ports: 2.5kV common, 1kV differential mode @ 1MHz AC Power Ports: 2.5kV common, 1kV differential mode @ 1MHz Signal Ports: 5kV (Fail-Safe Relay output) DC Power Ports: 5kV AC Power Ports: 5kV Signal Ports: 2kVac DC Power Ports: 2kVac AC Power Ports: 2kVac
IEC 60255-5 IEEE 1613, C37.90.3 IEEE 1613, C37.90.2 IEEE 1613, C37.90.1
Dielectric & HV Impluse Electrostatic Discharge Immunity Radiated RFI Fast Transcient
IEEE 1613, C37.90.1
Oscillatory
IEEE 1613, C37.90
H.V. Impulse
IEEE 1613, C37.90
Dielectric Strength
Note: All test reports and certificate can be downloaed from the central repository accessible at: https://agile.esd.alcatel-lucent.com/Agile/PLMServlet?module=CMBaseHandler&opcode=forwardToMainMenu To search for documents, please: 1. Go to 'Global Searches' 2. Click on 'Compliance Searches' 3. Choose which Search/Product Line, then you can search for all or specific Compliance Documents
Safety and Environmental Standards

ETS 300 019 Storage Class 1.1 ETS 300 019 Transportation Class 2.3 ETS 300 019 Stationary Use Class 3.1 OmniSwitch 6855 switches comply with Class-A standards for digital devices per the FCC Part 15, ICES-003, EN 55022, CISPR 22, AS/NZS 3548, and VCCI standards. Modules with copper connectors meet Class-A requirements using unshielded (UTP) cables.
OmniSwitch 6855 Series Hardware & Software Features Overview Table
Page 41
C h iis ii ffiic iio C ha assss sT Te ec ch hn niic ca all S Sp pe ec c ca att on nss

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 PoE ports; speed, link/activity/PoE applied System LEDs: Switch ID (indicates the stack ID of the unit in the stack: 1 to 7) System (OK) (chassis HW/SW status) PS1 (primary power supply status) PS2 (backup power status) OS6855-U24X Specific: 7 segment LED display on the front ( indicates the mode ( stacking or uplink) and stack number Mounting Physical Dimensions (W x D x H) The OS6855 Series chassis are 1U (One Rack Unit) OmniSwitch-6855 is rack mountable in 19 (W) racks Base/wall mounging is also offered Chassis size without P/S or P/S shelf OS6855-24 , OS6855-U24 : 17.32 x 10.63 x 1.73in (44.0 x 27.0 x 4.4 cm) OS6855-14 , OS6855-U10 : 8.5 x 10.25 x 1.73in ( 21.5 x 26 x 4.4) OS6855-U24X: 17.25 x 10.87 x 1.73in ( 43.8 x 27.4 x 4.4 cm ) Total size including P/S shelf and mounting ears OS6855-24 , OS6855-U24 : 19.00 x 17.56 x 1.73 in (48.2 x 44.6 x 4.4 cm) OS6855-U24X: 19 x 17.60 x 1.73in ( 48.2 x 44.8 x 4.4 cm ) OS6855-14 , OS6855-U10 ( PS tray attached to the side): 19.00 x 10.25 x 1.73in OS6855-14 , OS6855-U10 ( PS tray attached to the back): 8.5 x 17.5 x 1.73in Switch weight (no PS): OS6855-14: 5.28lb/2.42kg OS6855-U10: 5.28lb/2.42kg OS6855-24: 8.34lb/3.78kg OS6855-U24: 8.34lb/3.78kg OS6855-U24X: 11.68 lb/5.3 kg Switch weight (with one PS): OS6855-14: 7.78lb/3.55kg OS6855-U10: 7.78lb/3.55kg OS6855-24: 11.8lb/5.35kg OS6855-U24: 11.8lb/5.35kg OS6855-U24X: 15.14 lb/6.87 kg
Weights
Power Consumption The OmniSwitch 6855 Series
Power consumption without PoE : The power consumption measurements were obtained from the AC input power using nominal input voltage of 120VAC and running full traffic on all ports. PoE is disabled. Operational conditions for the test setup: Active State: Maximum ports per system, and with full LAN traffic operation. Idle State: System is up and ready to work, but with no LAN traffic. Total Amount of ports and speed 8+2 @ 1,000Mbs 12+2 @ 1,000Mbs 24 @ 1,000Mbs 24 @ 1,000Mbs 24@1Gig - 2@10Gig Power Consumption Active State (Watt) 25 30 46 49 51 Power Consumption Idle State (Watt) 24 29 44 48 50
Product: OS6855-U10 OS6855-14 OS6855-24 OS6855-U24 OS6855-U24X
These are acutal measured numbers. When power budget needs to be calculate it is advisable to add 10% buffer over the power consumtion numbers above.
Page 42
Power consumption with PoE: Operational Conditions for the test setup: Active State: Typical Maximum Power (15.4W) per PoE Port, and maximum amount of ports utilized at 15.4W. Idle State: PoE System has been turned on, but Power Device (PD) is set to 0.0 W. OS6855-14 Power Supply Model Delivered Power at PoE Port (W) AC Input Power Per Port (W) Power Loss Per Port at System (W) AC Input Power Idle State (W) Amount of PoE Ports Tested at 15.4W Total AC Power (W) Total PoE Power Loss at System (W) Total PoE Power Loss at System(%) OS6855-PSS-P 15.4 17.5 2.1 7 4 77 15.4 20 OS6855-24 OS6855PSL-P 15.4 19.5 4.1 8 4 86 24.4 28.37
Product:
Number of PoE ports 4 @ 15.4W/ port 4 @ 15.4W/ port
System Power Consumption with PoE Idle State (Watt) 30W + 7W = 37 46W + 8W = 54
System Power Consumption with PoE Active State (Watt) (30 + 7+ 4 x 2.1) = 45.4 (46 + 8 + 4 x 4.1) = 70.4
OS6855-14 OS6855-24
Heat Dissipation The OmniSwitch 6855 Series
1-watt 3.41214 BTU/hr. Note: To calculate the heat dissipation for the PoE Models the following formula has been used: Heat Dissipation = Chassis Power Consumption as measured x 3.41214 BTU/hr. Heat Dissipation WITHOUT POE : OS6855-14: 30 watts x 3.41214 102.4 BTU/hr OS6855-U10: 25 watts x 3.41214 85.3 BTU/hr OS6855-24: 46 watts x 3.41214 157 BTU/hr OS6855-U24: 49 watts x 3.41214 167.2 BTU/hr OS6855-U24X: 51 watts x 3.41214 174 BTU/hr Heat Dissipation WITH POE : 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 6855 chassis. Therefore, we only account for the heat dissipated on the OmniSwitch 6855 chassis plus the heat dissipated on the PoE daughter card inside the chassis including the power loss per port at the system. OS6855-14: 45.4 watts x 3.41214 154.9 BTU/hr. OS6855-24: 70.4 watts x 3.41214 240.2 BTU/hr.
Power plug type
Electrical Requirements
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 6855 switches have the following general electrical requirements: Each switch requires one grounded electrical outlet for each power supply installed in the. OmniSwitch 6855 switches offer both AC and DC power supply support.
Page 43
Name Plates
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.
Metro Ethernet Forum (MEF) 9 and 14 certification
OS6855 models are MEF certified 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) The OmniSwitch 6855 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) Restriction on Hazardous Substances in Electrical and Electronic Equipment (RoHS) OS6855 family is RoHS 6/6 compliant 2) WEEE (Waste Electrical and Electronic Equipment) 3) NEBS Level 3 Certified *-Contact for availability
Reliability Tests
Compliancy
Page 44
RoHS Requirements
RoHS Restriction on Hazardous Substances
EU Council Decision 87/95/EEC WEEE
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
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 6855 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). 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 6855 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.
Service & Support

Default Warranty One year on Hardware, and 90-days on Software. Additional, optional support is available. Contact your local Alcatel-Lucent representative for more information.
Page 45
Limited Lifetime Warranty
Warranty Service & Support Programs & End Of Life Lifetime Support
Hardware Warranty
Software Warranty
Life Span
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 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. 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. Limited Lifetime Warranty does not apply to SFPs. 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.
Page 46
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)
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.
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 6855 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. 48K routing table 8K 12K 4K 6K 128 2K 2K 2K 2MB 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. * 2,097,152 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. 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. N/A SFP, and RJ45 connectors Not supported RS-232 Console Port (RJ-45 connector). The console-protecting chip SEMTEC LCDA15C-6 is used along with the RJ45 connector. OS6855-24: four Gigabit Ethernet SFP combo ports OS6855-U24: two Gigabit Ethernet SFP combo ports OS6855-14 and U10: No combo ports N/A
10-Gigabit Ethernet Interface Connectors Stacking Console Port Combo Ports
10GigE Uplinks
Page 47
POE /(Power over Ethernet) In-line Power Temperature Sensor Thermal detection & Shutdown Clock Power Supply
Fans LEDS
The OmniSwitch 6855 Series platforms are 1U (Rack Unit) high 19" Rack-Mountable Dynamic and automatic module ID selection All models conform to Alcatel-Lucent coloring and labeling scheme Switch Faade for Alcatel-Lucent label 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, 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 Power supplies are able to attach to the rear of the unit Insertion or removal of redundant power supply Remote mounting of both primary and backup power supplies Single BPS for chassis and POE Circuit breaker protected OS6855 units Redundant Fans support Noise level Operating Temperature Storage Temperature Operating Humidity Storage Humidity Loop protection against loop back UDLD Support Cat 5, 5e, 6, and 6e
Support POE with full compliance of IEEE 802.3af Temperature Sensor National Semi-Conductor LM77 is supported Thermal detection and shutdown is supported. Real Time Clock Main and backup power supplies are external either directly connected to the rear of the unit or remotely mounted. Supports redundant dual hot swappable power supplies 6855-14 and 6855-U10 are fanless OS6855-24 and U24 fans are off by default and turn on only at increased temperature Per port Link/Activity/PoE monitoring LED support System Power, BPS, and Diagnostic LED support Hardware Device Level features supported Supported. Supported. Supported Supported Supported Supported Supported Supported Supported (Future Release) N/A Supported Supported Supported Supported Supported Supported N/A N/A 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 on 6855-24 Supported 1:N redundancy for 24 port models 6855-14 and 6855-U10 are fanless All OmniSwitch 6855 platforms are noiseless at 25C -40C to +70 C for OS6855-14 and OS6855-U10 -40C to +75 C for OS6855-24 and OS6855-U24 -40C to +85C 5% to 95% (non-condensing) 5% to 95% (non-condensing) Supported Supported Supported
Page 48
Capability to disable transmit function (or reset) of each PHY individually
Supported
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 UNH (or equivalent) operation standards Connectors/ Cabling Supported Supported Supported Supported Supported: Power over Ethernet is supported on 10/100/1000BASE-T ports only Optical transceivers are hot swappable Supported Supported Supported
Ethernet Specifications
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 SFP ports: LC or SC 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. 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 10/100/1000Mbps, Gigabit Ethernet ports 10/100/1000Mbps, Gigabit Ethernet ports 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/10GigE 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 because anything larger than 1553 would not be accepted. The same holds true for packets forwarded between two GigE/10GigE 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.
Connector type
Connections supported 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
Page 49
Inter-Frame Gap
Interface Alias (Port Alias)
Peak Flood Rate Configuration
Flow Control Trap Port Link Messages
Per port rate limiting Per-port L2/L3 multicast & broadcast flood limit is supported. Re-settable Statistics Counters Duplex Mode support
Auto-negotiation Crossover
Verifying Ethernet Port Configurations
Diagnostics
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) 997Mbps (10-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. IEEE 802.3x flow control. 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 Not to require external PCs or test equipment for running diagnostics
Page 50
P Pe er rffo or rm ma an nc ce e
Raw Fabric Capacity Switching Capacity All of the models in 6855 family use 24 port packet processor . The raw fabric capacity for all is : 24Gbps Full Duplex or 48Gbps aggregate OS6855-U10/-U10D: 10 Gbps Full Duple x or 20 Gbps aggregate OS6855-14/-14D: 14 Gbps Full Duplex or 28 Gbps aggregate OS6855-24/-24D/-24DL: 24Gbps Full Duplex or 48Gbps aggregate OS6855-U24/-U24D/-U24DL: 24Gbps Full Duplex or 48Gbps aggregate OS6855-U24X/-U24XD/-U24XDL: 48Gbps Full Duple x or 96Gbps aggregate 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. (10 Gbps) / ((8 bits/ byte) * (X+20)) = 14,880,952.3 pps (1 Gbps) / ((8 bits/ byte) * (X+20)) = 1,488,095.23 pps (100 Mbps) / ((8 bits/ byte) * (X+20)) = 148,809.52 pps (10 Mbps) / ((8 bits/ byte) * (X+20)) = 14,880.95 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 2-port 10-Gigabit Eth uplink/stacking supports 2 x 10-Gigabit Eth ports at wire-speed: 2 * 14,880,952.3 pps = 29,761,904.6pps (approx: 29.8Mpps) The 10 Gigabit Eth ports throughput at wire-speeds: 10 * 1,488,095.23 pps = 14,880,952.3pps (approx: 14.9Mpps) The 14 Gigabit Eth ports throughput at wire-speeds: 14 * 1,488,095.23 pps = 20,833,333.22pps (approx: 20.8Mpps) The 24 Gigabit Eth ports throughput at wire-speeds: 24 * 1,488,095.23 pps = 35,714,285.52pps (approx: 35.7Mpps) The OS6855-U10/-U10D supports up to 10 GE ports at wire-speeds: 14.9Mpps The OS6855-14/-14D supports up to 14 GE ports at wire-speed: 20.8Mpps The OS6855-24/-24D/-24DL supports up to 24 GE ports at wire-speeds: 35.7Mpps The OS6855-U24/-U24D/-U24DL supports up to 24 GE ports at wire-speeds: 35.7Mpps The OS6855-U24X/-U24XD/-U24XDL supports up to 24 GE ports + 2 10G: 65.5Mpps Throughput Performance Or Forwarding Rate Per Stand-Alone Switch 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. (10Gbps) / ((8 bits/ byte) * (X+20)) = 812,743.82 pps (1Gbps) / ((8 bits/ byte) * (X+20)) = 81,274.38 pps (100 Mbps) / ((8 bits/ byte) * (X+20)) = 8,127.43 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. 10 * 81,274.38 pps s = 812,743.8 pps (approx: 812.7Kpps) The 14 Gigabit Eth ports throughput at wire-speeds:
Throughput Performance Or Forwarding Rate Per Stand-Alone Switch
@64Byte Packets
@1518Byte Packets
Page 51
14 * 81,274.38 pps =1,137,841.32 pps (approx: 1.14Mpps) The 24 Gigabit Eth ports throughput at wire-speeds: 24 * 81,274.38 pps = 1,950,585.12pps (approx: 1.95Mpps) The OS6855-U10/-U10D supports up to 10 GigE. Eth ports at wire-speeds: : 812.7Kpps The OS6855-14/-14D supports up to 14 GigE Eth ports at wire-speed: 1.14Mpps The OS6855-24/-24D/-24DL supports up to 24 GigE Eth ports at wire-speeds: 1.95Mpps The OS6855-U24/-U24D/-U24DL supports up to 24 GigE Eth ports at wire-speeds: 1.95Mpps Layer-2 & Layer-3 Forwarding Rate Per port Latency Wire-speed on 10Mbps port 14,880 pps with 64 Byte packets Wire-speed on 100Mbps port 148,809 pps with 64 Byte packets Wire-speed on Gigabit Ethernet port 1,488,095 pps with 64 Byte packets Notes for latency: Latency test results generated by IXIA Device Version 3.65.284 RFC 2544 Latency Test Latency Measurement Type: First bit In to First bit Out ----- FIFO Protocol: the Layer-2 & Layer-3 Frame Rate: 100%
The OmniSwitch 6855 Layer-2 & Layer-3 Latencies / Throughput

Port Speed: Gigabit Latency Throughput 64 Byte Packets Estimated around 4.5s Wire-speed: 1000Mbps Full Duplex Port: 1,488,096pps 64 Byte Packets Estimated around 68.4s Wire-speed: 100Mbps Full Duplex Port: 148,810pps 64 Byte Packets Estimated around TBD s Wire-speed: 10Mbps Full Duplex Port: 14,881pps 1518 Byte Packets Estimated around 16s Wire-speed: 1000Mbps Full Duplex Port: 81,275pps 1518 Byte Packets Estimated around 184.6s Wire-speed: 100Mbps Full Duplex Port: 8,128pps 1518 Byte Packets Estimated around TBD s Wire-speed: 10Mbps Full Duplex Port: 813pps
Port Speed: 100Mbps Latency Throughput
Port Speed: 10Mbps Latency Throughput
System
Boot time Cold 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 stand-alone configuration when the switch can join the network and start passing traffic: approximately 115 sec. Approximately 65 sec Alcatel-Lucent OmniSwitch 6855 switches are designed in such a way that is highly reliable under extreme stress conditions. The OmniSwitch 6855 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: Running in normal operational mode where system is running under the specified CPU threshold values. Running above the CPU threshold values all the time.
Image download time System Resiliency Verification
Interfaces
Power over Ethernet Stacking ports Combo ports IEEE 802.3af (supported on all POE type chassis) N/A OS6855-24: 4 x Combo ports which can be individually configured to be be 10/100/1000BaseT or
Page 52
10GigE uplinks Ethernet minimum size packet Ethernet IP packet maximum transmission _ MTU Flood Control
1000BaseX and that can support SFP transceivers. OS6855-U24: 2 x Combo ports which can be individually configured to be 10/100/1000BaseT or 1000BaseX and that can support SFP transceivers. OS6855-14 and OS6855-U10 do not have combo ports N/A 64 Bytes 1000Mbps (GigE) and 10,000Mbps (10GigE); 9,216 Bytes (Jumbo frames) 10/100Mbps Eth IP packet max transmission unit; 1553 Bytes 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 997 Mbps on 10Gig port 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.
Layer-2/Layer-3 Switching
Root bridge priority / path cost: 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 6800/6855/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
Group mobility Rules supported:
Binding rules supported
Rule Precedence:
Max. number of 1x1 STP instances Maximum VLANs
Page 53
VLAN Stacking & Translation
Maximum number of BPDUs the switch can handle MAC Address Table IP Address Table Routes Layer-2 Table Hashing
RSTP Performance Sub-second performance
Max number of configured VLANs per port A-VLAN
Max number of configured VLANs per system
Max number of system wide Rules Maximum number of rules per chassis:
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)? Alcatel-Lucent Response: YES. How many VLAN IDs does this device support? Alcatel-Lucent Response: Comply with up to 4093. Maximum Number of Tagged VLANs per Port: 4093 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 48K routing table 12K forwarding LPM entries, 8K hosts entries per module 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-Port Binding rule MAC-IP-Port Binding rule 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). 8 K (8,192) 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.
Page 54
Max number of MAC Rules
Max number of Subnet Rules Max number of Protocol Rules System
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
Static ARP with multicast Mac
The UDP Relay Services
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.) 16 + 1 per port Maximum of 16 rules of combining Protocol & Port-Protocol rules are supported (If IP-E2 is used, total of 14 rules are supported) 6 (Note: Support for IP, IPX, DECNet, AppleTalk, SNAP, and Ethertype) 64 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 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) Note: Maximum number of MAC rules, Authenticated VLAN Users, Binding Rules, and 802.1x Users all share the 1,024 MAC Rules 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. Note: Maximum number of MAC rules, Authenticated VLAN Users, Binding Rules, and 802.1x Users all share the 1,024 Mac Rules 253 253 32 aggregates of up to 8 ports each 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 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. That feature is not supported on 10Gig (Ingress). However, flooding on egress 10Gig is supported. 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. 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.
Page 55
Service BOOTP/DHCP (Bootstrap Protocol/ Dynamic Host Configuration Protocol) NBNS/NBDD Generic services Auto-negotiation Traffic Control
UDP Port Number 67/68 (Request / Response)
Configurable Options 1. Next Hop Address 2. Forward delay 3. Maximum hops
137/138 Any number
1. to 1. to
VLANs to forward VLANs to forward
Spanning Tree
Maximum Number of STP Instances: Per Stack and/or Per Chassis
Spanning Tree Root bridge priority / path cost
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.)? Alcatel-Lucent Response: YES. 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 253 Instances 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 10000 M 3 The default port path costs are: ( IEEE Std. 802.1Q-2005 32 Bit) Port Speed Path cost 10M 2000000 100M 200000 1000 M 20000 10000 M 2000 *- Not available The default link aggregation path costs are (16 Bit): Linkagg speed Linkagg size Path cost 2 60
Page 56
8 2 100M 4 8 1000M N/A 10000M N/A The default link aggregation path costs are (32 Bit): LinkAgg speed LinkAgg size 2 10M 4 8 2 100M 4 8 1000M 2 4 8 10000M *- Not available
30 12 9 7 3 2 Path cost 1200000 800000 600000 120000 80000 60000 12000 8000 6000
Port Monitoring
Port Mirroring Usage Guidelines
Port Mapping
STP convergence time (flat, 1x1, 802.1s) 802.1w rapid reconfiguration
2 1200 4 800 8 600 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. The maximum number of mirroring sessions is limited to one on OmniSwitch 6800, whereas two (2) mirroring sessions are allowed on OmniSwitch 9000 and OmniSwitch 6855. You cannot configure a port mirroring and a port monitoring session on the same NI module in an OmniSwitch 9000. You cannot configure port mirroring and monitoring on the same switching ASIC on OmniSwitch 6855 Series switches. Each switching ASIC controls 24 ports (e.g., ports 124, 2548, etc.). For example, if a port mirroring session is configured for ports 1/12 and 1/22, then configuring a port monitoring session for any of the ports between 1 and 24 is not allowed. If a port mirroring session is configured across two switching ASICs, then configuring a monitoring session is not allowed on any of the ports controlled by each of the ASICs involved. For example, if a port mirroring session is configured for ports 1/8 and 1/30 on a 48-port switch, then configuring a port monitoring session involving any of the ports between 1 and 48 is not allowed. Port mirroring is not supported on logical link aggregate ports however, it is supported on individual ports that are members of a link aggregate. An N-to-1 port mirroring session is configurable, where N can be a number from 1 to 24 In other words, you can configure up to 23 ports for a single destination port in a session. Once you execute the port mirroring source destination command to define the mirrored port and enable port mirroring status, the port mirroring command must be used to enable the port mirroring session. By default, the mirroring port is subject to Spanning Tree changes that could cause it to go into a blocked state. To prevent this, specify the vlan_id number of the mirroring port that is to remain unblocked when executing the command. Usage Guidelines - Remote Port Mirroring Remote Port mirroring is supported on OS6855 Use the rpmir-vlan parameter with this command to configure remote port mirroring. There must not be any physical loop present in the remote port mirroring VLAN. Spanning Tree must be disabled for the remote port mirroring VLAN. Source learning must be disabled or overridden on the ports belonging to the remote port mirroring VLAN on intermediate and destination switches. The QoS redirect feature can be used to override source learning. Port mapping feature is supported on 6850/6855/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
Page 57
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
User Definable Loopback Interface
Sever Load Balancing (SLB) Layer-3 Routing Protocols (IPv4)
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. The main advantage of Loop-back interface is a more reliable Network Management path through OmniVista or an NMS station. Also, you can use the loop-back interface to uniquely identify the router within OSPF and BGP if you set the router-id to the same as the loop-back address. The loop-back can also be used for the RP (Rendezvous Point) in PIM-SM. The loop-back address is also used for the sFlow Agent IP address. The Loopback address is used for source IP of RADIUS authentication. 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. No supported
Layer-3 Routing Unicast (IPv4)

IP Routing Static routing RIP v1 & v2 OSPF v2 BGP v4 *- with AOS 6.4.2 release Multicast IGMP v1, v2 & v3 snooping PIM-SM PIM-DM DVMRP Network Protocol TCP/IP stack ARP DHCP relay Generic UDP relay per VLAN Resilience VRRPv2 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: 96K Maximum number of IPv6 routes that can be held in the software routing table: 5K 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.
Layer-3 Routing (IPX)
Residential Metro Triple-play Ethernet Access Large L3 table support
Routing Information Base (RIB) & Forwarding Information Base (FIB)
Page 58
Maximum number of IP route entries (Layer-3 Routing Table Size) (Maximum Routing Information Base RIB) Max number of IP Router interfaces per system Single mode Max number of IP routes Max number of IP static routes RIPv1&v2
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 12K IPv4 entries or 6K IPv6 entries. Since the table is shared and IPv6 entries take up twice the room of an IPv4 entry you can have combination like 10K IPv4 and 1K IPv6. Up to 48K routing table is supported. 12K forwarding LPM entries, 8K hosts entries per module. 1 K (1,024) Up to 48K 1 K (1,024) routes Maximum number of IP Routes: 48K Maximum number of RIPv2 interfaces per router: 10 Maximum number of RIPv2 peers per router, one per interface: 10 Maximum number of RIPv2 routes with no redistribution from OSPFv2 RIB on a OS6855 router: 6.5K (6.575K truncated to 6.5K)
Page 59
OSPFv2 Specifications
ECMP
BGP Routing Limitations * in AOS release 6.4.2
ARP Table: Max number of ARP entries per system Layer-3 forwarding, known IP@64 bytes pkt Layer-3 forwarding, known IP@1518 bytes pkt Layer-3 forwarding, known IP@ Jumbo pkt Trunking 2 VLANs, 64 Bytes pkt Trunking 2 VLANs, 1518 Bytes pkt RIP Learning Rate OSPF Learning Rate
The following values are the maximum limits enforced by the code. Maximum number of Areas (per router): 32 Maximum number of Interfaces (per area): 100 Maximum number of Interfaces (per router): 32 x 100 (Limited only by max. num of IPv4 interfaces = 4096) Maximum number of Link State Database entries (per router): 96K Maximum number of neighbors/adjacencies (per router): 254 Maximum number of neighbors/adjacencies (per area): 128 Maximum number of routes (per router): 96K Maximum number of OSPFv2- ECMP gateways (per destination): 4 Max number of OSPFv2 Sessions: 1 The following values are the tested limits with functionally verified (stress test). On OS6855 ABR routers: Max number of IP Routes on OS6855 router: 12K Max number of OSPFv2 Routes on OS6855 router: 12K Max number of OSPFv2 Interfaces on OS6855 ABR: 48 Max number of OSPFv2 Areas on OS6855 ABR: 6 Max number of OSPFv2 Adjacencies on OS6855 ABR: 48 Max number of LSAs on OS6855 ABR: 12K Tested number of OSPFv2- ECMP gateways (per destination): 4 Max number of OSPFv2 Sessions: 1 On OS6855 non-ABR routers: Max number of IP Routes on OS6855 router: 96K Max number of OSPFv2 Routes on OS6855 router: 96K Max number of OSPFv2 Interfaces on OS6855 non-ABR: 27 Max number of OSPFv2 Areas on OS6855 non-ABR: 6 Max number of OSPFv2 Adjacencies on OS6855 non-ABR: 27 Max number of LSAs on OS6855 non-ABR: 24K Tested number of OSPFv2- ECMP gateways (per destination): 4 Max number of OSPFv2 Sessions: 1 Notes: Please note that, the above OSPFv2 specifications may vary depending on the available system resources, and/or customer specific networking requirements & configurations. Please also note that, depending on the number of Areas, Interfaces, Adjacencies, and Neighbors configured, the maximum number of routes may vary. Please contact our customer Service & Support team, should your required specifications fall between "the limits as enforced by the code" and "the limits as functionally tested". Only 512 networks can be programmed in the ECMP table, so that the flows can be load balanced among the different paths. When having more than 512 ECMP routes on the show ip route, only the last (highest) 512 routes are programmed in the ECMP table. Only 512 networks can be load balanced over ECMP links The other ECMP networks will always be routed on the same link. Maximum BGP Peers per Router: 8 Maximum number of routes supported: 30,000 Range for AS Numbers 1 to 65535 Range of Local Preference Values 0 to 4294967295 Range for Confederation IDs 0 to 65535 Range for MED Attribute 0 to 4294967295 Up to 8K (8,192) L3 ARP entries are supported. Wire-speed Wire-speed Wire-speed Wire-speed Wire-speed 500 / sec 500 / sec
Page 60
Route Convergence for OSPF IP redistribution
Unicast Routing Protocol Performance
1.2 sec Supported platform: OS6800, OS6855, and OS9000 IPv4 Redistribution instances use route-maps to redistribute routes from a source protocol RIB to a destination protocol RIB. The source protocol can be BGP, RIP, OSPF, Local or Static. The destination protocol can be BGP, RIP or OSPF. Maximum number of route-maps that can be created on router: 200 Maximum number of route-map sequences that can be created on router: 400 Maximum number of IPv4 access-lists that can be configured on router: 200 Maximum number of OSPFv2 routes that can be redistributed into RIPv2: 6.5K Maximum number of RIPv2 routes that can be redistributed into OSPFv2: 6.5K Below table is high light of routing limitation in 6.1.3.R01 release for OS6850 and OS9000. OS6855 has the same performance as OS6850. OS6850 OSPFv2 ABR LSA#/Routes# OSPFV2 non-ABR LSA#/Routes# RIPv2 IPv4 Redistribution RIPv2 into OSPFv2 IPv4 Redistribution OSPFv2 into RIPv2 OSPFv3 ABR LSA#/Routes# OSPFv3 non-ABR LSA#/Routes# RIPng IPv6 Redistribution RIPng into OSPFv3 IPv6 Redistribution OSPFv3 into RIPng OS9000
12K/12K 24K/96K 6.5K
32K/32K 24K/96K (4 ECMP) 8.5K
6.5K
8K
6.5K 1.25K/1.25K 1.25K/1.25K 6.5K
8.5K 1.25K/1.25K 1.25K/5K (4 ECMP) 8.5K
1K
1K
1K
1K
Multicast & Network Protocols & Resilience

Multicast Performance Q: Does this device support IPv4 hardware-based Multicast Routing? A: Hardware-based native IPv4 & IPv6 Unicast & Multicast Routing is supported. The Alcatel OmniSwitch 9000s are designed to anticipate future network needs with wire-rate processing for IPv4/IPv6 and support for unicast and multicast applications such as voice-over-IP and video collaboration. The switches support edge requirements as Gigabit Ethernet to the desktop becomes commonplace and demand for power-over-Ethernet (PoE) capability increases. Q: How many IPv4 Multicast Routes are supported? A: We support as many IPv4 Multicast Routes as memory will allow. The more limiting factors are that we support 1,021IP Multicast flows (where a flow is classified as source-group pair). Q: How many IPv4 multicast packets does this device route per second at 64-bytes? A: Wire rate. Q: How many IPv4 multicast packets does this device route per second at 1518-bytes? A: Wire rate. Q: Does this device support IPv6 hardware-based Multicast Routing? A: Hardware-based native IPv4 & IPv6 Unicast & Multicast Routing is supported. The Alcatel OmniSwitch 6850/9000s is designed to anticipate future network needs with wire-rate
Page 61
Multicast Flows A flow is defined as a source-group pair.
Multicast support
Flow Table VLAN Replication Max number of DVMRP Interfaces Max number of DVMRP Neighbors Max number of DVMRP Tunnels Max number of PIM-SM Interfaces PIM-DM (IPv4)
processing for IPv4/IPv6 and support for unicast and multicast applications such as voice-over-IP and video collaboration. The switches support edge requirements as Gigabit Ethernet to the desktop becomes commonplace and demand for power-over-Ethernet (PoE) capability increases. Note: The OmniSwitch 6850/9000 supports IPv6 hardware-based Multicast Switching (forwarding between ports on the same VLAN) and IPv6 hardware-based Multicast Routing. Q: How many IPv6 Multicast Routes are supported? A: We support as many IPv6 Multicast Routes as memory will allow. The more limiting factors are that we support 1,021 IP Multicast flows (where a flow is classified by a source-group pair). Q: How many IPv6 multicast packets does this device route per second at 64-bytes? A: Wire rate. Q: How many IPv6 multicast packets does this device route per second at 1518-bytes? A: Wire rate. Maximum Multicast Flows per switch: 1,021 (with hardware routing) Up to 1,021 simultaneous multicast flows are supported. There is no hard limit on the number of static multicast groups that can be configured, but if you try to send traffic to the entire group at the same time the limit is still 1,021 hardware flows. A flow is defined as a source-group pair. In the case all hardware entries are exhausted, the IPMS will not perform software forwarding. IP multicast tunneling is performed in software. IGMPv1&v2&v3 Snooping MLD Snooping DVMRP PIM-SM PIM-DM 1021 entries per system 2048 entries per system 128 256 1 per interface 128 PIM-DM is a multicast routing protocol that defines a multicast routing algorithm for multicast groups that are densely distributed across a network. It uses the underlying unicast routing information base to flood multicast datagrams to all multicast routers. Prune messages are used to prevent future messages from propagating to routers with no group membership information. It employs the same packet formats as sparse mode PIM (PIM-SM). PIM-DM assumes that when a multicast source starts sending, all downstream systems want to receive multicast datagrams. Initially, multicast datagrams are flooded to all areas of the network. PIM-DM uses RPF (Reverse Path Forwarding) to prevent looping of multicast datagrams while flooding. If some areas of the network do not have group members, PIM-DM will prune off the forwarding branch by instantiating prune state. PIM-DM differs from PIM-SM in two essential ways: 1. There are no periodic joins transmitted, only explicitly triggered prunes and grafts. 2. There is no Rendezvous Point (RP). This is particularly important in networks that cannot tolerate a single point of failure.
Page 62
IGMP learning performance
Zapping
L2 static multicast Multicast without 8021.Q on 10/100Mbps interfaces Multicast without 8021.Q on 1000Mbps interfaces Multicast with 8021.Q, 0 copies, 1518Bytes pkt on 10/100/1000Mbps ports and/or GigE ports Multicast with 8021.Q, 1 copies, 1518Bytes pkt on 10/100/1000Mbps ports and/or GigE ports Multicast with 8021.Q, 2 copies, 1518Bytes pkt on 10/100/1000Mbps ports and/or GigE ports Network Protocols
The system can process 1000 IGMP per second. However, the performance can drop to 128 when IGMP are received too fast. Burst of 1000 IGMP reports at 1000 packet/sec: all 1000 groups are learnt Burst of 1000 IGMP reports at 1Gbps: only 128 groups are learnt You can configure ip multicast zapping to optimize channel surfing. That will instantly stop forwarding multicast to a client when that client sent an IGMP Leave. The zapping time can be measured by the leave message received by the switch and the last packet received by the client. This is usually in milliseconds. The feature is well suited for Multicast Switching and zapping only works well when ip multicast querying is disabled. 1022 static multicast MACs are supported on OS6855 and OS9000. The L2 Multicast table can have 1024 entries but 2 are reserved for other applications. Wire-speed Wire-speed Wire-speed Wire-speed Wire-speed DHCP Relay (including generic UDP Relay) TCP/IP Stack NDP ARP
Resilience
VRRPv3 Virtual Router Redundancy Protocol, VRRPv3, is designed to eliminate the single point of failure existing in a static default routed IPv6 environment. The loss of the default router isolates all systems not able to detect an alternate path. VRRPv3 provides the capability for assigning the responsibility of a virtual router to one of the IPv6 VRRPv3 routers on a LAN. A total of 255 VRRP3 instances can be configured if only IPv6 instances are configured. The total of 255 instances on a box is the maximum number of VRRP instances (VRRP2 + VRRP3) that can be configured on a box.. As an example if a user configures 200 VRRP2 instances, then only 55 VRRP3 instances can be configured. If a user configures 255 VRRP2 instances then no VRRP3 instances can be configured and vice versa.
Page 63
Layer-3 Routing Unicast (IPv6)

Layer-3 Routing Protocols (IPv6) IP Routing Static routing RIPng OSPF v3 Multicast MLD snooping PIM-SM PIM-DM Network protocol TCP/IP stack DHCP relay (including generic UDP relay) ARP Resilience VRRPv3 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: 96K Maximum number of IPv6 routes that can be held in the software routing table: 5K 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 12K IPv4 entries or 6K IPv6 entries. Since the table is shared and IPv6 entries take up twice the room of an IPv4 entry you can have combination like 10K IPv4 and 1K IPv6. Up to 16K routing table is supported. 6K forwarding LPM entries, 4K hosts entries per module. Latency: <10sec 1,000 The total number of IPv6 routes supported in hardware (with no IPv4 routes) is 6000 1,000 routes The recommended number of IPv6 interfaces is 100 The recommended number of IPv6 prefixes per interface is 50 The recommended number of IPv6 global unicast addresses per interface is 50 A 6to4 tunnel explicitly uses an ingress tunnel for each IPv4 interface configured on the system. The limit is 100 ingress tunnels The 10GIG routing performance over an IPv6 tunnel (6to4 and configured tunnel) has been determined to be 10,775,862 96 byte packets per second. The 10GIG routing performance NI-NI or Single NI has been determined to be 14,880,812 - 64 byte packets per second.
Large L3 table support
Routing Information Base (RIB) & Forwarding Information Base (FIB)
Maximum number of IP route entries (Layer-3 Routing Table Size) (Maximum Routing Information Base RIB) Max number of IP Router interfaces per system Single mode IPv6 routes Max number of IPv6 static routes IPv6 interfaces IPv6 prefixes per interface IPv6 global unicast addresses per interface A 6to4 tunnel
Page 64
RIPng
ARP Table: Max number of ARP entries per system OSPFv3 Specifications
IPv6 REDISTRIBUTION
Layer-3 forwarding, known IP@64 bytes pkt Layer-3 forwarding, known IP@1518 bytes pkt Layer-3 forwarding, known IP@ Jumbo pkt Trunking 2 VLANs, 64 Bytes pkt Trunking 2 VLANs, 1518 Bytes pkt RIP Learning Rate OSPF Learning Rate Route Convergence for OSPF
The following values are the maximum limits enforced by the code. The total number of RIPng interfaces is 100. The maximum number of RIPng neighbors is 20 Maximum number of RIPng routes: 5K routes (Depending on the number of RIPng interfaces, and neighbors configured the maximum number of routes may vary.) The following values are the tested limits functionally verified. The following configuration is used as a stress test: (a) Maximum number of RIPng interfaces per router: 10 (b) Maximum number of RIPng peers per OS6855 router: 10 (c) Maximum number of RIPng routes with no redistribution from OSPFv3 RIB: 1000 Up to 8K (8,192) L3 ARP entries are supported. The following values are the maximum limits enforced by the code. Maximum number of Areas (per router): 5 Maximum number of Interfaces (per router): 20 Maximum number of Link State Database entries (per router): 5K Maximum number of adjacencies (per router): 20 Maximum number of OSPF- ECMP gateways (per destination): 4 Maximum number of neighbors (per router): 16 Maximum number of routes (per router): Up to 50K (Depending on the number of Areas, Interfaces, Adjacencies, and Neighbors configured, the maximum number of routes may vary.) Max number of OSPF Sessions: 1 The following values are the tested limits functionally verified. The following configuration is used as a stress test: On an OS6855 non-ABR Routers: (a) Min. usable Hello Interval with 20 Interfaces in 5 Areas with 4 Interfaces in each Area: 5 sec (b) Min. usable Router Dead Interval with 20 Neighbors, 4 each in 1 Area for a total of 5 Areas: 20 sec (c) Max. usable number of LSAs that the OS6855 router can stably hold: 5K (d) Max. usable number of Ospfv3 Routes that the OS6855 router can stably hold in this scenario: 5K (e) Max. number of usable Ospfv3 Interfaces between any two OS6855 or OS6855/OS9000 routers: 4 (f) Max number of IP Routes on OS6855 router: 5K (g) Max number of OSPFv3 Routes on OS6855 router: 5K On an OS6855 ABR: (a) Min. usable Hello Interval with 20 Interfaces in 5 Areas with 4 Interfaces in each Area: 5 sec (b) Min. usable Router Dead Interval with 20 Neighbors, 4 each in 1 Area for a total of 5 Areas: 20 sec (c) Max. usable number of LSAs that the OS6855 router can stably hold: 5K (d) Max. usable number of Ospfv3 Routes that the OS6855 router can stably hold in this scenario: 5K (e) Max. number of usable Ospfv3 Interfaces in 5 areas with 5K LSAs: 20 (f) Max. number of usable Ospfv3 Neighbors in 5 areas with 5K LSAs: 20 (g) Max. number of usable Ospfv3 Interfaces between any two OS6855 routers: 4 (l) Max. number of usable Ospfv3 Areas on an OS6855 ABR: 5 Notes: Please note that, the above OSPFv3 specifications may vary depending on the available system resources, and/or customer specific networking requirements & configurations. Please also note that, depending on the number of Areas, Interfaces, Adjacencies, and Neighbors configured, the maximum number of routes may vary. Please contact our customer Service & Support team, should your required specifications fall between "the limits as enforced by the code" and "the limits as functionally tested". (a) Maximum number of route-maps that can be created on an OS6855 router: 200 (b) Maximum number of route-map sequences that can be created on an OS6855 router: 400 (c) Maximum number of IPv6 access-lists that can be configured on an OS6855 router: 200 (d) Maximum number of OSPFv3 routes that can be redistributed into RIPng: 1K (e) Maximum number of RIPng routes that can be redistributed into OSPFv3: 1K Wire-speed Wire-speed Wire-speed Wire-speed Wire-speed 500 / sec 500 / sec 1.2 sec
Page 65
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. 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 VRRP 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) With VRRP and Multinetting, you can still configure multiple instances to load balance the master role among the sub-netted interfaces. Routing protocols (RIP, OSPF, BGP) are supported in a multinetted environment. The routing interfaces are now based on ip interfaces, instead of the VLANs. Therefore, routing protocols are totally independent of VLANs and their data structures are maintained as part of an array indexed by ip interface only. There is no difference between running a routing protocol on an interface part of a multinetted vlan or a regular interface. Each subnet (interface) on the multinetted vlan can run its own routing protocol. The multicast routing protocols will be supported on one interface per VLAN. One interface designated the primary interface, will be used for the multicast routing protocols. The multicast routing protocols will not allow configuration on any non-primary interfaces. By default the first interface is the primary interface. DVMRP and PIM-SM will only allow configuration on the primary interface of a VLAN. This is to ensure consistency between the multicast routing protocols (DVMRP, PIM-SM, IPMRM), IPMS and IGMP.
Supported features:
Routing In Multinetting
Multicast Routing In Multinetting
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.
Page 66
Policy/QoS
QoS / ACLs 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 (rip, ospf, bgp) DropServices to drop tcp/udp ports IGMP ACLs L2/L3/L4 QoS fully supports IP multicast traffic (priority, bandwidth shaping..) 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 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 IP multicast condition: An ip multicast condition is used for IGMP ACLs. The multicast ip is actually the multicast group address used in the IGMP report packet. IP multicast can be combined with destination port, destination vlan, destination Mac, destination ip, that are the port/vlan/mac/ip of the device that sent the IGMP report 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.
Convergence / Triple Play
QoS Conditions & Actions supported
Priority Queues Traffic Prioritization Bandwidth Management Queue Management
Page 67
Queuing Scheme and Servicing Mode
Queue Mapping Table
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 Configurable policies
OS6855 has 8 queues per egress port OS6855 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 128 per port; 2048 policy rules per chassis OS6855: 2048 rules per slice 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 OS6855-24 Models port unit (1 TCAM) Max available HW rules per slot: 1664 Max available tcp/udp port ranges per slot: 16 Max available bandwidth shaping rules per slot: 832 OS6855 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.
Servicin SPQ or W SPQ or W SPQ or W SPQ or W SPQ or W SPQ or W SPQ or W SPQ or W
Rule logging
Page 68
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.
Page 69
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.
Page 70
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) Multicast ipv6 for MLD report filtering (similar to IGMP filtering) 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/ospf/bgp 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 This feature is supported on OS6855/9000 in 6.1.3.R01. 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.
Page 71
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 OS6855-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 VRRP (Virtual Router Redundancy Protocol), and OSPF ECMP (Equal Cost Multipath Protocol) 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 Network and Link Resiliency: Network and link resiliency are important parts of network availability, and the AOS OmniSwitch product family supports advanced routing, load sharing, and mechanisms for fast reconfiguration of links between switches, servers, and other network devices. These include: o VRRP (Virtual Router Redundancy Protocol), and OSPF Equal Cost Multipath Protocol 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
Page 72
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 before 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, OSPFv2 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
Page 73
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): IP multicast packet on range 224.0.0.0-224.0.0.255: that includes routing protocol packets such as OSPF, RIPv2 and VRRP packets 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 OSPF, RIPv2 VRRP 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. Supported platform: OS6800, OS6855, and OS9000 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 Supported platform: OS6800, OS6855, and OS9000 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:
Page 74
ACLMAN
DHCP Snooping Traffic Filtering User Authentication
Switch protocol security Switch management User-port shutdown profile
Port Disable
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. 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 These are the limitations for the 6.1.2.R03 release. - Only supported on the OS6855 Series - No stacking support - ACLMAN is restricted by the same number of rule limitations that QoS supports - ACL names are limited to 16 characters 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, OSPFv2 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/ospf/bgp 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
Page 75
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.
Page 76
Management
Simplified Manageability The following is only a highlight of the advanced network and switch management features supported by the OmniSwitch 6855 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 (The maximum number of mirroring sessions is limited to one on OmniSwitch 6800, whereas two mirroring sessions are allowed on OmniSwitch 9000 and OmniSwitch 6855). 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 Local (on the flash) and remote logging (Syslog) 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 Secured file upload using SFTP, or SCP 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 Secured file upload using SFTP, or SCP 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 GVRP for 802.1Q-compliant VLAN pruning and dynamic VLAN creation Command Line Interface (CLI), Telnet/SSH for remote CLI access, Web-based (HTTP/HTTPS) and SNMPv1/v2c/v3 for complete NMS integration
Configuration Mode
Page 77
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
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 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 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. 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
SNMP Traps Port Monitoring
Port Mirroring
Page 78
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) /10 Gigabit Ethernet (10 Gb/10000 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 OS6800/OS6855 does not have any SCP-daemon running on the switch, therefore this feature only works when OS6800/OS6855 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 OS6855, 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 does 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/OSPF/BGP/PIM-SM/DM (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.
Page 79
SFLOW Back-off Algorithm
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 OS6855 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 OS6855 will back-off to 2147483647 and stay at this (maximum, safe) sampling rate. Recommended sampling rates for various speeds at various load: Sampling Rates Medium Heavy Light Load Load Load 256 512 1024 512 1024 2048 8192* 65536* Max*
Link Speed 10Mb/s 100Mb/s 1Gb/s
TACACS+
10Gb/s 2048 4096 Max* *8192 is the empirical value found in the lab for 10Mbs, 65536 for 100 Mbps *Max: because the OS6855 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. Supported platform: OS6800, OS6855, and OS9000 Release 6.1.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.
Page 80
Source Learning
Source 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. OS6855 supports both hardware and software source learning modes. 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.
Hardware Learning
Source Learning Specifications

Source Learning RFCs supported Source Learning IEEE Standards supported MAC Address Table entries 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
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
Page 81
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.
Page 82
Software
Third Party Licenses and Notices 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 and 10Gigabit Ethernet ports on OmniSwitch 6855 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.
Capability Maturity Model (CMM) The Ethernet software
OmniSwitch 6855 Series IETF / IEEE Standards

The OmniSwitch 6855 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.1agConnectivity Fault Management IEEE 802.3ahCSMA/CD Access Method and Physical Layer Specifications (Future Release) 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 MAC Reduction 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. Protocol VLANs 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)
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.1t (MAC Reduction) IEEE 802.1x Extended 802.1x IEEE 802.1x MIB Port Access IEEE 802.1v IEEE 802.1w IEEE 802.3 IEEE 802.3i IEEE 802.3ab IEEE 802.3ac IEEE 802.3ad
Page 83
IEEE 802.3ae IEEE 802.3af IEEE 802.3ak IEEE 802.3x
IEEE 802.3u IEEE 802.3z
10-Gigabit Ethernet Power over Ethernet (PoE) 10Gbps XFP 10GBASE-CX4 type cables are compliant with IEEE 802.3ak Ethernet flow control IEEE 802.3x (programmable threshold) flow control: Release 6.3.1r01 does not currently support IEEE 802.3x 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.
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 1075 RFC 1112 RFC 1122 RFC 1142 RFC 1151 RFC 1155 / 2578-2580 RFC 1156 RFC 1157 / 2271 RFC 1191 RFC 1195 RFC 1212 / 2737 RFC 1213 / 2011-2013 RFC 1215 RFC 1253 / 1850 / 2328 RFC 1256 RFC 1269 / 1657 RFC 1305 / 2030 RFC 1321 RFC 1349 RFC 1370 RFC 1403 / 1745 RFC 1493 RFC 1518 / 1519 RFC 1519 RFC 1534 RFC 1541 / 1542 / 2131 / 3396 / 3442 RFC 1542 RFC 1573 / RFC 2233 / RFC 2863 RFC 1587 / 3101 RFC 1643 / RFC 2665 RFC 1657 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 DVMRPv2 IGMPv1 Internet Hosts OSI IS-IS Intra-domain Routing Protocol RDP SMIv1 & SMIv2 TCP / IP & MIB SNMPv1 Path MTU Discovery Use of OSI IS-IS for routing in TCP/IP & dual environments MIB & MIB-II SNMPv2 MIB Convention for SNMP Traps OSPFv2 & MIB ICMP Router Discovery Messages BGPv3&v4 MIB NTPv3 & Simple NTP MD5 IP & IP / Ethernet Applicability Statement for OSPF BGP / OSPF Interaction Bridge MIB CIDR CIDR Interoperation Between DHCP and BOOTP Dynamic Host Configuration Protocol (DHCP) Clarifications and Extensions for the Bootstrap Protocol Private Interface MIB OSPF NSSA Option Ethernet MIB BGPv3&v4 MIB
Page 84
RFC 1701 & 1702 RFC 1722 / 1723 / 2453 / 1724 RFC 1724 (which obsoletes RFC 1389) RFC 1745 RFC 1757 (formerly 1271) / 2819 RFC 1765 RFC 1771-1774 / 2842 / 2918 / 3392 RFC 1789 RFC 1798 RFC 1812 / 2644 RFC 1850 RFC 1886 RFC 1901, 1902, 1903, 1904, 1905, 1906, 1907 RFC 1908 RFC 1965 RFC 1966 RFC 1997/1998 RFC 2003 RFC 2011 RFC 2012 RFC 2013 RFC 2030 RFC 2042 RFC 2080 RFC 2096 RFC 2104 RFC 2131 / 3046 RFC 2132 RFC 2138 / 2865 / 2868 / 3575 / 2618 RFC 2139 / 2866 / 2867 / 2620
1701Generic Routing Encapsulation (GRE) 1702Generic Routing Encapsulation over IPV4 Networks RIPv2 Protocol Applicability Statement & MIB RIPv2 MIB Extension BGP / OSPF Interaction RMON & MIB OSPF Database Overflow is not currently supported. BGPv4 Connectionless Lightweight X.5000 Directory Access Protocol IPv4 Router Requirements OSPF Version 2 MIB DNS for IPv6 -SNMPv2c Management Framework -Coexistence and transitions relating to SNMPv1 and SNMPv2c BGP AS Confederations BGP Route Reflection BGP Communities Attributes -IP Encapsulation within IP. SNMPv2 MIB SNMPv2 MIB SNMPv2 MIB NTPv3 & Simple NTP BGP New Attribute 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. OSPF MD5 Signature SFTP Private Interface MIB IGMPv2 (Snooping for layer-2 multicast switching) & MIB Using Domains in LDAP/X.500 Distinguished Names Lightweight Directory Access Protocol (v3) Lightweight Directory Access Protocol (v3): Attribute Syntax Definitions Lightweight Directory Access Protocol (v3): UTF-8 String Representation of Distinguished Names The String Representation of LDAP Search Filters A Summary of the X.500 (96) User Schema for Use with LDAPv3 SNMPv1 PPP Extensible Authentication Protocol (EAP) IPv6 OSPFv2 Virtual Router Redundancy Protocol (VRRP) & MIB PIM-SM Protocol Specifications Administratively Scoped IP Multicast The OSPF Opaque LSA Option BGP MD5 Signature BGP Route Flap Damping 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.
RFC 2154 RFC 2228 RFC 2233 RFC 2236 / 2933 RFC 2247 RFC 2251 RFC 2252 RFC 2253 RFC 2254 RFC 2255 RFC 2256 RFC 2271 RFC 2284 RFC 2292 / 2373 / 2374 / 2460 / 2462 RFC 2328 (which obsoletes RFC1583 and RFC2178) RFC 2338 / 3768 / 2787 RFC 2362 RFC 2365 RFC 2370 / 3630 RFC 2385 RFC 2439 RFC 2452 / RFC 2454 RFC 2453 RFC 2461 RFC 2463 / 2466 RFC 2464 / 2553 / 2893 / 3493 / 3513
Page 85
RFC 2474 / 2475 / 2597 / 3168 / 3246 RFC 2475 RFC 2548 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 RFC 2715 / 2932 RFC 2727 RFC 2737 RFC 2740 RFC 2763 RFC 2784 RFC 2787 RFC 2796 RFC 2809 RFC 2819 RFC 2842 RFC 2863 RFC 2865 RFC 2866 RFC 2867 RFC 2868 RFC 2869/2869bits RFC 2882 RFC 2890 RFC 2893
DiffServ DiffServ Microsoft Vendor-specific RADIUS Attributes 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 RADIUS Authentication & Client MIB Note: We support this RFC 2618 through our own Proprietary Private MIB. Although, the mapping between the RFC 2618 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. RADIUS Accounting & Client MIB Note: 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. 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 Extensions / VLAN MIB Multicast Routing MIB MIB & MIB-II OSPFv3 for IPv6 Dynamic Hostname Exchange for IS-IS Generic Routing Encapsulation (GRE) Definitions of Managed Objects for the Virtual Router Redundancy Protocol BGP Route Reflection Implementation of L2TP Compulsory Tunneling via RADIUS Remote Network Monitoring Management Information Base BGPv4 Private Interface MIB 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 Key and Sequence Number Extensions to GRE (extensions defined are not supported) 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. BGPv4 Accounting Attributes and Record Formats IPv4 Multicast Routing MIB IGMP MIB PIM MIB for IPv4 Introduction to Accounting Management Criteria for Evaluating AAA Protocols for Network Access Dynamic Host Configuration Control (relay) DHCP / BootP Relay IPv6 Tunneling Policy Core BGP AS Confederations
RFC 2918 RFC 2924 RFC 2932 RFC 2933 RFC 2934 RFC 2975 RFC 2989 RFC 3046 RFC 3056 RFC 3060 RFC 3065
Page 86
RFC 3101 RFC 3168 RFC 3176 RFC 3246 RFC 3289 RFC 3376 (IGMPv3) RFC 3392 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 3569 RFC 3575 RFC 3623 RFC 3635 RFC 3636 RFC 3768 (which obsoletes RFC2338) RFC 4443/ 4293 RFC 4541
The OSPF Not-So-Stubby Area (NSSA) Option DiffServ RFC 3176 is for sFlow support DiffServ The RFC 3289 (DiffServ-MIB) IS NOT SUPPORTED. Snooping for layer-2 multicast switching BGPv4 Dynamic Host Configuration Protocol (DHCP) SNMPv3 SNMPv3 SNMPv3 SNMPv3 SNMPv3 SNMPv2c Dynamic Host Configuration Protocol (DHCP) IPv6 An Overview of Source-Specific Multicast (SSM) RADIUS Authentication & Client MIB Graceful OSPF Restart Pause Control IEEE 802.3 MAU MIB Virtual Router Redundancy Protocol (VRRP) & MIB ICMPv6 & MIB RFC 4541 Considerations for Internet Group Management Protocol (IGMP) and Multicast Listener Discovery (MLD) Snooping Switches
Service & Support, Integration & Installation
Escalation
Key Partners
Customer support / Professional Services
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. 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,
Page 87
Customer Training
Warranty Service & Support Programs & End Of Life Lifetime Support
Hardware Warranty
Software Warranty
Life Span
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. Limited Lifetime Warranty does not apply to SFPs. 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.
Page 88
Appedix A - Small Form Factor Pluggable (SFP MSA)

OmniSwitch 6855 Series switches use both copper-based and fiber-based optical Small Form Factor Pluggable (SFP) transceivers. SFPs are fully hot-swappable and are available for both short-reach and long-reach applications. Copper-based and fiber-based optical SFPs can be mixed on the same module.
Note: The information discussed in this section is not exhaustive and the original manufacturers fiber optics references must be consulted to obtain further information for proper design guidelines.
The maximum distance supported with fiber optics transceivers will be influenced by the following factors: o Specified fiber plants standards for cable wiring such as ISO/IEC-11801, TIA 568, IEEE 802.3u, o IEEE 802.3z/1000BASE-SX/LX/LHetc. o Modal Bandwidth (measured in MHZ*km: such as 200 MHZ*km, or 160 MHZ*kmetc) o Fiber quality o Attenuation or dB of loss per km (Attenuation is a measure of the loss of signal strength or light power that occurs as light pulses propagate through a run of multimode or single-mode fiber. Measurements are typically defined in terms of decibels or dB/km.). This loss could result from patch panels, splicing, optical connectors, optical jointsetc. o The Optical Power Budget (OPB) in dB allowance o The Optical Power Budget (in dB) provides the necessary optical signal range to establish a working fiber-optic link. The OPB is allocated for the fiber-optic cable. The OPB is the available optical power for a fiber optic link to accommodate fiber cable losses plus losses due to in-line connectors, splices, optical switches, and to provide margin for link aging and unplanned losses due to cable plant reconfiguration or repair. o The worst-case Optical Power Budget in dB for a fiber optic link is determined by: The difference between the minimum transmitters output optical power and the lowest receiver sensitivity. o The best way to determine the distance being supported is to take an OTDR (Optical Time Domain Reflecto-meter) measurement on the fiber cable plant. (These measurements must be made using the same wavelength of light as the transceiver that will be installed.) This will indicate the amount of loss per intended distance. If the loss is within the transceivers allowed power budget, the connection will work. Minimum distance requirements must be carefully considered. Alcatel-Lucent supports several alternate sources of fiber optics transceiver manufacturers for its switching and routing line of products. Alcatel-Lucent strongly recommends compliance with the original manufactures fiber optics specifications, and fiber optics design guidelines. Therefore, as a general rule, Alcatel-Lucent stays within the boundaries of the original manufacturers specifications. Any deviations from the norm require further evaluations and testing. The insertion loss parameter value for the MiniGBICs requires a very specific testing which is normally performed by the original manufacturer, but usually is not stated in their specification documents and the value may vary from one manufacturer to another. Here at Alcatel-Lucent, our engineering normally does not carry out such testing and therefore we rely on our approved manufacturer specifications data. Essentially, the original manufacturer upon request must supply this specific parameter value. It is not anywhere in their specification sheets. Here is what our Engineering suggests to do: Instead of relying on the manufacture's data for the insertion loss value, which also varies from one manufacturer to another, we suggest looking into the IEEE Standard Document. No matter what, all manufacturers must comply with the IEEE Standard. All of our MiniGBICs comply with the IEEE 802.3z. You can easily look up the insertion loss parameter and its value for our MiniGBICs in this document.
Handling Fiber and Fiber Optic Connectors

Using fiber is extremely simple, but several important standards should always be practiced. For best results, you should: Use premium grade jumper cables with duplex LC connectors Keep your fiber optic connectors clean Keep the transceiver interface clean OS6855 Series Boilerplate Doc. Rev.2.1a / Nov. 09 Page 89 Alcatel.Lucent-ESD Calabasas/CA./USA
Attenuate properly Use Premium Grade Jumper Cables with Duplex LC Connectors There are many brands of fiber optic jumper cables, with a wide range of quality between each manufacturer. Premium cables do three things well: They provide a good polish on the fiber optic connector end-face (where the light exits the cable). End-face geometries must be exceptionally precise and aligned to extremely tight tolerances. The better the endface geometry, the lower the loss and more consistent the connection. Poor connector interfaces will reflect light back into the laser, causing an increase in laser noise. They mate well with other connector interfaces. Chances are the manufacturer of the jumper cable will not be the same as the manufacturer of the transceiver connector interface. Premium jumper cables mechanically align themselves well into most transceiver interfaces. This provides both better performance as well as better repeatability. You will always see a variance in transceiver power due to connector alignment, often as much as 0.3 to 0.7 dB. Good jumper cables help reduce this variance. They continue to mate well after many insertions and removals. Premium grade jumper use premium connectors that maintain their mechanical integrity up to and beyond 2000 insertion cycles For better repeatability, always use duplex (two connectors fused together and terminated to two cables) LC connectors on your jumper cables when connecting to a fiber-optic transceiver. Two simplex connectors inserted into a transceiver interface will often have up to 3 dB greater variations in repeatability compared to duplex connectors. Never bend the fiber optic cable beyond its recommended minimum bend radius. This introduces bend losses and reflections that will degrade the performance of your system. It can also damage the fiber, although fiber is much tougher than most would assume. Still, it is highly recommended to buy only jumper cables with 3mm Kevlar jacketing, which offer superior protection and longer life. Keep Your Fiber Optic Connectors Clean Unlike electrical connectors, fiber-optic connectors must be extremely clean in order to ensure optimum system performance. Microscopic particles such as dust on the connector end-face (i.e., where the light exits the connector) can degrade the performance of your system, often to the point of failure. If you have low-power output from a fiber-optic transceiver or a fault signal from your equipment, begin the troubleshooting process by cleaning your fiber-optic connectors per manufacturer recommendations. Keep the Transceiver Interface Clean If you have cleaned your connectors, but still experience low-power output from a fiber-optic transceiver or a fault signal from your equipment, you should clean the transceiver interface by blowing inert dusting gas inside the transceiver interface. This removes dust and other small particles that may block the optical path between the optics of the transceiver and the connectors end-face. Attenuate Properly Often, equipment using laser-based transceivers need to have the optical path attenuated when performing loop-back testing or testing between two pieces of equipment. Too much optical power launched into the receiver will cause saturation and result in system failure. If you are using single mode fiber and you do not know the power output of the laser, it is always best to use a 10 dB attenuator when testing. Using the wrong type of attenuator will introduce problems, most notably reflection of light back into the laser, often resulting in excess noise and causing system failure. Inline attenuators eliminate the need for additional jumper cables and thus reduce the number of connection interfaces. This increases the integrity of the optical path resulting in a more accurate test.
SFP MSA Specifications SFP-MSA Connector: The SFP connector consists of a 20-pin receptacle and a SFP housing cage. The 20-pin connector provides the interface for the hot Pluggable SFP module. Each SFP module contains a serial interface to provide identification information that describes the SFP capabilities, standard interfaces, manufacturer and other information. LC Connector: The LC connector is a fiber-optic cable connector that uses one-half the size of current industry standards. It increases panel density and provides duplex connection in 50% less space with duplex fits of RJ-45 footprint. It is available in SM, MM versions with Super, Ultra and Angle (APC) polishing. It provides a user-friendly audible latch to indicate proper mating and supports pull proof.
Notes:
Page 90
*The worst-case Optical Power Budget in dB for a fiber optic link is determined by: The difference between the minimum transmitters output optical power and the lowest receiver sensitivity. Alcatel-Lucent switching & routing platforms support alternate sources of fiber-optics vendors, which are subject to change from time to time. Please be sure to contact Alcatel-Lucent Internetworking Product Marketing for a complete list of approved vendors. The following fiber optics transceivers specifications have been taken from Alcatel-Lucent IP Networking approved vendors original Specification Sheets.
Appendix B - Pin-Outs
RJ-45 Console Port Connector Pinouts
Pin Number 1 2 3 4 5 6 7 8 Shell Description (Signals as DCE Console Port) CTS NC RXD Ground Ground TXD NC RTS (Request to Send) Chassis Ground
RJ-45 Console Port Connector Pinouts

Pin Number 1 2 3 4 5 6 7&8 Shell Description (Signals as DTE Console Port) NC NC RXD Ground Ground TXD NC Chassis Ground
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
Power over Ethernet Port RJ-45 Pinouts (with PoE)

Pin Number 1 2 3 4&5 6 7&8 Description RX+ (-VDC) RX- (-VDC) TX+ (+VDC) ----TX- (+VDC) -----
Page 91
1 Gigabit Ethernet Port RJ-45 Pinouts (Non-PoE)

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
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
Page 92
OS6855 DB-25 Ppower Connection PIN-OUT

PIN 13
PIN 14
Pin Number Description OS6855 PoE Models 1 -50V 2 -50V 3 -50VRTN 4 -50VRTN 5 N/C 6 +12V 7 +12V 8 +12V 9 GND 10 GND 11 PS_ALTER 12 PS_GOOD 13 PS_PRESENT 14 -50V 15 -50V 16 -50VRTN 17 -50VRTN 18 N/C 19 +12V 20 +12V 21 GND 22 GND 23 GND 24 PS_TYPE0 25 PS_TYPE1
PIN 25
Pin Number Description OS6855 Non-PoE Models 1 N/C 2 N/C 3 N/C 4 N/C 5 N/C 6 +12V 7 +12V 8 +12V 9 GND 10 GND 11 PS_ALTER 12 PS_GOOD 13 PS_PRESENT 14 N/C 15 N/C 16 N/C 17 N/C 18 N/C 19 +12V 20 +12V 21 GND 22 GND 23 GND 24 PS_TYPE0 25 PS_TYPE1
Note: This the pin-outs for the external power supplies DB-25 connectors as located on the rear panel of OmniSwitch 6855 24 port platforms (as applicable). There are three DB-25 connectors. These connectors are used for connecting the appropriate power supply (s) to the OmniSwitch 6855 unit.
Appendix C - 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
Page 93
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.
Page 94
5. MTBF CALCULATION REQUIREMENTS 5.1 Bill of Materials The Bill of Materials (BOMs) is normally used to calculate the MTBFs of all the ESD 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.
Page 95
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
Page 96
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.
Page 97
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 OS6855 Series Boilerplate Doc. Rev.2.1a / Nov. 09 Page 98 Alcatel.Lucent-ESD Calabasas/CA./USA
Page 99

ALU Enterprise OmniSwitch6855 Boilerplate Rev 2.1a

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

ALU Enterprise OmniSwitch6855 Boilerplate Rev 2.1a

Hochgeladen von

Copyright:

Verfügbare Formate

ALCATEL-LUCENT Enterprise Solutions Div.

Ethernet & IP Networking Portfolio

OmniSwitch 6855 Hardened LAN Switch Boilerplate Document

The OmniSwitch 6855 Product Overview ______________________________________________ 7

Appendix B - Pin-Outs ________________________________________________________________ 91

Appendix C - MTBF Calculation Standards and Requirements ______________________________ 93

OS6855 Series Boilerplate Doc. Rev.2.1a / Nov. 09

OS6855 Series Boilerplate Doc. Rev.2.1a / Nov. 09

Alcatel-Lucent Company Background

About Alcatel-Lucent Enterprise Networking Solutions

OS6855 Series Boilerplate Doc. Rev.2.1a / Nov. 09

OmniSwitch 6855 Introduction

OS6855 Series Boilerplate Doc. Rev.2.1a / Nov. 09

The OmniSwitch 6855 Product Overview

OmniSwitch 6855 Series

OS6855 Series Boilerplate Doc. Rev.2.1a / Nov. 09

OS6855-PSS OS6855-PSS-P OS6855-PSS-D OS6855-PSS-P-D OS6855-PSL OS6855-PSL-P OS6855-PSL-D OS6855-PSL-DL

OS6855-24-FLTR OS6855-U24-FLTR OS6855-PSS-SHLF

OS6855 Series Boilerplate Doc. Rev.2.1a / Nov. 09

For more information please see the hardware user guide.

OmniSwitch 6855-14 Internal Architecture

OS6855 Series Boilerplate Doc. Rev.2.1a / Nov. 09

OmniSwitch 6855-U10 Internal Architecture

OS6855 Series Boilerplate Doc. Rev.2.1a / Nov. 09

OS6855 Series Boilerplate Doc. Rev.2.1a / Nov. 09

OmniSwitch 6855-24 Internal Architecture

OS6855 Series Boilerplate Doc. Rev.2.1a / Nov. 09

RJ45 console port USB (not used)

OS6855 Series Boilerplate Doc. Rev.2.1a / Nov. 09

OmniSwitch 6855-U24 Internal Architecture

OS6855 Series Boilerplate Doc. Rev.2.1a / Nov. 09

OS6855 Series Boilerplate Doc. Rev.2.1a / Nov. 09

OmniSwitch 6855-U24X Back Panel

OmniSwitch 6855-U24 Internal Architecture

OS6855 Series Boilerplate Doc. Rev.2.1a / Nov. 09

The OmniSwitch OS6855 Power Supply System

Power supplies for OS6855-14 and OS6855-U10

Power Supply Models

Power supplies for OS6855-24 and OS6855-U24

OmniSwitch 6855 Backup Power Supplies Matrix

- "PSL" denotes power supply for the 24 port models only.

100 FX Ethernet Transceivers

Supported Configuration Matrix for industrial grade tranceivers

OS6855 Series Boilerplate Doc. Rev.2.1a / Nov. 09

Managing Power over Ethernet (PoE)

Power over Ethernet Specifications

OmniSwitch 6855 Series platforms supporting PoE

OS6855 Series Boilerplate Doc. Rev.2.1a / Nov. 09

Port Priority Levels

Understanding Priority Disconnect

OS6855 Series Boilerplate Doc. Rev.2.1a / Nov. 09

Monitoring Power over Ethernet via CLI

OS6855 Series Boilerplate Doc. Rev.2.1a / Nov. 09

Redundant AC Circuit Recommendation

Grounding the Chassis

OS6855 Series Boilerplate Doc. Rev.2.1a / Nov. 09

MTBF ( Mean Time Between Failure)

OS6855 Series Boilerplate Doc. Rev.2.1a / Nov. 09

OS6855 Series Boilerplate Doc. Rev.2.1a / Nov. 09

OS6855 Series Boilerplate Doc. Rev.2.1a / Nov. 09

OS6855 Series Boilerplate Doc. Rev.2.1a / Nov. 09

OS6855 Series Boilerplate Doc. Rev.2.1a / Nov. 09

OS6855 Series Boilerplate Doc. Rev.2.1a / Nov. 09

OS6855 Series Boilerplate Doc. Rev.2.1a / Nov. 09