Clearly then, service providers need a more effective, manageable approach to tracking equipment and facilities in their networks if they seek to reduce their operating and capital expenditures while extending market share.
Network Discovery -
Finding the Right Solution
Network discovery engines are gradually going mainstream, for all the reasons explained above. But what constitutes a good discovery engine? That is, what characterizes an engine that provides relevant and accurate data to an inventory database reconciliation process in a way that meets the operational needs of the service provider?
The following are key characteristics that differentiate true network discovery solutions from the pretenders.
1. True Discovery, not “Give-Me-Data-and-I’ll-Confirm”. Some discovery solutions offer good reconciliation capabilities but in truth require the network operator to provide the majority of IP or OSI addresses in the network before checking the accuracy of data provided and digging deeper for lower level attributes. A true network discovery engine takes in some minimal data (e.g, gateway node addresses) and discovers the physical and logical attributes of the network.
2. Multi-technology, multi-vendor capability. A handful of network discovery engines work well within some areas of the network, such as IP networks, but fall short when it comes to the optical network layer, for example. Others only discover next generation networking equipment in optical networks, dismissing more than 75 percent of deployed legacy networks (especially in the optical layer, where older vintages don’t provide data on relationships with neighboring nodes). A good discovery engine offers the capability to cover most of the deployed network that the service provider is looking to discover and track.
3. Scalability and Robustness. Enterprise-level solutions do not adequately meet the needs of Tier 1 carriers for scalability (with tens of thousands of network devices) and robustness. Most discovery engines built specifically for carrier networks handle this requirement quite well, with tiered architectures and server redundancies enabling load-balancing, etc., to maximize availability and prevent failures.
4. Leverage Existing Standards, but Look for Flexibility Foremost. Standards are important – but the reality is very few are universally adopted by all service providers. Therefore, a network operator needs to consider whether its chosen discovery engine supports the interfaces it has implemented. For example, if a TMF814 or MTOSI interface has been