HP OpenView System Administration Handbook [Electronic resources] : Network Node Manager, Customer Views, Service Information Portal, HP OpenView Operations نسخه متنی

اینجــــا یک کتابخانه دیجیتالی است

با بیش از 100000 منبع الکترونیکی رایگان به زبان فارسی ، عربی و انگلیسی

HP OpenView System Administration Handbook [Electronic resources] : Network Node Manager, Customer Views, Service Information Portal, HP OpenView Operations - نسخه متنی

Tammy Zitello

| نمايش فراداده ، افزودن یک نقد و بررسی
افزودن به کتابخانه شخصی
ارسال به دوستان
جستجو در متن کتاب
بیشتر
تنظیمات قلم

فونت

اندازه قلم

+ - پیش فرض

حالت نمایش

روز نیمروز شب
جستجو در لغت نامه
بیشتر
لیست موضوعات
توضیحات
افزودن یادداشت جدید



Chapter 21. Plan, Document, Take Corrective Actions, Administer Changes


It is imperative that the

OpenView Operations (OVO) architecture and processes be well planned and documented. It is also crucial that you have management buy-in for this project because you will likely need co-operation between teams, such as application development, network configuration, and client access. For example, OVO requires that an OVO agent be installed on each monitored system. Typically, the OVO administrator and the client administrator are different engineers and may report to different managers. You will need to get approval from the system administrator to install the OVO agent on the client.

During the planning phase, you should keep accurate documentation such as network architecture, supported platforms, and monitored applications. You should also document which templates are assigned and distributed to which nodes. The OVO documentation should evolve with the project.

The purpose of corrective actions is to return the application (or whatever caused the OVO message to appear in the browser) back to its normal state. Corrective actions can be configured as automatic or manual from the user interface. Corrective actions may include restarting processes, sending email, or linking to a trouble ticketing system such as

OpenView Service Desk (OVSD).

Changes in the OVO environment may include adding templates and template conditions, rewriting scripts that are executed by templates, adding nodes to the node bank, or simply adding OVO operators. As your monitored enterprise evolves with new systems and applications, so should your OVO node bank, application bank, operator bank, and message source templates. Administering changes includes acting on OVO messages, updating the OVO environment, and updating documentation. Networks, systems, and applications are continuously evolving. Applications and database server versions change. New hardware and new users are deployed. As such, the administration of application monitoring needs to constantly change. New OVO agents need to be distributed, new templates need to be created, and new operators need to be configured.


    / 276