How to increase trace logging for Dynamic multipathing device specific module.
Article ID: 100004351
Updated On:
Cause
If it is determined that DMP DSM maybe the cause of issues with importing disk groups, deporting disk groups, not recognizing all paths to a LUN, etc., during troubleshooting, additional logging may be requested if the default level of logging does not provide enough information.
Resolution
To increase the log tracing for DMP DSM, perform the following procedure:
- From a command prompt, execute “vxtrace stop vdsm”. This will stop the default DMP DSM trace so it can be restarted in debug mode:
vxtrace stop vdsm - From a command prompt, execute ""vxtrace start vdsm file=
flags=0x3DF":
vxtrace start vdsm file=c:\vxdmp.etl flags=0x3DF - Perform steps to reproduce the issue.
- From a command prompt, execute "vxtrace stop vdsm". This disables the debug logging and needs to be run prior to collecting file (the data flushes from memory to the file and could take a few minutes to complete):
vxtrace stop vdsm
If the issue is reproduced, collect the output file, C:\vxdmp.etl and run VxExplorer utility so Veritas Technical Services can perform an analysis of the logs.
Applies To
SFW 5.X, SFW 6.X
DMP 5.X, SFW 6.X
Windows 2003
Windows 2008
Issue/Introduction
As part of troubleshooting issues with Dynamic multipathing (DMP) Device Specific Modules (DSM), Veritas Technical Support may need to increase debug / trace logging for DMP DSM.
Was this article helpful?
Yes
No
Powered by
