After entering the NPM configuration page, a Default Default network is displayed by Default, and all newly added monitoring nodes are added here by Default. However, if there are many sites in our network architecture, it is not convenient to determine the link errors between sites if we concentrate on one network. Next, we will re-plan the network based on the site.
Take "mail server" as an example. Click the Add network button. A network configuration item appears in the right-side window. Name the network in the network name, and then select the IP subnet to be added to the network, click ADD. The purpose here is to add all subnets of all mail servers to the newly created network container.
Then, add the Active Directory and the network site of the monitoring server in the same way.
After adding the network, enter the monitor configuration interface. Like the network, the monitor is also a default rule that automatically monitors all added networks. Click Add rule to create a monitoring path between networks.
Create a monitoring rule from the monitoring server site to the mail server site. Select the corresponding network site for the Monitor. As shown in the following figure, select all subnet connectivity monitoring between the monitoring server site and the mail server. You can customize the latency and packet loss rate. By default, machine learning in the cloud automatically detects changes.
Add exception, that is, add exception, you can select the subnet in the current network to exclude.
After creating the rule, return to the network performance Monitor Dashboard. The following figure shows the normal dashboard.
This article is forwarded from Li Xun 51CTO blog, original link: http://blog.51cto.com/lixun/1842382 , if you need to reprint, please contact the original author.