input
stringlengths 48
5.67k
| output
stringlengths 0
15.3k
|
---|---|
slo-sle-template description shows "exists" if left blank : When slo-sle-template is created with blank, it shows "exists". Is it expected?Attaching the screenshot. | Hi Kanchan ,Please provide the set up info where this is reproducible.Also please provide the payload/steps as well as i am not able to replicate the same.Regards,Nishad SubairHi Kanchan,Please try without sending the attribute <template-description></template-description> in the payload if value is not being set.Regards,Nishad Subair.Hi Nishad,This is part of payload, so if value is not given then UI should be able to handle the blank. Thanks,KanchanRaised RT-50045 with NSO UI team for the issue.Hi Kanchan,RT has been resolved and the fix is available in the NSO build : 6.1_230309.150845399.3f9c3d6ad347.Please verify.Thanks And Regards,Nishad Subair. |
NSO CFP - 5.0 - M2 - payload IETF Network Slice Service failed for L2: Was using payloads under Network Slice Services, found some name and contents mismatched:IETF-NSS-L3-ANY-TO-ANY-SHARED.xmlIETF-NSS-L3-HUB-SPOKE-DEDICATED.xmlgot some failure when using the IETF-NSS-L2-ANY-TO-ANY-SHARED.xml due to the missing Resource Pool Notes: Reginald was helping to resolve this ticket - the doc was fixed as well. | Issue was resolved as per Quy's comment. We should really add L2 resource pools are part of init-data |
M2 and M3 yangmodel mismatch: Hi,I'm developing the code for transport slice provisioning. I have formed yang model in M2 version. Now M3 also came up. Some of the attributes in M2 has been changed in M3.M2:<div class='table-wrap'><table class='confluenceTable'><tbody><tr><td class='confluenceTd'> </td><td class='confluenceTd'> +--rw ietf-nss-cisco:vpn-targets</td></tr><tr><td class='confluenceTd'> </td><td class='confluenceTd'> </td><td class='confluenceTd'> +--rw ietf-nss-cisco:vpn-target* </td></tr></tbody></table></div>M3:<div class='table-wrap'><table class='confluenceTable'><tbody><tr><td class='confluenceTd'> </td><td class='confluenceTd'> +--rw cisco-nss:vpn-targets</td></tr><tr><td class='confluenceTd'> </td><td class='confluenceTd'> </td><td class='confluenceTd'> +--rw cisco-nss:vpn-target* </td></tr></tbody></table></div>Is it a permanent change? Also, it'll be difficult for me to change the model every time the new release comes. | Hi Magesh,Yes, this change is permanent. We have changed ALL of the namespace for the cisco augmentations for the IETF models in order to follow more closely to the yang standards.Thanks,Regi |
CAT/NSO works incorrectly when 2 Circuit style policy created with same headend tailend color: Tested in build CW 218 NSO 6.1 M5+Setup - CW - 10.195.165.70 - admin/Cnc@1234 - cw-admin/Ovatest123@NSO - 10.195.165.75 - xrd1/xrd1Created a Circuit style policy and verify the policy details and map view in TE page.Now create another Circuit style policy with same Headend/Endpoint/color but all other values are different.In device, configuration of first CS policy is overwritten with second CS policy information but CNC/NSO holds both CS policy.NSO check sync fails for the first CS policy. - NSO CFP OBSERVATION2 different CS policy in CAT UI Provisioning NSO page cross launches to same CS policy in TE page.Among its corresponding SR policies, if a policy forward works , reverse throws error "unable to locate policy" and vice versa.Defect CSCwe10254 raised for the same. | Hi, there is a uniqueness constraint on SR-TE Policies in general.If you refer to our SR-TE Detailed Wiki () you can see there is a link on "SR-TE" as shown below: If you click on the "SR-TE" (), it will take you to a overview of SR-TE with a slide deck describing SR-TE constraints and behavior. If you go to slide 10, you will see: Here we can see, at a given head-end, an SR-TE Policy is uniquely identified by<ol>colorendpoint</ol>As Circuit Style SR-TE Policy is simply a bidirectional pair of SR-TE Policies, it follows the same constraints as SR-TE Policies.As such, it is invalid to create SR-TE Policies with same head-end, color, and endpoint. This applies to CS SR-TE Policies as well. I hope this helps answer your question.Thanks,Isaac KimDocumentation has been updated to reflect this condition.Documentation Updated. |
Slice Provisioning Issue: Hi,While provisioning a slice, getting below error,{"nsoResponse":"[{"Context":"[name = BGP AS Validation, message = BGP routing process is not configured on the device state = {'Endpoint': 'xrv9k-23_SDP-1-1', 'Keypath': '/cisco-flat-L3vpn-fp-internal:flat-L3vpn{NSS-Dedic-200-internal xrv9k-23_SDP-1-1}'}]","Category":" validation","Message":"/flat-L3vpn{NSS-Dedic-200-internal xrv9k-23_SDP-1-1}: STATUS_CODE: TSDN-L3VPN-415","Severity":" ERROR","StatusCode":"/flat-L3vpn{NSS-Dedic-200-internal xrv9k-23_SDP-1-1}: TSDN-L3VPN-415","Reason":" BGP routing process is not configured on the device"}]","status":"failure"}payload attached.Could you please help me? | Hi Magesh,You'll need to pre-configure the BGP on the XR device as a requirement for slicing, since slicing will pick up the BGP process from the XR device.Thanks,RegiHi Reginald,How do we configure that? can you pls give me any reference/material to follow?ThanksMageshI'm assuming you're using XR CLI NED, you can use the following command:<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"><pre>set devices device PIOSXR-0 config router bgp bgp-no-instance 100</pre></div></div>The above is day0 and only need to configured once per device.Thanks,RegiThanks Regi |
6.0 getting access denied on load merge operation : Installed NSO 6.0 + FP. I see 2 issues (maybe related): 1. Packages core-fp-common and resource-manager failed to load with same error:<ul><ul><ul>ALARM package-load-failure: LOAD_PACKAGE</ul></ul></ul> 2. When try to run the "load merge" operations - getting access denied. The files has all running permissions and belong to the current user I defined. when doing this operation - it fails:cd /home/nso600/nso-6.0-tsdn-5.0.0-M4+ENG-34/tsdn/bootstrap-datancs_cli -u adminconfigureunhide debugload merge CS-SR-internal-plan-kicker.xmlgetting:Error: access deniedcan you have a look and tell what went wrong on install process? server is 10.56.58.145 (nso600/Public1234!)Thanks! | PLMK once you update your Java version.hi Sahithi, I have fixed the java version issue, and now all packages are UP. Still facing issue of access denied when I try to do load merge. hi, I see that there is no "set" command on ncs cli, and no nacm permissions - is there a way to resolve those issues? NCS 6.0 successfully installed. |
Got 404 access error when trying to access a few TSDN FP info in github : Hi,Getting 404 access error when I tried to access below info. Is this github access permission issue ?Please let me know.Thanks,Jen-ShueELAN Device Configuration Reference: E-TREE Device Configuration Reference: Model Reference: | From the screenshot, it doesn't look like you're logged into github. Can you login and try again?Hi Jen Shue,As Discussed, you have access now.Closing thread.Thanks,Priyanka |
Provision policy failed on LSA setup with illegal reference: I have a LSA setup with 1 CFS and 2 RFS. PE-A is associated with rfs-29. I am able to onboard LSA providers and devices to CW cluster. When provision an sr-te policy either from CNC UI or NSO, both failed the validation with illegal reference.Steps:1. from NSO commit manager load the payload xml file (attached) 2. Click "Native Config" tab The following error message shows:"errors: reason: illegal reference. paths: /ncs:devices/device{rfs-29}/config/cisco-sr-te-cfp-internal:sr-te/cisco-sr-te-cfp-sr-policies-internal:policies/policy{srte_c_401_ep_100.100.10.3 PE-A}/head-end. path: /ncs:devices/device{rfs-29}/config/cisco-sr-te-cfp-internal:sr-te/cisco-sr-te-cfp-sr-policies-internal:policies/policy{srte_c_401_ep_100.100.10.3 PE-A}/head-end" | Hello, Please kindly share the setup info so I may verify the devices/config.CFS: 172.23.213.30RFS: 172.23.213.29 ; 172.23.213.39id/pw: root/Vtsisco@123!Let me know if you need any other information.Hello, I have been able to load the policy succesfully on rfs-29.rfs-29 was out of sync and thus the policy error is seen as above.There are alarms to indicate the rfs-29 was down for sometime (PE-A may have been onboarded during that time).Under CFS - the dispatch map contained the device but the config under the rfs node wasnt showing the device:admin@ncs% show devices lsa dispatch-mapdevice PE-A {ned-id cisco-iosxr-cli-7.38:cisco-iosxr-cli-7.38;remote-node rfs-29;}admin@ncs% show devices device rfs-29 config devices deviceNo entries found.When a compare config was requested, it indicated the device rfs-29 was out of sync.I have executed a sync-from on the rfs nodeadmin@ncs% request devices device rfs-29 sync-fromresult trueNow, the policy is onboarded successfully.admin@ncs% show sr-te policies policy srte_c_401_ep_100.100.10.3head-end PE-A;tail-end 100.100.10.3;color 401;binding-sid 11111;path 401 { dynamic { metric-type latency; pce; }}Thanks Janaki for finding the device OOS issue and resolve it. I went ahead and provision an L2vpn service from CNC and it stuck in "In-Progress" state. Cross launch to NSO the plan data showed 5/8 completed. Screenshots attached. Can you help to take a look?Hi Crystal, after investigation it seemed like the redeploy of service did not happen correctly. Everything else seemed to be in place, the logs indicate that the kickers etc were triggered properly but for some unknown reason the redeploy did not go through fully.When I redeployed the service it worked well and I also deleted the config and re-loaded it which also worked well.Please verify and let me know.Thanks Janaki for investigating the issue. I went ahead and delete the L2vpn service from CNC UI. But the entry still showed on CNC UI. When I cross launch to view in NSO, NSO UI showed "path does not exist". There seems to be a disconnect between CNC and NSO. Can you check if the correct status has been sent to CNC?Thanks.Hi Crystal, Sure! I can look at it, but it would be better to track this above issue in a new ticket.Please kindly proceed with opening up another ticket for troubleshooting this issue.Can you please confirm if the original issue with the illegal reference is fixed so I may proceed with closing this ticket?Please let me know.Sure Janaki. The illegal reference issue is resolved. You can close this ticket. I will open new ticket to track the other issue. Thanks again for your help.Thank you!rfs-29 was out of sync and thus the policy error is seen as above. Alarms indicate node had lost connectivity which resulted in the out of sync. Issue was fixed on the setup by manually running a sync from on the rfs-29 node. |
NSO crashed and won't start, after services deletion commands: As part of SH automation execution the NSO crashed and won't start, after executing the following commands:"delete flat-L3vpn","delete flat-L2vpn","delete l3vpn-ntw","delete l3vpn-route-policy","delete l2vpn-ntw","delete l2vpn-route-policy","delete sr-te","delete te"VM details:10.56.112.77auto1/Public1234!system installationNSO 5.7.2.1 + CFP M3/var/log/ncs/ncs.logJob logs:Link:console logs:...0:35:19 admin@ncs% 00:35:19 2022-03-22T00:35:19: %TESTCASES-INFO: Command to be executed: delete te00:35:19 delete te00:35:19 00:35:19 00:35:19 00:35:19 admin@ncs% 00:35:19 commit00:35:20 Commit complete.00:35:20 00:35:20 00:35:20 00:35:20 admin@ncs% 00:35:20 exit00:35:20 00:35:20 admin@ncs> 00:35:20 exit00:35:20 00:35:32 2022-03-22T00:35:31: %TESTCASES-INFO: Waiting 6.0 minutes for services to be deleted...FAILED TO CONNECT THE NSO CLI:...00:41:33 Last login: Mon Mar 21 22:35:07 2022 from 10.56.22.10100:41:33 ]00:41:33 00:41:33 2022-03-22 00:41:33,350: %UNICON-INFO: +++ initializing handle +++00:41:33 1337;RemoteHost=auto1@gd-oashery-nso]1337;CurrentDir=/home/auto1]1337;ShellIntegrationVersion=16;shell=bash]133;C;00:41:33 ]1337;RemoteHost=auto1@gd-oashery-nso]1337;CurrentDir=/home/auto1133;D;0]133;Aauto1@gd-oashery-nso:~$ ]133;Bncs_cli -u admin00:41:33 [?2004l]133;C;Failed to connect to server00:41:33 ]1337;RemoteHost=auto1@gd-oashery-nso]1337;CurrentDir=/home/auto1133;D;1]133;Aauto1@gd-oashery-nso:~$ ]133;B00:42:33 00:42:33 2022-03-22 00:42:33,500: %UNICON-ERROR: Timeout occurred : Timeout value : 6000:42:33 Command sent: ncs_cli -u admin00:42:33 Pattern: 00:42:33 Got: '1337;RemoteHost=auto1@gd-oashery-nsox07x1b]1337;CurrentDir=/home/auto1x07x1b]1337;ShellIntegrationVersion=16;shell=bashx07x1b]133;C;x07x1b]1337;RemoteHost=auto1@gd-oashery-nsox07x1b]1337;CurrentDir=/home/auto1x07x1b133;D;0x07x1b]133;Ax07auto1@gd-oashery-nso:<sub>$ x1b]133;Bx07ncs_cli -u adminx1b133;C;x07Failed to connect to serverx1b]1337;RemoteHost=auto1@gd-oashery-nsox07x1b]1337;CurrentDir=/home/auto1x07x1b133;D;1x07x1b]133;Ax07auto1@gd-oashery-nso:</sub>$ x1b]133;Bx07'00:42:33 2022-03-22T00:42:33: %TESTCASES-ERROR: [31mERROR occurred in send_line: ('Failed to match buffer on spawn', TimeoutError('Timeout occurred'))[0m[39m... | Hi Ofir,With the help from Isaac, we could not conclude what is root cause for the crash from the attached logs. We will try to reproduce this issue in the local setup. Please share all payloads of services before massive service deletion. Let see if we can reproduce the issue.Please confirm is it CNC 4.0 M4 build? Is there any settings that need to know to make it happens like CQ etc ...Thanks,LinhHello Ofir,I am assisting with RCA for this failure you are seeing.Would you be able to give me access to your Jenkins console logs : Thanks,Isaac KimHi Isaac, I don't have permissions for the Jenkins, but you can watch these logs at: or . btw, I re-installed the NSO (5.7.2.1 + M3) from scratch and when when the services have created via CW nso proxy REST API, in CW they displayed as in progress, now I'm not sure whether it's related to the same issue but it's worth to check that from NSO POV the services created properly, and the new NSO installation are correct, can you please help us verifying that ? it's the same NSO details:10.56.112.77auto1/Public1234!CW:10.56.112.51( ssh: cw-admin/Public1234! , UI: admin/Public1234!)Hi Ofir, All services that you push to NSO are not in 'reached' state because you don't set a proper username in nacm. This user 'auto1' (see the screen shot) is used to communicate to with NSO but it is not set proper access in nacm auto1@ncs% show nacm groups group ncsadmin user-name [ admin cw-admin private ]; 'auto1' should be member of nacm ncsadmin group-LinhHi Linh,we dont have such steps in installation confluence page.attached snapshot.Hi Arun,That is the same command in general. Only difference is it is going deep down inner level ( like a filter) so you could see it clearly.Thanks,LinhHi Linh, after fixing the nacm permissions, I re-deploy all the services, the status was green for all services, but then I started the automation script, after the execution of the delete commands, the nso server was crashed again, can you please take a look on it now ? the nso is down.Hi Ofir, Please leave the system as it for now. The team and I will take a look. We will let you know when we are done!Thanks,LinhSure, Linh. you can do the investigation, until Sunday we must have a solution so we won't be blocked.Thanks,Ofir. Can I have Jenkins console url again?Thanks,LinhHello Ofir,Would you be able to provide alternative links for new console logs? I cannot access the above link.Thanks,Isaac Kimis it ok ? Yes thank you!Will take a look now.Thanks,Isaac KimHello Ofir,Looking at your console logs, I can see something that stood out:<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"><pre class="code-java">480: 2022-03-25T17:20:17: Cleanup CFP Services481: 2022-03-25T17:20:17: Command to be executed: delete flat-L3vpndelete flat-L3vpn[ok][2022-03-25 14:20:14][edit]admin@ncs% 485: 2022-03-25T17:20:17: Command to be executed: delete flat-L2vpndelete flat-L2vpn[ok][2022-03-25 14:20:15][edit]admin@ncs% 489: 2022-03-25T17:20:18: Command to be executed: delete l3vpn-ntwdelete l3vpn-ntw[ok][2022-03-25 14:20:15][edit]</pre></div></div>We can see here that both flat-L3vpn and l3vpn-ntw servicepoints are being deleted in the same transaction. This is not supported behavior.With TSDN stacked services, only the top level NB servicepoint that is being used for provisioning can be interacted with.For example:l3vpn-ntw => If you are using l3vpn-ntw for L3 provisioning, then you can only use l3vpn-ntw (no flat-L3vpn)flat-L3vpn => If you are using flat-L3vpn for L3 provisioning, then you can only use flat-L3vpn (no l3vpn-ntw)l2vpn-ntw => If you are using l2vpn-ntw for L2 provisioning, then you can only use l2vpn-ntw (no flat-L2vpn)flat-L2vpn => If you are using flat-L2vpn for L2 provisioning, then you can only use flat-L2vpn (no l2vpn-ntw)From the above console logs, you can see that both l3vpn-ntw and flat-L3vpn servicepoints (and both L2 servicepoints) are being targeted. This will lead to undefined behavior and will definitely cause race conditions.Could you please try to reinstall your backup and try to remove the conflicting operations?Thanks,Isaac KimHi Isaac, This automation flow is being executed for a long time, I can send you prev logs, after upgrading to 5.7.2.1 + M3 it started to crash, this deletion script is been used by other teams as well, nothing has changed from our side but the NSO version which was upgraded, what do you mean by installing backup ? should I re-install everything all over again ? sorry but it's not acceptable solution, as the process is long and it takes the entire day for that, if it's not supported operation, I think you need to block it, anyway, crashing the entire NSO server and re-install is required, not acceptable.Hi Issac,As Ofir said, it is not acceptable for the System to crash in any race condition.we will modify the automation steps . but lets have CDETS on it to fix the issue.Ofir., please riase CDETS referring to this Jira ticket.Thanks,Arun.M.GHi Arun,Because the delete operation has conflicting servicepoints, the behavior afterwards is undefined. I can see from NSO crash dump that the issue stems from undefined plan path for ietf te from NSO side effect of trying to reactive redeploy zombie. Now we have to step through the entire delete flow to see where the race condition lies.To reiterate, it may not be acceptable for race conditions, but this is undefined behavior because there is conflict in servicepoint interaction. Again, with undefined behavior, the outcome is unpredictable which can cause crash like this.To be frank, it is unacceptable to continue using conflicting operations as part of automation flow. This needs to be resolved to have valid automation runs.I am continuing to look into this issue despite the undefined nature of the outcome.I will update on this ticket once we confirm exact root of issue.Thanks,Isaac KimPlease do not raise a CDETS for this ticket yet as we do not know if the issue stems from TSDN service logic, from platform failure, or from the undefined behavior due to servicepoint conflict.Until we identify root cause of issue, we should not jump to any conclusions.Because the automation NSO setup is reused across runs, the issue can stem from previous state. Because the NSO setup is "cleared" using conflicting delete operations, any run after the first run on virgin NSO setup is invalid.I wil be debugging on the earliest NSO logs provided as this should be the cleanest state. I can see that IETF TE oper-data was able to be referenced by platform correctly before the mass delete operation (which has conflicting servicepoint delete). After this transaction is processed, I can see NSO cannot access IETF TE oper-data plan path anymore. Any logs or automation "runs" after this point must be assumed invalid due to the conflicting operations.Hello Ofir and Arun,Thank you for your patience on this issue.With your input, we have been able to reproduce this issue consistently on our local setups and isolate the source of the issue.Reproduction Steps:1. Load merge all L2 payloads (as defined in Jenkins console logs) and all IETF TE payloads2. commit3. Wait for plan to be reached for all services4a. Failed Delete Commands :delete flat-L2vpndelete l2vpn-ntwdelete l2vpn-route-policydelete tecommitRESULT : NSO crash OR stuck IETF TE zombie4b. Successful Delete Commands :delete l2vpn-ntwdelete l2vpn-route-policydelete tecommitRESULT : Services Deleted, Zombies clearedIf you would like to have more details on our reproduction setup, please let me know and I can provide exact steps.Based on these results, I believe that fixing the conflicting delete operations can resolve your issue. If you fix the conflicting delete operations but still face NSO crash, please let us know so we can investigate further.For your existing TSDN + NSO automation setup, I have tried to recover the CDB, but because there are pending zombies with illegal references, I was not able to load the CDB files into a running NSO (which is required for CDB manipulation with ncs_load). Unfortunately, it seems like you will have to reinstall TSDN.For preventing this conflicting delete operations from occurring on service side, please feel free to open an enhancement request and we will see how we can implement some checks to prevent this from happening again.Thanks,Isaac KimHi Isaac,Thanks for the comments and suggestion. we agree on the steps. but NSO crash is not accepted in any Race condition. we should need to have a fix to avoid the issue hitting at customer side with this race condition.Thanks,Arun.M.GHi, raised CDETS for tracking, please keep this Jira ticket as a reference to cdets bug for further investigation.Thanks,Ofir.Hello Arun and Ofir,After discussing with team, we have come to conclusion that despite the undefined nature of the delete operations, it is not acceptable for NSO to crash in any circumstance.Thank you for raising the CDETs. We will look into the crash further now that we have a reproducible procedure.Yes, we will leave this ticket open for now and I will update this ticket if we have any progress on the CDETs.Thanks,Isaac KimThank you Isaac and team for the understanding.Late update, reproduction setup was provided to platform team few week ago. Waiting to get assigned to engineer.Hello Ofir and Arun, we have gotten a reply from platform team and we are working to bring a fix for TSDN 5.0.This issue seems quite rare. Despite this, the workaround for TSDN 4.0 is the following:<ol>Only delete top layer serviceWhen deleting service, use the full path to service instance</ol>I have added a warning in our TSDN 4.0 documentation for this.For TSDN 5.0, we will absorb the platform fix for this.Thanks,Isaac KimWorkaround provided for TSDN 4.0 and fix will be absorbed for TSDN 5.0 |
Test: What NSO version is supported: Test: What NSO version is supported | In this version, we support NSO 5.5.2 and 5.4.3.2In this version, we support NSO 5.5.2 and 5.4.3.2Thanks, I am happy |
Need to know the status of RON state 506,410: "message": "Error running action for side-effect item /cisco-ron-cfp:ron/ron-ml-plan{200_mux1}/plan/component{ncs:self self}/state{ncs:init}: Python cb_action error. Error: RON-410Hardware capability for the {QDD-400G-ZR-S, muxponder, 200} cannot be foundSTATUS_CODE: RON-506REASON: Fetch Optics failedCATEGORY: custom-actionSEVERITY: ERRORContext [name = Fetch Optics Data error, message = ZR Fetch Optics data action returned error state = {'service': '200_mux1', 'endpoint': 'P-TOPLEFT-VXR'}]" | Hi Aarthi,We are looking into your issue. Please standby as we might need more info from your end debug your system.Please provide the following:<ol>NSO versionCFP build versionDevice type and version used for testingAdd clear steps to reproduce an issue this includes details if some steps were done through NSO UI/CLI or through CNC UI, details on commit options used, order in which payloads were pushed, plan status in between, etc.All relevant payloads.NSO logs including trace if there was something pushed to the deviceIn some cases, wed like to understand the use-case where we see users performing certain actions especially when some steps are done through NSO UI/CLI.</ol>I can also take a look around and check your testbed if you provide credentials here.Thank you,AbeThe issue is resolved now. Thanks for the clarification Abe. You can close the TicketHi Aarthi,To find out more about RON status code displayed on the service-plan, please use. This will display both the reason and recommended-actions for any given RON status codeAs for the reason you have encountered the above issue,it is because of provisioning muxponder with 200 bandwidth when ZR-only (not ZR+) can only do muxponder = 400, and therefore not supported.Please let me know if answers your queries or if you have additional questions regarding this ticket.Thank you,AbeThanks Aarthi. Closing the ticket now.Answered all questions from Aarthi. Setting the issue as resolved and closing the ticket. |
Service creation via restconf proxy API is failing: In the latest CW builds the service creation via:"/crosswork/proxy/nso/restconf/data" is failing, I noticed that now the proxy urls contains "jsonrpc" instead of "restconf", is it a known change ? if yes, do you know who can provide us the updated urls and payloads ?Setup details:NSO:10.56.112.77auto1/Public1234!CW:10.56.112.51( ssh: cw-admin/Public1234! , UI: admin/Public1234!) | Hi OfirWe do not have information about the urls used by the CNC UI. Please reach out to the CNC UI team. They should be able to assist you here.Thanks,NikhilWe have found the root cause, it's on ifra-services side. Closing the ticket as the issue is with the infra services side |
Device added in one RFS is not seen in the CFS while creating service: Server details:CFS: 10.56.116.151RFS1: 10.56.116.152RFS2: 10.56.116.153login: nso/Public1234!ui ; backed both creds are same as mentioned aboveDevices I have in RFS1: PE-A,PE-B and 4 core devicesDevice I have in RFS2 : PE-CNow tried to create a service between PE-B to PE-C. Got following error:1/1. .../vpn-node-id illegal referenceVPN-node-id:PE-C"I am not able to create connection between two RFS nodes via CFS"Payload is attached | Hi Sampath,Seem like the device was not synced to the dispatch map properly. You can see from the output below that it does not exist on the CFS.<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"><pre>admin@ncs% show devices lsa dispatch-map device device CE-A { ned-id cisco-iosxr-cli-7.38:cisco-iosxr-cli-7.38; remote-node sareddyd-esxi-01-vm2;}device CE-B { ned-id cisco-iosxr-cli-7.38:cisco-iosxr-cli-7.38; remote-node sareddyd-esxi-01-vm2;}device P-BOTTOMLEFT { ned-id cisco-iosxr-cli-7.38:cisco-iosxr-cli-7.38; remote-node sareddyd-esxi-01-vm2;}device P-BOTTOMRIGHT { ned-id cisco-iosxr-cli-7.38:cisco-iosxr-cli-7.38; remote-node sareddyd-esxi-01-vm2;}device P-TOPLEFT { ned-id cisco-iosxr-cli-7.38:cisco-iosxr-cli-7.38; remote-node sareddyd-esxi-01-vm2;}device P-TOPRIGHT { ned-id cisco-iosxr-cli-7.38:cisco-iosxr-cli-7.38; remote-node sareddyd-esxi-01-vm2;}device PE-A { ned-id cisco-iosxr-cli-7.38:cisco-iosxr-cli-7.38; remote-node sareddyd-esxi-01-vm2;}device PE-B { ned-id cisco-iosxr-cli-7.38:cisco-iosxr-cli-7.38; remote-node sareddyd-esxi-01-vm2;}device sareddyd-esxi-01-vm2 { ned-id cisco-nso-nc-5.7:cisco-nso-nc-5.7; local;}device sareddyd-esxi-01-vm3 { ned-id cisco-nso-nc-5.7:cisco-nso-nc-5.7; local;}</pre></div></div>To remedy this issue you can run the following command to sync the device from RFS-2.<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"><pre>request devices lsa dispatch-map sync remote-nso sareddyd-esxi-01-vm3</pre></div></div>Let me know if you have any further questions.Thanks,RegiI have updated the wiki to include this in our troubleshooting guide for devices missing in the dispatch map: |
Enable NSO HA on IPv6 setup: Configured an NSO HA, follow this wiki link on an IPv6 setup:"show high-availability status" on primary node is OK, but not on secondary node. Is there any configuration missing for IPv6?Primary:admin@ncs> show high-availability statushigh-availability status mode primaryhigh-availability status current-id masterhigh-availability status assigned-role primaryhigh-availability status read-only-mode falseSecondary:admin@ncs> show high-availability statushigh-availability status mode nonehigh-availability status read-only-mode falseHere are the HA configuration on both nodes:Primary:admin@ncs% show high-availability token $9$a5bEJW74JrgYUlTImS7p4Fj3gvN/kxwhwVBGFmBjJok=;ha-node master { address fded:1bc1:fc3e:96d0:192:168:5:41; nominal-role primary;}ha-node standby { address fded:1bc1:fc3e:96d0:192:168:5:42; nominal-role secondary; failover-primary true;}settings { enable-failover true; start-up { assume-nominal-role true; join-ha true; } reconnect-interval 15; reconnect-attempts 3;}Secondary:admin@ncs% show high-availability token $9$9Kw3nWwqYpFjnk2FlX+8dr41rA3SUQ5cb02x3u+ZHPo=;ha-node master { address fded:1bc1:fc3e:96d0:192:168:5:41; nominal-role primary;}ha-node standby { address fded:1bc1:fc3e:96d0:192:168:5:42; nominal-role secondary; failover-primary true;}settings { enable-failover true; start-up { assume-nominal-role true; join-ha true; } reconnect-interval 15; reconnect-attempts 3;} | Hi Crystal,Can you provide access to the nodes so we can take a look?Thanks,AbeHi Abe,The NSO is using private subnet. You will need to reach it from jump host. NSO has been configured with dual-stack. Jump host: 172.20.111.162id: pw: root/Cwork123!NSO 41: 192.168.5.41 NSO 42: 192.168.5.42id/pw: root/Vtsisco@123!Thanks.-CrystalHi Crystal,Show high availability status on both nodes now shows HA has been stablished.Primary_node:root@ncs> show high-availability statushigh-availability status mode primaryhigh-availability status current-id masterhigh-availability status assigned-role primaryhigh-availability status read-only-mode falseID ADDRESS-------------------------------------------standby fded:1bc1:fc3e:96d0:192:168:5:42Secondary_node:root@ncs> show high-availability statushigh-availability status mode secondaryhigh-availability status current-id standbyhigh-availability status assigned-role secondaryhigh-availability status be-secondary-result initializedhigh-availability status primary-id masterhigh-availability status read-only-mode falsePer NSO admin guide (attached, ), to support ipv4 and ipv6 access simultaneously, we need to configure extra-listen for each agent and transport, where additional IP address and port pairs can be configured. (for ipv4 0.0.0.0, for ipv6 "::")example:<!-- Use the built-in SSH server --><ssh> <enabled>true</enabled> <ip>0.0.0.0</ip> <port>2024</port> <extra-listen> <ip>::</ip> <port>2024</port> </extra-listen></ssh>Please let me know if you have any other questions. Designating the issue resolved and ticket will be closed now.Thanks,AbeHi Crystal,Show high availability status on both nodes now shows HA has been stablished.Primary_node:root@ncs> show high-availability statushigh-availability status mode primaryhigh-availability status current-id masterhigh-availability status assigned-role primaryhigh-availability status read-only-mode falseID ADDRESS-------------------------------------------standby fded:1bc1:fc3e:96d0:192:168:5:42Secondary_node:root@ncs> show high-availability statushigh-availability status mode secondaryhigh-availability status current-id standbyhigh-availability status assigned-role secondaryhigh-availability status be-secondary-result initializedhigh-availability status primary-id masterhigh-availability status read-only-mode falsePer NSO admin guide (attached, ), to support ipv4 and ipv6 access simultaneously, we need to configure extra-listen for each agent and transport, where additional IP address and port pairs can be configured. (for ipv4 0.0.0.0, for ipv6 "::")example:<!-- Use the built-in SSH server --><ssh><enabled>true</enabled><ip>0.0.0.0</ip><port>2024</port><extra-listen><ip>::</ip><port>2024</port></extra-listen> </ssh>Please let me know if you have any other questions. Designating the issue resolved and ticket will be closed now.Thanks,AbeIncluding more information Abe shared here for future reference. Add "extra-listen" for <ha> section in ncs.conf. <ha> <enabled>true</enabled> <ip>0.0.0.0</ip> <port>4570</port> <extra-listen> <ip>::</ip> <port>4570</port> </extra-listen> <tick-timeout>PT20S</tick-timeout> </ha>Attached are other info. Abe shared. |
L3VPN service creation is failing on LSA HA setup (CFS in HA and 2 RFS in HA): Hi Team,I have installed TSDN M5 with LSA (CFS in HSA and RFS in HA). I am trying to create L3VPN service which is failing. Can somebody take a look into the setup.Setup:CFS VIP: 172.201.00.71:8080admin/Ovatest123@RFS-HA-70:172.201.00.70:8080admin/Ovatest123@RFS-HA-78:172.201.00.78:8080admin/Ovatest123@Thanks,Kanchan | Hi Kanchan,Please correct the setup IP you provided. It has a typo and i could not log on your setup. Also can you provide the error messages and provide a playload?Thanks,LinhHi Linh,Sorry for the typo: Setup:CFS VIP:172.20.100.71:8080admin/Ovatest123@RFS-HA-70:172.20.100.70:8080admin/Ovatest123@RFS-HA-78:172.20.100.78:8080admin/Ovatest123@Thanks,KanchanHere are the payload After submiter correct the tsdn-kicker-events name. Services work as expected. Closed the ticket-LinhFixed after correctiing tsdn-kicker-events |
TSDN-2.0.0 permanent zombie state on service deletion: Delection of a ietf-te-fp service never happens. It remains in zombie state. Using NSO netsim devices that are in sync and reachable. Attached is a file with the commands and available logs. | Is this related to "RT-45602: Show zombies stuck and transaction locked for deletion from NSO UI" ?Hi PauloWe tried to reproduce this with TSDN 2.0code and netsim device but it seems to be working fine for us. Can you please share the setup details where you see this issue?Thanks, NikhilHi Nikhil, I've shared with you (check email) a cisco.box folder with your complete system setup in a docker container. You can have it running in just a few minutes. Below is a file with the detail description of all steps needed to start the container and reproduce the delete problem. Hi Paulo,We checked the setup and found that the python version being used is 3.6.8 whereas the recommended version is 3.8 or above.Please upgrade the python version and then test the functionality. Let us know if you still see issues after the upgrade.Attaching the pre-requisites for TSDN 2.0.0.Thanks, NikhilHi Nikhil,I update the docker container to use python 3.8.6. I see the same behaviour.Vodafone testing environment is already using 3.8.6, and I see the same behaviour there.Deletion of NSO services remains in Zombie State and manually cleanup is always required.Hi Paulo,I checked the setup and found that you haven't configured nacm user correctly.admin@ncs% show nacm read-default deny;write-default deny;exec-default deny;groups { group ncsadmin { user-name [ private ]; } group ncsoper { user-name [ public ]; }}Please correct it as below. The steps are mentioned in the wiki url as well.Thanks,NikhilHi Nikhil, Problem is solved! Thank you very much for your assistance and help! Ticket can be closedClosing the ticket as the issue is resolved. |
Do we support transport slice with SRv6?: Question 1: In CNC6.0 we started to support transport slicing. Like to confirm if we support SRv6 in the slice? If we do, the flow will be 1. create the ODN with SRv6 enabled 2. create an NSST with the above ODN3. create L3 slice with the above NSSTQuestion 2: L2 slice with SRv6 is not supported, is this correct? | Hello Crystal,Question 1:L3 with Srv6 ODN is supported with resulting config looking as attached in screenshot.Question 2:L2 with Srv6 ODN is supported with resulting config looking as below: l2vpn { xconnect { group NSS-L2-P2P-internal { p2p NSS-L2-P2P-internal { interface GigabitEthernet0.100; neighbor-evpn-service { neighbor { evpn evi 1 service 1 { segment-routing { srv6; } locator MAIN; } } } } } } }Please let us know if this helps.Regards,Janaki DuggiralaCustomer confirmed ticket maybe resolved with provided information for srv6. |
CFS in scale setup not coming up after migration: We had 3 RFS, 1 CFS setup migrated from TSDN 5.0 to TSDN6.0 Drop 10. Following migration wiki.3 RFS have come up. But CFS did not come up, so increased the time out, but still no luck.Deleted the 5.0 packages from /var/opt/ncs/packages and copied 6.0 packages. For CFS, is this step right step ?Can you help.setup : 192.168.103.235 | credentials for CFS - 192.168.103.235 (cnctest/Ovatest123@) or admin/Ovatest123@Trying to start NSO.Saw the error below:Dec 01 17:39:51 scale-nso-CFS-235 ncs: - Cannot bind to internal socket 127.0.0.1:4569 : address already in useStopped all NSO, and all unnecessary NCS processes.Starting NCS now.Confirmed NSO is running and packages are up. Please see screenshot.Customer verified that issue is resolved and ticket can be closed. |
Migrated CFS bootstrap steps failing: We migrated TSDN LSA setup from TSDN 5.0 to 6.0. While verifying the boot strap steps, show status-code-cfp command alone is failing. Remaining steps are successful. Kindly help to resolve this issue.admin@ncs% show status-code-cfp----------------^syntax error: element does not existadmin@ncs%Setup : CFS 192.168.103.235RFS1 192.168.103.236, 237, 238admin/Ovatest123@ | Please enter "unhide debug" and then run status code command to verify such as :admin@ncs% unhide debugadmin@ncs% show status-code-cfp....status-code-cfp SR;Good. thank you for the help.Customer confirmed that issue is resolved and information has been received. |
Multiple route policies are attached to the parent route-policy even though payloads don't have multiple policies. The payload is attached is for reference.: Multiple route policies are attached to the parent route-policy even though payloads don't have multiple policies. The payload is attached is for reference.route-policy bgp_inapply SET_COLORv4_service_RP-L2NM-ODN-xrd-1-350apply SET_COLORv4_service_RP-L2NM-ODN-xrd-1-450passend-policy | Hi Ragesh,I can see that from your output, we can see an additional route policy being attached that is not defined in the payload mentioned in this ticket "RP-L2NM-ODN-xrd-1-450".To RCA this issue, I would need some more context about your NSO. The payload itself does not provide enough information to debug. To fast-track RCA, would you be able to provide your system ssh credentials? I will not make any changes.Thanks,Isaac KimHi Isaac,I have modified the configuration on device ; did sync-from, Not sure what configuration will have on the NSO, Please take a look on the NSO.NSO- 172.24.97.147Hi Ragesh,On your machine, I can see the following:<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"><pre class="code-java">admin@ncs% show l2vpn-rr-parent-route-policy...l2vpn-rr-parent-route-policy bgp_in xrd-1 { original-rr-route-policy ; local-route-policy RP-L2NM-ODN-xrd-1-350 { ipv4; } local-route-policy RP-L2NM-ODN-xrd-1-450 { ipv4; }}admin@ncs% show l2vpn-route-policy | nomore | match RP-L2NM-ODN-xrd-1-450[ok][2022-04-08 13:39:47][edit]admin@ncs% show l2vpn-ntw | nomore | match RP-L2NM-ODN-xrd-1-450[ok][2022-04-08 13:34:53][edit]</pre></div></div>It seems like there was a L2 service that referenced a valid l2vpn-route-policy "RP-L2NM-ODN-xrd-1-450". Somehow, this reference and l2vpn-route-policy definition was deleted without invoking service callbacks.Would you be able to tell me all the operations that were done related to "RP-L2NM-ODN-xrd-1-450"? Did you execute a cleanup action without first deleting service?Thanks,Isaac KimHi Issac,Yes, I configured the RP-L2NM-ODN-xrd-1-450 route policy for different L2VPN tunnels ; deleted the L2VPN service ; the route-policy from the CW-server. Later when we provide the other L2VPN service with RP-L2NM-ODN-xrd-1-350, both the route-policy is pushing to the device.Hi Ragesh,Sorry for the very delayed response. This scenario goes against NSO's fastmap functionality. That lingering route policy should have been removed as part of the associated L2 service delete unless no-deploy option was used for the delete commit or if cleanup action was used without first invoking delete which could cause race conditions.If you encounter this issue again, please feel free to update this ticket. I will take another look at your system and try to RCA the issue.Thanks,Isaac KimPlease open new JSD if encountered again. |
One of the 2nd clusters in NSO LSA HA with L3 network shows RFS nodes as down: Issue: One of the 2nd clusters in NSO LSA HA with L3 network shows RFS nodes as downSteps:1. I have setup LSA on two pairs of VMs - 1 cluster with 1 CFS, 2 RFS and another cluster with 1 CFS, 2 RFS.2. 1st cluster came up fine and status is UP for RFS nodes in "show cluster".3. 2nd cluster displays the status as down for RFS nodes.4. I checked CFS is able to connect to RFS nodes via port 2022. sync-from and ssh fetch-host keys returned true as well.5. admin@ncs> show cluster LAST RECEIVEDNAME NAME STATUS EVENT NOTIFICATIONS--------------------------------------------------nso-cw2-rfs1nso-cw2-rfs2 LOCAL REMOTEREMOTE NODE ADDRESS PORT CHANNELS USER USER STATUS TRACE-----------------------------------------------------------------------------nso-cw2-rfs2 192.168.6.63 2022 - admin admin down disablednso-cw2-rfs1 192.168.6.62 2022 - admin admin down disabledJanaki and Linh helped to check the setup and everything seems to correct with configurations. Hence, need help to resolve this issue so that NSO LSA with L3 can with HA mode. | Assigning to Van to please check the cluster.Hi Gomathi,After I enable device notificationset cluster device-notifications enabledThe cluster is upadmin@ncs% run show cluster RECEIVEDNAME NAME STATUS LAST EVENT NOTIFICATIONS--------------------------------------------------------------------------------------nso-cw2-rfs1 device-notifications up 0000-01-01T00:00:00-00:00 0nso-cw2-rfs2 device-notifications up 0000-01-01T00:00:00-00:00 0 LOCAL REMOTEREMOTE NODE ADDRESS PORT CHANNELS USER USER STATUS TRACE-----------------------------------------------------------------------------nso-cw2-rfs1 192.168.6.62 2022 - admin admin up disablednso-cw2-rfs2 192.168.6.63 2022 - admin admin up disabledRegards,LinhHi Linh,After enabling the device notification on cw2-cfs1, show cluster shows rfs nodes as up which is different setting from tsdn wiki.I enabled back HA on both cw1-cfs1 and cw2-cfs2 below is the output:cw1-cfs1:admin@ncs> show cluster RECEIVEDNAME NAME STATUS LAST EVENT NOTIFICATIONS--------------------------------------------------------------------------------------nso-cw1-rfs1 device-notifications up 0000-01-01T00:00:00-00:00 0 ncs-events up 0000-01-01T00:00:00-00:00 0nso-cw1-rfs2 device-notifications up 0000-01-01T00:00:00-00:00 0 ncs-events up 0000-01-01T00:00:00-00:00 0 LOCAL REMOTEREMOTE NODE ADDRESS PORT CHANNELS USER USER STATUS TRACE-----------------------------------------------------------------------------nso-cw1-rfs2 192.168.5.32 2022 - admin admin up disablednso-cw1-rfs1 192.168.5.31 2022 - admin admin up disabledcw2-cfs1:dmin@ncs> show cluster RECEIVEDNAME NAME STATUS LAST EVENT NOTIFICATIONS--------------------------------------------------------------------------------------nso-cw1-rfs1 device-notifications - 0000-01-01T00:00:00-00:00 - ncs-events - 0000-01-01T00:00:00-00:00 -nso-cw1-rfs2 device-notifications - 0000-01-01T00:00:00-00:00 - ncs-events - 0000-01-01T00:00:00-00:00 -Is the above output on cw2-cfs1 expected?Before enabling HA, cw2-cfs1 showed as below:admin@ncs% run show cluster RECEIVEDNAME NAME STATUS LAST EVENT NOTIFICATIONS--------------------------------------------------------------------------------------nso-cw2-rfs1 device-notifications up 0000-01-01T00:00:00-00:00 0nso-cw2-rfs2 device-notifications up 0000-01-01T00:00:00-00:00 0 LOCAL REMOTEREMOTE NODE ADDRESS PORT CHANNELS USER USER STATUS TRACE-----------------------------------------------------------------------------nso-cw2-rfs1 192.168.6.62 2022 - admin admin up disablednso-cw2-rfs2 192.168.6.63 2022 - admin admin up disabledadmin@ncs% exitadmin@ncs> request high-availability enableresult enabledI enabled HA on all NSO LSA nodes, except, cw1-rfs1 and cw2-rfs1 all other nodes are returning expected hcc and ha configs in L3 mode. cw2-rfs1 gives below misconfiguration error:admin@ncs> show high-availability statushigh-availability status mode nonehigh-availability status assigned-role secondaryhigh-availability status be-secondary-result "error (69) - configuration mismatch"high-availability status primary-id masterhigh-availability status read-only-mode falseI double checked all configs they seem to be configured correctly. CSR router is able to ping corresponding VIP IP on each related pair of cfs and rfs nodes.Can you check and confirm on above secondary node HA config error on cw2-rfs1.Thanks,Gomathi.Hi Gomathi,Can you check bgp router connection and configuration?nso-cw2-rfs1 (192.168.5.31)admin@ncs% show high-availability token $9$i61J6fDpauBiYapug5zczA4QRcuXHc1A/4+s7Lde8oI=;ha-node master { address 192.168.5.31; nominal-role primary;}ha-node standby { address 192.168.6.62; nominal-role secondary; failover-primary true;}admin@nso-cw1-rfs1:~$ Peer AS Up/Down State |#Received Accepted 65137 3d 11:02:52 Establ | 3 3-----------------------nso-cw2-rfs1 (192.168.6.62)admin@ncs% show high-availability token $9$hMmeGxncwdpTtiNNsNpU/w42hZ3BjEztZawyaVoTBug=;ha-node master { address 192.168.5.31; nominal-role primary;}ha-node standby { address 192.168.6.62; nominal-role secondary; failover-primary true;}admin@nso-cw2-rfs1:~$ Peer AS Up/Down State |#Received Accepted 65137 00:21:34 Establ | 4 4Hi Van,Below is the bgp configs on cw2-rfs1 - csr:router bgp 65137 template peer-policy ha-peer route-reflector-client send-community both exit-peer-policy ! template peer-session rfs1-peer remote-as 65138 exit-peer-session ! template peer-session rfs2-peer remote-as 65139 exit-peer-session ! bgp log-neighbor-changes timers bgp 1 10 10 neighbor 192.168.5.31 remote-as 65138 neighbor 192.168.6.62 remote-as 65139 ! address-family ipv4 redistribute connected neighbor 192.168.5.31 activate neighbor 192.168.5.31 send-community both neighbor 192.168.6.62 activate neighbor 192.168.6.62 send-community extended exit-address-familycsr-cw1-cw2-rfs1#ping 192.168.5.31Type escape sequence to abort.Sending 5, 100-byte ICMP Echos to 192.168.5.31, timeout is 2 seconds:!!!!!Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/1 mscsr-cw1-cw2-rfs1#ping 12.12.12.12Type escape sequence to abort.Sending 5, 100-byte ICMP Echos to 12.12.12.12, timeout is 2 seconds:!!!!!Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/1 mscsr-cw1-cw2-rfs1#ping 192.168.6.62Type escape sequence to abort.Sending 5, 100-byte ICMP Echos to 192.168.6.62, timeout is 2 seconds:!!!!!Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/1 mscsr-cw1-cw2-rfs1#ping 13.13.13.13 >>>> VIP of cw1-rfs2/cw2-rfs2 not pingable from csr.Type escape sequence to abort.Sending 5, 100-byte ICMP Echos to 13.13.13.13, timeout is 2 seconds:.....Success rate is 0 percent (0/5)csr-cw1-cw2-rfs1#csr-cw1-cw2-rfs1#ping 11.11.11.11Type escape sequence to abort.Sending 5, 100-byte ICMP Echos to 11.11.11.11, timeout is 2 seconds:!!!!!Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/1 msThanks,Gomathi.Hi Gomathi,Found duplicate stream notification entries in ncs.conf,"dispatch-map-update" in secondary node and "service-aa-changes" in primary node. HA is up after removing the extra config and restarting...admin@ncs> show high-availability high-availability enabledhigh-availability status mode primaryhigh-availability status current-id masterhigh-availability status assigned-role primaryhigh-availability status read-only-mode falseID ADDRESS -----------------------standby 192.168.6.62 Hi Van,Thanks for looking into the issue and fixing it!There was no error during ncs packages reload operation after ncs.conf file update on cw2-rfs2 node. Hence, not sure how the duplicate entries got added in ncs.conf file.I remember during ansible script execution the duplicate entries error was thrown during ncs packages reload. I removed them and restarted ncs with manual installation and it worked fine.On this VM, show hcc was fine and only HA had the issue. As the error was generic and ncs restart also worked didn't have clue that ncs.conf file had duplicate entries.It would help user if error was specific during HA config issue.Thanks,Gomathi.Hi Gomathi,The config syntax was fine as NSO can handle the duplications at start up but not forgiving when doing config comparison for HA. Best practice for setting up HA is replicating exact application and config on both nodes (NSO version, package versions, ncs.conf, HA/hcc config).It's a little vauge but "error (69) - configuration mismatch" should have pointed us to check HA/hcc config, ncs.conf.Regards,Van |
IPv6 CFS and RFS UI takes very long to load, sometimes fails to load.: Hi Team,I have IPv6 LSA setup. I am facing issues to load the CFS and RFS UI on ipv6 address.setup:CFS: (admin/Ovatest123@)RFS(rfs-62): (admin/Ovatest123@)RFS(rfs-63): (admin/Ovatest123@)RFS(rfs-67): (admin/Ovatest123@)Thanks,Kanchan | Kanchan to get back after confirming that there is no routing issue in their lab.VM issue caused this |
NSO CFP - TSDN M4/M5 wiki need update.: Hi NSO-CFP team,Based on the Millstone releases for M4 and M5, NSO team has confirmed there are no model changes.From both TSDN-M4 and M5 wiki links, under Model and Payload Changes, the information are identical to TSDN-M3 wiki. If M4 ; M5 did not have any model changes, this section should either be emptied or should have a note that the information was copied from M3 for referencing purpose.Even with no model changes, we found the following yang files were modified:cisco-flat-L2vpn-fp-internal-common.yangietf-l2vpn-ntw-cisco-augmentations.yangietf-l2vpn-ntw.yangplease see the attached diff output snapshotsWe tried to check the CHANGES text file for more info but unable to get any relevant data.We would like to have a change log if possible to know which yang files were modified for each milestone. This will help us identify the changes and incorporate them to our code and avoid the situation above.Please update the milestone wiki as we do follow this closely for each releases. All of the information from NSO wiki must be up to date as much as possible.Thanks and regards! | Hi Quy,The changes you mentioned are either internal model changes which do not impact payload or the model structure.All these changes mentioned do not impact north bound model.I agree that we should have cleared the page. I will clear the page.We update the revision date on all the yang models for every change made. ThanksSahithiThanks Sahithi for looking into this. Agree these are not a payload impacting changes, but as we include these models on the cnc side compilation and validations, we want to absorb these changes to avoid any specific issue that may occur due to these changes. Also in the past the internal model changes were showed up in the plan data (as xpaths) and we had trouble un/marshaling them though the cnc binding without the changed models. So, please inform us any changes (change log would be good) that you might have done on each release so that we can better evaluate and integrate them in CNC binding to avoid any issues later.Added list of models changed from M6 Wiki.Closing this ticket.ThanksSahithi |
L3VPN service shows "Unable to fetch interface id always": For "interface-id" field under path ,/l3nm:l3vpn-ntw/vpn-services/vpn-service{B4_Bkp_B4_Sync}/vpn-nodes/vpn-node{P-BOTTOMRIGHT}/vpn-network-accesses/vpn-network-access{Crosswork always displays a message "Unable to fetch interface-id. Please enter a valid interface-id"Kindly suggest,Is there a way "Interface-id" under below path can be learnt and shown as a drop down or can it list available interface values? | Updated Ajitha on the issue. Not CFP issue.UI team looking at the issue |
T-SDN CFP 3.0.0 - PCE-Initiated / PCC-Initiated provisioning flows: Hi All,We are working on an SDN project for Telefonica Germany and Brasil for thecustomization of T-SDN CFP 3.0.0 for L3VPN and L2VPN services withclassic MPLS underlay and TE underlay with these components:VPN Service - IETF L3NM and L2NM ModelsTE Transport - RSVP-TE/IETF-TE Model and SR-TE PolicySDN Orchestration and Automation - CNC 3.0 + SR-PCEThe scope of the project is to have a productized and supported implementation ofNSO + T-SDN CFP 3.0.0 + SDK + CNC suite + SR-PCE + OpenConfig NEDThe project has some complexity in the Automation design and implementationfor the T-SDN CFP 3.0.0 and CNC components alignment/customization, especiallyfor making CNC aware of deviated/customer specific IETF YANG models.please I would need an help to understand the provisioning flows in this setup:CNC (COE+CDG) + NSO + T-SDN CFP 3.0.0 + SR-TEI am looking into the code for T-SDN 3.0 CFP, but cannot find a final flow logicfor the IETF-TE and SR-TE provisioning in case of PCE-Initiated vs PCC-Initiated.Q1) Please do you have a documentation about this?Q2) I found PCE-Initiated JSON payloads, but please do you have an example about PCC-Initiated JSON payloads?Please could you confirm:Q3) For PCE-Initiated policies, is this the flow? > COE + NSO with T-SDN CRUD to SR-PCE with REST API – SR-PCE to devices with PCEPQ4) For PCC-Initiated policies, is this the flow? > COE + NSO with T-SDN CRUD to devices with NSO templates and NED (yellow path in the attached diagram)Q5) Which is the trigger or YANG leaf to determine if the policy should be PCE-Initiated or PCC-Initiated?Q6) For IETF-TE and SR-TE?ThanksRegardsGiorgio | Hi Giorgio,Can we schedule a webex meeting?I can reach out to you on teams.I will be adding Sujay to the meeting. He should be able answer most of your queries. ThanksSahithiUpdate from Giorgio```Hi Sahithi,thanks for the availabilityI have managed to find an explanationI will continue to investigate tomorrow and Friday and let you know early next weekto schedule a call.Regards. Giorgio```Hi Giorgio,Will be closing this ticket since there is no update.ThanksSahithiThe submitter found the explanation for the query in JSD. |
Issues while pushing Y.1731 configs: Wanted to start this thread while Im checking with CFM team about the Y.1731 issues that we are running into in our testbed.We tried the latest function pack and ran into couple of issues:peer-mep status reporting errorsProbes not going through(100% Lost, for Jitter ; Latency)Did you run into these issues while you were testing and validating Y1.731? Wondering if these are specific to our testbed. But I didnt find any such testbed specific issues so far. | Hi Lingesh,Can you provide the payloads that you push? Also which device version and platform that you are test it on?Does the plan show in reached after the configuration is push?Thanks,LinhPlease refer to CDETS: CSCvz21907, for payload detailsY1731 parameter configurations was changed. Please see the recording as guidelineWiki and Recording available here - Solution team need to restest this scenarios with M6 build |
Few RON ML services stuck in Provisioning state and Auto deleted from NSO - Unable to delete them from CNC UI: Hi team,Setup: CNC UI: 10.195.165.76 admin/Public1234!, NSO: 10.195.165.211 nso210/nso210I have created a RON ML service name def from CNC Optical services UI. The service showed success and configuration pushed to devices as well. But in couple of minutes the RON ML service def automatically removed from NSO and CNC UI shows the service in provisioning status. Kindly help troubleshoot.And In response to mail reply, I havent sent any delete request from Restconf. If so, I. believe the service must be deleted from CNC UI as well. | Please check with the team responsible for the server with IPthrough which "def" service delete was issued to NSO as captured in the following NSO audit.log messages. From NSO CFP perspective, the service got deleted as it was requested to.<INFO> 22-Jul-2021::17:41:04.843 nso211 ncs: audit user: nso210/31397 created new session via rest from :58655 with https<INFO> 22-Jul-2021::17:41:04.844 nso211 ncs: audit user: nso210/31397 RESTCONF: request with https: HTTP/1.1The delete notification issue CDETCSCvz11506 is resolved so closing this case.Fixed this issue as part of CSCvz11506 and the fix is available in Aug 13th Build. |
T-SDN L3NM CLI problem with route-policies spaces: In L3VPN CFP (L3NM), when programming a route-policy there is a blank space discrepancy between the CFP template and the outcome in XR when using CLI NED.This is well known when dealing with string leafs.The outcome is that the target devices (Node-4 in this example) are in-sync but compare-config is not empty. This can be fixed by adapting the template with blank spaces to match XR string encoding.Regards,Roqueadmin@ncs> request devices device Node-4 compare-configdiffdevices { device Node-4 { config {route-policy PASS_ALL {- valuepass;+ value" pass"; } } }} | Hi Roque, Can I please get a sample payload for this? Would like to reproduce this on our system. Thank you!Hello Roque, please let us know if we can get a payload for investigating this issue. Thank you!Hi,This ticket has been pending for some time.Please provide a reply by end of week. Otherwise this ticket will be closed.Thanks,Isaac KimHere you have but you can use the dcloud demos for CNC and follow their instructions that it will happen always.admin@ncs> show configuration l3vpn-route-policy VPN-101-ROUTE-POLICYcolor 4001 { ipv4 { prefix [ 30.2.1.0/24 30.2.2.0/24 30.2.3.0/24 ]; }}color 4003 { ipv4 { prefix [ 10.9.0.0/16 10.9.54.0/24 10.9.55.0/24 10.9.56.0/24 30.1.1.0/24 30.1.2.0/24 30.1.3.0/24 ]; }}admin@ncs>admin@ncs> show configuration l3vpn-ntw vpn-profiles valid-provider-identifiers routing-profile-identifier VPN-101-ROUTE-POLICYNo entries found.admin@ncs>admin@ncs> show configuration l3vpn-ntw vpn-services vpn-service vpn-101ie-profiles { ie-profile vpn-101-profile { rd 0:65000:101; vpn-targets { vpn-target 1 { route-targets 0:65000:101; route-target-type both; } } }}vpn-nodes { vpn-node Node-4 { custom-template ct-tpa; local-autonomous-system 65000; vpn-network-accesses { vpn-network-access Node-4-vpn1 { port-id GigabitEthernet0/0/0/1; connection { encapsulation-type tagged-int; tagged-interface { type dot1q; dot1q-vlan-tagged { cvlan-id 101; } } } ip-connection { ipv4 { address-allocation-type static-address; static-addresses { primary-address Node-4-vpn1-ipv4-address; address Node-4-vpn1-ipv4-address { provider-address 30.1.2.1; prefix-length 24; } } } } routing-protocols { routing-protocol Node-4-routing { type bgp; bgp { peer-autonomous-system 65003; address-family [ ipv4 ]; redistribute-connected-ipv4-af; neighbor [ 30.1.2.2 ]; } } } } } node-ie-profile vpn-101-profile; } vpn-node Node-5 { custom-template ct-tpa; local-autonomous-system 65000; vpn-network-accesses { vpn-network-access Node-5-vpn1 { port-id GigabitEthernet0/0/0/1; connection { encapsulation-type tagged-int; tagged-interface { type dot1q; dot1q-vlan-tagged { cvlan-id 101; } } } ip-connection { ipv4 { address-allocation-type static-address; static-addresses { primary-address Node-5-vpn1-ipv4-address; address Node-5-vpn1-ipv4-address { provider-address 30.1.1.1; prefix-length 24; } } } } routing-protocols { routing-protocol Node-5-vpn1-routing { type bgp; bgp { peer-autonomous-system 65003; address-family [ ipv4 ]; redistribute-connected-ipv4-af; neighbor [ 30.1.1.2 ]; } } } } } node-ie-profile vpn-101-profile; }}service-assurance { monitoring-state enable; profile-name "Gold_L3VPN_ConfigProfile system"; rule-name "Rule-L3VPN-NM system";}admin@ncs>admin@ncs> request devices device Node-5 compare-configdiff devices { device Node-5 { config { route-policy PASS_ALL {- value pass;+ value " passrn"; } } } }admin@ncs> request devices device Node-4 compare-configdiff devices { device Node-4 { config { route-policy PASS_ALL {- value pass;+ value " passrn"; } } } }admin@ncs>Thank you for the information Roque. An internal ticket has been created for this issue, Closing this ticket as all further tracking will be under CDETSIssue will be fixed as part of CDETS |
Need instructions on how to verify all of the "load merge" from configure bootstrap data.: Under installation - for configure bootstrap data and configure common bootstrap data, there are many 'load merge' commands need to be executed - some may or may not show any error but at the end, user may not know if all of the xml got load merged correctly or not - it would be very helpful to know some "show" command to verify this steps to ensure all of the xml were load merged. | If you look at the contents of the XML files, then you can run show commands based on that. You can also do a `commit dry-run` to check if the output matches the payload you're trying to load mergehi Reginald, there are more than 30 xml files - if we have to do a show command for each - this is not very practical way. would be good to know the show command for each block of load merge (i.e notification, kicker, etc..) Also some show command will need to have "hide/unhide tsdn" or "hide/unhide debug" prior to the 'show' command which we are not aware of. Please provide a better for user to verify during installation process. Thanks and regards!If you need to do an `unhide/hide` to load merge the payloads then you would need it for the show commands as well. You're best bet is to check before commit. Either a `commit dry-run` or `show | compare` (Juniper CLI) or `show configuration diff` (Cisco CLI).Thanks,RegiThanks Reginald for your input - the issue here is after installation and something went wrong - we would not know which command to use to verify all of the load merged were done correctly - for example - we were using LSA setup and all of the service got stuck in 'in-progress' state - we opened the ticket, , for the issue and found out that the notification-kicker was not load merged correctly or missing - so for user, it is not straight forward to know which notification is needed or which one to check with 'show' cmd. Please try to look at the issue from user point of view since it maybe obvious to nso developer to know but not the user. Thanks and regards!For now, you can do something like `commit dry-run outform xml` and the output shouldn't be too different from the bootstrap xml you're trying to load merge. You can even go ahead and verify the configs after commit. If look the the bootstrap XML files such as the kickers for example take a look at the parent tag you'll see its "kickers". as such you can do "show running-config kickers | display xml" (Cisco CLI) or "show kickers | display xml" (juniper). Just be aware if you had to do an `unhide debug` for the payload you merged then you'll need to do that as well for "show" command assuming you already ran "hide debug".In the meantime, I'll go ahead and create an internal ticket to update the documentation to add some verification for the bootstrap configs.Thanks,RegiDocumentation was updated as of M4. Closing this ticket now. |
Unable to create slice with QoS policy in template: Hi,I have tried to create slice using the template but it resulted in below error.Is there any day0 configuration has to be configured in device apart from BGP.Method failedreason: External error in the NED implementation for device xrv9k-27: Thu Dec 1 18:33:28.834 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/2 service-policy input input-policy !!% 'policy-lib' detected the 'warning' condition 'Policy-map not found' ! end | Hi Naveen,Yes, you need to configure policy-map and this should match QoS name.Below is what mentioned in wiki as well:QoS Policies defined in the following payload reference policy-maps which are expected to have been configured by the user beforehandThanks,NikhilProvided the required information to the user. Same is mentioned in the wiki as well.Can you provide sample configs to configure QoS policy map ?You just need to configure a policy map which matches the QoS name being configuredadmin@ncs(config)# devices device PIOSXR-0 config policy-mapIt looks like some more configs are required apart from policy-map,nso@ncs(config)# devices device xrv9k-25 config policy-map input-policynso@ncs(config-pmap)# devices device xrv9k-27 config policy-map input-policynso@ncs(config-pmap)# commit% No modifications to commit.And slice creation resulted in below error.External error in the NED implementation for device xrv9k-27: Thu Dec 1 20:46:42.833 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/2 service-policy input input-policy !!% 'qos-ea' detected the 'warning' condition 'Ingress queueing features is not supported' ! endAs discussed over teams,ingress QoS isn't supported on this device.User was able to successfully create the slice service using output-policy only.Thanks Nikhil |
CFP Upgrade on NSO LSA set-up: Hi Team,I am looking for information on CFP upgrade support from 4.0 FCS to 5.0-M4 on NSO LSA Set-up. Is there any link that I can refer to.Thanks,Kanchan | Spoke to Van. It seems we haven't updated the documents yet. Most likely it will be added as part of M5Hi Kanchan,Documentation will be added as part of M5Thanks,RegiSure, Thanks Regi |
L2vpn-Service is giving the full path instead of the feild name : /l2vpn-ntw:l2vpn-ntw/vpn-services/vpn-servicegetSchema api sending the full path url instead of field name and please find the attached screen shot | There are few more changes also need confirmation in VPN service is these are expected chnages and been added as part of some modal changes ? 1. New Leaf node is been added :name : vpn-type {kind: "leaf", name: "vpn-type", qname: "l2vpn-ntw:vpn-type", info: {string: "Service type."},}deps: info: {string: "Service type."}kind: "leaf"name: "vpn-type"qname: "l2vpn-ntw:vpn-type"type: {namespace: "urn:ietf:params:xml:ns:yang:ietf-l2vpn-ntw", name: "t551244651"}2. Leaf been removed in M3 {kind: "leaf", name: "vpn-svc-type", qname: "l2vpn-ntw:vpn-svc-type", info: {string: "Service type."},}access: {create: true, read: true, update: true, delete: true, execute: false}info: {string: "Service type."}kind: "leaf"name: "vpn-svc-type"qname: "l2vpn-ntw:vpn-svc-type"type: {namespace: "urn:ietf:params:xml:ns:yang:ietf-l2vpn-ntw", name: "t2237769791"}name: "t2237769791"namespace: "urn:ietf:params:xml:ns:yang:ietf-l2vpn-ntw". Hi Kirandeep,Regarding vpn-type and vpn-svc-type : The IETF-L2NM models have been completely refactored due to updating to the latest draft in M2. vpn-svc-type was changed to vpn-type during this update. Please refer to the M2 Model and Payload changes page for more details.Regarding 'evaluate_when_entries' attribute : As per the JSON RPC documentation : The evaluate_when_entries param signals that schema entries should be included in the schema even though their "when" or "tailf:display-when" statements evaluate to false, i.e. instead a boolean evaluated_when_entry param is added to these schema entries. i will check more on this attribute and update you.Regards,Nishad Subair.Hey Nishand, can you please update regarding the new attribute added and name is not coming correctly. Thanks KirandeepHi Kirandeep,We will check this and update you.Regards,Nishad SubairHi Kirandeep,We have raised a RT with the NSO platform team and will let you know once we hear anything from them.Regards,Nishad Subair.Hi Kirandeep,RT has been resolved and the fix is available in the NSO build : 6.1_230206.110843541.f67ad1e6cc9d.Please verify.Thanks And Regards,Nishad Subair. |
Day0 configs required for Dynamic MVPN provisioning: Hi Team,From the wiki: and The payloads that are shared in the TSDN wiki shows all node has is-receiver-site-only set to true, for root node it shouldn't it be false.<multicast xmlns="http://cisco.com/ns/nso/fp/examples/cisco-l3vpn-ntw"> <is-receiver-site-only>true</is-receiver-site-only></multicast>Also, pre-req for the device config only shows:multicast-routing address-family ipv4 interface Loopback0 enable ! mdt source Loopback0 !router bgp 1 address-family ipv4 mvpn!But when I tried to create Dynamic MVPN, I had to include`address-family ipv4 mvpn` in all neighbors under bgp configuration.Under PCE: pce -> segment-routing -> traffic-eng p2mp label-range min 15400 max 60000 fast-reroute lfaWithout defining the range, PCE won't be able to assign label.Can we update the wiki the above details.Thanks,Kanchan | Hi Kanchan,1 : Regarding is-receiver-site-only .The payloads that are shared in the TSDN wiki shows all node has is-receiver-site-only set to true (leaf nodes). For root node it should be false. i will update the wiki by adding a case for root as well.2 : Regarding PCE configs and address-family ipv4 mvpn ,We have these prerequisites received from the device team .Also It is expected from the user to know the day0 config for MVPN.Thanks And Regards,Nishad Subair.Hi Nishad, Once you make the changes in the wiki, can you provide me the link so I can get the payload.Thanks,Kanchan |
Unknown element "rd" while slice provisioning: Hi,I'm trying to provision a slice.I've set the "rd-type" as "manual" in global settings.Now i'm trying to pass the value for "rd" inside "sdp".Ex: "rd": "0:65001:300"I'm getting error:{ "ietf-restconf:errors": { "error": [ { "error-type": "application", "error-tag": "malformed-message", "error-path": "/ietf-network-slice-service:network-slice-services", "error-message": "unknown element: rd in /ietf-nss:network-slice-services/ietf-nss:slice-service[ietf-nss:service-id='Test-Dedic-530']/ietf-nss:sdps/ietf-nss:sdp[ietf-nss:sdp-id='1']/ietf-nss:rd" } ] }} | Hi,You need to configure rd-type = manual to configure per SDP: <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"><pre>admin@ncs% show network-slice-services global-settings rd-type | display json { "data": { "ietf-network-slice-service:network-slice-services": { "cisco-network-slice-service:global-settings": { "rd-type": "manual" } } }}</pre></div></div>Thanks,Regi |
BiDirectional info is missing in PCC while provisioning Circuit style policy using NSO: Hi,I have tried to configure Circuit Style policy using NSO but bidirectional info is missing in PCC though I have provided it in UI.This is a mandatory data to be passed such that CNC will be able to discover it as Circuit style policy.Kindly check and let us know.Setup: 172.27.226.119 ( nso/Vtsisco@123!)Thanks,Naveen | HI Naveen,Please provide more details like the steps followed including payload used , expected config .Regards,Nishad Subair.Hi Nishad,The below link contains config required to create Circuit style policy.The service is still available in my setup.Kindly take the payload from NSO UI.Setup: 172.27.226.119 ( nso/Vtsisco@123!)It would be better if you check with XR team as well.Thanks,NaveenHi Naveen,I was able to confirm this is due to a bug in template mapping for NC 7.8 NED. It will be fixed for the upcoming TSDN 5.0 M3 release.In the meantime, I would advise to try to use XR CLI NED for CS SR-TE. Bidirectional and other config should work fine for XR CLI NED.Thanks,Isaac KimFixed in TSDN 5.0 M3 |
RESTCONF DELETE operations fail and return status 400: We are using postman to send RESTCONF CREATE and DELETE operations to NSO server. While CREATE operations seem to be working as expected, DELETE operations fail when a bulk of operations is sent (about 10 or so) to server producing error "400 Bad request".The DELETE operations are usually successful on the next iteration, with no zombies or other issues found with the removed service. | Hello, thank you for the ticket. We are investigating this issue and will get back to you with further updates.Hello, Can you please provide the request command being used to Single and Bulk Delete the Services. Thank you.Hi,The CREATE ; DELETE operations we are using can be found in the following Postman collection: You can use a Postman runner to run them as bulk.ShlomiHi Sholmi,We are not aware the Restconf operations on NSO platform related bulk delete. Please see if you can file a ticket with NSO platform for the "Bad Request" Error.Hi Sahithi,I'm talking about normal CREATE ; DELETE RESTCONF NSO operations that are simply ran a few at a time, not about a bulk delete operation.Regards,Shlomi |
can CS internal policy editable : 1. created CS policy form NSO UI . 2. NSO created two internal policies . 3. edit bandwidth of one internal policy.4. commit was successful. 5. But It was not reflecting the updated bandwidth to the internal policy.are we supporting the edit of internal CS policies ? | Hi Kirandeep,Internal CS services cannot be modified from internal service. Please use top level service to modify.Please suggest if this answers the question.Regards,Nishad Subairok thank you for update so is their any error message when we try to edit ?As discussed , closing the ticket.We need to use the top level service to modify. |
Does not able to see devices: Does not able to see devices in the CFSadmin@ncs% request devices lsa dispatch-map sync remote-nso rfs-1success truedetail Dispatch Map Synced Successfullyadmin@ncs% request devices lsa dispatch-map sync remote-nso rfs-2success truedetail Dispatch Map Synced Successfullyadmin@ncs% request devices lsa dispatch-map sync remote-nso rfs-3success truedetail Dispatch Map Synced Successfullyadmin@ncs% show devices lsa dispatch-mapdevice rfs-1 { ned-id cisco-nso-nc-6.1:cisco-nso-nc-6.1;}device rfs-2 { ned-id cisco-nso-nc-6.1:cisco-nso-nc-6.1;}device rfs-3 { ned-id cisco-nso-nc-6.1:cisco-nso-nc-6.1;}admin@ncs%admin@ncs> show packages package package-version PACKAGENAME VERSION--------------------------------------------------------------cisco-aa-service-assurance 5.0.0cisco-cs-sr-te-cfp 5.0.0cisco-flat-L2vpn-fp-internal-ned 5.0.0cisco-flat-L3vpn-fp-internal-ned 5.0.0cisco-internet-access-service-fp 5.0.0cisco-internet-access-service-fp-internal-ned 5.0.0cisco-nso-nc-6.1 6.1cisco-pm-fp 5.0.0cisco-pm-fp-internal-ned 5.0.0cisco-rsvp-te-fp-internal-ned 5.0.0cisco-sr-te-cfp 5.0.0cisco-sr-te-cfp-internal-ned 5.0.0cisco-tsdn-core-fp-common 5.0.0core-fp-common 1.31.0core-fp-common-ned 1.0core-fp-plan-notif-generator 1.0.7custom-template-utils 2.0.10custom-template-utils-ned 1.0cw-dlm-fp 5.0.0-nso-6.1ietf-l2vpn-nm 5.0.0ietf-l3vpn-nm 5.0.0ietf-network-slice-service 5.0.0ietf-te-fp 5.0.0lsa-utils 1.0.1lsa-utils-ned 1.0resource-manager 4.0.1admin@ncs> show cluster connectionREMOTE LOCAL REMOTENODE ADDRESS PORT CHANNELS USER USER STATUS TRACE-------------------------------------------------------------------------rfs-3 172.28.174.227 2022 - admin admin up disabledrfs-1 172.28.174.225 2022 - admin admin up disabledrfs-2 172.28.174.226 2022 - admin admin up disabledadmin@ncs>NSO IP: 172.28.174.224 admin/Ovatest123@Packages Used for deployment:<del>rw-rw-r</del>- 1 admin admin 208291308 Dec 14 01:18 ncs-6.1_221212.150815390.4b4cc38b0df7.linux.x86_64.installer.bindrwxrwxr-x 4 ubuntu ubuntu 4096 Dec 16 16:54 nso-6.1_221212-tsdn-5.0.0-M5-NSO-Engg-1<del>rw-rw-r</del>- 1 admin admin 1214965885 Dec 16 17:31 nso-6.1_221212-tsdn-5.0.0-M5-NSO-Engg-1.tar.gz<del>rw-rw-r</del>- 1 admin admin 46984697 Dec 20 19:05 cw-na-dlm-fp-5.0.0-nso-6.1-eng.tar.gzdrwxrwxr-x 2 admin admin 4096 Jan 9 04:46 cluster_deployadmin@ubuntu2004:~$ pwd/home/adminThanks,Dinesh | RFS-1 - 172.28.174.225 admin/Ovatest12@RFS-2 - 172.28.174.226 admin/Ovatest12@RFS-3 - 172.28.174.227 admin/Ovatest12@Hi Dinesh, That is expected since you don't have any device on RFS-1, RFS-2, and RFS-3.RFS-1:admin@ncs> show devices listNAME ADDRESS DESCRIPTION NED ID ADMIN STATE-----------------------------------------------admin@ncs> exitadmin@ubuntu2004:~$ exitlogoutConnection to 172.28.174.225 closed.RFS-2:admin@ncs% run show devices listNAME ADDRESS DESCRIPTION NED ID ADMIN STATE-----------------------------------------------admin@ncs% exitadmin@ncs> exitadmin@ubuntu2004:~$ exitlogoutConnection to 172.28.174.226 closed.RFS-3:admin@ncs> show devices listNAME ADDRESS DESCRIPTION NED ID ADMIN STATE-----------------------------------------------admin@ncs> exitadmin@ubuntu2004:~$ exitlogoutConnection to 172.28.174.227 closed.LINLY-M-5617:~ linly$ ssh [email protected] you ONLY see RFS-x from device list in CFSadmin@ncs% show devices lsa dispatch-mapdevice rfs-1 { ned-id cisco-nso-nc-6.1:cisco-nso-nc-6.1;}device rfs-2 { ned-id cisco-nso-nc-6.1:cisco-nso-nc-6.1;}device rfs-3 { ned-id cisco-nso-nc-6.1:cisco-nso-nc-6.1;}Regards,LinhHi Linh,The RFS'are not learning the devices when I tried to onboard them. The CFS shows the no of RFS. But RFS does not shows any devices onboarded.Below is the error shown in my applicaiton.Nso Device Fetch Ssh Keys failed due to connect to NSO nsoRFS1Thanks,DineshIt seem you use dlm package to onboard device, but I saw a lot of dlm error on ncs.log<CRIT> 9-Jan-2023::21:53:15.754 ubuntu2004 ncs: - no registration found for callpoint dlm-port-config/service_create of type=external<CRIT> 9-Jan-2023::22:02:06.381 ubuntu2004 ncs: - no registration found for callpoint dlm-port-config/service_create of type=external<CRIT> 9-Jan-2023::22:02:27.270 ubuntu2004 ncs: - no registration found for callpoint dlm-port-config/service_create of type=external<CRIT> 9-Jan-2023::22:02:47.852 ubuntu2004 ncs: - no registration found for callpoint dlm-port-config/service_create of type=external<CRIT> 9-Jan-2023::22:03:08.367 ubuntu2004 ncs: - no registration found for callpoint dlm-port-config/service_create of type=external<CRIT> 9-Jan-2023::22:03:28.905 ubuntu2004 ncs: - no registration found for callpoint dlm-port-config/service_create of type=external<CRIT> 9-Jan-2023::22:14:29.433 ubuntu2004 ncs: - no registration found for callpoint dlm-port-config/service_create of type=external<CRIT> 9-Jan-2023::22:14:49.893 ubuntu2004 ncs: - no registration found for callpoint dlm-port-config/service_create of type=external<CRIT> 9-Jan-2023::22:15:10.412 ubuntu2004 ncs: - no registration found for callpoint dlm-port-config/service_create of type=externalAlso dlm package is not up. Please see the attached screen shotI just restart RFS-1 with this commandsudo NCS_RELOAD_PACKAGES=force /etc/init.d/ncs restartand the packages on RFS-1 are up.Please do the same for RFS-2 and RFS-3 to bring up all packages on these RFS.Then try to onboard devices again.Thanks,LinhHi Linh,This has fixed my issue. Thank you very much.. |
l2vpn nm daemon down in scale setup: Our scale setup has 25K devices with 185K VPN services. While creating L2VPN creation scripts, L2VPN daemon comes down after 2K services. Each service has 5 EP. In earlier release, it was 2 EP, and never saw this issue. We see this issue twice, and restarted NSO and moved on. This needs to be investigated.<CRIT> 12-Jan-2023::20:08:51.275 scale-nso2-CFS-133 ncs: - Daemon ncs-dp-2710-ietf-l2vpn-nm:main:9 timed out<INFO> 12-Jan-2023::20:54:25.673 scale-nso2-CFS-133 ncs: - Smart Licensing evaluation time remaining: 67d 16h 18m 0sSetup: 172.20.63.133UI, CLI: cnctest/Ovatest123@scale setup is updated with higher no. of open files, user process swap etc. | Hi Rama,This is know issue and has been fixed in NSO 6.0.1 .Please move to NSO and let us know if you still this.ThanksPriyankaHope this fix will be available in 6.1 as well. i am planning to use it. |
After upgrade from NSO 555 bootstrap failed on IETF-L2NM and IETF-L3NM: Will be attaching more logs soon.Ping me for testbed access.User admin last logged in 2022-10-14T01:01:32.190001+00:00, to nso-552-to-574-1, from 10.10.30.5 using cli-sshadmin connected from 10.10.30.5 using ssh on nso-552-to-574-1admin@ncs# config tEntering configuration mode terminalCurrent configuration users:nsoadmin https (webui from 20.20.10.141) on since 2022-10-13 18:04:23 terminal modeadmin@ncs(config)# unhide debugadmin@ncs(config)# load merge IETF-L2NM-AA-notification-settings.xmlLoading.Error: on line 2: unknown element: service-path-for-subscription in /cisco-aa-service-assurance:service-path-for-subscriptionadmin@ncs(config)# load merge IETF-L3NM-AA-notification-settings.xmlLoading.Error: on line 2: unknown element: service-path-for-subscription in /cisco-aa-service-assurance:service-path-for-subscriptionadmin@ncs(config)# load merge L2VPN-AA-notification-settings.xmlLoading.Error: on line 2: unknown element: service-path-for-subscription in /cisco-aa-service-assurance:service-path-for-subscriptionadmin@ncs(config)# load merge L3VPN-AA-notification-settings.xmlLoading.Error: on line 2: unknown element: service-path-for-subscription in /cisco-aa-service-assurance:service-path-for-subscriptionadmin@ncs(config)# commit% No modifications to commit.admin@ncs(config)# admin@ncs(config)# | Had session with Priyankai tried with unhide tsdn and it worked fine.Closing ticket since issue is resolved |
Scale -Plan completion Stuck -Plan completion Not happening for L2vpn services.( 1250 services created and 1250 services creation is running): Hi Team,We are trying to stabilize the XRV9K devices for the scale VPN count, We have 60 device topology, Initially, we created services for only 10 devices, and all the services are provisioned and it moved to success on the Crosswork, Later we powered ON 10 more devices and synced the devices to NSO and created 1250 L2vpn P2P services, but the Plan completion Not happening for those 1250 services. Attached are the service details. Please take a look at the issue.Please reach me for the setup details, I will unicast the details since it's a scale setup.FYI: We observed the issue after powering ON and provisioning the services, we didn't see any issue for the first 10 devices, It was already in the powered ON state and we provisioned the services. | Hi., This is blocking us to proceed further.can someone take a look on this issue?Thanks,Arun.M.GHi Ragesh,We see that a lot of netconfs are loaded in the setup which would be impacting the performance. Please delete all the netconfs if they are not being used along with the multi-vendor packages. This would help to increase the plan completion turnaround time.Please help us with the following information as well:- What is the test strategy?- How many and what kind of devices are being used? Are the devices shared across services and are they hosted on same or different server?- What is the plan wait time?- How many lines of config is pushed by each service?- What is the payload being used?Thanks,NikhilHi NIkhil,this is NSO LSA setup. and customer might have all NEDs configured.,when there is Unused NEds, why does the performance impacts? anyhow, the NEDs are unused. lets have a webex meeting to do that together as i dont want to end up in some unexpected things to happen.Below are the answers for your queries.<ul class="alternate" type="square">What is the test strategy? >> Actually we have a 60 devices topology having 48 PE devices and 12 Core devices includes 2 XTC and 2 RR . all devices having default resources 4vCPu, 16GB Ram and 64gb HD. All are Xrv9k devices that are created in Single UCS. It has the devices versions mixed with 7.7.1, 7.3.2, 7.5.2.while having all devices switched on, we were not able to scale more than 500 services ( 160 p2p, 160 evpn, 180 L3vpn vrf)so, to scale more , we switched off all devices except 10 PE devices and 12 core devices. we were able to reach 2k services per device pair. ( 2k was our target to reach per device pair)then. switched on another set of 10 PE devices, and started creating services and we ended up in this issue where Plan completion got stuck for 6 hours and after that , it started happening very very dead slow.Attached image has devices pairs and the count of services.<ul class="alternate" type="square">How many and what kind of devices are being used? Are the devices shared across services and are they hosted on same or different server?<ul class="alternate" type="square">What is the plan wait time? >> as per the script, we have 30 seconds interval between the services creation. it will take 2.5 hours to create 1250 services. ( 250 services between 5 pair of services).<ul class="alternate" type="square">How many lines of config is pushed by each service?it is as normal L2vpn p2p, l2vpn evpn service payload with 2 endpoints.<ul class="alternate" type="square">What is the payload being used?Attached payloads. Advised the user to remove the unused NEDS and related multi-vendor packages from the system to improve the performance.This is actually Bug in the product and it is valid scenario.not accepting that this has been moved to Invalid.removing the unused NEDs is just a workaround. not a real solution.when the neds are ununsed ,why does it impacts the performance. this is bug .CSCwd26703 is being tracked for this. There is a ticket already in progress with the platform for this issue. We will update CSCwd26703 once we get a solution from the platform team. Closed this ticket since we already have a bug open for this to track the progress. |
NSO Actions - need restconf URL for cleanup, syncfrom and syncto actions: Hi,Working on NSO actions using restconf.Actions:clean-upsync-fromsync-tothe restconf URL will be,https://<hostip:port>/crosswork/proxy/nso/restconf/data/<model-path>For Transport Slicing, what path should be supplied?Sample model-path for L2VPN:clean-up:/ietf-l2vpn-ntw:l2nm-actions/cleanupsync-from ; sync-to:/ietf-l2vpn-ntw:l2nm-actions/error-recovery | Hi Magesh,You can use the following for transport slicing:Cleanup:<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"><pre>/restconf/data/ietf-network-slice-service:network-slice-services/cisco-network-slice-service:actions/cleanup</pre></div></div>Inputs:<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"><pre> | +---x cisco-nss:cleanup | | +---w cisco-nss:input | | | +---w cisco-nss:service -> /network-slice-services/cisco-nss:slice-service-plan/service-id | | | +---w cisco-nss:sdp* -> /network-slice-services/cisco-nss:slice-service-plan/plan/component/name | | | +---w cisco-nss:no-networking boolean</pre></div></div>Error Recovery:<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"><pre>/restconf/data/ietf-network-slice-service:network-slice-services/cisco-network-slice-service:actions/error-recovery</pre></div></div>Inputs:<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"><pre> | +---x cisco-nss:error-recovery | +---w cisco-nss:input | | +---w cisco-nss:service -> /network-slice-services/cisco-nss:slice-service-plan/service-id | | +---w cisco-nss:sync-direction enumeration</pre></div></div>Let me know if you need anymore help.Thanks, RegiThanks Reginald. Let me check and confirmHi,In clean-up, we have one parameter,<div class='table-wrap'><table class='confluenceTable'><tbody><tr><td class='confluenceTd'> </td><td class='confluenceTd'> </td><td class='confluenceTd'> +---w cisco-nss:sdp* -> /network-slice-services/cisco-nss:slice-service-plan/plan/component/name</td></tr></tbody></table></div>Do we need to pass the "sdp-id" of the particular service?Hi,If we have to pass the SDP IDs then do we need to pass all the SDP ids for the service?Hi,I tried the below URL,payload and got the response.URL:https://<ip>/crosswork/proxy/nso/restconf/data/ietf-network-slice-service:network-slice-services/cisco-network-slice-service:actions/cleanuppayload:{ "no-networking": false, "service": "Dedic-520", "sdp" : }"0","1","2" are the SDP-IDs for the service "Dedic-520".Response:{ "cisco-network-slice-service:output": { "success": false, "detail": "Cleaning up IETF NSS service: Dedic-520 nn Removing service /network-slice-services/slice-service{Dedic-520}/sdps/sdp{0}n Removed service /network-slice-services/slice-service{Dedic-520}/sdps/sdp{0}n Removing service /network-slice-services/slice-service{Dedic-520}/sdps/sdp{1}n Removed service /network-slice-services/slice-service{Dedic-520}/sdps/sdp{1}n Removing service /network-slice-services/slice-service{Dedic-520}/sdps/sdp{2}nERROR: too few elems (15): too few /ietf-nss:network-slice-services/slice-service{Dedic-520}/sdps/sdp, 0 configured, at least 1 must be configurednSTATUS_CODE: TSDN-IETF-NSS-503nREASON: Cleanup failednCATEGORY: custom-actionnSEVERITY: ERRORnContext n" }}So, i got some response. Even though, its not success, can i assume that the payload is correct and NSO does some action on it?You're not required to input sdp-id. The sdp-id is only need if you want to cleanup a specific component, but if you're trying to cleanup the entire service then you do not need to define the sdp-idThanks,RegiThanks Regi |
Slice Service Details not returning connectivity type: Hi,While fetching the slice service details, connectivity-type attribute of connection-groups section is not being returned, when connectivity-type is "any-to-any". Its returning when connectivity-type is not "any-to-any". Earlier it was returning irrespective of connectivity-type.json response for non "any-to-any":"connection-groups": { "connection-group": [ { "connection-group-id": "Default", "connectivity-type": "ietf-vpn-common:hub-spoke" } ] }json response for "any-to-any":"connection-groups": { "connection-group": [ { "connection-group-id": "Default" } ] } | Hi Magesh,Are you using JSON RPC or Restconf? Can you please provide the request and slice payload?Thanks,RegiNo response from reporter. Closing the ticket.Thanks,Regi |
Not able to clean up zombies on RFS node: Not able to clean up zombies on the RFS node ; provisioning also fails since zombies on the RFS node.admin@ncs# show zombies servicePossible completions: /flat-L3vpnadmin@ncs# show zombies servicePossible completions: /flat-L3vpn /sr-te/cisco-sr-te-cfp-sr-policies-internal:policies/policyPlease provide the commands to clean up zombies on RFS node.CFS -10.194.63.169RFS1 -10.194.63.170RFS2 -10.194.63.242Credentials: admin/Vtsisco@123! | Hi Ragesh,I did clean up zombies in RFS1 with these commandsadmin@ncs% unhide tsdnadmin@ncs% request tsdn-common-actions zombie-cleanup zombie-path /flat-L3vpn force true########################<ol>Warning #########################You are about to forcefully cleanup a zombie which may result in undetermined behavior.Are you sure you want to proceed? yessuccess truedetail Starting zombie cleanup Removing zombie service: /ncs:zombies/ncs:service{"/flat-L3vpn[name='L3NM-L3VPN_NM-SID-90-internal'][endpoint-name='TB2-PE-A_1']"} Removed zombie serviceZombie cleanup finished</ol>admin@ncs% run show zombies% No entries found.Thanks Linh for the info, but still I am not able to create service, looks the plan is not cleaned. No zombies on the nso.Fri Feb 25 18:39:11 IST 2022:DEBUG: << " "error-message": "RPC error towards rfs-1: operation_failed: Operation failed because: Service plan ('/flat-L3vpn-internal/flat-L3vpn-plan') already exists: '/flat-L3vpn'""admin@ncs# show zombies service% No entries found.admin@ncs#Somehow the internal plan in rfs1 is still dangling aroundadmin@ncs> show flat-L3vpn-internal flat-L3vpn-plan L3NM-L3VPN_NM-SID-90-internal POST BACK ACTIONTYPE NAME TRACK GOAL STATE STATUS WHEN ref STATUS----------------------------------------------------------------self self true - ready not-reached - - - plan failed plan error-info message "Operation failed because: Service plan ('/flat-L3vpn-internal/flat-L3vpn-plan') already exists: '/flat-L3vpn'"These are steps to clean the internal plan left behind. 1. Save the internal plan to xml fileadmin@ncs> show flat-L3vpn-internal flat-L3vpn-plan L3NM-L3VPN_NM-SID-90-internal | display xml | save plan_issue.xml2. Exit ncs_cli prompt and edit plan_issue.xml then add operation="delete" in <flat-L3vpn-plan> <config xmlns="http://tail-f.com/ns/config/1.0"> <flat-L3vpn-internal xmlns="http://cisco.com/ns/nso/fp/examples/cisco-tsdn-flat-L3vpn-internal"> <flat-L3vpn-plan operation="delete"> <name>L3NM-L3VPN_NM-SID-90-internal</name> . .3. Use ncs_load to delete the planadmin@nso-10-194-63-170:~$ ncs_load -l -m -O plan_issue.xmlVerify the internal plan is delete admin@ncs> unhide tsdnadmin@ncs> show flat-L3vpn-internal flat-L3vpn-plan L3NM-L3VPN_NM-SID-90-internal----------------------------------------------------------------------------------^syntax error: unknown argumentAs you see the internal plan was deleted after thatHi Ragesh,I don't see any update regarding to this issue. I will close this ticket in next few days.Thanks,LinhThanks Linh, please close the ticket |
Issue with Dispatch map in LSA utils: Hi CFP team,For tm-tc fp, we tested our changes using dispatch map from core-fp-common package.admin@ncs% show dispatch-map dispatch-map 10.64.96.113 { ned-id cisco-iosxr-cli-7.38:cisco-iosxr-cli-7.38; rfs-node rfs-1;}dispatch-map rfs-1 { ned-id cisco-nso-nc-5.7:cisco-nso-nc-5.7;}admin@ncs% If Im not wrong, the limitation with this dispatch map is that there is no sync option and it gets updated only by Netconf notifications enabled. I went through srte fp, looks like you moved to dispatch map from lsa utils package. What is expectation from user with respect to dispatch map. Is it okay enforce them to add devices only after setting up Netconf notifications between CFS and RFS or are we supposed to use the dispatch map from LSA utils package.Im facing issues using dispatch map from lsa utils. I replaced the node information frompath "/core-fp-common:dispatch-map/core-fp-common:device" to "/ncs:devices/lsa-utils:lsa/lsa-utils:dispatch-map/lsa-utils:device/lsa-utils:name"Sometimes, the variable information I set in template is not getting settime="2022-03-08 01:27:35.745495" level=error msg=""or I see an illegal reference error. Can someone help me debug this issue.Regards,Moksha | Hi Raja,Dispatch-map primarily gets updated with netconf-notifications. We do have sync option as well.Below action can be used to sync dispatch map from the CFS NODE request devices lsa dispatch-map sync remote-nso <rfs-node-name>Please resolve this issue. Thnx |
Non json formatted notifications being transmitted to CNC: Non json formatted notifications being transmitted to CNC:{ "ietf-restconf:notification": { "eventTime": "2022-03-25T17:29:48.494948+00:00", "tailf-ncs:plan-state-change": {"service": /ietf-l3vpn-ntw:l3vpn-ntw/vpn-services/vpn-service[vpn-id='0-65008740'],<<--- Missing enclosing the value "component": "DEVLF1SLR02_23", "state": tailf-ncs:ready, "operation": "modified", "status": "reached" } }} | Hello, Can we please get information on the setup where this error is present. Thank you!What information do you need..?NSO 5.4.4.1CNC 2.xPackages:NAME VERSION ---------------------------------------alu-sr-cli-8.22 8.22.2 cisco-flat-L2vpn-fp 2.0.0 cisco-flat-L2vpn-fp-internal 2.0.0 cisco-flat-L3vpn-fp 2.0.2 cisco-flat-L3vpn-fp-internal 2.0.4 cisco-ios-cli-6.67 6.67.8 cisco-iosxr-cli-7.33 7.33.20 cisco-iosxr-nc-7.3 7.3.1 cisco-rsvp-te-fp 2.0.1 cisco-sr-te-cfp 2.0.0 cisco-sr-te-cfp-internal 2.0.0 cisco-tsdn-core-fp-common 2.0.0 core-fp-common 1.11.0 core-fp-delete-tag-service 1.0.2 core-fp-plan-notif-generator 1.0.0 custom-template-utils 2.0.5 cw-device-auth 1.0.0 dlm 4.0 flat-l2vpn-multi-vendors 2.0.0 flat-l3vpn-multi-vendors 2.0.0 flat-l3vpn-nokia 2.0.1 ietf-l2vpn-nm 2.0.0 ietf-l3vpn-nm 2.0.5 ietf-te-fp 2.0.0 resource-manager 3.5.4 rsvp-te-multi-vendors 2.0.0 sr-pce 1.0 sr-te-multi-vendors 2.0.0 tailf-hcc 5.0.2 The error appears when we deploy, modify, delete a service in the notification stream to CNC which rejects it as its not a valid JSOn format. Attaching email summary from Liran who helped diagnose the issue. Hello,Thank you for the above info.If possible I would like access to the NSO that has this error so I can run some commands to check the error.If not possible, please attach the payload of this service to this ticket.If you can propose a time during CET business hours I can possibly give you access via a screen share, as this is a customer deployment there is no generic cisco access without customer remote access clients.Any service creation (payload example) seems to trigger the malformed JSON service field in the RESTCONF notification message sent to CNC.Example:{ "ietf-restconf:notification": { "eventTime": "2022-03-25T17:29:48.494948+00:00", "tailf-ncs:plan-state-change": {"service": /ietf-l3vpn-ntw:l3vpn-ntw/vpn-services/vpn-service[vpn-id='0-65008740'], "component": "DEVLF1SLR02_23", "state": tailf-ncs:ready, "operation": "modified", "status": "reached" } }}The issue in the above format is missing enclosing quotes in: /ietf-l3vpn-ntw:l3vpn-ntw/vpn-services/vpn-service should be "service": "/ietf-l3vpn-ntw:l3vpn-ntw/vpn-services/vpn-service"Regards. Hello,Please let us know if 3PM - 4PM CET works for you?Since we are unable to reproduce this issue on our end we would like to g through the steps on the meeting.If thats on Friday yes works well for me.Please can we invite Liran Mendelovich (lmendelo) <[email protected]>, as he was the one that diagnosed the symptoms and knows how to show the error from the CNC side...Thank you - meeting invite has been sent.Hi Ulfat, After further investigation, we have concluded that this is a platform bug with NSO 5.4.4.1. The fix has been included in NSO 5.4.5.2. Please let us know if this bump is okay with you.Attached meeting minutes from 4/1/2022.Can you verify if the fix is also in 5.4.6, there is another work stream that may require is to upgrade to this release and we would like to verify if the same issue is fixed or not in that future release..? Thanks.Hello Ulfat, Yes this fix is present in 5.4.6 and subsequent releases. Also attached verification screenshot. Thank you.Hello, please confirm if this issue/questions is resolved so I may close the ticket. Thank you.I can confirm that upgrading to 5.4.5.2 fixed the issue. You can close the ticket. ThanksGreat - Thank you!Issue was being seen in NSO version 5.4.4.1.Customer has upgraded to NSO version 5.4.5.2 and issue is no longer seen.Resolving ticket. |
service-activation-failure: RPC error towards onc-real-new: operation_failed: Error in callback: NCS 5.5.2.3 M 3.2Deployed RON ML service. Service creation failed with no error message. It generates alarmservice-activation-failure: RPC error towards onc-real-new: operation_failed: Error in callbackonc-real-new sync-from is successful.Service name : RON_ML_4NSO : 10.195.165.226 cnctest/Ovatest123@ | Hi Ramakrishnan,We are looking into your issue. Please standby as it might take some time to debug your system.Thank you,AbeHi Ramakrishnan,Please provide additional information such as: 1. Device version / Image used for testing (XR and ONC devices)2. Payloads used for failed service deploymentInitially looking at your service-plan shown below, I can see that your RON_ML_4 service failed with a status code of RON-303, which indicates Config push failed possibly from invalid config.You can ping me when you are available and we can hop into a call to debug your system or you can check your payload and deploy service from a clean slate.status-code 303 { reason ""; category device; severity ERROR; recommended-actions "";cnctest@ncs% run show ron ron-ml-plan RON_ML_4 plan component | tab BACK STATUS POST ACTION TYPE NAME TRACK GOAL CODE STATE STATUS WHEN ref STATUS ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- self self false - RON-303 init reached 2021-07-30T10:09:38 - create-reached ready failed 2021-07-30T10:10:17 - - optical-controller Optical-Controller false - <font color="#de350b"> init reached 2021-07-30T10:09:45 - - cisco-ron-cfp-nano-plan-services:config-apply reached 2021-07-30T10:09:45 - - ready failed 2021-07-30T10:10:17 - - cisco-ron-cfp-nano-plan-services:router P-BOTTOMRIGHT-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 - - -CheckedRamakrishnan's configs getting pushed and tried it on my testbed and it gave an error:ALARM service-activation-failure: RPC error towards spitfire-r0: operation_failed: for ns2:interface-configurations1:netmask: 'ipv4-ma' detected the 'warning' condition 'Invalid host address or mask'Will schedule a webex meeting with him and debug his testbed.XR - x64-7.3.15.iso - Spitfire 8000 ONC - Daigo devices - 12.1.0. Wondering Why the RON ML is not displaying error message during provisioning. Ramakrishnan is using version device which is not supported in RON 1.0 M1 (CNC M3-2). Instructed reporter to upgrade devices or use existing ones with mentioned version in RON service deployments going forward. Also shared the RON pre-requisite pages for future referenceHi Ramakrishnan,RON 1.0 on M3-2 supports 7.3.2 XR device version (IOSXR image 7.3.2.25I) as indicated here on our release page: I recommend upgrading XR devices used with RON-ML service to the version above, and also verify if all items on this RON prerequisite list have been met: In the mean time I move to close this ticket - If issue persists after following the above recommendations, please open a new RON support ticket.Thank you, AbeFollowed up with Ramakrishnan if theres anymore questions regarding this ticket. He said to go ahead and close ticket as he no longer have any other questionsFollowed up with Ramakrishnan if theres anymore questions regarding this ticket. Reporter agreed to go ahead and close ticket. |
CFS HA : Please confirm that In NSO LSA CFS HA, if the Master goes unreachable, is it also expected that VIP cannot be reachable? | Hi Denish,VIP is used for both master and slave node. It should be reachable of one of them is reachable. It could have a little downtime when the ip is switch over the other nodeThanks,LinhHi Linh,It is actually not. For Example:When the CFS Master is powered of the VIP is also unreachable and does not able to reach it any longer.I can share the setup for you to take a look.Thanks,DineshHi Linh,As per the sync-up, this ticket can be closed as there's a expected time delay for the VIP to be reachable back post CFS Master .Thanks,Dinesh |
Need TSDN FP to support XR CLI NED - 7.52 with NSO 6.1.3: Currrent TSDN FP Release supports XR CLI NED - 7.49 . With enhancements in NED -XR CLI for device configs, need TSDN FP to migrate to 7.52 version XR CLI NED | Thanks Sujay. NED link - XR CLI NED : 7.52- Support for XR-CLI NED 7.52 has been added to TSDN. It will be available in the next build drop.Also, provided internal build with 7.52 support to Sujay over mail. |
Slice Kicker service for Routing Policy, ODN ...etc: Steps:1. Create slo-sle-template (NSST) System creates Routing Policy and Routing Policy Tags automatically.2. Create a slice use the above NSST System creates VPN service automatically3. Edit the internal created Routing Policy or Routing Policy Tag. I expect the kicker service will roll back to the original value but it does not.Same behavior for ODN template for the case that NSST is set as forwarding plane policy = as-blueprint. And a slice is created use this NSST. User should not be allow to edit the internal created services, Routing Policies... etc. With current design, we do not restrict users to edit internal created entries. The expectation is the kicker service will take care of this and revert back to the original data.Can you confirm if these are issues for Slice kicker service? | Thank you for your ticket. Developer working on reproducing issue.After reproducing, confirmed that service is working as designed. See below for Developer notes:Question/Answer 1:Regarding route-policy:Once the route-policy is created (By whichever service L2, L3, NSS-L2, NSS-L3) the config being pushed to the device depends solely on the l2vpn-routing-policy If a change is made under l2vpn-routing-policy/defined-sets or l2vpn-routing-policy/policy-definitions, the kickers monitoring the l2vpn-routing-policy will ensure that this new config is pushed to the device.Therefore, route-policy device config is not controlled by the service "using" the policy. It is controlled by the l2vpn-routing-policy.Question/Answer 2: Regarding ODN:Similarly, I believe is the same concept and case with ODN. The ODN template stands alone. It is being used by the NSS and pushed to the device through the NSS service. But making a change to ODN is a standalone change and will have the related effect on config.Question/Answer 3: Regarding User should not be allow to edit the internal created services, Routing Policies... etc.Yes, that is our recommendation. Because user changing internal data will result in discrepancy, exactly as in above 2 cases.Question/Answer 4: With current design, we do not restrict users to edit internal created entries.Yes, NSS is designed to use the other services (ODN, route-policy, PM etc) but it is not possible for us to hide/restrict the user from making changes to these other standalone services.If User tries to redeploy an NSS service (after making internal edits) there will be various errors seen (case by case basis). Please see below for a sample run.admin@ncs% show devices device PIOSXR-* config route-policydevice PIOSXR-0 { config { route-policy L2-ATTACH { value " apply NSS-L2-P2P-evi-1-internalrn apply PASS_ALLrn"; } route-policy NSS-L2-P2P-evi-1-internal { value " if evpn-route-type is 1 and rd in (ios-regex '.*:(1)$') thenrn set extcommunity color COLOR_40rn endifrn passrn"; } }}device PIOSXR-1 { config { route-policy L2-ATTACH { value " apply NSS-L2-P2P-evi-1-internalrn apply PASS_ALLrn"; } route-policy NSS-L2-P2P-evi-1-internal { value " if evpn-route-type is 1 and rd in (ios-regex '.*:(1)$') thenrn set extcommunity color COLOR_40rn endifrn passrn"; } }}device PIOSXR-2 { config { route-policy L2-ATTACH { value " apply PASS_ALLrn"; } }}admin@ncs% show | compare l2vpn-routing-policy { defined-sets { tag-sets { tag-set NSS-1-internal {- tag-value [ 1 ];+ tag-value [ 11 ]; } tag-set NSS-2-internal {- tag-value [ 2 ];+ tag-value [ 12 ]; } tag-set NSS-30-internal {- tag-value [ 30 ];+ tag-value [ 31 ]; } tag-set NSS-40-internal {- tag-value [ 40 ];+ tag-value [ 41 ]; } tag-set NSS-50-internal {- tag-value [ 50 ];+ tag-value [ 51 ]; } } } }admin@ncs% show devices device PIOSXR-* config route-policydevice PIOSXR-0 { config { route-policy L2-ATTACH { value " apply NSS-L2-P2P-evi-1-internalrn apply PASS_ALLrn"; } route-policy NSS-L2-P2P-evi-1-internal { value " if evpn-route-type is 1 and rd in (ios-regex '.*:(1)$') thenrn set extcommunity color COLOR_41rn endifrn passrn"; } }}device PIOSXR-1 { config { route-policy L2-ATTACH { value " apply NSS-L2-P2P-evi-1-internalrn apply PASS_ALLrn"; } route-policy NSS-L2-P2P-evi-1-internal { value " if evpn-route-type is 1 and rd in (ios-regex '.*:(1)$') thenrn set extcommunity color COLOR_41rn endifrn passrn"; } }}device PIOSXR-2 { config { route-policy L2-ATTACH { value " apply PASS_ALLrn"; } }}admin@ncs% request network-slice-services slice-service L2-P2P re-deployError: too many 'l2vpn-routing-policy defined-sets tag-sets tag-set NSS-40-internal tag-value', 2 configured, at most 1 must be configuredCorrect me if I am wrong for the summary:The kicker service will only take care of VPN service change, but not for other items (ODN, routing policiesetc). For example, a slice is created. 1. user edit internal vpn service: it will roll back to the original config.2. user edit ODN: slice config and the internal ODN config are different now. Since the ODN config is changed on device, but slice config. still remain the old data.3. user edit Routing policies: same behavior as item 2.Hi Crystal, Yes this correct.Also confirmed with our QA and it is correct.Regards,Janaki DuggiralaCustomer confirmed ticket can be closed. |
Redeploy dry-run not showing right config : Hi,I am seeing incorrect config while performing redeploy dry-run.Setup details: LSA IPv6Steps:1.Add all the nodes in NSO LSA cluster(CFS and RFS) and add devices using CW CDG2. Wait till the devices are in sync3. Deploy L2VPN4. Make one or more devices OOS or not reachable inside a provisioned service by shutting down a interface5. Try to edit the service. Provision will fail due to device out of sync6. Perform sync-from the device to make it in-sync9. From Action dropdown, click "Re-Deploy Dry Run "Output from response is not clear.Response from redeploy dry-run{ "ietf-l3vpn-ntw:output": { "cli": { "lsa-node": [ { "name": "rfs-63", "data": " devices { device xrv9k-PE6 { config { route-policy PASS_ALL {- value " pass";+ value pass; } } } }" } ] } }}Thanks,Kanchan | setup:CFS: (admin/Ovatest123@)RFS(rfs-62): (admin/Ovatest123@)RFS(rfs-63): (admin/Ovatest123@)RFS(rfs-67): (admin/Ovatest123@)Hello, this ticket is a duplicate as below:An internal ticket has been created for this issue as well:Thank you.Closing this ticket as all further tracking will be under CDETSIssue will be fixed under CDETS |
check-sync, sync-from, sync-to is failing on L3VPN service when device is OOS: Hi All,Steps I followed:1. Deployed a L3 VPN service on device-4 and device-6. Service got deployed successfully2. manually made changes to device-6 to make it out-of-sync3. Verified that device shows out-of-sync4. Edited the L3 VPN service, it failed as expected with error Device-6 out-of-sync5. from the error shown on CNC UI, tried to do a sync-from for the device-6, it didn't go throughBehavior observed: Changes got pulled from device-6(validated taht RFS node is in-sync with device-6) , but still L3VPN service is showing device out-of-sync message.expected: L3 VPN should show in-sync trueCW: admin/Ovatest123@CFS:admin/Ovatest123@RFS-62:admin/Ovatest123@RFS-63:admin/Ovatest123@Thanks,Kanchan | Hi Kanchan,When you bring the device back in-sync, did you do a service re-deploy for your L3 service?Thanks,Isaac KimHi Isaac,I did perform a sync-from or sync-to operation, commands performed are attached.Question here is: once my device is in-sync state, is it mandatory to perform re-deploy? if yes, then what sync-from or sync-to does?Also, when I perform re-deploy dry-run, I get following outputadmin@ncs# l3vpn-ntw vpn-services vpn-service L3VPN_NM-IGP-IPV4 re-deploy dry-runcli { lsa-node { name rfs-63 data devices { device xrv9k-PE6 { config { route-policy PASS_ALL { - value " passr "; + value pass; } } } } }}But I didn't change anything about route-policy, I changed the loopback address. expected?Hi Kanchan,Seems like UI bug, you can see from the text box: CLI command is : l3vpn-ntw vpn-servicesvpn-service L3VPN-NM-IGP-IPV4 error-recovery sync-direction sync-fromThis is error recovery action, not a device sync action.After doing sync-from on device, I would re-deploy the service to bring the "failed" service plan back into "success" state.Thanks,Isaac KimThanks Isaac.So on UI, it should not say "pushing to the device" as it it error-recovery action, right?also, is there a doc that explains what error recovery action is?Hi Isaac, I performed re-deploy and service came back to success state. Before re-deploying I checked re-deploy dry-run to verify what will be re-deployed, screenshot attached. But when I was editing the service, I changed loopback address on one device but CLI shows different thing.Hi Kanchan,I apologize for the very delayed response.For more details on error recovery you can look here : For the redeploy issue, this seems unrelated to the current issue described on the ticket. Please feel free to open a new JSD ticket for this!Thanks,Isaac KimPlease open new JSD if you encounter this again. Thank you! |
Is "Reactive Re Deploy" a supported action for L3 NM service ?: Can you please confirm whether "Reactive Re-deploy" is a supported action for L3 NM service with new model changes that were introduces as part of sub-service design ? | Hi Dedeepya,We do not have reactive redeploy at L3vpn service level. NSO supports reactive re-deploy at the vpn-node levelThanks Sahithi for confirming. In one of the previous grooming discussion, we captured the notes that saying "Reactive Re Deploy" is an available option at L3 NM service level. We will update with this confirmation.Hi , Update on this. We do support the functionality of reactive re-deploy.Just the re-deploy action, would execute the reactive re-deploy on the sub servicesietf-l3vpn-ntw:l3vpn-ntw/vpn-services/vpn-service=0-65008740 -> re-deployWhile the re-deploy with sync, would do a re-deploy on the sub servicesietf-l3vpn-ntw:l3vpn-ntw/vpn-services/vpn-service=0-65008740 -> re-deploy syncTo confirm the naming |
Addition of the "cnc-custom" metadata in L3VPN: We need to identify the L3VPN root service and the sub-services. Please add the following metadata to for both root and sub-service configs. path: "/l3nm:l3vpn-ntw/vpn-services/vpn-service" tailf:meta-data "cnc-custom" { tailf:meta-value '{ "field": "vpn-service", "rootService": "true" }'; }path: "/l3nm:l3vpn-ntw/vpn-services/vpn-service/vpn-nodes/vpn-node" tailf:meta-data "cnc-custom" { tailf:meta-value '{ "field": "vpn-node", "subService": "true" }'; } | |
[L3-NM] Missing VPN-node Subservice metadata annotation: TSDN 7.0.0 drop 1 has missing meta-data "cnc-custom" annotation for sub-service. Based on this annotation, CNC Provisioning (NSO) UI shows the sub-service element with additional functionality at each node level.It containing only rbac annotation. "meta_data": { "cnc-device-rbac": "config; keys=vpn-node-id"},As per 7.0 grooming, CNC UI team requested to extend the metadata with cnc-custom for vpn-node list type.expected:"meta_data": { "cnc-device-rbac": "config; keys=vpn-node-id", "cnc-custom": "{subService": true}" }L3-NM getSchema API response Attached. | I believe this ticket is regarding: . Please take a look.Hi Dedeepya,The mentioned changes was merged after the Drop 1. This will be available in the next Drop.There was an engineering build shared with Demeke earlier. Meanwhile you can use the engineering build if it needs to tested.I will update this ticket once the next Drop is available.Thanks And Regards,Nishad Subair.Nishad,We are expecting these changes in Drop1 to validate CNC UI workflows. Other meta-data changes reg L2 NM TE mapping are available in Drop1.Can you share Drop 2 data please.– Dedeepya Hi Dedeepya,We were unable to merge in drop1 as we got a go-ahead from UI team on engineering build after the test hand off of drop1.Our current drop 2 release is scheduled on Jan 31st. We should be able to provide a separate build for UI adhoc if required to verify the CNC UI workflows.ThanksSahithi |
SSH connectivity issue after migration: Migrated NSO from TSDN 5.0 FCS version to TSDN 6.0 Drop 10.SSH connectivity to simulated devices was working fine. After the migration, we get following error message.Failed to connect to device Node_1_100: connection refused: NEDCOM CONNECT: authenticate: Exhausted available authentication methods, server allowed: [ password ] in new stateNSO : 192.168.103.236admin/Ovatest123@Device : Node_1_100SSH keys fetched successfully. | Diff between TSDN 5.0 ncs.conf and TSDN 6.0 ncs.conf. < <DES3CBC>< <key1>0123456789abcdef</key1>< <key2>0123456789abcdef</key2>< <key3>0123456789abcdef</key3>< <initVector>0123456789abcdef</initVector>< </DES3CBC><< <AESCFB128>< <key>0123456789abcdef0123456789abcdef</key>< <initVector>0123456789abcdef0123456789abcdef</initVector>< </AESCFB128><< <AES256CFB128>< <key>0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef</key>< </AES256CFB128>—> <external-keys>> <command>${NCS_DIR}/bin/ncs_crypto_keys</command>> <command-argument>${NCS_CONFIG_DIR}/ncs.crypto_keys</command-argument>> </external-keys>Hello, Yes, Looking at this output, it seems the ssh key has been changed during migration in the ncs.conf file.To resolve this issue we recommend, 1. revert ssh key method in ncs.conf (or update to the older ssh key)2. restart ncsPlease let us know if this works.After speaking to Sreedhar, observed there is no ncs.conf back up file. Using diff set provided above, modified the ncs.conf file as below <encrypted-strings> <!-- <DES3CBC> <key1>0123456789abcdef</key1> <key2>0123456789abcdef</key2> <key3>0123456789abcdef</key3> <initVector>0123456789abcdef</initVector> </DES3CBC> <AESCFB128> <key>0123456789abcdef0123456789abcdef</key> <initVector>0123456789abcdef0123456789abcdef</initVector> </AESCFB128> <AES256CFB128> <key>0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef</key> </AES256CFB128> --> <external-keys> <command>${NCS_DIR}/bin/ncs_crypto_keys</command> <command-argument>${NCS_CONFIG_DIR}/ncs.crypto_keys</command-argument> </external-keys> </encrypted-strings>After restarting NSO, seeing belowadmin@ncs% request devices device xrv9-6 sync-fromresult truePlease verify if setup is working.Hi Janaki,Thanks. Able to sync the devices from NSO (just sync, no need to ssh fetch-keys)Customer verified that Issue is resolved and ticket can be closed. |
Does L2 VPN service support loopback interface as part of vpn-network-acess?: For L3VPN service, user can configure loopback interface as part of vpn-network-access configuration. Use follow the same from CNC UI for L2VPN, it showed error "loopback" is an invalid value. Can you confirm if loopback interface is supported for L2VPN?Here is the sample config for L3VPN with loopback interface:<attachment-circuits> <attachment-circuit> <ac-id>1</ac-id> <ac-tp-id>Loopback70</ac-tp-id> <ac-ip-address>70.70.70.2</ac-ip-address> <ac-ip-prefix-length>24</ac-ip-prefix-length> <sdp-peering> <protocol> <protocol-type>peering-protocol-bgp</protocol-type> <bgp-attributes xmlns="http://cisco.com/ns/nso/fp/examples/cisco-network-slice-service"> <neighbor>70.70.70.3</neighbor> <remote-as>70</remote-as> </bgp-attributes> </protocol> </sdp-peering> </attachment-circuit> </attachment-circuits> | Hi Crystal,Loopback is not supported by L2. You can see the supported values for interface here:pattern "(Bundle-Ether|FiftyGigE|FortyGigE|FourHundredGigE|HundredGigE|TenGigE|TwentyFiveGigE|TwoHundredGigE|GigabitEthernet|Ethernet)<ins>(/</ins>)*";Let me know if you have any other questions.Thanks,Isaac KimThank you for your confirmation. We wanted to validate that only.Does L3VPN support loopback interface ? Because i can see it is supported there.Hi,Yes Loopback is supported on L3. You can see the supported values for interface here:type string{ pattern "(Bundle-Ether|BVI|FiftyGigE|FortyGigE|FourHundredGigE|HundredGigE|Loopback|TenGigE|TwentyFiveGigE|TwoHundredGigE|GigabitEthernet|Ethernet)[0-9]+(/[0-9]+)*"; }Let me know if you have any other questions.Thanks,Isaac KimRequired Info given to the submitter |
No verification for routing-protocol->bgp->neighbor: If routing-protocol->bgp is specified, neighbor has to become a mandatory field | Hi Yevgeny,Since this feature is from 3.0 release, please open CDET enhancement bug, then dev team will take care of it.Thanks,LinhOK, will doClose it since he is going to file Sev6 CDETs |
Policies updated on the crosswork setup, but it's not able to find the CFS with forward true: Policies are updated on the crosswork setup, but it's not able to find the CFS with forward true. Screenshot attached. | Setup details below10.194.63.198 CFS -10.194.63.169RFS1- 10.194.63.170 ; 242 Please take a look on the issue.Hi Ragesh, after investigating your setup, I see the NSO is correctly configured for LSA. All the settings are in place and ready.Since there are a few alarms on your CW CFS page as in screenshot attached.I would suggest please checking yoursetup with Crosswork DLM.Please let me know once issue is resolved. Thank you. Hi Janaki, Thanks for checking the issue, Yes it's setting issue ; it resolved. Please close the ticket.Thank you Ragesh.This was a crosswork DLM issue and not an NSO issue. Customer has received assistance from DLM team. |
invalid data mode error thrown when navigating from devices to profile/policies: Created SR policy and Service profiles mapped with delay profile. Creation and assignment went fine. Tried viewing policy or service profile mapped from device configuration getting below error invalid data mode "cisco-sr-te-cfp-internal:sr-te", invalid expand mode "cisco-sr-te-cfp-sr-policies-internal:policies", invalid output mode "policy{SR-Policy-PM ASR9901-1}", go to application root / or try the legacy link /cisco-sr-te-cfp-internal:sr-te/cisco-sr-te-cfp-sr-policies-internal:policies/policy{SR-Policy-PM ASR9901-1}Same works fine when navigated from service manager | Hello, please provide NSO setup info, for further troubleshooting.Please find the NSO setup detailsNSO - 10.22.179.240 - xrd1/Cwork123!Thank you for the information. An Internal ticket has been raised with the NSO platform team to address this issue.RT#50709 and CDETS CSCwh52008We will inform you of any related updates.For now, added ticket to release notes with a recommendation to manually perform sync from/to with device.Further investigation awaited. |
Unable to parse error message: Were using NSO restconf APIs to create/modify services. Here is one of the error messages "error-message": "Python cb_pre_modification error. Delete on inter-layer-link ('P-BOTTOMRIGHT', '0/0/0/1') is not allowed at this moment, it in use by ron-ml BROWN_OLS_TPRHT_BTMRGT_400_TR service.STATUS_CODE: RON-421REASON: The inter-layer-link entry cannot be edited or deleted at the moment.CATEGORY: userSEVERITY: ERRORContext [name = inter-layer-link db edit state = {'Opertion': 'Delete', 'Keypath': '/cisco-ron-cfp:ron/inter-layer-link{P-BOTTOMRIGHT 0/0/0/1}', 'used-by': 'BROWN_OLS_TPRHT_BTMRGT_400_TR'}]"In this case ideally we would like to tell the user that Delete on inter-layer-link ('P-BOTTOMRIGHT', '0/0/0/1') is not allowed at this moment, it in use by ron-ml BROWN_OLS_TPRHT_BTMRGT_400_TR service.Which is part of the error-message, but can also be constructed using the REASON and used-by fileds.We will go ahead and attempt to parse the message per case basis but wanted to understand if there is a logic that can be followed generically. Or a list of status codes on which a certain method can be followed. | Had a call with Mukul and had a discussion regarding RON status codes. Questions and issues was resolved.Worked with Mukul to answer queries and provide RON status code bootstrap file |
nacm command are not available in 5.7.2.1 + TSDN 4.0.0 M3: Hi,I installed nso 5.7.2.1 on 10.56.116.132 (nso/Public1234!) server.I followed all the steps from standalone system installation until "NACM" section.Currently nso server does not accept any nacm commands, e.g. admin@ncs% set nacm cmd-exec-default permit groups group ncsadmin---------------^syntax error: element does not existCan you please advise ?Regards,Leonid | Hi Leonid,I saw you don't configure a proper right for 'nso' user. It need to be a member of ncsadmin group.I just add 'nso' user to ncsadmin group and set nacm is availaiblenso@lkronik-esxi-01-nso:~$ groupsnso adm cdrom sudo dip plugdev lxd ncsadminnso@ncs% set nacm cmd-exec-default permit ?Description: Access controlPossible completions: cmd-read-default - enable-external-groups - enable-nacm - enforce-nacm-on-services - By design NACM rules are ignored for changes done by services - FASTMAP, Reactive FASTMAP, or Nano services. exec-default - groups - log-if-default-permit - read-default - rule-list - write-default -Please check your setup and let me know it works as expected and I could close the ticket.Thanks,LinhI am going to close this ticket if I don't receive any new update in next few days.Thanks,Linh |
Optical fetch error: Receiving "Optical fetch error" while provisioning RON ML service. Verified Python, Paramiko, XMLlint , Java in root as well as non root user.Verify netconf subscription and NED value is 7.32Performed ssh-fetch-keys, sync-from, check-sync for optical controller. Please help troubleshoot | RPC error towards onc-real-new: operation_failed: Exception in callback: Circuit Provisioning failed. PCE Find Channel Failed - Optical validation failed: ZONE_RED worse than ZONE_GREEN Hi Ajitha, I pinged you at webex today to know if the issue still exists for you or not. Kindly let me know if you need any help in troubleshooting.It would be good if you can update the ticket progress/status.ThanksHi Ajitha,As discussed on webex, closing the issue.From Ajitha:I was able to create BL3toBR3 after sometime the service moved back to stuck in provisioning state I mean got into defect CSCvz11506. Please close the Jira ticket. I will reach you or raise new if i m unable to create the service Im holding the setup to troubleshoot |
From CNC, device can be moved between different RFS nodes which creates duplicate device entry in NSO: Hi All,From CNC server, I tried to migrate one of my device from one RFS to another, that created a duplicate device entry on the NSO RFS nodes.Steps I followed:Enabled LSA on CWAdded Providers, devices to CWCreated L2VPN on xrv9k-5 and xrv9k-6Edited device xrv9k-5, changed the admin state to Down and savedEdited device xrv9k-5, changed the RFS node from RFS-63 to RFS-62 and savedEdited device xrv9k-5, changed the admin state to Up and saved</ul>The above steps create one entry of device xrv9k-5 in RFS-62 as well.Set up details:CW: admin/Ovatest123@NSO CFS: admin/Ovatest123@NSO RFS-62 : admin/Ovatest123@NSO RFS-63 : admin/Ovatest123@Thanks,Kanchan | Hello Kanchan,On looking through NSO, I seexrv9k-5 present only onRFS-62.The dispatch map on CFS also reflects the devices correctly.To Note, Wikimentions ""the following are a few of the constraints:Device(s) cannot be shared across RFS nodes."""Please let me know if this helps.Hello Janaki,To proceed with my testing I deleted the device manually and re-installed the nodes. But I am able to reproduce the issue. Let me know when you are free for a call, I can show you the issue.Reached out to Kanchan, requesting for a time to setup the meeting to investigate further.Hi Janaki,Thanks for looking into my setup. I can see the alarm is getting generated on CFS (can be verified from UI/CLI).You can go ahead and close this ticket. I will work with CW infra team to capture the error.CDET : Thank you,Kanchan Thank you for the confirmation Kanchan! Closing Ticket.Per Reporter, Duplicate devices being created when moving device from RFS 62 to RFS 63 will be taken up by UI team onCDET : [https://cdetsng.cisco.com/webui/#view=CSCwb41976 <div class='table-wrap'><table class='confluenceTable'><tbody><tr><td class='confluenceTd'>https://cdetsng.cisco.com/webui/#view=CSCwb41976]</td></tr></tbody></table></div> |
versions are not matching in tm-tc and cfp for ncs-5.7-cisco-iosxr-7.38 and custom-template-utils: in TMTC and FP packages, we are seeing different version for the highlighted packages below :root@nso1:/home/admin/new_tmtc/TM-TC-4.3.0-98/packages# ls -lrttotal 98452<del>rw-rw-r</del>- 1 admin admin 218306 Mar 11 05:29 ncs-5.7-custom-template-utils-2.0.8--a14f1b1-2021-12-21.tar.gz<del>rw-rw-r</del>- 1 admin admin 58084739 Mar 11 05:29 ncs-5.7-cisco-iosxr_netconf-7.3.2.tar.gz<del>rw-rw-r</del>- 1 admin admin 42402915 Mar 11 05:29 ncs-5.7-cisco-iosxr-7.38.1.tar.gz<del>rw-r</del><del>r</del>- 1 admin admin 3383 Mar 11 05:29 ncs-5.7.2.1-tm-tc-multi-vendors-4.3.0-98.tar.gz<del>rw-r</del><del>r</del>- 1 admin admin 91905 Mar 11 05:29 ncs-5.7.2.1-cisco-tm-tc-fp-4.3.0-98.tar.gz<del>rw-rw-r</del>- 1 admin admin 772 Mar 11 05:30 manifest.jsonroot@nso1:/home/admin/new_tmtc/TM-TC-4.3.0-98/packages# cd /home/admin/tsdn-fp/root@nso1:/home/admin/tsdn-fp# cd nso-5.7.2.1-tsdn-4.0.0-M3/tsdn/core-fp-packages/root@nso1:/home/admin/tsdn-fp/nso-5.7.2.1-tsdn-4.0.0-M3/tsdn/core-fp-packages# ls -lrttotal 330232<del>rw-r</del><del>r</del>- 1 admin admin 23146 Mar 9 18:18 ncs-5.7-lsa-utils-1.0.0-7.tar.gz<del>rw-r</del><del>r</del>- 1 admin admin 216560 Mar 9 18:18 ncs-5.7-custom-template-utils-2.0.8--nso-5.7-test-9bd93f8-2022-01-06.tar.gz<del>rw-r</del><del>r</del>- 1 admin admin 18576 Mar 9 18:18 ncs-5.7-core-fp-plan-notif-generator-1.0.6.tar.gz<del>rw-r</del><del>r</del>- 1 admin admin 175372 Mar 9 18:18 ncs-5.7-core-fp-common-1.30.0.tar.gz<del>rw-r</del><del>r</del>- 1 admin admin 66917312 Mar 9 18:18 ncs-5.7-cisco-iosxr_netconf-7.5.1.tar.gz<del>rw-r</del><del>r</del>- 1 admin admin 58084739 Mar 9 18:18 ncs-5.7-cisco-iosxr_netconf-7.3.2.tar.gz<del>rw-r</del><del>r</del>- 1 admin admin 47854831 Mar 9 18:18 ncs-5.7-cisco-iosxr_netconf-7.315.tar.gz<del>rw-r</del><del>r</del>- 1 admin admin 60941295 Mar 9 18:18 ncs-5.7-cisco-iosxr-nc-7.4.2.22I.tar.gz<del>rw-r</del><del>r</del>- 1 admin admin 61128876 Mar 9 18:18 ncs-5.7-cisco-ios-6.77.9.tar.gz<del>rw-r</del><del>r</del>- 1 admin admin 13660 Mar 9 18:18 ncs-5.7.2.1-sr-te-multi-vendors-4.0.0.tar.gz<del>rw-r</del><del>r</del>- 1 admin admin 71987 Mar 9 18:18 ncs-5.7.2.1-cisco-tsdn-core-fp-common-4.0.0.tar.gz<del>rw-r</del><del>r</del>- 1 admin admin 89651 Mar 9 18:18 ncs-5.7.2.1-cisco-sr-te-cfp-internal-4.0.0.tar.gz<del>rw-r</del><del>r</del>- 1 admin admin 115663 Mar 9 18:18 ncs-5.7.2.1-cisco-sr-te-cfp-4.0.0.tar.gz<del>rw-r</del><del>r</del>- 1 admin admin 42478872 Mar 9 18:18 ncs-5.7.1-cisco-iosxr-7.38.6.tar.gzroot@nso1:/home/admin/tsdn-fp/nso-5.7.2.1-tsdn-4.0.0-M3/tsdn/core-fp-packages#Due to this mismatch, we are encountering below issue during CFP installation via script :sudo NCS_RELOAD_PACKAGES=force /etc/init.d/ncs restartStopping ncs: connection refused (stop)Starting ncs: Failed to load duplicate NCS package custom-template-utils: (/var/opt/ncs/packages/ncs-5.7-custom-template-utils-2.0.8--a14f1b1-2021-12-21.tar.gz)Daemon died status=21.Kindly fix the version issue.Thanks,Meenakshi | Hi Meenakshi,We have observed that common package versions are not updated in TM-TC FP from TSDN M3 Release bundle.Please reach out to TM-TC team. They should be able to assist you here.Thank you.Closing the ticket as the information has been provided |
dispatch-map-settings.xml file is missing on nso-5.7-tsdn-4.0.0-M2: dispatch-map-settings.xml file is missing on nso-5.7-tsdn-4.0.0-M2nso@nso-virtual-machine:~/nso-5.7-tsdn-4.0.0-M2/config$ ls -lrt dispatch-map-settings.xmlls: cannot access 'dispatch-map-settings.xml': No such file or directorynso@nso-virtual-machine:~/nso-5.7-tsdn-4.0.0-M2/config$Not able to load merge the dispatch-map-settings.xml file on non-lsa setup | Hi Ragesh,dispatch-map-settings.xml is no longer needed, the following installation instruction has been updated.Please try and let us know.Closing ticket due to no response from submitter for over a week. Assuming updated docs resolved the issue. |
Delete l2vpn service from CNC, it's gone from NSO but not from CNC in LSA setup: Please refer to . To summarize the issue:1. Provision l2vpn service from CNC, it stuck in "In Progress" state.2. Janaki helped to investigate and found the redeploy (I didn't trigger redeploy manually) did not go through fully for some unknown reason. Janaki redeployed the service and it worked. 3. I tried to delete the l2vpn service from CNC UI. On CNC it showed the service is still there. When cross launch to view in NSO, NSO showed "path does not exist". Can you check if the correct status has been sent to CNC?Thanks. | Hi Crystal, Thank you for the ticket!Can you please let me know what is the user when contacting NCS from UI for the creation/deletion.Hi Janaki, the user is root. Thanks.Hi Crystal, thank you for info please also let me know of a good time to do a Webex session (maybe today) so we can walkthrough this and troubleshoot.Issue was happening because the user "root" was being used to create and delete services from the CNC UI. This user was not present in the nacm and thus the redeploys were not happening correctly. On the webex call, we guided Crystal to add the "root" user to nacm rules on NCS CLI using following command:admin@ncs% set nacm groups group ncsadmin user-name root admin@ncs% commitCrystal was able to create and delete services successfully after this change. Closing ticket.Issue was happening because the user "root" was being used to create and delete services from the CNC UI. This user was not present in the nacm and thus the redeploys were not happening correctly.On the webex call, we guided Crystal to add the "root" user to nacm rules on NCS CLI using following command:admin@ncs% set nacm groups group ncsadmin user-name rootadmin@ncs% commitCrystal was able to create and delete services successfully after this change.Closing ticket. |
Use cases for NSO Actions: Check-Sync, Sync-from, Reactive-Re-Deploy...: We try to find the use case where we can test the following NSO Actions initiated from CNC:Check-SyncSync-fromSync-toReactive-Re-DeployWe went through the Error Recovery Procedures wiki, but not able to come up with the use cases to test the actions above.Thanks in advance. | Hi Crystal,Please refer to nso user guides for details regarding the NSO actions and how and when that can be used. Please find the documents under NSO after install. For System install they are under /opt/ncs/<ncs-x.x>/doc.Regards,Nishad Subair.Hi Nishad,By reading the user guide, I still can not come up with a use case to apply Reactive-Re-Deploy action. It will be great if you can help on this.Here is the description for "Reactive-Re-Deploy":=====================================This is a tailored re-deploy intended to be used in the reactive FASTMAP scenario. It differs from the ordinary re-deploy in that this action does not take any commit parameters.This action will re-deploy the services as an shallow depth re-deploy. It will be performed with the same user as the original commit. Also, the commit parameters will be identical to the latest commit involving this service.By default this action is asynchronous and returns nothing. Use the sync leaf to get synchronous behaviour and block until the service re-deploy transaction is committed. The sync leaf also means that the action will possibly return a commit result, such as commit queue id if any, or an error if the transaction failed. |
Unable to delete a device in M4: Hi,I have added devices to NSO and provisioned Circuit Style ; Slicing services.To upgrade the NED , I have tried to delete the devices after deleting the services.But post which I am unable to delete one of the devices and could see below service keep showing up and NSO not allowing it to delete. core-fp-delete-shutdown-servicexrv9k-23 GigabitEthernet 0/0/0/1 | Hi Naveen,Please provide your NSO setup details and also let us know which device you are unable to delete.Thanks,NikhilHi Nikhil,I am unable to delete xrv9k-23 device.The NSO details are as follows,URL : cred : nso/Vtsisco@123!Kindly let me know.Thanks,NaveenHi Naveen,I have deleted the core-fp-delete-shutdown-service from your setup. Please delete the services that use this device and then try to delete the device.Thanks,NikhilHi Nikhil,I am able to delete the device now.ThanksNaveenDeleted the core-fp-delete-shutdown-service and the user was able to the device thereafter. |
route_policy seems to be mandatory for L3VPN ODN policy: Creation of L3VPN ODN policy with route_policy "route_in" fails as the policy is not existing already.Same payload worked fine in NSO 6.0 version and didn't require route-policy as mandatory policy to be pre-existing. | Please ignore this issue and close it. The payload was of type L2VPN and works as expected once pre-requisite route_policy was added. |
Getting error while creating Dynamic L3MVPN: Hi Team,I am trying to create L3MVPN and getting error.Attached is the screenshot.Can someone help with what I am missing here.Thanks,Kanchan | I was not using payload and was creating directly through CNC UI.I was able to see it again, attaching the payloads These issues are caused by RT-49480, RT-50000.Restarting the NSO is workaround until we get the RT fixes |
Whether NSO model available to load for some transport slicing attributes.: Hi,Is there any NSO model available to load possible values for below attributes,1. Connectivity Type (slice service)2. Peering Protocol (slice service)3. Forward plane Policy type ( slice template)We need the possible values to be loaded in CNC for these attributes.Thanks, | <ol>Connectivity Type (slice service) => Released with M2Peering Protocol (slice service) => Released with M2Forward plane Policy type ( slice template) => Will be released with M4</ol>I've given the following cut down yang tree which has the both "connectivity-type" and "sdp-peering"<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"><pre>module: ietf-network-slice-service +--rw network-slice-services +--rw slice-service* [service-id] | +--rw service-id string | +--rw connection-groups | | +--rw connection-group* [connection-group-id] | | +--rw connection-group-id string | | +--rw connectivity-type? identityref | +--rw sdps | | +--rw sdp* [sdp-id] | | +--rw sdp-id string | | +--rw sdp-peering | | | +--rw protocol* [protocol-type] | | | +--rw protocol-type identityref | | | +--rw cisco-nss:bgp-attributes | | | +--rw (as-type)? | | | +--:(as-no-from-device) | | | +--rw cisco-nss:as-no-from-device? empty | | +--rw attachment-circuits | | | +--rw attachment-circuit* [ac-id] | | | +--rw ac-id string | | | +--rw sdp-peering | | | +--rw protocol* [protocol-type] | | | +--rw protocol-type identityref | | | +--rw cisco-nss:bgp-attributes! | | | +--rw cisco-nss:neighbor* inet:ip-address | | | +--rw cisco-nss:remote-as inet:as-number | | | +--rw cisco-nss:update-source! | | | | +--rw cisco-nss:if-type enumeration | | | | +--rw cisco-nss:if-id string | | | | +--rw cisco-nss:sub-if-id? int32 | | | +--rw cisco-nss:mpls-deactivation? boolean | | | +--rw cisco-nss:multihop? uint8</pre></div></div>Let me know if the above helps.Thanks,RegiHi,It looks like possible values for1. connectivityType : Any To-Any , Hub And Spoke 2. Peering Protocol : BGPIs these values are hardcoded or it is loaded from some other nso model.This will help us to leverage the same model instead of hard coding it in CNC. We are asking it since there is a possibility new values will be added in future ; we will end up changing it everytime.Thanks,NaveenHi,These are derived from IETF Models: connectivity-type uses "vpn-common:vpn-topology" type, so it's coming from the vpn-common module:<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"><pre> leaf connectivity-type { type identityref { base vpn-common:vpn-topology; } default "vpn-common:any-to-any"; description "Connection group connectivity type."; }</pre></div></div>However, we do restrict the above types to what we currently support.SDP Peering is part of IETF as well as "peering-protocol-type" is defined in the IETF slicing module:<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"><pre> grouping sdp-peering { description "A grouping for the slice service SDP peering."; container sdp-peering { description "Describes SDP peering attributes."; list protocol { key "protocol-type"; description "List of the SDP peering protocol."; leaf protocol-type { type identityref { base peering-protocol-type; } description "Identifies an entry in the list of SDP peering protocol type."; }</pre></div></div>but the "bgp-attributes" container is a cisco addition as you can see from the previous yang tree as there's a namespace prefix.Thanks,Regi |
Policy Type, Allow Customizations and Service Type missing in model: Hi,While provisioning we need to pass values to 1. Policy Type (Use-As-Is, Use-As-blueprint), 2. Allow Customizations (true/false)3. Service Type (L2/L3).But its not available in M3 model | Hi Magesh,Items 1 and 2 are coming in TSDN 4.0 M4.For item 3 you can see it in the YANG tree you referenced:<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"><pre class="code-java"> +--rw slice-service* [service-id] | +--rw service-tags | | +--rw tag-type* [tag-type] | | +--rw tag-type identityref | | +--rw value* string</pre></div></div>It will be done via service-tag.<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"><pre class="code-java"><config xmlns=></span> <network-slice-services xmlns=> <slice-service> <service-id>L2-P2P</service-id> <service-tags> <tag-type> <tag-type>service-tag-service</tag-type> <value>L2</value> </tag-type></pre></div></div>Let me know if you have any other questions.Thanks,Isaac KimHi Isaac,We are expecting all 3 attributes in slice template. It looks like service-tag is in slice-service.+--rw slo-sle-templates<div class='table-wrap'><table class='confluenceTable'><tbody><tr><td class='confluenceTd'> +--rw slo-sle-template* </td></tr><tr><td class='confluenceTd'> </td><td class='confluenceTd'> +--rw id string</td></tr><tr><td class='confluenceTd'> </td><td class='confluenceTd'> +--rw template-description? string</td></tr><tr><td class='confluenceTd'> </td><td class='confluenceTd'> +--rw cisco-nss:qos-policy!</td></tr><tr><td class='confluenceTd'> </td><td class='confluenceTd'> </td><td class='confluenceTd'> +--rw cisco-nss:L2!</td></tr><tr><td class='confluenceTd'> </td><td class='confluenceTd'> </td><td class='confluenceTd'> </td><td class='confluenceTd'> +--rw cisco-nss:input-policy? -> /network-slice-services/slo-sle-templates/qos-catalog/L2/input-qos-policy/name</td></tr><tr><td class='confluenceTd'> </td><td class='confluenceTd'> </td><td class='confluenceTd'> </td><td class='confluenceTd'> +--rw cisco-nss:output-policy? -> /network-slice-services/slo-sle-templates/qos-catalog/L2/output-qos-policy/name</td></tr><tr><td class='confluenceTd'> </td><td class='confluenceTd'> </td><td class='confluenceTd'> +--rw cisco-nss:L3!</td></tr><tr><td class='confluenceTd'> </td><td class='confluenceTd'> </td><td class='confluenceTd'> +--rw cisco-nss:input-policy? -> /network-slice-services/slo-sle-templates/qos-catalog/L3/input-qos-policy/name</td></tr><tr><td class='confluenceTd'> </td><td class='confluenceTd'> </td><td class='confluenceTd'> +--rw cisco-nss:output-policy? -> /network-slice-services/slo-sle-templates/qos-catalog/L3/output-qos-policy/name</td></tr><tr><td class='confluenceTd'> </td><td class='confluenceTd'> +--rw cisco-nss:forwarding-plane-policy? -> /cisco-sr-te-cfp:sr-te/cisco-sr-te-cfp-sr-odn:odn/odn-template/name</td></tr><tr><td class='confluenceTd'> </td><td class='confluenceTd'> +--rw cisco-nss:service-assurance</td></tr><tr><td class='confluenceTd'> </td><td class='confluenceTd'> +--rw cisco-nss:heuristics!</td></tr><tr><td class='confluenceTd'> </td><td class='confluenceTd'> </td><td class='confluenceTd'> +--rw cisco-nss:monitoring-state? aa-monitoring-state</td></tr><tr><td class='confluenceTd'> </td><td class='confluenceTd'> </td><td class='confluenceTd'> +--rw cisco-nss:preservation? historical-data-options</td></tr><tr><td class='confluenceTd'> </td><td class='confluenceTd'> </td><td class='confluenceTd'> +--rw cisco-nss:L2!</td></tr><tr><td class='confluenceTd'> </td><td class='confluenceTd'> </td><td class='confluenceTd'> </td><td class='confluenceTd'> +--rw cisco-nss:point-to-point!</td></tr><tr><td class='confluenceTd'> </td><td class='confluenceTd'> </td><td class='confluenceTd'> </td><td class='confluenceTd'> </td><td class='confluenceTd'> +--rw cisco-nss:profile-name string</td></tr><tr><td class='confluenceTd'> </td><td class='confluenceTd'> </td><td class='confluenceTd'> </td><td class='confluenceTd'> </td><td class='confluenceTd'> +--rw cisco-nss:rule-name string</td></tr><tr><td class='confluenceTd'> </td><td class='confluenceTd'> </td><td class='confluenceTd'> </td><td class='confluenceTd'> +--rw cisco-nss:multipoint!</td></tr><tr><td class='confluenceTd'> </td><td class='confluenceTd'> </td><td class='confluenceTd'> </td><td class='confluenceTd'> +--rw cisco-nss:profile-name string</td></tr><tr><td class='confluenceTd'> </td><td class='confluenceTd'> </td><td class='confluenceTd'> </td><td class='confluenceTd'> +--rw cisco-nss:rule-name string</td></tr><tr><td class='confluenceTd'> </td><td class='confluenceTd'> </td><td class='confluenceTd'> +--rw cisco-nss:L3!</td></tr><tr><td class='confluenceTd'> </td><td class='confluenceTd'> </td><td class='confluenceTd'> +--rw cisco-nss:profile-name string</td></tr><tr><td class='confluenceTd'> </td><td class='confluenceTd'> </td><td class='confluenceTd'> +--rw cisco-nss:rule-name string</td></tr><tr><td class='confluenceTd'> </td><td class='confluenceTd'> +--rw cisco-nss:ethernet-service-oam!</td></tr><tr><td class='confluenceTd'> </td><td class='confluenceTd'> +--rw cisco-nss:md-name string</td></tr><tr><td class='confluenceTd'> </td><td class='confluenceTd'> +--rw cisco-nss:md-level uint8</td></tr><tr><td class='confluenceTd'> </td><td class='confluenceTd'> +--rw cisco-nss:y-1731</td></tr><tr><td class='confluenceTd'> </td><td class='confluenceTd'> +--rw cisco-nss:id-type? enumeration</td></tr><tr><td class='confluenceTd'> </td><td class='confluenceTd'> +--rw cisco-nss:message-period? string</td></tr><tr><td class='confluenceTd'> </td><td class='confluenceTd'> +--rw cisco-nss:profile-delay? -> /l2vpn-ntw:l2vpn-ntw/cisco-l2vpn-ntw:y-1731-profile/name</td></tr><tr><td class='confluenceTd'> </td><td class='confluenceTd'> +--rw cisco-nss:profile-loss? -> /l2vpn-ntw:l2vpn-ntw/cisco-l2vpn-ntw:y-1731-profile/name</td></tr><tr><td class='confluenceTd'> </td><td class='confluenceTd'> +--rw cisco-nss:profile-synthetic-loss? -> /l2vpn-ntw:l2vpn-ntw/cisco-l2vpn-ntw:y-1731-profile/name</td></tr><tr><td class='confluenceTd'> +--rw cisco-nss:qos-catalog</td></tr><tr><td class='confluenceTd'> +--rw cisco-nss:L2</td></tr><tr><td class='confluenceTd'> </td><td class='confluenceTd'> +--rw cisco-nss:output-qos-policy* </td></tr><tr><td class='confluenceTd'> </td><td class='confluenceTd'> </td><td class='confluenceTd'> +--rw cisco-nss:name? string</td></tr><tr><td class='confluenceTd'> </td><td class='confluenceTd'> </td><td class='confluenceTd'> +--rw cisco-nss:description? string</td></tr><tr><td class='confluenceTd'> </td><td class='confluenceTd'> +--rw cisco-nss:input-qos-policy* </td></tr><tr><td class='confluenceTd'> </td><td class='confluenceTd'> +--rw cisco-nss:name? string</td></tr><tr><td class='confluenceTd'> </td><td class='confluenceTd'> +--rw cisco-nss:description? string</td></tr><tr><td class='confluenceTd'> +--rw cisco-nss:L3</td></tr><tr><td class='confluenceTd'> +--rw cisco-nss:output-qos-policy* </td></tr><tr><td class='confluenceTd'> </td><td class='confluenceTd'> +--rw cisco-nss:name? string</td></tr><tr><td class='confluenceTd'> </td><td class='confluenceTd'> +--rw cisco-nss:description? string</td></tr><tr><td class='confluenceTd'> +--rw cisco-nss:input-qos-policy* </td></tr><tr><td class='confluenceTd'> +--rw cisco-nss:name? string</td></tr><tr><td class='confluenceTd'> +--rw cisco-nss:description? string</td></tr></tbody></table></div>Hi Naveen,Apologies there is a typo in my previous reply. Items 1 and 2 are coming in TSDN 5.0 M4.So items 1 and 2 are not supported until TSDN 5.0 M4 is released.Regi will help with follow up question.Thanks,Isaac KimHi Naveen,Having "service-type" in the `slo-sle-template` was never planned for the newer revision . The `slo-sle-template` for most part allows configuration for both L2 and L3 applicable configs and the `slice-service` will pull the applicable configs based on the defined `service-tag-service` and `connectivity-type`.Thanks,Regi |
L2vpn P2p service with RSVP TE tunnel -failed to configure NSO 6.1- TSDO 5.0.0 M5+ Engineering build: Hi NSO Team,with NSO LSA , having one CFS and two RFS.Tried configuring the L2vpn p2p service with RSVP TE tunnel.,it is not pushing the config with the below payload structure.<te-service-mapping xmlns="http://cisco.com/ns/nso/fp/examples/cisco-l2vpn-ntw"><te-mapping><te-tunnel-list><ietf-te-service>L2NM-P2P-RSVPTE-128-1006</ietf-te-service><fallback>disable</fallback></te-tunnel-list></te-mapping></te-service-mapping>it is not pushing proper config to the devices. It is not pushing the tunnel id. Error as below in Native config tab.ASR9006-SDN-128External error in the NED implementation for device ASR9006-SDN-128: Config in diff couldn't be parsed: Skipped 1 line in context '/l2vpn/pw-class/encapsulation/mpls' : (line 24) : ' preferred-path interface tunnel-te fallback disable'NOTE: this might indicate invalid usage of device model, set config on device and sync-from to verify config syntax/structureInstead, it is working witht the below payload.,<te-service-mapping xmlns="http://cisco.com/ns/nso/fp/examples/cisco-l2vpn-ntw"><te-mapping><!--te-tunnel-list><te-tunnel-id>1006</te-tunnel-id></te-tunnel-list--></te-mapping></te-service-mapping>Please ping me, i can provide you the NSO details. Payload attached.Thanks,Arun.M.G | NOte: this issue is not seen in NSO standalone server.issue only NSO LSA setupHi Arun, I saw the same on my LSA setup with NSO 6.1 M5+ Eng. Please file a bug.Thanks,LinhHi Linh,Thanks . Filed CDETS CSCwe07262 Thanks,Arun.M.GFixed in 5.0 M7 |
zombies could not be deleted with large service: Created L2VPN service in scale setup with 100 EP, 700 EP, 1000 EP. However, we could not delete them. They resulted in zombie. We could not delete zombie also. CNC supports only L2VPN only till 50 EP. Need help in clearing, since it is blocking CNC testing.Setup : 172.20.63.132cnctest/Ovatest123@Service names: L2NM-L2-EVPN_MP_ELAN_12 - 200L2NM-L2-EVPN_MP_ELAN_20 - 1000L2-EVPN_MP_ELAN_75 - 75L2-EVPN_MP_ELAN_14 L2-EVPN_MP_ELAN_65 - 65 | Hi Srini,As suggested please try re-deploying the zombies and let us know if the zombies are cleared.executed the "zombies service /flat-L2vpn re-deploy" still 4 services are shown under zombie service. /flat-L2vpn The path to where the service resided that has been deleted and become a zombie. /flat-L2vpn The path to where the service resided that has been deleted and become a zombie. /flat-L2vpn The path to where the service resided that has been deleted and become a zombie. /flat-L2vpn The path to where the service resided that has been deleted and become a zombie. |
IPv6 Route Target in L3VPN service is not pushed to device: version:NSO: 6.1TSDN: 5.0.0 M5+Create a L3 slice with advance settings from CNC UI with following: Connectivity Route Target = Auto SDP advanced settings for route targets PE-A: import: 0:111:111 Export: 0:112:112 Both: 0:555:555 PE-B: Both: 0:666:666an L3VPN service is created by system (NSS-SliceL3Dedicated520-internal). It contains IPv4 and IPv6 address family under "vpn-node" -> "active-vpn-instance-profiles" -> "vpn-instance-profile". The Route Target is added to device under IPv4 address family but not IPv6. Attach the following:1. Slice payload2. NSS-SliceL3Dedicated520-internal payload 3. Config pushed to device | Hi Crytals,Address-family ipv4/ipv6 brought in is based on neighbor ip defined. It does not work with the current template. Please file a bug on this and DE will fix it.Thanks,LinhThanks Linh for looking into it. Here is the CDETS opened to track:Thanks.-CrystalThis fix is in M6 build. I am going to close the ticketRegards,Linh |
Nso failed to restart after adding tsdn and dlm: Installed 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.gzRestarted NCS using below command sudo NCS_RELOAD_PACKAGES=force /etc/init.d/ncs restartgetting below error NCS package upgrade failed with reason 'User java class "com.tailf.pkg.upgrade.UpgradeService" exited with status 1'Daemon died status=13 | Hello, Can you please provide the setup details so we can investigate further?Please find my setup detail NSO VM - 10.22.179.244 - admin/cisco123Hello, we have fixed your VM.Here are our observations.1. We noticed that your ncsadmin group was not configured correctly. So we ran the command below: admin@xrd1:~$ sudo usermod -a -G ncsadmin admin2. Next we noticed you have very little space on your VM to get all the packages loaded correctly (see screenshot attached). We highly recommend to switch to >= 64GB.Please let us know if this helps.Regards, Janaki DuggiralaMy over all VM is 150 GB. May I know exact requirement for all the packages.Some of the packages show java uninitialized errorHello,We logged into your VM and posted our findings (see screenshot attached). There is very little space.For all packages to load and TSDN to work, the proper settings should look as below:cisco@nso:~$ free -h total used free shared buff/cache availableMem: 62Gi 342Mi 60Gi 1.0Mi 2.3Gi 61GiSwap: 8.0Gi 0B 8.0GiAlso attached screenshot of Setup Requirements.After changing the required DRAM and Storage. NSO is up. Thanks for the resolutionCustomer changed the required DRAM and Storage and confirmed NSO is up. Closing ticket. |
Bandwidth not available in Transport Slicing service: Hi,We need to provision bandwidth for the slice service from CNC. But it is not found in NSO model. Kindly let us know.Thanks,Naveen | Configuring bandwidth per slice will be part of the dedicated SR TE feature which is coming in M4; however, you can configure bandwidth per pre-configured `forwarding-plane-policy` ( ie SR ODN service ) |
Sample payload needed for L3 H&S and L3 Any2Any with Tree-SID Static and Dynamic provisioning: Hi Team,I am looking for payloads for L3VPN H;S and L3VPN AnyToAny with Tree-SID Static and Dynamic provisioning. Can anyone help with payloads.Thanks,Kanchan | Hi Kanchan,This is original payloads.Please read through it and understanding prerequiste requirements.And attached are variation of Hub-spoke and any-to-any Thanks Linh, you can close the ticket. |
MaapiException observed during onboarding credentials(Exception:- failed because: sharedCreate() called outside fastmap): DLM uses MAAPI interface to interact with NSO. As a part of M4+ release, we are recompiling DLM service pack with NSO 6.0(nso-6.0.linux.x86_64.installer.bin). The exception observed while onboarding credentials. Please note the same code works fine with nso-5.7.6. Exception:======<ERROR> 30-Nov-2022::23:56:14.835 DLMConnection Thread-28: - Failed to reply to command:onboardCredentialsjava.lang.reflect.UndeclaredThrowableException: null at com.sun.proxy.$Proxy29.add(Unknown Source) ~ at com.cisco.crossworks.handlers.OnboardCredentialsHandler.handle(OnboardCredentialsHandler.java:23) ~ at com.cisco.crossworks.handlers.OnboardCredentialsHandler.handle(OnboardCredentialsHandler.java:14) ~ at com.cisco.crossworks.DLMConnection.processCommand(DLMConnection.java:279) at com.cisco.crossworks.DLMConnection.processQueue(DLMConnection.java:224) at com.cisco.crossworks.DLMConnection$1.run(DLMConnection.java:70) at java.lang.Thread.run(Thread.java:829) Caused by: com.tailf.navu.NavuException: com.tailf.maapi.MaapiException: /ncs:devices/authgroups/group{simulators}: Operation on: /ncs:devices/authgroups/group{simulators} failed because: sharedCreate() called outside fastmap at com.tailf.navu.NavuContextBase.create(NavuContextBase.java:917) ~ at com.tailf.navu.NavuContext.create(NavuContext.java:1035) ~ at com.tailf.navu.NavuList.doCreate(NavuList.java:510) ~ at com.tailf.navu.NavuList.sharedCreate(NavuList.java:473) ~ at com.cisco.nso.dao.impl.handlers.AddMH.handle(AddMH.java:37) ~ at com.cisco.nso.dao.impl.DAOImpl.invoke(DAOImpl.java:136) ~ ... 7 moreCaused by: com.tailf.maapi.MaapiException: /ncs:devices/authgroups/group{simulators}: Operation on: /ncs:devices/authgroups/group{simulators} failed because: sharedCreate() called outside fastmap at com.tailf.maapi.MaapiException.mk(MaapiException.java:62) ~ at com.tailf.maapi.Maapi.sharedCreate(Maapi.java:4573) ~ at com.tailf.maapi.Maapi.sharedCreate(Maapi.java:4523) ~ at com.tailf.navu.NavuContextBase.create(NavuContextBase.java:914) ~ at com.tailf.navu.NavuContext.create(NavuContext.java:1035) ~ at com.tailf.navu.NavuList.doCreate(NavuList.java:510) ~ at com.tailf.navu.NavuList.sharedCreate(NavuList.java:473) ~ at com.cisco.nso.dao.impl.handlers.AddMH.handle(AddMH.java:37) ~ at com.cisco.nso.dao.impl.DAOImpl.invoke(DAOImpl.java:136) ~ ... 7 moreAttached the ncs-java-vm.log. Please let me know if you need any other information. | Hi Ravi,As informed you before, please verify the NSO documentation provided in the NSO installation folder. They provide API's as well.You should be able to debug using these resources.We did not face this error in TSDN CFP, so we would not know the cause. ThanksSahithiQuery is for the NSO platform team. |
NSO restart with package reload force failing when i use core-fp-common on ncs 5.7.6: core fp common - ncs-5.7.6.2-core-fp-common-1.31.0.tar.gz | NSO sever details 10.104.127.41 ( nso / Cwork123! )# systemctl status ncs ncs.service - LSB: NCS Loaded: loaded (/etc/rc.d/init.d/ncs; bad; vendor preset: disabled) Active: failed (Result: exit-code) since Wed 2022-11-16 09:50:39 EST; 12h ago Docs: man:systemd-sysv-generator(8) Process: 8488 ExecStop=/etc/rc.d/init.d/ncs stop (code=exited, status=0/SUCCESS) Process: 8543 ExecStart=/etc/rc.d/init.d/ncs start (code=exited, status=13)Nov 16 09:50:38 nso-vm ncs: - CDB load: processing file: /opt/ncs/ncs-5.7.6/var/ncs/cdb/tailf-ncs-alarms_init.xmlNov 16 09:50:38 nso-vm ncs: - CDB load: processing file: /var/opt/ncs/cdb/aaa_init.xmlNov 16 09:50:39 nso-vm ncs: - NCS package upgrade failed with reason 'User java class "com.cisco.corefpcommon.upgrade.GlobalVarUpgrade" exite... status 1'Nov 16 09:50:39 nso-vm ncs: - NCS package upgrade failed with reason 'User java class "com.cisco.corefpcommon.upgrade.GlobalVarUpgrade" exite... status 1'Nov 16 09:50:39 nso-vm ncs: Starting ncs: NCS package upgrade failed with reason 'User java class "com.cisco.corefpcommon.upgrade.GlobalVarUp... status 1'Nov 16 09:50:39 nso-vm ncs: Daemon died status=13Nov 16 09:50:39 nso-vm systemd: ncs.service: control process exited, code=exited status=13Nov 16 09:50:39 nso-vm systemd: Failed to start LSB: NCS.Nov 16 09:50:39 nso-vm systemd: Unit ncs.service entered failed state.Nov 16 09:50:39 nso-vm systemd: ncs.service failed.Warning: ncs.service changed on disk. Run 'systemctl daemon-reload' to reload units.Hint: Some lines were ellipsized, use -l to show in full.# Hi Raja,I am not able to log in to the NSO. Please suggest if the credentials mentioned are correct.Regards,Nishad Subairslight correction in IP. It's 10.104.127.17Hi Raja,Please update the java version.Please refer the following documentation :Regards,Nishad SubairThanks nishad for checking the setup. It's working fine after switching to java 11Hi Raja,Thank you for the update.Regards,Nishad Subair |
More than 2 nodes in p2p+pbb: hi, when I put signaling option to evpn-pbb, it is possible to configure more than 2 nodes, even if I do not put any value in the svc-topo (which means the topology is p2p).is that a correct configuration - or NSO should limit to only 2 nodes? attached the config | Hello,Configuring more than 2 nodes for evpn-pbb is valid, but svc-topo will default to E-LAN. It seems you're currently running into a bug which is the result of the error message. I have created an internal ticket to fix the issue with default svc-topo.I have also added the bridge-group to the payload attached above to get a successful run. <bridge-group xmlns="http://cisco.com/ns/nso/fp/examples/ietf-l2vpn-ntw-cisco-augmentations">BRIDGE</bridge-group>Thank you.ok so you say it will eventually turn to ELAN, and not ELINE (=p2p)? Yes, we support E-LAN, E-TREE, as well as CUSTOM. To use ELINE, you would have to configure evpn-vpws instead of evpn-pbb.Hello, please kindly confirm if we may close this ticket. Thank you!TSDN supports E-LAN, E-TREE, as well as CUSTOM. To use ELINE, you would have to configure evpn-vpws instead of evpn-pbb. |
load merge config/dispatch-map-settings.xml fail: load merge failed while running the command for "Configure Common Bootstrap data". I checked the folder, dispatch-map-settings.xml does not exist under config/console outputadmin@ncs% load merge config/dispatch-map-settings.xmlError: failed to open file: File/directory does not exist. File name: dispatch-map-settings.xmladmin@ncs% | Continue with the remaining steps, and it failed to sync dispatch map. But the error message is confusing since this is a non-LSA setup and should not have concept of "CFS node".admin@ncs% request core-fp-common:cfp-common-actions sync-dispatch-mapsuccess falsedetail Dispatch Map Sync action not allowed on CFS node.Please refer to the updated installation wiki for standalone. You'll want to use the action `request devices lsa dispatch-map sync` instead.Let me know if you run into anymore issues.Thanks,RegiHi Crystal,Thank you for bringing this up! I took a look and you are right.There seems to be some outdated information in our install wiki related to dispatch map. Since we transitioned to lsa-utils package, dispatch map config and action targets has changed. Let me fix the wikis now. I will let you know when the wikis are updated.Thanks,Isaac KimHi Crystal,It seems like the wiki was updated.Please let us know if you run into any more issues. We will review the wikis again to ensure this does not happen.Thanks,Isaac KimHi Isaac,What are the different steps we need to follow? I still see the same commands to use for the following:load merge config/commit-queue-settings.xmlrequest core-fp-common:cfp-common-actions sync-dispatch-mapMaybe it takes sometime to reflect the change? Clear browser cache does not seem to help.Thanks.-CrystalThere's a fair bit of changes and the changes are reflecting on my end. We did remove `request core-fp-common:cfp-common-actions sync-dispatch-map` and replaced it with ``request devices lsa dispatch-map sync` as well as removing some bootstrap XML files.Let us know if you still have issues, maybe we can send you a copy of the page.Thanks,RegiHi Reginald,I think the problem is the URL. The one shared in this ticket is:But the one we refer to is:When use the one in this ticket, we got page not found. see screenshot attachedIt will be great if you can send a copy of the page for now.Thanks.-CrystalHi Crystal,You're correct it seems the external wiki wasn't updated. I've gone ahead and updated the page: .Please try again.Thanks,RegiHi Reginald,Yes, I see the wiki is updated. Tried the following 2 commands. "dispatch-map sync" is successful. But "load merge config/commit-queue-settings.xml" still fail because there is no such file under config/ folder. Do we still need "commit-queue-settings.xml" for non-LSA setup? Console output:============admin@ncs% load merge config/commit-queue-settings.xmlError: failed to open file: File/directory does not exist. File name: commit-queue-settings.xmladmin@ncs% request devices lsa dispatch-map syncsuccess truedetail Dispatch Map Synced SuccessfullyYes, you would need it for standalone NSO. Another issue with the wiki. The file is located under 'xml' folder. I've updated it again: Sorry for the inconvenience,RegiHi Reginald,I got the same error. And could not find xml folder on my VM. console output:============admin@ncs% load merge xml/commit-queue-settings.xmlError: failed to open file: File/directory does not exist. File name: commit-queue-settings.xmlls output from tsdn folder:====================root@nso-193:~/tsdn40_m2/nso-5.7-tsdn-4.0.0-M2# lsCHANGES config core-fp-packages example-packages get_technical_support_data.shThanks.-CrystalHi Reginald,I also do not see xml folder under config. FYI...Console output:============root@nso-193:~/tsdn40_m2/nso-5.7-tsdn-4.0.0-M2# ls configcommit-queue-settings.xml IETF-TE-plan-notification-settings.xml L3VPN-multi-vendor-iosxr-netconf.xmlIETF-L2NM-AA-notification-settings.xml IETF-TE-status-codes.xml L3VPN-plan-notification-settings.xmlIETF-L2NM-internal-plan-kicker.xml L2VPN-AA-notification-settings.xml L3VPN-status-codes.xmlIETF-L2NM-plan-notification-settings.xml L2VPN-cfp-configuration-kicker.xml RSVP-TE-status-codes.xmlIETF-L2NM-status-codes.xml L2VPN-internal-plan-kicker.xml SR-cfp-configuration-kicker.xmlIETF-L3NM-AA-notification-settings.xml L2VPN-multi-vendor-iosxe-cli.xml SR-internal-plan-kicker.xmlIETF-L3NM-internal-plan-kicker.xml L2VPN-multi-vendor-iosxr-netconf.xml SR-multi-vendor-iosxe-cli.xmlIETF-L3NM-plan-notification-settings.xml L2VPN-plan-notification-settings.xml SR-multi-vendor-iosxr-netconf.xmlIETF-L3NM-status-codes.xml L2VPN-status-codes.xml SR-plan-notification-settings.xmlIETF-TE-cfp-configuration-kicker.xml L3VPN-AA-notification-settings.xml SR-status-codes.xmlIETF-TE-internal-plan-kicker.xml L3VPN-cfp-configuration-kicker.xml xe-ip-sla-resource-pool.xmlIETF-TE-multi-vendor-iosxe-cli.xml L3VPN-internal-plan-kicker.xml xr-sman-id-resource-pool.xmlIETF-TE-multi-vendor-iosxr-netconf.xml L3VPN-multi-vendor-iosxe-cli.xmlGotcha, but commit-queue-settings.xml does seem to be there under config from your outputHi Crystal,It seems like there was some confusion.All TSDN bootstrap payloads can be found under <TSDN ROOT>/config.Thanks,Isaac KimHi Reginald ; Isaac,I am able to see the commit-queue-settings.xml file under config/ folder. But when run the command to load merge, it failed again. Can we have a webex on Tuesday to look further? Thanks. -Crystalconsole output:============root@nso-193:~/tsdn40_m2/nso-5.7-tsdn-4.0.0-M2/config# lscommit-queue-settings.xml IETF-TE-internal-plan-kicker.xml L2VPN-plan-notification-settings.xml SR-cfp-configuration-kicker.xmlIETF-L2NM-AA-notification-settings.xml IETF-TE-multi-vendor-iosxe-cli.xml L2VPN-status-codes.xml SR-internal-plan-kicker.xmlIETF-L2NM-internal-plan-kicker.xml IETF-TE-multi-vendor-iosxr-netconf.xml L3VPN-AA-notification-settings.xml SR-multi-vendor-iosxe-cli.xmlIETF-L2NM-plan-notification-settings.xml IETF-TE-plan-notification-settings.xml L3VPN-cfp-configuration-kicker.xml SR-multi-vendor-iosxr-netconf.xmlIETF-L2NM-status-codes.xml IETF-TE-status-codes.xml L3VPN-internal-plan-kicker.xml SR-plan-notification-settings.xmlIETF-L3NM-AA-notification-settings.xml L2VPN-AA-notification-settings.xml L3VPN-multi-vendor-iosxe-cli.xml SR-status-codes.xmlIETF-L3NM-internal-plan-kicker.xml L2VPN-cfp-configuration-kicker.xml L3VPN-multi-vendor-iosxr-netconf.xml xe-ip-sla-resource-pool.xmlIETF-L3NM-plan-notification-settings.xml L2VPN-internal-plan-kicker.xml L3VPN-plan-notification-settings.xml xr-sman-id-resource-pool.xmlIETF-L3NM-status-codes.xml L2VPN-multi-vendor-iosxe-cli.xml L3VPN-status-codes.xmlIETF-TE-cfp-configuration-kicker.xml L2VPN-multi-vendor-iosxr-netconf.xml RSVP-TE-status-codes.xmlroot@nso-193:~/tsdn40_m2/nso-5.7-tsdn-4.0.0-M2/config# cd ..root@nso-193:~/tsdn40_m2/nso-5.7-tsdn-4.0.0-M2# ncs_cli -u adminUser admin last logged in 2022-02-18T22:09:49.932596+00:00, to nso-193, from 10.21.93.73 using cli-sshadmin connected from 10.21.93.73 using ssh on nso-193admin@ncs> configure Entering configuration mode privateadmin@ncs% load merge xml/commit-queue-settings.xmlError: failed to open file: File/directory does not exist. File name: commit-queue-settings.xmlThe file path is relative to the directory in which ncs_cli is opened.Example:If I'm in the path: /home/rechand/Downloads/nso-5.7-tsdn-internal-4.0.0-M2<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"><pre> ~/Downloads/nso-5.7-tsdn-internal-4.0.0-M2 > ncs_cli -u admin admin@ncs> confEntering configuration mode private[ok][2022-02-18 17:36:36][edit]admin@ncs% load merge Possible completions: <filename/terminal> CHANGES conf/ core-fp-packages/ example-packages/ fp_data.json get_technical_support_data.sh init_data/ installer/ local-install/</pre></div></div>If you click the <tab> key after you type "load merge" it will try to do auto-completion and will show you the available files/directories.For your case, the "commit-queue-settings.xml" is in the "config" directory.If you still need help next week, then we can do a webex.Thanks,RegiThat is correct. If you look at the console output in my last reply: the command steps are:root@nso-193:~/tsdn40_m2/nso-5.7-tsdn-4.0.0-M2/config# lsroot@nso-193:~/tsdn40_m2/nso-5.7-tsdn-4.0.0-M2/config# cd ..root@nso-193:~/tsdn40_m2/nso-5.7-tsdn-4.0.0-M2# ncs_cli -u adminadmin@ncs> configureadmin@ncs% load merge xml/commit-queue-settings.xmlBut you're "commit-queue-settings.xml" is not in an xml folder as per your output its in config folder (~/tsdn40_m2/nso-5.7-tsdn-4.0.0-M2/config) . The very first XML file.<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"><pre>root@nso-193:~/tsdn40_m2/nso-5.7-tsdn-4.0.0-M2/config# lscommit-queue-settings.xml IETF-TE-internal-plan-kicker.xml L2VPN-plan-notification-settings.xml SR-cfp-configuration-kicker.xmlIETF-L2NM-AA-notification-settings.xml IETF-TE-multi-vendor-iosxe-cli.xml L2VPN-status-codes.xml SR-internal-plan-kicker.xmlIETF-L2NM-internal-plan-kicker.xml IETF-TE-multi-vendor-iosxr-netconf.xml L3VPN-AA-notification-settings.xml SR-multi-vendor-iosxe-cli.xmlIETF-L2NM-plan-notification-settings.xml IETF-TE-plan-notification-settings.xml L3VPN-cfp-configuration-kicker.xml SR-multi-vendor-iosxr-netconf.xmlIETF-L2NM-status-codes.xml IETF-TE-status-codes.xml L3VPN-internal-plan-kicker.xml SR-plan-notification-settings.xmlIETF-L3NM-AA-notification-settings.xml L2VPN-AA-notification-settings.xml L3VPN-multi-vendor-iosxe-cli.xml SR-status-codes.xmlIETF-L3NM-internal-plan-kicker.xml L2VPN-cfp-configuration-kicker.xml L3VPN-multi-vendor-iosxr-netconf.xml xe-ip-sla-resource-pool.xmlIETF-L3NM-plan-notification-settings.xml L2VPN-internal-plan-kicker.xml L3VPN-plan-notification-settings.xml xr-sman-id-resource-pool.xmlIETF-L3NM-status-codes.xml L2VPN-multi-vendor-iosxe-cli.xml L3VPN-status-codes.xmlIETF-TE-cfp-configuration-kicker.xml L2VPN-multi-vendor-iosxr-netconf.xml RSVP-TE-status-codes.xml</pre></div></div>Hi Reginald,I see there are 4 updates of this wiki today. I used version 5 command which is "load merge xml/commit-queue-settings.xml" instead of "load merge config/commit-queue-settings.xml. The latest version V6 has the right path.Now I am able to successfully load merge dispatch-map-settings.xml. Thanks for looking into the issue.Glad to hear it!Thanks,Regi |
Device mapped to different RFS throwing error message & not able to sync: Hi Team,Device mapped to different RFS throwing error message ; not able to sync.TB2-PE-C device is added to RFS-2, but in the sync it's throwing error message for PE-C on rfs-1admin@ncs% request devices sync-fromsync-result { device rfs-1 result false info illegal reference devices device rfs-1 config l2vpn-rr-parent-route-policy bgp_in TB2-PE-C device}sync-result { device rfs-2 result true}admin@ncs% show devices lsa dispatch-mapdevice TB2-P-BOTTOMLEFT { ned-id cisco-iosxr-nc-7.4:cisco-iosxr-nc-7.4; remote-node rfs-2;}device TB2-P-BOTTOMRIGHT { ned-id cisco-iosxr-nc-7.4:cisco-iosxr-nc-7.4; remote-node rfs-1;}device TB2-P-TOPLEFT { ned-id cisco-iosxr-nc-7.4:cisco-iosxr-nc-7.4; remote-node rfs-1;}device TB2-P-TOPRIGHT { ned-id cisco-iosxr-cli-7.38:cisco-iosxr-cli-7.38; remote-node rfs-1;}device TB2-PE-A { ned-id cisco-iosxr-nc-7.5:cisco-iosxr-nc-7.5; remote-node rfs-1;}device TB2-PE-B { ned-id cisco-iosxr-nc-7.5:cisco-iosxr-nc-7.5; remote-node rfs-1;}device TB2-PE-C { ned-id cisco-iosxr-nc-7.5:cisco-iosxr-nc-7.5; remote-node rfs-2;}device TB2-PE-D { ned-id cisco-iosxr-cli-7.38:cisco-iosxr-cli-7.38; remote-node rfs-1;}device TB2-PE-E { ned-id cisco-iosxr-cli-7.38:cisco-iosxr-cli-7.38; remote-node rfs-1;}device rfs-1 { ned-id cisco-nso-nc-5.7:cisco-nso-nc-5.7; local;}device rfs-2 { ned-id cisco-nso-nc-5.7:cisco-nso-nc-5.7; local;}admin@ncs% exitadmin@ncs> show devices listNAME ADDRESS DESCRIPTION NED ID ADMIN STATE-----------------------------------------------------------------------------TB2-P-BOTTOMLEFT 10.194.63.192 - cisco-iosxr-nc-7.4 unlockedTB2-PE-C 10.194.63.196 - cisco-iosxr-nc-7.5 unlockedadmin@ncs> show devices listNAME ADDRESS DESCRIPTION NED ID ADMIN STATE--------------------------------------------------------------------------------TB2-P-BOTTOMRIGHT 10.194.63.193 - cisco-iosxr-nc-7.4 unlockedTB2-P-TOPLEFT 10.194.63.190 - cisco-iosxr-nc-7.4 unlockedTB2-P-TOPRIGHT 10.194.63.191 - cisco-iosxr-cli-7.38 unlockedTB2-PE-A 10.194.63.194 - cisco-iosxr-nc-7.5 unlockedTB2-PE-B 10.194.63.195 - cisco-iosxr-nc-7.5 unlockedTB2-PE-D 10.194.63.214 - cisco-iosxr-cli-7.38 unlockedTB2-PE-E 10.194.63.213 - cisco-iosxr-cli-7.38 unlocked | Setup details:CFS-10.194.63.169RFS1-10.194.63.170RFS2-10.194.63.242Credentials: admin/Vtsisco@123!Hi RageshIt looks like the device was moved from one rfs node to another.Can you please let us know the exact steps you followed?Thanks.Hi Nikhil,Devices are onboarded to NSO via DLM-NSO sync, first time TB2-PE-C onboarded on rfs-1 ; the second time while attaching the device are onboarded to rfs-2.Hi Nikhil,We need the server for sanity, Please let us know the status of the issue.Hi RageshIt looks like an issue and we are checking it. The parent route policy is not getting cleared during the clean-up/deletion of the service.For a workaround, please delete the parent route policies from both the rfs node(steps below) and then do the device sync-from.<ol>Go to the rfs node.unhide tsdndelete l2vpn-rr-parent-route-policycommit</ol>Let us know if that resolves the issue.Thanks.Hi RageshPlease let us know if you were able to do the devices sync-from using the above steps.We have also created an internal Jira ticket() to look into the issue.Thanks,NikhilHi Nikhil,As discussed, raised bug for the issue, Please take a look on the issue.Closing the issue. Cdet() has been filed for this issue. |
Should Redeploy work for Zombie services?: A service is created then the device is moved out of sync, the service is then deleted and it moves to Failed state in CNC, zombie state in NSO.At this point the restconf APIs for redeploy, redeploy-reconcile etc stop working and return a 404 (As the service is in zombie state), and I see these options are gone from NSO UI too. Cleanup works and is able to remove the service from NSO. We think this is expected behavior, by design.Dinesh(submitter) thinks - Although, The sync-from or sync-to operations at the service level actions should bind service config in-line between CNC and NSO and thus the Re-deploy at that point should be successful. Which should also be confirmed with NSO team.Can you comment on what operations are applicable at this state? And if something else should be done to make redeploy work here? | Hi Mukul,Could you help list NSO API's which were used?It would help if it followed the flow as described in the ticket here.Thank youThe ticket started on a different note, and the things mentioned there in the description are not entirely accurate. Please refer to the flow I mentioned below - that's all we want to confirm.A service is created then the device is moved out of sync, the service is then deleted and it moves to Failed state in CNC, zombie state in NSO.The following actions are AWLAYS available from cnc (because we don't have the ability to determine what is applicable) - (out of these clean-up seems to work)-Check-sync -<serviceKey>/check-syncRe-deploy - <serviceKey>/redeployRe-deploy dry-run<serviceKey>/redeploywith dry-run requested in bodyRe-deploy-reconcile<serviceKey>/redeploywith reconcile requested in bodyReactive-redeploy <serviceKey>/reactive-re-deployOf course the above actions fail as the node <serviceKey> above is not available. While other actions like clean-up - (just added example for l2vpn)(Takes service-name in body)but basically all actions which don't use the node itself -are working.Hi Mukul,Referring back to the support email thread from June 10th 2021 with subject line:RESTCONF API's for service level actionsError-recovery and Cleanup are the 2 API's that require service name and not serviceKey.For deletion failure, if the service goes in zombie state, there are 2 options/route to take: 1) Device does not come back online - cleanup NSO using cleanup action 2) Device has come back up and user wants to cleanup the service from device as well - use error recovery actions.Note: Zombie resurrection is not supported. Refer to point 11 on the release notes page:Please refer to the link below as an example for point 2:After the call with Dinesh this morning, he had a question asking what the difference between redeploy and error-recovery:sync-to.The major difference here being:1.) redeploy will only try to push the updated part of the config to the device if there is any modification to begin with using fast map. Thus, if the service is not updated, redeploy will not push any new change on the device.2.) Error-recovery:Sync-to will try to sync the device and push the whole config from NSOs device tree to the actual deviceHeld a call with Mukul as well as Dinesh to explain zombie clean up action. Referenced the support thread from 10th June 2021 to show only Error-recovery and Cleanup actions use "service name" and not "serviceKey". Explained the difference between re-deploy and error-recovery. Closing call was handled by Linh Ly on August 3rd 2021. |
Provision status should not change if no config change on device with transactional commit failure: Steps:1. Edit an L2VPN service by changing locator name to be an invalid one (with space in the string) from Service Manager2. From Commit manager -> Click Commit -> Yes CommitAn Error repot pops up as expected (screenshot attached)3. Click "Close"4. Now the Plan showed failed from Configuration Editor.The configuration on device has no change due to this failure. Should the provision status remain the same as before commit because this commit is in transactional mode.The confusing part presents on CNC UI, is after users see this error message. User select Cancel -> Leave. And see the provisioning state as "Failed". But in fact there is no changes on the device. | playload attached. Hi Crystal,There has been much debate with the NSO platform team about whether no-CQ service failures should result in plan showing failed state. You can read more about the discussion here : To summarize, the conclusion was that the platform team determined that plan should show failed status when no-CQ transaction fails and is aborted, even if there is no southbound change.The behavior you have described is expected in accordance to behavior defined by NSO platform team. To recover your service state, you can follow our error recovery procedure : For your case, because nothing was pushed southbound (and assuming there was no out of band changes), to fix service plan state, simply re-deploy the service.Please let me know if you have any additional questions.Thanks,Isaac KimHi Isaac, don't have access to . Could you include the transcripts of that ticket here?Hi Srinivasan,There doesnt seem to be a way to post the entire transcript, but here is a snippet from the platform team describing the behavior mentioned above:I would say that this works as expected since the failed leaf has the following description: <tt>This leaf is present if any plan component in the plan is in a failed state; i.e., a state with status 'failed', or if the service failed to push its changes to the network.</tt> <tt>I think the reasoning behind setting the failed leaf even for a non-CQ commit is that we want it to behave the same way in both cases. And as the description of the failed leaf says the push of changes to the network has failed in both cases, so it should be set in both cases.</tt> <tt>It is worth noting that the failed leaf can also be set by the side effect queue if a side effect fails for some reason. So even if we would not set the failed leaf for non-CQ commits if might happen that the side-effect queue will set the failed leaf.</tt>Thanks,Isaac KimHi,Please let me know if the error recovery procedure that was recommended fixed the plan state.Thanks,Isaac KimExpected behavior according to NSO platform team. |
CLI NED does not work at all: admin/Public12345! | Hi Yevgeny,I accessed to your NSO and changed PE-A to cli and it works fine. Please see the attachedThanks,LInhI am going to close the tick if I don't see any update in next few days.Thanks,Linh |
RON Failed plan "status-code-detail" has device name in incorrect key: Generally when we have a failed plan for a service, there is a section called "status-code-details" - and it has per device information about the error. In this section the name of the device is generally in "impacted-device" - but for a failed RON plan the name of the device is in "name".Because we have a screen in CNC that relies on this information - our logic is breaking because of changed key. Is this something that can be corrected?Attached: JSON representation of RON failed plan showing the name of the device as "name"Attached: CNC screen which relies on this JSON - with empty device name - because it expected "impacted-device" | Hi Mukul - could you please provide the steps to reproduce and also the NSO payload for which you landed into the above issue.Here is the NSO payload - { "cisco-ron-cfp:ron-ml": { "mode": "transponder", "name": "BLUE_OLS_BTMLFT_TPRT_400_TR", "dac-rate": "1x1", "bandwidth": "400", "end-point": [ { "end-point-device": "P-BOTTOMLEFT", "terminal-device-packet": { "interface": [ { "index": 0, "ip-address": { "v4": "20.20.10.46/30" } } ] }, "terminal-device-optical": { "line-port": "0/0/0/1", "transmit-power": -90 } }, { "end-point-device": "P-TOPRIGHT", "terminal-device-packet": { "interface": [ { "index": 0, "ip-address": { "v4": "20.20.10.45/30" } } ] }, "terminal-device-optical": { "line-port": "0/0/0/1", "transmit-power": -90 } } ], "grid-type": "100mhz-grid", "circuit-id": "2", "ols-domain": { "service-state": "UNLOCKED" } }}Steps to reproduce are just execute the payload - and if the plan fails - then the failed plan doesn't match the regular TSDN CFP schema.I would just say that we should see if the failed plan construction differs from the TSDN CFP failed plan.Because I don't have absolute steps to make the service fail.Here is that section from a sample L3vpn failed plan with key as "impacted device"So did you send commit-queue parameters when executing the RON payload?These are being created using HTTP PATCH using CNC RESTCONF - which should be a wrapper over NSO restconf on URLWe're not specifying commit-queue parameters anywhere.Hey Mukul,I tried reproducing using the above payload but not able to fail the plan. Could you please provide the details of your nso server or share logs.Please use NSO as readonly. It is at admin / Public1234! Here you can find the service - BLUE_OLS_BTMLFT_TPRT_400_TRI also attached screenshot of the plan from both RON-ML and a normal L3VPN - one has impacted device in NSO.. one doesn'tSSH: nso552/Public1234!!Please use readonly. I don't own this NSOHi Mukul,Thanks for providing the server but its lot of information and was not so useful. We were looking at way to reproduce the issue as with the payload we couldnt reproduce. Anyhow I have opened an internal Jira ticket() for further analysis and fixing the issue in later build. I will go ahead and close this support ticket. Let me know if you have any doubts.HI Mukul, I am closing this ticket as i have opened an internal ticket to address this issue. Kindly see the comments section for more details.Thanks Mohit. I'm not able to view the other JIRA ticket. Please keep me updated with the status of the issue. |
LSA setup found issues: Hi,Installed an LSA setup and installation seems to be OK for both CFS and RFS nodes.However when I deploy services I see they all have incomplete plans with no error info. Can you please advise.Plan examples:Setup 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!Shlomi | Hi Sholmi,In the system provided, the subscription name is tsdn-kicker-events.Please note that it is rfs-kicker-events as per our wiki.I have already changed in your system. For ref:set devices device {rfs-node} netconf-notifications subscription rfs-kicker-events stream kicker-events local-user admin store-in-cdb trueI see the plan should be working as intended now.I will close this ticket if you see the issue is resolved.Thank youSahithiHi Sahithi,It seems to be working as expected now, thanks again for your help.ShlomiHi Shlomi,Your Welcome. Will be closing this ticket.ThanksSahithi |
Need XML payload to delete the performance measurement from Sr policy or ODN policy: Hi Nso team,we are using below payload to configure SR-PM for SR policies or ODN policies.from NSO UI, i am able to delete the Performance measurement . but i would need XML payload to remove the performance-measurement.can you please provide payload for the same? <config xmlns="http://tail-f.com/ns/config/1.0"><sr-te xmlns="http://cisco.com/ns/nso/cfp/cisco-tsdn-sr-te"><policies xmlns="http://cisco.com/ns/nso/cfp/cisco-tsdn-sr-te-sr-policies"><policy><name>L2NM-EVPN-SRTE-112-712</name><head-end><name>NCS55A2-SDN-112</name></head-end><tail-end>126.1.1.30</tail-end><color>722</color><binding-sid>722</binding-sid> <performance-measurement> <liveness-detection> <profile>SrPolicyLiveness2</profile> <invalidation-action>none</invalidation-action> <logging> <session-state-change/> </logging> </liveness-detection> <reverse-path-label>722</reverse-path-label> </performance-measurement> <!--performance-measurement> <delay-measurement> <profile>DelaySrPolicy</profile> <logging> <delay-exceeded/> </logging> </delay-measurement> <reverse-path-label>722</reverse-path-label> </performance-measurement--><path><preference>1</preference><dynamic><metric-type>igp</metric-type><pce /></dynamic></path></policy><policy><name>L2NM-EVPN-SRTE-30-712</name><head-end><name>ASR9901-SDN-30</name></head-end><tail-end>126.1.1.112</tail-end><color>712</color><binding-sid>712</binding-sid> <performance-measurement> <liveness-detection> <profile>SrPolicyLiveness2</profile> <invalidation-action>none</invalidation-action> <logging> <session-state-change/> </logging> </liveness-detection> <reverse-path-label>712</reverse-path-label> </performance-measurement> <!--performance-measurement> <delay-measurement> <profile>DelaySrPolicy</profile> <logging> <delay-exceeded/> </logging> </delay-measurement> <reverse-path-label>712</reverse-path-label> </performance-measurement--><path><preference>1</preference><dynamic><metric-type>igp</metric-type><pce /></dynamic></path></policy></policies></sr-te></config>Thanks,Arun.M.G | Connected with customer, requested for a call to create/verify the payload.To repharse my question:I would need to Disassociate ( delete) the Performance measurement from SR-POlicy.i would need to do the below action via Payload. policy srte_c_653_ep_126.1.1.128 performance-measurement no delay-measurementor policy srte_c_653_ep_126.1.1.128 no performance-measurementThanks,Arun.M.GI dont want to delete any PM profiles ( ie., global profile). Please try payload as below,<sr-te xmlns="http://cisco.com/ns/nso/cfp/cisco-tsdn-sr-te"> <policies xmlns="http://cisco.com/ns/nso/cfp/cisco-tsdn-sr-te-sr-policies"> <policy> <name>L2NM-EVPN-SRTE-112-712</name> <performance-measurement xmlns:nc="urn:ietf:params:xml:ns:netconf:base:1.0" nc:operation="delete"/> </policy> </policies></sr-te>Customer confirmed above payload works.Steps to retrieve XML payload for deletes.1.Log into NSO.2.Type in delete command needed for the delete. Do not commit.3.Run the command: show | compare | display xmlThis will generate related delete payload.Resolving ticket. |
Error recovery Action for slice sync-to/sync-from: 1. Create a slice contains PE-B as one of the SDPs2. Make PE-B out of sync.3. Edit the slice and commit to make the provisioning status = Failed4. Do "Check-Sync" action from transport slice table from CNC UI5. Do "Sync-to" action from transport slice table from CNC UI It returns "success": false (screenshot attached for more detail) But the provisioning status for the slice changed from Failed to Successful. Question 1: Should the Sync-to response be "success": true?6. Check audit log on NSO under /var/log/audit Question 2: I do not see either "check-sync" or "sync-to" action in audit.log. In order NSO release, we were able to validate the NSO action in audit.log. Is there changes in 6.0? Question 3: is /var/log/audit the correct location for nso audit.log? | Hi Crystal,1 : Please refer to the following Error Recovery Procedure . As out-of-sync is considered as a Persistent Failure , this will require manual intervention from the user to correct itself. Please refer to steps under Persistent Update Failure Recovery Flow.2 ; 3 : Please find the logs under /opt/log/ncsRegards,Nishad SubairHi Nishad,/opt/log/ncs does not seem to exist. Can you confirm the audit.log location again?# cd /opt/log/ncs-bash: cd: /opt/log/ncs: No such file or directoryThanks.-CrystalHi Crystal,As discussed , the latest audit logs are available under /var/log/ncs after the ncs restart.Please verify.Thanks,Nishad Subair.Hi Nishad,I am able to see the audit.log under /var/log/ncs after the ncs restart. From the chat, I understand "you don't see the most current log due to linux log rotation setting if the ncs is running since some days.". Is there any config change can be done to make the most current log visible instead of restart ncs?Thanks.-CrystalHi Crystal,In some cases , once the logs are rotated, NSO logging is not resumed until you either restart NSO or reload NSO.This is default behavior.You can check more on log rotate configs.Thanks And Regards,Nishad Subair.Here are some more observations in the audit log while make the NSO error recovery request from CNC:1. Actions show in audit.log Check-sync Re-deployReactive-Re-deployClean-up2. Actions NOT show in audit.logSync-toSync-from( as you stated in the chat, sync happens internally and in that case you might not be able to see sync action in log)3. Actions show partial info.Re-deploy dry run: in the log see "re-deploy" but no "dry run""INFO> 13-Sep-2023::00:17:52.023 nso-193 ncs: audit user: root/1221731 RESTCONF: request with https: POST /restconf/data/ietf-network-slice-service:network-slice-services/slice-service=Test-L3-106/re-deploy HTTP/1.1 trace-id=87e67403-99c5-40f9-9467-2326a5aac83d"Question: Should #3 log "re-deploy dry run" in the audit.log because from user's point of view, it is a different action that user request. If we use the same string, it is harder to trace based on the current audit.log.Hi Crystal,Regarding the Question #3 :dry-run is POST data in the redeploy request and post data would not be logged in audit log.Thanks And Regards,Nishad Subair.Hi Crystal ,As discussed , marking the ticket Done.Regards,Nishad Subair. |
LSA HA Custom Template: Please confirm in the case of CFS-HA and RFS-HA where should be the custom template load xml files has to be created. | Hi Dinesh, Custom-template must load on RFS nodes ONLY.Thanks,LinhHi Linh,I understand that for the appropriate device config extend, the template has to loaded at it's appropriate RFS node where the device is present.Please correct me If i'm wrong.Thanks,DineshYou are correct, Dinesh.-LinhHi Dinesh,I will close this issue in a few days if there is no update from your side.Thanks,LinhHi Linh,The created custom templates are unable to remove. From NSO the names of the templates are still lists out even after removing them from the following location.cd /var/opt/ncs/packages/custom-templates/templatesroot@ubuntu-10-194-57-50:/var/opt/ncs/packages/custom-templates/templates# ls -lrttotal 8<del>rw-r</del><del>r</del>- 1 root root 440 Apr 29 00:58 ct-logging.xml<del>rw-r</del><del>r</del>- 1 root root 557 Apr 29 01:16 ct-mtusize.xmlroot@ubuntu-10-194-57-50:/var/opt/ncs/packages/custom-templates/templates# rm -rf *Performed sudo NCS_RELOAD_PACKAGES=true /etc/init.d/ncs restart and sudo NCS_RELOAD_PACKAGES=force /etc/init.d/ncs restartNSO: 10.194.57.185 admin/Ovatest123@Enclosed is the comit-error when trying to apply those actual removed templates.Hi Dinesh,I debugged your setup yesterday and still saw a lot of CPU lock message. It could be because of that and CDB in a inconsistent between CFS and RFS. Could you please fix your system resource first? and Then start from fresh to see the issue is reproducable.Thanks,LinhHi Dinesh, There one step that you miss after removing custom-template from tar.gz file. You need manually to delete this custom-template from ncs_cli prompt.admin@ncs% unhide debugadmin@ncs%delete custom-template-info <custom-template-name>Thanks,LinhHi Linh,This works fine. I was able to delete custom templates info.Thanks,DineshClosed since it need manually to delete custom-template-info |
Not able to create a slice with Loopback interface.: Observed the below error, while creating a slice with Loopback interface.Error snippet:----------------Problem while provisioning the slice[{"Message":"/network-slice-services/slice-service{slice_30}/sdps/sdp{1}/attachment-circuits/attachment-circuit{1}/ac-tp-id (value "Loopback30"): ac-tp-id 'Loopback' is not supported with ac-tags 'attachment-circuit-tag-vlan-id'","nsoResponse":"/network-slice-services/slice-service{slice_30}/sdps/sdp{1}/attachment-circuits/attachment-circuit{1}/ac-tp-id (value "Loopback30"): ac-tp-id 'Loopback' is not supported with ac-tags 'attachment-circuit-tag-vlan-id'"}]Note: Getting the same error while trying to create a slice with Loopback 0 or any other interface ID. | Hi Renuka, this seems like a proper validation error message. Seems like the config you are trying to provision is not supported.I have found the exact validation and related ticket CDETS here : Related JSD :Seems like this validation was added as part of this CDETS ticket.Is there any ask to remove this validation? If not, I think we can junk this ticket.Thanks,Isaac Kim |
L3 NM service provisioning error while using jsonrpc: Validate transaction errors while provisioning L3 NM service using jsonrpc APIs.Issue is observed in CNC Provisioning (NSO) UI, as well as using NSO GUI.Note: There is no issue in provisioning L3 NM service through NSO CLI. But services are stuck in in-progress state (On some setups)Request:jsonrpc/validate_transResponse:{ "jsonrpc": "2.0", "error": { "type": "trans.validation_failed", "code": -32000, "message": "Validation failed", "data": { "errors": [ { "reason": "Python cb_validate error. '{L3-NM-SERVICE-3-NODES} not in /l3nm:l3vpn-ntw/vpn-services/cisco-l3nm:vpn-service-plan'", "paths": [ "/l3nm:l3vpn-ntw/vpn-services/vpn-service{L3-NM-SERVICE-3-NODES}/vpn-nodes/vpn-node{cp00}" ], "path": "/l3nm:l3vpn-ntw/vpn-services/vpn-service{L3-NM-SERVICE-3-NODES}/vpn-nodes/vpn-node{cp00}" } ] } }, "id": 295}Error details attached . | Fixed in drop 2. |
cant give long name to 5G slice : hi, I tried to provision network slice with name "L3-Dedicated-520", and it faild, since the underlying flat-l3vpn name got to long in one of the fields (maybe the vrf), since it is adding twice the word "internal". This limits the customer ability in giving meaningful name to the slice. server you can look 10.56.58.145 (nso574/Public1234!) | Hi ldan,We're planning to remove Flat-L3 for 5.0 so it wouldn't be an issue in future builds.ThanksPriyankafuture builds will have fix for CNC 5.0 |
NSO Service manager UI doesn't list the Custom FP: NSO: 10.195.165.55 admin/Ovatest123@After updating Custom FP in NSO path /var/opt/ncs/packages and reload success (with ignore validation ) , NSO CLI shows the Custom FP(show packages package package-version/oper status) , but NSO Service manager UI doesn't list the Custom FP. Would you please check | Hi Ajitha,Your packages don't seem to be compiled correctly. They're are missing the ".fxs" binary files which are used by NSO to load the models. Typically, they're located under a folder called "load-dir" at the root of the package.So for the L2NM package we have the following as an example:<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"><pre>ietf-l2vpn-nm/load-dir/ietf-l2vpn-ntw-cisco-augmentations.fxsietf-l2vpn-nm/load-dir/[email protected]/load-dir/[email protected]/load-dir/ietf-vpn-common.fxsietf-l2vpn-nm/load-dir/ietf-vpn-common-oper-status-aa-ext.fxsietf-l2vpn-nm/load-dir/ietf-l2vpn-ntw-nano-services.fxsietf-l2vpn-nm/load-dir/ietf-l2vpn-ntw.fxsietf-l2vpn-nm/load-dir/ietf-l2vpn-ntw-deviations.fxsietf-l2vpn-nm/load-dir/[email protected]/load-dir/[email protected]</pre></div></div>Let me know if you have anymore questions.Thanks,Regi |
CFS NSO node package reload took infinite time: Hi,I am trying to bringup the LSA NSO setup which has DLM package missing initially on CFS and RFS . After adding to /opt/ncs/packages and soft linked to /var/opt/ncs/packages, I tried request reload packages from ncs_cli. It took infinite time, never stopped the process. Later it seems aborted.After that I observed, some of the core packages and dlm package status is not up. To recover from the state, we restarted the node from vm center which eventually showed the all status are in up state. Didn't observed the same problem on RFS Node. DLM package installation went fine. NSO setup details:CFS: [email protected]: [email protected] [email protected]: ubuntudocAnother observation: LSA installation setup guide does not include dlm package installation details. Can this be added ? | HiDedeepya,Took a quick look at your setup. The VM sizes are way under recommended. For bare minimum lab use, it should be 8 vCPU, 64 GB RAM, 200 GB HDD. Your VMs are running with 4 vCPU, ~16GB RAM, 100GB HDD. This explain why your system operation is so slow.Please upsize your VMs then we can go from there. Currently the cluster is not even formed correctly.ubuntudoc@ncs> show cluster LAST RECEIVED NAME NAME STATUS EVENT NOTIFICATIONS -------------------------------------------rfs-1 rfs-2REMOTE LOCAL REMOTE NODE ADDRESS PORT CHANNELS USER USER STATUS TRACE ----------------------------------------------------------------------rfs-2 172.29.10.8 2022 - cisco cisco down disabled rfs-1 172.29.10.7 2022 - cisco cisco down disabledAnother point, the LSA installation instruction you pointed out was created for TSDN installation only. Since DLM, TM-TC, NCA are folded under NSO CFP group in CNC 6.0, we will update the procedures to include them.You can also install packages from latest Crosswork > NSO Deployment Manager >NSO Function Pack Bundles.Thanks Van for looking into it. We will increase to recommended size. Reg documentation as a general release note, please update the teams once it is available We can mark this resolved for now. Thanks Dedeepya. I am closing the ticket.Installation wiki was updated to include CLM, TM-TC, and NCA packages.Recommended VM size can be found in EC deck.Installation wiki was updated to include CLM, TM-TC, and NCA packages.Recommended VM size can be found in EC deck. |
When device credentials are being checked: Hi,Were trying to get to the bottom of CSCwb79704 - Playbook is able to run (UI or API) with wrong device credentials.Neha investigated it and saw that the credential check happens only when the new configuration is new and does not exist on the device, however, when it is already exists on the device, credential check is not performed as no config is pushed to the device. Is this logic part of NSO? Is it documented somewhere?Thanks,Mirel. | Hi Mirel,Yes , NSO checks for credentials only when there is a difference.When the config already exists on the NSO then it does not perform the operation since there is no diff.Thanks and Regards,Nishad Subair,Thanks for the confirmation. Is this documented in any NSO guide/wiki/doc?In the cdet CSCwb79704, user is trying to configure the attached service and we see that the service gets configured even if he passes wrong credentials for the devices. I am not completely sure what the service is trying to configure here, but it works with wrong device credentials even for the first time. From NCA playbook, we have verified that the credentials entered by the user are being set in NSO. Can you please take a look and let us know if device cred check is expected here or not. Hi Neha,I am not sure if the config is being pushed to the device here, looking at the template. To confirm, can you provide the complete NSO logs with xpath trace and trace enabled on the device? Or provide the setup with error.NSO throws an error only when there is an attempt to connect to the device. NSO can connect to device either via device config push or user trying to connect/sync-from/sync-to manually using the command on device tree. Device config push can be done via service or pushing the config on device from NSO.Please look at NSO getting started guide or the development guide for more info about NSO device manager throwing errors.ThanksSahithiHi Sahithi,Please find below the NSO details, where service has been installed. you can take a look at the logs and also try doing some configurations if needed. Also providing the payload for the config that user has tried to do here:NSO: 172.20.200.70admin/Cwork123!Devices: xrv9k-1 : 192.168.6.50 admin/cisco123xrv9k-2 : 192.168.6.51 admin/cisco123Config:"params": {"config": {"tailf-ncs:services": {"lowlatencypolicies:lowlatencypolicies": [{"devices": [{"name": "xrv9k-2","tailend": [{"color": 3000,"forward-class": 1,"ipaddress": "10.3.0.4","tailendname": "xrv9k-1"}]}],"name": "test"}]}},"nso_instance": "nso101","operation": "configure","path": "/ncs:services/lowlatencypolicies:lowlatencypolicies"Please let me know, if you need anything else from my side.As discussed on the call, NSO exhausts all methods of authentication before throwing connection refused error.Please check NSO guides for more on this behavior.Will be closing the ticket as there is no issue on NSO or TSDN CFP.ThanksSahithi |
How TSDN 2.0 Packages Handle "out-of-sync" devices: Hi Team,Customer environment requires that certain level of provisioning is done outside of the CNC/NSO services which requires a procedure for CNC provisioning the TSDN services that contemplates this scenario.The "no-out-of-sync-check" commit option available on the UI seems to cover that requirement of Create and Modify instances but when it comes to deletion, that option is not available leading to an incoherent status since the IETF-L3NM (l3vpn-ntw vpn-service) is deleted but the flat-l3vpn instance fails to delete (and therefore the device configuration is not removed).We end up with zombie entry and flat-l3vpn service plan shows this:ncsadmin@ncs-dectf1nsosrv1# show flat-L3vpn-plan POST BACK ACTIONTYPE NAME TRACK GOAL STATUS CODE STATE STATUS WHEN ref STATUS-----------------------------------------------------------------------------------------------------------------------------------------------------------self self true - - init not-reached - - - ready not-reached - - -endpoint DEVLF1SLR01_23 true - TSDN-L3VPN-302 init failed 2022-05-02T16:56:41 - - cisco-flat-L3vpn-fp-nano-plan-services:config-apply not-reached - - - ready not-reached - - - plan failed plan error-info message "Network Element Driver: device DEVLF1SLR01: out of sync" plan status-code-detail endpoint DEVLF1SLR01_23 code TSDN-L3VPN-302 context "Device out of sync" context-msg "Network Element Driver: device DEVLF1SLR01: out of sync" severity ERROR recommended-action "Check sync between device and NSO, and perform recovery steps."Our request is to:Understand what is the correct instance deletion process from UI when the device is out-of-sync;How to recover from this status;</ul>Best Regards,Fbio Gameiro | Hi Fabio,For out-of-sync devices - no-networking flag is used to make sure nothing goes to device .Use this flag as true for this case.Please follow this document to understand recovery process.TSDN Error Recovery Scenarios : Hope the above steps helps to understand recovery process.ThanksPriyankaHi Priyanka, Thanks for the clarification. Regarding the "no-out-of-sync-check" option is only available on the CNC UI for Edit/Create operations. The delete "button", when pressed and upon confirmation, doesn't give the chance to select the "no-out-of-sync-check" option (screen in attach) and therefore we will reach a "out-of-sync" issue and the deletion wont go through.What is the solution for deletion? Is the solution enabling "devices global-settings out-of-sync-commit-behaviour accept" or is there any other option?Regarding the recovery process described in the page you provided I start by seen a discrepancy between, for example, the "devices global-settings commit-queue enabled-by-default true" as "Pre-requisite config settings on NSO ." when the installation guide actually loads an XML file "config/commit-queue-settings.xml" which has "commit-queue enabled-by-default false" What are the recommended "devices global-settings" settings, namely on the commit-queue? Hi Fabio,As per webex discussion looks like you might need to try out actual CNC 2.0 packages and see if it there you see clean up action problem.We have gone over what all is supported by NSO and CNC UI for CNC 2.0 .I have tried to cover all your questions in webex.As per your confirmation i will close this ticket .ThanksPriyanka |
Need info on NSO LSA standalone setup change to HA setup and also upgrade from 5.0 to 6.0: NCS version: nso-6.1.linux.x86_64.installer.binCFP: -tsdn-5.0.0.tar.gzWe have 5.0 CCO image in SH unid setup with 52k services which has L2vpn and l3vpn services with SR/RSVP transports.Need help in below 2 tasks to do:1] Do we have any way/workaround to upgrade from 5.0 to 6.0 along with services migration?2] And also, we have installed NSO LSA setup in 5.0 without HA., do we have any possible to change the same setup with HA ?we shall sync up if needed.Thanks,Arun.M.G | 1] Do we have any way/workaround to upgrade from 5.0 to 6.0 along with services migration?>> TSDN supports core-fp upgrades hence L3 and SR-TE upgrade is supported but not L2, RSVP-TE.2] And also, we have installed NSO LSA setup in 5.0 without HA., do we have any possible to change the same setup with HA ?>> Regarding HA Conversion : Setting up HA is a standard NSO procedure and please refer to NSO documentation.We recommend that user can do following:1. Upgrade setup from 5.0 to 6.0 using guide -> 2. Move the setup from LSA to LSA + HA using NSO documentation here -> nso_admin_guide-6.1.pdf Chapter 7 : High AvailabilityRegards,Janaki DuggiralaHi Janaki,I would need to have NSO LSA HA with L3 deployement. does the "nso_admin_guide-6.1.pdf Chapter 7 : High Availability" covers the same?and also, i already have NSO LSA installed and it has services too. wanted to convert that to LSA HA . please provide document for that,thanks,Arun.M.Gcan you please provide me wiki that has steps to do ?Converting to LSA HA is standard NSO procedure, you can use NSO guidenso_admin_guide-6.1.pdf Chapter 7 : High AvailabilityNSO admin guide contains many useful sections and example sets such as Page 87,"""reference to a container-based example of the combined layer-2 and layer-3 BGP scenario can be found in the NSO example set. See the examples.ncs/development-guide/high-availability/ hcc/README"""Customer confirmed ticket can be closed at this time since setup is not available. |