NSO Integration Status - NETCONF port: From: Kavipriya Venkatraman -X (kavipven - INFOSYS LIMITED at Cisco) <kavipven@cisco.com> Sent: Tuesday, September 13, 2022 10:57 AMTo: Nirali Vasoya (nvasoya) <nvasoya@cisco.com>; Jason Wycoff (jwycoff) <jwycoff@cisco.com>Cc: infy-crossworkeks-dev(mailer list) <infy-crossworkeks-dev@cisco.com>; Rajesh Tupakula -X (rtupakul - INFOSYS LIMITED at Cisco) <rtupakul@cisco.com>; Srinivas Thirkateh -X (sthirkat - INFOSYS LIMITED at Cisco) <sthirkat@cisco.com>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