1 Overview

The Redfish standard comprises a set of specifications maintained by the Redfish Forum, a working group within DMTF. The standard defines a protocol that uses RESTful interfaces to provide access to data and operations associated with the management of systems and networks. One of the strengths of the Redfish protocol is that it works with a wide range of servers: from stand-alone servers to rack-mount and bladed environments to large-scale data centers and cloud environments.

The Redfish standard addresses several key issues for infrastructures that require scalability. Large infrastructures often consist of many simple servers of different makes and types. This hyper-scale usage model requires a new approach to systems management. The Redfish protocol addresses these needs by providing a standard protocol based on out-of-band systems management.

With these goals in mind, the Redfish protocol was designed as an open-industry standard to meet scalability requirements in multi-vendor deployments. It easily integrates with commonly used tools, using RESTful interfaces to perform operations and using JSON for data payloads.

1.1 Who should read this document?

Redfish responses can contain messages to help guide clients when next steps or corrective actions need to be taken. This document is useful for client developers who want to understand how to interpret standard Redfish messages. This document is also useful for service developers who want to understand how standard Redfish messages are to be used in their service.

1.2 How can I provide feedback?

Feedback on all Redfish specifications and documents is encouraged. Feedback can be directed to DMTF and the Redfish Forum by the following means:

• Redfish User Forum: https://redfishforum.com - User forum monitored by DMTF Redfish Forum personnel to answer questions about any Redfish-related topics.
• DMTF Feedback Portal: https://www.dmtf.org/standards/feedback - Formal submission portal for enhancements or proposals to DMTF and the Redfish Forum.

1.3 Where can I find more information?

The following web sites provide more information about the Redfish standard:

• Redfish Developer Hub

  Resources for developers who use Redfish to build applications. Contains an interactive schema explorer, hosted schema, and other links.

• Redfish Specification Forum

  DMTF Redfish-monitored user forum. Answers questions about Redfish-related topics.

• DMTF GitHub repositories

  Open source tools and libraries for working with Redfish.

• Redfish standards

  Schemas, specifications, mockups, white papers, FAQ, educational material, and more.

• DMTF Redfish Forum

  Working group that maintains the Redfish standard. Site lists member companies, future work and schedules, charter, and information about joining.

1.4 Related documents

The following documents are part of the Redfish development effort. They can be accessed or downloaded from DMTF's Redfish Standards web site: https://www.dmtf.org/standards/redfish

• DSP0218 - Platform Level Data Model (PLDM) for Redfish Device Enablement Specification - Binary-encoded JSON (BEJ) and dictionary-based mapping of Redfish schemas and properties into PLDM messages.
• DSP0266 - Redfish Specification - Main Redfish Specification.
• DSP0268 - Redfish Data Model Specification - Normative descriptions and additional text for every schema defined in DSP8010 and example payloads for every resource.
• DSP0270 - Redfish Host Interface Specification - "In-band" or "OS-based" Redfish host interface.
• DSP0272 - Redfish Interoperability Profiles Specification - Structure and JSON document that is used to define and publish an interoperability profile that checks an implementation's conformance to a defined minimum set of functionality.
• DSP2043 - Redfish Mockups Bundle - Set of mockups that can be used as sample output from GET responses from a Redfish service. Informative in nature, it was used to develop the schema. A person can set up an NGINX or similar server and configure it to output JSON format and then use this directory for demonstration purposes.
• DSP2044 - Redfish White Paper - Non-normative document helping those new to Redfish understand how to interact with the Redfish service and understand common functions and tasks.
• DSP2046 - Redfish Resource and Schema Guide - Informative documentation regarding common Redfish resource properties and a listing of properties that can be found in each of the Redfish resources.
• DSP2053 - Redfish Property Guide - Informative documentation providing an index to individual property definitions across all Redfish schema.
• DSP2065 - Redfish Message Registry Guide - Informative documentation providing details regarding the messages defined in Redfish standard message registries.
• DSP8010 - Redfish Schema - Redfish schema definitions. These files are normative in nature and are normatively referenced by the Redfish Specification. The three schema formats are CSDL (OData Common Schema Definition Language format, which is in XML), JSON Schema, and OpenAPI schema. These schema definitions should be functionally equivalent, thus specifying the schema in three different languages.
• DSP8011 - Redfish Standard Registries - Redfish registry definitions. This bundle of Redfish registries includes message registries used for Redfish-defined messages including events and privilege maps.
• DSP8013 - Redfish Interoperability Profiles Bundle - Bundle of published Redfish interoperability profile documents and supporting schema and sample documents used for creating profiles.

2 Reference guide

The following sections contain details for each message registry and their messages in the Redfish Standard Registries (DSP8011).

2.1 AccountSecurity 1.1.0

This registry defines the account security messages. These messages are intended for audit logs and security event notifications. Services shall not include these messages in responses to clients.

2.1.1 AccountCreated

Example: Account 'ContosoJoe' was created.

Indicates that an account was created.

• This message shall indicate that an account was created. Services shall not include this message in responses to clients.

Version Added: v1.0

Severity: OK

Resolution: None.

Message and Arguments: "Account '<1>' was created."

1. string: The username of the account that was created.
   • This argument shall contain the username of the account that was created.

2.1.2 AccountDisabled

Example: Account 'ContosoJoe' was disabled.

Indicates that an account was disabled.

• This message shall indicate that an account was disabled. Services shall not include this message in responses to clients.

Version Added: v1.0

Severity: Warning

Resolution: None.

Message and Arguments: "Account '<1>' was disabled."

1. string: The username of the account that was disabled.
   • This argument shall contain the username of the account that was disabled.

2.1.3 AccountEnabled

Example: Account 'ContosoJoe' was enabled.

Indicates that an account was enabled.

• This message shall indicate that an account was enabled. Services shall not include this message in responses to clients.

Version Added: v1.0

Severity: OK

Resolution: None.

Message and Arguments: "Account '<1>' was enabled."

1. string: The username of the account that was enabled.
   • This argument shall contain the username of the account that was enabled.

2.1.4 AccountLocked

Example: Account 'ContosoJoe' was locked due to excessive failed authorization attempts.

Indicates that an account was locked due to failed authorization attempts.

• This message shall indicate that an account was locked due to failed authorization attempts. Services shall not include this message in responses to clients.

Version Added: v1.0

Severity: Critical

Resolution: None.

Message and Arguments: "Account '<1>' was locked due to excessive failed authorization attempts."

1. string: The username of the account that was locked.
   • This argument shall contain the username of the account that was locked.

2.1.5 AccountLockoutExpired

Example: Account 'ContosoJoe' was unlocked following the expiration of a lockout timer.

Indicates that the lockout timer on an account expired and the account is now unlocked.

• This message shall indicate that the lockout timer on an account expired and the account is now unlocked. Services shall not include this message in responses to clients.

Version Added: v1.0

Severity: OK

Resolution: None.

Message and Arguments: "Account '<1>' was unlocked following the expiration of a lockout timer."

1. string: The username of the account that was unlocked.
   • This argument shall contain the username of the account that was unlocked.

2.1.6 AccountRemoved

Example: Account 'ContosoJoe' was removed.

Indicates that an account was removed.

• This message shall indicate that an account was removed. Services shall not include this message in responses to clients.

Version Added: v1.0

Severity: OK

Resolution: None.

Message and Arguments: "Account '<1>' was removed."

1. string: The username of the account that was removed.
   • This argument shall contain the username of the account that was removed.

2.1.7 AccountUnlocked

Example: Account 'ContosoJoe' was unlocked by an administrator.

Indicates that an account was manually unlocked.

• This message shall indicate that an account was manually unlocked. Services shall not include this message in responses to clients.

Version Added: v1.0

Severity: OK

Resolution: None.

Message and Arguments: "Account '<1>' was unlocked by an administrator."

1. string: The username of the account that was unlocked.
   • This argument shall contain the username of the account that was unlocked.

2.1.8 InsufficientPrivilege

Example: 'ContosoJoe' attempted an operation over 'Redfish' with the privileges 'Read', but requires the privileges 'Write'.

Indicates that a user with valid credentials attempted an operation without the necessary privileges.

• This message shall indicate that a user with valid credentials attempted an operation without the necessary privileges. Services shall not include this message in responses to clients.

Version Added: v1.0

Severity: Critical

Resolution: None.

Message and Arguments: "'<1>' attempted an operation over '<2>' with the privileges '<3>', but requires the privileges '<4>'."

1. string: The IP address of the user that attempted the operation.
   • This argument shall contain the IP address of the user that attempted the operation.
2. string: The protocol or interface over which the operation was attempted. Examples include 'Redfish', 'Web UI'. and 'SSH'.
   • This argument shall contain the protocol or interface over which the operation was attempted.
3. string: The privileges of the user that attempted the operation.
   • This argument shall contain the privileges of the user that attempted the operation.
4. string: The required privileges for the requested operation.
   • This argument shall contain the required privileges for the requested operation.

2.1.9 InvalidCredentials

Example: 'ContosoJoe' provided invalid credentials over 'HTTPS'.

Indicates that a user provided invalid credentials with a request.

• This message shall indicate that a user provided invalid credentials with a request, such as those found in the Authorization and X-Auth-Token HTTP request headers. Services shall not include this message in responses to clients.

Version Added: v1.0

Severity: Critical

Resolution: None.

Message and Arguments: "'<1>' provided invalid credentials over '<2>'."

1. string: The IP address of the user that attempted the operation.
   • This argument shall contain the IP address of the user that attempted the operation.
2. string: The protocol or interface over which the operation was attempted. Examples include 'Redfish', 'Web UI'. and 'SSH'.
   • This argument shall contain the protocol or interface over which the operation was attempted.

2.1.10 ManagerAccountRoleChanged

Example: Account 'ContosoJoe' has changed from role 'Administrator' to 'ReadOnly'.

Indicates that the role for an account was changed.

• This message shall indicate that the role for an account was changed. Services shall not include this message in responses to clients.

Version Added: v1.0

Severity: OK

Resolution: None.

Message and Arguments: "Account '<1>' has changed from role '<2>' to '<3>'."

1. string: The username of the account that was modified.
   • This argument shall contain the username of the account that was modified.
2. string: The former role for the account.
   • This argument shall contain the former Redfish role for the account.
3. string: The new role for the account
   • This argument shall contain the new Redfish role for the account.

2.1.11 PasswordModified

Example: The password for account 'ContosoJoe' was changed.

Indicates that the password of an account was changed.

• This message shall indicate that the password of an account was changed. Services shall not include this message in responses to clients.

Version Added: v1.0

Severity: OK

Resolution: None.

Message and Arguments: "The password for account '<1>' was changed."

1. string: The username of the account with the modified password.
   • This argument shall contain the username of the account with the modified password.

2.1.12 RolePrivilegeAdded

Example: Privilege 'Write' was added to role 'ReadOnly'.

Indicates that a privilege was added to a role.

• This message shall indicate that a privilege was added to a role. Services shall not include this message in responses to clients.

Version Added: v1.0

Severity: OK

Resolution: None.

Message and Arguments: "Privilege '<1>' was added to role '<2>'."

1. string: The privilege that was added to the role.
   • This argument shall contain the privilege that was added too the role.
2. string: The role that was modified.
   • This argument shall contain the Redfish role that was modified.

2.1.13 RolePrivilegeRemoved

Example: Privilege 'Write' was removed from role 'ReadOnly'.

Indicates that a privilege was removed from a role.

• This message shall indicate that a privilege was removed from a role. Services shall not include this message in responses to clients.

Version Added: v1.0

Severity: OK

Resolution: None.

Message and Arguments: "Privilege '<1>' was removed from role '<2>'."

1. string: The privilege that was removed from the role.
   • This argument shall contain the privilege that was removed from the role.
2. string: The role that was modified.
   • This argument shall contain the Redfish role that was modified.

2.1.14 SuccessfulLogin

Example: Successful login of user 'ContosoJoe' from '192.168.1.1' over 'HTTPS'.

Indicates that a user provided valid credentials and made a successful login.

• This message shall indicate that a user provided valid credentials and made a successful login. Services shall not include this message in responses to clients.

Version Added: v1.0

Severity: OK

Resolution: None.

Message and Arguments: "Successful login of user '<1>' from '<2>' over '<3>'."

1. string: The username of the account that made a successful login.
   • This argument shall contain the username of the account that made a successful login.
2. string: The IP address of the user that made a successful login.
   • This argument shall contain the IP address of the user that made a successful login.
3. string: The protocol or interface over which the login was made. Examples include 'Redfish', 'Web UI'. and 'SSH'.
   • This argument shall contain the protocol or interface over which the login was made.

2.1.15 UserCertificateAdded

Example: A user certificate was added to account 'ContosoJoe'.

Indicates that a user certificate was added to an account.

• This message shall indicate that a user certificate was added to an account. Services shall not include this message in responses to clients.

Version Added: v1.0

Severity: OK

Resolution: None.

Message and Arguments: "A user certificate was added to account '<1>'."

1. string: The username of the account with the certificate that was addedd.
   • This argument shall contain the username of the account with the certificate that was added.

2.1.16 UserCertificateRemoved

Example: A user certificate was removed from account 'ContosoJoe'.

Indicates that a user certificate was removed from an account.

• This message shall indicate that a user certificate was removed from an account. Services shall not include this message in responses to clients.

Version Added: v1.0

Severity: OK

Resolution: None.

Message and Arguments: "A user certificate was removed from account '<1>'."

1. string: The username of the account with the certificate that was removed.
   • This argument shall contain the username of the account with the certificate that was removed.

2.1.17 UserCertificateReplaced

Example: A user certificate was replaced on account 'ContosoJoe'.

Indicates that a user certificate was replaced on an account.

• This message shall indicate that a user certificate was replaced on an account. Services shall not include this message in responses to clients.

Version Added: v1.0

Severity: OK

Resolution: None.

Message and Arguments: "A user certificate was replaced on account '<1>'."

1. string: The username of the account with the certificate that was replaced.
   • This argument shall contain the username of the account with the certificate that was replaced.

2.1.18 UserKeyAdded

Example: A user key was added to account 'ContosoJoe'.

Indicates that a user key was added to an account.

• This message shall indicate that a user key was added to an account. Services shall not include this message in responses to clients.

Version Added: v1.0

Severity: OK

Resolution: None.

Message and Arguments: "A user key was added to account '<1>'."

1. string: The username of the account with the key that was added.
   • This argument shall contain the username of the account with the key that was added.

2.1.19 UserKeyRemoved

Example: A user key was removed from account 'ContosoJoe'.

Indicates that a user key was removed from an account.

• This message shall indicate that a user key was removed from an account. Services shall not include this message in responses to clients.

Version Added: v1.0

Severity: OK

Resolution: None.

Message and Arguments: "A user key was removed from account '<1>'."

1. string: The username of the account with the key that was removed.
   • This argument shall contain the username of the account with the key that was removed.

2.2 AutomationNodeEvent 1.1.0

This registry defines the messages for Automation node related events.

2.2.1 NodeDone

Example: The node with Id 'Node1' is done running.

A node is done running.

• This message shall indicate that a node NodeState property transitioned to Done.

Version Added: v1.0

Severity: OK

Resolution: None.

Message and Arguments: "The node with Id '<1>' is done running."

1. string: The Id of the node.
   • This argument shall contain the value of the Id property of the node resource that is done running.

2.2.2 NodeIdle

Example: The node with Id 'Node1' is idle.

A node is idle.

• This message shall indicate that a node NodeState property transitions to Idle.

Version Added: v1.0

Severity: OK

Resolution: None.

Message and Arguments: "The node with Id '<1>' is idle."

1. string: The Id of the node that is idle.
   • This argument shall contain the value of the Id property of the node resource that is idle.

2.2.3 NodeRunning

Example: The node with Id 'Node1' is running.

A node is running.

• This message shall indicate that a node NodeState property transitioned to one of the Running states.

Version Added: v1.0

Severity: OK

Resolution: None.

Message and Arguments: "The node with Id '<1>' is running."

1. string: The Id of the node.
   • This argument shall contain the value of the Id property of the node resource that is running.

2.2.4 NodeStoppedCondition

Example: The node with Id 'Node1' has stopped because of conditions.

A node has stopped because of conditions.

• This message shall indicate that a node has stopped and the NodeState property transitioned to ConditionStop.

Version Added: v1.0

Severity: Warning

Resolution: None.

Message and Arguments: "The node with Id '<1>' has stopped because of conditions."

1. string: The Id of the node.
   • This argument shall contain the value of the Id property of the node resource that has stopped.

2.2.5 NodeStoppedError

Example: The node with Id 'Node1' has stopped with warnings or errors.

A node has stopped with warnings or errors.

• This message shall indicate that a node has stopped and the NodeState property transitioned to ErrorStop.

Version Added: v1.0

Severity: Warning

Resolution: None.

Message and Arguments: "The node with Id '<1>' has stopped with warnings or errors."

1. string: The Id of the node.
   • This argument shall contain the value of the Id property of the node resource that has stopped.

2.2.6 NodeWaiting

Example: The node with Id 'Node1' is waiting.

A node is waiting.

• This message shall indicate that a node NodeState property transitioned to Waiting.

Version Added: v1.0

Severity: OK

Resolution: None.

Message and Arguments: "The node with Id '<1>' is waiting."

1. string: The Id of the node.
   • This argument shall contain the value of the Id property of the node resource that is waiting.

2.3 Base 1.23.0

This registry defines the base messages for Redfish.

2.3.1 AccessDenied

Example: While attempting to establish a connection to '/redfish/v1/UpdateService/FirmwareInventory/1/Actions/FirmwareInventory.UpdateImage', the service denied access.

Indicates that while attempting to access, connect to, or transfer to or from another resource, the service denied access.

• This message shall indicate that while attempting to access, connect to, or transfer to or from another resource, the service denied access.

Version Added: v1.0

Severity: Critical

Resolution: Attempt to ensure that the URI is correct and that the service has the appropriate credentials.

Message and Arguments: "While attempting to establish a connection to '<1>', the service denied access."

1. string: The URI provided.
   • This argument shall contain the URI provided for this operation.

2.3.2 AccessForbidden

Example: Forbidden.

Indicates that the request contained valid credentials, but the user does not have the necessary privileges to perform the requested operation.

• This message shall indicate that the request contained valid credentials, but the user does not have the necessary privileges to perform the requested operation.

Deprecated in v1.22 and later. This message was deprecated in favor of the existing InsufficientPrivilege message.

Version Added: v1.20

Severity: Critical

Resolution: Resubmit the request with credentials that contain the necessary privileges to perform the requested operation.

Message and Arguments: "Forbidden."

2.3.3 AccessUnauthorized

Example: Unauthorized.

Indicates that the request did not contain valid credentials.

• This message shall indicate that the request did not contain valid credentials, such as those found in the Authorization and X-Auth-Token HTTP request headers.

Version Added: v1.20

Severity: Critical

Resolution: Resubmit the request with valid credentials.

Message and Arguments: "Unauthorized."

2.3.4 AccountForSessionNoLongerExists

Example: The account for the current session was removed, and so the current session was removed as well.

Indicates that the account for the session was removed, and so the session was removed as well.

• This message shall indicate that the account for the session was removed, and so the session was removed as well.

Version Added: v1.0

Severity: OK

Resolution: Attempt to connect with a valid account.

Message and Arguments: "The account for the current session was removed, and so the current session was removed as well."

2.3.5 AccountModified

Example: The account was successfully modified.

Indicates that the account was successfully modified.

• This message shall indicate that the account was successfully modified.

Version Added: v1.0

Severity: OK

Resolution: None.

Message and Arguments: "The account was successfully modified."

2.3.6 AccountNotModified

Example: The account modification request failed.

Indicates that the modification requested for the account was not successful.

• This message shall indicate that the modification requested for the account was not successful.

Version Added: v1.0

Severity: Warning

Resolution: The modification may have failed due to permission issues or issues with the request body.

Message and Arguments: "The account modification request failed."

2.3.7 AccountRemoved

Example: The account was successfully removed.

Indicates that the account was successfully removed.

• This message shall indicate that the account was successfully removed.

Version Added: v1.0

Severity: OK

Resolution: None.

Message and Arguments: "The account was successfully removed."

2.3.8 ActionDeprecated

Example: The action 'OldAction' is deprecated.

Indicates the action is deprecated.

• This message shall indicate that the action is deprecated.

Version Added: v1.10

Severity: Warning

Resolution: Refer to the schema guide for more information.

Message and Arguments: "The action '<1>' is deprecated."

1. string: The name of the action.
   • This argument shall contain the name of the action that is deprecated.

2.3.9 ActionNotSupported

Example: The action 'DeactivateCloakingDevice' is not supported by the resource.

Indicates that the action supplied with the POST operation is not supported by the resource.

• This message shall indicate that the action supplied with the POST operation is not supported by the resource.

Version Added: v1.0

Severity: Critical

Resolution: Check the Actions property in the resource for the supported actions.

Message and Arguments: "The action '<1>' is not supported by the resource."

1. string: The name of the action.
   • This argument shall contain the name of the action.

2.3.10 ActionParameterDuplicate

Example: The action 'Reset' was submitted with more than one value for the parameter 'ResetType'.

Indicates that the action was supplied with a duplicated action parameter in the request body.

• This message shall indicate that the action was supplied with a duplicated action parameter in the request body.

Version Added: v1.0

Severity: Warning

Resolution: Resubmit the action with only one instance of the action parameter in the request body if the operation failed.

Message and Arguments: "The action '<1>' was submitted with more than one value for the parameter '<2>'."

1. string: The name of the action.
   • This argument shall contain the name of the action.
2. string: The name of the action parameter.
   • This argument shall contain the name of the action parameter.

2.3.11 ActionParameterMissing

Example: The action 'Reset' requires the parameter 'ResetType' to be present in the request body.

Indicates that the action requested was missing an action parameter that is required to process the action.

• This message shall indicate that the action requested was missing an action parameter that is required to process the action.

Version Added: v1.0

Severity: Critical

Resolution: Supply the action with the required parameter in the request body when the request is resubmitted.

Message and Arguments: "The action '<1>' requires the parameter '<2>' to be present in the request body."

1. string: The name of the action.
   • This argument shall contain the name of the action.
2. string: The name of the action parameter.
   • This argument shall contain the name of the action parameter.

2.3.12 ActionParameterNotSupported

Example: The parameter 'InvalidParameter' for the action 'Reset' is not supported on the target resource.

Indicates that the parameter supplied for the action is not supported on the resource.

• This message shall indicate that the parameter supplied for the action is not supported on the resource.

Version Added: v1.0

Severity: Warning

Resolution: Remove the parameter supplied and resubmit the request if the operation failed.

Message and Arguments: "The parameter '<1>' for the action '<2>' is not supported on the target resource."

1. string: The name of the action parameter.
   • This argument shall contain the name of the action parameter.
2. string: The name of the action.
   • This argument shall contain the name of the action.

2.3.13 ActionParameterUnknown

Example: The action 'Reset' was submitted with the invalid parameter 'InvalidParameter'.

Indicates that an action was submitted but an action parameter supplied did not match any of the known parameters.

• This message shall indicate that an action was submitted but an action parameter supplied did not match any of the known parameters.

Version Added: v1.0

Severity: Warning

Resolution: Correct the invalid action parameter and resubmit the request if the operation failed.

Message and Arguments: "The action '<1>' was submitted with the invalid parameter '<2>'."

1. string: The name of the action.
   • This argument shall contain the name of the action.
2. string: The name of the action parameter.
   • This argument shall contain the name of the action parameter.

2.3.14 ActionParameterValueConflict

Example: The parameter 'ResetType' with the requested value of 'ForceRestart' does not meet the constraints of the implementation.

Indicates that the requested parameter value could not be completed because of a mismatch with other parameters or properties in the resource.

• This message shall indicate that the requested parameter value could not be completed because of a mismatch with other parameters or properties in the resource.

Version Added: v1.12

Severity: Warning

Resolution: None.

Message and Arguments: "The parameter '<1>' with the requested value of '<2>' does not meet the constraints of the implementation."

1. string: The name of the parameter for which a write was requested.
   • This argument shall contain the name of the parameter provided in the action request.
2. string: The value of the parameter with which there is a conflict.
   • This argument shall contain the value of the parameter with which there is a conflict.

2.3.15 ActionParameterValueError

Example: The value 'InvalidValue' for the parameter 'ResetType' in the action 'Reset' is invalid.

Indicates that a parameter was given an invalid value.

• This message shall indicate that a parameter was given an invalid value, and the value cannot or should not be included in the message.

Version Added: v1.11

Severity: Warning

Resolution: Correct the value for the parameter in the request body and resubmit the request if the operation failed.

Message and Arguments: "The value for the parameter '<1>' in the action '<2>' is invalid."

1. string: The name of the action parameter.
   • This argument shall contain the name of the action parameter.
2. string: The name of the action.
   • This argument shall contain the name of the action.

2.3.16 ActionParameterValueFormatError

Example: The value '2024-01-01' for the parameter 'ManufactureDate' in the action 'UpdateManufactureDate' is not a format that the parameter can accept.

Indicates that a parameter was given the correct value type but the format of the value is not supported.

• This message shall indicate that a parameter was given the correct value type but the format of the value is not supported.

Version Added: v1.0

Severity: Warning

Resolution: Correct the value for the parameter in the request body and resubmit the request if the operation failed.

Message and Arguments: "The value '<1>' for the parameter <2> in the action <3> is not a format that the parameter can accept."

1. string: The value provided for the action parameter.
   • This argument shall contain the value provided for the action parameter. Numeric values shall be converted to a string, and null values shall be represented by the string null.
2. string: The name of the action parameter.
   • This argument shall contain the name of the action parameter.
3. string: The name of the action.
   • This argument shall contain the name of the action.

2.3.17 ActionParameterValueNotInList

Example: The value 'InvalidValue' for the parameter 'ResetType' in the action 'Reset' is not in the list of acceptable values.

Indicates that a parameter was given the correct value type but the value of that parameter was not supported. The value is not in an enumeration.

• This message shall indicate that a parameter was given the correct value type but the value of that parameter was not supported.

Version Added: v1.10

Severity: Warning

Resolution: Choose a value from the enumeration list that the implementation can support and resubmit the request if the operation failed.

Message and Arguments: "The value '<1>' for the parameter <2> in the action <3> is not in the list of acceptable values."

1. string: The value provided for the action parameter.
   • This argument shall contain the value provided for the action parameter.
2. string: The name of the action parameter.
   • This argument shall contain the name of the action parameter.
3. string: The name of the action.
   • This argument shall contain the name of the action.

2.3.18 ActionParameterValueOutOfRange

Example: The value '-5' for the parameter 'MemorySizeGB' in the action 'UpdateMemorySize' is not in the supported range of acceptable values.

Indicates that a parameter was given the correct value type but the value of that parameter is outside the supported range.

• This value shall indicate that a parameter was given the correct value type but the value of that parameter is outside the supported range.

Version Added: v1.18

Severity: Warning

Resolution: Correct the value for the parameter in the request body and resubmit the request if the operation failed.

Message and Arguments: "The value '<1>' for the parameter <2> in the action <3> is not in the supported range of acceptable values."

1. string: The value provided for the parameter.
   • This argument shall contain the value provided for the parameter.
2. string: The name of the parameter.
   • This argument shall contain the name of the parameter.
3. string: The name of the action.
   • This argument shall contain the name of the action.

2.3.19 ActionParameterValueTypeError

Example: The value '123' for the parameter 'ResetType' in the action 'Reset' is not a type that the parameter can accept.

Indicates that a parameter was given the wrong value type, such as when a number is supplied for a parameter that requires a string.

• This message shall indicate that a parameter was given the wrong value type, such as when a number is supplied for a parameter that requires a string.

Version Added: v1.0

Severity: Warning

Resolution: Correct the value for the parameter in the request body and resubmit the request if the operation failed.

Message and Arguments: "The value '<1>' for the parameter '<2>' in the action '<3>' is not a type that the parameter can accept."

1. string: The value provided for the action parameter.
   • This argument shall contain the value provided for the action parameter. Numeric values shall be converted to a string, and null values shall be represented by the string null.
2. string: The name of the action parameter.
   • This argument shall contain the name of the action parameter.
3. string: The name of the action.
   • This argument shall contain the name of the action.

2.3.20 ArraySizeTooLong

Example: The array provided for property 'AssociatedDrives' exceeds the size limit 100.

Indicates that the size of the array exceeded the maximum number of elements.

• This message shall indicate that the size of the array exceeded the maximum number of elements.

Version Added: v1.16

Severity: Warning

Resolution: Resubmit the request with an appropriate array size.

Message and Arguments: "The array provided for property '<1>' exceeds the size limit <2>."

1. string: The name of the property.
   • This argument shall contain the name of the property.
2. number: The maximum number of elements supported for the array.
   • This argument shall contain the maximum number of elements supported for the array for this property.

2.3.21 ArraySizeTooShort

Example: The array provided for property 'AssociatedDrives' is under the minimum size limit 1.

Indicates that the size of the array is less than the minimum number of elements.

• This message shall indicate that the size of the array is less than the minimum number of elements.

Version Added: v1.16

Severity: Warning

Resolution: Resubmit the request with an appropriate array size.

Message and Arguments: "The array provided for property '<1>' is under the minimum size limit <2>."

1. string: The name of the property.
   • This argument shall contain the name of the property.
2. number: The minimum number of elements supported for the array.
   • This argument shall contain the minimum number of elements supported for the array for this property.

2.3.22 AuthenticationTokenRequired

Example: The request could not be performed because an authentication token was not provided.

Indicates that the request could not be performed because an authentication token was not provided.

• This message shall indicate that the request could not be performed because the user provided in the request requires multifactor authentication and an authentication token was not provided.

Version Added: v1.15

Severity: Critical

Resolution: Obtain an authentication token and resubmit the request.

Message and Arguments: "The request could not be performed because an authentication token was not provided."

2.3.23 ChassisPowerStateOffRequired

Example: The chassis with Id 'Chassis1' is required to be powered off to perform this request.

Indicates that the request requires a specified chassis to be powered off.

• This message shall indicate that the request requires the specified Chassis resource to be powered off as indicated by its PowerState property.

Version Added: v1.6

Severity: Warning

Resolution: Power off the specified chassis and resubmit the request.

Message and Arguments: "The chassis with Id '<1>' is required to be powered off to perform this request."

1. string: The Id of the chassis that is required to be powered off.
   • This argument shall contain the value of the Id property of the Chassis resource that is required to be powered off.

2.3.24 ChassisPowerStateOnRequired

Example: The chassis with Id 'Chassis1' is required to be powered on to perform this request.

Indicates that the request requires a specified chassis to be powered on.

• This message shall indicate that the request requires the specified Chassis resource to be powered on as indicated by its PowerState property.

Version Added: v1.6

Severity: Warning

Resolution: Power on the specified chassis and resubmit the request.

Message and Arguments: "The chassis with Id '<1>' is required to be powered on to perform this request."

1. string: The Id of the chassis that is required to be powered on.
   • This argument shall contain the value of the Id property of the Chassis resource that is required to be powered on.

2.3.25 ConditionInRelatedResource

Example: One or more conditions exist in a related resource. See the OriginOfCondition property.

Indicates that one or more fault or error conditions exist in a related resource.

• This message shall indicate that one or more conditions that require attention exist in a resource that affects the Health or HealthRollup of this resource. This message can be used in place of multiple messages in a Conditions property to roll up conditions from a single resource. The resource can be located using the OriginOfCondition property. The value of the MessageSeverity property should match the highest severity of any conditions in the resource referenced by the OriginOfCondition property.

Version Added: v1.9

Severity: Warning

Resolution: Check the Conditions array in the resource shown in the OriginOfCondition property to determine the conditions that need attention.

Message and Arguments: "One or more conditions exist in a related resource. See the OriginOfCondition property."

2.3.26 CouldNotEstablishConnection

Example: The service failed to establish a connection with the URI '/redfish/v1/UpdateService/FirmwareInventory/1/Actions/FirmwareInventory.UpdateImage'.

Indicates that the attempt to access the resource, file, or image at the URI was unsuccessful because a session could not be established.

• This message shall indicate that the attempt to access the resource, file, or image at the URI was unsuccessful because a session could not be established.

Version Added: v1.0

Severity: Critical

Resolution: Ensure that the URI contains a valid and reachable node name, protocol information, and other URI components.

Message and Arguments: "The service failed to establish a connection with the URI '<1>'."

1. string: The URI provided.
   • This argument shall contain the URI provided for this operation.

2.3.27 CreateFailedMissingReqProperties

Example: The create operation failed because the required property 'Name' was missing from the request.

Indicates that a create operation was attempted on a resource but that properties that are required for the create operation were missing from the request.

• This message shall indicate that a create operation was attempted on a resource but that properties that are required for the create operation were missing from the request.

Deprecated in v1.14 and later. This message was deprecated in favor of PropertyMissing.

Version Added: v1.0

Severity: Critical

Resolution: Correct the body to include the required property with a valid value and resubmit the request if the operation failed.

Message and Arguments: "The create operation failed because the required property '<1>' was missing from the request."

1. string: The name of the required property.
   • This argument shall contain the name of the required property.

2.3.28 CreateLimitReachedForResource

Example: The create operation failed because the resource has reached the limit of possible resources.

Indicates that no more resources can be created on the resource as it has reached its create limit.

• This message shall indicate that no more resources can be created on the resource as it has reached its create limit.

Version Added: v1.0

Severity: Critical

Resolution: Either delete resources and resubmit the request if the operation failed or do not resubmit the request.

Message and Arguments: "The create operation failed because the resource has reached the limit of possible resources."

2.3.29 Created

Example: The resource was created successfully.

Indicates that all conditions of a successful create operation were met.

• This message shall indicate that all conditions of a successful create operation were met.

Version Added: v1.0

Severity: OK

Resolution: None.

Message and Arguments: "The resource was created successfully."

2.3.30 EmptyJSON

Example: The request body submitted contained an empty JSON object and the service is unable to process it.

Indicates that the request body contained an empty JSON object when one or more properties are expected in the body.

• This message shall indicate that the request body contained an empty JSON object when one or more properties are expected in the body.

Version Added: v1.2

Severity: Warning

Resolution: Add properties in the JSON object and resubmit the request.

Message and Arguments: "The request body submitted contained an empty JSON object and the service is unable to process it."

2.3.31 EventBufferExceeded

Example: Undelivered events may have been lost due to exceeding the event buffer.

Indicates undelivered events may have been lost due to a lack of buffer space in the service.

• This message shall indicate that event buffer space used by the service has been exceeded, and as a result one or more undelivered events may have been lost.

Version Added: v1.13

Severity: Warning

Resolution: None.

Message and Arguments: "Undelivered events may have been lost due to exceeding the event buffer."

2.3.32 EventSubscriptionLimitExceeded

Example: The event subscription failed due to the number of simultaneous subscriptions exceeding the limit of the implementation.

Indicates that an event subscription establishment was requested but the operation failed due to the number of simultaneous connections exceeding the limit of the implementation.

• This message shall indicate that an event subscription establishment was requested but the operation failed due to the number of simultaneous connections exceeding the limit of the implementation.

Version Added: v1.0

Severity: Critical

Resolution: Reduce the number of other subscriptions before trying to establish the event subscription or increase the limit of simultaneous subscriptions, if supported.

Message and Arguments: "The event subscription failed due to the number of simultaneous subscriptions exceeding the limit of the implementation."

2.3.33 GeneralError

Example: A general error has occurred. See Resolution for information on how to resolve the error, or @Message.ExtendedInfo if Resolution is not provided.

Indicates that a general error has occurred. Use in @Message.ExtendedInfo is discouraged. When used in @Message.ExtendedInfo, implementations are expected to include a Resolution property with this message and provide a service-defined resolution to indicate how to resolve the error.

• This message shall indicate that a general error has occurred. Implementations should not use this message in @Message.ExtendedInfo. If used in @Message.ExtendedInfo, implementations should include a Resolution property with this message and provide a service-defined resolution to indicate how to resolve the error.

Version Added: v1.0

Severity: Critical

Resolution: None.

Message and Arguments: "A general error has occurred. See Resolution for information on how to resolve the error, or @Message.ExtendedInfo if Resolution is not provided."

2.3.34 GenerateSecretKeyRequired

Example: The Time-based One-Time Password (TOTP) secret key for this account must be generated before access is granted. Perform the GenerateSecretKey action at URI '/redfish/v1/AccountService/Accounts/1/GenerateSecretKey' and retain the secret key from the response.

Indicates that the Time-based One-Time Password (TOTP) secret key needs to be generated for the account before accessing the service. The secret key can be generated with a POST to the GenerateSecretKey action for the ManagerAccount resource instance.

• This message shall indicate that the RFC6238-defined Time-based One-Time Password (TOTP) secret key needs to be generated for the account before accessing the service. The secret key can be generated with a POST to the GenerateSecretKey action for the ManagerAccount resource instance.

Version Added: v1.19

Severity: Critical

Resolution: Generate secret key for this account by performing the GenerateSecretKey action on the referenced URI and retaining the secret key from the action response to produce a Time-based One-Time Password (TOTP) for the Token property in future session creation requests.

Message and Arguments: "The Time-based One-Time Password (TOTP) secret key for this account must be generated before access is granted. Perform the GenerateSecretKey action at URI '<1>' and retain the secret key from the response."

1. string: The URI for the GenerateSecretKey action of the account that requires a new Time-based One-Time Password (TOTP) secret key.
   • This argument shall contain the URI for the GenerateSecretKey action of the account that requires a new RFC6238-defined Time-based One-Time Password (TOTP) secret key.

2.3.35 HeaderInvalid

Example: Header 'X-Auth-Token' is invalid.

Indicates that a request header is invalid.

• This message shall indicate that a request header is known but is invalid.

Version Added: v1.13

Severity: Critical

Resolution: Resubmit the request with a valid request header.

Message and Arguments: "Header '<1>' is invalid."

1. string: The request header.
   • This argument shall contain the full request header, including the field name and field value.

2.3.36 HeaderMissing

Example: Required header 'X-Auth-Token' is missing in the request.

Indicates that a required request header is missing.

• This message shall indicate that a required request header is missing in the request.

Version Added: v1.13

Severity: Critical

Resolution: Resubmit the request with the required request header.

Message and Arguments: "Required header '<1>' is missing in the request."

1. string: The missing required request header.
   • This argument shall contain the missing required request header.

2.3.37 InsufficientPrivilege

Example: There are insufficient privileges for the account or credentials associated with the current session to perform the requested operation.

Indicates that the credentials associated with the established session do not have sufficient privileges for the requested operation.

• This message shall indicate that the credentials associated with the established session do not have sufficient privileges for the requested operation.

Version Added: v1.0

Severity: Critical

Resolution: Either abandon the operation or change the associated access rights and resubmit the request if the operation failed.

Message and Arguments: "There are insufficient privileges for the account or credentials associated with the current session to perform the requested operation."

2.3.38 InsufficientStorage

Example: Insufficient storage or memory available to complete the request.

Indicates that the operation could not be completed due to a lack of storage or memory available to the service.

• This message shall indicate that the request exceeds the storage or memory available to the service. For cases where the payload is larger than the maximum size supported, regardless of available storage, the message PayloadTooLarge shall be used.

Version Added: v1.13

Severity: Critical

Resolution: Increase the free storage space available to the service and resubmit the request.

Message and Arguments: "Insufficient storage or memory available to complete the request."

2.3.39 InternalError

Example: The request failed due to an internal service error. The service is still operational.

Indicates that the request failed for an unknown internal error but that the service is still operational.

• This message shall indicate that the request failed for an unknown internal error but that the service is still operational.

Version Added: v1.0

Severity: Critical

Resolution: Resubmit the request. If the problem persists, consider resetting the service.

Message and Arguments: "The request failed due to an internal service error. The service is still operational."

2.3.40 InvalidIndex

Example: The index -5 is not a valid offset into the array.

The index is not valid.

• This message shall indicate that the index is not valid.

Version Added: v1.0

Severity: Warning

Resolution: Verify the index value provided is within the bounds of the array.

Message and Arguments: "The index <1> is not a valid offset into the array."

1. number: The array index.
   • This argument shall contain the array index value provided.

2.3.41 InvalidJSON

Example: The request body submitted is invalid JSON starting at line 10 and could not be parsed by the receiving service.

Indicates that the request body contains invalid JSON.

• This message shall indicate that the request body contains invalid JSON.

Version Added: v1.10

Severity: Critical

Resolution: Ensure that the request body is valid JSON and resubmit the request.

Message and Arguments: "The request body submitted is invalid JSON starting at line <1> and could not be parsed by the receiving service."

1. number: The line number where the invalid JSON starts.
   • This argument shall contain the line number where the invalid JSON starts.

2.3.42 InvalidObject

Example: The object at '/redfish/v1/Systems/InvalidSystem' is invalid.

Indicates that the object in question is invalid according to the implementation. An example is a firmware update malformed URI.

• This message shall indicate that the object in question is invalid according to the implementation.

Version Added: v1.0

Severity: Critical

Resolution: Either the object is malformed or the URI is not correct. Correct the condition and resubmit the request if it failed.

Message and Arguments: "The object at '<1>' is invalid."

1. string: The URI provided.
   • This argument shall contain the URI provided for this operation.

2.3.43 InvalidScheme

Example: The URI 'tftp://Contoso.com/file' contains a scheme that is not supported.

The scheme of the URI of a property or action parameter provided in the request body is not supported. For example, if tftp is provided for the scheme, but TFTP is not supported.

• This message shall indicate the scheme of the URI of a property or action parameter provided in the request body is not supported.

Version Added: v1.23

Severity: Warning

Resolution: Resubmit the request with an appropriate scheme for the URI.

Message and Arguments: "The URI '<1>' contains a scheme that is not supported."

1. string: The URI provided.
   • This argument shall contain the URI provided for this operation.

2.3.44 InvalidURI

Example: The URI '/redfish/v1/Systems/InvalidSystem' was not found.

Indicates that the operation encountered a URI that does not correspond to a valid resource.

• This message shall indicate that the operation encountered a URI that does not correspond to a valid resource.

Version Added: v1.10

Severity: Critical

Resolution: Provide a valid URI and resubmit the request.

Message and Arguments: "The URI '<1>' was not found."

1. string: The supplied URI.
   • This argument shall contain the invalid URI that was encountered.

2.3.45 LicenseRequired

Example: A license is required for this operation: 'AdvancedPowerManagement'.

Indicates that a license is required to perform the requested operation.

• This message shall indicate that that a license is required to perform the requested operation.

Version Added: v1.16

Severity: Critical

Resolution: Install the requested license and resubmit the request.

Message and Arguments: "A license is required for this operation: '<1>'."

1. string: The vendor description of the license required to perform the operation.
   • This argument shall contain the vendor description of the license required to perform the operation.

2.3.46 MalformedJSON

Example: The request body submitted was malformed JSON and could not be parsed by the receiving service.

Indicates that the request body was malformed JSON.

• This message shall indicate that the request body was malformed JSON.

Version Added: v1.0

Severity: Critical

Resolution: Ensure that the request body is valid JSON and resubmit the request.

Message and Arguments: "The request body submitted was malformed JSON and could not be parsed by the receiving service."

2.3.47 MaximumErrorsExceeded

Example: Too many errors have occurred to report them all.

Indicates that so many errors have occurred that the reporting service cannot return them all.

• The maximum number of errors that the implementation can report was exceeded. This shall not be the only message reported by the service. The use of this message should be limited to RDE implementations.

Version Added: v1.8

Severity: Critical

Resolution: Resolve other reported errors and retry the current operation.

Message and Arguments: "Too many errors have occurred to report them all."

2.3.48 MissingOrMalformedPart

Example: The multipart request contains malformed parts or is missing required parts.

Indicates that a multipart request is missing a required part or contains malformed parts.

• This message shall indicate that the request payload supplied as part of an HTTP multipart request is missing one or more required parts or contains malformed parts.

Version Added: v1.13

Severity: Critical

Resolution: Add any missing required parts or correct the malformed parts and resubmit the request.

Message and Arguments: "The multipart request contains malformed parts or is missing required parts."

2.3.49 NetworkNameResolutionNotConfigured

Example: Network name resolution is not configured on this service.

Indicates that network-based name resolution is not configured on the service.

• This message shall indicate that network-based name resolution, such as DNS or WINS protocols, is not configured on the service.

Version Added: v1.11

Severity: Warning

Resolution: Configure the network-based name resolution protocol support on this service, or update any URI values to include an IP address instead of a network name and resubmit the request.

Message and Arguments: "Network name resolution is not configured on this service."

2.3.50 NetworkNameResolutionNotSupported

Example: Resolution of network-based names is not supported by this service.

Indicates the service does not support network-based name resolution.

• This message shall indicate that the service does not support network-based name resolution, such as DNS or WINS protocols. URIs provided as property values must contain an IP address as the service cannot resolve a network name.

Version Added: v1.11

Severity: Warning

Resolution: Update any URI values to include an IP address instead of a network name and resubmit the request.

Message and Arguments: "Resolution of network-based names is not supported by this service."

2.3.51 NoOperation

Example: The request body submitted contain no data to act upon and no changes to the resource took place.

Indicates that the requested operation will not perform any changes on the service.

• This message shall indicate that the requested operation will not perform any changes on the service.

Version Added: v1.4

Severity: Warning

Resolution: Add properties in the JSON object and resubmit the request.

Message and Arguments: "The request body submitted contain no data to act upon and no changes to the resource took place."

2.3.52 NoValidSession

Example: There is no valid session established with the implementation.

Indicates that the operation failed because a valid session is required in order to access any resources.

• This message shall indicate that the operation failed because a valid session is required in order to access any resources.

Version Added: v1.0

Severity: Critical

Resolution: Establish a session before attempting any operations.

Message and Arguments: "There is no valid session established with the implementation."

2.3.53 OneTimePasscodeSent

Example: A one-time passcode was sent to: 'joe@contoso.com'. Supply the passcode as the Token property in the request to create a session.

Indicates that a required one-time passcode was sent to the user. The code should be provided as the Token property in the request to create a session.

• This message shall indicate that a one-time passcode was generated by the service as the result of a request to create a session. The one-time passcode shall be sent to the delivery address associated with account credentials supplied in the request.

Version Added: v1.17

Severity: OK

Resolution: Obtain the one-time passcode sent to the delivery address and resubmit the request using the passcode as the Token property.

Message and Arguments: "A one-time passcode was sent to: '<1>'. Supply the passcode as the Token property in the request to create a session."

1. string: The delivery address for the one-time passcode. The address is at least partially redacted.
   • This argument shall contain the delivery address for the one-time passcode. The value shall be partially or fully redacted to prevent receipt by unauthorized clients.

2.3.54 OperationFailed

Example: An error occurred internal to the service as part of the overall request. Partial results may have been returned.

Indicates that one of the internal operations necessary to complete the request failed. An example of this is when an internal service provider is unable to complete the request, such as in aggregation or RDE.

• This message shall indicate that one of the internal operations necessary to complete the request failed. Partial results of the client operation may be returned.

Version Added: v1.8

Severity: Warning

Resolution: Resubmit the request. If the problem persists, consider resetting the service or provider.

Message and Arguments: "An error occurred internal to the service as part of the overall request. Partial results may have been returned."

2.3.55 OperationNotAllowed

Example: The HTTP method is not allowed on this resource.

Indicates that the HTTP method in the request is not allowed on this resource.

• This message shall indicate that the HTTP method in the request is not allowed on this resource. This error message should be used together with HTTP status code 405 Method Not Allowed.

Version Added: v1.13

Severity: Critical

Resolution: None.

Message and Arguments: "The HTTP method is not allowed on this resource."

2.3.56 OperationTimeout

Example: A timeout internal to the service occurred as part of the request. Partial results may have been returned.

Indicates that one of the internal operations necessary to complete the request timed out. An example of this is when an internal service provider is unable to complete the request, such as in aggregation or RDE.

• This message shall indicate that one of the internal operations necessary to complete the request timed out. Partial results of the client operation may be returned.

Version Added: v1.8

Severity: Warning

Resolution: Resubmit the request. If the problem persists, consider resetting the service or provider.

Message and Arguments: "A timeout internal to the service occurred as part of the request. Partial results may have been returned."

2.3.57 PasswordChangeRequired

Example: The password provided for this account must be changed before access is granted. PATCH the Password property for this account located at the target URI '/redfish/v1/Managers/1/Accounts/1' to complete this process.

Indicates that the password for the account provided must be changed before accessing the service. The password can be changed with a PATCH to the Password property in the manager account resource instance. Implementations that provide a default password for an account may require a password change prior to first access to the service.

• This message shall indicate that the password for the account provided must be changed before accessing the service. The password can be changed with a PATCH to the Password property in the manager account resource instance. Implementations that provide a default password for an account may require a password change prior to first access to the service.

Version Added: v1.5

Severity: Critical

Resolution: Change the password for this account using a PATCH to the Password property at the URI provided.

Message and Arguments: "The password provided for this account must be changed before access is granted. PATCH the Password property for this account located at the target URI '<1>' to complete this process."

1. string: The URI of the target resource.
   • This argument shall contain the URI of the target manager account resource instance.

2.3.58 PasswordComplexityNotMet

Example: The password provided for this account does not meet the password complexity requirements of the service.

Indicates that the password for the account provided does not meet the password complexity requirements of the service. The password for the account was not changed.

• This message shall indicate that the password for the account provided does not meet the password complexity requirements of the service.

Version Added: v1.21

Severity: Critical

Resolution: Resubmit the request with a password that meets the password complexity requirements as specified by the PasswordGuidanceMessage property in the AccountService resource.

Message and Arguments: "The password provided for this account does not meet the password complexity requirements of the service."

2.3.59 PasswordIncorrectLength

Example: The password provided for this account does not meet the password length requirements of the service.

Indicates that the password for the account provided does not meet the password length requirements of the service. The password for the account was not changed.

• This message shall indicate that the password for the account provided does not meet the length requirements of the service. The length of the supplied password is either too short or too long.

Version Added: v1.21

Severity: Critical

Resolution: Resubmit the request with a password that meets the password length requirements as specified by the MinPasswordLength and MaxPasswordLength properties in the AccountService resource.

Message and Arguments: "The password provided for this account does not meet the password length requirements of the service."

2.3.60 PasswordReuseTooRecent

Example: The password provided for this account does not meet the password reuse requirements of the service.

Indicates that the password for the account provided does not meet the password reuse requirements of the service. The password for the account was not changed.

• This message shall indicate that the password for the account provided does not meet the password reuse requirements of the service. The supplied password was used too recently.

Version Added: v1.21

Severity: Critical

Resolution: Resubmit the request with a password that meets the password reuse requirements specified by the EnforcePasswordHistoryCount property in the AccountService resource.

Message and Arguments: "The password provided for this account does not meet the password reuse requirements of the service."

2.3.61 PayloadTooLarge

Example: The supplied payload exceeds the maximum size supported by the service.

Indicates that the supplied payload is too large to be accepted by the service.

• This message shall indicate that the payload supplied exceeds the size supported by the service. For cases where the payload size is supported but there is insufficient available storage space, the message InsufficientStorage shall be used.

Version Added: v1.13

Severity: Critical

Resolution: Check that the supplied payload is correct and supported by this service.

Message and Arguments: "The supplied payload exceeds the maximum size supported by the service."

2.3.62 PreconditionFailed

Example: The ETag supplied did not match the ETag required to change this resource.

Indicates that the ETag supplied did not match the current ETag of the resource.

• Indicates that the ETag supplied either in the header or using that @odata.etag annotation in the resource did not match the one expected by the service and so the operation on this resource failed. The use of this message shall only be used in responses for deep operations, since HTTP status code 412 is typically used for this.

Version Added: v1.8

Severity: Critical

Resolution: Try the operation again using the appropriate ETag.

Message and Arguments: "The ETag supplied did not match the ETag required to change this resource."

2.3.63 PreconditionRequired

Example: A precondition header or annotation is required to change this resource.

Indicates that the request did not provide the required precondition such as an If-Match or If-None-Match header or @odata.etag annotations.

• Indicates that the request did not provide the required precondition such as an If-Match or If-None-Match header or @odata.etag annotations. The use of this message shall only be used in responses for deep operations, since HTTP status code 428 is typically used for this.

Version Added: v1.8

Severity: Critical

Resolution: Try the operation again using an If-Match or If-None-Match header and appropriate ETag.

Message and Arguments: "A precondition header or annotation is required to change this resource."

2.3.64 PropertyDeprecated

Example: The deprecated property 'OldProperty' was included in the request body.

Indicates the property is deprecated.

• This message shall indicate that the property is deprecated.

Version Added: v1.10

Severity: Warning

Resolution: Refer to the schema guide for more information.

Message and Arguments: "The deprecated property '<1>' was included in the request body."

1. string: The name of the property.
   • This argument shall contain the name of the property that is deprecated.

2.3.65 PropertyDuplicate

Example: The property 'Name' was duplicated in the request.

Indicates that a duplicate property was included in the request body.

• This message shall indicate that a duplicate property was included in the request body.

Version Added: v1.0

Severity: Warning

Resolution: Remove the duplicate property from the request body and resubmit the request if the operation failed.

Message and Arguments: "The property '<1>' was duplicated in the request."

1. string: The name of the duplicate property.
   • This argument shall contain the name of the duplicate property. The value should follow RFC6901-defined JSON pointer notation rules.

2.3.66 PropertyMissing

Example: The property 'Name' is a required property and must be included in the request.

Indicates that a required property was not supplied as part of the request.

• This message shall indicate that a required property was not supplied as part of the request.

Version Added: v1.0

Severity: Warning

Resolution: Ensure that the property is in the request body and has a valid value and resubmit the request if the operation failed.

Message and Arguments: "The property '<1>' is a required property and must be included in the request."

1. string: The name of the property.
   • This argument shall contain the name of the property. The value should follow RFC6901-defined JSON pointer notation rules.

2.3.67 PropertyModified

Example: One or more properties were successfully modified.

Indicates that all properties listed in RelatedProperties in the message were successfully modified.

• This message shall indicate that the properties listed in RelatedProperties were successfully modified.

Version Added: v1.19

Severity: OK

Resolution: None.

Message and Arguments: "One or more properties were successfully modified."

2.3.68 PropertyNotUpdated

Example: The property 'Status' was not updated due to an internal service error. The service is still operational.

Indicates that a property was not updated due to an internal service error, but the service is still functional.

• This message shall indicate that a property was not updated due to an internal service error, but the service is still functional.

Version Added: v1.12

Severity: Critical

Resolution: Resubmit the request. If the problem persists, check for additional messages and consider resetting the service.

Message and Arguments: "The property '<1>' was not updated due to an internal service error. The service is still operational."

1. string: The name of the property.
   • This argument shall contain the name of the property. The value should follow RFC6901-defined JSON pointer notation rules.

2.3.69 PropertyNotWritable

Example: The property 'Manufacturer' is a read-only property and cannot be assigned a value.

Indicates that a property was given a value in the request body, but the property is a read-only property.

• This message shall indicate that a property was given a value in the request body, but the property is a read-only property.

Version Added: v1.0

Severity: Warning

Resolution: Remove the property from the request body and resubmit the request if the operation failed.

Message and Arguments: "The property '<1>' is a read-only property and cannot be assigned a value."

1. string: The name of the property.
   • This argument shall contain the name of the property. The value should follow RFC6901-defined JSON pointer notation rules.

2.3.70 PropertyUnknown

Example: The property 'InvalidPropertyName' is not in the list of valid properties for the resource.

Indicates that an unknown property was included in the request body.

• This message shall indicate that an unknown property was included in the request body.

Version Added: v1.0

Severity: Warning

Resolution: Remove the unknown property from the request body and resubmit the request if the operation failed.

Message and Arguments: "The property '<1>' is not in the list of valid properties for the resource."

1. string: The name of the unknown property.
   • This argument shall contain the name of the unknown property. The value should follow RFC6901-defined JSON pointer notation rules.

2.3.71 PropertyValueConflict

Example: The property 'BootSourceOverrideTarget' could not be written because its value would conflict with the value of the 'BootSourceOverrideEnabled' property.

Indicates that the requested write of a property value could not be completed because of a conflict with another property value.

• This message shall indicate that the requested write of a property could not be completed because of a conflict with the value of another property.

Version Added: v1.6

Severity: Warning

Resolution: None.

Message and Arguments: "The property '<1>' could not be written because its value would conflict with the value of the '<2>' property."

1. string: The name of the property for which a write was requested.
   • This argument shall contain the name of the property for which a write was requested.
2. string: The name of the property with which there is a conflict.
   • This argument shall contain the name of the property with which there is a conflict.

2.3.72 PropertyValueDeprecated

Example: The value 'OldValue' for the property 'OldProperty' is deprecated.

Indicates that a property was given a deprecated value.

• This message shall indicate that a property was given a deprecated value.

Version Added: v1.10

Severity: Warning

Resolution: Refer to the schema guide for more information.

Message and Arguments: "The value '<1>' for the property <2> is deprecated."

1. string: The value provided for the property.
   • This argument shall contain the deprecated value provided for the property.
2. string: The name of the property.
   • This argument shall contain the name of the property.

2.3.73 PropertyValueError

Example: The value provided for the property 'Status' is not valid.

Indicates that a property was given an invalid value.

• This message shall indicate that a property was given an invalid value, and the value cannot or should not be included in the message text.

Version Added: v1.11

Severity: Warning

Resolution: Correct the value for the property in the request body and resubmit the request if the operation failed.

Message and Arguments: "The value provided for the property '<1>' is not valid."

1. string: The name of the property.
   • This argument shall contain the name of the property. The value should follow RFC6901-defined JSON pointer notation rules.

2.3.74 PropertyValueExternalConflict

Example: The property 'BootSourceOverrideTarget' with the requested value of 'Pxe' could not be written because the value is not available due to a configuration conflict.

Indicates that the requested write of a property value could not be completed due to conflicts with other configurations in the service managed with non-Redfish interfaces.

• This message shall indicate that the requested write of a property could not be completed because the requested value of the property, which is a value supported by the implementation, cannot be accepted due to conflicts with other configurations in the service managed with non-Redfish interfaces.

Version Added: v1.10

Severity: Warning

Resolution: None.

Message and Arguments: "The property '<1>' with the requested value of '<2>' could not be written because the value is not available due to a configuration conflict."

1. string: The name of the property for which a write was requested.
   • This argument shall contain the name of the property for which a write was requested.
2. string: The value of the property that is in conflict.
   • This argument shall contain the value of the property that is in conflict.

2.3.75 PropertyValueFormatError

Example: The value '2024-01-01' for the property 'ManufactureDate' is not a format that the property can accept.

Indicates that a property was given the correct value type but the format of the value is not supported.

• This message shall indicate that a property was given the correct value type but the format of the value is not supported.

Version Added: v1.0

Severity: Warning

Resolution: Correct the value for the property in the request body and resubmit the request if the operation failed.

Message and Arguments: "The value '<1>' for the property <2> is not a format that the property can accept."

1. string: The value provided for the property.
   • This argument shall contain the value provided for the property. Numeric values shall be converted to a string, and null values shall be represented by the string null.
2. string: The name of the property.
   • This argument shall contain the name of the property. The value should follow RFC6901-defined JSON pointer notation rules.

2.3.76 PropertyValueIncorrect

Example: The property 'UserName' with the requested value of 'Admin!' could not be written because the value is not acceptable for the property.

Indicates that the requested write of a property value could not be completed because of an incorrect value of the property. Examples include values that do not match a regular expression requirement, passwords that do not match the implementation constraints, or specifying an invalid URI in a reference property.

• This message shall indicate that the requested write of a property could not be completed because of an incorrect value for the property.

Version Added: v1.7

Severity: Warning

Resolution: None.

Message and Arguments: "The property '<1>' with the requested value of '<2>' could not be written because the value is not acceptable for the property."

1. string: Name of the property for which a write was requested.
   • This argument shall contain the name of the property for which a write was requested.
2. string: Value of the property that is incorrect.
   • This argument shall contain the value of the property that is incorrect.

2.3.77 PropertyValueModified

Example: The property 'Temperature' was assigned the value '20' due to modification by the service.

Indicates that a property was given the correct value type but the value of that property was modified. Examples are truncated or rounded values.

• This message shall indicate that a property was given the correct value type but the value of that property was modified.

Version Added: v1.0

Severity: Warning

Resolution: None.

Message and Arguments: "The property '<1>' was assigned the value '<2>' due to modification by the service."

1. string: The name of the property.
   • This argument shall contain the name of the property.
2. string: The value assigned for property.
   • This argument shall contain the value assigned for property.

2.3.78 PropertyValueNotInList

Example: The value 'InvalidValue' for the property 'Status' is not in the list of acceptable values.

Indicates that a property was given the correct value type but the value of that property was not supported. The value is not in an enumeration.

• This message shall indicate that a property was given the correct value type but the value of that property was not supported.

Version Added: v1.0

Severity: Warning

Resolution: Choose a value from the enumeration list that the implementation can support and resubmit the request if the operation failed.

Message and Arguments: "The value '<1>' for the property <2> is not in the list of acceptable values."

1. string: The value provided for the property.
   • This argument shall contain the value provided for the property.
2. string: The name of the property.
   • This argument shall contain the name of the property. The value should follow RFC6901-defined JSON pointer notation rules.

2.3.79 PropertyValueOutOfRange

Example: The value '-5' for the property 'MemorySizeGB' is not in the supported range of acceptable values.

Indicates that a property was given the correct value type but the value of that property is outside the supported range.

• This value shall indicate that a property was given the correct value type but the value of that property is outside the supported range.

Version Added: v1.3

Severity: Warning

Resolution: Correct the value for the property in the request body and resubmit the request if the operation failed.

Message and Arguments: "The value '<1>' for the property <2> is not in the supported range of acceptable values."

1. string: The value provided for the property.
   • This argument shall contain the value provided for the property.
2. string: The name of the property.
   • This argument shall contain the name of the property. The value should follow RFC6901-defined JSON pointer notation rules.

2.3.80 PropertyValueResourceConflict

Example: The property 'BootSourceOverrideTarget' with the requested value of 'Pxe' could not be written because the value conflicts with the state or configuration of the resource at '/redfish/v1/Systems/1'.

Indicates that the requested write of a property value could not be completed due to the current state or configuration of another resource.

• This message shall indicate that the requested write of a property could not be completed because the requested value of the property, which is a value supported by the implementation, cannot be accepted due to conflicts in the state or configuration of another resource.

Version Added: v1.10

Severity: Warning

Resolution: None.

Message and Arguments: "The property '<1>' with the requested value of '<2>' could not be written because the value conflicts with the state or configuration of the resource at '<3>'."

1. string: The name of the property for which a write was requested.
   • This argument shall contain the name of the property for which a write was requested.
2. string: The value of the property that is in conflict.
   • This argument shall contain the value of the property that is in conflict.
3. string: The URI of the resource in conflict.
   • This argument shall contain the URI of the resource that is in conflict with the value of the requested property.

2.3.81 PropertyValueTypeError

Example: The value '123' for the property 'Manufacturer' is not a type that the property can accept.

Indicates that a property was given the wrong value type, such as when a number is supplied for a property that requires a string.

• This message shall indicate that a property was given the wrong value type.

Version Added: v1.0

Severity: Warning

Resolution: Correct the value for the property in the request body and resubmit the request if the operation failed.

Message and Arguments: "The value '<1>' for the property <2> is not a type that the property can accept."

1. string: The value provided for the property.
   • This argument shall contain the value provided for the property. Numeric values shall be converted to a string, and null values shall be represented by the string null.
2. string: The name of the property.
   • This argument shall contain the name of the property. The value should follow RFC6901-defined JSON pointer notation rules.

2.3.82 QueryCombinationInvalid

Example: Two or more query parameters in the request cannot be used together.

Indicates the request contains multiple query parameters and that two or more of them cannot be used together.

• This message shall indicate that the request contains multiple query parameters and that two or more of them cannot be used together.

Version Added: v1.6

Severity: Warning

Resolution: Remove one or more of the query parameters and resubmit the request if the operation failed.

Message and Arguments: "Two or more query parameters in the request cannot be used together."

2.3.83 QueryNotSupported

Example: Querying is not supported by the implementation.

Indicates that query is not supported on the implementation.

• This message shall indicate that query is not supported on the implementation.

Version Added: v1.0

Severity: Warning

Resolution: Remove the query parameters and resubmit the request if the operation failed.

Message and Arguments: "Querying is not supported by the implementation."

2.3.84 QueryNotSupportedOnOperation

Example: Querying is not supported with the requested operation.

Indicates that query is not supported with the given operation, such as when the $expand query is attempted with a PATCH operation.

• This message shall indicate that query is not supported with the given operation.

Version Added: v1.6

Severity: Warning

Resolution: Remove the query parameters and resubmit the request if the operation failed.

Message and Arguments: "Querying is not supported with the requested operation."

2.3.85 QueryNotSupportedOnResource

Example: Querying is not supported on the requested resource.

Indicates that query is not supported on the given resource, such as when the $skip query is attempted on a resource that is not a collection.

• This message shall indicate that query is not supported on the given resource.

Version Added: v1.0

Severity: Warning

Resolution: Remove the query parameters and resubmit the request if the operation failed.

Message and Arguments: "Querying is not supported on the requested resource."

2.3.86 QueryParameterOutOfRange

Example: The value '1000' for the query parameter '$top' is out of range. The maximum supported value is 100.

Indicates that a query parameter was provided that is out of range for the given resource. This can happen with values that are too low or that exceed what is possible for the supplied resource, such as when a page is requested that is beyond the last page.

• This message shall indicate that a query parameter was provided that is out of range for the given resource.

Version Added: v1.0

Severity: Warning

Resolution: Reduce the value for the query parameter to a value that is within range, such as a start or count value that is within bounds of the number of resources in a collection or a page number that is within the range of valid pages.

Message and Arguments: "The value '<1>' for the query parameter <2> is out of range <3>."

1. string: The value provided for the query parameter.
   • This argument shall contain the value provided for the query parameter.
2. string: The query parameter.
   • This argument shall contain the name of the query parameter.
3. string: The valid range for the query parameter.
   • This argument shall contain a string representation of the valid range of values supported for the query parameter.

2.3.87 QueryParameterUnsupported

Example: Query parameter 'InvalidParameter' is not supported.

Indicates that a query parameter is not supported.

• This message shall indicate that a query parameter is not supported by this service.

Version Added: v1.15

Severity: Warning

Resolution: Correct or remove the query parameter and resubmit the request.

Message and Arguments: "Query parameter '<1>' is not supported."

1. string: The query parameter.
   • This argument shall contain the name of the query parameter.

2.3.88 QueryParameterValueError

Example: The value 'Contoso' for the parameter '$top' is invalid.

Indicates that a query parameter was given an invalid value.

• This message shall indicate that a query parameter was given an invalid value that cannot or should not be included in the message.

Version Added: v1.11

Severity: Warning

Resolution: Correct the value for the query parameter in the request and resubmit the request if the operation failed.

Message and Arguments: "The value for the parameter '<1>' is invalid."

1. string: The query parameter.
   • This argument shall contain the name of the query parameter.

2.3.89 QueryParameterValueFormatError

Example: The value '2024-01-01' for the query parameter '$filter' is not a format that the parameter can accept.

Indicates that a query parameter was given the correct value type but the format of the value is not supported.

• This message shall indicate that a query parameter was given the correct value type but the format of the value is not supported.

Version Added: v1.0

Severity: Warning

Resolution: Correct the value for the query parameter in the request and resubmit the request if the operation failed.

Message and Arguments: "The value '<1>' for the parameter <2> is not a format that the parameter can accept."

1. string: The value provided for the query parameter.
   • This argument shall contain the value provided for the query parameter.
2. string: The query parameter.
   • This argument shall contain the name of the query parameter.

2.3.90 QueryParameterValueTypeError

Example: The value '123' for the query parameter '$filter' is not a type that the parameter can accept.

Indicates that a query parameter was given the wrong value type, such as when a number is supplied for a query parameter that requires a string.

• This message shall indicate that a query parameter was given the wrong value type, such as when a number is supplied for a query parameter that requires a string.

Version Added: v1.0

Severity: Warning

Resolution: Correct the value for the query parameter in the request and resubmit the request if the operation failed.

Message and Arguments: "The value '<1>' for the query parameter <2> is not a type that the parameter can accept."

1. string: The value provided for the query parameter.
   • This argument shall contain the value provided for the query parameter.
2. string: The query parameter.
   • This argument shall contain the name of the query parameter.

2.3.91 ResetRecommended

Example: In order to recover from errors, a component reset is recommended with the Reset action URI '/redfish/v1/Systems/1/Actions/ComputerSystem.Reset' and ResetType 'ForceRestart'.

Indicates that a component reset is recommended for error recovery while unaffected applications can continue running without any effect on accuracy and performance.

• This message shall indicate that a component reset is recommended for error recovery while unaffected applications can continue running without any effect on accuracy and performance.

Version Added: v1.12

Severity: Warning

Resolution: Perform the recommended reset action on the specified component.

Message and Arguments: "In order to recover from errors, a component reset is recommended with the Reset action URI '<1>' and ResetType '<2>'."

1. string: The URI for the reset action of the component that recommends a reset.
   • This argument shall contain the URI for the reset action that is recommended to be invoked for error recovery.
2. string: The ResetType required in a reset action on the component URI.
   • This argument shall contain the ResetType required in a reset action on the component URI for error recovery while unaffected applications can continue running without any effect on accuracy and performance. A reset action POST shall contain this ResetType parameter.

2.3.92 ResetRequired

Example: In order to apply changes, recover from errors, or complete the operation, a component reset is required with the Reset action URI '/redfish/v1/Systems/1/Actions/ComputerSystem.Reset' and ResetType 'ForceRestart'.

Indicates that a component reset is required for changes, error recovery, or operations to complete.

• This message shall indicate that a component reset is required for changes, error recovery, or operations to complete.

Version Added: v1.6

Severity: Warning

Resolution: Perform the required reset action on the specified component.

Message and Arguments: "In order to apply changes, recover from errors, or complete the operation, a component reset is required with the Reset action URI '<1>' and ResetType '<2>'."

1. string: The URI for the reset action of the component that requires a reset.
   • This argument shall contain the URI for the reset action that is required to be invoked for changes, error recovery or operations to complete.
2. string: The ResetType required in a reset action on the component URI.
   • This argument shall contain the ResetType required in a reset action on the component URI for changes, error recovery or operations to complete. A reset action POST shall contain this ResetType parameter.

2.3.93 ResourceAlreadyExists

Example: The requested resource of type 'Drive' with the property 'PredictedMediaLifeLeftThreshold' with the value '20' already exists.

Indicates that a resource change or creation was attempted but that the operation cannot proceed because the resource already exists.

• This message shall indicate that a resource change or creation was attempted but that the operation cannot proceed because the resource already exists.

Version Added: v1.0

Severity: Critical

Resolution: Do not repeat the create operation as the resource was already created.

Message and Arguments: "The requested resource of type '<1>' with the property '<2>' with the value '<3>' already exists."

1. string: The type of resource.
   • This argument shall contain the schema name of the resource.
2. string: The name of the property.
   • This argument shall contain the name of the property.
3. string: The value of the property.
   • This argument shall contain the value provided for the property. Numeric values shall be converted to a string, and null values shall be represented by the string null.

2.3.94 ResourceAtUriInUnknownFormat

Example: The resource at '/redfish/v1/UpdateService/FirmwareInventory/1/Actions/FirmwareInventory.UpdateImage' is in a format not recognized by the service.

Indicates that the URI was valid but the resource or image at that URI was in a format not supported by the service.

• This message shall indicate that the URI was valid but the resource or image at that URI was in a format not supported by the service.

Version Added: v1.0

Severity: Critical

Resolution: Place an image or resource or file that is recognized by the service at the URI.

Message and Arguments: "The resource at '<1>' is in a format not recognized by the service."

1. string: The URI provided.
   • This argument shall contain the URI provided for this operation.

2.3.95 ResourceAtUriUnauthorized

Example: While accessing the resource at '/redfish/v1/UpdateService/FirmwareInventory/1/Actions/FirmwareInventory.UpdateImage', the service received an authorization error 'Unauthorized'.

Indicates that the attempt to access the resource, file, or image at the URI was unauthorized.

• This message shall indicate that the attempt to access the resource, file, or image at the URI was unauthorized.

Version Added: v1.0

Severity: Critical

Resolution: Ensure that the appropriate access is provided for the service in order for it to access the URI.

Message and Arguments: "While accessing the resource at '<1>', the service received an authorization error '<2>'."

1. string: The URI provided.
   • This argument shall contain the URI provided for this operation.
2. string: The error message received from the authorization service.
   • This argument shall contain the error message received from the authorization service or software.

2.3.96 ResourceCannotBeDeleted

Example: The delete request failed because the resource requested cannot be deleted.

Indicates that a delete operation was attempted on a resource that cannot be deleted.

• This message shall indicate that a delete operation was attempted on a resource that cannot be deleted.

Version Added: v1.0

Severity: Critical

Resolution: Do not attempt to delete a non-deletable resource.

Message and Arguments: "The delete request failed because the resource requested cannot be deleted."

2.3.97 ResourceCreationConflict

Example: The resource could not be created. The service has a resource at URI '/redfish/v1/Systems/1' that conflicts with the creation request.

Indicates that the requested resource creation could not be completed because the service has a resource that conflicts with the request.

• This message shall indicate that the requested creation of a resource could not be completed because the service has a resource that conflicts with the request, such as when the resource already exists or an existing resource has similar property values.

Version Added: v1.7

Severity: Warning

Resolution: None.

Message and Arguments: "The resource could not be created. The service has a resource at URI '<1>' that conflicts with the creation request."

1. string: URI of the resource that conflicts with the creation request.
   • This argument shall contain the URI of the resource with which there is a conflict.

2.3.98 ResourceDeprecated

Example: The operation was performed on a deprecated resource '/redfish/v1/OldResource'.

Indicates the resource is deprecated.

• This message shall indicate that the resource is deprecated.

Version Added: v1.10

Severity: Warning

Resolution: Refer to the schema guide for more information.

Message and Arguments: "The operation was performed on a deprecated resource '<1>'."

1. string: The URI of the resource.
   • This argument shall contain the URI of the resource that is deprecated.

2.3.99 ResourceExhaustion

Example: The resource at '/redfish/v1/UpdateService/FirmwareInventory/1' was unable to satisfy the request due to unavailability of resources.

Indicates that a resource could not satisfy the request due to some unavailability of resources. An example is that available capacity was allocated.

• This message shall indicate that a resource could not satisfy the request due to some unavailability of resources.

Version Added: v1.2

Severity: Critical

Resolution: Ensure that the resources are available and resubmit the request.

Message and Arguments: "The resource '<1>' was unable to satisfy the request due to unavailability of resources."

1. string: The URI of the resource.
   • This argument shall contain the URI of the relevant resource.

2.3.100 ResourceInStandby

Example: The request could not be performed because the resource is in standby.

Indicates that the request could not be performed because the resource is in standby.

• This message shall indicate that the request could not be performed because the resource is in standby.

Version Added: v1.1

Severity: Critical

Resolution: Ensure that the resource is in the correct power state and resubmit the request.

Message and Arguments: "The request could not be performed because the resource is in standby."

2.3.101 ResourceInUse

Example: The change to the requested resource failed because the resource is in use or in transition.

Indicates that a change was requested to a resource but the change was rejected due to the resource being in use or transition.

• This message shall indicate that a change was requested to a resource but the change was rejected due to the resource being in use or transition.

Version Added: v1.0

Severity: Warning

Resolution: Remove the condition and resubmit the request if the operation failed.

Message and Arguments: "The change to the requested resource failed because the resource is in use or in transition."

2.3.102 ResourceMissingAtURI

Example: The resource at the URI '/redfish/v1/UpdateService/FirmwareInventory/1/Actions/FirmwareInventory.UpdateImage' was not found.

Indicates that the operation expected an image or other resource at the provided URI but none was found. Examples of this are in requests that require URIs such as firmware updates.

• This message shall indicate that the operation expected an image or other resource at the provided URI but none was found.

Version Added: v1.0

Severity: Critical

Resolution: Place a valid resource at the URI or correct the URI and resubmit the request.

Message and Arguments: "The resource at the URI '<1>' was not found."

1. string: The URI provided.
   • This argument shall contain the URI provided for this operation.

2.3.103 ResourceNotFound

Example: The requested resource of type 'Drive' named 'Drive1' was not found.

Indicates that the operation expected a resource identifier that corresponds to an existing resource but one was not found.

• This message shall indicate that the operation expected a resource identifier that corresponds to an existing resource but one was not found.

Version Added: v1.2

Severity: Critical

Resolution: Provide a valid resource identifier and resubmit the request.

Message and Arguments: "The requested resource of type '<1>' named '<2>' was not found."

1. string: The type of resource.
   • This argument shall contain the schema name of the resource.
2. string: The Id of the resource.
   • This argument shall contain the value of the Id property of the requested resource.

2.3.104 ResourceTypeIncompatible

Example: The @odata.type of the request body '#ManagerAccount.v1_3_0.ManagerAccount' is incompatible with the @odata.type of the resource, which is '#ManagerAccount.v1_2_0.ManagerAccount'.

Indicates that the resource type of the operation does not match that of the operation destination. Examples of this are a POST to a resource collection using the wrong resource type, an update where the @odata.type properties do not match, or a case of major version incompatibility.

• This message shall indicate that the resource type of the operation does not match that of the operation destination.

Version Added: v1.2

Severity: Critical

Resolution: Resubmit the request with a payload compatible with the resource's schema.

Message and Arguments: "The @odata.type of the request body '<1>' is incompatible with the @odata.type of the resource, which is '<2>'."

1. string: The @odata.type of the request.
   • This argument shall contain the value of the @odata.type property provided in the request.
2. string: The supported @odata.type value.
   • This argument shall contain the value of the @odata.type property supported by the resource.

2.3.105 RestrictedPrivilege

Example: The operation was not successful because the privilege 'Login' is restricted.

Indicates that the operation was not successful because a privilege is restricted.

• This message shall indicate that the operation was not successful because a privilege is restricted.

Version Added: v1.9

Severity: Warning

Resolution: Remove restricted privileges from the request body and resubmit the request.

Message and Arguments: "The operation was not successful because the privilege '<1>' is restricted."

1. string: The name of the restricted privilege.
   • This argument shall contain the name of the restricted privilege.

2.3.106 RestrictedRole

Example: The operation was not successful because the role 'ReadOnly' is restricted.

Indicates that the operation was not successful because the role is restricted.

• This message shall indicate that the operation was not successful because the role is restricted.

Version Added: v1.9

Severity: Warning

Resolution: No resolution is required. For standard roles, consider using the role specified in the AlternateRoleId property in the Role resource.

Message and Arguments: "The operation was not successful because the role '<1>' is restricted."

1. string: The name of the restricted role.
   • This argument shall contain the name of the restricted role.

2.3.107 ServiceDisabled

Example: The operation failed because the service at '/redfish/v1/AccountService' is disabled and cannot accept requests.

Indicates that the operation failed because the service, such as the account service, is disabled and cannot accept requests.

• This message shall indicate that the operation failed because the service, such as the account service, is disabled and cannot accept requests.

Version Added: v1.11

Severity: Warning

Resolution: Enable the service and resubmit the request if the operation failed.

Message and Arguments: "The operation failed because the service at '<1>' is disabled and cannot accept requests."

1. string: The URI of the disabled service.
   • This argument shall contain the URI of the disabled service.

2.3.108 ServiceInUnknownState

Example: The operation failed because the service is in an unknown state and can no longer take incoming requests.

Indicates that the operation failed because the service is in an unknown state and cannot accept additional requests.

• This message shall indicate that the operation failed because the service is in an unknown state and cannot accept additional requests.

Version Added: v1.0

Severity: Critical

Resolution: Restart the service and resubmit the request if the operation failed.

Message and Arguments: "The operation failed because the service is in an unknown state and can no longer take incoming requests."

2.3.109 ServiceShuttingDown

Example: The operation failed because the service is shutting down and can no longer take incoming requests.

Indicates that the operation failed because the service is shutting down, such as when the service reboots.

• This message shall indicate that the operation failed because the service is shutting down.

Version Added: v1.0

Severity: Critical

Resolution: When the service becomes available, resubmit the request if the operation failed.

Message and Arguments: "The operation failed because the service is shutting down and can no longer take incoming requests."

2.3.110 ServiceTemporarilyUnavailable

Example: The service is temporarily unavailable. Retry in 30 seconds.

Indicates the service is temporarily unavailable.

• This message shall indicate that the service is temporarily unavailable.

Version Added: v1.0

Severity: Critical

Resolution: Wait for the indicated retry duration and retry the operation.

Message and Arguments: "The service is temporarily unavailable. Retry in <1> seconds."

1. string: The retry duration in seconds.
   • This argument shall contain the number of seconds the client should wait before attempting the operation again.

2.3.111 SessionLimitExceeded

Example: The session establishment failed due to the number of simultaneous sessions exceeding the limit of the implementation.

Indicates that a session establishment was requested but the operation failed due to the number of simultaneous sessions exceeding the limit of the implementation.

• This message shall indicate that a session establishment was requested but the operation failed due to the number of simultaneous sessions exceeding the limit of the implementation.

Version Added: v1.0

Severity: Critical

Resolution: Reduce the number of other sessions before trying to establish the session or increase the limit of simultaneous sessions, if supported.

Message and Arguments: "The session establishment failed due to the number of simultaneous sessions exceeding the limit of the implementation."

2.3.112 SessionTerminated

Example: The session was successfully terminated.

Indicates that the DELETE operation on the session resource resulted in the successful termination of the session.

• This message shall indicate that the DELETE operation on the session resource resulted in the successful termination of the session.

Version Added: v1.3

Severity: OK

Resolution: None.

Message and Arguments: "The session was successfully terminated."

2.3.113 SourceDoesNotSupportProtocol

Example: The other end of the connection at '/redfish/v1/UpdateService/FirmwareInventory/1/Actions/FirmwareInventory.UpdateImage' does not support the specified protocol 'HTTPS'.

Indicates that while attempting to access, connect to, or transfer a resource, file, or image from another location that the other end of the connection did not support the protocol.

• This message shall indicate that while attempting to access, connect to, or transfer a resource, file, or image from another location that the other end of the connection did not support the protocol.

Version Added: v1.0

Severity: Critical

Resolution: Change protocols or URIs.

Message and Arguments: "The other end of the connection at '<1>' does not support the specified protocol <2>."

1. string: The URI provided.
   • This argument shall contain the URI provided for this operation.
2. string: The protocol specified.
   • This argument shall contain the name of the protocol requested for this operation.

2.3.114 StrictAccountTypes

Example: The request could not be fulfilled with the account types included in property 'AccountTypes' because the property StrictAccountTypes is set to true.

Indicates the request failed because a set of AccountTypes or OEMAccountTypes was not accepted while StrictAccountTypes is set to true.

• This message shall indicate that the request failed because a set of AccountTypes or OEMAccountTypes was not accepted while StrictAccountTypes is set to true.

Version Added: v1.9

Severity: Warning

Resolution: Resubmit the request either with an acceptable set of AccountTypes and OEMAccountTypes or with StrictAccountTypes set to false.

Message and Arguments: "The request could not be fulfilled with the account types included in property '<1>' because the property StrictAccountTypes is set to true."

1. string: The name of the property.
   • This argument shall contain the name of the property AccountTypes or OEMAccountTypes.

2.3.115 StringValueTooLong

Example: The string 'This is a very long string' exceeds the length limit 10.

Indicates that a string value passed to the given resource was longer than the maximum allowed length. An example is when an implementation has imposed a shorter maximum length than that allowed by the specification.

• This message shall indicate that a string value passed to the given resource was longer than the maximum allowed length.

Version Added: v1.2

Severity: Warning

Resolution: Resubmit the request with an appropriate string length.

Message and Arguments: "The string '<1>' exceeds the length limit <2>."

1. string: The string provided.
   • This argument shall contain the string value provided for this operation.
2. number: The maximum string length.
   • This argument shall contain the maximum supported string length for this property.

2.3.116 StringValueTooShort

Example: The string 'Too short' was under the minimum required length 16.

Indicates that a string value passed to the given resource was shorter than the minimum required length. An example is when an implementation has imposed a greater minimum length than that required by the specification. This message also applies to cases of empty strings where the minimum string length is 1.

• This message shall indicate that a string value passed to the given resource was shorter than the minimum required length.

Version Added: v1.16

Severity: Warning

Resolution: Resubmit the request with an appropriate string length.

Message and Arguments: "The string '<1>' was under the minimum required length <2>."

1. string: The string provided.
   • This argument shall contain the string value provided for this operation.
2. number: The minimum string length.
   • This argument shall contain the minimum supported string length for this property.

2.3.117 SubscriptionTerminated

Example: The event subscription was terminated.

An event subscription was terminated by the service. No further events will be delivered.

• This message shall indicate that an event subscription was terminated by the service.

Version Added: v1.5

Severity: OK

Resolution: None.

Message and Arguments: "The event subscription was terminated."

2.3.118 Success

Example: The request completed successfully.

Indicates that all conditions of a successful operation were met.

• This message shall indicate that all conditions of a successful operation were met.

Version Added: v1.0

Severity: OK

Resolution: None.

Message and Arguments: "The request completed successfully."

2.3.119 UndeterminedFault

Example: An undetermined fault condition was reported by 'Service1'.

Indicates that a fault or error condition exists but the source of the fault cannot be determined or is unknown to the service.

• This message shall indicate that a fault or error condition was reported to the service, but the source of the fault cannot be determined or is unknown to the service.

Version Added: v1.9

Severity: Critical

Resolution: None.

Message and Arguments: "An undetermined fault condition was reported by '<1>'."

1. string: The software, provider, or service that reported the fault condition.
   • This argument shall contain the name of the entity that reported the fault condition.

2.3.120 UnrecognizedRequestBody

Example: The service detected a malformed request body that it was unable to interpret.

Indicates that the service encountered an unrecognizable request body that could not even be interpreted as malformed JSON.

• This message shall indicate that the service encountered an unrecognizable request body that could not even be interpreted as malformed JSON.

Version Added: v1.0

Severity: Warning

Resolution: Correct the request body and resubmit the request if it failed.

Message and Arguments: "The service detected a malformed request body that it was unable to interpret."

2.4 Composition 1.2.0

This registry defines the messages for composition related events.

2.4.1 ConstrainedResourceAlreadyReserved

Example: The requested resources are reserved under reservation 'Reservation1'.

Indicates that the requested resources are already reserved in response to a constrained composition request.

• This message shall indicate that the requested resources are already reserved in response to a constrained composition request.

Version Added: v1.1

Severity: Critical

Resolution: Delete the reservation containing the resources and resubmit the request.

Message and Arguments: "The requested resources are reserved under reservation '<1>'."

1. string: The Id of the reservation.
   • This argument shall contain the value of the Id property of the CompositionReservation resource containing the requested resources.

2.4.2 EmptyManifest

Example: The provided manifest is empty or a stanza in the manifest contains no request.

Indicates that the manifest contains no stanzas or that a stanza in the manifest contains no request.

• This message shall indicate that the manifest contains no stanzas or that a stanza in the manifest contains no request.

Version Added: v1.1

Severity: Warning

Resolution: Provide a request content for the manifest and resubmit.

Message and Arguments: "The provided manifest is empty or a stanza in the manifest contains no request."

2.4.3 IncompatibleZone

Example: The requested resource blocks span multiple resource zones.

Indicates that not all referenced resource blocks are in the same resource zone.

• This message shall indicate that not all referenced ResourceBlock resources are in the same resource zone.

Version Added: v1.1

Severity: Critical

Resolution: Request resource blocks from the same resource zone.

Message and Arguments: "The requested resource blocks span multiple resource zones."

2.4.4 NoResourceMatch

Example: The requested resources of type 'Processor' are not available for allocation.

Indicates that the service could not find a matching resource based on the given parameters.

• This message shall indicate that the service could not find a matching resource based on the given parameters.

Version Added: v1.1

Severity: Critical

Resolution: Change parameters associated with the resource, such as quantity or performance, and resubmit the request.

Message and Arguments: "The requested resources of type '<1>' are not available for allocation."

1. string: The resource type requested.
   • This argument shall contain the schema name of the requested resource.

2.4.5 ResourceBlockChanged

Example: Resource block 'Block1' has changed on the service.

Indicates that a resource block has changed. This is not used whenever there is another event message for that specific change, such as when only the state has changed.

• This message shall indicate that one or more properties of a ResourceBlock resource have changed. This message shall not be used for cases where a more specific message could be used in its place.

Version Added: v1.0

Severity: OK

Resolution: None.

Message and Arguments: "Resource block '<1>' has changed on the service."

1. string: The Id of the resource block that has changed.
   • This argument shall contain the value of the Id property of the ResourceBlock resource that has changed.

2.4.6 ResourceBlockCompositionStateChanged

Example: The composition status of the resource block 'Block1' has changed.

Indicates that the composition state of a resource block has changed, specifically the value of the CompositionState property within CompositionStatus.

• This message shall indicate that the CompositionState property within the CompositionStatus object of a ResourceBlock resource has changed.

Version Added: v1.0

Severity: OK

Resolution: None.

Message and Arguments: "The composition status of the resource block '<1>' has changed."

1. string: The Id of the resource block that has changed.
   • This argument shall contain the value of the Id property of the ResourceBlock resource that has changed.

2.4.7 ResourceBlockInUse

Example: Resource block 'Block1' cannot be part of any new compositions.

Indicates that the composition request contains a resource block that is unable to participate in more compositions.

• This message shall indicate that the composition request contains a ResourceBlock resource that is unable to participate in more compositions due to restrictions specified in its CompositionStatus property. For example, the resource block has reached its composition limit specified by the MaxCompositions property.

Version Added: v1.0

Severity: Warning

Resolution: Remove the resource block from the request and resubmit the request.

Message and Arguments: "Resource block '<1>' cannot be part of any new compositions."

1. string: The Id of the resource block that cannot be part of any new compositions.
   • This argument shall contain the value of the Id property of the ResourceBlock resource that cannot be part of any new compositions.

2.4.8 ResourceBlockInvalid

Example: Resource block 'Block1' is not valid.

Indicates that the Id of a referenced resource block is no longer valid.

• This message shall indicate that the Id of a referenced ResourceBlock resource is no longer valid.

Version Added: v1.1

Severity: Critical

Resolution: Remove the resource block and resubmit the request.

Message and Arguments: "Resource block '<1>' is not valid."

1. string: The Id of the resource block.
   • This argument shall contain the value of the Id property of the ResourceBlock resource that is no longer valid.

2.4.9 ResourceBlockNotFound

Example: Resource block 'Block1' was not found.

Indicates that the referenced resource block was not found.

• This message shall indicate that the referenced ResourceBlock resource was not found.

Version Added: v1.1

Severity: Critical

Resolution: Remove the resource block and resubmit the request.

Message and Arguments: "Resource block '<1>' was not found."

1. string: The URI of the resource block.
   • This argument shall contain the value of the URI of the ResourceBlock resource that was not found.

2.4.10 ResourceBlockStateChanged

Example: The state of resource block 'Block1' has changed.

Indicates that the state of a resource block has changed, specifically the value of the State property within Status.

• This message shall indicate that the State property within the Status object of a ResourceBlock resource has changed.

Version Added: v1.0

Severity: OK

Resolution: None.

Message and Arguments: "The state of resource block '<1>' has changed."

1. string: The Id of the resource block that has changed.
   • This argument shall contain the value of the Id property of the ResourceBlock resource that has changed.

2.4.11 ResourceZoneMembershipChanged

Example: The membership of resource zone 'Zone1' has been changed.

Indicates that the membership of a resource zone has changed due to resource blocks being added or removed from the resource zone.

• This message shall indicate that entries found in the ResourceBlocks array within the Links object for a resource zone have been added or removed.

Version Added: v1.0

Severity: OK

Resolution: None.

Message and Arguments: "The membership of resource zone '<1>' has been changed."

1. string: The Id of the resource zone that has changed.
   • This argument shall contain the value of the Id property of the Zone resource that represents the resource zone that has changed.

2.4.12 SpecifiedResourceAlreadyReserved

Example: Resource block 'Block1' is already reserved under reservation 'Reservation1'.

Indicates that a resource block is already reserved in response to a specific composition request.

• This message shall indicate that a ResourceBlock resource is already reserved in response to a specific composition request.

Version Added: v1.1

Severity: Critical

Resolution: Delete the reservation containing the resource block or select a different resource block and resubmit the request.

Message and Arguments: "Resource block '<1>' is already reserved under reservation '<2>'."

1. string: The Id of the resource block.
   • This argument shall contain the value of the Id property of the ResourceBlock resource that is already reserved.
2. string: The Id of the reservation.
   • This argument shall contain the value of the Id property of the CompositionReservation resource containing the requested resource.

2.4.13 UnableToProcessStanzaRequest

Example: The provided manifest for the Compose action of type 'Simple' contains a stanza with Id of value 'Stanza1' with a Content parameter that could not be processed.

Indicates that the manifest provided for the Compose action contains a stanza with Content that could not be processed.

• This message shall indicate that the manifest provided for the Compose action contains a stanza with Content that could not be processed.

Version Added: v1.1

Severity: Critical

Resolution: Add the Content parameter to the stanza or remove the stanza, and resubmit the request.

Message and Arguments: "The provided manifest for the Compose action of type '<1>' contains a stanza with Id of value '<2>' with a Content parameter that could not be processed."

1. string: The RequestType of the Compose action.
   • This argument shall contain the value of the RequestType parameter of the Compose action.
2. string: The Id of the stanza.
   • This argument shall contain the value of the Id parameter of the stanza.

2.5 Environmental 1.5.0

This registry defines messages related to environmental sensors, heating and cooling equipment, or other environmental conditions.

2.5.1 CoolantConnectionPairReversed

Example: Coolant connector pair 'Secondary' connections are reversed.

Indicates that a supply and return pair of coolant connections are reversed.

• This message shall indicate that a supply and return coolant connection pair, represented by a CoolantConnector resource with a CoolantConnectorType valve of Pair, are reversed. Services may detect this condition by a negative delta temperature, negative flow rate, or other means.

Version Added: v1.5

Severity: Critical

Resolution: Correct the reversed supply and return coolant connections.

Message and Arguments: "Coolant connector pair '<1>' connections are reversed."

1. string: The name or identifier of the coolant connector pair.
   • This argument shall contain a string that identifies or describes the location or physical context of the coolant connector pair.

2.5.2 CoolantConnectionsCorrected

Example: Coolant connections 'Secondary' have been corrected.

Indicates that reversed coolant connections were corrected.

• This message shall indicate that a set of supply and return coolant connections, previously detected as connected in reverse, were corrected.

Version Added: v1.5

Severity: OK

Resolution: None.

Message and Arguments: "Coolant connections '<1>' were corrected."

1. string: The name or identifier of the coolant connectors.
   • This argument shall contain a string that identifies or describes the location or physical context of the affected coolant connections.

2.5.3 CoolantConnectionsReversed

Example: Coolant supply 'Secondary Supply' and return 'Secondary Return' connections are reversed.

Indicates that a supply and a return coolant connections are reversed.

• This message shall indicate that a set of supply and return coolant connections, represented by two or more CoolantConnector resources with CoolantConnectorType values of Supply, Return, SupplyGroupMember or ReturnGroupMember are reversed. Services may detect this condition by a negative delta temperature, negative flow rate, or other means. If both the supply and return CoolantConnector resources can be identified, the OriginOfCondition shall contain a link to the supply connector.

Version Added: v1.5

Severity: Critical

Resolution: Correct the reversed supply and return coolant connections.

Message and Arguments: "Coolant supply '<1>' and return '<2>' connections are reversed."

1. string: The name or identifier of the supply coolant connector.
   • This argument shall contain a string that identifies or describes the location or physical context of the supply coolant connector.
2. string: The name or identifier of the return coolant connector.
   • This argument shall contain a string that identifies or describes the location or physical context of the return coolant connector.

2.5.4 CoolingUnitGroupCritical

Example: Cooling unit group 'Row7' is in a critical state.

Indicates that a cooling unit group has a critical status.

• This message shall indicate that a cooling unit group is operating in a critical state due to a fault or a change in configuration.

Version Added: v1.4

Severity: Critical

Resolution: None.

Message and Arguments: "Cooling unit group '<1>' is in a critical state."

1. string: The name or identifier of the cooling unit group.
   • This argument shall contain a string that identifies or describes the group of CoolingUnit resources.

Note: This message is a more specific version of the following messages: ResourceEvent.ResourceStatusChangedCritical

2.5.5 CoolingUnitGroupNormal

Example: Cooling unit group 'Row7' is operating normally.

Indicates that a cooling unit group has returned to normal operations.

• This message shall indicate that a cooling unit group has returned to a normal operating state.

Version Added: v1.4

Severity: OK

Resolution: None.

Message and Arguments: "Cooling unit group '<1>' is operating normally."

1. string: The name or identifier of the cooling unit group.
   • This argument shall contain a string that identifies or describes the group of CoolingUnit resources.

Note: This message is a more specific version of the following messages: ResourceEvent.ResourceStatusChangedOK

2.5.6 CoolingUnitGroupWarning

Example: Cooling unit group 'Row7' is in a warning state.

Indicates that a cooling unit group has a warning status.

• This message shall indicate that a cooling unit group is operating with a warning status or in a non-redundant state due to a fault or a change in configuration.

Version Added: v1.4

Severity: Warning

Resolution: None.

Message and Arguments: "Cooling unit group '<1>' is in a warning state."

1. string: The name or identifier of the cooling unit group.
   • This argument shall contain a string that identifies or describes the group of CoolingUnit resources.

Note: This message is a more specific version of the following messages: ResourceEvent.ResourceStatusChangedWarning

2.5.7 DewPointProximityCaution

Example: Dew point proximity of coolant connector 'Secondary' temperature of 1.7 degrees (C) is below the 2.0 degree caution threshold.

Indicates that a temperature reading is below the lower caution dew point proximity threshold.

• This message shall indicate that a temperature reading violates a lower caution threshold for proximity to the dew point. If the reading originates from a Sensor resource, the message shall indicate that the value of the Reading property is below the value of the Reading property within the LowerCaution or LowerCautionUser properties.

Version Added: v1.5

Severity: Warning

Resolution: Check the condition of the resource listed in OriginOfCondition.

Message and Arguments: "Dew point proximity of <1> '<2>' temperature of <3> degrees (C) is below the <4> degree caution threshold."

1. string: The resource type or description of the resource.
   • This argument shall contain a string that identifies or describes the resource type of the temperature reading.
2. string: The name or identifier of the resource.
   • This argument shall contain a string that identifies or describes the location or physical context of the temperature reading.
3. number: The temperature in degrees Celsius.
   • This argument shall contain the temperature in degrees Celsius.
4. number: The dew point proximity caution threshold in degrees Celsius.
   • This argument shall contain the dew point proximity caution threshold in degrees Celsius.

Note: This message is a more specific version of the following messages: SensorEvent.ReadingBelowLowerCautionThreshold

2.5.8 DewPointProximityCritical

Example: Dew point proximity of coolant connector 'Secondary' temperature of 0.5 degrees (C) is below the 1.0 degrees critical threshold.

Indicates that a temperature reading is below the lower critical dew point proximity threshold.

• This message shall indicate that a temperature reading violates a lower critical threshold for proximity to the dew point. If the reading originates from a Sensor resource, the message shall indicate that the value of the Reading property is below the value of the Reading property within the LowerCritical or LowerCriticalUser properties.

Version Added: v1.5

Severity: Critical

Resolution: Check the condition of the resource listed in OriginOfCondition.

Message and Arguments: "Dew point proximity of <1> '<2>' temperature of <3> degrees (C) is below the <4> degrees critical threshold."

1. string: The resource type or description of the resource.
   • This argument shall contain a string that identifies or describes the resource type of the temperature reading.
2. string: The name or identifier of the resource.
   • This argument shall contain a string that identifies or describes the location or physical context of the temperature reading.
3. number: The temperature in degrees Celsius.
   • This argument shall contain the temperature in degrees Celsius.
4. number: The dew point proximity critical threshold in degrees Celsius.
   • This argument shall contain the dew point proximity critical threshold in degrees Celsius.

Note: This message is a more specific version of the following messages: SensorEvent.ReadingBelowLowerCriticalThreshold

2.5.9 DewPointProximityNoLongerCritical

Example: Dew point proximity of coolant connector 'Secondary' temperature of 1.8 degrees (C) no longer exceeds the critical level.

Indicates that a temperature reading is no longer below the critical dew point proximity threshold, but remains below the caution threshold.

• This message shall indicate that a temperature reading no longer violates the critical threshold for proximity to the dew point, but continues to violate the caution threshold. If the reading originates from a Sensor resource, the message shall indicate that the value of the Reading property is below the value of the Reading property within the LowerCaution or LowerCautionUser properties, but above the value of the LowerCritical and LowerCriticalUser properties.

Version Added: v1.5

Severity: OK

Resolution: None.

Message and Arguments: "Dew point proximity of <1> '<2>' temperature of <3> degrees (C) no longer exceeds the critical level."

1. string: The resource type or description of the resource.
   • This argument shall contain a string that identifies or describes the resource type of the temperature reading.
2. number: The name or identifier of the resource.
   • This argument shall contain a string that identifies or describes the location or physical context of the temperature reading.
3. number: The temperature in degrees Celsius.
   • This argument shall contain the temperature in degrees Celsius.

Note: This message is a more specific version of the following messages: SensorEvent.ReadingNoLongerCritical

2.5.10 DewPointProximityNormal

Example: Dew point proximity of coolant connector 'Secondary' temperature of 4.0 degrees (C) is normal.

Indicates that a dew point proximity temperature reading is now within normal operating range.

• This message shall indicate that a dew point proximity temperature reading has returned to its normal operating range.

Version Added: v1.5

Severity: OK

Resolution: None.

Message and Arguments: "Dew point proximity of <1> '<2>' temperature of <3> degrees (C) is normal."

1. string: The resource type or description of the resource.
   • This argument shall contain a string that identifies or describes the resource type of the temperature reading.
2. number: The name or identifier of the resource.
   • This argument shall contain a string that identifies or describes the location or physical context of the temperature reading.
3. number: The temperature in degrees Celsius.
   • This argument shall contain the temperature in degrees Celsius.

Note: This message is a more specific version of the following messages: SensorEvent.SensorReadingNormalRange

2.5.11 FanFailed

Example: Fan 'B3' has failed.

Indicates that a fan has failed.

• This message shall indicate that a fan has failed.

Version Added: v1.0

Severity: Critical

Resolution: Check the fan hardware and replace any faulty component.

Message and Arguments: "Fan '<1>' has failed."

1. string: The name or identifier of the fan.
   • This argument shall contain a string that identifies or describes the Fan resource.

Note: This message is a more specific version of the following messages: ResourceEvent.ResourceStatusChangedCritical

2.5.12 FanGroupCritical

Example: Fan group 'CPUs+GPUs' is in a critical state.

Indicates that a fan group has a critical status.

• This message shall indicate that a fan group is operating in a critical state due to a fault or a change in configuration.

Version Added: v1.0

Severity: Critical

Resolution: None.

Message and Arguments: "Fan group '<1>' is in a critical state."

1. string: The name or identifier of the fan group.
   • This argument shall contain a string that identifies or describes the group of Fan resources.

Note: This message is a more specific version of the following messages: ResourceEvent.ResourceStatusChangedCritical

2.5.13 FanGroupNormal

Example: Fan group 'CPUs+GPUs' is operating normally.

Indicates that a fan group has returned to normal operations.

• This message shall indicate that a fan group has returned to a normal operating state.

Version Added: v1.0

Severity: OK

Resolution: None.

Message and Arguments: "Fan group '<1>' is operating normally."

1. string: The name or identifier of the fan group.
   • This argument shall contain a string that identifies or describes the group of Fan resources.

Note: This message is a more specific version of the following messages: ResourceEvent.ResourceStatusChangedOK

2.5.14 FanGroupWarning

Example: Fan group 'CPUs+GPUs' is in a warning state.

Indicates that a fan group has a warning status.

• This message shall indicate that a fan group is operating with a warning status or in a non-redundant state due to a fault or a change in configuration.

Version Added: v1.0

Severity: Warning

Resolution: None.

Message and Arguments: "Fan group '<1>' is in a warning state."

1. string: The name or identifier of the fan group.
   • This argument shall contain a string that identifies or describes the group of Fan resources.

Note: This message is a more specific version of the following messages: ResourceEvent.ResourceStatusChangedWarning

2.5.15 FanInserted

Example: Fan 'B4' was inserted.

Indicates that a fan was inserted or installed.

• This message shall indicate that a fan was inserted or installed.

Version Added: v1.0

Severity: OK

Resolution: None.

Message and Arguments: "Fan '<1>' was inserted."

1. string: The name or identifier of the fan.
   • This argument shall contain a string that identifies or describes the Fan resource.

Note: This message is a more specific version of the following messages: ResourceEvent.ResourceStateChanged

2.5.16 FanRemoved

Example: Fan 'B4' was removed.

Indicates that a fan was removed.

• This message shall indicate that a fan was removed.

Version Added: v1.0

Severity: OK

Resolution: None.

Message and Arguments: "Fan '<1>' was removed."

1. string: The name or identifier of the fan.
   • This argument shall contain a string that identifies or describes the Fan resource.

Note: This message is a more specific version of the following messages: ResourceEvent.ResourceStateChanged

2.5.17 FanRestored

Example: Fan 'B4' was restored.

Indicates that a fan was repaired or restored to normal operation.

• This message shall indicate that a fan was repaired, replaced, or otherwise returned to normal operation.

Version Added: v1.0

Severity: OK

Resolution: None.

Message and Arguments: "Fan '<1>' was restored."

1. string: The name or identifier of the fan.
   • This argument shall contain a string that identifies or describes the Fan resource.

Note: This message is a more specific version of the following messages: ResourceEvent.ResourceStatusChangedOK

2.5.18 FanWarning

Example: Fan 'B3' has a warning condition.

Indicates that a fan has a warning condition.

• This message shall indicate that a fan has a warning condition but continues to operate, potentially in a degraded state.

Version Added: v1.4

Severity: Warning

Resolution: Check the fan hardware and replace any faulty component.

Message and Arguments: "Fan '<1>' has a warning condition."

1. string: The name or identifier of the fan.
   • This argument shall contain a string that identifies or describes the Fan resource.

Note: This message is a more specific version of the following messages: ResourceEvent.ResourceStatusChangedWarning

2.5.19 FilterInserted

Example: Filter 'Secondary' was inserted.

Indicates that a filter was inserted or installed.

• This message shall indicate that a filter was inserted or installed.

Version Added: v1.1

Severity: OK

Resolution: None.

Message and Arguments: "Filter '<1>' was inserted."

1. string: The name or identifier of the filter.
   • This argument shall contain a string that identifies or describes the Filter resource.

Note: This message is a more specific version of the following messages: ResourceEvent.ResourceStateChanged

2.5.20 FilterRemoved

Example: Filter 'Secondary' was removed.

Indicates that a filter was removed.

• This message shall indicate that a filter was removed.

Version Added: v1.1

Severity: OK

Resolution: None.

Message and Arguments: "Filter '<1>' was removed."

1. string: The name or identifier of the filter.
   • This argument shall contain a string that identifies or describes the Filter resource.

Note: This message is a more specific version of the following messages: ResourceEvent.ResourceStateChanged

2.5.21 FilterRequiresService

Example: Filter 'Secondary' requires service.

Indicates that a filter requires service.

• This message shall indicate that a filter requires service. Examples include a dirty filter or a filter reaching the end of its life.

Version Added: v1.1

Severity: Warning

Resolution: Replace the filter or filter media.

Message and Arguments: "Filter '<1>' requires service."

1. string: The name or identifier of the filter.
   • This argument shall contain a string that identifies or describes the Filter resource.

Note: This message is a more specific version of the following messages: ResourceEvent.ResourceStatusChangedWarning

2.5.22 FilterRestored

Example: Filter 'Secondary' was restored.

Indicates that a filter was repaired or restored to normal operation.

• This message shall indicate that a filter was repaired, replaced, or otherwise returned to normal operation.

Version Added: v1.1

Severity: OK

Resolution: None.

Message and Arguments: "Filter '<1>' was restored."

1. string: The name or identifier of the filter.
   • This argument shall contain a string that identifies or describes the Filter resource.

Note: This message is a more specific version of the following messages: ResourceEvent.ResourceStatusChangedOK

2.5.23 FilterSubsystemHealth

Example: The filter subsystem health is OK.

Indicates the health of the filter subsystem for the equipment.

• This message shall indicate the health of the filter subsystem for the equipment.

Version Added: v1.2

Severity: OK

Resolution: None.

Message and Arguments: "The filter subsystem health is <1>."

1. string: The health of the filter subsystem for the equipment.
   • This argument shall contain the health of the filter subsystem for the equipment. This argument shall contain a value defined by the Health enumeration in the Resource schema.

2.5.24 FlowRateAboveLowerCriticalThreshold

Example: Flow rate 'Secondary TCS' reading of 18.9 L/min is now above the 15 lower critical threshold but remains outside of normal range.

Indicates that a flow rate reading is no longer below the lower critical threshold but is still outside of normal operating range.

• This message shall indicate that a flow rate reading, previously below the lower critical threshold, no longer violates the lower critical threshold. However, the flow rate violates at least one lower threshold and is not within the normal operating range.

Version Added: v1.1

Severity: Warning

Resolution: Check the condition of the resource listed in OriginOfCondition.

Message and Arguments: "Flow rate '<1>' reading of <2> L/min is now above the <3> lower critical threshold but remains outside of normal range."

1. string: The name or identifier of the flow rate reading.
   • This argument shall contain a string that identifies or describes the location or physical context of the flow rate reading.
2. number: The flow rate in litres per minute.
   • This argument shall contain the flow rate in litres per minute.
3. number: The threshold value.
   • This argument shall contain the value of the Reading property within the LowerCritical or LowerCriticalUser properties of the Sensor resource.

Note: This message is a more specific version of the following messages: SensorEvent.ReadingAboveLowerCriticalThreshold

2.5.25 FlowRateAboveLowerFatalThreshold

Example: Flow rate 'Secondary TCS' reading of 14.8 L/min is now above the 12 lower fatal threshold but remains outside of normal range.

Indicates that a flow rate reading is no longer below the lower fatal threshold but is still outside of normal operating range.

• This message shall indicate that a flow rate reading, previously below the lower fatal threshold, no longer violates the lower fatal threshold. However, the flow rate violates at least one lower threshold and is not within the normal operating range.

Version Added: v1.1

Severity: Critical

Resolution: Check the condition of the resource listed in OriginOfCondition.

Message and Arguments: "Flow rate '<1>' reading of <2> L/min is now above the <3> lower fatal threshold but remains outside of normal range."

1. string: The name or identifier of the flow rate reading.
   • This argument shall contain a string that identifies or describes the location or physical context of the flow rate reading.
2. number: The flow rate in litres per minute.
   • This argument shall contain the flow rate in litres per minute.
3. number: The threshold value.
   • This argument shall contain the value of the Reading property within the LowerFatal property of the Sensor resource.

Note: This message is a more specific version of the following messages: SensorEvent.ReadingAboveLowerFatalThreshold

2.5.26 FlowRateAboveUpperCautionThreshold

Example: Flow rate 'Facility Water System' reading of 62.4 L/min is above the 60 upper caution threshold.

Indicates that a flow rate reading is above the upper caution threshold.

• This message shall indicate that a flow rate reading violates an upper caution threshold. If the reading originates from a Sensor resource, the message shall indicate that the value of the Reading property is above the value of the Reading property within the UpperCaution or UpperCautionUser properties. Otherwise, the message shall indicate that the reading violates an internal level or threshold.

Version Added: v1.1

Severity: Warning

Resolution: Check the condition of the resource listed in OriginOfCondition.

Message and Arguments: "Flow rate '<1>' reading of <2> L/min is above the <3> upper caution threshold."

1. string: The name or identifier of the flow rate reading.
   • This argument shall contain a string that identifies or describes the location or physical context of the flow rate reading.
2. number: The flow rate in litres per minute.
   • This argument shall contain the flow rate in litres per minute.
3. number: The threshold value.
   • If the reading originated from a Sensor resource, this argument shall contain the value of the Reading property within the UpperCaution or UpperCautionUser properties of the Sensor resource. Otherwise, this argument shall contain an internal level or threshold value.

Note: This message is a more specific version of the following messages: SensorEvent.ReadingAboveUpperCautionThreshold

2.5.27 FlowRateAboveUpperCriticalThreshold

Example: Flow rate 'Facility Water System' reading of 68.1 L/min is above the 65 upper critical threshold.

Indicates that a flow rate reading is above the upper critical threshold.

• This message shall indicate that a flow rate reading violates an upper critical threshold. If the reading originates from a Sensor resource, the message shall indicate that the value of the Reading property is above the value of the Reading property within the UpperCritical or UpperCriticalUser properties.

Version Added: v1.1

Severity: Critical

Resolution: Check the condition of the resource listed in OriginOfCondition.

Message and Arguments: "Flow rate '<1>' reading of <2> L/min is above the <3> upper critical threshold."

1. string: The name or identifier of the flow rate reading.
   • This argument shall contain a string that identifies or describes the location or physical context of the flow rate reading.
2. number: The flow rate in litres per minute.
   • This argument shall contain the flow rate in litres per minute.
3. number: The threshold value.
   • This argument shall contain the value of the Reading property within the UpperCritical or UpperCriticalUser properties of the Sensor resource.

Note: This message is a more specific version of the following messages: SensorEvent.ReadingAboveUpperCriticalThreshold

2.5.28 FlowRateAboveUpperFatalThreshold

Example: Flow rate 'Facility Water System' reading of 75.8 L/min is above the 70 upper fatal threshold.

Indicates that a flow rate reading is above the upper fatal threshold.

• This message shall indicate that a flow rate reading violates an upper fatal threshold. If the reading originates from a Sensor resource, the message shall indicate that the value of the Reading property is above the value of the Reading property within the UpperFatal property.

Version Added: v1.1

Severity: Critical

Resolution: Check the condition of the resource listed in OriginOfCondition.

Message and Arguments: "Flow rate '<1>' reading of <2> L/min is above the <3> upper fatal threshold."

1. string: The name or identifier of the flow rate reading.
   • This argument shall contain a string that identifies or describes the location or physical context of the flow rate reading.
2. number: The flow rate in litres per minute.
   • This argument shall contain the flow rate in litres per minute.
3. number: The threshold value.
   • This argument shall contain the value of the Reading property within the UpperFatal property of the Sensor resource.

Note: This message is a more specific version of the following messages: SensorEvent.ReadingAboveUpperFatalThreshold

2.5.29 FlowRateBelowLowerCautionThreshold

Example: Flow rate 'Secondary TCS' reading of 18.5 L/min is below the 20 lower caution threshold.

Indicates that a flow rate reading is below the lower caution threshold.

• This message shall indicate that a flow rate reading violates a lower caution threshold. If the reading originates from a Sensor resource, the message shall indicate that the value of the Reading property is below the value of the Reading property within the LowerCaution or LowerCautionUser properties.

Version Added: v1.1

Severity: Warning

Resolution: Check the condition of the resource listed in OriginOfCondition.

Message and Arguments: "Flow rate '<1>' reading of <2> L/min is below the <3> lower caution threshold."

1. string: The name or identifier of the flow rate reading.
   • This argument shall contain a string that identifies or describes the location or physical context of the flow rate reading.
2. number: The flow rate in litres per minute.
   • This argument shall contain the flow rate in litres per minute.
3. number: The threshold value.
   • This argument shall contain the value of the Reading property within the LowerCaution or LowerCautionUser properties of the Sensor resource.

Note: This message is a more specific version of the following messages: SensorEvent.ReadingBelowLowerCautionThreshold

2.5.30 FlowRateBelowLowerCriticalThreshold

Example: Flow rate 'Secondary TCS' reading of 14.7 L/min is below the 15 lower critical threshold.

Indicates that a flow rate reading is below the lower critical threshold.

• This message shall indicate that a flow rate reading violates a lower critical threshold. If the reading originates from a Sensor resource, the message shall indicate that the value of the Reading property is below the value of the Reading property within the LowerCritical or LowerCriticalUser properties.

Version Added: v1.1

Severity: Critical

Resolution: Check the condition of the resource listed in OriginOfCondition.

Message and Arguments: "Flow rate '<1>' reading of <2> L/min is below the <3> lower critical threshold."

1. string: The name or identifier of the flow rate reading.
   • This argument shall contain a string that identifies or describes the location or physical context of the flow rate reading.
2. number: The flow rate in litres per minute.
   • This argument shall contain the flow rate in litres per minute.
3. number: The threshold value.
   • This argument shall contain the value of the Reading property within the LowerCritical or LowerCriticalUser properties of the Sensor resource.

Note: This message is a more specific version of the following messages: SensorEvent.ReadingBelowLowerCriticalThreshold

2.5.31 FlowRateBelowLowerFatalThreshold

Example: Flow rate 'Secondary TCS' reading of 7.0 L/min is below the 12 lower fatal threshold.

Indicates that a flow rate reading is below the lower fatal threshold.

• This message shall indicate that a flow rate reading violates a lower fatal threshold. If the reading originates from a Sensor resource, the message shall indicate that the value of the Reading property is below the value of the Reading property within the LowerFatal property.

Version Added: v1.1

Severity: Critical

Resolution: Check the condition of the resource listed in OriginOfCondition.

Message and Arguments: "Flow rate '<1>' reading of <2> L/min is below the <3> lower fatal threshold."

1. string: The name or identifier of the flow rate reading.
   • This argument shall contain a string that identifies or describes the location or physical context of the flow rate reading.
2. number: The flow rate in litres per minute.
   • This argument shall contain the flow rate in litres per minute.
3. number: The threshold value.
   • This argument shall contain the value of the Reading property within the LowerFatal property of the Sensor resource.

Note: This message is a more specific version of the following messages: SensorEvent.ReadingBelowLowerFatalThreshold

2.5.32 FlowRateBelowUpperCriticalThreshold

Example: Flow rate 'Facility Water System' reading of 64.3 L/min is now below the 65 upper critical threshold but remains outside of normal range.

Indicates that a flow rate reading is no longer above the upper critical threshold but is still outside of normal operating range.

• This message shall indicate that a flow rate reading, previously above the upper critical threshold, no longer violates the upper critical threshold. However, the flow rate violates at least one upper threshold and is not within the normal operating range.

Version Added: v1.1

Severity: Warning

Resolution: Check the condition of the resource listed in OriginOfCondition.

Message and Arguments: "Flow rate '<1>' reading of <2> L/min is now below the <3> upper critical threshold but remains outside of normal range."

1. string: The name or identifier of the flow rate reading.
   • This argument shall contain a string that identifies or describes the location or physical context of the flow rate reading.
2. number: The flow rate in litres per minute.
   • This argument shall contain the flow rate in litres per minute.
3. number: The threshold value.
   • This argument shall contain the value of the Reading property within the UpperCritical or UpperCriticalUser properties of the Sensor resource.

Note: This message is a more specific version of the following messages: SensorEvent.ReadingBelowUpperCriticalThreshold

2.5.33 FlowRateBelowUpperFatalThreshold

Example: Flow rate 'Facility Water System' reading of 68.8 L/min is now below the 70 upper fatal threshold but remains outside of normal range.

Indicates that a flow rate reading is no longer above the upper fatal threshold but is still outside of normal operating range.

• This message shall indicate that a flow rate reading, previously above the upper fatal threshold, no longer violates the upper fatal threshold. However, the flow rate violates at least one upper threshold and is not within the normal operating range.

Version Added: v1.1

Severity: Critical

Resolution: Check the condition of the resource listed in OriginOfCondition.

Message and Arguments: "Flow rate '<1>' reading of <2> L/min is now below the <3> upper fatal threshold but remains outside of normal range."

1. string: The name or identifier of the flow rate reading.
   • This argument shall contain a string that identifies or describes the location or physical context of the flow rate reading.
2. number: The flow rate in litres per minute.
   • This argument shall contain the flow rate in litres per minute.
3. number: The threshold value.
   • This argument shall contain the value of the Reading property within the UpperFatal property of the Sensor resource.

Note: This message is a more specific version of the following messages: SensorEvent.ReadingBelowUpperFatalThreshold

2.5.34 FlowRateCritical

Example: Flow rate 'Facility Water System' reading of 67.4 L/min exceeds the critical level.

Indicates that a flow rate reading exceeds an internal critical level.

• This message shall indicate that a flow rate reading violates an internal critical level. This message shall be used for flow rate properties or Sensor resources that implement boolean trip points for a critical limit, such as from hardware mechanisms with no threshold value. The flow rate properties or Sensor resources may contain readable thresholds that coexist with this unspecified trip point.

Version Added: v1.1

Severity: Critical

Resolution: Check the condition of the resource listed in OriginOfCondition.

Message and Arguments: "Flow rate '<1>' reading of <2> L/min exceeds the critical level."

1. string: The name or identifier of the flow rate reading.
   • This argument shall contain a string that identifies or describes the location or physical context of the flow rate reading.
2. number: The flow rate in litres per minute.
   • This argument shall contain the flow rate in litres per minute.

Note: This message is a more specific version of the following messages: SensorEvent.ReadingCritical

2.5.35 FlowRateFatal

Example: Flow rate 'Facility Water System' reading of 73.1 L/min exceeds the fatal level.

Indicates that a flow rate reading exceeds an internal fatal level or flow rate reading is zero (0).

• This message shall indicate that a flow rate reading violates an internal fatal level. This message shall be used for flow rate properties or Sensor resources that implement boolean trip points for a fatal limit, such as from hardware mechanisms with no threshold value. The flow rate properties or Sensor resources may contain readable thresholds that coexist with this unspecified trip point.

Version Added: v1.1

Severity: Critical

Resolution: Check the condition of the resource listed in OriginOfCondition.

Message and Arguments: "Flow rate '<1>' reading of <2> L/min exceeds the fatal level."

1. string: The name or identifier of the flow rate reading.
   • This argument shall contain a string that identifies or describes the location or physical context of the flow rate reading.
2. number: The flow rate in litres per minute.
   • This argument shall contain the flow rate in litres per minute.

Note: This message is a more specific version of the following messages: SensorEvent.ReadingFatal

2.5.36 FlowRateNoLongerCritical

Example: Flow rate 'Facility Water System' reading of 67.1 L/min no longer exceeds the critical level.

Indicates that a flow rate reading no longer exceeds an internal critical level but still exceeds an internal warning level.

• This message shall indicate that a flow rate reading no longer violates an internal critical level but still violates an internal warning level. This message shall be used for flow rate properties or Sensor resources that implement boolean trip points for a critical limit, such as from hardware mechanisms with no threshold value. The flow rate properties or Sensor resources may contain readable thresholds that coexist with this unspecified trip point.

Version Added: v1.1

Severity: Warning

Resolution: Check the condition of the resource listed in OriginOfCondition.

Message and Arguments: "Flow rate '<1>' reading of <2> L/min no longer exceeds the critical level."

1. string: The name or identifier of the flow rate reading.
   • This argument shall contain a string that identifies or describes the location or physical context of the flow rate reading.
2. number: The flow rate in litres per minute.
   • This argument shall contain the flow rate in litres per minute.

Note: This message is a more specific version of the following messages: SensorEvent.ReadingNoLongerCritical

2.5.37 FlowRateNoLongerFatal

Example: Flow rate 'Facility Water System' reading of 68.1 L/min no longer exceeds the fatal level.

Indicates that a flow rate reading is no longer exceeds an internal fatal level but is still exceeds an internal critical level.

• This message shall indicate that a flow rate reading no longer violates an internal fatal level but still violates an internal critical level. This message shall be used for flow rate properties or Sensor resources that implement boolean trip points for a fatal limit, such as from hardware mechanisms with no threshold value. The flow rate properties or Sensor resources may contain readable thresholds that coexist with this unspecified trip point.

Version Added: v1.1

Severity: Critical

Resolution: Check the condition of the resource listed in OriginOfCondition.

Message and Arguments: "Flow rate '<1>' reading of <2> L/min no longer exceeds the fatal level."

1. string: The name or identifier of the flow rate reading.
   • This argument shall contain a string that identifies or describes the location or physical context of the flow rate reading.
2. number: The flow rate in litres per minute.
   • This argument shall contain the flow rate in litres per minute.

Note: This message is a more specific version of the following messages: SensorEvent.ReadingNoLongerFatal

2.5.38 FlowRateNormal

Example: Flow rate 'Secondary TCS' reading of 42.1 L/min is within normal operating range.

Indicates that a flow rate reading is now within normal operating range.

• This message shall indicate that a flow rate reading has returned to its normal operating range.

Version Added: v1.1

Severity: OK

Resolution: None.

Message and Arguments: "Flow rate '<1>' reading of <2> L/min is within normal operating range."

1. string: The name or identifier of the flow rate reading.
   • This argument shall contain a string that identifies or describes the location or physical context of the flow rate reading.
2. number: The flow rate in litres per minute.
   • This argument shall contain the flow rate in litres per minute.

Note: This message is a more specific version of the following messages: SensorEvent.SensorReadingNormalRange

2.5.39 FlowRateWarning

Example: Flow rate 'Facility Water System' reading of 62.8 L/min exceeds the warning level.

Indicates that a flow rate reading exceeds an internal warning level.

• This message shall indicate that a flow rate reading violates an internal warning level. This message shall be used for flow rate properties or Sensor resources that implement boolean trip points for a caution limit, such as from hardware mechanisms with no threshold value. The flow rate properties or Sensor resources may contain readable thresholds that coexist with this unspecified trip point.

Version Added: v1.1

Severity: Warning

Resolution: Check the condition of the resource listed in OriginOfCondition.

Message and Arguments: "Flow rate '<1>' reading of <2> L/min exceeds the warning level."

1. string: The name or identifier of the flow rate reading.
   • This argument shall contain a string that identifies or describes the location or physical context of the flow rate reading.
2. number: The flow rate in litres per minute.
   • This argument shall contain the flow rate in litres per minute.

Note: This message is a more specific version of the following messages: SensorEvent.ReadingWarning

2.5.40 FluidLevelAboveLowerCriticalThreshold

Example: Fluid level 'Fill Reservoir' reading of 15 percent is now above the 10 lower critical threshold but remains outside of normal range.

Indicates that a fluid level reading is no longer below the lower critical threshold but is still outside of normal operating range.

• This message shall indicate that a fluid level reading, previously below the lower critical threshold, no longer violates the lower critical threshold. However, the fluid level violates at least one lower threshold and is not within the normal operating range.

Version Added: v1.1

Severity: Warning

Resolution: Check the condition of the resource listed in OriginOfCondition.

Message and Arguments: "Fluid level '<1>' reading of <2> percent is now above the <3> lower critical threshold but remains outside of normal range."

1. string: The name or identifier of the fluid level reading.
   • This argument shall contain a string that identifies or describes the location or physical context of the fluid level reading.
2. number: The fluid level in percent.
   • This argument shall contain the fluid level in percent.
3. number: The threshold value.
   • This argument shall contain the value of the Reading property within the LowerCritical or LowerCriticalUser properties of the Sensor resource.

Note: This message is a more specific version of the following messages: SensorEvent.ReadingAboveLowerCriticalThreshold

2.5.41 FluidLevelAboveLowerFatalThreshold

Example: Fluid level 'Fill Reservoir' reading of 5 percent is now above the 1 lower fatal threshold but remains outside of normal range.

Indicates that a fluid level reading is no longer below the lower fatal threshold but is still outside of normal operating range.

• This message shall indicate that a fluid level reading, previously below the lower fatal threshold, no longer violates the lower fatal threshold. However, the fluid level violates at least one lower threshold and is not within the normal operating range.

Version Added: v1.1

Severity: Critical

Resolution: Check the condition of the resource listed in OriginOfCondition.

Message and Arguments: "Fluid level '<1>' reading of <2> percent is now above the <3> lower fatal threshold but remains outside of normal range."

1. string: The name or identifier of the fluid level reading.
   • This argument shall contain a string that identifies or describes the location or physical context of the fluid level reading.
2. number: The fluid level in percent.
   • This argument shall contain the fluid level in percent.
3. number: The threshold value.
   • This argument shall contain the value of the Reading property within the LowerFatal property of the Sensor resource.

Note: This message is a more specific version of the following messages: SensorEvent.ReadingAboveLowerFatalThreshold

2.5.42 FluidLevelAboveUpperCautionThreshold

Example: Fluid level 'Overflow Reservoir' reading of 81 percent is above the 80 upper caution threshold.

Indicates that a fluid level reading is above the upper caution threshold.

• This message shall indicate that a fluid level reading violates an upper caution threshold. If the reading originates from a Sensor resource, the message shall indicate that the value of the Reading property is above the value of the Reading property within the UpperCaution or UpperCautionUser properties. Otherwise, the message shall indicate that the reading violates an internal level or threshold.

Version Added: v1.1

Severity: Warning

Resolution: Check the condition of the resource listed in OriginOfCondition.

Message and Arguments: "Fluid level '<1>' reading of <2> percent is above the <3> upper caution threshold."

1. string: The name or identifier of the fluid level reading.
   • This argument shall contain a string that identifies or describes the location or physical context of the fluid level reading.
2. number: The fluid level in percent.
   • This argument shall contain the fluid level in percent.
3. number: The threshold value.
   • If the reading originated from a Sensor resource, this argument shall contain the value of the Reading property within the UpperCaution or UpperCautionUser properties of the Sensor resource. Otherwise, this argument shall contain an internal level or threshold value.

Note: This message is a more specific version of the following messages: SensorEvent.ReadingAboveUpperCautionThreshold

2.5.43 FluidLevelAboveUpperCriticalThreshold

Example: Fluid level 'Overflow Reservoir' reading of 97 percent is above the 95 upper critical threshold.

Indicates that a fluid level reading is above the upper critical threshold.

• This message shall indicate that a fluid level reading violates an upper critical threshold. If the reading originates from a Sensor resource, the message shall indicate that the value of the Reading property is above the value of the Reading property within the UpperCritical or UpperCriticalUser properties.

Version Added: v1.1

Severity: Critical

Resolution: Check the condition of the resource listed in OriginOfCondition.

Message and Arguments: "Fluid level '<1>' reading of <2> percent is above the <3> upper critical threshold."

1. string: The name or identifier of the fluid level reading.
   • This argument shall contain a string that identifies or describes the location or physical context of the fluid level reading.
2. number: The fluid level in percent.
   • This argument shall contain the fluid level in percent.
3. number: The threshold value.
   • This argument shall contain the value of the Reading property within the UpperCritical or UpperCriticalUser properties of the Sensor resource.

Note: This message is a more specific version of the following messages: SensorEvent.ReadingAboveUpperCriticalThreshold

2.5.44 FluidLevelAboveUpperFatalThreshold

Example: Fluid level 'Overflow Reservoir' reading of 100 percent is above the 99.5 upper fatal threshold.

Indicates that a fluid level reading is above the upper fatal threshold.

• This message shall indicate that a fluid level reading violates an upper fatal threshold. If the reading originates from a Sensor resource, the message shall indicate that the value of the Reading property is above the value of the Reading property within the UpperFatal property.

Version Added: v1.1

Severity: Critical

Resolution: Check the condition of the resource listed in OriginOfCondition.

Message and Arguments: "Fluid level '<1>' reading of <2> percent is above the <3> upper fatal threshold."

1. string: The name or identifier of the fluid level reading.
   • This argument shall contain a string that identifies or describes the location or physical context of the fluid level reading.
2. number: The fluid level in percent.
   • This argument shall contain the fluid level in percent.
3. number: The threshold value.
   • This argument shall contain the value of the Reading property within the UpperFatal property of the Sensor resource.

Note: This message is a more specific version of the following messages: SensorEvent.ReadingAboveUpperFatalThreshold

2.5.45 FluidLevelBelowLowerCautionThreshold

Example: Fluid level 'Fill Reservoir' reading of 19 percent is below the 20 lower caution threshold.

Indicates that a fluid level reading is below the lower caution threshold.

• This message shall indicate that a fluid level reading violates a lower caution threshold. If the reading originates from a Sensor resource, the message shall indicate that the value of the Reading property is below the value of the Reading property within the LowerCaution or LowerCautionUser properties.

Version Added: v1.1

Severity: Warning

Resolution: Check the condition of the resource listed in OriginOfCondition.

Message and Arguments: "Fluid level '<1>' reading of <2> percent is below the <3> lower caution threshold."

1. string: The name or identifier of the fluid level reading.
   • This argument shall contain a string that identifies or describes the location or physical context of the fluid level reading.
2. number: The fluid level in percent.
   • This argument shall contain the fluid level in percent.
3. number: The threshold value.
   • This argument shall contain the value of the Reading property within the LowerCaution or LowerCautionUser properties of the Sensor resource.

Note: This message is a more specific version of the following messages: SensorEvent.ReadingBelowLowerCautionThreshold

2.5.46 FluidLevelBelowLowerCriticalThreshold

Example: Fluid level 'Fill Reservoir' reading of 7 percent is below the 10 lower critical threshold.

Indicates that a fluid level reading is below the lower critical threshold.

• This message shall indicate that a fluid level reading violates a lower critical threshold. If the reading originates from a Sensor resource, the message shall indicate that the value of the Reading property is below the value of the Reading property within the LowerCritical or LowerCriticalUser properties.

Version Added: v1.1

Severity: Critical

Resolution: Check the condition of the resource listed in OriginOfCondition.

Message and Arguments: "Fluid level '<1>' reading of <2> percent is below the <3> lower critical threshold."

1. string: The name or identifier of the fluid level reading.
   • This argument shall contain a string that identifies or describes the location or physical context of the fluid level reading.
2. number: The fluid level in percent.
   • This argument shall contain the fluid level in percent.
3. number: The threshold value.
   • This argument shall contain the value of the Reading property within the LowerCritical or LowerCriticalUser properties of the Sensor resource.

Note: This message is a more specific version of the following messages: SensorEvent.ReadingBelowLowerCriticalThreshold

2.5.47 FluidLevelBelowLowerFatalThreshold

Example: Fluid level 'Fill Reservoir' reading of 0.5 percent is below the 1 lower fatal threshold.

Indicates that a fluid level reading is below the lower fatal threshold.

• This message shall indicate that a fluid level reading violates a lower fatal threshold. If the reading originates from a Sensor resource, the message shall indicate that the value of the Reading property is below the value of the Reading property within the LowerFatal property.

Version Added: v1.1

Severity: Critical

Resolution: Check the condition of the resource listed in OriginOfCondition.

Message and Arguments: "Fluid level '<1>' reading of <2> percent is below the <3> lower fatal threshold."

1. string: The name or identifier of the fluid level reading.
   • This argument shall contain a string that identifies or describes the location or physical context of the fluid level reading.
2. number: The fluid level in percent.
   • This argument shall contain the fluid level in percent.
3. number: The threshold value.
   • This argument shall contain the value of the Reading property within the LowerFatal property of the Sensor resource.

Note: This message is a more specific version of the following messages: SensorEvent.ReadingBelowLowerFatalThreshold

2.5.48 FluidLevelBelowUpperCriticalThreshold

Example: Fluid level 'Overflow Reservoir' reading of 91.5 percent is now below the 95 upper critical threshold but remains outside of normal range.

Indicates that a fluid level reading is no longer above the upper critical threshold but is still outside of normal operating range.

• This message shall indicate that a fluid level reading, previously above the upper critical threshold, no longer violates the upper critical threshold. However, the fluid level violates at least one upper threshold and is not within the normal operating range.

Version Added: v1.1

Severity: Warning

Resolution: Check the condition of the resource listed in OriginOfCondition.

Message and Arguments: "Fluid level '<1>' reading of <2> percent is now below the <3> upper critical threshold but remains outside of normal range."

1. string: The name or identifier of the fluid level reading.
   • This argument shall contain a string that identifies or describes the location or physical context of the fluid level reading.
2. number: The fluid level in percent.
   • This argument shall contain the fluid level in percent.
3. number: The threshold value.
   • This argument shall contain the value of the Reading property within the UpperCritical or UpperCriticalUser properties of the Sensor resource.

Note: This message is a more specific version of the following messages: SensorEvent.ReadingBelowUpperCriticalThreshold

2.5.49 FluidLevelBelowUpperFatalThreshold

Example: Fluid level 'Overflow Reservoir' reading of 97 percent is now below the 100 upper fatal threshold but remains outside of normal range.

Indicates that a fluid level reading is no longer above the upper fatal threshold but is still outside of normal operating range.

• This message shall indicate that a fluid level reading, previously above the upper fatal threshold, no longer violates the upper fatal threshold. However, the fluid level violates at least one upper threshold and is not within the normal operating range.

Version Added: v1.1

Severity: Critical

Resolution: Check the condition of the resource listed in OriginOfCondition.

Message and Arguments: "Fluid level '<1>' reading of <2> percent is now below the <3> upper fatal threshold but remains outside of normal range."

1. string: The name or identifier of the fluid level reading.
   • This argument shall contain a string that identifies or describes the location or physical context of the fluid level reading.
2. number: The fluid level in percent.
   • This argument shall contain the fluid level in percent.
3. number: The threshold value.
   • This argument shall contain the value of the Reading property within the UpperFatal property of the Sensor resource.

Note: This message is a more specific version of the following messages: SensorEvent.ReadingBelowUpperFatalThreshold

2.5.50 FluidLevelCritical

Example: Fluid level 'Overflow Reservoir' reading violates the critical level.

Indicates that a fluid level reading violates an internal critical level.

• This message shall indicate that a fluid level reading violates an internal critical level. This message shall be used for fluid level properties or Sensor resources that implement boolean trip points for a critical limit, such as from hardware mechanisms with no threshold value. The fluid level properties or Sensor resources may contain readable thresholds that coexist with this unspecified trip point.

Version Added: v1.1

Severity: Critical

Resolution: Check the condition of the resource listed in OriginOfCondition.

Message and Arguments: "Fluid level '<1>' reading violates the critical level."

1. string: The name or identifier of the fluid level reading.
   • This argument shall contain a string that identifies or describes the location or physical context of the fluid level reading.

Note: This message is a more specific version of the following messages: SensorEvent.ReadingCritical

2.5.51 FluidLevelNoLongerCritical

Example: Fluid level 'Overflow Reservoir' reading no longer violates the critical level.

Indicates that a fluid level reading no longer violates an internal critical level but still violates an internal warning level.

• This message shall indicate that a fluid level reading no longer violates an internal critical level but still violates an internal warning level. This message shall be used for fluid level properties or Sensor resources that implement boolean trip points for a critical limit, such as from hardware mechanisms with no threshold value. The fluid level properties or Sensor resources may contain readable thresholds that coexist with this unspecified trip point.

Version Added: v1.1

Severity: Warning

Resolution: Check the condition of the resource listed in OriginOfCondition.

Message and Arguments: "Fluid level '<1>' reading no longer violates the critical level."

1. string: The name or identifier of the fluid level reading.
   • This argument shall contain a string that identifies or describes the location or physical context of the fluid level reading.

Note: This message is a more specific version of the following messages: SensorEvent.ReadingNoLongerCritical

2.5.52 FluidLevelNormal

Example: Fluid level 'Overflow Reservoir' reading is within normal operating range.

Indicates that a fluid level reading is now within normal operating range.

• This message shall indicate that a fluid level reading has returned to its normal operating range.

Version Added: v1.1

Severity: OK

Resolution: None.

Message and Arguments: "Fluid level '<1>' reading is within normal operating range."

1. string: The name or identifier of the fluid level reading.
   • This argument shall contain a string that identifies or describes the location or physical context of the fluid level reading.

Note: This message is a more specific version of the following messages: SensorEvent.SensorReadingNormalRange

2.5.53 FluidLevelWarning

Example: Fluid level 'Overflow Reservoir' reading violates the warning level.

Indicates that a fluid level reading violates an internal warning level.

• This message shall indicate that a fluid level reading violates an internal warning level. This message shall be used for fluid level properties or Sensor resources that implement boolean trip points for a caution limit, such as from hardware mechanisms with no threshold value. The fluid level properties or Sensor resources may contain readable thresholds that coexist with this unspecified trip point.

Version Added: v1.1

Severity: Warning

Resolution: Check the condition of the resource listed in OriginOfCondition.

Message and Arguments: "Fluid level '<1>' reading violates the warning level."

1. string: The name or identifier of the fluid level reading.
   • This argument shall contain a string that identifies or describes the location or physical context of the fluid level reading.

Note: This message is a more specific version of the following messages: SensorEvent.ReadingWarning

2.5.54 FluidQualityCritical

Example: Fluid quality 'Secondary TCS' reading exceeds the critical level.

Indicates that a fluid quality reading exceeds an internal critical level.

• This message shall indicate that a fluid quality reading violates an internal critical level. This message shall be used for fluid quality properties or Sensor resources that implement boolean trip points for a critical limit, such as from hardware mechanisms with no threshold value. The fluid quality properties or Sensor resources may contain readable thresholds that coexist with this unspecified trip point.

Version Added: v1.1

Severity: Critical

Resolution: Check the condition of the resource listed in OriginOfCondition.

Message and Arguments: "Fluid quality '<1>' reading exceeds the critical level."

1. string: The name or identifier of the fluid quality reading.
   • This argument shall contain a string that identifies or describes the location or physical context of the fluid quality reading.

Note: This message is a more specific version of the following messages: SensorEvent.ReadingCritical

2.5.55 FluidQualityNoLongerCritical

Example: Fluid quality 'Secondary TCS' reading no longer exceeds the critical level.

Indicates that a fluid quality reading no longer exceeds an internal critical level but still exceeds an internal warning level.

• This message shall indicate that a fluid quality reading no longer violates an internal critical level but still violates an internal warning level. This message shall be used for fluid quality properties or Sensor resources that implement boolean trip points for a critical limit, such as from hardware mechanisms with no threshold value. The fluid quality properties or Sensor resources may contain readable thresholds that coexist with this unspecified trip point.

Version Added: v1.1

Severity: Warning

Resolution: Check the condition of the resource listed in OriginOfCondition.

Message and Arguments: "Fluid quality '<1>' reading no longer exceeds the critical level."

1. string: The name or identifier of the fluid quality reading.
   • This argument shall contain a string that identifies or describes the location or physical context of the fluid quality reading.

Note: This message is a more specific version of the following messages: SensorEvent.ReadingNoLongerCritical

2.5.56 FluidQualityNormal

Example: Fluid quality 'Secondary TCS' reading is within normal operating range.

Indicates that a fluid quality reading is now within normal operating range.

• This message shall indicate that a fluid quality reading has returned to its normal operating range.

Version Added: v1.1

Severity: OK

Resolution: None.

Message and Arguments: "Fluid quality '<1>' reading is within normal operating range."

1. string: The name or identifier of the fluid quality reading.
   • This argument shall contain a string that identifies or describes the location or physical context of the fluid quality reading.

Note: This message is a more specific version of the following messages: SensorEvent.SensorReadingNormalRange

2.5.57 FluidQualityWarning

Example: Fluid quality 'Secondary TCS' reading exceeds the warning level.

Indicates that a fluid quality reading exceeds an internal warning level.

• This message shall indicate that a fluid quality reading violates an internal warning level. This message shall be used for fluid quality properties or Sensor resources that implement boolean trip points for a caution limit, such as from hardware mechanisms with no threshold value. The fluid quality properties or Sensor resources may contain readable thresholds that coexist with this unspecified trip point.

Version Added: v1.1

Severity: Warning

Resolution: Check the condition of the resource listed in OriginOfCondition.

Message and Arguments: "Fluid quality '<1>' reading exceeds the warning level."

1. string: The name or identifier of the fluid quality reading.
   • This argument shall contain a string that identifies or describes the location or physical context of the fluid quality reading.

Note: This message is a more specific version of the following messages: SensorEvent.ReadingWarning

2.5.58 HumidityAboveLowerCriticalThreshold

Example: Humidity 'Room Ambient' reading of 26.3 percent is now above the 25 lower critical threshold but remains outside of normal range.

Indicates that a humidity reading is no longer below the lower critical threshold but is still outside of normal operating range.

• This message shall indicate that a humidity reading, previously below the lower critical threshold, no longer violates the lower critical threshold. However, the humidity violates at least one lower threshold and is not within the normal operating range.

Version Added: v1.0

Severity: Warning

Resolution: Check the condition of the resource listed in OriginOfCondition.

Message and Arguments: "Humidity '<1>' reading of <2> percent is now above the <3> lower critical threshold but remains outside of normal range."

1. string: The name or identifier of the humidity reading.
   • This argument shall contain a string that identifies or describes the location or physical context of the humidity reading.
2. number: The percent humidity.
   • This argument shall contain the humidity as a percentage.
3. number: The threshold value.
   • This argument shall contain the value of the Reading property within the LowerCritical or LowerCriticalUser properties of the Sensor resource.

Note: This message is a more specific version of the following messages: SensorEvent.ReadingAboveLowerCriticalThreshold

2.5.59 HumidityAboveUpperCautionThreshold

Example: Humidity 'Room Ambient' reading of 57 percent is above the 55 upper caution threshold.

Indicates that a humidity reading is above the upper caution threshold.

• This message shall indicate that a humidity reading violates an upper caution threshold. If the reading originates from a Sensor resource, the message shall indicate that the value of the Reading property is above the value of the Reading property within the UpperCaution or UpperCautionUser properties.

Version Added: v1.0

Severity: Warning

Resolution: Check the condition of the resource listed in OriginOfCondition.

Message and Arguments: "Humidity '<1>' reading of <2> percent is above the <3> upper caution threshold."

1. string: The name or identifier of the humidity reading.
   • This argument shall contain a string that identifies or describes the location or physical context of the humidity reading.
2. number: The humidity in percent units.
   • This argument shall contain the humidity as a percentage.
3. number: The threshold value.
   • This argument shall contain the value of the Reading property within the UpperCaution or UpperCautionUser properties of the Sensor resource.

Note: This message is a more specific version of the following messages: SensorEvent.ReadingAboveUpperCautionThreshold

2.5.60 HumidityAboveUpperCriticalThreshold

Example: Humidity 'Room Ambient' reading of 62.1 percent is above the 60 upper critical threshold.

Indicates that a humidity reading is above the upper critical threshold.

• This message shall indicate that a humidity reading violates an upper caution threshold. If the reading originates from a Sensor resource, the message shall indicate that the value of the Reading property is above the value of the Reading property within the UpperCritical or UpperCriticalUser properties.

Version Added: v1.0

Severity: Critical

Resolution: Check the condition of the resource listed in OriginOfCondition.

Message and Arguments: "Humidity '<1>' reading of <2> percent is above the <3> upper critical threshold."

1. string: The name or identifier of the humidity reading.
   • This argument shall contain a string that identifies or describes the location or physical context of the humidity reading.
2. number: The humidity in percent units.
   • This argument shall contain the humidity as a percentage.
3. number: The threshold value.
   • This argument shall contain the value of the Reading property within the UpperCritical or UpperCriticalUser properties of the Sensor resource.

Note: This message is a more specific version of the following messages: SensorEvent.ReadingAboveUpperCriticalThreshold

2.5.61 HumidityBelowLowerCautionThreshold

Example: Humidity 'Room Ambient' reading of 27.8 percent is below the 30 lower caution threshold.

Indicates that a humidity reading is below the lower caution threshold.

• This message shall indicate that a humidity reading violates an lower caution threshold. If the reading originates from a Sensor resource, the message shall indicate that the value of the Reading property is below the value of the Reading property within the LowerCaution or LowerCautionUser properties.

Version Added: v1.0

Severity: Warning

Resolution: Check the condition of the resource listed in OriginOfCondition.

Message and Arguments: "Humidity '<1>' reading of <2> percent is below the <3> lower caution threshold."

1. string: The name or identifier of the humidity reading.
   • This argument shall contain a string that identifies or describes the location or physical context of the humidity reading.
2. number: The humidity in percent units.
   • This argument shall contain the humidity as a percentage.
3. number: The threshold value.
   • This argument shall contain the value of the Reading property within the LowerCaution or LowerCautionUser properties of the Sensor resource.

Note: This message is a more specific version of the following messages: SensorEvent.ReadingBelowLowerCautionThreshold

2.5.62 HumidityBelowLowerCriticalThreshold

Example: Humidity 'Room Ambient' reading of 24.8 percent is below the 25 lower critical threshold.

Indicates that a humidity reading is below the lower critical threshold.

• This message shall indicate that a humidity reading violates a lower critical threshold. If the reading originates from a Sensor resource, the message shall indicate that the value of the Reading property is below the value of the Reading property within the LowerCritical or LowerCriticalUser properties.

Version Added: v1.0

Severity: Critical

Resolution: Check the condition of the resource listed in OriginOfCondition.

Message and Arguments: "Humidity '<1>' reading of <2> percent is below the <3> lower critical threshold."

1. string: The name or identifier of the humidity reading.
   • This argument shall contain a string that identifies or describes the location or physical context of the humidity reading.
2. number: The humidity in percent units.
   • This argument shall contain the humidity as a percentage.
3. number: The threshold value.
   • This argument shall contain the value of the Reading property within the UpperCritical or UpperCriticalUser properties of the Sensor resource.

Note: This message is a more specific version of the following messages: SensorEvent.ReadingBelowLowerCriticalThreshold

2.5.63 HumidityBelowUpperCriticalThreshold

Example: Humidity 'Room Ambient' reading of 59.2 percent is now below the 60 upper critical threshold but remains outside of normal range.

Indicates that a humidity reading is no longer above the upper critical threshold but is still outside of normal operating range.

• This message shall indicate that a humidity reading, previously above the critical threshold, no longer violates the critical threshold. However, the humidity violates at least one upper threshold and is not within the normal operating range.

Version Added: v1.0

Severity: Warning

Resolution: Check the condition of the resource listed in OriginOfCondition.

Message and Arguments: "Humidity '<1>' reading of <2> percent is now below the <3> upper critical threshold but remains outside of normal range."

1. string: The name or identifier of the humidity reading.
   • This argument shall contain a string that identifies or describes the location or physical context of the temperature reading.
2. number: The percent humidity.
   • This argument shall contain the humidity as a percentage.
3. number: The threshold value.
   • This argument shall contain the value of the Reading property within the UpperCritical or UpperCriticalUser properties of the Sensor resource.

Note: This message is a more specific version of the following messages: SensorEvent.ReadingBelowUpperCriticalThreshold

2.5.64 HumidityNormal

Example: Humidity 'Room Ambient' reading of 51.5 percent is within normal operating range.

Indicates that a humidity reading is now within normal operating range.

• This message shall indicate that a humidity reading has returned to its normal operating range.

Version Added: v1.0

Severity: OK

Resolution: None.

Message and Arguments: "Humidity '<1>' reading of <2> percent is within normal operating range."

1. string: The name or identifier of the humidity reading.
   • This argument shall contain a string that identifies or describes the location or physical context of the humidity reading.
2. number: The percent humidity.
   • This argument shall contain the humidity as a percentage.

Note: This message is a more specific version of the following messages: SensorEvent.SensorReadingNormalRange

2.5.65 LeakDetectedCritical

Example: Leak detector 'Rack #42 Spot' reports a critical level leak.

Indicates that a leak detector is in a critical state.

• This message shall indicate a leak detector is in a critical state.

Version Added: v1.1

Severity: Critical

Resolution: Check the condition of the resource listed in OriginOfCondition.

Message and Arguments: "Leak detector '<1>' reports a critical level leak."

1. string: The name or identifier of the leak detector.
   • This argument shall contain a string that identifies or describes the location or physical context of the leak detector.

Note: This message is a more specific version of the following messages: SensorEvent.ReadingCritical

2.5.66 LeakDetectedNormal

Example: Leak detector 'Rack #42 Spot' has returned to normal.

Indicates that a leak detector is within normal operating range.

• This message shall indicate that a leak detector returned to its normal operating state.

Version Added: v1.1

Severity: OK

Resolution: None.

Message and Arguments: "Leak detector '<1>' has returned to normal."

1. string: The name or identifier of the leak detector.
   • This argument shall contain a string that identifies or describes the location or physical context of the leak detector.

Note: This message is a more specific version of the following messages: SensorEvent.SensorReadingNormalRange

2.5.67 LeakDetectedWarning

Example: Leak detector 'Rack #19 Rope' reports a warning level leak.

Indicates that a leak detector is in a warning state.

• This message shall indicate a leak detector is in a warning state.

Version Added: v1.1

Severity: Warning

Resolution: Check the condition of the resource listed in OriginOfCondition.

Message and Arguments: "Leak detector '<1>' reports a warning level leak."

1. string: The name or identifier of the leak detector.
   • This argument shall contain a string that identifies or describes the location or physical context of the leak detector.

Note: This message is a more specific version of the following messages: SensorEvent.ReadingWarning

2.5.68 LeakDetectorConnected

Example: Leak detector 'Rack #19 Rope' was connected.

Indicates that an external leak detector was connected.

• This message shall indicate that an external leak detector was connected.

Version Added: v1.3

Severity: OK

Resolution: None.

Message and Arguments: "Leak detector '<1>' was connected."

1. string: The name or identifier of the leak detector.
   • This argument shall contain a string that identifies or describes the LeakDetector resource.

2.5.69 LeakDetectorDisconnected

Example: Leak detector 'Rack #19 Rope' was disconnected.

Indicates that an external leak detector was disconnected.

• This message shall indicate that an external leak detector was disconnected.

Version Added: v1.3

Severity: Warning

Resolution: Check the leak detector connection or re-connect the leak detector.

Message and Arguments: "Leak detector '<1>' was disconnected."

1. string: The name or identifier of the leak detector.
   • This argument shall contain a string that identifies or describes the LeakDetector resource.

2.5.70 LeakDetectorFailure

Example: Leak detector 'Rack #19 Rope' failed.

Indicates that the service cannot communicate with a leak detector or detected a failure.

• This message shall indicate that the service is unable to communicate with a leak detector or otherwise detected a fault condition with the leak detector.

Version Added: v1.3

Severity: Warning

Resolution: Check the leak detector hardware or connection.

Message and Arguments: "Leak detector '<1>' failed."

1. string: The name or identifier of the leak detector.
   • This argument shall contain a string that identifies or describes the LeakDetector resource.

2.5.71 LeakDetectorRestored

Example: Leak detector 'Rack #42 Spot' was restored.

Indicates that a leak detector was repaired or communications were restored.

• This message shall indicate that the service is able to communicate with a leak detector that had previously failed, or the leak detector was repaired or replaced.

Version Added: v1.3

Severity: OK

Resolution: None.

Message and Arguments: "Leak detector '<1>' was restored."

1. string: The name or identifier of the leak detector.
   • This argument shall contain a string that identifies or describes the LeakDetector resource.

2.5.72 PressureAboveLowerCriticalThreshold

Example: Pressure 'Secondary TCS' reading of 671 kPa is now above the 650 lower critical threshold but remains outside of normal range.

Indicates that a pressure reading is no longer below the lower critical threshold but is still outside of normal operating range.

• This message shall indicate that a pressure reading, previously below the lower critical threshold, no longer violates the lower critical threshold. However, the pressure violates at least one lower threshold and is not within the normal operating range.

Version Added: v1.1

Severity: Warning

Resolution: Check the condition of the resource listed in OriginOfCondition.

Message and Arguments: "Pressure '<1>' reading of <2> kPa is now above the <3> lower critical threshold but remains outside of normal range."

1. string: The name or identifier of the pressure reading.
   • This argument shall contain a string that identifies or describes the location or physical context of the pressure reading.
2. number: The pressure in kilopascals.
   • This argument shall contain the pressure in kilopascals.
3. number: The threshold value.
   • This argument shall contain the value of the Reading property within the LowerCritical or LowerCriticalUser properties of the Sensor resource.

Note: This message is a more specific version of the following messages: SensorEvent.ReadingAboveLowerCriticalThreshold

2.5.73 PressureAboveLowerFatalThreshold

Example: Pressure 'Secondary TCS' reading of 528 kPa is now above the 450 lower fatal threshold but remains outside of normal range.

Indicates that a pressure reading is no longer below the lower fatal threshold but is still outside of normal operating range.

• This message shall indicate that a pressure reading, previously below the lower fatal threshold, no longer violates the lower fatal threshold. However, the pressure violates at least one lower threshold and is not within the normal operating range.

Version Added: v1.1

Severity: Critical

Resolution: Check the condition of the resource listed in OriginOfCondition.

Message and Arguments: "Pressure '<1>' reading of <2> kPa is now above the <3> lower fatal threshold but remains outside of normal range."

1. string: The name or identifier of the pressure reading.
   • This argument shall contain a string that identifies or describes the location or physical context of the pressure reading.
2. number: The pressure in kilopascals.
   • This argument shall contain the pressure in kilopascals.
3. number: The threshold value.
   • This argument shall contain the value of the Reading property within the LowerFatal property of the Sensor resource.

Note: This message is a more specific version of the following messages: SensorEvent.ReadingAboveLowerFatalThreshold

2.5.74 PressureAboveUpperCautionThreshold

Example: Pressure 'Facility Water System' reading of 928 kPa is above the 900 upper caution threshold.

Indicates that a pressure reading is above the upper caution threshold.

• This message shall indicate that a pressure reading violates an upper caution threshold. If the reading originates from a Sensor resource, the message shall indicate that the value of the Reading property is above the value of the Reading property within the UpperCaution or UpperCautionUser properties. Otherwise, the message shall indicate that the reading violates an internal level or threshold.

Version Added: v1.1

Severity: Warning

Resolution: Check the condition of the resource listed in OriginOfCondition.

Message and Arguments: "Pressure '<1>' reading of <2> kPa is above the <3> upper caution threshold."

1. string: The name or identifier of the pressure reading.
   • This argument shall contain a string that identifies or describes the location or physical context of the pressure reading.
2. number: The pressure in kilopascals.
   • This argument shall contain the pressure in kilopascals.
3. number: The threshold value.
   • If the reading originated from a Sensor resource, this argument shall contain the value of the Reading property within the UpperCaution or UpperCautionUser properties of the Sensor resource. Otherwise, this argument shall contain an internal level or threshold value.

Note: This message is a more specific version of the following messages: SensorEvent.ReadingAboveUpperCautionThreshold

2.5.75 PressureAboveUpperCriticalThreshold

Example: Pressure 'Facility Water System' reading of 1015 kPa is above the 1000 upper critical threshold.

Indicates that a pressure reading is above the upper critical threshold.

• This message shall indicate that a pressure reading violates an upper critical threshold. If the reading originates from a Sensor resource, the message shall indicate that the value of the Reading property is above the value of the Reading property within the UpperCritical or UpperCriticalUser properties.

Version Added: v1.1

Severity: Critical

Resolution: Check the condition of the resource listed in OriginOfCondition.

Message and Arguments: "Pressure '<1>' reading of <2> kPa is above the <3> upper critical threshold."

1. string: The name or identifier of the pressure reading.
   • This argument shall contain a string that identifies or describes the location or physical context of the pressure reading.
2. number: The pressure in kilopascals.
   • This argument shall contain the pressure in kilopascals.
3. number: The threshold value.
   • This argument shall contain the value of the Reading property within the UpperCritical or UpperCriticalUser properties of the Sensor resource.

Note: This message is a more specific version of the following messages: SensorEvent.ReadingAboveUpperCriticalThreshold

2.5.76 PressureAboveUpperFatalThreshold

Example: Pressure 'Facility Water System' reading of 1138 kPa is above the 1100 upper fatal threshold.

Indicates that a pressure reading is above the upper fatal threshold.

• This message shall indicate that a pressure reading violates an upper fatal threshold. If the reading originates from a Sensor resource, the message shall indicate that the value of the Reading property is above the value of the Reading property within the UpperFatal property.

Version Added: v1.1

Severity: Critical

Resolution: Check the condition of the resource listed in OriginOfCondition.

Message and Arguments: "Pressure '<1>' reading of <2> kPa is above the <3> upper fatal threshold."

1. string: The name or identifier of the pressure reading.
   • This argument shall contain a string that identifies or describes the location or physical context of the pressure reading.
2. number: The pressure in kilopascals.
   • This argument shall contain the pressure in kilopascals.
3. number: The threshold value.
   • This argument shall contain the value of the Reading property within the UpperFatal property of the Sensor resource.

Note: This message is a more specific version of the following messages: SensorEvent.ReadingAboveUpperFatalThreshold

2.5.77 PressureBelowLowerCautionThreshold

Example: Pressure 'Secondary TCS' reading of 689 kPa is below the 700 lower caution threshold.

Indicates that a pressure reading is below the lower caution threshold.

• This message shall indicate that a pressure reading violates a lower caution threshold. If the reading originates from a Sensor resource, the message shall indicate that the value of the Reading property is below the value of the Reading property within the LowerCaution or LowerCautionUser properties.

Version Added: v1.1

Severity: Warning

Resolution: Check the condition of the resource listed in OriginOfCondition.

Message and Arguments: "Pressure '<1>' reading of <2> kPa is below the <3> lower caution threshold."

1. string: The name or identifier of the pressure reading.
   • This argument shall contain a string that identifies or describes the location or physical context of the pressure reading.
2. number: The pressure in kilopascals.
   • This argument shall contain the pressure in kilopascals.
3. number: The threshold value.
   • This argument shall contain the value of the Reading property within the LowerCaution or LowerCautionUser properties of the Sensor resource.

Note: This message is a more specific version of the following messages: SensorEvent.ReadingBelowLowerCautionThreshold

2.5.78 PressureBelowLowerCriticalThreshold

Example: Pressure 'Secondary TCS' reading of 541 kPa is below the 600 lower critical threshold.

Indicates that a pressure reading is below the lower critical threshold.

• This message shall indicate that a pressure reading violates a lower critical threshold. If the reading originates from a Sensor resource, the message shall indicate that the value of the Reading property is below the value of the Reading property within the LowerCritical or LowerCriticalUser properties.

Version Added: v1.1

Severity: Critical

Resolution: Check the condition of the resource listed in OriginOfCondition.

Message and Arguments: "Pressure '<1>' reading of <2> kPa is below the <3> lower critical threshold."

1. string: The name or identifier of the pressure reading.
   • This argument shall contain a string that identifies or describes the location or physical context of the pressure reading.
2. number: The pressure in kilopascals.
   • This argument shall contain the pressure in kilopascals.
3. number: The threshold value.
   • This argument shall contain the value of the Reading property within the LowerCritical or LowerCriticalUser properties of the Sensor resource.

Note: This message is a more specific version of the following messages: SensorEvent.ReadingBelowLowerCriticalThreshold

2.5.79 PressureBelowLowerFatalThreshold

Example: Pressure 'Secondary TCS' reading of 389 kPa is below the 450 lower fatal threshold.

Indicates that a pressure reading is below the lower fatal threshold.

• This message shall indicate that a pressure reading violates a lower fatal threshold. If the reading originates from a Sensor resource, the message shall indicate that the value of the Reading property is below the value of the Reading property within the LowerFatal property.

Version Added: v1.1

Severity: Critical

Resolution: Check the condition of the resource listed in OriginOfCondition.

Message and Arguments: "Pressure '<1>' reading of <2> kPa is below the <3> lower fatal threshold."

1. string: The name or identifier of the pressure reading.
   • This argument shall contain a string that identifies or describes the location or physical context of the pressure reading.
2. number: The pressure in kilopascals.
   • This argument shall contain the pressure in kilopascals.
3. number: The threshold value.
   • This argument shall contain the value of the Reading property within the LowerFatal property of the Sensor resource.

Note: This message is a more specific version of the following messages: SensorEvent.ReadingBelowLowerFatalThreshold

2.5.80 PressureBelowUpperCriticalThreshold

Example: Pressure 'Facility Water System' reading of 937 kPa is now below the 1000 upper critical threshold but remains outside of normal range.

Indicates that a pressure reading is no longer above the upper critical threshold but is still outside of normal operating range.

• This message shall indicate that a pressure reading, previously above the upper critical threshold, no longer violates the upper critical threshold. However, the pressure violates at least one upper threshold and is not within the normal operating range.

Version Added: v1.1

Severity: Warning

Resolution: Check the condition of the resource listed in OriginOfCondition.

Message and Arguments: "Pressure '<1>' reading of <2> kPa is now below the <3> upper critical threshold but remains outside of normal range."

1. string: The name or identifier of the pressure reading.
   • This argument shall contain a string that identifies or describes the location or physical context of the pressure reading.
2. number: The pressure in kilopascals.
   • This argument shall contain the pressure in kilopascals.
3. number: The threshold value.
   • This argument shall contain the value of the Reading property within the UpperCritical or UpperCriticalUser properties of the Sensor resource.

Note: This message is a more specific version of the following messages: SensorEvent.ReadingBelowUpperCriticalThreshold

2.5.81 PressureBelowUpperFatalThreshold

Example: Pressure 'Facility Water System' reading of 1019 kPa is now below the 1100 upper fatal threshold but remains outside of normal range.

Indicates that a pressure reading is no longer above the upper fatal threshold but is still outside of normal operating range.

• This message shall indicate that a pressure reading, previously above the upper fatal threshold, no longer violates the upper fatal threshold. However, the pressure violates at least one upper threshold and is not within the normal operating range.

Version Added: v1.1

Severity: Critical

Resolution: Check the condition of the resource listed in OriginOfCondition.

Message and Arguments: "Pressure '<1>' reading of <2> kPa is now below the <3> upper fatal threshold but remains outside of normal range."

1. string: The name or identifier of the pressure reading.
   • This argument shall contain a string that identifies or describes the location or physical context of the pressure reading.
2. number: The pressure in kilopascals.
   • This argument shall contain the pressure in kilopascals.
3. number: The threshold value.
   • This argument shall contain the value of the Reading property within the UpperFatal property of the Sensor resource.

Note: This message is a more specific version of the following messages: SensorEvent.ReadingBelowUpperFatalThreshold

2.5.82 PressureCritical

Example: Pressure 'Facility Water System' reading of 1026 kPa exceeds the critical level.

Indicates that a pressure reading exceeds an internal critical level.

• This message shall indicate that a pressure reading violates an internal critical level. This message shall be used for pressure properties or Sensor resources that implement boolean trip points for a critical limit, such as from hardware mechanisms with no threshold value. The pressure properties or Sensor resources may contain readable thresholds that coexist with this unspecified trip point.

Version Added: v1.1

Severity: Critical

Resolution: Check the condition of the resource listed in OriginOfCondition.

Message and Arguments: "Pressure '<1>' reading of <2> kPa exceeds the critical level."

1. string: The name or identifier of the pressure reading.
   • This argument shall contain a string that identifies or describes the location or physical context of the pressure reading.
2. number: The pressure in kilopascals.
   • This argument shall contain the pressure in kilopascals.

Note: This message is a more specific version of the following messages: SensorEvent.ReadingCritical

2.5.83 PressureNoLongerCritical

Example: Pressure 'Facility Water System' reading of 987 kPa no longer violates the critical level.

Indicates that a pressure reading no longer violates an internal critical level but still violates an internal warning level.

• This message shall indicate that a pressure reading no longer violates an internal critical level but still violates an internal warning level. This message shall be used for pressure properties or Sensor resources that implement boolean trip points for a critical limit, such as from hardware mechanisms with no threshold value. The pressure properties or Sensor resources may contain readable thresholds that coexist with this unspecified trip point.

Version Added: v1.1

Severity: Warning

Resolution: Check the condition of the resource listed in OriginOfCondition.

Message and Arguments: "Pressure '<1>' reading of <2> kPa no longer violates the critical level."

1. string: The name or identifier of the pressure reading.
   • This argument shall contain a string that identifies or describes the location or physical context of the pressure reading.
2. number: The pressure in kilopascals.
   • This argument shall contain the pressure in kilopascals.

Note: This message is a more specific version of the following messages: SensorEvent.ReadingNoLongerCritical

2.5.84 PressureNormal

Example: Pressure 'Facility Water System' reading of 781 kPa is within normal operating range.

Indicates that a pressure reading is now within normal operating range.

• This message shall indicate that a pressure reading has returned to its normal operating range.

Version Added: v1.1

Severity: OK

Resolution: None.

Message and Arguments: "Pressure '<1>' reading of <2> kPa is within normal operating range."

1. string: The name or identifier of the pressure reading.
   • This argument shall contain a string that identifies or describes the location or physical context of the pressure reading.
2. number: The pressure in kilopascals.
   • This argument shall contain the pressure in kilopascals.

Note: This message is a more specific version of the following messages: SensorEvent.SensorReadingNormalRange

2.5.85 PressureWarning

Example: Pressure 'Facility Water System' reading of 972 kPa exceeds the warning level.

Indicates that a pressure reading exceeds an internal warning level.

• This message shall indicate that a pressure reading violates an internal warning level. This message shall be used for pressure properties or Sensor resources that implement boolean trip points for a caution limit, such as from hardware mechanisms with no threshold value. The pressure properties or Sensor resources may contain readable thresholds that coexist with this unspecified trip point.

Version Added: v1.1

Severity: Warning

Resolution: Check the condition of the resource listed in OriginOfCondition.

Message and Arguments: "Pressure '<1>' reading of <2> kPa exceeds the warning level."

1. string: The name or identifier of the pressure reading.
   • This argument shall contain a string that identifies or describes the location or physical context of the pressure reading.
2. number: The pressure in kilopascals.
   • This argument shall contain the pressure in kilopascals.

Note: This message is a more specific version of the following messages: SensorEvent.ReadingWarning

2.5.86 PrimaryCoolantConnectorSubsystemHealth

Example: The primary coolant connector subsystem health is OK.

Indicates the health of the primary coolant connector subsystem for the equipment.

• This message shall indicate the health of the primary coolant connector subsystem for the equipment.

Version Added: v1.2

Severity: OK

Resolution: None.

Message and Arguments: "The primary coolant connector subsystem health is <1>."

1. string: The health of the primary coolant connector subsystem for the equipment.
   • This argument shall contain the health of the primary coolant connector subsystem for the equipment. This argument shall contain a value defined by the Health enumeration in the Resource schema.

2.5.87 PumpFailed

Example: Pump 'Output #3' has failed.

Indicates that a pump has failed.

• This message shall indicate that a pump has failed.

Version Added: v1.1

Severity: Critical

Resolution: Check the pump hardware and replace any faulty component.

Message and Arguments: "Pump '<1>' has failed."

1. string: The name or identifier of the pump.
   • This argument shall contain a string that identifies or describes the Pump resource.

Note: This message is a more specific version of the following messages: ResourceEvent.ResourceStatusChangedCritical

2.5.88 PumpInserted

Example: Pump 'Output #3' was inserted.

Indicates that a pump was inserted or installed.

• This message shall indicate that a pump was inserted or installed.

Version Added: v1.1

Severity: OK

Resolution: None.

Message and Arguments: "Pump '<1>' was inserted."

1. string: The name or identifier of the pump.
   • This argument shall contain a string that identifies or describes the Pump resource.

Note: This message is a more specific version of the following messages: ResourceEvent.ResourceStateChanged

2.5.89 PumpRemoved

Example: Pump 'Output #3' was removed.

Indicates that a pump was removed.

• This message shall indicate that a pump was removed.

Version Added: v1.1

Severity: OK

Resolution: None.

Message and Arguments: "Pump '<1>' was removed."

1. string: The name or identifier of the pump.
   • This argument shall contain a string that identifies or describes the Pump resource.

Note: This message is a more specific version of the following messages: ResourceEvent.ResourceStateChanged

2.5.90 PumpRestored

Example: Pump 'Output #3' was restored.

Indicates that a pump was repaired or restored to normal operation.

• This message shall indicate that a pump was repaired, replaced, or otherwise returned to normal operation.

Version Added: v1.1

Severity: OK

Resolution: None.

Message and Arguments: "Pump '<1>' was restored."

1. string: The name or identifier of the pump.
   • This argument shall contain a string that identifies or describes the Pump resource.

Note: This message is a more specific version of the following messages: ResourceEvent.ResourceStatusChangedOK

2.5.91 PumpSubsystemHealth

Example: The pump subsystem health is Critical.

Indicates the health of the pump subsystem for the equipment.

• This message shall indicate the health of the pump subsystem for the equipment.

Version Added: v1.2

Severity: OK

Resolution: None.

Message and Arguments: "The pump subsystem health is <1>."

1. string: The health of the pump subsystem for the equipment.
   • This argument shall contain the health of the pump subsystem for the equipment. This argument shall contain a value defined by the Health enumeration in the Resource schema.

2.5.92 ReservoirSubsystemHealth

Example: The reservoir subsystem health is Warning.

Indicates the health of the reservoir subsystem for the equipment.

• This message shall indicate the health of the reservoir subsystem for the equipment.

Version Added: v1.2

Severity: OK

Resolution: None.

Message and Arguments: "The reservoir subsystem health is <1>."

1. string: The health of the reservoir subsystem for the equipment.
   • This argument shall contain the health of the reservoir subsystem for the equipment. This argument shall contain a value defined by the Health enumeration in the Resource schema.

2.5.93 SecondaryCoolantConnectorSubsystemHealth

Example: The secondary coolant connector subsystem health is Critical.

Indicates the health of the secondary coolant connector subsystem for the equipment.

• This message shall indicate the health of the secondary coolant connector subsystem for the equipment.

Version Added: v1.2

Severity: OK

Resolution: None.

Message and Arguments: "The secondary coolant connector subsystem health is <1>."

1. string: The health of the secondary coolant connector subsystem for the equipment.
   • This argument shall contain the health of the secondary coolant connector subsystem for the equipment. This argument shall contain a value defined by the Health enumeration in the Resource schema.

2.5.94 TemperatureAboveLowerCriticalThreshold

Example: Temperature 'Facility Water Supply' reading of 16.1 degrees (C) is now above the 15 lower critical threshold but remains outside of normal range.

Indicates that a temperature reading is no longer below the lower critical threshold but is still outside of normal operating range.

• This message shall indicate that a temperature reading, previously below the lower critical threshold, no longer violates the lower critical threshold. However, the temperature violates at least one lower threshold and is not within the normal operating range.

Version Added: v1.0

Severity: Warning

Resolution: Check the condition of the resource listed in OriginOfCondition.

Message and Arguments: "Temperature '<1>' reading of <2> degrees (C) is now above the <3> lower critical threshold but remains outside of normal range."

1. string: The name or identifier of the temperature reading.
   • This argument shall contain a string that identifies or describes the location or physical context of the temperature reading.
2. number: The temperature in degrees Celsius.
   • This argument shall contain the temperature in degrees Celsius.
3. number: The threshold value.
   • This argument shall contain the value of the Reading property within the LowerCritical or LowerCriticalUser properties of the Sensor resource.

Note: This message is a more specific version of the following messages: SensorEvent.ReadingAboveLowerCriticalThreshold

2.5.95 TemperatureAboveLowerFatalThreshold

Example: Temperature 'Facility Water Supply' reading of 10.7 degrees (C) is now above the 10 lower fatal threshold but remains outside of normal range.

Indicates that a temperature reading is no longer below the lower fatal threshold but is still outside of normal operating range.

• This message shall indicate that a temperature reading, previously below the lower fatal threshold, no longer violates the lower fatal threshold. However, the temperature violates at least one lower threshold and is not within the normal operating range.

Version Added: v1.0

Severity: Critical

Resolution: Check the condition of the resource listed in OriginOfCondition.

Message and Arguments: "Temperature '<1>' reading of <2> degrees (C) is now above the <3> lower fatal threshold but remains outside of normal range."

1. string: The name or identifier of the temperature reading.
   • This argument shall contain a string that identifies or describes the location or physical context of the temperature reading.
2. number: The temperature in degrees Celsius.
   • This argument shall contain the temperature in degrees Celsius.
3. number: The threshold value.
   • This argument shall contain the value of the Reading property within the LowerFatal property of the Sensor resource.

Note: This message is a more specific version of the following messages: SensorEvent.ReadingAboveLowerFatalThreshold

2.5.96 TemperatureAboveUpperCautionThreshold

Example: Temperature 'CPU1' reading of 43.8 degrees (C) is above the 42 upper caution threshold.

Indicates that a temperature reading is above the upper caution threshold.

• This message shall indicate that a temperature reading violates an upper caution threshold. If the reading originates from a Sensor resource, the message shall indicate that the value of the Reading property is above the value of the Reading property within the UpperCaution or UpperCautionUser properties. Otherwise, the message shall indicate that the reading violates an internal level or threshold.

Version Added: v1.0

Severity: Warning

Resolution: Check the condition of the resource listed in OriginOfCondition.

Message and Arguments: "Temperature '<1>' reading of <2> degrees (C) is above the <3> upper caution threshold."

1. string: The name or identifier of the temperature reading.
   • This argument shall contain a string that identifies or describes the location or physical context of the temperature reading.
2. number: The temperature in degrees Celsius.
   • This argument shall contain the temperature in degrees Celsius.
3. number: The threshold value.
   • If the reading originated from a Sensor resource, this argument shall contain the value of the Reading property within the UpperCaution or UpperCautionUser properties of the Sensor resource. Otherwise, this argument shall contain an internal level or threshold value.

Note: This message is a more specific version of the following messages: SensorEvent.ReadingAboveUpperCautionThreshold

2.5.97 TemperatureAboveUpperCriticalThreshold

Example: Temperature 'CPU1' reading of 47.4 degrees (C) is above the 45 upper critical threshold.

Indicates that a temperature reading is above the upper critical threshold.

• This message shall indicate that a temperature reading violates an upper critical threshold. If the reading originates from a Sensor resource, the message shall indicate that the value of the Reading property is above the value of the Reading property within the UpperCritical or UpperCriticalUser properties.

Version Added: v1.0

Severity: Critical

Resolution: Check the condition of the resource listed in OriginOfCondition.

Message and Arguments: "Temperature '<1>' reading of <2> degrees (C) is above the <3> upper critical threshold."

1. string: The name or identifier of the temperature reading.
   • This argument shall contain a string that identifies or describes the location or physical context of the temperature reading.
2. number: The temperature in degrees Celsius.
   • This argument shall contain the temperature in degrees Celsius.
3. number: The threshold value.
   • This argument shall contain the value of the Reading property within the UpperCritical or UpperCriticalUser properties of the Sensor resource.

Note: This message is a more specific version of the following messages: SensorEvent.ReadingAboveUpperCriticalThreshold

2.5.98 TemperatureAboveUpperFatalThreshold

Example: Temperature 'CPU1' reading of 50.5 degrees (C) is above the 50 upper fatal threshold.

Indicates that a temperature reading is above the upper fatal threshold.

• This message shall indicate that a temperature reading violates an upper fatal threshold. If the reading originates from a Sensor resource, the message shall indicate that the value of the Reading property is above the value of the Reading property within the UpperFatal property.

Version Added: v1.0

Severity: Critical

Resolution: Check the condition of the resource listed in OriginOfCondition.

Message and Arguments: "Temperature '<1>' reading of <2> degrees (C) is above the <3> upper fatal threshold."

1. string: The name or identifier of the temperature reading.
   • This argument shall contain a string that identifies or describes the location or physical context of the temperature reading.
2. number: The temperature in degrees Celsius.
   • This argument shall contain the temperature in degrees Celsius.
3. number: The threshold value.
   • This argument shall contain the value of the Reading property within the UpperFatal property of the Sensor resource.

Note: This message is a more specific version of the following messages: SensorEvent.ReadingAboveUpperFatalThreshold

2.5.99 TemperatureBelowLowerCautionThreshold

Example: Temperature 'Facility Water Supply' reading of 14.7 degrees (C) is below the 15 lower caution threshold.

Indicates that a temperature reading is below the lower caution threshold.

• This message shall indicate that a temperature reading violates a lower caution threshold. If the reading originates from a Sensor resource, the message shall indicate that the value of the Reading property is below the value of the Reading property within the LowerCaution or LowerCautionUser properties.

Version Added: v1.0

Severity: Warning

Resolution: Check the condition of the resource listed in OriginOfCondition.

Message and Arguments: "Temperature '<1>' reading of <2> degrees (C) is below the <3> lower caution threshold."

1. string: The name or identifier of the temperature reading.
   • This argument shall contain a string that identifies or describes the location or physical context of the temperature reading.
2. number: The temperature in degrees Celsius.
   • This argument shall contain the temperature in degrees Celsius.
3. number: The threshold value.
   • This argument shall contain the value of the Reading property within the LowerCaution or LowerCautionUser properties of the Sensor resource.

Note: This message is a more specific version of the following messages: SensorEvent.ReadingBelowLowerCautionThreshold

2.5.100 TemperatureBelowLowerCriticalThreshold

Example: Temperature 'Facility Water Supply' reading of 11.8 degrees (C) is below the lower critical threshold.

Indicates that a temperature reading is below the lower critical threshold.

• This message shall indicate that a temperature reading violates a lower critical threshold. If the reading originates from a Sensor resource, the message shall indicate that the value of the Reading property is below the value of the Reading property within the LowerCritical or LowerCriticalUser properties.

Version Added: v1.0

Severity: Critical

Resolution: Check the condition of the resource listed in OriginOfCondition.

Message and Arguments: "Temperature '<1>' reading of <2> degrees (C) is below the <3> lower critical threshold."

1. string: The name or identifier of the temperature reading.
   • This argument shall contain a string that identifies or describes the location or physical context of the temperature reading.
2. number: The temperature in degrees Celsius.
   • This argument shall contain the temperature in degrees Celsius.
3. number: The threshold value.
   • This argument shall contain the value of the Reading property within the LowerCritical or LowerCriticalUser properties of the Sensor resource.

Note: This message is a more specific version of the following messages: SensorEvent.ReadingBelowLowerCriticalThreshold

2.5.101 TemperatureBelowLowerFatalThreshold

Example: Temperature 'Facility Water Supply' reading of 9.6 degrees (C) is below the 10 lower fatal threshold.

Indicates that a temperature reading is below the lower fatal threshold.

• This message shall indicate that a temperature reading violates a lower fatal threshold. If the reading originates from a Sensor resource, the message shall indicate that the value of the Reading property is below the value of the Reading property within the LowerFatal property.

Version Added: v1.0

Severity: Critical

Resolution: Check the condition of the resource listed in OriginOfCondition.

Message and Arguments: "Temperature '<1>' reading of <2> degrees (C) is below the <3> lower fatal threshold."

1. string: The name or identifier of the temperature reading.
   • This argument shall contain a string that identifies or describes the location or physical context of the temperature reading.
2. number: The temperature in degrees Celsius.
   • This argument shall contain the temperature in degrees Celsius.
3. number: The threshold value.
   • This argument shall contain the value of the Reading property within the LowerFatal property of the Sensor resource.

Note: This message is a more specific version of the following messages: SensorEvent.ReadingBelowLowerFatalThreshold

2.5.102 TemperatureBelowUpperCriticalThreshold

Example: Temperature 'CPU1' reading of 44.1 degrees (C) is now below the 45 upper critical threshold but remains outside of normal range.

Indicates that a temperature reading is no longer above the upper critical threshold but is still outside of normal operating range.

• This message shall indicate that a temperature reading, previously above the upper critical threshold, no longer violates the upper critical threshold. However, the temperature violates at least one upper threshold and is not within the normal operating range.

Version Added: v1.0

Severity: Warning

Resolution: Check the condition of the resource listed in OriginOfCondition.

Message and Arguments: "Temperature '<1>' reading of <2> degrees (C) is now below the <3> upper critical threshold but remains outside of normal range."

1. string: The name or identifier of the temperature reading.
   • This argument shall contain a string that identifies or describes the location or physical context of the temperature reading.
2. number: The temperature in degrees Celsius.
   • This argument shall contain the temperature in degrees Celsius.
3. number: The threshold value.
   • This argument shall contain the value of the Reading property within the UpperCritical or UpperCriticalUser properties of the Sensor resource.

Note: This message is a more specific version of the following messages: SensorEvent.ReadingBelowUpperCriticalThreshold

2.5.103 TemperatureBelowUpperFatalThreshold

Example: Temperature 'CPU1' reading of 49.5 degrees (C) is now below the 50 upper fatal threshold but remains outside of normal range.

Indicates that a temperature reading is no longer above the upper fatal threshold but is still outside of normal operating range.

• This message shall indicate that a temperature reading, previously above the upper fatal threshold, no longer violates the upper fatal threshold. However, the temperature violates at least one upper threshold and is not within the normal operating range.

Version Added: v1.0

Severity: Critical

Resolution: Check the condition of the resource listed in OriginOfCondition.

Message and Arguments: "Temperature '<1>' reading of <2> degrees (C) is now below the <3> upper fatal threshold but remains outside of normal range."

1. string: The name or identifier of the temperature reading.
   • This argument shall contain a string that identifies or describes the location or physical context of the temperature reading.
2. number: The temperature in degrees Celsius.
   • This argument shall contain the temperature in degrees Celsius.
3. number: The threshold value.
   • This argument shall contain the value of the Reading property within the UpperFatal property of the Sensor resource.

Note: This message is a more specific version of the following messages: SensorEvent.ReadingBelowUpperFatalThreshold