OLS Scenario - Sending wrong service name to ONC: Description=================OLS scenario Sendsto ONC internal service TOPLEFT_TOPRIGHT_400_TR_OLS-internalONC does not support dash , only underscore RPC error towardslshraga-sp-nac: operation_failed: Exception in callback: Missing valid value for name-type SERVICE_NAME forConnectivity service with UUID:. Validvalue shall contain alpha numeric with only underscore as the special characterwith length up to 64 characters.Environment=================UI+SSH: nso552/Public1234!LocalInstallation:/home/nso552/.0.0Service:=================<ron-ml><name>TOPLEFT_TOPRIGHT_400_TR_OLS</name><mode>transponder</mode><bandwidth>400</bandwidth><circuit-id>2</circuit-id><grid-type>100mhz-grid</grid-type><frequency>1951000</frequency><dac-rate>1x1</dac-rate><ols-domain><service-state>UNLOCKED</service-state></ols-domain><end-point><end-point-device>P-TOPLEFT</end-point-device><terminal-device-optical><line-port>0/0/0/0</line-port><transmit-power>-90</transmit-power></terminal-device-optical><terminal-device-packet><interface><index>0</index><ip-address><v4>20.20.10.13/30</v4></ip-address></interface></terminal-device-packet></end-point><end-point><end-point-device>P-TOPRIGHT</end-point-device><terminal-device-optical><line-port>0/0/0/0</line-port><transmit-power>-90</transmit-power></terminal-device-optical><terminal-device-packet><interface><index>0</index><ip-address><v4>20.20.10.14/30</v4></ip-address></interface></terminal-device-packet></end-point></ron-ml>
This issue was noticed with ONC FCS build which has some backward-incompatible change that caused the payload sent by RON CFP to fail. I assume you are testing with ONC FCS build which the CFP team has not tested yet. CFP team is working on a fix for this. In the meantime please test with Old ONC version that CFP team recommended.Van has patched your NSO server with the fix in cisco-ron-cfp package. The SERVICE_NAME sent to ONC will not have "-internal" anymore and just reflects the original RON service name. Make sure the RON service name created adheres to the above constraints i.e., alphanumeric+Underscore+64chars length so that we don't land into this issue again.NSO server is patched with the fix. The next RON1.0 build delivered will have the fix.