subnet interface status is down in router when create new routers
This is my scenario:
- Liberty
- RDO
- Centos 7
Topology:
(Internet)----(1)Physical Router(2)-----(em1)Manager(em2)----(em1)Compute node
Physical Router:
- Interface 1: xxx.yyy.zzz.www
- Interface 2: 192.168.70.1/24
Manager:
- em1: 192.168.70.10/24
- em2: 192.168.80.1/24
Compute node:
- em1: 192.168.80.13/24
This is what I do first:
In "Manager" I add this line to /etc/sysctl.conf:
net.ipv4.ip_forward = 1
Then, in "Manager":
# systemctl stop NetworkManager
# systemctl disable NetworkManager
# systemctl enable network
# systemctl disable firewalld
# systemctl stop firewalld
# yum update -y
# yum install -y https://rdoproject.org/repos/rdo-release.rpm
# yum update -y
# yum install -y openstack-packstack
# yum update -y
Reboot the box.
Then, in the "Compute Node" server I do the same than in the "Manager" server. All the traffic pass thru the "Manager" server, that has IP forwarding enabled.
Then, I generate the answer file:
packstack --gen-answer-file=respuestas.cfg
The only change I made on the response file:
CONFIG_COMPUTE_HOSTS=192.168.80.13
So, everything is installed on the Server called "Manager" and the only thing is installed on the other server is Nova (and Neutron Agent).
Once everything is installed, in the "Manager" server, I create the file /etc/sysconfig/network-scripts/ifcfg-br-ex and put this in there:
DEVICE=br-ex
DEVICETYPE=ovs
TYPE=OVSBridge
BOOTROTO=static
IPADD=192.168.80.1
NETMSK=255.255.255.0
DNS1=8.8.8.8
ONBOOT=yes
Then, in "Manager" I edit the /etc/sysconfig/network-scripts/ifcfg-em2 file and add/change this:
TYPE=OVSPort
DEVICETYPE=ovs
OVS_BRIDGE=br-ex
And then, I edit /etc/neutron/plugin.ini and add this:
network_vlan_ranges = physnet1
bridge_mappings = physnet1:br-ex
Finally, I restart network service:
# systemctl restart network.service
In Horizon, I create the correct rules in "Access & Security"/"Security Groups" section.
Now, due the "demo" project is created, I will use that internal network and router to connect my first instance (that is launched on the "admin" project). In order to do that, I edit the "private" network, make it shared, and then I'm able to launch an instance (cirros), ping the router (default gateway) and everything. I Can use floating IPs and they work fine.
The problem is when I want to create new networks/routers. This is what I do, as "admin" user:
# . keystonerc_admin
# neutron router-create router_test
# neutron net-create network_new_lan --provider:network_type vxlan
# neutron subnet-create --name subnet_new_lan --enable_dhcp --allocation-pool=start=172.16.90.2,end=172.16.90.254 --gateway=172.16.90.1 --dns-nameserver 8.8.8.8 network_new_lan 172.16.90.0/24
# neutron router-interface-add router_test subnet=subnet_new_lan
At this point, If I see in the "interfaces" section inside Project/Network/Routers in Horizon, in the "router_test" router, I'll see a "Down" status in the internal interface (which is the one we just created).
Any instance that uses this internal subnet (subnet_new_lan) will not get an IP and, of course, will not have connectivity to the router nor internet, nor nothing (because it doesn't ...
Don't touch sysctl.conf before running packstack.
I have to, because the second server ("Compute Node", 192.168.80.13) needs the IP forwarding from "Manager" in order to reach the Internet and download packages and stuff.