PowerEdge Servers Error and Event Messages Reference Guide
NVRE—REST Event Messages
NVRE0001
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to process the request because the Base Authentication Token is not present in the request.
- Detailed Description
- The request failed because the Base Authentication token is not present in the request header.
- Recommended Response Action
- Enter a Base Authentication Token in the request header and retry the operation.
- Category
- Configuration (NVRE = REST)
- Severity
- Critical
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
NVRE0002
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to process the request because the Authorization Token is not of Basic type.
- Detailed Description
- The request can not be processed because the Authorization Token entered is not of Basic type.
- Recommended Response Action
- Change the Authorization token type to Basic Authentication and retry the operation.
- Category
- Configuration (NVRE = REST)
- Severity
- Critical
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
NVRE0003
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to process the request because the authorization failed.
- Detailed Description
- The request can not be processed because the username and password provided in the authorization token is not valid.
- Recommended Response Action
- Provide a valid user name and password and retry the operation again.
- Category
- Configuration (NVRE = REST)
- Severity
- Critical
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
NVRE0004
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to process the request because the provided URL is not valid.
- Detailed Description
- The request can not be processed because the given URL is not valid.
- Recommended Response Action
- Enter a valid URL and retry the operation again.
- Category
- Configuration (NVRE = REST)
- Severity
- Critical
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
NVRE0005
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to process the request because the provided image stream is not valid.
- Detailed Description
- The request can not be processed because the given image stream is not a valid firmware image.
- Recommended Response Action
- Provide a valid image stream and retry the operation.
- Category
- Configuration (NVRE = REST)
- Severity
- Critical
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
NVRE0006
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to process the request because the input JSON payload is invalid. Error information: arg1.
- Arguments
- arg1 = details
- Detailed Description
- The request failed because the payload provided is not of valid JSON format.
- Recommended Response Action
- Enter a valid JSON payload and retry the operation again.
- Category
- Configuration (NVRE = REST)
- Severity
- Critical
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
NVRE0007
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to process the request because the VLAN ID entered is not an integer.
- Detailed Description
- The request can not be processed because the entered VLAN ID is not an integer.
- Recommended Response Action
- Enter a valid integer for VLAN ID in the payload and retry the operation again.
- Category
- Configuration (NVRE = REST)
- Severity
- Critical
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
NVRE0008
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to process the request because the URL is not valid.
- Detailed Description
- The request can not be processed because the entered odata URL does not have correct parenthesis.
- Recommended Response Action
- Enter a valid odata URL, check the correctness of parenthesis and retry the operation again.
- Category
- Configuration (NVRE = REST)
- Severity
- Critical
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
NVRE0009
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to process the request because the URL is not valid.
- Detailed Description
- The request can not be processed because the URL is not valid and the ID provided in the URL is not correct.
- Recommended Response Action
- Enter a valid URL, check for correctness of odata ID and retry the operation.
- Category
- Configuration (NVRE = REST)
- Severity
- Critical
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
NVRE0010
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to process the request because the integer value in the request URL for the key arg1 is invalid.
- Arguments
- arg1 = parameter key
- Detailed Description
- The request can not be processed because the value provided for the key is not an integer.
- Recommended Response Action
- Enter a valid integer value for the key and retry the operation.
- Category
- Configuration (NVRE = REST)
- Severity
- Critical
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
NVRE0011
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to process the request because the validation error does not exist.
- Detailed Description
- The request can not be processed because the given validation error ID is not present.
- Recommended Response Action
- Enter a valid validation error ID and retry the operation.
- Category
- Configuration (NVRE = REST)
- Severity
- Critical
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
NVRE0012
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to process the request because the fabric validation error does not exist.
- Detailed Description
- The request can not be processed because the given fabric validation error id is not present.
- Recommended Response Action
- Enter a valid fabric validation error id and retry the operation.
- Category
- Configuration (NVRE = REST)
- Severity
- Critical
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
NVRE0013
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to process the request because the link does not exist.
- Detailed Description
- The request can not be processed because the given link ID is not present.
- Recommended Response Action
- Enter a valid link ID and retry the operation.
- Category
- Configuration (NVRE = REST)
- Severity
- Critical
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
NVRE0014
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to process the request because the given HTTP method arg1 is not allowed for the given URL.
- Arguments
- arg1 = method name
- Detailed Description
- The request can not be processed because the given HTTP method is not allowed for the given URL.
- Recommended Response Action
- Provide a valid HTTP method and retry the operation.
- Category
- Configuration (NVRE = REST)
- Severity
- Critical
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
NVRE0015
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to process the request because the fabric design does not exist.
- Detailed Description
- The request can not be processed because the given fabric design ID is not present.
- Recommended Response Action
- Enter a valid fabric design ID and retry the operation.
- Category
- Configuration (NVRE = REST)
- Severity
- Critical
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
NVRE0016
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to process the request because the discovered server does not exist.
- Detailed Description
- The request can not be processed because the given discovered server ID is not present.
- Recommended Response Action
- Enter a valid discovered server ID and retry the operation.
- Category
- Configuration (NVRE = REST)
- Severity
- Critical
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
NVRE0017
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to process the request because the discovered server interface does not exist.
- Detailed Description
- The request can not be processed because the given discovered server interface ID is not present.
- Recommended Response Action
- Enter a valid discovered server interface ID and retry the operation.
- Category
- Configuration (NVRE = REST)
- Severity
- Critical
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
NVRE0018
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to process the request because the server interface bond does not exist.
- Detailed Description
- The request can not be processed because the given server interface bond id is not present.
- Recommended Response Action
- Enter a valid server interface bond id and retry the operation.
- Category
- Configuration (NVRE = REST)
- Severity
- Critical
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
NVRE0019
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to process the request because the VLAN does not exist.
- Detailed Description
- The request can not be processed because the given VLAN ID is not present.
- Recommended Response Action
- Enter a valid VLAN ID and retry the operation.
- Category
- Configuration (NVRE = REST)
- Severity
- Critical
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
NVRE0020
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to save the image file because necessary disk space is unavailable.
- Detailed Description
- The image file cannot be processed because necessary disk space is unavailable.
- Recommended Response Action
- Delete the current image file from /var/os10-image location and retry the operation.
- Category
- Configuration (NVRE = REST)
- Severity
- Critical
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
NVRE0021
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to process the request because the user arg1 does not have the privilege to change the password.
- Arguments
- arg1 = user name
- Detailed Description
- The password cannot be changed because the user identified in the message does not have the privilege to change the password.
- Recommended Response Action
- Enter a valid REST user name which has the privilege to change the password and retry the operation.
- Category
- Configuration (NVRE = REST)
- Severity
- Critical
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
NVRE0022
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to process the request because the service is not ready yet.
- Detailed Description
- The request can not be processed because the module to handle the request is not ready yet.
- Recommended Response Action
- Retry the operation after some time. If the issue persists, contact the administrator.
- Category
- Configuration (NVRE = REST)
- Severity
- Critical
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
NVRE0023
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to start the lifecycle operation on the I/O Module because the I/O Module arg1 is offline.
- Arguments
- arg1 = node Id
- Detailed Description
- The lifecycle operation on the I/O Module cannot be started because the I/O Module identified in the message is offline.
- Recommended Response Action
- Wait for the I/O Module to be available online and retry the operation.
- Category
- Configuration (NVRE = REST)
- Severity
- Critical
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
NVRE0024
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to create or update the fabric because the I/O Module arg1 is offline.
- Arguments
- arg1 = node Id
- Detailed Description
- The fabric cannot be created or updated because the I/O Module identified in the message is offline.
- Recommended Response Action
- Wait for the I/O Module to be available online and retry the operation.
- Category
- Configuration (NVRE = REST)
- Severity
- Critical
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
NVRE0025
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to create or update the fabric because the REST operation is not supported for L3 fabric personality.
- Detailed Description
- The fabric cannot be created or updated because the REST operation is not supported for L3 fabric personality.
- Recommended Response Action
- Do not use REST API to create or update the L3 fabric because L3 fabrics are automatically created when the L3 SmartFabric mode is enabled by using Command Line Interface (CLI).
- Category
- Configuration (NVRE = REST)
- Severity
- Critical
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
NVRE0026
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to perform REST create, update or delete operation because the REST configuration is locked.
- Detailed Description
- The request cannot be serviced now, because the configuration database is locked.
- Recommended Response Action
- Retry the operation after some time. If the issue persist, contact your OpenManage Enterprise-Modular administrator.
- Category
- Configuration (NVRE = REST)
- Severity
- Critical
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
NVRE0100
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to service the request because of internal server error.
- Detailed Description
- The request could not be serviced due to internal server error.
- Recommended Response Action
- Retry the operation after some time. If the issue persists, contact the administrator.
- Category
- Configuration (NVRE = REST)
- Severity
- Critical
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
NVRE0101
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to process the request because Authorization header is not present in the request.
- Detailed Description
- The request failed because there was no Authorization header in the request.
- Recommended Response Action
- Provide the authentication details in the Authorization header.
- Category
- Configuration (NVRE = REST)
- Severity
- Critical
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
NVRE0102
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to process the request because authentication type mentioned in Authorization header is not valid.
- Detailed Description
- The request cannot be processed because of invalid authentication type in Authorization header.
- Recommended Response Action
- Provide a valid authentication type in the Authorization header. (Ex : Basic).
- Category
- Configuration (NVRE = REST)
- Severity
- Critical
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
NVRE0103
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to process the request because token authentication failed.
- Detailed Description
- The request can not be processed because the Bearer token provided in the Authorization header is not valid.
- Recommended Response Action
- Provide a valid Bearer token and retry the operation again.
- Category
- Configuration (NVRE = REST)
- Severity
- Critical
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
NVRE0104
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to process the request because token authentication is disabled.
- Detailed Description
- The request can not be processed because the Bearer token authentication has been disabled.
- Recommended Response Action
- Retry with Basic authentication type in the Authorization header.
- Category
- Configuration (NVRE = REST)
- Severity
- Critical
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
NVRE0106
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- The current operation is completed. Enter the RSA passcode to successfully log in.
- Detailed Description
- Authentication requires second factor (RSA passcode) for completion.
- Recommended Response Action
- No response action is required.
- Category
- Configuration (NVRE = REST)
- Severity
- Informational
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
NVRE1001
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to retrieve the route policy data because the route policy does not exist.
- Detailed Description
- The route policy data cannot be retrieved because the route policy does not exist.
- Recommended Response Action
- Enter a valid route policy id and retry the operation.
- Category
- Configuration (NVRE = REST)
- Severity
- Warning
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
NVRE1002
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to retrieve the node policy mapping data because the node policy mapping does not exist.
- Detailed Description
- The node policy mapping data cannot be retrieved because the node policy mapping does not exist.
- Recommended Response Action
- Enter a valid node id and retry the operation.
- Category
- Configuration (NVRE = REST)
- Severity
- Warning
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
NVRE1003
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to create a route policy data because a route policy with similar name already exists.
- Detailed Description
- The route policy cannot be created because a route policy with a similar name already exists.
- Recommended Response Action
- Create a new route policy data with a unique policy ID, and then retry the operation.
- Category
- Configuration (NVRE = REST)
- Severity
- Warning
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
NVRE1004
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to create a node policy because a node policy with similar name already exists.
- Detailed Description
- A node policy cannot be created because a policy with a similar name already exists.
- Recommended Response Action
- Delete the node policy mapping that has the Service tag of the node as the key, and then re-create a new policy by using a new set of policy IDs.
- Category
- Configuration (NVRE = REST)
- Severity
- Warning
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
NVRE1005
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to create the route policy because an invalid policy data is entered.
- Detailed Description
- The route policy cannot be created because an invalid policy data is entered.
- Recommended Response Action
- Create a new route policy by entering valid policy data, and then create the route policy.
- Category
- Configuration (NVRE = REST)
- Severity
- Warning
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
NVRE1006
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to delete the route policy because the route policy is already mapped and the nodes are currently using the policies.
- Detailed Description
- The route policy cannot be deleted because it is already mapped and the nodes are currently using the policies.
- Recommended Response Action
- Delete the node policy mapping for the nodes and then delete the route policy.
- Category
- Configuration (NVRE = REST)
- Severity
- Critical
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
NVRE1010
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to update the route policy data because editing the Policy ID is not permitted.
- Detailed Description
- Theroute policy property cannot be updated because editing the Policy ID is notpermitted.
- Recommended Response Action
- Delete the current policy and create a new policy by usingthe necessary Policy ID.
- Category
- Configuration (NVRE = REST)
- Severity
- Warning
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
NVRE1012
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to update the password because it does not meet the required security criteria.
- Detailed Description
- The password does not meet the security requirements, including length, uppercase letters, lowercase letters, numeric characters and special characters.
- Recommended Response Action
- Ensure that the password has at least nine characters, at least one upper case letter (A-Z), at least one upper case letter (a-z), at least one numeric character (0-9) and at least one special character (!,@, #, $, %, ^, &, or *), and then retry the operation.
- Category
- Configuration (NVRE = REST)
- Severity
- Warning
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
NVRE1101
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to retrieve workflow data because the specified workflow ID does not exist.
- Detailed Description
- The workflow data cannot be retrieved because the workflow does not exist.
- Recommended Response Action
- Enter a valid workflow ID and retry the operation.
- Category
- Configuration (NVRE = REST)
- Severity
- Critical
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
NVRE1102
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to process the request because the workflow sub-component(s) specified in the payload does not exist. Error information: %1.
- Detailed Description
- The request could not be processed because the workflow sub-component(s) specified in the payload does not exist.
- Recommended Response Action
- Enter the appropriate workflow components and retry the operation again.
- Category
- Configuration (NVRE = REST)
- Severity
- Critical
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
NVRE1103
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to update the details of workflow components because the specified Workflow ID does not exist.
- Detailed Description
- The Workflow components cannot be updated because the Workflow ID does not exist.
- Recommended Response Action
- Enter a valid workflow ID and retry the operation again.
- Category
- Configuration (NVRE = REST)
- Severity
- Critical
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
NVRE1104
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to delete the workflow because the specified workflow ID does not exist.
- Detailed Description
- The Workflow cannot be deleted because the Workflow ID does not exist.
- Recommended Response Action
- Provide a valid workflow ID and attempt the delete operation again.
- Category
- Configuration (NVRE = REST)
- Severity
- Critical
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
NVRE1105
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to delete the specified workflow component(s) as it does not exist.
- Detailed Description
- The workflow component(s) cannot be deleted because it does not exist.
- Recommended Response Action
- No action required.
- Category
- Configuration (NVRE = REST)
- Severity
- Informational
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
NVRE1106
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to create or update the Server Interface Profile because the length of StaticOnboardInterface is more than 128 characters.
- Detailed Description
- TheServer Interface Profile cannot be created or updated because the length ofStaticOnboardInterface is invalid.
- Recommended Response Action
- EnterStaticOnboardInterface whose length does not exceed 128 characters and retrythe operation.
- Category
- Configuration (NVRE = REST)
- Severity
- Critical
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
NVRE2001
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to retrieve the IP Access Control List (ACL) rule data because the IP ACL rule with ACL name and sequence number does not exist.
- Detailed Description
- The IP Access Control List (ACL) rule data cannot be retrieved because the IP ACL rule data does not exist.
- Recommended Response Action
- Enter a valid IP Access Control List (ACL) rule with ACL name and sequence number and retry the operation.
- Category
- Configuration (NVRE = REST)
- Severity
- Warning
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
NVRE2002
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to retrieve the IP Access Control List (ACL) data because the IP ACL name does not exist.
- Detailed Description
- The IP ACL data cannot be retrieved because the IP ACL name does not exist.
- Recommended Response Action
- Enter a valid IP Access Control List (ACL) rule with ACL name, and then retry the operation.
- Category
- Configuration (NVRE = REST)
- Severity
- Critical
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
NVRE2003
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to create the IP Access Control List (ACL) rule data because there is already an IP ACL rule and sequence number with the same name.
- Detailed Description
- The IP Access Control List (ACL) rule cannot be created because there is already an IP ACL rule and sequence number with the same name.
- Recommended Response Action
- Enter a new IP Access Control List (ACL) rule with a unique ACL number and sequence number, and then retry the operation.
- Category
- Configuration (NVRE = REST)
- Severity
- Critical
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
NVRE2004
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to create the IP Access Control List (ACL) rule data because there is already an IP ACL rule an with the same name.
- Detailed Description
- The IP Access Control List (ACL) rule cannot be created because there is already an IP ACL rule with the same name.
- Recommended Response Action
- Enter a new IP Access Control List (ACL) rule with a unique ACL number, and then retry the operation.
- Category
- Configuration (NVRE = REST)
- Severity
- Warning
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
NVRE2500
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to upgrade since the protocol field is not provided.
- Detailed Description
- The upgrade cannot be completed because the protocol field is not provided.
- Recommended Response Action
- Provide a valid protocol and then retry the operation.
- Category
- Configuration (NVRE = REST)
- Severity
- Critical
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
NVRE2501
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to upgrade since the image URL is not provided.
- Detailed Description
- The image URL is empty unable to upgrade.
- Recommended Response Action
- Provide a valid image URL and then retry the operation.
- Category
- Configuration (NVRE = REST)
- Severity
- Critical
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
NVRE2502
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to upgrade since the image name is not provided.
- Detailed Description
- The image name is empty unable to upgrade.
- Recommended Response Action
- Provide a valid image name and then retry the operation.
- Category
- Configuration (NVRE = REST)
- Severity
- Critical
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
NVRE2503
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to upgrade since the image upgrade is progress.
- Detailed Description
- The image update is in progress.
- Recommended Response Action
- Wait for current update to complete and then retry the operation.
- Category
- Configuration (NVRE = REST)
- Severity
- Critical
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
NVRE2504
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- One or more node offline or cannot be communicated with.
- Detailed Description
- One or more node is offline or cannot be communicated with.
- Recommended Response Action
- Wait for the node be online then retry the operation.
- Category
- Configuration (NVRE = REST)
- Severity
- Critical
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
NVRE2505
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- The support to Enhanced Upgrade feature is changed to Enabled.
- Detailed Description
- Feature capability ofSmartFabric Manager has changed.
- Recommended Response Action
- No response action is required.
- Category
- Audit (NVRE = REST)
- Severity
- Informational
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
NVRE2506
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- The support to Enhanced Upgrade feature is changed to Disabled.
- Detailed Description
- Feature capability ofSmartFabric Manager has changed.
- Recommended Response Action
- No response action is required.
- Category
- Audit (NVRE = REST)
- Severity
- Informational
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
NVRE2600
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to collect Support bundle because the host path is not entered.
- Detailed Description
- The Support bundle cannot be collected because the host path is not entered.
- Recommended Response Action
- Enter a host path and retry the operation.
- Category
- Configuration (NVRE = REST)
- Severity
- Critical
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
NVRE2601
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to collect Support bundle because the host user name is not entered.
- Detailed Description
- The Support bundle cannot be collected because the host user name is not entered.
- Recommended Response Action
- Enter a host user name and retry the operation.
- Category
- Configuration (NVRE = REST)
- Severity
- Critical
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
NVRE2602
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to collect Support bundle because the host user password is not entered.
- Detailed Description
- The Support bundle cannot be collected because the host user password is not entered.
- Recommended Response Action
- Enter a host user password and retry the operation.
- Category
- Configuration (NVRE = REST)
- Severity
- Critical
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
NVRE2603
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to collect Support bundle because the host ip address is not entered.
- Detailed Description
- The Support bundle cannot be collected because the host ip address is not entered.
- Recommended Response Action
- Enter a host ip address and retry the operation.
- Category
- Configuration (NVRE = REST)
- Severity
- Critical
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
NVRE2604
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to collect Support bundle because the host ip address family is not entered.
- Detailed Description
- The support bundle cannot be collected because the host ip address family is not entered.
- Recommended Response Action
- Enter a host ip address family and retry the operation.
- Category
- Configuration (NVRE = REST)
- Severity
- Critical
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
NVRE2605
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to collect Support bundle because the host transfer protocol is not entered.
- Detailed Description
- The Support bundle cannot be collected because the host transfer protocol is not entered.
- Recommended Response Action
- Enter a host transfer protocol and retry the operation.
- Category
- Configuration (NVRE = REST)
- Severity
- Critical
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
NVRE2606
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to collect Support since the support bundle collection is progress.
- Detailed Description
- The Support bundle collection is in progress.
- Recommended Response Action
- Wait for current operation to complete and then retry the operation.
- Category
- Configuration (NVRE = REST)
- Severity
- Critical
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
NVRE3001
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to retrieve the IP prefix-list rule data because the IP prefix-list name and sequence number does not exist.
- Detailed Description
- The prefix-list rule data because the IP prefix-list name and sequence number does not exist.
- Recommended Response Action
- Enter a valid IP Access Control List (ACL) prefix-list rule with name and sequence number, and then retry the operation.
- Category
- Configuration (NVRE = REST)
- Severity
- Critical
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
NVRE3002
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to retrieve the IP prefix-list data because the IP prefix-list name does not exist.
- Detailed Description
- The prefix-list rule data cannot be retrieved because the IP prefix-list name and sequence number does not exist.
- Recommended Response Action
- Enter a valid IP Access Control List (ACL) rule with ACL name and sequence number, and then retry the operation.
- Category
- Configuration (NVRE = REST)
- Severity
- Critical
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
NVRE3003
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to create the IP prefix-list rule because there is already an IP prefix-list rule and sequence number with the same name.
- Detailed Description
- The IP prefix-list rule cannot be created because there is already an IP prefix-list rule and sequence number with the same name.
- Recommended Response Action
- Create an IP prefix-list rule by using a unique prefix-list name and sequence number, and then retry the operation.
- Category
- Configuration (NVRE = REST)
- Severity
- Critical
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
NVRE3004
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to create the IP prefix-list because there is already an IP prefix-list with the same name.
- Detailed Description
- The IP prefix-list cannot be created because there is already an IP prefix-list with the same name.
- Recommended Response Action
- Create an IP prefix-list rule by using a unique prefix-list name, and then retry the operation.
- Category
- Configuration (NVRE = REST)
- Severity
- Critical
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
NVRE4001
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to retrieve or update the route-map because the route-map does not exist.
- Detailed Description
- The route-map information cannot be retrieved or updated because the route-map does not exist.
- Recommended Response Action
- Enter a valid route-map name and retry the operation.
- Category
- Configuration (NVRE = REST)
- Severity
- Critical
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
NVRE4002
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to retrieve or update the route-map rule because the route-map rule does not exist.
- Detailed Description
- The route-map rule ID information cannot be retrieved or updated because the route-map rule does not exist.
- Recommended Response Action
- Enter a valid route-map rule ID and retry the operation.
- Category
- Configuration (NVRE = REST)
- Severity
- Critical
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
NVRE4003
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to create a route-map by using the name entered because the route-map already exists.
- Detailed Description
- Unable to create a route-map by using the name entered because the route-map already exists.
- Recommended Response Action
- Enter a new route-map name and retry the operation.
- Category
- Configuration (NVRE = REST)
- Severity
- Critical
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
NVRE4004
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to create a route-map rule by using the ID entered because the route-map rule already exists.
- Detailed Description
- The route-map rule cannot be created because the route-map rule already exists.
- Recommended Response Action
- Enter a new route-map rule ID and retry the operation.
- Category
- Configuration (NVRE = REST)
- Severity
- Critical
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
NVRE5001
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to retrieve the SFS Global data because the SFS Global data does not exist.
- Detailed Description
- The SFS Global data cannot be retrieved because the SFS Global data does not exist.
- Recommended Response Action
- Enter a valid SFS Global data, and then retry the operation.
- Category
- Configuration (NVRE = REST)
- Severity
- Warning
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
NVRE5002
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to create or update the SFS Global data because the entered SFS Global data is invalid.
- Detailed Description
- The SFS Global data cannot be created because the entered SFS Global data is invalid.
- Recommended Response Action
- Enter a valid SFS Global data, and then retry the operation.
- Category
- Configuration (NVRE = REST)
- Severity
- Warning
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
NVRE5003
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to create or update the Layer 3 Fabric configuration because the length of prefix characters entered is invalid.
- Detailed Description
- The Layer 3 Fabric configuration cannot be created or updated because the length of prefix characters entered is invalid.
- Recommended Response Action
- Enter prefix whose length does not exceed 31characters, and retry the operation.
- Category
- Configuration (NVRE = REST)
- Severity
- Warning
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
NVRE5004
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to create or update the Layer 3 Fabric configuration because an invalid Autonomous System Number (ASN) value is entered.
- Detailed Description
- The Layer 3 Fabric configuration cannot be created or updated because an invalid Autonomous System Number (ASN) value is entered.
- Recommended Response Action
- Enter a valid ASN value from 64,512 to 65,535, and then retry operation.
- Category
- Configuration (NVRE = REST)
- Severity
- Warning
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
NVRE5005
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to create or update the Layer 3 Fabric personality configuration because the control or management VLAN value entered is invalid.
- Detailed Description
- The Layer 3 Fabric personality configuration cannot be created or updated because the control or management VLAN value entered is invalid.
- Recommended Response Action
- Enter a valid control or management VLAN value and retry the operation. Range between 4000 and 4094 are reserved except 4091 for control or management vlan.
- Category
- Configuration (NVRE = REST)
- Severity
- Warning
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
NVRE6001
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to retrieve the SNMP server host data because the SNMP server does not exist.
- Detailed Description
- The SNMP server host data cannot be retrieved because the SNMP server does not exist.
- Recommended Response Action
- Enter a valid SNMP server host data, and then retry the operation.
- Category
- Configuration (NVRE = REST)
- Severity
- Warning
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
NVRE6002
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to create or update the SNMP server host data because invalid SNMP server data is entered.
- Detailed Description
- The SNMP server host data cannot be created or updated retrieved because invalid SNMP server data is entered.
- Recommended Response Action
- Enter a valid SNMP server host data, and then retry the operation.
- Category
- Configuration (NVRE = REST)
- Severity
- Warning
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
NVRE6003
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to create the SNMP server host because an SNMP server host already exists with the similar IP address.
- Detailed Description
- The SNMP server host data cannot be created because an SNMP server host already exists with the similar IP address.
- Recommended Response Action
- Create a SNMP server host by using a unique host IP address, and then retry the operation.
- Category
- Configuration (NVRE = REST)
- Severity
- Critical
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
NVRE6004
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to create the SNMP server host because an SNMP server data does not exist.
- Detailed Description
- The SNMP server host data cannot be created because an SNMP server data does not exist.
- Recommended Response Action
- Enter a valid SNMP server data and retry the operation.
- Category
- Configuration (NVRE = REST)
- Severity
- Critical
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
NVRE6005
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to create or update the SNMP server data because invalid data is entered.
- Detailed Description
- The SNMP server data cannot be created or updated because invalid data is entered.
- Recommended Response Action
- Enter a valid SNMP server data and retry the operation.
- Category
- Configuration (NVRE = REST)
- Severity
- Critical
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
NVRE6006
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to create the SNMP server data because there is an SNMP server data already exists with the same host IP address.
- Detailed Description
- The SNMP server data cannot be created because there is an SNMP server data already exists with the same host IP address.
- Recommended Response Action
- Enter a valid SNMP server data with a unique host IP address, and then retry the operation.
- Category
- Configuration (NVRE = REST)
- Severity
- Critical
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
NVRE7001
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to create or update the fabric nodes by using the preferred leader setting because the personality is not in L3 Fabric mode.
- Detailed Description
- The fabric nodes cannot be created or updated by using the preferred leadersetting because the personality is not in L3 Fabric mode.
- Recommended Response Action
- Update the fabric node to L3 Fabric and retry the operation.
- Category
- Configuration (NVRE = REST)
- Severity
- Critical
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
NVRE7002
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to create or update the fabric nodes by using the preferred leader setting because the node is not a leaf node.
- Detailed Description
- The fabric nodes cannot be created or updated by using the preferred leadersetting because the node is not a leaf node.
- Recommended Response Action
- Assign the node the role of a leaf node, and then retry the operation.
- Category
- Configuration (NVRE = REST)
- Severity
- Warning
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
NVRE8001
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to complete RestConf operation because the Service Tag of the node is unavailable.
- Detailed Description
- The RestConf operation can not be performed because the Service Tag of the node entered is unavailable.
- Recommended Response Action
- Enter a valid and existing Service Tag of the node, and retry the operation.
- Category
- Configuration (NVRE = REST)
- Severity
- Critical
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
NVRE8002
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to perform the RestConf operation because the RestConf URL entered is invalid.
- Detailed Description
- The RestConf operation cannot be performed because the RestConf URL is invalid.
- Recommended Response Action
- Enter a valid RestConf URL. and then retry the operation.
- Category
- Configuration (NVRE = REST)
- Severity
- Critical
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
NVRE9003
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Information about the restore canot be retrieved because the restore ID entered is unavailable.
- Detailed Description
- Information about the restore cannot be retrieved beacuse the restore ID entered is unavailable.
- Recommended Response Action
- Enter a valid and existing restore ID, and retry the operation.
- Category
- Configuration (NVRE = REST)
- Severity
- Critical
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\