This high-level view differs from the original Rmon standard. Rmon probes and agents embedded in internetworking gear focus on low-level activity within individual LAN segments. Most internetworking devices come with embedded Rmon capability, but tracking usage and application traffic demands a lot more processing power and memory. Adding Rmon2 functions to an internetworking device can interfere with its normal work. Network overload Watch out for the desire to gather too much information too often.
Voluminous data can swell bandwidth demand.
And condense data or filter out the most significant changes before sending it across expensive WAN connections. Probe placement Rmon monitoring requires a probe or embedded agent for every segment, while Rmon2 monitoring requires only a few probes to examine traffic across the network. That's good because probes are pricey. Place one between the server and users or at key gateway points. Interoperability is slow coming from Rmon2 vendors.