Hewlett Packard Enterprise Windows Server 2008 IMC Stateful Failover Deployment Guide
Reklam
Reklam
IMC Stateful Failover Deployment Guide (for
Windows Server 2008)
Abstract
This document describes the deployment of the IMC stateful failover cluster and installation of IMC on the
Windows Server 2008 operating system.
Part number: 5200-0117
Software Version:
Document version: 1.0
© Copyright 2015 Hewlett Packard Enterprise Development LP
The information contained herein is subject to change without notice. The only warranties for Hewlett
Packard Enterprise products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty.
Hewlett Packard Enterprise shall not be liable for technical or editorial errors or omissions contained herein.
Confidential computer software. Valid license from Hewlett Packard Enterprise required for possession, use, or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software
Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor’s standard commercial license.
Links to third-party websites take you outside the Hewlett Packard Enterprise website. Hewlett Packard
Enterprise has no control over and is not responsible for information outside the Hewlett Packard Enterprise website.
Acknowledgments
Intel®, Itanium®, Pentium®, Intel Inside®, and the Intel Inside logo are trademarks of Intel Corporation in the
United States and other countries.
Microsoft® and Windows® are trademarks of the Microsoft group of companies.
Adobe® and Acrobat® are trademarks of Adobe Systems Incorporated.
Java and Oracle are registered trademarks of Oracle and/or its affiliates.
UNIX® is a registered trademark of The Open Group.
Contents
IMC stateful failover networking and configuration ···································1
Network topology ························································································································· 1
Network topology description·········································································································· 1
Installation environment ················································································································ 2
Hardware requirements ·········································································································· 2
Software requirements ··········································································································· 2
Domain/DNS server description ······································································································ 3
Configuring the shared storage system ···························································································· 3
Configuring the node server ··········································································································· 3
Attaching the server node to the shared storage device ······································································· 7
IMC stateful failover cluster deployment procedures ································8
Adding the Windows 2008 application role ························································································ 8
Installing and configuring the failover cluster ··················································································· 12
Installing the failover cluster on both nodes ·············································································· 12
Configuring the cluster ········································································································· 15
Installing the database ················································································································ 26
Installing the database for node 1 ··························································································· 26
Installing the database for node 2 ··························································································· 48
Centralized IMC deployment ····························································· 56
Deploying IMC on node 1 ············································································································ 56
Registering the IMC Cluster/HPE iMC Start service on node 1 ···························································· 68
Registering IMC services on node 2 ······························································································ 69
Adding IMC service monitoring to cluster management ····································································· 72
Applying for stateful failover license ······························································································· 88
Distributed IMC deployment······························································ 89
Installing IMC ···························································································································· 89
Registering HPE iMC Start on node 1 ···························································································· 89
Registering HPE iMC Server and HPE iMC Start on node 2 ······························································· 89
Adding IMC service monitoring to cluster ························································································ 89
Applying for a stateful failover license ···························································································· 89
Precautions ··················································································· 90
Attachment ··················································································· 92
Accessing updates ····················································································································· 97 i
IMC stateful failover networking and configuration
Network topology
Figure 1 shows the typical network topology for IMC stateful failover.
Figure 1 Stateful failure network topology
Network topology description
Use WIN08-PLAT1 and WIN08-PLAT2 to form an IMC stateful failover cluster. Two HPE Proliant
DL 380 G7 servers as the cluster nodes. Each server must be installed with at least two GE cards.
The domain controller/DNS server provides key service support for the proper operation of the IMC stateful failover cluster. The server requires a stable configuration. This deployment guide uses an
1
HPE Proliant DL 380 G6 installed with the Windows 2008 R2 operating system (OS) and configured with domain control and DNS services for the cluster.
Use an HPE P2000G3 as the storage device to provide shared storage for the IMC stateful failover cluster. Shared storage is the basic element to implement the IMC stateful failover function.
Configure three logical disks on the storage device for the Windows 2008 failover cluster: arbitration disk, DTC disk, and data disk (for storing SQL server data and installing IMC).
Switch 1 is the front end network switch for stateful failover. It provides transmission services such as user authentication services.
Switch 2 is the backend storage network switch deployed for stateful failover. This deployment guide uses an H3C S5500EI to connect the cluster to the shared storage device. The selection of the device depends on the type and vendor of the shared storage device. Enable Layer 2 functions on the backend storage switch; assign the storage network cards of the cluster nodes (WIN08-
PLAT1 and WIN08-PLAT2) and P2000G3 to the same VLAN, and configure an aggregated link containing four GE links between them.
Each service and application in the Windows 2008 cluster can have an IP address and storage disk configured. In this deployment guide, to associate IMC with the database, configure the same shared disk with the same IP address for them.
Installation environment
Hardware requirements
Table 1 Hardware requirements
CPU (main frequency ≥ 2.5 GHz) Memory
Disk space required for data storage during operation (imcDataDir)
4 CPUs or 2 dual-core CPUs 8 GB 80 GB
As a best practice for a server node, use a battery on the RAID card to avoid data loss in case of a power failure of the server.
Software requirements
The following software and address requirements must be met:
Database software: Microsoft Windows Server 2008 Enterprise/DataCenter Edition, Microsoft
SQL Server 2008 Enterprise Edition
Microsoft Windows Server 2008 R2 Enterprise/Datacenter, Microsoft SQL Server 2008 R2
Enterprise
IMC versions:
iMC PLAT 5.1 SP1 (E0202P05) or later
iMC UAM 5.1 SP1 (E0301P03) or later iMC EAD 5.1 SP1 (E0301P03) or later
iMC TAM 5.1 (E0301) or later iNode DC 5.1 (E0301) or later
IP addresses required by the cluster: one cluster IP address, one application IP address
(used by IMC to provide services and also used as the database IP address), and one DTC address. The IP address must be on the same network segment of the server IP address.
2
The OS version must match the database version. For example, you must Install Microsoft
Windows 2008 R2 together with Microsoft SQL Server 2008 R2, or install Microsoft Windows
Server 2008 together with Microsoft SQL Server 2008. Version mismatch can cause database installation failure.
In this deployment guide, Microsoft Windows 2008 R2 Enterprise and Microsoft SQL Server 2008
R2 Enterprise is adopted.
Domain/DNS server description
This deployment guide specifies a separate server as the domain controller and DNS server:
DNS IP: 192.168.5.61
Domain name: iMCHA.com
NetBIOS domain name: iMCHA
For the network card properties of the PC where the domain controller resides, do not specify any other DNS server as the preferred DNS server; otherwise, operating nodes may fail to be added into the domain.
Create a cluster management user in the domain cluster that belongs to domains Admin and
Administrators, and set a password that is always valid.
Configuring the shared storage system
This deployment guide specifies an HPE P2000G3 as the storage device. For more information about the configuration, see the storage device configuration manual.
Follow these guidelines for configuration:
Configure three logical disks on the storage server for the two node servers in the cluster.
One disk is called data disk for the IMC and SQL servers. (Determine the disk space based on the IMC installation guide and the number of authentication users; 2T is assigned in this deployment guide.) The other two disks are a DTC disk and an arbitration disk. Each is assigned 1 GB space.
If a large volume of user traffic exists, configure link aggregation as a best practice.
Configuring the node server
Configure node servers WIN08-PLAT1 and WIN08-PLAT2:
1. Configure the IP settings:
To configure the port connecting the storage end, clear the IPv6 option for network
configuration and set the IP address, as shown in Figure 2 .
For service port configuration, clear the IPv6 option for network configuration; set the IP address and DNS server address; select Append these DNS suffixes; and enable
NETBIOS. For the configuration, see Figure 2 , Figure 3
3
Figure 2 Setting the IP address
Figure 3 Setting the DNS server
4
Figure 4 Setting the WINS server
2. Modify the computer name and add the computer to the domain (iMCHA.com). Enter the domain user (cluster) password and restart the server after adding it to the domain. For the
configuration, see Figure 5 , Figure 6 , and Figure 7 .
5
Figure 5 Modifying the computer name
Figure 6 Adding the computer to the iMCHA.com domain
Figure 7 Restarting the system
3. Log in to the server as the domain user imcha\cluster, and then add the user cluster to the
Administrators group of the local server, as shown in Figure 8 .
6
Figure 8 Adding the user cluster to the Administrators group
Attaching the server node to the shared storage device
This deployment guide uses the iSCSI initiator client provided by Windows 2008 to connect the three logical disks assigned by the storage device. For detailed procedures, see the configuration guide of the storage device.
7
IMC stateful failover cluster deployment procedures
Adding the Windows 2008 application role
1. Launch the server manager, select Roles in the left navigation tree, and click Add Roles in
the right configuration pane, as shown in Figure 9 .
Figure 9 Adding roles
2. Select Application Server as the server role, and then select Add Required Features in the
popup dialog box, as shown in Figure 10 .
8
Figure 10 Adding required features
3.
Click Next, as shown in Figure 11 .
Figure 11 Introduction to Application Server
9
4. Select .NET Framework 3.5.1, Incoming Remote Transactions, and Outgoing Remote
Transactions, as shown in Figure 12 .
Figure 12 Selecting role services
5.
Click Install, as shown in Figure 13 .
10
Figure 13 Confirmation
The system displays the installation progress bar, as shown in Figure 14 .
Figure 14 Installation progress bar
11
When the installation is complete, the system displays the installation results, as shown in
Figure 15 Installation results
Installing and configuring the failover cluster
Before install and configure the failover cluster, disable the firewalls on both nodes. Make sure the cluster service and unused NICs, including NICs that are not connected to network cables, are disabled.
Installing the failover cluster on both nodes
1. Open the control panel, and then select Programs > Turn Windows Features on or off, as
12
Figure 16 Control panel
2.
Select Features > Failover Clustering, and then click Next, as shown in Figure 17 .
Figure 17 Selecting features
3.
Click Install, as shown in Figure 18 .
13
Figure 18 Confirm selection
The system starts to install the selected feature and displays the installation result, as shown
Figure 19 Installation results
14
4. Click Close.
Configuring the cluster
1.
Open the Failover Cluster Manager on WIN08-PLAT1, as shown in Figure 20 .
Figure 20 Opening the Failover Cluster Manager
2. Right-click Failover Cluster Manager, and then select Create a Cluster from the menu, as
15
Figure 21 Creating a cluster
3.
Select the two cluster server nodes, as shown in Figure 22 .
Figure 22 Selecting server nodes
4.
Configure the cluster name and IP address, as shown in Figure 23 .
16
Figure 23 Configuring the cluster name and address
5.
Create the cluster, as shown in Figure 24 .
Figure 24 Creating the cluster
The system displays the progress bar, as shown in Figure 25 .
17
Figure 25 Progress bar
6.
Click Finish, as shown in Figure 26 .
Figure 26 Summary
The cluster and nodes appear in the Failover Cluster Manager, as shown in Figure 27 .
18
Figure 27 Displaying the cluster and nodes
7. Right-click iMCHACluster.IMCHA.COM, and then select More Actions > Configure Cluster
Quorum Settings from the menu, as shown in Figure 28 .
Figure 28 Configuring the cluster quorum
19
8.
Select Node and Disk Majority, and then click Next, as shown in Figure 29 .
Figure 29 Selecting the quorum configuration
9.
Select cluster disks, and then click Next, as shown in Figure 30 .
Figure 30 Selecting the volume for disk witness assignment
20
10. Click Next, as shown in Figure 31 .
Figure 31 Confirming the configuration
The system starts to configure the disk quorum and displays the result, as shown in Figure
Figure 32 Summary
21
11. View the configured arbitration disk in the Cluster Core Resources, as shown in Figure 33 .
Figure 33 Viewing the configured arbitration disk
12. Under iMCHACluster.IMCHA.COM, right-click Servers and applications, and then select
Configure a Service or Application, as shown in Figure 34 .
Figure 34 Configuring a service or application
13. Select Distributed Transaction Coordinator (DTC), and then select Next, as shown in
22
Figure 35 Selecting the DTC service
14. Set the name and IP address to be used for accessing the service or application, as shown in
Figure 36 Configuring the name and address
15. Select the storage disk to assign to DTC, and then click Next, as shown in Figure 37 .
23
Figure 37 Selecting the storage
16. Click Next, as shown in Figure 38 .
Figure 38 Confirmation
The system displays the configuration progress bar, as shown in Figure 39 .
24
Figure 39 Configuration progress bar
17. Click Finish, as shown in Figure 40 .
Figure 40 Service or application configuration completed
18. Select iMCHACluster.IMCHA.COM > Services and applications > iMCHAClusterDtc to
view detailed information about the configured DTC, as shown in Figure 41 .
25
Figure 41 Summary of iMCHAClusterDtc
Installing the database
Installing the database for node 1
Before installation, make sure the storage disk is attached to node 1 (WIN08-PLAT1), as shown in
Figure 42 Checking the storage disk connection
26
Installation procedure
1. Run the SQL Server 2008 installation file, open the SQL Server Installation Center, and then
click New SQL Server failover cluster installation, as shown in Figure 43 .
Figure 43 Opening the SQL Server Installation Center
After the installation starts up, the installation environment is checked. The installation can
continue only when no failure occurs during the check, as shown in Figure 44 .
Figure 44 Installation process
27
2. Click OK to install setup support files.
The system checks setup support rules, as shown in Figure 45 .
Figure 45 Checking the setup support rules
The installation can continue as long as no failed check items exist.
3.
Click Next, as shown in Figure 46 .
28
Figure 46 Installation process
4. Select features, specify the local disk (not the storage disk) on the server as the shared
feature directory, and then click Next, as shown in Figure 47 .
29
Figure 47 Selecting instance features and directories
5. Use the default SQL Server network name, select the default instance, and then click Next,
30
Figure 48 Using the default name and instance settings
6.
Verify that all disk space requirements are met, and then click Next, as shown in Figure 49 .
31
Figure 49 Checking the disk space requirements
7. Create a cluster resource group for the SQL Server failover cluster, and then click Next, as
shown in Figure 50 . Ignore the three warning messages
32
Figure 50 Creating a cluster resource group
8. Select available shared cluster disk resources for the SQL Server failover cluster, as shown in
33
Figure 51 Selecting shared cluster disk resources
9.
Set an IP address for the SQL Server failover cluster, as shown in Figure 52 .
Figure 52 Setting the IP address
34
10. Select Use service SIDs (recommended) as the security policy for the SQL Server failover
cluster, as shown in Figure 53 .
Figure 53 Selecting the security domain groups
11. For server configuration, click Use the same account for all SQL Server services, select
the domain and account name, and enter the password, as shown in Figure 54 .
35
Figure 54 Specifying the account name and password
12. For the database engine configuration, select Mixed Mode for Authentication Mode, and
select the current user in the Specify SQL Server administrators area, as shown in Figure
55 . By default, the storage disk is selected as the database installation directory.
36
Figure 55 Specifying the database engine configuration
13. Specify the database directories, as shown in Figure 56 . By default, the storage disk is
selected as the database installation directory.
37
Figure 56 Specifying the database directories
14. Check the cluster installation rules, and then click Next, as shown in Figure 57 .
38
Figure 57 Verifying the cluster installation rules
15. Verify the SQL Server features to be installed, ensure that the correct components and
directories have been specified, and then click Install, as shown in Figure 58 .
39
Figure 58 Verifying the SQL Server features
The system displays the installation progress bar, as shown in Figure 59 .
Figure 59 Installation progress bar
40
16. When the installation is complete, click Finish, as shown in Figure 60 .
Figure 60 Completing the installation
After the installation is complete, open the Failover Cluster Manager. You can see that the SQL
Server failover cluster is added to the cluster, as shown in Figure 61 .
41
Figure 61 Viewing the database of the node
Modifying the SQL Server properties
1. In the Failover Cluster Manager, right-click the server node, and then select Properties from
the menu, as shown in Figure 62 .
42
Figure 62 Modifying the database properties
2. Modify the maximum failures in the specified period and the period as needed. The
configuration shown in Figure 63 indicates that if the service or application fails more than 200
times in 1 hour, it will be set to the failed state.
43
Figure 63 Failover setting
3. Right-click the SQL Server, and then select Properties to open the properties dialog boxes of
the SQL Server and SQL Server Agent, as shown in Figure 64 .
44
Figure 64 Configuring the SQL Server properties
4.
On the Policies tab, complete the settings shown in Figure 65 .
45
Figure 65 Policy settings
5.
Complete the same settings on the SQL Server Agent, as shown in Figure 66 .
46
Figure 66 Configuring the SQL Server agent properties
Installing the database for node 2
Installation procedure
1. Run the SQL Server 2008 R2 installation file, open the SQL Server Installation Center, and
then click Add node to a SQL Server failover cluster, as shown in Figure 67 .
47
Figure 67 Opening the SQL Server Installation Center
The system first checks the rules. The installation can continue as long as no failed check
items exist, as shown in Figure 68 .
48
Figure 68 Installation progress bar
2.
After the check is passed, click Next, as shown in Figure 69 .
Figure 69 Rule check results
49
The system checks the setup support rules and setup support files.
3.
View the cluster node configuration, and then click Next, as shown in Figure 70 . The instance
name is the same as the cluster name.
Figure 70 Viewing the instance name
4. Enter the domain user (cluster) password for the SQL Server Database Engine and SQL
Server Agent, and then click Next, as shown in Figure 71 .
50
Figure 71 Configuring the password
5.
Add node rules, and then click Next, as shown in Figure 72 .
Figure 72 Adding nodes
51
The system displays the installation progress bar, as shown in Figure 73 .
Figure 73 Installation progress bar
6.
When the installation is complete, click Finish, as shown in Figure 74 .
52
Figure 74 Completing the installation
Switching the SQL Server database
To switch the SQL server database from WIN08-PLAT1 to WIN08-PLAT2 in case of a database failure:
1. In the cluster manager of WIN08-PLAT1, right-click the SQL Server node under
iMCHACluster.IMCHA.COM, and then select Move this service or application to another
node > Move to node WIN08-PLAT2 from the menu, as shown in Figure 75 .
53
Figure 75 Switching the database
After the switchover, WIN08-PLAT2 provides the SQL Server services.
2. Modify SQLSERVER(MSSSQLSERVER) to iMCHAClusterServices to facilitate
maintenance as needed, as shown in Figure 76 .
Figure 76 Modifying the node name
54
Centralized IMC deployment
In centralized deployment, the service components and the IMC platform are installed on the stateful failover cluster nodes.
Deploying IMC on node 1
1. Make sure the cluster service iMCHAClusterServices is running on node 1. Run the installation file of iMC PLAT 5.1 SP1 (E0202), and then right-click install.bat and select Run
as administrator, as shown in Figure 77 .
Figure 77 Running the cluster service
2.
Select Custom for Installation Type, as shown in Figure 78 .
55
Figure 78 Selecting the installation type
The database cluster has its own database IP address.
3. Select other server for Database Location, enter the database cluster IP address
(192.168.1.86 in this deployment guide), enter the password, and use the default port number
56
Figure 79 Checking the database connectivity
4. Click Next.
The welcome page appears, as shown in Figure 80 .
57
Figure 80 Welcome page
5.
Accept the agreement, and then click Next, as shown in Figure 81 .
58
Figure 81 Agreement page
6. Specify the components to install and the installation location, and then click Next. Because
IMC and the SQL server data files share the same disk, specify disk H as the installation
location and use the default directory, as shown in Figure 82 .
59
Figure 82 Agreement page
7.
Select Deploy or upgrade at once, and then click Next, as shown in Figure 83 .
Figure 83 Deployment and upgrade options
60
8. Verify the components to be deployed, and then start the installation.
The system displays the installation progress bar, as shown in Figure 84 .
Figure 84 Installation progress bar
9.
When the installation is complete, select the components to deploy, as shown in Figure 85 .
61
Figure 85 Selecting components
10. Specify the database storage directory. Open the storage disk H, create a file named imcdata
in the IMC installation directory (see Figure 86 ), and then copy the file path H:\Program
Files\imcdata to the IMC deployment guide (see Figure 87 ).
Figure 86 Creating the imcdata file
62
Figure 87 Specifying the data file location
11. Use the default Web service ports, as shown in Figure 88 .
Figure 88 Specifying the Web service ports
The system starts the deployment, as shown in Figure 89 .
63
Figure 89 Deploying components
12. Launch the Intelligent Deployment Monitoring Agent, and then click Install to import and install PLAT 5.1E0202P05 patches.
13. Click the Deploy tab to view the platform component version, as shown in Figure 90 .
Figure 90 Installing the platform patches
64
14. To install new components, specify the installation path of service components such as UAM,
EAD, and TAM, as shown in Figure 91 .
Figure 91 Deploying components
15. Click OK to start the deployment, as shown in Figure 92 .
Figure 92 Deploying service components
65
16. Specify the service component addresses.
The IMC and SQL Server share the same storage disk and IP address. The database IP address is the virtual IP address of the IMC platform and the IP address of the service components. For example, configure the UAM server's IP address as 192.168.1.86, as shown
in Figure 93 . Specify this IP address for the portal server, policy server, policy proxy server,
user self-service, DAM server, DAM proxy server, and TAM server. In this deployment guide, the cluster does not support IPv6. Leave the IPv6 address fields blank during deployment.
Figure 93 Deploying service components
17. After the deployment is component, upgrade UAM or EAD as needed.
18. On the Deploy tab of the Intelligent Deployment Monitoring Agent, view the deployed
components, as shown in Figure 94 .
66
Figure 94 Viewing deployed service components
Registering the IMC Cluster/HPE iMC Start service on node 1
The IMC cluster service starts IMC processes in the cluster environment. Check whether the
installClusterService.bat file exists in the \deploy directory of the IMC installation path.
If the file exists, right-click the file, and then select Run as administrator from the shortcut menu.
The IMC cluster service is then registered with the name iMC Cluster.
If the file does not exist, register the service by using the following steps:
1. Create a batch file named iMC Start.bat. The file content is as follows:
JavaService.exe -install "HPE iMC Start" " H: \Program
Files\iMC\deploy\jdk\jre\bin\server\jvm.dll" -Djava.class.path=deploy.jar -start com.h3c.imc.deploy.ProcessLauncher -params -wait start -stop com.h3c.imc.deploy.ProcessLauncher -params stop -current " H: \Program
Files\iMC\deploy" -path " H: \Program Files\iMC\deploy\jdk\jre\bin" -auto -shutdown
300 -startup 30 -description "iMC Startup Controller for Cluster Usage".
Change the disk to the actual storage disk, and verify that the IMC installation directory is correct.
2. Copy iMC Start.bat to the H: \Program Files\iMC\deploy directory.
3. Run the command prompt as an administrator and execute iMC Start.bat under the deploy
directory, as shown in Figure 95 .
67
Figure 95 Deploying service components
In the cluster environment, the cluster uses the iMC Cluster or HPE iMC Start service to start and stop IMC processes. The Automatically start the services when the OS starts option on the
Intelligent Deployment Monitoring Agent is unavailable, as shown in Figure 96 .
Figure 96 Intelligent Deployment Monitoring Agent
Registering IMC services on node 2
1.
Switch the cluster service iMCHAClusterServices from node 1 to node 2, as shown in Figure
68
Figure 97 Switching the cluster service to node 2
2.
Pause node 1, as shown in Figure 98 .
Figure 98 Pausing node 1
3. After attaching the shared disk to node 2, double-click vcredist.exe to install the disk. If it is already installed, ignore this step.
H:\Program Files\iMC\deploy\components\common\server\vcredist.exe
4. If vcredist.exe cannot be installed and an installer is required, you must install the
instmsi.exe first.
H:\Program Files\iMC\deploy\components\common\server\instmsi.exe
69
5. Run the command prompt as an administrator, and enter the \iMC\deploy directory to register
HPE iMC Server. svcinst.bat -install -instdir "h:\Program Files\iMC" -datadir "h:\Program
Files\imcdata" -servertype master -language en -country UN -dbtype SQLServer dbadminusername sa -dbadminpasswd "q1!w2@e3#"
In the previous command, the q1!w2@e3# string indicates the password. Make sure you enclose special characters, such as the pound sign (#), within quotation marks. The value
1433 indicates the database port number, which is the default port setting.
The command prompt displays the execution result, as shown in Figure 99 .
Figure 99 Execution result
6. Register the HPE iMC Start service on node 2 in the same way you register the service on node 1. (Details not shown.)
7. Run the Intelligent Deployment Monitoring Agent as an administrator, and then click the
Environment tab to view the monitoring data. If the agent cannot monitor the databases of the components correctly, enter the password of the sa user for the SQL Server database.
8. After the registration, verify the HPE iMC Start and HPE iMC Server services on the service
manager of node 1 and node 2, as shown in Figure 100 .
Figure 100 Viewing the services on a node
9. Switch the cluster service iMCHAClusterServices from node 2 back to node 1, as shown in
70
Figure 101 Switching the cluster service back to node 1
Adding IMC service monitoring to cluster management
1. Launch the cluster manager on WIN08-PLAT1, right-click iMCHAClusterServices, and select
Add a resource > Generic Service, as shown in Figure 102 .
71
Figure 102 Adding a service
2.
Select HPE iMC Server, and then click Next, as shown in Figure 103 .
Figure 103 Selecting a service
3.
Verify the service name and parameters, and then click Next, as shown in Figure 104 .
72
Figure 104 Confirmation
4.
After the service is added, click Finish, as shown in Figure 105 .
Figure 105 Summary
5. Add the HPE iMC Start service to cluster monitoring in the same way the HPE iMC Server is
added, as shown in Figure 106 . Then, the cluster can manage the IMC operation.
73
Figure 106 Summary of the cluster service
6. To enable the cluster to monitor IMC key processes and handle deadlocked IMC processes, add two dedicated scripts to the cluster. The script files are saved in a directory of the IMC platform installation disk, for example, iMC(PLAT)V700R001B02D004-E0202\HPE\Enterprise\windows\tools\cluster_tools.zip.
7. To enable the cluster to monitor the operation of key processes of IMC services, add a process monitoring script MonitorProcess.bat.
8. Verify that the portal component is installed. Then copy the following contents, starting from
@echo off (modify disk H: to the actual data storage disk) to a text file, change the file name to MonitorProcess.bat, and place the file in the IMC installation directory (for example,
H:\Program Files\iMC\).
@echo off rem This Program is used for iMC Process Monitoring. timeout 30
:again rem find UAM process and bound port, if can't find it then end tasklist | find /I "uam.exe" if %errorlevel% NEQ 0 date /t >> "H:\cluster_error.log" & time /t >>
"H:\cluster_error.log" & echo uam.exe error >> "H:\cluster_error.log" & goto over rem find portal process and bound port, if can't find it then end netstat -an | find ":50100" if %errorlevel% NEQ 0 date /t >> "H:\cluster_error.log" & time /t >>
"H:\cluster_error.log" & echo port 50100 error >> "H:\cluster_error.log" & goto over netstat -an | find ":50200"
74
if %errorlevel% NEQ 0 date /t >> "H:\cluster_error.log" & time /t >>
"H:\cluster_error.log" & echo port 50200 error >> "H:\cluster_error.log" & goto over tasklist | find /I "java.exe" if %errorlevel% NEQ 0 date /t >> "H:\cluster_error.log" & time /t >>
"H:\cluster_error.log" & echo java.exe error >> "H:\cluster_error.log" & goto over rem find policy server bound port, if can't find it then end netstat -an | find ":9019" if %errorlevel% NEQ 0 date /t >> "H:\cluster_error.log" & time /t >>
"H:\cluster_error.log" & echo port 9019 error >> "H:\cluster_error.log" & goto over timeout 10 goto again
:over echo. >> "H:\cluster_error.log" exit 9000
If the portal component is not installed:
@echo off rem This Program is used for iMC Process Monitoring. timeout 30
:again rem find UAM process and bound port, if can't find it then end tasklist | find /I "uam.exe" if %errorlevel% NEQ 0 date /t >> “H:\Program Files\iMC\cluster_error.log” & time
/t >> “H:\Program Files\iMC\cluster_error.log” & echo uam.exe error >>
“H:\Program Files\iMC\cluster_error.log “& goto over rem tasklist | find /I "java.exe" rem if %errorlevel% NEQ 0 date /t >> “H:\Program Files\iMC\cluster_error.log” & time /t >> “H:\Program Files\iMC\cluster_error.log” & echo java.exe error >>
“H:\Program Files\iMC\cluster_error.log “& goto over netstat -an | find ":9019" if %errorlevel% NEQ 0 date /t >> “H:\Program Files\iMC\cluster_error.log” & time
/t >> “H:\Program Files\iMC\cluster_error.log” & echo port 9019 error >>
“H:\Program Files\iMC\cluster_error.log” & goto over timeout 10 goto again
:over echo. >> “H:\Program Files\iMC\cluster_error.log” exit 9000
9. Right-click iMCHAClusterServices, and select Add a resource > Generic Application, as
75
Figure 107 Adding an application
10. Enter the command line and parameters (modify the disks as needed), and then click Next,
Figure 108 Configuring the application settings
76
11. View the added monitoring script, as shown in Figure 109 .
Figure 109 Summary of iMCHAClusterServices
12. Copy and decompress the PSTools folder to the root directory of disk H.
13. Open the PSTOOLS folder and edit the killpro.bat file: change the disk to the cluster data disk.
14. On node 1, run the command prompt as an administrator and enter the PSTOOLS file directory.
15. Enter PsExec.exe, and then click Agree on the popup dialog box, as shown in Figure 110 .
Figure 110 Accepting the agreement
77
16. Switch the cluster service to node 2. After attaching the cluster monitoring service to the disk, install PsExec.exe on node 2 in the same way it is installed on node 1. After installation, switch the cluster service back to node 1. (Details not shown.)
17. Right-click iMCHAClusterServices, and select Add a resource > Generic Application, as
Figure 111 Adding an application
18. Enter the command line and modify the disk as needed, as shown in Figure 112 .
78
Figure 112 Configuring the application settings
19. View the added script, as shown in Figure 113 .
Figure 113 Configuring the application settings
79
20. Open the iMCHAClusterServices to see the monitored resources: HPE iMC Server, HPE iMC
Start, MonitorProcess, and killPro. The MonitorProcess script monitors the operation of the specified IMC process and port. The killPro script terminates dead processes generated during a cluster failover failure. To terminate all IMC processes, take the killPro script offline, and then bring it online.
21. Modify the properties and dependencies of HPE iMC Server, HPE iMC Start, MonitorProcess, and killPro:
a. Open the properties dialog box of HPE iMC Server. On the Dependencies tab, add SQL
Server, IP address, and killPro as the dependencies, as shown in Figure 114 .
Figure 114 Adding resources
b. On the Policies tab, make the configurations shown in Figure 115 .
80
Figure 115 Configuring resources
c. Modify the properties of HPE iMC Start by adding HPE iMC Server and IP address as the
dependencies, as shown in Figure 116 .
81
Figure 116 Modifying HPE iMC start properties
d. On the Policies tab, make the configurations shown in Figure 117 .
82
Figure 117 Modifying HPE iMC start policies
e. Add HPE iMC Start as the dependency for MonitorProcess, as shown in Figure 118 .
83
Figure 118 Adding HPE iMC Start as the dependency
f. On the Policies tab, make the configurations shown in Figure 119 .
84
Figure 119 Modifying MonitorProcess policies
g. Add dependencies for killPro as shown in Figure 120 .
85
Figure 120 Adding HPE iMC Start as the dependency
22. After modification, right-click iMCHAClusterServices, and then select Bring this service or
application online, as shown in Figure 121 . The processes are brought online in the
following sequence:
a. killPro
b. HPE iMC Server
c. HPE iMC Start
d. MonitorProcess
86
Figure 121 Bringing services or applications online
Applying for stateful failover license
See HPE IMC deployment guides.
87
Distributed IMC deployment
In distributed deployment, the service components and the IMC Platform are installed on different servers. A typical case is to deploy the IMC Platform to a server, and service components to the stateful failover environment.
Installing IMC
1. Install the IMC Platform components on the master server and upgrade the IMC Platform to
5.1 SP1 (E0202P05). Install (not deploy) service components including UAM and EAD.
2. Copy the PLAT 5.1 SP1 (E0202P05) patch package to the local disk on node 1 of the cluster, and run the command prompt as an administrator.
3. Enter the install directory of the patch package at CLI, and run the following command to start the installation and deployment of the subordinate server: installslave.bat
localIp=192.168.1.86 (where 192.168.1.86 is the cluster virtual IP address; the localIp parameter is case-sensitive). Enter the master server IP address in the popup dialog box (IP address of the server with IMC Platform installed).
4. Click OK.
5. Perform other installation and deployment procedures in the centralized IMC deployment (see
"Deploying IMC on node 1"). When deploying service components, you are required to enter
the IPv4 address of the UAM server, policy server, policy proxy server, user self-service, DAM server, and authentication server.
6. Enter the cluster database virtual IP address 192.168.1.86
.
Registering HPE iMC Start on node 1
For more information, see "Registering the IMC Cluster/HPE iMC Start service on node 1."
Registering HPE iMC Server and HPE iMC Start on node 2
Unlike the centralized IMC deployment, you must change servertype to slave when registering
HPE iMC Server. For detailed procedures, see "Registering IMC services on node 2."
Register the HPE iMC Server: svcinst.bat -install -instdir "H:\Program Files\iMC" -datadir "H:\Program
Files\imcdata" -servertype slave -language EN -country UN -dbtype SQLServer dbadminusername sa -dbadminpasswd "q1!w2@e3#"
In the previous command, the q1!w2@e3# string indicates the password. Make sure you enclose special characters, such as the pound sign (#), within quotation marks. The value 1433 indicates the database port number, which is the default port setting.
Adding IMC service monitoring to cluster
For more information, see "Adding IMC service monitoring to cluster management."
Applying for a stateful failover license
See HPE IMC deployment guides.
88
Precautions
To upgrade IMC, switch iMCHAClusterServices to node 1 (where IMC is installed) and stop node
2, as shown in
Figure 122 . Take the HPE iMC Server, HPE iMC Start, and MonitorProcess
services in cluster monitoring offline, and start the H3C iMC Server in the Server Manager. Then, open the Intelligent Deployment Monitoring Agent to start the upgrade.
Figure 122 Switching the cluster service to node 1
After the upgrade is complete, right-click iMCHAClusterServices and select Bring this service or
application online. When HPE iMC Server, HPE iMC Start, and MonitorProcess services are online, resume node 2.
To use DBMAN to perform database recovery in the stateful failover environment:
1. Switch the cluster service to node 1 where IMC is installed and stop node 2.
2. Take the HPE iMC Server, HPE iMC Start, MonitorProcess, SqlServer, and SqlServerAgent services in Failover Cluster Manager offline.
3. Open the server manager on node 1, manually start HPE iMC Server, SQL Server
(MSSQLSERVER), and SQL Server agent (MSSQLSERVER), and then open the Intelligent
Deployment Monitoring Agent to start database recovery through DBMAN.
4. After the database recovery is complete, right-click iMCHAClusterServices and select Bring
this service or application online.
5. When SQL Server, SQLServer Agent, HPE iMC Server, HPE iMC Start, and MonitorProcess services are online, resume node 2.
89
If the cluster does not operate correctly due to the start failure of the H3C iMC Server service, perform the following operations:
1. Ping the domain name. Make sure the ping is successful.
2. Check the data disk for the
Program
file to see if an unrecognized file type exists. If the file exists, delete it.
3. Check whether the error log path
R:\Program Files\iMC\cluster_error.log
in the
MonitorProcess
script is placed in quotation marks. Delete the quotation marks.
4. If the H3C iMC Server service failed to start only on node 2, check whether the H3C iMC
Server service exists on the service list of node 2. If the service does not exist on the list, run the service registration scripts again. If the database password includes special characters in the scripts, place the special characters in quotation marks.
As a best practice, after the cluster recovers from a power failure, first restart the domain controller server and DNS server, and then the two node servers.
Install patches for the SQL Server database of the cluster on the two nodes. Before installing patches on a node, make sure the cluster resources, such as the IMC services, are offline and the other node is paused.
In distributed deployment, modify the virtual IP address of the SQL Server cluster if the address is not configured correctly during UAM or EAD deployment on the backup server:
1. On the backup server, make sure the IMC resources are offline and all processes and services are stopped.
2. On the primary server, modify the cluster IP address of the backup server in the <
IMC installation path
>\deploy\conf\ component-deploy.xml file. The cluster IP address must be the virtual IP address of the database, which is different from the IP address configured during UAM or EAD deployment.
3.
On the backup server, a
dd mq.localAddr=192.168.1.86:12345 to the end of the <I
MC installation path
>\deploy\conf\dma.conf file, where 192.168.1.86 and 12345 indicate the
IP address and port number of the SQL Server database cluster, respectively.
4. On both node servers, modify the IP addresses of all subordinate servers to the virtual IP address of the SQL Server database cluster in the <IMC installation
path>\common\conf\server_addr.xml file.
90
Attachment
Active Directory
High Availability Solution for the IMC Cluster (V2.2)
91
About HPE IMC documents
The following are the documents available for HPE IMC:
Documents
Hardware specifications and installation
Purpose
HPE IMC Getting Started Guide
HPE IMC Centralized Deployment Guide with Embedded Database
HPE IMC Centralized Deployment Guide with Local Database
HPE IMC Centralized Deployment Guide with Remote Database
Quickly guides you through the IMC main features and troubleshooting common problems.
Provides a complete guide to IMC platform and components installation and centralized deployment using embedded database.
Provides a complete guide to IMC platform and components installation and centralized deployment using local database.
Provides a complete guide to IMC platform and components installation and centralized deployment using remote database.
HPE IMC Distributed Deployment Guide with Local Database
HPE IMC Distributed Deployment Guide with Remote Database
HPE IMC Probe Installation Guide
HPE IMC RSM Installation Guide
Provides a complete guide to IMC platform and components installation and distributed deployment using local database.
Provides a complete guide to IMC platform and components installation and distributed deployment using remote database.
Provides a complete guide to IMC Probe installation and deployment.
Provides a complete guide to IMC RSM installation and deployment.
Provides a complete guide to IMC iHATool installation.
Guides you through installing SQL Server 2008 for IMC.
HPE IMC iHATool Installation Guide
SQL Server 2008 Installation and
Configuration Guide
SQL Server 2008 R2 Installation and
Configuration Guide
SQL Server 2012 Installation and
Configuration Guide
SQL Server 2014 Installation and
Configuration Guide
Oracle 11g Installation and Configuration
Guide(for Linux)
Guides you through installing SQL Server 2008 R2 for IMC.
Guides you through installing SQL Server 2012 for IMC.
Guides you through installing SQL Server 2014 for IMC.
Guides you through installing Oracle 11g on Linux for IMC.
Oracle 11g R2 Installation and Configuration
Guide(for Linux)
Guides you through installing Oracle 11g R2 on Linux for
IMC.
Oracle 12c Installation and Configuration
Guide(for Linux)
Guides you through installing Oracle 12c on Linux for IMC.
Guides you through installing MySQL 5.5 on Linux for IMC. MySQL 5.5 Installation and Configuration
Guide (for Linux)
MySQL 5.5 Installation and Configuration
Guide (for Windows)
Guides you through installing MySQL 5.5 on Windows for
IMC.
92
Documents
MySQL 5.6 Installation and Configuration
Guide (for Linux)
Purpose
Guides you through installing MySQL 5.6 on Linux for IMC.
MySQL 5.6 Installation and Configuration
Guide (for Windows)
Red Hat Enterprise Linux 6.4 Installation
Guide
Red Hat Enterprise Linux 7.0 Installation
Guide
Software configuration
Guides you through installing MySQL 5.6 on Windows for
IMC.
Guides you through installing Red Hat Enterprise Linux 6.4 for IMC.
Guides you through installing Red Hat Enterprise Linux 7.0 for IMC.
Describes operation procedures on the IMC platform. HPE IMC Enterprise and Standard Platform
Administrator Guide
HPE IMC Quality of Service Manager
Administrator Guide
HPE IMC Resource Automation Manager
Administrator Guide
HPE IMC Service Health Manager
Administrator Guide
HPE IMC VAN Connection Manager
Administrator Guide
HPE IMC VAN Software Defined Network
Manager Administrator Guide
HPE IMC VAN Fabric Manager
Administrator Guide
Describes operation procedures on the IMC Quality of
Service Manager.
Describes operation procedures on the Resource
Automation Manager.
Describes operation procedures on the Service Health
Manager.
Describes operation procedures on the IMC VAN
Connection Manager.
Describes operation procedures on the IMC VAN Software
Defined Network Manager.
Describes operation procedures on the IMC VAN Fabric
Manager.
HPE IMC Application Manager Administrator
Guide
Describes operation procedures on the IMC Application
Manager.
HPE IMC Branch Intelligent Management
System Administrator Guide
Describes operation procedures on the IMC Branch
Intelligent Management System.
HPE IMC Business Service Performance
Administrator Guide
HPE IMC IPsec VPN Manager Administrator
Guide
HPE IMC MPLS VPN Manager
Administrator Guide
Describes operation procedures on the IMC Business
Service Performance.
Describes operation procedures on the IMC IPsec VPN
Manager.
Describes operation procedures on the IMC MPLS VPN
Manager.
HPE IMC Network Traffic Analyzer
Administrator Guide
HPE IMC Service Operation Manager
Administrator Guide
Describes operation procedures on the IMC Network Traffic
Analyzer.
Describes operation procedures on the IMC Service
Operation Manager.
HPE IMC User Behavior Auditor
Administrator Guide
Describes operation procedures on the IMC User Behavior
Auditor.
HPE IMC UC Health Manager Admin Guide Describes operation procedures on the IMC UC Health
Manager.
HPE IMC Wireless Service Manager
Administrator Guide
HPE IMC User Access Manager
Administrator Guide
Describes operation procedures on the IMC Wireless
Service Manager.
Describes operation procedures on the IMC User Access
Manager.
93
Documents
HPE IMC TACACS+ Authentication
Manager Administrator Guide
HPE IMC EAD Security Policy Administrator
Guide
Online Help
Operations and maintenance
Readme
Purpose
Describes operation procedures on the IMC TACACS+
Authentication Manager.
Describes operation procedures on the IMC EAD Security
Policy Manager.
Helps you properly use IMC.
Provides most recent IMC release information.
94
Document conventions
This section describes the conventions used in the documentation.
Port numbering in examples
The port numbers in this document are for illustration only and might be unavailable on your device.
Command conventions
Convention
Boldface
Italic
#
GUI conventions
Description
Bold text represents commands and keywords that you enter literally as shown.
Italic text represents arguments that you replace with actual values.
A line that starts with a pound (#) sign is comments.
Convention
Boldface
Description
Window names, button names, field names, and menu items are in Boldface. For example, the New User window appears; click OK.
Multi-level menus are separated by angle brackets. For example, File > Create >
Folder.
Symbols
>
Convention
WARNING!
CAUTION:
IMPORTANT:
NOTE:
TIP:
Description
An alert that calls attention to important information that if not understood or followed can result in personal injury.
An alert that calls attention to important information that if not understood or followed can result in data loss, data corruption, or damage to hardware or software.
An alert that calls attention to essential information.
An alert that contains additional or supplementary information.
An alert that provides helpful information.
95
Support and other resources
Accessing Hewlett Packard Enterprise Support
For live assistance, go to the Contact Hewlett Packard Enterprise Worldwide website:
www.HPE.com/assistance
To access documentation and support services, go to the Hewlett Packard Enterprise Support
Center website:
www.HPE.com/support/HPEsc
Information to collect
Technical support registration number (if applicable)
Product name, model or version, and serial number
Operating system name and version
Firmware version
Error messages
Product-specific reports and logs
Add-on products or components
Third-party products or components
Accessing updates
Some software products provide a mechanism for accessing software updates through the product interface. Review your product documentation to identify the recommended software update method.
To download product updates, go to either of the following:
Hewlett Packard Enterprise Support Center Get connected with updates page:
www.HPE.com/support/e-updates
Software Depot website: www.HPE.com/support/softwaredepot
To view and update your entitlements, and to link your contracts, Care Packs, and warranties with your profile, go to the Hewlett Packard Enterprise Support Center More Information on
Access to Support Materials page:
www.HPE.com/support/AccessToSupportMaterials
IMPORTANT:
Access to some updates might require product entitlement when accessed through the
Hewlett Packard Enterprise Support Center. You must have an HPE Passport set up with relevant entitlements.
96
Websites
Website
Networking websites
Hewlett Packard Enterprise Networking Information Library
Hewlett Packard Enterprise Networking website
Hewlett Packard Enterprise Networking My Support
Link www.HPE.com/networking/resourcefinde r www.HPE.com/info/networking www.HPE.com/networking/support
General websites
Hewlett Packard Enterprise Information Library
Hewlett Packard Enterprise Support Center
Contact Hewlett Packard Enterprise Worldwide
Subscription Service/Support Alerts
Software Depot
Customer Self Repair (not applicable to all devices)
Insight Remote Support (not applicable to all devices) www.HPE.com/info/enterprise/docs www.HPE.com/support/HPEsc www.HPE.com/assistance www.HPE.com/support/e-updates www.HPE.com/support/softwaredepot www.HPE.com/support/selfrepair www.HPE.com/info/insightremotesuppor t/docs
Customer self repair
Hewlett Packard Enterprise customer self repair (CSR) programs allow you to repair your product.
If a CSR part needs to be replaced, it will be shipped directly to you so that you can install it at your convenience. Some parts do not qualify for CSR. Your Hewlett Packard Enterprise authorized service provider will determine whether a repair can be accomplished by CSR.
For more information about CSR, contact your local service provider or go to the CSR website: www.HPE.com/support/selfrepair
Remote support
Remote support is available with supported devices as part of your warranty, Care Pack Service, or contractual support agreement. It provides intelligent event diagnosis, and automatic, secure submission of hardware event notifications to Hewlett Packard Enterprise, which will initiate a fast and accurate resolution based on your product’s service level. Hewlett Packard Enterprise strongly recommends that you register your device for remote support.
For more information and device support details, go to the following website: www.HPE.com/info/insightremotesupport/docs
Documentation feedback
Hewlett Packard Enterprise is committed to providing documentation that meets your needs. To help us improve the documentation, send any errors, suggestions, or comments to Documentation
Feedback ( [email protected]
). When submitting your feedback, include the document title, part number, edition, and publication date located on the front cover of the document. For online
97
help content, include the product name, product version, help edition, and publication date located on the legal notices page.
98
İndir
Herkese açık bağlantı güncellendi
Sohbetinize giden herkese açık bağlantı güncellendi. You may view and manage your chat links after registration here.
Belge herkese açık bağlantısı
Reklam