You are on page 1of 50

BSC

HW Acceptance Test Procedures

BSC Acceptance Test Procedures


Contents
1.

APG43 Tests................................................................................................................3
1.1.
APG43 HW structure...........................................................................................3
1.2.
Initial APG43 tests...............................................................................................5
1.3.
Test APIO SW and STS SW are installed and activated.....................................6
1.4.
FAN test...............................................................................................................8
1.5.
Test of IO Device.................................................................................................9
1.6.
Configuration Change for the SSU Folder..........................................................9
1.7.
Backup of APG43 SW and Transfer to DVD....................................................10
1.8.
Restore of APG43 SW from DVD.....................................................................13
1.9.
NSF (Network Surveillance Function) testing..................................................14
1.10.
Failover test (prcboot)....................................................................................14
1.11.
FTP test..........................................................................................................15
2. APZ 212 55 Tests.......................................................................................................16
2.1
APZ 212 55 HW configuration..........................................................................16
2.2
Manual Intervention when CP-A is EX.............................................................17
2.3
Manual Intervention when CP-B is EX.............................................................18
2.4
Manual Initiated Small Restart..........................................................................20
2.5
Manual Initiated Large Restart..........................................................................21
2.6
Activate the Command Log...............................................................................22
2.7
Manual Initiated Large Restart with Reload from MS......................................23
2.8
Manual Initiated Large Restart with Reload from File......................................26
2.9
FEX Load on CP-A...........................................................................................28
2.10 FEX Load on CP-B............................................................................................29
2.11 Function Change Method II...............................................................................30
2.12 Initial Loading of CP-A.....................................................................................32
2.13 Initial Loading of CP-B.....................................................................................37
3
APT Tests:..................................................................................................................43
3.1
Check of RPs and EMs......................................................................................43
3.2
Test of CLM.......................................................................................................43
3.3
Test of XM.........................................................................................................45
3.4
Test of MUX3....................................................................................................46
3.5
Final Test of XM................................................................................................47
3.6
Test of RCM.......................................................................................................48
3.7
Test of ET...........................................................................................................49

1. APG43 Tests
1.1.

APG43 HW structure

The APG43 contains the following boards, which are located in an eGEM. The eGEM
magazine with the APG43 always contain an APZ 212 55.
APUB
The APUB is a GEP board. APG43 contains two boards, one per side.
Disk
The disk is a GED board. APG43 contains two boards, one per side.
DVD
The DVD is a GED board. APG43 contains one optional board.
Alarm
The alarm is a GEA board. APG43 contains one optional board.

Figure 1 APG43 connectivity

Figure 2 APG43 connectivity

Figure 3 BSC APG43 configuration

Figure 4 APG43 external connectivity

1.2.

Initial APG43 tests

Logon via remote desktop over the public network towards both sides of the APG43.
Before start of test it should be verified that the system is running normally.
1. Logon to the active APG43 side.
Check that you are connected to the active side:
C:\>prcstate
Printout: active
2. Print the Cluster_name and the Host_name from the active side:
C:\>cluster /ver

C:\>hostname
3. Check that all cluster groups are online:
C:\>cluster group
Printout: Status is listed for all available resource groups.
4. Check that all cluster resources are online:
C:\>cluster res
Printout: Listing status for all available resources
5. Check that the right SW is installed:
C:\>swrprint
Printout: AP SOFTWARE CHARACTERISTICS
6. Check that the right time zone is set:
C:\>mtzln -p
7. Check the date:
C:\>date
Printout: The current date is: day mm/dd/yyyy
Enter the new date: (mm-dd-yy)
Note: Enter RETURN or new date.
8. Check the time:
C:\>time
Printout: The current time is: hh:mm:ss
Enter the new time:
Note: Enter RETURN or new time.
9. List all alarms on APG:
C:\>alist
Note: Clear all alarms by using the appropriate OPI. Some alarms might not be cleared
here due to the missing CP connection (for example "AP SYSTEM CLOCK NOT
SYNCHRONIZED").
1.3.

Test APIO SW and STS SW are installed and activated

1. Open a command prompt:


Start -> All Programs -> Accessories -> Command Prompt
6

C:\>dsdls -a
The printout must contain:
node cp0
node ap1a or ap1b
Connect to the CP through the AD-ports. Use the SW Winfiol. Verify that the CP AP connection is enabled.
C:\>mml APAMP;
Printout: AP MAINTENANCE DATA
2. Test of MCS.
C:\>cpdtest -c
Printout: STATE must have the value CONNECTED
Start an MML session (with spontaneous printouts).
C:\>mml a
<IOMSP;
Printout: IO MML SERVICE DATA
<IOCDP;
Printout: IO CONFIGURATION DATA
Leave the MML session:
<EXIT;
3. Test of FMS.
C:\>cpfls -ls
Printout: CP FILE TABLE
4. Test of MAS.
C:\>mml a
<PTCOI;
CPT<PTWSP;
Printout: CP STATUS
End the session:
CPT<PTCOE;

5. Test of CPS.
List all defined system backup files:
<SYBFP:FILE;
Release the terminal:
<CTRL-D>
Printout: SYSTEM BACKUP FILES
Leave the MML session:
<EXIT;
Print the parameters for backup generation handling.
C:\>bupls
If any value is faulty, change it by using the command bupdef.
C:\>bupdef -n <ffr> -m <sfr> -s <sup>

1.4.

FAN test

This chapter can be omitted when the APG43 is delivered standalone, or if the fan
has been tested earlier.
1. Connect the power cabling to the Fan subrack.
2. Return to Central Processor (CP) mode.
C:\>exit
3. Make sure the alarm list is empty.
<ALLIP;
Printout: ALARM LIST
4. Switch to AP local mode on the AP where the procedure is to be done.
<APLOC;
The prompt changes from (<) to the Shell prompt.
5. Loosen one of the fan units and pull it out, or disconnect the power to the
Fans, or disconnect the cable to the fan subrack.
6. Verify that an alarm is indicated by the system.
7. Restore the fan unit or cable.

8. Verify that the alarm has ceased.


9. Repeat step 1 on page 8 to step 8 on page 9 for all fans in the magazine
Using the fan alarm function.

1.5.

Test of IO Device

The test in this chapter must only be done if the APG43 also has got the APIO
SW installed, that is, it is only for AP1.
In this test the connection ports for AD-terminals are checked and tested.
1. IO Device in CP, Attributes.
C:\>cpdlist -l
2. Print CP-AP connections.
C:\>cpdtest -c
3. Change IO Device in CP if the test is not successful.
C:\>cpdchange < . . .>
4. Return to Central Processor (CP) mode.
C:\>exit
5. Print IO device table.
<IOIOP:IO1=ALL;
Printout: IO DEVICE DATA
6. Switch to AP local mode on the AP where the procedure is to be
done.
<APLOC;
The prompt changes from (<) to the Shell prompt
1.6.

Configuration Change for the SSU Folder

1. Logon to the AP active side as a user with administrator rights and check
that you are logged on to the active side.
C:\>prcstate
2. List the APG43 configuration type for the SSU folder.
C:\>ssuls -l
The printed configuration type must be BSC, MSC or HLR for a One CP System.
Check that it is the correct one, if it is known what it must be. If it is not known,
It must be BSC for a One CP system.
If OK, omit the next step and continue with the next chapter.
3. Change the APG43 configuration type, if it is not the correct one.
9

C:\>ssucfg -c BSC -f
Check the result:
C:\>ssuls

1.7.

Backup of APG43 SW and Transfer to DVD

1. Logon to the AP active side as a user with administrator rights check that you
are logged on to the active side. Check current alarms.
C:\>prcstate
C:\>hostname
C:\>alist
2. Display a list of directories in the root directory of the system disk and check
that
c:\acs\data\BUR\ exists.
C:\>dir /ad c:\acs\data
Note: Create the BUR directory, if the directory does not exist:
C:\>mkdir c:\acs\data\BUR
3. Logout from the current active side.
C:\>exit
4. Logon to the AP passive side as a user with administrator rights and check that
you are
logged on to the passive side. Check current alarms.
C:\>prcstate
C:\>hostname
C:\>alist
5. Display a list of directories in the root directory of the system disk and check
That c:\acs\data\BUR\ exists.
C:\>dir /ad c:\acs\data
Note: Create the BUR directory, if the directory does not exist:

10

C:\>mkdir c:\acs\data\BUR
6. Check that directory images exists in K:\. Replace <clustername> with the
Name of the cluster. Check that the directories NodeA and NodeB exist.
C:\>dir \\<clustername>\images
7. Perform a complete backup of both sides. That is, data disk information is saved,
backup of
partition C:\ to D:\ is performed, and an archive backup is stored on the data
disks. The image
name and archive_filename are automatically generated.
C:\>burbackup -o
Confirm it by entering y
Note 1: The printout ... returned error 5 . . . . Might be received according to TR
HH91244. It is solved in LLV10.
Note 2: The created backup archives will be automatically verified.
Note 3: The procedure will take approximately one hour depending on system
load.
Note 4: The automatically generated image name is:
sidename_YYYYMMDD_HHMMSS.zip
The automatically generated archive_filename is:
K:\\Images\Node(A/B)\sidename_YYYYMMDD_HHMMSS.zip
Note 5: The text .burBackup one button backup execution completed. followed by
a prompt must be received
8. Print the current/last operation:
C:\>emfinfo
9. Is the current/last operation in status PROCESSING?
YES: Wait a while for the copy process to finish. Processing time for 1 GB is
approximately 22
minutes.
NO: If the APG43 contains no DVD board, continue with the next chapter.
Otherwise continue with the next step.
10. Insert an empty DVD into the APG43.
Note 1: The DVD must be an approved version for APG43 DVD Media Compatibility
List.
Note 2: A DVD of type DVD-R has to be chosen. This DVD must be used for the
delivery to the customer.
11. Transfer the backup file for side A on the DVD.

11

C:\>emfcopy -m TODVD \\<clustername>\images\NodeA\<zipfile>


Note 1: Parameter .o must be used, if the DVD is of type RW, so that the DVD is erased
before
data is copied to it.
Note 2: Enter the command from the active side.
Note 3: Lable the DVD with the name of the APG43, the side name, and the date.
12. Print the current/last operation:
C:\>emfinfo
13. Is the current/last operation in status PROCESSING?
YES: Wait a while for the copy process to finish. Processing time for 1 GB is
approximately 22 minutes. Then go to step 12 on page 35.
NO: Continue with the next step
14. Check the contents of the DVD:
C:\>dir G:
15. Insert another empty DVD into the APG43.
Note 1: The DVD must be an approved version for APG43.DVD Media Compatibility
List.
Note 2: A DVD of type DVD-R has to be chosen. This DVD must be used for the
delivery to the customer.
16. Transfer the backup file for side B on the DVD.
C:\>emfcopy .m TODVD \\<clustername>\images\NodeB\<zipfile>
Note 1: Parameter -o must be used, if the DVD is of type RW and if it is not the same
DVD as was used for side A, so that the DVD is erased before data is copied to it.
Note 2: Enter the command from the active side.
Note 3: Lable the DVD with the name of the APG43, the side name, and the date.
17. Print the current/last operation:
C:\>emfinfo
18. Is the current/last operation in status PROCESSING?
YES: Wait a while for the copy process to finish. Processing time for 1 GB is
approximately 22 minutes.
NO: Continue with the next step.
19. Check the contents of the DVD:

12

C:\>dir G:
1.8.
Restore of APG43 SW from DVD
1. Logon to the passive side.
2. Make the passive side owner to the DVD.
C:\>emfget
3. Insert a DVD with the backup for side A into the APG43.
4. Copy the zip backup for side A from the G: partition (DVD) to K:\images.
C:\>copy G:\<imagename for side A>.zip \\<clustername>\images\NodeA
5. Insert a DVD with the backup for side B into the APG43.
6. Copy the zip backup for the side B from the G: partition (DVD) to K:\images.
C:\>copy G:\<imagename for side B>.zip \\<clustername>\images\NodeB
7. Verify the zip backups for both sides.
C:\>burverify -i \\<clustername>\images\NodeA\<imagename for side A>.zip
C:\>burverify -i \\<clustername>\images\NodeB\<imagename for side B>.zip
8. Perform a restore to the D: partition on the passive side.
C:\>burrestore -a \\<clustername>\images\Node(A/B)\<imagename>.zip
9. Logon to the active side and reboot the side.
C:\>prcboot -.f
Wait until the side reboots and then logon to the same side, now passive.
Note: Maximum two reboots in 30 minutes per APG43 side must be executed to
prevent
cyclic AP reboot.
10. Perform a restore to the D: partition on the other side that is now passive.
C:\>burrestore -a \\<clustername>\images\Node(A/B)\<imagename>.zip
11. Restore passive side without rebooting the side.
C:\>burrestore -r <imagename> -s
Note: After a restore of the system it takes up to 10 minutes until the net share
is available. Until the share is available a new backup must not be made. Use
command "net share sysvol" to make sure that the share is available.
12. Shutdown the passive side.
C:\>prcboot -s
13. Logon to the other active side and restore this side.
C:\>burrestore -r <imagename>

13

Note: After a restore of the system it takes up to 10 minutes until the net share is
available. Until the share is available a new backup must not be made. Use command
"net share sysvol" to make sure that the share is available.
14. Verify cluster and side resources are online after restore
C:\>cluster res
Note: It can take some time before the side resources are online.
15. Reset the other side from the active side
C:\>hwmreset -f -n other
Wait for the other side to reboot and then logon to that side. Check that all cluster
resources are online.
C:\>cluster res | findstr -ive online
16. Check that there are two DVD-R versions with backups available for delivery
to the customer. The DVDs must be strapped to the APG43 magazine

1.9.

NSF (Network Surveillance Function) testing

External Network Surveillance Functionality


- Check if functionality flag is active (0=not active, 1=active)
using command
C:\ phaprint acs_nsf_activeflag
- If active disconnect the Ethernet (Public IP) cable in the
active node.
- Wait for Failover to occur and active node is rebooted.
- Check the rebooted node (now passive) is up again and
stable.
- Check all the cluster resources are online.
- Reconnect Ethernet cable and check interfaces are up
running.
- Repeat on the second node (now active)

1.10.

Failover test (prcboot)


-

Reboot active node by entering C:\PRCBOOT


After Failover, check that the external interfaces are up and
running.
Check the rebooted node (now passive) is up again and
stable.
Check all the cluster resources are online.
Repeat on the second node (now active)

14

1.11.

FTP test
-

Using a (S) FTP client, such as that provided by MS-DOS,


open up a session to the active node.
Dir and cd ftpvol if needed
Goto the dedicated FTP directory on the Node, K:\ftpvol\
Upload any test file onto the directory.
Exit session.
Open a new session to the active node.
Check for test file and rename it.
Download file to Local PC.
Exit session.
Check renamed file from Local PC.

15

2. APZ 212 55 Tests


2.1

APZ 212 55 HW configuration

Figure 5 APZ boards

16

Table 1 APZ 212 55 cabling


2.2

Manual Intervention when CP-A is EX

1. Check the alarm list.


<ALLIP;
Printout: ALARM LIST
2. Check that the CP is in status WO. CP-A should be executive.
<DPWSP;
Printout: CP STATE
If CP-A is not EX, switch the sides:
<DPSWI;
Release the terminal by entering <CTRL-D>.
Printout: CP STATE
3. Passivate the automatic output function.
<SYBUE;
4. Make output of a system backup copy to RELFSW2.

17

Note 1: Be sure first that you have an unbroken chain with RELFSW0, RELFSW1
and RELFSW2. RELFSW3 is not defined.
Note 2: SYBUP command separates CP-SB in APZ 212 55 and in APZ 212 60.
<SYBUP: FILE=RELFSW2;
Release the terminal by entering <CTRL-D>.
Printout: BACKUP INFORMATION OUTPUT PROGRESS
Printout: BACKUP INFORMATION OUTPUT
Wait until the output is finished.
5. Initiate procedure for CP repair.
<REPCI;
Release the terminal by entering <CTRL-D>.
Printout: CP DIAGNOSIS
6. Select a suspected board from the list of CP DIAGNOSIS printout. Initiate
manual intervention in the CP with parameters of the selected suspected board.
<REMCI: MAG=mag, PCB=PCB;
Printout: CP MANUAL INTERVENTION
Note 1: Perform actions specified in printout CP MANUAL INTERVENTION
If the CP is faultless (Test RESULT = NO FAULT), use the following parameters:
<REMCI: MAG=CPU, PCB=CPUB-B;
Printout: CP MANUAL INTERVENTION
Note 2: Perform actions specified in printout CP MANUAL INTERVENTION
7. Make sure that CP-A is EX.
<DPWSP;
Printout: CP STATE
8. Initiate a repair check.
<RECCI;
Release the terminal by entering <CTRL-D>.
Printout: CP REPAIR
Note: In APZ 212 55 and APZ 212 60, the system will always have the A side as
EX after successful command execution.
9. Activate the automatic output function.
<SYBUI;
10. Check the alarm list.
<ALLIP;
Printout: ALARM LIST

2.3

Manual Intervention when CP-B is EX

18

1. Switch executive side. CP in WO state. CP-B should be executive.


<DPSWI;
Release the terminal by entering <CTRL-D>.
Printout: CP STATE
2. Initiate procedure for CP repair.
<REPCI;
Release the terminal by entering <CTRL-D>.
Printout: CP DIAGNOSIS
3. Select a suspected board from the list of CP DIAGNOSIS printout. Initiate
manual
intervention in CP with parameters of the selected suspected board.
<REMCI: MAG=mag, PCB=PCB;
Printout: CP MANUAL INTERVENTION
Note 1: Perform actions specified in printout CP MANUAL INTERVENTION
If the CP is faultless (Test RESULT = NO FAULT), use the following parameters:
<REMCI: MAG=CPU, PCB=CPUB-A;
Printout: CP MANUAL INTERVENTION
Note 2: Perform actions specified in printout CP MANUAL INTERVENTION
4. Check whether CP-B is EX.
<DPWSP;
Printout: CP STATE
If CP-B is not EX, switch the sides:
<DPSWI;
Release the terminal by entering <CTRL-D>.
Printout: CP STATE
5. Initiate a repair check.
<RECCI;
Release the terminal by entering <CTRL-D>.
Printout: CP REPAIR
Note: In APZ 212 55 and APZ 212 60, the system will always have the A side as
EX after successful command execution.
6. Check whether CP-A is EX.
<DPWSP;
Printout: CP STATE
If CP-A is not EX, switch the sides:
<DPSWI;
Release the terminal by entering <CTRL-D>.
Printout: CP STATE

19

2.4

Manual Initiated Small Restart

1. Check the alarm list.


<ALLIP;
Printout: ALARM LIST
2. Print the restart escalation window for small restart.
<SYRAP: SMALLMINUTES;
Printout: SMALL SYSTEM RESTART WINDOW
3. Order a small restart. Check that the restart degree is RANK SMALL and that
it is command initiated.
The printout RESTART DATA is directed to the device defined for PRCA=32.
<SYREI: RANK=SMALL, EXPL=OTHER-TEST;
Printout: RESTART DATA
Note: The printout is normally received within 5 minutes.
4. Order another small restart within SMALLMINUTES minutes from the first
one.
Check that the restart degree is SMALL and command initiated.
(No escalation for manual restarts).
The printout RESTART DATA is directed to the device defined for PRCA=32.
<SYREI: RANK=SMALL, EXPL=OTHER-TEST;
Printout: RESTART DATA
Note: The printout is normally received within 5 minutes.
5. Cease the alarm SYSTEM RESTART.
<SYRAE;
6. Wait until the CP state is WO. Check the alarm list. No new UNEXPECTED
alarms should have been added since before the restart. Example of expected
alarms is alarms concerning the restart itself or the command log.
<ALLIP;
Printout: ALARM LIST
7. Check the CP event record. No new UNEXPECTED event should have
occurred in conjunction with the restart. Information about the restart itself will
be added. No fault type should be indicated.
<DIRCP;
Release the terminal by entering <CTRL-D>.
Printout: CP EVENT RECORD
8. Check the RP event record. It contains information about common events, RP
events and EM events. No new UNEXPECTED events should have occurred
in conjunction with the restart. Information about the restart itself will be added
as a common event. No new RP or EM events should have been added.

20

<DIRRP:RP=ALL;
Printout: RP EVENT RECORD

2.5

Manual Initiated Large Restart

1. Check the alarm list.


<ALLIP;
Printout: ALARM LIST
2. Print the restart escalation window for large restart.
<SYRAP: LARGEMINUTES;
Printout: LARGE SYSTEM RESTART WINDOW
3. Order a large restart. Order that the restart degree is LARGE and that it is
command
initiated.
The printout RESTART DATA is directed to the device defined for PRCA=32.
<SYREI: RANK=LARGE, EXPL=OTHER-TEST;
Printout: RESTART DATA
Note: The printout is normally received within 5 minutes.
4. Order another large restart within LARGEMINUTES minutes from the first
one. Check that the restart degree is LARGE and command initiated.
(No escalation for manual restarts).
The printout RESTART DATA is directed to the device defined for PRCA=32.
<SYREI: RANK=LARGE, EXPL=OTHER-TEST;
Printout: RESTART DATA
Note: The printout is normally received within 5 minutes.
5. Cease the alarm SYSTEM RESTART.
<SYRAE;
6. Wait until CP state is WO. Check the alarm list. No new UNEXPECTED
restarts & alarms should have been added since before the restart.
Example of expected alarms is alarms concerning the restart itself or the
command log.
<SYRIP: SURVEY;
Printout: SOFTWARE RECOVERY SURVEY
<ALLIP;
Printout: ALARM LIST
7. Check the CP event record. No new UNEXPECTED events should have
occurred in conjunction with the restart. Information about the restart itself will be
added. No fault type should be indicated.
<DIRCP;

21

Release the terminal by entering <CTRL-D>.


Printout: CP EVENT RECORD
8. Check the RP event record. It contains information about common events, RP
events and EM events. No new UNEXPECTED events should have occurred in
conjunction with the restart. Information about the restart itself will be added as a
common event. No new RP or EM events should have been added.
<DIRRP: RP=ALL;
Command: RP EVENT RECORD

2.6

Activate the Command Log

1. Switch to AP mode.
<APLOC;
Note: The prompt changes from (<) to the Shell prompt.
2. Determine whether the command log file exists.
C:\>cpfls -ls RELCMDHDF
For a Multiple CP system:
C:\>cpls -l
C:\>cpfls -cp <cpname> -ls RELCMDHDF
If it does not exist, create the command log file.
C:\>cpfmkfile -l 512 -c RELCMDHDF RELVOLUMSW
For a Multiple CP system:
C:\>cpfmkfile .cp <cpname> -l 512 -c RELCMDHDF RELVOLUMSW
Note: <cpname> must be written with capital letters.
Return to Central Processor (CP) mode:
C:\>exit
3. Check the alarm list.
<ALLIP;
Printout: ALARM LIST
Check whether the alarm .RELOAD PARAMETERS INVALID. is received. The
alarm .RELOAD PARAMETER INVALID. is received, if the command SYCSI is
entered without the parameter SFN, with the intention to create a new command
log subfile reference for backup, if such a reference did not exist. Fault Code 2 is
then received in the alarm printout.
The command SYCSI with the parameter SFN is only accepted if this alarm
exists. Otherwise it is rejected. The parameter SFN must be used when no
reference to a command log subfile exists for backup.
4. Create a command log subfile. If the alarm RELOAD PARAMETERS
INVALID is not received, the parameter SFN must be omitted:

22

<SYCSI;
If the alarm RELOAD PARAMETERS INVALID is received, the parameter
SFN must be used:
<SYCSI: SFN=0000001;
It might then be necessary to first create the subfile by entering the following
commands:
Switch to AP mode.
<APLOC;
C:\>cpfmkfile RELCMDHDF -0000001.
For a Multiple CP system:
C:\>cpls -l
C:\>cpfmkfile -cp <cpname> RELCMDHDF -0000001.
Return to CP Mode.
C:\>exit
Note: <cpname> must be written with capital letters.
5. Activate the command log.
<SYCLI;
Release the terminal by entering <CTRL-D>.
Wait for the result printout.
Printout: COMMAND LOG ACTIVATION RESULT
The command log is activated.

2.7

Manual Initiated Large Restart with Reload from MS

This chapter is only for AP1, since AP2 does not have APIO.
Manual Initiated Large Restart with Reload from Main Store (MS).
1. Print the system backup files and make sure that RELFSW2 can be
Overwritten.
<SYBFP:FILE;
Release the terminal by entering <CTRL-D>.
<SYBFP:FILE=RELFSW2;
Release the terminal by entering <CTRL-D>.
Printout: SYSTEM BACKUP FILES
2. The command logging function is initiated, if it has not already been initiated.
<SYCLI;
Release the terminal by entering <CTRL-D>.
Printout: COMMAND LOG ACTIVATION RESULT
3. Passivate the automatic output of the system backup.
<SYBUE;
Note: FAULT CODE 23 is received, if it is already passive.

23

4. Make a system backup. Wait for result printout.


<SYBUP:FILE=RELFSW2;
Release the terminal by entering <CTRL-D>.
Printout: BACKUP INFORMATION OUTPUT PROGRESS
Printout: BACKUP INFORMATION OUTPUT
Wait until the printout is finished.
5. Rotate the backup files.
During normal operation (that is, in a live exchange) all the files RELFSW0,
RELFSW1 and RELFSW2 contain valid dump generations. In that case command
SYTUC is used for rotation of backup files.
<SYTUC;
Release the terminal by entering <CTRL-D>.
If SYTUC is successfully executed, proceed with the next step. Otherwise
continue with this step. At start-up it might not be allowed to rotate the files,
because some of the files are defined but empty. In this case a manual rotation can
be done.
Note 1: The following procedure must never be used in a live switch!
Switch to AP local mode.
<APLOC;
Swap files.
C:\>cpfrename relfsw0 dummy
C:\>cpfrename relfsw2 relfsw0
C:\>cpfrename dummy relfsw2
For a Multiple CP system:
C:\>cpls -l
C:\>cpfrename -cp <cpname> relfsw0 dummy
C:\>cpfrename -cp <cpname> relfsw2 relfsw0
C:\>cpfrename -cp <cpname> dummy relfsw2
Note 2: <cpname> must be written with capital letters.
The contents of the files RELFSW0 and RELFSW2 are swapped. RELFSW0
will afterwards contain the latest dump.
Return to CP Mode.
C:\>exit
6. Activate automatic, periodic output towards the backup in the MS. The
predefined reloading file is RELFSW0.
<SYBUI;
The MS is validated by SYBUI, which means that reload is performed from MS.
If not validated, the reload will be performed from file.
7. Check that MS is validated.
<DPWSP;

24

Printout: CP STATE
BUA STATE must have the value 1 if MS is validated.
8. Print system backup copy in MS.
<SYBFP:MS;
Release the terminal by entering <CTRL-D>.
Printout: SYSTEM BACKUP FILES
9. Order a restart with reload. Wait for the reloading to finish. Check that a reload
was performed and that it was command initiated.
The printout RESTART DATA is directed to the device defined for PRCA=32.
<SYREI:RANK=RELOAD,EXPL=OTHER-TEST;
Printout: RESTART DATA
Note: Wait 2.10 minutes for the reloading to finish. The time is dependent of the
size of the exchange.
10. Print time and file usage at the latest system restart with restart rank
RELOAD. Information is then given about the reloading.
<SYBRP;
Printout: SYSTEM RELOADING INFORMATION
Verify that the reload was performed from MS
11. Check that the MS validation is removed after the reload from MS.
<DPWSP;
Printout: CP STATE
BUA STATE must have a different value than 1 if MS is not validated. If so, the
reload will be performed from file the next time it is performed.
12. Cease the alarm SYSTEM RESTART.
<SYRAE;
13. Print the alarm list. No new UNEXPECTED alarms should have been added
since before the restart. Example of expected alarms is alarms concerning the
restart itself or the command log.
<ALLIP;
Printout: ALARM LIST
Check whether the alarm MANUAL EXECUTION OF COMMAND LOG
REQUIRED is received. If the alarm is received, follow the OPI .Command Log
File, Manually
Execute.
14. Check the Error Interrupt Information. No new UNEXPECTED events should
have occurred in conjunction with the restart. Information about the restart itself
will be added. No fault type should be indicated.
<DIRCP;
Release the terminal by entering <CTRL-D>.

25

Printout: CP EVENT RECORD


15. Check the RP event record. It contains information about common events, RP
events and EM events. No new UNEXPECTED events should have occurred in
conjunction with the restart. Information about the restart itself will be added as a
common event. No new RP or EM events should have been added.
<DIRRP:RP=ALL;
Printout: RP EVENT RECORD
2.8

Manual Initiated Large Restart with Reload from File

1. Print the system backup files and make sure that RELFSW2 can be overwritten.
<SYBFP:FILE;
Release the terminal by entering <CTRL-D>.
<SYBFP:FILE=RELFSW2;
Release the terminal by entering <CTRL-D>.
Printout: SYSTEM BACKUP FILES
2. The command logging function is initiated, if it has not already been initiated.
<SYCLI;
Release the terminal by entering <CTRL-D>.
Printout: COMMAND LOG ACTIVATION RESULT
3. Passivate the automatic output of the system backup.
<SYBUE;
Note: FAULT CODE 23 is received, if it is already passive
4. Make a system backup. Wait for the result printout.
<SYBUP: FILE=RELFSW2;
Release the terminal by entering <CTRL-D>.
Printout: BACKUP INFORMATION OUTPUT PROGRESS
Printout: BACKUP INFORMATION OUTPUT
Wait until the printout is finished.
5. Rotate the backup files.
<SYTUC;
Release the terminal by entering <CTRL-D>.
If SYTUC is successfully executed, proceed with the next step. Otherwise
Continue with this step.
Rotate the reload files manually.
Note 1: This procedure must never be used in a live switch!
Switch to AP local mode.
<APLOC;
Rotate files.
C:\>cpfrename relfsw0 dummy
C:\>cpfrename relfsw2 relfsw0
C:\>cpfrename relfsw1 relfsw2

26

C:\>cpfrename dummy relfsw1


For a Multiple CP system:
C:\>cpls -l
C:\>cpfrename -cp <cpname> relfsw0 dummy
C:\>cpfrename -cp <cpname> relfsw2 relfsw0
C:\>cpfrename -cp <cpname> relfsw1 relfsw2
C:\>cpfrename -cp <cpname> dummy relfsw1
Note 2: <cpname> must be written with capital letters
Return to CP Mode.
C:\>exit
6. Order a restart with reload. Wait for the reloading to finish. Check that a reload
was performed and that it was command initiated.
The printout RESTART DATA is directed to the device defined for PRCA=32.
<SYREI: RANK=RELOAD, EXPL=OTHER-TEST;
Printout: RESTART DATA
Note: Wait 2.10 minutes for the reloading to finish. The time is dependent of the
size of the exchange.
7. Print time and file usage at the latest system restart with restart rank RELOAD.
Information is then given about the reloading.
<SYBRP;
Printout: SYSTEM RELOADING INFORMATION
Verify that the reload was performed from the file RELFSW0.
8. Cease the alarm SYSTEM RESTART.
<SYRAE;
9. Print the alarm list. No new UNEXPECTED alarms should have been added
since before the restart. Example of expected alarms is alarms concerning the
restart itself or the command log.
<ALLIP;
Printout: ALARM LIST
Check whether the alarm MANUAL EXECUTION OF COMMAND LOG
REQUIRED is received.
If the alarm is received, follow the OPI .Command Log File, Manually Execute.
10. Check the Error interrupt Information. No new UNEXPECTED events should
have occurred in conjunction with the restart. Information about the restart itself
will be added. No fault type should be indicated.
<DIRCP;
Release the terminal by entering <CTRL-D>.
Printout: CP EVENT RECORD

27

11. Check the RP event record. It contains information about common events, RP
events and EM events. No new UNEXPECTED events should have occurred in
conjunction with the restart. Information about the restart itself will be added as a
common event. No new RP or EM events should have been added.
<DIRRP:RP=ALL;
Printout: RP EVENT RECORD

2.9

FEX Load on CP-A

1. Disconnect the CP-A board and the CP-B board from the eGEM.
Note 1: The boards can be disconnected in any order.
Note 2: The boards should only be pulled out a few centimetres, not completely
removed from the magazine.
Note 3: A torx wrench is needed to disconnect the boards.
2. Disconnect the power to MAUB and wait 10 seconds.
Note: Use the unconditional power switch on the MAUB. If it does not have any
power switch, pull out the MAU board.
3. Reconnect the CP-A board into the eGEM. Wait 2-15 minutes for the reload to
finish. The following exchange header is an example of a printout that can be
received, if the logon attempt is successful. FEX must be received as CP state.
FEX 55REF_LSV18_C00_0925 AD-4 TIME 980101 0000 PAGE 1
<
Note 1: Nothing is received on the CDU display when the reload is finished, due
to the fact that the display is connected to the MAUB.
Note 2: The alarm CP FAULT is received due to missing MAUB.
4. Set the program clock.
<CACLS: TIME=hhmm, DATE=yymmdd;
5. Order a small restart to set the time in all APT blocks, job buffers and time
queues. (Printout terminal defined for PRCA=32).
<SYREI: RANK=SMALL, EXPL=OTHER-TEST;
Printout: RESTART DATA
<SYRIP: SURVEY;
Printout: RESTART INFORMATION
Note: The alarm CP FAULT reappears due to the system restart.
6. Reconnect the power to MAUB.
Note: Use the unconditional power switch on the MAUB. If it does not have any
power switch, push in the MAU board.
7. Cease the alarm SYSTEM RESTART.
<SYRAE;

28

8. Check the CP.


<RECCI;
Release the terminal by entering <CTRL-D>.
Printout: CP REPAIR
Note: The alarm CP FAULT will not cease even though RECCI is successfully
completed.
9. Reconnect the CP-B board into the eGEM.
Wait 5 minutes until CP display arrives to 390 phase.
10. Make a parallel start of standby CP-side, CP-B.
<RECCI;
Release the terminal by entering <CTRL-D>.
Printout: CP REPAIR
Note 1: In APZ 212 55 and APZ 212 60, the system will always have the A side
as EX after successful command execution.
Note 2: The alarm CP FAULT will cease.
11. Wait for CP to return to parallel operation.
<DPWSP;
Printout: CP STATE

2.10

FEX Load on CP-B

1. Disconnect the CP-A board and the CP-B board from the eGEM.
Note 1: The boards can be disconnected in any order.
Note 2: The boards should only be pulled out a few centimeters, not completely
removed from the magazine.
Note 3: A torx wrench is needed to disconnect the boards.
2. Disconnect the power to MAUB and wait 10 seconds.
Note: Use the unconditional power switch on the MAUB. If it does not
have any power switch, pull out the MAU board.
3. Reconnect the CP-B board into the eGEM.
Wait 2-15 minutes for the reload to finish.
The following exchange header is an example of a printout that can be received, if
the logon attempt is successful. .FEX. must be received as CP state.
FEX 55REF_LSV18_C00_0925 AD-4 TIME 980101 0000 PAGE 1
<
Note 1: Nothing is received on the CDU display when the reload is finished, due
to the fact that the display is connected to the MAUB.
Note 2: The alarm CP FAULT is received due to missing MAUB.

29

4. Set the program clock.


<CACLS: TIME=hhmm, DATE=yymmdd;
5. Order a small restart to set the time in all APT blocks, job buffers and time
Queues. (Printout terminal defined for PRCA=32).
<SYREI: RANK=SMALL, EXPL=OTHER-TEST;
Printout: RESTART DATA
<SYRIP: SURVEY;
Printout: RESTART INFORMATION
Note: The alarm CP FAULT reappears due to the system restart.
6. Reconnect the power to MAUB.
Note: Use the unconditional power switch on the MAUB. If it does not have any
power switch, push in the MAU board.
7. Cease the alarm SYSTEM RESTART.
<SYRAE;
8. Check the CP.
<RECCI;
Release the terminal by entering <CTRL-D>.
Printout: CP REPAIR
Note: The alarm CP FAULT will not cease even though RECCI is successfully
completed.
9. Reconnect the CP-A board into the eGEM.
Wait 5 minutes until CP display arrives to 390 phase.
10. Make a parallel start of standby CP-side, CP-A.
<RECCI;
Release the terminal by entering <CTRL-D>.
Printout: CP REPAIR
Note 1: In APZ 212 55 and APZ 212 60, the system will always have the
A side as EX after successful command execution.
Note 2: The alarm CP FAULT will cease.
11. Wait for CP to return to parallel operation.
<DPWSP;
Printout: CP STATE
12. Initiate command logging.
<SYCLI;
Release the terminal by entering <CTRL-D>.
Printout: COMMAND LOG ACTIVATION RESULT

30

2.11

Function Change Method II

1. If the automatic size alterations function is active, make it passive.


<SAOCP;
<SAOCS: STATE=PASSIVE;
2. Separate CP-SB.
<FCSEI;
Small restart of the APZ blocks is performed in SB side
3. Deactivate the automatic dumping of DS variables.
<SYBUE;
Note: FAULT CODE 23 is received, if it is already passive.
4. Set the FC mode.
<FCMOS: MODE=UMBNOTRSWI;
5. Order data transfer from CP-EX to CP-SB.
Deactivate the automatic dumping of DS variables
Wait for the printout.
<FCDAT;
Printout: DATA TRANSFER RESULT
6. Switch to AP mode.
<APLOC;
Note 1: The prompt changes from (<) to the Shell prompt.
Connect to CP-SB.
C:\>mml -as
For a Multiple CP system:
C:\>cpls .l
C:\>mml -cp <cpname> -as
Note 2: <cpname> must be written with capital letters.
Note 3: The prompt changes from the Shell prompt to (<).
7. Start the application blocks in CP-SB.
<SYATI: RESTART;
Printout: RESTART DATA
8. Connect to CP-EX.
End CP-SB terminal session.
<EXIT;
Note 1: The prompt changes from (<) to the Shell prompt.
Return to CP mode.
C:\>exit
Note 2: The prompt changes from the Shell mode to (<).

31

9. Switch the CP sides.


<FCSWI;
10. Perform a manual backup copy.
<SYBUP:FILE;
Release the terminal by entering <CTRL-D>.
Printout: OUTPUT TO FILE RELFSW2:
Accept the proposed file and give order for execution with semicolon (;).
ORDERED
Release the terminal by entering <CTRL-D>.
Printout: BACKUP INFORMATION OUTPUT PROGRESS
Printout: BACKUP INFORMATION OUTPUT
Wait until the printout is finished.
11. Rotate the reload files.
<SYTUC;
Release the terminal by entering <CTRL-D>.
12. Make parallel start of CP-SB side.
<DPPAI;
Release the terminal by entering <CTRL-D>.
Printout: CP SB START PASSED
Note: In APZ 212 55 and APZ 212 60, the system will always have the A side as
EX after successful command execution.
13. Activate the automatic dumping.
<SYBUI;
14. If the automatic size alteration function was set to passive in step 1, then
activate it.
<SAOCS:STATE=ACTIVE;

2.12

Initial Loading of CP-A


Initial loading is performed to CP-side A. Then RECCI is used
to order CP in normal state.

1. Open mml session to CP-SB.


C:\>mml -as

2. Connect CPT.

32

<PTCOI;

3. Ensure that the PHCI function is active. The PHCI indicator is


on, when the PHCI function is active.
Check CP status:
cpt<PTWSP;

4. If CP-A is not CP-SB, use the following command.


cpt<PTSWI;

5. Separate the CP.


cpt<PTSES;

6. Stop program execution.


cpt<PTPEE;

7. Disconnect CPT :
cpt<PTCOE;

8. Close mml session to CP-SB .


<EXIT;
Check if file RELFSW99 exists:
C:\>cpfls
Printout: CPF FILE TABLE
For details of selected RELFSW99 file:
C:\>cpfls -ls RELFSW99

33

Printout: CPF FILE TABLE


Open mml session to CP-SB .
C:\>mml -as

9. Connect CPT.
<PTCOI;

10. Order an initial load.


cpt<PTCPL:CS=A,FILE=RELFSW99;

11. Release the IO terminal and wait for the initial load to finish.
Enter <CTRL-D> on the IO terminal used for CPT.

12. Check the printouts from CPT (this repeats for a few minutes).
The following printouts may be received.
Printout: CPT MESSAGE INITIAL LOADING (ABSOLUTE)
STARTED
Printout: CPT MESSAGE INITIAL LOADING (ABSOLUTE) IN
PROGRESS

13. If loading is successful, this printout may appear:


Printout: CPT MESSAGE INITIAL LOADING (ABSOLUTE)
FINISHED

14. If loading is not successful, check the meaning of the fault


code in POD.
Printout: CPT MESSAGE INITIAL LOADING (ABSOLUTE)
STOPPED

34

Printout: CPT MESSAGE INITIAL LOADING (ABSOLUTE)


STARTED
Printout: CPT MESSAGE *** INITIAL IN PROGRESS
LOADING ABNORMAL
Solve the fault, and start again from step Error: Reference
source not found on page Error: Reference source not found.

15. Disconnect CPT:


cpt<PTCOE;

16. Close mml session.


<EXIT;

17. Open mml session to CP-SB.


C:\>mml -as

18. Wait for printout result (RANK SYSTEM START) after loading
in CP-SB side, or the exchange header.
Printout: SYSTEM STARTED

(if received)

19. Start the application blocks in CP-SB.


<SYATI:RESTART;
Printout: SYSTEM RESTARTED

20. Set Error Printout Format to large format in CP-SB.


<DIEFC:FORM=2;

21. Close mml session to CP-SB.

35

<EXIT;

22. Open mml session to CP-EX.


C:\>mml -a

23. Connect CPT.


<PTCOI;

24. Switch EX-side.


cpt<PTSWI;

25. Disconnect CPT.


cpt<PTCOE;

26. Wait for a large restart in CP-EX, side A. Then the restart is
received as a result of the Side Switch.
Printout: SYSTEM RESTARTED

27. Set the program clock in CP-EX.


<CACLS:DATE=yymmdd,TIME=hhmm;

28. Passivity the PHCI function by pressing the PHCI button on


the MAU board.
The PHCI indicator is off when the PHCI function is passive.

36

29. Prepare output of a system backup copy to RELFSW2 ( i.e. to


the highest defined reload file in an unbroken sequence of
files) :
<SYBUP:FILE;
Printout: OUTPUT TO FILE RELFSW2
Accept the proposed file and give order for execution with
semicolon (;).
ORDERED
Release the terminal by entering <CTRL-D>.
Printout: BACKUP INFORMATION OUTPUT PROGRESS
Printout: BACKUP INFORMATION OUTPUT
Wait until finished.

30. Make parallel start of CP-SB side. Wait for result:


<RECCI;
Printout: CP REPAIR

31. Check that CP-A is EX and CP-B is SB.


<DPWSP;
Printout: CP STATE

32. Close mml session.


<EXIT;

2.13

Initial Loading of CP-B

37

This section is intended to ensure that initial loading has been


tested on
CP-B.

1. Open mml session to CP-SB, side B.


C:\>mml -as

2. Connect CPT.
<PTCOI;

3. Activate the PHCI function. The PHCI indicator is on, when the
PHCI function is active.
Check CP status:
cpt<PTWSP;
Printout: CP STATE
The states should be CP-A EX and CP-B SBWO.

4. Separate the CP.


cpt<PTSES;

5. Stop program execution.


cpt<PTPEE;

6. Disconnect CPT.
cpt<PTCOE;

7. Close mml session to CP-SB .

38

<EXIT;
Check if file RELFSW99 exists:
C:\>cpfls
Printout: CPF FILE TABLE
For details of selected RELFSW99 file:
C:\>cpfls -ls RELFSW99
Printout: CPF FILE TABLE
Open mml session to CP-SB .
C:\>mml -as

8. Connect CPT.
<PTCOI;

9. Order an initial load.


cpt<PTCPL:CS=B,FILE=RELFSW99;

10. Release the IO terminal and wait for the initial load to finish.
Enter <CTRL-D> on the IO terminal used for CPT.

11. Check the printouts from CPT (this repeats for a few minutes).
The following printouts may be received.
Printout: CPT MESSAGE INITIAL LOADING (ABSOLUTE)
STARTED
Printout: CPT MESSAGE INITIAL LOADING (ABSOLUTE) IN
PROGRESS

39

12. If loading is not successful, check the meaning of the fault


code in POD.
Printout: CPT MESSAGE INITIAL LOADING (ABSOLUTE)
STOPPED
Printout: CPT MESSAGE INITIAL LOADING
(RELOCATABLE) STARTED
Printout: CPT MESSAGE *** INITIAL LOADING PROGRESS
ABNORMAL
Fix the fault, and start again from Step Error: Reference
source not found on page Error: Reference source not found.

13. If loading is successful, this printout may appear:


Printout: CPT MESSAGE INITIAL LOADING (ABSOLUTE)
FINISHED

14. Disconnect CPT.


cpt<PTCOE;

15. Close mml session.


<EXIT;

16. Open mml session to CP-SB.


C:\>mml -as

17. Wait for printout result (RANK SYSTEM START) after loading
in CP-SB side, or the exchange header.
Printout: SYSTEM STARTED

(if received)

40

18. Start the application blocks in CP-SB.


<SYATI:RESTART;
Printout: SYSTEM RESTARTED

19. Set Error Printout Format to large format in CP-SB.


<DIEFC:FORM=2;

33. Close mml session to CP-SB.


<EXIT;

34. Open mml session to CP-EX.


C:\>mml -a

35. Connect CPT.


<PTCOI;

36. Switch EX-side.


cpt<PTSWI;

37. Disconnect CPT.


cpt<PTCOE;

38. Wait for a large restart in CP-EX.


Printout: SYSTEM RESTARTED

41

39. Set the program clock in CP-EX.


<CACLS:DATE=yymmdd,TIME=hhmm;

40. Passivity the PHCI function on the MAU:


Press the PHCI button on the MAU. The PHCI indicator is off
when the PHCI function is passive.

41. Prepare output of a system backup copy to RELFSWn ( n,


highest defined reload file in an unbroken sequence of files) :
<SYBUP:FILE;
OUTPUT TO FILE RELFSWX: ;
ORDERED
Printout: OUTPUT TO FILE

42. Start parallel operation. Check that CP-SB can be updated.


Wait for result.
<RECCI;
Printout: CP REPAIR

43. Close mml session.


<EXIT;

42

3 APT Tests:
3.1

Check of RPs and EMs

This is an initial check of strapping, cabling and making sure that RPs and EMs are
working.
--------------------------------------------------------------------------------------------1. Make sure that the GEM/CDM magazines are strapped and cabled correctly
--------------------------------------------------------------------------------------------2. Check that RPs are Working (WO).
Command: EXRPP:RP=rp;
Printout: RP DATA
--------------------------------------------------------------------------------------------3. Check that EMs are Working (WO).
Command: EXEMP:EM=ALL,RP=rp;
Printout: EM DATA
---------------------------------------------------------------------------------------------

3.2
Note:

Test of CLM

If Network Synchronization data is defined, but none of the sources are


working, then the test of CLMs will fail. In this case, undefine the NS data.
Before test 8, the power must have been "on" for a minimum of 15 minutes.
RCM shall be blocked during the test, except for diagnostic test due to error
conditions encountered in test 8.

--------------------------------------------------------------------------------------------1.

Check that the CLMs are defined and the state of the CLMs.

43

Command: GDSTP:UNIT=unit;
Printout: DISTRIBUTED GROUP SWITCH STATE
--------------------------------------------------------------------------------------------2.

Deblock CLM-0 and make sure that CLM-0 is WO and the other CLMs are MBL.
Command: GDBLE:UNIT=CLM-0;
Printout: DISTRIBUTED GROUP SWITCH UNIT DEBLOCKING RESULT

--------------------------------------------------------------------------------------------3.

Initiate the test for CLM-1.


Command: GDTEI:UNIT=CLM-1;
Printout: DISTRIBUTED GROUP SWITCH UNIT TEST RESULT

--------------------------------------------------------------------------------------------4.

Deblock CLM-1.
Command: GDBLE:UNIT=CLM-1;
Printout: DISTRIBUTED GROUP SWITCH UNIT DEBLOCKING RESULT

--------------------------------------------------------------------------------------------5.

Wait until CLM-1 is WO, then block CLM-0. Confirm the blocking order.
Command: GDBLI:UNIT=CLM-0;
Printout: DISTRIBUTED GROUP SWITCH UNIT DEBLOCKING RESULT
The system responds:
WARNING ACCEPTANCE MEANS CONSIDERABLE RISK FOR THE WHOLE
EXCHANGE
ANSWER WITH YES IF YOU WANT TO CONTINUE
:YES;

--------------------------------------------------------------------------------------------6.

Initiate the test for CLM-0 and wait for result printout.

44

Command: GDTEI:UNIT=CLM-0;
Printout: DISTRIBUTED GROUP SWITCH UNIT TEST RESULT
--------------------------------------------------------------------------------------------7.

Deblock CLM-0.
Command: GDBLE:UNIT=CLM-0;
Printout: DISTRIBUTED GROUP SWITCH UNIT DEBLOCKING RESULT

--------------------------------------------------------------------------------------------8.

Check CONTRVALUE. Should be 32768 +-7000 (for all oscillators). If not,


follow the procedure:
1. Try to activate NS (i.e. deblock RCM or any other external reference).
2. If the activation is successful, wait 10 hours and repeat test 8.
3. If the activation is not successful then: If the value out of range belons to
oscillator 1 (son), replace the faulty board. If the value out of range belongs to
oscillator 0 (father), replace both CGB boards (it is not possible to discriminate
which board is faulty).
DO NOT ADJUST CONTROL VALUE
Command: GDCVP;
Printout: DISTRIBUTED GROUP SWITCH CLM CONTROL VALUE

---------------------------------------------------------------------------------------------

3.3

Test of XM

RPs and EMs for XMs should be deblocked and working.


--------------------------------------------------------------------------------------------1. Test plane A in the XM
Command: GDTEI:UNIT=XM-A-0-0;
Printout: DISTRIBUTED GROUP SWITCH UNIT TEST RESULT
--------------------------------------------------------------------------------------------2. Deblock the XM.

45

Command: GDBLE:UNIT=XM-A-0-0;
Printout: DISTRIBUTED GROUP SWITCH UNIT DEBLOCKING RESULT
---------------------------------------------------------------------------------------------3. Repeat point 1 and 2 for all XMs, both A- and B-plane.
--------------------------------------------------------------------------------------------4. Check the working state of the group switch. All XMs should be working.
Command: GDSTP;
Printout: DISTRIBUTED GROUP SWITCH STATE
---------------------------------------------------------------------------------------------

3.4

Test of MUX3

MUX3 have no EM control, so there is no need to check EMs.


--------------------------------------------------------------------------------------------1. Test plane A in the MUX3
Command: GDTEI:UNIT=MUX3-A-0;
Printout: DISTRIBUTED GROUP SWITCH UNIT TEST RESULT
--------------------------------------------------------------------------------------------2. Deblock the MUX3.
Command: GDBLE:UNIT=MUX3-A-0;
Printout: DISTRIBUTED GROUP SWITCH UNIT DEBLOCKING RESULT
--------------------------------------------------------------------------------------------3. Repeat step 1 and 2 for all MUX3s, both A- and B-plane.
--------------------------------------------------------------------------------------------4. Check the working state of the group switch. All MUX3s should be working.
Command: GDSTP;
Printout: DISTRIBUTED GROUP SWITCH STATE

46

---------------------------------------------------------------------------------------------

3.5

Final Test of XM

This is the final test of XMs.


Note:
All units within the distributed group switch should be working before the final
test of XMs is started.

--------------------------------------------------------------------------------------------1. Block XM in plane A.


Command: GDBLI:UNIT=XM-A-0-0;
Printout: DISTRIBUTED GROUP SWITCH UNIT BLOCKING RESULT
--------------------------------------------------------------------------------------------2. Test XM in plane A.
Command: GDTEI:UNIT=XM-A-0-0;
Printout: DISTRIBUTED GROUP SWITCH UNIT TEST RESULT
--------------------------------------------------------------------------------------------3. Deblock the XM.
Command: GDBLE:UNIT=XM-A-0-0;
Printout: DISTRIBUTED GROUP SWITCH UNIT DEBLOCKING RESULT
--------------------------------------------------------------------------------------------4. Repeat point 1 and 2 for all XMs, both A- and B-plane.
--------------------------------------------------------------------------------------------5. Check the working state of the group switch. All XMs should be working.
Command: GDSTP;
Printout: DISTRIBUTED GROUP SWITCH STATE
---------------------------------------------------------------------------------------------

47

3.6

Test of RCM

External Network Synchronization should be blocked during this test. These are
tested later during the integration test of the exchange.
In this test the RCM connection to the CLMs and the RCM data are checked and the
RCM is deblocked. Automatic tests verify that the reference clock operates within
defined limits and puts the unit out of service if not.
Note:
RCM is an optional feature and might not exist in all switches.

--------------------------------------------------------------------------------------------1. Load all Network Synchronization commands from DT.


--------------------------------------------------------------------------------------------2. Check if the RCM is defined and manually blocked (otherwise block it).
Command: NSSTP;
Printout: CLOCK REFERENCE STATE
Command: NSBLI:RCM=RCM-x;
--------------------------------------------------------------------------------------------3. Print the network synchronization data.
Command: NSDAP;
Printout: CLOCK REFERENCE SUPERVISION DATA
--------------------------------------------------------------------------------------------4. Initiate test of RCM. During test the frequency deviation and wander of the
reference clock is controlled against values printed above.
Command: NSTEI:RCM=RCM-x;
Printout: CLOCK REFERENCE TEST RESULT
--------------------------------------------------------------------------------------------5. Deblock the RCM if the test was successful. External clock references should
be left manually blocked.

48

Command: NSBLE:RCM=RCM-x;
Printout: NETWORK SYNCHRONIZATION MANUAL DEBLOCKING OF CLOCKREFERENCE EXECUTED
---------------------------------------------------------------------------------------------

3.7

Test of ET

Exchange terminal should be checked during this test.


Note:

MSP 1+1 protection also is checked during this test. MSP 1+1 protection is
optional and can be omitted during configuration.

--------------------------------------------------------------------------------------------1. Perform loopback test of ET terminal on ODF.


--------------------------------------------------------------------------------------------2. Check if the status of SDIP using command TSTP. Make sure that state for
SDIP is working. In the case of MSP 1+1 both MS should be in working state.
Command: TPSTP:SDIP=<SDIP name>;
Printout: SYNCHRONOUS DIGITAL PATH STATE
--------------------------------------------------------------------------------------------3. In the case of MSP 1+1 protection disconnect cable on ODF from one port of
protected pair. Make sure that state for SDIP is working.
Command: TPSTP:SDIP=<SDIP name>;
Printout: SYNCHRONOUS DIGITAL PATH STATE
--------------------------------------------------------------------------------------------4. In the case of MSP 1+1 protection disconnect cable on ODF from other port of
protected pair. Make sure that state for SDIP is working.
Command: TPSTP:SDIP=<SDIP name>;
Printout: SYNCHRONOUS DIGITAL PATH STATE
--------------------------------------------------------------------------------------------5. Repeat above steps for all exchange terminals in the node.

49

50