Q
From a Solaris SPARC system, do the following to export agent activity:
1. Open a terminal (for example, xterm or dtterm).
2. Do the following to stop the currently running qlremote agent:
a. Type the following and then press ENTER to determine the process identifier
root
root
b. Type the following and then press ENTER. pid is the identifier returned in
3. Start the agent, again, without forking into the background. Redirect the stdout
and stderr properties to a file (see
technical support.
4. Open a second terminal to start the SANsurfer FC HBA Manager GUI. Connect
to the host with the SANsurfer FC HBA Manager GUI.
5. From the terminal you opened in
agent. This causes the agent to clean up and terminate.
For a NetWare system, the qlremote.log is already exported.
FS0054603-00 C
Tracing SANsurfer FC HBA Manager GUI and Agent Activity (Debug)
(pid) of qlremote:
# ps -ef | grep qlremote
The pid displays, as in the following example. Note that in the example, the
pid is 227.
227
1
0 15:59:55 ?
410
409
0 16:01:46 pts/6 0:00
step
a.
# kill -TERM pid
# /opt/QLogic_Corporation/SANsurfer/qlremote
> /AgentOutput.txt 2>&1
0:00
/opt/QLogic_Corporation/
SANsurfer/qlremote
grep qlremote
section
12.2.1,
step
step
1, press CTRL+C to stop the qlremote
12 – Troubleshooting
2). Send the file to
12-15
Need help?
Do you have a question about the SANsurfer FC HBA Manager Application and is the answer not in the manual?