09-26-2022 11:16 AM
The server went down while being in use and upon attempting to bring the server up, it will not discover. Any ideas or help?
Blade will not discover, we have attempted a virtual reset through ssh and have also manually reseated the blade to attempt to get it to discover.
The have been no changes to the system prior to this event.
Here are the FSM logs from CLI:
P-RICH-UCSM-VB04-B# scope server 4/3
P-RICH-UCSM-VB04-B /chassis/server # show fsm status
Slot: 3
Server: sys/chassis-4/blade-3
FSM 1:
Remote Result: End Point Unavailable,End Point Protocol Error
Remote Error Code: 1002
Remote Error Description: CimcVMedia Error: Error retrieving vmedia attributes list-MC Error(-6): Connection is closing
Status: Discover Fail
Previous Status: Discover Fail
Timestamp: 2022-09-18T15:00:16.312
Try: 20
Flags: 0
Progress (%): 4
Current Task: getting inventory of server 4/3 via CIMC(FSM-STAGE:sam:dme:ComputeBladeDiscover:BmcInventory)
FSM 2:
Status: Nop
Previous Status: Identify Success
Timestamp: 2022-09-11T19:18:20.513
Try: 0
Progress (%): 100
Current Task:
FSM 3:
Status:
Previous Status:
Timestamp:
Try:
Flags:
Progress (%):
Current Task:
We tried replacing the Blade with a new one but still not discovering.
Getting following message.
Unable to change server power state-MC Error(-20): Management controller cannot or failed in processing request”.
Any ideas what should I do next? Thanks.
09-26-2022 11:30 AM
09-26-2022 11:52 AM
We've reseated slot 4/3 still the same.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide