How to correctly configure network interfaces on the monitoring server and similar services?

Question

linux

The essence of the question is this, there is a network in some way divided into segments, for example, using vlan, different addressing is different in different vlans, and now devices located in these subnets and vlans do not see each other. I have an assumption that this is not entirely correct. creates a lot of problems, for example, there is a service for monitoring or collecting logs, it turns out that you need to start a dozen interfaces on it. The same with authorization (ladp, radius), dns, ntp. What can I read or how to change the scheme of work with the network? The network of a small Internet provider, specifically, I do not deal with the networks themselves and there is not enough knowledge on the architecture of such networks. The same is generally true for the issue of network management, it seems to me not quite right to set up a dozen vlans on engineers' computers.

Answer 1

start a dozen interfaces

Believe me, setting up another subinterface on the server is much easier and safer than debugging some tricky network trouble. In addition, these subinterfaces for each VLAN will still be created somewhere else, well, not on the server, but on the router.
And what's stopping you from doing it now? Can't choose IP addressing and set up static routing? In any case, it is not problematic to leave at least 1k subinterfaces on the server, but it is better to remove all vlans from employees' computers, allocate a network and VLAN "for employees" to them, and configure routing on some router. I would do it on some L3 switch.