The Next Generation Archive SystemNGAST Internal Home Page |
|
|
|
|
| TEST 1: o Check the NGAS WEB Site: o Check that the "NGAST Internal Home Page" is properly loaded and readible. o Check that the "NGAS Disk Status Form" works as expected. o LS/WFI ONLY: Check that the "Last Archived WFI Frames" page works properly. o Check that the "NGAS Last Night Report" page works properly. o Check that the "Disk status Tool" works properly: o Check listed disks. o Click on a disk and inspect specific contents. o Click on the files of one of the disks check the list and a specific file. Also query the information from Observations DB. o Check the "Host Status Tool" if the hosts of interest are correctly displayed. (o Check the "Server Status Tool" and verify that the status is correctly displayed.) o Check that the "NGAS Operations Guide" can be accessed and is understood. o Check that the "NGAS Installation Guide" can be accessed and is understood. o Check that the "NGAS Troubleshooting Guide" can be accessed and is understood. o Check that the "NGAS Hardware Specifications" can be accessed and is understood. o Check that the "NG/AMS User Manual" can be accessed and is understood. o GAR ONLY: Check that the "NGAS Disk Recycling Manual" can be accessed and is understood. o LS ONLY: Check that the "Disk Procedures" manual can be accessed and is understood. o Check the "NGAST Contact Addresses" can be accessed. |
| TEST 2: o Log in on NGAS host as "ngasmgr": o NAU Host. o NBU Host. o AHU Host. |
| TEST 3: o Check that the NG/AMS Python-Client is Correctly Installed: o Check man-page: % ngasmgr> ngamsPClient: o NAU Host. o NBU Host. o AHU Host. o Check correct version: % ngasmgr> ngamsPClient -version: o NAU Host. o NBU Host. o AHU Host. |
| TEST 4: o Check that the NG/AMS C-Client is Correctly Installed: o Check man-page: % ngasmgr> ngamsCClient: o NAU Host. o NBU Host. o AHU Host. o Check correct version: % ngasmgr> ngamsCClient -version: o NAU Host. o NBU Host. o AHU Host. |
| TEST 5: o Check that the NG/AMS Server is running properly: o Inspect output from (check that Online): % ngasmgr> ngamsCClient -host <NAU> -port 7777 -status -cmd STATUS: o NAU Host. o NBU Host. o AHU Host. o Check that the NG/AMS Log File is available (check that updated recently after start-up): % ngasmgr> tail /NGAS/ngams_staging/log/LogFile.nglog: o NAU Host. o NBU Host. o AHU Host. |
| TEST 6: o Check that the NGAS disks in the system are mounted as expected: % ngasmgr> df /NGAS/data* o NAU Host. o NBU Host. o AHU Host. |
| TEST 7: o Reboot DHS Machine and Check that "ngamsIngest" is Running Properly: % <user>> ps -ef | grep ngamsIngest |
| TEST 8: o Check that an Archive Request can be handled properly on NAU. Issue a file directly to NG/AMS and inspect the XML output: % ngasmgr> ngamsCClient -host w2p2nau -port 7777 -status -cmd ARCHIVE -fileUri /opsw/NGAS/ngams/ngamsTest/src/SmallFile.fits |
| TEST 9: o Shutdown NGAS Host (CTRL-ALT-DEL on system console): o Check that the system swicthes off: o NAU Host. o NBU Host. o AHU Host. o Check that disks previously mounted in this host are now marked as unmounted in the NGAS WEB Site: o NAU Host. o NBU Host. o AHU Host. |
| TEST 10: o Start Up of NGAS Host: o NAU Host. o NBU Host. o AHU Host. o Check that the disk previously unmounted are now mounted. |
| TEST 11: o Archive WFI file on NAU. Produce file with WFI and observe that it is properly archived: o Check that the file appears in the list of files in the NGAS WEB Interfaces. o Check that the file appears as expected in the "Last Archived WFI Frames" page. o Check that log entries were produced on the NAU in connection with the handling of the Archive Request: % ngasmgr> tail /NGAS/ngams_staging/log/LogFile.nglog o Check that the file is physically stored on the Main and Replication Disks. o Check the log output from ngamsIngest: % e2p2ops> tail ... (o Check that an entry appears in the DFS Log Monitor for the Archive Request. ) |
| TEST 12: o Mondo Rescue CD Preparation. Create Installation CD according to "NGAS Troubleshooting Guide"/"Rescue CD Creation Procedure": o NAU Host. o NBU Host. o AHU Host. |
| TEST 13: o Installation of NGAS Host with Mondo Rescue CD: o Install: o NAU Host. o NBU Host. o AHU Host. o Switch on and check that the NG/AMS Server is up and running (check XML output): % ngasmgr> ngamsCClient -host w2p2nau -port 7777 -status -cmd STATUS: o NAU Host. o NBU Host. o AHU Host. |
| TEST 14: o Swap NBU->NAU: o Log into the NBU and follow the instructions given in "NGAS Troubleshooting Guide"/"NAU/NBU Switch Procedure". (o Restart ngamsIngest on the DHS machine changing the environment variable "NGAMS_HOST" to the host name of the NBU. |
| TEST 15: o Archive a file by copying it to the NG/AMS Back-Log Area: o Put the file via ftp, scp or rcp in the directory "w2p2nau:/NGAS/ngams_staging/back-log". Use e.g. file: "/opsw/NGAS/ngams/ngamsTest/src/SmallFile.fits " o Check in the NGAS WEB interfaces that the file has been archived. |
| TEST 16: o AHU ONLY: Data Consistency Checking: o Insert one or more disks in the AHU. o Observe that there is regular reading activity on the disk(s). o When the check has been carried out, check the "Last Check" column in the NGAS WEB Interfaces (specific disk status). o If descrepancies were found, check that a proper email indicating this was sent out by NG/AMS. |
| TEST 17: o AHU ONLY: Disk Cloning - Postponed. |
| TEST 18: o AHU ONLY: Disk Registration - Postponed. |
| TEST 19: o AHU ONLY: Disk Removal - Postponed. |
|
TEST 20: |
|
||||||||||||||