1 .. This work is licensed under a Creative Commons Attribution 4.0
2 .. International License. http://creativecommons.org/licenses/by/4.0
3 .. Copyright © 2017-2021 Aarna Networks, Inc.
5 vFWCL deployment Tutorial
6 #########################
11 This tutorial describes the step by step instructions on how to achieve the control loop for vFW use case. Instructions in this tutorial will enable you to deploy the vfw control loop specific usecase.
13 vFW service components
14 ~~~~~~~~~~~~~~~~~~~~~~
16 The vFW service is composed of the following components
20 - It is a packet generator which sends periodically different volumes of traffic to the sink through the firewall (vFw)
24 - Firewall: Reports the volume of traffic passing through to the DCAE collector (VES collector). The vFW has no real firewalling functionality.
25 - Traffic sink: Provides a graphical representation (bar charts) showing the volume of incoming traffic.
27 The below block diagram shows about the components part of vFW usecase
31 vFWCL service overview
32 ~~~~~~~~~~~~~~~~~~~~~~
34 The vFW contol loop use case consists in applying policy rules that aim to re-adjust the traffic volume
35 when high threshold (700 packets/10s) or low threshold (300 packets/10s) are crossed. In fact, the DCAE collects
36 events from the vFW, applies analytics (Threshold Crossing Analytics: TCA microservice) and publishes events to DMaap.
37 When detecting the triggering event, the policy engine executes the operational policy via the APP-C that modifies
38 vPKG application configurations in order to adjust the traffic volume to 500 packet per 10 seconds.
40 The vFW control loop is based on VES (VNF Event Stream) reported measurements that TCA analyses and publishes
41 related alams to DMaap. The policy has the responsibility for triggering ModifyConfig action that APPC executes
42 on the target vnf (vPKG). All closed loop interactions are relying on the Message router (DMaap) by publishing
43 topics and subscribing to them.
45 The ladder diagram below describes the components and their interactions that take place while running the vFWCL
50 vFW service design and deployment should be completed before following the steps of this tutorial
52 Refer the below tutorials for doing vFW service design and deployment
57 vFW Design Tutorial <../vfw-design-tutorial/index.rst>
58 vFW Deployment Tutorial <../vfw-deployment-tutorial/index.rst>
60 Adding DCAE artifacts and policies
61 ==================================
63 Follow the below steps to upload the blueprint for the TCA (Threshold Checking Application) DCAE microservice
64 and Distribute the service to the CLAMP
66 1. Login as DESIGNER (cs0008) and create the service, checkin and certify
70 2. Add any VNF (ex: vfw_pg) that was already created during the SDC design phase
72 In the composition canvas drag and drop a resource of type VF from the abstract section in the Elements section (left hand side panel)
76 3. Download the required DCAE MS blueprint to be attached to the service
78 Use the sample TCA blueprint located here:
79 https://git.onap.org/dcaegen2/platform/blueprints/tree/blueprints/k8s-tcagen2-clampnode.yaml
82 * Check if the version of the plugin used in the blueprint is different from existing, then update the blueprint import to match
83 * To check the version run this: `cfy plugins list | grep k8splugin`
85 4. Now upload the Control Loop Artifact. The procedure to upload the artifact is
87 * Click on the VF, as in the picture above the ‘vsp_pg 0’ is selected
88 * Click on ‘DEPLOYMENT ARTIFACTS’ and then click on “Add Artifact”
92 * Fill the details and in the type select DCAE_INVENTORY_BLUEPRINT, then click on Done as in the picture shown below
96 5. After uploading the DCAE artifact to the SDC Service, attach the policy model to the Service. From the left drop down,
97 select TCA policy under Policies, and click on the Add policy
101 6. Click on Checkin on top right corner then click OK
105 7. Search and select the same service from CATALOG and click on Certify on top right corner
109 8. Click Distribute to distribute the service, then click on Distribution in the left hand side panel and monitor until
110 the distribution is complete. We should see artifacts deployed in CLAMP and Policy engine, as can be seen in the picture below
114 At this point we can open the CLAMP GUI and verify that the DCAE microservice design template is in place
116 Deploy DCAE and Policy through CLAMP
117 ====================================
119 CLAMP is a GUI tool which enables the users to design the policies, distribute them to the DROOLS engine and eventually deploy
120 the DCAE microservices.
122 1. Add the necessary certificates in the browser to login to the CLAMP GUI
124 The default certificate can be found here: https://gerrit.onap.org/r/gitweb?p=clamp.git;a=blob;f=src/main/resources/clds/aaf/org.onap.clamp.p12;h=268aa1a3ce56e01448f8043cc0b05b5fceb5a47d;hb=HEAD
126 The password is: "China in the Spring"
127 The certificate must be loaded into your favorite browser before trying to load the CLAMP UI.
129 2. After the certificate is added, the CLAMP GUI can be accessed at:
130 `https://<host_IP>:30258` (host_IP is the node IP where CLAMP is running)
132 3. Before designing the policy we need to undeploy the default tca policy.
133 To undeploy default policy execute the below commands on control node
137 > kubectl get deployments -n onap | grep "dep-dcae-tca-analytics\|dcaegen2-analytics-tca" | awk '{print $1}' |
138 xargs kubectl delete deployments -n onap
139 > kubectl get svc -n onap | grep "dcae-tca-analytics\|dcaegen2-analytics-tca" | awk '{print $1}' |
140 xargs kubectl delete svc -n onap
141 To Verify there are no dcae-analytics POD, run the below command
142 > kubectl get pods -n onap | grep 'analytics'
144 4. If the service has been distributed correctly, following is how the service design templates
145 listed in the Loop Templates as below
149 Available Policy Models
153 5. Create the loop from the templates distributed by SDC
159 6. Add the Operational Policy
160 Click on Loop Instance drop down and select Modify then click, select the policy model type then click Add
166 7. Click on the MS application box and configure
167 Fill the details in the pop up window and click on the save changes button.
169 A. Click on app and Edit the Policy details, fill the below details
171 * eventName: vFirewallBroadcastPackets
173 * policyVersion: v0.0.1
174 * Select controlLoopSchemaType as VM
175 * policyName: DCAE.Config_tca-hi-lo
176 * Select Pdp Group Info from the drop down as defaultGroup & xacm
180 B. Click on the Add monitoring threshold1 button and fill the below details
183 * closedLoopControlName : name of the CL (ex: LOOP_TEMPLATE_mytest_srv_v1_0_vsp_pg0_k8s-tca)
184 * select the direction from dropdown (ex: LESS)
188 C. Click on the Add monitoring threshold2 button and fill the details same as above then click on Save Changes button
192 8. Click on the Operational policy box and configure
193 Fill the details in the pop window then click on save changes
199 9. Submit the control loop to the policy
200 From Loop Operations drop down select SUBMIT and click
204 10. Deploy the control loop to DCAE
205 From Loop Operations drop down select DEPLOY and click, verify the details and click Deploy
215 A successful deployment will make the service as DEPLOYED
217 11. You can login into the control node and verify whether your new analytics application got deployed using below command
221 > kubectl get pods -n onap | grep analytics
223 dep-dcae-tca-analytics-7fccbf459-xkxlq 2/2 Running 0 6m15s
225 > cfy deployment list | grep CLAMP
227 | CLAMP_615bb47a-ea3e-4a02-8928-0564df900826 | CLAMP_615bb47a-ea3e-4a02-8928-0564df900826 | 2020-11-10 19:23:22.286 |
228 2020-11-10 19:23:22.286 | tenant | default_tenant | admin |
233 Run the Robot heatbridge script to populate the vserver (OAM IP, VM flavor name, ID etc.) related information in AAI.
234 This is required by APPC/SDNC for performing LCM operations.
236 Following is the command usage along with the example
238 ./demo-k8s.sh <namespace> heatbridge <stack_name> <service_instance_id> <service> <oam-ip-address>
241 The stack_name & oam-ip-address of the VNF VM can be obtained from OpenStack Horizon and service_instance_id from the VID screen
245 ./demo-k8s.sh onap heatbridge vfw_sinc_vf e039b3d4-7ee5-4ad2-8108-ae31086ac7c0 vFW 172.29.249.157
246 Number of parameters:
250 ++ kubectl --namespace onap get pods
253 + POD=dev-robot-58f85bb64d-zz5bh
254 ++ dirname ./demo-k8s.sh
256 + SCRIPTDIR=scripts/demoscript
257 + ETEHOME=/var/opt/ONAP
259 ++ kubectl --namespace onap exec dev-robot-58f85bb64d-zz5bh -- bash -c 'ls -1q /share/logs/ | wc -l'
260 + export GLOBAL_BUILD_NUMBER=13
261 + GLOBAL_BUILD_NUMBER=13
263 + OUTPUT_FOLDER=0013_demo_heatbridge
265 + VARIABLEFILES='-V /share/config/robot_properties.py'
266 + kubectl --namespace onap exec dev-robot-58f85bb64d-zz5bh -- /var/opt/ONAP/runTags.sh -V /share/config/robot_properties.py -v HB_STACK:vfw_sinc_vf
267 -v HB_VNF:e039b3d4-7ee5-4ad2-8108-ae31086ac7c0 -v HB_VNF:vFW -v HB_SERVICE:vFW -v HB_IPV4_OAM_ADDRESS:172.29.249.157 -d /share/logs/0013_demo_heatbridge
268 -i heatbridge --display 103
269 Starting Xvfb on display :103 with res 1280x1024x24
270 Executing robot tests at log level TRACE
271 ==============================================================================
273 ==============================================================================
274 Testsuites.Demo :: Executes the VNF Orchestration Test cases including setu...
275 ==============================================================================
276 Run Heatbridge :: Try to run heatbridge | PASS |
277 ------------------------------------------------------------------------------
278 Testsuites.Demo :: Executes the VNF Orchestration Test cases inclu... | PASS |
279 1 critical test, 1 passed, 0 failed
280 1 test total, 1 passed, 0 failed
281 ==============================================================================
283 1 critical test, 1 passed, 0 failed
284 1 test total, 1 passed, 0 failed
285 ==============================================================================
286 Output: /share/logs/0013_demo_heatbridge/output.xml
287 Log: /share/logs/0013_demo_heatbridge/log.html
288 Report: /share/logs/0013_demo_heatbridge/report.html
290 Update the operational policy
291 =============================
293 1. GET the modelInvariantID of vPG
295 Following is the command usage along with the sample output
299 curl -k -X GET https://<kubernetes-host>:30233/aai/v11/network/generic-vnfs/ -H 'Accept: application/json' -H 'Authorization: Basic QUFJOkFBSQ==' -H ' Content-Type: application/json' -H 'X-FromAppId: Postman' -H 'X-TransactionId: get_generic_vnf' | jq
304 "vnf-id": "edc085e8-5088-4b73-bcdc-b8b0bf5e528b",
305 "vnf-name": "vfw_vpg_vnf",
306 "vnf-type": "vFWCL_service/vsp_vpg 0",
307 "service-id": "929190d1-fed1-4dff-883f-f0ede779065e",
308 "prov-status": "PREPROV",
309 "orchestration-status": "Created",
311 "is-closed-loop-disabled": false,
312 "resource-version": "1609783281808",
313 "model-invariant-id": "7d4fef5e-f9b0-4e03-a653-712d6630f389",
314 "model-version-id": "a248f68e-c1f2-4b25-8120-c4f7310b0d1e",
315 "model-customization-id": "cf0019db-f51f-472a-996d-9da19d41f7b4",
316 "relationship-list": {
319 "related-to": "service-instance",
320 "related-link": "/aai/v11/business/customers/customer/Demonstration/service-subscriptions/service-subscription/vFWCL/service-instances/service- instance/e039b3d4-7ee5-4ad2-8108-ae31086ac7c0",
321 "relationship-data": [
323 "relationship-key": "customer.global-customer-id",
324 "relationship-value": "Demonstration"
327 "relationship-key": "service-subscription.service-type",
328 "relationship-value": "vFWCL"
331 "relationship-key": "service-instance.service-instance-id",
332 "relationship-value": "e039b3d4-7ee5-4ad2-8108-ae31086ac7c0"
335 "related-to-property": [
337 "property-key": "service-instance.service-instance-name",
338 "property-value": "vFWCL_srv_00"
343 "related-to": "platform",
344 "related-link": "/aai/v11/business/platforms/platform/Platform-Demonstration",
345 "relationship-data": [
347 "relationship-key": "platform.platform-name",
348 "relationship-value": "Platform-Demonstration"
353 "related-to": "line-of-business",
354 "related-link": "/aai/v11/business/lines-of-business/line-of-business/LOB-Demonstration",
355 "relationship-data": [
357 "relationship-key": "line-of-business.line-of-business-name",
358 "relationship-value": "LOB-Demonstration"
366 "vnf-id": "816040b6-d9bf-43ba-b852-e31e21a0a5f4",
367 "vnf-name": "vfw_sinc_vnf",
368 "vnf-type": "vFWCL_service/vsp_sinc 0",
369 "service-id": "929190d1-fed1-4dff-883f-f0ede779065e",
370 "prov-status": "ACTIVE",
371 "orchestration-status": "Active",
373 "is-closed-loop-disabled": false,
374 "resource-version": "1609788164862",
375 "model-invariant-id": "4d432903-4338-48ae-a105-47c0c8d19193",
376 "model-version-id": "86b98636-150b-4f1c-a768-61e6c43a3199",
377 "model-customization-id": "d3671119-5b65-40ed-abea-d1fe0d09c3ba",
378 "relationship-list": {
381 "related-to": "vserver",
382 "related-link": "/aai/v11/cloud-infrastructure/cloud-regions/cloud- region/CloudOwner/RegionOne/tenants/tenant/747a01548b494670892413c496c1c250/vservers/vserver/3353a853-87cc-47cc-9e6a-4f45b6dc580f",
383 "relationship-data": [
385 "relationship-key": "cloud-region.cloud-owner",
386 "relationship-value": "CloudOwner"
389 "relationship-key": "cloud-region.cloud-region-id",
390 "relationship-value": "RegionOne"
393 "relationship-key": "tenant.tenant-id",
394 "relationship-value": "747a01548b494670892413c496c1c250"
397 "relationship-key": "vserver.vserver-id",
398 "relationship-value": "3353a853-87cc-47cc-9e6a-4f45b6dc580f"
401 "related-to-property": [
403 "property-key": "vserver.vserver-name",
404 "property-value": "zdfw1fwl01snk01"
409 "related-to": "vserver",
410 "related-link": "/aai/v11/cloud-infrastructure/cloud-regions/cloud- region/CloudOwner/RegionOne/tenants/tenant/747a01548b494670892413c496c1c250/vservers/vserver/642b5709-4f3d-405b-bcb2-dc82884cb8de",
411 "relationship-data": [
413 "relationship-key": "cloud-region.cloud-owner",
414 "relationship-value": "CloudOwner"
417 "relationship-key": "cloud-region.cloud-region-id",
418 "relationship-value": "RegionOne"
421 "relationship-key": "tenant.tenant-id",
422 "relationship-value": "747a01548b494670892413c496c1c250"
425 "relationship-key": "vserver.vserver-id",
426 "relationship-value": "642b5709-4f3d-405b-bcb2-dc82884cb8de"
429 "related-to-property": [
431 "property-key": "vserver.vserver-name",
432 "property-value": "zdfw1fwl01fwl01"
437 "related-to": "service-instance",
438 "related-link": "/aai/v11/business/customers/customer/Demonstration/service-subscriptions/service-subscription/vFWCL/service-instances/service- instance/e039b3d4-7ee5-4ad2-8108-ae31086ac7c0",
439 "relationship-data": [
441 "relationship-key": "customer.global-customer-id",
442 "relationship-value": "Demonstration"
445 "relationship-key": "service-subscription.service-type",
446 "relationship-value": "vFWCL"
449 "relationship-key": "service-instance.service-instance-id",
450 "relationship-value": "e039b3d4-7ee5-4ad2-8108-ae31086ac7c0"
453 "related-to-property": [
455 "property-key": "service-instance.service-instance-name",
456 "property-value": "vFWCL_srv_00"
461 "related-to": "platform",
462 "related-link": "/aai/v11/business/platforms/platform/Platform-Demonstration",
463 "relationship-data": [
465 "relationship-key": "platform.platform-name",
466 "relationship-value": "Platform-Demonstration"
471 "related-to": "line-of-business",
472 "related-link": "/aai/v11/business/lines-of-business/line-of-business/LOB-Demonstration",
473 "relationship-data": [
475 "relationship-key": "line-of-business.line-of-business-name",
476 "relationship-value": "LOB-Demonstration"
486 2. Get the Operational policy name and version
488 Following is the command usage and the sample output
492 curl -k -u 'healthcheck:zb!XztG34' -X GET -H 'Accept:application/json' https://<kubernetes-host>:6969/policy/pap/v1/pdps
494 #sample command and output
495 curl -k -u 'healthcheck:zb!XztG34' -X GET -H 'Accept:application/json' https://10.43.244.213:6969/policy/pap/v1/pdps | jq
496 % Total % Received % Xferd Average Speed Time Time Time Current
497 Dload Upload Total Spent Left Speed
498 100 2678 100 2678 0 0 7695 0 --:--:-- --:--:-- --:--:-- 7695
502 "name": "defaultGroup",
503 "description": "The default group that registers all supported policy types and pdps.",
504 "pdpGroupState": "ACTIVE",
509 "supportedPolicyTypes": [
511 "name": "onap.policies.controlloop.operational.Apex",
515 "name": "onap.policies.controlloop.operational.common.Apex",
519 "name": "onap.policies.native.Apex",
524 "currentInstanceCount": 1,
525 "desiredInstanceCount": 1,
529 "instanceId": "dev-policy-apex-pdp-0",
530 "pdpState": "ACTIVE",
531 "healthy": "HEALTHY",
532 "message": "Pdp Heartbeat"
538 "supportedPolicyTypes": [
540 "name": "onap.policies.controlloop.Operational",
544 "name": "onap.policies.controlloop.operational.common.Drools",
548 "name": "onap.policies.native.drools.Controller",
552 "name": "onap.policies.native.drools.Artifact",
557 "currentInstanceCount": 1,
558 "desiredInstanceCount": 1,
562 "instanceId": "dev-drools-0",
563 "pdpState": "ACTIVE",
570 "supportedPolicyTypes": [
572 "name": "onap.policies.controlloop.guard.common.FrequencyLimiter",
576 "name": "onap.policies.controlloop.guard.common.MinMax",
580 "name": "onap.policies.controlloop.guard.common.Blacklist",
584 "name": "onap.policies.controlloop.guard.coordination.FirstBlocksSecond",
588 "name": "onap.policies.monitoring.*",
592 "name": "onap.policies.optimization.*",
596 "name": "onap.policies.optimization.resource.AffinityPolicy",
600 "name": "onap.policies.optimization.resource.DistancePolicy",
604 "name": "onap.policies.optimization.resource.HpaPolicy",
608 "name": "onap.policies.optimization.resource.OptimizationPolicy",
612 "name": "onap.policies.optimization.resource.PciPolicy",
616 "name": "onap.policies.optimization.service.QueryPolicy",
620 "name": "onap.policies.optimization.service.SubscriberPolicy",
624 "name": "onap.policies.optimization.resource.Vim_fit",
628 "name": "onap.policies.optimization.resource.VnfPolicy",
632 "name": "onap.policies.native.Xacml",
636 "name": "onap.policies.Naming",
642 "name": "SDNC_Policy.ONAP_NF_NAMING_TIMESTAMP",
646 "currentInstanceCount": 1,
647 "desiredInstanceCount": 1,
651 "instanceId": "dev-policy-xacml-pdp-6c5f6db887-zkh6h",
652 "pdpState": "ACTIVE",
662 3. Remove the vFW Policy from PDP
664 Following is the command usage
668 POLICY_ID = "OPERATIONAL_dcae_service_v1_0_Drools_1_0_0_of6"
669 POLICY_VERSION = "1.0.0"
671 curl -k -u 'healthcheck:zb!XztG34' -X DELETE -H 'Content-Type:application/json' https://<kubernetes-host>:6969/policy/pap/v1/pdps/policies/$POLICY_ID/versions/$POLICY_VERSION
675 Following is the command usage and sample output
679 POLICY_TYPEID="onap.policies.controlloop.operational.common.Drools"
681 POLICY_ID="OPERATIONAL_dcae_service_v1_0_Drools_1_0_0_of6"
683 curl -k -u 'healthcheck:zb!XztG34' -X GET -H 'Accept:application/json' https://<kubernetes-host>:6969/policy/api/v1/policytypes/$POLICY_TYPEID/versions/$VERSIONID/policies/$POLICY_ID/versions/latest > operational_policy_template.json
685 5. Update this policy in the policy DB
687 Following is the command usage and sample output
691 POLICY_TYPEID="onap.policies.controlloop.operational.common.Drools"
694 curl -k -u 'healthcheck:zb!XztG34' -X POST -H 'Content-Type:application/json' --data @./operational_policy_template.json https://<kubernetes-host>:6969/policy/api/v1/policytypes/$POLICY_TYPEID/versions/$VERSIONID/policies
697 "tosca_definitions_version": "tosca_simple_yaml_1_1_0",
698 "topology_template": {
700 "OPERATIONAL_dcae_service_v1_0_Drools_1_0_0_of6": {
701 "type": "onap.policies.controlloop.operational.common.Drools",
702 "type_version": "1.0.0",
706 "failure_retries": "final_failure_retries",
707 "id": "ModifyConfig",
708 "failure_timeout": "final_failure_timeout",
709 "failure": "final_failure",
716 "resourceID": "7d4fef5e-f9b0-4e03-a653-712d6630f389"
721 "operation": "ModifyConfig"
723 "failure_guard": "final_failure_guard",
726 "failure_exception": "final_failure_exception",
727 "description": "ModifyConfig",
728 "success": "final_success"
730 "trigger": "ModifyConfig",
734 "name": "OPERATIONAL_dcae_service_v1_0_Drools_1_0_0_of6",
737 "policy-id": "OPERATIONAL_dcae_service_v1_0_Drools_1_0_0_of6",
738 "policy-version": "1.0.0"
743 "name": "ToscaServiceTemplateSimple",
748 6. Deploy this version of the policy using PAP API
750 Prepare the payload for the deployment API by naming the file as pap_template.json. The contents are policy name, version and command usage as below
754 cat pap_template.json
758 "policy-id": "OPERATIONAL_dcae_service_v1_0_Drools_1_0_0_of6",
759 "policy-version": "3"
764 curl -k -u 'healthcheck:zb!XztG34' -X POST --data @./pap_template.json -H 'Content-Type:application/json' https://<kubernetes-host>:6969/policy/pap/v1/pdps/policies
766 Set network topology for vPG in APPC
767 ====================================
769 1. Enable direct access to vFW PG VNF instance from control node
772 These steps are applicable only when your openstack instance is running on the GCP
774 You can refer to `Google Cloud Docs <https://cloud.google.com/vpc/docs/configure-alias-ip-ranges>`_ to find
775 more details about how to add IP alias to a running GCP instance
777 Execute the below commands from your laptop using gcloud CLI
779 a. Find the Default interface name and primary internal IP for the GCP instance
783 gcloud compute instances describe openstack-01 | grep 'nic\|networkIP'
785 #sample command output
787 networkIP: 10.128.0.43
789 b. For the Default interface nic0 add an IP alias from the default subnet
793 gcloud compute instances network-interfaces update openstack-01 \
794 --zone us-central1-f \
795 --network-interface nic0 \
799 Updating network interface [nic0] of instance [openstack-01]...done
801 c. Verify if the instance has got a new IP alias
805 gcloud compute instances describe openstack-01 | grep 'nic\|networkIP\|aliasIpRanges\|ipCidrRange'
807 # from the output note down the IP alias ipCidrRange attribute that you will need it inplace
809 ipCidrRange: 10.128.0.124/30
811 networkIP: 10.128.0.22
813 2. Map openstack-01 GCP IP alias to vFW PG VNF openstack instance public IP
815 a. SSH into GCP openstack-01 VM instance and verify if you can see the new IP alias in the routing table
819 ip route show table local | grep '/30'
822 local 10.128.0.112/30 dev eth0 proto 66 scope host
824 b. Find the vFW packet generator public / external network IP address
826 Run the below command on the openstack instance
830 openstack server list
832 | ID | Name | Status | Networks | Image | Flavor |
833 | 1faa6593-7e9e-452d-a5dc-1536e18e4b94 | zdfw1fwl01pgn01 | ACTIVE | OAM_NETWORK=10.10.10.12; public=172.29.249.200;
834 zdfw1fwl01_unprotected=192.168.10.200| trusty | m1.medium |
836 c. Now update openstack-01 GCP instance iptables to forward the traffic to vFW PG VNF VM
838 Below are the commands to forward all traffic reaching to IP alias (ex: 10.128.0.112/30)
839 to vFW PG VNF VM (ex:zdfw1fwl01pgn01) instance public IP (ex:172.29.249.200)
844 sudo iptables -t nat -I PREROUTING -d 10.128.0.112 -j DNAT --to-destination 172.29.249.200
845 sudo iptables -t nat -I POSTROUTING -s 172.29.249.200 -j MASQUERADE
847 # Update INPUT, FORWARD AND OUTPUT chain to allow traffic for all ports
848 sudo iptables -I INPUT 1 -p udp -j ACCEPT
849 sudo iptables -I FORWARD 1 -p tcp -j ACCEPT
850 sudo iptables -I OUTPUT 1 -p tcp -j ACCEPT
851 sudo iptables -I OUTPUT 1 -p udp -j ACCEPT
853 d. Verify if you can access vFW PG instance from the control node
855 SSH into vFW PG VNF instance using the openstack-01 GCP IP alias, it should connect to the vFW PG VNF instance
859 a. Get the VNF instance ID, either through VID or through AAI. Below the AAI request
861 Search for the vnf-name as vfw_pg_vsp_002-1 from the output of the below command and find the corresponding vnf-id,
862 the value is: a1ca05b4-3231-4e4a-a09c-74f2292fe577
866 curl -X GET https://<kubernetes-host>:30233/aai/v8/network/generic-vnfs/ -H 'Accept: application/json' -H 'Authorization: Basic QUFJOkFBSQ==' -H 'Content-Type:application/json' -H 'X-FromAppId: Postman' -H 'X-TransactionId: get_generic_vnf' -k
870 "vnf-id": "a1ca05b4-3231-4e4a-a09c-74f2292fe577",
871 "vnf-name": "vfw_pg_vsp_002-1",
872 "vnf-type": "vfw-service-002/vfw_pg_vsp_002 0",
873 "service-id": "f18af052-6dfb-40e8-ad25-f060eb898f53",
874 "prov-status": "ACTIVE",
875 "orchestration-status": "Active",
877 "is-closed-loop-disabled": false,
878 "resource-version": "1617776160138",
879 "model-invariant-id": "7a347a5a-8f3f-416c-81f3-13b30631c1e6",
880 "model-version-id": "f988048a-b4f4-4f5e-aa7c-fdaa0d7ea017",
881 "model-customization-id": "601d5d68-fbbe-4c1f-a624-08a3445ae8fe",
882 "relationship-list": {
884 "related-to": "service-instance",
885 "relationship-label": "org.onap.relationships.inventory.ComposedOf",
886 "related-link": "/aai/v16/business/customers/customer/Demonstration/service-subscriptions/service-subscription/vFW/service-instances/service-instance/6f294c8f-ac67-4b33-9e56-014fb63791a5",
887 "relationship-data": [{
888 "relationship-key": "customer.global-customer-id",
889 "relationship-value": "Demonstration"
891 "relationship-key": "service-subscription.service-type",
892 "relationship-value": "vFW"
894 "relationship-key": "service-instance.service-instance-id",
895 "relationship-value": "6f294c8f-ac67-4b33-9e56-014fb63791a5"
897 "related-to-property": [{
898 "property-key": "service-instance.service-instance-name",
899 "property-value": "vfw-service-002-1"
902 "related-to": "platform",
903 "relationship-label": "org.onap.relationships.inventory.Uses",
904 "related-link": "/aai/v16/business/platforms/platform/Platform-Demonstration",
905 "relationship-data": [{
906 "relationship-key": "platform.platform-name",
907 "relationship-value": "Platform-Demonstration"
910 "related-to": "line-of-business",
911 "relationship-label": "org.onap.relationships.inventory.Uses",
912 "related-link": "/aai/v16/business/lines-of-business/line-of-business/LOB-Demonstration",
913 "relationship-data": [{
914 "relationship-key": "line-of-business.line-of-business-name",
915 "relationship-value": "LOB-Demonstration"
918 "related-to": "vserver",
919 "relationship-label": "tosca.relationships.HostedOn",
920 "related-link": "/aai/v16/cloud-infrastructure/cloud-regions/cloud-region/CloudOwner/RegionOne/tenants/tenant/759425709b7a4b3ca257d3f93ef4e91e/vservers/vserver/856aed6e-cc25-4819-a03d-5549f5fe8662",
921 "relationship-data": [{
922 "relationship-key": "cloud-region.cloud-owner",
923 "relationship-value": "CloudOwner"
925 "relationship-key": "cloud-region.cloud-region-id",
926 "relationship-value": "RegionOne"
928 "relationship-key": "tenant.tenant-id",
929 "relationship-value": "759425709b7a4b3ca257d3f93ef4e91e"
931 "relationship-key": "vserver.vserver-id",
932 "relationship-value": "856aed6e-cc25-4819-a03d-5549f5fe8662"
934 "related-to-property": [{
935 "property-key": "vserver.vserver-name",
936 "property-value": "zdfw1fwl01pgn01"
941 "vnf-id": "be9e190e-a20c-4900-8074-cffec77131f1",
942 "vnf-name": "vfw_sinc_vsp_002-1",
943 "vnf-type": "vfw-service-002/vfw_sinc_vsp_002 0",
944 "service-id": "f18af052-6dfb-40e8-ad25-f060eb898f53",
945 "prov-status": "ACTIVE",
946 "orchestration-status": "Active",
948 "is-closed-loop-disabled": false,
949 "resource-version": "1617776104234",
950 "model-invariant-id": "9b25321d-9260-4739-97f8-7c85fba4e755",
951 "model-version-id": "c785c203-9c39-4b6a-9c2e-f24bb8d4d92d",
952 "model-customization-id": "a1e0ddf7-5d50-43a4-a6f1-0bfde3c1de78",
953 "relationship-list": {
955 "related-to": "service-instance",
956 "relationship-label": "org.onap.relationships.inventory.ComposedOf",
957 "related-link": "/aai/v16/business/customers/customer/Demonstration/service-subscriptions/service-subscription/vFW/service-instances/service-instance/6f294c8f-ac67-4b33-9e56-014fb63791a5",
958 "relationship-data": [{
959 "relationship-key": "customer.global-customer-id",
960 "relationship-value": "Demonstration"
962 "relationship-key": "service-subscription.service-type",
963 "relationship-value": "vFW"
965 "relationship-key": "service-instance.service-instance-id",
966 "relationship-value": "6f294c8f-ac67-4b33-9e56-014fb63791a5"
968 "related-to-property": [{
969 "property-key": "service-instance.service-instance-name",
970 "property-value": "vfw-service-002-1"
973 "related-to": "platform",
974 "relationship-label": "org.onap.relationships.inventory.Uses",
975 "related-link": "/aai/v16/business/platforms/platform/Platform-Demonstration",
976 "relationship-data": [{
977 "relationship-key": "platform.platform-name",
978 "relationship-value": "Platform-Demonstration"
981 "related-to": "line-of-business",
982 "relationship-label": "org.onap.relationships.inventory.Uses",
983 "related-link": "/aai/v16/business/lines-of-business/line-of-business/LOB-Demonstration",
984 "relationship-data": [{
985 "relationship-key": "line-of-business.line-of-business-name",
986 "relationship-value": "LOB-Demonstration"
989 "related-to": "vserver",
990 "relationship-label": "tosca.relationships.HostedOn",
991 "related-link": "/aai/v16/cloud-infrastructure/cloud-regions/cloud-region/CloudOwner/RegionOne/tenants/tenant/759425709b7a4b3ca257d3f93ef4e91e/vservers/vserver/30dd6250-8a74-4ed7-9729-6ce7190c6661",
992 "relationship-data": [{
993 "relationship-key": "cloud-region.cloud-owner",
994 "relationship-value": "CloudOwner"
996 "relationship-key": "cloud-region.cloud-region-id",
997 "relationship-value": "RegionOne"
999 "relationship-key": "tenant.tenant-id",
1000 "relationship-value": "759425709b7a4b3ca257d3f93ef4e91e"
1002 "relationship-key": "vserver.vserver-id",
1003 "relationship-value": "30dd6250-8a74-4ed7-9729-6ce7190c6661"
1005 "related-to-property": [{
1006 "property-key": "vserver.vserver-name",
1007 "property-value": "vfw_sinc_vsp_002-1"
1010 "related-to": "vserver",
1011 "relationship-label": "tosca.relationships.HostedOn",
1012 "related-link": "/aai/v16/cloud-infrastructure/cloud-regions/cloud-region/CloudOwner/RegionOne/tenants/tenant/759425709b7a4b3ca257d3f93ef4e91e/vservers/vserver/9ab8d517-2b1c-4d31-a04c-0fe2f8396815",
1013 "relationship-data": [{
1014 "relationship-key": "cloud-region.cloud-owner",
1015 "relationship-value": "CloudOwner"
1017 "relationship-key": "cloud-region.cloud-region-id",
1018 "relationship-value": "RegionOne"
1020 "relationship-key": "tenant.tenant-id",
1021 "relationship-value": "759425709b7a4b3ca257d3f93ef4e91e"
1023 "relationship-key": "vserver.vserver-id",
1024 "relationship-value": "9ab8d517-2b1c-4d31-a04c-0fe2f8396815"
1026 "related-to-property": [{
1027 "property-key": "vserver.vserver-name",
1028 "property-value": "zdfw1fwl01snk01"
1035 b. Get the public IP address of the Packet Generator VM from your deployment
1037 c. To mount APPC, run the below command by replacing <vnf-id> and <vnf-ip> with the values obtained from the above steps (a) & (b) respectively
1042 http://<kubernetes-host>:30230/restconf/config/network-topology:network-topology/topology/topology-netconf/node/<vnf-id> \
1043 -H 'Accept: application/xml' \
1044 -H 'Authorization: Basic YWRtaW46S3A4Yko0U1hzek0wV1hsaGFrM2VIbGNzZTJnQXc4NHZhb0dHbUp2VXkyVQ==' \
1045 -H 'Content-Type: text/xml' \
1046 -d '<node xmlns="urn:TBD:params:xml:ns:yang:network-topology">
1047 <node-id><vnf-id></node-id>
1048 <host xmlns="urn:opendaylight:netconf-node-topology"><vnf-ip></host>
1049 <port xmlns="urn:opendaylight:netconf-node-topology">830</port>
1050 <username xmlns="urn:opendaylight:netconf-node-topology">netconf</username>
1051 <password xmlns="urn:opendaylight:netconf-node-topology">netconf</password>
1052 <tcp-only xmlns="urn:opendaylight:netconf-node-topology">false</tcp-only>
1055 #smaple command and output:
1056 curl -vvv -X PUT http://192.168.122.99:30230/restconf/config/network-topology:network-topology/topology/topology-netconf/node/a1ca05b4-3231-4e4a-a09c-74f2292fe577 -H 'Accept: application/xml' -H 'Authorization: Basic YWRtaW46S3A4Yko0U1hzek0wV1hsaGFrM2VIbGNzZTJnQXc4NHZhb0dHbUp2VXkyVQ==' -H 'Content-Type: text/xml' -d '<node xmlns="urn:TBD:params:xml:ns:yang:network-topology"> <node-id>a1ca05b4-3231-4e4a-a09c-74f2292fe577</node-id> <host xmlns="urn:opendaylight:netconf-node-topology">192.168.122.238</host> <port xmlns="urn:opendaylight:netconf-node-topology">830</port> <username xmlns="urn:opendaylight:netconf-node-topology">netconf</username> <password xmlns="urn:opendaylight:netconf-node-topology">netconf</password> <tcp-only xmlns="urn:opendaylight:netconf-node-topology">false</tcp-only> </node>'
1057 * Trying 192.168.122.99...
1059 * Connected to 192.168.122.99 (192.168.122.99) port 30230 (#0)
1060 > PUT /restconf/config/network-topology:network-topology/topology/topology-netconf/node/a1ca05b4-3231-4e4a-a09c-74f2292fe577 HTTP/1.1
1061 > Host: 192.168.122.99:30230
1062 > User-Agent: curl/7.58.0
1063 > Accept: application/xml
1064 > Authorization: Basic YWRtaW46S3A4Yko0U1hzek0wV1hsaGFrM2VIbGNzZTJnQXc4NHZhb0dHbUp2VXkyVQ==
1065 > Content-Type: text/xml
1066 > Content-Length: 488
1068 * upload completely sent off: 488 out of 488 bytes
1072 * Connection #0 to host 192.168.122.99 left intact
1074 d. To verify the NETCONF connection has successfully being established, run the following request (replace <vnd-id> with yours)
1079 http://<kubernetes-host>:30230/restconf/operational/network-topology:network-topology/topology/topology-netconf/node/<vnf-id> \
1080 -H 'Accept: application/json' \
1081 -H 'Authorization: Basic YWRtaW46S3A4Yko0U1hzek0wV1hsaGFrM2VIbGNzZTJnQXc4NHZhb0dHbUp2VXkyVQ=='
1083 #smaple command and output:
1084 curl -X GET http://192.168.122.99:30230/restconf/operational/network-topology:network-topology/topology/topology-netconf/node/a1ca05b4-3231-4e4a-a09c-74f2292fe577 -H 'Accept: application/json' -H 'Authorization: Basic YWRtaW46S3A4Yko0U1hzek0wV1hsaGFrM2VIbGNzZTJnQXc4NHZhb0dHbUp2VXkyVQ==' | jq
1085 % Total % Received % Xferd Average Speed Time Time Time Current
1086 Dload Upload Total Spent Left Speed
1087 100 5368 100 5368 0 0 374k 0 --:--:-- --:--:-- --:--:-- 374k
1091 "node-id": "a1ca05b4-3231-4e4a-a09c-74f2292fe577",
1092 "netconf-node-topology:unavailable-capabilities": {},
1093 "netconf-node-topology:available-capabilities": {
1094 "available-capability": [
1096 "capability-origin": "device-advertised",
1097 "capability": "urn:ietf:params:netconf:capability:yang-library:1.0?revision=2018-01-17&module-set-id=29"
1100 "capability-origin": "device-advertised",
1101 "capability": "urn:ietf:params:netconf:base:1.1"
1104 "capability-origin": "device-advertised",
1105 "capability": "urn:ietf:params:netconf:base:1.0"
1108 "capability-origin": "device-advertised",
1109 "capability": "urn:ietf:params:netconf:capability:writable-running:1.0"
1112 "capability-origin": "device-advertised",
1113 "capability": "urn:ietf:params:netconf:capability:validate:1.1"
1116 "capability-origin": "device-advertised",
1117 "capability": "urn:ietf:params:netconf:capability:with-defaults:1.0?basic-mode=explicit&also-supported=report-all,report-all-tagged,trim,explicit"
1120 "capability-origin": "device-advertised",
1121 "capability": "urn:ietf:params:netconf:capability:interleave:1.0"
1124 "capability-origin": "device-advertised",
1125 "capability": "urn:ietf:params:netconf:capability:rollback-on-error:1.0"
1128 "capability-origin": "device-advertised",
1129 "capability": "urn:ietf:params:netconf:capability:xpath:1.0"
1132 "capability-origin": "device-advertised",
1133 "capability": "urn:ietf:params:netconf:capability:startup:1.0"
1136 "capability-origin": "device-advertised",
1137 "capability": "urn:ietf:params:netconf:capability:candidate:1.0"
1140 "capability-origin": "device-advertised",
1141 "capability": "urn:ietf:params:netconf:capability:notification:1.0"
1144 "capability-origin": "device-advertised",
1145 "capability": "(urn:ietf:params:xml:ns:netconf:notification:1.0?revision=2008-07-14)notifications"
1148 "capability-origin": "device-advertised",
1149 "capability": "(urn:ietf:params:xml:ns:yang:iana-crypt-hash?revision=2014-08-06)iana-crypt-hash"
1152 "capability-origin": "device-advertised",
1153 "capability": "(urn:ietf:params:xml:ns:yang:ietf-x509-cert-to-name?revision=2014-12-10)ietf-x509-cert-to-name"
1156 "capability-origin": "device-advertised",
1157 "capability": "(urn:ietf:params:xml:ns:yang:ietf-system?revision=2014-08-06)ietf-system"
1160 "capability-origin": "device-advertised",
1161 "capability": "(urn:ietf:params:xml:ns:yang:ietf-netconf-monitoring?revision=2010-10-04)ietf-netconf-monitoring"
1164 "capability": "(urn:ietf:params:xml:ns:yang:ietf-datastores?revision=2017-08-17)ietf-datastores"
1167 "capability-origin": "device-advertised",
1168 "capability": "(urn:ietf:params:xml:ns:yang:1?revision=2017-02-20)yang"
1171 "capability-origin": "device-advertised",
1172 "capability": "(urn:ietf:params:xml:ns:yang:ietf-interfaces?revision=2014-05-08)ietf-interfaces"
1175 "capability-origin": "device-advertised",
1176 "capability": "(urn:ietf:params:xml:ns:yang:iana-if-type?revision=2014-05-08)iana-if-type"
1179 "capability": "(urn:ietf:params:xml:ns:yang:ietf-netconf-server?revision=2016-11-02)ietf-netconf-server"
1182 "capability-origin": "device-advertised",
1183 "capability": "(urn:opendaylight:params:xml:ns:yang:sample-plugin?revision=2016-09-18)sample-plugin"
1186 "capability-origin": "device-advertised",
1187 "capability": "(http://nokia.com/pnf-simulator)pnf-simulator"
1190 "capability": "(urn:ietf:params:xml:ns:yang:ietf-ssh-server?revision=2016-11-02)ietf-ssh-server"
1193 "capability-origin": "device-advertised",
1194 "capability": "(urn:ietf:params:xml:ns:yang:ietf-netconf-notifications?revision=2012-02-06)ietf-netconf-notifications"
1197 "capability-origin": "device-advertised",
1198 "capability": "(urn:ietf:params:xml:ns:netconf:base:1.0?revision=2011-06-01)ietf-netconf"
1201 "capability-origin": "device-advertised",
1202 "capability": "(urn:ietf:params:xml:ns:yang:ietf-yang-types?revision=2013-07-15)ietf-yang-types"
1205 "capability": "(urn:mynetconf:test?revision=2019-03-01)mynetconf"
1208 "capability": "(urn:ietf:params:xml:ns:yang:ietf-keystore?revision=2016-10-31)ietf-keystore"
1211 "capability-origin": "device-advertised",
1212 "capability": "(urn:ietf:params:xml:ns:netmod:notification?revision=2008-07-14)nc-notifications"
1215 "capability-origin": "device-advertised",
1216 "capability": "(urn:ietf:params:xml:ns:yang:ietf-yang-metadata?revision=2016-08-05)ietf-yang-metadata"
1219 "capability-origin": "device-advertised",
1220 "capability": "(urn:ietf:params:xml:ns:yang:ietf-inet-types?revision=2013-07-15)ietf-inet-types"
1223 "capability-origin": "device-advertised",
1224 "capability": "(http://example.net/turing-machine?revision=2013-12-27)turing-machine"
1227 "capability": "(urn:ietf:params:xml:ns:yang:ietf-tls-server?revision=2016-11-02)ietf-tls-server"
1230 "capability-origin": "device-advertised",
1231 "capability": "(urn:ietf:params:xml:ns:yang:ietf-netconf-with-defaults?revision=2011-06-01)ietf-netconf-with-defaults"
1234 "capability": "(urn:ietf:params:xml:ns:yang:ietf-yang-library?revision=2018-01-17)ietf-yang-library"
1237 "capability-origin": "device-advertised",
1238 "capability": "(urn:ietf:params:xml:ns:yang:ietf-ip?revision=2014-06-16)ietf-ip"
1241 "capability-origin": "device-advertised",
1242 "capability": "(urn:ietf:params:xml:ns:yang:ietf-netconf-acm?revision=2018-02-14)ietf-netconf-acm"
1245 "capability-origin": "device-advertised",
1246 "capability": "(urn:opendaylight:params:xml:ns:yang:stream-count?revision=2016-09-18)stream-count"
1250 "netconf-node-topology:host": "192.168.122.238",
1251 "netconf-node-topology:clustered-connection-status": {
1252 "netconf-master-node": "akka.tcp://opendaylight-cluster-data@127.0.0.1:2550"
1254 "netconf-node-topology:connection-status": "connected",
1255 "netconf-node-topology:port": 830
1263 1. The information that we need to configure the VPP reporter (which is the VES agent application
1264 that generates events destined for the ONAP VES collector) is the VES IP and port.
1265 The below instructions can be used for this configuration
1269 kubectl get svc -n onap -o wide | grep ves
1270 dcae-hv-ves-collector ClusterIP 10.43.130.145 <none> 6061/TCP 12d app=dcae-hv-ves-collector
1271 dcae-ves-collector ClusterIP 10.43.83.158 <none> 8080/TCP,8443/TCP 12d app=dcae-ves-collector
1272 xdcae-hv-ves-collector NodePort 10.43.32.76 <none> 6061:30222/TCP 12d app=dcae-hv-ves-collector
1273 xdcae-ves-collector NodePort 10.43.97.42 <none> 8080:30235/TCP,8443:30417/TCP 12d app=dcae-ves-collector
1275 2. Use the port of xdcae-ves (30235 in this case) and the kubernetes-host IP
1277 - Log in to the vfw sinc VNF as user ubuntu
1278 - Modify /opt/config/dcae_collector_ip.txt and /opt/config/dcae_collector_port.txt
1279 - Kill the vpp reporter if running already
1280 - Start the vpp reporter by executing the script
1282 - cd /opt/VES/evel/evel-library/code/VESreporting
1284 - Add the following route for the metadata service if not present already
1288 sudo ip route add 169.254.169.254 via <vfw_sinc OAM_NETWORK IP> dev <interface name>
1290 # sudo ip route add 169.254.169.254 via 10.10.10.11 dev eth3
1291 - Verify that the metadata service is accessible by issuing the following command
1295 curl http://169.254.169.254
1298 1. The events generated from this program will trigger the vFW CL flow.
1299 In a successful deployment of the vFW CL, the graphs look as in the screenshot below.
1300 We can see that the bars are shorter and more uniform as compared to vFW deployment without the CL
1302 Browse to the zdfw1fwl01snk01 on port 667 to see a graph representing the traffic being received
1306 http://<zdfw1fwl01snk01>:667/
1310 4. Check the events sent by TCA on unauthenticated.DCAE_CL_OUTPUT
1312 These events are the resulting of the TCA application, e.g. TCA has noticed an event was crossing
1313 a given threshold, hence is sending a message of that particular topic. Then Policy will grab this event
1314 and perform the appropriate action, as defined in the Policy. In the case of vFWCL, Policy will send
1315 an event on the APPC_CL topic, that APPC will consume. This will trigger a NETCONF request to the
1316 packet generator to adjust the traffic.
1321 http://<kubernetes-host>:3904/events/unauthenticated.DCAE_CL_OUTPUT/group1/C1 \
1322 -H 'Accept: application/json' \
1323 -H 'Content-Type: application/cambria'
1325 #smaple command and output:
1326 curl -X GET http://10.43.214.215:3904/events/unauthenticated.DCAE_CL_OUTPUT/group1/C1 -H 'Accept: application/json' -H 'Content-Type: application/cambria' | jq
1327 % Total % Received % Xferd Average Speed Time Time Time Current
1328 Dload Upload Total Spent Left Speed
1329 100 909 100 909 0 0 677 0 0:00:01 0:00:01 --:--:-- 677
1331 "{\"closedLoopEventClient\":\"DCAE_INSTANCE_ID.dcae-tca\",\"policyVersion\":\"v0.0.1\",\"policyName\":\"DCAE.Config_tca-hi-lo\",\"policyScope\":\"DCAE\",\"target_type\":\"VM\",\"AAI\":{\"vserver.prov-status\":\"ACTIVE\",\"vserver.resource-version\":\"1617776112073\",\"vserver.is-closed-loop-disabled\":false,\"vserver.vserver-name2\":\"vfw_sinc_vsp_002-1\",\"vserver.vserver-id\":\"30dd6250-8a74-4ed7-9729-6ce7190c6661\",\"vserver.vserver-selflink\":\"http://10.200.142.157:8774/v2.1/servers/30dd6250-8a74-4ed7-9729-6ce7190c6661\",\"vserver.in-maint\":false,\"vserver.vserver-name\":\"vfw_sinc_vsp_002-1\"},\"closedLoopAlarmStart\":1500584201765465,\"closedLoopEventStatus\":\"ONSET\",\"closedLoopControlName\":\"ControlLoop-vFirewall-d0a1dfc6-94f5-4fd4-a5b5-4630b438850a\",\"version\":\"1.0.2\",\"target\":\"vserver.vserver-name\",\"requestID\":\"2f546551-f304-4e76-9e8e-45c601790823\",\"from\":\"DCAE\"}"
1334 5. Check the active streams value in vPG over restconf
1336 The number of streams will change along the time, this is the result of close-loop policy.
1337 When the traffic goes over a certain threshold, DCAE will publish an event on the unauthenticated.DCAE_CL_OUTPUT
1338 topic that will be picked up by APPC, that will send a NETCONF request to the packet generator to adjust the traffic it's sending.
1340 Run the below command to check the stream count, you should see the value as 5
1344 curl -v --noproxy '*' --user "admin":"Kp8bJ4SXszM0WXlhak3eHlcse2gAw84vaoGGmJvUy2U" -H "Accept: application/xml" -H "Content-type: application/xml" -X GET http:/<kubernetes-host>:30230/restconf/config/network-topology:network-topology/topology/topology-netconf/node/<VPG VNFID>/yang-ext:mount/stream-count:stream-count/streams/
1346 #sample command and output
1347 curl -v --noproxy '*' --user "admin":"Kp8bJ4SXszM0WXlhak3eHlcse2gAw84vaoGGmJvUy2U" -H "Accept: application/xml" -H "Content-type: application/xml" -X GET http:/192.168.122.99:30230/restconf/config/network-topology:network-topology/topology/topology-netconf/node/a1ca05b4-3231-4e4a-a09c-74f2292fe577/yang-ext:mount/stream-count:stream-count/streams/
1348 Note: Unnecessary use of -X or --request, GET is already inferred.
1349 * Unwillingly accepted illegal URL using 1 slash!
1350 * Trying 192.168.122.99...
1352 * Connected to 192.168.122.99 (192.168.122.99) port 30230 (#0)
1353 * Server auth using Basic with user 'admin'
1354 > GET /restconf/config/network-topology:network-topology/topology/topology-netconf/node/a1ca05b4-3231-4e4a-a09c-74f2292fe577/yang-ext:mount/stream-count:stream- count/streams/ HTTP/1.1
1355 > Host: 192.168.122.99:30230
1356 > Authorization: Basic YWRtaW46S3A4Yko0U1hzek0wV1hsaGFrM2VIbGNzZTJnQXc4NHZhb0dHbUp2VXkyVQ==
1357 > User-Agent: curl/7.58.0
1358 > Accept: application/xml
1359 > Content-type: application/xml
1362 < Content-Type: application/xml
1363 < Content-Length: 110
1365 * Connection #0 to host 192.168.122.99 left intact
1366 <streams xmlns="urn:opendaylight:params:xml:ns:yang:stream-count"><active-streams>5</active-streams></streams>
1369 .. |image16| image:: media/image16.png
1370 .. |image15| image:: media/image15.png
1371 .. |image5| image:: media/image5.png
1372 .. |image13| image:: media/image13.png
1373 .. |image1| image:: media/image1.png
1374 .. |image12| image:: media/image12.png
1375 .. |image14| image:: media/image14.png
1376 .. |image19| image:: media/image19.png
1377 .. |image7| image:: media/image7.png
1378 .. |image10| image:: media/image10.png
1379 .. |image4| image:: media/image4.png
1380 .. |image20| image:: media/image20.png
1381 .. |image9| image:: media/image9.png
1382 .. |image3| image:: media/image3.png
1383 .. |image17| image:: media/image17.png
1384 .. |image11| image:: media/image11.png
1385 .. |image24| image:: media/image24.png
1386 .. |image22| image:: media/image22.png
1387 .. |image18| image:: media/image18.png
1388 .. |image23| image:: media/image23.png
1389 .. |image2| image:: media/image2.png
1390 .. |image8| image:: media/image8.png
1391 .. |image21| image:: media/image21.png
1392 .. |image25| image:: media/image25.png
1393 .. |image53| image:: media/image53.jpg
1394 .. |image54| image:: media/image54.png