documentation-packages team mailing list archive

[Steve Langasek <steve.langasek@xxxxxxxxxxxxx>]

I don't find this request very clear.  Several questions:
 - What release are you seeking to have this release noted for?  tags suggest 17.04 or 17.10 or both, but neither of these are LTS releases, so I have to question whether the tags are correct.
 - Is the lack of persistent mac addresses a problem with the kernel driver?  With the underlying hardware?
 - In what environment should we expect to see this problem?  Is it POWER-specific?
 - The workaround suggested appears to be a one-off change, that would still not persist across reboots of the system (or perhaps the state persists within the VM, but would not persist across a cold boot).  Have I understood correctly?  If so, this does not seem like a complete workaround that warrants recommending to users in the release notes.
 - Why is this being suggested as a release notes change, instead of a request for a fix in the implementation?

** Changed in: ubuntu-release-notes
       Status: New => Incomplete

-- 
You received this bug notification because you are a member of
Documentation Packages, which is subscribed to ubuntu-docs in Ubuntu.
https://bugs.launchpad.net/bugs/1689616

Title:
  [SR-IOV]: Use static MAC addresses with udev rules for renaming VF
  interfaces (Mellanox CX4) (Documentation)

Status in The Ubuntu-power-systems project:
  New
Status in Release Notes for Ubuntu:
  Incomplete
Status in ubuntu-docs package in Ubuntu:
  Invalid

Bug description:
  Problem Description
  =============
  The udev rules for renaming the SR-IOV Mellanox CX4 VF interface are not getting
  implemented. After setting the udev rules, and unbind/bind the drivers for the VF's, 
  the interface name still doesn't change. Same issue isn't noticed for the PF of the
  SR-IOV adapter.
   
  Resolution
  =======
  Use static MAC addresses for renaming SRIOV Mellanox CX4 VF interfaces with udev rules.

  Documentation
  ==========
  With Mellanox CX4 SR-IOV when the VFs are created, each of them will get a random MAC address. 
  To be able to use the '70-persistent-net.rules' to define interfaces based on MAC Address, one need
  to set static MAC address to the VF. 

  This is an example
  SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="02:a9:bb:cc:dd:00", NAME="enP4p1s0vf"

  First execute below command 
  echo 02:a9:bb:cc:dd:00 > /sys/class/infiniband/mlx5_0/device/sriov/0/mac

  and then 
  do the unbind/bind
  echo 0004:01:00.2 > /sys/bus/pci/drivers/mlx5_core/unbind
  echo 0004:01:00.2 > /sys/bus/pci/drivers/mlx5_core/bind

  then one can see  
  enP4p1s0vf: flags=4098<BROADCAST,MULTICAST>  mtu 1500
          ether 02:a9:bb:cc:dd:00  txqueuelen 1000  (Ethernet)
          RX packets 0  bytes 0 (0.0 B)
          RX errors 0  dropped 0  overruns 0  frame 0
          TX packets 0  bytes 0 (0.0 B)
          TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1689616/+subscriptions