Infrastructure networks
Group your servers by IP address range: automatically detected networks, manual creation, overlaps and archives
Infrastructure networks group your servers by IP address range. This structures your infrastructure map by bringing together the machines that share the same range. You find them under Infrastructure › Network.
Automatically detected networks
Kabeen links each server to the network of its main interface, based on its IP address:
- for a server reported by the server agent, Kabeen looks for the network that exactly matches the range (address and mask) reported by the agent;
- for a server added manually, Kabeen looks for the most specific network that contains its IP address. Public IP addresses are not linked to any network.
If no network matches, Kabeen creates one automatically and names it after its address range, for example 10.0.0.0/24. For a server added manually, whose mask is unknown, the network created is a /24 range.
An automatically detected network is managed like any other: you can rename it, give it a description and a role (it has none when it is created and shows "Not defined"). However, its addressing (address and mask) is read-only: "The addressing of an automatically detected network cannot be changed."
In a server's details, the network of the main interface follows its IP address. For a server reported by the agent, this link cannot be changed by hand.
Creating a network manually
You can also declare a network yourself, for example for the address range allocated to you:
- Open Infrastructure › Network, then choose Add a network.
- Fill in the Network name, the range's IP address and its Subnet mask, in CIDR notation (for example
/24or/29). - Choose a Role if needed and add a Description.
The servers in this range that were not yet linked to any network join it.
An address range cannot overlap another network's range, including an archived network. If it does, Kabeen refuses to save it and shows "This address range overlaps an existing network. Change the address or the mask." Hovering the information icon lists the networks involved.
Flagged overlaps
Networks whose ranges overlap can still exist, for example if they were created before this rule. Kabeen flags them with a "This network overlaps:" badge, followed by the list of networks involved, both in the network list and in their details.
To fix an overlap, change the address or the mask of the manually added network, or archive the duplicate network.
Archiving a network
A network is no longer deleted directly: it is archived. An archived network leaves the list but remains available in the archives, where you can restore it or delete it permanently.
- In the network's details, open the menu and choose Archive the network. The details then show the Archived badge; the same entry becomes Unarchive the network.
- To find archived networks, open the ⋮ menu of the network list, then Archives. Each network is listed with its address and its origin (Detected automatically or Added manually). The Search a network field filters the list.
- From the archives:
- Restore puts the network back in the list;
- Delete, then Delete permanently, erases the network and all its links. This cannot be undone.
An automatically detected network that is archived still receives the servers of its range, so it is not created again by later detections. If it is deleted permanently, it comes back to your inventory as soon as one of its servers is detected again.
Archiving, restoring and deleting a network require the Delete permission on the Networks resource (see Roles and permissions).
Why it matters
Grouping the servers of the same range structures your infrastructure map. A network's details show the routing devices linked to it and the servers it hosts, each opening with a click.