New Question
0

VM unable to connect to virtual switch : vif_type: binding_failed

asked 2015-08-27 15:41:58 +0300

Rochdi gravatar image

updated 2015-08-27 15:45:26 +0300

Hi again, I followed the tutorial of neutron-hyperv-Agent until the end and after the creation of the new VM, it was successfully created and the hyper-v manager shows me the VM which was created through by Openstack. However, When I'd like to check for the vNIC of the VM, I found it not connected. After that, I followed the troubleshooting and I reached until neutron port-show $PORT_ID then I got :

+-----------------------+--------------------------------------------------------------
| Field                 | Value                                              |
+-----------------------+---------------------------------------------------------------------------------+
| admin_state_up        | True                                |
| allowed_address_pairs |                                                                     |
| binding:host_id       | WIN-C6EIDJEP5J0                                                |
| binding:profile       | {}                                                                  |
| binding:vif_details   | {}                                                                  |
| binding:vif_type      | binding_failel                                                      |
| binding:vnic_type     | normal                                                              |
| device_id             | 94690504-ca00-4f72-86f7-9f8c8833e9af                           |
| device_owner          | compute:nova                                                        |
| extra_dhcp_opts       |                                                                     |
| fixed_ips             | {"subnet_id": "a4895d36-28b8-447b-b551-f84796ffe5a1", "ip_address": "10.0.1.2"} |
| id                    | 0cf3d49f-fa77-4249-ad2c-59a237e22b47                                |
| mac_address           | fa:16:3e:4f:a3:f0                                                   |
| name                  |                                                                     |
| network_id            | 37dd11a3-07ce-4411-b290-b85bde4b2bb9                                |
| security_groups       | 120a3bde-efd3-4fb1-8416-a07ec83b0438                                |
| status                | DOWN                                                                |
| tenant_id             | 0335a8743dcc44aeaa8fecaae079f969                                   |
+-----------------------+---------------------------------------------------------------------------------+

for the neutron agent-list , I got:

+--------------------------------------+--------------------+-----------------+-------+----------------+---------------------------+
| id                                   | agent_type         | host            | alive | admin_state_up | binary                    |
+--------------------------------------+--------------------+-----------------+-------+----------------+---------------------------+
| 12623ad9-61a3-4707-abc9-04fbbc6c3ee9 | Metadata agent     | network         | :-)   | True           | neutron-metadata-agent    |
| 24666abb-0fa7-4b5a-92b1-aef5c128356a | HyperV agent       | WIN-C6EIDJEP5J0 | :-)   | True           | neutron-hyperv-agent      |
| 47599326-636e-46ae-98c1-96ac5ce5d63d | DHCP agent         | network         | :-)   | True           | neutron-dhcp-agent        |
| bb8a28a6-9ce3-432d-bef9-e9c6b799a35a | Open vSwitch agent | network         | :-)   | True           | neutron-openvswitch-agent |
| d3a805ad-16ee-4541-9629-4567d1ddedd2 | L3 agent           | network         | :-)   | True           | neutron-l3-agent          |
+--------------------------------------+--------------------+-----------------+-------+----------------+---------------------------+

for the following command line neutron subnet-show a4895d36-28b8-447b-b551-f84796ffe5a1, I got:

+-------------------+--------------------------------------------+
| Field             | Value                                      |
+-------------------+--------------------------------------------+
| allocation_pools  | {"start": "10.0.1.2", "end": "10.0.1.254"} |
| cidr              | 10.0.1.0/24                                |
| dns_nameservers   |                                            |
| enable_dhcp       | True                                       |
| gateway_ip        | 10.0.1.1                                   |
| host_routes       |                                            |
| id                | a4895d36-28b8-447b-b551-f84796ffe5a1       |
| ip_version        | 4                                          |
| ipv6_address_mode |                                            |
| ipv6_ra_mode      |                                            |
| name              |                                            |
| network_id        | 37dd11a3-07ce-4411-b290-b85bde4b2bb9       |
| tenant_id         | 0335a8743dcc44aeaa8fecaae079f969           |
+-------------------+--------------------------------------------+

for the following command line Get-VMNetworkAdapter -VMNetworkAdapterName $PORT_ID -All I got:

PS C:\Users\Administrator> Get-VMNetworkAdapter -VMNetworkAdapterName $PORT_ID -All

Name                                 IsManagementOs VMName            SwitchName MacAddress   Status IPAddresses
----                                 -------------- ------            ---------- ----------   ------ -----------
external                             True                             external   F8B156C7662A {Ok}
0cf3d49f-fa77-4249-ad2c-59a237e22b47 False          instance-00000009            FA163E4FA3F0        {}
6f396fe0-b475-4a9c-b632-550cbc50a159 False          instance-00000009            FA163E65D06D        {}

thank you for helping me and if you would like another file I will be in your service.

edit retag flag offensive close merge delete

1 answer

Sort by » oldest newest most voted
1

answered 2015-08-27 18:46:57 +0300

ader1990 gravatar image

updated 2015-08-27 19:59:21 +0300

Hello,

I see in your neutron-hyperv-agent log an error: "Endpoint does not support RPC method tunnel_update". In case your neutron networks are gre/vxlan, Neutron hyperv agent does not support tunneling. You can only use flat/vlan network types. More details here: http://www.cloudbase.it/quantum-hyper...

If you need tunneling options, here is the information you need: http://www.cloudbase.it/open-vswitch-... .

Thanks.

edit flag offensive delete link more

Comments

thank you for your reply . i found another problem while installing openvswitch installer which is : 'netcfg failed to install open vswitch hyperv switch extension'

Rochdi gravatar imageRochdi ( 2015-08-28 20:25:03 +0300 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

1 follower

Stats

Asked: 2015-08-27 15:41:58 +0300

Seen: 1,441 times

Last updated: Aug 27 '15