Unterschiede

Hier werden die Unterschiede zwischen zwei Versionen angezeigt.

--- nagios [2015/04/01 11:12] – [Ping] michael-neesen
+++ nagios [2024/06/09 10:29] (aktuell) – Externe Bearbeitung 127.0.0.1
@@ Zeile 1: / Zeile 1: @@
-====== NagiosCore Network Monitoring für Alcatel-Lucent Enterprise OmniSwitche ======
+====== NagiosCore Network Monitoring for Alcatel-Lucent Enterprise OmniSwitches ======
 Nagios Core can be used to monitor network devices and servers. Through SNMP and Nagios extensions, detailed information about network status and device status can be obtained. In this article, the implementation of monitoring using Nagios Core will be described based on Alcatel-Lucent Enterprise equipment.
-In this case, Nagios Core is installed on an CentOS 7 server with Nagios Core 4.0.7.
+In this case, Nagios Core is installed on an CentOS 7 server with Nagios Core 4.0.8.
 The IP address 192.168.10.240 is used.
@@ Zeile 14: / Zeile 14: @@
 In the next step, Nagios Core can be configured.
+===== Host Configuration =====
+<code>
+define host{
+	use		generic-switch
+	host_name	OS6860E-P24		; The name we're giving to this switch
+	alias		Core-Switch		; Another name associated with the switch
+	address		192.168.20.254		; IP address of the switch
+	hostgroups	Infrastructure		; Host groups this switch is associated with
+	}
+</code>
+In the first step the host has to be defined. A host can be every switch or chassis, which is reachable via an IP-Address. The host has a defined host_name and optionally an alias.
 A configuration file for each switch will be implemented. The defined services are
@@ Zeile 20: / Zeile 32: @@
   * Port Status
+{{:nagios.jpg?1261|}}
+Example of Nagios Core network monitoring with OmniSwitch- and OmniAccess-devices.
 ===== Ping =====
@@ Zeile 35: / Zeile 49: @@
 The ping interval is 0.5 seconds.
-==== Uptime ====
+===== Uptime =====
 The system uptime gives a good overview when a network device rebooted last time. Especially over night, that might be unrecognized and is visible with Nagios.
@@ Zeile 48: / Zeile 63: @@
 For this command SNMP is used. The host's IP address is used and the SNMP option sysUpTime.0 is checked. AOS returns the system uptime. The other options are necessary to ensure the SNMP communication with OmniSwitches. -L authNoPriv defined authentication but does not enforce encryption. MD5 is used for SNMP as it was defined on the network device before.
-==== Monitor port status ====
+===== Monitor port status =====
 The third use case for Nagios Core monitoring of Alcatel-Lucent Enterprise OmniSwitches is the port status monitoring. SNMP is used for this check.
@@ Zeile 64: / Zeile 80: @@
 </code>
-The general service settings are the same used for the uptime monitoring. However, the OID tree is used to monitor the port status. The last four digits define the port, which is 1023 - Port 23 in the first switch of a chassis.
+The general service settings are the same used for the uptime monitoring. However, the OID tree is used to monitor the port status. The last four digits define the port, which is 1023 - Port 23 in the first switch of a chassis. The alternative is to use the object name. That would be ifOperStatus.1023. How to convert the object name to OID and reverse is explained in this [[umwandlung_von_mib_zu_oid_bzw._oid_zu_mib_ueber_die_aos_cli|article]]
-In addition, notifications are enabled for this check. The contact nagiosadmin is notified 24 hours a day, 7 days a week when the status change to warning or critical and even though the status change to resolved. MIB translations can be found on the dokuwiki and also in the support web.
+In addition, notifications are enabled for this check. The contact nagiosadmin is notified 24 hours a day, 7 days a week when the status change to warning or critical and even though the status change to resolved. MIB translations can be found on the dokuwiki and also in the support web. \\
+Furthermore, passwords can be defined in the nagios config file resource.cfg. User variables are used to enable changes of recurring figures. They can be changed in a single point by using this file. In the example, the -A option would be e.g. $USERX$. \\
+Other variables are predefined. The host address can be defined in the host definition. When the host address is needed in services for this host, $HOSTADDRESS$ inserts the IP-Address.