topic Re: No ping between cisco C9300 and ICX-8200 switch in ICX Switches

No ping between cisco C9300 and ICX-8200 switch

Mohammadsaeed — Sun, 09 Jun 2024 09:59:09 GMT

Hi,

I have ICX-8200 switch link with cisco C9300 as trunk link but I can't ping between switches without make switch port native vlan 12 in cisco, and I don't want to use vlan 12 as native i want vlan 1

C9300 (port Gig1/0/1 ------> ICX-8200 (port 1/2/1)

here is my ICX8200 config:

vlan 1 by port
untagged ethe 1/2/1
spanning-tree 802-1w
!
vlan 12 name Network_Mgt by port
untagged ethe 1/2/1
spanning-tree 802-1w

!
ip route 0.0.0.0/0 10.25.60.100
!
!
fast port-span exclude ethe 1/2/1
hostname ICX8200-8P-200
ip multicast passive
ip tftp blocksize 8192
fdp run

!
interface management 1
!
interface ethernet 1/2/1
no cdp enable
spanning-tree 802-1w admin-edge-port
pvst-mode
!
interface ve 1
!
interface ve 12
ip address 10.25.61.135 255.255.254.0
!
interface ve 4000

Cisco Switch:

interface GigabitEthernet1/0/1
description *** Connected to ICX8200-8P ***
switchport trunk allowed vlan 1,9,12,14,22,131,132,202
switchport mode trunk
udld port aggressive
no vtp
spanning-tree portfast trunk
end

interface Vlan12
ip address 10.25.61.36 255.255.254.0
end

using these configuration no ping between cisco and ICX switch, but if i add this command under cisco switch:

switchport trunk native vlan 12

Then i can ping but I don't want to use vlan 12 as Native, i want vlan 1 only.

Any help please

Thanks

Re: No ping between cisco C9300 and ICX-8200 switch

jdryan — Mon, 10 Jun 2024 14:15:11 GMT

Hi Mohammadsaeed,

Could you try the below and give it a shot :
interface GigabitEthernet1/0/1
description *** Connected to ICX8200-8P ***
switchport trunk allowed vlan 1,9,12,14,22,131,132,202
switchport trunk native vlan 1
switchport mode trunk
udld port aggressive
no vtp
spanning-tree portfast trunk
end

and on the 8200 :

Conf t
vlan 1
untagged eth 1/2/1
vlan 12
tagged eth 1/2/1

If the requirement here is to not have native vlan at all, then with the current config on Cisco as it is.
Try the below on the 8200 :

Conf t
vlan 1
tagged eth 1/2/1
vlan 12
tagged eth 1/2/1
exit

Let us know if that helps !

- Ryan

Re: No ping between cisco C9300 and ICX-8200 switch

inphobia — Thu, 13 Jun 2024 02:17:46 GMT

bottom line is that with the current config your vlan headers are mismatched.

most cisco devices accept untagged packets on trunks by default, and they also have "switchport trunk native vlan 1" by default. since you untagged vlan 12 on eth 1/2/1 on the ruckus side it will be accepted by the cisco device & put on the native vlan. also, there's nothing wrong with using "switchport trunk native vlan 12" in this case. we use this for provisioning devices for example, so when they have no config they get put in a configuration vlan & when they get a config with vlan & reboot they continue to work.

tbh, i find it much more interesting in how the icx allows 2 different vlans to be untagged on the same port (as per your example). sounds like a flooding issue waiting to happen.

Re: No ping between cisco C9300 and ICX-8200 switch

jdryan — Tue, 02 Jul 2024 15:26:11 GMT

No the ICXs do not allow multiple untagged, only one vlan is allowed to be untagged.

Re: No ping between cisco C9300 and ICX-8200 switch

inphobia — Wed, 10 Jul 2024 14:17:21 GMT

ofcourse, there are very few valid reasons to have 2 access/untagged vlans on the same port; however the original poster said this was his config:

vlan 1 by port
untagged ethe 1/2/1
spanning-tree 802-1w
!
vlan 12 name Network_Mgt by port
untagged ethe 1/2/1
spanning-tree 802-1w

as such i'm curious if this is a config mockup or an actual running config. don't have access to an icx device today to check.

Re: No ping between cisco C9300 and ICX-8200 switch

jdryan — Sat, 20 Jul 2024 12:32:32 GMT

From what I believe, it was a way to convey how the configuration attempted
Hence, based on that, the suggestions were shared.
But as mentioned, we would not be able to use 2 untagged vlans at the same time, as we do not use hybrid-ports that usually support 2 untagged vlans.

Hence, one of the two would need to be passed as tagged/trunk-allowed vlan. on either ends.