|
* DNOS 3.x: This is a family of firmware for the campus access switches that can only be managed using a web based GUI or run as unmanaged device.
===DNOS6h a range of new fea===
===DNOS6===
* DNOS 6.x: This is the operating system running on the Dell Networking N-series (campus) networking switches. It is the latest version of the 'PowerConnect' operating system, running on a Linux Kernel. It is available as upgrade for the PowerConnect 8100 series switches (which then become a Dell Networking N40xx switch) and it also is installed on all DN N1000, N2000 and N3000 series switches. It has a full web-based GUI together with a full CLI (command line interface) and the CLI will be very similar to the original PowerConnect CLI, though with a range of new features like PVSTP (per VLAN spanning tree), Policy Based Routing and [[MLAG]].
===DNOS9===
* DNOS 9.x: This is the operating system running on Dell Networking S- and Z- series switches and is a further development of the [[FTOS]] or Force10 Operating System. Standard DNOS 9.x (and FTOS) only offers a CLI and no GUI, although with the automation toolset it is possible to create your own webGUI on DNOS9 / FTOS switches. DNOS 9.x is running on [[NetBSD]].
Only the PowerConnect 8100 will be able to run on DNOS 6.x: all other PowerConnect ethernet switches will continue to run its own PowerConnect OS (on top of VxWorks) while the PowerConnect W-series run on a Dell specific version of ArubaOS.
The Dell Networking S- xxxx and Z9x00 series will run on DNOS where the other Dell Networking switches will continue to run FTOS 8.x firmware.
===OS10===
OS10 is a Linux-based open networking OS that can run on all ONIE switches. As it runs directly in a Linux environment network admins can highly automate the network platform and manage the switches in a similar way as the (Linux) servers. OS10 is still under development, but available for testing and development.
==Hardware Abstraction Layer==
Three of the four product families from Dell Networking are using the [[Broadcom]] [[Broadcom#Trident+ ASIC|Trident+]] [[ASIC]]s, but the company doesn't use the [[API]]s from Broadcom: the developers at Dell Networking have written their own [[Hardware Abstraction Layer]] so that DNOS 9.x can run on different hardware platforms with minimal impact for the firmware. Currently three of the four DN switch families are based on the Broadcom Trident family (while the 4th - the E-series- run on self-developed ASICs<ref>Architecture description of the [http://www.force10networks.com/whitepapers/pdf/wp_DescESeries.pdf Force10 E-series] platform. Force10, 2006. Retrieved: 3 August 2012</ref>); and two of them are running DNOS 9.x (S- and Z- series) and if the product developers want or need to use different hardware for new products they only need to develop a HAL for that new hardware and the same firmware can run on it. This keeps the company flexible and not dependent on a specific hardware-vendor and can use both 3rd party or self designed ASICs and chipsets.
The underlying OS on which DNOS 9.x, runs, is based on [[NetBSD]] (while the DNOS 6.x runs on a Linux kernel), an implementation which is often used in embedded networking-systems. NetBSD is a very stable, open source, OS running on many different hardware platforms. By choosing for a proven technology with extended TCP functionality built into the core of the OS it reduces time during development of new products or extending the DNOS with new features.<ref>Force10 [http://www.force10networks.com/products/pdf/F10_FTOS.pdf FTOS Datasheet]{{dead link|date=September 2017 |bot=InternetArchiveBot |fix-attempted=yes }}, retrieved: 28 January 2012</ref>
===Modular setup===
DNOS 9.x is also modular where different parts of the OS run independently from each other within one switch: if one process would fail the impact on other processes on the switch are limited. This modular setup is also taken to the hardware level in some product-lines where a routing-module has three separate CPUs: one for management, one for L2 and one for L3 processing. This same approach is also used in the newer firmware-families from Cisco like the [[NX-OS]] for the Nexus product-line or the [[IOS XR]] for the high-end routers (the [[Carrier Routing System]]s) from [[Cisco Systems|Cisco]]. (and unlike the original [[IOS]]: processes under IOS aren't isolated from each other). This approach is regarded not only a way to make the firmware more resilient but also increases the security of the switches<ref>Communication Security Establishment Canada (CSEC) on [http://www.cse-cst.gc.ca/its-sti/services/cc/force-networks-v10-eng.html Force10 FTOS 7.8] {{webarchive|url=https://web.archive.org/web/20110819231415/http://www.cse-cst.gc.ca/its-sti/services/cc/force-networks-v10-eng.html |date=2011-08-19 }}</ref><ref>CSEC report on [http://www.cse-cst.gc.ca/documents/services/cc/force-networks-v10-sec-eng.pdf Security Target: Force10 Networks FTOS 7.8] {{webarchive|url=https://web.archive.org/web/20130604142300/http://www.cse-cst.gc.ca/documents/services/cc/force-networks-v10-sec-eng.pdf |date=2013-06-04 }}, published: 17 August 2009, retrieved: 28 January 2012</ref>
==Capabilities==
All DNOS 9.x based switches offer a wide range of layer2 and layer3 protocols. All features are available on all switches: some switch models (in the S-series) offer an additional license for layer3 or routing: this additional license is NOT required to use that protocol, but only required to get support from the Dell Networking support department on using these features. All interfaces on DNOS 9.x running switches are configured as a layer3 interface and by default shutdown. To use such an interface as an ethernet switchport you need to configure it as such (with the command "switchport") and then enable that port using "no shutdown".
Unlike DNOS 6.x, DNOS 9.x only offers a command line interface (CLI) to configure and monitor the switch directly, though it is possible with the Automation Tools to create your own webGui on DNOS 9.x switches.
| 