Incorrect configuration of ASR9903 on ron-ml 1x100G service creation: The configuration is a ron-ml service with rate 1x100G between a cisco 8201 and an ASR9903While the configuration works successfully in 8201, where also in 1x100G mode the Hu interface is identified with sub-interface index 0, on ASR9903 the Hu interface is not a sub-interface. So actually, the plan is completed and green, but the configuration is not applied at the router since the Hu interface do not exist.Following is the commit performed by the RON FPRP/0/RP0/CPU0:ron-asr9903-1#sh configuration commit changes 1000000282Sun Aug 28 06:12:36.754 PDTBuilding configuration...!! IOS XR Configuration 7.7.1controller Optics0/0/1/4transmit-power -45fec OFECdwdm-carrier 100MHz-grid frequency 1937000DAC-Rate 1x1.25!interface HundredGigE0/0/1/4/0ipv4 address 100.1.4.9 255.255.255.254!interface preconfigure HundredGigE0/0/1/4/0no shutdown!endWhile if we check for Hu interface it does not have the sub-if index:RP/0/RP0/CPU0:ron-asr9903-1#sh interfaces hundredGigE 0/0/1/? 0/0/1/0        HundredGigE Interface Instance 0/0/1/1        HundredGigE Interface Instance 0/0/1/10       HundredGigE Interface Instance 0/0/1/11       HundredGigE Interface Instance 0/0/1/2        HundredGigE Interface Instance 0/0/1/3        HundredGigE Interface Instance 0/0/1/4        HundredGigE Interface Instance 0/0/1/5        HundredGigE Interface Instance 0/0/1/6        HundredGigE Interface Instance 0/0/1/7        HundredGigE Interface Instance 0/0/1/8        HundredGigE Interface Instance 0/0/1/9        HundredGigE Interface Instance R/S/I/P/B or R/S/I/P Forward interface in Rack/Slot/Instance/Port/Breakout format or R/S/I/P formatThe correc tocnfiguration that NSO should send in this case for 1x100G to ASR9903 is:interface HundredGigE0/0/1/4ipv4 address 100.1.4.9 255.255.255.254!interface HundredGigE0/0/1/4no shutdown!
Hi Roberto,CFP follows this table for the logic to determine whether to config the main interface or a sub-interface (quoted from RON 2.0 SDS section 3.8.4):<div class='table-wrap'><table class='confluenceTable'><tbody><tr><td class='confluenceTd'> </td><td class='confluenceTd'></td></tr><tr><td class='confluenceTd'></td><td class='confluenceTd'>HundredGigE 0/0/1/0/0</td></tr><tr><td class='confluenceTd'></td><td class='confluenceTd'>HundredGigE 0/0/1/0/0HundredGigE 0/0/1/0/1</td></tr><tr><td class='confluenceTd'></td><td class='confluenceTd'>HundredGigE 0/0/1/0/0HundredGigE 0/0/1/0/1HundredGigE 0/0/1/0/2</td></tr><tr><td class='confluenceTd'></td><td class='confluenceTd'>FourHundredGigE 0/0/1/0/0</td></tr><tr><td class='confluenceTd'></td><td class='confluenceTd'>HundredGigE 0/0/1/0/0HundredGigE 0/0/1/0/1HundredGigE 0/0/1/0/2HundredGigE 0/0/1/0/3</td></tr></tbody></table></div>So far the only exception is that for 1x400G transponder case CFP will only configure the main interface. Could you please confirm if for ASR 9903 (A9903-20HG-PEC) we need to make another exception in 1x100G transponder case? Is that only forA9903-20HG-PEC?Thanks,LinmaoHi Roberto,Just a gentle reminder.Could you please confirm if only for ASR 9903 (A9903-20HG-PEC) we need to make an exception in 1x100G transponder case where NSO should configure the main interface instead of sub-interface?Thanks,LinmaoRON 2.0-M9 which has the fix has been released. So, I'm closing this ticket.