mirror of
https://github.com/librenms/librenms.git
synced 2024-10-07 16:52:45 +00:00
Fix some spellings.
This commit is contained in:
@@ -771,7 +771,7 @@ Output:
|
|||||||
{
|
{
|
||||||
"status": "ok",
|
"status": "ok",
|
||||||
"err-msg": "",
|
"err-msg": "",
|
||||||
"message": "Alert has been ackgnowledged"
|
"message": "Alert has been acknowledged"
|
||||||
}
|
}
|
||||||
```
|
```
|
||||||
|
|
||||||
|
@@ -11,7 +11,7 @@ if ($foo == 5) {
|
|||||||
```
|
```
|
||||||
|
|
||||||
### Line length
|
### Line length
|
||||||
Try to keep the length of a line to about 75-85 characters. This isn't essential but does enable compatbility for all screen sizes but above all enables reading of code easier.
|
Try to keep the length of a line to about 75-85 characters. This isn't essential but does enable compatibility for all screen sizes but above all enables reading of code easier.
|
||||||
|
|
||||||
### Control structures
|
### Control structures
|
||||||
A space should be used both before and after the parenthesis and also surrounding the condition operator.
|
A space should be used both before and after the parenthesis and also surrounding the condition operator.
|
||||||
|
@@ -79,12 +79,12 @@ __Installation__:
|
|||||||
_Note_: In case you get `Makefile:9: *** missing separator. Stop.`, compile manually using:
|
_Note_: In case you get `Makefile:9: *** missing separator. Stop.`, compile manually using:
|
||||||
* With IPv6: `gcc -Wall -O2 -fstack-protector -DWITH_IPV6 -o tinystats tinystats.c`
|
* With IPv6: `gcc -Wall -O2 -fstack-protector -DWITH_IPV6 -o tinystats tinystats.c`
|
||||||
* Without IPv6: `gcc -Wall -O2 -fstack-protector -o tinystats tinystats.c`
|
* Without IPv6: `gcc -Wall -O2 -fstack-protector -o tinystats tinystats.c`
|
||||||
3. Install into prefered path, like `/usr/bin/`.
|
3. Install into preferred path, like `/usr/bin/`.
|
||||||
|
|
||||||
__Configuration__:
|
__Configuration__:
|
||||||
|
|
||||||
_Note_: In this part we assume that you use DJB's [Daemontools](http://cr.yp.to/daemontools.html) to start/stop tinydns.
|
_Note_: In this part we assume that you use DJB's [Daemontools](http://cr.yp.to/daemontools.html) to start/stop tinydns.
|
||||||
And that your tinydns-instance is located in `/service/dns`, adjust this path if necesary.
|
And that your tinydns-instance is located in `/service/dns`, adjust this path if necessary.
|
||||||
|
|
||||||
1. Replace your _log_'s `run` file, typically located in `/service/dns/log/run` with:
|
1. Replace your _log_'s `run` file, typically located in `/service/dns/log/run` with:
|
||||||
```
|
```
|
||||||
@@ -95,7 +95,7 @@ And that your tinydns-instance is located in `/service/dns`, adjust this path if
|
|||||||
2. Create tinystats directory and chown:
|
2. Create tinystats directory and chown:
|
||||||
`mkdir /service/dns/log/main/tinystats && chown dnslog:nofiles /service/dns/log/main/tinystats`
|
`mkdir /service/dns/log/main/tinystats && chown dnslog:nofiles /service/dns/log/main/tinystats`
|
||||||
3. Restart TinyDNS and Daemontools: `/etc/init.d/svscan restart`
|
3. Restart TinyDNS and Daemontools: `/etc/init.d/svscan restart`
|
||||||
_Note_: Some say `svc -t /service/dns` is enough, on my install (Gentoo) it doesnt rehook the logging and I'm forced to restart it entirely.
|
_Note_: Some say `svc -t /service/dns` is enough, on my install (Gentoo) it doesn't rehook the logging and I'm forced to restart it entirely.
|
||||||
|
|
||||||
### MySQL
|
### MySQL
|
||||||
|
|
||||||
|
@@ -104,7 +104,7 @@ Placeholders:
|
|||||||
- Time Elapsed, Only available on recovery (`%state == 0`): `%elapsed`
|
- Time Elapsed, Only available on recovery (`%state == 0`): `%elapsed`
|
||||||
- Alert-ID: `%id`
|
- Alert-ID: `%id`
|
||||||
- Unique-ID: `%uid`
|
- Unique-ID: `%uid`
|
||||||
- Faults, Only available on alert (`%state != 0`), must be iterated in a foreach (`{foreach %faults}`). Holds all available information about the Fault, accessable in the format `%value.Column`, for example: `%value.ifDescr`. Special field `%value.string` has most Identification-information (IDs, Names, Descrs) as single string, this is the equivalent of the default used.
|
- Faults, Only available on alert (`%state != 0`), must be iterated in a foreach (`{foreach %faults}`). Holds all available information about the Fault, accessible in the format `%value.Column`, for example: `%value.ifDescr`. Special field `%value.string` has most Identification-information (IDs, Names, Descrs) as single string, this is the equivalent of the default used.
|
||||||
- State: `%state`
|
- State: `%state`
|
||||||
- Severity: `%severity`
|
- Severity: `%severity`
|
||||||
- Rule: `%rule`
|
- Rule: `%rule`
|
||||||
@@ -379,7 +379,7 @@ $config['alert']['transports']['pushbullet'] = 'MYFANCYACCESSTOKEN';
|
|||||||
## <a name="transports-clickatell">Clickatell</a>
|
## <a name="transports-clickatell">Clickatell</a>
|
||||||
|
|
||||||
Clickatell provides a REST-API requiring an Authorization-Token and at least one Cellphone number.
|
Clickatell provides a REST-API requiring an Authorization-Token and at least one Cellphone number.
|
||||||
Please consult Clickatell's documentation regarding number formating.
|
Please consult Clickatell's documentation regarding number formatting.
|
||||||
Here an example using 3 numbers, any amount of numbers is supported:
|
Here an example using 3 numbers, any amount of numbers is supported:
|
||||||
|
|
||||||
~~
|
~~
|
||||||
|
@@ -46,7 +46,7 @@ We would recommend that you run some form of php caching application such as PHP
|
|||||||
The MySQL server should be contactable from this layer on port 3306 unless it's changed.
|
The MySQL server should be contactable from this layer on port 3306 unless it's changed.
|
||||||
|
|
||||||
####Database Server
|
####Database Server
|
||||||
MySQL - At the moment this is the only databse server that is supported, work is being done to ensure MySQL Strict mode is also supported but this should be considered to be incomplete still.
|
MySQL - At the moment this is the only database server that is supported, work is being done to ensure MySQL Strict mode is also supported but this should be considered to be incomplete still.
|
||||||
|
|
||||||
The pollers, web and API layers should all be able to access the database server directly. It would be possible to configure MySQL multi master but that is outside the scope of this document.
|
The pollers, web and API layers should all be able to access the database server directly. It would be possible to configure MySQL multi master but that is outside the scope of this document.
|
||||||
|
|
||||||
@@ -63,7 +63,7 @@ $config['rrdtool_version'] = 1.5;
|
|||||||
```
|
```
|
||||||
|
|
||||||
####Memcache
|
####Memcache
|
||||||
Memcache is required for the distributed pollers to be able to register to a central location and record what devices are polled. Memcache can run from any of the kit so long as it is accessable by all pollers.
|
Memcache is required for the distributed pollers to be able to register to a central location and record what devices are polled. Memcache can run from any of the kit so long as it is accessible by all pollers.
|
||||||
|
|
||||||
####Pollers
|
####Pollers
|
||||||
Pollers can be installed and run from anywhere, the only requirements are:
|
Pollers can be installed and run from anywhere, the only requirements are:
|
||||||
@@ -78,7 +78,7 @@ This will provide the ability to have a single poller behind a NAT firewall moni
|
|||||||
|
|
||||||
Another benefit to this is that you can provide N+x pollers, i.e if you know that you require three pollers to process all devices within 300 seconds then adding a 4th poller will mean that should any one single poller fail then the remaining three will complete polling in time. You could also use this to take a poller out of service for maintenance, i.e OS updates and software updates.
|
Another benefit to this is that you can provide N+x pollers, i.e if you know that you require three pollers to process all devices within 300 seconds then adding a 4th poller will mean that should any one single poller fail then the remaining three will complete polling in time. You could also use this to take a poller out of service for maintenance, i.e OS updates and software updates.
|
||||||
|
|
||||||
It is exctremely advisable to either run a central recursive dns server such as pdns-recursor and have all of your pollers use this or install a recursive dns server on each poller - the volume of DNS requests on large installs can be significant.
|
It is extremely advisable to either run a central recursive dns server such as pdns-recursor and have all of your pollers use this or install a recursive dns server on each poller - the volume of DNS requests on large installs can be significant.
|
||||||
|
|
||||||
####Discovery
|
####Discovery
|
||||||
It's not necessary to run discovery services on all pollers. In fact, you should only run one discovery process per poller group. Designate a single poller to run discovery (or a seperate server if required).
|
It's not necessary to run discovery services on all pollers. In fact, you should only run one discovery process per poller group. Designate a single poller to run discovery (or a seperate server if required).
|
||||||
|
@@ -2,9 +2,9 @@
|
|||||||
|
|
||||||
LibreNMS comes with a configurable geochart based frontpage to visualize where your gear is located geographically.
|
LibreNMS comes with a configurable geochart based frontpage to visualize where your gear is located geographically.
|
||||||
|
|
||||||
### Expiremental map
|
### Experimentall map
|
||||||
|
|
||||||
An new expiremental map is available, this requires you to have properly formatted addresses in sysLocation or sysLocation override. As part of the standard poller these addresses will be Geocoded by Google and stored in the database. To enable this please set the following config:
|
An new experimental map is available, this requires you to have properly formatted addresses in sysLocation or sysLocation override. As part of the standard poller these addresses will be Geocoded by Google and stored in the database. To enable this please set the following config:
|
||||||
|
|
||||||
```php
|
```php
|
||||||
$config['front_page'] = "pages/front/map.php";
|
$config['front_page'] = "pages/front/map.php";
|
||||||
|
@@ -1,7 +1,7 @@
|
|||||||
# Graylog integration
|
# Graylog integration
|
||||||
|
|
||||||
We have simple integration for Graylog, you will be able to view any logs from within LibreNMS that have been parsed by the syslog input from within
|
We have simple integration for Graylog, you will be able to view any logs from within LibreNMS that have been parsed by the syslog input from within
|
||||||
Graylog itself. This includes logs from devices which aren't in LibreNMS still, you can also see logs for a sepcific device under the logs section
|
Graylog itself. This includes logs from devices which aren't in LibreNMS still, you can also see logs for a specific device under the logs section
|
||||||
for the device.
|
for the device.
|
||||||
|
|
||||||
Graylog itself isn't included within LibreNMS, you will need to install this separately either on the same infrastructure as LibreNMS or as a totally
|
Graylog itself isn't included within LibreNMS, you will need to install this separately either on the same infrastructure as LibreNMS or as a totally
|
||||||
|
@@ -45,7 +45,7 @@ Command | Description
|
|||||||
`.join <channel>` | Joins `<channel>` if user has admin-level.
|
`.join <channel>` | Joins `<channel>` if user has admin-level.
|
||||||
`.listdevices` | Lists the hostnames of all known devices.
|
`.listdevices` | Lists the hostnames of all known devices.
|
||||||
`.log [<N>]` | Prints `N` lines or last line of the eventlog.
|
`.log [<N>]` | Prints `N` lines or last line of the eventlog.
|
||||||
`.port <hostname> <ifname>` | Prints Port-related informations from `ifname` on given `hostname`.
|
`.port <hostname> <ifname>` | Prints Port-related information from `ifname` on given `hostname`.
|
||||||
`.quit` | Disconnect from IRC and exit.
|
`.quit` | Disconnect from IRC and exit.
|
||||||
`.reload` | Reload configuration.
|
`.reload` | Reload configuration.
|
||||||
`.status <type>` | Prints status informations for given `type`. Type can be `devices`, `services`, `ports`. Shorthands are: `dev`,`srv`,`prt`
|
`.status <type>` | Prints status informations for given `type`. Type can be `devices`, `services`, `ports`. Shorthands are: `dev`,`srv`,`prt`
|
||||||
@@ -105,10 +105,10 @@ Or using a single string using `,` as delimiter between various channels:
|
|||||||
# <a name="extensions">Extensions?!</a>
|
# <a name="extensions">Extensions?!</a>
|
||||||
|
|
||||||
The bot is coded in a unified way.
|
The bot is coded in a unified way.
|
||||||
This makes writing extensions by far less painfull.
|
This makes writing extensions by far less painful.
|
||||||
Simply add your `command` to the `$config['irc_external']` directive and create a file called `includes/ircbot/command.inc.php` containing your code.
|
Simply add your `command` to the `$config['irc_external']` directive and create a file called `includes/ircbot/command.inc.php` containing your code.
|
||||||
The string behind the call of `.command` is passed as `$params`.
|
The string behind the call of `.command` is passed as `$params`.
|
||||||
The user who requested something is accessable via `$this->user`.
|
The user who requested something is accessible via `$this->user`.
|
||||||
Send your reply/ies via `$this->respond($string)`.
|
Send your reply/ies via `$this->respond($string)`.
|
||||||
|
|
||||||
A more detailed documentation of the functions and variables available for extensions can be found at [IRC-Bot Extensions](IRC-Bot-Extensions);
|
A more detailed documentation of the functions and variables available for extensions can be found at [IRC-Bot Extensions](IRC-Bot-Extensions);
|
||||||
|
@@ -17,7 +17,7 @@ For this a small `bash` script is supplied in `scripts/` called `ifAlias`.
|
|||||||
This requires a little bit of setup on the monitored Server (Not the server running librenms!):
|
This requires a little bit of setup on the monitored Server (Not the server running librenms!):
|
||||||
|
|
||||||
* Add `ifAlias` from `/opt/librenms/scripts/` or download it from [here](#source) to the Server and make
|
* Add `ifAlias` from `/opt/librenms/scripts/` or download it from [here](#source) to the Server and make
|
||||||
it executeable `chmod +x /path/to/ifAlias`
|
it executable `chmod +x /path/to/ifAlias`
|
||||||
* Add to `snmpd.conf` something like:
|
* Add to `snmpd.conf` something like:
|
||||||
``pass .1.3.6.1.2.1.31.1.1.1.18 /path/to/ifAlias``
|
``pass .1.3.6.1.2.1.31.1.1.1.18 /path/to/ifAlias``
|
||||||
* Restart your `net-snmpd`
|
* Restart your `net-snmpd`
|
||||||
@@ -50,6 +50,6 @@ See [examples](#examples) for formats.
|
|||||||
# eth2: Peering: Peering Exchange
|
# eth2: Peering: Peering Exchange
|
||||||
```
|
```
|
||||||
|
|
||||||
# <a name="source">Sourcecode</a>:
|
# <a name="source">Source code</a>:
|
||||||
|
|
||||||
* https://github.com/librenms/librenms/blob/master/scripts/ifAlias
|
* https://github.com/librenms/librenms/blob/master/scripts/ifAlias
|
||||||
|
@@ -16,7 +16,7 @@ Either remove mac or xdp depending on which you want.
|
|||||||
A global map will be drawn from the information in the database, it is worth noting that this could lead to a large network map.
|
A global map will be drawn from the information in the database, it is worth noting that this could lead to a large network map.
|
||||||
Network maps for individual devices are available showing the relationship with other devices.
|
Network maps for individual devices are available showing the relationship with other devices.
|
||||||
|
|
||||||
One can also specicify the parameters to be used for drawing and updateing the network map.
|
One can also specicify the parameters to be used for drawing and updating the network map.
|
||||||
Please see http://visjs.org/docs/network/ for details on the configuration parameters.
|
Please see http://visjs.org/docs/network/ for details on the configuration parameters.
|
||||||
```php
|
```php
|
||||||
$config['network_map_vis_options'] = '{
|
$config['network_map_vis_options'] = '{
|
||||||
|
@@ -23,15 +23,15 @@ $config['poller_service_single_connection'] = false;
|
|||||||
```
|
```
|
||||||
|
|
||||||
## Distributed Polling
|
## Distributed Polling
|
||||||
Distributed polling is possible, and uses the same configuration options as are described for traditional distributed polling, except that the memcached options are not necessary. The database must be acessable from the distributed pollers, and properly configured. Remote access to the RRD directory must also be configured as described in the Distributed Poller documentation. Memcache is not required. Concurrency is managed using mysql GET_LOCK to ensure that devices are only being polled by one device at at time. The poller service is compatible with poller groups.
|
Distributed polling is possible, and uses the same configuration options as are described for traditional distributed polling, except that the memcached options are not necessary. The database must be accessible from the distributed pollers, and properly configured. Remote access to the RRD directory must also be configured as described in the Distributed Poller documentation. Memcache is not required. Concurrency is managed using mysql GET_LOCK to ensure that devices are only being polled by one device at at time. The poller service is compatible with poller groups.
|
||||||
|
|
||||||
## Multi-Master MySQL considerations
|
## Multi-Master MySQL considerations
|
||||||
Because locks are not replicated in Multi-Master MySQL configurations, if you are using such a configuration, you will need to make sure that all pollers are using the same MySQL server.
|
Because locks are not replicated in Multi-Master MySQL configurations, if you are using such a configuration, you will need to make sure that all pollers are using the same MySQL server.
|
||||||
|
|
||||||
## Single Connection
|
## Single Connection
|
||||||
If you are running MariaDB 10.2 or newer, you can tell poller-service to use a single mysql connectino for managing locks by setting `$config['poller_service_single_connection']` to `true`. *DO NOT* configure this for any version of MariaDB less than 10.2 or any version of MySQL.
|
If you are running MariaDB 10.2 or newer, you can tell poller-service to use a single mysql connection for managing locks by setting `$config['poller_service_single_connection']` to `true`. *DO NOT* configure this for any version of MariaDB less than 10.2 or any version of MySQL.
|
||||||
|
|
||||||
## Service Installation
|
## Service Installation
|
||||||
An upstart configuration `poller-service.conf` is provided. To install run `ln -s /opt/librenms/poller-service.conf /etc/init/poller-service.conf`. The service will start on boot and can be started manually by running `start poller-service`. If you recieve an error that the service does not exist, run `initctl reload-configuration`. The service is configured to run as the user `librenms` and will fail if that user does not exist.
|
An upstart configuration `poller-service.conf` is provided. To install run `ln -s /opt/librenms/poller-service.conf /etc/init/poller-service.conf`. The service will start on boot and can be started manually by running `start poller-service`. If you receive an error that the service does not exist, run `initctl reload-configuration`. The service is configured to run as the user `librenms` and will fail if that user does not exist.
|
||||||
|
|
||||||
An LSB init script `poller-service.init` is also provided. To install run `ln -s /opt/librenms/poller-service.init /etc/init.d/poller-service && update-rc.d poller-service defaults`.
|
An LSB init script `poller-service.init` is also provided. To install run `ln -s /opt/librenms/poller-service.init /etc/init.d/poller-service && update-rc.d poller-service defaults`.
|
||||||
|
@@ -1,6 +1,6 @@
|
|||||||
# Configuring interface descriptions for parsing.
|
# Configuring interface descriptions for parsing.
|
||||||
|
|
||||||
LibreNMS includes the ability to parse your interface descriptions for set information to diplay and segement in the WebUI.
|
LibreNMS includes the ability to parse your interface descriptions for set information to diplay and segment in the WebUI.
|
||||||
|
|
||||||
The following information is used from interface descriptions:
|
The following information is used from interface descriptions:
|
||||||
|
|
||||||
|
@@ -10,7 +10,7 @@ $config['rrdtool_version'] = 1.5;
|
|||||||
```
|
```
|
||||||
|
|
||||||
### RRDCached installation CentOS 6
|
### RRDCached installation CentOS 6
|
||||||
This example is based on a fresh LibreNMS install, on a minimimal CentOS 6 installation.
|
This example is based on a fresh LibreNMS install, on a minimal CentOS 6 installation.
|
||||||
In this example, we'll use the Repoforge repository.
|
In this example, we'll use the Repoforge repository.
|
||||||
|
|
||||||
```ssh
|
```ssh
|
||||||
|
@@ -10,7 +10,7 @@ Table of Content:
|
|||||||
# <a name="about">About</a>
|
# <a name="about">About</a>
|
||||||
|
|
||||||
Over the last couple of years, the primary attack vector for internet accounts has been static passwords.
|
Over the last couple of years, the primary attack vector for internet accounts has been static passwords.
|
||||||
Therefore static passwords are no longer suffient to protect unauthorized access to accounts.
|
Therefore static passwords are no longer sufficient to protect unauthorized access to accounts.
|
||||||
Two Factor Authentication adds a variable part in authentication procedures.
|
Two Factor Authentication adds a variable part in authentication procedures.
|
||||||
A user is now required to supply a changing 6-digit passcode in addition to it's password to obtain access to the account.
|
A user is now required to supply a changing 6-digit passcode in addition to it's password to obtain access to the account.
|
||||||
|
|
||||||
@@ -33,8 +33,8 @@ RFC4226 suggests a resynchronization attempt in case the passcode mismatches, pr
|
|||||||
|
|
||||||
## <a name="hotp">Counterbased One-Time-Password (TOTP)</a>
|
## <a name="hotp">Counterbased One-Time-Password (TOTP)</a>
|
||||||
|
|
||||||
This type uses an internal counter that needs to be in-synch with the server's counter to successfully authenticate the passcodes.
|
This type uses an internal counter that needs to be in sync with the server's counter to successfully authenticate the passcodes.
|
||||||
The main advantage over timebased OTP is the attacker doesnt only need to know the Secretkey but also the server's Counter in order to create valid passcodes.
|
The main advantage over timebased OTP is the attacker doesn't only need to know the Secretkey but also the server's Counter in order to create valid passcodes.
|
||||||
RFC4226 suggests a resynchronization attempt in case the passcode mismatches, providing the attacker a range of upto +4 increments from the actual counter to create passcodes.
|
RFC4226 suggests a resynchronization attempt in case the passcode mismatches, providing the attacker a range of upto +4 increments from the actual counter to create passcodes.
|
||||||
|
|
||||||
# <a name="config">Configuration</a>
|
# <a name="config">Configuration</a>
|
||||||
@@ -44,7 +44,7 @@ Enable Two-Factor:
|
|||||||
$config['twofactor'] = true;
|
$config['twofactor'] = true;
|
||||||
```
|
```
|
||||||
|
|
||||||
Set throttle-time (in secconds):
|
Set throttle-time (in seconds):
|
||||||
```php
|
```php
|
||||||
$config['twofactor_lock'] = 300;
|
$config['twofactor_lock'] = 300;
|
||||||
```
|
```
|
||||||
@@ -57,12 +57,12 @@ Create a Two-Factor key:
|
|||||||
- Go to 'My Settings' (/preferences/)
|
- Go to 'My Settings' (/preferences/)
|
||||||
- Choose TwoFactor type
|
- Choose TwoFactor type
|
||||||
- Click on 'Generate TwoFactor Secret Key'
|
- Click on 'Generate TwoFactor Secret Key'
|
||||||
- If your browser didnt reload, reload manually
|
- If your browser didn't reload, reload manually
|
||||||
- Scan provided QR or click on 'Manual' to see the Key
|
- Scan provided QR or click on 'Manual' to see the Key
|
||||||
|
|
||||||
## <a name="usage-google">Google Authenticator</a>
|
## <a name="usage-google">Google Authenticator</a>
|
||||||
|
|
||||||
Installation guides for Google Authneticator can be found [here](https://support.google.com/accounts/answer/1066447?hl=en).
|
Installation guides for Google Authenticator can be found [here](https://support.google.com/accounts/answer/1066447?hl=en).
|
||||||
|
|
||||||
Usage:
|
Usage:
|
||||||
- Create a key like described above
|
- Create a key like described above
|
||||||
|
@@ -102,7 +102,7 @@ General Guidelines
|
|||||||
web chat](http://webchat.freenode.net/) and follow the prompts to chat
|
web chat](http://webchat.freenode.net/) and follow the prompts to chat
|
||||||
via the web client.
|
via the web client.
|
||||||
|
|
||||||
- Ensure you read the Code Guidelines documention and understand the code
|
- Ensure you read the Code Guidelines documentation and understand the code
|
||||||
style that should be adhered to [6].
|
style that should be adhered to [6].
|
||||||
|
|
||||||
|
|
||||||
|
@@ -54,7 +54,7 @@ if (!$os) {
|
|||||||
}
|
}
|
||||||
```
|
```
|
||||||
|
|
||||||
Here is the file location for polling the new OS within a vendor MIB or a standart one:
|
Here is the file location for polling the new OS within a vendor MIB or a standard one:
|
||||||
|
|
||||||
```bash
|
```bash
|
||||||
includes/polling/os/pulse.inc.php
|
includes/polling/os/pulse.inc.php
|
||||||
@@ -73,7 +73,7 @@ Quick explanation and examples :
|
|||||||
|
|
||||||
```bash
|
```bash
|
||||||
snmpwalk -v2c -c public -m SNMPv2-MIB -M mibs
|
snmpwalk -v2c -c public -m SNMPv2-MIB -M mibs
|
||||||
//will give the overall OIDs that can be retrieve with this Standart MIB. OID on the left side and the result on the right side
|
//will give the overall OIDs that can be retrieve with this standard MIB. OID on the left side and the result on the right side
|
||||||
//Then we have just to pick the wanted OID and do a check
|
//Then we have just to pick the wanted OID and do a check
|
||||||
|
|
||||||
snmpget -v2c -c public -OUsb -m SNMPv2-MIB -M /opt/librenms/mibs -t 30 HOSTNAME SNMPv2-SMI::mib-2.1.1.0
|
snmpget -v2c -c public -OUsb -m SNMPv2-MIB -M /opt/librenms/mibs -t 30 HOSTNAME SNMPv2-SMI::mib-2.1.1.0
|
||||||
@@ -118,7 +118,7 @@ At first we copy the MIB file into the default directory:
|
|||||||
|
|
||||||
We are now ready to look at inside the file and find the OID we want to use. _For this documentation we'll use Pulse Secure devices._
|
We are now ready to look at inside the file and find the OID we want to use. _For this documentation we'll use Pulse Secure devices._
|
||||||
|
|
||||||
Then we can test it with the snmpget command (hostname must be reachabled):
|
Then we can test it with the snmpget command (hostname must be reachable):
|
||||||
|
|
||||||
```bash
|
```bash
|
||||||
//for example the OID iveCpuUtil.0:
|
//for example the OID iveCpuUtil.0:
|
||||||
@@ -324,7 +324,7 @@ if (is_numeric($sessions)) {
|
|||||||
```
|
```
|
||||||
We finish in the declaration of the two graph types in the database:
|
We finish in the declaration of the two graph types in the database:
|
||||||
|
|
||||||
We can do that within a file to share our work and contribute in the developpement of LibreNMS. :-)
|
We can do that within a file to share our work and contribute in the development of LibreNMS. :-)
|
||||||
|
|
||||||
```bash
|
```bash
|
||||||
sql-schema/xxx.sql
|
sql-schema/xxx.sql
|
||||||
|
@@ -791,7 +791,7 @@ function ack_alert() {
|
|||||||
$status = 'ok';
|
$status = 'ok';
|
||||||
$code = 200;
|
$code = 200;
|
||||||
if (dbUpdate(array('state' => 2), 'alerts', '`id` = ? LIMIT 1', array($alert_id))) {
|
if (dbUpdate(array('state' => 2), 'alerts', '`id` = ? LIMIT 1', array($alert_id))) {
|
||||||
$message = 'Alert has been ackgnowledged';
|
$message = 'Alert has been acknowledged';
|
||||||
}
|
}
|
||||||
else {
|
else {
|
||||||
$message = 'No alert by that ID';
|
$message = 'No alert by that ID';
|
||||||
|
Reference in New Issue
Block a user