Manuale d’uso / di manutenzione del prodotto 10.4 del fabbricante Juniper Networks
Vai alla pagina of 204
Junos ® O S MX S eries Etherne t S ervic es R out ers S olutions Guide Rel ease 10 . 4 Published: 2010-10-0 7 Cop yright © 2010, Juniper Netw orks, Inc.
Juniper Netw orks, Inc. 1194 North Mathil da Avenue Sunnyv ale, Calif ornia 94089 US A 408-7 45-2000 www .juniper .net This pr oduct includes the Env oy SNMP Engine, de velope d by Epilog ue T echnology , an Integr ate d Sys tems Compan y . Copyright © 1986-1 997 , Epilog ue T echnology C orporation.
END USER LICENSE A GREEMENT READ THIS END USER LICENSE A GREEMENT (“ AGREEMENT”) BEF ORE DOWNL OADING , INST ALLING, OR USING THE S OFTW ARE. BY DOWNL OADING , INST ALLING, OR USING THE S OFTW ARE.
Softw are in any manner tha t ext ends or is broader than the uses pur chased b y Customer fr om Juniper or an authorized Juniper re seller; (i) use Embedded Soft ware on non-Juniper equipment; (j) us.
12. Commercial C omputer Soft ware. The S oftwar e is “commercial c omputer softw are” and is pro vided with restric ted rights. Use , duplica tion, or disclosur e by the United S tat es go vernment is subject t o restric tions set forth in this Agr eement and as pr ovided in DF ARS 227 .
Cop yright © 2010, Juniper Netw orks, Inc. vi.
Abbr evia t ed T abl e of C ont ents A b o u tT h i sG u i d e.................................................x v i i P art 1 Overvie w C h a p t e r 1 O v e r v i e wo f E t h e r n e t S o l u t i o n s.
Cop yright © 2010, Juniper Netw orks, Inc. viii Junos 10. 4 MX Series Etherne t Services R outers Sol utions Guide.
T abl e of C ont ents A b o u tT h i sG u i d e.................................................x v i i Junos Documenta tion and R elea se Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii O b j e c t i v e s ...................
C h a p t e r 3 V i r t u a l S w i t c h e s ..................................................3 9 Lay er 2 Featur es for a Swit ching En vironment . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 Config uring Virtu al S witches as Separ at e R outing Inst ances .
P art 3 Ethernet Fil tering, Monitoring, and F ault Mana gement S olutions for MX S eries R out ers C h a p t e r 9 L a y e r2F i r e w a l lF i l t e r s .............................................9 5 Fire wall Filt ers for Bridge Domains and VPLS Instance s .
P art 4 Index I n d e x .............................................................1 7 7 Cop yright © 2010, Juniper Netw orks, Inc. xii Junos 10. 4 MX Series Etherne t Services R outers Sol utions .
List of Fig ur es P art 1 Overvie w C h a p t e r 1 O v e r v i e w o f E t h e r n e t S o l u t i o n s ......................................3 Figure 1: Nativ e (Normal) and VLAN-T agged Ethernet F ames . . . . . . . . . . . . . . . . 12 F i g u r e 2 : A M e t r o E t h e r n e t N e t w o r k .
Figure 22: Etherne t LFM with L oopback Support . . . . . . . . . . . . . . . . . . . . . . . . . 142 C h a p t e r 1 3 E t h e r n e t R i n g P r o t e c t i o n ..........................................1 4 5 Figure 23: Ethernet Ring P rote ction Exampl e Nodes .
List of T abl es A b o u tT h i sG u i d e.................................................x v i i T a b l e 1 : N o t i c e I c o n s .................................................x x i T abl e 2: T ext and S yntax C onventions . . . . . . . . . .
Cop yright © 2010, Juniper Netw orks, Inc. xvi Junos 10. 4 MX Series Etherne t Services R outers Sol utions Guide.
About T his Guide This pr efa ce pr ovides the f ollo wing guidelines f or using the Junos ® OS MX Serie s Ethernet Servic es Rout ers Sol utions Guide : • Junos Documenta tion and R ele ase Not es.
Objectiv es This g uide provide s an overvie w of the Lay er 2 fe atur es of the Junos OS and describe s how t o configur e the fe atur es to pr ovide sol utions to sev eral ne twork sc enarios.
Support ed R outing Pla tf orms For the Lay er 2 fe atur es described in this manual, the Junos O S currentl y supports the foll owing routing pl at forms: • Juniper Netw orks MX S eries Ethernet Servic es R outer s Using the Index es This r efer ence c ontains a standar d index with t opic entries.
2. Merg e the cont ents of the file int o your r outing pla tf orm config ura tion by issuing the loa d merge config ura tion mode command: [edit] user@host# l oad merg e / var /tmp/ ex-script.c onf loa d compl ete Merging a S nippet T o merg e a snippet, f ollo w these st eps: 1.
T able 1: Notice Ic ons Description Meaning Icon Indica tes important f ea tures or instructions. Informa tional note Indica tes a situa tion that might r esult in l oss of dat a or hardwar e damage. Caution Alert s you to the risk of per sonal injury or dea th.
T able 2: T ex t and Synt ax Con ventions ( continued) Exampl es Description Conv ention broadca st | multic ast ( string1 | string2 | string3 ) Indica tes a choic e betwe en the mutually ex clusiv e keyw ords or variabl es on either side of the symbol.
or are c ov ered under warr anty , and need postsal es technical support, y ou can ac ce ss our tool s and resour ces online or open a ca se with JT A C. • JT AC policies—For a c omple te under standing of our JT AC pr ocedur es and policies, re view the JT AC User Guide l oca ted a t http:/ / www .
Cop yright © 2010, Juniper Netw orks, Inc. xxiv Junos 10. 4 MX Series Etherne t Services R outers Sol utions Guide.
P ART 1 Ov erview • Overvie w of Ethernet Sol utions on page 3 1 Copyright © 2010 , Juniper Network s, Inc..
Cop yright © 2010, Juniper Netw orks, Inc. 2 Junos 10. 4 MX Series Etherne t Services R outers Sol utions Guide.
CHAPTER 1 Ov erview of Etherne t S ol utions • Ethernet T erms and Acron yms on page 3 • Netw orking and Internet working with Bridg es and R outers on pa ge 6 • Netw ork Addr essing at L ay er .
• bridge— A netw ork component define d by the IEEE tha t forw ards frame s from one LAN segment or VLAN t o another . The bridging func tion can be cont ained in a rout er , LAN swit ch, or other specialized de vice. S ee also s witch . • bridge domain— A set of l ogical ports tha t share the same fl ooding or broadca st chara cteristics.
• MS TP—Mul tiple Sp anning T ree P rot ocol. A spanning-tr ee prot ocol used t o prev ent loop s in bridge config ura tions. Unlike other type s of STP s, MS TP can bl ock ports sel ectivel y by VLAN. See als o RS TP . • O AM—Opera tion, Administr ation, and Maint enance.
• Netw orking at La yer 2: Forw arding Dual-T agged Fr ames on pag e 13 • Netw orking at La yer 2: L ogical Int erfa ce T ypes on page 14 • A Metro E thernet Netw ork with MX Series R outer s on.
coul d ol der bridges tha t wer e less int elligent de vices. Bridg es le arn much about the LAN segments the y connect t o from pr otoc ols like those in the S panning T ree Pr otocol (S TP) famil y . The ne twork l ay er (Lay er 3) is the highest la yer use d by netw ork nodes t o forwar d tra ffic as part of the da ta plane.
NO TE: The opposite of a “ globall y unique netw ork address” is the “l ocall y significant c onnection identifier” which connects tw o endpoints on a netw ork. For exampl e, MPLS label s such as 1000001 can r epeat in a ne twork, but a public IP address c an appear on the Interne t in only one pl ace a t a time (otherwise it is an err or).
R elat ed Documenta tion MX Series Etherne t Service s Rout ers S olutions P ag e • • Ethernet T erms and Acron yms on page 3 • Netw orking and Internet working with Bridg es and R outers on pa .
NO TE: Networking a t the frame l evel s ays nothing about the pr esence or absence of IP a ddresses a t the packe t lev el. Almost all ports, link s, and device s on a netw ork of LAN swit ches still hav e IP addresses, just a s do all the sourc e and destina tion hosts.
• Netw orking at La yer 2: Bene fits of Ethernet Frame s on page 9 • Netw orking at La yer 2: Forw arding VLAN T agged Fr ames on pag e 11 • Netw orking at La yer 2: Forw arding Dual-T agged Fr .
Figur e 1: Nativ e (Normal) and VLAN-T agge d Ethernet F ames The VLAN t ag subtra cts four b yte s from the tot al MTU length of the Etherne t frame, but this is sel dom a probl em if kept in mind . When this tag is use d in an Ethernet frame , the frame c omplies with the IEEE 802.
Netw orking at Lay er 2: Forwar ding Dual-T agg ed Fr ames The use of VLAN t agging to gr oup (or bundl e) sets of MA C addr esses is a start t owar d a method of f orwarding LAN tr affic ba sed on informa tion found in the fr ame, not on IP addre ss in the packe t.
• Netw orking and Internet working with Bridg es and R outers on pa ge 6 • Netw ork Addr essing at L ay er 2 and Lay er 3 on page 7 • Netw orking at La yer 2: Bene fits of Ethernet Frame s on pa.
A Metr o Ethernet Net work with MX S eries R outers Wha t woul d a Metro Etherne t network with Juniper Ne twork s MX Series Etherne t Service s R outers l ook like? It is v ery likel y that the Me tro Ethernet ne twork will pl ace MX S eries rout ers a t the edge of a VPL S and MPLS c ore netw ork.
Figur e 3: A Metro Etherne t Netw ork with MX Series R outer s In Figure 3 on p age 16, the cir cled number s refl ect the diff erent f ormats tha t the Ethernet frame s can tak e as the fr ames make their w ay fr om a host on one Ethernet swit ching hub to a host on the other hub .
• Netw orking and Internet working with Bridg es and R outers on pa ge 6 • Netw ork Addr essing at L ay er 2 and Lay er 3 on page 7 • Netw orking at La yer 2: Bene fits of Ethernet Frame s on pa.
• Netw orking at La yer 2: Bene fits of Ethernet Frame s on page 9 • Netw orking at La yer 2: Chall enges of Ethernet MA C Addr esses on pag e 10 • Netw orking at La yer 2: Forw arding VLAN T ag.
P ART 2 Ba sic S olutions f or MX S eries R out er s • Basic L ayer 2 Fe atur es on MX Series R outers on pa ge 21 • Virtual S witches on pag e 39 • VLANs Within Bridg e Domain and VPLS Envir on.
Cop yright © 2010, Juniper Netw orks, Inc. 20 Junos 10. 4 MX Series Etherne t Services R outers Sol utions Guide.
CHAPTER 2 Ba sic L a y er 2 Fe a tur es on MX S eries R out ers • Lay er 2 Fea tures f or a Bridging Environment on p age 21 • Exampl e R oadmap: Config uring a Basic Bridg e Domain Environment on.
• Spanning T ree P rotoc ols (xS TP , where the “x” repre sents the S TP type)—Bridges function b y associa ting a MAC a ddress with an int erfac e, simil ar to the wa y a rout er associa tes an IP netw ork address with a ne xt-hop int erfac e.
Figur e 5: Bridging Netw ork with MX Series R outer s The thr ee rout ers ea ch have a serie s of hosts on their Ethernet int erfac es, a s well a s aggr ega ted Etherne t links betw een them.
• R outer 2 and R outer 3 ha ve IRB c onfigured s o that they c an pass tr affic t o other rout ers in the rest of the ne twork. • R outer 1 ha s an acc ess interf ace which pro vides bridging on VLAN 205 and is connec ted to a cus tomer devic e configur ed on ge-2/2/2 .
T o config ure the Ethernet int erf aces and VLAN t ags on all thre e router s: 1. Config ure the Ethernet int erfac es and VLAN ta gs on R outer 1: [edit] chassis { aggre gat ed-devic es { ethernet { devic e-count 2; # Number of AE interf ace s on router } } } interf aces g e-2/ 1/0 { gigether-options { 802.
famil y bridge { interf ace-mode a ccess; vlan-id 205; } } } interf aces g e-2/2/ 4 { nativ e-vlan-id 200; # Unta gged pack ets g et vlan 200 ta g unit 0 { famil y bridge { interf ace-mode trunk; vlan.
encapsul ation vlan-bridg e; vlan-id 100; } } interf aces g e-3/3/3 { encapsul ation fl exibl e-ethernet-service s; vlan-ta gging; # Cust omer interf ace uses singl y-tagg ed frame s unit 200 { encapsul ation vlan-bridg e; vlan-id 200; } } interf aces g e-5/ 1/0 { gigether-options { 802.
vlan-id 100; } unit 200 { vlan-id 200; } } 3. Config ure the Ethernet int erfac es and VLAN ta gs on R outer 3: [edit] chassis { aggre gat ed-devic es { ethernet { devic e-count 2; # Number of AE inte.
802.3ad ae3; } } interf aces g e-11/ 1/2 { gigether-options { 802.3ad ae3; } } interf aces g e-11/ 1/3 { gigether-options { 802.3ad ae2; } } interf aces g e-11/ 1/ 4 { gigether-options { 802.3ad ae2; } } interf aces g e-11/ 1/5 { gigether-options { 802.
Exampl e Step: C onfiguring Bridg e Domains T o config ure the bridg e domains on all three rout ers: 1. Config ure a bridge domain on R outer 1: [edit] bridge-domains { vlan100 { domain-type bridge; vlan-id 100; interf ace g e-2/2/ 1.100; interf ace a e1.
domain-type bridge; vlan-id 200; interf ace g e-3/3/3.200; interf ace a e1.200; interf ace a e3.200; } } 3. Config ure a bridge domain on R outer 3: [edit] bridge-domains { vlan100 { domain-type bridge; vlan-id 100; interf ace g e-2/2/2.100; interf ace a e3.
Exampl e Step: C onfiguring Sp anning T ree P rot ocols Config ure the Spanning T ree P rotoc ol on all three r outer s. This is nec essary to a void the potential bridging l oop f ormed by the triangul ar archit ecture of the r outer s. MSTP is config ured on the thre e router s so the set of VLANs ha s an independent, loop-fr ee topol ogy .
3. Config ure MS TP on Rout er 3: [edit] prot ocols { mstp { configur ation-name ms tp-for-R1-2-3; # The names mus t match t o be in the same region revision-l ev el 3; # The re vision lev els must ma.
Figur e 6: Designat ed, R oot, and Alt ernat e Ports R elat ed Documenta tion MX Series Etherne t Service s Rout ers S olutions P ag e • • Lay er 2 Fea tures f or a Bridging Environment on p age 2.
2. R efer ence the IRB int erfac e at the bridg e domain l evel of the c onfigura tion. IRB supports La yer 2 bridging and La yer 3 r outing on the same interf ace . If the MAC addre ss on the arriving frame is the same a s that of the IRB int erfa ce, then the pa cket inside the frame is r outed .
interf ace a e1.100; interf ace a e3.100 routing-int erfac e irb. 0; } vlan-200 { domain-type bridge; vlan-id 200; interf ace g e-3/3/3.200; interf ace a e1.200; interf ace a e3.200 routing-int erfac e irb. 1; } } 2. Config ure the rout er link and IRB on R outer 3: [edit] interf aces { xe-1/1/0 { unit 0 { famil y inet { address 10 .
unit 4 { famil y inet { address 10 .0 .3.4/2 4 { } } unit 5 { famil y inet { address 10 .0 .3.5/24 { } } unit 6 { famil y inet { address 10 .0 .3.6 /24 { } } unit 7 { famil y inet { address 10 .0 .3.7 /24 { } } unit 8 { famil y inet { address 10 .0 .3.
vlan204 { vlan-id 204; routing-int erfac e irb.5 } vlan205 { vlan-id 205; routing-int erfac e irb. 6 } } R elat ed Documenta tion • MX Series Etherne t Service s Rout ers S olutions P ag e • Lay e.
CHAPTER 3 V irtual S wit ches • Lay er 2 Fea tures f or a S witching Envir onment on pag e 39 • Config uring Virtual S witches a s Separa te R outing Instances on pa ge 40 Lay er 2 Fea tures f or .
• Config uring Virtual S witches a s Separa te R outing Instances on pa ge 40 Config uring Virtual S witches a s Separ at e Routing Instanc es Y ou can config ure tw o virtual swit ches as separ at e routing inst ances on an MX S eries rout er with bridge domains and VLANs.
R elat ed Documenta tion • MX Series Etherne t Service s Rout ers S olutions P ag e • Lay er 2 Fea tures f or a S witching Envir onment on pag e 39 41 Copyright © 2010 , Juniper Network s, Inc.
Cop yright © 2010, Juniper Netw orks, Inc. 42 Junos 10. 4 MX Series Etherne t Services R outers Sol utions Guide.
CHAPTER 4 VLANs W ithin Bridg e Domain and VPL S Envir onments • VLANs Within a Bridg e Domain or VPLS Inst ance on pag e 43 • P acke t Flo w Thr ough a Bridged Ne twork with Normaliz ed VLANs on .
• Exampl e: Config uring One VPLS Instanc e for S ever al VLANs on pag e 55 P ack et Fl ow T hrough a Bridg ed Net work with Normaliz ed VLANs P acke ts rec eived o ver a La yer 2 l ogical int erfa ce f or bridging are proc essed in a strict sequenc e of steps.
Config uring a Normalized VLAN f or T r ansla tion or T agging This t opic pro vides configur a tion and opera tional informa tion to help y ou manipula te virtual l ocal are a network s (VLANs) within a bridge domain or a virtual priv at e LAN service (VPLS) inst ance.
Then, the sour ce MA C addre ss of a rec eived pack et is l earned ba sed on the normalize d VLAN config ura tion. For output pack ets, if the VLAN ta gs associa te d with an egress l ogical int erfa .
• vlan-ta gs outer out er-vlan-number inner inner-vlan-number • Use the vlan-id all sta tement t o configur e bridging for se ver al VLANS with minimal amount of config ura tion and switch r esourc es. For an ex ample of this c onfigura tion, see “Exampl e: Configuring One VPLS Inst ance f or Sev eral VLANs” on pa ge 55.
NO TE: This topic does not pre sent exhaustiv e configur ation listing s for all rout ers in the figure s. Howe ver , you can us e it with a broader config ura tion stra te gy to c omple te the MX Series r outer net work c onfigura tions. Consider the pr ovider bridg e network sho wn in Figur e 7 on page 48.
The VLANs’ bridging pa ths are sho wn with distinct da shed and dotte d lines. The VLANs at e ach site ar e: • L2-PE1 at Sit e 1: VLAN 100 and VLAN 300 • L2-PE2 at Sit e 2: VLAN 100 • L2-PE3 a.
} } interf aces g e-5/0 /0 { encapsul ation fl exibl e-ethernet-service s; fle xible-vl an-tagging; unit 1 { encapsul ation vlan-bridg e; vlan-ta gs outer 500 inner 100; # T his plac es two VLAN t ags.
Bridge domain c1–vl an-100 for c ustomer-c1–virtual-s witch ha s five l ogical int erfac es: • Logic al interf ac e ge-1/0 /0 .1 c onfigured on ph ysical port g e-1/0 /0 . • Logic al interf ac e ge-2/0 /0 .1 c onfigured on ph ysical port g e-2/0 /0 .
For more inf ormation about c onfiguring Ethernet pseudo wires a s part of VPLS , see the Junos OS Fe ature Guide . NO TE: This topic does not pre sent exhaustiv e configur ation listing s for all rout ers in the figure s.
to P0 and P1, Sit e 2 is connec ted t o P0 and P2 (not shown), Sit e 3 is connec ted t o P2 and P3, and Site 4 is c onnect ed to P1 and P3. VPL S pseudowir es config ured on the PE and P rout ers carry tr affic be tween the sit es. The pseudo wires f or the VPLS ins tances ar e shown with distinct da shed and dotted lines.
encapsul ation vlan-vpl s; vlan-id 302; } } routing-instanc es { cust omer-c1-vsi { instanc e-type vpls; vlan-id 100; interf ace g e-1/0 /0. 1; interf ace g e-2/0 /0.
The f ollo wing happens on the C2 VLAN a s a resul t of the vlan-id none configur ation: • A MA C table is cr ea ted f or each inst ance of vlan-id none . A ll MAC addr esses l earned ov er the interf ace s belonging t o this VPLS inst ance are a dded to this tabl e.
Figur e 9: Many VLANs on One VPLS Instanc e The La yer 2 PE r outer s are MX Series r outer s. Each site is c onnect ed to t wo P rout ers f or redundanc y , althou gh both links ar e only sho wn for L2-PE1 a t Site 1.
If VLANs 1 through 1000 f or customer C1 span the same sit es, then the vlan-id all and vlan-r ange sta tement s provide a w ay t o swit ch all of these VLANs with a minimum config ura tion effort and f ew er switch r esourc es. NO TE: Y ou cannot use the vl an-id all stat ement if you config ure an IRB interf ace on one or mor e of the VLANs.
} # End of cust omer-c1-v1-to-v1000 cust omer-c1-v1500 { instanc e-type vpls; vlan-id 1500; interf ace g e-1/0 /0. 11; interf ace g e-6/ 0/0 . 11; } # End of cust omer-c1-v1500 } # End of routing-instanc es Note the use of the vl an-id all and vlan-id-range s tat ements in the VPLS ins tance c alled cust omer-c1-v1-to-v1000 .
CHAPTER 5 Bulk A dministr a tion of L a y er 2 Fea tur es on MX S eries R out ers • Bulk Config ura tion of VLANs and Bridge Domains on pag e 59 • Exampl e: Config uring VLAN T ransl ation with a .
The f ollo wing ex ample tr ansla tes inc oming trunk pack ets from VLAN identifier 200 t o 500 and 201 to 501 ( other valid VLAN identifiers ar e not aff ect ed): [edit int erfac es ge-1/ 0/1] unit 0 { .
bridge-domains { bd-vlan–5 { vlan-id 5; } bd { vlan-id [ 1–4 6– 10 ]; } } If a VLAN identifier is alre ady part of a VLAN identifier list in a bridge domain under a routing inst ance, then y ou must dele te the VLAN identifier from the list be for e you can config ure an explicit or “r egul ar ” bridge domain.
Cop yright © 2010, Juniper Netw orks, Inc. 62 Junos 10. 4 MX Series Etherne t Services R outers Sol utions Guide.
CHAPTER 6 Dynamic P rofil es f or VLAN Int erf ac es and P rot oc ols • Dynamic Pr ofiles f or VPLS P seudowir es on pag e 63 • Exampl e: Config uring VPLS Pseudo wires with Dynamic P rofil es—B.
• Exampl e: Config uring VPLS Pseudo wires with Dynamic P rofil es—Ba sic Solutions on pag e 64 • Exampl e: Config uring VPLS Pseudo wires with Dynamic P rofil es—Compl ex Solutions on pag e 6.
vlan-id 20; } } ge-0 /0 /3 { unit 0 { vlan-id 30; } } NO TE: This is not a compl ete r outer c onfigura tion. With this c onfigura tion, broadca st pack ets inside fr ames arriving with VLAN identifier 10 on ge-0 /0 / 1 are normaliz ed to a dual-t agged fr ame with an outer VLAN value of 200 and an inner VLAN val ue of 100.
} ge-0 /0 /3 { unit 0 { vlan-id 30; } } [edit dynamic-pr ofiles] green_vpls_p w_1 interf ace s $junos-interf ace-if d-name { unit $junos-underl ying-unit-number { vlan-ta gs outer 200 inner 100; } } NO TE: This is not a compl ete r outer c onfigura tion.
} } ge-0 /0 /3 { unit 0 { vlan-id 100; } } NO TE: This is not a compl ete r outer c onfigura tion. With this c onfigura tion, broadca st pack ets inside fr ames arriving on ge-0 /0/1 are normalized t o a dual-tagg ed fr ame with an outer VLAN val ue of 200 and an inner VLAN val ue of 100.
vlan-ta gs outer 200 inner 100; } } NO TE: This is not a compl ete r outer c onfigura tion. With this c onfigura tion, broadca st pack ets inside fr ames arriving with VLAN identifier 100 on ge-0 /0 / 1 are normaliz ed to a fr ame with VLAN identifier 100 (in this ca se, they are unchang ed).
interf ace g e-0/ 0/0 . 1; ... # Other interf aces and s tat ements for Sal es } engineering { vlan-id 20; interf ace g e-1/0 /2.0; ... # Other interf aces and s tat ements for Engineering } acc ounting { vlan-id 30; interf ace g e-2/0 /3.
site sampl e-site-1 { site-identifier 1; } associa te-pr ofile gre en_vpls_pw_1; # Appl y profil e here } ... # Other routing instanc e sta tements [edit dynamic-pr ofiles] green_vpls_p w_1 interf ace.
NO TE: This is not a compl ete r outer c onfigura tion. In this ca se, fr ames arriving on the interf ace s are cla ssified accor ding to their bridg e domains and swit ched, if nec essary , to the VPL S pseudowir e trunk, ex cept f or Engineering frame s.
Config ura tion of T ag T ransla tion Using Dynamic Pr ofiles Consider a final c ase wher e the bridge domain VLANs need tr ansla tion a t the VPLS pseudowir e trunk interf ac e. In this ca se, sal es (VLAN 10) is mapped t o VLAN 110 and engineering (VLAN 20) is mappe d to VLAN 120.
CHAPTER 7 MX S eries R out er a s a DHCP R el a y Ag ent • MX Series R outer as a L ayer 2 DHCP R elay A gent on pag e 73 • Exampl e: Config uring DHCP Rel ay in a Bridg e Domain VLAN Environment .
R elat ed Documenta tion MX Series Etherne t Service s Rout ers S olutions P ag e • • Exampl e: Config uring DHCP Rel ay in a Bridg e Domain VLAN Environment on pa ge 74 • Exampl e: Config uring.
Exampl e: Configuring DHCP R ela y in a VPLS R outing Instance En vironment The f ollo wing ex ample c onfigures DHCP r ela y in a bridge domain (VLAN) envir onment. The MX S eries rout er will trust only the MA C addresses l earned on the list ed int erfac es.
interf ace g e-2/2/ 4.0; interf ace g e-2/2/6 .0; } } } } } } Y ou verify your c onfigur ation b y using two r ela ted c ommands: • show dhcp r elay binding r outing-instance v s1 bridge-domains bd1.
CHAPTER 8 MX S eries R out er in an A TM Ethernet Int erw orking Function • MX Series R outer A TM Ethernet Interw orking Function on pag e 77 • Exampl e: Config uring MX Series R outer A TM Ether.
Becaus e of the transl ation, the fl ow of pack ets and fr ames betw een PE1 (the M Serie s rout er) and PE2 (the MX series rout er) rout ers is not symmetric al, as is sho wn in Figure 11 on pag e 78.
Exampl e: Configuring MX S eries Rout er A TM Ethernet Int erworking Consider the r outer t opolog y shown in Figur e 13 on page 79. T he MX Series r outer is config ured a s the Pro vider Edge 2 (PE2) r outer in the figur e to support the A TM Ethernet IWF .
at-2/ 0/ 0 { encapsul ation ethernet-o ver-a tm; atm-options { vpi 100; } unit 0 { vci 100 .34; famil y inet { address 30 .1. 1.1/24; } } } } PE1 Config uation Config ure the La yer 2 Circ uit [edit] .
} } } PE2 Config uation Config ure the La yer 2 Circ uit on the MX Series R outer [edit] interf aces { ge-0 /2/0 { vlan-v ci-tagging; encapsul ation vlan-v ci-cc c; unit 0 { vlan-id 100; inner-vlan-id-r ange start 32 end 6 3; } } ge-0 /2/8 { unit 0 { famil y inet { address 20 .
vlan-ta gs outer 100 inner 34; famil y inet { address 30. 1. 1.10 /24; } } } } Y ou verify your c onfigur ation on the MX S eries rout er with the show l2circ uit connections command: user@PE2> sho.
PE1 Config uation Config ure the La yer 2 Circ uit [edit] interf aces { at-2/ 0/ 1 { atm-options { vpi 100; } unit 0 { encapsul ation vlan-v ci-cc c; vpi 100; vci-r ange 32 63; } } ge-5/ 0/ 0 { unit 0 { famil y inet { address 20 .1. 1.1/24; } famil y mpls; } } prot ocols { mpls { interf ace g e-5/0 /0.
ge-0 /2/0 { gigether-options { 802.3ad ae0; } } ge-0 /2/8 { unit 0 { famil y inet { address 20 .1. 1.10/2 4; } famil y mpls; ae0 { vlan-v ci-tagging; encapsul ation vlan-v ci-cc c; unit 0 { vlan-id 100; inner-vlan-id-r ange start 32 end 6 3; } } } prot ocols { mpls { interf ace g e-0/2/8 .
} } } } Y ou verify your c onfigur ation on the MX S eries rout er with the show l2circ uit connections command: user@PE2> show l2cir cuit connections Layer-2 Circuit Connections: Legend for connec.
atm-options { vpi 100; } unit 0 { encapsul ation vlan-v ci-cc c; vpi 100; vci-r ange start 32 end 6 3; } } ge-5/ 0/ 0 { unit 0 { famil y inet { address 20 .1. 1.1/24; } famil y iso; famil y mpls; } } prot ocols { rsvp { interf ace g e-5/0 /0. 0; } mpls { label-s witched-pa th lsp1-2 { from 10 .
} ge-0 /2/8 { unit 0 { famil y inet { address 20 .1. 1.10/2 4; } famil y iso; famil y mpls; } } prot ocols { rsvp { interf ace g e-0/2/8 .0; } mpls { label-s witched-pa th lsp2-1 { from 10 .255.1 71.14; to 10 .255.1 71.45; } label-s witched-pa th lsp1-2 { from 10 .
user@PE2> show c onnections CCC and TCC connections [Link Monitoring On] Legend for status (St) Legend for connection types UN -- uninitialized if-sw: interface switching NP -- not present rmt-if: .
unit 0 { famil y inet { address 20 .1. 1.1/24; } famil y iso; famil y mpls; } } prot ocols { rsvp { interf ace g e-5/0 /0. 0; } mpls { label-s witched-pa th lsp1-2 { from 10 .255.1 71.45; to 10 .255.1 71.14; } label-s witched-pa th lsp2-1 { from 10 .255.
famil y mpls; } } ae0 { vlan-v ci-tagging; encapsul ation vlan-v ci-cc c; unit 0 { vlan-id 100; inner-vlan-id-r ange start 32 end 6 3; } } } prot ocols { rsvp { interf ace g e-0/2/8 .0; } mpls { label-s witched-pa th lsp2-1 { from 10 .255.1 71.14; to 10 .
Y ou verify your c onfigur ation on the MX S eries rout er with the show conne ctions command: user@PE2> show c onnections CCC and TCC connections [Link Monitoring On] Legend for status (St) Legend.
Cop yright © 2010, Juniper Netw orks, Inc. 92 Junos 10. 4 MX Series Etherne t Services R outers Sol utions Guide.
P ART 3 Etherne t Fil t ering, Monit oring, and F aul t Mana g ement S ol utions f or MX S eries R out ers • Lay er 2 Fire wall Fil ters on pa ge 95 • IEEE 802. 1ag OAM C onnectivit y-Faul t Manag ement on page 103 • ITU-T Y .1 731 Ethernet Frame Del ay Mea surements on p age 119 • IEEE 802.
Cop yright © 2010, Juniper Netw orks, Inc. 94 Junos 10. 4 MX Series Etherne t Services R outers Sol utions Guide.
CHAPTER 9 L a yer 2 F ir e w all Fil t ers • Fire wall Fil ters f or Bridge Domains and VPL S Instanc es on page 95 • Exampl e: Config uring Policing and Marking of T ra ffic Entering a VPL S Cor .
R elat ed Documenta tion MX Series Etherne t Service s Rout ers S olutions P ag e • • Exampl e: Config uring Policing and Marking of T ra ffic Entering a VPL S Cor e on page 96 • Exampl e: Config uring Filt ering of Frames b y MAC A ddress on pag e 98 • Exampl e: Config uring Filt ering of Frames b y IEEE 802.
T o config ure policing and marking of tr affic ent ering a VPLS c ore: 1. Config ure policer bc ast-unkno wn-unicast-non-ip-mc ast-polic er , a firew all policer t o limit the aggr ega te br oadca st.
4. Appl y the fire wall fil ter a s an input filt er to the cust omer interf ace at g e-2/ 1/0 : [edit int erfac es] ge-2/1/0 { vlan-ta gging; encapsul ation fl exibl e-ethernet-service s; unit 5 { en.
count e vil-mac-address; # C ounts frame with the bad sour ce MA C address discard; } term tw o { then acc ept; # Make sur e to ac cept other tr affic } } } } 2.
NO TE: Layer 2 bridging is support ed only on the MX S eries rout ers. For more informa tion about how t o configur e Lay er 2 bridging, see the Junos OS Polic y Frame work Config ura tion Guide , the Junos OS Routing P rot ocols C onfigura tion Guide , and the Junos OS Fea ture Guide .
• Exampl e: Config uring Filt ering of Frames b y P acket L oss Priority on pag e 101 Exampl e: Configuring Fil tering of Fr ames by P ack et Lo ss Priority T o config ure an MX Serie s rout er fire.
} 3. Appl y the filt er filt er-plp-configure-f orwarding a s an input fil ter t o the ge-0/ 0/ 0 interf ac e: [edit int erfac es] ge-0 /0 /0 { unit 0 { famil y bridge { filt er { input filt er-plp-co.
CHAPTER 10 IEEE 802. 1a g O AM C onnectivit y-F aul t Mana g ement • Ethernet Oper ations, A dministra tion, and Maintenanc e on pag e 103 • Ethernet O AM Connec tivity Fa ult Manag ement on pag e.
• Fa ult isol ation, v erifica tion, and rec ov ery (isola tion and verifica tion are provide d by a combina tion of prot ocols, whil e reco very is the function of pr otoc ols such as spanning tree) The l oopback pr otocol used in Etherne t OAM is model ed on the standar d IP ping.
maintenanc e domain, each servic e instanc e is call ed a maintenanc e associa tion. A maintenanc e associa tion can be thou ght as a full mesh of maint enance endpoints (MEP s) having simil ar charac teristics. MEP s are ac tive CFM entities g enera ting and responding to CFM pr otoc ol messag es.
Figur e 15: Ethernet O AM with VPLS The f ollo wing are the c onfigur ations of the VPL S and CFM on the service pro vider rout ers. Config uration of PE1 [ edit chassis] fpc 5 { pic 0 { tunnel-servic.
vpls-vlan2000 { instanc e-type vpls; vlan-id 2000; interf ace g e-1/0 /7 .1; rout e-distinguisher 10.255. 168.231:2000; vrf-targ et tar get:1000:1; prot ocols { vpls { site-r ange 10; site vl an2000-PE1 { site-identifier 2; } } } } [edit pr otoc ols] rsvp { interf ace g e-0/ 0/0 .
interv al 1s; } mep 100 { interf ace g e-1/0 /7 .1; direction up; auto-disc ov ery; } } } } } } Config uration of PE2 [ edit chassis] fpc 5 { pic 0 { tunnel-services { bandwidth 1g; } } } [edit int er.
rout e-distinguisher 10.255. 168.230:2000; vrf-targ et tar get:1000:1; prot ocols { vpls { site-r ange 10; site vl an2000-PE2 { site-identifier 1; } } } } [edit pr otoc ols] rsvp { interf ace g e-5/2/7 .0; } mpls { label-s witched-pa th PE2-to-PE1 { to 10 .
direction up; auto-disc ov ery; } } } } } } Config uration of P rout er MPLS onl y , no CFM needed: [edit] interf aces { ge-5/2/7 { # Connec ted t o PE1 unit 0 { famil y inet { address 10 .200. 1. 10/24; } famil y mpls; } } ge-0 / 1/0 { # Connec ted t o PE2 unit 0 { famil y inet { address 10 .
interf ace f xp0.0 { disabl e; } interf ace g e-0/ 1/0 .0; interf ace g e-5/2/7 .0; } } } CFM on L2-CE1 Here is the c onfigura tion of CFM on L2-E1: [edit int erfac es] ge-5/2/3 { vlan-ta gging; unit .
interv al 1s; } mep 700 { interf ace g e-0/2/9 .0; direction do wn; auto-disc ov ery; } } } } } R elat ed Documenta tion MX Series Etherne t Service s Rout ers S olutions P ag e • • Ethernet Oper .
Here ar e the configur ations of CFM on the cus tomer rout ers. CFM on L2-CE1 [edit int erfa ces] ge-0 /2/9 { vlan-ta gging; unit 0 { vlan-id 2000; } } [edit pr otoc cols oam etherne t] connec tivity-.
vlan-ta gging; encapsul ation fl exibl e-ethernet-service s; unit 0 { encapsul ation vlan-bridg e; vlan-id 2000; } } ge-5/1/ 7 { vlan-ta gging; encapsul ation fl exibl e-ethernet-service s; unit 0 { encapsul ation vlan-bridg e; vlan-id 2000; } } [edit bridg e-domains] bridge-vl an2000 { domain-type bridge; vlan-id 2000; interf ace g e-5/0 /9 .
encapsul ation fl exibl e-ethernet-service s; unit 0 { encapsul ation vlan-bridg e; vlan-id 2000; } } ge-5/2/3 { vlan-ta gging; encapsul ation fl exibl e-ethernet-service s; unit 0 { encapsul ation vlan-bridg e; vlan-id 2000; } } [edit bridg e-domains] bridge-vl an2000 { domain-type bridge; interf ace g e-5/2/3.
• Exampl e: Config uring Ethernet CFM ov er VPLS on pa ge 105 • Exampl e: Config uring Ethernet CFM on Physic al Interf ace s on page 116 Exampl e: Configuring Etherne t CFM on Physic al Interf ac es CFM can be used t o monitor the ph ysical link be tween t wo rout ers.
} } } } The c onfigura tion on Rout er 2 mirrors tha t on R outer 1. R outer 2 Configur e the interf ac e and CFM: [edit] interf aces g e-0/2/5 { unit 0 { famil y inet; } } prot ocols { oam { ethernet.
Cop yright © 2010, Juniper Netw orks, Inc. 118 Junos 10. 4 MX Series Etherne t Services R outers Sol utions Guide.
CHAPTER 11 ITU-T Y . 1 7 31 Ethernet Fr ame Del a y Me a sur ements • Ethernet Fr ame Dela y Measur ements on pag e 119 • Config uring MEP Interf aces t o Support Ethernet Fr ame Dela y Mea sureme.
dela y mea surement pro vides fine c ontrol to oper at ors f or triggering del ay me asurement on a given servic e and can be used t o monitor S ervice L ev el Agreements (SLA s). Ethernet fr ame dela y measur ement also c ollec ts other useful inf ormation, such a s worst and best ca se del ays, a ver ag e delay , and av era ge del ay varia tion.
For tw o-way (r ound-trip) Ethernet fr ame dela y mea surement, either MEP c an send a reque st to begin a tw o-wa y dela y mea surement to it s peer MEP , which responds with timestamp inf ormation. R un-time sta tistics are c ollec ted and displ ay ed at the initia tor MEP .
Config uring MEP Interf ac es to S upport Ethernet Fr ame Dela y Mea surements Ethernet fr ame dela y measur ement is a useful t ool for pr oviding perf ormance sta tistics or supporting or challenging S ervice L ev el Agreement s (SLAs). By def ault, Etherne t frame dela y mea surement uses soft ware f or timestamping and del ay c alcul a tions.
T o perf orm Ethernet frame del ay me asur ement, make sur e that the f ollo wing config ura tion stat ement is NO T present: [edit r outing-options] ppm { no-dele gat e-proc essing; # This turns distribut ed PPMD OFF .
T able 3: Monitor Ethernet Del ay C ommand P arame ters ( continued) Description P aramet er Range P aramet er (Optional) Spe cifies the number of seconds t o wait betw een frame s.
NO TE: The only diff erenc e in the two c ommands is the use of the mep-sta tistics and dela y-statistics k eyword . The fiel ds for the se commands ar e described in T abl e 4 on page 125. T able 4: Show Ethernet Del ay C ommand P arame ters Description P aramet er Range P aramet er Specifies an e xisting maintenanc e domain (MD) to use .
NO TE: These are not c omplet e rout er configur ations. Config ura tion on Rout er MX-1 : [edit] interf aces { ge-5/2/9 { vlan-ta gging; unit 0 { vlan-id 512; } } } prot ocols { oam { ethernet { connec tivity-faul t-manag ement { trac eoptions { file e oam_cfm.
} prot ocols { oam { ethernet { connec tivity-faul t-manag ement { trac eoptions { file e oam_cfm.log siz e 1g files 2 w orld-r eadabl e; fla g all; } linktr ace { path-da taba se-size 255; ag e 10s; .
Statistics: CCMs sent : 1590 CCMs received out of sequence : 0 LBMs sent : 0 Valid in-order LBRs received : 0 Valid out-of-order LBRs received : 0 LBRs received with corrupted data : 0 LBRs sent : 0 L.
Identifier MAC address State Interface 101 00:90:69:0a:48:57 ok ge-5/2/9.0 The r emote R outer MX-1 shoul d also coll ect the del ay sta tistics (up t o 100 per session) for displ ay with mep-st atistics or del ay-sta tistics .
2 357 3 344 4 332 5 319 6 306 7 294 8 281 9 269 10 255 Average one-way delay : 312 usec Average one-way delay variation: 11 usec Best case one-way delay : 255 usec NO TE: When two sy stems ar e close t o each other , their one-wa y delay v alues are v ery high compare d to their tw o-way del ay v alues.
} } } prot ocols { oam { ethernet { connec tivity-faul t-manag ement { trac eoptions { file e oam_cfm.log siz e 1g files 2 w orld-r eadabl e; fla g all; } linktr ace { path-da taba se-size 255; ag e 1.
} maintenanc e-domain md6 { le vel 6; maintenanc e-associa tion ma6 { continuity-che ck { interv al 100ms; hold-int erval 1; } mep 101 { interf ace g e-0/2/5. 0; direction do wn; auto-disc ov ery; } } } } } } } From R outer MX-1 , start a tw o-way del ay mea surement to R outer MX-2 .
CCMs received out of sequence : 0 LBMs sent : 0 Valid in-order LBRs received : 0 Valid out-of-order LBRs received : 0 LBRs received with corrupted data : 0 LBRs sent : 0 LTMs sent : 0 LTMs received : .
8 92 9 92 10 108 Average two-way delay : 103 usec Average two-way delay variation: 8 usec Best case two-way delay : 92 usec Worst case two-way delay : 122 usec The c olle cted del ay st atistics ar e also sa ved (up t o 100 per session) and displ aye d as part of the MEP dela y sta tistics on R outer MX-1 .
Untagg ed interf ace config ura tion for R outer MX-1 . [edit] interf aces { ge-5/ 0/ 0 { unit 0; } ge-5/2/9 { unit 0; } } prot ocols { oam { ethernet { connec tivity-faul t-manag ement { trac eoptions { file e oam_cfm.
connec tivity-faul t-manag ement { trac eoptions { file e oam_cfm.log siz e 1g files 2 w orld-r eadabl e; fla g all; } linktr ace { path-da taba se-size 255; ag e 10s; } maintenanc e-domain md6 { le v.
CHAPTER 12 IEEE 802.3ah O AM Link-F aul t Mana g ement • Ethernet O AM Link Fa ult Manag ement on pag e 137 • Exampl e: Config uring Ethernet LFM Betw een PE and CE on pag e 138 • Exampl e: Conf.
Exampl e: Configuring Etherne t LFM Betw een PE and CE In this exampl e, LFM is enabled on an IP link be tween the pr ovider edg e (PE) and cust omer edge ( CE) interf aces. If the link goe s down, the f ault will be de tect ed b y LFM and the interf ac es on both sides will be marke d Link-Layer-Do wn .
link-faul t-management { interf ace g e-1/ 1/0 { pdu-interv al 1000; pdu-threshol d 5; } } } } } R elat ed Documenta tion MX Series Etherne t Service s Rout ers S olutions P ag e • • Ethernet O AM.
pdu-threshol d 5; } } } } } 2. Config ure LFM on the PE2 rout er with CC C: [edit] interf aces g e-1/0 /0 { encapsul ation ethernet-c cc; unit 0; } prot ocols { oam { ethernet { link-faul t-management.
T o config ure LFM on an aggr ega te d Ethernet interf ac e betwe en two r outers: 1. Config ure LFM on R outer 1 f or AE0: [edit] chassis { aggre gat ed-devic es { ethernet { devic e-count 1; } } } interf aces g e-1/0 / 1 { gigether-options { 802.3ad ae0; } } interf aces g e-2/0 /0 { gigether-options { 802.
802.3ad ae0; } } interf aces a e0 { unit 0 { famil y inet { address 11. 11.11. 1/24; } } } prot ocols { oam { ethernet { link-faul t-management { interf ace a e0; } } } } R elat ed Documenta tion MX S.
} prot ocols { oam { ethernet { link-faul t-management { interf ace g e-1/0 /0 { pdu-interv al 1000; pdu-threshol d 5; remot e-loopback; } } } } } 2. Config ure LFM l oopback on the CE rout er: [edit] interf aces g e-1/ 1/0 { unit 0 { famil y inet { address 11.
Cop yright © 2010, Juniper Netw orks, Inc. 144 Junos 10. 4 MX Series Etherne t Services R outers Sol utions Guide.
CHAPTER 13 Etherne t Ring P r ot ec tion • Ethernet Ring P rote ction on pag e 145 • Ethernet Ring P rote ction Using Ring Instanc es for L oad Bal ancing on page 147 • Exampl e: Config uring Et.
Ev ery node on the ring is one of two t ypes: • RPL owner node— This node owns the RPL and bl ocks or unbl ocks the RPL a s conditions requir e. This node initia tes the R-APS mess age .
• Exampl e: Config uring Load Bal ancing Within Etherne t Ring Prot ection f or MX Series R outers on pa ge 154 Ethernet Ring P rot ection Using Ring Instanc es for Loa d Balancing Juniper Netw ork MX Series Etherne t Service s Rout ers support Ethernet ring pr otec tion (ERP) to help a chieve high r eliability and netw ork stability .
Exampl e: Configuring Etherne t Ring Prot ection f or MX Series R outers This e xampl e configur es Ethernet ring prot ection f or three MX S eries rout er nodes: • Exampl e T opol ogy on pag e 148 .
• R outer 2’ s ea st contr ol channel interf ace is g e-1/0 /2.1 (the RPL) and the w est contr ol channel interf ac e is ge-1/2/ 1.1 . T he prot ection group is pg102 . • R outer 3’ s ea st contr ol channel interf ace is g e-1/0 /3.1 (the RPL) and the w est contr ol channel interf ac e is ge-1/0 / 4.
contr ol-channel ge-1/0 / 1.1; ring-prot ection-link-end; } west-int erfa ce { contr ol-channel ge-1/2/ 4.1; } } } } 4. C onfigure Etherne t OAM: [edit] prot ocols { oam { ethernet { connec tivity-fau.
ge-1/ 0/2 { vlan-ta gging; encapsul ation fl exibl e-ethernet-service s; unit 1 { encapsul ation vlan-bridg e; vlan-id 100; } } ge-1/2/1 { vlan-ta gging; encapsul ation fl exibl e-ethernet-service s; unit 1 { encapsul ation vlan-bridg e; vlan-id 100; } } } 2.
le vel 0; maintenanc e-associa tion 100 { mep 2 { interf ace g e-1/2/ 1; remot e-mep 1 { action-pr ofile rmep-def aults; } } } } maintenanc e-domain d3 { le vel 0; maintenanc e-associa tion 100 { mep 1 { interf ace g e-1/0 /2; remot e-mep 2 { action-pr ofile rmep-def aults; } } } } } } } } R outer 3 C onfigura tion T o config ure R outer 3: 1.
domain-type bridge; interf ace g e-1/0 / 4. 1; interf ace g e-1/0 /3.1; } } 3. Config ure the Ethernet pr otection gr oup: [edit] prot ocols { prot ection-group { ethernet-ring pg103 { ea st-interf ace { contr ol-channel ge-1/0 /3.1; } west-int erfa ce { contr ol-channel ge-1/0 / 4.
} } } R elat ed Documenta tion MX Series Etherne t Service s Rout ers S olutions P ag e • • Ethernet Ring P rote ction on pag e 145 • Exampl e: Vie wing Ethernet Ring Pr otection S ta tus—Norm.
an RPL owner . The ring-1 RPL o wner is CS1; the ring-2 RPL o wner is CS2. T he RPL owners block or unbl ock the RPL as conditions r equire and initia te R-AP S messag es. Each ring instanc e has t wo int erfac e ports (an ea st int erfac e and a west int erf ace) tha t participa te in the instanc e.
T able 5: Components of the Net work T opolog y Set tings Propert y • ring-1 —Dat a channel [200,300] • ring-2 —Dat a channel [500,6 00] Ring instanc es T wo cust omer sites ar e connect ed to.
T able 5: Components of the Net work T opolog y (c ontinued) Set tings Propert y AS1 ha s the foll owing pr otection gr oup properties: • Eas t interf ace— ge-2/ 0/5. 0 . • W est interfa ce— ge-2/1/ 1.0 . • Dat a channel for ring-1 — VLAN 200 , VLAN 300 .
set routing-inst ances vs bridg e-domains bd300 vlan-id 300 set routing-inst ances vs bridg e-domains bd500 vlan-id 500 set routing-inst ances vs bridg e-domains bd600 vlan-id 600 St ep-by-S tep Proc .
interf aces { ge-3/2/ 4 { vlan-ta gging; unit 0 { famil y bridge { interf ace-mode trunk; vlan-id-list 100-1000; } } } ge-5/2/3 { vlan-ta gging; unit 0 { famil y bridge { interf ace-mode trunk; vlan-id-list 100-1000; } } } prot ocols { prot ection-group { ethernet-ring ring-1 { ea st-interf ace { contr ol-channel { ge-3/2/ 4.
} } } } routing-instanc es { vs { instanc e-type virtual-swit ch; interf ace g e-3/2/ 4.0; interf ace g e-5/2/3.0; bridge-domains { bd100 { vlan-id 100; } bd101 { vlan-id 101; } bd200 { vlan-id 200; }.
set bridge-domains bd200 vl an-id 200 set bridge-domains bd300 vl an-id 300 set bridge-domains bd500 vl an-id 500 set bridge-domains bd6 00 vlan-id 600 St ep-by-S tep Proc edure T o config ure ERP on .
interf ace-mode trunk; vlan-id-list 100-1000; } } } ge-2/ 0/8 { unit 0 { famil y bridge { interf ace-mode trunk; vlan-id-list 100-1000; } } } prot ocols { prot ection-group { ethernet-ring ring-1 { ea st-interf ace { contr ol-channel { ge-2/ 0/ 4.0; vlan 100; } } west-int erfa ce { contr ol-channel { ge-2/ 0/8 .
bd101 { vlan-id 101; } bd200 { vlan-id 200; } bd300 { vlan-id 300; } bd500 { vlan-id 500; } bd600 { vlan-id 600; } } } Config uring ERP on AS1 CLI Quick Config uration T o quickl y configur e AS1 f or.
NO TE: Alwa ys c onfigure the ea st-interf ace st at ement first, bef ore config uring the west-int erfac e stat ement. [edit protection-group] user@as1# set ethernet-ring ring-1 e ast-int erfac e control-channel g e-2/0/5.
} west-int erfa ce { contr ol-channel { ge-2/1/ 1.0; vlan 100; } } data-channel { vlan [200 , 300]; } } } } prot ection-group { ethernet-ring ring-2 { ea st-interf ace { contr ol-channel { ge-2/ 0/5. 0; vlan 101; } } west-int erfa ce { contr ol-channel { ge-2/1/ 1.
V erifica tion T o confirm tha t the ERP configura tion for multipl e ring instanc es is opera ting, perf orm these ta sks: • V erifying the Ethernet Pr otection Ring on C S1 on pag e 166 • V erif.
ge-5/2/3 123 forwarding Ethernet ring data channel parameters for protection group ring-2 Interface STP index Forward State ge-3/2/4 124 discarding ge-5/2/3 125 forwarding Meaning T he output display ed sho ws the S TP index number used b y each int erfa ce in ring instanc es ring-1 and ring-2 .
Node ID Link Blocked Ring-1 NR No No No 00:21:59:03:ff:d0 Ring-2 NR No Yes Yes Meaning T he output display ed sho ws that pr otec tion groups ring-1 and ring-2 ha ve a R equest/ state of NR , meaning ther e is no request f or APS on the ring. If a R equest/ stat e of SF is displa yed , it indica tes ther e is a signal fail ure on the ring.
ge-2/0/4 300 44 default — switch/bd300 ge-2/0/8 300 45 default-switch/bd300 Ethernet ring IFBD parameters for protection group ring-2 Interface Vlan STP Index Bridge Domain ge-2/0/4 500 46 default .
Ethernet ring data channel parameters for protection group ring-2 Interface STP index Forward State ge-2/0/5 24 forwarding ge-2/1/1 25 forwarding Meaning T he output display ed sho ws the S TP index number used b y each int erfa ce in ring instanc es ring-1 and ring-2 .
Exampl e: Viewing Etherne t Ring Prot ection S ta tus—Normal Ring Opera tion Under normal opera ting conditions, when Etherne t ring prot ection is config ured c orrectl y , the ring prot ection lin.
R outer 3 will see almost identic al informa tion. user@router2> show pr otection-group e thernet-ring interf ace Ethernet ring port parameters for protection group pg102 Interface Control Channel Forward State Ring Protection Link End ge-1/2/1 ge-1/2/1.
Originator Remote Node ID No 00:01:02:00:00:01 Note tha t the ring prot ection link is no l onger bl ocke d and the node is no long er marked as origina tor .
Signal Failure Admin State Clear IFF ready set IFF ready Note tha t the f ailed int erfa ce ( ge-1/ 0/2. 1 ) is not forw arding. R outer 3 will see almost identical inf ormation.
P ART 4 Inde x • Index on pa ge 177 175 Cop yright © 2010, Juniper Netw orks, Inc..
Cop yright © 2010, Juniper Netw orks, Inc. 17 6 Junos 10. 4 MX Series Etherne t Services R outers Sol utions Guide.
Inde x S ymbols #, comments in c onfigur ation sta tements..................xxii ( ), in synta x descriptions...................................................xxii < >, in synta x descriptions...................................................xxi [ ], in config ura tion stat ements.
VLAN tag ne sting............................................................13 VLAN tag s...........................................................................11 Ethernet fr ame dela y config uring ...............................................
R ring prot ection Ethernet ov erview................................................145, 147 rout ers defined .................................................................................. 6 S sta tistics Ethernet frame dela y....................
Cop yright © 2010, Juniper Netw orks, Inc. 180 Junos 10. 4 MX Series Etherne t Services R outers Sol utions Guide.
Un punto importante, dopo l’acquisto del dispositivo (o anche prima di acquisto) è quello di leggere il manuale. Dobbiamo farlo per diversi motivi semplici:
Se non hai ancora comprato il Juniper Networks 10.4 è un buon momento per familiarizzare con i dati di base del prodotto. Prime consultare le pagine iniziali del manuale d’uso, che si trova al di sopra. Dovresti trovare lì i dati tecnici più importanti del Juniper Networks 10.4 - in questo modo è possibile verificare se l’apparecchio soddisfa le tue esigenze. Esplorando le pagine segenti del manuali d’uso Juniper Networks 10.4 imparerai tutte le caratteristiche del prodotto e le informazioni sul suo funzionamento. Le informazioni sul Juniper Networks 10.4 ti aiuteranno sicuramente a prendere una decisione relativa all’acquisto.
In una situazione in cui hai già il Juniper Networks 10.4, ma non hai ancora letto il manuale d’uso, dovresti farlo per le ragioni sopra descritte. Saprai quindi se hai correttamente usato le funzioni disponibili, e se hai commesso errori che possono ridurre la durata di vita del Juniper Networks 10.4.
Tuttavia, uno dei ruoli più importanti per l’utente svolti dal manuale d’uso è quello di aiutare a risolvere i problemi con il Juniper Networks 10.4. Quasi sempre, ci troverai Troubleshooting, cioè i guasti più frequenti e malfunzionamenti del dispositivo Juniper Networks 10.4 insieme con le istruzioni su come risolverli. Anche se non si riesci a risolvere il problema, il manuale d’uso ti mostrerà il percorso di ulteriori procedimenti – il contatto con il centro servizio clienti o il servizio più vicino.
