[openstack-dev] [tripleo] What is the proper way to use NetConfigDataLookup?

2018-07-06 Thread Mark Hamzy 
What is the proper way to use NetConfigDataLookup?  I tried the following:

(undercloud) [stack@oscloud5 ~]$ cat << '__EOF__' > 
~/templates/mapping-info.yaml
parameter_defaults:
  NetConfigDataLookup:
  control1:
nic1: '5c:f3:fc:36:dd:68'
nic2: '5c:f3:fc:36:dd:6c'
nic3: '6c:ae:8b:29:27:fa' # 9.114.219.34
nic4: '6c:ae:8b:29:27:fb' # 9.114.118.???
nic5: '6c:ae:8b:29:27:fc'
nic6: '6c:ae:8b:29:27:fd'
  compute1:
nic1: '6c:ae:8b:25:34:ea' # 9.114.219.44
nic2: '6c:ae:8b:25:34:eb'
nic3: '6c:ae:8b:25:34:ec' # 9.114.118.???
nic4: '6c:ae:8b:25:34:ed'
  compute2:
nic1: '00:0a:f7:73:3c:c0'
nic2: '00:0a:f7:73:3c:c1'
nic3: '00:0a:f7:73:3c:c2' # 9.114.118.156
nic4: '00:0a:f7:73:3c:c3' # 9.114.112.???
nic5: '00:0a:f7:73:73:f4'
nic6: '00:0a:f7:73:73:f5'
nic7: '00:0a:f7:73:73:f6' # 9.114.219.134
nic8: '00:0a:f7:73:73:f7'
__EOF__
(undercloud) [stack@oscloud5 ~]$ openstack overcloud deploy --templates -e 
~/templates/node-info.yaml -e ~/templates/mapping-info.yaml -e 
~/templates/overcloud_images.yaml -e 
~/templates/environments/network-environment.yaml -e 
~/templates/environments/network-isolation.yaml -e 
~/templates/environments/config-debug.yaml --disable-validations 
--ntp-server pool.ntp.org --control-scale 1 --compute-scale

But I did not see a /etc/os-net-config/mapping.yaml get created.

Also is this configuration used when the system boots IronicPythonAgent to 
provision the disk?

-- 
Mark

You must be the change you wish to see in the world. -- Mahatma Gandhi
Never let the future disturb you. You will meet it, if you have to, with 
the same weapons of reason which today arm you against the present. -- 
Marcus Aurelius

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [tripleo][heat][jinja] resources.RedisVirtualIP: Property error: resources.VipPort.properties.network: Error validating value 'internal_api': Unable to find network with name or id 'in

2018-06-14 Thread Mark Hamzy 
I am trying to delete the Storage, StorageMgmt, Tenant, and Management 
networks and trying to deploy using TripleO.

The following patch 
https://hamzy.fedorapeople.org/0001-RedisVipPort-error-internal_api.patch 
applied on top of /usr/share/openstack-tripleo-heat-templates from 
openstack-tripleo-heat-templates-8.0.2-14.el7ost.noarch

yields the following error:

(undercloud) [stack@oscloud5 ~]$ openstack overcloud deploy --templates -e 
~/templates/node-info.yaml -e ~/templates/overcloud_images.yaml -e 
~/templates/environments/network-environment.yaml -e 
~/templates/environments/network-isolation.yaml -e 
~/templates/environments/config-debug.yaml --ntp-server pool.ntp.org 
--control-scale 1 --compute-scale 1 --control-flavor control 
--compute-flavor compute 2>&1 | tee output.overcloud.deploy
...
overcloud.RedisVirtualIP:
  resource_type: OS::TripleO::Network::Ports::RedisVipPort
  physical_resource_id:
  status: CREATE_FAILED
  status_reason: |
resources.RedisVirtualIP: Property error: 
resources.VipPort.properties.network: Error validating value 
'internal_api': Unable to find network with name or id 'internal_api'
...

The following patch seems to fix it:

8<-8<-8<-8<-8<-
diff --git a/environments/network-isolation.j2.yaml 
b/environments/network-isolation.j2.yaml
index 3d4f59b..07cb748 100644
--- a/environments/network-isolation.j2.yaml
+++ b/environments/network-isolation.j2.yaml
@@ -20,7 +20,13 @@ resource_registry:
   {%- for network in networks if network.vip and 
network.enabled|default(true) %}
   OS::TripleO::Network::Ports::{{network.name}}VipPort: 
../network/ports/{{network.name_lower|default(network.name.lower())}}.yaml
   {%- endfor %}
+{%- for role in roles -%}
+  {%- if internal_api in role.networks|default([]) and 
internal_api.enabled|default(true) %}
   OS::TripleO::Network::Ports::RedisVipPort: ../network/ports/vip.yaml
+  {%- else %}
+  # Avoid weird jinja2 bugs that don't output a newline...
+  {%- endif %}
+{%- endfor -%}
 
   # Port assignments by role, edit role definition to assign networks to 
roles.
 {%- for role in roles %}
8<-8<-8<-8<-8<-

Note that I had to do an else clause because jinja2 would not output the 
newline that was outside of the for block.

Am I following the correct path to fix this issue?

-- 
Mark

You must be the change you wish to see in the world. -- Mahatma Gandhi
Never let the future disturb you. You will meet it, if you have to, with 
the same weapons of reason which today arm you against the present. -- 
Marcus Aurelius

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [tripleo][heat] where does ip_netmask in network_config come from?

2018-06-06 Thread Mark Hamzy 
When the system boots up, the IP addresses seem correct:

Jun  6 12:43:07 overcloud-controller-0 cloud-init: ci-info: | eno5:  | 
True |   .   |   .   |   .   | 6c:ae:8b:25:34:ed |
Jun  6 12:43:07 overcloud-controller-0 cloud-init: ci-info: | eno4:  | 
True | 9.114.118.241 | 255.255.255.0 |   .   | 6c:ae:8b:25:34:ec |
Jun  6 12:43:07 overcloud-controller-0 cloud-init: ci-info: | eno4:  | 
True |   .   |   .   |   d   | 6c:ae:8b:25:34:ec |
Jun  6 12:43:07 overcloud-controller-0 cloud-init: ci-info: | 
enp0s29u1u1u5: | True |   .   |   .   |   .   | 
6e:ae:8b:25:34:e9 |
Jun  6 12:43:07 overcloud-controller-0 cloud-init: ci-info: | 
enp0s29u1u1u5: | True |   .   |   .   |   d   | 
6e:ae:8b:25:34:e9 |
Jun  6 12:43:07 overcloud-controller-0 cloud-init: ci-info: |  lo:   | 
True |   127.0.0.1   |   255.0.0.0   |   .   | . |
Jun  6 12:43:07 overcloud-controller-0 cloud-init: ci-info: |  lo:   | 
True |   .   |   .   |   d   | . |
Jun  6 12:43:07 overcloud-controller-0 cloud-init: ci-info: | eno3:  | 
True | 9.114.219.197 | 255.255.255.0 |   .   | 6c:ae:8b:25:34:eb |
Jun  6 12:43:07 overcloud-controller-0 cloud-init: ci-info: | eno3:  | 
True |   .   |   .   |   d   | 6c:ae:8b:25:34:eb |
Jun  6 12:43:07 overcloud-controller-0 cloud-init: ci-info: | eno2:  | 
True |  9.114.219.44 | 255.255.255.0 |   .   | 6c:ae:8b:25:34:ea |
Jun  6 12:43:07 overcloud-controller-0 cloud-init: ci-info: | eno2:  | 
True |   .   |   .   |   d   | 6c:ae:8b:25:34:ea |

However, I am seeing the following when run-os-net-config.sh is run.  I 
put in a (sudo ip route; sudo ip -o address; sudo ip route get to 
${METADATA_IP}) before the ping check:

default via 9.114.219.254 dev eno3 proto dhcp metric 101
9.114.219.0/24 dev br-ex proto kernel scope link src 9.114.219.193
9.114.219.0/24 dev eno2 proto kernel scope link src 9.114.219.193
9.114.219.0/24 dev eno3 proto kernel scope link src 9.114.219.197 metric 
101
169.254.95.0/24 dev enp0s29u1u1u5 proto kernel scope link src 
169.254.95.120 metric 103
169.254.169.254 via 9.114.219.30 dev eno2

1: loinet 127.0.0.1/8 scope host lo\   valid_lft forever 
preferred_lft forever
1: loinet6 ::1/128 scope host \   valid_lft forever preferred_lft 
forever
2: eno2inet 9.114.219.193/24 brd 9.114.219.255 scope global eno2\  
valid_lft forever preferred_lft forever
2: eno2inet6 fe80::6eae:8bff:fe25:34ea/64 scope link tentative \ 
valid_lft forever preferred_lft forever
3: eno3inet 9.114.219.197/24 brd 9.114.219.255 scope global 
noprefixroute dynamic eno3\   valid_lft 538sec preferred_lft 538sec
3: eno3inet6 fd55:faaf:e1ab:3d9:6eae:8bff:fe25:34eb/64 scope global 
mngtmpaddr dynamic \   valid_lft 2591961sec preferred_lft 604761sec
3: eno3inet6 fe80::6eae:8bff:fe25:34eb/64 scope link \   valid_lft 
forever preferred_lft forever
6: enp0s29u1u1u5inet 169.254.95.120/24 brd 169.254.95.255 scope link 
noprefixroute dynamic enp0s29u1u1u5\   valid_lft 539sec preferred_lft 
539sec
6: enp0s29u1u1u5inet6 fe80::6cae:8bff:fe25:34e9/64 scope link \ 
valid_lft forever preferred_lft forever
8: br-exinet 9.114.219.193/24 brd 9.114.219.255 scope global br-ex\  
valid_lft forever preferred_lft forever
8: br-exinet6 fe80::6eae:8bff:fe25:34ec/64 scope link \ valid_lft 
forever preferred_lft forever

9.114.219.30 dev br-ex src 9.114.219.193
cache

Trying to ping metadata IP 9.114.219.30...FAILURE

It seems  like the data is coming from:

[root@overcloud-controller-0 ~]# cat /etc/os-net-config/config.json 
{"network_config": [{"addresses": [{"ip_netmask": "9.114.219.196/24"}], 
"dns_servers": ["8.8.8.8", "8.8.4.4"], "name": "nic1", "routes": 
[{"ip_netmask": "169.254.169.254/32", "next_hop": "9.114.219.30"}], 
"type": "interface", "use_dhcp": false}, {"addresses": [{"ip_netmask": 
"9.114.219.196/24"}], "dns_servers": ["8.8.8.8", "8.8.4.4"], "members": 
[{"name": "nic3", "primary": true, "type": "interface"}], "name": "br-ex", 
"routes": [{"default": true, "next_hop": "9.114.118.254"}], "type": 
"ovs_bridge", "use_dhcp": false}]}

Also in the log I see:

...
Jun  6 12:45:15 overcloud-controller-0 os-collect-config: [2018/06/06 
12:43:53 PM] [INFO] Active nics are ['eno2', 'eno3', 'eno4']
Jun  6 12:45:15 overcloud-controller-0 os-collect-config: [2018/06/06 
12:43:53 PM] [INFO] nic1 mapped to: eno2
Jun  6 12:45:15 overcloud-controller-0 os-collect-config: [2018/06/06 
12:43:53 PM] [INFO] nic2 mapped to: eno3
Jun  6 12:45:15 overcloud-controller-0 os-collect-config: [2018/06/06 
12:43:53 PM] [INFO] nic3 mapped to: eno4
...

templates/nic-configs/controller.yaml has the following section:
...
$network_config:
  network_config:
  - type: interface
name: nic1
use_dhcp: false
dns_servers:

Re: [openstack-dev] [tripleo] Blueprints moved out to Rocky

2017-12-14 Thread Mark Hamzy 
Alex Schultz <aschu...@redhat.com> wrote on 12/14/2017 09:24:54 AM:
> On Wed, Dec 13, 2017 at 6:36 PM, Mark Hamzy <ha...@us.ibm.com> wrote:
> ... As I said previously, please post the
> patches ASAP so we can get eyes on these changes.  Since this does
> have an impact on the existing functionality this should have been
> merged earlier in the cycle so we could work out any user facing
> issues.

Sorry about that.
https://review.openstack.org/#/c/528000/
https://review.openstack.org/#/c/528060/

I will see how easy it is to also support the old naming convention...

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tripleo] Blueprints moved out to Rocky

2017-12-13 Thread Mark Hamzy 
Alex Schultz <aschu...@redhat.com> wrote on 12/13/2017 04:29:49 PM:
> On Wed, Dec 13, 2017 at 3:22 PM, Mark Hamzy <ha...@us.ibm.com> wrote:
> > What I have done at a high level is to rename the images into 
architecture
> > specific
> > images.  For example,
> >
> > (undercloud) [stack@oscloud5 ~]$ openstack image list
> > +--
> +---++
> > | ID   | Name |
> > Status |
> > +--
> +---++
> > | fa0ed7cb-21d7-427b-b8cb-7c62f0ff7760 | ppc64le-bm-deploy-kernel |
> > active |
> > | 94dc2adf-49ce-4db5-b914-970b57a8127f | ppc64le-bm-deploy-ramdisk |
> > active |
> > | 6c50587d-dd29-41ba-8971-e0abf3429020 | ppc64le-overcloud-full |
> > active |
> > | 59e512a7-990e-4689-85d2-f1f4e1e6e7a8 | x86_64-bm-deploy-kernel |
> > active |
> > | bcad2821-01be-4556-b686-31c70bb64716 | x86_64-bm-deploy-ramdisk |
> > active |
> > | 3ab489fa-32c7-4758-a630-287c510fc473 | x86_64-overcloud-full |
> > active |
> > | 661f18f7-4d99-43e8-b7b8-f5c8a9d5b116 | x86_64-overcloud-full-initrd 
|
> > active |
> > | 4a09c422-3de0-46ca-98c3-7c6f1f7717ff | x86_64-overcloud-full-vmlinuz 
|
> > active |
> > +--
> +---++
> >
> > This will change existing functionality.
> >
> 
> Any chance of backwards compatibility if no arch is specified in the
> image list so it's not that impacting?

The patch as currently coded does not do that.  It is more consistent and
cleaner as it is currently written.  How opposed is the community to a
new convention?  I know we are pushing up against holidays and deadlines 
and
don't know how much longer it will take to also support the old naming
convention.

RedHat is asking for another identifier along with ppc64le given that 
there are
different optimizations and CPU instructions between a Power 8 system and 
a
Power 9 system.  The kernel is certainly different and the base operating
system might be as well.

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tripleo] Blueprints moved out to Rocky

2017-12-13 Thread Mark Hamzy 
> I just need an understanding on the impact and the timeline. Replying
> here is sufficient.
> 
> I assume since some of this work was sort of done earlier outside of
> tripleo and does not affect the default installation path that most
> folks will consume, it shouldn't be impacting to general testing or
> increase regressions. My general requirement for anyone who needed an
> FFE for functionality that isn't essential is that it's off by
> default, has minimal impact to the existing functionality and we have
> a rough estimate on feature landing.  Do you have idea when you expect
> to land this functionality? Additionally the patches seem to be
> primarily around the ironic integration so have those been sorted out?

I have been working on a multi-architecture patch for TripleO and am 
almost
ready to submit a WIP to r.o.o.  I have delayed until I can get all of the
testcases passing.

Currently the patches exist at:
https://hamzy.fedorapeople.org/TripleO-multi-arch/05.bb2b96e/0001-fix_multi_arch-tripleo-common.patch

https://hamzy.fedorapeople.org/TripleO-multi-arch/05.cc5fee3/0001-fix_multi_arch-python-tripleoclient.patch
 


And the full installation instructions are at:
https://fedoraproject.org/wiki/User:Hamzy/TripleO_mixed_undercloud_overcloud_try9

What I have done at a high level is to rename the images into architecture 
specific
images.  For example,

(undercloud) [stack@oscloud5 ~]$ openstack image list
+--+---++
| ID   | Name  | 
Status |
+--+---++
| fa0ed7cb-21d7-427b-b8cb-7c62f0ff7760 | ppc64le-bm-deploy-kernel  | 
active |
| 94dc2adf-49ce-4db5-b914-970b57a8127f | ppc64le-bm-deploy-ramdisk | 
active |
| 6c50587d-dd29-41ba-8971-e0abf3429020 | ppc64le-overcloud-full| 
active |
| 59e512a7-990e-4689-85d2-f1f4e1e6e7a8 | x86_64-bm-deploy-kernel   | 
active |
| bcad2821-01be-4556-b686-31c70bb64716 | x86_64-bm-deploy-ramdisk  | 
active |
| 3ab489fa-32c7-4758-a630-287c510fc473 | x86_64-overcloud-full | 
active |
| 661f18f7-4d99-43e8-b7b8-f5c8a9d5b116 | x86_64-overcloud-full-initrd  | 
active |
| 4a09c422-3de0-46ca-98c3-7c6f1f7717ff | x86_64-overcloud-full-vmlinuz | 
active |
+--+---++

This will change existing functionality.

I still need to work with RedHat on changing the patch for their needs, 
but it currently can
deploy an x86_64 undercloud, an x86_64 overcloud controller node and a 
ppc64le overcloud
compute node.

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [tripleo] control_virtual_ip and corosync

2017-10-23 Thread Mark Hamzy 
I am seeing "Can't connect to MySQL server on '9.114.118.250' ([Errno 113] 
EHOSTUNREACH)" when installing tripleo

Debugging it further, it seems that corosync will not start and returns an 
error code of 8.  This seems like not an error according to:

http://www.linux-ha.org/doc/dev-guides/_literal_ocf_running_master_literal_8.html

"The resource was found to be running in the Master role. This applies 
only to stateful (Master/Slave) resources, and only to their monitor 
action."

There is only one control baremetal node.

Further details are found in:

https://fedoraproject.org/wiki/User:Hamzy/TripleO_mixed_undercloud_overcloud_try8

-- 
Mark

You must be the change you wish to see in the world. -- Mahatma Gandhi
Never let the future disturb you. You will meet it, if you have to, with 
the same weapons of reason which today arm you against the present. -- 
Marcus Aurelius

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tripleo] Looking for help in properly configuring a TripleO environment

2017-10-23 Thread Mark Hamzy 
Joe Talerico  wrote on 10/09/2017 11:26:14 AM:

> If you ssh to your compute node can you ping 172.16.0.14?

Just a quick note to let everyone know that I am no longer seeing this 
problem.
I had to wait a while for lab services to update the firmware and then I 
was
seeing IP conflicts with rogue boxes on my DHCP range.

It seems that recent checkins to THT fixed this issue...


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [tripleo] Looking for help in properly configuring a TripleO environment

2017-10-09 Thread Mark Hamzy 
I am looking for help in properly configuring a TripleO environment on a 
machine with two network cards talking to two baremetal nodes in the 
overcloud also with two network cards.  One network will be for 
provisioning and one will be for internet connection.  I have documented 
my current configuration at:

https://fedoraproject.org/wiki/User:Hamzy/TripleO_mixed_undercloud_overcloud_try8


2017-09-23 23:54:49Z [overcloud.ControllerAllNodesValidationDeployment.0]: 
CREATE_COMPLETE  state changed
2017-09-23 23:54:49Z [overcloud.ControllerAllNodesValidationDeployment]: 
CREATE_COMPLETE  Stack CREATE completed successfully
2017-09-23 23:54:49Z [overcloud.ControllerAllNodesValidationDeployment]: 
CREATE_COMPLETE  state changed
2017-09-24 00:05:06Z [overcloud.ComputeAllNodesValidationDeployment.0]: 
SIGNAL_IN_PROGRESS  Signal: deployment d54b96a6-1860-4802-a$
45-db4ece0317e4 failed (1)
2017-09-24 00:05:06Z [overcloud.ComputeAllNodesValidationDeployment.0]: 
CREATE_FAILED  Error: resources[0]: Deployment to server fa$led: 
deploy_status_code : Deployment exited with non-zero status code: 1
2017-09-24 00:05:06Z [overcloud.ComputeAllNodesValidationDeployment]: 
CREATE_FAILED  Resource CREATE failed: Error: resources[0]: D$ployment to 
server failed: deploy_status_code : Deployment exited with non-zero status 
code: 1
2017-09-24 00:05:07Z [overcloud.ComputeAllNodesValidationDeployment]: 
CREATE_FAILED  Error: 
resources.ComputeAllNodesValidationDepl$yment.resources[0]: Deployment to 
server failed: deploy_status_code: Deployment exited with non-zero status 
code: 1
2017-09-24 00:05:07Z [overcloud]: CREATE_FAILED  Resource CREATE failed: 
Error: resources.ComputeAllNodesValidationDeployment.resou$ces[0]: 
Deployment to server failed: deploy_status_code: Deployment exited with 
non-zero status code: 1

 Stack overcloud CREATE_FAILED 

overcloud.ComputeAllNodesValidationDeployment.0:
  resource_type: OS::Heat::StructuredDeployment
  physical_resource_id: d54b96a6-1860-4802-ad45-db4ece0317e4
  status: CREATE_FAILED
  status_reason: |
Error: resources[0]: Deployment to server failed: deploy_status_code : 
Deployment exited with non-zero status code: 1
  deploy_stdout: |
...
Ping to 172.16.0.14 failed. Retrying...
Ping to 172.16.0.14 failed. Retrying...
Ping to 172.16.0.14 failed. Retrying...
Ping to 172.16.0.14 failed. Retrying...
Ping to 172.16.0.14 failed. Retrying...
Ping to 172.16.0.14 failed. Retrying...
Ping to 172.16.0.14 failed. Retrying...
Ping to 172.16.0.14 failed. Retrying...
Ping to 172.16.0.14 failed. Retrying...
FAILURE
(truncated, view all with --long)
  deploy_stderr: |
172.16.0.14 is not pingable. Local Network: 172.16.0.0/24

Burried somewhat in that URL was the following way to view my templates:

cp -r /usr/share/openstack-tripleo-heat-templates templates
(cd templates/; wget --quiet -O - 
https://hamzy.fedorapeople.org/openstack-tripleo-heat-templates.patch | 
patch -p1)

The controller and compute do install and get IP address from DHCP:

[hamzy@overcloud-controller-0 ~]$ ip a
1: lo:  mtu 65536 qdisc noqueue state UNKNOWN qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
   valid_lft forever preferred_lft forever
inet6 ::1/128 scope host 
   valid_lft forever preferred_lft forever
2: enP1p3s0f0:  mtu 1500 qdisc mq 
portid 98be9454b240 state DOWN qlen 1000
link/ether 98:be:94:54:b2:40 brd ff:ff:ff:ff:ff:ff
3: enP1p3s0f1:  mtu 1500 qdisc mq 
portid 98be9454b242 state DOWN qlen 1000
link/ether 98:be:94:54:b2:42 brd ff:ff:ff:ff:ff:ff
4: enP1p5s0f0:  mtu 1500 qdisc mq 
portid 98be94546360 state DOWN qlen 1000
link/ether 98:be:94:54:63:60 brd ff:ff:ff:ff:ff:ff
5: enP1p5s0f1:  mtu 1500 qdisc mq 
portid 98be94546362 state DOWN qlen 1000
link/ether 98:be:94:54:63:62 brd ff:ff:ff:ff:ff:ff
6: enP3p11s0f0:  mtu 1500 qdisc mq 
portid 40f2e9316940 state DOWN qlen 1000
link/ether 40:f2:e9:31:69:40 brd ff:ff:ff:ff:ff:ff
7: enP3p11s0f1:  mtu 1500 qdisc mq 
portid 40f2e9316942 state DOWN qlen 1000
link/ether 40:f2:e9:31:69:42 brd ff:ff:ff:ff:ff:ff
8: enP6p1s0f0:  mtu 1500 qdisc mq 
portid 98be94541f80 state DOWN qlen 1000
link/ether 98:be:94:54:1f:80 brd ff:ff:ff:ff:ff:ff
9: enP6p1s0f1:  mtu 1500 qdisc mq 
portid 98be94541f82 state DOWN qlen 1000
link/ether 98:be:94:54:1f:82 brd ff:ff:ff:ff:ff:ff
10: enP3p5s0f0:  mtu 1500 qdisc mq 
portid 01304534323130363730453131 state DOWN qlen 1000
link/ether 00:90:fa:74:05:50 brd ff:ff:ff:ff:ff:ff
11: enP3p5s0f1:  mtu 1500 qdisc mq 
portid