博客
关于我
强烈建议你试试无所不能的chatGPT,快点击我
floodlight make the VMs can not getDHCP IP address
阅读量:4490 次
发布时间:2019-06-08

本文共 2105 字,大约阅读时间需要 7 分钟。

这个问题我也遇到了,但是没人回答。

floodlight make the VMs can not getDHCP IP address

Asked by   
on 2014-01-14
 

I used the floodlight as the openflow controller in openstack. in the compute node ,I use the command "set-controller IP:port" to set the floodlight address as the ovs bridge br-int's controller. but when I typed the command,I found the OVS flow tables were flushed,the flow rules were deleted . So when I created a VM,the VM could not get the DHCP IP address,my Openstack is Grizzly vlan mode,I found the DHCP reply from network node could not recived by VM.

 Does you have the same problem? Does floodlight can be used in OPENSTACk as the openvswitch's controller? I used the floodlight to get the virtual network topology.

before I set the controller ,the OVS flow table is like this:

[root@node8 ~]# ovs-ofctl dump-flows br-int
NXST_FLOW reply (xid=0x4):
 cookie=0x0, duration=52.074s, table=0, n_packets=11, n_bytes=1430, idle_age=15, priority=3,in_port=29,dl_vlan=1000 actions=mod_vlan_vid:8,NORMAL
 cookie=0x0, duration=307.365s, table=0, n_packets=8123, n_bytes=728475, idle_age=0, priority=0 actions=NORMAL

[root@node8 ~]# ovs-vsctl show

3fa12857-c008-451f-a6f3-70cf30d1b92e
    Bridge br-int
        Port "qvoab109943-af"
            tag: 8
            Interface "qvoab109943-af"
        Port br-int
            Interface br-int
                type: internal
        Port "int-br-eth1"
            Interface "int-br-eth1"
    Bridge "br-eth1"
        Port "eth1"
            Interface "eth1"
        Port "phy-br-eth1"
            Interface "phy-br-eth1"
        Port "br-eth1"
            Interface "br-eth1"
                type: internal
    ovs_version: "1.7.1"

but after I set the controller,the flow tables is like this:

[root@node8 ~]# ovs-ofctl dump-flows br-int

NXST_FLOW reply (xid=0x4):

[root@node8 ~]# ovs-vsctl show

3fa12857-c008-451f-a6f3-70cf30d1b92e
    Bridge br-int
        Controller "tcp:10.0.0.7"
            is_connected: true
        Port "qvoab109943-af"
            tag: 8
            Interface "qvoab109943-af"
        Port br-int
            Interface br-int
                type: internal
        Port "int-br-eth1"
            Interface "int-br-eth1"
    Bridge "br-eth1"
        Port "eth1"
            Interface "eth1"
        Port "phy-br-eth1"
            Interface "phy-br-eth1"
        Port "br-eth1"
            Interface "br-eth1"
                type: internal
    ovs_version: "1.7.1"

转载于:https://www.cnblogs.com/duanguyuan/p/3530102.html

你可能感兴趣的文章
Hook基本知识
查看>>
Hook CreateProcess
查看>>
C#与C++之间类型的对应
查看>>
(C++C#类型互转工具)使用Signature Tool自动生成P/Invoke调用Windows API的C#函数声明...
查看>>
面试题
查看>>
Powershell + HTA
查看>>
IFG以太网帧间隙
查看>>
WINDOWS API 大全(一)
查看>>
Wmic
查看>>
WINDOWS API 大全(二)
查看>>
SetWindowsHookEx失败
查看>>
C/C++判断字符串是否包含某个字符串
查看>>
[C#菜鸟]C# Hook
查看>>
easyhook源码分析二——注入
查看>>
C#调用C++的库 P/Invoke工具集
查看>>
easyhook源码分析三——申请钩子
查看>>
easyhook源码分析一
查看>>
对“XXX::Invoke”类型的已垃圾回收委托进行了回调。这可能会导致应用程序崩溃、损坏和数据丢失。向非托管代码传递委托时,托管应用程序必须让这些委托保持活动状态,直到确信不会再次调用它们...
查看>>
VC中MessageBox与AfxMessageBox用法与区别
查看>>
Web开发使用jsTree实例
查看>>