All-
We've been using zabbix 2.x for a few months now, and the more I learn about it the happier I am with its functionality.
I didn't think we would ever make use of maps, but I started playing with making one yesterday afternoon and now I think it would be really useful for us.
I would like to map out our network, including the links between our three datacenters, but I'm struggling with how I should represent our core network devices that have multiple interfaces. It's possible that there's an obvious answer to this and I've just missed. As I said, I'm just getting started with maps.
We have multiple core network devices, let's call them "Core A", "Core B", and "Core C". Each of those devices has multiple interfaces. Since a host only has one visible name and there's no way to assign aliases to a particular interface (e.g. "Core A link to Core B"), what are others doing to represent these type of core network devices in maps, so that the we can correctly display and label each of the links that fan out from a particular core device to other components of the core and the network.
I was considering defining a distinct host for each interface that's part of each core device ("Core A link to Core B", "Core A link to Core C", etc.) and then using some kind of a sub-map to represent all of Core A, but that seems messy. Is there a better way that I've missed?
Thanks,
Tim
We've been using zabbix 2.x for a few months now, and the more I learn about it the happier I am with its functionality.
I didn't think we would ever make use of maps, but I started playing with making one yesterday afternoon and now I think it would be really useful for us.
I would like to map out our network, including the links between our three datacenters, but I'm struggling with how I should represent our core network devices that have multiple interfaces. It's possible that there's an obvious answer to this and I've just missed. As I said, I'm just getting started with maps.
We have multiple core network devices, let's call them "Core A", "Core B", and "Core C". Each of those devices has multiple interfaces. Since a host only has one visible name and there's no way to assign aliases to a particular interface (e.g. "Core A link to Core B"), what are others doing to represent these type of core network devices in maps, so that the we can correctly display and label each of the links that fan out from a particular core device to other components of the core and the network.
I was considering defining a distinct host for each interface that's part of each core device ("Core A link to Core B", "Core A link to Core C", etc.) and then using some kind of a sub-map to represent all of Core A, but that seems messy. Is there a better way that I've missed?
Thanks,
Tim