|
Post by jyundt on Oct 25, 2022 15:58:44 GMT
Should the ChassisID string in LLDPReceive include information such as SysName and SysDescr? As an example from lldpctl in Linux:
jyundt@server:~$ sudo lldpctl | grep Sys SysName: nyc3-tor-foo17 SysDescr: Juniper Networks, Inc. qfx####-###-### Ethernet Switch, kernel JUNOS ##.###-#.#, Build date: ####-##-## ##:##:# UTC Copyright (c) 1996-2021 Juniper Networks, Inc. SysName: nyc3-tor-foo18 SysDescr: Juniper Networks, Inc. qfx####-###-### Ethernet Switch, kernel JUNOS ##.###-#.#, Build date: ####-##-## ##:##:# UTC Copyright (c) 1996-2021 Juniper Networks, Inc. jyundt@server:~$
|
|
|
Post by mraineri on Oct 25, 2022 18:51:01 GMT
No, SysName and SysDescr are different TLVs in LLDP (Chassis ID is its own TLV). Is there a need to add new fields to allow for mapping SysName and SysDescr to Redfish?
|
|
|
Post by jyundt on Oct 25, 2022 18:55:30 GMT
mraineriYes, we'll need this additional TLV. This is related to this older thread about LLDP + BMC data; I (incorrectly!) thought that the existing LLDP data would contain this SysName/SysDescr but only realized it might be missing after re-reading DSP2046. What's the process to request this?
|
|
|
Post by mraineri on Oct 25, 2022 20:42:07 GMT
You just made the request! We'll discuss this further internally to make the additions.
|
|