|IPAM Event||Automatic Monitoring Threshold|
|IPAM is initially provisioned for the first time.||IPAM monitors the CPU, Memory, Disk, TCPWave Message Service communication from IPAM to remotes, database health, web page availability and response time, license usage, user lockouts, foreign authentication availability, core processes, vulnerability checks and hardware components.|
|A new Master/Slave DNS appliance is added||IPAM monitors for CPU, Memory, Disk, TCPWave Message Service, BIND/Yadifa functionality, vulnerability checks and hardware components such as Temperature, RAID health, power supply status etc.|
|A new DNS zone is added||IPAM monitors the zone availability on each master and slave. It also checks for the response time and trends it via an advanced charting framework.|
|A new DNS caching appliance is added||IPAM monitors for CPU, Memory, Disk, TCPWave Message Service, BIND/Unbound functionality, BGP/OSPF route advertisement, vulnerability checks and hardware components such as Temperature, RAID health, power supply status etc|
|A new DHCP scope is added.||IPAM monitors the scope and alerts when the scope is exceeding a pre-defined usage threshold.|
|A new DHCP appliance is added.||IPAM monitors the CPU, Memory, Disk, TCPWave Message Service, DHCP functionality, response time, vulnerability checks and hardware components.|
TCPWave customers can also choose to have all the three providers listed above to provide cloud DNS hosting for every DNS zone managed by TCPWave IPAM. DNS Zones created in the TCPWave IPAM support Zone Mirroring with Amazon’s Route 53 DNS, Rackspace DNS and Google DNS. DNS records added to the TCPWave IPAM are automatically synchronized with the cloud providers listed above using TCPWave’s powerful RestAPI methods. The management communication uses encrypted SSL thereby preventing man in the middle attacks. Contact us to schedule a demo.