Qlogic SANsurfer FC HBA Manager User Manual page 132

9 – Troubleshooting
Tracing SANsurfer FC HBA Manager and Agent Activity (Debug)
For Macintosh:
# /installation folder/qlremote > /AgentOutput.txt 2>&1
5. Open a second terminal to start the SANsurfer FC HBA Manager user
interface. Connect to the host with SANsurfer FC HBA Manager.
6. On the terminal you opened in
agent. This causes the agent to clean up and terminate.
From a Solaris SPARC/x86 system, follow these steps to export agent activity.
To export agent activity on Solaris:
1. Open a terminal (for example, xterm, or dtterm).
2. To stop the currently running qlremote agent, do the following:
a.
b.
NOTE:
3. In the agent.properties file, add the following line:
node.agent.quiet.mode.enable=1
4. Start the agent again without forking into the background. Redirect the
stdout and stderr properties to a file (see
Manager User Interface
service provider.
# /installation folder/qlremote
> /AgentOutput.txt 2>&1
9-20
To determine the process identifier (pid) of qlremote, type the following
and then press ENTER:
# ps -ef | grep qlremote
The pid is shown, as in the following example. Note that in the
example, the pid is 227.
root 227 1 0 15:59:55 ?
root 410 409 0 16:01:46 pts/6 0:00 grep qlremote
Type the following and then press ENTER:
# kill -TERM pid
The pid is the identifier returned in
Activity,
Step 1, press CTRL+C to stop the qlremote
0:00 /opt/QLogic_Corporation/
SANsurfer/qlremote
Step a.
Tracing SANsurfer FC HBA
Step 2). Send the file to your authorized
S
SN0054651-00 B