Skip to end of banner
Go to start of banner

opEvents - Solution Guide - System Configuration for a Production Environment

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

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


Adjust Node Summary Field List

Adjust NMIS to use JSON events

Add/Edit Escalations

Add/Edit Correlation Rules

Add/Edit Event Actions

Monitor opEvents for Proper Event Handling

Setup Summary Reports




  • No labels