HP EMS HARDWARE S B6191-90028 manual Startup Configuration File, File Names

Page 92

Hardware Monitor Configuration Files

Startup Configuration File

Startup Configuration File

Each hardware event monitor has its own startup configuration file which contains the monitoring requests currently defined for the monitor. At startup, following the execution of the ioscan utility, or when using the Hardware Monitoring Request Manager (monconfig) to manage monitoring requests, the entries in the startup configuration file are used to create monitoring requests for the monitor.

Each monitoring request in the startup configuration file is applied to all instances of the monitor's hardware resources. An identical set of default requests are included in the startup configuration file for each monitor.

You modify the contents of the startup configuration file using the Hardware Monitoring Request Manager. When you use the Hardware Monitoring Request Manager to create or manage monitoring requests, the results are stored as an entry in the monitor's startup configuration file. If you have selected the All Monitors option for the request, an entry will be made in the startup configuration file for all the monitors.

NOTE When Do Changes Made to a Startup Configuration File Take Effect?

Changes made to a startup configuration file are invoked when the system is restarted, following the execution of the IOSCAN utility, or when the Hardware Monitoring Request Manager is used to manage monitoring requests. For example, when you add, delete, or modify a monitoring request using the Hardware Monitoring Request Manager, the changes to the startup configuration file will take effect immediately.

File Names

The file naming convention for the startup configuration files is:

/var/stm/config/tools/monitor/monitorname.sapcfg

monitorname is the name of the monitor executable.

File Format

Entries in the startup configuration file use the following conventions:

•The startup configuration file contains monitoring request entries identifying the notification method and reporting criteria for the monitor. Each entry contains records consisting of a keyword, followed by a colon (:), followed by the value assigned to the keyword. For example, Criteria Threshold: INFORMATION

•'MONITOR' must be the first keyword found in each entry, but the remaining records in the entry are not order-dependent. For example:

MONITOR: /storage/events/disk_arrays/FW_SCSI

•Comments begin with the pound character (#) and continue until the end of the line. A comment may occur on a line by itself or after a blank space following the value for a keyword.

For example, either of the following are valid comments:

# Default monitoring entries

Target Type: SYSLOG

# Send events to syslog

Table 5-2 identifies the keywords that make up each entry in the startup configuration file. Each entry must contain the keywords identified as required.

92

Chapter 5

Page 91 Page 93
Image 92
Page 91 Page 93
Contents EMS Hardware Monitors Users Guide Manufacturing Part Number B6191-90028 SeptemberLegal Notices Printing History Page Contents Using the Peripheral Status Monitor Hardware Monitor Configuration FilesSpecial Procedures Contents About This Manual Related Web Site Introduction What is Hardware Monitoring? Hardware Monitoring OverviewHow Does Hardware Monitoring Work? Components Involved in Hardware MonitoringBenefits of Hardware Monitoring Products Supported by Hardware Monitors Tips for Hardware Monitoring Term Definition Hardware Monitoring TermsHardware Monitoring Terms Hardware Monitoring Terms Introduction Hardware Monitoring Overview Chapter Installing and Using Monitors Steps Involved Steps for Installing and Configuring Hardware Monitoring Installing EMS Hardware Monitors Supported System ConfigurationRemoving EMS Hardware Monitors Product Model/Product Special Number Requirements Checking for Special RequirementsDisk Arrays Disk Products Tape Products all supported by the Scsi Tape Devices MonitorHigh Availability Storage Systems Fibre Channel Scsi MultiplexersProduct Model/Product Special Requirements Number Fibre Channel AdaptersFibre Channel Arbitrated Loop FC-AL Hub System Fibre Channel SwitchMemory Interface Cards OthersSome Monitoring Request Examples Using Hardware Monitoring RequestsWhat Is a Monitoring Request? Building a Monitoring Request Running the Monitoring Request Manager To run the Monitoring Request Manager, typeEnabling Hardware Event Monitoring Severity Levels Notification Method Default Monitoring Requests13 Default Monitoring Requests for Each Monitor Listing Monitor Descriptions To list the descriptions of available monitorsViewing Current Monitoring Requests To view or show the current monitoring requestsAdding a Monitoring Request To add a monitoring request14 Monitoring Requests Configuration Settings Setting DescriptionEvent Description MC/ServiceGuard Severity Response Level 15 Event Severity LevelsEvent Severity Levels Example of Adding a Monitoring Request == ADD Comment Modifying Monitoring Requests To modify a monitoring requestVerifying Hardware Event Monitoring Checking Detailed Monitoring Status Events =Retrieving and Interpreting Event Messages Sample Event MessageDeleting Monitoring Requests To delete a monitoring requestTo disable hardware event monitoring Disabling Hardware Event MonitoringDetailed Description Detailed Picture of Hardware Monitoring Hardware Monitoring ArchitectureComponents from Three Different Applications Hardware Monitoring Request ManagerStartup Client EMS Hardware Event MonitorPolling or Asynchronous? Event Monitoring Service EMS Peripheral Status Monitor PSMDirectories and Files Description File Locations1File Locations Startup Process in Detail Monitoring Startup ProcessDisabling Monitoring Asynchronous Event Detection in Detail Event DecodingAsynchronous Event Detection Process Memory Monitor Polling FC-AL Hub and FC Switch Polling ProcessesEvent Polling in Detail Monitoring Polling Process Memory Monitor Polling Process Detailed Picture of Hardware Monitoring Chapter Using the Peripheral Status Monitor Peripheral Status Monitor Overview How Does the PSM Work? Peripheral Status Monitor PSM Components PSM StatesPSM Resource Paths PSM StatusHow Does the PSM Work? Chapter Configuring Package Dependencies using SAM To create a package resource dependencyResourcepollinginterval Resourceupvalue =UP From the Actions menu select Add Monitoring Request Creating EMS Monitoring Requests for PSMTo create a PSM monitoring request Specifying When to Send Event Notify Setting the Polling Interval Polling IntervalMonitoring Request Parameters Determining the Frequency of Events OptionsSelecting Protocols for Sending Events Notify Via Opcmsg ITOCritical Major Minor Normal To set the opcmsg ITOTo set the Snmp trap TCP and UDPTo set the TCP or UDP conditions To set for email notificationAdding a Notification Comment Comment Copying Monitoring Requests To change the monitoring parameters of a request Removing Monitoring Requests To remove monitoring requestsFrom the Actions menu select View Monitoring Request Viewing Monitoring RequestsTo view the parameters for a monitoring request Example 4-1 Example of Using setfixed Using the setfixed Utility to Restore Hardware UP StateTo restore the operating state of a resource to UP Using the Peripheral Status Monitor Hardware Monitor Configuration Files Monitor Configuration Files Monitor Configuration File Entries Setting Values DescriptionFile Names File FormatFrequency must be a Eventnum must be aInterval must be a Sample Global Configuration File Event DefinitionSeverity Action Polling IntervalSample Monitor-Specific Configuration File = Communication Device#POLLINTERVAL Startup Configuration File Startup Configuration File Entries Keyword Values DescriptionUDP Description Entry Default File EntriesDefault Monitoring Requests Peripheral Status Monitor PSM Configuration File Considerations for Modifying the PSM Configuration File PSM Configuration File Fields MonitorresourcenameCritical Downseverityope Example File Entries Special Procedures Fibre Channel Arbitrated Loop Hub Monitor Initial Monitor Configuration Configuring the FC-AL Monitor Configuration FileConfiguration Files Adding or Removing an FC-AL HubSetting Default Description Value This setting is requiredPSM Configuration File Fibre Channel Switch Monitor Adding or Removing an FC Switch Configuring the FC Switch Monitor Configuration FileChanging the FC Switch Monitoring Configuration 2PSM Configuration File Fields Special Procedures 112 Index 114 115
Top Page Image Contents