OSPF Opaque-LSAs may need to support leaf specific to different attributes Linktype,LinkID, LocIfAdr, RemIfAdr etc

[abdulzubaidhar-az]

OSPF Opaque-LSAs may need to support leaf specific to different attributes Linktype,LinkID, LocIfAdr, RemIfAdr etc

Hello,

On running gnmic with opaque-lsa/tlvs, we could see gnmic returns same path with different/multiple values. On looking at the cli output in the router, we see opaque-lsa may contain different attributes like Linktype,LinkID, LocIfAdr, RemIfAdr TEMetric, MaxBW, MaxRsvBW, UnRsvBW, , LinkLocalRemoteIdentifier etc.

gnmic response is confusing as we dont know which opaque-lsa/attribute returns the value as there is no key/leaf defined, can we introduce or add a value as part of sensor path so that the user can identify attributes under opaque-lsa.

Sensor sample with length field under opaque-lsa - This applies to type and value under same sensor path.

existing:

  "Path": "opaque-lsa/traffic-engineering/tlvs/tlv/link/sub-tlvs/sub-tlv/unknown-subtlv/state/length",
  "values": {
    "opaque-lsa/traffic-engineering/tlvs/tlv/link/sub-tlvs/sub-tlv/unknown-subtlv/state/length": 1
  }

proposal:

  "Path": "opaque-lsa/traffic-engineering/tlvs/tlv/link/sub-tlvs/sub-tlv[tlv-type-name=Linktype]/unknown-subtlv/state/length",
  "values": {
    "opaque-lsa/traffic-engineering/tlvs/tlv/link/sub-tlvs/sub-tlv[tlv-type-name=Linktype]/unknown-subtlv/state/length": 1
  }

complete response from gnmic
++++++++++++++++++++++++
"prefix": "openconfig:network-instances/network-instance[name=DEFAULT]/protocols/protocol[identifier=OSPF][name=DEFAULT]/ospfv2/areas/area[identifier=0.0.0.0]/lsdb/lsa-types/lsa-type[type=OSPFV2_AREA_SCOPE_OPAQUE_LSA]/lsas/lsa[link-state-id=1.0.0.100]",
"updates": [
{
"Path": "opaque-lsa/traffic-engineering/tlvs/tlv/link/sub-tlvs/sub-tlv/unknown-subtlv/state/length",
"values": {
"opaque-lsa/traffic-engineering/tlvs/tlv/link/sub-tlvs/sub-tlv/unknown-subtlv/state/length": 1
}
},
{
"Path": "opaque-lsa/traffic-engineering/tlvs/tlv/link/sub-tlvs/sub-tlv/unknown-subtlv/state/length",
"values": {
"opaque-lsa/traffic-engineering/tlvs/tlv/link/sub-tlvs/sub-tlv/unknown-subtlv/state/length": 4
}
},
{
"Path": "opaque-lsa/traffic-engineering/tlvs/tlv/link/sub-tlvs/sub-tlv/unknown-subtlv/state/length",
"values": {
"opaque-lsa/traffic-engineering/tlvs/tlv/link/sub-tlvs/sub-tlv/unknown-subtlv/state/length": 4
}
},
{
"Path": "opaque-lsa/traffic-engineering/tlvs/tlv/link/sub-tlvs/sub-tlv/unknown-subtlv/state/length",
"values": {
"opaque-lsa/traffic-engineering/tlvs/tlv/link/sub-tlvs/sub-tlv/unknown-subtlv/state/length": 4
}
},
{
"Path": "opaque-lsa/traffic-engineering/tlvs/tlv/link/sub-tlvs/sub-tlv/unknown-subtlv/state/length",
"values": {
"opaque-lsa/traffic-engineering/tlvs/tlv/link/sub-tlvs/sub-tlv/unknown-subtlv/state/length": 4
}
},
{
"Path": "opaque-lsa/traffic-engineering/tlvs/tlv/link/sub-tlvs/sub-tlv/unknown-subtlv/state/length",
"values": {
"opaque-lsa/traffic-engineering/tlvs/tlv/link/sub-tlvs/sub-tlv/unknown-subtlv/state/length": 4
}
},
{
"Path": "opaque-lsa/traffic-engineering/tlvs/tlv/link/sub-tlvs/sub-tlv/unknown-subtlv/state/length",
"values": {
"opaque-lsa/traffic-engineering/tlvs/tlv/link/sub-tlvs/sub-tlv/unknown-subtlv/state/length": 4
}
},
{
"Path": "opaque-lsa/traffic-engineering/tlvs/tlv/link/sub-tlvs/sub-tlv/unknown-subtlv/state/length",
"values": {
"opaque-lsa/traffic-engineering/tlvs/tlv/link/sub-tlvs/sub-tlv/unknown-subtlv/state/length": 8
}
},
{
"Path": "opaque-lsa/traffic-engineering/tlvs/tlv/link/sub-tlvs/sub-tlv/unknown-subtlv/state/length",
"values": {
"opaque-lsa/traffic-engineering/tlvs/tlv/link/sub-tlvs/sub-tlv/unknown-subtlv/state/length": 4
}
}

Cli

OSPF database, Area 0.0.0.0
Type ID Adv Rtr Seq Age Opt Cksum Len
OpaqArea*1.0.0.100 1.1.1.1 0x80000011 609 0x22 0x389f 136
Opaque LSA
Link (2), length 112:
Linktype (1), length 1:
1
LinkID (2), length 4:
197.0.0.25
LocIfAdr (3), length 4:
99.1.1.49
RemIfAdr (4), length 4:
99.1.1.48
TEMetric (5), length 4:
1
MaxBW (6), length 4:
100Gbps
MaxRsvBW (7), length 4:
100Gbps
UnRsvBW (8), length 32:
Priority 0, 100Gbps
Priority 1, 100Gbps
Priority 2, 100Gbps
Priority 3, 100Gbps
Priority 4, 100Gbps
Priority 5, 100Gbps
Priority 6, 100Gbps
Priority 7, 100Gbps
LinkLocalRemoteIdentifier (11), length 8:
Local 1088, Remote 0
Color (9), length 4:
0

Thanks,
Abdul

[dplore]

A device should also send UNKNOWN type for sub-tlv when there is not an already defined oc-ospf-types:OSPF_TE_LINK_TLV_TYPE.

In your example, TE-LINK-TYPE is defined. Could this be that the device you are querying is not supporting the full/intended OC model?

[abdulzubaidhar-az]

@dplore thanks. will check with device author and get back.

[abdulzubaidhar-az]

@dplore

we see sub TLVs types were returned for opaque-lsa/traffic-engineering/tlvs/tlv/link/sub-tlvs/sub-tlv/state/, we dont see option for length and value, as these are defined/known subtlvs, should not we allow length and value also as part of the same branch. right now I see we added keys/leaves length and value for unknown TLVs.

"prefix": "openconfig:network-instances/network-instance[name=DEFAULT]/protocols/protocol[identifier=OSPF][name=DEFAULT]/ospfv2/areas/area[identifier=0.0.0.0]/lsdb/lsa-types/lsa-type[type=OSPFV2_AREA_SCOPE_OPAQUE_LSA]/lsas/lsa[link-state-id=1.0.0.100]",
"updates": [
{
"Path": "opaque-lsa/traffic-engineering/tlvs/tlv/link/sub-tlvs/sub-tlv/state/type",
"values": {
"opaque-lsa/traffic-engineering/tlvs/tlv/link/sub-tlvs/sub-tlv/state/type": "TE_LINK_TYPE"
}
},
{
"Path": "opaque-lsa/traffic-engineering/tlvs/tlv/link/sub-tlvs/sub-tlv/state/type",
"values": {
"opaque-lsa/traffic-engineering/tlvs/tlv/link/sub-tlvs/sub-tlv/state/type": "TE_LINK_ID"
}
},
{
"Path": "opaque-lsa/traffic-engineering/tlvs/tlv/link/sub-tlvs/sub-tlv/state/type",
"values": {
"opaque-lsa/traffic-engineering/tlvs/tlv/link/sub-tlvs/sub-tlv/state/type": "TE_LINK_LOCAL_IP"
}
},
{
"Path": "opaque-lsa/traffic-engineering/tlvs/tlv/link/sub-tlvs/sub-tlv/state/type",
"values": {
"opaque-lsa/traffic-engineering/tlvs/tlv/link/sub-tlvs/sub-tlv/state/type": "TE_LINK_REMOTE_IP"
}
},
{
"Path": "opaque-lsa/traffic-engineering/tlvs/tlv/link/sub-tlvs/sub-tlv/state/type",
"values": {
"opaque-lsa/traffic-engineering/tlvs/tlv/link/sub-tlvs/sub-tlv/state/type": "TE_LINK_METRIC"
}
},
{
"Path": "opaque-lsa/traffic-engineering/tlvs/tlv/link/sub-tlvs/sub-tlv/state/type",
"values": {
"opaque-lsa/traffic-engineering/tlvs/tlv/link/sub-tlvs/sub-tlv/state/type": "TE_LINK_MAXIMUM_BANDWIDTH"
}
},
{
"Path": "opaque-lsa/traffic-engineering/tlvs/tlv/link/sub-tlvs/sub-tlv/state/type",
"values": {
"opaque-lsa/traffic-engineering/tlvs/tlv/link/sub-tlvs/sub-tlv/state/type": "TE_LINK_MAXIMUM_RESERVABLE_BANDWIDTH"
}
},
{
"Path": "opaque-lsa/traffic-engineering/tlvs/tlv/link/sub-tlvs/sub-tlv/state/type",
"values": {
"opaque-lsa/traffic-engineering/tlvs/tlv/link/sub-tlvs/sub-tlv/state/type": "TE_LINK_UNRESERVED_BANDWIDTH"
}
},
{
"Path": "opaque-lsa/traffic-engineering/tlvs/tlv/link/sub-tlvs/sub-tlv/state/type",
"values": {
"opaque-lsa/traffic-engineering/tlvs/tlv/link/sub-tlvs/sub-tlv/state/type": "TE_LINK_ADMIN_GROUP"
}
}
],

[ElodinLaarz]

Discussed in the OC Operators Meeting on April 21st, 2026:

This seems like a "cosmetic" bug with the vendor implementation? The data under .../unknown-subtlv/.... should not be returned when the type is known. (The model seems fine?)

You may want to open a bug with the vendor to see why the implementation is returning data.