Details
-
Type: Bug
-
Status: Closed
-
Priority: Minor
-
Resolution: Fixed
-
Affects Version/s: V3.14.0.0
-
Component/s: None
-
Labels:
Description
A data inconsistency issue exists if
- the neighbor device connected on a port is supporting LLDP protocol but is not a Profinet device
- the neighbor LLDP frame uses ChassisID subtype 7 (locally assigned) in its LLDP frame
The issue itself is an inconsistency between
- PDPortDataReal.PeerStationName (if accessed via Record Read) and
- lldpXPnoRemPortNoS (if accessed via SNMP)
It is expected that both access ways deliver the same content. However, if conditions mentioned above are met, the data is different.
This happens if e.g. a cisco switch is used as neighbor. In this case PeerStationName is empty string but lldpXPnoRemPortNoS contains the ChassisID of the switch.
Attachments
Issue Links
- clones
-
PSPNSV5-255 inconsistent NameOfStation reported in different access ways in case of Non-Profinet neighbor
- Closed
- is blocked by
-
PSPNS-2914 Upgrade LLDP to V4.4.0.13
- Closed
-
PSPNS-2916 update to LLDP V4.4.1.0
- Closed
- relates to
-
PSLLDP-156 wrong value returned for remote NameOfStation if read via SNMP and remote peer is a non-Profinet device
- Closed