Luis,
So Cisco don't use tagged/untagged. You build the vlan (or vlan range) and then apply it to a trunk interface. The 'native' keyword in the interface 'switchport trunk native' stanza sets the default untagged vlan for that particular port. Try something like this: vlan 65 name public vlan 100-200 name my-guest-vlans exit interface GigabitEthernet1/0/1 switchport trunk encapsulation dot1q switchport mode trunk switchport trunk native vlan 65 switchport trunk allowed vlan 100-200 exit Now be really careful with the number of vlans you allocate if you're running spanning tree, as spanning-tree will start to have problems with large numbers of vlans. With Cloudstack in advanced mode, we find that running the management network as native is often a better design. You can then allocate a vlan for public and just tell CloudStack what the vlan is and it will use it. You can then just include that vlan in your vlan allowed statement: switchport trunk allowed vlan 65,100-200 - Si ________________________________ From: Luis <lmartinez...@yahoo.com.INVALID> Sent: Monday, August 14, 2017 12:42 PM To: users@cloudstack.apache.org Subject: CS VLAN configuration in a Cisco 3560 switch Hi I have a question, following the manual for an advance networking I am trying to configure VLAN's in a Cisco 3560 but i am cofuse, is this all I need Can somebody post a complete example base on their experience? Thank you. This is what I have untagged VLAN 65 for public traffice tagged VLAN traffic for ranges 600-1000 for tagged trafficeinterface GigabitEthernet1/0/1 switchport trunk encapsulation dot1q switchport mode trunk switchport trunk native vlan 100-900 exit
