Ask Your Question

Monitoring of VNF is not working

asked 2020-05-22 08:05:11 -0500

Anshul Sehgal gravatar image


I have tacker stable/pike setup through kolla-ansible. Openstack VIM is registered and REACHABLE. Able to deploy/terminate VNF from tacker.

When applying monitoring policy, it is not working. I see icmp packet from tacker server to VIM server, for VIM status monitoring, but same is not there for VNF.

Below is the section having monitoring policy.


    image: CentOS-7
    name: Self_Healing
    flavor: Tacker_Flavor
    availability_zone: nova
    mgmt_driver: noop
      name: ping
        monitoring_delay: 20
        count: 3
        interval: 0.2
        timeout: 2
        retry: 6
        failure: respawn

Even if I shut down the instance manually in VIM, vnf manager shows instance as ACTIVE. No trace of same in tacker-server, tacker-conductor, mistral logs.

In deployed vnf event tab, last event is with Resource state "Active", Event type "Monitor" with monitoring details. No workflow created to monitor VNF.

Running Container Services are:

tacker_server, tacker_conductor, barbican_worker, barbican_keystone_listener, barbican_api, mistral_executor, mistral_engine, mistral_api, horizon, keystone, rabbitmq, mariadb, cron, kolla_toolbox, fluentd and memcached.

Kindly suggest what should be checked.

edit retag flag offensive close merge delete

1 answer

Sort by ยป oldest newest most voted

answered 2020-08-02 00:18:16 -0500

Magot gravatar image

I got same setup, same issue

edit flag offensive delete link more


I have checked that if we restart the tacker-server container(docker restart tacker_server), then ping monitor starts working.

And in same way if I terminate the VNF, to stop the monitoring, again have to restart the container.

Anshul Sehgal gravatar imageAnshul Sehgal ( 2020-08-20 10:01:39 -0500 )edit

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower


Asked: 2020-05-22 08:05:11 -0500

Seen: 60 times

Last updated: May 22 '20