XClarity Administrator events organized by severity
The following table lists all XClarity Administrator events, organized by severity (Information, Warning, and Critical).
| Event ID | Message String | Severity |
|---|---|---|
| FQXHMUP5011R | Retry the request. | |
| FQXHMUP5012R | Retry the request. | |
| FQXHMUP5013R | Retry the request. | |
| FQXHMCP1105I | Pattern [arg1] was deployed to [arg2]. | Informational |
| FQXHMCP1110I | Pattern [arg1] deployment started. | Informational |
| FQXHMCP1135I | Profile [arg1] redeployment has started. | Informational |
| FQXHMCP1145I | Profile [arg1] was redeployed to [arg2]. | Informational |
| FQXHMCP1165I | Profile [arg1] was unassigned from [arg2]. | Informational |
| FQXHMCP1190J | The server configuration non-compliant alert was deserted for profile [arg1]. | Informational |
| FQXHMCP1205I | Failover from server [arg1] to standby server [arg2] has completed. | Informational |
| FQXHMCP1210I | [arg1] failover from server [arg2] to standby server [arg3] has started. | Informational |
| FQXHMCP1300I | Local storage is being reset to the default configuration. | Informational |
| FQXHMCP1305I | Local storage has been reset to the default configuration. | Informational |
| FQXHMCP1400I | The Intel Optane DC Persistence Memory security operation is in progress. | Informational |
| FQXHMCP5100I | User [arg1] created pattern [arg2]. | Informational |
| FQXHMCP5110I | [arg1] deployed existing pattern [arg2]. | Informational |
| FQXHMCP5120I | User [arg1] edited pattern [arg2]. | Informational |
| FQXHMCP5130I | User [arg1] copied pattern [arg2]. | Informational |
| FQXHMCP5140I | User [arg1] renamed pattern [arg2]. | Informational |
| FQXHMCP5150I | User [arg1] deleted pattern [arg2]. | Informational |
| FQXHMCP5240I | User [arg1] renamed profile [arg2]. | Informational |
| FQXHMCP5250I | User [arg1] deleted profile [arg2]. | Informational |
| FQXHMCP5260I | User [arg1] deployed profile [arg2]. | Informational |
| FQXHMCP5300I | User [arg1] created address pool [arg2]. | Informational |
| FQXHMCP5320I | User [arg1] edited address pool [arg2]. | Informational |
| FQXHMCP5330I | User [arg1] copied address pool [arg2]. | Informational |
| FQXHMCP5340I | User [arg1] renamed address pool [arg2]. | Informational |
| FQXHMCP5350I | User [arg1] deleted address pool [arg2]. | Informational |
| FQXHMCP5400I | User [arg1] created standby pool [arg2]. | Informational |
| FQXHMCP5420I | User [arg1] edited standby pool [arg2]. | Informational |
| FQXHMCP5430I | User [arg1] copied standby pool [arg2]. | Informational |
| FQXHMCP5440I | User [arg1] renamed standby pool [arg2]. | Informational |
| FQXHMCP5450I | User [arg1] deleted standby pool [arg2]. | Informational |
| FQXHMCP5500I | User [arg1] created placeholder chassis [arg2]. | Informational |
| FQXHMCP5520I | User [arg1] edited placeholder chassis [arg2]. | Informational |
| FQXHMCP5530I | User [arg1] copied placeholder chassis [arg2]. | Informational |
| FQXHMCP5540I | User [arg1] renamed placeholder chassis [arg2]. | Informational |
| FQXHMCP5550I | User [arg1] deleted placeholder chassis [arg2]. | Informational |
| FQXHMCP5600I | User [arg1] created policy [arg2]. | Informational |
| FQXHMCP5620I | User [arg1] edited policy [arg2]. | Informational |
| FQXHMCP5630I | User [arg1] copied policy [arg2]. | Informational |
| FQXHMCP5640I | User [arg1] renamed policy [arg2]. | Informational |
| FQXHMCP5650I | User [arg1] deleted policy [arg2]. | Informational |
| FQXHMCP5700I | User [arg1] started failover monitoring for [arg2] using standby pool [arg3] and failover policy [arg4]. | Informational |
| FQXHMCP5710I | User [arg1] restarted failover monitoring for [arg2]. | Informational |
| FQXHMCP5720I | User [arg1] edited failover monitoring for [arg2]. | Informational |
| FQXHMCP5730I | User [arg1] performed a failover to standby server [arg2]. | Informational |
| FQXHMCP5750I | User [arg1] stopped failover monitoring for [arg2]. | Informational |
| FQXHMCP5760I | User [arg1] removed failover monitoring for [arg2]. | Informational |
| FQXHMCP5770I | User [arg1] started all failover monitoring. | Informational |
| FQXHMCP5780I | User [arg1] restarted all failover monitoring. | Informational |
| FQXHMCP5790I | User [arg1] stopped all failover monitoring. | Informational |
| FQXHMCR0002I | Job [arg1] was updated | Informational |
| FQXHMCR0003I | The web service is now available for general use. | Informational |
| FQXHMCR0004I | The rest api is now available for general use. | Informational |
| FQXHMCR0005I | The management server date and time were changed by user [arg1] at IP address [arg2]. | Informational |
| FQXHMCR0006I | The management server date and time were not successfully changed by user [arg1] at IP address [arg2]. | Informational |
| FQXHMCR0007I | Management server date and time is synchronized to the NTP server. | Informational |
| FQXHMCR0008I | Management server date and time is not synchronized to the NTP server. | Informational |
| FQXHMCR0011I | User [arg1] at IP address [arg2] mounted the sshfs mount point - [arg3]. | Informational |
| FQXHMCR0012I | User [arg1] at IP address [arg2] un-mounted the sshfs mount point - [arg3]. | Informational |
| FQXHMCR0013I | User [arg1] at IP address [arg2] import server [arg3] host key. | Informational |
| FQXHMCR0014I | User [arg1] at IP address [arg2] failed to mount sshfs mount point [arg3]. | Informational |
| FQXHMCR0015I | User [arg1] at IP address [arg2] failed to un-mount sshfs mount point [arg3]. | Informational |
| FQXHMCR0020I | User [arg1] at IP address [arg2] successfully enabled [arg3] service in the Lenovo XClarity Administrator. | Informational |
| FQXHMCR0021I | User [arg1] at IP address [arg2] successfully disabled [arg3] service in the Lenovo XClarity Administrator. | Informational |
| FQXHMCR0022I | User [arg1] at IP address [arg2] failed to enable [arg3] service in the Lenovo XClarity Administrator. | Informational |
| FQXHMCR0023I | User [arg1] at IP address [arg2] failed to disable [arg3] service in the Lenovo XClarity Administrator. | Informational |
| FQXHMCR0024I | The XClarity Administrator properties file contains invalid key values. | Informational |
| FQXHMCR0030I | User [arg1] successfully enable [arg2] service watchdog monitoring in the Lenovo XClarity Administrator. | Informational |
| FQXHMCR0031I | User [arg1] unsuccessfully enable [arg2] service watchdog monitoring in the Lenovo XClarity Administrator. | Informational |
| FQXHMCR0032I | User [arg1] successfully disable [arg2] service watchdog monitoring in the Lenovo XClarity Administrator. | Informational |
| FQXHMCR0033I | User [arg1] unsuccessfully disable [arg2] service watchdog monitoring in the Lenovo XClarity Administrator. | Informational |
| FQXHMCR0104I | Call home service connectivity has been restored | Informational |
| FQXHMDE0001I | User {0} started management of storage {1}. | Informational |
| FQXHMDI0001I | User [arg1] unmanaged chassis with UUID [arg2] (IP: [arg3]). | Informational |
| FQXHMDI0002I | User [arg1] has managed chassis with UUID [arg2] (IP: [arg3]) | Informational |
| FQXHMDI0018I | User [arg1] started management of chassis with UUID [arg2] (IP: [arg3]) with managed authentication enabled and manually entered credentials. | Informational |
| FQXHMDI0019I | User [arg1] started unmanagement of chassis with UUID [arg2] (IP: [arg3]). | Informational |
| FQXHMDI0021I | User [arg1] requested forced management of the chassis with UUID [arg2] (IP: [arg3]), which is already managed by Lenovo XClarity Administrator. The chassis will be unmanaged with force and then managed again. | Informational |
| FQXHMDI0024I | Children of chassis [arg1] unmanaged endpoint with UUID [arg2] (IP: {3}) during chassis unmanage task. | Informational |
| FQXHMDI0025I | SLP-broadcast discovery worker updated the list of unmanaged endpoints. | Informational |
| FQXHMDI0026I | A failure occurred when updating the password for user [arg1] on endpoint with UUID [arg2] (IP: [arg3]). | Informational |
| FQXHMDI0027I | User [arg1] started management of chassis with UUID [arg2] (IP: [arg3]) and managed authentication enabled and stored credentials [arg4]. | Informational |
| FQXHMDI0028I | User [arg1] started management of chassis with UUID [arg2] (IP: [arg3]) with managed authentication disabled and stored credentials [arg4]. | Informational |
| FQXHMDI0033I | User [arg1] unmanaged switch [arg2]. | Informational |
| FQXHMDI0034I | User [arg1] has managed switch [arg2] | Informational |
| FQXHMDI0035I | User [arg1] started unmanagement of switch [arg2] | Informational |
| FQXHMDI0036I | User [arg1] started management of switch [arg2] | Informational |
| FQXHMDI0041I | The request to set Single Sign On feature failed on server [arg1] | Informational |
| FQXHMDI0050I | The health of the SSD [arg1] in bay [arg2] of the RAID configuration [arg3] is back to normal. | Informational |
| FQXHMDI0060I | Server [arg1] was changed from the untrusted to trusted state. | Informational |
| FQXHMDI0061J | Server [arg1] was changed from the trusted to untrusted state because of [arg2]. | Informational |
| FQXHMDI0071I | A ThinkEdge server with machine type {1} and UUID {0} was discovered. | Informational |
| FQXHMDI0101I | User [arg1] unmanaged server with UUID [arg2] (IP: [arg3]). | Informational |
| FQXHMDI0102I | User [arg1] has managed server with UUID [arg2] (IP: [arg3]) | Informational |
| FQXHMDI0118I | User [arg1] started management of server with UUID [arg2] (IP: [arg3]) and managed authentication enabled. | Informational |
| FQXHMDI0119I | User [arg1] started unmanagement of server with UUID [arg2] (IP: [arg3]) | Informational |
| FQXHMDI0121I | User [arg1] requested forced management of the server with UUID [arg2] (IP: [arg3]), which is already managed by Lenovo XClarity Administrator. The server will be unmanaged with force and then managed again. | Informational |
| FQXHMDI0126G | The request by user [arg1] to manage server [arg2] resulted in no action, because node bay is already occupied by server - [arg3] | Informational |
| FQXHMDI0127I | The request by user [arg1] to manage device [arg2] resulted in no action, because IP address [arg3] is already used by the device with UUID [arg4]. | Informational |
| FQXHMDI0130I | User [arg1] started management of server with UUID [arg2] (IP: [arg3]) and managed authentication enabled and stored credentials [arg4]. | Informational |
| FQXHMDI0131I | User [arg1] started management of server with UUID [arg2] (IP: [arg3]) with managed authentication disabled and stored credentials [arg4]. | Informational |
| FQXHMDI0133I | The request by user [arg1] to manage device [arg2] (with IP address [arg3]) resulted in no action, because the device is already managed by this management server. | Informational |
| FQXHMDI0301I | User [arg1] unmanaged storage [arg2]. | Informational |
| FQXHMDI0302I | User [arg1] has managed storage [arg2] | Informational |
| FQXHMDI0319I | User [arg1] started unmanagement of storage [arg2] | Informational |
| FQXHMDI0501I | User [arg1] at IP address [arg2] enabled data collection service. | Informational |
| FQXHMDI0502I | User [arg1] at IP address [arg2] disabled data collection service. | Informational |
| FQXHMDI0600I | Job [arg1] has been updated. | Informational |
| FQXHMDM0001I | Inventory has changed [arg1]. | Informational |
| FQXHMDM0002I | Cabinet related has changed [arg1]. | Informational |
| FQXHMDM0003I | Connectivity to [arg1] [arg2] has been lost. UUID is [arg3]. | Informational |
| FQXHMDM0004I | Connectivity to endpoint [arg1] has been restored. Endpoint is [arg2]. | Informational |
| FQXHMDM0005I | The management NTP server or time zone information or both failed to push to device with UUID [arg1] (IP: [arg2]) | Informational |
| FQXHMDM0006I | The NTP settings could not be pushed to device with UUID [arg1] (IP: [arg2]) because the firmware is not compatible. | Informational |
| FQXHMDM0020I | User [arg1] from remote address [arg2] created resource group [arg3]. | Informational |
| FQXHMDM0021I | User [arg1] from remote address [arg2] successfully edit resource group [arg3]. | Informational |
| FQXHMDM0022I | User [arg1] from remote address [arg2] removed resource group [arg3]. | Informational |
| FQXHMDM0125I | User [arg1] requested a power action [arg2] - on device [arg3]. [arg4] | Informational |
| FQXHMDM0126I | User [arg1] set boot order - [arg2] - on device [arg3]. [arg4] | Informational |
| FQXHMDM0127I | User [arg1] requested a cryptography/NIST action [arg2] on device [arg3]. [arg4] | Informational |
| FQXHMDM0128I | User [arg1] requested a power capping action [arg2] on device [arg3]. [arg4] | Informational |
| FQXHMDM0129I | User [arg1] performed an inventory property change action on device [arg2]. [arg3] | Informational |
| FQXHMDM0130I | User [arg1] requested a CMM failover operation on device [arg2]. | Informational |
| FQXHMDM0131I | A power action started by user [arg1] was sent successfully to device [arg2]. [arg3] | Informational |
| FQXHMDM0132I | A boot order operation started by user [arg1] completed successfully on device [arg2]. [arg3] | Informational |
| FQXHMDM0133I | A cryptography/NIST action initiated by user [arg1] completed successfully on device [arg2]. [arg3] | Informational |
| FQXHMDM0134I | A power capping action initiated by user [arg1] completed successfully on device [arg2]. [arg3] | Informational |
| FQXHMDM0135I | An inventory property change action started by user [arg1] completed successfully on device [arg2]. [arg3] | Informational |
| FQXHMDM0136I | A CMM failover operation started by user [arg1] completed successfully on device [arg2].. | Informational |
| FQXHMDM0137I | An LED operation that was started by user [arg1] completed successfully on device [arg2].. | Informational |
| FQXHMDM0154I | The SSH console session was started by user [arg1] on switch [arg2]. | Informational |
| FQXHMDM0156I | The stored credentials for [arg1] were changed by [arg2] at [arg3]. | Informational |
| FQXHMDM0157I | The configuration data was updated successfully. | Informational |
| FQXHMDM0158I | The role groups allowed to access [arg1] were changed by [arg2] at [arg3]. | Informational |
| FQXHMDM0159I | The "public access" property for [arg1] was changed by [arg2] at [arg3]. | Informational |
| FQXHMDM0160I | The managed authentication enabled/disabled setting was changed for [arg1] by [arg2] at [arg3]. | Informational |
| FQXHMDM0161I | The security descriptor was changed for [arg1] by [arg2] at [arg3]. | Informational |
| FQXHMDM0162I | The configuration definitions was updated successfully. | Informational |
| FQXHMDM0163I | The connection between the management server and the management controller [arg1] is offline. Reason : [arg2] | Informational |
| FQXHMDM0163J | The connection between the management server and the management controller [arg1] is offline. | Informational |
| FQXHMDM0164I | The connection between the management server and the management controller [arg1] was restored. | Informational |
| FQXHMDM0165I | The device health state changed from [arg1] to [arg2]. | Informational |
| FQXHMDM0173I | The secure erase drive initiated for server {arg1}. | Informational |
| FQXHMDM0174I | The secure erase drive completed successfully for server {arg1}. | Informational |
| FQXHMDM0175I | The SFTP port enabled successfully for server {arg1}. | Informational |
| FQXHMDM0176I | The SFTP port disabled successfully for server {arg1}. | Informational |
| FQXHMDM0177I | The DNS and FQDN configuration initiated for server {arg1}. | Informational |
| FQXHMDM0179I | The MPFA Health Status is {arg1} for server {arg2}. | Informational |
| FQXHMDM0180I | The Core Inventory Service initialization completed successfully. | Informational |
| FQXHMEM0101I | The Audit log has wrapped, because it has reached the maximum size limit of [arg1]. | Informational |
| FQXHMEM0102I | The Audit log has reached 80% of the maximum size ([arg1] events). | Informational |
| FQXHMEM0103I | The Audit log has been cleared successfully by user [arg1] at IP address [arg2]. | Informational |
| FQXHMEM0104I | The Audit log maximum size has been changed from [arg1] to [arg2] by user [arg3] at IP address [arg4]. | Informational |
| FQXHMEM0201I | The event log has wrapped, because it has reached the maximum size limit of [arg1]. | Informational |
| FQXHMEM0202I | The event log has reached 80% of the maximum size ([arg1] events). | Informational |
| FQXHMEM0203I | The event log has been cleared by user [arg1] at IP address [arg2]. | Informational |
| FQXHMEM0204I | The event log maximum size has been changed from [arg1] to [arg2] by user [arg3] at IP address [arg4]. | Informational |
| FQXHMEM0205I | The events with type [arg1] from the event log have been cleared by user [arg2] at IP address [arg3]. | Informational |
| FQXHMEM0208I | An [arg1] exclusion filter with id [arg2] has been created by user [arg3] at IP address [arg4]. | Informational |
| FQXHMEM0209I | The [arg1] exclusion filter with id [arg2] has been modified by user [arg3] at IP address [arg4]. | Informational |
| FQXHMEM0210I | The [arg1] exclusion filter with id [arg2] has been deleted by user [arg3] at IP address [arg4]. | Informational |
| FQXHMEM0211I | Monitor [arg1] has been created by user [arg2] at IP address [arg3]. | Informational |
| FQXHMEM0212I | Monitor [arg1] has been modified by user [arg2] at IP address [arg3]. | Informational |
| FQXHMEM0213I | Monitor [arg1] has been deleted by user [arg2] at IP address [arg3]. | Informational |
| FQXHMEM0214I | Test event for monitor [arg1]. | Informational |
| FQXHMEM0316I | User [arg1] at IP Address [arg2] has successfully created a new predefined event filter called [arg3]. | Informational |
| FQXHMEM0317I | User [arg1] at IP Address [arg2] has successfully edit predefined event filter called [arg3]. | Informational |
| FQXHMEM0318I | User [arg1] at IP Address [arg2] has successfully deleted the predefined event filter called [arg3]. | Informational |
| FQXHMEM0319I | User [arg1] at IP Address [arg2] has modified the configuration of pusher called [arg3]. | Informational |
| FQXHMEM0320I | User [arg1] at IP Address [arg2] reset pusher called [arg3] to the default configuration. | Informational |
| FQXHMEM0321I | User [arg1] has made a new subscription on pusher [arg2]. | Informational |
| FQXHMEM0322I | User [arg1] has deleted a subscription on pusher [arg2]. | Informational |
| FQXHMEM0402I | Test event for the IOS push service. | Informational |
| FQXHMEM0403I | Test event for the Android push service. | Informational |
| FQXHMEM0404I | Test event for the WebSocket push service. | Informational |
| FQXHMEM0405I | Test event for the [arg1] IOS subscriber. | Informational |
| FQXHMEM0406I | Test event for the [arg1] Android subscriber. | Informational |
| FQXHMEM0407I | Test event for the [arg1] Websocket subscriber. | Informational |
| FQXHMEM0408I | An informational alert was asserted on device [arg1] with alert ID [arg2]. | Informational |
| FQXHMEM0411I | An informational alert was deasserted on device [arg1] with alert ID [arg2]. | Informational |
| FQXHMEM0412I | A warning alert was deasserted on device [arg1] with alert ID [arg2]. | Informational |
| FQXHMEM0413I | A critical alert was deasserted on device [arg1] with alert ID [arg2]. | Informational |
| FQXHMEM0414I | An unknown Informational event was generated on [arg1]. For more information, see the device documentation. | Informational |
| FQXHMEM0415I | An unknown Warning event was generated on [arg1]. For more information, see the device documentation. | Informational |
| FQXHMEM0416I | An unknown Critical event was generated on [arg1]. For more information, see the device documentation. | Informational |
| FQXHMEM9007I | The creation of the monitor was successful. | Informational |
| FQXHMEM9008I | The monitor was updated successfully. | Informational |
| FQXHMEM9009I | The monitor was reset successfully. | Informational |
| FQXHMEM9027I | The operation completed successfully. | Informational |
| FQXHMEM9056I | The creation of the monitor was successful. | Informational |
| FQXHMEM9058I | Informational | |
| FQXHMEM9059I | There are no DM Storage managed. | Informational |
| FQXHMEM9060I | There are no devices managed. | Informational |
| FQXHMEM9061I | The server thrown exception while trying to retrieve the list of devices. | Informational |
| FQXHMFC0011I | Pre-deployment validation completed successfully for all specified servers. | Informational |
| FQXHMFC0013I | All server preparation for image deployment has completed successfully. | Informational |
| FQXHMFC0014I | Started monitoring image deployment. | Informational |
| FQXHMFC0016I | Operating system deployment completed successfully on server {0}. | Informational |
| FQXHMFC0017I | Operating system deployment has completed for all specified servers. | Informational |
| FQXHMFC0038I | Management Server is checking the bundle file. | Informational |
| FQXHMFC0041I | A node profile {0} was created successfully for image deployment. | Informational |
| FQXHMFC0042I | A bootable ISO image was created successfully for operating system {0} with image name {1}. | Informational |
| FQXHMFC0043I | Bootable ISO image {0} mounted successfully to server {1}. | Informational |
| FQXHMFC0044I | The UEFI boot order sequence was modified successfully for server {0}. | Informational |
| FQXHMFC0045I | Restarting server {0} to boot from the mounted ISO image {1} and perform operating system installation. | Informational |
| FQXHMFC0046I | Preparing server {0} to boot to the installation environment completed successfully. | Informational |
| FQXHMFC0051I | Bootable ISO image {0} mounted successfully to server {1}(1). | Informational |
| FQXHMFC0074I | The operating system deployment process will be using the {0} method for assigning an IP address when configuring the deployed operating system. | Informational |
| FQXHMFC0118I | The running job was canceled successfully. | Informational |
| FQXHMFC0120I | OS deployment to server ({0}) has been started. | Informational |
| FQXHMFC0133I | The running job of importing OS image {0} was canceled successfully. | Informational |
| FQXHMFC0134I | Uploading the file {0} to the OS images repository. | Informational |
| FQXHMFC0135I | Copying the file {0} to the OS images repository. | Informational |
| FQXHMFC0136I | Management Server is checking the checksum of the uploaded image {0}. | Informational |
| FQXHMFC0137I | The file {0} was imported to the OS images repository successfully. | Informational |
| FQXHMFC0138I | Importing the operating system {0} was canceled by user {1}. | Informational |
| FQXHMFC0146I | The management server is waiting for the next import request. | Informational |
| FQXHMFC0149I | Importing the operating system was canceled by user {0}. | Informational |
| FQXHMFC0158I | The operating system deployment process status has not changed for {0} minutes. | Informational |
| FQXHMFC0159I | Deployment updated with MAC address {0}.. | Informational |
| FQXHMFC0160I | The running job of importing OS image was canceled successfully. | Informational |
| FQXHMFC0161I | Uploading the file to the OS images repository. | Informational |
| FQXHMFC0162I | Uploading the file to the OS images repository. | Informational |
| FQXHMFC0164I | The file {0} was imported to management server successfully. | Informational |
| FQXHMFC0191I | The management server is waiting for beginning the export custom profiles process. | Informational |
| FQXHMFC0193I | Exporting the custom profile. | Informational |
| FQXHMFC0194I | The custom profile was exported successfully. | Informational |
| FQXHMFC0213I | Some predefined device drivers and boot-option files were updated. Any customized os-image profiles using these files were automatically updated to include the new files. | Informational |
| FQXHMFC0222I | Custom post-installation scripts started on server {0}. | Informational |
| FQXHMFC0223I | Custom post-installation script {0} started on server {1}. | Informational |
| FQXHMFC0224I | Custom post-installation script {0} completed on server {1}. | Informational |
| FQXHMFC0225I | Custom post-installation scripts completed on server {0}. | Informational |
| FQXHMFC0228I | The custom profile has completed successfully. | Informational |
| FQXHMFC0231I | The installation environment was created successfully. | Informational |
| FQXHMFC0232I | Preparing the installation environment for the operating system. | Informational |
| FQXHMFC0233I | Installing the operating system on server {0}. | Informational |
| FQXHMFC0234I | Starting post-installation steps on server {0}). | Informational |
| FQXHMFC0235I | Restarting server {0}. | Informational |
| FQXHMFC0236I | The initial restart to the deployed operating system completed successfully. | Informational |
| FQXHMFC0237I | Downloading software payloads on server {0} to {1}. | Informational |
| FQXHMFC0238I | Downloading software payload {0}. | Informational |
| FQXHMFC0239I | Finished downloading software payload {0}. | Informational |
| FQXHMFC0241I | Finished downloading software payloads on server {0} to {1}. | Informational |
| FQXHMFC0246I | Operating system deployment stopped with errors. | Informational |
| FQXHMFC0247I | Pre-deployment validation completed successfully for server {0} with UUID: {1}. | Informational |
| FQXHMFC0248I | Deployed network settings are IP Mode: {0}, IP Address: {1}, Subnet Mask: {2}, Gateway Address: {3}, DNS1: {4}, DNS2: {5}, MTU: {6}. | Informational |
| FQXHMFC0250I | Deployed node settings are Host name: {0}, MAC address: {1}, VLAN ID: {2}, Storage: {3}. | Informational |
| FQXHMFC0256I | Installing custom device drivers on server {0}. | Informational |
| FQXHMFC0257I | Installing custom device driver {0} on server {1}. | Informational |
| FQXHMFC0258I | Successfully installed custom device driver {0} on server {1}. | Informational |
| FQXHMFC0260I | Installing custom device drivers on server {0} is complete. | Informational |
| FQXHMFC0262I | The boot files and driver files that are associated with {0} were overwritten by a bundle file that was imported by user {1}. | Informational |
| FQXHMFC0280I | Extracting software payloads on server {0} to {1}. | Informational |
| FQXHMFC0281I | Extracting software payload {0}. | Informational |
| FQXHMFC0282I | Finished extracting software payload {0}. | Informational |
| FQXHMFC0284I | Finished extracting software payloads on server {0} to {1}. | Informational |
| FQXHMFC0292I | Custom profile reported: {0}. | Informational |
| FQXHMFC0295I | No data retrieved due to license restriction. | Informational |
| FQXHMFC8602I | The image deployment job has been started. | Informational |
| FQXHMFC8605I | The following job has been created and started successfully: {0} | Informational |
| FQXHMFC8606I | Deployment in progress | Informational |
| FQXHMFC8608I | Operating-system credentials must be set. | Informational |
| FQXHMFC8875I | User {0} has started operating system deployment of {1} to node {2}. | Informational |
| FQXHMFC8877I | Operating system {0}] was deployed to node {1} by user {2}. | Informational |
| FQXHMFC8878I | User {0} modified the OS deployment default credentials. | Informational |
| FQXHMFC8879I | User {0} modified the OS deployment network mode. | Informational |
| FQXHMFC8880I | Operating system {0} was imported by user {1}. | Informational |
| FQXHMFC8881I | Operating system {0} was deleted by user {1}. | Informational |
| FQXHMFC8882I | The deployment of operating system {0} to node {1} was canceled by user {2}. | Informational |
| FQXHMJM0001I | Job [arg1] with id [arg2] was created. | Informational |
| FQXHMJM0002I | Job [arg1] was updated. | Informational |
| FQXHMJM0003I | Job [arg1] with id [arg2] was deleted. | Informational |
| FQXHMJM0004I | User [arg1] at IP address [arg2] created job schedule [arg3]. | Informational |
| FQXHMJM0006I | User [arg1] at IP address [arg2] updated job schedule [arg3]. | Informational |
| FQXHMJM0008I | User [arg1] at IP address [arg2] set the state to [arg3] for job schedule [arg4]. | Informational |
| FQXHMJM0010I | User [arg1] at IP address [arg2] called Run Now procedure for job schedule [arg3]. | Informational |
| FQXHMJM0012I | User [arg1] at IP address [arg2] cloned the job schedule [arg3]. | Informational |
| FQXHMJM0014I | User [arg1] at IP address [arg2] removed the following job schedule configurations: [arg3]. | Informational |
| FQXHMJM0016I | The management server launched the job(s) [arg1] for job scheduler [arg2] successfully. | Informational |
| FQXHMJM0018I | User [arg1] at IP address [arg2] successfully postponed job [arg3]. | Informational |
| FQXHMJM0026I | User [arg1] successfully deleted the following job: [arg2]. | Informational |
| FQXHMJM0027I | User [arg1] successfully deleted the following jobs: [arg2]. | Informational |
| FQXHMJM0028I | User [arg1] failed to delete the following job: [arg2]. | Informational |
| FQXHMJM0029I | User [arg1] failed to delete the following jobs: [arg2]. | Informational |
| FQXHMMF0003I | Metrics data collection for all DM Storage managed with ID [arg1] has finished. | Informational |
| FQXHMNM0125I | Management Server started by [arg1]. | Informational |
| FQXHMNM0126I | Management Server is shutdown by user [arg1] at IP address [arg2]. | Informational |
| FQXHMNM0127I | Management Server is put into single-user mode by user [arg1] at IP address [arg2]. | Informational |
| FQXHMNM0128I | Management Server is restarted by user [arg1] at IP address [arg2]. | Informational |
| FQXHMNM0129I | Management Server is put into unsupported state by user [arg1] at IP address [arg2]. | Informational |
| FQXHMNM90001I | The connection test was a success. | Informational |
| FQXHMRC0010I | User {0} has opened a Remote Control session to server {1}. | Informational |
| FQXHMRC0011I | User {0} has opened a remote media session to server {1}. | Informational |
| FQXHMSC0001I | User [arg1] updated L2 interfaces [arg2] with success. | Informational |
| FQXHMSC0002G | User [arg1] set an empty range of L2 interfaces [arg2]. | Informational |
| FQXHMSC0003G | User [arg1] was unable to get L2 interfaces from switch with the error message [arg2]. | Informational |
| FQXHMSC0004G | The range definition [arg2] given by user [arg1] did not produce any valid interfaces. | Informational |
| FQXHMSC0005G | User [arg1] tried to deploy the template but switch firmware version is too low and does not support [arg2] | Informational |
| FQXHMSC0006G | User [arg1] got response [arg2] from switch when updating interface [arg3] | Informational |
| FQXHMSC0101I | User [arg1] deployed Global Configuration with success. | Informational |
| FQXHMSC0102G | User [arg1] got response [arg2] from switch when updating LACP priority. | Informational |
| FQXHMSC0103G | User [arg1] got response [arg2] from switch when updating global tagNative. | Informational |
| FQXHMSC0104F | User [arg1] tried to deploy the template but switch firmware version is too low and does not support [arg2] | Informational |
| FQXHMSC0201I | User [arg1] deployed PortChannel Advanced Configuration with success. | Informational |
| FQXHMSC0202G | User [arg1] got response [arg2] from switch when deploying PortChannel Advanced Configuration Template. | Informational |
| FQXHMSC0203G | User [arg1] got response [arg2] from switch when updating portchannel [arg3]. | Informational |
| FQXHMSC0204G | User [arg1] tried to deploy the template but switch firmware version is too low and does not support LACP individual. | Informational |
| FQXHMSC0301I | User [arg1] deployed PortChannel Basic Configuration with success. | Informational |
| FQXHMSC0302G | User [arg1] gave an empty interfaces list. | Informational |
| FQXHMSC0303G | User [arg1] got response [arg2] from switch when checking to see if portchannel [arg3] exists. | Informational |
| FQXHMSC0304G | User [arg1] was unable to get L2 Interfaces from switch when deploying Portchannel Basic Configuration Template with the message [arg2]. | Informational |
| FQXHMSC0305G | The range definition [arg2] given by user [arg1] did not produce any valid interfaces. | Informational |
| FQXHMSC0306G | User [arg1] got an invalid response [arg2] from the switch. | Informational |
| FQXHMSC0307G | User [arg1] gave an incompatible port mode [arg2] with current port mode [arg3] on the switch | Informational |
| FQXHMSC0308G | User [arg1] got response [arg2] from switch when updating portchannel [arg3]. | Informational |
| FQXHMSC0309G | User [arg1] got response [arg2] from switch when creating portchannel [arg3]. | Informational |
| FQXHMSC0401I | User [arg1] deleted portchannels [arg2] with success. | Informational |
| FQXHMSC0402G | User [arg1] was unable to get portchannel list from switch with the message [arg2]. | Informational |
| FQXHMSC0403G | The range definition [arg2] given by user [arg1] did not produce any valid portchannels. | Informational |
| FQXHMSC0404G | User [arg1] was unable to delete any portchannels [arg3] having the response [arg2]. | Informational |
| FQXHMSC0405F | User [arg1] deleted portchannels [arg2] with success and with failure for [arg4] with the response [arg3]. | Informational |
| FQXHMSC0501I | User [arg1] deployed successfully the Spine Leaf Template. | Informational |
| FQXHMSC0502I | User [arg1] deployed successfully the Spine Node Template. | Informational |
| FQXHMSC0503G | User [arg1] gave an empty port list. | Informational |
| FQXHMSC0504G | User [arg1] tried to deploy the template but switch firmware version is too low and does not support Global BGP. | Informational |
| FQXHMSC0506G | User [arg1] got an error [arg2] when deleting current AS number [arg3] from switch. | Informational |
| FQXHMSC0507G | User [arg1] got response [arg2] from switch when setting BGP AS number [arg3]. | Informational |
| FQXHMSC0508G | User [arg1] got response [arg2] from switch when enabling BGP unnumbered globally. | Informational |
| FQXHMSC0509G | User [arg1] got response [arg2] from switch when enabling BGP unnumbered on interface [arg3]. | Informational |
| FQXHMSC0510G | User [arg1] got response [arg2] from switch when setting interface [arg3] as routed port. | Informational |
| FQXHMSC0601I | User [arg1] deployed successfully the VLAG Advanced Configuration Template. | Informational |
| FQXHMSC0602F | The VLAG Advanced Configuration Template that the user [arg1] deployed has no effect. | Informational |
| FQXHMSC0603G | User [arg1] got an invalid response [arg2] from switch when deploying VLAG Advanced Configuration Template. | Informational |
| FQXHMSC0604G | User [arg1] got response [arg2] from switch when setting VLAG healthcheck parameters. | Informational |
| FQXHMSC0605G | User [arg1] got response [arg2] from switch when trying to enable VLAG to set TIERID. | Informational |
| FQXHMSC0606G | User [arg1] got response [arg2] from switch when trying to disable VLAG to set TIERID. | Informational |
| FQXHMSC0607G | User [arg1] got response [arg2] from switch when setting VLAG parameters. | Informational |
| FQXHMSC0701I | User [arg1] deployed successfully the VLAG Instance Configuration Template. | Informational |
| FQXHMSC0702F | The VLAG Instance Configuration Template that the user [arg1] deployed has no effect. | Informational |
| FQXHMSC0703G | User [arg1] got an invalid response [arg2] from switch when deploying VLAG Instance Configuration Template. | Informational |
| FQXHMSC0704G | User [arg1] got response [arg2] from switch when [arg3] instance [arg4]. | Informational |
| FQXHMSC0801I | User [arg1] deployed successfully the VLAG Instance Delete Template. | Informational |
| FQXHMSC0802F | The VLAG Instance [arg2] the user [arg1] wanted to delete does not exist on the switch. | Informational |
| FQXHMSC0803G | User [arg1] got response [arg2] from switch when checking if instance [arg3] exists. | Informational |
| FQXHMSC0804G | User [arg1] got response [arg2] from switch when deleting instance [arg3]. | Informational |
| FQXHMSC0901I | User [arg1] deployed successfully the VLAG Peers Configuration Template. | Informational |
| FQXHMSC0902F | The VLAG Peers Configuration Template that the user [arg1] deployed has no effect. | Informational |
| FQXHMSC0903G | User [arg1] got response [arg2] from switch when getting current healthcheck parameters. | Informational |
| FQXHMSC0904G | User [arg1] got response [arg2] from switch when updating healthcheck parameters. | Informational |
| FQXHMSC0905G | User [arg1] got response [arg2] from switch when getting current ISL settings. | Informational |
| FQXHMSC0906G | User [arg1] got response [arg2] from switch when updating ISL settings. | Informational |
| FQXHMSC0907G | User [arg1] got response [arg2] from switch when getting current VLAG parameters. | Informational |
| FQXHMSC0908G | User [arg1] got response [arg2] from switch when updating VLAG parameters. | Informational |
| FQXHMSC1001I | User [arg1] added successfully the interfaces [arg2] in vlans [arg3]. | Informational |
| FQXHMSC1002F | The VLAN Configuration Template that the user [arg1] deployed has no effect. | Informational |
| FQXHMSC1003G | User [arg1] was unable to get interfaces from switch when deploying VLAN Configuration Template with the message [arg2]. | Informational |
| FQXHMSC1004G | User [arg1] was unable to get portchannels from switch when deploying VLAN Configuration Template with the message [arg2]. | Informational |
| FQXHMSC1005G | Range definition given by user [arg1] did not produce any valid interfaces to update. | Informational |
| FQXHMSC1006G | User [arg1] got an invalid response [arg2] from switch when deploying VLAN Configuration Template. | Informational |
| FQXHMSC1007G | User [arg1] got response [arg2] from switch when creating new VLAN [arg3]. | Informational |
| FQXHMSC1008G | User [arg1] got response [arg2] from switch when updating interface [arg3]. | Informational |
| FQXHMSC1101I | User [arg1] deleted VLANs [arg2] with success. | Informational |
| FQXHMSC1102F | User [arg1] deleted VLANs [arg2] with success and with failure for [arg4] with the response [arg3]. | Informational |
| FQXHMSC1103F | User [arg1] gave an empty list of VLAN IDs for VLAN Delete Template. | Informational |
| FQXHMSC1104G | User [arg1] was unable to get current VLANs from switch when deploying VLAN Delete Template with the message [arg2]. | Informational |
| FQXHMSC1105G | User [arg1] was unable to delete any VLANs [arg3] having the response [arg2]. | Informational |
| FQXHMSC1201I | User [arg1] deployed successfully the VLAN Properties Template. | Informational |
| FQXHMSC1202F | The VLAN Properties that the user [arg1] deployed has no effect. | Informational |
| FQXHMSC1203G | The VLAN [arg2] that the user [arg1] wanted to deployed the template does not exist. | Informational |
| FQXHMSC1204G | User [arg1] got an invalid response [arg2] from switch when getting VLAN properties. | Informational |
| FQXHMSC1205G | User [arg1] got response [arg2] from switch when updating VLAN [arg3] properties. | Informational |
| FQXHMSC1301I | User [arg1] removed interfaces [arg2] from VLANs [arg3] with success. | Informational |
| FQXHMSC1302F | The range definition given by user [arg1] did not produce any valid interfaces/portchannels. | Informational |
| FQXHMSC1303F | The VLAN Remove Template that the user [arg1] deployed has no effect. | Informational |
| FQXHMSC1304G | User [arg1] was unable to get interfaces from switch when deploying VLAN Remove Template with the message [arg2]. | Informational |
| FQXHMSC1305G | User [arg1] was unable to get portchannels from switch when deploying VLAN Remove Template with the message [arg2]. | Informational |
| FQXHMSC1307G | User [arg1] got response [arg2] from switch when updating interface [arg3]. | Informational |
| FQXHMSC1400G | User [arg1] failed to apply template because the switch operating system (ENoS) does not support configuration templates. | Informational |
| FQXHMSE0001I | The request completed successfully. | Informational |
| FQXHMSE0007G | Security policy state on chassis [arg1] is Pending. | Informational |
| FQXHMSE0008I | Security policy level on [arg1] matches security policy level [arg2] on the management server. | Informational |
| FQXHMSE0009I | Minimum SSL/TLS protocol level on [arg1] matches minimum SSL/TLS protocol levels client [arg2] and server [arg3] on the management server. | Informational |
| FQXHMSE0010I | Cryptographic mode on [arg1] matches cryptographic mode [arg2] on the management server. | Informational |
| FQXHMSE0105I | Server certificate replaced by user ID [arg1] at IP address [arg2]. | Informational |
| FQXHMSE0106I | A new server certificate was generated by user ID [arg1] at IP address [arg2]. | Informational |
| FQXHMSE0112I | Trust certificate for chassis [arg1] installed by user ID [arg2] at IP address [arg3]. | Informational |
| FQXHMSE0120I | The request to resolve the untrusted connection was not successful. | Informational |
| FQXHMSE0130I | A new CA root certificate was generated by user ID [arg1] at IP address [arg2]. | Informational |
| FQXHMSE0131I | A new server certificate was uploaded by user ID [arg1] at IP address [arg2]. | Informational |
| FQXHMSE0132I | The request to generate the certificate authority root certificate was successful. Server certificate regeneration is required. | Informational |
| FQXHMSE0133I | The request to generate a new server certificate was successful. | Informational |
| FQXHMSE0134I | The request to upload a new server certificate was successful. | Informational |
| FQXHMSE0141I | The endpoint certificate does not match the currently trusted certificate. | Informational |
| FQXHMSE0142I | The request to upload a new server certificate is processing. | Informational |
| FQXHMSE0143I | A new server certificate was uploaded to the temporary key store by user ID [arg1] at IP address [arg2]. | Informational |
| FQXHMSE0144I | A new server certificate was installed from the temporary key store by user ID [arg1] at IP address [arg2]. | Informational |
| FQXHMSE0146I | The request to install a new server certificate is processing. | Informational |
| FQXHMSE0147I | The request to retrieve SSH keys was not successful. | Informational |
| FQXHMSE0149I | The request to retrieve SSH keys has been processed. | Informational |
| FQXHMSE0150I | The request to retrieve SSH keys was not successful. | Informational |
| FQXHMSE0200I | The login was successful for user ID [arg1] at IP address [arg2]. | Informational |
| FQXHMSE0201I | The logout was successful for user ID [arg1] at IP address [arg2]. | Informational |
| FQXHMSE0202I | The login was unsuccessful for user ID [arg1] at IP address [arg2]. | Informational |
| FQXHMSE0203I | Account [arg1] was created by user ID [arg2] at IP address [arg3]. | Informational |
| FQXHMSE0204I | Account [arg1] was changed by user ID [arg2] at IP address [arg3]. | Informational |
| FQXHMSE0205I | The password was changed by user ID [arg1] at IP address [arg2] for user ID [arg3]. | Informational |
| FQXHMSE0206I | Account [arg1] was deleted by user ID [arg2] at IP address [arg3]. | Informational |
| FQXHMSE0207I | The values of the following system properties have changed. [arg1] | Informational |
| FQXHMSE0208I | The session [arg1] was terminated for user ID [arg2] at IP address [arg3] by [arg4] at IP address [arg5]. | Informational |
| FQXHMSE0209I | Account [arg1] is temporarily locked. | Informational |
| FQXHMSE0210I | The authentication attempt by user ID {0} failed. | Informational |
| FQXHMSE0240I | The request to add the user ID {0} completed successfully. | Informational |
| FQXHMSE0250I | The request to change the password for user ID {0} completed successfully. | Informational |
| FQXHMSE0260I | The request to modify the user ID {0} completed successfully. | Informational |
| FQXHMSE0270I | The request to delete the user ID {0} completed successfully. | Informational |
| FQXHMSE0300I | Security policy level was changed by user ID [arg1] at IP address [arg2] to [arg3]. | Informational |
| FQXHMSE0303I | Minimum password length was changed to [arg1] by user ID [arg2] at IP address [arg3]. | Informational |
| FQXHMSE0304I | Maximum password length was changed to [arg1] by user ID [arg2] at IP address [arg3]. | Informational |
| FQXHMSE0305I | The minimum password reuse cycle setting was changed to [arg1] by user ID [arg2] at IP address [arg3]. | Informational |
| FQXHMSE0306I | The password expiration period setting was changed to [arg1] days by user ID [arg2] at IP address [arg3]. | Informational |
| FQXHMSE0307I | The inactivity alert period setting was changed to [arg1] minutes by user ID [arg2] at IP address [arg3]. | Informational |
| FQXHMSE0308I | The minimum password change interval setting changed to [arg1] hours by user ID [arg2] at IP address [arg3]. | Informational |
| FQXHMSE0309I | The maximum number of login failures setting changed to [arg1] by user ID [arg2] at IP address [arg3]. | Informational |
| FQXHMSE0310I | The lockout period after maximum login failures setting changed to [arg1] minutes by user ID [arg2] at IP address [arg3]. | Informational |
| FQXHMSE0311I | The simple password rules setting was changed to [arg1] by user ID [arg2] at IP address [arg3]. | Informational |
| FQXHMSE0312I | The minimum different characters in passwords setting changed to [arg1] by user ID [arg2] at IP address [arg3]. | Informational |
| FQXHMSE0313I | The force user to change password on first login setting changed to [arg1] by user ID [arg2] at IP address [arg3]. | Informational |
| FQXHMSE0314I | The password expiration warning period setting changed to [arg1] by user ID [arg2] at IP address [arg3]. | Informational |
| FQXHMSE0331I | The request to change security-policy level to {0} completed successfully. | Informational |
| FQXHMSE0332I | The maximum concurrent sessions setting changed to [arg1] by user ID [arg2] at IP address [arg3]. | Informational |
| FQXHMSE0337I | The minimum password complexity rules setting changed to [arg1] by user ID [arg2] at IP address [arg3]. | Informational |
| FQXHMSE0400I | A node account created for user ID [arg1] by user ID [arg2] at IP address [arg3]. | Informational |
| FQXHMSE0401I | A node account for user ID [arg1] changed by user ID [arg2] at IP address [arg3]. | Informational |
| FQXHMSE0402I | A node account for user ID [arg1] deleted by user ID [arg2] at IP address [arg3]. | Informational |
| FQXHMSE0403I | Centralized node account management was enabled for chassis [arg1] by user ID [arg2] at IP address [arg3]. | Informational |
| FQXHMSE0404I | Node account management responsibility was transferred to chassis [arg1]. | Informational |
| FQXHMSE0405I | A node account for user ID [arg1] was activated on chassis [arg2] by user ID [arg3] at IP address [arg4]. | Informational |
| FQXHMSE0406I | A node account for user ID [arg1] was deactivated on chassis [arg2] by user ID [arg3] at IP address [arg4]. | Informational |
| FQXHMSE0503I | The minimum TLS protocol level settings for [arg1] were changed to client=[arg2], server=[arg3], OS deploy=[arg4] by user ID [arg5] at IP address [arg6]. | Informational |
| FQXHMSE0504I | The cryptographic mode for [arg1] was changed to [arg2] by user ID [arg3] at IP address [arg4]. | Informational |
| FQXHMSE0510I | The minimum TLS protocol level settings were changed to client={arg1}, server={arg2} on {arg3} devices of which {arg4} are successfully, see the full devices list in the log of job {arg5} | Informational |
| FQXHMSE0511I | Security mode is upgraded to {arg1} Mode on {arg2} devices of which {arg3} are successfully, see the full devices list in the log of job {arg4} | Informational |
| FQXHMSE0512I | Ipmioverkcs for {arg1} was {arg2} by user ID {arg3} at IP address {arg4}. | Informational |
| FQXHMSE0600I | An unsecure connection to the server at address {0}, port {1} completed successfully. | Informational |
| FQXHMSE0601I | A secure connection to the server at address {0}, port {1} was successful. | Informational |
| FQXHMSE0604I | Binding to the server using the distinguished name {0} completed successfully. | Informational |
| FQXHMSE0606I | A search for user entries on the server completed successfully. | Informational |
| FQXHMSE0608I | A search for role group entries on the server completed successfully. | Informational |
| FQXHMSE0616I | The LDAP server returned the following response to a test search for user entries. | Informational |
| FQXHMSE0617I | The LDAP server returned the following response to a test search for role group entries. | Informational |
| FQXHMSE0620I | The LDAP server selection method setting changed to [arg1] by user ID [arg2] at IP address [arg3]. | Informational |
| FQXHMSE0621I | A preconfigured LDAP server, [arg1], was added by user ID [arg2] at IP address [arg3]. | Informational |
| FQXHMSE0622I | The LDAP root distinguished name setting was changed to [arg1] by user ID [arg2] at IP address [arg3]. | Informational |
| FQXHMSE0623I | The Active Directory forest name setting was changed to "[arg1]" by user ID [arg2] at IP address [arg3]. | Informational |
| FQXHMSE0624I | The LDAP domain name setting was changed to "[arg1]" by user ID [arg2] at IP address [arg3]. | Informational |
| FQXHMSE0625I | The LDAP client distinguished name setting was changed to [arg1] by user ID [arg2] at IP address [arg3]. | Informational |
| FQXHMSE0626I | The LDAP client password setting was changed by user ID [arg1] at IP address [arg2]. | Informational |
| FQXHMSE0627I | The LDAP SSL setting was changed to [arg1] by user ID [arg2] at IP address [arg3]. | Informational |
| FQXHMSE0628I | The LDAP trusted certificate [arg1] was replaced by user ID [arg2] at IP address [arg3]. | Informational |
| FQXHMSE0629I | The LDAP trusted certificate [arg1] was deleted by user ID [arg2] at IP address [arg3]. | Informational |
| FQXHMSE0630I | The LDAP user authentication method setting changed to [arg1] by user ID [arg2] at IP address [arg3]. | Informational |
| FQXHMSE0631I | The LDAP user authentication method was set to [arg1] after a change attempted by user ID [arg2] at IP address [arg3] failed. | Informational |
| FQXHMSE0632I | The LDAP binding method setting changed to [arg1] by user ID [arg2] at IP address [arg3]. | Informational |
| FQXHMSE0633I | The LDAP User Search Attribute setting was changed to [arg1] by user ID [arg2] at IP address [arg3]. | Informational |
| FQXHMSE0634I | The LDAP Group Search Attribute setting was changed to [arg1] by user ID [arg2] at IP address [arg3]. | Informational |
| FQXHMSE0635I | The LDAP setting to use servers as Global Catalogs was changed to [arg1] by user ID [arg2] at IP address [arg3]. | Informational |
| FQXHMSE0636I | The LDAP Group Name Attribute setting was changed to [arg1] by user ID [arg2] at IP address [arg3]. | Informational |
| FQXHMSE0642I | The requested user authentication method was set successfully. | Informational |
| FQXHMSE0651I | The domain name service returned the following response to a {0} service request. | Informational |
| FQXHMSE0698K | One or more external LDAP servers are now reachable. | Informational |
| FQXHMSE0700I | Authorization group [arg1] was created by user ID [arg2] at IP address [arg3]. | Informational |
| FQXHMSE0701I | Authorization group [arg1] was changed by user ID [arg2] at IP address [arg3]. | Informational |
| FQXHMSE0702I | Authorization group [arg1] was deleted by user ID [arg2] at IP address [arg3]. | Informational |
| FQXHMSE0723I | The request to modify the role group {0} completed successfully. | Informational |
| FQXHMSE0724I | The request to delete the role group {0} completed successfully. | Informational |
| FQXHMSE0750I | The resource access control has been [arg1] by user ID [arg2] at the following IP address [arg3]. | Informational |
| FQXHMSE0751I | Access to resource [arg1] was granted by user ID [arg2] at IP address [arg3] for the following role groups: [arg4]. | Informational |
| FQXHMSE0752I | Access to resource [arg1] was modified by user ID [arg2] at IP address [arg3]. | Informational |
| FQXHMSE0753I | Access to resource [arg1] was removed by user ID [arg2] at IP address [arg3]. | Informational |
| FQXHMSE0796I | Resource Access Control was disabled by user [arg1] at IP address [arg2]. | Informational |
| FQXHMSE0797I | Resource Access Control was enabled by user [arg1] at IP address [arg2]. | Informational |
| FQXHMSE0798I | The following role groups were added to the list of default Resource Access Control role groups by user [arg1] at IP address [arg2]: [arg3]. | Informational |
| FQXHMSE0799I | The following role groups were removed from the list of default Resource Access Control role groups by user [arg1] at IP address [arg2]: [arg3]. | Informational |
| FQXHMSE0800I | Service provider metadata has been regenerated by [arg1]. | Informational |
| FQXHMSE0801I | Identity provider metadata has been regenerated by [arg1]. | Informational |
| FQXHMSE0802I | SAML single sign on has been disabled by [arg1]. | Informational |
| FQXHMSE0803I | SAML single sign on has been enabled by [arg1]. | Informational |
| FQXHMSE0910I | Stored credentials with ID [arg1] and the following user name and description were added by user [arg2] at IP address [arg3]: [arg4] - [arg5]. | Informational |
| FQXHMSE0911I | Stored credentials with ID [arg1] and the following user name and description were removed by user [arg2] at IP address [arg3]: [arg4] - [arg5]. | Informational |
| FQXHMSE0912I | The user name of the stored credentials with ID [arg1] was changed to the following by user [arg2] at IP address [arg3]: [arg4] - [arg5]. | Informational |
| FQXHMSE0913I | The description of the stored credentials with ID [arg1] was changed to the following by user [arg2] at IP address [arg3]: [arg4] - [arg5]. | Informational |
| FQXHMSE0914I | The password of the stored credentials with ID [arg1] and the following user name and description was changed by user [arg2] at IP address [arg3]: [arg4] - [arg5]. | Informational |
| FQXHMSE0916I | Head of Stack feature supported for firmware [arg1]. | Informational |
| FQXHMSE0917I | [arg1] enabled encapsulation for all future managed devices. | Informational |
| FQXHMSE0918I | [arg1] disabled encapsulation for all future managed devices. | Informational |
| FQXHMSE0919I | Custom role [arg1] was created by user [arg2] at IP address [arg3]. | Informational |
| FQXHMSE0920I | Custom role [arg1] was modified by user [arg2] at IP address [arg3]. | Informational |
| FQXHMSE0921I | Custom role [arg1] was deleted by user [arg2] at IP address [arg3]. | Informational |
| FQXHMSE0929I | The SSO login was successful for server [arg1]. | Informational |
| FQXHMSE0930I | The SSO login failed for server [arg1]. | Informational |
| FQXHMSE0931I | Functions enabled after system became compliant. | Informational |
| FQXHMSE0932I | New license was added to the system by [arg1] | Informational |
| FQXHMSE0933I | License was removed from system by [arg1] | Informational |
| FQXHMSE0934I | Single Sign On for servers was enabled by [arg1] | Informational |
| FQXHMSE0935I | Single Sign On for servers was disabled by [arg1] | Informational |
| FQXHMSE0936I | A new CyberArk certificate was generated by user ID [arg1] at IP address [arg2]. | Informational |
| FQXHMSE0937I | A new Single Sign On certificate was generated by user ID [arg1] at IP address [arg2]. | Informational |
| FQXHMSP00001I | The job [arg1] that was requested by user [arg2] to retrieve the chassis switch ports on device [arg3] was successful.[arg4] | Informational |
| FQXHMSS0001I | All Service Data files have been downloaded by user [arg1] at IP address [arg2]. | Informational |
| FQXHMSS0003I | Service Data file [arg1] was downloaded by user [arg2] at IP address [arg3]. | Informational |
| FQXHMSS1001I | The log level of logger [arg1] has been changed from [arg2] to [arg3] by user [arg4] at IP address [arg5]. | Informational |
| FQXHMSS1003I | The log size of logger [arg1] has been changed from [arg2] to [arg3] by user [arg4] at IP address [arg5]. | Informational |
| FQXHMSS1005I | The number of Service Data files to keep has been changed by user [arg1], at IP address [arg2], from [arg3] to [arg4]. | Informational |
| FQXHMSS1007I | The request from user [arg1], at IP address [arg2], to change the suppression time from [arg3] to [arg4] was successful. | Informational |
| FQXHMSS1009I | The number of informational Service Data files to keep has been changed by user [arg1], at IP address [arg2], from [arg3] to [arg4]. | Informational |
| FQXHMSS1011I | A Service Data file with the type [arg1] and dump configuration ID [arg2] was collected on the server. | Informational |
| FQXHMSS1012I | A Service Data file with the type [arg1] and a custom configuration was collected on the server. | Informational |
| FQXHMSS1014I | The dumped archives have been cleared from the server by user [arg1] at IP address [arg2]. | Informational |
| FQXHMSS1016I | The request from user [arg1] at IP address [arg2] to change the number of logs archives for appender [arg3] to [arg4] was successful. | Informational |
| FQXHMSS1017J | The request from user [arg1] at IP address [arg2] to change the number of logs archives for appender [arg3] to [arg4] has failed. | Informational |
| FQXHMSS1018I | The request from user [arg1] at IP address [arg2] to restore the log settings to the default values was successful. | Informational |
| FQXHMSS1020I | The generation of Service Data archive for user [arg1] at IP address [arg2] finished successfully. | Informational |
| FQXHMSS1022I | User [arg1] at IP address [arg2] initiated the generation of a Service Data file. | Informational |
| FQXHMSS1028I | The request by user [arg1] at IP address [arg2] to upload a file was successful. | Informational |
| FQXHMSS1029I | The request by user [arg1] at IP address [arg2] to change the Call Home configuration was successful. | Informational |
| FQXHMSS1030I | The configuration for Call Home was successfully saved. Forwarder {0} was created and forwarder {1} was updated with this configuration. | Informational |
| FQXHMSS1031I | User [arg1] at IP address [arg2] enabled Call Home. | Informational |
| FQXHMSS1032I | The configuration for Call Home was successfully saved. Forwarder {0} was created but forwarder {1} failed to be created with this configuration. | Informational |
| FQXHMSS1033I | User [arg1] at IP address [arg2] disabled Call Home. | Informational |
| FQXHMSS1034I | The configuration for Call Home was successfully saved. Forwarders {0} and {1} were created with this configuration. | Informational |
| FQXHMSS1035I | User [arg1] at IP address [arg2] reset the Call Home configuration. | Informational |
| FQXHMSS1048I | The request by user [arg1] at IP address [arg2] to save the contact information for Call Home on endpoint with UUID [arg3] was successful. | Informational |
| FQXHMSS1049I | The request by user [arg1] at IP address [arg2] to update the contact information for Call Home on endpoint with UUID [arg3] was successful. | Informational |
| FQXHMSS1050I | The request by user [arg1] at IP address [arg2] to clear the contact information for Call Home on endpoint with UUID [arg3] was successful. | Informational |
| FQXHMSS1051I | User [arg1] at IP address [arg2] enabled the tracing mechanism. | Informational |
| FQXHMSS1052I | User [arg1] at IP address [arg2] disabled the tracing mechanism. | Informational |
| FQXHMSS1053I | User [arg1] at IP address [arg2] enabled the auto dumping mechanism. | Informational |
| FQXHMSS1054I | User [arg1] at IP address [arg2] disabled the auto dumping mechanism. | Informational |
| FQXHMSS1055I | The Call Home test finished successfully. | Informational |
| FQXHMSS1057I | The Call Home test is pending. | Informational |
| FQXHMSS1060I | The Service Data archive has been successfully collected from endpoint {0}. | Informational |
| FQXHMSS1061I | Call Home can be enabled. The configuration is correct. | Informational |
| FQXHMSS1062I | User {0} from IP Address {1} has requested to download Service Data from endpoint {2}. | Informational |
| FQXHMSS1064I | The specified tickets have successfully been deleted. | Informational |
| FQXHMSS1066I | The list of tickets have been deleted successfully. | Informational |
| FQXHMSS1073I | The server is updating ticket {0} state. Remaining updates {1} out of {2}. | Informational |
| FQXHMSS1074I | The server has successfully updated all the problem tickets. | Informational |
| FQXHMSS1077I | Initializing Problem Number Update task. | Informational |
| FQXHMSS1078I | The changes were made successfully. | Informational |
| FQXHMSS1079I | The collection of the Service Data archive from endpoint {0} is ongoing. | Informational |
| FQXHMSS1081I | The file has been successfully added to the problem number attachment queue. | Informational |
| FQXHMSS1085I | The disable all managed endpoints Call Home state task is in pending. | Informational |
| FQXHMSS1086I | The enable all managed endpoints Call Home state task is in pending. | Informational |
| FQXHMSS1087I | The server has successfully disabled all Call Home states on all managed endpoints. | Informational |
| FQXHMSS1088I | The server has successfully enabled all Call Home states on all managed endpoints. | Informational |
| FQXHMSS1092I | Enabling Call Home state on the managed endpoints. Successfully changed state on {0} endpoints and failed on {1}. | Informational |
| FQXHMSS1093I | Disabling Call Home state on the managed endpoints. Successfully changed state on {0} endpoints and failed on {1}. | Informational |
| FQXHMSS1094I | There are no tickets that can be refreshed. | Informational |
| FQXHMSS1115I | The Call Home is enabled by the primary CMM. The Call Home is done via the primary CMM. | Informational |
| FQXHMSS1116I | The Call Home is disabled by the primary CMM. | Informational |
| FQXHMSS1117I | The Call Home State is unknown for this component. | Informational |
| FQXHMSS1118I | The Call Home State is unavailable for this component. | Informational |
| FQXHMSS1119I | The Call Home is enabled on this server. | Informational |
| FQXHMSS1120I | The Call Home is disabled on this server. | Informational |
| FQXHMSS1121I | The Call Home State is unknown for this server. | Informational |
| FQXHMSS1123I | The Call Home endpoint test call is in pending. | Informational |
| FQXHMSS1124I | The Call Home endpoint call is in pending. | Informational |
| FQXHMSS1125I | The Call Home endpoint test call is running. | Informational |
| FQXHMSS1126I | The Call Home endpoint call is running. | Informational |
| FQXHMSS1127I | Generate Problem Number. | Informational |
| FQXHMSS1128I | Collect Endpoint Service Data Archive. | Informational |
| FQXHMSS1129I | Upload Service Data Archive to Generated Problem Number. | Informational |
| FQXHMSS1131I | The Call Home test call for endpoint {0} ended successfully. The associated problem ticked number is {1}. | Informational |
| FQXHMSS1132I | The Call Home call for endpoint {0} ended successfully. The associated problem ticked number is {1}. | Informational |
| FQXHMSS1214I | Generated test event for {0} successfully. | Informational |
| FQXHMSS1219I | The configuration for Call Home was successfully saved. Forwarder {0} was updated with this configuration successfully. | Informational |
| FQXHMSS1220I | Not Set | Informational |
| FQXHMSS1221I | Disabled | Informational |
| FQXHMSS1222I | Enabled | Informational |
| FQXHMSS1226I | The Call Home State is loading for this component. | Informational |
| FQXHMSS1227I | The Call Home State is loading for this server. | Informational |
| FQXHMSS1229I | Not Set | Informational |
| FQXHMSS1244I | Disabled | Informational |
| FQXHMSS1245I | Enabled | Informational |
| FQXHMSS1246I | The configuration for Call Home was successfully saved. Forwarders {0} and {1} were updated with this configuration successfully. | Informational |
| FQXHMSS1247I | The Call Home is enabled on this switch. | Informational |
| FQXHMSS1248I | The Call Home is disabled on this switch. | Informational |
| FQXHMSS1249I | The Call Home State is unknown for this switch. | Informational |
| FQXHMSS1250I | The Call Home State is unavailable for this switch. | Informational |
| FQXHMSS1251I | The Call Home State is loading for this switch. | Informational |
| FQXHMSS1252I | The Call Home is enabled on this storage. | Informational |
| FQXHMSS1253I | The Call Home is disabled on this storage. | Informational |
| FQXHMSS1254I | The Call Home State is unknown for this storage. | Informational |
| FQXHMSS1255I | The Call Home State is unavailable for this storage. | Informational |
| FQXHMSS1256I | The Call Home State is loading for this storage. | Informational |
| FQXHMSS1260I | Not Set | Informational |
| FQXHMSS1261I | Disabled | Informational |
| FQXHMSS1262I | Enabled | Informational |
| FQXHMSS1263I | Lenovo Upload Facility cannot be enabled due to configuration values that are not valid. | Informational |
| FQXHMSS1264I | The configuration for Lenovo Upload Facility was successfully saved. Forwarder {0} was created with this configuration. | Informational |
| FQXHMSS1265I | The configuration for Lenovo Upload Facility was successfully updated and saved. | Informational |
| FQXHMSS1266I | The configuration for Lenovo Upload Facility was not saved. | Informational |
| FQXHMSS1267I | The Lenovo Upload Facility function was not reset. | Informational |
| FQXHMSS1268I | The Lenovo Upload Facility function has been reset. | Informational |
| FQXHMSS1274I | Lenovo Warranty Database (World Wide) | Informational |
| FQXHMSS1275I | Lenovo Warranty Web Service | Informational |
| FQXHMSS1276I | Lenovo Warranty Database (China only) | Informational |
| FQXHMSS1279I | The test was successful. | Informational |
| FQXHMSS1282I | Not Supported | Informational |
| FQXHMSS1283I | Ticket was opened by a user. | Informational |
| FQXHMSS2001I | Event [arg1] generated on [arg2] has been added to the Service Data collecting process. | Informational |
| FQXHMSS2005I | The Service Data archive for event [arg1] from [arg2] has been collected successfully. | Informational |
| FQXHMSS2006I | Call Home Service Forwarder [arg1] started creating the Ticket for event [arg2] generated on [arg3]. | Informational |
| FQXHMSS2007I | Call Home Service Forwarder [arg1] created Ticket [arg2] for event [arg3] generated on [arg4]. | Informational |
| FQXHMSS2009I | Call Home Service Forwarder [arg1] started uploading the collected Service Data to Ticket [arg2]. | Informational |
| FQXHMSS2010I | Call Home Service Forwarder [arg1] uploaded the Service Data to Ticket [arg2] successfully. | Informational |
| FQXHMSS2012I | SFTP Service Forwarder [arg1] started uploading the collected Service Data to [arg2]:[arg3]. | Informational |
| FQXHMSS2013I | SFTP Service Forwarder [arg1] uploaded the collected Service Data to [arg2]:[arg3] successfully. | Informational |
| FQXHMSS2016I | Service Forwarder [arg1] has been created by user [arg2] at IP address [arg3]. | Informational |
| FQXHMSS2017I | Service Forwarder [arg1] has been modified by user [arg2] at IP address [arg3]. | Informational |
| FQXHMSS2018I | Service Forwarder [arg1] has been deleted by user [arg2] at IP address [arg3]. | Informational |
| FQXHMSS2019I | The management server started collecting the Service Data archive for event [arg1] generated on [arg2]. | Informational |
| FQXHMSS2020I | Service Forwarder [arg1] has added the collected Service Data archive for event [arg2] generated on [arg3] in the pending queue. | Informational |
| FQXHMSS2021I | User [arg1] at IP address [arg2] has accepted the Service Data archive for event [arg3] generated on [arg4] for being processed by the active service forwarders. | Informational |
| FQXHMSS2022I | User [arg1] at IP address [arg2] has declined the Service Data archive for event [arg3] generated on [arg4] from being processed by the active service forwarders. | Informational |
| FQXHMSS2026I | User [arg1] at IP address [arg2] has successfully uploaded file [arg3] to Service Ticket [arg4]. | Informational |
| FQXHMSS2028I | The management server will skip creating a Ticket for event [arg1] generated on [arg2]. | Informational |
| FQXHMSS2035I | User [arg1] at IP Address [arg2] started the Call Home connectivity test. | Informational |
| FQXHMSS2036I | The Call Home connectivity test started by user [arg1] at IP Address [arg2] ended successfully. | Informational |
| FQXHMSS2038I | Lenovo Upload Facility Service Forwarder [arg1] started uploading the collected Service Data to [arg2] | Informational |
| FQXHMSS2039I | Lenovo Upload Facility Service Forwarder [arg1] uploaded the collected Service Data to [arg2] | Informational |
| FQXHMSS2043I | The request by user [arg1] at IP address [arg2] to save the Lenovo Upload Facility configuration was successful. | Informational |
| FQXHMSS2044I | The request by user [arg1] at IP address [arg2] to change the Lenovo Upload Facility configuration was successful. | Informational |
| FQXHMSS2045J | The request by user [arg1] at IP address [arg2] to change the Lenovo Upload Facility configuration was unsuccessful. | Informational |
| FQXHMSS2046I | User [arg1] at IP address [arg2] reset the Lenovo Upload Facility configuration. | Informational |
| FQXHMSS2048J | An upload of the file [arg1] to the Lenovo Upload Facility was initiated by user [arg2]. | Informational |
| FQXHMSS2049J | An upload of usage data to the Lenovo Upload Facility was initiated. | Informational |
| FQXHMSS2067I | Lenovo Call Home Forwarder and Lenovo Upload Facility Forwarder are disabled. | Informational |
| FQXHMSS2068I | Lenovo Call Home Forwarder is disabled. | Informational |
| FQXHMSS2069I | Lenovo Upload Facility Forwarder is disabled. | Informational |
| FQXHMSS2070I | Customer {0} has generated a Manual Software Call Home. | Informational |
| FQXHMSS2072I | Lenovo Call Home Forwarder and Lenovo Upload Facility Forwarder are disabled. | Informational |
| FQXHMSS2073I | Lenovo Upload Facility Forwarder is disabled. | Informational |
| FQXHMSS2075I | Forwarders {0} and {1} were created with this configuration. | Informational |
| FQXHMSS2076I | Forwarder {0} was created and forwarder {1} was updated with this configuration. | Informational |
| FQXHMSS2077I | Forwarder {0} was created but forwarder {1} failed to be created with this configuration. | Informational |
| FQXHMSS2078I | Forwarders {0} and {1} were updated with this configuration successfully. | Informational |
| FQXHMSS2079I | By enabling this forwarder, you are agreeing to send service data to Lenovo. If you do not agree, then please disable this forwarder. | Informational |
| FQXHMSS2080I | The Alert Period for warnings was updated successfully. | Informational |
| FQXHMSS2081I | Lenovo Call Home Forwarder does not exist. | Informational |
| FQXHMSS2083I | The file previously uploaded has been discarded. | Informational |
| FQXHMSS2093I | The customer number has been left blank. | Informational |
| FQXHMSS2094I | The customer number was verified. | Informational |
| FQXHMSS2103I | Case note successfully added to ticket. | Informational |
| FQXHMSS2109I | Attention: Call Home for this country requires a Lenovo Premier Support contract. For more information, contact your Lenovo representative or authorized business partner. | Informational |
| FQXHMSS2236I | Error State | Informational |
| FQXHMSS3035I | User [arg1] at IP Address [arg2] started the Lenovo Call Home connectivity test. | Informational |
| FQXHMSS3036I | The Lenovo Call Home connectivity test started by user [arg1] at IP Address [arg2] ended successfully. | Informational |
| FQXHMSS3038J | A Lenovo Call Home connection test has failed. Access token could not be retrieved. | Informational |
| FQXHMSS3039I | User [arg1] at IP Address [arg2] started a Manual Software Lenovo Call Home. | Informational |
| FQXHMSS3040J | A Lenovo Software Call Home Test has failed. The case could not be created. | Informational |
| FQXHMSS3041J | A Lenovo Software Call Home has failed. The case could not be created. | Informational |
| FQXHMSS3042J | A Lenovo Call Home Test has failed. The case could not be created. | Informational |
| FQXHMSS3043J | A Lenovo Manual Call Home has failed. The case could not be created. | Informational |
| FQXHMSS3044J | A Lenovo Call Home has failed. The case could not be created. | Informational |
| FQXHMSS3045I | A Lenovo Software Call Home Test has successfully completed. The case number is [arg1]. | Informational |
| FQXHMSS3046I | A Lenovo Software Call Home has successfully completed. The case number is [arg1]. | Informational |
| FQXHMSS3047I | A Lenovo Manual Call Home has successfully completed. The case number is [arg1]. | Informational |
| FQXHMSS3048I | A Lenovo Call Home Test has successfully completed. The case number is [arg1]. | Informational |
| FQXHMSS3049I | A Lenovo Call Home has successfully completed. The case number is [arg1]. The event that generates it, has the message: [arg2] and event id: [arg3] | Informational |
| FQXHMSS3050I | User [arg1] at IP Address [arg2] started a Manual Lenovo Call Home. | Informational |
| FQXHMSS3051I | User [arg1] at IP Address [arg2] started a Lenovo Call Home Test. | Informational |
| FQXHMSS3052I | User [arg1] at IP Address [arg2] started a Manual Software Lenovo Call Home Test. | Informational |
| FQXHMSS3053I | User [arg1] at IP address [arg2] has successfully uploaded file [arg3] to Lenovo Case [arg4]. | Informational |
| FQXHMSS3054I | The Lenovo Software Call Home Test has started uploading Service Data to case [arg1]. | Informational |
| FQXHMSS3055I | The Lenovo Software Call Home Test has successfully uploaded Service Data to case [arg1]. | Informational |
| FQXHMSS3056J | The Lenovo Software Call Home Test has failed to upload Service Data to case [arg1]. | Informational |
| FQXHMSS3057J | The Lenovo Software Call Home Test has failed to upload Service Data because Lenovo case could not be created. | Informational |
| FQXHMSS3058I | The Lenovo Software Call Home has started uploading Service Data to case [arg1]. | Informational |
| FQXHMSS3059I | The Lenovo Software Call Home has successfully uploaded Service Data to case [arg1]. | Informational |
| FQXHMSS3060J | The Lenovo Software Call Home has failed to upload Service Data to case [arg1]. | Informational |
| FQXHMSS3061J | The Lenovo Software Call Home has failed to upload Service Data because Lenovo case could not be created. | Informational |
| FQXHMSS3062I | The Lenovo Call Home Test has started uploading Service Data to case [arg1]. | Informational |
| FQXHMSS3063I | The Lenovo Call Home Test has successfully uploaded Service Data to case [arg1]. | Informational |
| FQXHMSS3064J | The Lenovo Call Home Test has failed to upload Service Data to case [arg1]. | Informational |
| FQXHMSS3065J | The Lenovo Call Home Test has failed to upload Service Data because Lenovo case could not be created. | Informational |
| FQXHMSS3066I | The Lenovo Call Home has started uploading Service Data to case [arg1]. | Informational |
| FQXHMSS3067I | The Lenovo Call Home has successfully uploaded Service Data to case [arg1]. | Informational |
| FQXHMSS3068J | The Lenovo Call Home has failed to upload Service Data to case [arg1]. | Informational |
| FQXHMSS3069J | The Lenovo Call Home has failed to upload Service Data because Lenovo case could not be created. | Informational |
| FQXHMSS3070I | User [arg1] at IP Address [arg2] started a Lenovo Call Home Pass Through. | Informational |
| FQXHMSS3071I | User [arg1] at IP Address [arg2] started a Lenovo Call Home Pass Through Test. | Informational |
| FQXHMSS3072J | A Lenovo Call Home Pass Through Test has failed. The case could not be created. | Informational |
| FQXHMSS3073J | A Lenovo Call Home Pass Through has failed. The case could not be created. | Informational |
| FQXHMSS3074I | A Lenovo Call Home Pass Through Test has successfully completed. The case number is [arg1]. | Informational |
| FQXHMSS3075I | A Lenovo Call Home Pass Through has successfully completed. The case number is [arg1]. | Informational |
| FQXHMSS3076I | Management Server will execute Call Home for the serviceable event [arg1] for device [arg2]. | Informational |
| FQXHMSS3077I | Management Server will not execute Call Home for the serviceable event [arg1] for device [arg2] because there is no forwarder to match device. | Informational |
| FQXHMSS3078I | Management Server will not execute Call Home for the serviceable event [arg1] for device [arg2] because there is already a ticket opened for this event and device. | Informational |
| FQXHMSS4001I | Internal service [arg1] terminated unexpectedly, and it has been restarted. Debug data on the termination has been collected and stored at [arg2] | Informational |
| FQXHMSS4011I | Internal service [arg1] terminated unexpectedly, and it has now been restarted. No debug data was collected. | Informational |
| FQXHMSS4016I | An IBM Manual Call Home has successfully completed. The problem record number is [arg1]. | Informational |
| FQXHMSS4017I | An IBM Call Home Test has successfully completed. The problem record number is [arg1]. | Informational |
| FQXHMSS4018I | A Call Home has successfully completed. The ticket number is [arg1]. | Informational |
| FQXHMSS4019I | An IBM Call Home Connection Test has successfully completed. The problem record number is [arg1]. | Informational |
| FQXHMSS4020J | A Manual Call Home has failed. The ticket could not be created. | Informational |
| FQXHMSS4021J | A Call Home Test has failed. The ticket could not be created. | Informational |
| FQXHMSS4022J | A Call Home has failed. The ticket could not be created. | Informational |
| FQXHMSS4023J | A Call Home Connection Test has failed. The ticket could not be created. | Informational |
| FQXHMSS4024J | The country has been successfully changed. | Informational |
| FQXHMSS4025J | The country could not be changed. | Informational |
| FQXHMSS5048I | User [arg1] at IP address [arg2] tried to enable Call Home, but a test must be done before. The test was launched. | Informational |
| FQXHMSS5049I | The Call Home test ended successfully. | Informational |
| FQXHMSS5051I | Call Home test was launched successfully. | Informational |
| FQXHMSS5052I | Call Home test generated by user [arg1] at IP address [arg2] ended successfully. | Informational |
| FQXHMSS5054I | User [arg1] at IP address [arg2] has successfully deleted problem record [arg3]. | Informational |
| FQXHMSS5055I | User [arg1] at IP address [arg2] has successfully deleted all the problem records. | Informational |
| FQXHMSS5056I | User [arg1] at IP address [arg2] has successfully changed the state of the auto dumping mechanism from [arg3] to [arg4]. | Informational |
| FQXHMSS5057I | User [arg1] at IP address [arg2] has successfully changed the state of the file tracing mechanism from [arg3] to [arg4]. | Informational |
| FQXHMSS5058I | User [arg1] at IP address [arg2] has successfully changed the Call Home number of retries from [arg3] to [arg4]. | Informational |
| FQXHMSS5059I | User [arg1] at IP address [arg2] has successfully changed the Call Home timeout between retries from [arg3] to [arg4]. | Informational |
| FQXHMSS5060I | User [arg1] at IP address [arg2] has successfully changed the Call Home file verification mode from [arg3] to [arg4]. | Informational |
| FQXHMSS5061I | Call Home event with ID [arg1] from component [arg2] has been added to the Call Home Processing queue. | Informational |
| FQXHMSS5063I | Call Home event with ID [arg1] from component [arg2] is being processed by the server Call Home task. | Informational |
| FQXHMSS5065I | Call Home event with ID [arg1] from component [arg2] was suppressed. Call Home aborted. | Informational |
| FQXHMSS5069I | Call Home event with ID [arg1] from component [arg2] has successfully been called home. The associated ticket number is [arg3]. | Informational |
| FQXHMSS5071I | Call Home event with ID [arg1] from component [arg2] will not be called home because the server Call Home function is disabled. | Informational |
| FQXHMSS5073I | Call Home event with ID [arg1] from component [arg2] will be removed from the Call Home queue because the Call Home function is disabled now. | Informational |
| FQXHMSS5081I | Call Home event with ID [arg1] from component [arg2] is being processed by the server Call Home task. The process is attaching the collected endpoint service data to ticket number [arg3]. | Informational |
| FQXHMSS5083I | Call Home event with ID [arg1] from component [arg2] is being processed by the server Call Home task. The process is attaching additional files to problem number [arg3]. | Informational |
| FQXHMSS5085I | The collected endpoint service data has been successfully attached to ticket number [arg1]. | Informational |
| FQXHMSS5086I | The additional file(s) have been successfully attached to ticket number [arg1]. | Informational |
| FQXHMSS5089I | Call Home test generated by user [arg1] at IP address [arg2] was launched successfully. | Informational |
| FQXHMSS5090I | User [arg1] at IP address [arg2] enabled Call Home. | Informational |
| FQXHMSS5091I | User [arg1] at IP address [arg2] disabled Call Home. | Informational |
| FQXHMSS5092I | The server suppressed Call Home call for event [arg1] generated on system [arg2]. | Informational |
| FQXHMSS5093I | Collecting the Service Data archive generated by event with ID [arg1] from endpoint [arg2] finished successfully. | Informational |
| FQXHMSS5101I | Event [arg1] received from system [arg2] was not called home. | Informational |
| FQXHMSS5103I | Test Event for Service Fowarder [arg1] generated by user [arg2] at ip address [arg3]. | Informational |
| FQXHMSS5104I | The warranty for [arg1] with the UUID [arg2] will expire in less than [arg3] days. | Informational |
| FQXHMSS5105I | The warranty for [arg1] with the UUID [arg2] is expired. | Informational |
| FQXHMSS5106I | An event was received from an endpoint that is not currently managed, at IP address [arg1]. This event has been ignored. | Informational |
| FQXHMSS5108I | Call Home and all other active serviceability functions for event [arg1] from system [arg2] were suppressed because the event matches one of the excluded events. | Informational |
| FQXHMSS5109I | The user [arg1] from IP address [arg2] has successfully enabled the option to suppress service forwarders for excluded events. | Informational |
| FQXHMSS5110I | The user [arg1] from IP address [arg2] has successfully disabled the option to suppress service forwarders for excluded events. | Informational |
| FQXHMSS5115I | User [arg1] from IP address [arg2] enabled the SSD Life Check Service. | Informational |
| FQXHMSS5116I | User [arg1] from IP address [arg2] disabled the SSD Life Check Service. | Informational |
| FQXHMSS5117I | User [arg1] from IP address [arg2] changed the warning threshold level for checking the remaining life of SDDs from [arg3] to [arg4]. | Informational |
| FQXHMSS5118I | User [arg1] from IP address [arg2] changed the error threshold level for checking the remaining life of SDDs from [arg3] to [arg4]. | Informational |
| FQXHMSS5119I | The warranty period was set successfully to : [arg1] days. | Informational |
| FQXHMSS5120I | A new bulletin event was raised. | Informational |
| FQXHMSS5121I | Call home was not triggered for device [arg1] as warranty is expired. | Informational |
| FQXHMSS9010I | There is approximately {0} Kilobytes that will be compressed and downloaded. | Informational |
| FQXHMSS9011I | There is approximately {0} Megabytes that will be compressed and downloaded. | Informational |
| FQXHMSS9012I | There is approximately {0} Gigabytes that will be compressed and downloaded. | Informational |
| FQXHMSS9013I | The granularity level has successfully been set to {0}. | Informational |
| FQXHMSS9014I | The Number of Logs to Archive has been set to status {0}. | Informational |
| FQXHMSS9016I | There is approximately {0} Kilobytes that will be compressed and downloaded. The user already downloaded an archive generated {2} second(s) ago. | Informational |
| FQXHMSS9017I | There is approximately {0} Megabytes that will be compressed and downloaded. The user already downloaded an archive generated {2} second(s) ago. | Informational |
| FQXHMSS9018I | There is approximately {0} Gigabytes that will be compressed and downloaded. The user already downloaded an archive generated {2} second(s) ago. | Informational |
| FQXHMSS9019I | There is approximately {0} Kilobytes that will be compressed and downloaded. The user already downloaded an archive generated {2} minute(s) ago. | Informational |
| FQXHMSS9020I | There is approximately {0} Megabytes that will be compressed and downloaded. The user already downloaded an archive generated {2} minute(s) ago. | Informational |
| FQXHMSS9021I | There is approximately {0} Gigabytes that will be compressed and downloaded. The user already downloaded an archive generated {2} minute(s) ago. | Informational |
| FQXHMST0001I | User {0} started management of storage {1}. | Informational |
| FQXHMUP1000I | The command completed successfully. | Informational |
| FQXHMUP1104I | Update setting {0} updated from {1} to {2}. | Informational |
| FQXHMUP1105I | Update setting [arg1] was updated from [arg2] to [arg3] by user [arg4]. | Informational |
| FQXHMUP2000I | The command completed successfully. | Informational |
| FQXHMUP2200I | This is a supported device. | Informational |
| FQXHMUP2301I | New devices were added to firmware Updates Inventory. [arg1]. | Informational |
| FQXHMUP2302I | Some devices were removed from the firmware Updates Inventory. [arg1]. | Informational |
| FQXHMUP2303I | Some components were added to the firmware Updates Inventory. [arg1]. | Informational |
| FQXHMUP2304I | Some components were removed from the firmware Updates Inventory. [arg1]. | Informational |
| FQXHMUP2305I | The firmware updates inventory has changed. [arg1]. | Informational |
| FQXHMUP2306I | The driver updates inventory has changed. [arg1]. | Informational |
| FQXHMUP2307I | The operating system driver updates repository has changed. [arg1]. | Informational |
| FQXHMUP2500I | Repository operation completed successfully. | Informational |
| FQXHMUP2507I | The repository operation was canceled successfully. | Informational |
| FQXHMUP2508I | The repository operation has started successfully. | Informational |
| FQXHMUP2509I | The repository operation is progressing normally. | Informational |
| FQXHMUP3006I | Policy operation completed successfully. | Informational |
| FQXHMUP3030I | Policy import completed successfully. | Informational |
| FQXHMUP3031I | Policy export completed successfully. | Informational |
| FQXHMUP3100I | New compliance data detected. [arg1]. | Informational |
| FQXHMUP4000I | The command completed successfully. | Informational |
| FQXHMUP4003I | Firmware Updates were started on system [arg1] by user [arg2]. | Informational |
| FQXHMUP4004I | Firmware Updates were started on management server [arg1] by user [arg2]. | Informational |
| FQXHMUP4005I | Firmware Updates were started on switch [arg1] by user [arg2]. | Informational |
| FQXHMUP4006I | The firmware was updated on system device [arg1] by user [arg2]. | Informational |
| FQXHMUP4007I | The firmware was updated on management server [arg1] by user [arg2]. | Informational |
| FQXHMUP4008I | The firmware was updated on switch device [arg1] by user [arg2]. | Informational |
| FQXHMUP4010I | PerformAction was started on the selected devices. | Informational |
| FQXHMUP4011I | Firmware Updates were started on the selected devices. | Informational |
| FQXHMUP4020I | PerformAction (simulation mode) was started on the selected devices. | Informational |
| FQXHMUP4021I | The firmware updates process (simulation mode) were started on the selected devices. | Informational |
| FQXHMUP4031I | The Cancel process was started on the selected devices. | Informational |
| FQXHMUP4032I | The Cancel process was started on the selected devices. | Informational |
| FQXHMUP4041I | PerformAction {0} was started on the selected devices. | Informational |
| FQXHMUP4051I | The removal of the completed jobs was successful. | Informational |
| FQXHMUP4052I | There are no completed jobs to remove. | Informational |
| FQXHMUP4091I | Update Status was obtained successfully. | Informational |
| FQXHMUP4092I | There are no firmware update tasks currently running. | Informational |
| FQXHMUP4093I | Update engine settings were obtained successfully. | Informational |
| FQXHMUP4094I | Update engine settings were set successfully. | Informational |
| FQXHMUP4095I | There were no Update engine settings to set. | Informational |
| FQXHMUP4101I | Firmware Updates were started on storage [arg1] by user [arg2]. | Informational |
| FQXHMUP4102I | The firmware was updated on storage [arg1] by user [arg2]. | Informational |
| FQXHMUP4151I | The firmware update was successful. | Informational |
| FQXHMUP4152I | The {0} firmware update was successful. | Informational |
| FQXHMUP4163I | The firmware update was skipped. The firmware for this device is already compliant. | Informational |
| FQXHMUP4164I | The firmware update was skipped. The selection for this device is Do Not Update. | Informational |
| FQXHMUP4167I | The firmware update was skipped. The firmware package was already applied. | Informational |
| FQXHMUP4211I | The firmware update on the Chassis Management Module was successful. | Informational |
| FQXHMUP4310I | The Flex System switch passed the verification step for firmware update. | Informational |
| FQXHMUP4311I | The firmware update on the Flex System switch was successful. | Informational |
| FQXHMUP4410I | The device firmware updates were successful. | Informational |
| FQXHMUP4411I | The primary management-controller firmware update was successful. | Informational |
| FQXHMUP4412I | The backup management-controller firmware update was successful. | Informational |
| FQXHMUP4413I | The primary management-controller restart was successful. | Informational |
| FQXHMUP4421I | The preboot Diagnostics firmware update was successful. | Informational |
| FQXHMUP4431I | The Primary uEFI firmware update was successful. | Informational |
| FQXHMUP4432I | The Backup uEFI firmware update was successful. | Informational |
| FQXHMUP4433I | The PSU firmware update was successful. | Informational |
| FQXHMUP4511I | The start of maintenance mode on the device was successful. | Informational |
| FQXHMUP4521I | The close of the maintenance mode operating system was successful. | Informational |
| FQXHMUP4531I | The device restart was successful. | Informational |
| FQXHMUP4535I | The device restart was not needed. | Informational |
| FQXHMUP4539I | The final action for device updates is complete. | Informational |
| FQXHMUP4541I | The prerequisites task was successful. | Informational |
| FQXHMUP4545I | The verification task was successful. | Informational |
| FQXHMUP4701I | The preparation for the inband components was successful. | Informational |
| FQXHMUP4707I | The close of the inband components session was successful. | Informational |
| FQXHMUP4709I | The {0} inband component firmware update was successful. | Informational |
| FQXHMUP4800I | The firmware update was successful. | Informational |
| FQXHMUP4840I | Update Complete | Informational |
| FQXHMUP4900I | Starting new process for taskid {0} Perform{1}. | Informational |
| FQXHMUP4910I | The power action was submitted successfully. | Informational |
| FQXHMUP4930I | The task has not started. | Informational |
| FQXHMUP4931I | The task is in progress for the specified device. | Informational |
| FQXHMUP4932I | The task was canceled. | Informational |
| FQXHMUP4933I | The task has completed successfully. | Informational |
| FQXHMUP4935I | No action required for this task. | Informational |
| FQXHMUP4936I | The task is currently awaiting user action for Pending Firmware Maintenance Mode. | Informational |
| FQXHMUP4937I | Restart the device to continue the update process. | Informational |
| FQXHMUP4940I | The firmware update was skipped. The hardware was not detected. | Informational |
| FQXHMUP4941I | No action required for this task unless there is a desire to force the update. To force the update, select the "Force update" option. | Informational |
| FQXHMUP4946I | Memory test is already enabled, setting is {0}, skip memory test config. | Informational |
| FQXHMUP4948I | Memory test enabled. | Informational |
| FQXHMUP4950I | Restore memory test settings succeeded. | Informational |
| FQXHMUP5000I | The command completed successfully. | Informational |
| FQXHMUP5011D | Unknown internal error. | Informational |
| FQXHMUP5011I | Mount media was started on the selected devices. | Informational |
| FQXHMUP5012D | Unknown internal error. | Informational |
| FQXHMUP5012I | Unmount media was started on the selected devices. | Informational |
| FQXHMUP5013D | Unknown internal error. | Informational |
| FQXHMUP5013I | Boot media was started on the selected devices. | Informational |
| FQXHMUP5100I | The operating system action completed successfully. | Informational |
| FQXHMUP5101I | Operating-system authentication was started on the selected devices. | Informational |
| FQXHMUP5102I | Operating-system compliance validation was started on the selected devices. | Informational |
| FQXHMUP5103I | OS device-driver updates were started on the selected devices. | Informational |
| FQXHMUP5200I | Perform {0} completed. {1} packages were updated. {2} succeed and {3} failed" | Informational |
| FQXHMUP5201I | The device-driver task has not started. | Informational |
| FQXHMUP5202I | The device-driver task is in progress for the specified device. | Informational |
| FQXHMUP5203I | The device-driver task was canceled. | Informational |
| FQXHMUP5204I | The device-driver task has completed successfully. | Informational |
| FQXHMUP5206I | No action required for this device-driver task. | Informational |
| FQXHMUP5207I | Start applying OS driver updates: {0}. | Informational |
| FQXHMUP5208I | Applying OS driver updates {0} completed. | Informational |
| FQXHMUP6010I | The packages have been downloaded: [arg1] by user [arg2]. | Informational |
| FQXHMUP6020I | The packages have been imported: [arg1] by user [arg2]. | Informational |
| FQXHMUP6021I | The packages have been imported: [arg1]; The packages have been discarded: [arg2] by user [arg3]. | Informational |
| FQXHMUP6022I | The packages have been discarded: [arg1] by user [arg2]. | Informational |
| FQXHMUP6030I | The packages have been deleted: [arg1] by user [arg2]. | Informational |
| FQXHMUP6040I | The following policy was created: [arg1] by user [arg2]. | Informational |
| FQXHMUP6041I | The following policy was modified: [arg1] by user [arg2]. | Informational |
| FQXHMUP6042I | The following policy was deleted: [arg1] by user [arg2]. | Informational |
| FQXHMUP6043I | Policy [arg1] was imported successfully by user [arg2]. | Informational |
| FQXHMUP6044I | Policy [arg1], which was imported by user [arg2], was discarded due to an unsafe policy name or a policy validation issue. | Informational |
| FQXHMUP6101I | The package [arg1] has been applied by user [arg2]. | Informational |
| FQXHMUP7500I | Repository operation completed successfully. | Informational |
| FQXHMUP7521I | The switch has network connectivity. | Informational |
| FQXHMUP7522I | The update package stack type matches the switch configuration. | Informational |
| FQXHMUP7523I | The stacked switch is the master switch. The firmware update can be applied. | Informational |
| FQXHMUP7524I | The firmware signature allows update. | Informational |
| FQXHMUP7525I | No other updates are in progress. | Informational |
| FQXHMUP7526I | The switch has the minimum firmware version that is required to support the update. | Informational |
| FQXHMUP7531I | Update package is compatible for this firmware version. | Informational |
| FQXHMUP7561I | The payload files were extracted successfully. | Informational |
| FQXHMUP7563I | Transferring main image to switch. | Informational |
| FQXHMUP7564I | Transferring boot image to switch. | Informational |
| FQXHMUP7565I | Requesting the switch to reset. | Informational |
| FQXHMUP7579I | The firmware update on the switch was successful. | Informational |
| FQXHMUP7599I | Generic Rackswitch firmware update message. | Informational |
| FQXHMUP7700I | The storage update completed successfully. | Informational |
| FQXHMUP7900I | The server has network connectivity. | Informational |
| FQXHMUP7925I | No other updates are in progress. | Informational |
| FQXHMUP7965I | Restarting the BMC. | Informational |
| FQXHMUP7966I | The update job canceled. | Informational |
| FQXHMUP7967I | The update job started. | Informational |
| FQXHMUP7979I | The image update successful. | Informational |
| FQXHMUP8000I | The management-server update operation completed successfully. | Informational |
| FQXHMUP8007I | The management-server update operation started successfully. | Informational |
| FQXHMUP8009I | The management-server update operation is progressing normally. | Informational |
| FQXHMUP8017I | The management-server updates repository operation was canceled successfully. | Informational |
| FQXHM0001J | Unknown message. | Warning |
| FQXHM0002J | The user name cannot be resolved. | Warning |
| FQXHM0003J | The user name is not valid. | Warning |
| FQXHM0004J | The POST request was not valid. | Warning |
| FQXHM0005J | The PUT request was not valid. | Warning |
| FQXHM0006J | Invalid request parameters. | Warning |
| FQXHM0007J | Invalid URL path. | Warning |
| FQXHM0008J | The list of countries for the specific language is not valid. | Warning |
| FQXHMCP1115J | Pattern [arg1] failed to deploy on [arg2]. | Warning |
| FQXHMCP1155J | Profile [arg1] could not be redeployed to [arg2]. | Warning |
| FQXHMCP1175J | Profile [arg1] could not be unassigned from [arg2]. | Warning |
| FQXHMCP1180J | Server configuration profile [arg1] is non-compliant. | Warning |
| FQXHMCP1185J | Server configuration profile [arg1] is non-compliant. | Warning |
| FQXHMCP1275J | Standby pool [arg1] has no servers available for failover. | Warning |
| FQXHMCP1315J | Local storage could not be reset to the default configuration. | Warning |
| FQXHMCR0001W | The IP address was changed on interface [arg1]. | Warning |
| FQXHMDE0001G | A trap alert destination subscription failure occurred when user {0} managed server {1} | Warning |
| FQXHMDE0002G | A trap alert destination unsubscription failure occurred when user {0} unmanaged server {1} | Warning |
| FQXHMDE0003G | Inventory data could not be retrieved from the endpoint {0} | Warning |
| FQXHMDE0010G | The SSL/TLS certificate provided by the {0} endpoint is not valid. | Warning |
| FQXHMDI0003G | A CIM subscription failure occurred after user [arg1] unmanaged chassis with UUID [arg2] (IP: [arg3]). | Warning |
| FQXHMDI0004G | The NTP server on chassis [arg2] could not be reset after user [arg1] unmanaged it. | Warning |
| FQXHMDI0005G | The request by user [arg1] to unmanage chassis with UUID [arg2] (IP: [arg3]) failed. | Warning |
| FQXHMDI0006G | The request by user [arg1] to manage chassis with UUID [arg2] (IP [arg3]) failed to setup failure on the management server. | Warning |
| FQXHMDI0007G | The request by user [arg1] to manage chassis [arg2] failed due to login lockout on the chassis. | Warning |
| FQXHMDI0008G | The request by user [arg1] to manage chassis [arg2] failed due to login failure to the chassis. | Warning |
| FQXHMDI0009G | The request by user [arg1] to manage chassis with UUID [arg2] (IP [arg3]) failed due to connection issues. | Warning |
| FQXHMDI0010G | The request by user [arg1] to manage chassis with UUID [arg2] (IP [arg3]) resulted in no action, because it is already being managed. | Warning |
| FQXHMDI0011G | The request by user [arg1] to manage chassis [arg2] did not complete due to a failure during inventory collection. | Warning |
| FQXHMDI0012G | The request by user [arg1] to manage chassis with UUID [arg2] (IP: [arg3]) failed because the management server was unable to retrieve the chassis' LDAP certificate. | Warning |
| FQXHMDI0013G | The request by user [arg1] to manage chassis with UUID [arg2] (IP: [arg3]) failed because the management server was unable to retrieve the chassis' CIM certificate. | Warning |
| FQXHMDI0014G | The request by user [arg1] to manage chassis with UUID [arg2] (IP: [arg3]) failed because the management server was unable to change the chassis security policy to match that of the server. | Warning |
| FQXHMDI0015G | The request by user [arg1] to manage chassis with UUID [arg2] (IP: [arg3]) failed because it was unable to set up centralized management (managed authentication). | Warning |
| FQXHMDI0016G | The request by user [arg1] to manage chassis with UUID [arg2] (IP: [arg3]) failed due to unknown failure. | Warning |
| FQXHMDI0017G | The request by user [arg1] to manage chassis with UUID [arg2] (IP: [arg3]) failed due to being unable to set the authentication mode of the server. | Warning |
| FQXHMDI0020I | The LDAP configuration data for chassis [arg2] failed to clean up after user [arg1] unmanaged it. | Warning |
| FQXHMDI0021G | The request by user [arg1] to manage chassis [arg2] failed when setting up group permissions on the chassis. | Warning |
| FQXHMDI0022G | The request by user [arg1] to manage chassis with UUID [arg2] (IP: [arg3]) failed when performing additional manage configuration information. | Warning |
| FQXHMDI0023G | Initial inventory collection by user [arg1] of chassis with UUID [arg2] (IP: [arg3]) did not complete successfully. | Warning |
| FQXHMDI0024G | Enabling local user accounts on endpoint [arg2] by user [arg1] failed. | Warning |
| FQXHMDI0026G | The request to update the password by user [arg1] on device with UUID [arg2] (IP: [arg3]) was not successful because of connection issues. | Warning |
| FQXHMDI0027G | User [arg1] cannot manage chassis with UUID [arg2] (IP: [arg3]) because of connection issues. | Warning |
| FQXHMDI0028G | The attempt by user [arg1] to manage chassis with UUID [arg2] (IP: [arg3]) was not successful. | Warning |
| FQXHMDI0029G | The request by user [arg1] to force the management of server [arg2] did not complete. | Warning |
| FQXHMDI0030G | The request by user [arg1] to force the management of the chassis [arg2] did not complete. | Warning |
| FQXHMDI0031G | Configuring CIM subscriptions to some nodes of the chassis failed after user [arg1] managed the chassis with UUID [arg2] (IP: [arg3]). | Warning |
| FQXHMDI0032G | Removing CIM subscriptions from some nodes of the chassis failed after user [arg1] unmanaged the chassis with UUID [arg2] (IP: [arg3]). | Warning |
| FQXHMDI0033G | The property [arg1] contains the unsupported character [arg2] . The following characters are not supported [arg3] | Warning |
| FQXHMDI0034G | The property [arg1] length exceeds the max supported limit of [arg2] characters. | Warning |
| FQXHMDI0035J | The IP address [arg1] of the device is a duplicate of another device IP address. | Warning |
| FQXHMDI0036J | The IP address [arg1] of the device is a duplicate of the management server IP address. | Warning |
| FQXHMDI0037I | The duplicate IP address issue for IP address [arg1] has been resolved. | Warning |
| FQXHMDI0037J | The request by user [arg1] to manage switch [arg2] failed because the management server was unable to retrieve the switch certificate. | Warning |
| FQXHMDI0038I | The duplicate IP address issue for IP address [arg1] has been resolved. | Warning |
| FQXHMDI0039J | The management server detected an IP conflict between the managed device and local network host. The IP address is [arg1] and the local network host MAC address is [arg2]. | Warning |
| FQXHMDI0040G | Updating the host configuration on chassis with UUID [arg1] has failed | Warning |
| FQXHMDI0040I | The management server detects no more conflicts in regard to the managed device and the network host IP address [arg1]. | Warning |
| FQXHMDI0041G | Updating the domain name on chassis with UUID [arg1] has failed | Warning |
| FQXHMDI0042G | Updating the host name on chassis with UUID [arg1] has failed | Warning |
| FQXHMDI0043G | Updating the display name on chassis with UUID [arg1] has failed | Warning |
| FQXHMDI0044G | Updating the IP interfaces on chassis with UUID [arg1] has failed | Warning |
| FQXHMDI0045G | Updating the rack information on chassis with UUID [arg1] has failed | Warning |
| FQXHMDI0046G | Updating the Lowest Rack Unit information on chassis with UUID [arg1] has failed | Warning |
| FQXHMDI0047G | Updating the display name on chassis with UUID [arg1] has succeeded with truncation. | Warning |
| FQXHMDI0048J | The health of SSD [arg1] in bay [arg2] of the RAID configuration [arg3] has diminished to a warning state. | Warning |
| FQXHMDI0070J | The link status is down for PCI device [arg2] on server [arg1]. | Warning |
| FQXHMDI0103G | A CIM subscription failure occurred after user [arg1] unmanaged server [arg3] | Warning |
| FQXHMDI0104G | The NTP server on server [arg2] failed to clean up after user [arg1] unmanaged it. | Warning |
| FQXHMDI0106G | The request by user [arg1] to manage server [arg2] failed because internal data related to this device could not be updated. | Warning |
| FQXHMDI0107G | The request by user [arg1] to manage server [arg2] failed due to login lockout on the server. | Warning |
| FQXHMDI0108G | The request by user [arg1] to manage server [arg2] failed during the login process to the server. | Warning |
| FQXHMDI0109G | The request by user [arg1] to manage server [arg2] failed due to connection issues. | Warning |
| FQXHMDI0110G | The request by user [arg1] to manage server [arg2] resulted in no action, because it is already being managed. | Warning |
| FQXHMDI0111G | The request by user [arg1] to manage server [arg2] did not complete due to a failure during inventory collection. | Warning |
| FQXHMDI0112G | The request by user [arg1] to manage rack server [arg2] failed because the management server was unable to retrieve the rack server's LDAP certificate. | Warning |
| FQXHMDI0113G | The request by user [arg1] to manage rack server [arg2] failed because the management server was unable to retrieve the rack server's CIM certificate. | Warning |
| FQXHMDI0114G | During the management process for rack server [arg1], the management server was unable to create the new user account RECOVERY_ID or disable local accounts on the server. | Warning |
| FQXHMDI0115G | The request by user [arg1] to manage rack server [arg2] failed because the management server was unable to update connections to use the temporary management userid created by the management server. | Warning |
| FQXHMDI0116G | The request by user [arg1] to manage rack server [arg2] failed for unknown reasons. | Warning |
| FQXHMDI0117G | The request by user [arg1] to manage rack server [arg2] failed due to being unable to set the authentication mode of the server. | Warning |
| FQXHMDI0120G | The request by user [arg1] to unmanage server [arg2] failed because internal data related to the device could not be properly updated. | Warning |
| FQXHMDI0122G | The request by user [arg1] to manage server [arg2] failed when performing additional manage configuration information. | Warning |
| FQXHMDI0123G | Initial inventory collection by user [arg1] of server [arg2] did not complete successfully. | Warning |
| FQXHMDI0124G | The request by user [arg1] to manage server [arg2] resulted in no action, because it is already being managed by a management server - [arg3]. | Warning |
| FQXHMDI0125G | The request by user [arg1] to manage rack server [arg2] failed because CIM over HTTPS is not enabled on the server. | Warning |
| FQXHMDI0128J | Address change for the device with UUID [arg1] was ignored because the IP address [arg2] is already used by the device with UUID [arg3]. | Warning |
| FQXHMDI0129G | During the management process for rack server [arg1], the management server was unable to create the new user account RECOVERY_ID because the minimum password length that is required by the rack server was not met. | Warning |
| FQXHMDI0140G | Updating the host configuration on server with UUID [arg1] has failed | Warning |
| FQXHMDI0141G | Updating the domain name on server with UUID [arg1] has failed | Warning |
| FQXHMDI0142G | Updating the host name on server with UUID [arg1] has failed | Warning |
| FQXHMDI0143G | Updating the display name on server with UUID [arg1] has failed | Warning |
| FQXHMDI0144G | Updating the IP interfaces on server with UUID [arg1] has failed | Warning |
| FQXHMDI0145G | Updating the rack information on server with UUID [arg1] has failed | Warning |
| FQXHMDI0147G | Updating the display name on server with UUID [arg1] has succeeded with truncation. | Warning |
| FQXHMDI0150I | System Guard is [arg1] on [arg2] devices of which [arg3] are successfully, see the full devices list in the log of job [arg4]. | Warning |
| FQXHMDI0201G | Cannot connect to the switch thru SSH. | Warning |
| FQXHMDI0202G | The management server cannot authenticate with switch {0} using the specified "enable" password. | Warning |
| FQXHMDI0306G | The request by user [arg1] to manage storage [arg2] failed because internal data related to this device could not be updated. | Warning |
| FQXHMDI0307G | The request by user [arg1] to manage storage [arg2] failed due to connection issues. | Warning |
| FQXHMDI0308G | The request by user [arg1] to manage storage [arg2] failed during the login process to the storage. | Warning |
| FQXHMDI0309G | The request by user [arg1] to unmanage storage [arg2] failed due to connection issues. | Warning |
| FQXHMDI0310G | The request by user [arg1] to manage storage [arg2] resulted in no action, because it is already being managed. | Warning |
| FQXHMDI0316G | The request by user [arg1] to manage storage [arg2] failed for unknown reasons. | Warning |
| FQXHMDI0320G | The request by user [arg1] to unmanage storage [arg2] failed because internal data related to the device could not be properly updated. | Warning |
| FQXHMDI0323G | Initial inventory collection by user [arg1] of storage [arg2] did not complete successfully. | Warning |
| FQXHMDM0138G | User [arg1] cannot perform a power operation on endpoint [arg2] because of connection issues. | Warning |
| FQXHMDM0139G | User [arg1] cannot modify the boot order on endpoint [arg2] because of connection issues. | Warning |
| FQXHMDM0140G | A cryptography/NIST operation started by user [arg1] on device [arg2] was not successful because of connection issues. | Warning |
| FQXHMDM0141G | User [arg1] cannot perform power capping on endpoint [arg2] because of connection issues. | Warning |
| FQXHMDM0142G | User [arg1] cannot modify an inventory property on endpoint [arg2] because of connection issues. | Warning |
| FQXHMDM0143G | User [arg1] cannot initiate a CMM failover on endpoint [arg2] because of connection issues. | Warning |
| FQXHMDM0144G | The led setting operation action started by user User [arg1] cannot set the LED on endpoint [arg2] because of connection issues. | Warning |
| FQXHMDM0145G | The operation requested by user [arg1] could not complete because access to endpoint with UUID [arg2] (IP: [arg3]) was denied. | Warning |
| FQXHMDM0146G | The operation requested by user [arg1] could not complete because access to endpoint [arg2] was denied due to insufficient privileges. | Warning |
| FQXHMDM0147G | The operation requested by user [arg1] could not complete on endpoint [arg2] because the operation is not supported. | Warning |
| FQXHMDM0148G | The operation requested by user [arg1] could not complete on endpoint [arg2] because the endpoint is not available. | Warning |
| FQXHMDM0149G | The operation requested by user [arg1] could not complete on endpoint with UUID [arg2] (IP: [arg3]) because authentication failed. | Warning |
| FQXHMDM0150G | The operation requested by user [arg1] could not complete on endpoint with UUID [arg2] (IP: [arg3]) because authorization credentials are expired. | Warning |
| FQXHMDM0151G | The operation requested by user [arg1] timed out on device with UUID [arg2] (IP: [arg3]). | Warning |
| FQXHMDM0152G | The operation requested by user [arg1] was interrupted on device [arg2]. | Warning |
| FQXHMDM0153G | The operation requested by user [arg1] was interrupted on device with UUID [arg2] (IP: [arg3]). | Warning |
| FQXHMDM0155G | Access was denied for the stored credentials with username '[arg1]' on the endpoint with UUID [arg2]. | Warning |
| FQXHMDM0165G | The device health state changed from normal to warning. | Warning |
| FQXHMDM0166K | The device health state changed from normal to critical. | Warning |
| FQXHMDM0167K | The device health state changed from warning to critical. | Warning |
| FQXHMDM0168G | The device health state changed from critical to warning. | Warning |
| FQXHMDM0169I | The device health state changed from critical to normal. | Warning |
| FQXHMDM0170I | The device health state changed from warning to normal. | Warning |
| FQXHMDM0171J | The request by user {0} to manage storage device {1} failed because the management server was unable to retrieve the storage certificate. | Warning |
| FQXHMEM0105J | The request from user [arg1], at IP address [arg2], to change the maximum size of the Audit log from [arg3] to [arg4] was not successful. | Warning |
| FQXHMEM0106J | The management server detected missing events from [arg1]. | Warning |
| FQXHMEM0206J | The request from user [arg1], at IP address [arg2], to change the maximum size of the event log from [arg3] to [arg4] was not successful. | Warning |
| FQXHMEM0207J | The request from user [arg1], at IP address [arg2],to clear the events with type [arg3] from the event log was not successful. | Warning |
| FQXHMEM0401I | Event forwarding monitor [arg1] failed to send notification to destination with error message: [arg2]. | Warning |
| FQXHMEM0409J | A warning alert was asserted on device [arg1] with alert ID [arg2]. | Warning |
| FQXHMEM9001J | The port number is not valid. | Warning |
| FQXHMEM9002J | The creation of the monitor was unsuccessful. The monitor name {0} is already taken. | Warning |
| FQXHMEM9003J | The creation of the monitor was unsuccessful. The maximum number of {0} SysLog monitors has been reached. | Warning |
| FQXHMEM9004J | The creation of the monitor was unsuccessful. The maximum number of {0} SNMPv3 monitors has been reached. | Warning |
| FQXHMEM9005J | The creation of the monitor was unsuccessful. The monitor is not configured correctly. | Warning |
| FQXHMEM9006J | The creation of the monitor was unsuccessful. The server was not able to save the configuration to the LDAP server. | Warning |
| FQXHMEM9010J | The reset of the monitor was unsuccessful. | Warning |
| FQXHMEM9011J | The update of the monitor was unsuccessful. | Warning |
| FQXHMEM9012J | The requested monitor is not available. | Warning |
| FQXHMEM9013J | The requested Event Action Task is no longer available. | Warning |
| FQXHMEM9014J | The information attached to the request is not complete. | Warning |
| FQXHMEM9015J | The server could not create the required Event Action Task because it is a duplicate of an existing one. | Warning |
| FQXHMEM9016J | The server could not persistently save the required Event Action Task. | Warning |
| FQXHMEM9017J | The creation of the monitor was unsuccessful. The maximum number of {0} email monitors has been reached. | Warning |
| FQXHMEM9018J | The creation of the monitor was unsuccessful. The maximum total number of {0} monitors has been reached. | Warning |
| FQXHMEM9019J | The URI is not valid. | Warning |
| FQXHMEM9020J | Invalid parameter. | Warning |
| FQXHMEM9021J | Invalid filter. | Warning |
| FQXHMEM9022J | An input field was not valid. | Warning |
| FQXHMEM9023J | The creation of the exclude filter was unsuccessful. | Warning |
| FQXHMEM9024J | The update of the exclude filter was unsuccessful. | Warning |
| FQXHMEM9025J | The exclude filter could not be deleted. | Warning |
| FQXHMEM9026J | The exclude filter could not be deleted. | Warning |
| FQXHMEM9028J | ID not valid. | Warning |
| FQXHMEM9029J | The request body is not valid. | Warning |
| FQXHMEM9030J | Internal error | Warning |
| FQXHMEM9031J | No description available. | Warning |
| FQXHMEM9032J | Look in the online documentation for the device to determine if that event is listed there. | Warning |
| FQXHMEM9033J | The authUser name {0} is already taken. | Warning |
| FQXHMEM9034J | The certificate was not added in the truststore. | Warning |
| FQXHMEM9035J | The certificate was added in the truststore. | Warning |
| FQXHMEM9036J | The certificate could not be added in the truststore. | Warning |
| FQXHMEM9037J | Do you want to add this certificate in the truststore? If you don't add it in the truststore no communication with the specified SMTP server will be possible. | Warning |
| FQXHMEM9039J | The creation of the monitor was successful but the download of the SMTP server's certificate failed. | Warning |
| FQXHMEM9040J | The monitor was updated successfully but the download of the SMTP server's certificate failed. | Warning |
| FQXHMEM9041J | The monitor was updated successfully but the download of the SMTP server's certificate failed. | Warning |
| FQXHMEM9042J | The update to the events configuration failed. | Warning |
| FQXHMEM9043J | The inserted scheduler is not correct. | Warning |
| FQXHMEM9044J | The creation of the monitor was successful but the download of the HTTPS server's certificate failed. | Warning |
| FQXHMEM9045J | The monitor was updated successfully but the download of the HTTPS server's certificate failed. | Warning |
| FQXHMEM9046J | The monitor was updated successfully but the download of the HTTPS server's certificate failed. | Warning |
| FQXHMEM9047J | Do you want to add this certificate in the truststore? If you don't add it in the truststore no communication with the specified HTTPS server will be possible. | Warning |
| FQXHMEM9048J | A certificate for this HTTPS server is already in the truststore.Do you want to replace the existing one with this certificate? | Warning |
| FQXHMEM9049J | The creation of the monitor was unsuccessful. The maximum number of {0} rest monitors has been reached. | Warning |
| FQXHMEM9050J | The request to acknowledge alert was unsuccessful. | Warning |
| FQXHMEM9051J | The request to acknowledge alert was unsuccessful. | Warning |
| FQXHMEM9052J | The request to delete acknowledge alert was unsuccessful. | Warning |
| FQXHMEM9053J | The request to delete acknowledge alert was unsuccessful. | Warning |
| FQXHMEM9054J | The request to acknowledge alerts has encountered various issues. | Warning |
| FQXHMEM9055J | The request to delete acknowledge alerts has encountered various issues. | Warning |
| FQXHMEM9056J | The request to start metrics collection for DM Storages has failed. | Warning |
| FQXHMEM9057J | The request to retrieve metrics is invalid. | Warning |
| FQXHMEMF9038J | A certificate for this SMTP server is already in the truststore.Do you want to replace the existing one with this certificate? | Warning |
| FQXHMFC0040G | Image deployment for server {0} is not in progress. | Warning |
| FQXHMFC0094F | Another user is currently logged into remote media for this server. Only one user may be logged into remote media functions at a time. | Warning |
| FQXHMFC0095F | The operation being attempted has timed out. The operation was : {0}. | Warning |
| FQXHMFC0097F | There are not enough available drives on the server to mount all selected devices. | Warning |
| FQXHMFC0098F | Unable to determine the type of drive for Virtual Media. | Warning |
| FQXHMFC0099F | Could not map a drive for the following device: {0}. | Warning |
| FQXHMFC0101F | A socket error has occurred. All connections have been closed. | Warning |
| FQXHMFC0102F | An internal operating system deployment error has occurred for the server. | Warning |
| FQXHMFC0108F | Could not remove the image from the server. | Warning |
| FQXHMFC0110F | Cannot mount the device ({0}) to a server because it is currently mounted to a different server. | Warning |
| FQXHMFC0111F | Unable to make a connection to the server. | Warning |
| FQXHMFC0114F | Images cannot be managed or deployed because the management server does not have a valid IP address configured for the operating system image deployment network interface. | Warning |
| FQXHMFC0115F | Images cannot be managed or deployed because the operating system deployment network interface is not configured. | Warning |
| FQXHMFC0229G | The custom profile has encountered a warning during post-install. The warning message is: {0}. | Warning |
| FQXHMFC0240G | An error occurred while downloading software payload {0}: {1}. | Warning |
| FQXHMFC0249G | An error occurred while executing post-installation script {0} on server {1}: {2}. | Warning |
| FQXHMFC0252F | The management server is waiting for the required core services to start. | Warning |
| FQXHMFC0259G | An error occurred while installing custom device driver {0} on server {1}: {2}. | Warning |
| FQXHMFC0283J | An error occurred while extracting software payload {0}: {1}. | Warning |
| FQXHMFC147F | The image deployment service is initializing. | Warning |
| FQXHMFC8600G | Operating systems on the selected servers will be overwritten. | Warning |
| FQXHMFC8604F | Global settings cannot be modified while a deployment is in progress. | Warning |
| FQXHMFC8607F | Information is still being collected about the management server and its managed chassis (if applicable). | Warning |
| FQXHMFC8610F | Incompatible images have been filtered out | Warning |
| FQXHMFC8612F | You must enter Active Directory credentials that will be used to join with specified domain | Warning |
| FQXHMFC8615F | The number of servers selected exceeds the number of Microsoft Windows deployment operations that can occur concurrently. | Warning |
| FQXHMFC8617F | VLAN tagging is not supported. | Warning |
| FQXHMFC8619F | The selected file could not be imported in IE. | Warning |
| FQXHMFC8620F | The selected configuration file is invalid, therefore the Configuration Tree cannot be generated and the Common and Specific tabs are disabled. | Warning |
| FQXHMFC8635F | Some OS-images are not listed due to missing WinPE file | Warning |
| FQXHMFC8636F | OS Deployment is in Progress | Warning |
| FQXHMJM0005J | User [arg1] at IP address [arg2] tried to create job schedule [arg3] but the operation was unsuccessful. | Warning |
| FQXHMJM0007J | User [arg1] at IP address [arg2] tried to update job schedule [arg3] but the operation was unsuccessful. | Warning |
| FQXHMJM0009J | User [arg1] at IP address [arg2] tried to change job schedule [arg3] state to [arg4], but the operation was unsuccessful. | Warning |
| FQXHMJM0011J | User [arg1] at IP address [arg2] called Run Now procedure for job schedule [arg3], but the operation was unsuccessful. | Warning |
| FQXHMJM0013J | User [arg1] at IP address [arg2] tried to clone job schedule [arg3], but the operation was unsuccessful. | Warning |
| FQXHMJM0015J | User [arg1] at IP address [arg2] tried to remove job schedule configurations but the operation was unsuccessful. Removed schedules: [arg3]. Not found IDs: [arg4] | Warning |
| FQXHMJM0017J | The management server tried to launch the job for job scheduler [arg1], but the operation was unsuccessful. | Warning |
| FQXHMJM0019J | User [arg1] at IP address [arg2] tried to postpone job [arg3] but the operation was unsuccessful. | Warning |
| FQXHMMF0001J | The connection to collect metrics between the management server and the management controller [arg1] is offline. | Warning |
| FQXHMMF0002J | The connection to forward metrics between the management server and the orchestrator server [arg1] is offline. | Warning |
| FQXHMMF0004J | Metrics data collection for all DM Storage managed with ID [arg1] has failed. | Warning |
| FQXHMMF0006J | Metrics data collection was missed from the device [arg1] between [arg2] and [arg3]. | Warning |
| FQXHMSE0004G | Security policy level [arg1] on [arg2] does not match security policy level [arg3] on the management server. | Warning |
| FQXHMSE0004J | The request could not be completed. | Warning |
| FQXHMSE0005G | Minimum SSL/TLS protocol level [arg1] on [arg2] does not match minimum SSL/TLS protocol levels client [arg3] and server [arg4] on the management server. | Warning |
| FQXHMSE0006G | Cryptographic mode [arg1] on [arg2] does not match cryptographic mode [arg3] on the management server. | Warning |
| FQXHMSE0101J | The certificate signing request (CSR) does not exist or cannot be read. | Warning |
| FQXHMSE0102J | The value specified for the country code is not valid. | Warning |
| FQXHMSE0104J | The request to upload a new server certificate was not successful. | Warning |
| FQXHMSE0107J | The request to regenerate a new server certificate was not successful. | Warning |
| FQXHMSE0108J | The request to download the server certificate was not successful. | Warning |
| FQXHMSE0109J | The request to generate a new certificate was not successful. | Warning |
| FQXHMSE0110J | The request to generate a certificate signing request (CSR) was not successful. | Warning |
| FQXHMSE0111J | The request to upload a new server certificate was not successful. | Warning |
| FQXHMSE0113J | The request to generate a new server certificate was not successful. | Warning |
| FQXHMSE0114J | The request to generate a certificate signing request (CSR) was not successful. | Warning |
| FQXHMSE0115J | The request to upload a new server certificate was not successful. | Warning |
| FQXHMSE0116F | The request to generate a new certificate was not successful. | Warning |
| FQXHMSE0117J | The request to resolve the untrusted connection to the endpoint was not successful. | Warning |
| FQXHMSE0118J | The request to resolve the untrusted connection was not successful. | Warning |
| FQXHMSE0119J | The request to resolve the untrusted connection was not successful. | Warning |
| FQXHMSE0121J | The request to generate a server certificate was not successful. | Warning |
| FQXHMSE0122J | The request to replace the server certificates was not successful. | Warning |
| FQXHMSE0123G | The trusted certificate for managed system [arg1] does not comply with the cryptographic mode of the system. | Warning |
| FQXHMSE0124J | The request to download the certificate revocation list (CRL) was not successful. | Warning |
| FQXHMSE0125J | The request to add the certificate revocation list (CRL) was not successful. | Warning |
| FQXHMSE0126J | The request to delete the certificate revocation list (CRL) was not successful. | Warning |
| FQXHMSE0127J | The request to upload a certificate was not successful. | Warning |
| FQXHMSE0128J | The provided certificate does not meet the current cryptographic mode requirements. | Warning |
| FQXHMSE0135J | The request to download the CA root certificate was not successful. | Warning |
| FQXHMSE0136J | The request to download the internal CA root certificate failed. | Warning |
| FQXHMSE0137J | The request to upload a new server certificate was not successful. | Warning |
| FQXHMSE0138J | The request to upload a new server certificate was not successful. | Warning |
| FQXHMSE0139J | The request to upload a new server certificate was not successful. | Warning |
| FQXHMSE0140J | The request to upload a new server certificate was not successful. | Warning |
| FQXHMSE0145J | The request to install the server certificate from the temporary key store was not successful. | Warning |
| FQXHMSE0148J | The request to retrieve SSH keys has been processed. | Warning |
| FQXHMSE0151J | The request to generate the server certificate was not successful. | Warning |
| FQXHMSE0152J | The request to generate the server certificate was not successful. | Warning |
| FQXHMSE0153J | The request to generate the server certificate was not successful. | Warning |
| FQXHMSE0154J | The request to resolve the untrusted certificates was not successful. | Warning |
| FQXHMSE0241J | The request to add the user ID {0} was not successful. | Warning |
| FQXHMSE0242J | The request to add the user ID {0} was not successful. | Warning |
| FQXHMSE0243J | The request to add the user ID {0} was not successful. | Warning |
| FQXHMSE0244J | The request to add the user ID {0} was not successful. | Warning |
| FQXHMSE0245J | The request to add the user ID {0} was not successful. | Warning |
| FQXHMSE0246J | The request to add a user was not successful. | Warning |
| FQXHMSE0247J | The request to add the user ID {0} was not successful. | Warning |
| FQXHMSE0251J | The request to change the password for user ID {0} was not successful. | Warning |
| FQXHMSE0252J | The request to change the password for user ID {0} was not successful. | Warning |
| FQXHMSE0253J | The request to change the password for user ID {0} was not successful. | Warning |
| FQXHMSE0254J | The request to change the password for user ID {0} was not successful. | Warning |
| FQXHMSE0255J | The request to change the password for user ID {0} was not successful. | Warning |
| FQXHMSE0256J | The request to change the password for user ID {0} was not successful. | Warning |
| FQXHMSE0257J | The request to change the password for user ID {0} was not successful. | Warning |
| FQXHMSE0261J | The request to modify the user ID {0} was not successful. | Warning |
| FQXHMSE0262J | The request to rename the user ID {0} was not successful. | Warning |
| FQXHMSE0263J | The request to modify the user ID {0} was not successful. | Warning |
| FQXHMSE0264J | The request to modify the user ID {0} was not successful. | Warning |
| FQXHMSE0265J | The request to modify the user ID {0} was not successful. | Warning |
| FQXHMSE0266J | The request to modify a user was not successful. | Warning |
| FQXHMSE0267J | The request to modify the user ID {0} was not successful. | Warning |
| FQXHMSE0268J | The request to modify the user ID {0} was not successful. | Warning |
| FQXHMSE0271J | The request to delete the user ID {0} was not successful. | Warning |
| FQXHMSE0272J | The request to delete a user was not successful. | Warning |
| FQXHMSE0273J | The request to delete the user ID {0} was not successful. | Warning |
| FQXHMSE0274J | User ID {0} does not have sufficient permissions for this specific request. | Warning |
| FQXHMSE0275J | An error occurred because the password of the user that is currently logged in has expired. | Warning |
| FQXHMSE0276J | Session credentials for user ID {0} cannot be verified. | Warning |
| FQXHMSE0277J | The request to log in could not be completed successfully. | Warning |
| FQXHMSE0280J | The requested user does not exist. | Warning |
| FQXHMSE0281J | The request could not be completed successfully. | Warning |
| FQXHMSE0290J | The request to log in could not be completed successfully. | Warning |
| FQXHMSE0291J | The request to log in could not be completed successfully. | Warning |
| FQXHMSE0292J | The request to log in could not be completed successfully. | Warning |
| FQXHMSE0293J | The request to log in could not be completed successfully. | Warning |
| FQXHMSE0294J | The request to log in could not be completed successfully. | Warning |
| FQXHMSE0295J | The request to log in could not be completed successfully. | Warning |
| FQXHMSE0296J | The request to log in could not be completed successfully. | Warning |
| FQXHMSE0297J | The request to log in could not be completed successfully. | Warning |
| FQXHMSE0298J | Login failed. The maximum number of active sessions for this user account is exceeded. Log out of an existing session, and try again. | Warning |
| FQXHMSE0301J | Could not change security-policy level. | Warning |
| FQXHMSE0302J | The request to change the account-security settings was not successful. | Warning |
| FQXHMSE0315J | The request to change the minimum password length was not successful. | Warning |
| FQXHMSE0316J | The request to change the maximum password length was not successful. | Warning |
| FQXHMSE0317J | The request to change the minimum password reuse cycle was not successful. | Warning |
| FQXHMSE0318J | The request to change the password expiration period was not successful. | Warning |
| FQXHMSE0319J | The request to change the web inactivity session timeout was not successful. | Warning |
| FQXHMSE0320J | The request to change the minimum password change interval was not successful. | Warning |
| FQXHMSE0321J | The request to change the maximum number of login failures was not successful. | Warning |
| FQXHMSE0322J | The request to change the lockout period after the maximum login failures was not successful. | Warning |
| FQXHMSE0323J | The request to change the simple password rules was not successful. | Warning |
| FQXHMSE0324J | The request to change the minimum different characters in a password was not successful. | Warning |
| FQXHMSE0325J | The request to change the password expiration warning period was not successful. | Warning |
| FQXHMSE0326J | The request to change the requirement to force a user to change password on first access was not successful. | Warning |
| FQXHMSE0327J | The request to change the minimum different characters allowed in a password was not successful. | Warning |
| FQXHMSE0328J | The request to change the minimum password length was not successful. | Warning |
| FQXHMSE0329J | The request to change the minimum password change interval was not successful. | Warning |
| FQXHMSE0330J | The request to change the password-expiration warning period was not successful. | Warning |
| FQXHMSE0333J | The request to change the maximum concurrent sessions value was not successful. | Warning |
| FQXHMSE0334J | There are {0} active license keys that entitle licenses for {1} devices; however, {2} managed devices require licenses. You have {3} days remaining to install the appropriate number of licenses to be in compliance. | Warning |
| FQXHMSE0336J | Please import the first license via the web interface in order to accept the License Agreement. | Warning |
| FQXHMSE0500J | The provided cryptographic mode value is not valid. | Warning |
| FQXHMSE0501J | The provided minimum SSL/TLS protocol level is not valid. | Warning |
| FQXHMSE0502J | The cryptographic mode is not compatible with the minimum SSL/TLS protocol level. | Warning |
| FQXHMSE0505J | The provided cryptographic mode value cannot be enforced with the current server certificate. | Warning |
| FQXHMSE0506J | The provided cryptographic mode value cannot be enforced with the currently configured endpoint user accounts. | Warning |
| FQXHMSE0507J | The provided cryptographic mode value cannot be enforced with the current trusted certificates. | Warning |
| FQXHMSE0508J | An internal connection failure occurred while attempting to change cryptographic settings on the endpoint. | Warning |
| FQXHMSE0509J | The command to change the cryptographic settings on the endpoint failed. | Warning |
| FQXHMSE0510J | The command to change the cryptographic settings failed. | Warning |
| FQXHMSE0602J | An unsecure connection to the server at address {0}, port {1} could not be completed successfully. | Warning |
| FQXHMSE0603J | A secure connection to the server at address {0}, port {1} could not be completed successfully. | Warning |
| FQXHMSE0605F | Binding to the server using the distinguished name {0} could not be completed successfully. | Warning |
| FQXHMSE0607J | A search for user entries on the server could not be completed successfully. | Warning |
| FQXHMSE0609J | A search for role group entries on the server could not be completed successfully. | Warning |
| FQXHMSE0610J | The request to change the LDAP configuration could not be completed successfully. | Warning |
| FQXHMSE0611J | The request to change the LDAP configuration could not be completed successfully. | Warning |
| FQXHMSE0612J | The LDAP trusted certificate was not found. | Warning |
| FQXHMSE0613J | The LDAP trusted certificate could not be added. | Warning |
| FQXHMSE0614J | The changes to the LDAP configuration could not be completed successfully. | Warning |
| FQXHMSE0615J | The LDAP trusted certificate could not be added. | Warning |
| FQXHMSE0618J | Unsecure communication to the server at address {0}, port {1} could not be completed successfully. | Warning |
| FQXHMSE0619J | Secure communication to the server at address {0}, port {1} could not be completed successfully. | Warning |
| FQXHMSE0640J | DNS resolution of LDAP server addresses could not be completed successfully. | Warning |
| FQXHMSE0641J | The requested user authentication method could not be set successfully. | Warning |
| FQXHMSE0643J | The root distinguished name could not be determined. | Warning |
| FQXHMSE0650J | The request to change LDAP client settings could not be completed successfully. | Warning |
| FQXHMSE0652G | The requested user authentication method was set successfully, but some warnings were noted. | Warning |
| FQXHMSE0653J | The root distinguished name is not valid. | Warning |
| FQXHMSE0654G | A search for user entries on the server could not be completed successfully. | Warning |
| FQXHMSE0655G | A search for role group entries on the server could not be completed successfully. | Warning |
| FQXHMSE0656J | No recovery user was found | Warning |
| FQXHMSE0710J | The requested role group does not exist. | Warning |
| FQXHMSE0711J | The request to add a role group was not successful. | Warning |
| FQXHMSE0712J | The request to add the role group {0} was not successful. | Warning |
| FQXHMSE0713J | The request to add the role group {0} was not successful. | Warning |
| FQXHMSE0714J | The request to add the role group {0} was not successful. | Warning |
| FQXHMSE0715J | The request to add the role group {0} was not successful. | Warning |
| FQXHMSE0716J | The request to modify a role group was not successful. | Warning |
| FQXHMSE0717J | The request to modify the role group {0} was not successful. | Warning |
| FQXHMSE0718J | The request to modify the role group {0} was not successful. | Warning |
| FQXHMSE0719J | The request to rename the role group {0} was not successful. | Warning |
| FQXHMSE0720J | The request to modify the role group {0} was not successful. | Warning |
| FQXHMSE0721J | The request to delete the role group {0} was not successful. | Warning |
| FQXHMSE0722J | The request to delete the role group {0} was not successful. | Warning |
| FQXHMSE0725J | The role group deletion request was not successful. | Warning |
| FQXHMSE0726J | The role group retrieval request was not successful. | Warning |
| FQXHMSE0727J | The role retrieval request was not successful. | Warning |
| FQXHMSE0728J | The role retrieval request was not successful. | Warning |
| FQXHMSE0729J | The role creation request was not successful. | Warning |
| FQXHMSE0730J | The role creation request was not successful. | Warning |
| FQXHMSE0731J | The request to add a role was not successful. | Warning |
| FQXHMSE0732J | The request to add a role was not successful. | Warning |
| FQXHMSE0733J | The request to add a role was not successful. | Warning |
| FQXHMSE0734J | The request to add a role was not successful. | Warning |
| FQXHMSE0735J | The role deletion request was not successful. | Warning |
| FQXHMSE0736J | The role deletion request was not successful. | Warning |
| FQXHMSE0737J | The request to add a role was not successful. | Warning |
| FQXHMSE0738J | The request to modify the role was not successful. | Warning |
| FQXHMSE0740J | The role group deletion request was not successful. | Warning |
| FQXHMSE0741J | The role deletion request was not successful. | Warning |
| FQXHMSE0742J | The request to modify a role group was not successful. | Warning |
| FQXHMSE0743J | The requested privilege does not exist. | Warning |
| FQXHMSE0744J | The privileges retrieval request was not successful. | Warning |
| FQXHMSE0745J | The privileges have not been defined. | Warning |
| FQXHMSE0746J | The requested privilege category does not exist. | Warning |
| FQXHMSE0751J | The request to {0} the resource access control was not successful. | Warning |
| FQXHMSE0752J | The request could not be completed successfully. | Warning |
| FQXHMSE0753J | The request to set up a new resource access was not successful. | Warning |
| FQXHMSE0754J | The request to setup a new resource access was not successful. | Warning |
| FQXHMSE0755J | The request to setup a new resource access was not successful. | Warning |
| FQXHMSE0756J | The request to setup a new resource access was not successful. | Warning |
| FQXHMSE0757J | The request to setup a new resource access was not successful. | Warning |
| FQXHMSE0758J | The request to modify the resource access was not successful. | Warning |
| FQXHMSE0759J | The request to modify the resource access was was not successful. | Warning |
| FQXHMSE0760J | The request to modify the resource access was not successful. | Warning |
| FQXHMSE0761J | The request to modify the resource access was not successful. | Warning |
| FQXHMSE0762J | The requested resource access does not exist. | Warning |
| FQXHMSE0763J | The request to modify the resource access was not successful. | Warning |
| FQXHMSE0764J | The request to delete the resource access was not successful. | Warning |
| FQXHMSE0765J | The requested resource access does not exist. | Warning |
| FQXHMSE0766J | The request to delete the resource access was was not successful. | Warning |
| FQXHMSE0767J | The request to delete the resource access was not successful. | Warning |
| FQXHMSE0768J | The request to delete resource access {0} was not successful. | Warning |
| FQXHMSE0769J | The request to add resource access {0} was not successful. | Warning |
| FQXHMSE0770J | The authorization request could not be created due to invalid request data. | Warning |
| FQXHMSE0771J | The authorization request could not be created due to missing request data. | Warning |
| FQXHMSE0772J | The authorization request could not be created due to conflicting resources in the request data. | Warning |
| FQXHMSE0773J | The authorization request could not be created due to missing request data. | Warning |
| FQXHMSE0774J | The authorization request could not be created because group membership could not be determined for the user. | Warning |
| FQXHMSE0775J | The request to create the resource access was not successful. | Warning |
| FQXHMSE0776J | The request to modify the resource access was not successful. | Warning |
| FQXHMSE0777J | The request to modify resource access {0} was not successful. | Warning |
| FQXHMSE0778J | The requested resource access control operation was not successful. | Warning |
| FQXHMSE0779J | The resource access control settings could not be retrieved. | Warning |
| FQXHMSE0780J | The request to update the resource access control settings could not be completed. | Warning |
| FQXHMSE0781J | The request to update the resource access control settings could not be completed. | Warning |
| FQXHMSE0810J | The external login request was not successful. | Warning |
| FQXHMSE0811J | The external login request was not successful. | Warning |
| FQXHMSE0812J | The external logon request was not successful. | Warning |
| FQXHMSE0813J | The external login request was not successful because the identity provider is not configured. | Warning |
| FQXHMSE0814J | The external login request was not successful because the response issue time is not valid. | Warning |
| FQXHMSE0815J | Regeneration of the service provider metadata was not successful. | Warning |
| FQXHMSE0816J | The identity provider metadata could not be validated. | Warning |
| FQXHMSE0817J | The request completed successfully. | Warning |
| FQXHMSE0818J | The core service could not be restarted. | Warning |
| FQXHMSE0819J | Retrieving certificate from endpoint {0} has failed | Warning |
| FQXHMSE0900J | The requested stored credentials operation was not successful. | Warning |
| FQXHMSE0901J | The requested stored credentials do not exist. | Warning |
| FQXHMSE0902J | The stored credentials user name is not valid. | Warning |
| FQXHMSE0903J | The stored credentials password is not valid. | Warning |
| FQXHMSE0904J | The credentials could not be created and stored. | Warning |
| FQXHMSE0905J | The credentials could not be updated. | Warning |
| FQXHMSE0906J | The credentials were not removed because they are currently in use. | Warning |
| FQXHMSE0907J | The credentials could not be removed. | Warning |
| FQXHMSE0908J | The stored credentials user name is not valid. | Warning |
| FQXHMSE0909J | The stored credentials description is not valid. | Warning |
| FQXHMSE0910J | Cannot update the username of these stored credentials because they are currently in use. | Warning |
| FQXHMSE0915I | Head of Stack feature not supported for firmware [arg1]. | Warning |
| FQXHMSE0915J | The specified user name and password combination already exists. | Warning |
| FQXHMSE0918J | The specified SAN name({0}) is not valid for the specified type({1}). | Warning |
| FQXHMSE0919J | The specified SAN type ({0}) or name ({1}) is not valid. | Warning |
| FQXHMSE0920J | The Subject Alternative Names has duplicate fields. | Warning |
| FQXHMSE0922F | Old licensing system is obsolete. Please use new licensing system. | Warning |
| FQXHMSE0923F | You are in TRIAL mode of the obsolete licensing system. Please use new licensing system. | Warning |
| FQXHMSE0925F | The number of devices managed is over the limit of number of devices that license permit. | Warning |
| FQXHMSE0927F | You have [arg1] days remaining to make your system compliant. | Warning |
| FQXHMSE0928F | License will expire soon. Check licenses. | Warning |
| FQXHMSP00002J | The job [arg1] requested by user [arg2] to retrieve the chassis switch ports on device [arg3] failed . | Warning |
| FQXHMSS0002J | The download of Service Data files was not successful by user [arg1] at IP address [arg2]. | Warning |
| FQXHMSS0004J | The download of Service Data file [arg1] was not successful by user [arg2] at IP address [arg3]. | Warning |
| FQXHMSS1002J | The request from user [arg1], at IP address [arg2], to change the log level of logger [arg3] from [arg4] to [arg5] was not successful. | Warning |
| FQXHMSS1004J | The request from user [arg1], at IP address [arg2], to change the log size of logger [arg3] from [arg4] to [arg5] was not successful. | Warning |
| FQXHMSS1006J | The request from user [arg1], at IP address [arg2], to change the number of Service Data files to keep from [arg3] to [arg4] was not successful. | Warning |
| FQXHMSS1008J | The request from user [arg1], at IP address [arg2], to change the suppression time from [arg3] to [arg4] was not successful. | Warning |
| FQXHMSS1010J | The request from user [arg1], at IP address [arg2], to change the number of informational Service Data files to keep from [arg3] to [arg4] was not successful. | Warning |
| FQXHMSS1013J | A request to collect a Service Data file on the server was not successful. | Warning |
| FQXHMSS1015J | An internal server error occurred during the deletion of the dumped service and support archives on the server, which was requested by user [arg1] at IP address [arg2]. | Warning |
| FQXHMSS1019J | The request from user [arg1] at IP address [arg2] to restore the log settings to the default values was not successful. | Warning |
| FQXHMSS1024J | The request by user [arg1] at IP address [arg2] to upload a file was not successful, because the file name was not valid. | Warning |
| FQXHMSS1025J | The request by user [arg1] at IP address [arg2] to upload a file was not successful, because the file could not be written to disk. | Warning |
| FQXHMSS1026J | The request by user [arg1] at IP address [arg2] to upload a file was not successful, because a temp file could not deleted. | Warning |
| FQXHMSS1027J | The request by user [arg1] at IP address [arg2] to upload a file was not successful, because the file format was not valid. | Warning |
| FQXHMSS1043J | An internal server error occurred while saving the Call Home configuration. | Warning |
| FQXHMSS1044J | Another test is ongoing. | Warning |
| FQXHMSS1045J | The request to upload the configuration file was not successful because the file contains an attempt to change the level for a restricted logger. | Warning |
| FQXHMSS1046J | The request to change the log level from {0} to {1} for the restricted logger {2} is not allowed. | Warning |
| FQXHMSS1048J | The contact information for Call Home of chassis with UUID {0} was not saved. | Warning |
| FQXHMSS1049J | The contact information for Call Home of chassis with UUID {0} cannot be changed or retrieved. | Warning |
| FQXHMSS1051J | The operation to reset the contact information on chassis with UUID {0} for Call Home was unsuccessful. | Warning |
| FQXHMSS1055J | The request from user [arg1], at IP address [arg2], to change the log level for the restricted logger [arg3] from [arg4] to [arg5] was not successful. | Warning |
| FQXHMSS1056J | The Call Home test finished unsuccessfully. There is no managed endpoint available for doing the test. | Warning |
| FQXHMSS1058J | The Call Home test finished unsuccessfully. There was an error. | Warning |
| FQXHMSS1059J | The Call Home test finished unsuccessfully. There was a problem on submitting the test report. | Warning |
| FQXHMSS1060J | The Call Home test was unsuccessful. | Warning |
| FQXHMSS1061J | Collecting the Service Data archive from endpoint {0} has failed. | Warning |
| FQXHMSS1062J | There is a Call Home test in progress. | Warning |
| FQXHMSS1063J | Call Home cannot be enabled due to configuration values that are not valid. | Warning |
| FQXHMSS1064J | The required archive is not available. | Warning |
| FQXHMSS1065J | Some of the specified tickets could not be deleted. | Warning |
| FQXHMSS1066J | The specified Problem Number is no longer available. | Warning |
| FQXHMSS1067J | The list of tickets could not be deleted because of a server error. | Warning |
| FQXHMSS1068J | Some of the tickets could not be deleted because of a server error. | Warning |
| FQXHMSS1069J | Changing the state of the auto dump mechanism was unsuccessful. | Warning |
| FQXHMSS1070J | Changing the state of the file tracing mechanism was unsuccessful. | Warning |
| FQXHMSS1071J | The inserted status ({0}) is not valid. It must be between {1} and {2}. | Warning |
| FQXHMSS1072J | A server error occurred while saving the values. | Warning |
| FQXHMSS1075J | An error occurred while updating the tickets states. | Warning |
| FQXHMSS1076J | Another update task is ongoing. | Warning |
| FQXHMSS1079J | Unable to replace endpoint callhome contact info with default server callhome configuration. | Warning |
| FQXHMSS1080J | An server error occurred while attaching the specified file to the problem number. | Warning |
| FQXHMSS1082J | Unsupported file format. | Warning |
| FQXHMSS1083J | Changing the state of the output aspect mechanism was unsuccessful. | Warning |
| FQXHMSS1084J | Another task that is changing the endpoints Call Home state is ongoing. | Warning |
| FQXHMSS1089J | The server has disabled the Call Home state on some of the managed endpoints. There are {0} endpoints on which the command failed. | Warning |
| FQXHMSS1090J | The server has enabled the Call Home state on some of the managed endpoints. There are {0} endpoints on which the command failed. | Warning |
| FQXHMSS1091J | The server failed to change the Call Home state on all the managed endpoints. | Warning |
| FQXHMSS1095J | The management server failed to parse the uploaded file. | Warning |
| FQXHMSS1110J | A server error occurred. | Warning |
| FQXHMSS1111J | The Call Home endpoint call switched in error state. | Warning |
| FQXHMSS1112J | Creating a Problem number failed. | Warning |
| FQXHMSS1113J | Collecting the Service Data archive from component {0} failed. | Warning |
| FQXHMSS1114J | Uploading the collected Service Data from component {0} to the opened PMR ({1}) failed. | Warning |
| FQXHMSS1130J | Call Home is not enabled. | Warning |
| FQXHMSS1215J | Cannot generate test event for {0} because the forwarder is disabled. | Warning |
| FQXHMSS1216J | Cannot generate test event for {0} because this type of forwarder requires a managed endpoint. | Warning |
| FQXHMSS1223J | The selected Problem Record is no longer available. | Warning |
| FQXHMSS1229J | There is another Call Home state change task on going. | Warning |
| FQXHMSS123J | There are no managed endpoints that support the Call Home function. They do not have the function implemented. | Warning |
| FQXHMSS1243J | Problem record {0} has not been deleted because the state is {1}. | Warning |
| FQXHMSS1244J | Ticket {0} has not been deleted because it is no longer available. | Warning |
| FQXHMSS1245J | None of the tickets were deleted. | Warning |
| FQXHMSS1246H | Some of the tickets were not deleted. | Warning |
| FQXHMSS1246J | Request to create forwarder has failed. | Warning |
| FQXHMSS1269J | The Lenovo Upload Facility is not set. | Warning |
| FQXHMSS1270J | Creating an archive with the selected archives and uploading it to Lenovo Upload Facility server failed. | Warning |
| FQXHMSS1277J | The Lenovo Upload Facility configuration is not valid. | Warning |
| FQXHMSS1278J | The test was not successful. | Warning |
| FQXHMSS2008J | Call Home Service Forwarder [arg1] was not able to create Ticket for event [arg2] generated on [arg3]. The forwarder has no more retries left. The process for this event will be dropped. | Warning |
| FQXHMSS2011J | Call Home Service Forwarder [arg1] was not able to upload the Service Data to Ticket [arg2]. The entry has no more retries left. The process for this event will be dropped. | Warning |
| FQXHMSS2014J | SFTP Service Forwarder [arg1] was not able to upload the Service Data to Ticket to [arg2]:[arg3]. The number of retries left is [arg4]. | Warning |
| FQXHMSS2023J | Call Home Service Forwarder [arg1] was not able to upload the Service Data to Ticket [arg2]. The number of retries left is [arg3]. | Warning |
| FQXHMSS2024J | Call Home Service Forwarder [arg1] was not able to create Ticket for event [arg2] generated on [arg3]. The number of retries left is [arg4]. | Warning |
| FQXHMSS2025J | SFTP Service Forwarder [arg1] was not able to upload the Service Data to Ticket to [arg2]:[arg3]. The entry has no more retries left. The process for this event will be dropped. | Warning |
| FQXHMSS2027G | User [arg1] at IP address [arg2] has tried to upload file '[arg3]' to Service Ticker [arg4] but the request failed. | Warning |
| FQXHMSS2029J | SFTP Service Forwarder [arg1] was not able to upload the Service Data to Ticket to [arg2]:[arg3] due to connectivity issues. The number of retries left is [arg4]. | Warning |
| FQXHMSS2030J | SFTP Service Forwarder [arg1] was not able to upload the Service Data to Ticket to [arg2]:[arg3] due to invalid credentials. The number of retries left is [arg4]. | Warning |
| FQXHMSS2031J | SFTP Service Forwarder [arg1] was not able to upload the Service Data to Ticket to [arg2]:[arg3] due to some transfer errors. The number of retries left is [arg4]. | Warning |
| FQXHMSS2032J | SFTP Service Forwarder [arg1] was not able to upload the Service Data to Ticket to [arg2]:[arg3] due to connectivity issues. The entry has no more retries left. The process for this event will be dropped. | Warning |
| FQXHMSS2033J | SFTP Service Forwarder [arg1] was not able to upload the Service Data to Ticket to [arg2]:[arg3] due to invalid credentials. The entry has no more retries left. The process for this event will be dropped. | Warning |
| FQXHMSS2034J | SFTP Service Forwarder [arg1] was not able to upload the Service Data to Ticket to [arg2]:[arg3] due to some transfer errors. The entry has no more retries left. The process for this event will be dropped. | Warning |
| FQXHMSS2037J | The Call Home connectivity test started by user [arg1] at IP Address [arg2] failed. | Warning |
| FQXHMSS2040J | Lenovo Upload Facility Service Forwarder [arg1] was not able to upload the Service Data to ticket to [arg2] due to connectivity issues. The entry has no more retries left. The process for this event will be dropped. | Warning |
| FQXHMSS2041J | Lenovo Upload Facility Service Forwarder [arg1] was not able to upload the Service Data to ticket to [arg2] due to connectivity issues. The number of retries left is [arg3] | Warning |
| FQXHMSS2063J | Lenovo Call Home Test Connection could not be executed. | Warning |
| FQXHMSS2064J | The information provided to do a Manual Software Lenovo Call Home is not valid. | Warning |
| FQXHMSS2065J | Could not generate a Manual Software Lenovo Call Home. | Warning |
| FQXHMSS2066J | Could not save customer number for future Call Home. | Warning |
| FQXHMSS2079J | The request to update maintenance information has encountered various issues. | Warning |
| FQXHMSS2080J | The Customer Number provided to do a Manual Software Lenovo Call Home is not valid. | Warning |
| FQXHMSS2081J | The Warranty Settings could not be set. | Warning |
| FQXHMSS2082J | The Warranty Settings could not be retrieved. | Warning |
| FQXHMSS2083J | The file could not be uploaded to Ticket. | Warning |
| FQXHMSS2084J | xClarity Administrator could not update the file previously uploaded. | Warning |
| FQXHMSS2085J | The maintenance information received is not valid. | Warning |
| FQXHMSS2086J | The maintenance information could not be created. | Warning |
| FQXHMSS2087J | The request to update maintenance information is not valid. | Warning |
| FQXHMSS2088J | The request to remove device from maintenance is not valid. | Warning |
| FQXHMSS2089J | The request to remove device from maintenance failed. | Warning |
| FQXHMSS2090J | The request to update maintenance information failed. | Warning |
| FQXHMSS2091J | The request to retrieve maintenance information is not valid. | Warning |
| FQXHMSS2092J | The customer number provided is not valid. | Warning |
| FQXHMSS2093J | Could not verify customer number. | Warning |
| FQXHMSS2098J | The case number provided is invalid. | Warning |
| FQXHMSS2099J | The case number provided doesn't exist. | Warning |
| FQXHMSS2100J | The case number provided is not a Lenovo ticket number. | Warning |
| FQXHMSS2101J | The case note could not be added. | Warning |
| FQXHMSS2102J | The case note could not be added. | Warning |
| FQXHMSS2104J | The Case note provided is invalid. | Warning |
| FQXHMSS2105J | Lenovo Call Home Forwarder is disabled. | Warning |
| FQXHMSS2106J | Could not generate a Lenovo Call Home Passh Through. | Warning |
| FQXHMSS2107J | The information provided to do a Lenovo Call Home Pass Through is not valid. | Warning |
| FQXHMSS2108J | Could not generate a Lenovo Call Home Pass Through. | Warning |
| FQXHMSS2110J | Information provided to accept the new Lenovo Privacy Statement is invalid | Warning |
| FQXHMSS2111J | Lenovo Privacy Statement has already been accepted and cannot be modified. | Warning |
| FQXHMSS2112J | An error occurred while trying to accept the Lenovo Privacy Statement. | Warning |
| FQXHMSS2113J | Action is not permitted because user has not accepted the new Lenovo Privacy Statement. | Warning |
| FQXHMSS2114J | This function cannot be performed because there is not sufficient licensing deployed. | Warning |
| FQXHMSS2115J | The configuration for Call Home was not saved. | Warning |
| FQXHMSS2116J | The operation to change Call Home server was unsuccessful. | Warning |
| FQXHMSS2243J | Lenovo Case {0} has not been deleted because the state is {1}. | Warning |
| FQXHMSS3037J | The Lenovo Call Home connectivity test started by user [arg1] at IP Address [arg2] failed. | Warning |
| FQXHMSS4002F | Internal service [arg1] terminated unexpectedly, and the VM will be restarted. Debug data on the termination has been collected and stored at [arg2] | Warning |
| FQXHMSS4003F | Internal service [arg1] terminated unexpectedly, and it could not be restarted. Debug data on the termination has been collected and stored at [arg2] | Warning |
| FQXHMSS4004F | Internal service [arg1] terminated unexpectedly, and it will not be recovered. Debug data on the termination has been collected and stored at [arg2] | Warning |
| FQXHMSS4005F | Internal service [arg1] terminated unexpectedly, and it could not to be restarted. As a result, the VM will be rebooted. Debug data on the termination has been collected and stored at [arg2] | Warning |
| FQXHMSS4012F | Internal service [arg1] terminated unexpectedly, and the VM will be restarted. No debug data was collected. | Warning |
| FQXHMSS4013F | Internal service [arg1] terminated unexpectedly, and it could not be restarted. No debug data was collected. | Warning |
| FQXHMSS4014F | Internal service [arg1] terminated unexpectedly, and will not be recovered. No debug data was collected. | Warning |
| FQXHMSS4015F | Internal service [arg1] terminated unexpectedly, and it could not be restarted. As a result, the VM will be rebooted. No debug data was collected. | Warning |
| FQXHMSS5067J | Call Home event with ID [arg1] from component [arg2] failed to be called home. Remaining retries [arg3]. | Warning |
| FQXHMSS5075J | Call Home event with ID [arg1] from component [arg2] failed to call home. There are no more remaining retries, so this function is aborting. | Warning |
| FQXHMSS5077J | For Call Home event with ID [arg1] from component [arg2], there was a failure when attaching service data to ticket number [arg3]. The number of remaining retries left is [arg4]. | Warning |
| FQXHMSS5079J | For Call Home event with ID [arg1] from component [arg2], there was a failure when attaching additional service data files to ticket number [arg3]. The number of remaining retries left is [arg4]. | Warning |
| FQXHMSS5100I | Events with event code [arg1] generated from system [arg2] will be suppressed from Service Data data auto-collect and Service Forwarding processing for [arg3] hours. | Warning |
| FQXHMSS5107I | The management server detected duplicate files. | Warning |
| FQXHMSS5111I | The request from user [arg1] from IP address [arg2] to enable the option to suppress service forwarders for excluded events was not successful. | Warning |
| FQXHMSS5112I | The request from user [arg1] from IP address [arg2] to disable the option to suppress service forwarders for excluded events was not successful. | Warning |
| FQXHMSS5113I | User [arg1] from IP address [arg2] has enabled the IP Duplication check service. | Warning |
| FQXHMSS5114I | User [arg1] from IP address [arg2] has disabled the IP Duplication check service. | Warning |
| FQXHMSS9005J | The request to change the log size was not successful. | Warning |
| FQXHMSS9006J | The request to change the log size was not successful. | Warning |
| FQXHMSS9007J | The maximum archive number should be positive, non zero, and no more than {0}. | Warning |
| FQXHMSS9008J | A logger was not selected. | Warning |
| FQXHMSS9015J | The request to generate a Service Data file was not successful, due to a previous request still in process. | Warning |
| FQXHMSS9023J | Updating the contact information on chassis with UUID {0} for Call Home was unsuccessful. | Warning |
| FQXHMST0001G | A trap alert destination subscription failure occurred when user {0} managed server {1} | Warning |
| FQXHMST0002G | A trap alert destination unsubscription failure occurred when user {0} unmanaged server {1} | Warning |
| FQXHMST0003G | Inventory data could not be retrieved from the endpoint {0} | Warning |
| FQXHMST0004G | Credentials could not be updated from endpoint {0} | Warning |
| FQXHMST0005G | User {0} cannot removed the credentials from endpoint {1} | Warning |
| FQXHMST0006G | User {0} cannot remove endpoint {1}. | Warning |
| FQXHMST0007G | Endpoint {0} could not be accessed because credentials were refused. | Warning |
| FQXHMST0008G | Endpoint {0} could not be accessed. | Warning |
| FQXHMST0009G | User {0} cannot access the endpoint {1}. | Warning |
| FQXHMST0010G | The SSL/TLS certificate provided by the {0} endpoint is not valid. | Warning |
| FQXHMST0015G | The controller {0} is not operational. | Warning |
| FQXHMTS0001G | A trap alert destination subscription failure occurred when user {0} managed server {1} | Warning |
| FQXHMTS0002G | A trap alert destination unsubscription failure occurred when user {0} unmanaged server {1} | Warning |
| FQXHMTS0003G | Inventory data could not be retrieved from the endpoint {0}. BIOS: {1}, BMC: {2} | Warning |
| FQXHMTS0004G | Credentials could not be updated from endpoint {0} | Warning |
| FQXHMTS0005G | User {0} cannot removed the credentials from endpoint {1} | Warning |
| FQXHMTS0006G | User {0} cannot remove endpoint {1}. | Warning |
| FQXHMTS0007G | There is no IPMI user slot available in the endpoint when user {0} was managing the server {1} | Warning |
| FQXHMTS0008G | The NTP server could not be set on the endpoint when user {0} was managing the server {1}. | Warning |
| FQXHMTS0009G | Endpoint {0} could not be accessed because credentials were refused. | Warning |
| FQXHMTS0010G | Endpoint {0} could not be accessed. | Warning |
| FQXHMTS0011G | User {0} cannot access the endpoint {1}. | Warning |
| FQXHMUP2001G | No managed data was found. | Warning |
| FQXHMUP2004J | The managed chassis list does not contain any {0}. | Warning |
| FQXHMUP2005J | Inventory collection did not find any {0} with an UUID of {1}. | Warning |
| FQXHMUP2007F | Inventory retrieval was not complete. | Warning |
| FQXHMUP2102J | Could not retrieve the token for the provided device {0}. | Warning |
| FQXHMUP2201G | Ethernet over USB is not enabled for device {0}. | Warning |
| FQXHMUP2202G | Firmware updates to the standby CMM are not supported on device {0}. | Warning |
| FQXHMUP2203G | Stacked mode is enabled on Flex System switch {0}. | Warning |
| FQXHMUP2204G | Protected mode is enabled on Flex System switch {0}. | Warning |
| FQXHMUP2205G | Device {0} is in an unsupported complex. | Warning |
| FQXHMUP2206G | Component {0} is in an unsupported option. | Warning |
| FQXHMUP2207G | Device {0} is an unsupported device with a machine type of {1}. | Warning |
| FQXHMUP2208G | Down-level firmware was found on option {0}. | Warning |
| FQXHMUP2209G | This device is not accessible. | Warning |
| FQXHMUP2210G | Device {0} is an unsupported node in the complex. | Warning |
| FQXHMUP2211G | Firmware updates to the active banks of switch modules are not supported on device {0}. | Warning |
| FQXHMUP2212G | Inventory collection is not complete. | Warning |
| FQXHMUP2213G | Could not retrieve the IP address for the provided device. | Warning |
| FQXHMUP2214G | Inventory collection will complete after the device powers on. | Warning |
| FQXHMUP2216G | OS device-driver updates are not supported for this device. | Warning |
| FQXHMUP2217G | Device-driver updates are not supported for this operating system. | Warning |
| FQXHMUP2218G | Firmware updates on IBM disk drives in Lenovo servers is not supported. | Warning |
| FQXHMUP2219G | The power supply unit (PSU) current firmware version is too low and does not support update. | Warning |
| FQXHMUP2501G | The repository operation could not complete because an update is in use. | Warning |
| FQXHMUP2503G | An invalid parameter was passed to the repository operation. | Warning |
| FQXHMUP2512F | The import process is complete. Some files were discarded for unknown reasons. | Warning |
| FQXHMUP2513F | The import process is complete. Some files are not valid signed packages and were discarded. | Warning |
| FQXHMUP2514F | The import process is complete. Some files are not recognized as update packages and were discarded. | Warning |
| FQXHMUP2515F | The import process is complete. Some files are for update types that are not supported and were discarded. | Warning |
| FQXHMUP2516F | The import process is complete. Some files are for operating systems that are not supported and were discarded. | Warning |
| FQXHMUP2517F | The import process is complete. Some files are for machine type that are not supported and were discarded. | Warning |
| FQXHMUP2518F | The import process is complete. Some files are not referenced by any metadata file that is currently in the repository and were discarded. | Warning |
| FQXHMUP2519F | The import process is complete. Some files are corrupted and were discarded. | Warning |
| FQXHMUP2522F | The import process is complete. Some update packages have a development-only version. | Warning |
| FQXHMUP2530F | Delete complete. Some update packages are used by firmware-compliance policies and cannot be deleted. | Warning |
| FQXHMUP2531F | Delete complete. Some update packages are referenced by other update packages and cannot be deleted. | Warning |
| FQXHMUP2532F | Delete complete. Some update packages are locked by other tasks and cannot be deleted. | Warning |
| FQXHMUP2533F | Delete complete. Some update packages are part of UXSP package and cannot be deleted. | Warning |
| FQXHMUP2534F | Delete complete. Some firmware-compliance policies files cannot be deleted. | Warning |
| FQXHMUP2540F | The import process is complete. Some files were discarded because they are for updates to the management server. | Warning |
| FQXHMUP2541F | The import process is complete. Some files were discarded because they are for firmware updates. | Warning |
| FQXHMUP2542F | The import process is complete. Some files were discarded because they are for Windows device drivers. | Warning |
| FQXHMUP2543J | Update packages are missing. | Warning |
| FQXHMUP2544F | Packaging the update packages failed. | Warning |
| FQXHMUP3001J | The policy name already exists. | Warning |
| FQXHMUP3002J | The policy is currently in use. | Warning |
| FQXHMUP3004J | The policy does not exist. | Warning |
| FQXHMUP3005J | Critical info is missing of the I/O Switch in inventory. | Warning |
| FQXHMUP3007J | The device type is not supported. | Warning |
| FQXHMUP3008J | Update packages are missing. | Warning |
| FQXHMUP3013J | The compliance result is incomplete for device in slot {0} of Chassis {1}. | Warning |
| FQXHMUP3020J | The compliance result is incomplete for rack server {0} with lowestRackunit {1} in {2}. | Warning |
| FQXHMUP3032F | Some files already exist. The files were not imported. | Warning |
| FQXHMUP3035F | The import process is complete. | Warning |
| FQXHMUP3101J | The firmware installed on this system is non-compliant. | Warning |
| FQXHMUP4003J | User ID {0} does not have sufficient permissions for this specific request. | Warning |
| FQXHMUP4009G | The device [arg1] is currently awaiting user action by user [arg2] for Pending Firmware Maintenance Mode. | Warning |
| FQXHMUP4081F | The {0} task was canceled by user. | Warning |
| FQXHMUP4082F | The {0} task was canceled by user. | Warning |
| FQXHMUP4083F | The {0} task was canceled by user. | Warning |
| FQXHMUP4084F | The {0} task was canceled because the task did not complete successfully and the directive StopOnError was specified for the job. | Warning |
| FQXHMUP4085F | The {0} task was canceled because the task did not complete successfully and the directive StopEndpointOnError was specified for the job. | Warning |
| FQXHMUP4086F | The {0} task was canceled because a dependency did not complete successfully. | Warning |
| FQXHMUP4163F | The firmware update was skipped. | Warning |
| FQXHMUP4164F | The firmware update was skipped. | Warning |
| FQXHMUP4167F | The firmware update was skipped. | Warning |
| FQXHMUP4169G | An error occurred during the restart of the system. | Warning |
| FQXHMUP4205F | A Flex System switch in the chassis does not meet the minimum firmware version requirement for the Chassis Management Module update. | Warning |
| FQXHMUP4305F | The Flex System switch in bay {0} does not meet the minimum firmware version {1} requirement for this Chassis Management Module update. | Warning |
| FQXHMUP4306F | The Flex switch module in bay {0} does not support the minimum firmware requirement for the Chassis Management Module update. | Warning |
| FQXHMUP4309F | The Flex System switch is powered off. | Warning |
| FQXHMUP4310F | The Flex System switch did not pass the verification step for firmware update. | Warning |
| FQXHMUP4539G | An unknown error occurred while attempting to finalize the device update process. | Warning |
| FQXHMUP4547G | User {0} does not have sufficient permissions to perform firmware updates to the device. | Warning |
| FQXHMUP4549G | User {0} does not have sufficient permissions to perform power action to the device. | Warning |
| FQXHMUP4708F | An error occurred while connecting to the device. | Warning |
| FQXHMUP4711F | A warning occurred performing the firmware update on the {0} inband component. | Warning |
| FQXHMUP4911G | Power actions are not supported for storage devices. | Warning |
| FQXHMUP4912G | An update is in progress for the specified device. | Warning |
| FQXHMUP4942F | Memory test is not supported on this server. | Warning |
| FQXHMUP4943F | XCC starts support memoryTestOptions in 2023/1, current XCC version is {0}, release date is {1}, skip memory test config. | Warning |
| FQXHMUP4944F | Failed to get biosAttributes, skip memory test config. | Warning |
| FQXHMUP4945F | memoryTestOptions is null, UEFI does not support memory test, skip memory test config. | Warning |
| FQXHMUP4947F | Failed to modify bios settings, memory test may be skipped. | Warning |
| FQXHMUP6101F | The repository size is not valid. | Warning |
| FQXHMUP6101J | The request to update the application by user [arg1] failed with return code [arg2]. | Warning |
| FQXHMUP6103F | The request to update the application by user {0} completed with return code {1}. The requested update is not applicable. | Warning |
| FQXHMUP7503F | At least one of the parsed parameters encountered a non-fatal error. | Warning |
| FQXHMUP7520F | The verification task was not attempted. | Warning |
| FQXHMUP7526F | The switch firmware version is lower than minimum recommended version. | Warning |
| FQXHMUP7701G | The verification task found that the specified storage-management user account does not have permission to access the FTP interface. | Warning |
| FQXHMUP7702G | The verification task found that the specified package cannot be applied. | Warning |
| FQXHMUP7703G | The verification task found an issue with the current health status of the storage device. | Warning |
| FQXHMUP7704G | The verification task found that the storage device could not be accessed. | Warning |
| FQXHMUP7920F | The verification task was not attempted. | Warning |
| FQXHMUP8003G | An invalid parameter was passed to the management-server update operation. | Warning |
| FQXHMUP8008G | The management-server update operation failed to start. | Warning |
| FQXHMUP8010G | The management-server update operation could not complete because another update is already in progress. | Warning |
| FQXHMUP8011G | A management-server update operation is already in progress. The requested update operation cannot be started. | Warning |
| FQXHMUP8012G | The management-server update package is not found. | Warning |
| FQXHMUP8014G | The management-server update operation failed to start. | Warning |
| FQXHMUP8015G | The management-server update operation failed. | Warning |
| FQXHMUP8018J | User ID {0} does not have sufficient permissions for this specific request. | Warning |
| FQXHMUP8019J | The management-server update package is not applicable. | Warning |
| FQXHMCP1215M | Failover from server [arg1] to standby server [arg2] was not successful. | Critical |
| FQXHMCP1255M | No standby servers were available in pool [arg1] for failover for server [arg2]. | Critical |
| FQXHMCP5105J | Pattern name [arg1] is already in use. | Critical |
| FQXHMCP5125J | Pattern [arg1] was not found. | Critical |
| FQXHMCP5305J | Address pool name [arg1] is already in use. | Critical |
| FQXHMCP5325J | Address pool [arg1] was not found. | Critical |
| FQXHMCP5405J | Standby pool name [arg1] is already in use. | Critical |
| FQXHMCP5425J | Standby pool [arg1] was not found. | Critical |
| FQXHMCP5505J | Placeholder chassis name [arg1] is already in use. | Critical |
| FQXHMCP5525J | Placeholder chassis [arg1] was not found. | Critical |
| FQXHMCP5605J | Policy name [arg1] is already in use. | Critical |
| FQXHMCP5625J | Policy [arg1] was not found. | Critical |
| FQXHMCR0103J | Call home service is unavailable for the moment due to a loss of connectivity | Critical |
| FQXHMDI0049K | The health of SSD [arg1] in bay [arg2] of the RAID configuration [arg3] has diminished to a critical state. | Critical |
| FQXHMDM0173K | The secure erase drive encountered an error for server {arg1}. | Critical |
| FQXHMDM0177K | The DNS and FQDN configuration encountered an error for server {arg1}. | Critical |
| FQXHMEM0410J | A critical alert was asserted on device [arg1] with alert ID [arg2]. | Critical |
| FQXHMFC0000N | The {0} service is not available. | Critical |
| FQXHMFC0001M | The management server encountered an internal error while attempting to import the image into the image repository. | Critical |
| FQXHMFC0002M | The specified operating system image is not valid. | Critical |
| FQXHMFC0003M | The imported operating systems could not be retrieved from the image repository. | Critical |
| FQXHMFC0004M | An internal error occurred. | Critical |
| FQXHMFC0005M | At least one server must be specified as a target when deploying an image. | Critical |
| FQXHMFC0006M | The number of image deployments in progress ({0}) and the newly requested image deployments ({1}) exceeds the maximum number of images that can be deployed concurrently. You can deploy a maximum of ({2}) images concurrently. | Critical |
| FQXHMFC0007M | The image for server {0} cannot be deployed. | Critical |
| FQXHMFC0008M | An internal error occurred while attempting to deploy an operating system image. | Critical |
| FQXHMFC0009M | The operating system deployment process did not complete for server {0}. | Critical |
| FQXHMFC0012M | The operating system deployment process did not complete for server {0}. The image deployment process for this server has timed out while preparing for image deployment at {1}. | Critical |
| FQXHMFC0015M | The operating system deployment process did not complete for server {0}. The image deployment process for this server has timed out because its status has not been updated from {1} in the last {2} minutes. | Critical |
| FQXHMFC0018M | The operating system deployment process did not complete for the server. | Critical |
| FQXHMFC0019M | The operating system deployment process did not complete for server {0}. | Critical |
| FQXHMFC0020M | The operating system deployment process did not complete for the server. | Critical |
| FQXHMFC0021M | The operating system deployment process did not complete for server {0}. | Critical |
| FQXHMFC0022M | Could not delete node profile information for the server. | Critical |
| FQXHMFC0023M | The operating system deployment process did not complete for the server. | Critical |
| FQXHMFC00242M | The deployment-data and software location value contains a forward slash character. | Critical |
| FQXHMFC00243M | The deployment-data and software location value contains a back slash character. | Critical |
| FQXHMFC00244M | The unattend file did not contain the {0} macro. The unattend file may not have scripts critical for the deploy to be successful. | Critical |
| FQXHMFC0024M | The operating system deployment process did not complete for server {0}. | Critical |
| FQXHMFC0025M | The operating system deployment process did not complete for the server. | Critical |
| FQXHMFC0027M | The operating system deployment process did not complete for server {0}. | Critical |
| FQXHMFC0028M | Could not unmount the bootable ISO due to missing information about the server. | Critical |
| FQXHMFC0029M | Could not unmount remote media {0} from server {1}. | Critical |
| FQXHMFC0030M | An {0} error occurred during the unmount of remote media {1} from server {2}. | Critical |
| FQXHMFC0031M | The operating system deployment process did not complete for the server. | Critical |
| FQXHMFC0032M | The operating system deployment process did not complete for server {0}. | Critical |
| FQXHMFC0033M | The operating system deployment process did not complete for the server. | Critical |
| FQXHMFC0034M | The operating system deployment process did not complete for server {0}. | Critical |
| FQXHMFC0035M | An internal error occurred due to an invalid or missing value for {0} property in the FlexCat.properties file. | Critical |
| FQXHMFC0036M | An internal error occurred (JSON response {0}). | Critical |
| FQXHMFC0037M | REST method {0} is not supported. | Critical |
| FQXHMFC0039M | Image deployment status {0} reported for image deployment {1} is not valid. | Critical |
| FQXHMFC0047M | The operating system deployment process did not complete for server {0}. An error occurred while trying to restart the server. | Critical |
| FQXHMFC0048M | The operating system deployment process did not complete for server {0}. The image deployment process for this server has timed out because its status has not been updated from {1} in the last {2} minutes. | Critical |
| FQXHMFC0052M | A remote file server with the same name already exists. | Critical |
| FQXHMFC0053M | Global settings have not been applied. | Critical |
| FQXHMFC0054M | Global settings have not been applied. | Critical |
| FQXHMFC0055M | The operating system cannot be deployed for server {0}. | Critical |
| FQXHMFC0056M | The specified operating system profile cannot be deleted. | Critical |
| FQXHMFC0057M | The maximum number of imported operating systems has been reached. | Critical |
| FQXHMFC0058N | The image deployment service is disabled. | Critical |
| FQXHMFC0059M | The default operating system credentials have not been changed. | Critical |
| FQXHMFC0060M | The default operating system credentials have not been changed. | Critical |
| FQXHMFC0061M | The default operating system credentials have not been changed. | Critical |
| FQXHMFC0062M | Could not get the default credentials to be used during operating system deployment. | Critical |
| FQXHMFC0063M | The operating system image {0} cannot be imported. | Critical |
| FQXHMFC0065M | The operating system deployment process did not complete for server {0}. | Critical |
| FQXHMFC0066M | The operating system deployment process did not complete. Deployment of the ESXi operating system to SAN storage volume {0} is not supported to this server because it has a local disk drive present. | Critical |
| FQXHMFC0067M | The operating system deployment process did not complete. The selected storage option of {0} was not found or the storage configuration is not supported for this server during the operating system installation. | Critical |
| FQXHMFC0068M | The operating system deployment process did not complete. An unsupported USB key was found for this server during the operating system installation. | Critical |
| FQXHMFC0069M | The operating system deployment process did not complete for server {0} ({1}). | Critical |
| FQXHMFC0070M | The operating system deployment process did not complete for server {0} ({1}). | Critical |
| FQXHMFC0071M | The operating system deployment process did not complete for server {0} ({1}). | Critical |
| FQXHMFC0072M | The operating system deployment process did not complete for server {0} ({1}). | Critical |
| FQXHMFC0073M | The operating system deployment process has been stopped for server {0} ({1}). | Critical |
| FQXHMFC0075M | The operating system deployment process has been stopped for server {0} ({1}). | Critical |
| FQXHMFC0077M | The maximum number of OS images or custom files that can be imported concurrently has been reached. | Critical |
| FQXHMFC0078M | Already at the maximum number of image operations concurrently. | Critical |
| FQXHMFC0079M | An OS image or custom file with the same file name exists in the OS-images repository. | Critical |
| FQXHMFC0080M | Unable to obtain the list of all chassis. | Critical |
| FQXHMFC0081M | Unable to mount the ISO image from the server. | Critical |
| FQXHMFC0082M | Unable to unmount the ISO from the server. | Critical |
| FQXHMFC0083M | Unable to deploy the operating system to the server. | Critical |
| FQXHMFC0084M | Verification of checksum failed. | Critical |
| FQXHMFC0085M | The checksum of the imported file does not match the provided checksum. | Critical |
| FQXHMFC0086M | Could not set the host name to be used during operating system deployment. | Critical |
| FQXHMFC0087M | Unable to obtain the list of all nodes. | Critical |
| FQXHMFC0093M | Authentication failed.\nMake sure that the user ID and password are correct. Then, try again. | Critical |
| FQXHMFC0100M | Unable to mount to the server because a connection could be be established. | Critical |
| FQXHMFC0103M | A serious error has occurred. | Critical |
| FQXHMFC0104M | Could not mount the remote drive to the server. | Critical |
| FQXHMFC0105M | Could not upload the image to the server. | Critical |
| FQXHMFC0106M | Could not upload the image to the server due to insufficient space on the server. | Critical |
| FQXHMFC0107M | Could not upload the image to the server because another image with the same name already exists on the server. | Critical |
| FQXHMFC0109M | Could not initialize the connection to the server. The exception was: {0}. | Critical |
| FQXHMFC0112M | The operating system deployment process did not complete for the server. | Critical |
| FQXHMFC0113M | The operating system deployment process did not complete for the server. | Critical |
| FQXHMFC0116M | Cannot lock server {0}. | Critical |
| FQXHMFC0117M | An OS image could not be deployed due to an internal error. | Critical |
| FQXHMFC0119M | Cannot cancel the running job. | Critical |
| FQXHMFC0121M | The operating system deployment process did not complete for the server {0}. | Critical |
| FQXHMFC0123M | The operating system deployment process did not complete for server {0} ({1}). | Critical |
| FQXHMFC0126M | The operating system deployment process did not complete for server {0}. | Critical |
| FQXHMFC0127M | Unable to obtain the nodes in deploying status. | Critical |
| FQXHMFC0128M | Unable to obtain the Global Setting data. | Critical |
| FQXHMFC0129M | Unable to set the Global Setting data. | Critical |
| FQXHMFC0130M | Unable to set the Global Setting data. | Critical |
| FQXHMFC0131M | Global settings have not been applied. | Critical |
| FQXHMFC0132M | The number of Microsoft Windows image deployments in progress ({0}) and the newly requested Microsoft Windows image deployments ({1}) exceeds the maximum number of Microsoft Windows images that can be deployed concurrently. You can deploy a maximum of ({2}) Microsoft Windows images concurrently. | Critical |
| FQXHMFC0139M | The operating system deployment process did not complete. The deployment process detected an additional attached disk drive {0} that contains a System type partition {1}. | Critical |
| FQXHMFC0140M | Can not process the request. | Critical |
| FQXHMFC0141M | The management server encountered an internal error while attempting to import the image into the image repository. | Critical |
| FQXHMFC0142M | Unable to obtain the inventory change of the nodes. | Critical |
| FQXHMFC0143M | The operating system image cannot be imported. | Critical |
| FQXHMFC0144M | The import job cannot be created. | Critical |
| FQXHMFC0145M | The file was not imported into the OS images repository successfully. | Critical |
| FQXHMFC0150M | An internal error occurred while attempting to save data for Global Settings. | Critical |
| FQXHMFC0151M | An internal error occurred while attempting to save data for Global Settings. | Critical |
| FQXHMFC0152M | An internal error occurred while attempting to save data for Global Settings. | Critical |
| FQXHMFC0153M | An internal error occurred while attempting to save data for Global Settings. | Critical |
| FQXHMFC0154M | The file name extension for the imported file is not correct. Ensure that the imported file has the correct extension for the type of file that is being imported, and try the import again. | Critical |
| FQXHMFC0155M | The operating system deployment process has been stopped for server {0} ({1}). | Critical |
| FQXHMFC0156M | The operating system deployment process has been stopped for server {0} ({1}). | Critical |
| FQXHMFC0157M | The operating system deployment process did not complete for server {0} ({1}). | Critical |
| FQXHMFC0160M | Could not retrieve the samba credentials to be used during operating-system deployment. | Critical |
| FQXHMFC0163M | The imported file type was not recognized. | Critical |
| FQXHMFC0165M | An image by that name already exists in the image repository. | Critical |
| FQXHMFC0166M | The operating system deployment process has been stopped for server {0} ({1}). | Critical |
| FQXHMFC0167M | The remote file import operation failed. | Critical |
| FQXHMFC0168M | The remote file import operation failed. | Critical |
| FQXHMFC0169M | The remote file import operation failed. | Critical |
| FQXHMFC0170M | The remote file import operation failed. | Critical |
| FQXHMFC0171M | A secure connection to the server could not be completed successfully. | Critical |
| FQXHMFC0172M | The remote file import operation failed. | Critical |
| FQXHMFC0173M | The remote file import operation failed. | Critical |
| FQXHMFC0174M | The request could not be completed due to malformed syntax. | Critical |
| FQXHMFC0175M | The OS file operation could not be completed successfully. | Critical |
| FQXHMFC0176M | The files cannot be imported. | Critical |
| FQXHMFC0177M | A secure connection to the server could not be completed successfully. | Critical |
| FQXHMFC0178M | XClarity Administrator cannot connect to the specified host. | Critical |
| FQXHMFC0179M | A connection cannot be established to the remote file server. | Critical |
| FQXHMFC0180M | Authentication issue occurred while trying to connect to the remote file server. | Critical |
| FQXHMFC0181M | The received profile Id was not found on server. | Critical |
| FQXHMFC0182M | An error has found when saving the custom profile on internal databases. | Critical |
| FQXHMFC0183M | The management server encountered an internal error while attempting to save the custom profile into the repository. | Critical |
| FQXHMFC0184M | Some internal error happened during the FlexCat management of custom profiles. | Critical |
| FQXHMFC0185M | The custom profile could not be exported. | Critical |
| FQXHMFC0186M | You cannot import OS-image profiles that were generated from later releases of the management server. | Critical |
| FQXHMFC0187M | The imported profile requires a base operating system not available in this appliance. | Critical |
| FQXHMFC0188M | The current appliance does not have enough space to import this custom profile. | Critical |
| FQXHMFC0192M | The custom profile export job can not be created. | Critical |
| FQXHMFC0195M | The custom profile name must not be changed. | Critical |
| FQXHMFC0196M | One or more items to be deleted could not be removed from the system. | Critical |
| FQXHMFC0197M | The specified remote-file-server ID is not valid. | Critical |
| FQXHMFC0198M | An internal error occurred while reading the remote-file-server information. | Critical |
| FQXHMFC0199M | The specified path to the remote-file-server does not exist or is not reachable. | Critical |
| FQXHMFC0200M | The custom profile cannot be transferred to the remote file server. | Critical |
| FQXHMFC0201M | The checksum value cannot be generated for the custom profile. | Critical |
| FQXHMFC0202M | The checksum value cannot be calculated for the imported custom profile. | Critical |
| FQXHMFC0203M | The custom profile could not be imported. | Critical |
| FQXHMFC0204M | A secure connection to the remote file server could not be completed successfully. | Critical |
| FQXHMFC0205M | A secure connection to the server could not be completed successfully. | Critical |
| FQXHMFC0206M | Could not set the hostname to be used during operating-system deployment. | Critical |
| FQXHMFC0207M | A customized OS-image profile with the same name already exists. | Critical |
| FQXHMFC0208M | The profile that you are attempting to import has no metadata file. | Critical |
| FQXHMFC0209M | The server was not able to join the specified Active Directory domain. | Critical |
| FQXHMFC0210M | The server successfully joined the Active Directory domain {0}. | Critical |
| FQXHMFC0211M | The server successfully joined Active Directory using the specified metadata. | Critical |
| FQXHMFC0212M | An internal error occurred while extracting the uploaded .tar file. | Critical |
| FQXHMFC0214M | The operating-system deployment did not complete. The deployment process detected an embedded hypervisor key that is connected to the server. | Critical |
| FQXHMFC0215M | The profile name contains a character that is not valid. Profile names can only contain the following characters: Lowercase characters (a-z) Uppercase characters (A-Z) Numbers (0-9) Underscore (_) Dash (-). | Critical |
| FQXHMFC0216M | The import request is already in progress. | Critical |
| FQXHMFC0217M | The description contains a character that is not valid. Description can only contain the following characters: Lowercase characters (a-z) Uppercase characters (A-Z) Numbers (0-9) Underscore (_) Dash (-). | Critical |
| FQXHMFC0218M | Deployment validation checking failed for a server. | Critical |
| FQXHMFC0219M | You must import the base {0} image before importing this kISO image. | Critical |
| FQXHMFC0220M | To deploy SLES 11 SP4 or 12 SP2 to a ThinkSystem server, you must use a kISO profile. | Critical |
| FQXHMFC0221M | Before importing the kISO, you must first delete the base SLES operating system and then import the base operating system again. | Critical |
| FQXHMFC0226M | Errors found during validation of the custom configuration settings. | Critical |
| FQXHMFC0227M | Unable to update the specified resource ID. | Critical |
| FQXHMFC0230M | The custom profile has encountered an error during post-install. The error message is: {0}. | Critical |
| FQXHMFC0237M | The bundle file is not supported by the current Lenovo XClarity Administrator version. Download the latest bundle file from the Lenovo Support website. | Critical |
| FQXHMFC0245M | Deployment validation checking failed for a server. The following IP addresses that were specified for operating-system deployment are already in use: {0}. | Critical |
| FQXHMFC0251M | The management server cannot validate the bundle file. Ensure that you selected a Lenovo bundle file and its associated signature file, and try again. | Critical |
| FQXHMFC0253M | A non-zero VLAN ID was specified, but VLAN tagging is disabled. To deploy with a VLAN ID, VLAN tagging must be enabled in Global Settings. | Critical |
| FQXHMFC0254M | The file could not be deleted. | Critical |
| FQXHMFC0255M | You must import the installer OS image before importing this package image. | Critical |
| FQXHMFC0261M | The file name contains a character that is not valid. File names can contain only the following characters: lowercase characters (a-z), uppercase characters (A-Z), numbers (0-9), underscores (_), and dashes (-). | Critical |
| FQXHMFC0262M | The host settings for the server with the specified UUID could not be found. | Critical |
| FQXHMFC0263M | The management server encountered an internal error while attempting to retrieve the host settings. | Critical |
| FQXHMFC0264M | The management server encountered an internal error while attempting to save the host settings. | Critical |
| FQXHMFC0265M | The management server encountered an internal error while attempting to delete the host settings for the server with the specified UUID. | Critical |
| FQXHMFC0266M | Your role is not granted with enough privileges to view this information. Please contact your administrator. For information about OS deployment privileges, see "OS deployment privileges" in the XClarity Administrator online documentation. | Critical |
| FQXHMFC0267M | Your role is not granted with enough privileges to view deploy information. Please contact your administrator. For information about OS deployment privileges, see "OS deployment privileges" in the XClarity Administrator online documentation. | Critical |
| FQXHMFC0268M | Your role is not granted with enough privileges to edit deploy information. Please contact your administrator. For information about OS deployment privileges, see "OS deployment privileges" in the XClarity Administrator online documentation. | Critical |
| FQXHMFC0269M | Your role is not granted with enough privileges to view global information. Please contact your administrator. For information about OS deployment privileges, see "OS deployment privileges" in the XClarity Administrator online documentation. | Critical |
| FQXHMFC0270M | Your role is not granted with enough privileges to edit global information. Please contact your administrator. For information about OS deployment privileges, see "OS deployment privileges" in the XClarity Administrator online documentation. | Critical |
| FQXHMFC0271M | Your role is not granted with enough privileges to view image repository information. Please contact your administrator. For information about OS deployment privileges, see "OS deployment privileges" in the XClarity Administrator online documentation. | Critical |
| FQXHMFC0272M | Your role is not granted with enough privileges to edit OS file information. Please contact your administrator. For information about OS deployment privileges, see "OS deployment privileges" in the XClarity Administrator online documentation. | Critical |
| FQXHMFC0273M | Your role is not granted with enough privileges to delete OS file information. Please contact your administrator. For information about OS deployment privileges, see "OS deployment privileges" in the XClarity Administrator online documentation. | Critical |
| FQXHMFC0274M | Your role is not granted with enough privileges to view remote file server information. Please contact your administrator. For information about OS deployment privileges, see "OS deployment privileges" in the XClarity Administrator online documentation. | Critical |
| FQXHMFC0275M | Your role is not granted with enough privileges to edit remote file server information. Please contact your administrator. For information about OS deployment privileges, see "OS deployment privileges" in the XClarity Administrator online documentation. | Critical |
| FQXHMFC0276M | Your role is not granted with enough privileges to delete remote file server information. Please contact your administrator. For information about OS deployment privileges, see "OS deployment privileges" in the XClarity Administrator online documentation. | Critical |
| FQXHMFC0277M | The management server encountered an internal error while attempting to retrieve the OS information. | Critical |
| FQXHMFC0278M | The OS information of the server with the specified UUID could not be found. | Critical |
| FQXHMFC0279M | The operating-system images cannot be deployed. | Critical |
| FQXHMFC0285M | The selected Customization Type Associated unattend and configuration-settings files requires the selection of at least one unattend file with an associated configuration-settings file. Import an unattend file with an associated configuration-settings file, and specify the files for use with the custom profile. | Critical |
| FQXHMFC0286M | The selected Customization Type Only unattend files requires the selection of at least one unattend file. Import an unattend file, and specify the file for use with the custom profile. | Critical |
| FQXHMFC0287M | The selected Customization Type Unassociated unattend and configuration-settings files requires the selection of both an unattend and configuration-settings file. Import an unattend file and a configuration-settings file, and specify the files for use with the custom profile. | Critical |
| FQXHMFC0288M | The selected Customization Type Unassociated unattend and configuration-settings files requires the selection of at least one unattend file. Import an unattend file, and specify the file for use with the custom profile. | Critical |
| FQXHMFC0289M | The selected Customization Type Unassociated unattend and configuration-settings files requires the selection of at least one configuration-settings file. Import a configuration-settings file, and specify the file for use with the custom profile. | Critical |
| FQXHMFC0290M | The selected Customization Type Only configuration-settings files requires the selection of at least one configuration-settings file. Import a configuration-settings file, and specify the file for use with the custom profile. | Critical |
| FQXHMFC0291M | The specified customizations are not valid for this operating system. | Critical |
| FQXHMFC0293M | A deployment is in progress. You cannot change the host settings while the deployment is ongoing. | Critical |
| FQXHMFC0294M | A deployment is in progress. You cannot delete the host settings while the deployment is ongoing. | Critical |
| FQXHMFC0296M | To deploy OS images, a Lenovo XClarity Pro license must be installed for every managed device that supports the Lenovo XClarity Administrator advanced function; however, the number of active licenses is not compliant with the number of managed devices. | Critical |
| FQXHMFC0297M | VLAN tagging is not supported for Linux operating-system deployments. | Critical |
| FQXHMFC049M | Could not set an internal password. | Critical |
| FQXHMFC050M | Cannot get the configuration of the management server. | Critical |
| FQXHMFC148M | The operating system image cannot be imported. | Critical |
| FQXHMFC8601M | The number of servers selected exceeds the number of deployment operations that can occur concurrently. | Critical |
| FQXHMFC8603M | Operating systems cannot be deployed to some of the selected servers. | Critical |
| FQXHMFC8876M | Operating system {0} could not be deployed to node {1} by user {2}. | Critical |
| FQXHMFC8883M | The deployment of operating system {0} to node {1} cannot be canceled by user {2}. | Critical |
| FQXHMMF0005J | Metrics data collection for all DM Storage managed could not start. | Critical |
| FQXHMNM90002E | The provided host is not valid. | Critical |
| FQXHMNM90003E | The provided port is not valid. | Critical |
| FQXHMNM90004E | The provided host could not be resolved. | Critical |
| FQXHMNM90005E | The provided host could not be reached. | Critical |
| FQXHMNM90006E | The provided port could not be reached. | Critical |
| FQXHMNM90007W | The provided port appears to be filtered. | Critical |
| FQXHMNM90008W | The connection test was a success but the port appears to be filtered. | Critical |
| FQXHMNM90009E | The connection test was unsuccessful. The port is closed and appears to be filtered. | Critical |
| FQXHMNM90010E | The connection test was unsuccessful. The port is closed. | Critical |
| FQXHMRC0000N | The {0} service is not available. | Critical |
| FQXHMRC0001M | REST method {0} is not supported. | Critical |
| FQXHMRC0002M | An internal error occurred (JSON response {0}). | Critical |
| FQXHMSE0003N | The request could not be completed. | Critical |
| FQXHMSE0103L | The request to generate a certificate signing request (CSR) was not successful. | Critical |
| FQXHMSE0335K | It has been over 90 days since non-compliance has been detected on {0} . Management functions have been disabled until this issue has been corrected. | Critical |
| FQXHMSE0699K | All external LDAP servers are unreachable. | Critical |
| FQXHMSE0924K | The system is not compliant due to number of managed devices is higher than license permit. | Critical |
| FQXHMSE0926K | Functions disabled due to license not compliant and 90 days of non-compliance expired. | Critical |
| FQXHMSS1021J | The generation of Service Data archive for user [arg1] at IP address [arg2] finished unsuccessfully. | Critical |
| FQXHMSS1023J | The request by user [arg1] at IP address [arg2] to generate a Service Data file was not successful, due to a previous request still in process | Critical |
| FQXHMSS1030J | The request by user [arg1] at IP address [arg2] to change the Call Home configuration was unsuccessful. | Critical |
| FQXHMSS1032J | User [arg1] at IP address [arg2] tried to enable Call Home but the operation was unsuccessful. | Critical |
| FQXHMSS1034J | User [arg1] at IP address [arg2] tried to disable Call Home but the operation was unsuccessful. | Critical |
| FQXHMSS1036J | User [arg1] at IP address [arg2] tried to reset the Call Home configuration, but the operation was unsuccessful. | Critical |
| FQXHMSS2002M | The management server was not able to find the appropriate system to collect the Service Data archive for event [arg1] generated on [arg2]. | Critical |
| FQXHMSS2003M | The management server encountered an error while trying to collect the Service Data archive for event [arg1] generated on [arg2]. | Critical |
| FQXHMSS2004J | The management server was not able to collect the Service Data archive for event [arg1] generated on [arg2]. | Critical |
| FQXHMSS2015M | SFTP Service Forwarder [arg1] encountered an error while trying to upload the collected Service Data to [arg2]:[arg3]. | Critical |
| FQXHMSS2042M | Lenovo Upload Facility Service Forwarder [arg1] encountered an error while trying to upload the collected Service Data to [arg2]:[arg3]. | Critical |
| FQXHMSS2047J | User [arg1] at IP address [arg2] tried to reset the Lenovo Upload Facility configuration, but the operation was unsuccessful. | Critical |
| FQXHMSS5050J | The Call Home test ended unsuccessfully. | Critical |
| FQXHMSS5053J | Call Home test generated by user [arg1] at IP address [arg2] ended unsuccessfully. | Critical |
| FQXHMSS5094J | Collecting the Service Data archive generated by event with ID [arg1] from endpoint [arg2] failed. | Critical |
| FQXHMSS5095J | Saving the collected Service Data archive generated by event with ID [arg1] from endpoint [arg2] inside the server failed. | Critical |
| FQXHMSS5096J | Uploading the collected endpoint Service Data archive to Problem Number with ID [arg1] failed. | Critical |
| FQXHMSS5097J | Uploading additional Service Data archive(s) to Problem Number with ID [arg1] failed. | Critical |
| FQXHMUP1103L | The inventory update request was not successful. | Critical |
| FQXHMUP2002L | Could not retrieve inventory. | Critical |
| FQXHMUP2003M | The inventory retrieval request could not complete. | Critical |
| FQXHMUP2006N | The inventory retrieval request could not complete. | Critical |
| FQXHMUP2099N | An unexpected error occurred. | Critical |
| FQXHMUP2101L | Could not retrieve the token for the provided device. | Critical |
| FQXHMUP2103L | The inventory update request could not complete. | Critical |
| FQXHMUP2104L | Could not update the profile. | Critical |
| FQXHMUP2215L | The security certificate that is used to establish a secure connection to a managed device has become untrusted. | Critical |
| FQXHMUP2502L | The repository operation failed. | Critical |
| FQXHMUP2504L | The repository could not connect with the fix service provider. | Critical |
| FQXHMUP2505L | The update could not be deleted because it is required for another update. | Critical |
| FQXHMUP2506L | The update could not be deleted. | Critical |
| FQXHMUP2510L | The update package cannot be added to the repository because the repository is full. | Critical |
| FQXHMUP2511L | The update could not be deleted because it is used by one or more policies. | Critical |
| FQXHMUP2520L | Internet connection failure. | Critical |
| FQXHMUP2521L | A download error occurred. One or more updates failed to download. | Critical |
| FQXHMUP2551L | The import process is not complete because the file uploading contents do not match the files that was validated. | Critical |
| FQXHMUP2552L | The CRC error was detected from the files acquired. | Critical |
| FQXHMUP2553L | An invalid mount point is used. | Critical |
| FQXHMUP2554L | The remote repository is inaccessible. | Critical |
| FQXHMUP2555L | The remote repository is ready only, this Operation is unsupported. | Critical |
| FQXHMUP2556L | There is a running Swap Repository Job. | Critical |
| FQXHMUP2557L | There is a running job which is using the firmware repository. | Critical |
| FQXHMUP2600L | The download package service was not started because the jobs cannot be registered. | Critical |
| FQXHMUP2601L | The download package service was not started because the job cannot be spawned. | Critical |
| FQXHMUP3003L | The policy could not be found. | Critical |
| FQXHMUP3009L | An unknown error occurred while copying the policy. | Critical |
| FQXHMUP3010L | The request to get compliance results for the device in slot {0} of Chassis {1} failed. | Critical |
| FQXHMUP3011L | The request to get compliance results for the device in slot {0} of Chassis {1} failed. | Critical |
| FQXHMUP3012L | Update packages were not found in the repository for target device in slot {0} of Chassis {1} while computing compliance result. | Critical |
| FQXHMUP3017L | Failed to get compliance result for rack server {0} with lowestRackunit {1} in {2}. | Critical |
| FQXHMUP3018L | Failed to get compliance result for rack server {0} with lowestRackunit {1} in {2}. | Critical |
| FQXHMUP3019L | Update packages were not found in the repository for rack server {0} with lowestRackunit {1} in {2} while computing compliance result. | Critical |
| FQXHMUP3021L | The specified policy name is invalid. | Critical |
| FQXHMUP3022L | An unknown error occurred while assigning policy. | Critical |
| FQXHMUP3023L | An unknown error occurred while unassigning policy. | Critical |
| FQXHMUP3033L | Some files are not valid. The files were not imported. | Critical |
| FQXHMUP3034L | The policy is currently assigned or predefined. | Critical |
| FQXHMUP4000L | The application failed to perform the specified request. | Critical |
| FQXHMUP4001L | The application could not perform the request. | Critical |
| FQXHMUP4002L | The application could not perform the cancel request. | Critical |
| FQXHMUP4010L | PerformAction was not started on the selected devices. | Critical |
| FQXHMUP4011L | The firmware updates process was not started on the selected devices for unknown error. | Critical |
| FQXHMUP4012L | The firmware updates process was not started on the selected devices because they have no associated update packages. | Critical |
| FQXHMUP4013L | The firmware updates process was not started on the selected devices because prerequisites are not met. | Critical |
| FQXHMUP4014L | The firmware updates process was not started on the selected devices because the job cannot be registered. | Critical |
| FQXHMUP4015L | The firmware updates process was not started on the selected devices because the job cannot be spawned. | Critical |
| FQXHMUP4016L | The firmware updates process was not started on the selected devices because one or more selected devices are already in use by one or more jobs. | Critical |
| FQXHMUP4017L | The firmware updates process was not started on the selected devices because there are no valid devices in the list. | Critical |
| FQXHMUP4018L | The firmware updates process was not started on the selected devices because the appliance sFTP server address cannot be retrieved. | Critical |
| FQXHMUP4019L | The firmware updates process was not started on the selected devices because the selected devices are a mix of Real and Demo data types. | Critical |
| FQXHMUP4020L | PerformAction (simulation mode) was not started on the selected devices. | Critical |
| FQXHMUP4021L | Firmware Updates (simulation mode) were not started on the selected devices for unknown error. | Critical |
| FQXHMUP4022L | The firmware updates process (simulation mode) were not started on the selected devices because they have no associated update packages. | Critical |
| FQXHMUP4023L | The firmware updates process (simulation mode) were not started on the selected devices because prerequisites are not met. | Critical |
| FQXHMUP4024L | The firmware updates process (simulation mode) was not started on the selected devices because the job cannot be registered. | Critical |
| FQXHMUP4025L | The firmware updates process (simulation mode) was not started on the selected devices because the job cannot be spawned. | Critical |
| FQXHMUP4026L | The firmware updates process (simulation mode) was not started on the selected devices because one or more selected devices are already in use by one or more jobs. | Critical |
| FQXHMUP4027L | The firmware updates process (simulation mode) was not started on the selected devices because there are no valid devices in the list. | Critical |
| FQXHMUP4028L | The firmware updates process (simulation mode) was not started on the selected devices because the appliance sFTP server address cannot be retrieved. | Critical |
| FQXHMUP4029L | The firmware updates process (simulation mode) was not started on the selected devices because the selected devices are a mix of Real and Demo data types. | Critical |
| FQXHMUP4031L | The Cancel process was not started on the selected devices. | Critical |
| FQXHMUP4032L | The Cancel process was not started on the selected devices. | Critical |
| FQXHMUP4041L | PerformAction {0} was not started on the selected devices. | Critical |
| FQXHMUP4042L | An error occurred trying to obtain inventory information for the specified device. | Critical |
| FQXHMUP4043L | No edge service information was found. | Critical |
| FQXHMUP4051L | An error occurred during the removal of the completed jobs. | Critical |
| FQXHMUP4060L | An error occurred while uploading the firmware update to the baseboard management controller. | Critical |
| FQXHMUP4061L | There is not enough free space on the RDOC in the baseboard management controller. | Critical |
| FQXHMUP4062L | An error occurred while connecting to remote disk on card of the baseboard management controller. | Critical |
| FQXHMUP4063L | The IPMI over KCS Access is disabled in the baseboard management controller. | Critical |
| FQXHMUP4064L | The target firmware version is lower than minimum recommended version. | Critical |
| FQXHMUP4065L | The BMC current firmware version is too low and does not support update. | Critical |
| FQXHMUP4066L | The verification task found that the specified package cannot be applied. | Critical |
| FQXHMUP4067L | The secure boot is enabled on this device. | Critical |
| FQXHMUP4087L | The {0} task was canceled because the verification task found an issue with the firmware update. | Critical |
| FQXHMUP4088L | An error occurred while preparing the package metadata file. | Critical |
| FQXHMUP4089L | An error occurred while preparing the package payload file. | Critical |
| FQXHMUP4091L | An error occurred while obtaining the Update Status. | Critical |
| FQXHMUP4093L | An error occurred while obtaining the Update engine settings. | Critical |
| FQXHMUP4094L | An error occurred while setting the Update engine settings. | Critical |
| FQXHMUP4111L | Apply Engine internal error. | Critical |
| FQXHMUP4151L | An error occurred while updating the firmware. | Critical |
| FQXHMUP4152L | An error occurred while updating firmware for the {0}. | Critical |
| FQXHMUP4161L | An error occurred while updating firmware for the {0}. | Critical |
| FQXHMUP4162L | An error occurred during the firmware update to the {0}. | Critical |
| FQXHMUP4165L | An error occurred while preparing the temporary work space for the firmware update. | Critical |
| FQXHMUP4168L | An error occurred while updating the firmware. | Critical |
| FQXHMUP4211L | An error occurred while performing the firmware update to the Chassis Management Module. | Critical |
| FQXHMUP4212L | A connection error to the CIMOM occurred while performing the firmware update on the Chassis Management Module. | Critical |
| FQXHMUP4213L | An error occurred while performing the firmware update on the Chassis Management Module. | Critical |
| FQXHMUP4214L | A CIMOM operation failed while performing the firmware update on the Chassis Management Module. | Critical |
| FQXHMUP4215L | An unknown error occurred while performing the firmware update on the Chassis Management Module. | Critical |
| FQXHMUP4216L | An authorization error occurred while performing the firmware update on the Chassis Management Module because the user name was not accepted. | Critical |
| FQXHMUP4217L | An authorization error occurred while performing the firmware update on the Chassis Management Module because the password was not accepted. | Critical |
| FQXHMUP4218L | An error occurred while performing the firmware update on the Chassis Management Module because the specified information was lost. | Critical |
| FQXHMUP4219L | An error occurred while performing the firmware update on the Chassis Management Module. | Critical |
| FQXHMUP4220L | Unable to install the package while performing the firmware update on the Chassis Management Module. | Critical |
| FQXHMUP4221L | The firmware update process has completed, the results could not be validated. | Critical |
| FQXHMUP4222L | An error occurred while performing the firmware update on the Chassis Management Module. | Critical |
| FQXHMUP4311L | The firmware update on the Flex System switch failed. | Critical |
| FQXHMUP4312L | A connection error occurred while performing the firmware update on the Flex System switch. | Critical |
| FQXHMUP4313L | An installation error occurred while performing the firmware update on the Flex System switch. | Critical |
| FQXHMUP4314L | An activation error occurred while performing the firmware update on the Flex System switch. | Critical |
| FQXHMUP4315L | A restart error occurred while performing the firmware update on the Flex System switch. | Critical |
| FQXHMUP4316L | An authorization error occurred while performing the firmware update on the Flex System switch because the user name was not accepted. | Critical |
| FQXHMUP4317L | An authorization error occurred while performing the firmware update to the Flex System switch because the password was not accepted. | Critical |
| FQXHMUP4318L | An unknown error occurred while performing the firmware update to the Flex System switch. | Critical |
| FQXHMUP4319L | An unknown error with URL occurred while performing the firmware update to the Flex System switch. | Critical |
| FQXHMUP4320L | A DCSS timeout error occurred while performing the firmware update to the Flex System switch. | Critical |
| FQXHMUP4321L | A DCSS error occurred while performing the firmware update on the Flex System switch. | Critical |
| FQXHMUP4322L | A fingerprint mismatched error occurred while performing the firmware update on the Flex System switch. | Critical |
| FQXHMUP4323L | The firmware download operation error while performing the firmware update on the Flex System switch. | Critical |
| FQXHMUP4324L | DCSS_RC_CDT_FAIL error occurred while performing the firmware update on the Flex System switch. | Critical |
| FQXHMUP4325L | The host key authentication failed while performing the firmware update on the Flex System switch. | Critical |
| FQXHMUP4326L | The host could not be contacted during the firmware update on the Flex System switch. | Critical |
| FQXHMUP4327L | A flash error occurred while performing the firmware update on the Flex System switch. | Critical |
| FQXHMUP4328L | A firmware update timeout occurred while performing the firmware update on the Flex System switch. | Critical |
| FQXHMUP4329L | The firmware update did not complete. | Critical |
| FQXHMUP4330L | Another firmware update is in progress. | Critical |
| FQXHMUP4331L | Access was denied by the Flex System switch. | Critical |
| FQXHMUP4332L | A prerequisite was not met for the Flex System switch update. | Critical |
| FQXHMUP4333L | An invalid namespace error occurred while performing the firmware update on the Flex System switch. | Critical |
| FQXHMUP4334L | An invalid parameter error occurred while performing the firmware update to the Flex System switch. | Critical |
| FQXHMUP4335L | A CIM connection error was detected while performing the firmware update on the Flex System switch. | Critical |
| FQXHMUP4336L | A prerequisite was not met for the Flex System switch update. | Critical |
| FQXHMUP4337L | A prerequisite was not met for the Flex System switch update. | Critical |
| FQXHMUP4338L | A CIM error was detected while performing the firmware update to the Flex System switch. | Critical |
| FQXHMUP4339L | An installation error occurred while performing the firmware update to the Flex System switch. | Critical |
| FQXHMUP4380L | The firmware update to the Flex System switch failed, indicating an error with the message "Firmware download operation failed". | Critical |
| FQXHMUP4381L | The firmware update to the Flex System switch failed, indicating an error with the message "DCSS_RC_CDT_FAIL." | Critical |
| FQXHMUP4382L | The firmware update to the Flex System switch failed, indicating an error with the message "time out." | Critical |
| FQXHMUP4383L | The firmware update to the Flex System switch failed, indicating an error with the message "Cannot download the same firmware version. Download another firmware." | Critical |
| FQXHMUP4384L | The firmware update to the Flex System switch failed, indicating an error with the message of failed to contact host. | Critical |
| FQXHMUP4385L | The firmware update to the Flex System switch failed, indicating an error with the message "file does not exist." | Critical |
| FQXHMUP4386L | Firmware update to the Flex System switch failed, indicating an error with the message of "flashing ended with failure." | Critical |
| FQXHMUP4387L | The firmware update to the Flex System switch failed, indicating an error with the message "Not enough disk space." | Critical |
| FQXHMUP4388L | The firmware update to Flex switch failed, indicating an error with the message "Firmware image fails data integrity". | Critical |
| FQXHMUP4389L | The firmware update to the Flex System switch failed, indicating an error with the message of "Host Key Authentication failed." | Critical |
| FQXHMUP4411L | An error occurred while performing the firmware update to the primary management controller. | Critical |
| FQXHMUP4412L | An error occurred while performing the firmware update to the backup management controller. | Critical |
| FQXHMUP4413L | An error occurred while restarting the primary management controller. | Critical |
| FQXHMUP4421L | An error occurred while performing the firmware update to the preboot Diagnostics. | Critical |
| FQXHMUP4431L | An error occurred while performing the firmware update to the Primary uEFI. | Critical |
| FQXHMUP4432L | An error occurred while performing the firmware update to the Backup uEFI. | Critical |
| FQXHMUP4433L | An error occurred while performing the firmware update to the PSU. | Critical |
| FQXHMUP4434L | An error occurred while performing the firmware update. There is an error with the update command line arguments. | Critical |
| FQXHMUP4435L | An error occurred while performing the firmware update with the specified firmware update package. | Critical |
| FQXHMUP4436L | An error occurred with the LAN-over-USB device while performing the firmware update. | Critical |
| FQXHMUP4437L | The LAN-over-USB driver is not installed on the device. | Critical |
| FQXHMUP4438L | The LAN-over-USB device number is unexpected. | Critical |
| FQXHMUP4439L | Failed to connect to the server. | Critical |
| FQXHMUP4440L | A configuration error was detected on the scalable complex while performing the firmware update. | Critical |
| FQXHMUP4441L | A connection error was detected while performing the firmware update. | Critical |
| FQXHMUP4442L | An authentication error was detected while performing the firmware update. | Critical |
| FQXHMUP4443L | A transaction error was detected while performing the firmware update. | Critical |
| FQXHMUP4444L | An unexpected connection error was detected while performing the firmware update. | Critical |
| FQXHMUP4445L | No IPMI driver was detected on the device. | Critical |
| FQXHMUP4446L | The validation phase of the firmware update process failed. | Critical |
| FQXHMUP4447L | There was an unexpected error during this operation. | Critical |
| FQXHMUP4448L | There is another update in progress on this device. | Critical |
| FQXHMUP4449L | A busy error was detected on the management controller during the firmware update. | Critical |
| FQXHMUP4450L | The UEFI update requires an operating system boot. | Critical |
| FQXHMUP4451L | Unable to determine the management-controller status while performing the firmware update. | Critical |
| FQXHMUP4452L | The management controller reported an abnormal status while performing the firmware update. | Critical |
| FQXHMUP4453L | The management controller reported an abnormal status while performing the firmware update. | Critical |
| FQXHMUP4454L | The firmware update was interrupted. | Critical |
| FQXHMUP4455L | The firmware update was interrupted. | Critical |
| FQXHMUP4456L | The firmware update was aborted. | Critical |
| FQXHMUP4457L | Unable to connect to the file server. | Critical |
| FQXHMUP4458L | A timeout error was encountered during the firmware update. | Critical |
| FQXHMUP4459L | Sufficient space is not available on the management controller for the firmware update. | Critical |
| FQXHMUP4460L | The target firmware-update package is not valid for this device. The firmware does not match this device. | Critical |
| FQXHMUP4461L | The target firmware-update package is not valid for this device. The security authentication failed. | Critical |
| FQXHMUP4462L | The target firmware-update package is corrupted. | Critical |
| FQXHMUP4463L | The connection was lost while performing the firmware update. | Critical |
| FQXHMUP4464L | An error occurred while performing the firmware update. The firmware transfer progress was interrupted. | Critical |
| FQXHMUP4465L | An error occurred while performing the firmware update. The management controller reported an abnormal status for the package upload. | Critical |
| FQXHMUP4466L | An error occurred while performing the firmware update. | Critical |
| FQXHMUP4467L | An error occurred while performing the firmware update. There is a package build/version mismatch. | Critical |
| FQXHMUP4468L | An error occurred while performing the firmware update. The firmware update cannot be applied because the firmware image is already in use. | Critical |
| FQXHMUP4469L | An error occurred while performing the firmware update. An SPI ROM access error was encountered during the update. | Critical |
| FQXHMUP4471L | An error occurred while performing the firmware update. The connection was lost during the update. | Critical |
| FQXHMUP4472L | An error occurred while performing the firmware update. The management controller did not report a change in the update progress. | Critical |
| FQXHMUP4473L | An error occurred while performing the firmware update. The management controller reported an abnormal status during the update. | Critical |
| FQXHMUP4474L | An error occurred while performing the firmware update. The firmware cannot be updated for an unknown reason. | Critical |
| FQXHMUP4475L | An error occurred while performing the firmware update. The updated firmware cannot be activated. | Critical |
| FQXHMUP4476L | An error occurred while performing the firmware update. The new version is mismatched. | Critical |
| FQXHMUP4477L | An error occurred while performing the firmware update. The management controller did not respond in the allocated time after a restart. | Critical |
| FQXHMUP4478L | An unknown error occurred while performing the firmware update. | Critical |
| FQXHMUP4511L | An unknown error occurred while attempting to start the device in maintenance mode. | Critical |
| FQXHMUP4512L | An error occurred while attempting to start the device in maintenance mode because the management controller does not support BMU. | Critical |
| FQXHMUP4513L | An error occurred while attempting to start the device in maintenance mode because the preboot Diagnostics does not support BMU. | Critical |
| FQXHMUP4514L | An error occurred while attempting to start the device in maintenance mode. The management controller did not respond to the CIM commands. | Critical |
| FQXHMUP4521L | An error occurred while attempting to complete close maintenance mode on the device. | Critical |
| FQXHMUP4522L | An unknown error occurred while attempting to complete close maintenance mode on the device. | Critical |
| FQXHMUP4531L | An unknown error occurred while attempting to restart the device. | Critical |
| FQXHMUP4532L | An error occurred while attempting to restart the device because the management controller does not support BMU updates. | Critical |
| FQXHMUP4533L | An error occurred while attempting to restart the device because the preboot Diagnostics does not support BMU updates. | Critical |
| FQXHMUP4534L | An error occurred while attempting to restart the device. The management controller did not respond to the CIM commands. | Critical |
| FQXHMUP4536L | An error occurred while attempting to restart the device. The Virtual Reseat was unsuccessful. | Critical |
| FQXHMUP4537L | An error occurred while attempting to restart the device. The device did not respond to the Agentless trigger. | Critical |
| FQXHMUP4538L | An error occurred while attempting to restart the device. The device failed to respond to the power control CIM calls. | Critical |
| FQXHMUP4541L | An unknown error occurred while attempting to perform the prerequisites on the device. | Critical |
| FQXHMUP4545L | The device is not ready for an update. | Critical |
| FQXHMUP4546L | The device did not meet the minimum version of UEFI firmware. | Critical |
| FQXHMUP4548L | Prerequisite firmware checks did not pass for this device. | Critical |
| FQXHMUP4564L | A CIM error occurred while performing the firmware update. | Critical |
| FQXHMUP4565L | A CIM command error occurred while performing the firmware update. | Critical |
| FQXHMUP4566L | A CIM execution error occurred while performing the firmware update. | Critical |
| FQXHMUP4567L | A download error occurred while performing the firmware update. | Critical |
| FQXHMUP4568L | A timeout error occurred while performing the firmware update. | Critical |
| FQXHMUP4569L | A management controller app connection error occurred while performing the firmware update. | Critical |
| FQXHMUP4570L | A management controller app parameter error occurred while performing the firmware update. | Critical |
| FQXHMUP4571L | An error occurred while performing the firmware update. The sensor, data, or record that was requested by the management controller is not present. | Critical |
| FQXHMUP4572L | A busy error occurred while performing the firmware update. | Critical |
| FQXHMUP4573L | An unknown error occurred while performing the firmware update. The management controller encountered an unknown error. | Critical |
| FQXHMUP4582L | An authentication error occurred while performing the firmware update. The remote device (management controller or CMM) cannot be authenticated. | Critical |
| FQXHMUP4583L | An authentication error occurred while performing the firmware update. The CIM authentication failed. | Critical |
| FQXHMUP4584L | A CIM instance error occurred while performing the firmware update. | Critical |
| FQXHMUP4585L | A CIM property error occurred while performing the firmware update. | Critical |
| FQXHMUP4586L | A CIM enumeration error occurred while performing the firmware update. | Critical |
| FQXHMUP4587L | A CIM provider error occurred while performing the firmware update. | Critical |
| FQXHMUP4588L | A CIM execution error occurred while performing the firmware update. | Critical |
| FQXHMUP4589L | A CIM logical error occurred while performing the firmware update. | Critical |
| FQXHMUP4590L | A CIM reboot failure occurred while performing the firmware update. | Critical |
| FQXHMUP4591L | A CIM connection timeout occurred while performing the firmware update. | Critical |
| FQXHMUP4592L | A CIM preconfiguration error occurred while performing the firmware update. The device is not available. | Critical |
| FQXHMUP4593L | A CIM preconfiguration error occurred while performing the firmware update. Unable to turn on the ESXi SSH. | Critical |
| FQXHMUP4594L | A CIM preconfiguration error occurred while performing the firmware update. SFCB Reboot cannot be disabled. | Critical |
| FQXHMUP4595L | A CIM flash error occurred while attempting to perform an update on the target system. | Critical |
| FQXHMUP4611L | An error occurred while attempting to prepare the device for firmware updates. The embedded Maintenance Mode image is not compatible with this product. | Critical |
| FQXHMUP4612L | An error occurred while attempting to prepare the device for firmware updates. The network connection cannot be established. | Critical |
| FQXHMUP4701L | An error occurred while preparing for the inband components. | Critical |
| FQXHMUP4702L | An error occurred while connecting to the device. | Critical |
| FQXHMUP4703L | An internal error occurred while performing firmware updates to the inband components. | Critical |
| FQXHMUP4704L | An unknown error occurred while performing firmware updates to the inband components. | Critical |
| FQXHMUP4705L | A firmware update timeout occurred while performing the firmware update. | Critical |
| FQXHMUP4706L | An undetected error occurred during the firmware update. | Critical |
| FQXHMUP4707L | An error occurred while closing the inband components session. | Critical |
| FQXHMUP4709L | An error occurred while performing firmware update to the {0} inband component. | Critical |
| FQXHMUP4712L | An error occurred performing the firmware update on the {0} inband component. | Critical |
| FQXHMUP4713L | An error occurred while performing firmware update to the {0} inband component. | Critical |
| FQXHMUP4714L | An internal error occurred while performing firmware updates to the inband components. | Critical |
| FQXHMUP4715L | An unclean maintenance-mode operation was found on this system. | Critical |
| FQXHMUP4801L | An error occurred performing the firmware update. LXCE indicated that the command line was not valid. | Critical |
| FQXHMUP4802L | An error occurred performing the firmware update. LXCE indicated a generic failure. | Critical |
| FQXHMUP4803L | An error occurred performing the firmware update. LXCE indicated a generic acquire failure. | Critical |
| FQXHMUP4804L | An error occurred performing the firmware update. LXCE indicated a generic scan failure. | Critical |
| FQXHMUP4805L | An error occurred performing the firmware update. LXCE indicated a generic query failure. | Critical |
| FQXHMUP4806L | An error occurred performing the firmware update. LXCE indicated a generic comparison failure. | Critical |
| FQXHMUP4807L | An error occurred performing the firmware update. LXCE indicated a generic update failure. | Critical |
| FQXHMUP4808L | An error occurred performing the firmware update. LXCE indicated that the ESXi host is unsupported. | Critical |
| FQXHMUP4809L | An error occurred trying to contact the IBM update repository. | Critical |
| FQXHMUP4810L | An error occurred trying to acquire the update package. LXCE indicated that there are no applicable updates available for the specified machine type or operating system. | Critical |
| FQXHMUP4811L | An error occurred trying to acquire the update package. LXCE indicated that the acquisition failed. | Critical |
| FQXHMUP4812L | An error occurred trying to acquire the update package. LXCE indicated that there was an error writing to the file or directory. | Critical |
| FQXHMUP4813L | An error occurred trying to acquire the update package. LXCE indicated that it was unable to get the machine type or operating system information. | Critical |
| FQXHMUP4814L | An error occurred trying to acquire or apply the update package. LXCE indicated that the pack meta data file is not valid or not found. | Critical |
| FQXHMUP4815L | An error occurred trying to query or compare the device. LXCE indicated that the machine type is not valid or unsupported. | Critical |
| FQXHMUP4816L | An error occurred trying to query or compare the device. LXCE indicated that the operating system is not valid or unsupported. | Critical |
| FQXHMUP4817L | An error occurred trying to apply the update package. LXCE indicated that no package was specified for the flash. | Critical |
| FQXHMUP4818L | An error occurred trying to apply the update package. LXCE indicated that it is unable to authenticate with the device. | Critical |
| FQXHMUP4819L | An error occurred trying to apply the update package. LXCE indicated that it is unable to connect to the device. | Critical |
| FQXHMUP4820L | An error occurred trying to apply the update package. LXCE indicated that the update timed out. | Critical |
| FQXHMUP4821L | An error occurred trying to apply the update package. LXCE indicated that there was a failure trying to connect to the TFTP/SFTP server to upload the payload. | Critical |
| FQXHMUP4822L | An error occurred trying to apply the update package. LXCE indicated that there was an authentication failure with the TFTP/SFTP server. | Critical |
| FQXHMUP4823L | An error occurred trying to apply the update package. LXCE indicated that the device had a connection failure with the TFTP/SFTP server. | Critical |
| FQXHMUP4824L | An error occurred trying to apply the update package. LXCE indicated that the device had an authentication failure with the TFTP/SFTP server. | Critical |
| FQXHMUP4825L | An error occurred trying to apply the update package. LXCE indicated that the update failed while attempting to send the file to the device. | Critical |
| FQXHMUP4826L | An error occurred trying to apply the update package. LXCE indicated that one or more payload files are not valid or not found. | Critical |
| FQXHMUP4827L | An error occurred trying to apply the update package. | Critical |
| FQXHMUP4828L | An error occurred trying to apply the update package. LXCE indicated that the device drivers that the package depends on are not present. | Critical |
| FQXHMUP4829L | An error occurred trying to apply the update package. LXCE indicated that the applicable hardware is not present in the system. | Critical |
| FQXHMUP4830L | An error occurred trying to apply the update package. LXCE indicated that the prerequisites are not met for this update. | Critical |
| FQXHMUP4831L | An error occurred trying to apply the update package. LXCE indicated that the update did not install successfully. | Critical |
| FQXHMUP4832L | An error occurred while applying the update package. The Flash pre-configuration failed. | Critical |
| FQXHMUP4833L | An error occurred while applying the update package. The process that is waiting for the firmware flash timed out before the update completed. | Critical |
| FQXHMUP4834L | An error occurred while applying the update package. The package metadata is either not valid or missing. | Critical |
| FQXHMUP4835L | An error occurred while applying the update package. The selected update package is not needed for a firmware flash. | Critical |
| FQXHMUP4836L | An error occurred while applying the update package. The local file and remote file do not match. | Critical |
| FQXHMUP4837L | An error occurred while applying the update package. The file upload to the SFTP server failed. | Critical |
| FQXHMUP4838L | An error occurred while applying the update package. Rollback to older versions is not allowed. | Critical |
| FQXHMUP4839L | An error occurred while applying the update package. LXCE indicated an issue to flash the update package. | Critical |
| FQXHMUP4840L | An error occurred while applying the update package. LXCE indicated an issue with support to backup firmware. | Critical |
| FQXHMUP4841L | Protocol Error | Critical |
| FQXHMUP4842L | Update Already in Progress | Critical |
| FQXHMUP4843L | Firmware Incompatibility Error | Critical |
| FQXHMUP4844L | Firmware Mismatch Error | Critical |
| FQXHMUP4845L | Insufficient Space | Critical |
| FQXHMUP4846L | Image Not Found | Critical |
| FQXHMUP4847L | Invalid Image | Critical |
| FQXHMUP4848L | Image Already Exists | Critical |
| FQXHMUP4849L | Invalid Build ID | Critical |
| FQXHMUP4850L | Build ID Mismatch | Critical |
| FQXHMUP4851L | Invalid URI | Critical |
| FQXHMUP4852L | Transfer Error | Critical |
| FQXHMUP4853L | Update Error | Critical |
| FQXHMUP4854L | Operation Not Supported | Critical |
| FQXHMUP4855L | Updates Disabled | Critical |
| FQXHMUP4856L | Operation Cancelled | Critical |
| FQXHMUP4857L | Data Transfer Timeout | Critical |
| FQXHMUP4858L | Flash Memory Access Error | Critical |
| FQXHMUP4859L | Flash Memory Size Error | Critical |
| FQXHMUP4860L | Connection Timeout | Critical |
| FQXHMUP4861L | Build Version Mismatch | Critical |
| FQXHMUP4862L | Memory Allocation Error | Critical |
| FQXHMUP4863L | Signature Verification Error | Critical |
| FQXHMUP4864L | MD5 Mismatch | Critical |
| FQXHMUP4865L | Client Timeout | Critical |
| FQXHMUP4866L | Opt Firmware Timeout | Critical |
| FQXHMUP4867L | Firmware Rollback Disabled | Critical |
| FQXHMUP4868L | Invalid Target Error | Critical |
| FQXHMUP4869L | Partial Failure | Critical |
| FQXHMUP4870L | EID Address Error | Critical |
| FQXHMUP4871L | Minimum Firmware Version Needed | Critical |
| FQXHMUP4872L | Unsupported Adapter | Critical |
| FQXHMUP4873L | PLDM Error | Critical |
| FQXHMUP4874L | Internal Error | Critical |
| FQXHMUP4900L | Unable to start new process for taskid {0} Perform{1}. | Critical |
| FQXHMUP4910L | The power action request failed. | Critical |
| FQXHMUP4934M | The task has failed. | Critical |
| FQXHMUP4949L | Restore memory test settings failed. | Critical |
| FQXHMUP5010L | The media operation request failed. | Critical |
| FQXHMUP5011L | Mount media was not started on the selected devices. | Critical |
| FQXHMUP5012L | Unmount media was not started on the selected devices. | Critical |
| FQXHMUP5013L | Boot media was not started on the selected devices. | Critical |
| FQXHMUP5014L | An unrecognized operation ({0}) was selected. | Critical |
| FQXHMUP5101L | Operating-system authentication was not started on the selected devices. | Critical |
| FQXHMUP5102L | Operating-system compliance validation was not started on the selected devices. | Critical |
| FQXHMUP5103L | OS device-driver updates were not started on the selected devices. | Critical |
| FQXHMUP5104L | A timeout error occurred while applying the device-driver update. | Critical |
| FQXHMUP5105L | Inventory information for the specified device cannot be obtained. | Critical |
| FQXHMUP5106L | The device-driver update process cannot be initialized. | Critical |
| FQXHMUP5107L | The device-driver update process cannot be initialized because the selected device failed to copy. | Critical |
| FQXHMUP5108L | Operating-system action was not started on the selected devices because the management server network address cannot be obtained. | Critical |
| FQXHMUP5109L | Operating-system action was not started on the selected devices because the job cannot be spawned. | Critical |
| FQXHMUP5110L | Operating-system action was not started on the selected devices because one or more selected devices are already in use by one or more jobs. | Critical |
| FQXHMUP5111L | The Windows Remote Management service cannot be used on the selected device. | Critical |
| FQXHMUP5112L | The target UpdateXpress System Pack {0} was not found in the windows drivers repository. | Critical |
| FQXHMUP5113L | The device-driver inventory cannot be collected on the selected device. | Critical |
| FQXHMUP5114L | The device-driver inventory cannot be compared against the UpdateXpress System Pack. | Critical |
| FQXHMUP5115L | The operating system is not reachable on the selected device because the operating system on the selected device is not running. | Critical |
| FQXHMUP5116L | The operating system is not reachable on the selected device because the hostname is not reachable from the management server. | Critical |
| FQXHMUP5117L | The operating system is not supported for operating system driver updates. | Critical |
| FQXHMUP5118L | The Windows Remote Management service for HTTPS connection cannot be used on the selected device. | Critical |
| FQXHMUP5119L | The device-driver action cannot be performed because the operating-system-deployment network interface is not configured. | Critical |
| FQXHMUP5120L | The target Windows OS updates were not found in the windows drivers repository: {0}. | Critical |
| FQXHMUP5205M | The device-driver task has failed. | Critical |
| FQXHMUP6102J | The request to update the application by user [arg1] failed with return code [arg2]. | Critical |
| FQXHMUP7501L | The update package does not contain any applicable machine types. | Critical |
| FQXHMUP7502L | Update package does not contain any applicable Machine Types Models. | Critical |
| FQXHMUP7521L | The verification task found that the switch does not have network connectivity. | Critical |
| FQXHMUP7522L | The verification task found that the update-package stack type does not match the switch configuration. | Critical |
| FQXHMUP7523L | The stacked switch is a member switch. The firmware update cannot be applied. | Critical |
| FQXHMUP7524L | The firmware is development signed and cannot be applied to production signed switch. | Critical |
| FQXHMUP7525L | Another update is in progress. | Critical |
| FQXHMUP7527L | The switch firmware version is too low and does not support update. | Critical |
| FQXHMUP7531L | Update to CNoS version 10.8.1 or higher is not supported when default credentials are used. | Critical |
| FQXHMUP7540L | The update package is not compatible with selected switch. | Critical |
| FQXHMUP7560L | No update jobs are found for selected switch. | Critical |
| FQXHMUP7561L | Unzipping payload did not produce expected files. | Critical |
| FQXHMUP7562L | Unable to get SFTP credentials. | Critical |
| FQXHMUP7563L | Transfer of the main image to switch failed. | Critical |
| FQXHMUP7564L | Transfer of the boot image to switch failed. | Critical |
| FQXHMUP7565L | Resetting the switch failed. | Critical |
| FQXHMUP7900L | The verification task found that the server does not have network connectivity. | Critical |
| FQXHMUP7925L | Another update is in progress. | Critical |
| FQXHMUP7940L | The update package is not compatible with selected server. | Critical |
| FQXHMUP7941L | The update package does not exist. | Critical |
| FQXHMUP7966L | No update job to cancel. | Critical |
| FQXHMUP7968L | The update job failed. | Critical |
| FQXHMUP8002L | The management-server update operation failed. | Critical |
| FQXHMUP8013L | The management-server update package cannot be applied. | Critical |
| FQXHMUP8016L | The update package cannot be downloaded or imported because the repository is full. | Critical |
| FQXHMUP8020L | The Repo package cannot be applied, because the used remote firmware repository is read only. | Critical |
Give documentation feedback