platform

airflowCorrected

Table 1. airflowCorrected properties

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

Table 2. airflowMismatch properties

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

Table 3. componentBooting properties

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

Table 4. componentDown properties

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

Table 5. componentFailed properties

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

Table 6. componentInserted properties

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

Table 7. componentLocatorDisabled properties

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

Table 8. componentLocatorEnabled properties

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.

componentPowerDown

Table 9. componentPowerDown properties

Property name

Value

Application name

platform

Event name

componentPowerDown

Default severity

critical

Message format string

Component type slot is being powered down due to insufficient power capacity

Cause

The componentPowerDown event is generated when a component is being powered off by the active control module as a means to bring the overall power consumption of the chassis down to a level the available power supplies are able to accommodate.

Effect

The specified component is powering down.

componentPowerUp

Table 10. componentPowerUp properties

Property name

Value

Application name

platform

Event name

componentPowerUp

Default severity

warning

Message format string

Component type slot is being powered up due to sufficient power capacity

Cause

The componentPowerUp event is generated when a component is being powered on by the active control module, following on from a power down as a result of insufficient power supplies. This event is not generated during normal power on events.

Effect

The specified component is powering on.

componentRemoved

Table 11. componentRemoved properties

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

Table 12. componentRestarted properties

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

Table 13. componentTemperatureExceeded properties

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

Table 14. componentTemperatureFailure properties

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

Table 15. componentTemperatureNormal properties

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

Table 16. componentUp properties

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

Table 17. controlModuleActivityChange properties

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

Table 18. controlModuleConfigSynchronized properties

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

Table 19. controlModuleImageSynchronized properties

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

Table 20. controlModuleInSync properties

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

Table 21. controlModuleOverlaySynchronized properties

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

Table 22. controlModuleSyncLost properties

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

Table 23. controlModuleSyncStart properties

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

Table 24. fantrayEmpty properties

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

Table 25. linecardCapacityDegraded properties

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

Table 26. linecardCapacityNormal properties

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

Table 27. platformLowPower properties

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

Table 28. platformLowReservePower properties

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.

platformNoPowerRedundancy

Table 29. platformNoPowerRedundancy properties

Property name

Value

Application name

platform

Event name

platformNoPowerRedundancy

Default severity

warning

Message format string

Power redundancy based on mode redundancy_mode is not available, required PSUs required_psus, operational PSUs active_psus

Cause

The available PSUs are not able to accomodate the configured power redundancy mode.

Effect

The desired power redundancy is not available.

platformNormalPower

Table 30. platformNormalPower properties

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.

platformPowerRedundancyRecovered

Table 31. platformPowerRedundancyRecovered properties

Property name

Value

Application name

platform

Event name

platformPowerRedundancyRecovered

Default severity

informational

Message format string

Power redundancy based on mode redundancy_mode is available, required PSUs required_psus, operational PSUs active_psus

Cause

The available PSUs are able to accomodate the configured power redundancy mode.

Effect

The desired power redundancy is available.

psuInputDown

Table 32. psuInputDown properties

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

Table 33. psuInputUp properties

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

Table 34. psuOutputDown properties

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

Table 35. psuOutputUp properties

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

Table 36. psuTemperatureFault properties

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

Table 37. psuTemperatureNormal properties

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

Table 38. systemInServiceSoftwareUpgrade properties

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

Table 39. systemReboot properties

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

Table 40. systemWarmReboot properties

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

Table 41. systemWarmRebootAborted properties

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.