Myriad Network v3.6 Configuration Notes

GUIDs

When you first launch Myriad Network or Myriad Network Master it creates and stores a "GUID" so it can be uniquely identified in a Network.

Whenever Myriad Network or Myriad Network Master connect to an upstream Master, it sends this GUID and the GUIDs of any slaves that are connected to it to the Master so the Master can check a couple of conditions:

1)	Does it already have a (now stale) connection from that GUID – if so, then terminate the “old” connection as it’s been disconnected – this can happen in Network outages, where Myriad network reconnects before the Windows IP stack times out the old connection.
2)	Is the Master’s GUID in the list of Slaves that has been received. This can happen if you accidentally connect 2 or more splits in a circle – i.e. Split1 connects to Split2 as it’s master, and Split2 connects to Split3, which in turn connects back to Split1.

The reason we check case 2) is because you get a loop condition where a user clicks a command on (for example) Split1 and this is sent up to Split2 which sends to 3 which sends it “up” to Split1, which gets very confused because it tries to carry out the same command again.

In this situation you will usually get a message box telling you that a Loop has been detected and the Master will terminate the connection and stop relaying messages so you know you need to take corrective action.
`
The other time it can crop up is something you will come if you use Network Master.

If you have 2 Split boxes with the same GUID – for example by copying the INI file around – then Network Master can lock up because it now has 2 perfectly valid connections from 2 fully functioning Split boxes on different IP addresses etc. but both with the same GUID. V3.5.15 will lock up when this happens, v3.5.16 and onwards attempts not to lock up, but at least one of the splits isn’t going to work because it can’t uniquely identify it.

The good news is that its very easy to correct – just open the configuration ini file you copied in and look for the GUID line and remove it completely then restart Myriad Network/Master:

[General]
GUID=EB263126-0C12-41BE-889F-C585FACB42AF

The next time it starts it will automatically create and store a new unique GUID and that’s that.