cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
987
Views
5
Helpful
4
Replies

3560 VLAN Issue

doug
Level 1
Level 1

I have two 3560's connected via a Cisco AirBridge.

For some reason, VLANs on the remote 3560-8 won't work properly.

 

The port in Corp looks like this: 

interface FastEthernet0/1
 description Bridge to Durham
 switchport trunk encapsulation dot1q
 switchport trunk native vlan 12
 switchport mode trunk
 srr-queue bandwidth share 10 10 60 20
 srr-queue bandwidth shape  10  0  0  0
 mls qos trust cos
 auto qos voip trust

 

The port in remote looks like this:

interface FastEthernet0/1
 description uplink to 1310 bridge
 switchport trunk encapsulation dot1q
 switchport trunk native vlan 12
 switchport mode trunk
 srr-queue bandwidth share 10 10 60 20
 srr-queue bandwidth shape  10  0  0  0
 mls qos trust cos
 auto qos voip trust
 spanning-tree portfast

 

I did notice the remote bridge has "vtp mode transparent".

What happens is I configure the ports for switchport voice vlan 7, and the phones don't come up on the new system.  If I use voice vlan 6, they attempt to come up on the old system, so I know we are reaching corporate.  Also data on vlan 12 works perfectly.

Not sure this is enough to get started with, but that "native vlan" line stumps me and makes me wonder if it's necessary.  My experience has always been that if a port is in trunk mode, you will get all the vlans...

1 Accepted Solution

Accepted Solutions

Hi

vlans are wrong , vlan 12 has 2 different names Data and data

and then you have 2 different voice vlans 5 and 6 which is it ? these should be identical both sides of the trunk

vlan 6 is called 2 different names too

 

vlan names are case sensitive at layer 2 between switches in the broadcast domain , so they must be the same at layer 2 or you will have issues

View solution in original post

4 Replies 4

Reza Sharifi
Hall of Fame
Hall of Fame

By default the native vlan is 1.  So, it has been changed to vlan 12 across all switches which is fine. Also, you are getting all vlans across the trunk port since you have  "switchport mode trunk" enabled on both switches.  Overall the config looks fine. Where is the gateway for all vlans?

HTH

Mark Malone
VIP Alumni
VIP Alumni

Hi

do the vlans name match at layer 2 , if its transparent means they had to be manually added and if it was done wrong or is not case sensitive it wont work , can you post the show vlan and sh int trunk from working and non working switch

 

natvie vlan shouldn't make a diff its juts for tagging that vlan

remove spanning-tree portfast  from the trunk , should not be on a trunk at all unless its specific with trunk added and connected to like router

Sho vlan (remote):

VLAN Name                             Status    Ports
---- -------------------------------- --------- -------------------------------
1    default                          active    Gi0/1
6    voice                            active    Fa0/2, Fa0/4
7    VLAN0007                         active    Fa0/3, Fa0/5, Fa0/6, Fa0/7
12   data                             active    Fa0/2, Fa0/4, Fa0/6, Fa0/7

 

sho vlan (corp)

VLAN Name                             Status    Ports
---- -------------------------------- --------- -------------------------------
1    default                          active    
5    Voice                            active    
6    Voiceservers                     active    Fa0/24
7    VLAN0007                         active    Fa0/2, Fa0/3, Fa0/4, Fa0/5, Fa0/6, Fa0/7, Fa0/8, Fa0/9
                                                Fa0/10, Fa0/11, Fa0/12, Fa0/13, Fa0/14, Fa0/15, Fa0/16

12   Data                             active    

 

sho int trunk (remote)

Port        Mode         Encapsulation  Status        Native vlan
Fa0/1       on           802.1q         trunking      12
Fa0/8       on           802.1q         trunking      12

Port        Vlans allowed on trunk
Fa0/1       1-4094
Fa0/8       1-4094

Port        Vlans allowed and active in management domain
Fa0/1       1,6-7,12,254
Fa0/8       1,6-7,12,254

Port        Vlans in spanning tree forwarding state and not pruned
Fa0/1       1,6-7,12,254
Fa0/8       1,6-7,12,254

 

sho int trunk (corp)

Port        Mode         Encapsulation  Status        Native vlan
Fa0/1       on           802.1q         trunking      12
Gi0/1       on           802.1q         trunking      1
Gi0/2       on           802.1q         trunking      1

Port      Vlans allowed on trunk
Fa0/1       1-4094
Gi0/1       1-4094
Gi0/2       1-4094

Port        Vlans allowed and active in management domain
Fa0/1       1,5-12,250,254,300
Gi0/1       1,5-12,250,254,300
Gi0/2       1,5-12,250,254,300

Port        Vlans in spanning tree forwarding state and not pruned
Fa0/1       1,5-12,250,254,300
Gi0/1       1,5-12,250,254,300
Gi0/2       1,5-12,250,254,300

Hi

vlans are wrong , vlan 12 has 2 different names Data and data

and then you have 2 different voice vlans 5 and 6 which is it ? these should be identical both sides of the trunk

vlan 6 is called 2 different names too

 

vlan names are case sensitive at layer 2 between switches in the broadcast domain , so they must be the same at layer 2 or you will have issues

Review Cisco Networking for a $25 gift card