Collection of CheckMK checks (see https://checkmk.com/). All checks and plugins are provided as is. Absolutely no warranty. Send any comments to thl-cmk[at]outlook[dot]com

Skip to content
Snippets Groups Projects
Commit 2161f487 authored by thl-cmk's avatar thl-cmk :flag_na:
Browse files

Update README.md

parent 1ece3831
No related branches found
No related tags found
No related merge requests found
......@@ -175,7 +175,7 @@ OMD[build]:~$
---
### Limitations
- local/neighbour interface names have to match the service names in Checkmk
- ~~local/neighbour interface names have to match the service names in Checkmk~~
---
### FAQ
......@@ -323,6 +323,14 @@ Wehre `--path-in-inventory` is the path to your inventory data and `--inventory-
</details>
<details><summary>How are port names mapped to interface service names?</summary>
\
When mapping Layer 2 port names, the first step is to check whether the port name is in the host's list of interface items; if it is, the port name is used; if it is not, the port name is searched for in the inventory interface table. If found it tries to find the correct item by comparing the list of items with the fields index, description, alias, physical address (MAC) and (if available) [name](https://thl-cmk.hopto.org/gitlab/checkmk/vendor-independent/inventory/inv_ifname). If we still can't find the item, we pad the index and try the search again.
So most of the time we should find the correct interface service for a port.
</details>
---
### Sample Output
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment