input
stringlengths 48
5.67k
| output
stringlengths 0
15.3k
|
|---|---|
PATCH request not working for slice catalog: Hi,While updating a template, when we try to update qos catalogs, nothing happens. We receive "204 No Content" as response.Template which is to be editied:{"ietf-network-slice-service:slo-sle-template":[{"id":"2222","template-description":"222- descp","cisco-network-slice-service:qos-policy":{"L2":{"input-policy":"input-policy","output-policy":"output-policy"},"L3":{"input-policy":"input-policy","output-policy":"output-policy"}}}]}Below we're removing the L2: input-policy from the payload.URL:https://<host>:<port>/crosswork/proxy/nso/restconf/data/ietf-network-slice-service:network-slice-services/slo-sle-templates/slo-sle-template=2222Payload: {"ietf-network-slice-service:slo-sle-template":[{"id":"2222","template-description":"222- descp","cisco-network-slice-service:qos-policy":{"L2":{"output-policy":"output-policy"},"L3":{"input-policy":"input-policy","output-policy":"output-policy"}}}]}Its not affecting the NSO and no update happens | Hi Magesh, When slo-sle-template is updated after the slice-service is already push to the device. CFP will not automatically update slice-service. You need to re-deploy manually the slice-service to see the effect. That is by design by CFPThanks,LinhHi Linh,I do believe template is not pushed to device , only slice is pushed to device.If template is not used by any slice then it should be possible to edit the QoS params in template. Please let us know whether it is designed in such a way.Kindly let us know attributes which are not possible edit once template is created because I could see we are able to edit the description.Thanks,NaveenHi Naveen,If you want to delete input-policy, you should not use PATCH. Please review this document on PATCHThis is the restconf command to delete input-policycurl --location --request DELETE 'http://<nso_ip>:8080/restconf/data/ietf-network-slice-service:network-slice-services/slo-sle-templates/slo-sle-template=P2P/cisco-network-slice-service:qos-policy/L2/input-policy' --header 'Content-Type: application/yang-data+xml' --header 'Authorization: Basic YWRtaW46Q2lzY28xMjMj' --data-raw ''Thanks,LInhHi Linh,I am able to change the Qos Policy in template whereas only removal of QoS policy is not working.I think it is NSO bug which has to be handled .If NSO is able to change the value of QoS internally then it should handle the removal also internally.Thanks,NaveenThat is how PATCH request does. It is not NSO bug. It is PATCH request behavior. PATCH request works like a merge operation and it would not remove the entry. I am able to delete qos-policy if I use DELETE request-LinhHi Linh,Got it , I could see PUT request is able to handle all the cases.Kindly let know whether there will be any impact to Slice if we make PUT request on template.Thanks,NaveenThe behavior is expected for PATCH request |
mVPN is missing in VPN Node Level : Model is missing in VPN Node Level Server Details: admin/adminssh: nso576/Public1234!NSO Folder: /home/nso576/.0.0Using : nso-5.7.6-tsdn-5.0.0-M3.tar.gz | This leaf node is not being used.Hi Evgeny, multicast -> enabled flag is not being used as part MVPN configuration for now. Enabling that flag would not enable the parameters under vpn-node. The user is expected to configure the vpn-service with the right mvpn config to enable the options under vpn-node.Hi Sahithi, I think this is not we meant. If you look at the model you ad published back at the time in this wiki page, Static Tree SID configuration is divided in to two parts (See attached picture).1. Part one - On VPN node level, where you assign a certain VPN node with static Tree SID policy 2. Part Two - On service level We are missing in published model the "Part One"Thank you so much for your assistance, problem solved |
NSO 5.7 M4 FRR enable resulting error: Hi Sahiti, Van,We have NSO 5.X + M4 CFP on one set upAfter service with RSVP TE tunnel was created, we wanted to enable FRR stateIt have following errorXR team had mentioned in past that PCE delegation should be removed from tunnelSo we did that and did Device->NSO sync as well.But still the Flex UI giving following errorCan someone help? Here is testbed details and tunnel between AA-NCS5501-1 and AA-NCS5501-2I have opened JIRA as wellThx,Vaishali | Hi Vaisali, Sorry I don't get your issue. Can you provide your service payload? Is FRR option available from CFP? Is this feature working in previous release?What is error message that you saw in NSO?Thanks,Linh1) yes FRR support is added in CFP M2 itself2) Service payload is like this which created similar tunnel 221<data xmlns="urn:ietf:params:xml:ns:yang:ietf-restconf"> <te xmlns="urn:ietf:params:xml:ns:yang:ietf-te"xmlns:y="http://tail-f.com/ns/rest"xmlns:te="urn:ietf:params:xml:ns:yang:ietf-te" xmlns:te-types="urn:ietf:params:xml:ns:yang:ietf-te-types"> <tunnels xmlns="urn:ietf:params:xml:ns:yang:ietf-te" xmlns:te="urn:ietf:params:xml:ns:yang:ietf-te"> <tunnel> <name>L2VPN_NM-P2P-RSVPTE-AA-NCS5501-1-221</name> <identifier>221</identifier> <description>L2VPN_NM-P2P-RSVPTE-AA-NCS5501-1-221</description> <head-end xmlns="http://cisco.com/ns/nso/fp/examples/cisco-te">AA-NCS5501-1</head-end> <tail-end xmlns="http://cisco.com/ns/nso/fp/examples/cisco-te">AA-NCS5501-3</tail-end> <source>100.100.100.2</source> <destination>100.100.100.6</destination> <signaling-type>te-types:path-setup-rsvp</signaling-type> <primary-paths> <primary-path> <name>L2VPN_NM-P2P-RSVPTE-AA-NCS5501-1-221</name> <path-computation-method xmlns:te-types="urn:ietf:params:xml:ns:yang:ietf-te-types">te-types:path-externally-queried</path-computation-method> <optimizations> <optimization-metric> <metric-type>te-types:path-metric-igp</metric-type> </optimization-metric> </optimizations> <preference>1</preference> </primary-path> </primary-paths> </tunnel> <tunnel> <name>L2VPN_NM-P2P-RSVPTE-AA-NCS5501-3-221</name> <identifier>221</identifier> <description>L2VPN_NM-P2P-RSVPTE-AA-NCS5501-3-221</description> <head-end xmlns="http://cisco.com/ns/nso/fp/examples/cisco-te">AA-NCS5501-3</head-end> <tail-end xmlns="http://cisco.com/ns/nso/fp/examples/cisco-te">AA-NCS5501-1</tail-end> <source>100.100.100.6</source> <destination>100.100.100.2</destination> <signaling-type>te-types:path-setup-rsvp</signaling-type> <primary-paths> <primary-path> <name>L2VPN_NM-P2P-RSVPTE-AA-NCS5501-3-221</name> <path-computation-method xmlns:te-types="urn:ietf:params:xml:ns:yang:ietf-te-types">te-types:path-externally-queried</path-computation-method> <optimizations> <optimization-metric> <metric-type>te-types:path-metric-igp</metric-type> </optimization-metric> </optimizations> <preference>1</preference> </primary-path> </primary-paths> </tunnel> </tunnels> </te> <l2vpn-ntw xmlns="urn:ietf:params:xml:ns:yang:ietf-l2vpn-ntw"> <vpn-services> <vpn-service> <vpn-id>L2VPN_NM_P2P_RSVPTE-221</vpn-id> <vpn-type>vpn-common:vpws</vpn-type> <vpn-nodes> <vpn-node> <vpn-node-id>AA-NCS5501-3</vpn-node-id> <te-service-mapping xmlns="http://cisco.com/ns/nso/fp/examples/cisco-l2vpn-ntw"> <te-mapping> <te-tunnel-list> <ietf-te-service>L2VPN_NM-P2P-RSVPTE-AA-NCS5501-3-221</ietf-te-service> <fallback>disable</fallback> </te-tunnel-list> </te-mapping> </te-service-mapping> <signaling-option> <ldp-or-l2tp> <pw-peer-list> <peer-addr>100.100.100.2</peer-addr> <vc-id>221</vc-id> <mpls-label xmlns="http://cisco.com/ns/nso/fp/examples/cisco-l2vpn-ntw">221</mpls-label> </pw-peer-list> </ldp-or-l2tp> </signaling-option> <vpn-network-accesses> <vpn-network-access> <id>221</id> <interface-id>GigabitEthernet0/0/0/0</interface-id> <connection> <encapsulation> <encap-type>vpn-common:dot1q</encap-type> <dot1q> <cvlan-id>221</cvlan-id> </dot1q> </encapsulation> </connection> </vpn-network-access> </vpn-network-accesses> </vpn-node> <vpn-node> <vpn-node-id>AA-NCS5501-1</vpn-node-id> <te-service-mapping xmlns="http://cisco.com/ns/nso/fp/examples/cisco-l2vpn-ntw"> <te-mapping> <te-tunnel-list> <te-tunnel-id>221</te-tunnel-id> </te-tunnel-list> </te-mapping> </te-service-mapping> <signaling-option> <ldp-or-l2tp> <pw-peer-list> <peer-addr>100.100.100.6</peer-addr> <vc-id>221</vc-id> <mpls-label xmlns="http://cisco.com/ns/nso/fp/examples/cisco-l2vpn-ntw">221</mpls-label> </pw-peer-list> </ldp-or-l2tp> </signaling-option> <vpn-network-accesses> <vpn-network-access> <id>1</id> <interface-id>GigabitEthernet0/0/0/0</interface-id> <connection> <encapsulation> <encap-type>vpn-common:dot1q</encap-type> <dot1q> <cvlan-id>221</cvlan-id> </dot1q> </encapsulation> </connection> </vpn-network-access> </vpn-network-accesses> </vpn-node> </vpn-nodes> </vpn-service> </vpn-services> </l2vpn-ntw></data> Hi Vaisali,I applied your payloads to my setup. They are working fine l2vpn xconnect and te-tunnel 221 are up.RP/0/RSP0/CPU0:PE3#show l2vpn xconnect group L2VPN_NM_P2P_RSVPTE-221Thu Dec 8 18:43:17.189 UTCLegend: ST = State, UP = Up, DN = Down, AD = Admin Down, UR = Unresolved, SB = Standby, SR = Standby Ready, (PP) = Partially Programmed, LU = Local Up, RU = Remote Up, CO = Connected, (SI) = Seamless InactiveXConnect Segment 1 Segment 2 Group Name ST Description ST Description ST ------------------------ ----------------------------- -----------------------------L2VPN_NM_P2P_RSVPTE-221 L2VPN_NM_P2P_RSVPTE-221 UP Hu0/0/0/4.221 UP 100.100.100.6 221 UP ----------------------------------------------------------------------------------------RP/0/RSP0/CPU0:PE3#show mpls traffic-eng tunnels name L2VPN_NM-P2P-RSVPTE-AA-NCS5501-3-221Thu Dec 8 18:38:44.494 UTCLSP Tunnel 100.100.100.6 221 is signalled, Signaling State: up Tunnel Name: L2VPN_NM-P2P-RSVPTE-AA-NCS5501-3-221 Tunnel Role: Tail InLabel: HundredGigE0/0/0/0, implicit-null Signalling Info: Src 100.100.100.6 Dst 100.100.100.5, Tun ID 221, Tun Inst 3, Ext ID 100.100.100.6 Router-IDs: upstream 100.100.100.1 local 100.100.100.5 Bandwidth: 0 kbps (CT0) Priority: 7 7 DSTE-class: 0 Soft Preemption: None SRLGs: not collected Path Info: Incoming Address: 10.10.10.10 Incoming: Explicit Route: Strict, 10.10.10.10 Strict, 100.100.100.5 Record Route: Disabled Tspec: avg rate=0 kbits, burst=1000 bytes, peak rate=0 kbits Session Attributes: Local Prot: Not Set, Node Prot: Not Set, BW Prot: Not Set Soft Preemption Desired: Not Set Resv Info: None Record Route: Disabled Fspec: avg rate=0 kbits, burst=1000 bytes, peak rate=0 kbitsDisplayed 0 (of 2) heads, 0 (of 0) midpoints, 1 (of 1) tailsDisplayed 0 up, 0 down, 0 recovering, 0 recovered headsI am not sure these are operation status that you looked at. Please let me knowRegards,LinhThere is no update from subimitter. I am going to close the ticketRegards,Linh |
Does explicit path is applicable to Circuit Style policy ?: Hi,It looks like by definition Circuit Style policy can only have delegated path and it is suppose to have only dynamic path with Bi-Dir association ID.It looks like NSO model has provision to support both dynamic as well as explicit.Kindly let us know whether explicit path is supported for Circuit Style.Thanks,Naveen | Hello, Yes it is supported. Pasted below is a sample payload + wiki page that can provide further guidance.Please let me know if this helps.Thank you.Regards,Janaki DuggiralaReceived confirmation from Naveen that ticket maybe closed and no further assistance required.If any further issues are encountered, please open a new ticket for the issue.Received confirmation from Naveen that ticket maybe closed and no further assistance required.If any further issues are encountered, please open a new ticket for the issue. |
cant retrieve l3vpn plan: noticed there is new path for the plan of l3vpn. we are not able to perform fetch of it. this is the query we use usually:but it doesnt work - can you please specify the new path we should use? Thanks | Hi Idan,This is new URLhttp://<tt>NSO</tt>:8888/restconf/data/ietf-l3vpn-ntw:l3vpn-ntw/vpn-services/cisco-l3vpn-ntw:vpn-service-plan=?offset=0;limit=100;depth=5Thanks,Linhthanks! working good now. Provided the current URL |
Transport Slicing - Need possible values for hub-rt & spoke-rt: When we tried to provide the value for hub-rt ; spoke-rt in conneciton groups it resulted in below error,{ "ietf-restconf:errors": { "error": [ { "error-type": "application", "error-tag": "malformed-message", "error-path": "/ietf-network-slice-service:network-slice-services", "error-message": "invalid value for: hub-rt in /ietf-nss:network-slice-services/ietf-nss:slice-service[ietf-nss:service-id='Test-Dedic-530']/ietf-nss:connection-groups/ietf-nss:connection-group[ietf-nss:connection-group-id='Default']/ietf-nss-cisco:vpn-target/ietf-nss-cisco:hub-rt: "import" is an invalid value." } ] }}Kindly let us know the possible values.Thanks,Naveen | Hi Naveen,hub-rt and spoke-rt for NSS has the following type definition:<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"><pre class="code-java">typedef route-distinguisher { type string { pattern + + + + + + + + + + + + + + + + + + + + + + + ; tailf:info "0:2-octet-asn:4-octet-number 1:4-octet-ipv4addr:2-octet-number 2:4-octet-asn:2-octet-number"; }}</pre></div></div>So the input for these hub-rt and spoke-rt should be in the following format:<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"><pre class="code-java">0:2-octet-asn:4-octet-number 1:4-octet-ipv4addr:2-octet-number 2:4-octet-asn:2-octet-number</pre></div></div>Let me know if you have any other questions.Thanks,Isaac KimHi Issac,Can you provide one sample value.Thanks,NaveenHi Naveen,One example value can be "0:65001:100"Thanks,Isaac Kim |
Clarificaion on NSO version link for TSDN 4.0.0 M3: Hi ,in the confluence page, TSDn 4.0.0 M3 release notes or system install., we dont see the 5.7.2.1 installer.bin file link . can u please update the location for every release if there is change in NCS version. And in the system install, it is mentioned as 5.5.2.9 , it is really confusing having different info in different places."Get the nso-5.5.2.9 bin installer file from CCO" in Since the NSO version is not same for standalone and LSA , Please update this link that reflects the proper NCS version for Standalone and LSA .NSO version for LSA : NSO Version : 5.7.1.1 .please provide the link for installer.bin file for this.And please provide the link for nso-5.7.1.1-tsdn-4.0.0-M3.tar.gz for LSA installation. | Hi Arun1. Please download the bin installer file from CCO. Below is the path for nso 5.7.2.12. We've deleted that internal system installation page. Please refer to the below link for any installation related information.3. The NSO version is same for standalone and LSA. It's 5.7.2.1 for both of them. We have updated the LSA wiki pages to reflect the same. Please refer to the below link.4. Below is the link for standalone and LSA installation:5. Once you extract the above tar file, you'll see the directories each for standalone and LSA. Below is the structure:<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"><pre class="code-java">$ tar -xf nso-5.7.2.1-tsdn-4.0.0-M3.tar.gz $ cd nso-5.7.2.1-tsdn-4.0.0-M3 $ ls -l -rw-r--r--. 1 cisco ncsadmin 67458 Mar 9 15:18 CHANGES -rwxr-xr-x. 1 cisco ncsadmin 23014 Mar 9 15:18 get_technical_support_data.sh drwxr-xr-x. 5 cisco ncsadmin 76 Mar 9 15:18 tsdn drwxr-xr-x. 4 cisco ncsadmin 46 Mar 9 15:18 tsdn-lsa</pre></div></div>Let us know if you need anything else or we are good to close the ticket.Thanks.Closing the ticket as the required information has been provided. |
Service Plan stuck inthe middle , no indication of what is wrong : UI+SSH: nso552/Public1234!LocalInstallation:/home/nso552/.0.0 | Please provide ned/device logs.The logs are on the server, Server details provided . Please look up yourselfPython VM debug mode enabled 10.56.58.145UI+SSH: nso552/Public1234!LocalInstallation:/home/nso542/.0.0/logsSorry, provided wrong server 10.56.58.197nso552/Public1234!Installation:/home/nso552/.0.0/logsThe service is struck because of an ONC ned error. The service-interface-point information available on the ONC is not synced into NSO and because of a defect in the ONC ned the optical-only service deployment (BOTTOMLEFT_BOTTOMRIGHT_400_TR_OLS) has failed. I will close ticket and open an internal ticket for the team to work on.Workaround: sync the ONC device into the NSO every time new SIPs are added. |
LSA setup found issues: I recently installed NSO FP 5.7.2.1-M4 LSA setup and seesome issues:On RFS nodes, when running command show packages package I see error in some packages:When provisioning an L2 native service I get error message: <error-message>RPCerrortowardsnso-ucs-haim1-vm2:operation_failed:for/cisco-flat-L2vpn-fp-internal-remote-site:flat-L2vpn-internal-remote-site-service:/flat-L2vpn-internal-remote-site-service:Pythoncb_validateerror.itemdoesnotexist(1):Thetemplatefilecisco-flat-L2vpn-fp-rr-parent-route-policyhasnotbeenloaded.</error-message>When provisioning an L3VPN service I get error message: <error-message>RPCerrortowardsnso-ucs-haim1-vm2:operation_failed:RPCerrortowardsPE-A:operation_failed:forns1:router/ns1:bgp/ns1:as/ns1:vrfs/ns1:vrf/ns1:address-families/ns1:address-family/ns1:af-name:'BGP'detectedthe'warning'condition'Theparentaddressfamilyhasnotbeeninitialized'</error-message> | Hi Shlomi,Thanks for reaching out to us.From the screenshot, it seems you didn't load the required packagecisco-iosxr-cli-7.38 (ncs-5.7.1-cisco-iosxr-7.38.6.tar.gz). What's the ned-id you set for the device "PE-A"?All the devices on the setup were added with NED ID cisco-iosxr-nc-7.3. If I need to use cisco-iosxr-nc-7.38 for all devices in the setup or just some?Also, isn't the attached error indicate failure on installed packages on the RFS node? I compared the packages on the RFS to those specified on the wiki, and found nothing missing.Hi Shlomi,cisco-iosxr-cli-7.38 NED is a required package for TSDN even you are only usingcisco-iosxr-nc-7.3 NED for your devices. The attached error also indicates the same, because the only "supported-ned-id" iscisco-iosxr-cli-7.38. You just need to addcisco-iosxr-cli-7.38 to your RFS node and reload packages and don't need to modify any of your devices.Hi,This seems to fix the issue of the error in the NED package and all packages appear to be loaded correctly and up.Now a new issue has come up: almost all the services I'm trying to deploy appear as 'in-progress' in CW UI and seem to have only partially successful plan. Can someone please take a look at the setup and advise?nso-ucs-haim1-vm1 (10.56.58.44) CFSnso-ucs-haim1-vm2 (10.56.58.122) RFS1nso-ucs-haim1-vm3 (10.56.58.128) RFS2Hi Shlomi,I have checked your RFS1 "nso-ucs-haim1-vm2 (10.56.58.122)" node and found that the bootstrap data *-internal-plan-monitor.xml are not loaded and that may be the root cause for services getting stuck at not-reached state.Please try to follow And you should see:% configure% unhide debug% show rfs-monitor-pathrfs-monitor-path /cisco-flat-L2vpn-fp-internal-local-site:flat-L2vpn-internal-local-site/cisco-flat-L2vpn-fp-internal-local-site:flat-L2vpn-plan;rfs-monitor-path /cisco-flat-L2vpn-fp-internal-remote-site:flat-L2vpn-internal-remote-site/cisco-flat-L2vpn-fp-internal-remote-site:flat-L2vpn-plan;rfs-monitor-path /cisco-flat-L2vpn-fp-internal-site:flat-L2vpn-internal-site/cisco-flat-L2vpn-fp-internal-site:flat-L2vpn-plan;rfs-monitor-path /cisco-flat-L3vpn-fp-internal:flat-L3vpn-internal/cisco-flat-L3vpn-fp-internal:flat-L3vpn-plan;rfs-monitor-path /cisco-rsvp-te-fp:rsvp-te/tunnel-te-plan;rfs-monitor-path /cisco-sr-te-cfp-internal:sr-te/cisco-sr-te-cfp-sr-odn-internal:odn/cisco-sr-te-cfp-sr-odn-internal:odn-template-plan;rfs-monitor-path /cisco-sr-te-cfp-internal:sr-te/cisco-sr-te-cfp-sr-policies-internal:policies/cisco-sr-te-cfp-sr-policies-internal:policy-plan;After that you may try to recreate the services. Please let me know if you are still facing any issue.Hi LinmaoThis indeed fixed the issue and services are now successfully deployed with full plans.I'm still not sure what could have happened to cause the missing bootstrap data. I'm pretty sure these commands were previously entered, as they were also in the other RFS node. Any ideas what could have caused this?You may close this JIRA case.Thanks for confirming the issue is resolved!It seems that the bootstrap setting was deleted via webui at around 31-Mar-2022::09:54:29.830 UTC time. |
Invalid namespace prefix: cisco-flat-L2vpn-fp: admin@ncs> show packages package package-version PACKAGENAME VERSION---------------------------------------------cisco-ios-cli-6.80 6.80.1cisco-iosxr-cli-7.38 7.38.6cisco-iosxr-nc-7.3 7.3.2cisco-nso-nc-5.7 5.7cisco-sr-te-cfp 4.0.0cisco-tm-tc-fp 4.3.0-98cisco-tsdn-core-fp-common 4.0.0core-fp-common 1.30.0core-fp-plan-notif-generator 1.0.6custom-template-utils 2.0.8custom-template-utils-ned 1.0cw-device-auth 4.1.1cw-dlm-fp 4.3.0-nso-5.7lsa-utils 1.0.0tm-tc-multi-vendors 4.3.0-98admin@ncs>admin@nso:~$ ncs --version5.7.2.1admin@nso:~$with above following packagesseeing below error while load merge of config filesadmin@ncs> configureEntering configuration mode privateadmin@ncs% unhide debugadmin@ncs% load merge SR-status-codes.xmladmin@ncs% load merge RSVP-TE-status-codes.xmladmin@ncs% load merge L3VPN-status-codes.xmladmin@ncs% load merge L2VPN-status-codes.xmladmin@ncs% load merge IETF-TE-status-codes.xmladmin@ncs% load merge IETF-L3NM-status-codes.xmladmin@ncs% load merge IETF-L2NM-status-codes.xmladmin@ncs% commitCommit complete.admin@ncs% load merge SR-plan-notification-settings.xmladmin@ncs% load merge L3VPN-plan-notification-settings.xmladmin@ncs% load merge L2VPN-plan-notification-settings.xmladmin@ncs% load merge IETF-TE-plan-notification-settings.xmladmin@ncs% load merge IETF-L3NM-plan-notification-settings.xmladmin@ncs% load merge IETF-L2NM-plan-notification-settings.xmladmin@ncs% commitAborted: 'kickers data-kicker plan-notification-kicker-/cisco-flat-L2vpn-fp:flat-L2vpn-plan monitor': Invalid namespace prefix: cisco-flat-L2vpn-fp | You are missing 'cisco-flat-L2vpn-fp' package.Thanks,Regithanks, now the CFS node is setup, i am seeing issue in setting RFS node.10.64.96.206 admin/Crosswork123!admin@nso-cluster-6:~$ cd nso-5.7.2.1-tsdn-4.0.0-M4/tsdn-lsa/tsdn-lsa-rfs/bootstrap-data/admin@nso-cluster-6:~/nso-5.7.2.1-tsdn-4.0.0-M4/tsdn-lsa/tsdn-lsa-rfs/bootstrap-data$ ncs_cliadmin connected from 64.103.219.103 using ssh on nso-cluster-6admin@ncs> configureEntering configuration mode privateadmin@ncs% load merge SR-status-codes.xmlError: on line 2: unknown element: status-code-cfp in /cfp-common-status-codes:status-code-cfpadmin@ncs% load merge SR-internal-plan-monitor.xmladmin@ncs% load merge RSVP-TE-status-codes.xmlError: on line 2: unknown element: status-code-cfp in /cfp-common-status-codes:status-code-cfpadmin@ncs% load merge RSVP-TE-internal-plan-monitor.xmladmin@ncs% load merge rfs-custom-template-settings.xmladmin@ncs% load merge L3VPN-status-codes.xmlError: on line 2: unknown element: status-code-cfp in /cfp-common-status-codes:status-code-cfpadmin@ncs% load merge L3VPN-internal-plan-monitor.xmladmin@ncs% load merge L2VPN-status-codes.xmlError: on line 2: unknown element: status-code-cfp in /cfp-common-status-codes:status-code-cfpadmin@ncs% load merge L2VPN-internal-plan-monitor.xmladmin@ncs% load merge dispatch-map-settings.xmladmin@ncs% load merge commit-queue-settings.xmladmin@ncs% load merge bootstrap-autopopulate-dispatch.xmladmin@ncs% commitadmin@ncs% exitThere are uncommitted changes.Discard changes and continue? yesadmin@ncs> exitadmin@nso-cluster-6:~/nso-5.7.2.1-tsdn-4.0.0-M4/tsdn-lsa/tsdn-lsa-rfs/bootstrap-data$ lsL2VPN-internal-plan-monitor.xml RSVP-TE-internal-plan-monitor.xml bootstrap-autopopulate-dispatch.xmlL2VPN-status-codes.xml RSVP-TE-status-codes.xml commit-queue-settings.xmlL3VPN-internal-plan-monitor.xml SR-internal-plan-monitor.xml dispatch-map-settings.xmlL3VPN-status-codes.xml SR-status-codes.xml rfs-custom-template-settings.xmladmin@nso-cluster-6:~/nso-5.7.2.1-tsdn-4.0.0-M4/tsdn-lsa/tsdn-lsa-rfs/bootstrap-data$ ncs_cliUser admin last logged in 2022-04-13T04:46:29.105763+00:00, to nso-cluster-6, from 64.103.219.103 using cli-sshadmin connected from 64.103.219.103 using ssh on nso-cluster-6admin@ncs> show packages package package-version PACKAGENAME VERSION---------------------------------------------cisco-flat-L2vpn-fp-internal 4.0.0cisco-flat-L3vpn-fp-internal 4.0.0cisco-ios-cli-6.77 6.77.9cisco-ios-cli-6.80 6.80.1cisco-iosxr-cli-7.38 7.38.6cisco-iosxr-nc-7.3 7.3.2cisco-iosxr-nc-7.315 7.315cisco-iosxr-nc-7.4 7.4.2cisco-iosxr-nc-7.5 7.5.1cisco-rsvp-te-fp 4.0.0cisco-sr-te-cfp-internal 4.0.0cisco-tm-tc-fp 4.3.0-98cisco-tsdn-core-fp-common 4.0.0core-fp-common 1.30.0core-fp-delete-tag-service 1.0.5core-fp-plan-notif-generator 1.0.6custom-template-utils 2.0.8cw-device-auth 4.1.1cw-dlm-fp 4.3.0-nso-5.7flat-l2vpn-multi-vendors 4.0.0flat-l3vpn-multi-vendors 4.0.0lsa-utils 1.0.0rsvp-te-multi-vendors 4.0.0sr-te-multi-vendors 4.0.0tm-tc-multi-vendors 4.3.0-98Hi Ajitha,It seems you are skipping some steps as you are missing "unhide debug". Please follow RFS installation wiki: .Thanks,RegiHi Ajitha,Please let me know by EOD today if you have further issues; otherwise, I will go ahead and close this ticket.Thanks,RegiClosing this ticket since original issue was resolved and there are not additional queries from the submitter |
steps to make CNC to function after change management IP on device: There is an use case comes for management IP address change on device. What are the steps for CNC to handle this.On CNC side, user may need to update device info manually on Device management page.Question is what extra steps needs to be done on NSO to make all 3 components (CNC, Device, NSO) are in sync. Thanks. | Hi Crystal,Is the requirement just for the mgmt ip change?Can we consider rest of the data related to device will stay the same i.e. configs ?ThanksSahithiHi Sahithi,Yes, just the mgmt ip change. Rest of the config on the device stay the same.Thanks.-Crystal |
Unable to create L2P2P in Drop 8: Hi,I am unable to create L2 P2P in drop 8 and gives me below error in NSO UI.errors: reason: illegal reference. paths: /l2vpn-ntw:l2vpn-ntw/vpn-services/vpn-service{NSS-L2-P2P-internal}/vpn-nodes/vpn-node{xrv9k-23}/cisco-l2vpn-ntw:te-service-mapping/te-mapping/odn/route-policy. path: /l2vpn-ntw:l2vpn-ntw/vpn-services/vpn-service{NSS-L2-P2P-internal}/vpn-nodes/vpn-node{xrv9k-23}/cisco-l2vpn-ntw:te-service-mapping/te-mapping/odn/route-policySetup:172.27.226.127 (nso/Vtsisco@123!)ThanksNaveen | Thank you for the ticket. Investigating.Connected with the submitter and fixed the issue. The slo-sle-template was missing the forwarding-plane-policy which references to a odn policy. After adding the same, we were successfully able to create the service. |
RFS Detach Steps: Hi Team,I have tried removing one of my RFS node manually from CFS CLI using the following CMD:admin@ncs% delete cluster remote-node rfs-3Output:admin@ncs% run show cluster connectionREMOTE LOCAL REMOTENODE ADDRESS PORT CHANNELS USER USER STATUS TRACE------------------------------------------------------------------------rfs-2 10.194.57.180 2022 - admin admin up disabledrfs-1 10.194.57.13 2022 - admin admin up disabledBit, from the CFS-UI I could still able to see the rfs-3 and also able to perform check-sync successful.Please help to share the complete detach steps if any.NSO version: 5.7.2.1TSDN cfp: 4.0.0 M4Thanks,Dinesh | Closing the ticket as the below cmd helped in removing the RFS node completely.admin@ncs% delete devices device rfs-3Thanks,Dinesh |
NSO LSA HA Wiki Guide: Hi Team,Please help to share NSO LSA HA Installation Wiki guide.Thanks,Dinsh | Please follow NSO documentation for NSO HA installation: Thank you for the given references.The ticket can be closed. |
JWT Auth file update for Crosswork: As per link,We need to use cert.pem and crosswork.pem filesBut, there is no cert.pem file under /home/cisco .Also, the file download from crosswork is not "crosswork.pem" it is crosswork.cerWould you please suggest from where we can get this cert.pem and crosswork.pem files.Also, the new Drop 7, jwt auth link does not have an example for using crosswork fqdn name instead of ip address. Kindly suggest/update the field changes needed for using fqdn name in place of crosswork ip address. | Hi Ajitha, You should be able to download certificate from browser and save it in pem formatThe fqdn related changes are updated here: PLMK if this helps or if anyother info is required |
NSO 6.0 M9 drop: Same revision dates was used for cisco-rsvp-te-fp.yang: cisco-rsvp-te-fp.yang has two Revisions with the same dates: revision 2023-05-04 { description "Modified default value for iosxr-default-ned-id to cisco-iosxr-cli-7.52"; } revision 2023-05-04 { description "Modified default value for iosxr-default-ned-id to cisco-iosxr-cli-7.49"; } | Hi Quy,Thanks for pointing this out. This is a typo, we will update the revision date and it will be released as part of next drop.Thanks,NikhilRevision date will be fixed and will be release with the next build drop. |
Customized NSO FP not operationally up: Customized NSO FP not operationally up in 10.195.165.75 - xrd1/xrd1 | Kindly guide to troubleshoot furtherCan you please share a copy of the customized packages?Copied the files below.i copied them in /var/opt/ncs/packages as well - my-l2vpn.tar.gz, my-l3vpn.tar.gz, my-sr-policy.tar.gz. Hi Reginald, As discussed, the attached tar file doesn't have any hidden file under template folder. But it introduces a hidden file in /var/opt/ncs/packages. Kindly check and adviceClosing this ticket. It seem packages were not tar'ed properly. There are a lot of "._" prefixed files. This article seems related to the issue: |
Provisioning Service from CAT UI throws error " server didnot respond to the request within 25 sec": Hi,While trying to provision l2vpn p2p srte service from CNC UI , facing the commit error "service did not respond to the request within 25 seconds". | payload atatched Hello Arun,I would need more information to RCA this issue.Would you be able to provide ssh credentials to your NSO node so I can check a few things? I will not modify anything.Thanks,Isaac KimHi Isaac,NSO: 10.56.116.240 ( nso/Public1234!)Thanks,Arun.M.GHi Arun,I can see in your logs the following:<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"><pre class="code-java">% Failed to commit one or more configuration items during a pseudo-atomic operation. All changes made have been reverted.!! SEMANTIC ERRORS: This configuration was rejected by!! the system due to semantic errors. The individual!! errors with each failed configuration command can be!! found below.l2vpnxconnect group L2NM-P2p-SRTE-742 p2p L2NM-P2p-SRTE-742 neighbor ipv4 126.1.1.30 pw-id 742 mpls label local 742 remote 753!!% Invalid argument: Remote label already assigned to neighbor ! !!!end</pre></div></div>It seems like NED error : "Remote label already assigned to this neighbor".It seems like later, there was a service update made to this service "L2NM-P2p-SRTE-742" and the plan became reached.Could you confirm the following?<ol>Did service provisioning show failed status when checking CNC UI after the timeout?Did service update make service go into provisioned state?Are you using CQ or no-CQ commits for these operations? I assume no-CQ was used which caused all changes to be reverted. This makes more sense in regards to the current plan status which is reached with a service update.</ol>Thanks,Isaac KimHi Isaac,yes. there was a commit failed due to the below mentioned label conflict. i have corrected after that.but sometime, even for proper service also, we are facing the commit error for time out.below are the answer .,1] Did service provisioning show failed status when checking CNC UI after the timeout? >> Service provisioning doesnt happen at all. it will stay on the same provisioning page.2] Did service update make service go into provisioned state? >> yes. i tried these to modify the SR policy in l2vpn p2p sr service. it worked.3] Are you using CQ or no-CQ commits for these operations? I assume no-CQ was used which caused all changes to be reverted. This makes more sense in regards to the current plan status which is reached with a service update. >> i am not modifying anything in the Advanced option in CNC UI during the commit.it is always by default.Note: this issue is intermittent. sometimes it commits properly.Hi Arun,Thank you for the quick reply. Seems like there is a system slowdown which might be the cause of the symptoms described. Let me take another look at your system and see if we can isolate the cause of slowdown.I may execute few operations on NSO to check NSO system responsiveness. I will not make any changes.Thanks,Isaac KimHi Arun,I ran a few checks and things seem to be okay:<ol>L2 Service Callback max time delta is 0.05 seconds (across all services)NSO L2 service get-modification reverse responds quickly on NSO CLINSO L2 service get-modification reverse responds quickly on NSO Web UI"top" shows low overall system resource utilizationCorrect ulimit fd limit</ol>So it didnt seem like NSO itself was having any slowdowns.Next I tried to test southbound operations such as device connect, device config pull, etc. Here we saw some greater levels of delay:<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"><pre class="code-java">admin@ncs% request devices device NCS55A2-SDN-112 compare-config | details very-verbose2022-04-06T20:27:03.585 device NCS55A2-SDN-112: compare-config...2022-04-06T20:27:03.586 device NCS55A2-SDN-112: taking device lock... ok (0.000 s)2022-04-06T20:27:03.599 device NCS55A2-SDN-112: connect...2022-04-06T20:27:04.410 device NCS55A2-SDN-112: cisco-iosxr-cli-7.38: connecting... ok (0.466 s)2022-04-06T20:27:05.370 device NCS55A2-SDN-112: connect: ok (1.771 s)2022-04-06T20:27:05.370 device NCS55A2-SDN-112: show...2022-04-06T20:27:05.459 device NCS55A2-SDN-112: cisco-iosxr-cli-7.38: reading config...2022-04-06T20:27:10.281 device NCS55A2-SDN-112: cisco-iosxr-cli-7.38: transforming input... ok (0.009 s)2022-04-06T20:27:10.293 device NCS55A2-SDN-112: cisco-iosxr-cli-7.38: reading config: ok (4.834 s)2022-04-06T20:27:10.296 device NCS55A2-SDN-112: cisco-iosxr-cli-7.38: retrieving transaction-id... ok (6.791 s)2022-04-06T20:27:17.090 device NCS55A2-SDN-112: cisco-iosxr-cli-7.38: extended parsing... ok (0.017 s)2022-04-06T20:27:17.108 device NCS55A2-SDN-112: cisco-iosxr-cli-7.38: populating cdb... ok (0.599 s)2022-04-06T20:27:17.708 device NCS55A2-SDN-112: show: ok (12.338 s)2022-04-06T20:27:17.726 device NCS55A2-SDN-112: releasing device lock2022-04-06T20:27:17.726 device NCS55A2-SDN-112: compare-config: ok (14.141 s)[ok][2022-04-06 20:27:17][edit]admin@ncs% request devices device ASR9901-SDN-30 compare-config | details very-verbose2022-04-06T20:29:42.512 device ASR9901-SDN-30: compare-config...2022-04-06T20:29:42.513 device ASR9901-SDN-30: taking device lock... ok (0.000 s)2022-04-06T20:29:42.524 device ASR9901-SDN-30: connect...2022-04-06T20:29:43.326 device ASR9901-SDN-30: cisco-iosxr-cli-7.38: connecting... ok (1.954 s)2022-04-06T20:29:46.278 device ASR9901-SDN-30: connect: ok (3.753 s)2022-04-06T20:29:46.278 device ASR9901-SDN-30: show...2022-04-06T20:29:46.353 device ASR9901-SDN-30: cisco-iosxr-cli-7.38: reading config...2022-04-06T20:29:51.034 device ASR9901-SDN-30: cisco-iosxr-cli-7.38: transforming input... ok (0.009 s)2022-04-06T20:29:51.047 device ASR9901-SDN-30: cisco-iosxr-cli-7.38: reading config: ok (4.693 s)2022-04-06T20:29:51.049 device ASR9901-SDN-30: cisco-iosxr-cli-7.38: retrieving transaction-id... ok (4.059 s)2022-04-06T20:29:55.112 device ASR9901-SDN-30: cisco-iosxr-cli-7.38: extended parsing... ok (0.013 s)2022-04-06T20:29:55.126 device ASR9901-SDN-30: cisco-iosxr-cli-7.38: populating cdb... ok (0.429 s)2022-04-06T20:29:55.556 device ASR9901-SDN-30: show: ok (9.277 s)2022-04-06T20:29:55.576 device ASR9901-SDN-30: releasing device lock2022-04-06T20:29:55.576 device ASR9901-SDN-30: compare-config: ok (13.063 s)[ok][2022-04-06 20:29:55][edit]</pre></div></div>We typically see half the response time for compare-config our real devices, but this is dependent on device and setup. But now I can see how this can potentially cause a problem, especially if NSO pull device config as part of the service provisioning transaction.This combined with the fact you are using no-CQ (default commit setting) and the fact that CNC UI has 25 second timeout, maybe CNC UI is waiting too long (over 25 seconds) for both device to fully provision.If you would like to see a full breakdown of timings for your commit, you can do the following:1. Log into NSO CLI 2. Enter config mode3. load merge L2 service payload (or set config) 4. run => "commit | details very-verbose"5. paste output hereThen I think it will be easier to isolate exactly which device operation is causing the most delay. It will also reveal if we are exceeding CNC UI timeout value.Thanks,Isaac KimHI Isaac,Thanks for the details and clarification.I will try to do from Ncs_cli using load merge L2 service payload and let u know. our labs are down . if will be back on monday . once it is back, i will check and let you know.Thanks,Arun.M.GDevice transaction phases revealed device response exceeded UI timeout value. |
Validation for policies created with IPv6 endpoint without SRv6 enable: During our test on an IPv6 CNC cluster, create an SR policy with IPv6 tail end info in the payload but SRv6 is not enabled. Configuration is pushed successfully but it causes the policy flapping. PCE sends create/delete message continuously. Please refer to the attach email discussion for more details. According to XTC team, a policy with IPv6 endpoints but SRv6 is not enabled is not a supported scenario.Question 1: Is it possible we add some validation in the model on CFP side?A similar scenario for transport slice. Our topology is configured as a dual stack topology. When create slice we do not enable SRv6, but as the result of slice creation, policies with IPv4 router TE-ID and IPv6 router TE-ID are created and it also have the policy flapping issue due to SRv6 is not enabled in the ODN attached to the slice.Question 2: What is the best way to communicate the behavior to the user for slice if a dual stack topology is configured? | Hi Crystal,Please proceed to file CDETS so we can solve the Question 1.We believe validation triggered for Question 1 will solve Question 2.Please let us know if this helps.Regards,Janaki DuggiralaHi Janaki,I have created CSCwh76502 to track.Thanks.-CrystalThank you Crystal, closing this ticket so the issue maybe tracked with the CDETS CSCwh76502 |
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. |
ELAN Config Problem: Device version we use is IOS-XR 7.5.2.15INSO 5.7.1.1We have deployed l2vpn in mode of any-to-any, but the config of device is failing (and also the corresponding flat-internal service is not created). This is the error we get:reason: RPC error towards PE-B: operation_failed: for ns1:l2vpn/ns1:bridge/ns1:groups/ns1:group/ns1:bridge-domains/ns1:bridge-domain/ns1:interfaces/ns1:interface/ns1:interface-name: Invalid argument: VPLS Bridge domains not supported on this platformI also tried to manually put this config into our device and got the same error (attached).Also attached the xml with the config we use. | What platform are you using?Also concerning the email:<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"><pre>I just want to emphasize that if I add - to the service name, I get some other error: reason: /cisco-flat-L2vpn-fp-internal-site:flat-L2vpn-internal-site-service{L2NM-EVPN-ELAN-270-internal PE-A_ELAN-PBB-NATIVE}: Python cb_validate error. Unknown error (66): cisco-flat-L2vpn-fp-um-evpn-multipoint-template.xml:134 Expression '{$GROUP_NAME}_evi_{$EVI_ID}' resulted in an incompatible value 'L2NM-EVPN-ELAN-270-internal_evi_4' for /ncs:devices/device{PE-A}/config/Cisco-IOS-XR-um-l2vpn-cfg:l2vpn/bridge/groups/group{L2NM-EVPN-ELAN-270-internal}/bridge-domains/bridge-domain/bridge-domain-name STATUS_CODE: TSDN-L2VPN-303 REASON: Config push failed CATEGORY: device SEVERITY: ERROR Context [name = Configuration Error, message = Could not apply service config on site state = {'Device': 'PE-A', 'Site': 'PE-A_ELAN-PBB-NATIVE', 'Service': 'L2NM-EVPN-ELAN-270-internal'}]</pre></div></div>The issue here is not adding the "-" but rather there's a character limit of 27 for `bridge-domain-name`, if you do not specify the bridge name in your payload the service will try to create it using some concatenations including service name. I'll create an internal ticket for this to try and clear up the error messageThanks,Regiwe usu NSO 5.7 along with FP 5.7.1.1if you need this is the server (nso5711/Public1234!). Device creds is admin/Public1234!. I meant device platform are you trying use the feature on an XRV9K?This feature is not supported by XRV9K. Please try ASR9K or NCSok thx. where does it specified what platform support this feature? I did not see it in the install guide or release notes ()This is an engineering build, so documentation may not be completeWe only tested this feature withVXR ASR9K and real device NCS5501We used this to bringup the ASR9K:Had a call with Idan, Haim, and Yevgeny. Asked them to use ASR9k and send them sample payloads and service device mappings via email |
Failed to start ncs when trying to intsall ncs 5.7.2.1: While installing "nso-5.7.2.1.darwin.x86_64.installer.bin" image, getting the below error "/opt/ncs/ncs-5.7.2.1/bin/ncs_conf_tool: Exec format error" | Hi KritikaPlease let us know how to access the setup where this error is seen so that we can debug the issue.Thank you.Hi KritikaSeems like you're using darwin image for Linux OS.Please use the linux image (nso-5.7.2.1.linux.x86_64.installer.bin) to install NSO for Linux OS.Thanks.Closing the ticket as the required information is provided to the user |
LSA setup status down: Hi,I tried to install an LSA setup.After configuring cluster I see the RFS nodes on the CFS node, but "show cluster" command shows status down. | Hi Sholimi,Have you run the command 'request cluster remote-node <rfs-name> ssh fetch-host-keys'?Please share your setup info. So I could take a lookThanks,LinhSetup details:nso-ucs-haim1-vm1 (10.56.58.44) CFSnso-ucs-haim1-vm2 (10.56.58.122) RFS1nso-ucs-haim1-vm3 (10.56.58.128) RFS2Credentials: nso5721/ Public1234!SSH:nso5721/ Public1234!Hi,This command seem to have done the trick. Thank you.You may close the case.Regards,Shlomi |
l2vpn route policy ->evpn-route-type ser: EVPN set is not being translated to device configuration. They yellow highlighted part is expected but not generated .In 4.0 it used to be a free text and user responsibility. In 5.0 it is suppose to be generated out of configuration, but is not cheapening | Hi Yevgeny,Please provide us the complete route-policy payload, since we need the policy-definition to investigate the policy being pushed to device.Thanks,NikhilHi Nikhil,PFA the payload including the service and the route policy. This was tested on a clean device configuration and failed to produce a working service.Thanks, Shlomi Had meeting with Customer. Requested updated payload for route-policy using RFC standard.Payload from customer contains 2 conditions with 1 action. This is not allowed as mentioned in wikiRequested customer to create 2 statements for each condition.Issue fixed for L2 route-policy, confirmed by customer as above.Following our meeting PFA the extra policy payloads we have been using and that have been failing Hello Shlomi, The payloads you have provided have missing vpn-nodes. Please check and fix. I have attached the sample payload we have tested with. We see the route-policy being pushed successfully to the device. As you can see in the screenshot, the APPEND_RPL was appended to the route-policy --> L3VPN_NM-SRTE-ODN-PE-A-44 Note: Please keep in mind that when you use the extra-policy field it will only push the string associated to the policy and not the policy definition. Let us know if all questions are answered.After investigating and undeploying / redploying L2VPN services with route policies I came across a weird finding: The provisioning is successful but only for the first service, if there is another L2 service that uses same evpn-route-type tag, the tunnel will fail to come up. I tried removing all previous services and provisioned one by one. The first one was successful, but after the second one, the tunnels belonging to the first service were gone. As the evpn-route-type tag can only have values 1, 3 this allows us to provision no more than two services successfully.Please advise.We would like to clarify thatevpn-route-type is not a "tag" but refers to types of traffic so it can be associated with multiple services.There is no validation stating that it should be only 1 and 3 either.Please also share your setup details in this ticket for further investigation.Adding the meeting minutes here:verified the commands being sent from NSO to the VXR are accurate and fit the info on postman commandsWhen using several EVPN_SET configurations in different services, they collide but we cannot tell if it is a VXR related limitationable to provision services 420 ; 290 simultaneously by dividing EVPN_SETs 1 ; 3 between themTE tunnels for service 250 are still not operational, possibly due to missing BGP connectivity between PE-A and PE-CL3 services might also be missing due to same issue A.I CFP team to continue looking into it and updateNikhil will share VXR credentials with CFP team for further investigationHad a meeting with the user and cleared the doubts they had. The services were working as expected.Had a meeting with the user and cleared the doubts they had. The services were working as expected. |
Questions on Dynamic MVPN Provisioning: Hi Team,I am looking for some information on Dynamic MVPN Provisioning, queries are listed below:1) For Static MVPN Model, how many Static Tree-SID policies can be attached to a single node, is there any limit?2) For Static/Dynamic MVPN Model, if I have attached a route policy to my MVPN service, what will happen if I update it or delete it. Will that be updated or removed from the device config as well.3) What are the allowed values for group-acl-ipv44) As this is P2MP feature, do we support point-to-point vpn-service-topology.5) For Any-To-Any, can I have more than one root in MVPN service.6) For hub-and-spoke, I assume there shoud be one root and other nodes as leafs, will there be any error if I define spoke as root or vice versa.7) Can I attached a dynamic tree-sid policy to Static MVPN Model.Thanks,Kanchan | Hi,Also wanted to check do we have alarms support for this feature?Thanks,KanchanHi Kanchan,Please find the answers for the following questions asked.1. For Static MVPN Model, how many Static Tree-SID policies can be attached to a single node, is there any limit? No 2. For Static/Dynamic MVPN Model, if I have attached a route policy to my MVPN service, what will happen if I update it or delete it. Will that be updated or removed from the device config as well. Yes. It will be updated /removed from the device config as well 3. What are the allowed values for group-acl-ipv4 It is a String. As per yang definition , The value is an integer ranging from 3000 to 3999 or a string of 32 case-sensitive characters. 4. As this is P2MP feature, do we support point-to-point vpn-service-topology. No.Thanks And Regards,Nishad Subair.Hi Nishad,Can you also provide answers for questions 5, 6 , 7 and alarm support?Thanks,KanchanHi Kanchan,5) For Any-To-Any, can I have more than one root in MVPN service.YesThanks And Regards,Nishad Subair.Adding email thread here to keep a track. Thank you Kanchan. Hope all the queries have been answered. Let us know if we can close the ticket. |
NSO 5.7.6 -TSDN 4.1 M2 - to NSO 6.0 - TSDN 5.0.0 -M4: Hi, We have Uni-d scale setup that is hvaing 5.7.6 TSDN 4.1.0 M2 build.we have 30k services and having 60 devices.do we have migration/Upgrade support ? in TSDN 5.0.0 , we have schema changes ., and all the services payload structure has changed. do we still support of Migration ?Thanks,Arun.M.G | Hi Arun,You are correct. Dued to model changes in 5.0, migration/upgrade is not supported from 4.1 to 5.0 M4Regards,Linh |
restconf patch API is not updating the list node instead it create a new entry.: restconf 'patch' API is not updating the list node instead it create a new entry. | Hi Demeke,Patch restconf is for updating existing service. Please double check the service name is matching with an existing service. Otherwise, it would create a new service name. Thanks,LinhHi Linh, Yes patch restconf is for updating existing service. But the question is inside the service data if user want to update the value of a single entry from the list it will create new entry in the list. And that seems an issue.Thanks,Demeke. Hi Demeke,Can you share the patch update payload?Thanks,Linh{"cisco-sr-te-cfp:sr-te": {"cisco-sr-te-cfp-sr-policies:policies": {"sid-list": [{"name": "sid1","sid": [{"index": 2,"mpls": {"label": 11}}]}]}}}Above is the patch payload and the update was the index value from 1 to 2.After the update below is the result { "cisco-sr-te-cfp:sr-te": { "cisco-sr-te-cfp-sr-policies:policies": { "sid-list": [{ "name": "sid1", "sid": [{ "index": 1, "mpls": { "label": 11 } }, { "index": 2, "mpls": { "label": 11 } }] }] } } }Expectation was to update the index value but the patch creates a new entry in the list.{ "index": 2, "mpls": { "label": 11 } }Hi Demeke,This is how sid-list defined yang model. list sid { key index; leaf index { tailf:info "<1-65535> - Sid Index"; description "<1-65535> - Sid Index"; type uint32 { range "1..65535"; } tailf:cli-allow-range; } min-elements 1;Since index is defined as key, you can not update it but deleting the whole index and then recreate with different key in your case is index 2.Thanks,LinhHi Linh,Yes it is the key and currently when user update the key values it creates new entry. The request is to enhance the restconf patch API to handle this scenario to be able to update key values? expectation is instead of forcing user to delete this key value and then create new, can we handle this internally in the API implementation and modify key values?Thanks,Demeke. |
Onboard ncs_netsim devices to CW: Need some guidance on how devices simulated with nets can be onboarded to CW. | Hi Sachin,Please refer the attached document regarding steps to bring ip netsim devices.Regarding other steps , please connect with the specific team for the same. We are from CFP team , so might not be able to provide onboarding details.Regards,Nishad Subair.Hi Nishad,I heard NSO CFP team tested the scale with 3500 devices. Assuming they are netsim devices, would you be able to provide the information on how those were setup and onboarded to NSO. This will help us understand and figure out how to onboard them on CW/CNC as well.Regards,-SrinivasanHi Srini,we have not done this with netsim devices, we did with southbound locked devices.We plan to test netsim by End of January.ThanksPriyanka |
NCS- 6.0 M4 +: L2VPN P2p, RSVP, creation, we are seeing that MPLS label is compulsory: 1) CFP = nso-6.0-tsdn-5.0.0-M4+ENG-34.tar.gz2) Create l2vpn and RSVP. 3) While committing the payload in NSO, we see that it asking MPLS label mandatory.4) Please check the attached document5) Logs: 10.56.112.77:/tmp/data_121222_133343_dir/data_121222_133343.tgzlogin: auto1/Public1234! | In TSDN 4.0 and 4.1 FP, mpls-label tagging was not mandatoryand device also doesnt need to have mpls-label as mandatory field.<mpls-label xmlns="http://cisco.com/ns/nso/fp/examples/cisco-l2vpn-ntw">111</mpls-label>can we know why this has been mandatory now ?Hello, we have created an internal ticket to fix this issue.Regards,Janaki DuggiralaHi janaki,Shouldnt we have CDETS for this as this is CFP bug?and also, why do we need to mention XMLNS for many tagging especially?for eg., <control-word xmlns="http://cisco.com/ns/nso/fp/examples/cisco-l2vpn-ntw">yes</control-word><metric xmlns="http://cisco.com/ns/nso/fp/examples/cisco-l3vpn-ntw">123</metric><te-service-mapping xmlns="http://cisco.com/ns/nso/fp/examples/cisco-l2vpn-ntw">in ietf-te tunnel:., <head-end xmlns="http://cisco.com/ns/nso/fp/examples/cisco-te">without this xmlns, it says unknown element. Regarding xmlns:This is expected behavior with the new IETF model updates from TSDN 5.0 M3.Per design we have IETF augmentations in an external model, so it is required to define xmlns (namespace).Regarding CDETS, you may file one if you would like to.Thank you.This issue has been fixed and merged and is available in TSDN 5.0 M5 release.CSCwd93202 - is raised. Issue is not resolved in M5. Details are mentioned in cdetsHi Sampath, I did verified the issue are fixed before the M5 release. Does the M5 installed at 10.56.112.77? I will look at this server if you confirm.Thanks,Linhpls check : 10.56.116.138 as mentioned in the cdets10.56.112.77 is also M5, I tested on 10.56.116.138, which is also same version.It installed a wrong build. The file size of ncs-6.0-ietf-l2vpn-nm-EXAMPLE-5.0.0.tar.gz is different from 6.0 release installed in my setupYour setup:/opt/ncs/packages$ ls -ltr | grep l2vpn-nm<del>rw</del>------ 1 root root 148845 Dec 15 11:03 ncs-6.0-ietf-l2vpn-nm-EXAMPLE-5.0.0.tar.gzMine setup:$ ls -ltr | grep l2vpn-nm-rwxr-xr-x. 1 root root 149149 Dec 20 20:36 ncs-6.0-ietf-l2vpn-nm-EXAMPLE-5.0.0.tar.gzI also looked the codes in your ncs-6.0-ietf-l2vpn-nm-EXAMPLE-5.0.0.tar.gz. It does not have python codes with the fix.Please get a correct build and install it again-Linh |
NSO CFP - 5.0 - M4 yang file changed without revision dates.: under ietf-l3, the cisco-l3vpn-ntw got modified but no revision found.module cisco-l3vpn-ntw { yang-version 1.1; namespace "http://cisco.com/ns/nso/fp/examples/cisco-l3vpn-ntw"; prefix cisco-l3nm; import ietf-l3vpn-ntw { prefix l3nm; } import cisco-mvpn { prefix cisco-mvpn; } import tailf-common { prefix tailf; } import tailf-ncs { prefix ncs; } import ietf-inet-types { prefix inet; } import tailf-kicker { prefix kicker; } import ietf-vpn-common { prefix vpn-common; } import cisco-tsdn-core-fp-common { prefix tsdn-core-fp-common; } import lsa-utils { prefix lsa-utils; } import resource-allocator { prefix ralloc; } import id-allocator { prefix idalloc; } import cisco-pm-fp { prefix cisco-pm-fp; } import custom-template-hook { prefix ct-hook; } import ietf-routing-types { prefix rt-types; reference "RFC 8294: Common YANG Data Types for the Routing Area"; } description "IETF L3VPN NTW Cisco NSO Modifications"; revision 2022-10-03 { description "Removed: container performance-measurement under l3vpn-ntw -> vpn-services -> vpn-service -> vpn-nodes -> vpn-node -> vpn-network-accesses -> vpn-network-access -> ip-connection -> oam"; } | Hi Quy,Thank you for reporting this .We will work on it and update this revisions as part of the next release.Regards,Nishad SubairThanks Nishad - will wait for M5 for the revision on this file. |
Test - Please close this: Testing... -Please close this JIRA | Test Ticket. Closing |
L3VPN service with XE with NSO 5.0 M4: We are not able to create l3vpn service with XE endpoint, we used sample payload from release notesHi Sahiti,Under list of known issues I see followingI tried putting RD under node but running into another issue<errors xmlns="urn:ietf:params:xml:ns:yang:ietf-restconf"> <error> <error-type>application</error-type> <error-tag>malformed-message</error-tag> <error-path xmlns:l3nm="urn:ietf:params:xml:ns:yang:ietf-l3vpn-ntw">/l3nm:l3vpn-ntw/l3nm:vpn-services</error-path> <error-message>unknown element: RD in /l3nm:l3vpn-ntw/l3nm:vpn-services/l3nm:vpn-service/l3nm:vpn-nodes/l3nm:vpn-node</error-message> </error></errors>Has anyone else able to successfully create service for XE that we can leverage the payloadWe were using sample payload from Yevegeny and team, and that is based on NSO CFP documentation as wellThx,VaishaliFrom: Sahithi Patibandla (sahpatib) <sahpatib@cisco.com>Date: Tuesday, December 6, 2022 at 9:29 AMTo: Vaishali Mithbaokar (vmithbao) <vmithbao@cisco.com>, Yevgeny Chechelnitsky (ychechel) <ychechel@cisco.com>, Manivel Sengottuvel -X (msengott - HCL TECHNOLOGIES LIMITED at Cisco) <msengott@cisco.com>, Shlomi Eliyahu (seliyahu) <seliyahu@cisco.com>, Jason Zhang (jaszhang) <jaszhang@cisco.com>, Jen-Shue Shih (jeshih) <jeshih@cisco.com>Subject: Re: L3VPN service with XE with NSO 5.0 M4Hi Vaishali,There have been quite many changes in M4 w.r.t service creation. We have moved to the newer IETF model for L3VPN in M4 release.Please look at the release details uploaded and the wiki we have provided with the release.This release includes:XR 7.7.2 CLI NED supportXR 7.8.1 CLI NED support with SIT buildXR 7.9.1 CLI NED support with DT buildRemoval of L2 Flat modelsRemoval of L3 Flat modelsUpgrade L3NM models to RFC version5G Slicing SRTE supportUpdate L2 and L3 Route Policy guided by IETF standardHighlighted changes are pertaining to the L3 VPN service.P.S: The wiki details and the above release notes are provided in the release email as well.ThanksSahithiFrom: Vaishali Mithbaokar (vmithbao) <vmithbao@cisco.com>Date: Tuesday, December 6, 2022 at 8:54 AMTo: Yevgeny Chechelnitsky (ychechel) <ychechel@cisco.com>, Manivel Sengottuvel -X (msengott - HCL TECHNOLOGIES LIMITED at Cisco) <msengott@cisco.com>, Shlomi Eliyahu (seliyahu) <seliyahu@cisco.com>, Jason Zhang (jaszhang) <jaszhang@cisco.com>, Jen-Shue Shih (jeshih) <jeshih@cisco.com>Cc: Sahithi Patibandla (sahpatib) <sahpatib@cisco.com>Subject: Re: L3VPN service with XE with NSO 5.0 M4+Sahiti as wellTo see if any delta between M3 and M4 that might have caused issue w.r.t service creation with XE?Thx,VaishaliFrom: Vaishali Mithbaokar (vmithbao) <vmithbao@cisco.com>Date: Monday, December 5, 2022 at 11:52 PMTo: Yevgeny Chechelnitsky (ychechel) <ychechel@cisco.com>, Manivel Sengottuvel -X (msengott - HCL TECHNOLOGIES LIMITED at Cisco) <msengott@cisco.com>, Shlomi Eliyahu (seliyahu) <seliyahu@cisco.com>, Jason Zhang (jaszhang) <jaszhang@cisco.com>, Jen-Shue Shih (jeshih) <jeshih@cisco.com>Subject: Re: L3VPN service with XE with NSO 5.0 M4Keeping Jason and JenShue also in the loopHi Yevgeny, Manivel, Shlomi,Did any of you try XE service on M4 milestone build and did it work?Thx,VaishaliFrom: Vaishali Mithbaokar (vmithbao) <vmithbao@cisco.com>Date: Monday, December 5, 2022 at 10:53 PMTo: Yevgeny Chechelnitsky (ychechel) <ychechel@cisco.com>, Manivel Sengottuvel -X (msengott - HCL TECHNOLOGIES LIMITED at Cisco) <msengott@cisco.com>, Shlomi Eliyahu (seliyahu) <seliyahu@cisco.com>Subject: L3VPN service with XE with NSO 5.0 M4Hi All,I had used your collection for M3 and was able to create L3VPN on XE endpointBut now we switched to M4, and am running into following when using M4 postman collection<errors xmlns="urn:ietf:params:xml:ns:yang:ietf-restconf"> <error> <error-type>application</error-type> <error-tag>malformed-message</error-tag> <error-path xmlns:l3nm="urn:ietf:params:xml:ns:yang:ietf-l3vpn-ntw">/l3nm:l3vpn-ntw/l3nm:vpn-services</error-path> <error-message>/l3vpn-ntw/vpn-services/vpn-service{L3VPN_NM-NATIVE-IPV4-500}: STATUS_CODE: TSDN-IETF-L3NM-416REASON: Route-distinguisher is mandatory when configuring L3VPN service on a XE deviceCATEGORY: validationSEVERITY: ERRORContext [name = Missing route-distinguisher. RD is mandatory for XEstate = {'Endpoint': 'AA-ASR903-2', 'Keypath': '/l3nm:l3vpn-ntw/vpn-services/vpn-service{L3VPN_NM-NATIVE-IPV4-500}'}]</error-message> </error> | Hi Vaishali ,Please share your payload that you usedThanks,Linh<vpn-services><vpn-service><vpn-id>XE-L3VPN_NM-NATIVE-IPV4-500</vpn-id><vpn-instance-profiles><vpn-instance-profile><profile-id>L3VPN_NM-NATIVE-IPV4</profile-id><rd>0:50:50</rd><address-family><address-familyxmlns:vpn-common="urn:ietf:params:xml:ns:yang:ietf-vpn-common">ipv4</address-family><vpn-targets><vpn-target><id>51</id><route-targets><route-target>0:51:51</route-target></route-targets><route-target-type>both</route-target-type></vpn-target><vpn-target><id>52</id><route-targets><route-target>0:52:52</route-target></route-targets><route-target-type>import</route-target-type></vpn-target><vpn-target><id>53</id><route-targets><route-target>0:53:53</route-target></route-targets><route-target-type>export</route-target-type></vpn-target></vpn-targets></address-family></vpn-instance-profile></vpn-instance-profiles><vpn-nodes><vpn-node><vpn-node-id>AA-ASR903-3</vpn-node-id> <RD>0:50:50</RD><local-as>1</local-as><vpn-network-accesses><vpn-network-access><id>1</id><interface-id>Loopback50</interface-id><ip-connection><ipv4><local-address>100.100.100.3</local-address><prefix-length>24</prefix-length></ipv4></ip-connection><routing-protocols><routing-protocol><id>EBGP</id><type xmlns:vpn-common="urn:ietf:params:xml:ns:yang:ietf-vpn-common">bgp-routing</type><bgp><address-family>ipv4</address-family><redistribute-connected><address-family>ipv4</address-family></redistribute-connected><neighbor>100.100.100.2</neighbor><peer-as>50</peer-as><multihop>11</multihop></bgp></routing-protocol></routing-protocols></vpn-network-access></vpn-network-accesses><active-vpn-instance-profiles><vpn-instance-profile><profile-id>L3VPN_NM-NATIVE-IPV4</profile-id></vpn-instance-profile></active-vpn-instance-profiles></vpn-node><vpn-node><vpn-node-id>AA-ASR903-2</vpn-node-id> <RD>0:50:50</RD><local-as>1</local-as><vpn-network-accesses><vpn-network-access><id>1</id><interface-id>Loopback50</interface-id><ip-connection><ipv4><local-address>100.100.100.2</local-address><prefix-length>24</prefix-length></ipv4></ip-connection><routing-protocols><routing-protocol><id>EBGP</id><type xmlns:vpn-common="urn:ietf:params:xml:ns:yang:ietf-vpn-common">bgp-routing</type><bgp><address-family>ipv4</address-family><redistribute-connected><address-family>ipv4</address-family></redistribute-connected><neighbor>100.100.100.3</neighbor><peer-as>50</peer-as><multihop>11</multihop></bgp></routing-protocol></routing-protocols></vpn-network-access></vpn-network-accesses><active-vpn-instance-profiles><vpn-instance-profile><profile-id>L3VPN_NM-NATIVE-IPV4</profile-id></vpn-instance-profile></active-vpn-instance-profiles></vpn-node></vpn-nodes></vpn-service></vpn-services>Hi Vaishali,This is known issue and had a bug on this . It will be fix on coming release. Right now it has a work-arround by defining RD in active-vpn-instance-profiles under node level. Based on your payload, its format looks like this <vpn-node-id>AA-ASR903-3</vpn-node-id> <local-as>1</local-as> <active-vpn-instance-profiles> <vpn-instance-profile> <profile-id>L3VPN_NM-NATIVE-IPV4</profile-id> <rd>0:50:50</rd> </vpn-instance-profile> </active-vpn-instance-profiles>You should modify the same on the other end.Thanks,Linhthx much it worked!Thanks for let me know. I closed the ticket.The issue will fix in the coming release. Currently it works with workarround approach |
Services migration failed with CDB error from 5.7.5.1 m8 to 5.7.6 M2: We have Uni-d scale setup that is hvaing 5.7.5.1 M8 build.we have 10k services and having 60 devices.Tried upgrading to 4.1.0 - 5.7.6-M2. we have the steps captured during previous migration. ticket id:now, afetr upgrade, while strating the NCS, it throws error.root@arupras2-esxi-01-vm2:/var/opt/ncs/packages# date;sudo NCS_RELOAD_PACKAGES=force /etc/init.d/ncs restart --ignore-initial-validation;dateFri Oct 28 13:09:13 IDT 2022Stopping ncs: connection refused (stop)Starting ncs: CDB: Upgrade failed: Upgrade transaction failed to validate: /ncs:devices/device{A-PE1}/device-type/cli/ned-id is not configuredDaemon died status=13.Fri Oct 28 13:22:58 IDT 2022root@arupras2-esxi-01-vm2:/var/opt/ncs/packages# date;sudo NCS_RELOAD_PACKAGES=force /etc/init.d/ncs restart --ignore-initial-validation;dateFri Oct 28 13:28:17 IDT 2022Stopping ncs: connection refused (stop)Starting ncs: CDB: Upgrade failed: Upgrade transaction failed to validate: /ncs:devices/device{A-PE1}/device-type/cli/ned-id is not configuredDaemon died status=13.Fri Oct 28 13:41:31 IDT 2022root@arupras2-esxi-01-vm2:/var/opt/ncs/packages#can you please help in recovering the setup?Thanks,Arun.M.G | Hi Arun,Please share your setup details. I will take a look.Thanks,LinhHi Linh,CFS : 10.56.116.121RFS1: 10.56.116.122RFS2: 10.56.116.123nso/Public1234!Thanks,Arun.M.GI had a call with Arun and explain what is missing step that create this issue. The old NED should be retained during start up NSO since devices in CDB still prefer to these old NED. After bringing back old NED, ncs-5.7.3-cisco-iosxr-7.39.5.tar.gz, ncs start up fine. This is wiki link for the upgrade |
internal created services for slice are editable. And silently revert back the change.: Internal created services for Slices (eg. L3vpn service for an L3 slice) is supposed to be NOT editble.We are able to edit it from CNC UI or NSO UI. Commit is successful, but the change is reverted back with no warning.We should not allow edit for the internal created services. Build combo: CW 220, CDG 247, COE 236, CAT 231, NSO6.1+TSDN5.0.0 M5 | HI Crystal,This is intended behavior from NSO Platform. TSDN CFP would not have any control over this. CFP would not be able to change this behavior.Hope this helps.ThanksSahithiHi Sahithi,If we are not able to block edit operation. Can we show some warning message for reverting back the changes?Thanks.-CrystalHi Crystal, That would not be possible as well. This is NSO's platform behavior. Also, this is expected behavior.CFP would not have any control or warning when top level services modify the lower level services. This is how the NSO services behave.This is the same behavior when customer modifies the service created device config manually. NSO reverts the device config when the service is touched. CFP does not expect the customer to touch any NSO created services or device config. NSO assumes complete control over service config or device config it creates. ThanksSahithiThis is a known behavior from NSO Platform.Expected behavior from NSO Platform |
DLM service status not showing UP on 5.7.6-tsdn-5.0.0-M4: Hi,DLM service pack not showing UP on 5.7.6-tsdn-5.0.0-M4, Screenshot is attached. Please take a look at the issue.NSO server- 10.56.116.240 | Hi RageshWe don't own the DLM service pack. Please get in touch with the DLM team for this issue. You can reach out to Ravi kumar kolla from their team.Thanks,NikhilIssue was with the DLM service pack, advised user to reach out to DLM team.Thanks Nikhil for the info, will check with the DLM team and fix the issue. |
Device config mapping images not loading TSDN 4.0.0 M2 and M3: 1] Not loading the Images for Device Config Mapping for l2nm in TSDN 4.0.0 M3 2] Not loading the image for IOSXR device mapping in TSDN 4.0.0 M3 - SR policy.3] Not loading the image for IOSXR device mapping in TSDN 4.0.0 M2 - SR policy.Please check and upload the images. | Hi ArunWe have corrected the mapping diagrams in mentioned Wiki pages.Please check and and let us know whether the mapping diagrams are visible to you now.ThanksHi Nikhil,Thanks. Now we see the images not loading in the below page alone., Hi ArunWe have tried to open the page in few systems and the images are loading fine for all of us.For now, I have attached the images for your reference here.Let us know if anything else is required or we can close the ticket.Thanks.Closing the ticket as the required information has been provided. |
CFS - Netconf notification subscription Alarm with connection-failure: Setting up SLA. Doing "RFS OnBoarding Steps", on step3, after commit, the following Alarm showed:admin@ncs% *** ALARM connection-failure: Failed to authenticate towards device rfs-29: Unknown SSH host keyI thought maybe I should use remote-name as root in step1 because root is the user to access my RFS VM. So I did that and proceed with step 4.Can I proceed with the rest of the steps and ignore the ALARM? | For the section"RFS OnBoarding Steps" on step 6, there's a little note for the alarmYou can double check if the alarm is cleared using the following command:<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"><pre>admin@cfs-node% run show alarms alarm-list alarm rfs-node-1 is-cleared SPECIFIC IS DEVICE TYPE MANAGED OBJECT PROBLEM CLEARED ---------------------------------------------------------------------------------------rfs-node-1 connection-failure /devices/device[name='rfs-node-1'] true </pre></div></div>It should be cleared after running fetch-ssh-host-keys action assuming you have the correct authentication details.Let me know if that works for you.Thanks,RegiThanks Reginald,I did the ssh key fetch and check the alarm. The result showed alarm is cleared. Just wonder if we can make some updates on the LSA install guide wiki?1) move or copy the notes from Step 6 to Step 32) include the command for ssh key fetch and command to check alarm is cleared eg: request devices device <rfs-node-name> ssh fetch-host-keys show alarms alarm-list alarm <rfs-node-name> is-clearedOne more question, on step1 the set authgroups command, what is the remote-name should we use? Is it the user id for ssh to the rfs VM?Here is the command on wiki:"set devices authgroups group cnc-rfs-auth default-map remote-name admin remote-password"Similar question for Step 6, what is the username/pw should be use for "set cluster remote-node" command? I simply use the same on wiki and it failed to authenticate.admin@ncs% set cluster remote-node rfs-29 address 172.23.213.29 port 2022 authgroup cnc-rfs-auth username ciscoadmin@ncs% set cluster authgroup cnc-rfs-auth default-map remote-name cisco remote-password Cisco123#admin@ncs% set cluster device-notifications disabledadmin@ncs% set cluster commit-queue enabledadmin@ncs% commitCommit complete.admin@ncs% *** ALARM cluster-subscriber-failure: Failed to establish netconf notification subscription to node rfs-29, stream ncs-events (Failed to authenticate towards remote-node rfs-29: Unknown SSH host key). Commit queue items with remote nodes will not receive required event notifications.admin@ncs% request cluster remote-node rfs-29 ssh fetch-host-keys result updatedfingerprint { algorithm ssh-ed25519 value 62:e0:84:42:14:0d:32:9b:51:a3:e4:23:3c:29:3a:15}admin@ncs% run show cluster LAST RECEIVED NAME NAME STATUS EVENT NOTIFICATIONS --------------------------------------------rfs-29 REMOTE LOCAL REMOTE NODE ADDRESS PORT CHANNELS USER USER STATUS TRACE ------------------------------------------------------------------------rfs-29 172.23.213.29 2022 - cisco cisco down disabled admin@ncs% *** ALARM cluster-subscriber-failure: Failed to establish netconf notification subscription to node rfs-29, stream ncs-events (Failed to authenticate towards remote-node rfs-29: Bad password for local user cisco). Commit queue items with remote nodes will not receive required event notifications.Thanks for your input. I'll go ahead and clarify the docs based on your inputs.As for your second post, the username/passwd should be the credentials you use to access the RFS device.Thanks Reginald for the info. I proceed further. On "Configure Bootstrap Data" got errors for 2 load merge commands:admin@ncs% load merge rfs-netconf-notif-sub.xmlAborted: internal erroradmin@ncs% load merge rfs-node-onboarding.xmlError: on line 5: invalid value for: address in /ncs:devices/ncs:device/ncs:address: "${RFS_ADDRESS}" is not a valid value.I have removed these two payloads from the 4.0 M2 wiki as they have been previously configured directly through CLI during onboard of RFS. (updated:)<h2></h2>Thanks Reginald for the clarification and wiki update. Will continue for the rest steps. |
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. |
config issues in Y1731 in TSDN 3.0.0 M4: NSO has installed with NCS 5.5.2.7 TSDN 3.0.0 M4.Attached payload for configuring y1731 for L2vpn EPVN service and L2vpn p2p service.We have the below listed issues in the configuration of y1731 through CFP. Raised JIRA ticket 1] By Default, It is always configuring SMAN with id icc-based in Ethernet CFM configurations. This should be configurable parameter where this SMAN support varies with different device types.For eg., I have created service between ASR9k and NCS55XX ., After the configuration., I face issues in bringing up the ethernet CFM.The config that got pushed:!ethernet cfm domain EVC level 4 id null service L2NM-L2NM-EVPN-VPWS-SRTE-104 xconnect group L2NM-EVPN-VPWS-SRTE-104 p2p L2NM-EVPN-VPWS-SRTE-104 id icc-based p2p 1 continuity-check interval 1s mep crosscheck mep-id 2!Error in device:RP/0/RSP0/CPU0:ASR9006-SDN-91#show ethernet cfm local meps Wed Aug 4 13:03:33.121 UTCDefects (from at least one peer MEP): A - AIS received I - Wrong interval R - Remote Defect received V - Wrong level L - Loop (our MAC received) T - Timed out C - Config (our ID received) M - Missing (cross-check) X - Cross-connect (wrong MAID) U - Unexpected (cross-check) P - Peer port downDomain EVC (level 4), Service L2NM-L2NM-EVPN-VPWS-SRTE-104 ID Interface (State) Dir MEPs/Err RD Defects AIS----- ------------------------ — -------- – ------- — 1 Te0/0/0/15.104 (Up) Up 1/1 Y RX RP/0/RSP0/CPU0:ASR9006-SDN-91#RP/0/RSP0/CPU0:ASR9006-SDN-91#show ethernet cfm peer meps Wed Aug 4 13:04:41.942 UTCFlags:> - Ok I - Wrong intervalR - Remote Defect received V - Wrong levelL - Loop (our MAC received) T - Timed outC - Config (our ID received) M - Missing (cross-check)X - Cross-connect (wrong MAID) U - Unexpected (cross-check)<ul>- Multiple errors received S - Standby</ul>Domain EVC (level 4), Service L2NM-L2NM-EVPN-VPWS-SRTE-104Up MEP on TenGigE0/0/0/15.104 MEP-ID 1================================================================================St ID MAC Address Port Up/Downtime CcmRcvd SeqErr RDI Error– ----- -------------- ------- ----------- --------- ------ ----- -----X 2 0032.17ea.a000 Up 00:04:06 246 0 246 246RP/0/RSP0/CPU0:ASR9006-SDN-91#This got fixed after changing the SMAN id in the device manually as below.,!ethernet cfm domain EVC level 4 id null service L2NM-L2NM-EVPN-VPWS-SRTE-104 xconnect group L2NM-EVPN-VPWS-SRTE-104 p2p L2NM-EVPN-VPWS-SRTE-104 id number 100 continuity-check interval 1s mep crosscheck mep-id 2!The are the available attributes for SMAN id under ethernet cfm. Attached snapshot.2] As per the current CFP implementation, SMAN id is getting configured with mep id value. Mep id can be same for the device. But SMAN ID value should be different for each service. Since it is taking the value of mep-id itself for SMAN id also, it is not possible configure same mepid now. We are forced to change the mep-id for every service.3] It is Not able to unconfigure the y1731 configs that got pushed. Please let me know if there is any possibilities to unconfigure only the y1731 config for the particular service .We should have possibility to unconfigure the Y1731 profile association to the services. The below marked config should be configurable and unconfigurable.!interface TenGigE0/0/0/15.104 l2transport description T-SDN Interface encapsulation dot1q 104 no ethernet cfm no mep domain EVC service L2NM-L2NM-EVPN-VPWS-SRTE-104 mep-id 1 no sla operation profile loss target mep-id 2 no sla operation profile delay target mep-id 2 ! | For item 1) and 2): the configuration was push based on configuration governance in git. Please submit your request configuration to configuration governance team for approval.Item3): I applied your payload and able to delete ethernet-service-oam from the service. I don't see any screenshot attached for this issue. Please follow this guide to report the issue.Note: For deleting ethernet-service-oam, it needs to delete ethernet-service-oam from both sides (local and remote) at the same time.Attached email thread Postman collection for delete oam TSN 3.0- Folder- L2VPN-NM-OAM- Delete Y1731 configuration is changed in M6 to address this issue.Wiki and Recording available here - |
Not able to cleanup the device as it is referred to a internal service: NSO Access info: 172.23.92.238 [ admin/Cwork123! ]admin@ncs> show zombies % No entries found.admin@ncs> confEntering configuration mode privateadmin@ncs% delete devices device R1admin@ncs% commitAborted: illegal reference 'core-fp-delete-shutdown-service R1 GigabitEthernet 0/0/0/3 device'admin@ncs% run show all devices detailscommit-queue { completed { queue-item 1648635163377 { when 2022-03-30T10:12:55.667022+00:00; status failed; devices [ R1 R10 ]; completed [ R10 ]; failed R1 { reason "External error in the NED implementation for device R1: Mon Apr 4 07:29:39.982 UTC% Failed to commit one or more configuration items during a pseudo-atomic operation. All changes made have been reverted. !! SEMANTIC ERRORS: This configuration was rejected by !! the system due to semantic errors. The individual !! errors with each failed configuration command can be !! found below.interface GigabitEthernet0/0/0/3 l2transport!!% Subinterface or Layer 2 configuration conflicts with existing configuration, or configuration in this commit: Cannot configure an interface as L2 when L3 configuration exists !!end"; } completed-services [ /cisco-flat-L2vpn-fp-internal-remote-site:flat-L2vpn-internal-remote-site-service /cisco-flat-L2vpn-fp:flat-L2vpn /core-fp-delete-tag-service:core-fp-delete-shutdown-service /l2vpn-ntw:l2vpn-ntw/l2vpn-ntw:vpn-services/l2vpn-ntw:vpn-service ]; failed-services [ /cisco-flat-L2vpn-fp-internal-local-site:flat-L2vpn-internal-local-site-service /core-fp-delete-tag-service:core-fp-delete-shutdown-service ]; } queue-item 1648656408733 { when 2022-03-30T16:07:00.793551+00:00; status completed; devices [ R1 R10 ]; completed [ R1 R10 ]; completed-services [ /cisco-flat-L2vpn-fp-internal-local-site:flat-L2vpn-internal-local-site-service[cisco-flat-L2vpn-fp-internal-local-site:name='L2NM-L2vpn_tldp_R1_R10_dot1q-internal'][cisco-flat-L2vpn-fp-internal-local-site:pe='R1'] /cisco-flat-L2vpn-fp-internal-remote-site:flat-L2vpn-internal-remote-site-service[cisco-flat-L2vpn-fp-internal-remote-site:name='L2NM-L2vpn_tldp_R1_R10_dot1q-internal'][cisco-flat-L2vpn-fp-internal-remote-site:pe='R10'] /cisco-flat-L2vpn-fp:flat-L2vpn[cisco-flat-L2vpn-fp:name='L2NM-L2vpn_tldp_R1_R10_dot1q-internal'] /core-fp-delete-tag-service:core-fp-delete-shutdown-service[core-fp-delete-tag-service:device='R1'][core-fp-delete-tag-service:if-type='GigabitEthernet'][core-fp-delete-tag-service:if-id='0/0/0/3'] /core-fp-delete-tag-service:core-fp-delete-shutdown-service[core-fp-delete-tag-service:device='R10'][core-fp-delete-tag-service:if-type='GigabitEthernet'][core-fp-delete-tag-service:if-id='0/0/0/3'] /l2vpn-ntw:l2vpn-ntw/l2vpn-ntw:vpn-services/l2vpn-ntw:vpn-service[l2vpn-ntw:vpn-id='L2vpn_tldp_R1_R10_dot1q'] ]; } }}admin@ncs% | Hello Shanmugavel,I would need a bit more context on this issue to RCA.But from your audit logs, I can assume that this was part of an automation run as I see the following unsupported operations:<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"><pre class="code-java"><INFO> 30-Mar-2022::18:10:31.649 nso1 ncs[32303]: audit user: admin/561699 CLI <INFO> 30-Mar-2022::18:10:31.657 nso1 ncs[32303]: audit user: admin/561699 CLI done<INFO> 30-Mar-2022::18:10:31.973 nso1 ncs[32303]: audit user: admin/561699 CLI <INFO> 30-Mar-2022::18:10:31.974 nso1 ncs[32303]: audit user: admin/561699 CLI done<INFO> 30-Mar-2022::18:10:32.288 nso1 ncs[32303]: audit user: admin/561699 CLI <INFO> 30-Mar-2022::18:10:32.289 nso1 ncs[32303]: audit user: admin/561699 CLI done<INFO> 30-Mar-2022::18:10:32.573 nso1 ncs[32303]: audit user: admin/561699 CLI <INFO> 30-Mar-2022::18:10:32.574 nso1 ncs[32303]: audit user: admin/561699 CLI done<INFO> 30-Mar-2022::18:10:32.882 nso1 ncs[32303]: audit user: admin/561699 CLI <INFO> 30-Mar-2022::18:10:32.882 nso1 ncs[32303]: audit user: admin/561699 CLI done<INFO> 30-Mar-2022::18:10:33.176 nso1 ncs[32303]: audit user: admin/561699 CLI <INFO> 30-Mar-2022::18:10:33.177 nso1 ncs[32303]: audit user: admin/561699 CLI done<INFO> 30-Mar-2022::18:10:33.509 nso1 ncs[32303]: audit user: admin/561699 CLI <INFO> 30-Mar-2022::18:10:33.510 nso1 ncs[32303]: audit user: admin/561699 CLI done<INFO> 30-Mar-2022::18:10:33.793 nso1 ncs[32303]: audit user: admin/561699 CLI <INFO> 30-Mar-2022::18:10:33.794 nso1 ncs[32303]: audit user: admin/561699 CLI done<INFO> 30-Mar-2022::18:10:34.078 nso1 ncs[32303]: audit user: admin/561699 CLI <INFO> 30-Mar-2022::18:10:34.078 nso1 ncs[32303]: audit user: admin/561699 CLI aborted<INFO> 30-Mar-2022::18:10:34.090 nso1 ncs[32303]: audit user: admin/561699 CLI <INFO> 30-Mar-2022::18:10:34.096 nso1 ncs[32303]: audit user: admin/561699 CLI done</pre></div></div>Again, I would like to strongly emphasize, deleting L2NM and Flat L2VPN in a single transaction is .This is likely why you are experiencing remaining artifacts from core-fp-delete-tag-service.Please reopen another ticket if you are able to reproduce this without executing unsupported operations. We will not spend more time debugging undefined behavior due to unsupported operations. This ticket will be junked unless proven that error is not caused by the conflicting delete.For more context on this, please refer to the following JSD ticket : Thanks,Isaac KimUnsupported operation : delete IETF L2NM and Flat L2 in single transaction.ok, Agree it is not supported operation, we will update the steps in automation but we are looking for the recovery steps here nowHello Shanmugavel,core-fp-delete-tag-service is a fully hidden servicepoint. It cannot be deleted unless with ncs_load commands which must be tailored specifically for your setup.We will not spend more time on these unsupported issues. I am very sorry. Our developer time is very valuable and we are rushing to meet our own deadlines. Please reinstall and ensure you are following our guidelines.Thanks,Isaac Kimthis will be the response "we will not spend time in giving the solution or workaround" when any customer get into issue like this? Take this as a negative case and give us a solution Hello Shanmugavel,We have given a fair warning here : Just like this ticket, we will not resolve your setup because you have executed unsupported operations as part of automation, even when we have given a warning as referenced in above ticket.If you feel like this response is unjustified, please escalate the issue with your manager.Thanks,Isaac Kim |
rename_list_entry issue for multi-key config: A JSON RPC rename_list_entry method is not working for multi-key scenario. Below is example from L2VPN service { "jsonrpc": "2.0", "id": 1, "method": "rename_list_entry", "params": { "th" : 1, "from_path" : "/l2vpn-ntw:l2vpn-ntw/vpn-services/vpn-service{KC-L2vpn}/vpn-nodes/vpn-node{xrv9k-12}/signaling-option/ldp-or-l2tp/pw-peer-list{192.168.0.14 150}", "to_keys" : }} | Hello Please let us know the Exact Error Message being seen.The following is the error response{ "jsonrpc": "2.0", "error": { "type": "rpc.method.invalid_params_type", "code": -32000, "message": "Invalid parameters' type", "data": { "param": "to_keys" }, "internal": "webui_util484" }, "id": 275}Thank you.Please let us know the NSO version being used.For example, I have used NSO version 6.1.3.1 and 6.1.4 and seen the error look as below:cisco@Janaki-nso-30:~/tsdn_jaduggir/T-SDN$ curl -b cookie -X POST -H 'Content-Type: application/json' -d ' {-H 'Content-Type: application/json' -d ' {"jsonrpc":"2.0","id":1,"method":"rename_list_entry","params":{"th": 1,"from_path": "/l2vpn-ntw/vpn-services/vpn-service{l2nm-p2p}/vpn-nodes/vpn-node{PIOSXR-0}/signaling-option/ldp-or-l2tp/pw-peer-list{198.18.1.5 1001}","to_keys": } }'{"jsonrpc":"2.0","error":{"type":"data.not_writable","code":-32000,"message":"Data not writable"},"id":1}Created Internal ticket on NSO to address these error messages for Multi-Key List Key Modification - RT#50828Will update this ticket when we receive an update from NSO platform.Thank you.Verified on NSO 6.1.4 rename_list_entry works well. Commands below:cisco@Janaki-nso-30:~/tsdn_jaduggir/T-SDN$ curl -b cookie -X POST -H 'Content-Type: application/json' -d ' {"jsonrpc":"2.0","id":1,"method":"rename_list_entry","params":{"th": 1,"from_path": "/l2vpn-ntw/vpn-services/vpn-service{l2nm-p2p}/vpn-nodes/vpn-node{PIOSXR-0}/signaling-option/ldp-or-l2tp/pw-peer-list{198.18.1.5 1001}","to_keys": } }'{"jsonrpc":"2.0","result":{},"id":1}cisco@Janaki-nso-30:~/tsdn_jaduggir/T-SDN$cisco@Janaki-nso-30:~/tsdn_jaduggir/T-SDN$ curl -b cookie -X POST -H 'Content-Type: application/json' -d ' { "jsonrpc":"2.0","id":1,"method":"validate_commit","params":{"th": 1}}'{"jsonrpc":"2.0","result":{},"id":1}cisco@Janaki-nso-30:~/tsdn_jaduggir/T-SDN$cisco@Janaki-nso-30:~/tsdn_jaduggir/T-SDN$cisco@Janaki-nso-30:~/tsdn_jaduggir/T-SDN$ curl -b cookie -X POST -H 'Content-Type: application/json' -d ' { "jsonrpc":"2.0","id":1,"method":"commit","params":{"th": 1}}'{"jsonrpc":"2.0","result":{"commit_queue":{"id":1697703114206,"status":"async"}},"id":1}cisco@Janaki-nso-30:~/tsdn_jaduggir/T-SDN$ ncs_cli -u adminUser admin last logged in 2023-10-19T08:11:56.180103+00:00, to Janaki-nso-30, from 127.0.0.1 using webui-httpadmin connected from 10.21.180.254 using ssh on Janaki-nso-30admin@ncs> configureEntering configuration mode privateadmin@ncs% show l2vpn-ntw | display keypath/l2vpn-ntw/vpn-services/vpn-service{l2nm-p2p}/vpn-type vpws/l2vpn-ntw/vpn-services/vpn-service{l2nm-p2p}/vpn-nodes/vpn-node{PIOSXR-0}/signaling-option/ldp-or-l2tp/pw-peer-list{192.168.0.15 151}/cisco-l2vpn-ntw:mpls-label 101Verified on NSO 6.1.3.1 and the method still works correctly. See below for complete commands (and screenshot attached)cisco@janaki-41:~/tsdn_jaduggir/T-SDN$ curl -i -c cookie -X POST -H 'Content-Type: application/json' -d '{"jsonrpc":"2.0","id":1,"method":"login","params":{ "user":"admin", "passwd":"admin"}}'HTTP/1.1 200 OKDate: Fri, 20 Oct 2023 15:25:15 GMTExpires: Thu, 01 Jan 1970 00:00:00 GMTCache-Control: private, no-cache, no-store, must-revalidate, max-age=0, proxy-revalidate, s-maxage=0Content-Length: 36Content-Type: application/json; charset=UTF-8Set-Cookie: sessionid_8080=sesssE+QqZAllnXpqgK5o9lxXw==; path=/; HttpOnlyVary: Accept-EncodingContent-Security-Policy: default-src 'self'; block-all-mixed-content; base-uri 'self'; frame-ancestors 'none';Strict-Transport-Security: max-age=15552000; includeSubDomainsX-Content-Type-Options: nosniffX-Frame-Options: DENYX-XSS-Protection: 1; mode=blockcisco@janaki-41:~/tsdn_jaduggir/T-SDN$ curl -b cookie -X POST -H 'Content-Type: application/json' -d 'Content-Type: application/json' -d '{"jsonrpc":"2.0","id":1,"method":"new_trans","params":{ "db": "running", "mode": "read_write"}}'cisco@janaki-41:~/tsdn_jaduggir/T-SDN$ curl -b cookie -X POST -H 'Content-Type: application/json' -d ' {-H 'Content-Type: application/json' -d ' {"jsonrpc":"2.0","id":1,"method":"rename_list_entry","params":{"th": 1,"from_path": "/l2vpn-ntw/vpn-services/vpn-service{l2nm-p2p}/vpn-nodes/vpn-node{PIOSXR-0}/signaling-option/ldp-or-l2tp/pw-peer-list{198.18.1.5 1001}","to_keys": } }'cisco@janaki-41:~/tsdn_jaduggir/T-SDN$ curl -b cookie -X POST -H 'Content-Type: application/json' -d ' {ntent-Type: application/json' -d ' { "jsonrpc":"2.0","id":1,"method":"validate_commit","params":{"th": 1}}'cisco@janaki-41:~/tsdn_jaduggir/T-SDN$ curl -b cookie -X POST -H 'Content-Type: application/json' -d ' { "jsonrpc":"2.0","id":1,"method":"commit","params":{"th": 1}}'{"jsonrpc":"2.0","result":{"commit_queue":{"id":1697815563132,"status":"async"}},"id":1}cisco@janaki-41:~/tsdn_jaduggir/T-SDN$cisco@janaki-41:~/tsdn_jaduggir/T-SDN$ ncs --version6.1.3.1Please confirm if ticket maybe closed.NSO 6.1.3.1 and NSO 6.1.4 both work correctly for rename_list_entry. Customer confirmed that ticket can be closed. |
RON build for CNC 6.0, NSO 6.1.4, TSDN 6.1.4 Drop 8 or 9 : Hi team,Kindly share the compatible RON image that works along with CNC 6.0, NSO 6.1.4, TSDN 6.1.4 Drop 8 or 9 .As per below link , the images arenso-6.1.linux.x86_64.installer.bin + nso-6.1-ron-2.1.0.signed.bin.Kindly suggest the RON build that can be used along with CNC 6.0, NSO 6.1.4, TSDN 6.1.4 Drop 8 or 9 . | Hi Ajitha.You can find RON 2.1.1 patch build here: Here's a summary of steps to install RON 2.1.1 on a setup with CNC 6.0 DTHO 9:1. make sure ncs-xxx-cisco-iosxr-749.tar.gz available2.install the below packages ncs-xxx-cisco-ron-core-fp-common-xxx.tar.gz ncs-xxx-cisco-optical-cfp-xxx.tar.gz ncs-xxx-cisco-ron-cfp-xxx.tar.gz ncs-xxx-cisco-zr-cfp-xxx.tar.gz ncs-xxx-onf-tapi-nc-xxx.tar.gz3.restart ncs with package reload4.bootstrapping RON per installation wiki5.onboard RON headend devices using CLI NED 7.49Please refer to the installation section of RON 2.1.1 for complete detailed stepsLet me know if you have any questions.Thanks,AbeHi Ajitha.You can find RON 2.1.1 patch build here:Here's a summary of steps to install RON 2.1.1 on a setup with CNC 6.0 DTHO 9:1. make sure ncs-xxx-cisco-iosxr-749.tar.gz available2.install the below packages ncs-xxx-cisco-ron-core-fp-common-xxx.tar.gz ncs-xxx-cisco-optical-cfp-xxx.tar.gz ncs-xxx-cisco-ron-cfp-xxx.tar.gz ncs-xxx-cisco-zr-cfp-xxx.tar.gz ncs-xxx-onf-tapi-nc-xxx.tar.gz3.restart ncs with package reload4.bootstrapping RON per installation wiki5.onboard RON headend devices using CLI NED 7.49Please refer to the installation section of RON 2.1.1 for complete detailed stepsLet me know if you have any questions.Thanks,AbeReached out to Ajitha and said to go ahead and close the ticket.RON 2.1.1 patch build ca be found here:Here's a quick summary of steps to install RON 2.1.1 on a setup with CNC 6.0 DTHO 9:1. make sure ncs-xxx-cisco-iosxr-749.tar.gz available2.install the below packages ncs-xxx-cisco-ron-core-fp-common-xxx.tar.gz ncs-xxx-cisco-optical-cfp-xxx.tar.gz ncs-xxx-cisco-ron-cfp-xxx.tar.gz ncs-xxx-cisco-zr-cfp-xxx.tar.gz ncs-xxx-onf-tapi-nc-xxx.tar.gz3.restart ncs with package reload4.bootstrapping RON per installation wiki5.onboard RON headend devices using CLI NED 7.49 |
Does not have access to download custom-template.tar.gz: Hi Team,the custom-template.tar.gz is does not able to be downloaded as the CEC credentials are not accepted.Please help to check. | Hello, the wiki page has been fixed. Please try again and confirm. Thank you.Hi,The issue has not been fixed.We are getting the following error upon clicking the hyper link.{ "errors" : [ { "status" : 404, "message" : "File not found." } ]}Thanks,DineshClosing ticket as customer has confirmed that download is successful.Wiki page link was fixed and download is successful. |
Provisioning Menu is not loading fully on regression setup: After installing 375 build on regression setup, the Provsioning Menu is not loading. We tried to re-install and restart NSO, but the issue still exists. Both the cert file and the auth key looks fine on both CW and NSO.Installed 387 and still seeing the same issue. Tried changing NSO to HTTP only, but it does not help. Restarted NSO, still the issue exists. This is blocking regression runs. cw-na-dg-6.0.0-541cw-na-cat-6.0.0-240-developcw-na-coe-6.0.0-264-developcw-na-platform-6.0.0-387-developJWT Logs throws errorroot@ubuntu2004:/var/log/ncs# tail -f ncs-python-cisco-cfp-jwt-auth.log2023-09-15 18:50:15.270 authenticate:261 INFO: Exception jwt-auth: HTTPSConnectionPool(host='10.23.213.27', port=30603): Max retries exceeded with url: /crosswork/sso/v2/userInfo (Caused by ProxyError('Cannot connect to proxy.', OSError('Tunnel connection failed: 504 Gateway Timeout')))2023-09-15 18:50:16.780 authenticate:261 INFO: Exception jwt-auth: HTTPSConnectionPool(host='10.23.213.27', port=30603): Max retries exceeded with url: /crosswork/sso/v2/userInfo (Caused by ProxyError('Cannot connect to proxy.', OSError('Tunnel connection failed: 504 Gateway Timeout')))2023-09-15 18:51:33.279 authenticate:261 INFO: Exception jwt-auth: HTTPSConnectionPool(host='10.23.213.27', port=30603): Max retries exceeded with url: /crosswork/sso/v2/userInfo (Caused by ProxyError('Cannot connect to proxy.', OSError('Tunnel connection failed: 504 Gateway Timeout')))2023-09-15 18:57:40.222 authenticate:261 INFO: Exception jwt-auth: HTTPSConnectionPool(host='10.23.213.27', port=30603): Max retries exceeded with url: /crosswork/sso/v2/userInfo (Caused by ProxyError('Cannot connect to proxy.', OSError('Tunnel connection failed: 504 Gateway Timeout')))NSO ? 10.195.165.178 (admin/Ovatest123@) | Hi Swetha, Can you please provide the setup on which you are facing this issue?NSO - 10.195.165.178 (admin/Ovatest123@)Can I get the CNC credentials too?10.23.213.27 - admin/Ovatest123@Adding CNC host IP to no-proxy on NSO server seems to help. Will wait for Shweta to update after nightly run.Added CNC host to no_proxy fixed the issue.Runs are completed. Provisioning issue was resolved. |
jwt token issue in upgraded setup: We migrated from NSO TSDN 5.0 to TSDN 6.0 LSA setup. we moved to jwt authentication for CW. specified ip, certificate file, and port no. However JWT authentication is not successful. We use public ip for NSO and private IP for CW. We have reachability from CW to NSO. Is this enough for the authentication? Do we need connectivity from NSO to CW ?NSO : 192.168.103.235 - admin/Ovatest123@CW: ssh -L 30166:192.168.5.48:30603 root@192.168.103.138 Creds for 192.168.103.138 - root/Cwork123!Creds for CW : admin/Ovatest123@i get authentication failed message. | Hi Ramakrishnan,CW should be reachable from NSO as well.Currently we are getting "Failed to establish a new connection: Connection timed out'))".Thanks And Regards,Nishad Subair.After establishing reachability, NSO JWT token issue is resolved. Thank you.Thank you for the update. As the issue is resolved , closing this ticket. |
Extra Resource Pool seen in M5, ip-lsa-pool & sman-id-pool: Noticed the following 2 Resource Pools were added as default in TSDN 4.0.0 M5ip-lsa-pool sman-id-poolAre there expected? | Hi Crystal,It is expected one pool is for XR Y1731, and other (ip sla) for XE.Thanks,LinhHi Crystal, I will close this ticket in couple days if there is no update from your side.Thanks,Linh |
interfaces not listed: While provisioning L2VPN service in CNC, all interfaces are not listed in the CNC. This list should be coming from NSO, CFP. Some gig interfaces in shutdown mode were not listed. Those interfaces were brought up and NSO sync was performed. Why few interfaces are not listed? | CNC : 10.195.165.208 - admin/Ovatest123@NSO : 10.195.165.224 - admin/Ovatest123@Device : 192.168.5.49You can ignore this JSDSure. Will be closing this.ThanksSahithi |
L2 Slice ID Charcter Length Limitation: Hi,I'm trying to create a L2 slice which has service-id of max 19 characters. Its throwing error like below,"error-message": "/l2vpn-ntw/vpn-services/vpn-service{NSS-UIT-Slice-L2-Chr-19-internal}: STATUS_CODE: TSDN-IETF-L2NM-407REASON: Missing inputCATEGORY: validationSEVERITY: ERRORContext "But, when try to create L3 of 19 chars length it get created successfully.Attaching the payloads of L3 and L2 both.Thanks,Magesh | Hi,Setup:User: nsoPwd: Vtsisco@123!Hi MagneshThere is a discrepancy between external service id and internal brigde-group name length. Dev is on going to fix this issue. I will close the ticket when the codes is merged in.Thanks,LinhHello, this issue has been fixed and merged. Fix will be available in the next drop. Issue has been fixed by changing the range of NSS service-id group from 19 to 17 to match L2 bridge-group length.CDETS tracking this issue is : CSCwh32635 |
Links for all dependent packages so that we can consume in tm-tc packages.: Request from TM-TC group to provide all links. | Response Captured:Hi Moksha,Custom-template-utils and Core-fp-common are cfp common packages.As mentioned in earlier emails, they are hosted in different repo.Re-adding the links from prior emails sent:CFP common packages: (Different from nso-snapshot)Official NED packages:Engineering NED packages:Please save these links for future purposes.If it is hard to download from above links, you can update using below alternate approach:We document every common package addition/update in the CHANGES file.CHANGES file is included in the build.Please look at the CHANGES file and consume the packages from build as an alternative.Please let me know if there any other issue.ThanksSahithi Email thread and the resolution attached |
Provision services failed with error: External error in the NED implementation for device XYZ: config exclusive: config exclusive: When create a NSS or L3vpn-ntw, failed with External error in the NED implementation for device XYZ config exclusive: config exclusive.The same payloads were used with M7 without any issue. On this test bed we have 3 devices with the same IOSXR version 7.11.1.27I, device TB2-PE-A and TB2-PE-C failed. Abe Tan helped debugging the issue where we check log files and also tried to run the same payload from cli with "commit dry-run" without any issue - only when "commit" the error msg displayed.admin@ncs% commit Aborted: External error in the NED implementation for device TB2-PE-C: config exclusive: config exclusivdmin@ncs%A device trace was turn on to capture log, ned-cisco-iosxr-cli-7.49-TB2-PE-C.trace, please see attached file.Please check if the issue could come from day 0 configuration or anything else that could be missing from the devices.Thanks and regards. | Hello NSO team, please close the ticket - as the issue has been resolved. The device had an inconsistency alarm set thus it prevented any configuration. Thanks and regards.Spoke to Quy and found out the device had an inconsistency alarm set thus it prevented any configuration. Closing the ticket as complete |
Configure SRv6 SR-TE Policies failed with CLI 7.5.2: Hi Team,Got a report below, could you please confirm - does M4 support SRv6 sr-te policy with CLI - 7.5.2?Thanks and regards,-QuyL2VPN-SRV6 ; L3VPN-SRV6 is created on PE-A/B with 7.5.2 image, but SRV6 is not created ; throwing below error message.Thu Mar 24 19:39:14 IST 2022:DEBUG: << " "error-message": "/cisco-sr-te-cfp-internal:sr-te/cisco-sr-te-cfp-sr-policies-internal:policies/policy{srv6_vpn_policy-5001 TB3-PE-A}: Python cb_validate error. STATUS_CODE: TSDN-SR-411REASON: SRv6 is not supported with current device or NEDCATEGORY: userSEVERITY: ERRORContext [name = SRv6 validation, message = Either device not synced or NED/device image version is not supported for SRv6 state = {'Service': 'srv6_vpn_policy-5001', 'Device': 'TB3-PE-A', 'NED-ID': 'cisco-iosxr-cli-7.38:cisco-iosxr-cli-7.38', 'Version': '7.5.2.19I'}]""Server info:172.24.97.147 nso/Vtsisco@123! | Hi Quy,SRv6 with Sr-ODN and SR-Policy is ONLY support for XR 7.3.2 right nowThanks,Linhhi Linh,Thank you for your update.Could you please confirm that XR 7.3.2 is the only version that supports SRv6 in NSO 4.0? From the under item 7, it stated:"The SRv6 feature introduced in this release is only supported on IOSXR 7.3.2 device. ReferDevice Matrix Support - CNC-3.0 - TSDN and RON. "where the link is still referring to CNC-3.0 . Wondering if all of the matrix are also applied for 4.0 ?Thanks and regards,-QuyHi Quy,This feature is carried over from 3.0 and there is no changed in XR version support - ONLY XR 7.3.2Thanks,Linh |
CFP Installation and Uninstallation steps differs: Hi,in NSO TSDN CFP 4.0.0 M3 and M4 installation link has steps to copy the every package to /opt/ncs/package and creating sudo ln -s link to /var/opt/ncs/packages.But, the unsintallation has steps of "sudo rm -rf /var/opt/ncs/packages/*.tar.gz" .this confuses a new user having different steps in different places. we should have respective steps for install and uninstall in the same way.please clarify, if we can have have m3 and m4 installation as mentioned in M2 .$ sudo /etc/init.d/ncs stop$ sudo cp core-fp-packages/*.tar.gz /var/opt/ncs/packages$ sudo cp example-packages/*.tar.gz /var/opt/ncs/packages$ sudo NCS_RELOAD_PACKAGES=force /etc/init.d/ncs restartplease correct the wiki and clarification needed.Thanks,Arun.M.G | Hi ArunThe steps mentioned in M4 ad M3 are performing the same functionality as the one mentioned in M2. You can use either of them to copy the packages.M4 and M3 steps are just a detailed version of the existing one and they allow you to delete the packages from your runtime directory(/var/opt/ncs/packages) but still keep the packages in your installation directory(/opt/ncs/packages/).Let us know if anything else is required or we can close the ticket.Thanks.Hi Nikhil ,Thanks for the clarification.from M3 /M4 system installation Guide and M3/M4 System uninstallation Guide, Installation guide talks about creating symbolic links , uninstallation talks about removing the packages from /var/opt/ncs/packages.does installing creating symbolic links and during uninstallation removing packages from /var/opt/ncs/packages works without unlink ?please clarifyThanks,Arun.M.GHi ArunThe below uninstallation step is removing the links created during the installation only. It's not deleting the packages but removing the links(unlinking) created in the runtime directory(/var/opt/ncs/packages)<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"><pre class="code-java">$ sudo rm -rf //opt/ncs/packages/*.tar.gz</pre></div></div>Let me know if anything else is required or I can close the ticket.Thanks, NikhilClosing the ticket as the required information has been provided. |
hcc package issue: Follow the steps to setup NSO HA for 5.5.2.3 wit the following wiki link:Issue1, at step 8: Can not find HCC package for 5.5.2 under: Issue2: I got the HCC package file (ncs-5.5.2-tailf-hcc-project-5.0.0.signed.bin) from other VM. It failed with "python not found" when run the following command. But python 3.8 is installed on the system.root@nso-169:~/HCC# sudo sh ncs-5.5.2-tailf-hcc-project-5.0.0.signed.binUnpacking...Verifying signature...ncs-5.5.2-tailf-hcc-project-5.0.0.signed.bin: 81: python: not foundncs-5.5.2-tailf-hcc-project-5.0.0.signed.bin: 90: python: not foundERRORERROR Failed to perform signature verification.ERROR Verification requires Python version 2.7.4 or later.ERRORroot@nso-169:~/HCC# python3 -VPython 3.8.10 | Hi Crystal,It seems python (not python3) is not setting on the setup.Does your system has python command? If not, please create a soft link python -> python3.The issue should be resolve after this!Thanks,LinhMissing python server setting |
info is not populating at show devices lsa dispatch-map device: I have a LSA setup, after adding my device in RFS, i can see the dispatch map updated. but this tree doesn't have required information "show devices lsa dispatch-map device". The actual problem i have seen is in my yang file, i set node information as path "/core-fp-common:dispatch-map/core-fp-common:device";even though dispatch map on cli shows it has device, while creating my plan, it errors with illegal reference error which says device doesn't exist. | Hi Raja,Please share your setup info. I just want to see how do you set it up.Thanks,LinhRaja responded via email mentioning that he no longer seeing the issue with dispatch map:<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"><pre>Hi All, I was doing some trial and error and I dont see the below issue now. I will continue with the current config and update if I face any issue further. Regards,Moksha</pre></div></div> |
Clarification needed on RSVPTE tunnel - IETF-TE-FP: Hi,we would like to know if we have support for path protection ( backup tunnel) te conifg in NSO CFP.!mpls traffic-enginterface GigabitEthernet0/0/0/6 backup-path tunnel-te 500 backup-path tunnel-te 150!Thanks,Arun.M.G | We do not. Are you able to use custom templates to satisfy your requirements?Hi Reginald,Thanks for the confirmation. can you please share the details / link to make use of Custom template with example?Thanks,Arun.M.GHere you go: You probably want to use device templates over feature templatesHi Arun,Did the device templates work for you?Thanks,RegiClosing ticket due to no response from submitterProposal suggested in this ticket will not work as PLM is looking for redundancy to be supported/expressed as part of service intent. |
Transport Slicing - hub rt value not accepting: Hi,While provisioning the transport slice, I'm giving,connectivity-type : any-to-anycisco-nss:vpn-target:auto-hub-rt: autohub-rt : 0:65001:100When i commit the transaction, i'm getting the below error:reason: invalid literal for int() with base 10: '0/0/0/1'. paths: /l3nm:l3vpn-ntw/vpn-services/vpn-service{NSS-L3-Dedic-100-internal}. path: /l3nm:l3vpn-ntw/vpn-services/vpn-service{NSS-L3-Dedic-100-internal}Thanks | Hi Magesh,Please share you payload.Thanks,Regi |
NSO TSDN 5.00-M4 FP service 250 failure: Service 250 also fails to be successfully deployed with working tunnels.It has single statements ; 2 head-ends and still we see no tunnel.Please review payloads (PFA) and advise.Regards,Shlomi | Had a meeting with Shlomi and tunnels are not up possibly due to missing BGP connectivity between PE-A and PE-C.Had a meeting with Shlomi and other required participants and figured out that the payload was missing some config due to which the tunnels were not getting created.Modified the payload and the tunnels were created.There was some config missing in the payload. Issue was resolved after fixing the payload |
Internal CS policies and VPN services mapping with parent service model: IN CNC UI , We have use-cases to know the mapping between internal policies/services that gets created from different model. Example for Circuit style model, it creates 2 internal SR-policies which has a different service key (Config ID/Name). The pattern we are seeing is '-internal' at the end. To understand and map the parent to the internal, we need to hardcode in our code.Is NSO model has this information available ? If not can this be a new requirement . | I'm not sure what exactly you are asking? Are you asking for the parent service backpointers to be available in the model instead of using the hardcoded service names based on `-internal` suffix?Thats correct. How do we know which parent service created the internal services ?Hi Dedeepya,You should be able to "get-modifications" to get the underlying services and then keep track of the parent services from CNC UI?Thanks,RegiHi,Had a discussion with my team and it seems you are able to get the service-meta-data via restconf which will show the backpointers ( ie parent services ).Command:Output:<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"><pre><vpn-services xmlns="urn:ietf:params:xml:ns:yang:ietf-l2vpn-ntw" xmlns:l2vpn-ntw="urn:ietf:params:xml:ns:yang:ietf-l2vpn-ntw"> <vpn-service refcounter="3" backpointer="[ /ietf-nss:network-slice-services/cisco-nss:slice-service-plan[cisco-nss:service-id='L2-ANY-TO-ANY']/cisco-nss:plan/cisco-nss:component[cisco-nss:type='ietf-nss-nano:sdp'][cisco-nss:name='0']/cisco-nss:state[cisco-nss:name='ietf-nss-nano:config-apply'] /ietf-nss:network-slice-services/cisco-nss:slice-service-plan[cisco-nss:service-id='L2-ANY-TO-ANY']/cisco-nss:plan/cisco-nss:component[cisco-nss:type='ietf-nss-nano:sdp'][cisco-nss:name='1']/cisco-nss:state[cisco-nss:name='ietf-nss-nano:config-apply'] /ietf-nss:network-slice-services/cisco-nss:slice-service-plan[cisco-nss:service-id='L2-HUB-SPOKE']/cisco-nss:plan/cisco-nss:component[cisco-nss:type='ietf-nss-nano:shared-slice'][cisco-nss:name='L2-ANY-TO-ANY']/cisco-nss:state[cisco-nss:name='ietf-nss-nano:config-apply'] ]"></pre></div></div>....Thanks,RegiExample you shown is for VPN services. My understanding is this will be same for SR Policy model as well. "backpointer" will reference the CS model instance that created these internal SR polices. Please confirm.Thank you. Hi Dedeepya,Sorry for the late response, but that's correct the service-meta-data is the same for all types of services as this is common information provided by the NSO platform and the our T-SDN CFPs itself.Thanks,Regi |
Device does not have a Network Element Driver registered error displayed though NSO installation was successful with devices: Device does not have a Network Element Driver registered error displayed though NSO installation was successful with devices | As per Link Ly triage analysis, this issue seems to be related to python3 crashing on NSO VM which is due to the memory leak known issue. This was impacting the NED packages to go into operation down state and NED registration issue for all devices.Note: The NSO VM (ubuntu 18) has sufficient resources (16 CPU, 64 Memory, 350 GB HD.) allocated but still memory crash issue is seen even with 2 services. This is interrupting testing ON/OFF.Workaround: Restarting ncs service with force package reload helped to resolve the issue. NED packages were updated to open UP state and devices were in-sync. |
Information needed on check-sync/sync-from/sync-to: Hi Team,I have a L3 MVPN service where I have one device out-of-sync.I want to check what will be the behavior of sync-from/sync-to on the L3 MVPN Service after I do sync-from on the device.Steps:1) Created a L3MVPN Service2) Login onto one of the device and update anything in the service3) Edit the Service, it will fail with the error device is out-of-sync4) perform sync-from on the device5) Perform sync-from or sync-toExpecting: it should pull the changes from the device and update the serviceCurrent behavior: ErrorScreenshot attached | Hello, Can you please provide us with the Payload being used and the NSO version being used for this issue? Attached the payloadCustomer confirmed this is NSO 6.1 versionDo we have any defect on this? or notes?So the issue is only when performing check-sync/sync-from/sync-to on MVPN Service? Customer confirmed that there is no behavior change and it is working correctlySee CDETS for more info |
NSO CFP - 5.0 - M3 - namespaces changed for multiple models - ODL compilation failure.: The M3 wiki page, , did not mentioned any changes to the new yang files under IETF-L3NM, we have to go through the Detail section to find these newly added feature:*ietf-mvpn.yang *cisco-mvpn.yang and the replacement of the namespaces following:ietf-te-cisco => cisco-teietf-l2vpn-ntw-cisco => cisco-l2vpn-ntwietf-l3vpn-ntw-cisco-augmentations => cisco-l3vpn-ntwApart from this, for IETF-L3NM - we faced issue with ODL from the new augmentation file mentioned above when we add the new 'mvpn' feature: Failed to execute goal org.opendaylight.yangtools:yang-maven-plugin:5.0.10:generate-sources (binding) on project ietf-l3vpn-nm-inventory-nbi-plugin: yang-to-sources: One or more code generators failed, including failed list(generatorClass=exception) {org.opendaylight.mdsal.binding.maven.api.gen.plugin.CodeGeneratorImpl=java.lang.NullPointerException} -> it would be nice if the Model/Payload change page have all the newly added and actual list of new or modified yang files. | Sure Quy, I will reach out to the developer who worked on this feature to add the additional new models to the models/changes page.Thanks,RegiHi Quy,I've gone ahead and update the wiki with a full list of model changes from M2--->Thanks,RegiHi Regi,Thank you so much for updating the wiki - i wish this was done at the M3 release on 10/7 so we could plan ahead - where 31 files were updated from the previous 3 files. Please keep the same update for M4 if possible.Thanks again,-QuySure, no problem. Will go ahead and close this ticket now.Thanks,Regi |
NSO CFP - 5.0 - M5-ENG-1 yang file changed without revision dates.: Best practice to add the revision when a yang file is modified, the following model yang files changed without 'revision':ietf-routing-policy.yang commenting out the block w/o revision of the following:// grouping apply-policy-group {// description// "Top-level container for routing policy applications. This// grouping is intended to be used in routing models where// needed.";ietf-l2vpn-ntw-nano-services.yangmodified w/o revision ncs:pre-condition {ncs:monitor "$SERVICE/l2vpn-ntw:vpn-nodes/l2vpn-ntw:vpn-node" {ncs:trigger-expr "not($SERVICE/l2vpn-ntw:vpn-type = 'vpn-common:mpls-evpn')";+ ncs:monitor "$SERVICE/vpn-type" {+ ncs:trigger-expr "not(. = 'vpn-common:mpls-evpn')"; } ncs:pre-condition {ncs:monitor "$SERVICE/l2vpn-ntw:vpn-nodes/l2vpn-ntw:vpn-node" {ncs:trigger-expr "$SERVICE/l2vpn-ntw:vpn-type = 'vpn-common:mpls-evpn'";+ ncs:monitor "$SERVICE/vpn-type" {+ ncs:trigger-expr ". = 'vpn-common:mpls-evpn'"; }</ul>ietf-network-slice-service.yang modified w/o revision dateuses ncs:service-data;ncs:servicepoint ietf-nss-servicepoint;+ ncs:servicepoint ietf-nss-servicepoint {+ ncs:conflicts-with ietf-nss-servicepoint;+ }cisco-network-slice-service.yangmodified w/o revision date @@ -216,6 +216,12 @@ module cisco-network-slice-service {}}}+ container sman-id-allocation-data {+ tailf:hidden full;+ leaf sman-id {+ type string;+ }+ }list dedicated-slice {Thanks and regards,-Quy | Hello, we have created an internal Jira ticket to track this revision date change.Thank you.Ticket has been fixed and merged. Fix will be available in the next release (TSDN 5.0 M5). Thank you. |
zlib 1.2.7.1 missing NSO 6.0: This is the error message while starting ncs/opt/ncs/current/lib/ncs/erts/bin/ncs.smp: /lib64/libz.so.1: version `ZLIB_1.2.7.1' not found (required by /opt/ncs/current/lib/ncs/erts/bin/ncs.smp)Latest zlib 1.2.7-20.el7_9 is installed in this setup Cent OS 7 setup.Exact zlib 1.2.7.1 is not available. How to proceed with starting ncs install.Setup : 172.20.63.189cnctest/Ovatest123@ | # yum list zlibLoaded plugins: fastestmirror, langpacksLoading mirror speeds from cached hostfilebase: centos.mirrors.hoobly.comextras: centos-distro.cavecreek.netupdates: centos.vwtonline.netInstalled Packageszlib.i686 1.2.7-20.el7_9 @updateszlib.x86_64 1.2.7-20.el7_9 @updates#Hello, we would recommend troubleshooting this issue with your support teams.For TSDN, We have already provided the relevant info on the release email.Regardless, I have posted link from a general google search as below which may provide some pointers.Thank you.Ticket is Misrouted. Troubleshooting this issue is not in our scope.Internal comment!!CentOS-7 is based on RHEL-7 (released back in 2014), which include libc-2.17, and therefore not supported since glibc-2.19 is required. Upgrading to CentOS-8 should solve this. |
Getting devices not have Network element driver registered in NSO: DescriptionInstalled NSO - ncs-6.1_221212.150815390.4b4cc38b0df7.linux.x86_64.installer.binAdded required tsdn and dlm package - nso-6.1_221212-tsdn-5.0.0-M5-NSO-Engg-1.tar.gz and cw-na-dlm-fp-5.0.0-nso-6.1-eng-38-221220.tar.gzNSO was properly connected and synced with devices. Due to power outage in lab all VM's got powered off. After bring up the VM's and devices checked the connectivity status getting this error Device <device name> does not have a Network Element Driver registeredTried removing devices and re-attached still getting same error | setup detail - 10.22.179.240 - xrd1/Cwork123!Hi Murali,I saw that some of package ware not up. So I restart NCS and every thing works normally now.I forsee this isssue would happen again since the system memory is NOT up to specificationxrd1@xrd1:~$ lsmemRANGE SIZE STATE REMOVABLE BLOCK0x0000000000000000-0x00000000bfffffff 3G online yes 0-230x0000000100000000-0x000000043fffffff 13G online yes 32-135Memory block size: 128MTotal online memory: 16GTotal offline memory: 0BPlease increase the DRAM on this server. At least it should be 64GB as minimun requirementThanks,LinhThere is no update from submitter. I am going to close the ticket.Regards,Linh |
Issues while provisioning from NSO to Juniper device. : Trying to provision from NSO to Juniper device (version:Junos: 22.1R1.10). Juniper device package install (ncs-5.7.6-juniper-junos-4.7.12.tar.gz), Device addition, ssh fetch host keys and sync succeeded. But while trying to provision, receiving error as belowError: Validation failederrors: reason: Python cb_validate error. STATUS_CODE: TSDN-L3VPN-408 REASON: Router NED not supported CATEGORY: user SEVERITY: ERROR Context [name = Router NED not supported: juniper-junos-nc-4.7:juniper-junos-nc-4.7, message = Missing dynamic device mapping state = {'Device': 'F9-Juniper-vMX', 'Service': 'L3NM-L3VPN_NM-IGP-IPV4-90-internal', 'Device NED ID': 'juniper-junos-nc-4.7:juniper-junos-nc-4.7'}] . paths: /cisco-flat-L3vpn-fp-internal:flat-L3vpn{L3NM-L3VPN_NM-IGP-IPV4-90-internal F9-Juniper-vMX_1}. path: /cisco-flat-L3vpn-fp-internal:flat-L3vpn{L3NM-L3VPN_NM-IGP-IPV4-90-internal F9-Juniper-vMX_1}Kindly help fixing the issue. ThanksSetup: 10.195.165.90 - xrd1/xrd1 | Hi Ajitha,I'm assuming you've already created a python implementation for the juniper NED. Now, you need to set the dynamic mappings for the juniper NED for L3.:<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"><pre>admin@ncs% show cisco-flat-L3vpn-fp:cfp-configurations dynamic-device-mapping dynamic-device-mapping cisco-ios-cli-6.77:cisco-ios-cli-6.77 { python-impl-class-name flat_l3vpn_multi_vendors.IosXE;}dynamic-device-mapping cisco-iosxr-nc-7.315:cisco-iosxr-nc-7.315 { python-impl-class-name flat_l3vpn_multi_vendors.NativeXR;}dynamic-device-mapping cisco-iosxr-nc-7.3:cisco-iosxr-nc-7.3 { python-impl-class-name flat_l3vpn_multi_vendors.NativeXR;}dynamic-device-mapping cisco-iosxr-nc-7.4:cisco-iosxr-nc-7.4 { python-impl-class-name flat_l3vpn_multi_vendors.NativeXR;}dynamic-device-mapping cisco-iosxr-nc-7.5:cisco-iosxr-nc-7.5 { python-impl-class-name flat_l3vpn_multi_vendors.UMXR;}dynamic-device-mapping cisco-iosxr-nc-7.6:cisco-iosxr-nc-7.6 { python-impl-class-name flat_l3vpn_multi_vendors.UMXR;}dynamic-device-mapping cisco-iosxr-nc-7.7:cisco-iosxr-nc-7.7 { python-impl-class-name flat_l3vpn_multi_vendors.UMXR;}</pre></div></div>Thanks,RegiHi Reginald, I have added Juniper NED . would you please suggest the steps for Python implementation for the Juniper NED/to check if its done correctly.I can see the Juniper package in "show packages package oper-status" and im able to add Juniper ned to device and sync it. But i dont see juniper equivalent of "cisco-flat-L3vpn-fp:cfp-configurations". Would you please suggest to resolve thisHi Ajitha,T-SDN does not support Juniper devices by default. You can leverage "multi-vendor" support by writing your own package which translates L3 Service configs to Juniper NED configuration.For more details, please refer to our wiki: Thanks,RegiSpoke to Ajitha, she will reach out to CX since it seems they added Juniper support |
Could not provision L2VPN service with 700 EP: NCS - 5.7.5.1, Scale setup with 25K devices.Tried to create L2VPN ELAN with 500 EP. It completed in 26 mins.L2-EVPN_MP_ELAN_14 Attempted to create the same with 700 EP. It took 75 mins and it timed out with following message<errors xmlns="urn:ietf:params:xml:ns:yang:ietf-restconf"> <error> <error-type>application</error-type> <error-tag>malformed-message</error-tag> <error-path></error-path> <error-message>rfs-3: transport timeout; closing session</error-message> </error></errors>Service : L2-EVPN_MP_ELAN_15Setup : 172.20.63.132 - cnctest/Ovatest123@ - CFS172.20.63.148,172.20.63.149,172.20.63.150 - Same credentialsNeed support to provision service upto 1000 EP. | Hi Rama, would you be able to tell me how long it took for the commit to timeout (75 minutes for single service before timeout)? Also is this a single L2VPN MP service or several services?Thanks,Isaac KimWhen you commit your L2 service, could you execute the commit with the following settings:commit | details very-verbose | save commit-output.txtOnce done, could you upload the commit-output.txt to this ticket?Thanks,Isaac KimI execute this command as REST api using curl command. This is a single L2VPN service with 700 end points from 700 devices. i dont execute explicit commit. The script completed in 4551 Seconds, same as 75 mins. Attaching the payload to this ticket. You can remove first and last line in the payload.Hi Rama,Can you try directly load merging the payload into NSO and see what the error message may be?If you're still getting transport timeout issues, then you may want to adjust your device timeouts:Globally:<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"><pre>admin@ncs% show devices global-settings connect-timeout 250;read-timeout 250;write-timeout 250;</pre></div></div>Per Device:<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"><pre>set devices device rfs-3 write-timeoutset devices device rfs-3 read-timeoutset devices device rfs-3 connect-timeout</pre></div></div>Thanks,RegiAfter sync-from, and increasing the timeout, service with 700EP created in 3052 seconds.Trying the same with 1000 EP times out.2406.955curl: (56) Recv failure: Connection reset by peerreal 40m6.966suser 0m0.055ssys 0m0.066sFinished 10 Service: L2-EVPN_MP_ELAN_20 to L2-EVPN_MP_ELAN_29 Took: 2411 SecondsCan you do a direct load onto NSO? It may help clarify the issue here, since "Connection reset by peer" is a pretty broad message.Thanks,RegiI loaded in NSO UI. Though it logged out after some time, i could see the service created with 1000 EP. Do we have a timeout that can be configured for a REST api request. curl timed out because it took around 40 minutes. Hi Srini,As discussed offline, please try with timeout option on curl client such as:<tt>curl --connect-timeout <duration> <URL></tt>Thanks,Van |
ELAN /ETREE Provisioning issue - NSO 6.1 - TSDN 5.0.0 M5+ - nso-6.1_221212-tsdn-5.0.0-M5-NSO-Engg-1.tar.gz: ELAN /ETREE Provisioning issue - NSO 6.1 - TSDN 5.0.0 M5+ - nso-6.1_221212-tsdn-5.0.0-M5-NSO-Engg-1.tar.gzCW 206 , Cat 215 and SH 242 combo installed with latest NSO 6.1 TSDN 5.0.0 M5 .( NSO 6.1 - TSDN 5.0.0 M5+ Engg Build., - nso-6.1_221212-tsdn-5.0.0-M5-NSO-Engg-1.tar.gz)We see issue in provisioning ELAN/ETREE services with below error. errors: reason: /cisco-flat-L2vpn-fp-internal-site:flat-L2vpn-internal-site-service{L2NM-MG-EVPN-MP-ELAN-2345-internal ASR9006-SDN-128_a1}/flat-L2vpn-evpn-multipoint/site{ASR9006-SDN-128_a1}/split-horizon: the 'when' expression "../leaf" failederrors: reason: /cisco-flat-L2vpn-fp-internal-site:flat-L2vpn-internal-site-service{L2NM-MG-EVPN-MP-ETREE-internal ASR9006-SDN-91_a1}/flat-L2vpn-evpn-multipoint/site{ASR9006-SDN-91_a1}/split-horizon: the 'when' expression "../leaf" failedAttached payload and snapshotsNOte: this was working fine in NSO 6.0 M5 . | This is known issue we already filed a RT |
Scope of support for L2/L3 vpn services over SRv6 policies: Hi,We have several features to support services over SRv6 policies in CNC 5.0 / SH 5.0, but according to the attached sheet the only supported service will be L3VPN over SRv6 ODN policies.Can you please clarify the scope of the support from NSO perspective in CFP for TSDN 5.0.0 ? Regards,Leonid. | Hi Leonid,We support only SR-ODN/SRv6-ODN for L3VPN and both SR-POLICY and SR-ODN for L2VPV P2P.Can you let us know what's the source of the attached sheet?Thanks,NikhilHi Leonid,Let us know if you need anything else from our side or we may close the ticket.Thanks,NikhilThank you for the quick response,What is the support for L2VPN EVPN and L2VPN ELAN/ETREE services ?Regards,Leonid.Hi LeonidFor L2VPN EVPN, we support both SR-Policy and SR-ODN and L2VPN ELAN/E-TREE, we support SR-ODN.Thanks,NikhilProvided required information to the user.Just a small update, L2VPNP2P does not support SR-ODN.When you are saying that "For L2VPN EVPN, we support both SR-Policy and SR-ODN" - do we support also L2VPN EVPN over SRv6-TE and SRv6-ODN or only regular (v4) SR-TE/ODN ? |
Information needed on L3 MVPN Dynamic/Static Tree-SID: Hi Team,It will be helpful if I can get more information on below items:1) mvpn-ipmsi-tunnel-ipv4 and mvpn-spmsi-tunnel-ipv4 From the payloads in TSDN5.0 Wiki, I found that tunnel-type in both is always same. Is this the case or user can define different options in both. if not permitted then will there be any errors2) IPv6 supported3) What platform versions are supported.4) There is vpn-service-topology that is introduced for L3, do we have sample payloads for P2P, any-to-any, hub-and-spoke5) For switch-wildcard, what other values are there apart from source-group.Thanks,Kanchan | Hi Kanchan,1) mvpn-ipmsi-tunnel-ipv4 and mvpn-spmsi-tunnel-ipv4From the payloads in TSDN5.0 Wiki, I found that tunnel-type in both is always same. Is this the case or user can define different options in both. if not permitted then will there be any errors > tunnel-type will be <tunnel-type>sr-mpls-p2mp</tunnel-type> for dynamic and tunnel-type will be <tunnel-type>static-sr-mpls-p2mp</tunnel-type> for static use cases. in dynamic , tunnel-type allways will be 'sr-mpls-p2mp' for both mvpn-ipmsi-tunnel-ipv4 and mvpn-spmsi-tunnel-ipv4.2) IPv6 supported > No. Only Ipv4 is supported now.3) What platform versions are supported. > Mvpn is supported by all XR versions as mentioned in the release wiki.Please refer to the following Please note that Route Policy data-mdt is supported from cisco-iosxr-nc-7.5.2+4) There is vpn-service-topology that is introduced for L3, do we have sample payloads for P2P, any-to-any, hub-> and-spoke > Please add the multicast containers from the mvpn payloads to the existing payloads you have for P2P, any-to-any, hub-and-spoke.5) For switch-wildcard, what other values are there apart from source-group. > switch-wildcard can be either 'source-group' or 'star-star'. 'star-star' is used for mdt partition.Thanks,Nishad Subair.Hi Nishad,Thanks for the all the responses.For L3 P2P, H;S, Any-to-any can you provide the link for the payloads? I have payloads for only L2 Service.Also wanted to check if we support L3 Static/Dynamic MVPN with service assurance?Thanks,KanchanHi Nishad,Do we also support XRd deployments for L3 MVPN ?Thanks,KanchanHi Nishad, Is Tree-SID supported on XE devices?Thanks,KanchanHi Kanchan,Not supported on XE devices.Thank you,Nishad Subair |
How to define Roles in P2MP in EVPN-MP In Flat Mode: I amreferring the FLAT model. node-roleis not there So I willfollow your logic PIOSXR-0 HUBPIOSXR-1..N SPOKEs | L2NM used hub and spoke terminology. Flat-L2 uses "tree" terminology ( ie. root/leaf ). The corresponding config for node-role in flat-L2 is called "leaf" |
need help with cleanup procedure on LSA setup: when i'm triggering cleanup on CFS, it always responds back with ok in north bound response. For example, if the device is out of sync with RFS, the North bound response with CFS for cleanup says ok. I expect the cleanup to fail because device is out of sync. In other words, requirement is to cleanup the service in one transaction from client to CFS to RFS. Can you please guide me | Can you please give me the setup where this issue has occurred?Thanks Sahithi,CFS - 10.64.96.102 nso/Cwork123!RFS - 10.64.96.124 nso/Cwork123!Device - 10.64.96.113 cisco / Cwork123!Hi Sahithi, Did you get a chance to look into it ? Please let me know if you need more infoHi Raja,Checked your setup.I do not see any of the T-SDN services on your setup.I see TM-TC FP package and an action call in audit Are you trying perform cleanup on tm-tc service?ThanksSahithiHi Sahithi, yes i'm trying to run cleanup on tm-tc service. Sorry i guess i was not clear. The issue is not related to tsdn fp.Hi Raja,TM-TC FP must have implemented their custom action for cleanup of their service. We are not aware of the implementation in TM-TC.Can you please approach the team which owns this FP? |
CNC M4 pacakges are referencing NETCONF NED in bootstrap files: CNC M4 pacakges are referencing NETCONF NED in bootstrap files.This should be changed to CLI NED.admin@ncs> show configuration cisco-sr-te-cfp:cfp-configurations dynamic-device-mapping cisco-ios-cli-6.77:cisco-ios-cli-6.77 { python-impl-class-name sr_te_multi_vendors.IosXE;}dynamic-device-mapping cisco-iosxr-nc-7.315:cisco-iosxr-nc-7.315 { python-impl-class-name sr_te_multi_vendors.NativeXR;}dynamic-device-mapping cisco-iosxr-nc-7.3:cisco-iosxr-nc-7.3 { python-impl-class-name sr_te_multi_vendors.NativeXR;}dynamic-device-mapping cisco-iosxr-nc-7.4:cisco-iosxr-nc-7.4 { python-impl-class-name sr_te_multi_vendors.NativeXR;}dynamic-device-mapping cisco-iosxr-nc-7.5:cisco-iosxr-nc-7.5 { python-impl-class-name sr_te_multi_vendors.UMXR;}admin@ncs> more SR-multi-vendor-iosxe-cli.xml<config xmlns="http://tail-f.com/ns/config/1.0"> <cfp-configurations xmlns="http://cisco.com/ns/nso/cfp/cisco-tsdn-sr-te"> <dynamic-device-mapping> <ned-id>cisco-ios-cli-6.77:cisco-ios-cli-6.77</ned-id> <python-impl-class-name>sr_te_multi_vendors.IosXE</python-impl-class-name> </dynamic-device-mapping> </cfp-configurations></config>more SR-multi-vendor-iosxr-netconf.xml <config xmlns="http://tail-f.com/ns/config/1.0"> <cfp-configurations xmlns="http://cisco.com/ns/nso/cfp/cisco-tsdn-sr-te"> <dynamic-device-mapping> <ned-id>cisco-iosxr-nc-7.3:cisco-iosxr-nc-7.3</ned-id> <python-impl-class-name>sr_te_multi_vendors.NativeXR</python-impl-class-name> </dynamic-device-mapping> <dynamic-device-mapping> <ned-id>cisco-iosxr-nc-7.4:cisco-iosxr-nc-7.4</ned-id> <python-impl-class-name>sr_te_multi_vendors.NativeXR</python-impl-class-name> </dynamic-device-mapping> <dynamic-device-mapping> <ned-id>cisco-iosxr-nc-7.315:cisco-iosxr-nc-7.315</ned-id> <python-impl-class-name>sr_te_multi_vendors.NativeXR</python-impl-class-name> </dynamic-device-mapping> <dynamic-device-mapping> <ned-id>cisco-iosxr-nc-7.5:cisco-iosxr-nc-7.5</ned-id> <python-impl-class-name>sr_te_multi_vendors.UMXR</python-impl-class-name> </dynamic-device-mapping> </cfp-configurations></config> | Hello,CLI NEDs are Native to TSDN and can be used at all times (has nothing to do with the above output/bootstrap)TSDN additionally provides option to test Netconf NEDs as seen in the above output created by the bootstrap files.If you do not want to use Netconf NEDs then not loading these bootstrap files will suffice.Please let me know if this helps.Thank you.Can we skip dynamic mapping configuration for CLI NED's?Yes, we can skip dynamic mapping configuration for CLI NED's because CLI is native and will work without any bootstrap configloaded in.Thanks for the update.For CLI NED update wiki as to not require explicit dynamic mapping configuration Thank you. The wiki has been updatedYou will see a comment as below which indicates that the bootstrap files are optional.Please let me know if I may close this ticket.<tt>## CFP Multi-Vendor Dynamic Mapping - Optional</tt><tt>for</tt><tt>CLI NED but required</tt><tt>for</tt><tt>NETCONF NED ##</tt><tt>==========================================================================================</tt><tt>load merge SR-multi-vendor-iosxr-netconf.xml</tt><tt>load merge L3VPN-multi-vendor-iosxr-netconf.xml</tt><tt>load merge L2VPN-multi-vendor-iosxr-netconf.xml</tt><tt>load merge IETF-TE-multi-vendor-iosxr-netconf.xml</tt>Closing ticket as issue is clarified.Updated Wiki with Information about CLI being native to TSDN and no bootstrap config required in the case of CLI. |
Provide sample configs and operational status for Y.1731 config: Can you provide sample configs that you used for below combinations and share the output of Y.1731 operational commands:XR ; XR deviceXE ; XE deviceXR ; XE device (this one I got from Sujay. I used VPN service config to configure probes between 2 XR devices)</ul>Y.1731 Operational Commands for XR:show ethernet sla statisticsshow ethernet cfm peer meps </ul>XE operational sample:XE-PE1#show ethernet cfm statisticsBRAIN MAC: 001e.49ac.dcbfDomainName: ncsMA Name: L2NM-xe-y173-xeMPID: 3 Last clearing of counters: never CCMs: Transmitted: 101 Rcvd Seq Errors: 0 LTRs: Unexpected Rcvd: 0 Total Tx LTR: 0 Total Rx Valid LTR: 0 Total Rx Invalid LTR: 0 Rx Invalid Relay Action: 0 LTMs: Total Tx LTM: 0 Total Rx Valid LTM: 0 Total Rx Invalid LTM: 0 LBRs: Transmitted: 0 Rcvd Seq Errors: 0 Rcvd in order: 0 Rcvd Bad MSDU: 0 Rx Invalid LBR: 0 LBMs: Total Tx LBM: 0 Total Rx Valid LBM: 0 Total Rx Invalid LBM: 0XR operational sample:RP/0/RSP0/CPU0:PE1#show ethernet cfm peer meplags:> - Ok I - Wrong intervalR - Remote Defect received V - Wrong levelL - Loop (our MAC received) T - Timed outC - Config (our ID received) M - Missing (cross-check)X - Cross-connect (wrong MAID) U - Unexpected (cross-check)<ul>- Multiple errors received S - Standby</ul>Domain nso (level 1), Service L2NM-xr-y1731-xrUp MEP on HundredGigE0/0/0/3 MEP-ID 1================================================================================St ID MAC Address Port Up/Downtime CcmRcvd SeqErr RDI Error– ----- -------------- ------- ----------- --------- ------ ----- -----X 2 1c00.0063.1d0c Up 00:06:29 389 0 389 389RP/0/RSP0/CPU0:PE1#show ethernet sla statisticource: Interface HundredGigE0/0/0/3, Domain nsoDestination: Target MEP-ID 2================================================================================Profile 'loss-profile', packet type 'cfm-loss-measurement'Scheduled to run every 1min first at 00:00:49 UTC for 1minOne-way Frame Loss (Source->Dest)~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~1 probes per bucketNo stateful thresholds.Bucket started at 01:09:49 UTC Sat 31 July 2021 lasting 1min Pkts sent: 60; Lost: 0 (0.0%); Corrupt: 0 (0.0%); Misordered: 0 (0.0%); Duplicates: 0 (0.0%) Result count: 0 Min: 0.000%; Max: 0.000%; Mean; 0.000%; StdDev: 0.000%;Bucket started at 01:10:49 UTC Sat 31 July 2021 lasting 1min Pkts sent: 60; Lost: 0 (0.0%); Corrupt: 0 (0.0%); Misordered: 0 (0.0%); Duplicates: 0 (0.0%) Result count: 0 Min: 0.000%; Max: 0.000%; Mean; 0.000%; StdDev: 0.000%;Bucket started at 01:11:49 UTC Sat 31 July 2021 lasting 1min Pkts sent: 60; Lost: 0 (0.0%); Corrupt: 0 (0.0%); Misordered: 0 (0.0%); Duplicates: 0 (0.0%) Result count: 0 Min: 0.000%; Max: 0.000%; Mean; 0.000%; StdDev: 0.000%;One-way Frame Loss (Dest->Source)~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~1 probes per bucketNo stateful thresholds.Bucket started at 01:09:49 UTC Sat 31 July 2021 lasting 1min Pkts sent: 60; Lost: 0 (0.0%); Corrupt: 0 (0.0%); Misordered: 0 (0.0%); Duplicates: 0 (0.0%) Result count: 0 Min: 0.000%; Max: 0.000%; Mean; 0.000%; StdDev: 0.000%;Bucket started at 01:10:49 UTC Sat 31 July 2021 lasting 1min Pkts sent: 60; Lost: 0 (0.0%); Corrupt: 0 (0.0%); Misordered: 0 (0.0%); Duplicates: 0 (0.0%) Result count: 0 Min: 0.000%; Max: 0.000%; Mean; 0.000%; StdDev: 0.000%;Bucket started at 01:11:49 UTC Sat 31 July 2021 lasting 1min Pkts sent: 60; Lost: 0 (0.0%); Corrupt: 0 (0.0%); Misordered: 0 (0.0%); Duplicates: 0 (0.0%) Result count: 0 Min: 0.000%; Max: 0.000%; Mean; 0.000%; StdDev: 0.000%; | Hello Nipa,Thanks for sharing the payloads. Helped us validate the configurations on our testbeds.I didnt see any noticeable differences between what you shared and what we configured on our testbed.Also, here are my findings in the outputs that you shared. Can you please double check:Output for show ethernet cfm peer meps:Peer mep status is showing X and not >(Ok)Output for show ethernet sla statistics:Only showing Loss related stats which is inline with what we see in our testbedI dont see any Probes stats being reported for Jitter ; LatencyBut I see that Service configuration shows that Delay profile got attached to the ServiceThanks,-LingeshPayload have been provided. Further support details will be given on |
Error: on line 2: unknown namespace: http://com/cisco/cfp-common-status-codes in status-code-cfp: Raising same issue again.10.56.116.162 nso/ Public1234!Error when trying to run this:cd nso-<NSO-Version><del>tsdn</del><Release-Version>/tsdn-lsa/tsdn-lsa-rfs/bootstrap-datancs_cli -u <user>% configure% unhide debug% load merge SR-status-codes.xml% load merge SR-internal-plan-monitor.xml% load merge RSVP-TE-status-codes.xml% load merge RSVP-TE-internal-plan-monitor.xml% load merge rfs-custom-template-settings.xml% load merge L3VPN-status-codes.xml% load merge L3VPN-internal-plan-monitor.xml% load merge L2VPN-status-codes.xml% load merge L2VPN-internal-plan-monitor.xml% load merge dispatch-map-settings.xml% load merge commit-queue-settings.xml% load merge bootstrap-autopopulate-dispatch.xml% commit | Hi Aviv,I look at your setup and I don't see any package installed.nso@ncs> show packages package% No entries found.nso@ncs>You need to install packages before load merge bootstrap xml files-LinhI am going to close the ticket if I don't receive any new update.Thanks,Linh |
cnc-custom metadata for two configs "ietf-te-service" and "policy" in L2VPN service.: We are planning to add a similar support as the interface list for two fields in L2VPN. Can you please help by adding a similar cnc-custom metadata for two configs "ietf-te-service" and "policy" in L2VPN model. Please note here there is a new attribute added "leaf-validation" : "true", compare to the other cnc-custom meta data we had in the other fields.For the policy the path is "/l2vpn-ntw:l2vpn-ntw/vpn-services/vpn-service/vpn-nodes/vpn-node/te-service-mapping/te-mapping/sr-policy/policy" and the following is the cnc-custom meta-data annotation tailf:meta-data "cnc-custom" { tailf:meta-value ' { "dependency": "[]", "type": "dropdown", "field": "policy-list","leaf-validation" : "true", "pre-select": "none" }'; }For ietf-te-service the path is "/l2vpn-ntw:l2vpn-ntw/vpn-services/vpn-service/vpn-nodes/vpn-node/te-service-mapping/te-mapping/te-tunnel-list/ietf-te-service" and the cnc-custom meta-data annotation will be tailf:meta-data "cnc-custom" { tailf:meta-value ' { "dependency": "[]", "type": "dropdown", "field": "ietf-te-service-list","leaf-validation" : "true", "pre-select": "none" }'; } | Thanks Demeke for creating thisHi Can you please confirm if we would still require the ietf_l2vpn_ui_validation.yang i.e.below annotation in the build along with the new requirement? // annotate a single path tailf:annotate "/ietf-l2vpn-ntw:l2vpn-ntw/ietf-l2vpn-ntw:vpn-services/ietf-l2vpn-ntw:vpn-service/ietf-l2vpn-ntw:vpn-nodes/ietf-l2vpn-ntw:vpn-node/cisco-l2vpn-ntw:te-service-mapping/cisco-l2vpn-ntw:te-mapping/cisco-l2vpn-ntw:te/cisco-l2vpn-ntw:sr-policy/cisco-l2vpn-ntw:sr-policy/cisco-l2vpn-ntw:policy" { tailf:meta-data "ui-data-validation" { tailf:meta-value "leaf-validation"; } }Internal JIRA ticket -> Latest Green Build CCO : Any update?Hi Sahithi, I installed the dev image and it works as expected. Please don't merge this change into CFP release that goes with the CNC 6.0 release train. As this change will break existing implementation it only should be merge into the CFP release that goes with CNC 7.0.Thanks Demeke!Ticket is completed and merged starting CNC 7.0. |
Isolation type missing for L2 P2P dedicated Slice: Hi,When we create L2P2P dedicated Slice. NSO UI doesn't show up isolation type.Where as it does show up for other types like HS.Kindly let us know. | Hi Naveenkumar,Isolation type and single-sided-control are removed from NSS L2-P2P in 6.0.Regards,LinhHi Linh, I do not see this reflected in . Did we miss anything here? It state in this sectionHello, please let us know if ticket maybe resolved.If no response is received, ticket will be closed EOD 8/26/2023.Hi Janaki,There is a meeting around this issue.Kindly don't close it.Thanks,NaveenPer the discussing meet, CNC team will make change in CNC UI. So I closed this ticket.Regards,Linh |
No device level failure details for L2VPN service: 1. Make one of the devices out of sync. (eg. PE-7)2. Provision L2vpn service Failed as expected. But on CNC UI Component Errors page does not show PE-7 in device table. The NSO-UI page shows empty "status-code-details" 3. Provision SRv6 policy Failed as expected. It does show "PE-7" on device table in CNC-UI. It also has "status-code-details" on NSO-UI.Is there a reason why L2vpn behaves differently?screenshots and payload attached.NSO version: 5.7.2.1TSDN version: 4.0.0 M4 | Hi Crystal,From looking at the Screenshots, it seems to me that the L2VPN configuration in itself is erroneous and thus there was no push to the device. The Error about device config is showing at the top of the Screenshot on the L2VPN page. The SRV6 on the other hand seems to have a config push which was failed due to device not being In Sync. Can you please confirm that the L2VPN config being pushed to the device is correct in the first place ...?Please also let me know the setup details if I can log into it and reproduce issue.Thank you.Hello, please let us know the status of this ticket so it may be closed. Thank you.Hi Janaki,The L2VPN configuration is a good one which has been used for many times as regression test. I am able to reproduce the issue. Here is the setup info.:CW URL: pw: Cwork123!NSO IP: 2001:420:10e:201d:172:23:85:193user: rootPw: Vtsisco@123!L2vpn service payload attached Hi Crystal, From further investigation this behavior is expected due to resource allocation in the payload.We will mark the plan as failed and an alarm text will be seen on NSO.Thank you.Regards,Janaki DuggiralaExpected behavior with Resource Allocation in L2VPN. |
NSO not closing Restconf stream sessions: This is triaged from wider team.I see that each Restconf stream is opening a new session, and session remains opened even when the request is closed.Also double checked the NSO documentation, and dont see nothing mentioning any logout is needed for such requests, also no login cookie token involved here.This is easily reproduced from CURL:admin@ncs> show users | countCount: 45 linesnso5711@iorgad-exsi-vm1:~$ curl -kisu USER:PASS -X GET -H "Accept:text/event-stream" HTTP/1.1 200 OKDate: Tue, 26 Apr 2022 05:16:47 GMTCache-Control: private, no-cache, must-revalidate, proxy-revalidateContent-Type: text/event-streamTransfer-Encoding: chunkedPragma: no-cacheContent-Security-Policy: default-src 'self'; block-all-mixed-content; base-uri 'self'; frame-ancestors 'none';Strict-Transport-Security: max-age=15552000; includeSubDomainsX-Content-Type-Options: nosniffX-Frame-Options: DENYX-XSS-Protection: 1; mode=block^Cnso5711@iorgad-exsi-vm1:~$admin@ncs> show users | countCount: 46 lines | Hi Liran,The restconf command that you test is for stream notification subscription and it is designed to have a very long session timeout.If you test on a normal restconf command, NSO does terminate the session. Take authgroup restconf for exampleadmin@ncs> show users | countCount: 9 linescurl -is -u admin:Cisco123# -H "Accept: application/yang-data+xml" HTTP/1.1 200 OKDate: Tue, 26 Apr 2022 20:51:30 GMTLast-Modified: Sat, 23 Apr 2022 01:36:47 GMTCache-Control: private, no-cache, must-revalidate, proxy-revalidateEtag: "1650-677834-287817"Content-Type: application/yang-data+xmlTransfer-Encoding: chunkedPragma: no-cacheAccess-Control-Allow-Origin: *Content-Security-Policy: default-src 'self'; block-all-mixed-content; base-uri 'self'; frame-ancestors 'none';Strict-Transport-Security: max-age=15552000; includeSubDomainsX-Content-Type-Options: nosniffX-Frame-Options: DENYX-XSS-Protection: 1; mode=block<authgroups xmlns="http://tail-f.com/ns/ncs" xmlns:ncs="http://tail-f.com/ns/ncs"> <group> <name>iosxe_authgroup</name> <default-map> <remote-name>admin</remote-name> <remote-password>$9$gdKMS2xf8pAySVzPZFeL/JZwwo6KF59UeIbvjYi/6fM=</remote-password> <remote-secondary-password>$9$2DS2LsLUzsfBSnKEf+NJ4bugTxihmHR94nDcuGFtX+A=</remote-secondary-password> </default-map> </group> <group> <name>iosxr_authgroup</name> <default-map> <remote-name>admin</remote-name> <remote-password>$9$h2kB2zmyVMWY+ZCttz5hrk0erNZ0MKKwrubw0Pv04iU=</remote-password> <remote-secondary-password>$9$DoPJbqjNbu3ZCNbnImg8F3UPZ5Oof7QcMUbtrOaG0Gk=</remote-secondary-password> </default-map> </group> <group> <name>vxr_iosxr_authgroup</name> <default-map> <remote-name>cisco</remote-name> <remote-password>$9$gyy5jCiJ/zUjBygSj80ToSrb4XKWmRSZUyWb3xaxFug=</remote-password> <remote-secondary-password>$9$XFRCcOBiq0dVnWwAlt7hImmJvJ3xrQToaaIEOya7h6Q=</remote-secondary-password> </default-map> </group></authgroups>admin@ncs> show users | countCount: 9 linesadmin@ncs>Termination session also shows in audit.log<INFO> 26-Apr-2022::13:51:30.065 linh-nso-172-8 ncs: audit user: admin/182 assigned to groups: ncsadmin,ncsoper,admin,wheel<INFO> 26-Apr-2022::13:51:30.066 linh-nso-172-8 ncs: audit user: admin/182 created new session via rest from 10.155.144.11:65404 with http<INFO> 26-Apr-2022::13:51:30.066 linh-nso-172-8 ncs: audit user: admin/182 RESTCONF: request with http: GET /restconf/data/tailf-ncs:devices/authgroups HTTP/1.1<INFO> 26-Apr-2022::13:51:30.074 linh-nso-172-8 ncs: audit user: admin/182 RESTCONF: response with http: HTTP/1.1 /restconf/data/tailf-ncs:devices/authgroups 200 duration 196521 ms<INFO> 26-Apr-2022::13:51:30.074 linh-nso-172-8 ncs: audit user: admin/182 terminated session (reason: normal)So if content-Type: is event-stream, it has a very long session timeout. Again it is by design.Thanks,LinhHi Liran,I will close this ticket in next few days if I don't see any update on your side.Thanks,LinhThis is first time we are aware that NSO sessions remain open.This creates an issue with CNC, thus requesting here a solution from NSO team.To add some context, from past issues, it was observed that stream connections were idle and did not receive any notifications without any indication this is why daily stream refresh mechanism was added, by closing the request and open a new one. Without it, there were notifications loss. Without closing sessions of closed connections by NSO, it can lead to reaching sessions limit and possibly further implications. Please note, additional ticket was opened for NSO team for option to use keep-alive as default at CNC. If it was added, we may have consider reducing the need for daily refresh mechanism. The option is supported and there was a request to add it to CNC NSO installation official guidelines, but it was rejected by NSO team.This leads to a problem with all possible considered solutions:1.Daily refresh mechanism, current situation: sessions count keep increasing, it can lead to reaching sessions limit and possibly further implications.2.Remove daily refresh mechanism: notification loss situations observed.3.Remove daily refresh mechanism together with keep-alive: rejected by NSO team to document it as CNC installation guidelines, and was not included in testing.Adding:Even regardless of daily refresh mechanism, NSO sessions remain open is still an issue, as in multiple scenarios, like CNC cluster restart, VM restart, service restart, leader change, user remove/add of NSO provider, patches installation, version update and more, a new request is triggered, leading to leftover NSO session from previous request. Over time, NSO sessions count can keep increasing. Also got indications from CX that additional clients may open NSO notification stream requests, which can lead to additional leftover NSO sessions on each disconnection / request stop.This is getting escalated from the customer and project manager, and triaged also from wider team.The keep-alive ticket:HI Lin/Van and Luan/Sahithi,Do we need to open an RT for this?Thanks,NipaHi Liran,Thanks for sharing the previous JSD. I reverified the settings as described this ticket. Event-connection session timeout works as expect with 4.0 M5 also as long as keepalive flag is in ncs.conf. To reiterate configuration setting, this flag '<keepalive>true</keepalive>' must be configured in ncs.conf.if keepalive-timeout is provided, the session will be closed by this time valueif keepalive-timeout is not provided, the session will be close in 3600 sec.Again, this settings works fine in 4.0 M5 Thanks,LinhAs written, keep-alive is supported, but it was officially rejected by NSO team to document it as CNC installation guidelines, therefore not included in CNC and was not included in testing - therefore it is not the current solution. Team still blocked and waiting for a solution from NSO team for this issue.Hi Liran,ncs.conf file has many configurations and it is really part of the platform. It does not make sense for us/the CFP team to keep repeating the documentation.Thanks,NipaPlatform provide a keep-alive settings in ncs.conf to resolve this issue.Regards,Linh |
NSO LSA HA after switchover observation: Setup: NSO LSA L3 HA - CFS - 192.168.5.67 , 192.168.6.67 VIP 3.3.3.7 - nsoaz1/Cnc@1234NSO LSA L3 HA - RFS1 - 192.168.5.68 , 192.168.6.68 VIP 4.4.4.7 - nsoaz1/Cnc@1234NSO LSA L3 HA - RFS2 - 192.168.5.69 , 192.168.6.69 VIP 5.5.5.7 - nsoaz1/Cnc@1234Hi team,Kindly suggest on below points.Observation 1:After NSO LSA L3 HA (CFS+RFS) Switchover from AZ1 to AZ2, CRUD operations accepted only after executed below commands.request cluster remote-node rfs-1 ssh fetch-host-keysrequest cluster remote-node rfs-2 ssh fetch-host-keysrequest devices fetch-ssh-host-keysrequest devices sync-fromShow cluster device notification status goes from up to - state.Observation 2:NSO allows changing Circuit style Resource pool . But, receiving attached error while trying auto bidirectional association id during CS policy creationObservation 3:No change made to color pool association. But after NSO LSA L3 HA (CFS+RFS) Switchover, new CS policy creation with auto color edits existing CS policy that was created with auto color pool.Same observation for disjoint also. | Hi Ajitha.Lets schedule a session to further investigate/validate observed behaviors.Thanks,AbeDid a session with Ajitha and confirmed the following cli commands are necessary after failover (observation 1):1. request cluster remote-node * ssh fetch-host-keys2. request devices fetch-ssh-host-keys3. request devices sync-fromFor observations 2 and 3, dry run error was avoided when triggering failover using ncs stop/start, instead of disabling HA (and not re-enabling HA) from the primary node.We did observe that after successful failover between primary and secondary nodes, applying CS SR policy shows inconsistent behavior where the dry-run values for color, disjoint and bi-directional fields where but was .I suspect some issue from the UI side and Ajitha will reach out to UI team and verify issue.Did a session with Ajitha and confirmed the following cli commands are necessary after failover (observation 1):1. request cluster remote-node * ssh fetch-host-keys2. request devices fetch-ssh-host-keys3. request devices sync-fromFor observations 2 and 3, dry run error was avoided when triggering failover using ncs stop/start, instead of disabling HA (and not re-enabling HA) from the primary node.We did observe that after successful failover between primary and secondary nodes, applying CS SR policyshows inconsistent behavior where the dry-run values for color, disjoint and bi-directional fields wherebut was.I suspect some issue from the UI side and Ajitha will reach out to UI team and verify issue. |
Provisioning L3/L2 vpn services throws illegal reference from NSO UI but same service payload works from ncs_cli: Hi Janaki,As discussed over Webex call, as part of this cdets - CSCwe53683 changes I am hitting below error when provisioning service from NSO UI.The same service payload when loaded and merged from ncs_cli works fine without any validation error.I am opening a JIRA ticket to resolve this discrepancy between NSO UI and ncs_cli.So, from Drop10 TSDN image onwards, we need to first create route-policy that will auto-create route-profile-identifiers.Services referring to this route-policy and route-profile identifiers will allow provisioning only if these entities are pre-existing in NSO and CNC.Tried to create route-policy first and then service provisioning from nso UI works fine.NSO logs have been collected and posted in box location - Thanks,Gomathi. | Attaching payloads with vpn profiles, route-profile-identifiers, l3vpn service all in one single payload that worked on ncs_cli without any error. Hi Gomathi,The payload is working for me in the UI too similar to cliThanksSahithiVerified that NSO UI and NSO CLI are working consistently in use case where1. Load RP (without routing-profile-indetifiers)2. Load Service3. Error is seen "Illegal Ref --"Attached verification screenshots.Resolution Notes:> When the service and the route-policy is loaded at the same time without creating routing-profile-identifiers, user will see an Illegal Ref Error.> This behavior comes from CDETS CSCwe53683 (VPN profiles are not auto created like cnc 4.x).> User will have to modify any payloads that manually create the routing-profile-identifier and instead first create the route-policies, NSO will auto-create identifiers and then load the service.Please let us know if we can assist further.The validation error was displayed from UI but not from ncs_cli when Janaki and me tried to load the payload and commit. @Janaki - can you confirm that we were able to commit the full payload during debugging?Showed the output of "show | compare" to Sahithi yesterday where all config changes were accepted to be pushed to device from ncs_cli.Shared the NSO setup details to Janaki during debugging the issue. Not sure how it got fixed on ncs_cli as well after that.I have shared the NSO logs with all the transactions performed. Hope it has the trace logs of the commit performed with full payload as reference point. |
phased provisioning with no networking: We are using phased provisioning for migrating devices in our scale setup. From TSDN 5.0 to TSDN 6.0 Drop 10. we need options in the xml payload for using the option no-networking. <action-name>migrate</action-name> <variable> <name>new-ned-id</name> <expr>/packages/package/component/ned/cli/ned-id</expr> </variable> I tried a new variable, it didnt work. Kindly suggest.request devices device PIOSXR-0 migrate new-ned-id cisco-iosxr-cli-7.52 no-networking | setup details 192.168.103.236admin / Ovatest123@Hi Srini,As discussed, please use the latest phased-provisioning-1.1.0 package and then try the migration with no-networking.For any empty type leaf, just give the variable name --><variable> <name>no-networking</name> </variable>Let us know if it works for you.Thanks.Suggested user to use the new phased-provisioning package to migrate devices with no-networking |
Not able to provision ELAN/ETREE-ODN services, existing route-policies are added even after deleting.: Hi-Not able to provision ELAN/ETREE-ODN services, existing route policies are added in the provisioning even after deleting.Tried to create the ELAN-ODN service with route-policy 350, but the provisioning is not successful ; it's adding 450 route-policy which was created sometime back ; deleted from devices ; NSO also, still it's showing on the provisioning.Thu Apr 21 16:32:57 IST 2022:DEBUG: << " <error-path xmlns:l2vpn-ntw="urn:ietf:params:xml:ns:yang:ietf-l2vpn-ntw">/l2vpn-ntw:l2vpn-ntw/l2vpn-ntw:vpn-services/l2vpn-ntw:vpn-service</error-path>"Thu Apr 21 16:32:57 IST 2022:DEBUG: << " <error-message>External error in the NED implementation for device xrd-2: Thu Apr 21 11:02:34.097 UTC "Thu Apr 21 16:32:57 IST 2022:DEBUG: << " "Thu Apr 21 16:32:57 IST 2022:DEBUG: << "% Failed to commit one or more configuration items during a pseudo-atomic operation. All changes made have been reverted. "Thu Apr 21 16:32:57 IST 2022:DEBUG: << " !! SEMANTIC ERRORS: This configuration was rejected by "Thu Apr 21 16:32:57 IST 2022:DEBUG: << "!! the system due to semantic errors. The individual "Thu Apr 21 16:32:57 IST 2022:DEBUG: << "!! errors with each failed configuration command can be "Thu Apr 21 16:32:57 IST 2022:DEBUG: << "!! found below. "Thu Apr 21 16:32:57 IST 2022:DEBUG: << " "Thu Apr 21 16:32:57 IST 2022:DEBUG: << " "Thu Apr 21 16:32:57 IST 2022:DEBUG: << "! "Thu Apr 21 16:32:57 IST 2022:DEBUG: << "extcommunity-set opaque COLOR_350 "Thu Apr 21 16:32:57 IST 2022:DEBUG: << " 350 "Thu Apr 21 16:32:57 IST 2022:DEBUG: << "end-set "Thu Apr 21 16:32:57 IST 2022:DEBUG: << "! "Thu Apr 21 16:32:57 IST 2022:DEBUG: << "!!% Policy uses policy . must be defined before can be attached. "Thu Apr 21 16:32:57 IST 2022:DEBUG: << "route-policy bgp_in "Thu Apr 21 16:32:57 IST 2022:DEBUG: << " apply SET_COLOR_EVPN_MP_service_RP-L2NM-ODN-xrd-2-350 "Thu Apr 21 16:32:57 IST 2022:DEBUG: << " apply SET_COLOR_EVPN_MP_service_RP-L2NM-ODN-xrd-2-450 "Thu Apr 21 16:32:57 IST 2022:DEBUG: << " pass "Thu Apr 21 16:32:57 IST 2022:DEBUG: << "end-policy "Thu Apr 21 16:32:57 IST 2022:DEBUG: << "! "Thu Apr 21 16:32:57 IST 2022:DEBUG: << "!!% Policy uses policy . must be defined before can be attached. "Thu Apr 21 16:32:57 IST 2022:DEBUG: << "route-policy SET_COLOR_EVPN_MP_service_RP-L2NM-ODN-xrd-2-350 "Thu Apr 21 16:32:57 IST 2022:DEBUG: << " if rd in (100.100.100.116:12345) then "Thu Apr 21 16:32:57 IST 2022:DEBUG: << " set extcommunity color COLOR_350 "Thu Apr 21 16:32:57 IST 2022:DEBUG: << " endif "Thu Apr 21 16:32:57 IST 2022:DEBUG: << "end-policy "Thu Apr 21 16:32:57 IST 2022:DEBUG: << "! "Thu Apr 21 16:32:57 IST 2022:DEBUG: << "!!% Policy uses policy . must be defined before can be attached. "Thu Apr 21 16:32:57 IST 2022:DEBUG: << "end</error-message>"Thu Apr 21 16:32:57 IST 2022:DEBUG: << " </error>"Thu Apr 21 16:32:57 IST 2022:DEBUG: << "</errors>" | Please take a look, Setup details belowCW- 172.24.97.142 XRD VM- 172.27.226.62Devices - 192.168.5.17 - 192.168.5.24Hi Ragesh,We are not able to login to the setup CW- 172.24.97.142 .Please suggest.Also please provide the payloads used.Thanks,Nishad Subair.Hi Nishad,We are able to login the CW setup with 172.24.97.142 admin/Public123!Payload attached which we used for the testing. Please take a look. Hi Ragesh,We are still not able to login to the setup CW- 172.24.97.142 .We are getting 'Connection closed by remote host'.Please suggest.Thanks ,NishadHi Nishad,Are you accessing Crosswork UI or ssh session?I have mentioned both the credentials below ; we don't see any issue on accessing the crosswork UI ; ssh.Currently the setup is not in problem state, but you can re-create the issue after creating the multiple route-policies and attached to the services.Crosswork UI can access with admin/Public123!SSH can access with cw-admin/Cwork123!Hi Ragesh,I am able to login successfully now.Please suggest that 172.24.97.147 is the correct NSO.Regards,Nishad Subair.Yes Nishad, 172.24.97.147 is the NSO we used on the Setup. |
CNC: NCS: 6.1.2tmtc-6.0.0-nso-6.1.2.20230725.0caa29b7.tar.gzdlm-6.0.0-nso-6.1.2.20230725.9da7ff81.tar.gz1) We have re-install devices to 7.8.2, 7.9.2 and 7.10.1.352) Once devices are installed, we have added them in CW via CSV3) Now I see that NSO state in DLM is empty.4) devices are shown added in NSO. 5) Now perform sync from on 10.56.116.25 - XTC6) Observed that device is not registered.7) tried to /etc/init.d/ncs stop. This command was hanging.logs: 10.56.116138: /home/nso/tsdn-6.0.0-nso-6.1.2.20230725.4df2068e/data_082823_213637.tgznso/Public1234!Now I have power off and power on. perform : sudo NCS_RELOAD_PACKAGES=force /etc/init.d/ncs restartnow ncs is up. But wanted to know why this issue came | Hi ,We checked the log and didn't find any relevant information to identify the issue why it happened.We need some environment o reproduce this issue. Let us know where we can reproduce this issue, |
Need help in configuring NSO HA with different time zones: Hi team,Brought up NSO L3 HA. Would you please help in configuring the secondary node NSO HA in different time zone.Note: For Crosswork, we have a field in installation file to mention the time zone. trying to check if there is similar way for NSO. | Hi Ajitha,Let's schedule a session to sync up and discuss.Thanks,AbeHad a session with Ajitha and helped her configure NTP config on all nodes. This is a primary requirement in LSA (HA) so that all nodes belonging to the cluster are configured to use UTC and are in sync despite having different local time due being situated in different timezones.Issue is fixed now and nodes are ntp synced. Moving ticket to resolved.Thank you,AbeHad a session with Ajitha and helped her configure NTP config on all nodes. This is a primary requirement in LSA (HA) so that all nodes belonging to the cluster are configured to use UTC and are in sync despite having different local time due being situated in different timezones.Issue is fixed now and nodes are ntp synced. Moving ticket to resolved.Thank you,Abe |
On ncs 5.4.6, clean up of service is leading to zombie: we create the service in single transaction ( stack mode ). I have observed that NSO responds with ok and then config is pushed to device which is contrary to previous functionality on 5.4.2 where only after config is pushed to device, nso responds with ok. Also, after cleaning up the service, we have observed that service stays as zombie. Below is the ip and creds of NSO, attached payload and command to create ; cleanup service IP: 10.64.96.124 ( nso / Cwork123! ) command to create service : netconf-console --host=10.64.96.124 -u nso -p Cwork123! --port=2022 --rpc=payload.xml command to clean up service: tm-tc-actions cleanup service Crosswork_1001 no-networking false | Hi Raja,I logged on your setup and saw you did not configure nacm user correctlynso@ncs% show nacmread-default permit;write-default permit;exec-default permit;groups { group ncsadmin { user-name [ private ]; } group ncsoper { user-name [ public ]; }Please correct it according to the wiki Also zombie that I saw is from tm-tc packagenso@ncs> show zombieszombies service /cisco-tm-tc-fp-internal:tm-tc pending-deleteWe are NOT the owner of the TM-TC package. Please contact the owner of this package for precise steps/command to cleanup the zombieThanks,LinhHi Linh, I added the following nacm config set nacm groups group ncsadmin user-name nsoi still see the same issue. Can you please test same usecase on a clean setup with proper nacm permissions and confirm.I see that it was tested on corrupted setup with existing zombies.We faced similar issue of plan not-reached and zombies not back tracking correctly when nacm permissions are not set correctly.ThanksSahithiHi Raja,I was able to cleanup zombie by going down to device levelnso@ncs% request tm-tc-actions cleanup service Crosswork_1001 device 10.64.96.123 no-networking truesuccess truedetailCleaning up TMTC service: Crosswork_1001 Removed all plan components Removing zombie service: /ncs:zombies/ncs:service{"/cisco-tm-tc-fp-internal:tm-tc[name='Crosswork_1001'][node-name='10.64.96.123']"} Removed zombie service Removed service oper Removed side-effects Removed side-effects Removed kickers Removed kickers Cleanup Successful for Crosswork_1001nso@ncs% run show zombies% No entries found.Please let me know if I can close the ticketRegards,LinhHi LinhUp on running the command for first time, we can observe that there is a zombie with pending-delete. After running the command again, the zombie is getting removed. please find screenshot in attachments. I have created another setup, please use it to debug10.104.127.17 nso / Cwork123!Hi Raja,As the rule of thumb, cleanup action should be used as the last resort. These are steps you should follow1. Delete the service2. If zombie stay behind then do a cleanup action.It seems to me that you perform a cleanup action without deleting the service first because I saw this warning "...Not able to retrieve diffset for zombie ..."Thanks,LinhHi Moksha,Glad the clean up worked with change . If you want me to file an RT Below details are required to file a RT:Problem statement.Expected behavior.NSO logs.Clear steps to reproduce the issue.Sample package/reproduction. Priority.Found in Version.When you provide the sample package. Please give the steps on how to reproduce the issue with it when installed locally.ThanksSahithiProblem statement : Up on cleaning up the service, there is a zombie created despite config delete is successful. When clean-up is retried, the zombie is getting cleared. Expected behaviour: There should not be any zombie if device config delete is successful NSO logs : Clear steps to reproduce the issue: Install the following functional pack on ncs version 5.4.6. - Set the following commands on ncs_cli 1.set cisco-tm-tc-fp:cfp-configurations dynamic-device-mapping cisco-iosxr-cli-7.33:cisco-iosxr-cli-7.33 python-impl-class-name tm_tc_multi_vendors.IosXR2.set cisco-tm-tc-fp:cfp-configurations stacked-service-enabledRun the following command to create the service ( the device key is 10.64.96.113 in given payload, change it as required ) - netconf-console -u nso -p Cwork123! --port=2022 --rpc=payload.xmlRun the following command to clean up the service ( the device key is 10.64.96.113 in given command, change it as required ) - tm-tc-actions cleanup service Crosswork device 10.64.96.113 no-networking falseShow zombies should display the zombie created due to cleanupRun again the same cleanup command Show zombies output should be empty, refer to attached screenshotSample package/reproduction : Priority :Found in Version : 5.4.6 Hi Moksha,The package you have given is with tm tc functionality. NSO team would not understand the tm-tc functionality. They will not be able to debug the clean up action. This ticket would be rejected if I file with FP specific logic. is something which is generic just for the NSO i.e remove all the TM-TC code, isolating just the issue with NSO here.Please create a sample package with example service and action which is replicates this issue.You can find example sample packages under -> nso-5.4.6/examples.ncs/getting-started/developing-with-ncsClean up is something which is used as last resort.ThanksSahithiHi Could you please answer the question by Sahithi?ThanksNipaPlease reply to Sahithi's question above.Thanks,NipaEmail from Moksha on 04/28+ TeamHi Sahithi / Nipa,Is there a way we can go ahead with tm-tc package for now, we never tried this and it might take some more time to understand and build the sample package.Regarding cleanup, we do it only when the devices gets removed from our application, which is not frequent.Regards,MokshaHi Moksha,Do you have a queue on RT system to file a defect? if so, please go ahead and file it. If not, let me know I will try and get you an access.Thanks,NipaHi Nipa, I don't have details on how to file a RT. Please provide the link, i can try and let you know if i have access. Regarding the cleanup, i already responded on email we do it only when the devices gets removed from our application, which is not frequent. During cleanup, we removed the configuration and remove the service in single transaction. Here is the link for RTClose this since the issue is not on TSDN CFGRegards,Linh |
Permission required: Hello,Please enable access for the user sivakbal@cisco.com. I would need to check the tickets raised for SH program.Thanks,Siva. | What exactly are you requesting access for?Thanks,RegiAccess to view and create the tickets.It seems you already have access to view/create tickets, since you were able to create the current ticket?Tried to access the ticket attached here. It is not accessible. Permission denied is returned. Could you check?Gotcha, when the tickets are created. The person who creates the ticket need to add everyone who needs access to the ticket.I have added you to . Can you check if it works now?You've also been added to CNC-Group, so you should have all access now to other tickets. Just make sure to log back out and login then retry and let me knowThank you, it worked. Appreciate it.No problem. I'll go ahead and close this ticket now.Thanks,Regi |
NCS 5.5.2.3 with M4 - Reverse Diff issue: <Filed for Arun.M.G>Hi Core FP Team,NSO : 10.56.116.240 ( installed with 5.5.2.3 M4) ( credentials : nso/Public1234!)since i am facing the reverse diff issue in 5.5.2.3 M4., I am trying to follow the wiki NSO Upgrade from 5.5.2.3 to 5.5.2.7 for CNC - M4 - Core FP - Confluence Eng SJC1 (cisco.com)While trying the step 1, the command "show core-fp-release release function-pack-store build" doesnt show any output.Wanted to know if it is fine to proceed with other steps or this will block anything to upgrade to 5.5.2.7 ?Attached mail has details of the issue and the fix #44719.Reverse Diff issue:nso@ncs> request l2vpn-ntw vpn-services vpn-service L2VPN_NM_P2P_SRTE-101 get-modifications reversecli { local-node { data -flat-L2vpn L2NM-L2VPN_NM_P2P_SRTE-101-internal {service-type p2p;flat-L2vpn-p2p {pw-id 101;local-site {pe A-PE1;if-type GigabitEthernet;if-id 0/0/0/6;if-encap dot1q;vlan-id 101;sub-if-id 101;xconnect-group-name L2VPN_NM_P2P_SRTE-101;p2p-name L2VPN_NM_P2P_SRTE-101;sr-te {preferred-path { - policy L2NM-P2P-SRTE-114-119; - }}control-word no;pw-class L2VPN_NM_P2P_SRTE-101;xconnect-local-ip 192.168.0.2;xconnect-remote-ip 192.168.0.18;}remote-site {pe A-PE6;if-type GigabitEthernet;if-id 0/0/0/6;if-encap dot1q;vlan-id 101;sub-if-id 101;xconnect-group-name L2VPN_NM_P2P_SRTE-101;p2p-name L2VPN_NM_P2P_SRTE-101;sr-te {preferred-path { - policy L2NM-P2P-SRTE-119-114; - fallback disable; - }}control-word no;pw-class L2VPN_NM_P2P_SRTE-101;}} -} devices { device A-PE1 { config { interface { GigabitEthernet-subinterface {GigabitEthernet 0/0/0/6.101 {mode l2transport;description "T-SDN Interface";encapsulation {dot1q { - vlan-id 101; - } - } - } } } - l2vpn { - pw-class L2NM-EVPN-SRTE-104 { - encapsulation { - mpls { - preferred-path { - sr-te { - policy srte_c_104_ep_192.168.0.16; - fallback disable; - } - } - } - } - } - pw-class L2VPN_NM_P2P_SRTE-101 { - encapsulation { - mpls { - preferred-path { - sr-te { - policy srte_c_101_ep_192.168.0.18; - } - } - } - } - } - xconnect { - group L2NM-EVPN-SRTE-104 { - p2p L2NM-EVPN-SRTE-104 { - interface GigabitEthernet0/0/0/6.104; - neighbor-evpn { - neighbor { - evpn 2 54 53 { - pw-class L2NM-EVPN-SRTE-104; - } - } - } - } - } - group L2VPN_NM_P2P_SRTE-101 { - p2p L2VPN_NM_P2P_SRTE-101 { - interface GigabitEthernet0/0/0/6.101; - neighbor 192.168.0.18 101 { - ip-version ipv4; - pw-class L2VPN_NM_P2P_SRTE-101; - } - } - } - } - } } } device A-PE6 { config { interface { GigabitEthernet 0/0/0/6 { - description "T-SDN Interface"; + shutdown; } GigabitEthernet-subinterface { - GigabitEthernet 0/0/0/6.101 { - mode l2transport; - description "T-SDN Interface"; - encapsulation { - dot1q { - vlan-id 101; - }}} } }l2vpn {pw-class L2VPN_NM_P2P_SRTE-101 {encapsulation {mpls {preferred-path {sr-te { - policy srte_c_101_ep_192.168.0.2; - fallback disable; - }}}}}xconnect {group L2VPN_NM_P2P_SRTE-101 {p2p L2VPN_NM_P2P_SRTE-101 {interface GigabitEthernet0/0/0/6.101;neighbor 192.168.0.2 101 { - ip-version ipv4; - pw-class L2VPN_NM_P2P_SRTE-101; - }}}}} } } }</ul> }}nso@ncs>Thanks,Arun.M.G | Arun upgrade to NSO 5.5.2.7 which resovled the reverse diff issue |
NSO_LSA: Load Bootstrap Data Failure : Does not able to commit the following boostrap data post tsdn installation. The commit throws the "application communication failure"admin@ubuntu2004:~/nso-5.7.2.1-tsdn-4.0.0-M3/tsdn-lsa/tsdn-lsa-rfs/bootstrap-data$ ncs_cli -u adminUser admin last logged in 2022-03-28T06:22:47.088218+00:00, to ubuntu2004, from 172.29.104.187 using cli-sshadmin connected from 172.29.104.187 using ssh on ubuntu2004admin@ncs> configureEntering configuration mode privateadmin@ncs% unhide debugadmin@ncs% load merge SR-status-codes.xmladmin@ncs% load merge SR-internal-plan-monitor.xmladmin@ncs% load merge RSVP-TE-status-codes.xmladmin@ncs% load merge RSVP-TE-internal-plan-monitor.xmladmin@ncs% load merge rfs-custom-template-settings.xmladmin@ncs% load merge L3VPN-status-codes.xmladmin@ncs% load merge L3VPN-internal-plan-monitor.xmladmin@ncs% load merge L2VPN-status-codes.xmladmin@ncs% load merge L2VPN-internal-plan-monitor.xmladmin@ncs% load merge dispatch-map-settings.xmladmin@ncs% load merge commit-queue-settings.xmladmin@ncs% load merge bootstrap-autopopulate-dispatch.xmladmin@ncs% commitAborted: application communication failureadmin@ncs% exit | Hi Dinesh,Could you please share the setup info so we can check what's going on?Or alternatively, could you please share all the NSO logs if you can?NSO IP: 10.104.57.133 admin/Ovatest123@Hi Dinesh,I'm not able to access the NSO.But based on the sync-up session we had, we found your java-vm ran out-of-memory when loading the packages.Can you please try to either increase the memory allocation to your NSO VM, or use the NCS_JAVA_VM_OPTIONS flag to restrict the java-vm max memory usage to below system capability, i.e.:export NCS_JAVA_VM_OPTIONS=-Xmx2GYou will need to do "request packages reload" after above adjustment.Please try and let me know if this resolves the issue.Hi Linmao,Thank you for your observation. It fixed the issue when I increased the VM Memory from the resource allocation.Unfortunately " export NCS_JAVA_VM_OPTIONS=-Xmx2G" did not help me.Thanks,DineshHi Dinesh,Thanks for confirming that the issue is resolved!For the second option with theNCS_JAVA_VM_OPTIONS flag, you will need to restart NSO (<tt>sudo</tt><tt>/etc/init</tt><tt>.d</tt><tt>/ncs</tt><tt>restart-with-package-reload</tt>) for it to take effect. Sorry for missing this earlier.Please let me know if we can close this ticket.Thanks,Hi Linmao, Yes, The ticket can be closed.Thank you for looking into the issue.Thanks,Dinesh |
System installation link for installing NCS version 5.7.2.1 is removed from m3 and m4: Hi,We dont see the system installation steps for NSO 5.7.2.1 NCS version . do we have any other page to refer for the installation of NSO version?in CFP installation, it says, The following assumptions are done for given installation and verification steps :NSO is installed in System-Install mode .Please provide installation steps for 5.7.2.1Thanks,Arun.M.G | Usually we don't handle NSO installation guide. It belongs to the platform team. As your request, this is the link Hi Linh,Thanks, May i know who is handling the confluence updates.? on which category to raise jira ticket , if we need to get the confluence page updated?can this be redirected to the respective team?we had this page till 4.0.0 M2.but not in M3 and M4.Hi Arun,These pages are for internal use ONLY. We decided to remove them because we don't want to update in every releaseThanks,Linh |
Unable to set RON default controller using RESTCONF when its value is empty: Hi,During fresh install and when RON default-controller is empty,When I try to send RESTCONF PATCH request to default-controller then NSO responds with below error message,"ietf-restconf:errors": { "error": [ { "error-type": "application", "error-tag": "invalid-value", "error-path": "/cisco-ron-cfp:ron/default-optical-controller", "error-message": "patch to a nonexistent resource" } ] } } Whereas , after setting default-controller from NSO , I am able to change/set using PATCH RESTCONF request.From CNC we need to set this value when the default-controller value is empty as well.Kindly help us in fixing this issue.Thanks,Naveen | Hi Mohit,As per our web-ex discussion , the details are as follows,The path which I tried is below,http://<tt>nso.host</tt>:<tt>nso.port</tt>/restconf/data/cisco-ron-cfp:ron/default-optical-controllerMethod : PATCHBody: { "cisco-ron-cfp:default-optical-controller": "onc-real-new"}Response:"ietf-restconf:errors": { "error": [ { "error-type": "application", "error-tag": "invalid-value", "error-path": "/cisco-ron-cfp:ron/default-optical-controller", "error-message": "patch to a nonexistent resource" } ] } } Method : POST Response:{ "ietf-restconf:errors": { "error": [ { "error-type": "application", "error-tag": "malformed-message", "error-path": "/cisco-ron-cfp:ron/default-optical-controller", "error-message": "unknown element: default-optical-controller in /cisco-ron-cfp:ron/cisco-ron-cfp:default-optical-controller/cisco-ron-cfp:default-optical-controller" } ] }}Hi Naveen,From your details above it seems like you are using wrong api url and request body. Could you please try the below requests and let me know if it works for you. I tested these on my setup with fresh install when there is no default optical controller present.Thanks,Mohit BUrl : Request Body:{"cisco-ron-cfp:ron":{"default-optical-controller":["onc-real-new"]}}Response status code returned: 204 No ContentUrl : Request Body:{"default-optical-controller":["onc-real-new"]}Response status code returned: 201 CreatedAfter discussion on webex, we were able to resolve the issue. kindly refer ticket notes for more details. |
Aborted: application communication failure: Operation failed while performing commit command as part of:Configure Bootstrap dataLoad merge the following files from config to activate notificationsAfter running commit I get the following:Aborted: application communication failure | Hello, please attach the files that caused this error, and let us know how to access the setup where this error is seen. Thank you.10.56.116.162 nso/Public1234!I just checked your system and most of packages are not upnso@ncs> show packages package oper-status PACKAGE PROGRAM META FILE CODE JAVA PYTHON BAD NCS PACKAGE PACKAGE CIRCULAR DATA LOAD ERRORNAME UP ERROR UNINITIALIZED UNINITIALIZED VERSION NAME VERSION DEPENDENCY ERROR ERROR INFO---------------------------------------------------------------------------------------------------------------------------------------cisco-aa-service-assurance - - - X - - - - - - -cisco-flat-L2vpn-fp - - - X - - - - - - -cisco-flat-L2vpn-fp-internal - - - X - - - - - - -cisco-flat-L3vpn-fp - - - X - - - - - - -cisco-flat-L3vpn-fp-internal - - - X - - - - - - -cisco-ios-cli-6.77 X - - - - - - - - - -cisco-iosxr-cli-7.38 X - - - - - - - - - -cisco-iosxr-nc-7.3 X - - - - - - - - - -cisco-iosxr-nc-7.315 X - - - - - - - - - -cisco-iosxr-nc-7.4 X - - - - - - - - - -cisco-iosxr-nc-7.5 X - - - - - - - - - -cisco-rsvp-te-fp - - - X - - - - - - -cisco-sr-te-cfp - - - X - - - - - - -cisco-sr-te-cfp-internal - - - X - - - - - - -cisco-tsdn-core-fp-common - - - X - - - - - - -core-fp-common - - - X - - - - - - -core-fp-delete-tag-service - - - X - - - - - - -core-fp-plan-notif-generator - - - X - - - - - - -custom-template-utils - - - X - - - - - - -flat-l2vpn-multi-vendors - - - X - - - - - - -flat-l3vpn-multi-vendors - - - X - - - - - - -ietf-l2vpn-nm - - - X - - - - - - -ietf-l3vpn-nm - - - X - - - - - - -ietf-te-fp - - - X - - - - - - -lsa-utils - - - X - - - - - - -resource-manager X - - - - - - - - - -rsvp-te-multi-vendors - - - X - - - - - - -sr-te-multi-vendors - - - X - - - - - - -I checked python version. The system have a wrong python3 version. Minimum version is 3.8nso@abendavi-nso1-cisco:~$ python3Python 3.6.9 (default, Jul 17 2020, 12:50:27) on linuxType "help", "copyright", "credits" or "license" for more information.Please correct your python according the wiki Closing ticket since Python version was noted to be incorrect when ticket was created.Python error identified. Closing ticket. |
Please provide access : ELAN Device Configuration Reference: E-TREE Device Configuration Reference: Model Reference: | Can you double check if you're signed into github? Please let me know if that was issue or if you still don't have access.Thanks,Regi |
L3VPN as part of core FP : Question 1:Kindly suggest, If L3VPN Functional pack location will be moved from example packages folder to Core packages folder from this release (NSO 6.0 - TSDN 5.0 - M4). Also, Please suggest if there is any impact/changes with respect to its consumption in CNC.Question 2:With respect to the New VPN model changes, above page gives the Payload Difference. Kindly suggest if there is any Device config level changes or updation( IOS XR . Do we have any wiki (similar to above payload wiki) to track the changes/updation. | Hi AjithaIETF-L3VPN-NM is still an example package in this release. It will be moved to core packages in future release.There are no changes with respect to the device level config. The device config remains the same.Thanks,NikhilProvided the required information to the user. |
Transport Slice: Connectivity Type and global-rd Clarification: Hi,Need a clarification on Connectivity Type and global-rd.When connectivity type is set to "any-to-any" and global-rd set to "auto",can we add "hub-rt" in transport slice? | Yes, RD (route-distinguisher) and RT (route-target) are different. "global-rd" is only applicable for configuring RDs; where, "hub-rt" is used to configure RTs for hubs.Thanks,RegiThanks Reginald |
Ingress/Egress QoS Override: Hi,I'm developing slice provisioning by forming yang model in M3.How do I set the value "No Override" or "Not Set" or "Node" using the model?Which attribute has to be used? | For Ingress QoS Override and Egress QoS Override, we have 3 values.1. No Override2. Not Set3. NoneHow do i set one of these values to an attribute?Hi Magesh,I'm not sure I understand your question. Are these attributes device configurations? What exactly are you trying to override?Thanks,RegiHi,I'm referring to the QoS: "cisco-nss:qos-policy"Ingress and Egress QoS override (if set) will apply these QoS profiles specified on the SDP interface instead of the QoS profiles referenced in the catalog. Currently we don't have QoS under SDPs in model. HI Magesh,That is correct. The QoS override under SDP is currently not implemented. That feature is more of a stretch goal and may or may not be implemented for 5.0.Thanks,RegiThanks Reginald |
"Loopback101\" is an invalid value when create a slice use loopback interface type: On CNC UI, create a slice use Interface Type = Loopback, it failed with the following error:[{"Message":"invalid value for: ac-tp-id in /ietf-nss:network-slice-services/ietf-nss:slice-service[ietf-nss:service-id='SliceL3Ded523Lpback']/ietf-nss:sdps/ietf-nss:sdp[ietf-nss:sdp-id='5']/ietf-nss:attachment-circuits/ietf-nss:attachment-circuit[ietf-nss:ac-id='6']/ietf-nss:ac-tp-id: "Loopback0" is an invalid value.","nsoResponse":"invalid value for: ac-tp-id in /ietf-nss:network-slice-services/ietf-nss:slice-service[ietf-nss:service-id='SliceL3Ded523Lpback']/ietf-nss:sdps/ietf-nss:sdp[ietf-nss:sdp-id='5']/ietf-nss:attachment-circuits/ietf-nss:attachment-circuit[ietf-nss:ac-id='6']/ietf-nss:ac-tp-id: "Loopback0" is an invalid value."}]From NSO UI, it gets the similar error when adding an SDP node.Screenshots attached.Is Loopback not supported for Slice or it is a product bug?Build combo:CW 220, CDG 247, COE 236, CAT 231, NSO6.1+TSDN M5 | Hi Crystal,This is a bug in the model. Please file a CDETs.Thanks,RegiThanks Reginald. CSCwe11532 is opened to track the issue.-CrystalFixing it in the CDET filed. |
too many open files - scale setup: We have LSA scale setup with 25K devices with 3 RFS, 1 CFS, with 160K VPN services. We are sending REST API to provision more VPN services. We have set the files limit as specified in the install instruction. However while creating services, we get this critical error message and NCS is stopped.ncs.log:<CRIT> 6-Jan-2023::03:23:23.995 scale-nso2-CFS-133 ncs: - Writing state file failed: /var/opt/ncs/state/global.data: too many open files (emfile)ncs.log:<CRIT> 6-Jan-2023::03:23:24.037 scale-nso2-CFS-133 ncs: - Writing state file failed: /var/opt/ncs/state/global.data: too many open files (emfile)For such a scale setup, what is the recommended no of files value that should be setup. We are facing this issue for the second time in 3 days.setup: 172.20.63.133cnctest/Ovatest123@ | Hi Rama,Please update limits in file to :soft nproc 100000hard nproc 100000soft nofile 100000hard nofile 100000soft core unlimited- nofile 100000we have used above settings in our scale lab.ThanksPriyankaWe are hitting this issue more often. We are provisioning ELAN service with 5 end points. Even 100K limit is not enough. I suspect there could be memory leak.Can you check this setup. Out of file descriptors for accept() - process limit reached# lsof | wc -l209011# lsof | grep ncs | wc -l8522#<CRIT> 9-Jan-2023::12:48:49.653 scale-nso2-CFS-133 ncs: - Out of file descriptors for accept() - process limit reached<CRIT> 10-Jan-2023::05:33:29.469 scale-nso2-CFS-133 ncs: - Daemon ncs-dp-2730-ietf-l3vpn-nm:main:9 timed out<CRIT> 10-Jan-2023::06:17:47.598 scale-nso2-CFS-133 ncs: - Out of file descriptors for accept() - process limit reached<CRIT> 10-Jan-2023::06:17:47.599 scale-nso2-CFS-133 ncs: - Writing state file failed: /var/opt/ncs/state/global.data: too many open files (emfile)<CRIT> 10-Jan-2023::09:59:36.011 scale-nso2-CFS-133 ncs: - Out of file descriptors for accept() - process limit reached<CRIT> 10-Jan-2023::14:54:51.177 scale-nso2-CFS-133 ncs: - Out of file descriptors for accept() - process limit reached<CRIT> 11-Jan-2023::03:28:11.120 scale-nso2-CFS-133 ncs: - Out of file descriptors for accept() - process limit reached<CRIT> 11-Jan-2023::05:33:01.156 scale-nso2-CFS-133 ncs: - Out of file descriptors for accept() - process limit reachedHi Rama,I checked your scale NSO :Your max user process is 4096 :$ ulimit -a core file size (blocks, -c) unlimiteddata seg size (kbytes, -d) unlimitedscheduling priority (-e) 0file size (blocks, -f) unlimitedpending signals (-i) 531115max locked memory (kbytes, -l) 64max memory size (kbytes, -m) unlimitedopen files (-n) 200000pipe size (512 bytes, -p) 8POSIX message queues (bytes, -q) 819200real-time priority (-r) 0stack size (kbytes, -s) 8192cpu time (seconds, -t) unlimited virtual memory (kbytes, -v) unlimitedfile locks (-x) unlimitedIn my NSO it is : admin1@NOS5-172-73:~$ admin1@NOS5-172-73:~$ ulimit -a core file size (blocks, -c) 0data seg size (kbytes, -d) unlimitedscheduling priority (-e) 0file size (blocks, -f) unlimitedpending signals (-i) 1031601max locked memory (kbytes, -l) 65536max memory size (kbytes, -m) unlimitedopen files (-n) 100000pipe size (512 bytes, -p) 8POSIX message queues (bytes, -q) 819200real-time priority (-r) 0stack size (kbytes, -s) 8192cpu time (seconds, -t) unlimitedvirtual memory (kbytes, -v) unlimitedfile locks (-x) unlimitedPlease update that value as well.Do following steps : sudo vi /etc/sysctl.confkernel.pid_max = 4194303To effect changes to take place :sudo sysctl -pPlease try after above and let me know if you see still see issue.ThanksPriyankaHi Priyanka,Am seeing below error while trying these steps. Am i missing some thing ?$ sudo vi /etc/sysctl.conf$ sudo sysctl -pvm.swappiness = 10sysctl: cannot stat /proc/sys/vn/nfs_cache_pressure: No such file or directorykernel.pid_max = 4194303Thanks,Sreedhar.Hi Sreedhar ,I was successfully able to update the max processes limits on your NSO :$ $ ulimit -a core file size (blocks, -c) 0data seg size (kbytes, -d) unlimitedscheduling priority (-e) 0file size (blocks, -f) unlimitedpending signals (-i) 531115max locked memory (kbytes, -l) 64max memory size (kbytes, -m) unlimitedopen files (-n) 200000pipe size (512 bytes, -p) 8POSIX message queues (bytes, -q) 819200real-time priority (-r) 0stack size (kbytes, -s) 8192cpu time (seconds, -t) unlimitedmax user processes (-u) 200000virtual memory (kbytes, -v) unlimitedfile locks (-x) unlimited$ $ Please run your tests and let us know if you still see issue.ThanksPriyanka |
Permission to view the pages: Not able to view the pages of below ,Permission denied. Please allow permission. | Hi Magesh,Please try now.Thanks,Regi |
NSO CFP - 5.0 - M4 'container policy-definitions' was commented from new yang: ietf-routing-policy.yang: From cisco-tsdn-core-fp-common folder, a new yang file was added "ietf-routing-policy.yang" the policy-definitions was commented out therefore our compilation failed.Please see the attachment for line# and details.From grouping apply-policy-group {} ...leaf-list import-policy { type leafref { path "/rt-pol:routing-policy/rt-pol:policy-definitions/" + "rt-pol:policy-definition/rt-pol:name"; require-instance true; }and leaf-list export-policy { type leafref { path "/rt-pol:routing-policy/rt-pol:policy-definitions/" + "rt-pol:policy-definition/rt-pol:name"; require-instance true; }where policy-definitions was used under the leafref but the container policy-definitions was under commented block.Please check.Thanks and regards,-Quy | Hi Quy,Grouping apply-policy-group in ietf-routing-policy.yang is not used in the code. So ideally should not be getting a compilation error.But as you mentioned , ODL compiler showed compilation error regarding the grouping apply-policy-group having the leafref where the policy-definitions and policy-definition was used in a path.We will take care of this as part of the next release.Regards,Nishad Subair |
NSO CFP - 5.0 - M4 ietf-l3vpn-ntw.yang removed the "uses vpn-common:service-status;" from container vpn-services: Regarding ietf-l3vpn-ntw.yang:under container vpn-services {} the "uses vpn-common:service-status;" was removed - our compilation failed without this service-status.We have uncommented for now.Was this commented out by mistake or meant to be?Please see the block of 'container vpn-service' from the attached file.Thanks and regards,-Quy | Hi Quy,We are not using vpn-common:service-status.Please suggest the purpose of the usage and if any functionality is depended on it.Regards,Nishad Subair. |