tap devices getting tagged to 4095
I have installed 2 node environment.
node 1- controller - nova-compute/
node 2 - compute node - nova-compute/
VMs launched on controller work fine. I am able to ping/ssh to them.
However, VMs launched on compute node cannot be pinged or sshed.
When i do, sudo ovs-vsctl show, I see that VMs (tap devices) on the compute node are all getting tag: 4095
Also, when look at the console log of the VMs, I see that
No lease, forking to background
starting DHCP forEthernet interface eth0 [ OK ]
cloud-setup: checking http:\/
wget: can't connect to remote host (169.254.169.254): Network is unreachable
cloud-setup: failed 1\/30: up 10.46. request failed
Any clue is appreciated.
Thanks,
vj
Question information
- Language:
- English Edit question
- Status:
- Answered
- For:
- neutron Edit question
- Assignee:
- No assignee Edit question
- Last query:
- Last reply:
Revision history for this message
|
#1 |
4095 is a special "dead" vlan for which all traffic is dropped. the
OVS quantum agent puts a linux device on this vlan if it does not find
a quantum port associated with the device, or if the port that is
found should not be forwarding traffic.
Its possible there's a problem with the communication channel between
the OVS agent on node 2 and the main quantum-server process on node 1.
Providing the logs for the agent on node 2 would probably help.
dan
On Thu, Aug 23, 2012 at 8:11 PM, Vijay
<email address hidden> wrote:
> New question #206661 on quantum:
> https:/
>
> I have installed 2 node environment.
> node 1- controller - nova-compute/
> node 2 - compute node - nova-compute/
>
> VMs launched on controller work fine. I am able to ping/ssh to them.
>
> However, VMs launched on compute node cannot be pinged or sshed.
>
> When i do, sudo ovs-vsctl show, I see that VMs (tap devices) on the compute node are all getting tag: 4095
>
> Also, when look at the console log of the VMs, I see that
>
> No lease, forking to background
> starting DHCP forEthernet interface eth0 [ OK ]
> cloud-setup: checking http:\/
> wget: can't connect to remote host (169.254.169.254): Network is unreachable
> cloud-setup: failed 1\/30: up 10.46. request failed
>
> Any clue is appreciated.
> Thanks,
> vj
>
>
> --
> You received this question notification because you are an answer
> contact for quantum.
--
~~~~~~~
Dan Wendlandt
Nicira, Inc: www.nicira.com
twitter: danwendlandt
~~~~~~~
Revision history for this message
|
#2 |
Thanks Dan for the reply!
Here is the log from ovs quantum agent on the second compute node:
DEBUG:root:## running command: sudo ovs-vsctl --timeout=2 list-ports br-int
DEBUG:root:## running command: sudo ovs-vsctl --timeout=2 get Interface eth2 external_ids
DEBUG:root:## running command: sudo ovs-vsctl --timeout=2 get Interface eth2 ofport
DEBUG:root:## running command: sudo ovs-vsctl --timeout=2 get Interface tap89afd232-ce external_ids
DEBUG:root:## running command: sudo ovs-vsctl --timeout=2 get Interface tap89afd232-ce ofport
DEBUG:root:## running command: sudo ovs-vsctl --timeout=2 get Interface tapeb806203-34 external_ids
DEBUG:root:## running command: sudo ovs-vsctl --timeout=2 get Interface tapeb806203-34 ofport
DEBUG:root:## running command: sudo ovs-vsctl --timeout=2 set Port tap89afd232-ce tag=4095
DEBUG:root:## running command: sudo ovs-ofctl add-flow br-int priority=
DEBUG:root:## running command: sudo ovs-vsctl --timeout=2 set Port tapeb806203-34 tag=4095
DEBUG:root:## running command: sudo ovs-ofctl add-flow br-int priority=
ovs-ofctl: -1: value too large for 2-byte field in_port
Here is the nova-compute log:
2012-08-23 20:15:57 DEBUG nova.compute.
u'5dc620b6-
2012-08-23 20:15:57 DEBUG nova.virt.
2012-08-23 20:15:57 DEBUG nova.utils [req-93bac5d9-
2012-08-23 20:15:57 DEBUG nova.utils [req-93bac5d9-
2012-08-23 20:15:57 DEBUG nova.utils [req-93bac5d9-
2012-08-23 20:15:57 DEBUG nova.utils [req-93bac5d9-
2012-08-23 20:15:57 DEBUG nova.utils [req-93bac5d9-
2012-08-23 20:15:57 DEBUG nova.virt.
2012-08-23 20:15:57 DEBUG nova.virt.
2012-08-23 20:15:57 DEBUG nova.virt.
2012-08-23 20:15:57 INFO nova.virt.
2012-08-23 20:15:57 INFO nova.virt.
2012-08-23 20:15:58 DEBUG nova.virt.firewall [req-93bac5d9-
2012-08-23 20:15:58 INFO nova.virt.firewall [req-93bac5d9-
2012-08-23 20:15:58 INFO nova.virt.firewall [req-93bac5d9-
2012-08-23 20:15:58 DEBUG nova.virt.firewall [req-93bac5d9-
2012-08-23 20:15:58 INFO nova.virt.firewall [req-93bac5d9-
2012-08-23 20:15:58 INFO nova.virt.firewall [req-93bac5d9-
2012-08-23 20:15:58 DEBUG nova.virt.firewall [req-93bac5d9-
2012-08-23 20:15:58 DEBUG nova.utils [req-93bac5d9-
2012-08-23 20:15:58 DEBUG nova.utils [req-93bac5d9-
2012-08-23 20:15:58 DEBUG nova.utils [req-93bac5d9-
2012-08-23 20:15:58 DEBUG nova.utils [req-93bac5d9-
2012-08-23 20:15:58 DEBUG nova.utils [req-93bac5d9-
Thanks,
-vj
_______
From: dan wendlandt <email address hidden>
To: <email address hidden>
Sent: Thursday, August 23, 2012 9:45 PM
Subject: Re: [Question #206661]: tap devices getting tagged to 4095
Your question #206661 on quantum changed:
https:/
Status: Open => Answered
dan wendlandt proposed the following answer:
4095 is a special "dead" vlan for which all traffic is dropped. the
OVS quantum agent puts a linux device on this vlan if it does not find
a quantum port associated with the device, or if the port that is
found should not be forwarding traffic.
Its possible there's a problem with the communication channel between
the OVS agent on node 2 and the main quantum-server process on node 1.
Providing the logs for the agent on node 2 would probably help.
dan
On Thu, Aug 23, 2012 at 8:11 PM, Vijay
<email address hidden> wrote:
> New question #206661 on quantum:
> https:/
>
> I have installed 2 node environment.
> node 1- controller - nova-compute/
> node 2 - compute node - nova-compute/
>
> VMs launched on controller work fine. I am able to ping/ssh to them.
>
> However, VMs launched on compute node cannot be pinged or sshed.
>
> When i do, sudo ovs-vsctl show, I see that VMs (tap devices) on the compute node are all getting tag: 4095
>
> Also, when look at the console log of the VMs, I see that
>
> No lease, forking to background
> starting DHCP forEthernet interface eth0 [ OK ]
> cloud-setup: checking http:\/
> wget: can't connect to remote host (169.254.169.254): Network is unreachable
> cloud-setup: failed 1\/30: up 10.46. request failed
>
> Any clue is appreciated.
> Thanks,
> vj
>
>
> --
> You received this question notification because you are an answer
> contact for quantum.
--
~~~~~~~
Dan Wendlandt
Nicira, Inc: http://
twitter: danwendlandt
~~~~~~~
--
If this answers your question, please go to the following page to let us
know that it is solved:
https:/
If you still need help, you can reply to this email or go to the
following page to enter your feedback:
https:/
You received this question notification because you asked the question.
Revision history for this message
|
#3 |
Hi Vijay, are you running quantum from source? If so I believe if you do a git pull this should fixed this issue for you. Alternatively if you do; sudo ovs-vsctl list-ports and then remove the interfaces from br-int (ovs-vsctl del-port br-int tapxxxx) that don't show up when you do ifconfig -a this should hopefully resolve the issue for you.
P.S: you can also do ovs-vsctl del-br br-int; ovs-vsctl add-br br-int; to fix this but it will break the network for the vms that are currently attached to br-int.
Revision history for this message
|
#4 |
Can u post which version of quantum u are using, and how u start the agent?
Thanks
Can you help with this problem?
Provide an answer of your own, or ask vj for more information if necessary.