You are on page 1of 40

Limited Internal

INSTRUCTION 1 (40)
Prepared (also subject responsible if other) No.

TEI/X Team 10/1531-2/CXP9040184/43-320


Approved Checked Date Rev Reference

TEI/XSB EGIORAE EALOFAL 2012-07-05 B AGM320 R1A

AGM320 APG43/2 Cloning Instruction

Abstract

This document describes the configuration steps to be performed on an


already installed APG43/2 system. Good APG43 knowledge is required for
this activity.

Application

This Instruction covers APG43/2 hardware.

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.

TEI/X Team 10/1531-2/CXP9040184/43-320


Approved Checked Date Rev Reference

TEI/XSB EGIORAE EALOFAL 2012-07-05 B AGM320 R1A

1 Revision information

Rev. Date Prepared Description

AGM320 R1A APG43/2


A 2012-06-22 TEIMCEC
APUB2 clone release.

New clone image rev. C


B 2012-07-05 TEIMCEC including CN-I 10922-
APZ21255/1-1096

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.

Details about this new implementation in chapter 5.1 step 2.


Limited Internal
INSTRUCTION 3 (40)
Prepared (also subject responsible if other) No.

TEI/X Team 10/1531-2/CXP9040184/43-320


Approved Checked Date Rev Reference

TEI/XSB EGIORAE EALOFAL 2012-07-05 B AGM320 R1A

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.

3 KNOWN BUGS AND LIMITATIONS


-

4 PREREQUISITES
Hardware and Firmware requirements

• The APG hardware supported for this release is APG43/2 (APUB2


boards)

• The APZ configuration supported is APZ 19.0.


The software level is AGM320 R1A aligned with APZ 19.0 CM005

Multicast Server prerequisites

• Telnet access to the APG43/2 is required to perform cloning.

• Symantec Ghost Solution Suite 1.1 (Which includes Symantec


Ghost 8.3) must be installed prior to the installation of the cloning
software.

• The cloning software will only run on Windows 2000 Professional/Server


SP4, XP Professional SP1a or Windows Server 2003
Standard/Enterprise.

IMPORTANT: Check carefully the following notes

NOTE: In case of Dual AP configuration, during cloning procedures, AP1-AP2


ethernet cables must be unplugged (on the AP side) in order to avoid IP
address conflict inside the internal network. That is due to the fact that
192.168.x.1 and 192.168.x.2 are the default IPN addresses and post cloning
procedures will change them to 192.168.x.3 and 192.168.x.4 in case of AP2
(x is 169 or 170).
Limited Internal
INSTRUCTION 4 (40)
Prepared (also subject responsible if other) No.

TEI/X Team 10/1531-2/CXP9040184/43-320


Approved Checked Date Rev Reference

TEI/XSB EGIORAE EALOFAL 2012-07-05 B AGM320 R1A

NOTE 2: It is required to physically remove CP connections (e.g. unplug


SCB-RP connection cables towards magazines hosting CP blades and
unplug CP-A, CP-B and MAU from the SPX magazine). The same applies to
EGEM2 environment (unplug cables connected to NWI as well).

NOTE 3: It is required to have only one public Ethernet connected to ETH1


(no ETH2 cable shall be present since “no teaming” is the default
configuration)
Limited Internal
INSTRUCTION 5 (40)
Prepared (also subject responsible if other) No.

TEI/X Team 10/1531-2/CXP9040184/43-320


Approved Checked Date Rev Reference

TEI/XSB EGIORAE EALOFAL 2012-07-05 B AGM320 R1A

5 DEPLOY THE CLONE IMAGE INTO AN APG43/2


About how to deploy the clone image into and APG43/2, refer to [1].

For the Clone Image to be deployed, refer to [4]

NOTE: The steps reported in this chapter, if not expressly specified, need to
be performed on both AP1 and AP2 systems.

5.1 Changing Parameters on an already installed machine

This chapter describes how to perform changes, on an already cloned machine,


to: Node Names, IP Addresses, Cluster Name, Cluster IP Address, Domain
Name, Domain Suffix, Subnet Mask and Default Gateway.

NOTE: If parameters already changed or the ConfigMenu.exe /preconfig has


already been performed before CloInstall.vbs (see ref. 1), and no further
changes are required, go directly to chapter 5.2.

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.

IMPORTANT: CloConfig must be executed on machine cloned at Ericsson


factory. CloConfig on updated machine (e.g. via FCH) is not supported.

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:

”c:\Program Files\AP\APOS\clone\CloCleanup.vbs” –deletetemp

Check on both nodes they have been actually removed:


Limited Internal
INSTRUCTION 6 (40)
Prepared (also subject responsible if other) No.

TEI/X Team 10/1531-2/CXP9040184/43-320


Approved Checked Date Rev Reference

TEI/XSB EGIORAE EALOFAL 2012-07-05 B AGM320 R1A

dir \\%COMPUTERNAME:~0,-1%A\c$\temp | findstr –i clone


dir \\%COMPUTERNAME:~0,-1%B\c$\temp | findstr –i clone

NOTE for AP2 only:


In case of AP2 only, follow the actions specified in Appendix 14.3 before
going on with next actions.

Once the actions in Appendix 14.3 have been completed, continue with
next step.

1 ACL backup

Active node A

Backup ACLs for K: drive


ACLdatadiskBackup.bat

Passive node B

2 Aposupdate start on node B

New CLOBIN R1D 109 22-APZ 212 55/4-995 released in AGM320 requires
aposclone service start on node B only.

This action is new compared to CLOBIN R1C present in previous AGM


clones.

Start aposclone service on node B only before launching CloConfig.

WARNING: If this step is missed, the whole procedure is going to fail.

WARNING: This step is required on node B only. If done on node A as


well, the whole procedure is going to fail.

cd /D “C:\Program Files\AP\APOS\clone”

aposclone.bat
Limited Internal
INSTRUCTION 7 (40)
Prepared (also subject responsible if other) No.

TEI/X Team 10/1531-2/CXP9040184/43-320


Approved Checked Date Rev Reference

TEI/XSB EGIORAE EALOFAL 2012-07-05 B AGM320 R1A


The expected printout is the following:

---
--- aposclone startup
---

Volume in drive C is NTSERV


Volume Serial Number is 1434-F528

Directory of C:\PROGRAM FILES\AP\APOS\Clone

05/04/2012 05:25 PM 94,208 aposclone.exe


1 File(s) 94,208 bytes
0 Dir(s) 12,106,698,752 bytes free
---
--- aposclone creation
---
---
--- Desktop Interact property
---
---
--- aposclone auto startup
---
---
--- aposclone starting
---
----------------------------------
--- aposclone query
---

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

Execution log (aposclone.log) is available under “C:\Program


Files\AP\APOS\clone” folder.
Limited Internal
INSTRUCTION 8 (40)
Prepared (also subject responsible if other) No.

TEI/X Team 10/1531-2/CXP9040184/43-320


Approved Checked Date Rev Reference

TEI/XSB EGIORAE EALOFAL 2012-07-05 B AGM320 R1A

3 CloConfig execution

NOTE: Check that the actions specified in chapter 4 have been correctly
performed before starting CloConfig.

NOTE 2: Perform the checks specified in Appendix 14.4 before starting


CloConfig.

Active node A

Start the reconfiguration procedure by running via Remote Desktop:

NOTE: Use only Remote Desktop (GUI)

”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.

TEI/X Team 10/1531-2/CXP9040184/43-320


Approved Checked Date Rev Reference

TEI/XSB EGIORAE EALOFAL 2012-07-05 B AGM320 R1A


Do not reconnect via GUI during this time frame. The operator may
erroneously kill opening windows causing installation failure.

Check whether or not the installation is over with the following command:

Node-A

4 Check the cloInstall.log under c:\temp\Clone:


type c:\temp\clone\cloinstall.log

An example of the expected printout below:

4/24/2012 12:29:01 PM INFO - DCOM settings Update Ended

4/24/2012 12:29:01 PM Return code is 0

4/24/2012 12:29:01 PM Dcomperm has changed settings on the A-


node.

4/24/2012 12:29:03 PM The system is installed and configured.

Both-nodes

5 Check both nodes

Check that both nodes are up and running:


prcstate –l

The printout should be:


active node is up and running
passive node is up and running

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

In case of successful installation, restore the previously saved ACLs for K:


drive:
ACLdatadiskRestore.bat
Limited Internal
INSTRUCTION 10 (40)
Prepared (also subject responsible if other) No.

TEI/X Team 10/1531-2/CXP9040184/43-320


Approved Checked Date Rev Reference

TEI/XSB EGIORAE EALOFAL 2012-07-05 B AGM320 R1A


Since the machine has changed Network Parameters, any previously stored
backup is no longer valid. Remove any reference to the already existing
backup using the procedure reported below:
One node:
- Delete Backup Images on K drive
echo y| del \\<clustername>\k$\images\nodea\*
echo y| del \\<clustername>\k$\images\nodeb\*

- Delete .ddi and DataDiskLayout file (if AP1)


echo y| del \\192.168.169.1\c$\acs\data\bur\*
echo y| del \\192.168.169.2\c$\acs\data\bur\*

- Delete .ddi and DataDiskLayout file (if AP2)


echo y| del \\192.168.169.3\c$\acs\data\bur\*
echo y| del \\192.168.169.4\c$\acs\data\bur\*

- Remove ClusDB directory (if AP1)


rmdir \\192.168.169.1\c$\acs\data\bur\clusdb /s /q
rmdir \\192.168.169.2\c$\acs\data\bur\clusdb /s /q

- Remove ClusDB directory (if AP2)


rmdir \\192.168.169.3\c$\acs\data\bur\clusdb /s /q
rmdir \\192.168.169.4\c$\acs\data\bur\clusdb /s /q

Both-nodes

7 Format D drive

It is required to remove the existing partition backups (related to old node


parameters):
format d: /q

The type of the file system is NTFS.


Enter current volume label for drive D: NTBACKUP
NTBACKUP

WARNING, ALL DATA ON NON-REMOVABLE DISK


DRIVE D: WILL BE LOST!
Proceed with Format (Y/N)? y
y
QuickFormatting 20928M

Format cannot run because the volume is in use by another


process. Format may run if this volume is dismounted first.
ALL OPENED HANDLES TO THIS VOLUME WOULD THEN BE INVALID.
Would you like to force a dismount on this volume? (Y/N) y
y
Volume dismounted. All opened handles to this volume are now
invalid.
Volume label (32 characters, ENTER for none)? NTBACKUP
NTBACKUP
Limited Internal
INSTRUCTION 11 (40)
Prepared (also subject responsible if other) No.

TEI/X Team 10/1531-2/CXP9040184/43-320


Approved Checked Date Rev Reference

TEI/XSB EGIORAE EALOFAL 2012-07-05 B AGM320 R1A


Creating file system structures.
Format complete.
21430708 KB total disk space.
21364308 KB are available.

Both-nodes

8 Restore the right ACLs on BUR directory


echo y| cacls c:\ACS\data\BUR /T /G Administrators:F
ACSADMG:F ACSUSRG:R

Passive node B

9 aposclone service removal

Remove aposclone service on node B only after completing CloConfig


phase.
cd /D “C:\Program Files\AP\APOS\clone”

aposclone_clean.bat

The expected printout is the following:

--- aposclone chk

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:

The specified service does not exist as an installed service.

Done

NOTE:

After the reconfiguration is finished some Post Cloning steps need to be


applied.
Limited Internal
INSTRUCTION 12 (40)
Prepared (also subject responsible if other) No.

TEI/X Team 10/1531-2/CXP9040184/43-320


Approved Checked Date Rev Reference

TEI/XSB EGIORAE EALOFAL 2012-07-05 B AGM320 R1A

10 Post Cloning steps

Once CloConfig is completed, perform the actions specified below:

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

If an error is returned, execute the operation on the other node.


In case the write cache is enabled, disable it by using the following
command:
“C:\Program Files\AP\APOS\clone\dskcache.exe” -w
PhysicalDrive1
“C:\Program Files\AP\APOS\clone\dskcache.exe” –w
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.

TEI/X Team 10/1531-2/CXP9040184/43-320


Approved Checked Date Rev Reference

TEI/XSB EGIORAE EALOFAL 2012-07-05 B AGM320 R1A

5.2 Post cloning steps

Active Node (Node A):

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:

11 Verify the Cluster Group is up and running


cluster group

If not, start the needed resources manually

12 Refresh the explorer process in order to make visible drives I and K


c:\temp\PostCloning\script\RefreshExplorer.bat

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

Where the “TZ_name” can be obtained using tzls command

Skip the following printout which may eventually occur at the end of
PostCloning script execution:
--- Configuration of the Passive Node finished ---

The process cannot access the file because it is being used by


another process.

For more details regarding the PostCloning.bat procedure refer to [14].

5.2.1 SSH Tectia settings

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.

TEI/X Team 10/1531-2/CXP9040184/43-320


Approved Checked Date Rev Reference

TEI/XSB EGIORAE EALOFAL 2012-07-05 B AGM320 R1A

5.3 AP2 Reconfiguration

In case of AP1 configuration, skip this chapter and go to chapter 0.

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.

The steps reported in this chapter have to be performed only when


configuring a system with two APGs and they apply to AP2 only.
It requires that all the steps in chapter 5.2 have been executed.

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:

• AP configuration (AP2 in our case)

• Node (Node A in our case)

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”.

2. Update the Reverse Lookup Zone pointers for AP2:


c:\TEMP\PostCloning\Utils\DNS\DNS_AP2_nodeA.bat

3. Reboot the node


prcboot -f

Wait until the restarted node is up again.

Active Node (Node B)

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.

TEI/X Team 10/1531-2/CXP9040184/43-320


Approved Checked Date Rev Reference

TEI/XSB EGIORAE EALOFAL 2012-07-05 B AGM320 R1A


NOTE: Do not take into account the error “ERROR: The network path was not
found. dsrm failed:DC=2,DC=169.168.192.in-
addr.arpa,CN=MicrosoftDNS,CN=System,DC=ITSAAP021D,DC=int:Directory
object not found”.

5. Update the Reverse Lookup Zone pointers for AP2 node B:


c:\TEMP\PostCloning\Utils\DNS\DNS_AP2_nodeB.bat

6. Reboot the node


prcboot -f

Wait until the restarted node is up again.

Both Nodes

7. Update the swrsid for AP2


c:\TEMP\PostCloning\swrprod_AGM320_AP2.bat

6 HCS service handling

Both Nodes

Launch the following command


setuphcservice -n

Here’s an example of expected printout:

Copyright (C) Ericsson AB. All rights reserved.

Registry value "HCServiceUser" was deleted.

User G7fF468YzkYDFUF removed as HC service user.

WARNING: If the cluster service is running on one of the nodes,


make sure to reboot that node after this operation.

Adding user nyJEIz12RDQZgWT to the system. This user will be used


to

run HC service that need to be run as a user with Administrator


rights.

ACS_HCS_Service will be changed to run as this user.

Updating services: ACS_HCS_Service - Updated

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.

TEI/X Team 10/1531-2/CXP9040184/43-320


Approved Checked Date Rev Reference

TEI/XSB EGIORAE EALOFAL 2012-07-05 B AGM320 R1A


Start ACS_HCS_Service:
c:\temp\PostCloning\script\HCS_start.bat

This script will configure the service as automatic start-up type and start it on
AP1.

It will be “demand start” and stopped on AP2.

7 SPOE IP BACKUP Definition (both AP1 and AP2)

Active-node

1. Run the following script in order to configure SPOE_IP_BACKUP:


c:\temp\PostCloning\SPOE_IP_BACKUP_PA3.bat
Limited Internal
INSTRUCTION 17 (40)
Prepared (also subject responsible if other) No.

TEI/X Team 10/1531-2/CXP9040184/43-320


Approved Checked Date Rev Reference

TEI/XSB EGIORAE EALOFAL 2012-07-05 B AGM320 R1A

8 Setup AP1 and AP2 for APZ connection


The steps reported below explain some basic tasks to be done in order to
allow CP-AP communication from an APG perspective.

Active-node

8.1 AP1/AP2 configuration: Common Part


In case of dual AP configuration, if not differently specified, the steps reported
below need to be performed on both the APGs.

Active-node

1. Assign the Administrator user the right permission to connect to the CP:
c:\temp\PostCloning\Utils\Administrator_permission.bat

The expected printout is:


Assign the the Administrator user the right permission to connect to
the CP

net localgroup ACSADMG Administrator /add


The command completed successfully

net localgroup MCSADMG Administrator /add


The command completed successfully

net localgroup CPADMG Administrator /add


The command completed successfully

Done!

2. ACS_APCONFBIN_CpAndProtocolType parameter change

Perform a soft function change session in order to set the correct value for
ACS_APCONFBIN_CpAndProtocolType (see ref. [2]).
The possible values are:

ACS_APCONFBIN_CpAndProtocolType APZ level


1 APZ2123x
2 APZ21240
3 APZ21250
APZ21255
4 APZ21260
Blade Cluster
Limited Internal
INSTRUCTION 18 (40)
Prepared (also subject responsible if other) No.

TEI/X Team 10/1531-2/CXP9040184/43-320


Approved Checked Date Rev Reference

TEI/XSB EGIORAE EALOFAL 2012-07-05 B AGM320 R1A

In case of parameter value equal to 1, continue with chapter 8.1.1.

In case of parameter value equal to 2, continue with chapter 8.1.2.

In case of parameter value equal to 3, continue with chapter 8.1.3.

In case of parameter value equal to 4, continue with chapter 8.1.4.

8.1.1 APG43/2 in APZ2123X source systems

This configuration refers to APG43 based IO systems in a Single CP


configuration for the following source systems:

• APZ21230

• APZ21233

• APZ21233/C

In order to allow the connection from an APG43 towards an APZ2123x check


the following parameters:

Active node

1. Verify that following parameter’s value is 1:


phaprint ACS_APCONFBIN_CpAndProtocolType

2. Verify that following parameter’s value is 0:


phaprint ACS_CSBIN_isMultipleCPSystem

The aforementioned values are the default ones.

3. Define the TFTP root:


C:\temp\PostCloning\APZ21233x\TFTP_root_set.bat

4. Define the entries for IPNA:


C:\temp\PostCloning\APZ21233x\host_entries_PA3.bat

5. Restart CS services:
C:\temp\PostCloning\APZ21233x\restartCS_delay.bat
Limited Internal
INSTRUCTION 19 (40)
Prepared (also subject responsible if other) No.

TEI/X Team 10/1531-2/CXP9040184/43-320


Approved Checked Date Rev Reference

TEI/XSB EGIORAE EALOFAL 2012-07-05 B AGM320 R1A

8.1.2 APG43/2 connected to APZ 212 40

This configuration refers to APG43 based IO systems in a Single CP


configuration for the following source systems:

• APZ 212 40

In order to allow the connection from an APG43 towards an APZ 212 40


check the following parameters:

Active node

1. Verify that following parameters’ value is 2:


phaprint ACS_APCONFBIN_CpAndProtocolType
phaprint MAS_CPTASP_Protocol

If not, change them to 2 via Soft Function Change.

2. Restart CS services:
C:\temp\PostCloning\APZ21233x\restartCS_delay.bat

Go to chapter 8.2 to configure CS parameters (if required) or go to chapter


8.3.
Limited Internal
INSTRUCTION 20 (40)
Prepared (also subject responsible if other) No.

TEI/X Team 10/1531-2/CXP9040184/43-320


Approved Checked Date Rev Reference

TEI/XSB EGIORAE EALOFAL 2012-07-05 B AGM320 R1A

8.1.3 APG43/2 connected to APZ 212 50

This configuration refers to APG43 based IO systems in a Single CP


configuration for the following source systems:

• APZ 212 50

In order to allow the connection from an APG43 towards an APZ 212 40


check the following parameters:

Active node

1. Verify that following parameter’s value is 3:


phaprint ACS_APCONFBIN_CpAndProtocolType
phaprint MAS_CPTASP_Protocol

If not, change them to 3 via Soft Function Change.

2. Restart CS services:
C:\temp\PostCloning\APZ21233x\restartCS_delay.bat

Go to chapter 8.2 to configure CS parameters (if required) or go to chapter


8.3.
Limited Internal
INSTRUCTION 21 (40)
Prepared (also subject responsible if other) No.

TEI/X Team 10/1531-2/CXP9040184/43-320


Approved Checked Date Rev Reference

TEI/XSB EGIORAE EALOFAL 2012-07-05 B AGM320 R1A

8.1.4 APG43/2 in blade configuration or APZ21255/APZ21260

Active node

1. Verify that following parameter’s value is 4:


phaprint ACS_APCONFBIN_CpAndProtocolType
phaprint MAS_CPTASP_Protocol

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, continue with next step, otherwise go to chapter


8.3

3. Connect AP1/AP2 ethernet connection cables

CONNECT CABLES FROM AP1 TO AP2.

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

4. Verify the AP2 respond to ping


ping -n 2 192.168.169.34

5. Add SPOE address of AP2


swmanage –ah ap_2 192.168.169.34

Go to chapter 8.3.
Limited Internal
INSTRUCTION 22 (40)
Prepared (also subject responsible if other) No.

TEI/X Team 10/1531-2/CXP9040184/43-320


Approved Checked Date Rev Reference

TEI/XSB EGIORAE EALOFAL 2012-07-05 B AGM320 R1A

8.2 CS parameters

Active node A

Check current CSBIN parameters:


nels

If changes of CS parameters are required, launch the following script from


active node A only:
C:\temp\PostCloning\CSparameters_both_nodes.bat X

Where X can be any of the following values, according to specific CSBIN


parameters’ settings:

X ACS_CSBIN_aptType ACS_CSBIN_nodeArchitecture ACS_CSBIN_isMultipleCPSystem

1 MSC Component Based Architecture SCP

NOT Component Based


3 MSC
Architecture
SCP

NOT Component Based


4 MSC
Architecture
MCP

5 BSC Component Based Architecture SCP

NOT Component Based


6 BSC
Architecture
SCP

7 HLR Component Based Architecture SCP

NOT Component Based


9 HLR
Architecture
SCP

NOT Component Based


10 HLR
Architecture
MCP

11 WLN Component Based Architecture SCP

NOT Component Based


13 WLN
Architecture
SCP

NOT Component Based


14 WLN
Architecture
MCP
Limited Internal
INSTRUCTION 23 (40)
Prepared (also subject responsible if other) No.

TEI/X Team 10/1531-2/CXP9040184/43-320


Approved Checked Date Rev Reference

TEI/XSB EGIORAE EALOFAL 2012-07-05 B AGM320 R1A

Option number 3 should not be used in case ACS_CSBIN_aptType value is


MSC, ACS_CSBIN_nodeArchitecture value is “NOT Component Based
Architecture” and ACS_CSBIN_isMultipleCPSystem value is SCP since these
three CS parameters are the default ones and no change is required.

An example of the expected printout is the following:


---
--- CSBIN CXC is
---
CXC1371340

----
---- Chosen configuration is MSC CBA SCP (1)
----

Edit parameter ACS_CSBIN_isMultipleCPSystem (assign value 0)


Edit parameter ACS_CSBIN_nodeArchitecture (assign value 1)
Edit parameter ACS_CSBIN_aptType (assign value 0)

---
--- 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.

TEI/X Team 10/1531-2/CXP9040184/43-320


Approved Checked Date Rev Reference

TEI/XSB EGIORAE EALOFAL 2012-07-05 B AGM320 R1A

---
--- 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
---

Passive Node is busy... Wait for execution to be finished


0

----------------------------------------------------------
--- 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.

TEI/X Team 10/1531-2/CXP9040184/43-320


Approved Checked Date Rev Reference

TEI/XSB EGIORAE EALOFAL 2012-07-05 B AGM320 R1A

Directory of c:\temp\PostCloning\logs

File Not Found


--- deleting c:\temp\PostCloning\logs\ACS_CSBIN_OK.txt
Volume in drive C is NTSERV
Volume Serial Number is 0C06-E964

Directory of c:\temp\PostCloning\logs

File Not Found


File Not Found
File Not Found
File Not Found
File Not Found
File Not Found
File Not Found
---
--- Checking CS parameters consistency on node A
---
05/04/2012 06:44 PM 9 ACS_CSBIN_OK.txt
---
--- Checking CS parameters consistency on node B
---
192.168.169.2
05/04/2012 06:44 PM 9 ACS_CSBIN_OK.txt

--------------------------------------------------------------------
--- CS parameters are aligned on both nodes
--------------------------------------------------------------------

---
--- "Restarting the whole Cluster except the "Cluster Group":"
---

Bringing resource group 'Disk Group' offline...

System error 5020 has occurred (0x0000139c).


The cluster resource could not be deleted or brought offline because
it is the quorum resource.

Bringing resource group 'RGAPM_0' offline...


Limited Internal
INSTRUCTION 26 (40)
Prepared (also subject responsible if other) No.

TEI/X Team 10/1531-2/CXP9040184/43-320


Approved Checked Date Rev Reference

TEI/XSB EGIORAE EALOFAL 2012-07-05 B AGM320 R1A

Group Node Status


-------------------- --------------- ------
RGAPM_0 ITSAAP021A Offline

Bringing resource group 'Disk Group' online...

Group Node Status


-------------------- --------------- ------
Disk Group ITSAAP021A Online

--- Execution Finished successfully


---
--- Waiting for clean-up
--- Logs available inside c:\temp\Postcloning\logs folder on both
nodes:
--- CSparameters_all.log on Active node (Full log)
--- CSparameters_chk_A.log on Active node (Consistency check for
"conf" and "fch" folders)
--- CSparameters_chk_B.log on Passive node (Consistency check for
"conf" and "fch" folders)
---
--- THE END
---

Both nodes

Check nels printout on both nodes and verify it is aligned:


nels
Limited Internal
INSTRUCTION 27 (40)
Prepared (also subject responsible if other) No.

TEI/X Team 10/1531-2/CXP9040184/43-320


Approved Checked Date Rev Reference

TEI/XSB EGIORAE EALOFAL 2012-07-05 B AGM320 R1A

8.3 Data Disk Quota Configuration

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

Set the right quota configuration


ssucfg -c <config> –f

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

Check new configuration:


ssuls

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.

8.4 IPMI and BIOS for APUB2

Verify the Firmware (IPMI and BIOS versions) installed on the boards:
ipmi_upg –f
wmic CSproduct List Status

In APZ19 the following CN-Is have been included:

• IPMI FW CXC138844 R13A (109 22-APZ 212 60/4-257)

• BIOS CXC1060242 R12A02 (109 22-APZ 212 60/4-258)

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.

TEI/X Team 10/1531-2/CXP9040184/43-320


Approved Checked Date Rev Reference

TEI/XSB EGIORAE EALOFAL 2012-07-05 B AGM320 R1A

9 Final Configuration Steps


AP1 Active node A

1. Update nodes
swmanage -s

AP1 Active node

2. Once CP-AP communication is completed, in order to allow a User to


access CP via MML sessions, follow OPI AP, Authority, Administer to
properly define User authority.

AP1/AP2 Active node A

3. Reboot the active node via prcboot command


prcboot -f

AP1/AP2 Active node B

4. Wait until the rebooted node is up again

Reboot the other node now active:


prcboot -f

Wait until the node is up again

AP1/AP2 both nodes

Due to TR HQ16402, the following actions are required:

echo y| cacls "C:\Program Files\AP\ACS\conf\CXC1371355.fmt" /T /G


Administrators:F ACSADMG:F ACSUSRG:R

echo y| cacls "C:\Program Files\AP\ACS\conf\CXC1371355.par" /T /G


Administrators:F ACSADMG:F ACSUSRG:R

echo y| cacls "C:\Program Files\AP\ACS\conf\CXC1371355.rsc" /T /G


Administrators:F ACSADMG:F ACSUSRG:R

echo y| cacls "C:\Program Files\AP\FIXS\conf\CXC1371373.fmt" /T /G


ACSUSRG:R Administrators:F APZADMG:F APZUSRG:R

echo y| cacls "C:\Program Files\AP\FIXS\conf\CXC1371373.par" /T /G


ACSUSRG:R Administrators:F APZADMG:F APZUSRG:R

echo y| cacls "C:\Program Files\AP\FIXS\conf\CXC1371373.tra" /T /G


Administrators:F APZADMG:F APZUSRG:R

echo y| cacls "C:\Program Files\AP\FIXS\conf\CXC1371373.rsc" /T /G


Administrators:F APZADMG:F APZUSRG:R
Limited Internal
INSTRUCTION 29 (40)
Prepared (also subject responsible if other) No.

TEI/X Team 10/1531-2/CXP9040184/43-320


Approved Checked Date Rev Reference

TEI/XSB EGIORAE EALOFAL 2012-07-05 B AGM320 R1A


echo y| cacls "C:\Program Files\AP\ACS\etc\HCS_service_def" /T /G
Administrators:F ACSADMG:F ACSUSRG:R

echo y| cacls "C:\Program Files\AP\PES\bin\sells.exe" /T /G


Administrators:F APZADMG:F APZUSRG:R

echo y| cacls "C:\Program Files\AP\PES\bin\seltran.exe" /T /G


Administrators:F APZADMG:F APZUSRG:R

10 HW info
In APZ19 the following APHW CN-Is have been included:

Block Block Rev. CN-I


number

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.

TEI/X Team 10/1531-2/CXP9040184/43-320


Approved Checked Date Rev Reference

TEI/XSB EGIORAE EALOFAL 2012-07-05 B AGM320 R1A

11 Health Check
Required Alan tool revision for AGM320 clone is:

• R9A or higher during post Health Check

The following bugs and limitations apply:

• TR HP17755 : AGM319: ACLs on K:\APZ\data wrongly set @


OCS_IPNAADM service restart.

• TR HP17766 : AGM319: ACLs on K:\CPS\logs wrongly set @


CPS_Tesrv service restart

• TR HP18799 : ACS:FCH: FCH dll permission change when the node


restarts.

• TR HP18811 : ACS:LCT: acls change after restart of node

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.

TEI/X Team 10/1531-2/CXP9040184/43-320


Approved Checked Date Rev Reference

TEI/XSB EGIORAE EALOFAL 2012-07-05 B AGM320 R1A


C:\acs\data\FCH Missing ACE - ACSADMG:F
C:\acs\data\FCH Missing ACE - ACSUSRG:R
C:\acs\logs\ALOG NT AUTHORITY\SYSTEM:(OI)(CI)F
C:\acs\logs\ALOG Missing ACE - ACSADMG:F
C:\acs\logs\ALOG Missing ACE - ACSUSRG:R
C:\acs\logs\EMF Missing ACE - ACSADMG:F
F:\acs\data\EMF NT AUTHORITY\SYSTEM:(OI)(CI)F
K:\APZ\data Missing ACE - SYSTEM:F
K:\APZ\data Missing ACE - Everyone:R
K:\CPS\logs Missing ACE - SYSTEM:F
K:\CPS\logs Missing ACE - Everyone:R
Limited Internal
INSTRUCTION 32 (40)
Prepared (also subject responsible if other) No.

TEI/X Team 10/1531-2/CXP9040184/43-320


Approved Checked Date Rev Reference

TEI/XSB EGIORAE EALOFAL 2012-07-05 B AGM320 R1A

12 REFERENCES
1. AGM320 User Guide for Clone Deployment, 2/198 17-CXP9040184/43-320

2. APG40, Soft Function Change, Parameter, Change 3/154 31-CNZ 222 81


3. AP, ADJUNCT PROCESSOR, ADD, 2/154 31-ANZ 222 43/3 Rev. A.
4. Clone Image for AGM320, 10/190 99-2/CXP9040184/43 Rev C

13 ABBREVIATIONS AND TERMINOLOGY


See Terminology and Abbreviation, Ref. #1, for most abbreviations and
terminology.
BDC = Backup Domain Controller
CMD = Command window
HW = Hardware
PDC = Primary Domain Controller
Limited Internal
INSTRUCTION 33 (40)
Prepared (also subject responsible if other) No.

TEI/X Team 10/1531-2/CXP9040184/43-320


Approved Checked Date Rev Reference

TEI/XSB EGIORAE EALOFAL 2012-07-05 B AGM320 R1A

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

1 Run of the configap command in order to create file and directory


structure.
configAP –i –s

Ignore the error messages regarding:


Adding user rights...
ERROR: Failed to deny network logon rights to SUPPORT_388945a0
. . .
ERROR: Failed to copy c:\acs\logs\lct\SetupService.def to
C:\WINNT\system32\SepService.def: The file exists.

2 Replication of the Active Directory towards the other node.


“C:\Program Files\AP\APOS\clone\repadmin.exe” /syncall

3 Link to a Time Zone value (TMZ) and a platform specific Time Zone (TZ).

Both nodes

4 Setting of the ACLs using the released ACL.dat file.


configAP –a

5 Setting of security.
C:\temp\PostCloning\PostInstall.bat

6 Removal of CloPrep.vbs, SETUPCL.exe and SYSPREP.exe in order to


avoid recloning of an installed machine.
7 In order to avoid the same couple of SSH TECTIA keys on all the
machines installed with the same clone image, the following script have to
be launched:
C:\temp\PostCloning\TECTIA\regenerateKeys.bat

8 Restart the TECTIA configuration tool executing the command:


C:\Program Files\SSH Communications Security\SSH Tectia\SSH
Tectia Server\ssh-server-config-tool.exe

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.

TEI/X Team 10/1531-2/CXP9040184/43-320


Approved Checked Date Rev Reference

TEI/XSB EGIORAE EALOFAL 2012-07-05 B AGM320 R1A


15 Restart the TECTIA configuration tool executing the command:
“C:\Program Files\SSH Communications Security\SSH Tectia\SSH
Tectia Server\ssh-server-config-tool.exe”

14.2 APPENDIX 2: Workaround for burbackup


In case of “burbackup –o” failure like the following:
SetTombstoneLifetime Failed : Access is denied.

-- Extended Error --- LDAP Provider : 00002098: SecErr: DSID-


03150A45, problem 4003 (INSUFF_ACCESS_RIGHTS), data 0

Failed to purge the Deleted Objects container in Active Directory


Domain Services

Apply the workaround listed in TR HL66748.

This type of fault usually occurs when launching the backup from node B.
sc \\%COMPUTERNAME:~0,-1%B qc burserver

The printout should look like the following


SERVICE_NAME: burserver

TYPE : 10 WIN32_OWN_PROCESS

START_TYPE : 2 AUTO_START

ERROR_CONTROL : 1 NORMAL

BINARY_PATH_NAME : C:\Program Files\AP\ACS\bin\burServer.exe

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"

Add the user (e.g. S9CV1aCqYA1JSN3VcKva) to the "Domain Admins" group


if it does not belong to it.
Limited Internal
INSTRUCTION 35 (40)
Prepared (also subject responsible if other) No.

TEI/X Team 10/1531-2/CXP9040184/43-320


Approved Checked Date Rev Reference

TEI/XSB EGIORAE EALOFAL 2012-07-05 B AGM320 R1A


net group "Domain Admins" <username> /add

Stop and start burServer on both nodes:


sc \\%COMPUTERNAME:~0,-1%B stop burserver

sc \\%COMPUTERNAME:~0,-1%B start burserver

sc \\%COMPUTERNAME:~0,-1%A stop burserver

sc \\%COMPUTERNAME:~0,-1%A start burserver

14.3 APPENDIX 3: AP2 configuration checks

IMPORTANT:

Check that the actions specified in chapter 4 have been performed.

Perform the following actions:

Both Nodes:

1 Check that FewerClones script has correctly updated AP2 IPN IP


addresses inside Cloning tools:
type "c:\program files\AP\APOS\clone\CloParam.vbs" | findstr
-i 192
type "c:\program files\AP\APOS\clone\cloCheck.vbs" | findstr
-i 192
type "c:\program files\AP\APOS\clone\CloCleanUp.vbs" |
findstr -i 192
type "c:\program files\AP\APOS\clone\CloInstall.vbs" |
findstr -i 192
type "c:\program files\AP\APOS\clone\CloneReg.vbs" | findstr
-i 192

An example of the expected printout is:

'CONST BackPlane_A = "192.168.169.3"


Limited Internal
INSTRUCTION 36 (40)
Prepared (also subject responsible if other) No.

TEI/X Team 10/1531-2/CXP9040184/43-320


Approved Checked Date Rev Reference

TEI/XSB EGIORAE EALOFAL 2012-07-05 B AGM320 R1A


'CONST BackPlane_B = "192.168.169.4"

Const NodeB_IPaddress= "192.168.169.4"

Const NodeB_IPaddress= "192.168.169.4"

strComputerB = "192.168.169.4"

strComputerB = "192.168.169.4"

strComputerB = "192.168.169.4"

Neither 192.168.169.1 nor 192.168.169.2 IPs shall be present inside the


printout.

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.

TEI/X Team 10/1531-2/CXP9040184/43-320


Approved Checked Date Rev Reference

TEI/XSB EGIORAE EALOFAL 2012-07-05 B AGM320 R1A

14.4 Active Directory and File Replication checks

Before starting CloConfig, perform the following checks:


Check if date and time on both nodes are synchronized, using the following
commands:

Active Node
If AP1:

net time \\192.168.169.1


net time \\192.168.169.2

If AP2:

net time \\192.168.169.3


net time \\192.168.169.4

If not, synchronize both nodes using the following commands:

Passive Node
If AP1:

net time \\192.168.169.33 /SET /y

If AP2:

net time \\192.168.169.34 /SET /y

Both Nodes
Verify in the following way that the replication is without errors
”C:\Program files\AP\APOS\Clone\repadmin.exe” /showrepl

Here’s an example of printout without errors:

repadmin running command /showrepl against server


localhost

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

==== INBOUND NEIGHBORS


======================================
Limited Internal
INSTRUCTION 38 (40)
Prepared (also subject responsible if other) No.

TEI/X Team 10/1531-2/CXP9040184/43-320


Approved Checked Date Rev Reference

TEI/XSB EGIORAE EALOFAL 2012-07-05 B AGM320 R1A

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

Following an example of the output:



CALLBACK MESSAGE: The following replication is in progress:
From: b9352ede-04aa-478c-a03b-23292cf0c98a._msdcs.ap212dom.int
To : c368391d-3f05-414b-8e99-829483a2b432._msdcs.ap212dom.int
CALLBACK MESSAGE: The following replication completed
successfully:
Limited Internal
INSTRUCTION 39 (40)
Prepared (also subject responsible if other) No.

TEI/X Team 10/1531-2/CXP9040184/43-320


Approved Checked Date Rev Reference

TEI/XSB EGIORAE EALOFAL 2012-07-05 B AGM320 R1A


From: b9352ede-04aa-478c-a03b-23292cf0c98a._msdcs.ap212dom.int
To : c368391d-3f05-414b-8e99-829483a2b432._msdcs.ap212dom.int
CALLBACK MESSAGE: SyncAll Finished.
SyncAll terminated with no errors.

The command doesn't solve any replication problem. It only facilitates


replication to happen at that moment (without waiting for the scheduled
replication) provided there are no replication problems, and thus avoids
situations like the user being found in one node and not found in the other.
Basically it will synchronize the active directory details instantaneously. If a
machine is not able to replicate this means that there is some fault with the
machine (probably due to a bad restore or due to some other reason).
If there is no replication between the nodes before the installation starts, the
installation may fail. If there is a problem with replication contact the next level
of support.

File replication check:

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

Verify if both files are present in both nodes:


If AP1:

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\

Remove the test files:


Limited Internal
INSTRUCTION 40 (40)
Prepared (also subject responsible if other) No.

TEI/X Team 10/1531-2/CXP9040184/43-320


Approved Checked Date Rev Reference

TEI/XSB EGIORAE EALOFAL 2012-07-05 B AGM320 R1A


If AP1:

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

Verify if both files have been deleted in both nodes:


If AP1:

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\

You might also like