Symptom
When TE tunnel is explicitly configured under ospf process and
there is no no "bandwidth" command configured under the "interface TE-tunnel", the tunnel ospf cost
is not well defined (can be one of two different values depends on configuration sequence).
Conditions
-no bandwidth configured on the TE tunnel
-non-default "bandwidth-reference" is configured under ospf
- tunnel is configured under ospf process.
Workaround
Manually configure the ospf cost on the TE tunnel
Further Problem Description
There are two main reasons that TE tunnel is configured under ospf protocol :
- setting TE tunnel ospf cost
- LDP sync (mpls ldp sync-igp-shortcuts)
Fist configuration is not affected because the cost is hardcoded (see workaround)
