topic Created vlan but no PVID is assigned to interface? in ICX Switches

Created vlan but no PVID is assigned to interface?

john_lieberman_ — Fri, 14 Aug 2020 16:27:12 GMT

I've created a vlan and assigned an interface to that vlan as well as ve and assigned it an ip. however when i show interface brief it shows the pvid as vlan 1. Shouldn't it automatically assign the vlan id of the untagged port assigned to it?

Re: Created vlan but no PVID is assigned to interface?

BenBeck — Fri, 14 Aug 2020 16:43:08 GMT

Hey John,

Can you provide the following output and note the port:

show run
show vlan
show vlan brief

Did you apply that interface as tagged or untagged? Depending on the code level you are on, even if you tag a port to a vlan, it will still exist in the default vlan as untagged (think native vlan or our old method known as dual-mode). This allows untagged traffic to pass on the interface.

Re: Created vlan but no PVID is assigned to interface?

john_lieberman_ — Fri, 14 Aug 2020 17:22:14 GMT

thx for the reply. dont have access to the switch at the moment. here s a copy of the config tho. also its SW: Version 08.0.80dT213 - so no dual-mode. both tagged and untagged as needed.

show run

Current configuration:
!
ver 08.0.80dT213
!
stack unit 1
module 1 icx7150-c12-poe-port-management-module
module 2 icx7150-2-copper-port-2g-module
module 3 icx7150-2-sfp-plus-port-20g-module
!
!
global-stp
!
!
!
vlan 1 name DEFAULT-VLAN by port
!
vlan 100 name data by port
tagged ethe 1/1/1 ethe 1/1/3 to 1/1/12
router-interface ve 100
spanning-tree 802-1w
!
vlan 101 name Voice by port
tagged ethe 1/1/2 to 1/1/12
--More--, next page: Space, next line: Return key, quit: Control-c
router-interface ve 101
spanning-tree 802-1w
!
!
!
!
!
!
!
!
!
!
!
!
!
boot sys fl sec
hostname Evergreen-ICX7150-C12
ip route 0.0.0.0/0 10.12.100.254
!
!
!
!
!
--More--, next page: Space, next line: Return key, quit: Control-c
!
!
!
!
!
!
!
!
interface ethernet 1/1/3
loop-detection
spanning-tree 802-1w admin-edge-port
trust dscp
!
interface ethernet 1/1/4
loop-detection
spanning-tree 802-1w admin-edge-port
trust dscp
!
interface ethernet 1/1/5
loop-detection
spanning-tree 802-1w admin-edge-port
trust dscp
!
--More--, next page: Space, next line: Return key, quit: Control-c
interface ethernet 1/1/6
loop-detection
spanning-tree 802-1w admin-edge-port
trust dscp
!
interface ethernet 1/1/7
loop-detection
spanning-tree 802-1w admin-edge-port
trust dscp
!
interface ethernet 1/1/8
loop-detection
spanning-tree 802-1w admin-edge-port
trust dscp
!
interface ethernet 1/1/9
loop-detection
spanning-tree 802-1w admin-edge-port
trust dscp
!
interface ethernet 1/1/10
loop-detection
spanning-tree 802-1w admin-edge-port
--More--, next page: Space, next line: Return key, quit: Control-c
trust dscp
!
interface ethernet 1/1/11
loop-detection
spanning-tree 802-1w admin-edge-port
trust dscp
!
interface ethernet 1/1/12
loop-detection
spanning-tree 802-1w admin-edge-port
trust dscp
!
interface ethernet 1/3/1
speed-duplex 1000-full
!
interface ethernet 1/3/2
speed-duplex 1000-full
!
interface ve 100
ip address 10.12.100.1 255.255.255.0
!
interface ve 101
ip address 10.12.101.1 255.255.255.0
--More--, next page: Space, next line: Return key, quit: Control-c
!
!
!
!
!
lldp med network-policy application voice tagged vlan 101 priority 4 dscp 46 ports ethe 1/1/1 to 1/1/12
lldp med network-policy application voice-signaling tagged vlan 101 priority 5 dscp 34 ports ethe 1/1/1 to 1/1/12
lldp run
!
!
!
!
!
end

Re: Created vlan but no PVID is assigned to interface?

BenBeck — Fri, 14 Aug 2020 17:25:20 GMT

Got it. So are you seeing pvid 1, correct? This would be expected as that column is showing you the untagged vlan more or less. All of your tagged ports there still exist in vlan 1 untagged since it is the default vlan. The 'show vlan' would confirm that I believe.

Re: Created vlan but no PVID is assigned to interface?

john_lieberman_ — Fri, 14 Aug 2020 17:29:35 GMT

the problem is i can't ping anything on either vlan. can't ping the router 1/1/1 can't ping the voice server in port 1/1/2. the arp table shows nothing. I figured the PVID not showing the vlan member meant something was wrong with config or switch.

Re: Created vlan but no PVID is assigned to interface?

BenBeck — Fri, 14 Aug 2020 17:40:06 GMT

Hey John,

I don't think the PVID display is a problem or unexpected based on your configuration.

Should all those ports be tagged or untagged?
Are we learning mac addresses?

It would probably be a lot easier to open a support case and have one of our engineers assist live.

Re: Created vlan but no PVID is assigned to interface?

john_lieberman_ — Fri, 14 Aug 2020 17:45:07 GMT

vlan 100 should be untagged, vlan 101 should be untagged on 1/1/2 and tagged on 1/1/3 to 1/1/12. dont have support for the switch. this is a simple 2 vlan voice and data configuration. Not sure why this config isn't working seems like it should. yes its learning the mac's.

Re: Created vlan but no PVID is assigned to interface?

BenBeck — Fri, 14 Aug 2020 17:51:07 GMT

Hey John,

You may just be learning macs in vlan 1 based on the configuration you sent in. You may need to remove the tagged ports in the data vlan and make then untagged (tagged for voice, untagged for data).

Re: Created vlan but no PVID is assigned to interface?

john_lieberman_ — Fri, 14 Aug 2020 17:55:16 GMT

if I run the command to untag it says the port is already an untagged member. I don't know...

Re: Created vlan but no PVID is assigned to interface?

BenBeck — Fri, 14 Aug 2020 18:05:16 GMT

It looks like the ports are tagged in vlan 100. I don't see them untagged anywhere else. You would need to do something like this:

conf t
vlan 100
no tagged eth
untagged eth