WalkerWiki - wiki.alanwalker.uk

User Tools

Site Tools

Trace:
vlan_tagging

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
vlan_tagging [2024/03/19 17:07] – [Setting the interface names in Controller] walkeradminvlan_tagging [2024/03/19 18:00] (current) – [Cisco Configuration] walkeradmin
Line 197: Line 197:
 ==== Testing the Encoding Live Configuration ==== ==== Testing the Encoding Live Configuration ====
 \\  \\ 
-This+\\ 
 +Remember, we have two outputs from our system: 
 +\\  
 +\\  
 +<color #ed1c24>eno4.101 239.100.100.1 src 15.0.100.1</color> 
 +\\  
 +\\  
 +<color #00a2e8>eno4.102 239.100.100.2 src 16.0.100.1</color> 
 +\\  
 +\\  
 +We can look for these outputs using tcpdump. 
 +\\  
 +\\  
 +<file> 
 +tcpdump -i eno4.101 -nn 
 + 
 + 
 +listening on eno4.101, link-type EN10MB (Ethernet), capture size 262144 bytes 
 +17:27:01.006691 IP 15.0.100.1.36187 > 239.100.100.1.1234: UDP, length 1316 
 +17:27:01.006709 IP 15.0.100.1.36187 > 239.100.100.1.1234: UDP, length 1316 
 +17:27:01.007661 IP 15.0.100.1.36187 > 239.100.100.1.1234: UDP, length 1316 
 +17:27:01.007693 IP 15.0.100.1.36187 > 239.100.100.1.1234: UDP, length 1316 
 +17:27:01.008649 IP 15.0.100.1.36187 > 239.100.100.1.1234: UDP, length 1316 
 +17:27:01.008668 IP 15.0.100.1.36187 > 239.100.100.1.1234: UDP, length 1316 
 +17:27:01.009774 IP 15.0.100.1.36187 > 239.100.100.1.1234: UDP, length 1316 
 +17:27:01.009793 IP 15.0.100.1.36187 > 239.100.100.1.1234: UDP, length 1316 
 +17:27:01.009808 IP 15.0.100.1.36187 > 239.100.100.1.1234: UDP, length 1316 
 +17:27:01.010699 IP 15.0.100.1.36187 > 239.100.100.1.1234: UDP, length 1316 
 +17:27:01.010715 IP 15.0.100.1.36187 > 239.100.100.1.1234: UDP, length 1316 
 +17:27:01.011659 IP 15.0.100.1.36187 > 239.100.100.1.1234: UDP, length 1316 
 +17:27:01.011682 IP 15.0.100.1.36187 > 239.100.100.1.1234: UDP, length 1316 
 +17:27:01.012649 IP 15.0.100.1.36187 > 239.100.100.1.1234: UDP, length 1316 
 +17:27:01.012666 IP 15.0.100.1.36187 > 239.100.100.1.1234: UDP, length 1316 
 +17:27:01.013685 IP 15.0.100.1.36187 > 239.100.100.1.1234: UDP, length 1316 
 +17:27:01.013703 IP 15.0.100.1.36187 > 239.100.100.1.1234: UDP, length 1316 
 +17:27:01.014651 IP 15.0.100.1.36187 > 239.100.100.1.1234: UDP, length 1316 
 +17:27:01.014668 IP 15.0.100.1.36187 > 239.100.100.1.1234: UDP, length 1316 
 +17:27:01.014698 IP 15.0.100.1.36187 > 239.100.100.1.1234: UDP, length 1316 
 +</file> 
 + 
 +<file> 
 +tcpdump -i eno4.102 -nn 
 + 
 + 
 +listening on eno4.102, link-type EN10MB (Ethernet), capture size 262144 bytes 
 +17:28:22.773052 IP 16.0.100.1.49656 > 239.100.100.2.1234: UDP, length 1316 
 +17:28:22.773069 IP 16.0.100.1.49656 > 239.100.100.2.1234: UDP, length 1316 
 +17:28:22.774040 IP 16.0.100.1.49656 > 239.100.100.2.1234: UDP, length 1316 
 +17:28:22.774057 IP 16.0.100.1.49656 > 239.100.100.2.1234: UDP, length 1316 
 +17:28:22.775044 IP 16.0.100.1.49656 > 239.100.100.2.1234: UDP, length 1316 
 +17:28:22.775065 IP 16.0.100.1.49656 > 239.100.100.2.1234: UDP, length 1316 
 +17:28:22.776058 IP 16.0.100.1.49656 > 239.100.100.2.1234: UDP, length 1316 
 +17:28:22.776082 IP 16.0.100.1.49656 > 239.100.100.2.1234: UDP, length 1316 
 +17:28:22.776101 IP 16.0.100.1.49656 > 239.100.100.2.1234: UDP, length 1316 
 +17:28:22.777058 IP 16.0.100.1.49656 > 239.100.100.2.1234: UDP, length 1316 
 +17:28:22.777076 IP 16.0.100.1.49656 > 239.100.100.2.1234: UDP, length 1316 
 +17:28:22.778118 IP 16.0.100.1.49656 > 239.100.100.2.1234: UDP, length 1316 
 +17:28:22.778136 IP 16.0.100.1.49656 > 239.100.100.2.1234: UDP, length 1316 
 +17:28:22.779131 IP 16.0.100.1.49656 > 239.100.100.2.1234: UDP, length 1316 
 +17:28:22.779153 IP 16.0.100.1.49656 > 239.100.100.2.1234: UDP, length 1316 
 +17:28:22.780139 IP 16.0.100.1.49656 > 239.100.100.2.1234: UDP, length 1316 
 +17:28:22.780162 IP 16.0.100.1.49656 > 239.100.100.2.1234: UDP, length 1316 
 +17:28:22.781088 IP 16.0.100.1.49656 > 239.100.100.2.1234: UDP, length 1316 
 +17:28:22.781111 IP 16.0.100.1.49656 > 239.100.100.2.1234: UDP, length 1316 
 +17:28:22.781131 IP 16.0.100.1.49656 > 239.100.100.2.1234: UDP, length 1316 
 +</file> 
 +\\  
 +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. 
 +\\  
 +\\  
 +---- 
 +==== 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 
 +---- -------------------------------- --------- ------------------------------- 
 +1    default                          active 
 +10   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 
 +20   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 
 +30   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 
 +40   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 
 +---- -------------------------------- --------- ------------------------------- 
 +1    default                          active 
 +10   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 
 +20   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 
 +30   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 
 +40   VLAN0040                         active    Gi0/37, Gi0/38, Gi0/39, Gi0/40 
 +                                                Gi0/41, Gi0/42, Gi0/43, Gi0/44 
 +                                                Gi0/48 
 +101  VLAN0101                         active    Gi0/45 
 +102  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). 
 +\\  
 +\\  
 + 
 + 
 + 
 + 
  
vlan_tagging.1710868052.txt.gz · Last modified: 2024/03/19 17:07 by walkeradmin