Resolving An Ans1267E Error; Resolving Issues Reported For Lshealth; Error For "Mgmtnode_Repl_State Error; Database_Replication_Failed - IBM Storwize V7000 Unified Series Problem Determination Manual

Resolving an ANS1267E error

An ANS1267E error might indicate an incorrect setting in the Tivoli
Manager server configuration.
An ANS1267E error can result from the Tivoli Storage Manager server not being
set up to handle hierarchical storage management (HSM) migrated files. A return
of ANS1267E means that the management class is not accepting files from HSM.
The fix for this is to set "spacemgtech" to "auto".

Resolving issues reported for lshealth

Use this information for resolving lshealth reported issues, specifically for
"MGMTNODE_REPL_STATE ERROR DATABASE_REPLICATION_FAILED" and
"The mount state of the file system /ibm/Filesystem_Name changed to error level."
These errors may be transient and may clear automatically at any time.

Error for "MGMTNODE_REPL_STATE ERROR

DATABASE_REPLICATION_FAILED"

To resolve the "MGMTNODE_REPL_STATE ERROR
DATABASE_REPLICATION_FAILED" error, complete the following procedure.
1. Verify that the other management node role has "Host State OK". Repair the
168
Storwize V7000 Unified: Problem Determination Guide Version
a. Run the stopbackup -d file_system_name command and the stoprestore -d
file_system_name command to stop any backup or restore operation.
b. Validate that no error occurred while stopping any Tivoli Storage Manager
service.
c. Run the chkfs file_system_name -v | tee /ftdc/chkfs_fs_name.log2
command to recapture the output to a file.
d. Run the startrestore command and the startbackup command to enable
Tivoli Storage Manager.
If you receive an error message (the number of mounted or used nodes does
not matter) at step 5 of the command internal execution steps like the
following,
(5/9) Performing mmfsck call for the file system check stderr:
Cannot check. "gpfs0" is mounted on 1 node(s) and in use on 1 node(s).
mmfsck: Command failed.
Examine previous error messages to determine cause.
perform the following steps:
a. Monitor the lsmount -r command until the mount status changes to "not
mounted".
b. Run the chkfs file_system_name command again.
Review the new output file for errors and save it for IBM support to investigate
any problems. It is expected that the file contains Lost blocks were found
messages. It is normal to have some missing file system blocks. If the only
errors that are reported are missing blocks, no further repair is needed.
However, if the chkfs command reports more severe errors, contact IBM
support to assist with repairing the file system.
host state if necessary.
®
Storage