Message:PostBoot processing on <Configuration name> has started.
Message Type: LOG
Severity: INFO
Probable Cause: Indicates that the PostBoot processing on the specified configuration group has started.
Recommended Action: No action is required.
Message:PostBoot processing on <Configuration name> is complete.
Message Type: LOG
Severity: INFO
Probable Cause: Indicates that the PostBoot processing on the specified configuration group has been completed.
Recommended Action: No action is required.
Message: Configuration File Replay has started.
Message Type: LOG
Severity: INFO
Probable Cause: Indicates that the configuration replay has started.
Recommended Action: No action is required.
Message: Configuration Replay is complete.
Message Type: LOG
Severity: INFO
Probable Cause: Indicates that the configuration replay has been completed.
Recommended Action: No action is required.
Message: Event: <Event Name>, Status: <Command status>, User command: <ConfD hpath string>.
Message Type: AUDIT
Class: DCMCFG
Severity: INFO
Probable Cause:Indicates that the user command has been executed successfully.
Recommended Action: No action is required.
Message: No Configuration File Replay.
Message Type: LOG
Severity: INFO
Probable Cause: Indicates that configuration file replay will not happen on this system boot up.
Recommended Action: No action is required.
Message: Configuration has been reset to default due to changes in configuration metadata.
Message Type: LOG
Severity: INFO
Probable Cause: Indicates that the configuration schema has changed and therefore the old configuration cannot be retained.
Recommended Action: Replay the saved configuration manually.
Message: Reset terminal timeout: <Timeout Reset Command>.
Message Type: AUDIT
Class: DCMCFG
Severity: INFO
Probable Cause: Indicates that terminal timeout has been reset.
Recommended Action: No action is required.
Message: Error Node replace model mismatch, chassis disabled WWN: <switch_wwn>.
Message Type: AUDIT | LOG
Severity: ERROR
Probable Cause: Indicates that the replacement switch model is different from the model of switch being replaced; this is not supported and therefore the chassis has been disabled.
Recommended Action: Use the same switch model for replacement.
Message: Switch is prepared for power-cycle. No clis will work henceforth. Need power-cycle or reload to make switch fully functional.
Message Type: LOG
Severity: INFO
Probable Cause: Indicates that database is shutdown gracefully so that node is power-cycle ready.
Recommended Action: Power-cycle or Reload to make switch fully functional.
Message: Switch is in ZTP mode. Configuration related commands will not be allowed. Cancel ZTP or wait until ZTP has completed to make changes to the switch configuration.
Message Type: LOG
Severity: INFO
Probable Cause: Indicates that ZTP mode is enabled and configuration related commands will not be allowed.
Recommended Action: Cancel ZTP mode or wait untl ZTP has completed to make changes to the switch configuration.
Message: Copy running-config to startup-config operation successful on this node.
Message Type: LOG
Severity: INFO
Probable Cause: Indicates that the running configuration has been copied to the startup configuration on the node.
Recommended Action: No action is required.
Message: Copy running-config to startup-config operation failed on this node.
Message Type: LOG
Severity: INFO
Probable Cause: Indicates failure to copy the running configuration to the startup configuration on the node.
Recommended Action: No action is required.
Message: Copy default-config to startup-config operation successful on this node.
Message Type: LOG
Severity: INFO
Probable Cause: Indicates that the default configuration has been copied to the startup configuration on the node.
Recommended Action: No action is required.
Message: Copy default-config to startup-config operation failed on this node.
Message Type: LOG
Severity: INFO
Probable Cause: Indicates failure to copy the default configuration to the startup configuration on the node.
Recommended Action: No action is required.
Message: Copy of the downloaded config file to the current running-config has completed successfully on this node.
Message Type: LOG
Severity: INFO
Probable Cause: Indicates that the downloaded configuration file has been copied to the current running configuration.
Recommended Action: No action is required.
Message: Copy of the downloaded config file to the current startup-config has completed successfully on this node.
Message Type: LOG
Severity: INFO
Probable Cause: Indicates that the downloaded configuration file has been copied to the current startup configuration.
Recommended Action: No action is required.
Message: Startup configuration file has been uploaded successfully to the remote location.
Message Type: LOG
Severity: INFO
Probable Cause: Indicates that the startup configuration file has been uploaded successfully.
Recommended Action: No action is required.
Message: Running configuration file has been uploaded successfully to the remote location.
Message Type: LOG
Severity: INFO
Probable Cause: Indicates that the running configuration file has been uploaded successfully.
Recommended Action: No action is required.
Message: Error (<error string>) encountered while copying configuration to flash/USB.
Message Type: LOG
Severity: INFO
Probable Cause: Indicates a failure to copy configuration file to flash or USB storage device.
Recommended Action: No action is required.
Message: Last configuration replay complete.
Message Type: LOG
Severity: INFO
Probable Cause: Indicates that a configuration was in progress during high availability and the configuration has been replayed.
Recommended Action: No action is required.
Message: Error (<error string>) last configuration replay failed.
Message Type: LOG
Severity: ERROR
Probable Cause: Indicates that a configuration was in progress during high availability and the configuration replay has failed.
Recommended Action: Reconfigure the failed command.
Message: Running configuration file has been uploaded successfully to flash.
Message Type: LOG
Severity: INFO
Probable Cause: Indicates that the running configuration file has been uploaded successfully.
Recommended Action: No action is required.
Message: Running configuration file has been uploaded successfully to USB.
Message Type: LOG
Severity: INFO
Probable Cause: Indicates that the running configuration file has been uploaded successfully to a USB storage device.
Recommended Action: No action is required.
Message: Startup configuration file has been uploaded successfully to flash.
Message Type: LOG
Severity: INFO
Probable Cause: Indicates that the startup configuration file has been uploaded successfully.
Recommended Action: No action is required.
Message: Startup configuration file has been uploaded successfully to USB.
Message Type: LOG
Severity: INFO
Probable Cause: Indicates that the startup configuration file has been uploaded successfully.
Recommended Action: No action is required.
Message: System initialization is complete. SLX-OS is ready to handle all commands.
Message Type: LOG
Severity: INFO
Probable Cause: Indicates that SLX-OS is ready to handle all commands after system initialization completion.
Recommended Action: No action is required.
Message: File has been uploaded successfully to USB.
Message Type: LOG
Severity: INFO
Probable Cause: Indicates that file has been uploaded successfully to USB.
Recommended Action: No action is required.
Message: Error while transferring file over tftp. Reason: <error string>
Message Type: LOG
Severity: ERROR
Probable Cause: Indicates a failure while transferring file over tftp.
Recommended Action: Refer to the reason code indicated in the command output for possible action.
Message: Copy file from flash completed successfully
Message Type: LOG
Severity: INFO
Probable Cause: Indicates a successful copy of file from flash.
Recommended Action: No action is required.
Message: Error while copying file from flash. Reason: <error string>
Message Type: LOG
Severity: ERROR
Probable Cause: Indicates a failure while copying file from flash.
Recommended Action: Refer to the reason code indicated in the command output for possible action.
Message: Configuration Rollback to checkpoint <Checkpoint Name> has started.
Message Type: LOG
Severity: INFO
Probable Cause: Indicates that the configuration rollback has started.
Recommended Action: No action is required.
Message: Configuration Rollback to checkpoint <Checkpoint Name> has been completed successfully.
Message Type: LOG
Severity: INFO
Probable Cause: Indicates that the configuration rollback has been completed successfully.
Recommended Action: No action is required.
Message: Configuration Rollback to checkpoint <Checkpoint Name> has been completed partially.
Message Type: LOG
Severity: ERROR
Probable Cause: Indicates that the configuration rollback has been completed partially.
Recommended Action: No action is required.
Message: Configuration Rollback to checkpoint <Checkpoint Name> has failed.
Message Type: LOG
Severity: ERROR
Probable Cause: Indicates failure to perform configuration rollback to the specified checkpoint.
Recommended Action: No action is required.
Message: Configuration Rollback to checkpoint <Checkpoint Name> is aborted.
Message Type: LOG
Severity: ERROR
Probable Cause: Indicates that the configuration rollback to the specified checkpoint is aborted.
Recommended Action: No action is required.
Message: Checkpoint <Checkpoint Name> is created by user <User Name>
Message Type: LOG
Severity: INFO
Probable Cause: Indicates that the checkpoint is created successfully.
Recommended Action: No action is required.
Message: Checkpoint <Checkpoint Name> is Deleted by user <User Name>
Message Type: LOG
Severity: INFO
Probable Cause: Indicates that the checkpoint is deleted successfully.
Recommended Action: No action is required.
Message: FIPS Zeroize operation request received.
Message Type: LOG
Severity: INFO
Probable Cause: Indicates that the Federal Information Protection Standard (FIPS) Zeroize operation request has been received.
Recommended Action: No action is required.
Message: FIPS Zeroize operation: all client sessions are notified that Zeroize in progress.
Message Type: LOG
Severity: INFO
Probable Cause: Indicates that all client sessions are notified about the Federal Information Protection Standard (FIPS) Zeroize operation in progress and the commands cannot be executed.
Recommended Action: No action is required.
Message: FIPS Zeroize operation: starting with cleanup for Zeroize.
Message Type: LOG
Severity: INFO
Probable Cause: Indicates that the configuration files cleanup for Federal Information Protection Standard (FIPS) Zeroize has started.
Recommended Action: No action is required.
Message: FIPS Zeroize operation: starting prepare phase for Zeroize.
Message Type: LOG
Severity: INFO
Probable Cause: Indicates that the prepare phase for Federal Information Protection Standard (FIPS) Zeroize has started, during which all the services will be shut down.
Recommended Action: No action is required.
Message: FIPS Zeroize operation: failed in prepare phase step for Zeroize.
Message Type: LOG
Severity: INFO
Probable Cause: Indicates that the Federal Information Protection Standard (FIPS) Zeroize operation has failed during the prepare phase.
Recommended Action: No action is required.
Message: FIPS Zeroize operation: Running Zeroize for secure deletion of the user configuration data.
Message Type: LOG
Severity: INFO
Probable Cause: Indicates that the Federal Information Protection Standard (FIPS) Zeroize operation is running for secure deletion of the user configuration data.
Recommended Action: No action is required.
Message: FIPS Zeroize operation: failed during secure deletion of the user configuration data.
Message Type: LOG
Severity: ERROR
Probable Cause: Indicates that the Federal Information Protection Standard (FIPS) Zeroize operation has failed during secure deletion of the user configuration data.
Recommended Action: Refer to the reason code indicated in the fips zeroize command output for possible action.
Message: FIPS Zeroize operation failed.
Message Type: LOG
Severity: INFO
Probable Cause: Indicates that the Federal Information Protection Standard (FIPS) Zeroize operation has failed.
Recommended Action: No action is required.
Message: FIPS Zeroize operation executed successfully.
Message Type: LOG
Severity: INFO
Probable Cause: Indicates that the Federal Information Protection Standard (FIPS) Zeroize operation has been executed successfully.
Recommended Action: No action is required.
Message: FIPS Zeroize operation failed. Node zeroizing or already zeroized.
Message Type: LOG
Severity: INFO
Probable Cause: Indicates that the Federal Information Protection Standard (FIPS) Zeroize operation has failed because the node is zeroizing or it was already zeroized.
Recommended Action: No action is required.
Message: Bare-Metal state is <Bare-Metal state>.
Message Type: LOG
Severity: INFO
Probable Cause: Indicates if the switch is in the bare-metal state.
Recommended Action: No action is required.
Message: Event-Handler: Exclusive run-mode action has been triggered and is active. Cluster formation operations will be paused.
Message Type: LOG
Severity: INFO
Probable Cause: Indicates that an activated event-handler that is configured with exclusive run-mode has been triggered. Cluster formation operations will be paused.
Recommended Action: No action is required.
Message: Event-Handler: Exclusive run-mode action has completed and is inactive. Cluster formation operations will be resumed.
Message Type: LOG
Severity: INFO
Probable Cause: Indicates that an activated event-handler that is configured with exclusive run-mode has completed. Cluster formation operations will be resumed.
Recommended Action: No action is required.
Message: Event-Handler: Action execution (Event-Handler: <Event-Handler Name>, Action Script: <Action Script Name>) timed out.
Message Type: LOG
Severity: ERROR
Probable Cause: Indicates that the action script associated with one of the event-handlers timed out.
Recommended Action: In case action script is going to take longer, reconfigure the event-handler activation action-timeout to a higher value.
Message: Event: <Event Name>, Status: success, Info: Successful login attempt through <connection method and IP Address>.
Message Type: AUDIT
Class: DCMCFG
Severity: INFO
Probable Cause: Indicates that the log in was successful. An IP address is displayed when the login occurs over a remote connection.
Recommended Action: Verify that the security event was planned. If the security event was planned, no action is required. If the security event was not planned, take appropriate action as defined by your enterprise security policy.
Message: Event: <Event Name>, Status: success, Info: Successful logout by user [<User>].
Message Type: AUDIT
Class: DCMCFG
Severity: INFO
Probable Cause: Indicates that the specified user has successfully logged out.
Recommended Action: No action is required.
Message: Software assert error detected in configuration manager service: <message>.
Message Type: LOG | FFDC
Severity: ERROR
Probable Cause: Indicates an error condition hit by the configuration manager (DCM) caused ASSERT.
Recommended Action: Execute the copy support command and contact your switch service provider.
Message: <Database Name> database integrity check timed out after <Timeout in minutes> minutes.
Message Type: LOG
Severity: INFO
Probable Cause: Indicates that the database integrity check timeout has occurred.
Recommended Action: No action is required.
Message: Encountered Database Corruption. System going down for auto-recovery.
Message Type: LOG
Severity: ERROR
Probable Cause: Indicates that the database operation failed because of database corruption. The system reloads for auto-recovery of the database.
Recommended Action: No action is required.
Message: Database Corruption was detected. Therefore, system was rebooted for recovery and may have taken longer than usual.
Message Type: LOG
Severity: INFO
Probable Cause: Indicates that the last system reload was for auto-recovery of database because the database corruption was detected.
Recommended Action: No action is required.
Message: <Database name> database corruption was detected. The system will startup with the default configuration for this database.
Message Type: LOG
Severity: INFO
Probable Cause: Indicates that database corruption was detected. The system has auto-recovered with the default configuration applied.
Recommended Action: No action is required.
Message: Event: Client <IP> is connected to telemetry server.
Message Type: LOG
Severity: INFO
Probable Cause: Indicates that a client is connected to telemetry server.
Recommended Action: No action is required.
Message: Event: Client <IP> is disconnected from telemetry server.
Message Type: LOG
Severity: INFO
Probable Cause: Indicates that a client is disconnected from telemetry server.
Recommended Action: No action is required.
Message: Event: Max limit on clients connected to telemetry server reached.
Message Type: LOG
Severity: INFO
Probable Cause: Indicates that a max number of clients connected to telemetry server.
Recommended Action: No action is required.
Message: Event: Connection to collector <Collector Name> has been established.
Message Type: LOG
Severity: INFO
Probable Cause:Indicates that a collector connection has been established.
Recommended Action: No action is required.
Message: Event: Collector <Collector Name> has been disconnected.
Message Type: LOG
Severity: INFO
Probable Cause: Indicates that a collector has been disconnected.
Recommended Action: No action is required.
Message: Database schema conversion succeeded.
Message Type: LOG
Severity: INFO
Probable Cause: Indicates that after a firmware download, the database schema was successfully converted to the schema supported by the firmware.
Recommended Action: No action is required.
Message: Database schema conversion failed.
Message Type: LOG
Severity: INFO
Probable Cause: Indicates that after a firmware download, a failure was encountered in converting the database schema to the schema supported by the firmware.
Recommended Action: No action is required.