7.13  Managed Entities

The Managed Entities page lists all the managed entities like EVA, Command View EVA Server, WBEM Server and VLS. As of the WEBES 4.5 release, WEBES has the capability to receive WBEM indications from a WBEM Server.

After adding the required managed devices, you can see the list of managed devices in the Managed Entity page. Figure  7–44 shows the list of all the devices managed by this node.

Figure 7–44 Managed Entities

Click for Larger Image

To view the details of a managed entity, Click on the particular managed entity (for example, Command View EVA Server or VLS ) which lists out the managed entity details as shown in Figure  7–45.

Figure 7–45 Managed Entity Detai

Click for Larger Image

As of the WEBES 4.5 release, the following new fields have been added in the Managed Entity Detail for EVAs:

Choose a Primary Contact
Refresh List
Go To Contacts
Out of Hours Contact
Refresh List
Go To Contacts
HP Contact
Refresh List
Go To Contacts

You can choose from the existing contact names for Primary Contact, Out of Hours Contact, and HP Contact or enter new contact names by clicking Go To Contacts button and filling the required information. The Refresh List button updates the new contact names (added) along with the existing contact names, if any.

If the node is not managing any entity, the Managed Entities page does not show any information on this. The following screen is an example of a node that is not managing any entity.

Figure 7–46 Managed Entities - No Entities

Click for Larger Image

You can modify or remove the existing managed devices from the SEA WUI. Enter the required details in the SEA WUI and Click Apply Changes button to modify the existing managed devices. Click Undo Changes button to cancel the modifications.

To remove the managed devices, check the device name and Click Delete button. Click Delete All to delete all the managed devices.

Refer to section 3.13 "Managed Entities (SMA, EVA, WBEM Server and VLS) Commands" for information on adding an EVA or VLS from the Command Line Interface (CLI).

Installing and Verifying VLS Support

The installation of HP ISEE VLS Support presumes that customers already have HP ISEE A.03.95 or later installed on a required 32-bit ProLiant Windows 2000 server or Windows Server 2003. Although, some ISEE context is provided, these instructions do not address installing or upgrading ISEE. For support on ISEE specific issues, contact your ISEE deployment manager. Typically, customers who acquire a standard configuration of HP ISEE install this themselves. It is expected that the VLS devices are already installed.

The HP ISEE Virtual Library System (VLS) Suport solution is a fully integrated part of a WEBES installation as of version 4.5 and must be installed in an ISEE environment.

The following steps explain how to install and verify VLS:

  1. If applicable, the installer should identify the customer support contract ID up front.
  2. Before attempting installation, the following should be reviewed:
Entity name (fully qualified VLS name; and if appropriate, user-defined alias); IP address is OK but name is better
IP address
Trap destination IP address(WEBES host), most likely localhost
Entitlement type (CarePack ID, Compaq ID, SAID, system handle, or warranty)
Entitlement serial number
Entitlement product number
Entitlement ID
Obligation ID
Physical location
Primary and "out of hours" contact name, phone, email

The following figure shows the Managed Entity Details for VLS:

Figure 7–47 Managed Entity Details Page - VLS

Click for Larger Image
  1. Note that legacy VLS devices may generate "support entitlement failed" because they lack updated labeling with the VLS product bundle model and serial numbers, in addition to individual component model and serial numbers. WEBES needs the specific VLS product bundle model number and serial number to validate entitlement. This is a known limitation; however customers with a valid warranty and/or support contract will receive support for the incidents transported to the HP backend. Out of warranty, VLS devices also generate this message.
  2. Follow the WEBES Install Guide and Release Notes for WEBES 4.5 for establishing HP ISEE VLS Support, including such specifics as the following:
Figure 7–48 VLS Beta Trial Notice

Click for Larger Image
  1. Verify the installation, configuration and ISEE transport.

Note


For Advanced ISEE configurations where the SPOP is a lower version than the ISEE Client, the SPOP must be upgraded before an upgrade to the ISEE Client. WEBES can be installed and run on an SPOP (ISEE advanced configuration), however, it is only supported in a standard ISEE configuration.

The default read community string is "public". The default write community string is "public". These are protected (encrypted) values that should not be changed.

Although a support contract ID is more useful, you can simply enter "warranty" when prompted in the GUI.

Use the "Management URL" link, if needed, to administer Command View VLS.

Configuring VLS devices in WEBES will automatically configure the SNMP trap destination settings in Command View. (This occurs directly on a VLS node unlike an EVA working through a Command View EVA management station.) You can check that they are configured correctly, especially the address of the monitoring station, using the Management URL link on the Managed Entity dialog. The Management URL autofills on the Managed Entity Detail dialog after the MIB has been read.

The "Trap destination IP address" is the WEBES host. Usually, "localhost" is sufficient. When "Network Address Translation" exists between the VLS and the WEBES host, use the IP address that the VLS system uses to reach the WEBES host.

Use the "Warranty Check" link to check warranty information including proper bundle number and serial number.

Other auto-filled fields report the state of the ISEE VLS Support implementation.

A red, crossed-out entity indicates either the NetCitizen2 MIB is not being read or trap destinations are not being set in the trap destination table. Look for mention of either or both on the Problem Reports tab.

If desired, click the New Install event on the Events tab for "Real Time Monitoring" to link to identifying details about each VLS you configured. If a "New Install" event is not generated, check that the VLS node is correctly configured in WEBES. "New Install" events only occur when WEBES first detects a new VLS node.

You can use the command line as an alternative to the WEBES WUI. The same commands apply for VLS as for EVA.
desta entity add
desta entity modify
desta entity remove

As with EVA,While doing an add or modify, follow the prompts for entering or changing configuration information. For modify, if you do not enter data, the value remains unchanged. As with EVA, If you make a mistake, just go to the "Do you want to save these properties?" prompt and enter "N". Then re-issue the "desta entity" add or modify command.

In WEBES, EVAs are referred to as "Managed Entities" or "Storage Cells." The terms apply to VLS devices as well.