Closed gaurav1510 closed 6 years ago
@gaurav1510 It looks like there is a communication issue between your Open Baton box and your generated VM. You might first check to make sure that you can reach the Open Baton ip address from your VM by executing
ping 192.168.136.84
on your VM. If that succeeds make sure that any security rules/firewall rules are opened on your Open Baton box to allow ingress on port 5672.
Yes sir, The IP address and even the port is reachable from the VM. However, nmap to the IP 192.168.136.84 does not return 5672 port.
And also I have enabled all the security rules -
Thanks for your previous reply.
On your Open Baton box can you see if port 5672 is open? On ubuntu the command is
netstat -an | grep 5672
tcp6 0 0 :::5672 :::* LISTEN
is the output
yes sir
You have unfortunately exhausted my knowledge of how to fix this issue but the problem is that the VM cannot connect to the Open Baton box on port 5672. You might want to get in touch with someone more familiar with your network and see if they can help you debug the issue.
The fix to this problem is that timeout value was less for ems in generic-vnfm. To change this update vnfm.ems.start.timeout in application.properties for generic-vnfm.
Closed due to inactivity
Hi sir, I am using NFVO 3.0 and appropriate corresponding generic-VNFM. While I spawn new VNFs using openbaton GUI, each NS Descriptor completes it's ALLOCATE and GRANT phase. However, then I get an error - no ems for hostame ..... Since VNF has completed its GRANT and ALLOCATE phase, VM is created and I can login it too. And logs (/var/log/openbaton/ems-receiver.log) say that - _INFO:main:EMS configuration paramters are hostname: client-565, username: admin, password: *****, autodel: true, heartbeat: 120, exchange name: openbaton-exchange INFO:pika.adapters.base_connection:Connecting to 192.168.136.84:5672 ERROR:pika.adapters.baseconnection:Connection to 192.168.136.84:5672 failed: timeout WARNING:pika.connection:Could not connect, 0 attempts left