SG2008P Trunk (802.1Q) configuration

SG2008P Trunk (802.1Q) configuration

SG2008P Trunk (802.1Q) configuration
SG2008P Trunk (802.1Q) configuration
2024-04-27 19:00:09 - last edited 2024-05-03 14:13:22
Tags: #VLAN
Model: SG2008P  
Hardware Version: V3
Firmware Version: 3.20

This is so basic setup that I don't even know how to begin.

 

I want to setup Port 8 as the 802.1Q trunk port.  Move the WebGUI interface to VLAN 254 on ip 10.0.254.8 255.255.255.0.  Build a DHCP Pool for my VLANs.  But I can't even get pass the basic stuff.  I thought it was going to be an easy process but turns out I don't get the WebGUI or something....

 

I created all the VLAN that the SG2008P will be expecting to be on...(PS:  Can I delete VLAN 1?  All my other, non-TP-Link, switches I either have VLAN disabled or moved all the switchport to 1000.

8fe77cf599414debb4a2440671c8bcec

 

Then I added them to physical port 1/0/8.  Then made sure the port was set to admit only Tagged (I tried it both ways same result)  Set port 1/0/7 as the test port with PVID 254 (untagged)

6f267defcbcc4794bc650fd1d0e5f58d

 

On the opposite end this is the configuration:

sw0(conf-if-te-1/0/46)# do sh run int te 1/0/46
interface TenGigabitEthernet 1/0/46
 mtu 9216
 switchport
 switchport mode trunk
 switchport trunk allowed vlan all
 no switchport trunk tag native-vlan
 no spanning-tree shutdown
 no fabric isl enable
 no fabric trunk enable
 no shutdown
!

45771e14126f41118c7defed29aacb3a

On the laptop I put in the VLAN254 (port 7) ip address manually (10.0.254.0/24). The expected result is that i should be able to ping the VLAN gateway... but nope...

 

I tried it on another switch with SG2008P, same results.  This is pretty basic level stuff.  So what am I missing? (And Yes, if I put the laptop on a different segment of the network, I can reach the VLAN 254 gateway.

  0      
  0      
#1
Options
2 Accepted Solutions
Re:SG2008P Trunk (802.1Q) configuration-Solution
2024-05-03 13:38:22 - last edited 2024-05-03 14:13:26

Okay I have figured out why it wasn't trunking.

 

For whatever reason it needed a native vlan setup.  meaning that it wants to pass untagged packet across the trunk.  Cisco calls it native vlan.  this is for old hardware that usually need to pass packet this way... but normally in my network I don't really use it.

 

What I did was create another VLAN, 4000, (using VLAN 1 = BAD) and made sure both ends of the trunk will pass untagged traffic using VLAN 4000.  Set the TPLink PVID for 4000 and tagged the rest of my other vlan.

 

Now for the management interface....

 

I semi figured out how to move the interface over but it's not reporting itself because the switch itself doesn't allow you to specify a gateway for the vlan interface.  I moved the webgui from 192.168.0.1 VLAN 1 to 10.0.254.8 VLAN 254, it can only be access directly on the switch, no where else on the network.

 

Anyone know a way to configure it so I can get in-band management??

Recommended Solution
  0  
  0  
#2
Options
Re:SG2008P Trunk (802.1Q) configuration-Solution
2024-05-03 14:12:35 - last edited 2024-05-03 14:37:13

 I figured out the last part as well.

 

I guess it was just easier to do it in CLI than trying to figure out the WebGUI.

 

(although, I really wish the CLI is more Cisco-like)

 

Anyway.... to fix my issue I just did a



SG2008P>en

SG2008P#show ip route  # noticed there is no route

SG2008P(config)#ip route 0.0.0.0 0.0.0.0 10.0.254.1 1 #create an all route to gateway

SG2008P#ping 1.1.1.1

Pinging 1.1.1.1 with 64 bytes of data :
Reply from 1.1.1.1 : bytes=64 time=20ms TTL=54
Reply from 1.1.1.1 : bytes=64 time=30ms TTL=54
Reply from 1.1.1.1 : bytes=64 time=20ms TTL=54
Reply from 1.1.1.1 : bytes=64 time=20ms TTL=54

Ping statistics for 1.1.1.1:
    Packets: Sent = 4 , Received = 4 , Lost = 0 (0% loss)
Approximate round trip times in milli-seconds:
Minimum = 20ms , Maximum = 30ms , Average = 22ms

 

and done.

 

Recommended Solution
  0  
  0  
#3
Options
2 Reply
Re:SG2008P Trunk (802.1Q) configuration-Solution
2024-05-03 13:38:22 - last edited 2024-05-03 14:13:26

Okay I have figured out why it wasn't trunking.

 

For whatever reason it needed a native vlan setup.  meaning that it wants to pass untagged packet across the trunk.  Cisco calls it native vlan.  this is for old hardware that usually need to pass packet this way... but normally in my network I don't really use it.

 

What I did was create another VLAN, 4000, (using VLAN 1 = BAD) and made sure both ends of the trunk will pass untagged traffic using VLAN 4000.  Set the TPLink PVID for 4000 and tagged the rest of my other vlan.

 

Now for the management interface....

 

I semi figured out how to move the interface over but it's not reporting itself because the switch itself doesn't allow you to specify a gateway for the vlan interface.  I moved the webgui from 192.168.0.1 VLAN 1 to 10.0.254.8 VLAN 254, it can only be access directly on the switch, no where else on the network.

 

Anyone know a way to configure it so I can get in-band management??

Recommended Solution
  0  
  0  
#2
Options
Re:SG2008P Trunk (802.1Q) configuration-Solution
2024-05-03 14:12:35 - last edited 2024-05-03 14:37:13

 I figured out the last part as well.

 

I guess it was just easier to do it in CLI than trying to figure out the WebGUI.

 

(although, I really wish the CLI is more Cisco-like)

 

Anyway.... to fix my issue I just did a



SG2008P>en

SG2008P#show ip route  # noticed there is no route

SG2008P(config)#ip route 0.0.0.0 0.0.0.0 10.0.254.1 1 #create an all route to gateway

SG2008P#ping 1.1.1.1

Pinging 1.1.1.1 with 64 bytes of data :
Reply from 1.1.1.1 : bytes=64 time=20ms TTL=54
Reply from 1.1.1.1 : bytes=64 time=30ms TTL=54
Reply from 1.1.1.1 : bytes=64 time=20ms TTL=54
Reply from 1.1.1.1 : bytes=64 time=20ms TTL=54

Ping statistics for 1.1.1.1:
    Packets: Sent = 4 , Received = 4 , Lost = 0 (0% loss)
Approximate round trip times in milli-seconds:
Minimum = 20ms , Maximum = 30ms , Average = 22ms

 

and done.

 

Recommended Solution
  0  
  0  
#3
Options