Job Management Partner 1/Client Security Control Description, User's Guide and Operator's Guide
- Organization of this subsection
- (1) When failover is performed
- (2) Administrator operations after failover
- (3) Precautions
(1) When failover is performed
The following are examples of when to perform failover for JP1/CSC - Manager and JP1/CSC - Agent. Whether to perform failover in each situation must be set by the administrator.
- When a JP1/CSC - Manager is terminated on the NT service
- When a hardware failure occurs
- When an OS failure occurs
- When power is cut
- When a network failure occurs
- When a failure occurs in AIM (JP1/CSC - Manager only)
(2) Administrator operations after failover
The administrator must perform the following operations when a failover occurs.
(a) JP1/CSC - Manager
Because JP1/CSC - Manager is started on the standby server, a message reporting JP1/CSC - Manager startup is output to the log.
The following table lists the operations that the administrator must perform if failover occurs during processing.
Table D-8 Administrator operations after failover (JP1/CSC - Manager)
Processing being performed during failover Operation performed by the administrator Security level judgment Use the JP1/CSC - Manager log file to check whether security level judgment has finished. If processing has not finished, perform security level judgment again.#1 Action implementation Use the JP1/CSC - Manager log file to check whether the action has finished. If processing has not finished, implement the action again.#2 Operations on a window If failover occurred during operation of a window (Security Policy Management window, Setup window, or Client Security Management window), use the JP1/CSC - Manager log file to check whether the operation has finished. If it has not, perform the operation again.
- #1
- To check whether or not the security level judgment has finished, check the messages output to the log file to indicate the start and end of security level judgment. If a start message from JP1/CSC - Manager was output between the start and end messages for security level judgment, processing has not finished.
- #2
- To check whether or not the action has finished, check the messages output to the log file to indicate the start and end of the action. If a start message from JP1/CSC - Manager was output between the start and end messages for the action, processing has not finished.
(b) JP1/CSC - Agent
Because JP1/CSC - Agent is started on the standby server, a message reporting JP1/CSC - Agent startup is output to the log.
The following table lists the operations that the administrator must perform if a failover occurs during processing.
Table D-9 Administrator operations after failover (JP1/CSC - Agent)
Processing being performed during failover Operation performed by the administrator Action implementation Use the JP1/CSC - Manager log file to check whether the action has finished. If processing has not finished, implement the action again.# Operation in the Setup window If a failover occurred while an operation was being performed in the Setup window, use the JP1/CSC - Agent log file to check whether the operation has finished. If it has not, perform the operation again.
- #
- To check whether the action has finished, review the messages output to the log file to indicate the start and end of the action. If a start message from JP1/CSC - Manager was output between the start and end messages for the action, processing has not finished.
(3) Precautions
Keep the following in mind when performing operation on a cluster system:
- If the JP1/CSC# service cannot start or stop, a JP1/CSC# process may still be running. In this situation, restart the system.
- Startup control (NT service) cannot be used for operations that run on the logical IP address of the cluster system. To control JP1/CSC# startup on a cluster system, use the cluster software.
- When running JP1/CSC# on a cluster system, do not enable JP1/CSC# to start automatically.
- #
- Refers to JP1/CSC - Manager when running JP1/CSC - Manager on a cluster system.
- Refers to JP1/CSC - Agent when running JP1/CSC - Agent on a cluster system.
All Rights Reserved. Copyright (C) 2009, 2011, Hitachi, Ltd.
Copyright, patent, trademark, and other intellectual property rights related to the "TMEng.dll" file are owned exclusively by Trend Micro Incorporated