BSCHW Acceptance Test Procedures 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 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 3 Figure 2 – APG43 connectivity Figure 3 – BSC APG43 configuration 4 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 5 C:\>hostname 3. Check the time: C:\>time Printout: The current time is: hh:mm:ss Enter the new time: Note: Enter RETURN or new time. Test APIO SW and STS SW are installed and activated 1. 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. 9. 1.3. 4. Some alarms might not be cleared here due to the missing CP connection (for example "AP SYSTEM CLOCK NOT SYNCHRONIZED"). Check that all cluster groups are online: C:\>cluster group Printout: Status is listed for all available resource groups. List all alarms on APG: C:\>alist Note: Clear all alarms by using the appropriate OPI. 8. 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. Open a command prompt: Start -> All Programs -> Accessories -> Command Prompt 6 . Check that the right time zone is set: C:\>mtzln -p 7. Test of FMS.C:\>dsdls -a The printout must contain: node cp0 node ap1a or ap1b Connect to the CP through the AD-ports. C:\>mml APAMP. 3. Test of MCS. Printout: CP STATUS End the session: CPT<PTCOE. C:\>cpdtest -c Printout: STATE must have the value CONNECTED Start an MML session (with spontaneous printouts). Printout: AP MAINTENANCE DATA 2. C:\>mml –a <PTCOI. C:\>cpfls -ls Printout: CP FILE TABLE 4. Printout: IO MML SERVICE DATA <IOCDP. Verify that the CP AP connection is enabled. 7 . Use the SW Winfiol. C:\>mml –a <IOMSP. CPT<PTWSP. Printout: IO CONFIGURATION DATA Leave the MML session: <EXIT. Test of MAS. Loosen one of the fan units and pull it out.5. 7. C:\>bupls If any value is faulty. The prompt changes from (<) to the Shell prompt. or disconnect the power to the Fans. 1. C:\>exit 3. 5. or disconnect the cable to the fan subrack. Connect the power cabling to the Fan subrack. Make sure the alarm list is empty. 2. <APLOC. 6. Verify that an alarm is indicated by the system. FAN test This chapter can be omitted when the APG43 is delivered standalone. C:\>bupdef -n <ffr> -m <sfr> -s <sup> 1.4. Return to Central Processor (CP) mode. change it by using the command bupdef. <ALLIP. Test of CPS. Print the parameters for backup generation handling. or if the fan has been tested earlier. Restore the fan unit or cable. 8 . List all defined system backup files: <SYBFP:FILE. Printout: ALARM LIST 4. Switch to AP local mode on the AP where the procedure is to be done. Release the terminal: <CTRL-D> Printout: SYSTEM BACKUP FILES Leave the MML session: <EXIT. Verify that the alarm has ceased. Logon to the AP active side as a user with administrator rights and check that you are logged on to the active side. Print IO device table. Configuration Change for the SSU Folder 1. Print CP-AP connections. Change the APG43 configuration type.> 4. omit the next step and continue with the next chapter. 3. If OK. MSC or HLR for a One CP System. C:\>ssuls -l The printed configuration type must be BSC. Repeat step 1 on page 8 to step 8 on page 9 for all fans in the magazine Using the fan alarm function.5. if it is known what it must be. In this test the connection ports for AD-terminals are checked and tested. . C:\>cpdtest -c 3. 9.8. Check that it is the correct one.6. Printout: IO DEVICE DATA 6. IO Device in CP. C:\>prcstate 2. Attributes. If it is not known. it is only for AP1. . C:\>cpdchange < . C:\>exit 5. if it is not the correct one. that is. Return to Central Processor (CP) mode. 1. <IOIOP:IO1=ALL. C:\>cpdlist -l 2. <APLOC. Test of IO Device The test in this chapter must only be done if the APG43 also has got the APIO SW installed. Switch to AP local mode on the AP where the procedure is to be done. Change IO Device in CP if the test is not successful. List the APG43 configuration type for the SSU folder. 1. 9 . It must be BSC for a One CP system. The prompt changes from (<) to the Shell prompt 1. Display a list of directories in the root directory of the system disk and check that c:\acs\data\BUR\ exists. 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. if the directory does not exist: C:\>mkdir c:\acs\data\BUR 3. Logout from the current active side.C:\>ssucfg -c BSC -f Check the result: C:\>ssuls 1. C:\>prcstate C:\>hostname C:\>alist 2. C:\>dir /ad c:\acs\data Note: Create the BUR directory.7. Check current alarms. Backup of APG43 SW and Transfer to DVD 1. C:\>exit 4. Check current alarms. if the directory does not exist: 10 . C:\>dir /ad c:\acs\data Note: Create the BUR directory. Logon to the AP active side as a user with administrator rights check that you are logged on to the active side. Logon to the AP passive side as a user with administrator rights and check that you are logged on to the passive side. Check that directory ‘images’ exists in K:\. Is the current/last operation in status PROCESSING? YES: Wait a while for the copy process to finish. Check that the directories ‘NodeA’ and ‘NodeB’ exist. Note 4: The automatically generated image name is: sidename_YYYYMMDD_HHMMSS. backup of partition C:\ to D:\ is performed. data disk information is saved. Replace <clustername> with the Name of the cluster. Print the current/last operation: C:\>emfinfo 9. Otherwise continue with the next step. C:\>dir \\<clustername>\images 7. Note 2: A DVD of type DVD-R has to be chosen. This DVD must be used for the delivery to the customer...zip The automatically generated archive_filename is: K:\\Images\Node(A/B)\sidename_YYYYMMDD_HHMMSS. Processing time for 1 GB is approximately 22 minutes. continue with the next chapter. 10. . 11 . It is solved in LLV10. 11.zip Note 5: The text . Note 2: The created backup archives will be automatically verified. C:\>burbackup -o Confirm it by entering ‘y’ Note 1: The printout . . Insert an empty DVD into the APG43. returned error 5 .burBackup one button backup execution completed. followed by a prompt must be received 8. Transfer the backup file for side A on the DVD. . NO: If the APG43 contains no DVD board. Might be received according to TR HH91244. Perform a complete backup of both sides. Note 1: The DVD must be an approved version for APG43 DVD Media Compatibility List.C:\>mkdir c:\acs\data\BUR 6. Note 3: The procedure will take approximately one hour depending on system load. and an archive backup is stored on the data disks. The image name and archive_filename are automatically generated. That is. NO: Continue with the next step 14. Is the current/last operation in status PROCESSING? YES: Wait a while for the copy process to finish. Note 3: Lable the DVD with the name of the APG43. Processing time for 1 GB is approximately 22 minutes.C:\>emfcopy -m TODVD \\<clustername>\images\NodeA\<zipfile> Note 1: Parameter . Check the contents of the DVD: C:\>dir G: 15. Note 3: Lable the DVD with the name of the APG43. if the DVD is of type RW. so that the DVD is erased before data is copied to it. Note 2: A DVD of type DVD-R has to be chosen. and the date.o must be used. 19. and the date. Check the contents of the DVD: 12 . Insert another empty DVD into the APG43. 17. Note 1: The DVD must be an approved version for APG43. 12. C:\>emfcopy . NO: Continue with the next step. Note 2: Enter the command from the active side. Note 2: Enter the command from the active side. Processing time for 1 GB is approximately 22 minutes.DVD Media Compatibility List. Then go to step 12 on page 35. Is the current/last operation in status PROCESSING? YES: Wait a while for the copy process to finish. the side name. Transfer the backup file for side B on the DVD. if the DVD is of type RW and if it is not the same DVD as was used for side A. This DVD must be used for the delivery to the customer. so that the DVD is erased before data is copied to it. Print the current/last operation: C:\>emfinfo 13. 16. Print the current/last operation: C:\>emfinfo 18.m TODVD \\<clustername>\images\NodeB\<zipfile> Note 1: Parameter -o must be used. the side name. Perform a restore to the D: partition on the passive side. 2. Shutdown the passive side. C:\>copy G:\<imagename for side B>. C:\>burverify -i \\<clustername>\images\NodeA\<imagename for side A>. Note: Maximum two reboots in 30 minutes per APG43 side must be executed to prevent cyclic AP reboot. Make the passive side owner to the DVD.8. Restore passive side without rebooting the side. C:\>burrestore -a \\<clustername>\images\Node(A/B)\<imagename>. now passive. 4. C:\>emfget 3. C:\>burrestore -a \\<clustername>\images\Node(A/B)\<imagename>. Copy the zip backup for side A from the G: partition (DVD) to K:\images. Copy the zip backup for the side B from the G: partition (DVD) to K:\images.C:\>dir G: 1. C:\>prcboot -. 12.zip \\<clustername>\images\NodeA 5.zip 9. Insert a DVD with the backup for side A into the APG43. 6. Use command "net share sysvol" to make sure that the share is available.zip 8. Logon to the passive side. 10. Until the share is available a new backup must not be made.zip C:\>burverify -i \\<clustername>\images\NodeB\<imagename for side B>.zip \\<clustername>\images\NodeB 7. C:\>burrestore -r <imagename> -s Note: After a restore of the system it takes up to 10 minutes until the net share is available. Logon to the other active side and restore this side.zip 11. C:\>prcboot -s 13. Insert a DVD with the backup for side B into the APG43.f Wait until the side reboots and then logon to the same side. C:\>burrestore -r <imagename> 13 . Restore of APG43 SW from DVD 1. Verify the zip backups for both sides. C:\>copy G:\<imagename for side A>. Perform a restore to the D: partition on the other side that is now passive. Logon to the active side and reboot the side. Failover test (prcboot) - Reboot active node by entering C:\PRCBOOT After Failover. 1=active) using command C:\ phaprint acs_nsf_activeflag . Check that all cluster resources are online. Check all the cluster resources are online. 14. 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.Reconnect Ethernet cable and check interfaces are up running.Wait for Failover to occur and active node is rebooted. check that the external interfaces are up and running. . . . Verify cluster and side resources are online after restore C:\>cluster res Note: It can take some time before the side resources are online.10. Repeat on the second node (now active) 14 . Check the rebooted node (now passive) is up again and stable.9. 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 the rebooted node (now passive) is up again and stable.Check all the cluster resources are online. . C:\>cluster res | findstr -ive online 16. .Note: After a restore of the system it takes up to 10 minutes until the net share is available. NSF (Network Surveillance Function) testing External Network Surveillance Functionality .Check if functionality flag is active (0=not active. Until the share is available a new backup must not be made.If active disconnect the Ethernet (Public IP) cable in the active node. 15. Use command "net share sysvol" to make sure that the share is available.Repeat on the second node (now active) 1. Check for test file and rename it. Dir and cd ftpvol if needed Goto the dedicated FTP directory on the Node.1. open up a session to the active node. Exit session. Download file to Local PC. 15 . Exit session. Open a new session to the active node.11. such as that provided by MS-DOS. Check renamed file from Local PC. FTP test - Using a (S) FTP client. K:\ftpvol\ Upload any test file onto the directory. 2.1 APZ 212 55 HW configuration Figure 5 –APZ boards 16 . APZ 212 55 Tests 2. <SYBUE. switch the sides: <DPSWI. Make output of a system backup copy to RELFSW2. Check that the CP is in status WO. Printout: CP STATE 3. CP-A should be executive. Check the alarm list. <DPWSP. Release the terminal by entering <CTRL-D>. Passivate the automatic output function. 4. Printout: ALARM LIST 2. Printout: CP STATE If CP-A is not EX.Table 1 – APZ 212 55 cabling 2.2 Manual Intervention when CP-A is EX 1. <ALLIP. 17 . <SYBUP: FILE=RELFSW2. <SYBUI. Initiate a repair check. use the following parameters: <REMCI: MAG=CPU. RELFSW1 and RELFSW2. <REPCI. <RECCI. <DPWSP. Printout: CP DIAGNOSIS 6. Activate the automatic output function. RELFSW3 is not defined. Printout: CP REPAIR Note: In APZ 212 55 and APZ 212 60.3 Manual Intervention when CP-B is EX 18 . Initiate manual intervention in the CP with parameters of the selected suspected board. Release the terminal by entering <CTRL-D>. Select a suspected board from the list of CP DIAGNOSIS printout. <REMCI: MAG=mag.Note 1: Be sure first that you have an unbroken chain with RELFSW0. 9. Note 2: SYBUP command separates CP-SB in APZ 212 55 and in APZ 212 60. Printout: CP MANUAL INTERVENTION Note 2: Perform actions specified in printout CP MANUAL INTERVENTION 7. the system will always have the A side as EX after successful command execution. Printout: ALARM LIST 2. 10. <ALLIP. Make sure that CP-A is EX. Release the terminal by entering <CTRL-D>. PCB=PCB. Printout: CP STATE 8. Printout: CP MANUAL INTERVENTION Note 1: Perform actions specified in printout CP MANUAL INTERVENTION If the CP is faultless (Test RESULT = NO FAULT). 5. Check the alarm list. Printout: BACKUP INFORMATION OUTPUT PROGRESS Printout: BACKUP INFORMATION OUTPUT Wait until the output is finished. PCB=CPUB-B. Release the terminal by entering <CTRL-D>. Initiate procedure for CP repair. 1. Printout: CP STATE 2. Select a suspected board from the list of CP DIAGNOSIS printout. Printout: CP STATE If CP-B is not EX. Printout: CP STATE If CP-A is not EX. Release the terminal by entering <CTRL-D>. switch the sides: <DPSWI. <DPWSP. Printout: CP MANUAL INTERVENTION Note 1: Perform actions specified in printout CP MANUAL INTERVENTION If the CP is faultless (Test RESULT = NO FAULT). <RECCI. use the following parameters: <REMCI: MAG=CPU. <DPWSP. CP in WO state. Printout: CP REPAIR Note: In APZ 212 55 and APZ 212 60. Check whether CP-A is EX. Release the terminal by entering <CTRL-D>. Release the terminal by entering <CTRL-D>. PCB=PCB. <REMCI: MAG=mag. CP-B should be executive. Initiate a repair check. Release the terminal by entering <CTRL-D>. switch the sides: <DPSWI. Release the terminal by entering <CTRL-D>. <REPCI. <DPSWI. PCB=CPUB-A. Initiate manual intervention in CP with parameters of the selected suspected board. 6. Check whether CP-B is EX. Printout: CP STATE 19 . Initiate procedure for CP repair. Printout: CP MANUAL INTERVENTION Note 2: Perform actions specified in printout CP MANUAL INTERVENTION 4. the system will always have the A side as EX after successful command execution. Printout: CP DIAGNOSIS 3. Printout: CP STATE 5. Switch executive side. Information about the restart itself will be added. <ALLIP. 5. Wait until the CP state is WO. No new UNEXPECTED event should have occurred in conjunction with the restart. Check that the restart degree is SMALL and command initiated. The printout RESTART DATA is directed to the device defined for PRCA=32. <SYRAE. Printout: ALARM LIST 7. 20 . Check the CP event record. 4. Printout: CP EVENT RECORD 8. <SYRAP: SMALLMINUTES. EXPL=OTHER-TEST. Check the alarm list. Release the terminal by entering <CTRL-D>. 6. <SYREI: RANK=SMALL.4 Manual Initiated Small Restart 1. No new RP or EM events should have been added. Order a small restart. Example of expected alarms is alarms concerning the restart itself or the command log. No new UNEXPECTED alarms should have been added since before the restart.2. Check the RP event record. The printout RESTART DATA is directed to the device defined for PRCA=32. Printout: RESTART DATA Note: The printout is normally received within 5 minutes. Printout: RESTART DATA Note: The printout is normally received within 5 minutes. Order another small restart within SMALLMINUTES minutes from the first one. Check the alarm list. Print the restart escalation window for small restart. EXPL=OTHER-TEST. Printout: SMALL SYSTEM RESTART WINDOW 3. Printout: ALARM LIST 2. Information about the restart itself will be added as a common event. <DIRCP. Cease the alarm SYSTEM RESTART. RP events and EM events. <SYREI: RANK=SMALL. It contains information about common events. No fault type should be indicated. <ALLIP. Check that the restart degree is RANK SMALL and that it is command initiated. No new UNEXPECTED events should have occurred in conjunction with the restart. (No escalation for manual restarts). <DIRRP:RP=ALL. <ALLIP. <SYRAP: LARGEMINUTES. Information about the restart itself will be added. No fault type should be indicated. Check the alarm list. No new UNEXPECTED events should have occurred in conjunction with the restart. Printout: RP EVENT RECORD 2. EXPL=OTHER-TEST. Printout: SOFTWARE RECOVERY SURVEY <ALLIP. Print the restart escalation window for large restart. <SYRIP: SURVEY. 21 . Order another large restart within LARGEMINUTES minutes from the first one. <SYREI: RANK=LARGE. The printout RESTART DATA is directed to the device defined for PRCA=32. Cease the alarm SYSTEM RESTART. 4. Printout: ALARM LIST 2. <DIRCP. <SYRAE. Printout: ALARM LIST 7. 5. The printout RESTART DATA is directed to the device defined for PRCA=32. Check that the restart degree is LARGE and command initiated. EXPL=OTHER-TEST. Order that the restart degree is LARGE and that it is command initiated. (No escalation for manual restarts). No new UNEXPECTED restarts & alarms should have been added since before the restart. Check the alarm list. Order a large restart. 6. Wait until CP state is WO. Printout: LARGE SYSTEM RESTART WINDOW 3. Check the CP event record. Printout: RESTART DATA Note: The printout is normally received within 5 minutes. Example of expected alarms is alarms concerning the restart itself or the command log. Printout: RESTART DATA Note: The printout is normally received within 5 minutes. <SYREI: RANK=LARGE.5 Manual Initiated Large Restart 1. Check the alarm list.Release the terminal by entering <CTRL-D>. with the intention to create a new command log subfile reference for backup. <ALLIP. The command SYCSI with the parameter SFN is only accepted if this alarm exists.RELOAD PARAMETER INVALID. if the command SYCSI is entered without the parameter SFN.RELOAD PARAMETERS INVALID. is received. Fault Code 2 is then received in the alarm printout. Create a command log subfile.cp <cpname> -l 512 -c RELCMDHDF RELVOLUMSW Note: <cpname> must be written with capital letters. No new RP or EM events should have been added. The alarm . Printout: CP EVENT RECORD 8. 4. Return to Central Processor (CP) mode: C:\>exit 3. It contains information about common events. Otherwise it is rejected. Printout: ALARM LIST Check whether the alarm . 2. Information about the restart itself will be added as a common event.6 Activate the Command Log 1. Command: RP EVENT RECORD 2. C:\>cpfmkfile -l 512 -c RELCMDHDF RELVOLUMSW For a Multiple CP system: C:\>cpfmkfile . If the alarm ‘RELOAD PARAMETERS INVALID’ is not received. if such a reference did not exist. the parameter SFN must be omitted: 22 . Determine whether the command log file exists. RP events and EM events. The parameter SFN must be used when no reference to a command log subfile exists for backup. Note: The prompt changes from (<) to the Shell prompt. Switch to AP mode. create the command log file. C:\>cpfls -ls RELCMDHDF For a Multiple CP system: C:\>cpls -l C:\>cpfls -cp <cpname> -ls RELCMDHDF If it does not exist. <DIRRP: RP=ALL. No new UNEXPECTED events should have occurred in conjunction with the restart. Check the RP event record. <APLOC. is received. Note: FAULT CODE 23 is received. 23 . <APLOC. 2. <SYBUE. the parameter SFN must be used: <SYCSI: SFN=0000001. 1. C:\>cpfmkfile RELCMDHDF -0000001. <SYCLI.7 Manual Initiated Large Restart with Reload from MS This chapter is only for AP1. Release the terminal by entering <CTRL-D>. For a Multiple CP system: C:\>cpls -l C:\>cpfmkfile -cp <cpname> RELCMDHDF -0000001. Return to CP Mode. <SYBFP:FILE. Release the terminal by entering <CTRL-D>. <SYBFP:FILE=RELFSW2. Printout: SYSTEM BACKUP FILES 2. Manual Initiated Large Restart with Reload from Main Store (MS). Activate the command log. If the alarm ‘RELOAD PARAMETERS INVALID’ is received. 5. Wait for the result printout. since AP2 does not have APIO. Printout: COMMAND LOG ACTIVATION RESULT 3. Release the terminal by entering <CTRL-D>. C:\>exit Note: <cpname> must be written with capital letters. Release the terminal by entering <CTRL-D>. Printout: COMMAND LOG ACTIVATION RESULT The command log is activated.<SYCSI. if it has not already been initiated. Print the system backup files and make sure that RELFSW2 can be Overwritten. Passivate the automatic output of the system backup. The command logging function is initiated. if it is already passive. <SYCLI. It might then be necessary to first create the subfile by entering the following commands: Switch to AP mode. Make a system backup. 5. Release the terminal by entering <CTRL-D>. In that case command SYTUC is used for rotation of backup files. <SYBUP:FILE=RELFSW2. Activate automatic. the reload will be performed from file. RELFSW0 will afterwards contain the latest dump. Release the terminal by entering <CTRL-D>. in a live exchange) all the files RELFSW0. 24 . The contents of the files RELFSW0 and RELFSW2 are swapped. <SYTUC. If not validated.4. Return to CP Mode. Otherwise continue with this step. RELFSW1 and RELFSW2 contain valid dump generations. At start-up it might not be allowed to rotate the files. During normal operation (that is. proceed with the next step. periodic output towards the backup in the MS. Rotate the backup files. Printout: BACKUP INFORMATION OUTPUT PROGRESS Printout: BACKUP INFORMATION OUTPUT Wait until the printout is finished. The MS is validated by SYBUI. <APLOC. which means that reload is performed from MS. The predefined reloading file is RELFSW0. <DPWSP. because some of the files are defined but empty. Check that MS is validated. 7. C:\>exit 6. If SYTUC is successfully executed. Swap files. Wait for result printout. Note 1: The following procedure must never be used in a live switch! Switch to AP local mode. <SYBUI. 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. In this case a manual rotation can be done. The time is dependent of the size of the exchange. 13. Cease the alarm SYSTEM RESTART. <SYBFP:MS. 10.10 minutes for the reloading to finish. No new UNEXPECTED events should have occurred in conjunction with the restart. <DPWSP. No new UNEXPECTED alarms should have been added since before the restart. <SYREI:RANK=RELOAD. Printout: RESTART DATA Note: Wait 2. Release the terminal by entering <CTRL-D>. 12. Print time and file usage at the latest system restart with restart rank RELOAD. Printout: ALARM LIST Check whether the alarm MANUAL EXECUTION OF COMMAND LOG REQUIRED is received. Order a restart with reload. Release the terminal by entering <CTRL-D>. Printout: SYSTEM RELOADING INFORMATION Verify that the reload was performed from MS 11. 8. No fault type should be indicated. the reload will be performed from file the next time it is performed. follow the OPI . Print system backup copy in MS. 14.EXPL=OTHER-TEST. Manually Execute. If the alarm is received. The printout RESTART DATA is directed to the device defined for PRCA=32. Wait for the reloading to finish. <ALLIP. Example of expected alarms is alarms concerning the restart itself or the command log. 25 . <DIRCP. <SYBRP. Printout: SYSTEM BACKUP FILES 9.Command Log File. Information is then given about the reloading. Check that the MS validation is removed after the reload from MS.Printout: CP STATE BUA STATE must have the value 1 if MS is validated. Check the Error Interrupt Information. Check that a reload was performed and that it was command initiated. Print the alarm list. If so. <SYRAE. Information about the restart itself will be added. Printout: CP STATE BUA STATE must have a different value than 1 if MS is not validated. <SYBFP:FILE. Release the terminal by entering <CTRL-D>. Printout: COMMAND LOG ACTIVATION RESULT 3. Note: FAULT CODE 23 is received. Information about the restart itself will be added as a common event. <DIRRP:RP=ALL. if it has not already been initiated. No new UNEXPECTED events should have occurred in conjunction with the restart. Release the terminal by entering <CTRL-D>. If SYTUC is successfully executed. Make a system backup. Printout: RP EVENT RECORD 2.Printout: CP EVENT RECORD 15. Wait for the result printout. Note 1: This procedure must never be used in a live switch! Switch to AP local mode. <SYCLI. Otherwise Continue with this step. <SYBUE. No new RP or EM events should have been added. Printout: BACKUP INFORMATION OUTPUT PROGRESS Printout: BACKUP INFORMATION OUTPUT Wait until the printout is finished. Check the RP event record. Release the terminal by entering <CTRL-D>. proceed with the next step. <APLOC. <SYTUC. The command logging function is initiated. 5. Rotate the reload files manually. <SYBUP: FILE=RELFSW2. Release the terminal by entering <CTRL-D>. if it is already passive 4. Passivate the automatic output of the system backup. Printout: SYSTEM BACKUP FILES 2. RP events and EM events. C:\>cpfrename relfsw0 dummy C:\>cpfrename relfsw2 relfsw0 C:\>cpfrename relfsw1 relfsw2 26 . Print the system backup files and make sure that RELFSW2 can be overwritten. Release the terminal by entering <CTRL-D>. Rotate files.8 Manual Initiated Large Restart with Reload from File 1. Rotate the backup files. It contains information about common events. <SYBFP:FILE=RELFSW2. C:\>exit 6. Information is then given about the reloading. Printout: ALARM LIST Check whether the alarm MANUAL EXECUTION OF COMMAND LOG REQUIRED is received. Release the terminal by entering <CTRL-D>. The printout RESTART DATA is directed to the device defined for PRCA=32. <SYBRP. Printout: SYSTEM RELOADING INFORMATION Verify that the reload was performed from the file RELFSW0. The time is dependent of the size of the exchange. No new UNEXPECTED alarms should have been added since before the restart. follow the OPI . 9. Wait for the reloading to finish. <SYREI: RANK=RELOAD. Printout: CP EVENT RECORD 27 . Print the alarm list. Example of expected alarms is alarms concerning the restart itself or the command log.Command Log File. Check that a reload was performed and that it was command initiated.10 minutes for the reloading to finish.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. Order a restart with reload. If the alarm is received. 8. Print time and file usage at the latest system restart with restart rank RELOAD. Printout: RESTART DATA Note: Wait 2. No new UNEXPECTED events should have occurred in conjunction with the restart. Manually Execute. No fault type should be indicated. <SYRAE. Check the Error interrupt Information. Cease the alarm SYSTEM RESTART. Information about the restart itself will be added. 7. <ALLIP. 10. EXPL=OTHER-TEST. <DIRCP. It contains information about common events. 2. If it does not have any power switch. Note 1: The boards can be disconnected in any order. Note 2: The alarm CP FAULT is received due to missing MAUB. Check the RP event record. 3. 7. <SYREI: RANK=SMALL. Order a small restart to set the time in all APT blocks. Note 3: A torx wrench is needed to disconnect the boards. Wait 2-15 minutes for the reload to finish.9 FEX Load on CP-A 1. DATE=yymmdd. RP events and EM events. Note: Use the unconditional power switch on the MAUB. 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. not completely removed from the magazine. job buffers and time queues. Note: Use the unconditional power switch on the MAUB. push in the MAU board. 28 . Cease the alarm SYSTEM RESTART. Disconnect the power to MAUB and wait 10 seconds. The following exchange header is an example of a printout that can be received. Reconnect the CP-A board into the eGEM. ‘FEX’ must be received as CP state. EXPL=OTHER-TEST.11. <SYRAE. pull out the MAU board. No new UNEXPECTED events should have occurred in conjunction with the restart. (Printout terminal defined for PRCA=32). If it does not have any power switch. Disconnect the CP-A board and the CP-B board from the eGEM. due to the fact that the display is connected to the MAUB. Printout: RESTART DATA <SYRIP: SURVEY. 5. 4. Note 2: The boards should only be pulled out a few centimetres. Printout: RP EVENT RECORD 2. No new RP or EM events should have been added. Set the program clock. Reconnect the power to MAUB. Information about the restart itself will be added as a common event. <DIRRP:RP=ALL. if the logon attempt is successful. <CACLS: TIME=hhmm. 6. Printout: RESTART INFORMATION Note: The alarm CP FAULT reappears due to the system restart. Note 2: The boards should only be pulled out a few centimeters. 9. <RECCI. Reconnect the CP-B board into the eGEM. Wait 5 minutes until CP display arrives to 390 phase.10 FEX Load on CP-B 1. CP-B. Make a parallel start of standby CP-side. Release the terminal by entering <CTRL-D>. Wait for CP to return to parallel operation. Reconnect the CP-B board into the eGEM. Wait 2-15 minutes for the reload to finish. 10. due to the fact that the display is connected to the MAUB. The following exchange header is an example of a printout that can be received. Disconnect the CP-A board and the CP-B board from the eGEM. pull out the MAU board. <DPWSP. Note 2: The alarm CP FAULT will cease. 2. Check the CP. if the logon attempt is successful. Printout: CP STATE 2. Note 2: The alarm CP FAULT is received due to missing MAUB. the system will always have the A side as EX after successful command execution. Note 3: A torx wrench is needed to disconnect the boards. 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. must be received as CP state. Note: Use the unconditional power switch on the MAUB.8. 3. If it does not have any power switch. not completely removed from the magazine. Printout: CP REPAIR Note 1: In APZ 212 55 and APZ 212 60.FEX. Note 1: The boards can be disconnected in any order. <RECCI. Disconnect the power to MAUB and wait 10 seconds. 29 . 11. Release the terminal by entering <CTRL-D>. Printout: CP REPAIR Note: The alarm CP FAULT will not cease even though RECCI is successfully completed. . <RECCI. CP-A. 9. Check the CP. DATE=yymmdd. Printout: CP STATE 12. <DPWSP. 8. Initiate command logging. Note: Use the unconditional power switch on the MAUB. Printout: RESTART INFORMATION Note: The alarm CP FAULT reappears due to the system restart. Set the program clock. Printout: CP REPAIR Note: The alarm CP FAULT will not cease even though RECCI is successfully completed. <RECCI. 6. Make a parallel start of standby CP-side. (Printout terminal defined for PRCA=32). <SYREI: RANK=SMALL. Printout: RESTART DATA <SYRIP: SURVEY. <SYRAE. the system will always have the A side as EX after successful command execution. Printout: COMMAND LOG ACTIVATION RESULT 30 . If it does not have any power switch. Release the terminal by entering <CTRL-D>.4. 7. Wait for CP to return to parallel operation. Order a small restart to set the time in all APT blocks. Release the terminal by entering <CTRL-D>. 11. Reconnect the CP-A board into the eGEM. push in the MAU board. Reconnect the power to MAUB. 5. <SYCLI. <CACLS: TIME=hhmm. EXPL=OTHER-TEST. Release the terminal by entering <CTRL-D>. Printout: CP REPAIR Note 1: In APZ 212 55 and APZ 212 60. Note 2: The alarm CP FAULT will cease. 10. job buffers and time Queues. Cease the alarm SYSTEM RESTART. Wait 5 minutes until CP display arrives to 390 phase. C:\>exit Note 2: The prompt changes from the Shell mode to (<). <SAOCP. Return to CP mode. <SYATI: RESTART. 2. 31 . 5. C:\>mml -as For a Multiple CP system: C:\>cpls . Connect to CP-EX. <SAOCS: STATE=PASSIVE. Printout: DATA TRANSFER RESULT 6. <APLOC. <SYBUE. Note 1: The prompt changes from (<) to the Shell prompt. <FCDAT. <FCSEI. if it is already passive. If the automatic size alterations function is active. make it passive. Connect to CP-SB.l C:\>mml -cp <cpname> -as Note 2: <cpname> must be written with capital letters. Switch to AP mode. Note: FAULT CODE 23 is received. 7. Separate CP-SB. End CP-SB terminal session. Start the application blocks in CP-SB. 4. <FCMOS: MODE=UMBNOTRSWI.2. Deactivate the automatic dumping of DS variables Wait for the printout. Set the FC mode. Order data transfer from CP-EX to CP-SB. <EXIT. Note 3: The prompt changes from the Shell prompt to (<).11 Function Change Method II 1. Note 1: The prompt changes from (<) to the Shell prompt. Printout: RESTART DATA 8. Deactivate the automatic dumping of DS variables. Small restart of the APZ blocks is performed in SB side 3. <FCSWI. Release the terminal by entering <CTRL-D>. Release the terminal by entering <CTRL-D>. <DPPAI. Rotate the reload files. then activate it. <SYTUC. Then RECCI is used to order CP in normal state. 14. ORDERED Release the terminal by entering <CTRL-D>. the system will always have the A side as EX after successful command execution.12 Initial Loading of CP-A Initial loading is performed to CP-side A. <SYBUI. <SYBUP:FILE.9. Switch the CP sides.). Make parallel start of CP-SB side. 11. 2. <SAOCS:STATE=ACTIVE. Connect CPT. Activate the automatic dumping. Open mml session to CP-SB. 32 . Printout: CP SB START PASSED Note: In APZ 212 55 and APZ 212 60. Printout: BACKUP INFORMATION OUTPUT PROGRESS Printout: BACKUP INFORMATION OUTPUT Wait until the printout is finished. If the automatic size alteration function was set to passive in step 1. Perform a manual backup copy. 10. C:\>mml -as 2. Printout: OUTPUT TO FILE RELFSW2: Accept the proposed file and give order for execution with semicolon (. 12. Release the terminal by entering <CTRL-D>. 1. 13. Check CP status: cpt<PTWSP. when the PHCI function is active. 4. use the following command. Check if file RELFSW99 exists: C:\>cpfls Printout: CPF FILE TABLE For details of selected RELFSW99 file: C:\>cpfls -ls RELFSW99 33 . Stop program execution. 6. Ensure that the PHCI function is active. 3. 5. The PHCI indicator is on. cpt<PTSES. cpt<PTSWI. Disconnect CPT : cpt<PTCOE. Close mml session to CP-SB . <EXIT. If CP-A is not CP-SB. Separate the CP. cpt<PTPEE. 7. 8.<PTCOI. check the meaning of the fault code in POD. Enter <CTRL-D> on the IO terminal used for CPT. cpt<PTCPL:CS=A. Check the printouts from CPT (this repeats for a few minutes). If loading is not successful. Printout: CPT MESSAGE INITIAL LOADING (ABSOLUTE) STOPPED 34 .Printout: CPF FILE TABLE Open mml session to CP-SB . Release the IO terminal and wait for the initial load to finish. Connect CPT. Order an initial load. 12. C:\>mml -as 9.FILE=RELFSW99. Printout: CPT MESSAGE INITIAL LOADING (ABSOLUTE) STARTED Printout: CPT MESSAGE INITIAL LOADING (ABSOLUTE) IN PROGRESS 13. <PTCOI. The following printouts may be received. 11. If loading is successful. this printout may appear: Printout: CPT MESSAGE INITIAL LOADING (ABSOLUTE) FINISHED 14. 10. 21. 15. <DIEFC:FORM=2. Set Error Printout Format to large format in CP-SB. <EXIT. C:\>mml -as 18. 35 .Printout: CPT MESSAGE INITIAL LOADING (ABSOLUTE) STARTED Printout: CPT MESSAGE *** INITIAL IN PROGRESS LOADING ABNORMAL Solve the fault. 16. Start the application blocks in CP-SB. and start again from step Error: Reference source not found on page Error: Reference source not found. Open mml session to CP-SB. 17. Close mml session. Disconnect CPT: cpt<PTCOE. Printout: SYSTEM STARTED (if received) 19. or the exchange header. <SYATI:RESTART. Close mml session to CP-SB. Printout: SYSTEM RESTARTED 20. Wait for printout result (RANK SYSTEM START) after loading in CP-SB side. Passivity the PHCI function by pressing the PHCI button on the MAU board. 36 . C:\>mml -a 23. Wait for a large restart in CP-EX. <PTCOI.<EXIT. Switch EX-side. <CACLS:DATE=yymmdd.TIME=hhmm. The PHCI indicator is off when the PHCI function is passive. 28. Set the program clock in CP-EX. 25. Open mml session to CP-EX. side A. Connect CPT. 24. 22. Printout: SYSTEM RESTARTED 27. cpt<PTCOE. 26. cpt<PTSWI. Disconnect CPT. Then the restart is received as a result of the Side Switch. to the highest defined reload file in an unbroken sequence of files) : <SYBUP:FILE. Check that CP-A is EX and CP-B is SB. Wait for result: <RECCI. 30. <EXIT.e. <DPWSP. Prepare output of a system backup copy to RELFSW2 ( i. ORDERED Release the terminal by entering <CTRL-D>. Close mml session.29.13 Initial Loading of CP-B 37 . Printout: CP REPAIR 31. Printout: CP STATE 32.). Printout: BACKUP INFORMATION OUTPUT PROGRESS Printout: BACKUP INFORMATION OUTPUT Wait until finished. Printout: OUTPUT TO FILE RELFSW2 Accept the proposed file and give order for execution with semicolon (. Make parallel start of CP-SB side. 2. Separate the CP. 7.This section is intended to ensure that initial loading has been tested on CP-B. Connect CPT. 1. 6. 5. Stop program execution. Disconnect CPT. Activate the PHCI function. 3. Check CP status: cpt<PTWSP. 4. The PHCI indicator is on. <PTCOI. side B. 38 . cpt<PTSES. Open mml session to CP-SB. Close mml session to CP-SB . Printout: CP STATE The states should be CP-A EX and CP-B SBWO. when the PHCI function is active. C:\>mml -as 2. cpt<PTCOE. cpt<PTPEE. <PTCOI. The following printouts may be received. Enter <CTRL-D> on the IO terminal used for CPT. Connect CPT. cpt<PTCPL:CS=B. 11. C:\>mml -as 8. Order an initial load. Printout: CPT MESSAGE INITIAL LOADING (ABSOLUTE) STARTED Printout: CPT MESSAGE INITIAL LOADING (ABSOLUTE) IN PROGRESS 39 . 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 . 9. Release the IO terminal and wait for the initial load to finish. Check the printouts from CPT (this repeats for a few minutes).FILE=RELFSW99. 10.<EXIT. C:\>mml -as 17. 16. Close mml session. this printout may appear: Printout: CPT MESSAGE INITIAL LOADING (ABSOLUTE) FINISHED 14.12. <EXIT. Printout: SYSTEM STARTED (if received) 40 . Wait for printout result (RANK SYSTEM START) after loading in CP-SB side. check the meaning of the fault code in POD. 13. or the exchange header. Printout: CPT MESSAGE INITIAL LOADING (ABSOLUTE) STOPPED Printout: CPT MESSAGE INITIAL LOADING (RELOCATABLE) STARTED Printout: CPT MESSAGE *** INITIAL LOADING PROGRESS ABNORMAL Fix the fault. 15. cpt<PTCOE. Open mml session to CP-SB. If loading is not successful. If loading is successful. and start again from Step Error: Reference source not found on page Error: Reference source not found. Disconnect CPT. Printout: SYSTEM RESTARTED 19.18. 37. <SYATI:RESTART. Disconnect CPT. <DIEFC:FORM=2. Connect CPT. cpt<PTCOE. Set Error Printout Format to large format in CP-SB. Wait for a large restart in CP-EX. Close mml session to CP-SB. Start the application blocks in CP-SB. C:\>mml -a 35. Printout: SYSTEM RESTARTED 41 . 34. 33. Open mml session to CP-EX. 36. 38. <PTCOI. Switch EX-side. cpt<PTSWI. <EXIT. OUTPUT TO FILE RELFSWX: .TIME=hhmm. 42 . Set the program clock in CP-EX. Close mml session. Prepare output of a system backup copy to RELFSWn ( n. 40. <EXIT. <CACLS:DATE=yymmdd. ORDERED Printout: OUTPUT TO FILE 42.39. Printout: CP REPAIR 43. Check that CP-SB can be updated. 41. Passivity the PHCI function on the MAU: Press the PHCI button on the MAU. <RECCI. highest defined reload file in an unbroken sequence of files) : <SYBUP:FILE. Start parallel operation. Wait for result. The PHCI indicator is off when the PHCI function is passive. the power must have been "on" for a minimum of 15 minutes.RP=rp. cabling and making sure that RPs and EMs are working. --------------------------------------------------------------------------------------------1. Before test 8. Command: EXRPP:RP=rp. except for diagnostic test due to error conditions encountered in test 8. Make sure that the GEM/CDM magazines are strapped and cabled correctly --------------------------------------------------------------------------------------------2. undefine the NS data. Printout: EM DATA --------------------------------------------------------------------------------------------- 3.1 Check of RPs and EMs This is an initial check of strapping. In this case. Check that the CLMs are defined and the state of the CLMs. but none of the sources are working. Check that EMs are Working (WO). RCM shall be blocked during the test. then the test of CLMs will fail. Command: EXEMP:EM=ALL. Printout: RP DATA --------------------------------------------------------------------------------------------3. --------------------------------------------------------------------------------------------1.3 APT Tests: 3. 43 .2 Note: Test of CLM If Network Synchronization data is defined. Check that RPs are Working (WO). Confirm the blocking order. 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. Printout: DISTRIBUTED GROUP SWITCH UNIT DEBLOCKING RESULT --------------------------------------------------------------------------------------------3. Command: GDBLE:UNIT=CLM-1.Command: GDSTP:UNIT=unit. Command: GDBLI:UNIT=CLM-0. --------------------------------------------------------------------------------------------6. Printout: DISTRIBUTED GROUP SWITCH UNIT DEBLOCKING RESULT --------------------------------------------------------------------------------------------5. Initiate the test for CLM-0 and wait for result printout. 44 . Deblock CLM-0 and make sure that CLM-0 is WO and the other CLMs are MBL. Deblock CLM-1. Wait until CLM-1 is WO. Printout: DISTRIBUTED GROUP SWITCH STATE --------------------------------------------------------------------------------------------2. Initiate the test for CLM-1. then block CLM-0. Command: GDBLE:UNIT=CLM-0. Command: GDTEI:UNIT=CLM-1. Printout: DISTRIBUTED GROUP SWITCH UNIT TEST RESULT --------------------------------------------------------------------------------------------4. replace both CGB boards (it is not possible to discriminate which board is faulty). Deblock CLM-0. 2. Test plane A in the XM Command: GDTEI:UNIT=XM-A-0-0. replace the faulty board.3 Test of XM RPs and EMs for XMs should be deblocked and working. Try to activate NS (i. Command: GDBLE:UNIT=CLM-0. deblock RCM or any other external reference).Command: GDTEI:UNIT=CLM-0. Deblock the XM. Printout: DISTRIBUTED GROUP SWITCH CLM CONTROL VALUE --------------------------------------------------------------------------------------------- 3. follow the procedure: 1. If the activation is successful.e. Printout: DISTRIBUTED GROUP SWITCH UNIT TEST RESULT --------------------------------------------------------------------------------------------2. Should be 32768 +-7000 (for all oscillators). 3. DO NOT ADJUST CONTROL VALUE Command: GDCVP. 45 . If not. --------------------------------------------------------------------------------------------1. If the activation is not successful then: If the value out of range belons to oscillator 1 (son). If the value out of range belongs to oscillator 0 (father). Check CONTRVALUE. Printout: DISTRIBUTED GROUP SWITCH UNIT TEST RESULT --------------------------------------------------------------------------------------------7. Printout: DISTRIBUTED GROUP SWITCH UNIT DEBLOCKING RESULT --------------------------------------------------------------------------------------------8. wait 10 hours and repeat test 8. both A. both A. Test plane A in the MUX3 Command: GDTEI:UNIT=MUX3-A-0. Repeat step 1 and 2 for all MUX3s. Printout: DISTRIBUTED GROUP SWITCH STATE 46 . Repeat point 1 and 2 for all XMs. Printout: DISTRIBUTED GROUP SWITCH UNIT DEBLOCKING RESULT --------------------------------------------------------------------------------------------3. Command: GDSTP. --------------------------------------------------------------------------------------------4.and B-plane. --------------------------------------------------------------------------------------------1. Printout: DISTRIBUTED GROUP SWITCH STATE --------------------------------------------------------------------------------------------- 3. All XMs should be working. Check the working state of the group switch. Printout: DISTRIBUTED GROUP SWITCH UNIT TEST RESULT --------------------------------------------------------------------------------------------2. Command: GDSTP. so there is no need to check EMs. --------------------------------------------------------------------------------------------4. Deblock the MUX3. Check the working state of the group switch. All MUX3s should be working.Command: GDBLE:UNIT=XM-A-0-0.and B-plane. Command: GDBLE:UNIT=MUX3-A-0.4 Test of MUX3 MUX3 have no EM control. Printout: DISTRIBUTED GROUP SWITCH UNIT DEBLOCKING RESULT ---------------------------------------------------------------------------------------------3. Printout: DISTRIBUTED GROUP SWITCH UNIT DEBLOCKING RESULT --------------------------------------------------------------------------------------------4.and B-plane. Command: GDSTP. Check the working state of the group switch.--------------------------------------------------------------------------------------------- 3. Command: GDBLI:UNIT=XM-A-0-0. Printout: DISTRIBUTED GROUP SWITCH STATE --------------------------------------------------------------------------------------------- 47 . Test XM in plane A. Repeat point 1 and 2 for all XMs. Block XM in plane A. both A. Command: GDBLE:UNIT=XM-A-0-0. Printout: DISTRIBUTED GROUP SWITCH UNIT BLOCKING RESULT --------------------------------------------------------------------------------------------2.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. Command: GDTEI:UNIT=XM-A-0-0. Deblock the XM. All XMs should be working. --------------------------------------------------------------------------------------------1. --------------------------------------------------------------------------------------------5. Printout: DISTRIBUTED GROUP SWITCH UNIT TEST RESULT --------------------------------------------------------------------------------------------3. Printout: CLOCK REFERENCE TEST RESULT --------------------------------------------------------------------------------------------5. Deblock the RCM if the test was successful. 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. Initiate test of RCM. --------------------------------------------------------------------------------------------3. Print the network synchronization data. Printout: CLOCK REFERENCE STATE Command: NSBLI:RCM=RCM-x. --------------------------------------------------------------------------------------------2. Check if the RCM is defined and manually blocked (otherwise block it).6 Test of RCM External Network Synchronization should be blocked during this test. Load all Network Synchronization commands from DT. --------------------------------------------------------------------------------------------1.3. 48 . In this test the RCM connection to the CLMs and the RCM data are checked and the RCM is deblocked. Printout: CLOCK REFERENCE SUPERVISION DATA --------------------------------------------------------------------------------------------4. These are tested later during the integration test of the exchange. Command: NSTEI:RCM=RCM-x. Command: NSSTP. During test the frequency deviation and wander of the reference clock is controlled against values printed above. Command: NSDAP. External clock references should be left manually blocked. In the case of MSP 1+1 protection disconnect cable on ODF from other port of protected pair. Repeat above steps for all exchange terminals in the node. In the case of MSP 1+1 protection disconnect cable on ODF from one port of protected pair. Printout: NETWORK SYNCHRONIZATION MANUAL DEBLOCKING OF CLOCKREFERENCE EXECUTED --------------------------------------------------------------------------------------------- 3. --------------------------------------------------------------------------------------------2.Command: NSBLE:RCM=RCM-x. 49 . Command: TPSTP:SDIP=<SDIP name>. Command: TPSTP:SDIP=<SDIP name>.7 Test of ET Exchange terminal should be checked during this test. Perform loopback test of ET terminal on ODF. Printout: SYNCHRONOUS DIGITAL PATH STATE --------------------------------------------------------------------------------------------5. Check if the status of SDIP using command TSTP. Printout: SYNCHRONOUS DIGITAL PATH STATE --------------------------------------------------------------------------------------------3. Make sure that state for SDIP is working. Note: MSP 1+1 protection also is checked during this test. In the case of MSP 1+1 both MS should be in working state. MSP 1+1 protection is optional and can be omitted during configuration. Make sure that state for SDIP is working. Make sure that state for SDIP is working. --------------------------------------------------------------------------------------------1. Printout: SYNCHRONOUS DIGITAL PATH STATE --------------------------------------------------------------------------------------------4. Command: TPSTP:SDIP=<SDIP name>. 50 .