OAM Domain configuration using GARP Generic OAM registration













- Slides: 13
OAM Domain configuration using GARP (Generic OAM registration protocol - GORP) David Elie-Dit-Cosaque, Kamakshi Sridhar, Maarten Vissers, Tony Van Kerckhove
Why automatic configuration of OAM domain? > Large number of flow points to configure • > prone to human errors Dynamic conditions MP’s may be added or deleted • Spanning tree changes Bridge Spanning tree branch • LP MP Upper level LP Need for Dynamic Configuration of the OAM domain. We propose GARP OAM Registration protocol (GORP) IEEE 802. 1 July 11 -16, 2004 — 2
GORP(GARP OAM Registration Protocol) Basics > GARP application > Similar to GVRP > New attributes = OAM levels > Just like in GVRP: GORP requires manual placement of at least two MPs to define an OAM domain • Enables Dynamic placement and Level assignment of all other LP’s • GVRP pruning can be translated to GORP pruning-> Increased security • GORP brings plug and play and security to OAM domain configuration IEEE 802. 1 July 11 -16, 2004 — 3
Level determination of LP’s using GORP > GORP: Each level is configured one at a time. > GORP: The order in which levels are configured does not matter. > Local decision: • Every activated LP must pick minimum{level#1, … level # k} MP 1 LP 1 20 20 MP 3 11 Customer Level Provider Level LP 2 MP 2 20 20 LP 3 LP 4 LP 5 LP 6 MP 4 11 11 11 Operator Level MP 5 LP 7 LP 8 9 9 9 MP 6 Lower Level attribute registration triggers changes of level 9 Physical Level ports P 1 IEEE 802. 1 July 11 -16, 2004 — 4 P 2 P 3 P 4 P 5 P 6 P 7 P 8
GORP mechanism (placement of LP’s and setting their levels) Manually configured MP 1 1 OAM 1 D 3 3 OAM 1 D 2 B 3 2 B 2 OAM 1 R OAM 1 D 4 1 OAM 1 D 2 1 OAM 1 D B 1 3 OAM 1 D 2 B 5 D OAM 1 R OAM 1 D OAM 1 R 3 2 B 4 4 R: registered D: declared IEEE 802. 1 July 11 -16, 2004 — 5 3 OAM 1 D 4 1 OAM 1 R OAM 1 D 1 3 OAM 1 D OAM 1 R 2 B 6 OAM 1 D 4 2 B 7 3 4 OAM 1 D 4
GORP mechanism (placement of LP’s and setting their levels) OAM 1 RD Port with autoconfigured LP 1 Port with manually configured MP 1 OAM 1 DR D DR OAM 1 D 3 3 OAM 1 D 2 OAM 1 DR D DR 4 1 OAM 1 D 2 1 OAM 1 D B 1 3 OAM 1 D OAM 1 RD R 2 B 5 D OAM 1 DR D Manually configured MP B 3 2 B 2 OAM 1 RD R RD OAM 1 R 3 2 B 4 4 R: registered D: declared IEEE 802. 1 July 11 -16, 2004 — 6 3 OAM 1 D 4 1 OAM 1 R OAM 1 DR D DR 1 3 OAM 1 D OAM 1 RD R 2 B 6 OAM 1 D D 4 2 B 7 3 4 OAM 1 D 4
GORP pruning > Just like GVRP pruning, can do GORP pruning. > GORP pruning results in: • > Automatic placement of MP’s wherever required Benefits: Automatic MP’s will plug in holes in the OAM domain. • Thus, Missing MP’s will not result in security leaks • IEEE 802. 1 July 11 -16, 2004 — 7
GORP pruning Missing MP MP 5 MP 1 MPb MPa MP Dynamically created MPs MP Manually created MPs MP 3 Provider Level MP 2 LP MP 4 MP 6 Customer Level GORP dynamic placement of MPs prevents OAM frames from leaking outside the OAM domain IEEE 802. 1 July 11 -16, 2004 — 8
New manual (or repaired) MPs New MP MP 5 MP 1 MPa MPb MP Dynamically created MPs MP Manually created MPs MP 3 Provider Level MP 2 MP 4 MP 6 New manual MP’s installed: existing IEEE 802. 1 July 11 -16, 2004 — 9 Customer Level MP’s will be removed.
GORP pruning (placement of boundary MP’s) OAM 1 RD OAM 1 DD Port with autoconfigured LP 1 Port with manually configured MP 1 Port with autoconfigured MP OAM 1 DR D DR OAM 1 D 3 3 OAM 1 D 2 OAM 1 DR D DR 4 1 OAM 1 D 2 1 OAM 1 D B 1 3 OAM 1 D OAM 1 RD R 2 B 5 D OAM 1 DR D Manually configured MP B 3 2 B 2 OAM 1 RD R RD OAM 1 R 3 2 B 4 4 3 R: registered D: declared IEEE 802. 1 July 11 -16, 2004 — 10 OAM 1 D 4 1 OAM 1 R OAM 1 DR D DR 1 3 OAM 1 D OAM 1 RD R 2 B 6 OAM 1 D D 4 2 B 7 3 4 OAM 1 D 4
GARP frame format Attribute Value is the OAM domain Level No modifications to the GARP frame format IEEE 802. 1 July 11 -16, 2004 — 11
Summary +GORP is a new GARP application similar to GVRP (same frame format, new attribute) +GORP allows OAM domain pruning to prevent leaks +GORP automatically configures/reconfigures OAM domain IEEE 802. 1 July 11 -16, 2004 — 12
www. alcatel. com IEEE 802. 1 July 11 -16, 2004 — 13