Revision history [back]

click to hide/show revision 1
initial version

neutron(havana) with floodlight can't ping vm

Hi Folks,

I am facing some problems about configuring neutron with bigswitch-plugin for floodlight controller(no devstack). I can use "neutron net-create xxx" to create network correctly. And I can also use "nova boot xx" to boot a virtual machine. The status of vm is active and the ip address is also correct.

Then, I configure ip address for br-int to ping vm. But, the ping is failed.

The following operations were used.

~# nova secgroup-list-rules default

+-------------+-----------+---------+-----------+--------------+

| IP Protocol | From Port | To Port | IP Range | Source Group |

+-------------+-----------+---------+-----------+--------------+

| tcp | 22 | 22 | 0.0.0.0/0 | |

| icmp | -1 | -1 | 0.0.0.0/0 | |

+-------------+-----------+---------+-----------+--------------+

~# neutron net-create vn1

Created a new network:

+----------------+--------------------------------------+

| Field | Value |

+----------------+--------------------------------------+

| admin_state_up | True |

| id | 8f4eb550-e221-4f28-ab01-df73fe9082e6 |

| name | vn1 |

| shared | False |

| status | ACTIVE |

| subnets | |

| tenant_id | 2c66a95435d149f899146c7564a53ead |

+----------------+--------------------------------------+

~# neutron subnet-create vn1 9.0.0.0/24

Created a new subnet:

+------------------+------------------------------------------+

| Field | Value |

+------------------+------------------------------------------+

| allocation_pools | {"start": "9.0.0.2", "end": "9.0.0.254"} |

| cidr | 9.0.0.0/24 |

| dns_nameservers | |

| enable_dhcp | True |

| gateway_ip | 9.0.0.1 |

| host_routes | |

| id | 3c59e7c3-2b39-4dc0-8d5b-2998243a09b7 |

| ip_version | 4 |

| name | |

| network_id | 8f4eb550-e221-4f28-ab01-df73fe9082e6 |

| tenant_id | 2c66a95435d149f899146c7564a53ead |

+------------------+------------------------------------------+

When I create the subnet, I find following error on floodlight controller.

21:10:45.778 WARN [n.f.v.NetworkResource:Dispatcher: Thread-20] Unrecognized field subnets in parsing network definition

21:10:45.779 WARN [n.f.v.NetworkResource:Dispatcher: Thread-20] Unrecognized field [ in parsing network definition

21:10:45.780 WARN [n.f.v.NetworkResource:Dispatcher: Thread-20] Unrecognized field enable_dhcp in parsing network definition

21:10:45.781 WARN [n.f.v.NetworkResource:Dispatcher: Thread-20] Unrecognized field true in parsing network definition

21:10:45.781 WARN [n.f.v.NetworkResource:Dispatcher: Thread-20] Unrecognized field network_id in parsing network definition

21:10:45.782 WARN [n.f.v.NetworkResource:Dispatcher: Thread-20] Unrecognized field 8f4eb550-e221-4f28-ab01-df73fe9082e6 in parsing network definition

21:10:45.783 WARN [n.f.v.NetworkResource:Dispatcher: Thread-20] Unrecognized field tenant_id in parsing network definition

21:10:45.783 WARN [n.f.v.NetworkResource:Dispatcher: Thread-20] Unrecognized field 2c66a95435d149f899146c7564a53ead in parsing network definition

21:10:45.784 WARN [n.f.v.NetworkResource:Dispatcher: Thread-20] Unrecognized field dns_nameservers in parsing network definition

21:10:45.784 WARN [n.f.v.NetworkResource:Dispatcher: Thread-20] Unrecognized field [ in parsing network definition

21:10:45.785 WARN [n.f.v.NetworkResource:Dispatcher: Thread-20] Unrecognized field ] in parsing network definition

21:10:45.786 WARN [n.f.v.NetworkResource:Dispatcher: Thread-20] Unrecognized field state in parsing network definition

21:10:45.786 WARN [n.f.v.NetworkResource:Dispatcher: Thread-20] Unrecognized field UP in parsing network definition

21:10:45.787 WARN [n.f.v.NetworkResource:Dispatcher: Thread-20] Unrecognized field allocation_pools in parsing network definition

21:10:45.787 WARN [n.f.v.NetworkResource:Dispatcher: Thread-20] Unrecognized field [ in parsing network definition

21:10:45.788 WARN [n.f.v.NetworkResource:Dispatcher: Thread-20] Unrecognized field start in parsing network definition

21:10:45.789 WARN [n.f.v.NetworkResource:Dispatcher: Thread-20] Unrecognized field 9.0.0.2 in parsing network definition

21:10:45.789 WARN [n.f.v.NetworkResource:Dispatcher: Thread-20] Unrecognized field end in parsing network definition

21:10:45.790 WARN [n.f.v.NetworkResource:Dispatcher: Thread-20] Unrecognized field 9.0.0.254 in parsing network definition

21:10:45.791 ERROR [n.f.v.NetworkResource:Dispatcher: Thread-20] Could not parse JSON Expected FIELD_NAME

~# nova boot --flavor 6 --key_name mykey --security_group default --image c50a6f5e-449a-4781-9da6-bc57e9fef3e7 --nic net-id=8f4eb550-e221-4f28-ab01-df73fe9082e6 cirros_vm1

+--------------------------------------+------------+--------+------------+-------------+-------------+

| ID | Name | Status | Task State | Power State | Networks |

+--------------------------------------+------------+--------+------------+-------------+-------------+

| 2d9d4181-8e1a-4701-b1ec-158826a0c8b6 | cirros_vm1 | ACTIVE | None | Running | vn1=9.0.0.3 |

+--------------------------------------+------------+--------+------------+-------------+-------------+

~# curl -X GET http://192.168.243.10:8080/networkService/v1.1/tenants/123456/networks

[{"name":"","guid":"8f4eb550-e221-4f28-ab01-df73fe9082e6","gateway":null,"portMac":[{"port":"50470c20-ceef-455f-a2d5-bbe42ae6e71c","mac":"FA:16:3E:C1:6B:72"},{"port":"94c9a068-ff4a-4ad6-9f18-667d7b7ee725","mac":"FA:16:3E:4E:E9:57"}]}]

Then, I use following commands to configure br-int:

~# ip addr flush eth2

~# ip addr add 9.0.0.201/24 dev br-int

~# ping 9.0.0.3

The ping is failed.

Then, I use "ovs-ofctl dump-flows br-int" to checkout flows.

~# ovs-ofctl dump-flows br-int

NXST_FLOW reply (xid=0x4):

There is nothing in flow table. Can anyone help me?