input
stringlengths 48
5.67k
| output
stringlengths 0
15.3k
|
|---|---|
Does RSVP TE Tunnel supports IPv6 address?: My CW is an IPv6 deployment with IPv6 devices onboarded. While creating RSVP Tunnel from UI, the source, destination node ID and node-id under numbered-node-hop takes IPv4 address but not IPv6. So I entered IPv4 addresses and commit. The tunnel is created. Shouldnt we accept IPv6 address as well since this is an IPv6 setup?Here is the reply from our CNC DE:I think we are limited to IPv4 MPLS tunnels only when it comes to RSVP TE tunnels - you may want to double check with the COE and NSO CFP experts.From the rsvp-te/ietf-te service model point of view which is a standard ietf model that NSO CFP examples package implements, the schema only allows IPv4 addresses (type yang:dotted-quad )For IPv6 usecase, I think usecase might be to support "MPLS Traffic Engineering Static IPv6 Routes over MPLS TE IPv4 Tunnels" as described here - again this we need to confirm with our domain experts.BTW, on RSVP-TE, it is still same CNC 2.0 functionality as far as the NSO CFP/CAT is concern. | Hi Crystal,CFP has done the standard IETF-TE implementation for the RSVP-TE use-case. There were no new requirements from CNC 2.0 to 3.0 for RSVP-TE use-case. Please work with PLMs on use-cases where IPv6 support is required and we can plan for it in 4.0.--Raghavi.PermalinkEditDeleteHi Crystal,CFP has done the standard IETF-TE implementation for the RSVP-TE use-case. There were no new requirements from CNC 2.0 to 3.0 for RSVP-TE use-case. Please work with PLMs on use-cases where IPv6 support is required and we can plan for it in 4.0.--Raghavi. |
frame size config in Y1731 profile : we have <frame-size>2000</frame-size> config in y1731-profile.Even though , if we dont give this tagging , it is always pushing the packet size 2000 config to device.it is not able to unconfigure the packet size. how to delete this packet size using payload. removing the frame size tag doesnt help.attached payload. ethernet sla profile loss type cfm-synthetic-loss-measurement probe send burst every 60 seconds packet count 60 interval 1000 milliseconds priority 2 packet size 2000 | Hi Arun,Please provide the given ned-id's to the devices referred in the payload.--Raghavi.The devices are managed with 7.3.1 and it is CLI NED : cisco-iosxr-cli-7.33 Hi Arun,From the yangs we have default value as 1000 for type synthetic-loss and delay. so even if you remove frame-size from your payload its going to configure the default value which is 1000. Its not possible to un-configure packet size when you choose type as synthetic-loss or delay, when type is loss it wont configure the packet size.But in your case why packet size is 2000 even after frame-size is removed from the payload. Let me know the best time we can go over the issue on your setup.--Raghavi. |
Hostname changed in nso - Dispatch map not updated: Steps performed for the observation:Added a device (ron-8201-1) with incorrect hostname(name: NODE_IP).Deleted the device.Added the same device(ron-8201-1) with correct hostname.Performed device SSH Fetch-host keys, Sync-from, check-sync and request cfp-common-actions sync-dispatch-map.Now tried to provision a service from CNC UI: But receiving error message " Enter a valid device name present in the core-fp-common:dispatch-map.Tried the same service provisioning from NSO, service created successfully. Kindly help to confirm how cnc gets the disptach-map update, so as to avoid the dispatch-map error | Hi Ajitha,I assume the screenshot is taken after you updated the device (both NSO device tree and the value you entered on UI for RoN service). If so, according to the error message, it seems CNC UI is still trying to push the ron-ml service payload with the old device/endpoint name (NODE_IP), which doesn't exist in the dispatch-map, and hence it seems a bug on the UI. Please let me know if my assumption is not correct and if you would like a webex to debug more.Please check above comment.Not a CFP issue. |
Import L3vpn service with SRv6 routing protocol failed with M7 CFP: In CFP M7, it adds a few config to support L3VPN over SRv6 TE. By adding the extra config in the .xml file. It failed to import with following error. Can you help to take a look?Payload attached.NSO version: 5.5.2.9TSDN FP: 3.0.0 M7 | Hi Crystal,It looks like you use a wrong xml tag for srv6. Please fix your payload by comparing it with this linkThanks,LinhThanks Linh for sharing the link. After replacing <ietf-l3vpn-ntw-cisco-augmentations_srv6> ; </ietf-l3vpn-ntw-cisco-augmentations_srv6> with <srv6 xmlns="http://cisco.com/ns/nso/fp/examples/ietf-l3vpn-ntw-cisco-augmentations"> ; </srv6>The .xml file is imported and provisioned successfully.One more question. I did a "Config View" from CAT UI and from there I can copy the payload which is in json format. I converted the json to xml and that's how I get to use <ietf-l3vpn-ntw-cisco-augmentations_srv6> in the .xml file. Should the "Config View" generate a correct name space, to make it easier for the user? Not sure is it NSO or CNC should take care of that part?Thanks.Hi Crystal,You could get json payload by following these steps1. Load merge XML payload and commit2. From nso configuration mode enter this command show l3vpn-ntw vpn-services vpn-service <service-name> | display jsonYou could save json payload to a file if you want show l3vpn-ntw vpn-services vpn-service <service-name> | display json | save <filename>Hope that is what you look for-LinhIt is the issue on CAT UI in convert the payload from JSON to XML format |
import tailf-ncs { prefix ncs; } missing from l2nm and l3nm deviations yang model changes resulting in the java binding compilation failure - this need a fix on yang files: import tailf-ncs { prefix ncs; } missing from l2nm and l3nm deviations yang model changes resulting in the java binding compilation failure - this need a fix on yang files: 1. ietf-l3vpn-ntw-deviations.yang 2. ietf-l2vpn-ntw-deviations.yang+ import tailf-ncs { prefix ncs; } | the TSDN 4.0 - 1.0 was used thus the ticket is under "" please help to correct it to CNCCFP Thank you for bringing this up, it does seem like we are missing import statements for tailf-ncs when we brought in new lsa-utils package integration.This will be fixed for TSDN 4.0 M2Resolved in M2, closing ticket. |
Route-policy PASS_ALL gets added by default for L3VPN service: During testing observed that route-policy PASS_ALL gets added by default for L3VPN service.Please find attached the payload, native configs, device configs for reference.route-policy PASS_ALL is not included as part of payload and does not exist on device configs as well. But still it gets added during provisioning of L3VPN service.I have collected logs on cfs and rfs VMs at | Found out that this seems to be existing behavior in CFP for L3VPN service. Opened sev6/enhancement cdets as per the discussion with Sahithi.This is an existing behaviour in CFP for L3VPN service. Below sev6 CDET has been opened for the enhancement. |
TSDN 5.0.0 - M2 - wiki has wrong info for IETF TE : 1. Under - the yang file should not be cisco-flat-L2vpn-fp.yang.2. Under - please correct the version of draft used | Hi Quy,I have updated the mentioned changes in the Wiki. Let us know if anything else is required or we may close the ticket.Thanks,NikhilHi Nikhil,Thanks for fixing the wiki on M2 - please close the ticket.Regards,-QuyUpdated the wiki as requested by the user. |
L2VPN service deletion struck in "in-progress" state for last 1 hour for Servcie: L2VPN-ASR9901-1-4-t-ldp-Vlan3154: I see L2VPN service deletion struck in "in-progress" state for last 1 hour for Servcie: L2VPN-ASR9901-1-4-t-ldp-Vlan3154 (deletion of other L2VPN services are going fine), can someone have a look as it is blocking me to move to M8?admin@ncs> show l2vpn-ntw vpn-services vpn-service-plan L2VPN-ASR9901-1-4-t-ldp-Vlan3154 planplan component self selfstate initstatus not-reachedstate readystatus not-reachedback-track trueplan component ietf-l2vpn-ntw-nano-services:vpn-node ASR9901-1state initstatus reachedwhen 2022-07-08T00:40:08state ietf-l2vpn-ntw-nano-services:config-applystatus not-reachedstate readystatus not-reachedback-track trueplan component ietf-l2vpn-ntw-nano-services:vpn-node ASR9901-4state initstatus reachedwhen 2022-07-08T00:40:08state ietf-l2vpn-ntw-nano-services:config-applystatus not-reachedstate readystatus not-reachedback-track trueadmin@ncs> | Connected with user and helped him delete the services |
NetSim Devices onboard: I am trying to use netsim. I made some progress. But, was wondering if you can help me get a little further.When I use netsim to create network and generate a XML file out of it, the IP addresses assigned are 127.0.0.1Can I ssh to these dummy devices that are generated?If I can do that, then I can somehow try to onboard them to CNC too.These are the steps that I am following:Create Authgroup1. ncs_cli -u admin2. configure3. set devices authgroups group default default-map remote-name admin4. set devices authgroups group default default-map remote-passwordCreate netsim network1. source /opt/ncs/ncs-6.1_230206.110843541.f67ad1e6cc9d/ncsrc2. ncs-netsim create-network ../packages/ncs-6.0.2-cisco-iosxr-7.44.3.tar.gz 2 cp03. ncs-netsim ncs-xml-init > devices.xml4. ncs_load -l -m devices.xml | When you create the netsims network, it will generate "netsim/README.netsim" which contains a list of devices and associated ports.As an example, I have an entry for PIOSXR-0:<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"><pre>name=PIOSXR-0 netconf=12022 snmp=11022 ipc=5010 cli=10022 dir=/home/rechand/Repos/T-SDN/running/tsdn-lsa-test/netsim/PIOSXR-/PIOSXR-0</pre></div></div>you can ssh directly into the device using the device locally via:<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"><pre>ssh admin@127.0.0.1 -p 10023</pre></div></div>Thanks,Regi |
Intermittent issue - NSO throws NEDCOM Connect socket closed issue: Setup - 10.195.165.90- xrd1/xrd1Tried to Delete 2 Circuit style policy from CNC UI one after the other (tried second delete after first commit succeeded). Received attached error message "NEDCOM Connect socket closed issue".The issue is intermittent. | Seem like the device was unreachable at the time of service deletion. I checked your setup but I no longer see the service "CS413", were you able to delete the service?Thanks,RegiHello, please let us know if this issue is still valid.If no response is received, ticket will be resolved EOD Sept 2nd.Thank you.Initial RCA was done. No further response from customer. Closing ticket. |
NSO CFP - 5.0 - M1 yang files changed without revision dates.: Create this ticket to track a list of changed yang files from NSO 5.0 - M1 release without revision added.[ Notes: Email was sent to Sahithi/Van/Nipa regarding the same]cisco-sr-te-cfp-sr-odn.yangcisco-sr-te-cfp-sr-policies.yangcisco-sr-te-cfp-sr-common.yangcisco-sr-te-cfp-sr-policies-internal.yangcisco-sr-te-cfp-sr-odn-internal.yangcisco-sr-te-cfp-sr-common-internal.yangietf-l2vpn-ntw.yangcisco-flat-L2vpn-fp.yang | Hi Quy,We have updated the wiki to reflect the changes are part of M1 docs: . We will update the revisions on the yang models itself for M2 release.Thanks,RegiThanks Regi for the updates, will check the revision on M2 once released.Notes: did not see any updates regarding the cisco-sr-te-cfp-sr-odn.yang and cisco-sr-te-cfp-sr-odn-internal.yang from the wiki for Model and Payloads changes.Regards,-Quy |
NSO HA function observations: I am working on Crosswork SH 5.0 FT. During my SH testing with NSO HA setup I observed some issues. I am following the below guide for NSO HA setup and testing.My Testbed versionCW: 284cw-na-cat-5.0.0-291cw-na-aa-5.0.0-327cw-na-fp-tmtc-5.0.0-270NSO : ncs-6.1_230124.150846953.5043401bc5beHA : ncs-6.1_230202.150846214.1e784fae5f6b-tailf-hcc-6.0.0.tar.gzObservation 1: If I stop the NSO service on Master node, slave become master, but it is working in read-only mode. So that I am not able to perform any action in NSO. Also, the provisioning option in CW is not showing.If I bring up the nso service in master node then read-only mode changed as false in standby(working as master). Also, I can be able to see the all the option in CW service. Please share your feedback on my observation. Shall I raise CDET if my observation is valid ?Query 2:Do we have to DB sync up manually if the original master node comes up after some time? if yes, please share the procedure for the same. | Hey Karthikeyan,Can you please setup details?Thanks,RegiReporter shared the setup details:<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"><pre>172.28.174.203 --> NSO1 (master)172.28.174.205 --> NSO2 (Slave)172.28.174.254 --> VIPadmin / Ovatest123@</pre></div></div>So, with your NSO installation file there should be docs located in: `/opt/ncs/current/doc/pdf/nso_admin_guide-6.1_230124.pdf`To outline related HA details for your queries:<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"><pre>To prevent split-brain to occur, NSO 5.7 or later comes with a rule-based algorithm. The algorithm is enabled by default, it can be disabled or changed from the parameters: /high-availability/settings/consensus/enabled [true] /high-availability/settings/consensus/algorithm [ncs:rule-based]The rule-based algorithm can be used in either of the two HA constellations: Two nodes: one nominal primary and one nominal secondary configured as failover-primary. Three nodes: one nominal primary, one nominal secondary configured as failover-primary and one perpetual secondary.On failover: Failover-primary: become primary but enable read-only mode. Once the secondary joins, disable read-only. Nominal primary: on loss of all secondaries, change role to none. If one secondary node is connected, stay primary.Note: In certain cases the rule-based consensus algorithm results in nodes being disconnected and will not automatically re-join the HA cluster, such as in the example above when the nominal primary becomes none on loss of all secondaries.To restore the HA cluster one may need to manually invoke the /high-availability/be-secondary-to action.Note #2: In the case where the failover-primary takes over as primary, it will enable read-only mode, if no secondary connects it will remain read-only. This is done to guarantee consistency.Read-write mode can manually be enabled from the the /high-availability/read-only action with the parameter mode passed with value false.</pre></div></div>Let me know if you have anymore questions.Thanks,RegiHello, please let us know if this issue is still valid.If no response is received, ticket will be resolved EOD Sept 2nd.Thank you.Customer was provided information. No further response from customer. Closing ticket. |
Unable to bring up NSO RON FP due to Python validate error: Unable to bring up NSO RON FP due to Python validate error during load merge.Setup: 10.194.57.249 - nso249/nso249Kindly help.nso249@ncs% load merge nso-5.4.2-ron-mvp-0.5.0-RC/init_data/xml/config/RON-status-codes.xmlnso249@ncs% commitAborted: 'status-codes core-function-pack RON': Python cb_validate error. namedtuple() got an unexpected keyword argument 'defaults'nso249@ncs% | Hi Ajitha,What RON build did you download? Please use our RC build, which you can find at - Then follow installation steps listed inPlease note the basic system requirements are:Java: OpenJDK 11.2 or laterPython: 3.8 or laterPython Module "Paramiko" (Installed root level)xmllint (latest package)Thanks,VanHi Ajitha,Were you able to complete RON CFP bring up? Please let me know whether this case can be closed.Thanks,VanHi Ajitha,Please let us know if the issue was resolved and this case can be closed.Thanks,VanConfirmed with Ajitha that the original issue with Python was resolved and she agreed to close the case. |
Configure CS-SR-TE policy failed under 'reserve-path segment-list: Configure CS SR-TE Static Path + Explicit SID failed with the following error msg: Method failed : External error in the NED implementationfor device TB3-PE-C: command:RP/0/RPO/CPUO:TB3-PE-C(config-sr-te-pp-info)#reverse-path segment-listc_11000_ep_100.100.100.6_to_ep_100.100.100.7_restore_CS.% Invalid input detected at '^' marker.From the M1 wiki, could not find which supported version of IOSXR we need to use for this feature.Could someone take a look at our setup and let us know.NSO: 10.194.63.180 (nso/Vtsisco@123!)Dry run is also attached. | Can you please let us know the Cisco IOS XR version used to test this feature?hi Sahithi,the devices are with 7.5.2.19Iplease let us know which version we should use and please also add this info to the wiki for CS-SR-TE for reference. hi NSO CFP team,Any update on this case?We need to know which supported version recommended by your team to update our devices for CS-SR-TE.Thanks!Details present in wiki: |
[Vodafone] TSDN 2.0 Customisation Development Support: Hi Experts,We are in the process of doing customization for the L2NM/Flat-L2vpn packages of TSDN 2.0 for Vodafone and we are facing some blockers in the process. We seek some help regarding commit queues and the interconnect between L2NM/Flat-L2VPN packages and the core-fp-plan-notif-generator and core-fp-delete-tag-service packages.Would be good to have a Webex session with someone from the BU to clarify these topics in order to unblock the development. Please do let us know your availability and we can set up a Webex with the developers of the customization.Thanks ; Best Regards,Fbio Gameiro | Discussed with Fabio and he'll be setting up a call to discuss on the clarifications required.Hi FabioHad a call with the team and helped them with the doubts they had.Thanks,NikhilClosing the ticket as the required assistance was provided. Please open a new ticket in case of any more issues. |
TSDN 5.0.0 - M6 Patch 1 - wiki does not have sample payload changed: Please add sample payloads for IETF-L3, IETF-L2 and IETF-NSS changes. | Hi Quy,The changes as part of this TSDN 5.0.0 - M6 Patch 1 Release are mostly validations and there are no payload changes.We can use the existing payloads.Thanks And Regards,Nishad Subair.Closing this ticket as there are no model changes which attribute a need for payloads.Thanks,Regi |
L2VPN auto route target configuration: Hi,I tried to configure an L2VPN service with auto route using the following syntax:<vpn-target xmlns=> <auto-hub-rt/> </vpn-target>But I keep getting the following error message:<error> <error-type>application</error-type> <error-tag>malformed-message</error-tag> <error-path></error-path> <error-message>/l2vpn-ntw/vpn-services/vpn-service{L2VPN_NM-ELAN-MH-341}/l2vpn-ntw-cisco:vpn-target/auto-hub-rt: the 'when' expression "/ralloc:resource-pools/idalloc:id-pool" failed</error-message></error>I am using NSO server credentials: nso576 / Public1234!Can you please explain how should the rt-pool be defined, how should it be configured in the L2 function pack and how can the values be fetched after successful allocation?Shlomi | Hello,Regarding,Can you please explain how should the rt-pool be defined, how should it be configured in the L2 function packPlease use sample config below to define the rt-pool<config xmlns="http://tail-f.com/ns/config/1.0"> <resource-pools xmlns="http://tail-f.com/pkg/resource-allocator"> <id-pool xmlns="http://tail-f.com/pkg/id-allocator"> <name>evi-id-pool</name> <range> <start>1</start> <end>4000</end> </range> </id-pool> <id-pool xmlns="http://tail-f.com/pkg/id-allocator"> <name>evi-source-target-pool</name> <range> <start>1</start> <end>400</end> </range> </id-pool> <id-pool xmlns="http://tail-f.com/pkg/id-allocator"> <name>rt-id-pool</name> <range> <start>1</start> <end>65535</end> </range> </id-pool> </resource-pools> <l2vpn-ntw xmlns="urn:ietf:params:xml:ns:yang:ietf-l2vpn-ntw"> <id-pools xmlns="http://cisco.com/ns/nso/fp/examples/ietf-l2vpn-ntw-cisco"> <evi-id-pool-name>evi-id-pool</evi-id-pool-name> <evi-source-target-pool-name>evi-source-target-pool</evi-source-target-pool-name> <rt-pool-name>rt-id-pool</rt-pool-name> </id-pools> </l2vpn-ntw></config> More Sample payloads can also be viewed here -Regarding,how can the values be fetched after successful allocation?You can run the below command for evi-alloc-data: run show l2vpn-ntw vpn-services vpn-service-plan l2nm-evpn plan evi-allocation-data | display keypath | nomoreAll the allocations can be seen under the plan too -admin@ncs% run show l2vpn-ntw vpn-services vpn-service-planLet me know if this helps.Regards, Janaki DuggiralaCustomer requested information to configure route policy. Information was provided. Closing ticket. |
CNC/CW support of SRv6 with emphasis on L2VPN: From TSDN 4.1.1 FCS Release Notes and from TSDN 5.0.0 FCS Release Notes, it is mentioned that SRv6 is supported on XR 7.3.2 and on 7.5.1 and above.However, the phrasing there did leave some room for doubt, as it referred to "this feature", where it could also been interpreted that there are other versions of XR which are also supported, or partially support some features.Please assist to clarify if support for all SRv6 features is limited to the versions in the above comment. | As mentioned in the wiki, SRv6 is supported only on XR version 7.3.2, 7.5.1 and above.To expand on the versions supported:7.5.1 and above would mean, all the versions released after 7.5.1 including itself.XR versions supported for Srv6 are 7.3.2, 7.5.1,7.5.2,7.6.1, 7.6.2, 7.7.1, etc.. |
Re: NSO HW requirement TSDN 4.0.0 for CNC 4.0 and CAA 4.0: Hi,We would need to know if there is any changes in the NSO HW requirement ( standalone and NSO LSA) for CNC 4.0 and CAA 4.0 ?For CAA 3.0, we had below profile. Please let me know if we can continue the same or any changes required.Functional Setup: 8 Core CPU and 64 GB RAM and 250GB HD ( 20 devices and 100 services) Scale Setup: 24 Cores, 132 GB of RAM, and 1TB of HD ( 80 devices and 5k services)Thanks,Arun.M.G | Hi Arun,There is no change in HW requirement as of now.You can continue with existing specifications .Although CPU can be brought down to 8 from 24 for scale set up .(should not impact with a smaller number of CPUs.)As the cdb size grows during scale just make sure memory is at least twice or thrice the cdb size for best performance .I hope this answers your question .Thanks,PriyankaHi Arun,I had some discussion within our team and we decided let's stick with 16vCPU for scale lab .Also keep 256GB swap mem.ThanksPriyankaHi Priyanka,Thanks . Sure. is that swap mem is seperate than the RAM and Disk?Hi Arun,Yes Swap mem is separate.ThanksPriyanka |
Discrepency in L2VPN and L3VPN modify messages when device is in Out of Sync: Query is mentioned in the document attached | 1)From device, make a interface shutdown and in NSO dont sync the device.2)Now from CNC, we tried to edit the service of L3VPN and L2VPN with CVLAN ID for L3VPN and L2VPN (even MEPID)3)Now we got valid error in the CNC UI, that device is not in Sync with NSO. In Kafka logs we got some discrepancy for L2VPN and L3VPN, Please check below4)So we need to know why L2VPN is not having error message and L3VPN is having error message. 5)Due to this, AA is performing differently, For l3VPN it is Showing provisioning state as Failed and For L2VPN, it is showing as Success.Please provide the details as mentioned in the release notes:1) NSO Version: 5.5.2.72) CFP - M63) Device version used: 7.4.1 and 7.0.24) Steps followed are explained in the below comments5) used two services: L2VPN (7.4.1 device with srte and other device 7.0.2 without SR), L3VPN plain6) Plan messages are mentioned in the doc attached7) This issue is related to the plan messages difference that we see between l2vpn and l3vpn, Let me know if you need separate logs for this ?When the device is out-of-sync and user tries to commit any more changes to the service (with commit queue disabled), the commit itself is aborted. Hence, in this case, none of the plan components would fail and no notifiations would be generated.The behavior for L2NM and L3NM is the same in this case. Please let us know if your steps were different. Also share the service state notifications for the case you mentioned and complete NSO logs.If needed, we can have a webex session to debug further.Let me know your feasible time Nishad. we can meet and discussHi Nishad, we have tried this same scenario in 5.5.2.9 M7. we dont see this isssue is reproducible.we see NSO notification for Monitoring state with error info for both l2vpn and l3vpn.issue not seen in M7. attached logs.Thanks,Arun.M.G Hi Arun,Thank you for the update.As verified by the submitter , working fine in 5.5.2.9 M7. |
Get DRY-RUN/Commit ERROR "validation failed : '_ncs_XmlTag' object is not subscriptable : undefined" after changing HOP-TYPE from strict to loose for a RSVP-TE with explicit path: 1. Use CNC provisioning UI to successfully create a PCC-init RSVP-TE. The headend is a XE device (ASR-907) and tailend is a XRV9K 7.3.2 device. The RSVP-TE is created with explicit path with numbered-node-hop and hop-type is 'strict'2. Go back to CNC provisioning UI to edit the same RSVP-TE. Change hop-type from 'strict' to 'loose' and try to do dry-run and commit.3. Either doing Dry-Run or Commit, it ends up with popup error - "validation failed : '_ncs_XmlTag' object is not subscriptable : undefined" 4. Below is the RSVP-TE payload that's successfully provisioned { "ietf-te:tunnel": { "name": "RSVP-907-112", "source": "41.41.41.41", "head-end": "JSS-ASR-907", "tail-end": "xrv9k-732-112", "identifier": 4112, "description": "XE41 to XR112", "destination": "112.112.112.112", "hold-priority": 3, "setup-priority": 3, "traffic-steering": { "autoroute": { "announce": { "metric": { "constant": 2147483647 } }, "destination": [ { "address": "111.111.111.111" } ] } }, "p2p-primary-paths": { "p2p-primary-path": [ { "name": "path-explicit-41-112", "path-computation-method": "ietf-te-types:path-explicitly-defined", "explicit-route-objects-always": { "route-object-include-exclude": [ { "index": 1, "numbered-node-hop": { "node-id": "115.115.115.115", "hop-type": "strict" } }, { "index": 2, "numbered-node-hop": { "node-id": "116.116.116.116", "hop-type": "strict" } }, { "index": 3, "numbered-node-hop": { "node-id": "114.114.114.114", "hop-type": "strict" } }, { "index": 4, "numbered-node-hop": { "node-id": "112.112.112.112", "hop-type": "strict" } } ] } } ] } }} | Hi Jen-Shue, Was able to reproduce the issue. Please file a CDETs.Thanks,RegiIssue is being tracked by CDETs: |
Does CLI NED cisco-iosxr-cli-7.33 suports for 7.3.2 and 7.4.1 ?: From CNC 3.0 NSO SFS, it says there is only NETCONF NED support for 7.3.2 and 7.4.1 .Is CLI NED cisco-iosxr-cli-7.33 suports for 7.3.2 and 7.4.1 ? | Hi Arun,Here is the wiki with supported ned versions.This is the iosxr-cli version supported by M5 release.IOSXR CLI NED - 7.33.12Let me know if you have any questions.--RaghaviHi Raghavi,thanks for responding.My question was different. Does the CLI NED cisco-iosxr-cli-7.33 is supported for XR device versions 7.3.2 and 7.4.1 ?or is that only NETCONF NED support for those device version?Hi Arun,CLI NED 7.33 supports all image versions with CLI.--Thanks. |
config difference on NSO Native Config and ASR920: provision an L3VPN with no policy. one node it ASR9K and the other node is ASR920. No SR policy associated in the service.Compare the "Native config" and config on ASR920, observe the following. Can you confirm if this is expected?service payload attached.ASR920 IOS: 17.6.1ASR9K IOS: 6.7.2Config 1:On NSO Native Config:=================interface Loopback8 ip redirects vrf forwarding L3VPN_NM-IGP-IPV4-80 ip address 80.80.11.1 255.255.255.252 no shutdownOn ASR920:============interface Loopback8 vrf forwarding L3VPN_NM-IGP-IPV4-80 ip address 80.80.11.1 255.255.255.252 no shutdownDelta:=====ip redirects <--- do not see this line on ASR920Config 2: Under router bgpOn NSO Native Config:=================address-family vpnv4 unicast neighbor 80.80.11.2 activate exit-address-familyON ASR920:=========address-family vpnv4 unicast neighbor 80.80.11.2 activate neighbor 80.80.11.2 send-community extended exit-address-familyDelta:====See extra line on ASR920, "neighbor 80.80.11.2 send-community extended" | HI Crystal,We are working on getting the device access.--RaghaviThe original payload is not the correct one. Attached the right one here. Sorry for the confusion. Hi Crystal,This is the expected behavior. The NED translates activate into the two commands you have mentioned. Even on the device, if you set only activate, it automatically also configures the send-community extended. So we see only activate in NSO native config which internally configure send-community on the device.I would suggest if you see similar issues in future try to set directly on the device and see the behavior.--Raghavi. |
L2 Provision Slice Creation Issue: Hi,While creating L2 slice, i'm getting below error:"/resource-pools/idalloc:id-pool{None}/range/start is not configured".Attached the payload and resource pool configurations as screenshot | Hi Magesh,Please share your setup details and payloads. It would take a look after having these info.Regards,LinhHi Linh,Attaching the payload.Setup: UserId: ubuntudocpwd: ubuntudocRegards,Magesh Hi Magesh,After looking at your NSO, I don't see you define any id-pool for l2nm service. Please the attached screenshotPlease follow this link to define id-pool for l2nmThanks,LinhHi Linh,Thanks for the solution. That issue got solved. Now i get this,[{"Message":"External error in the NED implementation for device xrv9k-12: Mon Jul 10 22:18:35.821 PDTr","nsoResponse":"External error in the NED implementation for device xrv9k-12: Mon Jul 10 22:18:35.821 PDTrnrn% Failed to commit one or more configuration items during a pseudo-atomic operation. All changes made have been reverted.rn !! SEMANTIC ERRORS: This configuration was rejected by rn!! the system due to semantic errors. The individual rn!! errors with each failed configuration command can be rn!! found below.rnrnrnl2vpnrn bridge group UIT-Test-L2rn bridge-domain UIT-Test-L2_evi_1rn interface GigabitEthernet0/0/0/1.122rn!!% Invalid argument: VPLS Bridge domains not supported on this platformrn !rn !rn !rn!rnend"}]Same setup.Regards,MageshHi Magesh,Oh! XRv9K does not support VPLS Bridge domains. Please use ASR9K/NCS5000 platform to test this feature.Regards,Linh |
NSO LSA mode RFS node install error: Hi,Am trying to install NSO LSA mode RFS node. But post install of TSDN 4.0.0 M6, noticed that not all the packages are installed. I see the same output in another RFS node also. Could you please help resolve this issue. admin@ncs> show packages package package-version | select build-info ncs version | select build-info file | select build-info package sha1 | select oper-status error-info | select oper-status up | tab PACKAGE ERRORNAME VERSION FILE SHA1 VERSION UP INFO-----------------------------------------------------------------------------------------------------------------------------------cisco-flat-L2vpn-fp-internal 4.0.0 ncs-5.7.3-cisco-flat-L2vpn-fp-internal-EXAMPLE-4.0.0.tar.gz 12d4bb99 5.7.3 - -cisco-flat-L3vpn-fp-internal 4.0.0 ncs-5.7.3-cisco-flat-L3vpn-fp-internal-EXAMPLE-4.0.0.tar.gz 12d4bb99 5.7.3 - -cisco-ios-cli-6.77 6.77.9 ncs-5.7-cisco-ios-6.77.9.tar.gz 5a04c3bd6 5.7 X -cisco-iosxr-cli-7.39 7.39.5 ncs-5.7.3-cisco-iosxr-7.39.5.tar.gz f317f940 5.7.3 X -cisco-iosxr-nc-7.3 7.3.2 ncs-5.7-cisco-iosxr-7.3.2.tar.gz b1e6ce2b 5.7 X -cisco-iosxr-nc-7.315 7.315 ncs-5.7-cisco-iosxr-7.315.tar.gz c81c8124 5.7 X -cisco-iosxr-nc-7.4 7.4.2 ncs-5.7.2-cisco-iosxr-7.4.2.tar.gz 2d6642fb 5.7.2 X -cisco-iosxr-nc-7.5 7.5 ncs-5.7.2.1-cisco-iosxr-nc-7.5-efd16e5-2022-04-22.tar.gz efd16e5 5.7.2.1 X -cisco-iosxr-nc-7.6 7.6.1 ncs-5.7.3-cisco-iosxr-7.6.1.tar.gz 87fec449 5.7.3 X -cisco-iosxr-nc-7.7 7.7 - - - X -cisco-rsvp-te-fp 4.0.0 ncs-5.7.3-cisco-rsvp-te-fp-EXAMPLE-4.0.0.tar.gz 12d4bb99 5.7.3 - -cisco-sr-te-cfp-internal 4.0.0 ncs-5.7.3-cisco-sr-te-cfp-internal-4.0.0.tar.gz 12d4bb99 5.7.3 - -cisco-tsdn-core-fp-common 4.0.0 ncs-5.7.3-cisco-tsdn-core-fp-common-4.0.0.tar.gz 12d4bb99 5.7.3 - -core-fp-common 1.30.0 ncs-5.7-core-fp-common-1.30.0.tar.gz 82b8637 5.7 - -core-fp-delete-tag-service 1.0.5 ncs-5.7-core-fp-delete-tag-service-1.0.5.tar.gz 843f7ea 5.7 - -core-fp-plan-notif-generator 1.0.6 ncs-5.7-core-fp-plan-notif-generator-1.0.6.tar.gz 9256a63 5.7 - -custom-template-utils 2.0.9 ncs-5.7.2-custom-template-utils-2.0.9.tar.gz 1884026 5.7.2 - -flat-l2vpn-multi-vendors 4.0.0 ncs-5.7.3-flat-l2vpn-multi-vendors-EXAMPLE-4.0.0.tar.gz 12d4bb99 5.7.3 - -flat-l3vpn-multi-vendors 4.0.0 ncs-5.7.3-flat-l3vpn-multi-vendors-EXAMPLE-4.0.0.tar.gz 12d4bb99 5.7.3 - -lsa-utils 1.0.1 ncs-5.7.2.1-lsa-utils-1.0.1.tar.gz d23c015 5.7.2.1 - -rsvp-te-multi-vendors 4.0.0 ncs-5.7.3-rsvp-te-multi-vendors-EXAMPLE-4.0.0.tar.gz 12d4bb99 5.7.3 - -sr-te-multi-vendors 4.0.0 ncs-5.7.3-sr-te-multi-vendors-4.0.0.tar.gz 12d4bb99 5.7.3 - -admin@ncs> show packages package oper-status | tab PACKAGE PROGRAM META FILE CODE JAVA PYTHON BAD NCS PACKAGE PACKAGE CIRCULAR DATA LOAD ERRORNAME UP ERROR UNINITIALIZED UNINITIALIZED VERSION NAME VERSION DEPENDENCY ERROR ERROR INFO---------------------------------------------------------------------------------------------------------------------------------------cisco-flat-L2vpn-fp-internal - - - X - - - - - - -cisco-flat-L3vpn-fp-internal - - - X - - - - - - -cisco-ios-cli-6.77 X - - - - - - - - - -cisco-iosxr-cli-7.39 X - - - - - - - - - -cisco-iosxr-nc-7.3 X - - - - - - - - - -cisco-iosxr-nc-7.315 X - - - - - - - - - -cisco-iosxr-nc-7.4 X - - - - - - - - - -cisco-iosxr-nc-7.5 X - - - - - - - - - -cisco-iosxr-nc-7.6 X - - - - - - - - - -cisco-iosxr-nc-7.7 X - - - - - - - - - -cisco-rsvp-te-fp - - - X - - - - - - -cisco-sr-te-cfp-internal - - - X - - - - - - -cisco-tsdn-core-fp-common - - - X - - - - - - -core-fp-common - - - X - - - - - - -core-fp-delete-tag-service - - - X - - - - - - -core-fp-plan-notif-generator - - - X - - - - - - -custom-template-utils - - - X - - - - - - -flat-l2vpn-multi-vendors - - - X - - - - - - -flat-l3vpn-multi-vendors - - - X - - - - - - -lsa-utils - - - X - - - - - - -rsvp-te-multi-vendors - - - X - - - - - - -sr-te-multi-vendors - - - X - - - - - - -Below are login details of both RFS nodes :-172.20.63.144 (cnctest/Ovatest123@)172.20.63.145 (cnctest/Ovatest123@) | This is of high priority and am awaiting for your inputs. Could you please help prioritize this.Hi SreedharPlease check the pre-requisites required when CFP is installed. This is not a NSO issue but a setup issue.I have upgraded python version on your setup. The python3 version was pointing to python3.6 and hence the packages were not getting loaded properly. I have linked the python3 to 3.8 on both the rfs nodes and the packages are loading properly now.Let me know if we can close the ticket.cnctest@ncs> show packages package oper-status | tab PACKAGE PROGRAM META FILE CODE JAVA PYTHON BAD NCS PACKAGE PACKAGE CIRCULAR DATA LOAD ERROR NAME UP ERROR UNINITIALIZED UNINITIALIZED VERSION NAME VERSION DEPENDENCY ERROR ERROR INFO ---------------------------------------------------------------------------------------------------------------------------------------cisco-flat-L2vpn-fp-internal X - - - - - - - - - - cisco-flat-L3vpn-fp-internal X - - - - - - - - - - cisco-ios-cli-6.77 X - - - - - - - - - - cisco-iosxr-cli-7.39 X - - - - - - - - - - cisco-iosxr-nc-7.3 X - - - - - - - - - - cisco-iosxr-nc-7.315 X - - - - - - - - - - cisco-iosxr-nc-7.4 X - - - - - - - - - - cisco-iosxr-nc-7.5 X - - - - - - - - - - cisco-iosxr-nc-7.6 X - - - - - - - - - - cisco-iosxr-nc-7.7 X - - - - - - - - - - cisco-rsvp-te-fp X - - - - - - - - - - cisco-sr-te-cfp-internal X - - - - - - - - - - cisco-tsdn-core-fp-common X - - - - - - - - - - core-fp-common X - - - - - - - - - - core-fp-delete-tag-service X - - - - - - - - - - core-fp-plan-notif-generator X - - - - - - - - - - custom-template-utils X - - - - - - - - - - flat-l2vpn-multi-vendors X - - - - - - - - - - flat-l3vpn-multi-vendors X - - - - - - - - - - lsa-utils X - - - - - - - - - - rsvp-te-multi-vendors X - - - - - - - - - - sr-te-multi-vendors X - - - - - - - - - - Thanks,NikhilHi Nikhil, Great !! Thanks for fixing both the nodes. Yes, please go ahead resolving the case.Thanks,Sreedhar.Issue was fixed, hence closing the ticket.Hi Nikhil,Could you please let me know what are steps/commands used to fix this ? That will be helpful incase if hit this issue again.Thanks,Sreedhar. |
how/where do I configure restconf keep-alive?: I added flag of keepalive=true in ncs.conf (like described here - )but getting error "keepalive cannot occur here as a child to 'ncs-config'."under which leaf I should add this flag? couldn't find example in NSO documentation. Thanks | Hi Idan,Please double check where you put this flag in ncs.conf. It should be under <webui> like this sample <webui> <enabled>true</enabled> <transport> <tcp> <enabled>true</enabled> <ip>0.0.0.0</ip> <port>8080</port> <keepalive>true</keepalive> <keepalive-timeout>30</keepalive-timeout> </tcp> <ssl> <enabled>false</enabled> <ip>0.0.0.0</ip> <port>8888</port> <keepalive>true</keepalive> <keepalive-timeout>30</keepalive-timeout> <key-file>${NCS_CONFIG_DIR}/ssl/cert/host.key</key-file> <cert-file>${NCS_CONFIG_DIR}/ssl/cert/host.cert</cert-file> </ssl> </transport> <cgi> <enabled>true</enabled> <php> <enabled>false</enabled> </php> </cgi> </webui>Regards,LinhKeep-alive works by follow x-path structure |
NSO write operations failed due to some lock: Installed CNC6.0 203 build. Onboard NSO provider and devices. On CNC UI NSO state shows empty value. Our dlm dev took a look and the finding is "the write operations are failing on NSO due to some lock." Please see attached email for more details.Do we know how does NSO get to lock mode? Is there a workaround to unlock?Here is the NSO VM info:IP: 2001:420:284:2004:4:112:219:4024id/pw: root/Vtsisco@123! | Hello, On logging in to VM we have noticed commits going through with no errors (screenshot attached)Please provide any additional information/specific steps to reproduce the lock issue so we may troubleshoot further.Regards,Janaki DuggiralaUser has done following: delete the devices and providers from CNC and on board both of them again Confirmed it works now.In such cases restarting NSO will also unlock the commits. |
CSCwb77036 - Device username and NSO username are same - Umap is throwing an error: From: Mirel Sprung (msprung) <msprung@cisco.com>Date: Wednesday, May 4, 2022 at 3:22 PMSubject: RE: CSCwb77036 - Device username and NSO username are same - Umap is throwing an errorHi Hemant, Nipa, This bug was opened on NCA, and were trying to figure out how to address it.Is this a known issue that is documented in our official guides?I found this wiki that talks about adding usermap (umap) to NSO authgroup: .Thanks,Mirel. | I tried adding umap username in authgroup and it worked fine.Umap works fine as expected.Here is the screenshot :Screenshot is attached .ThanksPriyankaWaiting for Joby to provide details and issue reproduction.ThanksPriyankaHad chat with Joby ,he is okay to close cdet and jsd. |
L2vpn over SRv6 with ODN attached - not supported?: My understanding in this release L2VPN over SRv6 does not support attaching SRv6-TE policy or ODN template. But I am able to provision an L2VPN over SRv6 with ODN template attached. Both Dry-Run and Commit went through. Can you confirm if this is supported. If it is not, should there be validation and fail the Dry-run or Commit?Thanks. | Payload attached. Hi Crystal,Will look into this and get back to you.Thanks,RegiHi Crystal,SRv6 is not supported with ODN or TE policy. If you do see an issue with validation. Please go ahead and file a CDETs. I'll go ahead and close this ticket, since the query has been answered.Thanks,Regi |
Devices in out of sync state when there is no changes in config in EC2 setup: Devices are in out of sync state in NSO even when there is no config changes. Issue seen in EC2 setup. Instances are powered off on daily basis and powered on next day for testing. Once all the instances are up when validating the device status found devices are in out of sync state.EC2 Setup detail will be shared in person | Had a call with customer. Investigating issue.Enabled trace logging on NSO as shown below to obtain additional data.admin@ncs% show devices global-settings tracetrace false;admin@ncs% set devices global-settings trace rawadmin@ncs% commiCommit complete.admin@ncs% show devices global-settings tracetrace raw;Created Internal TSDN ticket - Raised CDETS with IOSXR team - Awaiting information from IOSXR team. |
NSO LSA standalone with services converting to NSO LSA HA support: Hi team,Clarification please.If converting NSO standalone/NSO LSA standalone (with services and Devices) to NSO HA/NSO LSA HA is supported scenario (or) is it mandatory to setup HA first before any service creation/Device addition.Kindly suggest. | Hello,It is recommended to first setup HA before adding any devices/services.The ansible script has this usecase (install LSA-HA) as one of the options.Regarding support, We support the following casesStandalone -> Standalone + HA (supported)Standalone -> LSA (supported)LSA -> LSA + HA (supported)Please let us know of this helps.Regards,Janaki DuggiralaAbe helped Ajitha with the setup. |
Route-policy name and the attached parent route-policy names are different: Route-policy name and the attached parent route-policy names are different in EVPN-TREE provisioning.route-policy SET_COLOR_EVPN_MP_service_RP-L2NM-ODN-xrd-1-350 if rd in (100.100.100.112:350) then set extcommunity color COLOR_350 endifend-policy!route-policy bgp_in apply SET_COLORv4_service_RP-L2NM-ODN-xrd-1-350 apply SET_COLORv4_service_RP-L2NM-ODN-xrd-1-450 passend-policy | Hi Ragesh,From what you have described, it seems like a bug that was fixed for M5. You can find the CDETs here : Did you face any device errors when pushing this service?Thanks,Isaac KimHi Issac,Yes, Since the route-policy name ; attched parent route-policy names are different it's not able to attach the parent route-policy to the bgp neighbor.Attached the sreenshotHi Isaac,Thanks for letting us know about the cdets, but from the cdets below, there was a reference to - i'm unable to view the ticket. Could you please allow the access for read only to get more information?Thanks and regards,-QuyHi Quy, I have tried to share the ticket with you.Also, please let me know if you are still facing this issue on M5+ build.Thanks,Isaac KimPlease open new JSD if encountered again. Thanks! |
NSO LSA L3 HA stuck after Switchover: NSO LSA L3 HA not responding to any configuration or request after switchover from LHS to RHS. Kindly help troubleshoot furtherSetup:NSO LSA L3 HA - CFS - 192.168.5.67 , 192.168.6.67 VIP 3.3.3.7 - nsoaz1/Cnc@1234NSO LSA L3 HA - RFS1 - 192.168.5.68 , 192.168.6.68 VIP 4.4.4.7 - nsoaz1/Cnc@1234NSO LSA L3 HA - RFS2 - 192.168.5.69 , 192.168.6.69 VIP 5.5.5.7 - nsoaz1/Cnc@1234 | RFS-1 HA setup was not completely working due to token-mismatch. Updated ncs.crypto file on both nodes. |
RPC error towards hfayerst-esxi: operation_failed: Exception in callback: Circuit [UID = fcb95d75-4221-3583-8c15-02c4f2a16d76] Provisioning failed. PCE Find Channel Failed[PCE-PR00018] - Optical validation failed: ZONE_RED worse than ZONE_GREEN: nso552/Public1234!Local Installation: /home/nso552/.0.0 | For now close this issue, irrelevant The error is from ONC, advising something is wrong with the selected end-points.I will close the casePlease check with ONC. |
L2VPN-ELAN provisioning throws an error message.: L2VPN-ELAN provisioning throws an error message, please let me know is there any pre-requisite for provisioning the ELAN service. Screenshot attached. | Hi RageshCan you please let us know which platform are you using?Thankshi Nikhil, i'm replying for Ragesh as he is in IST zone. We were using cisco-iosxr-nc-7.5 (Version: 7.5.2.19I). Hope this is what you are looking for.RegardsHi Ragesh ,Looking at the error it clearly looks like a payload issue.Did you try payloads from :Please try using correct payloads and there is no pre-requisite as such from device. bridge-domain must be defined in payload.Thanks,PriyankaHi Priyanka,Tried after adding the bridge-domain payload, looks the XRV9K platform is not supported for bridge-domain config. Screenshot attachedXRv9K does not support VPLS bridge domain. Please try ASR9Kv.Thanks,RegiHi Regi,ASR9K is the physical device right, Do we have any virtual platform for ASR9K?You can use ASR9Kv.Thanks.Hi Nikhil,Could you please share the path to download the ASR9Kv image for the testing.Hi RageshPlease refer the below wiki page for ASR9Kv image:Hi RageshPlease let us know if anything else is needed or we may close the ticket.Thanks,NikhilClosing the ticket as the required information has been provided.Hi Nikhil,Please close the ticket. |
ESI value are not applied to the devices: ESI value that specified in the payload is not flushed to the devices | Hi YevgenyWe couldn't reproduce the issue on our system. We see the esi-value being propagated to the device.Can you please provide us with the system details where you are facing this issue.Thanks.NSO UI: ============= admin/Public12345!Devices:=============Access to devices: ssh: 10.56.58.145 nso5721/Public1234!From that VM SSH: admin/Public1234!192.168.122.204 PE-A192.168.122.143 PE-B192.168.122.240 PE-CService For example=============Hi YevgeniWe checked your setup and could see that there are multiple services pushing the esi-value on the same interface(PE-B). Below are those services and esi-values:L2VPN_NM-PBB-CUSTOM-SRTE-ODN-430 (esi-value 00.01.00.ac.ce.55.00.04.30)L2VPN_NM-ELAN-MH-340 (esi-value 00.01.00.ac.ce.77.00.0a.11)L2VPN_NM-PBB-CUSTOM-390 (esi-value 00.01.00.ac.ce.55.00.03.90)L2VPN_NM-ETREE-MH-380 (esi-value 00.01.00.ac.ce.55.00.0a.00)The device PE-B is having the esi-value 0 00.01.00.ac.ce.55.00.04.30 present which is posted through the L2VPN_NM-PBB-CUSTOM-SRTE-ODN-430 service.These multiple services are shifting the esi-value on the device and hence you are not able to see the required value.Thanks,NikhilPlease clean up extra services and re-deploy the service you want to useThis is not 100% accurate. Each service is using its own dedicated sub interface Hi Yevgeny,You mentioned XR supported sub-ifs for ethernet-segments, but was not able to get passed the following error:<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"><pre>RP/0/RSP0/CPU0:PE2(config-evpn-ac-es)#show configuration failedWed Mar 23 23:49:43.368 UTC!! 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.evpn interface HundredGigE0/0/0/7.200!!% Invalid argument: Subinterface not supported: mainports only ethernet-segment!!% Invalid argument: Cannot find Ethernet-Segment by name identifier type 0 00.01.00.ac.ce.55.00.0a.01!!% Invalid argument: Cannot find Ethernet-Segment by name ! ! interface HundredGigE0/0/0/7.300!!% Invalid argument: Subinterface not supported: mainports only ethernet-segment!!% Invalid argument: Cannot find Ethernet-Segment by name identifier type 0 00.01.00.ac.ce.55.00.0a.01!!% Invalid argument: Cannot find Ethernet-Segment by name ! !!end</pre></div></div>Can you please provide sample device configuration on how to create "evpn / interface / ethernet-segment" for sub-ifs?Thanks,RegiI did not know that . !!% Invalid argument: Subinterface not supported: mainports only ethernet-segmentThis means that we dont have an issue Closing ticket, since submitters request is not supported by XR device |
ELAN + ODN not working: When adding te-mapping/odn to ELAN we hit this error: <errors xmlns="urn:ietf:params:xml:ns:yang:ietf-restconf"><error><error-type>application</error-type><error-tag>malformed-message</error-tag><error-path></error-path><error-message>RPC error towards PE-A: operation_failed: for ns1:routing-policy/ns1:route-policies/ns1:route-policy/ns1:rpl-route-policy: 'YANG framework' detected the 'fatal' condition 'Operation failed'</error-message></error></errors> | added the config we used we notice that if we use "route-type" in the policy, we are able to attach it to the service - is it possible rd policies is not supported for ELAN?It should be support. The service should be sending the following for the route-policy for your payload"route-policy SET_COLOR_EVPN_MP_service_L2VPN_NM-ELAN-SRTE-ODN-PE-A-290n if rd in (100.100.100.7:1) thenrn set extcommunity color COLOR_250rn endifrnnnend-policy"Can you please let me know which NED, device version and device platform you are using?we use NED cisco-iosxr-nc-7.5:cisco-iosxr-nc-7.5. If you want you can look on the server (admin/Public1234!)Thanks, but NSO won't show the device version and device platform. I'm assuming the device version is 7.5? Can you double check as well as the platform?Also, NSO GUI seems to slow. Can I get the credentials for ssh to use CLI?Hi Idan,.I was able to reproduce the issue. This seems to be a bug. Please go ahead and file a CDETs.Thanks,RegiHi Idan,Just a reminder but please file a CDETs and close the case.Thanks,Regihi, how do I close this case? Idan filed CDETs: Issue was fixed and released as part of TSDN 4.0 M3Hi,As per meeting, there seems to be more issues other than the original error. I have gone through created an internal ticket at well as updated the CDETs.Thanks,RegiFixed as part of M5 |
Issue on getSchema API for L2VPN service: Issue on getSchema API for L2VPN service. In CNC provisioning UI for some fields after a successful set_value calls the subsequent get_schema API call does not bring newly added value to the fields. The following are examples of the fields with the path "/l2vpn-ntw:l2vpn-ntw/vpn-services/vpn-service{aaa}/vpn-nodes/vpn-node{xrv9k-22}/te-service-mapping/te-mapping/sr-policy/policy-type" "/l2vpn-ntw:l2vpn-ntw/vpn-services/vpn-service{aaa}/vpn-nodes/vpn-node{xrv9k-22}/te-service-mapping/te-mapping/sr-policy/fallback" "/l2vpn-ntw:l2vpn-ntw/vpn-services/vpn-service{aaa}/vpn-nodes/vpn-node{xrv9k-22}/te-service-mapping/te-mapping/odn/attach-point/parent-rr-route-policy" | Hi Demeke,Please provide us with the set_value and get_schema request where you are seeing the issue.Also, please provide with the CNC setup details.Thanks,NikhilHi Demeke,This issue is happening because the get_schema call is having insert_values = false. This is the reason the values are not returned in the get_schema response.I tried the same call with insert_values = true and was able to see the values being returned in the response.Thanks,NikhilHi,The suggestion given to use get_elem API is not working for our use case our Prov-UI editor is relay on the get_schema api. And the workaround is not helping.This is the original ticket related to this issueThanks,Demeke.Hi Demeke,The original ticket related to this issue is fixed The below RT raised for the original issue with NSO team has been fixed:The change will be included in thebelow and later versions:nso-5.5.9 (31-Jan-2023)nso-5.6.11nso-5.7.9 (24-Jan-2023)nso-5.8.7nso-6.0.1.1nso-6.0.2 (17-Jan-2023)nso-6.1 (13-Apr-2023)Thanks,NikhilBelow Original ticket related to this issue was fixedHence using insert_value=true would give the required response now. |
Provision Slice Service Issue: Hi,While provisioning a slice service i'm getting a validation error.Error Response:------------------{ "ietf-restconf:errors": { "error": [ { "error-type": "application", "error-tag": "malformed-message", "error-path": "/ietf-network-slice-service:network-slice-services/slice-service", "error-message": "/network-slice-services/slice-service{Dedic-500}: Python cb_validate error. STATUS_CODE: TSDN-IETF-NSS-400REASON: NoneCATEGORY: NoneSEVERITY: NoneContext [name = Status Code, message = Missing IETF NSS status code mapping state = {'Keypath': '/ietf-nss:network-slice-services/slice-service{Dedic-500}'}]" } ] }}Attaching the input payload also. | Hi Magesh,Please check if the bootstrap data is loaded correctly.IETF-NSS-status-codes.xmlRegards,Nishad Subair.Hi Nishad,I tried the steps for loading the xml as mentioned in the link,After that i restarted the ncs.But still facing the same issue |
Unable to compile after updating the yang model: Hi,I have added descriptions and added tailf:hidden to l2-vpn yang model to test couple of scenarios. After changing the yang and when I tried to do "make clean all" to compile my changes from src folder. It resulted in below error.ubuntudoc@ubuntudoc:~/nso-5.7.6-tsdn-5.0.0-M4/tsdn/example-packages/ietf-l2vpn-nm/src$ make clean allmake: *** No rule to make target 'clean'. Stop. Kindly let me know. | Hello, I would recommend checking the Makefile underpackages/ietf-l2vpn-nm/src for the clean target:It should look like below:clean: rm -rf $(DIRS)Please confirm to us how the Makefile looks.Regards,Janaki DuggiralaHi Naveen,Which build have you been using to change the yang files?We do not include make files in our release build.ThanksSahithiHi Sahiti,The steps which I did is as follows,1. Downloaded 2. tar -xvf nso-5.7.6-tsdn-5.0.0-M4.tar.gz3. tar -xvf nso-5.7.6-tsdn-5.0.0-M4/tsdn/example-packages/ncs-5.7.6-ietf-l2vpn-nm-EXAMPLE-5.0.0.tar.gz4. Updated yang file in nso-5.7.6-tsdn-5.0.0-M4/tsdn/example-packages/ietf-l2vpn-nm/src/yang/cisco-l2vpn-ntw.yang5. make clean all Yes , I don't see make file in the location.Kindly let me knowHi Naveen,You need to have build with source code to compile the changes.The build with source code is present in our release wiki. Please download that and compile them.ThanksSahithiReceived confirmation from customer that issue is resolved. Closing ticket.Customer was provided with following info:"""You need to have build with source code to compile the changes.The build with source code is present in our release wiki.Please download that and compile them."""Customer confirmed that issue is resolved. Closing ticket. |
L3VPN MVPN static tree-sid policy creation failing from CNC (prov-ui): L3VPN MVPN static tree-sid policy creation failing from CNC -UI giving these errors at different time please find attached Payload json file | Hello, Can you please let us know:If there is a BGP device already present?If yes, what is BGP AS number?Regards,Janaki DuggiralaHi Janaki,The BGP AS number in our devices are 100.router bgp 100Thanks,NaveenHello Naveen, in that case we recommend the payload should be changed from 1 to 100 for the local-as.please let us know if this helps.Updated the Payload local-as form 1 to 100 its still throwing this error Please provide setup info.NSO setup : nso/Vtsisco@123!Hello, we restarted NSO on your VM using command below:nso@nso-virtual-machine:~$ sudo service ncs restartThe error is no longer being seen.Please proceed with your testing.Regards,Janaki Duggiralawhat is the reason for the error ? and do we need to restart NSO each time ?thanks Janaki , the previous error not coming now be device Sync error are coming frequently even after doing check-sync what is the reason for the error ? the python VM seemed to be not running properly.and do we need to restart NSO each time ?if you see this specific error, we would recommend restarting the NSOWith the sync-from issue, can you check device connectivity on your end? is the device info on NSO correct? you can perform fetch-host-keys again as well..Hello, Please confirm if all issues are addressed and if we may close this ticket?Regards,Janaki DuggiralaClosing ticket since no further response has been received from customer.To assist with this issue,we restarted NSO on the VM using command below: nso@nso-virtual-machine:~$ sudo service ncs restart |
Error deploy l3vpn route policy: on our NSO ( nso576/Public1234!)when we try to associate l3vpn-routing-policy to a service, we get following error: <errors xmlns="urn:ietf:params:xml:ns:yang:ietf-restconf"> <error> <error-type>application</error-type> <error-tag>operation-failed</error-tag> <error-path></error-path> <error-message>External error in the NED implementation for device PE-A: command: endif : ^ % Invalid input detected at '^' marker. [ route-policy L3VPN_NM-SRTE-ODN-PE-A-40 / ]</error-message> </error></errors>ned version is cli 7.42attach the payload we use. | Hi Idan,We are able to create the service with the payload you provided.Please provide the restconf request sent from your side , so that it will be helpful in debugging the issue.Regards,Nishad Subair.What do you mean by "restconf request sent from your side", how is it different from the attached payload?Were you able to provision this service using our NSO? (attached below)If not, can you check if our NSO is configured correctly or missing anything?Hi Shlomi,The route-policy is not configured correctly. Please refer the following -In the route-policy, you are using multicast-action which should only be used for mvpn use-case. Please instead use Bgp-actions/set-ext-community. Please see sample payload for more details -> sample payload L3NM-RP.xmlThanks And Regards,Nishad Subair.Hi Nishad,After adapting payload as instructed, services are successfully deployed.Thanks.Hi Shlomi,Thank you for the update.Regards,Nishad Subair. |
IPv6 route target in L3VPN service is not pushed to device: I am using NSO 6.1 TSDN 5.0.0 M5+Use CNC create an L3 slice with advance settings. 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 automatically created. The service has both IPv4 and IPv6 address family under "active-vpn-instance-profiles" -> "vpn-instance-profile". But on device the router target is only added under IPv4 address family but not IPv6. | |
Need info on migration support from NSO 6.1 Engineering build to upcoming new NSO builds: Due to the below Jira ticket, we are blocked for ELAN/ ETREE., so, for SH scale testing, we have to scale up all services types like l2vpn p2p, evpn., l3vpn, elan, etree.just wanted to know if we scale up l2vpn p2p or EVPN, once new build comes, does the migration support available to upgrade to new build with scale services? | Hi Arun,It would depend on the yang model changes required by the ShowStopper/Blocker tickets created. If there is change which would be backwards incompatible, migration between milestones would not be possible.With next release, we do not see any yang changes with L2 or L3. We do have few backwards incompatible changes with CS SR CFP though.Hope this answers your query.ThanksSahithi |
Converting an existing L3 to L2 slice service: Hi,While updating a slice service from L3 to L2, i'm getting the error in NSO UI itself.Could you please look into this | Hello,Can we please get additional information for troubleshooting such as1. Payload used2. Steps to Reproduce.3. Setup Info.Regards,Janaki DuggiralaHi Janaki,As per our quick discussion, hope you have taken the necessary information.Will wait for your response.Thanks for your time.MageshHello, after internal discussions, we recommend filing a CDETS for this issue for further investigation. Hi Janaki,Filled the cdets CSCwd90968 for this issue.Thanks,NaveenReceived CDETS, will investigate this use-case with internal teams.RT Raised with platform for messaging change: Tail-f TAC #50004Block on RT-50025Hi Magesh,We've added a workaround as part of M6 Patch Release. We currently do not support update from L2 -> L3 or vice versa, but you should get error message now when you try to update the slice in this manner.Thanks,RegiFix released in M6 Patch Release |
cant configure dual stack ip address : cant configure dual-stack ip address under vpn-instance-profile, although in RFC it specify it is possible (see attached). | Hi Idan,Dual-stack vpn-instance-profile is not supported as of now. Please define for each of ipv4 and ipv6.Regards,Nishad Subairthank you. please update if expected in next release. Hi Idan,Sure. We will update if we plan to include in later releases.Thank you.Nishad Subair |
which NSO build have MVPN modal support ?: we are waiting for the MVPN modal support form NSO on CNC prov-ui Integration. which version is this available ? | TSDN 5.0 M3 realease supports MVPN feature.thank you for confirming. |
python class not loading on NCS 6.0: Im seeing failure with following error in tm-tc package. Python cb_nano_create error. Dynamic class 'tm_tc_multi_vendors.IosXR' not loaded in NSO.However, there are no errors in package status. Show packages package oper-status shows that all packages are successfully installed and python code has that class ( IosXR ) . Also, same code worked until 5.7.6. Setup details - nsorfs@172.20.200.71 ( Cwork123! ) | Hi Moksha,Can you try modifying the package meta data for internal and the multi vendor as below for the Python VM<python-package> <vm-name>-----<del>tm tc internal name</del>-</vm-name> <callpoint-model>threading</callpoint-model></python-package>The suggestion worked for the given error. |
NSO actions for Network Slice: From the "TSDN 5.0.0 - M4 - IETF Network Slice Services (EXAMPLE FP)" wiki. We do not see the following 3 as supported. Can you confirm if these are supported for network slicing? 1. Check-Sync 2. Re-deploy Dry Run 3. Reactive Re-deployHere is the TSDN wiki link: | Hi CrystalYes, the actions listed above are supported for network slicing.Thanks,NikhilProvided required info to the userThanks Nikhil,Can we update the wiki to include these 3 as well? Since this is a new service, our test plan uses this as a reference to create test cases. Thanks.-CrystalHi Crystal,Wiki has been updated with these actions.Thanks,Nikhil |
NSO-LSA:Need to know, what shall be the state in CNC, when CFS is Up and RFS(only one RFS installed) is down: 1) In NSO LSA setup, If my CFS VM is up and running fine and RFS which is only one configured with CFS is Down. 2) Now in CNC CFS will show degraded or as CFS is still up and running and reachable from CNC VM, CFS will show still up in above situation ?3) If L2vpn service is already created when both CFS and RFS is up and running, Now if I bring down the RFS and try to modify the service, then in this case, If CFS is showing as degrade/Green in CNC, then my expectation is that Service modification must fail. So my Understanding is correct ?. Error message will be sent to CNC, mentioning that RFS is down ? | Hi Sampath,1. For the first question, in a LSA setup where CFS is up and the RFS is down, CFS will still show as up and running.2. For the second question, you understanding is correct. If there was a service created when both CFS and RFS were up and you try to modify the service when RFS is down, you'll get a failed to connect to rfs node error message. Ex: "Aborted: Python cb_post_modification error. Unknown error (56): Failed to connect to device rfs-node-1: connection refused"Let us know if you need anything else or we may close this ticket.ThanksThanks Nikhil for Quick response, No Questions from my sideClosing ticket as information has been provided. |
Augment Existing IETF L2vpn YANG Model: We have a UI validation Framework. For the framework to be able to provide custom validations we need to add the following annotation to policy field in L2vpn model -ietf-l2vpn-ntw:vpn-servicevpn-nodesvpn-node0te-service-mappingte-mappingsr-policypolicy tailf:meta-data "ui-data-validation" { tailf:meta-value "leaf-validation"; }Is there a way to change the existing l2vpn model for the next NSO CFP build? | Hi Mukul,Here's an example for L3, you can leverage this for L2 as well. You need to create a separate yang file for annotations. I have attached test-ann.yang as an example on how to create annotations.<sup>Also keep in mind that just having the annotations yang file is not enough the L3 package in my example would need to be recompiled, but we have to specify the annotations yang file when recompiling:</sup><sup></sup><sup>Thanks,</sup><sup>Regi</sup>Hi,Thank you. To start with I copied the IETF-L2VPN package and unzipped it. I got the following files -ubuntudoc@ubuntudoc:~/temp$ tar -xvf ncs-5.7.2.1-ietf-l2vpn-nm-EXAMPLE-4.0.0.tar.gz ietf-l2vpn-nm/ietf-l2vpn-nm/CHANGESietf-l2vpn-nm/README.mdietf-l2vpn-nm/package-meta-data.xmlietf-l2vpn-nm/python/ietf-l2vpn-nm/python/ietf_l2vpn_nm/ietf-l2vpn-nm/python/ietf_l2vpn_nm/ietf_l2vpn_nm_actions.pyietf-l2vpn-nm/python/ietf_l2vpn_nm/ietf_l2vpn_nm_nano_plan.pyietf-l2vpn-nm/python/ietf_l2vpn_nm/ietf_l2vpn_nm_y1731.pyietf-l2vpn-nm/python/ietf_l2vpn_nm/main.pyietf-l2vpn-nm/python/ietf_l2vpn_nm/utils.pyietf-l2vpn-nm/src/ietf-l2vpn-nm/src/yang/ietf-l2vpn-nm/src/yang/ietf-ethertypes@2019-03-04.yangietf-l2vpn-nm/src/yang/ietf-inet-types@2010-09-24.yangietf-l2vpn-nm/src/yang/ietf-l2vpn-ntw-cisco-augmentations.yangietf-l2vpn-nm/src/yang/ietf-l2vpn-ntw-deviations.yangietf-l2vpn-nm/src/yang/ietf-l2vpn-ntw-nano-services.yangietf-l2vpn-nm/src/yang/ietf-l2vpn-ntw.yangietf-l2vpn-nm/src/yang/ietf-packet-fields@2019-03-04.yangietf-l2vpn-nm/src/yang/ietf-routing-types@2017-02-19.yangietf-l2vpn-nm/src/yang/ietf-vpn-common-oper-status-aa-ext.yangietf-l2vpn-nm/src/yang/ietf-vpn-common.yangietf-l2vpn-nm/src/java/ietf-l2vpn-nm/src/java/src/ietf-l2vpn-nm/templates/ietf-l2vpn-nm/templates/ietf-l2nm-l2vpn-evpn-mp-template.xmlietf-l2vpn-nm/templates/ietf-l2nm-l2vpn-template.xmlietf-l2vpn-nm/templates/ietf-l2nm-y1731-l2vpn-y1731-template.xmlietf-l2vpn-nm/load-dir/ietf-l2vpn-nm/load-dir/ietf-l2vpn-ntw-cisco-augmentations.fxsietf-l2vpn-nm/load-dir/ietf-ethertypes@2019-03-04.fxsietf-l2vpn-nm/load-dir/ietf-routing-types@2017-02-19.fxsietf-l2vpn-nm/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/ietf-packet-fields@2019-03-04.fxsietf-l2vpn-nm/load-dir/ietf-inet-types@2010-09-24.fxsietf-l2vpn-nm/build-meta-data.xmlI created a ietf-l2vpn-nm/src/yang/ui-validation.yang with following contents (changing from the YANG you had provided)module ui-validation { yang-version 1.1; namespace "urn:ietf:params:xml:ns:yang:ui-validation"; prefix ui-validation; import tailf-common { prefix tailf; } import ietf-l2vpn-ntw { prefix ietf-l2vpn-ntw; } revision 2022-03-14 { description "Initial revision."; } // annotate a single path tailf:annotate "/ietf-l2vpn-ntw:l2vpn-ntw/ietf-l2vpn-ntw:vpn-services/ietf-l2vpn-ntw:vpn-service/ietf-l2vpn-ntw:vpn-nodes/ietf-l2vpn-ntw:vpn-node/ietf-l2vpn-ntw:te-service-mapping/ietf-l2vpn-ntw:te-mapping/ietf-l2vpn-ntw:sr-policy/ietf-l2vpn-ntw:policy" { tailf:meta-data "ui-data-validation" { tailf:meta-value "leaf-validation"; } }}1. I'm not sure how to construct the whole path?2. How do I recompile this package back?ubuntudoc@ubuntudoc:~/temp$ ncsc --annotate ietf-l2vpn-nm/src/yang/ui-validation.yangncsc: Try 'ncsc -h' for help and more informationHi Mukul,I've update the ticket with the makefile we use for `ietf-l2vpn-ntw` as well as updated it to include the annotation yang file you have ( tried to match your directory structure ).If you look in the Makefile you can see that I have added:<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"><pre>--annotate ./yang/ui-validation.yang</pre></div></div>Now you just have to run "make clean all" to recompile the package.Thanks,RegiOne more thing your xpath is incorrect. Look at the xpath for "sr-policy" in "ietf-l2vpn-ntw-deviations.yang" as an exampleThanks. I updated the yang path to -/l2vpn-ntw:l2vpn-ntw/l2vpn-ntw:vpn-services/l2vpn-ntw:vpn-service/l2vpn-ntw:vpn-nodes/l2vpn-ntw:vpn-node/l2vpn-ntw:te-service-mapping/l2vpn-ntw:te-mapping/l2vpn-ntw:te/l2vpn-ntw:sr-policy/l2vpn-ntw:sr-policy/l2vpn-ntw:policyfrom the ietf-l2vpn-ntw-deviations.yangI placed your MakeFile under src/ and ran "make clean all" ; It looks like a lot of packages were not found -ubuntudoc@ubuntudoc:~/temp/ietf-l2vpn-nm/src$ make clean allrm -rf ../load-dir java/src//mkdir -p ../load-dirmkdir -p java/src///opt/ncs/current/bin/ncsc --annotate ./yang/ui-validation.yang --deviation ./yang/ietf-l2vpn-ntw-deviations.yang --fail-on-warnings `ls ietf-l2vpn-ntw-cisco-augmentations-ann.yang > /dev/null 2>;1 ;; echo "-a ietf-l2vpn-ntw-cisco-augmentations-ann.yang"` --yangpath ./yang --yangpath ../../cisco-flat-L2vpn-fp/src/yang --yangpath ../../custom-template-utils/src/yang --yangpath ../../core-fp-common/src/yang --yangpath ../../resource-manager/src/yang --yangpath ../../cisco-tsdn-core-fp-common/src/yang --yangpath ../../lsa-utils/src/yang -c -o ../load-dir/ietf-l2vpn-ntw-cisco-augmentations.fxs yang/ietf-l2vpn-ntw-cisco-augmentations.yang./yang/ietf-l2vpn-ntw-deviations.yang:10: error: module 'lsa-utils' not found./yang/ietf-l2vpn-ntw-deviations.yang:163: error: the node 'lsa' from module 'lsa-utils' (in node 'devices' from 'tailf-ncs') is not found./yang/ietf-l2vpn-ntw-deviations.yang:167: error: The XPath expression references an undefined node: the node 'lsa' from module 'lsa-utils' (in node 'devices' from 'tailf-ncs') is not found./yang/ietf-l2vpn-ntw-deviations.yang:167: error: The XPath expression references an undefined node: the node 'lsa' from module 'lsa-utils' (in node 'devices' from 'tailf-ncs') is not found./yang/ietf-l2vpn-ntw-deviations.yang:339: error: The XPath expression references an undefined node: the node 'lsa' from module 'lsa-utils' (in node 'devices' from 'tailf-ncs') is not found./yang/ietf-l2vpn-ntw-deviations.yang:339: error: The XPath expression references an undefined node: the node 'lsa' from module 'lsa-utils' (in node 'devices' from 'tailf-ncs') is not found./yang/ietf-l2vpn-ntw.yang:7: error: module 'custom-template-hook' not found./yang/ietf-l2vpn-ntw.yang:11: error: module 'cisco-flat-L2vpn-fp' not found./yang/ietf-l2vpn-ntw.yang:12: error: module 'cisco-tsdn-core-fp-common' not found./yang/ietf-l2vpn-ntw.yang:13: error: module 'lsa-utils' not found./yang/ietf-l2vpn-ntw.yang:40: error: module 'resource-allocator' not found./yang/ietf-l2vpn-ntw.yang:43: error: module 'id-allocator' not found./yang/ietf-l2vpn-ntw.yang:1277: error: the node 'resource-pools' from module 'resource-allocator' is not found./yang/ietf-l2vpn-ntw.yang:1284: error: the node 'resource-pools' from module 'resource-allocator' is not found./yang/ietf-l2vpn-ntw.yang:1701: error: the node 'l2vpn-route-policy' from module 'cisco-flat-L2vpn-fp' is not found./yang/ietf-l2vpn-ntw.yang:2971: error: the node 'lsa' from module 'lsa-utils' (in node 'devices' from 'tailf-ncs') is not found./yang/ui-validation.yang:14: error: prefix 'l2vpn-ntw' not foundyang/ietf-l2vpn-ntw-cisco-augmentations.yang:8: error: module 'cisco-tsdn-core-fp-common' not foundyang/ietf-l2vpn-ntw-cisco-augmentations.yang:11: error: module 'lsa-utils' not foundyang/ietf-l2vpn-ntw-cisco-augmentations.yang:437: error: The XPath expression references an undefined node: the node 'lsa' from module 'lsa-utils' (in node 'devices' from 'tailf-ncs') is not foundyang/ietf-l2vpn-ntw-cisco-augmentations.yang:437: error: The XPath expression references an undefined node: the node 'lsa' from module 'lsa-utils' (in node 'devices' from 'tailf-ncs') is not foundyang/ietf-l2vpn-ntw-cisco-augmentations.yang:438: error: The XPath expression references an undefined node: the node 'lsa' from module 'lsa-utils' (in node 'devices' from 'tailf-ncs') is not foundyang/ietf-l2vpn-ntw-cisco-augmentations.yang:438: error: The XPath expression references an undefined node: the node 'lsa' from module 'lsa-utils' (in node 'devices' from 'tailf-ncs') is not foundyang/ietf-l2vpn-ntw-cisco-augmentations.yang:438: error: The XPath expression references an undefined node: the node 'lsa' from module 'lsa-utils' (in node 'devices' from 'tailf-ncs') is not foundyang/ietf-l2vpn-ntw-cisco-augmentations.yang:438: error: The XPath expression references an undefined node: the node 'lsa' from module 'lsa-utils' (in node 'devices' from 'tailf-ncs') is not foundyang/ietf-l2vpn-ntw-cisco-augmentations.yang:513: error: The XPath expression references an undefined node: the node 'lsa' from module 'lsa-utils' (in node 'devices' from 'tailf-ncs') is not foundyang/ietf-l2vpn-ntw-cisco-augmentations.yang:513: error: The XPath expression references an undefined node: the node 'lsa' from module 'lsa-utils' (in node 'devices' from 'tailf-ncs') is not foundmake: *** Error 1You do need to have the dependent packages as per the folowing structure:<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"><pre>packages cisco-aa-service-assurance cisco-cs-sr-te-cfp cisco-flat-L2vpn-fp cisco-flat-L2vpn-fp-internal cisco-flat-L2vpn-fp-internal-ned cisco-flat-L3vpn-fp cisco-flat-L3vpn-fp-internal cisco-flat-L3vpn-fp-internal-ned cisco-ios-cli-6.74 cisco-ios-cli-6.77 cisco-iosxr-cli-7.33 cisco-iosxr-cli-7.38 cisco-iosxr-nc-7.3 cisco-iosxr-nc-7.315 cisco-iosxr-nc-7.4 cisco-iosxr-nc-7.5 cisco-rsvp-te-fp cisco-rsvp-te-fp-internal-ned cisco-sr-te-cfp cisco-sr-te-cfp-internal cisco-sr-te-cfp-internal-ned cisco-tsdn-core-fp-common core-fp-common core-fp-common-ned core-fp-delete-tag-service core-fp-plan-notif-generator custom-template-utils custom-template-utils-ned flat-l2vpn-multi-vendors flat-l3vpn-multi-vendors ietf-l2vpn-nm ietf-l3vpn-nm ietf-network-slice ietf-te-fp lsa-utils lsa-utils-ned resource-manager rsvp-te-multi-vendors sr-te-multi-vendors</pre></div></div>Make sure to untar them if they are tar'dThanks again. These errors are resolved but I still get this one - (although I double checked and yang path is correct)ubuntudoc@ubuntudoc:~/temp/ietf-l2vpn-nm/src$ make clean allrm -rf ../load-dir java/src//mkdir -p ../load-dirmkdir -p java/src///opt/ncs/current/bin/ncsc --annotate ./yang/ui-validation.yang --deviation ./yang/ietf-l2vpn-ntw-deviations.yang --fail-on-warnings `ls ietf-l2vpn-ntw-cisco-augmentations-ann.yang > /dev/null 2>;1 ;; echo "-a ietf-l2vpn-ntw-cisco-augmentations-ann.yang"` --yangpath ./yang --yangpath ../../cisco-flat-L2vpn-fp/src/yang --yangpath ../../custom-template-utils/src/yang --yangpath ../../core-fp-common/src/yang --yangpath ../../resource-manager/src/yang --yangpath ../../cisco-tsdn-core-fp-common/src/yang --yangpath ../../lsa-utils/src/yang -c -o ../load-dir/ietf-l2vpn-ntw-cisco-augmentations.fxs yang/ietf-l2vpn-ntw-cisco-augmentations.yang./yang/ui-validation.yang:14: error: bad argument value "l2vpn-ntw:l2vpn-ntw/l2vpn-ntw:vpn-services/l2vpn-ntw:vpn-service/l2vpn-ntw:vpn-nodes/l2vpn-ntw:vpn-node/l2vpn-ntw:te-service-mapping/l2vpn-ntw:te-mapping/l2vpn-ntw:te/l2vpn-ntw:sr-policy/l2vpn-ntw:sr-policy/l2vpn-ntw:policy", should be of type absolute-schema-nodeidmake: *** Error 1 Seems like you're missing the beginning forward slash in "l2vpn-ntw:l2vpn-ntw/l2vpn-ntw:vpn-services/l2vpn-ntw:vpn-service/l2vpn-ntw:vpn-nodes/l2vpn-ntw:vpn-node/l2vpn-ntw:te-service-mapping/l2vpn-ntw:te-mapping/l2vpn-ntw:te/l2vpn-ntw:sr-policy/l2vpn-ntw:sr-policy/l2vpn-ntw:policy"I did try the slash earlier too.. then it says path not found :ubuntudoc@ubuntudoc:~/temp/ietf-l2vpn-nm/src$ make clean allrm -rf ../load-dir java/src//mkdir -p ../load-dirmkdir -p java/src///opt/ncs/current/bin/ncsc --annotate ./yang/ui-validation.yang --deviation ./yang/ietf-l2vpn-ntw-deviations.yang --fail-on-warnings `ls ietf-l2vpn-ntw-cisco-augmentations-ann.yang > /dev/null 2>;1 ;; echo "-a ietf-l2vpn-ntw-cisco-augmentations-ann.yang"` --yangpath ./yang --yangpath ../../cisco-flat-L2vpn-fp/src/yang --yangpath ../../custom-template-utils/src/yang --yangpath ../../core-fp-common/src/yang --yangpath ../../resource-manager/src/yang --yangpath ../../cisco-tsdn-core-fp-common/src/yang --yangpath ../../lsa-utils/src/yang -c -o ../load-dir/ietf-l2vpn-ntw-cisco-augmentations.fxs yang/ietf-l2vpn-ntw-cisco-augmentations.yang./yang/ui-validation.yang:14: error: prefix 'l2vpn-ntw' not foundmake: *** Error 1ubuntudoc@ubuntudoc:~/temp/ietf-l2vpn-nm/src$ Another question is when this works ; what is the process to make sure these changes are available on an out of box installation of upcoming "TSDN 4.0.0 M5?" on NSO.looks like the import prefix is not matching with the prefix in the path. try this /ietf-l2vpn-ntw:l2vpn-ntw/ietf-l2vpn-ntw:vpn-services/ietf-l2vpn-ntw:vpn-service/ietf-l2vpn-ntw:vpn-nodes/ietf-l2vpn-ntw:vpn-node/ietf-l2vpn-ntw:te-service-mapping/ietf-l2vpn-ntw:te-mapping/ietf-l2vpn-ntw:sr-policy/ietf-l2vpn-ntw:policyBut, we really want to add this as a compiled package outside the service pacakge, is this not possible?Thank you Srini. Compilation works now. Please help regarding commit / packaging of this change so that its available on out of box installation. I'll meanwhile test this out.This works as expected. We need a way to commit this now.Closing this ticket as potential method to augment tailf extension seems to have been completed successfully by submitter.Lets please keep the ticket open as the issue is still not resolved and we're looking at how this can be packaged. |
CLI NED does not work at all: Result: config was not synced from devicefalseDevice PE-C does not advertise any known YANG modulesThis is CLI NED, how YANG model is related ???BTW, NETCONF NED works just fine | Hi YevgenyLooks like you are using a wrong port no. 830 works fine for NETCONF NEDs.Please use port no. 22 for CLI NEDs.Let us know if that resolves the error.Thanks.Clear, issue closed Closing the ticket as the issue is resolved |
Optics port not listed in CNC UI: NSO 5.5.3.2CNC 3.0.VXR devices are added with tag DWDM_optics in CNC.Checked the python is pointing to python 3, paramiko, xmllint is installed.netconf subscription is done for ONC.devices are using cisco-iosxr-nc-7.32:cisco-iosxr-nc-7.32While selecting devices for provisioning, we see devices, but not the ports under the devices. Probably, am i missing some config in the deviceserver: 10.195.165.190cnctest/Ovatest123@, for UI, CLI | HiRamakrishnan,Can you please elaborate what issue you're seeing?Optic port mappings with inter-layer-link are shown correctly in the attached screenshot.There were 2 sets of devices. i have deleted the devices like TOPLEFT etc long back. I am using the devices for TOPLEFT-VXR, TOPRIGHT-VXR etc. Not sure how Inter Layer link came up with old names. My issue is i dont see the ports for the devices (ending with VXR)The issue is in the inter-layer-link configuration. If you're still blocked, set up a webex session, I can walk you though it.Had a webex session with Ramakrishnan.Cleaned up old inter-layer-link config in his setup. The ONC controller configured in his NSO doesn't have Daigo optical simulation in the backend; hence, no optical configuration data was available for inter-layer-link config. Ramakrishnan will bring up Daigo simulation and reconnect offline. Mean while, close this case. |
TSDN-3.0.0-M3 - P2P Scenario Regression: Working with M2 with the same environment nso522/Public1234!Error running action for side-effect item /cisco-ron-cfp:ron/ron-ml-plan{TOPLEFT_BOTTOMLEFT_400_TR_P2P}/plan/component{ncs:self self}/state{ncs:init}: Python cb_action error. Error: STATUS_CODE: RON-506REASON: Fetch Optics failedCATEGORY: custom-actionSEVERITY: ERRORContext STATUS_CODE: RON-506REASON: Fetch Optics failedCATEGORY: custom-actionSEVERITY: ERRORContext [name = Fetch Optics Data error, message = ZR Fetch Optics data action returned error state = {'service': ListElement name=ron-ml tag=1842926444 keys={TOPLEFT_BOTTOMLEFT_400_TR_P2P}, 'endpoint': ListElement name=end-point tag=935030957 keys={P-BOTTOMLEFT}}] | Hi Yevgeny,Looks like this issue is old, can I close the ticket?Thanks,VanYevgeny has not responded and there is no outstanding RON support issue from his side that we know of, close the case. |
Creating device group for NACM for every device - need solution to add all devices for <ALL-ACCESS>: we have new changes pushed in for JWT and we have to follow steps as in below wiki. we have step to create device group where we have to provide devies . ##Create device groupncs_cli -u adminconfigureset devices device-group <ALL-ACCESS> device-name [ device-host-name1, device-host-name2]commit dry-runcommitfor FT, it is fine to give 10 to 15 devices. but for Scale, having 10k devices or 25k devices, it is not possible to provide every device hostname in this way. Even for 100 devices, this is going to be a pain pointdo we have any workaround to add all devices in single command?or should we follow up with CDETS?thanks,Arun.M.G | Hi Arun,There is no single command to create data on cdb. Simple shell script can be written to get the device names and set the device-group using the device-name.Hi sahithi,I got to know from CAT team that adding Individual devices to Device Group "ALL-ACCESS" is not needed .can you please confirm if we need to add all devices or not?if yes, can u pls provide if you have the script handy?Thanks,Arun.M.GHi Arun,Right, I believe rbac team defined the rule list for ALL-Access such that we would not require to add all devices.Thankssahithi |
jwt token authentication not working in NSO: Trying to enable JWT authentication in our NSO.Done the prerequisite like python3, requests package etc.Still the ncs-python-cisco-cfp-jwt-auth.log says authenticate:261 INFO: Exception jwt-auth: No module named 'requests'Previously cnctest was the user, now admin user also created for CW authentication. After requests module installed, does NSO need a restart.Kindly check the setup once. [ scale setup]172.20.63.189 cnctest/Ovatest123@admin/Ovatest123@ | Looks like requests module has not been installed on your VM. Please install and let me know if the error still existsrequests module was installed for python3 , in both cnctest, admin login. still the issue exists.Hi Rama,Please install requests module as root so it can be available system-wide.$ sudo su password for cnctest: # python3Python 3.8.15 (default, Dec 29 2022, 08:40:49) on linuxType "help", "copyright", "credits" or "license" for more information.>>> import requestsTraceback (most recent call last): File "<stdin>", line 1, in <module>ModuleNotFoundError: No module named 'requests'>>> thank you Van. It worked after installing requests as root user.Glad it works out for you, Rama. I'm going to close this ticket.Thanks! |
Steps to upload custom function pack in LSA setup: On standalone NSO, we can copy the custom fp to /var/opt/ncs/packages/ folder and restart ncs with package reload.For LSA setup, can I use the same steps to deploy custom FP?Do we need to do the same steps for CFS and RFS nodes? | Hi Crystal,What kind of custom fp are you referring to?For our TSDN custom function packs, you can follow the install guide as shown : You can follow the respective CFS/RFS install guide for the example packages. There should be example paths for our example fp as well.Let me know if you have any other questions.Thanks,Isaac KimHi Isaac,It is the fp we got from our CNC DEV, my-l2vpn, my-l3vpn and my-sr-policy. Should I deploy them for all CFS and RFS nodes?Just to confirm the steps in the link is:1. copy the tar.gz file to /opt/ncs/packages/2. create symbolic link from /opt/ncs/packages/ to /var/opt/ncs/packages/Thanks.-CrystalHi Crystal,Yes as the wiki states, "Copy required packages to /opt/ncs/packages/ directory and link them from /var/opt/ncs/packages (Note : sudo access needed)".I am not sure where you gotmy-l2vpn, my-l3vpn and my-sr-policy packages from. Your packages must be setup for LSA structure to work with LSA. For example, there should be a CFS facing service and RFS facing service. CFS facing service will create RFS facing service which will push config to device. So ideally, there would be two packages as you can see with our CFP and example FP packages, "external" (CFS) and "internal" (RFS) service packages.If you would like more information on how to convert a standalone package to LSA compatible packages, you can see the examples in NSO's documentation "nso_lsa-<NSO VERSION>.pdf" -> Chapter 2 : LSA Examples -> Rearchitecting an existing monolithic application into LSA. This pdf also has more information about the expected conditions and compatible service structures for LSA.Thanks,Isaac KimHi Isaac,I got the custom FPs from our CNC DEV which has been created by using the SDK as part of service extensibility support in this release. Can you share the pointer where we can download the NSO document. Will check the steps to convert a standalone package to LSA compatible packages.Thanks.-Crystal Hi Crystal,You can find all the documentation packaged with your NSO install. There is multiple types of documentation, web-based and pdf.For your local NSO install, you can find the pdfs here : <LOCAL NSO PATH>/doc/pdfFor your system NSO install, you can find the pdfs here : /opt/ncs/current/doc/pdfYou will also be able to find the entrypoint to the web docs under the "doc" folder in the above paths.Thanks,Isaac KimProvided instructions. Please feel free to reopen ticket if you have any additional questions. |
ELAN/ETREE support cases on SR & ODN: Hi- Do we support ELAN/ETREE for SR ; ODN?Any to Any - Plain, SR, ODNHub ; Spoke- Plain, SR, ODNCustom - Plain, SR, ODNM4 wiki page has the payload for ETREE, CUSTOM with ODN ; ELAN without SR ; ODN. So just want to confirm what are the possible cases supported for ELAN/ETREE with SR ; ODN. Please confirm the supported cases on NSO. | Only ODN is supported. M4 does have a bug when it comes to using route-policy with IPv4/IPv6 RD's. Currently, only evpn-route-type route-policies are working properly. This should be fixed by M5.Please refer to service device mappings to see what sort of configs you can push: Thanks,RegiHi Regi,Screenshots not loading for IOS-XR Device config mapping. please check.Hi Ragesh,I had re-uploaded the mappings. Please check now.Thanks,RegiHi Ragesh,Please let me know by EOD today if you have further issues; otherwise, I will go ahead and close this ticket.Thanks,Regi |
CFP throws error for RestConf request during Edit L2 P2P Slice: Create L2 Slice as Any To Any and edit to P2P. The NSO throws error saying bad path. Screenshot attached | As per the mail thread and confirmation from Sujay, For CNC 6.0, we will document this as unsupported behaviour. For CNC 7.0, we will check with device team on why this error is thrown during this transaction.As per the mail thread and confirmation from Sujay, For CNC 6.0, we will document this as unsupported behaviour. For CNC 7.0, we will check with device team on why this error is thrown during this transaction. |
Failed to re-deploy L3-NM service using Restconf APIs: Failed to re-deploy L3-NM service using Restconf APIsErrors: with payload: {}2024-01-16 06:26:24,417 ERROR c.c.u.c.u.NsoDataProvider Error in patchRestConf: {}org.springframework.web.client.HttpClientErrorException$NotFound: 404 Not Found: "{<EOL> "ietf-restconf:errors": {<EOL> "error": [<EOL> {<EOL> "error-type": "application",<EOL> "error-tag": "invalid-value",<EOL> "error-message": "uri keypath not found"<EOL> }<EOL> ]<EOL> }<EOL>}<EOL>" | Hi Dedeepya,With change in architecture, the northbound re-deploy is not a native action. It is an action created by CFP team. Please add cisco-l3vpn-ntw prefix for re-deploy.Thanks Sahithi. Issue is resolved after adding the prefix to re-deploy. |
L3VPN service creation is failing on LSA setup: Hi All,I am trying to create a L3VPN service on TSDN M4 LSA setup. Attaching the error screenshot.Set up details:NSO LSA:CFS: admin/Ovatest123@RFS-62: admin/Ovatest123@RFS-63: admin/Ovatest123@CNC Server: admin/Ovatest123@Thank you,Kanchan | Hello Kanchan,On your CFS node, I can see the following :<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"><pre class="code-java">admin@ncs% show devices device rfs-62 config devices deviceNo entries found.</pre></div></div>It seems like your rfs-62 config has not been synced with your CFS node.I would suggest to try a sync-from on your CFS node targeting your RFS node as suggested here :This may be a duplicate of Not a problem, just for reference.Let me know if this fixes your issue!Thanks,Isaac KimThanks Isaac for the quick response, that worked and fixed the issue.But I am wondering when I did the installation I made sure to sync RFS with CFS nodes. How come they are not in sync now. Is there a way CFS and RFS can be in sync without user manually perform the sync?Hmm that is weird. This LSA install procedure has been validate by our QA, so I assume that this issue wouldn't be a problem.But if we have already seen two of these issues via JSD from LSA install, that may indicate a problem or maybe we can add a validation after the sync step to make sure the RFS node is in-sync on CFS node.I will request our team to review the LSA CFS Install procedure again and I will update this ticket if we find anything.Thanks,Isaac KimI also remember I faced a similar issue on M2 or M3 and somebody from your team suggest to use "set devices device lower-nso-* out-of-sync-commit-behaviour accept " on CFS node.Can I still use this command to keep RFS and cFS nodes in sync?NSO has the following definition for "out-of-sync-commit-behaviour":<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"><pre class="code-java">3418 leaf out-of-sync-commit-behaviour {3419 type enumeration {3420 reject;3421 accept;3422 }3423 description3424 "Specifies the behaviour of a commit operation involving a3425 device that is out of sync with NCS. Value accept assumes that3426 the device's sync state is unknown and it is cleared on commit.3427 The behaviour is to reject such commits.";3428 }</pre></div></div>But the RFS sync step of the LSA CFS install procedure should resolve the device sync state as we do a sync-from operation on RFS node. I wouldn't recommend to change the "out-of-sync-commit-behaviour" for RFS node to accept.If you still have that email thread, would you be able post any explanation we gave for that recommendation?Thanks,Isaac KimHi Isaac,From CFS installation procedure, Under section: RFS OnBoarding Stepsstep: Onboard RFS device onto CFS device treeThis steps requires RFS to add "out-of-sync-commit-behaviour" as accept.So should I ignore this step?Hello Kanchan,Sorry that was my misunderstanding."out-of-sync-commit-behaviour" should be set to accept as part of our LSA install procedure.In the meantime, I will ask our QA team to review the LSA CFS install procedure again to see if there is any sync issue after full install procedure is completed.I will provide updates here.Thanks,Isaac KimHello Kanchan,I believe I have found the source of the issue.After LSA install, when you onboard new devices to RFS node, you must execute a sync-from on your CFS node.I reviewed the wiki, and this step is not defined as part of the procedure.I will add a note at the end of CFS install procedure to remind users of this sub-procedure when onboarding new devices.I will update this ticket once these documentation changes are complete.Let me know if this is a satisfactory solution.Thanks,Isaac KimHello Crystal and Kanchan,I have added the necessary information in a separate section in CFS install wiki here : Let me know if this is okay.Thanks,Isaac KimThanks Isaac for the quick help on this issue. Sure I will perform sync-from on CFS after onboarding the new devices.Great! In that case, I will mark this ticket as closed.If you have any remaining related questions, feel free to reopen this ticket.Thanks,Isaac KimDocumentation updated here : |
Need payload to create l3vpn service with Untagged interface: Hi NSO team,i am trying to create a L3vpn service with untagged interface ( on parent interface). but it is not allowed. NSO throws error as below. 1/1. .../type (value "vpn-common:untagged-int"): Connection encapsulation type must be vpn-common:dot1qattached snapshot. can you please provide valid payload to create l3vpn services on untagged interface? is there support?Thanks,Arun.M.G | After verifying with QA, it is noted that L3NM does not support vpn-common:untagged-intSince both L2 and L3 refer to some common models/options this option is not hidden.Hence a validation has been put in place that tells the user – Connection encapsulation type must be vpn-common:dot1q for L3NM Reached out to customer with above info, awaiting response/feedbackCustomer has received related information and approved. Closing ticket. |
cnc-custom metadata change for te-tunnel-id. : Path: "/l2vpn-ntw:l2vpn-ntw/vpn-services/vpn-service/vpn-nodes/vpn-node/te-service-mapping/te-mapping/te-tunnel-list/te-tunnel-id"tailf:meta-data "cnc-custom" { tailf:meta-value ' { "dependency": "[]", "type": "dropdown", "field": "te-tunnel-id-list", "pre-select": "none" }'; } | Hi Demeke,Please suggest on what should be the value for "leaf-validation" , true/false ?Thanks,Nishad Subair"leaf-validation" = falseHi Nishad, Please update the "leaf-validation" attribute for the ietf-te-service also currently it is "leaf-validation" is true please fix it as below."/l2vpn-ntw:l2vpn-ntw/vpn-services/vpn-service/vpn-nodes/vpn-node/te-service-mapping/te-mapping/te-tunnel-list/ietf-te-service"tailf:meta-data "cnc-custom" { tailf:meta-value ' { "dependency": "[]", "type": "dropdown", "field": "ietf-te-service-list", "leaf-validation": false, "pre-select": "none" }'; }Thanks,Demeke. |
Functional pack development: Hi team, Im trying to create new NSO functional pack. Using sample Customization ppt as reference.Need few clarifications.1. As per PPT we need to use 5.5.2.3. Our current NSO version is 5.7.x.x , please suggest if we need separate 5.5.2.3 version NSO for customizing 5.7.x.x NSO FP or document should be updated. 2. As per Slide 4 - The contents of the file are as shown below:$ ls nso-5.5.2.3-tsdn-internal-3.0.0-M5packages setup.mkActual NSO output doesnt have setup file, Please suggestnso249@nso249:~/nso-5.5.2.3-tsdn-internal-3.0.0-M5$ lsCHANGES example-packages init_dataconf fp_data.json installercore-fp-packages get_technical_support_data.sh local-install | Not sure, which PPT you're referring to. Please attach to this ticket.Thanks,RegiI have used PPT shared in Sorry , its Hi Ajitha,You would use NSO version which is supported by the release. For example, our latest milestone 4.0-M4 supports 5.7.2.1, so that's the version of NSO you would use. As for your other question about missing "setup.mk", it's because you picked up "internal-build" rather than the "source-code". Please refer to the release-notes to get the source-code of the release you want. Here's 4.0-M4 as reference: Please let me know if you have anymore questions.Thanks,RegiHi Ajitha,Please let me know by EOD today if you have further issues; otherwise, I will go ahead and close this ticket.Thanks,Regi |
CFS HA Failover: When CFS HA failover is performed, not able to bring back the nodes back to their's original states.Below are the output after performing back to original state actionsOn Master:admin@ncs> show high-availability statushigh-availability status mode masterhigh-availability status current-id masterhigh-availability status assigned-role masterhigh-availability status read-only-mode falseadmin@ncs>On Slave:admin@ncs> show high-availability statushigh-availability status mode nonehigh-availability status assigned-role slavehigh-availability status master-id masterhigh-availability status read-only-mode falsePlease also find the UI output enclosed herewith. | Hi Dinesh,Please share you setup info. We will take a look.Thanks,LinhHi Linh,NSO CFS Master: 10.194.57.204NSO CFS Slave: 10.194.57.45VIP: 10.194.57.58admin/Ovatest123@ - For all the nodes above.Thanks,DineshHi Dinesh,Last time Van, you and me debugged and we could not reproduce the issue. Have you try this issue again. Is it reproducable? If not, I would like to close this ticket.Thanks,LinhHi Linh,I'm testing a scenario that without any failover, My Master as master and Slave as slave,And the master goes down (i.e., unreachbale) and when it comes back by itself the following is found to be the it's status. admin@ncs> show high-availability statushigh-availability status mode nonehigh-availability status assigned-role slavehigh-availability status master-id standbyhigh-availability status read-only-mode falseadmin@ncs>Untill a ncs restart or vm reboot is performed, this doesn't turns into acting slave.NSO CFS Master: 10.194.57.204NSO CFS Slave: 10.194.57.45VIP: 10.194.57.58admin/Ovatest123@ - For all the nodes above.Thanks,DineshSteps to reproduce:1. Bring-up CFS HA with 5.7.2.1 #M52. Power shutdown the master VM manually3. Power-on the master VM back.4. Verify that the failover happened and the respective status for "show high-avialability status" found as expected in both the nodes.Please do let me know if any other information/details if required.Thanks,DineshServer Size is : SmallHi Dinesh ,I have increased the <tick-timeout>PT200S</tick-timeout> from 20 to 200 sec.Now it is working fine.Please try out and let us know if you still see issue.In your lab i tried failover ,as expected primary became standby and original standby took over as master .ThanksPriyankaHi Priyanka,Can you point out to the change where exactly?Is it a property of linux or NSO? Please confirmThanks,DineshI could able to see that the ncs.conf - ha section has been updated with your suggested variable.I performed powering-down the node whatever that is acting master.And turned it on. But still could not see that is coming up with proper expected state: Please check below.Output from Standy:admin@ncs> show high-availability statushigh-availability status mode nonehigh-availability status assigned-role slavehigh-availability status master-id masterhigh-availability status read-only-mode falseOutput from Master:admin@ncs> show high-availability statushigh-availability status mode masterhigh-availability status current-id masterhigh-availability status assigned-role masterhigh-availability status read-only-mode falseNOTE: Please be noted, that the failover I do is my manual power-off the master and then turn on the master.Thanks,DineshHi Dinesh ,As discussed over webex,we need to manually do switch over.It's not automatically, NSO cli can be used as discussed over a call.ThanksPriyanka.Correct steps have been provided. |
Errors with default optical, ron and zr packages: cisco-optical-cfp 1.0.0 ncs-5.5.2-cisco-optical-cfp-1.0.0-M0 407bdfd 5.5.2 - SyntaxError: invalid syntaxcisco-ron-cfp 1.0.0 ncs-5.5.2-cisco-ron-cfp-1.0.0-M0 407bdfd 5.5.2 - TypeError: namedtuple() got an unexpected keyword argument 'defaults'cisco-zr-cfp 1.0.0 ncs-5.5.2-cisco-zr-cfp-1.0.0-M0 407bdfd 5.5.2 - TypeError: namedtuple() got an unexpected keyword argument 'defaults' | Hi Tani,Please verify if the following RON requirements have been met.<ol>NSO Version :5.5.2Java: OpenJDK 11.2 or laterPython: 3.8 or laterPython Module "Paramiko" (Installed root level)xmllint (latest package)</ol>If the above requirements have been satisfied and the issue persist, please ping me and we can jump into a call to debug.Thank you,AbeHi Tani,Please verify if the following RON requirements have been met.<ol>NSO Version :5.5.2Java: OpenJDK 11.2 or laterPython: 3.8 or laterPython Module "Paramiko" (Installed root level)xmllint (latest package)</ol>If the above requirements have been satisfied and the issue persist, please ping me and we can jump into a call to debug.Thank you,AbeJust followed up with Tani if able to check RON pre-reqs and add them if it was missing. Tani said that he would check and get back to me if issue persist.Hi Tani,I move to close this ticket EOD tomorrow unless you still encounter issues after verifying all RON pre-reqs are satisfied. You can always open another support ticket if issue arises after we've closed this ticket.Please let me know if you have other question or concern regarding this ticket.Thank you.AbeInformed Tani that ticket will be closed today, Tuesday 07/20/21, if no response is heard from him/her regarding RON package issues persisting even after verifying pre-requisites.CInformed Tani that ticket will be closed today, Tuesday 07/20/21, if no response is heard from him/her regarding RON package issues persisting even after verifying pre-requisites. Treating this issue solved and closing the ticket. |
illegal reference for provisioning a policy on LSA setup: 1. Setup LSA with IPv6 addresses2. Onboard NSO and devices to CNC3. Provision policy or service from CNC UI The dry-run failed with illegal reference ( screenshot attached )Validation failed : illegal reference : /ncs:devices/device{rfs-196}/config/cisco-sr-te-cfp-internal:sr-te/cisco-sr-te-cfp-sr-policies-internal:policies/policy{SRv6-711-te-absolute-segments PE-C}/head-endshow commands output for cfs and rfs nodes:CFS:admin@ncs> show cluster RECEIVED NAME NAME STATUS LAST EVENT NOTIFICATIONS ------------------------------------------------------------------------------rfs-195 ncs-events up 2022-04-04T03:42:50.818341+00:00 10 rfs-196 ncs-events up 2022-04-04T22:15:01.063702+00:00 12 REMOTE LOCAL REMOTE NODE ADDRESS PORT CHANNELS USER USER STATUS TRACE -------------------------------------------------------------------------------------------rfs-196 2001:420:10e:201d:172:23:85:196 2022 - admin admin up disabled rfs-195 2001:420:10e:201d:172:23:85:195 2022 - admin admin up disabled RFS-195:root@rfs-195:~# ncs_cli -u adminUser admin last logged in 2022-04-04T22:13:13.951887+00:00, to rfs-195, from 2001:420:10e:201d:250:56ff:fe84:171e using netconf-sshadmin connected from 10.21.118.208 using ssh on rfs-195admin@ncs> show devices listNAME ADDRESS DESCRIPTION NED ID ADMIN STATE -----------------------------------------------------------------------------------CE-B f168:2000::192:168:11:98 - cisco-iosxr-cli-7.38 unlocked PE-A f168:2000::192:168:11:79 - cisco-iosxr-cli-7.38 unlocked SR-PCE-85 f168:2000::192:168:11:85 - cisco-iosxr-cli-7.38 unlocked TOP-LEFT f168:2000::192:168:11:76 - cisco-iosxr-cli-7.38 unlocked TOP-RIGHT f168:2000::192:168:11:74 - cisco-iosxr-cli-7.38 unlocked RFS-196:admin@ncs> show devices listNAME ADDRESS DESCRIPTION NED ID ADMIN STATE --------------------------------------------------------------------------------------BOTTOM-LEFT f168:2000::192:168:11:77 - cisco-iosxr-cli-7.38 unlocked BOTTOM-RIGHT f168:2000::192:168:11:75 - cisco-iosxr-cli-7.38 unlocked CE-A f168:2000::192:168:11:99 - cisco-iosxr-cli-7.38 unlocked PE-B f168:2000::192:168:11:78 - cisco-iosxr-cli-7.38 unlocked PE-C f168:2000::192:168:11:73 - cisco-iosxr-cli-7.38 unlocked | Hi Crystal,It seems like NSO is having trouble finding your RFS Node in your CFS device tree.Could you paste the output of the following commands from your CFS node (in config mode):1. "run show devices list"2. "show devices lsa dispatch-map"Thanks,Isaac KimHi Isaac,Here is the output from my CFS nodes:admin@ncs% run show devices listNAME ADDRESS DESCRIPTION NED ID ADMIN STATE ------------------------------------------------------------------------------------rfs-195 2001:420:10e:201d:172:23:85:195 - cisco-nso-nc-5.7 unlocked rfs-196 2001:420:10e:201d:172:23:85:196 - cisco-nso-nc-5.7 unlocked admin@ncs% show devices lsa dispatch-map device BOTTOM-LEFT { ned-id cisco-iosxr-cli-7.38:cisco-iosxr-cli-7.38; remote-node rfs-196;}device BOTTOM-RIGHT { ned-id cisco-iosxr-cli-7.38:cisco-iosxr-cli-7.38; remote-node rfs-196;}device CE-A { ned-id cisco-iosxr-cli-7.38:cisco-iosxr-cli-7.38; remote-node rfs-196;}device CE-B { ned-id cisco-iosxr-cli-7.38:cisco-iosxr-cli-7.38; remote-node rfs-195;}device PE-A { ned-id cisco-iosxr-cli-7.38:cisco-iosxr-cli-7.38; remote-node rfs-195;}device PE-B { ned-id cisco-iosxr-cli-7.38:cisco-iosxr-cli-7.38; remote-node rfs-196;}device PE-C { ned-id cisco-iosxr-cli-7.38:cisco-iosxr-cli-7.38; remote-node rfs-196;}device SR-PCE-85 { ned-id cisco-iosxr-cli-7.38:cisco-iosxr-cli-7.38; remote-node rfs-195;}device TOP-LEFT { ned-id cisco-iosxr-cli-7.38:cisco-iosxr-cli-7.38; remote-node rfs-195;}device TOP-RIGHT { ned-id cisco-iosxr-cli-7.38:cisco-iosxr-cli-7.38; remote-node rfs-195;}device rfs-195 { ned-id cisco-nso-nc-5.7:cisco-nso-nc-5.7; local;}device rfs-196 { ned-id cisco-nso-nc-5.7:cisco-nso-nc-5.7; local;}Hi Crystal,Your CFS output looks good. To accelerate RCA, would it be possible to provide your NSO node ssh credentials so I can check a few things? I will not modify anything on your NSO setup.Thanks,Isaac KimSure Isaac,Here is the info.:CFS: 172.23.85.194RFS-195: 172.23.85.195RFS-196: 172.23.85.196id/pw: root/Vtsisco@123!Thanks.-CrystalHello Crystal,Thank you for access to your setup.I can see the following on your CFS node :<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"><pre class="code-java">admin@ncs% show devices device rfs-195 config devices deviceNo entries found.</pre></div></div>It seems like your rfs-195 config has not been synced with your CFS node.I would suggest to try a sync-from on your CFS node targeting your RFS node as suggested here : Please let me know if this works.Thanks,Isaac KimThanks Isaac. I am able to provision service/policy after running the following commands on CFS node:request devices fetch-ssh-host-keysrequest devices sync-fromThanks.-CrystalGreat! In that case, I will mark this ticket as resolved.If you have any other further related issues, please feel free to reopen this ticket.Thanks,Isaac Kim |
TSDN 4.0.0 - M3 - CFP Upgrade from 3.0 to 4.0 Failed at "5. NSO Startup with package reload force + ignore initial validation": TSDN 4.0.0 - M3 - CFP Upgrade from 3.0 to 4.0 Failed at "5. NSO Startup with package reload force + ignore initial validation" with error message in attached screenshotAdditionally 1) steps 3 (3. Remove old packages from TSDN CFP 3.0) and 4 (4. Copy new packages from TSDN CFP 4.0 with new ncs.conf) are not clear enough to follow e.g it need to help withfor #3, how to identify legacy NEDs on 5.5.2.12-TSDN 3.0.0 RCsetup?For #3, (To migrate to : 6.77) and (To migrate to : 7.38) - what is meaning of this ?</ul>for #4, does this setup require all packages and all NEDs to be moved and need to identify subdirectory structure too for clarity.For #4, there are more NEDS in this package, with overlapping information from step #3, are these all required along with one from #3?</ul>2) For 5. NSO Startup with package reload force + ignore initial validationscript snippet does not correspond to one found on this upgrade scenario on system. See attached screenshot for what is found on system. | setup details10.194.63.180 ssh nso/Vtsisco@123!UI admin/Vtsisco@123!Hello Vipin,Below are replies to your questions1. For NED migration, both old NED and new NED need to be loaded into NSO. Because the old NED was compiled with old NSO version (NSO 5.5.2 from TSDN 3.0), to migrate from old NED to new NED, we need to load the old NED with new NSO version (NSO 5.7 from TSDN 4.0). This can be done by recompiling old NED with new NSO version. For your typical TSDN 3.0 -> 4.0 upgrade, there is no need to analyze which NED require migration as we provide instructions for packaged NEDs. We also provide old NEDs recompiled with new NSO version. From this point, we consider the old NED to be a "legacy" NED.Lets walk through the upgrade steps:3. Remove old packages from TSDN CFP 3.0Here we should remove old packages from TSDN CFP 3.0 from following path (path depends on type of install)NSO System Install: /var/opt/ncs/packages/NSO Local Install runtime directory: packages//// For NED packages that will be upgraded (major version upgrade), the "legacy" NED must be recompiled with new NSO version and loaded to migrate device data/// To load legacy NED with new NSO version, remove legacy NED package and replace with recompiled NED belowLegacy XE CLI NED 6.74 compiled with .7 (To migrate to : 6.77) : XE-CLI-6.74-compiled-with-.7Legacy XR CLI NED 7.33 compiled with .7 (To migrate to : 7.38) : XR-CLI-7.33-compiled-with-.7To "migrate" XE CLI NED 6.74 to 6.77, we need "legacy" XE CLI 6.74 NED recompiled with new NSO version 5.7. We provide this with the download link "XE-CLI-6.74-compiled-with-.7". Download the recompiled NED from the link and place it in path defined above. To "migrate" XR CLI NED 7.33 to 7.38, we need "legacy" NED 7.33 recompiled with new NSO version 5.7. We provide this with the download link "XR-CLI-7.33-compiled-with-.7". Download the recompiled NED from the link and place it in path defined above. 4. Copy new packages from TSDN CFP 4.0 with new ncs.conf/// Copy over 4.0 packages but do not remove any legacy NEDs compiled with .7With the recompiled "legacy" NEDs defined in <NSO PATH>/packages, copy TSDN 4.0 packages.At this point, you should have two NEDs per NED type. XR CLI 7.33 -> 7.38 NEDs:<NSO PATH>/packages/ncs-5.7-cisco-iosxr-7.38.X.tar.gz<NSO PATH>/packages/ncs-5.7-cisco-iosxr-7.33.X.tar.gzXE CLI 6.74 -> 6.77 NEDs:<NSO PATH>/packages/ncs-5.7-cisco-ios-6.77.X.tar.gz<NSO PATH>/packages/ncs-5.7-cisco-ios-6.74.X.tar.gzIn the next steps, you will reload NSO so that both "legacy" NED and "new major version" NED will be loaded into NSO. During migration upgrade step, you will migrate from the loaded "legacy" NED to the loaded "new major version" NED.I hope this clarifies the procedure for NED migration. 2. I can see that the script is a bit different. I will update the wiki to clarify the objective of the step which is to add "--ignore-initial-validation flag".Please let me know if you have any other questions.Thanks,Isaac KimHi Isaac, Blocker issue TSDN 4.0.0 - M3 - CFP Upgrade from 3.0 to 4.0 Failed at "5. NSO Startup with package reload force + ignore initial validation" with error message in attached screenshot is still not addressed. I believe you are still troubleshooting it?Thanks,VipinHello Vipin,I have discussed with Quy about some confusion about upgrade wiki steps. We identified few areas which I reworded for clarity. We identified that one issue on your setup is that your system is still pointing to old NSO version: It should be pointing to NSO 5.7 before you do a reload.Please refer to Step B-2 of the upgrade wiki and let me know if you are still running into the error.Thanks,Isaac Kimhi Isaac,We (Vipin and I) have discussed about the current nso version on .180 - the upgrade system - thanks for your help with the wiki steps - this will help all users during the upgrade process. We will follow the revised steps you have provided and will update you if any issue occurs. Thanks,-Quyhi Isaac - adding the email from Vipin lastnight since the ticket was closed:Hi Isaac, SahithiJIRA is closed pre-maturely so resorting to emails.Fixed ncs-5.7.2.1 install following steps Step-B, 2 -1 thru 3c.Error from 5, 3 change toroot@nso-10-194-63-180:/opt/ncs/ncs-5.7.2.1/etc/ncs# sudo NCS_RELOAD_PACKAGES=force /etc/init.d/ncs startStarting ncs: Bad configuration: /etc/ncs/ncs.conf:0: Cannot access directory ./ncs-cdb, definedfor/ncs-config/cdb/db-dirDaemon died status=21STEP-B, 2-4 is unclear about how to merge two ncs.conf (/opt/ncs/nso_5.7.2.1/etc/ncs/ncs.conf and/etc/ncs/ncs.conf). Please note there is typo here nso to fix (should be ncs).Quy ; I, interpreteda. merge changes from /etc/ncs/ncs.conf INTO/opt/ncs/nsoc_5.7.2.1/etc/ncs/ncs.confb. copy merged/opt/ncs/nsoc_5.7.2.1/etc/ncs/ncs.conf to/etc/ncs/ncs.conf i.e. overwrite /etc/ncs/ncs.conf. To identify changes to merge we two have to refer to changes required in ncs.conf per install for NSO TSDN 3.0 FP if you want to troubleshoot, setup details are:IP 10.194.63.180ssh nso/Vtsisco@123!Ui admin/ Vtsisco@123!Thanks,Vipin Sharma]Hi Quy,Not sure why the ticket was closed. We haven't closed it from our side. I see it still is open. Hopefully, we should be able to communicate in comments.Updating my reply on this comment. Hope it resolved the issue.```Hi Vipin,The below is occurring because your current ncs.conf is not pointing to the correct cdb folder.Try changing the below variable.<db-dir>{NCS_RUN_DIR}</db-dir> -> <db-dir>{NCS_RUN_DIR}/cdb</db-dir>Regarding the steps, I believe Isaac would have better input here.@Isaac Kim (isaakim) Any thoughts about steps for merging the ncs.conf files? ```ThanksSahithiHi Vipin and Quy!I have updated the wiki step B-2 with more explicit and clear steps.Please review and let me know if this change is satisfactory.Thank you for the feedback!Thanks,Isaac KimFailure At STEP-B, 8. Sync-from Migrated Devices for new NED capabilitiesadmin@ncs> request devices device TB4-PE-A sync-from dry-run result falseinfo Failed to connect to device TB4-PE-A: connection refused: NEDCOM CONNECT: Authenticate: Exhausted available authentication methods. Server allowed: [ keyboard-interactive password ] in new stateadmin@ncs>Hi Vipin,Would you be able to confirm what authentication method was used for this device prior to upgrade? Was it ssh-rsa, ssh-dss, etc?Thanks,Isaac KimHi Isaac,I do not know this, is there a way to find out ?I believe it should be default for device from cnc fp 3.0.0 RC Thanks,VipinHi Vipin,No problem, we will try to investigate now. I hope its okay if we validate few things on your machine. We may also try setting some NSO config to debug but will not push anything southbound. Thanks,Isaac KimHi Vipin,Do you by any chance still have a copy of your pre-upgrade ncs.conf? If so, would you be able to share it here?Thanks,Isaac KimHi Issac,thanks, Please take setup for your investigation. Thanks,VipinHere is pre-upgrade ncs.conf /home/nso/tsdn3.0.0-backup/etc_nsc_ncs.conf/home/nso/tsdn3.0.0-backup/ ncs-5.5.2.12@2022-03-18T17:07:00.backup.gz has entire backup before upgrade, may be you can find it here tooHi Quy and Vipin,I have RCAed this with the help of Linh and we discovered that the source of issue mentioned above was due to the fact that encrypted-strings in old ncs.conf was not transferred over to new ncs.conf which meant that ssh-rsa host keys could not be decrypted as the new ncs.conf default encryption keys were being used.old ncs.conf:<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"><pre class="code-xml"> ${NCS_DIR}/bin/ncs_crypto_keys ${NCS_CONFIG_DIR}/ncs.crypto_keys </pre></div></div>new ncs.conf:<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"><pre class="code-xml"> 0123456789abcdef 0123456789abcdef 0123456789abcdef 0123456789abcdef 0123456789abcdef0123456789abcdef 0123456789abcdef0123456789abcdef 0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef </pre></div></div>The solution to this problem is to transfer your old encryption keys to new ncs.conf:<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"><pre class="code-xml"> ${NCS_DIR}/bin/ncs_crypto_keys ${NCS_CONFIG_DIR}/ncs.crypto_keys </pre></div></div>We have done this for you during the debug process and now devices can be reached from your NSO setup.Thanks,Isaac KimHi Quy and Vipin,I hope the upgrade procedure went well!If everything is good, I will close this ticket in next few days.Please let me know if you have any other questions in this regard.Thanks,Isaac KimHi Isaac, The upgrade went well, thanks for updating the wiki per our requested - appreciated your help - you can close the ticket for us please.Thanks and regards,-QuyNotes: the most time consuming was the merging the old ncs.conf with the new version - there are so many configurations need to carry over. Hope we can simplify this step somehow. Designated closed. For additional queries on ncs.conf migration, please open a new ticket. |
Need pre-requisite configuration forL2VPN-E-Tree & evpn-pbb - custom: Need pre-requisite configuration forL2VPN-E-Tree ; evpn-pbb - custom to provision the service. | Hi Ragesh ,There is no prerequisite for this service from device perspective . bridge-domain must be defined in payload.ThanksPriyankaHi Priyanka,XRV9K platform is not supporting for bridge-domain config. The device version we have 7.5.2.19I, which version we have support for ELAN, ETREE ; PBB-Custom services? If XRV9K is not supporting any other simulator we can use for the testing?Hi Ragesh,The platform need to support VPLS Bridge Domains as noted on the wiki: XRv9K does not support VPLS Bridge Domains. Please try ASR9K.Thanks,RegiHi Regi,ASR9K is the physical device right, Do we have any virtual platform for ASR9K?You can use ASR9KvHi RageshPlease let us know if anything else is needed or we may close the ticket.Thanks,NikhilClosing the ticket as the required information has been provided. |
get_schema API issue on NSO M3 version: get_schema API issue on NSO M3 version.Request{"params": {"levels": -1,"insert_values": true,"stop_on_list": true,"path": "/l2vpn-ntw:l2vpn-ntw/vpn-services/vpn-service{TEST1}/vpn-nodes/vpn-node{TB3-P-BOTTOMLEFT}","evaluate_when_entries": true,"th": 5},"jsonrpc": "2.0","id": 102,"method": "get_schema"}Response{"jsonrpc": "2.0","error": {"type": "session.invalid_sessionid","code": -32000,"message": "Invalid sessionid"},"id": 102} | Hi Demeke,I tested in my local and the API seems to be working and getting the result correctly. From the message it seems like the session-id that you are using is invalid. Please use the "login" and "new_trans" API to get the session-id and transaction-id and then run this command with those id.Let us know your NSO setup details for us to check further in case the above does not work.Thanks,NikhilHi Nikhil,I still see this issue admin/Ovatest123@Try to create l2vpn services and when you add the vpn-node you will see the issue.Let me know if you want a webex session also.Thanks,Demeke.Hi Demeke,The above are CNC UI details. Can you help us with the NSO console server and login details?Please message me on teams if you want to have a session to discuss this.Thanks, NikhilHi Nikhil,Please find the NSO setup info. 10.22.179.181ubuntudoc/ubuntudocThanks,Demeke.Hi Demeke,This looks like a platform issue with the IETF L2NM model. We have raised a RT with the NSO platform team and will let you know once we hear anything from them.As a workaround, the get_schema request with "insert_values" = "false" can be used from CNC side. We have tested the same and it seems to be working fine. Below is the sample request:Request{"params": {"levels": -1,"insert_values": false,"stop_on_list": true,"path": "/l2vpn-ntw:l2vpn-ntw/vpn-services/vpn-service{TEST1}/vpn-nodes/vpn-node{TB3-P-BOTTOMLEFT}","evaluate_when_entries": true,"th": 5},"jsonrpc": "2.0","id": 102,"method": "get_schema"}Thanks,NikhilHi Nikhil,The suggested workaround works but it breaks CNC Prov-UI dynamic implementation and we are waiting for the official fix.Thanks,Demeke.Hi Demeke,We have already opened a case with the platform team for this issue. Will update you as soon as we hear from them.Thanks,NikhilHi Nikhil,We have tried the workaround to use the insert_values=false, and that cause issue in the subsequent get_schema API. And we have looked the get_elem API and that also does not help for our use case. In Prov-UI we use get_schema api and parse the data to show the panel view. Therefore the workaround is not working for our use-case and looking for the fix.This is a related ticketThanks,Demeke. Hi Demeke,The below RT raised for this issue with NSO team has been fixed:The change will be included in thebelow and later versions:nso-5.5.9 (31-Jan-2023)nso-5.6.11nso-5.7.9 (24-Jan-2023)nso-5.8.7nso-6.0.1.1nso-6.0.2 (17-Jan-2023)nso-6.1 (13-Apr-2023)Thanks,NikhilRT raised for this issue was fixed by the NSO team and hence the issue is resolved. |
How auto color from CS model choses the color: Hi,There is a option in CS model where user can choose auto-color or can manually specify the color.Kindly let me know how the auto-color value is chosen ?Is this depends on any resource pool in NSO which would leveraged if auto-color is chosen.I have attached the screenshot of different resource pool available in NSO.Thanks,Naveen | Hello Naveen,Please see answers below::Kindly let me know how the auto-color value is chosen ?>>>> You do not need to set any thing for selecting auto-color. If you do not set any color in the payload, the default option will be set to auto-color.Is this depends on any resource pool in NSO which would leveraged if auto-color is chosen.>> When auto-color is defaulted the pool undercs-sr-te-resource-pools is used.Sample payload is below: <cs-sr-te-resource-pools xmlns="http://cisco.com/ns/nso/cfp/cisco-cs-sr-te-cfp"> <color-pool-name>color-pool</color-pool-name> <bidirectional-association-id-pool-name>bidirectional-association-id-pool</bidirectional-association-id-pool-name> </cs-sr-te-resource-pools>If there is no resource-pool you will see an error message such as below:ContextPlease let us know if this helps.Regards,Janaki DuggiralaHi Janaki,It looks like there is a reference for 2 pool names namely "color-pool-name" ; "bidirectional-association-id-pool-name".Kindly let me know which pool range will be used to assign color to the policy ?Thanks,Naveen Hello Naveen,>> cs-sr-te-resource-pools -> color-pool-name is used for the color>> FP does not hardcode bidirectional id. Its either explicitly defined by user or auto allocated using the pool-nameClosing ticket since received confirmation from customer that all questions are clarified.Customer was provided clarification. Closing ticket after confirmation from customer. |
L2vpn P2p failed in plan in LSA setup - 5.0 - M4: 1) Install NSO - LSA with 5.0 M4, with TM-TC package2) DLM: dlm-service-pack/5.7.6/35/cw-na-dlm-fp-5.0.0-nso-5.7.6.tar.gz3) TM-TC: FP-integ/5.0.0-130/cw-na-fp-tmtc-5.0.0-130-nso-5.7.6.tar.gz4) above packages installed as per CNC status file, which we used for installing all components, same is attached with this request5) Error I am seeing in /var/log/ncs/ncs-python-vm-ietf-l2vpn-nm.log is as follows: <INFO> 07-Dec-2022::01:40:12.528 ietf-l2vpn-nm ncs-dp-1798193-ietf-l2vpn-nm:main:0-2-th-32062: - Internal plan for ('L2NM-L2VPN_P2P_PLAIN-16-internal', 'PE-B') does not exist for /cisco-tsdn-core-fp-common:rfs-flat-L2vpn-remote-site-plan6) logs of : ./get_technical_support_data.sh /tmp/data_120722_031330_dir/data_120722_031330.tgzserver CFS: 10.56.116.151nso/Public1234!RFS1: 10.56.116.152RFS2: 10.56.116.153nso/Public1234!7) Version package: 8) Below payload is sucessfull in M3 standalone : M3 standalone server: 10.56.116.138 : nso/Public1234!payload used:<config xmlns="http://tail-f.com/ns/config/1.0"> <l2vpn-ntw xmlns="urn:ietf:params:xml:ns:yang:ietf-l2vpn-ntw"> <vpn-services> <vpn-service> <vpn-id>L2VPN_P2P_PLAIN-16</vpn-id> <vpn-type>vpn-common:vpws</vpn-type> <vpn-nodes> <vpn-node> <vpn-node-id>PE-A</vpn-node-id> <signaling-option> <ldp-or-l2tp> <pw-peer-list> <peer-addr>100.100.100.6</peer-addr> <vc-id>16</vc-id> <mpls-label xmlns="http://cisco.com/ns/nso/fp/examples/cisco-l2vpn-ntw">111</mpls-label> </pw-peer-list> </ldp-or-l2tp> </signaling-option> <vpn-network-accesses> <vpn-network-access> <id>L2VPN_PLAIN-16</id> <interface-id>GigabitEthernet0/0/0/2</interface-id> <connection> <encapsulation> <encap-type>vpn-common:dot1q</encap-type> <dot1q> <cvlan-id>16</cvlan-id> </dot1q> </encapsulation> </connection> </vpn-network-access> </vpn-network-accesses> </vpn-node> <vpn-node> <vpn-node-id>PE-B</vpn-node-id> <signaling-option> <ldp-or-l2tp> <pw-peer-list> <peer-addr>100.100.100.5</peer-addr> <vc-id>16</vc-id> <mpls-label xmlns="http://cisco.com/ns/nso/fp/examples/cisco-l2vpn-ntw">112</mpls-label> </pw-peer-list> </ldp-or-l2tp> </signaling-option> <vpn-network-accesses> <vpn-network-access> <id>L2VPN_PLAIN-16</id> <interface-id>GigabitEthernet0/0/0/1</interface-id> <connection> <encapsulation> <encap-type>vpn-common:dot1q</encap-type> <dot1q> <cvlan-id>16</cvlan-id> </dot1q> </encapsulation> </connection> </vpn-network-access> </vpn-network-accesses> </vpn-node> </vpn-nodes> </vpn-service> </vpn-services> </l2vpn-ntw></config> | Hi Sampath,You defined netconf-notification subscription name wronglynso@ncs% show devices device sareddyd-esxi-01-vm2 netconf-notifications subscriptionsubscription sareddyd-esxi-01-vm2-cisco-custom-template-events { stream custom-template-events; local-user nso; store-in-cdb true;}subscription sareddyd-esxi-01-vm2-dispatch-map-update { stream dispatch-map-update; local-user nso; store-in-cdb true;}subscription sareddyd-esxi-01-vm2-kicker-events { stream kicker-events; local-user nso; store-in-cdb true;}Please correct netconf-notitifcations subscription name as defined in this link The plan should be 'reached' after the correction.Thanks,LinhWrong configuration for netconf-notification subscription |
Configs for Ipv4 and Ipv6 addresses: As part of Assur-81, SR-V6 monitoring we are looking for different xpath combinations for Ipv4/Ipv6 ip addresses for L3VPN/L2VPN service with L3vpn as the first priority. Could you please help to share the various config details or share the TestBed details to get these kind of config details. | Hi Jason,Attached are ipv4/ipv6 sample configurations. Asr9k-x64-7.6.2.xr.yaml is a simple topology with a few nodes while sol.yaml from Yevgeny Chechelnitsky (ychechel) is more complex topology. His details lab info is in this git Please contact him for access to the git.Thanks,Linh |
metrics and color for forward planning policy missing in yang model: Hi,While displaying the slice template catalogs we have columns metrics and color. Its missing in the M3 yang model. | Hi Manesh,Can you elaborate where do you see metric and color in the slo-sle-tempate (slice catalog)?Color and Metric should come from SR-ODN template.Thanks,LinhHi Linh,We're displaying color and metrics along with forward planning policy. As you said, it'll come along with ODN Template. Can you give me the model path for both color and metric?Hi Magesh,Attached odn-template.xmlSo in the slo-sle-template, the color and metric will be pull in by <forwarding-plane-policy xmlns="http://cisco.com/ns/nso/fp/examples/cisco-network-slice-service">igp</forwarding-plane-policy>Thanks,LinhThanks LinhAs discussing on the call, Magesh understood where to get the color and metric. I close the ticket |
l3vpn model changes: 1. can you tell if more changes planned, or this is the final model?2. regarding ie-profile (=vpn-instance-profile) can you please elaborate what is the active-vpn-instance-profiles ? I see it has its own configs, so I am not sure why do we need the vpn-instance-profile for? For instance in your example I see profile1 which has route targets config, And the node is associated with profile1, but also has route targets configured under the active-vpn-instance-profile. So question is do we need to accumulate the route targets coming from the active also? 3. I see the profile role so it means in case of hub;spoke we cant assign profile to a node with different role? | <ol>I believe Sahithi answered this in the email thread but I will re-iterate here:</ol><div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"><pre>Hi Haim/Idan,There should not be any major changes from the model mentioned below for M4 release:Models:https://wwwin-github.cisco.com/nso-function-pack/tsdn-fp-configs/tree/master/CNC-5.0/CoreFP-Models/ietf-l3vpn-ntw/yangSample Configs:https://wwwin-github.cisco.com/nso-function-pack/tsdn-fp-configs/tree/master/CNC-5.0/CoreFP-Models/ietf-l3vpn-ntw/sample-configsWe will update this thread or email when there are changes to the models.ThanksSahithi</pre></div></div>2. The details can be found here:<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"><pre> 'vpn-instance-profiles': Defines reusable parameters for the same 'vpn-service'.</pre></div></div><div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"><pre> 'active-vpn-instance-profiles': Lists the set of active VPN instance profiles for this VPN node. Concretely, one or more VPN instance profiles that are defined at the VPN service level can be enabled at the VPN node level; each of these profiles is uniquely identified by means of 'profile-id'. The structure of 'active- vpn-instance-profiles' is the same as the structure discussed in Section 7.4, except that the structure of 'active-vpn-instance- profiles' includes 'router-id' but does not include the 'role' leaf. The value of 'router-id' indicated under 'active-vpn- instance-profiles' takes precedence over the 'router-id' under the 'vpn-node' for the indicated address family. For example, Router IDs can be configured per address family. This capability can be used, for example, to configure an IPv6 address as a Router ID when such a capability is supported by involved routers. Values defined in 'active-vpn-instance-profiles' override the values defined at the VPN service level. An example is shown in Appendix A.3.</pre></div></div>To summarize, the "vpn-instance-profile" are just profile definitions and are not configured on the device unless if these "vpn-instance-profile" definitions are configured as the "active-vpn-instance-profile", which also allows overriding some of the configuration for "vpn-instance-profile"3. You would need separate "vpn-instance-profiles", one for "hub" and one for "spoke, then assign those profiles to your vpn-nodesthank you for the info |
service-tag-opaque not accepting more than one value: Hi,While provisioning a slice, I'm supplying more than one value to service-tag-opaque.Response from NSO:[{"Message":"too many /network-slice-services/slice-service{IT_test2}/service-tags/tag-type{ietf-nss:service-tag-opaque}/value, 2 configured, at most 1 must be configured","nsoResponse":"too many /network-slice-services/slice-service{IT_test2}/service-tags/tag-type{ietf-nss:service-tag-opaque}/value, 2 configured, at most 1 must be configured"}]Payload attached. | Hi Magesh, You defined as the following <tag-type> <tag-type>ietf-network-slice-service:service-tag-opaque</tag-type> <value>value</value> <value>test</value> </tag-type>Please remove one. CFP validates it and allow only one.Thanks,LinhIt is part of validation and tag-value should be at most 1 |
no plan notification on ELAN service: we noticed a case when operation assurance on services of type ELAN - we recieve from NSO notifications only on the service, but not on the planwhen doing the same operation on EVPN - we do see both service and plan notifications arrive - can you have a look on it? here is the single notification we get on the ELAN:[{"handle":"1","message":{"db":"running","changes":[{"keypath":"/l2vpn-ntw:l2vpn-ntw/vpn-services/vpn-service{L2VPN_NM-ELAN-170}/l2vpn-ntw-augmentations:service-assurance/monitoring-state","op":"value_set","value":"enable"}],"user":"admin","ip":"https://172.20.200.130"}}] | Hello, Notifications are usually determined by the bootstrap files that are onboarded to the setup.Can you please share the setup on which this issue was seen so we can investigate this?Regards,Janaki DuggiralaHere is NSO service info: 172.20.100.133 admin/Cwork123!172.20.200.133Uploaded the service payload Hello Jason,We see that plan notifications are not being generated for L2NM EVPN MP -> service-assurance, but we do see that the AA notifications are still being generated correctly. As CNC UI is already receiving AA notifications from NSO for service-assurance updates, it would be possible to use AA notifications rather than plan notifications.Just a note, we cant reproduce this behavior in TSDN 5.0.Thanks,Isaac KimHi Isaac,Thanks for the RCA. From what I understand, CAT uses both notifications for different purposes. Hi Alan ; Idan, would you please chime in on this.Thanks,-jasonhi Isaac, what do you mean by AA notifications? not sure nso-c listen to this kind of notifications - can you send example? which component in CNC listen to this notifications? Alan - are you aware of it? Hello, we have a separate notification stream for service-assurance config changes as these changes are not pushed to device (as it is a service config only) and may not always result in a plan change. The service-assurance notifications include all the required information that would be provided in an equivalent service-state-change notification, with the exception of no plan component information (which again is not relevant to service-assurance config as it is not pushed to any particular device/component).service-state-changes notification<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"><pre class="code-java">admin@ncs% run show notification stream service-state-changesnotification { eventTime 2022-11-03T18:27:16.981329+00:00 plan-state-change { service /l2vpn-ntw/vpn-services/vpn-service[vpn-id=] component PIOSXR-1_a1 state ready operation modified status reached }}</pre></div></div>service-aa-changes notification<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"><pre class="code-java">admin@ncs% run show notification stream service-aa-changesnotification { eventTime 2022-11-03T18:27:57.889234+00:00 service-assurance-config-change { service /l2vpn-ntw:l2vpn-ntw/vpn-services/vpn-service[vpn-id=EVPN-MP-ELAN] operation modified }}</pre></div></div>Here we can see that service-aa-changes notification has eventTime, full service path (including service name), and operation. This should have the relevant information to make necessary resulting operations/updates.Thanks,Isaac KimHi Isaac, I just checked on CFP5.0-M3, change of service-assurance on ELAN service does not send the plan change notification. The other VPN service does not have such problem. From what I understand, "plan change" notification is expected by CAT on service-assurance change. This feature has been working since CFP 3.0.Srini, Alan ; Idan, please confirm. Again, this is a severe issue which is blocking SH 5.0 feature development since it is not working on CFP 5.0-M3 either.Thanks,-jasonClosing this as the patch was provided for 5.0 M3 to generate plan notification on ELAN service. The issue is already fixed starting 5.0 M4. |
NSO TSDN 5.00-M4 FP route policy association failure: Hi,Trying to deploy some L2 services using route policy I see that even though the route policy was successfully created and deployed, the service association failed and I'm getting an error message saying "route-policy illegal reference" even though it exists. Same error appears while using the NSO configuration screen and in Postman commands.Please advise.NSO server: 10.56.58.197Credentials: admin / Public1234! SSH: cw-admin / Public1234! | Hi Shlomi,We are getting permission denied for the credentials provided. Please check and suggest.Regards,Nishad Subair.I found the problem.It was some missing configuration in route policy creation.You can close / remove this case.Thank you for your support.Hi Shlomi,Thank you for the update. I will close the ticket.Thanks,Nishad Subair. |
L2 with Point To Point Connectivity Type with Dedicated: Hi,Looks like isolation type is removed from L2 Slice when Point-To-Point is selected.Whereas "isolation type" type is shown when "Hub-Spoke" ; "Any-to-Any" is chosen.I persume it is a bug.Kindly let us know.Regards,Magesh | Hi Magesh,We will look into this.Thank youSahithiHi Magesh,L2 Slice supports isolation for connectivity types: Hub ; Spoke and Any-to-Any.It is not supported for P2P which why it does not show up on the UI.We updated the wiki to reflect the same: Please let us know if there is anything else regarding this query.ThanksSahithi |
evpn-pbb Undrlying TE: Fewquestions on the latest release M3. evpn-pbb - any-to-any Does it support underlying Static Policy SR-MPLS/SRv6Does it support underlying ODN Template SR-MPLS/SRv6Wiki does not contain any example,and we are failing to provision it. evpn-pbb - hub-spoke Wiki does not contain any example, and we are failing to provision it Does it support underlying Static Policy SR-MPLS/SRv6Does it support underlying ODN Template SR-MPLS/SRv6Wiki does not contain any example,and we are failing to provision it | HiOnly ODN SR-Policy is supported for evpn-pbb. SRv6 is not supported for evpn-pbb.Please refer to below link for device mappings. If the config is missing, then its not supportedLet us know if anything else is required or we may close the ticket.Thanks.Clear. This is not working though. Look at Hi YevgeniCDET() was filed for the issue Issue was fixed and released as part of TSDN 4.0 M3.Thank you.Closing the ticket as the issue is fixed. |
Need updated/modified prepackaged NSO FP for Brownfield support testing: For Brownfield support testing, Srinivasan chikala shared 3 examples to verify new custom FP. We also need to test extensibility in default Prepackaged service. Kindly share an updated/modified prepackaged NSO FP for L3VPN NM/L2VPN NM/SR/RSVP. Just adding one additional field/range variation/any simple change would be fine. | Hi Ajitha,I have attached the slides (Sample_Customization.pptx) about how to customize FP with L3NM and L2NM package as examples. You can follow the same to customize any released packages. Please let me know if this helps or you have any problem customizing the packages.Hi Linmao, Our understanding is to get custom Packages from developers and use it for our testing. But gone through the PPT. It has good explanation. Would you please share a webex recording/setup a call for any one Service pack modification, this would help us to proceed further.Hi Ajitha,I am not sure what your ask is. Can you clarify please?Thanks,NipaFor Brownfield support Feature testing, We received few custom FPs(CNC+NSO) from Srinivasan Chikala. Apart from that, we need to verify the behavior of modified Prepackaged FP (eg: L3VPN+ any one simple field change/new field addition). Would be helpful if you can share modified FP of any default Prepackaged FP(L3VPN/L2VPN/SR/RSVP/ODN/Flat). Hi Ajitha,You can use the sample FPs that we ship with the product and use the PPT sent by Lin to create yet another package. We do not have any more modified pakages to give away.Thanks,NipaClosing this ticket. Further issue can be resolved in new support ticket. |
Do not see head-end devices when provision service/policy on LSA setup: Steps:1. Setup IPv6 CNC with LSA. 2 Onboard provider and devices. I am able to see devices list on both of the rfs nodes as expected. 3. But when provision a service or policy, the head-end drop down shows empty list.Is there anything I can check on NSO side to make sure there is no configuration issue?NSO version: 5.7.2.1TSDN cfp: 4.0.0 M4 | Re-run the bootstrap load merge steps. Then I am able to see the head-end list. However, when commit the load merge commands, the output says "no modification to commit". It does seem the load merge was done the first time but didn't process properly which cause "show status-code-cfp" didn't work before re-run the load merg. Is this an issue to be looked at? Attached is the bootstrap load merge re-run done on one of the rfs nodes Hi Crystal,If you are not able to access your device list as part of your service provisioning, you may want to check a few things on NSO CLI.Verify Dispatch Map<ol>Log into NSO CLI on your CFS Node (ncs_cli -u <USER>)Enter config mode (configure)Check dispatch map (show devices lsa dispatch-map)</ol>Verify you have the output<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"><pre class="code-java">device <DEVICE NAME> { ned-id <NED ID>; remote-node <RFS NODE NAME>;}device <RFS NODE NAME> { ned-id <RFS NED ID>; local;}</pre></div></div>If you are missing the <DEVICE NAME> entry, you have to sync dispatch map ().If you are missing the <RFS NODE NAME> entry, you must onboard RFS node to CFS node ().Once you verify the above, please let me know if you are able to resolve the issue.Thanks,Isaac KimHi Isaac,I am able to see the head-end after re-run the bootstrap load merge steps as I described in my 2nd input on this ticket. It seems there is no change in 2nd commit, but the head-end info. displayed after that. Will keep an eye on this. If it happens again then maybe some potential issue for the load merge process. Thanks.-CrystalHi Crystal,Thats good that your setup is fine. We can keep this ticket in info-request state until end of this week and if we get no reply, then I will close it.Thanks,Isaac KIm |
TSDN-3.0.0-M3 - OLS Scenario Regression: Working with M2 with the same environment nso522/Public1234!Error running action for side-effect item /cisco-ron-cfp:ron/ron-ml-plan{TOPRIGHT_BOTTOMRIGHT_400_TR_OLS}/plan/component{ncs:self self}/state{ncs:init}: Python cb_action error. Failed to retrieve/validate SIPsSTATUS_CODE: RON-505REASON: Fetch Optics failedCATEGORY: custom-actionSEVERITY: ERRORContext [name = Fetch SIP Action Failed, message = Fetch SIP action Failed state = {'service': ListElement name=ron-ml tag=1842926444 keys={TOPRIGHT_BOTTOMRIGHT_400_TR_OLS}}] | Hi Yevgeny,Looks like this issue is old, can I close the ticket?Thanks,VanYevgeny has not responded and there is no outstanding RON support issue from his side that we know of, close the case. |
Route Policy Construction Problem: When route policy is constructed, it omits entriessee attached NSO: admin/Public1234!Devices: PE-A ; PE-C | Flase Flag, close the issue |
Update the "cnc-custom" metadata in policy in L2VPN: Under the L2VPN te-mapping the policy leaf("/l2vpn-ntw:l2vpn-ntw/vpn-services/vpn-service/vpn-nodes/vpn-node/te-service-mapping/te-mapping/sr-policy/policy") Please update the "cnc-custom" metadata as below tailf:meta-data "cnc-custom" { tailf:meta-value ' { "dependency": "[]", "type": "checkbox", "field": "auto-evi-target", "pre-select": "true","dependencyForReload": ["/l2vpn-ntw:l2vpn-ntw/vpn-services/vpn-service/vpn-nodes/vpn-node/te-service-mapping/te-mapping/sr-policy/policy-type"] }'; } | Minor update please use this to update the policy config metadatatailf:meta-data "cnc-custom" {tailf:meta-value ' { "dependency": "[/l2vpn-ntw:l2vpn-ntw/vpn-services/vpn-service/vpn-nodes/vpn-node/te-service-mapping/te-mapping/sr-policy/policy-type]", "type": "dropdown", "field": "policy", "leaf-validation": "true", "pre-select": "true", "reloadDependency": "[/l2vpn-ntw:l2vpn-ntw/vpn-services/vpn-service/vpn-nodes/vpn-node/te-service-mapping/te-mapping/sr-policy/policy-type]" }';}Hi Demeke,Shall we replace the existing meta-data which is mentioned below with the new one as in the message above ?Existing meta-data:tailf:meta-data "cnc-custom" { tailf:meta-value '{ "dependency": "[]", "type": "dropdown", "field": "policy-list", "leaf-validation": "true", "pre-select": "none" }'; }Proposed Change :tailf:meta-data "cnc-custom"{ tailf:meta-value ' { "dependency": "[/l2vpn-ntw:l2vpn-ntw/vpn-services/vpn-service/vpn-nodes/vpn-node/te-service-mapping/te-mapping/sr-policy/policy-type]", "type": "dropdown", "field": "policy", "leaf-validation": "true", "pre-select": "true", "reloadDependency": "[/l2vpn-ntw:l2vpn-ntw/vpn-services/vpn-service/vpn-nodes/vpn-node/te-service-mapping/te-mapping/sr-policy/policy-type]" }'; }Thank you,Nishad Subair Hi Nishad,The follwoing is correct one. the pre-select value needs to be "none".tailf:meta-data "cnc-custom"{ tailf:meta-value ' { "dependency": "[/l2vpn-ntw:l2vpn-ntw/vpn-services/vpn-service/vpn-nodes/vpn-node/te-service-mapping/te-mapping/sr-policy/policy-type]", "type": "dropdown", "field": "policy", "leaf-validation": "true", "pre-select": "none", "reloadDependency": "[/l2vpn-ntw:l2vpn-ntw/vpn-services/vpn-service/vpn-nodes/vpn-node/te-service-mapping/te-mapping/sr-policy/policy-type]" }';}Thanks,Demeke. |
Clarification on OOS Node Redeploy: Hi Team,Please help to confirm that the following scenario is correct or not.1. Create a L2VPN Service2. Bring any one of the service node out-of-sync3. Edit the service and commit changes4. The service will be pushed unto "failed" state.<ul><ul>Now click on re-deploy from the provisioning nso action button. Should this bring the service Success or say error that the particular node is outof-sync?</ul></ul>Please help to confirm | If you did not commit any action (sync-from/sync-to) to make the device in-sync, then yes a re-deploy of the service will still be in the "failed" state, assuming the commit has gone through ( usage of commit-queue or non-commit-queue but resource-manager allocation was required by the service )Thanks,RegiThank you.That seems to be a desperate issue. I have filed the Defect - CSCwb54540I'm seeing the service getting success even when I did not commit any action (sync-from/sync-to)I've updated both the CDETs as they seem related:It would be good if we can have a quick webex regarding this issue.Thanks,RegiHad webex session with Kanchan. The reason this issue was occurring is because service did not have ownership of the device configs as the device configs existed before service creation.I had Kanchan do a "re-deploy reconcile" of the service to re-take ownership of the configs. You can also clean up the device manually and do a sync-from as well if you do not want to do a "re-deploy reconcile". After this step, can you re-test this scenario and let me know if you are getting the expected results or not.Yes. I can perform re-deploy reconsile very well. but I would strongly say this is not the test scenario.The expectation is that any service should take the ownership on the very first commit-changes click at the time of service create.I would still test this following steps described as part of defect debug.Thank you very muchThe reason the service does not take ownership is because the configs existed on the device before service creation. That's also why you do not see dry-run output for the devices. This is expected behavior as far as NSO is concerned.NSO has a feature which does reconcile on first commit which is "commit reconcile", but this option doesn't seem to be available on CNC GUI which is why I suggested the "re-deploy reconcile"Thanks,RegiCould you please confirm, re-deploy reconsile of the service which has OOS/Unreachbale node should be successful or throw error?Hi Dinesh,When you edited the config with out-of-sync device, this commit was rejected and service plan reflects failure and that's to be expected but once you do a service re-deploy, in this case, the service rolls back to the previous provisioned state which was successful in this case ( since there are no new commits to be made by the service as previous commit was rejected ), so this is the expectation.Please let me know if you have any questions.Thanks,RegiHi Dinesh,Please let me know by EOD today if you have further issues; otherwise, I will go ahead and close this ticket.Thanks,RegiHi Regi,It is cleared that commit-queue global setting of the NSO cluster has to be set "false" and to sure that the device does not have any existing configuration of the same service.Hence the service owned by the devices will resolve these intermittent issues.You can please close the ticket.Thanks,Dinesh |
CFS goes out of sync with RFS nodes after every service creation or deletion: Hi All,I have NSO LSA cluster with 1 CFS and 2 RFS nodes.I did a RFS sync on CFS node and sync was successful. After that I added L3VPN service from CNC server which got successfully deployed.I check the sync status from CFS node UI and it shows out of sync with RFS nodes.Attaching the screenshot. I wanted to know if user is required to perform sync-from on CFS for all RFS nodes everytime a service is created or deleted.Thanks,Kanchan | Setup Details:CFS: admin/Ovatest123@RFS-62: admin/Ovatest123@RFS-63: admin/Ovatest123@Hi Kanchan,For LSA setup, RFS node will likely always be out of sync with CFS node as there are some internal changes happening on RFS node as part of service provisioning.This is actually why we need the "out-of-sync-commit-behavior" flag to be "accept", so that we can continue to make commits despite the out-of-sync status of RFS node on CFS node.I would suggest to try to provision another service when the CFS node shows RFS node as out-of-sync. The service should be able to be successfully provisioned despite the out-of-sync status. If this works, then everything seems to be working as intended.Thanks,Isaac KimHi Isaac,I am able to provision new services and policies when CFS is not in sync with RFS. So as per our conversation on the other issue described here: , I am concluding that CFS to RFS sync is only required when user adds a new device to RFS node. For other scenarios, it is ok if CFS shows not in sync with RFS, right?Here is what I am seeing on NSO CFS node:admin@ncs> request devices check-syncsync-result { device rfs-62 result unknown}sync-result { device rfs-63 result unknown}Additionally on CFS UI, clicking on check-sync doesn't show any color. is it also expected?Hi Kanchan,From what I understand, RFS node will show as "unknown" sync-state because of the nature of our internal services on RFS node when provisioning services. Despite the "unknown" sync-state, you should still be able to provision services. Yes, you will need to do a sync-from on the CFS node when onboarding new devices on the RFS node. You can assume this is expected behavior unless you run into issues with normal service operations.For NSO Web UI, the status will be same as the NSO CLI check-sync status. So I assume grey is "unknown".Thanks,Isaac KimThanks for the clarification Isaac. Yes I haven't faced the issue in spite of the "Unknown" sync-state. So if this is the expected behavior then we can close this ticket. Thanks for all your help.Perfect, thanks! Please feel free to open another ticket if you face any issues.Thanks,Isaac Kim |
CAT Provisioning page does not populate Service types when FQDN is selected : Setup:Jump host - 10.23.226.188 - root/Cwork123! CW - 192.168.5.50 , 192.168.6.50 - admin/Cnc@1234 - cw-admin/Ovatest123@ NSO L3 HA - 192.168.5.56 , 192.168.6.56 VIP 6.6.6.7 - nsoaz1/Cnc@1234 With Drop 7 , CAT Provisioning page does not populate Service types when FQDN is selected .But it works properly if Active Crosswork IP address is given.Kindly help fix the issue. | Scheduling a debug session with Ajitha to further investigate issue.Followed up with Ajitha on Wed 09-27-23, to see if she still need help regardingthis issue. Currently, she is working with the CAT UI team and will get back to me if additional support is needed. |
L3 NM subservice Error-recovery action: vpn-network-access-id is mandatory field ?: L3 NM subservice Error-recovery action: Is vpn-network-access-id a mandatory field ?Unable to perform error-recovery actions on sub-service (vpn-node) of a L3-NM service without passing dummy "vpn-network-access-id". Behavior is seen in CLI/ nso Restconf/NSO GUI.This is blocking us in validating subservice actions in Provisioning UI.admin@ncs% request l3vpn-ntw l3nm-actions error-recovery vpn-node xrv9k-25 service L3NM-MVPN-STATIC-TREE-700 sync-direction sync-fromValue for 'vpn-network-access-id' (<string>): ########################<ol>Warning #########################You are about to recover a T-SDN service.This will issue a sync on the device.Are you sure you want to proceed? yessuccess truedetail Recovery Complete for L3VPN Internal Services</ol>Restconf:Executing POST on URL with payload: {"sync-direction":"sync-to","service":"0-65008740","vpn-node":"xrv9k-22"}2024-01-16 06:19:32,650 ERROR c.c.u.c.u.NsoDataProvider Error in patchRestConf: {}org.springframework.web.client.HttpClientErrorException$BadRequest: 400 Bad Request: "{<EOL> "ietf-restconf:errors": {<EOL> "error": [<EOL> {<EOL> "error-type": "application",<EOL> "error-tag": "malformed-message",<EOL> "error-path": "/ietf-l3vpn-ntw:l3vpn-ntw/cisco-l3vpn-ntw:l3nm-actions/error-recovery/vpn-network-access-id",<EOL> "error-message": " is not provided"<EOL> }<EOL> ]<EOL> }<EOL>}<EOL>"Is this expected ? | |
PBB-CUSTOME over ODN policy : Trying tocreate PBB-Custom scenario with two end points with underlying ODN policy .Payload ; dry- run attached This is howI define my route policies <l2vpn-route-policy xmlns=><name>L2VPN_NM-PBB-CUSTOM-SRTE-ODN-PE-A-430</name> <color> <id>430</id> <ipv4> <rd>430:430</rd> </ipv4> </color> </l2vpn-route-policy> <l2vpn-route-policy xmlns=><name>L2VPN_NM-PBB-CUSTOM-SRTE-ODN-PE-B-430</name> <color> <id>430</id> <ipv4> <rd>430:431</rd> </ipv4> </color> </l2vpn-route-policy>Whenexecuting dry run, on one side default evpn-route type is applied if evpn-route-type is 1 then set extcommunity color COLOR_430 endifAnd on the other is not applied. NSO: admin/Public1234! | Hi Yevgeny,I checked your setup. This is your l2vpn-route-policy settingsl2vpn-route-policy L2VPN_NM-PBB-CUSTOM-SRTE-ODN-PE-A-430 { color 430 { ipv4 { rd [ 430:430 ]; } }}l2vpn-route-policy L2VPN_NM-PBB-CUSTOM-SRTE-ODN-PE-B-430 { color 430 { ipv4 { rd [ 430:431 ]; } evpn-route-type { route-type [ 1 2 ]; }What you see is expected! It seems the l2vpn-route-policy name is already exist with evpn-route-type!Please clean up your l2vpn-route-policy and retest again.Thanks,LinhHi Yevgeny,I will close this ticket in a few days if there is no update from your side.Thanks,LinhGot it |
Does transport slice support SRv6 in 6.0 release?: Just like to confirm if transport slice supports SRv6 in 6.0 release?Thanks. | Hi Crystal,Yes. We support Srv6 from Slice.Hi Crystal,To clarify, we support Srv6 from forwarding plane policy.ThanksSahithi |
"Preservation" option not seen in NSO service notification: Hi,Service Assurance preservation option is not seen while disabling the monitoring with option "remove" for the first time.Steps:1] Create l2vpn or l3vpn service.2] enable monitoring from CNC UI .3] after some time, disable monitoring from UI .we have preservation option as "remove" by default. do not change anything there and disable the monitoring.in kafka logs , we are not seeing the preservation option at all. RCietf-l2vpn-ntw:l2vpn-ntw/vpn-services/vpn-service=L2NM-P2p-SRTE-712Z{"ietf-l2vpn-ntw:vpn-service":{"vpn-id":"L2NM-P2p-SRTE-712","vpn-svc-type":"vpn-common:t-ldp","vpn-nodes":{"vpn-node":[{"vpn-node-id":"ASR9901-SDN-30","ne-id":"ASR9901-SDN-30","te-service-mapping":{"te-mapping":{"sr-policy":{"policy":"L2NM-EVPN-SRTE-30-712","fallback":"disable"}}},"signaling-options":[{"type":"vpn-common:t-ldp","t-ldp-pwe":{"ac-pw-list":[{"peer-addr":"126.1.1.112","vc-id":"712","mpls-label":753}]}}],"vpn-network-accesses":{"vpn-network-access":}},{"vpn-node-id":"NCS55A2-SDN-112","ne-id":"NCS55A2-SDN-112","te-service-mapping":{"te-mapping":{"sr-policy":{"policy":"L2NM-EVPN-SRTE-112-712","fallback":"disable"}}},"signaling-options":[{"type":"vpn-common:t-ldp","t-ldp-pwe":{"ac-pw-list":[{"peer-addr":"126.1.1.30","vc-id":"712","mpls-label":712}]}}],"vpn-network-accesses":{"vpn-network-access":}}]},"ietf-l2vpn-ntw-cisco-augmentations:service-assurance":{"monitoring-state":"disable","profile-name":"Silver_L2VPN_ConfigProfile system","rule-name":"Rule-L2VPN-NM-P2P-Basic system"}}}bmodify2while checking in NSO UI ., for service assurance, preservation option shows "remove" for twice.while selecting first option "(remove)" and disable the monitoring, we are not seeing the preservation option in the nso notification data,in CAT ui., for service assurance, preservation option shows only one "remove" .. when we try disable monitoring with this option, we are not seeing the nso notification with this option.only after doing "preserve" and disable, we see it.after that again enable the monitoring and disable it with "remove" , we see it.the issue is ,we are not seeing it for the very first time by default. | Hi Arun,1. The reason you're seeing "remove" twice in NSO UI is because the value in parenthesis is the default; therefore, preservation is already set to "remove".2. From the looks of the kafka logs, it looks like the NB is only sending back changes rather than a full query so I would think they're subscribed to the service changes but because preservation is already set to "remove" by default (as shown in your NSO UI pic) this won't count as a change/update on NSO; therefore, you will not see the notification for it.Let me know if you have anymore questions.Thanks,RegiHi reginald,i think there is no problem with subsription, since are see preservation option when we select option as "preserve". RCietf-l2vpn-ntw:l2vpn-ntw/vpn-services/vpn-service=L2NM-P2p-SRTE-712Z{"ietf-l2vpn-ntw:vpn-service":{"vpn-id":"L2NM-P2p-SRTE-712","vpn-svc-type":"vpn-common:t-ldp","vpn-nodes":{"vpn-node":[{"vpn-node-id":"ASR9901-SDN-30","ne-id":"ASR9901-SDN-30","te-service-mapping":{"te-mapping":{"sr-policy":{"policy":"L2NM-EVPN-SRTE-30-712","fallback":"disable"}}},"signaling-options":[{"type":"vpn-common:t-ldp","t-ldp-pwe":{"ac-pw-list":[{"peer-addr":"126.1.1.112","vc-id":"712","mpls-label":753}]}}],"vpn-network-accesses":{"vpn-network-access":}},{"vpn-node-id":"NCS55A2-SDN-112","ne-id":"NCS55A2-SDN-112","te-service-mapping":{"te-mapping":{"sr-policy":{"policy":"L2NM-EVPN-SRTE-112-712","fallback":"disable"}}},"signaling-options":[{"type":"vpn-common:t-ldp","t-ldp-pwe":{"ac-pw-list":[{"peer-addr":"126.1.1.30","vc-id":"712","mpls-label":712}]}}],"vpn-network-accesses":{"vpn-network-access":}}]},"ietf-l2vpn-ntw-cisco-augmentations:service-assurance":{"monitoring-state":"enable","preservation":"preserve","profile-name":"Silver_L2VPN_ConfigProfile system","rule-name":"Rule-L2VPN-NM-P2P-Basic system"}}}bmodify2Selecting remove after that, we can see the remove option also in Notification., RCietf-l2vpn-ntw:l2vpn-ntw/vpn-services/vpn-service=L2NM-P2p-SRTE-712Z{"ietf-l2vpn-ntw:vpn-service":{"vpn-id":"L2NM-P2p-SRTE-712","vpn-svc-type":"vpn-common:t-ldp","vpn-nodes":{"vpn-node":[{"vpn-node-id":"ASR9901-SDN-30","ne-id":"ASR9901-SDN-30","te-service-mapping":{"te-mapping":{"sr-policy":{"policy":"L2NM-EVPN-SRTE-30-712","fallback":"disable"}}},"signaling-options":[{"type":"vpn-common:t-ldp","t-ldp-pwe":{"ac-pw-list":[{"peer-addr":"126.1.1.112","vc-id":"712","mpls-label":753}]}}],"vpn-network-accesses":{"vpn-network-access":}},{"vpn-node-id":"NCS55A2-SDN-112","ne-id":"NCS55A2-SDN-112","te-service-mapping":{"te-mapping":{"sr-policy":{"policy":"L2NM-EVPN-SRTE-112-712","fallback":"disable"}}},"signaling-options":[{"type":"vpn-common:t-ldp","t-ldp-pwe":{"ac-pw-list":[{"peer-addr":"126.1.1.30","vc-id":"712","mpls-label":712}]}}],"vpn-network-accesses":{"vpn-network-access":}}]},"ietf-l2vpn-ntw-cisco-augmentations:service-assurance":{"monitoring-state":"disable","preservation":"remove","profile-name":"Silver_L2VPN_ConfigProfile system","rule-name":"Rule-L2VPN-NM-P2P-Basic system"}}}bmodify2The only problem is for rhe service that is getting created newly with option as "remove" doesnt add the "preservation" option in the notificaion.we can sync up if needed.Thanks,Arun.M.GI did a quick test with L2 and you're correct. The default values are not returning. This seems to be the behavior for NSO. I have noticed that if you explicitly define the default preservation as "remove" in a newly created service the subscription will return the change. Are you able to move forward if you explicitly set preservation in the payload sent to NSO (this includes the default "remove" option as well )?Thanks,RegiI will try to mention explicitly from payload and let u know. our labs are down . if will be back on monday . once it is back, i will check and let you know. Hi Arun,Let me know if you were able to resolve your issue, so I can close this ticket.Thanks,RegiHi Reginald,Tried to create new service with preversation as Remove.attached payload.got the "preservation" option in the notification.snipper below from kafka.RIietf-l2vpn-ntw:l2vpn-ntw/vpn-services/vpn-service=L2NM-EVPN-VPWS-SRTE-604Z {"ietf-l2vpn-ntw:vpn-service":{"vpn-id":"L2NM-EVPN-VPWS-SRTE-604","evi-id":6,"evi-source":604,"evi-target":605,"vpn-svc-type":"vpn-common:evpn-bgp","vpn-nodes":{"vpn-node":[{"vpn-node-id":"ASR9901-SDN-30","ne-id":"ASR9901-SDN-30","te-service-mapping":{"te-mapping":{"sr-policy":{"policy":"L2NM-EVPN-SRTE-30-604"}}},"signaling-options":,"vpn-network-accesses":{"vpn-network-access":}},{"vpn-node-id":"NCS55A2-SDN-112","ne-id":"NCS55A2-SDN-112","signaling-options":,"vpn-network-accesses":{"vpn-network-access":}}]},"ietf-l2vpn-ntw-cisco-augmentations:service-assurance":{"monitoring-state":"enable","preservation":"remove","profile-name":"Gold_L2VPN_ConfigProfile system","rule-name":"Rule-L2VPN-NM system"}}}bmodify2Thanks Arun. Since the issue is resolved. I'll go ahead and close this ticket. |
NSO LSA check-sync behavior when one RFS goes down with a service deployed on the devices present on it : Hi team,I have a question regarding the check-sync behavior on a LSA setup.I have 1CFS (cfs) and 2 RFS nodes(rfs-62 and rfs-63). I deployed one service on devices present only on rfs-62. Once service got deployed successfully, I did a ncs stop on that rfs(rfs-62)What should I expect when I perform check-sync on that deployed service?Thanks,Kanchan | Are you doing a service check-sync or device check-sync?For a service check-sync, you should get an error message something along the lines of<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"><pre>admin@cfs-node> request l2vpn-ntw vpn-services vpn-service EVPN-MP-ELAN check-syncError: Failed to connect to device rfs-node-1: connection refused</pre></div></div>Device check-sync should behavior similarly<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"><pre>admin@cfs-node> request devices device rfs-node-1 config devices device PIOSXR-0 check-sync Error: Failed to connect to device rfs-node-1: connection refused</pre></div></div>Thanks,RegiI was looking for both. Thanks for all the details RegiThanks,KanchanThanks Kanchan. I will go ahead and close this ticket. |
Fetching a single ODN template with restconf: Hi,Trying to get details for a single ODN template.When i try to hit the below URL,Getting all the templates. Need URL to get a single ODN templateThanks,Magesh | Hello,A standard RESTCONF request looks as below to retrieve a single ODN template:curl -is -u admin:admin -H "Accept: application/yang-data+xml" Reached out to customer with the command, awaiting feedback.Customer confirmed that the Restconf command provided in the ticket works and the ticket can be closed.Closing ticket. |
Not able to remove ONC provide : UI+SSH: nso552/Public1234!LocalInstallation:/home/nso552/.0.0 | Could you please provide more details on the issue - like what operation you tried and which exact ONC device?Make sure to delete any other NSO services deployed on the ONC device you are trying to delete before deleting the device.Any updates on this ticket? As mentioned before delete all the NSO services deployed on this ONC device first including the service for subscribing to netconf notifications and then delete the ONC device.Closing the issue assuming no comments received afterward.No updates received so moving the issue to closed.Did you do anything ? |
L2VPN-SRV6 provisioning throws error message for resource pool name.: Hi Team,L2VPN-SRV6 provisioning throws below error message, Looks resource-pool attribute name need to add in the L2VPN-SRV6 payload, Wiki I don't see the payload with resource-pool, Please share the payload for L2VPN-SRV6 with resource pool name." | Hi RageshI have attached the payload for L2VPN-SRV6 with resource pool name.Let us know if we may close the ticket.ThanksThanks Nikhil, You can close the ticket.Closing the ticket as the information has been provided. |
How do we pass ingress/egress values while provisioning: Hi,While Provisioning Slice, how do we pass the ingress/egress values as json?Currently i'm passing like,"ietf-network-slice-service-cisco:qos-catalog": { "L3": { "output-qos-policy": [ { "name": "output-qos" } ], "input-qos-policy": [ { "name": "input-qos" } ] } }Getting Error as below:"error-message": "unknown element: qos-catalog in /ietf-nss:network-slice-services/ietf-nss:slice-service/ietf-nss-cisco:qos-catalog" | Please ignore this. Wrongly opened |
configuration is not pushed to device: 10.195.165.90 - xrd1/xrd1 - NSO 6.0 - M4+L3VPN/L2VPN configuration is not pushed to device. Kindly help | Hello, please let us know the error message being seen when pushing the payload.Hello,We have not received further updates on this ticket.Please let us know error message/setup info to troubleshoot ticket.If no response is received, ticket will be scheduled to close Friday (1/6).Regards,Janaki DuggiralaClosing ticket since no further response has been received from customer. |
NSO Actions on Slicing Services: Can we apply NSO actions on transport slicing services?Actions like Check-SyncSync-FromSync-ToRe-Deploy Dry RunRe-DeployRe-Deploy ReconcileReactive-Re-DeployClean-upCan above the actions supported? | Hi Magesh,Please refer the detailed documentation for more details including actions supported:Regards,Nishad Subair.Thanks Nishad |
Transport Slicing : Need restconf API reference for JSONRPC API: Hi,We need to show available shared slices while provisioning dedicated slice.And able to get available shared slices using below JSONRPC call .URL:https://<nso-ip>:<port>/crosswork/proxy/nso/jsonrpc/get_leafref_valuesPayload:{"jsonrpc":"2.0","id":419,"method":"get_leafref_values","params":{"th":2,"path":"/ietf-nss:network-slice-services/slice-service{}/cisco-nss:shared/slice{}/service-id","skip_grouping":true,"limit":21}} Is it possible to do the same using RESTCONF API. We are not able to give empty braces {} in below restconf,https://<nso-ip>:<port>/crosswork/proxy/nso/restconf/data/ietf-network-slice-service:network-slice-services/slice-serviceThanks,Naveen | Hi Naveenkumar,This restconf command would give you a list of slice-services that exist in NSOcurl --location --request GET 'http://<NSO_IP>:8080/restconf/data/ietf-network-slice-service:network-slice-services/slice-service' --header 'Content-Type: application/yang-data+json' --header 'Authorization: Basic YWRtaW46Q2lzY28xMjMj' --data-raw ' {}'Let me know if this works for youRegards,LinhHi Linh,We need slices whose isolation type is "shared", There is a way in get_leafref_values JSONRPC with below payload,{"jsonrpc":"2.0","id":419,"method":"get_leafref_values","params":{"th":2,"path":"/ietf-nss:network-slice-services/slice-service{}/cisco-nss:shared/slice{}/service-id","skip_grouping":true,"limit":21}}As like JSONRPC , Is there equivalent RESTCONF API available ?Thanks,NaveenThe filter format in Restconf would be different. Please explore these documents to find the one that is working for youThanks,Linh |