Ethernet interface show no-carrier and in down state

I am setting up networking on MAAS to install Openstack by Juju.
I have 8 different subnets on 4 interfaces. So I create vlan interfaces.
With the same configuration, after deploy ubuntu 20.04 focal. 2 of them show as degraded and up, 2 are in down and no-carrier. Did I do something wrong on configuration ?. Please help me on this case.

This is some information:

ubuntu@S0039:~$ networkctl
IDX LINK TYPE OPERATIONAL SETUP
1 lo loopback carrier unmanaged
2 eno1 ether routable configured
3 eno2 ether no-carrier configuring
4 eno3 ether no-carrier configured
5 eno4 ether no-carrier configured
6 ens1f0 ether degraded configured
7 ens1f1 ether degraded configured
8 ens1f1.33 vlan routable configured
9 ens1f0.32 vlan routable configured
10 eno4.28 vlan no-carrier configured
11 eno4.31 vlan no-carrier configured
12 eno4.34 vlan no-carrier configured
13 eno3.29 vlan no-carrier configured
14 eno3.30 vlan no-carrier configured

ubuntu@S0039:~$ systemctl status -l systemd-networkd.service
● systemd-networkd.service - Network Service
Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled; vendor preset: enabled)
Active: active (running) since Sat 2020-06-06 15:46:41 UTC; 41min ago
TriggeredBy: ● systemd-networkd.socket
Docs: man:systemd-networkd.service(8)
Main PID: 1148 (systemd-network)
Status: “Processing requests…”
Tasks: 1 (limit: 37786)
Memory: 5.4M
CGroup: /system.slice/systemd-networkd.service
└─1148 /lib/systemd/systemd-networkd
Jun 06 15:46:51 ubuntu systemd-networkd[1148]: eno4.34: Gained IPv6LL
Jun 06 15:46:51 ubuntu systemd-networkd[1148]: eno3: Gained IPv6LL
Jun 06 15:46:51 ubuntu systemd-networkd[1148]: eno3.29: Gained IPv6LL
Jun 06 15:46:52 ubuntu systemd-networkd[1148]: eno3: Lost carrier
Jun 06 15:46:52 ubuntu systemd-networkd[1148]: eno3.29: Lost carrier
Jun 06 15:46:52 ubuntu systemd-networkd[1148]: eno3.30: Lost carrier
Jun 06 15:46:53 ubuntu systemd-networkd[1148]: ens1f1: Gained carrier
Jun 06 15:46:53 ubuntu systemd-networkd[1148]: ens1f1.33: Gained carrier
Jun 06 15:46:55 ubuntu systemd-networkd[1148]: ens1f1: Gained IPv6LL
Jun 06 15:46:55 ubuntu systemd-networkd[1148]: ens1f1.33: Gained IPv6LL

ubuntu@S0039:~$ cat /var/log/syslog | grep eno3
Jun 6 15:48:43 S0039 systemd-networkd[1148]: eno3: IPv6 successfully enabled
Jun 6 15:48:43 S0039 systemd-networkd[1148]: eno3.29: netdev ready
Jun 6 15:48:43 S0039 systemd-networkd[1148]: eno3.30: netdev ready
Jun 6 15:48:43 S0039 systemd-networkd[1148]: eno3.29: IPv6 successfully enabled
Jun 6 15:48:43 S0039 systemd-networkd[1148]: eno3.30: IPv6 successfully enabled
Jun 6 15:48:43 S0039 systemd-networkd[1148]: eno3: Link UP
Jun 6 15:48:43 S0039 systemd-networkd[1148]: eno3.29: Link UP
Jun 6 15:48:43 S0039 systemd-networkd[1148]: eno3.30: Link UP
Jun 6 15:48:43 S0039 systemd-networkd[1148]: eno3: Gained carrier
Jun 6 15:48:43 S0039 systemd-networkd[1148]: eno3.29: Gained carrier
Jun 6 15:48:43 S0039 systemd-networkd[1148]: eno3.30: Gained carrier
Jun 6 15:48:43 S0039 systemd-networkd[1148]: eno3.30: Gained IPv6LL
Jun 6 15:48:43 S0039 systemd-networkd[1148]: eno3: Gained IPv6LL
Jun 6 15:48:43 S0039 systemd-networkd[1148]: eno3.29: Gained IPv6LL
Jun 6 15:48:43 S0039 systemd-networkd[1148]: eno3: Lost carrier
Jun 6 15:48:43 S0039 systemd-networkd[1148]: eno3.29: Lost carrier
Jun 6 15:48:43 S0039 systemd-networkd[1148]: eno3.30: Lost carrier
Jun 6 15:48:43 S0039 systemd-networkd-wait-online[1149]: managing: eno3.29
Jun 6 15:48:43 S0039 systemd-networkd-wait-online[1149]: managing: eno3.29
Jun 6 15:48:43 S0039 cloud-init[1221]: ci-info: | eno3 | False | fe80::e643:4bff:feaa:c82/64 | . | link | e4:43:4b:aa:0c:82 |
Jun 6 15:48:43 S0039 cloud-init[1221]: ci-info: | eno3.29 | False | 192.168.29.39 | 255.255.255.0 | global | e4:43:4b:aa:0c:82 |
Jun 6 15:48:43 S0039 cloud-init[1221]: ci-info: | eno3.29 | False | fe80::e643:4bff:feaa:c82/64 | . | link | e4:43:4b:aa:0c:82 |
Jun 6 15:48:43 S0039 cloud-init[1221]: ci-info: | eno3.30 | False | 192.168.30.39 | 255.255.255.0 | global | e4:43:4b:aa:0c:82 |
Jun 6 15:48:43 S0039 cloud-init[1221]: ci-info: | eno3.30 | False | fe80::e643:4bff:feaa:c82/64 | . | link | e4:43:4b:aa:0c:82 |
Jun 6 15:48:43 S0039 cloud-init[1221]: ci-info: | 3 | 192.168.29.0 | 0.0.0.0 | 255.255.255.0 | eno3.29 | U |
Jun 6 15:48:43 S0039 cloud-init[1221]: ci-info: | 4 | 192.168.30.0 | 0.0.0.0 | 255.255.255.0 | eno3.30 | U |
Jun 6 15:48:43 S0039 cloud-init[1221]: ci-info: | 8 | fe80::/64 | :: | eno3 | U |
Jun 6 15:48:43 S0039 cloud-init[1221]: ci-info: | 9 | fe80::/64 | :: | eno3.29 | U |
Jun 6 15:48:43 S0039 cloud-init[1221]: ci-info: | 10 | fe80::/64 | :: | eno3.30 | U |
Jun 6 15:48:43 S0039 cloud-init[1221]: ci-info: | 19 | local | :: | eno3.30 | U |
Jun 6 15:48:43 S0039 cloud-init[1221]: ci-info: | 20 | local | :: | eno3 | U |
Jun 6 15:48:43 S0039 cloud-init[1221]: ci-info: | 21 | local | :: | eno3.29 | U |
Jun 6 15:48:43 S0039 cloud-init[1221]: ci-info: | 33 | ff00::/8 | :: | eno3 | U |
Jun 6 15:48:43 S0039 cloud-init[1221]: ci-info: | 34 | ff00::/8 | :: | eno3.29 | U |
Jun 6 15:48:43 S0039 cloud-init[1221]: ci-info: | 35 | ff00::/8 | :: | eno3.30 | U |
Jun 6 15:48:43 S0039 kernel: [ 9.131583] ixgbe 0000:19:00.0 eno3: renamed from eth2
Jun 6 15:48:43 S0039 kernel: [ 15.240846] ixgbe 0000:19:00.0: registered PHC device on eno3
Jun 6 15:48:43 S0039 kernel: [ 15.375305] 8021q: adding VLAN 0 to HW filter on device eno3
Jun 6 15:48:43 S0039 kernel: [ 21.891315] ixgbe 0000:19:00.0 eno3: NIC Link is Up 10 Gbps, Flow Control: None
Jun 6 15:48:43 S0039 kernel: [ 21.891474] IPv6: ADDRCONF(NETDEV_CHANGE): eno3: link becomes ready
Jun 6 15:48:43 S0039 kernel: [ 21.891946] IPv6: ADDRCONF(NETDEV_CHANGE): eno3.29: link becomes ready
Jun 6 15:48:43 S0039 kernel: [ 21.891975] IPv6: ADDRCONF(NETDEV_CHANGE): eno3.30: link becomes ready
Jun 6 15:48:43 S0039 kernel: [ 23.575520] ixgbe 0000:19:00.0 eno3: NIC Link is Down

Hi ,
I disabled spanning-tree on the switch, the port is up now. I don’t know why, because this switch has no uplink port. Maybe I will ask the support from our networking team.
Sorry for bothering you.
Thanks,
Kien

@ritzttk, no worries. hope you get it sorted out; if not, the forum is always here!