hwmgr_view man page on OSF1

Man page or keyword search:  
man Server   12896 pages
apropos Keyword Search (all sections)
Output format
OSF1 logo
[printable version]

hwmgr_view(8)							 hwmgr_view(8)

NAME
       hwmgr_view  -  Displays	information about the status of the system and
       its hardware components

SYNOPSIS
       /sbin/hwmgr view cluster

       /sbin/hwmgr  view  devices  [-dsf  device-special-filename]  [-category
       hardware-category] [-member cluster-member-name] [-cluster]

       /sbin/hwmgr view environment

       /sbin/hwmgr view hierarchy [-id hardware-component-id [-instance compo‐
       nent-instance]] [-member cluster-member-name]

       /sbin/hwmgr view timestamps [-reverse] [-a timestamp-attribute...]  [-a
       timestamp-attribute=time]  [-id hardware-component-id] [-category hard‐
       ware-category] [-member cluster-member-name] [-cluster]

       /sbin/hwmgr view transaction [-member cluster-member-name] [-cluster]

OPTIONS
       The following options are available:  Displays  information  about  the
       state  of each cluster member. This command is useful only in a cluster
       environment.  Displays all devices.  All devices on the local host  are
       returned	 by  default,  unless  you  also  specify one of the following
       options: Specifies a hardware category, such as disk or tape  on	 which
       to  perform the operation. Use the hwmgr get category command option to
       display a list of available category names.  Specifies the device  spe‐
       cial  file  for a particular device.  You can obtain the device special
       file name by using the hwmgr show component -full command  option  (see
       the  DSF	 GROUP) or the hwmgr show scsi command option.	Specifies that
       the operation be performed clusterwide.	If this option is  not	speci‐
       fied,  data for the local host is returned.  Specifies the host name of
       a cluster member on which to perform the operation.

	      For the purpose of this command, a device is  considered	to  be
	      any  hardware  component	that  has the dev_base_name attribute.
	      (Otherwise, the documentation uses the generic term component to
	      refer  to	 individual items of hardware such as a network card.)
	      Displays the internal hwmgr environment variable settings, which
	      you  can set in your environment configuration file such as your
	      file. Refer to hwmgr(8)  for  more  information.	 Displays  the
	      hierarchical  relationship of all hardware components. Each com‐
	      ponent is displayed with its descendent components. For example,
	      this  option  displays  SCSI  buses  with	 all  the SCSI devices
	      attached to each bus. If you do not  specify  a  cluster	member
	      name,  this  operation defaults to the local system.  Displays a
	      specific component and all its descendents. Specify  a  hardware
	      identifier  (HWID).   Specifies an instance of a hardware compo‐
	      nent. Some components might be in the hierarchy in more than one
	      place.  For example, SCSI disks on a shared bus might be seen in
	      the hierarchy under two or more buses.  Each entry for the  com‐
	      ponent in the hierarchy is considered a different instance.

	      You  must	 specify  the  -id option when using the -inst option.
	      Specifies the host name of a cluster member on which to  perform
	      the operation.

	      Use  the	hwmgr  view hierarchy command to display the currently
	      registered hardware components that  are	found  in  the	system
	      hierarchy.  Components that have a flagged status are identified
	      in the command output by the following codes:  (!)  warning  (X)
	      critical (-) inactive

	      Refer  to	 the description of the hwmgr status component command
	      for an explanation of these codes in hwmgr_ops(8). See the  Man‐
	      aging  Online Addition and Removal manual for procedures to cor‐
	      rect a component problem.	 Displays time	stamp  attributes  for
	      components, such as their registration time or the time that the
	      most recent event was posted. The timestamp attributes are  dis‐
	      played  in  chronological	 order.	 You can specify the following
	      additional options: Specifies that you want to display the  data
	      in reverse chronological order.  Specifies that you want to dis‐
	      play only timestamps that have the stated attribute. Examples of
	      valid  attributes	 are:  registration_time, start_stop_time, and
	      last_event_time. For example:

	      # hwmgr view timestamp -a registration_time Specifies  that  you
	      want  to	find a specific attribute and value pair.  Examples of
	      valid attributes are:  registration_time,	 start_stop_time,  and
	      last_event_time. An example of the syntax follows:

	      # hwmgr view timestamp -a registration_time="Thu Jun 20 16:00:28
	      2002"

	      You must specify the full time string of day,  date,  time,  and
	      year.   Specifies that you want to display timestamps for a par‐
	      ticular component. You must supply a  HWID  for  the  component,
	      which  you  obtain  by  using  the hwmgr show component command.
	      Specifies that you want to display timestamps for	 a  particular
	      category	of component. You can obtain a list of categories that
	      are available on the system by using the hwmgr get category com‐
	      mand.  Specifies the cluster member on which you want to perform
	      the operation.  Specifies that you want to perform the operation
	      on  all  members of the cluster.	Displays information about the
	      transactions that the hardware management kernel	code  uses  to
	      perform  some  requests,	including  the	status of: The current
	      hardware management transactions, if  any.   The	last  hardware
	      management transaction that was completed.  All requests for the
	      various transactions.

       You can specify the following additional options: Specifies the cluster
       member  on which you want to perform the operation.  Specifies that you
       want to perform the operation on all members of the cluster.

DESCRIPTION
       The commands described in this reference	 page  are  a  subset  of  the
       options	that  you  can use with the hwmgr command. See hwmgr(8) for an
       overview of the commands.

       Use the hwmgr view command option to display information about the sta‐
       tus  of	the system and its hardware components. Each view command pro‐
       vides different output about the components that you specify. Enter the
       view command that best fits your need. Refer to the following pages for
       information on related commands:	 hwmgr_show(8)	-  Describes  commands
       that  enable  you  to  display  information  from  hardware subsystems.
       hwmgr_get(8) - Describes commands that enable you to display  (get)  or
       configure  (set)	 component  attributes and identify component category
       names.  hwmgr_ops(8) - Describes commands that enable  you  to  perform
       administrative  tasks  on  hardware components, such as scanning buses,
       locating components, powering off components, and deleting components.

       See the Hardware Management manual for more  information	 about	compo‐
       nents,  device  special	files,	and a definitive list of the supported
       device names.  This manual provides further examples of	hwmgr  command
       usage and common procedures.

       You  can run some hwmgr commands directly from the SysMan Menu. You can
       also monitor many properties and attributes of components by using  the
       SysMan  Station	GUI. See the System Administration manual for informa‐
       tion about these interfaces.

RESTRICTIONS
       The following notes and restrictions apply:

       When working on a cluster, if you do not	 specify  a  member  name  the
       operation  defaults  to	the  local  member. Some command options might
       require that you specify a member name, but in general it is an option.

ERRORS
       The command returns an int with an errorno from <errno.h>.

EXAMPLES
       These examples have been reformatted for ease of reference.  The actual
       formatted  output  from	commands might be slightly different.  If your
       system is a member of a cluster, use the hwmgr command to send hardware
       management requests to any node in the cluster.	Use the following com‐
       mand to determine the current state of each member of the cluster:

	      # /sbin/hwmgr view cluster

		      Member ID	       State	Member HostName
		      ---------	       -----	---------------
			   1	       UP	rene (localhost)
			  31	       UP	witt
			  24	       UP	freu
			  10	       UP	 rogr  The  following  example
	      displays	 devices   (components	 that	have  a	 dev_base_name
	      attribute) that are connected to the system:

	      # /sbin/hwmgr view devices

	      # hwmgr view devices
	       HWID: Device Name	  Mfg	   Model	    Location
	       ----------------------------------------------------------------------
		  3: /dev/dmapi/dmapi
		  4: /dev/scp_scsi
		  5: /dev/kevm
		 58:	   /dev/disk/dsk0c	      COMPAQ	    BD0366459B
	      bus-0-targ-0-lun-0
		 59:	  /dev/disk/dsk1c	     COMPAQ	    BD0366459B
	      bus-0-targ-1-lun-0
		 60:	    /dev/disk/cdrom0c		COMPAQ	       CD-224E
	      bus-1-targ-0-lun-0
		 61:	   /dev/ntape/tape0	      COMPAQ	     SDT-10000
	      bus-5-targ-0-lun-0
		 66:	  /dev/disk/floppy0c		     3.5in	floppy
	      fdi0-unit-0
		 68: /dev/random
		 69: /dev/urandom

	      The information shown in the output is as follows: The  cluster-
	      wide unique hardware identifier (integer) assigned to the device
	      The device special file name for the device The manufacturer  of
	      the  device,  if provided The vendor's model number, as shown on
	      the device or its enclosure The physical location of the	device
	      as defined by the operating system

	      In the preceding example, no tape device is present and the fol‐
	      lowing command displays no information:

	      # /sbin/hwmgr view devices -cat tape The following example  dis‐
	      plays all devices on a cluster:

	      #	 /sbin/hwmgr  view  devices -cluster HWID: Device Name	   Mfg
	      Model			       Host		      Location
	      --------------------------------------------------------
	       3:      /dev/kevm				 jully	   28:
	      /dev/disk/floppy0c     3.5in  floppy     jully  fdi0-unit-0  40:
	      /dev/disk/dsk0c	 DEC  RZ28M    (C)DEC jully bus-0-targ-0-lun-0
	      41:    /dev/disk/dsk1c	  DEC	 RZ28L-AS     (C)DEC	 jully
	      bus-0-targ-1-lun-0  42:  /dev/disk/dsk2c	  DEC  RZ28	(C)DEC
	      jully  bus-0-targ-2-lun-0	 43:   /dev/disk/cdrom0c   DEC	 RRD46
	      (C)DEC  jully bus-0-targ-6-lun-0 44: /dev/disk/dsk3c   DEC RZ28M
	      (C)DEC phoey bus-1-targ-1-lun-0 45: /dev/disk/dsk4c   DEC RZ28L-
	      AS  (C)DEC  jully	 bus-1-targ-2-lun-0  45: /dev/disk/dsk4c   DEC
	      RZ28L-AS (C)DEC  phoey  bus-1-targ-2-lun-0  46:  /dev/disk/dsk5c
	      DEC RZ29B	   (C)DEC jully bus-1-targ-3-lun-0 46: /dev/disk/dsk5c
	      DEC RZ29B	   (C)DEC phoey bus-1-targ-3-lun-0 47: /dev/disk/dsk6c
	      DEC RZ28D	   (C)DEC jully bus-1-targ-4-lun-0 47: /dev/disk/dsk6c
	      DEC RZ28D	   (C)DEC phoey bus-1-targ-4-lun-0 48: /dev/disk/dsk7c
	      DEC RZ28L-AS (C)DEC jully bus-1-targ-5-lun-0 48: /dev/disk/dsk7c
	      DEC RZ28L-AS (C)DEC phoey bus-1-targ-5-lun-0 49: /dev/disk/dsk8c
	      DEC RZ1CF-CF (C)DEC jully bus-1-targ-8-lun-0 49: /dev/disk/dsk8c
	      DEC RZ1CF-CF (C)DEC phoey bus-1-targ-8-lun-0 50: /dev/disk/dsk9c
	      DEC  RZ1CB-CS  (C)DEC jully bus-1-targ-9-lun-0 .	.  .  The fol‐
	      lowing command enables you to display device information about a
	      particular component by specifying its device special file:

	      # /sbin/hwmgr view devices -dsf /dev/disk/cdrom0
	       HWID:	  DSF Name     Mfg  Model	Location
	       --------------------------------------------------------
		31:  /dev/disk/cdrom0c DEC  RRD47(C)DEC bus-0-targ-4-lun-0 The
	      following example command displays the component hierarchy:

	      #	 /sbin/hwmgr   view   hierarchy	  HWID:	  hardware   hierarchy
	      ------------------------------------
		 1: platform AlphaServer 800 5/500
		 2:   cpu CPU0
		 4:   bus pci0
		 5:	scsi_adapter isp0
		 6:	  scsi_bus scsi0
		18:	    disk bus-0-targ-0-lun-0 dsk0
		19:	    disk bus-0-targ-4-lun-0 cdrom0
		20:	graphics_controller trio0
		 8:	bus eisa0
		 9:	  serial_port tty00
		10:	  serial_port tty01
		11:	  parallel_port lp0
		12:	  keyboard PCXAL
		13:	  pointer PCXAS
		14:	  fdi_controller fdi0
		15:	    disk fdi0-unit-0 floppy0
		16:	network tu0
		17:	network tu1 The following example command displays the
	      partial component hierarchy. Use this command format to  display
	      information about specific components:

	      # /sbin/hwmgr view hierarchy -id 45 HWID: hardware hierarchy

		45:   connection pci0slot15
		70:	ide_adapter ata0
		71:	  scsi_bus scsi6
	       687:	    disk bus-6-targ-0-lun-0 cdrom53
		72:	   scsi_bus  scsi7  If	a component has a status other
	      than good, a status code appears next to its entry in  the  com‐
	      mand  output,  and  the  following  code	definition  string  is
	      appended to the header: (!) warning (X)  critical	 (-)  inactive
	      (see  -status).  For example, the following sequence of commands
	      simulates a CPU problem by forcing the CPU offline. The  CPU  is
	      flagged  in the output as (X)critical: # /sbin/hwmgr offline -id
	      700 hwmgr: CPU1 is now offline # /sbin/hwmgr -view hier -id  700
	      HWID:    hardware	 hierarchy  (!)warning (X)critical (-)inactive
	      (see						      -status)
	      ---------------------------------------------------------------------------
	       700: X cpu CPU1

	      When the CPU comes back online the status code  is  cleared,  as
	      follows:	# /sbin/hwmgr online -id 700 hwmgr: CPU1 is now online
	      # /sbin/hwmgr -view hier	-id  700  HWID:	   hardware  hierarchy
	      ---------------------------------------------------------------------------
	       700:   cpu CPU1

	      If you see such status output, use the -status component command
	      option to view a status summary as described in hwmgr_ops(8) and
	      refer to the Managing Online Addition  and  Removal  manual  for
	      more information.	 The following example displays the hwmgr com‐
	      mand environment variable settings:

	      # /sbin/hwmgr view env HWMGR_DATA_FILE =	"/etc/hwmgr/hwmgr.dat"
	      HWMGR_DEBUG  =  FALSE HWMGR_HEXINTS = FALSE HWMGR_NOWRAP = FALSE
	      HWMGR_VERBOSE = FALSE The following (truncated) example displays
	      all timestamps for all hardware components registered on a small
	      standalone system: # /sbin/hwmgr view timestamps
	       HWID:  Component	       Attribute  Name	      Hostname	  Time
	      occured
	      --------------------------------------------------------------------------------
		  1:   COMPAQ AlphaSe  registration_time    cymro.zk3. Mon Jul
	      22 10:23:20 2002
		  2:  CPU0	      registration_time	   cymro.zk3. Mon  Jul
	      22 10:23:20 2002
		  3:   dmapi	       registration_time    cymro.zk3. Mon Jul
	      22 10:23:20 2002
		  4:  scp	      registration_time	   cymro.zk3. Mon  Jul
	      22 10:23:20 2002
		  5:   kevm	       registration_time    cymro.zk3. Mon Jul
	      22 10:23:20 2002
		  6:  pci1	      registration_time	   cymro.zk3. Mon  Jul
	      22 10:23:20 2002
		  7:   pci1slot7       registration_time    cymro.zk3. Mon Jul
	      22 10:23:20 2002
		  9:  pci1slot9	      registration_time	   cymro.zk3. Mon  Jul
	      22 10:23:20 2002
		 11:   itpsa0	       registration_time    cymro.zk3. Mon Jul
	      22 10:23:24 2002
		 12:  scsi0	      registration_time	   cymro.zk3. Mon  Jul
	      22 10:23:24 2002
		 13:   pci2	       registration_time    cymro.zk3. Mon Jul
	      22 10:23:24 2002 The following example displays timestamps for a
	      specific component, in this case a hard disk: # /sbin/hwmgr view
	      timestamps -id 59 HWID:  Component  Attribute  Name	 Host‐
	      name			    Time		       occured
	      ---------------------------------------------------------------------------
		59:   dsk1	  registration_time	cariad.xxx. Thu Jun 20
	      16:00:28 2002
		59:  dsk1	last_event_time	     cariad.xxx.  Thu  Jun  20
	      16:00:33 2002 The following example displays all components that
	      match a timestamp value for a specific attribute: #  /sbin/hwmgr
	      -view timestamps -a last_event_time="Thu Jun 20 16:00:33 2002" #
	       HWID:   Component    Attribute Name     Hostname	  Time occured
	      ----------------------------------------------------------------------------
		  4:   scp	     last_event_time	 cariad.xxx Thu Jun 20
	      16:00:33 2002
		  5:  kevm	   last_event_time    cariad.xxx  Thu  Jun  20
	      16:00:33 2002
		 36:   tty00	     last_event_time	 cariad.xxx Thu Jun 20
	      16:00:33 2002
		  3:  dmapi	   last_event_time    cariad.xxx  Thu  Jun  20
	      16:00:33 2002
		 38:   tty01	     last_event_time	 cariad.xxx Thu Jun 20
	      16:00:33 2002
		 63:  lp0	   last_event_time    cariad.xxx  Thu  Jun  20
	      16:00:33 2002
		 68:   random	     last_event_time	 cariad.xxx Thu Jun 20
	      16:00:33 2002
		 69:  urandom	   last_event_time    cariad.xxx  Thu  Jun  20
	      16:00:33 2002
		 58:   dsk0	     last_event_time	 cariad.xxx Thu Jun 20
	      16:00:33 2002
		 59:  dsk1	   last_event_time    cariad.xxx  Thu  Jun  20
	      16:00:33 2002
		 60:   cdrom0	     last_event_time	 cariad.xxx Thu Jun 20
	      16:00:33 2002
		 61:  tape0	   last_event_time    cariad.xxx  Thu  Jun  20
	      16:00:33 2002
		 66:   floppy0	     last_event_time	 cariad.xxx Thu Jun 20
	      16:00:33 2002 The following  example  displays  the  transaction
	      information  for the local host: #  /sbin/hwmgr view trans hard‐
	      ware	     management		  transaction		status
	      -----------------------------------------------------------
	      there is no active transaction on this system
		the last transaction initiated from this system was:
		  transaction = general tx lock
		  proposal    = 3835
		  sequence    = 0
		  status      = 0
		the last transaction processed by this system was:
		  transaction = general tx lock
		  proposal    = 3835
		  sequence    = 0
		  status      = 0

	      proposal			      last   status    success	  fail
	      ----------------------------  -----------	 -------  -------
			 Lock member/ 3847  0		 85	  0
			  Modify CDB/ 3838  0		 4	  0
			    Read CDB/ 3834  0		 1	  0
			No operation/ 3835  0		 89	  0
		  Change name - lock/ 3836  0		 0	  0
		Change name - commit/ 3837  0		 0	  0
			      Locate/ 3832  0		 0	  0
				Scan/ 3801  0		 0	  0
	       Unconfigure - confirm/ 3933  0		 0	  0
		Unconfigure - commit/ 3934  0		 0	  0
		    Delete - confirm/ 3925  0		 0	  0
		     Delete - commit/ 3926  0		 0	  0
		  Redirect - confirm/ 3928  0		 0	  0
		  Redirect - commit1/ 3929  0		 0	  0
		  Redirect - commit2/ 3930  0		 0	  0
		      Refresh - lock/ 3937  0		 0	  0
		     Change basename/ 3938  0		 10	  0
			    Unindict/ 3841  0		 0	  0
			      Indict/ 3840  0		 0	  0

FILES
       See hwmgr(8) for more information.

SEE ALSO
       Commands: dop(8), dsfmgr(8), hwmgr_show(8), hwmgr_get(8), hwmgr_ops(8),
       sysman(8), sysman_station(8)

       Files: olar_config(4).

       Misc: olar_intro(5).

       Hardware Management, Managing Online Addition and Removal

								 hwmgr_view(8)
[top]
                             _         _         _ 
                            | |       | |       | |     
                            | |       | |       | |     
                         __ | | __ __ | | __ __ | | __  
                         \ \| |/ / \ \| |/ / \ \| |/ /  
                          \ \ / /   \ \ / /   \ \ / /   
                           \   /     \   /     \   /    
                            \_/       \_/       \_/ 
More information is available in HTML format for server OSF1

List of man pages available for OSF1

Copyright (c) for man pages and the logo by the respective OS vendor.

For those who want to learn more, the polarhome community provides shell access and support.

[legal] [privacy] [GNU] [policy] [cookies] [netiquette] [sponsors] [FAQ]
Tweet
Polarhome, production since 1999.
Member of Polarhome portal.
Based on Fawad Halim's script.
....................................................................
Vote for polarhome
Free Shell Accounts :: the biggest list on the net