03-01-2016 01:48 AM - edited 03-08-2019 04:46 AM
Hi,
I'm more of a server engineer rather than a network guru so please go easy on me ;-)
I'm trying to setup a little home lab. I currently have my core switch which is a Cisco 3750. The 3750 has various VLANs setup on it which trunk up to my Hyper V lab.
Ive purchased an 8 port TPLINK TL-SG2210P and need some advice on how to configure this to connect to the Cisco. Basically I want to plug devices (laptops, phones etc) into the TPLink and have access to the VLANs configured on in Hyper V (via the Cisco Trunks).
How would I go about doing this? Would I need to use LACP on the TPLink and Etherchannel on the Cisco? What about tagging/untagging/PVID etc?
Any advice would be greatly appreciated.
Solved! Go to Solution.
03-01-2016 07:59 AM
Looks ok as its SU , switched and in use
just check from your laptop on tplink and ping google make sure you have access through it and you can reach other devices in other vlans
03-01-2016 08:05 AM
Although its handy to know how to create a PortChannel between Cisco and another Vendor, its not doing much good unless you can run a second cable in your lab.
It looks fine, its bundled but the only way to be sure its actually 'load balancing' is to run a second cable.
You just need to create Vlan230 on the TPLink and ensure this is 'Tagged' on Port 8. FYI, I believe the Tplinks create a virtual port called 'LAG1' or something similar so when tagging, make sure you do it on both the physical port and the virtual LAG port.
03-01-2016 02:56 AM
Hi
you don't need an etherchannel but it will help having more bandwidth between the switches , you will need to use lacp as pgap wont work on tplink but if there both gig ports on home network 1 link would probably do. its lacp both sides its the open standard that works on all kit that etherchannel is on
Trunk between the tp and cisco allow all vlans you use locally that will cover you for anything connected , just leave the defaults on each switch in terms of native vlans you should be ok
Just assign your access ports to your vlans and trubk between the switches
This is how you do lacp in Cisco switch you will need to check the TP manual for that switch if you go that route
https://www.freeccnaworkbook.com/workbooks/ccna/configuring-etherchannel-utilizing-lacp
03-01-2016 07:36 AM
Here is the config on the 3750, are you able to verify?
I appreciate you may not know but, how would it be configured on the TP link side? Ive setup the LACP and this is what I get on Cisco side. Looks like LACP is working. What do I do with the TP Link? do I need to do any tagging on the ports? For example port 8 on the TP link it patched to port 23 on the cisco and my laptop is plugged into port 1 on the TP Link. I want to be able to get VLAN 230 working on it.
C3750-1#sh etherchannel port
Channel-group listing:
----------------------
Group: 1
----------
Ports in the group:
-------------------
Port: Gi1/0/23
------------
Port state = Up Mstr Assoc In-Bndl
Channel group = 1 Mode = Active Gcchange = -
Port-channel = Po1 GC = - Pseudo port-channel = Po1
Port index = 0 Load = 0x00 Protocol = LACP
Flags: S - Device is sending Slow LACPDUs F - Device is sending fast LACPDUs.
A - Device is in active mode. P - Device is in passive mode.
Local information:
LACP port Admin Oper Port Port
Port Flags State Priority Key Key Number State
Gi1/0/23 SA bndl 32768 0x1 0x1 0x118 0x3D
Partner's information:
LACP port Admin Oper Port Port
Port Flags Priority Dev ID Age key Key Number State
Gi1/0/23 SA 32768 a42b.b0ce.11b6 18s 0x0 0x44C 0x8 0x3D
Age of the port in the current state: 0d:00h:21m:05s
interface Port-channel1
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 1,110,230
switchport mode trunk
switchport nonegotiate
!
interface GigabitEthernet1/0/1
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 110,130,140,230,253,254,270
switchport mode trunk
!
interface GigabitEthernet1/0/2
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 110,130,140,230,253,254,270
switchport mode trunk
!
interface GigabitEthernet1/0/3
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 110,130,140,230,253,254,270
switchport mode trunk
!
interface GigabitEthernet1/0/4
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 110,130,140,230,253,254,270
switchport mode trunk
!
interface GigabitEthernet1/0/5
switchport access vlan 110
switchport mode access
switchport nonegotiate
!
interface GigabitEthernet1/0/6
switchport access vlan 112
switchport mode access
switchport nonegotiate
!
interface GigabitEthernet1/0/7
switchport access vlan 112
switchport mode access
switchport nonegotiate
!
interface GigabitEthernet1/0/8
switchport access vlan 112
switchport mode access
switchport nonegotiate
!
interface GigabitEthernet1/0/9
switchport access vlan 112
switchport mode access
switchport nonegotiate
!
interface GigabitEthernet1/0/10
switchport access vlan 112
switchport mode access
switchport nonegotiate
!
interface GigabitEthernet1/0/11
switchport access vlan 112
switchport mode access
switchport nonegotiate
!
interface GigabitEthernet1/0/12
switchport access vlan 112
switchport mode access
switchport nonegotiate
!
interface GigabitEthernet1/0/13
switchport access vlan 110
switchport mode access
switchport nonegotiate
!
interface GigabitEthernet1/0/14
switchport access vlan 110
switchport mode access
switchport nonegotiate
!
interface GigabitEthernet1/0/15
switchport access vlan 110
switchport mode access
switchport nonegotiate
!
interface GigabitEthernet1/0/16
switchport access vlan 110
!
interface GigabitEthernet1/0/17
switchport access vlan 110
!
interface GigabitEthernet1/0/18
switchport access vlan 999
shutdown
!
interface GigabitEthernet1/0/19
switchport access vlan 999
shutdown
!
interface GigabitEthernet1/0/20
switchport access vlan 999
shutdown
!
interface GigabitEthernet1/0/21
switchport access vlan 999
shutdown
!
interface GigabitEthernet1/0/22
switchport access vlan 999
shutdown
!
interface GigabitEthernet1/0/23
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 1,110,230
switchport mode trunk
switchport nonegotiate
speed 1000
duplex full
channel-group 1 mode active
!
interface GigabitEthernet1/0/24
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 110
switchport mode trunk
!
interface GigabitEthernet1/0/25
switchport access vlan 999
shutdown
!
interface GigabitEthernet1/0/26
switchport access vlan 999
shutdown
!
interface GigabitEthernet1/0/27
switchport access vlan 999
shutdown
!
interface GigabitEthernet1/0/28
switchport access vlan 999
shutdown
!
interface Vlan1
no ip address
shutdown
!
interface Vlan110
description MGMT
ip address 172.16.110.3 255.255.255.0
!
interface Vlan230
ip address 172.16.230.3 255.255.255.0
!
ip classless
ip route 0.0.0.0 0.0.0.0 172.16.110.2
ip route 172.16.130.0 255.255.255.0 172.16.110.1
ip route 172.16.140.0 255.255.255.0 172.16.110.1
ip route 172.16.230.0 255.255.255.0 172.16.110.1
ip route 172.16.253.0 255.255.255.0 172.16.110.1
ip route 172.16.254.0 255.255.255.0 172.16.110.1
ip http server
ip http secure-server
03-01-2016 07:49 AM
It looks like you only have a single interface in the portchannel at the moment (Gi1/0/23) so this doesn't really tell us if the Cisco is playing nicely with the TPLink in regards to LACP. Add another interface into the group on both sides and run a #show etherchannel summary on the Cisco to see what is going on.
In regards to the Vlans on the TPLink you need to:
When creating a Trunk port to another Switch, the Cisco will automatically make Vlan 1 the native (untagged) vlan and will tag the rest of the vlans, although you wont see this in the config itself.
On several other vendor switches, you will find that you have to manually turn a port into a 'Trunk' by setting the untagged (native) Vlan as 1 and tagging the rest of the Vlans on that port.
Thanks
Edit -
The TPLink user guide is fairly good, see here:
http://www.tp-link.us/resources/document/TL-SG2210P_V1_UG.pdf
Page 40 onwards lists LAG which is what Cisco call PortChannels or Etherchannels, you just need to configure it as LACP on the TPLink.
Page 57 lists Vlans and 802.1q trunks.
Looks fairly straight forward.
03-01-2016 07:54 AM
This is the output from show etherchannel sum. I only have one port on each side due to cabling restraints in my house (its only for a lab environment so throughput will be fairly low.)
C3750-1#sh etherchannel sum
Flags: D - down P - bundled in port-channel
I - stand-alone s - suspended
H - Hot-standby (LACP only)
R - Layer3 S - Layer2
U - in use f - failed to allocate aggregator
M - not in use, minimum links not met
u - unsuitable for bundling
w - waiting to be aggregated
d - default port
Number of channel-groups in use: 1
Number of aggregators: 1
Group Port-channel Protocol Ports
------+-------------+-----------+-----------------------------------------------
1 Po1(SU) LACP Gi1/0/23(P)
03-01-2016 07:59 AM
Looks ok as its SU , switched and in use
just check from your laptop on tplink and ping google make sure you have access through it and you can reach other devices in other vlans
03-01-2016 08:03 AM
03-01-2016 12:59 PM
Looks like we have it working :)
All ports are untagged in VLAN 1 and ports 1 and 8 are tagged in VLAN 230. I can ping external IPs as well as VMs in my Hyper V environment.
Thank you so much for all of your help.
03-03-2016 03:44 AM
Just one thing I have noticed is that I cant ping the management ip address of the TP link from the Cisco or visa versa.
Is that normal?
03-01-2016 08:05 AM
Although its handy to know how to create a PortChannel between Cisco and another Vendor, its not doing much good unless you can run a second cable in your lab.
It looks fine, its bundled but the only way to be sure its actually 'load balancing' is to run a second cable.
You just need to create Vlan230 on the TPLink and ensure this is 'Tagged' on Port 8. FYI, I believe the Tplinks create a virtual port called 'LAG1' or something similar so when tagging, make sure you do it on both the physical port and the virtual LAG port.
04-17-2019 11:48 AM
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide