Fibre Channel Arbitrated Loop Hub Monitor (dm_fc

Fibre Channel Arbitrated Loop Hub Monitor (dm_fc_hub))

Monitor Description | Configuration Files

Monitor Description

The Fibre Channel Arbitrated Loop Hub monitor is designed to monitor the operation of all supported FC-AL hubs on your system. If a problem is detected with a hub, the monitor immediately sends an event to Event Monitoring Service, which alerts you using the notification methods defined for the monitor. Clear, concise error messages identify the problem, what caused it, and what must be done to correct it.

The Fibre Channel Arbitrated Loop Hub monitor employs polling event detection. At regular intervals, the monitor requests status information from each hub. The monitor then analyzes the data returned to determine if a hardware problem has occurred. If an error has occurred that warrants notification, an event is generated immediately.

The monitor is launched automatically when the system is started, ensuring that all supported FC-AL hubs are protected from undetected hardware failure.

NOTE: Unlike the other EMS Hardware Monitors, the FC-AL hub monitor requires some initial configuration before it will function. Because a FC-AL hub is not part of the host's configuration, the host cannot detect any hubs during startup. You must tell the hub monitor what hubs you want it to monitor. This is done by defining two settings in the hub monitor configuration file, HUB_COUNT and HUB_X_IP_ADDRESS. Refer to "Initial Monitor Configuration" later in this data sheet.

Release History

February 1999 Release: Initial release

Supported Products

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

Special Requirements

The FC-AL Hub monitor requires:

Device Firmware revisions

Device Agent Firmware revision 2.14 or greater

Hub Controller Firmware revision 3.06 or greater

Firmware and installation instructions are available at http://www.software.hp.com

C++ runtime support patches

10.20 PHSS_16585 (supersedes PHSS_14262)

11.00 PHSS_16587 (supersedes PHSS_14577)

Before using the hub monitor, edit the monitor configuration file (/var/stm/config/tools/monitor/dm_fc_hub.cfg) to indicate what hubs will be monitored.

Resource Path

Event monitoring: /connectivity/events/hubs/FC_hub
Status monitoring: /connectivity/status/hubs/FC_hub

Monitor Name

/usr/sbin/stm/uut/bin/tools/monitor/dm_fc_hub

PSM State Control

The set_fixed utility must be used to return a hardware resource to the UP state following a failure. The monitor does not support automatic state control. (See "Using the set_fixed Utility to Restore Hardware UP State" in the EMS Hardware User's Guide.)

Configuration Files
Startup Configuration File (.sapcfg)

Initial Monitor Configuration

Unlike the other EMS Hardware Monitors, the FC-AL hub monitor requires some initial configuration before it will function. Because a FC-AL hub is not part of the host's configuration, the host cannot detect any hubs during startup. You must tell the hub monitor what hubs you want it to monitor. This is done by defining two settings in the hub monitor configuration file, HUB_COUNT and HUB_X_IP_ADDRESS.

To configure the FC-AL monitor configuration file:
Determine which hubs you want the monitor to be responsible for. Record the IP address for each of these hubs.

Open file /var/stm/config/tools/monitor/dm_fc_hub.cfg in an ASCII text editor.
Add the following line to the file:
HUB_COUNT n
Replace n with the value that reflects the number of hubs for which the monitor will be responsible. For example, the following line would monitor five hubs:
HUB_COUNT 5
Add the following line to file:
HUB_X_IP_ADDRESS nn.nn.nnn.nnn
Change the placeholder "X" to the number 1, and replace the "nn" fields with the IP address of the hub that will be designated as hub 1.
The completed line will look similar to the following:
HUB_1_IP_ADDRESS 15.43.214.101
If multiple hubs will be monitored, replicate the line from step 4 for each hub, changing the hub number and IP Address for each. When you are done, the number of lines should equal the number defined in the HUB_COUNT setting. For example, the following lines would configure the monitor for three hubs:
HUB_COUNT 3
HUB_1_IP_ADDRESS 15.43.214.101
HUB_2_IP_ADDRESS 15.43.214.171
HUB_3_IP_ADDRESS 15.43.214.184
Save the file.

To invoke the changes immediately, run the Hardware Monitoring Request Manager (/etc/opt/resmon/lbin/monconfig) and select the (E)nable Monitoring option of the Hardware Monitoring Request Manager, even if monitoring is already enabled. The Enable Monitoring option runs the startup client, which reads the contents of the configuration file and starts the hub monitor to begin monitoring of the FC-AL hubs.
There are other settings in the configuration file that can be changed to customize the operation of the FC-AL hub monitor. These settings are defined in Chapter 5, "Hardware Monitor Configuration Files" in the "EMS Hardware Monitor User's Guide."
Adding or Removing an FC-AL Hub

Adding or removing a hub from the monitor configuration involves changing the same configuration file settings described in the preceding procedure, HUB_COUNT and HUB_X_IP_ADDRESS.

To change the FC-AL hub monitoring configuration:
Determine the IP address for each hub your are adding or deleting.

Open file /var/stm/config/tools/monitor/dm_fc_hub.cfg in an ASCII text editor.
Locate the following line in the file and change value "n" to reflect the new number of hubs to be monitored:
HUB_COUNT n
If you are adding a hub, add the following line to file:
HUB_X_IP_ADDRESS nn.nn.nnn.nnn
Change the placeholder "X" to the number you want assigned to the hub (typically the next sequential number available), and replace the "nn" fields with the IP address of the hub.
The completed line will look similar to the following:
HUB_5_IP_ADDRESS 15.43.214.101
Repeat this step for each hub you are adding.
If you are removing a hub, locate the HUB_X_IP_ADDRESS line for the hub to be removed and delete it from the file. If you deleting multiple hubs, delete the line for each one.

Save the file.

To invoke the changes immediately, run the Hardware Monitoring Request Manager (/etc/opt/resmon/lbin/monconfig) and select the (E)nable Monitoring option. This option runs the startup client, which will cause the changes to the hub monitoring to take effect immediately.
Alternatively you can do nothing and the changes will be made at the next hub polling interval when the monitor recognizes the changes and launches the startup client to invoke them.
Startup Configuration File

File name: /var/stm/config/tools/monitor/dm_fc_hub.sapcfg

Default Entries: The monitor uses the standard default monitor request entries.
Monitor Configuration File (.cfg)
File name: /var/stm/config/tools/monitor/dm_fc_hub.cfg

Default settings:

POLL_INTERVAL 15 minutes

REPEAT_FREQUENCY 1 day (1440 minutes)

SEVERITY_ACTION Notify for all levels

Other Settings

The hub monitor also uses the following settings to configure the SNMP environment used by the hub. Note that two of these settings (HUB_COUNT and HUB_X_IP_ADDRESS) are required to indicate to the monitor what hubs should monitored. Changes that involve adding or deleting hubs to the configuration file while the monitor is running will be invoked at the next polling interval, or following the selection of the (E)nable Monitoring option from the Hardware Monitoring Request Manager (monconfig).

Setting Default Value Description

HUB_COUNT
none Manditory: Identifies the number of hubs (value) the monitor will be responsible for monitoring. This setting is required. Valid values from 0 to 100.

HUB_X_IP_ADDRESS
none Manditory: Identifies the IP address for each hub the monitor will monitor. The "X" placeholder is replaced by the number assigned to the hub, and "IP_address" is replaced by the IP address of the hub. There must be a separate setting for each hub. This setting is required.

SITE_SNMP_
GET_COMMUNITY

public 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.

HUB_X_SNMP_
GET_COMMUNITY SITE_SNMP_GET_COMMUNITY SNMP Get Community for hub X. X values from 1 up to and including HUB_COUNT are attempted.

SITE_LOCATION

none These settings define the text string used to identify the hub 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 contain embedded spaces.

HUB_X_LOCATION SITE_LOCATION Location of hub X. X values from 1 up to and including HUB_COUNT are attempted.

SITE_CONTACT none These settings define the text string used to identify the contact person 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 contain embedded spaces.

HUB_X_CONTACT SITE_CONTACT Contact person for hub X information. X values from 1 up to and including HUB_COUNT are attempted.

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

HUB_X_SNMP_RETRY SITE_SNMP_RETRY SNMP retry value for hub X. Valid values between 2 and 5

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

HUB_X_SNMP_TIMEOUT SITE_SNMP_TIMEOUT SNMP timeout value in seconds for hub X. Valid values between 1 and 5.

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

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

PSM Configuration File (.psmcfg)

File name: /var/stm/config/tools/monitor/dm_fc_hub.psmcfg

Default settings:

MONITOR_RESOURCE_NAME /connectivity/events/hubs/FC_hub

PSM_RESOURCE_NAME /connectivity/events/hubs/FC_hub

MONITOR_STATE_HANDLING NO_UP_CONTROL. UP state will be controlled by the set_fixed(1m) command

DOWN_SEVERITY_THRESHOLD Serious and Critical map to DOWN

Setting	Default Value	Description
HUB_COUNT	none	Manditory: Identifies the number of hubs (value) the monitor will be responsible for monitoring. This setting is required. Valid values from 0 to 100.
HUB_X_IP_ADDRESS	none	Manditory: Identifies the IP address for each hub the monitor will monitor. The "X" placeholder is replaced by the number assigned to the hub, and "IP_address" is replaced by the IP address of the hub. There must be a separate setting for each hub. This setting is required.
SITE_SNMP_ GET_COMMUNITY	public	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.
HUB_X_SNMP_ GET_COMMUNITY	SITE_SNMP_GET_COMMUNITY	SNMP Get Community for hub X. X values from 1 up to and including HUB_COUNT are attempted.
SITE_LOCATION	none	These settings define the text string used to identify the hub 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 contain embedded spaces.
HUB_X_LOCATION	SITE_LOCATION	Location of hub X. X values from 1 up to and including HUB_COUNT are attempted.
SITE_CONTACT	none	These settings define the text string used to identify the contact person 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 contain embedded spaces.
HUB_X_CONTACT	SITE_CONTACT	Contact person for hub X information. X values from 1 up to and including HUB_COUNT are attempted.
SITE_SNMP_RETRY	3	These settings define the SNMP retry value in seconds. The SITE setting is used for all hubs, unless overridden by a HUB_X setting for the specific hub identified by X. Valid values are 1 - 5.
HUB_X_SNMP_RETRY	SITE_SNMP_RETRY	SNMP retry value for hub X. Valid values between 2 and 5
SITE_SNMP_TIMEOUT	2	These settings define the SNMP timeout value in seconds. The SITE setting is used for all hubs, unless overridden by a HUB_X setting for the specific hub identified by X. Valid values are 1 - 5.
HUB_X_SNMP_TIMEOUT	SITE_SNMP_TIMEOUT	SNMP timeout value in seconds for hub X. Valid values between 1 and 5.
HUB_X_IS_MONITORED	1 (Yes)	This setting determines if the indicated hub will be monitored. Valid values are 0 (No) and 1 (Yes).
HUB_X_SYSNAME	none	Identifies the hub's sysname if the hub's system.sysName value is not set.

Top of Page / Diagnostics HOME

URL: http://docs.hp.com/hpux/onlinedocs/diag/ems/emd_fchb.htm
Last updated: Thursday June 10 15:35:15 PDT 2004

POLL_INTERVAL	15 minutes
REPEAT_FREQUENCY	1 day (1440 minutes)
SEVERITY_ACTION	Notify for all levels

MONITOR_RESOURCE_NAME	/connectivity/events/hubs/FC_hub
PSM_RESOURCE_NAME	/connectivity/events/hubs/FC_hub
MONITOR_STATE_HANDLING	NO_UP_CONTROL. UP state will be controlled by the set_fixed(1m) command
DOWN_SEVERITY_THRESHOLD	Serious and Critical map to DOWN