Bug 1647750

Summary: OVN: configurable dynamic mac range
Product: Red Hat Enterprise Linux 7 Reporter: lorenzo bianconi <lorenzo.bianconi>
Component: openvswitch2.10Assignee: lorenzo bianconi <lorenzo.bianconi>
Status: CLOSED ERRATA QA Contact: haidong li <haili>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.0CC: atelang, atragler, ctrautma, dalvarez, danken, fleitner, haili, igkioka, kfida, ovs-qe, qding
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: openvswitch2.10-2.10.0-26.el7fdn Doc Type: Enhancement
Doc Text:
This update adds the possibility to specify an OUI for MAC addresses dynamically allocated by OVN. As a result, users can specify an OUI for each OVN deployment to avoid MAC address collisions.
Story Points: ---
Clone Of: 1623260 Environment:
Last Closed: 2019-01-07 08:51:12 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On: 1623260    
Bug Blocks:    

Comment 3 haidong li 2018-11-26 09:12:57 UTC
verified on the latest version:
[root@dell-per730-42 ~]# uname -a
Linux dell-per730-42.rhts.eng.pek2.redhat.com 3.10.0-957.el7.x86_64 #1 SMP Thu Oct 4 20:48:51 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
[root@dell-per730-42 ~]# rpm -qa | grep openvswitch
[root@dell-per730-42 ~]# ovn-nbctl ls-add sw6
[root@dell-per730-42 ~]# ovn-nbctl  set NB_Global . options:mac_prefix="00:11:22:33:44:55"
[root@dell-per730-42 ~]# ovn-nbctl  set Logical-Switch sw6 other_config:subnet=
[root@dell-per730-42 ~]# ovn-nbctl lsp-add sw6 p6 -- lsp-set-addresses p6 dynamic
[root@dell-per730-42 ~]# ovn-nbctl get Logical-Switch-Port p6 dynamic_addresses
[root@dell-per730-42 ~]# ovn-nbctl lsp-add sw6 p7 -- lsp-set-addresses p7 dynamic
[root@dell-per730-42 ~]# ovn-nbctl get Logical-Switch-Port p7 dynamic_addresses
[root@dell-per730-42 ~]#

Comment 5 errata-xmlrpc 2019-01-07 08:51:12 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.