Re: [Openstack] veth pair disappear after hardware reboot
Varun, Not exactly documenting that “veth” is not saved on system reboot but this blog post may be useful for you: https://fosskb.wordpress.com/2014/06/10/managing-openstack-internaldataexternal-network-in-one-interface/ anthony. From: varun bhatnagar [mailto:varun292...@gmail.com] Sent: Monday, August 31, 2015 12:06 AM To: Mike Spreitzer Cc: openstack@lists.openstack.org Subject: Re: [Openstack] veth pair disappear after hardware reboot Hello Mike, Thanks a lot for replying. No, I am not aware about veths not surviving a reboot. Is it mentioned in any document of OpenStack? I have checked the Neutron services and they are absolutely fine after reboot. This problem is seen even when I kill/stop the network services and again try to start them. Could you please tell me if there is any fix for this? BR, Varun On Aug 31, 2015 4:46 AM, "Mike Spreitzer" mailto:mspre...@us.ibm.com>> wrote: You know that veths do not survive reboot, right? It is up to Neutron or whatever needs them to create them after each boot. Have you checked that all the right Neutron services came up and are healthy after your reboot? ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Re: [Openstack] veth pair disappear after hardware reboot
Hello Mike, Thanks a lot for replying. No, I am not aware about veths not surviving a reboot. Is it mentioned in any document of OpenStack? I have checked the Neutron services and they are absolutely fine after reboot. This problem is seen even when I kill/stop the network services and again try to start them. Could you please tell me if there is any fix for this? BR, Varun On Aug 31, 2015 4:46 AM, "Mike Spreitzer" wrote: > You know that veths do not survive reboot, right? It is up to Neutron or > whatever needs them to create them after each boot. Have you checked that > all the right Neutron services came up and are healthy after your reboot? > > ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Re: [Openstack] veth pair disappear after hardware reboot
You know that veths do not survive reboot, right? It is up to Neutron or whatever needs them to create them after each boot. Have you checked that all the right Neutron services came up and are healthy after your reboot? ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Re: [Openstack] veth pair disappear after hardware reboot
Hi, Can anyone please reply? Still struggling with the same problem. BR, Varun On Thu, Aug 27, 2015 at 3:03 PM, varun bhatnagar wrote: > Hi, > > I have OpenStack Juno installed on a multi-node step up. I have a cluster > running on that. In that cluster there are few VMs which are booting over > network from one of the VM. This works fine until I reboot my hardware. > > As soon as the blades are rebooted I start my VMs, then, PXE boot doesn't > work. I did ovs-vsctl show before and after reboot and I can see a > difference in ports attached to the bridge (logs attached). The *veth* > pairs (qvoXXX) are getting disappeared after reboot. > > Can anyone please suggest what could be done to avoid this? > > > BR, > Varun > ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
[Openstack] veth pair disappear after hardware reboot
Hi,
I have OpenStack Juno installed on a multi-node step up. I have a cluster
running on that. In that cluster there are few VMs which are booting over
network from one of the VM. This works fine until I reboot my hardware.
As soon as the blades are rebooted I start my VMs, then, PXE boot doesn't
work. I did ovs-vsctl show before and after reboot and I can see a
difference in ports attached to the bridge (logs attached). The *veth*
pairs (qvoXXX) are getting disappeared after reboot.
Can anyone please suggest what could be done to avoid this?
BR,
Varun
[root@compute0-5 ~]# ovs-vsctl show
dc6db4b2-922e-4a9c-8614-0c6ee82e812b
Bridge "tbr974f0285-eb"
Port "tbr974f0285-eb"
Interface "tbr974f0285-eb"
type: internal
Port "pvm974f0285-eb"
Interface "pvm974f0285-eb"
type: patch
options: {peer="pin974f0285-eb"}
Bridge "br-eth5"
Port "phy-br-eth5"
Interface "phy-br-eth5"
type: patch
options:
{peer="int-br-eth5"}
Port "br-eth5"
Interface "br-eth5"
type: internal
Port "enp1s0f0"
Interface "enp1s0f0"
Bridge "tbr1d212424-7f"
Port "pvm1d212424-7f"
Interface "pvm1d212424-7f"
type: patch
options:
{peer="pin1d212424-7f"}
Port "tbr1d212424-7f"
Interface "tbr1d212424-7f"
type: internal
Port "qvo1d212424-7f"
Interface "qvo1d212424-7f"
Bridge br-int
fail_mode: secure
Port br-int
Interface br-int
type: internal
Port "pin974f0285-eb"
Interface "pin974f0285-eb"
type: patch
options:
{peer="pvm974f0285-eb"}
Port "pin1d212424-7f"
Interface "pin1d212424-7f"
type: patch
options:
{peer="pvm1d212424-7f"}
Port "int-br-eth5"
Interface "int-br-eth5"
type: patch
options:
{peer="phy-br-eth5"}
ovs_version: "2.1.3"
[root@compute0-5 ~]# [root@compute0-5 ~]# ovs-vsctl show
dc6db4b2-922e-4a9c-8614-0c6ee82e812b
Bridge "tbr974f0285-eb"
Port "tbr974f0285-eb"
Interface "tbr974f0285-eb"
type: internal
Port "pvm974f0285-eb"
Interface "pvm974f0285-eb"
type: patch
options:
{peer="pin974f0285-eb"}
Bridge br-int
fail_mode: secure
Port "qvo08561197-c3"
tag: 82
Interface "qvo08561197-c3"
Port br-int
Interface br-int
type: internal
Port "qvoeaa9306e-df"
tag: 73
Interface "qvoeaa9306e-df"
Port "pin974f0285-eb"
Interface "pin974f0285-eb"
type: patch
options: {peer="pvm974f0285-eb"}
Port "int-br-eth5"
Interface "int-br-eth5"
type: patch
options: {peer="phy-br-eth5"}
Port "pin1d212424-7f"
Interface "pin1d212424-7f"
type: patch
options: {peer="pvm1d212424-7f"}
Bridge "tbr1d212424-7f"
Port "pvm1d212424-7f"
Interface "pvm1d212424-7f"
type: patch
options: {peer="pin1d212424-7f"}
Port "tbr1d212424-7f"
Interface "tbr1d212424-7f"
type: internal
Port "qvo1d212424-7f"
Interface "qvo1d212424-7f"
Bridge "br-eth5"
Port "br-eth5"
Interface "br-eth5"
type: internal
Port "enp1s0f0"
Interface "enp1s0f0"
Port "phy-br-eth5"
Interface "phy-br-eth5"
type: patch
options: {peer="int-br-eth5"}
ovs_version: "2.1.3"
[root@compute0-5 ~]# ___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
