{"id":32952,"date":"2019-10-31T21:49:55","date_gmt":"2019-10-31T18:49:55","guid":{"rendered":"https:\/\/prohoster.info\/blog\/kak-zavisit-perevod-termina-trunk-ot-vendora-kommutatorov\/"},"modified":"2019-10-31T21:49:55","modified_gmt":"2019-10-31T18:49:55","slug":"kak-zavisit-perevod-termina-trunk-ot-vendora-kommutatorov","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/administrirovanie\/kak-zavisit-perevod-termina-trunk-ot-vendora-kommutatorov","title":{"rendered":"How does the translation of the term trunk depend on the switch vendor?","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

I noticed this error (or, if you prefer, discrepancy) while reviewing the translation of the NETGEAR switches. The point is that when translating the term \u201ctrunk\u201d<\/strong> , it is essential to consider the vendor's interpretation\u2014 Cisco<\/strong> or HP<\/strong>, as there is a very different technical meaning between them.
\nLet's break it down.<\/p>\n

Let's look at the problem with the following examples:<\/p>\n

<\/p>\n

1. Cisco<\/strong><\/p>\n

<\/p>\n

\"How<\/p>\n

<\/p>\n

2. HP<\/strong><\/p>\n

<\/p>\n

\"How<\/p>\n

<\/p>\n

The attentive reader will notice that \u201ctrunk\u201d<\/strong> in these examples it has a different meaning.<\/p>\n

<\/p>\n

Let's delve deeper.<\/p>\n

<\/a><\/noindex><\/p>\n

The Cisco<\/h2>\n

<\/p>\n

\"How<\/p>\n

<\/p>\n

Cisco<\/strong> version under \u201ctrunk<\/strong>\u2019 understands a point-to-point channel<\/em> (a communication channel directly connecting two devices)<\/em>, which connects a switch and another network device, such as another switch or router. Its purpose is to carry traffic from multiple VLANs over a single channel and grant them access to the entire network<\/em>. In layman's terms, it is called a \u201ctrunk\u201d<\/strong>, which makes sense. <\/p>\n

<\/p>\n

Operating principle<\/h3>\n

<\/p>\n

Let's start with what VLAN is.<\/strong><\/h4>\n

<\/p>\n

VLAN<\/strong> stands for Virtual Local Area Network<\/em> or virtual local area network. This technology allows dividing a single physical network into several logical networks that operate independently of each other. For example, within an organization, there are HR department<\/strong>, accounting<\/strong> and IT department<\/strong>. They have their switches, which are connected through a central switch into a single network, and it is necessary to segregate the networks of these departments from each other. This is where VLAN technology comes into play. <\/p>\n

<\/p>\n

\"How<\/p>\n

<\/p>\n

This is how a network divided into VLANs (virtual networks) looks.<\/em><\/p>\n

<\/p>\n

Often, different colors are used to denote VLANs. <\/p>\n

<\/p>\n

\"How<\/p>\n

<\/p>\n

For instance, ports marked with green color belong to one VLAN, while ports marked with red color belong to another. Computers that reside in the same VLAN can interact only with each other<\/strong>, but cannot communicate with computers in another VLAN. <\/p>\n

<\/p>\n

Changes in the switching table for VLANs<\/strong><\/h4>\n

<\/p>\n

When creating VLANs, an additional field is added to the switching table in switches, which specifies VLAN identifiers. Simplified, it looks like this: <\/p>\n

<\/p>\n

\"How<\/p>\n

<\/p>\n

Here we see that ports 1 and 2 belong to VLAN 2, while ports 3 and 4 belong to VLAN 10.<\/em><\/p>\n

<\/p>\n

Let's move on. At the data link layer, data is transmitted in the form of frames (frames<\/em>). When transmitting frames from one switch to another, information is needed regarding which VLAN a particular frame belongs to. This information is added to the transmitted frame. Currently, an open standard is used for this purpose. IEEE 802.1Q<\/strong>. Step-by-step evolution of the frame in VLAN<\/strong><\/p>\n

<\/p>\n

    \n
  1. The computer generates and sends a regular frame (frame, also known as a data link layer packet, i.e., switch level)<\/em>, without adding anything. This frame looks like this:<\/li>\n<\/ol>\n

    <\/p>\n

    \"How<\/p>\n

    <\/p>\n

      \n
    1. The switch receives the frame. According to the switching table, it understands from which computer the frame arrived and to which VLAN this computer belongs. Then, the switch itself adds management information to the frame, known as the tag.<\/em> The tag is a field after the sender's MAC address, which contains, broadly speaking, the VLAN number. This is how a frame with a tag looks:<\/li>\n<\/ol>\n

      <\/p>\n

      \"How<\/p>\n

      <\/p>\n

      Then, the switch sends this frame to another switch. <\/p>\n

      <\/p>\n

        \n
      1. \n

        The switch that receives the frame extracts VLAN information from it, meaning it understands to which computer this frame should be sent, removes all management information from the frame, and forwards it to the recipient computer.<\/p>\n

        \n<\/li>\n

      2. \n

        The frame arrives at the recipient computer already without management information.<\/p>\n

        \n<\/li>\n<\/ol>\n

        <\/p>\n

        Now, let\u2019s return to our \u201ctrunk<\/strong>\u2019\u201d. The ports of the switch that support VLAN can be divided into two groups:<\/p>\n

        <\/p>\n

          \n
        1. Tagged ports (or trunk ports<\/em> at Cisco<\/strong>)<\/li>\n
        2. Untagged ports (or access ports<\/em>)<\/li>\n<\/ol>\n

          <\/p>\n

          We are interested in tagged ports or trunk ports. They are precisely designed to transmit data belonging to a single port<\/strong> while receiving data from several VLANs on one port (we remember that usually ports from different VLANs do not see each other)<\/strong> In this diagram, the tagged ports are number , which connect two switches. Frames will pass through them, for example, from computer<\/em>. <\/p>\n

          <\/p>\n

          \"How<\/p>\n

          <\/p>\n

          to computer 21<\/strong> and 22<\/strong>, which are located in the same VLAN, according to the scheme described above. E<\/strong> So, the communication channel between these ports in A<\/strong>is precisely called \u201c <\/p>\n

          <\/p>\n

          \u2019.\u201d Cisco<\/strong> How does the company interpret this term?trunk<\/strong>Here, in fact, there is no talk about VLAN. In the case of <\/p>\n

          <\/p>\n

          Version HP<\/strong><\/h2>\n

          <\/p>\n

          we are talking about channel aggregation technology. They have<\/strong> <\/p>\n

          <\/p>\n

          \"How<\/p>\n

          <\/p>\n

          \u2013 this is HP<\/strong> a logical channel \u201ctrunk\u201d<\/strong> , which combines multiple physical channels.<\/em>that combines multiple physical channels<\/em>Such aggregation allows for increased bandwidth and reliability of the channel. Let\u2019s illustrate with an example. Suppose we have two switches, each with four ports connected by four wires. <\/p>\n

          <\/p>\n

          \"How<\/p>\n

          <\/p>\n

          If we leave everything as it is \u2014 just connections between the switches \u2014 then these connections will pass frames to one another in a loop, forming loops<\/em> (and broadcast frames will be duplicated over and over again, causing the switches to enter a broadcast storm)<\/em>. <\/p>\n

          <\/p>\n

          Such duplicate connections are considered redundant<\/em>, and they need to be eliminated; for this purpose, the STP (Spanning Tree Protocol) is used. Then, out of our four connections, STP will disable three because it considers them redundant, leaving only one connection. <\/p>\n

          <\/p>\n

          So, if we combine these four physical channels, there will be one logical channel between the switches with increased bandwidth (the maximum speed of data transmission over a communication channel in a unit of time<\/em>). That is, all four channels are utilized, and the problem with redundant connections is resolved. This logical (aggregated) channel is referred to as HP<\/strong> \u201ctrunk<\/strong>Here, in fact, there is no talk about VLAN. In the case of <\/p>\n

          <\/p>\n

          \"How<\/p>\n

          <\/p>\n

          Channel aggregation can be configured between two switches or between a switch and a router. Up to eight physical channels can be combined into one logical channel. It is important that all ports included in the aggregated channel have the same parameters:<\/p>\n

          <\/p>\n