Difference between revisions of "Flowire CCo"
From Zenitel Wiki
m |
|||
| Line 3: | Line 3: | ||
By ''cluster'' we mean Flowires on a physical bus that share NMK - Network Membership Key. If several NMKs are used, each "NMK-group" will have its own CCo. | By ''cluster'' we mean Flowires on a physical bus that share NMK - Network Membership Key. If several NMKs are used, each "NMK-group" will have its own CCo. | ||
| − | But if there is more than two Flowires in a cluster it can make a difference which Flowire is the CCo. If the CCo Flowire is lost, then the communication in the whole cluster will stop for several seconds until a new CCo is agreed up on. Therefore it is best that a rack-side Flowire is CCo, so that a endpoint-side Flowire out in the field can be lost without affecting the rest of the cluster. | + | But if there is more than two Flowires in a cluster it can make a difference which Flowire is the CCo. If the CCo Flowire is lost, then the communication in the whole cluster will stop for several seconds until a new CCo is agreed up on. Therefore it is best that a rack-side Flowire is CCo, so that a endpoint-side Flowire out in the field can be lost without affecting the rest of the cluster. For point-to-point link between two Flowires it d |
Since Flowire SW version '''4.1.3.10''' it is possible to configure CCo mode, under the section "Configured PLC Role". | Since Flowire SW version '''4.1.3.10''' it is possible to configure CCo mode, under the section "Configured PLC Role". | ||
Revision as of 12:00, 3 March 2017
One of the Flowires in a cluster must be CCo - Central Coordinator. CCo is essentially a bus master. By default the Flowires automatically negotiate by them selves who is to be CCo.
By cluster we mean Flowires on a physical bus that share NMK - Network Membership Key. If several NMKs are used, each "NMK-group" will have its own CCo.
But if there is more than two Flowires in a cluster it can make a difference which Flowire is the CCo. If the CCo Flowire is lost, then the communication in the whole cluster will stop for several seconds until a new CCo is agreed up on. Therefore it is best that a rack-side Flowire is CCo, so that a endpoint-side Flowire out in the field can be lost without affecting the rest of the cluster. For point-to-point link between two Flowires it d
Since Flowire SW version 4.1.3.10 it is possible to configure CCo mode, under the section "Configured PLC Role".