unixdev.net


Switch to SpeakEasy.net DSL

The Modular Manual Browser

Home Page
Manual: (OSF1-V5.1-alpha)
Page:
Section:
Apropos / Subsearch:
optional field



hwmgr_ops(8)							 hwmgr_ops(8)



NAME

  hwmgr_ops - Hardware management commands for performing operations on	com-
  ponents

SYNOPSIS

  /sbin/hwmgr command [subsystem] [parameters]

  /sbin/hwmgr locate component [-time seconds]

  /sbin/hwmgr status component -id  hardware-component-id [-member cluster-
  member-name] [-good  | -ngood] [-warning  | -nwarning] [-critical  |
  -ncritical] [-inactive  | -ninactive]

SUMMARY	OF HWMGR OPERATIONAL COMMANDS

  Operational commands are characterized by a subsystem	identifier after the
  command name.	 The current subsystems	are: component,	scsi and name.

  Note that some hwmgr operation commands are available	for more than one
  subsystem. You should	use the	subsystem most closely associated with the
  type of operation you	want to	perform, depending on the parameter informa-
  tion that you	obtained using the view	and show command options.

  Some commands	require	you to specify a subsystem name. However, if you
  specify the identity of a hardware component then you	do not need to
  specify a subsystem name. The	hwmgr command is able to determine the
  correct subsystem on which to	operate, based on the component	identifier.

  The command options are organized by task application, defined in the	COM-
  MAND OPTIONS section.	The list of command options, the subsystems on which
  they operate,	and the	nature of the operation	is shown in the	following
  table:

  ___________________________________________________________________
  Option	 Subsystem		       Operation
  ___________________________________________________________________
  add		name			       Database	management
  delete				       Database	management

		component, name, and scsi
  edit		name, scsi		       Database	management
  locate	component		       Hardware	configuration
  offline	component, name		       OLAR
  online	component, name		       OLAR
  power		component, name		       OLAR
  redirect	scsi			       Hardware	configuration
  refresh	component, scsi		       Database	management
  reload	name			       Driver configuration
  remove	name			       Database	management
  scan					       Hardware	configuration

		component, name, and scsi
  status	component		       Hardware	configuration
  unconfigure	component, name		       Hardware	configuration
  unindict	component		       OLAR
  unload	name			       Driver configuration
  ___________________________________________________________________





COMMAND	OPTIONS

  The following	sections describe the flags and	parameters for each command
  set. The commands are	organized according to typical usage, with the more
  frequently used operations first:

    +  Hardware	Configuration -	Commands that you use to manipulate your
       hardware	configuration. You use these operations	after you have modi-
       fied your hardware configuration	and you	want the modifications to be
       implemented into	the operating system.

    +  Online Addition and Replacement (OLAR) -	Commands that you perform to
       maintain	maximum	system uptime and performance, such as adding addi-
       tional CPUs.

    +  Database	Management - Commands that you use to modify the hardware
       databases. The operating	system uses these databases to store informa-
       tion on the hardware components.

    +  Driver Configuration - Commands that you	use to configure the drivers
       that are	used by	hardware components.

  Hardware Configuration


  Use these commands that you use to manipulate	your hardware configuration
  and implement	any modifications to be	into the operating system. For exam-
  ple, replacing a failed SCSI disk or adding a	tape drive. Associated pro-
  cedures for these operations are provided in the System Administration
  Guide.

  ________________________________________________________
  Command Option   Supported Subsystem
  ________________________________________________________
  delete

		   component, name, scsi
  locate	   component
  redirect	   scsi
  scan

		   component, name, scsi
  status	   component
  ________________________________________________________

  delete
      Use this option to perform the following operation:

	+  Delete the specified	component from all members of the cluster or
	   from	only the member	that you specify.

	+  Remove all instances	of the specified component from	all system
	   databases.

	+  Delete all device special files that	are associated with the
	   specified component.

      When performing a	delete operation you must specify an identifier	for
      the component that you want to delete. You can obtain the	identifier
      for a specific component by using	the various hwmgr show command
      options. Valid identifiers are as	follows:

	+  A hardware identifier (HWID). This parameter	indicates that you
	   want	to perform the operation on the	component subsystem.

	+  A SCSI Device ID (did). This	parameter indicates that you want to
	   perform the operation on the	scsi subsystem.

	+  A component name. This parameter indicates that you want to
	   perform the operation on the	name subsystem.

      When you delete a	hardware component, the	system can no longer access
      that component. However, if deleted components remain connected to the
      system during a reboot, they are automatically renamed and reconfigured
      in the order they	are discovered,	which occurs when the system probes
      buses and	controllers.

      The delete command options are as	follows:

      -did scsi-device-id
	  Specifies The	SCSI device identifier.	If the entry is	not
	  registered in	the kernel with	HWC (only under	unusual	cir-
	  cumstances) the delete option	removes	the entry from the SCSI	data-
	  base without calling the component subsystem.

      -entry hardware-name
	  Specifies the	name of	the hardware persistence entry to delete.

      -id hardware-component-id
	  Specifies the	component on which you want to perform the operation.

      -member cluster-member-name
	  Specifies the	host name of a specific	cluster	member on which	you
	  want to perform the operation.

	  The -member option is	not supported if you specify the -did option
	  and the component is deleted from all	members	in the cluster.

  locate component
      Finds a hardware component.  The locate operation	is designed to help
      you find the physical location a component in the	system.	 How this is
      actually implemented depends on the hardware that	you want to find. If
      the locate operation is directed to a SCSI disk component, the disk
      attempts to flash	its activity light (if available). You can specify
      the following additional options with the	locate option:

      -id hardware-component-ID
	  Specifies the	hardware identifier, an	integer	such as	34.

      -time number
	  Specifies a duration of N seconds for	the light to flash. The
	  default is 30	seconds.

  redirect scsi
      Assigns the device special file names, cluster dev_t values, local
      dev_t values, Logical ID,	and hardware ID	of one hardware	component to
      another. Use this	command	to transfer the	system identity	from one com-
      ponent to	another, equivalent component.You might	use this option	when
      a	disk fails and you want	to replace it with a new disk/

      You must specify a SCSI Device IDs (did) for each	of the following
      options.	You can	obtain these identifiers by using the hwmgr show scsi
      command:

      -src source-did
	  The source component.	The system identity of this component will be
	  transferred to the target device.

      -dest target-did
	  The target component.	This device receives its identity from the
	  source device.

  scan component
      Scans the	system for new hardware	components and,	if a new component is
      found, configures	it.  If	you do not specify any arguments, the
      operation	scans all hardware on the system. The scan component option
      is asynchronous. When you	issue the command it completes immediately,
      although the scan	can still be active in the kernel.

      To test for completion of	a scan,	use the	Event Manager (EVM) evmwatch
      and evmshow commands to monitor for an event with	the following event
      name: sys.unix.hw.scan_completed.	For example:


	   # evmwatch -f '[name	sys.unix.hw.scan_completed]' | evmshow
	   A hardware scan has just completed.

      Alternatively, use the graphical EVM Viewer interface to monitor com-
      pletion of the scan.  (See the EVM(5) reference page for an introduc-
      tion to EVM.)

      You can specify the following additional options with the	scan option:

      -id hardware-component-identifier
	  Specifies the	hardware component identifier (HWID) for the device
	  on which on which to perform the scan	operation.

      -category	hardware-category
	  Specifies the	hardware category, such	as disk	or tape, on which to
	  perform the scan operation.  See also	the -get category option.

      -recurse
	  Performs a recursive scan downward in	the system topology. If	this
	  option is not	specified, the scan operation will not scan recur-
	  sively to hardware components	below the starting component, unless
	  recursion occurs as part of the normal scanning process for the
	  component.  A	bus, for example, is scanned recursively (since	that
	  is how the scan code for a bus is written).  A scan of a platform
	  (CPU)	is not normally	recursive.

      -instance	component-instance
	  Specifies an instance	of a hardware component	on on which to per-
	  form the scan. Some devices might be in the component	hierarchy in
	  more than one	place.	For example, SCSI disks	on a shared bus	are
	  seen in the hierarchy	under two buses.  Each entry for the com-
	  ponent in the	hierarchy is considered	a different instance.

      -member cluster-member-name
	  Specifies the	host name of a specific	cluster	member on which	you
	  want to perform the operation.

      -cluster
	  Specifies that the scan operation is performed on every cluster
	  member.

  scan name
      This operation scans a hardware persistence (database) entry for new
      devices. The scan	name option is asynchronous. When you issue the	com-
      mand it completes	immediately, although the scan can still be active in
      the kernel. To test for completion of a scan, use	the Event Manager
      (EVM) evmwatch and evmshow commands to monitor for an event with the
      following	event name: sys.unix.hw.scan_completed.	For example:


	   # evmwatch -f '[name	sys.unix.hw.scan_completed]' | evmshow
	   A hardware scan has just completed.

      Alternatively, use the graphical EVM Viewer interface to monitor com-
      pletion of the scan.  (See EVM(5)	for an introduction to EVM.)

      -entry hardware-name
	  Specifies the	name of	the hardware persistence entry to scan.

      -member cluster-member-name
	  Specifies the	host name of a specific	cluster	member on which	you
	  want to perform the operation.

      -cluster
	  Specifies that the scan operation is performed on every cluster
	  member.

  scan scsi
      The scan option probes the SCSI hardware for new devices.	 When you add
      a	new device to the system, system you can use the scan scsi option to
      find the new hardware and	configure it. If you do	not specify any	argu-
      ments, the command scans all SCSI	buses on the system.

      The scan scsi option is asynchronous but,	unlike the scan	component and
      scan name	options, you cannot test for completion	of the scan by watch-
      ing for the EVM event; "A	hardware scan has just completed". When	a
      scan detects changes to the SCSI configuration (such as when a newly-
      added device is found) a number of hardware change and registration EVM
      events are posted. Use the graphical EVM Viewer interface	to monitor
      these events when	it is necessary	to know	that a scan is complete	.
      (See EVM(5) for an introduction to EVM.)

      You can specify the following additional options with the	scan scsi
      command. Use the hwmgr show command options to find

      -bus scsi-bus
	  Specifies the	SCSI bus on which you want to perform the scan opera-
	  tion.	 The value is an integer, such as 0 (zero), This integer is
	  part of the component	name for the bus, such as pci0.	 Use the
	  hwmgr	show name command option to determine a	bus name.

      -target scsi-target
	  Specifies the	SCSI target on which you want to perform the scan
	  operation. The value is an integer, such as 5. This integer is part
	  of the valid path to the component, such as 0/5/0 (bus/target/lun).
	  Use the hwmgr	show scsi command option to determine the valid	path

      -lun scsi-lun
	  Specifies the	SCSI logical unit number on which you want to perform
	  the scan operation. The value	is an integer, such as 0 (zero). This
	  integer is part of the valid path to the component, such as 0/5/0
	  (bus/target/lun). Use	the hwmgr show scsi command option to deter-
	  mine the valid path

      -member cluster-member-name
	  Specifies the	host name of a specific	cluster	member on which	you
	  want to perform the operation.

  status component
      Returns a	status display for all components or a specified component.
      Refer to the Managing Online Addition and	Removal	manual,
      olar_config(4), and olar_intro(5)	for more information on	the use	of
      status information.

      The following options are	available:

      -id hardware-component-ID
	  Shows	the status of the component specified by the hardware com-
	  ponent identifier.

      -member cluster-member-name
	  Specifies the	host name of a specific	cluster	member on which	you
	  want to perform the operation.

      -good | -ngood
	  Specifies that you want to return only those components that have a
	  status of either good	or a status other than good. In	the output
	  from the status command option, the status displayed is null (no
	  content) when	a component is good.

      -warning | -nwarning
	  Specifies that you want to return only those components that have a
	  status of either warning or a	status other than warning.

      -critical	| -ncritical
	  Specifies that you want to return only those components that have a
	  status of either critical or a status	other than critical.

      -inactive	| -ninactive
	  Specifies that you want to return only those components that have a
	  status of either in active or	a status other than inactive. In this
	  release, this	status applies only to CPUs managed using Capacity on
	  Demand (COD).

      The output from the status command option	provides you with the follow-
      ing information:

      HWID
	  This field contains the hardware identifier (HWID) of	the com-
	  ponent. Use the hardware identifier with other hwmgr command
	  options (such	as view	component -id).	 You might need	this informa-
	  tion to identify a particular	component.

      HOSTNAME
	  This field contains the name of the host or the cluster member that
	  you specified	by using the -member option.

      STATUS SUMMARY
	  This field specifies four possible conditions	that describe the
	  status of the	component:

	    +  Null  - If there	is no entry in the field, the component	is
	       good.

	    +  Inactive	- The component	is inactive.

	    +  Warning - Warns you that	a component is not in an optimal
	       state but will return automatically to an optimal state.

	       For example, when you take a CPU	off line by using the offline
	       nosave command option, its status changes to a warning state.
	       It is only a warning status because this	CPU is otherwise
	       functional, and will automatically become online	and available
	       after you reboot	the system.

	    +  Critical	- Warns	you that a component is	not in an optimal
	       state and cannot	return automatically to	an optimal state. You
	       must intervene to bring the component back to an	optimal	state
	       (online and available).

	  The status categories	do not necessarily imply that a	hardware com-
	  ponent has failed. They only indicate	the present state of a com-
	  ponent depending on other hwmgr command options that you used.

      ACCESS STATE
	  This field specifies whether a component is on line or off line.
	  Refer	to  the	offline	component command option described in
	  hwmgr_ops(8) for a description of these states.

      STATE
	  This field specifies the following possible states of	the com-
	  ponent:

	    +  Unknown	- The system is	unable to determine the	status of the
	       component. Use other hwmgr command options and diagnostic
	       tools to	determine its status.

	    +  Available - The component is fully functional and ready for
	       use although it might not be currently online.

	    +  Unavailable - The component is unavailable.

	    +  Broken -	The component has failed.

	    +  Limited - The component has limited availability.

	    +  Off - The component is powered off.

      INDICT LEVEL
	  This field specifies the indictment status of	the component, mean-
	  ing that an error analysis tool has marked the component as suspect
	  and potentially failing. The component might need replacement.

	  The value of the INDICT LEVEL	field can:

	    +  (Null)  - The component is not indicted.

	    +  Low  - There is a low probability that this component is	at
	       fault.

	    +  Medium  - There is a medium probability that this component is
	       at fault.

	    +  High  -	There is a high	probability that this component	is at
	       fault.

      NAME
	  The component	name.

  Online Addition and Replacement (OLAR)


  Use these commands to	maintain maximum system	uptime and performance,	such
  as adding a CPU or replacing a failed	CPU. Procedures	for the	operations
  associated with these	commands are included in the Managing Online Addition
  and Removal manual, olar_config(4), and olar_intro(5).

  ____________________________________________________
  Command Option   Supported Subsystem
  ____________________________________________________
  offline	   component, name
  online	   component, name
  power		   component, name
  scan

		   component, name, scsi
  unindict	   component
  ____________________________________________________

  offline
      Specifies	that you want to take the specified component off line.	You
      can specify either a component name, or its hardware identifier (HWID).

      -id hardware-component-ID
	  Identifies the hardware component identifier (HWID) of the device
	  on which to performed	the operation. Specify an integer, such	as
	  52.  You can obtain the HWID of a device by using the	view
	  hierarchy command option.

	  The -id option and the -name option are mutually exclusive.

	  If the component is a	CPU and	there are processes bound to the CPU,
	  a warning message is displayed similar to the	following:
	       hwmgr: Active processes are bound to CPU1.  Use -verbose	for further
		   information.


	  Repeat the command, using the	-verbose option	to obtain details of
	  the bound processes. See RESTRICTIONS	for more information.

      -name hardware-name
	  Identifies the device	on which the operation is performed.  Specify
	  a device name, such as CPU2 (a processor).  You can obtain the name
	  of a device by using the view	hierarchy command option, as
	  described in hwmgr_view(8).

	  The -name option and the -id option are mutually exclusive.

      -nosave
	  Specifies that you do	not want the device's offline status to	per-
	  sist across a	reboot.	 When the system reboots, the device is	back
	  online.

      -force
	  Specifies that you want to force the device into the required
	  state. You might need	to use this option if there are	processes
	  bound	to the CPU by commands such as runon.

      -verbose
	  Specifies that you want to discover and display any impact caused
	  by your off line request. You	can then set the component to an
	  appropriate state before you take it off line.

  online
      Specifies	that you want to bring a component on line. The	options	are
      as follows:

      -id hardware-component-ID
	  Identifies the hardware component identifier (HWID) of the device
	  on which the operation is performed.	Specify	an integer, such as
	  52.  You can obtain the HWID of a device by using theview hierarchy
	  command option.

	  The -id option and the -name option are mutually exclusive.

      -name hardware-name
	  Identifies the device	on which the operation is performed.  Specify
	  a device name, such as CPU2(a	processor).  You can obtain the	name
	  of a device from the view hierarchy command option.

	  The -name option and the -id option are mutually exclusive.

  power
      Applies power to or removes power	from a component. The options are as
      follows:

      -id hardware-component-ID
	  Identifies the hardware component identifier (HWID) of the device
	  on which the operation is performed.	Specify	an integer, such as
	  52.  You can obtain the HWID of a component by using the view
	  hierarchy command option.

	  The -id option and the -name option are mutually exclusive.

      -name hardware-name
	  Identifies the device	on which the operation is performed.  Specify
	  a device name, such as CPU2 (a processor) .  You can obtain the
	  name of a component by using the view	hierarchy command option.

	  The -name option and the -id option are mutually exclusive.

      on|off
	  Switches (or toggles)	the power status of the	component.

  unindict
      Clears a component indictment.

      You can verify the indictment status of a	component using	the status
      component	command	option.

      Although indictment is automatic and determined by using the Compaq
      Analyze error analysis tool, you can optionally examine the indictment
      status and choose	to unindict a device. Typically, an indictment is
      removed only after a problem is thoroughly analyzed and corrective
      action (such as replacing	a component) is	taken. Refer to	the Managing
      Online Addition and Removal manual, olar_config(4), and olar_intro(5)
      for more information.



      -id hardware-component-ID
	  Identifies the hardware component identifier (HWID) of the device
	  on which the unindict	operation is performed.	 Specify an integer,
	  such as 52.  You can obtain the HWID of a device by using the	view
	  hierarchy command option.

      -member cluster-member-name
	  Identifies the host name of the cluster member that includes the
	  indicted component.

  Database Management


  Use these commands to	to modify the hardware databases. The operating	sys-
  tem uses these databases to store information	on the hardware	components.
  For example, supported buses and controllers are recognized on system
  startup and are automatically	configured into	the system. If you want	to
  add an unrecognized device, such as a	prototype in development, you might
  need to use the add name option to add the device to the name	subsystem

  ____________________________________
  Command Option   Supported Subsystem
  ____________________________________
  add		   name
  edit		   name, scsi
  unconfigure	   component, name
  ____________________________________

  add Adds a bus, controller or	device entry to	the name subsystem. The	fol-
      lowing options are available:

      -component_name persistence-name
	  Specifies the	base persistence name that should be used for this
	  persistence entry. For example, scsi is the persistence name for a
	  SCSI adapter.

      -component_num persistence-number
	  Specifies the	persistence number to be associated with this
	  hardware component. For example, the first SCSI bus is 0, making
	  the persistence entry	for the	bus scsi0.

      -component_type BUS|CONTROLLER|DEVICE
	  Specifies the	type for a hardware persistence	entry.

      -parent_name parent-bus/cont
	  Specifies the	persistence name of the	parent bus or controller, at
	  which	location the new entry will persist.  For example, a SCSI bus
	  might	persist	under parent bus tza.

      -parent_num parent-instance number
	  Specifies the	instance number	of the parent bus or controller	of
	  the hardware component. For example, the instance number for a SCSI
	  bus persisting on a parent tza bus might be instance 0, for tza0.

      -slot slot-number
	  Specifies the	slot number occupied by	this hardware component.  For
	  example, a SCSI bus might persist at slot 2 of the tza0 bus (tza0
	  slot 2).

      To add other (generic) types of entries to the name subsystem, the fol-
      lowing additional	options	are available:

      -component_type GENERIC
	  Specifies the	type for a hardware persistence	entry.

      -key string-value
	  Specifies a key used to identify the persistence entry.

      -member cluster-member-name
	  Specifies the	host name of a specific	cluster	member on which	you
	  want to perform the operation.

  edit (name)
      Enables you to update the	name subsystem by modifying the	hardware per-
      sistence of a bus, controller, or	device.	You must specify a hardware
      name using the -entry option.

      The following options are	available:

      -entry hardware-name
	  Specifies the	name of	the hardware persistence entry to edit:

	  [-parent_name	parent-name]
	      Specifies	a changed parent name for this persistence entry.

	  -parent_num parent-instance number
	      Specifies	a changed parent instance number for this persistence
	      entry.

	  -slot_num slot-number
	      Specifies	a changed slot number for this persistence entry.

      -member cluster-member-name
	  Specifies the	host name of a specific	cluster	member on which	you
	  want to perform the operation.

      To edit a	generic	persistence entry, use the following command syntax:



      hwmgr edit name



      -entry hardware-name
	  As for bus, controller, or device above. This	option is mandatory.

      -key string-value
	  Specifies a new value	for the	key for	this persistence entry.

      -member cluster-member-name
	  Specifies the	host name of a specific	cluster	member on which	you
	  want to perform the operation.

  edit (scsi)
      Enables you to assigns a unique name to a	legacy SCSI device that	does
      not have such a name.  You must specify a	SCSI Device ID (did).

      If a SCSI	device does not	provide	a unique name, it is seen as a dif-
      ferent device for	each path from which it	is accessed. Use the edit
      scsi command at every location from which	the device is seen, assigning
      the same name each time. The SCSI	subsystem assigns this name to the
      SCSI device, enabling the	device to be seen as the same device from all
      access paths used. The device will also receive a	unique device special
      file.

      The following options are	available:

      -did scsi-device-id
	  Specifies the	SCSI device identifier.	You can	obtain this identif-
	  ier by using the hwmgr show scsi command. This option	is mandatory

      -uwwid user-wwid-string
	  Specifies a unique user-defined identifier for the device.

      -member cluster-member-name
	  Specifies the	host name of a specific	cluster	member on which	you
	  want to perform the operation.

  unconfigure
      Unconfigures a hardware component.  Unconfiguring	a hardware component
      removes the registration of a component with the running kernel, but
      not the persistence entry	of the component from the databases.

      The following options are	available:

      -entry hardware-name
	  Specifies the	name of	the hardware persistence entry to delete when
	  you want to perform the operation on the name	subsystem.

	  The -entry option is and the -id option are mutually exclusive.

      -id hardware-component-ID
	  Unconfigures database	entries	that have the specified	hardware com-
	  ponent identifier. Use thos option when you want to perform the
	  operation on the component subsystem.

	  The -id option is and	the -entry option are mutually exclusive.

      -instance	component-instance
	  Specifies an instance	of a hardware component	on which to perform
	  the operation. Some devices might be in the component	hierarchy in
	  more than one	place.	For example, SCSI disks	on a shared bus	are
	  seen in the hierarchy	under two buses.  Each entry for the com-
	  ponent in the	hierarchy is considered	a different instance.

	  You can use this option only when you	specify	the -id	option.

      -recurse
	  Performs a recursive operation downward in the system	topology. If
	  this flag is not specified, the operation does not recurse to
	  hardware components below the	starting component.

	  You can use this option only when you	specify	the -id	option.

      -member host_name
	  Performs the operation on the	specified cluster member. If you do
	  not specify a	cluster	member,	the operation is performed on all
	  members of the cluster.

  Driver Configuration


  You use these	commands to configure drivers used by hardware components.

  ____________________________________
  Command Option   Supported Subsystem
  ____________________________________
  refresh	   component, scsi
  reload	   name
  remove	   name
  unload	   name
  ____________________________________

  refresh component
      Deletes all hardware components which are	not currently registered from
      every database.  Use this	command	only if	the system or cluster is set
      up in an optimal configuration and you want to remove obsolete hardware
      entries from all databases. This command removes any devices that	are
      not registered with hardware management at the time that you perform
      the operation.

      The following options are	available:

      -member cluster-member-name
	  Specifies the	host name of a specific	cluster	member on which	you
	  want to perform the operation.

      -cluster
	  Specifies that the scan operation is performed on every cluster
	  member. This is the default behavior.

  refresh scsi
      Deletes all SCSI devices which are not currently registered from every
      database.	Use this command only if the system or cluster is set up in
      an optimal configuration and you want to remove obsolete hardware
      entries from all databases. This command removes any devices that	are
      not registered with hardware management at the time that you perform
      the operation.

      The following options are	available:

      -all
	  Specifies that you want to perform the operation on all SCSI buses.

      -busscsi_bus
	  Specifies a particular SCSI bus on which to perform the operation.

      -did scsi-device-ID
	  Specifies a particular device, using the device identifier, on
	  which	the operation is to be performed.

      -member cluster-member-name
	  Specifies the	host name of a specific	cluster	member on which	you
	  want to perform the operation.

  reload name
      Performs a driver	unload followed	by a load. (See	the unload option.)

      The following options are	available:

      -driver driver-suffix
	  Specifies the	driver to reload.

      [-noconfig]
	  Specifies that the kernel configuration routine is not called	when
	  the driver is	reloaded.

      -member cluster-member-name
	  Specifies the	host name of a specific	cluster	member on which	you
	  want to perform the operation.



  remove name
      Removes a	hardware persistence entry from	the database but does not
      affect any hardware component currently using the	name. This option
      affects only the persistence of the name across reboots.

      The following options are	available:

      -entry [hardware-name| ALL]
	  Specifies the	name of	the hardware persistence to be removed.
	  Specify ALL to remove	all entries.

      -member cluster-member-name
	  Specifies the	host name of a specific	cluster	member on which	you
	  want to perform the operation.

  unload name
      Unloads a	module (usually	a driver) from memory after unconfiguring the
      module. The following options are	available:

      -driver driver-suffix
	  Specifies the	name of	the driver that	is to be unloaded from
	  memory.  For example,	tu, the	driver name for	the tulip network
	  interface card.

      -member cluster-member-name
	  Specifies the	host name of a specific	cluster	member on which	you
	  want to perform the operation.

DESCRIPTION

  The commands described in this reference page	are a subset of	the command
  options available from the hwmgr utility. Refer to hwmgr(8) for more infor-
  mation.

  Use the hwmgr	operational commands to	perform	operations on hardware com-
  ponents. You use the information obtained from other hwmgr commands to
  obtain the appropriate operational command parameters, such as device	iden-
  tifiers. Refer to the	following pages	for information	on related commands:

    +  hwmgr_show(8) - Commands	that enable you	to display information from
       the hardware device databases.

    +  hwmgr_view(8) - Commands	that enable you	to return information about
       the status of the system	and its	hardware devices, such as whether a
       particular disk has a valid I/O path.

    +  hwmgr_get(8) - Commands that enable you to obtain (get) or configure
       (set) device and	component attributes.

  See the System Administration	manual for more	information on device names
  and device special files and for a definitive	list of	the supported device
  names.  You can run some hwmgr commands by using the SysMan Menu, and	you
  can monitor many device properties and attributes by using the SysMan	Sta-
  tion.

RESTRICTIONS

  The following	notes and restrictions apply:

  Currently the	locate component -id command is	implemented only for SCSI
  disks, using the disk	activity indicator light (LED).

  When working on a cluster, if	you do not specify a member name the opera-
  tion defaults	to the local member.

  The -verbose option supports only RAD	binding	or binding to a	CPU by using
  the runon command.

ERRORS

  The command returns an int with an errorno from the <&lt;errno.h>&gt;	header file.

EXAMPLES

  These	examples have been reformatted for ease	of reference.  The actual
  formatted output from	commands might be slightly different.  For examples
  of the command options specific to hot-swap of CPUs, refer to	the Managing
  Online Addition and Removal manual.

   1.  The following command causes the	activity light on component HWID 66
       to flash	for one	minute:


	    # /sbin/hwmgr locate component -id 66 -time	60

       You obtain the HWID using the following command options:


	    # /sbin/hwmgr show scsi -type disk
	     66:  2	   cymro      disk	none	0      1    dsk16  [0/3/0]

   2.  The following command shows the status of all system components.	 Only
       partial output is included here:


	    # /sbin/hwmgr status comp
			     STATUS  ACCESS		INDICT
	     HWID:  HOSTNAME SUMMARY STATE    STATE	LEVEL	NAME
	    ------------------------------------------------------------------------
	       1:  cymro	     online   available	       AlphaServer 800 5/500
	       2:  cymro	     online   available	       CPU0
	       3:  cymro	     online   available	       unknown
	       4:  cymro	     online   available	       kevm


   3.  The following example shows how you can use the redirect	option to
       replace a failed	device (did=3).	This command assumes that:

	 +  You	used the show scsi (or other) option to	obtain the device
	    identifier (did) for the failed device.

	 +  The	replacement device is installed	according to the directions
	    in the Owner's Manual.

	 +  You	used the scan scsi option to probe for and register the
	    device.

	 +  You	used the show scsi option to obtain the	device identifier
	    (did) for the new device and found it to be	53.


	    # /sbin/hwmgr redirect scsi	-src 3 -dest 53

   4.  The following example shows how you check the indictment	status of a
       device, in this case a CPU, and change it if necessary. See the Manag-
       ing Online Addition and Removal manual for information on the indict-
       ment procedure.

       In this case, the Event Manager notified	you that Compaq	Analyze
       indicted	a CPU. The SysMan Station displays a critical event icon (a
       red circle with a slash):

	a.  Use	the following command to show which devices are	not in an
	    optimum state:


		 #  /sbin/hwmgr	status component -ngood	| grep CPU
				  STATUS   ACCESS		 INDICT
		 HWID:	HOSTNAME  SUMMARY  STATE     STATE	 LEVEL	   NAME
		 --------------------------------------------------------------
		   50:	ghent99	  critical offline   available	 medium	 (null)

	    A component	is shown as indicted.

	b.  Use	the following command to obtain	the indictment attributes:


		 #  /sbin/hwmgr	get attr -id 50	-a indicted_probability	-a indicted_urgency
		 indicted_probability =	10
		 indicted_urgency = 5

	c.  Use	the following command to change	the indicted status of a dev-
	    ice:


		 #  /sbin/hwmgr	unindict -id 50
		 hwmgr:	Unindict operation was successful

	d.  Use	the following command to verify	the change of status:


		 #  /sbin/hwmgr	get attr -id 50	| grep indict
		 indicted = 0
		 indicted_probability =	(null)
		 indicted_urgency = (null)

	    The	preceding example, shows that changing the indictment status
	    automatically resets the value of the indicted_probability and
	    indicted_urgency attributes.

   5.  The following command attempts to offline a CPU to which	processes are
       bound by	the runon command:


	    #  /sbin/hwmgr -offline -id	3
	    hwmgr: Active processes are	bound to CPU1.
	    Use	-verbose for further information.

       Use the following command to display more information about the bound
       processes:


	    #  /sbin/hwmgr -offline -id	3 -verbose
	    Warning active processes are bound to CPU1.

		Taking this CPU	offline	will suspend active processes until
		the CPU	is placed back online.

		For your system, a snapshot of the processes which could be
		affected includes:
		   PID	  CPU  USER  COMMAND
		   1256	  1    root  hwmgr
		   1187	  1    root  []
		   1186	  1    root  sh

	       hwmgr: Please use the -force switch if you wish to offline a
	       CPU with	bound processes.

       If you decide that the processes	can be safely terminated, you can
       choose to force the CPU offline as follows:


	    #  /sbin/hwmgr -offline -id	3 -force
	      hwmgr: CPU1 is now offline

       If you bring the	CPU back online, the suspended processes will res-
       tart.

FILES

  Refer	to hwmgr(8).

SEE ALSO

  Commands: dop(8), dsfmgr(8), hwmgr_view(8), hwmgr_get(8), hwmgr_show(8),
  sysman(8), sysman_station(8)

  Files: olar_config(4), processor_sets(4)

  Misc:	olar_intro(5)

  System Administration, Managing Online Addition and Removal