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

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

فونت

اندازه قلم

+ - پیش فرض

حالت نمایش

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


17.5 CONFIGURATION DOWNLOAD


The configuration of the OVO environment is stored in tables in the Oracle database. The information is available for external programs such as reporting tools or performance tools. The information is also available for sharing with other OVO servers or for creating a backup server in the event, the primary server is unavailable.

17.5.1 Why Download the Configuration?


Download the configuration to create a backup server. This requires many pre-requisites that will be covered in Chapter 19, "Enterprise Management Flexibility with Multiple Management Servers." You can also download the configuration to save the data in the event that the database is recreated. The default database configuration is installed in the initial stage of configuring the management server. After the enterprise-specific components are configured, this information should be preserved for later use in case it becomes necessary to re-load the customized configuration. Another reason to download the configuration is in case you need to distribute or share parts of the configuration with another OVO server. For example, you might have created several templates that could be reused in another OVO domain.

17.5.2 What Can You Download?


You can download all or any part of the configuration that is stored in the OVO database. The configuration download user interface shown in Figure 17-2 shows what components can be selected. Use the OVO Administrator's GUI or the command

opccfgdwn to download the components from the command line after you have created a "download spec file" from within the GUI. As an example, Figure 17-3 shows the selection of two templates.

Figure 17-2. Download Configuration Data window is used to select the specific components you want to download.

[View full size image]

Figure 17-3. Configuration Downloadthe Components window shows the selection of two templates.

[View full size image]

The procedure to create the download specification file is performed within the GUI. Select the following menu items to launch the user interface:

ActionsServerDownload Configuration .

The configuration download window as shown in Figure 17-3 shows an option at the bottom of the window to write the configuration specification file. If this is selected, only the specification file is written to disk. The spec file contains the necessary format that represents the selected components of the configuration. Clicking OK will download the configuration right away. Alternately, after creating the specification file, you can use the

opccfgdwn command at the command line.

17.5.3 Where Will the Downloaded Configuration End Up?


You specify where you want the download configuration files. The default location is /var/opt/OV/share/tmp/OpC_appl/cfgdwn. The default path is shown in Figure 17-4. The configuration download creates a download specification file (download.dsf) and a database index file in the download directory path.

Figure 17-4. Download selected components into the specified directory path.

[View full size image]

During the configuration download from the GUI, a terminal window is open to provide status, as shown in Figure 17-5.

Figure 17-5. Configuration Download Status window shows the progress of the download process.

[View full size image]

The following listing shows the results of the configuration download into the cfgdwn directory. A subdirectory and the download specification file are created.

# ls -l
total 2
drwx 3 root sys 96 Aug 7 22:27 C
-rw-rr 1 root opcgrp 61 Aug 7 22:27 download.dsf

This listing shows the contents of a download.dsf specification file:

# more download.dsf
INTERFACE_TEMPLATE "opcmsg(1|3)" ;
LOGFILE_TEMPLATE "test" ;
download.dsf: END

Looking inside the "C" directory, we find the database index file cfgdwn.idx. You also see the TEMPLATES directory that contains the components of the download. The "C" directory listing is shown here:

# ls -lR
total 2
drwx 4 root sys 96 Aug 7 22:27 TEMPLATES
-rw- 1 root sys 440 Aug 7 22:27 cfgdwn.idx
./TEMPLATES:
total 0
drwx 2 root sys 96 Aug 7 22:27 INTERFACE
drwx 2 root sys 96 Aug 7 22:27 LOGFILE
./TEMPLATES/INTERFACE:
total 4
-rw- 1 root sys 1971 Aug 7 22:27 interface.dat
./TEMPLATES/LOGFILE:
total 2
-rw- 1 root sys 739 Aug 7 22:27 logfile.dat

17.5.4 How Can You Distribute the Downloaded Configuration?


Prior to jumping right into our discussion on how to distribute a downloaded configuration, let us step back and consider why this process is necessary. One of the reasons you would download the configuration is to ensure that you have a current snapshot of the OpenView server environment. The configuration takes time and resources to set up and you can protect this investment if you take periodic snapshots of the environment as it evolves. The configuration download is one component of the management server environment. Other aspects of the environment were discussed earlier in this chapter. Another reason for performing a configuration download is to keep multiple management server configurations in sync. If you distribute the management and monitoring tasks performed by OVO across multiple servers, any one server could take over for another server in the event of failure. This is possible provided that you are regularly synchronizing the configuration across the servers. In the rest of this section, we discuss the details of the configuration download process.

Use the command

opcmgrdist on the primary server to distribute the downloaded configuration to the secondary server(s). This assumes that you have set up the second management server(s) to receive the configuration. The steps for this include the following:



    / 276