Unsolved
This post is more than 5 years old
1 Message
0
2395
M610 w/ BCM-57711 Failed to program virtual MAC on M8024
Just testing out some lab gear, running a few blades with BCM-57711 modules, in our B mezz slot, with M8024 switch blades.
When we power them up we get the following error messages:
Thu Dec 08 2016 19:10:25 Failed to program virtual MAC address on a component at bus 3 device 0 function 1.
Thu Dec 08 2016 19:10:25 Failed to program virtual MAC address on a component at bus 3 device 0 function 0.
As far as I can tell, everything is on the latest firmware edition (CMC and blades upgraded, and the latest update ISO ran on the m610s)
We originally had a pair of 8024-k's in there but realized there was the compatibility mismatch so we swapped them out for the normal 8024 but the error persists. We have 4 blades doing this so I don't imagine it is just a bad mezz card or anything.
Any thoughts on what the issue could be?
Klug_fr
11 Posts
0
January 22nd, 2017 01:00
Hello.
Same issue here.
I have six M610.
I swapped two 10 Gbps cards (mezzanine C) because of strange errors (voltage) of one M610.
M8024 as switch in the M1000E.
Since the swap, I have the same "failed to program virtual MAC address" on the 10 Gbps card.
The card is seen from the M1000E but can't be seen in ESX 5.5U.
Last ISO firmware upgrade was tried (witch january update) but it did not help.
Next (last) try will be to reseat the M610.
Did you manage to solve your issue?
Klug_fr
11 Posts
0
January 22nd, 2017 05:00
I fix part of my issue: FlexAddress seems to have enabled itself while I swapped the NIC.
So I stopped the blade, disable FlexAddress and booted it.
Voilà, no more "FlexAddress" nor "Failed to program virtual MAC address" error.
However the NIC still can not be seen from ESX.
The BIOS update (M610 january bundle from "Dell Repository Manager") seems to have bricked them.
The firmware update in this bundle is 35RF5 that is supposed to upgrade to 7.12.19.
The update doesn't see the NIC as BCM57711 (10 Gbps) but as BCM5709.
It flashed them with the wrong firmware and the card seems bricked.
It seems to be the same issue here: en.community.dell.com/.../19985968