* Applicable for Administration Gui 1.6 and newer.

Complete the following steps to add a new node for monitoring.

Before you start

It is recommended that you have the latest versions of NMIS and opCharts installed before you start. This ensures you have access to the latest revision of the Administration GUI.

There are 3 different ways to add nodes for monitoring. The first two can be done directly via the Administration GUI. The 3rd option requires using Open-AudIT to perform a discovery and integration.

Option 1: Add a single device

1. Open the Administration GUI using the Manage Nodes option for the FirstWave Applications splash page.

   Open

   

   1. Enter your username and password if prompted.

2. You should now be in the Home/Nodes screen. If this is a new installation, there will be only one node called localhost. Click on the + symbol to add a new node.

   Open

   

3. When adding a new node, there some minimum required fields that need to be completed:

   Open

   

   1. General Tab - the required fields on this tab are:

      1. Name - this is the name you want displayed for the node in NMIS/opCharts. Typically you would use the device hostname for this but you can add any unique name you like.

      2. Host Name/IP Address - this is the management IP address or FQDN of the device. NMIS will use this address/FQDN to connect to the device for the collection of metrics.

   2. SNMP or WMI - these are the current supported methods that NMIS will use to connect to a device and collect metrics.

      1. SNMP - SNMP v1, v2 and v3 are supported.

         • for SNMP v1 and v2, simply select the version and add the community string.

         • for SNMP v3, when you select this option and new tab called SNMPv3 will appear. Use this tab to add the SNMP v3 details.

      2. WMI

4. Save changes to complete the node addition. Once saved the device will be added to the polling cycle queue and metrics will start to be collected. Check the status of the device in opCharts to confirm collection is working or if there are any collection errors. Fields to check are:

   1. Status:

      1. reachable - NMIS can see the node and is not detecting any issues.

      2. degraded - NMIS can ping the node but has detected an issue. Common reasons for why a node becomes degraded is a threshold has exceeded or SNMP failure.

      3. unreachable - NMIS cannot ping the node. Double check the IP address of the node is pingable from the NMIS server.

   2. SNMP - if SNMP is configured correctly, the status of this field should be up.

   3. nodeVendor - this should reflect the node vendor. For example, Cisco Systems, Palo Alto Networks, etc. This may say net-snmp if it is a server or NMIS is using a default model.

   4. nodeModel - this is the ruleset NMIS is using to collect metrics from a node. These are called Models. The Model will typically reflect the vendor name and any OS specific information. For example CiscoNXOS for node using the Cisco NXOS operating system.

   5. sysDescr - this is the character string the describes the systems hardware, software and networking. This SNMP specific and NMIS uses this to determine the model to associate with node.

      Open

      

Option 2: Bulk import using CSV

If you have a large number of nodes to add into opAdmin, rather than adding them one at a time, there is the option to import them using a CSV file. Click on the following symbol to launch the bulk import wizard:

Open

1. Click the Download Template option to download a CSV template for your bulk import. Information on additional fields you require that are not present in the template can be found here: CSV template fields

2. Add node data to the template and save as CSV.

3. Upload the file via the wizard.