... | ... | @@ -27,11 +27,11 @@ Since you're logged in as super-admin, you can see the `Configuration` menu and |
|
|
|
|
|
Go to `Services`->`Machines` and click `Add New Machine`, type in `agent-bind9`.
|
|
|
|
|
|
Normally you would type in an FQDN or an IP address of the machine you want to monitor. By default Stork is being deployed using Docker. There are some example docker containers that run several sample machines that run Kea, BIND9 and two Kea instances running in failover pair. agent-bind9 is a name of one of such containers. Note that you didn't specify what kind of software is running on the `agent-bind9` machine. Stork server connected to the stork agent running that and the agent looked for Kea and BIND9 and found only bind. It should detect BIND9 app running there.
|
|
|
Normally you would type in an FQDN or an IP address of the machine you want to monitor. By default Stork is being deployed using Docker. There are several docker containers simulating machines with Kea and BIND9 in various modes of operation. agent-bind9 is a name of one of such containers. Note that you didn't specify what kind of software is running on the `agent-bind9` machine. Stork server connected to the stork agent running that and the agent looked for Kea and BIND9 and found only BIND. It should detect BIND9 app running there.
|
|
|
|
|
|
5. **Inspect the agent-bind9 machine**.
|
|
|
|
|
|
Click around. As of 0.3 the BIND9 capabilities are basic. Stork is able to check if bind9 process is running and display its version, number of zones configured, time since it last reconfiguration and more.
|
|
|
Click around. As of 0.5 the BIND9 capabilities are basic. Stork is able to check if bind9 process is running and display its version, number of zones configured, time since it last reconfiguration and more.
|
|
|
|
|
|
6. **Add new Kea machine to monitor**.
|
|
|
|
... | ... | @@ -53,7 +53,7 @@ The sample Kea configuration has couple subnets that you can inspect here. |
|
|
|
|
|
Go to `Services`->`Machines` and click `Add New Machine`, and add `agent-kea-ha1`. Repeat for `agent-kea-ha2`.
|
|
|
|
|
|
You can now inspect the HA status of those servers.
|
|
|
You can now inspect the HA status of those servers. Note the difference between the status between two partners.
|
|
|
|
|
|
9. **DHCPv6 support**.
|
|
|
|
... | ... | @@ -61,19 +61,19 @@ Stork fully supports IPv6 from the day one. Add another machine called `agent-ke |
|
|
|
|
|
10. **All subnets in your network**.
|
|
|
|
|
|
Stork lets you view and search through the subnets and pools. Go to `DHCP` and then `Subnets`. You will see all the subnets with pools in them. You can filter the subnets by type (any, DHCPv4 or DHCPv6). You can also type any string. For example, to limit the subnet to 192.0.3.0, you can search for `0.3`. Note that strings shorter than 4 characters require you to press Enter at the end. You can search for specific subnets, pools or pool boundaries.
|
|
|
Stork lets you view and search through the subnets and pools. Go to `DHCP` and then `Subnets`. You will see all the subnets with pools in them. You can filter the subnets by type (any, DHCPv4 or DHCPv6). You can also type any string. For example, to limit the subnet to 192.0.3.0, you can search for `0.3`. Note that strings shorter than 4 characters require you to confirm with Enter (strings of 4 chars or longer does not require that). You can search for specific subnets, pools or pool boundaries.
|
|
|
|
|
|
11. **Pool utilization**.
|
|
|
|
|
|
Open a new tab in your browser and connect to http://localhost:5000 (if running locally) or to http://stork.lab.isc.org:5000 to take a look at the traffic generator. This is not part of the Stork itself, it's a tool we developed to simulate actual networks. It's a bit simple, but sufficient enough to generate traffic. It retrieves list of subnets known by Stork and enables to generate traffic for each subnet. You may want to experiment with it. Things to play with it:
|
|
|
|
|
|
- set the number of clients to somewhat smaller value than the pool size. You'll see a warning (yellow triangle) once you cross the 80% utilization and critical (red error) once you cross 90%. Those threshold are hardcoded as of 0.5, but will be configurable in the future versions.
|
|
|
- set the number of clients to somewhat smaller value than the pool size. You'll see a warning (yellow triangle) once you cross the 80% utilization and critical (red error) once you cross 90%. Those thresholds are hardcoded as of 0.5, but will be configurable in the future versions.
|
|
|
|
|
|
- traffic generator is currently not able to generate traffic for more than one subnet in a shared network. When you click Start in the next subnet, the traffic in the other subnet for the same shared network stops. This is a limitation of the underlying perfdhcp tool that will be fixed in future Kea releases.
|
|
|
|
|
|
- Stork retrieves the information once per 10 seconds in its database. Unfortunately, the UI does not refresh itself yet and you need to press F5 or ctrl-R to reload the page to see. This will be fixed in Stork 0.6.
|
|
|
- Stork retrieves the information once per 10 seconds from its database. Unfortunately, the UI does not refresh itself yet and you need to press F5 or ctrl-R to reload the page to see. This will be fixed in Stork 0.6.
|
|
|
|
|
|
- The lease lifetimes have unnaturally short lifetimes of only 3 minutes.
|
|
|
- The lease lifetimes have unnaturally short lifetimes of only 3 minutes. Wait a little bit and they'll expire.
|
|
|
|
|
|
With a little bit of juggling around, you can see something like this:
|
|
|
|
... | ... | @@ -95,7 +95,7 @@ Click on Home and then Stork Kea DHCPv4 dashboard. You have plenty of statistics |
|
|
|
|
|
Stork 0.5 demo has a very rudimentary support for BIND statistics. We're currently using third party exporter and existing BIND dashboard.
|
|
|
|
|
|
On grafana interface, click `Home`, then `Import dashboard`, then type in 1666 into the Grafana.com dashboard id. Once the next import step pops up, make sure you change prometheus source to prometheus. (There's prometheus instance running in the demo, which is very eloquently called prometheus). Now you have two dashboards. One for Kea and another one for BIND.
|
|
|
On grafana interface, click `Home`, then `Import dashboard`, then type in 1666 into the Grafana.com dashboard id. Once the next import step pops up, make sure you change prometheus source to prometheus. (There's prometheus instance running in the demo, which is very eloquently named prometheus). Now you have two dashboards. One for Kea and another one for BIND.
|
|
|
|
|
|
15. **You can change your own password**.
|
|
|
|
... | ... | |