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

A multilayer switch (MLS) is a computer networking device that switches on OSI layer 2 like an ordinary network switch and provides extra functions on higher OSI layers. The MLS was invented[1] by engineers at Digital Equipment Corporation.

Switching technologies are crucial to network design, as they allow traffic to be sent only where it is needed in most cases, using fast, hardware-based methods. Switching uses different kinds of network switches. A standard switch is known as a layer-2 switch and is commonly found in nearly any LAN. Layer-3 or layer-4 switches require advanced technology (see managed switch) and are more expensive and thus are usually only found in larger LANs or in special network environments.

Multilayer switch

[edit]

Multi-layer switching combines layer-2, -3 and -4 switching technologies and provides high-speed scalability with low latency. Multi-layer switching can move traffic at wire speed and also provide layer-3 routing. There is no performance difference between forwarding at different layers because the routing and switching are all hardware-based – routing decisions are made by specialized application-specific integrated circuits (ASICs) with the help of content-addressable memory.[2]

Multi-layer switching can make routing and switching decisions based on the following

  • MAC address in a data link frame
  • Protocol field in the data link frame
  • IP address in the network layer header
  • Protocol field in the network layer header
  • Port numbers in the transport layer header

MLSs implement QoS in hardware. A multilayer switch can prioritize packets by the 6 bit differentiated services code point (DSCP). These 6 bits were originally used for type of service. The following 4 mappings are normally available in an MLS:[citation needed]

  • From OSI layer 2, 3 or 4 to IP DSCP (for IP packets) or IEEE 802.1p
  • From IEEE 802.1p to IP DSCP
  • From IP DSCP to IEEE 802.1p
  • From VLAN IEEE 802.1p to port egress queue.

MLSs are also able to route IP traffic between VLANs like a common router. The routing is normally as quick as switching (at wire speed).

Layer-2 switching

[edit]

Layer-2 switching uses the MAC addresses of the hosts’ network interface controllers (NICs) to decide where to forward frames. Layer-2 switching is hardware-based, which means switches use ASICs to build and maintain the forwarding information base and to perform packet forwarding at wire speed. One way to think of a layer-2 switch is as a multiport bridge.

Layer-2 switching is highly efficient because there is no modification to the frame required. Encapsulation of the packet changes only when the data packet passes through dissimilar media (such as from Ethernet to FDDI). Layer-2 switching is used for workgroup connectivity and network segmentation (breaking up collision domains). This allows a flatter network design with more network segments than conventional networks joined by repeater hubs and routers.

Layer-2 switches have the same limitations as bridges. Bridges break up collision domains, but the network remains one large broadcast domain which can cause performance issues and limits the size of a network. Broadcast and multicasts, along with the slow convergence of spanning tree, can cause major problems as the network grows. Because of these problems, layer-2 switches cannot completely replace routers. Bridges are good if a network is designed by the 80/20 rule: users spend 80 percent of their time on their local segment.[citation needed]

Layer-3 switching

[edit]

A layer-3 switch can perform some or all of the functions normally performed by a router. Most network switches, however, are limited to supporting a single type of physical network, typically Ethernet, whereas a router may support different kinds of physical networks on different ports.

Layer-3 switching is solely based on the (destination) IP address stored in the header of an IP datagram (layer-4 switching may use other information in the header). The difference between a layer-3 switch and a router is the way the device is making the routing decision. Conventionally, routers use microprocessors to make forwarding decisions in software, while the switch performs only hardware-based packet switching (by specialized ASICs with the help of content-addressable memory).[2][3] However, many routers now also have advanced hardware functions to assist with forwarding.

The main advantage of layer-3 switches is the potential for lower network latency as a packet can be routed without making extra network hops to a router. For example, connecting two distinct segments (e.g. VLANs) with a router to a standard layer-2 switch requires passing the frame to the switch (first L2 hop), then to the router (second L2 hop) where the packet inside the frame is routed (L3 hop) and then passed back to the switch (third L2 hop). A layer-3 switch accomplishes the same task without the need for a router (and therefore additional hops) by making the routing decision itself, i.e. the packet is routed to another subnet and switched to the destination network port simultaneously.

Because many layer-3 switches offer the same functionality as conventional routers they can be used as cheaper, lower latency replacements in some networks. Layer-3 switches can perform the following actions that can also be performed by routers:

The benefits of layer-3 switching include the following:

  • fast hardware-based packet forwarding with low latency
  • lower per-port cost compared to pure routers
  • flow accounting
  • Quality of service (QoS)

IEEE[citation needed] has developed hierarchical terminology that is useful in describing forwarding and switching processes. Network devices without the capability to forward packets between subnetworks are called end systems (ESs, singular ES), whereas network devices with these capabilities are called intermediate systems (ISs). ISs are further divided into those that communicate only within their routing domain (intradomain IS) and those that communicate both within and between routing domains (interdomains IS). A routing domain is generally considered as a portion of an internetwork under common administrative authority and is regulated by a particular set of administrative guidelines. Routing domains are also called autonomous systems.

A common layer-3 capability is an awareness of IP multicast through IGMP snooping. With this awareness, a layer-3 switch can increase efficiency by delivering the traffic of a multicast group only to ports where the attached device has signaled that it wants to listen to that group.

Layer-3 switches typically support IP routing between VLANs configured on the switch. Some layer-3 switches support the routing protocols that routers use to exchange information about routes between networks.

Layer-4 switching

[edit]

Layer-4 switching means hardware-based layer-3 switching technology that can also consider the type of network traffic (for example, distinguishing between UDP and TCP). Layer-4 switching provides additional datagram inspection by reading the port numbers found in the transport layer header to make routing decisions (i.e. ports used by HTTP, FTP and VoIP). These port numbers are found in RFC 1700 and reference the upper-layer protocol, program, or application.

Using layer-4 switching, the network administrator can configure a layer-4 switch to prioritize data traffic by application. Layer-4 information can also be used to help make routing decisions. For example, extended access lists can filter packets based on layer-4 port numbers. Another example is accounting information gathered by open standards using sFlow.

A layer-4 switch can use information in the transport-layer protocols to make forwarding decisions. Principally this refers to an ability to use source and destination port numbers in TCP and UDP communications to allow, block and prioritize communications.[4]

Layer 4–7 switch, web switch, or content switch

[edit]

Some switches can use packet information up to OSI layer 7; these may be called layer 4–7 switches, content switches, content services switches, web switches or application switches.

Content switches are typically used for load balancing among groups of servers. Load balancing can be performed on HTTP, HTTPS, VPN, or any TCP/IP traffic using a specific port. Load balancing often involves destination network address translation so that the client of the load-balanced service is not fully aware of which server is handling its requests. Some layer 4–7 switches can perform Network address translation (NAT) at wire speed. Content switches can often be used to perform standard operations such as SSL encryption and decryption to reduce the load on the servers receiving the traffic, or to centralize the management of digital certificates. Layer-7 switching is a technology used in a content delivery network (CDN).

Some applications require that repeated requests from a client are directed at the same application server. Since the client isn't generally aware of which server it spoke to earlier, content switches define a notion of stickiness. For example, requests from the same source IP address are directed to the same application server each time. Stickiness can also be based on SSL IDs, and some content switches can use cookies to provide this functionality.

Layer-4 load balancer

[edit]

The router operates on the transport layer and makes decisions on where to send the packets. Modern load balancing routers can use different rules to make decisions on where to route traffic. This can be based on least load, or fastest response times, or simply balancing requests out to multiple destinations providing the same services. This is also a redundancy method, so if one machine is not up, the router will not send traffic to it.

The router may also have NAT capability with port and transaction awareness and performs a form of port translation for sending incoming packets to one or more machines that are hidden behind a single IP address.

Layer 7

[edit]

Layer-7 switches may distribute the load based on uniform resource locators (URLs), or by using some installation-specific technique to recognize application-level transactions. A layer-7 switch may include a web cache and participate in a content-distribution network (CDN).[5][failed verification]

See also

[edit]

References

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

Multilayer switch

View on Grokipedia
from Grokipedia
A multilayer switch, also known as a Layer 3 switch, is a high-performance network device that integrates the functionalities of both a Layer 2 switch and a router, operating across multiple layers of the to enable efficient data forwarding based on MAC addresses at the and IP addresses at the network layer. This hybrid capability allows it to perform intra-VLAN switching at wire speeds while handling inter-VLAN and IP packet forwarding between subnets, offloading traditional routers to reduce latency and bottlenecks in enterprise networks. Unlike pure Layer 2 switches, which forward frames solely using MAC addresses within the same , multilayer switches examine packet headers at Layer 3 (and sometimes Layer 4 for advanced features like ) to make decisions, supporting protocols such as IP, as well as traffic management. They typically feature numerous Ethernet ports (often 24 or more) without WAN interfaces, making them ideal for LAN environments, and leverage hardware-based application-specific integrated circuits () for near-wire-speed processing of routed traffic. Introduced in the to address the growing complexity of enterprise networks with extensive and subnetting needs, multilayer switches evolved from early technologies like Cisco's Multilayer Switching (MLS), which provided Ethernet-based Layer 3 switching in conjunction with existing . Key benefits include enhanced scalability for data centers, policy-based enforcement for security and traffic prioritization, and cost-effective upgrades that minimize the need for separate hardware. In modern deployments, they facilitate inter- routing via Switched Virtual Interfaces (SVIs) and support advanced features like access control lists (ACLs) and subnet segmentation, making them essential in segmented networks, particularly where individual exceed 250 devices.

Overview

Definition and Principles

A multilayer switch is a hybrid network device that combines the capabilities of traditional switches and routers, operating across multiple layers of the Open Systems Interconnection (OSI) model—primarily Layers 2 through 4, and sometimes higher. At Layer 2, it forwards packets based on Media Access Control (MAC) addresses for efficient local network communication; at Layer 3, it routes using Internet Protocol (IP) addresses to enable inter-subnet traffic; and at Layer 4 or above, it can inspect transport-layer information such as port numbers or application data for more granular decision-making. This multi-layer operation sets it apart from single-layer devices, such as basic Layer 2 switches limited to MAC-based forwarding or dedicated routers focused on Layer 3 processing. The foundational principles of multilayer switching emphasize hardware-accelerated forwarding to achieve wire-speed performance, typically through Application-Specific Integrated Circuits (ASICs) that handle packet processing without relying on (CPU) intervention for each frame. These devices integrate switching fabrics—high-speed interconnects for data exchange—with dynamic routing tables, enabling rapid lookups and modifications like header rewrites during transit. Support for Virtual Local Area Networks (VLANs) further enhances segmentation, allowing logical isolation of broadcast domains across physical ports to improve and in shared environments. Evolving from 1990s Ethernet switches, this architecture addresses the limitations of software-based systems by offloading repetitive tasks to dedicated hardware. Multilayer switches integrate OSI layers by bridging the 2), 3), and 4) functionalities in a unified hardware platform, performing both bridging and without the full overhead of traditional software routers that process each packet sequentially in the CPU. This approach minimizes latency and maximizes throughput by pre-populating forwarding tables for instant decisions. At a high level, the device separates the —responsible for management functions like protocol exchanges and table updates—from the data plane, which executes the actual forwarding in , ensuring scalable operation in demanding networks.

Historical Development

The development of multilayer switches originated in the early , evolving from basic LAN switches to handle escalating and the introduction of Virtual LANs (VLANs) for . Cisco Systems played a pivotal role through its acquisition of Crescendo Communications in 1993, leading to the Catalyst 5000 series, which initially provided high-performance Layer 2 switching as a foundational precursor to multilayer functionality. These early innovations addressed the limitations of shared Ethernet hubs by enabling dedicated bandwidth per port, setting the stage for integrated higher-layer processing. In the mid-1990s, multilayer switching advanced significantly with the introduction of Layer 3 capabilities, allowing directly in hardware for faster performance than traditional software-based routers. This shift was propelled by the widespread adoption of switched Ethernet networks over shared media, reducing latency and improving in enterprise environments. Cisco's 1996 launch of Tag Switching technology exemplified this milestone, fusing routing and switching to support scalable backbones amid booming usage. The 2000s saw further integration of Layer 4-7 features into multilayer switches, enabling advanced management such as load balancing and SSL offloading. This evolution aligned with the rapid expansion of data centers and the surge, where devices needed to inspect and direct application-layer traffic efficiently. Cisco's Application Control Engine () module, introduced in 2007, provided up to 16 Gbps of Layer 4-7 throughput in a single appliance, enhancing and for growing online services. From the 2010s onward, multilayer switches incorporated (SDN) compatibility for programmable control and supported speeds up to 10/40/100 Gbps to meet hyperscale demands. In the 2020s, trends have shifted toward AI-optimized switching tailored for , with Cisco's Unified Edge platform—announced in November 2025—delivering integrated networking, compute, and storage for distributed AI workloads at remote sites. Throughout this history, primary drivers have included surging bandwidth needs from video streaming and , which diminished dependence on standalone routers by consolidating functions into versatile switches.

Layer 2 Functionality

Core Mechanisms

Multilayer switches perform core Layer 2 operations to handle Ethernet frames efficiently within local network segments, ensuring low-latency delivery and scalability in switched environments. These mechanisms include dynamic address learning, intelligent forwarding decisions, loop prevention, traffic segmentation, and collision management, all of which optimize intra-VLAN communication without relying on higher-layer protocols. MAC address learning is a fundamental process in multilayer switches, utilizing Content Addressable Memory (CAM) tables to map source es to specific ingress ports dynamically. Upon receiving a frame, the switch inspects the source and either adds it to the CAM table with the associated port and or updates an existing entry, enabling subsequent unicast forwarding. If the destination is absent from the table, the switch floods the frame to all other ports in the same to discover the recipient, preventing while minimizing unnecessary traffic through learned mappings. To prevent table bloat from stale entries, an aging timer removes inactive MAC-port associations, with a common default of 300 seconds configurable based on network dynamics. Frame forwarding mechanisms in multilayer switches balance speed and reliability through store-and-forward or cut-through modes. In store-and-forward mode, the switch buffers the complete frame, computes the (CRC) to detect transmission errors, and only forwards valid frames to the egress port determined by the CAM table lookup, ensuring error-free delivery at the cost of added latency. Conversely, cut-through mode initiates forwarding immediately after identifying the destination —typically within the first 6 bytes of the frame—bypassing full buffering and CRC validation to minimize delay, though it risks propagating corrupted frames if errors occur later in the packet. Integration of the (STP), standardized in , prevents broadcast storms and loops in redundant Layer 2 topologies by algorithmically selecting a root bridge and designating forwarding/blocking states for ports across the network. STP exchanges Bridge Protocol Data Units (BPDUs) to build a loop-free logical topology, blocking redundant links while maintaining path redundancy for . Enhancements in Rapid Spanning Tree Protocol (RSTP), defined by IEEE 802.1w, accelerate convergence from STP's potential 30-50 seconds to under 6 seconds by introducing rapid port transitions (e.g., from discarding to forwarding) and proactive topology change notifications, making it suitable for dynamic environments. VLAN tagging via the protocol supports trunking and segmentation by embedding a 4-byte tag—including a 12-bit VLAN Identifier (VID)—into Ethernet frames on trunk ports, allowing a single physical link to multiplex traffic from multiple virtual LANs. This isolation confines broadcasts, multicasts, and unknown unicasts to their respective s, reducing domain size and enhancing security without requiring separate hardware. Access ports handle untagged frames assigned to a default , while trunks preserve tags for inter-switch communication, enabling scalable control. Collision domain reduction is achieved through full-duplex operation in multilayer switches, which supports bidirectional communication on dedicated transmit and receive paths, eliminating shared media contention and the associated (CSMA/CD) mechanism from half-duplex Ethernet. Each port functions as an independent , allowing simultaneous full-speed transmission without backoff delays or retries, thereby doubling effective bandwidth and improving in local networks. These Layer 2 core mechanisms underpin the efficiency of multilayer switches by providing robust frame handling that seamlessly integrates with higher-layer routing for inter-VLAN traffic.

Role in Multilayer Environments

In multilayer switches, Layer 2 functionality serves as the foundational entry point for incoming packets, performing initial forwarding decisions based on MAC addresses within VLANs before handing off to Layer 3 for inter-subnet traffic. This bridging process leverages , such as application-specific integrated circuits (), to map VLANs to corresponding subnets efficiently, enabling wire-speed inter-VLAN routing without software intervention. For instance, in switches, the integrated switching engine handles VLAN-to-subnet transitions in hardware, minimizing latency in hybrid environments. Layer 2 also supports (QoS) mechanisms that prepare traffic for higher-layer processing, using (CoS) bits in the 802.1Q headers to prioritize frames based on their urgency. These three-bit CoS values, defined in IEEE 802.1p, allow switches to classify and shape traffic at the ingress stage—such as queuing voice packets ahead of —ensuring that persists through the Layer 3 handoff and avoids congestion in paths. In multilayer implementations like IOS-based switches, CoS markings are trusted and mapped to internal queues for shaping before , enhancing overall network efficiency. For multicast traffic, Layer 2 features like ( optimize distribution by listening to IGMP messages and building a table of interested receivers, thereby forwarding group communications only to relevant ports rather than flooding the entire domain. This prevents bandwidth waste in multilayer setups, where streams might otherwise overwhelm Layer 3 routers, and is supported in hardware on platforms like series for low-latency processing. IGMP snooping integrates seamlessly with Layer 3 multicast routing protocols, allowing the switch to constrain Layer 2 floods while enabling efficient upstream queries to routers. To enhance scalability across multiple devices, stacking protocols such as StackWise create a unified Layer 2 domain by interconnecting switches into a single logical unit with high-bandwidth backplanes, up to 1 Tbps in recent models, allowing seamless learning and spanning without STP loops. This architecture presents the stack as one switch to the network, supporting hybrid Layer 2/3 operations and simplifying management in large campus deployments. StackWise ensures consistent Layer 2 behavior across members, facilitating load balancing and redundancy for traffic destined for Layer 3 processing. In campus networks, Layer 2 ensures a bottleneck-free handoff to Layer 3 by confining broadcast domains to access layers while using routed links at distribution, as in the Layer 2 access with Layer 3 distribution model, which avoids extending VLANs excessively and leverages multilayer switches for fast IP forwarding. This design maintains high throughput, with Layer 2 handling local segmentation via VLANs that map directly to Layer 3 subnets, promoting efficient traffic flow without performance degradation. Basic MAC learning, as performed at Layer 2, underpins this by populating forwarding tables for quick initial lookups before escalation to .

Layer 3 Functionality

Routing Capabilities

Multilayer switches perform IP routing at Layer 3 using hardware-based forwarding mechanisms, such as on platforms, which optimizes packet processing by precomputing forwarding decisions. CEF relies on two key components: the (FIB), a derived copy of the table that maps destination prefixes to next-hop interfaces, and adjacency tables that cache Layer 2 rewrite information, such as MAC addresses, for efficient adjacency caching and reduced CPU involvement in data plane operations. This architecture enables multilayer switches to forward packets at line rate without software intervention for each packet, distinguishing them from traditional routers that rely on process switching. These switches support a range of protocols to build and maintain the in the , including static routes for manual configuration, as well as dynamic protocols such as (RIP) for distance-vector , (OSPF) for link-state path computation, (EIGRP) for hybrid metric-based decisions, and (BGP) for inter-domain . For , support includes protocols like OSPFv3, RIPng, and BGP. Dynamic protocols allow for automatic route updates and convergence in response to network changes, with the processing protocol messages to populate the , which is then synchronized to the FIB for data plane use. Protocol support varies by switch model and software image, such as IP Services enabling full EIGRP and BGP capabilities on platforms. Inter-VLAN routing is facilitated through Switched Virtual Interfaces (SVIs), which serve as Layer 3 gateways assigned to specific , allowing traffic from one —configured as described in Layer 2 functionality—to reach another without external devices. An SVI is created by associating an with a interface on the switch, enabling it to act as the for hosts in that and perform decisions based on the FIB. This integrated approach consolidates switching and , reducing latency for intra-switch communications. SVIs also support addressing and . For security, multilayer switches apply IP-based Access Control Lists (ACLs) to filter traffic at Layer 3, enforcing policies such as permit or deny rules on routed packets processed at wire speed via hardware. ACLs can include options to record matches for auditing, capturing details like source/destination IP and timestamps without impacting forwarding performance, as the rules are compiled into the switch's forwarding engine. ARP resolution integrates Layer 2 and Layer 3 operations, where the switch uses the to map IP addresses to MAC addresses for next-hop resolution, maintaining an ARP cache derived from the adjacency tables in CEF. This ensures efficient packet encapsulation during forwarding. Additionally, allows the switch to respond on behalf of remote hosts in the same , facilitating communication across subnets without host reconfiguration, particularly useful in environments.

Performance Enhancements

Multilayer switches achieve high-speed Layer 3 routing primarily through application-specific integrated circuits () that perform fixed-form in hardware, contrasting with the CPU-based software processing in traditional routers. This enables wire-speed forwarding, with modern models capable of processing up to 72 million packets per second (Mpps) for . For instance, the 4948 supports Layer 3 hardware-based Express Forwarding (CEF) routing at this rate without performance degradation from advanced services. Route caching in multilayer switches has evolved from early process switching, where each packet underwent CPU-intensive routing table lookups, to fast switching that caches forwarding decisions after the first packet in a flow. Subsequent advancements introduced topology-independent fast forwarding via CEF, which uses a prebuilt forwarding information base (FIB) and adjacency table to eliminate frequent cache invalidations and reduce dependency on per-flow caches like those in NetFlow switching. Post-2000s implementations further optimized this by minimizing NetFlow table sizes through adjacency-based lookups, enhancing scalability for dynamic environments. To manage large routing tables, multilayer switches employ hierarchical routing protocols such as OSPF and BGP, which support route summarization to aggregate multiple routes into fewer entries, thereby reducing table bloat and improving lookup efficiency. Modern models, like the Cisco Catalyst 6500 series with Sup3BXL supervisor, can scale to up to 1 million IPv4 routes in the while leveraging TCAM for high-speed FIB access. Similar scalability applies to routes in contemporary hardware. Redundancy in Layer 3 operations is provided by protocols like (HSRP) and (VRRP), which enable by sharing a across multiple switches. These protocols support sub-second convergence when timers are tuned (e.g., hello intervals below 1 second), allowing rapid active router election and minimal downtime during failures. Traffic engineering capabilities in multilayer switches include (PBR), which manipulates packet paths based on criteria such as source or destination IP addresses, overriding standard destination-based forwarding. PBR is implemented in hardware on supported platforms, ensuring low-latency path selection for optimized bandwidth utilization without impacting overall .

Layer 4-7 Functionality

Transport Layer Operations

Multilayer switches extend their Layer 3 routing capabilities by incorporating (Layer 4) operations, enabling decisions based on TCP and UDP port numbers to direct traffic more granularly than IP addressing alone. This functionality builds on as a prerequisite, allowing the switch to inspect packet headers for port information after initial routing determinations. For instance, traffic destined for HTTP services on port 80 or FTP on port 21 can be switched to specific server groups or paths optimized for those protocols. Layer 4 Access Control Lists (ACLs) provide extended filtering capabilities in multilayer switches, permitting or denying traffic based on TCP/UDP ports and TCP flags for enhanced and stateful . These ACLs support operators like "eq" for exact port matches (e.g., port 80), "neq" for exclusions, and "range" for contiguous ports, allowing up to 10 ports per access control entry to efficiently manage rules without excessive entries. Additionally, TCP flag matching enables detection of specific states, such as permitting packets where and ACK flags are set (+syn +ack) but is not (-fin), which aids in identifying connection establishment phases for firewall-like behavior. Basic load balancing at Layer 4 distributes incoming connections across multiple servers using algorithms that consider transport protocol details, improving availability and performance in environments. Methods include weighted round-robin, which cyclically assigns connections based on server capacity weights, and weighted least-connections, which directs traffic to the server with the fewest active connections, often computed via Layer 4 hashes incorporating source/destination IP and port numbers. For example, HTTP traffic on port 80 can be hashed and balanced to ensure even distribution without inspecting application data. Network Address Translation (NAT) and Port Address Translation (PAT) integrate seamlessly with Layer 4 operations in multilayer switches to conserve IPv4 addresses in routed networks, translating both IP addresses and port numbers as needed. In server NAT mode, the switch modifies destination IPs and ports for incoming packets to real server addresses, while client NAT handles return traffic; PAT specifically reuses ports (e.g., for TCP/UDP) to map multiple internal hosts to a single external IP. This is particularly useful in environments where Layer 3 routing feeds into Layer 4 port-aware translations, such as directing FTP sessions on port 21 through translated endpoints. Session persistence, or "sticky sessions," ensures that subsequent packets from the same client flow maintain affinity to the initially selected server, using Layer 4 attributes like source IP and for hashing. This prevents disruptions in stateful applications, such as keeping an HTTP session on port 80 and a related session on port 443 routed to the same backend server. In multilayer switches, this persistence is configured alongside load balancing to balance with connection continuity.

Application Layer Switching

Application layer switching in multilayer switches extends beyond basic transport-layer operations by performing deep packet inspection at OSI Layer 7, enabling decisions based on application-specific data such as HTTP headers, URLs, and to direct traffic intelligently. This content switching capability allows the switch to route requests to appropriate backend servers—for instance, directing traffic for "/images" paths to a dedicated image server while sending "/videos" requests to a video-optimized cluster—optimizing resource utilization and response times in data centers. Unlike port-based switching at Layer 4, this approach ensures application-aware load distribution without relying solely on TCP/UDP ports. SSL/TLS offload is a key feature in multilayer switches, where the device handles the computationally intensive decryption and encryption of secure traffic in hardware, relieving application servers from this burden and allowing them to focus on content processing. For example, in Cisco's Application Control Engine (), SSL termination occurs at the switch level, enabling subsequent Layer 7 inspection of decrypted payloads for policy enforcement while maintaining end-to-end security through re-encryption to servers. This offloading can significantly reduce server CPU usage for SSL-intensive applications, improving overall . Layer 7 load balancing in multilayer switches employs sophisticated algorithms to distribute traffic based on application context, including weighted round-robin for prioritizing server capacity and dynamic health checks via HTTP probes to monitor server availability and remove unhealthy nodes automatically. These mechanisms ensure ; for instance, F5 BIG-IP systems use content-based persistence to maintain session affinity via , preventing disruptions in stateful applications like sessions. Health probes might involve sending periodic GET requests to check response codes, rerouting traffic if a server returns errors like 500, thus maintaining service levels without manual intervention. Web caching and compression features integrated into multilayer switches reduce bandwidth consumption by storing frequently requested content locally and applying algorithms like to shrink data payloads before transmission. In F5 BIG-IP deployments, dynamic caching stores HTTP responses on the switch, serving subsequent identical requests from cache to cut latency, while compression profiles automatically detect and apply reductions achieving up to 75% bandwidth savings for text-heavy . ACE similarly supports inline compression, transparently compressing eligible content without application modifications, enhancing performance in bandwidth-constrained environments. Application firewalls within multilayer switches provide Layer 7 security through signature-based detection, scanning payloads for threats such as or by matching against predefined patterns in HTTP requests. For example, ACE modules include security policies that block malicious inputs by inspecting URI parameters and POST data, preventing exploits from reaching backend servers while allowing legitimate traffic. These firewalls operate inline, enforcing rules at wire speed to mitigate application-layer attacks without compromising .

Architecture and Implementation

Hardware Design

Multilayer switches employ advanced switching fabrics to enable high-speed, non-blocking data forwarding across multiple layers. Common architectures include crossbar switches, which provide direct any-to-any connectivity between ports without contention, and designs that allocate a central pool of for packet storage and retrieval. These fabrics ensure non-blocking throughput, allowing full line-rate even under full load; for instance, modern implementations support up to 800 Gbps per port in environments as of 2025. At the core of multilayer switch hardware are application-specific integrated circuits () and network processing units (NPUs), optimized for efficient Layer 2 and Layer 3 forwarding. ASICs handle deterministic, high-volume packet processing for basic switching and routing functions, while NPUs introduce programmability for higher-layer operations, such as Layer 4+ features including access control lists and . Modern designs increasingly incorporate programmable data planes, such as those supporting the P4 language, enabling custom forwarding behaviors. Additionally, AI/ML integration for real-time traffic prediction enhances buffer allocation and QoS as of 2025. Cisco's Unified Access Data Plane (UADP) ASICs, for example, integrate these capabilities in a single chip, supporting up to 240 Gbps of throughput with programmable elements for flexible protocol handling. Port configurations in multilayer switches typically feature modular chassis designs to accommodate varying deployment scales, ranging from compact 1U fixed-form factors for access layers to larger 10U-12U for core aggregation. These support pluggable transceivers like SFP for 1-10 Gbps and QSFP for 40-100 Gbps connections, enabling flexible media types such as or . The 6500 series, for instance, uses a 12U with hot-swappable line cards for up to hundreds of ports. Power and cooling systems are engineered for reliability and efficiency, with many multilayer switches incorporating (PoE) to deliver up to 100 W per port for powering endpoints like IP phones or cameras directly through Ethernet cables. Redundant power supply units (PSUs) provide 1+1 , ensuring by automatically switching to a backup during failures, while variable-speed fans manage thermal loads to minimize noise and energy use. Cisco Catalyst 3850 series switches exemplify this with dual hot-swappable PSUs supporting PoE budgets exceeding 700W. Buffer management is crucial for handling transient congestion, utilizing deep packet buffers—often in the range of tens of megabytes per port—to absorb microbursts, which are short-duration traffic spikes that can exceed link capacity. This architecture prevents packet drops by queuing excess data temporarily, with shared or per-port allocation schemes dynamically adjusting based on traffic patterns. In Nexus 3550 switches, a multilayered buffer offers robust protection against correlated microbursts in high-radix environments.

Software and Configuration

Multilayer switches rely on specialized operating systems to manage their advanced routing and switching capabilities. Cisco IOS and IOS XE serve as primary operating systems for many multilayer switches, providing a modular architecture that supports layer 3 and higher functionalities through feature-rich environments optimized for enterprise networking. Juniper Junos OS offers a consistent platform across devices, enabling unified management of routing, switching, and security features with a single codebase that reduces operational complexity. Both systems employ modular licensing models, where advanced features such as enhanced routing protocols or quality of service are activated via software licenses, allowing administrators to scale capabilities without hardware changes. Configuration of multilayer switches occurs through multiple interfaces to accommodate diverse administrative needs. The command-line interface (CLI) remains the most precise method, using hierarchical modes for operational monitoring and detailed configuration changes, such as enabling inter- routing or lists. Graphical user interfaces (GUIs), including web-based options like Cisco's Web UI or Juniper's J-Web, provide intuitive dashboards for initial setup, management, and basic monitoring without requiring deep CLI expertise. For , application programming interfaces (APIs) such as RESTCONF enable programmatic access to configuration data using HTTP-based methods, facilitating integration with tools for dynamic network adjustments. Management protocols ensure effective monitoring and maintenance of multilayer switches in production environments. (SNMP) is widely used for polling device status, interface statistics, and performance metrics, with versions 2c and 3 providing community-based or authenticated access respectively. protocol facilitates event logging by forwarding system messages, errors, and alerts to centralized servers for analysis, configurable at various severity levels to capture critical network events like link failures or policy violations. supports structured configuration changes and retrieval using XML-based remote procedure calls over SSH, enabling automated provisioning and compliance checks in large-scale deployments. Firmware updates for multilayer switches follow a structured process to incorporate enhancements like software-defined networking (SDN) integration and security improvements. Administrators typically download verified images from vendor portals, back up current configurations, and perform the upgrade via CLI commands, such as Cisco's "install add file" for IOS XE in install mode, which stages and activates the new software with minimal downtime through redundancy checks. Juniper's process involves using "request system software add" to validate and install Junos packages, often requiring a reboot to apply changes while preserving active sessions where possible. Post-2020 updates have increasingly included zero-trust integrations, such as enhanced identity verification and micro-segmentation features in Cisco IOS XE releases, aligning with NIST SP 800-207 guidelines for continuous authentication in network access. These upgrades also address SDN support by adding protocols like OpenFlow or NETCONF extensions for controller-based orchestration. Troubleshooting on multilayer switches leverages built-in diagnostics for rapid issue resolution. CLI "show" commands, such as "show ip route" or "show interfaces," display real-time forwarding tables, error counters, and protocol states to identify misconfigurations or congestion. Packet capture tools enable on-device ; Cisco's Embedded Packet Capture (EPC) defines filters and buffers to record packets matching criteria like IP addresses or ports, exporting them as PCAP files for external tools like . Juniper's "monitor traffic" or "request packet-capture" commands similarly filter and store live traffic for debugging issues or ACL drops, supporting both real-time viewing and file export. These tools, integrated into the switch hardware platform, allow non-disruptive diagnostics without external probes.

Applications and Comparisons

Network Deployment Scenarios

In enterprise and campus local area networks (LANs), multilayer switches are deployed in a hierarchical consisting of access, distribution, and core layers to manage aggregation and efficiently. At the access layer, switches such as the 9200 and 9300 Series connect end-user devices and access points, providing high-bandwidth interfaces like Multigigabit Ethernet to support dense user environments. The distribution layer, utilizing models like the Catalyst 9500 or 9400 Series, aggregates from multiple access switches via 10 Gbps to 100 Gbps uplinks and enforces policies including (QoS), security segmentation through TrustSec, and , thereby reducing latency and enhancing network resilience with features like StackWise Virtual for . In larger campuses, the core layer employs high-density switches such as the Catalyst 9600 Series to interconnect distribution blocks, ensuring low-oversubscription ratios (e.g., 3.6:1 at access) and fast convergence for scalable operations across buildings or sites. This deployment model benefits organizations by simplifying , improving through non-stop forwarding (NSF), and supporting growth without overhauling the infrastructure. In environments, multilayer switches serve as top-of-rack (ToR) devices to handle high-throughput and overlay networking demands. Switches like the 3100-V Series, in a compact 1RU form factor, deliver line-rate Layer 2 and Layer 3 switching at up to 2.56 Tbps throughput and 1.4 billion packets per second, ideal for connecting servers in virtualized setups. They support VXLAN encapsulation with BGP EVPN for scalable , enabling seamless host mobility and across thousands of virtual machines without performance bottlenecks. This configuration allows data centers to achieve low-latency forwarding and efficient resource utilization, with features like 16,000 (ACL) entries and shared buffering to manage bursty traffic from cloud-native applications. By integrating tools such as Power-on Auto Provisioning (POAP), these deployments facilitate rapid scaling in environments supporting enterprise applications and service provider hosting. At service provider network edges, multilayer switches integrate MPLS protocols to enable virtual private networks (VPNs) and traffic engineering for optimized connectivity. Provider edge (PE) devices, such as Cisco Catalyst 3850 Series switches, combine Layer 2 switching with Layer 3 routing using MPLS labels for high-performance packet forwarding across core networks, supporting inter-autonomous system (AS) VPNs that span multiple providers. Configurations involve virtual routing and forwarding (VRF) instances with route distinguishers and targets, alongside Multiprotocol BGP (MP-BGP) for route exchange between customer edge (CE) and PE routers, allowing seamless VPN extension over geographic boundaries. Traffic engineering enhancements, via Resource Reservation Protocol (RSVP), enable path optimization and load balancing across up to 32 multipaths, ensuring efficient bandwidth use in MPLS backbones. This setup is particularly valuable for delivering managed services like Layer 3 VPNs, where only edge modifications are needed for new site additions, minimizing operational complexity in large-scale deployments. Multilayer switches facilitate wireless integration by supporting Wi-Fi 6 and Wi-Fi 7 controllers, enabling unified wired-wireless architectures with seamless client . In campus networks, multilayer switches integrate with the 9800 Series controllers to manage access points, providing Layer 3 for inter-VLAN mobility and policy application across 802.11ax () and 802.11be (Wi-Fi 7) environments. The 9800 Series controllers, deployed alongside multilayer switches, leverage software-defined access (SD-Access) for automated fabric provisioning, ensuring low-latency handoffs and secure segmentation for high-density deployments. This integration supports features like in FlexConnect mode for local or central switching, enhancing in scenarios with thousands of mobile users, such as offices or educational institutions. By combining wired aggregation with control, these setups reduce infrastructure silos and improve overall network efficiency. As of 2025, multilayer switches act as edge gateways in hybrid cloud setups, converging and (IoT) traffic with low-latency routing to multi-cloud environments. Platforms like the Catalyst 8200 Series, functioning as multilayer edge devices, provide 5G-ready connectivity with integrated and VXLAN support for overlay networks spanning on-premises data centers and public clouds. These switches aggregate IoT data and 5G user plane traffic, using BGP EVPN for scalable segmentation and policy enforcement to handle diverse workloads from nodes. In hybrid scenarios, they enable secure data flow to cloud services via Cisco Edge Intelligence, supporting real-time analytics and automation for applications like or urban IoT deployments. This configuration ensures sub-millisecond latency for critical services while simplifying management across distributed hybrid infrastructures.

Differences from Routers and Hubs

Multilayer switches differ from traditional routers primarily in their routing mechanisms and operational scope. While both devices operate at Layer 3 of the OSI model to forward packets based on IP addresses, multilayer switches perform this routing using specialized hardware such as ASICs (Application-Specific Integrated Circuits), enabling wire-speed processing without relying on CPU-intensive software algorithms. In contrast, routers typically use general-purpose processors for routing decisions, which can introduce higher latency, especially under heavy loads, making multilayer switches faster for intra-LAN traffic. However, routers excel in advanced wide area network (WAN) features, such as extensive support for protocols like BGP for internet routing, NAT, VPN tunneling, and dial-up connections, which multilayer switches often lack or implement in a more limited fashion due to their LAN-focused design. This makes multilayer switches more cost-effective for local area network (LAN) environments where high-throughput inter-VLAN routing is needed without the overhead of full router capabilities. Compared to Layer 2-only switches, multilayer switches add native capabilities, allowing them to interconnect virtual LANs (VLANs) directly without requiring an external router, which reduces latency and simplifies . Layer 2 switches forward frames solely based on MAC addresses within a , potentially bottlenecking traffic across VLANs, whereas multilayer switches handle both Layer 2 switching and Layer 3 in hardware, enabling efficient segmentation and communication in segmented enterprise networks. In opposition to hubs, which operate at Layer 1 by broadcasting all incoming data to every connected port and sharing bandwidth equally, leading to collisions and broadcast storms in busy networks, multilayer switches intelligently learn MAC addresses to forward only to the intended destination port. This full-duplex operation and collision avoidance provide dedicated bandwidth per port, vastly improving efficiency and scalability over hubs' half-duplex, shared-medium approach. Relative to dedicated Layer 4-7 appliances, such as application delivery controllers, multilayer switches integrate basic transport and application-layer functions like load balancing and content switching within a single device, suiting simpler topologies where consolidated hardware reduces complexity and cost. However, these appliances offer more specialized acceleration for applications, including , SSL offloading, and advanced tailored to specific protocols, which multilayer switches handle in a more generalized manner without the same depth of optimization. Despite their advantages, multilayer switches have limitations, including higher costs compared to basic Layer 2 switches due to their advanced hardware, and potential challenges in very large WANs, where they may support fewer routes (e.g., up to 32,000 IPv4 routes on models like 9300) and lack robust handling for complex global routing tables compared to dedicated routers.

References

  1. https://www.techtarget.com/searchnetworking/tip/Layer-3-switches-explained
  2. https://www.cisco.com/c/en/us/tech/lan-switching/layer-three-switching-forwarding/index.html
  3. https://www.cse.wustl.edu/~jain/cis788-97/ftp/lan_switching/index.html
  4. https://www.cisco.com/c/en/us/support/docs/switches/catalyst-6000-series-switches/12022-39.html
  5. https://community.cisco.com/t5/switching/difference-between-layer-3-switch-multilayer-switch/td-p/1495807
  6. http://www.cisco.com/en/US/docs/ios/lanswitch/configuration/guide/lsw_ml_sw_over_support_TSD_Island_of_Content_Chapter.html
  7. https://community.cisco.com/t5/networking-knowledge-base/understanding-cisco-express-forwarding-cef-architecture/ta-p/5276856
  8. https://newsroom.cisco.com/c/r/newsroom/en/us/a/y1993/m09/cisco-to-acquire-high-performance-workgroup-networking-company.html
  9. https://newsroom.cisco.com/c/r/newsroom/en/us/a/y1996/m09/cisco-s-new-tag-switching-technology-fuses-routing-and-switching-for-scalable-high-performance-networks.html
  10. https://www.cisco.com/c/en/us/products/collateral/interfaces-modules/ace-application-control-engine-module/product_data_sheet0900aecd8045861b.html
  11. https://www.cisco.com/c/en/us/solutions/software-defined-networking.html
  12. https://newsroom.cisco.com/c/r/newsroom/en/us/a/y2025/m11/cisco-unified-edge-platform-for-distributed-agentic-ai-workloads.html
  13. https://www.cisco.com/c/en/us/support/docs/switches/catalyst-6500-series-switches/71079-arp-cam-tableissues.html
  14. https://standards.ieee.org/ieee/802.1D/3387/
  15. https://practonet.com/switching-concepts-mac-learning-aging-frame-switching-frame-flooding-mac-address-table/
  16. https://www.ciscopress.com/articles/article.asp?p=3089352&seqNum=7
  17. https://www.ieee802.org/1/pages/802.1w.html
  18. https://standards.ieee.org/ieee/802.1Q/6844/
  19. https://documentation.meraki.com/General_Administration/Tools_and_Troubleshooting/Fundamentals_of_802.1Q_VLAN_Tagging
  20. https://standards.ieee.org/ieee/802.3/10422/
  21. https://www.cisco.com/c/en/us/support/docs/lan-switching/spanning-tree-protocol/24062-146.html
  22. https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst9300/software/release/17-17/configuration_guide/ip_mcast_rtng/b_1717_ip_mcast_rtng_9300_cg.pdf
  23. https://www.networkworld.com/article/821490/lan-wan-chapter-12-multilayer-switching.html
  24. https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst3850/software/release/16-5/configuration_guide/qos/b_165_qos_3850_cg/configuring_qos.html
  25. https://www.intechopen.com/chapters/9717
  26. https://www.cisco.com/c/en/us/support/docs/switches/catalyst-6500-series-switches/10559-22.html
  27. http://www.cisco.com/en/US/docs/switches/lan/catalyst3850/software/release/3se/consolidated_guide/b_consolidated_3850_3se_cg_chapter_0100100.html
  28. https://www.cisco.com/c/en/us/products/collateral/switches/catalyst-9300-series-switches/white-paper-c11-741468.html
  29. https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst9500/software/release/17-9/configuration_guide/ha/b_179_ha_9500_cg/configuring_cisco_stackwise_virtual.html
  30. https://www.ciscolive.com/c/dam/r/ciscolive/global-event/docs/2025/pdf/BRKENS-1500.pdf
  31. https://orhanergun.net/understanding-layer-2-and-layer-3-switching-in-campus-networks
  32. https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/ipswitch_cef/configuration/xe-16-8/isw-cef-xe-16-8-book/isw-cef-overview.html
  33. https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst3650/software/release/3se/routing/configuration_guide/b_rt_3se_3650_cg/b_rt_3se_3650_cg_chapter_011.html
  34. https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst3750/software/release/12-2_25_sea/configuration/guide/3750scg/swiprout.pdf
  35. https://www.cisco.com/c/en/us/support/docs/lan-switching/inter-vlan-routing/41260-189.html
  36. https://sec.cloudapps.cisco.com/security/center/resources/access_control_list_logging.html
  37. https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/ipaddr/command/ipaddr-cr-book/ipaddr-i3.html
  38. https://www.cisco.com/c/en/us/products/collateral/switches/catalyst-4900-series-switches/product_data_sheet0900aecd8017a72e.html
  39. https://www.cisco.com/c/en/us/td/docs/ios/solutions_docs/ip_multicast/White_papers/sw_paths.html
  40. https://networklessons.com/switching/cef-cisco-express-forwarding
  41. https://blog.ipspace.net/2022/02/cache-based-forwarding/
  42. https://www.cisco.com/c/en/us/products/collateral/switches/catalyst-6500-series-switches/product_data_sheet09186a0080159856.html
  43. https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/ipapp_fhrp/configuration/15-sy/fhp-15-sy-book/fhp-hsrp.html
  44. https://networklessons.com/ip-services/hsrp-hot-standby-routing-protocol
  45. https://community.cisco.com/t5/switching/the-process-of-catalyst-3750-policy-base-routing/td-p/2100520
  46. https://www.cisco.com/c/en/us/td/docs/ios/slb/configuration/guide/slb_cg_book/slb_cg_info.html
  47. https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/sec_data_acl/configuration/xe-3s/sec-data-acl-xe-3s-book/sec-create-ip-al-filter.html
  48. https://www.cisco.com/c/en/us/td/docs/interfaces_modules/services_modules/csm/3-1/configuration/guide/csm_3_1/bsconfig.html
  49. https://www.firewall.cx/networking/network-fundamentals/cisco-switches-content-switching.html
  50. https://www.cisco.com/c/dam/en/us/td/docs/interfaces_modules/services_modules/csms/2-1-1/configuration/guide/ICNcsmsbook.pdf
  51. https://www.cisco.com/c/dam/global/en_sg/training-events/datacentertechbyte/assets/pdfs/ace-wp.pdf
  52. https://www.f5.com/glossary/layer-7-load-balancing
  53. https://www.loadbalancer.org/blog/layer-7-load-balancing-guide/
  54. https://www.f5.com/pdf/white-papers/intelligent-compression-wp.pdf
  55. https://techdocs.f5.com/kb/en-us/products/big-ip-aam/manuals/product/aam-concepts-11-6-0/2.html
  56. https://www.cisco.com/c/dam/global/en_ca/solutions/strategy/docs/sbaDC_loadbal.pdf
  57. https://www.networkcomputing.com/switches-routers/app-switches-boost-firewall-security
  58. https://www.a10networks.com/glossary/how-do-layer-4-and-layer-7-load-balancing-differ/
  59. https://www.sciencedirect.com/topics/computer-science/crossbar-switch
  60. https://www.cisco.com/c/en/us/td/docs/dcn/mds9000/hw/9700/cisco-mds-9700-switching-module-installation-guide/product-overview.html
  61. https://www.broadcom.com/products/ethernet-connectivity/switching/strataxgs/bcm78900-series
  62. https://www.cisco.com/c/en/us/solutions/silicon-one.html
  63. https://www.sciencedirect.com/topics/computer-science/network-processing-unit
  64. https://www.ciscolive.com/c/dam/r/ciscolive/global-event/docs/2022/pdf/BRKARC-2091.pdf
  65. https://www.cisco.com/c/en/us/products/collateral/switches/catalyst-6500-series-switches/data_sheet_c78-708665.html
  66. https://www.skyworksinc.com/-/media/SkyWorks/SL/documents/public/white-papers/understanding-the-ieee-8023bt-poe-standard.pdf
  67. https://www.cisco.com/c/en/us/products/collateral/switches/catalyst-3850-series-switches/data_sheet_c78-720918.html
  68. https://www.cisco.com/c/en/us/products/collateral/switches/nexus-3550-series/datasheet-c78-743875.pdf
  69. https://blogs.juniper.net/en-us/enterprise-cloud-and-transformation/not-all-deep-buffer-switches-are-created-equal
  70. https://www.cisco.com/site/us/en/products/networking/cloud-networking/ios-xe/index.html
  71. https://www.juniper.net/documentation/us/en/software/junos/junos-overview/topics/concept/junos-software-configuration-methods-overview.html
  72. https://www.cisco.com/c/en/us/support/docs/ios-nx-os-software/ios-xe-bengaluru-1761/217897-compare-traditional-licensing-smart-lic.html
  73. https://www.juniper.net/documentation/us/en/software/license/juniper-licensing-user-guide/juniper-licensing-user-guide.pdf
  74. https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst9400/software/release/17-1/configuration_guide/b_171-9400-cg/configuring_switch_webui.pdf
  75. https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/prog/configuration/1610/b_1610_programmability_cg/restconf_programmable_interface.pdf
  76. https://www.cisco.com/c/en/us/td/docs/routers/ios/config/17-x/syst-mgmt/b-system-management/m_esm-syslog.html
  77. https://www.juniper.net/documentation/us/en/software/junos/cli-reference/topics/ref/statement/syslog-edit-system.html
  78. https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/prog/configuration/167/b_167_programmability_cg/configuring_yang_datamodel.pdf
  79. https://www.juniper.net/documentation/us/en/software/junos/netconf/topics/topic-map/netconf-overview.html
  80. https://www.cisco.com/c/en/us/support/docs/routers/10000-series-routers/23233-sw-upgrade-highendrouters-23233.html
  81. https://www.juniper.net/documentation/us/en/software/junos/junos-install-upgrade/index.html
  82. https://nvlpubs.nist.gov/nistpubs/specialpublications/NIST.SP.800-207.pdf
  83. https://www.cisco.com/c/en/us/td/docs/solutions/Enterprise/Data_Center/VMDC/SDN/SDN.html
  84. https://packetpushers.net/blog/junos-useful-show-commands-capture-data-verification-troubleshooting-part-2/
  85. https://www.cisco.com/c/en/us/support/docs/ios-nx-os-software/ios-embedded-packet-capture/116045-productconfig-epc-00.html
  86. https://www.juniper.net/documentation/us/en/software/junos/network-mgmt/topics/topic-map/analyze-network-traffic-by-using-packet-capture.html
  87. https://www.cisco.com/c/en/us/td/docs/solutions/CVD/Campus/cisco-campus-lan-wlan-design-guide.html
  88. https://www.cisco.com/c/en/us/products/collateral/switches/nexus-3000-series-switches/datasheet-c78-736608.html
  89. https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst3850/software/release/16-3/configuration_guide/b_163_consolidated_3850_cg/b_163_consolidated_3850_cg_chapter_01000010.pdf
  90. https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/mp_l3_vpns/configuration/12-4t/mp-l3-vpns-12-4t-book.pdf
  91. https://www.cisco.com/c/en/us/td/docs/wireless/controller/9800/technical-reference/c9800-best-practices.html
  92. https://www.cisco.com/c/en/us/products/collateral/routers/catalyst-8200-series-edge-platforms/nb-06-cat8200-series-edge-plat-ds-cte-en.html
  93. https://www.cisco.com/site/us/en/solutions/networking/industrial-iot/edge-intelligence/index.html
  94. https://www.fs.com/blog/layer-3-switch-vs-router-what-is-your-best-bet-5181.html
  95. https://www.fibermall.com/blog/layer-3-switch-router.htm
  96. https://www.versitron.com/blogs/post/learn-the-key-differences-between-layer-3-switch-vs-router
  97. https://www.geeksforgeeks.org/computer-networks/difference-between-router-and-layer-3-switch/
  98. https://documentation.meraki.com/Switching/MS_-_Switches/Design_and_Configure/Configuration_Guides/Layer_3_Switching/Comparing_Layer_3_and_Layer_2_Switches
  99. https://cloudswit.ch/blogs/layer2-vs-layer3-switch-differences-choose/
  100. https://www.geeksforgeeks.org/computer-networks/difference-between-hub-and-switch/
  101. https://www.cisco.com/site/us/en/learn/topics/small-business/what-are-the-different-types-of-network-switches.html
  102. https://www.lightoptics.co.uk/blogs/news/what-is-a-multilayer-switch
  103. https://kemptechnologies.com/blog/layer-4-vs.-layer-7-load-balancing-what%27s-the-difference-and-which-one-do-i-need
  104. https://www.cisco.com/c/en/[us](/page/United_States)/products/collateral/switches/catalyst-9300-series-switches/nb-06-cat9300-ser-data-sheet-cte-en.html
Add your contribution
Related Hubs
User Avatar
No comments yet.