(file) Return to CIMOMShutdown.doc CVS log (file) (dir) Up to [Pegasus] / pegasus / doc / WorkPapers

File: [Pegasus] / pegasus / doc / WorkPapers / CIMOMShutdown.doc (download) / (as text)
Revision: 1.2, Thu Dec 13 14:53:30 2001 UTC (22 years, 5 months ago) by mike
Branch: MAIN
CVS Tags: test, preBug9676, postBug9676, pep_88, pegasus25BeforeLicenseUpdate, merge_of_dev, mday-merge-start, mday-merge-pegasus/src/Pegasus/Server, mday-merge-pegasus/src/Pegasus/Common, mday-2-0-patches, local, VERSION_2_1_RELEASE_HEAD, VERSION_2_1_RELEASE_BRANCH, VERSION_2_1_RELEASE, VERSION_2_1_1_RELEASE, VERSION_2_01_01, VERSION_2_00_RC_4, VERSION_2_00_RC_3, VERSION_2_00_RC_2, VERSION_2_00_RC_1, VERSION_2_00_BRANCH, VERSION_1_10, VERSION_1_09, VERSION_1_08, VERSION_1_07, TEST, TASK_PEP328_SOLARIS_NEVADA_PORT, TASK_PEP317_1JUNE_2013, TASK_PEP233_EmbeddedInstSupport-merge_out_trunk, TASK_BUG_5314_IPC_REFACTORING_ROOT, TASK_BUG_5314_IPC_REFACTORING_BRANCH, TASK_BUG_5314_IPC_REFACTORING-V1, TASK_BUG_5191_QUEUE_CONSOLIDATION_ROOT, TASK_BUG_5191_QUEUE_CONSOLIDATION_BRANCH, TASK-TASK_PEP362_RestfulService_branch-root, TASK-TASK_PEP362_RestfulService_branch-merged_out_from_trunk, TASK-TASK_PEP362_RestfulService_branch-merged_in_to_trunk, TASK-TASK_PEP362_RestfulService_branch-merged_in_from_branch, TASK-TASK_PEP362_RestfulService_branch-branch, TASK-TASK-BUG4011_WinLocalConnect-branch-New-root, TASK-TASK-BUG4011_WinLocalConnect-branch-New-merged_out_to_branch, TASK-TASK-BUG4011_WinLocalConnect-branch-New-merged_out_from_trunk, TASK-TASK-BUG4011_WinLocalConnect-branch-New-merged_in_to_trunk, TASK-TASK-BUG4011_WinLocalConnect-branch-New-merged_in_from_branch, TASK-TASK-BUG4011_WinLocalConnect-branch-New-branch, TASK-PEP362_RestfulService-root, TASK-PEP362_RestfulService-merged_out_to_branch, TASK-PEP362_RestfulService-merged_out_from_trunk, TASK-PEP362_RestfulService-merged_in_to_trunk, TASK-PEP362_RestfulService-merged_in_from_branch, TASK-PEP362_RestfulService-branch, TASK-PEP348_SCMO-root, TASK-PEP348_SCMO-merged_out_to_branch, TASK-PEP348_SCMO-merged_out_from_trunk, TASK-PEP348_SCMO-merged_in_to_trunk, TASK-PEP348_SCMO-merged_in_from_branch, TASK-PEP348_SCMO-branch, TASK-PEP328_SOLARIS_NEVADA_PORT_v2-root, TASK-PEP328_SOLARIS_NEVADA_PORT_v2-branch, TASK-PEP328_SOLARIS_NEVADA_PORT-root, TASK-PEP328_SOLARIS_NEVADA_PORT-branch, TASK-PEP328_SOLARIS_IX86_CC_PORT-root, TASK-PEP328_SOLARIS_IX86_CC_PORT-branch-v2, TASK-PEP328_SOLARIS_IX86_CC_PORT-branch, TASK-PEP317_pullop-root, TASK-PEP317_pullop-merged_out_to_branch, TASK-PEP317_pullop-merged_out_from_trunk, TASK-PEP317_pullop-merged_in_to_trunk, TASK-PEP317_pullop-merged_in_from_branch, TASK-PEP317_pullop-branch, TASK-PEP311_WSMan-root, TASK-PEP311_WSMan-branch, TASK-PEP305_VXWORKS-root, TASK-PEP305_VXWORKS-branch-pre-solaris-port, TASK-PEP305_VXWORKS-branch-post-solaris-port, TASK-PEP305_VXWORKS-branch-beta2, TASK-PEP305_VXWORKS-branch, TASK-PEP305_VXWORKS-2008-10-23, TASK-PEP291_IPV6-root, TASK-PEP291_IPV6-branch, TASK-PEP286_PRIVILEGE_SEPARATION-root, TASK-PEP286_PRIVILEGE_SEPARATION-branch, TASK-PEP274_dacim-root, TASK-PEP274_dacim-merged_out_to_branch, TASK-PEP274_dacim-merged_out_from_trunk, TASK-PEP274_dacim-merged_in_to_trunk, TASK-PEP274_dacim-merged_in_from_branch, TASK-PEP274_dacim-branch, TASK-PEP268_SSLClientCertificatePropagation-root, TASK-PEP268_SSLClientCertificatePropagation-merged_out_to_branch, TASK-PEP268_SSLClientCertificatePropagation-merged_out_from_trunk, TASK-PEP268_SSLClientCertificatePropagation-merged_in_to_trunk, TASK-PEP268_SSLClientCertificatePropagation-merged_in_from_branch, TASK-PEP268_SSLClientCertificatePropagation-branch, TASK-PEP267_SLPReregistrationSupport-root, TASK-PEP267_SLPReregistrationSupport-merging_out_to_branch, TASK-PEP267_SLPReregistrationSupport-merging_out_from_trunk, TASK-PEP267_SLPReregistrationSupport-merged_out_to_branch, TASK-PEP267_SLPReregistrationSupport-merged_out_from_trunk, TASK-PEP267_SLPReregistrationSupport-merged_in_to_trunk, TASK-PEP267_SLPReregistrationSupport-merged_in_from_branch, TASK-PEP267_SLPReregistrationSupport-branch, TASK-PEP250_RPMProvider-root, TASK-PEP250_RPMProvider-merged_out_to_branch, TASK-PEP250_RPMProvider-merged_out_from_trunk, TASK-PEP250_RPMProvider-merged_in_to_trunk, TASK-PEP250_RPMProvider-merged_in_from_branch, TASK-PEP250_RPMProvider-branch, TASK-PEP245_CimErrorInfrastructure-root, TASK-PEP245_CimErrorInfrastructure-merged_out_to_branch, TASK-PEP245_CimErrorInfrastructure-merged_out_from_trunk, TASK-PEP245_CimErrorInfrastructure-merged_in_to_trunk, TASK-PEP245_CimErrorInfrastructure-merged_in_from_branch, TASK-PEP245_CimErrorInfrastructure-branch, TASK-PEP241_OpenPegasusStressTests-root, TASK-PEP241_OpenPegasusStressTests-merged_out_to_branch, TASK-PEP241_OpenPegasusStressTests-merged_out_from_trunk, TASK-PEP241_OpenPegasusStressTests-merged_in_to_trunk, TASK-PEP241_OpenPegasusStressTests-merged_in_from_branch, TASK-PEP241_OpenPegasusStressTests-branch, TASK-Bugs5690_3913_RemoteCMPI-root, TASK-Bugs5690_3913_RemoteCMPI-merged_out_to_branch, TASK-Bugs5690_3913_RemoteCMPI-merged_out_from_trunk, TASK-Bugs5690_3913_RemoteCMPI-merged_in_to_trunk, TASK-Bugs5690_3913_RemoteCMPI-merged_in_from_branch, TASK-Bugs5690_3913_RemoteCMPI-branch, TASK-Bug2102_RCMPIWindows-root, TASK-Bug2102_RCMPIWindows-merged_out_to_branch, TASK-Bug2102_RCMPIWindows-merged_out_from_trunk, TASK-Bug2102_RCMPIWindows-merged_in_to_trunk, TASK-Bug2102_RCMPIWindows-merged_in_from_branch, TASK-Bug2102_RCMPIWindows-branch, TASK-Bug2102Final-root, TASK-Bug2102Final-merged_out_to_branch, TASK-Bug2102Final-merged_out_from_trunk, TASK-Bug2102Final-merged_in_to_trunk, TASK-Bug2102Final-merged_in_from_branch, TASK-Bug2102Final-branch, TASK-Bug2021_RemoteCMPIonWindows-root, TASK-Bug2021_RemoteCMPIonWindows-merged_out_to_branch, TASK-Bug2021_RemoteCMPIonWindows-merged_out_from_trunk, TASK-Bug2021_RemoteCMPIonWindows-merged_in_to_trunk, TASK-Bug2021_RemoteCMPIonWindows-merged_in_from_branch, TASK-Bug2021_RemoteCMPIonWindows-branch, TASK-Bug2021_RCMPIonWindows-root, TASK-Bug2021_RCMPIonWindows-merged_out_to_branch, TASK-Bug2021_RCMPIonWindows-merged_out_from_trunk, TASK-Bug2021_RCMPIonWindows-merged_in_to_trunk, TASK-Bug2021_RCMPIonWindows-merged_in_from_branch, TASK-Bug2021_RCMPIonWindows-branch, TASK-BUG7240-root, TASK-BUG7240-branch, TASK-BUG7146_SqlRepositoryPrototype-root, TASK-BUG7146_SqlRepositoryPrototype-merged_out_to_branch, TASK-BUG7146_SqlRepositoryPrototype-merged_out_from_trunk, TASK-BUG7146_SqlRepositoryPrototype-merged_in_to_trunk, TASK-BUG7146_SqlRepositoryPrototype-merged_in_from_branch, TASK-BUG7146_SqlRepositoryPrototype-branch, TASK-BUG4011_WinLocalConnect-root, TASK-BUG4011_WinLocalConnect-merged_out_to_branch, TASK-BUG4011_WinLocalConnect-merged_out_from_trunk, TASK-BUG4011_WinLocalConnect-merged_in_to_trunk, TASK-BUG4011_WinLocalConnect-merged_in_from_branch, TASK-BUG4011_WinLocalConnect-branch-New, TASK-BUG4011_WinLocalConnect-branch, STABLE, SLPPERFINST-root, SLPPERFINST-branch, RELEASE_2_9_2-RC2, RELEASE_2_9_2-RC1, RELEASE_2_9_2, RELEASE_2_9_1-RC1, RELEASE_2_9_1, RELEASE_2_9_0-RC1, RELEASE_2_9_0-FC, RELEASE_2_9_0, RELEASE_2_9-root, RELEASE_2_9-branch, RELEASE_2_8_2-RC1, RELEASE_2_8_2, RELEASE_2_8_1-RC1, RELEASE_2_8_1, RELEASE_2_8_0_BETA, RELEASE_2_8_0-RC2, RELEASE_2_8_0-RC1, RELEASE_2_8_0-FC, RELEASE_2_8_0, RELEASE_2_8-root, RELEASE_2_8-branch, RELEASE_2_7_3-RC1, RELEASE_2_7_3, RELEASE_2_7_2-RC1, RELEASE_2_7_2, RELEASE_2_7_1-RC1, RELEASE_2_7_1, RELEASE_2_7_0-RC1, RELEASE_2_7_0-BETA, RELEASE_2_7_0, RELEASE_2_7-root, RELEASE_2_7-branch, RELEASE_2_6_3-RC2, RELEASE_2_6_3-RC1, RELEASE_2_6_3, RELEASE_2_6_2-RC1, RELEASE_2_6_2, RELEASE_2_6_1-RC1, RELEASE_2_6_1, RELEASE_2_6_0-RC1, RELEASE_2_6_0-FC, RELEASE_2_6_0, RELEASE_2_6-root, RELEASE_2_6-branch-clean, RELEASE_2_6-branch, RELEASE_2_5_5-RC2, RELEASE_2_5_5-RC1, RELEASE_2_5_5, RELEASE_2_5_4-RC2, RELEASE_2_5_4-RC1, RELEASE_2_5_4, RELEASE_2_5_3-RC1, RELEASE_2_5_3, RELEASE_2_5_2-RC1, RELEASE_2_5_2, RELEASE_2_5_1-RC1, RELEASE_2_5_1, RELEASE_2_5_0-RC1, RELEASE_2_5_0, RELEASE_2_5-root, RELEASE_2_5-branch, RELEASE_2_4_FC_CANDIDATE_1, RELEASE_2_4_3, RELEASE_2_4_2, RELEASE_2_4_1-BETA3, RELEASE_2_4_1-BETA2, RELEASE_2_4_1-BETA1, RELEASE_2_4_1, RELEASE_2_4_0-RC3, RELEASE_2_4_0-RC2, RELEASE_2_4_0, RELEASE_2_4-root, RELEASE_2_4-branch, RELEASE_2_3_2-testfreeze, RELEASE_2_3_2-root, RELEASE_2_3_2-releasesnapshot, RELEASE_2_3_2-branch-freeze, RELEASE_2_3_2-branch, RELEASE_2_3_1-root, RELEASE_2_3_1-branch, RELEASE_2_3_0-root, RELEASE_2_3_0-msg-freeze, RELEASE_2_3_0-branch, RELEASE_2_2_1-snapshot, RELEASE_2_2_0_0-release, RELEASE_2_2_0-root, RELEASE_2_2_0-branch, RELEASE_2_2-root, RELEASE_2_14_1, RELEASE_2_14_0-RC2, RELEASE_2_14_0-RC1, RELEASE_2_14_0, RELEASE_2_14-root, RELEASE_2_14-branch, RELEASE_2_13_0-RC2, RELEASE_2_13_0-RC1, RELEASE_2_13_0-FC, RELEASE_2_13_0, RELEASE_2_13-root, RELEASE_2_13-branch, RELEASE_2_12_1-RC1, RELEASE_2_12_1, RELEASE_2_12_0-RC1, RELEASE_2_12_0-FC, RELEASE_2_12_0, RELEASE_2_12-root, RELEASE_2_12-branch, RELEASE_2_11_2-RC1, RELEASE_2_11_2, RELEASE_2_11_1-RC1, RELEASE_2_11_1, RELEASE_2_11_0-RC1, RELEASE_2_11_0-FC, RELEASE_2_11_0, RELEASE_2_11-root, RELEASE_2_11-branch, RELEASE_2_10_1-RC1, RELEASE_2_10_1, RELEASE_2_10_0-RC2, RELEASE_2_10_0-RC1, RELEASE_2_10_0, RELEASE_2_10-root, RELEASE_2_10-branch, PRE_LICENSE_UPDATE_2003, PREAUG25UPDATE, POST_LICENSE_UPDATE_2003, POSTAUG25UPDATE, PEP286_PRIVILEGE_SEPARATION_ROOT, PEP286_PRIVILEGE_SEPARATION_CODE_FREEZE, PEP286_PRIVILEGE_SEPARATION_BRANCH, PEP286_PRIVILEGE_SEPARATION_1, PEP244_ServerProfile-root, PEP244_ServerProfile-branch, PEP233_EmbeddedInstSupport-root, PEP233_EmbeddedInstSupport-branch, PEP217_PRE_BRANCH, PEP217_POST_BRANCH, PEP217_BRANCH, PEP214ROOT, PEP214BRANCH, PEP214-root, PEP214-branch, PEP213_SIZE_OPTIMIZATIONS, PEP-214B-root, PEGASUS_FC_VERSION_2_2, PEGASUS_2_5_0_PerformanceDev-string-end, PEGASUS_2_5_0_PerformanceDev-rootlt, PEGASUS_2_5_0_PerformanceDev-root, PEGASUS_2_5_0_PerformanceDev-r2, PEGASUS_2_5_0_PerformanceDev-r1, PEGASUS_2_5_0_PerformanceDev-lit-end, PEGASUS_2_5_0_PerformanceDev-buffer-end, PEGASUS_2_5_0_PerformanceDev-branch, PEGASUS_2_5_0_PerformanceDev-AtomicInt-branch, PEG25_IBM_5_16_05, NPEGASUS_2_5_0_PerformanceDev-String-root, NNPEGASUS_2_5_0_PerformanceDev-String-branch, Makefile, MONITOR_CONSOLIDATION_2_5_BRANCH, LOCAL_ASSOCPROV-ROOT, LOCAL_ASSOCPROV-BRANCH, IBM_241_April1405, HPUX_TEST, HEAD, CQL_2_5_BRANCH, CIMRS_WORK_20130824, CHUNKTESTDONE_PEP140, BeforeUpdateToHeadOct82011, BUG_4225_PERFORMANCE_VERSION_1_DONE
Changes since 1.1: +217 -0 lines
Merged dev branch into main trunk.

ࡱ>	molq	+bjbjt+t+	1PAA'&]dddd8$<mQh---2Q4Q4Q4Q4Q4Q4Q$RTXQ-!)x---XQ-dd----dt2Qdddd-2Q--1zuKS2Q`$P6d-PjPegasus Project Working Paper
CIMOM Shutdown 
AUTHOR:  Jenny Yu, Hewlett-Packard Company 
Revision Status 
PRIVATERevisionDateAuthor(s)Reason1.031 October 2001JYOriginal
Introduction
In a typical WBEM environment, once the CIMOM is started, it is expected to be always running and ready to service CIM requests. On occasions, the CIMOM does require to be shutdown. For example, the system administrator needs to backup the CIM repository or upgrade the CIMOM to a new release. 
Currently, there is no mechanism in the Pegasus WBEM implementation for shutting down the CIMOM gracefully. The only way to terminate the CIMOM is to kill the CIMOM process (on Unix) or stop the Pegasus service (on Windows). Terminating CIMOM abruptly may cause undesirable consequences if there are CIM operations in progress. Providers that are running may not have a chance to complete the operations in progress and perform the necessary cleanup steps. The CIM clients may not get any responses back from the CIMOM To ensure a graceful shutdown, a CIMOM shutdown mechanism must be provided in the Pegasus implementation. 
This paper is a proposal to add such a mechanism. 
Summary of Proposed Changes
The following is a summary of the proposed changes: 
Add a new command line interface for shutting down CIMOM.
Add a new CIMOM Shutdown Service to handle the CIMOM shutdown request.
Define configurable shutdown timeout properties.
Define provider behavior for provider termination.
These changes will be described in more details below. 
Definition of the Proposed Changes
This section defines the proposed changes required to implement the CIMOM shutdown solution. 
CIMOM shutdown Command Line Interface (CLI)
In the Pegasus implementation, the 'cimserver' command is used to start up CIMOM.  This command will be enhanced to add a new option for shutting down CIMOM.  The following is the proposed command line interface:
Command Syntax:
            cimserver -s [-t timeout_value] [-f]
Description:
-sThe '-s' (shutdown) option provides a way to shutdown the CIMOM gracefully.  -t  timeout_valueThe '-t' (timeout) option is used to specify the maximum amount of time (in seconds) the user is willing to wait for all the CIM operations to complete before shutting down the CIMOM.  If all the CIM operations cannot be completed within this timeout period, CIMOM will not be shutdown. 
If this option is not specified, a configurable default timeout value will be used.-fThe '-f' (force) option is used to indicate that the CIMOM should be shutdown after the specified (or default) timeout period has expired, regardless if there are CIM operations in progress or not. All CIM operations that are still in progress will be terminated/killed.  
This option should only be specified when the user is determined that the CIMOM has to be shutdown.The usage of the 'timeout' and 'force' options will be described in more details below.
Shutdown Timeout
Under normal operation, CIMOM should be able to be shutdown fairly quickly without problems.  There are, however, situations that may prevent CIMOM from shutting down within a reasonable amount of time.  For example, a misbehaved provider is hung or is not responding to requests, or a provider is serving a long-running CIM operation.
To handle such situations and to ensure that the CIMOM can be shutdown without having the user wait a long period of time (or indefinitely), two shutdown timeout values will be used.  One for determining whether or not to actually proceed with the shutdown, and the other for allowing some time for the actual shutdown to take place.
CIM Operation Completion Timeout 
After receiving a shutdown request, the system will wait for a configurable 'CIM operation completion timeout' period until all the CIM operations are complete before proceeding to shut down the CIMOM.  If after the timeout period has elapsed, and not all the CIM operations have been completed, the shutdown operation will not be continued and the CIMOM will be put back to its original running state.
This mechanism allows any long-running CIM operations to be continued and at the same time, allows the user (who issued the shutdown request) to decide what action to take.
This configurable timeout value can be overridden by specifying the '-t' (timeout) option and a timeout value (in seconds) in the command line.
Provider Shutdown Timeout
The system will proceed to shutdown CIMOM only if one of the following conditions has been met:
There are no outstanding CIM operation requests.
There are outstanding CIM operation requests, and a 'force' option was specified by the user.
Part of the CIMOM shutdown process is to shutdown all the providers. To allow some time for the providers to shutdown gracefully, the system will wait for a 'provider shutdown timeout' period before actually shutting down the CIMOM.  This provider shutdown timeout property is internal to CIMOM.  It cannot be changed by the user issuing the shutdown command.  However, it is a configurable property that can be changed depending on the need.
Force Shutdown
As described earlier, after the user issues a shutdown request, the system waits for a configurable (or user-specified) timeout period for all the CIM operations to complete.  If the CIM operations cannot be completed within that timeout period, CIMOM will not be shutdown.
There are, however, situations in which the CIMOM must be shutdown.  The '-f' (force) option is provided to force a shutdown, allowing the user to shutdown CIMOM regardless if there are outstanding CIM requests.  If the 'force' option is specified, any CIM operations that are in progress will be killed and CIMOM will be shutdown.
Provider Termination
The provider termination mechanism is the terminate() method in the Provider API.   The providers must implement this method.   Each of the active providers terminate() method will be called by the CIMOM Shutdown Service as part of the CIMOM shutdown process. To ensure a graceful shutdown, once the provider's terminate() method is called, the provider must perform the necessary steps to prepare for a shutdown.
The following defines the proposed behavior of a provider for the terminate() method.
When the provider's terminate() method is called, if the provider is not servicing any requests and there are no pending requests, it should simply perform any necessary cleanup steps and return to the caller.
If there are CIM operation requests pending, the provider must cancel those operations and throw a CIM Exception (TBD) back to the initiating clients to indicate that the requests cannot be carried out due to CIMOM shutdown.  It should then perform any necessary cleanup steps and return to the caller.
If there are CIM operations in progress, the provider must determine either to complete or abort the CIM operations.  Regardless of the decision, the provider must send a response back to the initiating clients.  If it chooses to abort the CIM operations, it must throw a CIM Exception (TBD) back to the initiating clients to indicate that the operation cannot be completed due to CIMOM shutdown.  It should then perform any necessary cleanup steps and return to the caller.
As described earlier, the CIMOM Shutdown Service allows a configurable provider shutdown timeout period before actually unloading the providers and shutting down the CIMOM. If the provider cannot complete the CIM operations and respond to the terminate() method within that time, it should expect to be unloaded.  The end result is that the CIM clients may not get a response back.  Providers should take that into consideration.

Client Request and Response 
While CIMOM is shutting down, a client connection request will result in a connection error.  For clients who have already established a connection to CIMOM, new CIM requests will be rejected and responded with a CIM error (TBD) indicating that the CIMOM is shutting down.
When a client receives a response containing a CIM error indicating that the CIMOM is shutting down, it should close the connection and reconnect to CIMOM at a later time.
CIMOM Shutdown Service
When a user issues the shutdown request using the cimserver s command, the shutdown request will be sent to the CIMOM.  A new service, called the CIMOM Shutdown Service, will be implemented within the CIMOM.  This service will be responsible for processing the shutdown request.
The CIMOM Shutdown Service handles the shutdown request as follows:
Disable new incoming client connections, return a CIM error (TBD) to the client requesting a new connection to indicate that the CIMOM is shutting down.
Disable new incoming CIM requests, return a CIM error (TBD) to the client to indicate that the CIMOM is shutting down.
Check to see if there are any outstanding CIM requests being processed by CIMOM.
If no outstanding CIM requests, proceed to shutdown CIMOM:
Terminate providers: For each loaded provider, call the provider's terminate() method.
Respond to the shutdown command client that CIMOM has been terminated.
If there are outstanding CIM requests, wait periodically for all the CIM requests to complete or until timeout expires.
If there are no more outstanding CIM requests, proceed to shutdown CIMOM and respond to the shutdown command client.
If timeout period has expired:
If  the force option is not specified:
Resume CIMOM by enabling incoming client connections and CIM requests
Return message to inform the shutdown command client that the CIMOM cannot be shutdown due to timeout.
If the force option is specified, proceed to shutdown CIMOM.
The following diagram shows the processing flow of a shutdown request by the CIMOM Shutdown Service:
  


Disable new incoming client connections and CIM requests

Outstanding CIM requests?

Shutdown providers

Send response back to shutdown command client

Wait n second(s)

Timeout?

Outstanding CIM requests? 

No

Yes

Force shutdown? 

No

Outstanding CIM requests? 

Shutdown CIMOM

Yes

No

No

Stop shutdown process and resume CIMOM

Send response back to shutdown command client

No

Yes

Yes

Yes

No



.5mnuvw))*&*'*(*a*b*|*}************+++0+3+B+C+F+H+K+L+O+P+w+x++++++++++++++OJQJhmHnHjUhmHnH0J6CJjCJUCJjCJU5CJ,=.[mh4$$\P@$5$$.[mh&	m				
,


*+ľ{xupmhc_`	
	


	
	
	
	
Q
e
fg	
p	
s	
	
	
	
	
	
5$&	m				
,


*+=]



*+$$lL$#$

&F@&
+=]



*+2T$>-Wla3b= !!"##{snic`]
j	
$	

	L

U&	

&	
_K
Q
_`	
	
	
	
-	
M	
_#2T$>-Wla3b= !!"###dd
&F
&F&
h##$=%%M&&&0'w''d((((Y)))*'*(*a*b*|*}*************++++++2+3+B+C+G+H+K+L+O+P+w+x+ľ5 0
o!	"	

"	
E 	
d	
$	
Q'		

	
*	{	
	

	
A6#$=%%M&&&0'w''d((((Y)

&F"
8

&F 
h
&F
h
&F$
h
&F'
h

&F
h
&F
h
&F
h
&F
h$Y)))*'*(*a*b*|*}*************+5 dd
~=z9!v% d
~=z9!v%dd
&F!0
h++++++2+3+B+C+G+H+K+L+O+P+w+x++++++++++dd dd
~=z9!v%x+++++++++++++++ ++++++dd/0P/R / =!"#$%D@PPPPPPPPPPPPPPPPp
[<@<Normal
1$ddCJhmH	nH	H@H	Heading 1$<@&5CJKHOJQJB@B	Heading 2$<@&56OJQJ<@<	Heading 3$<@&OJQJ@@@	Heading 4$<@&5OJQJ6@6	Heading 5
<@&CJ:@:	Heading 6
<@&6CJ>@>	Heading 7
<@&CJOJQJB@B	Heading 8
<@&6CJOJQJD	@D	Heading 9
	<@&56CJOJQJ<A@<Default Paragraph Font:O:Definition Term
>O>Definition Listh(O(
Definition6*O*H1$@&5CJ0KH$&O&H2$@&5CJ$&O&H3$@&5CJ"O"H4$@&5&O&H5$@&5CJ&O&H6$@&5CJ.O.Address
60O0
Blockquote
hhOCITE6$O$CODECJOJQJ$X@$Emphasis6(U@(	Hyperlink>*B*8V@8FollowedHyperlink>*B*0O0Keyboard5CJOJQJfOfPreformatted0 
#~=z9!v%CJOJQJZOZz-Bottom of Form!$1$$d<CJOJQJhmH	nH	TOT
z-Top of Form"$1$&d<CJOJQJhmH	nH	$O1$SampleOJQJ W@A Strong50OQ0
TypewriterCJOJQJ$Oa$Variable6,Oq,HTML Markup<B*"O"Comment<8Y@8Document Map)-D OJQJ4T@4
Block Text*x*B@*	Body Text+x4P@4Body Text 2,dx2Q@2Body Text 3-xCJDM@DBody Text First Indent.<C@<Body Text Indent
/hxHN@HBody Text First Indent 20FR@FBody Text Indent 21hdxDS@"DBody Text Indent 3
2hxCJ."@.Caption
3xx5&?@B&Closing40@R0Comment Text5CJL@Date60+@r0Endnote Text7CJX$@XEnvelope Address8&@/+DOJQJ>%@>Envelope Return9CJOJQJ, @,Footer
:
!2@2
Footnote Text;CJ,@,Header
<
!*
@*Index 1
=*@*Index 2
>*@*Index 3
?*
@*Index 4
@*@*Index 5
A*@*Index 6
B*@*Index 7
C*@*Index 8
D*@*Index 9
Ep:!@:
Index HeadingF5OJQJ$/@r$List
Gh(2@(List 2
H(3@(List 3
I8(4@(List 4
J(5@(List 5
K20@2List Bullet	L
&F(66@6
List Bullet 2	M
&F)67@6
List Bullet 3	N
&F*68@6
List Bullet 4	O
&F+69@6
List Bullet 5	P
&F,6D@6
List Continue
Qhx:E@":List Continue 2
Rx:F@2:List Continue 3
S8x:G@B:List Continue 4
Tx:H@R:List Continue 5
Ux21@b2List Number	V
&F-6:@r6
List Number 2	W
&F.6;@6
List Number 3	X
&F/6<@6
List Number 4	Y
&F06=@6
List Number 5	Z
&F1h-@h
Macro Text-[1$dd
	`	@ 
OJQJhmH	nH	\I@\Message Header&\8$d%d&d'd-DOJQJ2@2
Normal Indent],O@,Note Heading^4Z@4
Plain Text_CJOJQJ(K@(
Salutation`*@@*	Signaturea6J@"6Subtitleb$<@&OJQJD,@DTable of Authorities
c<#@<Table of Figures
d @>@R@Titlee$<@&5CJ KHOJQJ:.@:TOA Headingfx5OJQJ@TOC 1g"@"TOC 2h"@"TOC 3i"@"TOC 4j"@"TOC 5k"@"TOC 6l"@"TOC 7m"@"TOC 8n"@"TOC 9o:Ui $(P'	
#%?)*,01BDG:Ui $(P	

'P+#Y)+++!#$%'+#x++ "&8GI@T'H
(	
H

#
NB

SDiH
	
#	
H

##z
H


#

H

#!w
H

#
NB

SDqH

#
N

3c
N

3	
	H

#



NB

SD[N

3%)
H

#
l


xB+C{DEF[{{+@vHB
#
#
#

N
%
3%a
H
)
#g
B
*
Z
HB
,
#,p
NB
-
SD6
/
xB	C~DEFf~o~o	@	SN
0
30=
N
1
31R
NB
7
SD"'NB
8
SD$NB
:
SD NB
>
SDH
?
#
NB
@
SDN
B
3B&

C
pBCDEF		@N
D
3D
NB
E
SD

F
pBCDEF	@N
G
3G
NB
H
SDB
S	?%&&&&&&&&	&
&&&
&&&&&&&&&&&&&&&&&&& &!&"&#&$&%&'&	t,!tH **t
`z jt#zp#t	tGpz
tFz
t1Jt/J
tP	tBP
 
}t0pMtz
P"tCPz
tDP"z
tE@@:t)!:t%z
P*tZt	PZ	jt?P:t	z*t@JJt-@
@t*:"
t>tz
t
ttZtZt:j
t
Zt7 *`*t
z t8	*
*tpt(&'!!(&'Jenny Yu1C:\data\ms\word\AutoRecovery save of shutdown.asdJenny Yu1C:\data\ms\word\AutoRecovery save of shutdown.asdJenny Yu1C:\data\ms\word\AutoRecovery save of shutdown.asdJenny Yu"C:\docs\WBEM\shutdown\shutdown.docJenny Yu"C:\docs\WBEM\shutdown\shutdown.docJenny Yu"C:\docs\WBEM\shutdown\shutdown.docJenny Yu"C:\docs\WBEM\shutdown\shutdown.docJenny Yu"C:\docs\WBEM\shutdown\shutdown.docJenny Yu"C:\docs\WBEM\shutdown\shutdown.docJenny Yu"C:\docs\WBEM\shutdown\shutdown.doc2|B-Z}p<Y~&Xp 
EW2i1P<zOVy\NMNw|8VαMLOP2	@UC	"tiCj	"e	)StiCM/ 	"##tiC)	Z0a";tiCcE	ZINn\J	*yK	7K		lS8L	,KL	/zO	=zaS-.,V	+V]tiC$M;btiC_ec	wNg	Kk	ntptiCobvtiC%|tiC~	I~	..88..OJQJo(OJQJo(88OJQJo(OJQJo(hh.hhOJQJo(*..p.@.......p.@.......p.@.......p.@.......p.@.......p.@.....hh.o()hhOJQJo(88o(-hhOJQJo(hhOJQJo(88o(-hhOJQJo(88o(-hhOJQJo(o(-88o(-hhOJQJo(..p.@.....hhOJQJo(hhOJQJo(hhOJQJo(vhhOJQJo(hhOJQJo(hhOJQJo(ddo(-hhOJQJo(..p.@.....88o(-88o(-hhOJQJo(hh.hhOJQJo(88o(-88o(-88o(-hhOJQJo(hhOJQJo(1(\]l\]\]\]8]]|]]OP2,VZI+VcEZ0~,KL$M;bntpobv%|)S]/zO*yK"##"eUCNn\Jj=zaSI~M/ _eclS8L"";)7KwNgKk~}|]] @hOJQJo(2@&&&&'p@GTimes New Roman5Symbol3&Arial?5	Courier New5&zTahoma;Wingdings"h;[;[9[N6Q!2d*%'&Provider Interface ProposalJenny YuJenny YuOh+'0	$0
LXd
p|Provider Interface Proposalrov	Jenny YuIntennennNormal.dott	Jenny Yutt2nnMicrosoft Word 8.0P@@qd@bd@bd՜.+,D՜.+,d 
px
Hewlett PackardN*1Provider Interface ProposalTitle(MU
GENERATORProgId'Mozilla/4.6 [en] (WinNT; I) [Netscape]FrontPage.Editor.Document) 	

 !"#$%&'(*+,-./023456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[]^_`abcefghijknRoot Entry	Fb	dpData
)1Table1IUWordDocument1PSummaryInformation(\DocumentSummaryInformation8dCompObjjObjectPool	d	d
	FMicrosoft Word Document
MSWordDocWord.Document.89q

No CVS admin address has been configured
Powered by
ViewCVS 0.9.2