Documentation/Monitorig/NAGIOS

From ISP admin

Jump to: navigation, search

Contents

NAGIOS


Optimal and reliable performance of servers does not end by their installation and configuration. The server and other network features operation must be constantly monitore and their performance must be optimized. For this reason, the monitoring and visualising system Nagios has been integrated int the ISP admin system. This integrated system will automatically monitor individual network devices (routers, servers, UPS…). NAGOIS also watches services which run on these devices. Thanks to this system it is possible to very promptly respond to potential problems of the network, or requirements on changing the settings.

For standard usage of the integrated NAGIOS monitoring system it is not necessary to set anything, everything is prepared and configured right in the installation. In case you might find more interest in NAGIOS, you can use oficial documentation on the web of the project. After your interference into NAGIOS configuration file, however, we cannot guarantee the right running of monitoring such as in the default settings.


Setting the routers and devices

While setting the routers and devices into the system, you will have the possibility to assign them to superior devices for NAGIOS; with this setting the routers or devices allocate to a correct place in the topological maps and thus also in NAGIOS configuration.

It is, however, necessary to know that NAGIOS cannot create a topology of the network into a circle, this causes circulation. That is why you are advised to avoid assigning routers and devices. If it should happen that the devices are already assigned to a circle, edit the settings of the wrongly set routers so that they are not in circle, and then run this command:

nagios3 /usr/local/nagios/etc/nagios.cfg

Failure notification

The ISP admin allows to notify failures of the server, routers and to these connected devices such as UPS and this done by two means. You can utilise notification in the form of an e-mail, or a text message. E-mail notification is easy to set up, and message sending is without any extra costs. However, text message notification launching is a bit more complicated and also more costly. A great advantage is the fact that in case of a failure of connectivity into the Internet, you still have device check ensured by means of an independent GSM network. SMS gateway may be utilised for summoning the customers.

To the administrator server it is possible to connect to hardware SMS gateway through which the failure notifications may be send out. In the system setting it is thus possible to set a so called Notification SMS group and to assign it to any server, router, or device. After this, every failure notification is sent right through the SMS gateway. Thus an immediate delivery of the notification to the addressee is ensured even in case of connectivity failure. More information about the option of sending text messages right from the ISP admin system tobe found in the article on SMS gateway configuration.

Settings:

1) You can define your own notification group in the menu of Settings / Codebooks / Nagios, where you create individual groups which will be receiving failure notifications. For example, the first group might be called "Main administrators" and will be take care of the servers (MAIL, DNS, ISP admin ), spine routers, or VIP customers. The other group "Technicians" may take care of the remaining routers and of access points. The solution might be also this when you create several notification groups according to the catchment area and failure notifications will be only sent to those technicians who are listed as contacts in this catchment group (eg. according to the towns and cities, or localities so that the arrival time was minimized).

2) Then, into the created groups, fill in required e-mail contacts if it should be e-mail notification, or telephone numbers in case of notifications by means of text messages. Simply click on the text E-mail contacts, or Telephone numbers and enter the required contacts.

3) After adding groups defined by you, edit the appropriate routers for which you wish to enable failure notifications, and add these groups into the settings of "Report failures". All network devices connected to this router will be automatically included; in case you wish them to be excluded, you must do this at every single one of them separately. You can set out the supervision over the whole network among the individual network administrators, or the technicians.


NAGIOS announces an error: Error: Could not read host and service status information!

Whoops!

*Error: Could not read host and service status information!*

The most common cause of this error message (especially for new users), is the fact that Nagios is not actually running. If Nagios is indeed not running, this is a normal error message. It simply indicates that the CGIs could not obtain the current status of hosts and services that are being monitored. If you've just installed things, make sure you read the documentation on starting Nagios.


In this case, the only thing is to run a following command in a command line:

nagios3 /usr/local/nagios/etc/nagios.cfg
NAGIOS announces an error: Error: Not Found

Not Found

The requested URL /9623961223711250062466/ was not found on this server.


Apache/2.2.3 (Debian) PHP/5.2.0-8+etch16 mod_ssl/2.2.3 OpenSSL/0.9.8c Server at 95.80.203.50 Port 443


For solving, it is necessary to report the problem to the tech support which will arrange a correction. Report failures