From 721f92548d4b6c372b51fe8cb33485dda0f0983e Mon Sep 17 00:00:00 2001
From: thl-cmk <thl-cmk@outlook.com>
Date: Mon, 5 Aug 2024 18:59:12 +0000
Subject: [PATCH] Update HOWTO.md
---
HOWTO.md | 13 ++++++-------
1 file changed, 6 insertions(+), 7 deletions(-)
diff --git a/HOWTO.md b/HOWTO.md
index 0e630bb..b42dadb 100644
--- a/HOWTO.md
+++ b/HOWTO.md
@@ -65,7 +65,7 @@ Here you will find help on [Checkmk extension packages (MKPs)](https://docs.chec
1. Modify the user settings for NVDCT
- Before you create the topology data, take a look at `~/local/bin/nvdct/nvdct.toml`. Here you can fine tune some aspects of the topology creation. Before you do this, please create a copy of the nvdct.toml file (e.g. my_nvdct.toml) and only change the copy. By working with a copy of the `nvdct.toml` file, you ensure that your changes will survive the next update of the `nvdct.mkp`. For the CDP/LLDP topologies add at least your seed devices - from where NVDCT will start to create the topology - in the `SEED_DEVICES` section.
+ Before you create the topology data, take a look at `~/local/bin/nvdct/conf/nvdct.toml`. Here you can fine tune some aspects of the topology creation. Before you do this, please create a copy of the nvdct.toml file (e.g. my_nvdct.toml) and only change the copy. By working with a copy of the `nvdct.toml` file, you ensure that your changes will survive the next update of the `nvdct.mkp`. For the CDP/LLDP topologies add at least your seed devices - from where NVDCT will start to create the topology - in the `SEED_DEVICES` section.
```
# list of (additional to -s/--seed-devices) seed devices
@@ -88,23 +88,22 @@ Here you will find help on [Checkmk extension packages (MKPs)](https://docs.chec
1. Create the topology data
```
- ~/local/bin/nvdct/nvdct.py -u ~/local/bin/nvdct/my_nvdct.toml
+ ~/local/bin/nvdct/nvdct.py -u ~/local/bin/nvdct/conf/my_nvdct.toml
```
- For CMK 2.2.0 you should find the created data under
- `~/var/topology_data/`. There should be also a symbolic link to the default topology.
+ For CMK 2.3.0 you should find the created data under `~/var/check_mk/topology/data`. There should be also a symbolic link to the default topology.
```
- ~$ ls -ls ~/var/topology_data/
+ ~$ ls -ls ~/var/check_mk/topology/data
total 20
4 drwx------ 2 build build 4096 Apr 30 13:54 2024-04-30T13:54:51.04/
4 drwx------ 2 build build 4096 Apr 30 14:17 2024-04-30T14:17:05.04/
4 drwx------ 2 build build 4096 Apr 30 14:20 2024-04-30T14:20:07.04/
4 drwx------ 2 build build 4096 Apr 30 14:25 2024-04-30T14:25:17.04/
4 drwx------ 2 build build 4096 May 1 13:15 2024-05-01T13:15:51.05/
- 0 lrwxrwxrwx 1 build build 57 Apr 30 14:25 default -> /omd/sites/build/var/topology_data/2024-04-30T14:25:17.04/
+ 0 lrwxrwxrwx 1 build build 57 Apr 30 14:25 default -> /omd/sites/build/var/check_mk/topology/data/2024-04-30T14:25:17.04/
```
- For CMK 2.3.0 you will find those files under `~/var/check_mk/topology/data`
+ For CMK 2.2.0 you will find those files under `~/var/topology_data/`
1. Go to CMK and show the network topology
--
GitLab