NPar uptime

[Dana IT Unix Sysmgt.Tea]

Does anyone know a way to determine the uptime of an NPar when it is running VPars? We have some NPars that have been running a very long time where the VPars have been rebooted regularly but I don't believe that the NPar has actually been cycled since 1970.
Is it really helpful or valuable to ever boot an NPar since it would really only be a cycle of vpmon?
How long do people normally run an NPar between boots (where the NPar runs VPars which are booted regularly).
Appreciate any input

[Javed Khan_1]

Hi,

Go through the console log

Javed

[Michael Steele_2]

Hi

Why wouldn't the uptime from the Npar O/S command line be what you want?

I managed 5 Superdomes and they stayed up for years and we didn't worry about.

Unless you see a problem, then don't worry about it unless you want the training and to review the procedure, then its a good thing. Find the time to do it if you never have.

[Torsten.]

IMHO there is a small chance to find boot related entries in MP log, But since this is a FIFO, this information may be already gone.

Same for "vparstatus -e".

But who cares and why?

;-)

[Dana IT Unix Sysmgt.Tea]

Zero pointed my response.

We were kind of wondering on Friday how long our npars have been running and could not come up with a good answer.

We have a schedule to make sure vpars get booted every month and are wondering if people regularly boot npars or not. Its a pretty simple setup and not likely to get a memory leak, but can it run forever without a reboot?

I've requested HP delete the SEP response.

SEP