Versions Compared

Old Version 1

changes.mady.by.user Gill Houghton

Saved on

compared with

New Version Current

changes.mady.by.user Gill Houghton

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

These two messages identify the MD5 sum of the UDT Definition stored at MQTt MQTT Engine. Two methods are employed - calculated and from metadata

...

This message identifies the MD5 sum of the UDT Definition contained in the NBIRTH message from the Edge Node. We are able to identify the Edge Node publishing the conflicting UDT Definition from the topic.

Image Added


This message identifies the composition of the UDT Definition stored at MQTT Engine

Image Added


This message identifies the composition of the conflicting UDT Definition published by the Edge Node - 

Image Added


To resolve the conflict, you will need to compare the two UDT Definition compositions to identify any differences - in this case we can see that the UDT Definition in the NBIRTH contains an additional Metric "New Tag 2" which is not present in the stored UDT Definition at Engine.

Image Added


Resolution

  • If the correct UDT Definition is at MQTT Engine, correcting the UDT Definition at the Edge will resolve the conflict.
  • If the correct UDT Definition is at the Edge, disable MQTT Engine, delete the UDT Definition at MQTT Engine and refresh the Edge Node to rehydrate at MQTT Engine


Note

If you delete a UDT Definition at MQTT Engine on a system with multiple Edge Nodes, the first NBIRTH message containing a new UDT Definition will be used to store at MQTT Engine.