Rmon

1. Rmon

2. Diagram of RMON MIB Root ISO Org 1. Statistics DoD 2. History Internet 3. Alarm Mgmt Private 4. Hosts MIB 1 & 2 5. Host Top N RMON 6. Matrix MIB 1 7. Filter 8. Capture MIB 2 9. Event 10. Token Ring

3. RMON MIB Groups • Statistics - Traffic and error rates on a segment • History - Above statistics with a time stamp • Alarm - User defined threshold alarms on any RMON variable • Hosts - Traffic and error rates for each host by MAC address • Host Top N - Sorts hosts by top traffic and/or error rates • Matrix - Conversation matrix between hosts • Filter - Definition of what packet types to capture and store • Packet Capture - Creates a capture buffer on the probe that can be requested and decoded by the management application • Event - Generates log entries and/or SNMP traps • Token Ring - Token Ring extensions, most complex group

4. RMON Increases Management Capacity to 250% Distributed Techniques Save Time and Money Using RMON, Network Management Staff Can Provide Services to More Users and Segments Source: McConnell Consulting, Inc. 9/94 Survey of LAN Managers

5. Network Manager Needs More HelpClient / Server Revolution is Here • Mission critical client/server applications mean that network up-time and performance are required • Good information currently available for segment traffic, performance and utilization (RMON1) • End-to-end, global view of enterprise traffic is needed for troubleshooting today’s complex internetwork(RMON2) • Isolate cause of problem quickly and respond • Redeploy resources for optimal performance • Spot bandwidth utilization trends before bottlenecks occur

6. Remote Monitoring in the ISO ModelGoing Up-the-stack With RMON2 Application Presentation Session RMON2 Transport Network Data Link RMON Physical

7. Enterprise Network Traffic ManagementBenefits of Monitoring Protocols “Up-the-stack” • Understand network performance from an application perspective • Logical view of workgroup and application communication patterns • Clear visualization of end-to-end traffic • High-value enterprise traffic information results: • Improved performance through network tuning and optimal placement of network resources • Trend analysis based on actual growth rates • Accurate accounting data

8. IETF Responds: RMON2 Standard for Monitoring Higher Protocol Layers • RMON (1) accepted and implemented • RMON2 Working Group kicked off July 1994 • RMON2 Internet Draft delivered June 1995 • First RMON2 interoperability testing occurred in September 1996 • RMON2 received its RFC #s (2021, 2074) in January 1997 • Vendors can commence development of RMON2-compliant implementations immediately

9. What is RMON2? Standard for Monitoring Higher Protocol Layers • Major new capability: Provide statistics on network-and application-layer traffic • Open structure for collecting traffic data at higher protocol layers • Protocol directory critical aspect of the MIB • Additional enhancements: • Address Translation • User-defined histories • Probe configuration-device, modem and trap administration based on the Aspen MIB • Time sorted tables

10. 1. Statistics 11. Protocol Directory 2. History 12. Protocol Distribution 3. Alarm 13. Address Map 4. Hosts 14. Network-Layer Host 5. Host Top N 15. Network-Layer Matrix 6. Matrix 16. Application-Layer Host 7. Filter 17. Application-Layer Matrix 8. Capture 18. User History 9. Event 19. Probe Configuration 10. Token Ring 20. RMON Conformance Diagram of the RMON2 MIB Root RMON ISO Org RMON1 RMON2 DoD Internet Mgmt Private MIB 1&2 MIB 1 MIB 2

11. 11 12 13 14 15 16 17 18 19 20 RMON2 MIB Groups Protocol Directory - List of protocols the probe can monitor Protocol Distribution - Traffic statistics for each protocol Address Map - Maps network-layer to MAC-layer addresses Network-Layer Host - Traffic statistics to and from each discovered host Network-Layer Matrix - Traffic statistics on conversations between pairs of discovered hosts Application-Layer Host - Traffic statistics to and from each host by protocol providing insight into the use and growth of applications Application-Layer Matrix - Traffic statistics on conversations between pairs of hosts by protocol User History Collection - Periodic samples of user-specified variables Probe Configuration - Remote configuration of probe parameters RMON Conformance - Requirements for RMON2 MIB conformance

12. RMON2 Implementation Options Two Alternatives Balancing Price and Performance Network Layer Application Layer Statistics X X Hosts X X Matrix X X Matrix topN X X • “Type A” Implementations • Network layer traffic • Less memory and processor power • Expect to see embedded in hubs and switches • “Type B” Implementations • Application layer traffic • More memory and processor power • Basis for high-end traffic management applications

13. Impact of RMON2: Adding a Logical View to Management Products • Answers critical questions like: • What percent of WAN traffic is due to my order-entry application? • How fast is the Lotus Notes traffic growing? • How many hours does Fred spend on the web? • Requires new user-interface • Scaleable, end-to-end view of all traffic on network • Support range of logical groupings • Linked to other management applications • Essential for roll-out of client/server applications

14. Example RMON2 Solution: Transcend® Traffix™ Manager and SuperStack® II Enterprise Monitor

15. Tuning the Network to the Business • Comprehensive understanding of network traffic • Real-time and historical • Applications and protocols • Utilizing RMON2 data • Optimize the network to meet the needs of business applications • Speed troubleshooting at the enterprise network level, rather than the device or segment level • Set real policies for the business use of the network

16. System-level Management of Networked Apps • Top down view of all traffic on network • End-to-end display of conversations • Network-and application-layer traffic details • Designed and tested to scale to large, complex networks • Powerful, alternative logical groupings • Much more than “Protocol Domains” • Group by geography, function, subnet, VLAN, etc. • Easy-to-use navigation • Speeds troubleshooting • Global view to see interaction and scope • Zoom to problem hosts, devices, protocols • Launch detailed protocol analysis on any link

17. Communicate to Users and Management • Fully integrated traffic database • Real-time and historical information in all views • Histories over the past day, week, month, year, etc. • Trend analysis, comparison and graphing • Set thresholds on key parameters • Automated reporting • Key trends in application, network and device utilization • Easy report set-up from same view as GUI • Built-in, no data export/import required

18. Traffic Management is a New DisciplineBusiness ApplicationsTrafficInfrastructure • Brings together: • Application level monitoring • Enterprise-wide instrumentation • Ubiquitous standard • To achieve: • Analysis of applications’ use of infrastructure • Performance management as seen by users • Tuning, capacity planning, accounting, etc. based on business applications usage • System level troubleshooting • In the face of: • New network technologies (VLANs) • Unpredictable traffic trends

19. Mission: Enterprise Traffic ManagementBuild on Foundation of Infrastructure Management Business Objectives Quality of Service Efficiency Policies RMON2 Traffic Management Survival! MIB 2 RMON1 Infrastructure Management Troubleshooting Tuning and Planning

20. Physical - devices and segments Advantages: Enterprise Traffic ManagementNew Level of Network Knowledge and Capabilities Activity Infrastructure Management Traffic Management Concepts and Logical - traffic and applications Perspective Reflects organization , scope groups and Trouble Device control and Behavior of whole network configuration shooting Discriminate between application Physical connectivity problems and network problems Planning See effects on devices See causes, as well as effects “Purchase Order” planning Business planning based on real Tuning utilization and rate of growth Local utilization and rate of applications of growth at packet level Policies Standardize equipment Define “reasonable” use purchase Set use policies and enforce them

21. Results: Enterprise Traffic Management Improved Responses to Performance Problems Add Resources Traffic Policy Reconfigure Resources Year Trend/Report for Re-Design and Adding Resources Month Performance Assessment for Tuning and Optimization Days / Weeks Prioritize Network Use to Business Needs Hours / Minutes

22. Benefits: Enterprise Traffic ManagementMatch Network Investments to Business Objectives • Improve network performance, eliminate bottlenecks, so business applications run faster, more reliably • Find enterprise network system problems fast • Only invest due to business application growth • Don’t waste expensive network resource on “chat” traffic • Efficient distributed techniques bring the problem to the expert, rather than the expert to the problem • Ease-of-use means information can be handled by less skilled staff members