|
|
You have to configure simple OSPF authentication, but you are not provided with the secret being used by the remote router. How can you determine the correct secret?
r3 is an ASBR in a NSSA, and you need to summarize the external routes 192.168.0/24 through 192.168.3/24. What is wrong with the following configuration?
[edit protocols ospf] lab@r3# show reference-bandwidth 1g; area 0.0.0.1 { nssa { default-lsa { default-metric 1; type-7; } no-summaries; } area-range 10.0.4.0/22; area-range 192.168.0.0/22; interface fe-0/0/0.0 { metric 20; } interface fe-0/0/1.0 { metric 20; } }
Based on the following configuration, will the router's loopback address be advertised into OSPF, and if so, what type of LSA will be used to report the lo0 address?
[edit] lab@r3# show routing-options static { route 10.0.200.0/24 { next-hop 10.0.1.102; no-readvertise; } } router-id 10.0.3.3; [edit] lab@r3# show protocols ospf reference-bandwidth 1g; area 0.0.0.1 { nssa { default-lsa { default-metric 1; type-7; } no-summaries; } area-range 10.0.4.0/22; interface fe-0/0/0.0 { metric 20; } interface fe-0/0/1.0 { metric 20; } } area 0.0.0.0 { authentication-type md5; # SECRET-DATA interface at-0/1/0.35 { authentication-key "$9$I-EhyKsYoaUH" key-id 1; # SECRET-DATA } interface so-0/2/0.100 { interface-type nbma; authentication-key "$9$6M9/CpBW87Nb2" key-id 1; # SECRET-DATA neighbor 10.0.2.6 eligible; } }
You have just configured area 20 as a stub, but you note that external LSAs are still in the LSDB as shown next. Is this a problem?
[edit] lab@r7# set protocols ospf area 20 stub [edit] lab@r7# commit commit complete [edit] lab@r7# run show ospf database OSPF link state database, area 0.0.0.20 Type ID Adv Rtr Seq Age Opt Cksum Len Router *10.0.9.7 10.0.9.7 0x80000002 88 0x0 0x2584 72 OSPF external link state database Type ID Adv Rtr Seq Age Opt Cksum Len Extern 10.0.5.0 10.0.3.4 0x80000039 620 0x2 0x7fb7 36 Extern 192.168.0.0 10.0.9.6 0x8000001c 1579 0x2 0x2e0a 36 Extern *192.168.0.0 10.0.9.7 0x80000064 701 0x2 0x9757 36
Your goal is to advertise only 192.168.x/24 routes to a RIP neighbor. What is wrong with the following RIP export policy?
[edit] lab@r6# show policy-options policy-statement broke term 1 { from { protocol rip; route-filter 192.168.0.0/16 orlonger; } } then accept;
What is needed to make a Juniper Networks router generate a default route into a stub or NSSA?
|
|