Page of 548
Download Table of ContentsContents Print This PagePrint Bookmark

HP -UX B6941-90001 Administrator's Reference Manual

Management server on hp-ux.
Hide thumbs
   
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494 495 496 497 498 499 500 501 502 503 504 505 506 507 508 509 510 511 512 513 514 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546 547 548
HP OpenView IT/Operations
Administrator's Reference
Management Server on HP-UX
Edition 3
B6941-90001
HP OpenView IT/Operations
Version A.05.00
February 1999

Advertising

   Related Manuals for HP HP-UX B6941-90001

   Summary of Contents for HP HP-UX B6941-90001

  • Page 1

    HP OpenView IT/Operations Administrator’s Reference Management Server on HP-UX Edition 3 B6941-90001 HP OpenView IT/Operations Version A.05.00 February 1999...

  • Page 2: Legal Notices

    Legal Notices Hewlett-Packard makes no warranty of any kind with regard to this manual, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Hewlett-Packard shall not be held liable for errors contained herein or direct, indirect, special, incidental or consequential damages in connection with the furnishing, performance, or use of this material.

  • Page 3

    for DOD agencies, and subparagraphs (c) (1) and (c) (2) of the Commercial Computer Software Restricted Rights clause at FAR 52.227- 19 for other agencies. HEWLETT-PACKARD COMPANY 3404 E. Harmony Road Fort Collins, CO 80525 U.S.A. Use of this manual and flexible disk(s), tape cartridge(s), or CD-ROM(s) supplied for this pack is restricted to this product only.

  • Page 4

    MS Windows® are U.S. registered trademarks of Microsoft Corp. Oracle®, SQL*Net®, and SQL*Plus® are registered U.S. trademarks of Oracle Corporation, Redwood City, California. Oracle Reports™, Oracle7™, and Oracle7 Server™ are trademarks of Oracle Corporation, Redwood City, California. Java™ is a U.S. trademark of Sun Microsystems, Inc.

  • Page 5

    Manual updates may be issued between editions to correct errors or document product changes. To ensure that you receive the updated or new editions, you should subscribe to the appropriate product support service. See your HP sales representative for details. First Edition: June 1996 Second Edition: August 1997...

  • Page 7

    For information on how to install ITO on the management server, see the HP OpenView IT/Operations Installation Guide for the Management Server. For information about upgrading an earlier version of ITO , see the HP OpenView IT/Operations Software Release Notes. For information about ITO concepts, see the HP OpenView IT/...

  • Page 9

    Process names Window/dialog box names Text that you must enter Computer Bold Example Refer to the HP OpenView IT/ Operations Administrator’s Reference and the opc(1M) manpage for more information. You must follow these steps. At the prompt type: rlogin your_name where you supply your login name.

  • Page 10

    Font Type What the Font Type Represents Keyboard keys Keycap Buttons on the user interface. [Button] A menu name followed by a colon (:) Menu means that you select the menu, Items then the item. When the item is followed by an arrow (->), a cascading menu follows.

  • Page 11

    ITO in your own environment. The HP OpenView IT/Operations Installation Guide for the Management Server is for administrators who install ITO software on the management server and perform initial configuration.

  • Page 12

    Managing Your Networks with HP OpenView Network Node Manager is for administrators and operators. It describes the basic functionality of HP OpenView Network Node Manager which is an embedded part of ITO. The HP OpenView ServiceNavigator Concepts and Configuration Guide provides information for administrators who are responsible for installing, configuring, maintaining,...

  • Page 13

    ECS Designer product in the NNM and ITO environments. Advanced Network Security for HP OpenView IT/Operations If you purchase the Advanced Network Security (ANS) extension for HP OpenView IT/Operations , you receive the following additional documentation:...

  • Page 14

    The browser and the manuals are available in the appropriate ITO documentation software bundle. See the HP OpenView IT/Operations Installation Guide for the Management Server for general installation instructions using swinstall. Once the bundle is installed, you can open the library by selecting Online Manuals from the Help menu of any primary ITO window.

  • Page 15

    ITO's Motif GUI online information consists of two separate volumes, one for operators and one for administrators. In the operator's volume, you will find the HP OpenView IT/Operations Quick Start describing the main operator windows. Both volumes include: information you need to perform tasks, whether you are an operator...

  • Page 16

    Java GUI. A web browser opens and displays the help contents. Note that you must first configure ITO to use your preferred browser, see the HP OpenView IT/Operations Installation Guide for the Management Server for more information.

  • Page 17: Table Of Contents

    Installation Tips for DYNIX/ptx Managed Nodes ....63 Installation Tips for HP-UX 10.x and 11.x Managed Nodes ..63 Installation Tips for IRIX Managed Nodes ..... .70 Installation Tips for MPE/iX Managed Nodes .

  • Page 18: Table Of Contents

    NFS Cluster Servers on HP-UX 10.x ......125 NFS Cluster Client on HP-UX 10.x ......126 The ITO Default Operator on HP-UX 10.x and 11.x.

  • Page 19: Table Of Contents

    Contents System Resources adapted by ITO on Novell NetWare ...134 File Tree Layout on Olivetti UNIX Managed Nodes ....135 Standalone Systems or NFS Cluster Servers on Olivetti UNIX .

  • Page 20: Table Of Contents

    De-installing ITO Software from Managed Nodes ....173 Manually De-installing ITO Software from AIX Managed Nodes . . 175 Manually De-installing ITO Software from HP-UX Managed Nodes . .

  • Page 21: Table Of Contents

    Contents Manually De-installing ITO Software from OS/2 Managed Nodes . .175 Manually De-installing ITO Software from Solaris, NCR, and SINIX Managed Nodes ......... .176 Manually De-installing ITO Software from Windows NT Managed Nodes.

  • Page 22: Table Of Contents

    Contents Database Reports ......... . 261 Reports for Administrators.

  • Page 23: Table Of Contents

    Understanding ITO Processes ....... .355 Management Server Processes ......356 Managed Node Processes .

  • Page 24: Table Of Contents

    Secure Networking ......... 369 The RPC Client/Server Connection ......369 Processes and Ports.

  • Page 25: Table Of Contents

    B. Administration of MC/ServiceGuard Overview of HP MC/ServiceGuard ......500 Introducing MC/ServiceGuard ....... .501...

  • Page 26: Table Of Contents

    Man Pages for ITO APIs ........526 Man Pages for the HP OpenView ServiceNavigator ... . . 526...

  • Page 27

    Prerequisites for Installing ITO Agent Software...

  • Page 28

    Prerequisites for Installing ITO Agent Software This chapter lists all supported agents and describes the hardware and software prerequisites for each type of supported agent. This information is provided in order to help you select the correct agent platforms to use as ITO managed nodes.

  • Page 29: Managed Node Requirements, Hardware Requirements

    • 20 MB disk space for the software depot on the NetWare depot server in the SYS:volume • 7 MB additional free RAM on the NetWare server (4 MB for the ITO agent, 1 MB for TI-RPC, and 0.5 to 2 MB for the NetWare Management Agent and XCONSOLE).

  • Page 30: Software Requirements

    (About 20 MB is required during software installation.) Additional swap space: none Additional RAM: none Only PA-RISC version 1.1 is supported on HP-UX 10.x managed nodes. NOTE Windows NT Hardware Requirements The Windows NT systems you select as managed nodes must meet the following minimum hardware requirements: Windows NT 4.0 Workstation or Server...

  • Page 31

    Supported ITO-Agent Operating System Versions Operating System IBM RS/6000 BULL DPX/20 DataCenter/OSx Pyramid SVR4 Digital UNIX DEC Alpha DYNIX/ptx Intel 486 or higher HP-UX HP 9000 Technical Workstations HP-UX HP 9000 Enterprise Servers IRIX Silicon Graphics MPE/iX HP 3000/900 NCR UNIX SVR4 NCR System...

  • Page 32

    ITO supports the remote protocol calls (RPCs) but not the security features. Additional agent platforms may also be supported by HP partners, or directly by HP, either currently or in the near future. For a current list of supported agent platforms, contact your HP representative.

  • Page 33

    ITO management server communicate using DCE by default, however, processes on the agents can communicate with the management server using either DCE or NCS. DCE is the recommended communication mechanism wherever possible. Table 1-2 on page 33 shows which version of DCE is required for a given agent operating system.

  • Page 34

    Prerequisites for Installing ITO Agent Software Managed Node Requirements Operating system. For the supported OS versions, see Table 1-1 on page 31. DCE RPC: • DCE RPC. • For AIX 4.1, it is recommended you install the libc_r.a patch. It can be found on CD-ROM 5765-393, (titled, AIX V4 Update CD-ROM).

  • Page 35

    • IOSJPBASE4xx Japanese Base System Software Requirements for HP-UX 10.x Managed Nodes The following software must be installed on HP-UX 10.x managed nodes: Operating system. For the supported OS versions, see Table 1-1 on page 31. DCE RPC version 1.2.1 or higher on HP-UX 10.x (SD-package: DCE-Core.DCE-CORE-RUN)

  • Page 36

    Managed Node Requirements Software Requirements for HP-UX 11.x Managed Nodes The following software must be installed on HP-UX 11.x managed nodes: Operating system. For the supported OS versions, see Table 1-1 on page 31. DCE RPC version 1.7 or higher on HP-UX 11.x managed nodes.

  • Page 37

    SNMP daemon configured, running and automatically started XCONSOLE configured and running: remote console access (via telnet) must be allowed XCONSOLE.NLM must be installed and configured on each server. XCONSOLE is part of Novell products like Flex-IP or NetWare/IP. Novell NMA 2.1 installed and configured Novell NMA 2.1 is a NetWare add-on product and can be purchased...

  • Page 38

    NetBasic must be installed on NetWare depot servers NetBasic runtime version 6.00j - Build 4.127 or higher is required for NetWare depot server(s) (the systems which are used for the ITO agent software installation). See “Installation Tips for Novell NetWare Managed Nodes” on page 75 for details on how to get and install NetBasic.The valid runtime serial number to be used with...

  • Page 39

    SNMP deamons, snmpd and mib_2. Both must be running when you install the agent software. They ensure that the management server is able to determine the node type of the managed node. If you want to use MIB variable monitoring, both deamonns must continue to run after the installation.

  • Page 40

    Prerequisites for Installing ITO Agent Software Managed Node Requirements Software Requirements for SCO UnixWare Managed Nodes The following software must be installed on SCO UnixWare managed nodes: Operating System. For the supported OS versions, see Table 1-1 on page 31. UnixWare Networking Support Utilities: •...

  • Page 41

    On IRIX 5.3, NCS 1.5.1 package netls_eoe.sw or gr_ncs.sw. On IRIX 6.2, NCS 1.5.1 package license_eoe.sw.netls.server. If neither NCS nor DCE are found on the managed node, ITO installs llbd and lb_admin during ITO software installation. On IRIX 5.3, package eoe1.sw.svr4net with System V compatible networking must be installed.

  • Page 42

    ITO installs llbd and lb_admin during the ITO agent software installation. ARPA/Berkeley Services. The MIB monitoring functionality of ITO requires the snmpd of the HP OpenView platform, or SNMP-based, MIB-I (RFC 1156) or MIB-II (RFC1158) compliant agent software. Software Requirements for Windows NT Managed Nodes...

  • Page 43

    Installing ITO Agents on the Managed Nodes...

  • Page 44

    The installation procedures assume that you have already installed and configured the database and ITO on the management server, as described in the HP OpenView IT/Operations Installation Guide for the Management Server. Chapter 2...

  • Page 45: Overview

    You can check and change the system parameters using the tools listed in Table 2-1 on page 45. Table 2-1 System Administration Tools Operating System Digital UNIX DYNIX/ptx HP-UX IRIX NCR UNIX Olivetti UNIX Pyramid DataCenter/OSx SCO OpenServer Chapter 2...

  • Page 46

    Solaris NCR UNIX SVR4 and SGI have no automated tools. Windows NT system parameters cannot be changed. Table 2-2 on page 46 gives values for kernel parameters on HP-UX managed nodes. Other agent platforms generally require similar values. Table 2-2...

  • Page 47: General Installation Tips For Managed Nodes

    System resource files are, for example, /etc/rc.config.d (HP-UX 10.x and 11.x), /etc/inittab (AIX), and SYSSTART.PUB.SYS (MPE/iX) On HP-UX systems, see the appropriate man pages, for example: dced(1M), rpcd(1M), or llbd(1M). On MPE/iX systems, see the NCS online documentation located at: ncsman.pub.hpncs and manual.pub.hpncs.

  • Page 48

    Do not up or downgrade the OS version of the management server or managed node to a level not supported by ITO. For a list of supported OS versions on the management server, see the HP OpenView IT/Operations Installation Guide for the Management Server, and on the managed nodes, see Table 1-1, “Supported ITO-Agent Operating...

  • Page 49

    • Use a symbolic link. For example, for HP-UX 10.x: ln -s /mt1/OV /opt/OV • Mount a dedicated volume. For example, for AIX: mount /dev/hd4 /usr/lpp/OV Note that for HP-UX systems (versions below 10.00), /etc/update(1M) does not support installation on NFS-mounted file systems.

  • Page 50: Installation Tips To Be Performed On The Management Server, Installation Tips For Unix Managed Nodes

    Avoid interrupting the software installation or de-installation process on managed nodes. Doing so will cause a semaphore file to be left on the management server, and you will not be able to re-invoke the installation. In this case, remove the file manually.

  • Page 51

    ITO Advanced Network Security (ANS) extension, you need to copy the file nsp_pkg.Z, too. For more information on which platforms are supported, see the Advanced Network Security Extension for HP OpenView IT/Operations guide. Tips for NFS Cluster Client Specials The ITO software maintenance process for managed nodes makes the following assumptions about NFS cluster configurations:...

  • Page 52: Installation Tips For Aix Managed Nodes

    -kill The agent software component must also be selected for cluster clients, even if the software is already installed on the cluster server because node-specific directories, symbolic links, mounts etc. are established for each cluster node. You can, however, respond with “n”...

  • Page 53

    Manual AIX Agent Installation In some situations, it may be desirable to install the AIX agent software without using the management server. This manual installation makes it possible to prepare the workstation, so that it is ready to become an ITO managed node when it is later connected to the network.

  • Page 54

    Use the following instructions to install the ITO AIX agent on an AIX system that will become an ITO managed node: 1. Copy the ITO agent package to a temporary directory on the managed node. On the management server, this agent package is located in: /var/opt/OV/share/databases/OpC/mgd_node/vendor/ibm/\ rs6000/aix/A.05.00/RPC_DCE_[TCP|UDP]/opc_pkg.Z If you intend to run ITO Advanced Network Security (ANS) on this node, you also need to copy the file:...

  • Page 55

    58 for ITO agents on AIX Cluster-Client systems after the ITO agent software package has been installed on the AIX Cluster Server system. For more information, see “Manually Activating the ITO Agent on NFS Cluster Clients” on page 169.

  • Page 56: Installation Tips For Aix Managed Nodes Running Sp2/hacmp

    Do not check [Force Update] otherwise the management server will re-install the agent. If the agent is pre-installed on the node, the management server will activate the node, and install the selected components. Note that if the agent software is not pre-installed, this action will install the agent.

  • Page 57

    HACMP (as a boot, service or standby adapter) is available on an HACMP node, it can be used for ITO Agent installation. However, communication with the ITO server must be possible via this additional adapter. There is no need to set up IP aliases or modify shell scripts in this case, and all pre-installation tasks can be skipped.

  • Page 58

    Installing ITO Agents on the Managed Nodes General Installation Tips for Managed Nodes Note that the status of the icon representing the node in Node Bank window does not change color immediately when the node in the HACMP cluster goes down: it will change color only after ITO has determined that it cannot contact the control agent on that node.

  • Page 59

    Problems with IP Aliases in AIX OS One very important consequence of setting the IP alias on the interface is that HACMP no longer works correctly. This is true for all events that deal with IP addresses, such as; acquire service address, acquire takeover address, swap adapter, and so on.

  • Page 60

    Communication failure to message receiver: Connection request rejected (dce/rpc).Buffering messages.(OpC30-3) These entries may safely be ignored. Messages are not lost: they are sent to the ITO server after communication is re-established. This usually takes no more than a few seconds. Installing AIX HACMP Agents...

  • Page 61: Installation Tips For Dec Alpha Nt Managed Nodes

    • The installation script checks if the IP address which is used for the ITO installation is tied to the boot, service, or standby interfaces, and issues a warning if this is the case. However, the installation proceeds nonetheless. • If you select automatic start of ITO agents, the file /etc/inittab is also updated so that the clinit entry remains the last one - as is required by HACMP.

  • Page 62: Installation Tips For Digital Unix Managed Nodes

    For instructions on manually installing the DEC Alpha NT agent, see “Manual Installation: Windows NT Agent” on page 111. Note however that the location on the ITO management server of the opc_pkg.Z, opc_inst.bat, opc_pre.bat, opcsetup.inf, unzip.exe and unzip.txt files for the DEC Alpha NT platform is: /var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/\ alpha/nt/A.05.00/RPC_DCE_TCP...

  • Page 63: Installation Tips For Dynix/ptx Managed Nodes, Installation Tips For Hp-ux 10.x And 11.x Managed Nodes

    Installation Tips for HP-UX 10.x and 11.x Managed Nodes You can install ITO on HP-UX 10.x and 11.x platforms using the advanced features of HP Software Distributor (HP SD-UX) to help reduce installation costs and time. You can use this method to install the ITO agent software package from a software depot on a node other than the ITO management server.

  • Page 64

    Subsequent agent installations then get the package from the local depot. Figure 2-1 Standard ITO Agent Installation Method Wide Area Network Local Area Network (WAN) (LAN) Management Server ITO Node 1 ITO Agent Package ITO Node 2 ITO Node N Key: Data Transmission Chapter 2...

  • Page 65

    Package Key: Creating a Software Depot on a Remote Node To create an HP-UX 10.x or 11.x Software Distributor (SD) Depot for the installation of ITO managed nodes: If you don’t have additional licenses, you can only copy the package locally.

  • Page 66

    (default) or use an SD depot. Manual HP-UX Agent Installation In some situations, it may be desirable to install the ITO HP-UX agent software without using the management server. This manual installation makes it possible to prepare the workstation, so that it is...

  • Page 67

    Copy the ITO agent package to a temporary directory on the If you intend to run ITO Advanced Network Security (ANS) on this node, NOTE you also need to copy the following file from the same directory (HP-UX 10.x/11.x, as appropriate): nsp_pkg.Z b.

  • Page 68

    Install the agent on the node: NOTE For cluster nodes, use swcluster, instead of swinstall, on the cluster server. d. Examine the node’s logfile /var/adm/sw/swagent.log. If • Using an existing SD depot: a. Install the agent on the node: b.

  • Page 69

    /Update ITO Software and Configuration window. Select all components (but do not check [Force Update] otherwise the management server will re-install the agent), then click [OK]. If the agent is pre-installed on the node, the management server will activate the node, and install the selected components. Note that if the agent software is not pre-installed, this action will install the agent.

  • Page 70: Installation Tips For Irix Managed Nodes, Installation Tips For Mpe/ix Managed Nodes

    “RPC Daemon or Local Location Broker Problems and Solutions” on page 422. On MPE/iX 6.0 use NSLOOKUP.HPDCE.SYS to check IP addresses. On HP-UX 10.x management servers, ftp is used to install the MPE/iX agent. In its current release, ITO only supports the domain name service for IP address resolution.

  • Page 71

    Installing ITO Agents on the Managed Nodes General Installation Tips for Managed Nodes configured in RESLVCNF.NET.SYS on the managed node) or, if no name server is running, the management server name must be locally registered in HOSTS.NET.SYS. IP address resolution via Network Directory (NSDIR.NET.SYS) or Probe (and Probe Proxy) is not supported.

  • Page 72

    Installing ITO Agents on the Managed Nodes General Installation Tips for Managed Nodes • If the Add/Modify Node window has been used to select the Automatic Update of System Resource Files option for the managed node, SYSSTART.PUB.SYS is created or updated, (unless it already contains a pre-existing ITO entry).

  • Page 73

    where <my job-stream facility> for example, is Maestro's mstream. If there is no entry for ITO in SYSSTART.PUB.SYS, the automatic software installation will insert an entry for ITO in SYSSTART.PUB.SYS where the major parts look like this: comment <customer-defined stream-facility> OPCSTRTJ.BIN.OVOPC The executable library, SNMPXL.NET.SYS, must be available, and ITO must have execution rights;...

  • Page 74: Installation Tips For Ncr Unix Svr4 Managed Nodes

    Managed Nodes The system name uname -s must not be set to any of the names AIX, Solaris, HP-UX, SCO, DYNIX/ptx, OSF/1, Digital UNIX, Reliant UNIX, SINIX, IRIX, Olivetti, or UnixWare. If the Multi-User version of UNIX is installed, ITO can be installed only after networking package WIN-TCP from NCR UNIX SVR4 is first installed.

  • Page 75: Installation Tips For Novell Netware Managed Nodes

    Differences are noted in the following sections where they occur during the installation. Figure 2-3 on page 76 shows all installation steps made on the ITO management server and on the Novell NetWare depot server. Note that the numbers in the installation steps correspond to numbers of the following instructions.

  • Page 76

    Installing ITO Agents on the Managed Nodes General Installation Tips for Managed Nodes Figure 2-3 Installing the ITO Novell NetWare Agent Package ITO Management Server 1. Admin GUI 1st part: - add NetWare managed nodes - run Actions->Install for all managed nodes;...

  • Page 77

    NetWare depot server. The NetWare Depot Server Phase The NetWare depot server is a NetWare server which installs the ITO agent software on other NetWare servers. It stores the ITO agent depot which contains the installation package opc_pkg. All ITO agents are installed from the depot server.

  • Page 78

    Alternatively, you can obtain NetBasic from the following address: ftp://ovweb.external.hp.com/pub/NetBasic/nbv6.exe NOTE HP OpenView can change the location and/or name of the NetBasic installation file without notice. b. Run NBV6.EXE on the Windows 95 or Windows NT version 4.0, and follow the instructions provided during the NetBasic installation.

  • Page 79

    Developer Environment. You can not develop or compile your own NetBasic script programs. e. After all required NetBasic .NLMs have been successfully installed on the depot server, the Windows 95 or Windows NT 4.0 system is no longer needed. 4. Unzip opc_pkg.z, enter: load unzip sys:/tmp/opc_pkg.Z...

  • Page 80

    ITO agent software. a. On the depot server, execute the command itoinst. The following menu options are displayed: • Install HP IT/Operations Agent for NetWare 4.x installs the ITO agent. • Deinstall HP IT/Operations Agent for NetWare 4.x de-installs the ITO agent.

  • Page 81

    • Exit Installation immediately exits the procedure. b. Select the Install HP IT/Operation Agent for NetWare 4.x option and respond to the prompts. c. Enter the name of the ITO management server. d. Enter the IP address of the ITO management server.

  • Page 82

    NetWare version as 3.x and does not allow selection. The NetWare depot server is listed; note that it can also be an ITO agent for the NetWare server. Any NetWare SFT III systems are also on the list and can be selected in the same way as other Novell NetWare systems.

  • Page 83

    If this is the case the file SYS:ETC/NETINFO.CFG is checked for the string TCPIP. If the string is found you are warned that in order to run ITO server, TCP/IP should be invoked and it is suggested that you also run INETCFG.NLM.

  • Page 84

    The NMA agent is supported by the ITO agent for NetWare server but this functionality requires NMA to be installed on the selected NetWare servers; currently NMA installation is not provided as part of the ITO agent for NetWare server installation • Checks for CLIB The CLIB.NLM version is checked;...

  • Page 85

    ITO managed nodes. Enter: /opt/OV/bin/OpC/opcsw -installed < node_name > 7. Assign your templates to the NetWare managed nodes and distribute the templates, actions, monitors, and commands. See the HP ITO Administrator’s Guide to Online Information for more information about assigning and distributing templates.

  • Page 86

    Changed Configuration Files Each configuration file on the NetWare server that is changed by the ITO installation process (like AUTOEXEC.NCF) is stored in the same directory with the extension .ITO; this is in case you need to restore the old system.

  • Page 87

    NetWare that a service opens its own virtual screen on the console screen. The operator uses this to control the service. The ITO agent opens a separate virtual screen on NetWare server console when started. By selecting the options in the menu of the ITO agent screen the operator is able to start/stop the ITO agents and query the agents status.

  • Page 88: Installation Tips For Olivetti Unix Managed Nodes

    For example, the local file system /bigdisk on the cluster client must be mounted to the exported file system /bigdisk on the cluster server. Some of the logfiles checked by the logfile encapsulator are not, by default, present on Olivetti managed nodes, for example /var/adm/messages.

  • Page 89: Installation Tips For Os/2 Managed Nodes

    Inetd. If Domain Name Service (DNS) is not present on the managed node, it is necessary to add at least the management server and the managed node to the hosts file. This file is located in the directory to which the environment variable ETC is pointing.

  • Page 90

    If it is not running, a warning is displayed along with instructions concerning how to inform the management server manually. 1. Copy the following files from the management server to a temporary directory on the OS/2 managed node: • installation script opcinst.cmd /var/opt/OV/share/databases/OpC/mgd_node/vendor/\ ibm/intel/os2/A.05.00/RPC_DCE_TCP/install/\...

  • Page 91

    See Table 2-3 on page 91 for a list of available response file tokens. The following is an example of a typical response file: INSTALLATION_TMP_DIR C:\TMP OPC_INSTALLATION_DRIVE C: MANAGEMENT_SERVER management.server.com • interactively, by calling the opcinst.cmd command and responding directly to the prompts of the installation script: opcinst.cmd...

  • Page 92: Installation Tips For Pyramid Datacenter/osx Managed Nodes

    For example, the local file system /bigdisk on the cluster client must be mounted to the exported file system /bigdisk on the cluster server. Some of the logfiles checked by the logfile encapsulator are not, by default, present on Pyramid managed nodes, for example /var/adm/badlog.

  • Page 93: Installation Tips For Sco Openserver Managed Nodes, Installation Tips For Sco Unixware Managed Nodes

    For example, local file system /bigdisk on cluster client must be mounted to exported file system /bigdisk on cluster server. Some of the logfiles that are observed by the ITO logfile encapsulator are not present by default on UnixWare managed nodes, for example the logfile /var/adm/messages.

  • Page 94: Installation Tips For Sinix Managed Nodes

    For example, the local file system /bigdisk on the cluster client must be mounted to the exported file system /bigdisk on the cluster server. Some of the logfiles checked by the logfile encapsulator are not, by default, present on SINIX managed nodes, for example: /var/adm/loginlog.

  • Page 95: Installation Tips For Solaris Managed Nodes

    If you want to configure the Domain Name Server (DNS) on a SINIX managed node, in addition to editing the /etc/resolv.conf file, you will need to add the line: <nodename> (uname -n) to the following files: • /etc/net/ticlts/hosts • /etc/net/ticots/hosts •...

  • Page 96

    Manual Solaris Agent Installation In some situations, it may be desirable to install the Sun Solaris agent software without using the management server. Manual installation prepares the workstation to become an ITO managed node when it is later connected to the network. This is useful if many workstations are...

  • Page 97

    Do not check [Force Update] otherwise the management server will NOTE re-install the agent. If the agent is pre-installed on the node, the management server will activate the node, and install the selected components. Note that if the agent software is not pre-installed, this action will install the agent.

  • Page 98

    1. After manually installing the agent on the node, enter: /opt/OV/bin/OpC/install/opcactivate <ITO_mgt_server>\ -cs <server_codeset> -cn <agent_codeset> The agent then attempts to send messages to the management server. For more information about codesets, see Chapter 8, “ITO Language Support,” on page 333.

  • Page 99: Installation Tips For Windows Nt Systems

    NT systems. There are four installation procedures that you can use depending on the network configuration as described in Table 2-4 on page 99: In this manual, a Windows NT installation server is a primary or NOTE backup domain controller with the ITO agent package installed.

  • Page 100

    111 installation a. A standard installation procedure requires the HP ITO account on the installation server in a trusted domain to have administrative rights in the trusting domain. Trust refers to a relationship between Windows NT domains, in which one domain is aware of the users in another domain, and can assign rights to those users.

  • Page 101: Installation Requirements

    Domain 1 Installing ITO Agents on the Managed Nodes ftp installation Stand-alone Windows NT System Possible only if Domain 2 gives administrative rights to the HP ITO account in Domain 1 Primary or Backup Domain Controller standard installation Windows NT...

  • Page 102

    -l fileset OVOPC-CLT.OVOPC-NT-CLT • If your installation includes 35 or less NT managed nodes, use the setting for the kernel parameter maxfiles given in the HP OpenView IT/Operations Installation Guide for the Management Server. If your installation includes more than 35 NT managed nodes, increase the setting of maxfiles by:...

  • Page 103

    Use these instructions for your first Windows NT agent package installation, or if you need to create an installation server in a domain that does not give administrative rights to the HP ITO account on an installation server in another domain.

  • Page 104

    • Installation Server: leave this field blank. An installation server is not available for this domain (you are creating one with this procedure), and any entry here will create an error message when the installation script runs.

  • Page 105

    The script will set up the domain controller as the Windows NT managed node that can also function as the installation server for all other NT nodes. 16. The installation is complete when you see the line Installation program successfully finished.

  • Page 106

    General Installation Tips for Managed Nodes You can also verify the installation by checking the NT services window and looking for the entry HP ITO Agent, which should be running, and the HP ITO installation service, which will not be running.

  • Page 107

    For more information on rights and permissions for the HP ITO account, see “The HP ITO Account” on page 114.

  • Page 108

    (and is in the same domain, or has administrative rights for the HP ITO account in this domain). This example uses the system ntserver.com • If Service Pack 1 or 2 is installed on your Windows NT version 3.51 or 4.0 managed node, change the communication type from...

  • Page 109

    When installing the agent on another domain controller, use the password of the HP ITO account on the domain controller where you first installed the agent software. The installation script will then install the agent package on the NT workstation.

  • Page 110

    Installing ITO Agents on the Managed Nodes General Installation Tips for Managed Nodes If an installation server is already available, and you want to re-install or upgrade ITO agent software on additional Windows NT nodes, see “Standard Agent Package Installation” on page 106.

  • Page 111

    Manual Installation: Windows NT Agent In some situations, it may be desirable to install the ITO NT agent software on an NT PC without using the management server. This pre- installation makes it possible to prepare the PC, so that it is ready to become an ITO managed node when it is later connected to the network.

  • Page 112

    To install the NT agent on an NT PC that will become an ITO managed node: 1. Copy the files listed below from: /var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/\ [intel | alpha]/nt/A.05.00/RPC_DCE_TCP/ on the ITO management server, to the C:\temp directory of the managed node: • opc_pkg.Z (rename this file to opc_pkg.zip) • opc_pre.bat • unzip.exe •...

  • Page 113

    4. Run the setup batch file on the NT PC from a command prompt: cd \temp opc_pre.bat 5. On the management server, add the NT node to the appropriate node group. 6. When the NT PC is connected to the ITO management server, update...

  • Page 114: The Hp Ito Account

    The HP ITO Account The standard installation of the ITO agent package on a Windows NT managed node installs the HP ITO account by default as a member of the administrators group and consequently gives the account all those user rights that are available under Windows NT. Although it is...

  • Page 115

    File Tree Layouts on the Managed-Node Platforms...

  • Page 116

    File Tree Layouts on the Managed-Node Platforms This chapter provides file trees to show the directory structures on all Managed Node platforms supported by ITO. These are as follows: DEC Alpha NT Digital UNIX (OSF/1) HP-UX 10.x/11.x MPE/iX NCR UNIX SVR4 Novell NetWare Olivetti UNIX...

  • Page 117

    File Tree Layouts on the Managed-Node Platforms NFS cluster clients and server systems, where appropriate For detailed information about the directory contents, see the opc(5) page. Note that all man pages reside on the management server. Chapter 3...

  • Page 118: File Tree Layout On Aix Managed Nodes, Standalone System Or Nfs Cluster Server On Aix

    NFS Cluster Client on AIX AIX cluster clients (both diskless, dataless, and diskpoor) are those AIX systems that have /usr file system NFS mounted. Their cluster server is the system to which /usr is mounted. No additional mounts are required on cluster clients on AIX by ITO version A.02.00 and later.

  • Page 119: Ito Default Operator On Aix, System Resources Adapted By Ito On Aix

    ITO Default Operator on AIX The ITO default operator, opc_op, owns /home/opc_op as home directory. By default, the operator uses the Korn Shell (/bin/ksh) and is not allowed to log into the system directly (* entry in /etc/passwd). System Resources Adapted by ITO on AIX ITO applies changes in the following system resource files: /etc/passwd and /etc/security/passwd - entry for ITO default operator...

  • Page 120: File Tree Layout On Dec Alpha Nt Manged Nodes

    File Tree Layouts on the Managed-Node Platforms File Tree Layout on DEC Alpha NT Manged Nodes File Tree Layout on DEC Alpha NT Manged Nodes Figure 3-2 ITO Software on DEC Alpha NT Managed Nodes <node> alpha utils ITO Default Operator on DEC Alpha NT Managed Nodes Information concerning default ITO operators for DEC Alpha NT is the same as the information concerning default ITO operators for Windows...

  • Page 121: Alpha Nt Managed Nodes

    File Tree Layouts on the Managed-Node Platforms File Tree Layout on DEC Alpha NT Manged Nodes System Resources Adapted by ITO on DEC Alpha NT Managed Nodes Information concerning adapted system resources for DEC Alpha NT is the same as the information concerning adapted system resources for Windows NT on intel and is described in “System Resources Adapted by ITO on Windows NT”...

  • Page 122: File Tree Layout On Digital Unix Managed Nodes

    Digital UNIX In general, standalone systems are treated as cluster servers. The cluster server exports the /usr/opt or /usr file system with read-only permissions. ITO software is located on the /usr/opt/OV path, with the logical path name the same as the physical path-name.

  • Page 123: Nfs Clients On Digital Unix, The Ito Default Operator On Digital Unix

    NFS Clients on Digital UNIX Digital UNIX cluster clients are those Digital UNIX systems that have the /usr/opt or /usr file system NFS mounted. Their cluster server is the system to which /usr/opt or /usr is mounted and must also be a system running Digital UNIX.

  • Page 124: System Resources Adapted By Ito On Digital Unix

    File Tree Layouts on the Managed-Node Platforms File Tree Layout on Digital UNIX Managed Nodes System Resources Adapted by ITO on Digital UNIX ITO makes changes in the following system resource files during installation: /etc/passwd and /etc/shadow (if present), Protected Password Database (if present) - entry for the default ITO operator /etc/group - group entry for the default ITO operator /sbin/init.d/opcagt - ITO startup/shutdown script...

  • Page 125: File Tree Layout On Hp-ux 10.x And 11.x Managed Nodes

    ITO Software on HP-UX 10.x and 11.x Managed Nodes <lang> If HP OpenView NNM is also installed on the managed node, only those directories displayed in bold-face type are created by ITO. On the management server (which also acts as a managed node) the software trees shown above is combined with the management server file...

  • Page 126: Nfs Cluster Client On Hp-ux 10.x

    The cluster server exports the file system shown in Figure 3-5 to the cluster clients. You can configure cluster clients for HP-UX 10.01 and above using SAM. NOTE Figure 3-5 Exported File System From HP-UX 10.x Cluster Server to Cluster...

  • Page 127: The Ito Default Operator On Hp-ux 10.x And 11.x

    File Tree Layout on HP-UX 10.x and 11.x Managed Nodes The ITO Default Operator on HP-UX 10.x and 11.x The ITO default operator, opc_op, owns /home/opc_op as home directory. By default, the operator uses the Korn Shell (/usr/bin/ksh) and is not allowed to log into the system directory (a * entry is made for the password in /etc/passwd).

  • Page 128: File Tree Layout On Mpe/ix Managed Nodes, Ito Default Operator On Mpe/ix

    Application Desktop or the administrator’s Application Bank, to an MPE/iX managed node. The vt3k operation requires the HP Network Services (NS) node name of the remote HP 3000. However, nodes selected from the map are identified by the ARPA hostname.

  • Page 129

    file below to avoid this problem: /etc/opt/OV/share/conf/OpC/mgmt_sv/vt3k.conf This file can be a symbolic link to /etc/xnmvt3k.conf or the file below, used by ITO for remote logins on HP 3000 systems via vt3k: /etc/opt/OV/share/conf/xnmvt3-k.conf ITO resolves the ARPA host name to NS node name as follows: 1.

  • Page 130

    File Tree Layout on MPE/iX Managed Nodes Figure 3-7 ARPA to NS Node Name Mapping #ARPA NS node name #---------------------------------------------------------------------- hpbbli smarty hpsgmx18.sgp.hp.com hpsgmx18.sgp.hpcom topaz.sgp.hp.com nstopaz.mis.hpsg Comment #different node names #but same domain #same node names, but #Managed Node belongs to...

  • Page 131: File Tree Layout On Ncr Unix Svr4 Managed Nodes

    NFS Cluster Client on NCR UNIX SVR4 NCR UNIX cluster clients are those NCR UNIX systems that have /opt file system NFS mounted. Their cluster server is the system to which /opt is mounted and must also be a system running NCR UNIX.

  • Page 132: The Ito Default Operator On Ncr Unix Svr4

    File Tree Layouts on the Managed-Node Platforms File Tree Layout on NCR UNIX SVR4 Managed Nodes The ITO Default Operator on NCR UNIX SVR4 The ITO default operator, opc_op, owns /home/opc_op as home directory. By default, the operator uses the Bourne Shell (/bin/sh) and is locked until the passwd(1M) command is executed.

  • Page 133: File Tree Layout On Novell Netware Managed Nodes, Ito Default Operator On Novell Netware

    File Tree Layout on Novell NetWare Managed Nodes Figure 3-9 ITO Software on Novell NetWare Managed Nodes SYS:OPT/OV <lang> During installation, ITO creates the opc_op account which has the same security level as the user ADMIN. This account is a normal user account and is used to execute applications.

  • Page 134: System Resources Adapted By Ito On Novell Netware

    file <mng_server_name> <IP_address> is added when you answer (Y)es to the question “Do you want to add the ITO management server to SYS:ETC/HOSTS file?” if this line is not already present in the HOSTS file Entry...

  • Page 135: File Tree Layout On Olivetti Unix Managed Nodes

    Standalone Systems or NFS Cluster Servers on Olivetti UNIX In general, standalone systems are treated as cluster servers. The cluster server exports the /opt file system with read-only permissions. ITO software is located on the /opt/OV path, with the same logical and physical path names.

  • Page 136: Nfs Cluster Clients On Olivetti Unix, The Ito Default Operator On Olivetti Unix

    NFS Cluster Clients on Olivetti UNIX Olivetti UNIX cluster clients are those Olivetti UNIX systems that have the /opt file system NFS mounted. Their cluster server is the system to which /opt is mounted and must also be a system running Olivetti UNIX.

  • Page 137: System Resources Adapted By Ito On Olivetti Unix

    System Resources Adapted by ITO on Olivetti UNIX ITO makes changes in the following system resource files during installation: /etc/passwd and /etc/shadow (if present), Protected Password Database (if present) - entry for the default ITO operator /etc/group - group entry for the default ITO operator /etc/init.d/opcagt - ITO startup/shutdown script /etc/rc0.d - file K09opcagt created /etc/rc1.d - file K09opcagt created...

  • Page 138: File Tree Layout On Os/2 Manged Nodes, Ito Default Operator On Os/2 Managed Nodes

    File Tree Layouts on the Managed-Node Platforms File Tree Layout on OS/2 Manged Nodes File Tree Layout on OS/2 Manged Nodes Figure 3-11 ITO Software on OS/2 Managed Nodes install ITO Default Operator on OS/2 Managed Nodes OS/2 does not support a user concept so that no ITO default operator exists on OS/2 managed nodes.

  • Page 139: File Tree Layout On Pyramid Datacenter/osx Managed Nodes

    Pyramid DataCenter/OSx In general, standalone systems are treated as cluster servers. The cluster server exports the /opt file system with read-only permissions. ITO software is located on the /opt/OV path, with the logical path name the same as the physical path name.

  • Page 140: Nfs Cluster Clients On Pyramid Datacenter/osx, The Ito Default Operator On Pyramid Datacenter/osx

    Pyramid DataCenter/OSx cluster clients are those Pyramid DataCenter/OSx systems that have the /opt file system NFS mounted. Their cluster server is the system to which /opt is mounted and must also be a system running Pyramid DataCenter/OSx. The ITO Default Operator on Pyramid...

  • Page 141: System Resources Adapted By Ito On Pyramid Datacenter/osx

    File Tree Layout on Pyramid DataCenter/OSx Managed Nodes Field Group-ID 177 or higher Users opc_op Description ITO default operator group System Resources Adapted by ITO on Pyramid DataCenter/OSx ITO makes changes in the following system resource files during installation: /etc/passwd and /etc/shadow (if present), Protected Password Database (if present) - entry for the default ITO operator /etc/group - group entry for the default ITO operator /etc/init.d/opcagt - ITO startup/shutdown script...

  • Page 142: File Tree Layout On Sco Openserver Managed Nodes

    SCO OpenServer In general, standalone systems are treated as cluster servers. The cluster server exports the /opt file system with read-only permissions. The ITO software is located in the /opt/OV path, with the same logical and physical path names.

  • Page 143: Nfs Cluster Clients On Sco Openserver, The Ito Default Operator On Sco Openserver

    NFS Cluster Clients on SCO OpenServer SCO OpenServer cluster clients are those SCO OpenServer systems that have the /opt file system NFS mounted. Their cluster server is the system to which /opt is mounted and must also be a system running SCO OpenServer.

  • Page 144: System Resources Adapted By Ito On Sco Openserver

    File Tree Layouts on the Managed-Node Platforms File Tree Layout on SCO OpenServer Managed Nodes Field Group-ID 77 or higher Users opc_op Description ITO default operator group System Resources Adapted by ITO on SCO OpenServer ITO makes changes in the following system resource files during installation: /etc/passwd and /etc/shadow (if present), Protected Password Database (if present) - entry for the default ITO operator...

  • Page 145: File Tree Layout On Sco Unixware Managed Nodes

    SCO UnixWare In general, standalone systems are treated as cluster servers. The cluster server exports the /opt file system with read-only privileges. The ITO software is located in the /opt/OV path, with the same logical and physical path names.

  • Page 146: Nfs Cluster Clients On Sco Unixware, The Ito Default Operator On Sco Unixware

    NFS Cluster Clients on SCO UnixWare SCO UnixWare cluster clients are those SCO UnixWare systems that have the /opt file system NFS mounted. Their cluster server is the system to which /opt is mounted and must also be a system running SCO UnixWare.

  • Page 147: System Resources Adapted By Ito On Sco Unixware

    System Resources Adapted by ITO on SCO UnixWare ITO makes changes in the following system resource files during installation: /etc/passwd and /etc/shadow (if present), Protected Password Database (if present) - entry for the default ITO operator /etc/group - group entry for the default ITO operator /etc/init.d/opcagt - ITO startup/shutdown script /etc/rc0.d - file K09opcagt created /etc/rc1.d - file K09opcagt created...

  • Page 148: File Tree Layout On Sequent Dynix/ptx Managed Nodes, On Sequent Dynix/ptx

    Sequent DYNIX/ptx In general, standalone systems are treated as cluster servers. The cluster server exports the /opt file system with read-only permissions. ITO software is located on the /opt/OV path, with the logical path name the same as the physical path-name.

  • Page 149: Nfs Cluster Clients On Dynix/ptx, The Ito Default Operator On Sequent Dynix/ptx

    NFS Cluster Clients on DYNIX/ptx Sequent DYNIX/ptx cluster clients are those DYNIX/ptx systems that have the /opt file system NFS mounted. Their cluster server is the system to which /opt is mounted and must also be a system running Sequent DYNIX/ptx.

  • Page 150: System Resources Adapted By Ito On Sequent Dynix/ptx

    File Tree Layouts on the Managed-Node Platforms File Tree Layout on Sequent DYNIX/ptx Managed Nodes System Resources Adapted by ITO on Sequent DYNIX/ptx ITO makes changes in the following system resource files during installation: /etc/passwd and /etc/shadow (if present), Protected Password Database (if present) - entry for the default ITO operator /etc/group - group entry for the default ITO operator /etc/init.d/opcagt - ITO startup/shutdown script...

  • Page 151: File Tree Layout For Silicon Graphics Irix

    IRIX cluster clients (both diskless, and normal disks) are those IRIX systems that have either a /usr file system or /opt file system NFS mounted. Their cluster server is the system to which /usr or /opt is mounted. If the /opt file system is not already NFS mounted (only /usr...

  • Page 152: The Ito Default Operator On Sgi Irix, System Resources Adapted By Ito On Sgi Irix

    File Tree Layouts on the Managed-Node Platforms File Tree Layout for Silicon Graphics IRIX mount <cluster_server>:/opt /opt The ITO Default Operator on SGI IRIX The ITO default operator opc_op and the group opcgrp are created as the ITO default operator if they don’t already exist. Table 3-14 ITO Entry in /etc/passwd on SGI IRIX Managed Nodes Field...

  • Page 153

    /etc/init.d/opcagt - ITO startup/shutdown script /etc/rc0.d - file K09opcagt created /etc/rc2.d - file S89opcagt is created /etc/exports - on cluster server only; entry for export of /opt directory /etc/fstab - on cluster client only; entry for mount /opt directory /etc/init.d/grad_nck - NCS startup/shutdown script /etc/rc0.d - file K35nck is created...

  • Page 154: File Tree Layout On Sinix Managed Nodes, Standalone Systems Or Nfs Cluster Servers On Sinix

    SINIX In general, standalone systems are treated as cluster servers. The cluster server exports the /opt file system with read-only permissions. ITO software is located on the /opt/OV path, with the logical path name the same as the physical path name.

  • Page 155: Nfs Cluster Clients On Sinix, The Ito Default Operator On Sinix

    NFS Cluster Clients on SINIX SINIX cluster clients are those SINIX systems that have the /opt file system NFS mounted. Their cluster server is the system to which /opt is mounted and must also be a system running SINIX. The ITO Default Operator on SINIX The ITO default operator opc_op and the group opcgrp are created as the ITO default operator if they don’t already exist.

  • Page 156: System Resources Adapted By Ito On Sinix

    File Tree Layouts on the Managed-Node Platforms File Tree Layout on SINIX Managed Nodes System Resources Adapted by ITO on SINIX ITO makes changes in the following system resource files during installation: /etc/passwd and /etc/shadow (if present), Protected Password Database (if present) - entry for the default ITO operator /etc/group - group entry for the default ITO operator /etc/init.d/opcagt - ITO startup/shutdown script /etc/rc0.d - file K09opcagt created...

  • Page 157: File Tree Layout On Solaris Managed Nodes, Standalone Systems Or Nfs Cluster Servers On Solaris

    By default, Solaris does not export the /opt file system; not even on the cluster server. During the ITO installation process on the cluster server, care is taken to export the /opt file system if it was not already exported.

  • Page 158: Nfs Cluster Client On Solaris, The Ito Default Operator On Solaris

    Solaris cluster clients (both with and without disks) are those Solaris systems that have either a /usr or /opt file system NFS mounted. Their cluster server is the system to which /usr or /opt is mounted. If the /opt file system is not already NFS mounted (only /usr NFS mounted), then ITO mounts local /opt to /opt of the cluster server: mount <cluster_server>:/opt /opt...

  • Page 159

    File Tree Layouts on the Managed-Node Platforms File Tree Layout on Solaris Managed Nodes /etc/rc3.d/S76ncs - file created (if not already present) /etc/rc0.d/K52ncs - file created (if not already present) /etc/rc2.d/K52ncs - file created (if not already present) Chapter 3...

  • Page 160: File Tree Layout On Windows Nt Managed Nodes

    During installation, ITO creates the HP ITO account which has all rights and privileges that are required for the ITO agent software. It also creates the opc_op account which is a normal user account and is used to execute applications.

  • Page 161: Ito Default Operator On Windows Nt, System Resources Adapted By Ito On Windows Nt

    ControlSet\Control\Lsa\MSV1_0 HKEY_LOCAL_MACHINE\SYSTEM\Current ControlSet\Services\HP ITO Agent And if on a primary or backup domain controller: HKEY_LOCAL_MACHINE\SYSTEM\Current ControlSet\Services\HP ITO Installation Server Chapter 3 File Tree Layouts on the Managed-Node Platforms File Tree Layout on Windows NT Managed Nodes Entry HP ITO account Defined during...

  • Page 162

    File Tree Layouts on the Managed-Node Platforms File Tree Layout on Windows NT Managed Nodes Chapter 3...

  • Page 163

    Software Maintenance on Managed Nodes...

  • Page 164

    Removing ITO agent software packages from the management server that are no longer required. For information about adding an additional ITO agent software package NOTE to the management server, see the HP OpenView IT/Operations Installation Guide for the Management Server. Chapter 4...

  • Page 165

    (UNIX only). Failing that, make sure the local /etc/hosts.equiv (on the UNIX managed nodes) contains an entry for the management server. Before installing ITO software on the managed nodes, or de-installing ITO software from the managed nodes, read the section “General Installation Tips for Managed Nodes”...

  • Page 166

    Software Maintenance on Managed Nodes Overview Figure 4-1 Adding a Managed Node to the Node Bank Window For detailed information about how to set the managed node attributes, refer to the online help. Select the Automatic (De-)Installation option, and the ITO software is automatically installed onto the managed node when you invoke the installation for this system in the Install/Update ITO Software and Configuration window.

  • Page 167: Installing Or Updating Ito Software Automatically

    Installing or Updating ITO Software Automatically To install the ITO bits on the managed node automatically, use the Install/Update ITO Software and Configuration window and select the Actions:Agents->Install/Update SW & Config… item in the menu bar. Figure 4-2 Install/Update ITO Software and Configuration Window For detailed information about the Install/Update ITO Software and Configuration window, see the online help.

  • Page 168

    3. Check the local (managed node) installation logfile for any problems: DEC Alpha NT Digital UNIX (OSF/1) HP-UX 10.x and 11.x MPE/iX NCR UNIX SVR4 Novell NetWare Olivetti UNIX...

  • Page 169: Manually Activating The Ito Agent On Nfs Cluster Clients

    NFS Cluster Server system, and the ITO agent software bits must be available on the target node through an NFS mount of the ITO home directory (/opt/OV for HP-UX, Solaris, SINIX and NCR; /usr/lpp/OV for AIX). The full path-name of opcactivate command is:...

  • Page 170: Changing The Communication Type

    NOTE Manual activation of the ITO agent software on NFS Cluster Client Nodes is only supported for HP-UX 10.x/11.x, AIX, Solaris, NCR and SINIX managed node with ITO version A.05.00 and higher. In addition, only homogeneous NFS Clusters are supported and the cluster server and cluster client systems must have the same OS.

  • Page 171

    ITO agent software: 1. Ensure that your managed nodes meet the software requirements described in Chapter 1 of the HP OpenView IT/Operations Administrator’s Reference. In particular, ensure that the required DCE RPC software is installed and that the DCE daemon is running if you switch to DCE RPC.

  • Page 172

    You can also choose COMM_DCE_TCP instead of COMM_DCE_UDP. Note, however, that COMM_DCE_UDP is recommended. c. Select Start on Management Server, and specify user root to execute the application because opcnode must be called with root permissions. Click on [OK].

  • Page 173: De-installing Ito Software From Managed Nodes

    If you are de-installing the ITO agent software from a Windows NT Primary or Backup Domain Controller, the accounts for the domain users HP ITO account and opc_op must be deleted manually after the de-installation of the ITO agent software.

  • Page 174

    Software Maintenance on Managed Nodes De-installing ITO Software from Managed Nodes DEC Alpha NT Digital UNIX (OSF/1) HP-UX 10.x and 11.x MPE/iX NCR UNIX SVR4 Novell NetWare Olivetti UNIX OS/2 Pyramid DataCenter/OSx SCO OpenServer SCO UnixWare Sequent DYNIX/ptx SGI IRIX...

  • Page 175: Manually De-installing Ito Software From Aix Managed Nodes

    If opcinst.cmd has been removed after the installation, copy the script from the directory \opt\OV\bin\OpC\install on the managed node or from the management server to a temporary location, see “Manual OS/2 Agent Installation” on page 90. NOTE opcinst.cmd must be executed in a temporary directory; do not run opcinst.cmd from the directories \opt\OV or \var\opt\OV.

  • Page 176: Managed Nodes, Nodes, Manually De-activating The Ito Agent On An Nfs Cluster Client

    Software Maintenance on Managed Nodes De-installing ITO Software from Managed Nodes If the de-installation fails, stop all ITO agents and remove the directories \var\opt and \opt\OV from the managed nodes. Manually edit the startup command STARTUP. CMD to remove ITO-related information. Manually De-installing ITO Software from Solaris, NCR, and SINIX Managed Nodes 1.

  • Page 177

    Manual de-activation of the ITO agent software on NFS Cluster Client NOTE Nodes is only supported for HP-UX 10.x/11.x, AIX, Solaris, NCR and SINIX managed node with ITO version A.05.00 and higher. In addition, only homogeneous NFS Clusters are supported and the cluster server and cluster client systems must have the same OS.

  • Page 178: Managing Ito Agent Software

    ITO agent software version. If you install a new ITO agent version (having the same fileset name) on a management server supporting the same (or a super) set of OS versions as the previously installed ITO agent version, the previous ITO agent version is erased.

  • Page 179

    <platform_selector> <ito_version> <package_type> Chapter 4 Software Maintenance on Managed Nodes Managing ITO Agent Software Is one of the following values: • dec/alpha/unix • hp/s700/hp-ux • hp/s700/hp-ux10 • hp/s800/hp-ux • hp/s800/hp-ux10 • hp/pa-risc/hp-ux11 • hp/s900/mpe-ix • ibm/intel/os2 • ibm/rs6000/aix • ms/alpha/nt •...

  • Page 180

    Software Maintenance on Managed Nodes Managing ITO Agent Software NOTE Do not use swremove to de-install an ITO agent package that you no longer require. Running swremove is only useful if you wish to de-install all ITO agent packages of a particular architecture. In addition, remove the managed nodes from the ITO Node Bank before doing a complete de-installation of all managed nodes of a given architecture.

  • Page 181: Debugging Software (de-)installation On Managed Nodes, Enabling (de-)installation Debugging

    /var/opt/OV/log/OpC/mgmt_sv/install.log The (de-)installation process can be debugged both locally (on the management server) and remotely (on the managed node). A debug definition file inst_debug.conf is provided to force debugging and to specify debug options. The debug facility is, therefore, available regardless of whether the script inst.sh is invoked manually or called...

  • Page 182

    Software Maintenance on Managed Nodes Debugging Software (De-)Installation on Managed Nodes NOTE The syntax of the file inst_debug.conf is not checked. Be careful when editing this file because syntax errors will cause the installation process to abort. To disable debugging remove the file /var/opt/OV/share/tmp/OpC/mgmt_sv/inst_debug.conf For a detailed description of the (de-)installation debug facilities and examples of the file inst_debug.conf, see the man page...

  • Page 183

    Configuring ITO...

  • Page 184

    ITO configuration to managed nodes, and how to integrate applications into ITO. In addition to this chapter, you should also read the HP OpenView IT/Operations Concepts Guide, to gain a fuller understanding of the elements and the windows you can use to review or customize these preconfigured elements.

  • Page 185: Preconfigured Elements, Managed Nodes

    Note also the configuration tips in this section. Managed Nodes By default, the management server is also configured as a managed node with the default templates for SNMP event interception, ITO message interception, logfile encapsulation and monitoring as described in this section.

  • Page 186: Message Groups

    I/O, and so forth. Messages generated by ITO itself. This message group should not be used by opcmsg(1|3).The ITO message group cannot be deleted. Messages relating to print spooling/hard-copy functionality (for example, lp(1), lpr(1), HP OpenView OpenSpool). Chapter 5...

  • Page 187: The Message Browser

    Message Group... Performance Messages related to hardware (CPU, disk, process) and software (for example, HP OpenView PerfView) malfunctions. SNMP Messages generated by SNMP traps. Security Messages related to security violations or attempts to break into a system. You can add, modify, or delete message groups with the Message Group Bank window on the ITO GUI, while working as ITO administrator.

  • Page 188

    Configuring ITO Preconfigured Elements Table 5-2 Message Severity Levels Severity Level... Critical Major Minor Warning Normal ? Unknown NOTE The severity column of the Message Browser window provides a maximum of four characters to indicate a message’s severity level. Table 5-2 on page 188 shows this abbreviated form in bold, underlined text.

  • Page 189

    Figure 5-1 Message Attributes and Values The additional message attributes that appear in the Message Browser headline are shown in Figure 5-1 on page 189 and described in the following list: Chapter 5 Owned/Marked Message State A flag in this column indicates either that a user has taken note (Marked) or ownership (Owned) of a message or that the message is a notification message.

  • Page 190

    Configuring ITO Preconfigured Elements Unmatched Message An Unmatched Message does not match any of the filters defined for a message source. Filters are sets of conditions which configure ITO to accept or suppress messages. These messages require your special attention because they can represent problems for which no preconfigured action exists.

  • Page 191: Message Ownership

    History Browser window. Escalations Indicates if the message has been escalated to (or from) another ITO server. The value of the attribute tells you the message has: Date Specifies the date the message was received on the ITO management server.

  • Page 192

    For more information on which flags you might expect to find in the own- state column and what they mean, see “Understanding the Message Browser Headline” on page 187. For information on how to go about setting the ownership and ownership-display modes, see the HP ITO Administrator’s Guide to Online Information. Message-ownership Modes...

  • Page 193: Template Groups

    Enforced Ownership of messages is no longer optional: it is enforced. Informational The concept of ownership is replaced with that of marking/unmarking. A “marked” message indicates that an operator has taken note of a message. In optional mode, the owner of a message has exclusive read-write access to the message: all other users who have this message in their browser have only limited access to it.

  • Page 194

    Templates for Digital UNIX agent Event correlation templates for the ITO agent Event correlation templates for ITO management server Templates for HP-UX 10.x agent Templates for HP-UX 11.x agent Templates for IBM OS/2 agent Templates for SGI agent Templates for MC/ServiceGuard...

  • Page 195: Ito Users

    Templates for SCO OpenServer agent Templates for SCO UnixWare agent Templates for SINIX 5.43 or earlier agent Templates for SINIX 5.44 or later agent Templates for Windows NT Systems Management Server Templates for Solaris agent Templates for Windows NT agent...

  • Page 196

    Modify User window to change the password of each configured user. On HP-UX systems running the HP VUE GUI, you can start the ITO GUI by opening the System_Admin folder in the Application Manager window and double-clicking the ITO GUI symbol. A short introduction to ITO is also available by clicking the ITO symbol in the System_Info folder of the general toolbox.

  • Page 197

    For more information on the scope of each default operator, see the HP OpenView IT/Operations Concepts Guide. The following tables show you at a glance which node groups, message groups, applications and application groups are assigned by default to each of the operators.

  • Page 198

    Configuring ITO Preconfigured Elements Message Group Output Performance SNMP Security It is important to remember that although the various operators may have the same message group icon in their respective Message Groups window, the messages each operator receives and the nodes those messages come from are not necessarily the same: the responsibility matrix chosen by the administrator for a given operator determines which node group sends which messages to which operator.

  • Page 199

    Application Groups SNMP Data Tools UN*X Tools The applications and application groups assigned by default to the ITO users reflect the responsibility given to them by the administrator. Table 5-7 on page 198 and Table 5-8 on page 199 show you at a glance which applications and applications groups are assigned by default to each user.

  • Page 200

    On the managed node, provide a /etc/hosts.equiv entry for the management server. This solution is preferable to the method above if you log in or run applications on the managed node as many different users.

  • Page 201: Applications

    Applications ITO provides the following applications and application groups in the administrator’s default Application Bank window: Table 5-9 Administrator’s Applications and Application Groups Broadcast ITO Status Jovw MPE Tools Net Activity Net Config Net Diag NetWare Config NetWare Performance NetWare Tools NNM Tools NT Tools OS/2 Tools...

  • Page 202

    Configuring ITO Preconfigured Elements Tools UN*X Tools Virtual Terminal Broadcast Broadcast is an ITO application that allows you to issue the same command on multiple systems in parallel. UNIX: Default user: opc_op. Default password: none required, because application is started via the ITO action agent.

  • Page 203: Disk Space

    ITO shows the current disk usage: UNIX: Command issued: opcdf (This is a script calling bdf on HP-UX, and df on Solaris, AIX, NCR UNIX SVR4, SGI IRIX, SCO OpenServer, SCO UnixWare, Digital UNIX (OSF/1), DYNIX/ptx, Olivetti UNIX, Pyramid DataCenter/OSx, and SINIX/Reliant.)

  • Page 204

    Application Bank window. These can be copied to the operators’ Application Desktop window, as required. For complete coverage of this topic, see the HP ITO Administrator’s Guide to Online Information. Double-clicking the HP OpenView symbol “OV Services” in the Application Bank window displays the following underlying OV...

  • Page 205

    NOTE OV Services and OV Applications are always started as user opc_op. PerfView Double-clicking the Performance symbol in the Application Bank window displays the following underlying symbols: Start Glance Start PerfView Physical Terminal The script defined as the Physical Terminal command in the Managed Node Configuration window is called when starting the physical terminal application.

  • Page 206

    ITO displays the status of the running processes: UNIX: Command issued: opcps (This is a script calling ps -eaf on HP-UX, AIX, Solaris, NCR UNIX SVR4, SGI IRIX, SCO OpenServer, SCO UnixWare, Digital UNIX (OSF/1), DYNIX/ptx, Olivetti UNIX, Pyramid DataCenter/OSx, and SINIX/Reliant.)

  • Page 207

    System Administration Manager (SAM) — Motif and ASCII (HP-UX) ITO can start the ASCII or Motif version of the SAM user interface on HP-UX systems. Note that the Motif interface is only available on HP-UX versions 9.0 and higher. Motif SAM...

  • Page 208

    Default password: none configured For a virtual terminal connection to MPE/iX systems, ITO uses vt3k as virtual terminal emulator for HP 3000 nodes running MPE/iX. For ARPA host name to NS node name mapping, see the section “ARPA-to-NS Node-Name Mapping for MPE/iX” on page 128.

  • Page 209: Windows Nt Applications (intel & Dec Alpha-based), Cancel Reboot

    NOTE IBM OS/2 telnet does not require a user name, only the password associated with a given user name. To use virtual terminal, click: Customized startup, and enter the password along with a dummy user name. Refer to “Virtual Terminal PC” on page 225 for information about a Virtual Terminal on a Windows NT managed node.

  • Page 210

    Configuring ITO Preconfigured Elements Returns the following memory information: memory • Total paging-file size (NT swap file) • Available paging-file • physical location of the page file and its limits (minimum, maximum) Returns network information. network Returns the information listed below for each drive: drives DRIVE NAME...

  • Page 211

    • Priority (higher number -> higher priority) and other information. Returns CPU load information for each processor on cpuload the system. Processor time Private time Returns the percentage of processor User Time Interrupts/s Returns the number of device Returns the Windows NT IP Configuration. This Ipconfig consists of the: •...

  • Page 212: Installed Software, Ito Install Log

    Configuring ITO Preconfigured Elements Description of Values Returned: Refer to the User Configurable Parameters for this application. ITO Install Log This application returns the contents of the ITO installation log from the selected Windows NT node. Default: cmd.exe /c “type c:\temp\inst.log” User Configurable Parameters: None.

  • Page 213: Job Status, Lm Sessions

    If the selected system is acting as a logon server, it will show sessions of the users for which it has validated logons. If no user name is shown by the entry, it indicates that a service has created this session connection.

  • Page 214: Local Users, Memory Load, Netbios Sessions

    Configuring ITO Preconfigured Elements The number of open resources associated with the Opens connection. Time since this connection was last used. Idle time Local Users This application prints the name of the user who is locally logged onto the selected Windows NT node. If you need more information about the users and sessions, use the Show Users application.

  • Page 215: Perfmon Objs

    Returns only objects that match the string, starting from the beginning of the object. For example, /o s returns the objects system, server, and server work queues, while /o sy returns system, and /over matches nothing and returns an error message.

  • Page 216: Process Kill

    If you want the ITO operator to be able to kill any process, configure the application to run under HP ITO account. Description of Values Returned: Refer to the User Configurable Parameters for this application.

  • Page 217: Reg Viewer

    Pop up a notification window.This allows the local user to cancel the shutdown process. If this occurs, the management server will receive an error message. None, this application requires an entry from the table below. Configuring ITO...

  • Page 218

    Configuring ITO Preconfigured Elements To scan registry for pattern: /scan <pattern> /initkey lm|cu|cr|us /key <path> [/view] To enumerate a registry tree (thereby printing out registry keys to the set depth: emum uses a config file that verifies keys that should not be processed): /enum <depth>...

  • Page 219: Server Config

    Program Groups; Secure; Windows 3.1 Migration Status; Description; Server Config This application displays settings for the Server service for the selected Windows NT node. Default: net.exe config server User Configurable Parameters: For a full description of net.exe, refer to the Windows NT documentation.

  • Page 220: Server Stats

    Configuring ITO Preconfigured Elements Server Stats This application displays in-depth statistics about the Server service for the selected Windows NT node. Default: net.exe statistics server User Configurable Parameters: For a full description of net.exe, refer to the Windows NT documentation.

  • Page 221: Show Services, Show Drivers

    Show Drivers This application lists all drivers that are present on the selected Windows NT node. Default: itomserv.exe /list d User Configurable Parameters: see “Show Services” on page 221 Description of Values Returned: True name of the service. If you wish to perform actions NAME on the service, this is the name that should be used.

  • Page 222

    Configuring ITO Preconfigured Elements /list s | d | a Although the /e parameter is not useful from the application bank, it is NOTE included here because it may be useful for use with monitor scripts Description of Values Returned: Name Display Status...

  • Page 223: Show Users, Start Services, Stop Services

    Stop Services This application stops the requested service. Since administrative rights are required to stop and start Windows NT services, the user must be defined as HP ITO Account, and not opc_op. Default: itomserv.exe / stop <service name> Chapter 5 Configuring ITO...

  • Page 224: Tcp/ip Status, Used Shares

    Configuring ITO Preconfigured Elements User Configurable Parameters: see “Show Services” on page 221 TCP/IP Status This application displays protocol statistics and current active TCP/IPnetwork connections for the selected Windows NT node Default: netstat.exe User Configurable Parameters: Refer to the Windows NT documentation. Description of Values Returned: The protocol that is used for the connection.

  • Page 225: Novell Netware Applications, Virtual Terminal Pc, Workst Stats

    This section lists and defines the default applications in the NetWare Tools, NetWare Config and NetWare Performance application groups. ITO for NetWare can manage any NetWare server that is running the NetWare Management Agent (NMA). You must install the NMA on each server you want to manage.

  • Page 226: Performance Monitoring

    ITO management console. The NMA 2.1 agent is a set of NetWare agent NLMs that must be deployed on each NetWare server that you want to manage from the ITO console or Novell ManageWise console. The NetWare agent NLMs are: NWTRAP.NLM - 400+ traps with Novell NetExpert help text...

  • Page 227

    In addition to the monitors provided by NMA, ITO users can also create their own ITO templates to monitor any integer MIB variables supported by NMA. This allows ITO users to monitor NetWare server variables not monitored internally by the NMA.

  • Page 228

    • Total Packets Sent • Trend Graph • Volume Free Space Applications from this bank execute as user root on the server and make SNMP GET calls to collect performance data from the NetWare server. NetWare Tools The following application icons are available by default in NetWare Tools window.

  • Page 229

    Users action is the Connection action’s emphasis on data relating specifically to connections. This enables you to determine how busy the server really is and which connections and users are the busiest. CPU Info. Returns information about devices including the CPU...

  • Page 230

    Please note that these applications must be started via the customized-startup application so that additional parameters such as the name of an NLM can be entered. Installed Software (NW). installed on the server using PINSTALL: Default: instlsw <server_name> PINSTALL is a product from Novell used to install software packages such as NMA on NetWare Servers.

  • Page 231

    Use Network Interfaces as a troubleshooting tool to determine why a user cannot log in to a file server. If the frame types are different, you can change the frame type in the user’s NET.CFG file, edit the user’s frame type to match the server’s frame type, and restart the user’s system.

  • Page 232

    <server_name> NetWare’s server disk storage space is divided into volumes. “Volume” enables you to view information about the volumes in a server running NMA software; for example size, free space, how the volumes are distributed across the disks, and which users are using the space.

  • Page 233: Os/2 Applications

    This application requires only the remote console password (which may be different from the opc_op password). For NetWare SFT III servers, add another XCONSOLE application which calls the primary IO Engine rather than the MS Engine as in the default XCONSOLE application. NOTE The user name for the Xconsole application is xconsole.

  • Page 234

    Configuring ITO Preconfigured Elements Application List running processes List mounted drives Display Free Space ITO Control Agent Application on OS/2 Managed Nodes The ITO control agent on OS/2 managed nodes is a Presentation Manager application which displays a window that lets you start, stop, query the status of, and kill the ITO agents.

  • Page 235: Event Correlation

    ITO agent and currently runs on the platforms listed in Table 5-12. For more information on the concepts behind event correlation as well as the way it works in ITO, see the HP OpenView IT/Operations Concepts Guide. For help in setting up event correlation in ITO, see the section on tasks in the HP ITO Administrator’s Guide to Online Information.

  • Page 236: Logfile Encapsulation

    Configuring ITO Preconfigured Elements Table 5-12 ITO Event-correlation Runtime: Supported Platforms HP-UX 10.x HP-UX 11.x Solaris: 2.51, 2.6, 7 Windows NT: 3.51, 4.0 Logfile Encapsulation For detailed information about encapsulated logfiles, refer to the appropriate template in the ITO GUI. Note that the templates are configured to collect information from logfiles that are produced by...

  • Page 237

    Table 5-14 Encapsulated Logfiles on AIX HACMP Managed Nodes Logfile /var/adm/cluster.log Table 5-15 Encapsulated Logfiles on Digital UNIX Managed Nodes Logfile /var/adm/cron/log /var/adm/messages /usr/adm/sialog /var/adm/wtmp /usr/adm/lplog a. /var/adm/messages must be present in the /etc/syslog.conf file. b. If /var/adm/sialog is not present, add it using: touch /var/adm/sialog c.

  • Page 238

    (opckmsg). This is most easily done by adding the command /opt/OV/bin/OpC/opckmsg to the system boot file. A corresponding entry is provided (commented with “#”) by installing ITO on HP-UX 10.x managed nodes. You therefore only need to delete the comment sign (”#”) from the line “# start_opckmsg”, for the template to work.

  • Page 239

    Table 5-17 Encapsulated Logfiles on NCR UNIX SVR4 Managed Nodes Logfile /var/adm/loginlog /var/cron/log /etc/.osm /var/adm/sulog /var/adm/wtmpx Table 5-18 Encapsulated Logfiles on Olivetti UNIX Managed Nodes Logfile /var/cron/log /var/adm/messages /var/adm/sulog /var/adm/wtmpx /var/lp/logs/lpsched /var/lp/logs/request a. You must manually create the /var/adm/messages in the /etc/syslog.conf file.

  • Page 240

    Configuring ITO Preconfigured Elements Table 5-19 Encapsulated Logfiles on Pyramid DataCenter/OSx Managed Nodes Logfile /var/cron/log /etc/.osm /var/adm/sulog /var/adm/wtmpx /var/adm/badlog /usr/spool/lp/logs/l psched /usr/spool/lp/logs/r equests Table 5-20 Encapsulated Logfiles on SCO OpenServer Managed Nodes Logfile /usr/lib/cron/log /usr/adm/messages /usr/adm/sulog /etc/wtmp /usr/adm/syslog /usr/spool/lp/logs/l psched /usr/spool/lp/logs/r equests Description...

  • Page 241

    Table 5-21 Encapsulated Logfiles on SCO UnixWare Managed Nodes Logfile /var/cron/log /var/adm/messages /var/adm/sulog /var/adm/wtmpx /var/lp/logs/lpsched /var/lp/logs/request a. Requires the logfile /var/adm/messages in the file /etc/syslog.conf Table 5-22 Encapsulated Logfiles on SGI IRIX Managed Nodes Logfile /var/adm/loginlog /var/cron/log /var/adm/sulog /var/adm/SYSLOG /var/adm/wtmpx a.

  • Page 242

    Configuring ITO Preconfigured Elements Logfile /usr/spool/adm/syslog /usr/spool/lp/logs/lps ched /usr/spool/lp/remotelp /usr/spool/lp/logs/req uests Table 5-24 Encapsulated Logfiles on Siemens Nixdorf SINIX/Reliant Managed Nodes Logfile /var/cron/log /etc/.osm /var /adm/sulog /var/adm/wtmpx /var/adm/loginlog a. Default setup is used in the /etc/default/cron file b. Default setup is used in /etc/default/su file c.

  • Page 243: Snmp Trap And Event Interception

    ITO administrator GUI. By default, ITO intercepts SNMP traps from any application sending traps to the opctrapd daemon running on the management server and on all managed nodes where the OV trap daemon (ovtrapd) is running, or where port 162 can be accessed directly.

  • Page 244

    NNM collection station for the management server (preferably, the collection station connected via the fastest network). The destination system(s) for SNMP devices on HP-UX nodes is set in the /etc/SnmpAgent.d/snmpd.conf file with a trap_dest:<nodename> statement.

  • Page 245: Ito Message Interception, Mpe/ix-console Message Interception

    NetWare NMA 2.1 traps template filters the 379 traps that can be generated by the NMA module when an important event on the NetWare server occurs. Event Interception with ECS opctrapd connects by default to the correlated event flow of pmd. You can change this behavior by adding an appropriate statement to the opcinfo file on the managed node.

  • Page 246

    Configuring ITO Preconfigured Elements For details about the MPE/iX console messages which are intercepted, inspect the MPE/iX console template MPE Cons Msgs in the Message Source Templates window. Table 5-27 Default Message Mapping on MPE/iX Managed Nodes MPE/iX Classification Database Hardware Jobs Logging...

  • Page 247

    Mapping NMEV Markers Messages from the MPE operating system might contain so-called Node Management Event (NMEV) markers. ITO uses these markers to map MPE/iX console messages to the severity, message group, application, and object fields for ITO messages. NMEV markers have the format NMEV#pcc@aaa, where: Table 5-29 shows how NMEV markers are mapped in ITO.

  • Page 248

    Configuring ITO Preconfigured Elements MPE/iX ITO Message Application Group Network Network Network Output Output Output Output Storage Storage Storage Logging Logging Hardware Output Hardware Application/OS Subsystem Network-OSI Network-NS Network-SNA Ciper Devices I/O Services Native Mode Spooler Page Printer Device Manager Printer,Tape,Spool Software Resiliency Threshold Mgr...

  • Page 249

    MPE/iX ITO Message Application Group Storage Storage Security Hardware Misc For example, the marker NMEV#200@214 would generate a message with the severity Warning, in the message group Storage, concerning the application Printer,Tape,Spool. If no ITO-to-MPE/iX mapping is available for an MPE/iX console message intercepted by ITO, the original MPE/iX classification is used as a default value and the message appears in the message group Misc until you configure a message group that more accurately suits your...

  • Page 250

    fields. It is not recommended to create user-defined IDs because it is possible that the user-defined application IDs could conflict with HP-defined ID in the future, if HP added entries to the default consdesc file. The default consdesc file is located in...

  • Page 251: Monitored Objects

    Monitors SWAP utilization; this value can swap_util only be monitored on HP-UX versions 8.07 or higher Table 5-31 illustrates what the threshold values are for the various monitors supplied with ITO for the managed nodes and how often it is compared to the actual value.

  • Page 252

    HP-UX, versions 8.07 or higher only a. Digital UNIX = 90%: No AIX or HP-UX 10.x b. Digital UNIX = 10 mins: No AIX or HP-UX 10.x, c. No SCO OpenServer or SINIX d. No Digital UNIX e. No Digital UNIX f.

  • Page 253

    Table 5-32 Object Thresholds on Windows NT Managed Nodes Object Monitors free disk space on C: drive dflt_disk_util_NT Monitors processor use. A message is dflt_cpu_util_NT sent only if the threshold is exceeded for four consecutive minutes Monitors the RPC services. dflt_rpcss_NT Table 5-33 Object Thresholds on OS/2 Managed Nodes...

  • Page 254

    Configuring ITO Preconfigured Elements Object snmpd_mon_ext External monitor for Snmpd External monitor for Mib_2 mib2_mon_ext Scheduled action that checks which Multiple processes are running external monitors a. Requires TME NetFinity; see “Software Requirements for OS/2 Managed Nodes” on page 38. b.

  • Page 255

    Figure 5-2 NT Performance Monitor Syntax NTPerfMon\\ LogicalDisk \\ % Free Space \\ 0 \\ C: The language for the command may be either in English, or in the local language defined for the Windows NT system where the template will be used.

  • Page 256

    If the MIB OID (Object Idenitifer) 1.3.6.1.4.1.2.5.11.1.10 is already used, use the next free one (only the last number will differ), but make sure that the template on the management server reflects that change. Start the DMI subagent (DMISA.EXE, part of SystemView agent); if it is already running, stop and restart it.

  • Page 257

    Table 5-34 Attribute IDs of TME NetFinity MIB Variables CPU Utilization Drive C: Space Used Drive D: Space Used Drive C: Space Remaining Drive D: Space Remaining IP Packets Sent IP Packets Received with Errors Locked Memory Memory Usage Print Jobs Queued Process Count Swap file size Swap space remaining...

  • Page 258

    Configuring ITO Preconfigured Elements Attribute Name TCP/IP Interface 0 - Bytes Received Thread Count UDP Datagrams Sent UDP Datagrams Received Calculating the Value of a MIB Variable MIB variables have the following format and can be calculated by replacing the angle brackets with the desired value: <OID>.2.5.11.1.10.1.3.1.<X>.6.<ID>...

  • Page 259: Templates For External Interfaces

    Configuring ITO Preconfigured Elements Monitoring MIB Objects from other Communities MIB objects can also be monitored from communities other than public. To do this, add the following line to the opcinfo file on the managed node (see Table 10-3 on page 399 for the location of the opcinfo file on all platforms): SNMP_COMMUNITY <community>...

  • Page 260: General Configuration Tips Regarding File Names

    Preconfigured Elements General Configuration Tips Regarding File Names If you provide actions/cmds/monitor command files for MPE/iX managed nodes on the management server in: /var/opt/OV/share/databases/OpC/mgd_node/\ customer/hp/s900/mpe-ix make sure that the file names are not longer than 8 characters. The characters underscore ( _ ) and dash ( - ) are not allowed.

  • Page 261: Database Reports, Reports For Administrators

    For more information, see the documentation supplied with the OpenView Service Reporter product and the HP OpenView IT/Operations Concepts Guide. Reports for Administrators You can access ITO administrator reports by selecting Actions:Utilities->Reports…...

  • Page 262

    (GUI, API, CLI), date, time, report area and any associated actions. The “audit-level” setting determines which areas are included in the report. Review of the ITO error logfile on the management server: /var/opt/usr/OV/log/OpC/mgmt_sv/opcerror Logon audit report for all operators ITO user, showing UNIX user, source (GUI, API, CLI, etc), date, time, report area (logon/off) and (un/successfull) actions.

  • Page 263

    User Profile Overview User Profile Report Working ITO Users a. For more information about the logfiles containing the errors, see the section “On The ITO Management Server” on page 460. Additional reports can be defined by customizing the file: /etc/opt/OV/share/conf/OpC/mgmt_sv/reports/<lang>/\ admin.rpts...

  • Page 264: Reports For Operators

    Detailed report on all pending messages seen by the user who runs the report Review of the ITO error logfile on the management server: /var/opt/OV/log/OpC/mgmt_sv/opcerr Report on selected active messages Detailed report on selected active messages...

  • Page 265: Long-term Reports, Report Security

    Sel. Pending Details Detailed report on selected pending messages a. For more information about the logfiles, see the section “On The ITO Management Server” on page 460. You can define additional reports by customizing the file: /etc/opt/OV/share/conf/OpC/mgmt_sv/reports/<lang>/\ oper.rpts Whenever an operator saves report output to a file without specifying an absolute path (starting with “/”) the file is stored in the operator’s Unix...

  • Page 266

    For more information, see the Oracle product documentation. NOTE The web-reporting server must be on the same side of any firewall as the ITO database server. Any other configuration is not supported. Chapter 5...

  • Page 267: Flexible-management Configuration, Templates For Flexible Management

    • practical examples For additional help concerning the tasks involved in setting up the flexible management features in ITO, see the sections on flexible-management tasks in the HP ITO Administrator’s Guide to Online Information. Templates for Flexible Management ITO provides a set of ASCII templates which you can copy and edit to define the ITO features required to set up and use flexible management...

  • Page 268

    Management responsibility can be switched to a backup server if the ITO primary server fails. This template defines two management servers (M1) and (M2); management server M2 can act as a backup server for management server M1. Defines the responsible managers for message escalation.

  • Page 269

    Defines the period of time in which a service is to be provided or a outage system (such as a database server) or service is scheduled to be unavailable. Defines the responsible managers for service-related message service distribution, for example, competence centers, etc.

  • Page 270

    Configuring ITO Flexible-management Configuration A secondary ITO manager of an agent. This management server has permission to take over responsibility and become the primary ITO manager for an agent. • SECONDARYMANAGER • NODE <node> The node name of the SECONDARYMANAGER.

  • Page 271

    This is also used to escalate messages from one manager to another. • MSGTARGETMANAGER Management server to which you forward a message. NOTE Always specify the IP address of the target management server as 0.0.0.0. The real IP address is then resolved by the domain name service (DNS). • TIMETEMPLATE The name of the corresponding time template.

  • Page 272

    Configuring ITO Flexible-management Configuration messages are sent to the management server name stored in the primmgr file. If the primmgr file does not exist, messages are sent according to the opcsvinfo file. • DESCRIPTION A string describing the message target rule condition.

  • Page 273

    • MSGOPERATION Three types are possible, see Table 5-39 on page 277: • Suppress • Log-only • Inservice Template Syntax You can use the syntax described in the following sections as a basis for configuring flexible management features (for example, the switching of responsibility between managers) in the template files provided.

  • Page 274

    You can replace the <string> variable with $OPC_ALWAYS to specify that the time condition is always true. To specify that the current primary manager is always used as the message target server, replace the <node> variable with $OPC_PRIMARY_MGR Syntax for Service Hours and Scheduled Outages In the following description of the syntax rules for templates used to define service hours and scheduled outages, the “e”...

  • Page 275

    configfile [TIMETEMPLATES [CONDSTATUSVARS] <statusvarsdef>] RESPMGRCONFIGS <respmgrconfigs> Syntax for the declaration of condition status variables: statusvarsdef ::= <statusvarsdef> CONDSTATUSVAR <string> <bool> |e Syntax for the Time Template: timetmpls <timetmpls> TIMETEMPLATE <string> DESCRIPTION <string> <timetmpldefs> <conditions> |e timetmpldefs TIMEZONETYPE <string>| timezonetype Fix | Local conditions TIMETMPLCONDS timetmplconds...

  • Page 276

    Note that the templates must not be renamed: ITO looks for specific, template file name. For more information on how to set up both service hours and scheduled outages, see the section on Flexible Management Tasks in the HP ITO Administrator’s Guide to Online <node> <nodelist>...

  • Page 277

    You can change this behavior by setting the value of the OPC_AUTO_DEBUFFER parameter in the opcsvinfo file on the ITO management server to FALSE. IN this case, messages remain in the Pending Messages Browser window. In addition, you can change the value of the message attributes: •...

  • Page 278

    Configuring ITO Flexible-management Configuration MSGOPERATION TIMETEMPLATE “SLA_cust1” TROUBLETICKET True MSGOPERATION TIMETEMPLATE “SLA_cust2” NOTIFICATION False For more information on these and other variables, see “Syntax for Service Hours and Scheduled Outages” on page 274. The Condition-status Variable. allow you to enable and disable conditions dynamically. The conditions are used in message-target-rules conditions and must be declared at be beginning of the template after the declaration of several variables for one conditions as well as one variable...

  • Page 279

    fixed local time zone (e.g. EST for US Eastern Standard Time). The ITO management server uses the value of the time zone string and the time (in UTC) to calculate the fixed local time on the given management server for which an outage has been scheduled.

  • Page 280

    Configuring ITO Flexible-management Configuration This string instructs the ITO management server to apply the time frame for service hours defined on the ITO management server (e.g. 08:00 -- 16:00) as a sliding time frame for managed nodes in their respective local time zone.

  • Page 281

    file on each target management server. Table 5-40 provides more information about these parameters, their default values, and a short description of the function of each parameter.

  • Page 282: Time Templates

    Configuring ITO Flexible-management Configuration Parameter Name OPC_FORW_CTRL_SWTCH_TO_TT OPC_SEND_ACKN_TO_CTRL_SWTCH OPC_SEND_ANNO_TO_CTRL_SWTCH OPC_SEND_ANT_TO_CTRL_SWTCH OPC_SEND_ANNO_TO_NOTIF OPC_SEND_ANT_TO_NOTIF OPC_ONE_LINE_MSG_FORWARD Time Templates A time template consists of: The name used to refer to the time template. The time conditions. Each time condition defines a specific time period and contains the definition of the time, day of the week, and/or date.

  • Page 283

    For information about setting the TIMEZONE variable for MPE/iX nodes, see Chapter 2 of the HP OpenView IT/Operations Administrator’s Reference. The following examples show various ways to specify time formats in the...

  • Page 284

    Configuring ITO Flexible-management Configuration • To set a time period from the year 1995 to 2000, use the syntax: DATE FROM 01/01/1995 TO 12/31/1999 • To set a time on December 31 1998, from 23:00 to 23:59, use the syntax: TIME FROM 23:00 TO 23:59 DATE ON 12/31/1998 If you include the day of the week (for example, Monday April 1, 1997), ITO cross-checks the day and date you have entered to make...

  • Page 285

    NOTE At least one of the following parts must be used for the definition. ITO does not interpret any one of the following parts as “always”. • Match • Suppress • TIME FROM <time> TO <time> Specify a time period. Set the <time> using the format: <HH>:<MM>...

  • Page 286: Example Templates For Flexible Management

    WEEKDAY FROM Monday TO Friday DATE 1/1/95 RESPMGRCONFIGS RESPMGRCONFIG DESCRIPTION “responsible mgrs for agents in Europe” SECONDARYMANAGERS SECONDARYMANAGER NODE IP 0.0.0.0“hptest.bbn.hp.com” DESCRIPTION “Boeblingen” SECONDARYMANAGER NODE IP 0.0.0.0 “hpsystem.bbn.hp.com” DESCRIPTION “Boeblingen gateway” ACTIONALLOWMANAGERS ACTIONALLOWMANGER NODE IP 0.0.0.0 “hptest.bbn.hp.com” DESCRIPTION “Boeblingen” Chapter 5...

  • Page 287

    ACTIONALLOWMANGER NODE IP 0.0.0.0 “hpsystem.bbn.hp.com” DESCRIPTION “Boeblingen gateway” ACTIONALLOWMANGER NODE IP 0.0.0.0 “$OPC_PRIMARY_MGR” DESCRIPTION “ITO primary manager” MSGTARGETRULES MSGTARGETRULE DESCRIPTION “other messages” MSGTARGETRULECONDS MSGTARGETMANAGERS MSGTARGETMANAGER TIMETEMPLATE “shift2” OPCMGR NODE IP 0.0.0.0 “system.aaa.bb.com” Follow-the-Sun Responsibility Switch # Time-template configurations for follow-the-sun functions...

  • Page 288

    • Forward messages with message group DATABASE to a database expert center (dbexpert) and pass control of the message to this center, inform a second server (dbnotify) and, finally, cause the message to be acknowledged directly on the local ITO server...

  • Page 289

    • Inform another server (Treasury) about messages concerning financial and CAD applications • Inform server (master) about critical messages coming from nodes x1 and x2 TIMETEMPLATES # none RESPMGRCONFIGS RESPMGRCONFIG DESCRIPTION “msg-forwarding target specification” MSGTARGETRULES MSGTARGETRULE DESCRIPTION “Database” MSGTARGETRULE DESCRIPTION “Financial Application”...

  • Page 290: Service Hours

    Configuring ITO Flexible-management Configuration Service Hours The following example template defines service hours for a SAP server with the node name saparv01. This node has to be in service on weekdays from 08:00 hours to 16:00 hours. TIMETEMPLATES # time template TIMETEMPLATE “service hours”...

  • Page 291: Variables, Environment Variables, Snmp Variables

    Variables This section lists and defines the variables that can be used with ITO, and gives an output example, where appropriate. Each variable is shown with the required syntax. It is also often useful to surround the variable with quotes, especially if it NOTE may return a value that contains spaces.

  • Page 292

    Configuring ITO Variables Returns all variables assigned to the trap. Sample <$*> output: [1] .1.1 (OctetString): arg1 [2] .1.2 (OctetString): kernighan.c.com Returns the time the event was received as the number <$@> of seconds since the Epoch (Jan 1, 1970) using the time_t representation.

  • Page 293

    Returns the textual name of the remote pmd’s machine <$F> if the event was forwarded. Sample output: kernighan.c.com Returns the generic trap ID. Sample output: 6 <$G> <$MSG_OBJECT> Returns the name of the object associated with the event. This is set in the Message Defaults section of the Add/Modify SNMP Trap window.

  • Page 294: Logfile, Console, And Ito Interface Templates

    Configuring ITO Variables Returns the date the event was received using the local <$x> date representation. Sample output: 03/27/97 Logfile, Console, and ITO Interface Templates The variables listed below can be used in most logfile, Console, and ITO Interface template text entry fields (exceptions are noted). The variables can be used within ITO, or passed to external programs.

  • Page 295: Threshold Monitor Templates

    <$OPC_MGMTSV> Returns the name of the current ITO management server. Sample output: richie.c.com The following variables are only available for the MPE/iX console message source template. See “Generating a New NMEV Marker” on page 249 for a description of the format of the NMEV marker and how it is generated.

  • Page 296: Broadcast Applications And User Interface

    Configuring ITO Variables Returns the name of a threshold monitor. This is set in the Monitor Name field of the Add/Modify Monitor window. Sample output: cpu_util <$THRESHOLD> Returns the value set for a monitor threshold. This is set in the Threshold: field on the Add/Modify Monitor window.

  • Page 297

    IP Map. Sample output: kernighan.c.com richie.c.com $OPC_USER Returns the name of the ITO user who is currently logged in on the management server. Sample output: opc_adm Time Templates The variables listed below can be used in ITO time templates. See /etc/opt/OV/share/conf/OpC/mgmt_sv/ tmpl_respmgrs/example.m2.

  • Page 298

    Configuring ITO Variables Chapter 5...

  • Page 299

    Installing/Updating the ITO Configuration on the Managed Nodes...

  • Page 300

    This chapter describes how to install/update the ITO configuration on the managed nodes. In addition to this chapter, you should also read the HP OpenView IT/Operations Concepts Guide, for a fuller understanding of the elements and the windows you can use to review or customize them.

  • Page 301: Configuration Installation/update On Managed Nodes, Script And Program Distribution To Managed Nodes

    ITO only distributes these scripts and programs if they are not installed on the managed node, or if a newer version is available on the management server. However, in order to reduce network traffic and speed up distribution, note the following points: 1.

  • Page 302

    Installing/Updating the ITO Configuration on the Managed Nodes Configuration Installation/Update on Managed Nodes novell/intel/nw olivetti/intel/unix pyramid/mips/unix sco/intel/unix sco/intel/uw sequent/intel/dynix sgi/mips/irix sni/mips/sinix sun/sparc/solaris 2. If you need a certain binary to be present only on specific systems, transfer the file manually. Furthermore, do not put the file in the default directory on the managed nodes.

  • Page 303

    6-1. Set a low number in the Parallel Distribution field. For more information, press • Reduce the process priority of opcdistm (distribution manager) on the management server using the renice(1) command. Chapter 6 Configuration Installation/Update on Managed Nodes to see help on this field.

  • Page 304

    Installing/Updating the ITO Configuration on the Managed Nodes Configuration Installation/Update on Managed Nodes Figure 6-1 Configure Management Server Window 5. If identical files for actions|cmds|monitor are found in the following directories: /var/opt/OV/share/databases/OpC/mgd_node/customer/\ <arch> and: /var/opt/OV/share/databases/OpC/mgd_node/vendor/\ <arch>/<ito_version>/<package_type> the customer’s file is used in preference.

  • Page 305: Distributing The Ito Agent Configuration To The Managed Nodes

    Workstations) should be compiled using the -DA1.1 option (HP-PA compatibility mode). This is because these programs must also run on HP 9000 series 800 computers (Enterprise Servers). (ITO does not distinguish between these two architectures.) If this is not possible, the following symbolic link must be replaced by an ordinary s800/hp-ux directory tree for HP-UX 10.x managed nodes:...

  • Page 306

    To distribute the appropriate files, select the corresponding options in the Install/Update ITO Software and Configuration window. These scripts and programs are distributed only if they are not already installed on the managed node, or when a newer version is available on the management server. Chapter 6...

  • Page 307

    Command Broadcast or started from the Application Desktop a. Where <arch> is the platform-specific directory, for example: hp/s700/hp-ux10 On managed nodes, the scripts and programs are put into the directories listed in Table 6-2 and Table 6-3. Chapter 6 Installing/Updating the ITO Configuration on the Managed Nodes Configuration Installation/Update on Managed Nodes...

  • Page 308

    Table 6-2 Temporary Directories for Distributed Scripts and Programs on Managed Nodes Operating Managed Node DEC Alpha Windows NT DEC Alpha AXP Digital UNIX HP 3000/900 MPE/iX HP 9000/[78]00 HP-UX 10.x and 11.x IBM RS/6000, Bull DPX/20 System /usr/OV/tmp/OpC/bin/alpha/actions /usr/OV/tmp/OpC/bin/alpha/cmds...

  • Page 309

    Operating Managed Node System Intel 486 or higher DYNIX/ptx Novell NetWare OS/2 OpenServer and UnixWare Windows NT NCR System UNIX SVR4 3xxx/4xxx/5xxx (Intel 486 or higher) Olivetti (Intel PCs) Olivetti UNIX SVR4 Pyramid Pyramid mips_r3000 DataCenter/OSx Chapter 6 Installing/Updating the ITO Configuration on the Managed Nodes Configuration Installation/Update on Managed Nodes Temporary Directory /var/opt/OV/tmp/OpC/bin/actions...

  • Page 310

    Installing/Updating the ITO Configuration on the Managed Nodes Configuration Installation/Update on Managed Nodes Operating Managed Node Siemens Nixdorf SINIX Silicon Graphics IRIX Sun SPARCstation Solaris The binaries are located in the temporary directories only during the distribution phase. When distribution is completed, the local ITO action and monitor agents are stopped, the binaries moved/copied to their final destination, and the ITO action and monitor agents restarted.

  • Page 311

    Managed Node HP 9000/700 HP-UX HP 9000/800. 10.x and 11.x HP 3000/900 MPE/iX IBM RS/6000, Bull DPX/20 Chapter 6 Installing/Updating the ITO Configuration on the Managed Nodes Configuration Installation/Update on Managed Nodes Directory /var/opt/OV/bin/OpC/actions /var/opt/OV/bin/OpC/cmds /var/opt/OV/bin/OpC/monitor ACTIONS.OVOPC cap=BA,IA,PM,MR,DS,PH COMMANDS.OVOPC cap=BA,IA,PM,MR,DS,PH MONITOR.OVOPC...

  • Page 312

    Installing/Updating the ITO Configuration on the Managed Nodes Configuration Installation/Update on Managed Nodes Managed Node Intel 486 or Novell higher NetWare OS/2 OpenServer UnixWare DYNIX WindowsNT Directory sys:/var/opt/OV/tmp/OpC/bin/\ actions sys:/var/opt/OV/tmp/OpC/bin/\ cmds sys:/var/opt/OV/tmp/OpC/bin/\ monitor \var\opt\OV\bin\OpC\actions \var\opt\OV\bin\OpC\cmds \var\opt\OV\bin\OpC\monitor /var/opt/OV/bin/OpC/actions /var/opt/OV/bin/OpC/cmds /var/opt/OV/bin/OpC/monitor /usr/OV/bin/OpC/intel/actions /usr/OV/bin/OpC/intel/cmds /usr/OV/bin/OpC/intel/monitor Access Rights...

  • Page 313

    Managed Node NCR System UNIX SVR4 3xxx/4xxx/5xx x (Intel 486 or higher Olivetti Olivetti (INTEL PCs) UNIX Pyramid Data mips_r3000 Center/ OSx Siemens SINIX Nixdorf Chapter 6 Installing/Updating the ITO Configuration on the Managed Nodes Configuration Installation/Update on Managed Nodes Directory /var/opt/OV/bin/OpC/actions /var/opt/OV/bin/OpC/cmds...

  • Page 314

    Installing/Updating the ITO Configuration on the Managed Nodes Configuration Installation/Update on Managed Nodes Managed Node Silicon IRIX Graphics Solaris SPARCstation a. OS/2 has only write-access permission; files that can be read can also be executed if a read-only flag is set. OS/2 does not support a user concept. The ITO action agent and monitor agent append the appropriate directories to the $PATH setting of the executing user.

  • Page 315

    Integrating Applications into...

  • Page 316

    Integrating Applications into ITO This chapter describes how to integrate applications into ITO. The HP OpenView IT/Operations Concepts Guide provides more detailed information on the elements and the windows you can use to carry out the integration. See also the HP OpenView IT/Operations Application Integration Guide available with the HP OpenView IT/Operations Developer’s Toolkit.

  • Page 317: Integrating Applications Into Ito, Integrating Applications Into The Application Desktop

    If you have purchased an application which is prepared for ITO integration (for example, HP OpenView OpenSpool, HP OpenView OmniBack II, or HP OpenView OmniStorage) you can integrate it quickly and easily using opccfgupld(1M). You can integrate applications into the following components of ITO: operators’...

  • Page 318: Examples Of Application Integration Tasks

    Application Registration Files (ARFs) which define how users access applications and how application processes are managed. HP OpenView applications also have access to HP OpenView windows through the HP OpenView Windows Applications Programming Interface (API). This is useful, for example, for generating application-specific submaps, as done by HP OpenView OpenSpool, HP OpenView OmniBack II, and HP OpenView OmniStorage.

  • Page 319

    5. Verify that the IP topology is being built under the IP Internet symbol in the root submap. Integrating “Ethernet Traffic HP” as an OV Application. 1. Working as the administrator, from the menu bar of the root IP Map, select Window:Application Bank….

  • Page 320

    As administrator: Log out and log in again, to use this OV Application. Select a node and double-click on the Ethernet Traffic HP application in the ITO Application Bank. Drag and drop this OV application into an operator’s Assigned Applications window to enable the operator to monitor the ethernet traffic.

  • Page 321

    Start PerfView This application enables you to graph performance data on the selected managed node(s). This application runs on the management server and requires that HP PerfView is installed on the management server. Start Glance This application starts HP GlancePlus on the managed node. This requires that HP GlancePlus is first installed on the managed node.

  • Page 322

    Distribute the [Commands] components to the managed nodes. For more information, see the HP OpenView MeasureWare Agent User’s Manual and the online help for HP PerfView and HP GlancePlus. Integrating PerfView 4.0 and MeasureWare Agents PerfView 3.0 integration is based on the logfile encapsulation of PerfView’s alarm log database (logfile PerfView, template group...

  • Page 323

    Running PerfView 3.0 and PerfView 4.0 in parallel If you upgrade some managed nodes from PerfView 3.0 to the MeasureWare agent, remember to perform either one of the following two steps to avoid receiving redundant PerfView alarms: unregister MeasureWare agents from the PerfView 3.0 analysis station (PerfView’s central alarm logfile) modify the PerfView logfile template in ITO to intercept only the events originating from those managed nodes where PerfView 3.0 is...

  • Page 324: Integrating Applications As Broadcast Commands

    Integrating Applications into ITO Integrating Applications into ITO b. Select [No Window] (for example, X Application) from the option button. c. Click on [OK]. 4. Select again the application labeled ITO Status from the Application Bank. 5. Copy this application using Actions:Application->Copy and modify it to become the ITO Agents Stop application: a.

  • Page 325: Integrating Applications As Actions, Integrating Monitoring Applications

    Note that HP ITO Account is part of the Administrator, Domain Administrator and User Administrator groups. If an action is prohibited for one of these groups, the HP ITO Account will not be able to perform that action. The application must be accessible via the root’s $PATH settings on UNIX systems, or the path must be fully qualified on the corresponding...

  • Page 326: Application Logfile Encapsulation, Application Message Interception, Server Message Stream Interface Api

    Most applications running on Windows NT systems use Eventlogs. The information in these databases can be extracted by the logfile encapsulator, but there are some differences in the set-up procedure. Refer to the ITO online help or the HP OpenView IT/Operations Concepts Guide for more information. Application Message Interception...

  • Page 327: Broadcasts On Managed Nodes

    Do not ask for specific user input in the profile. Instead, you can provide an appropriate default value, to be returned only when is pressed. For example, the following script for HP-UX 10.x produces an endless loop if no valid answer is specified. #!/usr/bin/sh TERM=””...

  • Page 328: Sms Integration

    NT nodes, and to restart SMS services if they fail. NT agents installed on every Site Server report SMS information about the entire SMS hierarchy without using any SMS mechanisms. Supported Versions of SMS ITO supports both the English and the Japanese System Management Server (SMS) 1.2 on Microsoft Windows NT Server 3.51 and 4.0.

  • Page 329

    How to integrate ITO with SMS The ITO/SMS integration has two parts. The first consists of the standard NT application event log template, and the second consists of a specific SMS application event log template and fourteen threshold monitors. This sections explains how to set up and install these templates and monitors.

  • Page 330

    These servers are also logged into the NT application event log of the Site Server. The Application Event Log template must be on a Site Server— even if the site is distributed. 2. Customize the conditions for the templates.

  • Page 331

    3. Distribute the templates (and the agent as well, if it is not already installed). How SMS messages relate to ITO messages When ITO reports SMS messages in the Message Browser, it assigns a Message Group and Message Object that is appropriate to the message. The tables below show how the SMS messages will be mapped in ITO.

  • Page 332: Ems Integration

    Monitoring requests for EMS are configured using the EMS GUI client which is integrated into SAM, the HP-UX system administration tool. To start the EMS GUI, start SAM, for example from the ITO Application Bank window, and double-click on the Resource Management icon, then on the Event Monitoring Service icon.

  • Page 333

    ITO Language Support...

  • Page 334

    ITO Language Support This chapter describes the language dependencies of the ITO management server processes, managed node commands and processes, and the ITO GUI. It also describes the languages and LANG settings supported for the various ITO platforms. In addition, you will find information on the character sets supported by ITO.

  • Page 335: Language Support On The Management Server, Language Of Messages On Management Server

    /sbin/init.d/ov500 At this point, the LANG variable is set to C or not yet set. If you require the ITO server processes to send their status messages in a different (supported) language, set LANG before ovstart ovacomm is called.

  • Page 336: Ito Gui Considerations

    In this case, however, although you are running on a Japanese management server you will receive messages and some labels in Japanese, due to various HP OpenView platform restrictions. If your management server is in a Japanese environment, but you want to receive English messages, set the following language variables as shown: LANG=ja_JP.SJIS, and LC_MESSAGES=C.

  • Page 337

    ITO-Specific X Resources Used for Fonts Resource Opc.fixedTextFont Opc.variableTextFont Opc.buttonFont Chapter 8 Language Support on the Management Server Resource Font used for window titles. Font used for icon titles. Description Font used in list boxes, for example, in the Message Browser.

  • Page 338: Language Support On Managed Nodes, Language Of Messages On Managed Nodes

    Windows NT, DEC Alpha NT, Novell NetWare, and OS/2 managed nodes use the NT System Language. A LANG environment variable is not available. HP-UX, AIX, Solaris, Digital UNIX, and Windows NT (Intel-based) are NOTE supported in Japanese and English environments.

  • Page 339: Character Sets For Internal Processing On Managed Nodes

    ITO database. Consequently, when a message is generated on a managed node, it must often be converted before it can be sent to the management server and stored in the database. ITO takes care of this conversion. If necessary, automatic character-set conversions take place through ITO managed node processes before a message is sent to the server.

  • Page 340: The Ascii Character Set

    ASCII can be converted to Shift JIS without loss of data and enables you to manage English nodes (running with ASCII as internal character set) with a Japanese management server. Note however, that if you are using ASCII as the character set for internal processing ( in the Node Advanced Options window), you must also specify ASCII as the character set for the monitored logfile messages.

  • Page 341: External Character Set On Managed Nodes

    The following table shows the values of LANG supported by ITO, and the related external character set, in an English environment. Table 8-5 External Character Sets in an English Environment Platform Digital UNIX HP-UX 10.x/11.x MPE/iX Novell NetWare Chapter 8 Language Support on Managed Nodes LANG <lang>.ISO8859-1...

  • Page 342

    ITO Language Support Language Support on Managed Nodes Platform OS/2 NCR UNIX SVR4, SCO UnixWare, SGI IRIX, Sequent DYNIX/ptx, Olivetti UNIX, Pyramid DataCenter/OSx SCO OpenServer Siemens Nixdorf SINIX Solaris Windows NT <lang> refers to any language that is supported by the operating system. Although it is possible to specify literally any language in this field, you can receive ITO messages only in a language supported by ITO.

  • Page 343: Character Sets Supported By The Logfile Encapsulator

    Table 8-6 External Character Sets in a Japanese Environment Platform HP-UX 10.x and 11.x Digital UNIX Solaris Windows NT a. Only with Solaris 2.6 and later. Character Sets supported by the Logfile Encapsulator The ITO Logfile Encapsulator is capable of monitoring files with different character sets.

  • Page 344

    Multilingual OEM code page 850 OEM US code page 437 Multilingual ANSI code page 1252 Japanese ANSI code page 932 Shift JIS EUC (2-byte Extended UNIX code) Windows HP-UX, Solaris, AIX, Digital UNIX Nodes Nodes HP-UX HP-UX Solaris NetWare, Other OS/2 Nodes...

  • Page 345: Character Conversion In Ito, English Environment

    (save) ISO 8859-1 opccfgupld opccfgdwn ITO Server ISO 8859-1 OVwindows ISO 8859-1 Management Server Key: SV CS = Server Character Set Ext. CS = External Character Set Chapter 8 HP-UX Solaris NCR UNIX ISO 8859-1 SGI IRIX config SCO OS...

  • Page 346

    Configuration upload and download is done using ISO 8859-1. No runtime conversion is done on the management server. Conversion is only performed for managed node configuration files if the ITO agents on HP-UX or MPE/iX are running with the processing character set, ROMAN8. Managed Nodes: Incoming SNMP events are always interpreted as being ASCII.

  • Page 347

    ISO8859-1/WE8ISO8859P1 (the database character set). Tips On HP-UX, it is possible to define different character sets for different managed nodes. It is recommended that you set the character set most frequently used on each managed node. For example, if you mostly monitor logfiles with ROMAN8 characters, you should use ROMAN8 for...

  • Page 348: Japanese Environment

    Configuration upload and download is performed using Shift JIS. No runtime conversion is done on the management server. Conversion is only performed for managed node configuration files if the ITO agents on HP-UX, Solaris, AIX, and Digital UNIX are running with the processing character set EUC. Managed Nodes: Incoming SNMP events are always interpreted as ASCII.

  • Page 349

    ITO in the EUC character set, you should set the managed node character set to EUC. If in doubt, use Shift JIS. Note that you can use a different character set for each HP-UX managed node. You determine the managed node character set by the character sets used in your environment.

  • Page 350: Localized Object Names

    ITO Language Support Localized Object Names Localized Object Names Although most of the ITO-specific configuration can be localized, there are some restrictions. Restrictions Only ASCII characters are supported in node names. The name of ITO objects, for example, the template name, message group name, or node group name, is used as an internal identifier by ITO and therefore should not be localized.

  • Page 351: Flexible Management In A Japanese Environment

    Flexible Management in a Japanese Environment If your management server runs with the character set Shift JIS, but your managed nodes are running with the character set EUC, you must perform some extra configuration steps; namely you have to manually convert the MoM configuration file on the management server from Shift...

  • Page 352

    ITO Language Support Flexible Management in a Japanese Environment Chapter 8...

  • Page 353

    An Overview of ITO Processes...

  • Page 354

    This chapter provides a functional overview of ITO: it describes ITO manager and agent processes and subprocesses, and lists files used by ITO. The chapter is divided into sections that describe the following: Management Server Processes Managed Node Processes Secure Networking Figure 9-1 on page 355 provides a functional overview of the major parts of ITO.

  • Page 355: Understanding Ito Processes

    Calls (RPCs) based on DCE or NCS, files (=queues), pipes, or signals. These mechanisms apply to communication between the management server and the managed nodes as well as to communication between processes running locally on the management server. Figure 9-1...

  • Page 356: Management Server Processes

    An Overview of ITO Processes Understanding ITO Processes For more information on how the processes communicate with one another and what each process does, see “Management Server Processes” on page 356 and “Managed Node Processes” on page 360. Management Server Processes...

  • Page 357

    The event-correlation manager connects to the opcecm Server MSI to allow access to and modification of messages from the ITO message flow by the event- correlation (EC) engine. Depending on filters and conditions, the messages are then correlated and...

  • Page 358

    The ITO GUI for the ITO template administrator, opcuitadm required for the template administrator’s configuration activities. Runs as user root. The opcuiwww server process serves the ITO Java- opcuiwww based operator GUIs. It forwards all communication requests between the Java-based GUIs and the display manager.

  • Page 359

    Queue/pipe between the display manager and control manager File to inform the ITO management server processes about configuration changes; for example, regroup conditions, nodes, trouble-ticket, notification service. Queue/pipe between the display manager and GUI (opcuiop/opcuiadm).

  • Page 360: Managed Node Processes

    An Overview of ITO Processes Understanding ITO Processes Server File Name Queue/pipe used by the message manager and message- mpimmp/ stream-interfaces to transfer messages from MSI-programs to mpimmq the message manager Queue/pipe between the message receiver and message msgmgrq/ manager.

  • Page 361

    The event-correlation agent connects to the agent opceca MSI in the same way that the ECS runtime library is integrated into the ITO server. This connection allows access to and modification of messages from the ITO message flow on the agent; those messages modified by...

  • Page 362

    The message agent triggers local automatic actions by forwarding the task to the action agent.

  • Page 363

    Table 9-2 Locating Process-related Files on the Managed Nodes DEC Alpha NT HP-UX 10.x and 11.x Digital UNIX NCR UNIX SVR4 Olivetti UNIX OS/2 Pyramid DataCenter/OSx SCO OpenServer SCO UnixWare Sequent DYNIX/ptx SGI IRIX Solaris MPE/iX Novell NetWare Windows NT The files that the ITO processes on the managed node use are described...

  • Page 364

    MSI programs to the message agent File that holds any messages that cannot be passed to the management server (for example, if the network is down). The messages will be read from this file once the management server is available.

  • Page 365

    Chapter 9 File Contents and Function ITO trace logfile. For more information on activating tracing see the section on troubleshooting in the HP OpenView IT/ Operations Administrator’s Reference. Temporary files used by the action agent, for example, to store the action or application output written to stderr and sdtout.

  • Page 366: Process Security

    RPC server. For example, just as a server needs to determine whether or not an incoming request is from a genuine ITO client, an RPC client also needs to be sure that the server it is calling is a real ITO server.

  • Page 367

    RPC client and an RPC server illustrates the procedure in the context of ITO. In this case, the RPC client is the message agent on the managed node, and the RPC server is the message receiver on the management server: 1.

  • Page 368

    ITO associates two names with the two types of node in its environment, namely: one each for the management server and the managed node. All management server processes then run under the name associated with the management server, and all managed node processes under the identity of the name associated with the managed node.

  • Page 369: Secure Networking, The Rpc Client/server Connection

    RPC request. The first thing it does is to look up in the LLBD or RPCD on the remote system the specific port number of the RPC server it needs to talk to: the LLBD Chapter 9...

  • Page 370: Processes And Ports

    In this case, ITO generates an error message. For more information on how to set port ranges and the consequences of incorrect port assignment, see the HP ITO Administrator’s Guide to Online Information. Dynamic Port Assignment through a Firewall:...

  • Page 371: Restrictions And Recommendations

    TCP as the DCE RPC protocol. UDP requires significantly less overhead and is therefore faster and less demanding of resources. If the managed nodes and management server are connected over a slow or busy network (WAN, X.25 etc.), or even if the volume of data to be transmitted is large, it is more reliable to use TCP.

  • Page 372

    An Overview of ITO Processes Secure Networking Chapter 9...

  • Page 373

    Tuning, Troubleshooting, Security, and Maintenance...

  • Page 374

    Tuning, Troubleshooting, Security, and Maintenance This chapter contains information for administrators who perform system maintenance, performance tuning, and troubleshooting. It also describes some important security information, and how to change the hostname and IP address of your management server and manged nodes. Chapter 10...

  • Page 375: Performance Tuning, Improving Snmp Management Platform Performance

    Reduce the amount of memory used by ovwdb(1M) (the HP OpenView Windows object database daemon) for managing large numbers of nodes. Do not use the logging and tracing options provided for the HP OpenView Network Node Manager daemons (trapd, netmon, etc.) unless absolutely necessary.

  • Page 376: Improving Database Performance, Improving Ito's Performance

    Tuning, Troubleshooting, Security, and Maintenance Performance Tuning Suppress the appearance of the ITO Alarm Severity symbol in the HP OpenView submaps by changing the ITO app-defaults file. Set the line Opc.statusPropOnAllNodes in the file /opt/OV/lib/X11/app-defaults/<language>/Opc to False. The default setting is True.

  • Page 377

    1. Reducing the number of managed nodes for parallel configuration distribution (Configure Management Server window, [Actions: Server: Configure…]). 2. Making sure operators close any View- and History-Browser windows not currently required. This reduces: • the amount of RAM required for the GUI •...

  • Page 378: Troubleshooting: Recommended Practices

    Make sure that the following directories are included in your PATH: • /opt/OV/bin/OpC • /opt/OV/bin/OpC/install Do not modify HP OpenView product files, such as X resources, without retaining copies of the original files. Make sure that you are not using up too much of your management station’s CPU and system resources by collecting too much data, or by...

  • Page 379: Troubleshooting: Tracing

    Trace logfiles can provide pointers to where and when the problem occurred. Tracing can be activated for specific management server and/or agent processes by adding a statement to the opcsvinfo and/or opcinfo file. To simplify the interpretation of the trace logfile, tracing can be activated for specific functional areas by specifying one or more functional areas in...

  • Page 380: Activating Tracing

    files: Management server processes: /opt/OV/bin/OpC/install/opcsvinfo HP-UX 10.x and 11.x managed node processes (refer to Table 10-3, “Location of the opcinfo File on ITO Managed Nodes,” on page 399 for file locations on other supported platforms):...

  • Page 381

    # (c) Copyright Hewlett-Packard Co. 1998 ################################################################# OPC_INSTALLED_VERSION A.05.00 OPC_MGMT_SERVER arthur.ashe.hp.com OPC_INSTALLATION_TIME 23/01/98 15:06:18 OPC_TRACE TRUE OPC_TRACE_AREA INT,ACTN OPC_TRACE_TRUNC FALSE ################################################################# # end of opcsvinfo ################################################################# Chapter 10 Tuning, Troubleshooting, Security, and Maintenance opcsvinfo OpC Installation Information of Management Server HP OpenView IT/Operations Troubleshooting: Tracing...

  • Page 382: Interpreting The Trace File

    The trace information is written to the following trace logfile: Management server trace file: /var/opt/OV/share/tmp/OpC/mgmt_sv/trace HP-UX 10.x and 11.x managed node trace file (refer to Chapter 3 of the HP OpenView IT/Operations Administrator’s Reference for file locations on other supported platforms):...

  • Page 383: Troubleshooting: Characterizing The Problem

    When you encounter a symptom associated with a problem, make a note of all associated information: Scope: What is affected? • Distinguish between management server and managed node problems. • If you suspect that a problem lies on a managed node, try to duplicate it on a different node, to find out whether it is...

  • Page 384: Debug Information For Os/2 Managed Nodes

    Tuning, Troubleshooting, Security, and Maintenance Troubleshooting: Characterizing the Problem Debug Information for OS/2 Managed Nodes On OS/2 managed nodes, ITO provides an REXX (OS/2 scripting language) script, \opt\OV\bin\OpC\utils\opcclct.cmd. Run this script when you are in a situation that requires attention of a support engineer.

  • Page 385: Troubleshooting: General Considerations

    ITO is an application that is both memory- and swap-space intensive. Problems may occur simply due to the exhaustion of resources. Communication between the ITO management server processes is based on DCE remote procedure calls, which may cause occasional failures and time-outs of manager/agent communications.

  • Page 386: Troubleshooting: How Ito Reports Errors, Errors Reported In Logfiles

    Errors Reported in Logfiles Error messages are written to two different locations: 1. All errors detected by the ITO server or by agent processes are written to the appropriate log file. 2. In addition (if possible) an ITO message is generated for display in the Message Browser.

  • Page 387: Errors Reported Via The Message Browser

    Errors Reported via the Message Browser In most cases when an error is written to the opcerror log files on the management server or on a managed node, ITO tries to generate a message and display it on the Message Browser of any users responsible for monitoring the message group, OpC.

  • Page 388: Errors Reported Via The Gui Error Dialog Box

    Errors originating from HP OpenView functionality used in the GUI (for example, a submap can not be created, because the HP OpenView Windows map does not have write permissions). Problems in retrieving or writing data to or from the database (for example, it may not be possible to get detailed message information from the database).

  • Page 389: Errors Reported Via Stderr And Stdout

    Tuning, Troubleshooting, Security, and Maintenance Troubleshooting: How ITO Reports Errors Errors Reported via stderr and stdout When starting ITO commands or scripts (for example, opcagt and opcsv), errors which occur during the operation are reported to the stderr/stdout device assigned to the calling shell. Errors reported by terminal applications started from the application desktop, are also displayed on stderr and stdout.

  • Page 390: Troubleshooting: When You Need More Information

    Troubleshooting: When you Need More Information Troubleshooting: When you Need More Information Further information to help you troubleshoot is available in: The HP OpenView IT/Operations Software Release Notes, or the files in the ReleaseNotes directory: /opt/OV/ReleaseNotes ITO online help. The documentation set provided with ITO.

  • Page 391: Troubleshooting: Specific Problems, Troubleshooting On The Management Server

    Troubleshooting on the Management Server This section includes descriptions of specific problems that may occur on the ITO management server and provides a solution. For other problems that are not listed here, you can refer to the following manuals: Chapter 10 Tuning, Troubleshooting, Security, and Maintenance Troubleshooting: Specific Problems...

  • Page 392

    Database error: ORA-01034 : ORACLE not available ORA-07318 smsget = open error when opening sgadef.dbf file HP-UX Error: 2: No such file or directory (OpC50-15) Could not connect to database P:openview Please check that the database processes are running (OpC50-2) Description The Oracle database services are not running.

  • Page 393

    Description B ITO connects to Oracle as user opc_op using OS authentication. Oracle allows you to define a prefix for OS authentication users. ITO adds the user opc_op with the assumption that no prefix is used. If you have defined a prefix, ITO will be unable to connect. Solution A Check that the file /etc/oratab exists.

  • Page 394

    Tuning, Troubleshooting, Security, and Maintenance Troubleshooting: Specific Problems Problem Could not connect to Oracle when using SQL*Net, with following error message: Database error: ORA-12158: (Cnct err, can’t get err txt See Servr Msgs & Codes Manual) (OpC50-15) Description ITO connects as user opc_op to the database. For this reason, the current directory (the directory where you started ITO) must be readable by user opc_op Solution...

  • Page 395

    ITO Server Problems and Solutions Problem The ITO management server status is completely corrupted, even after the ovstop opc and ovstart opc sequence. Description Lots of corrupted messages in the message browser; lots of critical ITO error messages, ITO agents on managed nodes cannot be stopped/started, configuration distribution does not work, and so forth.

  • Page 396

    (ovw) Root window is created, but the following error message is immediately displayed: ovw: Could not resolve hostname (mgmt_server_host_name) for licensing Description HP OpenView Windows (ovw) did not have permission to look up the name of the management server in /etc/hosts (this is necessary for license checking). Solution...

  • Page 397

    -eaf | grep ovhelp kill <proc_id> Problem HP OpenView Windows (ovw) objects have been hidden and are no longer visible. Description Using the third mouse button action “Hide Symbol” means the symbol will no longer be displayed on the map.

  • Page 398: Troubleshooting On Managed Nodes

    Troubleshooting on Managed Nodes This section includes descriptions of specific problems that may occur on the ITO managed nodes and provides a solution. 1. Identify the ITO version installed on the management server by looking at the /opt/OV/bin/OpC/install/opcsvinfo file on the management server.

  • Page 399

    Siemens Nixdorf SINIX Solaris Windows NT 3. To obtain more detailed information, use the what(1) command for UNIX systems: For example, for HP-UX 10.x and 11.x managed nodes: what /opt/OV/bin/OpC/opc* Chapter 10 Tuning, Troubleshooting, Security, and Maintenance Troubleshooting: Specific Problems...

  • Page 400

    If you have specified the correct password and the message rexec: Lost connection is displayed, then possibly the management server is not yet known on the managed node. Solution Add the management server entry to /etc/hosts and/or update your Name Server if one is used.

  • Page 401

    IP connectivity (for example, missing routes to the other LAN interfaces). Incomplete Name Service Configuration. of the host name for a managed node (or management server) stored in the name service not containing all host name/IP-address associations, incomplete name-service configuration prevents ITO from applying its authorization algorithm.

  • Page 402

    IP-address of the managed node, a message sent by this managed node will be rejected. For example, if the managed node jacko.bbn.hp.com has the IP-addresses 193.1.1.1 for the X.25 interface, and 15.136.120.169 for the Ethernet interface. The name service used by the managed node is...

  • Page 403

    193 15.136.121.2. arthur.bbn.hp.com arthur 192.1.1.1 arthur.bbn.hp.com arthur-fddi In this case, the resolution of arthur. bbn.hp.com would only return 193.1.4.1, and not all three addresses. IP Connectivity. You can check IP-connectivity by using the ping(1M) command as follows: # ping 193.1.4.1...

  • Page 404

    The managed node and management server both have two LAN interfaces, but are only connected through the 15.136.120 subnet. There is no route from the management server to the managed node through the 193.1.1 subnet, or from the managed node to the management server through the 194.1.1 subnet respectively.

  • Page 405

    The LAN card is not configured with the ieee option required for vt3k operations. Solution A Get the current lanconfig statement from /etc/netlinkrc on the management server, and resubmit the command with the additional ieee parameter. grep lanconfig /etc/netlinkrc lanconfig…ieee...

  • Page 406

    Troubleshooting: Specific Problems Description B No ARPA-to-NS node-name mapping is defined in /etc/opt/OV/share/conf/OpC/mgmt_sv/vt3k.conf and the NS node for the management server is not set, or it belongs to a different domain. Solution B1 Specify a corresponding mapping in vt3k.conf. (See the section “ARPA-to-NS Node-Name Mapping for MPE/iX”...

  • Page 407

    Solution Check that the environment variable DISPLAY on the management server is set to a long hostname; for example xyz.bbn.hp.com:0.0, not xyz:0.0. This display-string is passed to the agent when it tries to start the X-application by redirecting the display to the management server.

  • Page 408

    Check that the installed OS version is still supported by ITO: /opt/OV/bin/OpC/agtinstall/opcversion -a If the installed OS version is not supported by the current version of the ITO agents, ask your HP representative for assistance and available patches. Problem ITO configuration is not installed on the managed node. For this reason, the ITO logfile encapsulator, message interceptor, console interceptor and...

  • Page 409

    Problem After an application upgrade, ITO no longer works as expected. Description After the upgrade of installed applications on the managed node, logfile encapsulation, MPE/iX console message interception, and so forth, appear not to work properly. This could be caused by different message patterns, localized logfiles, different path and/or file name of the logfiles, and so forth.

  • Page 410

    Tuning, Troubleshooting, Security, and Maintenance Troubleshooting: Specific Problems Solution C If you change the password on the managed nodes for default users of an application startup from the ITO Application Desktop, you must adapt the password in the ITO configuration, too. This is only necessary if the application is configured as having a Window (Input/Output), and if no appropriate .rhosts or /etc/hosts.equiv entry is available.

  • Page 411

    Description C The command or application path is different; for example, /usr/bin/ps (HP-UX 10.x, 11.x). Solution C. Use (hard or symbolic) links or copy the command or application to the appropriate destination. Write a script/program which calls the right command or application, depending on the platform. For example: my_ps.sh...

  • Page 412

    -stop; opcagt -start sequence, perform the steps specified in the following tables, working locally on the managed node as user root. All pending messages not yet sent to the management server and all pending actions (for example, automatic and operator-initiated actions, scheduled actions and command broadcast) will be lost.

  • Page 413

    ITO GUIs are terminated (ps -eaf | grep opcui). If they are not, terminate them using the [File: Exit] or (Ctrl+E) functions on any HP OpenView submap owned by ITO or use the kill(1) com- mand. 2. Stop the server processes: ovstop opc ovoacomm b.

  • Page 414

    Tuning, Troubleshooting, Security, and Maintenance Troubleshooting: Specific Problems Table 10-5 Clean-up and Restart ITO Agents on Other SVR4 Managed Nodes 1. Stop ITO agents, including the control agent. 2. Check that all ITO agents are stopped. 3. Check again that all ITO agents are stopped using the list of agent PIDs given by the opcagt - status...

  • Page 415

    Table 10-6 Clean-up and Restart of ITO Agents on AIX and MPE/iX Managed Nodes Task 1. Stop ITO agents, /usr/lpp/OV/OpC/opcagt including the control -kill agent. 2. Check that all ITO /usr/lpp/OV/OpC/opcagt agents are stopped. -status 3. Check again that ps -eaf|grep opc all ITO agents are kill <proc_id>...

  • Page 416

    Tuning, Troubleshooting, Security, and Maintenance Troubleshooting: Specific Problems Problem Automatic or operator-initiated action, scheduled action, command broadcast, or application hangs and does not terminate. Description Due to programming errors or requests for user input, automatic and/or operator-initiated actions, or scheduled actions can hang and not finish. Solution Determine the process ID of the endlessly running action using the ps command.

  • Page 417

    Problem User’s profile is not executed as expected when broadcasting a command or starting an application. Description The profile of the executing user is executed before starting the command/application on the managed node. The profile execution might not work as expected under the following conditions: •...

  • Page 418

    Tuning, Troubleshooting, Security, and Maintenance Troubleshooting: Specific Problems MPE/iX Managed Node Runtime Problems and Solutions Problem Extremely long time for command broadcasting and application startup. Description The command broadcasting and application startup are done within jobs. When the job limit is reached, the jobs are queued. Non-ITO jobs also increase the number of running/pending jobs.

  • Page 419

    Problem ITO agents stop processing due to too many files being open. Description If the permanent file, LASTUUID.PUB.HPNCS has not been created, NCS creates a temporary one, which it does not close. Over a period of time, it tries to re-creates this file many times. The result is that the number of open file descriptors increases, and the system table used to administrate open files is overloaded.

  • Page 420

    Tuning, Troubleshooting, Security, and Maintenance Troubleshooting: Specific Problems Problem Command broadcast and application does not terminate. Description The command broadcasting and application startup are done within jobs named OPCAAJOB. If such a job does not terminate, perform the following solution. Solution 1.

  • Page 421

    Description You can set the port range in the Node Advanced Options window, but this doesn’t have any effect. MPE/iX managed nodes cannot communicate with the ITO management server through a firewall. Solution There is no workaround available. OS/2 Managed Node Runtime Problems and Solutions Problem Action agent cannot redirect stdout and stderr.

  • Page 422

    (llbd), or the DCE RPC daemon (dced/rpcd). Solution For UNIX systems: check that the dced/rpcd is running on the management server, and that either an llbd or dced/rpcd is running on all managed nodes. ps -eaf | grep dced (rpcd) ps -eaf | grep llbd You can use the tools rpccp/dcecp to check that rpcd/dced is running.

  • Page 423

    MIB effectively the automatic resolution of node attributes when you configure a new node in ITO. For more details, see the related snmpd man page. For HP-UX, see the HP OpenView SNMP Agent Administrator’s Guide. Chapter 10 Tuning, Troubleshooting, Security, and Maintenance...

  • Page 424: Nfs Problems And Solutions

    Tuning, Troubleshooting, Security, and Maintenance Troubleshooting: Specific Problems NFS Problems and Solutions Problem The logfile encapsulator reports the warning message: Unable to get status of file <filename>. Stale NFS handle. Description The logfile encapsulator can sometimes perceive logfiles set up on NFS as being open, even after they have been removed.

  • Page 425: Changing Hostnames/ip Addresses, Changing The Hostname/ip Address Of The Management Server

    IP addresses if a node becomes a member of another sub-net. In this case, the IP address or fully qualified domain name may change In general, on HP-UX systems, the IP address and the related hostname are configured in: /etc/hosts...

  • Page 426

    For more information about the Oracle database, see the HP OpenView IT/Operations Installation Guide for the Management Server. 3. Change the ITO management server's IP-address and/or node name in the ITO database according to the “old/new name” naming scheme...

  • Page 427

    5. Stop OpenView and all other integrated services (including ITO): /opt/OV/bin/ovstop 6. Modify the following ITO management server configurations: a. To change the hostname, edit the following files. Always replace any occurrence of the old hostname with the new one:...

  • Page 428

    Tuning, Troubleshooting, Security, and Maintenance Changing Hostnames/IP Addresses 7. Reconfigure the ITO management server system with the new hostname/IP address. For details, see the HP-UX System Manager’s Guide. To change the host name permanently, run the special initialization script /sbin/set_parms.

  • Page 429

    $ORACLE_HOME/bin/svrmgrl connect internal startup exit exit For information on the Oracle database, see the HP OpenView IT/Operations Installation Guide for the Management Server. 11. Start OpenView and all other integrated services (including ITO): /opt/OV/bin/ovstart NOTE At this point the agent will start forwarding its buffered messages.

  • Page 430

    Shut down the ITO agents: /opt/OV/bin/OpC/opcagt -kill b. Update the agent’s opcinfo file with the ITO management server’s new hostname. See Table 10-3 on page 399 for the location of the opcinfo file on the managed nodes. c. Restart the ITO agent processes:...

  • Page 431: Changing The Hostname/ip Address Of A Managed Node

    Re-install the ITO agent software when you have finished with this task. For more information on de-installing and re-installing the agent software, see the HP OpenView IT/Operations Installation Guide for the Management Server. 1. On all ITO managed nodes whose IP address you want to change, stop...

  • Page 432

    4. For all ITO managed nodes you want to modify: a. Reconfigure the ITO managed node system to the new hostname/IP-address. If you are moving from a “non-name server” environment to a “name server” environment, make sure the name server has access to the new hostname/IP-address.

  • Page 433

    6. On your management server for all ITO managed nodes whose hostname/IP-address you want to change: a. Use the ping command to update OpenView’s “knowledge” of the changed hostname and IP address: ping <new_name> b. Update the OpenView Topology Database with: /opt/OV/bin/nmdemandpoll <new_name>...

  • Page 434

    1. Follow steps 2 through 7 above on all management server systems that control or monitor the modified node. 2. Carry out step 8 on all ITO management server systems that refer in any ITO template to the old hostname.

  • Page 435: Ito Security, System Security

    System Security The following sections describe the areas that the administrator needs to address in order to install and run ITO on an HP-UX system that is C2 compliant. For information on how to make a system C2 compliant, see the relevant, product-specific documentation.

  • Page 436

    ACLs. If root-login over the network is not allowed, the ITO agent has to be installed manually. For more information about installing the agent manually, see the HP OpenView IT/Operations Installation Guide for the Management Server Password aging and changing can lead to problems with remote application startup.

  • Page 437: Network Security

    RPC server. For example, in the same way that an RPC server needs to determine whether or not an incoming request is from a genuine ITO client, an RPC client also needs to be sure that the server it is calling really is an ITO server.

  • Page 438

    DCE Nodes Each managed node running the DCE ITO agent and each management server must be member of a DCE cell. The initial cell member must be a DCE server system—this step configures the DCE-cell administrator cell_admin, who plays an important role in all further DCE configuration.

  • Page 439

    1. Ensure that each managed node and the management server are members of a DCE cell as well as a DCE server system itself. To add a node to a DCE cell, run the DCE utility dce_config locally on each of the nodes to be added.

  • Page 440

    -remove option. 5. Use the ITO GUI to select the appropriate security level for the managed node or management server using DCE RPCs. By default, the security level is set to “No Security”. To set or change the security level: a.

  • Page 441

    In the context of ITO, Figure 10-1 on page 442 uses the example of message transmission to illustrate the authentication process the DCE client and server go through. The numerical call outs in Figure 10-1 on page 442 point to further information, which is provided in the following list: 1.

  • Page 442

    Tuning, Troubleshooting, Security, and Maintenance ITO Security 3. The RPC client sends the RPC request 4. The RPC server (opcmsgr) checks the ticket with the password in the key file Figure 10-1 The DCE RPC Client-Server Authentication Process opcctla ITO RPC...

  • Page 443: Port Security

    file and on the management server in the relevant entry in the database. In this way, security on a given managed node may be changed to handle, for example, the addition of sensitive connections.

  • Page 444

    RPC client-server request. For more general information on dynamic port assignment in ITO, see “Processes and Port Numbers” on page 444 and the HP OpenView IT/Operations Concepts Guide. An RPC client using DCE or NCS does not automatically know the port number of the RPC server on the remote system and, consequently, has to obtain this information before initiating an RPC request.

  • Page 445

    ITO assigns port numbers dynamically to those processes that are granted an RPC connection. The port numbers are configurable and are checked against the range defined in the GUI each time an RPC server registers itself. Information relating to the assignment of ITO-specific...

  • Page 446

    ITO Security defined port range on the management server. Subsequently, you will need to restart the server processes and increase the port range. On the managed node, you need to delete the variable OPC_COMM_PORT_RANGE in the nodeinfo file and restart the agents.

  • Page 447

    TT & notification service mgr a. m=number of ITO Server in parallel use n = number of agents in parallel use b. Local = connects to the display server on the local machine Chapter 10 Tuning, Troubleshooting, Security, and Maintenance Ports...

  • Page 448: Port Restrictions

    ITO Security NOTE You need to stop and restart both the management server and the agent processes in order to enable any changes to (or initial configuration of) the port ranges on the ITO management server and the managed node.

  • Page 449

    ITO, when called by clients using UDP. Since the managed nodes may make DCE RPC calls (using UDP) to the rpcd on the management server, it is important that the rpcd/dced runs in an environment (on the management server) where the value of RPC_RESTRICTED_PORTS is set to match the port range defined both...

  • Page 450

    Tuning, Troubleshooting, Security, and Maintenance ITO Security ITO Security The administrator needs to investigate the security implications and possibilities that are addressed during the configuration of ITO itself. For example, managed nodes will only allow those management servers that it recognizes as action-allowed managers to execute operator-initiated actions.

  • Page 451

    Tuning, Troubleshooting, Security, and Maintenance ITO Security File Access and Permissions When a user starts an ITO operator GUI session, the working directory is defined by environment variable $OPC_HOME (if set) or $HOME. If neither $OPC_HOME nor $HOME is set, then /tmp is the default working directory.

  • Page 452

    Application”) that are started from ITO start under the same unix user as the operator, which is not usually opc_op. Program Security The HP-UX 10.x and 11.x programs /opt/OV/bin/OpC/opc and /opt/OV/bin/OpC/opcuiadm) have the s-bit (set user-ID on execution). For MPE/iX, note that the job OPCSTRTJ.BIN.OVOPC contains the readable password of AGENT.OVOPC if the standard STREAM facility...

  • Page 453: Database Security

    Once a user is logged on, security mechanisms of the database control access to the database and tables. For all other database security aspects see Using Relational Databases with HP OpenView Network Node Manager and the vendor’s manuals supplied with the database. ITO Application Setup and Execution Applications run under the account (user and password) specified by the...

  • Page 454

    “File Access and Permissions” on page 451. Passwords on DCE Managed Nodes When executed on the management server with the -server option, the ITO utility opc_sec_register_svr.sh creates a special principal opc-agt-adm which has the permissions needed to modify accounts on the managed node.

  • Page 455

    By default no password is specified. Passwords on Windows NT Managed Nodes The password for the HP ITO account can be assigned during the installation of the agent software. If a password is not assigned, a default password will be created; a password is not assigned by default.

  • Page 456

    Tuning, Troubleshooting, Security, and Maintenance ITO Security Passwords on Novell NetWare Managed Nodes The password for the default operator opc_op is not assigned during the installation of the agent software. For security reasons, it is strongly recommended to assign a password to opc_op, using NetWare tools, after the agent software is installed.

  • Page 457: Auditing

    Normal audit control is the default mode after installation. In normal mode the ITO administrator can change the level of auditing using the Configure Management Server window. Enhanced audit control can only be set by the user root, and cannot be reset without re-initializing the database.

  • Page 458

    Tuning, Troubleshooting, Security, and Maintenance Auditing Table 10-11 Audit Areas of the Administrator Audit Level Audit Area ITO User • logon • logoff • change password Actions, Applications, Broadcasts • start • add/modify/ delete Message Source Templates • add/modify/delete • add/modify/delete automatic and operator-initiated action •...

  • Page 459

    Audit and you are running ITO in a large environment with a high number of managed nodes and users. Otherwise your database may quickly run out of space. See the HP ITO Administrator’s Guide to Online Information for information about how to configure auditing. Chapter 10...

  • Page 460: System Maintenance, On The Ito Management Server

    You can configure scheduled actions to help you with routine system-maintenance tasks. For more information on how to schedule actions, see the HP ITO Administrator’s Guide to Online Information. On The ITO Management Server ITO provides the following methods for backing up data on the ITO management server: •...

  • Page 461: Automated Backup

    For more information, see the appropriate Oracle documentation. For information on how to set up Archive-log mode in ITO, see “Maintaining the Database” on page 468 and the section on database tasks in the HP ITO Administrator’s Guide to Online Information. Off-line Backup The opc_backup tool offers two backup possibilities, which allow you to backup ITO configuration data only, include the current and history...

  • Page 462

    Application Desktop window. • ITO server processes, ITO Operator Web GUI, trouble ticket and notification services remain fully operational. • a partial recovery of the Oracle database is possible, for example: •...

  • Page 463

    2. Shutdown the database 3. Set the archive log parameters in the init.ora file: $ORACLE_HOME/dbs/init${ORACLE_SID}.ora a. Uncomment the following line to start the archive process: log_archive_start = true b. Uncomment the following line to specify the archive directory, and fill in the corresponding values for <ORACLE_BASE> and <ORACLE_SID>: log_archive_dest = <ORACLE_BASE>/<ORACLE_SID>/arch NOTE...

  • Page 464

    Tuning, Troubleshooting, Security, and Maintenance System Maintenance where <user_name> is the name of the operator you want to receive the message, and <message text> is the text of the message you want the operator to see. If the -user option is not specified, all operators receive the message.

  • Page 465

    logs not moved by ito_oracle.sh and copies the ITO configuration in the file system that is not backed up by nnm_checkpoint.ovpl. The NNM script nnm_checkpoint.ovpl backs up all operational NNM databases and also backs up the directory $OV_CONF, which includes some ITO configuration files, the NNM database (flat) files, and the NNM configuration files.

  • Page 466

    Tuning, Troubleshooting, Security, and Maintenance System Maintenance Run all of the restore scripts found in the directory; $OV_CONF/ovbackup/restore/operational/ including ito_restore.sh and nnm_restore.ovpl. The ito_restore.sh script restores the Oracle database asking you to choose between the following restore options: a. to the state of the last backup? b.

  • Page 467

    • Use a full offline backup that was taken with opc_backup with the full option • Restore a full offline backup of the complete system To restore the database to its state at the time of the last backup requires only data contained in the backup. This means, that the restore will work even if you have to re-install ITO.

  • Page 468: Maintaining The Database

    To restore previously backed-up history messages or audit information, see the opchistupl(1m) or opcaudupl(1m) man pages in the HP OpenView IT/Operations Man Pages. Backup the ITO configuration regularly. See the previous sections for more informations on what backup possibilities are available in ITO.

  • Page 469

    Oracle 7.3.4 and 8.0.5 on HP-UX 10.20 and Oracle 8.0.5 on HP-UX 11.0. Binaries for a given version of Oracle on HP-UX 10.20 are not the same as the binaries for the same Oracle version on HP-UX 11.0 - they are different releases.

  • Page 470

    Tuning, Troubleshooting, Security, and Maintenance System Maintenance /etc/csh.login /etc/rc.config.d/ovoracle /etc/opt/OV/share/conf/ovdbconf You will need to change the database release entry and check the .profile and .cshrc files of the users that require access to the database, for example; oracle, root, and opc_op. /etc/tnsnames.ora (if SQL*Net is used) /etc/listener.ora (if SQL*Net is used) /etc/sqlnet.ora (if SQL*Net is used)

  • Page 471

    2. Shutdown the database 3. Move selected control file(s) to a directory on the other disk, for example from disk /u01 to disk /u02: mv /u01/oradata/openview/control03.ctl \ /u02/oradata/openview/control03.ctl 4. Modify the control file name(s) in: $ORACLE_HOME/dbs/init${ORACLE_SID}.ora, for example, from: control_files = (/u01/oradata/openview/control01.ctl, /u01/oradata/openview/control02.ctl, /u01/oradata/openview/control03.ctl) to the following:...

  • Page 472

    A large trapd.log can reduce the performance of ITO. A backup file /var/opt/OV/log/trapd.log.old is provided. For detailed information about system maintenance in HP OpenView, see the HP OpenView Network Node Manager Administrator’s Reference. Maintaining ITO Directories and Files...

  • Page 473: On Ito Managed Nodes

    On ITO Managed Nodes You should periodically backup, and then erase, local ITO logfiles (and their backups). ITO uses 90% of the specified log directory size for local message logging and 10% for error/warning logging. ITO also uses an automatic backup mechanism for the logfiles (four on UNIX systems, nine on MPE/iX).

  • Page 474

    SINIX/Reliant, Solaris, MPE/iX Novell NetWare Windows NT HP-UX 10.x, and 11.x, and Window NT Managed Nodes The following table describes where local logfiles reside on managed nodes running; HP-UX 10.x, and 11.x and Windows NT. Directories Containing Runtime Data /var/lpp/OV/tmp/OpC...

  • Page 475

    Table 10-13 Local Logfiles on HP-UX 10.x, 11.x, and Windows NT Managed Nodes Logfile Default Logfile path /usr/OV/log/OpC/<node> ITO errors/warnings opcerror opcerro(1-3) ITO messages opcmsglg opcmsgl(1-3) AIX and MPE/iX Managed Nodes The following table describes where local logfiles reside on managed nodes running AIX and MPE/iX.

  • Page 476

    Tuning, Troubleshooting, Security, and Maintenance System Maintenance Table 10-15 Local Logfiles on Other Managed Nodes Digital UNIX, DYNIX/ptx, NCR UNIX SVR4, Olivetti UNIX, Logfile Default Logfile path /var/opt/OV/log/OpC ITO errors/warnings opcerror, opcerro(1-3) ITO messages opcmsglg, opcmsg (1-3) Pyramid DataCenter/OSx, OS/2, SCO OpenServer, SCO UnixWare, SGI IRIX, SINIX/Reliant, and Solaris Chapter 10...

  • Page 477: License Maintenance, License Types

    file - not on a central license server. One clear and significant advantage of this approach is that it is not necessary to set up a license server which handles the licenses. In addition, the product may be used even behind firewalls and in Service Guard environments.

  • Page 478: Ito License Maintenance Tools

    5 Nodes and 1 User. NNM can manage a maximum of 25 objects with this license. Instant-On Same as the ITO management server license. Runtime = 120 days Same as the ITO management server Emergency license. Runtime = 14 days...

  • Page 479

    { -delete } | { -report } | { -help } Notes • opclic does not allow more than one server license password in the license file. • Passwords added using unsupported methods are invalid: ITO will not start, and the invalid password(s) must be removed with opclic (see also list).

  • Page 480

    Notes • An ITO management server license may not be removed with the delete option: it can only be removed or replaced with: -add <license_pwd> -force • ITO management server license type: start/end time •...

  • Page 481

    ITO Managed Node APIs and Libraries...

  • Page 482

    ITO Managed Node APIs and Libraries This chapter provides information about: ITO APIs on Managed Nodes ITO APIs for Novell NetWare Managed Nodes ITO Managed Node Libraries Include Files on all Managed Nodes Managed Node Makefiles Appendix A...

  • Page 483: Ito Apis On Managed Nodes

    Novell NetWare managed nodes. An example of how the API functions are used is available in the file opcapitest.c on the management server in the directory /opt/OV/OpC/examples/progs/. See “Managed Node Makefiles” on page 497 for a list of the corresponding makefiles.

  • Page 484: Ito Apis For Novell Netware Managed Nodes, Loadable Modules

    ITO Managed Node APIs and Libraries ITO APIs for Novell NetWare Managed Nodes ITO APIs for Novell NetWare Managed Nodes A set of ITO agent APIs is provided for Novell NetWare agents. These APIs provide inter-process communication between ITO agents and the custom NLMs;...

  • Page 485

    ITO Managed Node APIs and Libraries ITO APIs for Novell NetWare Managed Nodes An additional example is provided in the following file on the management server: /opt/OV/OpC/examples/progs/nwopcnlm.c Appendix A...

  • Page 486: Ito Managed Node Libraries

    ITO A.04.xx libopc_r.sl /usr/lib/libdce.1 /usr/lib/libc.1 -lopc_r -ldce -lc_r The ITO A.04.xx HP-UX 11.x agent is a re-certified HP-UX 10.x agent and does not make use of any HP-UX 11.x specific features, for example Kernel Threads. ITO A.05.00 libopc_r.sl /usr/lib/libdcekt.1 /usr/lib/libpthread.1 /usr/lib/libnsl.1 /usr/lib/libc.1...

  • Page 487

    ITO Version ITO A.03.xx Library libopc_r.sl Libraries /usr/lib/libdce.1 linked to the /usr/lib/libc.1 ITO library. Link and -lopc_r -ldce -lc_r compile options Description libopc_r.sl is the reentrant version of the agent library for the use of DCE. It is not exchangeable with the NCS version.

  • Page 488

    ITO Managed Node APIs and Libraries ITO Managed Node Libraries ITO Version ITO A.03.xx Library libopc78_r.sl Libraries /usr/lib/libdce.1 linked to the /usr/lib/libc_r.1 ITO library. Link and -D_REENTRANT compile -lopc78_r -ldce -lc_r options Description This library is not exchangeable with the NCS version.

  • Page 489

    ITO Version ITO A.03.xx Library libopc.so Libraries linked to the ITO library. Link and -lopc compile options Description Library libopcapi.a Libraries linked to the ITO library. Link and -lopcapi (-lxpg -lc) compile options Description The example Makefile is incomplete. Appendix A ITO Managed Node APIs and Libraries ITO Managed Node Libraries ITO A.04.xx...

  • Page 490

    ITO Managed Node APIs and Libraries ITO Managed Node Libraries ITO Version ITO A.03.xx Library libopc_r.o Libraries linked to the ITO library. Link and -D_THREAD_SAVE compile -D_CMA_NOWRAPPERS_ options -lopc_r -lpthreads -lc_r Description Library libopc.o Libraries linked to the ITO library. Link and -lopc compile...

  • Page 491

    ITO Version ITO A.03.xx Library libopc.so Libraries /usr/lib/libnck.a linked to the /usr/lib/libsocket.so ITO library. /usr/lib/libnsl.a Link and -lopc -lsocket -lnsl compile -lc -lucb options Description Library libopc.so Libraries /usr/lib/libnck.a linked to the /usr/lib/libc.so ITO library. Link and -lopc -lsocket -lnsl compile options Description...

  • Page 492

    ITO Managed Node APIs and Libraries ITO Managed Node Libraries ITO Version ITO A.03.xx Library Libraries linked to the ITO library. Link and compile options Description Library libopc.so Libraries /usr/lib/libnck.a linked to the /usr/lib/libsocket.so ITO library. /usr/lib/libnsl.so Link and compile options Description Library...

  • Page 493

    ITO Version ITO A.03.xx Library Libraries linked to the ITO library. Link and compile options Description Library libopc.a Libraries no libraries linked with linked to the libopc ITO library. Link and -lopc -lsocket -lnsl_s compile options Description Library libopc.so Libraries /usr/lib/libnck.a linked to the /usr/lib/libc.a...

  • Page 494

    ITO Managed Node APIs and Libraries ITO Managed Node Libraries ITO Version ITO A.03.xx Library Libraries linked to the ITO library. Link and compile options Description Library Libraries linked to the ITO library. Link and compile options Description Library opc.dll opcappi.dll Libraries linked to the...

  • Page 495

    ITO Version ITO A.03.xx Library Libraries linked to the ITO library. Link and compile options Description Library Libraries linked to the ITO library. Link and compile options Description Library Libraries linked to the ITO library. Link and compile options Description Appendix A ITO Managed Node APIs and Libraries ITO Managed Node Libraries...

  • Page 496: Include Files On All Managed Nodes

    Intel 486 or higher Intel 486 or higher Silicon Graphics Indigo DEC Alpha AXP Intel 486 or higher Olivetti (INTEL PCs) Pyramid mips_r3000 HP 3000/900 Intel 486 or higher HP-UX 10.x and 11.x /opt/OV/include/opcapi.h Solaris /opt/OV/include/opcapi.h /usr/lpp/OV/include/opcapi.h UNIX SVR4 /opt/OV/include/opcapi.h SCO OpenServer /opt/OV/include/opcapi.h SCO UnixWare /opt/OV/include/opcapi.h...

  • Page 497: Managed Node Makefiles

    /opt/OV/OpC/examples/progs/ Managed Node Makefiles The directory /opt/OV/OpC/examples/progs on the management server also contains the makefiles for building the examples. They use the correct compile and link options needed to get a correctly built executable. Makef.aix Makef.dec...

  • Page 498

    For Windows NT use the Microsoft Developer Studio 4.2 or higher. See also /opt/OV/OpC/examples/progs/README Management Server Makefile The following makefile is available in the directory /opt/OV/OpC/examples/progs on the management server. Makef.hpsv (makefile for the management server on HP-UX) Appendix A...

  • Page 499

    Administration of MC/ServiceGuard...

  • Page 500: Overview Of Hp Mc/serviceguard

    ITO. For more detailed information about MC/ServiceGuard, see the Managing MC/ServiceGuard manual. To install and configure ITO in an MC/ServiceGuard cluster, see Appendix B in the HP OpenView IT/Operations Installation Guide for the Management Server. Appendix B...

  • Page 501: Introducing Mc/serviceguard, Glossary Of Mc/serviceguard Terms

    Introducing MC/ServiceGuard Multi-Computer/ServiceGuard is a powerful hardware and software solution that can switch control from one ITO management server to another if a management server fails. Critical information is stored on shared disks that are also mirrored. Uninterruptible power supplies (UPS) are also included to guarantee continuous operation if a power failure occurs.

  • Page 502

    Administration of MC/ServiceGuard Introducing MC/ServiceGuard package. If a service fails while a package is running, the package may be halted and restarted on an Adoptive Node. MC/Service Guard Daemon A daemon that monitors the state of the SG cluster, all nodes in the cluster, all network resources, and all services.

  • Page 503: How Mc/serviceguard Works, Example 1: Mc/serviceguard Package Switchover

    How MC/ServiceGuard Works The following examples illustrate scenarios in which MC/ServiceGuard is used to switch control of a package between different cluster servers: Example 1: MC/ServiceGuard Package Switchover The SG cluster shown in Figure B-1 represents a typical scenario: Node 1 runs the application packages A and B Node 2 is runs the application package C Node 3 is runs the application packages D, E, and F The nodes are connected by two redundant LANs connected by way of...

  • Page 504

    Administration of MC/ServiceGuard How MC/ServiceGuard Works Figure B-1 MC/ServiceGuard Package Switchover: Before the Switch Bridge Package A Root 1 Package B Node 1 Package A Disk Package A Mirror Assume that node 1 fails. Node 2 is an adoptive node for Package A, but for Package B no adoptive node is specified;...

  • Page 505: Example 2: Mc/serviceguard Local Network Switching

    Figure B-2 MC/ServiceGuard Package Switchover: After the Switch Bridge Node 1 Package A Disk Package A Mirror Example 2: MC/ServiceGuard Local Network Switching The example below shows two SG nodes connected by one virtual LAN. LANs 0 and 1 are connected by a bridge and act as one subnet. Node 1 and node 2 communicate by way of LAN 0.

  • Page 506: Mc/serviceguard Redundant Data And Control Subnets

    Administration of MC/ServiceGuard How MC/ServiceGuard Works Assume that the LAN 0 network interface card on node 2 fails: The standby LAN interface, LAN 1, takes on the identity of LAN 0 on node 2. The subnet and IP addresses are switched to the hardware path associated with LAN 1.

  • Page 507

    Figure B-5 MC/ServiceGuard Redundant Data and Heartbeat Subnets NODE 1 Package A Dedicated Heartbeat LAN Primary LAN: Heartbeat/Data Bridge Standby LAN: Heartbeat/Data The heartbeat interval is set in the SG cluster configuration file. Heartbeat time-out is the length of time that the SG cluster will wait for a node’s heartbeat before performing a transfer of package.

  • Page 508: Mc/serviceguard And Ip Addresses, Portable Ip Addresses

    Administration of MC/ServiceGuard MC/ServiceGuard and IP addresses MC/ServiceGuard and IP addresses One of the many useful features of MC/ServiceGuard is the ability to assign multiple IP addresses to a single LAN interface card. Each primary network interface card has a unique IP address. This address is fixed to the node and is not transferable to another node.

  • Page 509: Mc/serviceguard And Ito, Mc/serviceguard Support On The Management Server

    SG cluster node to another, together with the SG package. MC/ServiceGuard Support on the Management Server NNM 5.0 does not support MC/ServiceGuard directly. In other words, it is not possible to create an NNM 5.0 ServiceGuard package. However, it is possible to run NNM 5.0 independently on each SG cluster node.

  • Page 510

    ServiceGuard Node1 ITO/NNM Agent active connections if the ITO server is running on Node 1 active connections if the ITO server is running on Node 2 To reduce the amount of data on the shared disk, only /var/opt/OV/share and /etc/opt/OV/share are installed on the shared disk.

  • Page 511: Troubleshooting Ito In A Serviceguard Environment, Ito Sg Logfiles, Maintenance Notes For Ito/nnm And Mc/serviceguard

    Troubleshooting ITO in a ServiceGuard Environment This chapter describes some of the problems you might encounter when working with ITO SG packages, and provides some specific troubleshooting hints. For more general troubleshooting information, see the troubleshooting section in the Managing MC/ServiceGuard manual. ITO SG Logfiles MC/ServiceGuard and the ITO SG package use the following two logfiles: /var/adm/syslog/syslog.log...

  • Page 512

    Administration of MC/ServiceGuard Troubleshooting ITO in a ServiceGuard Environment Appendix B...

  • Page 513

    ITO Tables and Tablespaces in the Database...

  • Page 514: Ito Tables In The Database

    ITO Tables and Tablespaces in the Database ITO Tables in the Database ITO Tables in the Database See the HP OpenView IT/Operations Reporting and Database Schema for detailed information about the ITO tables in the RDBMS. Appendix C...

  • Page 515: Ito Tables And Tablespace

    To increase the size of a tablespace, you must add a datafile of a particular size to the tablespace. You can do this interactively using the Oracle tool, Server Manager, or using the sql command: alter tablespace add datafile. Table C-1 on page 516 shows the default tablespace design and the assigned database tables.

  • Page 516

    ITO Tables and Tablespaces in the Database ITO Tables and Tablespace Table C-1 ITO Tables and Tablespaces in an Oracle Database Tables/ Table- Description space opc_act_messages OPC_1 opc_anno_text OPC_2 opc_annotation opc_msg_text opc_orig_ msg_text opc_node_names OPC_3 All other tables OPC_4 Size SIZE 4M AUTOEXTEND ON NEXT 6M MAXSIZE 500M...

  • Page 517

    Tables/ Table- Description space Default OPC_5 tablespace of user opc_op opc_hist_messages OPC_6 opc_hist_msg_text OPC_7 opc_hist_orig_text OPC_8 Appendix C ITO Tables and Tablespaces in the Database Size SIZE 1M AUTOEXTEND ON NEXT 1M MAXSIZE 500M DEFAULT STORAGE ( INITIAL 32K NEXT 32K PCTINCREASE 0 ) SIZE 4M AUTOEXTEND ON NEXT 1M...

  • Page 518

    ITO Tables and Tablespaces in the Database ITO Tables and Tablespace Tables/ Table- Description space opc_hist_ OPC_9 annotation opc_hist_anno_ text Temporary data OPC_TEMP (used for sorting) Index tablespace OPC_INDEX1 for active messages Index tablespace OPC_INDEX2 for history messages Size SIZE 4M AUTOEXTEND ON NEXT 1M MAXSIZE 500M DEFAULT STORAGE (...

  • Page 519

    Table C-2 Non-ITO Specific Tablespace Tables/ Tablespace Description Tablespace SYSTEM containing the system tables. Temporary data. TEMP Rollback RBS1 segments (this tablespace is not ITO specific) Tablespace for TOOLS Oracle Tool Tables (e.g., report writer) Appendix C ITO Tables and Tablespaces in the Database Size SIZE 50M DEFAULT STORAGE (...

  • Page 520

    ITO Tables and Tablespaces in the Database ITO Tables and Tablespace Appendix C...

  • Page 521

    ITO Man Pages Listing...

  • Page 522

    ITO Man Pages Listing This appendix provides a list of each man page for the HP OpenView IT/Operations Developer’s Toolkit. To refer to the man pages, call them from the command line by using: . If you wish to man <manpagename>...

  • Page 523: Overview Of Ito Man, Man Pages In Ito

    Overview of ITO Man Pages You can access the following ITO man pages, either directly at the command line, or by way of the online help: Man Pages in ITO Man Page call_sqlplus.sh(1) inst.sh(1M) inst_debug(5) opc(1|5) opc_audit_secure(1M) opc_backup(5) opc_backup(1M) opc_recover(5) opc_recover(1M) opcack(1M) opcackmsg(1M)

  • Page 524

    files into the database. Change the node address of nodes in the ITO database. Configure ITO client filesets. Configure an ITO management server. Upgrade the structure of the ITO database. Initialize the database with default configuration. Create or destroy the ITO database scheme.

  • Page 525

    opcdbsetup(1M) opcdbupgr(1M) opcdcode(1M) opcgetmsgids(1m) opchbp(1M) opchistdwn(1M) opchistupl(1M) opcmack(1) opcmgrdist(1M) opcmom(4) opcmomchk(1) opcmon(1) opcmsg(1) opcpat(1) opcragt(1M) opcskm(3) opcsqlnetconf(1M) opcsv(1M) Appendix D ITO Man Pages Listing Overview of ITO Man Pages Create the tables in the ITO database. Upgrade the ITO database from a previous version to the current version of ITO.

  • Page 526: Man Pages For Ito Apis, Man Pages For The Hp Openview Servicenavigator

    Man Pages for ITO APIs Man Page opcmon(3) opcmsg(3) Man Pages for the HP OpenView ServiceNavigator Man Page opcservice(1M) Man Pages for the ITO Developer’s Kit APIs Man Page msiconf(4) Registration tool for server configuration files.

  • Page 527

    opc_comif_close(3) opc_comif_freedata(3) opc_comif_open(3) opc_comif_read(3) opc_comif_read_request(3) opc_comif_write(3) opc_comif_write_request(3) opc_connect_api(3) opc_distrib(3) opcagtmon_send(3) opcagtmsg_api(3) opcanno_api(3) opcapp_start(3) opcappl_api(3) opcapplgrp_api(3) opcconf_api(3) opcdata(3) opcdata_api(3) opcif_api(3) opciter(3) Appendix D ITO Man Pages Listing Overview of ITO Man Pages Close an instance of the communication queue interface. Free data that was allocated by opc_comif_read().

  • Page 528

    ITO Man Pages Listing Overview of ITO Man Pages opcmsg_api(3) opcmsggrp_api(3) opcmsgregrpcond_api(3) opcnode_api(3) opcnodegrp_api(3) opcnodehier_api(3) opcprofile_api(3) opcregcond(3) opctempl_api(3) opctempfile_api(3) opctemplgrp_api(3) opctransaction_api(3) opcuser_api(3) Functions to manage ITO messages. Functions to manage ITO message groups. Functions to create and modify ITO message regroup conditions. Functions to configure ITO managed nodes.

  • Page 529

    file tree AR:118 AR:119 HACMP AR:56 manual de-installation AR:175 manual installation AR:53 AR:58 AR:60 NFS cluster clients AR:118 standalone or NFS cluster server AR:118 system resources AR:119 troubleshooting AR:411 alarm severities AR:372 alternative operator CG:203 American EBCDIC AR:342 annotating messages CG:87...

  • Page 530

    AR:315 AR:316 application integration AR:315 as actions AR:323 AR = Administrator’s Reference Guide; CG = Concepts Guide as broadcast commands AR:322 distribution AR:315 HP OpenView AR:315 AR:316 IP Map AR:316 monitoring AR:323 Network Node Manager for IP AR:316 applications CG:40...

  • Page 531

    ASCII AR:338 AR = Administrator’s Reference Guide; CG = Concepts Guide Index character sets character conversion AR:343 external character set AR:339 fileset requirements for HP-UX Managed Nodes AR:336 logfile encapsulator set AR:341 managed nodes AR:337 management server AR:333 valid for logfile encapsulator...

  • Page 532

    AR:427 administrators AR:197 operators AR:197 template groups CG:141 the managed node to a new IP address AR:421 the management server to a new IP address AR:421 user profiles CG:134 configuring nodes CG:103 configuring templates CG:138 CONSDESC.COMMANDS.OVO PC file AR:250...

  • Page 533

    AR:447 operators AR:447 report output AR:447 file tree AIX managed nodes AR:118 AR:119 DEC Alpha NT managed nodes AR:120 Digital UNIX managed nodes AR:122 DYNIX/ptx managed nodes AR:148 HP-UX 10.x managed nodes AR:125 AR:127 HP-UX 11.x managed nodes AR:125...

  • Page 534

    CG:119 adding services CG:119 applications in ITO AR:315 AR:316 copy and paste function CG:107 nodes CG:106 HP OpenView Service Reporter CG:225 HP-UX 10.x managed node requirements AR:35 AR:36 HP-UX 10.x managed nodes AR:63 file tree AR:125 NFS file tree...

  • Page 535

    AR:167 AR:169 DEC Alpha NT AR:61 Digital UNIX managed nodes tips AR:62 DYNIX/ptx managed nodes tips AR:63 HP-UX 10.x managed nodes tips AR:63 HP-UX 11.x managed nodes tips AR:63 IRIX managed nodes tips AR:70 managed node tips AR:47 managed nodes...

  • Page 536

    AR:360 action agent AR:360 monagtp/q AR:360 monitor agent AR:360 mpicmap/q AR:360 mpimap/q AR:360 msgagtdf AR:360 msgagtp/q AR:360 msgip/q AR:360 opcecap/q AR:360 pids AR:360 trace AR:360 local logfiles for HP-UX 10.x AR:470 managed node attributes AR:166 managed node requirements AR:33 Index...

  • Page 537

    AR = Administrator’s Reference Guide; CG = Concepts Guide Index file tree layouts AR:116 files AR:358 hardware requirements AR:29 AR:30 HP-UX AR:303 HP-UX 10.x AR:63 HP-UX 10.x file tree AR:125 AR:127 HP-UX 11.x AR:63 HP-UX 11.x file tree AR:125 installation AR:45 AR:165 installation prerequisites AR:28 installation tips...

  • Page 538

    AR = Administrator’s Reference Guide; CG = Concepts Guide manual installation on AIX nodes AR:53 AR:58 AR:60 on DEC Alpha NT nodes AR:62 on HP-UX nodes AR:66 on OS/2 nodes AR:90 on Solaris nodes AR:96 on Windows NT nodes AR:111...

  • Page 539

    Master Index This index contains references to three ITO manuals. All page numbers are prefaced with a two letter abbreviation indicating the manual that contains the reference. For example, the index entry security that information about security can be found on page 94 in the Concepts Guide, and also on pages 397 and 416 in the Administrator’s Reference.

  • Page 540

    AR:146 SINIX managed nodes AR:155 NFS cluster servers NCR UNIX SVR$ AR:131 SGI IRIX AR:151 Solaris AR:157 NFS managed nodes HP-UX 10.x AR:125 NMEV marker generating AR:249 mapping to ITO AR:247 NNM collection station check for existence CG:178 NNM ECS...

  • Page 541

    For example, the index entry security that information about security can be found on page 94 in the Concepts Guide, and also on pages 397 and 416 in the Administrator’s Reference. on management server AR:251 on OS/2 managed nodes...

  • Page 542

    Master Index This index contains references to three ITO manuals. All page numbers are prefaced with a two letter abbreviation indicating the manual that contains the reference. For example, the index entry security that information about security can be found on page 94 in the Concepts Guide, and also on pages 397 and 416 in the Administrator’s Reference.

  • Page 543

    Master Index This index contains references to three ITO manuals. All page numbers are prefaced with a two letter abbreviation indicating the manual that contains the reference. For example, the index entry security that information about security can be found on page 94 in the Concepts Guide, and also on pages 397 and 416 in the Administrator’s Reference.

  • Page 544

    AR:274 condition-status variable AR:278 timezone string AR:278 CG:94 AR:397 AR:416, shows service hours CG:218 service reports CG:224 CG:225 services HP OpenView CG:119 Settings Browser Settings window CG:60 CG:73 Browser View window CG:60 CG:73 Save Browser Settings window CG:60 CG:73 severity...

  • Page 545

    AR:259 AR:419 snmpd.conf CG:178 software supported OS on managed nodes AR:31 software depot creating AR:65 using AR:66 software distributor (HP-UX 10.x) AR:63 installation tips AR:63 software distributor (HP-UX 11.x) AR:63 installation tips AR:63 software installation/update configuration to managed nodes AR:299...

  • Page 546

    AR:181 Graphical User Interface AR:392 ITO processes AR:391 AR:392 local location broker AR:418 managed nodes AR:394 AR:420 management server AR:387 MPE/iX managed nodes AR:414 MPE/iX managed nodes installation AR:401 AR:420 on OS/2 managed nodes AR:380 opcdbinit AR:390 Oracle database...

  • Page 547: Table Of Contents

    AR:109 ftp reinstallation AR:100 installation AR:99 installation requirements AR:101 manual installation AR:111 standard installation AR:99 AR:106 the HP ITO account AR:114 trust between domains AR:100 user rights AR:114 with reset, threshold monitors CG:170 without reset, threshold monitors CG:171 X Resources...

  • Page 548

    Master Index This index contains references to three ITO manuals. All page numbers are prefaced with a two letter abbreviation indicating the manual that contains the reference. For example, the index entry security CG:94 AR:397 AR:416, shows that information about security can be found on page 94 in the Concepts Guide, and also on pages 397 and 416 in the Administrator’s Reference.

This manual also for:

Openview it

Comments to this Manuals

Symbols: 0
Latest comments: