We recommend deploying one monitoring point at each location you want to monitor. A typical recommendation would be:
- Branch offices and Headquarters
- m35 (includes WiFi interface)
- Alternative - r45 (higher capacity monitoring point) if volumes/needs dictate this
- For example, the r45 has two Usage monitoring ports.
- Alternative - v35 (virtual monitoring point) if needs dictate this
- Data center
- Alternative - r400 (10 Gbps capable monitoring point) if >1 Gbps required
- s35 (software sequencer)
- For customers hosting cloud-based applications (for example, on AWS or Azure), we recommend deploying an s35 in each region or application environment. This allows bi-directional testing between user locations and the hosted platform.
- s35 (software sequencer)
See the Monitoring Point Comparison page for a detailed feature comparison.
Considerations for monitoring point placement
Within a given location, we recommend deploying “as close to the network core as possible”. Considerations include:
- General - Deploy behind the firewall.
- Deploying behind the firewall provides a more accurate picture of what users are experiencing.
- Usage monitoring - Deploy at an aggregation point.
- Typically at a gateway or a VLAN trunk.
- This allows you to monitor traffic from as many users and applications as possible.
- Usage monitoring - Deploy downstream of network address translation (NAT).
- This allows you to see private IP addresses rather than public IP addresses.
- This is helpful when you need to know which user is connected to a particular application or is using an excessive amount of bandwidth.
- Experience monitoring - Deploy as you would deploy a typical user.
- You want your monitoring results to mimic those of a user so the closer the network environment you deploy in is to that of the user (for example, same physical location, same subnet, same VLAN if applicable, same QoS characteristics if applicable, etc.) the more closely your results will be to what the user is experiencing.
- Delivery monitoring - Deploy such that you can monitor end-to-end from the user to an application.
- We recommend deploying at an aggregation point - typically at a gateway or a VLAN trunk.
- From there, create network paths to one or more WAN targets and to one or more LAN targets (users), depending on what you wish to monitor.
- Delivery and Experience monitoring - Deploy in the core (data center) as well as at user sites.
- This provides another point of reference for network and application performance monitoring. It allows you to create dual-ended paths to test WAN connectivity between the data center and user locations (Delivery monitoring). It also allows you to compare application performance from the data center with that from user locations (Experience monitoring).