107 lines
3.6 KiB
Plaintext
107 lines
3.6 KiB
Plaintext
|
||
Layer 2 Discovery Module for LLDP
|
||
Installation document
|
||
|
||
------------------
|
||
Tree Layout
|
||
------------------
|
||
|
||
./ .................... Top-Level Root Directory
|
||
COPYING ............. License description (GPL version 2)
|
||
ChangeLog ........... Binary package change history
|
||
INSTALL ............. This file
|
||
README.md............ Overview of this distribution
|
||
|
||
data/ ................. Configuration files for Zabbix
|
||
zabbix3.0/ .......... Configuration file for Zabbix 3.0
|
||
templates/ ........ LLDP monitoring template
|
||
value_mapping/ .... Configuration file for value mapping
|
||
|
||
mibs/ ................. Management Information Base files
|
||
lldp-mibs/ .......... Management Information Base module for LLDP (LLDP-MIB)
|
||
|
||
source/ .............. Source of Zabbix loadable module
|
||
|
||
------------------
|
||
Install
|
||
------------------
|
||
|
||
How to install loadable module.
|
||
-----------------------------------
|
||
|
||
1. Store the LLDP-MIB files in a location according to Net-SNMP's MIBDIR setting.
|
||
|
||
ex) /usr/share/snmp/mibs/
|
||
|
||
2. Build and store the loadable module in place.
|
||
|
||
ex) /usr/lib/zabbix/modules/
|
||
|
||
3. Make settings to load loadable modules into Zabbix Server / Proxy configuration file.
|
||
|
||
ex) LoadModulePath=/usr/lib/zabbix/modules
|
||
LoadModule=lldp_get.so
|
||
|
||
4. Restart the Zabbix Server / Proxy process.
|
||
Check the Zabbix Server / Proxy log file and confirm that the following wording
|
||
indicating that the loadable module has been loaded is output.
|
||
|
||
ex) lldp_get module: loaded by server process. [1]
|
||
loaded modules: lldp_get.so
|
||
|
||
The display may vary depending on the version of Zabbix and the log debug level.
|
||
(The example shows the case when Zabbix 3.0 is set to log level 3)
|
||
|
||
|
||
How to setting templates
|
||
-----------------------------------
|
||
|
||
1. Login to the Zabbix Web interface with an account with super administrator privileges.
|
||
|
||
2. [Administration] -> [General settings] -> [Value mapping], value mapping
|
||
Import the file for setting.
|
||
|
||
3. [Settings] -> [Template], import the LLDP monitoring template.
|
||
|
||
|
||
How to setting the host
|
||
-----------------------------------
|
||
|
||
1. "Create Host" is done from setting screen.
|
||
Set the IP address in "SNMP interfaces".
|
||
|
||
2. Set "Template LLDP - General" or "Template LLDP - IndexNum" to the created host. (Select one)
|
||
|
||
Template LLDP - General .... Use "ifName" as the local port number
|
||
Template LLDP - IndexNum ... Use "ifIndex" as the local port number
|
||
|
||
Tips : In most cases, please use "Template LLDP - General".
|
||
If the local port number becomes "eth0" please try "Template LLDP - IndexNum".
|
||
|
||
3. (Zabbix 3.x) Wait for low-level discovery to generate the item.
|
||
(Zabbix 4.0 or later) Execute [Check now] from the discovery rule on the host setting screen to generate the item.
|
||
|
||
|
||
------------------
|
||
Special function
|
||
------------------
|
||
|
||
How to overwrite lldp.rem.sysname
|
||
-----------------------------------
|
||
|
||
You can override the adjacent device host name ([Connect to] Host item) using host macros.
|
||
|
||
1. Check the 5th parameter (macro name) from the key of the item that is acquiring
|
||
the neighbor device information.
|
||
|
||
ex) Item Key : lldp.rem.sysname[{HOST.CONN},{$SNMP_COMMUNITY},1,7,{$FIXED_SYSNAME_1}]
|
||
5th parameter : {$FIXED_SYSNAME_1}
|
||
|
||
2. On the host macro setting screen, make the following settings.
|
||
Set "character string acquired from the fifth parameter" in the macro field.
|
||
Set "Overwrite character string" in the value field.
|
||
|
||
3. From the next monitoring timing, the specified character string is collected as "Neighbor device host name".
|
||
|
||
# EOF
|