1 / 8

NVO3 Fault Management

NVO3 Fault Management. draft-tissa-nvo3-oam-fm-00 March 2014 London. Based on architecture and framework of IEEE 802.1 CFM (Continuity Fault Management) Where applicable same opcodes and TLVs as CFM are utilized Has the following abilities: Fault verification and isolation

may
Download Presentation

NVO3 Fault Management

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. NVO3 Fault Management draft-tissa-nvo3-oam-fm-00 March 2014 London

  2. Based on architecture and framework of IEEE 802.1 CFM (Continuity Fault Management) • Where applicable same opcodes and TLVs as CFM are utilized • Has the following abilities: • Fault verification and isolation • Connectivity monitoring and detection of cross connect errors • Performance and Loss measurement • Accommodate operational hierarchy (domain levels) • Nested OAM Highlights

  3. Transport Header O- OAM F- payload fragmentpresent NVO3 Shim O F 96 byte fixed size optional payload. Use cases coming up Optional Payload fragment EthType 0x8902 OAM Packet OAM Message

  4. draft-ietf-nvo3-dataplane-requirements-02 • Section 3.2.2 – L2VNI and L3VNI can be nested • Payload fragment facilitate path selection at boundary nodes for OAM packets L3VNI L2 VNI NVE NVE Applicability of Payload fragment

  5. draft-ietf-nvo3-dataplane-requirements-02 • Section 3.6 – Introduces concept of Hierarchical NVE for NVO3, • MD-LEVEL allows OAM messages to be restricted to the scope. NVE NVE MD-LEVEL - 4 NVE NVE NVE NVE Applicability of MD-Level MD-L =1 packets are dropped MD-L > 1 are forwarded MD-LEVEL - 1

  6. Draft-ietf-nvo3-overlay-problem-statement-04 • Need isolation between tenant traffic • Most often leaking between tenant traffic happens due to miss configuration or equipment or software defects • CCM (Continuity Check Message) provides cross connect error detection • Cross connect error raises notification Applicability of CCM

  7. Nested MP Interaction NVE TS TS NVE Router customer MD Level 0 … 7 NVO3 MD Level 0 … 7 Underlay MD Level 0…7 MD Level 0…7 Link MD Levels MEP for UnderLay MIP overlay in case of hierarchical Or nested VNI MEP for Overlay MIP for underlay MEP for Link Level

  8. Wider review and comments • Suggestions on additional NVO3 specific extensions ? Next steps

More Related