Unicenter Network and Systems Management Option for VMware Readme - CA Technologies
{{search ? 'Close':'Search'}}

Unicenter NSM Option for VMware Software 3.1


1.0 Welcome

2.0 Operating System Support

3.0 System Requirements
3.1 Hardware

4.0 Installation Considerations

5.0 Known Issues

6.0 Contacting Technical Support


1.0 Welcome

Welcome to Unicenter NSM Option for VMware Software. This file consists of information about the Unicenter NSM Option for VMware Software, known issues and how to contact technical support.


2.0 Operating System Support

The following operating systems are supported (as of the publishing of this document):

Unicenter NSM Option for VMware Software Manager

Windows

  • Windows NT 4.0 +SP6a

  • Windows 2000

  • Windows 2003

    Unicenter NSM Option for VMware Software Session Manager/Agent

    Windows

  • Windows NT 4.0 +SP6a

  • Windows 2000

  • Windows 2003

    VMNIX

  • VMware ESX Server V1.5

  • VMware ESX Server V2.0.0

  • VMware ESX Server V2.0.1

    Linux

  • Red Hat 8.0

  • Red Hat AS 2.1

  • SuSE SLES 8.0

    Computer Associates supports these operating systems for the duration of their lifecycle (as determined by the operating system's manufacturer or until Computer Associates announces that we are dropping support). Visit our web site at http://ca.com/ for the latest information about supported operating systems.


    3.0 System Requirements

    For the most up-to-date system requirements, visit our web site at http://ca.com/.

    Unicenter NSM Option for VMware Software Manager

    Windows

  • Unicenter NSM 3.0 (0000, 0202, 0211) (Unicenter Explorer, WorldView, Event Management, and Agent Technology including DSM)

  • Unicenter NSM 3.1 (Unicenter Explorer, WorldView, Event Management, and Agent Technology including DSM)

    Unicenter NSM Option for VMware Software Session Manager/Agent

    Windows

  • Unicenter NSM 3.0 (0000, 0202, 0211) (Agent Common Services)

  • Unicenter NSM 3.1 (Agent Common Services)

  • VMware GSX Server V2.0

  • VMware GSX Server V2.5

  • VMware GSX Server V2.5.1

    VMNIX

  • Unicenter NSM 3.0 (Agent Common Services)

    Linux

  • Unicenter NSM 3.0 (0000, 0305) (Agent Common Services)

  • VMware GSX Server V2.0

  • VMware GSX Server V2.5

  • VMware GSX Server V2.5.1

    Patches

    The following published patches must be installed prior to installing Unicenter NSM Option for VMware Software. Please contact support for a complete, up to date list of required patches.

    Windows

    Unicenter NSM 3.0/0202

  • QO41549

  • QO50836

  • QO50823

  • QO50824

  • QO50825

    Unicenter NSM 3.0/0211

  • QO40265

  • QO40741

  • QO39833

  • QO44909

  • QO47035

  • QO50730

  • QO50129

  • QO50131

  • QO50132

    Unicenter NSM 3.0/0305

  • QO50834

    Unicenter NSM 3.1/0000

  • QO50760

  • QO50764

  • QO50762

  • QO50761

  • QO50763

  • QO50776

    Linux

    Unicenter NSM 3.0 GA

  • QO50835

  • QO50833

    Netware

    Unicenter NSM TNG 2.4.2 GA

  • QO50826


    3.1 Hardware

    The hardware requirements for Unicenter NSM Option for VMware Software are the same as Unicenter NSM.


    4.0 Installation Considerations

  • The VMware Management User Interface must be installed on the VMware GSX Server so the CA VMware Agent functions properly on the GSX platform. Please install the VMware Management User Interface package prior to installing any Unicenter NSM Option for VMware Software components.

  • The "hosts" file on the Windows Manager must be modified to add the names and IP Addresses for servers with no DNS entry.


    5.0 Known Issues

  • On any Linux or VMNIX Server please make sure that "uncompress" utility is present. If not please run following command:
    ln -s /bin/gunzip /bin/uncompress 

  • Do not uninstall Unicenter NSM Option for VMware Software using Unicenter NSM Uninstall. Unicenter NSM Option for VMware Software should be uninstalled from the Windows Control Panel Add/Remove Programs. When you uninstall Unicenter NSM Option for VMware Software, DIA is also uninstalled if Unicenter NSM Option for VMware Software is the only consumer of DIA.

  • You must have at least one virtual machine (VM) residing on your VMware server for Unicenter NSM Option for VMware Software to discover your server.

  • All virtual machines on a GSX Server should be powered on for Remote Management. The agent will not detect virtual machines which are powered on for Local Management.

  • InstallShield Process IDriver.exe will reach 99% CPU usage once the Unicenter NSM Option for VMware Software installation finishes on Windows NT Server running VMware GSX Server. This is an InstallShield issue. The issue number is 1532798.

  • After installing the performance agents, the performance agent updates, and the performance manager updates, reconfigure the performance agents by "dropping" a profile on them in performance configuration. This updates the performance agent configuration to make the VMware metrics available in performance scope and performance trend.

  • You may experience timeouts when monitoring a large number of VMs in Performance Scope. To eliminate timeouts, ensure the latest updates for Performance Scope and the Performance Agents are installed.

  • If you are unable to connect to a VMware Server through CA VMware Administrator GUI please make sure that the Address property of the VMware Server in the Business Process View is set correctly. If not, please change the Address accordingly. You can view the properties of the objects by right clicking on them and selecting Open Details if you are in Unicenter NSM 2D Map or Property Notebook if you are in Unicenter NSM Explorer.

  • Make sure that the configuration files for all VMs on your VMware GSX Server on Windows do not have parentheses '( )' in the file names.

  • Due to limitations in the VMware API on VMware ESX Servers, when no VMs are running on the server, monitoring any VMware VM Disk or VMware VM Network metrics in Performance Scope will result in an error message being displayed. You can check if no VMs are running by looking at the VMware Engine System – Running VMs metric.

  • When a particular VM is not running, the majority of VMware metrics monitored by the Performance Agent will return a 0 (zero) value. By looking at the VMware VM System – VM State metric you can determine if the VM is running or not. However, some metrics will still be available if they are stored in the VM configuration file on the server. These metrics are:

    VMware VM Memory – Maximum Available Kb

    VMware VM Memory - Minimum Available Kb

    VMware VM Memory - Configured Kb

    VMware VM Memory - Configured Shares

    VMware VM CPU - Configured Shares

    VMware VM System - Virtual CPU Count

  • In the Unicenter NSM Option for VMware Software Administrator GUI, for ESX Servers, the CPU usage total for virtual machines and the service console may exceed 100%. This may happen when the service console and virtual machines are heavily using CPU cycles.

  • When monitoring VMware metrics in Performance Scope, the real-time chart update frequency may not be the same as the specified poll period due to delays in the VMware interface.

  • After an individual component install (if selected one after the other) on Windows NT Server an InstallShield error message 1628 maybe displayed. Note: Unicenter NSM Option for VMware Software gets installed even though this message is displayed. This is an InstallShield issue. The issue number is 1532798.


    6.0 Contacting Technical Support

    For technical assistance with this product, contact Technical Support at http://ca.com for a complete list of locations and phone numbers. Technical support is available 24 hours a day, 7 days a week.

Chat with CA

Just give us some brief information and we'll connect you to the right CA Expert.

Our hours of availability are 8AM - 5PM CST.

All Fields Required

connecting

We're matching your request.

Unfortunately, we can't connect you to an agent. If you are not automatically redirected please click here.

  • {{message.agentProfile.name}} will be helping you today.

    View Profile


  • Transfered to {{message.agentProfile.name}}

    {{message.agentProfile.name}} joined the conversation

    {{message.agentProfile.name}} left the conversation

  • Your chat with {{$storage.chatSession.messages[$index - 1].agentProfile.name}} has ended.
    Thank you for your interest in CA.


    How Did We Do?
    Let us know how we did so that we can maintain a quality experience.

    Take Our Survey >

    Rate Your Chat Experience.

    {{chat.statusMsg}}

agent is typing