fetch_validate_sip ERROR: Brand new NSO SIPs Verified, InterLayer Links recreated Plan is not Generated <ERROR> 25-May-2021::17:25:26.579 cisco-ron-cfp ncs-dp-2445-cisco-ron-cfp:main-5-usid-121-cisco-ron-cfp-validate-service-input: - Traceback (most recent call last): File "/home/nso542/nso-5.4.2/src/ncs/pyapi/ncs/dp.py", line 656, in wrapper ret = fn(self, uinfo, str(name), kp, input, output, act_trans) File "/home/nso542/nso-5.4.2/src/ncs/pyapi/ncs/dp.py", line 618, in fn2 return ofn(self, uinfo, name, kp, input, output) File "/home/nso542/RON-ML/state/packages-in-use/1/cisco-ron-cfp/python/cisco_ron_cfp/ron_actions.py", line 39, in cb_action self._fetch_validate_sip(root, service) File "/home/nso542/RON-ML/state/packages-in-use/1/cisco-ron-cfp/python/cisco_ron_cfp/ron_actions.py", line 215, in _fetch_validate_sip raise CustomActionException(cisco_ron_cfp.ron_ml_errors.CustomActionException: Error: STATUS_CODE: RON-505REASON: Fetch Optics failedCATEGORY: custom-actionSEVERITY: ERRORContext 
Please refer to where Ravi and I noted the string format foroptical-add-drop value for inter-layer-link.I this setup, I correctedoptical-add-drop string on ports 0/0/0/0 and network-element (site name) forP-TOPRIGHT-VXR as:admin@ncs% show | compare ron { inter-layer-link P-TOPLEFT-VXR 0/0/0/0 { ols-domain {- optical-add-drop /1/6/2/0/20,19;+ optical-add-drop 1/6/2/20,19; } } inter-layer-link P-TOPRIGHT-VXR 0/0/0/0 { ols-domain {- network-element daigosim9;+ network-element daigosim17;- optical-add-drop /1/3/2/0/10,9;+ optical-add-drop 1/3/2/10,9; } } }It passes the original optical fetch issue and currently fails due to XR routers are not reachable.admin@ncs% *** ALARM connection-failure: Failed to connect to device P-TOPLEFT-VXR: host is unreachableadmin@ncs%admin@ncs% run show ron ron-ml-plan 400Gbps-Transponder-OLS plan POST BACK STATUS ACTION TYPE NAME TRACK GOAL CODE STATE STATUS WHEN ref STATUS --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------self self false - - init reached 2021-05-25T17:25:26 - failed ready not-reached - - - optical-controller Optical-Controller false - - init not-reached - - - cisco-ron-cfp-nano-plan-services:config-apply not-reached - - - ready not-reached - - - cisco-ron-cfp-nano-plan-services:router P-TOPLEFT-VXR false - - init not-reached - - - cisco-ron-cfp-nano-plan-services:config-apply not-reached - - - ready not-reached - - - cisco-ron-cfp-nano-plan-services:router P-TOPRIGHT-VXR false - - init not-reached - - - cisco-ron-cfp-nano-plan-services:config-apply not-reached - - - ready not-reached - - -plan failedplan error-info message "Error running action for side-effect item /cisco-ron-cfp:ron/ron-ml-plan{400Gbps-Transponder-OLS}/plan/component{ncs:self self}/state{ncs:init}: Python cb_action error. Error: Hardware capability does not support this configuration of mode/bandwidth/fec/dacnSTATUS_CODE: RON-410nREASON: Hardware transceiver capability does not support the configured mode and bandwidth.nCATEGORY: usernSEVERITY: ERRORnnSTATUS_CODE: RON-506nREASON: Fetch Optics failednCATEGORY: custom-actionnSEVERITY: ERRORnContext [name = Fetch Optics Data error, message = ZR Fetch Optics data action returned errorn state = {'service': ListElement name=ron-ml tag=1842926444 keys={400Gbps-Transponder-OLS}, 'endpoint': ListElement name=end-point tag=935030957 keys={P-TOPLEFT-VXR}}]n"plan error-info log-entry /ron/ron-ml/log/log-entryadmin@ncs% request devices device P-TOPLEFT-VXR connectresult falseinfo Failed to connect to device P-TOPLEFT-VXR: host is unreachableadmin@ncs% request devices device P-TOPRIGHT-VXR connectresult falseinfo Failed to connect to device P-TOPRIGHT-VXR: host is unreachableadmin@ncs% *** ALARM connection-failure: Failed to connect to device P-TOPRIGHT-VXR: host is unreachableVRs are back We are back to square 0400Gbps-Transponder-OLS===================I understand thatyou has removed leading back slashes in SIP addDrop configuration .Thats fine, still the problem exist Error running action for side-effectitem /cisco-ron-cfp:ron/ron-ml-plan{400Gbps-Transponder-OLS}/plan/component{ncs:selfself}/state{ncs:init}: Python cb_action error. Error: STATUS_CODE: RON-505REASON: Fetch Optics failed CATEGORY: custom-action SEVERITY: ERROR Context400Gbps-Transponder-P2P===================RPC error towards PE-A-VXR:unknown_element:ns2:interface-configurations/ns2:interface-configuration/ns1:optics/ns1:optics-modulationAs per Anoosh, we can not upgrade, and you guyswill have to dig in to this You can use our Netconf Browse if you wish andinspect the NETCONF models : 192.168.122.73 admin/Public1234!As you can see below from the XR device Netconf trace, NSO sent correct payload to the device but got unknown-element error. This causes by the device doesn't understand the payload content(s), which points to the image on the device being too old.We'd recommend to upgrade the image on your XR routers to make sure your environment is working. You can work out the image details with PMs on RON program after this. There is nothing else we can help you on this.>>>>out 25-May-2021::20:33:21.661 user: nso542/188 thandle 3712 hostname nso-ucs-haim1 device P-TOPLEFT-VXR session-id=3964231496<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="4"> <edit-config xmlns:nc="urn:ietf:params:xml:ns:netconf:base:1.0"> <target> <candidate/> </target> <test-option>test-then-set</test-option> <error-option>rollback-on-error</error-option> <config> <interface-configurations xmlns="http://cisco.com/ns/yang/Cisco-IOS-XR-ifmgr-cfg"> <interface-configuration> <active>act</active> <interface-name>Optics0/0/0/3</interface-name> <description>2</description> <optics xmlns="http://cisco.com/ns/yang/Cisco-IOS-XR-controller-optics-cfg"> <optics-transmit-power>-90</optics-transmit-power> <optics-dwdm-carrier> <param-type>frequency</param-type> <grid-type>100mhz-grid</grid-type> <param-value>1951000</param-value> </optics-dwdm-carrier> <optics-modulation>16qam</optics-modulation> <optics-fec>fec-ofec</optics-fec> </optics> </interface-configuration> </interface-configurations> </config> </edit-config></rpc>>>>>out 25-May-2021::20:33:21.662 user: nso542/188 thandle 3712 hostname nso-ucs-haim1 device P-TOPLEFT-VXR session-id=3964231496<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="5"> <validate> <source> <candidate/> </source> </validate></rpc><<<<in 25-May-2021::20:33:21.669 user: nso542/188 thandle 3712 hostname nso-ucs-haim1 device P-TOPLEFT-VXR session-id=3964231496<rpc-reply message-id="4" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"> <rpc-error> <error-type>protocol</error-type> <error-tag>unknown-element</error-tag> <error-severity>error</error-severity> <error-path xmlns:ns1="http://cisco.com/ns/yang/Cisco-IOS-XR-controller-optics-cfg" xmlns:ns2="http://cisco.com/ns/yang/Cisco-IOS-XR-ifmgr-cfg">ns2:interface-configurations/ns2:interface-configuration/ns1:optics/ns1:optics-modulation</error-path> <error-info> <bad-element>optics-modulation</bad-element> </error-info> </rpc-error></rpc-reply>OK, how about 400Gbps-Transponder-OLS SIP fetch problem ? IT is not related to XR versionThe inter-layer-link forP-TOPLEFT-VXR 0/0/0/0 andP-TOPRIGHT-VXR 0/0/0/0 were still wrong. I corrected the same pair in your older NSO. Here are what were changed:nso542@ncs% show | compare ron { inter-layer-link P-TOPLEFT-VXR 0/0/0/0 { ols-domain {- optical-add-drop 1/6/2/0/20,19;+ optical-add-drop 1/6/2/20,19; } } inter-layer-link P-TOPRIGHT-VXR 0/0/0/0 { ols-domain {- network-element daigosim9;+ network-element daigosim17;- optical-add-drop 1/3/2/0/10,9;+ optical-add-drop 1/3/2/10,9; } } }There's no more fetch SIP error but you need to update RON CFP as I mentioned last week. There was an issue working with ONC 20.4.2021 drop that require a rebuild of RON CFP.Yevgeny closes the case, will upgrade his environment.