VMware VCLOUD REQUEST MANAGER 1.0.0 Instrukcja Użytkownika Pobierz pdf (Strona 8)

Release Notes for Zenoss Ser-

vice Dynamics Version 4.1.1

• In device/component fields, if you enclose a query in double quotes, it searches for that device or component

by using an exact match search (fastest). For example, searching for "abc" matches abc, but not abcd or

babc.

For more information about event console filtering, see the chapter titled "Using Resource Manager" in Resource

Management Administration.

1.4.1.4. Zenoss DataStore

• Command-line access to the Zenoss DataStore is available only to the zenoss user; Zenoss DataStore tools

are located only in the zenoss user's $PATH.

Run all Zenoss DataStore commands as the zenoss user, as in:

su - zenoss

zends -u root

• If you currently are running Zenoss DataStore 5.5.13, you must install an updated version (Version 5.5.15).

To install the new version, run this series of commands:

service zenoss stop

service zends stop

rpm -Uvh zends-5.5.15-1.Version.el5.i386.rpm

service zends start

service zenoss start

• When upgrading, zends.cnf file customizations may need to be manually merged. For more information,

refer to the chapter titled "Upgrading" in Resource Management Installation.

• When upgrading with a remote Zenoss DataStore configured, any modifications made to $ZENHOME/bin/

zenoss_init_pre or $ZENHOME/bine/zenoss_upgrade_pre will be preserved automatically as part of the up-

grade. Modified versions will be backed up to zenoss_init_pre.rpmsave and zenoss_upgrade_pre.rpmsave,

respectively. You must merge any changes to these settings into the zenoss_init_pre and

zenoss_upgrade_pre files before starting Zenoss for the first time. (Internal Defects 29584, 29553)

1.4.1.5. IPv6

Resource Manager can model and monitor IPv6-addressed devices by using SNMP, Telnet or SSH. Ping mon-

itoring is also supported for IPv6. Resource Manager installation (and communications links among Resource

Manager components) must continue to be over IPv4. This includes all links between local or distributed Zen-

Hubs and collectors, and Resource Manager dependencies (such as RabbitMQ).

When adding a new device to Resource Manager, the DNS resolution of the device name dictates whether

Resource Manager attempts to connect by using IPv4 or IPv6. If you enter an IP address directly (either as a

device name or by manually changing a device's management IP), then Resource Manager can be forced to

use IPv4 or IPv6 manually.

If you want to monitor devices in your infrastructure that have IPv6 addresses, make sure you have installed

and configured an IPv6 interface on your Resource Manager server.

1.4.1.6. ZenHub

This release of Resource Manager uses RelStorage, a backend for ZODB that stores pickles in a relational

database. With the switch to RelStorage, the pcachesize and pcachedir options are no longer relevant. Remove

these options from any daemon configuration (.conf) files. (Defect 28620)

1.4.1.7. TrapForwarder ZenPack

The TrapForwarder ZenPack is deprecated in this release. SNMP traps are now handled as part of notifications.

For more information, see the chapter titled "Using Resource Manager" in Resource Management Administra-

tion.

1.4.1.8. Reports

The process for determining device state has changed for the Availability report. Previously, if an event was

reported that indicated a device down condition before the start of the report window, this event would not be

1 2 3 4 5 6 7 8 9 10 11 12 13 ... 20 21

Komentarze do niniejszej Instrukcji

Brak uwag

VMware VCLOUD REQUEST MANAGER 1.0.0 Instrukcja Użytkownika Strona 8

Komentarze do niniejszej Instrukcji

Powiązane produkty i podręczniki dla Oprogramowanie VMware VCLOUD REQUEST MANAGER 1.0.0