Generic | Microcode Download |
|
|
|
|
|
|
|
|
|
|
|
| |||
This | service | aid | provides a | means | of | executing a | "generic" | script | from a | diske | ||||||
The intended purpose for this "generic" script is | to load microcode to a suppor | |||||||||||||||
resource. This script is responsible for executing | whatever | program | is | required | ||||||||||||
order | to | download | the microcode onto | the | adapter | or | device. |
|
|
| ||||||
This | service | aid | is supported in both concurrent | and | standalone modes | from | disk, | |||||||||
LAN, | or | loadable | media. |
|
|
|
|
|
|
|
|
|
| |||
On entry, the service aid displays information about | what it does. It then asks | |||||||||||||||
Genucode diskette to be inserted into the diskette | drive. The diskette must be | |||||||||||||||
format. The service aid then | restoresgenucodethe scriptto the/tmpfiledirectory. |
|
|
| ||||||||||||
Then | the | script | is | executed. | The | script | must at | that point | then pull | off | any ot |
needed files from the diskette. The script should then exec whatever program is
necessary in order | to | perform its | function. On completion, a status | code | is | retu | ||||
and the user is returned to the genucodeservice scriptaid.Theshould have a # ! |
|
| ||||||||
/usr/bin/ksh | line | at | the | beginning | of | the file. Return status | of 0 | should | be | ret |
the program | was | successful, else | a | returned. |
|
|
Local Area Network Analyzer
This selection is used to exercise the LAN communications adapters
Ÿ | Connectivity testing | between | two network stations. Data is | transferred | between | |||||||
| the | two | stations. | This | requires the user | to input | the | Internet | Addresses of | |||
| stations. |
|
|
|
|
|
|
|
|
|
| |
Ÿ | Monitoring | ring | monitored | for | a | period | of | time. | ||||
| Soft | and | hard errors | are | analyzed. |
|
|
|
|
|
|
Periodic Diagnostics
This | selection | provides | a | tool | for | configuring | periodic | diagnostics | and | automatic | |||||||||||
log analysis. A hardware resource can be chosen to be tested once | a | day, | at | ||||||||||||||||||
specified | time. | If the | resource | cannot | be | tested | because | it | is | busy, | error | ||||||||||
is | performed. Hardware | errors | logged | against | a resource can also be | monitored b | |||||||||||||||
enabling | Automatic | Error | Log | Analysis. | This | allows |
| error log analysis to be | performed | ||||||||||||
every time | a | hardware | error | is put | into the | error | log. If | a | problem | is dete | |||||||||||
message | is | posted to | the | system | console | and | a mail message sent to | the | user(s) | ||||||||||||
belonging | to | the | system | group | with | information | about the | failure such | as | the | Ser | ||||||||||
Request | Number. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |||
|
|
|
|
|
|
|
| Chapter | 9. Introducing | Tasks | and | Aids |
|
|
|
|
|