Operations Sentinel Status User Guide - Public Support Login - Unisys

More documents

Recommendations

Info

Introduction to Components the Event Server Application Program Interface (API). For further information, see the Single Point Operations Administration and Configuration Guide and the Single Point Operations Event Server Application Program Interface Programming Guide. The following examples show attribute change and delete object event reports as they would be specified in a SP-AMS, SMART AMS, or CP-AMS database, or as they would be sent to spo_pipe in the Single Point Operations installation directory: TYPE=AC|CLASS=FileSystem|INSTANCE=/usr|HOST=localhost| Percent Space Used=78|Inodes Free=2345 TYPE=DE|CLASS=FileSystem|INSTANCE=/usr|HOST=localhost The following examples show the same attribute change and delete object event reports as they would be sent by an application using the Event Server API: SPD_ReportValue("FileSystem","/usr","localhost",NULL, NULL,0,2,"Percent Space Used",78,"Inodes Free",2345); SPD_DeleteObject("FileSystem","/usr","localhost",NULL,NULL,0); 1.2.4. Shared Components For a component shared by multiple hosts, such as a shared disk, the attribute values reported for the component may differ for each host. For example, a shared disk may be up on one host and down on another. Therefore, Status maintains a distinct logical component for each host reporting on the component. Status also provides a way to display in one table the logical components representing a single physical component. 1.2.5. How Components Are Identified Components in Status are uniquely identified by a combination of three attributes: • Component name • Component class • Host on which the component resides By using these three attributes, Status can distinguish between two components of the same class and with the same name that reside on different hosts. In addition, two components on the same host can have the same name as long as they are of different classes. For example, a run and a disk drive on the same host can have the same name. For each event report Status receives, it checks the attributes in the event report to determine whether the event applies to a host in the current configuration and a component class in the current classification. Status discards any event report that applies to a host not in the current configuration or to a class not in the current classification. Once a component is created in Status, its name, host, and class cannot change because these are used to identify the component. 1–10 7833 4778–008
1.2.6. Creating Components Introduction to Components A component in the Status data model can be created automatically based on an event report, or operations staff can define it explicitly. A component may be automatically created when Status receives an event report that applies to a component that it is not already modeling. Depending on the component class, Status responds to such an event report either by ignoring it or by adding a new component to its data model. When you define each component class using Single Point Operations Configuration, you specify which action to take. For details, see 7.2. Automatic creation of components is typically used for hardware components. With automatic creation, you do not have to define explicitly all the hardware components to be monitored. On an OS 2200 or MCP system, for example, the data collector collects available data for hardware components and, based on this data, components within Status are automatically created. You may, however, want to define explicitly some of the components to be monitored. One reason for doing this is to specify values for attributes (for example, Expected Status) different from the default values supplied during automatic creation. It is easy to define components explicitly and to save these definitions in named sets that you can retrieve later. For details, see Section 6. 1.2.7. Component Groups A component group is a collection of components that operations personnel have decided to monitor through a single icon in the Status diagram. (See 3.2.) Components in a component group can be selected based on the names of the components, the classes of the components, and the hosts on which the components reside. For information about defining component groups, see 5.1. 1.2.8. Instruction and Note Files Each component in Status can have two associated text files: an instruction file and a note file. These files reside on mass storage, so they remain on the Single Point Operations server indefinitely, across multiple executions of Status. Instruction files enable your site to develop explicit instructions for operators: You can develop a different instruction file for each component, or associate one file with many similar components. For example • A site may have one instruction file that applies to all disk drives. • For tape drives, a site may have one instruction file for reel tapes and another instruction file for cartridge tapes. • A site may have a separate instruction file for every background run or process monitored by Status. For information about creating instruction files and associating them with components, see 6.1. 7833 4778–008 1–11
Page 1: ClearPath Enterprise Servers Operat
Page 4 and 5: NO WARRANTIES OF ANY NATURE ARE EXT
Page 7 and 8: Contents Section 1. Introduction to
Page 9 and 10: Contents 4.2.1. Name...............
Page 11 and 12: Contents 6.1.10. Defining Component
Page 13 and 14: Appendix F. Predefined Icons Suppli
Page 15 and 16: Figures 1-1. Example of a Status Di
Page 17 and 18: Section 1 Introduction to Single Po
Page 19 and 20: Class Description of Status The nex
Page 21 and 22: Figure 1-2. Data Flow to Single Poi
Page 23 and 24: Description of Status [UNIX] The UN
Page 25: • Storage area (memory module)
Page 29 and 30: Section 2 Getting Started This sect
Page 31 and 32: Operating Considerations • TYPE T
Page 33 and 34: 2.1.4. OS 2200 Considerations [OS 2
Page 35 and 36: Operating Considerations The MCP ag
Page 37 and 38: 2.2. Preparing to Use Status Prepar
Page 39 and 40: The following illustration shows th
Page 41 and 42: Setting Up Status • MCPTapeMonx.y
Page 43 and 44: 2.3.3. Resource Sets Setting Up Sta
Page 45 and 46: Setting Up Status combination of cl
Page 47 and 48: 2.4. Starting and Terminating Statu
Page 49 and 50: Starting and Terminating Status 2.4
Page 51 and 52: Changing the Status Environment Ope
Page 53 and 54: Section 3 Status Displays This sect
Page 55 and 56: 3.2. Status Diagram Status Diagram
Page 57 and 58: 3.2.2. How the Status Diagram Is Up
Page 59 and 60: 3.2.4. Pull-Down Menus Status Diagr
Page 61 and 62: 3.2.5. Window Backgrounds Status Di
Page 63 and 64: 3.4. Component Tables Component Tab
Page 65 and 66: Component Tables component is added
Page 67 and 68: Status adds a row at the bottom of
Page 69 and 70: Figure 3-6. Unreported Components T
Page 71 and 72: 3.5. Attribute List Attribute List
Page 73 and 74: Attribute List short time, and then
Page 75 and 76: 3.6. Dialog Windows Dialog Windows
Page 77 and 78:
Section 4 Component Attributes This
Page 79 and 80:
4.1.3. Status Attributes Types of A
Page 81 and 82:
Types of Attributes When the value
Page 83 and 84:
4.2.5. Seen 4.2.6. Notes Attributes
Page 85 and 86:
4.2.9. Event Received Attributes Th
Page 87 and 88:
4.3. Site-Defined Attributes 4.3.1.
Page 89 and 90:
Site-Defined Attributes • The val
Page 91 and 92:
Attributes Specific to the OS 2200
Page 93 and 94:
Attributes Specific to the OS 2200
Page 95 and 96:
Attributes Specific to the MCP Host
Page 97 and 98:
Attributes Specific to the MCP Host
Page 99 and 100:
Section 5 Diagram Definitions A dia
Page 101 and 102:
5.1.2. Capabilities Defining Compon
Page 103 and 104:
Defining Component Groups A window
Page 105 and 106:
Defining Component Groups 5.1.8. Sp
Page 107 and 108:
5.1.10. Adding New Component Groups
Page 109 and 110:
5.1.14. Deleting Default Groups for
Page 111 and 112:
Defining Component Groups Backgroun
Page 113 and 114:
Defining Component Table Templates
Page 115 and 116:
Page 117 and 118:
Page 119 and 120:
5.3. Saving a Diagram Definition Sa
Page 121 and 122:
Changing the Diagram Definition in
Page 123 and 124:
After you select a diagram definiti
Page 125 and 126:
Section 6 Component Sets This secti
Page 127 and 128:
Defining Components Explicitly 6.1.
Page 129 and 130:
Defining Components Explicitly 6.1.
Page 131 and 132:
6.2. Saving Component Set Definitio
Page 133 and 134:
Deleting Component Set Definitions
Page 135 and 136:
Section 7 Defining Classifications
Page 137 and 138:
7.2. Defining Status Classification
Page 139 and 140:
Defining Status Classifications Ret
Page 141 and 142:
Changing Component Class Characteri
Page 143 and 144:
Page 145 and 146:
Page 147 and 148:
Page 149 and 150:
Adding and Deleting Component Class
Page 151 and 152:
7.5. Configuring Site-Defined Attri
Page 153 and 154:
Configuring Site-Defined Attributes
Page 155 and 156:
Configuring Site-Defined Attributes
Page 157 and 158:
7.6. Additional Specifications 7.6.
Page 159 and 160:
Appendix A Troubleshooting This app
Page 161 and 162:
Event Report Logging produced by Si
Page 163 and 164:
A.2. Unreported Components Table Un
Page 165 and 166:
Appendix B Tape Monitor for OS 2200
Page 167 and 168:
B.2. TapeMon Classification [OS 220
Page 169 and 170:
TapeMon Classification [OS 2200] co
Page 171 and 172:
TapeMon Classification [OS 2200] St
Page 173 and 174:
Appendix C Tape Monitor for MCP Hos
Page 175 and 176:
C.2. MCPTapeMon Classification MCPT
Page 177 and 178:
MCPTapeMon Classification • Icon
Page 179 and 180:
Appendix D UNIX Resource Monitor [U
Page 181 and 182:
D.1.4. UnixMon Classification Using
Page 183 and 184:
D.2.2. CPU Class Attribute Descript
Page 185 and 186:
Attribute Description UnixMon Class
Page 187 and 188:
Appendix E Classifications for Clea
Page 189 and 190:
Classifications for ClearPath IX an
Page 191 and 192:
Appendix F Predefined Icons Supplie
Page 193 and 194:
User4_lg User4_sm UserDefinedAsync_
Page 195 and 196:
Predefined Icons Supplied with Sing
Page 197 and 198:
Appendix G Related Product Informat
Page 199 and 200:
Index A adding component class, 7-1
Page 201 and 202:
color coding, 3-4 component classes
Page 203 and 204:
E Edit Components table (figure), 6
Page 205 and 206:
N Name attribute, 4-6 CPU class (ta
Page 207 and 208:
System Types host class characteris
Page 210:
*78334778-008* 78334778-008
show all

Operations Sentinel Status User Guide - Public Support Login - Unisys

Create successful ePaper yourself

Delete template?

Save as template?