Purpose
This Solution Guide will provide a detailed, single reference for configuring opEvents for use in a production environment.
Related Pages
Additional related pages will be linked throughout this Solution Guide.
Scenario
The administrator is deploying opEvents 4.x in a production environment and desires to enable as much functionality as possible, beyond the default settings provided by the installer.
Prerequisites
This Solution Guide assumes the installation, setup and configuration of NMIS9.x and opEvents 4.x on a single-server. Additional Solution Guides are available for multitiered deployments using opHA.
Install/Update opEvents
Add opEvents License Key
Accept EULA
System Resources and Install
Determine Starting Hardware Specifications
A minimum install of opEvents 4 requires NMIS 9 as the base and requires 4vCPU and 8GB-RAM as a starting point. However, system resource requirements will depend highly on the number of devices, interfaces being collected, additional of syslog processing and number of events / minute. More information can be found HERE: Plan
Test Login Using Default Credentials
After you have completed the install of opEvents you should test the login using the default credentials. Default Credentials (Passwords) for NMIS9 VM
Setup and Configure opEvents (Initial)
Consolidate your Browser Cookies
NMIS9 and opEvents by default use separate browser cookies to maintain your login information. This means that if you log into NMIS, you would need to login again to opEvents. You can, however configure both products to share the same browser cookie.
Configure NMIS9:
- Open /usr/local/nmis9/conf/Config.nmis
- Locate the 'auth_cookie_flavor' setting under 'authentication' and ensure it is set to 'omk'
- Locate the 'auth_web_key' setting under 'authentication', this should be set to a long, random string. Make sure you COPY this as you will need it later.
- Save and close the file.
- If you needed to change either of these settings make sure you restart the nmis9d daemon
Configure opEvents4:
- Open /usr/local/omk/conf/opCommon.json
- Locate the "omkd_secrets" setting, change this to match the setting you copied from 'auth_web_key' earlier.
- Save and close the file.
- If you changed this setting make sure to restart the omkd daemon
Adjust Node Summary Field List
NMIS9 shares a limited number of device fields with opEvents by default. These are defined in the 'node_summary_field_list' in the NMIS9 configuration file. You should review this setting in /usr/local/nmis9/conf/Config.nmis as you may want to append this list to include additional fields you may want to make available to opEvents for event handling or decision making.
Adjust NMIS to use JSON events
If you have opCharts installed with NMIS9 and opEvents4 you should configure opCharts for automated dependency mapping, AND configure opEvents to process events from a JSON stream. The following links detail how to configure each option.
Add/Edit Correlation Rules
Add/Edit Event Actions
Monitor opEvents for Proper Event Handling
Setup Summary Reports