Reassign the server profile to a server blade previously removed from an enclosure

When you reinsert a server blade into the same bay, the server profile is reassociated with it and a task notification is created. But, if you reinsert a server blade into a different bay, the server profile associated with that server blade has a task error message stating that the server blade has been moved to a new location. To resolve this issue, either reassign the server profile to the server blade in the new location, or move the server blade to the original bay.

Prerequisites

Minimum required session ID privileges: Server administrator

Reassigning the server profile to a server blade previously removed from an enclosure using REST APIs

Reassigning the server profile to a server blade previously removed from an enclosure using REST APIs
Get the server blade that was reinserted into a different bay. `GET /rest/server-hardware?filter="state='AddedWithErrors'"` Get the server profile URI that was associated with the server blade. `GET /rest/tasks?filter="associatedResourceUri='{server blade URI}'"` Get the server profile associated with the server blade. `GET /rest/server-profiles/{id}` Add the correct server hardware URI to the server profile. Update the server profile. `POST /rest/server-profiles`

Get the server blade that was reinserted into a different bay.

GET /rest/server-hardware?filter="state='AddedWithErrors'"
Get the server profile URI that was associated with the server blade.

GET /rest/tasks?filter="associatedResourceUri='{server blade URI}'"
Get the server profile associated with the server blade.

GET /rest/server-profiles/{id}
Add the correct server hardware URI to the server profile.
Update the server profile.

POST /rest/server-profiles

prev	up	next
Power on or power off server hardware	home	Read a rack server