Re: Switch trunk not working

ms69553924 · ‎08-13-2020

Hello Cisco Community,

currently I am trying to extend the configuration of two productive switches with a new vlan 190 and try to connect them via a new fiber cable. The firmware is quite old, but upgrading in the productive system would be not that easy to schedule.

Planned architecture:
Location A:
-) Switch SF300 (Firmware v1.3.0.62)
-) One client is connected via fastethernet port 26 and access mode to vlan190
-) Gigabit ethernet port 4 is connect with the switch of location B (via fiber), trunk mode vlan 190
Location B:
-) Switch SF250 (Firmware v2.1.0.60)
-) One client is connected via fastethernet port 1 and access mode to vlan190
-) Gigabit ethernet port 4 is connected to the switch of location A (via fiber), trunk mode vlan 190

The uplink on both sides to the clients in between the switches is working without issues. Currently we also have SSH access to the SF300, but we can not enable it for the SF250 (seems to be a firmware bug), so our options are limited here too.

We assigned an IP to the client at location A (SF300/26) and the same for the client at location B (SF250/1), but can not ping over the trunk between the switches. Pinging between client B and switch B is working (over the new vlan), we can not test it via client A and switch A, because we can not set a second ip interface for vlan 190 (seems like a firmware bug too, if we set it we loose the first set).

The current configuration is below, we also testet with access mode instead of trunks with the same result. In the configuration also "switchport mode trunk" is not shown, if I try to set it manually over the CLI it will not be shown anyway.

I am also not sure about the line "ip default-gateway 192.168.3.254" in the config of SF300 (location B).

Any hints what is going wrong here, would be great!

Configuration of Switch SF300 (Location A):
vlan database
vlan 61,180,190
[...]

interface vlan 1
no ip address dhcp
!
interface vlan 180
name X
ip address 192.168.1.1 255.255.255.0
!
interface vlan 190
name "Y"
ip address 192.168.2.1 255.255.255.0
!
interface fastethernet1
switchport access vlan 190
switchport trunk native vlan none
!
interface fastethernet2
switchport mode trunk
switchport trunk native vlan 180
switchport trunk allowed vlan remove 1,190
!
interface fastethernet3
switchport mode trunk
switchport trunk native vlan 180
switchport trunk allowed vlan remove 1,190
!
interface fastethernet4
switchport mode trunk
switchport trunk native vlan 180
switchport trunk allowed vlan remove 1,190
!
interface fastethernet5
switchport mode trunk
switchport trunk native vlan 180
switchport trunk allowed vlan remove 1,190
!
interface fastethernet6
switchport mode trunk
switchport trunk native vlan 180
switchport trunk allowed vlan remove 1,190
!
interface fastethernet7
switchport mode trunk
switchport trunk native vlan 180
switchport trunk allowed vlan remove 1,190
!
interface fastethernet8
switchport mode trunk
switchport trunk native vlan 180
switchport trunk allowed vlan remove 1,190
!
interface fastethernet9
switchport mode trunk
switchport trunk native vlan 180
switchport trunk allowed vlan remove 1,190
!
interface fastethernet10
switchport mode trunk
switchport trunk native vlan 180
switchport trunk allowed vlan remove 1,190
!
interface fastethernet11
switchport mode trunk
switchport trunk native vlan 180
switchport trunk allowed vlan remove 1,190
!
interface fastethernet12
switchport mode trunk
switchport trunk native vlan 180
switchport trunk allowed vlan remove 1,190
!
interface fastethernet13
switchport mode trunk
switchport trunk native vlan 180
switchport trunk allowed vlan remove 1,190
!
interface fastethernet14
switchport mode trunk
switchport trunk native vlan 180
switchport trunk allowed vlan remove 1,190
!
interface fastethernet15
switchport mode trunk
switchport trunk native vlan 180
switchport trunk allowed vlan remove 1,190
!
interface fastethernet16
switchport mode trunk
switchport trunk native vlan 180
switchport trunk allowed vlan remove 1,190
!
interface fastethernet17
switchport mode trunk
switchport trunk native vlan 180
switchport trunk allowed vlan remove 1,190
!
interface fastethernet18
switchport mode trunk
switchport trunk native vlan 180
switchport trunk allowed vlan remove 1,190
!
interface fastethernet19
switchport mode trunk
switchport trunk native vlan 180
switchport trunk allowed vlan remove 1,190
!
interface fastethernet20
switchport mode trunk
switchport trunk native vlan 180
switchport trunk allowed vlan remove 1,190
!
interface fastethernet21
switchport mode trunk
switchport trunk native vlan 180
switchport trunk allowed vlan remove 1,190
!
interface fastethernet22
spanning-tree link-type point-to-point
switchport mode trunk
switchport trunk allowed vlan remove 190
macro description switch
!next command is internal.
macro auto smartport dynamic_type switch
!
interface fastethernet23
spanning-tree link-type point-to-point
switchport mode trunk
switchport trunk allowed vlan remove 190
macro description switch
!next command is internal.
macro auto smartport dynamic_type switch
!
interface fastethernet24
spanning-tree link-type point-to-point
switchport mode trunk
switchport access vlan none
switchport trunk native vlan none
switchport trunk allowed vlan remove 1-21,23-4094
macro description switch
!next command is internal.
macro auto smartport dynamic_type switch
!
interface fastethernet25
switchport mode trunk
switchport trunk native vlan 180
switchport trunk allowed vlan remove 1,190
!
interface fastethernet26
switchport mode trunk
switchport trunk allowed vlan remove 1,190
!
interface fastethernet27
switchport mode trunk
switchport trunk native vlan 180
switchport trunk allowed vlan remove 1,190
!
interface fastethernet28
switchport mode trunk
switchport trunk native vlan 180
switchport trunk allowed vlan remove 1,190
!
interface fastethernet29
switchport mode trunk
switchport trunk native vlan 180
switchport trunk allowed vlan remove 1,190
!
interface fastethernet30
switchport mode trunk
switchport trunk native vlan 180
switchport trunk allowed vlan remove 1,190
!
interface fastethernet31
switchport mode trunk
switchport trunk native vlan 180
switchport trunk allowed vlan remove 1,190
!
interface fastethernet32
switchport mode trunk
switchport trunk native vlan 180
switchport trunk allowed vlan remove 1,190
!
interface fastethernet33
switchport mode trunk
switchport trunk native vlan 180
switchport trunk allowed vlan remove 1,190
!
interface fastethernet34
switchport mode trunk
switchport trunk native vlan 180
switchport trunk allowed vlan remove 1,190
!
interface fastethernet35
switchport mode trunk
switchport trunk native vlan 180
switchport trunk allowed vlan remove 1,190
!
interface fastethernet36
switchport mode trunk
switchport trunk native vlan 180
switchport trunk allowed vlan remove 1,190
!
interface fastethernet37
switchport mode trunk
switchport trunk native vlan 180
switchport trunk allowed vlan remove 1,190
!
interface fastethernet38
switchport mode trunk
switchport trunk native vlan 180
switchport trunk allowed vlan remove 1,190
!
interface fastethernet39
switchport mode trunk
switchport trunk native vlan 180
switchport trunk allowed vlan remove 1,190
!
interface fastethernet40
switchport mode trunk
switchport trunk native vlan 180
switchport trunk allowed vlan remove 1,190
!
interface fastethernet41
switchport mode trunk
switchport trunk native vlan 180
switchport trunk allowed vlan remove 1,190
!
interface fastethernet42
switchport mode trunk
switchport trunk native vlan 180
switchport trunk allowed vlan remove 1,190
!
interface fastethernet43
switchport mode trunk
switchport trunk native vlan 180
switchport trunk allowed vlan remove 1,190
!
interface fastethernet44
switchport mode trunk
switchport trunk native vlan 180
switchport trunk allowed vlan remove 1,190
!
interface fastethernet45
switchport mode trunk
switchport trunk native vlan 180
switchport trunk allowed vlan remove 1,190
!
interface fastethernet46
spanning-tree link-type point-to-point
switchport mode trunk
switchport trunk allowed vlan remove 190
macro description switch
!next command is internal.
macro auto smartport dynamic_type switch
!
interface fastethernet47
spanning-tree link-type point-to-point
switchport mode trunk
switchport trunk allowed vlan remove 190
macro description switch
!next command is internal.
macro auto smartport dynamic_type switch
!
interface fastethernet48
spanning-tree link-type point-to-point
switchport mode trunk
switchport trunk allowed vlan remove 190
macro description switch
!next command is internal.
macro auto smartport dynamic_type switch
!
interface gigabitethernet1
spanning-tree link-type point-to-point
switchport mode trunk
switchport trunk allowed vlan remove 190
macro description switch
!next command is internal.
macro auto smartport dynamic_type switch
!
interface gigabitethernet2
spanning-tree link-type point-to-point
switchport mode trunk
switchport trunk allowed vlan remove 190
macro description switch
!next command is internal.
macro auto smartport dynamic_type switch
!
interface gigabitethernet3
switchport mode trunk
switchport trunk allowed vlan remove 190
!
interface gigabitethernet4
spanning-tree link-type point-to-point
switchport mode trunk
switchport access vlan none
switchport trunk allowed vlan remove 1-189,191-4094
macro description switch
!next command is internal.
macro auto smartport dynamic_type switch

Configuration of Switch SF300 (Location A):

vlan database
vlan 60,180,190

[...]

interface vlan 1
ip address 192.168.3.1 255.255.255.0
no ip address dhcp
!
interface vlan 190
name "Y"
!
interface fastethernet5
switchport mode access
!
interface fastethernet26
switchport mode access
switchport access vlan 190
!
interface gigabitethernet1
channel-group 1 mode on
!
interface gigabitethernet3
channel-group 1 mode on
!
interface gigabitethernet4
switchport trunk allowed vlan add 190
switchport default-vlan tagged
!
interface Port-channel1
description "LAG 1"
!
interface Port-channel2
shutdown
description "LAG 2"
!
exit
ip default-gateway 192.168.3.254

Georg Pauwen · ‎08-13-2020

Hello,

not sure I understand what you are asking. Which IP address do you want to ping from which IP address ? If you can narrow your post down, it would be easier to understand. Which switch (and IP address) do you want to ping from which switch (and IP address), using which trunk interface on each switch ?

ms69553924 · ‎08-13-2020

Thank you for the fast reply.

My (not working) test set is:

Client A connected to switch A can not reach client B connected to switch B and the opposite.

I used vlan 190 for that. Access port from each switch to the client, trunk port between the switches.

IP client A: 192.168.2.10/24

IP client B: 192.168.2.11/24

IP switch A: 192.168.2.1/24

No firewalls locally on the clients

ICMP is running in timeout.

(No gateway)

Ping between switch A and client A works, Ping between switch A and B not.

ms69553924 · ‎08-13-2020

The used ports are bold in my first post, at the config section.

Georg Pauwen · ‎08-13-2020

Hello,

you posted two configurations under the same header:

Configuration of Switch SF300 (Location A):

What is the IP address of Switch B ? And what is the configuration of Switch B ?

ms69553924 · ‎08-13-2020

Thank you for the hint. Sorry for mixing up a little bit.

The first configuration is switch A, the second configuration is switch B.

Switch B just has:

interface vlan 1
ip address 192.168.3.1 255.255.255.0
no ip address dhcp

No ip for vlan 190 and it is not possible to add a second interface over the Web GUI or CLI. It just replaces the active configuration and we have to keep it in vlan 1.

I think the main problem is that we can not send packages through the trunk interface (gig4 in both configurations).

Georg Pauwen · ‎08-13-2020

Hello,

the only way an IP address in Vlan 1 and an IP address in Vlan 90 could communicate is if you have inter-Vlan routing configured on a different layer 3 device.

ms69553924 · ‎08-13-2020

Ok, I try to describe the problem better.

Switch A:

1) added vlan190

2) connected to Client A:

interface fastethernet1
switchport access vlan 190
switchport trunk native vlan none

3) connected to switch B:

interface gigabitethernet4
spanning-tree link-type point-to-point
switchport mode trunk
switchport access vlan none
switchport trunk allowed vlan remove 1-189,191-4094
macro description switch
!next command is internal.
macro auto smartport dynamic_type switch

Switch B:

1) added vlan190

2) connected with client B:

interface fastethernet26
switchport mode access
switchport access vlan 190

3) connected with switch A:

interface gigabitethernet4
switchport trunk allowed vlan add 190
switchport default-vlan tagged

Then I assign ip 192.168.1.2 to client A and ip 192.168.1.3 to client B and try to establish any connection between those two. This does not work.

Thank you for your effort.

Georg Pauwen · ‎08-13-2020

Hello,

got it.

I think the problem is most likely related to the way the trunks are configured.

interface gigabitethernet4
spanning-tree link-type point-to-point
switchport mode trunk
switchport access vlan none
switchport trunk allowed vlan remove 1-189,191-4094
macro description switch
!next command is internal.
macro auto smartport dynamic_type switch

interface gigabitethernet4
switchport trunk allowed vlan add 190
switchport default-vlan tagged

Can you try and configure both sides with just the minimal trunk configuration, where all Vlans are allowed ?

ms69553924 · ‎08-14-2020

What I tried to accomplish is that (minimal config):

Accessports to the clients:

interface fastethernet26
switchport mode access
switchport access vlan 190

Trunkports between the switches:

interface gigabitethernet4
switchport mode trunk
switchport trunk allowed vlan add 190

In general this should do the trick?

But somehow over the webinterface the result from my last post comes to the config. Configuring via SSH is only at switch B possible (where we currently have this:

interface gigabitethernet4
switchport trunk allowed vlan add 190
switchport default-vlan tagged)

I also tried it with accessports between the switches, without success. Unfortunately we can not send all vlans over the trunk, because we have some other connections between those switches (other vlans/ports).