fail to create L2 P2P dedicated slice : Create an L2 P2P dedicated slice from CNC UI. It failed with the following error:Problem while provisioning the slice[{"Message":"/network-slice-services/slice-service{SL-L2-P2P-Dedi-690}/cisco-nss:shared: the 'when' expression "derived-from-or-self(../isolation, 'ietf-nss:service-isolation-dedicated')" failed","nsoResponse":"/network-slice-services/slice-service{SL-L2-P2P-Dedi-690}/cisco-nss:shared: the 'when' expression "derived-from-or-self(../isolation, 'ietf-nss:service-isolation-dedicated')" failed"}]I do not have payload for the slice, but attach the screenshots for all the data entered for creating slice. Also attached the payload for creating ODN and NSST. build combo: infra 293 + CDG 441 + COE 171 + CAT 151 + NSO 6.1.2 drop5
 Hi Crystal, The error message seems to indicate a validation was triggered due to incorrect config being present in the payload.In detail, this validation is present on the shared container as below:  container shared {   when "derived-from-or-self(../isolation, 'ietf-nss:service-isolation-dedicated')";To investigate, we may need to fix the payload or you may need to reconfigure the settings to make sure they match the validation mentioned above.Let me know if this helps.Regards,Janaki DuggiralaHello, to summarize the meeting:1. Validation was triggering due to incorrect single-sided-control config present in the payload. Once the incorrect single-sided-control was removed. Payload was succesful.2. single-sided control is present in the wiki (correctly) and can be found under the NSO UI Path -> ietf-nss:network-slice-services/slice-service{L3-Dedicated}/cisco-nss:shared3. Regarding single-sided-control usage:P2P: no single-sided-controlHub and spoke: single-sided-control with service-isolation-dedicatedAny-to-any: single-sided-control with service-isolation-dedicated4. single-sided-control is only used for Dedicated service. This is because dedicated side of the slice can be configured to force the same forwarding path selection in each direction when connecting to a shared endpoint. This behavior can is modeled in the dedicated slice service by setting the single-sided-control flag.Please let us know if all questions are resolved and if we may please close this ticket.Thanks Janaki for sharing the info. One question about the pre-requisite for adding global settings for L2 P2P dedicated slice provision to work. Is "L2-ATTACH" a reserved word or it can be a user defined value?eg. set network-slice-services global-settings parent-rr-route-policy L2-ATTACHHello Crystal, it can be any route-policy. L2-ATTACH is only a sample.Customer queries were answered. Customer confirmed ticket can be resolved.