12 – Troubleshooting
Tracing SANsurfer FC HBA Manager GUI and Agent Activity (Debug)
12.2.2
Exporting or Saving Agent Activity Logs
This section discusses:
The agent logs
■
Exporting or saving the agent logs
■
12.2.2.1
The Agent Logs
Agent activity automatically logs to one of the following. The name and location of
the log differs, depending on the type of system.
Windows 2000/Windows Server 2003. Event Viewer
■
Red Hat/SuSE Linux. /var/log/messages
■
Solaris SPARC. /var/log/syslog
■
NetWare. sys:\\etc\qlremote.log
■
12.2.2.2
Exporting or Saving the Agent Logs
From a Windows 2000/Windows Server 2003 system, do the following to save the
current application log from the Event Viewer:
1. Click the Start button, point to Programs, point to Administrative Tools, and
click Event Viewer.
2. From the Log menu, select Save As. Save the file using an appropriate name.
From a Red Hat/SuSE Linux system, do the following to export agent activity:
1. Open a terminal (for example, xterm or eterm).
2. Stop the currently running qlremote agent:
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.
12-14
(see section 12.2.2.1)
# killall -TERM qlremote
# /usr/local/bin/qlremote > /AgentOutput.txt 2>&1
(see section 12.2.2.2)
section
12.2.1,
step
step
1, press CTRL+C to stop the qlremote
Q
2). Send the file to
FS0054603-00 C
Need help?
Do you have a question about the SANsurfer FC HBA Manager Application and is the answer not in the manual?
Questions and answers