Normas Y Procedimientos De Auditoria Objetivos de auditoria Objetivos de auditoria

not all covers are in place, dirty filter(s), peripheral cables on cage

∆ 21 or more DELTA–1 WARNING EXHAUST–INTAKE (ambient) UNIT TOO HOT: MESSAGE TO OPERATOR

not all covers are in place

∆ 21 or more DELTA–3 WARNING POWER SUPPLY–INTAKE not all covers are in place

6–4–4 Power Up Log

The Power Up Log records the host’s bootup progress in the form of messages. (See example that starts below.) The messages can act as clues to a power on/bootup problem. When a system hangs during bootup, either the process described in the last message or the process that follows is likely to be the step that the host could not complete.

Installing software cleans the hard drive and begins new Log files. To keep these files at a manageable size they are divided when they reach a certain size. The first Power Up Log (#00) holds the power on and bootup that includes the software installation messages. The default selection for the Power Up Log is the log for the most recent Power Up. To select another Power Up Log, press Esc Esc.

Starting with software version R6.2, software installation may include a low level format of the hard drive. If so, the message: “Correcting Disk, please wait...” appears immediately after the message ”Initializing SCSI driver. . .” This reformatting will add 20 to 40 minutes to the installation process.

LOGIQ 700 Ultrasound General Electric Medical Systems

Board Support Version 2.1 (5.63 DISK) Updated Firmware 46–312590–G01–M

2/2/1997 08:47:10

Initializing Standard output device... Done.

Initializing pNA+... Done.

Note: add_route for 3.28.104.0, gateway 3.28.124.1. failed. Normal Note: add_route for 3.7.56.0, gateway 3.28.124.2. failed. Normal Note: add_route for 3.7.60.0, gateway 3.28.124.3. failed. Normal Note: add_route for 3.28.100.0, gateway 3.28.124.4. failed. Normal Initializing System clock... Done.

Initializing SCSI driver... Done.

The following SCSI devices were found...

Hard Drive ID 0 Vendor: SEAGATE Model: ST3243ON models identified here MOD Drive ID 1 Vendor: FUJITSU Model: M2512A yours may differ NFS path ”/home/isle2” mounted from 3.28.124.3 as volume 99.9.

NFS path ”/home/isle2/mvme/mvme40” is the default NFS directory.

Probing SCSI Bus for Optical Memory Volume... Not Found.

Probing SCSI Bus for Direct Access Volume... Partitioned Drive Found at 5.0.

Mounting Direct Access Partition Number 1... Mount at 5.512.

Mounting Direct Access Partition Number 0... Mount at 5.256.

Checking File System on pHILE+ Volume ”5.512”

Please be patient... Verify complete. No errors Checking File System on pHILE+ Volume ”5.256”

Please be patient... Verify complete. No errors Initializing pSH... Done.

Initializing telnet daemon... Done.

Initializing FTP daemon... Done.

Initializing NFS daemon... Done.

Setting Vector Page ($00000000–$00000FFF) Write Protected.

Setting BSP Copy ($01E00000–$02000000) Write Protected.

Setting BSP’s Code ($00012000–$0004BF3E) Write Protected.

Starting Application...

Looking for SS Board ... FOUND Looking for VP Board ... FOUND Looking for XY Board ... FOUND Looking for ALM_CT Board ... FOUND Looking for TLM Board ... FOUND Looking for CALM_CT Board ... FOUND Looking for CINE Board ... FOUND Looking for BMP Board ... FOUND Looking for DP Board ... FOUND Looking for CFP Board ... FOUND Looking for PIA Board ... FOUND Probing for Beamformer boards...

Looking for FECB Board ... FOUND Looking for EQ Board ... FOUND Looking for SYTM Board ... FOUND Performing Config Mgr init ... done Looking for TD Board 15 ... FOUND Looking for TD Board 14 ... FOUND Looking for TD Board 13 ... FOUND Looking for TD Board 12 ... FOUND Looking for TD Board 11 ... FOUND Looking for TD Board 10 ... FOUND Looking for TD Board 9 ... FOUND Looking for TD Board 8 ... FOUND Looking for TD Board 7 ... FOUND Looking for TD Board 6 ... FOUND Looking for TD Board 5 ... FOUND Looking for TD Board 4 ... FOUND Looking for TD Board 3 ... FOUND Looking for TD Board 2 ... FOUND Looking for TD Board 1 ... FOUND Looking for TD Board 0 ... FOUND Number of TD Boards Found = 16 Beamformer initialization complete going into calm_init

going into bm_init going into dp_init going into dp_actm_init going into sc_xy_init going into cf_init going into pnl_init going into cine_init leaving sys_init

Setup sys params... Done

R6.2 at Feb 2 1997 09:29:54 Last item reported is Software Rev and Creation time

6–4–5 System Configuration Log

Note

After running disruptive tests, the System Configuration software may be unable to correctly read EEPROMs. If READ errors occur here, exit diagnostics, regain access to gemsC, then ‘View’ the Configuration Log BEFORE you enter the ‘Diagnostics’ menu bar choice.

Description. There are five pages to this log:

Log Page 1: General Information

Log Page 2: FRU Model and Serial Numbers

Log Page 3: TD board A/D hardware parameters and TD cable type Log Page 4: Probe Model and Serial Numbers

Log Page 5: System Model and Serial Numbers (stored on backplanes)

The System Configuration Log is the place to find data about the system software and hardware. The log holds model and serial numbers of all major parts and Service information. Part and serial numbers are burned into Electrically Erasable and Programmable Read Only Memory (EEPROM) on the Field Replaceable Unit (FRU) at the factory.

There are other fields to be seen also. The MC queries the circuit boards’ IIC EEPROM whenever you start the system or diagnostic software, or request the Configuration Log.

Bad Data. The Log reports the numbers as BAD if they don’t conform to an expected format. Part Numbers come in two formats: the traditional ‘46–’ and the new ‘G ’ for Global Item Master that starts at 2 million. Part Number can also mean Model Number. A Bar Code reports a part’s serial number. Look at the FRU’s labeling and bar code for the actual data.

Key Elements. MC, VMEbus, SS, FECB, CPU control cable, EQ (FE controller), VP (BE controller), and an InSite EEPROM on each major circuit board and probe are the hardware parts that enable system configuration checking.

Accessing the System Configuration Log. To access the System Configuration Log you must be at the top level Diagnostic menu bar. See page 6–26. Use [Esc][Esc

]