<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Switch on Aperture Zone</title>
    <link>https://aperturezone.com/tags/switch/</link>
    <description>Recent content in Switch on Aperture Zone</description>
    <image>
      <url>https://aperturezone.com/logo.webp</url>
      <link>https://aperturezone.com/logo.webp</link>
    </image>
    <generator>Hugo -- gohugo.io</generator>
    <language>fr-fr</language>
    <lastBuildDate>Fri, 13 Mar 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://aperturezone.com/tags/switch/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Spanning Tree Protocol: understanding and deploying STP/MSTP</title>
      <link>https://aperturezone.com/posts/stp/</link>
      <pubDate>Fri, 13 Mar 2026 00:00:00 +0000</pubDate>
      
      <guid>https://aperturezone.com/posts/stp/</guid>
      <description>&lt;h1 id=&#34;heading&#34;&gt;&lt;/h1&gt;
&lt;hr&gt;
&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;
&lt;p&gt;If you have multiple switches, you’ve surely heard of the &lt;strong&gt;Spanning Tree Protocol&lt;/strong&gt;. But there’s often a gap between theory and practice—especially when you encounter unusual hardware with unexpected interfaces.&lt;/p&gt;
&lt;p&gt;This article details a real-world implementation of MSTP on three HP 1910 switches (based on Comware H3C), including the problems encountered and the solutions found. Spoiler: the GUI won’t be your friend.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id=&#34;why-stp&#34;&gt;Why STP?&lt;/h2&gt;
&lt;h3 id=&#34;the-loop-problem&#34;&gt;The Loop Problem&lt;/h3&gt;
&lt;p&gt;In a network with multiple interconnected switches, &lt;strong&gt;physical loops&lt;/strong&gt; can exist—whether intentional for redundancy or accidental. Without protection, a broadcast frame enters a loop and circulates indefinitely, duplicating itself with each pass. Within seconds, the network is 100% saturated: this is a &lt;strong&gt;broadcast storm&lt;/strong&gt;, and it renders the infrastructure completely unusable.&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>LACP on HP V1910 (H3C Comware)</title>
      <link>https://aperturezone.com/posts/lacp/</link>
      <pubDate>Wed, 11 Mar 2026 00:00:00 +0000</pubDate>
      
      <guid>https://aperturezone.com/posts/lacp/</guid>
      <description>&lt;p&gt;&amp;gt; &lt;strong&gt;Infrastructure involved&lt;/strong&gt;: HP V1910 (x2), Synology NAS (x3), TrueNAS, Windows Server 2022 (Hyper-V)&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;LACP (Link Aggregation Control Protocol), defined by the &lt;strong&gt;IEEE 802.3ad&lt;/strong&gt; standard (part of 802.1AX), allows multiple physical links to be grouped into a single logical link called a LAG (Link Aggregation Group). There are numerous benefits:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Increased aggregate bandwidth&lt;/strong&gt; for multiple traffic flows&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Automatic redundancy&lt;/strong&gt;: if a physical link fails, the others take over without intervention&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Dynamic negotiation&lt;/strong&gt;: the protocol detects and adapts to changes in link status&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&amp;gt; ⚠️ &lt;strong&gt;Important&lt;/strong&gt;: LACP does not increase the throughput of a single flow. A given flow always remains on the same physical link (hashing). The benefit is realized across multiple simultaneous flows.&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>HTTPS on HP ProCurve V1910</title>
      <link>https://aperturezone.com/posts/procurve/</link>
      <pubDate>Tue, 10 Mar 2026 00:00:00 +0000</pubDate>
      
      <guid>https://aperturezone.com/posts/procurve/</guid>
      <description>&lt;p&gt;Securing access to the web interface of managed switches is one of those tasks that seems trivial on paper. On recent hardware, it is indeed trivial. On HP ProCurve V1910 switches—Comware v5 switches that are still used in many home labs and small infrastructures—it&#39;s a different story. This article documents the entire project, the pitfalls, the discoveries, and an honest conclusion about what it&#39;s really worth.&lt;/p&gt;
&lt;p&gt;The test infrastructure: three HP V1910 switches (firmware 5.20 Release 1519P06) on a dedicated, isolated management VLAN with no Internet access. An internal CA based on OpenSSL runs on a Linux server in the infrastructure.&lt;/p&gt;</description>
    </item>
    
  </channel>
</rss>
