Votos - 4, Puntuación media: 3.3 ( )

Fabricar: AMCC Tamaño del archivo: 337.51 kb Nombre del archivo: Idioma del manual:

A recommendation is then made as to whether an update is needed, and you are asked to confirm whether you want to continue. If you confirm that you want to continue, the new firmware image is downloaded to the specified controller. A reboot is required for the new firmware image to take effect. Example: //localhost> /c0 update fw=/tmp/prom0006.img Warning: We strongly recommend backing up your data before updating the firmware. Updating the firmware can render the device driver and/or management tools incompatible. It is recommended to have a copy of current firmware image for rollbacks. Examining compatibility data from firmware image and /c0 ... Done. New-Firmware Current-Firmware Current-Driver Current-API --------------------------------------------------------------------- FE9X 3.05.00.005 FE9X 3.05.00.005 2.26.04.007 2.01.00.008 Current firmware version is the same as the new firmware. Recommendation: No need to update. 3ware Serial ATA RAID Controller CLI Guide Controller Object Commands Given the above recommendation... Do you want to continue ? Y|N [N]: y Downloading the firmware from file /tmp/prom0006.img ... Done. The new image will take effect after reboot. force attribute is optional. If you include it, the compatibility checks are bypassed. /cx show alarms [reverse] Asynchronous events (also referred to as AENs or alarms) are originated by firmware and captured by their respective device drivers. These events reflect warning, debugging, and/or informative messages for the end user. These events are kept in a finite queue inside the kernel, awaiting extraction by user space programs such as CLI and/or 3DM. The /cx show alarms command displays all available alarms on a given controller. The default is to display the most recent alarm or AEN message first. The user can also use the [reverse] attribute to display the most recent alarm or AEN message last. Alarms generated on 7000/8000 controllers do not have dates, so you will see a '-' in the Date column. This means that it is not applicable. In addition, alarm messages on 7000/8000 controllers contain the severity in the message text, so the Severity column also shows a '-'. Typical output looks like: tw_cli> /c1 show alarms reverse Ctl Date Severity Message -------------------------------------------------------------------------------------------c1 [Fri Nov 28 04:26:31 2003] ERROR (0x04:0x0002): Degraded unit detected:unit=0, port=2c1 [Fri Nov 28 06:13:54 2003] INFO (0x04:0x000B): Rebuild started: unit=0c1 [Fri Nov 28 06:30:35 2003] INFO (0x04:0x003B): Background rebuild paused:unit=0c1 [Fri Nov 28 06:33:00 2003] ERROR (0x04:0x0002): Degraded unit detected:unit=0, port=0c1 [Fri Nov 28 06:33:04 2003] ERROR (0x04:0x0002): Degraded unit detected:unit=0, port=4c1 [Fri Nov 28 06:33:46 2003] INFO (0x04:0x000B): Rebuild started: unit=0c1 [Fri Nov 28 06:37:58 2003] INFO (0x04:0x000B): Rebuild started: unit=0c1 [Fri Nov 28 07:51:34 2003] INFO (0x04:0x0005): Background rebuild done:unit=0c1 [Fri Nov 28 07:59:43 2003] INFO (0x04:0x0005): Background rebuild done:unit=0c1 [Mon Dec 1 02:26:12 2003] ERROR (0x04:0x0002): Degraded unit detected:unit=0, port=3 Chapter 2. CLI Syntax Reference /cx show diag This command extracts controller diagnostics suitable for technical support usage. Note that some characters might not be printable or rendered correctly (human readable). It is recommended to save the output from this command to a file, where it can be communicated to technical support or further studied with Linux utilities such as od(1). In order to redirect the output you must run the following command from a command line, not from within the tw_cli shell. tw_cli /c0 show diag > diag.txt /cx show rebuild 9000 series controllers support background tasks and allow you to schedule a regular time when they occur. Rebuild is one of the supported background tasks. Migrate and initialize are other background tasks that follow the same schedule as rebuild. Other background tasks for which there are separate schedules are verify and selftest. For each background task, up to 7 time periods can be registered, known as slots 1 through 7. Each task schedule can be managed by a set of commands including add, del, show and set a task. Background task schedules have a slot id, start-day-time, duration, and status attributes. For details about setting up a schedule for background rebuild tasks, see “Setting Up a Rebuild Schedule” on page 50. Rebuild activity attempts to (re)synchronize all members of redundant units such as RAID-1, RAID-10, RAID-5 and RAID-50. Rebuild can be started manually or automatically if a spare has been defined. Scheduled rebuilds will take place during the scheduled time slot, if enabled the schedules are enabled. For in depth information about rebuild and other background tasks, see “About Background Tasks” in the 3ware Serial ATA RAID Controller User Guide. The show rebuild command displays the current rebuild background task sche...

Descargar ahora

Introduzca dos números de la imagen: