E-mail
|
Key
This line was removed.
This word was removed. This word was added.
This line was added.
|
Changes (6)
View Page History... |
| {toc:minLevel=4|maxLevel=5|printable=false} |
| h4. 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. |
... |
| \\ !verify_1.jpg|border=1! |
| h4. 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: |
... |
| {code}[root@training70 ~]# /usr/local/groundwork/ctlscript.sh status gwservices Checking for GroundWork Services: |
| GroundWork Services: [ running ]{code} |
| GroundWork Services: [ running ]{code} |
| {Note}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. {code}[root@training70 ~]# source /usr/local/groundwork/scripts/setenv.sh {code}{Note} |
| h4. 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: |
... |
| * 60999 JMS listener |
| h4. 4.0 Changes to Syslog Configuration |
| |
... |