3 failure information detection, 1 logon failure is recorded in operation log, 2 dump file is created – Hitachi GR2000 Series User Manual

Page 175: 3 failure information detection -9, 1 logon failure is recorded in operation log -9, 2 dump file is created -9

Advertising
background image

Troubleshooting

GR2K-GA-0015

7-9

Ver. 07-02

7.3

Failure information detection

7.3.1

Logon failure is recorded in operation log

Confirm the contents of a log message referring to Chapter 5, in the GR2000
Operations Log and MIB Reference, when the logon a failure is recorded in an
operation log.

7.3.2

Dump file is created

Perform the operation below when the dump file of RM, RP, or NIF is collected in a
dump file storage directory (/primaryMC/var/dump). See Chapter 2 in the GR2000
Operations Log and MIB Reference.

1. Confirm the creation time of a file

Execute ls -l to confirm the time at which the file was created.

Figure 7-2 Confirmation of dump file creation time

2. Examine the reason the file was created.

Execute a show logging command and confirm the contents of a log message at
the time the file was created referring to Chapter 5, in the GR2000 Operations
Log and MIB Reference.

Figure 7-3 Confirmation of log message during dump file creation

3. Collect failure information

Execute a show tech-support command to collect failure information when a
dump file is created due to a failure (See Section 8.1, “Acquisition of failure
information
” for more details).

4. Save a file

Save when a dump file is required for failure analysis. See Section 8.2,
“Transmission of Maintenance Information
”, when saving a dump file in the
console or remote operation terminal. Execute a cp command when saving a
dump file in reserved MC.

5. Delete a file

Execute an erase dumpfile command to delete the file when a dump file is not
required during termination of failure analysis.

> ls -l /primaryMC/var/dump

total 2536

-rwxr-xr-x 1 root wheel 2596411 Aug 19 16:04 rmdump

>

> show logging

[Omitted halfway]

EVT 08/19 16:04:04 E3 RM 00003004 1000:000000000111 RM restarted due to

user operation.

EVT 08/19 16:03:57 E3 RM 01910202 1001:000000000000 System restarted by

user operation.

[Omitted hereinafter]

>

Advertising