Changes between Version 6 and Version 7 of librenms

Timestamp:

Nov 22, 2016, 8:26:59 AM (8 years ago)

Author:

admin

Comment:

--

librenms

@@ -162 +162 @@
 Check now that you can run snmpstatus against your other group members servers:
 {{{
-$ snmpstatus www.'your neighbors domain.ws.ac.lk
+$ snmpstatus www.'your neighbors domain'.ws.ac.lk
 }}}
 
@@ -200 +200 @@
 }}}
 PLEASE NOTE
-
+vi /etc/mysql/mysql.conf.d/mysqld.cnf
+
+Within the [mysqld] section please add:
+{{{
+innodb_file_per_table=1
+sql-mode=""
+}}}
+service mysql restart
 Here we are using <your Password> as the password for LibreNMS to access MySQL. Please replace <your Password> with, Please do not forget the password as you will need it in the future
 
@@ -254 +261 @@
 
 We need to create a LibreNMS system user, librenms
-
+{{{
 # useradd librenms -d /opt/librenms -M -r
 # usermod -a -G librenms www-data
-
+}}}
  
 ==== Cloning the LibreNMS source code with git ====
@@ -311 +318 @@
 # service apache2 restart
 }}}
-
+==== Web installer ====
+
+You can choose either a web configuration or manual configuration at the command line. We're going to use the Web installer, which is by far the easiest, but we'll include the manual configuration as a reference at the end of this document.
+
+At this stage you can launch the web installer by going to http://librenms.'yourdomain'.ws.ac.lk/install.php
+
+Follow the onscreen instructions.
+
+ - Stage 0 is a summary of the PHP modules installed, normally you should just click on ''Next Stage''
+
+ - Stage 1 prompts you for the database settings. Enter
+
+   *  DB Host: localhost
+
+   *  DB User: librenms
+
+   *  DB Pass: <your password used for mysql database lireNMS>
+
+   *  DB Name: librenms
+
+ - Stage 2 is the DB creating itself - it should finish correctly, and you simply click on ''Goto Add User'' at the bottom
+
+ - Stage 3: enter a username, password (do not forget the password) and E-mail address. This will become the login you use to access the web interface.
+
+ - Stage 4 should show you the successful user creation, click on ''Generate Config''
+
+ - Stage 5: the interface should show, at this point:
+
+The config file has been created
+
+You can now click '''Finish install'''
+
+ - Stage 6: you are done!
+
+You can now follow the instructions and click where it says '''click here to login to your new install'''.
+
+A useful tool is provided with LibreNMS to help verify that the software is installed correctly.
+
+Let's try it out:
+{{{
+# cd /opt/librenms
+# ./validate.php
+}}}
+You may see warnings about the software not being up to date, and some more about permissions. You can probably ignore these for now, but it might come in useful later if you experience issues with LibreNMS.
+
+We can now secure the ''/opt/librenms'' directory again:
+{{{
+# chown librenms /opt/librenms
+}}}
+
+=== Configuring LibreNMS ===
+
+==== Setting the SNMP community ====
+First, edit the file /opt/librenms/config.php,
+
+# vi /opt/librenms/config.php
+
+and find the line:
+{{{
+$config['snmp']['community'] = array("public");
+}}}
+And change it to:
+{{{
+$config['snmp']['community'] = array("NetManage");
+}}}
+ 
+==== Tell LibreNMS which subnets it's allowed to scan automatically ====
+
+By default, LibreNMS will try ask for the list of “neighbors” that network devices "see" on the network. This is done using the Link Layer Discovery Protocol (LLDP) or Cisco's CDP (Cisco Discovery Protocol).
+
+But to be on the safe side, and not scan networks outside your organization, LibreNMS needs to be told which subnets it's allowed to scan for new devices.
+
+Still in the file /opt/librenms/config.php, find the line:
+{{{
+#$config['nets'][] = "10.0.0.0/8";
+}}}
+And replace this with the following to scan our specific subnets in use by our network and the workshop infrastructure.
+{{{
+$config['nets'][] = "192.248.0.0/16";
+}}}
+We need to make one more change...
+
+ 
+==== Tell LibreNMS not to add duplicate devices ====
+
+A situation can happen where two devices have duplicate SNMP sysName. (that's hostname in IOS) They could be two different devices, so it would be a good idea to have LibreNMS automatically add and monitor them.
+
+But it can also happen that the SAME device is seen multiple times by LibreNMS - once using LLDP/CDP, and another time via OSPF (for example).
+
+In that case, it ends up added twice. For instance, you may suddenly see two devices called rtr2-fa0-0.ws.ac.lk and rtr2, and this is not what we want.
+
+Since "both" devices are in fact the same, their SNMP sysName will be identical, and we can tell LibreNMS to NOT add devices if one already exists with the same sysName - after all, this shouldn't happen in a well configured network! 
+
+To avoid this, add the following line at the bottom of the config.php file:
+{{{
+$config['allow_duplicate_sysName'] = false;
+}}}
+... this will prevent LibreNMS from adding the device if it exists already with the same sysName. You will be able to see if there are duplicate devices deteced in the Event Log (Overview -> Event Log).
+
+After you've added the above setting, save the file and exit - we’re nearly done!
+
+ 
+==== Add a host ====
+
+Let's add localhost (i.e.: YOUR virtual server), using the following commands. Later you'll do this from the Web interface:
+
+# cd /opt/librenms
+# php addhost.php localhost NetManage v2c
+
+You should see:
+
+Added device localhost (1)
+
+Notice we explicitly tell LibreNMS which SNMP community to use. We also assume it's SNMP v2c. If you're using v3, there are additional steps which aren't provided here.
+
+==== Discover and Poll newly added hosts ====
+
+LibreNMS first “discovers” each host that has been added. This means that it methodically examines each host you added and figures out what it should monitor. The discover.php script does not automatically scan your network to find new devices. To run this script do:
+{{{
+# cd /opt/librenms
+# sudo -u librenms php discovery.php -h all
+}}}
+NOTE: This could take some time. If you try to add devices that do not yet have an snmp service configured, then the discovery script takes a while to time out.
+
+Once this has finished you can now "poll" the hosts. This means LibreNMS now knows what it wishes to monitor for each host, but it has yet to populate its database with initial values for each item. To do this we do:
+{{{
+# sudo -u librenms php poller.php -h all
+}}}
+As you can see the poller.php script does quite a bit with just a few devices. When we add it to a cronjob below this helps explain why LibreNMS is a resource intensive tool.
+
+==== Create cronjob ====
+
+Create the cronjob which will run periodic tasks required by LibreNMS:
+{{{
+# cd /opt/librenms
+# cp librenms.nonroot.cron /etc/cron.d/librenms
+}}}
+
+ 
+1.4 Install complete
+
+That's it! You now should be able to log in to http://librenms.'your domain'.ws.ac.lk/ and begin to explore the information being collected for your monitored devices.
+
+
+PLEASE NOTE: We have not covered HTTPS setup in this example, so your LibreNMS install is not secure by default. Please do not expose it to the public Internet unless you have configured HTTPS and taken appropriate web server hardening steps.
+