search

openBackhaul / synchronization

Synchronization model according to ITU-T G.7721-2018
Apache License 2.0
1 stars 0 forks source link

Incomplete definition of "switch-type" FORCED_SWITCH #45

Open openBackhaul opened 2 years ago

openBackhaul commented 2 years ago

The definition of the values for the switch-type attribute in the sync-protection-spec grouping is not clear:

demx8as6 commented 2 years ago

The CoreModel offers the following value for parameter /control-construct/forwarding-domain/fc/fc-switch/switch-control

  1. It seams that the entire parameter "switch-type" could be removed, because it is part of the CoreModel (to be verified)

  2. The 'selected source' can be found at /control-construct/forwarding-domain/fc/fc-switch/selected-fc-port

core-model-1-4.yang:459:  identity SWITCH_CONTROL_NORMAL {
core-model-1-4.yang-460-    base SWITCH_CONTROL;
core-model-1-4.yang-461-    description
core-model-1-4.yang-462-      "No administrative control applied to the switch.";
core-model-1-4.yang-463-  }
core-model-1-4.yang-464-
core-model-1-4.yang:465:  identity SWITCH_CONTROL_MANUAL {
core-model-1-4.yang-466-    base SWITCH_CONTROL;
core-model-1-4.yang-467-    description
core-model-1-4.yang-468-      "Resource temporarily chosen by control configuration where the resource is not the preferred resource.
core-model-1-4.yang-469-       Preferred resource has highest priority.
core-model-1-4.yang-470-       Temporarily overrides reversion.
core-model-1-4.yang-471-       If this resource fails, it will switch to best available resource.
core-model-1-4.yang-472-       If resource selected is shared and another FC requires the resource, then the selection control will change to Normal and switch to best available based upon normal rules.
core-model-1-4.yang-473-       Cannot manually switch a Forced switch, cannot remove a forced switch, cannot switch to a locked out item and will be rejected if the protection process is deactivated by being Freeze = true).
core-model-1-4.yang-474-       A manual switch/route that is selecting an FcPort, LTP, FC, Link or Route that is subsequently set to LOCK_OUT will have the manual removed (changed to NORMAL) and will switch away from the FcPort with LOCK_OUT to best available based upon normal rules.
core-model-1-4.yang-475-       A manual switch that is selecting an FcPort that is subsequently selected by a Forced switch will be restored to normal operation and the manual will be removed.
core-model-1-4.yang-476-       A manual switch/route that is selecting an FcPort, LTP, FC, Link or Route that is subsequently manual selected by another switch/route will have the manual removed and will switch away from the FcPort.
core-model-1-4.yang-477-       Can be returned to NORMAL by configuration action.";
core-model-1-4.yang-478-  }
core-model-1-4.yang-479-
core-model-1-4.yang:480:  identity SWITCH_CONTROL_FORCED {
core-model-1-4.yang-481-    base SWITCH_CONTROL;
core-model-1-4.yang-482-    description
core-model-1-4.yang-483-      "Resource temporarily chosen by control configuration where the resource is not the preferred resource.
core-model-1-4.yang-484-       Preferred resource has highest priority.
core-model-1-4.yang-485-       Temporarily overrides reversion.
core-model-1-4.yang-486-       If this resource fails it will NOT switch.
core-model-1-4.yang-487-       If resource selected is shared and another FC requires the resource through a FORCE on that FC and the FC is of a higher FcPriority then the selection control on this FC will change to NORMAL and switch to best available based upon normal rules.
core-model-1-4.yang-488-       If the resource selected is then set to LOCK_OUT then the selection control will change to NORMAL and switch to best available based upon normal rules.
core-model-1-4.yang-489-       Can be returned to NORMAL by configuration action.";
core-model-1-4.yang-490-  }
openBackhaul commented 2 years ago

Proposal to the 5G-xhaul call on 14th of September 2022: There is a switchControl attribute in the FcSwitch class of the Core IM. The switchControl attribute is of SwitchControl enumeration. The SwitchControl enumeration contains NORMAL, MANUAL and FORCED as values. The SyncProtectionSpec::switchType : SwitchType attribute in the Synchronization modelling contains the same. The SyncProtectionSpec class is augmenting the ControlParameter_Pac of the Core IM. The SyncProtectionSpec::switchType attribute of the Synchronization modelling is redundant to the SwitchControl::switchControl attribute of the Core IM.

Changes:

DanielaSpreafico commented 2 years ago

I have a question regarding the last phrase on the proposal: what does it mean " In case the selection process has failed the currently selected clock parameter must not be exposed in the management interface." ? I mean: the selection process selects between the clock sources (sync LTPs defined on the initial configuration) the "currently selected clock source", OK. Then in case the selection process has failed the node goes on a specific state (holdover? ) using Local Oscillator. In this case there isn't "currently selected clock source", so no need to expose to the management interface. Correct?

demx8as6 commented 2 years ago

@DanielaSpreafico - I would answer your question "Correct?" with "yes - correct" - let's make sure in the call 2022-09-14 that all the understanding is correct on all sides.

demx8as6 commented 2 years ago

Decision made at the 5G-xhaul call on 14th of September 2022: There is a switchControl attribute in the FcSwitch class of the Core IM. The switchControl attribute is of SwitchControl enumeration. The SwitchControl enumeration contains NORMAL, MANUAL and FORCED as values. The SyncProtectionSpec::switchType : SwitchType attribute in the Synchronization modelling contains the same. The SyncProtectionSpec class is augmenting the ControlParameter_Pac of the Core IM. The SyncProtectionSpec::switchType attribute of the Synchronization modelling is redundant to the SwitchControl::switchControl attribute of the Core IM.

Changes: