cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Bookmark
|
Subscribe
|
1000
Views
1
Helpful
7
Replies

VLAN's Pruned when Not configured to do so.

larrycraig
Level 1
Level 1

Hello,

  I am struggling with what should be a straight forward switch add to a network. We have a 2960XR three switch core stack with seven VLAN's configured, of which one is for management. The core is configured with all the SVI's for all VLANs and the second switch is only configured with an SVI for the management vlan.  The second switch is a 3560CG that we are trying to use to extend the network out into the receiving area. 

  Both switches can see each other on layer two via cdp and show all details.  The trunk is configured and up. VTP was not previously configured, but has since been configured with the core in the server role and the tiny switch as a client. I cannot get layer three to come up and all attempts to ping fail.  I have wiped the 3560CG several times and started over.  Where I am now is that when I run "show interface trunk" on the core I see that all VLANs appear to be being pruned on the interface to the other switch. I determine this from this section of the output:

Port Vlans in spanning tree forwarding state and not pruned
Gi2/0/35 17,19,99
Gi2/0/52 none

All other interfaces (Scrubbed from the above) are show the same as the first shown above.

The port configuration for gi2/0/52 is:

interface GigabitEthernet2/0/52
description UPLINK to warehouse gi0/10
switchport trunk allowed vlan 16-20,99
switchport trunk native vlan 16
switchport mode dynamic desirable
spanning-tree portfast network

I did not previously have dynamic desirable, it was added on a recommendation but did not resolve anything.

The corresponding port at the other end of the Trunk link is configured as follows:

interface GigabitEthernet0/10
description UPLINK to Core gi2/0/52
switchport trunk encapsulation dot1q
switchport trunk native vlan 16
switchport trunk allowed vlan 16-20,99
switchport mode dynamic desirable

The command "show interface trunk" on this switch does not show any issues. Leading me to believe the issue is at the core. The output for this switch is as follows:

sh int trunk

Port Mode Encapsulation Status Native vlan
Gi0/10 desirable 802.1q trunking 16

Port Vlans allowed on trunk
Gi0/10 16-20,99

Port Vlans allowed and active in management domain
Gi0/10 16-20,99

Port Vlans in spanning tree forwarding state and not pruned
Gi0/10 16-20,99

 

Core code level is: 15.2(4)E6

3560CG code is: 15.2(2)E10

I have walked away to get clear perspective, but I am still missing something that I believe is super simple.  If you can offer an insight it is appreciated.

 

1 Accepted Solution

Accepted Solutions

First, I went to VTP to try it when it was not working.  I have already backed that out.  And ......

 

SHOOT ! ! 

 

I just found it.  Thank you both, I did not have "switchport mode trunk" on the core side at all.  I knew it was going to be something stupid. Thank you for entertaining my broken brain.

View solution in original post

7 Replies 7

can you draw the topology

I am no artist, so I hope this helps.

Selection_313.png

Hi

 First off, put them in VTP transparent mode. You dont need this protocol.

 If I understood, all you need is to plug this 3560 to the 2960 stack, extend some vlans and manage the switch via IP address?

 Take one interface in both side and setup as trunk. As simples as possible

interface Gix/x

switchport mode trunk

 

===============================

On the 3560

vlan x

name mgmt

exit

conf t

interface vlan x (same vlan used on core for management)

ip add x.x.x. x.x.x (same network used on core, different IP address)

Take the interface you connected to the Core

 Interface Gix/x

switchport mode trunk

ip route 0.0.0.0 0.0.0.0 x.x.x.x ( Core´s management Vlan ip address)

 

 

 

First, I went to VTP to try it when it was not working.  I have already backed that out.  And ......

 

SHOOT ! ! 

 

I just found it.  Thank you both, I did not have "switchport mode trunk" on the core side at all.  I knew it was going to be something stupid. Thank you for entertaining my broken brain.

You are welcome. Glad you sorted that out.

you are so welcome.