You want to share routes between two routing instances that you have configured?
What are two ways to accomplish this task? (Choose two.)
static route with a next-hop of next-table pointing to the appropriate routing table which contains more accurate information rib-groups to mirror routing information from one route-table to another. However, in many cases, in order to make this work, interface-routes also need to be mirrored. RIB Group policy can be used to constrain the routing information instance-import and instance-export statements configured within the individual routing-instances to leak routes from one table to another. Again, policy can be used here to constrain the routing information. This method is more straightforward than the rib-group method A final approach is to use physical interfaces or logical-tunnels to stitch routing-instances and use a routing protocol or static routes across this connection between the two routing-instances.
To share routes between two routing instances on a Junos device, you can configure an instance import policy in one or both instances to import routes from the other instance. Alternatively, a RIB (Routing Information Base) group can be used to share routes between instances. Reference::
Routing Instances Overview, Juniper Networks Documentation
RIB Groups Configuration Guide, Juniper Networks Documentation
Which statement is correct about the FE80;:/10 prefix?
The FE80::/10 prefix is reserved for IPv6 link-local addresses. These addresses are auto-configured on all IPv6-enabled interfaces and can be used for communication within the local link (subnet) only.
Juniper Networks Technical Documentation on IPv6 Addressing
What are three well-known mandatory BGP attributes? (Choose three.)
https://www.catchpoint.com/bgp-monitoring/bgp-attributes
BGP Attribute Categories
There are four categories of BGP attributes:
Well-known mandatory:Recognized by all BGP peers, passed to all peers, and present in all Update messages. Well-known mandatory attributes include:- Next-hop- Origin- AS PATH
Well-known discretionary:Recognized by all routers, passed to all peers, and optionally included in the Update message. Well-known discretionary attributes include:- Local Preference- Atomic Aggregate
Optional transitive:Possibly recognized by BGP routers and passed to BGP peers. Optional transitive attributes are marked as partial when not recognized. Optional transitive attributes include:- Aggregator- Community
Optional non-transitive:Possibly recognized by BGP routers but not passed to peers. Optional non-transitive attributes include:- Multi-exit discriminator (MED)- Originator ID- Cluster-ID
The three well-known mandatory BGP attributes that must be present in every BGP update message are:
Next Hop: Indicates the next hop IP address to reach the advertising BGP peer.
Origin: Indicates how the route was originated, whether it was via IGP, EGP, or incomplete.
AS Path: Lists the autonomous systems that the update has traversed.
Juniper Networks Technical Documentation on BGP Attributes
Exhibit
Referring to the exhibit, how do you verify the status of the tunnel from R1?
Exhibit
Which two statements are correct about the service provider MPLS network shown in the exhibit? (Choose two.)
Rolande
6 days agoCassi
2 months agoKatina
3 months agoThea
4 months agoMona
5 months agoVelda
5 months agoGary
6 months agoLettie
6 months agoMariann
6 months agoEveline
7 months agoLucy
7 months agoMelynda
7 months agoDarrel
8 months agoEllen
8 months agoHollis
8 months agoTayna
9 months agoMitsue
9 months agoSophia
9 months agoCarisa
9 months agoHollis
10 months agoDick
10 months agoJillian
10 months agoTricia
11 months agoFletcher
11 months agoLaila
11 months agoOlene
12 months agoBernadine
1 years agoOlive
1 years agoHershel
1 years agoAnissa
1 years agoMeaghan
1 years ago