Hello,
I am trying to trace from a LV subnetwork all the way up to the MV subnetwork, but the trace always stops at the LV subnetwork controller and doesn't go further.
On the other hand, tracing from MV down to LV subnet is working fine.
I think this may be because the LV controllers are directional, but not sure. Wasn't the "target tier" option especially made for this purpose ?
Thanks
Solved! Go to Solution.
Hi @Mike
with the new tier group / tiers configuration, it now works as expected :
However, I had to modify my MV subnet definition to include some of the LV features (when applying the LV definition, I had an error saying that those features should be in the parent subnetwork definition).
Now the questions :
- is it normal in a hierarchical network that it is not allow tracing from a tier group to another tier group ?
- in any case, the MV subnetwork propagation stops at the subnetwork controllers. I have to manually put this in the condition barriers, is it expected in a hierarchical network ?
As far as I understand this figure :
It seems normal that subnetwork won't stop at subnetwork controllers unless it is specified in the subnet definition. Otherwise, tier A in the example above would stop at tier B controllers, which is not what we want in this configuration. But I could not find explicit rules about the different behaviors between hierarchical and partitioned.