Message: DHCP Auto-Deployment firmware download start.
Message Type: LOG
Severity: INFO
Probable Cause:Indicates that DHCP automatic firmware download has started.
Recommended Action: No action is required.
Message:DHCP Auto-Deployment failed due to dual-MM HA sync timeout.
Message Type: AUDIT | LOG
Severity: ERROR
Probable Cause: Indicates that the DHCP Auto Deployment (DAD) process has failed because HA synchronization of the dual-management module has timed out.
Recommended Action: No action is required.
Message: DHCP Auto-Deployment failed during DHCP process.
Message Type: LOG
Severity: ERROR
Probable Cause: Indicates that the DHCP Auto Deployment (DAD) process failed because the dhclient is not getting the FTP server IP or the firmware path information.
Recommended Action: No action is required.
Message: Last firmware download session is in progress.
Message Type: LOG
Severity: INFO
Probable Cause: Indicates that the previous firmware download session is still in progress.
Recommended Action: No action is required.
Message: Last firmware download session failed.
Message Type: LOG
Severity: ERROR
Probable Cause: Indicates that the last firmware download session has failed.
Recommended Action: No action is required.
Message: DHCP Auto-Deployment cluster formation timeout.
Message Type: LOG
Severity: ERROR
Probable Cause: Indicates that not all nodes have completed DHCP Auto Deployment (DAD) before the current DAD session limit.
Recommended Action: No action is required.
Message: DHCP Auto-Deployment sanity check failed.
Message Type: LOG
Severity: ERROR
Probable Cause: Indicates that the DHCP Auto Deployment (DAD) sanity check has failed.
Recommended Action: No action is required.
Message: DHCP Auto-Deployment principle node ready.
Message Type: LOG
Severity: INFO
Probable Cause: Indicates that the principle node is ready for the secondary node to join.
Recommended Action: No action is required.
Message: Current firmware skip firmware download.
Message Type: LOG
Severity: INFO
Probable Cause: Indicates that the new firmware is already loaded on the switch and therefore there is no need to trigger firmware download.
Recommended Action: No action is required.
Message: DHCP Auto-Deployment session fail to start firmware download.
Message Type: LOG
Severity: ERROR
Probable Cause: Indicates that the DHCP Auto Deployment (DAD) session has failed to start firmware download.
Recommended Action: No action is required.
Message: DHCP Auto-Deployment firmware download completed successfully.
Message Type: AUDIT | LOG
Severity: INFO
Probable Cause: Indicates that the DHCP Auto Deployment (DAD) process has completed successfully.
Recommended Action: No action is required.
Message: DHCP Auto-Deployment firmware download failed.
Message Type: AUDIT | LOG
Severity: ERROR
Probable Cause: Indicates that the DHCP Auto Deployment (DAD) process has failed.
Recommended Action: No action is required.
Message: DHCP Auto-Deployment node succeeded.
Message Type: LOG
Severity: INFO
Probable Cause: Indicates that DHCP Auto Deployment (DAD) succeeded on the node.
Recommended Action: No action is required.
Message: DHCP Auto-Deployment cluster partially succeeded.
Message Type: LOG
Severity:WARNING
Probable Cause: Indicates that some of the nodes are not in the cluster before the DHCP Auto Deployment (DAD) session time limit.
Recommended Action: No action is required.
Message: DHCP Auto-Deployment cluster succeeded.
Message Type: LOG
Severity: INFO
Probable Cause: Indicates that DHCP Auto Deployment (DAD) succeeded on all nodes.
Recommended Action: No action is required.
Message: DHCP Auto-Deployment firmware mismatch.
Message Type: LOG
Severity: WARNING
Probable Cause: Indicates that the secondary node has a different firmware from the principle node.
Recommended Action: No action is required.
Message: DHCP Auto-Deployment running global configuration script.
Message Type: LOG
Severity: INFO
Probable Cause: Indicates that DHCP Auto Deployment (DAD) is running global configuration script.
Recommended Action: No action is required.
Message: DHCP Auto-Deployment complete global configuration script
Message Type: LOG
Severity: INFO
Probable Cause: Indicates that DHCP Auto Deployment (DAD) has completed running global configuration script.
Recommended Action: No action is required.
Message: DHCP Auto-Deployment running local configuration script.
Message Type: LOG
Severity: INFO
Probable Cause: Indicates that DHCP Auto Deployment (DAD) is running local configuration script.
Recommended Action: No action is required.
Message: DHCP Auto-Deployment complete local configuration script.
Message Type: LOG
Severity: INFO
Probable Cause: Indicates that DHCP Auto Deployment (DAD) has completed running local configuration script.
Recommended Action: No action is required.
Message: DHCP Auto-Deployment running local command.
Message Type: LOG
Severity: INFO
Probable Cause: Indicates that DHCP Auto Deployment (DAD) is running local command.
Recommended Action: No action is required.
Message: DHCP Auto-Deployment complete local command.
Message Type: LOG
Severity: INFO
Probable Cause: Indicates that DHCP Auto Deployment (DAD) has completed running local command.
Recommended Action: No action is required.
Message: DHCP Auto-Deployment unexpected switch reboot.
Message Type: LOG
Severity: WARNING
Probable Cause: Indicates that an unexpected switch reboot has occurred in the middle of the DHCP Auto Deployment (DAD) session.
Recommended Action: No action is required.
Message: DHCP Auto-Deployment parameter error.
Message Type: LOG
Severity: ERROR
Probable Cause: Indicates that a parameter (/etc/fabos/dad/dadparams) error has occurred.
Recommended Action: No action is required.
Message: DHCP Auto-Deployment wait for principle node timeout.
Message Type: LOG
Severity: ERROR
Probable Cause: Indicates that the secondary node has not found the DHCP Auto Deployment (DAD) principle node in the cluster.
Recommended Action: No action is required.
Message: DHCP Auto-Deployment principle node in cluster is not in principle role.
Message Type: LOG
Severity: ERROR
Probable Cause: Indicates that the secondary node has found the DHCP Auto Deployment (DAD) principle node in the cluster, but the principle node is not in principle role.
Recommended Action: No action is required.
Message: DHCP Auto-Deployment timeout when wait for CLI ready.
Message Type: LOG
Severity: ERROR
Probable Cause: Indicates that the Network OS CLI has failed to start up
Recommended Action: No action is required.
Message: DHCP Auto-Deployment timeout when running local command.
Message Type: LOG
Severity: ERROR
Probable Cause: Indicates that the local command was running for a long time.
Recommended Action: No action is required.
Message: DHCP Auto-Deployment secondary node timeout when joining cluster.
Message Type: LOG
Severity: ERROR
Probable Cause: Indicates that the secondary node was taking long time to join the cluster.
Recommended Action: No action is required.
Message: DHCP Auto-Deployment fail to copy running-config startup-config.
Message Type: LOG
Severity: ERROR
Probable Cause: Indicates that DHCP Auto Deployment (DAD) has failed to copy the running configuration to the startup configuration.
Recommended Action: No action is required.
Message: DHCP Auto-Deployment secondary node fail to notify principle node.
Message Type: LOG
Severity: ERROR
Probable Cause: Indicates that the secondary node has failed to send update to the principle node.
Recommended Action: No action is required.
Message: DHCP Auto-Deployment succeed to download option 239 script.
Message Type: LOG
Severity: INFO
Probable Cause: Indicates that the option 239 script is downloaded.
Recommended Action: No action is required.
Message: DHCP Auto-Deployment starts option 239 script.
Message Type: LOG
Severity: INFO
Probable Cause: Indicates that the option 239 script starts to run.
Recommended Action: No action is required.
Message: XMC Discovery Succeed
Message Type: LOG
Severity: INFO
Probable Cause: Indicates that Cloud Connector Discovery Succeed.
Recommended Action: No action is required.