I was wondering if anyone here has done VLAN trunking between Ubiquiti and Cisco Switches?
I currently have access to a C2960X-48TS-LL & US-48-500W swithches, and I would like to try to learn how to configure port trunking properly between the two different OEMs solutions. I have succesfully kinda trunked a port on the US-48-500W for my testing AP, connecting two different VLAN’s for my ubiquiti WLAN-access point, to have to dedicated WLAN-networks.
I have done the CCNA ITN course, and I have a self hosted Ubiquiti network control server (not the proper name).
I tired to configure the C2960X with the VLAN trunking commands from the Cisco, but I do not see any changes in port behavior on the US-48-500W side.
Here are the commands I used for the C2960X
1. Login to the switch
2. Config t
3. interface gigabitethernet0/1
4. switchport mode dynamic auto
5. swithcport access vlan 200
6. swithcport trunk native vlan 1
Cisco config is wrong, almost got it though. This is the syntax for trunks:
conf t
interface Gi0/1
switchport mode trunk
switchport nonegotiate
!switchport nonegotiate turns of Cisco's Dyanmic Trunking Protocol, which Ubiquity doesn't support and even if you use Cisco stuff, most everyone turn it off anyways.
!Optional commands:
switchport trunk allowed vlans 200-300 (whatever range)
switchport trunk native vlan XXX (this sets what untagged frames will be treated as. On Cisco Vlan1 is always considered untagged on ports)
If you have a really old code on your Cisco switch, you may also need to do this to force the use of the dot1q standard, most switches from the last decade+ use dot1q as the standard, only super old Cisco stuff requires this:
switchport trunk encapsulation dot1q
Don't forgot to also create your vlans and setup spanning-tree on the Cisco side as well:
vlan 2
name WORKSTATIONS
vlan 3
name SERVERS
vlan 4
name IOT
....
spanning-tree mode rapid-pvst ! Set switch to rapid-per vlan spanning tree, fairly sure this is what Ubiquity does.
spanning-tree portfast bpduguard default !This globally turns on port fast on your ports so you don't have to wait for spanning-tree to do its thing
On the Ubiquity side, all ports are trunks by default with Vlan 1 being the native/untagged Vlan, so don’t actually need to change anything there unless you want to limit what Vlans are going over the trunk to your Cisco switch.
Update
I just checked by running your guide, sadly looks like I will have to add the allowed VLAN’s one by one
Also looks like I need to update my IOS version on the C2960X to the latest version to define that dot1q-standard. I will try to check if I could get it working without that standard.
I am running IOS 15.0 on the C2960X
You are going to have to make the VLANs in the controller on the Ubiquiti side and also make the VLANs with the same ID number on the Cisco side. Once both sides have the VLANs set up and all using the same ID numbers then you just set the switch ports as you want for what is allowed on what ports.
Sorry for taking a long time, I have not had sadly time to boot up my lab until 10 min ago. Note that the TRUNK-link is connected to the GE-port 0/1 on Cisco C2960X & GE37 on the US-48.
Here is what the C2960X is showing
VLAN Trunking
Spanning tree
