[ https://issues.apache.org/jira/browse/CLOUDSTACK-6841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Murali Reddy updated CLOUDSTACK-6841: ------------------------------------- Assignee: (was: Murali Reddy) > [OVS] Remote_ips for tunnel ports are not configured properly in case of > multipel physical networks > ---------------------------------------------------------------------------------------------------- > > Key: CLOUDSTACK-6841 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6841 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server, Network Controller > Affects Versions: 4.4.0 > Environment: Latest build from 4.4 with commit > 32bbc84db99d0e5f7f9b2a3fb41e4e783a2de350 > Reporter: Sanjeev N > Priority: Critical > Labels: ovs > Fix For: Future > > Attachments: cloud-44.dmp, management-server.rar, > ovstunnel-host13.log, ovstunnel-host14.log > > > [OVS] Remote_ips for tunnel ports are not configured properly in case of > multipel physical networks > Steps to reproduce: > ============== > 1.Bring up CS in advanced zone with xen cluster with min of two hosts > and two nics on both the hosts > 2.Create two physical networks with GRE isolation during zone creation: > in physical network1 add guest,public&management traffic types with tag "tag1" > in physical network2 add only guest traffic with tag "tag2" > 3.create two network offerings NO1&NO2 with virtual networking and ovs as the > connectivity service provider and user taggings tag1 & tag2 in NO1 & NO2 > respectively > 4.Create isolated networks nw1 & nw2 using NO1 & NO2 > 5.Deploy vms in both the netwoks and make sure that both the networks are > spread across both the hosts in the cluster > 6.Verify tunnel ports remote_ips on both the hosts > On xenservers used NIC0 for physical network1(by using traffic labels) and > NIC1 for physical network2 > NIC0&NIC1 both have routable IP addresses. > Result: > ===== > Remote_ips for all the tunnel ports created in the above networks are set to > NIC1 ip addresses. But tunnel ports in network created on physical network1 > should have NIC0 ip address as remote_ip and NIC1 ip address for the tunnel > ports in other network. > mysql> select * from ovs_tunnel_interface; > +----+--------------+---------------+-------------------+---------+------------+ > | id | ip | netmask | mac | host_id | label > | > +----+--------------+---------------+-------------------+---------+------------+ > | 1 | 0 | 0 | 0 | 0 | lock > | > | 2 | 10.147.42.13 | 255.255.255.0 | 78:2b:cb:74:c4:ab | 1 | > management | > | 3 | 10.147.42.14 | 255.255.255.0 | d4:ae:52:7a:a5:9d | 2 | > management | > | 4 | 10.147.42.13 | 255.255.255.0 | 78:2b:cb:74:c4:ab | 1 | gre > | > | 5 | 10.147.42.14 | 255.255.255.0 | d4:ae:52:7a:a5:9d | 2 | gre > | > +----+--------------+---------------+-------------------+---------+------------+ > 5 rows in set (0.00 sec) > Here management label is on NIC0 and gre is on NIC1 and > 10.147.42.13&10.147.42.14 are assigned to NIC1 on the hosts. > But in the above table we are using same ip address against bot the labels. > So tunnel ports for both the networks are created with same remote_ip address. > Host details are as follows: > mysql> select > id,name,private_ip_address,public_ip_address,data_center_id,cluster_id from > host where id in (1,2); > +----+-----------------+--------------------+-------------------+----------------+------------+ > | id | name | private_ip_address | public_ip_address | > data_center_id | cluster_id | > +----+-----------------+--------------------+-------------------+----------------+------------+ > | 1 | Rack1Pod1Host13 | 10.147.40.13 | 10.147.40.13 | > 1 | 1 | > | 2 | Rack1Pod1Host14 | 10.147.40.14 | 10.147.40.14 | > 1 | 1 | > +----+-----------------+--------------------+-------------------+----------------+------------+ > 2 rows in set (0.00 sec) > 10.147.40.13& 10.147.40.14 ip addresses are management addresses assigned to > NIC0 on both the hosts. > Tunnel ports details on the hosts are: > system@xapi16: > lookups: hit:11752 missed:3227 lost:0 > flows: 4 > port 0: xapi16 (internal) > port 1: t4018-2-1 (gre: key=4018, remote_ip=10.147.42.13) > port 2: vif26.0 > system@xapi15: > lookups: hit:4359 missed:167 lost:0 > flows: 0 > port 0: xapi15 (internal) > port 1: t992-2-1 (gre: key=992, remote_ip=10.147.42.13) > port 2: vif25.0 > Attaching MS log file, cloud DB and ovstunnel log files. -- This message was sent by Atlassian JIRA (v6.3.4#6332)