ページに移動 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. All right s reserve d. This pr ogram and its do ...
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 OR O THERWISE EXPRESSING Y OUR AGREEMENT T O THE TERMS CONT AINED HEREIN, YOU ( AS CU ST OMER OR IF YOU ARE NO T THE CUST OMER, AS A REPRESENT A TIVE ...
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) use Embe dded Softwar e (or mak e it avail able f or use) on Juniper equipment that the Cust omer did not originally purcha se from Juniper or an author ...
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 .7201 thr ough 227 .7202-4 , F AR 12.212, F AR 27 .405(b ) ...
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......................................3 P art 2 Basic S olutions f or MX Series R outer s Chapter 2 Basic L ay er 2 Fea tures on MX Series Rout e ...
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 ........................................................x v i i i A u d i e n c e..................................... ...
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 . . . . . . . . . . . . . . . . 40 Chapter 4 VLANs Within Bridg e Domain and ...
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 . . . . . . . . . . . . . . . . . . . . 95 Exampl e: Config uring Policing and Marking o ...
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 Guide ...
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 .....................................1 5 Figure 3: ...
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 . . . . . . . . . . . . . . . . . . . . . . 148 Figure 2 4: ERP with Multipl e Prot e ...
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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxi P art 3 Ethernet Fil tering, Monitoring, and F ...
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 on pag e xvii • Objectiv es on pag e xviii • Audienc e on page xviii • Support ed R outing Pla tf orms on page xix • Using the Index es on pa ...
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. NO TE: For additional information about Junos O S—either corre ctions to or informa tion that might ha ve been omit ted from this g uide—see the softwa ...
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. Using the Exampl es in This Manual If you w ant ...
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. From the HTML or PDF v ersion of the manual, cop y a config ura tion ...
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. W arning Alert s you to the risk of per sonal injury from a l aser . Las er warning T a ...
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. T he set of choices is often encl osed in parenthe ses for cl arity . | (pipe symbol) rsvp { # R ...
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 .juniper .net/ us/ en/loc al/ pdf/ resour ce-gu ...
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 2 and Lay er 3 on page 7 • 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 ...
• 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. A s et of tools us ed to pr ovide manag ement for link s, device , a ...
• 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 pag e 15 • Lay er 2 Netw orking St andards on pag e 17 Netw orking and Internetw orking with Bridge s and Rout ers T raditionall y , different har ...
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. On the Int ernet, th ...
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 ge 6 • 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 ...
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. Ther e are many re asons f or the continued need f or IP , not the le ast of ...
• 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 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 pag e ...
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. 1Q (formerl y IEEE 802. 1q) specifica tion. T oge ther , the four ...
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. Howe ver , there is a major limita tion in trying to buil d forwar ding tabl es bas ...
• 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 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 agged Fr ames on ...
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. The VLAN l abels in the pack et are s tacke d wit ...
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 . The fr ame can ha ve tw o VLAN tag s (inner and outer), one tag ( ...
• 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 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 agged Fr ames on ...
• 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 agged Fr ames on pag e 11 • 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 ...
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 onments on pag e 43 • Bulk Adminis tra tion of Lay er 2 Fea tures on MX Serie s Rout ers on pa ge 59 • Dynamic Pr ofiles f or VLAN Interf aces and P ...
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 pag e 22 • Exampl e St ep: Configuring Int erf aces and VLAN T ags on pag e 24 • Exampl e St ep: Configuring Bridg e Domains on pag e 30 • Exam ...
• 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. Just a s routing pr otocol s use pack ets t o detec t and prev ent routing l oops, bridges us e x ...
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 are link ed to the Int ernet, and R outer 1 and R outer 3 ar e also link ed to s witches c onfigured with a r ange of VLANs, as sho w ...
• 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 . R outer 3 has an a cc ess interf ace which pro vides bridging on VLAN 200 ...
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.3ad ae2; } } interf aces g e-2/ 1/ 1 { g ...
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-id-list 200-205; # T his trunk port is part of VLAN rang e 200–205 } } } interf aces g e-2/2/ 6 { encapsul ation fl exibl e-ethernet-service s; vla ...
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.3ad ae3; } } interf aces g e-5/ 1/ 1 { 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 interf ace s on router } } } interf aces g e-2/2/2 { encapsul ation fl exibl e-etherent-servic es; vlan-ta gging; # Cust omer interf ace uses singl y-tagg ...
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.3ad ae2; } } interf aces a e2 { unit 0 { famil y bridge { interf ace-mode trunk; vlan-id-list 100 ...
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.100; } vlan200 { domain-type bridge; vlan-id 200; interf ace g e-2/2/ 1.200; interf ace g e-2/ ...
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.100; } vlan200 { domain-type bridge; vlan-id 200; interf ace g e-3/3/3.200; 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 . The L ...
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 tch interf ace a e2; interf ace a e3; msti 1 { vlan100; # T his VLAN corresponds t o MS TP instance 1 } msti 2 { vlan200; # T his VLAN corresponds t ...
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 21 • Exampl e R oadmap: Config uring a Basic Bridg e Domain Environment on pag e 22 • Exampl e St ep: Configuring Int erf aces and VLAN T ags on pa ...
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 . Otherwise, the MA C address is l earned or look ed ...
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 .0 .20.3/24; # R ...
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.8/24 { } } } } bridge-domains { vlan-100 { domain-type bridge; vlan-id 100; interf ace g e-2/2/2.1 ...
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 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 pag e 22 • Exampl 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 a S witching En vironment Juniper Netw orks MX S eries Ethernet Servic es R outer s include all standar d Ethernet capabilities a s well a s enhance d ...
• 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. Bef ore you be gin, you shoul d hav e already c onfigure d a basic bridg ...
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. Chapter 3: V irtual Swit ches ...
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 pag e 44 • Config uring a Normalized VLAN f or T ransl ation or T agging on pag e 45 • Config uring Learning Domains f or VLAN IDs Bound to Logic ...
• 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. P acke ts rec eived o ver a La yer 2 l ogical int erfa ce f or bridging when a normali ...
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. T he VPLS c onfigura tion is not co ver ed in this topic. For mor e informa tio ...
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 ce do not mat ch the normalized VLAN t ags within the pack et, then appr opriat e VLAN tag oper ations (such as push-push, pop-pop , pop-swap , sw ap- ...
• 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. R elat ed Documenta ...
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. Figur e 7: Pro vider Bridge Ne twork Usi ...
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 at Sit e 3: VLAN 100 • L2-PE4 at Sit e 4: VLAN 300 NO TE: The configur ations in this chapt er are onl y partial exampl es of compl et e and function ...
} } 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 on the pr ovider # pseudowir e } unit 11 { encapsul ation vlan-bridg e; vlan-ta gs outer 6 00 inner 300; # This plac es tw o VLAN tags on the pr ovid ...
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 . • Logic al interf ac e ge-3/0 /0 .1 c onfigured on ph ysical port g e-3/0 /0 . • Logic ...
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. 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 ti ...
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. The VLANs a t each site a ...
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. 1; interf ace g e-3/0 /0. 1; } # End of cust omer-c1-vsi cust omer-c2-vsi { instanc e-type vpls; vlan-id none; # T his will remov e the VLAN tags fr om pack ets sent on VPLS f or cust ...
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. The rec eive d or config ured VLAN ta gs are not c onsidered when the MA C addre ...
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. Sit e 1 is connec ted 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 ...
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. The ...
} # 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 . The vl an-id all stat ...
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 VLAN ID List on p age 59 • Exampl e: Config uring Multipl e Bridge Domains with a VLAN ID List on pa ge 60 Bulk Config ura tion of VLANs and Bridg e ...
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 { ... # Other logic al interf ace st atement s famil y bridge { interf ace-mode trunk # T ransla tion is only f or trunks vlan-id-list [ 100 500–60 ...
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. Also , the explicit bridg e ...
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—Ba sic Sol utions on page 64 • Exampl e: Config uring VPLS Pseudo wires with Dynamic P rofil es—Compl ex Sol utions on page 68 Dynamic Pr ofile s f ...
• 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 68 Exampl e: Configuring VPL S Pseudo wires with Dynamic Pr ofil es—Basic S olutions The f ollo wing limita tions apply t o dynamic profil es f or VP ...
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. T he broadc ast pack et ...
} 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. With this c onfigura tion, broadca st pack ets inside fr ames arriving with VLAN identifier 10 ...
} } 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. T he same configur ation c an be acc omplished using dynamic ...
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). The br oadca st pack et and frame s egressing g e-0/ 0/2 ...
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.0; ... # Other interf aces and s tat ements for A cc ounting } others { vlan-id—list [ 40 50 ]; # Other depar ...
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 s $junos-interf ace-if d-name { unit $junos-underl ying-unit-number { vlan-id 200; # T his is the outer ta g famil y bridge { interf ace-mode trunk; ...
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. Engineering frames (VLAN 30 ) are onl y swit ched within the interf ac es listed within bridg ...
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. This c onfigura tion adds tag transl ation to the VPL S pseudowir ...
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 on pa ge 74 • Exampl e: Config uring DHCP Rel ay in a VPL S R outing Instance Envir onment on pag e 75 MX Series R outer a s a Lay er 2 DHCP R ela y ...
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 DHCP Rel ay in a VPL S R outing Instance Envir onment on pag e 75 Exampl e: Configuring DHCP R ela y in a Bridge Domain VLAN Envir onment The f ollo ...
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. NO TE: This is not a compl ete r outer c onfigura tion. The r outer ha s three int erfa ...
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 • show dhcp r elay binding r outing-instance v s1 bridge-domains bd1 det ail user@router1> show dhcp r elay binding r outing-instance v s1 bridg ...
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 Ethernet Interworking on pa ge 79 MX Series R outer A TM Ethernet Int erworking Function Y ou can config ure an MX Serie s router a s part of an 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. Figure 11: A TM Ethernet VLAN Int erworking P ack et S tructure g017429 MPLS Inner VLAN L3 Ether type SA D A Ethernet MPLS Inner VLAN L3 Ether type ...
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 . Figure 13: A TM Ethernet VLAN Int erworking CE1 CE2 g017428 A TM DSLAM Ser vice Stack ed V ...
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] 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 ...
} } } 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 .1. 1.10/2 4; } famil y mpls; } } prot ocols { mpls { interf ace g e-0/2/ ...
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> show l2cir cuit connections Layer-2 Circuit Connections: Legend for connection status (St) EI -- encapsulation invalid NP -- interface h/w not present MM ...
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. 0; } ospf { area 0 .0 .0 .0 { interf ace g e-5 ...
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 .0; } ospf { area 0 .0 .0 .0 { interf ace g e-0/2/8 .0; inter ...
} } } } 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 connection status (St) EI -- encapsulation invalid NP -- interface h/w not present MM -- mtu mismatch Dn -- down EM -- encapsulation mismatch VC-Dn -- Virtu ...
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 .255.1 71.45; to 10 .255.1 71.14; } label-s witched-pa t ...
} 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 .255.1 71.45; to 10 .255.1 71.14; } interf ace g e-0/2/8 .0; } isis { interf ace g e-0 ...
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: remote interface switching WE -- wrong encapsulation lsp-sw: LSP switching DS -- disabled tx-p2mp-sw: transmit P2MP switching Dn -- down rx-p2mp-sw: r ...
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.1 71.14; to 10 .255.1 71.45; } interf ace g e-5/0 /0. 0; } isis { interf ace g e-5/0 /0. 0; } co ...
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 .255.1 71.45; } label-s witched-pa th lsp1-2 { from 10 .255.1 71.45; to 10 .255.1 71.14; } inter ...
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 for connection types UN -- uninitialized if-sw: interface switching NP -- not present rmt-if: remote interface switching WE -- wrong encapsulation ls ...
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.3ah O AM Link-Faul t Manag ement on page 137 • E ...
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 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 ...
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.1p Bit s on page 99 • Exampl ...
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, unknown unic ast, and non-IP mul tica st to 50 kbps: [edit fir ewall] policer bc ast-unkno wn-unicast-non-ip-mc ast-polic er { if-ex ceeding { bandw ...
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 { encapsul ation vlan-vpl s; vlan-id 9; famil y vpls { filt er { input cust omer-1; } } } } R elat ed Documenta tion MX Series Etherne t Service s Rout er ...
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. Appl y evil-mac-address a s an input filter t o vlan100200 on R outer 1: [edit r outing-instance s] virtual-swit ch-R1-1 { bridge-domains { vlan100200 { domain-type bridge; forw arding-opt ...
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 . This e xampl e Lay er 2 bridging firew all filt er finds any i ...
• 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 firew all filt er to pr ovide ma tching on the pack et l oss priority (PLP) l evel c arried in the fr ame, use the loss-priorit y or loss-priority-e xc ep ...
} 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-configur e-forwar ding; } } } } R elat ed Documenta tion • MX Series Etherne t Service s Rout ers S olutions P ag e • Fire wall Fil ters f or Bridge ...
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 104 • Exampl e: Config uring Ethernet CFM ov er VPLS on pa ge 105 • Exampl e: Config uring Ethernet CFM on Bridge C onnections on pag e 112 • 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. Aft er a fa ult is det ect ed, the l oopback protoc ol performs ...
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. Ther e is also a maintenanc e interme diat e point ...
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-services { bandwidth 1g; } } } [edit int erfac es] ge-1/ 0/7 { encapsul ation fl exibl e-ethernet-service s; vlan-ta gging; unit 1 { encapsul ation vlan-vpl ...
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 .0; } mpls { label-s witched-pa th PE1-to-PE2 { to 10 .100 .1. 1; } in ...
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 erfac es] ge-5/ 0/9 { vlan-ta gging; encapsul ation fl exibl e-ethernet-service s; unit 1 { encapsul ation vlan-vpl s; vlan-id 2000; } } ge-5/2/7 { unit ...
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 .200. 1.1; } interf ace g e-5/2/7 .0; } bgp { group PE2-t o-PE1 { type internal; loc al-addres ...
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 .100 . 1.10 /24; } famil y mpls; } } lo0 { unit 0{ famil ...
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 0 { vlan-id 2000; } } [edit pr otoc ols oam] ethernet { connec tivity-faul t-manag ement { maintenanc e-domain customer { le vel 7; maintenanc e-assoc ...
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 ations, A dministra tion, and Maintenanc e on pag e 103 • Ethernet O AM Connec tivity Fa ult Manag ement on pag e 104 • Exampl e: Config uring Eth ...
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-faul t-manag ement { maintenanc e-domain customer { le vel 7; maintenanc e-associa tion customer-sit e1 { continuity-che ck { interv al 1s; } mep 700 ...
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 .0; in ...
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.0; interf ace g e-5/ 1/7 .0; } [edit ...
• 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. T his functionality is similar t o that support ed b y theIEEE 802.3ah LFM ...
} } } } 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 { connec tivity-faul t-manag ement { maintenanc e-domain privat e { le vel 0; maintenanc e-associa tion privat e-ma { continuity-che ck { interv al 1 ...
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 surements on pa ge 122 • T riggering an Ethernet Fr ame Dela y Measur ements Session on p age 123 • Vie wing Ethernet Frame Del ay Me asur ements Sta ti ...
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 . The cl ocks do not need t o be synchroniz ed at the tr ansmitting and re ...
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. Y ...
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 . } R elat ed Documenta tion MX Series Etherne t Service s Rout ers S olutions P ag e • • Ethernet Fr ame Dela y Measur ements o ...
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. The def ault is 1 sec ond. 1–255 sec onds (def aul t: 1) wait time If you a tt empt to monit or dela ys to a none xistent MA C address, you must e xit the applica tio ...
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 . Exis tin ...
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.log siz e 1g files 2 w orld-r eadabl e; fla g all; } linktr ace { path-da taba se-size 2 ...
} 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; } 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 ...
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 LTMs sent : 0 LTMs received : 0 LTRs sent : 0 LTRs received : 0 Sequence number of next LTM request : 0 1DMs sent : 10 Valid 1DMs received : 0 Invalid ...
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 . user@MX-1> show oam etherne t connectivit y-faul t-management mep-st atistics maintenanc e-domain md6 MEP identifier: 2 ...
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. T his is because one-wa y delay me asur ement ...
} } } 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; } maintenanc e-domain md6 { le vel 6; maintenanc e-associa tion ma6 { continuity-che ck { interv al 100ms; hold-int erval 1; } mep 201 { interf ac ...
} 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 . user@MX-1> monitor etherne t delay-me asurement tw o-way mep ...
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 : 0 LTRs sent : 0 LTRs received : 0 Sequence number of next LTM request : 0 1DMs sent : 0 Valid 1DMs received : 0 Invalid 1DMs received : 0 DMMs sent : ...
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 . user@MX-1> show oam etherne t connecti ...
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.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 { l ...
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 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/2; direction do wn; auto-d ...
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: Config uring Ethernet LFM for C CC on pa ge 139 • Exampl e: Config uring Ethernet LFM for A ggreg at ed Ethernet on pag e 140 • Exampl e: Config uring ...
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 . This r esult s in notifica tions to various ...
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 Link Fa ult Manag ement on pag e 137 • Exampl e: Config uring Ethernet LFM for C CC on pa ge 139 • Exampl e: Config uring Ethernet LFM for A ggre ...
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 { interf ace g e-1/0 /0 { pdu-interv al 1000; pdu-threshol d 5; } } } } } R elat ed Documenta tion MX Series Etherne t Service s Rout ers S olutions ...
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.3ad ae0; } } interf aces a e0 { unit 0 { ...
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 Series Etherne t Service s Rout ers S olutions P ag e • • Ethernet O AM Link Fa ult Manag ement on pag e 137 • Exampl e: Config uring Ethernet LF ...
} 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. 11.11.2/24; } } } prot ocols { oam { ethernet { link-faul t-management { interf ace g e- ...
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 Ethernet Ring Pr otection f or MX Serie s Rout ers on pag e 148 • Exampl e: Config uring Load Bal ancing Within Etherne t Ring Prot ection f or MX Ser ...
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 . • Normal node— All other nodes on the ring (that is, those tha t are not the RPL owner node) opera te a s normal nodes and ha ve no special r ole on the ri ...
• 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 . ERP is use ...
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 1 (RPL Owner) C onfigura tion on pag e 149 • R outer 2 C onfigura tion on pag e 150 • R outer 3 C onfigura tion on pag e 152 Exampl e ...
• 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.1 . T he prot ection group is pg103 . NO ...
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-faul t-manag ement { action-pr ofile rmep-def aults { def ault-ac tion { interf ace-do wn; } } maintenanc e-domain d1 { le vel 0; maintenanc e-associa ti ...
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. Config ure the bridge domain: [edit] bridge-domains { bd1 { domain-type bridge; interf ace ...
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. Conf ...
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.1; } } } } 4. C onfigure Etherne t OAM: [edit] prot ocols { oam { e ...
} } } 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—Normal Ring Opera tion on pag e 171 • Exampl e: Vie wing Ethernet Ring Pr otection S ta tus—Ring Fail ure C ondition on page 172 Exampl e: Configuring ...
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. Interf ace ge-2/ 0/8 .0 , the we st interf ace o ...
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 A S 1: • Cust omer site 1, VLAN 200 and VLAN 300 • Cust omer site 2, VLAN 500 and VLAN 600 Cust omer sites CS1 ha s the foll owing prot ection gr ...
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 . • Dat a channel for ring-2 — VLAN 500 , VLAN 600 . AS1 ha s the foll owing bri ...
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 edure T o config ure ERP on C S1: Config ure the trunk interf ace ge-3/2/ 4 to c onnect CS1 t o CS2 and the trunk int erf ace ge-5/2/3 t o connec t CS ...
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. 0; vlan 100; } ring-pr ...
} } } } 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; } bd300 { vlan-id 300; } bd500 { vlan-id 500; } bd600 { vlan-id 600; } } } } } Config uring ERP on CS2 CLI Quick Config uration T o quickl y configur e ...
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 C S2: Config ure the trunk interf ace ge-2/ 0/ 4 to c onnect CS2 t o CS1 and trunk int erfa ce ge-2/ 0/8 t o connec t CS2 t o CS1, and config ure the ...
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 .0; vlan 100; } } data-channel { vlan ...
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 ERP , copy the f ollo wing commands and pa ste them int o the swit ch terminal windo w of AS1: [edit] set interf aces g e-2/0 /5 unit 0 famil y bridg ...
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. 0 user@as1# set ethernet-ring ring-1 e ast-int erfac e control-channel vl an 100 user@as1# set ethernet-ring ring-1 w est-inte ...
} 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.0; vlan 101; } } data-channel { vlan [500 , 600]; } } } bridge-domains { bd100 { vlan ...
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 erifying the Data Channel C S1 on pag e 166 • V erifying the VLANs on CS1 on pag e 167 • V erifying the Ethernet Pr otection Ring on C S2 on pag e 167 ...
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 . The S TP index contr ols the forw arding beha vior fo ...
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. T he out ...
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 — switch/bd500 ge-2/0/8 500 47 default-switch/bd500 ge-2/0/4 600 46 default — switch/bd600 ge-2/0/8 600 47 default-switch/bd600 Meaning T he output ...
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 . The S TP index contr ols the forw arding beha vior for a set of VLANs on the da ...
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 link (RPL) o wner (Rout er 1 in the configur ation exampl e) will see the foll owing: R outer 1 Opera tional Commands (Normal Ring Opera tion) user@route ...
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.1 forwarding No ge-1/0/2 ge-1/0/2.1 forwarding No Signal Failure Admin State Clear IFF ready ...
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 . user@router1> show pr otection-group e thernet-ring interf ace Ethernet ring port parameters for protection group pg101 Interface Control Channel Forward State Ring Protection Link End ge- ...
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. user@router2> show pr otection-group e thernet-ring node-stat e Ethernet ring APS State Event Ring Protection Link Owner pg102 idle NR-RB No Restore Timer Quard Timer O ...
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.......................................xxii { }, in config ur ...
VLAN tag ne sting............................................................13 VLAN tag s...........................................................................11 Ethernet fr ame dela y config uring ....................................................................... 122 exampl es.......................................................125, 1 ...
R ring prot ection Ethernet ov erview................................................145, 147 rout ers defined .................................................................................. 6 S sta tistics Ethernet frame dela y..........................................123, 124 support, technic al See t echnical support synta x conv entions..... ...
Cop yright © 2010, Juniper Netw orks, Inc. 180 Junos 10. 4 MX Series Etherne t Services R outers Sol utions Guide ...
Juniper Networks 10.4のメーカーから受け取ることができるドキュメントは、いくつかのグループに分けられます。その一部は次の通りです:
- #BRANDの図面#
- 10.4の取扱説明書
- Juniper Networksの製品カード
- パンフレット
- またはJuniper Networks 10.4の消費電力シール
それらは全部重要ですが、デバイス使用の観点から最も重要な情報は、Juniper Networks 10.4の取扱説明書に含まれています。
取扱説明書と呼ばれる文書のグループは、Juniper Networks 10.4の取り付け説明書、サービスマニュアル、簡易説明書、またはJuniper Networks 10.4のユーザーマニュアル等、より具体的なカテゴリーに分類されます。ご必要に応じてドキュメントを検索しましょう。私たちのウェブサイトでは、Juniper Networks 10.4の製品を使用するにあたって最も人気のある説明書を閲覧できます。
Juniper Networks 10.4デバイスの取扱説明書はどのようなものですか？
取扱説明書は、ユーザーマニュアル又は単に「マニュアル」とも呼ばれ、ユーザーがJuniper Networks 10.4を使用するのを助ける技術的文書のことです。説明書は通常、全てのJuniper Networks 10.4ユーザーが容易に理解できる文章にて書かれており、その作成者はその分野の専門家です。
Juniper Networksの取扱説明書には、基本的な要素が記載されているはずです。その一部は、カバー/タイトルページ、著作権ページ等、比較的重要度の低いものです。ですが、その他の部分には、ユーザーにとって重要な情報が記載されているはずです。
1. Juniper Networks 10.4の説明書の概要と使用方法。説明書にはまず、その閲覧方法に関する手引きが書かれているはずです。そこにははJuniper Networks 10.4の目次に関する情報やよくある質問、最も一般的な問題に関する情報を見つけられるはずです。つまり、それらはユーザーが取扱説明書に最も期待する情報なのです。
2. 目次。Juniper Networks 10.4に関してこのドキュメントで見つけることができる全てのヒントの目次
3. Juniper Networks 10.4デバイスの基本機能を使うにあたってのヒント。 Juniper Networks 10.4のユーザーが使い始めるのを助けてくれるはずです。
4. トラブルシューティング。Juniper Networks 10.4に関する最も重要な問題を診断し、解決するために役立つ体系化された手続き
5. FAQ。よくある質問
6. 連絡先。一人では問題を解決できない場合に、その国におけるJuniper Networks 10.4のメーカー/サービスへの連絡先に関する情報。
Juniper Networks 10.4についてご質問がありますか？
次のフォームを使用してください
見つけた説明書を読んでもJuniper Networks 10.4の問題を解決できない場合、下記のフォームを使用して質問をしましょう。ユーザーのどなたかがJuniper Networks 10.4で同様の問題を抱えていた場合、その解決方法を共有したいと考えるかもしれません。