... | ... | @@ -41,9 +41,9 @@ Since you're logged in as super-admin, you can see the `Configuration` menu and |
|
|
|
|
|
### 4. Add new Kea machine to monitor
|
|
|
|
|
|
Go to `Services`->`Machines` and switch to `Unauthorized` machines view (top-right corner). Now click the action button in `agent-kea` machine and then click `Authorize` in the menu. And then switch back to `Authorized` machines.
|
|
|
Go to `Services`->`Machines` and switch to `Unauthorized` machines view (top-right corner). Now click the action button in `agent-kea` machine and then click `Authorize` in the menu. And then switch back to `Authorized` machines.
|
|
|
|
|
|
In the demo, there are several docker containers simulating machines with Kea and BIND in various modes of operation. `agent-kea` is the name of one of such containers. Note that you didn't specify what kind of software is running on the `agent-kea` machine. Stork server connected to the stork agent running there and the agent looked for Kea and BIND 9 and found only DHCPv4 deamon and Control Agent (CA) of Kea.
|
|
|
In the demo, there are several docker containers simulating machines with Kea and BIND in various modes of operation. `agent-kea` is the name of one of such containers. Note that you didn't specify what kind of software is running on the `agent-kea` machine. Stork server connected to the stork agent running there and the agent looked for Kea and BIND 9 and found only DHCPv4 daemon and Control Agent (CA) of Kea.
|
|
|
|
|
|
Kea is being shipped with CA (Control Agent) preconfigured with control sockets for DHCPv4, DHCPv6 and DDNS. This simplifies deployment. In this particular Kea deployment only DHCPv4 daemon is installed. CA tries to connect to all of those daemons and continues with only those that respond. That makes it easy to deploy daemons selectively. However, Stork looks at the CA config and determines that there are 3 daemons expected, but only DHCPv4 is running. The other ones are greyed out and on their tab there is information that Stork agent cannot communicate with them. As this is the initial situation Stork concludes that this is as expected and switches off monitoring of these daemons, only DHCPv4 is monitored and its status is green.
|
|
|
|
... | ... | @@ -103,7 +103,7 @@ To restart Kea, use the following command: |
|
|
|
|
|
You can now logout from the docker image using `exit` or by pressing ctrl-d.
|
|
|
|
|
|
The
|
|
|
The
|
|
|
|
|
|
### 7. DHCPv6 support
|
|
|
|
... | ... | |