This page allows you to configure hosts. From Opsview 3.1 onwards, you need to have the CONFIGUREHOSTS access level in your role to be able to configure hosts.

This is the primary hostname, or IP, for this host.

Bear in mind that a host does not have to be an actual host, so this field does not have to be an actual hostname or IP.

Changes to this field will update the Monitored by field.

This is the name of the host as known by Nagios. This needs to be unique across the entire monitoring system. Note that reports and performance graphs will use the name to find historical information, so if you change the name of a host these will be lost.

The name is constrained to 63 characters.

This is for a list of other hostname or IPs that this host corresponds to. Enter a comma to separate the addresses. You can use spaces to enhance readability.

When you configure your servicecheck, you can access these addresses using the macros $ADDRESSES$, (which returns the entire list including commas, with spaces stripped), $ADDRESS1$ (for the 1st address), $ADDRESS2$ (for 2nd address), etc.

If other addresses are not defined, but the $ADDRESSx$ macros are used, $ADDRESSx$ will default to the primary IP address of the host. $ADDRESSES$ is left undefined.

This field only appears if you have more than one monitoring server. Select which monitoring server you want this host associated with. This monitoring server will then monitor all services for this host.

From Opsview 3.1, this list will restrict the items based on your role's access levels for CONFIGUREHOSTS.

This field will also be updated based on the Hostname or IP of the server because Opsview will try and pick the monitoring server which has a name or address most similar to the host.

Select the parents of this host. This will set the parent child relationship within Nagios so that host outages can be calculated better.

There are various filters that can be selected to reduce the number of hosts visible in the source list on the right.

This list will only show host groups which are leaves at the bottom of the host group hierarchy. From Opsview 3.1 onwards, the list will be restricted based on your role's access level for CONFIGUREHOSTS.

If you have admin access, then a New Hostgroup text field will appear if you want to create a new hostgroup.

Assign keywords to this host. Only service checks with the same keyword that is also on this host will be associated with this keyword.

You can use a comma separated list of keywords. Keywords are alphanumeric.

Note: You cannot currently assign keywords to embedded service checks, so it is not possible to tag those services.

Choose which states this host should notify on. The host is considered flapping if it changes states more than 7 times in the last 20 checks.

For SNMP v1 or v2c, you only need to enter the community string.

For SNMP v3, you have to enter the password, the authentication protocol and the authentication password. If you do not enter a privacy password, no privacy will be set.

To test the authentication information, you can press Query Host which will attempt to communicate with the host and retrieve a list of interfaces.

You can also run Snmpwalk, which will list all the SNMP OID values available for this particular host.

Note: the Snmpwalk option is not available when you create or clone a host - it is only available on edit screens. Also, the credentials used to run snmpwalk are the saved credentials, not the values you can see on the form.

If you use an SNMP polling service check, AES128 may not be a supported Privacy Protocol because the underlying Net-SNMP software may not support AES128.

If you have any shell characters for the SNMP v3 parameters, these may not get passed to the SNMP polling service check correctly. This is a limitation in the check_snmp plugin.

This field only appears when the SNMP field toggle is pressed and a Query host is run. Extra fields will appear which can be used to monitor specific links on the device.

The information within the brackets will not be saved, though when you press Query host, it will find the latest information.

Select the interfaces you want monitored.

The Warning and Critical thresholds may be specified in either bits per second or as a percentage (signified by including the % character).

If you want to change the servicecheck options for SNMP interfaces, goto Advanced → SNMP Interface Polling

Normally, interfaces are monitored by name, so if the SNMP index position changes (which could happen on a router reboot), then a rescan of the device will occur to check.

If there are multiple interfaces with the same name, the ifIndex will also be passed to the plugin to check. If the ifName does not match the expect interface name for this ifIndex, an alert will be raised which says:

WARNING - Interface name $user_specified_ifname expected at index $user_specified_index, but got $name!

You will need to run Query host to list the interfaces to check again.

Note: if the index moves to a position with the same interface name, then Opsview will not see a change and continue monitoring this interface as usual even though it could be a different interface.

If you have a Cisco router, please check this Cisco support article regarding ifIndex persistence.

If this option is specified, then NMIS will be setup to poll this host to get interface statistics.

Note: NMIS only works with SNMP v1/2c at the moment.

If Use NMIS for Interfaces is selected, then you will need to tell NMIS what type of host this is. This allows it to select an appropriate profile to determine the characteristics of the host.