Seagate ST3250824NS Guida alla Risoluzione dei Problemi Pagina 29

  • Scaricare
  • Aggiungi ai miei manuali
  • Stampa
  • Pagina
    / 32
  • Indice
  • SEGNALIBRI
  • Valutato. / 5. Basato su recensioni clienti
Vedere la pagina 28
Release Notes 29
Known Issues
The following sections describe known issues for this release.
Persistent IP Address
Beginning with the J200 release, the IP address is persistent. The IP address is
stored on the midplane. When the controller is powered on, the firmware looks at
the IP address in the midplane and stores this address in the controllers flash
memory. When you replace a controller with a new controller, the new controller
will have the same IP address as the old controller.
In previous versions of the firmware, the IP address was only stored in the flash
memory of the controller. If it was necessary to replace a controller, you would have
to update the IP address of the new controller.
This causes an incompatibility between previous versions of the firmware and the
J200 firmware. When you upgrade to J200, the firmware looks at the midplane for
the IP address. If there is an IP address, that address is written to the controllers
Flash memory. If the location of the IP address on the midplane does not contain a
valid IP address, then the IP address in the controllers Flash memory is used. This
might cause you to lose connectivity during the upgrade process. As described in
“Updating RAID Controller Software” on page 10, you must connect directly to the
storage system in order to change the IP address.
Documentation Errata
In the CLI Reference Manual and in CLI help, descriptions of the CLI commands
scrub vdisk and verify vdisk incorrectly state that these commands
correct errors that they find. In fact, the number of inconsistencies found is only
reported in the "Vdisk verification complete" event (event code 21) in the event
log. Such inconsistencies can indicate that a drive in the virtual disk is going bad.
Similarly, in the Administrators Guide, the topic “Verifying a Virtual Disk”
incorrectly states that the Verify utility corrects errors that it finds. In fact, the
number of inconsistencies found is only reported in the "Vdisk verification
complete" event (event code 21) in the event log. Such inconsistencies can
indicate that a drive in the virtual disk is going bad.
Similarly, in the glossary, the definition of verify should state that errors are only
reported, not corrected.
Vedere la pagina 28
1 2 ... 24 25 26 27 28 29 30 31 32

Commenti su questo manuale

Nessun commento