XClarity Administrator events organized by severity
The following table lists all XClarity Administrator events, organized by severity (Information, Warning, and Critical).
| Event Code | Message String | Severity |
|---|---|---|
| FQXHMCP1105I | Pattern {0} was deployed to {1}. | Informational |
| FQXHMCP1110I | Pattern {0} deployment started. | Informational |
| FQXHMCP1135I | Profile {0} redeployment has started. | Informational |
| FQXHMCP1145I | Profile {0} was redeployed to {1}. | Informational |
| FQXHMCP1165I | Profile {0} was unassigned from {1}. | Informational |
| FQXHMCP1205I | Failover from server {0} to standby server {1} has completed. | Informational |
| FQXHMCP1210I | {0} failover from server {1} to standby server {2} 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 {0} created pattern {1}. | Informational |
| FQXHMCP5110I | {0} deployed existing pattern {1}. | Informational |
| FQXHMCP5120I | User {0} edited pattern {1}. | Informational |
| FQXHMCP5130I | User {0} copied pattern {1}. | Informational |
| FQXHMCP5140I | User {0} renamed pattern {1}. | Informational |
| FQXHMCP5150I | User {0} deleted pattern {1}. | Informational |
| FQXHMCP5240I | User {0} renamed profile {1}. | Informational |
| FQXHMCP5250I | User {0} deleted profile {1}. | Informational |
| FQXHMCP5260I | User {0} deployed profile {1}. | Informational |
| FQXHMCP5300I | User {0} created address pool {1}. | Informational |
| FQXHMCP5320I | User {0} edited address pool {1}. | Informational |
| FQXHMCP5330I | User {0} copied address pool {1}. | Informational |
| FQXHMCP5340I | User {0} renamed address pool {1}. | Informational |
| FQXHMCP5350I | User {0} deleted address pool {1}. | Informational |
| FQXHMCP5400I | User {0} created standby pool {1}. | Informational |
| FQXHMCP5420I | User {0} edited standby pool {1}. | Informational |
| FQXHMCP5430I | User {0} copied standby pool {1}. | Informational |
| FQXHMCP5440I | User {0} renamed standby pool {1}. | Informational |
| FQXHMCP5450I | User {0} deleted standby pool {1}. | Informational |
| FQXHMCP5500I | User {0} created placeholder chassis {1}. | Informational |
| FQXHMCP5520I | User {0} edited placeholder chassis {1}. | Informational |
| FQXHMCP5530I | User {0} copied placeholder chassis {1}. | Informational |
| FQXHMCP5540I | User {0} renamed placeholder chassis {1}. | Informational |
| FQXHMCP5550I | User {0} deleted placeholder chassis {1}. | Informational |
| FQXHMCP5600I | User {0} created policy {1}. | Informational |
| FQXHMCP5620I | User {0} edited policy {1}. | Informational |
| FQXHMCP5630I | User {0} copied policy {1}. | Informational |
| FQXHMCP5640I | User {0} renamed policy {1}. | Informational |
| FQXHMCP5650I | User {0} deleted policy {1}. | Informational |
| FQXHMCP5700I | User {0} started failover monitoring for {1} using standby pool {2} and failover policy {3}. | Informational |
| FQXHMCP5710I | User {0} restarted failover monitoring for {1}. | Informational |
| FQXHMCP5720I | User {0} edited failover monitoring for {1}. | Informational |
| FQXHMCP5730I | User {0} performed a failover to standby server {1}. | Informational |
| FQXHMCP5750I | User {0} stopped failover monitoring for {1}. | Informational |
| FQXHMCP5760I | User {0} removed failover monitoring for {1}. | Informational |
| FQXHMCP5770I | User {0} started all failover monitoring. | Informational |
| FQXHMCP5780I | User {0} restarted all failover monitoring. | Informational |
| FQXHMCP5790I | User {0} stopped all failover monitoring. | Informational |
| FQXHMCR0002I | Job {0} 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 {0} at IP address {1}. | Informational |
| FQXHMCR0006I | The management server date and time were not successfully changed by user {0} at IP address {1}. | 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 {0} at IP address {1} mounted the sshfs mount point - {2}. | Informational |
| FQXHMCR0012I | User {0} at IP address {1} un-mounted the sshfs mount point - {2}. | Informational |
| FQXHMCR0013I | User {0} at IP address {1} import server {2} host key. | Informational |
| FQXHMCR0014I | User {0} at IP address {1} failed to mount sshfs mount point {2}. | Informational |
| FQXHMCR0015I | User {0} at IP address {1} failed to un-mount sshfs mount point {2}. | Informational |
| FQXHMCR0020I | User {0} at IP address {1} successfully enabled {2} service in the Lenovo XClarity Administrator. | Informational |
| FQXHMCR0021I | User {0} at IP address {1} successfully disabled {2} service in the Lenovo XClarity Administrator. | Informational |
| FQXHMCR0022I | User {0} at IP address {1} failed to enable {2} service in the Lenovo XClarity Administrator. | Informational |
| FQXHMCR0023I | User {0} at IP address {1} failed to disable {2} service in the Lenovo XClarity Administrator. | Informational |
| FQXHMCR0024I | The XClarity Administrator properties file contains invalid key values. | Informational |
| FQXHMCR0030I | User {0} successfully enable {1} service watchdog monitoring in the Lenovo XClarity Administrator. | Informational |
| FQXHMCR0031I | User {0} unsuccessfully enable {1} service watchdog monitoring in the Lenovo XClarity Administrator. | Informational |
| FQXHMCR0032I | User {0} successfully disable {1} service watchdog monitoring in the Lenovo XClarity Administrator. | Informational |
| FQXHMCR0033I | User {0} unsuccessfully disable {1} service watchdog monitoring in the Lenovo XClarity Administrator. | Informational |
| FQXHMCR0104I | Call home service connectivity has been restored | Informational |
| FQXHMDI0001I | User {0} unmanaged chassis with UUID {1} (IP: {2}). | Informational |
| FQXHMDI0002I | User {0} has managed chassis with UUID {1} (IP: {2}) | Informational |
| FQXHMDI0018I | User {0} started management of chassis with UUID {1} (IP: {2}) with managed authentication enabled and manually entered credentials. | Informational |
| FQXHMDI0019I | User {0} started unmanagement of chassis with UUID {1} (IP: {2}). | Informational |
| FQXHMDI0020I | The LDAP configuration data for chassis {1} failed to clean up after user {0} unmanaged it. | Informational |
| FQXHMDI0021I | User {0} requested forced management of the chassis with UUID {1} (IP: {2}), which is already managed by Lenovo XClarity Administrator. The chassis will be unmanaged with force and then managed again. | Informational |
| FQXHMDI0024I | Children of chassis {0} unmanaged endpoint with UUID {1} (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 {0} on endpoint with UUID {1} (IP: {2}). | Informational |
| FQXHMDI0027I | User {0} started management of chassis with UUID {1} (IP: {2}) and managed authentication enabled and stored credentials {3}. | Informational |
| FQXHMDI0028I | User {0} started management of chassis with UUID {1} (IP: {2}) with managed authentication disabled and stored credentials {3}. | Informational |
| FQXHMDI0033I | User {0} unmanaged switch {1}. | Informational |
| FQXHMDI0034I | User {0} has managed switch {1}. | Informational |
| FQXHMDI0035I | User {0} started unmanagement of switch {1}. | Informational |
| FQXHMDI0036I | User {0} started management of switch {1}. | Informational |
| FQXHMDI0037I | The duplicate IP address issue for IP address {0} has been resolved. | Informational |
| FQXHMDI0038I | The duplicate IP address issue for IP address {0} has been resolved. | Informational |
| FQXHMDI0040I | The management server detects no more conflicts in regard to the managed device and the network host IP address {0}. | Informational |
| FQXHMDI0041I | The request to set Single Sign On feature failed on server {0}. | Informational |
| FQXHMDI0050I | The health of the SSD {0} in bay {1} of the RAID configuration {2} is back to normal. | Informational |
| FQXHMDI0060I | Server {0} was changed from the untrusted to trusted state. | Informational |
| FQXHMDI0101I | User {0} unmanaged server with UUID {1} (IP: {2}). | Informational |
| FQXHMDI0102I | User {0} has managed server with UUID {1} (IP: {2}) | Informational |
| FQXHMDI0118I | User {0} started management of server with UUID {1} (IP: {2}) and managed authentication enabled. | Informational |
| FQXHMDI0119I | User {0} started unmanagement of server with UUID {1} (IP: {2}) | Informational |
| FQXHMDI0121I | User {0} requested forced management of the server with UUID {1} (IP: {2}), which is already managed by Lenovo XClarity Administrator. The server will be unmanaged with force and then managed again. | Informational |
| FQXHMDI0127I | The request by user {0} to manage device {1} resulted in no action, because IP address {2} is already used by the device with UUID {3}. | Informational |
| FQXHMDI0130I | User {0} started management of server with UUID {1} (IP: {2}) and managed authentication enabled and stored credentials {3}. | Informational |
| FQXHMDI0131I | User {0} started management of server with UUID {1} (IP: {2}) with managed authentication disabled and stored credentials {3}. | Informational |
| FQXHMDI0133I | The request by user {0} to manage device {1} (with IP address {2}) resulted in no action, because the device is already managed by this management server. | Informational |
| FQXHMDI0301I | User {0} unmanaged storage {1}. | Informational |
| FQXHMDI0302I | User {0} has managed storage {1}. | Informational |
| FQXHMDI0319I | User {0} started unmanagement of storage {1}. | Informational |
| FQXHMDI0501I | User {0} at IP address {1} enabled data collection service. | Informational |
| FQXHMDI0502I | User {0} at IP address {1} disabled data collection service. | Informational |
| FQXHMDI0600I | Job {0} has been updated. | Informational |
| FQXHMDM0001I | Inventory has changed {0}. | Informational |
| FQXHMDM0002I | Cabinet related has changed {0}. | Informational |
| FQXHMDM0003I | Connectivity to {0} {1} has been lost. UUID is {2}. | Informational |
| FQXHMDM0004I | Connectivity to endpoint {0} has been restored. Endpoint is {1}. | Informational |
| FQXHMDM0005I | The management NTP server or time zone information or both failed to push to device with UUID {0} (IP: {1}) | Informational |
| FQXHMDM0006I | The NTP settings could not be pushed to device with UUID {0} (IP: {1}) because the firmware is not compatible. | Informational |
| FQXHMDM0020I | User {0} from remote address {1} created resource group {2}. | Informational |
| FQXHMDM0021I | User {0} from remote address {1} successfully edit resource group {2}. | Informational |
| FQXHMDM0022I | User {0} from remote address {1} removed resource group {2}. | Informational |
| FQXHMDM0125I | User {0} requested a power action {1} - on device {2}. {3}. | Informational |
| FQXHMDM0126I | User {0} set boot order - {1} - on device {2}. {3}. | Informational |
| FQXHMDM0127I | User {0} requested a cryptography/NIST action {1} on device {2}. {3}. | Informational |
| FQXHMDM0128I | User {0} requested a power capping action {1} on device {2}. {3}. | Informational |
| FQXHMDM0129I | User {0} performed an inventory property change action on device {1}. {2}. | Informational |
| FQXHMDM0130I | User {0} requested a CMM failover operation on device {1}. | Informational |
| FQXHMDM0131I | A power action started by user {0} was sent successfully to device {1}. {2}. | Informational |
| FQXHMDM0132I | A boot order operation started by user {0} completed successfully on device {1}. {2}. | Informational |
| FQXHMDM0133I | A cryptography/NIST action initiated by user {0} completed successfully on device {1}. {2}. | Informational |
| FQXHMDM0134I | A power capping action initiated by user {0} completed successfully on device {1}. {2}. | Informational |
| FQXHMDM0135I | An inventory property change action started by user {0} completed successfully on device {1}. {2}. | Informational |
| FQXHMDM0136I | A CMM failover operation started by user {0} completed successfully on device {1}.. | Informational |
| FQXHMDM0137I | An LED operation that was started by user {0} completed successfully on device {1}.. | Informational |
| FQXHMDM0154I | The SSH console session was started by user {0} on switch {1}. | Informational |
| FQXHMDM0156I | The stored credentials for {0} were changed by {1} at {2}. | Informational |
| FQXHMDM0157I | The configuration data was updated successfully. | Informational |
| FQXHMDM0158I | The role groups allowed to access {0} were changed by {1} at {2}. | Informational |
| FQXHMDM0159I | The "public access" property for {0} was changed by {1} at {2}. | Informational |
| FQXHMDM0160I | The managed authentication enabled/disabled setting was changed for {0} by {1} at {2}. | Informational |
| FQXHMDM0161I | The security descriptor was changed for {0} by {1} at {2}. | Informational |
| FQXHMDM0162I | The configuration definitions was updated successfully. | Informational |
| FQXHMDM0163I | The connection between the management server and the management controller {0} is offline. Reason : {1}. | Informational |
| FQXHMDM0164I | The connection between the management server and the management controller {0} was restored. | Informational |
| FQXHMDM0165I | The device health state changed from {0} to {1}. | Informational |
| FQXHMDM0169I | The device health state changed from critical to normal. | Informational |
| FQXHMDM0170I | The device health state changed from warning to normal. | 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 {0}. | Informational |
| FQXHMEM0102I | The Audit log has reached 80% of the maximum size ({0} events). | Informational |
| FQXHMEM0103I | The Audit log has been cleared successfully by user {0} at IP address {1}. | Informational |
| FQXHMEM0104I | The Audit log maximum size has been changed from {0} to {1} by user {2} at IP address {3}. | Informational |
| FQXHMEM0201I | The event log has wrapped, because it has reached the maximum size limit of {0}. | Informational |
| FQXHMEM0202I | The event log has reached 80% of the maximum size ({0} events). | Informational |
| FQXHMEM0203I | The event log has been cleared by user {0} at IP address {1}. | Informational |
| FQXHMEM0204I | The event log maximum size has been changed from {0} to {1} by user {2} at IP address {3}. | Informational |
| FQXHMEM0205I | The events with type {0} from the event log have been cleared by user {1} at IP address {2}. | Informational |
| FQXHMEM0208I | An {0} exclusion filter with id {1} has been created by user {2} at IP address {3}. | Informational |
| FQXHMEM0209I | The {0} exclusion filter with id {1} has been modified by user {2} at IP address {3}. | Informational |
| FQXHMEM0210I | The {0} exclusion filter with id {1} has been deleted by user {2} at IP address {3}. | Informational |
| FQXHMEM0211I | Monitor {0} has been created by user {1} at IP address {2}. | Informational |
| FQXHMEM0212I | Monitor {0} has been modified by user {1} at IP address {2}. | Informational |
| FQXHMEM0213I | Monitor {0} has been deleted by user {1} at IP address {2}. | Informational |
| FQXHMEM0214I | Test event for monitor {0}. | Informational |
| FQXHMEM0316I | User {0} at IP Address {1} has successfully created a new predefined event filter called {2}. | Informational |
| FQXHMEM0317I | User {0} at IP Address {1} has successfully edit predefined event filter called {2}. | Informational |
| FQXHMEM0318I | User {0} at IP Address {1} has successfully deleted the predefined event filter called {2}. | Informational |
| FQXHMEM0319I | User {0} at IP Address {1} has modified the configuration of pusher called {2}. | Informational |
| FQXHMEM0320I | User {0} at IP Address {1} reset pusher called {2} to the default configuration. | Informational |
| FQXHMEM0321I | User {0} has made a new subscription on pusher {1}. | Informational |
| FQXHMEM0322I | User {0} has deleted a subscription on pusher {1}. | Informational |
| FQXHMEM0401I | Event forwarding monitor {0} failed to send notification to destination with error message: {1}. | 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 {0} IOS subscriber. | Informational |
| FQXHMEM0406I | Test event for the {0} Android subscriber. | Informational |
| FQXHMEM0407I | Test event for the {0} Websocket subscriber. | Informational |
| FQXHMEM0408I | An informational alert was asserted on device {0} with alert ID {1}. | Informational |
| FQXHMEM0411I | An informational alert was deasserted on device {0} with alert ID {1}. | Informational |
| FQXHMEM0412I | A warning alert was deasserted on device {0} with alert ID {1}. | Informational |
| FQXHMEM0413I | A critical alert was deasserted on device {0} with alert ID {1}. | Informational |
| FQXHMEM0414I | An unknown Informational event was generated on {0}. For more information, see the device documentation. | Informational |
| FQXHMEM0415I | An unknown Warning event was generated on {0}. For more information, see the device documentation. | Informational |
| FQXHMEM0416I | An unknown Critical event was generated on {0}. For more information, see the device documentation. | Informational |
| FQXHMJM0001I | Job {0} with id {1} was created. | Informational |
| FQXHMJM0002I | Job {0} was updated. | Informational |
| FQXHMJM0003I | Job {0} with id {1} was deleted. | Informational |
| FQXHMJM0004I | User {0} at IP address {1} created job schedule {2}. | Informational |
| FQXHMJM0006I | User {0} at IP address {1} updated job schedule {2}. | Informational |
| FQXHMJM0008I | User {0} at IP address {1} set the state to {2} for job schedule {3}. | Informational |
| FQXHMJM0010I | User {0} at IP address {1} called Run Now procedure for job schedule {2}. | Informational |
| FQXHMJM0012I | User {0} at IP address {1} cloned the job schedule {2}. | Informational |
| FQXHMJM0014I | User {0} at IP address {1} removed the following job schedule configurations: {2}. | Informational |
| FQXHMJM0016I | The management server launched the job(s) {0} for job scheduler {1} successfully. | Informational |
| FQXHMJM0018I | User {0} at IP address {1} successfully postponed job {2}. | Informational |
| FQXHMJM0026I | User {0} successfully deleted the following job: {1}. | Informational |
| FQXHMJM0027I | User {0} successfully deleted the following jobs: {1}. | Informational |
| FQXHMJM0028I | User {0} failed to delete the following job: {1}. | Informational |
| FQXHMJM0029I | User {0} failed to delete the following jobs: {1}. | Informational |
| FQXHMMF0003I | Metrics data collection for all DM Storage managed with ID {0} has finished. | Informational |
| FQXHMNM0125I | Management Server started by {0}. | Informational |
| FQXHMNM0126I | Management Server is shutdown by user {0} at IP address {1}. | Informational |
| FQXHMNM0127I | Management Server is put into single-user mode by user {0} at IP address {1}. | Informational |
| FQXHMNM0128I | Management Server is restarted by user {0} at IP address {1}. | Informational |
| FQXHMNM0129I | Management Server is put into unsupported state by user {0} at IP address {1}. | Informational |
| FQXHMSC0001I | User {0} updated L2 interfaces {1} with success. | Informational |
| FQXHMSC0101I | User {0} deployed Global Configuration with success. | Informational |
| FQXHMSC0201I | User {0} deployed PortChannel Advanced Configuration with success. | Informational |
| FQXHMSC0301I | User {0} deployed PortChannel Basic Configuration with success. | Informational |
| FQXHMSC0401I | User {0} deleted portchannels {1} with success. | Informational |
| FQXHMSC0501I | User {0} deployed successfully the Spine Leaf Template. | Informational |
| FQXHMSC0502I | User {0} deployed successfully the Spine Node Template. | Informational |
| FQXHMSC0601I | User {0} deployed successfully the VLAG Advanced Configuration Template. | Informational |
| FQXHMSC0701I | User {0} deployed successfully the VLAG Instance Configuration Template. | Informational |
| FQXHMSC0801I | User {0} deployed successfully the VLAG Instance Delete Template. | Informational |
| FQXHMSC0901I | User {0} deployed successfully the VLAG Peers Configuration Template. | Informational |
| FQXHMSC1001I | User {0} added successfully the interfaces {1} in vlans {2}. | Informational |
| FQXHMSC1101I | User {0} deleted VLANs {1} with success. | Informational |
| FQXHMSC1201I | User {0} deployed successfully the VLAN Properties Template. | Informational |
| FQXHMSC1301I | User {0} removed interfaces {1} from VLANs {2} with success. | Informational |
| FQXHMSE0008I | Security policy level on {0} matches security policy level {1} on the management server. | Informational |
| FQXHMSE0009I | Minimum SSL/TLS protocol level on {0} matches minimum SSL/TLS protocol levels client {1} and server {2} on the management server. | Informational |
| FQXHMSE0010I | Cryptographic mode on {0} matches cryptographic mode {1} on the management server. | Informational |
| FQXHMSE0105I | Server certificate replaced by user ID {0} at IP address {1}. | Informational |
| FQXHMSE0106I | A new server certificate was generated by user ID {0} at IP address {1}. | Informational |
| FQXHMSE0112I | Trust certificate for chassis {0} installed by user ID {1} at IP address {2}. | Informational |
| FQXHMSE0130I | A new CA root certificate was generated by user ID {0} at IP address {1}. | Informational |
| FQXHMSE0131I | A new server certificate was uploaded by user ID {0} at IP address {1}. | Informational |
| FQXHMSE0143I | A new server certificate was uploaded to the temporary key store by user ID {0} at IP address {1}. | Informational |
| FQXHMSE0144I | A new server certificate was installed from the temporary key store by user ID {0} at IP address {1}. | Informational |
| FQXHMSE0200I | The login was successful for user ID {0} at IP address {1}. | Informational |
| FQXHMSE0201I | The logout was successful for user ID {0} at IP address {1}. | Informational |
| FQXHMSE0202I | The login was unsuccessful for user ID {0} at IP address {1}. | Informational |
| FQXHMSE0203I | Account {0} was created by user ID {1} at IP address {2}. | Informational |
| FQXHMSE0204I | Account {0} was changed by user ID {1} at IP address {2}. | Informational |
| FQXHMSE0205I | The password was changed by user ID {0} at IP address {1} for user ID {2}. | Informational |
| FQXHMSE0206I | Account {0} was deleted by user ID {1} at IP address {2}. | Informational |
| FQXHMSE0207I | The values of the following system properties have changed. {0}. | Informational |
| FQXHMSE0208I | The session {0} was terminated for user ID {1} at IP address {2} by {3} at IP address {4}. | Informational |
| FQXHMSE0209I | Account {0} is temporarily locked. | Informational |
| FQXHMSE0300I | Security policy level was changed by user ID {0} at IP address {1} to {2}. | Informational |
| FQXHMSE0303I | Minimum password length was changed to {0} by user ID {1} at IP address {2}. | Informational |
| FQXHMSE0304I | Maximum password length was changed to {0} by user ID {1} at IP address {2}. | Informational |
| FQXHMSE0305I | The minimum password reuse cycle setting was changed to {0} by user ID {1} at IP address {2}. | Informational |
| FQXHMSE0306I | The password expiration period setting was changed to {0} days by user ID {1} at IP address {2}. | Informational |
| FQXHMSE0307I | The inactivity alert period setting was changed to {0} minutes by user ID {1} at IP address {2}. | Informational |
| FQXHMSE0308I | The minimum password change interval setting changed to {0} hours by user ID {1} at IP address {2}. | Informational |
| FQXHMSE0309I | The maximum number of login failures setting changed to {0} by user ID {1} at IP address {2}. | Informational |
| FQXHMSE0310I | The lockout period after maximum login failures setting changed to {0} minutes by user ID {1} at IP address {2}. | Informational |
| FQXHMSE0311I | The simple password rules setting was changed to {0} by user ID {1} at IP address {2}. | Informational |
| FQXHMSE0312I | The minimum different characters in passwords setting changed to {0} by user ID {1} at IP address {2}. | Informational |
| FQXHMSE0313I | The force user to change password on first login setting changed to {0} by user ID {1} at IP address {2}. | Informational |
| FQXHMSE0314I | The password expiration warning period setting changed to {0} by user ID {1} at IP address {2}. | Informational |
| FQXHMSE0332I | The maximum concurrent sessions setting changed to {0} by user ID {1} at IP address {2}. | Informational |
| FQXHMSE0400I | A node account created for user ID {0} by user ID {1} at IP address {2}. | Informational |
| FQXHMSE0401I | A node account for user ID {0} changed by user ID {1} at IP address {2}. | Informational |
| FQXHMSE0402I | A node account for user ID {0} deleted by user ID {1} at IP address {2}. | Informational |
| FQXHMSE0403I | Centralized node account management was enabled for chassis {0} by user ID {1} at IP address {2}. | Informational |
| FQXHMSE0404I | Node account management responsibility was transferred to chassis {0}. | Informational |
| FQXHMSE0405I | A node account for user ID {0} was activated on chassis {1} by user ID {2} at IP address {3}. | Informational |
| FQXHMSE0406I | A node account for user ID {0} was deactivated on chassis {1} by user ID {2} at IP address {3}. | Informational |
| FQXHMSE0503I | The minimum TLS protocol level settings for {0} were changed to client={1}, server={2}, OS deploy={3} by user ID {4} at IP address {5}. | Informational |
| FQXHMSE0504I | The cryptographic mode for {0} was changed to {1} by user ID {2} at IP address {3}. | Informational |
| FQXHMSE0620I | The LDAP server selection method setting changed to {0} by user ID {1} at IP address {2}. | Informational |
| FQXHMSE0621I | A preconfigured LDAP server, {0}, was added by user ID {1} at IP address {2}. | Informational |
| FQXHMSE0622I | The LDAP root distinguished name setting was changed to {0} by user ID {1} at IP address {2}. | Informational |
| FQXHMSE0623I | The Active Directory forest name setting was changed to {0} by user ID {1} at IP address {2}. | Informational |
| FQXHMSE0624I | The LDAP domain name setting was changed to {0} by user ID {1} at IP address {2}. | Informational |
| FQXHMSE0625I | The LDAP client distinguished name setting was changed to {0} by user ID {1} at IP address {2}. | Informational |
| FQXHMSE0626I | The LDAP client password setting was changed by user ID {0} at IP address {1}. | Informational |
| FQXHMSE0627I | The LDAP SSL setting was changed to {0} by user ID {1} at IP address {2}. | Informational |
| FQXHMSE0628I | The LDAP trusted certificate {0} was replaced by user ID {1} at IP address {2}. | Informational |
| FQXHMSE0629I | The LDAP trusted certificate {0} was deleted by user ID {1} at IP address {2}. | Informational |
| FQXHMSE0630I | The LDAP user authentication method setting changed to {0} by user ID {1} at IP address {2}. | Informational |
| FQXHMSE0631I | The LDAP user authentication method was set to {0} after a change attempted by user ID {1} at IP address {2} failed. | Informational |
| FQXHMSE0632I | The LDAP binding method setting changed to {0} by user ID {1} at IP address {2}. | Informational |
| FQXHMSE0633I | The LDAP User Search Attribute setting was changed to {0} by user ID {1} at IP address {2}. | Informational |
| FQXHMSE0634I | The LDAP Group Search Attribute setting was changed to {0} by user ID {1} at IP address {2}. | Informational |
| FQXHMSE0635I | The LDAP setting to use servers as Global Catalogs was changed to {0} by user ID {1} at IP address {2}. | Informational |
| FQXHMSE0636I | The LDAP Group Name Attribute setting was changed to {0} by user ID {1} at IP address {2}. | Informational |
| FQXHMSE0700I | Authorization group {0} was created by user ID {1} at IP address {2}. | Informational |
| FQXHMSE0701I | Authorization group {0} was changed by user ID {1} at IP address {2}. | Informational |
| FQXHMSE0702I | Authorization group {0} was deleted by user ID {1} at IP address {2}. | Informational |
| FQXHMSE0750I | The resource access control has been {0} by user ID {1} at the following IP address {2}. | Informational |
| FQXHMSE0751I | Access to resource {0} was granted by user ID {1} at IP address {2} for the following role groups: {3}. | Informational |
| FQXHMSE0752I | Access to resource {0} was modified by user ID {1} at IP address {2}. | Informational |
| FQXHMSE0753I | Access to resource {0} was removed by user ID {1} at IP address {2}. | Informational |
| FQXHMSE0796I | Resource Access Control was disabled by user {0} at IP address {1}. | Informational |
| FQXHMSE0797I | Resource Access Control was enabled by user {0} at IP address {1}. | Informational |
| FQXHMSE0798I | The following role groups were added to the list of default Resource Access Control role groups by user {0} at IP address {1}: {2}. | Informational |
| FQXHMSE0799I | The following role groups were removed from the list of default Resource Access Control role groups by user {0} at IP address {1}: {2}. | Informational |
| FQXHMSE0800I | Service provider metadata has been regenerated by {0}. | Informational |
| FQXHMSE0801I | Identity provider metadata has been regenerated by {0}. | Informational |
| FQXHMSE0802I | SAML single sign on has been disabled by {0}. | Informational |
| FQXHMSE0803I | SAML single sign on has been enabled by {0}. | Informational |
| FQXHMSE0910I | Stored credentials with ID {0} and the following user name and description were added by user {1} at IP address {2}: {3} - {4}. | Informational |
| FQXHMSE0911I | Stored credentials with ID {0} and the following user name and description were removed by user {1} at IP address {2}: {3} - {4}. | Informational |
| FQXHMSE0912I | The user name of the stored credentials with ID {0} was changed to the following by user {1} at IP address {2}: {3} - {4}. | Informational |
| FQXHMSE0913I | The description of the stored credentials with ID {0} was changed to the following by user {1} at IP address {2}: {3} - {4}. | Informational |
| FQXHMSE0914I | The password of the stored credentials with ID {0} and the following user name and description was changed by user {1} at IP address {2}: {3} - {4}. | Informational |
| FQXHMSE0915I | Head of Stack feature not supported for firmware {0}. | Informational |
| FQXHMSE0916I | Head of Stack feature supported for firmware {0}. | Informational |
| FQXHMSE0917I | {0} enabled encapsulation for all future managed devices. | Informational |
| FQXHMSE0918I | {0} disabled encapsulation for all future managed devices. | Informational |
| FQXHMSE0919I | Custom role {0} was created by user {1} at IP address {2}. | Informational |
| FQXHMSE0920I | Custom role {0} was modified by user {1} at IP address {2}. | Informational |
| FQXHMSE0921I | Custom role {0} was deleted by user {1} at IP address {2}. | Informational |
| FQXHMSE0929I | The SSO login was successful for server {0}. | Informational |
| FQXHMSE0930I | The SSO login failed for server {0}. | Informational |
| FQXHMSE0931I | Functions enabled after system became compliant. | Informational |
| FQXHMSE0932I | New license was added to the system by {0}. | Informational |
| FQXHMSE0933I | License was removed from system by {0}. | Informational |
| FQXHMSE0934I | Single Sign On for servers was enabled by {0}. | Informational |
| FQXHMSE0935I | Single Sign On for servers was disabled by {0}. | Informational |
| FQXHMSE0936I | A new CyberArk certificate was generated by user ID {0} at IP address {1}. | Informational |
| FQXHMSE0937I | A new Single Sign On certificate was generated by user ID {0} at IP address {1}. | Informational |
| FQXHMSP00001I | The job {0} that was requested by user {1} to retrieve the chassis switch ports on device {2} was successful.{3}. | Informational |
| FQXHMSS0001I | All Service Data files have been downloaded by user {0} at IP address {1}. | Informational |
| FQXHMSS0003I | Service Data file {0} was downloaded by user {1} at IP address {2}. | Informational |
| FQXHMSS1001I | The log level of logger {0} has been changed from {1} to {2} by user {3} at IP address {4}. | Informational |
| FQXHMSS1003I | The log size of logger {0} has been changed from {1} to {2} by user {3} at IP address {4}. | Informational |
| FQXHMSS1005I | The number of Service Data files to keep has been changed by user {0}, at IP address {1}, from {2} to {3}. | Informational |
| FQXHMSS1007I | The request from user {0}, at IP address {1}, to change the suppression time from {2} to {3} was successful. | Informational |
| FQXHMSS1009I | The number of informational Service Data files to keep has been changed by user {0}, at IP address {1}, from {2} to {3}. | Informational |
| FQXHMSS1011I | A Service Data file with the type {0} and dump configuration ID {1} was collected on the server. | Informational |
| FQXHMSS1012I | A Service Data file with the type {0} and a custom configuration was collected on the server. | Informational |
| FQXHMSS1014I | The dumped archives have been cleared from the server by user {0} at IP address {1}. | Informational |
| FQXHMSS1016I | The request from user {0} at IP address {1} to change the number of logs archives for appender {2} to {3} was successful. | Informational |
| FQXHMSS1018I | The request from user {0} at IP address {1} to restore the log settings to the default values was successful. | Informational |
| FQXHMSS1020I | The generation of Service Data archive for user {0} at IP address {1} finished successfully. | Informational |
| FQXHMSS1022I | User {0} at IP address {1} initiated the generation of a Service Data file. | Informational |
| FQXHMSS1028I | The request by user {0} at IP address {1} to upload a file was successful. | Informational |
| FQXHMSS1029I | The request by user {0} at IP address {1} to change the Call Home configuration was successful. | Informational |
| FQXHMSS1031I | User {0} at IP address {1} enabled Call Home. | Informational |
| FQXHMSS1033I | User {0} at IP address {1} disabled Call Home. | Informational |
| FQXHMSS1035I | User {0} at IP address {1} reset the Call Home configuration. | Informational |
| FQXHMSS1045I | This is a eCC Test Call. | Informational |
| FQXHMSS1048I | The request by user {0} at IP address {1} to save the contact information for Call Home on endpoint with UUID {2} was successful. | Informational |
| FQXHMSS1049I | The request by user {0} at IP address {1} to update the contact information for Call Home on endpoint with UUID {2} was successful. | Informational |
| FQXHMSS1050I | The request by user {0} at IP address {1} to clear the contact information for Call Home on endpoint with UUID {2} was successful. | Informational |
| FQXHMSS1051I | User {0} at IP address {1} enabled the tracing mechanism. | Informational |
| FQXHMSS1052I | User {0} at IP address {1} disabled the tracing mechanism. | Informational |
| FQXHMSS1053I | User {0} at IP address {1} enabled the auto dumping mechanism. | Informational |
| FQXHMSS1054I | User {0} at IP address {1} disabled the auto dumping mechanism. | Informational |
| FQXHMSS2001I | Event {0} generated on {1} has been added to the Service Data collecting process. | Informational |
| FQXHMSS2005I | The Service Data archive for event {0} from {1} has been collected successfully. | Informational |
| FQXHMSS2006I | Call Home Service Forwarder {0} started creating the Ticket for event {1} generated on {2}. | Informational |
| FQXHMSS2007I | Call Home Service Forwarder {0} created Ticket {1} for event {2} generated on {3}. | Informational |
| FQXHMSS2009I | Call Home Service Forwarder {0} started uploading the collected Service Data to Ticket {1}. | Informational |
| FQXHMSS2010I | Call Home Service Forwarder {0} uploaded the Service Data to Ticket {1} successfully. | Informational |
| FQXHMSS2012I | SFTP Service Forwarder {0} started uploading the collected Service Data to {1}:{2}. | Informational |
| FQXHMSS2013I | SFTP Service Forwarder {0} uploaded the collected Service Data to {1}:{2} successfully. | Informational |
| FQXHMSS2016I | Service Forwarder {0} has been created by user {1} at IP address {2}. | Informational |
| FQXHMSS2017I | Service Forwarder {0} has been modified by user {1} at IP address {2}. | Informational |
| FQXHMSS2018I | Service Forwarder {0} has been deleted by user {1} at IP address {2}. | Informational |
| FQXHMSS2019I | The management server started collecting the Service Data archive for event {0} generated on {1}. | Informational |
| FQXHMSS2020I | Service Forwarder {0} has added the collected Service Data archive for event {1} generated on {2} in the pending queue. | Informational |
| FQXHMSS2021I | User {0} at IP address {1} has accepted the Service Data archive for event {2} generated on {3} for being processed by the active service forwarders. | Informational |
| FQXHMSS2022I | User {0} at IP address {1} has declined the Service Data archive for event {2} generated on {3} from being processed by the active service forwarders. | Informational |
| FQXHMSS2026I | User {0} at IP address {1} has successfully uploaded file {2} to Service Ticket {3}. | Informational |
| FQXHMSS2028I | The management server will skip creating a Ticket for event {0} generated on {1}. | Informational |
| FQXHMSS2035I | User {0} at IP Address {1} started the Call Home connectivity test. | Informational |
| FQXHMSS2036I | The Call Home connectivity test started by user {0} at IP Address {1} ended successfully. | Informational |
| FQXHMSS2038I | Lenovo Upload Facility Service Forwarder {0} started uploading the collected Service Data to {1}. | Informational |
| FQXHMSS2039I | Lenovo Upload Facility Service Forwarder {0} uploaded the collected Service Data to {1}. | Informational |
| FQXHMSS2043I | The request by user {0} at IP address {1} to save the Lenovo Upload Facility configuration was successful. | Informational |
| FQXHMSS2044I | The request by user {0} at IP address {1} to change the Lenovo Upload Facility configuration was successful. | Informational |
| FQXHMSS2046I | User {0} at IP address {1} reset the Lenovo Upload Facility configuration. | Informational |
| FQXHMSS3035I | User {0} at IP Address {1} started the Lenovo Call Home connectivity test. | Informational |
| FQXHMSS3036I | The Lenovo Call Home connectivity test started by user {0} at IP Address {1} ended successfully. | Informational |
| FQXHMSS3039I | User {0} at IP Address {1} started a Manual Software Lenovo Call Home. | Informational |
| FQXHMSS3045I | A Lenovo Software Call Home Test has successfully completed. The case number is {0}. | Informational |
| FQXHMSS3046I | A Lenovo Software Call Home has successfully completed. The case number is {0}. | Informational |
| FQXHMSS3047I | A Lenovo Manual Call Home has successfully completed. The case number is {0}. | Informational |
| FQXHMSS3048I | A Lenovo Call Home Test has successfully completed. The case number is {0}. | Informational |
| FQXHMSS3049I | A Lenovo Call Home has successfully completed. The case number is {0}. | Informational |
| FQXHMSS3050I | User {0} at IP Address {1} started a Manual Lenovo Call Home. | Informational |
| FQXHMSS3051I | User {0} at IP Address {1} started a Lenovo Call Home Test. | Informational |
| FQXHMSS3052I | User {0} at IP Address {1} started a Manual Software Lenovo Call Home Test. | Informational |
| FQXHMSS3053I | User {0} at IP address {1} has successfully uploaded file {2} to Lenovo Case {3}. | Informational |
| FQXHMSS3054I | The Lenovo Software Call Home Test has started uploading Service Data to case {0}. | Informational |
| FQXHMSS3055I | The Lenovo Software Call Home Test has successfully uploaded Service Data to case {0}. | Informational |
| FQXHMSS3058I | The Lenovo Software Call Home has started uploading Service Data to case {0}. | Informational |
| FQXHMSS3059I | The Lenovo Software Call Home has successfully uploaded Service Data to case {0}. | Informational |
| FQXHMSS3062I | The Lenovo Call Home Test has started uploading Service Data to case {0}. | Informational |
| FQXHMSS3063I | The Lenovo Call Home Test has successfully uploaded Service Data to case {0}. | Informational |
| FQXHMSS3066I | The Lenovo Call Home has started uploading Service Data to case {0}. | Informational |
| FQXHMSS3067I | The Lenovo Call Home has successfully uploaded Service Data to case {0}. | Informational |
| FQXHMSS3070I | User {0} at IP Address {1} started a Lenovo Call Home Pass Through. | Informational |
| FQXHMSS3071I | User {0} at IP Address {1} started a Lenovo Call Home Pass Through Test. | Informational |
| FQXHMSS3074I | A Lenovo Call Home Pass Through Test has successfully completed. The case number is {0}. | Informational |
| FQXHMSS3075I | A Lenovo Call Home Pass Through has successfully completed. The case number is {0}. | Informational |
| FQXHMSS3076I | Management Server will execute Call Home for the serviceable event {0} for device {1}. | Informational |
| FQXHMSS3077I | Management Server will not execute Call Home for the serviceable event {0} for device {1} because there is no forwarder to match device. | Informational |
| FQXHMSS3078I | Management Server will not execute Call Home for the serviceable event {0} for device {1} because there is already a ticket opened for this event and device. | Informational |
| FQXHMSS4001I | Internal service {0} terminated unexpectedly, and it has been restarted. Debug data on the termination has been collected and stored at {1}. | Informational |
| FQXHMSS4011I | Internal service {0} 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 {0}. | Informational |
| FQXHMSS4017I | An IBM Call Home Test has successfully completed. The problem record number is {0}. | Informational |
| FQXHMSS4018I | A Call Home has successfully completed. The ticket number is {0}. | Informational |
| FQXHMSS4019I | An IBM Call Home Connection Test has successfully completed. The problem record number is {0}. | Informational |
| FQXHMSS5048I | User {0} at IP address {1} 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 {0} at IP address {1} ended successfully. | Informational |
| FQXHMSS5054I | User {0} at IP address {1} has successfully deleted problem record {2}. | Informational |
| FQXHMSS5055I | User {0} at IP address {1} has successfully deleted all the problem records. | Informational |
| FQXHMSS5056I | User {0} at IP address {1} has successfully changed the state of the auto dumping mechanism from {2} to {3}. | Informational |
| FQXHMSS5057I | User {0} at IP address {1} has successfully changed the state of the file tracing mechanism from {2} to {3}. | Informational |
| FQXHMSS5058I | User {0} at IP address {1} has successfully changed the Call Home number of retries from {2} to {3}. | Informational |
| FQXHMSS5059I | User {0} at IP address {1} has successfully changed the Call Home timeout between retries from {2} to {3}. | Informational |
| FQXHMSS5060I | User {0} at IP address {1} has successfully changed the Call Home file verification mode from {2} to {3}. | Informational |
| FQXHMSS5061I | Call Home event with ID {0} from component {1} has been added to the Call Home Processing queue. | Informational |
| FQXHMSS5063I | Call Home event with ID {0} from component {1} is being processed by the server Call Home task. | Informational |
| FQXHMSS5065I | Call Home event with ID {0} from component {1} was suppressed. Call Home aborted. | Informational |
| FQXHMSS5069I | Call Home event with ID {0} from component {1} has successfully been called home. The associated ticket number is {2}. | Informational |
| FQXHMSS5071I | Call Home event with ID {0} from component {1} will not be called home because the server Call Home function is disabled. | Informational |
| FQXHMSS5073I | Call Home event with ID {0} from component {1} will be removed from the Call Home queue because the Call Home function is disabled now. | Informational |
| FQXHMSS5081I | Call Home event with ID {0} from component {1} is being processed by the server Call Home task. The process is attaching the collected endpoint service data to ticket number {2}. | Informational |
| FQXHMSS5083I | Call Home event with ID {0} from component {1} is being processed by the server Call Home task. The process is attaching additional files to problem number {2}. | Informational |
| FQXHMSS5085I | The collected endpoint service data has been successfully attached to ticket number {0}. | Informational |
| FQXHMSS5086I | The additional file(s) have been successfully attached to ticket number {0}. | Informational |
| FQXHMSS5089I | Call Home test generated by user {0} at IP address {1} was launched successfully. | Informational |
| FQXHMSS5090I | User {0} at IP address {1} enabled Call Home. | Informational |
| FQXHMSS5091I | User {0} at IP address {1} disabled Call Home. | Informational |
| FQXHMSS5092I | The server suppressed Call Home call for event {0} generated on system {1}. | Informational |
| FQXHMSS5093I | Collecting the Service Data archive generated by event with ID {0} from endpoint {1} finished successfully. | Informational |
| FQXHMSS5098I | Call Home eCC Call. | Informational |
| FQXHMSS5099I | Call Home eCC Test Call. | Informational |
| FQXHMSS5100I | Events with event code {0} generated from system {1} will be suppressed from Service Data data auto-collect and Service Forwarding processing for {2} hours. | Informational |
| FQXHMSS5101I | Event {0} received from system {1} was not called home. | Informational |
| FQXHMSS5103I | Test Event for Service Fowarder {0} generated by user {1} at ip address {2}. | Informational |
| FQXHMSS5104I | The warranty for {0} with the UUID {1} will expire in less than {2} days. | Informational |
| FQXHMSS5105I | The warranty for {0} with the UUID {1} is expired. | Informational |
| FQXHMSS5106I | An event was received from an endpoint that is not currently managed, at IP address {0}. This event has been ignored. | Informational |
| FQXHMSS5107I | The management server detected duplicate files. | Informational |
| FQXHMSS5108I | Call Home and all other active serviceability functions for event {0} from system {1} were suppressed because the event matches one of the excluded events. | Informational |
| FQXHMSS5109I | The user {0} from IP address {1} has successfully enabled the option to suppress service forwarders for excluded events. | Informational |
| FQXHMSS5110I | The user {0} from IP address {1} has successfully disabled the option to suppress service forwarders for excluded events. | Informational |
| FQXHMSS5111I | The request from user {0} from IP address {1} to enable the option to suppress service forwarders for excluded events was not successful. | Informational |
| FQXHMSS5112I | The request from user {0} from IP address {1} to disable the option to suppress service forwarders for excluded events was not successful. | Informational |
| FQXHMSS5113I | User {0} from IP address {1} has enabled the IP Duplication check service. | Informational |
| FQXHMSS5114I | User {0} from IP address {1} has disabled the IP Duplication check service. | Informational |
| FQXHMSS5115I | User {0} from IP address {1} enabled the SSD Life Check Service. | Informational |
| FQXHMSS5116I | User {0} from IP address {1} disabled the SSD Life Check Service. | Informational |
| FQXHMSS5117I | User {0} from IP address {1} changed the warning threshold level for checking the remaining life of SDDs from {2} to {3}. | Informational |
| FQXHMSS5118I | User {0} from IP address {1} changed the error threshold level for checking the remaining life of SDDs from {2} to {3}. | Informational |
| FQXHMSS5119I | The warranty period was set successfully to : {0} days. | Informational |
| FQXHMUP1105I | Update setting {0} was updated from {1} to {2} by user {3}. | Informational |
| FQXHMUP2301I | New devices were added to firmware Updates Inventory. {0}. | Informational |
| FQXHMUP2302I | Some devices were removed from the firmware Updates Inventory. {0}. | Informational |
| FQXHMUP2303I | Some components were added to the firmware Updates Inventory. {0}. | Informational |
| FQXHMUP2304I | Some components were removed from the firmware Updates Inventory. {0}. | Informational |
| FQXHMUP2305I | The firmware updates inventory has changed. {0}. | Informational |
| FQXHMUP2306I | The driver updates inventory has changed. {0}. | Informational |
| FQXHMUP3100I | New compliance data detected. {0}. | Informational |
| FQXHMUP4003I | Firmware Updates were started on system {0} by user {1}. | Informational |
| FQXHMUP4004I | Firmware Updates were started on management server {0} by user {1}. | Informational |
| FQXHMUP4005I | Firmware Updates were started on switch {0} by user {1}. | Informational |
| FQXHMUP4006I | The firmware was updated on system device {0} by user {1}. | Informational |
| FQXHMUP4007I | The firmware was updated on management server {0} by user {1}. | Informational |
| FQXHMUP4008I | The firmware was updated on switch device {0} by user {1}. | Informational |
| FQXHMUP4101I | Firmware Updates were started on storage {0} by user {1}. | Informational |
| FQXHMUP4102I | The firmware was updated on storage {0} by user {1}. | Informational |
| FQXHMUP6010I | The packages have been downloaded: {0} by user {1}. | Informational |
| FQXHMUP6020I | The packages have been imported: {0} by user {1}. | Informational |
| FQXHMUP6021I | The packages have been imported: {0}; The packages have been discarded: {1} by user {2}. | Informational |
| FQXHMUP6022I | The packages have been discarded: {0} by user {1}. | Informational |
| FQXHMUP6030I | The packages have been deleted: {0} by user {1}. | Informational |
| FQXHMUP6101I | The package {0} has been applied by user {1}. | Informational |
| FQXPMCL0005I | Start to install OS. | Informational |
| FQXPMCL0006I | Export raid config successfully. | Informational |
| FQXPMCL0007I | Import raid config successfully. | Informational |
| FQXPMCL0008I | Export uefi settings successfully. | Informational |
| FQXPMCL0009I | Import uefi settings successfully. | Informational |
| FQXPMCL0010I | Export bmc settings successfully. | Informational |
| FQXPMCL0011I | Import bmc settings successfully. | Informational |
| FQXPMEM0002I | LXPM firmware image found. Starting LXPM | Informational |
| FQXPMEM0003I | LXPM has exited. Control returned to UEFI | Informational |
| FQXPMEM0004I | Launching diagnostic program | Informational |
| FQXPMEM0005I | boot diagnostic program success | Informational |
| FQXPMNM0002I | Set BMC network parameters to new values. | Informational |
| FQXPMOS0010I | Red Hat RHEL 7.3 (64-bit) OS installed | Informational |
| FQXPMOS0011I | Red Hat RHEL 6.9 (64-bit) OS installed | Informational |
| FQXPMOS0012I | SLES 12 for AMD64 and Intel64 Service Pack 2 OS installed | Informational |
| FQXPMOS0013I | SLES 11 for AMD64 and Intel64 Service Pack 4 OS installed | Informational |
| FQXPMOS0014I | Windows Server 2012 R2 SERVERWINFOUNDATION OS installed | Informational |
| FQXPMOS0015I | Windows Server 2012 R2 SERVERSTANDARD OS installed | Informational |
| FQXPMOS0016I | Windows Server 2012 R2 SERVERDATACENTER OS installed | Informational |
| FQXPMOS0017I | Windows Server 2012 R2 SERVERSOLUTION OS installed | Informational |
| FQXPMOS0018I | Windows Server 2012 R2 SERVERSTORAGESTANDARD OS installed | Informational |
| FQXPMOS0019I | Hyper-V Server 2012 R2 SERVERHYPERCORE OS installed | Informational |
| FQXPMOS0020I | Hyper-V Server 2016 SERVERHYPERCORE OS installed | Informational |
| FQXPMOS0021I | Windows Server 2016 SERVERSOLUTION OS installed | Informational |
| FQXPMOS0022I | Windows Server 2016 SERVERSTANDARD OS installed | Informational |
| FQXPMOS0023I | Windows Server 2016 SERVERDATACENTER OS installed | Informational |
| FQXPMOS0024I | Windows Server 2016 SERVERSTORAGESTANDARD OS installed | Informational |
| FQXPMOS0025I | Windows Server 2016 SERVERSTORAGEWORKGROUP OS installed | Informational |
| FQXPMOS0026I | Vmware ESXi 6.5 U1 OS installed | Informational |
| FQXPMOS0027I | Vmware ESXi 6.0 U3 OS installed | Informational |
| FQXPMSR0012I | Change disk drives' state successfully. | Informational |
| FQXPMSR0022I | Create new virtual disk successfully. | Informational |
| FQXPMSR0032I | Removed existing virtual disk successfully. | Informational |
| FQXPMUP0101I | Start to update LXPM | Informational |
| FQXPMUP0102I | Start to update window driver | Informational |
| FQXPMUP0103I | Start to update linux driver | Informational |
| FQXPMUP0104I | Start to update UEFI | Informational |
| FQXPMUP0105I | Start to update BMC | Informational |
| FQXPMUP0106I | Successful to update the firmware | Informational |
| FQXPMVD0003I | Update VPD data successfully. | Informational |
| FQXSFDD0001I | DRIVER HEALTH PROTOCOL: Missing Configuration. Requires Change Settings From F1. | Informational |
| FQXSFDD0003I | DRIVER HEALTH PROTOCOL: Reports 'Reboot' Required Controller. | Informational |
| FQXSFIO0013I | The device found at Bus {0} Device {1} Function {2} could not be configured due to resource constraints. The Vendor ID for the device is {3} and the Device ID is {4}. The physical slot number is {5}. | Informational |
| FQXSFIO0015I | IFM: System reset performed to reset adapters. | Informational |
| FQXSFIO0018I | IFM: Configuration too large for compatibility mode. | Informational |
| FQXSFMA0001I | DIMM {0} Disable has been recovered. {1}. | Informational |
| FQXSFMA0002I | The uncorrectable memory error state has been cleared. | Informational |
| FQXSFMA0006I | {0} DIMM {1} has been detected, the DIMM serial number is {2}. | Informational |
| FQXSFMA0007I | {0} DIMM number {1} has been replaced. {2}. | Informational |
| FQXSFMA0008I | DIMM {0} POST memory test failure has been recovered. {1}. | Informational |
| FQXSFMA0009I | Invalid memory configuration for Mirror Mode has been recovered. {0}. | Informational |
| FQXSFMA0010I | Invalid memory configuration for Sparing Mode has been recovered. {0}. | Informational |
| FQXSFMA0011I | Memory population change detected. {0}. | Informational |
| FQXSFMA0012I | The PFA of DIMM {0} has been deasserted. | Informational |
| FQXSFMA0013I | Mirror Fail-over complete. DIMM {0} has failed over to to the mirrored copy. {1}. | Informational |
| FQXSFMA0014I | Memory spare copy initiated. {0}. | Informational |
| FQXSFMA0015I | Memory spare copy has completed successfully. {0}. | Informational |
| FQXSFMA0017I | DIMM Re-enabled. {0}. | Informational |
| FQXSFMA0018I | DIMM Service Action Detected, Slot Re-Enabled. {0}. | Informational |
| FQXSFMA0019I | System Memory Resized. {0}. | Informational |
| FQXSFMA0026I | DIMM {0} Self-healing attempt at Rank {1} Sub Rank {2} Bank {3} Row {4} in Device {5}. {6}. | Informational |
| FQXSFMA0029I | The PFA of DIMM {0} has been deasserted after applying PPR for this DIMM. {1}. | Informational |
| FQXSFPU0017I | A processor microcode update failed. | Informational |
| FQXSFPU0020I | The UEFI firmware image capsule signature is invalid. | Informational |
| FQXSFPU0021I | The TPM physical presence state has been cleared. | Informational |
| FQXSFPU0022I | The TPM configuration is not locked. | Informational |
| FQXSFPU0023I | Secure Boot Image Verification Failure has been cleared as no failure in this round boot. | Informational |
| FQXSFPU0024I | TCM_TPM_POLICY is undefined. | Informational |
| FQXSFPU0025I | The default system settings have been restored. | Informational |
| FQXSFPU0026I | TCM daughter card field update is not supported. Please remove the TCM daughter card and reboot. | Informational |
| FQXSFPU0027I | TCM daughter card has been changed. Please return to the original TCM daughter card and reboot. | Informational |
| FQXSFPU0028I | Intel BIOS ACM startup failed, make sure TPM is enabled. | Informational |
| FQXSFPU0029I | The default system settings have been restored. | Informational |
| FQXSFPU4034I | TPM Firmware recovery is finished, rebooting system to take effect. | Informational |
| FQXSFPU4037I | TPM Firmware recovery is finished. | Informational |
| FQXSFPU4038I | TPM Firmware recovery successful. | Informational |
| FQXSFPU4041I | TPM Firmware update is in progress. Please DO NOT power off or reset system. | Informational |
| FQXSFPU4042I | TPM Firmware update is finished, rebooting system to take effect. | Informational |
| FQXSFPU4044I | The current TPM firmware version could not support TPM version toggling. | Informational |
| FQXSFPU4046I | TPM Firmware will be updated from TPM1.2 to TPM2.0. | Informational |
| FQXSFPU4047I | TPM Firmware will be updated from TPM2.0 to TPM1.2. | Informational |
| FQXSFPU4048I | TPM Firmware update is finished. | Informational |
| FQXSFPU4049I | TPM Firmware update successful. | Informational |
| FQXSFPU4052I | TPM_TCM_POLICY is not locked | Informational |
| FQXSFPU4055I | System boot is blocked, please remove TCM card. | Informational |
| FQXSFPU4080I | Host Power-On password has been changed. | Informational |
| FQXSFPU4081I | Host Power-On password has been cleared. | Informational |
| FQXSFPU4082I | Host Admin password has been changed. | Informational |
| FQXSFPU4083I | Host Admin password has been cleared. | Informational |
| FQXSFPU4084I | Host boot order has been changed. | Informational |
| FQXSFPU4085I | Host WOL boot order has been changed. | Informational |
| FQXSFSM0007I | The XCC System Event log (SEL) is full. | Informational |
| FQXSFSR0002I | {0} GPT corruption recovered, DiskGUID: {1}. | Informational |
| FQXSPBR4000I | Management Controller {0}: Configuration restored from a file by user {1}. | Informational |
| FQXSPBR4001I | Running the backup Management Controller {0} main application. | Informational |
| FQXSPBR4002I | Management Controller {0} Reset was caused by restoring default values. | Informational |
| FQXSPBR4003I | Platform Watchdog Timer expired for {0}. | Informational |
| FQXSPBR4004I | Server timeouts set by user {0}: EnableOSWatchdog={1}, OSWatchdogTimout={2}, EnableLoaderWatchdog={3}, LoaderTimeout={4}. | Informational |
| FQXSPBR4005I | Management Controller {0}: Configuration saved to a file by user {1}. | Informational |
| FQXSPBR4006I | Management Controller {0}: Configuration restoration from a file by user {1} completed. | Informational |
| FQXSPBR4007I | Management Controller {0}: Configuration restoration from a file by user {1} failed to complete. | Informational |
| FQXSPBR4008I | Management Controller {0}: Configuration restoration from a file by user {1} failed to start. | Informational |
| FQXSPBT0000I | Power On for system {0}. | Informational |
| FQXSPBT0001I | Power Cycle Hard requested for system {0}. | Informational |
| FQXSPBT0002I | Power Cycle Hard requested for system {0}. | Informational |
| FQXSPBT0003I | Power Cycle Soft requested for system {0}. | Informational |
| FQXSPBT0004I | PXE Boot Requested for system {0}. | Informational |
| FQXSPBT0005I | Diagnostics Boot Requested for system {0}. | Informational |
| FQXSPBT0006I | System Restart Requested for system {0}. | Informational |
| FQXSPBT0007I | No bootable media available for system {0}. | Informational |
| FQXSPBT0008I | Non-bootable media selected for system {0}. | Informational |
| FQXSPBT0009I | Non-bootable media selected for system {0}. | Informational |
| FQXSPBT0010I | PXE server not found for system {0}. | Informational |
| FQXSPBT0011I | User timeout on boot for system {0}. | Informational |
| FQXSPBT0012I | System {0} boot from floppy {1} initiated. | Informational |
| FQXSPBT0013I | System {0} boot from local drive {1} initiated. | Informational |
| FQXSPBT0014I | System {0} boot from PXE on Network Port {1} initiated. | Informational |
| FQXSPBT0015I | System {0} boot diagnostics initiated. | Informational |
| FQXSPBT0016I | System {0} boot from CD {1} initiated. | Informational |
| FQXSPBT0017I | System {0} boot from ROM initiated. | Informational |
| FQXSPBT0018I | System {0} boot initiated. | Informational |
| FQXSPBT0019I | Critical Stop during OS load on system {0}. | Informational |
| FQXSPBT0020I | Run-time critical stop on system {0}. | Informational |
| FQXSPBT0021I | OS Graceful stop on system {0}. | Informational |
| FQXSPBT0022I | OS Graceful shutdown begun on system {0}. | Informational |
| FQXSPBT0023I | OS Graceful shutdown begun on system {0}. | Informational |
| FQXSPBT0024I | Agent not responding on system {0}. | Informational |
| FQXSPCA0012I | Sensor {0} has transitioned to normal state. | Informational |
| FQXSPCA0013I | Sensor {0} has transitioned to normal state. | Informational |
| FQXSPCA0020I | Sensor {0} has transitioned to non-critical from a more severe state. | Informational |
| FQXSPCA0021I | Sensor {0} has transitioned to non-critical from a more severe state. | Informational |
| FQXSPCA0026I | Sensor {0} indicates a monitor state. | Informational |
| FQXSPCA0027I | Sensor {0} indicates a monitor state. | Informational |
| FQXSPCA0028I | Sensor {0} has an informational state. | Informational |
| FQXSPCA0029I | Sensor {0} has an informational state. | Informational |
| FQXSPCA0030I | Redundancy {0} has been restored. | Informational |
| FQXSPCA2000I | Numeric sensor {0} going low (lower non-critical) has deasserted. | Informational |
| FQXSPCA2001I | Numeric sensor {0} going low (lower non-critical) has deasserted. | Informational |
| FQXSPCA2002I | Numeric sensor {0} going low (lower critical) has deasserted. | Informational |
| FQXSPCA2003I | Numeric sensor {0} going low (lower critical) has deasserted. | Informational |
| FQXSPCA2004I | Numeric sensor {0} going low (lower non-recoverable) has deasserted. | Informational |
| FQXSPCA2005I | Numeric sensor {0} going low (lower non-recoverable) has deasserted. | Informational |
| FQXSPCA2006I | Numeric sensor {0} going high (upper non-critical) has deasserted. | Informational |
| FQXSPCA2007I | Numeric sensor {0} going high (upper non-critical) has deasserted. | Informational |
| FQXSPCA2008I | Numeric sensor {0} going high (upper critical) has deasserted. | Informational |
| FQXSPCA2009I | Numeric sensor {0} going high (upper critical) has deasserted. | Informational |
| FQXSPCA2010I | Numeric sensor {0} going high (upper non-recoverable) has deasserted. | Informational |
| FQXSPCA2011I | Numeric sensor {0} going high (upper non-recoverable) has deasserted. | Informational |
| FQXSPCA2014I | Sensor {0} has deasserted the transition from normal to non-critical state. | Informational |
| FQXSPCA2015I | Sensor {0} has deasserted the transition from normal to non-critical state. | Informational |
| FQXSPCA2016I | Sensor {0} has transitioned to a less severe state from critical. | Informational |
| FQXSPCA2017I | Sensor {0} has transitioned to a less severe state from critical. | Informational |
| FQXSPCA2018I | Sensor {0} has deasserted the transition to non-recoverable from a less severe state. | Informational |
| FQXSPCA2019I | Sensor {0} has deasserted the transition to non-recoverable from a less severe state. | Informational |
| FQXSPCA2024I | Sensor {0} has deasserted the transition to non-recoverable. | Informational |
| FQXSPCA2025I | Sensor {0} has deasserted the transition to non-recoverable. | Informational |
| FQXSPCA2031I | Redundancy Lost for {0} has deasserted. | Informational |
| FQXSPCA2032I | Redundancy Degraded for {0} has deasserted. | Informational |
| FQXSPCA2033I | Non-redundant:Sufficient Resources from Redundancy Degraded or Fully Redundant for {0} has deasserted. | Informational |
| FQXSPCA2034I | Non-redundant:Sufficient Resources from Insufficient Resources for {0} has deasserted. | Informational |
| FQXSPCA2035I | Non-redundant:Insufficient Resources for {0} has deasserted. | Informational |
| FQXSPCA2036I | Redundancy Degraded from Fully Redundant for {0} has deasserted. | Informational |
| FQXSPCA2037I | Redundancy Degraded from Non-redundant for {0} has deasserted. | Informational |
| FQXSPCN4000I | Serial Redirection set by user {0}: Mode={1}, BaudRate={2}, StopBits={3}, Parity={4}, SessionTerminateSequence={5}. | Informational |
| FQXSPCN4001I | Remote Control session started by user {0} in {1} mode. | Informational |
| FQXSPCN4002I | User {0} has terminated an active console session. | Informational |
| FQXSPCN4003I | Remote Control session started by user {0} in {1} mode has been closed. | Informational |
| FQXSPCR2001I | Sensor {0} has deasserted the transition to non-recoverable from a less severe state. | Informational |
| FQXSPDA0001I | The Power Button {0} has been pressed. | Informational |
| FQXSPDA0002I | The Sleep Button {0} has been pressed. | Informational |
| FQXSPDA0003I | The Reset Button {0} has been pressed. | Informational |
| FQXSPDA0004I | The Latch to {0} has been opened. | Informational |
| FQXSPDA0005I | The Service Request {0} has been enabled. | Informational |
| FQXSPDA2000I | The System {0} has detected a POST Error deassertion. | Informational |
| FQXSPDA2004I | The Latch to {0} has been closed. | Informational |
| FQXSPDM4000I | Inventory data changed for device {0}, new device data hash={1}, new master data hash={2}. | Informational |
| FQXSPDM4001I | Storage {0} has changed. | Informational |
| FQXSPDM4002I | Device {0} VPD is not valid. | Informational |
| FQXSPDM4003I | TKLM servers set by user {0}: TKLMServer1={1} Port={2}, TKLMServer2={3} Port={4}, TKLMServer3={5} Port={6}, TKLMServer4={7} Port={8}. | Informational |
| FQXSPDM4004I | TKLM servers device group set by user {0}: TKLMServerDeviceGroup={1}. | Informational |
| FQXSPDM4005I | User {0} has generated a new encryption key pair and installed a self-signed certificate for the TKLM client. | Informational |
| FQXSPDM4006I | User {0} has generated a new encryption key and certificate signing request for the TKLM client. | Informational |
| FQXSPDM4007I | User {0} has imported a signed certificate for the TKLM client from {1}. | Informational |
| FQXSPDM4008I | User {0} has imported a server certificate for the TKLM server. | Informational |
| FQXSPDM4009I | User {0} has {1} file {2} from {3}. | Informational |
| FQXSPDM4010I | Inventory data collecting and processing complete for {0}, sequence number is {1}. | Informational |
| FQXSPEA2001I | Sensor {0} has deasserted the transition from normal to non-critical state. | Informational |
| FQXSPEA2002I | Sensor {0} has transitioned to a less severe state from critical. | Informational |
| FQXSPEM0000I | The Log {0} used by {1} has been disabled. | Informational |
| FQXSPEM0001I | The Log {0} used by {1} has been disabled. | Informational |
| FQXSPEM0002I | The Log {0} used by {1} has been disabled. | Informational |
| FQXSPEM0003I | The Log {0} has been cleared. | Informational |
| FQXSPEM0004I | The Log {0} is full. | Informational |
| FQXSPEM0005I | The Log {0} is almost full. | Informational |
| FQXSPEM0006I | The System {0} has been reconfigured. | Informational |
| FQXSPEM0007I | The System {0} has encountered an OEM System Boot Event. | Informational |
| FQXSPEM0009I | The System {0} has generated an auxiliary Log Entry in Log {1}. | Informational |
| FQXSPEM0012I | Management system {0} is off-line. | Informational |
| FQXSPEM0016I | FRU {0} not installed on system {1}. | Informational |
| FQXSPEM0017I | Activation requested for FRU {0} on system {1}. | Informational |
| FQXSPEM0018I | FRU {0} on system {1} is active. | Informational |
| FQXSPEM0019I | Activation in progress for FRU {0} on system {1}. | Informational |
| FQXSPEM0020I | Deactivation request for FRU {0} on system {1}. | Informational |
| FQXSPEM0021I | FRU {0} on system {1} is in standby or 'hot spare' state. | Informational |
| FQXSPEM0022I | Deactivation in progress for FRU {0} on system {1}. | Informational |
| FQXSPEM0023I | Communication lost with FRU {0} on system {1}. | Informational |
| FQXSPEM2000I | The Log {0} used by {1} has been enabled. | Informational |
| FQXSPEM2001I | The Log {0} used by {1} has been enabled. | Informational |
| FQXSPEM2002I | The Log {0} used by {1} has been enabled. | Informational |
| FQXSPEM2004I | The Log {0} is no longer full. | Informational |
| FQXSPEM2008I | The System {0} has recovered from a system hardware fault. | Informational |
| FQXSPEM2010I | Sensor {0} has returned to normal on management system {1}. | Informational |
| FQXSPEM2011I | Controller {0} has returned to normal on management system {1}. | Informational |
| FQXSPEM2012I | Management system {0} is enabled. | Informational |
| FQXSPEM2013I | Management system {0} is enabled. | Informational |
| FQXSPEM2014I | Sensor {0} has returned to normal on management system {1}. | Informational |
| FQXSPEM2015I | FRU {0} has recovered on management system {1}. | Informational |
| FQXSPEM4000I | The {0} on system {1} cleared by user {2}. | Informational |
| FQXSPEM4001I | The {0} on system {1} is 75% full. | Informational |
| FQXSPEM4002I | The {0} on system {1} is 100% full. | Informational |
| FQXSPEM4003I | LED {0} state changed to {1} by {2}. | Informational |
| FQXSPEM4004I | SNMP {0} enabled by user {1}. | Informational |
| FQXSPEM4005I | SNMP {0} disabled by user {1}. | Informational |
| FQXSPEM4006I | Alert Configuration Global Event Notification set by user {0}: RetryLimit={1}, RetryInterval={2}, EntryInterval={3}. | Informational |
| FQXSPEM4007I | Alert Recipient Number {0} updated: Name={1}, DeliveryMethod={2}, Address={3}, IncludeLog={4}, Enabled={5}, EnabledAlerts={6}, AllowedFilters={7}. | Informational |
| FQXSPEM4008I | SNMP Traps enabled by user {0}: EnabledAlerts={1}, AllowedFilters={2}. | Informational |
| FQXSPEM4009I | The UEFI Definitions have been changed. | Informational |
| FQXSPEM4010I | UEFI Reported: {0}. | Informational |
| FQXSPEM4011I | XCC failed to log previous event {0}. | Informational |
| FQXSPEM4012I | User {0} made system {1} Encapsulation lite Mode. | Informational |
| FQXSPEM4013I | Battery error was detected by RAID controller. The battery unit needs replacement.({0},{1},{2},{3},{4}) | Informational |
| FQXSPEM4014I | The RAID controller has problem with the battery. Please contact technical support to resolve this issue.({0},{1},{2},{3},{4}) | Informational |
| FQXSPEM4015I | The RAID controller detected unrecoverable error. The controller needs replacement.({0},{1},{2},{3},{4}) | Informational |
| FQXSPEM4016I | The RAID controller detected one or more problems. Please contact technical support for additional assistance.({0},{1},{2},{3},{4}) | Informational |
| FQXSPEM4017I | The RAID controller detected one or more possible configuration changes within the subsystem. Please check the drive LED status. If necessary, contact technical support for additional assistance.({0},{1},{2},{3},{4}) | Informational |
| FQXSPEM4018I | Enclosure issue detected with one or more units. Please check the enclosure units to repair the problem.({0},{1},{2},{3},{4}) | Informational |
| FQXSPEM4019I | Connectivity issue detected with the enclosure. Please check your cable configurations to repair the problem.({0},{1},{2},{3},{4}) | Informational |
| FQXSPEM4020I | Fan problem detected with the enclosure. Please check the enclosure unit fan for correct operation.({0},{1},{2},{3},{4}) | Informational |
| FQXSPEM4022I | Enclosure power supply has problem. Please check the enclosure unit power supply for correct operation.({0},{1},{2},{3},{4}) | Informational |
| FQXSPEM4023I | One or more virtual drive are in abnormal status that may cause unavailable virtual drive. Please check the event logs and if events are targeted to the same disk then replace the drive. If necessary, contact technical support for additional assistance.({0},{1},{2},{3},{4}) | Informational |
| FQXSPEM4024I | The RAID controller detected one or more possible configuration problem within the subsystem. Please check the event logs and if events are targeted to the same disk then replace the drive. If necessary, contact technical support for additional assistance.({0},{1},{2},{3},{4}) | Informational |
| FQXSPEM4025I | One or more virtual drive have problem. Please contact technical support to resolve this issue.({0},{1},{2},{3},{4}) | Informational |
| FQXSPEM4026I | Drive error was detected by RAID controller. Please contact technical support to resolve this issue.({0},{1},{2},{3},{4}) | Informational |
| FQXSPEM4027I | Drive error was detected by RAID controller. Please check the event logs and if events are targeted to the same disk then replace the drive. If necessary, contact technical support for additional assistance.({0},{1},{2},{3},{4}) | Informational |
| FQXSPEM4028I | The port {0} of PCIe device {1} at {2} has link {3}. | Informational |
| FQXSPEM4029I | All PCIe slots on {0} may not be functional based upon your current CPU population. | Informational |
| FQXSPEM4030I | A scheduled operation on the RAID controller has encountered an issue. Refer to RAID Logs under Server Management, Local Storage, for details.({0},{1},{2},{3},{4}) | Informational |
| FQXSPFC4000I | The bare metal connection process has been started. | Informational |
| FQXSPFC4001I | The bare metal update application reports a status of {0}. | Informational |
| FQXSPFC4002I | System running in setup. | Informational |
| FQXSPFC4003I | UEFI deployment boot mode is enabled for NextBoot. | Informational |
| FQXSPFC4004I | UEFI deployment boot mode is enabled for NextAc. | Informational |
| FQXSPFC4005I | UEFI deployment boot mode has been disabled. | Informational |
| FQXSPFW0003I | The System {0} encountered firmware progress. | Informational |
| FQXSPFW0004I | UEFI advanced memory test is completed. | Informational |
| FQXSPFW0005I | UEFI advanced memory test is completed. | Informational |
| FQXSPFW2000I | The System {0} has detected a POST Error deassertion. | Informational |
| FQXSPFW2001I | The System {0} has detected a POST Error deassertion. | Informational |
| FQXSPFW2002I | The System {0} has recovered from a firmware hang. | Informational |
| FQXSPIO0000I | The connector {0} has been connected. | Informational |
| FQXSPIO0009I | An EISA Fail Safe timeout occurred on system {0}. | Informational |
| FQXSPIO0010I | A Correctable Bus Error has occurred on bus {0}. | Informational |
| FQXSPIO0016I | Identifying slot {0} on system {1}. | Informational |
| FQXSPIO0017I | Package installed in slot {0} for system {1}. | Informational |
| FQXSPIO0018I | Slot {0} in system {1} is ready for installation. | Informational |
| FQXSPIO0019I | Slot {0} in system {1} is ready for removal. | Informational |
| FQXSPIO0020I | Power is off on slot {0} of system {1}. | Informational |
| FQXSPIO0021I | Removal requested for slot {0} of system {1}. | Informational |
| FQXSPIO0022I | Interlock activated on slot {0} of system {1}. | Informational |
| FQXSPIO0024I | Slot {0} of system {1} holds spare. | Informational |
| FQXSPIO2001I | The connector {0} configuration error has been repaired. | Informational |
| FQXSPIO2002I | The System {0} has detected a POST Error deassertion. | Informational |
| FQXSPIO2003I | System {0} has recovered from a diagnostic interrupt. | Informational |
| FQXSPIO2004I | Bus {0} has recovered from a bus timeout. | Informational |
| FQXSPIO2005I | System {0} has recovered from an NMI. | Informational |
| FQXSPIO2006I | System {0} has recovered from an NMI. | Informational |
| FQXSPIO2007I | A PCI PERR recovery has occurred on system {0}. | Informational |
| FQXSPIO2008I | A PCI SERR on system {0} has deasserted. | Informational |
| FQXSPIO2009I | System {0} has recovered from a EISA Fail Safe timeout. | Informational |
| FQXSPIO2010I | Bus {0} has recovered from a Correctable Bus Error. | Informational |
| FQXSPIO2011I | Bus {0} has recovered from an Uncorrectable Error. | Informational |
| FQXSPIO2012I | System {0} has recovered from a Fatal NMI. | Informational |
| FQXSPIO2013I | Bus {0} has recovered from a Fatal Bus Error. | Informational |
| FQXSPIO2014I | Bus {0} is no longer operating in a degraded state. | Informational |
| FQXSPIO2015I | Fault condition removed on slot {0} on system {1}. | Informational |
| FQXSPIO2017I | Slot {0} empty for system {1}. | Informational |
| FQXSPIO2020I | Power is on for slot {0} of system {1}. | Informational |
| FQXSPIO2023I | Slot {0} enabled on system {1}. | Informational |
| FQXSPIO2024I | Slot {0} of system {1} no longer holds spare. | Informational |
| FQXSPMA0001I | Error Detected and Corrected for {0} on Subsystem {1}. | Informational |
| FQXSPMA0003I | {0} Added on Subsystem {1}. | Informational |
| FQXSPMA0004I | {0} Disabled on Subsystem {1}. | Informational |
| FQXSPMA0009I | Memory sparing initiated for {0} on Subsystem {1}. | Informational |
| FQXSPMA0014I | Redundancy {0} has been restored. | Informational |
| FQXSPMA0022I | Memory sparing initiated for {0} on Subsystem {1}. | Informational |
| FQXSPMA0023I | Memory sparing initiated for {0} on Subsystem {1}. | Informational |
| FQXSPMA0025I | Sensor {0} has asserted. | Informational |
| FQXSPMA2002I | Configuration error for {0} on Subsystem {1} has deasserted. | Informational |
| FQXSPMA2003I | {0} Removed on Subsystem {1}. | Informational |
| FQXSPMA2004I | {0} Enabled on Subsystem {1}. | Informational |
| FQXSPMA2005I | The System {0} has detected a POST Error deassertion. | Informational |
| FQXSPMA2006I | Parity Error Recovery for {0} on Subsystem {1}. | Informational |
| FQXSPMA2007I | Scrub Failure for {0} on Subsystem {1} has recovered. | Informational |
| FQXSPMA2008I | Uncorrectable error recovery detected for {0} on Subsystem {1}. | Informational |
| FQXSPMA2009I | Memory sparing concluded for {0} on Subsystem {1}. | Informational |
| FQXSPMA2010I | {0} on Subsystem {1} is no longer Throttled. | Informational |
| FQXSPMA2011I | Memory Logging Limit Removed for {0} on Subsystem {1}. | Informational |
| FQXSPMA2012I | An Over-Temperature Condition has been removed on the {0} on Subsystem {1}. | Informational |
| FQXSPMA2013I | The System {0} has detected a POST Error deassertion. | Informational |
| FQXSPMA2015I | Redundancy Lost for {0} has deasserted. | Informational |
| FQXSPMA2016I | Redundancy Degraded for {0} has deasserted. | Informational |
| FQXSPMA2017I | Non-redundant:Sufficient Resources from Redundancy Degraded or Fully Redundant for {0} has deasserted. | Informational |
| FQXSPMA2018I | Non-redundant:Sufficient Resources from Insufficient Resources for {0} has deasserted. | Informational |
| FQXSPMA2019I | Non-redundant:Insufficient Resources for {0} has deasserted. | Informational |
| FQXSPMA2020I | Redundancy Degraded from Fully Redundant for {0} has deasserted. | Informational |
| FQXSPMA2021I | Redundancy Degraded from Non-redundant for {0} has deasserted. | Informational |
| FQXSPMA2024I | Sensor {0} has deasserted. | Informational |
| FQXSPNM4000I | Management Controller {0} Network Initialization Complete. | Informational |
| FQXSPNM4001I | Ethernet Data Rate modified from {0} to {1} by user {2}. | Informational |
| FQXSPNM4002I | Ethernet Duplex setting modified from {0} to {1} by user {2}. | Informational |
| FQXSPNM4003I | Ethernet MTU setting modified from {0} to {1} by user {2}. | Informational |
| FQXSPNM4004I | Ethernet locally administered MAC address modified from {0} to {1} by user {2}. | Informational |
| FQXSPNM4005I | Ethernet interface {0} by user {1}. | Informational |
| FQXSPNM4006I | Hostname set to {0} by user {1}. | Informational |
| FQXSPNM4007I | IP address of network interface modified from {0} to {1} by user {2}. | Informational |
| FQXSPNM4008I | IP subnet mask of network interface modified from {0} to {1} by user {2}. | Informational |
| FQXSPNM4009I | IP address of default gateway modified from {0} to {1} by user {2}. | Informational |
| FQXSPNM4010I | DHCP[{0}] failure, no IP address assigned. | Informational |
| FQXSPNM4011I | ENET[{0}] DHCP-HSTN={1}, DN={2}, IP@={3}, SN={4}, GW@={5}, DNS1@={6}. | Informational |
| FQXSPNM4012I | ENET[{0}] IP-Cfg:HstName={1}, IP@={2}, NetMsk={3}, GW@={4}. | Informational |
| FQXSPNM4013I | LAN: Ethernet[{0}] interface is no longer active. | Informational |
| FQXSPNM4014I | LAN: Ethernet[{0}] interface is now active. | Informational |
| FQXSPNM4015I | DHCP setting changed to {0} by user {1}. | Informational |
| FQXSPNM4016I | Domain name set to {0} by user {1}. | Informational |
| FQXSPNM4017I | Domain Source changed to {0} by user {1}. | Informational |
| FQXSPNM4018I | DDNS setting changed to {0} by user {1}. | Informational |
| FQXSPNM4019I | DDNS registration successful. The domain name is {0}. | Informational |
| FQXSPNM4020I | IPv6 enabled by user {0}. | Informational |
| FQXSPNM4021I | IPv6 disabled by user {0}. | Informational |
| FQXSPNM4022I | IPv6 static IP configuration enabled by user {0}. | Informational |
| FQXSPNM4023I | IPv6 DHCP enabled by user {0}. | Informational |
| FQXSPNM4024I | IPv6 stateless auto-configuration enabled by user {0}. | Informational |
| FQXSPNM4025I | IPv6 static IP configuration disabled by user {0}. | Informational |
| FQXSPNM4026I | IPv6 DHCP disabled by user {0}. | Informational |
| FQXSPNM4027I | IPv6 stateless auto-configuration disabled by user {0}. | Informational |
| FQXSPNM4028I | ENET[{0}] IPv6-LinkLocal:HstName={1}, IP@={2}, Pref={3}. | Informational |
| FQXSPNM4029I | ENET[{0}] IPv6-Static:HstName={1}, IP@={2}, Pref={3}, GW@={4}. | Informational |
| FQXSPNM4030I | ENET[{0}] DHCPv6-HSTN={1}, DN={2}, IP@={3}, Pref={4}, DNS1@={4}. | Informational |
| FQXSPNM4031I | IPv6 static address of network interface modified from {0} to {1} by user {2}. | Informational |
| FQXSPNM4032I | DHCPv6 failure, no IP address assigned. | Informational |
| FQXSPNM4033I | Telnet port number changed from {0} to {1} by user {2}. | Informational |
| FQXSPNM4034I | SSH port number changed from {0} to {1} by user {2}. | Informational |
| FQXSPNM4035I | Web-HTTP port number changed from {0} to {1} by user {2}. | Informational |
| FQXSPNM4036I | Web-HTTPS port number changed from {0} to {1} by user {2}. | Informational |
| FQXSPNM4037I | CIM/XML HTTP port number changed from {0} to {1} by user {2}. | Informational |
| FQXSPNM4038I | CIM/XML HTTPS port number changed from {0} to {1} by user {2}. | Informational |
| FQXSPNM4039I | SNMP Agent port number changed from {0} to {1} by user {2}. | Informational |
| FQXSPNM4040I | SNMP Traps port number changed from {0} to {1} by user {2}. | Informational |
| FQXSPNM4041I | Syslog port number changed from {0} to {1} by user {2}. | Informational |
| FQXSPNM4042I | Remote Presence port number changed from {0} to {1} by user {2}. | Informational |
| FQXSPNM4043I | SMTP Server set by user {0} to {1}:{2}. | Informational |
| FQXSPNM4044I | Telnet {0} by user {1}. | Informational |
| FQXSPNM4045I | DNS servers set by user {0}: UseAdditionalServers={1}, PreferredDNStype={2}, IPv4Server1={3}, IPv4Server2={4}, IPv4Server3={5}, IPv6Server1={6}, IPv6Server2={7}, IPv6Server3={8}. | Informational |
| FQXSPNM4046I | LAN over USB {0} by user {1}. | Informational |
| FQXSPNM4047I | LAN over USB Port Forwarding set by user {0}: ExternalPort={1}, USB-LAN port={2}. | Informational |
| FQXSPNM4048I | PXE boot requested by user {0}. | Informational |
| FQXSPNM4049I | User {0} has initiated a TKLM Server Connection Test to check connectivity to server {1}. | Informational |
| FQXSPNM4050I | User {0} has initiated an SMTP Server Connection Test. | Informational |
| FQXSPNM4051I | User {0} has set the SMTP Server reverse-path to {1}. | Informational |
| FQXSPNM4052I | DHCP specified hostname is set to {0} by user {1}. | Informational |
| FQXSPNM4053I | DNS discovery of Lenovo XClarity Administrator has been {0} by user {1}. | Informational |
| FQXSPNM4054I | The hostname from DHCP is {0} by user {1}. | Informational |
| FQXSPNM4055I | The hostname from DHCP is invalid. | Informational |
| FQXSPNM4056I | The NTP server address {0} is invalid. | Informational |
| FQXSPNM4057I | Security: IP address: {0} had {1} login failures, it will be blocked to access for {2} minutes. | Informational |
| FQXSPOS4000I | OS Watchdog response {0} by {1}. | Informational |
| FQXSPOS4001I | Watchdog {0} Screen Capture Occurred. | Informational |
| FQXSPOS4002I | Watchdog {0} Failed to Capture Screen. | Informational |
| FQXSPOS4003I | Platform Watchdog Timer expired for {0}. | Informational |
| FQXSPOS4004I | Operating System status has changed to {0}. | Informational |
| FQXSPOS4005I | Host Power-On password changed. | Informational |
| FQXSPOS4006I | Host Power-On password cleared. | Informational |
| FQXSPOS4007I | Host Admin password changed. | Informational |
| FQXSPOS4008I | Host Admin password cleared. | Informational |
| FQXSPOS4009I | OS Crash Video Captured. | Informational |
| FQXSPOS4010I | OS Crash Video Capture Failed. | Informational |
| FQXSPPP4000I | Attempting to {0} server {1} by user {2}. | Informational |
| FQXSPPP4001I | Server Power Off Delay set to {0} by user {1}. | Informational |
| FQXSPPP4002I | Server {0} scheduled for {1} at {2} by user {3}. | Informational |
| FQXSPPP4003I | Server {0} scheduled for every {1} at {2} by user {3}. | Informational |
| FQXSPPP4004I | Server {0} {1} cleared by user {2}. | Informational |
| FQXSPPP4005I | The power cap value changed from {0} watts to {1} watts by user {2}. | Informational |
| FQXSPPP4006I | The minimum power cap value changed from {0} watts to {1} watts. | Informational |
| FQXSPPP4007I | The maximum power cap value changed from {0} watts to {1} watts. | Informational |
| FQXSPPP4008I | The soft minimum power cap value changed from {0} watts to {1} watts. | Informational |
| FQXSPPP4009I | The measured power value exceeded the power cap value. | Informational |
| FQXSPPP4010I | The new minimum power cap value exceeded the power cap value. | Informational |
| FQXSPPP4011I | Power capping was activated by user {0}. | Informational |
| FQXSPPP4012I | Power capping was deactivated by user {0}. | Informational |
| FQXSPPP4013I | Static Power Savings mode has been turned on by user {0}. | Informational |
| FQXSPPP4014I | Static Power Savings mode has been turned off by user {0}. | Informational |
| FQXSPPP4015I | Dynamic Power Savings mode has been turned on by user {0}. | Informational |
| FQXSPPP4016I | Dynamic Power Savings mode has been turned off by user {0}. | Informational |
| FQXSPPP4017I | Power cap and external throttling occurred. | Informational |
| FQXSPPP4018I | External throttling occurred. | Informational |
| FQXSPPP4019I | Power cap throttling occurred. | Informational |
| FQXSPPP4020I | The measured power value has returned below the power cap value. | Informational |
| FQXSPPP4021I | The new minimum power cap value has returned below the power cap value. | Informational |
| FQXSPPP4022I | The server was restarted for an unknown reason. | Informational |
| FQXSPPP4023I | The server is restarted by chassis control command. | Informational |
| FQXSPPP4024I | The server was reset via pushbutton. | Informational |
| FQXSPPP4025I | The server was powered-up via power pushbutton. | Informational |
| FQXSPPP4026I | The server was restarted when the watchdog expired.. | Informational |
| FQXSPPP4027I | The server was restarted for OEM reason. | Informational |
| FQXSPPP4028I | The server was automatically powered on because the power restore policy is set to always restore.. | Informational |
| FQXSPPP4029I | The server was automatically powered on because the power restore policy is set to restore previous power state.. | Informational |
| FQXSPPP4030I | The server was reset via Platform Event Filter. | Informational |
| FQXSPPP4031I | The server was power-cycled via Platform Event Filter. | Informational |
| FQXSPPP4032I | The server was soft reset. | Informational |
| FQXSPPP4033I | The server was powered up via Real Time Clock (scheduled power on). | Informational |
| FQXSPPP4034I | The server was powered off for an unknown reason. | Informational |
| FQXSPPP4035I | The server was powered off by chassis control command. | Informational |
| FQXSPPP4036I | The server was powered off via pushbutton. | Informational |
| FQXSPPP4037I | The server was powered off when the watchdog expired. | Informational |
| FQXSPPP4038I | The server stayed powered off because the power restore policy is set to always restore.. | Informational |
| FQXSPPP4039I | The server stayed powered off because the power restore policy is set to restore previous power state.. | Informational |
| FQXSPPP4040I | The server was powered off via Platform Event Filter. | Informational |
| FQXSPPP4041I | The server was powered off via Real Time Clock (scheduled power off). | Informational |
| FQXSPPP4042I | Management Controller {0} reset was initiated due to Power-On-Reset. | Informational |
| FQXSPPP4043I | Management Controller {0} reset was initiated by PRESET. | Informational |
| FQXSPPP4044I | Management Controller {0} reset was initiated by CMM. | Informational |
| FQXSPPP4045I | Management Controller {0} reset was initiated by XCC firmware. | Informational |
| FQXSPPP4046I | Remote power permission is {0}. | Informational |
| FQXSPPP4047I | Management Controller {0} reset was initiated by user {1}. | Informational |
| FQXSPPP4048I | Attempting to AC power cycle server {0} by user {1}. | Informational |
| FQXSPPP4049I | Management Controller {0} reset was initiated by Front Panel. | Informational |
| FQXSPPR0000I | {0} detected as present. | Informational |
| FQXSPPR0001I | {0} detected as absent. | Informational |
| FQXSPPR0002I | {0} has been disabled. | Informational |
| FQXSPPR2000I | {0} detected as present. | Informational |
| FQXSPPR2001I | {0} detected as absent. | Informational |
| FQXSPPR2002I | {0} has been enabled. | Informational |
| FQXSPPU0000I | {0} in slot {1} has been added. | Informational |
| FQXSPPU0008I | {0} has been Disabled. | Informational |
| FQXSPPU0010I | A terminator has been detected on {0}. | Informational |
| FQXSPPU2000I | {0} in slot {1} has been removed. | Informational |
| FQXSPPU2001I | An Over-Temperature Condition has been removed on {0}. | Informational |
| FQXSPPU2002I | The Processor {0} is no longer operating in a Degraded State. | Informational |
| FQXSPPU2003I | {0} has Recovered from IERR. | Informational |
| FQXSPPU2004I | {0} has Recovered from FRB1/BIST condition. | Informational |
| FQXSPPU2005I | {0} has Recovered from FRB2/POST condition. | Informational |
| FQXSPPU2006I | {0} has Recovered from FRB3 condition. | Informational |
| FQXSPPU2007I | The System {0} has detected a POST Error deassertion. | Informational |
| FQXSPPU2008I | {0} has been Enabled. | Informational |
| FQXSPPU2009I | {0} has Recovered from a Configuration Mismatch. | Informational |
| FQXSPPU2011I | An SM BIOS Uncorrectable CPU complex error for {0} has deasserted. | Informational |
| FQXSPPW0001I | Power supply {0} in the enclosure (MTM-SN: {1})has been added. | Informational |
| FQXSPPW0002I | Power supply {0} in the enclosure (MTM-SN: {1})has been added. | Informational |
| FQXSPPW0004I | The input to {0} has been lost or fallen out of range. | Informational |
| FQXSPPW0005I | {0} is operating in an Input State that is out of range. | Informational |
| FQXSPPW0006I | Power supply {0} in the enclosure (MTM-SN: {1})has lost input. | Informational |
| FQXSPPW0007I | Power supply {0} in the enclosure (MTM-SN: {1})has lost input. | Informational |
| FQXSPPW0008I | {0} has been turned off. | Informational |
| FQXSPPW0009I | {0} has been Power Cycled. | Informational |
| FQXSPPW0010I | {0} has encountered an error during power down. | Informational |
| FQXSPPW0011I | {0} has lost power. | Informational |
| FQXSPPW0015I | Power On for system {0}. | Informational |
| FQXSPPW0017I | Computer System {0} Enabled. | Informational |
| FQXSPPW0018I | Computer System {0} is in Sleep - light mode. | Informational |
| FQXSPPW0019I | Computer System {0} is in Sleep - light mode. | Informational |
| FQXSPPW0020I | Computer System {0} is in Hibernate. | Informational |
| FQXSPPW0021I | Computer System {0} is in Standby. | Informational |
| FQXSPPW0022I | Computer System {0} is in soft - off mode. | Informational |
| FQXSPPW0023I | Computer System {0} is in hard - off mode. | Informational |
| FQXSPPW0024I | Computer System {0} is sleeping. | Informational |
| FQXSPPW0026I | The Battery {0} has been added. | Informational |
| FQXSPPW0052I | Sensor {0} has transitioned to normal state. | Informational |
| FQXSPPW0053I | Sensor {0} has transitioned to normal state. | Informational |
| FQXSPPW0054I | Sensor {0} has transitioned to normal state. | Informational |
| FQXSPPW0055I | Sensor {0} has transitioned to normal state. | Informational |
| FQXSPPW0068I | Sensor {0} has transitioned to non-critical from a more severe state. | Informational |
| FQXSPPW0069I | Sensor {0} has transitioned to non-critical from a more severe state. | Informational |
| FQXSPPW0070I | Sensor {0} has transitioned to non-critical from a more severe state. | Informational |
| FQXSPPW0071I | Sensor {0} has transitioned to non-critical from a more severe state. | Informational |
| FQXSPPW0080I | Sensor {0} indicates a monitor state. | Informational |
| FQXSPPW0081I | Sensor {0} indicates a monitor state. | Informational |
| FQXSPPW0082I | Sensor {0} indicates a monitor state. | Informational |
| FQXSPPW0083I | Sensor {0} indicates a monitor state. | Informational |
| FQXSPPW0084I | Sensor {0} has an informational state. | Informational |
| FQXSPPW0085I | Sensor {0} has an informational state. | Informational |
| FQXSPPW0086I | Sensor {0} has an informational state. | Informational |
| FQXSPPW0087I | Sensor {0} has an informational state. | Informational |
| FQXSPPW0089I | Redundancy {0} has been restored. | Informational |
| FQXSPPW0090I | Redundancy {0} has been restored. | Informational |
| FQXSPPW0091I | Redundancy {0} has been restored. | Informational |
| FQXSPPW0092I | {0} has transitioned to a D0 power state. | Informational |
| FQXSPPW0093I | {0} has transitioned to a D1 power state. | Informational |
| FQXSPPW0094I | {0} has transitioned to a D2 power state. | Informational |
| FQXSPPW0095I | {0} has transitioned to a D3 power state. | Informational |
| FQXSPPW2001I | Power supply {0} in the enclosure (MTM-SN: {1})has been removed. | Informational |
| FQXSPPW2002I | Power supply {0} in the enclosure (MTM-SN: {1})has returned to OK status. | Informational |
| FQXSPPW2003I | Failure no longer predicted on {0}. | Informational |
| FQXSPPW2004I | {0} has returned to a Normal Input State. | Informational |
| FQXSPPW2005I | {0} has returned to a Normal Input State. | Informational |
| FQXSPPW2006I | {0} has returned to a Normal Input State. | Informational |
| FQXSPPW2007I | {0} Configuration is OK. | Informational |
| FQXSPPW2008I | {0} has been turned on. | Informational |
| FQXSPPW2009I | Power supply {0} in the enclosure (MTM-SN: {1})has been removed. | Informational |
| FQXSPPW2010I | {0} has recovered from an error during power down. | Informational |
| FQXSPPW2011I | {0} power was restored. | Informational |
| FQXSPPW2012I | Soft power control working for {0}. | Informational |
| FQXSPPW2013I | {0} has Recovered | Informational |
| FQXSPPW2014I | Failure no longer predicted on {0}. | Informational |
| FQXSPPW2015I | Power supply {0} in the enclosure (MTM-SN: {1})has returned to OK status. | Informational |
| FQXSPPW2016I | Power Control of System {0} has recovered. | Informational |
| FQXSPPW2017I | {0} has returned to a Normal Input State. | Informational |
| FQXSPPW2025I | The Battery {0} is no longer critically low. | Informational |
| FQXSPPW2026I | The Battery {0} has been removed from unit {1}. | Informational |
| FQXSPPW2027I | The Battery {0} has recovered. | Informational |
| FQXSPPW2028I | Numeric sensor {0} going low (lower non-critical) has deasserted. | Informational |
| FQXSPPW2029I | Numeric sensor {0} going low (lower non-critical) has deasserted. | Informational |
| FQXSPPW2030I | Numeric sensor {0} going low (lower non-critical) has deasserted. | Informational |
| FQXSPPW2031I | Numeric sensor {0} going low (lower non-critical) has deasserted. | Informational |
| FQXSPPW2032I | Numeric sensor {0} going low (lower critical) has deasserted. | Informational |
| FQXSPPW2033I | Numeric sensor {0} going low (lower critical) has deasserted. | Informational |
| FQXSPPW2034I | Numeric sensor {0} going low (lower critical) has deasserted. | Informational |
| FQXSPPW2035I | Numeric sensor {0} going low (lower critical) has deasserted. | Informational |
| FQXSPPW2036I | Numeric sensor {0} going low (lower non-recoverable) has deasserted. | Informational |
| FQXSPPW2037I | Numeric sensor {0} going low (lower non-recoverable) has deasserted. | Informational |
| FQXSPPW2038I | Numeric sensor {0} going low (lower non-recoverable) has deasserted. | Informational |
| FQXSPPW2039I | Numeric sensor {0} going low (lower non-recoverable) has deasserted. | Informational |
| FQXSPPW2040I | Numeric sensor {0} going high (upper non-critical) has deasserted. | Informational |
| FQXSPPW2041I | Numeric sensor {0} going high (upper non-critical) has deasserted. | Informational |
| FQXSPPW2042I | Numeric sensor {0} going high (upper non-critical) has deasserted. | Informational |
| FQXSPPW2043I | Numeric sensor {0} going high (upper non-critical) has deasserted. | Informational |
| FQXSPPW2044I | Numeric sensor {0} going high (upper critical) has deasserted. | Informational |
| FQXSPPW2045I | Numeric sensor {0} going high (upper critical) has deasserted. | Informational |
| FQXSPPW2046I | Numeric sensor {0} going high (upper critical) has deasserted. | Informational |
| FQXSPPW2047I | Numeric sensor {0} going high (upper critical) has deasserted. | Informational |
| FQXSPPW2048I | Numeric sensor {0} going high (upper non-recoverable) has deasserted. | Informational |
| FQXSPPW2049I | Numeric sensor {0} going high (upper non-recoverable) has deasserted. | Informational |
| FQXSPPW2050I | Numeric sensor {0} going high (upper non-recoverable) has deasserted. | Informational |
| FQXSPPW2051I | Numeric sensor {0} going high (upper non-recoverable) has deasserted. | Informational |
| FQXSPPW2056I | Sensor {0} has deasserted the transition from normal to non-critical state. | Informational |
| FQXSPPW2057I | Sensor {0} has deasserted the transition from normal to non-critical state. | Informational |
| FQXSPPW2058I | Sensor {0} has deasserted the transition from normal to non-critical state. | Informational |
| FQXSPPW2059I | Sensor {0} has deasserted the transition from normal to non-critical state. | Informational |
| FQXSPPW2060I | Sensor {0} has transitioned to a less severe state from critical. | Informational |
| FQXSPPW2061I | Sensor {0} has transitioned to a less severe state from critical. | Informational |
| FQXSPPW2062I | Sensor {0} has transitioned to a less severe state from critical. | Informational |
| FQXSPPW2063I | Sensor {0} has transitioned to a less severe state from critical. | Informational |
| FQXSPPW2064I | Sensor {0} has deasserted the transition to non-recoverable from a less severe state. | Informational |
| FQXSPPW2065I | Sensor {0} has deasserted the transition to non-recoverable from a less severe state. | Informational |
| FQXSPPW2066I | Sensor {0} has deasserted the transition to non-recoverable from a less severe state. | Informational |
| FQXSPPW2067I | Sensor {0} has deasserted the transition to non-recoverable from a less severe state. | Informational |
| FQXSPPW2076I | Sensor {0} has deasserted the transition to non-recoverable. | Informational |
| FQXSPPW2077I | Sensor {0} has deasserted the transition to non-recoverable. | Informational |
| FQXSPPW2078I | Sensor {0} has deasserted the transition to non-recoverable. | Informational |
| FQXSPPW2079I | Sensor {0} has deasserted the transition to non-recoverable. | Informational |
| FQXSPPW2096I | Redundancy Lost for {0} has deasserted. | Informational |
| FQXSPPW2097I | Redundancy Lost for {0} has deasserted. | Informational |
| FQXSPPW2098I | Redundancy Lost for {0} has deasserted. | Informational |
| FQXSPPW2099I | Redundancy Degraded for {0} has deasserted. | Informational |
| FQXSPPW2100I | Redundancy Degraded for {0} has deasserted. | Informational |
| FQXSPPW2101I | Redundancy Degraded for {0} has deasserted. | Informational |
| FQXSPPW2102I | Non-redundant:Sufficient Resources from Redundancy Degraded or Fully Redundant for {0} has deasserted. | Informational |
| FQXSPPW2103I | Non-redundant:Sufficient Resources from Redundancy Degraded or Fully Redundant for {0} has deasserted. | Informational |
| FQXSPPW2104I | Non-redundant:Sufficient Resources from Redundancy Degraded or Fully Redundant for {0} has deasserted. | Informational |
| FQXSPPW2105I | Non-redundant:Sufficient Resources from Insufficient Resources for {0} has deasserted. | Informational |
| FQXSPPW2106I | Non-redundant:Sufficient Resources from Insufficient Resources for {0} has deasserted. | Informational |
| FQXSPPW2107I | Non-redundant:Sufficient Resources from Insufficient Resources for {0} has deasserted. | Informational |
| FQXSPPW2108I | Non-redundant:Insufficient Resources for {0} has deasserted. | Informational |
| FQXSPPW2109I | Non-redundant:Insufficient Resources for {0} has deasserted. | Informational |
| FQXSPPW2110I | Non-redundant:Insufficient Resources for {0} has deasserted. | Informational |
| FQXSPPW2111I | Redundancy Degraded from Fully Redundant for {0} has deasserted. | Informational |
| FQXSPPW2112I | Redundancy Degraded from Fully Redundant for {0} has deasserted. | Informational |
| FQXSPPW2113I | Redundancy Degraded from Fully Redundant for {0} has deasserted. | Informational |
| FQXSPPW2114I | Redundancy Degraded from Non-redundant for {0} has deasserted. | Informational |
| FQXSPPW2115I | Redundancy Degraded from Non-redundant for {0} has deasserted. | Informational |
| FQXSPPW2116I | Redundancy Degraded from Non-redundant for {0} has deasserted. | Informational |
| FQXSPPW4001I | PCIe Power Brake for {0} has been {1}. | Informational |
| FQXSPSB2000I | The System {0} has detected a POST Error deassertion. | Informational |
| FQXSPSD0000I | The {0} has been added. | Informational |
| FQXSPSD0001I | The {0} has been added. | Informational |
| FQXSPSD0003I | Hot Spare enabled for drive {0} in the enclosure (MTM-SN: {1}). | Informational |
| FQXSPSD0004I | Consistency check has begun for {0}. | Informational |
| FQXSPSD0005I | Hot Spare enabled for drive {0} in the enclosure (MTM-SN: {1}). | Informational |
| FQXSPSD0007I | Array rebuild in progress on drive {0} in the enclosure (MTM-S/N: {1}). | Informational |
| FQXSPSD0008I | Array rebuild in progress on drive {0} in the enclosure (MTM-S/N: {1}). | Informational |
| FQXSPSD2000I | Drive {0} in the enclosure(MTM-SN: {1}) has been removed. | Informational |
| FQXSPSD2001I | Drive {0} in the enclosure(MTM-SN: {1}) has been enabled. | Informational |
| FQXSPSD2002I | Failure no longer Predicted on drive {0} in the enclosure (MTM-S/N: {1}). | Informational |
| FQXSPSD2003I | Hot Spare disabled for drive {0} in the enclosure (MTM-SN: {1}). | Informational |
| FQXSPSD2004I | Consistency check completed for {0}. | Informational |
| FQXSPSD2005I | Array critical deasserted on drive {0} in the enclosure (MTM-S/N: {1}). | Informational |
| FQXSPSD2006I | Array restored on drive {0} in the enclosure (MTM-S/N: {1}). | Informational |
| FQXSPSD2007I | Array rebuild completed on drive {0} in the enclosure (MTM-S/N: {1}). | Informational |
| FQXSPSD2008I | Drive {0} in the enclosure(MTM-SN: {1}) has been enabled. | Informational |
| FQXSPSD2009I | The System {0} has detected a POST Error deassertion. | Informational |
| FQXSPSD2010I | Drive {0} in the enclosure(MTM-SN: {1}) has been removed. | Informational |
| FQXSPSD2011I | Failure no longer Predicted on drive {0} in the enclosure (MTM-S/N: {1}). | Informational |
| FQXSPSD2012I | Hot Spare disabled for drive {0} in the enclosure (MTM-SN: {1}). | Informational |
| FQXSPSD2013I | Array critical deasserted on drive {0} in the enclosure (MTM-S/N: {1}). | Informational |
| FQXSPSD2014I | Array restored on drive {0} in the enclosure (MTM-S/N: {1}). | Informational |
| FQXSPSD2015I | Array rebuild completed on drive {0} in the enclosure (MTM-S/N: {1}). | Informational |
| FQXSPSD2016I | Sensor {0} has deasserted. | Informational |
| FQXSPSE0001I | The Computer System {0} has detected a secure mode violation. | Informational |
| FQXSPSE0002I | The Computer System {0} has detected a pre-boot user password violation. | Informational |
| FQXSPSE0003I | The Computer System {0} has detected a pre-boot setup password violation. | Informational |
| FQXSPSE0004I | The Computer System {0} has detected a network boot password violation. | Informational |
| FQXSPSE0005I | The Computer System {0} has detected a password violation for user {1}. | Informational |
| FQXSPSE0006I | The management controller {0} has detected an out-of-band password violation for system {0}. | Informational |
| FQXSPSE2000I | The Chassis {0} was closed. | Informational |
| FQXSPSE4000I | Certificate Authority {0} has detected a {1} Certificate Error. | Informational |
| FQXSPSE4001I | Remote Login Successful. Login ID: {0} using {1} from {2} at IP address {3}. | Informational |
| FQXSPSE4002I | Security: Userid: {0} using {1} had {2} login failures from WEB client at IP address {3}. | Informational |
| FQXSPSE4003I | Security: Login ID: {0} had {1} login failures from CLI at {2}. | Informational |
| FQXSPSE4004I | Remote access attempt failed. Invalid userid or password received. Userid is {0} from WEB browser at IP address {1}. | Informational |
| FQXSPSE4005I | Remote access attempt failed. Invalid userid or password received. Userid is {0} from TELNET client at IP address {1}. | Informational |
| FQXSPSE4006I | SSL data in the Management Controller {0} configuruation data is invalid. Clearing configuration data region and disabling SSL. | Informational |
| FQXSPSE4007I | Security: Userid: {0} using {1} had {2} login failures from an SSH client at IP address {3}. | Informational |
| FQXSPSE4008I | SNMPv1 {0} set by user {1}: Name={2}, AccessType={3}, Address={4},. | Informational |
| FQXSPSE4009I | LDAP Server configuration set by user {0}: SelectionMethod={1}, DomainName={2}, Server1={3}, Server2={4}, Server3={5}, Server4={6}. | Informational |
| FQXSPSE4010I | LDAP set by user {0}: RootDN={1}, UIDSearchAttribute={2}, BindingMethod={3}, EnhancedRBS={4}, TargetName={5}, GroupFilter={6}, GroupAttribute={7}, LoginAttribute={8}. | Informational |
| FQXSPSE4011I | Secure Web services (HTTPS) {0} by user {1}. | Informational |
| FQXSPSE4012I | Secure CIM/XML(HTTPS) {0} by user {1}. | Informational |
| FQXSPSE4013I | Secure LDAP {0} by user {1}. | Informational |
| FQXSPSE4014I | SSH {0} by user {1}. | Informational |
| FQXSPSE4015I | Global Login General Settings set by user {0}: AuthenticationMethod={1}, LockoutPeriod={2}, SessionTimeout={3}. | Informational |
| FQXSPSE4016I | Global Login Account Security set by user {0}: PasswordRequired={1}, PasswordExpirationPeriod={2}, MinimumPasswordReuseCycle={3}, MinimumPasswordLength={4}, MinimumPasswordChangeInterval={5}, MaxmumLoginFailures={6}, LockoutAfterMaxFailures={7}. | Informational |
| FQXSPSE4017I | User {0} created. | Informational |
| FQXSPSE4018I | User {0} removed. | Informational |
| FQXSPSE4019I | User {0} password modified. | Informational |
| FQXSPSE4020I | User {0} role set to {1}. | Informational |
| FQXSPSE4021I | User {0} custom privileges set: {1}{2}{3}{4}{5}{6}{7}. | Informational |
| FQXSPSE4022I | User {0} for SNMPv3 set: AuthenticationProtocol={1}, PrivacyProtocol={2}, AccessType={3}, HostforTraps={4}. | Informational |
| FQXSPSE4023I | SSH Client key added for user {0}. | Informational |
| FQXSPSE4024I | SSH Client key imported for user {0} from {1}. | Informational |
| FQXSPSE4025I | SSH Client key removed from user {0}. | Informational |
| FQXSPSE4026I | Security: Userid: {0} had {1} login failures from a CIM client at IP address {2}. | Informational |
| FQXSPSE4027I | Remote access attempt failed. Invalid userid or password received. Userid is {0} from a CIM client at IP address {1}. | Informational |
| FQXSPSE4028I | Security: Userid: {0} had {1} login failures from IPMI client at IP address {2}. | Informational |
| FQXSPSE4029I | Security: Userid: {0} had {1} login failures from SNMP client at IP address {2}. | Informational |
| FQXSPSE4030I | Security: Userid: {0} had {1} login failures from IPMI serial client. | Informational |
| FQXSPSE4031I | Remote Login Successful. Login ID: {0} from {1} serial interface. | Informational |
| FQXSPSE4032I | Login ID: {0} from {1} at IP address {2} has logged off. | Informational |
| FQXSPSE4033I | Login ID: {0} from {1} at IP address {2} has been logged off. | Informational |
| FQXSPSE4034I | User {0} has removed a certificate. | Informational |
| FQXSPSE4035I | A certificate has been revoked. | Informational |
| FQXSPSE4036I | The {0} certificate is expired and has been removed. | Informational |
| FQXSPSE4037I | Crypto mode modified from {0} to {1} by user {2}. | Informational |
| FQXSPSE4038I | Minimum TLS level modified from {0} to {1} by user {2}. | Informational |
| FQXSPSE4039I | Temporary user account {0} is created by inband tool. | Informational |
| FQXSPSE4040I | Temporary user account {0} expires. | Informational |
| FQXSPSE4041I | Security: Userid: {0} had {1} login failures from a SFTP client at IP address {2}. | Informational |
| FQXSPSE4042I | The third-party password function {0}. | Informational |
| FQXSPSE4043I | Retrieving the third-party password {0}. | Informational |
| FQXSPSE4044I | User {0} third-party hashed password has been {1}. | Informational |
| FQXSPSE4045I | The Salt of user {0} third-party password has been {1}. | Informational |
| FQXSPSE4046I | The third-party password of the user {0} has been retrieved. | Informational |
| FQXSPSE4047I | Role {0} is {1} and assigned with custom privileges {2}{3}{4}{5}{6}{7}{8}{0}0]{0}1] by user {0}2]. | Informational |
| FQXSPSE4048I | Role {0} is removed by user {1}. | Informational |
| FQXSPSE4049I | Role {0} is assigned to user {1} by user {2}. | Informational |
| FQXSPSE4050I | {0} sent IPMI command from {1}, raw data: {2}{3}{4}. | Informational |
| FQXSPSR2001I | Sensor {0} has deasserted the transition to non-recoverable from a less severe state. | Informational |
| FQXSPSS4000I | Management Controller Test Alert Generated by {0}. | Informational |
| FQXSPSS4001I | Server General Settings set by user {0}: Name={1}, Contact={2}, Location={3}, Room={4}, RackID={5}, Rack U-position={6}, Address={7}. | Informational |
| FQXSPSS4002I | License key for {0} added by user {1}. | Informational |
| FQXSPSS4003I | License key for {0} removed by user {1}. | Informational |
| FQXSPSS4004I | Test Call Home Generated by user {0}. | Informational |
| FQXSPSS4005I | Manual Call Home by user {0}: {1}. | Informational |
| FQXSPSS4006I | Call Home to {0} failed to complete: {1}. | Informational |
| FQXSPSS4007I | The BMC functionality tier is changed from {0} to {1}. | Informational |
| FQXSPSS4008I | The {0} setting has been changed to {1} by user {2}. | Informational |
| FQXSPSS4009I | System enters LXPM maintenance mode. | Informational |
| FQXSPSS4010I | Test Audit Log generated by user {0}. | Informational |
| FQXSPTR4000I | Management Controller {0} clock has been set from NTP server {1}. | Informational |
| FQXSPTR4001I | Date and Time set by user {0}: Date={1}, Time-{2}, DST Auto-adjust={3}, Timezone={4}. | Informational |
| FQXSPTR4002I | Synchronize time setting by user {0}: Mode=Sync with NTP Server, NTPServerHost1={1}:{2},NTPServerHost2={3}:{4},NTPServerHost3={5}:{6},NTPServerHost4={7}:{8},NTPUpdateFrequency={0}0]. | Informational |
| FQXSPTR4003I | Synchronize time setting by user {0}: Mode=Sync with server clock. | Informational |
| FQXSPUN0006I | Sensor {0} has transitioned to idle. | Informational |
| FQXSPUN0007I | Sensor {0} has transitioned to active. | Informational |
| FQXSPUN0008I | Sensor {0} has transitioned to busy. | Informational |
| FQXSPUN0009I | Sensor {0} has asserted. | Informational |
| FQXSPUN0010I | Sensor {0} has deasserted. | Informational |
| FQXSPUN0012I | Sensor {0} is deasserting predictive failure. | Informational |
| FQXSPUN0013I | Sensor {0} has indicated limit exceeded. | Informational |
| FQXSPUN0014I | Sensor {0} has indicated limit no longer exceeded. | Informational |
| FQXSPUN0015I | Sensor {0} has indicated performance met. | Informational |
| FQXSPUN0016I | Sensor {0} has indicated performance lags. | Informational |
| FQXSPUN0017I | Sensor {0} has transitioned to normal state. | Informational |
| FQXSPUN0021I | Sensor {0} has transitioned to non-critical from a more severe state. | Informational |
| FQXSPUN0024I | Sensor {0} indicates a monitor state. | Informational |
| FQXSPUN0025I | Sensor {0} has an informational state. | Informational |
| FQXSPUN0026I | Device {0} has been added. | Informational |
| FQXSPUN0027I | Device {0} has been removed from unit {1}. | Informational |
| FQXSPUN0028I | Device {0} has been enabled. | Informational |
| FQXSPUN0029I | Device {0} has been disabled. | Informational |
| FQXSPUN0030I | Sensor {0} has indicated a running state. | Informational |
| FQXSPUN0031I | Sensor {0} has indicated an in-test state. | Informational |
| FQXSPUN0032I | Sensor {0} has indicated a power off state. | Informational |
| FQXSPUN0033I | Sensor {0} has indicated a on-line state. | Informational |
| FQXSPUN0034I | Sensor {0} has indicated an off-line state. | Informational |
| FQXSPUN0035I | Sensor {0} has indicated an off-duty state. | Informational |
| FQXSPUN0036I | Sensor {0} has indicated a degraded state. | Informational |
| FQXSPUN0037I | Sensor {0} has indicated a power save state. | Informational |
| FQXSPUN0039I | Redundancy {0} has been restored. | Informational |
| FQXSPUN0048I | Sensor {0} has transitioned to normal state. | Informational |
| FQXSPUN0056I | Sensor {0} has deasserted. | Informational |
| FQXSPUN2000I | Numeric sensor {0} going low (lower non-critical) has deasserted. | Informational |
| FQXSPUN2001I | Numeric sensor {0} going low (lower critical) has deasserted. | Informational |
| FQXSPUN2002I | Numeric sensor {0} going low (lower non-recoverable) has deasserted. | Informational |
| FQXSPUN2003I | Numeric sensor {0} going high (upper non-critical) has deasserted. | Informational |
| FQXSPUN2004I | Numeric sensor {0} going high (upper critical) has deasserted. | Informational |
| FQXSPUN2005I | Numeric sensor {0} going high (upper non-recoverable) has deasserted. | Informational |
| FQXSPUN2009I | Sensor {0} has deasserted. | Informational |
| FQXSPUN2010I | Sensor {0} has asserted. | Informational |
| FQXSPUN2011I | Sensor {0} is deasserting predictive failure. | Informational |
| FQXSPUN2012I | Sensor {0} has deasserted. | Informational |
| FQXSPUN2013I | Sensor {0} has indicated limit no longer exceeded. | Informational |
| FQXSPUN2014I | Sensor {0} has indicated limit exceeded. | Informational |
| FQXSPUN2015I | Sensor {0} has indicated performance lags. | Informational |
| FQXSPUN2016I | Sensor {0} has indicated performance met. | Informational |
| FQXSPUN2018I | Sensor {0} has deasserted the transition from normal to non-critical state. | Informational |
| FQXSPUN2019I | Sensor {0} has transitioned to a less severe state from critical. | Informational |
| FQXSPUN2020I | Sensor {0} has deasserted the transition to non-recoverable from a less severe state. | Informational |
| FQXSPUN2023I | Sensor {0} has deasserted the transition to non-recoverable. | Informational |
| FQXSPUN2026I | Device {0} has been removed from unit {1}. | Informational |
| FQXSPUN2027I | Device {0} has been added. | Informational |
| FQXSPUN2028I | Device {0} has been disabled. | Informational |
| FQXSPUN2029I | Device {0} has been enabled. | Informational |
| FQXSPUN2030I | Device {0} has been removed from unit {1}. | Informational |
| FQXSPUN2038I | Sensor {0} has recovered from an install error. | Informational |
| FQXSPUN2040I | Redundancy Lost for {0} has deasserted. | Informational |
| FQXSPUN2041I | Redundancy Degraded for {0} has deasserted. | Informational |
| FQXSPUN2042I | Non-redundant:Sufficient Resources from Redundancy Degraded or Fully Redundant for {0} has deasserted. | Informational |
| FQXSPUN2043I | Non-redundant:Sufficient Resources from Insufficient Resources for {0} has deasserted. | Informational |
| FQXSPUN2044I | Non-redundant:Insufficient Resources for {0} has deasserted. | Informational |
| FQXSPUN2045I | Redundancy Degraded from Fully Redundant for {0} has deasserted. | Informational |
| FQXSPUN2046I | Redundancy Degraded from Non-redundant for {0} has deasserted. | Informational |
| FQXSPUN2047I | Sensor {0} has deasserted the transition to non-recoverable. | Informational |
| FQXSPUN2049I | Sensor {0} has deasserted the transition from normal to non-critical state. | Informational |
| FQXSPUN2050I | Sensor {0} has transitioned to a less severe state from critical. | Informational |
| FQXSPUP0000I | A hardware change occurred on system {0}. | Informational |
| FQXSPUP0001I | A firmware or software change occurred on system {0}. | Informational |
| FQXSPUP0002I | A firmware or software change occurred on system {0}. | Informational |
| FQXSPUP0003I | A firmware or software change occurred on system {0}. | Informational |
| FQXSPUP0008I | A successful hardware change was detected on system {0}. | Informational |
| FQXSPUP0009I | A successful software or firmware change was detected on system {0}. | Informational |
| FQXSPUP2004I | The hardware on system {0} is compatible. | Informational |
| FQXSPUP2005I | The firmware or software on system {0} are compatible. | Informational |
| FQXSPUP2006I | Valid and Supported hardware was detected on system {0}. | Informational |
| FQXSPUP2007I | Valid and Supported firmware or software was detected on system {0}. | Informational |
| FQXSPUP4000I | Please ensure that the Management Controller {0} is flashed with the correct firmware. The Management Controller is unable to match its firmware to the server. | Informational |
| FQXSPUP4001I | Flash of {0} from {1} succeeded for user {2}. | Informational |
| FQXSPUP4002I | Flash of {0} from {1} failed for user {2}. | Informational |
| FQXSPUP4003I | {0} firmware mismatch internal to system {1}. Please attempt to flash the {2} firmware. | Informational |
| FQXSPUP4004I | XCC firmware mismatch between nodes {0} and {1}. Please attempt to flash the XCC firmware to the same level on all nodes. | Informational |
| FQXSPUP4005I | FPGA firmware mismatch between nodes {0} and {1}. Please attempt to flash the FPGA firmware to the same level on all nodes. | Informational |
| FQXSPWD0000I | Watchdog Timer expired for {0}. | Informational |
| FQXSPWD0001I | Reboot of system {0} initiated by watchdog {1}. | Informational |
| FQXSPWD0002I | Powering off system {0} initiated by watchdog {1}. | Informational |
| FQXSPWD0003I | Power cycle of system {0} initiated by watchdog {1}. | Informational |
| FQXSPWD0004I | Watchdog Timer interrupt occurred for {0}. | Informational |
| FQXHMCP1115J | Pattern {0} failed to deploy on {1}. | Warning |
| FQXHMCP1155J | Profile {0} could not be redeployed to {1}. | Warning |
| FQXHMCP1175J | Profile {0} could not be unassigned from {1}. | Warning |
| FQXHMCP1180J | Server configuration profile {0} is non-compliant. | Warning |
| FQXHMCP1185J | Server configuration profile {0} is non-compliant. | Warning |
| FQXHMCP1190J | The server configuration non-compliant alert was deserted for profile {0}. | Warning |
| FQXHMCP1275J | Standby pool {0} has no servers available for failover. | Warning |
| FQXHMCP1315J | Local storage could not be reset to the default configuration. | Warning |
| FQXHMCP5105J | Pattern name {0} is already in use. | Warning |
| FQXHMCP5125J | Pattern {0} was not found. | Warning |
| FQXHMCP5305J | Address pool name {0} is already in use. | Warning |
| FQXHMCP5325J | Address pool {0} was not found. | Warning |
| FQXHMCP5405J | Standby pool name {0} is already in use. | Warning |
| FQXHMCP5425J | Standby pool {0} was not found. | Warning |
| FQXHMCP5505J | Placeholder chassis name {0} is already in use. | Warning |
| FQXHMCP5525J | Placeholder chassis {0} was not found. | Warning |
| FQXHMCP5605J | Policy name {0} is already in use. | Warning |
| FQXHMCP5625J | Policy {0} was not found. | Warning |
| FQXHMCR0103J | Call home service is unavailable for the moment due to a loss of connectivity | Warning |
| FQXHMDI0003G | A CIM subscription failure occurred after user {0} unmanaged chassis with UUID {1} (IP: {2}). | Warning |
| FQXHMDI0004G | The NTP server on chassis {1} could not be reset after user {0} unmanaged it. | Warning |
| FQXHMDI0005G | The request by user {0} to unmanage chassis with UUID {1} (IP: {2}) failed. | Warning |
| FQXHMDI0006G | The request by user {0} to manage chassis with UUID {1} (IP {2}) failed to setup failure on the management server. | Warning |
| FQXHMDI0007G | The request by user {0} to manage chassis {1} failed due to login lockout on the chassis. | Warning |
| FQXHMDI0008G | The request by user {0} to manage chassis {1} failed due to login failure to the chassis. | Warning |
| FQXHMDI0009G | The request by user {0} to manage chassis with UUID {1} (IP {2}) failed due to connection issues. | Warning |
| FQXHMDI0010G | The request by user {0} to manage chassis with UUID {1} (IP {2}) resulted in no action, because it is already being managed. | Warning |
| FQXHMDI0011G | The request by user {0} to manage chassis {1} did not complete due to a failure during inventory collection. | Warning |
| FQXHMDI0012G | The request by user {0} to manage chassis with UUID {1} (IP: {2}) failed because the management server was unable to retrieve the chassis' LDAP certificate. | Warning |
| FQXHMDI0013G | The request by user {0} to manage chassis with UUID {1} (IP: {2}) failed because the management server was unable to retrieve the chassis' CIM certificate. | Warning |
| FQXHMDI0014G | The request by user {0} to manage chassis with UUID {1} (IP: {2}) 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 {0} to manage chassis with UUID {1} (IP: {2}) failed because it was unable to set up centralized management (managed authentication). | Warning |
| FQXHMDI0016G | The request by user {0} to manage chassis with UUID {1} (IP: {2}) failed due to unknown failure. | Warning |
| FQXHMDI0017G | The request by user {0} to manage chassis with UUID {1} (IP: {2}) failed due to being unable to set the authentication mode of the server. | Warning |
| FQXHMDI0021G | The request by user {0} to manage chassis {1} failed when setting up group permissions on the chassis. | Warning |
| FQXHMDI0022G | The request by user {0} to manage chassis with UUID {1} (IP: {2}) failed when performing additional manage configuration information. | Warning |
| FQXHMDI0023G | Initial inventory collection by user {0} of chassis with UUID {1} (IP: {2}) did not complete successfully. | Warning |
| FQXHMDI0024G | Enabling local user accounts on endpoint {1} by user {0} failed. | Warning |
| FQXHMDI0026G | The request to update the password by user {0} on device with UUID {1} (IP: {2}) was not successful because of connection issues. | Warning |
| FQXHMDI0027G | User {0} cannot manage chassis with UUID {1} (IP: {2}) because of connection issues. | Warning |
| FQXHMDI0028G | The attempt by user {0} to manage chassis with UUID {1} (IP: {2}) was not successful. | Warning |
| FQXHMDI0029G | The request by user {0} to force the management of server {1} did not complete. | Warning |
| FQXHMDI0030G | The request by user {0} to force the management of the chassis {1} did not complete. | Warning |
| FQXHMDI0031G | Configuring CIM subscriptions to some nodes of the chassis failed after user {0} managed the chassis with UUID {1} (IP: {2}). | Warning |
| FQXHMDI0032G | Removing CIM subscriptions from some nodes of the chassis failed after user {0} unmanaged the chassis with UUID {1} (IP: {2}). | Warning |
| FQXHMDI0033G | The property {0} contains the unsupported character {1} . The following characters are not supported {2}. | Warning |
| FQXHMDI0034G | The property {0} length exceeds the max supported limit of {1} characters. | Warning |
| FQXHMDI0035J | The IP address {0} of the device is a duplicate of another device IP address. | Warning |
| FQXHMDI0036J | The IP address {0} of the device is a duplicate of the management server IP address. | Warning |
| FQXHMDI0037J | The request by user {0} to manage switch {1} failed because the management server was unable to retrieve the switch certificate. | Warning |
| FQXHMDI0039J | The management server detected an IP conflict between the managed device and local network host. The IP address is {0} and the local network host MAC address is {1}. | Warning |
| FQXHMDI0040G | Updating the host configuration on chassis with UUID {0} has failed | Warning |
| FQXHMDI0041G | Updating the domain name on chassis with UUID {0} has failed | Warning |
| FQXHMDI0042G | Updating the host name on chassis with UUID {0} has failed | Warning |
| FQXHMDI0043G | Updating the display name on chassis with UUID {0} has failed | Warning |
| FQXHMDI0044G | Updating the IP interfaces on chassis with UUID {0} has failed | Warning |
| FQXHMDI0045G | Updating the rack information on chassis with UUID {0} has failed | Warning |
| FQXHMDI0046G | Updating the Lowest Rack Unit information on chassis with UUID {0} has failed | Warning |
| FQXHMDI0047G | Updating the display name on chassis with UUID {0} has succeeded with truncation. | Warning |
| FQXHMDI0048J | The health of SSD {0} in bay {1} of the RAID configuration {2} has diminished to a warning state. | Warning |
| FQXHMDI0061J | Server {0} was changed from the trusted to untrusted state because of {1}. | Warning |
| FQXHMDI0070J | The link status is down for PCI device {1} on server {0}. | Warning |
| FQXHMDI0103G | A CIM subscription failure occurred after user {0} unmanaged server {2}. | Warning |
| FQXHMDI0104G | The NTP server on server {1} failed to clean up after user {0} unmanaged it. | Warning |
| FQXHMDI0106G | The request by user {0} to manage server {1} failed because internal data related to this device could not be updated. | Warning |
| FQXHMDI0107G | The request by user {0} to manage server {1} failed due to login lockout on the server. | Warning |
| FQXHMDI0108G | The request by user {0} to manage server {1} failed during the login process to the server. | Warning |
| FQXHMDI0109G | The request by user {0} to manage server {1} failed due to connection issues. | Warning |
| FQXHMDI0110G | The request by user {0} to manage server {1} resulted in no action, because it is already being managed. | Warning |
| FQXHMDI0111G | The request by user {0} to manage server {1} did not complete due to a failure during inventory collection. | Warning |
| FQXHMDI0112G | The request by user {0} to manage rack server {1} failed because the management server was unable to retrieve the rack server's LDAP certificate. | Warning |
| FQXHMDI0113G | The request by user {0} to manage rack server {1} failed because the management server was unable to retrieve the rack server's CIM certificate. | Warning |
| FQXHMDI0114G | During the management process for rack server {0}, 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 {0} to manage rack server {1} 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 {0} to manage rack server {1} failed for unknown reasons. | Warning |
| FQXHMDI0117G | The request by user {0} to manage rack server {1} failed due to being unable to set the authentication mode of the server. | Warning |
| FQXHMDI0120G | The request by user {0} to unmanage server {1} failed because internal data related to the device could not be properly updated. | Warning |
| FQXHMDI0122G | The request by user {0} to manage server {1} failed when performing additional manage configuration information. | Warning |
| FQXHMDI0123G | Initial inventory collection by user {0} of server {1} did not complete successfully. | Warning |
| FQXHMDI0124G | The request by user {0} to manage server {1} resulted in no action, because it is already being managed by a management server - {2}. | Warning |
| FQXHMDI0125G | The request by user {0} to manage rack server {1} failed because CIM over HTTPS is not enabled on the server. | Warning |
| FQXHMDI0126G | The request by user {0} to manage server {1} resulted in no action, because node bay is already occupied by server - {2}. | Warning |
| FQXHMDI0128J | Address change for the device with UUID {0} was ignored because the IP address {1} is already used by the device with UUID {2}. | Warning |
| FQXHMDI0129G | During the management process for rack server {0}, 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 {0} has failed | Warning |
| FQXHMDI0141G | Updating the domain name on server with UUID {0} has failed | Warning |
| FQXHMDI0142G | Updating the host name on server with UUID {0} has failed | Warning |
| FQXHMDI0143G | Updating the display name on server with UUID {0} has failed | Warning |
| FQXHMDI0144G | Updating the IP interfaces on server with UUID {0} has failed | Warning |
| FQXHMDI0145G | Updating the rack information on server with UUID {0} has failed | Warning |
| FQXHMDI0147G | Updating the display name on server with UUID {0} has succeeded with truncation. | 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 {0} to manage storage {1} failed because internal data related to this device could not be updated. | Warning |
| FQXHMDI0307G | The request by user {0} to manage storage {1} failed due to connection issues. | Warning |
| FQXHMDI0308G | The request by user {0} to manage storage {1} failed during the login process to the storage. | Warning |
| FQXHMDI0309G | The request by user {0} to unmanage storage {1} failed due to connection issues. | Warning |
| FQXHMDI0310G | The request by user {0} to manage storage {1} resulted in no action, because it is already being managed. | Warning |
| FQXHMDI0316G | The request by user {0} to manage storage {1} failed for unknown reasons. | Warning |
| FQXHMDI0320G | The request by user {0} to unmanage storage {1} failed because internal data related to the device could not be properly updated. | Warning |
| FQXHMDI0323G | Initial inventory collection by user {0} of storage {1} did not complete successfully. | Warning |
| FQXHMDM0138G | User {0} cannot perform a power operation on endpoint {1} because of connection issues. | Warning |
| FQXHMDM0139G | User {0} cannot modify the boot order on endpoint {1} because of connection issues. | Warning |
| FQXHMDM0140G | A cryptography/NIST operation started by user {0} on device {1} was not successful because of connection issues. | Warning |
| FQXHMDM0141G | User {0} cannot perform power capping on endpoint {1} because of connection issues. | Warning |
| FQXHMDM0142G | User {0} cannot modify an inventory property on endpoint {1} because of connection issues. | Warning |
| FQXHMDM0143G | User {0} cannot initiate a CMM failover on endpoint {1} because of connection issues. | Warning |
| FQXHMDM0144G | The led setting operation action started by user User {0} cannot set the LED on endpoint {1} because of connection issues. | Warning |
| FQXHMDM0145G | The operation requested by user {0} could not complete because access to endpoint with UUID {1} (IP: {2}) was denied. | Warning |
| FQXHMDM0146G | The operation requested by user {0} could not complete because access to endpoint {1} was denied due to insufficient privileges. | Warning |
| FQXHMDM0147G | The operation requested by user {0} could not complete on endpoint {1} because the operation is not supported. | Warning |
| FQXHMDM0148G | The operation requested by user {0} could not complete on endpoint {1} because the endpoint is not available. | Warning |
| FQXHMDM0149G | The operation requested by user {0} could not complete on endpoint with UUID {1} (IP: {2}) because authentication failed. | Warning |
| FQXHMDM0150G | The operation requested by user {0} could not complete on endpoint with UUID {1} (IP: {2}) because authorization credentials are expired. | Warning |
| FQXHMDM0151G | The operation requested by user {0} timed out on device with UUID {1} (IP: {2}). | Warning |
| FQXHMDM0152G | The operation requested by user {0} was interrupted on device {1}. | Warning |
| FQXHMDM0153G | The operation requested by user {0} was interrupted on device with UUID {1} (IP: {2}). | Warning |
| FQXHMDM0155G | Access was denied for the stored credentials with username {0} on the endpoint with UUID {1}. | Warning |
| FQXHMDM0163J | The connection between the management server and the management controller {0} is offline. | Warning |
| FQXHMDM0165G | The device health state changed from normal to warning. | Warning |
| FQXHMDM0168G | The device health state changed from critical to warning. | 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 {0}, at IP address {1}, to change the maximum size of the Audit log from {2} to {3} was not successful. | Warning |
| FQXHMEM0106J | The management server detected missing events from {0}. | Warning |
| FQXHMEM0206J | The request from user {0}, at IP address {1}, to change the maximum size of the event log from {2} to {3} was not successful. | Warning |
| FQXHMEM0207J | The request from user {0}, at IP address {1},to clear the events with type {2} from the event log was not successful. | Warning |
| FQXHMEM0409J | A warning alert was asserted on device {0} with alert ID {1}. | Warning |
| FQXHMEM0410J | A critical alert was asserted on device {0} with alert ID {1}. | Warning |
| FQXHMJM0005J | User {0} at IP address {1} tried to create job schedule {2} but the operation was unsuccessful. | Warning |
| FQXHMJM0007J | User {0} at IP address {1} tried to update job schedule {2} but the operation was unsuccessful. | Warning |
| FQXHMJM0009J | User {0} at IP address {1} tried to change job schedule {2} state to {3}, but the operation was unsuccessful. | Warning |
| FQXHMJM0011J | User {0} at IP address {1} called Run Now procedure for job schedule {2}, but the operation was unsuccessful. | Warning |
| FQXHMJM0013J | User {0} at IP address {1} tried to clone job schedule {2}, but the operation was unsuccessful. | Warning |
| FQXHMJM0015J | User {0} at IP address {1} tried to remove job schedule configurations but the operation was unsuccessful. Removed schedules: {2}. Not found IDs: {3}. | Warning |
| FQXHMJM0017J | The management server tried to launch the job for job scheduler {0}, but the operation was unsuccessful. | Warning |
| FQXHMJM0019J | User {0} at IP address {1} tried to postpone job {2} but the operation was unsuccessful. | Warning |
| FQXHMMF0001J | The connection to collect metrics between the management server and the management controller {0} is offline. | Warning |
| FQXHMMF0002J | The connection to forward metrics between the management server and the orchestrator server {0} is offline. | Warning |
| FQXHMMF0004J | Metrics data collection for all DM Storage managed with ID {0} has failed. | Warning |
| FQXHMMF0005J | Metrics data collection for all DM Storage managed could not start. | Warning |
| FQXHMMF0006J | Metrics data collection was missed from the device {0} between {1} and {2}. | Warning |
| FQXHMSC0002G | User {0} set an empty range of L2 interfaces {1}. | Warning |
| FQXHMSC0003G | User {0} was unable to get L2 interfaces from switch with the error message {1}. | Warning |
| FQXHMSC0004G | The range definition {1} given by user {0} did not produce any valid interfaces. | Warning |
| FQXHMSC0005G | User {0} tried to deploy the template but switch firmware version is too low and does not support {1}. | Warning |
| FQXHMSC0006G | User {0} got response {1} from switch when updating interface {2}. | Warning |
| FQXHMSC0102G | User {0} got response {1} from switch when updating LACP priority. | Warning |
| FQXHMSC0103G | User {0} got response {1} from switch when updating global tagNative. | Warning |
| FQXHMSC0104F | User {0} tried to deploy the template but switch firmware version is too low and does not support {1}. | Warning |
| FQXHMSC0202G | User {0} got response {1} from switch when deploying PortChannel Advanced Configuration Template. | Warning |
| FQXHMSC0203G | User {0} got response {1} from switch when updating portchannel {2}. | Warning |
| FQXHMSC0204G | User {0} tried to deploy the template but switch firmware version is too low and does not support LACP individual. | Warning |
| FQXHMSC0302G | User {0} gave an empty interfaces list. | Warning |
| FQXHMSC0303G | User {0} got response {1} from switch when checking to see if portchannel {2} exists. | Warning |
| FQXHMSC0304G | User {0} was unable to get L2 Interfaces from switch when deploying Portchannel Basic Configuration Template with the message {1}. | Warning |
| FQXHMSC0305G | The range definition {1} given by user {0} did not produce any valid interfaces. | Warning |
| FQXHMSC0306G | User {0} got an invalid response {1} from the switch. | Warning |
| FQXHMSC0307G | User {0} gave an incompatible port mode {1} with current port mode {2} on the switch | Warning |
| FQXHMSC0308G | User {0} got response {1} from switch when updating portchannel {2}. | Warning |
| FQXHMSC0309G | User {0} got response {1} from switch when creating portchannel {2}. | Warning |
| FQXHMSC0402G | User {0} was unable to get portchannel list from switch with the message {1}. | Warning |
| FQXHMSC0403G | The range definition {1} given by user {0} did not produce any valid portchannels. | Warning |
| FQXHMSC0404G | User {0} was unable to delete any portchannels {2} having the response {1}. | Warning |
| FQXHMSC0405F | User {0} deleted portchannels {1} with success and with failure for {3} with the response {2}. | Warning |
| FQXHMSC0503G | User {0} gave an empty port list. | Warning |
| FQXHMSC0504G | User {0} tried to deploy the template but switch firmware version is too low and does not support Global BGP. | Warning |
| FQXHMSC0506G | User {0} got an error {1} when deleting current AS number {2} from switch. | Warning |
| FQXHMSC0507G | User {0} got response {1} from switch when setting BGP AS number {2}. | Warning |
| FQXHMSC0508G | User {0} got response {1} from switch when enabling BGP unnumbered globally. | Warning |
| FQXHMSC0509G | User {0} got response {1} from switch when enabling BGP unnumbered on interface {2}. | Warning |
| FQXHMSC0510G | User {0} got response {1} from switch when setting interface {2} as routed port. | Warning |
| FQXHMSC0602F | The VLAG Advanced Configuration Template that the user {0} deployed has no effect. | Warning |
| FQXHMSC0603G | User {0} got an invalid response {1} from switch when deploying VLAG Advanced Configuration Template. | Warning |
| FQXHMSC0604G | User {0} got response {1} from switch when setting VLAG healthcheck parameters. | Warning |
| FQXHMSC0605G | User {0} got response {1} from switch when trying to enable VLAG to set TIERID. | Warning |
| FQXHMSC0606G | User {0} got response {1} from switch when trying to disable VLAG to set TIERID. | Warning |
| FQXHMSC0607G | User {0} got response {1} from switch when setting VLAG parameters. | Warning |
| FQXHMSC0702F | The VLAG Instance Configuration Template that the user {0} deployed has no effect. | Warning |
| FQXHMSC0703G | User {0} got an invalid response {1} from switch when deploying VLAG Instance Configuration Template. | Warning |
| FQXHMSC0704G | User {0} got response {1} from switch when {2} instance {3}. | Warning |
| FQXHMSC0802F | The VLAG Instance {1} the user {0} wanted to delete does not exist on the switch. | Warning |
| FQXHMSC0803G | User {0} got response {1} from switch when checking if instance {2} exists. | Warning |
| FQXHMSC0804G | User {0} got response {1} from switch when deleting instance {2}. | Warning |
| FQXHMSC0902F | The VLAG Peers Configuration Template that the user {0} deployed has no effect. | Warning |
| FQXHMSC0903G | User {0} got response {1} from switch when getting current healthcheck parameters. | Warning |
| FQXHMSC0904G | User {0} got response {1} from switch when updating healthcheck parameters. | Warning |
| FQXHMSC0905G | User {0} got response {1} from switch when getting current ISL settings. | Warning |
| FQXHMSC0906G | User {0} got response {1} from switch when updating ISL settings. | Warning |
| FQXHMSC0907G | User {0} got response {1} from switch when getting current VLAG parameters. | Warning |
| FQXHMSC0908G | User {0} got response {1} from switch when updating VLAG parameters. | Warning |
| FQXHMSC1002F | The VLAN Configuration Template that the user {0} deployed has no effect. | Warning |
| FQXHMSC1003G | User {0} was unable to get interfaces from switch when deploying VLAN Configuration Template with the message {1}. | Warning |
| FQXHMSC1004G | User {0} was unable to get portchannels from switch when deploying VLAN Configuration Template with the message {1}. | Warning |
| FQXHMSC1005G | Range definition given by user {0} did not produce any valid interfaces to update. | Warning |
| FQXHMSC1006G | User {0} got an invalid response {1} from switch when deploying VLAN Configuration Template. | Warning |
| FQXHMSC1007G | User {0} got response {1} from switch when creating new VLAN {2}. | Warning |
| FQXHMSC1008G | User {0} got response {1} from switch when updating interface {2}. | Warning |
| FQXHMSC1102F | User {0} deleted VLANs {1} with success and with failure for {3} with the response {2}. | Warning |
| FQXHMSC1103F | User {0} gave an empty list of VLAN IDs for VLAN Delete Template. | Warning |
| FQXHMSC1104G | User {0} was unable to get current VLANs from switch when deploying VLAN Delete Template with the message {1}. | Warning |
| FQXHMSC1105G | User {0} was unable to delete any VLANs {2} having the response {1}. | Warning |
| FQXHMSC1202F | The VLAN Properties that the user {0} deployed has no effect. | Warning |
| FQXHMSC1203G | The VLAN {1} that the user {0} wanted to deployed the template does not exist. | Warning |
| FQXHMSC1204G | User {0} got an invalid response {1} from switch when getting VLAN properties. | Warning |
| FQXHMSC1205G | User {0} got response {1} from switch when updating VLAN {2} properties. | Warning |
| FQXHMSC1302F | The range definition given by user {0} did not produce any valid interfaces/portchannels. | Warning |
| FQXHMSC1303F | The VLAN Remove Template that the user {0} deployed has no effect. | Warning |
| FQXHMSC1304G | User {0} was unable to get interfaces from switch when deploying VLAN Remove Template with the message {1}. | Warning |
| FQXHMSC1305G | User {0} was unable to get portchannels from switch when deploying VLAN Remove Template with the message {1}. | Warning |
| FQXHMSC1307G | User {0} got response {1} from switch when updating interface {2}. | Warning |
| FQXHMSC1400G | User {0} failed to apply template because the switch operating system (ENOS) does not support configuration templates. | Warning |
| FQXHMSE0004G | Security policy level {0} on {1} does not match security policy level {2} on the management server. | Warning |
| FQXHMSE0005G | Minimum SSL/TLS protocol level {0} on {1} does not match minimum SSL/TLS protocol levels client {2} and server {3} on the management server. | Warning |
| FQXHMSE0006G | Cryptographic mode {0} on {1} does not match cryptographic mode {2} on the management server. | Warning |
| FQXHMSE0007G | Security policy state on chassis {0} is Pending. | Warning |
| FQXHMSE0123G | The trusted certificate for managed system {0} does not comply with the cryptographic mode of the system. | 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 {0} days remaining to make your system compliant. | Warning |
| FQXHMSE0928F | License will expire soon. Check licenses. | Warning |
| FQXHMSP00002J | The job {0} requested by user {1} to retrieve the chassis switch ports on device {2} failed. | Warning |
| FQXHMSS0002J | The download of Service Data files was not successful by user {0} at IP address {1}. | Warning |
| FQXHMSS0004J | The download of Service Data file {0} was not successful by user {1} at IP address {2}. | Warning |
| FQXHMSS1002J | The request from user {0}, at IP address {1}, to change the log level of logger {2} from {3} to {4} was not successful. | Warning |
| FQXHMSS1004J | The request from user {0}, at IP address {1}, to change the log size of logger {2} from {3} to {4} was not successful. | Warning |
| FQXHMSS1006J | The request from user {0}, at IP address {1}, to change the number of Service Data files to keep from {2} to {3} was not successful. | Warning |
| FQXHMSS1008J | The request from user {0}, at IP address {1}, to change the suppression time from {2} to {3} was not successful. | Warning |
| FQXHMSS1010J | The request from user {0}, at IP address {1}, to change the number of informational Service Data files to keep from {2} to {3} 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 {0} at IP address {1}. | Warning |
| FQXHMSS1017J | The request from user {0} at IP address {1} to change the number of logs archives for appender {2} to {3} has failed. | Warning |
| FQXHMSS1019J | The request from user {0} at IP address {1} to restore the log settings to the default values was not successful. | Warning |
| FQXHMSS1021J | The generation of Service Data archive for user {0} at IP address {1} finished unsuccessfully. | Warning |
| FQXHMSS1023J | The request by user {0} at IP address {1} to generate a Service Data file was not successful, due to a previous request still in process | Warning |
| FQXHMSS1024J | The request by user {0} at IP address {1} to upload a file was not successful, because the file name was not valid. | Warning |
| FQXHMSS1025J | The request by user {0} at IP address {1} to upload a file was not successful, because the file could not be written to disk. | Warning |
| FQXHMSS1026J | The request by user {0} at IP address {1} to upload a file was not successful, because a temp file could not deleted. | Warning |
| FQXHMSS1027J | The request by user {0} at IP address {1} to upload a file was not successful, because the file format was not valid. | Warning |
| FQXHMSS1030J | The request by user {0} at IP address {1} to change the Call Home configuration was unsuccessful. | Warning |
| FQXHMSS1032J | User {0} at IP address {1} tried to enable Call Home but the operation was unsuccessful. | Warning |
| FQXHMSS1034J | User {0} at IP address {1} tried to disable Call Home but the operation was unsuccessful. | Warning |
| FQXHMSS1036J | User {0} at IP address {1} tried to reset the Call Home configuration, but the operation was unsuccessful. | Warning |
| FQXHMSS1055J | The request from user {0}, at IP address {1}, to change the log level for the restricted logger {2} from {3} to {4} was not successful. | Warning |
| FQXHMSS2004J | The management server was not able to collect the Service Data archive for event {0} generated on {1}. | Warning |
| FQXHMSS2008J | Call Home Service Forwarder {0} was not able to create Ticket for event {1} generated on {2}. The forwarder has no more retries left. The process for this event will be dropped. | Warning |
| FQXHMSS2011J | Call Home Service Forwarder {0} was not able to upload the Service Data to Ticket {1}. The entry has no more retries left. The process for this event will be dropped. | Warning |
| FQXHMSS2014J | SFTP Service Forwarder {0} was not able to upload the Service Data to Ticket to {1}:{2}. The number of retries left is {3}. | Warning |
| FQXHMSS2023J | Call Home Service Forwarder {0} was not able to upload the Service Data to Ticket {1}. The number of retries left is {2}. | Warning |
| FQXHMSS2024J | Call Home Service Forwarder {0} was not able to create Ticket for event {1} generated on {2}. The number of retries left is {3}. | Warning |
| FQXHMSS2025J | SFTP Service Forwarder {0} was not able to upload the Service Data to Ticket to {1}:{2}. The entry has no more retries left. The process for this event will be dropped. | Warning |
| FQXHMSS2027G | User {0} at IP address {1} has tried to upload file {2} to Service Ticker {3} but the request failed. | Warning |
| FQXHMSS2029J | SFTP Service Forwarder {0} was not able to upload the Service Data to Ticket to {1}:{2} due to connectivity issues. The number of retries left is {3}. | Warning |
| FQXHMSS2030J | SFTP Service Forwarder {0} was not able to upload the Service Data to Ticket to {1}:{2} due to invalid credentials. The number of retries left is {3}. | Warning |
| FQXHMSS2031J | SFTP Service Forwarder {0} was not able to upload the Service Data to Ticket to {1}:{2} due to some transfer errors. The number of retries left is {3}. | Warning |
| FQXHMSS2032J | SFTP Service Forwarder {0} was not able to upload the Service Data to Ticket to {1}:{2} due to connectivity issues. The entry has no more retries left. The process for this event will be dropped. | Warning |
| FQXHMSS2033J | SFTP Service Forwarder {0} was not able to upload the Service Data to Ticket to {1}:{2} due to invalid credentials. The entry has no more retries left. The process for this event will be dropped. | Warning |
| FQXHMSS2034J | SFTP Service Forwarder {0} was not able to upload the Service Data to Ticket to {1}:{2} 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 {0} at IP Address {1} failed. | Warning |
| FQXHMSS2040J | Lenovo Upload Facility Service Forwarder {0} was not able to upload the Service Data to ticket to {1} 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 {0} was not able to upload the Service Data to ticket to {1} due to connectivity issues. The number of retries left is {2}. | Warning |
| FQXHMSS2045J | The request by user {0} at IP address {1} to change the Lenovo Upload Facility configuration was unsuccessful. | Warning |
| FQXHMSS2047J | User {0} at IP address {1} tried to reset the Lenovo Upload Facility configuration, but the operation was unsuccessful. | Warning |
| FQXHMSS2048J | An upload of the file {0} to the Lenovo Upload Facility was initiated by user {1}. | Warning |
| FQXHMSS2049J | An upload of usage data to the Lenovo Upload Facility was initiated. | Warning |
| FQXHMSS3037J | The Lenovo Call Home connectivity test started by user {0} at IP Address {1} failed. | Warning |
| FQXHMSS3038J | A Lenovo Call Home connection test has failed. Access token could not be retrieved. | Warning |
| FQXHMSS3040J | A Lenovo Software Call Home Test has failed. The case could not be created. | Warning |
| FQXHMSS3041J | A Lenovo Software Call Home has failed. The case could not be created. | Warning |
| FQXHMSS3042J | A Lenovo Call Home Test has failed. The case could not be created. | Warning |
| FQXHMSS3043J | A Lenovo Manual Call Home has failed. The case could not be created. | Warning |
| FQXHMSS3044J | A Lenovo Call Home has failed. The case could not be created. | Warning |
| FQXHMSS3056J | The Lenovo Software Call Home Test has failed to upload Service Data to case {0}. | Warning |
| FQXHMSS3057J | The Lenovo Software Call Home Test has failed to upload Service Data because Lenovo case could not be created. | Warning |
| FQXHMSS3060J | The Lenovo Software Call Home has failed to upload Service Data to case {0}. | Warning |
| FQXHMSS3061J | The Lenovo Software Call Home has failed to upload Service Data because Lenovo case could not be created. | Warning |
| FQXHMSS3064J | The Lenovo Call Home Test has failed to upload Service Data to case {0}. | Warning |
| FQXHMSS3065J | The Lenovo Call Home Test has failed to upload Service Data because Lenovo case could not be created. | Warning |
| FQXHMSS3068J | The Lenovo Call Home has failed to upload Service Data to case {0}. | Warning |
| FQXHMSS3069J | The Lenovo Call Home has failed to upload Service Data because Lenovo case could not be created. | Warning |
| FQXHMSS3072J | A Lenovo Call Home Pass Through Test has failed. The case could not be created. | Warning |
| FQXHMSS3073J | A Lenovo Call Home Pass Through has failed. The case could not be created. | Warning |
| FQXHMSS4002F | Internal service {0} terminated unexpectedly, and the VM will be restarted. Debug data on the termination has been collected and stored at {1}. | Warning |
| FQXHMSS4003F | Internal service {0} terminated unexpectedly, and it could not be restarted. Debug data on the termination has been collected and stored at {1}. | Warning |
| FQXHMSS4004F | Internal service {0} terminated unexpectedly, and it will not be recovered. Debug data on the termination has been collected and stored at {1}. | Warning |
| FQXHMSS4005F | Internal service {0} 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 {1}. | Warning |
| FQXHMSS4012F | Internal service {0} terminated unexpectedly, and the VM will be restarted. No debug data was collected. | Warning |
| FQXHMSS4013F | Internal service {0} terminated unexpectedly, and it could not be restarted. No debug data was collected. | Warning |
| FQXHMSS4014F | Internal service {0} terminated unexpectedly, and will not be recovered. No debug data was collected. | Warning |
| FQXHMSS4015F | Internal service {0} terminated unexpectedly, and it could not be restarted. As a result, the VM will be rebooted. No debug data was collected. | Warning |
| FQXHMSS4020J | A Manual Call Home has failed. The ticket could not be created. | Warning |
| FQXHMSS4021J | A Call Home Test has failed. The ticket could not be created. | Warning |
| FQXHMSS4022J | A Call Home has failed. The ticket could not be created. | Warning |
| FQXHMSS4023J | A Call Home Connection Test has failed. The ticket could not be created. | Warning |
| FQXHMSS4024J | The country has been successfully changed. | Warning |
| FQXHMSS4025J | The country could not be changed. | Warning |
| FQXHMSS5050J | The Call Home test ended unsuccessfully. | Warning |
| FQXHMSS5053J | Call Home test generated by user {0} at IP address {1} ended unsuccessfully. | Warning |
| FQXHMSS5067J | Call Home event with ID {0} from component {1} failed to be called home. Remaining retries {2}. | Warning |
| FQXHMSS5075J | Call Home event with ID {0} from component {1} failed to call home. There are no more remaining retries, so this function is aborting. | Warning |
| FQXHMSS5077J | For Call Home event with ID {0} from component {1}, there was a failure when attaching service data to ticket number {2}. The number of remaining retries left is {3}. | Warning |
| FQXHMSS5079J | For Call Home event with ID {0} from component {1}, there was a failure when attaching additional service data files to ticket number {2}. The number of remaining retries left is {3}. | Warning |
| FQXHMSS5094J | Collecting the Service Data archive generated by event with ID {0} from endpoint {1} failed. | Warning |
| FQXHMSS5095J | Saving the collected Service Data archive generated by event with ID {0} from endpoint {1} inside the server failed. | Warning |
| FQXHMSS5096J | Uploading the collected endpoint Service Data archive to Problem Number with ID {0} failed. | Warning |
| FQXHMSS5097J | Uploading additional Service Data archive(s) to Problem Number with ID {0} failed. | Warning |
| FQXHMUP3101J | The firmware installed on this system is non-compliant. | Warning |
| FQXHMUP6101J | The request to update the application by user {0} failed with return code {1}. | Warning |
| FQXHMUP6102J | The request to update the application by user {0} failed with return code {1}. | Warning |
| FQXPMNM0001G | Failed to set new BMC network parameters. | Warning |
| FQXPMVD0001H | Failed to get VPD data. | Warning |
| FQXPMVD0002H | Failed to update the VPD data. | Warning |
| FQXSFDD0001G | DRIVER HEALTH PROTOCOL: Missing Configuration. Requires Change Settings From F1. | Warning |
| FQXSFDD0007G | Security Key Lifecycle Manager (SKLM) IPMI Error. | Warning |
| FQXSFIO0014J | A bad option ROM checksum was detected for the device found at Bus {0} Device {1} Function {2}. The Vendor ID for the device is {3} and the Device ID is {4}. The physical slot number is {5}. | Warning |
| FQXSFIO0019J | PCIe Resource Conflict {0}. | Warning |
| FQXSFIO0020J | PCIe Isolation has occurred in PCIe slot {0}. The adapter may not operate correctly. | Warning |
| FQXSFIO0021J | PCIe LER has occurred in PCIe slot {0}. The adapter may not operate correctly. | Warning |
| FQXSFIO0022J | PCIe Link Width has degraded from {1} to {2} in PCIe slot {0}. | Warning |
| FQXSFIO0023J | PCIe Link Speed has degraded from {1} to {2} in PCIe slot {0}. | Warning |
| FQXSFMA0002G | The uncorrectable memory error state has been cleared. | Warning |
| FQXSFMA0037G | Intel Optane DCPMM interleave set (DIMM {0}) is migrated from another system (Platform ID: {1}), these migrated DCPMMs are not supported nor warranted in this system. | Warning |
| FQXSFPU0016G | A processor within the system has failed the BIST. | Warning |
| FQXSFPU0017G | A processor microcode update failed. | Warning |
| FQXSFPU0021G | Hardware physical presence is in asserted state. | Warning |
| FQXSFPU0022G | The TPM configuration is not locked. | Warning |
| FQXSFPU0023G | Secure Boot Image Verification Failure Warning. | Warning |
| FQXSFPU0024G | Intel UEFI ACM startup failed, make sure TPM is enabled. | Warning |
| FQXSFPU0032G | A boot configuration error has been detected. | Warning |
| FQXSFPU0033G | Processor has been disabled. | Warning |
| FQXSFPU4033F | TPM Firmware recovery is in progress. Please DO NOT power off or reset system. | Warning |
| FQXSFPU4036F | TPM Firmware recovery is starting. Please DO NOT power off or reset system. | Warning |
| FQXSFPU4043G | TPM Firmware update aborted. System is rebooting... | Warning |
| FQXSFPU4044F | The current TPM firmware version could not support TPM version toggling. | Warning |
| FQXSFPU4045G | Physical Presence is not asserted, abort TPM Firmware upgrade. | Warning |
| FQXSFPU4050G | Failed to update TPM Firmware. | Warning |
| FQXSFPU4051G | Undefined TPM_TCM_POLICY found | Warning |
| FQXSFPU4052G | TPM_TCM_POLICY is not locked | Warning |
| FQXSFPU4053G | System TPM_TCM_POLICY does not match the planar. | Warning |
| FQXSFPU4054G | TPM/TCM card logical binding has failed. | Warning |
| FQXSFPU4056J | TCM daughter card field update is not supported. Please remove the TCM daughter card and reboot | Warning |
| FQXSFSR0002G | {0} GPT corruption recovered, DiskGUID: {1}. | Warning |
| FQXSFSR0003G | The number of boot attempts has been exceeded. No bootable device found. | Warning |
| FQXSPCA0000J | Numeric sensor {0} going low (lower non-critical) has asserted. | Warning |
| FQXSPCA0001J | Numeric sensor {0} going low (lower non-critical) has asserted. | Warning |
| FQXSPCA0006J | Numeric sensor {0} going high (upper non-critical) has asserted. | Warning |
| FQXSPCA0007J | Numeric sensor {0} going high (upper non-critical) has asserted. | Warning |
| FQXSPCA0014J | Sensor {0} has transitioned from normal to non-critical state. | Warning |
| FQXSPCA0015J | Sensor {0} has transitioned from normal to non-critical state. | Warning |
| FQXSPCA0032J | Redundancy Degraded for {0} has asserted. | Warning |
| FQXSPCA0033J | Non-redundant:Sufficient Resources from Redundancy Degraded or Fully Redundant for {0} has asserted. | Warning |
| FQXSPCA0034J | Non-redundant:Sufficient Resources from Insufficient Resources for {0} has asserted. | Warning |
| FQXSPCA0036J | Redundancy Degraded from Full Redundancy for {0} has asserted. | Warning |
| FQXSPCA0037J | Redundancy Degraded from Non-redundant for {0} has asserted. | Warning |
| FQXSPEA0001J | Sensor {0} has transitioned from normal to non-critical state. | Warning |
| FQXSPEM0010J | Sensor {0} is unavailable or degraded on management system {1}. | Warning |
| FQXSPEM0011J | Controller {0} is unavailable or degraded on management system {1}. | Warning |
| FQXSPEM0014G | Sensor {0} has failed on management system {1}. | Warning |
| FQXSPEM0015J | FRU {0} has failed on management system {1}. | Warning |
| FQXSPIO0014J | Bus {0} is operating in a degraded state. | Warning |
| FQXSPIO0023G | Slot {0} disabled on system {1}. | Warning |
| FQXSPIO2000J | The connector {0} has been disconnected. | Warning |
| FQXSPMA0010J | {0} on Subsystem {1} Throttled. | Warning |
| FQXSPMA0011G | Memory Logging Limit Reached for {0} on Subsystem {1}. | Warning |
| FQXSPMA0016J | Redundancy Degraded for {0} has asserted. | Warning |
| FQXSPMA0017J | Non-redundant:Sufficient Resources from Redundancy Degraded or Fully Redundant for {0} has asserted. | Warning |
| FQXSPMA0018J | Non-redundant:Sufficient Resources from Insufficient Resources for {0} has asserted. | Warning |
| FQXSPMA0020J | Redundancy Degraded from Full Redundancy for {0} has asserted. | Warning |
| FQXSPMA0021J | Redundancy Degraded from Non-redundant for {0} has asserted. | Warning |
| FQXSPMA0024G | Sensor {0} has asserted. | Warning |
| FQXSPPU0002G | The Processor {0} is operating in a Degraded State. | Warning |
| FQXSPPU0013G | {0} has correctable error. | Warning |
| FQXSPPU2010G | A terminator has not been detected on the processor {0}. | Warning |
| FQXSPPW0003G | Failure predicted on {0}. | Warning |
| FQXSPPW0014G | Failure predicted on {0}. | Warning |
| FQXSPPW0025G | The Battery {0} is critically low. | Warning |
| FQXSPPW0028J | Numeric sensor {0} going low (lower non-critical) has asserted. | Warning |
| FQXSPPW0029J | Numeric sensor {0} going low (lower non-critical) has asserted. | Warning |
| FQXSPPW0030J | Numeric sensor {0} going low (lower non-critical) has asserted. | Warning |
| FQXSPPW0031J | Numeric sensor {0} going low (lower non-critical) has asserted. | Warning |
| FQXSPPW0040J | Numeric sensor {0} going high (upper non-critical) has asserted. | Warning |
| FQXSPPW0041J | Numeric sensor {0} going high (upper non-critical) has asserted. | Warning |
| FQXSPPW0042J | Numeric sensor {0} going high (upper non-critical) has asserted. | Warning |
| FQXSPPW0043J | Numeric sensor {0} going high (upper non-critical) has asserted. | Warning |
| FQXSPPW0056J | Sensor {0} has transitioned from normal to non-critical state. | Warning |
| FQXSPPW0057J | Sensor {0} has transitioned from normal to non-critical state. | Warning |
| FQXSPPW0058J | Sensor {0} has transitioned from normal to non-critical state. | Warning |
| FQXSPPW0059J | Sensor {0} has transitioned from normal to non-critical state. | Warning |
| FQXSPPW0088J | Sensor {0} has indicated an install error. | Warning |
| FQXSPPW0099J | Redundancy Degraded for {0} has asserted. | Warning |
| FQXSPPW0100J | Redundancy Degraded for {0} has asserted. | Warning |
| FQXSPPW0101J | Redundancy Degraded for {0} has asserted. | Warning |
| FQXSPPW0102J | Non-redundant:Sufficient Resources from Redundancy Degraded or Fully Redundant for {0} has asserted. | Warning |
| FQXSPPW0103J | Non-redundant:Sufficient Resources from Redundancy Degraded or Fully Redundant for {0} has asserted. | Warning |
| FQXSPPW0104J | Non-redundant:Sufficient Resources from Redundancy Degraded or Fully Redundant for {0} has asserted. | Warning |
| FQXSPPW0105J | Non-redundant:Sufficient Resources from Insufficient Resources for {0} has asserted. | Warning |
| FQXSPPW0106J | Non-redundant:Sufficient Resources from Insufficient Resources for {0} has asserted. | Warning |
| FQXSPPW0107J | Non-redundant:Sufficient Resources from Insufficient Resources for {0} has asserted. | Warning |
| FQXSPPW0111J | Redundancy Degraded from Full Redundancy for {0} has asserted. | Warning |
| FQXSPPW0112J | Redundancy Degraded from Full Redundancy for {0} has asserted. | Warning |
| FQXSPPW0113J | Redundancy Degraded from Full Redundancy for {0} has asserted. | Warning |
| FQXSPPW0114J | Redundancy Degraded from Non-redundant for {0} has asserted. | Warning |
| FQXSPPW0115J | Redundancy Degraded from Non-redundant for {0} has asserted. | Warning |
| FQXSPPW0116J | Redundancy Degraded from Non-redundant for {0} has asserted. | Warning |
| FQXSPSD0002G | Failure Predicted on drive {0} in the enclosure (MTM-SN: {1}). | Warning |
| FQXSPSD0003G | Failure Predicted on drive {0} in the enclosure (MTM-SN: {1}). | Warning |
| FQXSPSE0000F | The Chassis {0} was opened. | Warning |
| FQXSPUN0000J | Numeric sensor {0} going low (lower non-critical) has asserted. | Warning |
| FQXSPUN0003J | Numeric sensor {0} going high (upper non-critical) has asserted. | Warning |
| FQXSPUN0009G | Sensor {0} has asserted. | Warning |
| FQXSPUN0011G | Sensor {0} is asserting predictive failure. | Warning |
| FQXSPUN0018J | Sensor {0} has transitioned from normal to non-critical state. | Warning |
| FQXSPUN0026G | Device {0} has been added. | Warning |
| FQXSPUN0038J | Sensor {0} has indicated an install error. | Warning |
| FQXSPUN0041J | Redundancy Degraded for {0} has asserted. | Warning |
| FQXSPUN0042J | Non-redundant:Sufficient Resources from Redundancy Degraded or Fully Redundant for {0} has asserted. | Warning |
| FQXSPUN0043J | Non-redundant:Sufficient Resources from Insufficient Resources for {0} has asserted. | Warning |
| FQXSPUN0045J | Redundancy Degraded from Full Redundancy for {0} has asserted. | Warning |
| FQXSPUN0046J | Redundancy Degraded from Non-redundant for {0} has asserted. | Warning |
| FQXSPUN0049J | Sensor {0} has transitioned from normal to non-critical state. | Warning |
| FQXSPUN0051J | Sensor {0} has transitioned from normal to non-critical state. | Warning |
| FQXSPUN0052J | Sensor {0} has transitioned from normal to non-critical state. | Warning |
| FQXSPUN0056G | Sensor {0} has asserted. | Warning |
| FQXSPUN2012G | Sensor {0} is asserting predictive failure. | Warning |
| FQXHMCP1215M | Failover from server {0} to standby server {1} was not successful. | Critical |
| FQXHMCP1255M | No standby servers were available in pool {0} for failover for server {1}. | Critical |
| FQXHMCR0001W | The IP address was changed on interface {0}. | Critical |
| FQXHMDI0049K | The health of SSD {0} in bay {1} of the RAID configuration {2} has diminished to a critical state. | Critical |
| FQXHMDM0166K | The device health state changed from normal to critical. | Critical |
| FQXHMDM0167K | The device health state changed from warning to critical. | Critical |
| FQXHMSE0698K | One or more external LDAP servers are now reachable. | 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 |
| FQXHMSS2002M | The management server was not able to find the appropriate system to collect the Service Data archive for event {0} generated on {1}. | Critical |
| FQXHMSS2003M | The management server encountered an error while trying to collect the Service Data archive for event {0} generated on {1}. | Critical |
| FQXHMSS2015M | SFTP Service Forwarder {0} encountered an error while trying to upload the collected Service Data to {1}:{2}. | Critical |
| FQXHMSS2042M | Lenovo Upload Facility Service Forwarder {0} encountered an error while trying to upload the collected Service Data to {1}:{2}. | Critical |
| FQXPMCL0001K | Bootx64.efi is not found. Failed to Boot OS. | Critical |
| FQXPMCL0002K | Failed to read Deployment Manager Signature from USB. | Critical |
| FQXPMCL0003K | BMC communication failed: DRIVER Mount Failure. | Critical |
| FQXPMCL0004K | BMC communication succeeded. Volume Name MISMATCHED. | Critical |
| FQXPMCL0005K | Current System Boot Mode is Legacy. OS Clone only support UEFI Mode. | Critical |
| FQXPMCL0006K | Failed to export raid config. | Critical |
| FQXPMCL0007K | Failed to import raid config. | Critical |
| FQXPMCL0008K | Failed to export uefi settings. | Critical |
| FQXPMCL0009K | Failed to import uefi settings. | Critical |
| FQXPMCL0010K | Failed to export bmc settings. | Critical |
| FQXPMCL0011K | Failed import bmc settings. | Critical |
| FQXPMEM0001M | Unable to locate LXPM firmware image | Critical |
| FQXPMEM0006M | Unable to locate diagnostic firmware image | Critical |
| FQXPMEM0007M | Diagnostic image cannot be launched as "Console Redirection" is enabled | Critical |
| FQXPMEM0008M | Diagnostic image cannot be launched as the image may be corrupt | Critical |
| FQXPMEM0009M | Unexpected error occur | Critical |
| FQXPMOS0001K | Bootx64.efi is not found. Failed to Boot OS. | Critical |
| FQXPMOS0002K | Failed to read Deployment Manager Signature from USB. | Critical |
| FQXPMOS0003K | Failed to copy Windows boot files to target | Critical |
| FQXPMOS0004K | BMC Communication Failed: EMMC2USB Mount Failure. | Critical |
| FQXPMOS0005K | BMC communication failed: DRIVER Mount Failure. | Critical |
| FQXPMOS0006K | BMC communication succeeded. Volume Name MISMATCHED. | Critical |
| FQXPMOS0007K | Failed to read License RTF file. | Critical |
| FQXPMOS0008K | Please make sure the Ethernet cable has been plugged into your computer and your network settings are correct. | Critical |
| FQXPMOS0009K | Current System Boot Mode is Legacy. LXPM OS installation only support UEFI Mode. | Critical |
| FQXPMRS0011K | Failed to change disk drives' state. | Critical |
| FQXPMSD0001M | HDD Test was interrupted by the host with a hardware or software reset | Critical |
| FQXPMSD0002M | A fatal error or unknown test error occurred while the device was executing its self-test | Critical |
| FQXPMSD0003M | self-test completed having a test element that failed and the test element that failed is not known. | Critical |
| FQXPMSD0004M | self-test completed having the electrical element of the test failed. | Critical |
| FQXPMSD0005M | self-test completed having the servo (and/or seek) test element of the test failed. | Critical |
| FQXPMSD0006M | self-test completed having the read element of the test failed. | Critical |
| FQXPMSD0007M | Hard Drive(s) not found | Critical |
| FQXPMSD0008M | UEFI is not ready for LXPM to send command to test hard drive. | Critical |
| FQXPMSD0009M | Device error is occurred when LXPM send command to test hard drive. | Critical |
| FQXPMSD0010M | uEFI is timeout while LXPM send command to test hard drive. | Critical |
| FQXPMSD0011M | The hard drive is not supported by uEFI while LXPM send command to test hard drive. | Critical |
| FQXPMSR0001K | Found unsupported RAID adapter. | Critical |
| FQXPMSR0021L | Failed to create new virtual disk. | Critical |
| FQXPMSR0031L | Failed to remove existing virtual disk | Critical |
| FQXPMUP0001K | The system configuration does not meet the prerequisite | Critical |
| FQXPMUP0002K | The selected packages are not compatible | Critical |
| FQXPMUP0003K | Unable to obtain the minimum level of UEFI | Critical |
| FQXPMUP0004K | Unable to obtain the installed version of UEFI | Critical |
| FQXPMUP0005K | Unable to obtain the installed version of BMC | Critical |
| FQXPMUP0006K | Unable to obtain the installed version of LXPM | Critical |
| FQXPMUP0007K | Unable to obtain the installed version of linux driver | Critical |
| FQXPMUP0008K | Unable to obtain the installed version of windows driver | Critical |
| FQXPMUP0201M | BMC communication failed: EMMC2USB mount failure. Failed to update the firmware | Critical |
| FQXPMUP0202M | Transfer the update package error. Failed to update the firmware | Critical |
| FQXPMUP0203M | BMC communication failed: EMMC2USB unmount failure. Failed to update the firmware | Critical |
| FQXPMUP0204M | BMC communication failed: Execute the update cmd failure. Failed to update the firmware | Critical |
| FQXPMUP0205M | BMC communication failed: Get the update status failure.Failed to update the firmware | Critical |
| FQXPMUP0206M | The level of the update package is too old. Failed to update the firmware. | Critical |
| FQXPMUP0207M | The update package is invalid. Failed to update the firmware. | Critical |
| FQXPMUP0208M | Failed to execute reboot BMC command | Critical |
| FQXPMVD0011K | Failed to get the TPM/TPM card/TCM policy status | Critical |
| FQXPMVD0012K | Failed to set the TPM/TPM card/TCM policy | Critical |
| FQXSFDD0002M | DRIVER HEALTH PROTOCOL: Reports 'Failed' Status Controller. | Critical |
| FQXSFDD0004M | DRIVER HEALTH PROTOCOL: Reports 'System Shutdown' Required Controller. | Critical |
| FQXSFDD0005M | DRIVER HEALTH PROTOCOL: Disconnect Controller Failed. Requires 'Reboot'. | Critical |
| FQXSFDD0006M | DRIVER HEALTH PROTOCOL: Reports Invalid Health Status Driver. | Critical |
| FQXSFIO0005M | An intra-board UPI failure has been detected on the link between processor {0} port {1} and processor {2} port {3}. | Critical |
| FQXSFIO0006M | An inter-board UPI failure has been detected on the link between processor {0} port {1} and processor {2} port {3}. | Critical |
| FQXSFIO0007M | An error has been detected by the IIO on Bus {0}. The value of Global Fatal Error Status register is {1}. The value of Global Non-Fatal Error Status register is {2}. Please check error logs for additional downstream device error data, the physical slot number is {3}. | Critical |
| FQXSFIO0008M | An intra-board UPI dynamic link width reduction has been detected on the link between processor {0} port {1} and processor {2} port {3}. | Critical |
| FQXSFIO0009M | An inter-board UPI dynamic link width reduction has been detected on the link between processor {0} port {1} and processor {2} port {3}. | Critical |
| FQXSFIO0010M | An Uncorrectable PCIe Error has Occurred at Bus {0} Device {1} Function {2}. The Vendor ID for the device is {3} and the Device ID is {4}. The Physical slot number is {5}. | Critical |
| FQXSFIO0011M | A PCIe parity error has occurred on Bus {0} Device {1} Function {2}. The Vendor ID for the device is {3} and the Device ID is {4}. The Physical slot number is {5}. | Critical |
| FQXSFIO0012M | A PCIe system error has occurred on Bus {0} Device {1} Function {2}. The Vendor ID for the device is {3} and the Device ID is {4}. The Physical slot number is {5}. | Critical |
| FQXSFIO0016M | IFM: Reset loop avoided - Multiple resets not allowed. | Critical |
| FQXSFIO0017M | IFM: Error communicating with the BMC - IFM may not be deployed correctly. | Critical |
| FQXSFMA0001M | DIMM {0} has been disabled due to an error detected during POST. {1}. | Critical |
| FQXSFMA0002M | An uncorrectable memory error has been detected on DIMM {0} at address {1}. {2}. | Critical |
| FQXSFMA0003K | A memory mismatch has been detected. Please verify that the memory configuration is valid. {0}. | Critical |
| FQXSFMA0004N | No system memory has been detected. {0}. | Critical |
| FQXSFMA0005N | Memory is present within the system but could not be configured. Please verify that the memory configuration is valid. {0}. | Critical |
| FQXSFMA0008M | DIMM {0} has failed the POST memory test. {1}. | Critical |
| FQXSFMA0009K | Invalid memory configuration for Mirror Mode. Please correct memory configuration. {0}. | Critical |
| FQXSFMA0010K | Invalid memory configuration for Sparing Mode. Please correct memory configuration. {0}. | Critical |
| FQXSFMA0012L | The {0} PFA Threshold limit has been exceeded on DIMM {1} at address {2}. {3}. | Critical |
| FQXSFMA0016M | Memory spare copy failed. {0}. | Critical |
| FQXSFMA0022N | All DIMMs have been disabled and the system will be unable to boot until this is corrected. | Critical |
| FQXSFMA0023M | Error has occurred in NVDIMM flash. NVDIMM backup/restore may not operate correctly. {0}. | Critical |
| FQXSFMA0024M | Error has occurred in NVDIMM Supercap. NVDIMM backup/restore may not operate correctly. {0}. | Critical |
| FQXSFMA0025M | NVDIMM Supercap has been disconnected. NVDIMM will lose its backup ability until this is corrected. {0}. | Critical |
| FQXSFMA0026M | DIMM {0} Self-healing attempt {1}. {2}. | Critical |
| FQXSFMA0027K | Invalid memory configuration (Unsupported DIMM Population) detected. Please verify memory configuration is valid.{0}. | Critical |
| FQXSFMA0027M | DIMM {0} Self-healing fail at Rank {1} Sub Rank {2} Bank {3} Row {4} in Device {5}. {6}. | Critical |
| FQXSFMA0028K | Memory Capacity exceeds CPU limit. {0}. | Critical |
| FQXSFMA0028M | DIMM {0} Self-healing attempt number over DIMM level threshold {1} at Rank {2} Sub Rank {3} Bank {4} Row {5} in Device {6}. {7}. | Critical |
| FQXSFMA0030K | Intel Optane DCPMM DIMM {0} Percentage Remaining is less than {1}% and still functioning. | Critical |
| FQXSFMA0031K | Intel Optane DCPMM DIMM {0} has reached 1% remaining spares block and still functioning. | Critical |
| FQXSFMA0032M | Intel Optane DCPMM DIMM {0} has no remaining spares block. | Critical |
| FQXSFMA0033M | Intel Optane DCPMM persistent memory interleave set has {0} DCPMMs(DIMM {1}), {2} DIMMs' location is not correct. | Critical |
| FQXSFMA0034M | DIMM {0} (UID: {1}) of Intel Optane DCPMM persistent memory interleave set should be moved to DIMM slot {2} in sequence. | Critical |
| FQXSFMA0035M | Intel Optane DCPMM interleave set should have {0} DCPMMs, but {1} DCPMMs are missing. | Critical |
| FQXSFMA0036M | DIMM {0} (UID: {1}) of Intel Optane DCPMM persistent memory interleave set is missing. | Critical |
| FQXSFMA0038K | All Intel Optane DCPMMs could not be auto unlocked because of no passphrase. | Critical |
| FQXSFMA0039K | One or more onboard Intel Optane DCPMMs could not be auto unlocked because of invalid passphrase. | Critical |
| FQXSFMA0040K | Invalid Intel Optane DCPMM configuration detected. Please verify DCPMM configuration is valid. | Critical |
| FQXSFMA0041K | Near Memory/Far Memory ratio (1:{0}.{1}) for Intel Optane DCPMM configuration is not in recommended range (1:4 - 1:16). | Critical |
| FQXSFMA0042K | Intel Optane DCPMM is not supported by processor of this system. | Critical |
| FQXSFPU0001N | An unsupported processor has been detected. | Critical |
| FQXSFPU0002N | An invalid processor type has been detected. | Critical |
| FQXSFPU0003K | A processor mismatch has been detected between one or more processors in the system. | Critical |
| FQXSFPU0004K | A discrepancy has been detected in the number of cores reported by one or more processors within the system. | Critical |
| FQXSFPU0005K | A mismatch between the maximum allowed UPI link speed has been detected for one or more processors. | Critical |
| FQXSFPU0006K | A power segment mismatch has been detected for one or more processors. | Critical |
| FQXSFPU0007K | Processors have mismatched Internal DDR Frequency | Critical |
| FQXSFPU0008K | A core speed mismatch has been detected for one or more processors. | Critical |
| FQXSFPU0009K | An external clock frequency mismatch has been detected for one or more processors. | Critical |
| FQXSFPU0010K | A cache size mismatch has been detected for one or more processors. | Critical |
| FQXSFPU0011K | A cache type mismatch has been detected for one or more processors. | Critical |
| FQXSFPU0012K | A cache associativity mismatch has been detected for one or more processors. | Critical |
| FQXSFPU0013K | A processor model mismatch has been detected for one or more processors. | Critical |
| FQXSFPU0014N | A processor family mismatch has been detected for one or more processors. | Critical |
| FQXSFPU0015K | A processor stepping mismatch has been detected for one or more processors. | Critical |
| FQXSFPU0016N | A processor within the system has failed the BIST. | Critical |
| FQXSFPU0018N | CATERR(IERR) has asserted on processor {0}. | Critical |
| FQXSFPU0019N | An uncorrectable error has been detected on processor {0}. | Critical |
| FQXSFPU0030N | A firmware fault has been detected in the UEFI image. | Critical |
| FQXSFPU0031N | The number of POST attempts has reached the value configured in F1 setup.The system has booted with default UEFI settings. User specified settings have been preserved and will be used on subsequent boots unless modified before rebooting. | Critical |
| FQXSFPU0034L | The TPM could not be initialized properly. | Critical |
| FQXSFPU4035M | TPM Firmware recovery failed. TPM chip may be damaged. | Critical |
| FQXSFPU4039M | Fail to recovery TPM version. TPM chip may be broken. | Critical |
| FQXSFPU4040M | TPM selftest has failed. | Critical |
| FQXSFPU4056M | TPM/TCM card is changed, need install back the original TCM/TPM card which shipped with the system. | Critical |
| FQXSFPW0001L | CMOS has been cleared. | Critical |
| FQXSFSM0001L | Power capping is disabled. | Critical |
| FQXSFSM0002N | Boot Permission denied by Management Module: System Halted. | Critical |
| FQXSFSM0003N | Timed Out waiting on boot permission from Management Module: System Halted. | Critical |
| FQXSFSM0004M | An XCC communication failure has occurred. | Critical |
| FQXSFSM0005M | An error occurred while saving UEFI settings to the XCC. | Critical |
| FQXSFSM0006M | Unable to retrieve the system configuration from the BMC. | Critical |
| FQXSFSM0008M | Boot permission timeout detected. | Critical |
| FQXSFSR0001M | {0} GPT corruption detected, DiskGUID: {1}. | Critical |
| FQXSFTR0001L | An invalid date and time have been detected. | Critical |
| FQXSPCA0002M | Numeric sensor {0} going low (lower critical) has asserted. | Critical |
| FQXSPCA0003M | Numeric sensor {0} going low (lower critical) has asserted. | Critical |
| FQXSPCA0004N | Numeric sensor {0} going low (lower non-recoverable) has asserted. | Critical |
| FQXSPCA0005N | Numeric sensor {0} going low (lower non-recoverable) has asserted. | Critical |
| FQXSPCA0008M | Numeric sensor {0} going high (upper critical) has asserted. | Critical |
| FQXSPCA0009M | Numeric sensor {0} going high (upper critical) has asserted. | Critical |
| FQXSPCA0010N | Numeric sensor {0} going high (upper non-recoverable) has asserted. | Critical |
| FQXSPCA0011N | Numeric sensor {0} going high (upper non-recoverable) has asserted. | Critical |
| FQXSPCA0016M | Sensor {0} has transitioned to critical from a less severe state. | Critical |
| FQXSPCA0017M | Sensor {0} has transitioned to critical from a less severe state. | Critical |
| FQXSPCA0018N | Sensor {0} has transitioned to non-recoverable from a less severe state. | Critical |
| FQXSPCA0019N | Sensor {0} has transitioned to non-recoverable from a less severe state. | Critical |
| FQXSPCA0022M | Sensor {0} has transitioned to critical from a non-recoverable state. | Critical |
| FQXSPCA0023M | Sensor {0} has transitioned to critical from a non-recoverable state. | Critical |
| FQXSPCA0024N | Sensor {0} has transitioned to non-recoverable. | Critical |
| FQXSPCA0025N | Sensor {0} has transitioned to non-recoverable. | Critical |
| FQXSPCA0031L | Redundancy Lost for {0} has asserted. | Critical |
| FQXSPCA0035M | Non-redundant:Insufficient Resources for {0} has asserted. | Critical |
| FQXSPCR0001N | Sensor {0} has transitioned to non-recoverable from a less severe state. | Critical |
| FQXSPDA0000N | The System {0} encountered firmware error - no video device detected. | Critical |
| FQXSPEA0002M | Sensor {0} has transitioned to critical from a less severe state. | Critical |
| FQXSPEM0008N | The System {0} has encountered a system hardware fault. | Critical |
| FQXSPEM0013L | Management system {0} is disabled. | Critical |
| FQXSPFW0000N | The System {0} encountered a POST Error. | Critical |
| FQXSPFW0001N | Firmware BIOS (ROM) corruption was detected on system {0} during POST. | Critical |
| FQXSPFW0002N | The System {0} encountered a firmware hang. | Critical |
| FQXSPIO0001L | The connector {0} has encountered a configuration error. | Critical |
| FQXSPIO0002N | The System {0} encountered firmware error - unrecoverable keyboard failure. | Critical |
| FQXSPIO0003N | A diagnostic interrupt has occurred on system {0}. | Critical |
| FQXSPIO0004L | A bus timeout has occurred on bus {0}. | Critical |
| FQXSPIO0005N | An I/O Channel Check NMI has occurred on system {0}. | Critical |
| FQXSPIO0006N | A software NMI has occurred on system {0}. | Critical |
| FQXSPIO0007N | A PCI PERR has occurred on system {0}. | Critical |
| FQXSPIO0008N | A PCI SERR has occurred on system {0}. | Critical |
| FQXSPIO0011N | An Uncorrectable Error has occurred on {0}. | Critical |
| FQXSPIO0012N | A Fatal NMI Error has occurred on system {0}. | Critical |
| FQXSPIO0013N | A Fatal Bus Error has occurred on bus {0}. | Critical |
| FQXSPIO0015M | Fault in slot {0} on system {1}. | Critical |
| FQXSPMA0002N | Configuration Error for {0} on Subsystem {1}. | Critical |
| FQXSPMA0005N | Subsystem {0} has insufficient memory for operation. | Critical |
| FQXSPMA0006N | Parity Error for {0} on Subsystem {1}. | Critical |
| FQXSPMA0007L | Scrub Failure for {0} on Subsystem {1}. | Critical |
| FQXSPMA0008N | Uncorrectable error detected for {0} on Subsystem {1}. | Critical |
| FQXSPMA0012M | An Over-Temperature Condition has been detected on the {0} on Subsystem {1}. | Critical |
| FQXSPMA0013N | The System {0} has detected no memory in the system. | Critical |
| FQXSPMA0015L | Redundancy Lost for {0} has asserted. | Critical |
| FQXSPMA0019M | Non-redundant:Insufficient Resources for {0} has asserted. | Critical |
| FQXSPPU0001N | An Over-Temperature Condition has been detected on {0}. | Critical |
| FQXSPPU0003N | {0} has Failed with IERR. | Critical |
| FQXSPPU0004M | {0} has Failed with FRB1/BIST condition. | Critical |
| FQXSPPU0005M | {0} has Failed with FRB2/POST condition. | Critical |
| FQXSPPU0006M | {0} has Failed. | Critical |
| FQXSPPU0007N | CPU voltage mismatch detected on {0}. | Critical |
| FQXSPPU0009N | {0} has a Configuration Mismatch. | Critical |
| FQXSPPU0011N | An SM BIOS Uncorrectable CPU complex error for {0} has asserted. | Critical |
| FQXSPPU0012M | {0} has machine check error. | Critical |
| FQXSPPW0002L | Power supply {0} in the enclosure (MTM-SN: {1})has failed. | Critical |
| FQXSPPW0003L | Power supply {0} in the enclosure (MTM-SN: {1})has failed. | Critical |
| FQXSPPW0007L | {0} has a Configuration Mismatch. | Critical |
| FQXSPPW0012L | Soft power control has failed for {0}. | Critical |
| FQXSPPW0013L | {0} has Failed. | Critical |
| FQXSPPW0016K | Power Control of System {0} has failed. | Critical |
| FQXSPPW0027M | The Battery {0} has failed. | Critical |
| FQXSPPW0032M | Numeric sensor {0} going low (lower critical) has asserted. | Critical |
| FQXSPPW0033M | Numeric sensor {0} going low (lower critical) has asserted. | Critical |
| FQXSPPW0034M | Numeric sensor {0} going low (lower critical) has asserted. | Critical |
| FQXSPPW0035M | Numeric sensor {0} going low (lower critical) has asserted. | Critical |
| FQXSPPW0036N | Numeric sensor {0} going low (lower non-recoverable) has asserted. | Critical |
| FQXSPPW0037N | Numeric sensor {0} going low (lower non-recoverable) has asserted. | Critical |
| FQXSPPW0038N | Numeric sensor {0} going low (lower non-recoverable) has asserted. | Critical |
| FQXSPPW0039N | Numeric sensor {0} going low (lower non-recoverable) has asserted. | Critical |
| FQXSPPW0044M | Numeric sensor {0} going high (upper critical) has asserted. | Critical |
| FQXSPPW0045M | Numeric sensor {0} going high (upper critical) has asserted. | Critical |
| FQXSPPW0046M | Numeric sensor {0} going high (upper critical) has asserted. | Critical |
| FQXSPPW0047M | Numeric sensor {0} going high (upper critical) has asserted. | Critical |
| FQXSPPW0048N | Numeric sensor {0} going high (upper non-recoverable) has asserted. | Critical |
| FQXSPPW0049N | Numeric sensor {0} going high (upper non-recoverable) has asserted. | Critical |
| FQXSPPW0050N | Numeric sensor {0} going high (upper non-recoverable) has asserted. | Critical |
| FQXSPPW0051N | Numeric sensor {0} going high (upper non-recoverable) has asserted. | Critical |
| FQXSPPW0060M | Sensor {0} has transitioned to critical from a less severe state. | Critical |
| FQXSPPW0061M | Sensor {0} has transitioned to critical from a less severe state. | Critical |
| FQXSPPW0062M | Sensor {0} has transitioned to critical from a less severe state. | Critical |
| FQXSPPW0063M | Sensor {0} has transitioned to critical from a less severe state. | Critical |
| FQXSPPW0064N | Sensor {0} has transitioned to non-recoverable from a less severe state. | Critical |
| FQXSPPW0065N | Sensor {0} has transitioned to non-recoverable from a less severe state. | Critical |
| FQXSPPW0066N | Sensor {0} has transitioned to non-recoverable from a less severe state. | Critical |
| FQXSPPW0067N | Sensor {0} has transitioned to non-recoverable from a less severe state. | Critical |
| FQXSPPW0072M | Sensor {0} has transitioned to critical from a non-recoverable state. | Critical |
| FQXSPPW0073M | Sensor {0} has transitioned to critical from a non-recoverable state. | Critical |
| FQXSPPW0074M | Sensor {0} has transitioned to critical from a non-recoverable state. | Critical |
| FQXSPPW0075M | Sensor {0} has transitioned to critical from a non-recoverable state. | Critical |
| FQXSPPW0076N | Sensor {0} has transitioned to non-recoverable. | Critical |
| FQXSPPW0077N | Sensor {0} has transitioned to non-recoverable. | Critical |
| FQXSPPW0078N | Sensor {0} has transitioned to non-recoverable. | Critical |
| FQXSPPW0079N | Sensor {0} has transitioned to non-recoverable. | Critical |
| FQXSPPW0096L | Redundancy Lost for {0} has asserted. | Critical |
| FQXSPPW0097L | Redundancy Lost for {0} has asserted. | Critical |
| FQXSPPW0098L | Redundancy Lost for {0} has asserted. | Critical |
| FQXSPPW0108M | Non-redundant:Insufficient Resources for {0} has asserted. | Critical |
| FQXSPPW0109M | Non-redundant:Insufficient Resources for {0} has asserted. | Critical |
| FQXSPPW0110M | Non-redundant:Insufficient Resources for {0} has asserted. | Critical |
| FQXSPSB0000N | The System {0} has encountered a motherboard failure. | Critical |
| FQXSPSD0001L | Drive {0} in the enclosure(MTM-SN: {1}) has been disabled due to a detected fault. | Critical |
| FQXSPSD0002L | Drive {0} in the enclosure(MTM-SN: {1}) has been disabled due to a detected fault. | Critical |
| FQXSPSD0005L | Array critical asserted on drive {0} in the enclosure (MTM-S/N: {1}). | Critical |
| FQXSPSD0006L | Array failed on drive {0} in the enclosure (MTM-S/N: {1}). | Critical |
| FQXSPSD0007L | Array critical asserted on drive {0} in the enclosure (MTM-S/N: {1}). | Critical |
| FQXSPSD0008K | Rebuild Aborted for array {0}. | Critical |
| FQXSPSD0008L | Array failed on drive {0} in the enclosure (MTM-S/N: {1}). | Critical |
| FQXSPSD0009M | The System {0} encountered firmware error - unrecoverable boot device failure. | Critical |
| FQXSPSD0016M | Sensor {0} has asserted. | Critical |
| FQXSPSR0001N | Sensor {0} has transitioned to non-recoverable from a less severe state. | Critical |
| FQXSPUN0001M | Numeric sensor {0} going low (lower critical) has asserted. | Critical |
| FQXSPUN0002N | Numeric sensor {0} going low (lower non-recoverable) has asserted. | Critical |
| FQXSPUN0004M | Numeric sensor {0} going high (upper critical) has asserted. | Critical |
| FQXSPUN0005N | Numeric sensor {0} going high (upper non-recoverable) has asserted. | Critical |
| FQXSPUN0019M | Sensor {0} has transitioned to critical from a less severe state. | Critical |
| FQXSPUN0020N | Sensor {0} has transitioned to non-recoverable from a less severe state. | Critical |
| FQXSPUN0022M | Sensor {0} has transitioned to critical from a non-recoverable state. | Critical |
| FQXSPUN0023N | Sensor {0} has transitioned to non-recoverable. | Critical |
| FQXSPUN0040L | Redundancy Lost for {0} has asserted. | Critical |
| FQXSPUN0044M | Non-redundant:Insufficient Resources for {0} has asserted. | Critical |
| FQXSPUN0047N | Sensor {0} has transitioned to non-recoverable. | Critical |
| FQXSPUN0050M | Sensor {0} has transitioned to critical from a less severe state. | Critical |
| FQXSPUN0053M | Sensor {0} has transitioned to critical from a less severe state. | Critical |
| FQXSPUN0054M | Sensor {0} has transitioned to critical from a less severe state. | Critical |
| FQXSPUN0055M | Sensor {0} has transitioned to critical from a less severe state. | Critical |
| FQXSPUP0004L | A hardware incompatibility was detected on system {0}. | Critical |
| FQXSPUP0005L | A firmware or software incompatibility was detected on system {0}. | Critical |
| FQXSPUP0006L | Invalid or Unsupported hardware was detected on system {0}. | Critical |
| FQXSPUP0007L | Invalid or Unsupported firmware or software was detected on system {0}. | Critical |
| FQXSPUP2009L | A failing software or firmware change was detected on system {0}. | Critical |
Give feedback