Issue
Sigma Transition in StruxureWare Building Operation, where the Sigma controllers and the ES are on different subnets. Globals are not being passed to or from the Sigma system.
Product Line
EcoStruxure Building Operation, Satchwell Sigma
Environment
- Globals
- Global values
- Link addressing
Cause
This issue is being caused because the Sigma controllers are on a different subnet to the Enterprise server.
Sigma global data is passed between controllers using "Broadcast" messages, 192.168.1.255 for instance. These messages are normally stopped by network switches/routers, and are not passed between different subnets.
To overcome this, Sigma employs "Link Addressing". For further information on this please review Link Addressing on a Sigma System
Resolution
As Sigma servers do not make use of the global broadcasts, on a current Sigma system there may not be any Link Addressing in place for the Server subnet, and this will mean that if an ES is placed on that subnet, it will not see any global broadcasts either.
When carrying out a Sigma Transition consider if there is a need to pass global data to or from the Sigma system, and if so, add a DNN3 to the subnet and Link Address it..
