cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1068
Views
0
Helpful
7
Replies

Adapter 1 in server 1/1 has unidentified FRU

technicalBRO
Level 1
Level 1

Hello.

Updated UCS 5108 from version 2.2 to 3.2. Why hasn't it been updated, let's skip this question.
The update process was successful, but an error appeared in the UI - "Adapter 1 in server 1/1 has unidentified FRU".
Found this article - https://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/ts/faults/reference/ErrMess/UCS_SEMs.html.
Can anyone advise on how to fix it?
Thank you.

1 Accepted Solution

Accepted Solutions

Since only one server is impacted this seems more like something not in sync with that one server, and not an overall hardware/firmware compatibility issue.

In attempt to get Server 1/1 fully in sync with UCSM, I would try (hidden) `reset slot` command as detailed in this doc:

+ https://www.cisco.com/c/en/us/support/docs/servers-unified-computing/unified-computing-system/214047-troubleshooting-ucs-blade-discovery-issu.html

View solution in original post

7 Replies 7

marce1000
VIP
VIP

 

 - FYI : https://www.kozeniauskas.com/itblog/2012/11/12/ucs-blade-is-stuck-on-discovery-after-ucs-firmware-upgrade-unidentified-fru/

 M.



-- Each morning when I wake up and look into the mirror I always say ' Why am I so brilliant ? '
    When the mirror will then always repond to me with ' The only thing that exceeds your brilliance is your beauty! '

Steven Tardy
Cisco Employee
Cisco Employee

I totally forgot about adapters when answering your other question(s).

Any chance the Cisco VIC adapters are M81KR's (or some other PID on this list)?

If they are M81KR VICs, then you will have to roll back to UCSM 2.2(8x) and stay there.

Hi.

Help me look at this correctly?

Cisco UCS VIC 1240
PID:UCSB-MLOM-40G-01
VID:V01
SKU:UCSB-MLOM-40G-01
Vendor ID:4407
Sub Vendor ID:4407

The VIC 1240 is still supported in UCSM 3.1 (as "UCSB-MLOM-40G-01" is listed on the release note page I linked previously) and even up to UCSM 4.1(3) by checking the UCS HCL[1].

Also on the release notes page the minimum version is listed, 2.2(1b), so seems like if the server/VIC was on 2.2(3x) that the VIC should still work with that updated UCSM and down version VIC (if that is the current scenario).

Is this happening on all servers/blades? Or just some/one of the servers/blades?

Does the adapter show under: UCSM / Equipment / Server 1/1 / [Installed Firmware] (click the "+" on the top left to expand all.)

If the VIC/adapter shows there, then maybe you can right-click and [Update Firmware]. Wait a few minutes and then [Active Firmware], then reboot the server.
If the VIC/adapter does NOT show there, then I would probably try a decommission/recommission of that server in attempt to fully populate the inventory of that server.

[1] https://ucshcltool.cloudapps.cisco.com/public/

Hi.


Is this happening on all servers/blades? Or just some/one of the servers/blades?

this is only on one blade #1


Does the adapter show under: UCSM / Equipment / Server 1/1 / [Installed Firmware] (click the "+" on the top left to expand all.)

technicalBRO_0-1697972191987.png

The screen applies to all 8 blades

Since only one server is impacted this seems more like something not in sync with that one server, and not an overall hardware/firmware compatibility issue.

In attempt to get Server 1/1 fully in sync with UCSM, I would try (hidden) `reset slot` command as detailed in this doc:

+ https://www.cisco.com/c/en/us/support/docs/servers-unified-computing/unified-computing-system/214047-troubleshooting-ucs-blade-discovery-issu.html

Gracias.
It worked.

Thank you!

Review Cisco Networking for a $25 gift card

Review Cisco Networking for a $25 gift card