Mellanox ConnectX-3 EN duplicate permanent MAC address issue

Discussion in 'Networking' started by tedaz, Jun 12, 2019.

  1. tedaz

    tedaz New Member

    Joined:
    Nov 13, 2015
    Messages:
    5
    Likes Received:
    0
    I bought two second-hand ConnectX-3 (Model No CX311A, P/N MCX311A-XCAR) .
    These two cards work as expectation except these two cards have exact same permanent MAC address, please refer the attached photos and snapshot.

    The labels shown mac address should be "E4 1D 2D 6D XX XX", but the OS/driver shown mac address "00 02 C9 05 6A A8" for both cards.

    I've manually changed one card's "current mac address" to make them connectable. But it is really inconvenient to manually change the temperate mac every time after OS installing.

    It is definitely the permanent mac address been modified due to what ever purpose.

    Is there anyway to re-flash something to change the permanent mac address?
    a01.jpg
    a02.jpg
    a03.png
     
    #1
  2. klui

    klui Member

    Joined:
    Feb 3, 2019
    Messages:
    36
    Likes Received:
    16
    From http://mellanox28.rssing.com/chan-11024349/all_p4.html

    Use the flint utility. Per the thread:
    Code:
    # mst start
    
     Query the mac:
    # flint -d /dev/mst/mt25418_pci_cr0 -qq q
    
     Change the mac:
    # flint -d /dev/mst/mt25418_pci_cr0 -mac 02c90abcdef0 sg
    
     Change the GUID:
    # flint -d /dev/mst/mt25418_pci_cr0 -guid 0002c9000abcdef0 sg
    
    # flint -d /dev/mst/mt25418_pci_cr0 -qq q
     
    #2
    cesmith9999 and tedaz like this.
  3. tedaz

    tedaz New Member

    Joined:
    Nov 13, 2015
    Messages:
    5
    Likes Received:
    0
    Thanks for @klui help, yes, these two cards' permanent mac address successfully changed, and after the reboot the system, these two cards supported RDMA.

    Code:
    mst status -v
    
    MST devices:
    ------------
      mt4099_pci_cr0         bus:dev.fn=01:00.0
      mt4099_pciconf0        bus:dev.fn=01:00.0
    ============================================================
    flint -d /dev/mst/mt4099_pci_cr0 -qq q
    
    Image type:            FS2
    FW Version:            2.42.5000
    FW Release Date:       5.9.2017
    Product Version:       02.42.50.00
    Rom Info:              type=UEFI version=skipped cpu=skipped
                           type=PXE version=skipped devid=skipped cpu=skipped
    Device ID:             4099
    Description:           Node             Port1            Port2            Sys image
    GUIDs:                 0002c90300056aa8 0002c90300056aa9 0002c90300056aaa 0002c90300056aab
    MACs:                                       0002c9056aa8     0002c9056aa9
    VSD:
    PSID:                  MT_1170110023
    ============================================================
    flint -d /dev/mst/mt4099_pci_cr0 -mac E41D2D6DB6B0 sg
    
    -W- GUIDs are already set, re-burning image with the new GUIDs ...
        You are about to change the Guids/Macs/Uids on the device:
    
                            New Values              Current Values
            Node  GUID:     0002c90300056aa8        0002c90300056aa8
            Port1 GUID:     0002c90300056aa9        0002c90300056aa9
            Port2 GUID:     0002c90300056aaa        0002c90300056aaa
            Sys.Image GUID: 0002c90300056aab        0002c90300056aab
            Port1 MAC:          e41d2d6db6b0            0002c9056aa8
            Port2 MAC:          e41d2d6db6b1            0002c9056aa9
    
     Do you want to continue ? (y/n) [n] : Y
    Burning FS2 FW image without signatures - OK
    Restoring signature                     - OK
    ============================================================
    flint -d /dev/mst/mt4099_pci_cr0 -guid 00E41D2D6DB6B0 sg
    
    -W- GUIDs are already set, re-burning image with the new GUIDs ...
        You are about to change the Guids/Macs/Uids on the device:
    
                            New Values              Current Values
            Node  GUID:     0000e41d2d6db6b0        0002c90300056aa8
            Port1 GUID:     0000e41d2d6db6b1        0002c90300056aa9
            Port2 GUID:     0000e41d2d6db6b2        0002c90300056aaa
            Sys.Image GUID: 0000e41d2d6db6b3        0002c90300056aab
            Port1 MAC:          e41d2d6db6b0            e41d2d6db6b0
            Port2 MAC:          e41d2d6db6b1            e41d2d6db6b1
    
     Do you want to continue ? (y/n) [n] : y
    Burning FS2 FW image without signatures - OK
    Restoring signature                     - OK
    ============================================================
    flint -d /dev/mst/mt4099_pci_cr0 -qq q
    
    Image type:            FS2
    FW Version:            2.42.5000
    FW Release Date:       5.9.2017
    Product Version:       02.42.50.00
    Rom Info:              type=UEFI version=skipped cpu=skipped
                           type=PXE version=skipped devid=skipped cpu=skipped
    Device ID:             4099
    Description:           Node             Port1            Port2            Sys image
    GUIDs:                 0000e41d2d6db6b0 0000e41d2d6db6b1 0000e41d2d6db6b2 0000e41d2d6db6b3
    MACs:                                       e41d2d6db6b0     e41d2d6db6b1
    VSD:
    PSID:                  MT_1170110023
    ============================================================
    reboot the computer
     
    #3
  4. Terry Wallace

    Terry Wallace PsyOps SysOp

    Joined:
    Aug 13, 2018
    Messages:
    84
    Likes Received:
    35
    You got cards that a lazy person flashed with a upgrade. They flashed the same Mac onto multiple cards. You got it all fixed correctly though.
     
    #4
  5. tedaz

    tedaz New Member

    Joined:
    Nov 13, 2015
    Messages:
    5
    Likes Received:
    0
    These two cards also experiencing "Wrong VPD format" issue, would you please give me a help?

    Code:
    mlxburn -d mt4099_pciconf0 -vpd
    -E- Failed to Read VPD: -E- Wrong VPD format
    child process exited abnormally
    Code:
    mlxburn -d mt4099_pci_cr0 -vpd
    -E- Failed to Read VPD: -E- Wrong VPD format
    child process exited abnormally
     
    #5
Similar Threads: Mellanox ConnectX-3
Forum Title Date
Networking Mellanox ConnectX-3 ejectable Thursday at 10:15 PM
Networking Mellanox ConnectX-3 Low File Transfer Speed Sep 9, 2019
Networking Mellanox ConnectX-3 VPI Twinax compatibility with Cisco Nexus 3064 Aug 14, 2019
Networking Mellanox ConnectX-3 EN "Wrong VPD format" issue Jun 20, 2019
Networking Proxmox 5.4, HP Flashed Mellanox Connectx-3, pfSense = issue May 28, 2019

Share This Page