5.If you still cannot connect, try to connect using the server’s IP address instead of its server name (or vice versa).
6.If you can now connect, stop here.
The host name or IP address that failed may be incorrect.
7.If you still cannot connect, check network connectivity. Ping the target server and other machines in the same subnet.
8.If you cannot ping the server or the hosts on the same subnet, there is a network outage. Stop here, and correct the problem. Then reconnect to the VTL server.
Case: Connection fails during log in
1.Verify the user name and password.
The password is case‐sensitive. Make sure the Caps Lock key is not pressed on the keyboard
2.If the user name or password was incorrect, stop here, and log in using the correct credentials.
3.If the user name and password seem to be correct, make sure they exist on the server. From the machine where VTL console is installed, open a secure shell (ssh) session on the VTL server, and log on using the same user name and password as above.
Note that ssh may be disabled if local security policies so require.
4.If ssh is enabled but you still cannot log in, the user name or password is probably incorrect. Stop here, and obtain proper credentials.
5.If you can log in using ssh, check the status of the VTL server software modules. From the ssh commandline, run the following command:
#ipstor status
6.If a module has stopped, restart it with the following command, and stop here.
#vtl restart <module name>
Case: Connection fails while retrieving the server configuration
1.If the connection fails while retrieving the server configuration, note any error messages that appear.
2.Then contact Sun technical support.
Case: Connection fails while checking the VTL license
1. Contact Sun technical support.
230 VTL User Guide • May 2008 | G • 96267 |
