Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

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 question206661@answers.launchpad.net wrote:

New question #206661 on quantum: https://answers.launchpad.net/quantum/+question/206661

I have installed 2 node environment. node 1- controller - nova-compute/nova-api/nova-volume/nova-network/quanutm-server/OpenVswitch in vlan mode/quantum-openvswitch-agent. node 2 - compute node - nova-compute/nova-api/openvswitch/quantum-openvswitch-agent

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:\/\/169.254.169.254\/2009-04-04\/meta-data\/instance-id 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 ~~~~~~~~~~~~~~~~~~~~~~~~~~~