11-21-2013 12:09 PM - edited 03-01-2019 11:22 AM
48 C220-M3 managed through UCSM 2.1.3a
3 servers with discovery failed; ack,.... doesn't solve the issue
Decommission, Recommission; I get the confirmation that recommission is started, but nothing happens ?
any advice ?
11-21-2013 01:47 PM
Typically when discovery fails to start without a specific error it has something to do with the Management connection. First thing to look at is the Management Connection Policy in the Policies Tab under equipment.
If it is not set to Auto Acknowledge then you will need to go to the server (assuming it shows up in the equipment tree) and Select Inventory->CIMC->then select management connection (note it will be grayed out unless the policy is set to user acknowledge).
Then Select Sidband for Single Wire Managment (Single Connect) or Shared LOM for Dual Wire.
If that is not the case then verify that the cables are actually connected to the 2232. You could try differnt ports, but if you do make sure you decom/recom to clear the DME entries in UCSM.
If the server is not even showing up in the equipment tree you should decom, connect a crash cart to the server (keybord and monitor) F8 into CIMC and restore factory defaults. Once the CIMC reboots and you see a link light on the VIC you can then recom the server.
Steve McQuerry
UCS - Technical Marketing
11-21-2013 02:58 PM
Hi Wdey,
Can you provide a screenshot of where the FSM is failing during the discovery process?
Have these servers worked before?
What kind of adapter are you using(VIC1225 or P81E)?
Is this single-wire or dual-wire?
The most important question, did you set the cimc default settings?
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