• Aucun résultat trouvé

A7.0 B.fC.D.tiEliU&iIIDtI

Dans le document this document. (Page 78-82)

A7.1 As.s.UlJellgtl~

8lt/03/1Z

1. The reader is already familiar with the NOS/VE Installation and deadstart process but Is not 'amll'.r with what to do In particular 'allure situations.

2. The system analyst will look at the MOO display for falture Information In the event of a system f.llure. If the system has not failed but peripheral faltures are suspected, the systeM analyst will .ook at the Engineering Log for failure infor.atlon.

3. The site has generated a deadstart tape with the specified physical and lo:gical configurations as depicted below. Unless otherwise specified, assume the sIte has Installed NOS/VE, has been running the system, has permanent fltes on disk and has backup tapes of the permanent files.

If the performance of the system Is degrading and there is an MDO console, see If unrecovered disk fallure(s) have been reported.

Alternatively, use the

DISPLAY_BINARY_lOG

comm.nd to determine whether unrecovered disk/tape 'allures have been reported In the Engineering Log.

The first alternative to consider when a peripheral fa' lure is suspected Is to terminate NOS/VE (If stl II runnIng) and revert to NOS (single-state execution). When NOS/VE Is terminated, all devices remain DOWN In the NOS configuration. Therefore "ALET may be used on NOS to isolate and repair peripheral hardware problems. If the prob'e. Is a hardware logIc failure and Is repelred, one should be able to perform a continuation deadstart and resume norma. operatIon. If this alternative Is not chosen and the failing element is the system deadstart control'er or disk drive. any mod'fled date In NOS/VE real memory at the time of the tallure ~III be lost.

If repair will take too long or files MI11 be lost as a result of the failure, the dIscussion below Is pertJnent.

Note that the disk and tape units are only accessible from one controller. This Is not a recommended configuration from the standpoints of fault tolerance and system performance. Compare the following scenarios Mlth those of conflguraton '2.

channet 0 channel 2 channel 6

COMPANY PRIVATE

-A7.0 RECONFIGURATION

A7.3 CONFIGURATION '1 - SINGLE CONTROLLER

• •

4---A7.3.1 OISK R£CONFIGURATION SCENARIOS

:

conrl~uratlon, I.e. the INSTAll_LOGICAL_CONfIGURATION subcommand of the LOGICAL_CONFIGURATION_UTILITY (leU) should 'exclude' the 'ailing element. In addition the con'lguratlon prolog may need to be changed If It Mas set up to INITIALIZE_HI_VOLUME and ADD_VOLUME_TO_SET for the failing element; these subcommands must be deleted.

b. Perform an 'Init.11.tlon deadstart' of NOS/VE. re-Install the logical configuration to 'Include' the repaired element. Note that the new'y Installed logical confIguration Mtll not become actiye until the next continuation deadstart.

r.

When convenient do a TERMINATE_SYSTEM and then a continuation deadstart. This will activate the logical configuration Installed above.

NOS/YE (CYCLE 18)

NOS/VE Peripheral Maintenance and Support A7.0 RECONFIGURATION

A7.3.1 DISK RECONFIGURATIOH SCENARIOS

84/03112

g. Execute the leU to INITIALIZE_HS_YOLUME and ADD_VOlUME_TO_SET for the repaired element.

h. Reload any permanent files not previously reloaded. SET_DEADSTART_DEVICE systeM-core command must be changed to reflect the type of unit and the unit-number (1) for the new 51st •• disk. The configuration prolog must also be rebuilt.

The new prolog should hav. the failing device (0) in the physical configuration but not In the loglca' configuration, i.e. the INSTALL_LOGICAL_CONfIGURATION subcommand of the LeU should 'exclude' the tailing element. In addition the configuration prolog may need to be changed If It was set up to INITIALIZE_MS_VOlUKE and ADD_VOLUME_TD_SET for the neM system deylce; these subcommands must be deleted. re-install the logica' configuration to 'Include' the repaired element.· 8Mote th:at the neNly Installed logical confIguration Hili not become active until the next continuation deadstart.

e. When convenient do • TERMINATE_SYSTEM and then 8 continuation deadstart. This Nill activate the logical conf1guratlon Installed above.

f. Execute the LeU to INTITIAlIZE_"S_VOLU"E and ADD_VOLUME_TO_SET for the repaired element.

g. Reload any permanent files not pr~vlous'Y reloaded.

the INSTALL_LOGICAL_CONFIGURATION subcommand of the LOGICAL_CONFIGURATION_UTILITY (leU) should 'exclude- the 'ailing element. In addition the Initialization prolog may need to be changed If It was set up to INITIAlIZE_HS_VOLUHE and ADD_VOLUME_TO_SET for the failing device) these

COMPANY PRIVATE

-Perlphera' and Support A7.0 RECONFIGURATION

A7.3.1 DISK RECONFIGURATION SCENARIOS subcommands must be deleted.

b. Perform an 'Instal •• tlon deadstart' of NOS/VE configuration will not become active contInuation deadstart.

continuation deadstart. This w.11 activate the logical confIguration installed above.

f. Execute the leU to INITIALIIE_HS_VOLUME and ADD_VOLUME_TD_SET tor the repaired element.

g. Reload any permanent files not previously reloaded.

h. Continue with norma' 51ste. operation.

4. Assume the controller on channel '0 requires repair and that the repair will take too long. The desIred result Is to delete the failing controller from the configuration and continue degraded operation with the single contro'ler on channel '2. configuration. The SET_DEADSTART_CONTROLLER sYstem-core command may need to be changed I' the controller on channel

t. Continue degraded system operation.

g. When the 'ailing controller has been repaired, use the INSTALL_PHYSICAL_CONFIGURATION subcommand of the PHYSICAL_CONFIGURAT.ION_UTILITY to re-install the orlglna' physical configuration. Note that the newly Installed physical configuration NIJt not become actlYe until the next continuation deadstart.

h. When convenient do a TERMINATE_SYSTEM. Ree.bllno cannot occur whl.e the NOS/VE system Is executing.

I. Recable to match the Instatled physical configuration.

j . Perform a continuation deadstart.

k. ContInue with normal system operation.

NOS/VE (CYCLE 18)

NOS/VE Peripheral Maintenance and Support

A1.~ RECONfIGURATION

A7.3.1 DISK RECONFIGURATION SCENARIOS

84103/12

e. Continue degraded system operation.

r.

When the failing controller has been repaired, use the

INSTALL_PHYSICAL_CONFIGURATION

subco_mand of

the PHYSICAL_CONfIGURATION_UTILITY

to

re-jnste ••

the original physical configuration. Note that the newly Inst.lled physical configuration does not beeo •• act've untIl the next contInuation deadstart.

g. When convenient do a TERMINATE_SYSTEM. Reeabtlng cannot occur whJle the NOS/YE system is executing.

h. Recable to match the Installed physical configuration.

I. Perform a continuation deadstart. This

w."

activate the physlca' configuration Installed abov~.

J. Continue with norma. system operation. scenarios concerning a failing disk drive.

b. Remove the disk pack tHOA) from drive .1 and mount It on the spare dr iva.

c.

Perform a

continuation deadstart

and request

operator Intervention.

d.

FroM wIthin the

LeU

use the

INSTALL_LOGICAL_CONFIGURATION

Dans le document this document. (Page 78-82)