You can use Putty (SSH) to access the Console go to the GUI in SETUP -> administrator -> Function: Remote access - Read the help notes below or in the GUI.
Using this function, you can manage console tools remotely via the SSH protocol (secure shell). The default user is cli and cannot be altered. The password, however, can be changed.
Allow IP
Here you can assign IP addresses (separated by a semicolon) which are granted remote access to the server. When left blank, the field indicates no restrictions.
Set port
The default port is 22222 for security reasons, because high-number ports are invisible to port scanners. You can only change the setting to a port within the 1024-65535 range. You cannot indicate ports already in use.
Password
Password length is 5 characters minimum. Be sure to use strong passwords.
Confirm password
Please retype your new password.
Password cannot contain:
* special characters such as ' " ` ^ & $ # [ ] \/ | *
* spaces
To connect to the server from Linux/MacOSX systems use:
ssh -2 -p 22222 -l cli ip_address
where:
* option: -2 indicates the SSH protocol version used for connection
* option: -p indicates the remote access port
* option: -l indicates the user (the user needs to be cli)
* option: address_ip indicates the address of the server to which you want to connect
You will be asked for the remote access password you have entered on the server.
To connect to the server from Microsoft Windows, download the free SSH client (Putty):
* in the Host Name (or IP address) field, enter the IP address of the server
* in the Port field, enter the same port as in the server GUI (default 22222)
* in the Protocol field, select SSH
* in the category: Connection -> Data -> Auto-login-username, enter: cli
* in Terminal -> Keyboard -> The Function Keys and keypad, select VT100+
* go back to the Session category, enter the session name in the Saved Sessions field, and click the Save button
* click on the newly saved session, click Open, and enter the password. (If you have not entered the Auto-login-username, Putty will prompt you for a username. At the prompt, enter cli).
I've successfully setup putty and removed all the snapshots and snapshot configs. So far so good . . .
What can I do to check the integrity of the RAID and the physical drives? I think I have a bad drive in the array - the 3Com array controller says it's a 5 drive array but only 4 are listed. One of the drive bays has a green light that's on all the time, which I suppose is the bad drive. I'm not familiar with this type of hardware - how do I check if the drive is bad and what do I do to replace it?
Not knowing the type of RAID controller from 3Ware but you can go here to there website and or ask there Forum users there but I believe it is a function to perform a RAID Verify.
I found the problem - 5 drive array only had 4 functioning drives and has been degraded. Swapping in a new drive doesn't fix the problem, so there must be another hardware issue somewhere. The 9550 controller is obsolete so 3ware is not providing much support for it. The unit is old enough to warrant complete replacement, if I can convince the powers that be here that it's cheaper in the long run.
I'll be doing complete backup on that server today - I just hope it doesn't fail before I can replace it.
Thanks for all of your help! It is greatly appreciated! I have to say that this is the BEST forum experience I have ever had. Keep up the great work!
Glad you are getting it resolved and thanks for the comment as we try to help as bast we can to make sure that you are working. You should look into the DSS V6 and do some replications to so if this happens again you will be able to still continue.
I finally got the RAID array to an OK state, but have not restarted the NAS as of yet. If I log on to the Open-E GUI for the NAS, it tells me there is no logical volume (which is what it was doing when the array was degraded). Should I restart the NAS now that the array is good? Will that bring the logical volume back on line?
Reply With Quote