Hp Surestore Disk Array 12h and FC60 Manuel d'utilisateur Page 308

  • Télécharger
  • Ajouter à mon manuel
  • Imprimer
  • Page
    / 466
  • Table des matières
  • DEPANNAGE
  • MARQUE LIVRES
  • Noté. / 5. Basé sur avis des utilisateurs
Vue de la page 307
308 Managing the Disk Array Using Array Manager 60
previous firmware releases are logged in the major event log. Earlier versions of firmware
(prior to HP08) use the standard log file format, also called Asychrnonous Event
Notification (AEN).
Note
On firmware HP08 and later, major event logging is enabled by default. If major
event logging has been disabled by disabling the UTM, only standard log entries
will be available.
Allocating Space for Disk Array Logs
The amount of space available for storing log files on the host in controlled by the host
environment variable
AM60_MAX_LOG_SIZE_MB
. This variable defines the maximum size
(in megabytes) allocated for storage of the disk array log files. The log files are stored as
individual files in /var/opt/hparray/log. All log files will be maintained until the specified
maximum value is exceeded. At that point, the oldest log file will be deleted to make room
for the new file (FIFO).
The valid range for
AM60_MAX_LOG_SIZE_MB
is 100 to 4096 (100 MB to 4 GB). Any value
outside of this range is ignored and the default value is used. The default value for allocated
log storage area is 100 MB.
Note
- When changing the value for
AM60_MAX_LOG_SIZE_MB,
AM60Srvr must be
stopped and restarted before the new value will take effect. To enforce the
AM60_MAX_LOG_SIZE_MB
value, it is necessary to stop and restart AM60Srvr
every time the host is rebooted.
- When setting a large value for
AM60_MAX_LOG_SIZE_MB
, make sure the /var
file system is large enough to accommodate the logs files. If it is not, the log files
may overflow the
/var
file system.
Vue de la page 307
1 2 ... 303 304 305 306 307 308 309 310 311 312 313 ... 465 466

Commentaires sur ces manuels

Pas de commentaire