Job Management Partner 1/Client Security Control Description, User's Guide and Operator's Guide

Appendix D.2 Prerequisites and supported operations

Organization of this subsection

(1) Prerequisites

(2) Supported operations

(1) Prerequisites

The following table explains the prerequisites for running JP1/CSC - Manager and JP1/CSC - Agent on a cluster system.

Table D-1 Prerequisites

Component Prerequisites

OS and required software

OS

Windows Server 2003, Enterprise Edition or Windows Server 2008 Enterprise

OS cluster software

Microsoft Cluster Server (MSCS) or Windows Server Failover Cluster (WSFC)

Servers Two servers in a cluster configuration

Network

A logical IP address can be used for communication when communication is lost due to a problem in the cluster software or for some other reasons.

Correspondence between host names and IP addresses is not changed by cluster software or name servers during JP1/CSC - Manager operation.

The LAN board corresponding to the host name has the highest priority in the network binding settings, with no other LAN boards of higher priority.

Shared disk

Failover can be performed from the active server to the standby server.

The shared disk must be allocated before starting JP1/CSC^#1.

The shared disk must not be deallocated while JP1/CSC^#1 is active.

Exclusion control is performed so that invalid usage does not exist from multiple servers.

Contents written to files are guaranteed even when failover occurs.

Failover can be performed forcibly even when the shared disk is being used by another process.

Recovery measures when a shared disk error is detected is controlled by the cluster software, and is transparent to JP1/CSC^#1. If JP1/CSC^#1 needs to be started or stopped during the recovery process, the start/stop execution request must be issued from the cluster software.

Logical IP address

Communication is performed using an address that can be carried over.

The logical IP address must be assigned before starting JP1/CSC^#1.

The logical IP address must not be deallocated while JP1/CSC^#1 is active.

Recovery measures when a network error is detected is controlled by the cluster software, and is transparent to JP1/CSC^#1. If JP1/CSC^#1 needs to be started or stopped during the recovery process, the start/stop execution request must be issued from the cluster software.

AIM^#2

AIM must also be configured for operation in the cluster system.

JP1/CSC - Manager must be set up so that failover is performed after AIM failover is completed.

#1

Refers to JP1/CSC - Manager when running JP1/CSC - Manager on a cluster system, or to JP1/CSC - Agent when running JP1/CSC - Agent on a cluster system.

#2

The prerequisites for AIM are unnecessary when running only JP1/CSC - Agent on a cluster system.

Component	Prerequisites
OS and required software	OS Windows Server 2003, Enterprise Edition or Windows Server 2008 Enterprise OS cluster software Microsoft Cluster Server (MSCS) or Windows Server Failover Cluster (WSFC)
Servers	Two servers in a cluster configuration
Network	A logical IP address can be used for communication when communication is lost due to a problem in the cluster software or for some other reasons. Correspondence between host names and IP addresses is not changed by cluster software or name servers during JP1/CSC - Manager operation. The LAN board corresponding to the host name has the highest priority in the network binding settings, with no other LAN boards of higher priority.
Shared disk	Failover can be performed from the active server to the standby server. The shared disk must be allocated before starting JP1/CSC^#1. The shared disk must not be deallocated while JP1/CSC^#1 is active. Exclusion control is performed so that invalid usage does not exist from multiple servers. Contents written to files are guaranteed even when failover occurs. Failover can be performed forcibly even when the shared disk is being used by another process. Recovery measures when a shared disk error is detected is controlled by the cluster software, and is transparent to JP1/CSC^#1. If JP1/CSC^#1 needs to be started or stopped during the recovery process, the start/stop execution request must be issued from the cluster software.
Logical IP address	Communication is performed using an address that can be carried over. The logical IP address must be assigned before starting JP1/CSC^#1. The logical IP address must not be deallocated while JP1/CSC^#1 is active. Recovery measures when a network error is detected is controlled by the cluster software, and is transparent to JP1/CSC^#1. If JP1/CSC^#1 needs to be started or stopped during the recovery process, the start/stop execution request must be issued from the cluster software.
AIM^#2	AIM must also be configured for operation in the cluster system. JP1/CSC - Manager must be set up so that failover is performed after AIM failover is completed.

(2) Supported operations

When JP1/CSC - Manager is run on a cluster system, only operations for JP1/CSC - Manager itself are supported.

When JP1/CSC - Agent is run on a cluster system, only operations for JP1/CSC - Agent itself are supported.

Cluster environment (shared disks and logical IP addresses) control depends on cluster software control. Therefore, if the prerequisites listed in Table D-1 Prerequisites are not satisfied, or problems occur with cluster environment control, check the cluster software and OS.

[Contents][Back][Next]

[Trademarks]

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