Loading...
Loading...
The DLm health check utility runs once per hour or upon request. The utility checks numerous components of the DLm. During one or more health check runs per day, the DLm health check report identifies the following error condition: DLmT5127E VNX/VG8 System Status Check Failed: Failed Configured DataMovers Status Check: Slot getreason did not return status 5 The following line appear further down in the health check report: Configured DataMovers Status FAILED Slot n getreason=25END All other Data Mover checks pass in the same health check report: Communication to VNX data movers via the Data network All active datamovers are available <-- The health check report shows this check for all VTEs All 10 Gbps network switch checks also pass.
This result from the DLm health check report is a transient timing condition in the DLm health check code. Mutliple instances of this error were investigated. This instances were non-repeating conditions, and the VNX logs contained no errors. If a Data Mover had an actual problem,, the condition would be persistent. In that case, more DLm health check tests would fail. Examples are the VTE-level communication test to the data movers and the 10 Gbps network switch port tests. The DLm primary management VTE launches the DLm health check utility. The utility starts several componenent checks. Each VTE runs its own component checks, such as testing access through the data network. The primary management VTE also checks the administrative-level functions of the DLm. The VTE component connection checks run at the same time as any DLm read/write operations and replication. During this time, the primary management VTE launches the "/nas/sbin/getreason" command to validate the health of the data movers. When a data mover is busy, the data mover throttles administrative requests and processes the requests in the order received. If the processing takes longer than the health check or the underlying "getreason" command allows, the health check can report reason code 25 sporadically. The getreason code 25 indicates that the Data Mover Management Module encountered a condition. The management module interfaces with the control station and users, and facilitates command interaction. A persistent "getreason" response of status 25 would indicate a possible issue with the data mover. A condition that does not repeat can result from a busy data mover. The DLm health check sends the "getreason" command to the VNX control station. In parallel, the health check checks connectivity to each data mover. These parallel actions increase the load on the data movers while the health check runs.
Error DLmT5127E is a DLm Tools health check error. Other errors in the DLm health check report, or a different data mover status code, would indicate an actual error. Wait a few moments. Rerun the health check or the VNX "/nasmcd/getreason" command. If the command returns the same status code for the same data mover, rerun the "getreason" command immediately. If the command returns the same status code again, gather logs from the DLm (Dell Support login required). Open a service request and attach the logs.
Click on a version to see all relevant bugs