- Community Home
- >
- Software
- >
- HPE OneView
- >
- Difference between SERVER_ALREADY_MONITORED and SE...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
15 hours ago
15 hours ago
Difference between SERVER_ALREADY_MONITORED and SERVER_ALREADY_ADDED
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?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
a minute ago
a minute ago
Re: Difference between SERVER_ALREADY_MONITORED and SERVER_ALREADY_ADDED
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".
I work at HPE
HPE Support Center offers support for your HPE services and products when and how you need it. Get started with HPE Support Center today.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]
