What are two causes for this behavior?

— Exhibit —
protocols {
bgp {
group isps {
type external;
peer-as 13090194;
multipath multiple-as;
neighbor ;
neighbor ;
}
}
}
— Exhibit —
Refer to the Exhibit.
The exhibit shows the complete BGP configuration for a router. The network operator reports that
both peering sessions are up, but the router is not conducting per-flow load balancing over the
connections to these two peers.
What are two causes for this behavior? (Choose two.)

— Exhibit —
protocols {
bgp {
group isps {
type external;
peer-as 13090194;
multipath multiple-as;
neighbor ;
neighbor ;
}
}
}
— Exhibit —
Refer to the Exhibit.
The exhibit shows the complete BGP configuration for a router. The network operator reports that
both peering sessions are up, but the router is not conducting per-flow load balancing over the
connections to these two peers.
What are two causes for this behavior? (Choose two.)

A.
The forwarding-table export policy is not configured to cause per-flow load balancing.

B.
The multiple-as parameter causes BGP to only choose multiple paths to different ASs, rather
than multiple paths to the same AS.

C.
The router has different IGP metrics to these BGP peers.

D.
The BGP peers are not sending identical advertisements over the two sessions.

Explanation:



Leave a Reply 0

Your email address will not be published. Required fields are marked *