In order to monitor the traffic passing through your network, you need a Monitoring Point deployed and connected to the switch port you want to monitor. Once this is done, all you need to do is to identify local subnets prior to monitoring.
- A Monitoring Point must be set up and cabled for Usage monitoring. In particular, the Monitoring Point’s Primary Usage monitoring port must be physically connected to the switch port being monitored.
- The Monitoring Point location must be set.
Identify local subnets
In order for APM to be able to distinguish between inbound and outbound traffic, you need to identify the subnets local to the Monitoring Point. Configuring traffic direction also enables you to resolve hostnames on local subnets. By default, hostnames are resolved every time a Usage monitoring page is loaded. Configuring traffic direction ensures that IP addresses in local subnets are resolved at the time flow records are generated, and that that information preserved for the duration of Usage monitoring history. Addresses in external subnets will continue to be resolved in real-time.
To specify local subnets:
- Navigate to Usage > Monitoring Points.
- For the Monitoring Point interface you want to configure, click the icon.
- In the Configure dropdown, select Traffic Direction.
- In the IP Address and Netmask fields, enter a local subnet (e.g., 172.16.123.0) and associated subnet mask (e.g., 255.255.255.0).
- Click to add any additional local subnets.
- Click Apply before selecting any other configuration option (e.g., Alert Profiles).
Possible next steps include:
- To start Usage monitoring, see Start Usage Monitoring.
- To set up alerts to detect when various traffic flow characteristics are outside of acceptable limits, see Usage Alerts.
- To identify application flows that are not already identified by APM, see Custom Applications.
- To configure your Monitoring Point to monitor from a secondary Usage monitoring port or ports, see Usage Monitoring Ports