Professional Documents
Culture Documents
1
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
2
1. APG43 Tests
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.
3
Figure 2 – APG43 connectivity
4
Figure 4 –APG43 external connectivity
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.
C:\>prcstate
Printout: active
2. Print the ‘Cluster_name’ and the ‘Host_name’ from the active side:
C:\>cluster /ver
5
C:\>hostname
C:\>cluster group
Printout: Status is listed for all available resource groups.
C:\>cluster res
Printout: Listing status for all available resources
C:\>swrprint
Printout: AP SOFTWARE CHARACTERISTICS
C:\>date
Printout: The current date is: day mm/dd/yyyy
Enter the new date: (mm-dd-yy)
Note: Enter RETURN or new date.
C:\>time
Printout: The current time is: hh:mm:ss
Enter the new time:
Note: Enter RETURN or new time.
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").
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
<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
CPT<PTCOE;
7
5. Test of CPS.
List all defined system backup files:
<SYBFP:FILE;
This chapter can be omitted when the APG43 is delivered standalone, or if the fan
has been tested earlier.
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.
8
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.
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. 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
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.
9
C:\>ssucfg -c BSC -f
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.
Note: Create the BUR directory, if the directory does not exist:
C:\>mkdir c:\acs\data\BUR
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.
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
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.
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
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.
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.
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.
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.
12
C:\>dir G:
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
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
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.
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
14
1.11. FTP test
15
2. APZ 212 55 Tests
16
Table 1 – APZ 212 55 cabling
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.
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
19
2.4 Manual Initiated Small Restart
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.
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
20
<DIRRP:RP=ALL;
Printout: RP EVENT RECORD
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.
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
21
Release the terminal by entering <CTRL-D>.
Printout: CP EVENT RECORD
1. Switch to AP mode.
<APLOC;
Note: The prompt changes from (<) to the Shell prompt.
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.
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
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.
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.
24
Printout: CP STATE
BUA STATE must have the value 1 if MS is validated.
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.
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
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
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
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.
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
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.
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.
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.
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.
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.
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.
30
2.11 Function Change Method II
2. Separate CP-SB.
<FCSEI;
Small restart of the APZ blocks is performed in SB side
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 (<).
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;
14. If the automatic size alteration function was set to passive in step 1, then
activate it.
<SAOCS:STATE=ACTIVE;
C:\>mml -as
2. Connect CPT.
32
<PTCOI;
Check CP status:
cpt<PTWSP;
cpt<PTSWI;
cpt<PTSES;
cpt<PTPEE;
7. Disconnect CPT :
cpt<PTCOE;
<EXIT;
C:\>cpfls
33
Printout: CPF FILE TABLE
C:\>mml -as
9. Connect CPT.
<PTCOI;
cpt<PTCPL:CS=A,FILE=RELFSW99;
11. Release the IO terminal and wait for the initial load to finish.
12. Check the printouts from CPT (this repeats for a few minutes).
34
Printout: CPT MESSAGE INITIAL LOADING (ABSOLUTE)
STARTED
Solve the fault, and start again from step Error: Reference
source not found on page Error: Reference source not found.
cpt<PTCOE;
<EXIT;
C:\>mml -as
18. Wait for printout result (RANK SYSTEM START) after loading
in CP-SB side, or the exchange header.
<SYATI:RESTART;
<DIEFC:FORM=2;
35
<EXIT;
C:\>mml -a
<PTCOI;
cpt<PTSWI;
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.
<CACLS:DATE=yymmdd,TIME=hhmm;
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;
Accept the proposed file and give order for execution with
semicolon (;).
ORDERED
<RECCI;
Printout: CP REPAIR
<DPWSP;
Printout: CP STATE
<EXIT;
37
This section is intended to ensure that initial loading has been
tested on
CP-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
cpt<PTSES;
cpt<PTPEE;
6. Disconnect CPT.
cpt<PTCOE;
38
<EXIT;
C:\>cpfls
C:\>mml -as
8. Connect CPT.
<PTCOI;
cpt<PTCPL:CS=B,FILE=RELFSW99;
10. Release the IO terminal and wait for the initial load to finish.
11. Check the printouts from CPT (this repeats for a few minutes).
39
12. If loading is not successful, check the meaning of the fault
code in POD.
Fix the fault, and start again from Step Error: Reference
source not found on page Error: Reference source not found.
cpt<PTCOE;
<EXIT;
C:\>mml -as
17. Wait for printout result (RANK SYSTEM START) after loading
in CP-SB side, or the exchange header.
40
18. Start the application blocks in CP-SB.
<SYATI:RESTART;
<DIEFC:FORM=2;
<EXIT;
C:\>mml -a
<PTCOI;
cpt<PTSWI;
cpt<PTCOE;
41
39. Set the program clock in CP-EX.
<CACLS:DATE=yymmdd,TIME=hhmm;
Press the PHCI button on the MAU. The PHCI indicator is off
when the PHCI function is passive.
<SYBUP:FILE;
ORDERED
<RECCI;
Printout: CP REPAIR
<EXIT;
42
3 APT Tests:
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
---------------------------------------------------------------------------------------------
Command: EXRPP:RP=rp;
Printout: RP DATA
---------------------------------------------------------------------------------------------
Command: EXEMP:EM=ALL,RP=rp;
Printout: EM DATA
---------------------------------------------------------------------------------------------
Note:
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;
---------------------------------------------------------------------------------------------
2. Deblock CLM-0 and make sure that CLM-0 is WO and the other CLMs are MBL.
Command: GDBLE:UNIT=CLM-0;
---------------------------------------------------------------------------------------------
Command: GDTEI:UNIT=CLM-1;
---------------------------------------------------------------------------------------------
4. Deblock CLM-1.
Command: GDBLE:UNIT=CLM-1;
---------------------------------------------------------------------------------------------
5. Wait until CLM-1 is WO, then block CLM-0. Confirm the blocking order.
Command: GDBLI:UNIT=CLM-0;
:YES;
---------------------------------------------------------------------------------------------
6. Initiate the test for CLM-0 and wait for result printout.
44
Command: GDTEI:UNIT=CLM-0;
---------------------------------------------------------------------------------------------
7. Deblock CLM-0.
Command: GDBLE:UNIT=CLM-0;
---------------------------------------------------------------------------------------------
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).
Command: GDCVP;
---------------------------------------------------------------------------------------------
3.3 Test of XM
---------------------------------------------------------------------------------------------
Command: GDTEI:UNIT=XM-A-0-0;
---------------------------------------------------------------------------------------------
45
Command: GDBLE:UNIT=XM-A-0-0;
----------------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------------
4. Check the working state of the group switch. All XMs should be working.
Command: GDSTP;
---------------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------------
Command: GDTEI:UNIT=MUX3-A-0;
---------------------------------------------------------------------------------------------
Command: GDBLE:UNIT=MUX3-A-0;
---------------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------------
4. Check the working state of the group switch. All MUX3s should be working.
Command: GDSTP;
46
---------------------------------------------------------------------------------------------
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;
---------------------------------------------------------------------------------------------
2. Test XM in plane A.
Command: GDTEI:UNIT=XM-A-0-0;
---------------------------------------------------------------------------------------------
Command: GDBLE:UNIT=XM-A-0-0;
---------------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------------
5. Check the working state of the group switch. All XMs should be working.
Command: GDSTP;
---------------------------------------------------------------------------------------------
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.
---------------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------------
2. Check if the RCM is defined and manually blocked (otherwise block it).
Command: NSSTP;
Command: NSBLI:RCM=RCM-x;
---------------------------------------------------------------------------------------------
Command: NSDAP;
---------------------------------------------------------------------------------------------
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;
---------------------------------------------------------------------------------------------
5. Deblock the RCM if the test was successful. External clock references should
be left manually blocked.
48
Command: NSBLE:RCM=RCM-x;
---------------------------------------------------------------------------------------------
3.7 Test of ET
Note:
MSP 1+1 protection also is checked during this test. MSP 1+1 protection is
optional and can be omitted during configuration.
---------------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------------
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.
---------------------------------------------------------------------------------------------
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.
---------------------------------------------------------------------------------------------
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.
---------------------------------------------------------------------------------------------
49
50