Instances on Mitaka getting Request TIme out quite frequently

asked 2016-10-23 21:13:26 -0500

linuxtechi gravatar image

Hello Folks ,

I have recently deploy multi node openstack mikata for the internal use. I am getting Request time out and some times Destination host unreachable while pinging and accessing the instances.

Reply from  x.x.x.x: bytes=32 time=490ms TTL=52
Reply from  x.x.x.x: bytes=32 time=478ms TTL=52
Reply from  x.x.x.x: bytes=32 time=477ms TTL=52
Reply from  x.x.x.x: bytes=32 time=482ms TTL=52
Request timed out.
Request timed out.
Reply from  x.x.x.x: Destination host unreachable.
Reply from  x.x.x.x: Destination host unreachable.
Reply from  x.x.x.x: Destination host unreachable.
Reply from  x.x.x.x: bytes=32 time=483ms TTL=52
Reply from  x.x.x.x: bytes=32 time=481ms TTL=52
Reply from  x.x.x.x: bytes=32 time=485ms TTL=52

Any idea how to resolve this issue, i have already double check my network settings on my physical host as well. Below is the details of my Setup :

Controller Node - Three bond interface , one for mgmt (management VLAN IP is assigned to it and used for all api communication) , VMdata (VM data Vlan ip is assigned and used for Tunneling) and dmz ( external ip is assigned to this interface for accessing the server from outside )

Compute Node ( Same Networking like Controller node)

Network Node (Same Networking like Controller node, the only difference is that i have added dmz bond in br-ex bridge as port and assign the ip of dmz to br-ex interface )

Thanks in advance.

edit retag flag offensive close merge delete