LAG or TRUNK? (Consolidating VLANS)

[TheGoob]

Hello.

So I have only ever know it as Trunk and have used a Catalyst at one time to do so, but after some googles I keep seeing LAG come up.

This is essentially my want; I have 5 vlans on an SG350XG and I want to bring those same vlans onto an SG550X by.

A am just a bit confused when it comes to creating this, as I do not see any vlan integration (looking wrong place?) I mean I assume I just create L2 vlans on SG550X and assign the interfaces I want to belong to which vlan, but the link between? 1 Interface on 350XG and 1 Interface 550X, but how to set those up I am not finding much, unless I am and am not understanding it. I just assumed I’d dedicate “a” Interface on Switch, tell it Trunk and assign it the 5 vlans; done. But seems not so basic. 

[Kasun Bandara]

@TheGoob hi, in cisco terminology,

trunk is link which can send many VLANs. LAG is collection of physical links work as a one logical link to increase bandwidth and same time it gives failure tolerance for certain level. 

you can create LAG between 350 and 550 switch using 2 or more links (there is max limit) then allow your 5 VLANs though that link.

[TheGoob]

Ah alright, so LAG combines multiple physical (5 max) interfaces for increased bandwidth + multiple vlans whereas a Trunk is multiple vlans on an interface.

I could go the LAG route for knowledge sake and experience but both the Switches will have the Trunks on their 10Gbps ports so not too concerned about bandwidth. I just could not find any documentation showing how to add vlans to the trunks. 
Would this work? (On SG350X);

int ge 1/10
  (config-if)#switchport trunk encapsulation dot1q
  (config-if)#switchport mode trunk
  (config-if)#switchport trunk allowed vlan 2-6

And do the same on the SG500X?

[Kasun Bandara · Accepted solution]

@TheGoob you can do as below. make sure both sides have same config. when you change port to LAG and mode, link may reset.

LAG --
go to 'port management' > 'link aggregation' > 'LAG management'
select the one of LAG form the list and edit. then add the interfaces connected to other end switch which needs the LAG. select LACP.

so the same process for other end switch too. make sure both switches configured properly. because both sides need to have same config.

TRUNK --
go to 'VLAN management' > 'interface settings'
select interface type 'LAG' click 'GO'
select the new LAG created and edit
change interface mode to 'Trunk'
save and apply

go to 'Port VLAN membership'
select interface type 'LAG' click 'GO'
select the new LAG created and 'join vlan'
select required VLANs to pass thorugh the LAG.
save and apply

[TheGoob]

I really can not seem to get this to work... I have verified my configurations, both are "same" but I am missing something.

[TheGoob]

Cool, works nice TY. Stupid question just out of curiosity… Could I do let’s say 1 10Gbps Port for LAG on Switch 1st then 10 x 1Gbps Ports for other end of LAG on 2nd Switch or can it not be like that? 

[TheGoob]

When I do these identically on SW1 (Main, DHCP Server etc) and SW 2, other than cresting same vlans on S2 and assigning ports to each vlan, do I do anything else? I’m assuming a host connected to let’s say vlan2 on SW will grab an ip/dns from S1 vlan 2?