1 / 15

Flightcase IT Services Pvt. Ltd.

Flightcase offers managed IT Support Services, Network Monitoring Center, remote monitoring management, Telecom Management services and 24 / 7 Outsourced noc Services that helps industries for their business growth.<br>

Flightcase
Download Presentation

Flightcase IT Services Pvt. Ltd.

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Remote Network Monitoring

  2. Remote Network Monitoring • RMON is designed for “flow-based” monitoring, while SNMP • is often used for “device-based” management. • RMON is similar to other flow-based monitoring technologies such as NetFlow and SFlow because the data collected deals mainly with traffic patterns rather than the status of individual devices. • One disadvantage of this system is that remote devices shoulder more of the management burden and require more resources to do so. Some devices balance this trade-off by implementing only a subset of the RMON MIB groups (see below). A minimal RMON agent implementation could support only statistics, history, alarm, and event.

  3. Table of Contents • Basic Concepts • RMON Goals • RMON MIB Table Management • RMON MIB Groups • RMON2

  4. RMON Basic Concepts • Extends the SNMP functionality without changing the protocol • Allows the monitoring of remote networks (internetwork management) • MAC-layer (layer 2 in OSI) monitoring • Defines a Remote Monitoring (RMON) MIB that supplements MIB-II • with MIB-II, the manager can obtain information on individual devices only • with RMON MIB, the manager can obtain information on the LAN as a whole • called network monitors, analyzers or probes

  5. RMON Goals • Monitoring subnetwork-wide behavior • Reducing the burden on agents and managers • Continuous off-line monitoring in the presence of failures (in network or manager) • Proactive monitoring • perform some of the manager functions (e.g., diagnostics) • Problem detection and reporting • Provide value-added (analyzed) data • Support multiple managers

  6. Example Configuration for Remote Monitoring Management console with RMON probe Ethernet Central Site Router Router Local management console with RMON probe Router Router Ethernet PC with RMON probe FDDI backbone Bridge Router with RMON probe Ethernet Token Ring LAN PC with RMON probe

  7. agent a agent b agent c Subnetwork X Interface 1 RMON probe Interface 2 Subnetwork Y agent e agent d Example of RMON probe with two interfaces

  8. Control of Remote Monitors • RMON MIB contains features that support extensive control from NMS • Configuration control • Action Invocation • RMON MIB is organized into a number of functional groups • Each group may contain one or more control tables and one or more data tables • Control table (typically read-write)contains parameters that describe the data in a data table(typically read-only)

  9. Configuration Control • At configuration time, NMS sets the appropriate control parameters to configure the remote monitor to collect the desired data • the parameters are set by adding a new row to the control table or by modifying an existing row • a control table may contain objects that specify the source of data to be collected, the type of data, the collection timing, etc. • To modify or disable a particular data collection function: • it is necessary first to invalidate the control row • this causes the deletion of that row and the deletion of all associated rows in data tables • NMS can create a new control row with the modified parameters

  10. create Request under Creation Transitions of EntryStatus State non- existent valid invalid performed by manager performed by agent

  11. rmon (mib-2 16) statistics (1) history (2) alarm (3) host (4) hostTopN (5) matrix (6) filter (7) capture (8) event (9) tokenRing (10) RMON MIB

  12. RMON MIB2 • RMON MIB monitors MAC-level subnet traffic • RMON MIB2 can monitor traffic of packets at layers 3 to 7 of the OSI Reference Model • Provides Network-layer Visibility • can distinguish between local LAN and remote LAN traffic • Provides Application-layer Visibility • can analyze traffic to and from hosts for particular applications • can determine which applications are putting the load on the net • RMON MIB2 is basically an extension of RMON MIB

  13. rmon (mib-2 16) statistics (1) protocolDir (11) history (2) protocolDist (12) alarm (3) addressMap (13) host (4) nlHost (14) hostTopN (5) nlMatrix (15) matrix (6) alHost (16) filter (7) capture (8) alMatrix (17) event (9) usrHistory (18) tokenRing (10) probeConfig (19) RMON 2 RMON 1 RMON MIB2

  14. Summary • RMON extends the SNMP functionality without changing the protocol • RMON can monitor information on a whole subnetwork • RMON is used extensively in analyzing network traffic for problem detection and network planning • RMON2 can be used to analyze network traffic more accurately even to the application level

  15. Thank You!! Presented By Flightcase IT Services Pvt. Ltd. For more details: Email - info@fltcase.com Phone No. - (817) 350-6011

More Related