dov
Minnow
Posts: 6
|
Post by dov on Jan 13, 2022 12:33:58 GMT
The PortId property for LLDPRecieve/LLDPTransmit has the description: "A colon delimited string of hexadecimal octets identifying a port to be transmitted from this endpoint." and has a pattern enforcing this colon delimited string. The problem is that the property PortIdSubtype is meant to determine the type (format) used by the LLDP "PortId" field. The allowed subtypes include types that PortId will not comply to the defined pattern. For example: PortIdSubtype "Interface Name" can have the PortId value that does not have any colons.
Issue present in Port v1.5.0
|
|
|
Post by mraineri on Jan 13, 2022 17:55:55 GMT
My understanding is the intent is PortId will contain the raw hex value received over the wire, and the PortIdSubtype gives the client information for how to interpret the hex values. So, this would be an example of how a MAC address (00:55:CC:33:AA:FF) would appear:
{ "PortId": "00:55:CC:33:AA:FF", "PortIdSubtype": "MacAddr" } And this would be an example of how the interface name "eth0" would appear:
{ "PortId": "65:74:68:30", "PortIdSubtype": "IfName" }
|
|