Getting Started with vFabric Hyperic v.5.7 - VMware

More documents

Recommendations

Info

JSW runs as a native executable; it invokes and monitors the vFabric Hyperic Agent's JVM,based on configuration information provided to the wrapper at startup. In this way, the wrappersupports restarts of the JVM process without stopping the wrapper process itself. The JSWprocess acts as a watchdog for the JVM process, periodically pinging it for availability.For information about wrapper configuration, see Agent Java Service Wrapper Configuration.What Happens When an Agent Starts UpA vFabric Hyperic Agent needs to know how to connect to the vFabric Hyperic Server, and thevFabric Hyperic Server needs to know how to connect to the vFabric Hyperic Agent — eachcomponent needs the IP address and listen port (and other connection properties) to use toestablish a connection with the other. As described in About Agent Configuration you can definethe connection properties interactively at first agent startup, or in the agent'sagent.properties file.When you start a vFabric Hyperic Agent:5. The agent checks to see if there is a /data directory that contains the vFabric HypericServer's connection properties.o At first startup, the /data directory will not exist — it is created after the firstsuccessful connection between agent and server is established.o If the agent finds the connection properties, it tries to connect to the vFabricHyperic Server - see step 5 below.6. If the agent did not find the /data directory, it looks for an agent.properties file in ahidden directory named .hq in the home directory of the user that runs the agent.o This directory will not exist unless you have previously created it. This location forthe properties file is supported to ensure configuration data is not lost in theevent that the complete agent installation is overwritten in an upgrade.o If the agent finds the connection properties, it tries to connect to the vFabricHyperic Server - see step 5 below.7. If the agent did not find the agent-server connection properties in anagent.properties file in the hidden /.hq directory, it looks at theagent.properties file in its /conf directory.o If the agent finds the connection properties, it tries to connect to the vFabricHyperic Server - see step 5 below.8. If the agent did not find connection properties in the agent.properties file in its/conf directory, it prompts for the properties to be supplied interactively in thecommand shell.9. Upon obtaining the agent-server connection properties, the agent attempts to connect tothe vFabric Hyperic Server.10. Once communications between agent and server have been successfully established:o The agent saves the vFabric Hyperic Server connection settings inAgentHome/data.14
o The vFabric Hyperic Server saves the vFabric Hyperic Agent's connectionsettings in the vFabric Hyperic database.Automatic Restart BehaviorAs described above, JSW process periodically pings the agent JVM process.If the JVM process exits with a non-zero exit code, indicating the JVM is hung or crashed, theJSW will restarts the JVM process. Messages in the Agent and JSW logs indicate that the JSWhas restarted the Agent. If the JSW cannot restart the JVM process, it will try again, up to a totalof five times. You can configure different actions for the JSW, including the action it takes upona particular JVM process exit code, and the number of times that it will attempt to restart theprocess.Agent - Server CommunicationThis section is an overview of the communications between a vFabric Hyperic Agent and thevFabric Hyperic Server.Agent-to-Server CommunicationUpon startup, a vFabric Hyperic Agent initiates a communications channel with the vFabricHyperic Server. The agent continuously batches and sends monitoring results for the platform tothe server. Agent-to-server data flows over HTTPS via a byte-encrypted XML protocol calledLather.The agent sends this data to the server:SSL certificate — When an agent connects to a server using https, it presents an SSLcertificate as part of the handshake. For information about certificate verification, seevFabric Hyperic 4.6.x SSL Certificate Processing on About SSL in vFabric Hyperic.plugin status — When an agent starts up and loads the plugins in its plugin directory, itsends a plugin status report to the server, including the MD5 checksum of each plugin itloaded. This server uses this information for the server-agent plugin synchronization(SAPS) process, described in About Plugin Sync at Agent Startup on Plugin Deploymentand Management in vFabric Hyperic Administration.metrics — You can configure the batch size is using the agent.maxBatchSizeproperty in agent.properties.event — You can configure the batch size using agent.eventReportBatchSize inagent.properties.o auto-discovery results — Auto-discovery results are reported after each autodiscoveryscan.o By default, the default scan runs every 15 minutes. You can configure thefrequency using the autoinventory.defaultScan.interval.millis inagent.properties15
Page 1 and 2: Getting Started with vFabricHyperic
Page 3 and 4: ContentsAbout Getting Started with
Page 5 and 6: About Getting Started with vFabric
Page 7 and 8: Key Facts for vFabric Hyperic Insta
Page 9 and 10: About SSL in vFabric HypericAbout t
Page 11 and 12: By default, the vFabric Hyperic Ser
Page 13: You can also ensure that you do not
Page 17 and 18: Unidirectional Communication via a
Page 19 and 20: Propertyserver.java.optstomcat.maxt
Page 21 and 22: vFabric Hyperic Installation and St
Page 23 and 24: 3. Start the vFabric Hyperic Server
Page 25 and 26: d. Open firewall port if necessary.
Page 27 and 28: 6. Import discovered resources.o Af
Page 29 and 30: Step-by-Step ProceduresSelect and D
Page 31 and 32: About vFabric Hyperic JREsBoth vFab
Page 33 and 34: Password Requirement for vFabric Hy
Page 35 and 36: About the vFabric Hyperic vAppA vir
Page 37 and 38: vFabric Hyperic Server vApp Adminis
Page 39 and 40: Prerequisites and RequirementsThese
Page 41: 5. Click the Custom Properties tab.
Page 44 and 45: checkpoint_segments — Set the val
Page 46 and 47: Stop PostgreSQLStop PostgreSQL with
Page 48 and 49: o On Windows platforms, enter:PathT
Page 50 and 51: 17. What port should HQ's built-in
Page 52 and 53: 3. On the Administrator User Inform
Page 54 and 55: After installing the agent, proceed
Page 56 and 57: 3. Entering the following command i
Page 58 and 59: Install vFabric Hyperic Server:1. O
Page 60 and 61: For information and required and op
Page 62 and 63: About vFabric Hyperic Agent RPMThe
Page 64 and 65:
o On Windows platforms, install the
Page 66 and 67:
Set Up Agent in Properties FileAbou
Page 68 and 69:
About Password EncryptionThe first
Page 70 and 71:
About Where the Agent Finds Server
Page 72 and 73:
agent.setup.camPortDescriptionYou c
Page 74 and 75:
agent.setup.agentIPDescriptionThis
Page 76 and 77:
agent.keystore.pathDescriptionThis
Page 78 and 79:
About unidirectional communicationI
Page 80 and 81:
If the properties file does not alr
Page 82 and 83:
Two-Step Migration ProcedureIn this
Page 84 and 85:
One-Step Migration ProcedureNote: I
Page 86 and 87:
Command Required Optionalhq-exporth
Page 88 and 89:
Argument Description Default Behavi
Page 90 and 91:
Parameter Description DefaultqueryT
Page 92 and 93:
hq-install.log — this file contai
Page 94 and 95:
Create a Custom Agent Upgrade Bundl
Page 96 and 97:
The installer installs a new versio
Page 98 and 99:
Change vFabric Hyperic Server Sizin
Page 100 and 101:
Changing from Unidirectional to Bid
Page 102 and 103:
Configure vCenter Operations Manage
Page 104 and 105:
Depending on your environment, you
Page 106 and 107:
For example:$ telnet 192.168.1.114
Page 108 and 109:
To resolve this problem, you must r
Page 110 and 111:
Java Service Wrapper TimeoutUnder h
Page 112 and 113:
Overloaded BackendIf the vFabric Hy
show all

Getting Started with vFabric Hyperic v.5.7 - VMware

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?