10-24-2024 01:53 PM
Howdy folks (by the way, there is no good 'label' for this question),
I've got a Python script going out to many sites around the world to query both 'ComputeRackUnit' and 'ComputeBlade' class IDs. This is across everything from M2s (almost gone!) through to M6s.
Part of the data I get returned is the 'oper_state'.
I'm having trouble getting the definitions for the states that are returned, especially servers that are not powered on.
Below are the states that I am trying to get definitions for (I know some seem obvious, but I wouldn't want to assume). Bonus points for a link to the documentation.
Thanks!
Solved! Go to Solution.
10-30-2024 01:17 PM - edited 10-30-2024 01:23 PM
Just to close the loop on this, I logged into the FIs and reviewed the servers with each of the statuses and combined that with the little documentation I found to put together status definitions that work for my organization.
Here they are in case they help anyone else:
**'seen on' is an incomplete list, it only represents instances of the status seen in our environment**
State | Seen on |
Slot Status |
Admin State |
Availability | Discovery State |
Association State |
Typical Cause |
COMPUTE-FAILED | M5 | Equipped | In Service | Unavailable | Failed | Unassociated | Setup of Vmedia failed |
DEGRADED | M2, M4, M5 | Equipped | In Service | Unavailable | Complete | Associated | System Board failures (DIMM/CPU/power/etc) |
DISCOVERY | M4, M5 | Equipped | In Service | Unavailable | Retry | Unassociated | System Board failures (DIMM/CPU/power/etc) that prevent discovery after start/restart |
DISCOVERY-FAILED | M5 | Equipped | In Service | Unavailable | Failed | Unassociated | System Board failures (DIMM/CPU/power/etc) that prevent discovery after start/restart |
INACCESSIBLE | M2, M3, M4 | Equipped | In Service | Unavailable | Complete | Associated | After the server has been successfully shut down, but still "In Service" & "Equipped" |
INOPERABLE | M4, M5 | Equipped | In Service | Unavailable | Retry | Unassociated | System Board failures (DIMM/CPU/power/etc) |
POWER-OFF | M2, M4, M5 | Equipped | In Service | Unavailable | Complete | Associated | After the server has been successfully shut down, but still "In Service" & "Equipped" |
REMOVED | M5 | Missing | n/a | Unavailable | n/a | n/a | The server has been physically removed but has not been decommissioned in UCSM |
UNASSOCIATED | M4, M5 | Equipped | In Service | Available | Complete | Unassociated | The server is physically installed, but not associated with a profile and therefore not in use. |
10-30-2024 01:17 PM - edited 10-30-2024 01:23 PM
Just to close the loop on this, I logged into the FIs and reviewed the servers with each of the statuses and combined that with the little documentation I found to put together status definitions that work for my organization.
Here they are in case they help anyone else:
**'seen on' is an incomplete list, it only represents instances of the status seen in our environment**
State | Seen on |
Slot Status |
Admin State |
Availability | Discovery State |
Association State |
Typical Cause |
COMPUTE-FAILED | M5 | Equipped | In Service | Unavailable | Failed | Unassociated | Setup of Vmedia failed |
DEGRADED | M2, M4, M5 | Equipped | In Service | Unavailable | Complete | Associated | System Board failures (DIMM/CPU/power/etc) |
DISCOVERY | M4, M5 | Equipped | In Service | Unavailable | Retry | Unassociated | System Board failures (DIMM/CPU/power/etc) that prevent discovery after start/restart |
DISCOVERY-FAILED | M5 | Equipped | In Service | Unavailable | Failed | Unassociated | System Board failures (DIMM/CPU/power/etc) that prevent discovery after start/restart |
INACCESSIBLE | M2, M3, M4 | Equipped | In Service | Unavailable | Complete | Associated | After the server has been successfully shut down, but still "In Service" & "Equipped" |
INOPERABLE | M4, M5 | Equipped | In Service | Unavailable | Retry | Unassociated | System Board failures (DIMM/CPU/power/etc) |
POWER-OFF | M2, M4, M5 | Equipped | In Service | Unavailable | Complete | Associated | After the server has been successfully shut down, but still "In Service" & "Equipped" |
REMOVED | M5 | Missing | n/a | Unavailable | n/a | n/a | The server has been physically removed but has not been decommissioned in UCSM |
UNASSOCIATED | M4, M5 | Equipped | In Service | Available | Complete | Unassociated | The server is physically installed, but not associated with a profile and therefore not in use. |
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