Ask Your Question
1

neutron(havana) with floodlight can't ping vm

asked 2014-04-14 09:04:18 -0600

zuocheng gravatar image

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 ... (more)

edit retag flag offensive close merge delete

1 answer

Sort by ยป oldest newest most voted
1

answered 2014-04-14 14:58:38 -0600

SGPJ gravatar image

Please check the following: * Proper Security Group rules been added for ICMP both ingress & egress (as in your case it is fine), * Run floodlight application with learning switch module not forwarding module in neutron properties file an restart neutron server.

Then try to ping VM.

edit flag offensive delete link more

Comments

Thank you.

I use "net.floodlightcontroller.learningswitch.LearningSwitch" to replace "net.floodlightcontroller.forwarding.Forwarding" in neutron.properties file.

But, the ping is still failed.

And I show the flows of br-int, there is still nothing.

I find out when floodlight controller starts , it clears the all flows on the ovs bridge.

Is the ping failed due to the empty flow table of the br-int?

zuocheng gravatar imagezuocheng ( 2014-04-15 10:18:13 -0600 )edit

can you debug using wireshark. are you using opensource or commercial version?

SGPJ gravatar imageSGPJ ( 2014-04-19 11:10:29 -0600 )edit

Thanks. I solve it, my dhcp agent is down all the time. After using /usr/bin/neutron-dhcp-agent to restart the dhcp agent, the system works.

zuocheng gravatar imagezuocheng ( 2014-05-04 03:38:34 -0600 )edit

Good that it works for you. Thanks.

SGPJ gravatar imageSGPJ ( 2014-06-18 01:23:57 -0600 )edit

Your Answer

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

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2014-04-14 09:04:18 -0600

Seen: 165 times

Last updated: Apr 14 '14