Need to know the status of RON state 506,410: "message": "Error running action for side-effect item /cisco-ron-cfp:ron/ron-ml-plan{200_mux1}/plan/component{ncs:self self}/state{ncs:init}: Python cb_action error. Error: RON-410Hardware capability for the {QDD-400G-ZR-S, muxponder, 200} cannot be foundSTATUS_CODE: RON-506REASON: Fetch Optics failedCATEGORY: custom-actionSEVERITY: ERRORContext [name = Fetch Optics Data error, message = ZR Fetch Optics data action returned error state = {'service': '200_mux1', 'endpoint': 'P-TOPLEFT-VXR'}]"
Hi Aarthi,We are looking into your issue. Please standby as we might need more info from your end debug your system.Please provide the following:<ol>NSO versionCFP build versionDevice 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>I can also take a look around and check your testbed if you provide credentials here.Thank you,AbeThe issue is resolved now. Thanks for the clarification Abe. You can close the TicketHi Aarthi,To find out more about RON status code displayed on the service-plan, please use. This will display both the reason and recommended-actions for any given RON status codeAs for the reason you have encountered the above issue,it is because of provisioning muxponder with 200 bandwidth when ZR-only (not ZR+) can only do muxponder = 400, and therefore not supported.Please let me know if answers your queries or if you have additional questions regarding this ticket.Thank you,AbeThanks Aarthi. Closing the ticket now.Answered all questions from Aarthi. Setting the issue as resolved and closing the ticket.