input
stringlengths 48
5.67k
| output
stringlengths 0
15.3k
|
|---|---|
Aborted: illegal reference 'core-fp-delete-shutdown-service R1 GigabitEthernet 0/0/0/3 device': this is the regression job :On task 57 : The policy fails and ends up creating zombies.even after clearing zombies and a series of illegal references and deleting polices, it always ends up reaching this state :admin@ncs>Aborted: illegal reference 'core-fp-delete-shutdown-service R1 GigabitEthernet 0/0/0/3 device'Could you please check what's going wrong where ?Or please clearly mention what are the steps to perform to clear zombie and illegal reference in case of NSO LSA setup and which step to perform on PFS and CFS .showtech for RFS :/auto/ncahi/Users/mesarma/cwork_proj/8june/data_060822_153530.tgzshowtech for CFS :/auto/ncahi/Users/mesarma/cwork_proj/8june/data_060822_153722.tgz | Hello Meenakshi,We have received several queries about this issue.It is very important for us to know the steps you took prior to this error. Would you be able to describe the steps you took prior to this error to the best of your ability? This way we can try to reproduce and RCA the issue.Thanks,Isaac KimHello Meenakshi,From your console logs for Task 57, I can see that you are making an out-of-band config change on device prior to creating a L2 service with no device sync in between. This will definitely cause out-of-sync error when creating the L2 service. If you take a look at the return string for the error, you can see the message states device R1 is out-of-sync.Also I do not see any error message with Aborted: illegal reference 'core-fp-delete-shutdown-service R1 GigabitEthernet 0/0/0/3 device'. Where do you see this?So far, from what I can see, there is nothing that occurred in your logs that is not expected.Please update with more information.Thanks,Isaac KimHello Meenakshi,For more information on handling zombies, please check : For more information on error recovery, please check : Thanks,Isaac KimHello Meenakshi,Please note, as mentioned in the wiki link above for zombie handling, NSO's native zombie actions, such as re-deploy and resurrect, are not supported by TSDN CFP.Instead please follow the guide on the wiki link for zombie handling. Typically for zombies, error recovery action is used when device is reachable and out-of-sync, cleanup action is used when device is unreachable or reachable and in-sync. For more information on these actions, please explore the wiki page.Thanks,Isaac KimHello Meenakshi,I believe we have been able to provide information on proper zombie handling and recovery options. It seems like we have been able to address your issue. If there is no reply in few days, I will close this ticket.Thanks,Isaac Kimyes, understood the zombie handling. Kindly close the ticket. |
RON CFP Inter-link validation is hard: Hi,After many tests with the RON CFP by different teams, the inter-links are proven to be very problematic.We would like to ask for some inter-layer-link actions that would support operations.Example operations (all read-only) are:1- validate all inter-layer-link: Make sure that the UUIDs or "optical-add-drop" exist2- list-all-SIPs: for a given TAPI device, list all existing SIP UUIDs and its correspondent inventory data in the format that should be input for "inter-layer-link" configuration.We think these actions and similar actions will help on the most common problem with RON CFP installation.Regards,Roque | Hi Roque,Thanks for reaching out to us and providing the feedback. We will discuss these enhancement requests with the team and get back to you on this.Regards,Linmaohi, any news?Hi Roque,Sorry for the late reply. We have discussed on this internally and we are planning to add 2 new actions to RON CFP:<ol>An action to validate all entries in inter-layer-link, this action will return which entry is invalid or all entries are valid;An action to print all SIPs/optical-add-drop from a give TAPI device in the expected format for inter-layer-link.</ol>The tentative release to include these two actions would be RON 2.0.0-M5 coming in Apr. 15. We will also keep you posted for any updates.ThanksHi Roque,I'm closing this ticket as we have created internal tickets for the enhancement. In M5 (Apr. 15) or M6 (May. 13) you should be able to see in the release note that the new actions have been added.Enhancement will be included inM5 (Apr. 15) or M6 (May. 13). |
Not able to see the real stats from devices after deploying y1731 service: With NSO 5.5.2.7 + M6 installed, deployed the Y1731 service (please find the attachment for the payloads), after while all the stats still remaining as "0".The similar payloads were deployed on NSO 5.5.2.3 + M4 env, it was able to get the real stats. | Hello Jason, do you by any chance have the original payloads from your M4 setup? If so, please upload them here!Jason, please also share the output from the following commands given on the device.```RP/0/RSP0/CPU0:PE1#show ethernet sla configuration-errors``````RP/0/RSP0/CPU0:PE1#show ethernet sla statistics``````RP/0/RSP0/CPU0:PE1#show ethernet cfm peer meps```Here are the payloads for NSO5.5.2.3 with M4, after service deploy, we did manual load merge of y1731_device_config_override.xml Hi Jason, can we also get access to your setup?Hi Reginald, I did check "show ethernet cfm peer meps" on the same devices last night it was in Ok (>) state, even that, I did not see the real stats, means the output of "show ethernet sla statistics" looks were the same (no real stats). But I saw "show ethernet cfm peer meps" turn to error state today. The NSO info: 172.20.200.112 admin/Cwork123! service name "new-l2nm-p2p-sr-1"Hello Jason, we checked your NSO CLI instance and we saw that your "new-l2nm-p2p-sr-1" plan is in failed state with out-of-sync device. Please correct this first and check Y1731 probe statistics. Hi Isaac, I did the device sync, and checked the Y1731 probes, it looks the same. Would you please check? Thank.Hello Jason,After trying few things, we found that your frame size of 2000 exceeded your Interface MTU of 1500. Once we reduced frame size to 1000 connection issues were resolved. We also noticed that changing delay version to 1 fixed the 100% dropped packets. This seems to be specific for NCS5501 device.Apart from this, we confirmed that NSO configuration is correctly pushed to device in accordance to config governance defined schema. As such, NSOs role was successfully completed. Device level logic and configuration should be analyzed by subject experts (such as why delay version 0 is causing issues on NCS5501, is there an expectation to use delay version 0?)Also please note, your previous payload for M4 used frame-size of 1000 which likely indicates why you did not face connectivity issues.Thanks,Isaac KimHi Isaac, I made the changes as you suggested below, and re-deploy the service, but I still could not the probes coming...Hi Jason,I took a look at your setup. As Isaac mentioned were unable to get delay version 0 to work; however, we were able to get delay statistic working with version 1. If you need delay version 0 to work, then please provide the expected device configuration that you need.Thanks,Regi |
Y.1731 device config with prefix L2NM-: Can we remove this prefix L2NM- from the device config cfm-domains-domain-services-service? ethernet-features { cfm { domains {domain md-1 {services {service L2NM-new-l2nm-p2p-sr-1 {continuity-check-interval { - ccm-interval 1s; - }cross-check {cross-check-meps { - cross-check-mep 2; - }}service-properties { - service-type p2p-cross-connect; - group-name new-l2nm-p2p-sr-1; - switching-name new-l2nm-p2p-sr-1; - short-ma-name-format number; - short-ma-name-number 100; - }}}domain-properties { - level 0; - mdid-format null; - }} } } }</ul> | What issue is the prefix causing? The prefix is used to determine whether the config was initially created by which serviceWhy we change the "service" Id? should it match to the "vpn-service"-"vpn-id" in service configs? In this case it is "new-l2nm-p2p-sr-1".The device configuration is pushed by the internal service, so it pick up the internal service name there. We do this concatenation to determine if the config was pushed by L2NM services or directly from flat-L2vpn service.Why we need to determine this on the device configs level? Who will consume this device config level info (it is pushed by IETF or Flat model)? From AA perspective, it will be more straight forward to match the cfm "service id" on device config to the "vpn-id" in the L2NM service config.Please file a CDETs. We can consider removing the concatenation.Closing ticket, since this issue is now handled by CDETs, |
Fail to get NSO 5.7 installer with 401 Unauthorized error: Use the following command to get NSO installer, but fail with 401 error. Can you give me the permission to get the files?root@nso-147:~/nso57# wget --no-check-certificate -<del>2022-02-13 18:27:09</del>- Resolving earth.tail-f.com (earth.tail-f.com)... 10.147.45.20Connecting to earth.tail-f.com (earth.tail-f.com)|10.147.45.20|:8443... connected.WARNING: cannot verify earth.tail-f.com's certificate, issued by CN=HydrantID Server CA O1,OU=HydrantID Trusted Certificate Service,O=IdenTrust,C=US: Unable to locally verify the issuer's authority.HTTP request sent, awaiting response... 401 Unauthorized | Hi Crystal,I will forward this request to someone who has access to these permissions.Will update this ticket if there is any progress.Thanks,Isaac KimHi Crystal,It seems like earth.tail-f uses CEC ID and Password for access.This means you would be able to access the link using:wget --user <CEC USER ID> --password <CEC USER PASSWORD> <TAIL-F EARTH LINK> --no-check-certificateI have tested this and it seems to work for me. Please let me know if you have any other questions or concerns.Thanks,Isaac KimThanks Isaac,The command works for me. There is one extra thing that I need to do which is to put "" in front of the special character in my password. Thanks again for your timely response and the solution.-Crystal |
NSO session getting expired when clicking on bgp routing policy under L3VPN: NSO session getting expired when click on bgp routing policy under L3VPN service.Setup details 10.22.179.240 - xrd1/Cwork123!Same issue seen for other RSVP tunnel | Hi Murali,This was a known NSO GUI bug for NSO 6.X engineering builds. As mentioned in the past, we do not recommend doing any service provisioning or service config modification on NSO GUI until official NSO 6.X build is released.For the GUI bug itself, we have already created a platform RT to resolve the issue and platform engineers are working on a solution.As we have already instructed in the past to avoid NSO GUI service provisioning for NSO 6.X engineering builds, I will close this ticket as invalid.Thanks,Isaac KimNSO 6.X ENG WebUI is known to be unstable. This is one of the currently known failure cases. Invalid as we have already instructed all users to avoid NSO WebUI for service provisioning due to instability. |
NSO L3NM FP VPN endpoint port-id attribute does not supports Tunnel-IP: I am trying to provide a Tunnel interface while configuring L3VPN. Looks like the port-id attribute is not allowing the type tunnel-IP. As per the yang, it seems string.ietf-l3vpn-nm --> ietf-l3vpn-ntw.yang(container vpn-network-accesses -> leaf port-id is referring -> l3vpn-svc:svc-id from [email protected]) Inside the yang file : [email protected] the leaf svc-id is declared as below. typedef svc-id { type string; description "Defines a type of service component identifier."; }Also observed Tunnel-interface is not provided as an option in the dropdown of CNC UI (Services ; Traffic EngineeringProvisioning -> L3VPN/L3vpn-Service)Setup Details:==========CNC Versions: Crosswork Image Version: release-4.4.0 (Build 250) and Crosswork Infrastructure Version: 4.4.1 (Build rc.3)COE Version: v4.1.1-rc.5+build.10NED Version: cisco-iosxr-cli-7.40admin@ncs# show ncs-state | include versionncs-state version 5.7.6admin@ncs# show packages package package-versionNAME PACKAGE VERSION-----------------------------------------------aws-common-actions 2.3.1aws-infoblox-provision 1.9.2aws-pedc-tunnel-actions 1.3aws-pedc-tunnel-service 2.1aws-tunnel-actions 2.2aws-tunnel-service 2.1cisco-aa-service-assurance 4.1.0cisco-cnfo 1.1.0cisco-flat-L2vpn-fp 4.1.0cisco-flat-L2vpn-fp-internal 4.1.0cisco-flat-L3vpn-fp 4.1.0cisco-flat-L3vpn-fp-internal 4.1.0cisco-ios-cli-6.77 6.77.9cisco-iosxr-cli-7.40 7.40.1cisco-iosxr-cli-7.46 7.46.4cisco-iosxr-nc-7.6 7.6cisco-iosxr-nc-7.7 7.7.1cisco-rsvp-te-fp 4.1.0cisco-sr-te-cfp 4.1.0cisco-sr-te-cfp-internal 4.1.0cisco-tsdn-core-fp-common 4.1.0cnfm-nc-1.1 1.1config-inventory 1.2core-fp-common 1.30.0core-fp-delete-tag-service 1.0.5core-fp-plan-notif-generator 1.0.6custom-template-utils 2.0.9cw-device-auth 4.4.0cw-dlm-fp 4.4.0-nso-5.7.6flat-l2vpn-multi-vendors 4.1.0flat-l3vpn-multi-vendors 4.1.0ietf-l2vpn-nm 4.1.0ietf-l3vpn-nm 4.1.0ietf-te-fp 4.1.0lsa-utils 1.0.1resource-manager 3.5.7sr-te-multi-vendors 4.1.0 ========================================================admin@ncs# show running-config devices device 20.0.1.14 | de-select configdevices device 20.0.1.14address 20.0.1.14device-type cli ned-id cisco-iosxr-cli-7.40state admin-state unlocked! | Hi Srinivasa,Below are the port types we support in L3NM FP:Bundle-Ether,BVI,FiftyGigE,FortyGigE,FourHundredGigE,HundredGigE,Loopback,TenGigE,TwentyFiveGigE,TwoHundredGigE,,GigabitEthernet,EthernetWe have check to not add other port ids.Yeah i noticed that it allows only the type : Ether,BVI,FiftyGigE,FortyGigE,FourHundredGigE,HundredGigE,Loopback,TenGigE,TwentyFiveGigE,TwoHundredGigE,,GigabitEthernet,Ethernet but not Tunnel-ip. But it was declared as string. Logically it should allow. I guess you guys are validating inside package code.Could you please let us know whether the support for Tunnel-ip is going to be added or not? We have a dependency on this type: Tunnel-Ip. In case we want to customise, Is there any way to do that without impacting the visualization on the topology? Any leads on customisation would be a great help to us. Hi Srinivasa,We do not have any requirement to add tunnel-ip in CNC 6.0. If you believe it needs to added, please create an AHA ticket for CFP to be prioritized by PLM.I am not sure if the customization would be straightforward. First step is to remove the pattern check in the yang, re-compile the package and verify if the tunnel ip is being accepted and configured on the device.ThanksSahithi |
Does TSDN5.0.0 supports Transport Slicing and Circuit Style policy on XE devices: Does NSO6.1 TSDN5.0.0 supports Transport Slicing and Circuit Style policy on XE devices? | Hi Crystal,Please check the TSDN 5.0.0 wiki in detailed documentation for both the features on supported devices.From my understanding, both of the features are not currently supported on XE devices.CS SR is supported only on 7.9.1.Let us know if there is an issue in the wiki.ThanksSahithi |
NSO Integration Status - NETCONF port: From: Kavipriya Venkatraman -X (kavipven - INFOSYS LIMITED at Cisco) <[email protected]> Sent: Tuesday, September 13, 2022 10:57 AMTo: Nirali Vasoya (nvasoya) <[email protected]>; Jason Wycoff (jwycoff) <[email protected]>Cc: infy-crossworkeks-dev(mailer list) <[email protected]>; Rajesh Tupakula -X (rtupakul - INFOSYS LIMITED at Cisco) <[email protected]>; Srinivas Thirkateh -X (sthirkat - INFOSYS LIMITED at Cisco) <[email protected]>Subject: NSO Integration StatusHi Nirali/Jason,We are testing the EKS NSO Integration on the CW Setup. We have created the NSO setup on EKS and while adding nso in providers in cw setup ui, we see that the HTTPS(8888) and HTTP(8080) ports are reachable but NETCONF port (2022) is not reachable. We are trying to resolve the unreachable issue currently.Thanks and Regards,Kavipriya V | Hi Kavipriya,Thank you for reaching out.If you need assistance with T-SDN Core Function Pack on EKS, please file ticket HERE.For now, I have filed a ticket on your behalf here: I have a few questions to understand the issue better.1.What CFP helm chart milestone release are you using for testing? Did you make any updates to the released chart?2.What was the helm install command used to bring up the instance?3.Are you using AWS NLB to reach NSO?4.Generally crosswork components talk to NSO on JSON-RPC and RESTCONF over port 8080 only and that is what is exposed by default. We did not expose port 8888, hence my question, was the chart altered in any way to expose this port? Thanks,NiraliHi Nirali,Thank you for the responsewe have referred this document for installing NSO on eks 1) CNC CFP on EKS 1.0.0 - M3 Release 2) helm install cnc-test cnc-cfp --set persistence.enabled=false --set image.repository=148213121008.dkr.ecr.us-east-1.amazonaws.com/nso-cnc-cfp --set service.annotations."service.beta.kubernetes.io/aws-load-balancer-type"=external --set service.annotations."service.beta.kubernetes.io/aws-load-balancer-nlb-target-type"=ip --set service.annotations."service.beta.kubernetes.io/aws-load-balancer-scheme"=internet-facing 3) yes, aws Nlb is connected with the setup to reach nso 4) sorry 8888 port is also unreachable (only 8080 port is exposed and reachable) but team said that NETCONF port and HTTPS port have to be reachable so that in device NSO will be sync Now devices are not connected to NSO(not in sync) Im not able to access the ticket u have providedThanks and Regards, Kavipriya VHi Nirali,Update on the NSO Integrationhttps was disabled so we made changes in configuration to enable httpsNow https,netconf are reachable but still NSO we were not able to register with device-sync is not happeningDoes it requires any additional configuration separately for sync up?+ AlokAlok, could you please provide access for Kavipriya to access JSD?Hi Kavipriya,Thanks for the details. From what I see below, you are trying to access NSO via NETCONF over NLB and it is not reachable. This is expected because the helm chart we have for NSO doesnt expose netconf on K8s service. Also, I believe the way https is being accessed is incorrect here, the access should be via NLB with certificate management done by AWS.We can update the helm chart to expose more ports in the load balancer service to get this connectivity. I can help you with that. I will send an invite for us to work on this.Thanks,NiraliHi Nirali/Alok,Thanks, I have got the access for the JSD issue <> .Thanks and Regards,Kavipriya VThanks for joining the call. Below are the meeting notes and future steps:<ol>NSO Helm chart doesnt expose netconf port and this is needed for CDG-NSO integration. This will be fixed in M5 release.CNC doesnt have support for FQDN yet, so NSO pod is being accessed with Pod IP rather than via NLB. For this reason, direct https was enabled on NSO. This is not how it is envisioned though. Eventually, SSL termination will be on NLB, and internal communication will be over http.Adding devices to NSO via DLM doesnt work as TSDN CFP container image doesnt have DLM and other packages developed outside CFP team. With M4 release, there is a provision to add/update custom packages into existing TSDN container image. Infy team to follow the document and try it out.</ol>Thanks,Nirali |
ASR9K devices are not sync with NSO and throws error "Bad device configuration: ({case_clause,not_found})": Hi -ASR9K devices are not synced with NSO, SSH configuration looks fine and tried generating a new crypto key on devices, still seeing the same issue.Seeing the below error message during the sync operation. Please take a look.admin@ncs(config-device-ASR9K-1)# ssh fetch-host-keysresult failedinfo ASR9K-1: Bad device configuration: ({case_clause,not_found})admin@ncs(config-device-ASR9K-1)# *** ALARM configuration-error: ASR9K-1: Bad device configuration: ({case_clause,not_found})admin@ncs> show devices listNAME ADDRESS DESCRIPTION NED ID ADMIN STATE----------------------------------------------------------------------------AG1 192.168.6.14 - cisco-iosxr-cli-7.40 unlockedAG2 192.168.6.15 - cisco-iosxr-cli-7.40 unlockedAG3 192.168.6.16 - cisco-iosxr-cli-7.40 unlockedAG4 192.168.6.17 - cisco-iosxr-cli-7.40 unlockedASR9K-1 192.168.6.28 - cisco-iosxr-cli-7.40 unlockedASR9K-2 192.168.6.29 - cisco-iosxr-cli-7.40 unlockedSetup details:RFS1- 172.29.106.132Device- 192.168.6.28 | Hi Ragesh,I checked the setup and found that theSSH Algorithms public-key configuration was missing for the devices mentioned and hence the error was coming.I have added the configuration forASR9K-1 and it seems to be working fine now.Please update the configuration forASR9K-2. Refer to the below url to set the missing configuration.Let us know if the issue is resolved and we can close the ticket.Thanks, NikhilThanks Nikhil, Issue fixed on the setup after adding the below ssh config on NSO.set devices global-settings ssh-algorithms public-key [ ssh-ed25519 ecdsa-sha2-nistp256 ecdsa-sha2-nistp384 ecdsa-sha2-nistp521 rsa-sha2-512 rsa-sha2-256 ssh-rsa set devices device ASR9K-2 ssh-algorithms public-key [ ssh-rsa ]TheSSH Algorithms public-key configuration was missing for the devices mentioned and hence the error was coming.The issue was resolved after adding the configuration. |
API request to make update for L2vpn Route Policy Tag: I am trying to update L2vpn Route Policy Tag via API. Here is the method, URL and payload that I use. But it failed. Not sure if my URL or payload is incorrect. Please share the correct info. Thanks in advance.Method: PATCHURL:======https://<tt>cat.cw.host</tt>:<tt>cat.cw.port</tt>/crosswork/proxy/nso/restconf/data/cisco-l2vpn-routing-policy:l2vpn-routing-policy/defined-sets/tag-sets/Paylod:======{ "tag-set": [ { "name": "COLOR_250", "tag-value": [ 251 ] } ]}Error:===={ "ietf-restconf:errors": { "error": [ { "error-type": "application", "error-tag": "malformed-message", "error-path": "/cisco-l2vpn-routing-policy:l2vpn-routing-policy/defined-sets/tag-sets/tag-set", "error-message": "too many /l2vpn-routing-policy/defined-sets/tag-sets/tag-set{COLOR_250}/tag-value, 2 configured, at most 1 must be configured" } ] }}-Crystal | As discussed, this would be the right behavior for L2 and the limitation should be applied to L3 and L2 behavior is as expected.This is correct behavior for L2 VPN route policy.Please confirm the PATCH request failure is expected for L2 and L3 Route Policy Tag. I found out use PUT request, the update is successful. Like to confirm we support PUT for updating L2 and L3 Route Policy Tag instead of PATCH method. It is the same behavior for other Route Policy items such as source-prefix, destination-prefix...etc.Thanks.-Crystal |
Need Modified prepackaged NSO service pack for 5.7.5.1 release: Hi team, Received modified flat L3VPN NSO service pack for Flat L3VPN 5.7.2.1 earlier. Would you please share the same modified flat L3VPN package for 5.7.5.1 release.Previous communication mail: Build with Custom FP Changes - Sahithi.Model change:list address-family { leaf maximum-prefix { tailf:info "<32-10000000> - IPV4 Maximum Prefix"; when "../address-family = 'ipv4'"; type uint32 { range "32..10000000"; } default 32;}Thanks | Hi Ajitha,Your custom FP build with NSO 5.7.2.1 should work with NSO 5.7.5.1 since both have same major NSO version.Give it a short and let us know the outcome.Thanks,LinhHi LinhI tried this already and received error message for "flat l3vpn internal" entry - "show platform oper-status"Setup: 10.195.165.90 - xrd1/xrd1Would you please have a look. Error message:xrd1@ncs> show packages package oper-status packages package cisco-flat-L3vpn-fp-internal oper-status file-load-error oper-status error-info [ "None of the supported-ned-ids are loaded" ]I logged on your set up and see cisco-flat-L3vpn-fp-internal is up. Please see the attachedSorry for typo on setup details. Setup: 10.195.165.75 - xrd1/xrd1You have a wrong ned-id in package-meta-data of ncs-5.7.2.1-cisco-flat-L3vpn-fp-internal-EXAMPLE-4.0.0.tar.gz<supported-ned-id xmlns:cisco-iosxr-cli-7.38="http://tail-f.com/ns/ned-id/cisco-iosxr-cli-7.38">cisco-iosxr-cli-7.38:cisco-iosxr-cli-7.38</supported-ned-id> I changed it to 7.39 which is exist on your setup and tar package back with the same package name. The package is up nowHi Linh/Sahithi,Received below validation error while trying the NED. Kindly suggest Validation failederrors: reason: Python cb_validate error. STATUS_CODE: TSDN-L3VPN-408 REASON: Router NED not supported CATEGORY: user SEVERITY: ERROR Context [name = Router NED not supported: cisco-iosxr-cli-7.39:cisco-iosxr-cli-7.39, message = Missing dynamic device mapping state = {'Device': 'NCS-3', 'Service': 'L3VPN_FLAT-IGP-IPV4-120', 'Device NED ID': 'cisco-iosxr-cli-7.39:cisco-iosxr-cli-7.39'}] . paths: /cisco-flat-L3vpn-fp-internal:flat-L3vpn{L3VPN_FLAT-IGP-IPV4-120 NCS-3}. path: /cisco-flat-L3vpn-fp-internal:flat-L3vpn{L3VPN_FLAT-IGP-IPV4-120 NCS-3} |
Incorrect configuration of ASR9903 on ron-ml 1x100G service creation: The configuration is a ron-ml service with rate 1x100G between a cisco 8201 and an ASR9903While the configuration works successfully in 8201, where also in 1x100G mode the Hu interface is identified with sub-interface index 0, on ASR9903 the Hu interface is not a sub-interface. So actually, the plan is completed and green, but the configuration is not applied at the router since the Hu interface do not exist.Following is the commit performed by the RON FPRP/0/RP0/CPU0:ron-asr9903-1#sh configuration commit changes 1000000282Sun Aug 28 06:12:36.754 PDTBuilding configuration...!! IOS XR Configuration 7.7.1controller Optics0/0/1/4transmit-power -45fec OFECdwdm-carrier 100MHz-grid frequency 1937000DAC-Rate 1x1.25!interface HundredGigE0/0/1/4/0ipv4 address 100.1.4.9 255.255.255.254!interface preconfigure HundredGigE0/0/1/4/0no shutdown!endWhile if we check for Hu interface it does not have the sub-if index:RP/0/RP0/CPU0:ron-asr9903-1#sh interfaces hundredGigE 0/0/1/? 0/0/1/0 HundredGigE Interface Instance 0/0/1/1 HundredGigE Interface Instance 0/0/1/10 HundredGigE Interface Instance 0/0/1/11 HundredGigE Interface Instance 0/0/1/2 HundredGigE Interface Instance 0/0/1/3 HundredGigE Interface Instance 0/0/1/4 HundredGigE Interface Instance 0/0/1/5 HundredGigE Interface Instance 0/0/1/6 HundredGigE Interface Instance 0/0/1/7 HundredGigE Interface Instance 0/0/1/8 HundredGigE Interface Instance 0/0/1/9 HundredGigE Interface Instance R/S/I/P/B or R/S/I/P Forward interface in Rack/Slot/Instance/Port/Breakout format or R/S/I/P formatThe correc tocnfiguration that NSO should send in this case for 1x100G to ASR9903 is:interface HundredGigE0/0/1/4ipv4 address 100.1.4.9 255.255.255.254!interface HundredGigE0/0/1/4no shutdown! | Hi Roberto,CFP follows this table for the logic to determine whether to config the main interface or a sub-interface (quoted from RON 2.0 SDS section 3.8.4):<div class='table-wrap'><table class='confluenceTable'><tbody><tr><td class='confluenceTd'> </td><td class='confluenceTd'></td></tr><tr><td class='confluenceTd'></td><td class='confluenceTd'>HundredGigE 0/0/1/0/0</td></tr><tr><td class='confluenceTd'></td><td class='confluenceTd'>HundredGigE 0/0/1/0/0HundredGigE 0/0/1/0/1</td></tr><tr><td class='confluenceTd'></td><td class='confluenceTd'>HundredGigE 0/0/1/0/0HundredGigE 0/0/1/0/1HundredGigE 0/0/1/0/2</td></tr><tr><td class='confluenceTd'></td><td class='confluenceTd'>FourHundredGigE 0/0/1/0/0</td></tr><tr><td class='confluenceTd'></td><td class='confluenceTd'>HundredGigE 0/0/1/0/0HundredGigE 0/0/1/0/1HundredGigE 0/0/1/0/2HundredGigE 0/0/1/0/3</td></tr></tbody></table></div>So far the only exception is that for 1x400G transponder case CFP will only configure the main interface. Could you please confirm if for ASR 9903 (A9903-20HG-PEC) we need to make another exception in 1x100G transponder case? Is that only forA9903-20HG-PEC?Thanks,LinmaoHi Roberto,Just a gentle reminder.Could you please confirm if only for ASR 9903 (A9903-20HG-PEC) we need to make an exception in 1x100G transponder case where NSO should configure the main interface instead of sub-interface?Thanks,LinmaoRON 2.0-M9 which has the fix has been released. So, I'm closing this ticket. |
Dynamic Tree SID configuration for IOS-XR: Hi,I'm the manager of EPN ; Crosswork's Tier4 testing lab and, we've recently tried bringing up Tree SID configuration in our lab for testing on CW 4.3. We require some assistance regarding dynamic Tree SID configuration (we've managed to properly configure the static tree).Could anyone one from the CFP team contact us for that?Thanks,Lior A. | Hi Lior,We would be supporting dynamic Tree SID from CNC 5.0 release. Below is the config, we are implementing for Dynamic Tree SID from CFP side which does not include PCE config.ThanksSahithi |
Failed to connect Device error shown in CNC - NSO shows different IP : In CNC the following error message shown for one the device - Major - NSO Sync-from/to failed. NSO Reported Error: Failed to connect to device PE-A: connection refused: NEDCOM CONNECT: No route to host (Host unreachable) in new stateOn checking further found the different IP configuration information in NSO than the one configured in device. Checked the device configuration all looks fine. Setup detail - CW - 10.22.179.235 - admin/Cwork123!NSO - 10.194.60.130 - xrd1/Cwork123! | Hi Murali, apologies for delay. I will take a look today~Hi Murali,After a quick look at your NSO configuration, it seems like PE-A is defined as192.168.5.11. Im not sure why CW GUI is showing 192.168.5.21.admin@ncs> show devices listNAME ADDRESS DESCRIPTION NED ID ADMIN STATE----------------------------------------------------------------------------P-BOTTOM-LEFT 192.168.5.26 - cisco-iosxr-cli-7.43 unlocked P-BOTTOM-RIGHT 192.168.5.27 - cisco-iosxr-cli-7.43 unlocked P-TOP-LEFT 192.168.5.24 - cisco-iosxr-cli-7.43 unlocked P-TOP-RIGHT 192.168.5.25 - cisco-iosxr-cli-7.43 unlocked PE-A 192.168.5.11 - cisco-iosxr-cli-7.43 unlocked PE-B 192.168.5.22 - cisco-iosxr-cli-7.43 unlocked PE-C 192.168.5.23 - cisco-iosxr-cli-7.43 unlocked SR-PCE 192.168.5.28 - cisco-iosxr-cli-7.43 unlocked When executing check-sync on PE-A, it showsadmin@ncs> request devices device PE-A check-syncresult errorinfo Failed to authenticate towards device PE-A: Unknown SSH host keyI manually updated ssh host keys usingadmin@ncs> request devices fetch-ssh-host-keysfetch-result {...After this I executed a check-sync on PE-A again and it showsadmin@ncs> request devices device PE-A check-syncresult errorinfo Failed to connect to device PE-A: connection refused: NEDCOM CONNECT: Authenticate: Exhausted available authentication methods. Server allowed: [ publickey password ] in new stateI am not sure how these devices were setup, but prior to running CNC or NSO operations, I would make sure that all devices are correctly onboarded.From our testing, device operations and connectivity on NSO 6.1 is working fine. These errors you are seeing are likely due to your setup or onboarding bootstrap config. Please make sure you are able to ssh into each device using the authgroup credentials from XRDevices.Thanks,Isaac KimHi IsaacI haven't configured that IP address 192.168.5.11 to my device. It was working fine earlier configured IP for PE-A device is 192.168.5.21. I have attached screen shot of devices onboarded and configured IP address.I checked completely and not sure how and why PE-A devices shows different IP address rather than one configured in device.On same NSO or CNC I was able to provision services and policies earlier.Hi Murali,I cannot think of any scenario where a device will be onboarded with a different IP from what was configured. It could potentially be that certain changes were not committed.If you would like, we can get on a call to try to resolve this.Thanks,Isaac KimHi Isaac,Sure we can discuss over the call to resolve this.Regards,Murali BGot on call, but decided we need CNC instance to be up to continue with RCA. No relevant info found from NSO logs.Murali to reach out when he has another CNC instance and able to reproduce issue.If you are not able to reproduce, please let me know here as well.Thanks,Isaac KimGot on another call, found that there is old DLM config from cloned NSO instance which could be source of issue. Could not reproduce on CNC UI. We will keep watch again, but next time we clone NSO and add to a new CNC instance we should try to cleanup old DLM config.Check for old DLM config:1.enter NSO CLI2.enter config mode ("configure")3.show dlm config ("show cisco-dlm")4.delete any stale entries ("delete cisco-dlm crosswork-vm <CW IP>")5.commit changes ("commit")6.continue with onboarding NSO to CNCIf Murali faces this again, we will reconvene and investigate further.If we dont face this for some time (assuming we follow above steps), I think we can assume this issue is resolved.Thanks,Isaac KimHi Murali, I believe this ticket has been resolved.To prevent the ticket from being open too long, I will mark this as resolved.If you face this issue again, please open a new JSD and reference this JSD for context.Thanks,Isaac Kim |
NSO LSA - CFS crashed while trying to scale up the services- NSO 6.1 , TSDN 5.0.0 M5+ patch Eng build 2: Hi,Setup: 172.29.106.131 ( CFS) 172.29.106.132 ( RFS1)172.29.106.133 ( RFS2)NSO LSA installed with NSO 6.1 , TSDN 5.0.0 M5+ patch Eng build 26.1_230109.073843810.4384ecc7db9anso-6.1_230109-tsdn-5.0.0-M5From CW proxy API, with 5 concurrent users, trying to scale services in 5 pair of different endpoint. It is simple l2vpn p2p service. afte some around 450 services, CFS crashed.nso@nso-172-29-106-131:~$ ncs_cliFailed to connect to servernso@nso-172-29-106-131:~$CFS ( NSO provider) went unreachable in CW. hence all my services provisioning started failing.Collected logs and logs present at CFS device 172.29.106.131/home/nso/data_011923_103547_dirsetup is in issue state.please ping me for setup details., i can unicase the credentials. please use it for Read-only.Thanks,Arun.M.G | Hi Arun,Please try the test using this build :Also please enabled coredump on all your nodes CFS and RFSs .1. ulimit -S -c unlimited#enable core dump permanently, add following line in /etc/security/limits.conf to update system limit #to verify ulimit -c ,close all sessions and open new then new limit will be shown. 2. soft core unlimited#settings up coredump path3. sudo sysctl <del>w kernel.core_pattern=/tmp/core</del>%e-%s-%u-%g-%p-%torsudo sysctl -w kernel.core_pattern="/tmp/%e_core_dump.%p"(based on requirement )#You can make core dump file path changes permanent, by adding following line in /etc/sysctl.conf4. kernel.core_pattern="/tmp/core-%e-%s-%u-%g-%p-%t"orkernel.core_pattern="/tmp/%e_core_dump.%p"Significance of format specifier for coredump:<ol>%e The process or thread's comm value, which typically is the same as the executable filename (without path prefix, and truncated to a maximum of 15 characters)%i TID of thread that triggered core dump, as seen in the PID namespace in which the thread resides.%p PID of dumped process, as seen in the PID namespace in which the process resides.%s Number of signal causing dump.</ol>#To test crash to generate coredump5. kill -11 $$#Verify if coredumps get generated :ls -lart/tmp/ | grep core<del>rw</del>------ 1 admin1 admin1 2080768 Oct 6 11:18 bash_core_dump.21904#for ncs process crashkill -s SIGSEGV $(pgrep ncs.smp)#to verify ulimit -c ,close all sessions and open new then new limit will be shown.Before next run please enable and verify if coredump crash are getting generated .After crash please share coredump crash it will help platform team to analyze the failure.Thanks PriyankaWorking on CDETS |
provisioning not reflected till 'Sync to': I am using REST API to provision SR TE policy in cluster setup. i am using no-networking = false, so that config is pushed to device. After the api is executed through shell script, SR policy is available in cluster but not in device. After 'Sync to' the config is available in device. Should i modify any other parameter in the script, so that config is pushed to device after the script execution. NSO is available in 172.20.63.132 - cnctest/Ovatest123@device in RFS - 172.20.63.148 - xrv9k-4 | Hello, I looked in all of the RFS for a device calledxrv9k-4 and couldnt find one.Attached screenshots.Please provide more information on this ticket for further troubleshooting.Regards,Janaki DuggiralaHi Janaki,There is a typo in device name. Could you please check "xrv9-4" and "xrv9-6" devices in RFS.Thanks,Sreedhar.xrv9-4 is available in 172.20.63.150 - RFS3Hello,Assuming:Your cluster is up > show clusterYou have performed a host key fetch > request cluster remote-node my-rfs-node ssh fetch-host-keysYour devices and NSO and service are all in sync > plan is reached, no commits failedI would recommend not using the no-networking field in CURL command.My command is as below (I tried to update color):::curl -is -u admin:admin -X PATCH -H "Content-type: application/yang-data+xml" -d '<data xmlns="urn:ietf:params:xml:ns:yang:ietf-restconf"> <sr-te xmlns="http://cisco.com/ns/nso/cfp/cisco-tsdn-sr-te"> <policies xmlns="http://cisco.com/ns/nso/cfp/cisco-tsdn-sr-te-sr-policies"> <policy> <name>SR-CLI-DYNAMIC</name> <head-end> <name>PIOSXR-1</name> </head-end> <tail-end>127.0.0.1</tail-end> <color>150</color> <binding-sid>111</binding-sid> </policy> </policies> </sr-te></data>' 'http://localhost:8080/restconf/data'And this worked to push config correctly to device. When I use the no-networking, indeed the config does not push correctly to device.Let me know if this is alright.Regards,Janaki DuggiralaThank you. I removed the no-networking option and config is being pushed to the device. However is it a bug in using no-networking option. Is it deprecated option?Hello, The no-networking option is not needed, since its a simple commit to update config. This is like a standard commit on the NSO CLI and with the standard commit there is a no-networking option which enables to not send anything to the device (see screen shot attached). Let me know if this helps and I will proceed to close this ticket. Thank you. Regards, Janaki DuggiralaCustomer was using incorrect params in RPC command. Assisted customer with the right command. |
Old route-policies get added during provisioning services though CNC or device side there are no route-policies: Old route-policies get added during provisioning services though CNC or device side there are no route-policiesSteps:1. I deployed latest NSO 6.1 and tsdn builds on my NSO LSA setup. Note: Old cdb on NSO VMs was deleted and this is freshly deployed NSO build.2. When I try to provision ETREE-SRODN service, observing that old route-policies also get added though CNC or device side there are no route-policies.Attaching the payload, native configs on NSO UI and existing device configs for reference.Collected NSO logs on all LSA cluster nodes, will be attaching the logs soon. | During commit it showed that devices were out of sync and picking old route-policies. Once synched it adds only one route-policy. I saw similar issue with L3NM-SRTE service where config gets pushed to generic parent route-policy though it's not specified in payload. will try once and if able to repro on new NSO build, will open new JSD ticket. Thanks.The devices were out of sync and picking old route-policies. Once synched it adding the required route-policy only. |
Intermittently hitting "Read time out error" and it fails commit: Setup - 10.195.165.75 - xrd1/xrd1Received Read time out error message while pushing attached payload.Please find attached screenshot. Issue is intermittent.Kindly check if there is a way to handle this error. | CDETS filed after discussion with Ajitha |
After consuming new ONC, provisioning fails : After consuming new ONC, provisioning fails Please see attached .Env Details: NSO: ssh+ UI -> nso552/Public1234!CNC: UI: admin/Public1234!SSH: cw-admin/Public1234! | Hi Yevgeny, the issue you are seeing is due to ONC is missing transmit power in connectivity service output. We will have to wait for ONC to provide a fix.Roberto has provided the workaround:With the build 17.09.2021.CVT.CB4 and by applying the correct Env Variable (updated in wiki page copied below for convenience)On a CW cluster with ONC already deployed, execute on the shell:<ol></ol>This will open up a vi editor. 2. Scroll down to section, 3. the following lines if they are present (added as part of previous workaround):- name: networkholder.optval.activation.active.defaultvalue: ZONE_UNKNOWN- name: networkholder.optval.activation.whatif.defaultvalue: ZONE_UNKNOWN 4. the following lines to workaround the missing Logo params on the device- name: optvalidation.logo_data.mandatoryvalue: "false" 5. Save the file and exit 6. All 3 replicas of onc-pce-service will restart (starting from onc-pce-service-2) 7. Once restarts are complete (may take up to 15 minutes and can be checked with "kubectl get pod | grep onc-pce") ONC usage can resume |
Policy/Service showing as in-progress in CNC & the NSO plan message shows the ncs:ready not reached: Policy/Service showing as in-progress in CNC ; the NSO plan message shows the ncs:ready not reachedBut these policy config pushed to the device successfully.Server : 10.194.63.198CFS : 10.194.63.169RFS1: 10.194.63.170RFS2: 10.194.63.242RFS ; CFS has same credentials.Issue screenshot attached | Hi Ragesh,I checked on your setup and on your CFS node, it is missing some required LSA notification kickers.admin@ncs% show kickers notification-kickerNo entries found.Please refer the following wiki for correct LSA bootstrap procedure.Thanks,NishadThanks Nishad for looking the issue, After loading the cfs-netconf-notification-kicker.xml issue got fixed, Please close the ticket.Corrected the bootstrap data and issue got fixed. |
Python cb_validate error. STATUS_CODE: TSDN-L2VPN-408: Provisioning failed with error: Python cb_validate error. STATUS_CODE: TSDN-L2VPN-408 | Bootstrapping on CFS was done while havingauthentication issue with the RFS nodes; therefore, dynamic device mapping information was not populated on the RFS nodes, which caused the error when the L2VPN service was deployed.Issue action commands below con the CFS node to get dynamic config pushed to the RFS nodes. Services were successfully deployed afterwards.unhide tsdnrequest flat-L2vpn-actions update-internal-cfp-configurationsrequest ietf-te-actions update-internal-fp-configurationsrequest flat-L3vpn-actions update-internal-cfp-configurationsrequest cisco-sr-te-cfp:sr-te update-internal-cfp-configurationsCommand to verify on RFS nodes:unhide tsdnshow cisco-flat-L2vpn-fp-internal:cfp-configurationsshow cisco-flat-L3vpn-fp-internal:cfp-configurationsshow cisco-sr-te-cfp-internal:cfp-configurationsshow cisco-rsvp-te-fp:cfp-configurations |
cisco-zr-dco-cfp-native-flexport-linecard-template.xml:10 Element: 'port-ranges' only exists for ned-id: cisco-iosxr-nc-7.4:cisco-iosxr-nc-7.4: After consuming TSDN M6 FP, this thing started to appear Since starting from M6 two packages collide between the two: ncs-5.5-cisco-iosxr-nc-7.3.2.34I.tar.gzncs-5.5-cisco-iosxr-nc-7.3.2.37I.tar.gzncs-5.5.2.3-core-fp-plan-notif-generator-1.0.4.tar.gzncs-5.5.2.3-core-fp-plan-notif-generator-1.0.6.tar.gzI had chosen the latest for both cases . | Please install compatible RON CFP withCNC 3.0 M6 and let us know if you're still facing the issue. Release pages: (which redirects to )Hi Yevgeny,Please confirm whether you still having the issue with RON reported in this ticket. It seems to me that you no longer facing the issue, according to the email you sent to TSDN support alias of installing RON M3 build. If I am not hearing from you, I will close this case Monday 9/13/21.Thanks,VanAssuming the issue is no longer a problem after installing compatible RON ; CNC packages. |
Knowdge sharing session on NSO Actions - CNC3.0: Hi Team,This is to request for a knowledge sharing session on NSO Action button options from CNC3.0 as discussed in the last Scrubber meeting.From the Testing point of view: We would like to understand and remark the combination of usecases with the following NSO options.More specific to when and where are the scenarios exactly these recovery options used.Error recovery Check-SyncError recovery Sync-fromError recovery Sync-toReactive-RedeployRe-Deploy ReconcileRising this request ins-pite of gone through appropriate guidlines given against corefp wiki-page.Thanks,Dinesh | Please refer to all service related supported actions in our wiki. For example, for SR-TE you can refer here: The error-recovery flow wiki should be helpful for when to use these actions are applicable: For NSO device level action, please refer to the official NSO Documentation: If you have any specific questions after going through the links above, then go ahead and ask them here and I'll go ahead and try to answer to the best of my ability.Thanks,Regi Error recovery Check-SyncWhat does Error recovery check-sync do? Device check-sync compares device config and config in NSO DB. This is clear. But we are not very clear about error recovery Check-Sync. What is the use casse for this action? Error recovery Sync-fromWhen a service is in failure state, we would like to know what instance this sync-from can be performed to bring the plan state success and how.? Error recovery Sync-toWhen a service is in failure state, we would like to know what instance this sync-to can be performed to bring the plan state success and how.?Note: Either in the webex recording nor in the Wiki link, this option is never discussed. Reactive-RedeployAfter performing necessary error recovery step, What does Reactive action do? What is the use case for this? Re-Deploy ReconcileAfter performing necessary error recovery step, What does reconcile action do? What is the use case for this?We had a meeting details are posted here: |
Device Hostname Update not reflected in CW GUI: Hi Team, I been observing below 2 scenarios, request you to please check and share your comments on it.Scenario-1 :-> When Updated hostname and Inventory ID from CW GUI DLM page only Inventory ID is being updated (Hostname attribut not updated).Scenario-2 :-> When renamed device hostname from nso cli, latest hostname details are not reflected in GUI.Please have a look at attached mail thread for detailed description.Thank you.Kind regards, Rohit M | Hello Rohit,It seems like your query involves DLM package and CNC GUI. Both of these things are not within the scope of TSDN. I would recommend to forward this query to the respective owners of the previously mentioned features.Thanks,Isaac KimHi Issac Kim, Thank you for letting me know. Would you please share their queue link so that I can raise my request to them.Kind regards, Rohit MHi Rohit,We do not know if they have a queue setup but you can contact Ravi Kumar Kolla from DLM team.I will close this request.ThanksSahithiUnrelated to TSDN CFP. Query was regarding DLM FP. |
LSA - Capacity method details: HI, I have install CFS and RFS1 and RFS2. Now before adding providers in the CNC, I need to know how to use Capacity method in LSA setup. For SH testing, I have some test cases to use this setup. I am already using round robin. I am not understanding what is capacity method how to use it. Please let me know | Hi Sampath,Could you please elaborate what is capacity method ? Is it NSO or CFP-related issue?Can you share the specific issues you see with CFP or NSO?Thanks,Priyanka Hi Sampath,I will close this JSD if i dont get info before EOD today.ThanksPriyankaI have attached the snapshot. Please check and let me know Hi Sampath,Please work with CNC UI team .This is not related to CFP or NSO.ThanksPriyanka |
Steps to generate the jwt-token to test with authentication provider: Followed "TSDN 6.0.0 - Drop 5 (DTHO) - cisco cfp-jwt-auth package" wiki to enable RBAC PAM. After the config done, tried to test it by running the following command, but it failed.curl -is -H "Authorization: Bearer $(cat /root/temp/jwt.txt)" -vMaybe the token that I used is wrong. Like to find out the steps to generate the jwt token and use it in the command. Attached are the jwt.txt file and the curl response that I got. Thanks. | Thanks Subramanian for the webex session on this. In summary, the issue is the certificate pem file was not exported from root. After replacing the certificate pem file, the curl command works fine. Can you update the wiki, by adding one extra note to click on "Crosswork" (the root level) under Certificate Hierarchy before clicking export button to be clearer?Here is the webex recording info:link: Password:pBHxijM5Had a a screenshare and helped resolve the issue.The wiki is also updated for the same . Thanks Crystal for uploading the recording. |
l3vpn 'probes' section accepts string values for "agent-vlan" instead of enforcing only numbers and range: Hi,We see that "probes" section (for Accedian probes) in l3vpn services allows string values for "agent-vlan" field.But in reality it can be only number and only in specific range.Shouldn't NSO/CFP enforce it ? Also we have some doubt about 'vpn-network-access' field - it's correlated with vpn-network-access id from vpn-node section. Should this be unique for every VPN-service ?Regards,Leonid. | Hi Leonid,The ID for "vpn-network-access" will be unique only for a given vpn-node. However it is not unique across every service or every vpn-node. It is not globally unique.Also, we can definitely add in the range for "agent-vlan". Could you tell us what the range should be?Thank you for clarifying regarding "vpn-network-access" field.Regarding the range for "agent-vlan" - it's the standard 1-4094 as for dot1qHi Aravind,Should we track via cdets?Thanks,Arun.M.Gyes sure!Sure, thank youFiled CSCwh37105 in CDETS for tracking.available in the next drop |
Timeour while service commit: Setup: CNC: 10.195.165.70 - admin/Cnc@1234NSO: 10.195.165.75 - xrd1/xrd1While trying to commit a service , im getting "Post "https://10.195.165.75:8888/jsonrpc/validate_trans": context deadline exceeded (Client.Timeout exceeded while awaiting headers)" attached error. Please help troubleshoot reason for failure and if its known issue | Hi Ajitha,As discussed over Webex its not an issue and you are not seeing it anymore.ThanksPriyanka Hi Priyanka, we discussed and hope you were trying to troubleshoot my observation with logs. I see many devices were added to NSO (not CNC) and my devices are not able to authenticate in NSO. Unable to create any services. Would you please check asap |
L2vpn EVPN service created. Device name contains dots (domain name): Same issue as CSCwc18044: Fixed in M7Patch Applied on the system to fix it. | Patch applied |
config l3vpn without bgp neighbor : hi, we noticed that there is an option not to set neighbor under bgp part - is that correct to model the service like that? our NSO server 10.56.58.197 (nso574/Public1234!)see service - | Hi Idan,There is an option to set neighbors in BGP .The one you highlighted in yellow in the screenshot you attached, there was blue plus sign too , please use that one to add neighbor in NSO UI L3 Service.Attached screenshot for reference.ThanksPriyankahi - my question is - bgp neighbor is not a mandatory field? shouldnt NSO prevent user creating l3vpn when bgp neighbor is not set? thx. Hi Idan ,I will forward the you email discussion.This change is backward incompatible hence it is decided with discussion across CNC teams.Hope the thread i will send you might you understand the reason.ThanksPriyankathanks, saw you mail. but the original question was on route-target - and here I ask on bgp neighbor - both cases are the same? |
CNC tsdn-core-fp-common alarms purge and NSO CLI alarms: When we re-deploy a TSDN CFP RSVP-TE service and the configuration is rejected by the device I see and "service-activation-failure" alarm in the NSO CLIncsadmin@ncs-ts4nso01vs001# te tunnels tunnel pcepadap10496 re-deployError: External error in the NED implementation for device WSBMPS11: command: path: Error: String too longncsadmin@ncs-ts4nso01vs001# *** ALARM service-activation-failure: External error in the NED implementation for device WSBMPS11: command: path: Error: String too longncsadmin@ncs-ts4nso01vs001# but this alarm is no longer present in the alarm list:ncsadmin@ncs-ts4nso01vs001# show alarms alarm-listalarms alarm-list number-of-alarms 0This alarm is actually removed by tsdn-core-fp-common. Why does this happen?<INFO> 22-Jun-2022::11:46:52.392 cisco-tsdn-core-fp-common Thread-9: - Received alarm: /te:te/tunnels/tunnel<DEBUG> 22-Jun-2022::11:46:52.394 cisco-tsdn-core-fp-common Thread-9: - alarm text: External error in the NED implementation for device WSBMPS11: command: path: Error: String too long<DEBUG> 22-Jun-2022::11:46:52.412 cisco-tsdn-core-fp-common : - CQ Alarms received: {'cq_alarms': []}<DEBUG> 22-Jun-2022::11:46:52.413 cisco-tsdn-core-fp-common : - Waiting for subscription event<INFO> 22-Jun-2022::11:46:52.414 cisco-tsdn-core-fp-common : - Service alarms: {'service_alarms': []}<DEBUG> 22-Jun-2022::11:46:52.414 cisco-tsdn-core-fp-common : - Waiting for subscription event<INFO> 22-Jun-2022::11:46:52.414 cisco-tsdn-core-fp-common Thread-9: - Purged alarm: /te:te/tunnels/tunnelI'm struggling to explain to Vodafone this "ghost" alarms displayed in the CLI.Context:1) Vodafone Germany wants to test the SNMP alarm notifications originating from NSO, going into their alarm monitoring system named Spectrum. One of the alarms when want to see is: ALARM service-activation-failure2) Im not using CQ3) Im using the RSVP-TE TSDN CFPThis is how Im generating this alarm in the Vodafone Germany Lab:Package is loaded correctly and service is created correctly.No alarms present in NSO.ncsadmin@ncs-ts4nso01vs001#ncsadmin@ncs-ts4nso01vs001# te tunnels tunnel pcepadap10496 deep-check-syncsync-result { local-node { in-sync true }}ncsadmin@ncs-ts4nso01vs001# show alarms alarm-list number-of-alarmsalarms alarm-list number-of-alarms 0</ul>I make a change in the NSO service device template, making a string longer that what the device will accept.This will cause the device to reject the config with an error: string too longPerform a packages reload.</ul>Perform a service re-deploy that will fail with String too long:I can see the alarm ALARM service-activation-failure appearing in all open NSO CLI terminalsI can see it being deleted in the cisco-tsdn-core-fp-common log.</ul>ncsadmin@ncs-ts4nso01vs001# show alarms alarm-list number-of-alarmsalarms alarm-list number-of-alarms 0ncsadmin@ncs-ts4nso01vs001# te tunnels tunnel pcepadap10496 re-deployError: External error in the NED implementation for device WSBMPS11: command: path: Error: String too longncsadmin@ncs-ts4nso01vs001# *** ALARM service-activation-failure: External error in the NED implementation for device WSBMPS11: command: path: Error: String too longncsadmin@ncs-ts4nso01vs001#System message at 2022-06-23 13:00:45...Commit performed by ncsadmin via ssh using cli.ncsadmin@ncs-ts4nso01vs001#ncsadmin@ncs-ts4nso01vs001#ncsadmin@ncs-ts4nso01vs001#ncsadmin@ncs-ts4nso01vs001# show alarms alarm-list number-of-alarmsalarms alarm-list number-of-alarms 0ncsadmin@ncs-ts4nso01vs001#ncsadmin@ncs-ts4nso01vs001#<DEBUG> 23-Jun-2022::13:00:45.213 cisco-tsdn-core-fp-common : - CQ Alarms received: {'cq_alarms': []}<DEBUG> 23-Jun-2022::13:00:45.213 cisco-tsdn-core-fp-common : - Waiting for subscription event<INFO> 23-Jun-2022::13:00:45.214 cisco-tsdn-core-fp-common : - Service alarms: {'service_alarms': [('ncs', 'service-activation-failure', '/te:te/tunnels/tunnel[name="pcepadap10496"]', '')]}<DEBUG> 23-Jun-2022::13:00:45.214 cisco-tsdn-core-fp-common : - Waiting for subscription event<INFO> 23-Jun-2022::13:00:45.222 cisco-tsdn-core-fp-common Thread-9: - Received alarm: /te:te/tunnels/tunnel<DEBUG> 23-Jun-2022::13:00:45.224 cisco-tsdn-core-fp-common Thread-9: - alarm text: External error in the NED implementation for device WSBMPS11: command: path: Error: String too long<DEBUG> 23-Jun-2022::13:00:45.246 cisco-tsdn-core-fp-common : - CQ Alarms received: {'cq_alarms': []}<DEBUG> 23-Jun-2022::13:00:45.246 cisco-tsdn-core-fp-common : - Waiting for subscription event<INFO> 23-Jun-2022::13:00:45.247 cisco-tsdn-core-fp-common : - Service alarms: {'service_alarms': []}<DEBUG> 23-Jun-2022::13:00:45.247 cisco-tsdn-core-fp-common : - Waiting for subscription event<INFO> 23-Jun-2022::13:00:45.247 cisco-tsdn-core-fp-common Thread-9: - Purged alarm: /te:te/tunnels/tunnelWhen the ALARM service-activation-failure is created in NSO, the SNMP Notification is sent to Spectrum.The Vodafone operations team monitoring Spectrum sees the alarm and will go to NSO to perform an investigation and eventually mark the alarm cleared but no alarm is present in NSO.ncsadmin@ncs-ts4nso01vs001# show alarms alarm-list number-of-alarmsalarms alarm-list number-of-alarms 0ncsadmin@ncs-ts4nso01vs001# show alarms alarm-list number-of-alarmsalarms alarm-list number-of-alarms 0a) I need to explain the above behaviour to Vodafone in the context of how should the operational team act facing this alarm.B) In the NSO admin guide it is written:Alarm Identity: service-activation-failureClear condition(s): If the service is successfully redeployed, the alarm is cleared.but Vodafone will not have this alarm in NSO. | Hi Sujay,For TSDN, I believe this has been the behavior for service alarms. tsdn-core-fp-common code purges the alarm which is then reflected on the plan state marked failed with the exact alarm text. This applicable to all the services.This failure will be sent in plan notification.ThanksSahithiExpected behavior from CFP. Delete alarms are purged as we want NSO to recreate the same alarms on re-deploy. |
Unable to migrate device NEDs as part of NSO upgrade: Stuck on the Step 6 of the NSO guide: Tried "show devices | match "devices"" and got the following output:devices device 172.20.200.138devices device AA-ASR1001x-1devices device AA-ASR903-2devices device AA-ASR903-3devices device AA-NCS5501-1devices device AA-NCS5501-2devices device AA-NCS5501-3devices device AA-XRV9k-1devices device AA-XRV9k-2When used these device names on the command above as:request devices device AA-ASR1001x-1 migrate new-ned-id cisco-iosxr-cli-7.49 dry-run verboseGives the following error:Error: Failed to connect to device AA-ASR1001x-1: connection refused: NEDCOM CONNECT: Authenticate: Exhausted available authentication methods. Server allowed: [ publickey keyboard-interactive password ] in new stateNeed help with migrating device NEDs as part of NSO upgrade. This is in continuation with the ticket raised on Friday: | Hi Raghasuma, just closing out on this ticket.We discussed offline that the problem is due to changing encryption keys in ncs.conf during upgrade which caused the hashed passwords to be un-decodable. The solution was to rehash device authgroup passwords with the new encryption strings defined in ncs.conf by simply updating the authgroup with same password. Afterwards we confirmed that devices are reachable.If you have any additional questions please let me know.Thanks,Isaac Kim |
Information needed regarding Custom Template deployment on NSO LSA HA: Hi Team,In LSA, custom templates are only added to RFS nodes. I am trying this when RFS is in HA mode. Do I have to add custom template to both HA nodes of RFS or I can just add it using VIP IP and RFS HA will take care of it.Kindly help to understand the scenario.Thanks,Kanchan | Hi Kanchan ,As per Webex discussion, we need a custom template package on both nodes, but yes creation from VIP makes it synch on the standby node.After adding the same packages on both nodes you will be good to create or use custom templates from VIP.ThanksPriyankaWebex suggestion provided.Thanks Priyanka. |
Uninstallation of CFS throwing error: NSO CFS: 10.56.116.121 ( nso/Public1234!)NSO RFS : 10.56.116.122 ( nso/Public1234!)I have NCS 5.7.2.1 with TSND 4.0.0 M4 installed.while trying to uninstall the CFS, facing error at the below steps.nso@ncs% delete cluster remote-node rfs-1nso@ncs% commitAborted: 'cluster commit-queue enabled' (value "true"): At least one cluster remote-node has to be configured. All LSAdevices must be configured as cluster devices.nso@ncs% delete cluster authgroup cluster-rfs-authError: element not foundnso@ncs% delete cluster device-notifications enablednso@ncs% commitAborted: 'cluster commit-queue enabled' (value "true"): At least one cluster remote-node has to be configured. All LSAdevices must be configured as cluster devices.nso@ncs%can you please help in this?Thanks,Arun.M.G | Hi Arun,As discussed , If the cluster has ONLY one RFS, you could not delete it. Instead need to delete the whole cluster.I have updated the wiki as well for the next release.Please suggest if the solution worked and we can close this ticket.Regards,Nishad SubairHi Nishad, yes, that worked. please update the confluence and we can close this.Thanks for your help.Thanks,Arun.M.GHad discussion with the submitter and provided the solution.Also updated the M6 wiki with the Note mentioning "If the cluster has ONLY one RFS, need to delete the whole cluster". |
code error message on cisco-tsdn-core-fp-common: NSO Version:6.1_230124.150846953.5043401bc5beLogin details:ssh -L 30163:192.168.22.76:8888 [email protected] (Password: Cwork123!) (UI login: admin/Cwork123!)SSH login:SSH to Jump host 10.23.213.208 ssh login for 192.168.22.76: admin/Cwork123! | Hello, I have logged into your NSO and run the following command:admin@ncs> request packages package cisco-tsdn-core-fp-common redeployThis has redeployed the package and fixed the error. Please verify.Thanks Janaki. It looks good now.Redeployed package on NSO. Customer confirmed issue is resolved. |
Want access to Make files for compiling customizing T-SDN FP: As part of TCL POC, we want to demonstrate to customers that we can customize service packs on NSO and show changes on GUI. For example currently encapsulation type is only dot1q present but customers also want to add second-dot-1q as well | Hello, please post details on error message received and steps to reproduceHello, we have not received further response on this ticket.Please let us know if this issue persists.Note: If no response is received ticket will be closed EOD Aug 2nd. |
Reactiv-Redeploy does not work properly: Steps:1. Headend node is out of sync2. Provision a policy with async commit queue Provision failed as expect3. Do a sync-to to make headend not in sync4. Do "Reactive-Redeploy" The provisioned policy is still in failed stateXRV9K 7.3.2.33I is used | Hi Crystal,Please following the steps from wiki linked to resolve the issue.Sync-to and reactive-redeploy is not a right command in this case.Thanks,LinhBy reading the link, I am not sure for this scenario what would be the right command to use except for redeploy? We would like to know in what scenario can reactive-redeploy and redeploy-reconcile can be used?Read the link one more time and found there is flow for "Redeploy reconcile" under "Persistent Create Failure Recovery Flow". Need clarification on the followings:1. For this flow, one of the steps says "Sync from on device". Is it to do a Sync from device action? copy the device config to NSO?2. I still do not see a flow for "Reactive Redeploy". Can you share the flow for this action?Thanks.All the flows outlined are with respect to NSO being the source of the actions (ie NSO sync-from device)I**don't believe we have a flow outlined for reactive-re-deploy specifically. For the most part on how they differ, is that reactive-re-deploy is shallow and asynchronous by default. You can think of `reactive-re-deploy = re-deploy shallow` except `re-deploy shallow` is synchronous. There are some cases where reactive-re-deploy maybe helpful, but currently nothing comes to mind specifically for T-SDN. For now, you should just follow the wiki on the error flows that Linh forwarded and if any of the flows do not help then feel free to reach out again and we can go over steps to resolve the issue.Had webex with submitter and explained the difference |
timeout error when provision L3VPN service on XE setup: Provision L3VPN service with SR policy. It includes one end XR (PE2-ASR9k) and the other end XE (ASR920-2-PE8).During the commit, 2 popups with the following error messages: net/http: request canceled (Client.Timeout exceeded while awaiting headers)Server did not respond to the request within 25 seconds.The provision is actually went through. Can someone take a look? Attached is the discussion with cnc-ui-dev | HI Crystal,Can you provide me the steps to reproduce and payload used..?--Raghavi.Attached please find the payload. The steps is to use CAT UI and import this attached xml file to provision L3VPN service in a setup with has XE devices. Thanks. HI Crystal,We are working on getting the device access.--RaghaviHi Crystal,As we can successfully deploy the service, for me to further debug need details like time when you committed the service and the time you received the plan ready reached notification from NSO.If not you can simple provide the logs. I am looking for ncs-python-vm-ietf-l3vpn-nm.log.Also i would suggest to try out this on NSO UI.Also for future JSD tickets please include all the info requested in this wiki.--Raghavi. NSO: 5.5.2.7TSDN cfp: 3.0.0 M5Device type ; version: ASR920: 17.6.1 ASR9K: 6.7.2Payload attached. Note: Tried it with an upgraded setup using inventory id to provision service. Payload changed to use inventory id instead of host name for nodes.NSO log attached. HI Crystal,As discussed over the call..it's the delay in response from device not the NSO. We can check timeout for devices in NSO using below commanddefault timeout is 20Secondshow devices global-settings read-timeout read-timeout 20;In this case XE device is taking little longer time to respond. so increasing this value will help to avoid timeout from NSO if there is any delay in response from the device.--RaghaviHi Crystal,Did the above comment from fix your issue?Thanks,Regino response from submitter |
unable to create sr-te policy - error : Tried to create a sr-te-policy on NSO - got the following error msg:message: RPC error towards TB3-PE-B: unknown_element: ns2:sr/ns1:traffic-engineering/ns1:policies/ns1:policy/ns1:candidate-paths/ns1:preferences/ns1:preference/ns1:path-infos/ns1:path-info/ns1:hop-typeNSO: 172.24.97.147 (ssh pw "Vtsisco@123!") | Hi Quy,Please provide the details mentioned in our release notes: Thanks,Nishadhi Nishad,Thanks for getting back to us. Here is the information:i was using NSO UI and CNC-UI to create the sr-te policy (similar payload below)Hi Quy,Please provide the following details.Platform used and version number.Thanks,Nishadhi Nishad,please see the attached files for the infoThanks and regards,-QuyHi Quy,We re-deployed the service and it worked fine.Also tried to reproduce the issue again , but was not reproducible.The Trace for the device wasn't enabled. if you face the issue again , please provide the reproduction steps and logs for further debugging.Thanks ,Nishadhi Nishad,Thanks for the update - will try couple more use cases and will update soon.Good to know that the sr-te policy after redeployed the service went to success state.Regards,-Quyhi Nishad,I tried to create a new sr-te policy from CNC UI and the issue is still displayed.We use ASR9K devices.Please see attached files for the payload, the output of the dry run and the snapshot of the error msg.Hope this is enough information for you.Thanks and regards,-Quy Hi Quy,Issue is because you are using 7.4.2 device but using 7.3 NED.NC NEDs need to match device version otherwise please use CLI.Thanks,Nishadhi Nishad, after changing to 7.4 NED, the sr-te policy went through - was wondering why the NSO did not flag/error out with other policy (i.e. L3/L2 policy) creation.Thanks for your help. You can close this ticket.Regards,-QuyHi Quy,Thank you for the update.Regards,Nishad |
device sync-from failed after change device-type to netconf ned: Steps:1. This is on a CSP5K setup with Crossowork, CNC and CDG installed2. Onboard provider and devices3. The devices gets created on NSO with cli ned automatically.4. Change to netconf ned by using cli command on NSO VM:set devices device xrv9k-7 device-type netconf ned-id cisco-iosxr-nc-7.35. Do a device sync-from command. It failed with missing element.admin@ncs> request devices device xrv9k-7 sync-fromresult falseinfo xrv9k-7: missing element: hop-type in /ncs:devices/ncs:device/ncs:config/Cisco-IOS-XR-segment-routing-ms-cfg:sr/Cisco-IOS-XR-infra-xtc-agent-cfg:traffic-engineering/Cisco-IOS-XR-infra-xtc-agent-cfg:policies/Cisco-IOS-XR-infra-xtc-agent-cfg:policy/Cisco-IOS-XR-infra-xtc-agent-cfg:candidate-paths/Cisco-IOS-XR-infra-xtc-agent-cfg:preferences/Cisco-IOS-XR-infra-xtc-agent-cfg:preference/Cisco-IOS-XR-infra-xtc-agent-cfg:path-infos/Cisco-IOS-XR-infra-xtc-agent-cfg:path-infoNSO logs attached.NSO version: 5.5.2.7TSDN CFP: 3.0.0 M6Device: XRV9K 7.3.2 33I | Hi Crystal,XRV9K 7.3.2.33I is not listed on our as such it hasn't tested and validated so we are unable to support this version for the M6 release.Please upgrade to 7.3.2.37I and let me know if you run into the issue there. We can then move forward to investigating the issue further.Thanks,RegiNo response from submitter. Closing ticket. |
XML Payload need to Create L3vpn on Untagged interface: Hi,I have XML paylaod to create L3vpn for tagged interface.but i would need for untagged interface..i have tried removing the connection tag. but doesnt work. <port-id>TenGigE0/0/0/0</port-id><!--connection> <encapsulation-type>tagged-int</encapsulation-type> <tagged-interface> <type>dot1q</type> <dot1q-vlan-tagged> <cvlan-id>106</cvlan-id> </dot1q-vlan-tagged> </tagged-interface> </connection-->attached payload for L3vpn with tagged interface | It seem your payload is incorrect. This is untagged sample payload <l2vpn-ntw xmlns="urn:ietf:params:xml:ns:yang:ietf-l2vpn-ntw"> <vpn-services> <vpn-service> <vpn-id>l2nm-p2p</vpn-id> <vpn-svc-type>vpn-common:t-ldp</vpn-svc-type> <vpn-nodes> <vpn-node> <vpn-node-id>PE1</vpn-node-id> <ne-id>PE1</ne-id> <signaling-options> <type>vpn-common:t-ldp</type> <t-ldp-pwe> <ac-pw-list> <peer-addr>100.100.100.6</peer-addr> <vc-id>1001</vc-id> <mpls-label>101</mpls-label> </ac-pw-list> </t-ldp-pwe> </signaling-options> <vpn-network-accesses> <vpn-network-access> <id>l2vpn-p2p-ac1</id> <connection> <encapsulation-type>vpn-common:untagged-int</encapsulation-type> <untagged-interface> <l2-access-type>vpn-common:untagged-int</l2-access-type> <untagged> <physical-inf>GigabitEthernet0/0/0/3</physical-inf> <sub-if-id>100</sub-if-id> </untagged> </untagged-interface> </connection> </vpn-network-access> </vpn-network-accesses> </vpn-node> <vpn-node> <vpn-node-id>PE2</vpn-node-id> <ne-id>PE2</ne-id> <signaling-options> <type>vpn-common:t-ldp</type> <t-ldp-pwe> <ac-pw-list> <peer-addr>100.100.100.5</peer-addr> <vc-id>1001</vc-id> <mpls-label>102</mpls-label> </ac-pw-list> </t-ldp-pwe> </signaling-options> <vpn-network-accesses> <vpn-network-access> <id>l2vpn-p2p-ac1</id> <connection> <encapsulation-type>vpn-common:untagged-int</encapsulation-type> <untagged-interface> <l2-access-type>vpn-common:untagged-int</l2-access-type> <untagged> <physical-inf>GigabitEthernet0/0/0/3</physical-inf> <sub-if-id>100</sub-if-id> </untagged> </untagged-interface> </connection> </vpn-network-access> </vpn-network-accesses> </vpn-node> </vpn-nodes> </vpn-service> </vpn-services> </l2vpn-ntw>Regards,LinhHi Linh, Thanks for quick response. I am looking for L3vpn . Not l2vpn.1] I wanted to configure l3vpn on parent interface , without sub-interface.Thanks,Arun.M.GHi Arun, Attached l3nm.xml is corrected oneThanks,LinhHi Linh,I dont see the attachment .Thanks,Arun.M.GThe payload is provided |
SRV6 policy provisioning throws error : SRV6 policy provisioning throws below error message:SRv6 is not supported with current device or NEDCATEGORY: userSEVERITY: ERRORContext [name = SRv6 validation, message = Either device not synced or NED/device image version is not supported for SRv6 state = {'Service': 'srv6_vpn_policy-9002', 'Device': 'TB3-PE-B', 'NED-ID': 'cisco-iosxr-nc-7.4:cisco-iosxr-nc-7.4', 'Version': ''}]"" | Additional info:10.194.63.142 (CNC cluster - ssh - cw-admin/Cwork123!)10.294.63.147 (NSO - non-LSA with M2 - ssh - nso/Vtsisco@123!)correction on the cluster and NSO setup - only the IP addresses were incorrect 172.24.97.142172.24.97.147 hi NSO team, any update on this and do you need any other info from us?Thanks and regards.Hi Quy,Srv6 policy is supported only for XR 7.3.2 version.ThanksSahithiRef: |
Devices not showing in the dispatch map for CFS & RFS: Devices not showing in the dispatch map for CFS ; RFS.admin@ncs% show dispatch-mapNo entries found.admin@ncs% run show devices device rfs-1 netconf-notifications subscription FAILURE ERRORNAME STATUS REASON INFO-------------------------------------------------------------rfs-1-cisco-custom-template-events running - -rfs-1-dispatch-map-update running - -rfs-cisco-custom-template-events running - -rfs-dispatch-map-update running - -tsdn-kicker-events running - -admin@ncs%CFS-10.194.63.169RFS1-10.194.63.170RFS2-10.194.63.242Credentials: admin/Vtsisco@123! | Hi Ragesh,I have updated wiki with correct verification steps for the dispatch map : On your CFS node now it shows correctly :admin@ncs% show devices lsa dispatch-map device TB2-P-BOTTOMLEFT { ned-id cisco-iosxr-cli-7.36:cisco-iosxr-cli-7.36; remote-node rfs-1;}device TB2-P-BOTTOMRIGHT { ned-id cisco-iosxr-cli-7.36:cisco-iosxr-cli-7.36; remote-node rfs-1;}device TB2-P-TOPLEFT { ned-id cisco-iosxr-cli-7.36:cisco-iosxr-cli-7.36; remote-node rfs-1;}device TB2-P-TOPRIGHT { ned-id cisco-iosxr-cli-7.36:cisco-iosxr-cli-7.36; remote-node rfs-1;}device TB2-PE-A { ned-id cisco-iosxr-cli-7.36:cisco-iosxr-cli-7.36; remote-node rfs-1;}device TB2-PE-B { ned-id cisco-iosxr-cli-7.36:cisco-iosxr-cli-7.36; remote-node rfs-2;}device TB2-PE-C { ned-id cisco-iosxr-cli-7.36:cisco-iosxr-cli-7.36; remote-node rfs-2;}device rfs-1 { ned-id cisco-nso-nc-5.5:cisco-nso-nc-5.5; local;}device rfs-2 { ned-id cisco-nso-nc-5.5:cisco-nso-nc-5.5; local;}admin@ncs% RFS Node won't show this .Only CFS will show .Also to refresh the dispatch map :admin@ncs% request devices lsa dispatch-map sync remote-nso rfs-1I tried refreshing in your CFS node and it worked fine.Please let us know if you need any further assistance.ThanksPriyanka |
L3VPN + OND with SRv6 in 5.0 service model: We have an L3vpn service attached with ODN templates + SRv6 in CNC4.0. After converted it with CNC5.0 format. The provision is successful but the policies are in operational down state. Attached are the payloads for 4.0 and 5.0. Can you let me know if anything is wrong for the conversion? Thanks. | Hi Crystal,I do not see any issue with your payload from first glance. It looks similar to payload suggested in the wiki for L3NM support with SR ODN Would you be able to help here?ThanksSahithi |
[TM-TC] Post cleanup , unable to create new plan again.: In tm-tc fp, cleanup is successfully deleting the config that is intended to be removed. But after retrying creation and cleanup multiple times, the cleanup is throwing below alarm on CLI admin@ncs# *** ALARM service-activation-failure: Operation failed because: Not able to retrieve diffset for zombie nano service : '/cisco-tm-tc-fp-internal:tm-tc'After throwing this alarm on CLI, the cleanup returns success but new plan creation fails. This happens after trying for few times and creating new plan is blocked after we hit this. | Hi Raja, thank you for the information.Seems like there are some leftover artifacts from cleanup action which may be interfering with your service creation.Leftover artifacts from cleanup action are typically the result of race conditions. If you see the TM TC cleanup action, we do a delete operation and afterwards force-backtrack plan components. These two operations can result in a race condition which can cause certain artifacts to regenerate during cleanup. Otherwise there could be leftover artifacts that can result in unexpected behavior.To avoid this, for TSDN, we mandate users to first attempt to delete service prior to using cleanup action as a last resort option.Could you confirm if service was deleted prior to cleanup?Thanks,Isaac KimHi Raja,After some discussion, we have decided that the best solution would be to use NSO's native delete operation.As Sahithi corrected me last call, NSO delete is not a synchronous operation. We must keep in mind, cleanup action also has a async delete operation at the beginning of the action. This is what is causing the race conditions and artifacts you mentioned in this ticket. If we do not delete the TMTC service prior to force backtrack, service configuration will remain as leftover artifacts. In addition, in my testing, I have seen TMTC cleanup action leave artifacts when executed on created service with out of sync device. So a delete + converged plan prior to cleanup is a . Otherwise behavior is undefined. : plan must be in backtrack mode and fully converged (which means no active operations on plan are running).To meet this pre-condition, we can do a NSO delete + commit. Once we commit, service config is deleted and zombies will spawn which will backtrack the plan asynchronously.If there are no errors during backtrack, the plan should eventually be cleaned up. In this case, cleanup action is not required.In case there are errors (such as connection refused, out of sync), the plan will fail and remain in backtrack mode. This meets the pre-condition stated above and cleanup action should be executed next.In order to ensure that plan has fully converged, we will need to introduce some kind of external poller mechanism to check plan state. Here is an example flow:<ol>Delete Service ACommitExternally Poll NSO for Service A plan state<ol>Service A plan has no failure during backtrack<ol>Plan is deleted<ol>DONE</ol></ol>Service A plan has failure during backtrack<ol>Plan is stuck in failed state and in backtrack mode<ol>Execute cleanup action<ol>DONE</ol></ol></ol></ol></ol>Based on this flow, we can see that the main condition for the poller is to determine if the plan has failed or not. If the plan does not fail during backtrack, the plan should not exist. If the plan does fail during backtrack, the plan will fail and converge. If the plan is currently backtracking, plan should exist and there should be no plan failures.So to determine if we need to execute cleanup action, all we have to do is check if plan has failed or not.To check plan status, you can check two items:<tm tc plan> -> plan -> error-info -> message<tm tc plan> -> plan -> failedIn most cases, there will be an error-info message on plan for failed delete. But in edge cases, there are times when message is empty.I hope this is a viable solution to this problem. Please let us know what you think.Thanks,Isaac KimThanks for looking into the issue. I see, conclusion is that there is no way we can achieve synchronous deletion of plan which is a must as per design of collection service which triggers TM-TC FP. I have concern in polling externally to check if plan deletion is successful or not. This can work in case of standalone installations but there is no plan created on CFS in case of LSA deployments. Given this, we want to do all the changes with in tm-tc fp instead of handling it on client side. Is there any polling API available in ncs api that we can use ? That would be helpful to achieve whatever you are suggesting but within fp code. Hi Moksha,As discussed on call, I have tried to find a way to stream notifications from RFS node to CFS node stream. But I do not think that is possible. We can check the received RFS service-state-change notifications on the CFS node through NSO device tree, but this will require an external poller.To utilize notification stream, you will need to interface with notification stream on the NSO node where the service is located. In the case of LSA, the RFS service-state-change notification stream should be used. A custom kicker can be utilized to watch the received notifications for each RFS node and execute a custom action which can copy over the notifications to CFS notification stream. But this will be more complicated.Thanks,Isaac KimA solution was proposed to submitter and abosorbed. |
NCS 6.1 with M5+ LSA Setup not working: CNC is unable to detect CFS in a LSA setup when installed with NSO 6.1 with M5+ CFP. Setup Details: CNC - 10.194.63.198 (admin/Public123! cw-admin/Cwork123!)NSO CFS - 10.194.63.169 (nso/Vtsisco@123!)NSO RFS-1 - 10.194.63.170 (nso/Vtsisco@123!)NSO - RFS-2 - 10.194.63.242 (nso/Vtsisco@123!) | Hi Sachin, I will investigate your setup now. Thanks.After investigating, NSO CFS node seems to be responding fine from NSO CLI and NSO WebUI. When checking CNC WebUI, we can see that there are connection timeout errors from DLM which is trying to connect to CFS node port 20243. I assume that DLM should be trying to connect to 2024 which is NSO's ssh port.Sachin to connect with CNC devs about DLMHi Sachin,If everything has been resolved from NSO side, please let me know.I will close this ticket in a few days if there is no reply.Thanks,Isaac KimDLM package was having trouble with misconfigured port. NSO seems to be functioning fine. |
Multiple issues with 4.1.0-M2: 1] 1 am not able to provision L2VPN or L3VPN service with devices in south bound locked, Service is going to failed state saying "devices in south-bound locked" state2] With devices unlocked: Some of the services failed during provisioning with "RPC error towards RFS-1: operation_failed: Commit failed because commit queue item 1663485287551 has an overlapping service or device modification." ERROR3] When i re-deploy those services failed in (issue 2), i am getting -> RPC error towards RFS-1: unknown_element: for /cisco-flat-L2vpn-fp-internal-remote-site:flat-L2vpn-internal-remote-site-service/cisco-flat-L2vpn-fp-internal-remote-site:flat-L2vpn-p2p: /flat-L2vpn-internal-remote-site-service/flat-L2vpn-p2p: the 'when' expression "../service-type = 'p2p'" failedCFS and RFS show tech copied @ /auto/ncahi/cw_pyats/users/shbalu/bkp/NSO:-rwxrwxrwx. 1 shbalu eng 824M Sep 20 09:16 data_091922_215719.tgz -rwxrwxrwx. 1 shbalu eng 1.4G Sep 20 09:17 data_091922_215737.tgz | Not seeing Southbound lock issue with L3VPN service, but looking or update on issue 2and 3Below CDET has been raised for this. Hence closing this ticket.CSCwd15938 - L2VPN service creation failed with Commit queue overlapping service or device modification |
Unable to fetch the ssh-host key for the RFS node and the cluster status showing down: Hi-Unable to fetch the ssh key for the RFS node and the cluster status showing down. Please take a look.admin@ncs% request cluster remote-node rfs-1 ssh fetch-host-keysresult failedinfo Connection to rfs-1 timed outadmin@ncs% run show cluster LAST RECEIVEDNAME NAME STATUS EVENT NOTIFICATIONS-------------------------------------------rfs-1rfs-2REMOTE LOCAL REMOTENODE ADDRESS PORT CHANNELS USER USER STATUS TRACE-------------------------------------------------------------------------rfs-2 172.29.106.133 2022 - admin admin down disabledrfs-1 172.29.106.132 2022 - admin admin down disabledCluster setupCFS - 172.29.106.131RFS1 - 172.29.106.132RFS2 - 172.29.106.133Credentials: admin/Cwork123! | Hello,Please check your netconf ports and network connectivity.Regards,Janaki Duggiralawe are able to ping from CFS to RFS.can you please let us know how to check the netconf ports?setup details are provided below., can you please check ?Thanks,Arun.M.GHello, We tried to log into the setup mentioned here but we were unable to log in. Please give us the correct IPs to CFS/RFS. If these IPs are correct then maybe the network is not stable, so we are unable to troubleshoot.jaduggir@$ ssh [email protected]: connect to host 172.29.106.132 port 22: Operation timed out Regards, Janaki DuggiralaHi Janaki,Able to connect the VM's now, Could you please check the setup.nso@gd-arupras2-nso:~$ ssh [email protected] authenticity of host '172.29.106.131 (172.29.106.131)' can't be established.ECDSA key fingerprint is SHA256:DTy6b5qyCA+gJkcw1JjeB7hcPUNlaR3tRGMcSwbGb1c.Are you sure you want to continue connecting (yes/no)? yesWarning: Permanently added '172.29.106.131' (ECDSA) to the list of known [email protected]'s password:Welcome to Ubuntu 18.04.1 LTS (GNU/Linux 4.15.0-29-generic x86_64)Documentation: Management: Support: Canonical Livepatch is available for installation.<ul class="alternate" type="square">Reduce system reboots and improve kernel security. Activate at: 674 packages can be updated.459 updates are security updates.Last login: Wed Sep 14 09:46:58 2022 from 10.65.57.218admin@nso-172-29-106-131:~$Thank you. We are checking.Dev Notes: From investigation,Command stuck hereadmin@ncs% request devices fetch-ssh-host-keysadmin@ncs% request devices device rfs-1 connectNext,admin@nso-172-29-106-132:/etc/ncs$ sudo ufw statusStatus: activeTo Action From2244 ALLOW Anywhere22/tcp ALLOW Anywhere2244 (v6) ALLOW Anywhere (v6)22/tcp (v6) ALLOW Anywhere (v6)Customer did not open firewall port for 2022 and 2024We opened those ports on RFS 1From Linh Ly,Able to connect to rfs1 from cfs after open 2022/2024 port on RFS1admin@ncs> request devices device rfs-1 ssh fetch-host-keysresult updatedfingerprint {algorithm ssh-ed25519value 2d:46:b1:ae:4f:a2:06:6f:4a:e8:f8:b9:a0:2a:02:a3}admin@ncs> request devices device rfs-1 sync-fromresult trueRFS 2 ports need to be opened as well:sudo ufw allow from any to any port <port-number> proto tcpAfter opening ports, Cluster is UPadmin@ncs% run show cluster RECEIVEDNAME NAME STATUS LAST EVENT NOTIFICATIONS-------------------------------------------------------------------------------rfs-1 device-notifications up 0000-01-01T00:00:00-00:00 0 ncs-events up 0000-01-01T00:00:00-00:00 0rfs-2REMOTE LOCAL REMOTENODE ADDRESS PORT CHANNELS USER USER STATUS TRACE-------------------------------------------------------------------------rfs-2 2022 - admin admin down disabledrfs-1 2022 - admin admin up disabledThanks Janaki for checking the issue, allowed 2022 port on RFS2 firewall and now the cluster status showing fine for RFS1 and RFS2.admin@ncs% run show cluster RECEIVEDNAME NAME STATUS LAST EVENT NOTIFICATIONS-------------------------------------------------------------------------------rfs-1 device-notifications up 0000-01-01T00:00:00-00:00 0 ncs-events up 0000-01-01T00:00:00-00:00 0rfs-2 device-notifications up 0000-01-01T00:00:00-00:00 0 ncs-events up 0000-01-01T00:00:00-00:00 0REMOTE LOCAL REMOTENODE ADDRESS PORT CHANNELS USER USER STATUS TRACE-------------------------------------------------------------------------rfs-2 172.29.106.133 2022 - admin admin up disabledrfs-1 172.29.106.132 2022 - admin admin up disabledThank you, closing ticket.Regards,Janaki DuggiralaCustomer did not open firewall port for 2022 and 2024.Assisted customer with enabling ports.Cluster came up successfully.Below command used for allowing the netconf on NSO-VMsudo ufw allow from any to any port 2022 proto tcp |
L3VPN with Point-to-point: Hi Team,Are we supporting L3 VPN with P2P vpn service topology, if yes can I get the payload for the same.Also want to confirm for Dynamic MVPN provisioning we do not support P2P vpn-service-topology, if user uses P2P with dynamic MVPN what error will be thrown.Thanks,Kanchan | P2P is not supported on L3VPN. We have CDETS from Ajitha for it and we are working on it. Should be resolved in M6 release.ThanksSahithiThanks Sahithi. you can close the ticketWorking on a CDET with exact same issue. |
NSO 6.1 - TSDN 5.0.0 M5+ NSO License issue - CAA 5.0 - SH Uni-d Scale setup: Hi,I am seeing below error in my NSO LSA setup (in both CFS and RFS). We have NSO LSA setup installed NSO6.1 , TSDN 5.0.0 M5+ . I am using this setup for SH Uni-d Scale testing, I have 27702 services configured as of now.Can you please check and help ?Since this is Scale setup, having 27k services, please use the Setup for RO purpose onlySetup: 172.29.106.131 - CFS (nso/Cwork123!)172.29.106.132 - RFS1 (nso/Cwork123!)172.29.106.133 - RFS2 (nso/Cwork123!) | Hi Arun,You're using an engineering build of NSO, so this is normal. Is the causing any other issues other than the notification?Thanks,RegiHi reginald,As of now no. do we have any side effects becuase of this. if nothing and if this is normal, please close this ticket.Sounds good. There shouldn't be any side-effects. Closing the ticket now.Thanks,Regi |
Context [name = Fetch SIP Error, message = Fetch SIP Failed]: Error====Context File "/home/nso542/RON-ML/state/packages-in-use/1/cisco-optical-cfp/python/cisco_optical_cfp/optical_actions.py", line 424, in cb_action sips = controller.fetch_sip(File "/home/nso542/RON-ML/state/packages-in-use/1/cisco-optical-cfp/python/cisco_optical_cfp/onc.py", line 213, in fetch_sip inv_id = self._get_inventory_key(key)File "/home/nso542/RON-ML/state/packages-in-use/1/cisco-optical-cfp/python/cisco_optical_cfp/onc.py", line 314, in _get_inventory_key (rack, shelf, slot, port) = rem.split("/")Environment==========UI + SSH: nso542/Public1234!Instance: Local Installation /home/nso542/RON-MLONC_HOST=10.56.58.69ONC_PORT=30666ONC_USER=adminONC_PWD=cisco123Service:========<ron-mlxmlns="http://cisco.com/ns/nso/cfp/cisco-ron"><name>400Gbps-Transponder-OLS</name><mode>transponder</mode><bandwidth>400</bandwidth><circuit-id>2</circuit-id><grid-type>100mhz-grid</grid-type><frequency>1951000</frequency><dac-rate>1x1</dac-rate><ols-domain><service-state>UNLOCKED</service-state></ols-domain><end-point><end-point-device>P-TOPLEFT-VXR</end-point-device><terminal-device-optical><line-port>0/0/0/0</line-port><transmit-power>-90</transmit-power></terminal-device-optical><terminal-device-packet><interface><index>0</index><ip-address><v4>20.20.10.13/30</v4></ip-address></interface></terminal-device-packet></end-point><end-point><end-point-device>P-TOPRIGHT-VXR</end-point-device><terminal-device-optical><line-port>0/0/0/0</line-port><transmit-power>-90</transmit-power></terminal-device-optical><terminal-device-packet><interface><index>0</index><ip-address><v4>20.20.10.14/30</v4></ip-address></interface></terminal-device-packet></end-point></ron-ml> | The add/drop port format - "Add/Drop port in proper format like ". In the ron->inter-layer-link list the entries are provided in an incorrect format /1/4/2/0/26,25 - instead, it should be 1/4/2/26,25.show ron inter-layer-linkinter-layer-link P-BOTTOMLEFT-VXR 0/0/0/0 { site Site6; ols-domain { network-element tcc3; optical-add-drop */1/4/2/0/26,25*; }}inter-layer-link P-BOTTOMLEFT-VXR 0/0/0/1 { site Site6; ols-domain { network-element tcc3; optical-add-drop */1/4/2/0/28,27*; }}inter-layer-link P-BOTTOMLEFT-VXR 0/0/0/2 { site Site6; ols-domain { network-element tcc3; optical-add-drop */1/4/2/0/24,23*; }}...Hi Yevgeny,Please check installation pre-requistes section, Python module Prarmiko and xmllint are particularly required by RON CFP.I did the following quick tests in your system and looks like Pramiko is missing (unless I missed your normal environment settings for local installation):(pythonEnv) nso542@iorgad-exsi-vm1:~$ netconf-console --host 10.56.58.69 --port 30666 --user admin --password cisco123 --helloYou must install the python ssh implementation paramiko in order to use ssh.(pythonEnv) nso542@iorgad-exsi-vm1:~$ pythonPython 3.8.5 (default, Jul 20 2020, 19:50:14) on linuxType "help", "copyright", "credits" or "license" for more information.>>> import paramikoTraceback (most recent call last): File "<stdin>", line 1, in <module>ModuleNotFoundError: No module named 'paramiko'>>>Problem continues, all the required components are out there I have a ask from you to prevent moving forward by tiny steps. Can you please make this payload work ? root@iorgad-exsi-vm1:~#python3.8Python 3.8.2(default, Mar 21 2020, 17:24:44)on linuxType"help", "copyright", "credits" or"license" for more information.>>> import paramiko;>>> exit();root@iorgad-exsi-vm1:~#xmllint --versionxmllint: using libxml version20903I have changed couple SIP settings in your system to get over the SIP fetch failure. Although I couldn't get the plan reached status completely but I think it will work after clearing pre-existing router config.I am not sure of your ONC topology, you probably need to verify the service-interface-point connection pairs. And, please follow Ravi advice above to configure the inter-layer-link.Before:inter-layer-link P-TOPLEFT-VXR 0/0/0/0 { ols-domain { network-element daigosim9; optical-add-drop /1/6/2/0/20,19; }}inter-layer-link P-TOPRIGHT-VXR 0/0/0/0 { ols-domain { network-element daigosim9; optical-add-drop /1/3/2/0/10,9; }}set ron inter-layer-link P-TOPLEFT-VXR 0/0/0/0After:nso542@ncs% show ron inter-layer-link P-TOPLEFT-VXR 0/0/0/0 ols-domain { network-element daigosim9; optical-add-drop 1/6/2/20,19;}nso542@ncs% show ron inter-layer-link P-TOPRIGHT-VXR 0/0/0/0ols-domain { network-element daigosim10; optical-add-drop 1/1/3/20,19;}nso542@ncs% run show ron ron-ml-plan 400Gbps-Transponder-OLS plan BACK STATUS POST ACTION TYPE NAME TRACK GOAL CODE STATE STATUS WHEN ref STATUS -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------self self false - - init reached 2021-05-25T12:11:43 - create-reached ready not-reached - - - optical-controller Optical-Controller false - RON-101 init reached 2021-05-25T16:05:48 - - cisco-ron-cfp-nano-plan-services:config-apply reached 2021-05-25T16:05:48 - - ready not-reached - - - cisco-ron-cfp-nano-plan-services:router P-TOPLEFT-VXR false - - init not-reached - - - cisco-ron-cfp-nano-plan-services:config-apply not-reached - - - ready not-reached - - - cisco-ron-cfp-nano-plan-services:router P-TOPRIGHT-VXR false - - init not-reached - - - cisco-ron-cfp-nano-plan-services:config-apply not-reached - - - ready not-reached - - -This specific problem was resolved, i will move to a new ticket on the follow up Corrected inter-layer-link issue but the setup has issue with XR routers. Yevgeny decided to close the case and moved to new setup. |
Hardware transceiver capability does not support the configured mode and bandwidth: EnvironmentDescription: UI + SSH: nso542/Public1234!Instance: Local Installation /home/nso542/RON-MLSimulation Type: VXR + ZR Emulation Service: AttachedXML FileDevices Types: Spitfires 8201Device Details: Attached Json FileDevice Credentials: admin/Public1234! | Fetch optic port details on ZR failed. Following log message from ncs-python-vm-cisco-zr-cfp.log. Seems like the ZR device name misspelled instead of VXR it is given as XVR in the payload, please fix this for both ZRs and retry.Exception during fetch optics '{P-TOPLEFT-XVR} not in /ncs:devices/deviceadmin@ncs> show devices listNAME ADDRESS DESCRIPTION NED ID ADMIN STATE----------------------------------------------------------------------------------P-BOTTOMLEFT-VXR 192.168.122.182 - cisco-iosxr-nc-7.3 unlockedP-BOTTOMRIGHT-VXR 192.168.122.4 - cisco-iosxr-nc-7.3 unlockedP-TOPLEFT-VXR 192.168.122.104 - cisco-iosxr-nc-7.3 unlockedP-TOPRIGHT-VXR 192.168.122.170 - cisco-iosxr-nc-7.3 unlockedPE-A 172.16.1.35 - cisco-iosxr-cli-7.33 unlockedPE-A-VXR 192.168.122.102 - cisco-iosxr-nc-7.3 unlockedPE-B 172.16.1.36 - cisco-iosxr-cli-7.33 unlockedPE-B-VXR 192.168.122.28 - cisco-iosxr-nc-7.3 unlockedPE-C 172.16.1.37 - cisco-iosxr-cli-7.33 unlockedPE-C-VXR 192.168.122.185 - cisco-iosxr-nc-7.3 unlockedonc-sd-team 10.56.58.69 - onf-tapi-nc-1.0 unlockedThanks,RaviHi Yevgeny,Please update the case after the issue is resolved.Thanks,VanHi Yevgeny,We notice you're using unsupported optical adapter device, PID "DP04QSDD-E30-19A".Please checktransceiver-capability for supported PIDsThanks,Vanadmin@ncs> show devices device P-TOPLEFT-VXR live-status optics-oper optics-ports optics-port Optics0/0/0/3 optics-info transceiver-infooptics-info transceiver-info date 202005optics-info transceiver-info optics-vendor-rev N/Aoptics-info transceiver-info optics-serial-no 201800148optics-info transceiver-info optics-vendor-part DP04QSDD-E30-19Aoptics-info transceiver-info optics-type "QSFPDD 400G ZRP"optics-info transceiver-info vendor-name "Acacia Comm Inc."optics-info transceiver-info oui-no 31.32.00optics-info transceiver-info optics-pid DP04QSDD-E30-19Aoptics-info transceiver-info optics-vid N/Aadmin@ncs> show devices device PE-A-VXR live-status optics-oper optics-ports optics-port Optics0/0/0/0 optics-info transceiver-infooptics-info transceiver-info date 202005optics-info transceiver-info optics-vendor-rev N/Aoptics-info transceiver-info optics-serial-no 201800148optics-info transceiver-info optics-vendor-part DP04QSDD-E30-19Aoptics-info transceiver-info optics-type "QSFPDD 400G ZRP"optics-info transceiver-info vendor-name "Acacia Comm Inc."optics-info transceiver-info oui-no 31.32.00optics-info transceiver-info optics-pid DP04QSDD-E30-19Aoptics-info transceiver-info optics-vid N/AHi Van, After upgrading to the ZR version you had recommended, have a i new error RPC error towards PE-A-VXR: unknown_element: ns2:interface-configurations/ns2:interface-configuration/ns1:optics/ns1:optics-modulationNAME: "FourHundredGigE0/0/0/0", DESCR: "Cisco QSFPDD 400G ZRP Pluggable Optics Module"PID: QDD-400G-ZRP-S , VID: ES03, SN: ACA24490072Now it a Different Error Python cb_nano_create error. Unknown error (66): cisco-ron-cfp-using-cisco-zr-template.xml:13 Expression '{$FEC}' resulted in an incompatible value 'None' for /cisco-zr-cfp:zr/dco{400Gbps-Transponder-internal P-TOPLEFT-VXR}/fecSTATUS_CODE: RON-824REASON: Failed to process and initiate terminal-device config on zr cfpCATEGORY: serviceSEVERITY: ERRORContext [name = terminal-device config state = {'service': '/cisco-ron-cfp:ron/ron-ml{400Gbps-Transponder}', 'device': 'P-TOPLEFT-VXR'}]Hi Yevgeny,It's a strange error. Please do the following so we can continue debugging your setup:<ol>Your XR router is running version7.3.15.05I while ours are7.3.15.12I. Please upgrade to7.3.15.12I or later if possible.Enable<hide-group><name>ron</name></hide-group> in ncs.confEnable python-vm logging level debug</ol>By the way, we took your service config and recreated in our setup successfully.Thanks,VanHi Van,You are missing a point. Your problem is not with XrV 9K Running 7.3.15.05I, but with Spitfire 8K Running xrv9k-full-x-7.3.2.23I PE-A Is XrV 9K and T-TOPLEFT is 8K. Your problem is with 8Ks. Here isthe proof, same service running between two 8Ks , same problem <ron-ml xmlns="http://cisco.com/ns/nso/cfp/cisco-ron"> <name>400Gbps-Transponder</name> <mode>transponder</mode> <bandwidth>400</bandwidth> <circuit-id>2</circuit-id> <grid-type>100mhz-grid</grid-type> <frequency>1951000</frequency> <dac-rate>1x1</dac-rate> <end-point > <end-point-device>P-TOPLEFT-VXR</end-point-device> <terminal-device-optical > <line-port>0/0/0/0</line-port> <transmit-power>-90</transmit-power> </terminal-device-optical> <terminal-device-packet > <interface > <index>0</index> <ip-address > <v4>20.20.10.13/30</v4> </ip-address> </interface> </terminal-device-packet> </end-point> <end-point > <end-point-device>P-TOPRIGHT-VXR</end-point-device> <terminal-device-optical > <line-port>0/0/0/0</line-port> <transmit-power>-90</transmit-power> </terminal-device-optical> <terminal-device-packet > <interface > <index>0</index> <ip-address > <v4>20.20.10.14/30</v4> </ip-address> </interface> </terminal-device-packet> </end-point></ron-ml>Hi Yevgeny,RON 0.5 doesn't support XR 7.3.2.My point was your Spitfire routers PE-A-VXR,P-TOPLEFT-VXR, and evenP-TOPRIGHT-VXR are running older build of XR 7.3.15 (05I) as compared to my working setup, which is running XR 7.3.15 (12I).I am asking you to upgrade your routers toXR 7.3.15 (12I) if possible.Thanks,VanThis is the image we found, is that ok ?8000-golden-x64-7.3.15.23I-PROD_BUILD_7_3_15_23I_DT_IMAGE.isoI am not sure about this particular image. I have uploaded a copy of 7.3.15.12I to/auto/tftpboot-users-sj/vanpham, you can pick up from there.$ md5sum 8000-golden-x64-7.3.15.12I-PROD_BUILD_7_3_15_12I_DT_IMAGE.iso 12769458a0b762137abc6502e9cd23ee 8000-golden-x64-7.3.15.12I-PROD_BUILD_7_3_15_12I_DT_IMAGE.isoPlease let me know if you have trouble downloading the image.Provide image also wont load. Can you please provide your YAML configuration forinspection <sup>yaml file attached. Please note that we're running XVR simulator on bare metal server. If you're running your simulator from a VM, there are more settings required on the hypervisor. VXR sim support alias: [email protected].</sup>What is this ?linecard_types: Yevgeny's setup is working with updated XR 7.3.15 image. |
Unable to add/edit customer in service tag of transport slicing: Hi,I'm trying to update the customer in service tags. While updating the customer, i'm getting a popup "Method failed" and logs out.Setup:userid: nsopwd: Vtsisco@123! | Hi Magesh,Are you seeing this issue in the latest M6 build?Thanks,RegiHi Regi,I have noticed this issue in below build,nso-6.1_230124-tsdn-5.0.0-M6Thanks,NaveenHi Naveen,Please try with the latest patch build nso-6.1_230206-tsdn-5.0.0-M7.tar.gz (M6+ Patch 1). This has some fixes related to the service-tags.Thanks,RegiHello, please let us know if this issue is still valid.If no response is received, ticket will be resolved EOD Sept 8th.Thank you.No further response from customer. Closing ticket. |
l3vpn topology and RT directions : When using topology (any-to-any/hub-spoke) is there a limitation or convention on the RTs directions in case we use ie-profile? For instance, I configured any-to-any service, but the direction of the RTs (configured under ie-profile) is import which is not so correct for any-to-any topology. Another example is in hub-spoke in that case, I put the RTs with import - which doesnt make sense for the hub node (also both for the spoke node). So should we expect any possible direction or NSO will limit it? attached example of hub spoke in which the RTs are with direction "both". | Hello,There is no limitation or convention on the RTs directions.The service will setup the basic topology defined by the user using the RTs, but there's no restriction if the user wants to import/export/both extra vpn-targets.Let me know if this helps.Regards,Janaki DuggiralaHello, Please let us know if this issue is resolved and if we close the ticket?If no further response is received, ticket will be closed Friday (1/6).Regards,Janaki DuggiralaClosing ticket since no further response has been received from customer. |
FQDN not working on 6.10: hi, when we add NSO provider in CrossWork with FQDN the provider stays unreachable. in prev versions (6.0, 5.76) it worked well. can you please let us know if this build support FQDN? our NSO is 10.56.58.145 (nso610/Public1234!). | Hi Idan,From the wiki, we have not changed the ncs.conf configuration between M4/M5/M5+.This looks like 6.1 nightly platform which might have triggered this. NSO CFP team does not test with FQDN for NSO Platform.NSO Platform team would be the right be place to raise this issue.ThanksSahithi |
L2vpn Route Policy Tag UI takes multiple tag-value but dry-run failed: From CNC UI, user is allow to add multiple tag-value for L2vpn Route Policy Tag. Do a dry run, the following error pops up:Reasontoo many , 2 configured, at most 1 must be configuredPath/cisco-l2vpn-routing-policy:l2vpn-routing-policy/defined-sets/tag-sets/tag-set{tet}/tag-valueSame issue if use API to create, "tag-value" is a list but when enter multiple values, the request failed with the following error:ietf-restconf:errors": { "error": [ { "error-type": "application", "error-tag": "malformed-message", "error-path": "/cisco-l2vpn-routing-policy:l2vpn-routing-policy/defined-sets/tag-sets/tag-set", "error-message": "too many /l2vpn-routing-policy/defined-sets/tag-sets/tag-set{COLOR_250}/tag-value, 2 configured, at most 1 must be configured" } ] }Should we not allow user to add multiple tag-value if not allowed? So the UI should disable the Add button once 1 tag-value is added. And the API should not be a list for "tag-value". | As discussed, the limitation should be applied to L3 and L2 behavior is as expected.This is expected behavior for L2VPN route policy |
vpn instance profile under vpn node: hi, looking on the wiki of l3vpn changes I want to know how the reference to the vpn-instance-profile is done from node. in the yang model I see some new object called - "active-vpn-instance-profiles", which has additional information under it (see attached). in the example payload however, I see there is a reference called "vpn-instance-profile" under the vpn node. the question is - do we use "vpn-instance-profile" to do the reference? and if so - can you elaborate what is the "active-vpn-instance-profiles" - and maybe even give example of payload using it? Thanks! | Hi IdanThe L3NM Model RFC update is still under progress and the payload will be corrected within next few weeks.Let us know if we are good to close the ticket for now.Thanks,Nikhilok, you can close the ticket. Update us when the model is closed. Thank you!The L3NM Model RFC update is still under progress and the payload will be corrected within next few weeks. Will update the user when the model is closed. |
NSO LSA tsdn 5.0 M7 -commands for "RPL association" removal are not created and not pushed to the device: The issue is only on NSO LSA - in NSO standalone (with the same M7) the commands for the update are pushed correctly to the device.CFS - 10.56.116.131, RFS 1 - 10.56.116.133, RFS 2 - 10.56.116.134 (credentials for all: nso/Public1234!)Steps to reproduce:1. I created l3vpn service over SR-ODN named "v6-l3vpn_114_117-420_odn" – see attached payload with ODN templates, RPLs, service. 2. After service configs were pushed to the devices (service has two endpoints on 192.168.255.114 and 192.168.255.117 devices) and ODN templates become instantiated and UP - I did (via NSO UI, same issue via CW UI) removal of export route-policy association from 192.168.255.114 endpoint – see attached snapshot with changesNow I am seeing the following issues:a) I checked the native config section - no configs are being generatedb) After pressing Commit button - NSO reported success, but configs for "export route policy" removal (or any other commands) were NOT pushed to the device.I collected logs using get_technical_support_data.sh from CFS and RFS nodes and copied them to the folder in box: | FiledHi Leonid,We were not able to reproduce the issue in our setup and can see that the config is being removed properly when removing the export route-policy association.Please help us with your system details to check this issue further.Thanks,NikhilWhich "system details" are needed?In the same NSO that I already mentioned (10.56.116.131) and the same service - I tried again and there no device commands shown in "native config":the only thing that is shown is:rfs-1<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="1"> <edit-config xmlns:nc="urn:ietf:params:xml:ns:netconf:base:1.0"> <target> <running/> </target> <test-option>test-then-set</test-option> <error-option>rollback-on-error</error-option> <with-inactive xmlns="http://tail-f.com/ns/netconf/inactive/1.0"/> <config> <flat-L3vpn xmlns="http://cisco.com/ns/nso/fp/examples/cisco-tsdn-flat-L3vpn-internal"> <name>L3NM-v6-l3vpn_114_117-420_odn-internal</name> <endpoint-name>192.168.255.114_114</endpoint-name> <endpoint> <endpoint-name>192.168.255.114_114</endpoint-name> <sr-te> <odn> <route-policy xmlns:nc="urn:ietf:params:xml:ns:netconf:base:1.0" nc:operation="delete"> <route-policy-name>l3-rpl-114_305</route-policy-name> </route-policy> </odn> </sr-te> <vrf> <address-family> <address-family>ipv6</address-family> <export-route-policy-name xmlns:nc="urn:ietf:params:xml:ns:netconf:base:1.0" nc:operation="delete"/> </address-family> </vrf> </endpoint> </flat-L3vpn> </config> </edit-config></rpc>If commit is pressed the "removal" commands are not being pushed to the device also.Hi Leonid,As discussed during our meetings, there was some issue in the setup, the service was not owning the config and hence the config on the device was not getting removed. We did a cleanup of the service, cleared the config on the device and then created the service again which was working fine as expected.The configs are now getting removed properly from the device while removing the association of route policy.Hence closing the issue.Thanks,NikhilCleaned up the service and config and the functionality was working fine after that. |
L3VPN with SRv6 payload in xml format: reference to the following wiki and include this in the L3vpn payload.Import from CNC UI, got the following error:Unknown element: srv6 in /l3nm:l3vpn-ntw/l3nm:vpn-services/l3nm:vpn-service/l3nm:vpn-nodes/l3nm:vpn-node/l3nm:active-vpn-instance-profiles/cisco-l3nm:srv6Can you share the right format to use in the xml file?Payload attached. | Hi Crystal,You can find the XML format for SRv6 for L3NM in the above sample payloadThanksSahithiUpdated the payload with the following by referring to the suggested wiki:<srv6 xmlns="http://cisco.com/ns/nso/fp/examples/cisco-l3vpn-ntw"> <address-family> <name>ipv6</name> <locator-name>ALG0r5</locator-name> </address-family></srv6>Still fail to load from both NSO UI and CNC UI. Updated payload and error message from NSO UI attached. Hi Crystal,Srv6 is inside vpn-instance-profile, the payload you have does not reflect that and thus the error. <active-vpn-instance-profiles> <vpn-instance-profile> <profile-id>ie_01</profile-id> <srv6 xmlns="http://cisco.com/ns/nso/fp/examples/cisco-l3vpn-ntw"> <address-family> <name>ipv4</name> <locator-name>locv4</locator-name>ThanksSahithiThanks Sahithi. It works after moving the srv6 inside vpn-instance-profile. Thanks again for the help. |
Got 404 error when accessing tsdn links in github: The links for CNC-145 and CNC-146 in github used to work, but now returns 404 not found error. Do you know if the path changes? Or I need permission to access?Device Configuration Reference (CNC-145) Model Reference Device Configuration Reference (CNC-146) Engineering and LCM on SRv6/L2VPN EVPN VPWS over SRv6 | Hi Crystal,It seems like the access list for this private repo was reset. Would you be able to provide a list of user id (or group) that require access to this repo?Thanks,Isaac KimThanks Isaac.Can you do it for cnc-qa ? If not, I can provide the list.Thanks.-CrystalThese config repos are open for readonly by all group. Your user has all required rights, please check.Requested user to check with EngIT team for access issues. Tried by adding individual user id for repo, still same error.Crystal raised ticket with EngIT - Hi Crystal, seems like expected resolution from EngIT team is Jan 20. Please let us know if you have any issues with access tomorrow. Otherwise we will close the ticket if there is no response.Hi Isaac, Looks like I can access this link: But can not access the following 2 links:Thanks.-CrystalHi Crystal,Those last two links are invalid as the directory name has been corrected recently.Here are the two links again with the new change:Please let me know if you cannot access these links or if everything is okay.Thanks,Isaac KimThanks Isaac,The 2 new links work good. Thanks for the help.-Crystal |
y1731 - M6 - SMAN ID validation error. - errors: reason: is not configured. paths: /ralloc:resource-pools/idalloc:id-pool{sman-id-pool}/range/start. path: /ralloc:resource-pools/idalloc:id-pool{sman-id-pool}/range/start: Hi,Attached l2vpn EVPn with Y1731 enabled payload.tried confiugred , but facing error as below.,errors: reason: is not configured. paths: /ralloc:resource-pools/idalloc:id-pool{sman-id-pool}/range/start. path: /ralloc:resource-pools/idalloc:id-pool{sman-id-pool}/range/starti have configured resource pool via NSO UI . | Hi Arun, Please load merge config/xr-sman-id-resource-pool.xml as indicating in the M6 wikiRegards,LinhPlease see my previous commentHi Linh,,Thanks for the update. i have followed .in this we didnt have that particular step.i will try as mentioned in Hi LInh,it worked after load merge config/xr-sman-id-resource-pool.xml .if possible, please add this step in the wikipage Thanks,Arun.M.GHi Arun,SMAN pool is only need for L2VPN/L2NM service when Y1731 is configured. That is why it is put under L2VPN/L2NM.Putting this information under system install main page would make people more confusing.Regards,Linh |
NSO Plan errors: Deployed the following RON-ML configuration:ron ron-ml agg1_c1mode transponderbandwidth 400ols-domain service-state UNLOCKEDend-point agg1 terminal-device-optical line-port 0/0/0/0 terminal-device-packet interface 0 ip-address v4 1.1.1.1/31 !!end-point c1 terminal-device-optical line-port 0/0/0/0 ols-domain end-point-state UNLOCKED terminal-device-packet interface 0 ip-address v4 1.1.1.2/31 !!!And were seeing the following errors, need assistance in debugging:do show ron ron-ml agg1_c1 log log-entrylog log-entry 2022-02-02T09:56:45.554372+00:00 type service-modified level error message "Error running action for side-effect item /cisco-ron-cfp:ron/ron-ml-plan{agg1_c1}/plan/component{ncs:self self}/state{ncs:init}: Python cb_action error. Failed to retrieve/validate SIPs"log log-entry 2022-02-02T12:25:20.134264+00:00 type service-modified level error message "Error running action for side-effect item /cisco-ron-cfp:ron/ron-ml-plan{agg1_c1}/plan/component{ncs:self self}/state{ncs:init}: Python cb_action error. Failed to retrieve/validate SIPs"log log-entry 2022-02-02T12:26:25.986888+00:00 type service-modified level error message "Error running action for side-effect item /cisco-ron-cfp:ron/ron-ml-plan{agg1_c1}/plan/component{ncs:self self}/state{ncs:init}: Python cb_action error. Failed to retrieve/validate SIPs" | Hi Ulfat,In order to reduce the turn-around time, please include the following information if you can when reaching out for support:<ol>Device type and version used for testingAdd clear steps to reproduce an issue this includes details if some steps were done through NSO UI/CLI or through CNC UI, details on commit options used, order in which payloads were pushed, plan status in between, etc.All relevant payloads.NSO logs including trace if there was something pushed to the deviceIn some cases, wed like to understand the use-case where we see users performing certain actions especially when some steps are done through NSO UI/CLI.</ol>In this case,NSO logs will be very helpful for us to understand the issue.Device Type ; Version: RP/0/RP0/CPU0:c1#show versionThu Feb 3 19:21:39.358 UTCCisco IOS XR Software, Version 7.4.1.06I LNTCopyright (c) 2013-2020 by Cisco Systems, Inc.Build Information: Built By : gopalk2 Built On : Sun Nov 15 19:25:55 UTC 2020 Build Host : iox-lnx-053 Workspace : /auto/iox-lnx-053-san1/nightly_xr-dev/201115B_8000/ws Version : 7.4.1.06I Label : 7.4.1.06Icisco 8201 (VXR) processor with 16GB of memoryc1 uptime is 2 days, 1 hour, 34 minutesCisco 8201 1RU ChassisStep 1. Added ONC to NSO, verified connectivity and synched from:devices device oncaddress 10.48.71.227port 30666authgroup ONCdevice-type netconf ned-id onf-tapi-nc-1.0connect-retries attempts 5trace falseout-of-sync-commit-behaviour acceptstate admin-state unlockedStep 2. Configured Inter-Link-Layershow running-config ron inter-layer-linkron inter-layer-link agg1 0/0/0/0site Smolenskols-domain network-element ROADM1ols-domain optical-add-drop 1/2002/1/1,2ols-domain optical-controller onc!ron inter-layer-link agg1 0/0/0/1ols-domain network-element ROADM1ols-domain optical-add-drop 1/2004/1/2,1ols-domain optical-controller onc!ron inter-layer-link agg2 0/0/0/0ols-domain network-element ROADM1ols-domain optical-add-drop 1/2002/1/4,3ols-domain optical-controller onc!ron inter-layer-link agg2 0/0/0/1ols-domain network-element ROADM1ols-domain optical-add-drop 1/2004/1/4,3ols-domain optical-controller onc!ron inter-layer-link agg3 0/0/0/0ols-domain network-element ROADM3ols-domain optical-add-drop 1/2002/1/2,1ols-domain optical-controller onc!ron inter-layer-link agg3 0/0/0/1ols-domain network-element ROADM3ols-domain optical-add-drop 1/2004/1/2,1ols-domain optical-controller onc!ron inter-layer-link agg4 0/0/0/0ols-domain network-element ROADM3ols-domain optical-add-drop 1/2002/1/4,3ols-domain optical-controller onc!ron inter-layer-link agg4 0/0/0/1ols-domain network-element ROADM3ols-domain optical-add-drop 1/2004/1/4,3ols-domain optical-controller onc!ron inter-layer-link c1 0/0/0/0site StPetersburgols-domain network-element ROADM2ols-domain optical-add-drop 1/2002/1/1,2ols-domain optical-controller onc!ron inter-layer-link c1 0/0/0/1ols-domain network-element ROADM2ols-domain optical-add-drop 1/2004/1/2,1ols-domain optical-controller onc!ron inter-layer-link c1 0/0/0/3ols-domain network-element ROADM2ols-domain optical-add-drop 1/2006/1/2,1ols-domain optical-controller onc!ron inter-layer-link c2 0/0/0/0ols-domain network-element ROADM2ols-domain optical-add-drop 1/2002/1/4,3ols-domain optical-controller onc!ron inter-layer-link c2 0/0/0/1ols-domain network-element ROADM2ols-domain optical-add-drop 1/2004/1/4,3ols-domain optical-controller onc!ron inter-layer-link c2 0/0/0/3ols-domain network-element ROADM2ols-domain optical-add-drop 1/2006/1/4,3ols-domain optical-controller onc!ron inter-layer-link c3 0/0/0/0ols-domain network-element ROADM4ols-domain optical-add-drop 1/2004/1/2,1ols-domain optical-controller onc!ron inter-layer-link c3 0/0/0/1ols-domain network-element ROADM4ols-domain optical-add-drop 1/2002/1/2,1ols-domain optical-controller onc!ron inter-layer-link c3 0/0/0/3ols-domain network-element ROADM4ols-domain optical-add-drop 1/2006/1/2,1ols-domain optical-controller onc!ron inter-layer-link c4 0/0/0/0ols-domain network-element ROADM4ols-domain optical-add-drop 1/2004/1/4,3ols-domain optical-controller onc!ron inter-layer-link c4 0/0/0/1ols-domain network-element ROADM4ols-domain optical-add-drop 1/2002/1/4,3ols-domain optical-controller onc!ron inter-layer-link c4 0/0/0/3ols-domain network-element ROADM4ols-domain optical-add-drop 1/2006/1/4,3ols-domain optical-controller onc!Step 3. Configured RON-ML Service:show running-config ron ron-mlron ron-ml agg1_c1mode transponderbandwidth 400ols-domain service-state UNLOCKEDend-point agg1 terminal-device-optical line-port 0/0/0/0 ols-domain end-point-state UNLOCKED terminal-device-packet interface 0 !!end-point c1 terminal-device-optical line-port 0/0/0/0 ols-domain end-point-state UNLOCKED terminal-device-packet interface 0 !!!step 4. view the Ron-ml-plan Information, and error is observed.For the logs please can you be specific as to what logs you require, no device trace is available as the plan doesn't move to the device config apply.Hi Ulfat,Thanks for providing the above info. For logs, we would probably just needncs-python-vm-cisco-zr-cfp.log andncs-python-vm-cisco-ron-cfp.log.As requested: Linmao, we found that the original issues was related to a incorrect transponder PID value being shown by the VXR device. When we fixed that issue we were able to progress further. However now we receive the following errror:root@ncs(config)# *** ALARM service-activation-failure: RPC error towards agg4: operation_failed: for ns2:interface-configurations/ns2:interface-configuration/ns1:optics/ns1:optics-transmit-power: Invalid argument: Entered tx power not supported by optics. Range supported by the platform is -100 to 10root@ncs(config)# do show running-config ron ron-ml agg4_c2ron ron-ml agg4_c2mode transponderbandwidth 400ols-domain service-state UNLOCKEDend-point agg4 terminal-device-optical line-port 0/0/0/0 ols-domain end-point-state UNLOCKED terminal-device-packet interface 0 !!end-point c2 terminal-device-optical line-port 0/0/0/1 ols-domain end-point-state UNLOCKED terminal-device-packet interface 0 !!!ron inter-layer-link agg4 0/0/0/0ols-domain network-element ROADM3ols-domain optical-sip 5e3c96ff-8c52-3ac8-b281-c4e8fa60e37bols-domain optical-controller onc!ron inter-layer-link c2 0/0/0/1ols-domain network-element ROADM2ols-domain optical-sip b6ac904f-2b0d-3b02-b12b-9ccf57e19277ols-domain optical-controller onc!Can you suggest a way to see what tx power value is being pushed to CNC as we get the following errors reported in the inc-restconf.log:cnc-restconf.log:4-Feb-2022::12:33:51.395 usid=41512 tid=236628 datastore=running context=cli device=c2 NETCONF error reply: RPC error towards c2: operation_failed: for ns2:interface-configurations/ns2:interface-configuration/ns1:optics/ns1:optics-transmit-power: Invalid argument: Entered tx power not supported by optics. Range supported by the platform is -100 to 10cnc-restconf.log:4-Feb-2022::12:33:51.395 usid=41512 tid=236628 datastore=running context=cli device=agg4 NETCONF error reply: RPC error towards agg4: operation_failed: for ns2:interface-configurations/ns2:interface-configuration/ns1:optics/ns1:optics-transmit-power: Invalid argument: Entered tx power not supported by optics. Range supported by the platform is -100 to 10cnc-restconf.log:4-Feb-2022::13:07:56.672 usid=42744 tid=238902 datastore=running context=cli device=agg4 NETCONF error reply: RPC error towards agg4: operation_failed: for ns2:interface-configurations/ns2:interface-configuration/ns1:optics/ns1:optics-transmit-power: Invalid argument: Entered tx power not supported by optics. Range supported by the platform is -100 to 10cnc-restconf.log:4-Feb-2022::13:07:56.686 usid=42744 tid=238902 datastore=running context=cli device=c2 NETCONF error reply: RPC error towards c2: operation_failed: for ns2:interface-configurations/ns2:interface-configuration/ns1:optics/ns1:optics-transmit-power: Invalid argument: Entered tx power not supported by optics. Range supported by the platform is -100 to 10cnc-restconf.log:4-Feb-2022::13:21:54.114 usid=43298 tid=240316 datastore=running context=cli device=c2 NETCONF error reply: RPC error towards c2: operation_failed: for ns2:interface-configurations/ns2:interface-configuration/ns1:optics/ns1:optics-transmit-power: Invalid argument: Entered tx power not supported by optics. Range supported by the platform is -100 to 10cnc-restconf.log:4-Feb-2022::13:21:54.121 usid=43298 tid=240316 datastore=running context=cli device=agg4 NETCONF error reply: RPC error towards agg4: operation_failed: for ns2:interface-configurations/ns2:interface-configuration/ns1:optics/ns1:optics-transmit-power: Invalid argument: Entered tx power not supported by optics. Range supported by the platform is -100 to 10cnc-restconf.log:4-Feb-2022::13:25:58.397 usid=43636 tid=241372 datastore=running context=cli device=c2 NETCONF error reply: RPC error towards c2: operation_failed: for ns2:interface-configurations/ns2:interface-configuration/ns1:optics/ns1:optics-transmit-power: Invalid argument: Entered tx power not supported by optics. Range supported by the platform is -100 to 10cnc-restconf.log:4-Feb-2022::13:25:58.411 usid=43636 tid=241372 datastore=running context=cli device=agg4 NETCONF error reply: RPC error towards agg4: operation_failed: for ns2:interface-configurations/ns2:interface-configuration/ns1:optics/ns1:optics-transmit-power: Invalid argument: Entered tx power not supported by optics. Range supported by the platform is -100 to 10cnc-restconf.log:4-Feb-2022::13:30:19.768 usid=43906 tid=242322 datastore=running context=cli device=c2 NETCONF error reply: RPC error towards c2: operation_failed: for ns2:interface-configurations/ns2:interface-configuration/ns1:optics/ns1:optics-transmit-power: Invalid argument: Entered tx power not supported by optics. Range supported by the platform is -100 to 10cnc-restconf.log:4-Feb-2022::13:30:19.768 usid=43906 tid=242322 datastore=running context=cli device=agg4 NETCONF error reply: RPC error towards agg4: operation_failed: for ns2:interface-configurations/ns2:interface-configuration/ns1:optics/ns1:optics-transmit-power: Invalid argument: Entered tx power not supported by optics. Range supported by the platform is -100 to 10Hi Ulfat,For transmit power, you can choose to determine the value in your ron-ml payload or use a default value in transceiver-capability table or use an optical controller PCE to determine. The transmit power that you manually set takes priority. If no transmit power is provided, the service uses the value from the transceiver-capability table. If no value in the table is availabe, the service will use the value populated by the optical controller (service will multiply the value by 10). The configured transmit-power is populated as part of ron ron-ml ron-data end-point.To check thetransceiver-capability table:admin@ncs% show ron transceiver-capabilityTo check thevalue populated by the optical controller:admin@ncs> show context connectivity-context connectivity-service-oper-data <uuid>To checkconnectivity-service uuid:admin@ncs> show ron uuid-lookupHope this helps.Hi Linmao, I tried to overwrite the values in the payload:ron ron-ml agg4_c2mode transponderbandwidth 400ols-domain service-state UNLOCKEDend-point agg4 terminal-device-optical line-port 0/0/0/0 terminal-device-optical transmit-power -10 ols-domain end-point-state UNLOCKED terminal-device-packet interface 0 !!end-point c2 terminal-device-optical line-port 0/0/0/1 ols-domain end-point-state UNLOCKED terminal-device-packet interface 0 !!!But the plan still fails with the same error below... can you suggest a plan to identify what is causing the error?plan failedplan error-info message "RPC error towards agg4: operation_failed: for ns2:interface-configurations/ns2:interface-configuration/ns1:optics/ns1:optics-transmit-power: Invalid argument: Entered tx power not supported by optics. Range supported by the platform is -100 to 10"plan error-info log-entry /ron/ron-ml/log/log-entry BACK STATUS POST ACTIONTIME TYPE NAME TRACK GOAL CODE STATE STATUS WHEN ref STATUS-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------2022-02-04T13:53:28 self self false - RON-198 init failed 2022-02-04T13:53:27 - not-reached ready not-reached - - - optical-controller Optical-Controller false - RON-200 init reached 2022-02-04T13:53:07 - - cisco-ron-cfp-nano-plan-services:config-apply reached 2022-02-04T13:53:07 - - ready reached 2022-02-04T13:53:27 - - cisco-ron-cfp-nano-plan-services:router agg4 false - RON-101 init reached 2022-02-04T13:53:27 - - cisco-ron-cfp-nano-plan-services:config-apply reached 2022-02-04T13:53:27 - - ready not-reached - - - cisco-ron-cfp-nano-plan-services:router c2 false - RON-101 init reached 2022-02-04T13:53:27 - - cisco-ron-cfp-nano-plan-services:config-apply reached 2022-02-04T13:53:27 - - ready not-reached - - -2022-02-04T13:53:28 self self false - RON-198 init failed 2022-02-04T13:53:27 - not-reached ready not-reached - - - optical-controller Optical-Controller true init RON-110 init reached 2022-02-04T13:53:07 - - cisco-ron-cfp-nano-plan-services:config-apply not-reached - - - ready not-reached - - - cisco-ron-cfp-nano-plan-services:router agg4 false - - init not-reached - - - cisco-ron-cfp-nano-plan-services:config-apply not-reached - - - ready not-reached - - - cisco-ron-cfp-nano-plan-services:router c2 false - - init not-reached - - - cisco-ron-cfp-nano-plan-services:config-apply not-reached - - - ready not-reached - - -Hi Ulfat,Could you please share the logs (ncs-python-vm-cisco-ron-cfp.log, ncs-python-vm-cisco-zr-cfp.log, ncs-python-vm-cisco-optical-cfp.log and devices netconf trace logs) after you overwrited the value?Please also feel free to setup a meeting to debug with us if you like. Not sure if the logs files were not uploaded correctly but I'm sure I uploaded these before....Hi Ulfat,From the plan you pasted above, I believe you are using devices:agg4 and c2 for serviceagg4_c2. But I can't find the device trace logs for these 2 devices from the file you uploaded. Could you please also include them?Hi Ulfat,Are you still having the above issue? If so, please provide us the requested info as mentioned above or we will close this ticket in a week.Thanks.Closing the ticket as no response from submitter is received for more than a week. Please open a new ticket if you need any further assistance. |
WEB UI SSL enablement - PAM authentication failed : We have avery strange behavior with authentication in local installation. One Ienable ssl on webui, system user (that I run the nso with) stops working, and I am able to login with admin only!<INFO>2-Feb-2022::20:29:25.400 nso-ucs-haim1 ncs: audit user: /0local authentication failed via webui from 10.56.235.30:59671 with http: no such local user<INFO>2-Feb-2022::18:59:47.911 nso-ucs-haim1 ncs: audit user: /0 PAM authentication failed via rest from10.56.57.59:11201 with https: phase auth, timeoutThisproblem started with nso57, and it is a problem, since CNC uses https Youtake this flag out, and we are back in business 10.56.58.197nso57/Public1234!cd~/.0.0 | Looking in to the issue.Thanks,NishadHi Yevgeny,Looks like port 8888 is running many other processes which caused the issue.We changed the port and it started working fine.Thanks,NishadClosing ticket since no response from submitter assuming changing port number resolved the issue |
Discussion on Y1731 Profile disassociation and stale entries in AA: We have two cdets raised CSCvz74193 and CSCvz74161. While performing test as per I-comments, we land up in stale subservice in AA. | I would like to mention, reporter requested for meeting at 9:30PM IST (9:00AM PST Wednesday Sept 29) to discuss this issue. If this does not work, please contact Sampath. Please provide some more details about the specific issue we discussed on call (y-1731 profile definition behavior on device). Thanks.No Need of meeting, I tested as per Issac comments, AA side we are seeing stale entries, that we will discuss with AA team. You can move the bug to respective state.Isaac is on PTO today, hence I am replying to this ticket. As discussed on teams, you would be creating a new cdets for AA team and we can mark both these cdets:CSCvz74193, CSCvz74161 to J state.This is not a CFP issue. Submitter will reach out to AA team. |
Im facing some configuration issue suddenly in the working RON setup: Please find the error below:Python cb_nano_create error. Unknown error (66): cisco-ron-cfp-using-cisco-zr-template.xml:13 Expression '{$FEC}' resulted in an incompatible value 'None' for /cisco-zr-cfp:zr/dco{BOTTOMLEFT_BOTTOMRIGHT_400_TR_OLS-internal P-BOTTOMLEFT-VXR}/fec STATUS_CODE: RON-824 REASON: Failed to process and initiate terminal-device config on zr cfp CATEGORY: service SEVERITY: ERROR Context [name = terminal-device config state = {'service': '/cisco-ron-cfp:ron/ron-ml{BOTTOMLEFT_BOTTOMRIGHT_400_TR_OLS}', 'device': 'P-BOTTOMLEFT-VXR'}]Even after setting the transciever capabilty I'm facing this issue | Can you please attach ncs-python-vm-cisco-ron-cfp.log and ncs-python-vm-cisco-zr-cfp.log files.Can you write down the procedure that led to this error and also please upload your payloadPlease find the payload here:{ "cisco-ron-cfp:ron-ml": { "name": "BOTTOMLEFT_BOTTOMRIGHT_400_TR_OLS", "mode": "transponder", "bandwidth": "400", "grid-type": "100mhz-grid", "circuit-id": "3", "frequency": 1951000, "dac-rate": "1x1", "end-point": [ { "end-point-device": "P-BOTTOMLEFT-VXR", "terminal-device-optical": { "line-port": "0/0/0/3", "transmit-power": -90 }, "terminal-device-packet": { "interface": [ { "index": 0, "ip-address": { "v4": "20.20.10.13/30" } } ] } }, { "end-point-device": "P-BOTTOMRIGHT-VXR", "terminal-device-optical": { "line-port": "0/0/0/3", "transmit-power": -90 }, "terminal-device-packet": { "interface": [ { "index": 0, "ip-address": { "v4": "20.20.10.14/30" } } ] } } ] }} Reached out to Aarthi for a call. The tar attached is not extractable. Hi Aarthi,Is the issue resolved? Please let us know if you're still needing suport; otherwise, we will close this ticket in 3 days.Dismiss the case for now as there's no feedback from the reporter despite repeated attempts to contact. Please open new case if issue is seen again. |
NSO error recovery audit log - wrong action name: The audit log under /var/log/ncs on NSO VM shows different name for some actions. "Sync-from", "Sync-to" shows "error-recovery""Re-deploy Dry Run" shows "re-deploy""Re-deploy Reconcile" shows "re-deploy"The same action name should be seen the audit log for easy debugging.Attached is the actions with audit log messages.Please let me know if there is a concern to open a CDETS. | Hi Crystal, Please provide NSO API invoked from CNC UI for the each of scenarios that you reported the issue.Thanks,LinhThanks Mukul.Hi Linh,From end users point of view, they will not know the internal implementation. All of the actions are error recovery includes the one highlighted the ones have matching action names. It would be great if we can add more details to distinguish different actions. And that is the purpose of having audit log.What do you think?Thanks.-CrystalFrom: "Mukul Shukla (mukshukl)" <[email protected]>Date: Friday, August 6, 2021 at 1:07 PMTo: Crystal Yu <[email protected]>, "nso-ned-jira.gen -X (Generic User at Cisco)" <[email protected]>Cc: "cat-ui-dev(mailer list)" <[email protected]>Subject: Re: NSO error recovery audit log - wrong action nameHello Crystal,I think this makes sense. The sync-from and sync-to are actually part of error-recovery actions of a service and sync-from and sync-to are actually just sync directions being passed -Here is a sample call for L3VPN for sync-to We call - /ietf-l3vpn-ntw:l3nm-actions/error-recoveryWith payload - {"sync-direction": "sync-to" , "service": serviceName}For sync-from the payload changes to reflect sync-direction, the URL doesnt. So its actually an error recovery call.For Redeploy maybe the message can be improved from NSO, but here again the call is always to redeploy We POST to serviceKey + "/re-deploy". Only the payload (type of redeploy) changes in payload Normal redeploy no payloadRe-deploy Dry run - { "dry-run": { "outformat": "cli" } }Redeploy Reconcile - { "reconcile": { "keep-non-service-config":{} } }Thanks,MukulFrom: Crystal Yu (cyu2000) <[email protected]>Date: Friday, August 6, 2021 at 12:11 PMTo: nso-ned-jira.gen -X (Generic User at Cisco) <[email protected]>, Mukul Shukla (mukshukl) <[email protected]>Subject: Re: NSO error recovery audit log - wrong action nameHi Linh,I am including Mukul here to help me for the information you requested.Hi Mukul,I tried all the error recovery actions from Provision UI page. And found some of them does not have the right action name in NSO audit log. Linh is looking for the APIs invoked from CNC UI. Can you help to share the info.? Mainly for the highlighted ones.Here is the description for the JSD request in case you can not access the link:The audit log under /var/log/ncs on NSO VM shows different name for some actions."Sync-from", "Sync-to" shows "error-recovery""Re-deploy Dry Run" shows "re-deploy""Re-deploy Reconcile" shows "re-deploy"The same action name should be seen the audit log for easy debugging.Attached is the actions with audit log messages.Please let me know if there is a concern to open a CDETS.Thanks.-CrystalHi Crystal,I'm not too sure what the ask here is? Are the actions requested incorrect or just not showing up properly in the audit.log?First of all let me say, that T-SDN does not manage `/var/log/ncs/audit.log`, this log is managed by the NSO Platform as such if there are issues with the logging an RT with the platform team would need to be filed; however, ifthe issue is incorrect actions are being requested, then that means the at the NB interface which is sending the wrong commands to NSO as these are POST requests.As far as incorrect logging is concerned, I would need reproduction steps with NSO directly since I was unable to reproduce the issue by manually sending POST requests.<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"><pre>curl -X POST http://127.0.0.1:8080/restconf/data/cisco-sr-te-cfp:sr-te/cisco-sr-te-cfp-sr-policies:policies/policy=SRv6-701-igp-absolute-disjoint/re-deploy --user admin:admin</pre></div></div>audit.log output<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"><pre><INFO> 9-Aug-2021::09:03:32.321 pop-os ncs[39559]: audit user: admin/153 RESTCONF: request with http: POST /restconf/data/cisco-sr-te-cfp:sr-te/cisco-sr-te-cfp-sr-policies:policies/policy=SRv6-701-igp-absolute-disjoint/re-deploy HTTP/1.1 trace-id=299decb2-bfa0-465a-824d-44bef4219945 <INFO> 9-Aug-2021::09:03:32.326 pop-os ncs[39559]: audit user: admin/155 assigned to groups: admin <INFO> 9-Aug-2021::09:03:32.326 pop-os ncs[39559]: audit user: admin/155 created new session via rest from 127.0.0.1:43212 with http <INFO> 9-Aug-2021::09:03:32.592 pop-os ncs[39559]: audit user: admin/155 terminated session (reason: normal) <INFO> 9-Aug-2021::09:03:32.592 pop-os ncs[39559]: audit user: admin/153 terminated session (reason: normal) <INFO> 9-Aug-2021::09:03:32.592 pop-os ncs[39559]: audit user: admin/153 RESTCONF: response with http: HTTP/1.1 /restconf/data/cisco-sr-te-cfp:sr-te/cisco-sr-te-cfp-sr-policies:policies/policy=SRv6-701-igp-absolute-disjoint/re-deploy 204 duration 307963 ms trace-id=299decb2-bfa0-465a-824d-44bef4219945</pre></div></div>Thanks,RegiI should say the above output was created using NSO 5.5.2.3. It would be good if you can provide the details outlined for support: Thanks,RegiHi Reginald,We have a test case to test audit log for NSO actions triggered from CNC UI. What I am checkin is the audit log message itself not the action request is incorrect. Based on the information you shared. The audit log has to be handled by NSO team. Do you happened to know the CDETS's product and component to use for NSO platform.Hi Crystal,Let's first narrow down the issue and see if its actually a bug with NSO or not. Can you please share a screenshot of the action information in CNC UI?Submitter wanted logging for not just the RESTCONF API, but the payload pushed as well. This sort of logging can be enabled but should be done so in production settings.<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"><pre>from ncs.conf(5):/ncs-config/logs/webui-access-log/traffic-log (boolean) [false] Is either true or false. If true, all HTTP(S) traffic towards the embedded Web server is logged in a log file named traffic.trace. The log file can be used to debugging JSON-RPC/REST/RESTCONF. Beware: Do not use this log in a production setting. This log is not enabled by default and is not rotated, i.e. use logrotate(8).</pre></div></div>The log output is as follows:1. Send RESTCONF POST request with payload<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"><pre>curl -X POST http://127.0.0.1:8080/restconf/data//cisco-sr-te-cfp:sr-te/cisco-sr-te-cfp-sr-policies:policies/policy=SR-CLI-DYNAMIC/re-deploy --user admin:admin -d {"dry-run":{"outformat":"cli"}} --header "Content-Type:application/yang-data+json"</pre></div></div>2. Output from logs/trace_.traffic<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"><pre>POST /restconf/data//cisco-sr-te-cfp:sr-te/cisco-sr-te-cfp-sr-policies:policies/policy=SR-CLI-DYNAMIC/re-deploy HTTP/1.1 Accept: */*^M Host: 127.0.0.1:8080^M User-Agent: curl/7.74.0^M Content-Length: 31^M Content-Type: application/yang-data+json^M Authorization: Basic YWRtaW46YWRtaW4=^M [2021-08-10 13:42:56.940] ===== CLI -> SRV ===== {"dry-run":{"outformat":"cli"}} [2021-08-10 13:42:57.327] ===== SRV -> CLI ===== HTTP/1.1 200 OK^M Date: Tue, 10 Aug 2021 20:42:56 GMT^M Cache-Control: private, no-cache, must-revalidate, proxy-revalidate^M Content-Length: 69^M Content-Type: application/yang-data+json^M X-Cisco-NSO-Trace-ID: 867356d5-7953-42da-af8d-d7720c8b4c19^M Pragma: no-cache^M Content-Security-Policy: default-src 'self'; block-all-mixed-content; base-uri 'self'; frame-ancestors 'none';^M Strict-Transport-Security: max-age=15552000; includeSubDomains^M X-Content-Type-Options: nosniff^M X-Frame-Options: DENY^M X-XSS-Protection: 1; mode=block^M ^M { "cisco-sr-te-cfp-sr-policies:output": { "cli": { } } }</pre></div></div> |
Re: Actions Supported for a given service: Ref Email - Re: Actions Supported for a given service -As per feature - F108236 - CNC-117: Select Usability Improvements in Service Provisioning . CNC UI implemented an option to execute the following actions on each service via restconf calls (in attachment)As we have noted so far there are cases like when the service is in zombie state certain actions are not applicable.I have two questions here Are there any situations (like zombie state) when these actions are not applicable?Is there any way for CNC to detect these states? | **For a service to go into a zombie state, it must be deleted first and when you delete a service then all of the service configurations are removed from NSO CDB; therefore, any actions which go down this service config path to trigger said action will fail as the config path does not exist.Can CNC check if the service path exists before executing the service actions?Thanks. My question is are you aware of anything else apart from Zombie state when these actions are not applicable?Attaching the email regarding the issue discussion. |
How to differentiate from get_Schema API response to load leafref key in different cases: Previously prov-ui editor renders any leafref as a text field with validation that user entered data exists (default behavior ).Now we have different cases to render on prov-ui editor ,As prov-ui editor is dynamic and generic way to load the modal we need help in identify the solution to differentiate between two cases.some use cases prov-ui need to add a custom dropdown as a special case e.g in case of VPN-Profiles.Based on initial analysis To handle these cases generically we have added a check based on--> IN case, If we have ( is_leafref = true , kind= key ) without any value we load it as a custom drop-down--> IN case, If we have is_leafref = true , kind= key and has value =ct-logging we load it as text field with validation that user entered ( default behavior).Just want to confirm is this valid check and enough to handle for all the case or is there a way we can differentiate between two to handle both cases except adding these checks.NOTE: added the screen shot for these KEY response form get_schema JSON RPC call. | Hi Kirandeep,In a scenario, where the leafref points to value A,B,C and D.If you have a model without any value field, then yes the drop down list would be correct.If the model shows a value chosen from the leafref then yes, the textbox/text-field would be the right choice to populate the value.Let me know if this helps?hey janaki, Thanks for confirming, so we can go head and add that check based on value felid we populate the dropdown and text for leafref pointsQuick question - how will you be populating the drop down? What field will be used?In case of Leafref as kind key we are using custom modal select field to populate the dropdown on selection we do validate by calling method: "exists" in JSON RPC call.Okay, thank you. Please let me know if your query is answered and if I may close this ticket.yes we can close this ticket got the confirmation needed Customer requested feedback wit design question. Feedback/Clarification was provided. |
fail to create L2 P2P dedicated slice : Create an L2 P2P dedicated slice from CNC UI. It failed with the following error:Problem while provisioning the slice[{"Message":"/network-slice-services/slice-service{SL-L2-P2P-Dedi-690}/cisco-nss:shared: the 'when' expression "derived-from-or-self(../isolation, 'ietf-nss:service-isolation-dedicated')" failed","nsoResponse":"/network-slice-services/slice-service{SL-L2-P2P-Dedi-690}/cisco-nss:shared: the 'when' expression "derived-from-or-self(../isolation, 'ietf-nss:service-isolation-dedicated')" failed"}]I do not have payload for the slice, but attach the screenshots for all the data entered for creating slice. Also attached the payload for creating ODN and NSST. build combo: infra 293 + CDG 441 + COE 171 + CAT 151 + NSO 6.1.2 drop5 | Hi Crystal, The error message seems to indicate a validation was triggered due to incorrect config being present in the payload.In detail, this validation is present on the shared container as below: container shared { when "derived-from-or-self(../isolation, 'ietf-nss:service-isolation-dedicated')";To investigate, we may need to fix the payload or you may need to reconfigure the settings to make sure they match the validation mentioned above.Let me know if this helps.Regards,Janaki DuggiralaHello, to summarize the meeting:1. Validation was triggering due to incorrect single-sided-control config present in the payload. Once the incorrect single-sided-control was removed. Payload was succesful.2. single-sided control is present in the wiki (correctly) and can be found under the NSO UI Path -> ietf-nss:network-slice-services/slice-service{L3-Dedicated}/cisco-nss:shared3. Regarding single-sided-control usage:P2P: no single-sided-controlHub and spoke: single-sided-control with service-isolation-dedicatedAny-to-any: single-sided-control with service-isolation-dedicated4. single-sided-control is only used for Dedicated service. This is because dedicated side of the slice can be configured to force the same forwarding path selection in each direction when connecting to a shared endpoint. This behavior can is modeled in the dedicated slice service by setting the single-sided-control flag.Please let us know if all questions are resolved and if we may please close this ticket.Thanks Janaki for sharing the info. One question about the pre-requisite for adding global settings for L2 P2P dedicated slice provision to work. Is "L2-ATTACH" a reserved word or it can be a user defined value?eg. set network-slice-services global-settings parent-rr-route-policy L2-ATTACHHello Crystal, it can be any route-policy. L2-ATTACH is only a sample.Customer queries were answered. Customer confirmed ticket can be resolved. |
Need help in bringing up a NSO L3 HA setup: The ticket is related to ,Hi Thomas/team,Need a quick help please.Tried to bring up end to end NSO L3 HA and it came up as expected, except VIP 7.7.7.7 did not came up in Primary NSOs Loopback IP. Would you please suggest.Jump host - 10.23.226.188 root/Cwork123!NSO 192.168.5.69, 192.168.6.69 VIP 7.7.7.7 (Credentials - nsoaz1/Cnc@1234)Router 5.5.5.5 admin/Cwork123!Steps followed:Brought up Ubuntu 22.04. Installed Java, Python, gobgp, NSO 6.1.2 and corresponding tailf-hcc package.Brought up CSR router and configured necessary bgp config (VIP 7.7.7.7 is learnt as bgp route in CSR routers routing table).Followed NSO HA wiki and configured HA, HCC configs L3 configs are similar to your configuration.L3 HA came up, Secondary node IP shown in Primary. All looks good except just 1 point - VIP not assigned to Loopback IP.ThanksAjitha | Hi Ajitha,Ive logged on to your NSO nodes and verified that the VIP is indeed assigned to the loopback interface of the primary node (see pic attached). Also, if you need to seewhich interface HCC will choose for a particular VIP address that you have provided, use the command ip route get <VIP_Address> (first command on the attached pic).Will close the ticket now as designate as resolved.Thank you.Hi Ajitha,Ive logged on to your NSO nodes and verified that the VIP is indeed assigned to the loopback interface of the primary node (see pic attached). Also, if you need to seewhich interface HCC will choose for a particular VIP address that you have provided, use the command ip route get <VIP_Address> (first command on the attached pic).Will close the ticket now as designate as resolved.Thank you. |
RFS HA is broken: Hi Team,We are trying to bring up RFS-HA. Unfortunately the HA doesn't come up after following the HA installation guide as it is.The standby node status as been found as follows:admin@ncs> show high-availability statushigh-availability status mode nonehigh-availability status assigned-role slavehigh-availability status be-slave-result "error (27) - FXS mismatch"high-availability status master-id masterhigh-availability status read-only-mode falsePlease help to check and share the clarity on the issue. | Hi Dinesh ,As discussed over webex this is junk JSD,having M5 on primary and M4 on secondary would never work which saw.Please have same builds on both and then try.closing now.ThanksPriyanka |
NSO-M7, TM-TC-244: L2VPN P2p-L2nm-Plan not moving to completed: NSO version - 5.7.4CFP build version - 4.0 M7Device type and version used for testing - 1) 10.56.23.148 - 7.7.1 2) 10.56.23.21 - 7.5.2Add clear steps to reproduce an issue this includes details if some steps were done through NSO UI/CLI or through CNC UI, details on commit options used, order in which payloads were pushed, plan status in between, etc.>> sampath >> 1) Install latest LSA 4.0 M7 with one CFS and two RFS. 2) Created L2VPN P2p Plain. Service got stuck in plan. Config got pushed into devices, but Plan is not completed in NSO>> Logs attachedCFS: 10.56.116.151RFS1: 10.56.116.152RFS2: 10.56.116.153nso/Public1234! | Hi Sampath ,Please fix your bootstrap for netconf notifications :nso@ncs% run show devices device sareddyd-esxi-01-vm2 netconf-notifications subscription FAILURE NAME STATUS REASON ERROR INFO -----------------------------------------------------------------------------------------------------------------------------------rfs-cisco-custom-template-events running - - rfs-dispatch-map-update running - - sareddyd-esxi-01-vm2-cisco-custom-template-events running - - *sareddyd-esxi-01-vm2-dispatch-map-events failed subscribe Failed to create subscription: bad_element: no such stream *sareddyd-esxi-01-vm2-kicker-events running - - tsdn-kicker-events running - - nso@ncs% run show devices device sareddyd-esxi-01-vm3 netconf-notifications subscription FAILURE NAME STATUS REASON ERROR INFO -----------------------------------------------------------------------------------------------------------------------------------rfs-cisco-custom-template-events running - - rfs-dispatch-map-update running - - sareddyd-esxi-01-vm3-cisco-custom-template-events running - - *sareddyd-esxi-01-vm3-dispatch-map-events failed subscribe Failed to create subscription: bad_element: no such stream *sareddyd-esxi-01-vm3-kicker-events running - - tsdn-kicker-events running - - Please follow verification section post install :Thanks,Priyanka |
NSO allow to delete route-target from l3nm: Tried to create l3nm with no RT, but NSO not allow this (see attached). After creation of l3nm with RT, it is possible to delete all RTs - so is this field mandatory or not? It has effect on validations we do in CNC. | Hi Idan,'route-target-type' is mandatory when the 'vpn-target' is present.In the second screenshot , you created l3 with vpn-target list but no 'route-target-type' . that is why the error "route-target-type' is not configured".in the first screenshot , you deleted the 'route-target' list which is not mandatory.Regards,Nishad Subairhi, thank you, so when I look on the yang model, how can I tell which field is mandatory, and which is not? the question here is why NSO will not block this kind of config? l3vpn without route targets is not a real scenario. Hi Idan,route-targets is optional on device and mandatory would break backwards compatibility.Thanks,Nishad Subair |
SR-TE Service cleanup via UI gets stuck in in-progress state: SR-TE Service cleanup via UI gets stuck in in-progress stateIve saved the NSO logs in the below server. Server:172.28.122.102 temp1/Cwork123!$ ls -ltrtotal 1940592-rwxrwxrwx 1 temp1 temp1 131378022 Jun 8 19:52 data_060822_224554.tgz <-CFS-rwxrwxrwx 1 temp1 temp1 946363052 Jun 8 19:54 data_060822_224847.tgz <-RFS-1-rwxrwxrwx 1 temp1 temp1 909420360 Jun 8 20:01 data_060822_225322.tgz <-RFS-2-rwxrwxrwx 1 temp1 temp1 684909909 Jun 8 22:18 showtech_capp-aa_all_20220609050836.tar.gz-rwxrwxrwx 1 temp1 temp1 644942619 Jun 8 22:33 showtech_capp-cat_all_20220609051816.tar.gz$ pwd/tmp/reg7_policy_cleanup$Ive removed the zombie using resurrect, but service is still in in-progress state. Issue seen in both #209 and #214.admin@ncs> request zombies service /sr-te/cisco-sr-te-cfp-sr-policies-internal:policies/policy resurrectresult trueadmin@ncs> show zombie% No entries found.admin@ncs>admin@ncs> show configuration | display set | match 9066admin@ncs> | Hi Joseph,First thing to note is that zombie resurrect is not a supported action for TSDN CFPs. Second thing to note is that zombie resurrect will restore service state from the zombie itself, so if you see the service back in provisioning state, that is what resurrect is intended to do.Also, I cannot find the logs on your server. Could you provide the absolute path to logs?Could you also detail the steps you took before the cleanup action?Thanks,Isaac Kimzombie resurrect was performed after the clean-up had failed (got stuck in in-progress). So how do we remove this zombie?Could you also detail the steps you took before the cleanup action?Step1 : Create the service via UI using l2vpn_R1_R10_srpolicy_tldp_dot1q.iniStep2 : Start Basic monitoring and then stop monitoringStep3 : Perform clean-up via UI Could you provide the absolute path to logs?$ pwd/tmp/reg7_policy_cleanup$Hi Joseph,From your steps, it seems like you executed cleanup action without first deleting service. This is not a supported flow for TSDN. Cleanup action should only be executed as a last resort option to clear a failed delete service as stated in our documentation. As such, delete should always precede cleanup, otherwise you will face race conditions such as leftover artifacts.Please try the following steps:1. Delete service + commit2. Check for zombies, if there are stuck zombies continue to next step3. Execute cleanup action targeting serviceHi Joseph, we have discussed few recovery options via Webex chat. I believe we have been able to address your issue for this JSD ticket. If there is no reply in next few days, I will close this ticket.Thanks,Isaac Kim |
Need help on how to setup NSO HA for 6.1.2: Please help setting up the HA for GEO-HA testing for CNC 6.0Please let us know what needed for the VMs.Thanks and regards. | Hi Quy,Can you provide/prepare the following:1 ESXi Host where we can deploy the following:3 VMs with two network interfaces each, one for private one for public network.Download a CSR100V (latest version from CCO) image and install on the same ESXi host as the VMs aboveTwo virtual switches on the same ESXiProvide the public IPs for the VMs<img src="https://jira-eng-gpk3.cisco.com/jira/images/icons/attach/noimage.png" imagetext="IMG_5645.jpg|thumbnail" align="absmiddle" border="0" />hi Abe, Thanks for getting back to us regarding the HA setup for L3.We would like to know if you could help and what do we need if we want to have L2 instead - what requirements are needed.Synced up with Quy and walked her in setting up L2 HA using tail-f HCC 6.0.0 package (VIP). Answered all questions regarding the setup and is clear on her side. Closing the ticket now since they are ok with L2 HA for now.Hi Quy,Please let me know if you have additional questions from our sync-up yesterday regarding setting up NSO L2 HA. I hope Ive answered all your questions, but let me know if you have additional queries about the steps/setup.In the mean time, Im closing the ticket and designate it as done.Thank you,AbeHi Quy,Please let me know if you have additional questions from our sync-up yesterday regarding setting up NSO L2 HA. I hope Ive answered all your questions, but let me know if you have additional queries about the steps/setup.In the mean time, Im closing the ticket and designate it as done.Thank you,Abe |
CNC 2.0 Spring4Shell vulnerability testing: L3VPN Profile creation error: Hi Nipa, Divya and Sid,NSO: 5.4.6CNC 2.0.2When we try to create the L3VPN profile I am seeing the below error.Steps to reproduce.Step 1: Created a L3vpn Route PolicyStep 2: Click on VPN ProfilesStep 3: Click + and select Route policy and click on Commit Changes.No Configuration change detectedfilename/crosswork/proxy/nso/jsonrpc/get_leafref_values{"params":{"path":"/l3vpn-ntw:l3vpn-ntw/vpn-profiles/valid-provider-identifiers/routing-profile-identifier/id","skip_grouping":true,"th":60},"jsonrpc":"2.0","id":2303,"method":"get_leafref_values"}{"jsonrpc":"2.0","result":{"values":["RTR-P-1222","RTR-Policy-100"],"source":"/cisco-flat-L3vpn-fp:l3vpn-route-policy"},"id":2303}{"params":{"path":"/l3vpn-ntw:l3vpn-ntw/vpn-profiles/valid-provider-identifiers/routing-profile-identifier/id","value":"RTR-P-1222","th":60},"jsonrpc":"2.0","id":2304,"method":"set_value"}{"jsonrpc":"2.0","error":{"type":"rpc.method.invalid_params","code":-32602,"message":"Invalid parameters","data":{"reason":"wrong number of identifiers","param":"path"},"internal":"webui_util699"},"id":2304} | Hi Joby,Could you please share your NSO IP and credentials?I will take a look.ThanksPriyankaNSO : 10.195.165.233 (admin/Ovatest123@)As discussed over Webex NSO CFP is working perfectly fine for these steps.It seems to be CNC UI issue.I will close the JSD now.Thanks,PriyankaIssue here is CFP team fixed the issue with NSO 5.4.6 without letting the CAT UI team.Who is going to fix this as this is part of 2.0 PatchThanks,ShanBalu.Hi Shanmugavel,We re-qualified the TSDN CFP 2.0 with NSO 5.4.6 for the Log4j vunerability. There is nothing else we changed.Thanks,Nipa |
Need steps to configure NSO HA L3 BGP : For 6.0 release, we have a requirement to test NSO HA with L3 mode and bgp configs.QA needs sequence of pre-requisite steps and few other configs for deploying NSO HA with L3 mode. Hence, we request to provide some point of contact for troubleshooting issues and support when needed. | Customer was helped by Thomas in an email thread and was provided the following:1.NSO Admin guide (and pointed out the Tailf HCC overview)2.NSO HA guide3.Demo recording of Thomas setting up L3 HAGetting below errors when configuring NSO HA L3 bgp settings on NSO Primary VM:admin@ncs% set hcc bgp node primary-node neighbor 192.168.20.4 as 65131admin@ncs% commitAborted: application communication failureadmin@ncs% set hcc bgp node primary-node enabledValue for 'gobgp-bin-dir' (<string>): /usr/binValue for 'as' (<unsignedInt>): 65132Value for 'router-id' (<IP address>): 192.168.20.5admin@ncs% commitAborted: application communication failureNeed someone to troubleshoot this issue and provide resolution for it.Hello, please provide us setup details so we may investigate.unicasted the setup detailsRetried the steps as discussed on webex session with CFP team, but still getting application communication failure error while committing hcc bgp configs. Need to wait for Van Pham to check into this issue till Monday.Checked with Van, unable to log into NSO 1 and NSO 2 is missing config.>> need gobgp config on all nso and routerScreenshots attached.Requesting additional information.gobgp config/package was already installed on both NSO1 and NSO2 VMs. Below is the output on the VMs.nso-vm1-sa:/home/admin# apt install gobgpdReading package lists... DoneBuilding dependency tree... DoneReading state information... Donegobgpd is already the newest version (2.25.0-3build1).0 upgraded, 0 newly installed, 0 to remove and 4 not upgraded.root@nso-vm2-sa:/home/admin# apt install gobgpdReading package lists... DoneBuilding dependency tree... DoneReading state information... Donegobgpd is already the newest version (2.25.0-3build1).0 upgraded, 0 newly installed, 0 to remove and 5 not upgraded.However, executing the below command gives no file error on both VMs.root@nso-vm1-sa:/home/admin# cat /etc/gobgpd.ymlcat: /etc/gobgpd.yml: No such file or directoryon router, below are the bgp configs that were configured:csr-vm5#router bgp 65131 bgp log-neighbor-changes neighbor 192.168.5.26 remote-as 65132 neighbor 192.168.6.59 remote-as 65133 ! address-family ipv4 redistribute connected neighbor 192.168.5.26 activate neighbor 192.168.6.59 activate exit-address-familyI followed the steps suggested by Thomas in webex recording for installing gobgpd.Can we get the missing configs or install steps that need to be configured on both NSO VMs and router as well? Hi Gomathi,It looks like gobgp config in NSO is missing:admin@ncs% show hcc bgpNo entries found.Please try the following config with correct router interface IP addresses, AS, and router id:Primary NSO:set hcc bgp node master enabled as 65132 router-id 192.168.5.26 gobgp-bin-dir /usr/bin neighbor 192.168.5.x as 65131Secondary NSO:set hcc bgp node standby enabled as 65133 router-id 192.168.6.59 gobgp-bin-dir /usr/bin neighbor 192.168.6.x as 65131On both nodes, do: request high-availability disableThen after bgp config, do:request high-availability enableHi Van,Can we look into this issue on webex meeting? I tried below configs with "primary-node" changed to "master" and "secondary-node" changed to "standby" with corresponding IP, AS and router-id values. But, still getting same error.admin@ncs% commitAborted: application communication failureThanks,Gomathi.Hi Gomathi,After updated to latest gobgp version 3.16.0, bgp is functional and high-availability is up.admin@ncs> show high-availabilityhigh-availability enabledhigh-availability status mode primaryhigh-availability status current-id masterhigh-availability status assigned-role primaryhigh-availability status read-only-mode falseID ADDRESS ------------------------standby 192.168.5.252admin@ncs> show hccNODE BGPD BGPD ID PID STATUS ADDRESS STATE CONNECTED --------------------------------------------------------------master 39514 running 192.168.5.29 ESTABLISHED true1. wget 2. scp gobgp_3.16.0_linux_amd64.tar.gz to NSO node3. tar zxf gobgp_3.16.0_linux_amd64.tar.gz4. sudo mv gobgp* /usr/local/bin/Note that "gobgp-bin-dir /usr/local/bin" as the new gobgp was installed under/usr/local/bin directory.admin@nso-vm1-sa:~$ which gobgp/usr/local/bin/gobgp<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"><pre class="code-java">For reference, below is config on primary node. hcc config should be changed accordingly on secondary node.admin@ncs% show high-availability token $9$UHHL5OHfYJg3iCyjJGIl90gE2Lv5VMM3trHMEUqHUWc=;ha-node master { address 192.168.5.26; nominal-role primary;}ha-node standby { address 192.168.6.59; nominal-role secondary; failover-primary ;}settings { enable-failover ; start-up { assume-nominal-role ; join-ha ; } reconnect-interval 15; reconnect-attempts 3;}[ok][2023-08-01 00:20:29][edit]admin@ncs% show hccenabled;vip-address [ 192.168.5.27 ];bgp { node master { enabled; gobgp-bin-dir /usr/local/bin; as 65132; router-id 192.168.5.26; neighbor 192.168.5.29 { as 65131; } }}[ok][2023-08-01 00:20:36]</pre></div></div>Switchover is working as expected with changes made to NSO host default route and added route reflector in the CSR1000V.Setup is working, Gomathi agreed to close this case. |
Testing Token with an Authentication Provider fails: installed TSDN 6.0.0 - Drop 5 (DTHO) on 10.23.213.183(root / Cwork123!) and cnc server 192.168.6.10 Performed Testing Token with an Authentication Provider with following error- 2023-08-03 13:52:41.480 authenticate:261 INFO: Exception jwt-auth: HTTPSConnectionPool(host='192.168.6.10', port=30603): Max retries exceeded with url: /crosswork/sso/v2/userInfo (Caused by NewConnectionError('<urllib3.connection.VerifiedHTTPSConnection object at 0x7f06b24fbbb0>: Failed to establish a new connection: Connection refused'))Please help if anything is missing or misconfiged. | tgt_token=$(curl -k -X POST -H 'Content-Type: application/x-www-form-urlencoded' -H 'Accept: text/plain' -d 'username=admin;password=Vtsisco@123!')jwt_token=$(curl -k -X POST -H 'Content-Type: application/x-www-form-urlencoded' -d service=)Unbale to reach cnc server from nso:root@nso-4:/var/log/ncs# tgt_token=$(curl -k -X POST -H 'Content-Type: application/x-www-form-urlencoded' -H 'Accept: text/plain' -d 'username=admin;password=Vtsisco@123!') % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 -<del>:</del><del>:</del>- -<del>:</del><del>:</del>- -<del>:</del><del>:</del>- 0curl: (7) Failed to connect to 192.168.6.10 port 30603: Connection refusedroot@nso-4:/var/log/ncs# requests.exceptions.ConnectionError: HTTPSConnectionPool(host='192.168.6.10', port=30603): Max retries exceeded with url: /crosswork/sso/v2/userInfo (Caused by NewConnectionError('<urllib3.connection.VerifiedHTTPSConnection object at 0x7f2934ec82e0>: Failed to establish a new connection: Connection refused'))To resolve this issue, you should check the following:<ol>Ensure that the target machine with IP '192.168.6.10' is reachable and running the service you are trying to access on port '30603'.</ol><ol>Verify that the service is up and running and that it's configured to listen on the correct IP address and port.</ol><ol>Check if there are any firewalls or security groups that might be blocking the connection.If the service is running on a remote machine, ensure that there are no network connectivity issues between your machine and the remote server.</ol>Had a screenshare with Feng and have agreed to close the ticket for now as we are seeing network issue on the setup. If the issue happens again Feng has informed to reach back |
EVPN-VPWS not supported on IOSXE devices: Tried to configure EVPN ELAN/ETREE in IOS XE device and received a error message from NSO saying "EVPN-VPWS not supported on IOSXE devices". Attached screenshot. Please confirm, if NSO dont support EVPN ELAN ETREE (VPWS) in IOS XE at all. | EVPN MP(ELAN/ETREE) is not supported for XE.XE only supports P2P, EVPN is not supported at all.Updated the same to Ajitha on teams, hence closing the ticket.Required information given to the user.Thanks Nikhil for confirming, Correction in title - EVPN VPLS(ELAN/ETREE) not VPWS |
Provision SRv6 policy with netconf ned does not push config to device : Steps:1. set 2 of my nodes (headend and tailend) to use netconf ned cisco-iosxr-nc-7.3.2. provision an SRv6 policy from CAT UI. After commit, it showed successful. But policy config is not pushed to device.device type and version: XRV9K 7.3.2 38Ipayload attached. | Hi,Version 7.3.2.38I is not supported on M5.Please refer the Release Notes Doc below:Hi Sahithi,We need to support newer version of XRV9K 7.3.2 and 38I is the one released from platform team for us to test. Let me know if we can only use 34I to report issues for M5?Is it possible to be netconf ned issue before it push config to devices? Here are some observations.:Load the payload from "Commit manager" via NSO UIFor cli ned: it shows the policy config to be pushed (screenshot attached)For netconf ned: It shows empty contents with "No devices affected"From CNC UI, import the payload and do dry run:For cli ned: It shows the policy config to be pushed.For netconf ned: It shows the contents of the policy but it is different from the cli dry run outputScreenshots and dryrun output attached. Tried to downgrade my device to 34I. Looks like the image no longer exist under the location mentioned in M5 wiki.lnx-cw1.cisco.com:130> cd /auto/iox-ucs-017-san1/lnx-cw1.cisco.com:131> cd prod/lnx-cw1.cisco.com:132> ls -ltrtotal 16drwxrwxr-x 5 ingunawa xrops 4096 Aug 17 14:18 7.3.2.37I.SIT_IMAGEdrwxrwxr-x 5 ingunawa xrops 4096 Aug 24 22:08 7.3.2.38I.SIT_IMAGEdrwxrwxr-x 5 ingunawa xrops 4096 Aug 31 13:19 7.3.2.39I.SIT_IMAGEdrwxrwxr-x 5 ingunawa xrops 4096 Sep 7 15:22 7.3.2.40I.SIT_IMAGEHi Sahithi,Per your suggestion. I picked up TSDN M6 and redeployed my devices with 7.3.2 37I. The issue is still the same. Can we have a webex session to look further?Steps provided for Correct working.Sync-from devices when the device-type changed.Then creation of service works as expected.CSCvz62371: Policy provision is successful but config does not push to device - ned changed from cli to netconf |
RON ML service creation failed with status code RON-304: NSO 5.5.3.2 CNC 3.0 RON 1.0RON ML service creation failed with status code RON-304 . it does not give more information. NSO : 10.195.165.226service name: RON_ML_7How to get more information about the RON status codes. Any commands ?cred: cnctest/Ovatest123@ | Hi Ramakrishnan,I looked at your setup and it seems like an issue with optical-controller.For service RON_ML_5, i see below error.ron ron-ml RON_ML_5 plan-location /ron/ron-ml-plan log log-entry 2021-08-07T15:05:47.346776+00:00 type service-modified level error message "Error running action for side-effect item /cisco-ron-cfp:ron/ron-ml-plan{RON_ML_5}/plan/component{ncs:self self}/state{ncs:init}: Python cb_action error. Failed to retrieve/validate SIPsnSTATUS_CODE: RON-505nREASON: Fetch Optics failednCATEGORY: custom-actionnSEVERITY: ERRORnContext n"For service RON_ML_6 and RON_ML_7, i see below error.status-code 304 { reason "Connectivity-service initiated on the optical-controller has failed"; category device; severity ERROR; recommended-actions " The reason for connectivity service failure is unknown and requires debugging optical-controller server.";Could you please provide me with more details on which ONC version are you using and if your sips used are valid. This would help us debug the issue further.Gave ONC details, build 673, service is in PENDING_REMOVAL state.HI Ramakrishnan,After our discussion on webex yesterday, we realized that the RON_ML_7 service is in pending-removal state at ONC level.We can't do anything about pending removal asONC has failed to configure the service. We should justdelete the service and try again.Today, I was trying to delete the service and realized that ONC is not up and running. Could you please check and let me know wats the issue with ONC.Brought up the ONC again, deleted the service, Tried it again. It worked. go ahead and close this case.Hi Ramakrishnan, As discussed on webex, you were able to deploy the service successfully after deleting once. Hence closing the ticket. |
resource-manager ERR in NSOUtil redeploy: Custom service leveraging resource-manager bundled with example-packages(../example-packages/ncs-5.5-resource-manager-3.5.4.tar.gz) generates an error during IP address allocation (service redeploy).Service requires an ID and IP address from the resource-manager pools. ID allocation works as expected, IP allocation fails as per below:ERROR in ncs-java-vm.log:NSOUtil redeploy: re-deploying /ncs:services/ODNL3:ODNL3{demo} as user admin (tid: 38552, type: DEFAULT, trans: true) %s/touch<ERROR> 20-Oct-2021::11:51:29.289 IPAddressAllocator$RequestThread pool-38-thread-1: -java.lang.ClassCastException: class com.tailf.conf.ConfList cannot be cast to class com.tailf.conf.ConfObjectRef (com.tailf.conf.ConfList and com.tailf.conf.ConfObjectRef are in unnamed module of loader 'app') at com.tailf.pkg.ipaddressallocator.IPAddressAllocator.allocateAddress(IPAddressAllocator.java:359) ~ at com.tailf.pkg.ipaddressallocator.IPAddressAllocator$RequestThread.run(IPAddressAllocator.java:1968) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) at java.lang.Thread.run(Thread.java:834) Package has identical package-meta-data.xml with corresponding CCO release for 5.5.2, but underlying code differs (NSOUtil.java).When using the CCO resource-manager, custom service produces no errors and successfully is allocated both ID and IP.Code for allocations in custom service:34 pool_name = "LoopbackIDPool"35 _sync = False36 allocation_name = allocation_prefix + _serviceName3738 id_result = id_allocator.id_request(service,39 _serviceNode,40 tctx.username,41 pool_name,42 allocation_name,43 _sync)66 pool_name = "LoopbackIPPool"67 cidr = 3268 allocation_name = allocation_prefix + <em>serviceName + '</em>' + dev_name + '_' + str(allocation_loopbackID)6970 ip_allocator.net_request(service,71 _serviceNode,72 tctx.username,73 pool_name,74 allocation_name,75 cidr)Let me know if you need additional info. | We have created a jira ticket for this Issue internally and added it to the release notes.Continue using the RM from CCO for the external package development since current example package has the bug.Release post 3.0 should contain the fix for this issue.We have created a jira ticket for this Issue internally and added it to the release notes.Continue using the RM from CCO for the external package development since current package in the bundle has the bug.Release post 3.0 should contain the fix for this issue. |
Along with Info message, CNC should show allowed range/variable type(str/int) as in NSO: Wherever "allowed values/ranges" are present in NSO tool tip/info message (like l3nm local autonomous system), CNC has to show allowed ranges/variable type(str/int) .Issue : NSO is not sending the range in some cases - so prov-ui is not able to fix this. Follow up with NSO team. It may needs the JSON RPC response to bring these additional info as part of the get_Schema API so that the Prov-UI will parse and display it accordingly.Cdets for more details: | Hi Kirandeep,Could please be specific on what all you need and is not supported currently in NSO UI?As there are so many services and different yang models for them, without knowing what exactly you need and what is missing.As per the defect, you attached it looks like CNC UI defect.But details provided in this JSD ticket are quite contradictory.Appreciate it if you provide each and every detail.ThanksPriyanka Info needed with details.TO be more specific: from get_Schema API response we get the field info which on CNC we are showing in tooltip as additional information which shows the range along with the info e.g : /cisco-sr-te-cfp:sr-te/cisco-sr-te-cfp-sr-policies:policies --> field : color Information:<1-4294967295> - SR policy colorbut services in /l3vpn-ntw:l3vpn-ntw/vpn-services/vpn-service. --> local-autonomous-system will have range but it not the part of get_schema api repsonse "info": attribute so we are not able to show the range along with info on that element. so we need this information form NSO as part of JSON RPC response as additional info as part of the get_Schema API so that the Prov-UI will parse and display it accordingly.please refer the screen shot attached to see the different between those values also added the get_Schema API response for reference.Hi Kirandeep,NSO PLM needs to be contacted for this.ThanksPriyankaPending on NSO PLM,had chat with Mukul ,he will take care |
Not able to provision L2VPN with SRV6 policy.: Not able to provision L2VPN with SRV6 policy, getting below error message.Tried with below neds cisco-iosxr-nc-7.3, cisco-iosxr-nc-7.4, cisco-iosxr-nc-7.5 ; cisco-iosxr-cli-7.38, all neds getting same error message.In the wiki i don't see L2VPN+SRV6 policy payload, It will helpful if you can share the sample payload for L2VPN+SRV6 policy.Setup -172.24.97.142nso- 172.24.97.147admin@ncs> *** ALARM service-activation-failure: /cisco-flat-L2vpn-fp-internal-local-site:flat-L2vpn-internal-local-site-service{L2NM-L2NM-SRV6-internal TB3-PE-D}: Python cb_validate error. STATUS_CODE: TSDN-L2VPN-416REASON: L2VPN association with SRv6 via SR policy is not supported for this release.CATEGORY: userSEVERITY: ERRORContext [name = Not supported , message = L2VPN association with SRv6 is not supported for this release.state = {'Device': 'TB3-PE-D', 'Service': 'L2NM-L2NM-SRV6-internal', 'Policy': 'srv6_vpn_policy-9001'}] | Hello Ragesh,According to our Flat-L2VPN detailed wiki for TSDN 4.0 M2, SRv6 policy association in Flat L2 via preferred-path is not supported for this current release. Instead, you may use the Flat-L2VPN EVPN SRv6 locator field to associate directly.Wiki Reference : Yang Tree for SRv6 locator (Referenced from Flat-L2VPN Detailed Wiki)<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"><pre class="code-bash"> +--rw flat-L2vpn* [name] | +--rw flat-L2vpn-evpn-vpws | | +--rw -site | | | +--rw srv6! | | | | +--rw locator? string | | +--rw remote-site! | | +--rw srv6! | | | +--rw locator? string</pre></div></div>After reviewing the wiki, I agree that it is not so clear how to associate SRv6 policy with Flat-L2VPN EVPN service using locator. I will relocate the info box and add a sample payload demonstrating the above to the wiki starting TSDN 4.0 M2.Please let me know if you have any other questions or concerns.Thanks,Isaac KimHello Ragesh,On second review, it does seem like our Flat-L2VPN detailed wiki provides sample payload for Flat-L2VPN EVPN + SRv6 association. You can find it here : In addition, the sample payload for IETF L2NM + SRv6 association can be found in our IETF L2NM detailed wiki here : As the sample payload is provided in our wiki, I will assume this ticket is resolved.Please feel free to reopen this ticket with any reply if you have any additional comments.Thanks,Isaac KimHello,For future reference,The path to IETF L2 + SRv6 association is hereYANG Tree for IETF L2 SRv6 Locator (Referenced from IETF L2 detailed wiki)<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"><pre class="code-bash"> +--rw l2vpn-ntw | +--rw vpn-services | | +--rw vpn-service* [vpn-id] | | | +--rw vpn-nodes | | | | +--rw vpn-node* [vpn-node-id ne-id] | | | | +--rw te-service-mapping | | | | | +--rw srv6! | | | | | +--rw locator? string</pre></div></div>I have added additional note in both Flat L2 and IETF L2NM detailed wikis to clarify this association. |
Post config throws internal error on xml file loading: Post config throws internal error on xml file loadingadmin@ncs% load merge rfs-netconf-notif-sub.xmlError: internal erroradmin@ncs% load merge RSVP-TE-status-codes.xmlError: internal erroradmin@ncs% load merge SR-cfp-configuration-kicker.xmlError: internal erroradmin@ncs% load merge SR-multi-vendor-iosxe-cli.xmlError: internal erroradmin@ncs% load merge SR-multi-vendor-iosxr-netconf.xmlError: internal erroradmin@ncs% load merge SR-plan-notification-settings.xmlError: internal erroradmin@ncs% load merge SR-status-codes.xmlError: internal erroradmin@ncs% load merge xr-sman-id-resource-pool.xmlError: internal erroradmin@ncs% load merge rfs-node-onboarding.xmlError: internal errorCFS node: 10.194.63.169 (ssh: nso/Vtsisco@123!)RFS node1: 10.194.63.170 (ssh access - same as CFS)RFS node2: 10.194.63.242 (ssh access - same as CFS) | Replace the $ Parameters in the xml and load merge as mentioned in the wiki${RFS_NODE_NAME} -> replaced by the actual name of rfs.This has been mentioned in the wiki in the section on load merging the files.Wiki Link: I could not find the instruction below from the wiki for M2 - could you please send screen shot on "Replace the $ Parameters in the xml and load merge as mentioned in the wiki${RFS_NODE_NAME} -> replaced by the actual name of rfs." Please give example - these are load merge for CFS node.Thanks and regards,-QuyExample:Open the xml and replace parameters denoted with $ variable${RFS_NODE_NAME} -> replaced by the actual name of rfsThe variable names should self explanatory to replace.Let me know if there is any variable which is ambiguous.Thanks for flagging about the Wiki. Let me add this instructionThanks for checking - while you are at the wiki please correct the path location for these xml files - here is the current wiki instruction Done. Changed from /xml -> init_data/xml |
Issue with page load - TSDN 3.0.0-M6 - L2NM -> L2vpn -> Device Config Mapping: TSDN 3.0.0-M6 - L2NM -> L2vpn -> Device Config Mapping The link doesnt load the Device mapping Images of XR and XE.Attached snapshot. | Screenshots of Mappings from wiki Hi Arun,Attached the screenshots for mapping from wiki.Were you not able to access the screenshot from wiki , as i see image attached in your screenshot. ?ThanksPriyankaI am able to view the device mapping from that link.thanks. |
An extra old route-policy gets added to only one device for ETREE-SRODN service: An extra old route-policy "L2NM-ETREE-SRODN-91-720-NCS1" gets added to only one device for ETREE-SRODN serviceSteps:1. Provision ETREE-SRODN service1 with 3 nodes with route-policy PASS as parent policy. It will be successful.2. Provision another ETREE-SRODN service2 with 3 nodes with route-policy PASS as parent policy. It will be successful.3. Delete service and related entities for service1 above from CNC UI.4. Provision another ETREE-SRODN service3 with 3 nodes with route-policy PASS as parent policy. Provisioning will fail as it's looking for old route-policy "L2NM-ETREE-SRODN-91-720-NCS1" for NCS1 device.5. We can see the issue reported in the output of native configs.Attaching logs collected on NSO VM soon. | Cleaned up the extra route policy on RFS. Gomathi confirmed, it is working now |
500 netsim devices fail to stary: I used to be able to create a netsim-network of 500 devices and start all the devices in M7. After I upgraded to M8, on the same VM, I am not able to start all 500 devices. After about 180, I see these errors while starting the device:DEVICE cp0180 OK STARTEDCDB boot error: failed to write schema file: ./cdb/C.cdbDaemon died status=16DEVICE cp0181 FAILInternal error: Supervision terminatedInternal error: Component terminated (application_controller) ({application_start_failure,confd,<tt>shutdown,{failed_to_start_child,second,{shutdown,{failed_to_start_child,cs_usess,{{badmatch,{error,enospc</tt>,[{cs_usess,get_next_tid,1,[{file,"cs_usess.erl"},{line,2778}]},{cs_usess,init,1,[{file,"cs_usess.erl"},{line,954}]},{gen_server,init_it,2,[{file,"gen_server.erl"},{line,390}]},{gen_server,init_it,6,[{file,"gen_server.erl"},{line,353}]},{proc_lib,init_p_do_apply,3,[{file,"proc_lib.erl"},{line,249}]}]}}}}},{confd_app,start,[normal,[]]}}})Daemon died status=19 | Hi Sachin,Can you please check the number of file descriptors on your VM?Can you set them to maximum and number and restart the netsim devices?Hi Sahithi. These are the limits on my VM:root@nso-215:/var/opt/ncs/xr_netsim# ulimit -areal-time non-blocking time (microseconds, -R) unlimitedcore file size (blocks, -c) 0data seg size (kbytes, -d) unlimitedscheduling priority (-e) 0file size (blocks, -f) unlimitedpending signals (-i) 482582max locked memory (kbytes, -l) 15457224max memory size (kbytes, -m) unlimitedopen files (-n) 1024pipe size (512 bytes, -p) 8POSIX message queues (bytes, -q) 819200real-time priority (-r) 0stack size (kbytes, -s) 8192cpu time (seconds, -t) unlimitedmax user processes (-u) 482582virtual memory (kbytes, -v) unlimitedfile locks (-x) unlimitedEverything is set to max. 166 devices started up fine and then they failed. The NSO server is 172.20.98.215 (nso/Vtsisco@123!)These are the limits set:soft nproc 65535hard nproc 65535soft nofile 65535hard nofile 65535hard memlock 65536soft memlock 65536Am I missing any of the configuration?Could it be because I am running out of space? root@nso-215:/var/opt/ncs/xr_netsim# df -hFilesystem Size Used Avail Use% Mounted ontmpfs 12G 1.3G 11G 11% /run/dev/mapper/ubuntu-<del>vg-ubuntu</del>-lv 98G 98G 0 100% /tmpfs 59G 0 59G 0% /dev/shmtmpfs 5.0M 0 5.0M 0% /run/lock/dev/sda2 2.0G 252M 1.6G 14% /boottmpfs 12G 4.0K 12G 1% /run/user/1002root@nso-215:/var/opt/ncs/xr_netsim# Do the new version of the simulated devices take more memory than they used to in M7 or M6 ? |
Not able to acesss the jira ticket https://jira-eng-gpk3.cisco.com/jira/servicedesk/customer/portal/71/RONCFPSD-444: Not able to access the below url | You should be able to access it now. PLMK if any issues |
interface discovery with simulated device: We are using TSDN 4.0 packages with NSO 5.7.5.1For testing customer case scenario, we need to provision L2VPN devices with hundreds of end points. So, we are using simulated devices in addition to xrv9k devices. NSO has to discover the simulated device and its interfaces. Simulated devices support only SNMP and telnet. We added the simulated device IP to NSO, and connect is failing with timeout. We tried to enable trace by configuring (devices device Node_1_1 trace pretty), it created the file under /var/log/ncs/ned-cisco-iosxr-cli-7.39-Node_1_1.trace. 1. We need NSO to discover the device interfaces through telnet.So that we can provision L2VPN service with interfaces available in the device with no-networking option.NSO - 172.20.63.148 - root/Ovatest123@ | if we are using SSH for device Node_1_2, we get this error message NEDCOM CONNECT: Unable to reach a settlement: and in new state. can we force NSO to use password for SSH as below.debug1: SSH2_MSG_SERVICE_ACCEPT receiveddebug3: send packet: type 50debug3: receive packet: type 51debug1: Authentications that can continue: passworddebug3: start over, passed a different list passworddebug3: preferred gssapi-keyex,gssapi-with-mic,publickey,keyboard-interactive,passworddebug3: authmethod_lookup passworddebug3: remaining preferred: ,gssapi-with-mic,publickey,keyboard-interactive,passworddebug3: authmethod_is_enabled passworddebug1: Next authentication method: [email protected]'s password:debug3: send packet: type 50debug2: we sent a password packet, wait for replydebug3: receive packet: type 52debug1: Authentication succeeded (password).Authenticated to 10.20.1.1 (:22).Hi Ramakrishnan,We are not able to connect to 172.20.63.148 with the provided credentials.Please suggest.Regards,Nishad Subair.Hi Nishad,It was a typo. Please try cnctest/Ovatest123@Thanks,Sreedhar.Hi Sreedhar, Ramakrishnan,We can help you to connect the simulated devices via ssh or telnet, please give us couple devices with credentials that can be reached from your NSO.Regards,Hi Nishad,I have added you in one of the mail thread where below details are provided. Also pasted below (incase if the table is not clear, please do look into that mail for info.) For trail Please find below 3 sheer devices, each belonging to each of RFSSheer Hostname Sheer IPConnectivity Type enabledSheer LoginsRFS node RFS node IPRFS LoginsCFS IPNode_1_110.20.1.1Telnetcisco/ciscoRFS1172.20.63.148cnctest/[email protected]_1_510.20.1.5Telnetcisco/ciscoRFS2172.20.63.149cnctest/Ovatest123@Node_1_10010.20.1.100Telnetcisco/ciscoRFS3172.20.63.150cnctest/Ovatest123@Pasted snip of telnet of one of sheer from RFS1 $ telnet 10.20.1.1Trying 10.20.1.1...Connected to 10.20.1.1.Escape character is '^]'.Username: ciscociscoPassword: ciscoDevice_10_20_1_1#show running-configshow running-configThu Apr 7 21:00:07.958 PDTBuilding configuration...!! IOS XR Configuration 6.6.3!! Last configuration change at Thu Apr 7 20:23:30 2022 by cisco!hostname PE1-ASR9kclock timezone PST -8..!interface GigabitEthernet0/0/0/0description #Connected to Agilent 101/1 from PE1 this router"ipv4 address 16.1.1.1 255.255.255.0!interface GigabitEthernet0/0/0/1cdpipv4 address 16.1.1.5 255.255.255.252!We did mention this interface (GigabitEthernet0/0/0/1) in the payload of the script which is used to provision. Script copied to RFS1 for reference in below path - $ ls -l deploy_services_L2VPN_CNC4_Node_11-to-Node_15-rwxrwxr-x 1 cnctest cnctest 28342 Sep 28 10:45 deploy_services_L2VPN_CNC4_Node_11-to-Node_15Thanks,Sreedhar.I did verify onboarding a simulated device with telnet protocol in my setup and it works fine.admin@ncs% show devices device r1address 10.195.72.32;port 62083;authgroup iosxr_authgroup;device-type { cli { ned-id cisco-iosxr-cli-7.42; protocol telnet; }}trace pretty;state { admin-state unlocked;}admin@ncs% request devices device r1 conPossible completions: config - NCS copy of the device configuration connect - Connect to the deviceadmin@ncs% request devices device r1 connectresult trueinfo (admin) Connected to r1 - 10.195.72.32:62083Thanks,LinhThere was connectivity issue from the simulated device, which is fixed now, admin@ncs# devices device Node_1_1 connectresult trueinfo (admin) Connected to Node_1_1 - 10.20.1.1:23admin@ncs# exitStill interfaces are not discovered. what command does NSO use to discover interfaces? We can accordingly check if that command is properly working in simulated device.What prompt does NSO expects in admin mode. Not clear why NSO times out, when there is # prompt being returned?Is it mandatory to get into admin mode for interface discovery.– Reading admin config– Entering admin modeadmininput 3-Oct-2022::04:14:03.974 user: cnctest/1011756 thandle 6203791 hostname scale-nso2-RFS1 device Node_1_1 ***adminSimulator(admin)#output 3-Oct-2022::04:19:04.049 user: cnctest/1011756 thandle 6203791 hostname scale-nso2-RFS1 device Node_1_1 ***<ul class="alternate" type="square"> progress: show: reading config error << 3-Oct-2022::04:19:04.051 user: cnctest/1011756 thandle 6203791 hostname scale-nso2-RFS1 device Node_1_1 ERROR: External error in the NED implementation for device Node_1_1: Read timeout after 300 seconds, blocked on "nSimulator(admin)#" when waiting for "Invalid input detected." | "This command is not authorized." | "Command authorization failed." | "Unable to login.dmin sername:" | "<br class="atl-forced-newline" />A." | "dmin mode has been deprecated" | "<br class="atl-forced-newline" />A.$">> 3-Oct-2022::04:19:04.053 user: cnctest/1011756 thandle 6203791 hostname scale-nso2-RFS1 device Node_1_1 CLOSE 0: (Pool: false)<< 3-Oct-2022::04:19:04.054 user: cnctest/1011756 thandle 6203791 hostname scale-nso2-RFS1 device Node_1_1 CLOSEDAfter adding 'connected ' string, now NSO proceeds, but it issues 'show running-config', and it waits for 5 mins to time out. Not sure why it is waiting for 5 minscisco connected from 192.168.71.148 using ssh on Device_10.20.1.1Device_10.20.1.1(admin)#output 3-Oct-2022::06:31:10.083 user: cnctest/1013271 thandle 6207591 hostname scale-nso2-RFS1 device Node_1_1 ***<ul class="alternate" type="square">Entered admin modeshow running-configinput 3-Oct-2022::06:31:10.084 user: cnctest/1013271 thandle 6207591 hostname scale-nso2-RFS1 device Node_1_1 ***show running-configDevice_10.20.1.1(admin)#output 3-Oct-2022::06:36:10.224 user: cnctest/1013271 thandle 6207591 hostname scale-nso2-RFS1 device Node_1_1 ***exitinput 3-Oct-2022::06:36:10.226 user: cnctest/1013271 thandle 6207591 hostname scale-nso2-RFS1 device Node_1_1 ***One more question, how does NSO discover the interfaces. I tried 'Sync from', but i dont see this information being queried. We also want to know the CLI commands used to discover the interfaces in this device.Hi Ramakrishnan,It looks like there is some issue with the simulated device you are using.We connected to the device and checked. There is no interfaces/config available in the device. that is the reason why you are not able to see the same in NSO.Regards,Nishad Subair.Surprising.... Which device have you connected ? In simulated devices only defined show commands like "show running-config" , "show interfaces" ... only will work and give o/p. If we try other show commands, there wont be any o/p. Most probably this could be the reason, the configs or interfaces are not noticed. If you don't see any o/p for these show commands then please ensure the ip address of node, which is been tried. We are more interested in below asks from Ramakrishnan Srinivasan :- "How does NSO discover the interfaces. Tried 'Sync from', but i dont see this information being queried. We also want to know the CLI commands used to discover the interfaces in this device"Hi Srinivasan ,I looked at your set up today ,as per my suggestion last time I suggested to use right port for connecting .Today I tried for one device :admin@ncs% show | compare devices { device Node_1_1 {<ul class="alternate" type="square">port 23;+ port 22; device-type <div class="error"><span class="error">Unknown macro: { cli {- protocol telnet;+ protocol ssh; } }</span> </div> }}admin@ncs% request devices device Node_1_1 sync-from result trueI can now see config for this device Node_1_1 for which I moved it to ssh from telnet and port 22.Please do same operation of rest of 8K+ devices on your NSO .Please close JSD if you are good .Please try creating services after fixing ports on rest of devices .ThanksPriyankaWe can now provision the service with interface discovered using SSH. We can deal with telnet issue later. |
Unable to import Route policy tag from CNC UI that was working in NSO: Attached JSON and XML format Route policy tag is imported properly from NSO. But unable to import same files from CNC. CNC throws Failed to load form error. | But the same config works frrom CNC RESTCONF APIHi Ajitha, based on your description it seems like NSO is loading the payloads fine but CNC is having issues. I think we should recategorize this as CNC UI JSD.Thanks,Isaac KimHi Ajitha,I am not sure how to reassign a JSD to CNC UI team. For now, I will close this ticket and a new one can be created for CNC UI. If you have any additional questions, please feel free to reopen this ticket.Thanks,Isaac KimForward to CNC UI team. NSO interfaces working as expected as described in ticket. |
NSO allow space in service name: hi, on odn/l2/l3 NSO doesnt allow to have space in service name - test test is not a valid name. on slice, policy it is possible to give such name. what is the correct behavior? should all services support space or block this option? | Hi Idan, apologies for the delay, I will check this for you tomorrow. We are currently overloaded with items for upcoming M6 build.Hi Idan,Slice will validate proper naming as part of M6.Thanks,RegiHello, For L2, L3 Policy Validations see wiki page -Validations will be strictly enforced by NSO. after M6 release.Regards,Janaki Duggirala |
Not able to create the sr-policy using TSDN package : Hi Team,I have load merged all the configs in NSO and did all the changes in NSO config file. I have followed all the steps in the attached file but I am getting below error. I am attaching the screenshot of the error and file which I followed to configure configs.Regards,Faisal | Hello, looks to be an issue with packages not loading correctly.Can you please run on NSO:(oper-mode)> show packages package oper-statusand check/post if all packages are loaded and no errors are seen?Hi Janaki,Packages were loaded correctly that's why we were able to access the yang path from NSO cli. Anyways for your reference I am attaching the oper-status screenshot from NSO.Regards,FaisalCan we have a quick call today to fix this issue?Yes, I have pinged you on Webex teams and dropping a note here as well. Let me know a good time for you and we can setup a call.Regards,Janaki DuggiralaHi Janaki,Have you used netsim devices for creation of policy?Regards,FaisalWe can meet 9:30 PM IST, please ping me by then. I will be available. After meeting with Faisal, documenting notes below:From the meeting, Faisal was using TSDN 3.0 with NSO 5.7.5.1.Requested Faisal to switch to TSDN 4.0 M8 release.Provided Faisal with Wiki Links for TSND 4.0 and M8Hi Janaki,We have deployed the .0 package and load merged the bootstrap files. Now I am able to create the policies.Thank you so much for the help.You can go ahead and close the ticket.Regards,FaisalThank you FaisalCustomer was requested to switch to TSDN 4.0 from TSDN 3.0 with NSO 5.7.x and they have created sr-te policies successfully using the wiki pages. |
Mandatory values for Circuit style: Kindly share the mandatory configuration commands for Circuit style with respect to CNC/NSO.Sharing below mandatory fields to bring up a CS policy oper up from Device point of view.NSO seems to have only headend , tailend and working path metric as mandatory values. Kindly suggestpolicy igp-l1-l7-16 bandwidth 50000 color 16 end-point ipv4 192.168.20.7 autoroute include ipv4 all ! path-protection ! candidate-paths preference 10 dynamic pcep ! metric type te ! ! backup-ineligible ! constraints segments protection unprotected-only adjacency-sid-only ! ! bidirectional co-routed association-id 10 ! ! preference 20 dynamic pcep ! metric type te ! ! constraints segments protection unprotected-only adjacency-sid-only ! disjoint-path group-id 7 type node sub-id 70 ! bidirectional co-routed association-id 11 ! ! preference 30 dynamic pcep ! metric type te ! ! constraints segments protection unprotected-only adjacency-sid-only ! disjoint-path group-id 7 type node sub-id 70 ! bidirectional co-routed association-id 12 ! ! ! performance-measurement liveness-detection liveness-profile backup name CS-protected liveness-profile name CS-working ! | Hi Ajitha, I will reply to this tomorrow. We are overloaded with M6 related items today.Hi Ajitha, below is a sparse tree with current mandatory nodes for CS SR-TE:<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"><pre class="code-java">module: cisco-cs-sr-te-cfp +--rw cs-sr-te-policy* [name]| +--rw name string| +--rw head-end | | +--rw device -> /ncs:devices/lsa-utils:lsa/dispatch-map/device/name | | +--rw ip-address inet:ip-address | +--rw tail-end | | +--rw device -> /ncs:devices/lsa-utils:lsa/dispatch-map/device/name | | +--rw ip-address inet:ip-address| +--rw (color-choice)? | | +--:(auto-color) | | | +--rw auto-color? empty | | +--:(color) | | +--rw color? uint32| +--rw path-protection! (Only dynamic, M6)| +--rw working-path | | +--rw (sr-te-path-choice)?| | +--:(explicit-path) | | | +--rw explicit| | | +--rw (forward-sid-list-type)?| | | | +--:(forward-sid-list-name)| | | | | +--rw forward-sid-list-name? -> /cisco-sr-te-cfp:sr-te/cisco-sr-te-cfp-sr-policies:policies/sid-list/name| | | | +--:(forward-sid-list)| | | | +--rw forward-sid-list!| | | +--rw (reverse-sid-list-type)?| | | +--:(reverse-sid-list-name)| | | | +--rw reverse-sid-list-name -> /cisco-sr-te-cfp:sr-te/cisco-sr-te-cfp-sr-policies:policies/sid-list/name| | | +--:(reverse-sid-list)| | | +--rw reverse-sid-list!| | +--:(dynamic-path) | | +--rw dynamic! | | +--rw constraints| | | +--rw segments!| | | | +--rw protection? enumeration (Only dynamic, M6)</pre></div></div>It is very similar to SR-TE Policy mandatory nodes.For reference here is a sparse tree with mandatory nodes for SR-TE Policy:<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"><pre class="code-java">module: cisco-sr-te-cfp-sr-policies augment /cisco-sr-te-cfp:sr-te: +--rw policies +--rw policy* [name] | +--rw name cisco-sr-te-cfp-sr-types:Cisco-ios-xr-string | +--rw head-end* [name] | | +--rw name -> /core-fp-common:dispatch-map/device| +--rw tail-end inet:ip-address | +--rw color uint32| +--rw path* [preference] | | +--rw preference uint16</pre></div></div>As you can see for both SR-TE Policy and CS SR-TE Policy, we dont enforce a complete policy as mandatory. It is up to user to configure the policy as they need.Thanks,Isaac KimHi Ajitha, we have not received a reply for a week. I believe we have provided a sufficient response. I will close this ticket.If you have any additional questions, please feel free to reopen this ticket.Thanks,Isaac KimSufficient information provided to submitter. Behavior is as expected. |
Maximum number of headend on a single ODN policy: What is the max number of headend that we can configure on a ODN policy? One of the customer is asking below Can ODN Template contain 2400 head-ends per policy? Could I get an answer before 4:00 PM today? | Hi Joby ,For SR ODN ,yang models supports as many headends .So customer should be fine .Thanks,Priyanka |
With 5 Current users - Client.Timeout exceeded while awaiting headers error seen for API request for provisioning services : Build: CW130, COE95, CAT115, CS51, SH129, CDG118, .7.6-4.1.0-M2NSO setup: ( credetails: admin/Cwork123!)CFS: 172.29.109.131RFS1: 172.29.109.132RFS2: 172.29.109.133In latest 4.1 build, while we are trying to use 5 concurrent users to create services, we are facing this same issue continuously and the services creating are failing in API. We have used 5 concurrent users to provision services.we tried provisioning L2vpn P2P services.{"error":"Patch https://172.29.106.131:8888/restconf/data/: context deadline exceeded (Client.Timeout exceeded while awaiting headers)","code":500}Showtech at 10.56.116.240 ( nso/Public1234!)/home/nso/cw130-cat115-sh129-service-provisioning-failing | Hi Arun,Please provide the following details :full error message that is shown in the second screenshot.It mentions like 'object already exists'.how long it took for the request to get the object error response and context deadline error response. Would like to know about the timeouts.Regards,Nishad Subair.Hi Nishad, The second snapshot mentioned to just show many services failed. few are object already exists which is not issue.but the issue is client.Timeout exceeded.The full error message is {"error":"Patch https://172.29.106.131:8888/restconf/data/: context deadline exceeded (Client.Timeout exceeded while awaiting headers)","code":500}it throws error after 60 seconds .Thanks,Arun.M.GHi Arun,We are unable to login to the NSO set up provided.Please suggest.Regards,NishadSorry for the typo in the server ips.CFS: 172.29.106.131RFS1: 172.29.106.132RFS2: 172.29.106.133admin/Cwork123!we are facing this issue while configuring multiple l3vpn sevices sequentially with single user itself.Note: commit-queue disabled. Hi Arun,I checked NSO and it looks fine.Looks like the current timeout set is 60s . Please increase the timeout to 5 mins and try again.Regards,Nishad Subair. |
VPN Profiles created using CNC RESTCONF API not reflected in CNC until ISTP Full sync: Setup - 10.195.165.85 - xrd1/xrd1Tested with latest patch 6.1 M5+Service type-> VPN Profiles created from CNC REST CONF is not reflected in CNC UI/NSO Connector log.But NSO shows the VPN Profiles.Please check and confirm if NSO advertises it to NSO connector. | Can you give us your setup credentials to verify?The credentials xrd1/xrd1 does not seem to work. Is this NSO setup?Hi, please provide a reply.If there is no response for a week, we will close this ticket and you may open a new JSD if you face again.Thanks,Isaac KimKindly close the ticketDefect CSCwe08193 was raised for tracking with CNC devCDETs was created for this issue. |
New validation on CS policy service: Installing the new NSO FP7 I noticed a service that we use to deploy in previous versions successfully is now failing due to new validation with error message: policy-type cs-policy is only available for vpn-type vpws-evpnThe service uses VPN type vpn-common:vpws and 2 VPN nodes using explicit TE service mapping with policy type: cs-policy (now valid for deployment only with policy type: policy)I couldnt find any information about this new restriction in the documentation Is this expected behavior? are the CS services supporting cs-policies only of VPN type: vpn-common:vpws-evpn or is this some bug in the latest FP?Service name: CS-EXPLICIT-560NSO server: credentials: admin / Public1234!CW server: credentials: admin / Public1234! | Not a valid use-case. Discussed with submitter on email. There is currently an active discussion about this case. Duplicate CDETs about the same has already been raised. |
CSCwe96179 - NSO HA VIP goes unreachable and unable to provision service when Secondary node is down: Tested in build CW 5.0.0.26 release + NSO 6.1 M8CW - 192.168.133.105 - admin/Cnc@1234 - cw-admin/Ovatest123@NSO - VIP 192.168.133.202 - primary 192.168.133.112 - Secondary 192.168.133.203 - xrd1/xrd1Login to Crosswork with NSO HA. Provider page->NSO entry - use only VIP IP as expected.Execute command 'reboot' in secondary NSO CLI.VIP IP goes unreachable. Unable to ping/login to NSO with VIP IP , though Primary node is up. (Observation 1)Even after secondary node comes up, HA didn't come up automatically. "show high-availability status" and "show ncs-state ha" shows none.HA established only after executing "request high-availability enable" in both NSOs.Please find attached webex recordingPassword: VePraDF4 | Kindly help with below defects asapWill do a debug session with Ajitha.Hi Ajitha,Per NSO-HA guide, this is an expected behavior:If you still have a question regarding this issue, lets have a discussion.Left a message to Ajitha if she still needs clarification and help with this expected behavior.Spoke to Ajitha and agreed we could close the ticket. |