dm_fc_hub man page on HP-UX

Man page or keyword search:  
man Server   10987 pages
apropos Keyword Search (all sections)
Output format
HP-UX logo
[printable version]

dm_fc_hub(1m)							 dm_fc_hub(1m)

NAME
       - monitors fibre channel arbitrated loop hubs

SYNOPSIS
DESCRIPTION
       is  the	hardware  event	 monitor for Fibre Channel Arbitrated Loop Hub
       products. It monitors all instances of the devices for  the  occurrence
       of abnormal events.

       event  monitoring  requests  are	 created using the Hardware Monitoring
       Request Manager (monconfig). Monitoring	requests  for  status  changes
       caused  by events are created using the Event Monitoring Service (EMS).
       Both types of monitoring requests are handled by the EMS.

   Supported Devices
       monitors the following disk devices:

	      Fibre Channel Arbitrated Loop Hub Model A3724A
	      Fibre Channel Arbitrated Loop Hub Model A4839A

   Options
       does not support any options.

   Resource Class Paths
       Event Monitor  /connectivity/events/hubs/FC_hub

       Status Monitor /connectivity/status/hubs/FC_hub

   Additional Configuration Settings
       supports the following additional settings in its configuration file.

       Identifies the number of hubs the monitor will be responsible for moni‐
       toring.
			   This setting is required.

       Identifies  the	IP  address for each hub the monitor will monitor. The
       "X" placeholder is replaced by the number assigned to  the  hub.	 There
       must be a separate setting for each hub. This setting is required.

       These  settings	define	the SNMP community assigned to the hubs
       being
			   monitored. The SITE setting is used for  all
			   hubs,  unless  overridden by a HUB_X setting
			   for the specific hub identified  by	X.  The
			   text string cannot contain embedded spaces.

       Identifies  the hub's location if the hub's system.sysLo‐
       cation value is not set. This value is used as the  hub's
       location	 in  log  messages. The SITE setting is used for
       all hubs, unless overridden by a HUB_X  setting	for  the
       specific hub identified by X. The text string cannot con‐
       tain embedded spaces.

       Identifies the  hub  contact  if	 the  hub's  sys‐
       tem.sysContact  value  is  not  set. This value is
       used as the hub's contact  in  log  messages.  The
       SITE setting is used for all hubs, unless overrid‐
       den by a HUB_X setting for the specific hub  iden‐
       tified by X. The text string cannot contain embed‐
       ded spaces.

       These settings define the SNMP retry  value
       in  seconds.  The  SITE setting is used for
       all hubs, unless overridden by a HUB_X set‐
       ting  for the specific hub identified by X.
       Valid values are 1 - 5.

       These settings define the SNMP time‐
       out  value in seconds. The SITE set‐
       ting is used for	 all  hubs,  unless
       overridden  by  a  HUB_X setting for
       the specific hub	 identified  by	 X.
       Valid values are 1 - 5.

       This setting determines if the indi‐
       cated hub will be  monitored.  Valid
       values are 0 (No) and 1 (Yes).

       Identifies  the hub's sysname if the
       hub's system.sysName  value  is	not
       set.

   Severity Levels
       All  hardware  events are assigned a
       severity level by the monitor. These
       severity	 levels	 reflect the poten‐
       tial impact of the event	 on  system
       operation.  Monitoring  requests are
       created based on the  severity  lev‐
       els.

	      An  event	 that  will  or has
	      already  caused  data   loss,
	      system  down  time,  or other
	      loss  of	service.  Immediate
	      action is required to correct
	      the problem. System operation
	      will  be	impacted and normal
	      use of  the  hardware  should
	      not  continue until the prob‐
	      lem is corrected. If Service‐
	      Guard  is	 installed and this
	      is a critical  component,	 it
	      will  perform a package fail-
	      over.

	      An event that may cause  data
	      loss,  system  down  time, or
	      other loss of service if left
	      uncorrected.    The   problem
	      should be repaired as soon as
	      possible.	  System  operation
	      and normal use of	 the  hard‐
	      ware may be impacted. If Ser‐
	      viceGuard	 is  installed	and
	      this is a critical component,
	      it  will	perform	 a  package
	      fail-over.

	      An  event that could escalate
	      to a more	 serious  condition
	      if not corrected. The problem
	      should be repaired at a  con‐
	      venient  time.  System opera‐
	      tion should not  be  impacted
	      and  normal  use of the hard‐
	      ware can	continue.  If  Ser‐
	      viceGuard
			     is	 installed,
			     it	 will	NOT
			     perform	  a
			     package  fail-
			     over.

	      An event that will not likely
	      escalate to  a  more  serious
	      condition if let uncorrected.
	      The problem can  be  repaired
	      at  a convenient time. System
	      operation will not be  inter‐
	      rupted  and normal use of the
	      hardware	can  continue.	 If
	      ServiceGuard is installed, it
	      will NOT	perform	 a  package
	      fail-over.

	      An  event that occurs as part
	      of the  normal  operation	 of
	      the  hardware.  No  action is
	      required. If ServiceGuard	 is
	      installed,  it  will NOT per‐
	      form a package fail-over.

   Application Usage
       This monitor will be  deprecated	 on
       new server models. Please use System
       Management Homepage (see hpsmh(1M)).

DEPENDENCIES
       Event Monitoring Services (EMS) must
       be installed and running.

AUTHOR
       was developed by HP.

FILES
       Executable.

       The resource dictionary for
			   Describes	the
			   location of var‐
			   ious	  resources
			   in the  resource
			   hierarchy.

       Startup	configuration file contain‐
       ing entries for all
			   monitoring
			   requests.

       Log  file for all monitors using the
       Event Monitoring Service, including
			   Any	errors	are
			   logged here.

SEE ALSO
       monconfig(1m), EMS(5), psmmon(1m)

								 dm_fc_hub(1m)
[top]

List of man pages available for HP-UX

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