mcfgtrace


The mcfgtrace command modifies the tracing configuration of a running cell and takes the same argument format as a line in the mcell.trace file. mcfgtrace syntax

See Event-management-CLI-trace-configuration for instructions on setting up CLI trace configuration files.

The following figure shows the syntax for mcfgtrace.

mcfgtrace syntax

mcfgtrace [-h|-?] [-z] [-q] [-c <ConfigFile>] [-l <HomeLocation>] {-p <Var Value>}
[-i UserID[/Password][@Host[/Port]]] [-n <cellName>|-n @Host[/Port[#Key]]]
[-v] (<Module Level Destination>| Switch <Switch Destination>)

The -n option is required if the cell is remote or if cellName differs from Host. See Using the -n option for more information.

Module Level Destination is the command-specific option for mcfgtrace. For more information, see mcfgtrace parameters. For a list of common command options that apply to all CLI commands, see Event-management-common-command-options.

mcfgtrace parameters

The following table lists the parameters for mcfgtrace.

mcfgtrace parameters

Parameter

Available values

Module

ALL| Module
For a list of modules, see the mcell.trace file.

Note

Your module-level configuration can be requested by BMC Support if you are working with them to resolve an issue.

Level
ALL | VERBOSE | INFORM | WARNING | ERROR | FATAL
Switch

SwitchName
For a list of switch names, see the mcell.trace file.

Destination

no | stderr | console |DestinationFileName

mcfgtrace example

To activate maximum tracing for all modules and send the output to the all.trace file in the temporary directory for Cell1, which is by default installationDirectory/pw/server\log\Cell1, enter the following command:

mcfgtrace -n Cell1 ALL ALL '%T/all.trace' 

mcfgtrace return codes

No specific return codes exist for mcfgtrace. See Event-management-return-codes for a list of common return codes that apply to all CLI commands.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*