Verifying Installation


This page covers steps to verify your GroundWork Monitor installation. It's a good idea to verify the installation by checking the user interface and viewing system data, and checking the connections for Nagios and Foundation. You may also choose to configure your firewall.

1.0 Checking the User Interface

An Operator role is predefined for you. The Operator role provides access to GroundWork Monitor applications such as Status and Event Console.

  1. Log into GroundWork Monitor as an Operator with the User ID operator and Password operator.
  2. Select the Status application tab.
  3. Expand the tree (left panel) and navigate to hosts and services checking that the status information is correct.

2.0 Checking the Connection

The Event Broker takes passive checks sent to port 5667 on the GroundWork server and loads it directly into the Nagios results buffer. Using the Event Broker for processing passive checks by-passes the Nagios command pipe. The Event Broker is part of Nagios and therefore only a Nagios restart is required to have the passive checks working:

  • Check Nagios
    [root@training70 ~]# /usr/local/groundwork/ status nagios
    nagios is already running
  • Check Foundation
    [root@training70 ~]# /usr/local/groundwork/ status gwservices
    Checking for GroundWork Services:
    GroundWork Services:                                        [ running ]
    If you received the message No such file or directory, you may need to enter the following command which puts it on the path environment variable. This is necessary once per shell session.
    [root@training70 ~]# source /usr/local/groundwork/scripts/

3.0 Configuring your Firewall

Upon successful installation and verification of GroundWork Monitor you can choose to configure your firewall. In addition, the following ports must be open on the GroundWork server:

  • 22 SSH (TCP)
  • 80 Apache (TCP)
  • 162 SNMP (UDP)
  • 443 SSL (TCP)
  • 514 Syslog (UDP)
  • 4913 Foundation Listener (TCP)
  • 8004 JMX
  • 8009 Application Server
  • 16011 JMS administration port
  • 16400 JNDI service
  • 60999 JMS listener

4.0 Changes to Syslog Configuration

As part of the installation process, the operating system's syslogd process has been disabled and is replaced with a GroundWork installation of syslogng. Any customizations to /etc/syslog.conf must be moved to /usr/local/groundwork/common/etc/syslog-ng/syslog-ng.conf and any future modifications to /etc/syslog.conf will not have any effect.


installation installation Delete
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.