David Harrington wrote:
In SNMPv3, we developed an identifier to identify each engine, but users actually prefer to model the network topology using the IP address, because when dealing with topology maps the purpose is tomanage the devices in the network.
With this whole identity stuff, people have to change their thinking and start thinking outside the box (buzzzzzzzzzzzzzzzzz-word :)
IP is great for talking from A to B. Once A and B where hosts, now they generally are virtual hosts, or even only a service.
As such the "IP" here is a reasonable ID, as it represents the service.
If a device catches fire, you don't want to search through diagrams of virtual services; you want to know where the device is so you can put the fire out. ;-) As Juergen said, which identifier works best depends on what you are trying to do, and no single identifier will always be the best choice.
It always depends on what you want to do, I fully agree, but for your example the "SNMP service" you will be looking at are 2 services:
- cpu load, memory usage etc, on the virtual device => this is "SNMP service on vhost X" - temperature, harddisk status etc on the physical host => this is "SNMP service on physical host Y" Those are two different services, not one, but two, and probably more.Most very likely vhost X has a different IP from host Y, thus using IP's here is one way to go. The problem comes when the IP changes, your service is still the same, but you based your ID on something which is not a stable identifier.
This is of course also all a similar problem with Multihoming and Mobility etc. One day you are IP X the other moment you are IP Z.
The real way to solve this is the Identity layer, and HIP provides just that.
Greets, Jeroen
Attachment:
signature.asc
Description: OpenPGP digital signature