An important point about managed networks is the definition of the boundary. This is the point outside of which the NMS has no jurisdiction. NNM must have some idea about this in order to avoid trying to discover nodes unnecessarily. This can arise when a given network is connected to the Internet and the operator wants discovery to stop its data collection at the last node before the Internet. The network boundary problem is also seen in multiservice networks that contain numerous clouds of different technologies, including:
As for the Internet case, this may require careful administrative actions, such as specifying a seed file in NNM. In essence, this sets a boundary address for management beyond which it is not permitted (or meaningful) to operate . One last point about this is that even when the boundary has been carefully and correctly designated, the traffic introduced by network management may be too high. [1] In this case, it is important to be able to pace the management operations to suit the available bandwidth.
|