06MW3.5 SW LFC

Open Unix Shell and type the following:

1. {ctuser@hostname} rsh  darc

2. [ctuser@darc] cat /proc/scsi/scsi

   note:

   Output should look similar to the following. Look for two drives. If there are NOT two drives, troubleshoot.

   Attached devices:

   Host: scsi0 Channel: 00 Id: 00 Lun: 00

        Vendor: SEAGATE Model: ST336753LW Rev: 0006

        Type: Direct-Access ANSI SCSI revision: 03

   Host: scsi0 Channel: 00 Id: 01 Lun: 00

        Vendor: SEAGATE Model: ST336753LW Rev: 0006

        Type: Direct-Access ANSI SCSI revision: 03

3. Close the Unix Shell.

Perform this recommended procedure to check DVD or MOD functionality prior to performing a LFC.

1. Verify the SCSI Tower DVD-RAM power is applied and the green LED at front of tower is lit.

2. Verify the SCSI Tower terminator LED is lit (located at the rear).

3. Verify the Host Computer DVD-ROM drive does not have a disk in it.

4. Open a Unix Shell and verify the SCSI Tower components are present (two examples are shown below, but may not match your SCSI Tower configuration):

   {ctuser@hostname} scsistat

   Example #1:

   Device 0 00 Direct-Access SEAGATE ST336753LW FW Rev: HPS2 OS 36 GB

   Device 1 01 Direct-Access SEAGATE ST373453LW FW Rev: HPS2 73 GB Image

   Device 1 02 Direct-Access SEAGATE ST373453LW FW Rev: HPS2 73 GB Image

   Device 2 03 Optical Device SONY SMO-F551-SD FW Rev: 1.04 SCSI Tower Sony MOD

   Device 2 04 CD-ROM MATSHITA DVD-RAM LF-D521 FW Rev: A109 SCSI Tower DVD-RAM

   Example #2:

   Device 0 00 Direct-Access SEAGATE ST336753LW FW Rev: HPS3

   Device 1 01 Direct-Access SEAGATE ST373453LW FW Rev: HPS3

   Device 1 02 Direct-Access SEAGATE ST373453LW FW Rev: HPS3

   Device 2 03 Optical Device SONY SMO-F551-SD FW Rev: 1.03 SCSI Tower Sony MOD

   Device 2 04 CD-ROM HITACHI DVD-RAM GF-2050 FW Rev: E372 SCSI Tower Hitachi DVD-RAM

   Device 4 00 CD-ROM HL-DT-ST DVD-ROM GDR8163B FW Rev: 0B15

5. (For Linux Consoles Only) DVD Drive Verification:

   1. Create a temporary testing file:

      {ctuser@hostname} su  -

      Password: <password>

      {root@hostname} dd  if=/dev/urandom  of=/tmp/foo  bs=1024  count=50k

      51200+0 records in

      51200+0 records out

   2. Ensure the temporary testing file was created:

      {root@hostname} ls  -al  /tmp/foo

      -rw-r--r-- 1 root root 52428800 May 10 11:55 /tmp/foo

      (”5242880” represents the file size.)

   3. Calculate the checksum for the local temporary file.

      note:

      These numbers will change every time you generate a new file.

      {root@hostname} sum  /tmp/foo

      45731   51200

      note:

      1st # = checksum (FE should write this down to use for comparison later)

      2nd # = size of file checksum'd

      Checksum    File Size in kilobytes

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

      45731                51200

   4. Insert DVD into SCSI Tower.

      Data on inserted DVD will be destroyed.

   5. Create a filesystem on the DVD by typing the following:

      {root@hostname} mkfsDVD

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

      *** CAUTION ***

      A filesystem already exists on this DVD.

      This utility will create a new file system on the DVD. In turn it will wipe clean any existing files and data. Make sure you have the correct DVD media in the correct DVD drive.

      Do you wish to proceed? [n] y

      Making file system. This will take approximately 3-5 minutes

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

   6. Mount the DVD:

      {root@hostname} mountDVD

      Mounting DVD

   7. Copy the file to the target device:

      {root@hostname} cp  /tmp/foo  /DVD  &&  sync

   8. Unmount the drive & eject the DVD to ensure the system's cache is flushed. This is required to calculate the checksum properly.

      1. {root@hostname} unmountDVD

         DVD is now unmounted.

      2. Eject the DVD

      3. Reinsert the DVD

      4. Remount the target device, using mountDVD.

   9. Generate checksum on file in DVD drive:

      {root@hostname} sum  /DVD/foo

      45731 51200

   10. Verify (compare) the file's checksum calculated by the host console matches the checksum calculated by the drive.

   11. {root@hostname} unmountDVD

       DVD is now unmounted.

   12. Eject the DVD

6. (For IRIX Consoles Only) MOD Drive Verification:

   1. Create a temporary testing file:

      {@hostname} su  -

      Password: <password>

      {root@hostname} dd  if=/dev/urandom  of=/tmp/foo  bs=1024  count=50k

      51200+0 records in

      51200+0 records out

   2. Ensure the temporary testing file was created:

      {root@hostname} ls  -al  /tmp/foo

      -rw-r--r-- 1 root root 52428800 May 10 11:55 /tmp/foo

      (”5242880” represents the file size.)

   3. Calculate the checksum for the local temporary file.

      note:

      These numbers will change every time you generate a new file.

      {root@hostname} sum  /tmp/foo

      45731   51200

      note:

      1st # = checksum (FE should write this down to use for comparison later)

      2nd # = size of file checksum'd

      Checksum    File Size in kilobytes

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

      45731                51200

   4. Insert MOD into SCSI Tower.

      Data on inserted MOD will be destroyed.

   5. Create a filesystem on the target device (MOD) by typing the following:

      {root@hostname} mkfsMOD

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

      *** CAUTION ***

      A filesystem already exists on this MOD.

      This utility will create a new file system on the MOD. In turn it will wipe clean any existing files and data. Make sure you have the correct MOD media in the correct MOD drive.

      Do you wish to proceed? [n] y

      Making file system. This will take approximately 3-5 minutes

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

   6. Mount the MOD:

      {root@hostname} mountMOD

      Mounting MOD

   7. Copy the file to the target device:

      {root@hostname} cp  /tmp/foo  /MOD  &&  sync

   8. Unmount the drive & eject the MOD to ensure the system's cache is flushed. This is required to calculate the checksum properly.

      1. {root@hostname} unmountMOD

         MOD is now unmounted.

      2. Eject the MOD

      3. Reinsert the MOD

      4. Remount the target device, using mountMOD.

   9. Generate checksum on file in MOD drive:

      {root@hostname} sum  /MOD/foo

      45731 51200

   10. Verify (compare) the file's checksum calculated by the host console matches the checksum calculated by the drive.

   11. {root@hostname} unmountMOD

       MOD is now unmounted.

   12. Eject the MOD

1. Record Autovoice Volume control settings (ALT-F3 by Toolchest, upper right corner).

2. Write down all of the system INFO information on the reconfig screens, including the network information (use the appropriate information sheet, found in GRE/Xtream Operator Console Information Sheets). You cannot restore the INFO file during the Load from Cold on the new console.

3. Verify and record specific system hardware configuration.

   1. Open a shell and type the following:

      {ctuser@hostname} cat  /usr/g/config/INFO

   2. Record screen information in Console Information Sheets.

      For an example output, see Example Config/INFO Output.

4. If the console has Connect Pro installed, write down the information when you run installhisris so it can be entered on the new console when installing the Connect Pro option.

5. With Application Software UP, record gantry revolutions and tube usage:

   1. Launch Common Service Desktop.

   2. Record the Next Patient Exam Number.

   3. Capture gantry revs located in the upper right corner of the Home Page.

      This value will be entered after “Restore System State”.

   4. For each tube, record Tube Usage mAs, Tube Model #, Tube Serial #, and Tube Install Date.

      For the current tube, also record Housing Name, Housing Serial #, and Tube Name.

      1. Select Common Service Desktop.

      2. Select Error logs.

      3. Select Tube Usage.

         

      4. Select Summary and record the information.

         

      5. Go back and select Details to record Scan Seconds.

         

      6. Do this for all tubes listed.

      7. Close the window.

6. Close the Service Desktop window in the upper left corner of the screen.

If your system does NOT have “Exam Split” option, skip this section.

Perform these steps before powering down your current GOC2, GOC3 or GOC4 Operator Console:

1. Open a Unix Shell and type the following:

   1. {ctuser@hostname} su  –

   2. Password: <password>

   3. [root@hostname] ls  –l  ~ctuser/ves/.hesMode

      note:

      There are no spaces in the phrase ~ctuser/ves/.hesMode

2. Examine the results.

   • If the results are similar to:

     -rw-r--r-- 1 ctuser users 0 Apr 3 12:43

     /usr/g/ctuser/ves/.hesMode

     Then HES (Hard Exam Split) mode is configured.

   • If the results show ‘No such file or directory’, then VES (Virtual Exam Split) mode is configured.

3. Record Exam Split Mode (Hard or Virtual). This info will be used during the LFC Options Installation.

4. Close the Unix Shell

Systems upgrading from software 04MW44.9 or previous versions will need to rebuild the HIPAA files. Before proceeding, record the User Names (that operators log in as), groups, and permissions used. User passwords will need to be reset after the software load.

notice Two “Save System State” MOD procedures must be performed: You must save the system state onto your original system state MOD, label it appropriately, and keep it in a secure place. You must then save the system state onto a new MOD. This MOD will be used for the rest of this SW LFC.

Perform the following steps on the IRIX console before powering down and installing the GRE/Xtream Operator Console.

1. Save System State (twice) to an MOD on the IRIX console before installing the new GRE/Xtream Operator Console.

   1. Insert the MOD into the SCSI Tower MOD drive.

   2. Select: Service Desktop.

   3. If reloading software, select: UTILITIES. If upgrading from earlier version software, select: PM.

   4. Select: System State.

   5. Select ALL to save all data.

   6. Select SAVE.

   7. If applicable, select OK when the following message appears: System State Media Status: Please insert a DVD or MOD into the drive and press Save again.

   8. When completed select DISMISS.

   9. For the original MOD, label the MOD as “Final IRIX Conversion Release”.

   10. Repeat Steps a-j, for the second “Save System State”, using a new MOD, and label with the same SW release that is found on the DVD label.

2. Modify System State MOD

   1. Insert System State MOD into the drive.

   2. Open a Unix Shell and type the following:

      1. {ctuser@hostname} su  –

      2. Password: <password>

      3. [root@hostname] mountMOD

      4. [root@hostname] cd  /MOD/service_mod_data/system_state

      5. [root@hostname] chmod 666 *bb .epdlog

         (change permissions on tube usage & edit patient data files)

      6. [root@hostname] rm  -f  *.stats

         (removes runtime stats on non-HPOWER systems)

      7. [root@hostname] rm  -f  iipBackupGen2.tar.Z

         (removes IIP “tar ball” files à not used by new IIP)

      8. [root@hostname] rm  -f  Voxtool.prefs

         (removes Voxtool preferences ⇒ new Voxtool application uses new set of preferences)

      9. [root@hostname] rm  -f  smartscore.tar.gz

         (removes SmartScore files ⇒ SmartScore not applicable to PathFinder / not supported by PathFinder software)

      10. [root@hostname] rm  -f  vxtlBackup.tar

          (removes VoxTool files ⇒ new Voxtool application uses new set of files)

      11. Remove VoxtoolPrefs/* and CT_PerfusionPrefs/* files

      12. [root@hostname] rm  -f  movierx*

          (removes Direct 3D preferences that the customer cannot edit)

      13. [root@hostname] rm  -f  *.flm

      14. [root@hostname] rm  -f  *.pro

      15. [root@hostname] rm  -f  *.vrp

      16. [root@hostname] rm  -f  *.adv

      17. [root@hostname] rm  -f  *.adv.research

      18. [root@hostname] rm  -f  *.disp

      19. [root@hostname] rm  -f  *.disp.research

      20. [root@hostname] cd

      21. [root@hostname] unmountMOD

   3. Close the Unix Shell.

3. Go to Install GRE/Xtream Console

notice Two “Save System State” DVD procedures must be performed: You must save the system state onto your original System State DVD, label it appropriately, and keep it in a secure place. You must then save the System State onto a new DVD. This DVD will be used for the rest of this SW LFC.

Perform these steps before powering down your current GOC2, GOC3 or GOC4 Console:

1. Insert the DVD-RAM into the SCSI Tower DVD drive.

2. Select Service Desktop

3. If reloading software, select: UTILITIES. If upgrading from earlier version software, select: PM.

4. Select System State

   note:

   System State Save may be under Utilities or PM.

5. Select ALL to save all data.

6. Select SAVE

7. If applicable, select OK when the following message appears: System State Media Status: Please insert a DVD or MOD into the drive and press Save again.

8. When completed select DISMISS.

9. For the original DVD, label the DVD as “Linux System State Backup”.

10. Repeat Steps 1-8, for the second “Save System State”, using a new DVD, and label with the same SW release that is found on the DVD label.

11. Close the Service Desktop window in the upper left corner of the screen.

12. Sites performing the next sub-section should not remove the DVD-RAM from the SCSI Tower DVD-RAM drive.

Determine type of Host computer:

1. Remove the console front cover and look at the front of the Host Computer for host type.

2. Open a shell and type: hinvEnter

   You will see one of the following:

   (For HP8000) CPU: GenuineIntel Intel(R) Xeon(TM) CPU 2.66GHz

   (For HP8200) CPU: GenuineIntel Intel(R) Xeon(TM) CPU 3.20GHz

Refer to software version recorded earlier in Software Related Prerequisites.

Using the information gained from the above two sections, follow the flowchart below, to determine whether or not you need to perform the BIOS Setup.

(Clicking on the blue boxes will advance to the proper section of this document.)

Figure 2. BIOS Setup Decision Tree

1. Determine Host Computer BIOS version

   1. Open a Unix Shell and halt the system:

      1. {ctuser@hostname} halt

      2. The Operator Console monitor will display a System halted message when it is acceptable to power OFF the Operator Console.

      Power Operator Console ON at the front switch.

   2. At the hp invent screen on the monitor, press F2.

   3. Verify the Main menu screen is displayed.

   4. View BIOS Version, and verify it is JQ.W1.13US or greater.

      • If it is the correct version, go to Set Up the xw8000 Host BIOS - Main Setup Screen

      • If it is NOT the correct version, proceed with Step 2 (below).

2. Remove Operator Console front cover.

3. Insert BIOS floppy disk in Host Computer.

4. Reboot Host Computer. (Front power button on Host computer.)

5. When the BIOS Setup Utility screen is displayed, select Option A, Flash BIOS by typing A and pressing the Enter key.

   The BIOS will begin to load from floppy. Allow the BIOS to load completely.

6. Reboot, press any key.

   The “Press any key to reboot” message will be displayed when the BIOS-flashing is complete.

   Remove BIOS floppy disk from the drive to prevent boot-up from floppy.

7. Press F2 to interrupt the boot-up sequence to edit BIOS settings.

Changes can be made by cursor-selecting the parameter, then using the “+” and “-“ buttons to toggle its value.

The Main setup screen is shown in Figure 3. Confirm that all parameters are set as shown.

Figure 3. Main Setup Screen

1. From the Main Menu screen, use arrow key to select (move to) Advanced to view the Advanced setup screens.

2. The Advanced BIOS setup screen is shown below. The BIOS components that will be updated in the next steps are highlighted.

   

3. From the Advanced Menu screen, use arrow key to select (move to) Processors and press Enter.

4. Set all Processors parameters as shown below.

   

5. When Processors setup is complete, press Esc key to return to the Advanced menu.

6. From the Advanced Menu screen, use arrow key to select (move to) PCI Slot 1 and press Enter.

7. Set all Advanced-PCI Slot 1 parameters as shown below.

   

8. When Advanced-PCI Slot 1 setup is complete, press Esc key to return to the Advanced menu.

9. From the Advanced Menu screen, use arrow key to select (move to) PCI Slot 2 and press Enter.

10. Set all Advanced-PCI Slot 2 parameters as shown below.

    

11. When Advanced-PCI Slot 2 setup is complete, press Esc key to return to the Advanced menu.

12. From the Advanced Menu screen, use arrow key to select (move to) PCI Slot 3 and press Enter.

13. (For Adaptec) Set all Advanced-PCI Slot 3 parameters as shown below.

    (For QLogic) Device Vendor and Card Vendor will read 1077H. Set all Advanced-PCI Slot 3 parameters as shown below, EXCEPT Option ROM Scan, which should be set to [Enabled].

    

14. When Advanced-PCI Slot 3 setup is complete, press the Esc key to return to the Advanced menu.

15. From the Advanced Menu screen, use arrow key to select (move to) PCI Slot 4 and press Enter.

16. Set all Advanced-PCI Slot 4 parameters as shown below.

    

17. When Advanced-PCI Slot 4 setup is complete, press Esc key to return to the Advanced menu.

18. From the Advanced Menu screen, use arrow key to select (move to) PCI Slot 5 and press Enter.

19. Set all Advanced-PCI Slot 5 parameters as shown below.

    

20. When Advanced-PCI Slot 5 setup is complete, press the Esc key to return to the Advanced menu.

1. From the Main Menu screen (shown below), use arrow key (move) to select Power.

2. Setup POWER as shown below.

   

3. When POWER setup is complete, press the Esc key to return to the Main menu.

1. Setup BOOT: From the Main Menu screen, use arrow key to select (move to) Boot.

2. Set all Boot parameters as shown below.

   

3. Arrow-select (move) to Boot Device Priority and press the Enter key.

4. Setup BOOT DEVICE PRIORITY as shown below.

   

   note:

   The CD-ROM Drive may be missing. Ignore this.

   note:

   The ! key disables/enables devices.

5. When BOOT DEVICE PRIORITY setup is complete, press the Esc key to return to the Main menu.

6. Save BIOS settings as shown in the two figures below.

   1. From Main menu, arrow to (move to) EXIT.

   2. Select Exit Saving Changes and Enter key.

      

   3. Select YES and Enter key to “Save configuration changes and exit now”.

      

Host BIOS setup is complete.

1. Remove the GRE/Xtream Operator Console's front cover.

2. Remove the Hospital Backbone Ethernet cable from the Console Bulkhead Assembly, located at the rear of the Operator Console.

3. Insert the OS disk into the DVD-ROM drive on the Host Computer. See the following illustration.

   

4. Select one of the following methods to re-power the Operator Console:

   1. If Applications are up:

      1. Select the Shut Down button.

         

      2. Select Restart then OK to restart the system.

         

   2. If Application Software is down, at the toolchest open a Unix Shell and type:

      1. {ctuser@hostname} halt

      2. The Operator Console monitor will display a System halted message when it is acceptable to power OFF the Operator Console.

      3. Power OFF the Operator Console at the front panel switch.

         

      4. Wait 30 seconds to allow the disk drive to settle; then power ON the Operator Console at the front panel switch.

5. As the computer restarts, the booting process messages appear. After the booting process completes, the boot: prompt appears.

6. At the boot prompt, type the following depending on system type:

   (For English Keyboard only) GEHC2 Enter

   (For International Command only) iGEHC2 Enter

   note:

   The Console Operating System load takes approximately 15 minutes. If the boot: prompt does not appear, then either the DVD-ROM is bad or the Console Operating System DVD is not installed in the drive. Typing GEHC will result in both scan and display being on one monitor and require a LFC.

7. After the OS is loaded, a red button appears and displays Reboot.

8. Remove the OS disk, when it ejects.

9. Press ENTER to reboot.

10. The Host Computer reboots.

    note:

    Do not insert the Application disk into the Host Computer until the system reboots and the [root@localhost] window appears, displaying the [root@localhost root]# prompt.

There is a single Application DVD used for both the Host Computer and the DARC. All applications software will be loaded to the Host Computer during this process.

notice FAILURE TO INSTALL THE CORRECT APPLICATION SOFTWARE AND SELECT THE CORRECT SYSTEM DAS HARDWARE CONFIGURATION WILL RESULT IN SYSTEM DOWNTIME AND DCB CIRCUIT BOARD REPLACEMENT. (THIS FAILURE WILL OCCUR AFTER THE FLASH DOWNLOAD PROCEDURE FLASHES THE FIRMWARE.)

1. After the Host Computer reboots, verify that the window appears with the [root@localhost root]# prompt.

   

2. In the root@localhost Window, verify the SCSI Tower MOD and DVD are present:

   [root@localhost root]# cat  /proc/scsi/scsi

3. Insert the Application DVD into the DVD-ROM drive on the Host Computer. See the illustration below.

   

4. After approximately 15 seconds a pop-up box appears:

   

5. Select Yes.

   note:

   If the pop-up box Question does not appear after two minutes, type the following and wait approximately one minute for the pop-up box to appear.

   mount  /mnt/cdrom Enter

   /mnt/cdrom/autorun Enter

6. After approximately 15 seconds, an Installation Utility window appears. (See illustration, below.)

   

7. Select Load. A prompt message appears asking if you wish to load the INFO file from the System State DVD.

   

8. System State DVD:

   • If you do NOT have a System State or the System State is unusable, select No.

   • If you have a System State DVD, select Yes. When prompted, ensure the System State DVD is in the DVD drive in the SCSI Tower (on top of the console), and then select ok.

     

     An “unMount media” pop-up may appear. No action is required.

9. Select the System tab.

   See example System Settings screen, below.

   

10. Verify that the Next Patient Exam # on the System Settings screen is the value restored from Save System State. Otherwise, set to 1.

11. Verify that the proper Time Zone is selected

    Select/enter information as required for your system configuration.

12. Select the Preferences tab.

    See the illustration below, for an example Preference Settings screen.

    

13. Select the units for patient weight.

14. Select Language: (English or other).

15. Select Preferred FastCal KV - select the kV to be calibrated during FastCal. These kVs should include all kVs that the site uses for patient scanning.

16. Select Target Noise Index Table.

    (Default is Table 2.)

17. Verify proper Date Format is selected.

18. Verify proper Time Format is selected.

19. Select AutoVoice Language.

20. Verify Modified in Room Start is set to Off. Sites in Japan must be set to On.

21. Set HIPAA Present to OFF unless the customer requests HIPAA to be ON.

22. Select the site preferred Dose Information Display option for the site to use in monitoring calculated Patient Dose (on view edit screen):

    Select ON (full DOSE Display) or previous Customer setting.

    note:

    A scroll bar below this menu may be present. It contains the System Information from the INFO file System State.

23. Select the Hardware tab.

24. Select Hardware Parameter Selection.

    An example Select Hardware Configuration screen is shown below.

    

    note:

    FAILURE TO INSTALL THE CORRECT APPLICATION SOFTWARE AND SELECT THE CORRECT SYSTEM DAS HARDWARE CONFIGURATION WILL RESULT IN SYSTEM DOWNTIME AND DCB CIRCUIT BOARD REPLACEMENT. (THIS FAILURE WILL OCCUR AFTER THE FLASH DOWNLOAD PROCEDURE FLASHES THE FIRMWARE.)

    Select your System types HW Parameters, and close this window.

25. On the Hardware Settings screen, the Number of IGs is set to 1.

    

26. Select the Network tab.

    See example Network Settings screen, below.

    

27. Configure Network Settings:

    1. Suite Name: Add your name here.

       note:

       The Suite Name must start with a letter, followed by 3 alphanumeric characters. Total must be four characters long. The name of the OC interface is <Suite Name>_oc within the scanner's subnet. It is suggested that you choose CT01 as its name, unless a different Suite Name is required.

    2. Host Name: Add your host name here.

       note:

       The Host Name identifies the hostname and AE Title of the scanner. It:

       • MUST NOT be <Suite Name>_oc or <Suite Name>_OC.

       • MUST NOT exceed 16 Characters.

       • MUST only contain the following characters: a through z, 0 through 9, - and _

    3. IP Address - Site supplied address.

    4. The following procedure should be performed if your customer Ethernet hospital backbone begins with 172.16.0.xx, OR if the scanner will connect to a device with an IP address of 172.16.0.xx.

       1. If hospital backbone starts with 172.16.0.xx and this is a first time install, continue and complete the software load on the HOST and DARC. When the DARC applications load is complete the DARC subnet can be changed by running “reconfig”. During reconfig, check the Change DARC subnet box, and enter the following value: 169.254.0

       2. If the hospital backbone starts with 172.16.0.xx, and the DARC subnet was already changed, continue and complete the software load on the HOST and DARC.

       3. If the DARC subnet was already changed and needs to be set to the 172.16.0 subnet continue and complete the load on HOST and DARC and run reconfig to change the DARC subnet.

    5. Net Mask - Site supplied address.

       note:

       If the hospital backbone IP address is 192.9.220.xx, then the Net Mask must be set to 255.255.255.252.

    6. Broadcast Address - Site supplied address.

    7. Default Gateway - Site supplied address.

       note:

       Make sure the NUM LOCK button on the keyboard is not active. If it is, deselect it to enable the ACCEPT button in the next step. Failure to deactivate the NUM LOCK results in load issues.

    8. If your customer has AW Direct Connect, then select Enable AW DirectConnect?. Complete the LFC, making certain to configure this feature in AW Direct Connect. (Do not configure AW Direct Connect now.)

    9. If there is an Internal Option - Internal Subnet setting displayed and checked, then un-check it. (This option might not appear on your system.)

    10. Verify with customer’s network administrator if they have NIS. If they do, ensure the Advanced Options and Use NIS? boxes are checked. If they don’t, ensure these selections are not checked.

        1. Domain Name: add your name here (get name from customer’s network administrator).

        2. Enter the IP Address of Internal Server: add your IP address here (get IP address from customer’s network administrator).

    11. If your customer wants to synchronize the system time to their NTP server, then select Enable Network Time Protocol, and enter the Primary Server IP address.

28. Select the ACCEPT button at the right corner of the User Interface.

29. An Install INFO pop-up box is displayed.

    See the following illustration, for a typical Install INFO message (the Install INFO message is different for each system configuration).

    

30. Select yes, if correct, and wait for system to reboot.

    note:

    If the information is not correct, select the NO button. This returns you to the Hardware screen. Select the Hardware Parameters Selection button and select the correct system configuration from the displayed list. Select the Accept button again, followed by the YES button on the Install INFO pop-up to accept the new hardware configuration.

31. The following pop-up message appears:

    Please make sure the CT Application SW is in the drive - the system will be rebooted.

    No action is required for this pop-up. The system will automatically reboot after approximately 10 seconds if the OK button is not selected.

    note:

    Do not remove the Apps DVD from the Host Computer until instructed to do so.

32. As the system reboots, the following shell Installation screen appears and the application software starts loading.

    

33. STOP. When the system prompts you to reboot (after approximately 13 minutes), DO NOT answer Yes immediately.

    Before selecting Yes to reboot, the following command line (next step) must be entered to prevent possible trackball issues in the future. This step should eliminate lengthy downtime due to loss of trackball functionality.

34. In the terminal window that is already open, as root, type the following:

    note:

    X11 = X eleven

    root@hostname cp  /etc/X11/xorg.conf  /etc/X11/xorg.conf.clean

    root@hostname cp:overwrite ‘etc/X11/xorg.conf.clean’? y

    To verify that command was successful, complete the following command and verify that Creation date and size of xorg.conf.clean and xorg.conf are identical to each other. They may be a different size than listed below. You should get a table similar to the one listed below. The bottom two files are not significant.

    root@hostname cd /etc/X11

    root@hostname ls –al xorg.conf*

    Permissions        owner   group      size    Creation date   File Name

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

    -rw-------    1    root    root       2683    Jun  5 14:46    xorg.conf

    -rw-------    1    root    root       2683    Jun  5 14:46    xorg.conf.clean

      

    -rw-r--r--    1    root    root       2212    Apr 13 15:34    xorg.conf.lfc

    -rw-r--r--    1    root    root       2216    Apr 13 15:33    xorg.conf.orig

35. Now reboot by selecting Yes in the window that opened previously. The system is going down for reboot NOW.

    

    note:

    During the reboot of the console, a message may appear to the effect that the system was not able to determine what the tube type was and to run the TIC tool. This message should be ignored.

36. After approximately 3 minutes, a pink pop-up box appears, stating CT Software Auto-Start Disabled. In this box, select OK.

    

37. Press the button on the DVD-ROM drive to remove the Apps DVD from the Host Computer.

Confirm the Host Computer Software type. Output of the following commands MUST BE EXACT.

1. Open a Unix Shell and type the following to see software and hardware Config information:

   {ctuser@hostname} cd  /usr/g/bin

   {ctuser@hostname} swhwinfo

   06MW03.5. <hardware revision info here>

   Example: 06MW03.5.H2_P_S4_G_Zeus

2. Confirm that the swhwinfo results match the software revision shown on the Applications Disk.

   • If the revisions match, continue with this procedure.

   • If the revisions do NOT match, reload the software (Load from Cold Installation Procedures).

3. Type: cat  /GEHC*

   Release: GEHC/CTT Linux 4.3.16

   Built: Tue Jul 12 12:29:10 CTD 2005

4. Confirm that the cat result matches the Operating System version shown on the OS disk.

5. Close the Unix Shell.

1. Insert the “Tube Usage Patch for 06MW03.5,” CD-ROM (p/n 5172979) into the HOST DVD Drive.

2. Open a Unix Shell and type the following:

   1. {ctuser@hostname} su  -

   2. Password: <password>

   3. [root@hostname] mount  /mnt/cdrom

   4. [root@hostname] cd  /mnt/cdrom

   5. [root@hostname] ./install_patch  –p  GEMS-CT-PFM3-TUBEUSAGE-1-1.i386.rpm

      Output from the patch install will state “Installing GEMS-CT-PFM3-TUBEUSAGE-1-1.i386” and end in the text “******POST_INSTALL******”

   6. [root@hostname] cd  /

   7. [root@hostname] umount  /mnt/cdrom

3. Remove the CD from the Drive

4. Close the Unix Shell.

This section describes the steps necessary to change the DARC Node BIOS to enable the OS load onto DARC Node from the Host Computer. The DARC Node Boot Order BIOS is modified before the DARC Node OS load, and must be returned to original settings after the DARC Node OS load for proper normal operation.

1. Open a Unix Shell and type the following:

   1. {ctuser@hostname} su  -

   2. Password: <password>

   3. [root@hostname] service  cliservice  start

   4. [root@hostname} telnet  localhost  623

   5. At Server Prompt type: darc

   6. username Enter

   7. password Enter

      Login successful

   8. dpccli> reset

      ok

      dpccli> console

2. Interrupt the DARC boot process to enter the BIOS Setup mode. When the message “Press <F2> to enter setup” appears, press F2.

   note:

   F2 may have to be pressed many times before BIOS setting screen can be seen. There will be a short delay before the DARC BIOS setup screen is displayed.

   

3. Select Boot Menu, using arrow keys.

4. Highlight Boot Device Priority Menu, then press Enter.

   

5. Highlight 1st Boot Device, then press Enter.

6. A small window will appear with the options available. Using the down-arrow key, scroll down to highlight IBA 1.1.08 Slot 0338, then press Enter.

   

7. Using the down-arrow key, scroll down to highlight the 2nd Boot Device entry. Press Enter.

8. A small window will appear with the options available. Using the down-arrow key, scroll down to highlight the ATAPI CD-ROM entry. Press Enter.

   

9. Using the down-arrow key, scroll down to highlight the 3rd Boot Device entry. Press Enter.

10. A small window will appear with the options available. Using the down-arrow key, scroll down to highlight the Hard Drive entry. Press Enter.

11. Verify the Boot device Priority is set to:

         IBA 1.1.08 Slot 0338

         ATAPI CD-ROM

         Hard Drive

         IBA 1.1.08 Slot 0339

         Removable Devices

    note:

    The removable devices might not be present. This is OK.

12. Press Esc to exit back to Boot menu.

13. Save DARC BIOS settings:

    1. From Boot menu, arrow to (move to) Exit menu.

    2. Highlight Exit Saving Changes, and press Enter

       

    3. Highlight [Yes], and press Enter, to “Save configuration changes and exit now.”

       Wait one minute.

       

    note:

    After saving the DARC BIOS, the DARC BIOS Setup Utility will disappear (within one minute) and the DARC will begin to Reboot. If the BIOS SETUP UTILITY window does not disappear within a minute, perform the steps within this section again.

14. When the darc login: prompt appears, close the Terminal Window.

This process is performed with Applications down.

If the Host Computer is able to successfully remote shell the DARC Node, perform the instructions in this section. Performing the reconfigScanDisk script may cause DARC Node OS load issues. Deleting DARC Node SCSI partitions will prevent DARC Node OS load issues. The reconfigScanDisk script is not a viable/usable script on 06MW03.5 software/hardware and will be removed later in the LFC.

In a Unix Shell, type the following:

1. {ctuser@hostname} su  -

2. password: <password>

3. [root@hostname] rsh  darc

4. [root@darc] umount  /raw_data

   note:

   Some previous DARC Application Software versions may not have mounted /raw_data. In this case, you will see “umount: /raw_data: not mounted” message.

5. [root@darc] parted  -s  /dev/sda  rm  1

   The command contains the number “one”, not the letter “l”.

   note:

   Normally, there will be no output or message displayed after performing the parted commands.

   However, should the following message appear, ignore it and continue.

   Warning: Unable to align partition properly. This probably means that another partitioning tool generated an incorrect partition table, because it didn't have the correct BIOS geometry. It is safe to ignore, but ignoring may cause (fixable) problems with some boot loaders.

6. [root@darc] parted  -s  /dev/sdb  rm  1

7. Close the Unix Shell.

The OS DVD will be used again; however, this time it will be loaded onto the DARC Node from the Host Computer. If any problems arise, verify the correct disk is installed.

1. Place OS DVD into the Host Computer DVD-ROM Drive. (See Illustration, below.)

   

2. Open a Unix Shell and type the following:

   1. {ctuser@hostname} su  -

   2. Password: <password>

   3. [root@hostname] cd  /usr/g/scripts

   4. [root@hostname] ./start_darcOS

   An Attention window appears. See the illustration below.

   

3. Follow the instructions in the Attention window and then insert the Linux Operating System, version 4.3.16 DVD into the Host Computer DVD-ROM Drive.

4. Select OK.

   A sh window displays initial information, followed by a series of four rows of dots.

   sh

   Copying OS packages from the DVD to the HOST’s hard drive. This takes about 10 minutes.………………………………………………………………………….

   ………………………………………………………………………….

   ………………………………………………………………………….

   ………………………………………………………………………….

   note:

   The display of dots reflects the copy process from the Host Computer DVD drive to the DARC Node. This process takes approximately 15 minutes.

5. Once the copy process is complete, the load will begin and the following message will appear:

   OS load has started. This takes about 18 minutes.

   ##.## % done.

   note:

   The DARC OS Load will stop prematurely ONLY if an error is encountered. An Error Dialog Box will appear with a brief description of the error. Select OK after reading the instructions displayed on the Monitor. Refer to DARC OS Load Pop-Up Boxes for additional information on these error pop-up windows. Also, if any problems arise, verify the correct software disk is installed and verify BIOS Setup Utility Boot Order is correct.

   note:

   A %done status is displayed during the DARC OS load. This is only a timed countdown sequence and does not provide status of the actual load process. When the DARC OS load has completed a reboot message will appear.

6. Once the load process is complete, a sh window appears and the DARC reboots:

   Sh

   Waiting for the DARC to boot up…

7. When the DARC OS load has completed, a pop-up message is displayed:

   

8. The OS disk ejects automatically. Remove the OS disk from the drive and close the drive.

9. Select OK.

10. To verify the OS has been loaded on the DARC Node, open a Unix Shell and type the following:

    note:

    If the DARC login prompt [root@localhost root] is not present, then try reloading the DARC Node OS again per the procedure. Always be sure the DARC OS matches the Host OS already loaded.

    1. {ctuser@hostname} su  -

    2. Password: <password>

    3. [root@hostname] rsh  darc

    4. [root@localhost root]

       (If the prompt is displayed exactly as shown, then the login was successful and the DARC OS was loaded properly.)

    5. [root@localhost root] exit

11. This completes the OS load on the DARC.

12. Next: load the DARC Applications in the HP Host Computer. See DARC Application Software Installation from Host Computer.

1. Open a Unix Shell and type the following:

   1. {ctuser@hostname} su  -

   2. Password: <password>

   3. [root@hostname] cd  /usr/g/scripts

   4. [root@hostname] ./start_darc_load

   A shell window pops up and the load begins. A successful load takes 5-12 minutes.

   When the process is complete the load window will disappear.

2. Close the Unix Shell (do not use for the next process).

Overview: The reconfigScanDisk script is not used and must be removed with each LFC. The new script to verify the Disk Array in the SDDA or DARC 2 Node is {ctuser@darc} sudo gre-raid. This script is performed with the option to repartition or create (-c), assemble (-a) or query (-q).

Open a Unix Shell and type the following:

1. {ctuser@hostname} su  -

2. Password: <password>

3. [root@hostname] rsh  darc

4. [root@darc] cd  /usr/g/scripts

5. [root@darc]] ls  reconfigScanDisk

   reconfigScanDisk

6. [root@darc] rm  reconfigScanDisk

   Type y to remove: y

7. [root@darc] ls  reconfigScanDisk

   reconfigScanDisk will be gone.

Close the Unix Shell.

This section describes the steps necessary to change the BIOS on the DARC Node. This step is required to return the DARC BIOS to its original settings, now that the OS has been loaded onto the DARC from the Host Computer. The DARC BIOS was changed at the beginning of the procedure to load the OS onto DARC from the Host Computer, and now will be changed back for normal operation.

1. Open a Unix Shell and type the following:

   1. {ctuser@hostname} su  -

   2. Password: <password>

   3. [root@hostname] service  cliservice  start

   4. [root@hostname] telnet  localhost  623

   5. server: darc

   6. username Enter

   7. password Enter

      Login successful

   8. dpccli> reset  -c

      ok

      GEHC/CTT Linux 4.3.16

      Kernel 2.6.7-2.2 smp...

      See you on the darc side of the moon

      darc login:

      note:

      A slight delay here is normal. Be patient.

2. Interrupt the DARC boot process to enter the BIOS Setup mode. When the message “Press <F2> to enter setup” appears, press F2.

   note:

   F2 may have to be pressed many times before BIOS setting screen can be seen.

   There will be a short delay before the DARC BIOS setup screen is displayed.

   

3. Highlight Boot Menu, using arrow keys.

4. Highlight Boot Device Priority Menu, then press Enter

   

5. Highlight 1st Boot Device, and press Enter.

   

6. Continue setting Boot Device Priority.

   

   

   

7. Verify the Boot device Priority is set to:

        ATAPI CD-ROM

        Hard Drive

        IBA 1.1.08 Slot 0339

        IBA 1.1.08 Slot 0338

   

8. Press Esc to exit back to Boot menu.

9. Save BIOS settings:

   1. From Boot menu, arrow to (move to) Exit menu.

   2. Highlight Exit Saving Changes, and press Enter.

      

   3. Highlight Yes, and press Enter, to “Save configuration changes and exit now.”

      Wait one minute.

      

   note:

   After saving the DARC BIOS, the DARC BIOS Setup Utility will disappear (within one minute) and the DARC will begin to Reboot. If the BIOS SETUP UTILITY window does not disappear within a minute, perform the steps within this section again.

10. When the darc login: prompt appears, close the Terminal Window.

1. When applications are up, open a Unix Shell from the Service icon -> Utilities tab -> Utilities folder. Perform the following:

   1. Insert the IRIX System State MOD into the SCSI Tower MOD drive. The DVD drive should be empty.

   2. {ctuser@hostname} cd  /usr/g/bin

   3. {ctuser@hostname} sysstategui  -MOD  -IRX2LNX

   4. When the system state GUI comes up, select and restore each item individually, by selecting the item and then selecting RESTORE.

      note:

      Continue until all items are restored.

   5. The IRIX to Linux conversion should take around 40 minutes. The command lines will scroll very quickly during the conversion in the window. When the scrolling stops, the System State has completed the conversion. When it has completed, close the window.

2. Shutdown Applications.

3. Close the Unix shell.

4. Remove the MOD from the drive.

5. Proceed toRun Tube Usage Conversion Tool (skip the next sub-section, “Restore System State from DVD”).

1. Open a Unix Shell and verify the SCSI Tower MOD and DVD are present:

   {ctuser@hostname} scsistat

2. Close the Unix Shell.

3. Insert the Save System State DVD into DVD-RAM SCSI Tower drive.

4. Select the SERVICE icon.

5. Select: UTILITIES

6. Select: SYSTEM STATE

7. Select ALL

8. Select RESTORE

9. Verify the overall system state content has restored correctly (look for message “Save/Restore System State Completed Successfully”), then select CANCEL.

   

10. When completed, select DISMISS or close the window.

    note:

    If Scan Hardware Reset question appears - answer [NO]. This reset is performed during FLASH Download Update.

If HIPAA is turned ON, then configure it now. (Refer to HIPAA Configuration) When HIPAA configuration is complete, return to this procedure.

For general information on Product Network Filters, please see Product Network Filter Theory.

If your customer has special network requirements, then proceed to Configure Product Network Filters now. When PNF configuration is complete, return to this procedure.

If the site requires the configuration of AW Direct Connect, then configure it now (see AW Direct Connect). When configuration is complete, return to this procedure.

notice NEVER Use CTRL - ALT - DELETE to reboot the host computer. This technique will NOT reboot all console subsystems, and as such is an unacceptable practice.

To restart the system:

1. Replace the Hospital Backbone Ethernet cable to the Console Bulkhead Assembly (located at the rear of the Operator Console).

2. Open a Unix shell and type the following:

   {ctuser@hostname} reboot

When the system comes up the following screen will be displayed if HIPAA Present was set to On during the LOAD process. Verify the admin screen below has the following 'Select user':

• Select user: admin

• Password: ctAdmin