NC360M Shown as Not Mapped within vConnect Manager

[DavidJackson]

I have a c3000 chassis with 4 1-10GB-F vConnect modules installed in all four bays.  I have tried installing the NC360M in both Mezz slot 1 and Mezz slot 2 on a BL460c g6 blade.  I have assigned the two onboard nics to a network, but whenever I try to assign ports 3 and 4 to a network it always shows up as "not mapped". 

I had an extra NC382m laying around and when I installed that nic it was successfully mapped to the correct slot on both Mezz slot 1 and Mezz slot 2.  So the Mezz slots work as they should.  Is there anyway to check the currently installed firmware on the NC360m? 

I booted the blade from the HP SPP iso and it did not give me an option to upgrade the firmware.  The c3000 onboard administrator detects that the nic is installed in the blade.  When I boot from a linux live CD I am able to see that 4 nics are detected.