which value as the TE cost of each link within the MPLS domain?

When implementing Cisco MPLS TE, the constrained-based path calculations will use which value
as the TE cost of each link within the MPLS domain?

When implementing Cisco MPLS TE, the constrained-based path calculations will use which value
as the TE cost of each link within the MPLS domain?

A.
By default, it will use the IGP metric, or each link can be assigned a specific value using the
admin-weight command.

B.
It can only use the IGP metric as the TE cost.

C.
It will use the interface bandwidth as the TE cost.

D.
Each link must be assigned a TE cost using the metric command.

Explanation:



Leave a Reply 2

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


safronsoup

safronsoup

Modifying the administrative weight

Admin weight is by default equal to the IGP link metric (cost). Increase the TE cost on the link if it is desirable to exclude a certain link from any path computation, while keeping the link available if that link represent the only path available.

XR
mpls traffic-eng
interface Gi0/0/0/1
admin-weight

IOS
interface g0/0
mpls traffic-eng administrative-weight

safronsoup

safronsoup

XR
mpls traffic-eng
interface Gi0/0/0/1
admin-weight “TE weight”

IOS
interface g0/0
mpls traffic-eng administrative-weight “TE weight”