3 | Debugging and logging options configuration | |
| <?xml version="1.0" encoding="windows=1252" standalone="no"?> | |
| <!DOCTYPE log SYSTEM "logger.dtd"> | |
| <log> |
|
| <record> |
|
| . | |
| . | |
| . |
|
| </record> |
|
| </log> |
|
| <?xml version="1.0" encoding="windows=1252" standalone="no"?> | |
| <!DOCTYPE log SYSTEM "logger.dtd"> | |
| <log> |
|
| <record> |
|
| . | |
| . | |
| . |
|
| </record> |
|
| </log> |
|
Capture provider cache information
This section describes how you can write the dynamic information stored in the provider to a debug log file. The debug log file is an XML file.
Any of the following information can be logged:
•connection cache
•configuration
•zoning cache
The following procedure is the equivalent of the extrinsic method Brocade_Agent.LogCacheData.
Capturing information from the provider cache
1.Launch the Brocade SMI Agent Configuration Tool.
2.Click Provider Cache in the menu tree (see Figure 26).
3.Check the check boxes next to the information you want to capture:
•Connection Cache
•Configuration
•Zoning Cache
4.Type the location of the log file or click Select Folder to browse for the file location.
An XML file with the name SMIAgentCache<timestamp> will be created in that location.
5.Click Log Deadlock Information to log the current status of threads that are in a deadlock situation.
This is the equivalent of the extrinsic method Brocade_Agent.LogCacheData.
6.Click Dump now.
42 | Brocade SMI Agent User’s Guide |
|