[rhos-list] Quantum Networking Interfaces.

Gary Kotton gkotton at redhat.com
Sun May 5 07:39:36 UTC 2013


On 05/03/2013 08:42 PM, Minton, Rich wrote:
>
> Quick question regarding quantum networking interfaces, specifically 
> br-int.
>
> I have a 5 node cluster -- 1 Controller/compute node which runs the 
> Quantum server and the l3-agent, 1 Network node which runs the 
> dhcp-agent, and 3 compute nodes. The all have openvswitch installed 
> and I have created the br-int interfaces on all. One thing I noticed 
> is that only the quantum server node (controller) and the network node 
> have an entry for "br-int" when I run the route command. The compute 
> nodes do not.
>

This could be a result of the following:
1. On the nodes that you have routing entry for br-int you most probably 
added a interface , that is, you have created a file 
/etc/sysconfig/network-scripts/ifcfg-br-int
2. On the other nodes you most probably just added br-int to the ovs


>   The VMs on my other compute nodes get an IP from DHCP but I am not 
> able to ping my gateway (10.0.56.1) from within the VM.
>

I have a few questions which hopefully could provide some more details 
(sorry for the silly questions - it is just a bit difficult to debug 
remotely):-
Which version are you using?
Are you able to send pings between VM's on different hosts?
Did you try and capture traffic on the interfaces of the various hosts? 
This may help isolate where the ICMP is being discarded.

Thanks
Gary

> I can ping the same gateway from each of the compute hosts. I 
> double-checked all of my config files and they appear to be correct. I 
> can send any of those along if needed.
>
> Controller -  with Quantum Server
>
> Kernel IP routing table
>
> Destination     Gateway         Genmask         Flags Metric Ref    
> Use Iface
>
> 10.0.0.0        *               255.255.255.0   U     0      0        
> 0 eth0.502
>
> 10.255.254.0    *               255.255.255.0   U     0      0        
> 0 eth0.159
>
> 172.17.0.0      *               255.255.255.0   U     0      0        
> 0 eth0.500
>
> link-local      *               255.255.0.0     U     1003   0        
> 0 eth0
>
> link-local      *               255.255.0.0     U     1004   0        
> 0 eth1
>
> link-local      *               255.255.0.0     U     1009   0        
> 0 br-int
>
> link-local      *               255.255.0.0     U     1010   0        
> 0 eth0.159
>
> link-local      *               255.255.0.0     U     1011   0        
> 0 eth0.500
>
> link-local      *               255.255.0.0     U     1012   0        
> 0 eth0.502
>
> link-local      *               255.255.0.0     U     1028   0        
> 0 br-ex
>
> default         172.17.0.1      0.0.0.0         UG    0      0        
> 0 eth0.500
>
> Network Node
>
> Kernel IP routing table
>
> Destination     Gateway         Genmask         Flags Metric Ref    
> Use Iface
>
> 10.0.0.0        *               255.255.255.0   U     0      0        
> 0 eth0.502
>
> 10.255.254.0    *               255.255.255.0   U     0      0        
> 0 eth0.159
>
> 172.17.0.0      *               255.255.255.0   U     0      0        
> 0 eth0.500
>
> 10.0.56.0       *               255.255.248.0   U     0      0        
> 0 tapaee8f28f-74
>
> link-local      *               255.255.0.0     U     1003   0        
> 0 eth0
>
> link-local      *               255.255.0.0     U     1004   0        
> 0 eth1
>
> link-local      *               255.255.0.0     U     1009   0        
> 0 br-int
>
> link-local      *               255.255.0.0     U     1010   0        
> 0 eth0.159
>
> link-local      *               255.255.0.0     U     1011   0        
> 0 eth0.500
>
> link-local      *               255.255.0.0     U     1012   0        
> 0 eth0.502
>
> default         172.17.0.1      0.0.0.0         UG    0      0        
> 0 eth0.500
>
> Compute Nodes
>
> Kernel IP routing table
>
> Destination     Gateway         Genmask         Flags Metric Ref    
> Use Iface
>
> 10.0.0.0        *               255.255.255.0   U     0      0        
> 0 eth0.502
>
> 10.255.254.0    *               255.255.255.0   U     0      0        
> 0 eth0.159
>
> 172.17.0.0      *               255.255.255.0   U     0      0        
> 0 eth0.500
>
> link-local      *               255.255.0.0     U     1005   0        
> 0 eth0
>
> link-local      *               255.255.0.0     U     1006   0        
> 0 eth1
>
> link-local      *               255.255.0.0     U     1042   0        
> 0 eth0.159
>
> link-local      *               255.255.0.0     U     1043   0        
> 0 eth0.500
>
> link-local      *               255.255.0.0     U     1044   0        
> 0 eth0.502
>
> default         172.17.0.1      0.0.0.0         UG    0      0        
> 0 eth0.500
>
> Ok, so this may not be a quick question...
>
> Once again, all or your help is greatly appreciated.
>
> Rick
>
> _Richard Minton_
>
> LMICC Systems Administrator
>
> 4000 Geerdes Blvd, 13D31
>
> King of Prussia, PA 19406
>
> Phone: 610-354-5482
>
>
>
> _______________________________________________
> rhos-list mailing list
> rhos-list at redhat.com
> https://www.redhat.com/mailman/listinfo/rhos-list

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/rhos-list/attachments/20130505/73b968df/attachment.htm>


More information about the rhos-list mailing list