1 / 11

TRILL OAM

TRILL OAM. Tissa Senevirathne 87 th IETF, Berlin Germany 2013. Requirements document is now RFC 6905 Framework document cleared WG last call. Fault management document is a WG document -01 of Performance management document published -00 of OAM MIB document available for review

hina
Télécharger la présentation

TRILL OAM

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. TRILL OAM Tissa Senevirathne 87th IETF, Berlin Germany 2013

  2. Requirements document is now RFC 6905 • Framework document cleared WG last call. • Fault management document is a WG document • -01 of Performance management document published • -00 of OAM MIB document available for review • We are behind on advertised (Vancouver) timelines for Fault-management document Updates

  3. Fault management document • MIB • Performance Management • Next steps Agenda

  4. Fault Management

  5. Added based on the review comments • IEEE CFM is flexible and extensible • Does not have out of the box, default operations mode • Base Mode provide out of the box, default mode, where all RBridges are members of a default Maintenance Association. • Virtual MEP is at the CPU • Allow to use Ping to test liveliness, • Trace route to test reachability • Can not be used to isolate faults to port level TRILL OAM Base Mode

  6. MEPID: RB-nickname MA Domain Name: TrillBaseMode MA Name : 65532 (0xFFFC) MD Level : 3 TRILL Base Mode Please refer to appendix B: draft-ietf-trill-oam-fm

  7. CCM was originally designed for single path 802.1 bridged networks • CCM uses a single RDI flag to denote failure to receive CCM probes. • In TRILL only a single flow/Path may be at fault among many flows. • In TRILL we use • Single RDI flag on CCM message: which is set on timeout of any flow from any remote partner • SNMP Notifications (traps) that notify last good flow and first good flow after the failure • Idea here is • RDI Flag tells there is a fault seen • Logs/SNMP allow to further isolate the failure to the exact flow • Path Trace message utilized to further isolate the failure along the path CCM and variation for TRILL (multipath)

  8. SNMP notification-1: Upon CCM timeout send with {Remote MEP-ID, flow-ID of the last good flow and last sequence number received } RDI flag is set on TO Can be sticky or reset After full cycle CCM from remote MEP-1 MEP-A SNMP notification-2: Upon CCM resumption {Remote MEP-ID, flow-ID of the first good flow and first sequence number received } CCM in TRILL Ref: Section 12.1 draft-ietf-trill-oam-fm

  9. RDI flag set for MEP-1 CCM from remote MEP-1 CCM {RDI=1} MEP-A OR => RDI No RDI flag set for MEP-2 CCM in TRILL – multiple remote MEP CCM from remote MEP-2 Ref: Section 12.1 draft-ietf-trill-oam-fm

  10. Second last paragraph, the last sentence reads: . . . “In the foregoing example, it is MEP-A, flow-id (1) and sequence number 9”. • This should read as . . . “In the foregoing example, it is MEP-A, flow-id (3)and sequence number 9”. Errata section 12.1

  11. Official liaison letter to SDOs to review fault management document • Review and WG adoption of Performance management document • Review of MIB document • Update of fault management and MIB document based on SDO comments • Target: Prior to next IETF Next steps

More Related