How to install SSL Certificate for Nectus GUI


This guide explains how to generate the CSR code and install a commercial SSL certificate for Windows Apache so that you could access your Nectus GUI page securely via HTTPS.

It assumes that during Nectus installation, you selected the default location which is C:\Program Files\Nectus.

If you installed Nectus in a different folder, make sure to adjust the commands and locations given in this guide accordingly.

In general, in order to have a website accessible using secure HTTPS connection, the web server must have a pair of public and private keys configured.

The public key must be signed by a trusted Certificate Authority and added to a digital SSL certificate.

To obtain that certificate, you will need to send the certificate signing request (CSR) code to your SSL provider. Please refer to instructions below:

Generating CSR using OpenSSL

  1. On your Windows server, press Win+R, enter cmd and hit OK


2. Enter the following command to run OpenSSL: “C:\Program Files\Nectus\Web\Apache24\bin\openssl.exe”



3. The prompt will change to OpenSSL>. This means we can run the OpenSSL commands now.

To generate a new CSR/Key pair for your future SSL certificate, execute the following this command:


req -new -newkey rsa:2048 -nodes -keyout “C:\Program Files\Nectus\Web\Apache24\conf\yourdomain.key” -out “C:\Program Files\Nectus\Web\Apache24\conf\yourdomain.csr” -config “C:\Program Files\Nectus\Web\Apache24\conf\openssl.cnf”


4. You will be prompted to enter certain information related to your domain.

The commentaries for each field are provided after the // sign.

Country Name (2 letter code) [AU]:US // enter the ISO 3166-2 compliant country code here

State or Province Name (full name) [Some-State]:California // the field for the state

Locality Name (eg, city) []:Los Angeles // the field for the city

Organization Name (eg, company) [Internet Widgits Pty Ltd]:NA // the name of your company. If you do not have a company or do not wish to indicate it, simply put NA

Organizational Unit Name (eg, section) []:NA // a department of your company. NA can be used here

Common Name (e.g. server FQDN or YOUR name) [] // this is the field for your domain

Email Address []:. // this field is not required generally so you can leave it blank

Please enter the following ‘extra’ attributes

to be sent with your certificate request

A challenge password []:. // can be left blank

An optional company name []:. // can be left blank


5. Once done, the C:\Program Files\Nectus\Web\Apache24\conf\ directory will have two new files, the file with the CSR code (.csr) and the file with the private key (.key).

We’ll leave the private key for the time being. The CSR code has to be provided to your certificate vendor — this code is the base for your commercial SSL certificate.

Please contact your SSL vendor for instructions with SSL activation.

6. When the SSL is issued, you should receive at least two files: SSL certificate in a .crt (or .pem, .cer) file, and the CA-bundle (also can be called intermediate CA, root CA certificates) with extensions like .ca-bundle, .crt.

Please note that Apache requires only PEM-encoded certificates, so PKCS#7 or PKCS#12 encoded SSLs won’t work.

Configuring SSL for Apache

7. Upload those files to the C:\Program Files\Nectus\Web\Apache24\conf\ directory.

8. Then, go to the C:\Program Files\Nectus\Web\Apache24\conf\extra folder, and open the httpd-ssl.conf file in Notepad.

9. Find and edit the following directives and make sure that they point to the SSL certificate, Private Key, and the CA-bundle files accordingly:


SSLCertificateFile “${SRVROOT}/conf/yourdomain.crt”

SSLCertificateKeyFile “${SRVROOT}/conf/yourdomain.key”

SSLCACertificateFile “${SRVROOT}/conf/”


Note that the SSLCACertificateFile directive is commented out by default. You need to delete the # sign at the beginning of the string to uncomment the directive.

10. Save the configuration file

11. Return back to the C:\Program Files\Nectus\Web\Apache24\bin folder and double-click on ApacheMonitor.exe


12. The ApacheMonitor app will appear in the system tray at the lower right corner of your screen. Find and click it there.

13. Hit “Restart”


14. Now you can try accessing your Nectus GUI page in the browser via HTTPS:

Configuring Linux Monitoring in Nectus


Configuring Linux Monitoring in Nectus

Nectus Server 1.55 adds feature to monitor some system parameters on hosts running Linux. Enabling this feature for your infrastructure requires two steps:

  • Configuring of Nectus Server;
  • Installing and configuring of Nectus remote agents on target Linux machines.

This guide describes steps for Nectus Server configs. Installing and configuring of Linux remote agents are described here.

Linux monitoring integration

Choose the following menu item from the Nectus GUI to set global Linux monitoring parameters.

This will open the next window:

  • Agent mode determines whether the agent runs in passive mode (when it waits for an incoming connection from the server and then collects the required metrics) or in active mode when the agent connects to the server pro-actively and sends the collected data.
  • Server TCP port sets the server port number for incoming connections from the agents running in active mode. If you set Agent mode to passive then this value is not used.
  • Pre-shared Key determines the secret key used to encrypt and decrypt messages between Nectus Server and the monitoring agents. You can set string of any length but recommended length is from 8 to 16 characters. The exactly same key should be set in all agents’ configuration files (parameter SERVER_PRESHARED_KEY, see details here).

Click OK to save configured parameters.



Select “Linux Monitoring Settings” from the “Monitoring” menu to configure your monitoring profiles for Linux machines.

Click “Create” to create a new monitoring profile:

In the following form enter the name of your profile and choose metrics you would like to monitor:


Configure the necessary metric parameters like minimal and maximal thresholds, alerting etc.

You can create any number of profiles and assign each of them to different group of Linux machines.

Linux Servers


Select “Linux Servers” from the “Inventory” menu to configure groups and servers to be monitored.

Click “Create new Group” in the next form:


Enter “Group Name” for the new group, select “Enable monitoring” and choose the desired Monitoring Profile for this server group:

Also select the appropriate alert recipients in this form.

You can create any number of monitoring groups if you need to apply different profiles or alert recipients for different server groups.

When you have finished with the groups switch to the next tab “Servers” in the same form and click “Add Server” to add a Linux server to be monitored:

In the next window enter the Hostname (optional, it will be obtained later during the monitoring process), IP address, TCP port of the remote agent’s listening socket (default 5400) and choose the appropriate Group:

You can choose different values of TCP port for different servers according to your network configuration. But note that this value must match the parameter AGENT_PORT set in the agent’s configuration file (see details here).

After clicking “OK” you will see the server in the following list and you will be able to View, Edit and Delete the server (operations are marked with a red square).

After you have added all the desired servers and installed the remote agents the process of monitoring of your Linux hosts will start automatically.


Device View Auto Population Rules

, ,

Device View Auto Population Rules

Device View is the logical grouping of the devices that can be used in different places within the Nectus application. In the previous versions of Nectus, the user would manually add devices into device views which may become a significant management overhead.

In Nectus version 1.55 we introduced an ability to automatically populate device views based on specific conditions such as device names, types, etc.

User can define a set of conditions which has to be true for Nectus to automatically add devices to device views.

This article will guide you through the process of defining the auto population rules for device views.

To access your SNMP Device Views go to Inventory Views SNMP Device View



To add a new Device View, click Create in the upper right hand corner of the SNMP Devices Views page.


Give a name to your new Device View.



Press Save button to finish creation of Device view.


Open again newly created device view and in the upper right-hand corner, select Edit Rules.

This will open the Devices View Auto Population Rules page.


Select the plus sign to add a new Auto Population Rule.


Add all the required Auto-population rules and press Ok button to Save.

If multiple rules are defined all the rules must be TRUE for device to be automatically added. (Logical AND).

Your rules will be processed daily at 3:00 PM.

If you would like to apply your rules immediately, press the Apply Rules button.


Monitoring BGP Sessions with Nectus


Monitoring BGP Sessions with Nectus

Nectus 1.2.53 introduces ability to automatically discover and monitor iBGP and eBGP sessions across all router types and manufacturers.

Nectus scheduled network discovery automatically finds all the BGP sessions via SNMP polls and adds it to Nectus database where user can group them by type and enable active monitoring and alerting.

BGP Session Discovery

As part of regular scheduled network discovery Nectus detects all existing BGP Sessions and adds it to one of the existing BGP group which has “Default” flag set to ON.

You can see all the BGP sessions that were discovered in Inventory -> BGP Sessions or in left side panel called “BGP Sessions


If you right-click on BGP Session and select “Properties


.. you can assign a human friendly name or change a group membership for any of the BGP sessions.


You can create multiple BGP session groups and assign discovered BGP sessions to different groups according to its type or functional purpose.

To create a new Group, right-click on “BGP Sessions” line and select “Add New Group” on context menu.


Configure New Group name, set “Enable monitoring” to ON if you want all BGP Sessions in this group to be monitored for UP/DOWN Status.


If you set “Default” value to ON, this group will become a group where all newly discovered BGP sessions be added automatically. Only one group can have “Default” value set to ON

You can also assign BGP Session to a Group by right-clicking on BGP session and selecting “Move BGP Session to..” option



By clicking “View Session Info” on BGP Session context menu you can view detailed information about BGP Session



After you finished creating BGP session groups, assigning BGP sessions to corresponding groups and enabling BGP session groups for Monitoring the final step is to enable BGP Sessions monitoring in corresponding SNMP Device Monitoring Profiles that are applied to the routers that terminate all the BGP sessions.

Find required SNMP Monitoring Profile and enable “BGP Session Status” Monitoring Option

Now are you all set to start monitoring your BGP sessions line a pro.


UPS Health Status Monitoring with Nectus


UPS Status Monitoring with Nectus

Health monitoring of UPS units is one of the most critical tasks of network infrastructure monitoring.

If UPS fails during power outage it results in immediate network downtime resulting in loss of revenue and degrading user experience.

Most of the modern UPS Units perform daily self-tests and results of those self-tests are available via SNMP protocol.

Our goal is to collect those self-test results on regular basis and generate an alert or incident when self-test indicates a UPS failure.

Step 1. Determine which SNMP OID to use

Very first step before you can start monitoring UPS health status is to determine which SNMP OID contains self-test information for your UPS units.

You can open a support case with your UPS vendor and request SNNP OID string for self-test information.

For example, SNMP OID for self-test information from UPS manufactured by APC is .

This OID returns following values:

1 = Ok

2 = Failed

3 = Invalid Test

4 = Test In Progress


Step 2. Create Device View that contain all UPS units

Next step is to create a Device View that contain all UPS units that we want to monitor.

To create a Device View go to Inventory -> Views -> SNMP Device Views.


Create a new Device Vice called “UPS Units”



Step 3. Create Custom SNMP Tracker for UPS Self-Test Info

Now we are ready to create a custom SNMP tracker that will be polling our UPS units every 5 min for self-test information.

In Nectus GUI go to Monitoring → SNMP Monitoring Settings → Custom SNMP Trackers


Press “Create” button to bring up Custom SNMP Tracker creation interface.

Complete tracker General information tab with correct SNMP OID and select Device View that contains all UPS units that we want to monitor.


Select Email and SMS list for Alert Recipients.

In “Alerts” Tab we need to specify which status values will be considered Normal and which values should trigger Alerts.

You can specify multiple values separated by comma.


Define an Alert Severity level for Alarm Values as Informational, Warning or Critical.

Define number of consecutive readings for which UPS self-test status must report an Alarm condition before formal Alert is created.

Nectus performs one SNMP poll per 5 min.

If you define value for consecutive readings as 3 it should result in Alert created after 15 minutes of True Alarm conditions.

Press “Save” to complete Custom SNMP tracker creation for UPS Status Monitoring

This completes creation of custom tracker that will be monitoring UPS self-test information on all APC UPS units in your network.


Suppression of Frequent Identical Alerts In Nectus


Suppression of Frequent Identical Alerts In Nectus

Often when a network device or interface changes its state between Up and Down multiple times in a short time interval, numerous identical alerts will be sent to all the configured alert recipients.

Nectus offers the ability to suppress frequent identical alerts to reduce informational noise level by specifying a suppression timer for up to three hours.

Nectus calculates a CRC hash value from each of the email alert bodies and if hash values of two alerts are matching they are considered to be identical and can be suppressed.

Nectus excludes event timer values and specific metric values from hash calculation logic. You can configure the suppression timer from 0 to 180 minutes where 0 means no suppression.

To configure the suppression timer, go to    Monitoring -> Global Monitoring Settings



Under Monitoring Settings, select the Alerts tab.

To enable suppression specify a time interval from 1 to 180 minutes.

At the end of the time interval, alert logic will resume as normal.

Setting timer to 0 will disable the suppression.



Importing WMI Servers from CSV file to Nectus


Importing WMI Servers from CSV file to Nectus

To import a list of Windows Servers from CSV file to Nectus prepare a CSV file with only single column containing list of IP addresses of Windows Servers.

No other information is required.

File format example in Excel.

To start import, right-click on WMI Server Group that you want to import servers into and select “Import  WMI Servers from CSV file” option



Select CSV File that you prepared.



Press “Start” button


Nectus will import each server individually and collect basic Server information via WMI Interface.


Configuring WMI Integration in Nectus


Configuring WMI Integration in Nectus

Nectus uses WMI Interface in several of its modules.

List of modules that depends on WMI Integration:

  1. Windows Server Monitoring Module
  2. IPAM Module

In Windows Server Monitoring module Nectus uses WMI interface to poll Windows Servers for critical health metrics such as CPU and RAM Utilization etc.

In IPAM Module Nectus uses WMI interface to interact with Microsoft DNS and DHCP servers while Importing and creating reservations.

WMI Integration settings must be complete before Nectus can communicate with Windows Servers in those modules.

To complete WMI Integration go to Settings -> General Settings -> WMI Integration

Click on “WMI Integration” link and complete all the required fields for WMI Service account

that will be used by Nectus connect to Windows Servers via WMI Interface.

WMI Service account should not have password expiration policy to prevent Integration from breaking every time password has to be changed.

Use “Test” button to test Service account credential against any of Windows Servers of your choice.

After connection “Test” is passed WMI Integration is complete.


Adjusting min. detectable ICMP outage duration in Nectus


Adjusting Min. detectable ICMP outage duration in Nectus

When Nectus is configured to monitor UP/DOWN Status for network devices with ICMP it sends Echo packets at preset interval called Inter-Packet Delay.

By default, this Interval is set to 10 seconds.

Network Device is considered down if Echo-Reply is not received for “N” consecutive Echo packets.

By default “N” is set to 10.

So, by combining Inter-Packet Delay and “N” Value we can see that minimum duration of the outage that can be detected by Nectus with default settings is 100 seconds.

Sometimes when network a prone to fast transient outages or burstable traffic patterns that can impact ICMP it may be beneficial to increase minimum detectable ICMP outage duration to higher value. This can helps to eliminate alerts about short lived outages and only alert on outages that have more lasting impact.

To adjust Inter-Packet Delay or “N” Value go to “Monitoring -> Global Monitoring Settings


And adjust values on “ICMP Monitoring” Tab according to your business needs.


Monitoring HTTP URLs with Nectus NMS


Monitoring HTTP URLs with Nectus NMS

Have you ever been surprised to find out your website hadn’t been running or online?

Realtime status updates of your website can relieve you of the frustration of downtime and provide with instant alerts to your team.

Nectus HTTP Monitoring module can take the burden of URL monitoring away and provide real-time status of thousands of URLs, all using one quick view.

Nectus can poll websites on with preset frequency and alert you via Email or SMS if any of the websites are down.

Creating URL Groups in Nectus

HTTP URL Monitoring starts with creating URL Groups.

To create a URL group, right click on the Web Servers group on the left side panel. When the context menu appears, click on Add New Group.

After clicking Add New Group, a pop-up window appears.

Window allows you to set a Poll Frequency, which defined how often Nectus will poll your website.

Enable Monitoring can be checked to begin monitoring for all URLs that are members of this group.

Send Alerts to Email Group and Send Alerts to SMS Group can be checked to specify URL Down Alert recepients for Email or SMS notifications.

To modify members’ list of any of the existing E-mail or SMS groups click on the group name.

Once you click on the Alert group name a popup window appears where changes can be made to the existing alert groups.

Adding URLs to Groups in Nectus

After creating URL groups, you now may add URLs that you want to monitor to the group you have just created.

Right Click on any of the group name and select: Add New URL

After clicking Add New URL, you can add the URL and give the URL a specific name. You may also specify which group the URL goes into.

Once you have added the URL, monitoring start automatically.

Repeat this process for every URL you’d like to enable for monitoring.

After you have finished adding all of your URLs you will be able to quickly see the status of all the URLs in the left side panel.


Multiple Alert Email Aggregation in Nectus


Multiple Alert Email Aggregation in Nectus

Very often during site level power or network outages or during network maintenance multiple devices become offline at the same time causing multiple individual DOWN Email alerts to be sent at the same time.

Depending in the size of the site it can be well over hundreds or even thousands alert emails to be sent out to corresponding e-mail recipients configured for given site.

Starting from version 1.2.52 Nectus offers an option to aggregate multiple DOWN or UP email alerts into a single multi-device alert notification containing a list of all devices that became DOWN or UP within last monitoring interval.

To enable Alert Aggregation, go to Monitoring -> Global Monitoring Settings: “Alert” Tab

And Select “Aggregate multiple UP/DOWN Alerts” Option.


Monitoring Cisco Power Supplies with SNMP


Monitoring Cisco Power Supplies with SNMP

Cisco Power Supply

Cisco Power Supply

Step 1. Determine which SNMP OID to use

Very first step before you can start monitoring power supply status is to determine which SNMP OID is supported by specific router or switch type you want to monitor.

The main challenge here is that there is no consensus among manufacturers on specific SNMP OID and even within Cisco products OID can be different on different product lines.

Let’s take Cisco Catalyst 3750 series switches as an example.

For all Cisco 3700 series switches SNMP OID that contain power supply status is . (ciscoEnvMonSupplyState) from CISCO-ENVMON-MIB

Cisco TAC is usually a good resource to confirm which OID can be used for different Cisco product lines.


Step 2. Obtain Power Supply Index Values

Next step is to perform SNMP GET BULK or SNMP Walk query for selected OID (. against one of the switches that you planning to monitor to determine how many power supplies this specific switch model has and what are the index values for each power supply.

Sample GET Bulk Response from Cisco Catalyst 3750:

‘[1034]’ => “1”

‘[2034]’ => “1”

In this SNMP GET-BULK response we see that switch has two power supplies with indexes: 1034 and 2034.


Step 3. Obtain list of Status Values for SNMP OID

Last step before we can start monitoring power supply is to consult MIB for possible values that this specific OID can report for power supply status.

For SNMP OID there are 6 possible status codes:

Normal (1), Warning (2), Critical (3), Shutdown (4), Not Present (5), Not Functioning (6)


Step 4. Create Custom SNMP Tracker for Each Power Supply

Now we are ready to create custom SNMP trackers for each of the power supplies.

In Nectus GUI go to Monitoring → SNMP Monitoring Settings → Custom SNMP Trackers

Press “Create” button to bring up Custom SNMP Tracer creation interface.

We will have to create two separate trackers, one for each power supply.

Complete tracker “General” settings Tab according to this

Note that for this tracker we created a device view called “Cisco Catalyst 3700 Switches” that contain all Cisco Catalyst 3700 Series switches that we want to monitor with this tracker.

If you want to enable Power supply monitoring for more switches later, you just need to add new switches to this Device View.

Select which email lists will be used as email Alert recipients.

In “Alerts” Tab we need to specify which status values will be considered Normal and which values should trigger Alerts. You can specify multiple values separated by comma.

Define an Alert Severity level for Alarm Values as Informational, Warning or Critical.

Define number of consecutive readings for which power supply status has to report an Alarm condition before formal Alert is created. Nectus performs one SNMP poll per 5 min.

So if you define value for consecutive readings as 3 it should result in Alert created after 15 minutes of True Alarm conditions.

Press “Save” to complete Custom SNMP tracker creation for Power Supply 1.

Repeat the same process for Power Supply 2.

Now you have created custom trackers that will be monitoring both power supplies on all Cisco Catalyst 3700 Switches in your network.


Using Subnet Profiles in Nectus IPAM


Using Subnet Profiles in Nectus IPAM

One of the unique features offered by Nectus is the ability to logically split each subnet into predefined ranges reserved for specific categories such as users, servers, infrastructure devices, etc. This is done with the help of subnet profiles. In Nectus, subnet profile is a set of IP ranges with a unique color code and a distinct name. Color coding makes it easier to locate an IP range reserved for a specific device type. This article explains how to create subnet profiles in Nectus.

  1. Creating a Subnet Profile

To create a new subnet profile, go to Main Menu and select Settings → General Settings → IPAM Integration.

In the “IPAM Integration” window that appears, select Subnet Profile tab and click Add button.

Begin defining a new subnet profile in the “Add Subnet Profile” GUI window that appears. Assign a name to your new profile. Define the first device category. Determine how many IP address you would like to reserve for the first device category and assign an order number for the first (Start) and the last (End) IP address in the group. Chose a color code for the device category.

Use + button to add additional device categories. Press Save to save your new profile.


2. Assigning Profile to a Subnet


To assign a profile to a subnet, right click on the selected subnet and select Properties.

On the “Properties” page that appears, select the desired profile and press Save button.


3. Benefits of Subnet Profiles

Once you have assigned a profile to a subnet, your subnet map will display color-coded IP ranges reserved for the device categories.

This visual guide will help you better manage IP addresses in the subnet.


Importing subnets to IPAM from IGP routing protocols explained.


When importing Subnets into IPAM from routing protocols Nectus apply following rules:

  1. Only subnets from IGRP routing protocols (EIGRP, OSPF, ISIS, RIP) are being considered for import.
  2. Nectus will not import subnets from iBGP  or eBGP.
  3. Nectus start importing subnets in the order from smallest to largest:  /32 ,   /31, then /30, then /29…etc.  This is done to give individual subnets priority over  summaries.
  4. Every imported subnet is validated against overlapping with existing subnets.
  5. Nectus will not import subnets that overlap with any of the existing subnets.
  6. Nectus will only import subnets that fall into defined IPAM address space.

Using Custom Subnet Tags in Nectus IPAM


Using Custom Subnet Tags in Nectus IPAM

One of the unique features of Nectus IPAM is ability to define unlimited number of properties aka “custom tags” and assign it to any of the subnets.

For example: “Building Floor”, “Datacenter” or “Application Name” can be defined for each subnet as a custom Tag.

To create a new custom tag go to Settings → General Setting → IPAM Integration

On “Subnet Tags” tab you will see current list of Tags that already exist in database.

To add a new tag press “+” button next to drop-down menu with all the tags.

Specify Tag name and press “Save” button

After you defined Tag’s name you can start adding specific Tag values for this Tag by pressing on “+ Add” button at the right upper corner of the page.

You can define as many Tag Value as required.

After you finished defining Tag values you can open Properties for any subnet in IPAM and you will see all the defined Tags as a drop-down menus where you can select specific Tag value for given subnet.


Suppressing excessive E-mail alerts during site level network outages


When whole site power outage or network maintenance is in progress it is default behavior for Nectus to send individual DOWN alerts for each device in that site possibly resulting in hundreds of DOWN e-mail alerts followed by the same amount of UP e-mail alerts sent out to all configured alert recipients.

In version 1.2.53 Nectus introduced a feature that allows user to reduce number of alert e-mails during site level network outages to only specifically designated devices called “Gateways”

For each site user can designate some of the devices as “Gateways” and following alert rules will be applied:

  1. If all the Gateways in given site are DOWN, Nectus will not send DOWN alerts for regular devices located in the same site.
  2. If at least one Gateway in given site is still UP then Nectus will send individual DOWN alerts for all of the devices detected as DOWN.
  3. If all the Gateways in given site recovered from DOWN to UP, Nectus will not send UP alerts for regular devices located in the same site.
  4. If at least one Gateway in given site is still DOWN then Nectus will send individual UP alerts for all of the devices detected as UP.

To configure Site Gateways right click on Site and select Properties

Press “Site Gateways” Button

Select devices that you want to be gateways for given site and press Save button


Using Graphs in Custom Dashboards


Using Graphs in Custom Dashboards

Nectus offers extensive capabilities of visualizing different aspects of network performance and presenting it in custom dashboards.

This article guides you through the basic step of process of adding graphs to custom dashboards.

Step 1. Prepare Graphs for the Dashboard.

Generate the graph you’d like to include in a dashboard. Make sure to adjust the required time range using the drop-down menu in the left upper corner.

Click URL button to obtain the URL address for the graph.

In the URL window, click Copy and save the URL address into Notepad.

If creating a dashboard with multiple different graphs, repeat building graphs and save URLs for every graph that will be included in dashboard.

Step 2. Create Custom Dashboard.

Once you have built the graphs and saved all the URLs, you are now ready to create a custom dashboard.

Go to Monitor → Custom Dashboards → Manage Custom Dashboards.

Click Add Dashboard button.

In the “Dashboard Widgets” menu select “Custom Graphs” Tab, select the number of graphs you’d like to display in Dashboard by checking the boxes on the left, and paste the URL addresses that you previously saved.

Give Dashboard a Name and press “Ok”

Your new dashboard is now listed in the Custom Dashboards list. Click on the name to open it.

If desired, use paper clip icon in the right upper corner to make this dashboard appear every time you login.


Using Custom SNMP Trackers in Nectus


Using Custom SNMP Trackers in Nectus

Nectus offers extensive SNMP based network monitoring capabilities that allow users to track any metrics accessible via SNMP.

In addition to standard metrics, such as CPU, RAM or TCAM utilization, Nectus offers a new feature called “Custom SNMP Tracker” that allows you to monitor virtually any metrics accessible via SNMP.

This article will guide you through the basic steps required for setting up custom SNMP trackers in Nectus.

In the Main Menu, go to Monitoring → SNMP Monitoring Settings → Custom SNMP Trackers.

This opens a “Custom SNMP Trackers” window. To create a new custom SNMP Tracker, click the Add Tracker button.

In the “Add New Custom SNMP Tracker” interface box that appears, specify the following parameters:

  1. Tracker name (Example: “Power Supply Temperature Sensor”)
  2. SNMP OID to be used with “SNMP GET” request for Data
  3. Unit Name (Example: C for Temperature)
  4. Data Type (Integer or Floating)
  5. The Device View that contains list of devices to be used for collecting data from
  6. Select “Log to DB” if you would like to save metrics values to a database every 5 minutes
  7. Select “Email Alerts” if you would like to be alerted when metrics exceeds pre-defined thresholds
  8. Min and Max Threshold Values
  9. Select the number of “Consecutive Readings” exceeding threshold that would trigger an alert
  10. Select one of the existing email lists/groups to receive the alerts (Example: “Network Admins”).
  11. Click Edit Alert Templates to fully customize the alert email for the metric

Customize the E-mail template for Alert and for Recovery event when Metric value returns to normal range.

You have now created your first custom SNMP tracker. To create additional trackers, use “Clone” feature to create and edit a copy of an existing tracker available from the “Custom SNMP Trackers” page.