Personal tools

NaraBrickDailyMaintenance: Difference between revisions

From Adapt

Jump to: navigation, search
No edit summary
 
No edit summary
Line 1: Line 1:
__NOTOC__
==Raid health monitoring==
==Raid health monitoring==



Revision as of 15:47, 12 September 2008

Raid health monitoring

Areca RAIDS

The two areca RAIDS are web-accessable at [[1][2]] (top 12 drives) and [[3][4]] (bottom 12 drives). The default screen should show the health of any raid that is part of the set.

  • Stuff to Check
  • System Controls -> View Events, look for any unexpected failures or other information.
  • <nop>VolumeSet Functions -> Check Volume Set. When the raid is able to be online for over a day. The check should be run once every month or two to check raid parity and force disk failure in a controlled circumstance.

3ware Raid

The 3ware raid is accessable locally only. So to connect, you must open an ssh tunnel into erasrb2. The following will allow access from https://localhost:9090 to be forwarded to the 3ware port (888) on erasrb2.

ssh toaster@207.245.162.200 -L9090:localhost:888
  • Stuff to Check
  • Initial login screen will tell health of the raid
  • Monitor -> Alarms, look for unusual events
  • Management -> Mainenance , Verify unit should be run periodically to make sure the mirror is complete and to force disk failure.

Raid Mail Config

Each raid is configured to send loads of information via e-mail when any event occurs, this includes power up, logins, and system checks. Current Rick and Mike are set to receive these mails. The raids send mail to @umiacs addresses only since they use the umiacs mail servers as an smtp server.