unixdev.net


Switch to SpeakEasy.net DSL

The Modular Manual Browser

Home Page
Manual: (HP-UX-11.11)
Page:
Section:
Apropos / Subsearch:
optional field



 amlog(1M)							   amlog(1M)




 NAME
      amlog - displays host-based controller log entries for a disk array

 SYNOPSIS
      amlog [-s StartTime] [-e EndTime] [-t <RecordType[,RecordType...]>]

      [-c] [-d LogDir] [-S] [-V] [-a ArrayID]

      amlog -?

 DESCRIPTION
      amlog displays the contents of the disk array controller logs
      maintained by the host.  These logs contain information useful for
      diagnosing and troubleshooting the disk array.  The host maintains
      multiple log files containing entries for each disk array.

      The ArrayID used to address the disk array must be the disk array ID.
      An alias name cannot be used because alias names are not recorded in
      the log.

    Identifying Disk Modules
      Disk modules are identified within Array Manager 60 using a numbered
      pair of the form n:n.  The first number identifies the SCSI channel
      (or bus) connecting the array controller to the enclosure containing
      the disk module.	The channel number is indicated on the back of the
      array controller enclosure.  The second number is the disk module SCSI
      ID.  The SCSI ID is determined by the slot in which the disk module is
      installed, but is not the same as the physical slot number (0-9).

      For example, the numbered pair 2:1 identifies the disk module on
      channel 2 with a SCSI ID of 1. Refer to the Disk Array FC/60 User's
      Guide for more information on disk module addressing.

    Options
      amlog supports the following options:

	   -a ArrayID	  Identify a specific disk array for which the logs
			  will be displayed.  The default is to display the
			  logs for all disk arrays.

	   -c		  Limits major event log output to events of
			  critical priority.  This option is ignored unless
			  specified in conjunction with -t mel.

	   -d LogDir	  Specify the path name of the log directory.  The
			  default is /var/opt/hparray/log.

	   -e EndTime	  Specify the ending date and time.  Log records
			  with a later date and time will not be printed.
			  The default is the time of the last log record.
			  Uses the same format as StartTime.



				    - 1 -	  Formatted:  August 2, 2006






 amlog(1M)							   amlog(1M)




	   -s StartTime	  Specify the starting date and time.  Log records
			  with an earlier date and time will not be printed.
			  The default is the time of the oldest log record.
			  The format for entering the date and time is
			  MMddhhmm[yy], where

			  MM   = Month (01-12)
			  dd   = Day (01-31)
			  hh   = Hour (00-23)
			  mm   = Minute (00-59)
			  yy   = Year (00-99) [optional].  Years earlier
			       than 90 are interpreted as 2000 + YY.

	   -S		  Raw output display.  Data is output as a colon-
			  delimited ASCII text string.	Raw output format is
			  described below.

	   -t RecordType  Specify the log record types to be displayed.
			  Valid record types are ctrlr (controller log
			  sense) and mel (major event log). The default
			  selection is ctrlr. Major event logging is
			  available in firmware versions HP07 and later.

	   -V		  Verbose output, displays additional "raw" major
			  event log data, which can only be interpreted via
			  the MEL Specification. This option is ignored
			  unless specified in conjunction with -t mel.

	   -?		  Display expanded usage message.  This option
			  overrides all others.

 SECURITY CONFIGURATION
      This command is modified for all security configurations.

    Security Behavior/Restrictions
      Use of this command is restricted to authorized users only.

    Command Authorizations
      This command requires the sysadmin authorization to successfully
      execute.

    Privileges
      The command has been modified to support least privilege. The
      potential privileges possessed by the command and their uses include:

      allowdacread	  This privilege is raised to provide discretionary
			  read access to the devices.

      allowdacwrite	  This privilege is raised to provide discretionary
			  write access to the devices.




				    - 2 -	  Formatted:  August 2, 2006






 amlog(1M)							   amlog(1M)




      allowmacread	  This privilege is raised to provide mandatory read
			  access to the devices.

      allowmacwrite	  This privilege is raised to provide mandatory
			  write access to the devices.

      filesysops	  This privilege is raised to allow the mknod(2)
			  system call to succeed.

      writeaudit	  The command generates its own audit records and
			  submits these directly to the system audit trail.
			  This privilege is raised whenever the command
			  needs to write an audit record.

 EXTERNAL INFLUENCES
    Environment Variables
      LC_MESSAGES determines the language in which messages are displayed.
      The current language settings can be checked with locale(1).

      AM60_MAX_LOG_SIZE_MB 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 this variable is 100 to 4096 (100 MB to 4 GB). If
      a value outside of this range is specified, it will be ignored and the
      default value will be used. The default value for allocated log
      storage area is 100 MB. When setting a value, make sure the /var file
      system is large enough to accommodate the logs files. If it is not,
      the log files may overflow the file system.

 RETURN VALUE
      amlog returns the following values:

	   0	Successful completion.
	   1	An error in execution (I/O, subsystem, security, etc.)
		occurred.
	   2	An error in command syntax occurred: for example, an unknown
		command-line option was passed.

 DIAGNOSTICS
      The following message can be generated by amlog:

      Usage: amlog [-s <&lt&lt&lt;StartTime>&gt&gt&gt;] [-e <&lt&lt&lt;EndTime>&gt&gt&gt;]
	   [-t <&lt&lt&lt;RecordType[,RecordType...]>&gt&gt&gt;] [-c]
	   [-d <&lt&lt&lt;LogDir>&gt&gt&gt;] [-S] [-V] [-a <&lt&lt&lt;ArrayID>&gt&gt&gt;]

      Extended help: amlog -?




				    - 3 -	  Formatted:  August 2, 2006






 amlog(1M)							   amlog(1M)




	   An error in command syntax has occurred.  Re-enter the command
	   with all necessary arguments.

 EXAMPLES
      Display the controller log for disk array 000200A0B805E798.  Display
      the log entries entered since 6/1/99.

	   amlog -s 0601000099 -a 000200A0B805E798

      Display the controller log for all disk arrays on the host.  Use the
      default settings to display all log entries.

	   amlog

 RAW OUTPUT FORMAT
      The contents of the raw output text string for log entries is as
      follows:

      Default Log Output

	   AL:LogFilename:AddSenAvailable:SenseDate:SenseTime:FRUCode:
	   FRUCodeQual:SK:ASC:ASCQ:ArrayID:LogDate:LogTime:LUN

      One record will be printed for each log entry between the start and
      end times.

      LogFilename is the name of the server log file where the record is
      found.

      The leading AL is literal, and identifies this as an AM60 LOG record.

      AddSenAvailable is a boolean that indicates whether the SenseDate,
      SenseTime and FRUCodeQual are available from the SCSI sense data that
      generates these fields.  If FALSE (0), these fields will be undefined.

      SenseDate and SenseTime correspond to the time of the reported event,
      while LogDate and LogTime correspond to the time when the event was
      written to the log file.	The format of the SenseDate is MMDDYY, while
      that of LogDate is MMDDYYYY.  The format for the SenseTime and LogTime
      is HHMMSS.

      The SCSI sense data fields, FRUCode, SK, ASC,ASCQ, are one byte
      hexadecimal; the FRUCodeQual field is two bytes hexadecimal.

      The LUN field will be appended to the output only if the LUN
      information in the sense data is valid.

      Major Event Log Output

	   AM:LogFilename:ArrayID:LogMonth:LogDay:LogYear:LogHour:LogMin:
	   LogSec:SeqNum:EventType:EventMonth:EventDay:EventYear:



				    - 4 -	  Formatted:  August 2, 2006






 amlog(1M)							   amlog(1M)




	   EventHour:EventMin:EventSec:EventCategory:CompType:
	   LocationValid:CompLocation:EventPriority:SK:ASC:ASCQ:FRUCode:
	   FRUCodeQual:LUN

      One record will be printed for each log entry between the start and
      end times.

      LogFilename is the name of the server log file where  the record is
      found.

      The leading AM is literal, and identifies this as an AM60 LOG record.

      The Log* timestamp indicates when this event was written to the log
      file.

      The Event* timestamp indicates when this event occurred.

      LocationValid is a boolean that indicates whether the CompLocation
      field is valid.

      If LocationValid is TRUE (1), CompLocation indicates an enclosure and,
      if applicable, a slot.  Otherwise, this field is undefined.  If both
      an enclosure and slot are indicated, they will be separated by a
      comma.  The CompType field determines whether the CompLocation field
      will include a slot number.

      SK, ASC, and ASCQ are SCSI sense data, each one byte hexadecimal.

      If  "-c" is specified, only MEL events with an EventPriority of
      CRITICAL will be displayed.

      The final three fields (FRUCode,FRUCodeQual, and LUN) are only
      displayed if the EventType is 0x3101 (Asynchronous Event
      Notification--or AEN).  FRUCode and FRUCodeQual are one and two bytes
      hexadecimal, respectively.  The LUN field is only displayed if valid
      LUN information is available in the AEN sense data.

 DEPENDENCIES
      There are no dependencies for this command.

 AUTHOR
      amlog was developed by HP.

 SEE ALSO
      amdsp(1M), amcfg(1M), amutil(1M), ammgr(1M), AM60Srvr(1M).









				    - 5 -	  Formatted:  August 2, 2006