topic Re: Difference between SERVER_ALREADY_MONITORED and SERVER_ALREADY_ADDED in HPE OneView

Difference between SERVER_ALREADY_MONITORED and SERVER_ALREADY_ADDED

danielzting — Thu, 28 Aug 2025 05:51:26 GMT

When using the POST/rest/server-hardware API to add a server for monitoring with "configurationState": "Monitored", I get back an ID that I can query for the status of the task. Sometimes, the task fails with a "taskErrors" with "errorCode": "SERVER_ALREADY_ADDED" and other times it fails with "SERVER_ALREADY_MONITORED". Wondering what is the difference between these two?

Re: Difference between SERVER_ALREADY_MONITORED and SERVER_ALREADY_ADDED

Harshitha_K — Thu, 28 Aug 2025 04:58:45 GMT

HI @danielzting ,

The error code SERVER_ALREADY_ADDED and SERVER_ALREADY_MONITORED indicate slightly different conditions when using the POST /rest/server-hardware API to add a server for monitoring. Here's the difference between the two:

SERVER_ALREADY_ADDED
- This error occurs when the server hardware being added is already present in the system, but it may not necessarily be in the "Monitored" state. For example, the server could already exist as "Managed" or might have been added previously but is in a different configuration state.
- Essentially, the server is already recognized by the system, and attempting to add it again creates a conflict.
SERVER_ALREADY_MONITORED
- This error occurs when the server hardware being added is already present in the system and is specifically in the "Monitored" state.
- Since the server is already being monitored, there is no need to add it again with the same configurationState set to "Monitored."

Note:

Make sure you are not unintentionally attempting to add the same server hardware more than once.
Before attempting to add a server, you can query the existing server hardware list (GET /rest/server-hardware) to verify whether the server is already present in the system and its current configuration state.
If the server is already added but not in the "Monitored" state, you may need to update its configuration rather than re-adding it.

Please find the below link that might help you: link1 and link2.

Thank you!

Hope this information has helped you, Please click on the "Thumbs Up/Kudo" icon as a token of appreciation. Also, if this post has helped to solve your issue, consider marking this as an "Accepted Solution".

Re: Difference between SERVER_ALREADY_MONITORED and SERVER_ALREADY_ADDED

danielzting — Fri, 29 Aug 2025 04:08:31 GMT

@Harshitha_K

Thanks for the clarification! So SERVER_ALREADY_ADDED can occur if the server is in the Managed state. My understanding that Managed is a superset of Monitored. For my purposes we only need Monitored, so am I correct to treat a server that's already in Managed state as successful?

But you also say that SERVER_ALREADY_ADDED can indicate it "might have been added previously but is in a different configuration state"—does this mean the server is neither Managed or Monitored? My question now: are there any states where I would need to remove and re-add or change the configuration of the server rather than skip?

BTW, link 1 gives me Document not available