VMware VCLOUD REQUEST MANAGER 1.0.0 Manuel d'utilisateur télécharger pdf (Page 12)

Release Notes for Zenoss Ser-

vice Dynamics Version 4.1.1

Prerequisite Restriction

Product Resource Manager 4.x, Zenoss 2.5 or higher

Required ZenPacks ZenPacks.zenoss.HpuxMonitor

Supported HP-UX Releases HP-UX 11

Supported Processors PA-RISC, Itanium

Table 2. HP-UX Prerequisites

• The section titled "Limitations" has been removed.

• In the chapter titled LDAP Authentication, the following note was removed:

Zenoss recommends that you make sure that your LDAP server requires at least four successive failures to

lock an account. Due to authentication design, each login to Resource Manager goes through three different

Web pages. Each one of these pages requests a user authentication, which ends up making a single call to

the LDAP backend. Thus, if the user makes one mistake and the LDAP server locks the account on three

successive failures, the user's account will be locked even though he specified the password once.

• In the chapter titled Multi-Realm IP Networks, the following prerequisite was added:

Before setting up multi-realms, you must delete all Resource Manager networks. (These are automatically

recreated.)

• In the chapter titled Nexux7k, the following limitation has been added:

To model Cisco Nexus 7000 series switches with multiple enabled VDCs, the user name used to perform

modeling must be authorized to run the following command on the switch:

show running-config vdc-all

This command requires authenticating as a user with one of these user roles:

• network-admin

• network-operator

• vdc-admin

• vdc-operator

1.6.3. Zenoss Service Dynamics Impact and Event Management

In the chapter titled "Working with Impact," a new section was added.

1.6.3.1. Adding Context Information to Notifications

In addition to the context information available to notifications (see the section titled "Working with Notifications"

in Resource Manager Administration), Impact events populate a variable (esa) which has one variable (causes),

which is a list. Each list entry is an event, with these attributes:

• evt

• clearEvt

• eventSummary

• clearEventSummary

• urls

Another entry, impactChain, contains the chain of resources that Resource Manager uses to determine that

this event caused the service problem. The causes are listed in order of probability of root cause, from highest

to least.

To iterate over the list items in causes using TALES, you can use the tal:repeat clause. For example:

1 2 ... 7 8 9 10 11 12 13 14 15 16 17 ... 20 21

Pas de commentaire

VMware VCLOUD REQUEST MANAGER 1.0.0 Manuel d'utilisateur Page 12