Get 50% Discount on All Your Purchases at PrepAway.com - Latest Exam Questions This is ONE TIME OFFER 50% Enter your email address to receive your 50% off dicount code: A confirmation link will be sent to this email address to verify your login. GET YOUR DISCOUNT CODE * We value your privacy. We will not rent or sell your email address.
50% Enter your email address to receive your 50% off dicount code: A confirmation link will be sent to this email address to verify your login. GET YOUR DISCOUNT CODE * We value your privacy. We will not rent or sell your email address.
SPECIAL OFFER: GET 50% OFF 50% Use Discount Code: BRIEF50 A confirmation link was sent to your e-mail. Please check your mailbox for a message from support@prepaway.com and follow the directions. Shop Now
50% Use Discount Code: BRIEF50 A confirmation link was sent to your e-mail. Please check your mailbox for a message from support@prepaway.com and follow the directions. Shop Now
which type of traffic protection mechanism is used for the LSP? seenagapeMay 31, 2013 Refer to the Exhibit. Referring to the exhibit, which type of traffic protection mechanism is used for the LSP? A.fast-reroute B.link-protection C.node-link-protection D.secondary Show Answer
rob says: August 24, 2016 at 2:38 pm https://www.juniper.net/techpubs/en_US/junos11.4/topics/concept/mpls-lsp-link-protect-overview-solutions.html http://www.juniper.net/documentation/en_US/junos13.3/topics/concept/mpls-lsp-multiple-bypass.html http://www.juniper.net/documentation/en_US/junos13.3/topics/usage-guidelines/mpls-configuring-link-protection-on-interfaces-used-by-lsps.html#id-90675 Type: Bypass LSP If fast-reroute was up, You would see something along the lines of 24.24.24.0 From: 192.168.1.2, LSPstate: Up, ActiveRoute: 0 LSPname: to-datacenter, LSPpath: Primary LSPtype: Static Configured Suggested label received: -, Suggested label sent: – Recovery label received: -, Recovery label sent: 300528 Resv style: 1 SE, Label in: -, Label out: 300528 Time left: -, Since: Wed Aug 24 11:22:43 2016 Tspec: rate 85Mbps size 85Mbps peak Infbps m 20 M 1500 Port number: sender 3 receiver 8066 protocol 0 FastReroute desired PATH rcvfrom: localclient Adspec: sent MTU 1500 Path MTU: received 1500 PATH sentto: 20.0.0.3 (ge-0/0/3.0) 7 pkts RESV rcvfrom: 20.0.0.3 (ge-0/0/3.0) 7 pkts, Entropy label: No Explct route: 24.58.0.2 Record route: 20.0.0.3 20.0.0.13 30.0.0.5 30.0.0.15 Detour is Up Detour Tspec: rate 0bps size 0bps peak Infbps m 20 M 1500 Detour adspec: sent MTU 1500 Path MTU: received 1500 Detour PATH sentto: 20.0.0.1 (ge-0/0/2.0) 4 pkts Detour RESV rcvfrom: 20.0.0.1 (ge-0/0/2.0) 3 pkts, Entropy label: No Detour Explct route: 20.0.0.1 20.0.0.7 20.0.0.13 30.0.0.7 30.0.0.13 Detour Record route: 20.0.0.1 20.0.0.7 20.0.0.13 30.0.0.5 30.0.0.15 Detour Label out: 300816 node-link-protection would have a similar output with user@R1> show mpls lsp extensive Ingress LSP: 1 sessions 192.168.5.1 From: 192.168.1.1, State: Up , ActiveRoute: 0, LSPname: lsp2-r1-to-r5 ActivePath: via-r2 (primary) Node/Link protection desired Secondary would show a up if it was a secondary lsp. 0 0
why?
0
0
https://www.juniper.net/techpubs/en_US/junos11.4/topics/concept/mpls-lsp-link-protect-overview-solutions.html
http://www.juniper.net/documentation/en_US/junos13.3/topics/concept/mpls-lsp-multiple-bypass.html
http://www.juniper.net/documentation/en_US/junos13.3/topics/usage-guidelines/mpls-configuring-link-protection-on-interfaces-used-by-lsps.html#id-90675
Type: Bypass LSP
If fast-reroute was up, You would see something along the lines of
24.24.24.0
From: 192.168.1.2, LSPstate: Up, ActiveRoute: 0
LSPname: to-datacenter, LSPpath: Primary
LSPtype: Static Configured
Suggested label received: -, Suggested label sent: –
Recovery label received: -, Recovery label sent: 300528
Resv style: 1 SE, Label in: -, Label out: 300528
Time left: -, Since: Wed Aug 24 11:22:43 2016
Tspec: rate 85Mbps size 85Mbps peak Infbps m 20 M 1500
Port number: sender 3 receiver 8066 protocol 0
FastReroute desired
PATH rcvfrom: localclient
Adspec: sent MTU 1500
Path MTU: received 1500
PATH sentto: 20.0.0.3 (ge-0/0/3.0) 7 pkts
RESV rcvfrom: 20.0.0.3 (ge-0/0/3.0) 7 pkts, Entropy label: No
Explct route: 24.58.0.2
Record route: 20.0.0.3 20.0.0.13 30.0.0.5 30.0.0.15
Detour is Up
Detour Tspec: rate 0bps size 0bps peak Infbps m 20 M 1500
Detour adspec: sent MTU 1500
Path MTU: received 1500
Detour PATH sentto: 20.0.0.1 (ge-0/0/2.0) 4 pkts
Detour RESV rcvfrom: 20.0.0.1 (ge-0/0/2.0) 3 pkts, Entropy label: No
Detour Explct route: 20.0.0.1 20.0.0.7 20.0.0.13 30.0.0.7 30.0.0.13
Detour Record route: 20.0.0.1 20.0.0.7 20.0.0.13 30.0.0.5 30.0.0.15
Detour Label out: 300816
node-link-protection would have a similar output with
user@R1> show mpls lsp extensive
Ingress LSP: 1 sessions
192.168.5.1
From: 192.168.1.1, State: Up , ActiveRoute: 0, LSPname: lsp2-r1-to-r5
ActivePath: via-r2 (primary)
Node/Link protection desired
Secondary would show a up if it was a secondary lsp.
0
0