NSO Plan errors: Deployed the following RON-ML configuration:ron ron-ml agg1_c1mode  transponderbandwidth 400ols-domain service-state UNLOCKEDend-point agg1 terminal-device-optical line-port 0/0/0/0 terminal-device-packet interface 0 ip-address v4 1.1.1.1/31 !!end-point c1 terminal-device-optical line-port 0/0/0/0 ols-domain end-point-state UNLOCKED terminal-device-packet interface 0 ip-address v4 1.1.1.2/31 !!!And were seeing the following errors, need assistance in debugging:do show ron ron-ml agg1_c1 log log-entrylog log-entry 2022-02-02T09:56:45.554372+00:00 type  service-modified level  error message "Error running action for side-effect item /cisco-ron-cfp:ron/ron-ml-plan{agg1_c1}/plan/component{ncs:self self}/state{ncs:init}: Python cb_action error. Failed to retrieve/validate SIPs"log log-entry 2022-02-02T12:25:20.134264+00:00 type  service-modified level  error message "Error running action for side-effect item /cisco-ron-cfp:ron/ron-ml-plan{agg1_c1}/plan/component{ncs:self self}/state{ncs:init}: Python cb_action error. Failed to retrieve/validate SIPs"log log-entry 2022-02-02T12:26:25.986888+00:00 type  service-modified level  error message "Error running action for side-effect item /cisco-ron-cfp:ron/ron-ml-plan{agg1_c1}/plan/component{ncs:self self}/state{ncs:init}: Python cb_action error. Failed to retrieve/validate SIPs" 
Hi Ulfat,In order to reduce the turn-around time, please include the following information if you can when reaching out for support:<ol>Device type and version used for testingAdd clear steps to reproduce an issue this includes details if some steps were done through NSO UI/CLI or through CNC UI, details on commit options used, order in which payloads were pushed, plan status in between, etc.All relevant payloads.NSO logs including trace if there was something pushed to the deviceIn some cases, wed like to understand the use-case where we see users performing certain actions especially when some steps are done through NSO UI/CLI.</ol>In this case,NSO logs will be very helpful for us to understand the issue.Device Type ; Version: RP/0/RP0/CPU0:c1#show versionThu Feb 3 19:21:39.358 UTCCisco IOS XR Software, Version 7.4.1.06I LNTCopyright (c) 2013-2020 by Cisco Systems, Inc.Build Information: Built By   : gopalk2 Built On   : Sun Nov 15 19:25:55 UTC 2020 Build Host  : iox-lnx-053 Workspace  : /auto/iox-lnx-053-san1/nightly_xr-dev/201115B_8000/ws Version   : 7.4.1.06I Label    : 7.4.1.06Icisco 8201 (VXR) processor with 16GB of memoryc1 uptime is 2 days, 1 hour, 34 minutesCisco 8201 1RU ChassisStep 1. Added ONC to NSO, verified connectivity and synched from:devices device oncaddress      10.48.71.227port       30666authgroup     ONCdevice-type netconf ned-id onf-tapi-nc-1.0connect-retries attempts 5trace      falseout-of-sync-commit-behaviour acceptstate admin-state unlockedStep 2. Configured Inter-Link-Layershow running-config ron inter-layer-linkron inter-layer-link agg1 0/0/0/0site Smolenskols-domain network-element ROADM1ols-domain optical-add-drop 1/2002/1/1,2ols-domain optical-controller onc!ron inter-layer-link agg1 0/0/0/1ols-domain network-element ROADM1ols-domain optical-add-drop 1/2004/1/2,1ols-domain optical-controller onc!ron inter-layer-link agg2 0/0/0/0ols-domain network-element ROADM1ols-domain optical-add-drop 1/2002/1/4,3ols-domain optical-controller onc!ron inter-layer-link agg2 0/0/0/1ols-domain network-element ROADM1ols-domain optical-add-drop 1/2004/1/4,3ols-domain optical-controller onc!ron inter-layer-link agg3 0/0/0/0ols-domain network-element ROADM3ols-domain optical-add-drop 1/2002/1/2,1ols-domain optical-controller onc!ron inter-layer-link agg3 0/0/0/1ols-domain network-element ROADM3ols-domain optical-add-drop 1/2004/1/2,1ols-domain optical-controller onc!ron inter-layer-link agg4 0/0/0/0ols-domain network-element ROADM3ols-domain optical-add-drop 1/2002/1/4,3ols-domain optical-controller onc!ron inter-layer-link agg4 0/0/0/1ols-domain network-element ROADM3ols-domain optical-add-drop 1/2004/1/4,3ols-domain optical-controller onc!ron inter-layer-link c1 0/0/0/0site StPetersburgols-domain network-element ROADM2ols-domain optical-add-drop 1/2002/1/1,2ols-domain optical-controller onc!ron inter-layer-link c1 0/0/0/1ols-domain network-element ROADM2ols-domain optical-add-drop 1/2004/1/2,1ols-domain optical-controller onc!ron inter-layer-link c1 0/0/0/3ols-domain network-element ROADM2ols-domain optical-add-drop 1/2006/1/2,1ols-domain optical-controller onc!ron inter-layer-link c2 0/0/0/0ols-domain network-element ROADM2ols-domain optical-add-drop 1/2002/1/4,3ols-domain optical-controller onc!ron inter-layer-link c2 0/0/0/1ols-domain network-element ROADM2ols-domain optical-add-drop 1/2004/1/4,3ols-domain optical-controller onc!ron inter-layer-link c2 0/0/0/3ols-domain network-element ROADM2ols-domain optical-add-drop 1/2006/1/4,3ols-domain optical-controller onc!ron inter-layer-link c3 0/0/0/0ols-domain network-element ROADM4ols-domain optical-add-drop 1/2004/1/2,1ols-domain optical-controller onc!ron inter-layer-link c3 0/0/0/1ols-domain network-element ROADM4ols-domain optical-add-drop 1/2002/1/2,1ols-domain optical-controller onc!ron inter-layer-link c3 0/0/0/3ols-domain network-element ROADM4ols-domain optical-add-drop 1/2006/1/2,1ols-domain optical-controller onc!ron inter-layer-link c4 0/0/0/0ols-domain network-element ROADM4ols-domain optical-add-drop 1/2004/1/4,3ols-domain optical-controller onc!ron inter-layer-link c4 0/0/0/1ols-domain network-element ROADM4ols-domain optical-add-drop 1/2002/1/4,3ols-domain optical-controller onc!ron inter-layer-link c4 0/0/0/3ols-domain network-element ROADM4ols-domain optical-add-drop 1/2006/1/4,3ols-domain optical-controller onc!Step 3. Configured RON-ML Service:show running-config ron ron-mlron ron-ml agg1_c1mode  transponderbandwidth 400ols-domain service-state UNLOCKEDend-point agg1 terminal-device-optical line-port 0/0/0/0 ols-domain end-point-state UNLOCKED terminal-device-packet interface 0 !!end-point c1 terminal-device-optical line-port 0/0/0/0 ols-domain end-point-state UNLOCKED terminal-device-packet interface 0 !!!step 4. view the Ron-ml-plan Information, and error is observed.For the logs please can you be specific as to what logs you require, no device trace is available as the plan doesn't move to the device config apply.Hi Ulfat,Thanks for providing the above info. For logs, we would probably just needncs-python-vm-cisco-zr-cfp.log andncs-python-vm-cisco-ron-cfp.log.As requested: Linmao, we found that the original issues was related to a incorrect transponder PID value being shown by the VXR device. When we fixed that issue we were able to progress further. However now we receive the following errror:root@ncs(config)# *** ALARM service-activation-failure: RPC error towards agg4: operation_failed: for ns2:interface-configurations/ns2:interface-configuration/ns1:optics/ns1:optics-transmit-power: Invalid argument: Entered tx power not supported by optics. Range supported by the platform is -100 to 10root@ncs(config)# do show running-config ron ron-ml agg4_c2ron ron-ml agg4_c2mode  transponderbandwidth 400ols-domain service-state UNLOCKEDend-point agg4 terminal-device-optical line-port 0/0/0/0 ols-domain end-point-state UNLOCKED terminal-device-packet interface 0 !!end-point c2 terminal-device-optical line-port 0/0/0/1 ols-domain end-point-state UNLOCKED terminal-device-packet interface 0 !!!ron inter-layer-link agg4 0/0/0/0ols-domain network-element ROADM3ols-domain optical-sip 5e3c96ff-8c52-3ac8-b281-c4e8fa60e37bols-domain optical-controller onc!ron inter-layer-link c2 0/0/0/1ols-domain network-element ROADM2ols-domain optical-sip b6ac904f-2b0d-3b02-b12b-9ccf57e19277ols-domain optical-controller onc!Can you suggest a way to see what tx power value is being pushed to CNC as we get the following errors reported in the inc-restconf.log:cnc-restconf.log:4-Feb-2022::12:33:51.395 usid=41512 tid=236628 datastore=running context=cli device=c2 NETCONF error reply: RPC error towards c2: operation_failed: for ns2:interface-configurations/ns2:interface-configuration/ns1:optics/ns1:optics-transmit-power: Invalid argument: Entered tx power not supported by optics. Range supported by the platform is -100 to 10cnc-restconf.log:4-Feb-2022::12:33:51.395 usid=41512 tid=236628 datastore=running context=cli device=agg4 NETCONF error reply: RPC error towards agg4: operation_failed: for ns2:interface-configurations/ns2:interface-configuration/ns1:optics/ns1:optics-transmit-power: Invalid argument: Entered tx power not supported by optics. Range supported by the platform is -100 to 10cnc-restconf.log:4-Feb-2022::13:07:56.672 usid=42744 tid=238902 datastore=running context=cli device=agg4 NETCONF error reply: RPC error towards agg4: operation_failed: for ns2:interface-configurations/ns2:interface-configuration/ns1:optics/ns1:optics-transmit-power: Invalid argument: Entered tx power not supported by optics. Range supported by the platform is -100 to 10cnc-restconf.log:4-Feb-2022::13:07:56.686 usid=42744 tid=238902 datastore=running context=cli device=c2 NETCONF error reply: RPC error towards c2: operation_failed: for ns2:interface-configurations/ns2:interface-configuration/ns1:optics/ns1:optics-transmit-power: Invalid argument: Entered tx power not supported by optics. Range supported by the platform is -100 to 10cnc-restconf.log:4-Feb-2022::13:21:54.114 usid=43298 tid=240316 datastore=running context=cli device=c2 NETCONF error reply: RPC error towards c2: operation_failed: for ns2:interface-configurations/ns2:interface-configuration/ns1:optics/ns1:optics-transmit-power: Invalid argument: Entered tx power not supported by optics. Range supported by the platform is -100 to 10cnc-restconf.log:4-Feb-2022::13:21:54.121 usid=43298 tid=240316 datastore=running context=cli device=agg4 NETCONF error reply: RPC error towards agg4: operation_failed: for ns2:interface-configurations/ns2:interface-configuration/ns1:optics/ns1:optics-transmit-power: Invalid argument: Entered tx power not supported by optics. Range supported by the platform is -100 to 10cnc-restconf.log:4-Feb-2022::13:25:58.397 usid=43636 tid=241372 datastore=running context=cli device=c2 NETCONF error reply: RPC error towards c2: operation_failed: for ns2:interface-configurations/ns2:interface-configuration/ns1:optics/ns1:optics-transmit-power: Invalid argument: Entered tx power not supported by optics. Range supported by the platform is -100 to 10cnc-restconf.log:4-Feb-2022::13:25:58.411 usid=43636 tid=241372 datastore=running context=cli device=agg4 NETCONF error reply: RPC error towards agg4: operation_failed: for ns2:interface-configurations/ns2:interface-configuration/ns1:optics/ns1:optics-transmit-power: Invalid argument: Entered tx power not supported by optics. Range supported by the platform is -100 to 10cnc-restconf.log:4-Feb-2022::13:30:19.768 usid=43906 tid=242322 datastore=running context=cli device=c2 NETCONF error reply: RPC error towards c2: operation_failed: for ns2:interface-configurations/ns2:interface-configuration/ns1:optics/ns1:optics-transmit-power: Invalid argument: Entered tx power not supported by optics. Range supported by the platform is -100 to 10cnc-restconf.log:4-Feb-2022::13:30:19.768 usid=43906 tid=242322 datastore=running context=cli device=agg4 NETCONF error reply: RPC error towards agg4: operation_failed: for ns2:interface-configurations/ns2:interface-configuration/ns1:optics/ns1:optics-transmit-power: Invalid argument: Entered tx power not supported by optics. Range supported by the platform is -100 to 10Hi Ulfat,For transmit power, you can choose to determine the value in your ron-ml payload or use a default value in transceiver-capability table or use an optical controller PCE to determine. The transmit power that you manually set takes priority. If no transmit power is provided, the service uses the value from the transceiver-capability table. If no value in the table is availabe, the service will use the value populated by the optical controller (service will multiply the value by 10). The configured transmit-power is populated as part of ron ron-ml ron-data end-point.To check thetransceiver-capability table:admin@ncs% show ron transceiver-capabilityTo check thevalue populated by the optical controller:admin@ncs> show context connectivity-context connectivity-service-oper-data <uuid>To checkconnectivity-service uuid:admin@ncs> show ron uuid-lookupHope this helps.Hi Linmao, I tried to overwrite the values in the payload:ron ron-ml agg4_c2mode  transponderbandwidth 400ols-domain service-state UNLOCKEDend-point agg4 terminal-device-optical line-port 0/0/0/0 terminal-device-optical transmit-power -10 ols-domain end-point-state UNLOCKED terminal-device-packet interface 0 !!end-point c2 terminal-device-optical line-port 0/0/0/1 ols-domain end-point-state UNLOCKED terminal-device-packet interface 0 !!!But the plan still fails with the same error below... can you suggest a plan to identify what is causing the error?plan failedplan error-info message "RPC error towards agg4: operation_failed: for ns2:interface-configurations/ns2:interface-configuration/ns1:optics/ns1:optics-transmit-power: Invalid argument: Entered tx power not supported by optics. Range supported by the platform is -100 to 10"plan error-info log-entry /ron/ron-ml/log/log-entry                     BACK   STATUS                       POST ACTIONTIME     TYPE          NAME    TRACK GOAL CODE  STATE           STATUS  WHEN     ref STATUS-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------2022-02-04T13:53:28 self          self    false -  RON-198 init           failed  2022-02-04T13:53:27 - not-reached                          ready           not-reached -     - -     optical-controller      Optical-Controller false -  RON-200 init           reached  2022-02-04T13:53:07 - -                          cisco-ron-cfp-nano-plan-services:config-apply reached  2022-02-04T13:53:07 - -                          ready           reached  2022-02-04T13:53:27 - -     cisco-ron-cfp-nano-plan-services:router agg4    false -  RON-101 init           reached  2022-02-04T13:53:27 - -                          cisco-ron-cfp-nano-plan-services:config-apply reached  2022-02-04T13:53:27 - -                          ready           not-reached -     - -     cisco-ron-cfp-nano-plan-services:router c2     false -  RON-101 init           reached  2022-02-04T13:53:27 - -                          cisco-ron-cfp-nano-plan-services:config-apply reached  2022-02-04T13:53:27 - -                          ready           not-reached -     - -2022-02-04T13:53:28 self          self    false -  RON-198 init           failed  2022-02-04T13:53:27 - not-reached                          ready           not-reached -     - -     optical-controller      Optical-Controller true init RON-110 init           reached  2022-02-04T13:53:07 - -                          cisco-ron-cfp-nano-plan-services:config-apply not-reached -     - -                          ready           not-reached -     - -     cisco-ron-cfp-nano-plan-services:router agg4    false -  -  init           not-reached -     - -                          cisco-ron-cfp-nano-plan-services:config-apply not-reached -     - -                          ready           not-reached -     - -     cisco-ron-cfp-nano-plan-services:router c2     false -  -  init           not-reached -     - -                          cisco-ron-cfp-nano-plan-services:config-apply not-reached -     - -                          ready           not-reached -     - -Hi Ulfat,Could you please share the logs (ncs-python-vm-cisco-ron-cfp.log, ncs-python-vm-cisco-zr-cfp.log, ncs-python-vm-cisco-optical-cfp.log and devices netconf trace logs) after you overwrited the value?Please also feel free to setup a meeting to debug with us if you like. Not sure if the logs files were not uploaded correctly but I'm sure I uploaded these before....Hi Ulfat,From the plan you pasted above, I believe you are using devices:agg4 and c2 for serviceagg4_c2. But I can't find the device trace logs for these 2 devices from the file you uploaded. Could you please also include them?Hi Ulfat,Are you still having the above issue? If so, please provide us the requested info as mentioned above or we will close this ticket in a week.Thanks.Closing the ticket as no response from submitter is received for more than a week. Please open a new ticket if you need any further assistance.