Hubbry Logo
Network switchNetwork switchMain
Open search
Network switch
Community hub
Network switch
logo
7 pages, 0 posts
0 subscribers
Be the first to start a discussion here.
Be the first to start a discussion here.
Network switch
Network switch
Network switch
View on Wikipedia
from Wikipedia

Avaya ERS 2550T-PWR, a 50-port Ethernet switch

A network switch (also called switching hub, bridging hub, Ethernet switch, and, by the IEEE, MAC bridge[1]) is networking hardware that connects devices on a computer network by using packet switching to receive and forward data to the destination device.

A network switch is a multiport network bridge that uses MAC addresses to forward data at the data link layer (layer 2) of the OSI model. Some switches can also forward data at the network layer (layer 3) by additionally incorporating routing functionality. Such switches are commonly known as layer-3 switches or multilayer switches.[2]

Switches for Ethernet are the most common form of network switch. The first MAC Bridge[3][4][5] was invented[6] in 1983 by Mark Kempf, an engineer in the Networking Advanced Development group of Digital Equipment Corporation. The first 2 port Bridge product (LANBridge 100) was introduced by that company shortly after. The company subsequently produced multi-port switches for both Ethernet and FDDI such as GigaSwitch. Digital decided to license its MAC Bridge patent in a royalty-free, non-discriminatory basis that allowed IEEE standardization. This permitted a number of other companies to produce multi-port switches, including Kalpana.[7] Ethernet was initially a shared-access medium, but the introduction of the MAC bridge began its transformation into its most-common point-to-point form without a collision domain. Switches also exist for other types of networks including Fibre Channel, Asynchronous Transfer Mode, and InfiniBand.

Unlike repeater hubs, which broadcast the same data out of each port and let the devices pick out the data addressed to them, a network switch learns the Ethernet addresses of connected devices and then only forwards data to the port connected to the device to which it is addressed.[8]

Overview

[edit]
Cisco small business SG300-28 28-port Gigabit Ethernet rackmount switch and its internals

A switch is a device in a computer network that connects other devices together. Multiple data cables are plugged into a switch to enable communication between different networked devices. Switches manage the flow of data across a network by transmitting a received network packet only to the one or more devices for which the packet is intended. Each networked device connected to a switch can be identified by its network address, allowing the switch to direct the flow of traffic maximizing the security and efficiency of the network.

A switch is more intelligent than an Ethernet hub, which simply retransmits packets out of every port of the hub except the port on which the packet was received, unable to distinguish different recipients, and achieving an overall lower network efficiency.

An Ethernet switch operates at the data link layer (layer 2) of the OSI model to create a separate collision domain for each switch port. Each device connected to a switch port can transfer data to any of the other ports at any time and the transmissions will not interfere.[a] Because broadcasts are still being forwarded to all connected devices by the switch, the newly formed network segment continues to be a broadcast domain. Switches may also operate at higher layers of the OSI model, including the network layer and above. A switch that also operates at these higher layers is known as a multilayer switch.

Segmentation involves the use of a switch to split a larger collision domain into smaller ones in order to reduce collision probability and to improve overall network throughput. In the extreme case (i.e. micro-segmentation), each device is directly connected to a switch port dedicated to the device. In contrast to an Ethernet hub, there is a separate collision domain on each switch port. This allows computers to have dedicated bandwidth on point-to-point connections to the network and also to run in full-duplex mode. Full-duplex mode has only one transmitter and one receiver per collision domain, making collisions impossible.

The network switch plays an integral role in most modern Ethernet local area networks (LANs). Mid-to-large-sized LANs contain a number of linked managed switches. Small office/home office (SOHO) applications typically use a single switch, or an all-purpose device such as a residential gateway to access small office/home broadband services such as DSL or cable Internet. In most of these cases, the end-user device contains a router and components that interface to the particular physical broadband technology.

Many switches have pluggable modules, such as Small Form-factor Pluggable (SFP) modules. These modules often contain a transceiver that connects the switch to a physical medium, such as a fiber optic cable.[10][11] Alternatively, DAC (Direct Attach Copper) cables may be used in place of modules.[12] These modules were preceded by Medium Attachment Units connected via Attachment Unit Interfaces to switches[13][14] and have evolved over time: the first modules were Gigabit interface converters, followed by XENPAK modules, SFP modules, XFP transceivers, SFP+ modules, QSFP,[15] QSFP-DD,[16] and OSFP[17] modules. Pluggable modules are also used for transmitting video in broadcast applications.[18][19] With the advent of increased speeds together with Co-packaged optics (CPO), which bring the transceivers close to the switching chip of the switch, reducing power consumption, pluggable modules become replaceable laser light sources, and fiber optics are connected directly to the front of the switch instead of through pluggable modules. CPO is also considerably easier to adapt to water cooling.[20][21][22][23]

Role in a network

[edit]

Switches are most commonly used as the network connection point for hosts at the edge of a network. In the hierarchical internetworking model and similar network architectures, switches are also used deeper in the network to provide connections between the switches at the edge.

In switches intended for commercial use, built-in or modular interfaces make it possible to connect different types of networks, including Ethernet, Fibre Channel, RapidIO, ATM, ITU-T G.hn and 802.11. This connectivity can be at any of the layers mentioned. While the layer-2 functionality is adequate for bandwidth-shifting within one technology, interconnecting technologies such as Ethernet and Token Ring is performed more easily at layer 3 or via routing.[24] Devices that interconnect at the layer 3 are traditionally called routers.[25]

Where there is a need for a great deal of analysis of network performance and security, switches may be connected between WAN routers as places for analytic modules. Some vendors provide firewall,[26][27] network intrusion detection,[28] and performance analysis modules that can plug into switch ports. Some of these functions may be on combined modules.[29]

Through port mirroring, a switch can create a mirror image of data that can go to an external device, such as intrusion detection systems and packet sniffers.

A modern switch may implement power over Ethernet (PoE), which avoids the need for attached devices, such as a VoIP phone or wireless access point, to have a separate power supply. Since switches can have redundant power circuits connected to uninterruptible power supplies, the connected device can continue operating even when regular office power fails.

In 1989 and 1990, Kalpana introduced the first multiport Ethernet switch, its seven-port EtherSwitch.[30]

Bridging

[edit]
A modular network switch with three network modules (a total of 36 Ethernet ports) and one power supply
A five-port layer-2 switch without management functionality
A five-port layer-2 switch without management functionality

Modern commercial switches primarily use Ethernet interfaces. The core function of an Ethernet switch is to provide multiple ports of layer-2 bridging. Layer-1 functionality is required in all switches in support of the higher layers. Many switches also perform operations at other layers. A device capable of more than bridging is known as a multilayer switch.

A layer 2 network device is a multiport device that uses hardware addresses (MAC addresses) to process and forward data at the data link layer (layer 2).

A switch operating as a network bridge may interconnect otherwise separate layer 2 networks. The bridge learns the MAC address of each connected device, storing this data in a table that maps MAC addresses to ports. This table is often implemented using high-speed content-addressable memory (CAM), some vendors refer to the MAC address table as a CAM table.

Bridges also buffer an incoming packet and adapt the transmission speed to that of the outgoing port. While there are specialized applications, such as storage area networks, where the input and output interfaces are the same bandwidth, this is not always the case in general LAN applications. In LANs, a switch used for end-user access typically concentrates lower bandwidth and uplinks into a higher bandwidth.

The Ethernet header at the start of the frame contains all the information required to make a forwarding decision, some high-performance switches can begin forwarding the frame to the destination whilst still receiving the frame payload from the sender. This cut-through switching can significantly reduce latency through the switch.

Interconnects between switches may be regulated using the Spanning Tree Protocol (STP) that disables forwarding on links so that the resulting local area network is a tree without switching loops. In contrast to routers, spanning tree bridges must have topologies with only one active path between two points. Shortest path bridging and TRILL (Transparent Interconnection of Lots of Links) are layer 2 alternatives to STP which allow all paths to be active with multiple equal cost paths.[31][32]

Types

[edit]
A rack-mounted 24-port 3Com switch

Form factors

[edit]
A ZyXEL ES-105A 5-port desktop Ethernet switch. The metal casing of the switch has been opened, revealing internal electronic components.

Switches are available in many form factors, including stand-alone, desktop units which are typically intended to be used in a home or office environment outside a wiring closet; rack-mounted switches for use in an equipment rack or an enclosure; DIN rail mounted for use in industrial environments; and small installation switches, mounted into a cable duct, floor box or communications tower, as found, for example, in fiber to the office infrastructures.

Rack-mounted switches may be stand-alone units, stackable switches or large chassis units with swappable line cards.

Configuration options

[edit]
  • Unmanaged switches have no configuration interface or options. They are plug and play. They are typically the least expensive switches, and therefore often used in a small office/home office environment. Unmanaged switches can be desktop or rack mounted.[33]
  • Managed switches have one or more methods to modify the operation of the switch. Common management methods include: a command-line interface (CLI) accessed via serial console, telnet or Secure Shell, an embedded Simple Network Management Protocol (SNMP) agent allowing management from a remote console or management station, or a web interface for management from a web browser. Two sub-classes of managed switches are smart and enterprise-managed switches.[33]
  • Smart switches (aka intelligent switches) are managed switches with a limited set of management features. Likewise, web-managed switches are switches that fall into a market niche between unmanaged and managed. For a price much lower than a fully managed switch they provide a web interface (and usually no CLI access) and allow configuration of basic settings, such as VLANs, port-bandwidth and duplex.[34][33]
  • Enterprise managed switches (aka managed switches) have a full set of management features, including CLI, SNMP agent, and web interface. They may have additional features to manipulate configurations, such as the ability to display, modify, backup and restore configurations. Compared with smart switches, enterprise switches have more features that can be customized or optimized and are generally more expensive than smart switches. Enterprise switches are typically found in networks with a larger number of switches and connections, where centralized management is a significant savings in administrative time and effort. A stackable switch is a type of enterprise-managed switch.

Typical management features

[edit]
A couple of managed D-Link Gigabit Ethernet rackmount switches, connected to the Ethernet ports on a few patch panels using Category 6 patch cables (all installed in a standard 19-inch rack)

Traffic monitoring

[edit]

It is difficult to monitor traffic that is bridged using a switch because only the sending and receiving ports can see the traffic.

Methods that are specifically designed to allow a network analyst to monitor traffic include:

  • Port mirroring – Because the purpose of a switch is to not forward traffic to network segments where it would be superfluous, a node attached to a switch cannot monitor traffic on other segments. Port mirroring is how this problem is addressed in switched networks: In addition to the usual behavior of forwarding frames only to ports through which they might reach their addressees, the switch forwards frames received through a given monitored port to a designated monitoring port, allowing analysis of traffic that would otherwise not be visible through the switch.
  • Switch monitoring (SMON) is described by RFC 2613 and is a provision for controlling facilities such as port mirroring.[35]
  • RMON[36]
  • sFlow

These monitoring features are rarely present on consumer-grade switches. Other monitoring methods include connecting a layer-1 hub or network tap between the monitored device and its switch port.[37]

See also

[edit]

Notes

[edit]

References

[edit]
[edit]
Revisions and contributorsEdit on WikipediaRead on Wikipedia

Network switch

View on Grokipedia
from Grokipedia
A network switch is a hardware device that connects multiple computing devices—such as computers, printers, and servers—within a (LAN), enabling them to communicate efficiently by receiving data packets from one device and forwarding them to the intended destination based on MAC addresses at the (Layer 2) of the . Unlike older hubs that broadcast data to all connected devices, a switch intelligently directs traffic only to the specific recipient, reducing and improving overall performance. Network switches operate by maintaining a dynamic table, often called a (CAM) table, which maps to the physical on the switch. When a packet arrives at an input , the switch examines the destination ; if it matches an entry in the table, the packet is forwarded to the corresponding output , while unknown addresses trigger a temporary broadcast (flooding) to learn new mappings through a process known as MAC learning. This mechanism ensures low-latency, collision-free communication, particularly in Ethernet-based networks supporting speeds from 10 Mbps to 100 Gbps or higher. Switches come in various types to suit different network needs, including unmanaged switches for basic, plug-and-play connectivity in small environments and managed switches that provide configurable features like virtual LANs (VLANs), (QoS) prioritization, and security protocols. Layer 2 switches focus on MAC-based forwarding within a single , while Layer 3 switches incorporate capabilities to connect multiple subnets or VLANs, bridging the gap between switching and functions. In contrast to routers, which connect disparate networks (e.g., LAN to WAN) and handle inter-network traffic using IP addresses at the network layer (Layer 3), switches are optimized for intra-network device-to-device communication, making them essential building blocks for scalable, high-performance LANs in homes, offices, and data centers. Their adoption has been pivotal in evolving from shared-medium networks to dedicated, full-duplex topologies, supporting modern applications like streaming, , and IoT deployments.

Fundamentals

Definition and Overview

A network switch is a hardware device that connects multiple devices within a , forwarding data packets between them based on Media Access Control (MAC) addresses to enable efficient communication in local area networks (LANs). Unlike simpler devices, it operates primarily at Layer 2 of the , inspecting packet headers to direct traffic only to the intended recipient rather than broadcasting to all connected devices. This selective forwarding minimizes and supports high-speed data transfer in environments like offices or data centers. Key components of a network switch include multiple ports for device connections, such as Ethernet RJ-45 ports or optic interfaces; (ASIC) chips that handle rapid packet processing and forwarding decisions; and a that facilitates high-capacity internal data exchange between ports and processing elements. These elements work together to ensure reliable, low-overhead operation at wire speeds. Network switches differ from hubs, which indiscriminately broadcast data to all ports in half-duplex mode, leading to collisions and inefficiency; switches intelligently segment traffic and enable full-duplex communication for collision-free transmission. In contrast to routers, which function at Layer 3 using IP addresses to interconnect distinct networks, switches focus on intra-LAN connectivity via MAC addresses without between subnets. The primary benefits of network switches include increased available bandwidth through dedicated collision domains per port, reduced latency from targeted packet delivery, and the ability to handle multiple simultaneous connections without performance degradation. Modern switches evolved from early bridge technologies that connected network segments, providing a scalable foundation for contemporary LANs.

Historical Development

Network switches emerged in the mid-1980s as an evolution of network bridges, which addressed limitations in early local area networks (LANs) by segmenting traffic and reducing collisions compared to shared-medium hubs. The first commercial Ethernet bridge, Digital Equipment Corporation's (DEC) LANBridge 100, was introduced in 1986, marking a pivotal advancement in multiport switching for Ethernet environments. This device, building on bridge technology developed internally at DEC since 1983, enabled efficient frame forwarding across LAN segments, laying the groundwork for modern switches. Bob Metcalfe, co-inventor of Ethernet in 1973 at PARC, played a foundational role in this progression through his work on distributed packet-switching, which influenced the shift toward scalable LAN technologies like switches. In the 1990s, standardization efforts solidified the role of switches in enterprise networks. The standard, which included the (STP) developed by in 1985, was published in 1990, enabling loop-free topologies essential for multi-switch deployments and achieving widespread adoption throughout the decade. (100 Mbps), standardized as IEEE 802.3u in 1995, spurred the commercialization of high-speed switches, allowing networks to transition from 10 Mbps shared media to dedicated switched connections. Cisco Systems, founded in 1984, began dominating the market during this period through acquisitions like Crescendo Communications in 1993, which bolstered its Ethernet switching portfolio and established it as a leader in scalable network infrastructure. The 2000s saw further performance leaps with , initially standardized by IEEE 802.3z in 1998 for fiber optic media and extended by IEEE 802.3ab in 1999 for twisted-pair copper following drafts in 1997, and widely commercialized in the early for backbone and desktop applications. Managed switches gained prominence, incorporating (SNMP) for remote configuration and monitoring, a standard formalized in the late 1980s but integrated into enterprise-grade switches during this era to support growing network complexity. From the 2010s onward, higher-speed Ethernet variants proliferated to meet data center and cloud demands. The IEEE 802.3ae standard for 10 Gigabit Ethernet, ratified in 2002, saw significant adoption in the 2010s, with port shipments exceeding two million by 2009 and continuing to grow. Standards for 40G and 100G Ethernet (IEEE 802.3ba) were approved in 2010, enabling aggregation in high-bandwidth environments. Software-defined networking (SDN) emerged around 2011 with the release of OpenFlow version 1.1 by the Open Networking Foundation, allowing programmable control planes in switches for dynamic traffic management. Post-2020, edge computing has influenced switch design by emphasizing low-latency, distributed processing capabilities to support IoT and real-time applications at network peripheries. More recently, the IEEE 802.3df standard for 800 Gigabit Ethernet was approved in 2024, further enhancing switch performance for data centers and high-bandwidth applications. Ongoing work includes IEEE P802.3dj targeting up to 1.6 Tb/s.

Core Operations

Switching Mechanisms

Network switches operate at Layer 2 of the OSI model, primarily using MAC addresses to make forwarding decisions for Ethernet frames. The core process begins with MAC address learning, where the switch inspects the source MAC address of each incoming frame on a port and records it in the Content Addressable Memory (CAM) table, also known as the MAC address table. This table maps source MAC addresses to specific ingress ports, allowing the switch to build a dynamic forwarding database without manual configuration. If a source MAC address is already in the table but associated with a different port, the switch updates the entry to reflect the new port, ensuring the table remains current as devices move or networks change. Once the CAM table is populated, the switch uses it to forward frames based on the destination . For unicast forwarding, the switch performs a lookup in the CAM table; if the destination MAC matches an entry, the frame is sent only to the associated port, optimizing bandwidth by avoiding unnecessary traffic. If the destination MAC is unknown (not in the table), the switch treats it as an unknown unicast and floods the frame to all ports except the source port to ensure delivery while learning the destination's location from subsequent responses. Broadcast forwarding occurs for frames with a destination MAC of all ones (FF:FF:FF:FF:FF:FF), such as ARP requests, where the switch floods the frame to all ports except the ingress port to reach all devices in the . For multicast forwarding at Layer 2, without additional protocols, the switch typically floods frames to all ports except the source, similar to broadcasts; however, with mechanisms like enabled, it forwards to only those ports where group membership has been reported, directing traffic to interested receivers. Switches employ various switching techniques to balance latency, error detection, and performance when forwarding frames. In store-and-forward mode, the switch receives the entire frame, buffers it in memory, and performs a to verify integrity before forwarding; this ensures error-free transmission but introduces latency proportional to frame size divided by link bandwidth, typically around 5.12 μs for a 64-byte frame on . Cut-through switching minimizes latency by reading only the first 6 bytes (destination ) and immediately forwarding if the egress port is determined, without full error checking; this can propagate errors but is ideal for low-error environments, achieving near-wire-speed performance. A hybrid approach, fragment-free switching, stores the first 64 bytes (the minimum size, covering the collision window) to check for early collisions before forwarding the rest, reducing error propagation while keeping latency lower than store-and-forward. By design, switches segment networks into separate collision domains per port, isolating traffic and preventing frame collisions that occur in shared media like hubs. Each port operates as an independent domain, allowing simultaneous transmissions without interference, which is foundational for full-duplex operation where devices can send and receive data concurrently over separate transmit and receive paths, doubling effective bandwidth (e.g., 200 Mbps on a 100 Mbps link) and eliminating the need for carrier sense multiple access with collision detection (CSMA/CD). This micro-segmentation enhances scalability in modern Ethernet networks, where full-duplex is the default on switch ports connected to end devices. To prevent bridging loops in redundant topologies, switches implement the Spanning Tree Protocol (STP) as defined in . STP runs on all switch ports, exchanging Bridge Protocol Data Units (BPDUs) to elect a root bridge based on the lowest bridge ID (priority plus ), then calculates the shortest path to the root for each switch and blocks redundant ports to create a loop-free logical . Ports in blocking state do not forward data traffic but listen for BPDUs; if a link failure occurs, STP reconverges by promoting blocked ports, with a typical convergence time of 30-50 seconds in the original standard. This mechanism ensures path redundancy while maintaining network stability, originally standardized in in 1990 and revised in 1998.

Layered Functionality

Network switches primarily function at the OSI model's Layer 2 (Data Link layer), where they perform switching based on Media Access Control (MAC) addresses to forward Ethernet frames between connected devices. At this layer, switches maintain a MAC address table that maps device MAC addresses to specific ports, enabling efficient frame delivery by examining the destination MAC address in incoming frames and directing them to the appropriate output port without broadcasting to all ports. Frame handling at Layer 2 includes validation through the Frame Check Sequence (FCS), a 32-bit cyclic redundancy check (CRC) appended to each Ethernet frame to detect transmission errors; if the recalculated FCS at the receiving end does not match the received value, the frame is discarded to prevent corrupted data propagation. At the OSI Layer 1 (), switches provide the foundational connectivity through various physical interfaces that handle electrical or optical signal transmission. Common interfaces include RJ-45 connectors for twisted-pair copper cabling, supporting speeds up to 10 Gbps in modern implementations, and (SFP) transceivers for optic links, allowing flexible deployment in diverse environments such as data centers or enterprise LANs. These interfaces ensure reliable bit-level transmission while adhering to standards. Many advanced switches extend functionality beyond Layer 2 into Layer 3 (Network layer) through multilayer designs, where they inspect IP headers to enable routing capabilities such as inter-VLAN routing and application of Access Control Lists (ACLs) based on source/destination IP addresses and protocols. At Layer 4 (Transport layer) and above, switches support basic filtering mechanisms, such as port-based ACLs for TCP and UDP traffic, allowing control over specific application ports (e.g., permitting HTTP on TCP port 80) without performing deep packet inspection, which is typically reserved for dedicated security appliances. Support for Virtual Local Area Networks (s) is a key Layer 2 extension standardized by , which inserts a 4-byte VLAN tag into Ethernet frames to enable logical segmentation of broadcast domains across physical networks. This tagging includes a 12-bit VLAN Identifier (VID) for up to 4096 unique s and a priority field for quality-of-service differentiation; trunk ports configured for 802.1Q carry tagged frames from multiple s, facilitating scalable network partitioning without requiring separate physical infrastructure. In contrast to traditional bridges, which operate similarly at Layer 2 but rely on software-based processing and typically support only 2 to 4 ports, network switches employ dedicated for hardware-accelerated forwarding, achieving wire-speed across higher port densities—often 24 to 48 ports or more—making them suitable for modern, high-throughput environments.

Network Integration

Role in Network Architectures

Network switches play a pivotal role in local area networks (LANs) by serving as the central connectivity hub for endpoints such as personal computers, servers, and printers, enabling efficient data exchange within a bounded geographic area. In these environments, switches facilitate the formation of star topologies, where all devices connect directly to the switch, centralizing traffic control and minimizing collisions compared to older bus or ring configurations. This design enhances performance by allowing full-duplex communication on each , supporting higher bandwidth demands in modern or campus settings. Within larger enterprise architectures, switches are integral to hierarchical network designs, which organize into distinct layers for scalability and manageability. At the access layer, switches provide direct connections to end-user devices (e.g., PCs, phones, printers), offering port-level security and (PoE) to support devices like IP phones. Large MAC address tables are not needed in access switches because they connect directly to end-user devices, typically learning only a limited number of MAC addresses—often one per port, or two if VoIP is used with PC passthrough—making table sizes of 4K–16K entries sufficient. A 48-port access switch might only need to handle a few hundred MAC entries at most. In contrast, distribution and core switches aggregate traffic from many access switches and must track thousands of MAC addresses across the broader network, requiring much larger tables. The distribution layer employs switches for aggregating traffic from multiple access switches, enforcing policies such as access control lists (ACLs) and routing to segment network traffic efficiently. Meanwhile, core layer switches form the high-speed backbone, prioritizing low-latency, high-throughput forwarding across the enterprise without processing intensive policies, ensuring seamless interconnectivity between buildings or data centers. Switches integrate with complementary devices to extend network reach and functionality; they connect upstream to routers for access to wide area networks (WANs) and the , while downstream ports link to wireless access points (APs) to enable hybrid wired-wireless environments. This integration allows switches to distribute IP addresses and manage traffic from APs, supporting seamless mobility for users. For scalability in expansive deployments, techniques like switch stacking combine multiple units into a single logical entity, expanding port and providing through ring topologies with up to 480 Gbps of stacking bandwidth. Cisco's StackWise Virtual technology further virtualizes two chassis as one, simplifying management and enhancing in larger fabrics. In contemporary contexts, switches adapt to specialized environments for optimal performance. In data centers, top-of-rack (ToR) switches mount directly above server racks, providing low-latency connectivity to hosts while aggregating traffic to spine or layers in scalable fabrics supporting speeds up to 800 Gbps. For (IoT) networks, edge switches deploy at the network periphery to connect low-power sensors and actuators, offering ruggedized ports, industrial protocols, and capabilities to process data locally and reduce latency in distributed systems like or smart cities.

Bridging and Forwarding

Network switches operate as multiport bridges, extending the principles of transparent bridging to connect multiple (LAN) segments efficiently. Transparent bridging, as defined in the IEEE 802.1D standard, enables switches to learn the location of devices automatically through a self-learning process without requiring explicit configuration from connected hosts. When a frame arrives, the switch examines the source media access control (MAC) address and associates it with the ingress port in its forwarding database, building a dynamic map of the network topology over time. For frames with destination MAC addresses already known in the forwarding database, the switch performs forwarding by directing the frame solely to the corresponding egress , optimizing bandwidth usage and reducing unnecessary traffic. If the destination is unknown, the switch resorts to flooding, the frame out all other except the source to ensure delivery, a mechanism that also aids in initial network discovery. This flooding versus selective forwarding decision hinges directly on the outcome of a destination lookup in the forwarding database. To maintain the integrity of the forwarding database, switches implement aging timers for learned MAC address entries, automatically removing inactive records to accommodate network changes such as device mobility or failures. The default aging time for these entries is 300 seconds, after which an unused is discarded unless refreshed by subsequent traffic. A critical aspect of bridging in switches is loop prevention, achieved through the specified in , which constructs a loop-free logical across the bridged network. STP initiates by electing a root bridge, the central reference point, based on the lowest bridge ID—a composite value comprising a configurable priority (default 32768) and the switch's base , ensuring deterministic selection in case of ties. Once elected, STP calculates the shortest path to the root for each switch using port costs, which are inversely proportional to link speed (e.g., lower costs for ports versus 10 Mbps links), blocking redundant paths to eliminate loops while allowing . The original STP, while effective, suffers from slow convergence times of 30 to 50 seconds following changes due to its timer-based . To this, the Rapid Spanning Tree Protocol (RSTP), ratified as IEEE 802.1w in 2001, introduces enhancements such as explicit handshaking for port transitions and role-based proposals, enabling convergence in as little as a few seconds—typically 3 to 6 seconds under default hello intervals. RSTP maintains backward compatibility with STP while accelerating recovery through reduced reliance on lengthy timers like max age and forward delay. In contrast to transparent bridging prevalent in Ethernet environments, source-route bridging represents a legacy approach primarily associated with networks under IEEE 802.5 standards. In source-route bridging, the originating device embeds the full path through bridges in the frame header using route information fields, allowing bridges to forward based on explicit instructions rather than learned addresses; this method, while enabling complex topologies, is not the primary bridging technique for modern Ethernet switches due to its overhead and Token Ring's obsolescence.

Classifications and Variants

Layer-Based Types

Network switches are classified based on the layers they operate at, determining their , forwarding mechanisms, and suitable applications. Layer 1 switches, such as advanced , function solely at the by amplifying and regenerating electrical or optical signals to extend transmission distances without processing any addressing information. Traditional Layer 1 devices like hubs lack , broadcasting all incoming traffic to every port and creating a single , which leads to inefficiencies like increased collisions in shared media environments. Hubs are obsolete and rarely used in modern networks. In contrast, modern Layer 1 switches, such as the 3550-H for low-latency, high-speed interconnects in monitoring and distribution, provide dedicated physical connections via matrix switching without or collision domains, primarily appearing in specialized high-density signal distribution scenarios. Layer 2 switches operate at the , forwarding Ethernet frames based on MAC addresses learned from incoming traffic, thereby segmenting LANs into separate collision domains per port to reduce broadcast traffic and improve efficiency. They maintain a table to make forwarding decisions, enabling fast, hardware-based switching within a . Unmanaged Layer 2 switches are simple, plug-and-play devices without configuration interfaces, ideal for small-scale home or office LANs requiring basic connectivity without advanced management. In contrast, managed Layer 2 switches offer configurable features like support for logical segmentation, , and to prevent loops, making them suitable for enterprise environments needing controlled LAN expansion. Layer 3 switches integrate Layer 2 capabilities with routing, using IP addresses to forward packets between different subnets or VLANs, supporting both static routes and dynamic protocols like OSPF or BGP for path determination. They achieve high-performance inter-VLAN routing at wire speeds—matching the full bandwidth of ports—through specialized application-specific integrated circuits () that handle forwarding in hardware, minimizing latency compared to software-based routers. This makes Layer 3 switches essential in medium to large enterprise networks for efficient traffic segmentation and without bottlenecks. Multilayer switches extend functionality to Layer 4 and above, incorporating details like TCP/UDP port numbers to enable application-aware processing, such as prioritizing traffic via (QoS) policies or duplicating traffic for analysis through . These switches support features like access control lists based on application protocols but stop short of or stateful firewalling, distinguishing them from dedicated security appliances. They are deployed in environments requiring enhanced , such as networks balancing performance and basic application optimization. Specialized switches include (SDN) variants that function as agents, separating the from the data plane to allow programmable forwarding via centralized controllers, enabling dynamic policy enforcement across networks. In data centers, fabric switches utilize Clos topology—a multi-stage, non-blocking architecture with spine and leaf layers—to provide scalable, low-latency interconnects supporting massive patterns between servers. These designs ensure high throughput and in hyperscale environments.

Form Factors and Deployment

Network switches are available in diverse form factors tailored to specific physical and environmental requirements, ranging from compact desktop models to scalable rack-mounted and modular designs. These variations enable deployment in settings from small offices to large-scale enterprise and industrial networks, prioritizing factors like space efficiency, expandability, and durability. Desktop unmanaged switches represent the simplest form factor, characterized by their small size and plug-and-play operation without requiring configuration. Typically equipped with 5 to 8 ports, these switches are suited for home or small office/home office (SOHO) environments, providing basic connectivity for devices like computers and printers in low-density setups. A 5-port Gigabit Ethernet switch is a suitable and common choice for such networks due to its simplicity, affordability, and sufficient port capacity for basic connectivity needs. In contrast, rack-mount switches are engineered for standardized 19-inch equipment racks, commonly occupying 1U (1.75 inches high) or 2U chassis to accommodate higher port densities of 24 to 48 Gigabit or faster interfaces. These are prevalent in enterprise wiring closets, where they support modular expansions like (PoE) capabilities and facilitate organized cabling in structured networking infrastructures. Switches further differ in configuration types: fixed-configuration models integrate a set number of ports in a non-expandable, all-in-one unit, offering cost-effective simplicity for stable network sizes, while modular switches feature expandable slots for line cards that allow incremental additions of ports, interfaces, or performance upgrades to adapt to growing demands. Deployment environments influence form factor selection, with wall-mount designs providing rugged, compact enclosures for industrial applications exposed to vibration, dust, or temperature extremes, often featuring DIN-rail compatibility for secure installation. In data centers, switches are frequently integrated into blade server chassis, enabling high-density interconnectivity among multiple servers while minimizing cabling and optimizing airflow in rack-based architectures. For campus networks, outdoor-rated switches withstand weather elements like rain, humidity, and wide temperature ranges, supporting extended deployments for wireless access points or surveillance in external areas. Power delivery options enhance versatility, particularly through PoE standards that transmit both data and electricity over Ethernet cables. The IEEE 802.3af standard delivers up to 15.4 watts per port for basic devices, while 802.3at extends this to 30 watts, and 802.3bt supports up to 90 watts per port for power-hungry endpoints like pan-tilt-zoom cameras or access points. Additionally, redundant units (PSUs) are standard in enterprise and industrial switches, operating in modes to maintain uptime during primary power disruptions and supporting hot-swappable configurations for minimal .

Management and Features

Configuration and Management

Network switches are configured and managed through a variety of interfaces and protocols to enable operational control, monitoring, and . Configuration involves setting parameters such as port attributes and , while encompasses remote access, , and security mechanisms. These capabilities distinguish basic switches from advanced ones, allowing administrators to optimize and troubleshoot issues efficiently. Switches are broadly categorized as unmanaged or managed based on their configurability. Unmanaged switches operate in a plug-and-play manner, requiring no initial setup or ongoing administration, as they automatically handle frame forwarding without user intervention. In contrast, managed switches support detailed configuration and monitoring, typically assigned an for remote access, enabling features like and traffic prioritization. A middle ground are smart or web-smart switches, which provide limited capabilities through a web-based interface for tasks such as basic port monitoring, configuration, and , without full CLI or SNMP support, making them suitable for small to mid-sized networks. This allows network administrators to customize operations for enterprise environments, though it introduces complexity compared to unmanaged models. Management interfaces provide multiple access methods for configuration and oversight. The console interface uses a serial connection for local, out-of-band access, ideal for initial setup or recovery scenarios where network connectivity is unavailable. Remote CLI access occurs via for unencrypted sessions or SSH for secure, encrypted connections, allowing command-line administration over IP networks. Web-based graphical user interfaces (GUIs) are accessible through HTTP or , offering browser-based configuration for less technical users, with providing encryption to protect credentials and data. SNMP serves primarily for monitoring but also supports limited configuration, with versions including SNMPv1 and v2c using community strings for basic authentication, while SNMPv3 adds user-based security, encryption, and integrity checks. Key configurations on managed switches include port-level settings, , loop prevention, and . Port speed and duplex mode can be set to auto-negotiation for automatic detection or manually to fixed values like 10/100/1000 Mbps full-duplex, ensuring compatibility and preventing mismatches that cause errors. VLAN assignment groups ports into logical networks for segmentation, configured via CLI or GUI to isolate traffic and enhance security. (STP) settings, such as enabling Rapid STP (RSTP) or configuring port roles and priorities, prevent loops by blocking redundant paths while allowing . updates maintain security and functionality, performed via CLI using TFTP or USB, with backups of current configurations recommended prior to upgrades. Management protocols facilitate monitoring, logging, and . Remote Monitoring () collects statistics like packet counts and errors on interfaces, enabling proactive threshold-based alerts without constant polling. forwards event logs to a central server for auditing and , capturing messages via UDP or secure TLS connections. , , and (AAA) integrates with for centralized user validation over UDP or TACACS+ for TCP-based, granular command-level control, often configured with multiple servers for redundancy. Automation streamlines deployment and ongoing management. Zero-touch provisioning (ZTP) enables switches to automatically download configurations and images from a DHCP server upon , reducing manual intervention in large-scale rollouts. API integrations like RESTCONF (HTTP-based) and (XML over SSH) allow programmatic configuration using models, supporting tools for orchestration in software-defined networks.

Traffic Monitoring and Analysis

Traffic monitoring and analysis in network switches involve techniques to observe, capture, and diagnose traffic patterns, enabling administrators to assess performance, identify anomalies, and optimize network operations. These methods provide visibility into data flows without disrupting normal forwarding, supporting proactive maintenance in enterprise and data center environments. Port mirroring, also known as Switched Port Analyzer (SPAN) in Cisco implementations, copies traffic from one or more source ports or VLANs to a designated destination port for external analysis tools like Wireshark or tcpdump. This allows real-time packet inspection on a single switch without affecting production traffic. Remote SPAN (RSPAN) extends this capability across multiple switches by encapsulating mirrored traffic in a dedicated VLAN, facilitating centralized monitoring in distributed topologies. RSPAN requires configuration of source ports, a VLAN for transport, and a destination port on the remote switch, ensuring mirrored packets traverse trunks without interference. Simple Network Management Protocol (SNMP) counters provide aggregated metrics on interface activity, including bytes and packets sent or received, error types such as (CRC) failures and collisions, and utilization thresholds. These counters, stored in the switch's (MIB), enable polling by systems to track long-term trends like interface saturation. For high-speed interfaces exceeding 20 Mbps, 64-bit counters are recommended to avoid wraparound issues in byte and packet tallies. Utilization is calculated from input/output octet rates against interface capacity, alerting on thresholds like 80% to prevent degradation. Flow-based monitoring exports summarized traffic records from switches to external collectors, reducing overhead compared to full packet capture. , originally developed by , aggregates flows based on attributes like source/destination IP, ports, and protocol, exporting version 9 records for detailed analysis of top talkers and application usage. sFlow employs statistical sampling, typically 1:1000 packets, to monitor high-volume networks efficiently by sending UDP datagrams with header samples and counter data. IPFIX, standardized as RFC 7011, extends with flexible templates for bidirectional flows and extensible fields, supporting modern protocols in scalable environments. Built-in diagnostics on network switches include LED indicators for quick status checks, such as link status, speed, and activity on ports, allowing immediate visual identification of issues like no-link or duplex mismatches. Command-line interfaces provide deeper insights; for example, the "show interfaces" command in displays real-time statistics including input/output rates, errors, and buffer failures for port-level problems. These tools operate via console or management interfaces, offering non-disruptive access to operational data during live network conditions. Troubleshooting common issues like bandwidth bottlenecks relies on SNMP utilization counters to pinpoint oversubscribed ports, where sustained high input rates indicate congestion from bursty or misconfigured uplinks. Broadcast storms, caused by loops in layer 2 , flood the network with duplicate frames, detectable through rapid increases in broadcast packet counters and STP logs showing topology changes or root inconsistencies. (STP) logs, accessed via commands like "show spanning-tree detail," reveal events such as port state transitions or BPDU inconsistencies, enabling loop isolation by blocking redundant paths.

Advanced Capabilities

Security and Quality of Service

Network switches incorporate various security mechanisms to protect against unauthorized access and network disruptions. Port security limits the number of MAC addresses that can be learned on a switch port, preventing unauthorized devices from connecting by restricting access to a predefined maximum, typically through MAC address limiting or sticky learning, where dynamically learned addresses are saved in the configuration to persist across reboots. Additionally, IEEE 802.1X provides port-based network access control, enabling mutual authentication between clients and the network via protocols like EAP, ensuring only authorized devices gain access to the port. DHCP snooping mitigates rogue DHCP server attacks by validating DHCP messages, allowing only trusted ports to forward server responses and building a binding table of legitimate client IP-MAC-port associations to block unauthorized IP assignments. Access control lists (ACLs) enhance switch by filtering traffic at Layer 2 and Layer 3, permitting or denying packets based on criteria such as source/destination MAC addresses, IP addresses, or numbers, which helps enforce policies and protect against unauthorized traffic flows. within ACLs further defends against denial-of-service (DoS) attacks by capping the transmission rate of specific traffic types, ensuring critical resources remain available. Storm control prevents broadcast, multicast, and unicast floods from overwhelming the network by monitoring traffic levels and dropping excess packets when thresholds—often set as percentages of bandwidth, such as 5-10% for broadcasts—are exceeded. For link-level protection, () provides encryption and integrity for Ethernet frames between directly connected devices, using AES-GCM to secure data in transit without impacting higher-layer protocols. Quality of Service (QoS) features in switches prioritize traffic to ensure reliable performance for critical applications amid congestion. Traffic classification identifies and marks packets using (CoS) bits in the 802.1Q tag for Layer 2 prioritization or Code Point (DSCP) values in the for Layer 3, enabling switches to apply consistent policies across the network. Queuing mechanisms manage buffered packets during overload; strict priority queuing serves high-priority queues first to minimize latency for time-sensitive traffic like voice, while weighted fair queuing (WFQ) allocates bandwidth proportionally among flows based on assigned weights, preventing any single flow from monopolizing resources. To control bandwidth usage, shaping and policing regulate outbound traffic rates. Shaping buffers excess packets to smooth bursts and conform to a committed rate, avoiding downstream drops, whereas policing discards or remarks non-conforming packets immediately to enforce strict limits, both aiding in fair allocation and preventing congestion propagation in switched environments. These QoS elements, often combined with basic segmentation for traffic isolation, support differentiated service delivery in enterprise networks.

Multilayer and Specialized Switches

Multilayer switches extend beyond basic Layer 2 and Layer 3 functionality by integrating hardware-accelerated routing capabilities, such as Express Forwarding (CEF), which uses a (FIB) stored in Ternary Content-Addressable Memory (TCAM) for parallelized, high-speed IP lookups without software intervention. These switches also support (MPLS) for efficient Layer 3 VPNs, enabling scalable routing and forwarding separation through per-VPN Routing and Forwarding (VRF) tables and label-based packet switching across provider edges. In data centers, specialized switches employ non-blocking fabrics, often based on Clos topologies, to ensure full wire-speed forwarding across all ports simultaneously, preventing internal congestion and supporting high-throughput applications like . Modern data center switches support Ethernet speeds up to 800 Gbps, with emerging 1.6 Tbps capabilities as of 2025, to meet demands of AI and . These fabrics integrate with (RoCE), a protocol that enables low-latency, over lossless Ethernet networks, reducing CPU overhead for storage and high-performance computing workloads. Software-Defined Networking (SDN) and Network Function Virtualization (NFV) switches leverage programmable data planes defined by the P4 language, allowing custom packet processing on hardware like or FPGAs without protocol dependencies. Such switches integrate with controllers like the Open Network Operating System (ONOS), which provides distributed management for white-box hardware and virtualized functions, enabling dynamic reconfiguration and redundancy in edge and core networks. Industrial and edge switches are ruggedized for harsh environments, featuring IP67-rated enclosures that protect against dust and water immersion, alongside wide operating temperature ranges from -40°C to 75°C for reliable deployment in outdoor or factory settings. They incorporate (TSN) standards, particularly IEEE 802.1Qbv's time-aware shaper, to guarantee bounded latency and deterministic delivery for real-time Industrial IoT applications like automation control. For wired-wireless convergence, certain enterprise switches embed and Wi-Fi 7 controllers, unifying management of Ethernet ports and access points to streamline deployment in branch or campus networks with seamless and centralized policy enforcement.

References

  1. https://www.cloudflare.com/learning/network-layer/what-is-a-network-switch/
  2. https://www.networkworld.com/article/969239/what-is-a-network-switch-and-how-does-it-work.html
  3. https://www.techtarget.com/searchnetworking/definition/switch
  4. https://www.cisco.com/site/us/en/learn/topics/networking/what-is-network-switching.html
  5. https://www.cisco.com/site/us/en/learn/topics/networking/what-is-an-ethernet-switch.html
  6. https://www.spiceworks.com/tech/networking/articles/what-is-network-switch/
  7. https://www.ciscolive.com/c/dam/r/ciscolive/global-event/docs/2023/pdf/BRKARC-2092.pdf
  8. https://www.cisco.com/c/en/us/solutions/small-business/resource-center/networking/network-switch-vs-router.html
  9. https://community.cisco.com/t5/networking-knowledge-base/recognize-the-purpose-functions-of-various-network-devices/ta-p/3157636
  10. https://learningnetwork.cisco.com/s/blogs/a0D3i000002SKQdEAO/a-brief-history-of-network-virtualization
  11. https://hackaday.com/2024/08/27/decs-lan-bridge-100-the-invention-of-the-network-bridge/
  12. https://www.networkworld.com/article/723527/lan-wan-living-legends-ethernet-inventor-bob-metcalfe.html
  13. https://ipwatchdog.com/2016/02/04/spanning-tree-protocol-internet-routing/
  14. https://standards.ieee.org/beyond-standards/ethernet-50th-anniversary/
  15. https://adapture.com/why-cisco-is-an-industry-powerhouse/
  16. https://www.cse.wustl.edu/~jain/cis788-97/ftp/gigabit_ethernet/index.html
  17. https://www.cisco.com/c/en/us/td/docs/switches/connectedgrid/cg-switch-sw-master/software/configuration/guide/sysmgmt/CGS_1000_Sysmgmt/sm_snmp.html
  18. https://www.networkworld.com/article/731976/lan-wan-40-100g-ethernet-standard-ratified.html
  19. https://www.computerweekly.com/feature/The-history-of-OpenFlow
  20. https://www.datacenterfrontier.com/special-reports/article/11428810/edge-computing-and-why-it-matters-in-2020-and-beyond
  21. https://standards.ieee.org/ieee/802.3df/11244/
  22. https://www.ieee802.org/3/dj/
  23. https://www.ciscopress.com/articles/article.asp?p=3089352&seqNum=6
  24. https://www.cisco.com/c/en/us/support/docs/switches/catalyst-6500-series-switches/71079-arp-cam-tableissues.html
  25. https://community.cisco.com/t5/networking-knowledge-base/network-switching-operation/ta-p/4193160
  26. https://www.cisco.com/c/en/us/support/docs/switches/catalyst-6000-series-switches/23563-143.html
  27. https://www.cisco.com/c/en/us/td/docs/switches/datacenter/pf/configuration/guide/b-pf-configuration/Layer-2-Multicast-Forwarding.pdf
  28. https://www.ti.com/lit/pdf/spru941
  29. https://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus9000/sw/92x/Layer-2_switching/configuration/guide/b-cisco-nexus-9000-nx-os-layer-2-switching-configuration-guide-92x/b-cisco-nexus-9000-nx-os-layer-2-switching-configuration-guide-92x_chapter_01000.pdf
  30. https://www.ciscopress.com/articles/article.asp?p=3089352&seqNum=7
  31. https://networklessons.com/cisco/ccna-routing-switching-icnd1-100-105/collision-domains
  32. https://www.cisco.com/c/en/us/tech/lan-switching/spanning-tree-protocol/index.html
  33. https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst9200/software/release/16-12/configuration_guide/lyr2/b_1612_lyr2_9200_cg/configuring_spanning_tree_protocol.html
  34. https://standards.ieee.org/ieee/802.1D/3387/
  35. https://community.cisco.com/t5/networking-knowledge-base/overview-of-layer-2-switched-networks-and-communication/ta-p/3128423
  36. https://www.cisco.com/c/en/us/products/collateral/switches/catalyst-1000-series-switches/nb-06-cat1k-ser-switch-ds-cte-en.html
  37. https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst9300/software/release/16-5/configuration_guide/sec/b_165_sec_9300_cg/configuring_ipv4_acls.html
  38. https://standards.ieee.org/ieee/802.1Q/6844/
  39. https://grouper.ieee.org/groups/802/1/files/public/docs1997/tagging.pdf
  40. https://community.cisco.com/t5/switching/difference-between-transparent-bridge-and-a-switch/td-p/2716654
  41. https://www.cisco.com/c/en/us/products/collateral/switches/catalyst-micro-switches/cat-micro-switches-wp.html
  42. https://www.cisco.com/c/en/us/td/docs/solutions/CVD/Campus/cisco-campus-lan-wlan-design-guide.html
  43. https://biztechmagazine.com/article/2013/10/understanding-different-layers-routing-and-switching
  44. https://www.cisco.com/site/us/en/learn/topics/small-business/network-switch-how.html
  45. https://www.cisco.com/c/en/us/td/docs/cloud-systems-management/network-automation-and-management/dna-center/2-3-5/user_guide/b_cisco_dna_center_ug_2_3_5/m_onboard-and-provision-devices-with-plug-and-play.html
  46. https://www.cisco.com/c/en/us/products/collateral/switches/catalyst-9000/nb-06-cat-9k-stack-wp-cte-en.html
  47. https://www.cisco.com/site/us/en/products/networking/cloud-networking-switches/index.html
  48. https://www.cisco.com/site/us/en/products/networking/industrial-iot/index.html
  49. https://www.juniper.net/documentation/us/en/software/junos/bridging-learning/topics/task/layer-2-services-address-learning-and-forwarding-configuring-table-timeout-interval.html
  50. https://standards.ieee.org/ieee/802.1w/1046/
  51. https://standards.ieee.org/ieee/802.5m/1118/
  52. https://intronetworks.cs.luc.edu/current1/mob2/ethernet.html
  53. https://cs.slu.edu/~chambers/spring13/443/assignments/lab04.html
  54. https://www.cisco.com/c/en/us/products/collateral/switches/nexus-3550-series/datasheet-c78-743831.html
  55. https://www.cisco.com/site/us/en/learn/topics/small-business/what-are-the-different-types-of-network-switches.html
  56. https://www.cisco.com/site/us/en/learn/topics/networking/what-is-a-managed-switch.html
  57. https://blogs.cisco.com/smb/understanding-the-different-types-of-ethernet-switches
  58. https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst9400/software/release/16-6/configuration_guide/b_166_rtng_9400_cg/b_166_rtng_9400_cg_chapter_01.html
  59. https://community.cisco.com/t5/networking-knowledge-base/understanding-cisco-express-forwarding-cef-architecture/ta-p/5276856
  60. https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst2960xr/software/15-2_2_e/routing/configuration_guide/b_rt_1522e_2960xr_cg/b_rt_152ex1_2960-xr_cg_chapter_011.html
  61. http://www.blackbox.com/insights/blackbox-explains/inner/detail/networking/connectivity/layer-2-layer-3-and-layer-4-switches
  62. https://www.summit360.com/switch-layer-levels/
  63. https://opennetworking.org/wp-content/uploads/2014/10/openflow-spec-v1.4.0.pdf
  64. https://www.arista.com/assets/data/pdf/Datasheets/7300X_DS.pdf
  65. https://www.etherwan.com/us/products/ethernet-switches/commercial-unmanaged-ethernet-switches
  66. https://tripplite.eaton.com/products/network-switches-unmanaged~54-196
  67. https://www.fibermall.com/blog/5-port-ethernet-switch.htm
  68. https://www.cisco.com/c/dam/en/us/td/docs/switches/datacenter/nexus9000/hw/n9396_hig/guide/b_n9396_hardware_install_guide_appendix_0101.html
  69. https://www.tp-link.com/us/business-networking/soho-switch-unmanaged/tl-sg1024/
  70. https://www.supermicro.com/en/products/networking/switches
  71. https://www.moxa.com/en/products/industrial-network-infrastructure/ethernet-switches/rackmount-switches
  72. https://www.curvature.com/resources/ask-the-expert/what-is-the-difference-between-a-fixed-and-modular-switch-pt-1/
  73. https://prerackit.com/fixed-vs-modular-switches-which-is-the-right-choice-for-your-network/
  74. https://www.trendnet.com/store/products/front-access-switch/8-port-hardened-industrial-gigabit-poe-wall-mounted-front-access-switch-TI-PG80F-v2
  75. https://planetechusa.com/product/wgs-4215-8p2xv-industrial-l2-8-port-10-100-1000t-802-3at-poe-2-port-10g-sfp-wall-mount-managed-ethernet-switch-with-lcd-touch-screen/
  76. https://www.cisco.com/c/en/us/td/docs/solutions/Enterprise/Data_Center/DC_BladeServer/DCBladServ/BSrv_Ch1.html
  77. https://www.lenovo.com/us/en/glossary/blade/
  78. https://blogs.juniper.net/en-us/ai-native-networking/introducing-the-ultimate-ethernet-switch-for-extreme-conditions
  79. https://www.extremenetworks.com/products/switches/industrial-switches/isw-series
  80. https://www.cbtnuggets.com/blog/technology/networking/802-3at-vs-802-3af-which-poe-standard-to-use
  81. https://www.perle.com/supportfiles/poe_background_technical_note.shtml
  82. https://help.ui.com/hc/en-us/articles/115000263008-PoE-Availability-and-Modes
  83. https://www.juniper.net/documentation/us/en/software/junos/high-availability/topics/topic-map/redundant-power-system-understanding.html
  84. https://community.cisco.com/t5/switching/power-combined-or-redundant-on-9600/td-p/4283601
  85. https://maisvch.com/blog/power-redundancy-in-industrial-ethernet-switches-ensuring-uninterrupted-network-operations/
  86. https://www.techtarget.com/searchnetworking/answer/What-is-the-difference-between-a-managed-and-unmanaged-switch
  87. https://www.fieldengineer.com/blogs/network-switch-managed-vs-unmanaged
  88. https://www.blackbox.com/en-us/insights/blackbox-explains/inner/detail/networking/connectivity/the-difference-between-unmanaged-managed-and-web-smart-switches
  89. https://www.cisco.com/c/en/us/support/docs/switches/catalyst-6000-series-switches/10600-9.html
  90. https://networklessons.com/system-management/configure-ssh-cisco-ios
  91. https://www.cisco.com/c/en/us/support/docs/smb/switches/cisco-550x-series-stackable-managed-switches/1238-tz-log-into-the-gui-of-a-switch.html
  92. http://www.cisco.com/en/US/docs/switches/lan/catalyst3850/software/release/3.2_0_se/multibook/configuration_guide/b_consolidated_config_guide_3850_chapter_01101010.html
  93. https://www.cisco.com/c/en/us/support/docs/smb/switches/cisco-550x-series-stackable-managed-switches/smb5304-upgrade-firmware-on-a-switch.html
  94. https://www.cisco.com/c/en/us/support/docs/lan-switching/spanning-tree-protocol/24062-146.html
  95. https://www.cisco.com/c/en/us/support/docs/smb/switches/cisco-550x-series-stackable-managed-switches/smb5566-upgrade-firmware-on-a-switch-through-the-command-line-interf.html
  96. https://www.cisco.com/c/en/us/td/docs/dcn/nx-os/nexus9000/101x/configuration/system-management/cisco-nexus-9000-series-nx-os-system-management-configuration-guide-101x/m-configuring-rmon.html
  97. https://www.cisco.com/en/US/docs/storage/san_switches/mds9000/sw/rel_1_x/1_3/fm/configuration/guide/Logging.pdf
  98. http://www.cisco.com/en/US/docs/storage/san_switches/mds9000/sw/rel_3_x/configuration/guides/cli_3_3_1/cradtac1.html
  99. https://www.cisco.com/c/en/us/td/docs/iosxr/ncs5500/system-setup/79x/b-system-setup-cg-ncs5500-79x/m-secure-ztp.html
  100. https://www.cisco.com/c/en/us/products/collateral/switches/catalyst-9300-series-switches/catalyst-programmability-automation-wp.html
  101. https://obkio.com/blog/network-switch-monitoring/
  102. https://www.cisco.com/en/US/docs/switches/lan/catalyst3850/software/release/3.2_0_se/multibook/configuration_guide/b_consolidated_config_guide_3850_chapter_01101101.html
  103. https://community.cisco.com/t5/networking-knowledge-base/understanding-span-rspan-and-erspan/ta-p/3144951
  104. https://www.kentik.com/blog/what-is-port-mirroring-span-explained/
  105. https://www.cisco.com/c/en/us/support/docs/ip/simple-network-management-protocol-snmp/26007-faq-snmpcounter.html
  106. https://www.dnsstuff.com/switch-monitoring-management
  107. https://www.varonis.com/blog/flow-monitoring
  108. https://www.noction.com/blog/netflow-sflow-ipfix-netstream
  109. https://www.progress.com/flowmon/solutions/network-and-cloud-operations/netflow-ipfix
  110. https://www.cisco.com/c/en/us/support/docs/switches/catalyst-6500-series-switches/12027-53.html
  111. https://networklessons.com/cisco/ccnp-tshoot/cisco-ios-show-interface-explained
  112. https://obkio.com/blog/network-switch-issues/
  113. https://www.cisco.com/c/en/us/support/docs/lan-switching/spanning-tree-protocol/28943-170.html
  114. https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst9400/software/release/16-10/configuration_guide/sec/b_1610_sec_9400_cg/b_1610_sec_9400_cg_chapter_011100.pdf
  115. https://standards.ieee.org/ieee/802.1X/7345/
  116. https://www.cisco.com/c/en/us/td/docs/dcn/nx-os/nexus3548/103x/configuration/security/cisco-nexus-3548-nx-os-security-configuration-guide-103x/m-configuring-dhcp-snooping.pdf
  117. https://kb.netgear.com/21708/What-are-access-control-lists-ACLs-and-how-do-they-work-with-my-NETGEAR-Smart-Switch-or-fully-managed-switch
  118. https://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus3000/sw/layer2/503_U2_1/b_Cisco_n3k_layer2_config_guide_503_U2_1/b_Cisco_n3k_layer2_config_gd_503_U2_1_chapter_01111.pdf
  119. https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst3750x_3560x/software/release/15-2_2_e/configuration/guide/b_1522e_consolidated_3750x_3560X_cg/b_1522e_consolidated_3750x_3560X_cg_chapter_0110110.pdf
  120. https://www.cisco.com/c/en/us/support/docs/quality-of-service-qos/qos-packet-marking/10103-dscpvalues.html
  121. https://www.cisco.com/c/en/us/td/docs/ios/qos/configuration/guide/12_2sr/qos_12_2sr_book/config_wfq.html
  122. https://www.cisco.com/c/en/us/support/docs/quality-of-service-qos/qos-policing/19645-policevsshape.html
  123. https://community.cisco.com/t5/switching/router-with-cef-and-multilayer-switch-with-cef/td-p/1885742
  124. https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/ipswitch_cef/configuration/xe-16-10/isw-cef-xe-16-10-book/isw-cef-overview.html
  125. https://www.cisco.com/c/en/us/tech/multiprotocol-label-switching-mpls/multiprotocol-label-switching-vpns-mpls-vpns/index.html
  126. https://documentation.ipinfusion.com/ocnos-sp-mpls-6.6/Content/mpls/mpls-l3-vpn-configuration/mpls-l3-vpn-configuration.htm?TocPath=Multi-Protocol%2520Label%2520Switching%2520Configuration%257CMPLS%2520Layer-3%2520VPN%2520Configurations%257C_____0
  127. https://www.networkworld.com/article/3802351/next-gen-ethernet-standards-set-to-move-forward-in-2025.html
  128. https://www.anixter.com/content/dam/Suppliers/Belden/White%2520Papers/DataCentre-Fabrics-Explained_NovDec12-StandardsUpdate.pdf
  129. https://files.siemon.com/en/whitepaper/13-01-15-fat-tree-switch-fabric-architectures-in-the-data-center.pdf
  130. https://docs.nvidia.com/networking/display/MLNXOFEDv23070512/RDMA%2Bover%2BConverged%2BEthernet%2B%28RoCE%29
  131. https://www.roceinitiative.org/
  132. https://p4.org/
  133. https://www.cs.princeton.edu/~jrex/papers/P4-ccr14.pdf
  134. https://opennetworking.org/onos/
  135. https://www.lightreading.com/data-centers/onos-onf-create-integrated-nfv-approach
  136. https://planetechusa.com/product/isw-800t-m12-ip67-rated-m12-industrial-fast-ethernet-switch-8-port-10-100base-tx-40-75c/?srsltid=AfmBOoqD98EPv-SYbsSx_bZuSgfnwrnxHrec5AzKvk2woKLlfw2xzKjS
  137. https://www.cisco.com/site/us/en/products/networking/industrial-switches/index.html
  138. https://1.ieee802.org/tsn/
  139. https://www.keysight.com/us/en/use-cases/internet-of-things-iot/industrial/industrial-iot-tsn.html
  140. https://www.cisco.com/site/us/en/products/networking/switches/catalyst-9200-series-switches/index.html
  141. https://support.huawei.com/enterprise/en/doc/EDOC1100368571/780811d7/solution-overview
Add your contribution
Related Hubs
User Avatar
No comments yet.