You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This reports the time of the last reboot of the component
Does this indicate the time at which the reboot was initiated by the user/ the component going down? or does it indicate the time at which the component came back up to oper-status ACTIVE?
boot-time:
This timestamp indicates the time that the system was last restarted.
up-time:
The amount of time since the network operating system was initialized
What is the difference between restarted and rebooted in this context? Linux boot-time usually refers to /proc/stat btime. Is that a valid for the boot-time leaf? For platforms with multiple components like Line Cards and Fabric Cards, (with and without CPU), there can be different boot-time/up-time per component. Would it be possible to have enhance ocplatform to contain a component-boot-time/component-up-time for individual components?
The text was updated successfully, but these errors were encountered:
IMO, /components/component/state/last-reboot-time should represent the time which a component has booted up. I will propose this clarification to the yang description for review.
Does this indicate the time at which the reboot was initiated by the user/ the component going down? or does it indicate the time at which the component came back up to oper-status ACTIVE?
What is the difference between restarted and rebooted in this context? Linux boot-time usually refers to /proc/stat btime. Is that a valid for the boot-time leaf? For platforms with multiple components like Line Cards and Fabric Cards, (with and without CPU), there can be different boot-time/up-time per component. Would it be possible to have enhance ocplatform to contain a component-boot-time/component-up-time for individual components?
The text was updated successfully, but these errors were encountered: