Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarification on last-reboot-time, boot-time and up-time #1171

Open
AnandJyrm opened this issue Aug 24, 2024 · 1 comment · May be fixed by #1179
Open

Clarification on last-reboot-time, boot-time and up-time #1171

AnandJyrm opened this issue Aug 24, 2024 · 1 comment · May be fixed by #1179

Comments

@AnandJyrm
Copy link

  • last-reboot-time:

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?

@dplore
Copy link
Member

dplore commented Sep 9, 2024

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

2 participants