Return To Help Topics List

Adding and Editing Tests

nandView revolves around the tests. A test is a network service on a particular device that is either working (up, clear) or not working (down, critical). While you can modify the code to support whatever tests you wish, nandView supports four major types out the box: ICMP ping, TCP, UDP and Protocol verification. We'll first explain the supported tests, and then go into creating and deleting them.

Types of Tests
A nandView test contains three parts: the device (and its IP address), a 'type' and a 'test'. The type specifies what kind of test it is, such as a TCP or UDP connection. The 'test' field specifies what to do with the type, such as connect on port 25 or 3306. For example, to check if a web server is running, which runs on TCP port 80, you'd set type to 'TCP' and test to '80'.

ICMP - The ping test is very basic. If the device responds to a ping, it passes. Most device should contain a ping test. Please note that some firewalls will block pings altogether but allow other services to pass. There are three valid entries for the 'test' field with an ICMP test: ping, pingfirst, pinglast. 'ping' is a straight forward ping. The 'pingfirst' and 'pinglast' tests are a bit unique in that they can affect the rest of the tests for a particular device. If you specify 'pingfirst', then the ping test will run before any other tests for that particular device. If the ping test passes, the other tests are run. If the ping fails, the other tests do not run, and will show the skipped test symbol. The 'pinglast' test does the opposite. If at least one of the other tests passes for that device, the pinglast test will not run. If all other tests fail, then it will run.

TCP - This will check if a TCP port is accepting connections. Specify the port in the 'test' field.

UDP - This will check if a UDP port is accepting and returning information upon connection. Unlike TCP, the UDP protocol is classified as 'connectionless'. This means a client can send data to the server, and doesn't have any guarantees the data got there. nandView tries to get around this by sending a very small data packet to the specified port, and listening to see if the server issued a reply. There is a possibility that your UDP services won't behave in this manner. If you find a particular UDP test never passes, and know the service is working, please inform nandView and we'll see if we can add some workarounds into future versions.

Protocol - The protocol check is an advanced feature of nandView. It goes beyond checking if a connection is accepted, and actually issues commands for certain information transfer protocols. Instead of merely seeing if your email server is accepting connections on port 25, nandView will also make an SMTP HELO request, and look at the output. Protocol tests take in an optional second argument, seperated by a colon, to specify additional information. For example, a protocol test of 'http' will check a web server running on port 80. If you wrote 'http:8080', it'll check on port 8080 instead.

ExamplesWhat is sent to the serverWhat is expected in reply
httpport number80http
GET / HTTP/1.1
Host: ip_address:port
Connection: close
HTTP/1.1 200 OK
ftpport number21ftp
smtpport number25smtp
dnsdomain to lookupwww.google.comdns
DNS lookupDNS reply

Add/Edit Devices and Tests
Administrator can add devices, add tests or edit tests from the dashboard. There is an add device and add test link at the bottom of the page, and each row in the test status grid has an edit button. Functionally, they all work the same. The 'add test' screen is slightly different in that it can be used to automatically select the device name and IP address from a list of already entered devices/IPs. Please note that although the dashboard will group together all the tests for a device, to rename a device you need to edit each test individually.

Device - The device name.
IP Address - The IP address the test should connect to. Note that nandView supports devices having multiple IP addresses.
Type - Select the type of test (see above).
Test - Specify the test, such as a port number (see above).
Email - Choose which email list to send critical/clear notifications. The first choice is always (no email), which doesn't send any notifications.
Run group - nandView supports up to four run groups for additional scalability and flexibility. If you don't want or need to use run groups, choose group 1. The poller program runs all the tests in either group 1, 2, 3 or 4. You can choose to run these groups on different schedules (such as group 1 polling every five minutes, group 2 every thirty minutes) or with different timeout periods.
Notes - Any further description or documentation on this device/test.

Click the button at the bottom to submit the information.

Deleting A Test
To delete a test, click the 'edit' link from the test status grid. Now click on the 'Delete This Test' button. You will be asked to confirm the deletion. Test deletion is permanent and irreversible.

Return To Help Topics List