The new flexible RAID Management enables disks of logical drives to be switched from one enclosure or adapter to another without the configuration being lost. A disk of this type is identified by a blue exclamation point , which indicates a foreign configuration. This foreign configuration can be imported or deleted.
Configurations can be imported or deleted from disks only if the disk is already available again.
If this was not done automatically, please perform the function using the Make ready action (by means of the pull-down menu of the
Actions button or by right-clicking on the disk). You can then start the dialog described below using the Manage foreign configuration
action.
5.5.1 Manage foreign configuration
This action enables you to import or delete one individual foreign configuration or all foreign configurations.
In the dialog box (see the example below) use the index to select either one individual foreign configuration or all (merged) for all foreign configurations for processing and confirm your selection using the Import or Clear button.
The Cancel button in one of the dialog boxes shown below enables you to abort the action without any effect on the existing configuration.
5.5.1.1 Import
When you select Import, the future overall configuration is displayed before the actual import operation begins.
When you select an individual foreign configuration, this is examined and imported regardless of the existing configuration. When you select all (merged), an attempt is made to combine all existing configurations with the foreign configurations.
The import is performed after you have confirmed this and clicked on the OK button.
5.5.1.2 Clear
When you select Clear, you must confirm the operation once again in another dialog box. When one individual foreign configuration is selected, it is cleared.
●
When all (merged) is selected, all foreign configurations are deleted.
●
Note: If a disk which still contains an old configuration was replaced during maintenance work, it is also identified by a blue flag on
the left of the tree. In this case you must delete the old configuration before you can use the disk again.
5.6 Task
In order to maintain the operational reliability of a RAID system, certain actions can be repeated at regular intervals. These include, for example the consistency check of the logical drives, the Patrol Read of the disks or the recalibration of existing BBUs.
When the appropriate object (system, controller, disk, logical drive, BBU) or an existing task object has been selected, the object action Manage task (the dialog described below) can be started via the button pull-down menu Actions or by clicking the right mouse button on the object.
5.6.1 Manage task
This action is used to create, modify or delete a task.
5.6.1.1 Create
If a task does not exist for the selected object and the desired action, you can define and create a task with the following properties. Select via Task the action that is to be regularly carried out.
For each respective task an optional Exception behavior can be specified. You can deselect the default setting to stop after 4 errors. Furthermore you can change the default behavior that after an error a new attempt to start the task is made after 2 minutes, 1 hour, and 8 hours beyond the regular setting. That way you can arrange the number of attempts skip on error and the next regular start time for the task.
Use Frequency to set the required period (from minute-by-minute to yearly). There are various settings depending on the Frequency selected which are used to define the action recurrences more exactly.
The Start time valid for the task, i.e. when the action is started for the very first time, has a default value now when creating the task. If the action cannot be started, because e.g. the action is already in use, the option now will not be offered. Additionaly a time around 24 hours later than current time will be set as default time. Otherwise, if the problem happens when leaving the dialog a time around 8 hours later will be set automatically. A different starting time can be agreed upon by choosing later and with input of a valid date as well as a desired time. When the button Create is pressed, the required action is started either within the next minute or after expiration of a selected later start time.
Recurrence is used to select a value of 1 to 100 so that, depending on the choice of Frequency, the action can be repeated within a
A weekly Frequency can also have one or more Weekdays in order to define the starting point more exactly. If no weekday is selected, the current weekday is automatically set as used in the pre-setting. Furthermore the selected weekdays will be considered by the calculation of the first starting point if later is selected.
The exact day of the month can be set via the selection on day. If a month does not have a corresponding day, e.g. 30th February, the action is started on the next possible day of the following month.
On the other hand, the selection on the is used to select the first to last week of the appropriate month plus a weekday to start the action.
Also the rule of the desired day of month will be considered if you decided to use a later starting point.
Annual Frequency allows the selection of an exact starting-day (see above) and also offers one or more months in order to define the starting point more exactly.
If an exact day in the month is defined, but this day is not in available certain months, then the corresponding months are automatically deselected and excluded as a selection option. February 29th is an exception. Such a selection is allowed as this day exists in certain years but not all of them. If necessary, the action is started on the next possible day of the following month, i.e. on March 1st. If no month is selected, the current month is automatically set as used in the pre-setting.
With the choice of later by the Start time the rule of the desired day of month and also the selected months will be considered by the calculation of the exact starting time.
When the button Create is pressed, the required action is started within the next minute or after another desired start time if later is selected. If thereby the Frequency is set at weekly, monthly or annually, the first start time is then in the current week or within a month or year, respectively.
When you quit the dialog by means of the Cancel button, no effect on any existing configuration will occur.
If you want to create a task for Patrol Read you must set Patrol Read mode to manual beforehand. Otherwise the task for Patrol Read will be ignored.
5.6.1.2 Modify
Via the selection of an existing task object or by selection of an action in the dialog, for which the selected object already has a task defined, you can modify the settings of the task.
The Start time is preset at later when a task is modified. If this setting is not changed, the next start time is calculated when the OK button is pressed based on the set and, if necessary, any modified values. If the Frequency is set at weekly, monthly or annually, the next start time is then in the current week or within a month or year, respectively. Only a subsequent date is based on the value set in
Recurrence.
If the Start time is changed to now, the action is started within the next minute after the button OK was pressed. If the action cannot be started, because e.g. the action is already running, the option now will not be offered. Otherwise, if the problem happens when leaving the dialog a time around 8 hours later will be set automatically.
Likewise, the status and the internal task error counter is reset after the button OK has been pressed. When you quit the dialog via the Cancel button, no changes will occur.
5.6.1.3 Delete
The task is deleted when the button Delete is pressed. This does not influence, interrupt nor terminate any current action triggered by the task.
6 Events
6.1 Displaying Events
The event window is located at the lower edge of the user interface. It contains the latest events of all the RAID controllers which are managed by ServerView RAID Manager.
You can use the delimiter bar to enlarge or reduce this window. The width of the columns can be changed by dragging its border in the table header. This is somtimes useful for long event messages. A double click on an event opens a dialog, with which it is easy to navigate through the events and to catch the whole detailed message at a glance.
The following information is available for each event:
The type is additionaly presented by an icon which indicates the severity of the event.
●
Error Warning
Important Information
Date and time at which the event occurred
●
The name of the object which reported the event
●
Event ID
●
A brief message with a description of the event
●
ServerView RAID Manager logs all events in a Log file in plain text. This file is in XML format and is simple to read out and process. In addition, all events are sent out as SNMP traps for further processing by ServerView Event Manager or any other management tool that can handle traps (e.g. IBM Tivoli, HP OpenView, etc.). Please refer to the ServerView documentation for further details and configuration options.
By default all events show up in the operating system's logging facility. On Windows based systems entries can be found in Start >
Settings > Control Panel > Administrative Tools > Event Viewer (Application), on Linux systems in /var/log/messages, and on Solaris
Note that the message texts, IDs and error classes of the events are the same as those used in the traps and in file/system logging. The only difference is that the four error classes of the traps have been reduced to three error classes for the events (Informational = Information, Minor = Warning, Major and Critical = Error).
6.2 Events / SNMP Traps
The basis for the ServerView RAID SNMP Agent is the MIB file RAID.mib (Windows) or FSC-RAID-MIB.txt (Linux/VMware/Solaris). All the information and trap types are defined in this file. The traps of the MIB are listed below.
The message texts, IDs and error classes of the traps are the same as those used in the event messages in the interface and in file/system logging.
If the described recovery actions do not solve the problem please call your local Fujitsu Help Desk.