1 / 32

Transport Performance Metric MIB

Transport Performance Metric MIB. draft-ietf-rmonmib-tpm-mib-01.txt Russell Dietz rdietz@hifn.com RMONMIB Working Group 49 th IETF – San Diego, CA 2000. Work Request. Client. Server. Work Result. ?. Application Performance…. Work Request. Sub Request. Sub Request. Sub Request.

fabian
Télécharger la présentation

Transport Performance Metric MIB

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. Transport Performance Metric MIB draft-ietf-rmonmib-tpm-mib-01.txt Russell Dietzrdietz@hifn.com RMONMIB Working Group49th IETF – San Diego, CA 2000

  2. Work Request Client Server Work Result ? Application Performance… RMONMIB WG - 49th IETF San Diego, CA 2000

  3. Work Request Sub Request Sub Request Sub Request Sub Request Sub Result Sub Result Client Server Sub Result Sub Result Work Result ? Why transport metrics? Trouble- shooting RMONMIB WG - 49th IETF San Diego, CA 2000

  4. HTTP Connect *form*.jdbc-sybase *order-entry *finish *form*.jdbc-sybase re-directed finish-ack Client Server entry-ack form graphic HTTP ACK Web (HTTP) Example RMONMIB WG - 49th IETF San Diego, CA 2000

  5. H.323 Connect Q.931 (Set) H.245 (start) H.245 (alive) H.245 (alive) rtsp (audio) rtsp (video) Client Server H.245 (video) Q.931 (H.245) H.323 (Q.931) NetMeeting (H.323) Example RMONMIB WG - 49th IETF San Diego, CA 2000

  6. Jitter Exchange Response Application Response Connection Connection Sequence Connection Window Routing Categories of Metrics RMONMIB WG - 49th IETF San Diego, CA 2000

  7. Jitter Metrics • Message Jitter… • starts with the abstraction of a communicated message… a sequence of adjacent data packets transferred in a given direction, concluded by the transfer of one or more adjacent data packets in the other direction. • measures the inter-packet gaps only for data packets within messages. It does not measure the gaps between the messages themselves. RMONMIB WG - 49th IETF San Diego, CA 2000

  8. Message Jitter… • example, an application that is downloading a series of large graphics. The client first requests a graphic file download from the server. The server then sends the graphic to the client. The client then requests the next graphic, and so on. Within each download, the observed inter-packet gaps are of interest. The inter-packet gap from the last packet of one download and the first packet of the next is of less interest These later gaps are excluded. RMONMIB WG - 49th IETF San Diego, CA 2000

  9. Metric Units Description N Inter-Packet Gaps Count of the # of Inter-Packet Gaps measured for Data from the Client to the Server (x) uSec Sum total of the Delta Times in these Inter-Packet Gaps (X2) uSec2 Sum total of the Delta Timessquared in these Inter-Packet Gaps Xmax uSec The maximum Delta Time of Inter-Packet Gaps measured Xmin uSec The minimum Delta Time of Inter-Packet Gaps measured. (IX) Sum total of the data point # times the Delta Timesin these Inter-Packet Gaps Message Jitter RMONMIB WG - 49th IETF San Diego, CA 2000

  10. Jitter Metrics • Stream Jitter… • does not include message considerations. Rather, measures the inter-packet gaps for all packets of the data stream for a given transfer direction. RMONMIB WG - 49th IETF San Diego, CA 2000

  11. Stream Jitter… • example is where an H.323 Voice-over-IP (VoIP) data-stream is transferring an audio data-stream over RTP from one end-point to another. In this case, all inter-packets gaps observed would be of interest. RMONMIB WG - 49th IETF San Diego, CA 2000

  12. Metric Units Description N Inter-Packet Gaps Count of the # of Inter-Packet Gaps measured for Data from the Client to the Server (x) uSec Sum total of the Delta Times in these Inter-Packet Gaps (X2) uSec2 Sum total of the Delta Timessquared in these Inter-Packet Gaps Xmax uSec The maximum Delta Time of Inter-Packet Gaps measured Xmin uSec The minimum Delta Time of Inter-Packet Gaps measured. (IX) Sum total of the data point # times the Delta Timesin these Inter-Packet Gaps Stream Jitter RMONMIB WG - 49th IETF San Diego, CA 2000

  13. H.323 Connect Q.931 (Set) H.245 (start) H.245 (alive) H.245 (alive) rtsp (audio) rtsp (video) Client Server H.245 (video) Q.931 (H.245) H.323 (Q.931) H.323 – Stream Jitter Stream Jitter RMONMIB WG - 49th IETF San Diego, CA 2000

  14. Response Metrics • Exchange Responses… • starts with the abstraction of a communicated exchange-message. An exchange-message is considered to start with a series of adjacent data packets transferred in a given direction (exchange message request). The end of such a message is defined to be the transfer of one or more adjacent data packets in the other direction (exchange message response). Matters of sequencing or retransmission (duplicate) detection are excluded from consideration in the analysis of data packets when observing exchange-message related packets. RMONMIB WG - 49th IETF San Diego, CA 2000

  15. Exchange Response Example RMONMIB WG - 49th IETF San Diego, CA 2000

  16. Metric Units Description N Client-> Svr Exchange Msg Requests Count of # Client<->Server request/response pairs measured for exchange messages from the Client to the Server  mSec Sum total of the Start-to-Start Delta Times in these Exchange Response Times (x2) mSec2 Sum squared total of the Start-to-StartDelta Times in these Exchange Response Times Xmax mSec The maximum Start-to-Start Delta Time of these Exchange Response Times Xmin mSec The minimum Start-to-Start Delta Time of these Exchange Response Times (IX) Sum total of the data point # times the Start-to-Start Delta Time Exchange Response Start to Start RMONMIB WG - 49th IETF San Diego, CA 2000

  17. HTTP Connect *form*.jdbc-sybase *order-entry *finish *form*.jdbc-sybase re-directed finish-ack Client Server entry-ack form graphic HTTP ACK HTTP – Exchange Response Exchange Response RMONMIB WG - 49th IETF San Diego, CA 2000

  18. Application Response Example RMONMIB WG - 49th IETF San Diego, CA 2000

  19. Metric Units Description N Client->Svr Application Message Requests Count of the # Client->Server request/response pairsmeasured for application message from the Client to the Server  mSec Sum total of the Start-to-Start Delta Times in these Application Response Times (x2) mSec2 Sum squared total of the Start-to-Start Delta Times in these Application Response Times Xmax mSec The maximum Start-to-Start Delta Time of these Application Response Times Xmin mSec The minimum Start-to-Start Delta Time of these Application Response Times (IX) Sum total of the data point # times the Start-to-Start Delta Time Application Response Start to Start RMONMIB WG - 49th IETF San Diego, CA 2000

  20. HTTP Connect *form*.jdbc-sybase *order-entry *finish *form*.jdbc-sybase re-directed finish-ack Client Server entry-ack form graphic HTTP ACK HTTP – Application Response Application Response RMONMIB WG - 49th IETF San Diego, CA 2000

  21. Jitter Exchange Response Application Response Connection Connection Sequence Connection Window Routing More Metrics… RMONMIB WG - 49th IETF San Diego, CA 2000

  22. TPM MIB – Changes in 01 • Basic edits for minor corrections • Removal of some ‘statistics’ for complete ‘reports’ • Usage of xxxClientID in place of xxxClientServerAddress RMONMIB WG - 49th IETF San Diego, CA 2000

  23. Aggregation Aggregation APM – Overall Framework Flow Micro-flow APM Study TPM Study RMONMIB WG - 49th IETF San Diego, CA 2000

  24. TPM MIB - Framework • APM MIB used to determine application flows/aggregations to report micro-flows in TPM report table. • TPM Controls used to create performance metric reports on flows/aggregations. • All reports are in the form of statistics • Drill-down for performance anomalies RMONMIB WG - 49th IETF San Diego, CA 2000

  25. TPM MIB Tables • tpmReportControlTable - Study Control • tpmMetricTable - Metric Selection • tpmReportTable - Detail Reports • tpmCurrentTable - Current Aggregations • tpmExceptionTable - Exception Reports RMONMIB WG - 49th IETF San Diego, CA 2000

  26. APM/TPM Report Table Linkage apmReportControl – N tpmReportControl – N apmReportControlIndex - N apmReportEntry – N, r tpmReportEntry – N, r, m, f..n apmReportIndex - r tpmReportEntry – N, r, m+1, f..n apmReportEntry – N, r+1 tpmReportEntry – N, r+1, m, f..n apmReportIndex - r+1 tpmReportEntry – N, r+1, m+1, f..n RMONMIB WG - 49th IETF San Diego, CA 2000

  27. APM/TPM Current Table Links apmReportControl – N tpmReportControl – N apmReportControlIndex - N apmCurrentEntry – N, t tpmCurrentEntry – N, t, m, f..n apmTransactionID - t tpmCurrentEntry – N, t, m+1, f..n apmCurrentEntry – N, t..n tpmCurrentEntry – N, t..n, m, f..n apmTransationID – t..n tpmCurrentEntry – N, t..n, m+1, f..n RMONMIB WG - 49th IETF San Diego, CA 2000

  28. APM/TPM Exception Table Links apmExceptionTable – E tpmExceptionControl – E apmExceptionIndex - E apmTransaction Responsiveness Notification – E apmTransactionID - t tpmExceptionReportEntry – E, t, m, f..n tpmExceptionReportEntry – E, t, m+1, f..n apmTransaction Unsuccessful Notification – E tpmExceptionReportEntry – E, t+1, m. f..n apmTransactionID – t+1 tpmExceptionReportEntry – E, t+1, m+1, f..n RMONMIB WG - 49th IETF San Diego, CA 2000

  29. APM/TPM – Micro-flows • tpmReportTable • tpmReportControlIndex • protocolLocalDirIndex – Application (micro) • protocolLocalDirIndex – Network • tpmReportServerAddress • tpmReportClientID • tpmReportMetricIndex – Metric and Protocol • tpmCurrentApmTransactionID RMONMIB WG - 49th IETF San Diego, CA 2000

  30. APM/TPM Micro-flows RMONMIB WG - 49th IETF San Diego, CA 2000

  31. Updates in process • Enhance ‘linkage’ with APM features for additional ‘drill-down’ • Integration of metrics from PMCAPS • Integration of metric selection • Document describing usage of metrics for specific application groupings RMONMIB WG - 49th IETF San Diego, CA 2000

  32. Transport Performance Metric MIB draft-ietf-rmonmib-tpm-mib-01.txt Russell Dietzrdietz@hifn.com RMONMIB Working Group49th IETF – San Diego, CA 2000

More Related