Monitor and troubleshoot
Documents under this category describe tools that can help you monitor, diagnose, and troubleshoot SR Linux software. This section also includes Log Event documentation to help you interpret log messages generated by SR Linux software.
- Event Handler Guide
  This document describes the functionality and configuration for the event handler framework on the Nokia Service Router Linux (SR Linux).
- Log Events Guide
  This document provides guidance for operators to interpret log events for the Nokia Service Router Linux (SR Linux).
- OAM and Diagnostics Guide
- Troubleshooting Toolkit
  This document describes how to use and configure diagnostic tools for the Nokia Service Router Linux (SR Linux).

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.
Raising event	airflowMismatch
Clearing event	N/A

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.
Raising event	N/A
Clearing event	airflowCorrected

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.
Raising event	N/A
Clearing event	N/A

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.
Raising event	N/A
Clearing event	componentUp

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.
Raising event	N/A
Clearing event	componentUp

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.
Raising event	componentRemoved, fantrayEmpty
Clearing event	N/A

componentInsertedInInvalidSlot

Table 7. componentInsertedInInvalidSlot properties
Property name	Value
Application name	platform
Event name	componentInsertedInInvalidSlot
Default severity	warning
Message format string	Component type is inserted in invalid slot slot
Cause	The componentInsertedInInvalidSlot event is generated when a component is being inserted in invalid slot.
Effect	The specified component will not be taken into use.
Raising event	N/A
Clearing event	N/A

componentLocatorDisabled

Table 8. 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.
Raising event	N/A
Clearing event	N/A

componentLocatorEnabled

Table 9. 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.
Raising event	N/A
Clearing event	N/A

componentPowerDown

Table 10. 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.
Raising event	N/A
Clearing event	componentPowerUp

componentPowerUp

Table 11. 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.
Raising event	componentPowerDown
Clearing event	N/A

componentRemoved

Table 12. 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.
Raising event	N/A
Clearing event	componentInserted

componentRestarted

Table 13. 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.
Raising event	N/A
Clearing event	N/A

componentTemperatureExceeded

Table 14. 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.
Raising event	N/A
Clearing event	componentTemperatureNormal

componentTemperatureFailure

Table 15. 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.
Raising event	N/A
Clearing event	componentTemperatureNormal

componentTemperatureNormal

Table 16. 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.
Raising event	componentTemperatureExceeded, componentTemperatureFailure
Clearing event	N/A

componentUp

Table 17. 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.
Raising event	componentDown, componentFailed
Clearing event	N/A

controlModuleActivityChange

Table 18. 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.
Raising event	N/A
Clearing event	N/A

controlModuleConfigSynchronized

Table 19. 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.
Raising event	N/A
Clearing event	N/A

controlModuleImageSynchronized

Table 20. 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.
Raising event	N/A
Clearing event	N/A

controlModuleInSync

Table 21. 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.
Raising event	controlModuleSyncLost
Clearing event	N/A

controlModuleOverlaySynchronized

Table 22. 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.
Raising event	N/A
Clearing event	N/A

controlModuleSyncLost

Table 23. 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.
Raising event	N/A
Clearing event	controlModuleInSync

controlModuleSyncStart

Table 24. 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.
Raising event	N/A
Clearing event	N/A

fantrayEmpty

Table 25. 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.
Raising event	N/A
Clearing event	componentInserted

fips140ConfiguredOperDown

Table 26. fips140ConfiguredOperDown properties
Property name	Value
Application name	platform
Event name	fips140ConfiguredOperDown
Default severity	critical
Message format string	FIPS-140 is enabled operationally down for reason down-reason
Cause	FIPS-140 has been successfully configured but it is oper-down because of an error.
Effect	None
Raising event	N/A
Clearing event	N/A

fips140ConfiguredOperUp

Table 27. fips140ConfiguredOperUp properties
Property name	Value
Application name	platform
Event name	fips140ConfiguredOperUp
Default severity	notice
Message format string	FIPS-140 has been enabled and fully operational
Cause	FIPS-140 is successfully enabled and operational.
Effect	None
Raising event	N/A
Clearing event	N/A

fips140ConfiguredWaitingReboot

Table 28. fips140ConfiguredWaitingReboot properties
Property name	Value
Application name	platform
Event name	fips140ConfiguredWaitingReboot
Default severity	notice
Message format string	FIPS-140 is enabled but operationally down until next reboot
Cause	FIPS-140 has been successfully configured.
Effect	FIPS-140 active after next reboot
Raising event	N/A
Clearing event	N/A

fips140NotActive

Table 29. fips140NotActive properties
Property name	Value
Application name	platform
Event name	fips140NotActive
Default severity	notice
Message format string	FIPS-140 is not activated
Cause	FIPS-140 is not configured.
Effect	None
Raising event	N/A
Clearing event	N/A

fips140Removed

Table 30. fips140Removed properties
Property name	Value
Application name	platform
Event name	fips140Removed
Default severity	notice
Message format string	FIPS-140 has been disabled but is operationally up until next reboot
Cause	FIPS-140 has been successfully unconfigured.
Effect	FIPS-140 inactive after next reboot.
Raising event	N/A
Clearing event	N/A

linecardCapacityDegraded

Table 31. 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.
Raising event	N/A
Clearing event	linecardCapacityNormal

linecardCapacityNormal

Table 32. 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.
Raising event	linecardCapacityDegraded
Clearing event	N/A

platformLowPower

Table 33. 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.
Raising event	N/A
Clearing event	platformNormalPower

platformLowReservePower

Table 34. 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.
Raising event	N/A
Clearing event	platformNormalPower

platformNoPowerRedundancy

Table 35. 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.
Raising event	N/A
Clearing event	platformPowerRedundancyRecovered

platformNormalPower

Table 36. 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.
Raising event	platformLowPower, platformLowReservePower
Clearing event	N/A

platformPowerRedundancyRecovered

Table 37. 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.
Raising event	platformNoPowerRedundancy
Clearing event	N/A

psuInputDown

Table 38. 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.
Raising event	N/A
Clearing event	psuInputUp

psuInputUp

Table 39. 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.
Raising event	psuInputDown
Clearing event	N/A

psuOutputDown

Table 40. 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.
Raising event	N/A
Clearing event	psuOutputUp

psuOutputUp

Table 41. 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.
Raising event	psuOutputDown
Clearing event	N/A

psuTemperatureFault

Table 42. 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.
Raising event	N/A
Clearing event	psuTemperatureNormal

psuTemperatureNormal

Table 43. 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.
Raising event	psuTemperatureFault
Clearing event	N/A

systemInServiceSoftwareUpgrade

Table 44. 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.
Raising event	N/A
Clearing event	N/A

systemReboot

Table 45. 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
Raising event	N/A
Clearing event	N/A

systemWarmReboot

Table 46. 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.
Raising event	N/A
Clearing event	N/A

systemWarmRebootAborted

Table 47. 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.
Raising event	N/A
Clearing event	N/A

July 16, 2026