Differences

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

--- vlan_tagging [2024/03/19 17:29] – [Testing the Encoding Live Configuration] walkeradmin
+++ vlan_tagging [2024/03/19 18:00] (current) – [Cisco Configuration] walkeradmin
@@ Line 198: / Line 198: @@
 \\
 \\
-Remember, we have two output from our system:
+Remember, we have two outputs from our system:
 \\
 \\
@@ Line 235: / Line 235: @@
 :27:01.014668 IP 15.0.100.1.36187 > 239.100.100.1.1234: UDP, length 1316
 :27:01.014698 IP 15.0.100.1.36187 > 239.100.100.1.1234: UDP, length 1316
-:27:01.015667 IP 15.0.100.1.36187 > 239.100.100.1.1234: UDP, length 1316
-:27:01.015690 IP 15.0.100.1.36187 > 239.100.100.1.1234: UDP, length 1316
 </file>
 <file>
 tcpdump -i eno4.102 -nn
-dropped privs to tcpdump
-tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
 listening on eno4.102, link-type EN10MB (Ethernet), capture size 262144 bytes
 :28:22.773052 IP 16.0.100.1.49656 > 239.100.100.2.1234: UDP, length 1316
@@ Line 264: / Line 262: @@
 :28:22.781111 IP 16.0.100.1.49656 > 239.100.100.2.1234: UDP, length 1316
 :28:22.781131 IP 16.0.100.1.49656 > 239.100.100.2.1234: UDP, length 1316
-:28:22.782084 IP 16.0.100.1.49656 > 239.100.100.2.1234: UDP, length 1316
+</file>
-:28:22.782101 IP 16.0.100.1.49656 > 239.100.100.2.1234: UDP, length 1316
+\\
-:28:22.783075 IP 16.0.100.1.49656 > 239.100.100.2.1234: UDP, length 1316
+It is clear the there is only one set of VLAN tagged traffic on each VLAN output, but all coming from the same physical interface. This is exactly what we want.
-:28:22.783091 IP 16.0.100.1.49656 > 239.100.100.2.1234: UDP, length 1316
+\\
+\\
+----
+==== Cisco Configuration ====
+\\
+For most cases, the customer will be responsible for this, but for this example we will have to configure our own switch, there is not really a lot to do here for a simple test.
+\\
+\\
+We have created two vlan interfaces on our Encoding Live server, and those VLANs will also have to be present on the switch we are connecting to. The interface on the switch will have to be a Trunk Port, the interface on the Encoding Live server is still just an interface for traffic (i.e. it is NOT a trunk port).
+\\
+\\
+Log in to your Cisco switch, and use the following:
+\\
+\\
+Configure the interface to operate in trunk mode using the commands
+  en
+  conf t
+  int gigabitEthernet 0/47 (use your own interface obviously)
+  switchport mode trunk
+\\
+That should be it, if you get an error
+  Command rejected: An interface whose trunk encapsulation is "Auto" can not be configured to "trunk" mode.
+\\
+You need to manually set the port encapsulation mode: (go back to the top level of the cisco command line first)
+  en
+  conf t
+  int gigabitEthernet 0/47 (use your own interface obviously)
+  switchport trunk encapsulation dot1q
+  switchport mode trunk
+\\
+Now we need to do the following:
+  Create the same VLANs as on our output device (Encoding Live in this example)
+  Assign an interface to each VLAN
+\\
+Below is my current VLAN configuration on the Cisco switch. The interfaces I wish to use (45/46) are currently in VLAN0040. There is no VLAN101 or VLAN102.
+<file>
+VLAN Name                             Status    Ports
+---- -------------------------------- --------- -------------------------------
+    default                          active
+   VLAN0010                         active    Gi0/1, Gi0/2, Gi0/3, Gi0/4
+                                                Gi0/5, Gi0/6, Gi0/7, Gi0/8
+                                                Gi0/9, Gi0/10, Gi0/11, Gi0/12
+   VLAN0020                         active    Gi0/13, Gi0/14, Gi0/15, Gi0/16
+                                                Gi0/17, Gi0/18, Gi0/19, Gi0/20
+                                                Gi0/21, Gi0/22, Gi0/23, Gi0/24
+   VLAN0030                         active    Gi0/25, Gi0/26, Gi0/27, Gi0/28
+                                                Gi0/29, Gi0/30, Gi0/31, Gi0/32
+                                                Gi0/33, Gi0/34, Gi0/35, Gi0/36
+   VLAN0040                         active    Gi0/37, Gi0/38, Gi0/39, Gi0/40
+                                                Gi0/41, Gi0/42, Gi0/43, Gi0/44
+                                                Gi0/45, Gi0/46, Gi0/48
+</file>
+\\
+We can create the VLAN and add the interface to it in one line on the cisco:
+  en
+  conf t
+  int gigabitEthernet 0/45
+  switchport access vlan 101
+\\
+If the VLAN does not exist, you will see this message:
+  % Access VLAN does not exist. Creating vlan 101
+Repeat these steps for all other required VLANs.
+\\
+\\
+<file>
+VLAN Name                             Status    Ports
+---- -------------------------------- --------- -------------------------------
+    default                          active
+   VLAN0010                         active    Gi0/1, Gi0/2, Gi0/3, Gi0/4
+                                                Gi0/5, Gi0/6, Gi0/7, Gi0/8
+                                                Gi0/9, Gi0/10, Gi0/11, Gi0/12
+   VLAN0020                         active    Gi0/13, Gi0/14, Gi0/15, Gi0/16
+                                                Gi0/17, Gi0/18, Gi0/19, Gi0/20
+                                                Gi0/21, Gi0/22, Gi0/23, Gi0/24
+   VLAN0030                         active    Gi0/25, Gi0/26, Gi0/27, Gi0/28
+                                                Gi0/29, Gi0/30, Gi0/31, Gi0/32
+                                                Gi0/33, Gi0/34, Gi0/35, Gi0/36
+   VLAN0040                         active    Gi0/37, Gi0/38, Gi0/39, Gi0/40
+                                                Gi0/41, Gi0/42, Gi0/43, Gi0/44
+                                                Gi0/48
+  VLAN0101                         active    Gi0/45
+  VLAN0102                         active    Gi0/46
 </file>
+\\
+Above we can see the two new VLANs of 101 and 102, and in these VLANs are the respective interfaces of Gi0/45 and Gi0/46. That should be it, now Save your Cisco configuration.
+\\
+As per the diagram below:
+{{:vlan_tagging_001.png?900|}}
+\\
+\\
+\\
+We should observe now that we can connect to the Multicast 239.0.100.1:1234 when connected to interface 45 on the switch (which has the traffic tagged as 101), but we will not see the Multicast 23.0.100.2:1234 unless we connect to interface 46 on the Cisco switch (which has the traffic tagged as 102).
+\\
+\\