NonStop NS-Series Operations Guide (H06.12+)

3. Monitor the dump to make sure that it finishes successfully:
a. Wait for this message to appear:
CPU n has been dumped to dumpfile
b. Check the size of dumpfile to verify that the end-of-file pointer (EOF) is not equal to
zero.
> FUP INFO dumpfile
When a processor is dumped to disk, the RCVDUMP utility begins copying the dump
in a compressed format from the specified processor into a disk file called dumpfile.
If dumpfile does not exist, the RCVDUMP utility creates it. As the dump proceeds,
the status of the processor being dumped changes in the Processor Status dialog box to
indicate that a dump is in progress. When the dump is finished, the status of the selected
processor in the Processor Status dialog box changes to indicate the completion of the
dump.
Blade Element Reintegration
Whether TFDS or RCVDUMP was used to dump the PE for an individual Blade Element,
reintegration should take place automatically upon completion of the dump. The OSM Service
Connection has a Reintegrate PE action, located under the Processor Components object, in case
the automatic reintegration fails.
Troubleshooting and Recovery Operations for Disk Dumps
If a message indicates that the dump was not successful, repeat Dumping a Processor to Disk
on page 9-13 using the other ServerNet fabric.
If a halt code for the selected processor appears in the Processor Status dialog box of the OSM
Low-Level Link, look it up in the Processor Halt Codes Manual for further information about the
cause of failure and the appropriate recovery procedure.
Backing Up a Processor Dump to Tape
Back up a processor dump to tape from the compressed disk file generated by the TACL
RECEIVEDUMP command (or the RCVDUMP utility):
1. Follow the instructions in “Dumping a Processor to Disk” (page 116).
2. Use the BACKUP utility to copy the processor dump to tape, as described in Section 10, Disk
Drives: Monitoring and Recovery.
3. See “Submitting Information to Your Service Provider” (page 119).
Replacing Processor Memory
Processor memory is field-replaceable for all Integrity NonStop systems. Call your service
provider. If memory units cannot be replaced, the memory board must be replaced.
If the Service State attribute of a Blade Element object is not OK (see “Monitoring Processor
Performance Using ViewSys” (page 108)), the memory board might need to be replaced. Contact
your service provider.
Replacing the Processor Board and Processor Entity
Processor boards and entities are field-replaceable for all Integrity NonStop systems. Call your
service provider.
118 Processors and Components: Monitoring and Recovery