1 / 6

PCE Working Group Meeting IETF-67, November 2006, San Diego

PCE Working Group Meeting IETF-67, November 2006, San Diego. A set of monitoring tools for Path Computation Element based Architecture draft-vasseur-pce-monitoring-01.txt JP Vasseur ( jpv@cisco.com ). Quick overview.

marny-anderson
Download Presentation

PCE Working Group Meeting IETF-67, November 2006, San Diego

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. PCE Working Group MeetingIETF-67, November 2006, San Diego A set of monitoring tools for Path Computation Element based Architecture draft-vasseur-pce-monitoring-01.txt JP Vasseur (jpv@cisco.com) 67th IETF, San Diego, November 2006

  2. Quick overview • PCE Monitoring: WG item, • The need for OAM functions has been expressed at several occasions, • Main OAM features specified by this document: • Check of PCE’s liveness along a path computation chain (may be reduced to a single element) where the set of PCEs may or may not be specified by the PCC, • Performance metric collection (e.g. processing times, …) related to the PCE(s) involved in the path computation chain for a specific or a general request, • Standalone functionality or part of a path computation process. 67th IETF, San Diego, November 2006

  3. Quick overview • Monitoring functions can be activated *during* path computation request (PCReq/PCRep messages) or as part of a standalone request (newly defined PCEP messages) • New PCEP messages: PCMonReq and PCMonRep • New PCEP objects defined: • MONITORING (carried within PCMonReq/PCMonRep or PCReq/PCRep messages):Check, Record, General, Processing time, Incomplete, Monitoring-id-number, • PCE-ID (carried within PCMonReq/PCMonRep or PCReq/PCRep messages): used to record the PCE IP address • PROC-TIME (carried within PCMonRep/PCRep messages): (Estimated) Current/Min/Max/Average/Variance processing times 67th IETF, San Diego, November 2006

  4. Three use cases (example shown when the BRPC procedure is in use) PCRep message with (optionally) PCE-ID objects + PROC-TIME object PCMonRep message with (optionally) PCE-ID objects PCMonReq message with MONITORING (C=1), TE LSP attributes. PCReq message with MONITORING (C=1, P=1), TE LSP attributes. *PCE Area 2 Area 1 * ABR1 * ABR3 Example 1: check of the path computation chain liveness for TE LSP T1 (no path computation), path computation chain unknown PCE-ID optionally recorded B B * * ABR3 A ABR4 Area 0 Area 2 Area 1 * ABR1 * ABR3 Example 2: Path computation request + performance metric along the path computation chain. PCE-ID optionally recorded B B * * ABR3 A ABR4 Area 0 67th IETF, San Diego, November 2006

  5. Three use case (example shown when the BRPC procedure is in use) PCMonReq message with MONITORING (C=1), set of PCE-IDs specified PCMonRep message with (optionally) PCE-ID objects + PROC-TIME Example 3: performance metric gathering for a general request along a specific path computation chain (ABR1-ABR4) Area 2 Area 1 * ABR1 * ABR3 B B * * ABR3 A ABR4 Area 0 67th IETF, San Diego, November 2006

  6. Conclusion • Comments have been received on the list, new items to be covered in the next revision, details on procedures, • New metrics can easily be added in future revisions (e.g. Timestamping, queues states, …) without any change to the architecture • Is there a WG support for such functionality ? • WG ID ? 67th IETF, San Diego, November 2006

More Related