Professional Documents
Culture Documents
01k.AGM320 APG432 Cloning Instruction
01k.AGM320 APG432 Cloning Instruction
INSTRUCTION 1 (40)
Prepared (also subject responsible if other) No.
Abstract
Application
Contents
1 Revision information 2
2 GENERAL 3
3 KNOWN BUGS AND LIMITATIONS 3
4 PREREQUISITES 3
5 DEPLOY THE CLONE IMAGE INTO AN APG43/2 5
5.1 Changing Parameters on an already installed machine 5
5.2 Post cloning steps 13
5.3 AP2 Reconfiguration 14
6 HCS service handling 15
7 SPOE IP BACKUP Definition (both AP1 and AP2) 16
8 Setup AP1 and AP2 for APZ connection 17
8.1 AP1/AP2 configuration: Common Part 17
8.2 CS parameters 22
8.3 Data Disk Quota Configuration 27
8.4 IPMI and BIOS for APUB2 27
9 Final Configuration Steps 28
10 HW info 29
11 Health Check 30
12 REFERENCES 32
13 ABBREVIATIONS AND TERMINOLOGY 32
14 APPENDIXES 33
14.1 APPENDIX 1: Post Cloning steps 33
14.2 APPENDIX 2: Workaround for burbackup 34
14.3 APPENDIX 3: AP2 configuration checks 35
14.4 Active Directory and File Replication checks 37
Limited Internal
INSTRUCTION 2 (40)
Prepared (also subject responsible if other) No.
1 Revision information
NOTE:
New CLOBIN R1D 109 22-APZ 212 55/4-995 released in AGM320 requires
aposclone service start on node B only before launching CloConfig.vbs.
2 GENERAL
Cloning Instruction includes all the post installation steps to be performed on
an APG43/2 system in order to have it working and ready to be connected to
an APZ.
After reconfiguration of the system each APG43/2 is identical to the other.
4 PREREQUISITES
Hardware and Firmware requirements
NOTE: The steps reported in this chapter, if not expressly specified, need to
be performed on both AP1 and AP2 systems.
NOTE 2: The defined Forwarders (if any) will be removed from the system by
the CloConfig procedure and needs to be reset manually after the
reconfiguration is over.
Before starting, check that the actions specified in chapter 4 have been
performed.
Both nodes
Delete on both nodes the directory Clone under c:\temp running the following
commands from Active node:
Once the actions in Appendix 14.3 have been completed, continue with
next step.
1 ACL backup
Active node A
Passive node B
New CLOBIN R1D 109 22-APZ 212 55/4-995 released in AGM320 requires
aposclone service start on node B only.
cd /D “C:\Program Files\AP\APOS\clone”
aposclone.bat
Limited Internal
INSTRUCTION 7 (40)
Prepared (also subject responsible if other) No.
---
--- aposclone startup
---
SERVICE_NAME: aposclone
TYPE : 110 WIN32_OWN_PROCESS (interactive)
STATE : 4 RUNNING
(STOPPABLE, NOT_PAUSABLE,
IGNORES_SHUTDOWN))
WIN32_EXIT_CODE : 0 (0x0)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0
3 CloConfig execution
NOTE: Check that the actions specified in chapter 4 have been correctly
performed before starting CloConfig.
Active node A
”c:\Program Files\AP\APOS\clone\CloConfig.vbs”
When asked for the “Administrator’s password”, insert it and press enter.
A prompt to allow changing the parameters will appear.
Fill the fields with the new parameters and save the changes choosing “Set
parameters and configure the system”.
The reconfiguration will continue automatically performing the following
main steps:
• Cluster stop on B and A nodes
• Active Directory demote/promote
• Start CloInstall with newly configured parameters
(hostname/domain/IP addresses)
Wait until the opened Remote Desktop session is automatically closed at first
node reboot.
It may take up to 3 hours for the complete procedure to be finished (in case
hostnames/domain must be changed). In case only IP addresses must be
changed, the procedure will take a few minutes to be completed.
During some of the CloConfig phases it is not possible to login to the node.
IMPORTANT:
Limited Internal
INSTRUCTION 9 (40)
Prepared (also subject responsible if other) No.
Check whether or not the installation is over with the following command:
Node-A
Both-nodes
If the printout is not as above, open Clone User Guide document in Ref. 1,
and follow the actions specified in Appendix 1 (“New Recovery Actions”
section).
6 Restore ACLs
Both-nodes
7 Format D drive
Both-nodes
Passive node B
aposclone_clean.bat
SERVICE_NAME: aposclone
TYPE : 110 WIN32_OWN_PROCESS
(interactive)
STATE : 4 RUNNING
(STOPPABLE, NOT_PAUSABLE,
IGNORES_SHUTDOWN))
WIN32_EXIT_CODE : 0 (0x0)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0
--- aposclone disable
4124
SUCCESS: The process with PID 4124 has been terminated.
----------------------------------
--- aposclone query
---
[SC] EnumQueryServicesStatus:OpenService FAILED 1060:
Done
NOTE:
Active node A
Check and, in case, Disable Write Cache for both the data disks:
“C:\Program Files\AP\APOS\clone\dskcache.exe”
PhysicalDrive1
“C:\Program Files\AP\APOS\clone\dskcache.exe”
PhysicalDrive2
For AP1:
• Perform chapter 6
For AP2:
• Perform chapter 5.3 (only steps 2 and 5 about DNS reverse lookup
pointers without any node reboot)
• Perform chapter 6
For chapter 8.1, it should not be required to perform Soft Function change or
launching CS parameter script in order to change CSBIN parameters (the
ones visible in nels printout) since already performed in post cloning phase
when cloning the machine.
If they are not the expected ones, change them following the instructions in
chapters 8.1 and 8.2.
Limited Internal
INSTRUCTION 13 (40)
Prepared (also subject responsible if other) No.
Launch the following scripts in this section, using GUI or SSH connections
(DO NOT USE telnet connection, see TR HL46741), in order to apply the
correct configuration for the node:
13 Run the following post configuration batch file (in case of default time
zone):
c:\temp\PostCloning\PostCloning.bat
Check the result of the Post Cloning procedure looking at the log files stored
under c:\temp\PostCloning\logs on the Active node.
NOTE: The command given without parameters will set the default time
zone: “(GMT+01:00) Amsterdam, Berlin, Bern, Rome,
Stockholm, Vienna” bound at position “0”. In case a different time
zone needs to be bound, the correct syntax is reported below:
c:\temp\PostCloning\PostCloning.bat “TZ_name” TMZ_value
Skip the following printout which may eventually occur at the end of
PostCloning script execution:
--- Configuration of the Passive Node finished ---
SSH regenerate keys on active node and copying of keys to passive node
plus ssh-server-config-tool.exe included in PostCloning.bat (for details on the
performed actions, see Appendix A: Post Cloning steps in chapter 14).
Limited Internal
INSTRUCTION 14 (40)
Prepared (also subject responsible if other) No.
In case you are here after having executed CloConfig phase (chapter 5.1), the
node is already configured as AP2 and this chapter shall be skipped.
NOTE: all the steps in this section, if not differently mentioned, need to be
performed on the AP2 node only.
Launch the following scripts in this section, using GUI or SSH connections
(DO NOT USE telnet connection, see TR HL46741), in order to apply the
correct configuration for the node:
Active-node (Node A)
1. Execute the fewer clones AP2 configuration script on the active node
(node A) of AP2. Two input parameters are foreseen for this script:
c:\TEMP\PostCloning\FewerCloneConfig_PA18.bat AP2
NOTE: Do not take into account the error “The group or resource is not in the
correct state to perform the requested operation”.
NOTE: It is OK if the “prcstate –l” printout shows that not all the resources are
up and running as the two nodes are not aligned (one is configured as AP2,
while the other not yet)
4. Execute the fewer clones configuration script on the new active node
(node B) for AP2:
c:\TEMP\PostCloning\FewerCloneConfig_PA18.bat AP2
Limited Internal
INSTRUCTION 15 (40)
Prepared (also subject responsible if other) No.
Both Nodes
Both Nodes
Done
NOTE: Don’t care about the warning inside the printout example above
Limited Internal
INSTRUCTION 16 (40)
Prepared (also subject responsible if other) No.
This script will configure the service as automatic start-up type and start it on
AP1.
Active-node
Active-node
Active-node
1. Assign the Administrator user the right permission to connect to the CP:
c:\temp\PostCloning\Utils\Administrator_permission.bat
Done!
Perform a soft function change session in order to set the correct value for
ACS_APCONFBIN_CpAndProtocolType (see ref. [2]).
The possible values are:
• APZ21230
• APZ21233
• APZ21233/C
Active node
5. Restart CS services:
C:\temp\PostCloning\APZ21233x\restartCS_delay.bat
Limited Internal
INSTRUCTION 19 (40)
Prepared (also subject responsible if other) No.
• APZ 212 40
Active node
2. Restart CS services:
C:\temp\PostCloning\APZ21233x\restartCS_delay.bat
• APZ 212 50
Active node
2. Restart CS services:
C:\temp\PostCloning\APZ21233x\restartCS_delay.bat
Active node
If not, change it to 4 via Soft Function Change (as specified in chapter 8.1 step
2).
Active node A
2. CS parameters change
Run the following script from active node A only. This script will change on
both nodes CS parameters ():
C:\temp\PostCloning\CSparameters_both_nodes.bat X
Where X can be any of the values described in chapter 8.2 (e.g. X=5 for Evo
configuration BSC/SCP in CBA environment).
In case of dual AP configuration, connect AP1 and AP2. Verify that the
communication link is up by pinging from the AP1 the “IP Address for SPOE” of
the AP2 (192.168.169.34).
AP1 Active-node
Go to chapter 8.3.
Limited Internal
INSTRUCTION 22 (40)
Prepared (also subject responsible if other) No.
8.2 CS parameters
Active node A
----
---- Chosen configuration is MSC CBA SCP (1)
----
---
--- PHAEDIT for CS parameters on node A
---
Parsing format file ...
Parsing parameter file ...
Parameter editing session started.
:Category: Private
int[0, 1] (0):
:Category: Private
int[0, 1] (0):
:Category: Private
int[0, 3] (0):
:Parameters updated
Exiting ...
edit ACS_CSBIN_isMultipleCPSystem
0
edit ACS_CSBIN_nodeArchitecture
1
edit ACS_CSBIN_aptType
0
end
Limited Internal
INSTRUCTION 24 (40)
Prepared (also subject responsible if other) No.
---
--- PHACREATE for CS parameters
---
Parameter tables generated. No errors found.
---
--- Copy modified CS parameter file to
c:\acs\data\fchcurrent\CXC1371340\ directory
---
1 file(s) copied.
0
----------------------------------------------------------
--- Checking CS parameters (nels) on node A
----------------------------------------------------------
System Type: Single-CP System
APT Type: MSC
Node Architecture: Component Based Architecture SCX
Standalone
---
--- Changing CS parameters on node B
---
----------------------------------------------------------
--- Checking CS parameters (nels) on node B
----------------------------------------------------------
System Type: Single-CP System
APT Type: MSC
Node Architecture: Component Based Architecture SCX
Standalone
---------------------------------------------------------------------
-------- Checking CS .par file on both "conf" and
"fch" folders --------
---------------------------------------------------------------------
---
--- Initial clean-up
---
--- deleting c:\temp\PostCloning\logs\ACS_CSBIN_NOK.txt
Volume in drive C is NTSERV
Volume Serial Number is 0C06-E964
Limited Internal
INSTRUCTION 25 (40)
Prepared (also subject responsible if other) No.
Directory of c:\temp\PostCloning\logs
Directory of c:\temp\PostCloning\logs
--------------------------------------------------------------------
--- CS parameters are aligned on both nodes
--------------------------------------------------------------------
---
--- "Restarting the whole Cluster except the "Cluster Group":"
---
Both nodes
This chapter describes how to set the Data Disk Quota Configuration for CP
Systems (default BSC). The procedure needs to be applied on both AP1 and
AP2 systems.
Active-node
where <config> parameter depends on the configuration used and the size of
the Data Disks.
See some examples below:
AP1 systems:
MSCBC-AP1-8M450 MSC-S BC HD 450 GB
MSCBC-AP1-8M600 MSC-S BC HD 600 GB
MSC MSC in Single CP HD 300 GB
HLR MSC in Single CP HD 300 GB
BSC BSC in Single CP HD 300 GB
AP2 systems:
MSCBC-AP2-8M450 MSC-S BC HD 450 GB
MSCBC-AP2-8M600 MSC-S BC HD 600 GB
NOTE: For details about other configurations, see MAN ssucfg page 1/190
80-CNZ 222 166 or Application Information 2/155 18-ANZ 222 43/5.
Verify the Firmware (IPMI and BIOS versions) installed on the boards:
ipmi_upg –f
wmic CSproduct List Status
If not present, load the aforementioned CN-Is. They are already part of APZ
19.0 supported HW, as specified in APZ 19.0 HW baseline.
Limited Internal
INSTRUCTION 28 (40)
Prepared (also subject responsible if other) No.
1. Update nodes
swmanage -s
10 HW info
In APZ19 the following APHW CN-Is have been included:
APHW, IPMI
UPG FW
CXC138844 R13A 109 22-APZ 212 60/4-257
UPGRADE FOR
APUB2
APHW:
INTRODUCTION
OF NEW BIOS CXC1060242 R12A02 109 22-APZ 212 60/4-258
R12 FOR
APUB2
As already specified in APZ 19 User Guide for clone deployment (Ref. 1) the
aforementioned CN-Is are part of AGM320 release as well and they need to
be installed on cloned machine (since IPMI FW and BIOS are related to HW
only).
Limited Internal
INSTRUCTION 30 (40)
Prepared (also subject responsible if other) No.
11 Health Check
Required Alan tool revision for AGM320 clone is:
Due to these bugs, the following ACL errors could be reported by ALAN:
The following folders/files on the active node (B-node) have corrupt ACL's:
Folder/File Unexpected/Missing ACE
------------------------------ ------------------------------
C:\winnt\system32\apaclset.exe AUTHORITY\Authenticated Users:R
C:\winnt\system32\apaclset.exe BUILTIN\Server Operators:C
C:\winnt\system32\apaclset.exe NT AUTHORITY\SYSTEM:F
C:\winnt\system32\integrityap.exe AUTHORITY\Authenticated Users:R
C:\winnt\system32\integrityap.exe BUILTIN\Server Operators:C
C:\winnt\system32\integrityap.exe NT AUTHORITY\SYSTEM:F
C:\Program Files\AP\FIXS\conf\cxc1371373.fmt ITSAAP021D\ACSUSRG:R
C:\Program Files\AP\FIXS\conf\cxc1371373.par ITSAAP021D\ACSUSRG:R
C:\Program Files\AP\ACS\bin\ACS_FCH_Server.exe Missing ACE - Everyone:R
C:\Program Files\AP\ACS\bin\ACS_FCH_Server.exe Missing ACE - ACSADMG:F
C:\Program Files\AP\ACS\bin\fchcommit.exe Missing ACE - ACSADMG:F
C:\Program Files\AP\ACS\bin\fchconf.exe Missing ACE - ACSADMG:F
C:\Program Files\AP\ACS\bin\fchdump.exe Missing ACE - ACSADMG:F
C:\Program Files\AP\ACS\bin\fchend.exe Missing ACE - ACSADMG:F
C:\Program Files\AP\ACS\bin\fchevent.exe Missing ACE - ACSADMG:F
C:\Program Files\AP\ACS\bin\fchfb.exe Missing ACE - ACSADMG:F
C:\Program Files\AP\ACS\bin\fchgen.exe Missing ACE - ACSADMG:F
C:\Program Files\AP\ACS\bin\fchrst.exe Missing ACE - ACSADMG:F
C:\Program Files\AP\ACS\bin\fchstart.exe Missing ACE - ACSADMG:F
C:\Program Files\AP\ACS\bin\fchstate.exe Missing ACE - ACSADMG:F
C:\Program Files\AP\ACS\lib\libACS_FCH_R1A_DMDN7.dll Missing ACE - Everyone:R
C:\Program Files\AP\ACS\lib\libACS_FCH_R1A_DMDN7.dll Missing ACE - ACSADMG:R
C:\Program Files\AP\ACS\lib\libACS_FCH_R1A_DMDN7.dll Missing ACE - ACSUSRG:R
Limited Internal
INSTRUCTION 31 (40)
Prepared (also subject responsible if other) No.
12 REFERENCES
1. AGM320 User Guide for Clone Deployment, 2/198 17-CXP9040184/43-320
14 APPENDIXES
14.1 APPENDIX 1: Post Cloning steps
The appendix reports the steps performed during the execution of the
PostCloning.bat configuration file.
Active-node
3 Link to a Time Zone value (TMZ) and a platform specific Time Zone (TZ).
Both nodes
5 Setting of security.
C:\temp\PostCloning\PostInstall.bat
Passive Node:
14 In order to have the same hostkey files on both nodes, copy the tectia
server hostkey files (hostkey and hostkey.pub) from the active to the
passive node running:
C:\temp\PostCloning\TECTIA\copy_hostkey.vbs
Limited Internal
INSTRUCTION 34 (40)
Prepared (also subject responsible if other) No.
This type of fault usually occurs when launching the backup from node B.
sc \\%COMPUTERNAME:~0,-1%B qc burserver
TYPE : 10 WIN32_OWN_PROCESS
START_TYPE : 2 AUTO_START
ERROR_CONTROL : 1 NORMAL
LOAD_ORDER_GROUP :
TAG : 0
DISPLAY_NAME : burServer
DEPENDENCIES : RpcSs
SERVICE_START_NAME : ITSAAP013D\S9CV1aCqYA1JSN3VcKva
Check that the service user belongs to the global group "Domain Admins":
net group "Domain Admins"
IMPORTANT:
Both Nodes:
strComputerB = "192.168.169.4"
strComputerB = "192.168.169.4"
strComputerB = "192.168.169.4"
In case IPNs AP2 IP addresses are not correctly set within Cloning Tools,
launch the following script:
cd /D c:\temp\PostCloning\script
cscript UpdateCTforAP2.vbs
Limited Internal
INSTRUCTION 37 (40)
Prepared (also subject responsible if other) No.
Active Node
If AP1:
If AP2:
Passive Node
If AP1:
If AP2:
Both Nodes
Verify in the following way that the replication is without errors
”C:\Program files\AP\APOS\Clone\repadmin.exe” /showrepl
Default-First-Site-Name\ITSAAP120A
DC Options: IS_GC
Site Options: (none)
DC object GUID: 195183e1-d9ca-4c14-affe-59dbe3c4b7e1
DC invocationID: 195183e1-d9ca-4c14-affe-59dbe3c4b7e1
DC=ITSAAP120D,DC=int
Default-First-Site-Name\ITSAAP120B via RPC
DC object GUID: bccd0400-98b0-45e2-8b7c-
9d544131c42d
Last attempt @ 2010-11-09 15:52:08 was successful.
CN=Configuration,DC=ITSAAP120D,DC=int
Default-First-Site-Name\ITSAAP120B via RPC
DC object GUID: bccd0400-98b0-45e2-8b7c-
9d544131c42d
Last attempt @ 2010-11-09 15:52:08 was successful.
CN=Schema,CN=Configuration,DC=ITSAAP120D,DC=int
Default-First-Site-Name\ITSAAP120B via RPC
DC object GUID: bccd0400-98b0-45e2-8b7c-
9d544131c42d
Last attempt @ 2010-11-09 15:52:08 was successful.
DC=DomainDnsZones,DC=ITSAAP120D,DC=int
Default-First-Site-Name\ITSAAP120B via RPC
DC object GUID: bccd0400-98b0-45e2-8b7c-
9d544131c42d
Last attempt @ 2010-11-09 15:52:08 was successful.
DC=ForestDnsZones,DC=ITSAAP120D,DC=int
Default-First-Site-Name\ITSAAP120B via RPC
DC object GUID: bccd0400-98b0-45e2-8b7c-
9d544131c42d
Last attempt @ 2010-11-09 15:52:08 was successful.
If there is no replication between the nodes before the installation starts, the
installation may fail. Ensure that replication is working between the two nodes
before starting the installation.
A way to overcome the replication problems could be to force a replication
between the nodes, using the following command:
”C:\Program files\AP\APOS\Clone\repadmin.exe” /syncall
/A
Active Node
Create two files to test File Replication:
If AP1:
copy nul
\\192.168.169.1\c$\winnt\sysvol\domain\scripts\testa.txt
copy nul
\\192.168.170.2\c$\winnt\sysvol\domain\scripts\testb.txt
If AP2:
copy nul
\\192.168.169.3\c$\winnt\sysvol\domain\scripts\testa.txt
copy nul
\\192.168.170.4\c$\winnt\sysvol\domain\scripts\testb.txt
dir \\192.168.169.1\c$\winnt\sysvol\domain\scripts\
dir \\192.168.169.2\c$\winnt\sysvol\domain\scripts\
If AP2:
dir \\192.168.169.3\c$\winnt\sysvol\domain\scripts\
dir \\192.168.169.4\c$\winnt\sysvol\domain\scripts\
del \\192.168.169.2\c$\winnt\sysvol\domain\scripts\testa.txt
del \\192.168.170.1\c$\winnt\sysvol\domain\scripts\testb.txt
If AP2:
del \\192.168.169.4\c$\winnt\sysvol\domain\scripts\testa.txt
del \\192.168.170.3\c$\winnt\sysvol\domain\scripts\testb.txt
dir \\192.168.170.1\c$\winnt\sysvol\domain\scripts\
dir \\192.168.170.2\c$\winnt\sysvol\domain\scripts\
If AP2:
dir \\192.168.170.3\c$\winnt\sysvol\domain\scripts\
dir \\192.168.170.4\c$\winnt\sysvol\domain\scripts\