Differences

This shows you the differences between two versions of the page.

--- networking:small_form_factor_pluggable_sfp_p [2024/06/17 16:26] – aperez
+++ networking:small_form_factor_pluggable_sfp_p [2025/02/24 09:37] (current) – aperez
@@ Line 7: / Line 7: @@
 ----
 ----
+[[networking:fiber_optics|]]
+[[networking:optical_fiber_fundamentals_fibers|networking:optical_fiber_fundamentals_fibers]]
+----
+----
 {{ :networking:sfp1.jpg?500 |}}
@@ Line 48: / Line 54: @@
 ----
 ----
-{{ :networking:sfp2.jpg?600 |}}
+{{ :networking:sfp2.jpg?500 |}}
 ----
 ----
-{{ :networking:sfp3.jpg?600 |}}
+{{ :networking:sfp3.jpg?500 |}}
 ----
 ----
-{{ :networking:sfp4.png?600 |}}
+{{ :networking:sfp4.png?500 |}}
 ----
 ----
@@ Line 177: / Line 183: @@
 ** QSFP28**
-{{ :networking:sfp6.jpg?600 |}}
+{{ :networking:sfp6.jpg?500 |}}
 The **QSFP28 is a Quad (4-channel)** small form factor hot pluggable fibre optical transceiver used for 100 Gigabit Ethernet (100GbE) data communications applications. The QSFP28 integrates 4 transmit and 4 receiver channels. The number 28 means each lane carries up to 28G data rate. QSFP28 supports 4x25G breakout connection, 2x50G breakout, or 1x100G depending on the type of QSFP28 transceiver used. The 100G QSFP28 Single Lambda optical transceivers convert four 25G electrical signals into a single-wave 100G PAM4 optical signal for data transmission by using a DSP. The optical transmitting and receiving units are reduced from four to one, effectively reducing the internal optical complexity of the optical module.
@@ Line 297: / Line 303: @@
   approved along with some 200G not listed here. Remember our quote (above) from Bob Metcalfe, co inventor of
   Ethernet:  "The wonderful thing about standards is we have so many to choose from."
+----
+----
+**Addressing the New Paradigm**
+**IEEE 802.3df™-2024**, **with its parallel x8 structure for 800 GbE**, enables Ethernet to address the reality of today’s networks where dual 400 GbE links are already being supported in a single x8 copper or optical connection. While this helped enable higher 400 GbE port density, it has emerged into even greater flexibility for configuring a port. Consider a given eight-lane port: it could be configured to support any of the following scenarios: a) one eight-lane implementation; b) two four-lane implementations; c) four two-lane implementations; d) eight one-lane implementations.
+Thus, in combination with the standards noted in Table 1, a network architect can configure a single port to support standardized 100 GbE, 200 GbE, 400 GbE, or 800 GbE. This enables leveraging economies of scale to drive costs down throughout the entire ecosystem.
+{{ :networking:sfp21.jpg?500 |}}
+**Looking Ahead**
+As previously highlighted from the latest IEEE 802.3™ Ethernet bandwidth assessment, by 2025 traffic levels are forecasted to be 2.3x to 55.4x the observed levels of 2017. While it is anticipated that IEEE 802.3df™-2024 will provide relief to a number of applications, the continuing exponential growth of industry bandwidth needs will necessitate the next rate of Ethernet sooner than the historical approximate 7 years that has been observed since 10 GbE.
+The IEEE P802.3dj 200 Gb/s, 400 Gb/s, 800 Gb/s, and 1.6 Tb/s Ethernet Task Force emerged out of the IEEE P802.3df™ Task Force. The focus of this force will be on developing solutions based on 200 Gb/s or greater electrical and optical signaling. Those familiar with Ethernet are familiar with its propensity to provide upgrade paths. Therefore, the IEEE P802.3dj™ Task Force will be focused on solutions based on 1, 2, 4, and 8 lanes. As illustrated in Figure 3, with a lane rate of 200 Gb/s, solutions for 20 GbE, 400 GbE, 800 GbE, and the next Ethernet rate, 1.6 Tb/s, will be developed. This project is currently scheduled for completion in 2026.
+{{ :networking:sfp22.jpg?500 |}}
+----
+----
+**FEC** on an SFP port refers to **Forward Error Correction (FEC)**, which is a technique used in fiber optic and Ethernet networks to enhance data transmission reliability by detecting and correcting errors without the need for retransmission.
+**FEC (Forward Error Correction)**:
+FEC is a mechanism that adds redundant information to the transmitted data. This redundancy allows the receiving end to detect and correct errors caused by signal degradation or noise during transmission.
+Purpose: FEC is essential for high-speed data links (e.g., 10G, 25G, 40G, 100G Ethernet) to improve link quality and performance.
+Types: Different FEC modes can be used depending on the standard and speed of the connection (e.g., Reed-Solomon FEC).
+  *   **auto**   Enable FEC Auto-Neg
+  *   **cl108**  Enable clause108 with 25G
+  *   **cl74**   Enable clause74 with 25G
+  *   **off**    Turn FEC off, FEC is mandatory for speeds 50G or higher
+----
+----
+**Benefits of FEC on SFP Ports**:
+  * Error Correction: FEC can correct errors due to signal attenuation or interference.
+  * Better Link Performance: Allows for longer cable runs or higher speeds by improving signal integrity.
+  * No Retransmissions: Unlike other error correction methods, FEC works proactively without needing retransmissions, which is important for low-latency environments.
+----
+----
+**Aruba Switch 6400:**
+  CS-2P-MDFHA-A#** show ver**
+  -----------------------------------------------------------------------------
+  ArubaOS-CX
+  (c) Copyright 2017-2024 Hewlett Packard Enterprise Development LP
+  -----------------------------------------------------------------------------
+  Version      : FL.10.13.1010
+  Build Date   : 2024-04-09 00:34:12 UTC
+  Build ID     : ArubaOS-CX:FL.10.13.1010:ef2109377880:202404090010
+  Build SHA    : ef21093778805e954ec130b0939d34927bb7ba19
+  Hot Patches  :
+  Active Image : primary
+  Service OS Version : FL.01.14.0002
+  BIOS Version       : FL.01.0002
+CS-2P-MDFHA-A(config)# **interface 1/3/36**
+**error-control**    Configure the error control (**FEC**) mode
+  CS-2P-MDFHA-A(config-if)# error-control
+    auto        Use the transceiver default
+    base-r-fec  Use IEEE BASE-R (Firecode) FEC
+    none        Do not use any FEC
+    rs-fec      Use IEEE Reed-Solomon FEC
+----
+**C9500 Cisco Catalyst**
+C9500-N#**show ver**
+  Cisco IOS XE Software, **Version 17.12.03**
+  Cisco IOS Software [Dublin], Catalyst L3 Switch Software (CAT9K_IOSXE), Version 17.12.3, RELEASE SOFTWARE (fc7)
+  interface TwentyFiveGigE1/0/3
+   description VLAN 526 PTP A.B.C.D/EF X30
+   switchport access vlan 526
+   switchport mode access
+   mtu 9100
+   logging event trunk-status
+   logging event bundle-status
+   udld port aggressive
+   fec cl74
+  C9500-N(config-if)#interface TwentyFiveGigE1/0/3
+  C9500-N(config-if)#fec ?
+    auto   Enable FEC Auto-Neg
+    cl108  Enable clause108 with 25G
+    cl74   Enable clause74 with 25G
+    off    Turn FEC off, FEC is mandatory for speeds 50G or higher
 ----
 ----