Mandatory values for Circuit style: Kindly share the mandatory configuration commands for Circuit style with respect to CNC/NSO.Sharing below mandatory fields to bring up a CS policy oper up from Device point of view.NSO seems to have only headend , tailend and working path metric as mandatory values. Kindly suggestpolicy igp-l1-l7-16  bandwidth 50000  color 16 end-point ipv4 192.168.20.7  autoroute  include ipv4 all  !  path-protection  !  candidate-paths  preference 10   dynamic   pcep   !   metric    type te   !   !   backup-ineligible   !   constraints   segments    protection unprotected-only    adjacency-sid-only   !   !   bidirectional   co-routed   association-id 10   !  !  preference 20   dynamic   pcep   !   metric    type te   !   !   constraints   segments    protection unprotected-only    adjacency-sid-only   !   disjoint-path group-id 7 type node sub-id 70   !   bidirectional   co-routed   association-id 11   !  !  preference 30   dynamic   pcep   !   metric    type te   !   !   constraints   segments    protection unprotected-only    adjacency-sid-only   !   disjoint-path group-id 7 type node sub-id 70   !   bidirectional   co-routed   association-id 12   !  !  !  performance-measurement  liveness-detection   liveness-profile backup name CS-protected   liveness-profile name CS-working  !
Hi Ajitha, I will reply to this tomorrow. We are overloaded with M6 related items today.Hi Ajitha, below is a sparse tree with current mandatory nodes for CS SR-TE:<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"><pre class="code-java">module: cisco-cs-sr-te-cfp +--rw cs-sr-te-policy* [name]| +--rw name string| +--rw head-end | | +--rw device -> /ncs:devices/lsa-utils:lsa/dispatch-map/device/name | | +--rw ip-address inet:ip-address | +--rw tail-end | | +--rw device -> /ncs:devices/lsa-utils:lsa/dispatch-map/device/name | | +--rw ip-address inet:ip-address| +--rw (color-choice)? | | +--:(auto-color) | | | +--rw auto-color? empty | | +--:(color) | | +--rw color? uint32| +--rw path-protection! (Only dynamic, M6)| +--rw working-path  | | +--rw (sr-te-path-choice)?| | +--:(explicit-path) | | | +--rw explicit| | | +--rw (forward-sid-list-type)?| | | | +--:(forward-sid-list-name)| | | | | +--rw forward-sid-list-name? -> /cisco-sr-te-cfp:sr-te/cisco-sr-te-cfp-sr-policies:policies/sid-list/name| | | | +--:(forward-sid-list)| | | | +--rw forward-sid-list!| | | +--rw (reverse-sid-list-type)?| | | +--:(reverse-sid-list-name)| | | | +--rw reverse-sid-list-name -> /cisco-sr-te-cfp:sr-te/cisco-sr-te-cfp-sr-policies:policies/sid-list/name| | | +--:(reverse-sid-list)| | | +--rw reverse-sid-list!| | +--:(dynamic-path) | | +--rw dynamic! | | +--rw constraints| | | +--rw segments!| | | | +--rw protection? enumeration (Only dynamic, M6)</pre></div></div>It is very similar to SR-TE Policy mandatory nodes.For reference here is a sparse tree with mandatory nodes for SR-TE Policy:<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"><pre class="code-java">module: cisco-sr-te-cfp-sr-policies augment /cisco-sr-te-cfp:sr-te:  +--rw policies   +--rw policy* [name]   | +--rw name cisco-sr-te-cfp-sr-types:Cisco-ios-xr-string   | +--rw head-end* [name]   | | +--rw name -> /core-fp-common:dispatch-map/device| +--rw tail-end inet:ip-address   | +--rw color uint32| +--rw path* [preference]   | | +--rw preference uint16</pre></div></div>As you can see for both SR-TE Policy and CS SR-TE Policy, we dont enforce a complete policy as mandatory. It is up to user to configure the policy as they need.Thanks,Isaac KimHi Ajitha, we have not received a reply for a week. I believe we have provided a sufficient response. I will close this ticket.If you have any additional questions, please feel free to reopen this ticket.Thanks,Isaac KimSufficient information provided to submitter. Behavior is as expected.