PowerEdge Servers Error and Event Messages Reference Guide

CUPD—Firmware Event Messages

CUPD0201

NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the Applicable Event or Alert Types section.

Message: Unable to update catalog because the repository type cannot be changed to another repository type.
Detailed Description: The catalog cannot be updated because the repository type cannot be changed to another repository type.
Recommended Response Action: Make sure the entered repository type matches the existing repository type and retry the operation.
Category: Updates (CUPD = Firmware)
Severity: Warning
Redfish Event Type: Not Applicable
Applicable Event or Alert Types: No alerts are applicable for this message

CUPD3010

NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the Applicable Event or Alert Types section.

Message: Unable to download the catalog file.
Detailed Description: The catalog file cannot be downloaded because an error occurred.
Recommended Response Action: Make sure the remote repository is available and retry the operation.
Category: Updates (CUPD = Firmware)
Severity: Critical
Redfish Event Type: Not Applicable
Applicable Event or Alert Types: No alerts are applicable for this message

CUPD3013

NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the Applicable Event or Alert Types section.

Message: Unable to retrieve catalogs from the database.
Detailed Description: Catalog data cannot be retrieved because an error occurred.
Recommended Response Action: Retry the operation. If the issue persists, contact your system administrator.
Category: Updates (CUPD = Firmware)
Severity: Critical
Redfish Event Type: Not Applicable
Applicable Event or Alert Types: No alerts are applicable for this message

CUPD3014

NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the Applicable Event or Alert Types section.

Message: Unable to create or update baseline.
Detailed Description: The baseline cannot be created or updated because an error occurred.
Recommended Response Action: Make sure the entered baseline information is valid and retry the operation. If the issue persists, contact your system administrator.
Category: Updates (CUPD = Firmware)
Severity: Critical
Redfish Event Type: Not Applicable
Applicable Event or Alert Types: No alerts are applicable for this message

CUPD3015

NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the Applicable Event or Alert Types section.

Message: Unable to create the repository.
Detailed Description: The repository cannot be created because an error occurred.
Recommended Response Action: Make sure the entered repository information is valid and retry the operation. If the issue persists, contact your system administrator.
Category: Updates (CUPD = Firmware)
Severity: Critical
Redfish Event Type: Not Applicable
Applicable Event or Alert Types: No alerts are applicable for this message

CUPD3016

NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the Applicable Event or Alert Types section.

Message: Unable to retrieve device information for the baseline ID entered.
Detailed Description: The device information cannot be retrieved for the provided baseline ID.
Recommended Response Action: Make sure the provided baseline ID is valid and retry the operation.
Category: Updates (CUPD = Firmware)
Severity: Critical
Redfish Event Type: Not Applicable
Applicable Event or Alert Types: No alerts are applicable for this message

CUPD3018

NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the Applicable Event or Alert Types section.

Message: Unable to retrieve catalog details because the entered catalog ID does not exist.
Detailed Description: Catalog information cannot be retrieved because the entered catalog ID does not exist.
Recommended Response Action: Enter a valid catalog ID and retry the operation.
Category: Updates (CUPD = Firmware)
Severity: Warning
Redfish Event Type: Not Applicable
Applicable Event or Alert Types: No alerts are applicable for this message

CUPD3019

NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the Applicable Event or Alert Types section.

Message: Unable to create a catalog with the provided parameters.
Detailed Description: The catalog cannot be created.
Recommended Response Action: Make sure the entered catalog information is valid and retry the operation. If the issue persists, contact your system administrator.
Category: Updates (CUPD = Firmware)
Severity: Critical
Redfish Event Type: Not Applicable
Applicable Event or Alert Types: No alerts are applicable for this message

CUPD3020

NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the Applicable Event or Alert Types section.

Message: Unable to update catalog because the entered catalog ID does not exist.
Detailed Description: The catalog cannot be updated because the provided catalog ID does not exist.
Recommended Response Action: Provide a valid catalog ID and retry the operation.
Category: Updates (CUPD = Firmware)
Severity: Critical
Redfish Event Type: Not Applicable
Applicable Event or Alert Types: No alerts are applicable for this message

CUPD3021

NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the Applicable Event or Alert Types section.

Message: The entered catalog(s) cannot be deleted.
Detailed Description: The catalog(s) cannot be deleted either because the catalog job(s) are currently running or the entered catalog ID(s) do not exist.
Recommended Response Action: Make sure that the catalog ID(s) are valid and not currently running and retry the operation.
Category: Updates (CUPD = Firmware)
Severity: Critical
Redfish Event Type: Not Applicable
Applicable Event or Alert Types: No alerts are applicable for this message

CUPD3022

NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the Applicable Event or Alert Types section.

Message: Unable to retrieve baseline information.
Detailed Description: Unable to retrieve baseline information because an error occurred.
Recommended Response Action: Retry the operation. If the issue persists, contact your system administrator.
Category: Updates (CUPD = Firmware)
Severity: Critical
Redfish Event Type: Not Applicable
Applicable Event or Alert Types: No alerts are applicable for this message

CUPD3023

NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the Applicable Event or Alert Types section.

Message: Unable to retrieve device information for the provided baseline ID.
Detailed Description: Device information cannot be retrieved for the provided baseline ID.
Recommended Response Action: Make sure the provided baseline ID is valid and retry the operation.
Category: Updates (CUPD = Firmware)
Severity: Critical
Redfish Event Type: Not Applicable
Applicable Event or Alert Types: No alerts are applicable for this message

CUPD3024

NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the Applicable Event or Alert Types section.

Message: Unable to retrieve component information for the provided baseline and device IDs.
Detailed Description: Component information cannot be retrieved for the provided baseline and device IDs.
Recommended Response Action: Make sure the provided baseline and device IDs are valid and retry the operation.
Category: Updates (CUPD = Firmware)
Severity: Critical
Redfish Event Type: Not Applicable
Applicable Event or Alert Types: No alerts are applicable for this message

CUPD3025

NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the Applicable Event or Alert Types section.

Message: Unable to create or update baseline because the entered target ID is invalid.
Detailed Description: The baseline cannot be created or updated because the entered target ID is invalid.
Recommended Response Action: Enter a valid target ID and retry the operation.
Category: Updates (CUPD = Firmware)
Severity: Critical
Redfish Event Type: Not Applicable
Applicable Event or Alert Types: No alerts are applicable for this message

CUPD3026

NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the Applicable Event or Alert Types section.

Message: The entered baseline(s) cannot be deleted.
Detailed Description: The baseline(s) cannot be deleted either because the baseline(s) are running or the baseline ID(s) are invalid.
Recommended Response Action: Make sure the entered ID(s) are valid and not currently running and retry the operation.
Category: Updates (CUPD = Firmware)
Severity: Critical
Redfish Event Type: Not Applicable
Applicable Event or Alert Types: No alerts are applicable for this message

CUPD3027

NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the Applicable Event or Alert Types section.

Message: Unable to retrieve catalog information using the entered repository ID.
Detailed Description: Catalog information cannot be retrieved using the entered repository ID.
Recommended Response Action: Make the sure the entered repository ID is valid and retry the operation.
Category: Updates (CUPD = Firmware)
Severity: Critical
Redfish Event Type: Not Applicable
Applicable Event or Alert Types: No alerts are applicable for this message

CUPD3028

NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the Applicable Event or Alert Types section.

Message: Unable to retrieve baseline information using the entered job ID.
Detailed Description: Baseline information cannot be retrieved using the entered job ID.
Recommended Response Action: Make sure the entered job ID is valid and retry the operation.
Category: Updates (CUPD = Firmware)
Severity: Critical
Redfish Event Type: Not Applicable
Applicable Event or Alert Types: No alerts are applicable for this message

CUPD3032

NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the Applicable Event or Alert Types section.

Message: Unable to update catalog because the catalog ID entered does not exist.
Detailed Description: The catalog cannot be updated because the catalog ID provided does not exist.
Recommended Response Action: Enter a valid catalog ID and retry the operation.
Category: Updates (CUPD = Firmware)
Severity: Critical
Redfish Event Type: Not Applicable
Applicable Event or Alert Types: No alerts are applicable for this message

CUPD3033

NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the Applicable Event or Alert Types section.

Message: Unable to create the update job because the baseline ID entered exceeds the maximum allowed length.
Detailed Description: The update job cannot be created because the baseline ID entered exceeds the maximum limit of 255 characters.
Recommended Response Action: Enter a baseline ID less than 255 characters and retry the operation.
Category: Updates (CUPD = Firmware)
Severity: Critical
Redfish Event Type: Not Applicable
Applicable Event or Alert Types: No alerts are applicable for this message

CUPD3034

NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the Applicable Event or Alert Types section.

Message: Unable to create the update job because the entered connection profile name exceeds the maximum allowed length.
Detailed Description: The update job cannot be created because the entered connection profile name exceeds the maximum limit of 255 characters.
Recommended Response Action: Enter a connection profile name less than 255 characters and retry the operation.
Category: Updates (CUPD = Firmware)
Severity: Critical
Redfish Event Type: Not Applicable
Applicable Event or Alert Types: No alerts are applicable for this message

CUPD3035

NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the Applicable Event or Alert Types section.

Message: Unable to create the update job because the entered repository ID exceeds the maximum allowed length.
Detailed Description: The update job cannot be created because the entered repository ID exceeds the maximum limit of 255 characters.
Recommended Response Action: Enter a repository ID less than 255 characters and retry the operation.
Category: Updates (CUPD = Firmware)
Severity: Critical
Redfish Event Type: Not Applicable
Applicable Event or Alert Types: No alerts are applicable for this message

CUPD3036

NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the Applicable Event or Alert Types section.

Message: Unable to create the update job because the entered catalog ID exceeds the maximum allowed length.
Detailed Description: The update job cannot be created because the entered catalog ID exceeds the maximum limit of 255 characters.
Recommended Response Action: Enter a catalog ID less than 255 characters and retry the operation.
Category: Updates (CUPD = Firmware)
Severity: Critical
Redfish Event Type: Not Applicable
Applicable Event or Alert Types: No alerts are applicable for this message

CUPD3037

NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the Applicable Event or Alert Types section.

Message: Unable to create the update job because the entered operation name exceeds the maximum allowed length.
Detailed Description: The update job cannot be created because the entered operation name exceeds the maximum limit of 255 characters.
Recommended Response Action: Enter an operation name less than 255 characters and retry the operation.
Category: Updates (CUPD = Firmware)
Severity: Critical
Redfish Event Type: Not Applicable
Applicable Event or Alert Types: No alerts are applicable for this message

CUPD3038

NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the Applicable Event or Alert Types section.

Message: Unable to create the update job because the entered operation name is invalid.
Detailed Description: The update job cannot be created because the entered operation name is invalid.
Recommended Response Action: Enter a valid operation name and retry the operation.
Category: Updates (CUPD = Firmware)
Severity: Critical
Redfish Event Type: Not Applicable
Applicable Event or Alert Types: No alerts are applicable for this message

CUPD3039

NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the Applicable Event or Alert Types section.

Message: Unable to create the update job because the entered Compliance Update value exceeds the maximum allowed length.
Detailed Description: The update job cannot be created because the entered Compliance Update value exceeds the maximum limit of 255 characters.
Recommended Response Action: Enter a Compliance Update value less than 255 characters and retry the operation.
Category: Updates (CUPD = Firmware)
Severity: Critical
Redfish Event Type: Not Applicable
Applicable Event or Alert Types: No alerts are applicable for this message

CUPD3040

NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the Applicable Event or Alert Types section.

Message: Unable to create the update job because the entered Compliance Update value is invalid.
Detailed Description: The update job cannot be created because the entered Compliance Update value is invalid.
Recommended Response Action: Make sure the entered Compliance Update value is true or false and retry the operation.
Category: Updates (CUPD = Firmware)
Severity: Critical
Redfish Event Type: Not Applicable
Applicable Event or Alert Types: No alerts are applicable for this message

CUPD3041

NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the Applicable Event or Alert Types section.

Message: Unable to create the update job because the entered Sign Verify value exceeds the maximum allowed length.
Detailed Description: The update job cannot be created because the entered Sign Verify value exceeds the maximum limit of 255 characters.
Recommended Response Action: Enter a Sign Verify value less than 255 characters and retry the operation.
Category: Updates (CUPD = Firmware)
Severity: Critical
Redfish Event Type: Not Applicable
Applicable Event or Alert Types: No alerts are applicable for this message

CUPD3042

NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the Applicable Event or Alert Types section.

Message: Unable to create the update job because the entered signVerify value is invalid.
Detailed Description: The update job cannot be created because the entered signVerify value is invalid.
Recommended Response Action: Make sure the entered signVerify value is true or false and retry the operation.
Category: Updates (CUPD = Firmware)
Severity: Critical
Redfish Event Type: Not Applicable
Applicable Event or Alert Types: No alerts are applicable for this message

CUPD3043

NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the Applicable Event or Alert Types section.

Message: Unable to create the update job because the entered Staging value exceeds the maximum allowed length.
Detailed Description: The update job cannot be created because the entered Staging value exceeds the maximum limit of 255 characters.
Recommended Response Action: Enter a Staging value less than 255 characters and retry the operation.
Category: Updates (CUPD = Firmware)
Severity: Critical
Redfish Event Type: Not Applicable
Applicable Event or Alert Types: No alerts are applicable for this message

CUPD3044

NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the Applicable Event or Alert Types section.

Message: Unable to create the update job because the entered Staging value is invalid.
Detailed Description: The update job cannot be created because the entered Staging value is invalid.
Recommended Response Action: Make sure the entered Staging value is true or false and retry the operation.
Category: Updates (CUPD = Firmware)
Severity: Critical
Redfish Event Type: Not Applicable
Applicable Event or Alert Types: No alerts are applicable for this message

CUPD3045

NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the Applicable Event or Alert Types section.

Message: Unable to create the update job because the provided job parameters are empty.
Detailed Description: The update job cannot be created because the entered job parameters are empty.
Recommended Response Action: Enter valid job parameters and retry the operation.
Category: Updates (CUPD = Firmware)
Severity: Critical
Redfish Event Type: Not Applicable
Applicable Event or Alert Types: No alerts are applicable for this message

CUPD3046

NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the Applicable Event or Alert Types section.

Message: Unable to create the update job because the Key attribute is missing from a job parameter.
Detailed Description: The update job cannot be created because the Key attribute is missing from a job parameter.
Recommended Response Action: Make sure all job parameters have the Key attribute and retry the operation.
Category: Updates (CUPD = Firmware)
Severity: Critical
Redfish Event Type: Not Applicable
Applicable Event or Alert Types: No alerts are applicable for this message

CUPD3047

NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the Applicable Event or Alert Types section.

Message: Unable to create the update job because the Value attribute is missing from a job parameter.
Detailed Description: The update job cannot be created because the Value attribute is missing from a job parameter.
Recommended Response Action: Make sure all job parameters have the Value attribute and retry the operation.
Category: Updates (CUPD = Firmware)
Severity: Critical
Redfish Event Type: Not Applicable
Applicable Event or Alert Types: No alerts are applicable for this message

CUPD3048

NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the Applicable Event or Alert Types section.

Message: Unable to create or update the catalog because the entered repository name exceeds the maximum allowed length.
Detailed Description: The catalog cannot be created or updated because the entered repository name exceeds the maximum limit of 255 characters.
Recommended Response Action: Enter a repository name less than 255 characters and retry the operation.
Category: Updates (CUPD = Firmware)
Severity: Critical
Redfish Event Type: Not Applicable
Applicable Event or Alert Types: No alerts are applicable for this message

CUPD3049

NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the Applicable Event or Alert Types section.

Message: Unable to create or update the catalog because the entered repository description exceeds the maximum allowed length.
Detailed Description: The catalog cannot be created or updated because the entered repository description exceeds the maximum limit of 255 characters.
Recommended Response Action: Enter a repository description less than 255 characters and retry the operation.
Category: Updates (CUPD = Firmware)
Severity: Critical
Redfish Event Type: Not Applicable
Applicable Event or Alert Types: No alerts are applicable for this message

CUPD3050

NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the Applicable Event or Alert Types section.

Message: Unable to create or update the catalog because the entered repository username exceeds the maximum allowed length.
Detailed Description: The catalog cannot be created or updated because the entered repository username exceeds the maximum limit of 255 characters.
Recommended Response Action: Enter a repository username less than 255 characters and retry the operation.
Category: Updates (CUPD = Firmware)
Severity: Critical
Redfish Event Type: Not Applicable
Applicable Event or Alert Types: No alerts are applicable for this message

CUPD3051

NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the Applicable Event or Alert Types section.

Message: Unable to create or update the catalog because the entered repository domain name exceeds the maximum allowed length.
Detailed Description: The catalog cannot be created or updated because the entered repository domain name exceeds the maximum limit of 255 characters.
Recommended Response Action: Enter a repository domain name less than 255 characters and retry the operation.
Category: Updates (CUPD = Firmware)
Severity: Critical
Redfish Event Type: Not Applicable
Applicable Event or Alert Types: No alerts are applicable for this message

CUPD3052

NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the Applicable Event or Alert Types section.

Message: Unable to create or update the catalog because the entered Check Certificate value is invalid.
Detailed Description: The catalog cannot be created or updated because the entered Check Certificate value is invalid.
Recommended Response Action: Make sure the entered Check Certificate value is true or false and retry the operation.
Category: Updates (CUPD = Firmware)
Severity: Critical
Redfish Event Type: Not Applicable
Applicable Event or Alert Types: No alerts are applicable for this message

CUPD3053

NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the Applicable Event or Alert Types section.

Message: Unable to create or update the catalog because the entered repository type is invalid.
Detailed Description: The catalog cannot be created or updated because the entered repository type is invalid.
Recommended Response Action: Enter a valid repository type and retry the operation.
Category: Updates (CUPD = Firmware)
Severity: Critical
Redfish Event Type: Not Applicable
Applicable Event or Alert Types: No alerts are applicable for this message

CUPD3054

NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the Applicable Event or Alert Types section.

Message: Unable to create or update the catalog because the repository name is missing.
Detailed Description: The catalog cannot be created or updated because there is no value entered for repository name.
Recommended Response Action: Enter the repository name and retry the operation.
Category: Updates (CUPD = Firmware)
Severity: Critical
Redfish Event Type: Not Applicable
Applicable Event or Alert Types: No alerts are applicable for this message

CUPD3055

NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the Applicable Event or Alert Types section.

Message: Unable to create or update the catalog because the repository type is missing.
Detailed Description: The catalog cannot be created or updated because there is no value entered for repository type.
Recommended Response Action: Enter the repository type and retry the operation.
Category: Updates (CUPD = Firmware)
Severity: Critical
Redfish Event Type: Not Applicable
Applicable Event or Alert Types: No alerts are applicable for this message

CUPD3056

NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the Applicable Event or Alert Types section.

Message: Unable to create or update the catalog because the repository source is missing.
Detailed Description: The catalog cannot be created or updated because there is no value entered for repository source.
Recommended Response Action: Enter the repository source and retry the operation.
Category: Updates (CUPD = Firmware)
Severity: Critical
Redfish Event Type: Not Applicable
Applicable Event or Alert Types: No alerts are applicable for this message

CUPD3057

NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the Applicable Event or Alert Types section.

Message: Unable to create or update the baseline because the entered Downgrade Enabled value is invalid.
Detailed Description: The baseline cannot be created or updated because the entered Downgrade Enabled value is invalid.
Recommended Response Action: Make sure the entered Downgrade Enabled value is true or false and retry the operation.
Category: Updates (CUPD = Firmware)
Severity: Critical
Redfish Event Type: Not Applicable
Applicable Event or Alert Types: No alerts are applicable for this message

CUPD3058

NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the Applicable Event or Alert Types section.

Message: Unable to create or update the catalog because the repository username or password is missing.
Detailed Description: The catalog cannot be created or updated because the repository username or password is missing.
Recommended Response Action: Enter the repository username and password and retry the operation.
Category: Updates (CUPD = Firmware)
Severity: Critical
Redfish Event Type: Not Applicable
Applicable Event or Alert Types: No alerts are applicable for this message

CUPD3059

NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the Applicable Event or Alert Types section.

Message: Unable to create or update the baseline because the entered baseline name exceeds the maximum allowed length.
Detailed Description: The baseline cannot be created or updated because the entered baseline name exceeds the maximum limit of 255 characters.
Recommended Response Action: Enter a baseline name less than 255 characters and retry the operation.
Category: Updates (CUPD = Firmware)
Severity: Critical
Redfish Event Type: Not Applicable
Applicable Event or Alert Types: No alerts are applicable for this message

CUPD3060

NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the Applicable Event or Alert Types section.

Message: Unable to create or update the baseline because the entered baseline description exceeds the maximum allowed length.
Detailed Description: The baseline cannot be created or updated because the entered baseline description exceeds the maximum limit of 255 characters.
Recommended Response Action: Enter a baseline description less than 255 characters and retry the operation.
Category: Updates (CUPD = Firmware)
Severity: Critical
Redfish Event Type: Not Applicable
Applicable Event or Alert Types: No alerts are applicable for this message

CUPD3061

NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the Applicable Event or Alert Types section.

Message: Unable to create or update the baseline because the entered Is64Bit value is invalid.
Detailed Description: The baseline cannot be created or updated because the entered Is64Bit value is invalid.
Recommended Response Action: Make sure the entered Is64Bit value is true or false and retry the operation.
Category: Updates (CUPD = Firmware)
Severity: Critical
Redfish Event Type: Not Applicable
Applicable Event or Alert Types: No alerts are applicable for this message

CUPD3062

NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the Applicable Event or Alert Types section.

Message: Unable to create or update the catalog because the catalog source or file name is missing.
Detailed Description: The catalog cannot be created or updated because there is no value entered for catalog source or filename.
Recommended Response Action: Enter the catalog source and filename and retry the operation.
Category: Updates (CUPD = Firmware)
Severity: Critical
Redfish Event Type: Not Applicable
Applicable Event or Alert Types: No alerts are applicable for this message

CUPD3063

NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the Applicable Event or Alert Types section.

Message: Unable to create or update the catalog because an Online Repository already exists.
Detailed Description: The catalog cannot be created or updated because an Online Repository already exists.
Recommended Response Action: No response action required.
Category: Updates (CUPD = Firmware)
Severity: Critical
Redfish Event Type: Not Applicable
Applicable Event or Alert Types: No alerts are applicable for this message

CUPD3064

NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the Applicable Event or Alert Types section.

Message: Unable to create or update the catalog because a repository with the same name already exists.
Detailed Description: The catalog cannot be created or updated because a repository with the same name already exists.
Recommended Response Action: Enter a different name and retry the operation.
Category: Updates (CUPD = Firmware)
Severity: Critical
Redfish Event Type: Not Applicable
Applicable Event or Alert Types: No alerts are applicable for this message

CUPD3065

NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the Applicable Event or Alert Types section.

Message: Unable to retrieve the list of associated baselines because no device IDs were provided.
Detailed Description: The list of associated baselines cannot be retrieved because no target IDs were provided.
Recommended Response Action: Enter a valid device ID and retry the operation.
Category: Updates (CUPD = Firmware)
Severity: Critical
Redfish Event Type: Not Applicable
Applicable Event or Alert Types: No alerts are applicable for this message

CUPD3066

NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the Applicable Event or Alert Types section.

Message: Unable to create or update the catalog because the entered repository password exceeds the maximum allowed length.
Detailed Description: The catalog cannot be created or updated because the entered repository password exceeds the maximum limit of 255 characters.
Recommended Response Action: Enter a repository password less than 255 characters and retry the operation.
Category: Updates (CUPD = Firmware)
Severity: Critical
Redfish Event Type: Not Applicable
Applicable Event or Alert Types: No alerts are applicable for this message

CUPD3067

NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the Applicable Event or Alert Types section.

Message: Unable to create or update the catalog or baseline because the entered job type does not exist.
Detailed Description: The catalog or baseline cannot be created or updated because the entered job type does not exist.
Recommended Response Action: Enter a valid job type and retry the operation.
Category: Updates (CUPD = Firmware)
Severity: Critical
Redfish Event Type: Not Applicable
Applicable Event or Alert Types: No alerts are applicable for this message

CUPD3068

NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the Applicable Event or Alert Types section.

Message: Unable to update the firmware because an exception occurred during the update process.
Detailed Description: The firmware cannot be updated because an exception occurred during the update process.
Recommended Response Action: Make sure the device is available and retry the operation. If the issue persists, contact your system administrator.
Category: Updates (CUPD = Firmware)
Severity: Critical
Redfish Event Type: Not Applicable
Applicable Event or Alert Types: No alerts are applicable for this message

CUPD3069

NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the Applicable Event or Alert Types section.

Message: Unable to create or update the catalog because the entered filename exceeds the maximum allowed length.
Detailed Description: The catalog cannot be created or updated because the entered filename exceeds the maximum limit of 255 characters.
Recommended Response Action: Enter a filename less than 255 characters and retry the operation.
Category: Updates (CUPD = Firmware)
Severity: Critical
Redfish Event Type: Not Applicable
Applicable Event or Alert Types: No alerts are applicable for this message

CUPD3070

NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the Applicable Event or Alert Types section.

Message: Unable to create or update the catalog because the entered catalog source path exceeds the maximum allowed length.
Detailed Description: The catalog cannot be created or updated because the entered catalog source path exceeds the maximum limit of 255 characters.
Recommended Response Action: Enter a catalog source path less than 255 characters and retry the operation.
Category: Updates (CUPD = Firmware)
Severity: Critical
Redfish Event Type: Not Applicable
Applicable Event or Alert Types: No alerts are applicable for this message

CUPD3071

NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the Applicable Event or Alert Types section.

Message: Unable to create or update the catalog because the entered repository source exceeds the maximum allowed length.
Detailed Description: The catalog cannot be created or updated because the entered repository source exceeds the maximum limit of 255 characters.
Recommended Response Action: Enter a repository source less than 255 characters and retry the operation.
Category: Updates (CUPD = Firmware)
Severity: Critical
Redfish Event Type: Not Applicable
Applicable Event or Alert Types: No alerts are applicable for this message

CUPD3072

NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the Applicable Event or Alert Types section.

Message: Unable to retrieve rollback information because the entered device ID is empty or invalid.
Detailed Description: Firmware rollback information cannot be retrieved either because the entered device ID is invalid or no device ID is provided in the URI.
Recommended Response Action: Enter a valid device ID and retry the operation. The device ID must be part of the URI in this format: https://<IPAddress>/api/UpdateService/RollbackSoftwares?$filter=DeviceId eq <deviceid>.
Category: Updates (CUPD = Firmware)
Severity: Critical
Redfish Event Type: Not Applicable
Applicable Event or Alert Types: No alerts are applicable for this message

CUPD3073

NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the Applicable Event or Alert Types section.

Message: Unable to retrieve rollback information because an exception occurred.
Detailed Description: Firmware rollback information cannot be retrieved because an exception occurred.
Recommended Response Action: Retry the operation. If the issue persists, contact your system administrator.
Category: Updates (CUPD = Firmware)
Severity: Critical
Redfish Event Type: Not Applicable
Applicable Event or Alert Types: No alerts are applicable for this message

CUPD3074

NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the Applicable Event or Alert Types section.

Message: Unable to retrieve certificate information because the entered URI Path is empty or invalid.
Detailed Description: Certificate information cannot be retrieved because the entered URI Path is empty or invalid.
Recommended Response Action: Enter a valid URI Path and retry the operation.
Category: Updates (CUPD = Firmware)
Severity: Critical
Redfish Event Type: Not Applicable
Applicable Event or Alert Types: No alerts are applicable for this message

CUPD3075

NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the Applicable Event or Alert Types section.

Message: Unable to display certificate details because the certificate is invalid.
Detailed Description: Certificate details cannot be displayed because the certificate is invalid.
Recommended Response Action: Make sure the device has a valid certificate and retry the operation.
Category: Updates (CUPD = Firmware)
Severity: Critical
Redfish Event Type: Not Applicable
Applicable Event or Alert Types: No alerts are applicable for this message

CUPD3076

NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the Applicable Event or Alert Types section.

Message: Unable to retrieve Update Package details because the entered file token does not exist.
Detailed Description: Update Package information cannot be retrieved because the entered file token does not exist.
Recommended Response Action: Make sure the correct file token is entered and retry the operation.
Category: Updates (CUPD = Firmware)
Severity: Critical
Redfish Event Type: Not Applicable
Applicable Event or Alert Types: No alerts are applicable for this message

CUPD3077

NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the Applicable Event or Alert Types section.

Message: Unable to retrieve Update Package details because the information is not available.
Detailed Description: Update Package information cannot be retrieved because the information is not available.
Recommended Response Action: Make sure the requested file is a valid Update Package and retry the operation.
Category: Updates (CUPD = Firmware)
Severity: Critical
Redfish Event Type: Not Applicable
Applicable Event or Alert Types: No alerts are applicable for this message

CUPD3078

NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the Applicable Event or Alert Types section.

Message: Unable to generate Update Report because the Update File Token is missing.
Detailed Description: The Update Report cannot be generated because there is no value entered for Update File Token.
Recommended Response Action: Enter a valid Update File Token and retry the operation.
Category: Updates (CUPD = Firmware)
Severity: Critical
Redfish Event Type: Not Applicable
Applicable Event or Alert Types: No alerts are applicable for this message

CUPD3079

NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the Applicable Event or Alert Types section.

Message: Unable to generate Update Report because the entered file token does not exist.
Detailed Description: The Update Report cannot be generated because the entered file token does not exist.
Recommended Response Action: Make sure the correct file token is entered and retry the operation.
Category: Updates (CUPD = Firmware)
Severity: Critical
Redfish Event Type: Not Applicable
Applicable Event or Alert Types: No alerts are applicable for this message

CUPD3080

NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the Applicable Event or Alert Types section.

Message: Unable to generate Update Report because no targets were entered.
Detailed Description: The Update Report cannot be generated because there are no targets entered.
Recommended Response Action: Enter a valid Update Report target and retry the operation.
Category: Updates (CUPD = Firmware)
Severity: Critical
Redfish Event Type: Not Applicable
Applicable Event or Alert Types: No alerts are applicable for this message

CUPD3081

NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the Applicable Event or Alert Types section.

Message: Unable to generate Update Report because no applicable targets were found.
Detailed Description: The Update Report cannot be generated because no applicable targets were found.
Recommended Response Action: No response action required.
Category: Updates (CUPD = Firmware)
Severity: Critical
Redfish Event Type: Not Applicable
Applicable Event or Alert Types: No alerts are applicable for this message

CUPD3082

NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the Applicable Event or Alert Types section.

Message: Unable to display certificate details.
Detailed Description: The certificate details cannot be displayed because an exception occurred.
Recommended Response Action: Retry the operation. If the problem persists, contact your system administrator.
Category: Updates (CUPD = Firmware)
Severity: Critical
Redfish Event Type: Not Applicable
Applicable Event or Alert Types: No alerts are applicable for this message

CUPD3083

NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the Applicable Event or Alert Types section.

Message: Unable to retrieve Package Update details.
Detailed Description: The Update Package information cannot be retrieved because an exception occurred.
Recommended Response Action: Retry the operation. If the problem persists, contact your system administrator.
Category: Updates (CUPD = Firmware)
Severity: Critical
Redfish Event Type: Not Applicable
Applicable Event or Alert Types: No alerts are applicable for this message

CUPD3084

NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the Applicable Event or Alert Types section.

Message: Unable to generate the Update Report.
Detailed Description: The Update Report cannot be generated because an exception occurred.
Recommended Response Action: Retry the operation. If the problem persists, contact your system administrator.
Category: Updates (CUPD = Firmware)
Severity: Critical
Redfish Event Type: Not Applicable
Applicable Event or Alert Types: No alerts are applicable for this message

CUPD3086

NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the Applicable Event or Alert Types section.

Message: Unable to view or modify the baseline(s) because the entered ID(s) are invalid.
Detailed Description: The baseline(s) cannot be viewed or modified because the ID(s) entered are invalid.
Recommended Response Action: Provide valid baseline ID(s) and retry the operation.
Category: Updates (CUPD = Firmware)
Severity: Critical
Redfish Event Type: Not Applicable
Applicable Event or Alert Types: No alerts are applicable for this message

CUPD3087

NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the Applicable Event or Alert Types section.

Message: Unable to display component details because no components were found for the entered baseline and device IDs.
Detailed Description: Component details cannot be displayed because no components were found for the entered baseline and device IDs.
Recommended Response Action: No response action required.
Category: Updates (CUPD = Firmware)
Severity: Critical
Redfish Event Type: Not Applicable
Applicable Event or Alert Types: No alerts are applicable for this message

CUPD3088

NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the Applicable Event or Alert Types section.

Message: Unable to create an Update Package job because there is currently another Update Package job running.
Detailed Description: The job cannot be created because there is another Update Package job currently running. Only one Update Package job can run at a time.
Recommended Response Action: Wait for the other Update Package job to complete and retry the operation.
Category: Updates (CUPD = Firmware)
Severity: Critical
Redfish Event Type: Not Applicable
Applicable Event or Alert Types: No alerts are applicable for this message

CUPD3089

NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the Applicable Event or Alert Types section.

Message: Unable to create or update the baseline because the catalog ID entered is invalid.
Detailed Description: The baseline cannot be created or updated because the catalog ID entered is invalid.
Recommended Response Action: Enter a valid catalog ID and retry the operation.
Category: Updates (CUPD = Firmware)
Severity: Critical
Redfish Event Type: Not Applicable
Applicable Event or Alert Types: No alerts are applicable for this message

CUPD3090

NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the Applicable Event or Alert Types section.

Message: Unable to retrieve baseline list either because the device ID(s) entered are invalid, the ID(s) provided are not associated with a baseline or a group is used as a target for a baseline.
Detailed Description: Associated baselines cannot be retrieved either because the device ID(s) entered are invalid or the ID(s) provided are not associated with a baseline.
Recommended Response Action: Make sure the entered device ID(s) are valid and retry the operation.
Category: Updates (CUPD = Firmware)
Severity: Critical
Redfish Event Type: Not Applicable
Applicable Event or Alert Types: No alerts are applicable for this message

CUPD3091

NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the Applicable Event or Alert Types section.

Message: Unable to delete catalog(s) because there are no catalog ID(s) entered.
Detailed Description: Catalog(s) cannot be deleted because there are no catalog ID(s) provided.
Recommended Response Action: Enter a valid catalog ID and retry the operation.
Category: Updates (CUPD = Firmware)
Severity: Critical
Redfish Event Type: Not Applicable
Applicable Event or Alert Types: No alerts are applicable for this message

CUPD3092

NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the Applicable Event or Alert Types section.

Message: Unable to delete catalog(s) because the entered catalog ID(s) are associated with a baseline.
Detailed Description: Catalog(s) cannot be deleted because the provided catalog ID(s) are associated with a baseline.
Recommended Response Action: Delete any baselines associated with the provided catalog ID(s) and retry the operation.
Category: Updates (CUPD = Firmware)
Severity: Critical
Redfish Event Type: Not Applicable
Applicable Event or Alert Types: No alerts are applicable for this message

CUPD3093

NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the Applicable Event or Alert Types section.

Message: Unable to update the catalog because the request payload contains null values.
Detailed Description: The catalog cannot be updated because the request payload contains null values.
Recommended Response Action: Make sure all fields have a valid value and retry the operation.
Category: Updates (CUPD = Firmware)
Severity: Critical
Redfish Event Type: Not Applicable
Applicable Event or Alert Types: No alerts are applicable for this message

CUPD3094

NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the Applicable Event or Alert Types section.

Message: Unable to display the software rollback information because the device ID entered does not have any software rollback information associated with it.
Detailed Description: The software rollback information cannot be displayed because the device ID entered does not have any software rollback information associated with it.
Recommended Response Action: No response action required.
Category: Updates (CUPD = Firmware)
Severity: Warning
Redfish Event Type: Not Applicable
Applicable Event or Alert Types: No alerts are applicable for this message

CUPD3095

NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the Applicable Event or Alert Types section.

Message: Unable to display software rollback information because the rollback ID entered does not have any software rollback information associated with it.
Detailed Description: The software rollback information cannot be displayed because the rollback ID entered does not have any software rollback information associated with it.
Recommended Response Action: No response action is required.
Category: Updates (CUPD = Firmware)
Severity: Critical
Redfish Event Type: Not Applicable
Applicable Event or Alert Types: No alerts are applicable for this message

CUPD3096

NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the Applicable Event or Alert Types section.

Message: Unable to create or update the baseline because the repository ID is missing or invalid.
Detailed Description: The baseline cannot be created or updated because the repository ID entered is missing or invalid.
Recommended Response Action: Make sure the repository ID entered is valid and retry the operation.
Category: Updates (CUPD = Firmware)
Severity: Critical
Redfish Event Type: Not Applicable
Applicable Event or Alert Types: No alerts are applicable for this message

CUPD3097

NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the Applicable Event or Alert Types section.

Message: Unable to retrieve supported compliance status because the entered status ID is invalid.
Detailed Description: Supported compliance status cannot be retrieved because the entered status ID is invalid.
Recommended Response Action: Provide a valid Status ID and retry the operation.
Category: Updates (CUPD = Firmware)
Severity: Critical
Redfish Event Type: Not Applicable
Applicable Event or Alert Types: No alerts are applicable for this message

CUPD3098

NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the Applicable Event or Alert Types section.

Message: Unable to create or update the baseline because a baseline with the same name already exists.
Detailed Description: The baseline cannot be created or updated because a baseline with the same name already exists.
Recommended Response Action: Enter a unique baseline name and retry the operation.
Category: Updates (CUPD = Firmware)
Severity: Critical
Redfish Event Type: Not Applicable
Applicable Event or Alert Types: No alerts are applicable for this message

CUPD3099

NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the Applicable Event or Alert Types section.

Message: Unable to delete the entered baseline(s) because an associated job is running.
Detailed Description: The entered baseline(s) cannot be removed because an associated job is running.
Recommended Response Action: Make sure that all entered baselines are not currently running and retry the operation.
Category: Updates (CUPD = Firmware)
Severity: Warning
Redfish Event Type: Not Applicable
Applicable Event or Alert Types: No alerts are applicable for this message

CUPD3100

NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the Applicable Event or Alert Types section.

Message: Unable to delete the entered catalog(s) because an associated job is running.
Detailed Description: The entered catalog(s) cannot be removed because an associated job is running.
Recommended Response Action: Make sure that all entered catalogs are not associated with a running job and retry the operation.
Category: Updates (CUPD = Firmware)
Severity: Warning
Redfish Event Type: Not Applicable
Applicable Event or Alert Types: No alerts are applicable for this message

CUPD3101

NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the Applicable Event or Alert Types section.

Message

Unable to remove update file because the field(s) arg1 cannot be null or empty.

Arguments

arg1 = field names

Detailed Description

The operation cannot be completed because the mentioned field(s) are mandatory.

Recommended Response Action

Make sure all mandatory fields are provided and retry the operation.

Category

Updates (CUPD = Firmware)

Severity

Warning

Redfish Event Type

Not Applicable

Applicable Event or Alert Types

No alerts are applicable for this message

CUPD3102

NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the Applicable Event or Alert Types section.

Message

Unable to generate a report for the specified target(s) because the user arg1 does not have sufficient privileges to generate a report.

Arguments

arg1 = current user name

Detailed Description

The report for the specified target(s) cannot be generated because the user identified in the message does not have sufficient privileges to generate the report.

Recommended Response Action

Retry the operation by logging in as a user with sufficient privileges.

Category

Updates (CUPD = Firmware)

Severity

Warning

Redfish Event Type

Not Applicable

Applicable Event or Alert Types

No alerts are applicable for this message

CUPD3103

NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the Applicable Event or Alert Types section.

Message: Unable to create or update the baseline because the entered name is invalid.
Detailed Description: The baseline cannot be created or updated either because the entered name exceeds the maximum allowed length or there is no name entered.
Recommended Response Action: Enter a baseline name less than 255 characters and retry the operation.
Category: Updates (CUPD = Firmware)
Severity: Critical
Redfish Event Type: Not Applicable
Applicable Event or Alert Types: No alerts are applicable for this message

CUPD3104

NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the Applicable Event or Alert Types section.

Message: The catalog ID entered is not associated with any firmware baseline.
Detailed Description: The catalog ID entered is not associated with any firmware baseline.
Recommended Response Action: No response action required.
Category: Updates (CUPD = Firmware)
Severity: Warning
Redfish Event Type: Not Applicable
Applicable Event or Alert Types: No alerts are applicable for this message

CUPD3105

NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the Applicable Event or Alert Types section.

Message: Unable to update the entered baseline because it is currently being refreshed.
Detailed Description: The baseline cannot be updated because a job associated with the baseline is running.
Recommended Response Action: Wait until the associated job is complete and retry the operation.
Category: Updates (CUPD = Firmware)
Severity: Warning
Redfish Event Type: Not Applicable
Applicable Event or Alert Types: No alerts are applicable for this message

CUPD3106

NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the Applicable Event or Alert Types section.

Message: Unable to create or update the catalog because an Online Repository already exists.
Detailed Description: Unable to create or update the catalog because an Online Repository already exists.
Recommended Response Action: Unable to create or update the catalog because an Online Repository already exists.
Category: Updates (CUPD = Firmware)
Severity: Warning
Redfish Event Type: Not Applicable
Applicable Event or Alert Types: No alerts are applicable for this message

CUPD3107

NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the Applicable Event or Alert Types section.

Message

Unable to complete the operation because a catalog with the same release identifier : arg1 already exists.

Arguments

arg1 = release identifer

Detailed Description

Unable to complete the operation because a catalog with the same release identifier already exists.

Recommended Response Action

No response action required.

Category

Updates (CUPD = Firmware)

Severity

Warning

Redfish Event Type

Not Applicable

Applicable Event or Alert Types

No alerts are applicable for this message

CUPD3108

NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the Applicable Event or Alert Types section.

Message

Unable to generate the Update Report because the Update Package file signature is invalid. Error description: arg1.

Arguments

arg1 = error description

Detailed Description

The Update Report cannot be generated because the Update Package file signature is invalid. For more information, see the OpenManage Enterprise-Modular Users Guide on the support site.

Recommended Response Action

No response action required.

Category

Updates (CUPD = Firmware)

Severity

Critical

Redfish Event Type

Not Applicable

Applicable Event or Alert Types

No alerts are applicable for this message

CUPD3109

NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the Applicable Event or Alert Types section.

Message: Insufficient disk space available. At least 3GB free space is required.
Detailed Description: Insufficient disk space available. At least 3GB free space is required.
Recommended Response Action: No response action required.
Category: Updates (CUPD = Firmware)
Severity: Warning
Redfish Event Type: Not Applicable
Applicable Event or Alert Types: No alerts are applicable for this message

CUPD3110

NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the Applicable Event or Alert Types section.

Message: Error while downloading console update archive file.
Detailed Description: Error while downloading console update archive file.
Recommended Response Action: Please check the uploading file.
Category: Updates (CUPD = Firmware)
Severity: Critical
Redfish Event Type: Not Applicable
Applicable Event or Alert Types: No alerts are applicable for this message

CUPD3111

NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the Applicable Event or Alert Types section.

Message: Downloaded file size does not match with remote file size.
Detailed Description: File download error :: downloaded file size does not match with remote file size.
Recommended Response Action: No response action required.
Category: Updates (CUPD = Firmware)
Severity: Critical
Redfish Event Type: Not Applicable
Applicable Event or Alert Types: No alerts are applicable for this message

CUPD3112

NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the Applicable Event or Alert Types section.

Message: Unable to retrieve validated catalog details as dell.com is not reachable.
Detailed Description: Unableto retrieve validated catalog details as dell.com is not reachable.
Recommended Response Action: Retry the operation. If the problem persists, contact system or network administrator.
Category: Updates (CUPD = Firmware)
Severity: Warning
Redfish Event Type: Not Applicable
Applicable Event or Alert Types: No alerts are applicable for this message

CUPD3113

NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the Applicable Event or Alert Types section.

Message: Invalid release identifier provided, unable to create or update catalog for validated firmware solution baseline.
Detailed Description: The request cannot be processed because the provided release identifier is invalid.
Recommended Response Action: Refer to RESTAPI guide to retrieve validated catalog versions and retry the operation.
Category: Updates (CUPD = Firmware)
Severity: Warning
Redfish Event Type: Not Applicable
Applicable Event or Alert Types: No alerts are applicable for this message

CUPD3114

NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the Applicable Event or Alert Types section.

Message

Unable to create catalog for validated firmware solution baseline as automatic or manual update is only applicable for latest release identifier arg1.

Arguments

arg1 = latest release identifier

Detailed Description

The request cannot be processed because the provided release identifier is invalid.

Recommended Response Action

Use the latest release identifier that supports automatic or manual updates and retry the operation. The latest release identifier can be availed by calling get validated catalog version API.

Category

Updates (CUPD = Firmware)

Severity

Warning

Redfish Event Type

Not Applicable

Applicable Event or Alert Types

No alerts are applicable for this message

CUPD3115

NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the Applicable Event or Alert Types section.

Message: Backup option is only applicable for latest release identifier of validated firmware solution baseline.
Detailed Description: The request cannot be processed because the provided release identifier is invalid.
Recommended Response Action: Usethe latest release identifier by calling get validated catalog version API and retry the operation.
Category: Updates (CUPD = Firmware)
Severity: Warning
Redfish Event Type: Not Applicable
Applicable Event or Alert Types: No alerts are applicable for this message

CUPD3116

NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the Applicable Event or Alert Types section.

Message

Invalid input parameter : arg1 provided, unable to update the catalog.

Arguments

arg1 = input parameter name

Detailed Description

Invalid input parameter provided, unable to update the catalog.

Recommended Response Action

Provide valid input parameter and retry the operation.

Category

Updates (CUPD = Firmware)

Severity

Warning

Redfish Event Type

Not Applicable

Applicable Event or Alert Types

No alerts are applicable for this message

CUPD3117

NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the Applicable Event or Alert Types section.

Message: Unable to complete the operation for validated firmware solution baseline as operation is only applicable for latest release identifier.
Detailed Description: Unable to complete the operation for validated firmware solution baseline as operation is only applicable for latest release identifier.
Recommended Response Action: No response action required.
Category: Updates (CUPD = Firmware)
Severity: Warning
Redfish Event Type: Not Applicable
Applicable Event or Alert Types: No alerts are applicable for this message

CUPD3118

NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the Applicable Event or Alert Types section.

Message: Unable to update catalog for validated firmware solution baseline as release identifier cannot be modified.
Detailed Description: Unable to update catalog for validated firmware solution baseline as release identifier cannot be modified.
Recommended Response Action: No response action required.
Category: Updates (CUPD = Firmware)
Severity: Warning
Redfish Event Type: Not Applicable
Applicable Event or Alert Types: No alerts are applicable for this message

CUPD3119

NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the Applicable Event or Alert Types section.

Message: Unable to create or update baseline because the selected devices are not supported by the Infrastructure Update Catalog.
Detailed Description: The Infrastructure Update Catalog supports only the following device types: CDU, Power shelf, and IRC.
Recommended Response Action: Select supported device types and try again. Or use a different catalog type for the selected devices.
Category: Updates (CUPD = Firmware)
Severity: Critical
Redfish Event Type: Not Applicable
Applicable Event or Alert Types: No alerts are applicable for this message

CUPD4102

NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the Applicable Event or Alert Types section.

Message: Unable to retrieve the latest version for the console update.
Detailed Description: The console update discovery process was unable to complete. The service failed to check for available updates, download the update bundle, or stage it for installation. Common root causes include network connectivity problems to the update source, proxy misconfiguration, insufficient disk space on the appliance, or an unreachable update repository.
Recommended Response Action: 1)Verify network connectivity between the appliance and the configured update source.2.If a proxy is configured, validate proxy settings and ensure the update source URL is reachable through it.3.Check available disk space on the appliance and free up storage if necessary.4.Review the console-update-manager-service logs for the specific failure reason.5.Retry the Console Update Task.
Category: Updates (CUPD = Firmware)
Severity: Critical
Redfish Event Type: Not Applicable
Applicable Event or Alert Types: No alerts are applicable for this message

CUPD4103

NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the Applicable Event or Alert Types section.

Message: Unable to validate the checksum of the console update bundle.
Detailed Description: The downloaded update bundles checksum does not match the expected value recorded in the manifest. This indicates the bundle file was corrupted during transfer or has been tampered with. The staged bundle cannot be trusted for installation.
Recommended Response Action: 1)Delete the staged bundle and re-run the discovery task to download a fresh copy.2.If using a network share as the update source, verify the bundle file integrity at the source location.3.Investigate potential network reliability issues such as packet loss or proxy interference that could corrupt downloads.4.If the problem persists after re-download, obtain the bundle directly from Dell Support and upload it via the Console Update Upload API.
Category: Updates (CUPD = Firmware)
Severity: Critical
Redfish Event Type: Not Applicable
Applicable Event or Alert Types: No alerts are applicable for this message

CUPD4110

NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the Applicable Event or Alert Types section.

Message

Console update started for version arg1.

Arguments

arg1 = latest_version

Detailed Description

The console update execution process has been initiated for the specified target version.

Recommended Response Action

1)No immediate action required. This is a normal operational event.2.Monitor upgrade progress through the job status events.3.The upgrade typically takes 1545 minutes depending on scope. Do not restart the appliance or interrupt the process during this time.

Category

Updates (CUPD = Firmware)

Severity

Informational

Redfish Event Type

Not Applicable

Applicable Event or Alert Types

No alerts are applicable for this message

CUPD4111

NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the Applicable Event or Alert Types section.

Message

Console update to version arg1 completed successfully.

Arguments

arg1 = latest_version

Detailed Description

Console update to version <Latest Version> completed successfully.The appliance is now running the new version and lockdown mode (if engaged) has been automatically released.

Recommended Response Action

1)No immediate action required. This is a normal operational event.2.Verify the appliance is reporting the expected new version.3.Confirm that lockdown mode has been released and normal API operations have resumed.

Category

Updates (CUPD = Firmware)

Severity

Informational

Redfish Event Type

Not Applicable

Applicable Event or Alert Types

No alerts are applicable for this message

CUPD4112

NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the Applicable Event or Alert Types section.

Message

Console update to version arg1 failed at stage arg2.

Arguments

arg1 = latest_version
arg2 = update_stage

Detailed Description

The console update process failed during one of its update stages. Depending on the stage, an automatic rollback may have been attempted.Check the console update logs for more details.

Recommended Response Action

1)Identify the failed stage from the message and review the corresponding service logs for root cause.2. Review the Console Update logs for detailed failure information.3. If a rollback succeeded, the appliance is on the previous version and it is safe to retry after resolving the root cause.4. If a rollback failed, do not retry. Collect a debug log bundle and contact Dell Support.5. For fallback scenarios (rate limit, path traversal, reboot limit, state corruption), check the service logs for the specific condition that triggered this error.

Category

Updates (CUPD = Firmware)

Severity

Critical

Redfish Event Type

Not Applicable

Applicable Event or Alert Types

No alerts are applicable for this message

CUPD4113

NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the Applicable Event or Alert Types section.

Message

Console update rollback completed successfully at stage arg1.

Arguments

arg1 = update_stage

Detailed Description

The automatic rollback completed successfully after an upgrade failure. The database was restored using the preferred backup mechanism, and the filesystem was reverted to its pre-upgrade state. The appliance is now running the previous known-good version with no data loss.

Recommended Response Action

1)The appliance is back on the previous version. Verify normal operation.2.Review the console update logs to understand the original upgrade failure before retrying.3.Review the rollback logs for any warnings that may affect a future retry.4. If the update is critical, contact Dell Support for guidance before re-attempting the upgrade.

Category

Updates (CUPD = Firmware)

Severity

Warning

Redfish Event Type

Not Applicable

Applicable Event or Alert Types

No alerts are applicable for this message

CUPD4114

NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the Applicable Event or Alert Types section.

Message: Console update rollback failed. Manual intervention required.
Detailed Description: The automatic rollback failed after an upgrade failure. Both the primary and fallback restore mechanisms were unsuccessful. The appliance may be in an inconsistent state and requires manual intervention.
Recommended Response Action: 1)Do not restart the appliance without Dell Support guidance.2.Collect a debug log bundle immediately.3.Contact Dell Support with the debug log bundle, the failed target version, and the previous version.4.Do not attempt another upgrade or manual recovery without Dell Support direction.
Category: Updates (CUPD = Firmware)
Severity: Critical
Redfish Event Type: Not Applicable
Applicable Event or Alert Types: No alerts are applicable for this message

CUPD4120

NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the Applicable Event or Alert Types section.

Message: Console update lockdown mode engaged. API requests will be restricted.
Detailed Description: Lockdown mode has been engaged prior to starting the console update. During lockdown, most Console Update API endpoints return 503 Service Unavailable to prevent conflicting operations such as uploading a new bundle during an active upgrade. Lockdown is enforced at multiple layers to ensure consistency.
Recommended Response Action: 1)No immediate action required. Lockdown is a normal protective measure during upgrades.2.Lockdown is automatically released when the upgrade completes or rolls back.3.If lockdown persists after upgrade completion, verify the upgrade task status and release lockdown manually if needed.
Category: Updates (CUPD = Firmware)
Severity: Warning
Redfish Event Type: Not Applicable
Applicable Event or Alert Types: No alerts are applicable for this message

CUPD4121

NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the Applicable Event or Alert Types section.

Message: Console update lockdown mode released. Normal operations resumed.
Detailed Description: Lockdown mode has been released following upgrade completion (either success or rollback). All Console Update API endpoints are restored to normal operation and new requests will be accepted.
Recommended Response Action: 1)No immediate action required. This is a normal operational event.2.If this event does not appear after an upgrade completes, verify the lockdown status and release it manually if necessary.
Category: Updates (CUPD = Firmware)
Severity: Informational
Redfish Event Type: Not Applicable
Applicable Event or Alert Types: No alerts are applicable for this message

CUPD4122

NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the Applicable Event or Alert Types section.

Message: Request blocked: console update lockdown mode is active.
Detailed Description: Request blocked: console update lockdown mode is active.
Recommended Response Action: Wait for the active upgrade to complete. Lockdown is automatically released upon completion. Check upgrade progress in the Jobs UI.
Category: Updates (CUPD = Firmware)
Severity: Warning
Redfish Event Type: Not Applicable
Applicable Event or Alert Types: No alerts are applicable for this message

CUPD4130

NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the Applicable Event or Alert Types section.

Message: Pre-upgrade health audit failed. Upgrade cannot proceed.
Detailed Description: Console update detects that the appliance is not healthy enough to proceed. The audit checks disk space, CPU and memory.
Recommended Response Action: 1) Review the health audit details in the console update logs for the specific failing check.2. Disk space: Free up space on the appliance or add more disk space.3. CPU/Memory: Wait for high-load operations to complete, or increase resources if virtualized.4. Retry the upgrade after resolving the health issue.
Category: Updates (CUPD = Firmware)
Severity: Critical
Redfish Event Type: Not Applicable
Applicable Event or Alert Types: No alerts are applicable for this message

CUPD4140

NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the Applicable Event or Alert Types section.

Message

OME console update started for arg1 and version arg2.

Arguments

arg1 = ome_name
arg2 = latest_version

Detailed Description

The system initiates console update to the connected appliance and instructs it to apply the staged package.

Recommended Response Action

No action required. Monitor progress in the Jobs UI. Each OME update runs independently; failure of one OME does not block others.

Category

Updates (CUPD = Firmware)

Severity

Informational

Redfish Event Type

Not Applicable

Applicable Event or Alert Types

No alerts are applicable for this message

CUPD4141

NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the Applicable Event or Alert Types section.

Message

OME console update completed successfully for arg1.

Arguments

arg1 = ome_name

Detailed Description

The target OME appliance finishes updating, after which the system performs the necessary cleanup and confirms the appliances new version.

Recommended Response Action

No action required. Verify the OMEs version in the Federation UI.

Category

Updates (CUPD = Firmware)

Severity

Informational

Redfish Event Type

Not Applicable

Applicable Event or Alert Types

No alerts are applicable for this message

CUPD4142

NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the Applicable Event or Alert Types section.

Message

OME console update failed for arg1 and arg2.

Arguments

arg1 = ome_name
arg2 = reason

Detailed Description

The update on the downstream appliance does not complete successfully, potentially due to communication issues or a problem within the appliances update process.

Recommended Response Action

1)Check the failure reason2.Verify network connectivity between the federation appliance and the OME.3.Check the OMEs own logs for update failures.4.Check firewall rules.5.Retry the OME update from the Federation UI or Jobs UI.

Category

Updates (CUPD = Firmware)

Severity

Critical

Redfish Event Type

Not Applicable

Applicable Event or Alert Types

No alerts are applicable for this message

CUPD4143

NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the Applicable Event or Alert Types section.

Message

Circuit breaker tripped for OME arg1. Halting further update attempts.

Arguments

arg1 = ome_name

Detailed Description

Repeated failures to update a specific OME appliance trigger the circuit breaker. The circuit breaker prevents further attempts until manually reset, protecting both the federation appliance and the OME from cascading failure loops.

Recommended Response Action

1)Investigate why the OME is consistently failing to update.2.Fix the underlying issue (network, OME health).3.Reset the circuit breaker by re-running the OME Console Update Task from the Jobs UI.4.If the OME is decommissioned or unreachable long-term, remove it from the federation group.

Category

Updates (CUPD = Firmware)

Severity

Critical

Redfish Event Type

Not Applicable

Applicable Event or Alert Types

No alerts are applicable for this message