Sponsored Content
Full Discussion: Managed system's uptime
Operating Systems AIX Managed system's uptime Post 302975090 by sunnybee on Wednesday 8th of June 2016 03:34:03 AM
Old 06-08-2016
Managed system's uptime

How to find Physical server uptime from HMC/ ASMI.

Server was in standby mode. We have started the Lpar manually. Server rebooted automatically but no information updated in Lpars's errpt, alog.console or HMC prior to the reboot.
 

9 More Discussions You Might Find Interesting

1. Web Development

managed service reccomendations

Dunno If its ok to post this, but I am looking for a company to manage our linux server. If the company is a specialist in security issues then that would be ideal Thanks Ed (5 Replies)
Discussion started by: edzillion
5 Replies

2. UNIX for Dummies Questions & Answers

Difference between system uptime and last boot time.

My Linux system was last rebooted few hours ago. But it seems little confusing for me to figure out the exact reason behind it. I guess following command should justify what i meant to say. # date Wed May 11 13:22:49 IST 2011 # last | grep "May 10" reboot system boot 2.6.18-194.el5 ... (5 Replies)
Discussion started by: pinga123
5 Replies

3. Shell Programming and Scripting

Extract the uptime from the output of the uptime command

Hi! I want to extract the uptime from the output of the uptime command. The output: 11:53 up 3:02, 2 users, load averages: 0,32 0,34 0,43 I just need the "3:02" part. How can I do this? Dirk (6 Replies)
Discussion started by: Dirk Einecke
6 Replies

4. Solaris

uptime command not showing how long the system has been up

Hello folks, uptime command not shows how long the system has been up. I know it come from a corruption of /var/adm/utmpx file. I've done : cat /dev/null > /var/adm/utmpx Now who and last commands work fine. But uptime still give me back an answer without the "up time". In which... (6 Replies)
Discussion started by: gogol_bordello
6 Replies

5. Shell Programming and Scripting

Managed file transfer

Hello All, Firstly, the systems involved are Solaris 9/10 x86 and SPARC. At present, we have an internally written file transfer system that we use to manage incoming transfers and distribute the files to relevant processing systems. This is based on log watching. Over the years its become... (3 Replies)
Discussion started by: dcarrion87
3 Replies

6. AIX

HMC updates managed system firmware on both T and P sides ?

Hi, I'm planning to update managed system firmware to new release using HMC. This is cite from IBM documentation describing HMC managed system updates: What I know we install new firmware to T side and in case some problems we boot P side and reject new fw on T. So if HMC updates both T and... (0 Replies)
Discussion started by: vilius
0 Replies

7. Solaris

Finding system uptime without login

Hi, Am writing a script where I want to find uptime of certain servers. Is there any command where we can find uptime without login to the server, since the server list is big logging to the server will time consuming. Thanks in advance (7 Replies)
Discussion started by: rogerben
7 Replies

8. Shell Programming and Scripting

Solaris, Perl, and precise system uptime??

OK folks, my first post here.. hope the community can come up with a clever solution. Cross posting this in the Solaris and Shell scripting forums, as problem is scripting problem specifically on Solaris platform. I am trying to detect a host's uptime with greater precision than is offered up... (1 Reply)
Discussion started by: Yeaboem
1 Replies

9. Solaris

Precise system uptime??

OK folks, my first post here.. hope the community can come up with a clever solution. Cross posting this in the Solaris and Shell scripting forums, as problem is scripting problem specifically on Solaris platform. I am trying to detect a host's uptime with greater precision than is offered up... (1 Reply)
Discussion started by: Yeaboem
1 Replies
cimserver(8)						      System Manager's Manual						      cimserver(8)

NAME
cimserver - start or stop the CIM Server; display the version number or running status of the CIM Server SYNOPSIS
cimserver [configProperty=value] ... cimserver -s [ shutdownTimeout = value ] cimserver -v cimserver -h cimserver --help cimserver --version cimserver --status Remarks This command can only be executed by a privileged user. DESCRIPTION
The cimserver command provides a command line interface to stop and start the CIM Server, as well as to display the version number or run- ning status of the CIM Server. After installation, the CIM Server must be started using the cimserver command. If the system is rebooted, the CIM Server will automati- cally restart, with the exception of the case where the CIM Server was shutdown prior to the reboot. Generally, once the CIM Server is started, it is expected to be always running and ready to serve CIM requests. However, if the CIM Server must be stopped and restarted, the cimserver command can be used to shutdown the CIM Server gracefully and restart it at a later time. Starting the CIM Server Issuing the cimserver command without any options starts the CIM Server process. When starting the CIM Server using the cimserver command, the <configProperty=value> syntax can be used to set the configuration properties to be used by the CIM Server. It is important to know that the values specified in the cimserver command apply only to the current CIM Server process that gets started. The default values for the configuration properties do not change. For a list of the CIM Server config- uration properties, see the man page for the cimconfig command. Shutting down the CIM Server Issuing the cimserver command with the -s option stops the CIM Server. Optionally, a timeout value can be specified by setting the shut- downTimeout configuration property. Under normal operation, CIM Server should be able to be shutdown fairly quickly without problem. There are, however, situations that may prevent CIM Server from shutting down within a reasonable amount of time. For example, a provider that is not responding to requests, or a provider that is servicing a long-running CIM request. To handle such situations and to ensure that the CIM Server can be shutdown without having the user wait a long period of time (or indefinitely), a shutdown timeout value is used. The shutdown timeout value is the maximum amount of time (in seconds) the user is willing to wait for the CIM Server to complete all the outstanding CIM operation requests before shutting down the CIM Server. If the specified shutdown timeout period expires, the CIM Server will be shutdown even if there are CIM operations in progress. The shutdown timeout value is a CIM Server configuration property (shut- downTimeout ) that can be changed using the command. The default shutdown timeout value is 10 seconds. A timeout value (in seconds) can be specified in the cimserver command to shutdown the CIM Server using the =value> syntax. This overrides the default shutdown timeout value. The minimum timeout value is 2 seconds. While CIM Server is shutting down, a client connection request will result in a connection error (the same as if the CIM Server were not running). For clients who have already established a connection to the CIM Server, new CIM requests will be rejected with a CIM error indicating that the CIM Server is shutting down. When a client receives a response containing a CIM error indicating that the CIM Server is shutting down, it should close the connection and reconnect to CIM Server at a later time. Options The cimserver command recognizes the following options: -v, --version Display the version number or running status of the CIM Server. -h, --help Display the command usage. --status Display the running status of the CIM Server. -s Stop the CIM Server. Specify the timeout value for shutting down the CIM Server. This can only be used in conjunction with the -s option. The minimum timeout value is 2 seconds. If this is not specified, the default configurable timeout value will be used. configProperty=value Set the value for the specified configuration property to be used in starting the CIM Server. EXIT STATUS
The cimserver command returns one of the following values: 0 Success 1 Error The cimserver --status command returns one of the following values: 0 The CIM Server is running 1 Error 2 The CIM Server is not running When an error occurs, an error message is written to stderr and an error value of 1 is returned. DIAGNOSTICS
unable to connect to CIM Server. CIM Server may not be running. The cimserver command was issued to stop the CIM Server when CIM Server was not running. An exit status value of 1 is returned. Error: Bind failed: Failed to bind socket. The cimserver command was issued to start the CIM Server and the CIM Server was already running. An exit status value of 1 is returned. EXAMPLES
Stop the CIM Server with the default timeout value of 10 seconds. cimserver -s Stop the CIM Server with a timeout value of 5 seconds. cimserver -s shutdownTimeout=5 Start the CIM Server. cimserver Start the CIM Server with the configuration property enableNamespaceAuthorization set to true. cimserver enableNamespaceAuthorization=true Display the version number of the CIM Server. This version number is used to identify the release version of the CIM Server in the OpenPe- gasus release. cimserver -v Display the command usage. cimserver -h SEE ALSO
cimconfig(8). cimserver(8)
All times are GMT -4. The time now is 02:47 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy