HP-UX I/O Subsystem EVM Events

ManualsBrandsHP ManualsSoftwareHP Event Monitoring Service Software

HPUX I/O Subsystem EVM Events

1 Introduction ..................................................................................................................................2

2 I/O Terms and Definitions..............................................................................................................2

3 EVM Eventing Mechanism..............................................................................................................3

4 Components of an EVM Event ........................................................................................................4

4.1 Standard Data.......................................................................................................................4

4.2 Variable Data .......................................................................................................................5

5 EVM Events Generated by I/O Subsystem .......................................................................................6

5.1 I/O Node State Change Event ................................................................................................7

5.2 Property Modify Event ............................................................................................................8

5.3 Health Property Modify Event ................................................................................................10

5.4 I/O Node Instance Number Change .....................................................................................11

5.5 Replacement of a Stale Device Special File with a New Device Special File................................12

5.6 Automatic PCI Error Recovery................................................................................................13

6 References .................................................................................................................................15

Summary of content (15 pages)

PAGE 1
HPUX I/O Subsystem EVM Events 1 Introduction ..................................................................................................................................2 2 I/O Terms and Definitions..............................................................................................................2 3 EVM Eventing Mechanism..............................................................................................................3 4 Components of an EVM Event .......................
PAGE 2
1 Introduction The HP-UX I/O subsystem uses the Event management system (EVM) mechanism to report changes in I/O components’ state. The EVM subsystem provides services to distribute, store and retrieve this information. This document provides the details of the EVM events generated by the I/O subsystem. It covers the circumstances during which the event is generated, the format of the events, and the information contained in the event. A generic example of the EVM subsystem is also provided.
PAGE 3
EVM Eventing Mechanism Subscribers Posters sockets Logger Logs sockets EVM Daemon Application processes sockets sockets Application processes Event Viewer /dev/kevm User Q ! KERNEL_ONLY Kernel Subscribers kevm Kernel Posters Kernel Q An EVM subsystem is a means through which any system component or application program can report the status of an operation.
PAGE 4
Components of an EVM Event An EVM event consists of the following fields. 1) The standard data or the fixed data component: The value of the standard data remains constant across different instances of the event. 2) The variable data: Variable data items vary from event to event. A typical EVM event looks as follows. Event Full Name: sys.unix.io.state_change.new_state._class.ccc._instance.iii. _cim.HP_EVMEventIndication Standard Data: Event Name: sys.unix.io.state_change.
PAGE 5
suspended Indicates that the I/O node is suspended. _class.ext_bus Indicates that the I/O node belongs to the class ext_bus. _instance.5 Indicates that the I/O node instance is 5. Format A human readable string that summarizes the event. Priority A description of the order in which the events are delivered to the subscribing clients. Note: The I/O subsystem mainly uses the Name, Format and Priority fields in its posted events.
PAGE 6
5 EVM Events Generated by I/O Subsystem The following table gives the events that are generated by the I/O subsystem based on the operation initiated on an I/O node.
PAGE 7
5.1 I/O Node State Change Event An I/O node is said to change its state when the software state of the node changes. An I/O node can assume the following software states: CLAIMED The I/O node is bound to a driver. UNCLAIMED The I/O node is not bound to any driver. UNUSABLE The hardware at this address has become unusable as a result of some error condition. SUSPENDED The associated hardware and software are in a suspended state.
PAGE 8
The execution of this command causes the software state of the I/O node to change to SUSPENDED. As a result an EVM event is generated. Given below is the output obtained from the evmshow command. EVM event generated after an I/O node changes state Formatted Message: An I/O node "c8xx" at hardware path "0/4/1/1" has changed state. Event Data Items: Event Name: sys.unix.io.state_change.suspended._class.ext_bus._instance.
PAGE 9
Variable Data: node_name type STRING value “” pname type STRING value “” pvalue type EvmTYPE_OPAQUE value plen type UNIT64 value 0 class type STRING value “” _instance type UINT64 value 0 _cim type STRING value “” hw_attr type EvmTYPE_OPAQUE hw_path type STRING value “” Example: The following property modify EVM event is generated when an rmsf is performed on a hardware path. The “id bytes” property of the tgtpath associated with the I/O node is modified.
PAGE 10
5.3 Health Property Modify Event The health property of an I/O node denotes the state of the node as defined by the subsystem that manages this node (for example, the driver). The values that the health property can take are: Online The I/O node is online and is ready to issue or receive I/O tranfers. Offline The I/O node is offline and cannot be accessed. Limited The I/O node is operating in a performance degraded (sub-optimal) state.
PAGE 11
EVM event generated after health property of I/O node is modified Formatted Message: The health property of I/O node "esdisk" has been changed Event Data Items: Event Name: sys.unix.io.health.offline._class.disk._instance.
PAGE 12
EVM event generated when instance number of the I/O node is changed Formatted Message: An I/O node "esdisk" at hardware path "64000/0xfa00/0x2" has changed instance number Event Data Items: Event Name: sys.unix.io.instance_change._instance.200._class.disk._orig_inst ance.
PAGE 13
Example: The following event is generated when the io_redirect_dsf command is used to replace the dev_t of a device special file with the dev_t of a stale device special file. EVM event when stale device special file is replaced by a new device special file Formatted Message: DSF "/dev/disk/disk151" has been replaced with "/dev/disk/disk288" Event Data Items: Event Name : sys.unix.io.devt_changed._class.disk._instance.
PAGE 14
Format : Base I/O event Variable Items: node_name (STRING) = "lba" class (STRING) = "ba" instance (UINT64) = 11 hw_path (STRING) = "1/0/6" cim (STRING) = "HP_DeviceIndication" hw_attr (OPAQUE) = [OPAQUE VALUE: 1282 bytes] Example: The following event is generated if PCI error recovery fails. EVM event generated when PCI error recovery fails Formatted Message: Base I/O event Event Data Items: Event Name: sys.unix.io.pci_er.failed._class.ba._instance.11._cim.
PAGE 15
6 References For more information, see the following documents and man pages: • HP-UX Event Manager Programmer's Guide: HP-UX 11i v3 Edition 1: PCI Error Recovery Product Note: HP-UX 11i v3: • • • • • • • • ioscan(1M) manpage rmsf(1M) manpage ioinit(1M) man page EVM(5) manpage evmget(1) manpage evmshow(1) manpage olrad(1M) manpage io_redirect_dsf(1M) manpage • © 2008 Hewlett-Packard Development Company, L.P.