Qlogic SANsurfer FC HBA Manager Guía de usuario Pagina 143

  • Descarga
  • Añadir a mis manuales
  • Imprimir
  • Pagina
    / 152
  • Tabla de contenidos
  • SOLUCIÓN DE PROBLEMAS
  • MARCADORES
  • Valorado. / 5. Basado en revisión del cliente
Vista de pagina 142
12 – Troubleshooting
Tracing SANsurfer iSCSI HBA Manager GUI and Agent Activity (Debug)
IS0054602-00 A 12-19
Q
From a Solaris SPARC system, do the following to export agent activity:
1. Open a terminal (for example, xterm or dtterm).
2. Do one of the following to stop the currently running iqlremote agent:
Type the following command and then press ENTER.
/etc/rc3.d/S99iqlremote stop
Type the following command and then press ENTER.
pkill -TERM iqlremote
Do the following.
a. Type the following and then press ENTER to determine the process
identifier (pid) of iqlremote:
# ps -ef | grep iqlremote
The pid displays, as in the following example. Note that in the example,
the pid is 227.
b. Type the following and then press ENTER. pid is the identifier returned
in step a.
# kill -TERM pid
3. Start the agent, again, without forking into the background. Redirect the stdout
and stderr properties to a file (see section 12.2.2, step 2). Send the file to
technical support.
# /opt/QLogic_Corporation/SANsurfer/iqlremote
> /AgentOutput.txt 2>&1
4. Open a second terminal to start the SANsurfer iSCSI HBA Manager GUI.
Connect to the host with the SANsurfer iSCSI HBA Manager GUI.
5. From the terminal you opened in step 1, press CTRL+C to stop the iqlremote
agent. This causes the agent to clean up and terminate.
root 227 1 0 15:59:55 ? 0:00 /opt/QLogic_Corporation/
SANsurfer/iqlremote
root 410 409 0 16:01:46 pts/6 0:00 grep iqlremote
Vista de pagina 142
1 2 ... 138 139 140 141 142 143 144 145 146 147 148 ... 151 152

Comentarios a estos manuales

Sin comentarios