Hi,   I am trying to instantiate CSR VNF from NFVO service package, the instance is getting created and is in Running state on Openstack with 1 IP address allocated to it, the port is also UP. However, on ESC the deployment is in Error state. The logs don't show anything other than this warning message:  2020-02-11 18:06:38.681 WARN    Type: VM_NETWORK_STATE 2020-02-11 18:06:38.681 WARN    Status: FAILURE 2020-02-11 18:06:38.681 WARN    Status Code: 500 2020-02-11 18:06:38.681 WARN    Status Msg: Warning: VM [austx-lab-dev-es_CSR-2-_0_abcaf96b-45bf-4820-9b2b-37973f59292e] has a network problem: Gateway with ip 98.6.63.65is down. 2020-02-11 18:06:38.681 WARN    Tenant: admin     On Openstack, when I checked the instance, I see the day 0 config has also not got pushed.  Even after I push the configs manually, I am not able to reach the VM from outside (98.6.63.73), even though I can ping the gateway (98.6.63.65) from outside (like ESC and NSO machines).   This is the config I am pushing: hostname CSRhost ! platform console serial ! ip domain name cisco.com ! username admin privilege 15 password 0 admin ! enable secret cisco123 ! vrf definition Mgmt address-family ipv4 exit-address-family ! interface GigabitEthernet1 description management network vrf forwarding Mgmt ip address 98.6.63.73 255.255.255.240 ip access-group MGMT-IN in no shut ! crypto key generate rsa modulus 1024 ip tftp source-interface GigabitEthernet1 ip ssh source-interface GigabitEthernet1 ip ssh version 2 no ip ssh stricthostkeycheck ip ssh authentication-retries 5 ip scp server enable ip route vrf Mgmt 0.0.0.0 0.0.0.0 98.6.63.65 file prompt quiet ! snmp-server community public RO ! ip access-list extended PUBLIC-IN permit tcp any eq 443 any established permit udp any eq domain any ! !####_DAY0_LICENSE ! license smart enable ! do write   How do I debug this further? any inputs from CSR/ openstack or ESC experts?   Thanks, Neetika ... View more

Hi,   I am trying to instantiate CSR VNF from NFVO service package, the instance is getting created and is in Running state on Openstack with 1 IP address allocated to it, the port is also UP. However, on ESC the deployment is in Error state. The logs don't show anything other than this warning message:  2020-02-11 18:06:38.681 WARN   Type: VM_NETWORK_STATE 2020-02-11 18:06:38.681 WARN   Status: FAILURE 2020-02-11 18:06:38.681 WARN   Status Code: 500 2020-02-11 18:06:38.681 WARN   Status Msg: Warning: VM [austx-lab-dev-es_CSR-2-_0_abcaf96b-45bf-4820-9b2b-37973f59292e] has a network problem: Gateway with ip 98.6.63.65is down. 2020-02-11 18:06:38.681 WARN   Tenant: admin     On Openstack, when I checked the instance, I see the day 0 config has also not got pushed.  Even after I push the configs manually, I am not able to reach the VM from outside (98.6.63.73), even though I can ping the gateway (98.6.63.65) from outside (like ESC and NSO machines).   This is the config I am pushing: hostname CSRhost ! platform console serial ! ip domain name cisco.com ! username admin privilege 15 password 0 admin ! enable secret cisco123 ! vrf definition Mgmt address-family ipv4 exit-address-family ! interface GigabitEthernet1 description management network vrf forwarding Mgmt ip address 98.6.63.73 255.255.255.240 ip access-group MGMT-IN in no shut ! crypto key generate rsa modulus 1024 ip tftp source-interface GigabitEthernet1 ip ssh source-interface GigabitEthernet1 ip ssh version 2 no ip ssh stricthostkeycheck ip ssh authentication-retries 5 ip scp server enable ip route vrf Mgmt 0.0.0.0 0.0.0.0 98.6.63.65 file prompt quiet ! snmp-server community public RO ! ip access-list extended PUBLIC-IN permit tcp any eq 443 any established permit udp any eq domain any ! !####_DAY0_LICENSE ! license smart enable ! do write   How do I debug this further? any inputs from CSR/ openstack or ESC experts?   Thanks, Neetika   ... View more

Hello!!   I am trying to remove some service instances that I created using NFVO FP. Basically when I created the CSR provisioning service instance, the ESC deployment failed. So I deleted the NSO service instance, expecting that it would remove the service as well as ESC failed deployment, but after deleting I noticed it has left a zombie service show below.   I don't see any vnf-info in NSO for this service, not sure why this is leftover? How do I cleanup these zombie services?   Also what is the right process to remove vnf service on nso without creating any zombie? any actions or delete service package available?       zombies service /nfv/cisco-nfvo:vnf-info[name='CSR-VM-22']   delete-path /nfv/cisco-nfvo:vnf-info[name='CSR-VM-22']                                                                                                   POST                                                          BACK                                         ACTION   TYPE         NAME                                     TRACK   GOAL   STATE   STATUS       WHEN   ref   STATUS   ---------------------------------------------------------------------------------------------------------- self         self                                     false   -     init     reached       -     -     -                                                                           ready   not-reached   -     -     -         deployment   austx-lab-dev-esc-01-vnf-info-CSR-VM-22   false   -     init     reached       -     -     -                                                                           create   reached       -     -     -                                                                           ready   not-reached   -     -     -           ... View more

Hi folks,   I am curious to understand that when I see configuration of a device that is set by some NSO service in xml format, I see the refcount and backpointers by default in the output of "show running-config" or show full-configuration, I was thinking if I use " hide service-meta-data" this should help me to hide the refcounts and back pointers but it doesn't! any one has any clue how to do hide these refcounts:   admin@ncs# show running-config devices device IOS2 config ios:ip | hide service-meta-data | display xml <config xmlns="http://tail-f.com/ns/config/1.0">   <devices xmlns="http://tail-f.com/ns/ncs">   <device>     <name>IOS2</name>       <config>       <ip xmlns="urn:ios">         <source-route>true</source-route>         <gratuitous-arps-conf>           <gratuitous-arps>false</gratuitous-arps>         </gratuitous-arps-conf>         <finger>         </finger>         <http>           <server>false</server>           <secure-server>false</secure-server>         </http>         <route>           <ip-route-forwarding-list refcounter="1"   backpointer="[ /charter:charter/charter:rfs/rfs-ip:rfs-ip[rfs-ip:device='IOS2'] ]" >             <prefix>192.168.71.25</prefix>             <mask>255.255.255.252</mask>             <forwarding-address>192.168.71.18</forwarding-address>           </ip-route-forwarding-list>         </route>       </ip>       </config>   </device>   </devices> </config> admin@ncs#   ... View more

Hello   I have an ADVA device for which the NETCONF ned is created using Pioneer package. When I try device sync-from on NSO, I am getting this error: admin@ncs(config)# devices device AUSDTXIRDAW sync-from result false info RPC error towards AUSDTXIRDAW: operation_not_supported: Request could not be completed because those datastores cannot be operated at the same time.   I am not sure if the device capabilities has to do something with it, but if I check the device capabilities it shows these: admin@ncs(config)# devices device AUSDTXIRDAW capability               Possible completions:   :candidate:1.0                                                                                           :rollback-on-error:1.0                                                                                   :validate:1.0                                                                                             :validate:1.1                                                                                             :writable-running:1.0                                                                                     http://metroethernetforum.org/ns/yang/mef-cfm                                                             http://metroethernetforum.org/ns/yang/mef-soam-fm                                                         http://metroethernetforum.org/ns/yang/mef-soam-pm      ............     Does anyone know how can I resolve this?   Thanks, Neetika ... View more