M2M - Cascade Topology
Cascade Topology
The figure below shows 16 masters connected to each other such that any master is routeable to any other master using route mode direct:
In a Cascade topology, the URL Lists would be configured as shown below:
Note: The system number is being used here for readability, the actual URL/IP address must be entered into the URL List.
This topology has many advantages over the previously listed methods:
-
Each master is able to see all the other masters, with one hop
-
No passing of messages, which reduces the processing load on the master
-
Robust, if one master goes down communication is lost with only that master and the devices connected to it
-
Reduced network traffic
Note:
When multiple masters exist within a large NetLinx installation the significance of the System number component cannot be over emphasized.
Out of habit it is easy to ignore the system field within NetLinx Studio because its value has not meant anything in standalone systems. A significant source of technical support phone calls will be directly related to invalid or unintentionally incorrect settings of the system number, URL List, or route mode.
When NetLinx Studio connects to a single master, yet allows the user to access all other system masters it is inevitable that some confusion will occur.
Therefore, it is a good idea to document each master’s system number and the topology of the interconnections!