The fmsha command provides a command-line interface to the Management Server process running in High Availability (HA) mode. Running Foglight® in HA mode allows you to manage multiple instances of the Management Server in a JGroup partition that supports the HA feature.
• |
Configure JavaTM Virtual Machine (JVM) options and add entries to the Foglight classpath |
The remotemonitor command provides command-line interface to the Remote Monitor application. The Remote Monitor communicates with multiple instances of the Management Server running in HA mode. If a server fails to reply, the Remote Monitor logs an event and sends e-mails to the server administrator. The Remote Monitor uses a list of host names or host names and port numbers to identify High Availability servers that it communicates with. This information is stored in the <foglight_home>/config/remote_monitor.config file under the server.urls entry.
For information on how to install and configure the Remote Monitor, see Remote Monitor ; for additional information about the Remote Monitor application, see the Foglight Installation and Setup Guide.
The remotemonitor command offers a set of options that you can use to perform any of the following operations as required:
• |
Configure JavaTM Virtual Machine (JVM) options and add entries to the Remote Monitor classpath |
Displays the version number, copyright, build number, and installation directory. | |||
The following table shows the default port assignments that are used in HA mode. The port numbers can be specified at installation time, or after the installation using the configuration parameters in the file <foglight_home>/config/server.config.
NOTE: In addition to the ports listed below, in some configurations, the Foglight® Management Server may use additional ports, such as the ports used by JGroups which is the underpinning component of Foglight HA. JGroups is a toolkit for reliable multicast communication. In a default configuration, it dynamically allocates some UDP ports for the communication between cluster members. Network traffic from those ports does not go beyond the local subnet. Therefore, no special firewall configuration is needed. |
Bidirectional between the HA Management Server Primary and Secondary servers. | ||||
Description: Cluster multicast port, used when Foglight is running in HA mode. | ||||
Configuration parameter: server.cluster.mcast_port | ||||
Bidirectional between the HA Management Server Primary and Secondary servers. | ||||
Description: Port for TCP communication between two Management Servers when Foglight is running in HA mode. NOTE: The TCP port number is not configured in the <foglight_home>/config/server.config file, like the rest of the ports described in this table. It is specified in the following line of the <foglight_home>/config/jgroups-config.xml file:
<TCPPING initial_hosts="${jgroups.bind_addr}[7800],otherhost[7800]" … To enable TCP communication, you must first uncomment the appropriate lines of code in the jgroups-config.xml file, as instructed in Tuning connection issues in HA implementations . 2014-04-07 16:53:01.125 VERBOSE [main] STDOUT - --------------------------------------------------------- GMS: address is 127.0.0.1:3307 (cluster=my-cluster-name) | ||||
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Nutzungsbedingungen Datenschutz Cookie Preference Center