One unified fault management platform for the next generation DDI deployments.

Ensures the organizations's DDI availability and improves reliability.
Advanced Monitoring from TCPWave

When it comes to core DDI monitoring, the world‘s largest organizations turn towards TCPWave. With over 1490 REST API calls, the TCPWave IPAM stands apart in today‘s tech-savvy automation industry. TCPWave‘s customers need not purchase a separate add-on to monitor their DDI infrastructure. The TCPWave IPAM monitors the DDI ecosystem for thresholds, problems, security breaches, misconfigurations, overloaded data links, sluggish response times, etc. The anycast monitoring goes one step further with an insight into the backbone routing infrastructure. Leveraging the TCPWave IPAM, the customers can monitor the availability, uptime, and response time of every DDI remote on the network. The embedded reporting engine derives various valuable monitoring metrics so that the customer‘s DDI architects and engineers can quickly identify the alerting trends and take the appropriate corrective actions.

Monitoring for today‘s DevOps and NetOps

To ensure a smooth DDI availability and functionality, a few of the critical components need constant monitoring:

  • The DNS and DHCP network services on the remotes.
  • The transport layer communicates with the management layer.
  • The DNS and DHCP response times, availability, replication over the wide-area network.
  • Performance of the webserver and the response time of the webserver.

Today‘s mission-critical application infrastructure needs a monitoring framework to assimilate the core application synthetics combined with deep DDI visibility. To understand how mission-critical applications and end-users experience the applications, a robust monitoring engine with DDI as a focal point is required. The idea of a strong monitoring engine is to detect and alert various thresholds so that corrective action can be taken in a timely fashion. A prompt response taken by the DDI administrator is critical to the time taken to resolve a potential DDI outage. It is precisely what TCPWave delivers to its customers.


The TCPWave IPAM provides a DDI administrator with numerous screens to configure and monitor the thresholds. The monitoring engine does a systematic collection of the pre-defined and pre-configured thresholds. Some of the key performance indicators are also used in the performance charts.

If there is any mismatch in the configuration, the configuration policy checks alert the monitoring engine. The threshold breaches are transformed into notifications by the notifications engine. Properly worded alerts are embedded into the notifications engine so that an entry-level network operator can understand what to do. The alerts quickly correlate how the DDI performance and the network performance can impact the business transactions and the end-user experience.

Intuitive Monitoring Framework

The network administrators can visualize a robust monitoring framework using the DDI management user interface. The users have the privilege to filter and sort the alerts chronologically. A set of filters can be applied to the alerts so that the customer‘s network architects can perform event correlation analysis based on the sequence of events or alerts. The TCPWave monitoring framework has innovative intelligence embedded in it. For example, if a TCPWave DDI remote is set for scheduled maintenance, it would not flood the fault management systems with many redundant alerts. There will be one overall alert if the remote is not reachable over the network. Since the remote is powered off or isolated from the network, the system suppresses the application level alerts. The monitoring design goes one step further and provides customized alerting on specific alerts so that a set of application owners would know if the DDI infrastructure is causing a problem. For example, the SSL certificates management team can subscribe and get a specific notification when the web server certificate is due for renewal. The TCPWave CLI framework also provides a list of alerts and monitoring settings for a group of DDI devices or a single remote.

Monitoring where speed matters

At TCPWave, we understand that the end-user experience is critical to business performance. As organizations keep changing their network topologies, the overall control and the management of a seamless DDI infrastructure has a growing set of variables. The traditional applications that used to be present on-prem have changed their hosting platform to the cloud. In today‘s world, the employees access various applications from various remote locations. Therefore, the availability of the mission-critical DNS and DHCP services is critical for the employee‘s productivity. TCPWave‘s monitoring design considers these factors carefully.


The DDI remotes perform self-monitoring and report the statistics to the upstream monitoring engine that runs on the TCPWave IPAM. It constitutes the distributed self-monitoring model. The second model is in the opposite direction, where the DDI managers centrally check the DDI remotes for a different set of monitoring thresholds. This distributed monitoring model ensures that a single device is not overwhelmed to perform monitoring. The response time for the APIs to manage the DNS entries is highly critical to various cloud and container orchestrators.

The TCPWave IPAM performs monitoring while providing a millisecond response time to the provisioning ecosystem, comprising various cloud and container management systems. The fault management engineering combined with a correlation analysis done by the reporting engine is designed in the core TCPWave IPAM fabric to provide a 100% DDI SLA for your organization.