[ Contents
] [ Index ]
If a server is not responding or may be down, check the following: Make sure the SANscape Agents are running at the server. ps -e | grep ss The names ssmon and ssserver should both be present
in the output. If they are not, proceed to Step 2. If they are, proceed
to Step 4. (Windows NT) Go to Settings > Control Panel > Services and
verify that SANscape Monitor, SANscape
Server, and SANscape Startup
services are started. If they are not, proceed to Step 2. If they
are, proceed to Step 4. (Windows 2000) Go to Start > Administrative Services > Computer
Management. Click Services & Applications and verify that
SANscape Monitor, SANscape
Server, and SANscape
Startup Services are started. If they are not, proceed to Step
2. If they are, proceed to Step 4.
(Windows NT/2000) Stop and start the services by right-clicking
the service you want to start or stop. (IBM AIX) Stop and start the agents as explained in the
SANscape User's Guide.
To test the TCP/IP connectivity at the command line, type
ping {IP address of the server or the other server name} If you do not get a reply, then there is a problem in the TCP/IP
protocol services. Contact your MIS department for assistance.
If the name or password is not correct, make the connection by editing
the entries. See the appropriate section below: Linux Operating Environment - Creating Users and Passwords. AIX Operating Environment - Creating Users and Passwords. The password has to be one established through the procedure for
setting up SANscape users.
|