Tagged Ethernet interface (VLAN PFC) fails to activate on Ubuntu 16.04

Environment:

  • Ubuntu 16.04, Kernel 4.15.0-29-generic
  • MLNX_OFED_LINUX-4.3-1.0.1.0:
  • MCX416A-CCAT

Configured PFC with VLAN 100 and Priority 3. While trying to enable the interface, I get:

root@sm16:~# nmcli con up ens1f0.100

Error: Connection activation failed: Failed to find a compatible device for this connection

Any pointers?

This is how the configuration of the tagged and untagged interfaces look like:

root@sm16:~# nmcli c s

NAME UUID TYPE DEVICE

ens1f0 e5251358-dffb-4e07-b72f-b9e93ca6eca8 802-3-ethernet –

ens1f0.100 10c8d003-164a-4a8d-a21f-ff6bb712a090 vlan –

nmcli con s ens1f0.100 | less

connection.id: ens1f0.100

connection.uuid: 10c8d003-164a-4a8d-a21f-ff6bb712a090

connection.interface-name: ens1f0

connection.type: vlan

connection.autoconnect: yes

connection.autoconnect-priority: 0

connection.timestamp: 0

connection.read-only: no

connection.permissions:

connection.zone: –

connection.master: –

connection.slave-type: –

connection.autoconnect-slaves: -1 (default)

connection.secondaries:

connection.gateway-ping-timeout: 0

connection.metered: unknown

connection.lldp: -1 (default)

802-3-ethernet.port: –

802-3-ethernet.speed: 0

802-3-ethernet.duplex: –

802-3-ethernet.auto-negotiate: yes

802-3-ethernet.mac-address: –

802-3-ethernet.cloned-mac-address: –

802-3-ethernet.mac-address-blacklist:

802-3-ethernet.mtu: 4200

802-3-ethernet.s390-subchannels:

802-3-ethernet.s390-nettype: –

802-3-ethernet.s390-options:

802-3-ethernet.wake-on-lan: 1 (default)

802-3-ethernet.wake-on-lan-password: –

ipv4.method: manual

ipv4.dns:

ipv4.dns-search:

ipv4.dns-options: (default)

ipv4.dns-priority: 0

ipv4.addresses: 10.0.20.75/24

ipv4.gateway: –

ipv4.routes:

ipv4.route-metric: -1

ipv4.ignore-auto-routes: no

ipv4.ignore-auto-dns: no

ipv4.dhcp-client-id: –

ipv4.dhcp-timeout: 0

ipv4.dhcp-send-hostname: yes

ipv4.dhcp-hostname: –

ipv4.dhcp-fqdn: –

ipv4.never-default: no

ipv4.never-default: no

ipv4.may-fail: yes

ipv4.dad-timeout: -1 (default)

ipv6.method: auto

ipv6.dns:

ipv6.dns-search:

ipv6.dns-options: (default)

ipv6.dns-priority: 0

ipv6.addresses:

ipv6.gateway: –

ipv6.routes:

ipv6.route-metric: -1

ipv6.ignore-auto-routes: no

ipv6.ignore-auto-dns: no

ipv6.never-default: no

ipv6.may-fail: yes

ipv6.ip6-privacy: -1 (unknown)

ipv6.addr-gen-mode: stable-privacy

ipv6.dhcp-send-hostname: yes

ipv6.dhcp-hostname: –

vlan.parent: ens1f0

vlan.id: 100

vlan.flags: 1 (REORDER_HEADERS)

vlan.ingress-priority-map:

vlan.egress-priority-map: 0:3,1:3,2:3,3:3,4:3,5:3,6:3,7:3

nmcli con s ens1f0| less

connection.id: ens1f0

connection.uuid: e5251358-dffb-4e07-b72f-b9e93ca6eca8

connection.interface-name: ens1f0

connection.type: 802-3-ethernet

connection.autoconnect: yes

connection.autoconnect-priority: 0

connection.timestamp: 0

connection.read-only: no

connection.permissions:

connection.zone: –

connection.master: –

connection.slave-type: –

connection.autoconnect-slaves: -1 (default)

connection.secondaries:

connection.gateway-ping-timeout: 0

connection.metered: unknown

connection.lldp: -1 (default)

802-3-ethernet.port: –

802-3-ethernet.speed: 0

802-3-ethernet.duplex: –

802-3-ethernet.auto-negotiate: yes

802-3-ethernet.mac-address: –

802-3-ethernet.cloned-mac-address: –

802-3-ethernet.mac-address-blacklist:

802-3-ethernet.mtu: 4200

802-3-ethernet.s390-subchannels:

802-3-ethernet.s390-nettype: –

802-3-ethernet.s390-options:

802-3-ethernet.wake-on-lan: 1 (default)

802-3-ethernet.wake-on-lan-password: –

ipv4.method: auto

ipv4.dns:

ipv4.dns-search:

ipv4.dns-options: (default)

ipv4.dns-priority: 0

ipv4.addresses:

ipv4.gateway: –

ipv4.routes:

ipv4.route-metric: -1

ipv4.ignore-auto-routes: no

ipv4.ignore-auto-dns: no

ipv4.dhcp-client-id: –

ipv4.dhcp-timeout: 0

ipv4.dhcp-send-hostname: yes

ipv4.dhcp-hostname: –

ipv4.dhcp-fqdn: –

ipv4.never-default: no

ipv4.may-fail: yes

ipv4.dad-timeout: -1 (default)

ipv6.method: auto

ipv6.dns:

ipv6.dns-search:

ipv6.dns-options: (default)

ipv6.dns-priority: 0

ipv6.addresses:

ipv6.gateway: –

ipv6.routes:

ipv6.route-metric: -1

ipv6.ignore-auto-routes: no

ipv6.ignore-auto-dns: no

ipv6.never-default: no

ipv6.may-fail: yes

ipv6.ip6-privacy: -1 (unknown)

ipv6.addr-gen-mode: stable-privacy

ipv6.dhcp-send-hostname: yes

ipv6.dhcp-hostname: –

Hi Michael,

Thank you for posting your question on the Mellanox Community.

Based on the information provided, please follow Mellanox Community Document → https://community.mellanox.com/s/article/howto-configure-pfc-on-connectx-4 .

If after applying the Community document, the issue issue is not resolved, please open a Mellanox Support case by sending an email to support@mellanox.com mailto:support@mellanox.com

Thanks and regards,

~Mellanox Technical Support

Hi,

I’m not sure how HowTo Configure PFC on ConnectX-4 https://community.mellanox.com/s/article/howto-configure-pfc-on-connectx-4 article is helpful. It doesn’t relate to NetworkManager at all.

To whoever is reading this thread - this question is NOT answered as of this moment.