platform
airflowCorrected
airflowCorrected:platform
Property name | Value |
---|---|
Application name | platform |
Event name | airflowCorrected |
Default severity | notice |
Message format string | The type in slot slot now matches the dominant airflow of other modules in the system |
Cause | The specified module is now part of the majority (either front to back, or back to front) fans + PSUs in the system. This clearance is triggered when a module moves from being part of the minority to the majority, typically through other modules being plugged/unplugged. |
Effect | The specified module is providing correct airflow to the system. |
airflowMismatch
airflowMismatch:platform
Property name | Value |
---|---|
Application name | platform |
Event name | airflowMismatch |
Default severity | critical |
Message format string | The type in slot slot does not match the airflow of other modules in the system |
Cause | The inserted module does not match the airflow direction of other modules in the system. |
Effect | The system is working with inefficient cooling, and may trigger thermal protection. |
componentBooting
componentBooting:platform
Property name | Value |
---|---|
Application name | platform |
Event name | componentBooting |
Default severity | informational |
Message format string | Component type slot has started initialization |
Cause |
The componentBooting event is generated when the active control module has started initializing the component. |
Effect | The specified component has started initializing. |
componentDown
componentDown:platform
Property name | Value |
---|---|
Application name | platform |
Event name | componentDown |
Default severity | critical |
Message format string | Component type slot is no longer operational |
Cause |
The componentDown event is generated when a component has transitioned from any other operational state to the down state. |
Effect | The specified component is now down. |
componentFailed
componentFailed:platform
Property name | Value |
---|---|
Application name | platform |
Event name | componentFailed |
Default severity | critical |
Message format string | Component type slot has failed, reason reason |
Cause | The componentFailed event is generated when a component has transitioned from any other operational state to the failed state. |
Effect | The specified component is now failed. |
componentInserted
componentInserted:platform
Property name | Value |
---|---|
Application name | platform |
Event name | componentInserted |
Default severity | notice |
Message format string | Component type slot has been inserted into the system |
Cause | The componentInserted event is generated when a component has been initially detected by the active control module. |
Effect | The specified component is detected. |
componentLocatorDisabled
componentLocatorDisabled:platform
Property name | Value |
---|---|
Application name | platform |
Event name | componentLocatorDisabled |
Default severity | notice |
Message format string | Locator LED disabled on type slot |
Cause |
The componentLocatorDisabled event is generated when the locator LED for the component has been disabled, either via timeout, or via operator action. |
Effect | The specified component's LED is no longer flashing with locator functionality. |
componentLocatorEnabled
componentLocatorEnabled:platform
Property name | Value |
---|---|
Application name | platform |
Event name | componentLocatorEnabled |
Default severity | notice |
Message format string | Locator LED enabled on type slot for duration seconds |
Cause | The componentLocatorEnabled event is generated when the locator LED for the component has been enabled by an operator action. |
Effect | The specified component's LED is now flashing with locator functionality. |
componentRemoved
componentRemoved:platform
Property name | Value |
---|---|
Application name | platform |
Event name | componentRemoved |
Default severity | critical |
Message format string | Component type slot has been removed from the system |
Cause | The componentRemoved event is generated when a component has is no longer detected in the system. This does not necessarily indicate that the component has been physically removed, but indicates that it is no longer detected by the active control module. |
Effect | The specified component is no longer detected by the active control module. |
componentRestarted
componentRestarted:platform
Property name | Value |
---|---|
Application name | platform |
Event name | componentRestarted |
Default severity | critical |
Message format string | Component type slot has been restarted |
Cause |
The componentRestarting event is generated when the a component has been restarted. |
Effect | The specified component has been restarted. |
componentTemperatureExceeded
componentTemperatureExceeded:platform
Property name | Value |
---|---|
Application name | platform |
Event name | componentTemperatureExceeded |
Default severity | warning |
Message format string | Component type slot has exceeded its temperature threshold, current temperature temperatureC |
Cause |
The componentTemperatureExceeded event is generated when the component has exceeded its temperature threshold. |
Effect | The specified component has a temperature sensor that is overheating, the component may shut down by thermal protection. |
componentTemperatureFailure
componentTemperatureFailure:platform
Property name | Value |
---|---|
Application name | platform |
Event name | componentTemperatureFailure |
Default severity | warning |
Message format string | Component type slot has exceeded its safe operating temperature, component will be powered down in 10 seconds. Current temperature temperatureC |
Cause |
The componentTemperatureFailure event is generated when the component has exceeded its maximum temperature. |
Effect | The specified component has a temperature sensor that has overheated, the component will shut down in 10 seconds for thermal protection. |
componentTemperatureNormal
componentTemperatureNormal:platform
Property name | Value |
---|---|
Application name | platform |
Event name | componentTemperatureNormal |
Default severity | notice |
Message format string | Component type slot temperature is now normal, current temperature temperatureC |
Cause | The componentTemperatureNormal event is generated when the component has recovered from a temperature exceeded state. |
Effect | The specified component is now within temperature operating limits. |
componentUp
componentUp:platform
Property name | Value |
---|---|
Application name | platform |
Event name | componentUp |
Default severity | notice |
Message format string | Component type slot is now operational |
Cause |
The componentUp event is generated when a component has transitioned from any other operational state to the up state. |
Effect | The specified component is now up. |
controlModuleActivityChange
controlModuleActivityChange:platform
Property name | Value |
---|---|
Application name | platform |
Event name | controlModuleActivityChange |
Default severity | critical |
Message format string | Control module slot has become activity_state |
Cause | The controlModuleActivityChange event is generated when there has been an activity change on either control module. |
Effect | The specified control module has transitioned to the specified state. |
controlModuleConfigSynchronized
controlModuleConfigSynchronized:platform
Property name | Value |
---|---|
Application name | platform |
Event name | controlModuleConfigSynchronized |
Default severity | informational |
Message format string | Configuration synchronization with standby control module standby_slot has succeeded |
Cause |
Configuration has been successfully synchronized between the active and standby control modules. |
Effect | The standby control module now has the same configuration as the active. |
controlModuleImageSynchronized
controlModuleImageSynchronized:platform
Property name | Value |
---|---|
Application name | platform |
Event name | controlModuleImageSynchronized |
Default severity | informational |
Message format string | Image synchronization with standby control module standby_slot has succeeded |
Cause |
Images have been successfully synchronized between the active and standby control modules. |
Effect | The standby control module now has the same images as the active. |
controlModuleInSync
controlModuleInSync:platform
Property name | Value |
---|---|
Application name | platform |
Event name | controlModuleInSync |
Default severity | informational |
Message format string | Active and standby control modules are now synchronized |
Cause | All synchronization activities have completed between the active and standby control modules. |
Effect | The standby control module is now ready for a control module switchover, if necessary. |
controlModuleOverlaySynchronized
controlModuleOverlaySynchronized:platform
Property name | Value |
---|---|
Application name | platform |
Event name | controlModuleOverlaySynchronized |
Default severity | informational |
Message format string | Overlay synchronization with standby control module standby_slot has succeeded |
Cause |
Overlays have been successfully synchronized between the active and standby control modules. |
Effect | The standby control module now has the same overlay as the active. |
controlModuleSyncLost
controlModuleSyncLost:platform
Property name | Value |
---|---|
Application name | platform |
Event name | controlModuleSyncLost |
Default severity | critical |
Message format string | Active control module has lost visibility of the standby control module |
Cause | Connection between the active and standby control modules has been lost. |
Effect | The standby control module is no longer capable of taking over in the event of a failure of the active, no configuration or images are being synchronized. |
controlModuleSyncStart
controlModuleSyncStart:platform
Property name | Value |
---|---|
Application name | platform |
Event name | controlModuleSyncStart |
Default severity | informational |
Message format string | Active and standby control modules are now synchronizing synchronization_category |
Cause |
A synchronization has been triggered between the active and standby control modules. |
Effect | Configuration, images, or persistent storage is being synchronized between the active and standby control module. |
fantrayEmpty
fantrayEmpty:platform
Property name | Value |
---|---|
Application name | platform |
Event name | fantrayEmpty |
Default severity | critical |
Message format string | Component fan-tray slot is not present in the system |
Cause |
The fantrayEmpty event is generated when a fan-tray has transitioned from any other operational state to the empty state, or is never present. |
Effect | The system may have cooling issues. |
linecardCapacityDegraded
linecardCapacityDegraded:platform
Property name | Value |
---|---|
Application name | platform |
Event name | linecardCapacityDegraded |
Default severity | critical |
Message format string | Linecard slot forwarding complex forwarding-complex fabric capacity degraded |
Cause | The specified linecard's forwarding complex has insufficient operational fabric links. |
Effect | Packets may be dropped if the linecard's forwarding complex is sending and receiving significant amounts of traffic to the fabric. |
linecardCapacityNormal
linecardCapacityNormal:platform
Property name | Value |
---|---|
Application name | platform |
Event name | linecardCapacityNormal |
Default severity | informational |
Message format string | Linecard slot forwarding complex forwarding-complex fabric capacity normal |
Cause | The specified linecard's forwarding complex has sufficient operational fabric links again. |
Effect | Normal behavior is restored for sending and receiving traffic to the fabric. |
platformLowPower
platformLowPower:platform
Property name | Value |
---|---|
Application name | platform |
Event name | platformLowPower |
Default severity | emergency |
Message format string | Insufficient power for currently installed components, current_powerW available, required_powerW required |
Cause | Available power from operational power supplies is insufficient to power all components in the system. |
Effect | Components in the system will be powered down until required power is lower than what is supplied by operational power supplies. |
platformLowReservePower
platformLowReservePower:platform
Property name | Value |
---|---|
Application name | platform |
Event name | platformLowReservePower |
Default severity | critical |
Message format string | Insufficient reserve power for currently installed components, current_powerW available, required_powerW required |
Cause | Available power is less than one power supply capacity extra to power all components in the system. |
Effect | Power will be insufficient if one operational power supply is lost. |
platformNormalPower
platformNormalPower:platform
Property name | Value |
---|---|
Application name | platform |
Event name | platformNormalPower |
Default severity | informational |
Message format string | Sufficient power for currently installed components, current_powerW available, required_powerW required |
Cause | Available power from operational power supplies is sufficient to power all components in the system. |
Effect | Enough power is available. |
psuInputDown
psuInputDown:platform
Property name | Value |
---|---|
Application name | platform |
Event name | psuInputDown |
Default severity | warning |
Message format string | Power input on power-supply slot is down |
Cause |
Input fault on the specified power supply is set. |
Effect | The specified power supply can no longer supply power to the system. |
psuInputUp
psuInputUp:platform
Property name | Value |
---|---|
Application name | platform |
Event name | psuInputUp |
Default severity | notice |
Message format string | Power input on power-supply slot is up |
Cause |
Input fault on the specified power supply is clear. |
Effect | The specified power supply can now supply power to the system. |
psuOutputDown
psuOutputDown:platform
Property name | Value |
---|---|
Application name | platform |
Event name | psuOutputDown |
Default severity | warning |
Message format string | Power output on power-supply slot is down |
Cause |
Output fault on the specified power supply is set. |
Effect | The specified power supply can no longer supply power to the system. |
psuOutputUp
psuOutputUp:platform
Property name | Value |
---|---|
Application name | platform |
Event name | psuOutputUp |
Default severity | notice |
Message format string | Power output on power-supply slot is up |
Cause |
Output fault on the specified power supply is clear. |
Effect | The specified power supply can now supply power to the system. |
psuTemperatureFault
psuTemperatureFault:platform
Property name | Value |
---|---|
Application name | platform |
Event name | psuTemperatureFault |
Default severity | warning |
Message format string | Component type slot has raised a temperature fault, current temperature temperatureC |
Cause | The psuTemperatureFault event is generated when the power supply raises a temperature fault. |
Effect | The power supply is overheating, and may shut down by thermal protection. |
psuTemperatureNormal
psuTemperatureNormal:platform
Property name | Value |
---|---|
Application name | platform |
Event name | psuTemperatureNormal |
Default severity | notice |
Message format string | Component type slot temperature fault is now clear, current temperature temperatureC |
Cause | The psuTemperatureNormal event is generated when the power supply recovered from a temperature fault state. |
Effect | The power supply is now within temperature operating limits. |
systemInServiceSoftwareUpgrade
systemInServiceSoftwareUpgrade:platform
Property name | Value |
---|---|
Application name | platform |
Event name | systemInServiceSoftwareUpgrade |
Default severity | critical |
Message format string | System is upgrading from old_version to new_version, utilizing warm reboot |
Cause | The systemInServiceSoftwareUpgrade event is generated when a software triggered in service software upgrade request has been made. |
Effect | The control and management plane of the system will go offline, the datapath will continue forwarding based on current state. The system will upgrade the kernel, operating system, and/or applications as needed. |
systemReboot
systemReboot:platform
Property name | Value |
---|---|
Application name | platform |
Event name | systemReboot |
Default severity | critical |
Message format string | System going down for reboot |
Cause | The systemReboot event is generated when a software triggered reboot has been made. |
Effect | The system will go offline for reboot. |
systemWarmReboot
systemWarmReboot:platform
Property name | Value |
---|---|
Application name | platform |
Event name | systemWarmReboot |
Default severity | critical |
Message format string | System going down for warm reboot |
Cause | The systemWarmReboot event is generated when a software triggered warm reboot has been made. |
Effect | The control and management plane of the system will go offline, the datapath will continue forwarding based on current state. |
systemWarmRebootAborted
systemWarmRebootAborted:platform
Property name | Value |
---|---|
Application name | platform |
Event name | systemWarmRebootAborted |
Default severity | critical |
Message format string | System has aborted a requested warm reboot due to reason |
Cause | The systemWarmRebootAborted event is generated when a software triggered warm reboot request has been aborted, typically due to unsupported configuration. |
Effect | The in progress warm reboot has been aborted, no effect to system configuration or state. |