Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

ROUTER GATEWAY AND INTERNAL INTERFACE STATUS ARE DOWN ?

As per your suggestion for the above question we have created new external network "public" 192.168.12.0/24 with gateway having IP matching IP of real router to Internet(which is 192.168.0.3). After adding bridge to the network node, internet connectivity is working fine but, following issues comes

  • when checked in horizon we found the routers internal interface and external interface/gateway status are down and admin status is up(refer the image attached).
  • ifconfig command doesn't show any ip address in VMs but both ip's(internal address as well as floating ip) are displayed on dashboard.
  • virtual machine are not able to ping each other as well as internet

ROUTER GATEWAY AND INTERNAL INTERFACE STATUS ARE DOWN ?

As per your suggestion for the above question we have created new external network "public" 192.168.12.0/24 with gateway having IP matching IP of real router to Internet(which is 192.168.0.3). After adding bridge to the network node, internet connectivity is working fine but, following issues comes

  • when checked in horizon we found the routers internal interface and external interface/gateway status are down and admin status is up(refer the image attached).
  • ifconfig command doesn't show any ip address in VMs but both ip's(internal address as well as floating ip) are displayed on dashboard.
  • virtual machine are not able to ping each other as well as internet

    image description

ROUTER GATEWAY AND INTERNAL INTERFACE STATUS ARE DOWN ?

As per your suggestion for the above question we have created new external network "public" 192.168.12.0/24 with gateway having IP matching IP of real router to Internet(which is 192.168.0.3). After adding bridge to the network node, internet connectivity is working fine but, following issues comes

  • when checked in horizon we found the routers internal interface and external interface/gateway status are down and admin status is up(refer the image attached).
  • ifconfig command doesn't show any ip address in VMs but both ip's(internal address as well as floating ip) are displayed on dashboard.
  • virtual machine are not able to ping each other as well as internet

    image description

For OVS configuration on one of the ethernet interface on network node and OVS bridge, we have made following configuration in ethernet and bridge device:

Bridge device configuration:

DEVICE=br-ex
DEVICETYPE=ovs
TYPE=OVSBridge
MACADDR=f8:0f:41:fc:48:65
BOOTPROTO=static
ONBOOT=yes
IPADDR=192.168.12.2
PREFIX=16
NETMASK=255.255.0.0
GATEWAY=192.168.0.3
DNS1=202.138.96.2
DNS2=8.8.8.8

Ethernet port configuration :

DEVICE=eth3
HWADDR=F8:0F:41:FC:48:65
#TYPE=Ethernet
TYPE=OVSPort
DEVICETYPE=ovs
OVS_BRIDEGE=br-ex
UUID=e84b351d-bfc7-427f-8dda-84a1b1df5f26
ONBOOT=yes
NM_CONTROLLED=no
BOOTPROTO=none
IPADDR=192.168.12.2
PREFIX=16
NETMASK=255.255.0.0
GATEWAY=192.168.0.3
DNS=202.138.96.2
DNS2=8.8.8.8
DEFROUTE=yes
IPV4_FAILURE_FATAL=yes
IPV6INIT=no
NAME="System eth3"

In file /etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini , we updated

bridge_mapping=external:br-ex

In file /etc/neutron/plugin.ini , we updated

type_drivers=gre,flat,vxlan,vlan

The issue remains the same. Please suggest the modifications to be done for successful deployment.

ROUTER GATEWAY AND INTERNAL INTERFACE STATUS ARE DOWN ?

As per your suggestion for the above question we have created new external network "public" 192.168.12.0/24 with gateway having IP matching IP of real router to Internet(which is 192.168.0.3). After adding bridge to the network node, internet connectivity is working fine but, following issues comes

  • when checked in horizon we found the routers internal interface and external interface/gateway status are down and admin status is up(refer the image attached).
  • ifconfig command doesn't show any ip address in VMs but both ip's(internal address as well as floating ip) are displayed on dashboard.
  • virtual machine are not able to ping each other as well as internet

    image description

For OVS configuration on one of the ethernet interface on network node and OVS bridge, we have made following configuration in ethernet and bridge device:

Bridge device configuration:

DEVICE=br-ex
DEVICETYPE=ovs
TYPE=OVSBridge
MACADDR=f8:0f:41:fc:48:65
BOOTPROTO=static
ONBOOT=yes
IPADDR=192.168.12.2
PREFIX=16
NETMASK=255.255.0.0
GATEWAY=192.168.0.3
DNS1=202.138.96.2
DNS2=8.8.8.8

Ethernet port configuration :

DEVICE=eth3
HWADDR=F8:0F:41:FC:48:65
#TYPE=Ethernet
TYPE=OVSPort
DEVICETYPE=ovs
OVS_BRIDEGE=br-ex
UUID=e84b351d-bfc7-427f-8dda-84a1b1df5f26
ONBOOT=yes
NM_CONTROLLED=no
BOOTPROTO=none
IPADDR=192.168.12.2
PREFIX=16
NETMASK=255.255.0.0
GATEWAY=192.168.0.3
DNS=202.138.96.2
DNS2=8.8.8.8
DEFROUTE=yes
IPV4_FAILURE_FATAL=yes
IPV6INIT=no
NAME="System eth3"

In file /etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini , we updated

bridge_mapping=external:br-ex

In file /etc/neutron/plugin.ini , we updated

type_drivers=gre,flat,vxlan,vlan

and ovs-vsctl show

[root@newnetwork network-scripts]# ovs-vsctl show
821c052b-827b-41db-9412-cfa33407d615
    Bridge br-tun
        Port patch-int
            Interface patch-int
                type: patch
                options: {peer=patch-tun}
        Port br-tun
            Interface br-tun
                type: internal
    Bridge br-ex
        Port br-ex
            Interface br-ex
                type: internal
        Port "eth3"
            Interface "eth3"
    Bridge br-int
        fail_mode: secure
        Port int-br-ex
            Interface int-br-ex
        Port "qr-b1dc84d3-a8"
            tag: 4095
            Interface "qr-b1dc84d3-a8"
                type: internal
        Port patch-tun
            Interface patch-tun
                type: patch
                options: {peer=patch-int}
        Port "tap4137ae1e-fb"
            tag: 2
            Interface "tap4137ae1e-fb"
                type: internal
        Port "tap41d2aa33-8f"
            tag: 1
            Interface "tap41d2aa33-8f"
                type: internal
        Port br-int
            Interface br-int
                type: internal
    ovs_version: "2.1.3"

The issue remains the same. Please suggest the modifications to be done for successful deployment.

ROUTER GATEWAY AND INTERNAL INTERFACE STATUS ARE DOWN ?

As per your suggestion for the above question we have created new external network "public" 192.168.12.0/24 with gateway having IP matching IP of real router to Internet(which is 192.168.0.3). After adding bridge to the network node, internet connectivity is working fine but, following issues comes

  • when checked in horizon we found the routers internal interface and external interface/gateway status are down and admin status is up(refer the image attached).
  • ifconfig command doesn't show any ip address in VMs but both ip's(internal address as well as floating ip) are displayed on dashboard.
  • virtual machine are not able to ping each other as well as internet

    image description

For OVS configuration on one of the ethernet interface on network node and OVS bridge, we have made following configuration in ethernet and bridge device:

Bridge device configuration:

DEVICE=br-ex
DEVICETYPE=ovs
TYPE=OVSBridge
MACADDR=f8:0f:41:fc:48:65
BOOTPROTO=static
ONBOOT=yes
IPADDR=192.168.12.2
PREFIX=16
NETMASK=255.255.0.0
GATEWAY=192.168.0.3
DNS1=202.138.96.2
DNS2=8.8.8.8

Ethernet port configuration :

DEVICE=eth3
HWADDR=F8:0F:41:FC:48:65
#TYPE=Ethernet
TYPE=OVSPort
DEVICETYPE=ovs
OVS_BRIDEGE=br-ex
UUID=e84b351d-bfc7-427f-8dda-84a1b1df5f26
ONBOOT=yes
NM_CONTROLLED=no
BOOTPROTO=none
IPADDR=192.168.12.2
PREFIX=16
NETMASK=255.255.0.0
GATEWAY=192.168.0.3
DNS=202.138.96.2
DNS2=8.8.8.8
DEFROUTE=yes
IPV4_FAILURE_FATAL=yes
IPV6INIT=no
NAME="System eth3"

In file /etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini , we updated

bridge_mapping=external:br-ex

In file /etc/neutron/plugin.ini , we updated

type_drivers=gre,flat,vxlan,vlan

and ovs-vsctl show

[root@newnetwork network-scripts]# ovs-vsctl show
821c052b-827b-41db-9412-cfa33407d615
    Bridge br-tun
        Port patch-int
            Interface patch-int
                type: patch
                options: {peer=patch-tun}
        Port br-tun
            Interface br-tun
                type: internal
    Bridge br-ex
        Port br-ex
            Interface br-ex
                type: internal
        Port "eth3"
            Interface "eth3"
    Bridge br-int
        fail_mode: secure
        Port int-br-ex
            Interface int-br-ex
        Port "qr-b1dc84d3-a8"
            tag: 4095
            Interface "qr-b1dc84d3-a8"
                type: internal
        Port patch-tun
            Interface patch-tun
                type: patch
                options: {peer=patch-int}
        Port "tap4137ae1e-fb"
            tag: 2
            Interface "tap4137ae1e-fb"
                type: internal
        Port "tap41d2aa33-8f"
            tag: 1
            Interface "tap41d2aa33-8f"
                type: internal
        Port br-int
            Interface br-int
                type: internal
    ovs_version: "2.1.3"

The According to suggestions which are given do changes some issues gone but some the issue remains the same. Please suggest the modifications to be done for successful deployment.