VMware VCM 5.3 Guía para resolver problemas descargar pdf (Pagina 17)

Network Connectivity

VCM relies heavily on network connectivity to all Agents. In systems where you have a split installation,

failed network connectivity can also cause problems with VCM. Failures in network connectivity are not

likely to occur across all systems involved with the operation of VCM at the same time, so issues with the

network are occasionally easier to diagnose. Issues with the network are usually first discovered in the UI

with the failure of some VCM or VCM Patching job to a single or subset of machines. A common error

message associated with connectivity problems is “Ping Failed” as seen below.

The simplest way to test network connectivity is to ping the Agent from the Collector. If the environment

contains a firewall, if the Agent is a UNIX agent, or if the Agent machine is using the HTTP protocol

instead of the DCOM protocol for its primary communication method, it may be necessary to connect to

the HTTP port of the Agent on the target machine from the Collector. This can be done by using the telnet

command in the following way:

C:\> telnet target_machine 26542

In the above example, the name of the machine we are testing is “target_machine” and the HTTP port

used is 26542. A successful test of this type should return nothing but a blank screen. This is the target

system answering the connection request and awaiting further instructions. You can break this connection

by typing “Ctrl-]” and then typing “quit” to exit the telnet program. If you receive any other message,

such as “Connection refused” or “Connection timeout”, that is a good indication of network

communication problems. These issues will need to be worked out with the local network support

individuals before VCM troubleshooting may continue.

Hardware and Performance Issues

Hardware and performance issues are some of the most difficult issues to diagnose because they are

usually sporadic and random. In fact, there may be times where the only constant you can count on is

random errors. This is the time to look at possible hardware and/or performance problems. Running out

of disk space is the most common hardware problem. Simply check the file manager to verify that

enough disk space is present for both the database and for VCM itself. Next, make sure that there is

enough memory and enough CPU cycles to ensure that the VCM services and processes can function

properly. If VCM is competing with several other processes on the system that are unrelated to VCM,

performance may degrade to the point that errors and exceptions are produced in the debug log. Finally,

it may be necessary to run diagnostics on the hardware components, such as the memory chips,

processor(s) and system boards. Refer to VCM documentation to see the recommended hardware

configurations needed to run VCM properly in the different possible environments.

Types of Problems

VMware, Inc. 17

1 2 ... 12 13 14 15 16 17 18 19 20 21 22 ... 67 68

Sin comentarios

VMware VCM 5.3 Guía para resolver problemas Pagina 17