Preview Tool

Cisco Bug: CSCvv08998 - TE metric for MADJ interface is not inherited from of its IGP metric when it is not configured in SR

Last Modified

Oct 01, 2020

Products (1)

  • Cisco ASR 9000 Series Aggregation Services Routers

Known Affected Releases


Description (partial)

For MADJ Interface, TE Metric is not set from its IGP Metric.
Instead, primary interface's igp-metric is used.

Segment routing should be enabled. 
MADJ should be configured.
Cost configured on the MADJ interface should be different from that of the primary interface.

When TE Metric is not configured under Segment Routing AND Primary and MADJ Interface have different IGP Metric.

For Ex: TE metric for  Interface Te0/0/0/0 is not configured under segment routing.

Interface Te0/0/0/0 in Area 0 is configured with IGP metric of 20 and where as MADJ interface Te0/0/0/0 in Area 1 is configured with metric 200.
r5#show ospf int br   | inc Te0/0/0/0

Te0/0/0/0          100    0             20    P2P   1/1
Te0/0/0/0*         100   1             200   P2P   1/1

When we generate ELL in Area 1 we are setting TE metric of 20 instead of 200

r5#show ospf database opaque-area ext-link link-addr $
            OSPF Router with ID ( (Process ID 100)
                Type-10 Opaque Link Area Link States (Area 1)

  LS age: 496
  Options: (No TOS-capability, DC)
  LS Type: Opaque Area Link
  Link State ID:
  Opaque Type: 8
  Opaque ID: 1063
  Advertising Router:
  LS Seq Number: 800000ae
  Checksum: 0xa1ff
  Length: 196

    Extended Link TLV: Length: 172
      Link-type : 1
      Link ID   :
      Link Data :

     ASLA sub-TLV: Length: 44
         SABM Len:    4
         UDABM Len:   0
         SABM Val:    0x50000000 
          Unidir Link Delay : 7 micro sec, Anomalous: no
          Unidir Link Min Delay : 7 micro sec, Anomalous: no
          Unidir Link Max Delay : 7 micro sec
          Unidir Link Delay Variance : 0 micro sec
          TE Metric : 20 ============= This should be 200
Bug details contain sensitive information and therefore require a account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.