Building an efficient, understandable and convenient monitoring environment requires planning and making choices. The following list of steps and points for attention is a guideline and helps you to make the right decisions.

1. Define your goals

What are your must-haves and nice-to-haves?

  • What is the most important equipment in your network?
  • Where are the black spots or problem points in your network?
  • What do you want to monitor? Everything with a connector or a specific group of devices, subnets or IP ranges?
  • Who will receive alarms?
  • Who will have access to your monitoring environment?

2. Prepare your equipment.

SNMP support is of eminent importance when it comes to maximum visibility and control.

  • Enable SNMP support on as much equipment as possible.
  • Avoid using the standard community names “public” and “private”. Define your own community names and configure your equipment accordingly.
  • Use the inefficient SNMPv1 as little as possible. Use the much more efficient SNMPv2 by default.
  • Do not use SNMPv1 or v2 over the internet! Use SNMPv3 with encryption instead!
  • Allow the use of SNMP through your firewall to monitor your DMZ subnets.
  • Set your Quantellium server as the Trap and Syslog receiver in your main equipment.

3. Define a logical map structure.

Quantellium supports a layered map structure. A well-defined layered map topology contributes to a clearer view of the infrastructure, a better understanding of the availability status of your devices and helps to understand the consequences of a critical error more quickly.

  • What is your root map (the top level map)?
  • Keep your maps orderly. If possible, add no more than 100 device objects to a map. Take this into account when designing the map layout.
  • Define equipment clusters and add them to separate maps. For example, if you add the servers in the data center to a separate map, also add the switch (es), to which they are connected, to that same map!
  • Define a naming convention for your maps. Use meaningful names and descriptions.
  • Use MapLinks to link maps together. A MapLink is a reference to another (child) map.

4. Add device objects to your maps.

The Quantellium “IP scan” program allows you to scan an IP range for devices. Each found device is assigned to a Quantellium class and automatically added to the map.

  • Define your scan profiles. Scan profiles contain information about IP ports, SNMP versions, community names, and encryption keys for SNMPv3.
  • Keep your (IP) scan ranges small. Scanning can take a long time.
  • Perform a scan for each defined map. After the first scan run, maps remain up-to-date by periodically re-executing the scans themselves.

Using the IP scan tool is the recommended way to add devices to your maps.

5. Fine-tune your project settings.

Set up or modify Trap and Syslog filters and define alert groups.

  • Without filters you will probably receive a lot of trap and syslog messages initially. Create blocking filters for irrelevant messages or for events of which you already know the cause.
  • The system-wide default setting for the minimal severity level of syslog messages is “critical”. If you receive many “critical” messages from many different devices, consider changing this setting, but be careful with this.

6. Maintenance

Make maintaining your Quantellium monitoring environment a standard part of your change management procedures. Quantellium project maintenance must include at least:

  • Adding or removing new or outdated equipment.
  • Adding, deleting or modifying event blocking filters

The PDCA cycle is a model for continuous improvement. It consists of four iterative steps: Plan, Do, Check, and Act (PDCA). Repeated over and over again, these four steps enable continuous improvement.